Table of Contents

5.1 Module and Port Status Dialog Boxes

5.1.1 Module Status Dialog Box
5.1.2 Port Status Dialog Boxes

5.2 Cisco 6100 Series System Entities and Containment Hierarchy
5.3 State Detection and Propagation
5.4 Usage State
5.5 Slot State
5.6 Service State Functions
5.7 Supporting Entity Service State
5.8 Administrative State

5.8.1 Locking an Actively Connected Entity
5.8.2 Service Affecting Configuration Rules
5.8.3 Automatic Locking and Unlocking

5.9 Operational State
5.10 Fault Tolerant State

Cisco 6100 Series System and ViewRunner State Management

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 Windows:

• Usage state

• Slot state

• Service state

• Administrative state

• Supporting Entity Service state

• Operational state

• Maintenance state

• Fault Tolerant state

Of these states, Administrative, Operational, and Usage states are International Standards Organization (ISO) compliant. The remaining states are Cisco 6100 Series-specific states.

The Administrative state is an operator-defined state. All other states are system-provided either through discovery or through ViewRunner for Windows polling of the Cisco 6100 Series system event log or Cisco 6100 Series SNMP agent data elements.

5.1 Module and Port Status Dialog Boxes

With ViewRunner for Windows, you can display the states of a particular module or port. Types of modules functioning in ViewRunner for Windows include: CAP ATU-C, DMT-2 ATU-C, STU-C line interface module (LIM), system controller (SC), network interface (NI), and LIM controller, and in the case of subtended Cisco 6100 Series systems, the subtend NI. The Status dialog boxes are similar for both modules and ports. The dialog boxes contain

• A description of all asserted alarms. Alarm severity is indicated by text and a colored icon. Alarms represent the Operational state of the module and any of its ports.

• The module's Usage state. Busy indicates that all the module's subordinate ports are busy. Active indicates that one but not all of the module's subordinate ports are busy. Idle indicates that none of the module's subordinate ports are busy.

5.1.1 Module Status Dialog Box

The Status tab on a Module Properties dialog box displays state information about that specific module. Figure 5-1 is representative of the display of states on module Status tabs for all the modules in the user interface. See "System Operation and Performance with a Digital Off-Hook Configuration," for information about status displays for particular modules of 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.

Press the Configuration tab to display additional fields. These include Inventory Details and ATU-C (or LIM) Connect on Demand, and the Administrative state, which allows the user to lock or unlock the particular module.

5.1.2 Port Status Dialog Boxes

The Status tab on a port displays state information about a specific port. Figure 5-2 is representative of the display of states on module status tabs for all the modules in the user interface. See "System Operation and Performance with a Digital Off-Hook 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 the LIM Properties button to get information on the LIM that corresponds to the CAP ATU-C port selected. When the CAP ATU-C Port field is Trained, the dialog box also displays port information such as upstream and downstream rate.

5.2 Cisco 6100 Series System Entities and Containment Hierarchy

To fully understand states and their impact on system operations, you may find some background in terminology helpful. Key terminology includes entities and the containment hierarchy.

• An entity is an item in the user interface representing a discoverable or provisionable item. There are physical entities and logical entities. An example of a physical entity is a module. An example of a logical entity is a subscriber.

• The Cisco 6100 Series system software employs the concept of a containment hierarchy for propagating state changes between various entities.

Figure 5-3 illustrates the specific containment hierarchy model used to propagate state changes between various entities.

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/subordinate resource relationships are also important when you are managing
resource deletions. See "Deleting System Components," for more information on deleting entities.

5.3 State Detection and Propagation

The Cisco 6100 Series system states are detected by means of a polling algorithm. Thus, ViewRunner retrieves state information from the Cisco 6100 Series system when dialog boxes are opened. ViewRunner for Windows provides a Refresh button in each Status dialog box allowing you to refresh the current state information.

The data is not real-time. For example, if a particular modem's Usage state is Idle, and if you pressed the Refresh button before beginning the process of removing that modem from the pool, you might disconnect a subscriber who accessed that modem just after your refresh action.

5.4 Usage State

The Usage state indicates whether or not the module 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 also indicates that an analog cross-connect exists between an ATU-C modem from the modem pool and a LIM port. Table 5-1 shows each Usage state that can appear on the Status dialog box.

Table 5-1: Usage States

Dialog Box Display	Description
Busy	The entity is 100 percent in use. Normally associated with ports. For a module to be Busy, all of its subordinate ports must be busy.
Idle	The entity is not in use.
Active	The entity is in use, but has more capacity. For example, a module is Active when one but not all of its subordinate ports are busy. The Active state provides a quick check for any subordinate resources that are in use. Active states apply to modules, logical pools, chassis, and nodes.

5.5 Slot State

The Slot state identifies whether a module has been detected by the Cisco 6100 Series system as present and whether a configuration or managed object representation exists for that module in the node. When a module is detected, a managed object is automatically generated. Table 5-2 describes Slot states.

Table 5-2: Slot States

Dialog Box Display	Description
Empty Unprovisioned	Neither a module nor a module-managed object exists. Entity-managed object is not supported in this release.
Empty Provisioned	A module managed object exists, but the system has not detected the presence of the module since power up or since the previous deletion of the managed module configured (for that slot). This state is not supported in this release.
Filled Invalid	The module detected is invalid for the slot.
Filled Mismatch	This state indicates the module detected does not match the managed object module type configured for the slot.
Filled Valid	A module-managed object exists and the module type is present. For slots in the LCC1, a LIM controller module must be equipped in the LCC and must be communicating with a previously detected MC. For slots in the MC, an SC module must be equipped in the MC.

1LCC = line concentration chassis

In addition to the Slot state value, ViewRunner for Windows displays below the Slot state field the type of module that has been discovered just below the Slot state field. For ATU-C modules, the words "Direct Connect" or "Digital Off-Hook" are appended to the module name. The actual
words depend on how the module is jumpered. Refer to the Cisco 6100 Series Direct Connect Installation Guide or the Cisco 6100 Series Set Up and Installation Manual for more detail on CAP ATU-C jumpering.

5.6 Service State Functions

The SC monitors states when a particular port or connection is available. For example, the SC 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. The Service state is derived from a combination of Administrative, Operational and Supporting Entity Service states. Table 5-3 describes the Service states.

Table 5-3: Service States

Display Box Display	Description
In Service	The resource has all necessary permission and can provide service when requested.
Out-of-Service	One or more assigned or derived attributes of the resource prevent it from providing service.

If a supporting entity's Service state is 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 its supporting entity's Service state. Therefore, if the supporting entity in the containment hierarchy has a Service state of Out-of-Service, then all of its subordinate entities are also Out-of-Service.

5.7 Supporting Entity Service State

All entities' states change depending on the setting of the supporting entity's state. The Cisco 6100 Series system's Service state describes whether an entity is able to provide service. Service state is derived from a combination of Administrative, Operational and Supporting Entity Service states.

Table 5-4 describes the Supporting Entity Service states.

Table 5-4: Supporting Entity Service States

Dialog Box Display	Description
In Service	All resources that this resource depends on can provide service when requested.
Out-of-Service	A resource that this resource depends on cannot provide service.

5.8 Administrative State

The Administrative state serves two purposes. It enables you to lock an entity to prevent it from providing service, and it provides a mechanism for triggering state changes in the Cisco 6100 Series system configuration.

The Status tab displays the Administrative state for an entity. The Configuration tab lets you both display and modify the entity's Administrative state. To access the Administrative state, select
the Configuration tab on any entity's Property dialog box. In this release, 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 5-5 describes the Administrative states.

Table 5-5: Administrative States

Dialog Box Display	Description
Locked	Entity does not have administrative permission to perform its function.
Unlocked	Entity has administrative permission to perform its function.

As Administrative state is a component of the Service state. If the Administrative state is Locked, the Service state becomes Out-of-Service.

5.8.1 Locking an Actively Connected Entity

ViewRunner for Windows requires you to carefully evaluate whether or not to administratively lock an entity's use. Locking an entity takes it Out-of-Service and terminates any active calls.

ViewRunner for Windows requires the highest level entity to be administratively locked before you execute an action that results in ViewRunner locking subordinate entities. This guarantees that possible configuration changes are not sent to an In-Service entity without forcing a transition to the Unlocked state first.

5.8.2 Service Affecting Configuration Rules

ViewRunner for Windows requires an entity to be locked before it allows modification or deletion of the entity's service-affecting configuration parameters. 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 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 non service-affecting parameters while they are unlocked, and it allows selection of the OK or Apply button.

When the OK or Apply button is selected, ViewRunner for Windows determines the configuration modifications you requested. If only nonservice-affecting data has changed, ViewRunner proceeds with modifying the entity's Administrative state.

5.8.3 Automatic Locking and Unlocking

In some instances, ViewRunner for Windows sends lock messages to the Cisco 6100 Series system without an explicit state change. Done for convenience, this eliminates tedious lock operations when locking is clearly required before further action can be taken.

ViewRunner for Windows performs automatic locks under the following conditions:

• Deletion of an LCC---ViewRunner for Windows requires the LIM controller to be locked for the chassis to be deleted. ViewRunner for Windows automatically locks all LIMs, ports, and subscribers before deleting all of the module configurations. If the LIM controller is not locked, the Delete Chassis option is dimmed.

• Deletion of CAP ATU-C or LIMs---ViewRunner for Windows requires the module to be locked. ViewRunner for Windows automatically locks all of the module's ports before deleting the module configuration.

ViewRunner enforces rules that restrict entity unlocking with the following exception: LIM ports can be unlocked if they are assigned to a pool.

---

Note The above user interface rule is required to prevent the Cisco 6100 Series system from making DOH connection attempts on unassigned LIM ports. LIM ports must be Locked unless they are assigned to a pool. Therefore, ViewRunner disables the LIM port unlocking until the port is assigned to a pool. Conversely, ViewRunner prevents LIM port release from a pool unless the port is Locked.

---

• PVC configuration required---A subscriber cannot be Unlocked unless that subscriber has at least one PVC configured. This rule prevents DOH connection attempts when a port cannot pass ATM cells.

5.9 Operational State

Operational states specify whether or not the resource is in an alarmed condition. Operational states cannot be changed; State is a display-only field in the Port Status dialog box.

Table 5-6 describes the ViewRunner for Windows Operational states.

Table 5-6: Operational States

Dialog Box Display	Description
Enabled	The resource is not in an alarm state. The resource is partially or fully operable and can provide service when so requested.
Disabled	The resource is currently in an alarm state due to a fault being detected. The resource is inoperable and unable to provide service.

The Operational state signals that a fault has been detected for a resource and provides details of specific alarms or the severity of the alarm. 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 the severity of each. Operational state alarms also display on the module ejector tabs at the Chassis View. The alarms and the corresponding colors are listed in order of severity in Table 5-7.

Table 5-7: Operational State Alarms

State	Color
Blue	Provisioned
Red	Critical Alarm
Orange	Major Alarm
Green	No Alarms

5.10 Fault Tolerant State

Fault Tolerant states identify those modules that can operate in either Active or Standby mode.

Table 5-8 describes the Fault Tolerant modes of Active, Standby and Aligning.

Posted: Mon Oct 4 14:13:48 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.