Cisco Bug: CSCsg35358 - No OSPF adjacency when WS-SVC-IPSEC-1 is first installed
Jan 28, 2017
- Cisco IOS
Known Affected Releases
Symptom: When WS-SVC-IPSEC-1 is install into router and router is reconfigured to use the module, OSPF does not come up. A reload of router is required. Conditions: Two 7606 route connected via a T3. IPsec VPN encryption is configured on the logical interface vlan100 which the T3 serial interface (s1/0/0) is binded to. On router_a, following was configured:- int vlan100 shut int s1/0/0 no crypto connect vlan 100 ip address 10.192.2.2 255.255.255.252 and OSPF adjacency came up fine. Customer did this to replace their faulty WS-SVC-IPSEC-1 module. When new WS-SVC-IPSEC-1 was put back into router_a, customer configure this:- int s1/0/0 no ip address 10.192.2.2 255.255.255.252 crypto connect vlan 100 int vlan100 no shut and OSPF adjacency could not come up. clear ip ospf proc had not affect. router_a had to be reloaded for OSPF adjacency to come up.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases