03-15-2016 11:00 PM - edited 03-12-2019 12:29 AM
We are having ASA 5580 in active-standby mode all interfaces are gig interfaces, due to high traffic on inside interface we want to bundle two ports for inside. Now problem is that the device is under production and is having more than around 400 lines of ACL under that inside interface along with some static routes also.
What troubles me :-
Please guide me for performing this activity on ASA.
Thanks,
Bhushit
Solved! Go to Solution.
03-16-2016 02:46 PM
You do not "need" to reload the ASA when configuring port-channels.
To configure the existing port into a port-channel you need to remove the nameif command from the interface. removing this will also remove all other commands that reference this interface name.
This is not a good option as you will need to reload both the ASA's. I suggest copying the running config out, change the interface configuration to have portchannel, then copy it back to the primary ASA's running-config. This will give little to no down time.
--
Please remember to select a correct answer and rate helpful posts
03-16-2016 11:51 PM
What I am suggesting is the following:
1. copy the running configuration out to an FTP server
copy running-config ftp://username:password@<FTPSERVERIP
2. edit the configuration with the following. Keep in mind that this is just an example and you should change the configuration to your needs and edit the relevant interface as well as adding in the new port-channel. it is important that you keep the exact same nameif, security-level, and IP that was on the interface you are moving to the port-channel.
interface Gig0/1
no nameif
no security-level
no ip add
channel-group 1 mode on
interface Gig0/2
channel-group 1 mode on
no shut
interface po1
security-level 100
nameif inside
ip add 10.10.10.1 255.255.255.0 standby 10.10.10.2
3. Save the file and copy it back to the ASAs running configuration:
copy ftp://username:password@<FTPSERVERIP running-config
4. Check to see that the Primary ASA is still the Active ASA. Check to see that the configuration has been changed correctly and that traffic is flowing as normal.
5. save the ASA configuration.
--
Please remember to select a correct answer and rate helpful posts
03-16-2016 02:46 PM
You do not "need" to reload the ASA when configuring port-channels.
To configure the existing port into a port-channel you need to remove the nameif command from the interface. removing this will also remove all other commands that reference this interface name.
This is not a good option as you will need to reload both the ASA's. I suggest copying the running config out, change the interface configuration to have portchannel, then copy it back to the primary ASA's running-config. This will give little to no down time.
--
Please remember to select a correct answer and rate helpful posts
03-16-2016 09:59 PM
With restart, I was referring to that method of swapping the startup-config with new configuration.
" I suggest copying the running config out, change the interface configuration to have portchannel, then copy it back to the primary ASA's running-config. This will give little to no down time."
Didn't get you there you mean after removing nameif from an interface, creating portchannel and putting nameif, I copy my running config into the console ?
This will take much time to paste the full config as my current running config is too lengthy with more than 20000 objects and more than 1000 rules.
What if I just copy that interface related(nameif related - routes and ACL) running config back ?
Thanks again,
Bhushit
03-16-2016 11:51 PM
What I am suggesting is the following:
1. copy the running configuration out to an FTP server
copy running-config ftp://username:password@<FTPSERVERIP
2. edit the configuration with the following. Keep in mind that this is just an example and you should change the configuration to your needs and edit the relevant interface as well as adding in the new port-channel. it is important that you keep the exact same nameif, security-level, and IP that was on the interface you are moving to the port-channel.
interface Gig0/1
no nameif
no security-level
no ip add
channel-group 1 mode on
interface Gig0/2
channel-group 1 mode on
no shut
interface po1
security-level 100
nameif inside
ip add 10.10.10.1 255.255.255.0 standby 10.10.10.2
3. Save the file and copy it back to the ASAs running configuration:
copy ftp://username:password@<FTPSERVERIP running-config
4. Check to see that the Primary ASA is still the Active ASA. Check to see that the configuration has been changed correctly and that traffic is flowing as normal.
5. save the ASA configuration.
--
Please remember to select a correct answer and rate helpful posts
03-16-2016 11:51 PM
Yeah got it !!
Thanks !!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide