Legacy Data System Reference - Comtech EF Data
Legacy Data System Reference - Comtech EF Data
Legacy Data System Reference - Comtech EF Data
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
12.10 X25 Port<br />
12.10.1 X25 frame relay encapsulation<br />
SE/PORT Configuration Parameters<br />
Console SNMP Text-based Config<br />
X25 frame relay encapsulation<br />
ifwanX25Encapsulation [ifwan#]<br />
X25Encapsulation<br />
For X25 protocol only.<br />
Defines how the X.25 traffic will be handled by the NetPerformer HDLC driver. In<br />
particular, it specifies which encapsulation technique is used to get the X.25 traffic<br />
through the Frame Relay network:<br />
• ANNEX-F: FRF.3 Annex F deals with multiprotocol support over Frame Relay.<br />
With Annex-F encapsulation, a frame identifier header is added to the normal<br />
frame to differentiate the various protocols. In the case of X.25, this identifier<br />
consists of a 6-byte suite. When an X.25 frame is received by the NetPerformer<br />
HDLC driver, it is stripped of its leading and trailing flags, as well as its CRC.<br />
Then a Frame-Relay header (2 bytes of DLCI) and a 6-byte frame identifier is<br />
added to the X.25 frame before transmission. The X.25 frame is integrally copied<br />
into a Frame Relay frame (LAPB header and data). All types of frames (INFO,<br />
UI, SUPERVISOR) are copied in the same way.<br />
• ANNEX-G: FRF.3 Annex F deals with CCITT X.25 encapsulation over Frame-<br />
Relay. With Annex-G encapsulation, an X.25 frame received by the NetPerformer<br />
HDLC driver is stripped of its leading and trailing flags, as well as its<br />
CRC. It is then integrally copied into a Frame Relay frame. All frame types that<br />
are received on the HDLC port (INFO, UI, SUPERVISOR) are encapsulated.<br />
Values: ANNEX-F, ANNEX-G<br />
Default: ANNEX-G<br />
Memotec Inc. 12-21
Change language