Junos OS

Hello all,

I just enabled virtual-chassis between my two qfx5100-48s-6q swithces and I am seeing some odd behavior. I am not able to see the backup linecard ports with the command "show interface terse" but I am able to set additional interfaces and then commit succesfully. As a test, I added interfaces xe-1/0/25 , xe-2/0/25 and xe-3/0/25 and commited succesfully. Is that expected behavior when I only have two switches? Furthemore, the new interfaces I created do not shop up with the interface terse command but they do appear in the running config.

{master:0}[edit]
atetu@emp-cle.core-01.qfx5100# set interfaces xe-2/0/25 description TEST

{master:0}[edit]
atetu@emp-cle.core-01.qfx5100# set interfaces xe-3/0/25 description TEST

{master:0}[edit]
atetu@emp-cle.core-01.qfx5100# commit
fpc0:
configuration check succeeds
fpc1:
commit complete
fpc0:
commit complete

I attached a file with the output from show virtual-chassis / vc-port statistics extensive and the output looks correct.

Thanks in advance,

-AT

Attachment(s)

vc output.txt   10 KB 1 version

Hi Adrian,

Looking at the outputs attached I see that you have 2 members on the stack, however you are configuring following interfaces,

{master:0}[edit]
atetu@emp-cle.core-01.qfx5100# set interfaces xe-2/0/25 description TEST
{master:0}[edit]
atetu@emp-cle.core-01.qfx5100# set interfaces xe-3/0/25 description TEST

These will not show because the numbering used is based on members 2 and 3 that don't exist, the validation of the configuraiton will be depending on the version you are using, maybe a code will allow you to commit and other code will not.

Can you plesa share the output of >show chassis hardware to confirm what interfaces are configurable

Regards,

Jeffry Rivera

Hi Jeffry,

Thanks for your reply! I will get the additional vc output in the morning but I enabled ports xe-2/0/25 & xe-3/0/25 just to see if it works. Your reply answered why the unit accepted the config and commit. I tried doing "set interface xe-?" and xe-1/0/x was not an option, just xe-0/0/x. After configuring port  xe-1/0/25,  the output appears in show config but not in interface terse.

et-0/0/48 {
unit 0 {
family inet;
}
}
et-0/0/50 {
description "VC-PORT 1 of 2";
}
et-0/0/51 {
description "VC-PORT 2 of 2";
}
xe-1/0/25 {
unit 0 {
family inet;
}

Thanks,

-AT

Hi AdrianT04,

Greetings, regarding the non-existent interfaces showing up in the configuration file, is expected, you have a range from 0 to 9 FPC's since you are using a standard VC set up, if you go above that you will see an error message like this : error: fpc value outside range, what is not ok is not being able to see xe-1/0/25 using the show interfaces terse  

Can you share the output from the following commands:

>show chassis hardware
>show configuration chassis

Do you have an optic inserted or a DAC cable in port xe-1/0/25? if no, please insert one, if yes do you see any lights?

Regards,
Lil Dexx
JNCIE-ENT#863, 3X JNCIP-[SP-ENT-DC], 4X JNCIA [cloud-DevOps-Junos-Design], Champions Ingenius, SSYB

If this solves your problem, please mark this post as "Accepted Solution" so we can help others too \:)/

Hi LilDexx,

Thanks for your reply! I do not have remote access to the unit yet but I will get the additional vc output in the morning. I enabled xe-1/0/25 just to see if it works. I am using two DAC cables in ports 50 and 51 on both units. I tried doing "set interface xe-?" and xe-1/0/x was not an option, just xe-0/0/x.

Thanks,

-AT

Hi LilDexx,

I attached the show chassis hardware and config output. I plugged a fiber module into port xe-1/0/25 and port shows up now in the interface terse output. I connected another fiber module into port xe-1/0/29 without any sort of configuration and that port shows up as well now. Can you please confirm if everything looks alright? 

--terse snippet--

ge-0/0/47.0 up up inet 10.10.100.51/24
pfe-1/0/0 up up
pfe-1/0/0.16383 up up inet
inet6
pfh-1/0/0 up up
pfh-1/0/0.16383 up up inet
xe-1/0/25 up down
xe-1/0/25.0 up down inet
xe-1/0/29 up down
xe-1/0/29.16386 up down

Thanks,

-AT

Attachment(s)

chassis hardware.txt   2 KB 1 version

Hey AdrianT04,

Glad to hear that, it means that the chassisd was able to recognize the interface as part as the hardware inventory, nevertheless, I am not seeing the optic in the show chassis hardware, can you do a physical loop with those 2 ports and check the following directly from the PFE :

>start shell pfe network fpc1
PFEM0(vty)#show sfp list ---->you should see the optics listed 
PFEM0(vty)#show sfp <Index> info

From CLI

show interfaces diagnostics optics xe-1/0/25
show interfaces diagnostics optics xe-1/0/29

Regards,
Lil Dexx
JNCIE-ENT#863, 3X JNCIP-[SP-ENT-DC], 4X JNCIA [cloud-DevOps-Junos-Design], Champions Ingenius, SSYB

If this solves your problem, please mark this post as "Accepted Solution" so we can help others too \:)/

Hi LilDexx,

I think I copied the show chassis hardware output before I inserted the SFPs. I believe everthing looks good at the moment.

FPC 1 REV 16 650-064380 TA3717230636 QFX5100-48S-6Q
CPU BUILTIN BUILTIN FPC CPU
PIC 0 BUILTIN BUILTIN 48x10G-6x40G
Xcvr 25 REV 01 740-031981 G1905045305 SFP+-10G-LR
Xcvr 29 REV 01 740-031981 G1905045306 SFP+-10G-LR
Xcvr 50 REV 01 740-038624 G1807174757-2 QSFP+-40G-CU1M
Xcvr 51 REV 01 740-038624 G1807174759-1 QSFP+-40G-CU1M
Power Supply 0 REV 04 740-041741 1GA27112940 JPSU-650W-AC-AFO
Power Supply 1 REV 04 740-041741 1GA27113506 JPSU-650W-AC-AFO
Fan Tray 0 QFX5100 Fan Tray 0, Front to Back Airflow - AFO
Fan Tray 1 QFX5100 Fan Tray 1, Front to Back Airflow - AFO
Fan Tray 2 QFX5100 Fan Tray 2, Front to Back Airflow - AFO
Fan Tray 3 QFX5100 Fan Tray 3, Front to Back Airflow - AFO
Fan Tray 4 QFX5100 Fan Tray 4, Front to Back Airflow - AFO

atetu@emp-cle.core-01.qfx5100> show interfaces diagnostics optics xe-1/0/25
Physical interface: xe-1/0/25
Laser bias current : 35.986 mA
Laser output power : 0.7640 mW / -1.17 dBm
Module temperature : 23 degrees C / 73 degrees F
Module voltage : 3.3010 V
Receiver signal average optical power : 0.0001 mW / -40.00 dBm

{master:0}
atetu@emp-cle.core-01.qfx5100> show system alarms
1 alarms currently active
Alarm time Class Description
2020-01-31 10:45:08 EST Minor Rescue configuration is not set

-AT

AdrianT04,

Ohh... Great! that makes sense now, so now with all authority and doubtlessly I can confirm that everything is working like a charm.

You have my blessing Sir, enjoy Junos! 

If this solves your problem, please mark this post as "Accepted Solution" so we can help others too \:)/

Regards,
Lil Dexx
JNCIE-ENT#863, 3X JNCIP-[SP-ENT-DC], 4X JNCIA [cloud-DevOps-Junos-Design], Champions Ingenius, SSYB

Thank you very much for your prompt replies and assitance on this LilDexx!

Best regards,

-Adrian