hi
Interesting problem, that has got me a running around the houses.
So we have 2 setups, mx960 running 2x re-2000 and mx960 running 2x re-1800-s - as a note we are using a routing-instance, but this is setup on both configurations
Following is for the mx960 running re-2000. snmp is ran to poll both the routing engines - this works as expected.
mx960 running re-1800-s. snmp is ran to poll both the routing engines, but we are only able to poll the active routing-engine. the backup does not want to work. if we failover, the new backup RE becomes unresponsive. dug a little deaper, and the routing on the backup re-1800-s looks perfect, arp entries are up showing the local IP range. from the backup RE I am able to ping anything that is directly connected on the same network. as soon as I attempt to ping an address that is a bgp neighbour on a seperate network, the ping's begin to fail - this IP is reachable from the active RE.
"show route" is the exact same as the active as well. looked at our working pair, and the only changes I can see is the following, but I dont see why these would affect routing:
set system no-multicast-echo
set system no-redirects
set system no-redirects-ipv6
The way we have setup the routing-engine IP's are as follows:
set groups re0 interfaces fxp0 unit 0 family inet address 1.1.1.1/25
set groups re1 interfaces fxp0 unit 0 family inet address 1.1.1.2/25
Looking for generic routing issues that would effect backup RE from being able to communicate with the active routing-table. Any assistance would be great. Thanks CG