Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Bandwidth
Link Status
The Link status page (Status > Bandwidth > Links) lists all of the links currently configured on the VCS, along with
the number of calls and the bandwidth being used by each link.
the number of calls and the bandwidth being used by each link.
The following information is displayed:
Field
Description
Name
The name of each link. Clicking on a link Name takes you to the configuration page for that link.
Calls
The total number of calls currently traversing the link. Note that a single call may traverse more than
one link, depending on how your system is configured.
one link, depending on how your system is configured.
Bandwidth
used
used
The total bandwidth of all the calls currently traversing the link.
Pipe Status
The Pipe status page (Status > Bandwidth > Pipes) lists all of the pipes currently configured on the VCS, along with
the number of calls and the bandwidth being used by each pipe.
the number of calls and the bandwidth being used by each pipe.
The following information is displayed:
Field
Description
Name
The name of each pipe. Clicking on a pipe Name takes you to the configuration page for that pipe.
Calls
The total number of calls currently traversing the pipe. Note that a single call may traverse more than
one pipe, depending on how your system is configured.
one pipe, depending on how your system is configured.
Bandwidth
used
used
The total bandwidth of all the calls currently traversing the pipe.
Policy Server Status and Resiliency
You must specify a Status path when configuring the VCS's connection to a policy server. It identifies the path from
where the status of the remote service can be obtained. By default this is status.
where the status of the remote service can be obtained. By default this is status.
Up to 3 different policy server addresses may be specified. The VCS polls each address on the specified path every 60
seconds to test the reachability of that address. The VCS accepts standard HTTP(S) response status codes. (Note
that the developers of the policy service must ensure that this provides the appropriate status of the service.)
seconds to test the reachability of that address. The VCS accepts standard HTTP(S) response status codes. (Note
that the developers of the policy service must ensure that this provides the appropriate status of the service.)
If a server does not respond to status requests, VCS will deem that server's status to be in a failed state and it will not
be queried for policy service requests until it returns to an active state. Its availability will not be checked again until
after the 60 second polling interval has elapsed.
be queried for policy service requests until it returns to an active state. Its availability will not be checked again until
after the 60 second polling interval has elapsed.
When the VCS needs to make a policy service request, it attempts to contact the service via one of the configured
server addresses. It will try each address in turn, starting with Server 1 address, and then if necessary - and if
configured - via the Server 2 address and then the Server 3 address. The VCS only tries to use a server address if it
is in an active state, based on its most recent status query.
server addresses. It will try each address in turn, starting with Server 1 address, and then if necessary - and if
configured - via the Server 2 address and then the Server 3 address. The VCS only tries to use a server address if it
is in an active state, based on its most recent status query.
The VCS has a non-configurable 30 seconds timeout value for each attempt it makes to contact a policy server.
However, if the server is not reachable, the connection failure will occur almost instantaneously. (Note that the TCP
connection timeout is usually 75 seconds. Therefore, in practice, a TCP connection timeout is unlikely to occur as
either the connection will be instantly unreachable or the 30 second request timeout will occur first.)
However, if the server is not reachable, the connection failure will occur almost instantaneously. (Note that the TCP
connection timeout is usually 75 seconds. Therefore, in practice, a TCP connection timeout is unlikely to occur as
either the connection will be instantly unreachable or the 30 second request timeout will occur first.)
The VCS uses the configured Default CPL if it fails to contact the policy service via any of the configured addresses.
323
Cisco TelePresence Video Communication Server Administrator Guide