Re: [j-nsp] virtual-chassis and interfaces
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:da...@appliedi.net] 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:bblackf...@nwresd.k12.or.us] 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: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] 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:da...@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 ___ 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
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. Dan Farrell Sent from my iPhone On Aug 6, 2010, at 4:45 PM, Stefan Fouant sfou...@shortestpathfirst.net wrote: -Original Message- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp- boun...@puck.nether.net] On Behalf Of snort bsd Sent: Friday, August 06, 2010 3:01 PM To: juniper-nsp Subject: [j-nsp] virtual-chassis and interfaces Hi all: With virtual-chassis, after I login, I only see interfaces (under stanza interfaces) on master, not those interfaces on the back up mode or line card mode. How could I configure those interfaces that are not on master? do I have to login each physical switch in order to configure those interfaces? They might not necessarily show up in the configuration until you actually define them... it depends on how they were brought into the virtual- chassis. However if your Virtual-Chassis is set up correctly, they should still show up when you do a 'show interfaces terse'. The FPC portion of the interface naming convention is what is used to identify the interfaces on a given virtual-chassis member. In other words, interfaces on member-id 2 will show up in 'show interfaces terse' as ge-2/x/x or xe-2/x/x. You can verify that your virtual-chassis is working correctly by doing a 'show virtual-chassis status', or even a 'show chassis hardware' will give you a clue as to whether or not all the members are shown in the virtual-chassis. HTHs. Stefan Fouant, CISSP, JNCIEx2 www.shortestpathfirst.net GPG Key ID: 0xB5E3803D ___ 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
Re: [j-nsp] virtual-chassis and interfaces
-Original Message- From: Dan Farrell [mailto:da...@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 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
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: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] 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:da...@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 ___ 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
Re: [j-nsp] virtual-chassis and interfaces
On Sat, Aug 07, 2010 at 06:46:03AM -0700, Bill Blackford wrote: 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. Yay. I was getting sick of having to deal with 9.2: For each unit: 1. Do not install, or remove an already installed EX-UM-2X4SFP uplink module (not supported on 9.2 and hangs interface-control daemon--no me0 or vme interface works in this condition). 2. Power on, assign vme address, root-auth, ssh. 3. Copy code and upgrade switch. 4. (re-)install EX-UM-2X4SFP. 5. Only after this attempt to stack the units into a VC. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] virtual-chassis and interfaces
Hi all: With virtual-chassis, after I login, I only see interfaces (under stanza interfaces) on master, not those interfaces on the back up mode or line card mode. How could I configure those interfaces that are not on master? do I have to login each physical switch in order to configure those interfaces? ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] virtual-chassis and interfaces
Hi, Just configure them. Just remember about naming convention. Regards, Piotr Bratkowski W dniu 2010-08-06 21:00, snort bsd pisze: Hi all: With virtual-chassis, after I login, I only see interfaces (under stanza interfaces) on master, not those interfaces on the back up mode or line card mode. How could I configure those interfaces that are not on master? do I have to login each physical switch in order to configure those interfaces? ___ 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
Re: [j-nsp] virtual-chassis and interfaces
just configure them? under interface stanze of each member of the virtual-chassis? --- On Sat, 7/8/10, Piotr Bratkowski pioterb...@o2.pl wrote: From: Piotr Bratkowski pioterb...@o2.pl Subject: Re: [j-nsp] virtual-chassis and interfaces To: juniper-nsp@puck.nether.net Received: Saturday, 7 August, 2010, 5:23 AM Hi, Just configure them. Just remember about naming convention. Regards, Piotr Bratkowski W dniu 2010-08-06 21:00, snort bsd pisze: Hi all: With virtual-chassis, after I login, I only see interfaces (under stanza interfaces) on master, not those interfaces on the back up mode or line card mode. How could I configure those interfaces that are not on master? do I have to login each physical switch in order to configure those interfaces? ___ 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 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] virtual-chassis and interfaces
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Login to the master, edit - edit interfaces and then ge-0/0/0 for ge-0/0/0 on master ge-1/0/0 for second member and so on ( or it could be ge-0/1/0 for the second member I don't remeber the convention) Regards, Piotr Bratkowski W dniu 2010-08-06 22:13, snort bsd pisze: just configure them? under interface stanze of each member of the virtual-chassis? --- On Sat, 7/8/10, Piotr Bratkowski pioterb...@o2.pl wrote: From: Piotr Bratkowski pioterb...@o2.pl Subject: Re: [j-nsp] virtual-chassis and interfaces To: juniper-nsp@puck.nether.net Received: Saturday, 7 August, 2010, 5:23 AM Hi, Just configure them. Just remember about naming convention. Regards, Piotr Bratkowski W dniu 2010-08-06 21:00, snort bsd pisze: Hi all: With virtual-chassis, after I login, I only see interfaces (under stanza interfaces) on master, not those interfaces on the back up mode or line card mode. How could I configure those interfaces that are not on master? do I have to login each physical switch in order to configure those interfaces? ___ 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 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJMXHDFAAoJEFmGJVrtk3rVrFEH/iiHqXdgnXO5eCqUyJv2wdP7 ioTM7FjPyN+5W4pqV+9VmHZd1joGmdaofGBJFhs6jsYwruaQC/umiVMM+rLSOJ1r yAT1J7CBYDDCVNqQ7yAo1tQRiwS9TwtxA9L2srseLyu5lZb1DDVBEDGuyDo/tmJf 5Aups2h0kZtsemOvGpmiInUw+/HWmkJOP1uuUUK0AW8fvbh7lT7DccVnhJtD6nHd ZjZD2BmHyScLjpf+oIPIcn6ODEKvA02/JRC1aO4gmTAS0KjBf5E0j2gQTRkuuTno xpvZkX4DFqj6P2Ke1waebTZdM2+ZucZBfWDOeC8UzSm5X2NCN9K1S2P6e2HXDqU= =mTDs -END PGP SIGNATURE- ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] virtual-chassis and interfaces
-Original Message- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp- boun...@puck.nether.net] On Behalf Of snort bsd Sent: Friday, August 06, 2010 3:01 PM To: juniper-nsp Subject: [j-nsp] virtual-chassis and interfaces Hi all: With virtual-chassis, after I login, I only see interfaces (under stanza interfaces) on master, not those interfaces on the back up mode or line card mode. How could I configure those interfaces that are not on master? do I have to login each physical switch in order to configure those interfaces? They might not necessarily show up in the configuration until you actually define them... it depends on how they were brought into the virtual-chassis. However if your Virtual-Chassis is set up correctly, they should still show up when you do a 'show interfaces terse'. The FPC portion of the interface naming convention is what is used to identify the interfaces on a given virtual-chassis member. In other words, interfaces on member-id 2 will show up in 'show interfaces terse' as ge-2/x/x or xe-2/x/x. You can verify that your virtual-chassis is working correctly by doing a 'show virtual-chassis status', or even a 'show chassis hardware' will give you a clue as to whether or not all the members are shown in the virtual-chassis. HTHs. Stefan Fouant, CISSP, JNCIEx2 www.shortestpathfirst.net GPG Key ID: 0xB5E3803D ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
