Shown by the master here 


user@switch> show virtual-chassis

Virtual Chassis ID: 0019.e250.47a0
Virtual Chassis Mode: Enabled
                                          Mastership        Mixed  Neighbor List
Member ID  Status  Serial No    Model      priority   Role    Mode   ID  Interface
0 (FPC 0)  Prsnt   AK0207360276 ex4200-24t     249   Master*    N   8   vcp-0    
                                                                    1   vcp-1    
1 (FPC 1)  Prsnt   AK0207360281 ex4200-24t     248   Backup     N   0   vcp-0    
                                                                    2   vcp-1 

If you do come up with information on this not being supported on some cards, I would appreciate that.  I will continue through digging in the meantime, but as fart as I can tell, a bridge domain is completely useless on these cards if you literally cannot use ANY layer 2 security features...

BTW, did you open a case on this with TAC?  I would assume you have support on an MX.

Hi,

The * indicates which member within the virtual chassis that is managing the connection. If you session into the backup RE and run the same command you will see the * moves to the backup.

request session member 1

Tim

That info is shown here under Role

https://www.juniper.net/documentation/en_US/junos/topics/reference/command-summary/show-virtual-chassis-status-mx-series.html

but is not shown here

https://www.juniper.net/documentation/en_US/junos/topics/reference/command-summary/show-virtual-chassis.html

Will look to get this 2nd part improved.

I may do that.  In the meantime, 15 other vendors do what the MX can't. So I have a work around.  Just annoyed at the juniper documentation error.

@ elivaughan - I do understand your frustration, and can only say that Juniper is trying to improve their documentation every day.  As for those 15 other vendors, I fully expect that the MX can do a lot more networking functions, outside of Port Level Security on DPCE modules, than those 15 vendors can; there are always trade-offs.  Especially in the time frame that DPCE modules were the standard bearer, I believe MX was almost never used at access layer of network, and most likely is still not often used there, due primarily price per port.  In general it is Juniper devices like EX, where Port Level Security is performed.

This is not an excuse for not documenting this behavior fully, which I am still looking into.  I suggested a case so that TAC or someone within Juniper Engg could confirm 100% that this functionality is NOT there with DPCE based cards.  I am making a best guess on this.

As well, this functionality was added in Junos 14.1R1, which came out July 2014.  This is 1st time I have heard of any complaint in regards to this feature, and it has been out more than 3.5 years.  Again, not an excuse, but a fact.

Best Regards.

I am running a legacy DHCP server on an EX3300 (v12.3).

I have a few server interfaces that I want to address with DHCP reservations from within an existing pool but I DO NOT want them to receive a default gateway (routers, DHCP Option 3).

Is it possible to override the pool configuration and not send routers information using a static reservation? My testing suggests that including the router option requires a functioning IP or hostname as a parameter. Not including the router option sends the pool's default configuration.

Currently I see two workarounds. One is to split the pools into one that provides the routers option, and one that doesn't. The other involves making reservations for every other device...I might as well not use DHCP in that case!

Hi, how can I find, what is wrong with my network? My topology is with access Cisco switches, distribution switches and Cisco core switches but the Cisco core switches they are in stack. And everything was fine.. Now we migrated old core Cisco switches to new Juniper core QFX and EX. switches in stack in ring topology, two QFX are In one location like one stack, two QFX are in other location and one QFX in other location. And all 5 QFX are in stack like one in ring topology. In Juniper QFX we create Link aggreggation with lacp and we connect all our cisco equipment with channel groups (port channels in lacp mode) to new Juniper QFX core switches. And the network is too slow now... The problem is all our end user systems in access level work so slowly ... The all our network is toooooooooo slow.............................. How can we troubleshot the problems?

RSTP may have decided on a Root switch different from what it shold be.  Apparently, QFX should be Root.

Also, RSTP on Juniper is standard 802.1w [one instance] while Cisco is proprietary Rapid PVST+ [instance per VLAN]. Both are compabile. 

Thanks.

 One QFX is Master  and one another QFX is backup.
The master QFX Juniper is  root.

2nd DHCP issue in as many days.

EX3300 running legacy DHCP server is incorrectly distributing addresses from an adjacent pool. Output from dhcp_logfile shows the DHCPDISCOVER being received on 172.20.1.33. This should generate a offer from the 172.20.1.32/27 pool but something happens and the server selects an address from the 172.20.1.0/27 pool.

*** dhcp_logfile ***
Mar 21 11:36:44 received packet from 0.0.0.0 port 68 interface vlan.791 routing instance default
Mar 21 11:36:44 Link local IP: 0
Mar 21 11:36:44 -- looking for pool with subnet 172.20.1.33, prefix length 32
Mar 21 11:36:44 -- [pfxlen 25] Found pool `172.20.1.0/27'

UPDATE: Solved this with a restart of the dhcp service:

>restart dhcp

Do you read the same on all Cisco switches as well?

Thanks.

Hello,

I have a pair of QFX5100's configured as MC-LAG peers. I have an MC-LAG going up to an MX5 router - ge-0/0/41 on both QFX5100-A and QFX5100-B connect to MX5.

The problem is I'm seeing drops in my best-effort queue even though I'm pushing less than 500Mbps through the interface. I'm using iperf to generate UDP traffic. When I push more than 100Mbps, I'm seeing thousands of drops on my ge-0/0/41 interfaces (the mc-ae interface is ae8). Here is my QoS configuration:

admin@QFX5100-B# show class-of-service
classifiers {
    dscp CLASSIFIER-DSCP {
        forwarding-class FC-BE {
            loss-priority low code-points [ 000000 000001 000010 000011 000100 000101 000110 000111 001000 001001 001010 001011 001100 001101 001110 001111 010000 010001 010010 010100 010011 010101 010110 010111 011000 011100 011001 011010 011011 011101 011110 011111 100000 100001 100011 100100 100101 100110 100111 101000 101001 101010 101011 101100 101101 101111 110001 110010 110011 110100 110101 110110 110111 111000 111001 111010 111011 111100 111101 111110 111111 ];
        }
        forwarding-class FC-AF {
            loss-priority low code-points 100010;
        }
        forwarding-class FC-NC {
            loss-priority low code-points 110000;
        }
        forwarding-class FC-EF {
            loss-priority low code-points 101110;
        }
    }
}
drop-profiles {
    DP-STANDARD {
        interpolate {
            fill-level [ 95 99 ];
            drop-probability [ 0 50 ];
        }
    }
}
shared-buffer {
    ingress {
        percent 100;
        buffer-partition lossless {
            percent 5;
        }
        buffer-partition lossless-headroom {
            percent 0;
        }
        buffer-partition lossy {
            percent 95;
        }
    }
    egress {
        percent 100;
        buffer-partition lossless {
            percent 5;
        }
        buffer-partition lossy {
            percent 75;
        }
        buffer-partition multicast {
            percent 20;
        }
    }
}
forwarding-classes {
    class FC-BE queue-num 0;
    class FC-AF queue-num 1;
    class FC-NC queue-num 2;
    class FC-EF queue-num 3;
}
traffic-control-profiles {
    TC-PROFILE-STANDARD {
        scheduler-map SCHEDMAP-STANDARD;
    }
    TC-PROFILE-STRICT {
        scheduler-map SCHEDMAP-STRICT;
    }
}
forwarding-class-sets {
    FC-SET-STANDARD {
        class FC-BE;
        class FC-AF;
        class FC-NC;
    }
    FC-SET-STRICT {
        class FC-EF;
    }
}
interfaces {
    ge-* {
        forwarding-class-set {
            FC-SET-STANDARD {
                output-traffic-control-profile TC-PROFILE-STANDARD;
            }
            FC-SET-STRICT {
                output-traffic-control-profile TC-PROFILE-STRICT;
            }
        }
        unit 0 {
            classifiers {
                dscp CLASSIFIER-DSCP;
            }
        }
    }
    xe-* {
        forwarding-class-set {
            FC-SET-STANDARD {
                output-traffic-control-profile TC-PROFILE-STANDARD;
            }
            FC-SET-STRICT {
                output-traffic-control-profile TC-PROFILE-STRICT;
            }
        }
        unit 0 {
            classifiers {
                dscp CLASSIFIER-DSCP;
            }
        }
    }
    ae* {
        forwarding-class-set {
            FC-SET-STANDARD {
                output-traffic-control-profile TC-PROFILE-STANDARD;
            }
            FC-SET-STRICT {
                output-traffic-control-profile TC-PROFILE-STRICT;
            }
        }
        unit 0 {
            classifiers {
                dscp CLASSIFIER-DSCP;
            }
        }
    }
}
scheduler-maps {
    SCHEDMAP-STANDARD {
        forwarding-class FC-BE scheduler SCHED-BE;
        forwarding-class FC-AF scheduler SCHED-AF;
        forwarding-class FC-NC scheduler SCHED-NC;
    }
    SCHEDMAP-STRICT {
        forwarding-class FC-EF scheduler SCHED-EF;
    }
}
schedulers {
    SCHED-BE {
        transmit-rate percent 80;
        buffer-size {
            remainder;
        }
        priority low;
        drop-profile-map loss-priority low protocol any drop-profile DP-STANDARD;
    }
    SCHED-AF {
        transmit-rate percent 5;
        buffer-size percent 5;
        priority low;
        drop-profile-map loss-priority low protocol any drop-profile DP-STANDARD;
    }
    SCHED-NC {
        transmit-rate percent 5;
        buffer-size percent 5;
        priority low;
        drop-profile-map loss-priority low protocol any drop-profile DP-STANDARD;
    }
    SCHED-EF {
        shaping-rate percent 10;
        buffer-size percent 0;
        priority strict-high;
    }
}

Here is the interface stats:

admin@QFX5100-B# run show interfaces ge-0/0/41 extensive
Physical interface: ge-0/0/41, Enabled, Physical link is Up
  Interface index: 670, SNMP ifIndex: 651, Generation: 161
  Description: L3 Link to MX5-B - NeutralPath
  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: Copper
  Device flags   : Present Running
  Interface flags: SNMP-Traps Internal: 0x4000
  Link flags     : None
  CoS queues     : 12 supported, 12 maximum usable queues
  Hold-times     : Up 0 ms, Down 0 ms
  Current address: 28:a2:4b:42:33:d8, Hardware address: 28:a2:4b:42:33:0c
  Last flapped   : 2018-02-14 22:47:30 CST (4w6d 11:44 ago)
  Statistics last cleared: 2018-03-21 09:35:39 CDT (01:55:53 ago)
  Traffic statistics:
   Input  bytes  :           1584906758                14984 bps
   Output bytes  :            943837004               101200 bps
   Input  packets:              1214425                   19 pps
   Output packets:              1471527                   96 pps
   IPv6 transit statistics:
    Input  bytes  :                   0
    Output bytes  :                   0
    Input  packets:                   0
    Output packets:                   0
  Input errors:
    Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Bucket drops: 0, Policed discards: 0,
    L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0, FIFO errors: 0,
    Resource errors: 0
  Output errors:
    Carrier transitions: 0, Errors: 0, Drops: 12360, Collisions: 0, Aged packets: 0, FIFO errors: 0,
    HS link CRC errors: 0, MTU errors: 0, Resource errors: 0, Bucket drops: 0
  Egress queues: 12 supported, 7 in use
  Queue counters:       Queued packets  Transmitted packets      Dropped packets
    0                                0              1307498                12360
    1                                0                    0                    0
    2                                0                   14                    0
    3                                0                   39                    0
    4                                0                    0                    0
    7                                0               160280                    0
    8                                0                    0                    0
  Queue number:         Mapped forwarding classes
    0                   FC-BE
    1                   FC-AF
    2                   FC-NC
    3                   FC-EF
    4                   no-loss
    7                   network-control
    8                   mcast
  Active alarms  : None
  Active defects : None
  MAC statistics:                      Receive         Transmit
    Total octets                    1584906758        943837004
    Total packets                      1214425          1471527
    Unicast packets                    1207472          1460998
    Broadcast packets                        0               23
    Multicast packets                     6953            10506
    CRC/Align errors                         0                0
    FIFO errors                              0                0
    MAC control frames                       0                0
    MAC pause frames                         0                0
    Oversized frames                         0
    Jabber frames                            0
    Fragment frames                          0
    VLAN tagged frames                 1207472
    Code violations                          0
  MAC Priority Flow Control Statistics:
    Priority :  0                             0                0
    Priority :  1                             0                0
    Priority :  2                             0                0
    Priority :  3                             0                0
    Priority :  4                             0                0
    Priority :  5                             0                0
    Priority :  6                             0                0
    Priority :  7                             0                0
  Filter statistics:
    Input packet count                       0
    Input packet rejects                     0
    Input DA rejects                         0
    Input SA rejects                         0
    Output packet count                                       0
    Output packet pad count                                   0
    Output packet error count                                 0
    CAM destination filters: 1, CAM source filters: 0
  Autonegotiation information:
    Negotiation status: Complete
    Link partner:
        Link mode: Full-duplex, Flow control: None, Remote fault: OK, Link partner Speed: 1000 Mbps
    Local resolution:
        Flow control: None, Flow control tx: None, Flow control rx: None, Remote fault: Link OK
  Packet Forwarding Engine configuration:
    Destination slot: 0 (0x00)
  Interface transmit statistics: Disabled

  Logical interface ge-0/0/41.0 (Index 552) (SNMP ifIndex 662) (HW Token 2147483649) (Generation 184)
    Flags: Up SNMP-Traps 0x24024000 Encapsulation: Ethernet-Bridge
    Traffic statistics:
     Input  bytes  :                    0
     Output bytes  :               389618
     Input  packets:                    0
     Output packets:                 2861
    Local statistics:
     Input  bytes  :                    0
     Output bytes  :               389618
     Input  packets:                    0
     Output packets:                 2861
    Transit statistics:
     Input  bytes  :                    0                    0 bps
     Output bytes  :                    0                    0 bps
     Input  packets:                    0                    0 pps
     Output packets:                    0                    0 pps
    Protocol aenet, AE bundle: ae8.0, Generation: 208, Route table: 0

And here are some QoS output commnads:

admin@QFX5100-B# run show interfaces queue ge-0/0/41
Physical interface: ge-0/0/41, Enabled, Physical link is Up
  Interface index: 670, SNMP ifIndex: 651
  Description: L3 Link to DAL-MX5-B - NeutralPath
Forwarding classes: 16 supported, 7 in use
Egress queues: 12 supported, 7 in use
Queue: 0, Forwarding classes: FC-BE
  Queued:
    Packets              :                     0                     0 pps
    Bytes                :                     0                     0 bps
  Transmitted:
    Packets              :               1317060                    36 pps
    Bytes                :             933203718                 45760 bps
    Tail-dropped packets : Not Available
    RL-dropped packets   :                     0                     0 pps
    RL-dropped bytes     :                     0                     0 bps
    Total-dropped packets:                 12360                     0 pps
    Total-dropped bytes  :              17389225                     0 bps
Queue: 1, Forwarding classes: FC-AF
  Queued:
    Packets              :                     0                     0 pps
    Bytes                :                     0                     0 bps
  Transmitted:
    Packets              :                     0                     0 pps
    Bytes                :                     0                     0 bps
    Tail-dropped packets : Not Available
    RL-dropped packets   :                     0                     0 pps
    RL-dropped bytes     :                     0                     0 bps
    Total-dropped packets:                     0                     0 pps
    Total-dropped bytes  :                     0                     0 bps
Queue: 2, Forwarding classes: FC-NC
  Queued:
    Packets              :                     0                     0 pps
    Bytes                :                     0                     0 bps
  Transmitted:
    Packets              :                    14                     0 pps
    Bytes                :                  1372                     0 bps
    Tail-dropped packets : Not Available
    RL-dropped packets   :                     0                     0 pps
    RL-dropped bytes     :                     0                     0 bps
    Total-dropped packets:                     0                     0 pps
    Total-dropped bytes  :                     0                     0 bps
Queue: 3, Forwarding classes: FC-EF
  Queued:
    Packets              :                     0                     0 pps
    Bytes                :                     0                     0 bps
  Transmitted:
    Packets              :                    39                     0 pps
    Bytes                :                  3822                     0 bps
    Tail-dropped packets : Not Available
    RL-dropped packets   :                     0                     0 pps
    RL-dropped bytes     :                     0                     0 bps
    Total-dropped packets:                     0                     0 pps
    Total-dropped bytes  :                     0                     0 bps
Queue: 4, Forwarding classes: no-loss
  Queued:
    Packets              :                     0                     0 pps
    Bytes                :                     0                     0 bps
  Transmitted:
    Packets              :                     0                     0 pps
    Bytes                :                     0                     0 bps
    Tail-dropped packets : Not Available
    RL-dropped packets   :                     0                     0 pps
    RL-dropped bytes     :                     0                     0 bps
    Total-dropped packets:                     0                     0 pps
    Total-dropped bytes  :                     0                     0 bps
Queue: 7, Forwarding classes: network-control
  Queued:
    Packets              :                     0                     0 pps
    Bytes                :                     0                     0 bps
  Transmitted:
    Packets              :                162251                    22 pps
    Bytes                :              12489518                 13936 bps
    Tail-dropped packets : Not Available
    RL-dropped packets   :                     0                     0 pps
    RL-dropped bytes     :                     0                     0 bps
    Total-dropped packets:                     0                     0 pps
    Total-dropped bytes  :                     0                     0 bps
Queue: 8, Forwarding classes: mcast
  Queued:
    Packets              :                     0                     0 pps
    Bytes                :                     0                     0 bps
  Transmitted:
    Packets              :                     0                     0 pps
    Bytes                :                     0                     0 bps
    Tail-dropped packets : Not Available
    RL-dropped packets   :                     0                     0 pps
    RL-dropped bytes     :                     0                     0 bps
    Total-dropped packets:                     0                     0 pps
    Total-dropped bytes  :                     0                     0 bps

admin@QFX5100-B# run show class-of-service interface ge-0/0/41
Physical interface: ge-0/0/41, Index: 670
Queues supported: 12, Queues in use: 7
  Congestion-notification: Disabled
  Forwarding class set: FC-SET-STANDARD, Index: 52944
    Output traffic control profile: TC-PROFILE-STANDARD, Index: 36518
  Forwarding class set: FC-SET-STRICT, Index: 43469
    Output traffic control profile: TC-PROFILE-STRICT, Index: 46173

  Logical interface: ge-0/0/41.0, Index: 552
Object                  Name                   Type                    Index
Classifier              CLASSIFIER-DSCP        dscp                    49277
Classifier              ieee8021p-default      ieee8021p                  11

admin@QFX5100-B# run show class-of-service shared-buffer
Ingress:
  Total Buffer     :  12480.00 KB
  Dedicated Buffer :  2912.81 KB
  Shared Buffer    :  9567.19 KB
    Lossless          :  478.36 KB
    Lossless Headroom :  0.00 KB
    Lossy             :  9088.83 KB

  Lossless Headroom Utilization:
  Node Device         Total          Used                  Free
  0                   0.00 KB        0.00 KB               0.00 KB

Egress:
  Total Buffer     :  12480.00 KB
  Dedicated Buffer :  3744.00 KB
  Shared Buffer    :  8736.00 KB
    Lossless          :  436.80 KB
    Multicast         :  1747.20 KB
    Lossy             :  6552.00 KB

Finally, the interface config:

admin@QFX5100-B# show interfaces ae8
description "L3 Link to DAL-MX5-B - NeutralPath";
aggregated-ether-options {
    lacp {
        active;
        system-id 00:00:00:00:00:08;
        admin-key 1;
    }
    mc-ae {
        mc-ae-id 8;
        chassis-id 1;
        mode active-active;
        status-control standby;
        init-delay-time 420;
    }
}
unit 0 {
    family ethernet-switching {
        interface-mode trunk;
        vlan {
            members [ VLAN-100 VLAN-200 VLAN-300 VLAN-400 ];
        }
    }
}

{master:0}[edit]
admin@QFX5100-B# show interfaces ge-0/0/41
description "L3 Link to DAL-MX5-B - NeutralPath";
ether-options {
    802.3ad ae8;
}

In my opinion, there should be NO reason for the QFX to drop anything on this interface. Like I said, I'm pushing between 200Mbps and 400Mbps on a 1Gbps interface. Why are there drops?

I'm running 14.1X53-D40.8. Any help would be appreciated. Thanks!

Good day, everyone. My background is primarily Cisco, so I'm still cutting my teeth on Juniper's way of doing things. 

We have a virtual chassis composed of four EX-3300 48-port switches: One master, one backup, and two linecard, all located in the same LAN closet. All of the switches have uplinks to a Palo Alto PA-500 network appliance. There are fourteen VLANS defined in this VC.

We are in a situation where we need to extend this network to a satellite facility. The fiber run is in place, and all I need now is guidance on how to extend our network presence from our LAN closet to this facility a few miles down the road.

My understanding, from the documentation, is that EX3300 switches CANNOT run in a mixed virtual chassis, which presents a problem. We would like to do the following:

1.  Connect the current VC to an EX2200-24P switch, located at the satellite facility.

2. Connect an EX2300-C-12P to the EX2200 above, so that we can extend the network to a neighboring outbuilding.

If I cannot add these switches to the existing VC and run in mixed mode, what are my options? These switches need to be able to see all of the resources the VC manages.

I am currently trying to do something similar.   I think you need a new feature to be supported in Junos called 'port-bounce'.  This is where the RADIUS server sends a COA (Change of Authorization) message to the switch that changes the VLAN and also bounces the port to force a new DHCP request.    

Apparently no config is required on the switch, but the feature was only implemented in 17.3 on an EX4300 (what I am using - not sure about your switch).  So you may want to look at Pathfinder.juniper.net to see if you need new Junos.  Here is some info:

https://apps.juniper.net/feature-explorer/feature-info.html?fKey=7896&fn=Port+bounce+with+CoA+requests+and+framed-IPv6-address+RADIUS+attribute+for+AAA

The other thing you need is for the Port-Bounce RADIUS VSA to be sent by the RADIUS server.   Our server does not have this in the juniper.dct file, so it is unable to send it.    Unfortunately I have also been unable to find a new juniper.dct dictionary anywhere.   

More info:  https://www.juniper.net/documentation/en_US/junos/topics/concept/802-1x-radius-initiated-changes.html#jd0e56

We use Pulse Policy Secure for this, and I was considering modifying the juniper.dct file to include the new VSA, but don't know what the attribute value should be.  If you find out, do let me know!

Good luck.

Andy

You could very well be correct. These are older line cards, so that could actually be the reason for the documentation lagging the feature.  Which is fine, as long as that is the case. I'll buy new cards.  But i would need to know which cards would support this. I can have a discussion with my sales guys, though.

I think my biggest issue is...  If the MX doesn't support this on these cards, then that means there was a time when there was literally no way to perform layer 2 security on the MX.  Bridge domains have been supported since version 9.x, maybe even before.

I'll try to figure out which cards do support this feature.

Hi Guys,

I have an interesting issue. I have a 2 member VC where I am using preprovisioning. However that info seems to be getting ignored by the switches upon reboot. Even if I stagger the reboots the wrong switch becomes master. In my preprovision config I have the higher serial numbered switch set as member 0 and routing-engine role assigned. Upon reboot of all the switches member 1 always becomes master. Even if I let member 0 boot first it will stay as a Line card until the other is booted. It will not assume its role as a routing engine until the other node comes up and then it assumes the backup role.  It also doesnt route traffic. I have to manually trigger a role release for member 0 to assume the Master routing role. After that everything works and connectivity is restored. Anyone seen this kind of behavior?  Pasted my VC config below. 

preprovisioned;
no-split-detection;
member 0 {
role routing-engine;
serial-number GA02170704XX;
}
member 1 {
role routing-engine;
serial-number GA02170701XX

Hi ,

What is the JUNOs version running?

What if you shutdown member 1, is member 0 continue as linecard? Did you try to reactivate mastership by issuing the command

>request virtual-chassis reactivate 

Regards,

Ajo Thomas

I've same situation.

this evening I'll try as you described.

regards