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

 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.

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

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.

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,

there is an issue I observe on a Juniper virtual-chassis made of a pair of EX 4550 switches running by Junos 12.3R11.2.

The environment looks like this:

Windows dhcp-client connected to the virtual-chassis, to the particular routing instance where we have enabled DHCP-relay agent, DHCP snooping, dynamic ARP inspection (DAI) and IP source guard (IPSG).

During the DHCP lease process the dhcp-client requests IP address and switch writes the lease information down to dhcp-snooping table, which then being used for DAI and IPSG. Halfway through the lease period, the DHCP client requests a lease renewal, and the DHCP server extends the lease. The problem I have faced with is that during the renewal procces switch doen't not updates the lease timer in it's dhcp-snooping table. Consequently, after lease timer expires on the switch, DAI starts to drop a traffic generated by the host.

Does anybody had something similar and know how to fix this?

Hi everyone! It's my first time configuring Juniper devices and I would like to ask some help if you may.

Scenario: We have SRX240 HA Cluster connected 2 EX4300 in virtual chassis. I attached the topology.

Issue: When the member1 switch is the Master, I can ping from router to switch, router to server, and vice-versa so basically no problem at all. But when member0 switch becomes the Master, I cannot ping from router to switch, router to server, or vice versa. There is also RTO when member0 is down.

Here is the virtual chassis status:

root@EX-4300# run show virtual-chassis

Virtual Chassis ID: c14c.9326.a5d7
Virtual Chassis Mode: Enabled
                                                Mstr           Mixed Route Neighbor List
Member ID  Status   Serial No    Model          prio  Role      Mode  Mode ID  Interface
0 (FPC 0)  Prsnt    PE3715020154 ex4300-48t     255   Backup       N  VC   1  vcp-255/1/3
1 (FPC 1)  Prsnt    PE3713320098 ex4300-48t     255   Master*      N  VC   0  vcp-255/1/0

Member ID for next new member: 2 (FPC 2)

root@EX-4300# run show virtual-chassis vc-port
fpc0:
--------------------------------------------------------------------------
Interface   Type              Trunk  Status       Speed        Neighbor
or                             ID                 (mbps)       ID  Interface
PIC / Port
1/3         Configured         -1    Up           40000        1   vcp-255/1/0

fpc1:
--------------------------------------------------------------------------
Interface   Type              Trunk  Status       Speed        Neighbor
or                             ID                 (mbps)       ID  Interface
PIC / Port
1/0         Configured         -1    Up           40000        0   vcp-255/1/3

Here are the interfaces between SRX and EX:

SRX-A ge-0/0/14 ---> EX1 ge-0/0/46

SRX-A ge-0/0/15 ---> EX2 ge-1/0/46

SRX-B ge-5/0/14 ---> EX1 ge-0/0/47

SRX-B ge-5/0/15 ---> EX1 ge-1/0/47

EX1 ge-0/0/10 ---> Server

EX2 ge-1/0/10 ---> Server

ISP ---> SRX-A ge-0/0/7

root@EX-4300# run show interfaces terse | match ae*
Interface               Admin Link Proto    Local                 Remote
ge-0/0/10.0             up    up   aenet    --> ae3.0
ge-0/0/46.0             up    up   aenet    --> ae0.0
ge-0/0/47.0             up    up   aenet    --> ae0.0
ge-1/0/10.0             up    up   aenet    --> ae3.0
ge-1/0/46.0             up    up   aenet    --> ae1.0
ge-1/0/47.0             up    up   aenet    --> ae1.0
ae0                     up    up
ae0.0                   up    up   eth-switch
ae1                     up    up
ae1.0                   up    up   eth-switch
ae3                     up    up
ae3.0                   up    up   eth-switch

root@SRX-B> show interfaces terse | match reth*
ge-0/0/7.0              up    up   aenet    --> reth2.0
ge-0/0/14.0             up    up   aenet    --> reth0.0
ge-0/0/15.0             up    up   aenet    --> reth1.0
ge-5/0/7.0              up    down aenet    --> reth2.0
ge-5/0/14.0             up    up   aenet    --> reth0.0
ge-5/0/15.0             up    up   aenet    --> reth1.0
reth0                   up    up
reth0.0                 up    up   inet     10.10.0.1/24
reth1                   up    up
reth1.0                 up    up   inet     10.10.0.2/24
reth2                   up    up
reth2.0                 up    up   inet     210.4.118.114/29

If you guys have any idea what could possibly be wrong or has suggestions, I would be happy to try them out.

U-Boot 1.1.6 (Mar 28 2011 - 04:05:40)

Board: EX4200-24T 4.17
EPLD: Version 10.0 (0x80)
DRAM: Initializing (1024 MB)
FLASH: 8 MB

Firmware Version: --- 01.00.00 ---
USB: EHCI host controller not found
Error, couldn't init Lowlevel part

Unable to execute the POST test pci
POST: pci FAILED

Hi,

Just need some clarity on the ex2200-C POE switch.Currently i have a few access points (4) connected to it. There is also a outdoor access point that need to be powered but it requires more power than than the indoor ones. According to datasheet all ports can provide a max of 30W depeneding on what is configured where.So the interface in question is ge-0/0/1. It seems like the endpoint AP only draws 9.8W and goes into a bootup loop, not sure if it due to not enough power being provided to the AP etc. Can anyone shared their expereice on this.Perhaps some specific configuration.

root@as-4> show configuration poe
management class;
interface all;

root@as-4> show poe interface    
Interface    Admin       Oper    Max        Priority       Power          Class
             status      status  power                     consumption    
 ge-0/0/0    Enabled      ON     30.0W      Low            10.0W           4
 ge-0/0/1    Enabled      ON     25.0W(L)   Low            9.8W            4

Hello,

Is it possible to use VxLAN to "transport" QinQ ? Or vlan in vxlan ? 

Thks

We are facing the following issue:

With an ex2200 device we set a port as a trunk one with a tagged VLAN

The we add an untagged VLAN and we set in the native VLAN value the untagged one

If we connect for example a laptop with windows operating System everything is OK and we reach bot VLAN's

If we connect a linux OS based device, server or latop we can't reach neither the tagged VLAN nor the untagged one

Is there any known issue with this kind of configuration or with this configuration with  linux devices ?

If we set the switch port as access with the untagged VLAN works fine with  linux devices

Thanks in advance for your support

Best Regards

We had a very strange issue today with the arp, in this EX4200.

One of our servers was very unresponsive, even though the IP and mac showed up in the arp table,

We had drops on pings.

Once I cleared the arp, the response came back to normal.

How often does the arp need to be cleaned.?

What is causing this in the configuration of my EX4200 layer 2 switch? It is connected to a stack of EX4500 switch which act as the core of my network and provide layer 2 and 3

protocols {

    igmp-snooping {

        vlan all;

    }

    ##

    ## Warning: configuration block ignored: unsupported platform (ex4200-48px)

    ##

    dcbx {

        interface all;

    }

    rstp;

    lldp {

        interface all;

    }

    lldp-med {

        interface all;

    }

}

I have EX2200 with a LAG setup as ae0

want to connect it to a 4200 with LAG setup as ae1.

Does it matter what the ae number matches.?

Using an ex4300 and ELS style config, I have configured interface ranges, say access-vlan4, and I have configured RSTP on that range:

rstp {
interface access-vlan4 {
edge;
}
bpdu-block-on-edge;
}

also block on edge to try to help prevent switching loops.  Let's say that one particular port (in that interface range) we'd like a STP running switch plugged in.  We want to just discard any BPDUs inbound and not block that port but let normal traffic pass.  What would be the best way to configure that, in the ELS format?

Hello experts,
I am at a site and the core routers are passing all vlan to ex3300 switch, with avaya phones being used.
Data and voip had been configured on the ex3300 port, but I can only see the data IP when I do a show lldp.
any help would be appreciated.

I am not able to see the 3rd member in the JWEB.

When I ssh to the VC, I can see the ports I created.

When I use the JWEB, I do not see the ge-2/0/0-47 ports.

When I issue a halt, it only see's two fpc's.

root@CORPSW-FL3-VC1-0> request system halt all-members
warning: This command will halt all the members.
If planning to halt only one member use the member option
Halt the system ? [yes,no] (no) yes

Halting fpc1

Halting fpc2
Shutdown at Wed Feb 3 20:59:22 2016.
[pid 3090]
message sent

{master:0}
root@CORPSW-FL3-VC1-0>

version 12.3R6.6;
system {
    host-name CORPSW-FL3-VC1-0;
    root-authentication {
        encrypted-password "$1$RlqTw5lF$E7dSQWNN9OTzfVb3z6i8P0"; ## SECRET-DATA
    }
    services {
        ssh {
            protocol-version v2;
        }
        telnet;
        netconf {
            ssh;
        }
        web-management {
            http;
        }
        dhcp {
            traceoptions {
                file dhcp_logfile;
                level all;
                flag all;
            }
        }
    }
    syslog {
        user * {
            any emergency;
        }
        file messages {
            any notice;
            authorization info;
        }
        file interactive-commands {
            interactive-commands any;
        }
    }
}
chassis {
    alarm {
        management-ethernet {
            link-down ignore;
        }
    }
    auto-image-upgrade;
}
interfaces {
    ge-0/0/0 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/1 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/2 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/3 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/4 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/5 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/6 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/7 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/8 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/9 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/10 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/11 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/12 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/13 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/14 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/15 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/16 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/17 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/18 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/19 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/20 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/21 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/22 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/23 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/24 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/25 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/26 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/27 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/28 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/29 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/30 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/31 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/32 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/33 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/34 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/35 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/36 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/37 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/38 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/39 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/40 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/41 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/42 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/0/43 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/1/0 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/1/1 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/1/2 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-0/1/3 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/0 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/1 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/2 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/3 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/4 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/5 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/6 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/7 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/8 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/9 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/10 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/11 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/12 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/13 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/14 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/15 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/16 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/17 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/18 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/19 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/20 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/21 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/22 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/23 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/24 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/25 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/26 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/27 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/28 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/29 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/30 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/31 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/32 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/33 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/34 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/35 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/36 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/37 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/38 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/39 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/40 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/41 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/42 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/0/43 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/1/0 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/1/1 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/1/2 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-1/1/3 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/0 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/1 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/2 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/3 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/4 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/5 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/6 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/7 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/8 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/9 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/10 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/11 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/12 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/13 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/14 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/15 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/16 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/17 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/18 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/19 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/20 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/21 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/22 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/23 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/24 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/25 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/26 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/27 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/28 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/29 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/30 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/31 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/32 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/33 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/34 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/35 {
        unit 0 {
            family ethernet-switching;
        }
    }
    ge-2/0/36 {
        unit 0 {
            family ethernet-switching;
        }
    }
    vlan {
        unit 0 {
            family inet {
                address 10.10.9.221/24;
            }
        }
    }
}
routing-options {
    static {
        route 0.0.0.0/0 next-hop 10.10.9.254;
    }
}
protocols {
    igmp-snooping {
        vlan all;
    }
    rstp;
    lldp {
        interface all;
    }
    lldp-med {
        interface all;
    }
}
ethernet-switching-options {
    storm-control {
        interface all;
    }
}
vlans {
    default {
        l3-interface vlan.0;
    }
}
virtual-chassis {
    member 0 {
        mastership-priority 255;
    }
    member 1 {
        mastership-priority 255;
    }
    member 2 {
        mastership-priority 255;
    }
}
-------------------------------------------------
Stops showing at interface ge-1/0/43, should show ge-2/0/0 next

root@CORPSW-FL3-VC1-0> show interfaces ?
Possible completions:
<[Enter]> Execute this command
<interface-name> Name of physical or logical interface
 vcp-255/0/44
 vcp-255/0/44.32768
 vcp-255/0/45
 vcp-255/0/45.32768
 vcp-255/0/46
 vcp-255/0/46.32768
 vcp-255/0/47
 vcp-255/0/47.32768
 ge-0/0/0
 ge-0/0/0.0
 ge-0/0/1
 ge-0/0/1.0
 ge-0/0/2
 ge-0/0/2.0
 ge-0/0/3
 ge-0/0/3.0
 ge-0/0/4
 ge-0/0/4.0
 ge-0/0/5
 ge-0/0/5.0
 ge-0/0/6
 ge-0/0/6.0
 ge-0/0/7
 ge-0/0/7.0
 ge-0/0/8
 ge-0/0/8.0
 ge-0/0/9
 ge-0/0/9.0
 ge-0/0/10
 ge-0/0/10.0
 ge-0/0/11
 ge-0/0/11.0
 ge-0/0/12
 ge-0/0/12.0
 ge-0/0/13
 ge-0/0/13.0
 ge-0/0/14
 ge-0/0/14.0
 ge-0/0/15
 ge-0/0/15.0
 ge-0/0/16
 ge-0/0/16.0
 ge-0/0/17
 ge-0/0/17.0
 ge-0/0/18
 ge-0/0/18.0
 ge-0/0/19
 ge-0/0/19.0
 ge-0/0/20
 ge-0/0/20.0
 ge-0/0/21
 ge-0/0/21.0
 ge-0/0/22
 ge-0/0/22.0
 ge-0/0/23
 ge-0/0/23.0
 ge-0/0/24
 ge-0/0/24.0
 ge-0/0/25
 ge-0/0/25.0
 ge-0/0/26
 ge-0/0/26.0
 ge-0/0/27
 ge-0/0/27.0
 ge-0/0/28
 ge-0/0/28.0
 ge-0/0/29
 ge-0/0/29.0
 ge-0/0/30
 ge-0/0/30.0
 ge-0/0/31
 ge-0/0/31.0
 ge-0/0/32
 ge-0/0/32.0
 ge-0/0/33
 ge-0/0/33.0
 ge-0/0/34
 ge-0/0/34.0
 ge-0/0/35
 ge-0/0/35.0
 ge-0/0/36
 ge-0/0/36.0
 ge-0/0/37
 ge-0/0/37.0
 ge-0/0/38
 ge-0/0/38.0
 ge-0/0/39
 ge-0/0/39.0
 ge-0/0/40
 ge-0/0/40.0
 ge-0/0/41
 ge-0/0/41.0
 ge-0/0/42
 ge-0/0/42.0
 ge-0/0/43
 ge-0/0/43.0
 ge-1/0/0
 ge-1/0/0.0
 ge-1/0/1
 ge-1/0/1.0
 ge-1/0/2
 ge-1/0/2.0
 ge-1/0/3
 ge-1/0/3.0
 ge-1/0/4
 ge-1/0/4.0
 ge-1/0/5
 ge-1/0/5.0
 ge-1/0/6
 ge-1/0/6.0
 ge-1/0/7
 ge-1/0/7.0
 ge-1/0/8
 ge-1/0/8.0
 ge-1/0/9
 ge-1/0/9.0
 ge-1/0/10
 ge-1/0/10.0
 ge-1/0/11
 ge-1/0/11.0
 ge-1/0/12
 ge-1/0/12.0
 ge-1/0/13
 ge-1/0/13.0
 ge-1/0/14
 ge-1/0/14.0
 ge-1/0/15
 ge-1/0/15.0
 ge-1/0/16
 ge-1/0/16.0
 ge-1/0/17
 ge-1/0/17.0
 ge-1/0/18
 ge-1/0/18.0
 ge-1/0/19
 ge-1/0/19.0
 ge-1/0/20
 ge-1/0/20.0
 ge-1/0/21
 ge-1/0/21.0
 ge-1/0/22
 ge-1/0/22.0
 ge-1/0/23
 ge-1/0/23.0
 ge-1/0/24
 ge-1/0/24.0
 ge-1/0/25
 ge-1/0/25.0
 ge-1/0/26
 ge-1/0/26.0
 ge-1/0/27
 ge-1/0/27.0
 ge-1/0/28
 ge-1/0/28.0
 ge-1/0/29
 ge-1/0/29.0
 ge-1/0/30
 ge-1/0/30.0
 ge-1/0/31
 ge-1/0/31.0
 ge-1/0/32
 ge-1/0/32.0
 ge-1/0/33
 ge-1/0/33.0
 ge-1/0/34
 ge-1/0/34.0
 ge-1/0/35
 ge-1/0/35.0
 ge-1/0/36
 ge-1/0/36.0
 ge-1/0/37
 ge-1/0/37.0
 ge-1/0/38
 ge-1/0/38.0
 ge-1/0/39
 ge-1/0/39.0
 ge-1/0/40
 ge-1/0/40.0
 ge-1/0/41
 ge-1/0/41.0
 ge-1/0/42
 ge-1/0/42.0
 ge-1/0/43
 ge-1/0/43.0
 bme0
 bme0.32768
 bme0.32770
 bme0.32771
 dsc
 gre
 ipip
 lo0
 lo0.16384
 lsi
 me0
 me0.0
 mtun
 pimd
 pime
 tap
 vlan
 vlan.0





--------------------------------------------------
root@CORPSW-FL3-VC1-0> show virtual-chassis

Virtual Chassis ID: 8494.e36a.0857
Virtual Chassis Mode: Enabled
                                           Mstr           Mixed Neighbor List
Member ID  Status   Serial No    Model     prio  Role      Mode ID  Interface
0 (FPC 0)  Prsnt    CU0215380336 ex2200-48t-4g 255 Master*   NA  2  vcp-255/0/44
                                                                 1  vcp-255/0/45
                                                                 2  vcp-255/0/46
                                                                 1  vcp-255/0/47
1 (FPC 1)  Prsnt    CU0215380136 ex2200-48t-4g 255 Backup    NA  0  vcp-255/0/44
                                                                 2  vcp-255/0/45
                                                                 0  vcp-255/0/46
                                                                 2  vcp-255/0/47
2 (FPC 2)  Inactive CU0215380786 ex2200-48t-4g 255 Linecard  NA  1  vcp-255/0/44
                                                                 0  vcp-255/0/45
                                                                 1  vcp-255/0/46
                                                                 0  vcp-255/0/47

Member ID for next new member: 3 (FPC 3)


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


root@CORPSW-FL3-VC1-0> show virtual-chassis vc-port
fpc0:
--------------------------------------------------------------------------
Interface   Type              Trunk  Status       Speed        Neighbor
or                             ID                 (mbps)       ID  Interface
PIC / Port
0/44        Configured          6    Up           1000         2   vcp-255/0/45
0/45        Configured          5    Up           1000         1   vcp-255/0/44
0/46        Configured          6    Up           1000         2   vcp-255/0/47
0/47        Configured          5    Up           1000         1   vcp-255/0/46

fpc1:
--------------------------------------------------------------------------
Interface   Type              Trunk  Status       Speed        Neighbor
or                             ID                 (mbps)       ID  Interface
PIC / Port
0/44        Configured          5    Up           1000         0   vcp-255/0/45
0/45        Configured          6    Up           1000         2   vcp-255/0/44
0/46        Configured          5    Up           1000         0   vcp-255/0/47
0/47        Configured          6    Up           1000         2   vcp-255/0/46

fpc2:
--------------------------------------------------------------------------
Interface   Type              Trunk  Status       Speed        Neighbor
or                             ID                 (mbps)       ID  Interface
PIC / Port
0/44        Configured          5    Up           1000         1   vcp-255/0/45
0/45        Configured          6    Up           1000         0   vcp-255/0/44
0/46        Configured          5    Up           1000         1   vcp-255/0/47
0/47        Configured          6    Up           1000         0   vcp-255/0/46

{master:0}

---------------------------------------------------------------------------------------
root@CORPSW-FL3-VC1-0> show virtual-chassis status

Virtual Chassis ID: 8494.e36a.0857
Virtual Chassis Mode: Enabled
 Mstr Mixed Neighbor List
Member ID Status Serial No Model prio Role Mode ID Interface
0 (FPC 0) Prsnt CU0215380336 ex2200-48t-4g 255 Master* NA 2 vcp-255/0/44
 1 vcp-255/0/45
 2 vcp-255/0/46
 1 vcp-255/0/47
1 (FPC 1) Prsnt CU0215380136 ex2200-48t-4g 255 Backup NA 0 vcp-255/0/44
 2 vcp-255/0/45
 0 vcp-255/0/46
 2 vcp-255/0/47
2 (FPC 2) Inactive CU0215380786 ex2200-48t-4g 255 Linecard NA 1 vcp-255/0/44
 0 vcp-255/0/45
 1 vcp-255/0/46
 0 vcp-255/0/47

Member ID for next new member: 3 (FPC 3)

{master:0}
root@CORPSW-FL3-VC1-0> show virtual-chassis mode
fpc0:
--------------------------------------------------------------------------
Mixed Mode: Disabled

fpc1:
--------------------------------------------------------------------------
Mixed Mode: Disabled

fpc2:
--------------------------------------------------------------------------
Mixed Mode: Disabled

{master:0}
root@CORPSW-FL3-VC1-0> show virtual-chassis active-topology
fpc0:
--------------------------------------------------------------------------
 Destination ID Next-hop

 1 1(vcp-255/0/47.32768)

 2 2(vcp-255/0/44.32768)

fpc1:
--------------------------------------------------------------------------
 Destination ID Next-hop

 0 0(vcp-255/0/46.32768)

 2 2(vcp-255/0/45.32768)

fpc2:
--------------------------------------------------------------------------
 Destination ID Next-hop

 0 0(vcp-255/0/45.32768)

 1 1(vcp-255/0/46.32768)

{master:0}
root@CORPSW-FL3-VC1-0> show virtual-chassis device-topology
fpc0:
--------------------------------------------------------------------------
 Neighbor List
Member Device Status System ID Member Device Interface
 0 0 Prsnt ec3e.f751.c9c0 1 3 vcp-255/0/45
 0 1 internal-0/24
 2 6 vcp-255/0/44
 0 1 Prsnt ec3e.f751.c9c1 0 0 internal-1/27
 1 3 Prsnt ec3e.f751.97c0 1 4 internal-0/24
 0 0 vcp-255/0/44
 2 6 vcp-255/0/45
 1 4 Prsnt ec3e.f751.97c1 1 3 internal-1/27
 2 6 Prsnt ec3e.f752.3a40 1 3 vcp-255/0/44
 0 0 vcp-255/0/45
 2 7 internal-0/24
 2 7 Prsnt ec3e.f752.3a41 2 6 internal-1/27

fpc1:
--------------------------------------------------------------------------
 Neighbor List
Member Device Status System ID Member Device Interface
 0 0 Prsnt ec3e.f751.c9c0 1 3 vcp-255/0/45
 0 1 internal-0/24
 2 6 vcp-255/0/44
 0 1 Prsnt ec3e.f751.c9c1 0 0 internal-1/27
 1 3 Prsnt ec3e.f751.97c0 1 4 internal-0/24
 0 0 vcp-255/0/44
 2 6 vcp-255/0/45
 1 4 Prsnt ec3e.f751.97c1 1 3 internal-1/27
 2 6 Prsnt ec3e.f752.3a40 1 3 vcp-255/0/44
 0 0 vcp-255/0/45
 2 7 internal-0/24
 2 7 Prsnt ec3e.f752.3a41 2 6 internal-1/27

fpc2:
--------------------------------------------------------------------------
 Neighbor List
Member Device Status System ID Member Device Interface
 0 0 Prsnt ec3e.f751.c9c0 1 3 vcp-255/0/45
 0 1 internal-0/24
 2 6 vcp-255/0/44
 0 1 Prsnt ec3e.f751.c9c1 0 0 internal-1/27
 1 3 Prsnt ec3e.f751.97c0 1 4 internal-0/24
 0 0 vcp-255/0/44
 2 6 vcp-255/0/45
 1 4 Prsnt ec3e.f751.97c1 1 3 internal-1/27
 2 6 Prsnt ec3e.f752.3a40 1 3 vcp-255/0/44
 0 0 vcp-255/0/45
 2 7 internal-0/24
 2 7 Prsnt ec3e.f752.3a41 2 6 internal-1/27

{master:0}
root@CORPSW-FL3-VC1-0>

What is needed to make the 3rd EX2200 show up as useable  

Thanks

Hi,

We run a private datacenter with EX4500 VC at the core and EX4200 VC at the edges.

On the EX4200 stacks, we've got hundreds of vmware/Dell servers with multiple 1G attachments.

We don't use LACP on server attachments (load distribution is achieved by vmware/vsphere proprietary algorithms, distributing vm mac adresses on network uplink). It's been running for years without any problems.

We usually don't accept on our network other hosts/devices than those we test and install by ourselves.

For the first time we are asked to offer network connection to some custumer exotic devices... and they want 4x1G LACP attachements on the EX4200 edge switches.

Ten years ago, I had a very bad experience in such a configuration when a customer plugged its own (nortel) switch with multiple attachements into our core campus switch.

The Core was configured with static aggregation (no LACP, old style MLT aggregation), the customer misconfigured its switch and forgot to validate link aggregation on his side... boom... loop... campus down.

Today, as we will configure the AE interface with LACP (active mode) I guess this couldn't happen today with LACP, even if the customer misconfigured its devices and forgot to validate link aggregation or LACP.

I'd like to discuss how an EX4200 with LACP would act in such a situation ?

=> Our side, EX4200 4x1G, LACP   VS  customer, misconfigured, 4x1G, no link aggregation, no LACP :

LACP shouldn't come up on our side.

=> If the customer is transmitting traffic/broadcasts over its misconfigured non agregated ports, what will happen ? Will the EX4200 drop these packets (because they're being received on interfaces part of a LAG that is down, even if each individual interface is up) or accept them and switch them on individual interfaces, hence creating a loop ?

ence creating a loop ?

In other words, does LACP prevent loop formation in such (mis)configuration ?

Regards,

Pascal