Hi Team,

I have a core switch 4600 and a EX 2200 Connected to it as trunk, I am running vstp and core is set to bridge pririty of 4k,

the ex switch prioruty was set to 16 K, but Still I see EX 2200 spanning tree as the root bridge , not the core switch ? I was thinking that the EX should be having the roodbidge of Core.

* Note there is only one trunk connected between EX 4600 and EX 2200. 

* I have only shown a vlan due to space limitation

ON EX 2200

=====================

set protocols rstp disable

set protocols vstp vlan all bridge-priority 16k

root@sw-11> show spanning-tree bridge 

STP bridge parameters for VLAN 56

  Root ID                           : 16440.44:f4:77:69:5b:01

  Hello time                        : 2 seconds

  Maximum age                       : 20 seconds

  Forward delay                     : 15 seconds

  Message age                       : 0 

  Number of topology changes        : 0

  Local parameters 

    Bridge ID                       : 16440.44:f4:77:69:5b:01

    Extended system ID              : 1

    Internal instance ID            : 0

ON EX 4600 (Core)

=============================

set protocols vstp vlan 56 bridge-priority 4k

STP bridge parameters for VLAN 60

  Root ID                           : 4156.54:4b:8c:b6:5d:e2

  Hello time                        : 2 seconds

  Maximum age                       : 20 seconds

  Forward delay                     : 15 seconds

  Message age                       : 0 

  Number of topology changes        : 18

  Time since last topology change   : 914034 seconds

  Local parameters 

    Bridge ID                       : 4156.54:4b:8c:b6:5d:e2

    Extended system ID              : 60

http://www.juniper.net/techpubs/en_US/junos15.1/topics/example/vstp_on_qfx_example.html

And one more thing:

Note: When configuring xSTP on EX4300 and EX4600 switches, you must add all the interfaces in the applied VLANs in configurations. For MSTP, configure all interfaces in all VLANs at the [edit protocols mstp interface] hierarchy level.

 I am the CTO for Independent Technology Group (ITG) a Los Angeles, California based Juniper Networks Elite reseller partner. We are expanding and looking to hire a mid to senior level engineer with solid Junos experience.

The focus of the job would be on conducting post sales professional services for our customers. Some pre-sales work, done in conjunction with our TAM’s (Territory Account Managers) is also part of the job description.

If you are interested in learning more about ITG and the opportunity to work with a high energy company with an expanding practice please reach out to me via private message and I will provide you with my complete contact information.

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

We spoke to our Juniper SE team and they were surprised to hear that it's unsupported on the EX4600 platform. Interestingly, I also tested this on a QFX5100 with the same results. I guess that makes sense because the QFX5100 and EX4600 are pretty much the same device.

On another note, we ended up accomplishing our goals with some static/host routes. Not exactly elegant, but it works.

Yes there is a limit to routing instance types for both EX4600 and QFX5100.  I believe it is a hardware chip limitation.

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?

Dear,

There are some error messages on EX-3200 Switch like below log messages,

And other EX-3200 switches have same error messages.

Do  you know what this error messages mean by ? This error is critical ?

Please, check this meaasges and attached  document.

Let me know your opinion on this error.

Thank you in advance.

ForceTEC_ID@EX3200_Site> show log messages | match error | no-more
Jun 10 20:07:22  EX3200_Site : %PFE-3: master rule valid status get failed on device 0 during ipsg rule get- Error 0
Jun 10 20:07:22  EX3200_Site : %PFE-3: master rule valid status get failed on device 1 during ipsg rule get- Error 4
Jun 10 20:07:22  EX3200_Site : %PFE-3: master rule valid status get failed on device 2 during ipsg rule get- Error 4
Jun 22 11:31:30  EX3200_Site : %PFE-3: master rule valid status get failed on device 0 during ipsg rule get- Error 0

ForceTEC_ID@EX3200_Site> show log messages | no-more
Jun 10 20:00:00 EX3200_Site newsyslog[1318]: logfile turned over due to size>128K
Jun 10 20:00:01  EX3200_Site eventd: %SYSLOG-3: sendto: No route to host
Jun 10 20:00:01  EX3200_Site /kernel: %KERN-5-KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd ge-0/0/0 - ATTACHED state - acting as standby link
Jun 10 20:00:01  EX3200_Site /kernel: %KERN-5-KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd ge-0/0/0 - CD state - ready to carry traffic
Jun 10 20:00:00  EX3200_Site chassisd[1274]: %DAEMON-5-CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Ok (jnxFruContentsIndex 4, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FAN: FAN @ 0/*/*, jnxFruType 13, jnxFruSlot 0)
Jun 10 20:00:00  EX3200_Site chassisd[1274]: %DAEMON-5-CHASSISD_SNMP_TRAP7: SNMP trap generated: FRU insertion (jnxFruContentsIndex 4, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FAN: FAN @ 0/*/*, jnxFruType 13, jnxFruSlot 0)
Jun 10 20:00:00  EX3200_Site chassisd[1274]: %DAEMON-5: unknown trap request type 6
Jun 10 20:00:01  EX3200_Site snmpd[1280]: %DAEMON-5-LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 60 bytes, actually sent 48 bytes
Jun 10 20:00:01  EX3200_Site snmpd[1280]: %DAEMON-5-LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 12 bytes
Jun 10 20:00:02  EX3200_Site /kernel: %KERN-5-KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd ge-0/0/1 - ATTACHED state - acting as standby link
Jun 10 20:00:03  EX3200_Site /kernel: %KERN-5-KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd ge-0/0/1 - CD state - ready to carry traffic
Jun 10 20:00:11  EX3200_Site eswd[1272]: %DAEMON-1: Root bridge in  context 0 changed from 32768:00:26:88:77:61:01 to 4096:80:71:1f:4b:86:00
Jun 10 20:00:17  EX3200_Site ppmd[1287]: %DAEMON-3: ppmd_delete_cfm_pending_entries: CFMD delete pending timer expired
Jun 10 20:00:17  EX3200_Site ppmd[1287]: %DAEMON-3: ppmd_delete_cfm_pending_entries: connection received 0x1ad7000
Jun 10 20:00:46  EX3200_Site /kernel: %KERN-3: init_panel: craft panel init
Jun 10 20:03:03  EX3200_Site xntpd[1279]: %NTP-5: time reset +118.829715 s
Jun 10 20:03:09  EX3200_Site xntpd: %NTP-3: NTP Server Unreachable
Jun 10 20:03:19  EX3200_Site last message repeated 5 times
Jun 10 20:04:39  EX3200_Site login: %AUTH-5: Login attempt for user swolf91 from host 130.1.37.142
Jun 10 20:04:41  EX3200_Site login[1324]: %AUTH-6-LOGIN_INFORMATION: User swolf91 logged in from host 130.1.37.142 on device ttyp0
Jun 10 20:05:09  EX3200_Site mgd[1326]: %INTERACT-5-UI_DBASE_LOGIN_EVENT: User 'swolf91' entering configuration mode
Jun 10 20:05:24  EX3200_Site login: %AUTH-5: Login attempt for user ForceTEC_ID from host 130.1.37.219
Jun 10 20:05:25  EX3200_Site chassism[1259]: %DAEMON-3: auth PASS
Jun 10 20:05:25  EX3200_Site chassism[1259]: %DAEMON-3: mainboard authentication result: SEC_AUTH_PASS
Jun 10 20:05:28  EX3200_Site login[1334]: %AUTH-6-LOGIN_INFORMATION: User ForceTEC_ID logged in from host 130.1.37.219 on device ttyp1
Jun 10 20:05:42  EX3200_Site mgd[1336]: %INTERACT-5-UI_DBASE_LOGIN_EVENT: User 'ForceTEC_ID' entering configuration mode
Jun 10 20:05:44  EX3200_Site mgd[1336]: %INTERACT-5-UI_COMMIT: User 'ForceTEC_ID' requested 'commit' operation (comment: none)
Jun 10 20:05:58  EX3200_Site mgd[1326]: %INTERACT-5-UI_COMMIT: User 'swolf91' requested 'commit' operation (comment: none)
Jun 10 20:06:09  EX3200_Site mgd[1336]: %INTERACT-5-UI_DBASE_LOGOUT_EVENT: User 'ForceTEC_ID' exiting configuration mode
Jun 10 20:06:56  EX3200_Site /kernel: %KERN-4: Percentage memory available(18)less than threshold(20 %)- 1
Jun 10 20:07:22  EX3200_Site : %PFE-3: master rule valid status get failed on device 0 during ipsg rule get- Error 0
Jun 10 20:07:22  EX3200_Site : %PFE-3: master rule valid status get failed on device 1 during ipsg rule get- Error 4
Jun 10 20:07:22  EX3200_Site : %PFE-3: master rule valid status get failed on device 2 during ipsg rule get- Error 4
Jun 10 20:07:25  EX3200_Site mgd[1326]: %INTERACT-5-UI_DBASE_LOGOUT_EVENT: User 'swolf91' exiting configuration mode

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

Hi !

There is a new bug in the above mentioned version which took us 2-3 hours to find:

Preface: since recent when you define "set chassis aggegated-interfaces Ethernet device-count 23"you are not longer bound to ae0 up o ae22 but you can freely chose your interface number as long as the amount of AEs is below the stated number and commit only gives  an error if the amount of aes is higher than the device-count.

At least this is only partly true as:

Our customer wanted to set the ae-numbers equal to the main VLAN numbers so he created ae1337 and attached 2 physical interfaces to that ae.The ae1337 came up, LACP worked as planned, but only LLDP packets from the switch could be seen on the attached server.

We first blamed the server, the bonding, the server interfaces, the SFPs....

BUT

After 2-3 hours of testing every possible and impossible cause we found out, that for ae numbers > around 500 the forwarding of packets from the physical interface unit  to the ae unit does not work.

The only visible indication is that the counters on the ge-x/y/z.0 interfaces of the ae are incrementing whereas  the ae1337.0 counters stay at 0, but the ae1337 physical interface counters show packets in and out.

Changing the ae number to a number below around 500 everything works fine again

Commit or any log does not state any error.

So my result:s

1. it is a bug, as you can specify interface numbers > 500 but  they are not working

2. the control mechanism at commit does not detect it

3. it is very very complicated to find

therefore

4. do not use ae numbers higher than around 500

5. hopefully someone@juniper will forward this to engineering

regards

Alexander

Hello

What is the BTU air contioner requirement for the EX switches series?

Thank you,

Nils.

For any BTU calculation just use max W per switch (it is not x2 with redundant supplies unless both are active) multiple that by 3.14 (watts to BTU conversion) and you have max BTU required.  You now have a max number needed - go from there.

Was Juniper TAC involved with any of this, like was there a Juniper Case opened?  Do you have Juniper Support contract for your switches?

NO, as I am an external consultant on a project and currently the customer is in the installation phase of a new DC and thus has no time for that.

And for us the problem is solved by using only lower range AE numbers.

regards

alexander

Hi,

I am looking to interconnect 3 EX3300 switches in Virtual-Chassis setup. One of the switches will be configured as master with prioroty 255 and the other 2 will be LCC with priority 0. My question is what will happen to the LCC switches if they lose all the links to the master (highly unlikely, I know). Will they remain in LCC state or will elect another master between themselves?

Also, the VC will be connected with an AE interface consisting of 3 10GE ports to another switch - each of the 3 ports will be on different member of the VC. If the LCC switches lose the communcations to the master switch am I right to asume that the remote switch will remove the 2 links connected to the LCC switches from the bundle but will keep the one connected to the master, thus the AE interface will remain up with only 1 member in? The reason I am thinking that this would happen is that the LACP will sense that the 2 interfaces to the LCC switches are now connected to different entity and will be taken out of the bundle.

Thank you,

D

Hi,

You should allow one of the other switches to perform the RE function in the event the active RE fails. If you use mastership priority of 0 the LC roles will never assume the RE role. If the active RE fails and there is no backup RE traffic forwarding will be impacted. 

See this link

With regards to the ae bundle, I believe that the RE would believe that it has split from the virtual chassis and also stop forwarding traffic. If you have a backup RE there would be an alternate path and traffic would be forwarded.

Tim