Motorola 68241 User Guide - Page 25

RFC877 Multiprotocol Encapsulation, First byte of the Call User Data CUD of Call Request will be CC.

Get Motorola 68241 - Vanguard 312 Router PDF manuals and user guides View all Motorola 68241 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 25 highlights

WAN Adapter RFC877 Multiprotocol Encapsulation Overview RFC877 encapsulation specifies transporting of IP using NLPID (Network Layer Protocol Identification) over X.25. The Vanguard Router rejects all RFC877 LCON calls for other protocols. When RFC877 encapsulation is selected, the IP datagram encapsulation is as follows: • First byte of the Call User Data (CUD) of Call Request will be "CC." • The IP datagram is sent as part of X.25 data. There are no other headers or trailers. Motorola's Version of RFC887 Motorola's version of RFC877 deviates from standard RFC877 where specification of Router Maximum Transmission Unit (MTU) size is derived via WAN packet size negotiation at the X.25 layer. Instead, the Vanguard Router supports a configurable MTU size as specified in RFC1356, described below. Otherwise, the Motorola version complies with all RFC877 requirements. Refer to the IP Interface Configuration Table menu for more information on MTU size. RFC877 Limitations The following limitations apply to the use of RFC877: • Bridging and other routed protocols are not supported. • Only one RFC877 incoming LCON call is supported. The incoming call is assigned the lowest RFC877 LCON. Additional RFC877 calls are not accepted. Note: Any number (up to a maximum of 254) of outgoing RFC877 LCONs can be set up. • The RFC877 option of parallel SVCs between two routers is not supported. When interoperating in a Cisco or Proteon network configured for Extended LANView, you must turn off parallel SVC support on their routers. • The Q-bit must not be set in the data packets. If the Q-bit is set, the call is cleared. Vanguard Routing Model T0100-01, Revision B 2-9 Release 5.4

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
Vanguard Routing Model
2-9
T0100-01, Revision B
Release 5.4
WAN Adapter
RFC877 Multiprotocol Encapsulation
Overview
RFC877 encapsulation specifies transporting of IP using NLPID (Network Layer
Protocol Identification) over X.25. The Vanguard Router rejects all RFC877 LCON
calls for other protocols.
When RFC877 encapsulation is selected, the IP datagram encapsulation is as
follows:
•
First byte of the Call User Data (CUD) of Call Request will be “CC.”
•
The IP datagram is sent as part of X.25 data. There are no other headers or
trailers.
Motorola’s Version
of RFC887
Motorola’s version of RFC877 deviates from standard RFC877 where specification
of Router Maximum Transmission Unit (MTU) size is derived via WAN packet size
negotiation at the X.25 layer. Instead, the Vanguard Router supports a configurable
MTU size as specified in RFC1356, described below. Otherwise, the Motorola
version complies with all RFC877 requirements. Refer to the IP Interface
Configuration Table menu for more information on MTU size.
RFC877 Limitations
The following limitations apply to the use of RFC877:
•
Bridging and other routed protocols are not supported.
•
Only one RFC877 incoming LCON call is supported. The incoming call is
assigned the lowest RFC877 LCON. Additional RFC877 calls are not
accepted.
Note:
Any number (up to a maximum of 254) of outgoing RFC877 LCONs
can be set up.
•
The RFC877 option of parallel SVCs between two routers is not supported.
When interoperating in a Cisco or Proteon network configured for Extended
LANView, you must turn off parallel SVC support on their routers.
•
The Q-bit must not be set in the data packets. If the Q-bit is set, the call is
cleared.