The Manager checks the statuses of registered devices by using SNMP, ping or unique protocol at intervals of 60 seconds (default). It is as follows which method to use.
Method to use | Devices |
|---|---|
SNMP | ETERNUS GR series |
ping | Devices supporting automatic detection, other than the above devices. |
unique protocol | Agent introduction server node |
For a device using SNMP, the system obtains information about the status of the device with the respective vendor's private MIB. If the status of the device has been changed compared with that stored by Manager, the system displays a device event and changes the device icon color according to the change.
However the status cannot be changed for the ETERNUS SN2000 series Fibre Channel switch and PRIMEGRY BX600 fibre channel switch blades.
A device using ping cannot detect a change in device status, however, if an abnormality occurs in the device or in a network between the device and Manager. In this event, the device does not respond to ping (non-communicating state), the event is displayed, and the icon color becomes gray. The next time that the device responds to polling, the previous state (state before the non-communicating state) is restored. The device which uses an unique protocol operates considerable ping by using an unique protocol.
With either SNMP or ping, Systemwalker Centric Manager linkage and Shell/bat linkage are enabled by default. The swsag code reported to Centric Manager is 4822. The linkage behavior can be modified. For information see "C.10 Device Polling Setting File".
Users can customize polling intervals, the time at which operation stops, the specification of devices to be excluded from polling operation, and other device polling functions. For details, see "C.10 Device Polling Setting File".
Note
This function does not support manual embedding devices for which no IP address is set.
Information
To use SNMP, define "public" as the community name. For information on communication with a different community name, see "SNMP_COMMUNITY_NAME_FOR_IP" in the "C.2 sanma.conf Parameter", so that an appropriate community name can be set.
