[j-nsp] virtual-chassis and interfaces

[Stefan Fouant]

> -----Original Message-----
> From: Dan Farrell [mailto:danno at appliedi.net]
> Sent: Saturday, August 07, 2010 7:20 AM
> To: Stefan Fouant
> Cc: snort bsd; juniper-nsp
> Subject: Re: [j-nsp] virtual-chassis and interfaces
> 
> I see the same thing on fresh configs - once I define something on one
> of those interfaces, it shows up.

What I've seen in my experience is that if you create a virtual-chassis from
a factory default configuration, i.e. take them out of the box, stack them,
connect the VCP cables, and then power them up one by one in the desired
order of member-id - everything will work perfectly and the configurations
should have all interfaces defined.  

If there is some other configuration other than factory-default, well then,
it seems the act of connecting it to the virtual-chassis has the tendency to
blow away any of the respective interfaces in the configuration referencing
the new member-id whose interfaces are being brought into the configuration.
As I mentioned previously, this is just for the configurations - the
interfaces are still in fact active and will show up with a 'show interfaces
terse'.

What I will usually do if I've already got interfaces and such configured on
a standalone device and I want to bring that into a virtual-chassis, as a
precautionary measure I will save the configuration into a text file.  This
way if the interfaces are blown away I can simply edit the text file, do a
simple find and replace function to reset the FPC portion of the respective
interfaces to the proper member-id, and then do a 'load merge' operation.

Stefan Fouant, CISSP, JNCIEx2
www.shortestpathfirst.net
GPG Key ID: 0xB5E3803D