Switching

Hi all,

 

I 've tested 2 x EX4300 formed as virtual chassis in order to increase the port density but it seems not work, as we all know, one switch will be the master and other will be backup under virtual chassis technology. However, when I plug the cable connect to the backup switch, it can not transit traffic while connecting to master switch is work. Is there any misconfiguration? Or backup switch will not handle any data traffic?

 

 

You have no interfaces configured for the new switch.

 

set interfaces ge-1/0/0 unit 0 family ethernet-switching storm-control default
set interfaces ge-1/0/1 unit 0 family ethernet-switching storm-control default
set interfaces ge-1/0/2 unit 0 family ethernet-switching storm-control default
.
.
.


set protocols rstp interface ge-1/0/0
set protocols rstp interface ge-1/0/1
set protocols rstp interface ge-1/0/2
.
.
.

To expand on what Smicker notes, when you join another switch to the VC the ports on that switch have a new first number (the FPC) changing from:

ge-0/0/0 to ge-1/0/0

And so on for all the ports.

 

There is no configuration added for those ports.  so you must add this as Smicker notes in his examples.

Hi Spuluka,

 

Thanks for your information. I 've followed your recommendation to add the new commands to the virtual chassis. But it still not works. Do you have any suggestions? 

 

Attached detail log for your reference. 

 

Regards,

Dylen

 

 

>show virtual-chassis status
>show virtual-chassis vc-port statistics
>show virtual-chassis vc-path
>show virtual-chassis
>show chassis pic-mode
If the PIC mode setting is not set to virtual-chassis, set the PIC mode to virtual-chassis:
user@switch> request chassis pic-mode virtual-chassis

Maybe need to save config off device and return to factory default, zeroize media and then load saved config.

In addition to the VC status commands that Lyndidon lists, can you also run 

 

show interfaces terse

 

So we can confirm the interfaces are recognized.

And also

show chassis hardware models

 

Finally, when you say it does not work, exactly what test are you running and what are the results?

 Hi Spuluka,

 

Actually, I rebuild the EX2200VC by the steps as below:

1. Split EX2200 Virtual Chassis into two standalone switches and power on them

2. Factory default and zeroized the EX2200 Switches

3. Install the JTAC recommended version(Junos 12.3R12) for each EX2200 switch

4. Shutdown the backup node EX2200 and configure master node EX2200 first by preprovisioned and vc ports

[edit virtual-chassis]

user@switch# set preprovisioned

user@switch# set member 0 serial-number abc123 role routing-engine

user@switch# set member 1 serial-number def456 role routing-engine

user@switch# set no-split-detection

[edit]

user@switch# run request virtual-chassis vc-port set pic-slot 0 port 46

user@switch# run request virtual-chassis vc-port set pic-slot 0 port 47

 

5. Power on the backup switch and configure vc ports of 46 and 47

6. Cable the vc port

7. Virtual Chassis will be establish

 

After I rebuild the VC, I can see all interfaces include master and backup member by show interfaces terse command,

but the backup switch still not forward any data traffic.

 

For my testing, I use 2 PCs one is cabling on master switch and other is cabling on the backup switch then they ping with each other and failed.

 

Do you have any suggestions?

 

Regards,

Dylen

run this command

#set system commit synchronize

#commit full

 

display the results of some >show virtual-chassis ?

>show virtual-chassis status

 

Standard stuff:

 

do you see link light on both interfaces PC's are plugged into?  Does show interface terse show those interfaces are up?  Perform show ethernet-switching table and do you see the PC MAC addresses showing up and associated with proper interface?

 

You could also configure a VLAN with these interfaces in it, add some L3 address to the VLAN, and then see if each PC can ping that IP - which would be IP associated with Master RE.  To check other switch, perform a Master switchover.

Hi rccpgm,

 

Thanks for your reminding. I also tested two PCs connected to master switch then they can ping with each other until they connected to the different member switch, the connection is unreachable. 

 

I agree your point. But as my knowledge, Virtual Chassis is interconnected two or more switches as a single logical switch, so I should be able to ping each other from the two PCs regardless which member switch connected to them physically. Please correct me if my understanding is incorrect.

 

Regards,

Dylen

Yes you are correct. Why are you not posting the resuls of the show commands requested to view the vc status, statistics, path, interface configurations, interface terse output, ethernet-switching table etc.

Agree but I expecting that maybe your 2nd switch could be bad or have some issue besides setup or config.

Yes???

Sent from my iPhone

Hi all, 

 

Finally, I can ping with each other by add the command set interface ge-1/0/0~45 unit 0 family ethernet-switching.

 

But is it normal behavior? I suppose all interfaces should be act as ethernet switching mode under virtual chassis by default, or I need to add ethernet switching on all other member switch manually when I build VC each time? 

You do not have to configure all interfaces for ethernet-switching in order for it work. If the interface in question is required then yes. You do not have to manually configure each interface individualy. In fact there re several different ways you can configure eth-sw

You can use configuration groups to ensure that all interfaces are configured for ethernet switching, you can use interface-range member, interface-range member-range, and various combinations. Please mark your answer as the solution.

As lyndidon stated, you should not have to configure the interfaces as ethernet-switching, this should be default configuration. You did state previousy that you performed:

 

Factory default and zeroized the EX2200 Switches

 

Depending on the exact order you performed these 2 steps, along with a commit of factory default, this "could" be potential reason your switch got into this state.

 

Ethernet-switching should be default setting for all interfaces.