Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- :
- About fadzila_h
Stats
Member since
08-14-2007
6
Posts
0
Helpful
0
Solutions
07-20-2014
07:20 PM
Hi Lauzamor, Although I already have the answer from Jouni, I am interested to hear result from your test too. Thank you. - Fadzila
... View more
07-20-2014
07:16 PM
Hi Jouni, Thank you very much for feedback and advice. Meaning all that I need to do is the following and there should be no impact to existing traffic. I will inform this to my team mates :D ------------------------------------------------------------------ Step 1: config t Step 2: interface GigabitEthernet1 nameif NEWNAME exit Step 3: access-list inside_access_in rename NEWNAME_access_in ------------------------------------------------------------------
... View more
07-16-2014
08:09 PM
Hi Lauzamor, Yes please help double check on this. Thank you very much for assistance.
... View more
07-16-2014
07:53 PM
Hi Lauzamor, Thank you for the reply. But during step 1 - the moment I applied the name change on ASDM - I saw the following on the show run - it looks like the "access-group inside_access_in" automatically associated to new interface name "inside-NEWNAME". The interface details, MTU and the route all automatically change to point to new interface name. --------------------------------------------- interface GigabitEthernet1 nameif inside-NEWNAME security-level 100 ip address 192.168.10.1 255.255.255.0 standby 192.168.10.2 mtu inside-NEWNAME 1500 route inside-NEWNAME 192.168.50.0 255.255.255.0 192.168.1.1 1 route inside-NEWNAME 192.168.60.0 255.255.255.0 192.168.1.1 1 access-group inside_access_in in interface inside-NEWNAME ----------------------------------------------------------- So I was wonder if the traffic from inside interface will be processed correctly by this time. Btw - i was testing this on ASA 8.4 using GNS3 lab. Would it be different if using 8.3 ?
... View more
07-16-2014
07:22 AM
Hi All, Need your advise on procedure to rename ASA interface on live firewall. I have prepared a workplan to rename an interface on ASA 8.3 as below. Will there be any impact the existing live traffic going through the intrface? ====================================================== \\ Original interface name interface GigabitEthernet1 nameif inside security-level 100 ip address 192.168.10.1 255.255.255.0 standby 192.168.10.2 access-list inside_access_in extended permit tcp object HOST-192.168.1.10 object net-DMZ-172.16.0.0-25 eq ftp access-list inside_access_in extended permit tcp object HOST-192.168.1.11 object HOST-172.16.0.130 eq https access-list inside_access_in extended permit tcp object HOST-192.168.1.12 object net-DMZ-172.16.0.0-25 eq ssh mtu inside 1500 route inside 192.168.50.0 255.255.255.0 192.168.1.1 1 route inside 192.168.60.0 255.255.255.0 192.168.1.1 1 ====================================================== \\ ##STEP 1. Execute rename the interface using Cisco ASA ASDM Interface GigabitEthernet1 nameif inside-NEWNAME ====================================================== \\ Result After interface name changed interface GigabitEthernet1 nameif inside-NEWNAME security-level 100 ip address 192.168.10.1 255.255.255.0 standby 192.168.10.2 access-list inside_access_in extended permit tcp object HOST-192.168.1.10 object net-DMZ-172.16.0.0-25 eq ftp access-list inside_access_in extended permit tcp object HOST-192.168.1.11 object HOST-172.16.0.130 eq https access-list inside_access_in extended permit tcp object HOST-192.168.1.12 object net-DMZ-172.16.0.0-25 eq ssh mtu inside-NEWNAME 1500 route inside-NEWNAME 192.168.50.0 255.255.255.0 192.168.1.1 1 route inside-NEWNAME 192.168.60.0 255.255.255.0 192.168.1.1 1 access-group inside_access_in in interface inside-NEWNAME ====================================================== \\ ##STEP 2. Execute using CLI to rename the access-list access-list inside_access_in rename inside-NEWNAME_access_in Result: ------------ access-list inside-NEWNAME_access_in extended permit tcp object HOST-192.168.1.10 object net-DMZ-172.16.0.0-25 eq ftp access-list inside-NEWNAME_access_in extended permit tcp object HOST-192.168.1.11 object HOST-172.16.0.130 eq https access-list inside-NEWNAME_access_in extended permit tcp object HOST-192.168.1.12 object net-DMZ-172.16.0.0-25 eq ssh access-group inside-NEWNAME_access_in in interface inside-NEWNAME ========================================================= Thank you. Fadzila
... View more
- Tags:
- #asa #firewall
Labels:
07-20-2014
Hi Lauzamor,Although I already have the answer from Jouni, I am
interested to hear result from your ...
07-20-2014
Hi Jouni,Thank you very much for feedback and advice.Meaning all that I
need to do is the following ...
07-16-2014
Hi Lauzamor,Thank you for the reply.But during step 1 - the moment I
applied the name change on ASDM...
Public Statistics
| Date Registered | 08-14-2007 06:38 PM |
| Date Last Visited | 08-18-2017 03:56 AM |
| Total Messages Posted | 6 |
