|
|
State management plays a key role in monitoring system resource status, managing service turn-up, and deleting resources. This chapter provides detailed information about the various Cisco 6100 Series system states, their meanings, and their impact on system operation.
The following states are supported by the Cisco 6100 Series system and by ViewRunner for
HP OpenView:
Of these states, Administrative, Operational, and Usage States are International Organization for for Standardization (ISO) compliant. The remaining states are Cisco 6100 Series system-
specific states.
The Administrative State is an operator-defined state. All other states are provided by the system either through autodiscovery, ViewRunner operation, or user-initiated polling of Cisco 6100 Series system Simple Network Management Protocol (SNMP) Agent data elements (opening
dialog boxes).
To access the state of a particular entity in ViewRunner for HP OpenView, place your cursor over the particular module in the 6100 Chassis View and click the right mouse button to select a property dialog box. States are readily viewable under each module or port Status tab. Use each module or port Configuration tab to manage the Administrative State.
The values of each state displayed within ViewRunner for HP OpenView are a function of the most recent Cisco 6100 Series system SNMP Agent poll. These states presented in a dialog box are retrieved from the Cisco 6100 Series system whenever a dialog box is opened and whenever a status tab is selected. Therefore, it is important to manage service-affecting changes with the Refresh button, which is provided on many of the user interface dialog boxes. The Refresh button retrieves the latest available values for the fields in the opened dialog box and redisplays the dialog box, enabling you to make change decisions based on up-to-date data.
With ViewRunner for HP OpenView, you can display the states of a particular module or port. Modules include ATU-C, line interface module (LIM), system controller (SC) module, network interface (NI) module, LIM controller module, and the subtend host module (STM). The status dialog boxes are similar for both modules and ports. The dialog boxes contain the following:
The Status tab on a module properties dialog box displays state information about that specific module. Figure 6-1 is representative of the display of states on module status tabs for all the modules in the user interface. See "Monitoring Status and Configuration," for information about status displays for particular modules in the Cisco 6100 Series system.
The Administrative and Operational states are indented under the Service State Details field. If one or more of these states takes on a negative state relative to its ability to provide service, the Service State field transitions from In Service to Out of Service. For example, if the Administrative State is changed from Unlocked to Locked, the Service State field changes from In Service to Out of Service. The lock and bell icons to the left of each tab name also indicate the operational and administrative state.
Press the Configuration tab to display configuration management fields. These include
1. Administrative State
2. Inventory Details
3. Transceiver Properties
The Status tab on a port displays state information about a specific port. Figure 6-2 is representative of the display of states on module Status tabs for all the modules in the user interface. See "Monitoring Status and Configuration," for information about status displays for particular ports on the Cisco 6100 Series system.
When the Usage State field is Busy, you can click LIM Properties to get information on the LIM that is connected to this ATU-C port. When the ATU-C Port Status field is Trained, the dialog box also displays port information such as the upstream and downstream rate.
Click the Configuration tab to display the Administrative State of the port (which allows you to lock or unlock the particular port) or to edit a physical or logical pool.
To fully understand states and their impact on system operations, some background in terminology is helpful. Key terminology includes entities and the containment hierarchy.
Figure 6-3 illustrates the specific containment hierarchy model to propagate state changes between various entities.
Within the containment hierarchy, superior entities contain subordinate entities. As shown in Figure 6-3, chassis are superior to slots; slots are superior to modules; and modules are superior
to ports.
Note that some entities can be both superior and subordinate. For example, a module is a superior entity to its ports, and a subordinate entity to its chassis.
Supporting or subordinate resource relationships are also important when managing resource deletions. See "Adding and Deleting System Components," for more information on deleting entities.
ViewRunner retrieves state information from the Cisco 6100 Series system when dialog boxes are opened. If Cisco 6100 Series system state information changes while the dialog box is open, you are typically not notified. ViewRunner for HP OpenView provides a Refresh button in each status dialog box, which allows you to refresh the current state information.
The Usage State indicates whether or not the entity is currently involved in an active ADSL connection. For an ADSL connection to be active, a modem must either be Trained or Training. For Digital Off-Hook (DOH) configurations, the Busy state applies to both ATU-C and LIM ports because DOH requires an analog cross-connect to exist between an ATU-C modem and a LIM port. Table 6-1 shows each Usage State that might appear on the Status dialog box.
| Display | Description |
|---|---|
Busy | Entity is 100% in use. A port is Busy when it is involved in an active ADSL connection. For a module to be Busy, all of its subordinate ports must be busy. |
Idle | Entity is not in use. |
Active | Indicates that the entity is in use but has more capacity. For example, a module is Active when some but not all of its subordinate ports are busy. The Active State provides a quick check to see if any of its subordinate resources are in use. The Active State applies only to modules. |
The Slot State identifies whether a module has been detected by the Cisco 6100 Series system as physically present and whether a configuration exists for it in the node. A persistent module configuration is generated automatically when the Cisco 6100 Series system detects the presence of a module. A configuration also is generated when a management system, such as ViewRunner for HP OpenView, preprovisions a configuration into an empty slot. Table 6-2 describes Slot States.
| Display | Description |
|---|---|
Empty Unprovisioned | A module is not present for this slot, nor does a configuration exist for it. The 6100 Chassis View depicts this state as an empty slot in the chassis bitmap. |
Empty Provisioned | A module configuration exists, but the Cisco 6100 Series system has not detected the presence of the module since power up. The 6100 Chassis View depicts the slot with a module bitmap and a blue (unknown) ejector tab. |
Filled Invalid | The module detected is invalid for the slot. |
Filled Mismatch | The module detected does not match the configuration for the slot. |
Filled Valid | A valid module configuration exists and the node reports the corresponding module is present. |
In addition to the slot state value, ViewRunner for HP OpenView also displays the type of module reported as physically present in the slot. For ATU-C modules, the words ATU-C module detected display just below the Slot State field. This is useful when the slot is in the filled mismatch state. The 6100 Chassis View bitmap displays what is configured in the slot. So, this field can be used to identify the mismatch.
The SC module monitors states to know when a particular port or connection is available. For example, the SC module does not send a connection request to a modem that has a Service State of Out of Service. Service States describe the overall ability of a resource to provide service. It is derived from a combination of Administrative, Operational, and Supporting Entity Service States. Table 6-3 describes the Service States.
| Display | Description |
|---|---|
In Service | The resource has all the necessary permission, ability, and availability to provide service when requested. |
Out of Service | One or more assigned or derived attributes of the resource prevent it from providing service. |
When a supporting entity's Service State transitions to Out of Service, that state propagates downward through the Cisco 6100 Series system containment hierarchy to all subordinate entities. The Subordinate Service State depends on the supporting entity Service State. Therefore, if the supporting entity in the containment hierarchy has a Service State of Out of Service, all of its subordinate entities are also Out of Service.
A supporting entity is defined as containing subordinate entities. For example, a module is a "supporting entity" to its ports, and conversely a port is a subordinate entity to a module.
When the supporting entity Service State transitions to Out of Service, that state propagates downward through the Cisco 6100 Series system containment hierarchy to all subordinate entities. The Subordinate Service State depends on the supporting entity Service State. Therefore, if the supporting entity in the containment hierarchy has a Service State of Out of Service, all of its subordinate entities are also Out of Service. The Cisco 6100 Series system tears down active calls for entities that transition to Out of Service and does not attempt to use them for new calls.
The Supporting Entity Service State is simply the Service State of the supporting entity in the containment hierarchy. This state represents the administrative permissions and the operational capabilities of all the higher-level entities which depend on this resource. If the supporting entity Service State is Out of Service, the subordinate entity Service State is also Out of Service. Table 6-4 describes the Supporting Entity Service States.
| Display | Description |
|---|---|
In Service | The supporting entity has the necessary permission, ability, or availability to provide service when requested. |
Out of Service | The supporting entity is unable to provide service. Therefore, none of the subordinate entities can provide service. |
The Administrative State serves two purposes. It enables you to lock an entity to prevent it from providing service. It also provides a mechanism for triggering state changes in the Cisco 6100 Series system configuration.
The Status tab displays the Administrative State for that entity. The Configuration tab lets you both display and modify the Administrative State for the entity. To access the Administrative State, select the Configuration tab on any entity property dialog box. The Administrative State
is either Locked or Unlocked. When an entity is Locked, it cannot actively participate in
node operation.
Unlocking an entity gives administrative permission to allow that entity to perform its function. Table 6-5 describes the Administrative States.
| Display | Description |
|---|---|
Locked | The entity does not have administrative permission to perform its function. |
Unlocked | The entity has administrative permission to perform its function. |
Because Administrative State is a component of the Service State, if Administrative State is Locked, the Service State becomes Out of Service.
When an administrator locks an entity, the lock ripples downward through the Cisco 6100 Series system containment hierarchy to all of its subordinate resources. As a result, every subordinate resource Service State changes to Out of Service.
Configuration changes are not applied to an entity unless they are changed after the Administrative State is set to Locked. Configuration changes can be entered into the configuration dialog box for the entity while the entity is Unlocked. However, these changes do not get applied until the entity Administrative State is subsequently locked and unlocked again.
Locking an entity takes it Out of Service and terminates any active calls. When an operator locks an entity, a confirmation dialog box (or boxes) is presented if the entity or any of its subordinates is involved in an active ADSL connection.
ViewRunner for HP OpenView requires the highest level entity to be administratively locked prior to executing an action that results in ViewRunner locking subordinate entities. This paradigm guarantees that service-affecting configuration changes are never sent to an In Service entity without first forcing a transition to the Unlocked state.
ViewRunner for HP OpenView requires that an entity to be locked prior to allowing modification or deletion of the service-affecting configuration parameters for the entity. Service-affecting parameters are any parameters that alter the service (DOH connection or PVC) provided to a subscriber. Examples include bit rate configuration, administrative state, and PVC configuration.
Nonservice-affecting configuration parameters do not require an unlock transition in order for them to take effect in the Cisco 6100 Series system. Nonservice-affecting parameters include entity names, such as Subscriber ID, and other system configuration parameters that are not directly involved with services. ViewRunner dialog boxes allow modification of these nonservice-affecting parameters while they are unlocked, and allow selection of the OK and Apply buttons.
When you select OK or Apply, ViewRunner for HP OpenView determines the configuration modifications that you requested. If only nonservice-affecting data has changed, ViewRunner proceeds with modifying the entity Administrative State.
In some instances, ViewRunner for HP OpenView sends lock messages to the Cisco 6100 Series system without an explicit state change. Done for convenience, this eliminates tedious lock operations when locking would clearly be required to take further action.
ViewRunner for HP OpenView performs automatic locks under the following conditions:
ViewRunner enforces the following rules that restrict entity unlocking:
The Operational State specifies whether the resource is in an alarmed condition or not. Operational States cannot be changed; it is a display-only field in the Status dialog boxes. Table 6-6 describes the Operational States.
| Display | Description |
|---|---|
Enabled | The resource is not in an alarm state. The resource is partially or fully operable and is able to provide service when so requested. |
Disabled | The resource is currently in an alarm state because of a fault being detected. The resource is totally inoperable and unable to provide service. |
The Operational State signals that a fault has been detected for a resource, but does not provide any details of specific alarms or the severity. ViewRunner allows you to view specific alarms by displaying a list box directly below the Operational State that shows all current alarms for the resource along with their severity.
The operational state of the fan tray is represented by a rectangular, colored box which is displayed in the upper right corner of the chassis in the Chassis View. The box changes colors to reflect the status of the fan tray. The fan status and alarm colors are the same as those used to indicate status and alarms of the Cisco 6100 Series Chassis. (See "Cisco 6100 Series Chassis View Colors" section for more information.) (See "Cisco 6100 Series Chassis View Colors" section on page B-3 for more information.)
Posted: Fri Oct 8 16:01:16 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.