I have a pair of 4400s setup specifically for SIP voice services. In our config we have an 'outside' public IP connecting to the carrier voice cloud, and a 'inside' IP connecting to my private IP network.
interface GigabitEthernet0/0/0 description PDC1-PDCL10-ASW1 G1/0/4 ip address 172.18.91.41 255.255.255.0 media-type rj45 negotiation auto redundancy rii 1 redundancy group 1 ip 172.18.91.40 exclusive ip virtual-reassembly ! interface GigabitEthernet0/0/1 description pdc1-pdcp10-isw1 G1/0/25 ip address 22.214.171.124 255.255.255.224 media-type rj45 negotiation auto redundancy rii 2 redundancy group 1 ip 126.96.36.199 exclusive ip virtual-reassembly !
On the standby router we set the same 'interface' commands but used the next IP (i.e. G0- 172.18.91.42 and G1- 188.8.131.52).
Gig 0/0/2 is simply a crossover cable between the two routers.
On to the problem:
For a test we disconnected the cable between Router 1 and G0/0/0 the interface went down/down as expected. Alll the redundancy rolled over to the Router 2 as it became 'active'.
However when Router1 lost interface G0/0/0 it reloaded with: System returned to ROM by RG-application reload on voice-b2bha RG at 16:08:47
We then reconnected the cable from Router1 G0/0/0. it rediscovered the HA and became Active. This then caused Router2 to reload with the same error.
In a call with TAC this behavior was 'normal' and suppose to be there to help prevent any split brain (loop, active interfaces, routes, etc) problems. It just seems very excessive to reload a router rather than employ some sort of standby process.
The sloppy drawing shows the interface we 'disconnected' for this test. Once that was done the Router 2 became Active and Router 1 reloaded.
Anybody else use this "Redundancy" service command? Can you point me to a better document or am i using this correctly?
This post is more of a discussion than troubleshooting BTW.
Inviting all network professionals in operations! We'd like to understand what would be valuable for you in a mobile application. Your response will help Cisco improve a product feature that could benefit you. Thanks!
Click here to take the sur...
Cisco’s software-defined wide area network (SD-WAN) solution allows user to quickly and seamlessly establish an overlay fabric to connect an enterprise’s data centers, branch and campus locations, as well as colocation facilities in order to imp...
1. Log into CLI of DNAC:
ssh maglev@< DNAC appliance IP> -p 2222
2. Run this curl command to get token to get member id:
curl -X POST -u admin:<admin user password> -H -V https://<CLUSTER-IP>/api/system/v1/identitymgmt/token
Enterprise Switching Business Unit is glad to announce Beta release 16.12.2 for all Catalyst 9200/9300/9400/9500/9600 and Catalyst 3650/3850 Platforms. This release is made available to allow users to test, evaluate and share fee...
Purpose of the document
This document describes the general recommendations or best practices when designing and deploying the Cisco SD-Access technology. The document assumes that the reader has a general overview of Cisco's SD-Access for Distributed C...