Currently peering with the IIX
(in order of connecting):
Peer Name | Size | Type | Status | IPv6 | Backup Link | Redundancy | Status | ![]() |
10Gb/s | 10GE | ![]() |
Active | ![]() |
---|---|---|---|---|---|---|---|
![]() |
100GE | 100GE | ![]() |
Active | 100Gb/s | ![]() |
|
![]() |
100Gb/s | 100GE | ![]() |
Active | 100Gb/s | ![]() |
|
![]() |
100Gb/s | 100GE | ![]() |
Active | 100Gb/s | ![]() |
![]() |
200Mb/s | GE | ![]() |
![]() |
![]() |
20Gb/s | 10GE | ![]() |
Active | Yes | ![]() |
![]() |
40Gb/s | 40GE | ![]() |
Active | 40Gb/s | ![]() |
![]() |
1Gb/s | GE | ![]() |
Active | ![]() |
![]() |
1Gb/s | GE | ![]() |
Active | ![]() |
![]() |
10Gb/s | 10GE | ![]() |
![]() |
![]() |
40Gb/s | 10GE | ![]() |
Active | ![]() |
![]() |
20Gb/s | 10GE | ![]() |
Active | Yes | ![]() |
![]() |
200Gb/s | 100GE | ![]() |
Active | 200Gb/s | ![]() |
![]() |
100Mb/s | GE | ![]() |
Active | 100Mb/s | Yes | ![]() |
![]() |
100Gb/s | 100GE | ![]() |
Active | ![]() |
![]() |
100Mb/s | GE | ![]() |
Active | ![]() |
![]() |
100Gb/s | 100GE | ![]() |
Active | 100Gb/s | ![]() |
![]() |
40Gb/s | 10GE | ![]() |
Active | ![]() |
![]() |
200Gb/s | 100GE | ![]() |
Active | Yes | ![]() |
![]() |
40Gb/s | 40GE | ![]() |
Active | ![]() |
![]() |
200Gb/s | 100GE | ![]() |
Active | Yes | ![]() |
Note:
- Backup line – 2nd peer on standby, not forwarding traffic.
- Redundancy – 2nd peer where both peers are active and forwarding traffic.
Adding up the speed figures of the Shared GigE connected Peers in the above table, may result in a figure that is larger than the nominal IIX GigE trunks speed. This does not imply “overbooking”, or oversubscription of the access lines.
Traffic distribution in multiplexed networks is statistical. The correct way to check for trunk utilization would, therefore, be to go over some statistics.