Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I am having a very strange issue. Initially I thought this was a simple fix...5 hours later i am still in the same predicament. I am simply trying to use an ASA 5505 as a router. Why not use a router you ask, unfortunately I do not have that optio...
We are having some strange behavior with an REP segment. Several times a day we get a link failure and the following message is in the ME3400 switch that drops the link. We are monitoring the CPU utilization and see no spike during the time that th...
Ok, so it looks like, of the IP'd devices on the "inside" of the 5505 (192.168.1.x) may in fact have a mis-configuration though I was assured that all was well...
That address (1.116) is reachable through the whole path..it is the only one of mess..s...
I have another piece to the puzzle that only makes things even more confusing...
There is a subnet (who's SVI is on the same core switch) that can reach the 192.168.1.x network both ways. 10.3.201.x. I attached a couple screenshots they took.
Yeah I have asked them 3 times to verify that..they ensure me that is all correct. Guess I will need to validate myself. The capture shows inbound but no outbound.
access-list cap line 1 extended permit ip any4 any4 (hitcnt=23914)
capture capin typ...
Hey Jon,
No worries, I am here because I am out of ideas, no harm in double checking.
Yes same client with no firewall blocking ICMP. I have done the packet tracer and the ASA comes back saying all should pass:
5505(config)# packet-tracer input engi...
Yeah everything points to something in the ASA it seems. I just have no clue what that is...I have upgraded the code and see no bugs related. The config is just about replicated from the other ASA that is passing traffic...no clue at this point. T...
