Cisco TRC5 CTS-RMT-TRC5= User Manual
Product codes
CTS-RMT-TRC5=
17
Deployment Details
August 2012 Series
17
Procedure 7
Configure VCS subzones
Cisco VCS uses the concept of zones and subzones to define where
devices are registered on the network. The proper location of devices is
important to allow Cisco VCS to protect the expensive WAN resources in the
underlying network. After the location of devices is defined, additional set-
tings called links and pipes are used to control the number of calls allowed
between sites.
devices are registered on the network. The proper location of devices is
important to allow Cisco VCS to protect the expensive WAN resources in the
underlying network. After the location of devices is defined, additional set-
tings called links and pipes are used to control the number of calls allowed
between sites.
The local zone is a container of subzones local to Cisco VCS. VCS automati-
cally creates a cluster zone, default zone, default subzone, and traversal
subzone. Additional subzones are created to segment the video endpoints
into their respective locations. Figure 2 below shows the relationship
between the zones and subzones.
cally creates a cluster zone, default zone, default subzone, and traversal
subzone. Additional subzones are created to segment the video endpoints
into their respective locations. Figure 2 below shows the relationship
between the zones and subzones.
Figure 2 - Relationship between zones and subzones in Cisco VCS
1064
Traversal Subzone:
For calls between
H.323 and SIP
Local Zone
Default
Zone
Default
Subzone
Traversal
Subzone
User Created Subzone:
For endpoints who match
the criteria specified
for different locations
Default Subzone:
For endpoints who do not
match the criteria for the
user created subzones
Cluster Zone:
For calls from other
cluster members
User
Created
Subzones
Cluster
Zone
Default Zone:
For calls from an
unknown zone
A subzone is created for the HQ location, as well as one for each remote site
location. Figure 3 shows the subzones and IP address ranges in blue as they
are defined in the foundation architecture.
location. Figure 3 shows the subzones and IP address ranges in blue as they
are defined in the foundation architecture.
Figure 3 - Subzones in foundation architecture
MCU
Subzone: SZ_HQ
IP Subnet: 10.4.0.0/17
IP Subnet: 10.4.0.0/17
Subzone: SZ_Remote_2
IP Subnet: 10.5.80.0/21
IP Subnet: 10.5.80.0/21
Nexus 5500
Unified CM
Unity Connection
Data Center
Firewalls
Firewalls
WAN
Router
Internet Edge
Firewalls & RA-VPN
WAN Routers
Wireless LAN
Controllers
WAAS
Access
Switches
Distribution
Layer 6500
VSS Switch
Layer 6500
VSS Switch
ACE
WAAS
Central
Manager
Nexus
2000
Storage
UCS Rack-mount Servers
for NTP, DNS, and Syslog
Access
Switch
Collapsed
LAN Core
LAN Access
Remote Site
1065
User
Teleworker /
Mobile Worker
MPLS
WANs
WANs
Internet
PSTN
Headquarters
Data Center
WAN Aggregation
Internet Edge
Access
Switch
Stack
WAN
Routers
Remote Site
WAAS
Wireless
IP Phone
Wireless
IP Phone
IP Phone
Wireless
IP Phone
IP Phone
V
V
V
V
V
Executive
System
Video
Communication
Servers
Communication
Servers
Mulitpurpose
Room System
Subzone: SZ_Remote_1
IP Subnet: 10.5.0.0/21
IP Subnet: 10.5.0.0/21
Executive
System
Mulitpurpose
Room System
The default subzone is not used, and any rogue endpoints registered to it
cannot make calls to the authorized endpoints in the user-created subzones.
Bandwidth control among sites is done using links and pipes as outlined
below, so you will not utilize the subzone bandwidth settings.
cannot make calls to the authorized endpoints in the user-created subzones.
Bandwidth control among sites is done using links and pipes as outlined
below, so you will not utilize the subzone bandwidth settings.
Create one subzone for each location that has video endpoints.
Step 1:
From the master VCS, navigate to
VCS configuration > Local Zone
> Subzones
, and then click
New
.
Step 2:
On the Create subzone page, in the
Name
box, enter
SZ_HQ
,
and
then click
Create subzone.