I have 2 different models, on both i have the option to change the sysDescr.
So i wound assume that all moxa switche have user defined sysDescr.
The test was on a " Moxa EDS-P506E-4PoE-2GTXSFP" .
Torstein Eide
added a comment - I have 2 different models, on both i have the option to change the sysDescr.
So i wound assume that all moxa switche have user defined sysDescr.
The test was on a " Moxa EDS-P506E-4PoE-2GTXSFP" .
This is not recommended (and undocumented) way.
Really all definitions MUST have real oid_num.
You can use first discovery for translate, but fill correct numeric oids after.
Mike Stupalov
added a comment - This is not recommended (and undocumented) way.
Really all definitions MUST have real oid_num.
You can use first discovery for translate, but fill correct numeric oids after.
Torstein Eide
added a comment - The
$config[ 'mibs' ][$mib][ 'processor' ][ 'swMgmt' ]
"swMgmt" is the parent oid.
okay, the oid and key can be the same.
Why? the discovery will translate it. i currently don't see the benefit of using my time on doing a task that the discovery script does more effectively at minimal cost.
Torstein Eide
added a comment - Why? the discovery will translate it. i currently don't see the benefit of using my time on doing a task that the discovery script does more effectively at minimal cost.
Mike Stupalov
added a comment - Please show why incorrect (examples of incorrect sysDescr) for hardware detect:
-$config['os'][$os]['sysDescr_regex'][] = '/^(?:MOXA )?(?<hardware>\w\S+)/';
Updated in r10307.