We value your feedback.
Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!
Course Of The Month
7 days, 7 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Unable to see all interfaces configured on Cisco ASA 5505
Posted on 2012-12-30
I have a Base license ASA 5505 that's restricted to 3 vlans
vlan1 is the inside interface 192.168.1.1
vlan2 is the outside interface x.x.x.x
vlan3 is being set up to be an isolated IP range so Ethernet 0/7 is enabled with a security level 100 and an IP of 192.168.168.1 (restricted traffic flow is set to restrict traffic to vlan1 (inside))
Now both the 192.168.1.1 interface and the 192.168.168.1 interfaces are connected to the same switch and from there I have a single test machine that is also connected to the same switch.
There is no DHCP set on either interfaces.. I have a static address set on the workstation of 192.168.168.2
my problem is I am not understanding why I can not even ping the 192.168.168.1 interface.
If I switch the workstation over to 192.168.1.2 I can see the 192.168.1.1 interface fine.
Am I missing something with the "restricted traffic flow" setting
Enable traffic between two or more interfaces with the same security level is unchecked (ADSM)
And enable traffic between two or more hosts connected to the same interface is also unchecked (ADSM)
Any help would be appreciated
vlan1 is the inside interface 192.168.1.1
vlan2 is the outside interface x.x.x.x
vlan3 is being set up to be an isolated IP range so Ethernet 0/7 is enabled with a security level 100 and an IP of 192.168.168.1 (restricted traffic flow is set to restrict traffic to vlan1 (inside))
Now both the 192.168.1.1 interface and the 192.168.168.1 interfaces are connected to the same switch and from there I have a single test machine that is also connected to the same switch.
There is no DHCP set on either interfaces.. I have a static address set on the workstation of 192.168.168.2
my problem is I am not understanding why I can not even ping the 192.168.168.1 interface.
If I switch the workstation over to 192.168.1.2 I can see the 192.168.1.1 interface fine.
Am I missing something with the "restricted traffic flow" setting
Enable traffic between two or more interfaces with the same security level is unchecked (ADSM)
And enable traffic between two or more hosts connected to the same interface is also unchecked (ADSM)
Any help would be appreciated
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
5
7 Comments
I have not touched the vlan configs at all on the switch, I assumed on HP procurve switches that all the ports are untagged.
I can post the config shortly .
I can post the config shortly .
If your workstations is Windows system, check arp result.. "arp -a" in command promt.
If the result is "192.168.168.1 xx-xx-xx-xx-xx-xx dynamic", Layer 2 is working correctly which mean problem area will be ASA only.
If the result is "incomplete", i would prefer direct testing which is your workstation is directly connected to 192.168.168.1 interface.
Hope this help.
Regards,
If the result is "192.168.168.1 xx-xx-xx-xx-xx-xx dynamic", Layer 2 is working correctly which mean problem area will be ASA only.
If the result is "incomplete", i would prefer direct testing which is your workstation is directly connected to 192.168.168.1 interface.
Hope this help.
Regards,
If I connect a note book directly to the interface every thing works fine. I have subsequently upgraded the ASA to the Security + model. and now have a total of 4 VLANS.
as long as I isolate the interface on its own switch every thing works fine.
I know the config you see below is missing a translation rule... but right now I just want to be able to ping the interface
I apologize ahead of time the config has changed a little since I first posted.
Result of the command: "show run"
: Saved
:
ASA Version 8.2(5)
!
hostname ciscoasa
enable password ****************** encrypted
passwd ************** encrypted
names
!
interface Ethernet0/0
switchport access vlan 2
!
interface Ethernet0/1
switchport access vlan 2
!
interface Ethernet0/2
switchport access vlan 2
!
interface Ethernet0/3
!
interface Ethernet0/4
!
interface Ethernet0/5
switchport access vlan 4
!
interface Ethernet0/6
!
interface Ethernet0/7
switchport access vlan 3
!
interface Vlan1
nameif inside
security-level 100
ip address 192.168.169.2 255.255.255.0
!
interface Vlan2
nameif outside
security-level 0
ip address *.*.*.* 255.255.255.224
!
interface Vlan3
nameif ISOLATED
security-level 100
ip address 10.1.10.1 255.255.255.0
!
interface Vlan4
nameif TEST
security-level 100
ip address 10.10.10.1 255.255.255.0
!
ftp mode passive
pager lines 24
logging enable
logging asdm informational
mtu inside 1500
mtu outside 1500
mtu ISOLATED 1500
mtu TEST 1500
no failover
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0
nat (ISOLATED) 1 0.0.0.0 0.0.0.0
route outside 0.0.0.0 0.0.0.0 *.*.*.* 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-reco
http server enable
http 0.0.0.0 0.0.0.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
crypto ca trustpoint _SmartCallHome_ServerCA
crl configure
crypto ca certificate chain _SmartCallHome_ServerCA
certificate ca 6ecc7aa5a7032009b8cebcf4e9
quit
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd auto_config outside
!
dhcpd address 192.168.169.170-192.168.16
dhcpd dns 8.8.8.8 interface inside
dhcpd enable inside
!
dhcpd address 10.1.10.100-10.1.10.110 ISOLATED
dhcpd dns 8.8.8.8 interface ISOLATED
dhcpd enable ISOLATED
!
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
webvpn
!
!
prompt hostname context
: end
as long as I isolate the interface on its own switch every thing works fine.
I know the config you see below is missing a translation rule... but right now I just want to be able to ping the interface
I apologize ahead of time the config has changed a little since I first posted.
Result of the command: "show run"
: Saved
:
ASA Version 8.2(5)
!
hostname ciscoasa
enable password ****************** encrypted
passwd ************** encrypted
names
!
interface Ethernet0/0
switchport access vlan 2
!
interface Ethernet0/1
switchport access vlan 2
!
interface Ethernet0/2
switchport access vlan 2
!
interface Ethernet0/3
!
interface Ethernet0/4
!
interface Ethernet0/5
switchport access vlan 4
!
interface Ethernet0/6
!
interface Ethernet0/7
switchport access vlan 3
!
interface Vlan1
nameif inside
security-level 100
ip address 192.168.169.2 255.255.255.0
!
interface Vlan2
nameif outside
security-level 0
ip address *.*.*.* 255.255.255.224
!
interface Vlan3
nameif ISOLATED
security-level 100
ip address 10.1.10.1 255.255.255.0
!
interface Vlan4
nameif TEST
security-level 100
ip address 10.10.10.1 255.255.255.0
!
ftp mode passive
pager lines 24
logging enable
logging asdm informational
mtu inside 1500
mtu outside 1500
mtu ISOLATED 1500
mtu TEST 1500
no failover
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0
nat (ISOLATED) 1 0.0.0.0 0.0.0.0
route outside 0.0.0.0 0.0.0.0 *.*.*.* 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-reco
http server enable
http 0.0.0.0 0.0.0.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
crypto ca trustpoint _SmartCallHome_ServerCA
crl configure
crypto ca certificate chain _SmartCallHome_ServerCA
certificate ca 6ecc7aa5a7032009b8cebcf4e9
quit
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd auto_config outside
!
dhcpd address 192.168.169.170-192.168.16
dhcpd dns 8.8.8.8 interface inside
dhcpd enable inside
!
dhcpd address 10.1.10.100-10.1.10.110 ISOLATED
dhcpd dns 8.8.8.8 interface ISOLATED
dhcpd enable ISOLATED
!
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
webvpn
!
!
prompt hostname context
: end
Featured Post
Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Occasionally, we encounter connectivity issues that appear to be isolated to cable internet service. The issues we typically encountered were reset errors within Internet Explorer when accessing web sites or continually dropped or failing VPN conne…
This article offers some helpful and general tips for safe browsing and online shopping. It offers simple and manageable procedures that help to ensure the safety of one's personal information and the security of any devices.
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Suggested Courses
Course of the Month7 days, 7 hours left to enroll
729 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.