Security Management

Hi everyone,

We are using NeDi as our network inventory system and im having issues with the EX3400 model.

When trying to list FPC modell description the virtual chassi only lists a singular modell on the EX3400 whilst EX3300 gives me information as POE,48T,48P and so on..

EX-3300:
show snmp mib walk 1.3.6.1.4.1.2636.3.1.8.1.6
jnxContentsDescr.1.1.0.0
jnxContentsDescr.2.1.1.0 = Power Supply: Power Supply 0 @ 0/0/*
jnxContentsDescr.2.2.1.0 = Power Supply: Power Supply 0 @ 1/0/*
jnxContentsDescr.2.3.1.0 = Power Supply: Power Supply 0 @ 2/0/*
jnxContentsDescr.2.4.1.0 = Power Supply: Power Supply 0 @ 3/0/*
jnxContentsDescr.2.5.1.0 = Power Supply: Power Supply 0 @ 4/0/*
jnxContentsDescr.4.1.1.1 = FAN: Fan 1 @ 0/0/0
jnxContentsDescr.4.1.1.2 = FAN: Fan 2 @ 0/0/1
jnxContentsDescr.4.2.1.1 = FAN: Fan 1 @ 1/0/0
jnxContentsDescr.4.2.1.2 = FAN: Fan 2 @ 1/0/1
jnxContentsDescr.4.3.1.1 = FAN: Fan 1 @ 2/0/0
jnxContentsDescr.4.3.1.2 = FAN: Fan 2 @ 2/0/1
jnxContentsDescr.4.4.1.1 = FAN: Fan 1 @ 3/0/0
jnxContentsDescr.4.4.1.2 = FAN: Fan 2 @ 3/0/1
jnxContentsDescr.4.5.1.1 = FAN: Fan 1 @ 4/0/0
jnxContentsDescr.4.5.1.2 = FAN: Fan 2 @ 4/0/1
jnxContentsDescr.7.1.0.0 = FPC: EX3300 48-Port @ 0/*/*
jnxContentsDescr.7.2.0.0 = FPC: EX3300 48-Port @ 1/*/*
jnxContentsDescr.7.3.0.0 = FPC: EX3300 48-Port POE+ @ 2/*/*
jnxContentsDescr.7.4.0.0 = FPC: EX3300 48-Port @ 3/*/*
jnxContentsDescr.7.5.0.0 = FPC: EX3300 48-Port @ 4/*/*
jnxContentsDescr.8.1.1.0 = PIC: 48x 10/100/1000 Base-T @ 0/0/*
jnxContentsDescr.8.1.2.0 = PIC: 4x GE/XE SFP+ @ 0/1/*
jnxContentsDescr.8.2.1.0 = PIC: 48x 10/100/1000 Base-T @ 1/0/*
jnxContentsDescr.8.2.2.0 = PIC: 4x GE/XE SFP+ @ 1/1/*
jnxContentsDescr.8.3.1.0 = PIC: 48x 10/100/1000 Base-T @ 2/0/*
jnxContentsDescr.8.3.2.0 = PIC: 4x GE/XE SFP+ @ 2/1/*
jnxContentsDescr.8.4.1.0 = PIC: 48x 10/100/1000 Base-T @ 3/0/*
jnxContentsDescr.8.4.2.0 = PIC: 4x GE/XE SFP+ @ 3/1/*
jnxContentsDescr.8.5.1.0 = PIC: 48x 10/100/1000 Base-T @ 4/0/*
jnxContentsDescr.8.5.2.0 = PIC: 4x GE/XE SFP+ @ 4/1/*
jnxContentsDescr.9.1.0.0 = Routing Engine 1
jnxContentsDescr.9.2.0.0 = Routing Engine 0

EX-3400: (Multiple 48T,48P and 24P in reality)
root@MAL-SW13> show snmp mib walk 1.3.6.1.4.1.2636.3.1.8.1.6
jnxContentsDescr.1.1.0.0
jnxContentsDescr.2.1.1.0 = Power Supply 0 @ 0/0/*
jnxContentsDescr.2.2.1.0 = Power Supply 0 @ 1/0/*
jnxContentsDescr.2.3.1.0 = Power Supply 0 @ 2/0/*
jnxContentsDescr.2.4.1.0 = Power Supply 0 @ 3/0/*
jnxContentsDescr.2.5.1.0 = Power Supply 0 @ 4/0/*
jnxContentsDescr.2.6.1.0 = Power Supply 0 @ 5/0/*
jnxContentsDescr.2.7.1.0 = Power Supply 0 @ 6/0/*
jnxContentsDescr.2.8.1.0 = Power Supply 0 @ 7/0/*
jnxContentsDescr.2.9.1.0 = Power Supply 0 @ 8/0/*
jnxContentsDescr.2.10.1.0 = Power Supply 0 @ 9/0/*
jnxContentsDescr.4.1.1.0 = Fan Tray 0 @ 0/0/*
jnxContentsDescr.4.1.2.0 = Fan Tray 1 @ 0/1/*
jnxContentsDescr.4.2.1.0 = Fan Tray 0 @ 1/0/*
jnxContentsDescr.4.2.2.0 = Fan Tray 1 @ 1/1/*
jnxContentsDescr.4.3.1.0 = Fan Tray 0 @ 2/0/*
jnxContentsDescr.4.3.2.0 = Fan Tray 1 @ 2/1/*
jnxContentsDescr.4.4.1.0 = Fan Tray 0 @ 3/0/*
jnxContentsDescr.4.4.2.0 = Fan Tray 1 @ 3/1/*
jnxContentsDescr.4.5.1.0 = Fan Tray 0 @ 4/0/*
jnxContentsDescr.4.5.2.0 = Fan Tray 1 @ 4/1/*
jnxContentsDescr.4.6.1.0 = Fan Tray 0 @ 5/0/*
jnxContentsDescr.4.6.2.0 = Fan Tray 1 @ 5/1/*
jnxContentsDescr.4.7.1.0 = Fan Tray 0 @ 6/0/*
jnxContentsDescr.4.7.2.0 = Fan Tray 1 @ 6/1/*
jnxContentsDescr.4.8.1.0 = Fan Tray 0 @ 7/0/*
jnxContentsDescr.4.8.2.0 = Fan Tray 1 @ 7/1/*
jnxContentsDescr.4.9.1.0 = Fan Tray 0 @ 8/0/*
jnxContentsDescr.4.9.2.0 = Fan Tray 1 @ 8/1/*
jnxContentsDescr.4.10.1.0 = Fan Tray 0 @ 9/0/*
jnxContentsDescr.4.10.2.0 = Fan Tray 1 @ 9/1/*
jnxContentsDescr.7.1.0.0 = FPC: EX3400-24P @ 0/*/*
jnxContentsDescr.7.2.0.0 = FPC: EX3400-24P @ 1/*/*
jnxContentsDescr.7.3.0.0 = FPC: EX3400-24P @ 2/*/*
jnxContentsDescr.7.4.0.0 = FPC: EX3400-24P @ 3/*/*
jnxContentsDescr.7.5.0.0 = FPC: EX3400-24P @ 4/*/*
jnxContentsDescr.7.6.0.0 = FPC: EX3400-24P @ 5/*/*
jnxContentsDescr.7.7.0.0 = FPC: EX3400-24P @ 6/*/*
jnxContentsDescr.7.8.0.0 = FPC: EX3400-24P @ 7/*/*
jnxContentsDescr.7.9.0.0 = FPC: EX3400-24P @ 8/*/*
jnxContentsDescr.7.10.0.0 = FPC: EX3400-24P @ 9/*/*
jnxContentsDescr.8.1.1.0 = PIC: 24x10/100/1000 Base-T @ 0/0/*
jnxContentsDescr.8.1.2.0 = PIC: 2x40G QSFP @ 0/1/*
jnxContentsDescr.8.1.3.0 = PIC: 4x10G SFP/SFP+ @ 0/2/*
jnxContentsDescr.8.2.1.0 = PIC: 24x10/100/1000 Base-T @ 1/0/*
jnxContentsDescr.8.2.2.0 = PIC: 2x40G QSFP @ 1/1/*
jnxContentsDescr.8.2.3.0 = PIC: 4x10G SFP/SFP+ @ 1/2/*
jnxContentsDescr.8.3.1.0 = PIC: 48x10/100/1000 Base-T @ 2/0/*
jnxContentsDescr.8.3.2.0 = PIC: 2x40G QSFP @ 2/1/*
jnxContentsDescr.8.3.3.0 = PIC: 4x10G SFP/SFP+ @ 2/2/*
jnxContentsDescr.8.4.1.0 = PIC: 48x10/100/1000 Base-T @ 3/0/*
jnxContentsDescr.8.4.2.0 = PIC: 2x40G QSFP @ 3/1/*
jnxContentsDescr.8.4.3.0 = PIC: 4x10G SFP/SFP+ @ 3/2/*
jnxContentsDescr.8.5.1.0 = PIC: 48x10/100/1000 Base-T @ 4/0/*
jnxContentsDescr.8.5.2.0 = PIC: 2x40G QSFP @ 4/1/*
jnxContentsDescr.8.5.3.0 = PIC: 4x10G SFP/SFP+ @ 4/2/*
jnxContentsDescr.8.6.1.0 = PIC: 48x10/100/1000 Base-T @ 5/0/*
jnxContentsDescr.8.6.2.0 = PIC: 2x40G QSFP @ 5/1/*
jnxContentsDescr.8.6.3.0 = PIC: 4x10G SFP/SFP+ @ 5/2/*
jnxContentsDescr.8.7.1.0 = PIC: 48x10/100/1000 Base-T @ 6/0/*
jnxContentsDescr.8.7.2.0 = PIC: 2x40G QSFP @ 6/1/*
jnxContentsDescr.8.7.3.0 = PIC: 4x10G SFP/SFP+ @ 6/2/*
jnxContentsDescr.8.8.1.0 = PIC: 48x10/100/1000 Base-T @ 7/0/*
jnxContentsDescr.8.8.2.0 = PIC: 2x40G QSFP @ 7/1/*
jnxContentsDescr.8.8.3.0 = PIC: 4x10G SFP/SFP+ @ 7/2/*
jnxContentsDescr.8.9.1.0 = PIC: 48x10/100/1000 Base-T @ 8/0/*
jnxContentsDescr.8.9.2.0 = PIC: 2x40G QSFP @ 8/1/*
jnxContentsDescr.8.9.3.0 = PIC: 4x10G SFP/SFP+ @ 8/2/*
jnxContentsDescr.8.10.1.0 = PIC: 48x10/100/1000 Base-T @ 9/0/*
jnxContentsDescr.8.10.2.0 = PIC: 2x40G QSFP @ 9/1/*
jnxContentsDescr.8.10.3.0 = PIC: 4x10G SFP/SFP+ @ 9/2/*
jnxContentsDescr.9.1.0.0 = Routing Engine 0
jnxContentsDescr.9.2.0.0 = Routing Engine 9

Any ideas to why this occurs? the OiD should be the same.

Same output with
show snmp mib walk jnxContentsDescr.7

Hi anf@tyrens.se, 

Greetings, 

Could you please check by executing this command?

show snmp mib walk jnxVirtualChassisMemberModel

show snmp mib walk jnxExVirtualChassis

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

Kudos are appreciated too! 

Regards, 

Sharat Ainapur

Oh terrific Sharat!

Thanks alot for this reply.

I tried to run show snmp mib walk 1.3 |grep 3400 but i guess it may have been to un specific to come across this as it only loaded "system".

Thank you again!

Hi Sharat,

This would work fine with other inventory systems i presume but as it tries to retrieve the serial nr values from the same hierachy from description OiD it fails when changing from slot to VC-member description..

Is there any KB-article about this issue present or bug report?

@sharatainapur

Hello anf@tyrens.se, 

Yes, you are right and even I was thinking about the same. 

Was checking through the documentation and there exists one for an MX series VC: https://www.juniper.net/documentation/en_US/junos/topics/reference/general/virtual-chassis-mx-series-slot-numbers-for-snmp.html

Could you please attach the output that you got for a better understanding?

I am checking for any known bug and also maybe a few of the folks might help us to get the KB/bug links.

Regards, 

Sharat Ainapur

Hi,

If you mean the output from our inventory system NeDi it's not an error to resolve the OID.
It's just that it retrieves and links for example the serial number to each specific part.

If you look at attached file it links the slot number with desc, serial nr etc to give an accurate lists of all the modules within the same tree.
So from an EX3200 or EX3300 im getting all the members, SFP's, PSU's with model description, serial number in a formatted list.

When using the OID for VC-member all i get is the "ex3400 24t" but nothing else since it cant match the slot with VC-member.

Hope you understand what im trying to say.

This has been resolved when upgrading to junos-arm-32-18.2R3.4!

Best Regards
Andreas

Hi Andreas, 

Thanks for updating the post, this will help others in the forum as well. 

Glad to know that this is fixed after upgrading to junos-arm-32-18.2R3.4.

Regards, 

Sharat