3
Votes

Controller: Set network element hostname

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
 
3
Votes

Controller: Set network element hostname

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Controller: Set network element hostname
Controller: Set network element hostname
2023-03-13 23:28:49

Hello!, 

 

I would like the Omada SDN controller to set the hostname & SNMP sysName attribute. This is to have proper integration with an external NMS system that polls metrics from the following elements in my case:

 

EAP225-Outdoor(US) v1.0

EAP245(US) v3.0

TL-SG2210MP v1.0

 

As is today, the devices present a sysName equal to the model (I'm assuming that the hostname too). As other network elements from different manufacturers or Linux systems, I would expect it to be the hostname as defined in the Operating system/firmware.

 

As seen in the controller:

 

 

As seen from SNMP data:

 

 

 

 

Examples from CLI:

 

# snmpwalk -v2c -c cstring wap01.lan iso.3.6.1.2.1.1.5.0
iso.3.6.1.2.1.1.5.0 = STRING: "EAP225-Outdoor"
 

 

That entry is expected to be unique to the equipment, so trying to add another node of the same type fails (example from LibreNMS but behaviour is pretty standard from other SNMP tools):

 

                 LibreNMS\Exceptions\HostSysnameExistsException: Already have device wap03.lan due to duplicate sysName: eap245

 

 

 

Example from other implementations:

 

 

 

 

# snmpwalk -v2c -c cstring nas02.lan iso.3.6.1.2.1.1.5.0
iso.3.6.1.2.1.1.5.0 = STRING: "nas02"


# snmpwalk -v2c -c cstring bigiron.lan iso.3.6.1.2.1.1.5.0
iso.3.6.1.2.1.1.5.0 = STRING: "bigiron"

 

#1
Options