[j-nsp] Recommended firmware for QFX5100-48T
dale.shaw+j-nsp at gmail.com
Mon Oct 10 16:34:35 EDT 2016
On 11 Oct 2016 6:23 AM, "Graham Brown" <juniper-nsp at grahambrown.info> wrote:
> Hi Paul,
> Correct, just use 'replace pattern xe-0/0/0 with ge-0/0/0' etc and you
> should be fine.
I don't think that's how it works on qfx5100-48**T**
It's more like copper based EX, where the interfaces are configured as
ge-x/x/x even if they're plugged into something capable of only 10 or
I seem to recall that there is a trick to making it work that involves
autoneg but I'm currently using a tiny screen and an imaginary keyboard so
digging up the details isn't possible right now.
I'm certain that JTAC could help but I'll try to find something when I'm
> On 11 October 2016 at 07:05, Paul S. <contact at winterei.se> wrote:
> > Hi Joel,
> > Thanks for replying.
> > What are the steps to configure the ports as "ge." Do I just get rid of
> > from the config and replace it with ge for that port, that's all?
> > On 10/11/2016 12:21 AM, joel jaeggli wrote:
> >> On 10/10/16 7:34 AM, Paul S. wrote:
> >>> Hi folks,
> >>> Are everyone running the JTAC recommended 14.1X53-D35.3 or have you
> >>> found better stability at some newer revision?
> >>> My problem is that the "tri state" 10g ports (copper) don't seem to
> >>> want to run at anything less than 10g. It links up when connected to a
> >>> 1g device, but still claims that the port is operating in 10g mode.
> >>> The biggest issue I have is that if I assign a /30 to the p2p
> >>> interfaces (between the qfx and any copper 1g device), my p2p latency
> >>> is somewhere from 10 to 40ms.
> >>> I asked around to see if there's any way to force the ports into 1g
> >>> mode, but the "speed" knob is missing. I deliberately turned on
> >>> auto-negotiation, does not seem to help.
> >>> 802.3ad LAGs created using any of these links also claim to have
> >>> speeds of 20g/40g when there's in reality only 4g of capacity.
> >>> Can someone hit me with a clue stick? Thanks!
> >> I presume that you're specifing the port config as ge-0/0/foo rather
> >> than xe-0/0/foo
> >> joel@ show interfaces ge-0/0/46
> >> Physical interface: ge-0/0/46, Enabled, Physical link is Up
> >> Interface index: 701, SNMP ifIndex: 616
> >> Description:
> >> Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps, 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
> >> Current address:
> >> Last flapped : 2016-08-26 03:31:56 UTC (6w3d 19:46 ago)
> >> Input rate : 0 bps (0 pps)
> >> Output rate : 0 bps (0 pps)
> >> Active alarms : None
> >> Active defects : None
> >> Interface transmit statistics: Disabled
> >> Logical interface ge-0/0/46.0 (Index 563) (SNMP ifIndex 617)
> >> Flags: SNMP-Traps 0x4004000 Encapsulation: ENET2
> >> Input packets : 146287
> >> Output packets: 292513
> >> Protocol inet, MTU: 1500
> >> Flags: Sendbcast-pkt-to-re
> >> Addresses, Flags: Is-Preferred Is-Primary
> >> Destination:
> >> joel@> show chassis hardware
> >> Hardware inventory:
> >> Item Version Part number Serial number Description
> >> Chassis QFX5100-48S-6Q
> >> Pseudo CB 0
> >> Routing Engine 0 BUILTIN BUILTIN QFX Routing
> >> Engine
> >> FPC 0 REV 05
> >> Xcvr 46 NON-JNPR SFP-T
> >> joel@> show version
> >> fpc0:
> >> ------------------------------------------------------------
> >> --------------
> >> Hostname:
> >> Model: qfx5100-48s-6q
> >> JUNOS Base OS Software Suite [13.2X51-D38]
More information about the juniper-nsp