ATM Option System Reference - Comtech EF Data

More documents

Recommendations

Info

ATM Option - The CLP field of every ATM cell generated by the segmentation process is set to a constant value (0 or 1). This value is configured separately for each PVC. • ATM-to-FR direction: - If one or more cells belonging to an ATM frame has its CLP field set to 1, the DE field is also set to 1 in the corresponding Frame Relay frame. On the Net- Performer this is the default mode. - No mapping is performed from the ATM layer to FR layer. The DE field of the Frame Relay frame is set to a constant value (0 or 1), which is configured separately for each PVC. Congestion Indication Mapping The NetPerformer provides both forward and backward congestion indication. • Congestion is detected when the queue size goes above the threshold defined by the Congestion Queue Size parameter for the PVC. • A second threshold, the Maximum Queue Size parameter, determines when frame discarding is required. • On the NetPerformer, forward congestion indication is supported at the frame level with Forward Explicit Congestion Notification (FECN), and at the cell level with Explicit Forward Congestion Indication (EFCI). • Congestion Indication Forward in the FR-to-ATM direction: Two modes are available: - The value of the Frame Relay FECN field is mapped to the ATM EFCI field of every cell generated by the segmentation process. On the NetPerformer this is the default mode. - No mapping is performed from the FR layer to the ATM layer.The EFCI field of every ATM cell is set to a constant value (0 or 1). This value is configured separately for each PVC. If there is congestion at the ATM layer in the forward direction, the IWF can set the EFCI field to 1 no matter which mode is configured. • Congestion Indication Forward in the ATM-to-FR direction: Two modes are available: - The value of the ATM EFCI field is mapped to the FECN field of the Frame Relay frame. On the NetPerformer this is the default mode. - The FECN field of every ATM cell is set to a constant value (0 or 1). This value is configured separately for each PVC. • Congestion Indication Backward: The Frame Relay Backward Explicit Congestion Notification (BECN) field has no equivalent in ATM. - In the FR-to-ATM direction, the BECN field is ignored. - In the ATM-to-FR direction, the BECN field is set to 1 if a congestion situation is detected by the NetPerformer in the FR-to-ATM direction. 1-20 Memotec Inc.
Product Overview - Congestion is determined using the Congestion Queue size parameter. Command/Response Field Mapping This involves a different process in different directions: • FR-to-ATM direction: The Frame Relay C/R field is mapped to the Common Part Convergence Sublayer – User to User (CPCS-UU) Least Significant Bit (LSB) of the CPCS PDU. • ATM-to-FR direction: The CPCS-UU LSB is mapped to the C/R field. • In both directions the NetPerformer handles the mapping internally, with no PVC configuration required. DLCI Field Mapping • With FRF.8 there is a one-to-one mapping between the Frame Relay DLCI and the ATM VPI/VCI. Transparent versus Translation Mode FRF.8 specifies two operating modes for user protocol encapsulation at the upper layer: • Transparent Mode: The IWF leaves the user data unchanged. No mapping, fragmentation or reassembly is performed. • Translation Mode: The IWF maps the Frame Relay RFC-1490 frames to ATM RFC-1483 CPCS Protocol Data Units (PDU) and vice versa, as shown in Figure 1-8. - When the IWF receives fragmented packets on a Frame Relay PVC, it reassembles them before forwarding them to the ATM PVC. - In the reverse direction, fragmentation is performed on the received CPCS PDU before forwarding the fragmented packets to the Frame Relay PVC. • Each FRF.8 PVC is configured separately for transparent versus translation mode: - For Transparent Mode, set the Header Translation parameter to NO. Memotec Inc. 1-21
Page 1 and 2: ATM Option NetPerformer ® System R
Page 3 and 4: Contents Chapter 1: Product Overvie
Page 5 and 6: 4. 10 ILMI Channel VCI . . . . . .
Page 7 and 8: 5.8.1 ATM Adaptation Layer . . . .
Page 9 and 10: Product Overview 1 Memotec Inc. 1-1
Page 11 and 12: Product Overview and higher capacit
Page 13 and 14: 1.2.2 Error Checking 1.2.3 Cell Tra
Page 15 and 16: Product Overview • Another diffic
Page 17 and 18: 1.2.7 ATM Addressing Product Overvi
Page 19 and 20: NOTE: Service categories can be def
Page 21 and 22: 1.3 ATM Support on the NetPerformer
Page 23 and 24: Product Overview 7. Link to another
Page 25 and 26: Product Overview The NetPerformer p
Page 27: Product Overview page 1-21). Howeve
Page 31 and 32: 1.3.5 PPP Over AAL5 Product Overvie
Page 33 and 34: AAL0 Adaptation Layer Product Overv
Page 35 and 36: Product Overview On the SDM-9360A,
Page 37 and 38: SVC Modes Supported Product Overvie
Page 39 and 40: Configuration 2 Memotec Inc. 2-1
Page 41 and 42: Configuration When you execute the
Page 43 and 44: Unit ID> (main prompt) Figure 2-1:
Page 45 and 46: SE/GLOBAL example: with ATM license
Page 47 and 48: Configuration Included in this calc
Page 49 and 50: SE/SLOT example: with data channels
Page 51 and 52: 2.5 Configuring the Digital Link Co
Page 53 and 54: 2.6 Configuring the ATM Channel Con
Page 55 and 56: 2.7 Configuring the ATM PVCs Config
Page 57 and 58: SE/PVC/ ATMPVCR example: on the SDM
Page 59 and 60: 2.7.2 PVC in AAL1 Mode SE/PVC/AAL1
Page 61 and 62: SE/PVC/ RFC1483 example Configurati
Page 63 and 64: 2.7.6 PVC in ATM-MULTIPLEX Mode SE/
Page 65 and 66: 2.8.1 SVC in ATMPVCR Mode SE/SVC/ A
Page 67 and 68: SE/SVC/ ATMPVCR example: ANSWER Typ
Page 69 and 70: 2.8.4 SVC in ATMPPP Mode SE/SVC/ AT
Page 71 and 72: 2.9 Configuration Examples Configur
Page 73 and 74: SE/PVC/#/ ATMPVCR example PVC Confi
Page 75 and 76: Monitoring and Statistics 3 Memotec
Page 77 and 78: Monitoring and Statistics NOTE: Vie
Page 79 and 80:
Monitoring and Statistics SVC 1> Nu
Page 81 and 82:
SVC Status Console SNMP SVC Status
Page 83 and 84:
DSVC/ATM example Monitoring and Sta
Page 85 and 86:
3.3 Status of ATM PVCs DC/PVC examp
Page 87 and 88:
DE/PVC example Monitoring and Stati
Page 89 and 90:
3.4 Viewing Reserved Channels DP/GL
Page 91 and 92:
3.5 Status of ATM Channels DC/SLOT
Page 93 and 94:
SE/SLOT/CHANNEL Configuration Param
Page 95 and 96:
4.4 Scrambling function 4.5 UNI Ver
Page 97 and 98:
4.8 ATM Signaling Channel VCI SE/SL
Page 99 and 100:
SE/PVC Configuration Parameters 5 M
Page 101 and 102:
SE/PVC Configuration Parameters Val
Page 103 and 104:
5.3.3 Service category Values: SDM-
Page 105 and 106:
5.3.6 Maximum burst size (MBS) in c
Page 107 and 108:
SE/PVC Configuration Parameters NOT
Page 109 and 110:
5.3.16 IP RIP SE/PVC Configuration
Page 111 and 112:
5.3.20 OSPF face on both sides of t
Page 113 and 114:
5.3.24 OSPF Hello interval 5.3.25 O
Page 115 and 116:
5.3.29 IP multicast protocol 5.3.30
Page 117 and 118:
5.3.34 Broadcast group SE/PVC Confi
Page 119 and 120:
5.3.37 Cell Packetization SE/PVC Co
Page 121 and 122:
SE/PVC Configuration Parameters of
Page 123 and 124:
SE/PVC Configuration Parameters M-l
Page 125 and 126:
5.4.12 TONE ON (ms) 5.4.13 TONE OFF
Page 127 and 128:
5.4.16 Fwd digits SE/PVC Configurat
Page 129 and 130:
5.5 FRF.8 Mode 5.5.1 Port 5.5.2 DLC
Page 131 and 132:
SE/PVC Configuration Parameters •
Page 133 and 134:
5.5.8 Frame relay DE bit 5.5.9 Fram
Page 135 and 136:
5.6 RFC1483 Mode 5.6.1 BRG connecti
Page 137 and 138:
5.8.2 Remote PVC number 5.8.3 Class
Page 139 and 140:
SE/SVC Configuration Parameters 6 M
Page 141 and 142:
6.3 ATMPVCR Mode 6.3.1 SVC Destinat
Page 143 and 144:
6.3.7 Call Retry Delay 6.3.8 Peak c
Page 145 and 146:
Index A AAL service classes 1-4 AAL
Page 147 and 148:
IP RIP password 5-12 IP RIP TX/RX 5
Page 149 and 150:
ATM Option 5
show all

ATM Option System Reference - Comtech EF Data

Create successful ePaper yourself

Delete template?

Save as template?