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.
Hi folks,I have an unusual one I need some help with. I have a pair of 5525's active/standby, and during an upgrade from 8.6 to 9.14 via 9.0(4); the recommended path from Cisco, i've noticed something strange in the config for contexts and it's causi...
I have a single 3945 which has 2 x Fibre providers terminating onto it (say Gi0/1 and Gi0/2). There are multiple VLAN's and subnets on the router, one of which is solely dedicated to Gi0/2. Gi0/2 lives in a VRF with its own DHCP/NAT/Crypto maps (and ...
Unusual one that's just recently surfaced.
We are using a certain SIP provider for outbound calls, which up until recently appears to have been working fine.
We have two gateways, which sit directly behind our border routers to the internet. The...
A bit of a curly one.
I have a small network of routers that are all connected back to a single site via a crypto-map and matching subnets in ACL's.
In addition, I have an inbound static TCP NAT rule on the same inbound interface to a host on the i...
Curly one for the experts around here:)I decided recently to switch out our border router (1841 12.4 advsecurity) with a shiny new 1941 (15.2 SEC/K9) as the CPU upgrade was needed.In doing so, I seem to have introduced some strange issues.The core be...
Appreciate it! If you need more info, feel free to drop me a message. As a standalone setup it works great for making it two separate services, but trying to failover one link to another i'm not so sure of.
Thanks George, sorry this took a while as the router has a huge amount of config on it I had to sanitise. Building configuration...
!
hostname router1
!
boot-start-marker
boot-end-marker
!
!
vrf definition GeneralVRF
rd 192.168.10.0:666
!
address...
Thanks Ashok,
I don't have the ability to span anything at this site (no boxes to use for tcpdump/wireshark).
The BYE packets get through if the calls are under 7 or so minutes. The SIP provider is in AWS (if that makes any difference).
There a...
The border routers are not likely to be the culprit as shorter length calls are fine. There is no NAT and it's just passing a routered packet through to a directly connected subnet.
I'm not able to do a full capture on the border routers at pres...
Ahh that looks to have done the trick. Port 499 is now accessible from the outside world via the NAT to internal, and from other networks on the IPSEC mesh also appear to be working (At least telneting from source interfaces on the remote routers). ...
