cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

498
Views
0
Helpful
3
Replies

ASA 5555

So I have a ASA 5555, coming off it I have a L3 Switch. This switch has its own set of VLANs that I would like to keep seperate from another vlan database on another L3 switch hanging off it as well that houses a seperate network. I would like to be able to monitor the network from one side to the other with NMS software and scans etc. Should I have a router on a stick configuration for the interfaces to allow the vlans to communicate with the inside network for SNMP and other software and how will this interfere with VLANs that may have the same id, wouldn't those machines essentially be able to talk when that is not the intended behavior. I was going for being able to monitor each network but essentially routing to another network allowing each to have their own vlan database without them bleeding into each other.

1 ACCEPTED SOLUTION

Accepted Solutions
Rob Ingram
VIP Mentor

@DerekLazarus78183 

So you have L3 switch > ASA > L3 switch?

 

If each L3 switch has an SVI for the local networks, configure a routed link between the switch and the ASA. Define static routes on the ASA to each network, via the next hop, the ASA won't know about the VLAN IDs. You'll obviously have to permit traffic via an ACL inbound on the ASAs interface.

View solution in original post

3 REPLIES 3
Rob Ingram
VIP Mentor

@DerekLazarus78183 

So you have L3 switch > ASA > L3 switch?

 

If each L3 switch has an SVI for the local networks, configure a routed link between the switch and the ASA. Define static routes on the ASA to each network, via the next hop, the ASA won't know about the VLAN IDs. You'll obviously have to permit traffic via an ACL inbound on the ASAs interface.

View solution in original post

Yes

I pretty much had already set things up this way turns out there was a software config issue with repositories not being configured for particular subnets after deep diving into everything. Thanks !