Motorola 110502USM001 - Vanguard 60 Router, Vanguard 100, Vanguard 200, Vanguard 6520, Vanguard 6560 User Manual

Motorola

Vanguard Applications Ware

IP and LAN Feature Protocols

Vanguard Router Basics

POWER

STATUS

SERVICE

RESET

Notice

©1999 Motorola, Inc.
20 Cabot Boulevard
Mansfield, Massachusetts 02048
[phone]
All rights reserved
Printed in U.S.A.

Restricted Rights Notification for U.S. Government Users

The software (including firmware) addressed in this manu al is provided to the U.S.
Government under agreement which grants the government the minimum “restricted rights”
in the software, as defined in the Federal Acquisition Regulatio n (FAR) or the Defense
Federal Acquisition Regulation Supplement (DFARS), whichever is applicable.

If the software is procured for use by the Department of Defense, the following legend
applies:

Restricted Rights Legend

Use, duplication, or disclosure by the Government

is subject to restrictions as set forth in

subparagraph (c)(1)(ii) of the

Rights in Technical Data and Computer Software

clause at DFARS 252.227 -70 13 .

If the software is procured for use by any U.S. Government entity other than the Department
of Defense, the following notice applies:

Notice

Notwithstanding any other lease or license agreement that may pertain to,
or accompany the delivery of, this computer software, the rights of the
Government regarding its use, repr odu cti o n, and disclos ure are as set forth
in F A R 52.227 -19 (C ).

Unpublished - rights reserved under the copyright laws of the United States.

Notice (continued)

Proprietary Material

Information and software in this document are proprietary to Mo torola, Inc. (o r its Suppliers)
and without the express prior permission of an officer of Motorola, may not be copied,
reproduced, disclosed to others, publi s hed, or used, in whol e or i n p art , f or any purpose other
than that for which it is being made available. Use of soft ware de scribed in this document is
subject to the terms and conditions of the Motorola Software License Agreement.

This document is for information purposes only and is subject to change without notice.

To comment on this manual, please send e-mail to [e-mail]

Part No. T0100-01, Rev B
Publication Code: KP
First Printing: November 1998

Manual is current for Release 5.4 of Vanguard Applications Ware.

Contents

v

Vanguard Router Basics

Chapter 1. Introduction to Vanguard IP and LAN Feature Protocols

IP and LAN Protocol Support ...................................................................... 1-2

Physical LAN Connectivity ..................................................................... 1-3

LAN Forwarding Options ........................................................................ 1-4

Network Layer - Routing ......................................................................... 1-5

RFC ............................................................................................................... 1-7

Chapter 2. Vanguard Routing Model

Functional Overview of the Vanguard Router Model .................................. 2-2

IP Forwarder ................................................................................................. 2-3

WAN Adapter ............................................................................................... 2-4

LCON Encapsulation ............................................................................... 2-6

Codex Proprietary Encapsula tion ............................................................. 2-7

RFC1294 Multiprotocol Encapsulation ................................................... 2-8

RFC877 Multiprotocol Encapsula tion ..................................................... 2-9

RFC1356 Multiprotocol Encapsulation ................................................... 2-10

LAN Connection Encapsulation Examples .............................................. 2-11

WAN Port ..................................................................................................... 2-13

WANView and LANView ............................................................................ 2-14

WANView - Point to Point LCON ............................................................... 2-16

LANView of the WAN - Group LCONs ...................................................... 2-17

LANView Examples ................................................................................ 2-21

RTP/UDP/IP Header Compression ............................................................... 2-25

How RTP/UDP/IP Compression and Decompression Occurs ................. 2-28

Using Bridging Routers to Connect LANs and Networks ........................... 2-31

Chapter 3. Configuring a Vanguard Router

Configuration ................................................................................................ 3-2

Example WANView Configuration - Point-to-Point LCONs .................. 3-5

Example LAN View Configuration - Group LCONs .............................. 3-7

Configure LAN Connections ........................................................................ 3-9

LAN Connection Parameters Menu ......................................................... 3-10

Configuring LAN Connection Table ........................................................ 3-11

LAN Connection Table Record Parameters ............................................. 3-16

vi

Contents (continued)

Chapter 4. LAN Connection Statistics

Using LAN Connection Statistics ................................................................. 4-2

LAN Connection Statistics ....................................................................... 4-3

LAN Connection Summary Statistics ...................................................... 4-8

RTP/UDP/IP Compression Statistics ....................................................... 4-9

LAN Connection Group Statistics ............................................................ 4-12

Index

Introduction to Vanguard IP and LAN Feature Protocols 1-1

Chapter 1

Introduction to Vanguard IP and LAN

Feature Protocols

Overview

Introduction This chapter introd uce s t he key features and protocols supported by t he Vanguard IP

Applications Ware. You will find a summary of the major Request for Comments
(RFCs) supported by Vanguard IP Applications Ware.

1-2 Introduction to Vanguard IP and LAN Feature Protocols

IP and LAN Protocol Support

IP and LAN Protocol Support

Introduction Motorola’s Vanguard Applications Ware support a wide option of LAN and Internet

Protocol functionality and options. Figure 1-1 lists some of the functionality
supported by the Vanguard IP Applications Ware.

Figure 1-1. Vanguard IP Protocol Support

Physical Layer

Data Link Layer

Network Layer

Transport Layer

Application Layer

Ethernet (802.3) Token Ring (802.5)

Bridging

Internet Protocol (IP)

OSPF DVMRP

ICMP

TCP

SNMP

TELNET

RIP

BOOTP

UDP

IPX

Appletalk

Frame Relay, PPP, X.25, ISDN, SMDS,
Multilink PPP

Slim IP SoTCP

Introduction to Vanguard IP and LAN Feature Protocols 1-3
T0100-01, Revision B Release 5.4

IP and LAN Protocol Support

Physical LAN Connectivity

Introduction The Vanguard products offer serial interfaces for connection to Ethernet and Token

Ring LAN.

Ethernet 802.3 Vanguard Ethernet functionality complies with the IEEE 802.3 specifications and

provides Transparent Bridging to transport many different protocols over the Wide
Area Network (WAN) to remote dest inations. Supported protocols include:

• Novell Netware

•DECnet

• Banyan Vines

Token Ring 802.5 Vanguard Token Ring LAN functionality complies with the IEEE 802.5

specifications and provides Source Route Bridging to transport many different
protocols over the Wide Area Network (WAN) to a remote destination. Some of the
supported protocols include:

• Novell NetWare

• SDLC Cluster Controller

• IBM PC LAN

• NetBIOS

• IBM 3270 Emulation 3.0

• IBM APPC

See the IEEE 802.5 specification for additional details on Token Ring functionality.

1-4 Introduction to Vanguard IP and LAN Feature Protocols

IP and LAN Protocol Support

LAN Forwarding Options

Introduction The Vanguard products supports three forwarding options for carry traffic and

interconnecting LANs. The Vanguard can act as a:

•Bridge

•Router

• Bridge Router (BRouter)

Bridging

Bridges work at the Data Link layer providing connectionless service.

Vanguard
products support bridging of data traffic for Token Ring and Ethernet LANs.
Bridging LAN traffic minimizes your networking costs by eliminating the need for
redundant networks and maximizes the availability of dedicated facilities such as
servers and printers, as well as public Frame Relay and X.25 services, across
multiple LANs. The Vanguard supports these types of bridging

• Translational Bridging

• Source Route Bridging for Token Ring

• Transparent Bridging

Routing Router interconnect network segments and transport data across an network from a

source to a destination. Routers store and forward data in an network regardless of
network topology.

Routers operate at the Network layer and, therefore, offer some

flexibility in choosing several network level services.

Bridge Routing When configured as a bridging router, the Vanguard supports both bridging and

routing within the same node concurrently. The Vanguard provide bridging router
functions including

• Routing packets if a specific routing protocol is globally enabled.

• Filtering packets if you configure specific protocol filters.

• Bridging packets if they are not routed or filtered. In this case, they are
forwarded according to their destination MAC address.

Introduction to Vanguard IP and LAN Feature Protocols 1-5
T0100-01, Revision B Release 5.4

IP and LAN Protocol Support

Network Layer - Routing

Introduction This section highlights routing features and protocols supported by the Vanguard IP

Applications Ware.

Internet Protocol
(IP) Routing

The Internet Protocol is a connectionless packet delivery protocol that performs
addressing, delivery, processing and control for transporting data packets over a
network.

Motorola’s implementation of IP Routing supports these protocol and features:

• ARP (Address Resolution Protocol)

• RIP version 1 and version 2 (Routing Information Protocol)

• On Demand RIP

• OSPF

• Default Gateway and Default Subnet Gateway

• IP Broadcast Handling

• IP Multicast Routing - IGMP (Internet Group Multicast Protocol) and
DVMRP support

• IP Address Filtering and Access Control

• ICMP Router Discovery

• Proxy Routing

• Network Address Translation (NAT)

• Class Inter-Domain Routing (CIDR) for OSPF and static routes

In addition, Motorola IP implementation also offers band width manageme nt
solutions to maximize network performance and availability. These solutions offer:

• Dial on demand routing

• IP load balancing

• Bandwidth on demand

• Data compression

• Bandwidth allocation

• Time of Day link control

• Traffic and Protocol pr ioritization

OSPF The Vanguard supports Open Short Path Fir st Protocol (OSPF) defi ned by RFC 158 3

version 2. OSPF is an Inter ior Gatewa y Protocol (IGP) used t o distribut e informat ion
among routers belonging to an autonomous system (AS). Vanguard implementation
of OSPF offers:

• TOS routing - Packet routing based on Type of Service (TOS)

• Variable Length Subnet Masks — Lets you break an IP addr ess into variable
size subnets, conserving IP address space.

• Routing authenti cation — Provides additional routing security

• CIDR - Classless Interdomain Routing

• IP subnetting and the tagging of externally derived routing information. It
uses IP multicast when sending or receiving packets.

1-6 Introduction to Vanguard IP and LAN Feature Protocols

IP and LAN Protocol Support

SLIM IP Slim Internet Protocol (SIP) is a subset of the IP protocol. SIP is available on the

Vanguard 100, Vanguard 200, Vanguard 6520, and Vanguard 6560. You can install
SIP when the Vanguard needs only the IP functions to communicate between an
SNMP Manager and the internal SNMP Agent. The device does not need to know
how to forward IP traffic. SIP terminates within the Vanguard devices.

SoTCP SoTCP is a proprietary protocol that allows a Vanguard to encapsulate and transport

serial protocols over the IP network. This feature allows terminal and host devices
operating serial pr otocols to connect and communicate with each other over an IP
network. This provides a cost-effective alternative to X.25 WAN connection.

IPX The Internetwork Packe t Exchange (IPX) pro tocol is the networ k layer protocol used

in Novell NetWare networks. Vanguard products can serve as IPX routers to
interconnect PC workstations with any Novell server in a LAN/WAN internetwork.

Appletalk The Vanguard supports AppleTalk routing over Ethernet LANs. AppleTalk is a

routable protocol tha t comprises se veral prot ocols develop ed by Apple Compu ter for
intercomputer communication.

Protocol Priority The Vanguard supports prioritization of IP, IPX, Appletalk, Voice over IP, and

transparent bridging traffic so that WAN bandwidth is shared effectively between
them.

Introduction to Vanguard IP and LAN Feature Protocols 1-7
T0100-01, Revision B Release 5.4

RFC

RFC

Introduction The Vanguard IP Applications Ware adheres to global industry standards defined by

IETF and IEEE.

RFCs Supported by
Vangua rd

This table lists some of the RFCs supported by Vanguard IP Applications Ware.

RFC Description

768 User Datagram Protocol.

J. Postel. A ug-28-1980 .

791 Internet Protocol.

J. Postel. Sep-01-1981.

792 Internet Control Message Protocol.

J. Postel. Sep-01-1981.

Note

Not all messages covered by RFC 792 are supported by
Vanguard Applications Ware.

793 Transmission Control Protocol.

J. Postel. Sep-01-1981.

826 An Ethernet Address Resolution Protocol-or-Converting

network protocol addresses to 48.bit Ethernet Address for
Transmission on Ethernet hardware.

D.C. Plummer. Nov-01-1982.

877 Standard For The Transmission Of IP Datagrams Over Public

Data Networks.
J.t. Korb. Sep-01-1983.

919 Broadcasting Internet Datagrams.

J.C. Mogul. Oct-01-1984.

922 Broadcasting Internet datagrams in the presence of subnets.

J.C. Mogul. Oct-01-1984.

950 Internet St andard Subnetting Procedure.

J.C. Mogul, J. Postel. Aug-01-1985.

951 Bootstrap Protocol (BootP).

B. Croft, J. Gilmore. September 1985

1042 Standard For The Transmission Of IP Datagrams Over IEEE

802 Networks.
J. Postel, J.K. Reynolds. Feb-01-1988.

1058 RIP Version 2 Carrying Additional Information.

G. Malkin. January 1993.

1-8 Introduction to Vanguard IP and LAN Feature Protocols

RFC

1155 Structure And Identification Of Management Information For

TCP/IP-based Internets.
M.t. Rose, K. Mccloghrie. May-01-1990.

1157 Simple Network Management Protocol (SNMP).

J.D. Case, M. Fedor, M.L. Schoffstall, C. Davin. May-01-1990.

1209 Transmission Of IP Datagrams Over The SMDS Service.

D.m. Piscitello, J. Lawrence. Mar-01-1991.

1212 Concise MIB Definitions.

M.t. Rose, K. Mccloghrie. Mar-01-1991.

1213 Management Information Base For Network Management Of

TCP/IP-based Internets:MIB-II.
K. Mccloghrie, M.t. Rose. Mar-01-1991.

1231 IEEE 802.5 Token Ring MIB.

K. Mccloghrie, R. Fox, E. Decker. May-01-1991.

1256 ICMP Router Discovery Messages.

S. Deering. September 1991.

1286 Definitions Of Managed Objects For Bridges.

E. Decker, P. Langille, A. Rijsinghani, K. Mccloghrie.
December, 1991.

1294 Multiprotocol Interconnect Over Frame Relay.

T. Bradley, C. Brown, A. Malis. January 1992.

1315 Management Information Base for Frame Rela y DTEs.

C. Brown, F. Baker, C. Carvalho. April 9, 1992.

1398 Definitions Of Managed Objects For The Ethernet-like In terface

T ypes.
F. Kastenholz. January 1993.

1490 Multiprotocol Interconnect Over Frame Relay.

T. Bradley, C. Brown, & A. Malis. July 1993.

1517 Applicability Statement For The Implementation Of Classless

Inter-Domain Routing (CIDR).
Internet Engineering Steering Group, R. Hinden. September

1993.

1518 An Architecture For IP Address Allocation With CIDR.

Y. Rekhter & T. Li. September 1993.

1519 Classless Inter-Domain Routing (CIDR): an Address

Assignment and Aggregation Strategy.
V. Fuller, T. Li, J. Yu, & K. Varadhan. September 1993.

1520 Exchanging Routing I nformation Acr oss Provide r Boundaries in

the CIDR Environment.
Y. Rekhter & C. Topolcic. September 1993.

RFC Description

Introduction to Vanguard IP and LAN Feature Protocols 1-9
T0100-01, Revision B Release 5.4

RFC

1534 Interoperation Between DHCP and B OOTP.

R. Droms. October 1993.

1542 Clarifications an d Extensions for BOOTP.

W. Wimer. October 1993

1631 The Network Address Translation (NAT).

K. Egevang, P. Francis. May 1994.

1812 Requirements for IP Version 4 Routers.

F. Baker. June 1995.

1918 Add ress Allocation for Private Internets.

Y. Rekhter, B. Moskowitz, D. Karrenberg, G. J. de Groot & E.
Lear. February 1996.

2131 Dynamic Host Configuration Protocol.

R.Droms. March 1997.

RFC Description

Vanguard Routing Model 2-1

Chapter 2

V anguard Routing Model

Overview

Introduction Before you attempt to configure a Vanguard device for LAN operation you should

take time to understand how the Vanguard router works. Understanding this unique
routing model will make configuring the Vanguard router easier.

What is in this
Chapter

This chapter provides information on how a Vanguard router interconnects two or
more LANs over a WAN. This chapter will

• describe the key components of the Vanguard routing model

• the concepts of X.25 virtual circuits and how they are used in the Vanguard

• the term LAN connection, LCON - what it means and why is it used.

• LANview and WANview models

• provide basics configuration examples

Note about
Configuration
Examples

The configuration examples provided in this manual highlight the important
parameters that should be configured and do not detail all configurable parameters.
In addition, these examples may not work with your specific network but can be
modified and adapted for your use.

2-2 Vanguard Routing Model

Functional Overview of the Vanguard Router Model

Functional Overview of the Vanguard Router Model

Introduction Vanguard devices provide interconnection of LANs over WAN using a routing

model based on X.25 packet switching technology. Traffic from a LAN port passes
internally to a WAN port via a virtual circuit call. Most other bridge and router
manufacturers configure WAN links based on physical connections only.

Logical Function The Vanguard routing model occurs by three logical functions as shown in

Figure 2-1 and described below:

Figure 2-1. Functional Diagram of Vanguard Routing Model

Function Description

IP Forwarder

The IP Forwarder provides Router, Bridge, or Router-bridge functions. Data traffic from
the LAN por t passes to the IP Forwarder through a v irtual circuit defined by a Router
Interface (1 as shown in Figure 2-1). Depending on the IP Forwarder function configured,
the data traffic is passed to the WAN adaptor through another virtual circuit defined by
another Router Interface (5 as shown in Figure 2-1).The IP Forwarder can have multiple
virtual circuits to the WAN Adaptor.

WAN Adaptor

The WAN Adaptor connects the I P For w ar der to the W AN po rt s v ia a vi rt ual circuit called
the LAN connection, LCON. LCONs uses X.25 based addressing to establish virtual
circuits. The WAN Adaptor encapsulates IP traffic for transport over the WAN. The WAN
Adaptor supports RFC 887, RFC 1294, RFC 1356, RFC 149 0 multip rotoco l encaps ulation .

WAN Port

The Vanguard can connect to Frame Rela y, X.25, MX25, ISDN, Sync PPP, or XDLC
networks.

WAN

LAN

LAN Port

Ethernet

Token Ring

WAN Port

Frame Relay

X.25

MX25

ISDN

Sync PPP

XDLC

Vanguard Router

LAN
Port

1

5

FRI

Port

LCON

FRI

Station

LAN

IP Forwarder

- Bridge

- Router

W AN Adaptor

WAN Po rt

Router

Interface

Vanguard Router

Vanguard Router

WAN

Vanguard Routing Model 2-3
T0100-01, Revision B Release 5.4

IP Forwarder

IP Forwarder

Introduction The IP Forwarder provides the Routing, Bridge, or Bridge-Routing function in the

Vanguard.

Note

For more information on Bridge-Router functions refer to “U sing Bridging
Routers to Connect LANs and Networks” section on page 2-31.

Virtual Circuits
Defined by Router
Interface

The connection point of the IP forwarder to the LAN port is a virtual circuit called a
Router Interface. Each Router Interface has an IP address associated with it. This IP
address must have its network portion equal to the network number to which it
connects.

2-4 Vanguard Routing Model

WAN Adapter

W AN Adapter

Introduction The WAN Adapter is the logical funct ion that co nnects the IP Forwarder t o the WAN

ports. Specifically, the WAN Adaptor:

• Implements the LAN connection (LCON)

• Performs the WAN encapsulation

• Establishes the remote connections using SVCs or PVCs

• Collects and maintains statistics on each remote LAN connection

• Controls data flow

What is an LAN
Connection ­LCON?

The WAN Adaptor connects the IP Forwarder to the WAN ports via a virtual circuit
called the LAN Connection, LCON. LCONs uses X.2 5 based add ressing t o est ablish
virtual circuits.

LAN Protocols LAN protocols serve two purposes:

• Access termination such as traditional serial protocols

• Routing LAN data along pr oper WAN paths

The Vanguard WAN Adapter allows Vanguard LAN software to implement a more
efficient layer of routing.

An overlay network that the LAN routing functions see is superimposed on top of
the actual virtua l circuit network and physi cal network i mplement ed by the Motorola
access devices.

WAN Adaptor
Interconnections

Figure 2-2 shows how the WAN Adapter is used to provide a LAN overlay network.

Figure 2-2. WAN Adapter Interconnections

X.25
Stack

Up To 2000
Connections

Up To 250

Bridge

Links

Up To 254

Router

Interfaces

PVC

SVC

SVC

FR-DCE Port

X.25 Port

FR-DTE Port

Bridge Router

Handler

LAN Port

WAN Adapter

X.25

Stack

Vanguard Routing Model 2-5
T0100-01, Revision B Release 5.4

WAN Adapter

Flow Control Data passed from the LAN protocol stacks to the WAN Adapter may be queued

inside the WAN module. This is due to the relatively low bandwidth of the WAN
port(s) compared with a LAN port and to competition for that limited WAN port
bandwidth with serial data access ports. When this occurs, data flow between the
WAN Adapter and the WAN protocol stack is temporarily halted to allow the WAN
port to reduce its queues to a manageable level. Detection of this condition and
reaction to it is referred to as flow control. Data wai ting for t ransmission onto a WAN
link is kept on an LCON queue. The maximum size of this queue is configurable.

However, data passed from the WAN Adapter to the LAN protocol stacks should be
transmitted almost immediatel y due to the significantly higher bandwidth of the
LAN port compared to the WAN port(s).

Call Disconnection The Vanguard Router uses the X.25 mode for establishing virtual circuits over the

WAN. Connections to remote destinations can be disconnected at any time due to
network failures and operator interventions.

• The WAN Adapter recognizes when it receives a Clear Indication packet that
a call is disconnected and notifies the LAN forwarders.

• The WAN Adapter flushes its flow control queues of any saved packet s.

• If the LAN Connection has an Autocall Mnemonic configured, the WAN
Adapter restarts the ca ll establish ment proce ss.

• If the LAN connection is not configured to autocall, no call establishment
actions occur until receipt of an Incoming Call packet from the remote
destination.

Statistics The WAN Adapter maintains, displays, and resets its statistics independently of the

WAN protocol stack and the LAN protocol stacks. All interaction is through the
standard CTP interface.These statistics are shown in the LAN Connection Statistics
screens.

Summary Status The WAN Adapter provides an LCON Summary Status display that contains

information about a ll configur ed LAN connections , their as sociated br idge-links, and
their associated router interfaces.

2-6 Vanguard Routing Model

WAN Adapter

LCON Encapsulation

Introduction The WAN Adapter encapsulates pr otocol -spec ific i nfo rmatio n in th e dat a pac ket th at

is needed at the remote end of th e conn ect io n. The following encapsulation methods
are used:

• Codex Proprietary encapsulation

• RFC 1294 Multiprotocol encapsulation

• RFC 877 IP encapsulation

You can configure these encapsulation methods in the LAN Connection record.

Vanguard Routing Model 2-7
T0100-01, Revision B Release 5.4

WAN Adapter

Codex Proprietary Encapsulation

Overview The WAN Adapter handles Codex Proprietary encapsulation as follows:

• The WAN Adapter places a 2-byte message trailer in the packet before the
packet is passed to the WAN protocol stack.

• This 2-byte trailer is passed as data by the WAN Adapter stack and is
processed and stripped from the packet by the receiving WAN Adapter.

• The packet is passed to the router or bridge forwarder.

Two-Byte Message
Trailer

This 2-byte field is used as follows:

• Byte 1: Indicates the protocol type of the LAN forwarder, such as SR, STPE,
and IP. The key Protocol IDs are: IP=00, IPX = 07, Motorola Codex SR=64,
Motorola Codex STPE=65, and Motorola Codex TB=66.

• Byte 2: Indicates other packet-specific information. This byte contains
information that is copied from the Control field portion of the Application
field of the packet header. For example, bits in this field indicate whether the
frame’s CRC is present.

2-8 Vanguard Routing Model

WAN Adapter

RFC1294 Multiprotocol Encapsulation

Overview RFC1294 encapsulation is used for the IP and RIP protocols. RFC1490 extends

RFC1294 to handle SNA protocols. For IP and IPX, however, RFC1294 and
RFC1490 are identical. Al l protocols are encapsulated using the NLPID format for I P.

How the WAN
Adaptor Handles
RFC 1294

The WAN adapter handles RFC1294 encapsulation as follows:

1) The WAN Adapter creates an RFC1294 header and places it in the packet in

front of the data before the packet is passed to the WAN protocol stack.

2) The RFC1294 header is passed as data by the WAN protocol stack and is

processed and stripped from the packet by the receiving WAN Adapter.

3) The packet is passed to the Routing forwarder.

Note

The Vanguard does not support the RFC1294 encapsulation of bridge data.
If a WAN Adapter LAN Connection record has the parameter LAN Forwarder
Type of BRID or BROUT, then the Encapsulation Type must be CODEX
(not RFC1294); otherwise, bridge data will be lost. If bridge traffic will be sent
over an FRI port, then the encapsulated bridge traffic can be sent over an Annex
G station on the port.

Packet Format Figure 2-3 shows the two main WAN packet formats in use for Frame Relay

connections.

Figure 2-3. Packet Formats

Q9.22

NPLID

CRC

Flag

ADDR

LGN
LCN

CTL

Type=0

Flags

Flag

Q9.22

CRC

Q9.22

OxCC

Flag

Q9.22

CRC
CRC

Flag

CTL

LAPB Header

X25 Packet Header

Codex Trailer

Codex Encapsulation

Annex G Station

RFC1294 Encapsulation

Bypass Station

Note: The RFC1204 encapsulation to a

Bypass FR station is used for
interoperability with non-Motorola
routers.

Note: Motorola to Motorola links are recommende d to use

Codex encapsulation over Annex G-type Frame
Relay stations.

Protocol
Packet

Protocol
Packet

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.

2-10 Vanguard Routing Model

WAN Adapter

RFC1356 Multiprotocol Encapsulation

Overview RFC1356 and RFC877 encapsulation standards are virtually t he same. The Vanguard

Router complies with RFC1356 encapsulation over X.25 with the following
exceptions:

• While RFC1356 specifies multi-protocol support, only the IP protocol is
supported.

• The NLPID encapsulation of RFC1356 is supported; SNAP encapsulation
is not.

Vanguard Routing Model 2-11
T0100-01, Revision B Release 5.4

WAN Adapter

LAN Connection Encapsulation Examples

Examples The following examples illustrate LAN traffic encapsulation by

• Codex Proprietary Encapsulation

• Frame Relay - RFC 1294 and RFC 1490

LCON over X.25
using Codex
Proprietary
Encapsulation

Figure 2-4 depicts LAN traf fic enca psulated by Code x Proprieta ry Encapsulati on for
transport over an X.25 network. At the regional site a Va nguard connects with up to
254 branch sites ov er X.25. The encaps ulat ion t ype sho uld be Code x Propr ieta ry due
to the RFC limitation of s upporting only a single call. The LCONs can be connected
in any combination of Router Interfaces (On Demand or Permanent SVCs) and
Bridge Links (Permanent SVCs only) as long as the total capacity is not exceeded.

Figure 2-4. Maximum LAN Connections Over X.25 With Codex
Proprietary Encapsulation and Permanent SVCs

Vanguard

Terminal Server

X.25 SVCs

Cisco

254 Branches

Vanguard

IP Host

Token Ring

Vanguard

Token Ring

Codex

Prop

Encaps

Token Ring

Branch 1

Branch 254

Vanguard

Legacy

Protocol

Server

Codex

Prop Encaps

X.25

Image Server

:

2-12 Vanguard Routing Model

WAN Adapter

LCON over Frame
Relay using RFC
1490 Encapsulation

This example depicts use of the maximum number of LAN Connections. At the
regional site is a Vanguard that needs to connect with up to 254 branch sites over
Frame Relay. Frame Relay supports a 254 DLCI maximum per node and permanent
SVCs only. These LCONs can be connected in any combination of router interfaces
and bridge links as long as the total capacity is not exceeded. Supported
encapsulation types over Frame Relay are Codex Proprietary and RFC1294/1490.
Figure 2-5 shows this example.

Figure 2-5. Maximum LAN Connections Over Frame Relay With Codex
Proprietary or RFC1294 and Permanent SVCs

Vanguard

Terminal Server

Cisco

254 Branches

Vanguard

IP Host

Token Ring

Vangua rd

Token Ring

Branch 1

Branch 2xx

Vangu ard

Legacy

Protocol

Server

Codex Prop
Encaps or
RFC1294

Image Server

Branch 2

Branch 3

DLCI 1

DLCI 4

DLCI 2

DLCI 5

DLCI 3

Codex Prop
Encaps or
RFC1294

254 Branches

Central Site

Vanguard Routing Model 2-13
T0100-01, Revision B Release 5.4

WAN Port

W AN Port

Types of WAN
Virtual Circuits

The Vanguard supports the foll owing types of WAN virtual circuits:

• Frame Relay DLCI (Bypass)

• Annex G (X.25 over Frame Relay) (SVC)

• X.25 (SVC)

• MX25 (SVC)

• XDLC (SVC)

•ISDN

• PPP

Configuring the
WAN Port

To configure the WAN port, refer to the Vanguard Basic Configuration Manual
(Part Number, T0113).

2-14 Vanguard Routing Model

WANView and LANView

W ANView and LANV iew

Introduction The Vanguard provides two types of interconnection of LANs over a WAN,

LANView and WANView. This section provides a brief description of each and
example functional diagrams.

WANView and
LANView Overview

The following table describes WANView and LANView.

Differences Figure 2-7 and Figure 2-6 show the difference in the internal data connections

between a LANview (Group LCONs) and traditional WANview (point-to-point
LCONs). With LANView, three different LCONs are mapped to the same Router
Interface. With a WANview, each LCON (that is, each virtual circuit) is tied to a
different Router Interface. For WANView, each Router Interface must be assigned a
different IP Network (or Subnetwork) address.

Name Type Description

WANView Point-to-

Point
LCONs

The most common mechanism of routing between
two Vanguard routers over a WAN link with a virtual
circuit configured as a poin t-to-point LAN connect ion
(LCON). The LCON is associated with a unique
router interface on each end. The LCON is considere d
to be a network with only t wo hosts and is assign ed its
own, unique subnetwork number.

LANView Group

LCONs

Grouped LCONs are multiple virtual circuits
associated with the same router interface.
Conceptually, all of the WAN-attached nodes are
considered to be on a vi rtual LAN. All WAN
interfaces are assig ned di fferent host addresses on the
same netw ork number.

Vanguard Routing Model 2-15
T0100-01, Revision B Release 5.4

WANView and LANView

Figure 2-6. W ANview

Figure 2-7. LANView

Node A

10.1.0.2

10.2.0.2

Network

FRI-1

S-2

FRI-1

S-3

FRI-1

S-1

LCON 1

LCON 2

LCON 3

10.1.0.1

Node B

Node C

10.3.0.2

Router

Node D

WAN Adapter Router

Ethernet

Note: FRI = Frame Relay Interface

S = Station

10.2.0.1

10.3.0.1

A

B
C

1

5
6
7

WAN

Note

Different Router Interfaces (5, 6, and 7) are used.

Router Interfaces

FRI Port 1

Network

FRI-1

S-2

FRI-1

S-3

FRI-1

S-1

LCON 1

LCON 2

LCON 3

10.0.0.1

Router

Node D

WAN Adapter Router

Ethernet

Note: FRI = Frame Relay Interface

S = Station

Note

One Router Interface (5) is used.

Node A

10.0.0.2

10.0.0.3

Node B

Node C

10.0.0.4

WAN

5

1

Router Interface

FRI Port 1

2-16 Vanguard Routing Model

WANView - Point to Point LCON

W ANV iew - Point to Point LCON

What is WANView? The V anguard WANView mechanism allows routing be tween two Vanguards over an

WAN link using a point-to-point virtual circuit, the LCON. Each WAN link or
connection has a unique LCON. The LCON is considered to be an IP network with
only two hosts and is assigned its own, unique IP subnetwork number.

Benefits of
WANView

The benefits of WANView include:

• less administrations - you are not required to configure the Next Hop address

• better manageability - each WAN link has a unique IP subnetwork number

WANView
Interoperability
Issues

When interoperating with non-Motorola routers it may not be possible to use
WANView. For interoperability with non-Motorola routers use LANView.

Example:
WANView over
Frame Relay

Figure 2-8 illustrates an example of WANView over Frame Relay.

Figure 2-8. W ANView over Frame Relay

In this example, there are two point-to-point connections. One point-to-point
connection is from Node 100 Router Interface #5 to Node 200 Router Interface #5.
The other point-to-point connection is from Node 100 Router Interface #6 to Node
300 Router Interface #5. The two en ds on each WANV ie w point-to-point co nnection,
are on the same IP Subnet.

Vanguard

Vanguard

Vanguard

Token Ring

Router Interface #5

172.16.1.1

Router Interface #6

172.17.2.1

Router Interface #5

172.16.1.2

Router Interface #5

172.17.2.2

Subnet 172.16.1.0

Subnet 172.17.2.0

WAN Link

WAN Link

Node 100

Node 200

Node 300

Vanguard Routing Model 2-17
T0100-01, Revision B Release 5.4

LANView of the WAN - Group LCONs

LANView of the W AN - Group LCONs

What is a LANView
of the WAN?

The LANView feature provides flexible configuration of all virtual circuits over the
WAN port for either single or multiple IP interface addresses.

The connection point of any IP forwarder to a network is called a Router Interface.
A Router Interface has an IP Host address associated with it . This interface address
must have its network portion equal to the network number to which it connects.

The LANView feature can map several SVCs/PVCs to a single Router Interface.
This is useful for adding new Vanguard nodes at branch sites, or when adding Dial
on Demand or Bandwidth on Demand connections to a node. Configuring a Wide
Area Network as a single IP network avoids costly workstation and PC
reconfigurations.

A LANView of the WAN allows a group of SVC connections, known as a LAN
Connection Gr oup, to be mapped to a singl e IP Router Inte rfac e, and thu s a sing le IP
network level address. This lets the WAN be treated as a logical LAN, where all
nodes on the logical LAN use the same IP network level address.

The LANView of WAN also applies to Router IPX addresses. All WAN SVCs in a
LAN Connection Group are considered to be on the same IPX Network Number.

In the discussions that follow, a Network Address is the combination of the Network
and Subnetwork Address.

Examples Figure 2-9 shows the LANView concept. The IP topology shows all Vanguards

connected to IP Network Address 192.168.0.0. However, each of the Vanguards has
been assigned a unique H ost address.

Figure 2-9. LANView Topology

In this exampl e, Vanguard-A has three SVCs, one to each remote destination. Each
SVC is configured with a different Next Hop Address of 192.168.0.2 for
Vanguard-B, 192.168.0.3 for Vanguard-C, and 192.168.0.4 for Vanguard-D. All
three SVCs, or LCONs are associated with a single Router Interface in Vanguard-A.
The interface in Vanguard-A is assigned the IP address 192.168.0.1. The concept is
similar to a LAN, where each Vanguard is assigned an IP address, as shown in
Figure 2-10.

Vanguard-A

Vanguard-B

192.0.0.0

192.168.0.2

Vanguard-C

Vanguard-D

192.168.0.3

192.168.0.4

192.168.0.1

2-18 Vanguard Routing Model

LANView of the WAN - Group LCONs

Figure 2-10. LAN Topology

Features and Uses LANView features include:

• Up to 2000 LCONs per router depending on product, any set of which can be
associated as a group to a single Router Interface

• Up to 254 Router Interfaces per router

• Multiple physical ports can share a single Router Interf ace Network Address.
This includes combining X.25, Frame Relay, and dial ports. You can mix X.25

SVC LAN Connections and Frame Rela y PVC LAN Connection s in th e same
LAN Connection Group.

• Multiple incoming calls accepted using RFC877 encapsulation

• Varying encapsulation types for SVCs within the same LANView

• Bridged data sent over SVCs/PVCs that are part of a LANView

• Disabling of IP RIP or IPX RIP Split Horizon for LANView full mesh
networks

Support The LANView feature supports the following:

• Frame Relay and X.25 networks

• IP and IPX protocol s

• Existing point-to- point view confi guration (one IP Network Addr ess per LAN
Connection)

A router configured as LANView at the central site is able to operate with multiple
Point-to-Point Views on the other end of the WAN link.

Advantages You can benefit most from LANView if you are already using a LANView in your

backbone networks. As show n in Figur e 2-11, it is effor tless to add se veral rou ters a t
branch sites with the same IP Network address if you are already running with your
regional site WAN link configured as IP Network address 10.0.0.0. You need not
change any of the configuration at the regional site.

LANView is also appropriate if you have a shortage of IP Network address space. If
you use Class C addresses (24-bit Network address and 8-bit Local address), you
must balance the number of hosts on a subnetwork against the number of
subnetworks you can have. In this situation, having fewer subnetwork addresses
allows for more hosts at each subnetwork, since the WAN uses only one Subnet.

The LANView feature also simplifies adding Dial on Demand and Bandwidth on
Demand connections to a node.

Vanguard-A

Vanguard-B

192.168.0.2

Vanguard-C

Vanguard-D

192.168.0.3

192.168.0.4

192.168.0.1

Vanguard Routing Model 2-19
T0100-01, Revision B Release 5.4

LANView of the WAN - Group LCONs

Example Figure 2-1 1 sh ows an ex ample of add ing ro uter b ranch s ites to an exist ing WAN link.

Figure 2-11. Adding Branch Sites to an Existing WAN Link

Grouping LAN
Connections

A LAN Connection Group, or LCON Group, is a set of LCONs (SVCs/PVCs) that
are associated with a single Router Interface. Each LCON in a group is configured
with the IP and/or IPX node address of the Router on the remote end of the LCON.

Encapsulation

LCONs are configured with an Encapsulation Type, which determines how the
various protocols (IP, IPX, etc.) are encoded in a packet. Each SVC within the LAN
Connection Group can be selected to have a different WAN encapsulation. For
example, in an X.25 network, one SVC can have encapsulation Type RFC877 while
another is CODEX.

Mixed SVCs/PVCs

Each LAN Connection Group can support mixed types of SVCs, as allowed by the
network type. You can mix permanent SVCs, On Demand SVCs, and Dial On
Demand SVCs. You can also have PVCs in the same LAN Connection Group as
SVCs.

Parallel SVCs

A Parallel SVC is an LCON configure d as attach ed to the same Rou ter Inter face as a
primary SVC in the local router and the same next hop address as the primary SVC
in the remote rou ter.

MTU Size

All SVCs in a LAN Connection Group have the same Router MTU size, since
Router MTU size is configured on a per Router Interface basis.

Broadcast Information

IP and IPX RIP can be enabled or dis abled on any Rou ter Inter face associ ated wit h a
LAN Connection Group.

Net 1 1

Router

FR/X.25

10.0.0.1

Router

10.0.0.2

Vanguard

10.0.0.3

V anguard

10.0.0.4

Regional Site

Net 12

2-20 Vanguard Routing Model

LANView of the WAN - Group LCONs

Configuration
Considerations

You configure the LANView using the LAN Connection Table described on

“Configuring LAN Connection Table” section on page 3-11. Configuration
parameters are also described in the Vanguard Configuration Basics Manual.

LANView configuration is similar to LAN Connection configuration. Entering the
same Router Interface address for several LAN Connections ties all desired LAN
Connections to the same Router Interface.

Booting Connections Within the Group

Booting any LAN Connection that is part of a group does not affect any other LAN
Connections belonging to that group. Also, any LAN Forwarder changes, Bridge
Link Number Changes, or Router Interface Number changes (unless the Router
Interface is alr eady assoc iated with a group) require a Node boot to t ake ef fect. Ot her
changes can take effect with a LAN Connection boot.

You can p erform the following operations without a node boot; only a LAN
Connection boot is required:

• Configure a new LAN Connection and boot it into an existing LAN
Connection Group

• Move a LAN Connection from one LAN Connection Group to another.

RIP Split Horizon

On broadcast-type networks, RIP split horizon reduces the possibility of routing
loops by blocking information about routes from being advertised out the interface
from which it originated.

Since LANView makes multiple remote nodes reachable through a single Router
Interface, you must disable RIP Split Horizon on that Router Inte rface for all nodes
to receive all necessary routing information.

When you disable split horizon, internal hold down timers ensure that nodes stop
“listening ” after a network failur e. This eliminates the possibility of accepting any
route misinformation and allows time for the failure information to work its way into
all the routing databases.

Limitations The following limitations apply to the LANView feature:

• Bridging traffic is not allowed over On Demand SVCs that are part of a
LANView. However, Bridging traffic is allowed over perm anent SVCs that
are part of LANView.

• X.25 PVCs are not supporte d as part of a LAN Connection Group.

Vanguard Routing Model 2-21
T0100-01, Revision B Release 5.4

LANView of the WAN - Group LCONs

LANView Examples

LANView over X.25 Figure 2-12 is a common application for LANView over X.25. At the HQ site is a

router (Node D) that needs to connect to three other branch nodes (Nodes A to C).
The solid line den otes a perma nent SVC. The dot ted l ines de note On Demand SVCs .

In Figure 2-12, Node D has a LANView of the WAN. The WAN is really a logical
LAN with an IP network level address of 10.0.0.0. Node D has one IP Router
Interface with addr ess 10.0.0.4, which can reach any of the branches (No des A to C)
via three SVCs tied to the same Router Interface (for example, Interface #5). This
example shows that a LANView can be a mix of Permanent and On Demand SVCs.

Without LANView functionality, this same network would require Node D to have
three IP Router Interfaces, each with a different IP network level address. With
LANView, the same three connections use only one IP network level address.

Figure 2-12. LANVie w fo r IP Over X.25

Vanguard

Terminal Serve r

Cisco

Vanguard

Token Ring

Vanguard

Token Ring

10.0.0.1

Vangua rd

Legacy

Protocol

Server

Image Server

Node A

Node B

Node C

10.0.0.2

10.0.0.3

10.0.0.4

Node D

IP WS

2-22 Vanguard Routing Model

LANView of the WAN - Group LCONs

LANView for IPX
over Frame Relay

Figure 2-13 is a similar application to the one shown in Figure 2-12 for IPX.
Node 10000000 has a LANV iew of the WAN. The WAN is really a logical LAN with

an IPX network address of 12, where each router is a different node number on the
network. Node 10000000 has one IPX Router Interface, which can reach any of the
other three nodes via three SVCs tied to this Router Interface. Without LANView,
this same network would require Node 10000000 to have three IPX Router
Interfaces, each with a different IPX network address. With LANView, the same
remote node connection uses only one IPX network address.

Figure 2-13. LANVie w for IPX

Vanguard

Cisco

Vanguard

Token Ring

V anguard

Token Ring

Vangua rd

IP WS

IPX Net 8

IPX Net 12
Node 1000000 3

IPX Net 9

IPX Net 12
Node 1000000 2

IPX Net 12
Node 10000001

Frame Relay

IPX Net 12

Codex Prop

IPX
Net 12

Node 10000000

IPX Net 10

Vanguard Routing Model 2-23
T0100-01, Revision B Release 5.4

LANView of the WAN - Group LCONs

LANView over
Frame Relay

Figure 2-14 shows LANView in a Frame Relay Network. This is an example of full
mesh connectivity between the branches.

At both the headquarters and the branches, a single Router interface, with IP
Network address 10.0.0.0 is used.

Figure 2-14. LANView over Frame Relay

Vanguard

Cisco

Vanguard

Token Ring

V a nguard

Token Ring

10.0.0.4

Vanguard

Node A

Node B

Node C

10.0.0.2

10.0.0.3

10.0.0.1

Node D

IP Host

Codex Prop Encaps or

RFC1294

DLCI 1

DLCI 4

DLCI 2

DLCI 5

DLCI 3

Network 10.0.0.3

Codex Prop Encaps or
RFC1294

DLCI 6

2-24 Vanguard Routing Model

LANView of the WAN - Group LCONs

Vanguard Router
using LANView
Interoperating with
Cisco Backbone

Figure 2-15 is an example of LANView interoperating with a Cisco backbone. The
key difference in this application is that even though RFC877 is used as the
interoperability encapsulation between the routers and other RFC877-compliant
routers, connectivity between the routers uses the CODEX encapsulation. This
demonstrates support for multiple encapsulations within the same LANView.

Figure 2-15. LANView Using Multiple Encapsulation Types

Vanguard

Vanguard

Token Ring

Vanguard

Token Ring

10.0.0.1

Node A

Node B

Node C

10.0.0.2

10.0.0.3

10.0.0.4

Cisco

RFC877

RFC877

RFC877

X.25

12.0.0.0

SDLC

Async

56 Kbps

Cisco

Cisco

Cisco

IP IP

IPIP

IP

Host

Token Ring

Codex Prop.

877 X.25

10.0.0.0

Codex Prop.

Vanguard Routing Model 2-25
T0100-01, Revision B Release 5.4

RTP/UDP/IP Header Compression

RTP/UDP/IP Header Compression

Introduction The Vanguard router can provid e RTP/UDP/IP header compre ssion on a link -by-l ink

basis. This section examines the options for RTP/UDP/IP header compression.

What is a RTP/UDP/
IP Header?

User Datagram Protocol (UDP) is a transport layer protocol that provides best effort
packet delivery on top of IP. As it is best effort service, UDP does not guarantee
reliable delivery. The Real Time Protocol (RTP) resides on top of UDP/IP and

provides fast delivery of real time traffic such as voice. Motorola’s implementation
of VoIP uses UDP/IP or RTP/UDP/IP protocols to carry packetized voice.

Why Is RTP/UDP/IP
Header
Compression
Needed?

Packetized voice is encapsulated into IP packets before being transported over an IP
network. In encapsulating the packetized voice, RTP, UDP and IP header
information is added to the packet to provide information on how the IP packet is to
be the routed through the IP network. This RTP/UDP/IP header information is
typically 40 bytes in size. This is a relatively large overhead considering that an
average voice packet is approximately 64 bytes. Comparing the encapsulated data
payload and voice payl oad shown in Figure 2-16, the 40 byte RTP/UDP/IP header is
a significant overhead when it is applied to the voice packet. The motivation for
compressing the RTP/UDP/IP header is to reduce overhead and bandwidth usage.

Figure 2-16. Encapsulated Data Packet and Voice Packet

Data Packet

IP UDP RTP

40 Bytes 2048 Bytes

Voice PacketIP UDP RTP

40 Bytes

64 Bytes

2-26 Vanguard Routing Model

RTP/UDP/IP Header Compression

Motorola’s
Implementation of
RTP/UDP/IP Header
Compression

Vanguard routers supports RTP/UDP/IP and/or UDP/IP header compression. As
shown in Figure 2-17, the V anguard compr esses the 40 byte head er to between 2 to 4
bytes. If UDP checksum is being sent, the RTP/UDP/IP header is compressed from
40 bytes to 4 bytes. If no UDP checksum is being sent, header compression is 40
bytes to 2 bytes.

Figure 2-17. RTP/UDP/IP Header Compression

Motorola’s Vanguard products support:

• header compression by traffic type - RTP/UDP/IP, UDP/IP, or both

• header compression on a link-by-link basis

• header compression of RTP/UDP/IP or UDP/IP packets carried over PPP or
Frame Relay WAN links

Options for Header
Compression

The Vanguard products can support header compression in four different
configurations. Header compression can be enabled to:

• Compress outgoing packets only; incoming compressed packets are not
recognized for decompression.

• Decompress the incoming compressed packets only; outgoing packets sent on
an interface are not compressed.

• Compress all the outgoing packets and decompress all the incoming
compressed packets on an interface.

In addition, header compression can be configured to autodetect the compression
state of incoming and outgoing packets. If an incoming packet received on a link is
compressed then the outgoing packets are also be compressed.

Packet Voice/DataIP UDP RTP

Packet Voice/Data

IP UDP R TP

40 Bytes

2 to 4 Bytes

Vanguard Routing Model 2-27
T0100-01, Revision B Release 5.4

RTP/UDP/IP Header Compression

Compression and
Decompression

If an RTP/UDP/IP packet is compressed befor e transmission of the WAN link, it must
be decompressed at the receiving end. Each Vanguard supporting header compression,
has a compressor and decompressor function.

Figure 2-18. Vanguard Compression/Decompression Function

Compressor

Decompressor

Compressor

Decompressor

Vanguard
Compression Function

Vanguard
Compression Function

2-28 Vanguard Routing Model

RTP/UDP/IP Header Compression

How RTP/UDP/IP Compression and Decompression Occurs

Introduction This section describes how the Vanguard RTP/UDP/IP compression and

decompression occurs.

Determining if the
Packet can be
Compressed

When the Vanguard receive a packet, the first step is to determine if the packet can
be compressed. The Vanguard performs this process:

Step Process

1 The Vanguard examines the packet’s RTP/UDP/IP header information and

looks at the following:

• Source IP address

• Destination IP address

• Source UDP port

• Destination UDP port

• SSRC field

These items define a flow. If the packet with a new flow is received, this
flow information will be saved in the compressor list.

2 The Vanguard compares the packet’s source and destination UDP ports

against a list of configured UDP port ranges on which header compression
can be applied. If eith er source o r destina tion port s match the conf igurati on,
the packet is considered for compression.

If the packet’s source and

destination UDP port:

• Match the configured list, the packet is checked against the negative
cache.

• Does not match the configure list, the packet is forwarded without
compression.

3 The negative cache contains a list of dynamically identified flows that

should not be compressed.
The packet’s flow (source IP address, destination IP address, source UDP

port, destination UDP port, and SSRC field) is compared against the
negative cache. If the packet’s flow:

• Matches an entry in the negative cache, the pa cket is forwarded wi thout
compression.

• Does not match an entry in the negative cache, the packet can be
compressed.

Vanguard Routing Model 2-29
T0100-01, Revision B Release 5.4

RTP/UDP/IP Header Compression

Compressing the
RTP/UDP/IP Header

If the Vanguard determines that the packet can be compressed, it compresses the

packet’s RTP/UDP/IP header as shown in Figure 2-19 and the table:

Figure 2-19. Compression Process

Context Identifier A unique Context Identifier (CID) is assigned to each flow. The CID contains the

following information:

8-bit or 16-bit CID Number

This is used to uniquely identify a flow or session. If the number of sessions is less
than 255, an 8-bit CID numb er is u sed ; i f t he n u mber of s ess io ns i s gr ea ter t han 2 55,
a 16-bit CID number is used.

Router A

RTP/ UDP/IP

header

Voice/Data

Packet

Router B

Voice/Data

Packet

1

1st Packet

RTP/UDP/IP

header

Voice/Data

Packet

Compressed RTP/UDP/

IP Header + CID

Voice/Data

Packet

2

2nd Packet

RTP/U DP/IP

header

Voice/Data

Packet

Compressed RTP/UDP/

IP Header + CID

Voice/Data

Packet

3rd Packet

Compressed RTP/UDP/

IP Header + CID

Step Process

1 The RTP/UDP/IP header of the first packet is not compressed. The first

packet will have the full R TP/UDP/I P header and a Contex t Identifier ( CID)
attached to it. The CID is used to uniquely identify the session between the
compressor and decompressor modules. The Vanguard attaches the CID
before sending the packet.

2 For all subsequent packets, the Vanguard compressor module compresses

the 40 byte RTP/UDP/IP header into a 2 or 4 byte compressed header. The
Vanguard compressor module also attaches the CID to the packet.

2-30 Vanguard Routing Model

RTP/UDP/IP Header Compression

4-bit Sequence Number

Each packet is numbered sequentially from 0 to 15. The decompressor on the
receiving Vanguard uses the sequence number to determine if packets are received
out of sequence or if there is packet loss. The decompressor recomputes the UDP
checksum of every 16th decompressed packet. This recomputed UDP checksum is
compared against the transmitted UDP checksum. If the UDP checksums match, the
decompressor forwards the decompressed packets. If the UDP checksums do not
match, the decompressor se nds a CONTEXT_STATE packet to the compressor.

The CONTEXT_STATE packet contains:

• the CID of the context which needs to be synchronized.

• the sequence number of the last correctly received compressed packet.

When the compressor rece iv es a CONTEXT STATE packet, it sends t he ne xt pa cke t
with a full RTP/UDP/IP header. The CONTEXT_STATE packet provides both
synchronization and error recovery.

Configuring RTP/
UDP/IP Header
Compression

To configure the RTP/UDP/IP header compression parameters, access the following
CTP menu:

Configure -> Configure LAN Connection -> LAN Connection Table

For detailed parameter descriptions refer to “LAN Connection Table Record
Parameters” section on page 3-16.

Note

The RTP/UDP/IP header compression parameters only appears for RFC 1294
encapsulation type.

Vanguard Routing Model 2-31
T0100-01, Revision B Release 5.4

Using Bridging Routers to Connect LANs and Networks

Using Bridging Routers to Connect LANs and Networks

Introduction A bridging router is a device in which both bridge and router software run

concurrently. The Vanguard internetworking systems provide bridging router
functions.

Note

For additional information on Bridging, refer to the Bridging Manual
(Part Number T0100-02).

Operation of
Bridging Router

A bridging router handles packets as follows:

• Routes packets if a specific routing protocol is globally enabled.

• Filters packets if you configure specific protocol filters.

• Bridges packets if they are not routed or filtered. In this case, they are
forwarded according to their destination MAC address.

Bridging and
Routing in the
Vanguard Node

Note that Vanguard support both bridging and routing within the same node for the
same protocol. When using this feature, it is important to configure filters that
disable either routing or bridging between the two end points to prevent packet
duplication.

Bridges work at the Data Link layer providing connectionless service. Routers
operate at the Network la yer and, theref ore, offer some flexibil ity in choosing several
network level services.

How Vanguard
Bridging Routers
Work

Vanguard bridging routers examine every packet on a network. The source host
builds a packet from the Application layer downward to the Physical layer and
passes the packet over the network. There can be severa l different values for the Data
Link (MAC) destination addres s used with the packet. The Data Link address m ay
be:

• Addressed to the Motorola internetworking node itself (case 1)

• Addressed to some other node (case 2)

• Addressed as a broadcast packet (case 3)

Case 1 In case 1, the frame is addressed to the Vanguard internetworking node, as des cri be d

here:

• A host sends a frame to the MAC address of the Vanguard node, itse lf.

• The packet is given to the routing forwarder within the node. The bridging
forwarder is not used in this case.

• The routing forwarder accesses the Network layer that contains the
destination address of the packet.

• The forwarder compares the Network layer destination address to the
addresses in the routing table to obtain the best match.

- If the best match is made, the router re builds the Data Lin k layer and passes

the packet to the next hop.

- If no match is made, the router discards the packet. For IP, an unreachable

packet is transmitted back to the sender.

2-32 Vanguard Routing Model

Using Bridging Routers to Connect LANs and Networks

Case 2 In case 2, where the Data Link address is different from the Vanguard node’s own

data link address, the packet can be forwarded by bridging (assuming the packet is
not destined for a host on the local network). The NAP node examines every packet
on the LAN for possible bridging as described here:

• The packet is passed to the br idge forwarder in the Vanguard internetworking
node. The routing forwarder is not used for this type of packet.

• If using Transparent Bridging (TB), the bridge accesses the MAC address
associated with the packet.

- The TB scans its forwarding table looking for a match with the MAC

address of the packet it is processing. The matching entry in the table
includes information as to where to forward the frame.

- The frame is forwarded along its spanning tree links so that a copy

eventually reaches the desired destination if a match is not found.

• If using Source Route Bridging, the bridge accesses the Routing Information
Field (RIF) in the packet frame.

- The frame is forwarded according to the RIF.

- The RIF indicates the specific next link to use to forward the packet frame.

It may also indicate either a spanning tree broadcast or an all route
broadcast of the packet within the bridge network.

Case 3 In case 3, a Broadcast Data Link address is used as described here:

• The Vanguard node gives a copy of the packet frame to the bridge forwarder.

• If Transparent Bridging is used, the frame is forwarded along the spanning
tree links so that a copy eventually reaches all networks.

• If Source Route Br idging is us ed, th e f rame i s for warded a ccordi ng to the RI F
in the same way as for a specific MAC address as previously described.

• An additional copy of the packet is given to the routing forwarder for
processing.

Limitation for
Bridging and
Routing in the
Same Node

Although bridging and routing for the same protocol is supported within the same
Vanguard node, there is a basic limitation that these functions cannot occur for end
stations both usi ng the s ame LANs. If this is attempted, as was d esc ri bed previously,
packets can be duplicated and sent by both the bridge and the router between the
same end stations, which causes communication failures. To avoid such
circumstances, use the filters that can be configured for both bridges and routers to
block the type of traffic that you do not want forwarded.

The Bridged Protocols parameter in the Configure Bridge Parameter menu controls
whether IP, IPX, or both protocols are forwarded over bridge links. In most cases, it
is better to route IP and IPX rather than bridge them. Disabling the forwarding of IP
or IPX with the Bridged Protocols parameter is like filtering the protocol on all
bridge links.

Vanguard Routing Model 2-33
T0100-01, Revision B Release 5.4

Using Bridging Routers to Connect LANs and Networks

Using Bridge and
Router Filters

Figure 2-20 shows an example of a network where filtering is used.

Figure 2-20. Using Bridge and Router Filters to Control Network Traffic

Figure 2-20
Explanation

Figure 2-20 is explained here:

• Several smaller LANs (LAN 2, 3, and 4) have stations that communicate with
stations on LAN 1 and with other stations in the network (not shown).

• Bridging is used in the lower part of the network because only direct
communicati ons to a main LA N are available and there is no need for the
overhead of running a RIP protocol (except in node N3).

• Connections are provided by nodes N1 through N4 and other nodes that
function as bridges and routers or bridging routers.

• Stations S2 and S4 communicate with station S1 by bridgin g, since nodes 2 and
4 provide only bridging.

• For stations 2 and 4 to communicate with other remote stations, the traffic is
bridged to node 1, and from there it is routed to the destination.

• Station S 3 can be set up to eith er bridge or route to s tations o n LAN 1, but no t to
both simultaneously (for example, bridge to station S1 and route to station S5).

• For node 3, you can either bridge between LAN 3 and LAN 1, or route. The
decision can be policy based or derived from traffic considerations.

• Routing is used, sta tions on LAN 3 can route to all ot her sta tions in the net work
and should select brid ge pr otocol fi lter s to bl ock IP tr af fic on bridg e link s going
from LAN 3 to LAN 1. This allows full routing for IP traffic and bridging for
other protocols.

S5

RouterRouter

Router

Bridge,
Router

S1

Bridge,

Router

Bridge,

Router

Bridge,

Router

S2 S3 S4

LAN 2

LAN 3

LAN 1

LAN 4

N1

N2

N3

N4

2-34 Vanguard Routing Model

Using Bridging Routers to Connect LANs and Networks

Source Routing
Bridging
Environment

In a Source Routing Bridging envi r onment , the bri dge acce sse s the address and path
to reach the destination address from response to the router discovery frame.

If the sender forwards the packet to a host, depending on the type of Transport layer
service the host uses, the host transmits an acknowledgment to the sender.

How Addressing
Schemes Affect
MAC Bridging and
IP Routing

The following table describes the differences between I P rou ti ng an d MAC bri dgi ng
according to the addressing scheme used:

MAC Bridging

Addressing

IP Routing

Addressing

IP Subnet

Addressing

Data delivery Delivers data based on

MAC addresses.

Delivers data based on IP
addresses.

Delivers data based on
subnet IP addresses:
network address,
subnetwork address, host
address.

Address style Flat addressing: each

address identifies a
machine.

Hierarchical addressing:
each address identifies a
network and a machine
on the network.

Multiple directly
connected physical
networks can share a
single network address.

Address attachment MAC addresses can be

permanently assigned to
hardware units.

IP addresses cannot be
permanently assigned to
the hardware.

IP subnet addresses
cannot be permanently
assigned to the hardware.

Data delive ry after
machine relocation

MAC bridging allows
delivery to the same
MAC address when
hardware is relocated.

IP address must be
updated after the
machine is relocated.

IP address must be
updated after the
machine is relocate d.

Address table size MAC bridging over large

networks involves very
large address tables.

IP routing over large
networks requires
smaller address tables.

Same as IP routing
addressing.

Forwarding decisions Based on exact matches

of full 48-bit MAC
address.

Based on exact or partial
matches of the network
portion of the 32-bit IP
address.

Based on which port to
use to deliver the packet
to the subnet address.

Configuring a Vanguard Router 3-1

Chapter 3

Configuring a V anguard Router

Introduction This section highlights the basic configuration parameters that are required to

configure the Vanguard device to carry LAN traffic over a WAN as shown in
Figure 3-1.

Figure 3-1. Network T opology

WAN

LAN

LAN Port

Ethernet

Token Ring

WAN Port

Frame Relay

X.25
MX25
ISDN

PPP

XDLC

Vanguard Router

LAN
Port

1

5

FRI

Port

LCON

FRI

Station

LAN

IP Forwarder

- Bridge

- Router

W AN Adaptor

WAN Po rt

Router

Interface

Vanguard Router

Vanguard Router

WAN

3-2 Configuring a Vanguard Router

Configuration

Configuration

Introduction The example configurations provided in this section highlights the important

parameters that should be configured. For a step by step procedure on how to
configure the Vanguard Router, refer to the Vanguard Basic Configuration Manual
(Part Number T0113).

Parameter
Descriptions

“Configure LAN Connections” section on page 3-9 provides detailed parameter
descriptions. For other parameters descriptions and more detail ed configuration
examples you may have to refer to the feature or protocol manual.

Parameters
Applicable For All
Applications

This section list the table records and parameters that you should configure for
Vanguard Router operation rega rdless of net work layer opera tion. Later sections wil l
highlight additional parameters you will need to configure for specific operation or
applications.

Step Configure Menu

1 Configure the Node Record.

Configure -> Node

2 Configure the WAN Port. The WAN

Port may be on e of the following:

• Frame Relay

• X.25

• MX.25

•ISDN

• PPP

• XDLC

Note

Depending on the WAN Port you
select, you may need to configure
other WAN records or parameters.
Refer to the specific fe ature or
protocol manual for more info rmatio n
on configuring parameters for the
WAN port.

Configure -> Port

3 Configure the LAN Port:

•Ethernet

• Token Ring

Configure -> Port

4 Enable the Router Interface State(s)

Configure -> Configure Router ->
Configure Router Interface State

5 Configure the LAN Connection Table

(LCON).

Configure -> Configure LAN
Connections

6 Configure the Mnemonic Table

Configure -> Configure Network
Services -> Mnemonic Table

7 Configure the Route Selection Table

Configure -> Configure Network
Services -> Route Selection Table

Configuring a Vanguard Router 3-3
T0100-01, Revision B Release 5.4

Configuration

Bridging Configure these additional parameters or table records for bridging operation:

• Bridge Parameter

• Bridge Link Parameter

Other Bridge parameters are optional.

Note

Remember to set the “LAN Forwarder Type” parameter to BRID or BROUT.
This parameter is configurable under

Configure -> LAN Connection Table.

Apple Talk Configure these additi onal pa ramete rs or table re cords t o suppor t Apple Talk routing

over the Ethernet LAN:

• Apple Talk Parameter

• Zone Seed Table

• Apple Talk Interface

Note

Apple Talk can only be configured for point-to-point LCON (WANView). Set
the “LAN Connection Type” parameter to “Pt-to-Pt.” this parameter is
configurable under

Configure -> Configure LAN Connection Table.

OSPF Configure these additional parameters or table records to support OSPF routing:

• IP Interface

• IP Parameters

• OSPF Routing Parameters

• OSPF Interface

• OSPF Area Parameter

SoTCP Configure these additional parameters or table records to support SoTCP:

• IP Interface

• SoTCP Map Table

• SoTCP Parameters

Note

When configuring the Route Selection Table, specify SOTCP as the destination
to which calls are routed.

Slim IP Configure these additional parameters or table records to support Slim IP on the

Vanguard 6560, 6520, 200 and 100:

• S IP record

• SNMP Agent Configuration record

3-4 Configuring a Vanguard Router

Configuration

IPX Configure these additional parameter or table records to support IPX routing over a

Novell network:

• IPX Parameters

• IPX Interfaces

IP Routing Configure these additional parameter or table records for routing in an IP network:

• IP Interface

• IP Parameters

For more information on ot her paramet ers and fea tures avail able for IP Routing refe r
to the IP Routing Manual (Part Number T0100-03).

Configuring a Vanguard Router 3-5
T0100-01, Revision B Release 5.4

Configuration

Example W ANVi ew Configuration - Point-to-Point L CONs

Introduction This example highlights how to configure a Vanguard Router to carry LAN traffic

over a WAN using WANView. Point-to-Point LCON will be used.

Example
Configuration ­Parameters and
Tables

Figure 3-2 below illustrates the functional diagram of the Vanguard Router and the
important parameters that should be configured. In this example, Node 200 and
Node 300 are configured to initiate calls to Node 100. When configuring Node 200

and Node 300’s LAN Connection Tables, an entry must be made for the autocall
mnemonic. In addition, the mnemonic table must be configured.

Note

Default valu es are used for parameters not specified in the table.

Figure 3-2. WANView Functional Diagram - Point-to-Point LCON

LAN
Port

1

5

FRI

Port 1

LCON 1

LAN

IP Forwarder

- Bridge

- Router

WAN Adaptor

W AN Port

WAN

Router Interface

6

LCON 2

FRI-1S1

FRI-1S2

Node 100

Node 200

Node 300

Port 5

Port 1

Port 1

LAN

LAN

Port 5

Port 5

10.33.1.1

10.33.1.2

10.33.2.1

10.33.2.2

Step

Menu Node 100 Node 200 Node 300

Configure the Node
Record

Configure --> Node Node Name: Node 100

Node Address: 100

Node Name: Node 200
Node Address: 200

Node Name: Node 300
Node Address: 300

Configure the WAN
Port

Configure --> Port Port Number: 1

Port Type: FRI
Connection Type: SIMP
Clock Source:EXT
Highest Station Number: 2
Control Protocol Support : LM I

Port Number: 1

Port Type: FRI
Connection Type: SIMP
Clock Source:EXT
Highest Station Number: 1
Control Protocol Support:LMI

Port Number: 1
Port Type: FRI
Connection Type: SIMP
Clock Source:EXT
Highest Station Number: 1
Control Protocol Support:LMI

Configure --> FRI Station Port Number: 1

Station Number: 1
Station Type: Annex G
DLCI: 16

Station Number: 2
Station Type: Annex G
DLCI: 17

Port Number: 1

Station Number: 1
Station Type: Annex G
DLCI: 16

Port Number: 1

Station Number: 1
Station Type: Annex G
DLCI: 17

Configure the LAN
Port

Configure --> Port Port Number: 5

Port Type: ETH

Port Number: 5
Port Type: ETH

Port Number: 5
Port Type: ETH

3-6 Configuring a Vanguard Router

Configuration

Configuration Tips These tips may be useful when configuring the example above:

• Remote Connection ID - the Remote Connection ID specifies exactly where
within the receiving node the call is to terminate. You specify the Remote
Connection ID in the LAN Connect ion Table for the node that initiat es call. In
this example, for Node 200, you must specify a Remote Connection ID of 1
which corresponds to Node 100’s LCON-1 or Entry 1 of the LAN Connection
Table.

• Route Selection Table - the function of the Route Selection Table is to allow
the X.25 Call request to be routed wit hin the node. The Route Sel ectio n Table
can be configured to pass the X.25 Call Request to a WAN Port (FRI-1s1) or
to an endpoint within the node, the LCON. Therefore, for Node 200 and 300,
which initiates calls , specify the X.25 calli ng address and the WAN Port as the
Destination. For the Node 100, which receives calls, specify the X.25 called
address and the LCON as the destination.

• Router Inter face - for WANView, specify a router interface for ea ch WAN
link. If for example you add additional nodes to the network, Node 400 and
500, you will be required to enable and configure two more interfaces
(interface 7 and 8) at Node 100.

Configure the
LCON

Configure --> Configure
LAN Connections -->
Configure LAN Connection
Parameter

Maximum Number of LAN
Connections: 32 (Default)

Maximum Number of LAN
Connections: 32 (Default)

Maximum Numb er of LAN
Connections: 32 (Default)

Configure --> Configure
LAN Connections -->
Configure LAN Connection
Table

Entry Number: 1
Interface Number: 5
LAN Forwarder Type: ROUT
LAN Connection Type:
PT-to-PT

Entry Number:2
Interface Number: 6
LAN Forwarder Type: ROUT
LAN Connection Type:
PT-to-PT

Entry Number: 1
Interface Number: 5
LAN Forwarder Type: ROUT
LAN Connection Type:
PT-to-PT
Autocall Mnemonic: Call100
Maximum Number of Autocall
Attempts: 0
Remote Connection ID: 1

Entry Number: 1
Interface Number: 5
LAN Forwarder Type: ROUT
LAN Connection Type:
PT-to-PT
Autocall Mnemonic: Call100
Maximum Numb er of Autocall
Attempts: 0
Remote Connection ID: 2

Configure the
Mnemonic Table

Configure --> Configure
Network Service -->
Configure Mnemonic Table

N/A Entry Number: 1

Mnemonic Name: Call100
Call Parameter: 10094

Entry Number: 1
Mnemonic Name: Call100
Call Parameter: 10094

Configure the
Router Interface

Configure --> Configure
Router --> Configure
Router Interface State

Interface #1 State: Enabled
Interface #5 State: Enabled
Interface #6 State: Enabled

Interface #1 State: Enabled
Interface #5 State: Enabled

Interface #1 State: Enabled
Interface #5 State: Enabled

Configure --> Configure
Router --> Configure IP -->
Interface

Entry Number: 1
Interface : 1
IP Address: 10.33.6.10

Entry Number: 2
Interface: 5
IP Address: 10.33.1.1

Entry Number: 2
Interface: 6
IP Address: 10.33.2.1

Entry Number: 1
Interface : 1
IP Address: 10.33.7.10

Entry Number: 2
Interface: 5
IP Address: 10.33.1.2

Entry Number: 1
Interface : 1
IP Address: 10.33.10.10

Entry Number: 2
Interface: 5
IP Address: 10.33.2.2

Configure the
Route Selection
Table

Configure --> Configure
Network Services -->
Route Selection Table

Entry Number:1
Address: 10094
Destination: LCON

Entry Number: 1
Address: 100
Destination: FRI-1s1
Priority 1

Entry Number: 1
Address: 100
Destination: FRI-1s1
Priority 1

Step

(continued)

Menu Node 100 Node 200 Node 300

Configuring a Vanguard Router 3-7
T0100-01, Revision B Release 5.4

Configuration

Example LAN View Configurat ion - Group LCONs

Introduction This example highlights how to configure a Vanguard Router to carry LAN traffic

over a WAN using LANView. Group LCON will be used.

Example
Configuration ­Parameters and
Tables

Figure 3-3 below illustrates the functional diagram of the Vanguard Router and the
important parameters that should be configured. In this example, Node 100 is
configured to initiates calls to Node 200 and Node 300. Only one router interf ace is
configured at Node 100 and the LAN Connection Type is set to GROUP.

Note

Default valu es are used for parameters not specified in the table.

Figure 3-3. LANView Functional Diagram - Group LCON

LAN
Port

1

5

FRI

Port 1

LCON 1

LAN

IP Forwarder

- Bridge

- Router

WAN Adaptor

W AN Port

Router Interface

LCON 2

FRI-1S1

FRI-1S2

WAN

Node 200

Node 300

Port 1

Port 1

LAN

LAN

Port 5

Port 5

Node 100

Port 5

Port 1

3-8 Configuring a Vanguard Router

Configuration

Step Menu Node 100 Node 200 Node 300

Configure the Node
Record

Configure --> Node Node Name: Node 100

Node Address: 100

Node Name: Node 200
Node Address: 200

Node Name: Node 300
Node Address: 300

Configure the WAN
Port

Configure --> Port Port Number: 1

Port Type: FRI
Connection Type: SIMP
Clock Source:EXT
Highest Station Number: 2
Control Protocol Support:LMI

Port Number: 1

Port Type: FRI
Connection Type: SIMP
Clock Source:EXT
Highest Station Number: 1
Control Protocol Support:LMI

Port Number: 1
Port Type: FRI
Connection Type: SIMP
Clock Source:EXT
Highest Station Number: 1
Control Protocol Support:LMI

Configure --> FRI Station Port Number: 1

Station Number: 1
Station Type: Annex G
DLCI: 16

Station Number: 2
Station Type: Annex G
DLCI: 17

Port Number: 1

Station Number: 1
Station Type: Annex G
DLCI: 16

Port Number: 1

Station Number: 1
Station Type: Annex G
DLCI: 17

Configure the LAN
Port

Configure --> Port Port Number: 5

Port Type: ETH

Port Number: 5
Port Type: ETH

Port Number: 5
Port Type: ETH

Configure the LCON Configure --> Configure

LAN Connections -->
Configure LAN
Connection Parameter

Maximum Number of LAN
Connections: 32 (Default)

Maximum Numb er of LAN
Connections: 32 (Default)

Maximum Number of LAN
Connections: 32 (Default)

Configure --> Configure
LAN Connections -->
Configure LAN
Connection Table

Entry Number: 1
Interface Number: 5
LAN Forwarder Type: ROUT
LAN Connection Type: Group
Autocall Mnemonic:Call200
Remote Connection ID: 1

Entry Number:2
Interface Number: 5
LAN Forwarder Type: ROUT
LAN Connection Type: Group
Autocall Mnemonic:Call300
Remote Connection ID: 1

Entry Number: 1
Interface Number: 5
LAN Forwarder Type: ROUT
LAN Connection Type: PT-to­PT

Entry Number: 1
Interface Number: 5
LAN Forwarder Type: ROUT
LAN Connection Type: PT- t o­PT

Configure the
Mnemonic Table

Configure --> Configure
Network Service -->
Configure Mnemonic
Table

Entry Number: 1
Mnemonic Name: Call200
Call Parameter: 20094

Entry Number: 1
Mnemonic Name: Call300
Call Parameter: 30094

N/A N/A

Configure the Router
Interface

Configure --> Configure
Router --> Configure
Router Interface State

Interface #1 State: Enabled
Interface #5 State: Enabled

Interface #1 State: Enabled
Interface #5 State: Enabled

Interface #1 State: Enabled
Interface #5 State: Enabled

Configure --> Configure
Router --> Configure IP -­> Interface

Entry Number: 1
Interface : 1
IP Address: 10.33.6.10

Entry Number: 2
Interface: 5
IP Address: 10.33.1.1

Entry Number: 1
Interface : 1
IP Address: 10.33.7.10

Entry Number: 2
Interface: 5
IP Address:10.33.1.2

Entry Number: 1
Interface : 1
IP Address: 10.33.10.10

Entry Number: 2
Interface: 5
IP Address: 10.33.1.3

Configure the Route
Selection Table

Configure --> Configure
Network Services -->
Route Selection Table

Entry Number: 1
Address: 200
Destination: FRI 1s1

Entry Number: 2
Address 300
Destination FRI 1s2

Entry Number: 1
Address: 20094
Destination: LCON

Entry Number: 1
Address: 30094
Destination: LCON

Configuring a Vanguard Router 3-9
T0100-01, Revision B Release 5.4

Configure LAN Connections

Configure LAN Connections

Introduction The Configure LAN Connection menu pr ovides access to the LAN Connection Table

and LAN Connection Parameters re cords. Figure 3-4 shows the Configure LAN
Connection Menu.

Figure 3-4. Configure LAN Connection Menu

Node: Address: Date: Time:
Menu: Configure LAN Connections Path:

LAN Connection Parameters
LAN Connection Table

3-10 Configuring a Vanguard Router

Configure LAN Connections

LAN Connection Parameters Menu

Introduction Use the LAN Connection Paramete rs menu to configure the number of LAN

Connections. The maximum number of configurable LAN Connections is 254.
These can be both Router Interfaces and Bridge links.

Note that since four Bridge links are assigned for LAN Bridge links, the number of
WAN Bridge Links supported is 250.

What You See in
This Record

Figure 3-5 shows the LAN Connection Parameters menu.

Figure 3-5. LAN Connection Parameters Menu

Parameter The Maximum Number of LAN Connections parameter is described below:

*Maximum Number of LAN Connections

Node: Address: Date: Time:
Menu: Configure LAN Connections Path:

1. LAN Connection Parameters

Range: 32 to 2000 (depends on the product)
Default: 32
Description: Specifies the configurable number of LAN Connections.

Connections are either Router Interfaces or Bridge links.

Configuring a Vanguard Router 3-11
T0100-01, Revision B Release 5.4

Configure LAN Connections

Configuring LAN Connection Table

What You See in
This Record

Figure 3-6 shows the LAN Connection Table Record.

Figure 3-6. LAN Connection Table

Note

Some parameters will only appear with entry or configuration of another
parameter. Refer to the “LAN Connection Table Record Parameters” section on

page 3-16 for parameter descriptions and guidelines.

Entry Number
LAN Forwarder Type
Bridge Link Number
LAN Connection Type
Router Interface Number
Encapsulation Type
Next Hop IP Address
Next Hop IPX Node Number
Autocall Mnemonic
Autocall Timeout
Maximum Number of Autocall Attempts
Remote Connection ID
Parallel SVCs
Parallel SVC Trigger Mechanism
Parallel SVC Threshold
Parallel SVC Port
On Demand
Idle Timeout
Broadcast
LCON Queue Limit
Billing Records
Traffic Priority
Protocol Priority Profiles
Credit Cycle
IP Precedence for Voice Traffic
RTP/UDP/IP Header Compression
Compression Type
UDP Port Ranges
Maximum Packet Size
Number of Session to be Compressed
Full Header Refresh Counter

Node: Address: Date: Time:
Menu: Configure LAN Connections Path:

LAN Connection Parameters

LAN Connection Table

3-12 Configuring a Vanguard Router

Configure LAN Connections

Configuration
Guidelines

When you configure the LAN Connection Table Record, use the following
guidelines:

• The Bridge Link Number must reference a configured Bridge Link.

• If an Autocall Mnemonic is specified, then the entry must exist in the
Mnemonic Table.

• If Billing Records are ON, then a Billing Printer Mnemonic must be specified
in the Mnemonic Table.

• If a LAN Connection is to receive calls, there must be an LCON entry in the
Routing Table.

Configuration
Matrix

The LAN Forwarder Type that you select determines the parameters that appear on
the screen. The follow ing table shows a matrix of the allowable combinations. An
“X” means that for the LAN Forwarder Type you configured, there is no prompt for
the listed parameter.

LANView Configuration Matrix

Parameter Displayed For ROUT LAN

Forwarder Type

For BRID LAN

Forwarder Type

For BROUT LAN

Forwarder Type

*LAN Forwarder Type ROUT BRID BROUT
*Bridge-Link

Number

X 5 to Maximum

Configurable

5 to Maximum

Configurable
LAN Connection Type PT_to_PT, GROUP X PT_to_PT, GROUP
*Router Interface

Number

5 to Maximum
Configurable

X 5 to Maximum

Configurable
Encapsulation Type CODEX, RFC877,

RFC1294
RFC877 requires

GROUP LAN
Connection Type

CODEX, RFC1294 CODEX, RFC1294

Next Hop IP Address Valid IP address in dotted

notation
Not prompted for LAN

Connection Type of
PT_to_PT

X Valid IP address in dotted

notation

Not prompted for LAN

Connection Type of

PT_to_PT
Next Hop IPX Node

Number

Up to a 12-digit number
Not prompted for LAN

Connection Type of
PT_to_PT

Not prompted for
Encapsulation Type of
RFC877

X Up to a 12-digit number

Not prompted for LAN

Connection Type of

PT_to_PT

Not prompted for

Encapsulation Type of

RFC877

Configuring a Vanguard Router 3-13
T0100-01, Revision B Release 5.4

Configure LAN Connections

Autocall
Mnemonic

0 to 8 alphanumeric
Must be configured if

Encapsulation Type of
RFC877

0 to 8 alphanumeric 0 to 8 alphanumeric

Autocall Tim eout 5 to 255 seconds

Not prompted if Autoca ll
Mnemonic not entered

5 to 255 seconds
Not prompted if Autoca ll

Mnemonic not entered

5 to 255 seconds

Not prompted if Autocall

Mnemonic not entered
Maximum Number of

Autocall Attempts

0 to 255 times
Not prompted if Autoca ll

Mnemonic not entered

0 to 255 times
Not prompted if Autoca ll

Mnemonic not entered

0 to 255 times

Not prompted if Autocall

Mnemonic not entered
Remote

Connection ID

1 to 254
Appears if Autocall

Mnemonic configured
and Encapsulation Type
is not RFC877

1 to 254
Appears if Autocall

Mnemonic configured
and Encapsulation Type
is not RFC877

1 to 254

Appears if Autocall

Mnemonic configured

and Encapsulation Type

is not RFC877
Parallel SV Cs 0 to 1

Appears if Autocall
Mnemonic configured
and Encapsulation Type
is not RFC1294

No prompt appears if
LAN Connection Type is
GROUP and Next Hop
IP Address is 0.0.0.0.

X0 to 1

Appears if Autocall

Mnemonic configured

and Encapsulation Type

is not RFC1294

No prompt appears if

LAN Connection Type is

GROUP and Next Hop

IP Address is 0.0.0.0.
Parallel SVC Threshold 1 to 65534

Appears if Parallel SVCs
configured to non-zero
value or the
Encapsulation Type is
RFC 877

X 1 to 65534

Appears if Parallel SVCs

configured to non-zero

value or the

Encapsulation Type is

RFC 877
Parallel SVC Port 0 to 32 alphanumeric

Appears if Parallel SVCs
configured to non-zero
value

X 0 to 32 alphanumeric

Appears if Parallel SVCs

configured to

non-zero value

LANView Configuration Matrix

(continued)

Parameter Displayed For ROUT LAN

Forwarder Type

For BRID LAN

Forwarder Type

For BROUT LAN

Forwarder Type

3-14 Configuring a Vanguard Router

Configure LAN Connections

On Demand ENABLED, DISABLED

Appears if Autocall
Mnemonic configured
and Encapsulation Type
is CODEX

XX

Idle Timeout 0 to 65534 seconds

Appears if Encapsulati on
Type is RFC877, or On
Demand is Enabled, or
Parallel SVCs are
configured

XX

Broadcast ENABLED, DISABLED

Appears with GROUP
LAN Connection Type

X ENABLED, DISABLED

Appears with GROUP

LAN Connection Type
LCON Queue Limit 0 to 65534 0 to 65534 0 to 65534
Billing Records ON, OFF ON, OFF ON, OFF
Traffi c Priority LOW, MED, HIGH,

EXP, LOW-AND­PROTOCOL, MED­AND-PROTOCOL,
HIGH-AND­PROTOCOL, EXP­AND-PROTOCOL

LOW, MED, HIGH,
EXP, LOW-AND­PROTOCOL, MED­AND-PROTOCOL,
HIGH-AND­PROTOCOL, EXP­AND-PROTOCOL

LOW, MED, HIGH,

EXP, LOW-AND-

PROTOCOL, MED-

AND-PROTOCOL,

HIGH-AND-

PROTOCOL, EXP-

AND-PROTOCOL
Protocol Pr iority Profiles 1 to 100

Appears if Traffic
Priority is co nfigured as
LOW-AND­PROTOCOL, MED­AND-PROTOCOL,
HIGH-AND­PROTOCOL, or EXP­AND-PROTOCOL

1 to 100
Appears if Traffic

Priority is co nfigured as
LOW-AND­PROTOCOL, MED­AND-PROTOCOL,
HIGH-AND­PROTOCOL, or EXP­AND-PROTOCOL

1 to 100

Appears if Traffic

Priority is co nfigured as

LOW-AND-

PROTOCOL, MED-

AND-PROTOCOL,

HIGH-AND-

PROTOCOL, or EXP-

AND-PROTOCOL
Credit Cycle 1 to 200

Appears if Traffic
Priority is co nfigured as
LOW-AND­PROTOCOL, MED­AND-PROTOCOL,
HIGH-AND­PROTOCOL, or EXP­AND-PROTOCOL

1 to 200
Appears if Traffic

Priority is co nfigured as
LOW-AND­PROTOCOL, MED­AND-PROTOCOL,
HIGH-AND­PROTOCOL, or EXP­AND-PROTOCOL

1 to 200

Appears if Traffic

Priority is co nfigured as

LOW-AND-

PROTOCOL, MED-

AND-PROTOCOL,

HIGH-AND-

PROTOCOL, or EXP-

AND-PROTOCOL

LANView Configuration Matrix

(continued)

Parameter Displayed For ROUT LAN

Forwarder Type

For BRID LAN

Forwarder Type

For BROUT LAN

Forwarder Type

Configuring a Vanguard Router 3-15
T0100-01, Revision B Release 5.4

Configure LAN Connections

IP Precedence for Voice
Traffic

0 to 7
Appears if Traffic

Priority is co nfigured as
LOW-AND­PROTOCOL, MED­AND-PROTOCOL,
HIGH-AND­PROTOCOL, or EXP­AND-PROTOCOL

0 to 7
Appears if Traffic

Priority is co nfigured as
LOW-AND­PROTOCOL, MED­AND-PROTOCOL,
HIGH-AND­PROTOCOL, or EXP­AND-PROTOCOL

0 to 7

Appears if Traffic

Priority is co nfigured as

LOW-AND-

PROTOCOL, MED-

AND-PROTOCOL,

HIGH-AND-

PROTOCOL, or EXP-

AND-PROTOCOL

LANView Configuration Matrix

(continued)

Parameter Displayed For ROUT LAN

Forwarder Type

For BRID LAN

Forwarder Type

For BROUT LAN

Forwarder Type

3-16 Configuring a Vanguard Router

Configure LAN Connections

LAN Connection Table Record Parameters

Introduction This section describes the LAN Connection Record parameters. Any parameter with

an asterisk (*) requires a Node boot; changes to other parameters require a Table
Record boot.

Parameters From the LAN Connection Table Record, you can conf igure the following

parameters:

Entry Number

Range: 1 to n, where n = 32 to 2000 (depending on the product)
Default: 1
Description: Specifies the entry number used to reference this table record. The

allowable range of values reflect the maximum number of LAN
connections set in the LAN Connection Parameters menu.

*LAN Forwarder Type

Range: ROUT, BRID, BROUT
Default: ROUT
Description: Specified if the LAN Connect ion i s to pass b ridged , rout ed, and /or

brouted traffic:

• BRID: Bridged LAN traffic is transported across this
connection.

• ROUT: Routed LAN traffic is transported across this
connection.

• BROUT: Both bridged and rou ted LAN traf f ic are trans porte d
across this connection.

Boot Type: Changes to this parameter require a Node Boot to take effect.

Configuring a Vanguard Router 3-17
T0100-01, Revision B Release 5.4

Configure LAN Connections

*Bridge Link Number

Range: 5 to n, where n = 36 to 250
Default: 5
Description: Specifies the Bridge link using this LAN Connection record. This

connection makes it possible to pass LAN data through the WAN
network to a remote Vanguard bridge. The allowable range of
values reflects the maximum number of bridge links set in the
Bridge Parameters Menu.

For more information, refer to the Bridging Manual

(Part Number T0100-04).
Guidelines: Appears only with the LAN Forwarder Type = BRID or BROUT.
Boot Type: Changes to this parameter require a Table and Node Record boot.

LAN Connection Type

Range: PT_to_PT, GROUP
Default: PT_to_PT (Point-to-Point)
Description: Specifies whether this LAN Connection defines a point-to-point

connection across the WAN, or is part of a group of LAN

Connections. If configur ed as GROUP, multiple LAN Connecti ons

can use the same Router Interface number. If configured as

PT_to_PT, the Router Interface configured must be unique to this

LAN Connection.
Guidelines: Appears only if the LAN Forwarder type is configured as ROUT

or BROUT.
Boot Type: When changing from GROUP to PT_PT, a Node boot is required.

Otherwise, a Table and Node Record boot is required.

3-18 Configuring a Vanguard Router

Configure LAN Connections

*Router Int e rface Number

Range: 5 to n, where n = 36 to 254
Default: 5
Description: Specifies a Router Interface using this LAN Connection record.

This connection makes it possible to pass LAN data through the

WAN network to a remote Vanguard router. The allowable range

of values reflects t he maximum numbe r of I P or IPX in terf aces se t

in the IP or IPX Parameters Menu.
Guidelines: Appears if the LAN Forwarder Type is configured as ROUT or

BROUT
Boot Type: Changes to this parameter require a Node Boot to take effect.

Encapsulation Type

Range: • CODEX, RFC 877, RFC 1294

(if LAN Forwarder Type = ROUT)

• CODEX (if LAN Forwarder Type = BRID)

• CODEX (if LAN Forwarder Type = BROUT)
Default: CODEX
Description: Specifies the type of encapsulation used over this LAN

connection. Encapsulation types supported include:

• CODEX: Codex Proprietary Encapsulation

• RFC 877/1356: RFC 877/1356 X.25 protocol encapsulation

for IP

• RFC 1294/1490: RFC 1294/1490 multiproto col enca psulatio n

over Frame Relay

Guidelines: Codex Proprietary encapsulation is required when

LAN Forwarder Type = BRID or BROUT.

Boot Type: Changes to this parameter require a Table and Node Record boot

to take effect.

Configuring a Vanguard Router 3-19
T0100-01, Revision B Release 5.4

Configure LAN Connections

Next Hop IP Address

Range: A valid IP address in dotted decimal notation
Default: 0.0.0.0
Description: Specifies the IP a ddress of t he Rout er Inte rface on t he other end of

this LAN Connection, which is the next hop on the path to the
final destination. Th is LAN Connection i s used if it is t he optimum
route to reach the destination IP address. Note that the Network
and Host portion of the IP address is needed.

A setting of 0.0.0.0 for a LAN connection using RFC 1294
encapsulation and mapped to a Frame Relay BYPASS station or
Annex G circuit will result in an InvARP Request being sent.

For all other LAN connections a value of 0.0.0.0 causes this
parameter to be ignored.

Guidelines: Appears only if the LAN Connection type is configured as

GROUP.

Next Hop IPX Node Number

Range: 1 to 12 hexadecimal digits
Default: 0
Description: Specifies the IPX node number of the Router on the other end of

this LAN Connection, which is the next hop on the path to the
final destination. This LAN Connection is used if this is the
optimum route to reach the destination IP address.

A setting of 0 causes this parameter to be ignored.

Guidelines: Appears only if the LAN Connection Type is configured as

GROUP and the Encapsulation Type is CODEX or RFC1294.

3-20 Configuring a Vanguard Router

Configure LAN Connections

Autocall Mnemonic

Range: 0 to 8 alphanumeric characters
Default: If (blank), this means autocalling is not initiated by this LAN

connection entry; the LAN Connection Table entry at the remote

device must initiate the call.
Description: Used when this LAN Connection record initiates the autocall.
Guidelines: • A corresponding entry must be made in the Mnemonic Table.

• If this record is configured for autocalling, then the referenced
Autocall Mnemonic will contain a remote address that this
LAN connection uses in an X.25 call.

• Address must equal the address of the node to which the
remote LAN is attached (the LAN to which you want to
bridge). The LAN Connection Subaddress configured in the
node record is appended to this address to form the complete
called address of an X.25 call packet.

Autocall Timeout

Range: 5 to 255
Default: 5
Description: Interval in seconds bet ween calling attempts when auto calling .
Boot Type: Changes to this parameter require a Table and Node Record boot.

*Maximum Number of Autocall Attempts

Range: 0 to 255
Default: 10
Description: Specifies the number of times the LAN connection attempts to

autocall a remote destination. A value of 0 allows unlimited
attempts.

Boot Type: Changes to this parameter require a Table and Node Record boot.

Configuring a Vanguard Router 3-21
T0100-01, Revision B Release 5.4

Configure LAN Connections

Remote Connection ID

Range: 1
Default: 1
Description: When the LAN Connection Record sends a call request, this

parameter specifies which target WAN Adapter LAN Connection
Table to connect to.

The Remote Connection ID is ca rried in the Call User Data (CUD)

field of the call request packet when Encapsulation Type = CODEX.
Boot Type: Changes to this parameter require a Table and Node Record boot.
Guidelines: Appears only with:

• CODEX or RFC 1294 encapsulation

• Autocall mnemonic entered

*Parallel SVCs

Range: 0 to 1
Default: 0
Description: Specifies the maximum number of parallel connections that can be

established to the remote destination. Parallel SVCs are established

when congestion thresholds are reached on active connections.
Boot Type: Changes to this parameter require a Table and Node Record boot.
Guidelines: Appears only if:

• LAN Forwarder Type is configured as ROUT/BROUT

• An Autocall Mnemonic name has been specified

• Encapsulation Type is either RFC 877 or CODEX

Parallel SVC Trigger Mechanism:

Range: THRESHOLD, PORT_CONGEST
Default: THRESHOLD
Description: Specifies which criterion is used to activate or deactivate parallel

SVCs.

• THRESHOLD - The length of the queue at the LAN-WAN
interface determines when to bring up a second link.

• PORT_CONGESTION - The port utiliz ation i s compared to the
configured thresholds to determine when to activate or
deactivate a second link.

Guidelines: If using the PORT_CONGEST value, you must configure the

Network Services BoD Table parameters .

3-22 Configuring a Vanguard Router

Configure LAN Connections

Parallel SVC Threshold

Range: 0 to 65534
Default: 8000
Description: Specifies the number of outstanding data bytes that triggers the

use of a Parallel SVC. If this number of dat a bytes was trans mitted
without acknowledgment, the receipt of additional data for
transmission triggers Parallel SVC use. If a Parallel SVC doesn’t
exist, one is established (if the Paralle l SVCs parameter is
configured to a non-zero value). Note that this parameter must be
configured with a value less than the LCON Queue Limit
parameter.

Guidelines: Appears only if the Parallel SVC field is configur ed to a non-zero

value, or the Encapsul ation Type is RFC 877, and parallel SVC
Trigger Mechanism is set to THRESHOLD.

Parallel SVC Port

Range: 0 to 32 alphanumeric characters. Use the space character to blank

the field.
Default: blank
Description: Specifies the port over which the Parallel SVC is established.

Allowable values can take one of two forms. The first is a port

identifier string. For example, to send the Parallel SVC over port

8:

a) Enter the string X25-8.

The other form is a Switched Services Table destination name. For

example, if the port that the Parallel SVCs come up over is a dial

on demand port:

a) Enter th e string “New York”.
b) In the corresponding entry in the Switched Services Table,

map “New York” to any port string, for example, X25-8.

If left blank, the Parallel SVC is established over the same port as

the Primary SVC.
Guidelines: Appears only if the Parallel SVC field is configur ed to a non-zero

value.

Configuring a Vanguard Router 3-23
T0100-01, Revision B Release 5.4

Configure LAN Connections

On Demand

Range: ENABLED/DISABLED if Encapsulation Type = CODEX
Default: DISABLED if Encapsulation Type = CODEX.

On when Encapsulation Type = RFC 877.
Description: Specifies whether a ci rcuit is es tablished at system star tup, or upon

receiving data to pass. On Deman d SVCs can supp ort IP, IPX, and

Asynchronous traffic over X.25 by becoming active when there is

data to send and deactivating once all data has been sent.
Guidelines: Appears only with:

• LAN Forwarder Type = ROUT and,

• Autocall mnemonic is entered.

Boot Type: Changes to this parameter require a Table and Node Record boot.

*Idle Timeout

Range: 0 to 65535 seconds
Default: 90 seconds
Description: Specifies the amount of time in seconds the SVC remains

connected without passing data before the SVC is deactivated.

Any positive value deactivates the On Demand SVC as stated

earlier in this document.

A zero Idle Timer entry allows the SVC to come up as On

Demand, but when there is no more data to send, the link remains

active and functions as a Permanent SVC.
Boot Type: Changes to this parameter require a Node boot.
Guidelines: Appears only with:

• LAN Forwarder Type configured as ROUT and,

• RFC 877, or CODEX configured with On Demand
ENABLED and,

• Autocall mnemonic entered.

Broadcast

Range: ENABLE, DISABLE
Default: Enabled
Description: Specifies whether broadcast datagrams are transmitted over this

LAN Connection to the remote destination.

Guidelines: Appears only if the LAN Connection Type is configured as

GROUP.

3-24 Configuring a Vanguard Router

Configure LAN Connections

LCON Queue Limit

Range: 0 to 65536
Default: 16000
Description: The LCON Queue Limit parameter specifies the maximum

number of bytes that are queued for this LAN before transmission
on the WAN link. Set this parameter for two seconds of data on the
WAN link.

Billing Records

Range: OFF, ON
Default: OFF
Description: Enables or disables the creation (storing and printing) of billing

records for the LAN connection:

• ON: Billing records are generated.

• OFF: Billing records are not generated.

Traffic Priority

Range: LOW, MED, HIGH, EXP, LOW-AND-PROTOCOL, MED-AND-

PROTOCOL, HIGH-AND-PROTOCOL, EXP-AND-

PROTOCOL
Default: HIGH
Description: Specifies the Traffic Priority level of this LAN Connection and

also enables Protocol Priority depending on the option configured.

• LOW: One Low Priority packet is sent for every Traffic
Priority Ste p number of Medium priority packets.

• MED: One Medium priority packet is sent for every Traffic
Priority Ste p number of High priority p ackets.

• H IGH: High i s the first level of priority packets sent, if no
expedite priority packets are sent.

• EXP: Expedite priority packets have the highest priority and
use all of the link bandwidth that they need. Any remaining
bandwidth is shared by the high, medium, and low priority
packets.

• LOW-AND-PROTOCOL - Low Priority with Protocol
Priority enabled.

• MED-AND-PROTOCOL - Medium Priority with Protocol
Priority enabled.

• HIGH-AND-PROTOCOL - High Priority with Protocol
Priority enabled.

• EXPEDITE-AND-PROTOCOL - Expedite Priority with
Protocol Pr iority enable d.

Configuring a Vanguard Router 3-25
T0100-01, Revision B Release 5.4

Configure LAN Connections

Protocol Priority Profiles

Range 1 to 100
Default 1
Description You can specify up to three protocol priority profiles. Enter the

profiles separated by a comma (,) as shown:

1, 2
or
1 , 2 , 3

These profiles correspond to the entry numbers of the Protocol
Priority Profile table configured under Configure Network
Services. The order in which the profiles are specified indicates
the order of priority among the profil es. These profile s are used for
classifying and servicing the traffic flows depending on the class
and bandwidth assignments configured.

Credit Cycle

Range 1 to 200
Default 4
Description Specifies the granularity of traffic forwarding in KBytes. This is

the block of byte transfer within which each class has its share
depending on its assigned percentage and is used for the
bandwidth allocation for each traffic class as configured in the
Protocol Priority Profile Table.

(For example, If port speed or CIR equals 64000 Kbits, credit
cycle equa ls:
64,000/8

2

3-26 Configuring a Vanguard Router

Configure LAN Connections

IP Precedence for Voice Traffic

Default 0
Range 0-7

0 - Routine
1 - Priority
2 - Immediate
3 - Flash
4 - Flash Override
5- Critical/E CP
6 - Internetw ork Control
7 - Network Control

Description Specifies the IP Precedence for provided FAST PATH service for

voice packets. Enter a non-zero value to enable.
If the voice module in the Vanguard has already classified an

incoming packet as voice class, the IP precedence in the packet
will be set to the configured IP precedence value.

If the incoming packet has not been classified, the IP precedence
in the packet will be compared against the configured IP
precedence value. If th e valu es match, t hen the incoming packet is
classified as voice class and receives FAST PATH service.

RTP/UDP/IP Header Compression

Default DISABLE
Range DISABLE, TRANSMIT, RECEIVE, DUPLEX, AUTODETECT
Description Enables or disables header compression on this LCON:

• DISABLE - disables header compression.

• TRANSMIT - indicates that compressed packets are
transmitted but not received.

• RECEIVE - indicates that compressed packet s are received
only but not transmitted.

• DUPLEX - indicates that compressed packets are received
and transmitted.

• AUTODETECT- indicates that if the incoming traffic is
compressed then the outgoing traffic will be compressed.

Note

RTP/UDP/IP header compression parameters only appear if
Encapsulation Type is set to RFC 1294.

Configuring a Vanguard Router 3-27
T0100-01, Revision B Release 5.4

Configure LAN Connections

Compression Type

Default RTP
Range RTP, UDP, RTP+UDP
Description Specifies the compression type:

• RTP - This option compresses RTP/UPD/IP packet headers
only. The Vanguard only tries to compress packets with even
number UDP ports and UDP header packet size greater than
12 bytes.

• UDP - This option compresses UDP/IP header compression
only . Thi s allows voice hea der pac ket compre ss ion. However,
the RTP header of the RTP/UDP/IP stream is not compressed.

• RTP+UDP - This option allows both RTP/UDP/IP and
UDP/IP header compression. If this is configured, all packets
are compressed.

Note

Changes to this parameter causes the context list to be refreshed.

UDP Port Ranges

Default 1025-65535
Range 1025 to 65535
Description Specifies a range of UDP ports. Header compression applies to

packets re ceived or transmitted on this range of UDP ports .
Specify the parameter as individual ports or a range of ports; for
example 1025-6500, 6567, 7600-7650.

A maximum of eight port ranges can be specified.

Maximum Packet Size

Default 0
Range 0 to 2048
Description Specifies the maximum size of the packet to be compressed.

Packets with size exceeding this value are not compressed.
If this parameter is set to 0, then maximum packet size is ignored.

3-28 Configuring a Vanguard Router

Configure LAN Connections

Note

There are four additional RTP/UDP/IP Header Compression DEBUG
parameters. Unless you are a thoroughly experienced network professional,
operating in the DEBUG Mode is not recommended. Please contact your
Motorola Service Representative for additional information.

Number of Session to be Compressed

Default 255
Range 1 to 1024
Description Specifies the number of session to be compressed. Chan ges to th is

parameter causes the context list to be refreshed.
Each compression session that exists between the compressor and

decompressor is uniquely i denti fied by a sessi on conte xt iden ti fier
(CID). The CID can be 8 or 16 bit. When the configured value
exceeds 255, a 16 bit C ID.

Full Header Refresh Counter

Default 0
Range 0 to 1000
Description A setting of 0 indicates that there is no periodic transfer. A setting

of 1 to 1000 indicates the number of compressed packet
transmitted before a FULL HEADER packet is retransmitted.

LAN Connection Statistics 4-1

Chapter 4

LAN Connection Statistics

Overview

Introduction This chapter describes how to monitor the performance and operation of the

Vanguard using LAN Connection statistics.

4-2 LAN Connection Statistics

Using LAN Connection Statistics

Using LAN Connection Statistics

Function The LAN Connection Statistics menu s provides options for viewing various LAN

Connection statistics.

What You See in
This Screen

Figure 4-1 shows the LAN Connection Statistics menu. Select the appropriate
number to view a particular screen.

Figure 4-1. LAN Connection Statistics Menu

Selections The LAN Connection Statistics menu provides these LAN statistics options:

Node: Address: Date: Time:
Menu:Lan Connection Statistics Path:

LAN Connection Stats
Connection Summary Stats
RTP/UDP/IP Compression Stats
LAN Connection Group Statistics
Reset LAN Connection Stats

Menu Option Displays...

LAN Connection Stats Detailed transmit and receive statistics

for primary and Parallel SVCs.

LAN Connection Summary Stats An overall picture of the LANView

indicating which connections are
currently active.

LAN Connection Group Statistics A single line of address information for

each next hop destination in a LAN
Connection Group.

RTP/UDP/IP Compression Stats Statistics for RTP/UDP/IP header

compression for each LCON entry.

LAN Connection Statistics 4-3
T0100-01, Revision B Release 5.4

Using LAN Connection Statistics

LAN Connection St at istics

Function When you select LAN Connection S tatistic s, the Detailed LAN Connect ion Stat istics

screen provides three pages of detailed information about all current LAN
Connections and LAN Connection Groups.

What You See in
This Screen

An example of a Detailed LAN Connection S tati stics scree n is shown in Figure s 4-2,
4-3, and 4-4.

Figure 4-2. Detailed LAN Connection Statistics Screen, Page 1

Figure 4-3. Detailed LAN Connection Statistics Screen, Page 2

Node: Address: Date: Time:
Detailed LAN Connection Statistics: LCON-1 Page: 1 of 3

Call Summary:
Connection Type: GROUP SVC(O) Encapsulation Type: CODEX

Connection State: Connected
Forwarders Connected: Router
Remote Address: 80094
Next Hop IP Address: 134.33.200.4 Next Hop IPX Node Number: 15
Number of auto-call attempts: 1
Last clear cause code:
Last clear diagnostic code:

Packet Summary: Transmit Receive
Data 221 403

Call Request 1 0
Call Accept 0 1
Clear Request 0 0
Clear Confirm 0 0
Reset Request 0 0
Reset Confirm 0 0

Press any key to continue ( ESC to exit ) ...

Last Statistics Reset:
Transmit Data Summary:

Number of Packets Transmitted: 222
Average Transmit Packet Size: 77
Current Transmit Queue Depth: 0
Maximum Transmit Queue Depth: 2 at

Receive Data Summary:
Number of Packets Received: 403
Average Receive Packet Size: 188

Discard Summary:
Packets Discarded Due to Max Frame Size Exceeded: 0
Transmit Packets Discarded Due to Node Transit Delay: 0
Transmit Packets Discarded Due to Congestion: 0
Transmit Packets Discarded Due to Clear Requests: 0
Transmit Packets Discarded Due to Call Establishment Failure: 0

Press any key to continue ( ESC to exit ) ...

4-4 LAN Connection Statistics

Using LAN Connection Statistics

Figure 4-4. Detailed LAN Connection Statistics Screen, Page 3

Note

Information appearing above the dashed line on page three applies to primary
SVCs. Info rmation belo w the dashed line applies to any Para llel SVCs.

Node: Address: Date: Time:
Detailed LAN Connection Statistics: LCON-1 Page: 3 of 3

Outbound TX Pck Avg TX TX Bytes RX Pck Avg RX
Channel Count Pck Size Outstanding Count Pck Size
========= ========== ========== =========== ========== ==========

FRI-3S1(1) 9 18 1 6 31

-------------------------------------------------------------------­X25-4 (1) 100 64 2000 150 56

Press any key to continue ( ESC to exit ) ...

LAN Connection Statistics 4-5
T0100-01, Revision B Release 5.4

Using LAN Connection Statistics

Screen Terms The Detailed LAN Connection Statistics screen provides the following information:

Term Indicates...

Call
Summary

This field provides information about the following:

• Connection Type: Specifies whether the connection is point-to-
point (PT_to_PT) or GROUP, and whether an SVC or a PVC is
established.

• Connection State: Specifies the current state of the PVC or SVC.
The possible states are: Unconfigured, Calling, Awaiting Call,
Awaiting Data, Connected, Autocall Failure, Software Disabled,
Operator Disabled, Congested.

• Forwarders Connected: Specifies which forwarders are currently
connected to this LAN Connection: Source Route; Spanning
Tree.

• Remote Address: Specifies the called address of the remote W AN
Adapter LAN Connection for connected SVCs. The possible
states are: Blank for PVCs; blank for disconnected SVCs; No
Mnemonic (for autocall SVCs whose mnemoni c does not exi st in
the Mnemonic Table); Max Attempts (for Autocall SVCs that
reached their autocall maximum attempts count).

• Next Hop IP Address: Specifies the IP address of the next
destination in a path, if the LCON is configured as GROUP (that
is, if it is part of a LANView.)

• Next Hop IPX Node Number: Specifies the IPX next hop node
number if the LCON is configured as GROUP (that is, i f it is par t
of a LANView.)

• Number of auto call attempts: Specifies the number of times the
WAN Adapter attempted to autocall before it either succeeded or
failed in establishing the connection.

• Last clear cause code: This is the cause code in the call clear
packet last received by the LAN connection, and explains why
the last call was cleared.

• Last clear diagnostic code: This is the diagnostic code in the call
clear packet last received by the LAN Connection and explains
why the call was cleared.

4-6 LAN Connection Statistics

Using LAN Connection Statistics

Packet
Summary

• Data: Summary of each packet sent on the WAN and received
from the WAN bridge link.

• Call Request: Specifies the total number of Call Reques t Packets
sent on the WAN and received from the WAN.

• Call Accept: Specifies the total number of Call Accept Packets
sent on the WAN and received from the WAN.

• Clear Request: Specifies the total number of Clear Request
Packets se nt on the WAN.

• Clear Confirm: Specifies the total number of Clear Confirmation
Packets sent on the WAN and received from the WAN.

• Reset Request: Specifies the total number of Reset Request
Packets sent on the WAN and received from the WAN.

• Reset Confirm: Specifies the total number of Rese t Confirmation
Packets sent on the WAN and received from the WAN.

Fields within the Packet Summary group may report values even
though the Connection State field indicates that the SVC is in the
calling state. In coming data packets from the LAN Forwarder a re on e
example of this condition.

Last
Statistics
Reset

Date and time of the last statistics reset. Resetting the statistics does
not clear the last call information from the detailed port statistics
screen. This information is cleared only on a node boot.

Transmit
Data
Summary

Information on the tr ansmission of packets and those awaiting
transmission to the WAN. Totals are provided for: the number of
packets transmitted, the average transmitted packet size in bytes, and
the current and maximum transmit queue depths in packets.

Receive
Data
Summary

Information on the number of packets re ceived and the av erage size of
the packets received from the WAN. Totals are provided for: the
number of packets received and the average received packet size in
bytes.

Discard
Summary

This field provides the fo llowing totals for packets discarded for the
following reasons:

• Transmit Packets Discarded Due to Max Frame Size Exceeded.

• Transmit Packets Discarded Due to Node Transit Delay.

• Transmit Packet Discarded Due to Congestion (data buffered
more than 1 sec.).

For LAN Connections that are part of a LANView, a single line appears with the
following items for each SVC to a next hop destination.

Outbound
Channel

Identity string of the outbound channel.

Tx Pck
Count

Total number of packets transmitted.

A vg Tx Pck
Size

Average transmitted packet size.

Term Indicates...

LAN Connection Statistics 4-7
T0100-01, Revision B Release 5.4

Using LAN Connection Statistics

Tx Bytes
Outstand­ing

Total number of transmit bytes outstanding.

Rx Pck
Count

Number of packets received.

Avg Rx
Pck Size

Average receive packet size.

Term Indicates...

4-8 LAN Connection Statistics

Using LAN Connection Statistics

LAN Connection Summary St at istics

Function The LAN Connection Summary Statistics screen provides an overall picture of the

LANView indicating which connections are currently active.

What You See in
This Screen

Figure 4-5 shows an example of the LAN Connection Summary Statistics screen.

Figure 4-5. LAN Connection Summary Statistics Example

Screen Terms The LAN Connection Summary Statistics screen provides this information:

Node: Address: Date Time:
LAN Connection Summary Status Page: 1 of 1

LAN Bridge Conn. Remote
Connection Link Type Destination
================== ================ ========== =====================
1 Waiting 5 Configured SVC

Press any key to continue ( ESC to exit )

Term Indicates...

LAN
Connection

LAN Connection entry number and current state of a conf igured
LAN Connection. The possible states are:

• Not Properly Configured

• Not Connected

•Calling

• Awaiting Call

• Awaiting Data

• C onnected

• Waiting for Clear Confirmation

•Disabled

Bridge Link WAN Bridge Link number associated with this LAN connection.

The possible current states of the WAN Bridge Link are:

• Not Applicable

• Emp ty; Mismatch

• In active; Active

• C ongested

• Software Disabled

• U ser Disabled
Connection Type LAN Connection is a PVC, a Calling SVC, or a Called SVC.
Remote

Destination

Remote destination t o which th is LAN Conne ction is co nnecte d.
This includes the Remote Connection ID.

LAN Connection Statistics 4-9
T0100-01, Revision B Release 5.4

Using LAN Connection Statistics

RTP/UDP/IP Compression Statistics

Function The RTP/UDP/IP Compression statistics provide detailed information on

compression applied t o packe ts re ceived or tr ansm itte d on a pa rtic ular L CON. When
you access the RTP/UDP/IP Compression statistics menu you will be prompted to
enter the LCON number.

What You See In
This Screen

Figure 4-6 and Figure 4-7 shows examples of the RTP/UDP/IP Compression
Statistics screens.

Figure 4-6. RTP/UDP/IP Compression Statistics Screen Page 1 of 2

Node: Address: Date: Time:
RTP/UDP/IP Compression Statistics Page: 1 of 2

LAN Connection Entry #3

Transmission Type: DUPLEX Compression Type: RTP

Packets Received for Compression: 0 Compressed Packets Transmitted: 0

Packets Receiver Received: 0 Compressed Packets Received: 0

Active Transmittor Contexts: 0 Active Receivers Contexts:0

Bytes Received by Compressor: 0 Bytes transmitted after Compression: 0

Bytes Received by Decompressor: 0 Bytes forwarded after Decompression: 0

Total Contexts:0
Negative Cache Entries:0
Errors detected by receiver: 0
Synchronization Lost packets received: 0
Synchronization Lost packets transmitted: 26

4-10 LAN Connection Statistics

Using LAN Connection Statistics

Figure 4-7. RTP/UDP/IP Compression Statistics Screen Page 2 of 2

Screen Terms The RTP/UDP/IP Compression Statistics screen contains the following info rmation:

Node: Address: Date: Time:
RTP/UDP/IP Compression Statistics Page: 2 of 2

Context Entries

Type SourceIPAddr DestIPAddr ScrUDPPort DestUDPPort SSRC Error
Transmit 217.1.84.1 2.2.2.2 5005 5005 1 0
Transmit 84.1.34.2 3.3.3.3 5006 6005 1 0
Receive 3.3.3.3 5.5.5.5 6006 6000 1 0

Press any key to continue ( ESC to exit ) ...

Term Indicates...

Transmission Type The connection type that is active.
Compression Type The compression type that is active.
Packets Received for

Compression

Total number of packets qualified for compression based on the
configured values. Only UDP/IP packets matching the configuration are
considered.

Compressed Packets
Transmitted

Total number of compressed packets transmitted. (This includes only
COMPRESSED_RTP & COMPRESSED_UDP.)

Packets Receiver Received Total number of packets the receiver compressor module received. This

includes FULL_HEADER packets and COMPRESSED packets.
Compressed Packets Received Total num ber of compressed packets received.
Active Transmitter Contexts Number of active context entries in the transmittor (compressor) context

list.
Active Receiver Contexts Number of active context entries in the receiver (decompressor) context

list.
Bytes Received for Compression Total bytes recei ved for compress ion based on the configured pa rameters.
Bytes trans mitted after

Compression

Total bytes transmitted after compression.

Bytes Received by Receiver Total bytes received by the receiver (decompressor) module for

decompression.
Bytes forwarded after

Decompression

Total bytes forwarded after decompression.

Total Contexts Total number of context entries.

LAN Connection Statistics 4-11
T0100-01, Revision B Release 5.4

Using LAN Connection Statistics

Negative Cache Entries Number of negative cache entries.
UDP Checksum Errors detected

by receiver

Number of UDP checksum errors detected by the receiver

(decompressor).
Synchronization Lost packets

received

Number of CONTEXT_STATE packets received to re-synchronize the

decompressor context.
Synchronization Lost packets

transmitted

Number of CONTEXT_ST ATE packets transmitted to re-synchronize the

compressor context.

Term Indicates...

4-12 LAN Connection Statistics

Using LAN Connection Statistics

LAN Connection Group St atist ics

Function When you select LAN Connection Group Statistics, the Vanguard CTP menu

prompts for:

• A Router Interface number corresponding to the LAN Connection Group

• Which Group to display, if multiple Groups exist on this Router Interface.
This is based on IP/IPX N etwork Addresses configured for the interface.

Once you provide this information, a statistics screen appears displaying a single line
for each next hop destination in the LAN Connection Group.

What You See In
This Screen

Figure 4-8 shows an example LAN Connection Group Statistics screen.

Figure 4-8.

LAN Connection Group Statisti cs Screen Example

Node: Address: Date: Time:
LAN Connection Group Statistics Page: 1 of 1

This LAN Connection Group is tied to Router Interface #5

There is 1 LAN Connection in this group

Next Hop Next Hop Remote Parallel
LAN Connection IP Address IPX Node Number Destination SVCs
================= ================ =============== ================ =======

1 Connected 134.33.200.4 15 80094 0/0

Press any key to continue ( ESC to exit ) ...

LAN Connection Statistics 4-13
T0100-01, Revision B Release 5.4

Using LAN Connection Statistics

Screen Terms The LAN Connection Group Statistics screen contains the following information:

Note

A LAN Connection Group can have more connections to next hop destinations
than fit in one CTP screen. Consistent with existing Vanguard functionality, you
can press the space bar to display multiple screens of this information. Screens
can be redisplayed using Ctrl R. You can also escape out of the statistics
command using ESC or Ctrl T.

Term Indicates...

LAN Connection The activity state of LAN Connections.

This can be Idle, Connected, or Calling.

Next Hop Address An IP address or IPX node number or

both.

Remote Destination An X.121 address or Frame Relay

Port/Station/DLCI.

Parallel SVCs Number of Parallel SVCs currently

configured/established.

Index

Index-1

Numerics

802.3 1-3

802.5 1-3

A

Addressing schemes

differences between M AC bridging and IP

routing 2-34

Appletalk 1-6

B

bandwidth management 1-5
Bandwidth on Demand

LANView 2-17

Bridge Link Number

specifying 3-12

Bridge links

referenced by Bridge Link Number 3-12
bridge routing 1-4
bridging 1-4
Bridging and routing

in a 6500 node 2-31
Bridging routers

definition 2-31

operations of 2-31

C

Codex Proprietary Encapsulation 2-7
compression 2-27

D

Data Link layer 2-31
Dial on Demand

Bridging traffic 2-20

E

encapsulation 2-6

Codex Proprietary 2-7

RFC 1294 2-8

RFC 887 2-9

RFC1356 2-10
Ethernet (802.3) 1-3
Examples of Applications

LANView for IP Over X.25 2-21

LANView for IPX 2-22

LANView using multiple encapsulation

types 2-24

LANView with Frame Relay 2-23

F

Flow Control

WAN Adaptor 2-5

G

Group LCON 2-14
Grouping LAN Connections 2-19

MTU Size 2-19

I

Interfaces

Ethernet 1-3
Token Ring 1-3

IP Applications Ware

protocol supported 1-2
IP Forwarder 2-2, 2-3
IP routing

features supported 1-5
IPX 1-6

L

LAN connection

using LCON 3-12
LAN Connection Group 2-17, 2-19

Booting 2-20

Mixed SVCs/PVCs 2-19
LAN Connection Parameters Me nu 3-10
LAN Connection Table

configuration 3-9

parameters 3-11
LAN forwarding

options 1-4
LAN protocols 2-4

function 2-4
LAN Topology 2-18
LANView 2-14, 2-17

advantages 2-18

Broadcast Information 2-19

combining X.25, Frame Relay, and dial

ports 2-18
comparison with WANView 2-14
configuration 2-20
configuration example 3-7
encapsulation types 2-18
example 2-15, 2-19
features 2-18
Frame Relay example 2-23
IP over X.25 example 2-21
IP RIP 2-19

Index-2

L (Continued)

LANView

IPX Example 2-22
IPX RIP 2-19
limitations 2-20
multiple incoming calls 2-18
multiple physical ports 2-18
parallel SVC 2-19
RIP Split Horizon 2-20
topology 2-17
using multiple encapsulation types

example 2-24

LCON 2-19

configuration guidelines 3-12
configuration matrix 3-12
definition 2-4
encapsulation 2-6
RTP/UDP/IP header compression 2-26
specifying 3-12
summary status 2-5

Limitations

LANView 2-20

M

model

Vanguard Router Model 2-1

O

OSPF 1-5

P

Parallel SVC 2-19

statistics 4-4
physical connectivity 1-3
Point-to-Point LCON 2-14
protocol priority 1-6

R

Request for Comments, see RFC
RFC 1-7
RFC 1294 2-8
RFC 887 2-9
RFC1356 2-10
RIP split horizon

LANView 2-20
Router Interface 2-17

LANView 2-14, 2-17

WANview 2-18

what is it 2-3
routing 1-4

R (Continued)

RTP/UDP/IP header compression 2-25

configuring 2-30
Context Identifier 2-29
voice 2-25

S

SLIM IP 1-6
SoTCP 1-6
Statistics

Detailed LAN Connection Stat isti cs Screen 4-3

Statistics menu

LAN Connection Summary Statistics 4-8

T

Token Ring (802.5) 1-3

U

UDP 2-25
User Datagram Protocol, see UDP

V

Vanguard Router Model

functional overview 2-2
logical functions 2-2

virtual circuits 2-3

W

WAN Adapter

definition 2-4
encapsulation 2-6
interconnection 2-4
statistics 2-5

WAN adapter

interconnections example 2-4

WAN Adaptor 2-2

Codex Proprietary Encapsulation 2-7
Flow control 2-5
RFC 1294 Multiprotocol Encapsulation 2-8

WAN adaptor

Call disconn ection 2-5

WAN Port 2-2, 2-13

port types supported 2-13

WANView 2-14

comparison with LANView 2-14
configuration example 3-5
configuration tips 3-6

WANview

Internal Data Connection s 2-15