10-11-2019 09:46 AM - edited 02-21-2020 09:34 AM
Hello All,
I have 13 ASA's and the ASDM is able to reach all of them except one.
I have went through all the troubleshooting and all the forum answers on here and it still isnt reachable.
Can someone recommend anything?
Thanks in advance,
E
Solved! Go to Solution.
10-16-2019 06:48 AM
Here is outside:
Gateway of last resort is 1.1.1.1 to network 0.0.0.0
S* 0.0.0.0 0.0.0.0 [1/0] via 1.1.1.1, outside
S 4.2.2.2 255.255.255.255 [1/0] via 1.1.1.1, outside
C 1.1.1.1 255.255.255.224 is directly connected, outside
L 1.1.1.1 255.255.255.255 is directly connected, outside
Here is outside-backup:
Gateway of last resort is 1.1.1.1 to network 0.0.0.0
S 8.8.8.8 255.255.255.255 [1/0] via 2.2.2.2, outside-backup
C 2.2.2.2 255.255.255.252 is directly connected, outside-backup
L 2.2.2.2 255.255.255.255 is directly connected, outside-backup
And here is sho int ip brief:
ASA5506# sho int ip brief
Interface IP-Address OK? Method Status Protocol
Virtual0 127.1.0.1 YES unset up up
GigabitEthernet1/1 1.1.1.1 YES CONFIG up up
GigabitEthernet1/2 2.2.2.2 YES CONFIG up up
GigabitEthernet1/3 192.168.20.1 YES CONFIG up up
GigabitEthernet1/4 192.168.120.1 YES CONFIG up up
GigabitEthernet1/5 10.254.254.1 YES CONFIG up up
GigabitEthernet1/6 unassigned YES unset administratively down down
GigabitEthernet1/7 unassigned YES unset administratively down down
GigabitEthernet1/8 unassigned YES unset administratively down down
Internal-Control1/1 127.0.1.1 YES unset up up
Internal-Data1/1 unassigned YES unset up up
I am going from a 192.168.30.0 subnet to 192.168.20.0 subnet. Different office, different state. I rebooted it again last night and still cant reach it.
Thanks,
E
Internal-Data1/2 unassigned YES unset up up
Internal-Data1/3 unassigned YES unset up up
Internal-Data1/4 169.254.1.1 YES unset up up
Management1/1 unassigned YES unset up up
NorthVa5506#
10-16-2019 07:07 AM
Is 192.168.30.0/24 coming in over a VPN connection on the outside interface? If yes, do you have the command management-access <interface> where interface is the interface name of the interface you are trying to connect to?
You do not have the 192.168.30.0/24 subnet defined in you http list
ASA# sho run http
http server enable
http 192.168.1.0 255.255.255.0 outside-backup
http 192.168.2.0 255.255.255.0 outside
If you are accessing the interface with IP 192.168.20.1 then you would need to add the command http 192.168.30.0 255.255.255.0 <interface name> where interface name is the name of the interface you are trying to connect to as well as management-access command I mentioned earlier.
10-16-2019 07:36 AM - edited 10-16-2019 07:39 AM
Hi @Marius Gunnerud you are the man.
I added the http 192.168.30.0 inside on the target ASA and it worked.
I have ASDM pulled up and I am able to upgrade the image.
Thank you very much,
E
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