You could also configure re0 and re1 with different host names by adding -re0 or -re1 to the hostname in the groups re0 and re1 respectively. This will give a visual confirmation when someone logs into the RE with master-only address.
Thanks, Nilesh. Sent from my iPhone > On Nov 24, 2015, at 2:41 PM, Chris Kawchuk <juniperd...@gmail.com> wrote: > > Relevant config snippet/stanzas: > > ## Last commit: 2015-11-24 16:03:02 EST by me > version 13.3R6.5; > groups { > re0 { > interfaces { > fxp0 { > unit 0 { > family inet { > address 172.xx.xx.1/24 { > master-only; > } > address 172.xx.xx.2/24; > } > } > } > } > } > re1 { > interfaces { > fxp0 { > unit 0 { > family inet { > address 172.xx.xx.1/24 { > master-only; > } > address 172.xx.xx.3/24; > } > } > } > } > } > } > apply-groups [ re0 re1 ]; > ... > ... > ... > > note the 'master-only" directive. You then SNMP/SSH/etc... to the proverbial > '.1' address, which always goes to the master RE; whichever one is active. > > Hope that helps.! > > - Ck. > > > > >> On 25/11/2015, at 5:07 AM, Mike Williams <mike.willi...@comodo.com> wrote: >> >> Hi all, >> >> So we just got our first Juniper devices with dual-REs (if you exclude >> virtual >> chassis'). >> Before I get into actually configuring them, I'm wondering how others handle >> management, as I'm a touch confused. >> >> Normally we just SSH/snmp to the loopback address, optionally jumping off >> from >> a device on the same OoB network if routing is down (yes, we should >> configure >> a backup router). >> >> Juniper document providing each RE with it's own loopback address. >> If you do that, you'd have to detect if what you're connected to is master >> or >> backup, right? > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp