Smarts NCM: Riverbed Steelhead devices get discovered as "Generic"
Article ID: 330940
Updated On:
Products
Issue/Introduction
Riverbed steelhead devices (specific model Ex1160) get classified as "Generic" post discovery in NCM. The following entries can be found in autodisc.log-
Sep 12 10:48:02 :-244164288/10.xx.xx.xx@1320/snmp#4: discoverDriverViaSnmp: 10.101.40.18: (trying Driver #1320:Riverbed)
Sep 12 10:48:02 :-244164288/10.xx.xx.xx@1320/snmp#4: [01;32mExecuting function "Riverbed::initialize"[00m...
Sep 12 10:48:02 :-244164288/10.xx.xx.xx@1320/snmp#4: [01;32mExecuting function "Riverbed::initialize"[00m...done #0.000000e+00 (0)
Sep 12 10:48:02 :-244164288/10.xx.xx.xx@1320/snmp#4: [01;32mExecuting function "Riverbed::discoverDevice"[00m...
Sep 12 10:48:02 :-244164288/10.xx.xx.xx@1320/snmp#4: DASL: Riverbed Steelhead discovery
Sep 12 10:48:02 :-244164288/10.xx.xx.xx@1320/snmp#4: DASL: possible Riverbed device; querying further
Sep 12 10:48:02 :-244164288/10.xx.xx.xx@1320/snmp#4: DASL: error retrieving chassis S/N via SNMP: RTSNMPVar::getDASLValueFromVb: Can't read OID(1.3.6.1.4.1.17163.1.1.1.2.0) (syntax:128) -- NOSUCHOBJECT/NOSUCHINSTANCE/ENDOFMIBVIEW (TSNOTE) (RTSNMPVar.cpp#640)
Sep 12 10:48:02 :-244164288/10.xx.xx.xx@1320/snmp#3: ERROR: error retrieving chassis S/N via SNMP: RTSNMPVar::getDASLValueFromVb: Can't read OID(1.3.6.1.4.1.17163.1.1.1.2.0) (syntax:128) -- NOSUCHOBJECT/NOSUCHINSTANCE/ENDOFMIBVIEW (TSNOTE) (RTSNMPVar.cpp#640)
Sep 12 10:48:02 :-244164288/10.xx.xx.xx@1320/snmp#3: ++++++++++++++++++++
Sep 12 10:48:02 :-244164288/10.xx.xx.xx @1320/snmp#3: ...iverbed/hwfuncs.inc#97: ERROR: error retrieving chassis S/N via SNMP: RTSNMPVar::getDASLValueFromVb: Can't read OID(1.3.6.1.4.1.17163.1.1.1.2.0) (syntax:128) -- NOSUCHOBJECT/NOSUCHINSTANCE/ENDOFMIBVIEW (TSNOTE) (RTSNMPVar.cpp#640)
Environment
Cause
Resolution
- Ensure you do not make any changes to the package Directory ($VOYENCE_HOME/package), or to any of the package directory contents.
- Copy the file to be modified from the directory structure under the package directory, to the directory structure under the custompackage directory. Create the directories under custompackage directory if they don t exist already.
In this case: cp $VOYENCE_HOME/package/riverbed/Riverbed.models $VOYENCE_HOME/custompackage/riverbed/Riverbed.models
- Open Riverbed.models file located at $VOYENCE_HOME/custompackage/riverbed/ directory and add the following device entry at the end of file and save it.
EX1160H; 1.51; 1320
- Run mkmodelsxml.pl from $VOYENCE_HOME/custompackage/riverbed/ directory
$VOYENCE_HOME/tools/mkmodelsxml.pl < Riverbed.models> RiverbedModels.xml
- Copy/move the file RiverbedModels.xml from $VOYENCE_HOME/custompackage/riverbed/ directory to $VOYENCE_HOME/custompackage/pkgxml/Riverbed/
- Run below command:
service voyence restart
- After the service restart, remove the device from NCM and discover it again.
The result of the above operation should be successful discovery of the Riverbed device with system OID ending with 1.51 & classification of the specific device type.
Additional Information
Feedback
