Accepted Solutions
Hi!
I wouldn't be that concerned by the individual links and pipes. They will be automatically created for you when you make the SubZones. You can acheive what you want in your simple deployment with just the Subzone configuration. Unlimited bandwith within a subzone, and limit the calls out of it to all other subzones or zones.
1: Create 4 subzones on your VCS.
VCS configuration > Local Zone > Subzones.
2: For each Subzone, create a membership rule.
I would guess that the TYPE can be SUBNET. So as a membership rule, add the subnet for the location corresponding to that subzone.
VCS configuration > Local Zone > Subzone membership rules.
Subnet address and prefix length
These two fields together determine the range
of IP addresses that will belong to this subzone.
(Applies only if the Type is Subnet.)
The Address range field shows the range of
IP addresses to be allocated to this subzone,
based on the combination of the Subnet
address and Prefix length.
If you have a network at site ONE that has a IP network address 10.1.1.0 as a C-net, the membership rule should be:
Subnet address: 10.1.1.0
Prefix length 24
If you have a network at site TWO that has a IP network address 10.1.2.0 as a C-net, the membership rule should be:
Subnet address: 10.1.2.0
Prefix length 24
and so on...
3: Configure the Subzones limitations for your four subzones
As you can see, you do not need to configure individual links and pipes, unless you want to do more advanced limitations between your locations.
//Robert
Hi
just think about it this way
subzone total will be unlimited as a total
however the links like point to point links/connection each with a pip that make bandwidth limit between two wubzones only
in other words you need a link for every two subzones
S1 to S2 ( bidirectional no need to S2 to S1 )
S1 to S3
S2 to S3
un in each link you apply the pips
but keep in mind that you want to limit the number of calls/bandwidth for the sites with 1152 at any time then you need to use that pip for every link belong to that site
for example S1 has to be lmited for 1152 only
then you create a pip called S1_pip apply to each link belong to S1
S1 to S1 node one/pip S!_pip
S1_S3 node one/Pip S_pip
see the bellow example from VCS admin guide
in the above example head office subzone uses two link one to home office and the other to branch office
however both links using same pip so ifyou have the pip total bandwidth as 1152 that mean as a total for head office to comunicate with any other osubzones at a given time it wont reach 1152 even the zubzone setting total set to unlimited ( two layers of bandwidth control here )
hope this help
good luck
In above scenario:
I know i'll have to have links from each location (I should say "subzone") to other locations so as to make successful call.
as in above diagram, a pipe at each location (subzone) would be enough or would I have to create pipe for each link going to each location (subzone)?
Please help...
Hi!
I wouldn't be that concerned by the individual links and pipes. They will be automatically created for you when you make the SubZones. You can acheive what you want in your simple deployment with just the Subzone configuration. Unlimited bandwith within a subzone, and limit the calls out of it to all other subzones or zones.
1: Create 4 subzones on your VCS.
VCS configuration > Local Zone > Subzones.
2: For each Subzone, create a membership rule.
I would guess that the TYPE can be SUBNET. So as a membership rule, add the subnet for the location corresponding to that subzone.
VCS configuration > Local Zone > Subzone membership rules.
Subnet address and prefix length
These two fields together determine the range
of IP addresses that will belong to this subzone.
(Applies only if the Type is Subnet.)
The Address range field shows the range of
IP addresses to be allocated to this subzone,
based on the combination of the Subnet
address and Prefix length.
If you have a network at site ONE that has a IP network address 10.1.1.0 as a C-net, the membership rule should be:
Subnet address: 10.1.1.0
Prefix length 24
If you have a network at site TWO that has a IP network address 10.1.2.0 as a C-net, the membership rule should be:
Subnet address: 10.1.2.0
Prefix length 24
and so on...
3: Configure the Subzones limitations for your four subzones
As you can see, you do not need to configure individual links and pipes, unless you want to do more advanced limitations between your locations.
//Robert
Hi,
I'm running across an issue.
requirement is: unit with subZone can use unlimited bandwidth, while calls between subzone can use 1152K bandwidth. but calls between units within the same subZone are using on 1152K bandwidth. attached is the screenshot.
Please help!
P.S: when I created subZones manually, VCS created links from those subZones to defaultZones only. it didn't create links between manually created subZones. I had to manually create a link.
