1. Manuals
  2. Brands
  3. Motorola Manuals
  4. Network Router
  5. 110502USM001 - Vanguard 60 Router
  6. User manual

Motorola 110502USM001 - Vanguard 60 Router User Manual

User guide
Hide thumbs
Table of Contents

Advertisement

Quick Links

Motorola
P O W E R
RESET
S TAT U S
S E R V I C E
Vanguard Applications Ware
IP and LAN Feature Protocols
Vanguard Router Basics

Advertisement

Table of Contents
loading

Related Manuals for Motorola 110502USM001 - Vanguard 60 Router

Summary of Contents for Motorola 110502USM001 - Vanguard 60 Router

  • Page 1 Motorola P O W E R RESET S TAT U S S E R V I C E Vanguard Applications Ware IP and LAN Feature Protocols Vanguard Router Basics...
  • Page 2 Notice ©1999 Motorola, Inc. 20 Cabot Boulevard Mansfield, Massachusetts 02048 (508) 261-4000 All rights reserved Printed in U.S.A. Restricted Rights Notification for U.S. Government Users The software (including firmware) addressed in this manual is provided to the U.S. Government under agreement which grants the government the minimum “restricted rights”...
  • Page 3 Information and software in this document are proprietary to Motorola, Inc. (or its Suppliers) and without the express prior permission of an officer of Motorola, may not be copied, reproduced, disclosed to others, published, or used, in whole or in part, for any purpose other than that for which it is being made available.

  • Page 5: Table Of Contents

    Contents Vanguard Router Basics Chapter 1. Introduction to Vanguard IP and LAN Feature Protocols IP and LAN Protocol Support ..............Physical LAN Connectivity ..............LAN Forwarding Options ................ Network Layer - Routing ................. RFC ....................... Chapter 2. Vanguard Routing Model Functional Overview of the Vanguard Router Model ........
  • Page 6 Contents (continued) Chapter 4. LAN Connection Statistics Using LAN Connection Statistics ..............LAN Connection Statistics ............... LAN Connection Summary Statistics ............RTP/UDP/IP Compression Statistics ............LAN Connection Group Statistics ............4-12 Index...

  • Page 7: Chapter 1. Introduction To Vanguard Ip And Lan Feature Protocols

    Chapter 1 Introduction to Vanguard IP and LAN Feature Protocols Overview Introduction This chapter introduces the key features and protocols supported by the Vanguard IP Applications Ware. You will find a summary of the major Request for Comments (RFCs) supported by Vanguard IP Applications Ware. Introduction to Vanguard IP and LAN Feature Protocols...

  • Page 8: Ip And Lan Protocol Support

    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.

  • Page 9: Physical Lan Connectivity

    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 destinations.

  • Page 10: Lan Forwarding Options

    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.

  • Page 11: Network Layer - Routing

    (IP) Routing 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 •...
  • Page 12 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.

  • Page 13: Rfc

    Introduction The Vanguard IP Applications Ware adheres to global industry standards defined by IETF and IEEE. RFCs Supported by This table lists some of the RFCs supported by Vanguard IP Applications Ware. Vanguard Description User Datagram Protocol. J. Postel. Aug-28-1980. Internet Protocol.
  • Page 14 Description 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.
  • Page 15 Description 1534 Interoperation Between DHCP and BOOTP. R. Droms. October 1993. 1542 Clarifications and 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.

  • Page 17: Chapter 2. Vanguard Routing Model

    Chapter 2 Vanguard 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 This chapter provides information on how a Vanguard router interconnects two or Chapter...

  • Page 18: Functional Overview Of The Vanguard Router 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.

  • Page 19: Ip Forwarder

    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 “Using Bridging Routers to Connect LANs and Networks” section on page 2-31. Virtual Circuits The connection point of the IP forwarder to the LAN port is a virtual circuit called a Defined by Router Router Interface.

  • Page 20: Wan Adapter

    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 virtual circuit network and physical network implemented by the Motorola access devices. WAN Adaptor Figure 2-2 shows how the WAN Adapter is used to provide a LAN overlay network.
  • Page 21 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.

  • Page 22: Lcon Encapsulation

    WAN Adapter LCON Encapsulation Introduction The WAN Adapter encapsulates protocol-specific information in the data packet that is needed at the remote end of the connection. The following encapsulation methods are used: • Codex Proprietary encapsulation • RFC 1294 Multiprotocol encapsulation •...

  • Page 23: Codex Proprietary Encapsulation

    Trailer • 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.

  • Page 24: Rfc1294 Multiprotocol Encapsulation

    Note: The RFC1204 encapsulation to a Bypass FR station is used for interoperability with non-Motorola Type=0 routers. Codex Trailer Flags Flag Note: Motorola to Motorola links are recommended to use Codex encapsulation over Annex G-type Frame Relay stations. Figure 2-3. Packet Formats Vanguard Routing Model...

  • Page 25: Rfc877 Multiprotocol Encapsulation

    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.

  • Page 26: Rfc1356 Multiprotocol Encapsulation

    WAN Adapter RFC1356 Multiprotocol Encapsulation Overview RFC1356 and RFC877 encapsulation standards are virtually the 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. •...

  • Page 27: Lan Connection Encapsulation Examples

    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 Figure 2-4 depicts LAN traffic encapsulated by Codex Proprietary Encapsulation for using Codex transport over an X.25 network.
  • Page 28 WAN Adapter LCON over Frame This example depicts use of the maximum number of LAN Connections. At the Relay using RFC regional site is a Vanguard that needs to connect with up to 254 branch sites over 1490 Encapsulation Frame Relay. Frame Relay supports a 254 DLCI maximum per node and permanent SVCs only.

  • Page 29: Wan Port

    WAN Port WAN Port Types of WAN The Vanguard supports the following types of WAN virtual circuits: Virtual Circuits • Frame Relay DLCI (Bypass) • Annex G (X.25 over Frame Relay) (SVC) • X.25 (SVC) • MX25 (SVC) • XDLC (SVC) •...

  • Page 30: Wanview And Lanview

    WANView and LANView WANView and LANView 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 The following table describes WANView and LANView. LANView Overview Name Type...
  • Page 31 WANView and LANView FRI Port 1 Router Interfaces Node D 10.1.0.2 Ethernet Node A 10.1.0.1 FRI-1 LCON 1 10.2.0.2 FRI-1 Node B LCON 2 Router FRI-1 LCON 3 10.2.0.1 10.3.0.2 10.3.0.1 Node C Network WAN Adapter Router Note: FRI = Frame Relay Interface S = Station Note Different Router Interfaces (5, 6, and 7) are used.

  • Page 32: Wanview - Point To Point Lcon

    • less administrations - you are not required to configure the Next Hop address • better manageability - each WAN link has a unique IP subnetwork number WANView When interoperating with non-Motorola routers it may not be possible to use Interoperability WANView. For interoperability with non-Motorola routers use LANView.

  • Page 33: Lanview Of The Wan - Group Lcons

    LANView of the WAN - Group LCONs LANView of the WAN - Group LCONs What is a LANView The LANView feature provides flexible configuration of all virtual circuits over the of the WAN? 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.
  • Page 34 LANView of the WAN - Group LCONs 192.168.0.4 192.168.0.1 192.168.0.2 192.168.0.3 Vanguard-D Vanguard-A Vanguard-B Vanguard-C 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 •...
  • Page 35 LANView of the WAN - Group LCONs Example Figure 2-11 shows an example of adding router branch sites to an existing WAN link. Vanguard Regional Site 10.0.0.3 10.0.0.1 Net 11 Router FR/X.25 Vanguard 10.0.0.4 10.0.0.2 Router Net 12 Figure 2-11. Adding Branch Sites to an Existing WAN Link Grouping LAN A LAN Connection Group, or LCON Group, is a set of LCONs (SVCs/PVCs) that Connections...
  • Page 36 LANView of the WAN - Group LCONs Configuration You configure the LANView using the LAN Connection Table described on Considerations “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.

  • Page 37: Lanview Examples

    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 denotes a permanent SVC.
  • Page 38 LANView of the WAN - Group LCONs LANView for IPX Figure 2-13 is a similar application to the one shown in Figure 2-12 for IPX. over Frame Relay Node 10000000 has a LANView 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.
  • Page 39 LANView of the WAN - Group LCONs LANView over Figure 2-14 shows LANView in a Frame Relay Network. This is an example of full Frame Relay 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.
  • Page 40 LANView of the WAN - Group LCONs Vanguard Router Figure 2-15 is an example of LANView interoperating with a Cisco backbone. The using LANView key difference in this application is that even though RFC877 is used as the Interoperating with interoperability encapsulation between the routers and other RFC877-compliant Cisco Backbone routers, connectivity between the routers uses the CODEX encapsulation.

  • Page 41: Rtp/Udp/Ip Header Compression

    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.
  • Page 42 Packet Voice/Data 2 to 4 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...
  • Page 43 RTP/UDP/IP Header Compression Compression and If an RTP/UDP/IP packet is compressed before transmission of the WAN link, it must Decompression be decompressed at the receiving end. Each Vanguard supporting header compression, has a compressor and decompressor function. Vanguard Vanguard Compression Function Compression Function Compressor Decompressor...

  • Page 44: How Rtp/Udp/Ip Compression And Decompression Occurs

    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 When the Vanguard receive a packet, the first step is to determine if the packet can Packet can be be compressed.
  • Page 45 RTP/UDP/IP Header Compression Compressing the If the Vanguard determines that the packet can be compressed, it compresses the RTP/UDP/IP Header packet’s RTP/UDP/IP header as shown in Figure 2-19 and the table: Router A Router B 1st Packet Voice/Data Voice/Data RTP/UDP/IP Compressed RTP/UDP/ Packet Packet...
  • Page 46 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.

  • Page 47: Using Bridging Routers To Connect Lans And Networks

    There can be several different values for the Data Link (MAC) destination address used with the packet. The Data Link address may • Addressed to the Motorola internetworking node itself (case 1) • Addressed to some other node (case 2) •...
  • Page 48 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: •...
  • Page 49 Using Bridging Routers to Connect LANs and Networks Using Bridge and Figure 2-20 shows an example of a network where filtering is used. Router Filters Router Router LAN 1 Router Bridge, Router Bridge, Bridge, Bridge, Router Router Router LAN 3 LAN 4 LAN 2 Figure 2-20.
  • Page 50 Using Bridging Routers to Connect LANs and Networks Source Routing In a Source Routing Bridging environment, the bridge accesses the address and path Bridging to reach the destination address from response to the router discovery frame. Environment 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.

  • Page 51: Chapter 3. Configuring A Vanguard Router

    Chapter 3 Configuring a Vanguard 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. WAN Port Frame Relay X.25 MX25 LAN Port ISDN Ethernet...

  • Page 52: Configuration

    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 “Configure LAN Connections”...
  • Page 53 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 ->...
  • Page 54 Configuration 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 •...

  • Page 55: Example Wanview Configuration - Point-To-Point Lcons

    Configuration Example WANView Configuration - Point-to-Point LCONs 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 Figure 3-2 below illustrates the functional diagram of the Vanguard Router and the Configuration - important parameters that should be configured.
  • Page 56 Configuration Step (continued) Menu Node 100 Node 200 Node 300 Configure the Configure --> Configure Maximum Number of LAN Maximum Number of LAN Maximum Number of LAN LCON LAN Connections --> Connections: 32 (Default) Connections: 32 (Default) Connections: 32 (Default) Configure LAN Connection Parameter Configure -->...

  • Page 57: Example Lan View Configuration - Group Lcons

    Configuration Example LAN View Configuration - 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 Figure 3-3 below illustrates the functional diagram of the Vanguard Router and the Configuration - important parameters that should be configured.
  • Page 58 Configuration Step Menu Node 100 Node 200 Node 300 Configure the Node Configure --> Node Node Name: Node 100 Node Name: Node 200 Node Name: Node 300 Record Node Address: 100 Node Address: 200 Node Address: 300 Configure the WAN Configure -->...

  • Page 59: Configure Lan Connections

    Configure LAN Connections Configure LAN Connections Introduction The Configure LAN Connection menu provides access to the LAN Connection Table and LAN Connection Parameters records. Figure 3-4 shows the Configure LAN Connection Menu. Node: Address: Date: Time: Menu: Configure LAN Connections Path: LAN Connection Parameters LAN Connection Table...

  • Page 60: Lan Connection Parameters Menu

    Configure LAN Connections LAN Connection Parameters Menu Introduction Use the LAN Connection Parameters 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.

  • Page 61: Configuring Lan Connection Table

    Configure LAN Connections Configuring LAN Connection Table What You See in Figure 3-6 shows the LAN Connection Table Record. This Record Node: Address: Date: Time: Menu: Configure LAN Connections Path: LAN Connection Parameters LAN Connection Table Entry Number LAN Forwarder Type Bridge Link Number LAN Connection Type Router Interface Number...
  • Page 62 Configure LAN Connections Configuration When you configure the LAN Connection Table Record, use the following Guidelines 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.
  • Page 63 Configure LAN Connections LANView Configuration Matrix (continued) Parameter Displayed For ROUT LAN For BRID LAN For BROUT LAN Forwarder Type Forwarder Type Forwarder Type Autocall 0 to 8 alphanumeric 0 to 8 alphanumeric 0 to 8 alphanumeric Mnemonic Must be configured if Encapsulation Type of RFC877 Autocall Timeout...
  • Page 64 Configure LAN Connections LANView Configuration Matrix (continued) Parameter Displayed For ROUT LAN For BRID LAN For BROUT LAN Forwarder Type Forwarder Type Forwarder Type On Demand ENABLED, DISABLED Appears if Autocall Mnemonic configured and Encapsulation Type is CODEX Idle Timeout 0 to 65534 seconds Appears if Encapsulation Type is RFC877, or On...
  • Page 65 Configure LAN Connections LANView Configuration Matrix (continued) Parameter Displayed For ROUT LAN For BRID LAN For BROUT LAN Forwarder Type Forwarder Type Forwarder Type IP Precedence for Voice 0 to 7 0 to 7 0 to 7 Traffic Appears if Traffic Appears if Traffic Appears if Traffic Priority is configured as...

  • Page 66: Lan Connection Table Record Parameters

    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 configure the following parameters: Entry Number Range:...
  • Page 67 Configure LAN Connections *Bridge Link Number Range: 5 to n, where n = 36 to 250 Default: 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.
  • Page 68 Configure LAN Connections *Router Interface Number Range: 5 to n, where n = 36 to 254 Default: 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 the maximum number of IP or IPX interfaces set in the IP or IPX Parameters Menu.
  • Page 69 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 address of the Router Interface on the other end of this LAN Connection, which is the next hop on the path to the final destination.
  • Page 70 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: •...
  • Page 71 Configure LAN Connections Remote Connection ID Range: Default: 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 carried in the Call User Data (CUD) field of the call request packet when Encapsulation Type = CODEX.
  • Page 72 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 data bytes was transmitted without acknowledgment, the receipt of additional data for transmission triggers Parallel SVC use.
  • Page 73 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 circuit is established at system startup, or upon receiving data to pass. On Demand SVCs can support 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.
  • Page 74 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.
  • Page 75 Configure LAN Connections Protocol Priority Profiles Range 1 to 100 Default Description You can specify up to three protocol priority profiles. Enter the profiles separated by a comma (,) as shown: 1, 2 1 , 2 , 3 These profiles correspond to the entry numbers of the Protocol Priority Profile table configured under Configure Network Services.
  • Page 76 Configure LAN Connections IP Precedence for Voice Traffic Default Range 0 - Routine 1 - Priority 2 - Immediate 3 - Flash 4 - Flash Override 5- Critical/ECP 6 - Internetwork Control 7 - Network Control Description Specifies the IP Precedence for provided FAST PATH service for voice packets.
  • Page 77 Configure LAN Connections Compression Type Default 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.
  • Page 78 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. 3-28 Configuring a Vanguard Router...

  • Page 79: Chapter 4. Lan Connection Statistics

    Chapter 4 LAN Connection Statistics Overview Introduction This chapter describes how to monitor the performance and operation of the Vanguard using LAN Connection statistics. LAN Connection Statistics...

  • Page 80: Using 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 Figure 4-1 shows the LAN Connection Statistics menu. Select the appropriate This Screen number to view a particular screen.

  • Page 81: Lan Connection Statistics

    Using LAN Connection Statistics LAN Connection Statistics Function When you select LAN Connection Statistics, the Detailed LAN Connection Statistics screen provides three pages of detailed information about all current LAN Connections and LAN Connection Groups. What You See in An example of a Detailed LAN Connection Statistics screen is shown in Figures 4-2, This Screen 4-3, and 4-4.
  • Page 82 Using LAN Connection Statistics 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) --------------------------------------------------------------------...
  • Page 83 Using LAN Connection Statistics Screen Terms The Detailed LAN Connection Statistics screen provides the following information: Term Indicates... Call This field provides information about the following: Summary • Connection Type: Specifies whether the connection is point-to- point (PT_to_PT) or GROUP, and whether an SVC or a PVC is established.
  • Page 84 Using LAN Connection Statistics Term Indicates... Packet • Data: Summary of each packet sent on the WAN and received Summary from the WAN bridge link. • Call Request: Specifies the total number of Call Request Packets sent on the WAN and received from the WAN. •...
  • Page 85 Using LAN Connection Statistics Term Indicates... Tx Bytes Total number of transmit bytes outstanding. Outstand- Rx Pck Number of packets received. Count Avg Rx Average receive packet size. Pck Size LAN Connection Statistics T0100-01, Revision B Release 5.4...

  • Page 86: Lan Connection Summary Statistics

    Using LAN Connection Statistics LAN Connection Summary Statistics Function The LAN Connection Summary Statistics screen provides an overall picture of the LANView indicating which connections are currently active. What You See in Figure 4-5 shows an example of the LAN Connection Summary Statistics screen. This Screen Node: Address:...

  • Page 87: Rtp/Udp/Ip Compression Statistics

    Using LAN Connection Statistics RTP/UDP/IP Compression Statistics Function The RTP/UDP/IP Compression statistics provide detailed information on compression applied to packets received or transmitted on a particular LCON. When you access the RTP/UDP/IP Compression statistics menu you will be prompted to enter the LCON number.
  • Page 88 Using LAN Connection Statistics 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 Transmit 84.1.34.2 3.3.3.3 5006 6005 Receive 3.3.3.3 5.5.5.5 6006 6000 Press any key to continue ( ESC to exit ) ... Figure 4-7.
  • Page 89 Using LAN Connection Statistics Term Indicates... Negative Cache Entries Number of negative cache entries. UDP Checksum Errors detected Number of UDP checksum errors detected by the receiver by receiver (decompressor). Synchronization Lost packets Number of CONTEXT_STATE packets received to re-synchronize the received decompressor context.

  • Page 90: Lan Connection Group Statistics

    Using LAN Connection Statistics LAN Connection Group Statistics 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 Network Addresses configured for the interface.
  • Page 91 Using LAN Connection Statistics Screen Terms The LAN Connection Group Statistics screen contains the following information: 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.

  • Page 93: Index

    Index Numerics 802.3 Flow Control 802.5 WAN Adaptor Addressing schemes Group LCON 2-14 differences between MAC bridging and IP Grouping LAN Connections 2-19 routing 2-34 MTU Size 2-19 Appletalk Interfaces bandwidth management Ethernet Bandwidth on Demand Token Ring LANView 2-17 IP Applications Ware Bridge Link Number protocol supported...
  • Page 94 L (Continued) R (Continued) LANView RTP/UDP/IP header compression 2-25 IPX Example 2-22 configuring 2-30 IPX RIP 2-19 Context Identifier 2-29 limitations 2-20 voice 2-25 multiple incoming calls 2-18 multiple physical ports 2-18 parallel SVC 2-19 SLIM IP RIP Split Horizon 2-20 SoTCP topology...

This manual is also suitable for:

Vanguard 100Vanguard 200Vanguard 6520Vanguard 6560

Table of Contents