Unsolved
This post is more than 5 years old
2 Posts
0
905
August 22nd, 2007 03:00
sysName or DNS name used?
Got an issue with naming within SMARTS.
Why are some switches coming up with the SNMP sysName and others coming up with the FQDN in SMARTS when discovered with the AM/PM server. (I am assuming that it is the SNMP sysName since the format is in UpperCase - DNS is in lowercase)
All of the Cisco Switches are configured with the management address on VLAN 2 and NOT Loopback.
There has been no change to the name-resolver.conf file which is set for TM_USEAUTONAME, and the search order is;
TM_USELOOPBACK
TM_USESYSNAME
TM_USENONPRIVATEIP
TM_USEPRIVATEIP
TM_USEAGENTADDRESS
Is there anyway of forcing to use the DNS and not the SNMP sysName.
Message was edited by:
RussParker
Why are some switches coming up with the SNMP sysName and others coming up with the FQDN in SMARTS when discovered with the AM/PM server. (I am assuming that it is the SNMP sysName since the format is in UpperCase - DNS is in lowercase)
All of the Cisco Switches are configured with the management address on VLAN 2 and NOT Loopback.
There has been no change to the name-resolver.conf file which is set for TM_USEAUTONAME, and the search order is;
TM_USELOOPBACK
TM_USESYSNAME
TM_USENONPRIVATEIP
TM_USEPRIVATEIP
TM_USEAGENTADDRESS
Is there anyway of forcing to use the DNS and not the SNMP sysName.
Message was edited by:
RussParker
No Events found!
smarts3
6 Posts
0
August 23rd, 2007 23:00
Change the order in "conf/discovery/name-resolver.conf".
Default is
AutoNameOrder 0 TM_USELOOPBACK
AutoNameOrder 1 TM_USESYSNAME
AutoNameOrder 2 TM_USENONPRIVATEIP
AutoNameOrder 3 TM_USEPRIVATEIP
AutoNameOrder 4 TM_USEAGENTADDRESS
.
You can change the priority,for example,
AutoNameOrder 2 TM_USELOOPBACK
AutoNameOrder 4 TM_USESYSNAME
AutoNameOrder 0 TM_USENONPRIVATEIP
AutoNameOrder 1 TM_USEPRIVATEIP
AutoNameOrder 3 TM_USEAGENTADDRESS
In this cace the sysName is used last.
----
Katsuhiko
RussParker
2 Posts
0
August 28th, 2007 00:00
EMC came back to me through a support call and told me of one other setting.
Similar idea to what you were suggesting but to force the sysName by AutoNameOrder 0 TM_USESYSNAME.
Then, in the discovery.conf file though, comment out;
DisplayNameFormat = "AUTOASSIGNED" and un-comment DisplayNameFormat = "MIBIISYSNAME". Restart AM/PM server
This actually did work and showed me that it wasn't SMARTS that was the issue, but the Cisco IOS command "ip domain-name " had been left on some of the Cisco switches along with an old domain name.
This caused the descrepency within DNS and the Name resolution in SMARTS where SMARTS was seeing some devices with FQDN and some without.
It was the ones WITH the FQDN that had the command Cisco IOS "ip domain-name".
What confused me to start with was SMARTS showed the DNS FQDN and not that the FQDN entered on the Cisco device with the Cisco IOS command "ip domain-name".
Thanks
Russ