User Manual
Product information and planning
9500 MPR Rel. 3.1
3DB18809AAAA Issue 1182/980
2.8.16.3 SDH2SDH
STM-1 traffic packetized only internally to 9500 MPR-E equipment.
Figure 91. STM-1 Traffic
Flow Id present (user defined)
If there are intermediate nodes in each node build the Cross-connection tables based on Flow Id.
Bandwidth guaranteed (according to QoS o Highest Queue Priority association)
No flooding-autolearning necessary
Both the IWFs belong to 9500 MPR-E and the packets are not supposed to exit the 9500 MPR-E network.
The IWF parameters listed above, have predetermined values and don’t need to be provisioned.
– Mac addresses are determined as consequences of the cross connections.
– Payload size is fixed
– Clock source: clock recovery differential/node timing
– Flow Id provisioned by ECT/NMS
2.8.16.4 ETH2ETH
None of the IWFs belongs to 9500 MPR-E.
None of the parameters listed in the previous slide has to be configured (the 9500 MPR-E is transparent).
Figure 92. E1 Traffic
Any packet belonging to an Eth2Eth TDM flow is treated as any other Ethernet packet with the only
exception of giving it an higher priority based on the MEF 8 Ethertype.
Eth
Eth
RNC
Eth
Eth
WiMAX
(NodeB)
WiMAX
(NodeB)
WiMAX
(NodeB)
Eth
Eth
Eth
RNC
PSNPSN
PSNPSN
To Next Page
Loading...
