Hi Arix,

You also may want to check documentation about SFPs and QSFPs capabilities, there is a wide number of options.

Based on the output you could use 4x 100gig links (or its variations for breakout connections) and 40x 10gig links. check out the different transceiver modules supported. they will be listed in the proper QFX datasheet.

For example, for a QFX5k

Determining Interface Support for the QFX5100 Device

https://www.juniper.net/documentation/en_US/release-independent/junos/topics/reference/specifications/interface-qfx5100-support.html

QFX5100 ETHERNET SWITCH

https://www.juniper.net/assets/us/en/local/pdf/datasheets/1000480-en.pdf

hope it helps.

cheers,

Benjamin

Hi Reload,

the QFX will be able to run from one power module, these are hot swapable, as long as you keep one power unit the switch will not go offline.

Hope it helps,

Benjamin

hi There, 

You might want to check pathfinder in case you need more transceiver data.

https://apps.juniper.net/hct/category/#catKey=100001&modelType=10%20Gigabit%20Ethernet&pf=QFX%20Series 

For that model it support 2-10km 

https://apps.juniper.net/hct/model/?component=QFX-SFP-10GE-LR&catKey=100001&cat=Transceivers

If this solves your problem, please mark this post as "Accepted Solution".

If you think that my answer was helpful, please spend some Kudos.

Regards,

Franky

 hi all,

Thanks for reply..

How can be understood about a transciver module on qfx device receives low optic signal or sending low optical signal?

Secondly how can be listed the ports that haven't got any transciver module on them? There is  4 qfx devices in VC.

Thanks

Ar

Thanks All for being here to help .. 

I'm sure that this SKU last order was on 25/6/2020 - as per juniper website ..

Also for your information this was very cost effiective in case of large numbers of 10 G  fiber connections ..

Hi.

I have a completly new ex3400 VC setup where I have issues to commit a configuration with rstp edge configuration set to a interface range.

The stack consists of 7 x ex3400-48T running JunOS 18.2R3-S4.1.

If I just take one random interface and issue the command set protocol rstp interface ge-6/0/1 edge and do a commit, the configuration is commited. But if instead do set protocol rstp interface AccessPort-BaseConfig edge and do a commit I get this error message:

error: Unique id allocation failed for '//var/etc/stp_port.id' - no more free ids
error: Failed to allocate unique port-id for xSTP - likely due to exceeding the number of user configurable STP ports which is 4095
error: foreign file propagation (ffp) failed

The interface range configuration looks like this:

interfaces {
    interface-range AccessPort-BaseConfig {
        member-range ge-0/0/0 to ge-6/0/47;
        unit 0 {
            family ethernet-switching {
                interface-mode access;
                storm-control default;
            }
        }
    }

This is working on at least two other setups running the smae JunOS version.I have tried to reboot the stack completly, with the same result.

Any ideas?

Best regards,
Johan Christensson

Hi Johan,

This seem to be a known issue, you can find it below,

https://prsearch.juniper.net/InfoCenter/index?page=prcontent&id=PR1366903

The best way to proceed will be changing the ranges to a minor range as the example provided on the PR,

set interfaces interface-range  jtac-test1 member-range ge-0/0/0 to ge-6/0/47
set interfaces interface-range jtac-test1 member-range ge-7/0/0 to ge-8/0/47
set interfaces interface-range jtac-test2 member-range ge-7/0/0 to ge-8/0/47
set interfaces interface-range jtac-test2 member-range ge-0/0/0 to ge-6/0/47

Pleas try the workaround to double check.

If this worked for you please mark as "Accepted Solution" so we can help others too

Best Regards,

Jeff

Hi Johan,

Can you please try setting the member range as:

set interfaces interface-range AccessPort-BaseConfig member-range ge-0/0/0 to ge-0/0/47

set interfaces interface-range AccessPort-BaseConfig member-range ge-1/0/0 to ge-1/0/47

set interfaces interface-range AccessPort-BaseConfig member-range ge-2/0/0 to ge-2/0/47

set interfaces interface-range AccessPort-BaseConfig member-range ge-3/0/0 to ge-3/0/47

set interfaces interface-range AccessPort-BaseConfig member-range ge-4/0/0 to ge-4/0/47

set interfaces interface-range AccessPort-BaseConfig member-range ge-5/0/0 to ge-5/0/47

set interfaces interface-range AccessPort-BaseConfig member-range ge-6/0/0 to ge-6/0/47

Also, just to double confirm on the PR mentioned, what is the output for:

show interfaces | display set | display inheritance | count

Switch: Ex2300-24P

Version: 18.1R3.3

I'm having issue with web-management interface. If I only have https enabled:

web-management {
            http;
            https {
                system-generated-certificate;
                interface irb.10;
            }
        }

I get err_too_many_redirects error. If I enable http, that works but its not secure.

Also, in one of the switch I'm getting Phone Home Client on the web interface. I saw following in its conf:

system {
    ....
    phone-home {
        server https://redirect.juniper.net;
        rfc-compliant;
    }
}

I can't delete phone-home, it doesn't give me that option:

root@SW-ACC-D01# delete system p
                                    ^
'p' is ambiguous.
Possible completions:
+ personality-file-list-of-directories  List of Optional directories for personality-tarball of device> pic-console-authentication  Authentication for the console port on PICs> ports                Craft interface RS-232 ports> processes            Process control> proxy                Proxy information for the router
{master:0}[edit]
root@SW-RCP-ACC-D01# delete system p

I tried deactivate, but same issue. Please bear in mind that I'm remoted in through SSH.

How do I get rid of this and get back to Juniper Web Device Manager ?

Hi Johan,

I believe separating the member ranges to work. This will ensure that the pool size is reduced. You can try splitting up the ports in the below range,

 ge-0/0/0 to ge-6/0/47;

 you can split it up and check if that helps.

Please mark Accepted Solution if this helps you solve your query. Kudos are always appreciated!

1. show chassis hardware

2. yes

3. show interfaces diagnostics optics <interface-name>

Hi all.

As this is my first post in this forum, don't judge me too hard if I am writing in the wrong forum, getting anything wrong or being inaccurate.

My question is about Junos and support for IEEE 1905.1?

As a part of my training with Juniper equipment I'm using a rather old EX2200-C-12T-2G running version 12.3R12.4 as my main switch in my home network. The switch was zeroized and is running a basic configuration. The network in a flat layer 2 without any firewalls or vlans.

In case of narrowing down my case I say that I have two TP-LINK Deco M5 units connect to my network. This units are capable of making both a wireless and wired connection for backhaul. (More information on this page: https://www.tp-link.com/us/support/faq/1794/)

I would like to connect my units to port ge-0/0/5 and ge-0/1/0 with this configured:

unit 0 {
family ethernet-switching;
}

but if I do, it will put the Deco units in a network loop and become quite unstable.  But in my case, it looks like my switch don't forward packets based on IEEE 1905.1 protocol? Therefor I have to use wireless connection as backhaul but that is more unreliable and with a lower bandwidth.

I used to have an unmanaged Netgear switch and back then there were no issues but after replacing it with a Juniper unit I'm unable to use connect the Deco units to my wired network.

Hopefully there are someone in this forum that has any knowledge about IEEE 1905.1 and Junos and maybe have a suggestion? Can "Layer 2 Protocol Tunnelling" be a path to follow? If so, how do I implement it?

Thanks in advance and best regards,

Terje

Hi all and thanks for the quick reply.

After that I changed the interface-range to look like the below, the configuration was commited.

interfaces {
    interface-range AccessPort-BaseConfig {
        member-range ge-0/0/0 to ge-0/0/47;
        member-range ge-1/0/0 to ge-1/0/47;
        member-range ge-2/0/0 to ge-2/0/47;
        member-range ge-3/0/0 to ge-3/0/47;
        member-range ge-4/0/0 to ge-4/0/47;
        member-range ge-5/0/0 to ge-5/0/47;
        member-range ge-6/0/0 to ge-6/0/47;
        unit 0 {
            family ethernet-switching {
                interface-mode access;
                storm-control default;
            }
        }
    }

We are using a QFX5100 switch and multiple servers are connected to it. Each server has two connections to the switch the first connection is working fine, the second connection does not the switch shows that the link state is always down. In fact, traffic arrives at the physical interface of the switch, and the link negotiation was complete.

The logical interface is always down:

uniscon@DCUA02-SW01> show interfaces xe-0/0/20 terse 
# interface connected to a server X (eth1)
Interface               Admin Link Proto    Local                 Remote
xe-0/0/20               up    up
xe-0/0/20.0             up    up   eth-switch

uniscon@DCUA02-SW01> show interfaces xe-0/0/19 terse    
# interface connected to a server X (eth0)
Interface               Admin Link Proto    Local                 Remote
xe-0/0/19               up    down
xe-0/0/19.0             up    down eth-switch

here are the non-working interface details:

show interfaces xe-0/0/19 extensive    
Physical interface: xe-0/0/19, Enabled, Physical link is Up
  Interface index: 672, SNMP ifIndex: 533, Generation: 163
  Description: eth0 on appsrv5
  Link-level type: Ethernet, MTU: 9188, LAN-PHY mode, Link-mode: Auto, Speed: 10 Gbps, BPDU Error: None, Loop Detect PDU Error: None, Ethernet-Switching Error: None,
  MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled, Auto-negotiation: Enabled, Remote fault: Offline, Media type: Copper
  Device flags   : Present Running
  Interface flags: Link-Layer-Down 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: 44:f4:77:b5:4a:96, Hardware address: 44:f4:77:b5:4a:96
  Last flapped   : 2020-07-01 16:35:39 CEST (17:59:55 ago)
  Statistics last cleared: 2020-07-01 14:26:51 CEST (20:08:43 ago)
  Traffic statistics:
   Input  bytes  :              1005534                    0 bps
   Output bytes  :                    0                    0 bps
   Input  packets:                 2959                    0 pps
   Output packets:                    0                    0 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: 16, Errors: 0, Drops: 0, 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, 5 in use
  Queue counters:       Queued packets  Transmitted packets      Dropped packets
    0                                0                    0                    0
    3                                0                    0                    0
    4                                0                    0                    0
    7                                0                    0                    0
    8                                0                    0                    0
  Queue number:         Mapped forwarding classes
    0                   best-effort
    3                   fcoe
    4                   no-loss
    7                   network-control
    8                   mcast
  Active alarms  : None
  Active defects : None
  PCS statistics                      Seconds
    Bit errors                             0
    Errored blocks                         0
  Ethernet FEC statistics              Errors
    FEC Corrected Errors                    0
    FEC Uncorrected Errors                  0
    FEC Corrected Errors Rate               0
    FEC Uncorrected Errors Rate             0
  MAC statistics:                      Receive         Transmit
    Total octets                       1005534                0
    Total packets                         2959                0
    Unicast packets                          0                0
    Broadcast packets                     2890                0
    Multicast packets                       69                0
    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                       0
    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: Symmetric/Asymmetric, Remote fault: OK, Link partner Speed: 10 Gbps
    Local resolution:
        Flow control: None, Flow control tx: Disabled, Flow control rx: Disabled, Remote fault: Link OK
  Packet Forwarding Engine configuration:
    Destination slot: 0 (0x00)
  CoS information:
    Direction : Output
    CoS transmit queue               Bandwidth               Buffer Priority   Limit
                              %            bps     %           usec
    0 best-effort             5      500000000     5              0      low    none
    3 fcoe                   35     3500000000    35              0      low    none
    4 no-loss                35     3500000000    35              0      low    none
    7 network-control         5      500000000     5              0      low    none
    8 mcast                  20     2000000000    20              0      low    none
  Interface transmit statistics: Disabled

  Logical interface xe-0/0/19.0 (Index 579) (SNMP ifIndex 575) (Generation 194)
    Flags: Device-Down SNMP-Traps 0x24024000 Encapsulation: Ethernet-Bridge
    Traffic statistics:
     Input  bytes  :                    0
     Output bytes  :                    0
     Input  packets:                    0
     Output packets:                    0
    Local statistics:
     Input  bytes  :                    0
     Output bytes  :                    0
     Input  packets:                    0
     Output packets:                    0
    Transit statistics:
     Input  bytes  :                    0                    0 bps
     Output bytes  :                    0                    0 bps
     Input  packets:                    0                    0 pps
     Output packets:                    0                    0 pps
    Protocol eth-switch, MTU: 9188, Generation: 217, Route table: 5
      Input Filters: storage-dst

For comparison sake, here is the working interface that is connected to the server:

show interfaces xe-0/0/20 extensive    
Physical interface: xe-0/0/20, Enabled, Physical link is Up
  Interface index: 673, SNMP ifIndex: 534, Generation: 164
  Description: eth1 on appsrv5
  Link-level type: Ethernet, MTU: 9188, LAN-PHY mode, Link-mode: Auto, Speed: 10 Gbps, BPDU Error: None, Loop Detect PDU Error: None, Ethernet-Switching Error: None,
  MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled, Auto-negotiation: Disabled, Remote fault: Offline, 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: 44:f4:77:b5:4a:97, Hardware address: 44:f4:77:b5:4a:97
  Last flapped   : 2020-07-01 11:50:55 CEST (22:44:58 ago)
  Statistics last cleared: Never
  Traffic statistics:
   Input  bytes  :            142019669                    0 bps
   Output bytes  :           4069747174                 4584 bps
   Input  packets:              1569096                    0 pps
   Output packets:              5075888                    1 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: 189, Errors: 0, Drops: 0, 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, 5 in use
  Queue counters:       Queued packets  Transmitted packets      Dropped packets
    0                          2108741              2108741                    0
    3                                0                    0                    0
    4                                0                    0                    0
    7                                0                    0                    0
    8                           262441               262441                    0
  Queue number:         Mapped forwarding classes
    0                   best-effort
    3                   fcoe
    4                   no-loss
    7                   network-control
    8                   mcast
  Active alarms  : None
  Active defects : None
  PCS statistics                      Seconds
    Bit errors                             0
    Errored blocks                         0
  Ethernet FEC statistics              Errors
    FEC Corrected Errors                    0
    FEC Uncorrected Errors                  0
    FEC Corrected Errors Rate               0
    FEC Uncorrected Errors Rate             0
  MAC statistics:                      Receive         Transmit
    Total octets                     142019669       4069726772
    Total packets                      1569096          5075849
    Unicast packets                    1521520          2461348
    Broadcast packets                    47370          2110717
    Multicast packets                      206           503784
    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                       0
    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: Symmetric/Asymmetric, Remote fault: OK, Link partner Speed: 10 Gbps
    Local resolution:
        Flow control: None, Flow control tx: Disabled, Flow control rx: Disabled, Remote fault: Link OK
  Packet Forwarding Engine configuration:
    Destination slot: 0 (0x00)
  CoS information:
    Direction : Output
    CoS transmit queue               Bandwidth               Buffer Priority   Limit
                              %            bps     %           usec
    0 best-effort             5      500000000     5              0      low    none
    3 fcoe                   35     3500000000    35              0      low    none
    4 no-loss                35     3500000000    35              0      low    none
    7 network-control         5      500000000     5              0      low    none
    8 mcast                  20     2000000000    20              0      low    none
  Interface transmit statistics: Disabled

  Logical interface xe-0/0/20.0 (Index 580) (SNMP ifIndex 576) (Generation 165)
    Flags: Up SNMP-Traps 0x24024000 Encapsulation: Ethernet-Bridge
    Traffic statistics:
     Input  bytes  :             25166180
     Output bytes  :                19934
     Input  packets:                42806
     Output packets:                   39
    Local statistics:
     Input  bytes  :             25166180
     Output bytes  :                19934
     Input  packets:                42806
     Output packets:                   39
    Transit statistics:
     Input  bytes  :                    0                    0 bps
     Output bytes  :                    0                    0 bps
     Input  packets:                    0                    0 pps
     Output packets:                    0                    0 pps
    Protocol eth-switch, MTU: 9188, Generation: 186, Route table: 5

Any help is appreciated 

Hi yassine_fadh1,

The below indicates that interface xe-0/0/19 is up but the link is down. Indicating the link is not up. It could be an issue on transit or an issue with the remote end connected to this specific interface. Please ensure both Admin and Link and UP.

uniscon@DCUA02-SW01> show interfaces xe-0/0/19 terse    
# interface connected to a server X (eth0)Interface               Admin Link Proto    Local                 Remote
xe-0/0/19               up    down
xe-0/0/19.0             up    down eth-switch

Also, you can see this alarm in the interface description for xe-0/0/19

show interfaces xe-0/0/19 extensive    
Physical interface: xe-0/0/19, Enabled, Physical link is Up
  Interface index: 672, SNMP ifIndex: 533, Generation: 163
  Description: eth0 on appsrv5
  Link-level type: Ethernet, MTU: 9188, LAN-PHY mode, Link-mode: Auto, Speed: 10 Gbps, BPDU Error: None, Loop Detect PDU Error: None, Ethernet-Switching Error: None,
  MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled, Auto-negotiation: Enabled, Remote fault: Offline, Media type: Copper
  Device flags   : Present Running
  Interface flags: Link-Layer-Down SNMP-Traps Internal: 0x4000

Please ensure the link is up and then everything should work fine.

Hope this helps

Please mark "Accepted Solution" if this helps you solve your query. Kudos are always appreciated!

Thank you for your reply, but this issue is on all servers :

# server N (eth1)
xe-0/0/9                up    down
xe-0/0/9.0              up    down eth-switch
# server N (eth0)
xe-0/0/10               up    up
xe-0/0/10.0             up    up   eth-switch
# server N+1 (eth1)
xe-0/0/11               up    down
xe-0/0/11.0             up    down eth-switch
# server N+1 (eth0)
xe-0/0/12               up    up
xe-0/0/12.0             up    up   eth-switch
# server N+2 (eth1)
xe-0/0/13               up    down
xe-0/0/13.0             up    down eth-switch
# server N+2 (eth0)
xe-0/0/14               up    up
xe-0/0/14.0             up    up   eth-switch
# server N+3 (eth1)
xe-0/0/15               up    down
xe-0/0/15.0             up    down eth-switch
# server N+3 (eth0)
xe-0/0/16               up    up
xe-0/0/16.0             up    up   eth-switch

xe-0/0/17               up    down
xe-0/0/17.0             up    down eth-switch
xe-0/0/18               up    up
xe-0/0/18.0             up    up   eth-switch
xe-0/0/19               up    down
xe-0/0/19.0             up    down eth-switch
xe-0/0/20               up    up
xe-0/0/20.0             up    up   eth-switch

Hi yassine_fadh1, 

Greetings, 

I see that there is an input filter in the output you shared for xe-0/0/19 whereas this isn't seen on xe-0/0/20.

I believe the input filter is blocking this traffic, could you confirm that for us ? Also, please check if there are any filter applied to this interface and the others as well and confirm if the same are applied/not on the other interface in the pair.

show interfaces xe-0/0/19 extensive ..
...
Input Filters: storage-dst

Hope this helps. 

Please mark "Accept as solution" if this answers your query. 

Kudos are appreciated too! 

Regards, 

Sharat Ainapur

Thank you for your reply,

I did that before but it did not help here is output after removing the filter

uniscon@DCUA02-SW01# run show configuration interfaces xe-0/0/19                                            
description "eth0 on appsrv5";
mtu 9188;
ether-options {
    auto-negotiation;
}
unit 0 {
    family ethernet-switching {
        interface-mode access;
        vlan {
            members Storage;
        }
    }
}

# commit confirmed will be rolled back in 9 minutes
{master:0}[edit]
uniscon@DCUA02-SW01# run show interfaces xe-0/0/19 terse            
Interface               Admin Link Proto    Local                 Remote
xe-0/0/19               up    down
xe-0/0/19.0             up    down eth-switch

# commit confirmed will be rolled back in 9 minutes

This looks like a physical issue.

If this is a duplex optic try flipping the two fibers inserted on one side reversing the transmit and receive connections.  I've seen issues where the pair gets flipping in the patch panel process across facilities or some cables are designed to do such a flip.

Also have a look at the optic details to see if there is a light or power level issue.

show interfaces diagnostics optics 

show interfaces diagnostics optics xe-0/0/19