Quantcast
Channel: Ethernet Switching topics
Viewing all 2326 articles
Browse latest View live

2xEX2300 VC: fpc0 ifd null, port 28 / dc-pfe: ifd null, port 28 what does these messages mean?

$
0
0

Hi,

 

I have a 2xEX2300-48p virtual-chassi that sends these syslog messages 24/7 (around 128K per day):

Mar  8 15:06:11 *hostname* dc-pfe: ifd null, port 29
Mar  8 15:06:11 *hostname* fpc0 ifd null, port 29
Mar  8 15:06:15 *hostname* dc-pfe: ifd null, port 28
Mar  8 15:06:15 *hostname* fpc0 ifd null, port 28
Mar  8 15:06:16 *hostname* dc-pfe: ifd null, port 28
Mar  8 15:06:16 *hostname* fpc0 ifd null, port 28
Mar  8 15:06:17 *hostname* dc-pfe: ifd null, port 29
Mar  8 15:06:17 *hostname* fpc0 ifd null, port 29
Mar  8 15:06:17 *hostname* dc-pfe: ifd null, port 28
Mar  8 15:06:17 *hostname* fpc0 ifd null, port 28
Mar  8 15:06:18 *hostname* dc-pfe: ifd null, port 29
Mar  8 15:06:18 *hostname* fpc0 ifd null, port 29
Mar  8 15:06:19 *hostname* dc-pfe: ifd null, port 29
Mar  8 15:06:19 *hostname* fpc0 ifd null, port 29
Mar  8 15:06:24 *hostname* dc-pfe: ifd null, port 28
Mar  8 15:06:24 *hostname* fpc0 ifd null, port 28
Mar  8 15:06:25 *hostname* dc-pfe: ifd null, port 28
Mar  8 15:06:25 *hostname* fpc0 ifd null, port 28
Mar  8 15:06:25 *hostname* dc-pfe: ifd null, port 29
Mar  8 15:06:25 *hostname* fpc0 ifd null, port 29
Mar  8 15:06:26 *hostname* dc-pfe: ifd null, port 28
Mar  8 15:06:26 *hostname* fpc0 ifd null, port 28
Mar  8 15:06:26 *hostname* dc-pfe: ifd null, port 29
Mar  8 15:06:26 *hostname* fpc0 ifd null, port 29
Mar  8 15:06:27 *hostname* dc-pfe: ifd null, port 29
Mar  8 15:06:27 *hostname* fpc0 ifd null, port 29
Mar  8 15:06:32 *hostname* dc-pfe: ifd null, port 28
Mar  8 15:06:32 *hostname* fpc0 ifd null, port 28
Mar  8 15:06:33 *hostname* dc-pfe: ifd null, port 28
Mar  8 15:06:33 *hostname* fpc0 ifd null, port 28
Mar  8 15:06:33 *hostname* dc-pfe: ifd null, port 29
Mar  8 15:06:33 *hostname* fpc0 ifd null, port 29
Mar  8 15:06:34 *hostname* dc-pfe: ifd null, port 28
Mar  8 15:06:34 *hostname* fpc0 ifd null, port 28
Mar  8 15:06:34 *hostname* dc-pfe: ifd null, port 29
Mar  8 15:06:34 *hostname* fpc0 ifd null, port 29
Mar  8 15:06:35 *hostname* dc-pfe: ifd null, port 29
Mar  8 15:06:35 *hostname* fpc0 ifd null, port 29

What on earth does it mean?

show interface ifd-index 28:

root@hostname> show interfaces ifd-index 28
  Logical interface .local..0 (Index 0) (SNMP ifIndex 0)
    Flags: Down Point-To-Point Encapsulation: Unspecified
    Protocol inet, MTU: Unlimited
      Flags: None
      Addresses, Flags: Is-Primary
        Local: 10.1.1.4
    Protocol iso, MTU: Unlimited
      Flags: None
    Protocol inet6, MTU: Unlimited
    Max nh cache: 0, New hold nh limit: 0, Curr nh cnt: 0, Curr new hold cnt: 0, NH drop cnt: 0
      Flags: None
    Protocol mpls, MTU: Unlimited, Maximum labels: 3
      Flags: None
    Protocol eth-switch, MTU: Unlimited
      Flags: None
    Protocol 56, MTU: Unlimited
      Flags: None
    Protocol 57, MTU: Unlimited
      Flags: None
    Protocol 60, MTU: Unlimited
      Flags: None
    Protocol 61, MTU: Unlimited
      Flags: None

show interface ifd-index 29:

root@hostname> show interfaces ifd-index 29
  Logical interface .local..0 (Index 0) (SNMP ifIndex 0)
    Flags: Down Point-To-Point Encapsulation: Unspecified
    Protocol inet, MTU: Unlimited
      Flags: None
      Addresses, Flags: Is-Primary
        Local: 10.1.1.4
    Protocol iso, MTU: Unlimited
      Flags: None
    Protocol inet6, MTU: Unlimited
    Max nh cache: 0, New hold nh limit: 0, Curr nh cnt: 0, Curr new hold cnt: 0, NH drop cnt: 0
      Flags: None
    Protocol mpls, MTU: Unlimited, Maximum labels: 3
      Flags: None
    Protocol eth-switch, MTU: Unlimited
      Flags: None
    Protocol 56, MTU: Unlimited
      Flags: None
    Protocol 57, MTU: Unlimited
      Flags: None
    Protocol 60, MTU: Unlimited
      Flags: None
    Protocol 61, MTU: Unlimited
      Flags: None

my irb.500 interface, which I use for management has IP 10.1.1.4.

root@hostname> show interfaces irb.500
  Logical interface irb.500 (Index 651) (SNMP ifIndex 717)
    Flags: Up SNMP-Traps 0x4004000 Encapsulation: ENET2
    Bandwidth: 1000mbps
    Routing Instance: default-switch Bridging Domain: MGMT-INTERNAL
    Input packets : 224490
    Output packets: 6157558
    Protocol inet, MTU: 1500
      Flags: Sendbcast-pkt-to-re, Is-Primary
      Addresses, Flags: Is-Default Is-Preferred Is-Primary
        Destination: 10.1.1/24, Local: 10.1.1.4, Broadcast: 10.1.1.255

How do I stop these messages from being generated? And if I can't and there's nothing to worry about, how do I stop them from being sent to my syslog server?

 

thanks in advance

 

best regards,

Peter


Virtual chassis benefits

$
0
0

Hi,

I am setting up a little infrastructure relying on two EX3300.

Communications with the outside world depend on a single optical link, so I have to connect it on one of them.

In order to get redundency, all network interfaces are bonded on both servers and storage appliances.

So my servers and their storage can be comfortable even if a switch fails, I just have to connect the fiber to the other one in that case.

I now have to set up a link between the two switches to make this really work, thank to the uplink ports and DAC cables.

So I am asking question : with such a simple setup (switch configurations are the same, except managment IP and name), do I have any benefit in setting up a virtual chassis for these two switches ? It is interrsting for my culture, but appart that ?

Thanks for any kind of explanation.

Regards

VLANs

$
0
0

Hi experts,

 

I am a bit confused regarding the below scenario, any input from you guys would be greatly appreciated. 

 

EX2200(1) ------------- EX2200(2)

 

Two EX series switches connected via an aggregated interface ae0 .(ge-0-0-0 and ge-0/0/1 on both sides)

 

I configure switch (1) ae0 port mode trunk and vlan member is VLAN 20. 

unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members VLAN20;

 

On the Switch(2), let's assume all ports except ge-0/0/0 and ge-0/0/1 are access ports and connecting to end devices. 

 

What happens if only configure port-mode and not assign any VLANs?

unit 0 {
family ethernet-switching {
port-mode trunk;

 

No VLAN configs at all on the Switch (2)

 

Can someone please explain to me what is the default behavior in terms of default vlan and native vlan on switch (2)?

 

Thanks

 

 

 

 

 

 

 

Enabling Proxy Arp

$
0
0

Coming from Cisco, proxy arp is enabled by default on switches.  I understand that on juniper switches (EX4300/4600) proxy arp is NOT enabled by default.  My question is, does proxy arp need to be enabled per interface or can it be enabled globaly on juniper switches?

I2C read from EEPROM device 0x51 failed

$
0
0

Platform: EX8216

 

Code: 15.1R6-S2.1

 

Description:

Master and Backup Routing-Engines is not fetching any outputs.

Customer performed format installation on both the REs.

 

 

During the boot process, chassis is recording below logs:

 

fdisk: invalid fdisk partition table found

 

Firmware Version: --- 03.04.00 ---

CPLD/FPGA image versions on the board:

        GCBC FPGA = 05.04 | BTCPLD = 07

USB:   scanning bus for devices... 2 USB Device(s) found

       scanning bus for storage devices... 1 Storage Device(s) found

I2C read from EEPROM device 0x51 failed.

I2C read from EEPROM device 0x51 failed.

I2C read from EEPROM device 0x51 failed.

I2C read from EEPROM device 0x51 failed.

 

I2C read from EEPROM device 0x51 failed.

 

Is the I2C read is failing for the hard disk ?

 

Expectation:

 

I would like to learn on how to find which part of the chassis is 0X51.

 

From chassisd logs,  I could see FPC0 and FPC15 online request is being rejected continuously.

 

Mar  8 06:59:00  socket = 36

Mar  8 06:59:01  <==Rcv FPC 0 FPC_READY, pipe 0x0x2556c00, reconnect:0, fpc_state:3, transition:2 rec_progress:0 fru_error:0, reason:0, issu_rec:0

Mar  8 06:59:01  LCC connection not online: Rejecting FPC online request

 

Mar  8 06:58:59  socket = 36

Mar  8 06:59:00  <==Rcv FPC 15 FPC_READY, pipe 0x0x2556d00, reconnect:0, fpc_state:3, transition:2 rec_progress:0 fru_error:0, reason:0, issu_rec:0

Mar  8 06:59:00  LCC connection not online: Rejecting FPC online request

 

Thanks in advance!

Device on Network Getting DHCP When Statically Configured on Separate VLAN

$
0
0

Greetings, 

We've been seeing some very strange behavior with some devices on our network.  We have devices that are statically configured on a specific subnet.  Yet, these particular devices are being mysteriously assigned DHCP from a different subnet.  This behaviour just started happening a few days ago.  Clearly, this simply shouldn't be happening.  First of all, these devices are supposed to be statically configured, second, they're on a subnet that is NOT configured for DHCP.  Third, the DHCP leases they're getting are from a separate subnet, which means that somehow DHCP request packets are crossing subnets which makes no sense.  We have a network where there are Juniper EX-2200s at the access layer.  One of these switches may have been damaged by a power surge.  Does anybody have any idea about this?  

Shutdown EX9204

$
0
0

Does anyone know the correct syntax to shut down an EX9204 running JUNOS 17? Documented commands do not work:

 

request system power-off: doesn't exist  (are you ^#%&* kidding me?)

request system halt: doesn't exist

request system reboot power-off fpc: reboots the system

 

That I have to ask this on the forum is either embarassing for me or for Juniper, I'm not sure which.

 

--Paul

 

IGMP-snooping Question

$
0
0

I need a bit of assistance here.

 

I have the following situation.

 

switch-1 with multicast sources attached.  this is not my switch and I have no operational/config visability of it.  This has igmp-snooping enabled.

 

I then have a second switch-2.  This is connected to switch-1.

This switch-2 has recievers that want to recieve sources from switch-1 and also from locally attached sources.

 

I have enabled igmp-snooping on switch-2 on the relevant vlan and set the link facing switch-1 as a multicast-router.

the recievers on switch-2 are all working fine but I am seeing all the MCAST traffic from the sources on switch-2 being pushed over the link to switch-1.

 

I had not expected that.  I as under the impression that this would only happen if switch-1 registered an interest in recieving the traffic.

a packet capture on the inter switch link shows an IGMPv2 query to all mcast routers 224.0.0.1 coming in from switch-1.

 

Is this packet what is triggering the traffic push?

 

thank you

 

 


EX2200 buffer overflows leading to dropped packets?

$
0
0

Hi all,

Trying to debug a problem with dropped packets from our firewall cluster; the cluster members are both connected to an EX2200 switch. When I look at the output of show interfaces <int> extensive on one of the firewall ints, I see the following sort of drops:

Egress queues: 8 supported, 4 in use
  Queue counters:       Queued packets  Transmitted packets      Dropped packets
    0 best-effort                    0           9868942044              9784947
    1 assured-forw                   0                    0                    0
    5 expedited-fo                   0                    0                    0
    7 network-cont                   0              4261145                    0

 Then I looked at the output of show interfaces queue <int>, and saw this output:

Egress queues: 8 supported, 4 in use
Queue: 0, Forwarding classes: best-effort
  Queued:
  Transmitted:
    Packets              :            9872164091
    Bytes                :         9429934422345
    Tail-dropped packets :               9790369
    RL-dropped packets   :                     0
    RL-dropped bytes     :                     0
Queue: 1, Forwarding classes: assured-forwarding
  Queued:
  Transmitted:
    Packets              :                     0
    Bytes                :                     0
    Tail-dropped packets :                     0
    RL-dropped packets   :                     0
    RL-dropped bytes     :                     0
Queue: 5, Forwarding classes: expedited-forwarding
  Queued:
  Transmitted:
    Packets              :                     0
    Bytes                :                     0
    Tail-dropped packets :                     0
    RL-dropped packets   :                     0
    RL-dropped bytes     :                     0
Queue: 7, Forwarding classes: network-control
  Queued:
  Transmitted:
    Packets              :               4261833
    Bytes                :             348050796
    Tail-dropped packets :                     0
    RL-dropped packets   :                     0
    RL-dropped bytes     :                     0

So in looking up the cause of "Tail-dropped packets", the Juniper tech article said that it was most likely the result of a packet buffer overflow. My question is, what kind of buffers do the EX2200 have, are they shared between port groups, and can an EX2200 sustain line-rate 1G/sec flows or not? (All the input and output NICs from the firewall are 1G)

TLSmiley Very HappyR - experiencing dropped packets on an interface, suspect buffer overflows, how to fix?

dhcp snooping in MX

$
0
0

For the life of me, I am unable to get dhcp snooping to work on a juniper MX 480.   We are using flexible-vlan-tagging and bridge-domains. I have tried setting one port to trusted, and another to untrusted, both to untrusted... and I already know that "trunk" ports are trusted by default and "access" ports are untrusted by default.  However, this seems to not matter on this setup. no matter which settings i enable (arp-inspection, option 82...) the command "show dhcp-security binding" is blank and dhcp continues to work. I need it to NOT work... per dhcp-snooping policy...
I will point out we are using an external dhcp server, not the server integrated into the juniper MX.
Is this a limitation of an MX? Has anyone attempted to use dhcp-security features on an MX?

LAG Issue between Juniper EX2200-C and Cisco 3560 Layer 2 loop

$
0
0

Having some issues with a very simple Lab scenario between an EX2200-C and a Cat 3560. Both devices are basically in default configuration. The Juniper has the configuration listed below and the topology is listed below that. My issue is that when I have the Catalyst with no LAG/Etherchannel configuration I end up getting a Layer 2 loop. It seems that the member interfaces on the Juniper are still forwarding traffic even though the Aggregated interface is down. I'm used to seeing the Cisco devices put the interfaces into an individual state and keep them running in STP to prevent loops.

 

Is this behavior normal?

 

----
Notes 1: This is a lab test environment
Notes 2: You shouldn't have one end not configured for LAG but this is a test to see what happens in that case
Notes 3: I'm trying to simulate the scenario where one party provisions a LAG before the other
EX2200-C is running: 12.3R12 ############################################################################ Spanning tree interface parameters for instance 0 Interface Port ID Designated Designated Port State Role port ID bridge ID Cost ge-0/1/1.0 128:562 128:562 32768.3c61046021c1 20000 FWD DESG {master:0} ############################################################################ root> show configuration chassis aggregated-devices { ethernet { device-count 1; } } root# show interfaces ge-0/0/0 ether-options { speed { 100m; } 802.3ad ae0; } root# show interfaces ge-0/0/01 ether-options { speed { 100m; } 802.3ad ae0; } root# show interfaces ae0 description "Link to DSW1"; aggregated-ether-options { lacp { active; } } unit 0 { family ethernet-switching; } ############################################################################ LAG +--+ | | +---------------------------------------------+ |---------------------------------------------| || | | || || +--+ || || || ge-0/0/1||ge-0/0/1 ||f0/1 +--------------+ +--------------+ | | | | | EX-2200C |ge-0/1/1 g0/1| c3560 | | +-------------------------+ | | | | | +--------------+ +--------------+   
#############################################################################

 

What does the * aka asterisk symbol mean on a virtual chassis ?

$
0
0

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 

Provide a static DHCP reservation with no router information

$
0
0

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!

Broadcast storm, loop, flood how to find from where the dissasters camming?

$
0
0

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?

SOLVED: DHCP server assigning addresses from wrong pool

$
0
0

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


QFX5100 interface drops

$
0
0

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!

Extend Existing Network Without Adding Switches to Virtual Chassis

$
0
0

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.

Ex3300 Virtual Chassis preprovisioning issue.

$
0
0

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

Firewall filters: "Internet-only" for a VLAN

$
0
0

Hi there,

 

I like to take my first steps into the world of firewall filtering on EX3300 switches, but the more I read the more I'm getting confused! :-)

My first project is: From vlan123 everything should be forbidden except "going to the internet" and ICMP traffic for monitoring purposes.

 

This is my first try. I didn't test it yet, because that's only possible on saturday's during "maintenance time".

 

firewall {
	family inet
		filter vlan123-filters
			term allow-internet {
				from {
					protocol [ tcp udp ];
					port [ 53 80 443 ];
				}
				then accept;
			term allow-icmp {
				from {
					protocol icmp:
				}
				then accept;
			}
	vlans {
		vlan123 {
			filter {
				input vlan123-filters;
				output vlan123-filters;
			}
		}
	}
}

 

What do you think about that? I would be very glad about comments so I can give it a try tomorrow!

 

Thanks a lot and many greets

Stephan

EX3300 Number of LAG limit

$
0
0

Hello,

I have a set of 4 EX3300 devices setup as a Virtual-Chassis.

I need to configure 40 LAG on it but I read in the documentation that EX3300 only support a maximum of 32 LAG.

However, the cli allows up to 111 LAG in the configuration (which is the LAG limit for EX4200).

So I am wondering if it is safe to configure more than 32 LAG on a EX3300 Virtual Chassis or if the documentation is just not up-to-date : https://www.juniper.net/documentation/en_US/junos/topics/concept/interfaces-lag-overview.html

 

Does anyone have any information or experience with more than 32 LAG on EX3300 ?

Thanks,

pierre.

Viewing all 2326 articles
Browse latest View live


Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>