Sometimes, users may be unable to get an MIB result (physical hardware information for example) by using entPhysicalTable (1.3.6.1.2.1.47.1.1.1) for the MX Virtual Chassis (MX-VC) when loading Junos OS Release 16.1 and later.
This article describes how to fetch equivalent MIB information by using jnxBoxAnatomy or jnxFruTable.
Note: This issue is fixed in Junos OS Releases 19.4R3-S6, 20.3R3-S1, 20.4R3, and 21.1R3.
There may not be any output during the MIB walk as shown below:
{master:member0-re0} labroot@MXVC-router> show snmp mib walk entPhysicalTable <<< No output
You can get equivalent MIB information from jnxBoxAnatomy (1.3.6.1.4.1.2636.3.1) or jnxFruTable (1.3.6.1.4.1.2636.3.1.15) on MX-VC.
For example, you can get physical hardware information from MIB jnxContentsEntry (1.3.6.1.4.1.2636.3.1.8.1), which is under jnxBoxAnatomy (1.3.6.1.4.1.2636.3.1).
{master:member0-re0} labroot@MXVC-router> show snmp mib walk 1.3.6.1.4.1.2636.3.1.8.1 jnxContentsContainerIndex.1.2.0.0 = 1 jnxContentsContainerIndex.1.3.0.0 = 1 jnxContentsContainerIndex.2.6.0.0 = 2 jnxContentsContainerIndex.2.6.1.0 = 2 ….. jnxContentsModel.4.18.2.0 = FFANTRAY-MX960-HC-S jnxContentsModel.4.18.3.0 = FFANTRAY-MX960-HC-S jnxContentsModel.4.18.4.0 = FFANTRAY-MX960-HC-S jnxContentsModel.4.18.5.0 = FFANTRAY-MX960-HC-S jnxContentsModel.4.18.6.0 = FFANTRAY-MX960-HC-S jnxContentsModel.4.18.7.0 = FFANTRAY-MX960-HC-S jnxContentsModel.4.18.8.0 = FFANTRAY-MX960-HC-S jnxContentsModel.4.18.9.0 = FFANTRAY-MX960-HC-S jnxContentsModel.4.18.10.0 = FFANTRAY-MX960-HC-S jnxContentsModel.4.18.11.0 = FFANTRAY-MX960-HC-S jnxContentsModel.4.18.12.0 = FFANTRAY-MX960-HC-S jnxContentsModel.7.21.0.0 = MPC5E-100G10G jnxContentsModel.7.22.0.0 = MPC5E-100G10G jnxContentsModel.7.24.0.0 = MX-MPC2E-3D-Q jnxContentsModel.7.25.0.0 = MX-MPC2E-3D-Q jnxContentsModel.7.29.0.0 = MX-MPC2E-3D-Q jnxContentsModel.7.30.0.0 = MPC2E-3D-NG-Q ...snip