Switching

4600-4300 VC

We are replacing our existing core Switch (Ex 4200) with two EX 4600 and two EX 4300 in one  VC, I have referred   juniper site to find that both the 4600 and 4300 should be same os version , but same need is not mentioned anywhere in the second URL from juniper , Can some one let me know whether  the OS version of both 4600 and 4300 should be same( I am sure that the OS version should be same for same devices, but not sure with Mixed Mode VC).This is very important for me as I need to Complete the Setup in two weeks.

1.http://www.juniper.net/techpubs/en_US/release-independent/junos/topics/reference/specifications/cable-ex4600-virtual-chassis.html

"For Junos OS releases between 13.2X50-D10 and 14.1X53-D25, use the use the EX4300 as a master and backup RE in the Virtual Chassis. For Junos OS Release 14.1X53-D25 and later, the EX4600 is fully supported as the master in a mixed Virtual Chassis of EX4600 and EX4300. Ensure all members of the Virtual Chassis are running the same Junos OS “

Below URL does not mention anything that the OS version should be the same. 

2.https://www.juniper.net/techpubs/en_US/junos14.1/topics/task/configuration/virtual-chassis-ex4600-cli.html

OR  does that mean only  both 4600 needs to be the same ? 

Here is the version of the new device that is planned to be implemented.

1. EX 4600 -  14.1X53-D27.3
2. EX 4600-   14.1X53-D27.3
3. EX 4300-   13.2X51-D26.2
4. EX 4300-   13.2X51-D26.2

root> show version

fpc0:

--------------------------------------------------------------------------

Model: ex4600-40f

Junos: 14.1X53-D27.3

JUNOS Base OS Software Suite [14.1X53-D27.3]

JUNOS Base OS boot [14.1X53-D27.3]

JUNOS Crypto Software Suite [14.1X53-D27.3]

JUNOS Crypto Software Suite [14.1X53-D27.3]

JUNOS Online Documentation [14.1X53-D27.3]

JUNOS Kernel Software Suite [14.1X53-D27.3]

JUNOS Packet Forwarding Engine Support (qfx-ex-x86-32) [14.1X53-D27.3]

JUNOS Routing Software Suite [14.1X53-D27.3]

JUNOS Enterprise Software Suite [14.1X53-D27.3]

JUNOS Web Management Platform Package [14.1X53-D27.3]

JUNOS py-base-i386 [14.1X53-D27.3]

JUNOS Host Software [14.1X53-D27.3]

root> show version

fpc0:

--------------------------------------------------------------------------

Model: ex4300-48t

JUNOS EX  Software Suite [13.2X51-D26.2]

JUNOS FIPS mode utilities [13.2X51-D26.2]

JUNOS Online Documentation [13.2X51-D26.2]

JUNOS EX 4300 Software Suite [13.2X51-D26.2]

JUNOS Web Management [13.2X51-D26.2]

JUNOS py-base-powerpc [13.2X51-D26.2]

{master:0}

Yes within any VC the SW releases must be the same on all switches or else that switch will not be allowed to join the VC.

Even if they didn't have to be the same version (which they do), 14.1X53-D30 is now the JTAC recommended version for both switches.  So unless there is something very specific that requires you 13.2 on the 4300s, why wouldn't you run them all on 14.1X53-D30?

I've found 14.1 to be a significant improvement that has fixed lot of issues on my 4300s that were previously running the 13.2 series.

Hi,

I've configured a cluster of 4600 and 4300. all of them are in the same version 14.1X53-D30.3

{master:0}
root> show virtual-chassis status

Virtual Chassis ID: 16cb.9c39.daaa
Virtual Chassis Mode: Mixed
                                                Mstr           Mixed Route Neighbor List
Member ID  Status   Serial No    Model          prio  Role      Mode  Mode ID  Interface
0 (FPC 0)  Prsnt    TC3715360031 ex4600-40f     255   Master*      Y  VC   1  vcp-255/0/24
                                                                           2  vcp-255/0/25
1 (FPC 1)  Prsnt    PE3715170212 ex4300-48t     255   Linecard     Y  VC   0  vcp-255/1/0
                                                                           2  vcp-255/1/1
2 (FPC 2)  Prsnt    PE3715170178 ex4300-48t     128   Linecard     Y  VC   1  vcp-255/1/0
                                                                           0  vcp-255/1/1

Everything seemed fine until i tried

> show chassis alarms

but i got the result that no alarms were up, which is weird because the alarm leds in the EX4300 are on.

Also when i try to connect to any ethernet interface on EX4300 the link isn't working like i wasn't connecting anything.

Has someone been through that? if so how do i need to check?

Regards.

Giulianna

I too have an error like the below , but my setup is up and running for more than 2 months.

2 alarms currently active
Alarm time Class Description
2015-11-26 19:22:54 IST Minor FPC 1 PEM 0 is not powered
2015-11-26 19:02:54 IST Minor FPC 0 PEM 0 is not powered

I do not have alram on 4300, I have two  4600  + 2 4300 in VC.

eg: 

request virtual-chassis mode mixed reboot

set virtual-chassis preprovisioned
set virtual-chassis member 0 role routing-engine
set virtual-chassis member 0 serial-number x.x.x.x
set virtual-chassis member 1 role routing-engine
set virtual-chassis member 1 serial-number x.x.x.x
set virtual-chassis member 2 role line-card
set virtual-chassis member 2 serial-number x.x.x.x
set virtual-chassis member 3 role line-card
set virtual-chassis member 3 serial-number x.x.x.x

1. On each individual member switch, configure the ports that will be used to interconnect the member switches into VCPs using the following command:
   
user@switch> request virtual-chassis vc-port set pic-slot pic-slot-numberport port-number local

   where pic-slot-number is the PIC slot number.

   For instance, if you wanted to set port 0 on the QSFP+ interface on PIC slot 2 as a VCP:

   
user@switch> request virtual-chassis vc-port set pic-slot 2 port 0 local

   The VCPs automatically bundle into a Link Aggregation Group when two or more interfaces of the same speed are configured into VCPs between the same two member switches. See Understanding EX Series Virtual Chassis Port Link Aggregation.

Have you done a preprovisioned setup , there was a mistake in the  juniper document where they did not add "local "to the configuration which was fixed by Juniper after I reported that to them.I think if you follow that steps of preprovisioned it should work.

https://www.juniper.net/techpubs/en_US/junos14.1/topics/task/configuration/virtual-chassis-ex4600-cli.html

For connection , please refer the below

http://www.juniper.net/techpubs/en_US/release-independent/junos/topics/reference/specifications/cable-ex4600-virtual-chassis.html

sorry , that Iaccidently accepted the solution.

once you connected a device to the interface of 4300, can you login and check whether that interface is added to a vlan or not , also see >show  interface ge- 1/0/x , you will see all the details there . please post it if you still dont see it , secondly the 4600 is ELS and it allows irb instaed of VLan so creating vlan should be as below , also see the spanning tree

sorry , that accidently accepted the solution.

once you connected a device to the interface of 4300, can you login and check whether that interface is added to a vlan or not , also see >show  interface ge- 1/0/x , you will see all the details there . please post it if you still dont see it , secondly the 4600 is ELS and it allows irb instaed of VLan so creating vlan should be as below , also see the spanning tree

Hi,

Thanks for the reply, i let you know that i configured the chassis with a non provisioned configuration.

Also, when i check the interfaces in edit mode i only see the ones from the 4600(Master) but i don't see the ones from the 4300

but i can see the rest of interfaces in cli mode

{master:0}
root> show interfaces terse
Interface               Admin Link Proto    Local                 Remote
vcp-255/0/24            up    up
vcp-255/0/24.32768      up    up
vcp-255/0/25            up    up
vcp-255/0/25.32768      up    up
gr-0/0/0                up    up
pfe-0/0/0               up    up
pfe-0/0/0.16383         up    up   inet
                                   inet6
pfh-0/0/0               up    up
pfh-0/0/0.16383         up    up   inet
ge-1/0/0                up    down
pfe-1/0/0               up    up
pfe-1/0/0.16383         up    up   inet
                                   inet6
pfh-1/0/0               up    up
pfh-1/0/0.16383         up    up   inet
ge-1/0/1                up    down
ge-1/0/2                up    down
ge-1/0/3                up    down
ge-1/0/4                up    down
ge-1/0/5                up    down
ge-1/0/6                up    down
ge-1/0/7                up    down
ge-1/0/8                up    down
ge-1/0/9                up    down
ge-1/0/10               up    down
ge-1/0/11               up    down
ge-1/0/12               up    down
ge-1/0/13               up    down
ge-1/0/14               up    down
ge-1/0/15               up    down
ge-1/0/16               up    down
ge-1/0/17               up    down

I tried adding the interface to a vlan

{master:0}[edit]
root# show vlans
default {
    vlan-id 1;
    l3-interface irb.0;
}

{master:0}[edit]
root# show interfaces irb
unit 0 {
    family inet {
        dhcp {
            vendor-id Juniper-ex4600-40f;
        }
    }
}

{master:0}[edit]
root# set interface ge-1/0/12 unit 0 family ethernet-switching vlan members default

And then connected to interface ge-1/0/12, but it's still the same

root# run show interfaces ge-1/0/12
Physical interface: ge-1/0/12, Enabled, Physical link is Down
  Interface index: 661, SNMP ifIndex: 557
  Link-level type: Ethernet, MTU: 1514, MRU: 0, Speed: Auto, Duplex: Auto,
  BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled,
  Source filtering: Disabled, Flow control: Disabled, Auto-negotiation: Enabled,
  Remote fault: Online, Media type: Fiber,
  IEEE 802.3az Energy Efficient Ethernet: Disabled
  Device flags   : Present Running Down
  Interface flags: Hardware-Down SNMP-Traps Internal: 0x4000
  Link flags     : None
  CoS queues     : 12 supported, 12 maximum usable queues
  Current address: 5c:45:27:a0:7e:6f, Hardware address: 5c:45:27:a0:7e:6f
  Last flapped   : 2016-01-28 01:16:32 UTC (00:12:59 ago)
  Input rate     : 0 bps (0 pps)
  Output rate    : 0 bps (0 pps)
  Active alarms  : LINK
  Active defects : LINK
  Interface transmit statistics: Disabled

  Logical interface ge-1/0/12.0 (Index 555) (SNMP ifIndex 0)
    Flags: Device-Down SNMP-Traps 0x24024000 Encapsulation: Ethernet-Bridge
    Input packets : 0
    Output packets: 0
    Protocol eth-switch, MTU: 1514
      Flags: Is-Primary

Any other suggestion?

please refer and check  , also change to another port 2/0/1 or other

http://forums.juniper.net/t5/Ethernet-Switching/curious-problem-interface-EX4200-down/td-p/93880

set up an ip for the vlan and check, 

http://kb.juniper.net/InfoCenter/index?page=content&id=KB26486&actp=search

Thanks for the help, i kinda know why the interfaces don't work.

It's because the VC is not supported using just one EX4600 and all the other members EX4300

In case of failure of the master (ex4600) only the same model can take the role of master.

So that means i need to get another ex4600 😞

Anyways i just created a vc between the two 4300 and put the 4600 connected to an ex port.

if you want to know more go to http://www.juniper.net/techpubs/en_US/release-independent/junos/topics/reference/specifications/cable-ex4600-virtual-chassis.html

note: i did tried to configure the chassis with version 14.1X53-D16 it only supports one switch of each model. when i added the other 4300 the whole chassis becomes a non mixed one, so only the two 4300 are recognized in it.

Giulianna

Good to hear that , would help any one trying the same, I never noticed it , since I had two 4600 + two 4300.

Binoy

Hello,

Have you found any solution of this issue.

Actualy we are also facing the same issue in our network.

Can you suggest us any Solution you found without buying any other Juniper parts.

Abhinav