View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
943 | RackTables | SNMP | public | 2013-07-15 15:22 | 2018-11-14 14:50 |
Reporter | cidemx | Assigned To | adoom42 | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | won't fix | ||
Product Version | 0.19.9 | ||||
Summary | 943: Unknown OID '2636.1.1.1.2.59' - Juniper EX8200 Series Virtual Chassis (EX8216) | ||||
Description | We needed to add the Juniper Virtual Chassis to our Racktables. There were already some Juniper Switche, which we used as Templates. Because the EX8200 have XE interfaces, I created a new iftable_processors pattern to use 10G SFP SR. We have build the package and deployed it in our Environment. If you would add it as a patch in the current version, that would be very helpful. $iftable_processors['juniper-xe-10G-SFP-SR'] = array ( 'pattern' => '@^xe-([[:digit:]]+)/0/([[:digit:]]+)$@', 'replacement' => '\\0', 'dict_key' => '1-30', 'label' => 'unit \\1 port \\2', 'try_next_proc' => FALSE, ); snmp.php Original '2636.1.1.1.2.31' => array ( 'dict_key' => 905, 'text' => 'Juniper EX4200 series', 'processors' => array ('juniper-ex-pic0-1000T', 'juniper-ex-mgmt'), ), new '2636.1.1.1.2.31' => array ( 'dict_key' => 905, 'text' => 'Juniper EX4200 series', 'processors' => array ('juniper-ex-pic0-1000T', 'juniper-ex-mgmt'), ), '2636.1.1.1.2.59' => array ( 'dict_key' => 905, 'text' => 'Juniper EX8200 series', 'processors' => array ('juniper-ex-pic0-1000T', 'juniper-ex-mgmt', 'juniper-xe-10G-SFP-SR'), ), | ||||
Tags | No tags attached. | ||||
|
|
This is a modular device, so additional SNMP information is required. Please gather ENTITY-MIB data described here: http://wiki.racktables.org/index.php/FAQ#Why_does_the_SNMP_sync_feature_return_Unknown_OID_.28n.n.n.n.n.29 | |
Please re-open if you can provide the ENTITY-MIB data. | |
Thanks for your help. Just wanted to do the Entity-MIB walk, and noticed that Juniper doesn't support this. I found an equivalent which is Chassis-MIB. I will attache 2 Files. One is chassis-mib and the other is virtualchassis-mib regards, Norman |
|
vchassis.txt (6,852 bytes)
SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.2.0 = STRING: "BA0910101015" SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.2.1 = STRING: "BA0910111054" SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.2.8 = STRING: "032011000027" SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.2.9 = STRING: "042011000009" SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.3.0 = INTEGER: 3 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.3.1 = INTEGER: 3 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.3.8 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.3.9 = INTEGER: 2 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.4.0 = Hex-STRING: 2C 6B F5 78 F4 00 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.4.1 = Hex-STRING: 2C 6B F5 7F C4 00 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.4.8 = Hex-STRING: 00 18 7D 15 E6 52 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.4.9 = Hex-STRING: 00 18 7D 17 2C F7 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.5.0 = STRING: "11.2R3.3" SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.5.1 = STRING: "11.2R3.3" SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.5.8 = STRING: "11.2R3.3" SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.5.9 = STRING: "11.2R3.3" SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.6.0 = INTEGER: 0 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.6.1 = INTEGER: 0 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.6.8 = INTEGER: 129 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.6.9 = INTEGER: 129 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.7.0 = INTEGER: 62378356 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.7.1 = INTEGER: 62378360 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.7.8 = INTEGER: 62378354 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.7.9 = INTEGER: 54527742 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.8.0 = STRING: "ex8216" SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.8.1 = STRING: "ex8216" SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.8.8 = STRING: "ex-xre" SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.8.9 = STRING: "ex-xre" SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.9.0 = "" SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.9.1 = "" SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.9.8 = "" SNMPv2-SMI::enterprises.2636.3.40.1.4.1.1.1.9.9 = "" SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.0.13.118.99.112.45.48.47.48.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.0.13.118.99.112.45.48.47.49.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.0.15.118.99.112.45.48.47.48.47.52.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.0.15.118.99.112.45.48.47.48.47.53.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.0.15.118.99.112.45.49.47.48.47.48.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.0.15.118.99.112.45.49.47.48.47.49.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.1.13.118.99.112.45.48.47.48.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.1.13.118.99.112.45.48.47.49.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.1.15.118.99.112.45.48.47.48.47.52.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.1.15.118.99.112.45.48.47.48.47.53.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.1.15.118.99.112.45.49.47.48.47.48.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.1.15.118.99.112.45.49.47.48.47.49.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.8.13.118.99.112.45.48.47.48.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.8.13.118.99.112.45.49.47.48.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.8.13.118.99.112.45.49.47.49.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.8.13.118.99.112.45.49.47.50.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.8.13.118.99.112.45.49.47.51.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.9.13.118.99.112.45.48.47.48.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.9.13.118.99.112.45.49.47.48.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.9.13.118.99.112.45.49.47.49.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.9.13.118.99.112.45.49.47.50.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.3.9.13.118.99.112.45.49.47.51.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.0.13.118.99.112.45.48.47.48.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.0.13.118.99.112.45.48.47.49.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.0.15.118.99.112.45.48.47.48.47.52.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.0.15.118.99.112.45.48.47.48.47.53.46.51.50.55.54.56 = INTEGER: 2 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.0.15.118.99.112.45.49.47.48.47.48.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.0.15.118.99.112.45.49.47.48.47.49.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.1.13.118.99.112.45.48.47.48.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.1.13.118.99.112.45.48.47.49.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.1.15.118.99.112.45.48.47.48.47.52.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.1.15.118.99.112.45.48.47.48.47.53.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.1.15.118.99.112.45.49.47.48.47.48.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.1.15.118.99.112.45.49.47.48.47.49.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.8.13.118.99.112.45.48.47.48.46.51.50.55.54.56 = INTEGER: 2 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.8.13.118.99.112.45.49.47.48.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.8.13.118.99.112.45.49.47.49.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.8.13.118.99.112.45.49.47.50.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.8.13.118.99.112.45.49.47.51.46.51.50.55.54.56 = INTEGER: 2 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.9.13.118.99.112.45.48.47.48.46.51.50.55.54.56 = INTEGER: 2 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.9.13.118.99.112.45.49.47.48.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.9.13.118.99.112.45.49.47.49.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.9.13.118.99.112.45.49.47.50.46.51.50.55.54.56 = INTEGER: 1 SNMPv2-SMI::enterprises.2636.3.40.1.4.1.2.1.4.9.13.118.99.112.45.49.47.51.46.51.50.55.54.56 = INTEGER: 2 |
|
The Chassis MIB you describe is proprietary and limited to Juniper products. Please provide a full SNMP walk and/or upgrade the device firmware to determine if there is an industry-standard way to acquire the module data. | |
Thanks for the info. I uploaded a full walk now. regards, Norman |
|
I looked through the full SNMP walk and didn't find a way to translate the data into a modular device in RackTables. The feature hasn't been released yet, but soon RackTables will support modular devices in this fashion: - 'SNMP sync' is performed on the chassis object. - ENTITY-MIB OIDs are polled to determine the device hierarchy. There are entries in the ENTITY-MIB tables for each component (the chassis, blades, ports). Parent/child relationships are also specified. - A separate object is created in RT for each blade. Each blade's 'Container' is set to the chassis object. - A table is available which maps the ENTITY-MIB entries to entries in the IF-MIB table. Using this correlation, the MAC address of each port can be determined. - When viewing the chassis object, ports and IP addresses of all child objects are displayed for easy reference. Using the patches you originally submitted would let you 'SNMP sync' the device, and ports of all blades would be added to the chassis object itself (no child objects would exist). If you find that acceptable, just patch your local installation. If you want to get the modular approach working, I suggest upgrading the firmware on your device and performing another full walk to see if ENTITY-MIB data is available. The MIB tarball from Juniper's site does include ENTITY-MIB which leads me to believe it is supported, at least in the latest version. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2013-07-15 15:22 | cidemx | New Issue | |
2013-07-15 15:22 | cidemx | Status | new => assigned |
2013-07-15 15:22 | cidemx | Assigned To | => adoom42 |
2013-07-15 15:22 | cidemx | File Added: ifTable | |
2013-07-15 15:33 | cidemx | File Added: sysDescr | |
2013-07-15 15:34 | cidemx | File Added: sysObjectID | |
2013-10-06 22:52 | adoom42 | Tag Attached: modular | |
2013-10-06 22:54 | adoom42 | Note Added: 0001829 | |
2013-10-06 22:54 | adoom42 | Status | assigned => feedback |
2013-10-10 04:32 | adoom42 | Note Added: 0001853 | |
2013-10-10 04:32 | adoom42 | Status | feedback => closed |
2013-10-10 04:32 | adoom42 | Resolution | open => won't fix |
2013-10-15 14:28 | cidemx | Note Added: 0001859 | |
2013-10-15 14:28 | cidemx | Status | closed => feedback |
2013-10-15 14:28 | cidemx | Resolution | won't fix => reopened |
2013-10-15 14:29 | cidemx | File Added: vchassis.txt | |
2013-10-15 14:29 | cidemx | File Added: chassis.txt | |
2013-10-15 14:30 | cidemx | Note Edited: 0001859 | |
2013-10-15 16:51 | adoom42 | Note Added: 0001861 | |
2013-10-15 17:47 | cidemx | File Added: fullwalk.tar.gz | |
2013-10-15 17:47 | cidemx | Note Added: 0001863 | |
2013-10-15 17:47 | cidemx | Status | feedback => assigned |
2013-10-16 00:17 | adoom42 | Note Added: 0001865 | |
2013-10-16 00:17 | adoom42 | Status | assigned => closed |
2013-10-16 00:17 | adoom42 | Resolution | reopened => won't fix |
2018-11-14 14:50 | infrastation | Tag Detached: modular |