Hmm, I haven't seen any issues going directly from 9.2R3.5 straight to 10.0S1.1, but everyone's mileage may vary.
-b -----Original Message----- From: Dan Farrell [mailto:[email protected]] Sent: Monday, August 09, 2010 1:20 PM To: Bill Blackford; 'Stefan Fouant' Cc: 'juniper-nsp' Subject: RE: [j-nsp] virtual-chassis and interfaces That difference in JUNOS is HUGE!!! I had 9.2 or something on an EX3200 that I just fubar'd because I forgot the warnings and attempted to upgrade directly to 10.0S.1 . Oh boy. If you receive 9x loaded switches shipped from Juniper/your vendor, upgrade to 10x before doing anything else. Dan -----Original Message----- From: Bill Blackford [mailto:[email protected]] Sent: Saturday, August 07, 2010 9:46 AM To: 'Stefan Fouant'; Dan Farrell Cc: 'juniper-nsp' Subject: RE: [j-nsp] virtual-chassis and interfaces I just received a pair, individually set the root-auth and sys login info, then attached VCP cables, powered back up and as stated had to create the config. Interfaces on the second FPC. As a side note: I also noticed that these shipped with 10.1R1.8. Just three months ago, another set shipped with 9.2 something. -b -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stefan Fouant Sent: Saturday, August 07, 2010 6:01 AM To: 'Dan Farrell' Cc: 'juniper-nsp' Subject: Re: [j-nsp] virtual-chassis and interfaces > -----Original Message----- > From: Dan Farrell [mailto:[email protected]] > 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 _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
