Table Of Contents
Status Definitions
General Status Definitions
Status Definitions for Nodes
Status Definitions for Views
Status Definitions for Folders
Status Definitions for Interfaces
Admin Status
Operational Status
Status
ITP Status Definitions
Status Definitions for Application Servers
Status Definitions for Application Server Processes
Status Definitions for Application Server Process Associations
Status Definitions for ITP Interfaces
Admin Status
Operational Status
Status
Status Definitions for Links
Status Definitions for Linksets
Status Definitions for Signaling Gateway Mated Pairs
Status Definitions for Signaling Points
RAN-O Status Definitions
Status Definitions for RAN-O Interfaces and Virtual Circuits
Admin Status
Operational Status
Connect State for GSM Abis
Connect State for UMTS Iub
Alarm States
Redundancy State
Status
Status Definitions for Cards
Status Definitions for RAN-O and PWE3 Backhauls
mSEF Status Definitions
Status Definitions for APNs
Status Definitions
This appendix defines the default status settings for all Cisco Mobile Wireless Transport Manager (MWTM) network objects.
This appendix contains:
•
General Status Definitions
•
ITP Status Definitions
•
RAN-O Status Definitions
•
mSEF Status Definitions
General Status Definitions
The following status definitions apply to both ITP, IPRAN, and mSEF networks:
•
Status Definitions for Nodes
•
Status Definitions for Views
•
Status Definitions for Folders
•
Status Definitions for Interfaces
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 Simple Network Management Protocol (SNMP) queries have been sent to the node.
•
Polling—The node is being polled.
•
Unknown—The node failed to respond to an SNMP request. The MWTM sets all associated signaling points, linksets, or links to Unknown.
•
Unmanaged—One of these situations exists:
–
The node is known indirectly by the MWTM. In other words, the MWTM knows the node exists but there is no known SNMP stack on the node for the MWTM to query.
–
An MWTM user has set the node to Unmanaged status, to prevent the MWTM from polling the node.
(ITP only) If the associated signaling points are referenced via linksets to other signaling points, the MWTM automatically sets all associated signaling points to Unmanaged, and deletes all associated linksets and links, as well as all linksets and links that reference the node as an adjacent node.
(ITP only) If the associated signaling points are not referenced to other signaling points, the MWTM automatically deletes the signaling points, all associated linksets and links, and all linksets and links that reference the node as an adjacent node.
•
Waiting—The node is in the Discovery queue but is not currently being discovered.
•
Warning—The node is active, but one or more associated objects are in Failed, Unavailable, Unknown, or Warning status and are not Ignored.
Status Definitions for Views
Possible values for the current status of the view are:
•
Active—All objects in the chosen view are currently Active and fully functional.
•
Unmanaged—All objects in the chosen view are currently Unmanaged.
•
Warning—One or more objects in the chosen view is currently not Active.
Status Definitions for Folders
Possible values for folders (such as Physical and Mgmt Interfaces) are:
•
Active—All objects in the chosen folder are currently Active and fully functional.
•
Warning—At least one object is not Active.
Status Definitions for Interfaces
This section provides definitions for these statuses:
•
Admin Status
•
Operational Status
•
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.
Status
Possible values for the status of an interface are:
•
Active
•
Down
•
Unknown
•
Warning
ITP Status Definitions
ITP status definitions include this information:
•
Status Definitions for Application Servers
•
Status Definitions for Application Server Processes
•
Status Definitions for Application Server Process Associations
•
Status Definitions for ITP Interfaces
•
Status Definitions for Links
•
Status Definitions for Linksets
•
Status Definitions for Signaling Gateway Mated Pairs
•
Status Definitions for Signaling Points
Status Definitions for Application Servers
Possible values for the current status of the application server are:
•
Active—The application server is available and application traffic is active. At least one application server process serving this application server is Active.
•
Down—The application server is not available. All application server processes that serve this application server are Down. This is the initial status for application servers.
•
Inactive—The application server is available, but no application traffic is active (that is, at least one application server process is Inactive, and no application server process is Active).
•
Pending—The last remaining Active application server process serving this application server has become Inactive or Down. The next status for this application server will be Active, Inactive, or Down, depending on the recovery timer, and whether an application server process can become Active.
•
Shutdown—An administrator has forced the application server to an unavailable state.
•
Unknown—The MWTM cannot determine the current status of the application server.
•
Warning—The application server is Active, but one of these conditions exists:
–
At least one application server process association for this application server is not fully functional.
–
A signaling gateway-mated pair has been defined for this signaling point, but no application server exists on the mate.
–
The mate's application server is not Active.
Status Definitions for Application Server Processes
Possible values for the current status of the application server process are:
•
Unknown—The MWTM cannot determine the current status of the application server process.
•
Unmanaged—The MWTM cannot determine the status of the application server process because there is no known SNMP stack on the node that hosts this application server process for the MWTM to query.
Status Definitions for Application Server Process Associations
Possible values for the current status of the application server process association are:
•
Active—The remote peer at the application server process association is available and application traffic is active.
•
Blocked—The application server process association cannot receive normal data traffic, but it can send and receive control messages.
•
Down—The remote peer at the application server process association is not available, or the related SCTP association is down. This is the initial status for application server process associations.
•
Inactive—The remote peer at the application server process association is available, and the related SCTP association is up, but application traffic has stopped. The application server process association should not receive any data or SNMP messages for the application server.
•
Pending—The last remaining Active application server process serving this application server process association has become Inactive or Down. The next status for this application server process association will be Active, Inactive, or Down, depending on the recovery timer, and whether an application server process can become Active.
•
Shutdown—An administrator has forced the application server process association to an unavailable state.
•
Unknown—The MWTM cannot determine the current status of the application server process association.
•
Warning—The application server process association is Active, but some underlying facility is not fully functional.
Status Definitions for ITP Interfaces
This section provides definitions for these statuses:
•
Admin Status
•
Operational Status
•
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.
Status
Possible values for the status of an interface are:
•
Active
•
Down
•
Unknown
•
Warning
Status Definitions for Links
Possible values for the current status of the link are:
•
Active—The link is currently fully functional.
•
Blocked—Traffic on this link is disabled by protocol.
•
Failed—An error is preventing traffic from flowing on this link, or the associated linkset has been set to Shutdown status.
A link can be Failed from an MTP3 perspective, but control messages might still be sent or received on the link, resulting in changing packet/second and bit/second rates. The rates might also be different at each end of the link, depending on the reason for the failure and the timing related to each endpoint.
•
InhibitLoc—A local ITP administrator has set the link to prevent traffic from flowing.
•
InhibitRem—A remote ITP administrator has set the link to prevent traffic from flowing.
•
Shutdown—An ITP administrator has set the link to prevent traffic from flowing.
•
Unknown—Either the node associated with this link has failed to respond to an SNMP request, or the MWTM found that the link no longer exists.
When you physically delete a link, the Status field shows Unknown until you delete the link from the MWTM database.
•
Warning—The link is active and traffic is flowing, but one or more of these situations has occurred:
–
The link is congested.
–
The link has exceeded the defined Receive % or Send %.
–
One or more of the local or remote IP addresses defined for SCTP is not active.
Status Definitions for Linksets
Possible values for the current status of the linkset are:
•
Active—The linkset is currently fully functional.
•
Shutdown—An ITP administrator has set the linkset to prevent traffic from flowing. When a linkset is set to Shutdown, all its associated links are set to Failed by Cisco IOS.
•
Unavailable—An error is preventing traffic from flowing on this linkset.
•
Unknown—Either the node associated with this linkset has failed to respond to an SNMP request, or the MWTM found that the linkset no longer exists.
•
Warning—The linkset is active, but one or more links in the linkset is congested or is in Failed, Unknown, or Warning status, and is not Ignored. At least one link is available and can carry traffic.
Status Definitions for Signaling Gateway Mated Pairs
Possible values for the current status of the signaling gateway-mated pair are:
Active—The signaling gateway-mated pair is available and application traffic is active.
Down—The signaling gateway-mated pair is not available.
Inactive—The signaling gateway-mated pair is available, but application traffic has stopped.
Shutdown—An administrator has forced the signaling gateway-mated pair to an unavailable state.
Unknown—The MWTM cannot determine the current status of the signaling gateway-mated pair.
Warning—The signaling gateway-mated pair is Active, but some underlying facility is not fully functional.
Status Definitions for Signaling Points
Possible values for the current status of the signaling point are:
Active—The signaling point is currently fully functional.
Unknown—The MWTM cannot poll the node associated with the signaling point.
Unmanaged—The MWTM cannot discover the signaling point. It is not an ITP node.
Warning—The signaling point is active, but one or more associated links or linksets is in Failed, Unavailable, Unknown, or Warning status and is not flagged as Ignored.
RAN-O Status Definitions
RAN-O status definitions include this information:
•
Status Definitions for RAN-O Interfaces and Virtual Circuits
•
Status Definitions for Cards
•
Status Definitions for RAN-O and PWE3 Backhauls
Status Definitions for RAN-O Interfaces and Virtual Circuits
This section provides definitions for these 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 or virtual circuit 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 or virtual circuit 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 Global System for Mobile Communications (GSM) interface are:
Connected—The node is monitoring local and remote alarm status.
Disconnected—The system ignores the local alarm status. The local transmitter on the short-haul is disabled. Capability messages are transmitted to the remote describing the provisioning. The system stays disconnected until the remote capabilities are known and the peer state transitions 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 Universal Mobile Telecommunications System (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:
•
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 node. The node stops transmitting backhaul samples.
Received Alarm—Indicates receive problem in the local node. The remote node 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—The interface is currently fully functional.
Down—The interface is not available.
Unknown—The MWTM cannot determine the current status of the interface.
Warning—The interface is Active, but some underlying object is not fully functional.
Status Definitions for Cards
Possible values for cards in Cisco Optical Networking System (ONS) nodes are:
Active—The card is currently fully functional.
Not Present—Preconfigured but not inserted in the ONS chassis
Failed—Not functional
Warning—Not in configured protection state
Unknown—Failed SNMP
Status Definitions for RAN-O and PWE3 Backhauls
Possible values for RAN and PWE3 backhauls are:
Active—The RAN backhaul is currently fully functional.
Unknown—The MWTM cannot determine the current status of the RAN backhaul.
Warning—At least one of the shorthaul interfaces or IP backhaul interfaces is not active
Failed—None of the shorthaul or IP backhaul interfaces are active
mSEF Status Definitions
mSEF status definitions include the following:
•
Status Definitions for APNs
Status Definitions for APNs
Possible values for the current APN status include:
Active—The APN is currently fully functional.
Warning—An APN Instance associated with a top-level APN is not active.
Unknown—The node failed to respond to an SNMP request.