This page is intended to describe use of HCoS inside Circuit Cross-Connect - CCC environment.In order to guarantee dedicated bandwidth along CCC path it is necessary to apply traffic classifiers at the ingress and hierarchical schedulers and shapers at the egress. Using 2 Juniper MX204 routers and 2 DELL PowerEdge R520 servers we will simulate production GTS scenario. These devices are regular part of Prague's laboratory on which it is allowed access with known credentials.
Physical layout
Logical layout
IP Addresses used on devices
| Device | IP Address | Interface | Purpose |
|---|---|---|---|
| HCoS#1 | 10.1.1.10 | iDrac | web access for management |
| 10.1.1.21 | em1 | ssh access for configuration | |
| 192.168.0.1 | p3p2 | HCoS#1-A iPerf client | |
| 192.168.1.1 | p3p1 | HCoS#1-C iPerf client | |
| HCoS#2 | 10.1.1.11 | iDrac | web access for management |
| 10.1.1.22 | em1 | ssh access for configuration | |
| 192.168.2.1 | p4p2 | HCoS#2-D iPerf client | |
| 192.168.0.2 | p4p1.10 | HCoS#2-B iPerf server for point-to-point with HCoS#1-A iPerf client | |
| 192.168.1.2 | p4p1.20 | HCoS#2-B iPerf server for point-to-point with HCoS#1-C iPerf client | |
| 192.168.2.2 | p4p1.30 | HCoS#2-B iPerf server for point-to-point with HCoS#2-D iPerf client | |
| MX204#1 | 10.1.0.67 | fxp0 | ssh access for configuration |
| MX204#2 | 10.1.0.131 | fxp0 | ssh access for configuration |