User Guide for Mobile Wireless Transport Manager 5.0 - Appendix A--MWTM Status Definitions [Cisco Mobile Wireless Transport Manager]

Table Of Contents

MWTM Status Definitions

Status Definitions for Interfaces

Admin Status

Operational Status

Connect State for GSM Abis

Connect State for UMTS Iub

Alarm States

Redundancy State

Status

Status Definitions for Nodes

Status Definitions for Views

MWTM Status Definitions

This appendix defines the default status settings for all MWTM network objects.

This appendix includes the following information:

•Status Definitions for Interfaces

•Status Definitions for Nodes

•Status Definitions for Views

Status Definitions for Interfaces

This section provides definitions for the following statuses:

•Admin Status

•Operational Status

•Connect State for GSM Abis

•Connect State for UMTS Iub

•Alarm States

•Redundancy State

•Status

Admin Status

Possible values for the administrative status of the interface are:

Unknown—Unknown administrative status

Up —Administratively up

Shutdown—Administratively down

Testing—Administrator is testing the interface

Operational Status

Possible values for the operational status of the interface are:

Unknown—Unknown operational status.

Up —Interface is up.

Down—Interface is down.

Testing—Interface is in test mode.

Dormant—Interface is dormant.

Not Present —An interface component is missing.

Lower Layer Down —An interface is down because of a lower-layer interface.

Connect State for GSM Abis

Possible values for the connect state of a GSM interface are:

Connected —The device is monitoring local and remote alarm status.

Disconnected—The system ignores the local alarm status. The local transmitter on the short-haul is disabled. Capabilitymessages are transmitted to the remote describing the provisioning. The system stays disconnected until the remote capabilities are known and the peer state is transitioned to connected.

Send Connect —One or more attempts have been made to connect to remote peer.

Receive Connect —The local-peer has received a connect request from the remote-peer.

Connect Rejected —Connection was rejected.

ACK Connect —The initial connect request was sent and acknowledged by remote-peer. The local-peer is now waiting for a connect request from the remote-peer.

Check Connect —The local peer has reason to believe its remote peer has failed. Additional tests are being processed to verify peer's state.

Connect State for UMTS Iub

Possible values for the connect state of a UMTS interface are:

Initialized —The connection is starting initialization.

Starting—The shorthaul interface is administratively active, but the backhaul interface is down.

Closed—The backhaul interface is active, but the shorthaul is administratively closed.

Stopped—Unable to connect to peer in specified time interval. Additional attempts will be tried based on peer request or restart timers.

Closing—Connection closed by administration request.

Stopping —Connection shut down by peer's Term-Request. Will transition to stopped state.

Connect Sent —Connection request sent to peer.

ACK Received —Connection request sent and acknowledgement has been received from peer. Now waiting for peer's connection request.

ACK Sent —Connection request received and acknowledgement has been sent to peer. Connection request sent and waiting for peer's acknowledgement.

Open —Connection open and available for traffic.

Alarm States

The alarm states for a UMTS Iub interface include the following:

•Local Receive Alarm State

•Local Transmit Alarm State

•Remote Receive Alarm State

•Remote Transmit Alarm State

Possible values for these alarm states are:

Remote Alarm —Indicates a problem at the remote end. The alarm generated by the remote interface in the E1/T1 data stream is sent and no other action is required.

No Alarm —No alarm is present.

Local Alarm —Indicates local interface problem. The interface has not received synchronization from the GSM device. Device stops transmitting backhaul samples.

Received Alarm —Indicates receive problem in the local device. The remote device stops transmitting backhaul data and indicates a blue alarm.

Alarm State Unavailable —Indicates the alarm state is not available. This state only applies to the remote and occurs when the peer connection is inactive.

Redundancy State

Possible values for the redundancy state of GSM Abis or UMTS Iub interfaces are:

Active—Active owner of interface.

Standby—Active owner of interface.

Status

Possible values for the status of an interface are:

Active

DiscoveringDown

Polling

Unknown

Unmanaged

Waiting

Warning

Status Definitions for Nodes

Possible values for the current status of the node are:

Active—The node is currently fully functional.

Discovering—The node is being discovered, and SNMP queries have been sent to the device.

Polling—The node is being polled.

Unknown—The node failed to respond to an SNMP request. MWTM sets all associated interfaces to Unknown.

Unmanaged—One of the following situations exists:

–The node is known indirectly by MWTM. In other words, MWTM knows the device exists but there is no known SNMP stack on the device for MWTM to query.

–An MWTM user has set the node to Unmanaged status to prevent MWTM from polling the node.

Waiting—The node is in the Discovery queue but is not currently being discovered.

Warning—The node is active, but one or more interfaces is in Failed, Unavailable, Unknown, or Warning status and is not Ignored.

Status Definitions for Views

Possible values for the current status of the view are:

Active—All objects in the selected view are currently Active and fully functional.

Unmanaged—All objects in the selected view are currently Unmanaged.

Warning—One or more objects in the selected view is currently not Active.

	User Guide for Mobile Wireless Transport Manager 5.0
	Appendix A--MWTM Status Definitions
User Guide for Mobile Wireless Transport Manager 5.0 About This Document MWTM Overview Discovering Your RAN-O Networks Using MWTM Getting Started with MWTM Working with Views Working with Events Working with Nodes Working with Interfaces Viewing the Topology of the Network Working with MWTM Statistics Reports Configuring MWTM Security Configuring MWTM for Your Network Troubleshooting MWTM and the Network Accessing MWTM Data from the Web Browser Appendix A--MWTM Status Definitions Appendix B--MWTM FAQs Appendix C--MWTM Command Reference Appendix D--MWTM MIB Reference Appendix E--MWTM Trap Reference Appendix F--Configuring MWTM to Run with Various Networking Options Appendix G--MWTM Statistics Export File Formats Appendix H--MWTM and Ports Appendix I--Open Source License Notices for the Cisco Mobile Wireless Transport Manager Glossary Index	Download this chapter Appendix A--MWTM Status Definitions Download the complete book Cisco Mobile Wireless Transport Manager User Guide (PDF - 5 MB) Feedback Table Of Contents MWTM Status Definitions Status Definitions for Interfaces Admin Status Operational Status Connect State for GSM Abis Connect State for UMTS Iub Alarm States Redundancy State Status Status Definitions for Nodes Status Definitions for Views MWTM Status Definitions This appendix defines the default status settings for all MWTM network objects. This appendix includes the following information: •Status Definitions for Interfaces •Status Definitions for Nodes •Status Definitions for Views Status Definitions for Interfaces This section provides definitions for the following statuses: •Admin Status •Operational Status •Connect State for GSM Abis •Connect State for UMTS Iub •Alarm States •Redundancy State •Status Admin Status Possible values for the administrative status of the interface are: Unknown—Unknown administrative status Up —Administratively up Shutdown—Administratively down Testing—Administrator is testing the interface Operational Status Possible values for the operational status of the interface are: Unknown—Unknown operational status. Up —Interface is up. Down—Interface is down. Testing—Interface is in test mode. Dormant—Interface is dormant. Not Present —An interface component is missing. Lower Layer Down —An interface is down because of a lower-layer interface. Connect State for GSM Abis Possible values for the connect state of a GSM interface are: Connected —The device is monitoring local and remote alarm status. Disconnected—The system ignores the local alarm status. The local transmitter on the short-haul is disabled. Capabilitymessages are transmitted to the remote describing the provisioning. The system stays disconnected until the remote capabilities are known and the peer state is transitioned to connected. Send Connect —One or more attempts have been made to connect to remote peer. Receive Connect —The local-peer has received a connect request from the remote-peer. Connect Rejected —Connection was rejected. ACK Connect —The initial connect request was sent and acknowledged by remote-peer. The local-peer is now waiting for a connect request from the remote-peer. Check Connect —The local peer has reason to believe its remote peer has failed. Additional tests are being processed to verify peer's state. Connect State for UMTS Iub Possible values for the connect state of a UMTS interface are: Initialized —The connection is starting initialization. Starting—The shorthaul interface is administratively active, but the backhaul interface is down. Closed—The backhaul interface is active, but the shorthaul is administratively closed. Stopped—Unable to connect to peer in specified time interval. Additional attempts will be tried based on peer request or restart timers. Closing—Connection closed by administration request. Stopping —Connection shut down by peer's Term-Request. Will transition to stopped state. Connect Sent —Connection request sent to peer. ACK Received —Connection request sent and acknowledgement has been received from peer. Now waiting for peer's connection request. ACK Sent —Connection request received and acknowledgement has been sent to peer. Connection request sent and waiting for peer's acknowledgement. Open —Connection open and available for traffic. Alarm States The alarm states for a UMTS Iub interface include the following: •Local Receive Alarm State •Local Transmit Alarm State •Remote Receive Alarm State •Remote Transmit Alarm State Possible values for these alarm states are: Remote Alarm —Indicates a problem at the remote end. The alarm generated by the remote interface in the E1/T1 data stream is sent and no other action is required. No Alarm —No alarm is present. Local Alarm —Indicates local interface problem. The interface has not received synchronization from the GSM device. Device stops transmitting backhaul samples. Received Alarm —Indicates receive problem in the local device. The remote device stops transmitting backhaul data and indicates a blue alarm. Alarm State Unavailable —Indicates the alarm state is not available. This state only applies to the remote and occurs when the peer connection is inactive. Redundancy State Possible values for the redundancy state of GSM Abis or UMTS Iub interfaces are: Active—Active owner of interface. Standby—Active owner of interface. Status Possible values for the status of an interface are: Active DiscoveringDown Polling Unknown Unmanaged Waiting Warning Status Definitions for Nodes Possible values for the current status of the node are: Active—The node is currently fully functional. Discovering—The node is being discovered, and SNMP queries have been sent to the device. Polling—The node is being polled. Unknown—The node failed to respond to an SNMP request. MWTM sets all associated interfaces to Unknown. Unmanaged—One of the following situations exists: –The node is known indirectly by MWTM. In other words, MWTM knows the device exists but there is no known SNMP stack on the device for MWTM to query. –An MWTM user has set the node to Unmanaged status to prevent MWTM from polling the node. Waiting—The node is in the Discovery queue but is not currently being discovered. Warning—The node is active, but one or more interfaces is in Failed, Unavailable, Unknown, or Warning status and is not Ignored. Status Definitions for Views Possible values for the current status of the view are: Active—All objects in the selected view are currently Active and fully functional. Unmanaged—All objects in the selected view are currently Unmanaged. Warning—One or more objects in the selected view is currently not Active.
	Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks