Technical FAQs

Ask a Question

Changing SNMP hostname field of NMC through InfraStruxure Central may cause a communications issue.

Issue:

Changing SNMP hostname field of NMC through InfraStruxure Central may cause a communications issue.

Product Line:

InfraStruxure Central
StruxureWare Central
StruxureWare Data Center Expert
APC Network Management cards

Environment:

All versions

Cause:

Changed configurations.

Resolution:

With InfraStruXure Central/StruxureWare Data Center Expert, you can use the device menu to access "APC SNMP device configuration" where settings on APC network enabled devices can be changed or templates to change devices can be created. If you use this feature to change the NMS hostname field associated with SNMPv1 settings and Authentication, certain settings may cause InfraStruXure Central to change the device communications settings for the devices you're trying to configure. If you try using normally considered non-routable addresses such as listed below, ISX Central will see this as invalid and set the read and write community strings associated with that device back to the default of public and private. The same thing will happen if the user attempts to use a '0' or '*' as a wildcard.

Currently: Anything entered into NMS hostname Field with the IP ranges: of 10.*.*.* 172.16.*.* 192.168.*.* or anything with a 0 in IP other then 0.0.0.0 would be considered invalid and reset the SNMP scan settings in ISXC but (not on the NMC).

This feature will be fixed in ISX Central 6.2 due out early 2011. Any of the following patterns can be entered into the NMS Hostname Field and be accepted by both ISXC and the NMC x.255.255.255 x.x.255.255 x.x.x.255 255.255.255.255 A Hostname
Was this helpful?
What can we do to improve the information ?