Table E-1 Definition of Status Icons
Icon
|
GUI Element
|
Possible Values
|
|
Node status
|
Active—Node is fully functional.
|
View status
|
Active—All objects in the chosen view are currently Active and fully functional
|
Folder status
|
Active—All objects in the chosen folder are currently Active and fully functional.
|
Admin status
|
Up—Administratively up.
|
Operational status
|
Up—Interface is up.
|
Interface status
|
Active—Interface is Active.
|
Application Server status
(ITP only)
|
Active—The application server is available and application traffic is Active. At least one application server process serving this application server is Active.
|
Application Server Process Associations status
(ITP only)
|
Active—The remote peer at the application server process association is available and application traffic is Active.
|
Links status
(ITP only)
|
Active—The link is currently fully functional.
|
Linksets status
(ITP only)
|
Active—The linkset is currently fully functional.
|
Signaling Gateway Mated Pairs status
(ITP only)
|
Active—The signaling gateway-mated pair is available and application traffic is active.
|
Signaling Point status
ITP only)
|
Active—The signaling point is currently fully functional.
|
GSM Abis Connect status
(RAN-O only)
|
Connected—The node is monitoring local and remote alarm status.
|
UMTS Iub Connect status (RAN-O only)
|
Open—Connection is open and available for traffic.
|
UMTS Iub Alarm status
(RAN-O only)
|
No alarm—No alarm is present.
|
UMTS Iub Redundancy status
(RAN-O only)
|
Active—Active owner of interface
Standby—Standby owner of interface.
|
UMTS Iub Interface status
(RAN-O only)
|
Active—The interface is currently fully functional.
|
Card definition status
|
Active—The card is currently fully functional.
|
RAN-O status
|
Active—The RAN backhaul is currently fully functional.
|
PWE3 Virtual Circuit
|
Active— The virtual circuit is active.
|
Inbound Operational Status
(IPRAN only)
|
Up —Virtual circuit operationally active.
|
Outbound Operational Status
(IPRAN only)
|
Up —Virtual circuit operationally active.
|
APN status
(mSEF only)
|
Active—The APN is currently fully functional.
|
|
Node status
|
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.
|
|
Node status
|
Unknown—The node failed to respond to an SNMP request. The MWTM sets all associated signaling points, linksets, and links to Unknown.
|
Admin status
|
Unknown—Unknown administrative status.
|
Operational status
|
Unknown—Unknown operational status.
Down—Interface is down.
Dormant—Interface is dormant.
Not present—An interface component is missing.
Lower Layer Down—An interface is down because of a lower-layer interface.
|
Interface status
|
Down—The interface is not available.
Unknown—The MWTM cannot determine the current status of the interface.
|
Application Server status
(ITP only)
|
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.
Unknown—The MWTM cannot determine the current status of the application server.
|
Application Server Process status
(ITP only)
|
Unknown—The MWTM cannot determine the current status of the application server process.
|
Application Server Process Associations status
(ITP only)
|
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.
Unknown—The MWTM cannot determine the current status of the application server process association.
|
| |
Links status
(ITP only)
|
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.
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.
|
Linksets status
(ITP only)
|
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.
|
Signaling Gateway Mated Pairs status
(ITP only)
|
Down—The signaling gateway-mated pair is not available.
Inactive—The signaling gateway-mated pair is available, but application traffic has stopped.
Unknown—The MWTM cannot determine the current status of the signaling gateway-mated pair.
|
Signaling Point status
(ITP only)
|
Unknown—The MWTM cannot determine the current status of the signaling point.
|
GSM Abis Connect status
(RAN-O only)
|
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.
|
UMTS Iub Connect status
(RAN-O only)
|
Starting—The shorthaul interface is administratively active, but the backhaul interface is down.
Stopped—Unable to connect to peer in specified time interval. Additional attempts will be tried based on peer request or restart timers.
|
UMTS Iub Alarm status
(RAN-O only)
|
Local Alarm—Indicates local interface problem. The interface has not received synchronization from the GSM node. The node stops transmitting backhaul samples.
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.
|
Card definition status
(RAN-O only)
|
Not Present—Preconfigured but not inserted in the ONS chassis
Failed—Not functional
Unknown—Failed SNMP
|
RAN-O status
(RAN-O only)
|
Failed—None of the shorthaul or IP backhaul interfaces are active.
Unknown—The MWTM cannot determine the current status of the RAN backhaul.
|
PWE3 Virtual Circuit status
|
Down—The virtual circuit is down.
Unknown—MWTM cannot determine the current status of the interface.
|
APN status
(mSEF only)
|
Unknown—The node failed to respond to an SNMP request.
|
|
Node status
|
Warning—The node is active, but one or more associated objects are in Failed, Unavailable, Unknown, or Warning status and are not Ignored.
|
Folder status
|
Warning—At least one object is not Active.
|
Interface status
|
Warning—The interface status is Active, but some underlying facility is not fully functional.
|
Application Server status
(ITP only)
|
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.
|
Application Server Process Associations status
(ITP only)
|
Warning—The application server process association is Active, but some underlying facility is not fully functional.
|
Links status
(ITP only)
|
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.
|
Linksets status
(ITP only)
|
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.
|
Signaling Gateway Mated Pairs status
(ITP only)
|
Warning—The signaling gateway-muted pair is Active, but some underlying facility is not fully functional.
|
Signaling Point status
(ITP only)
|
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.
|
GSM Abis Connect status
(RAN-O only)
|
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.
|
UMTS Iub Connect status
(RAN-O only)
|
Initialized—The connection is starting initialization.
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.
|
| |
UMTS Iub Alarm status
(RAN-O only)
|
Received Alarm—Indicates receive problem in the local node. The remote node stops transmitting backhaul data and indicates a blue alarm.
|
UMTS Iub Interface status
(RAN-O only)
|
Warning—The interface is Active, but some underlying object is not fully functional.
|
Card definition status
(RAN-O only)
|
Warning—Not in configured protection state.
|
RAN-O status
(RAN-O only)
|
Warning—At least one of the shorthaul interfaces or IP backhaul interfaces is not Active.
|
PWE3 Virtual Circuit
|
Warning—At least one of the components of the virtual circuit is not active.
|
APN status
(mSEF only)
|
Warning—An APN instance associated with a top-level APN is not active.
|
|
Node status
|
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.
|
View status
|
Unmanaged—All objects in the chosen view are currently Unmanaged.
|
Application Server Process status
(ITP only)
|
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.
|
Signaling Point status
(ITP only)
|
Unmanaged—The MWTM cannot discover the signaling point. It is not an ITP node.
|
|
Admin status
|
Shutdown—Status is Down.
Testing—Object is in Test mode.
|
Operational status
|
Testing—Object is in Test mode.
|
Application Server status
(ITP only)
|
Shutdown—An administrator has forced the application server to an unavailable state.
|
Application Server Process Associations status
(ITP only)
|
Shutdown—An administrator has forced the application server process association to an unavailable state.
|
Links status
(ITP only)
|
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.
|
Linksets status
(ITP only)
|
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.
|
PWE3 Virtual Circuit
|
Shutdown—The virtual circuit is administratively closed.
|
Signaling Gateway Mated Pairs status
(ITP only)
|
Shutdown—An administrator has forced the signaling gateway-mated pair to an unavailable state.
|
UMTS Iub Connect status
(RAN-O only)
|
Closed—The backhaul interface is active, but the shorthaul is administratively closed.
Closing—Connection closed by administration request.
|
UMTS Iub Alarm status
(RAN-O only)
|
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.
|
Feedback
