Cisco TelePresence Administrator's Manual page 282

Grey Headline (continued)
Command reference - xStatus
Searches:
Current:
Total:
Dropped:
Zone [1..1000]:
Name: <S: 1,50 Node name>
Bandwidth:
LocalUsage: <0..100000000>
ClusterUsage: <0..100000000>
Status: <Active/Failed/Warning>
Cause: {Visible if status is Failed or Warning} <System unreachable/ Systems unreachable>
Type: <Neighbor/TraversalClient/TraversalServer/ENUM/DNS>
Neighbor: {Visible if Type is Neighbor}
Peer [1..6]:
H323: {Visible if H323 Mode=On for Zone}
Status: <Unknown/Active/Failed>
Cause: {Visible if Status is Failed} <No response from gatekeeper/DNS resolution failed/Invalid IP address>
Address: <IPv4Addr/IPv6Addr> {One Address line per address from DNS lookup}
Port: <1..65534>
LastStatusChange: <Time not set/Date Time>
SIP: {Visible if SIP Mode=On for Zone}
Status: <Unknown/Active/Failed>
Cause: {Visible if Status is Failed} <No response from gatekeeper/DNS resolution failed/Invalid IP address>
Address: <IPv4Addr/IPv6Addr> {One Address line per address from DNS lookup}
Port: <1..65534>
LastStatusChange: <Time not set/Date Time>
TraversalClient: {Visible if Type is TraversalClient}
Peer [1..6]:
H323: {Visible if H323 Mode=On for Zone}
Status: <Unknown/Active/Failed>
Cause: {Visible if Status is Failed} <No response from gatekeeper/DNS resolution failed/Invalid alias/Authentication Failed/Invalid IP address>
Overview and System
Introduction
status configuration
D14049.08
November 2010
Cisco VCS Zones and Clustering and
configuration neighbors peers
Call Bandwidth
processing control
282
CISCO TELEPRESENCE VIDEO COMMUNICATION SERVER
Firewall
Applications Maintenance
traversal
ADMINISTRATOR GUIDE
Appendices