r***@osl.uoregon.edu
2017-03-24 12:23:21 UTC
Issue #1913 has been reported by Brian Candler.
----------------------------------------
Bug #1913: Naming method 'sysname' ignores sysname
https://osl.uoregon.edu/redmine/issues/1913
Author: Brian Candler
Status: New
Priority: Normal
Assignee:
Category:
Target version:
Resolution:
Here is a device with a valid sysName:
<pre>
# snmpwalk -v2c -c NetManage 100.68.100.235 sysName
SNMPv2-MIB::sysName.0 = STRING: transit1.nren.ws.nsrc.org
</pre>
This is what I want the device to be known as in Netdot.
The forward DNS matches its SNMP IP:
<pre>
# dig +short transit1.nren.ws.nsrc.org
100.68.100.235
</pre>
But the reverse DNS points to a more detailed name (including the interface).
<pre>
# dig +short -x 100.68.100.235
fa0-0.transit1.nren.ws.nsrc.org.
# dig +short fa0-0.transit1.nren.ws.nsrc.org
100.68.100.235
</pre>
Site.conf has:
<pre>
DEVICE_NAMING_METHOD_ORDER => [ 'sysname', 'snmp_target' ],
</pre>
Therefore I was expecting it to take the Netdot device name from the sysName. But when I add the device, it uses the reverse DNS for the target address instead.
<pre>
# /usr/local/netdot/bin/updatedevices.pl -H 100.68.100.235 -I -c xxxxxxxx
...
SNMP::Info::specify() - Changed Class to SNMP::Info::Layer3::Cisco.
DEBUG - SNMPv2 session with host 100.68.100.235 established
DEBUG - Device::get_snmp_info: SNMP target is 100.68.100.235
...
DEBUG - Device::get_snmp_info: Finished getting SNMP info from 100.68.100.235
DEBUG - Device::discover: Device 100.68.100.235 does not yet exist
DEBUG - Device::_get_main_ip: Trying method sysname
DEBUG - Device::_get_main_ip: Chose 100.68.100.235 using naming method: sysname
DEBUG - Device::assign_name: 100.68.100.235 resolves to fa0-0.transit1.nren.ws.nsrc.org
INFO - Inserted new RR: fa0-0.transit1.nren.ws.nsrc.org
</pre>
----------------------------------------
Bug #1913: Naming method 'sysname' ignores sysname
https://osl.uoregon.edu/redmine/issues/1913
Author: Brian Candler
Status: New
Priority: Normal
Assignee:
Category:
Target version:
Resolution:
Here is a device with a valid sysName:
<pre>
# snmpwalk -v2c -c NetManage 100.68.100.235 sysName
SNMPv2-MIB::sysName.0 = STRING: transit1.nren.ws.nsrc.org
</pre>
This is what I want the device to be known as in Netdot.
The forward DNS matches its SNMP IP:
<pre>
# dig +short transit1.nren.ws.nsrc.org
100.68.100.235
</pre>
But the reverse DNS points to a more detailed name (including the interface).
<pre>
# dig +short -x 100.68.100.235
fa0-0.transit1.nren.ws.nsrc.org.
# dig +short fa0-0.transit1.nren.ws.nsrc.org
100.68.100.235
</pre>
Site.conf has:
<pre>
DEVICE_NAMING_METHOD_ORDER => [ 'sysname', 'snmp_target' ],
</pre>
Therefore I was expecting it to take the Netdot device name from the sysName. But when I add the device, it uses the reverse DNS for the target address instead.
<pre>
# /usr/local/netdot/bin/updatedevices.pl -H 100.68.100.235 -I -c xxxxxxxx
...
SNMP::Info::specify() - Changed Class to SNMP::Info::Layer3::Cisco.
DEBUG - SNMPv2 session with host 100.68.100.235 established
DEBUG - Device::get_snmp_info: SNMP target is 100.68.100.235
...
DEBUG - Device::get_snmp_info: Finished getting SNMP info from 100.68.100.235
DEBUG - Device::discover: Device 100.68.100.235 does not yet exist
DEBUG - Device::_get_main_ip: Trying method sysname
DEBUG - Device::_get_main_ip: Chose 100.68.100.235 using naming method: sysname
DEBUG - Device::assign_name: 100.68.100.235 resolves to fa0-0.transit1.nren.ws.nsrc.org
INFO - Inserted new RR: fa0-0.transit1.nren.ws.nsrc.org
</pre>
--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://osl.uoregon.edu/redmine/my/account
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://osl.uoregon.edu/redmine/my/account