|
|
This chapter contains the following sections:
Cisco UGM's presence polling function monitors the device for a reboot operation. When Cisco UGM detects a reboot, rediscovery is initiated on that device, and an internal alarm is generated: Chassis has been reloaded and will be rediscovered. This alarm is informational only. Check the Event Browser for alarm details.
When the card-level presence polling function finds card changes, rediscovery is initiated on the parent device, and an internal alarm is generated: Card presence polling discovered card shuffling - chassis will be rediscovered. This alarm is informational only. Check the Event Browser for alarm details.
You can detect communication loss with a managed device by using presence polling. Loss of communication can occur for various reasons:
When Cisco UGM first detects loss of communication to a managed device, it does not immediately transition the device to the errored state, but retries presence polling. Select the number of retries as described in the "Setting the Presence Polling Interval for Cards" section.
Presence polling uses an interval specified in the "Setting Presence Polling Intervals for Devices in Normal, Errored, and Reload States" section. If all the communication attempts prove unsuccessful, the device transitions to the errored state. An internal alarm event (communicationLost) with a Major severity level is raised against the affected device. You can view alarm events in the Event Browser.
The default presence polling intervals are:
These attributes enable Cisco UGM to detect the addition or removal of cards in a device, and then initiate rediscovery of the device.
Table 8-1 Presence Polling MIB Attributes
| MIB Attribute Name | Description |
|---|---|
 |
Note In the Cisco Universal Gateway Manager Settings dialog box, the values you enter depend on the total number of managed devices in your network. You may need to change this value a few times in order to determine the optimum setting for your network. |
Step 2 Enter the interval at which a device should be polled in the normal state.
The interval should be an integer value that is greater than 30 seconds. The default is 60 seconds.
Step 3 Enter the interval at which a device should be polled in the errored state.
The interval should be an integer value that is greater than 30 seconds. The default is 60 seconds.
Step 4 Enter the interval at which a device should be polled in the reload state.
The interval should be an integer value that is greater than 30 seconds. The default is 60 seconds.
Step 5 Click Apply.
Step 2 Enter the interval at which cards should be polled.
The interval should be an integer value that is greater than 30 seconds. The default is 300 seconds.
|
Note This value depends on the total number of managed devices and components in your network. You may need to change this value a few times in order to determine the optimum setting for your network. |
Step 3 Click Apply.
When Cisco UGM first detects loss of communication to a managed device, it does not immediately transition the device to the errored state, but retries presence polling by using the polling interval specified in the "Setting Presence Polling Intervals for Devices in Normal, Errored, and Reload States" section. If these communication attempts are unsuccessful, the device transitions to the errored state.
Step 2 Enter the number of times Cisco UGM tries to re-establish connectivity before transitioning the device into the errored state.
The number that you enter should be an integer value that is 0 or larger. A value of 0 disables retries; the default is 1.
|
Note A large value causes a delay before loss of communication with a device is detected. |
Step 3 Click Apply.
The failure of the active device and the activation of the standby device is detected by Cisco UGM's redundancy presence polling feature. This redundancy state change generates a warning alarm against the device object.
When Cisco UGM receives traps from these devices, both devices transition to a "handover" state while control of the cards is transferred. The process can take several minutes and prevents the possible reading of incorrect values and subsequent failure to create new objects in the rediscovery that follows.
|
Note The handover interval is currently set to 90 seconds. If you find that this
interval is inadequate to transfer control, change the value of the appropriate
variable in the ASMainCtrlUserData.ini configuration file:
AS5800ChassisHandoverLingerSec or AS5850ChassisHandoverLingerSec. In order for these new values to take effect, restart the ASMainCtrl controller by typing these commands: cd /opt/cemf/bin cemf shell sysmgrClient -k ASMainCtrl sysmgrClient -x ASMainCtrl |
The handover state is followed by the commissioning state when device component rediscovery is completed.
|
Note Do not commission or decommission more than three devices at a time. |
Commission a device to return it to a normal (commissioned) state within the EMS.
When you commission a device, an informational alarm is raised in Event Browser, and Cisco UGM starts discovery on the device to resolve any card inventory changes that may have occurred while the device was in the decommissioned state. When discovery is completed, the device returns to the normal or errored state depending on whether commissioning was successful.
|
Note When a device is commissioned, all its components (cards and ports) also transition into the commissioned state. |
The procedure to commission a device is described in the "Commissioning and Decommissioning a Device or Card" section.
|
Note Do not commission or decommission more than three devices at a time. |
With Cisco UGM, you can decommission a device from any state, and an informational alarm is raised in Event Browser.
You can decommission a device due to one of these causes:
A decommissioned object is still managed by Cisco UGM, and has alarms raised against it unconditionally. Performance or presence polling is carried out, and alarm events are collected and viewed by using the Event Browser. In addition, the color of the icon representing the object in the Map Viewer indicates the severity and number of alarms raised. However, because the object is in a decommissioned state, no alarm propagation takes place.
|
Note When a chassis is decommissioned, all its components (cards and ports) also transition into the decommissioned state. |
The procedure to commission a device is described in the "Commissioning and Decommissioning a Device or Card" section.
Commission a card to return it to a normal (commissioned) state within the system.
When you commission a card, Cisco UGM reconciles its status with that of the actual card on the device. When this is completed, the card returns to either the normal or errored state. If the card is removed from the device, the corresponding card object is deleted.
|
Note When a parent device is commissioned, all its components (cards and ports) also transition into the commissioned state. Likewise, when a card is commissioned, all its ports are also commissioned. |
The procedure to commission a device is described in the "Commissioning and Decommissioning a Device or Card" section.
You can decommission a card from any state due to one of these causes:
A decommissioned object is still managed by Cisco UGM, and has alarms raised against it unconditionally. Performance or presence polling is carried out, and alarm events are collected and viewed by using the Event Browser. In addition, the color of the icon representing the object in the Map Viewer indicates the severity and number of alarms raised. However, because the object is in a decommissioned state, no alarm propagation takes place.
When a parent device is decommissioned, all its components (cards and ports) also transition into the decommissioned state. Likewise, when a card is decommissioned, all its ports are also decommissioned.
The procedure to commission a device is described in the "Commissioning and Decommissioning a Device or Card" section.
Step 2 Choose AS5xxx object> Chassis > Chassis Commissioning.
Choose Card object > Card Commissioning.
Step 3 Click Commission or Decommission.
 |
Tip Decommissioned devices appear as shaded icons in the right-hand pane of the Map Viewer. |
Posted: Fri Apr 4 23:24:08 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.