342-86400-498PS
Issue 1.2
April 2012
Page 38
Copyright
GE Multilin Inc. 2010-2012
t
2
t
1
TDM Pipe #1
TDM Pipe #2
TDM Pipe #3
TDM Pipe #4
Time
5
7
6
2
0
3
7
6
5
3
2 0
6
5
2
6
5
2
2
7
7
t
2
t
1
TDM Pipe #1
TDM Pipe #2
TDM Pipe #3
TDM Pipe #4
Time
5
7
6
2
0
3
7
6
5
3
2 0
6
5
2
6
5
2
2
7
7
NOTE: Each colored “slice” indicates traffic at different priority level
Figure 25:
TDM pipe bandwidth utilization (example)
IMPORTANT NOTES
- Any given D-PVLAN can belong to one and only one TDM pipe.
- A paddleboard port can belong to only one D-PVLAN, so all QVLANs that
are accessing the ETHER-1000 system through the same paddleboard port
will use the same TDM pipe.
- If a paddleboard port is forced to certain source & mapping priority, all
QVLANs ingressing the port will have the same priority.
- If the QVLANs ingressing the same paddleboard port are supposed to have
different priorities, their prioritization must be carried out outside the
JungleMUX system (typically on the external switch) and passed onto the
JungleMUX system using source priority.
- Traffic being locally added/dropped to/from different TDM pipes is combined
on the drop side of the ETHER-1000 unit.
“Add” frames are competing for
the GMII port‟s add bandwidth (1 Gbps) based on their
EtherType
/
source
priority
designations, while the “drop” frames are competing for the GMII
port‟s drop bandwidth (1 Gbps) based on their
mapping priority
designations.
(The frame‟s source and mapping priority are assigned at the frame‟s source
port i.e. the port at which the frame enters the ETHER-1000 system.)
