Vanguard Applications Ware Basic Protocols Point-to-Point ... · Point to Point Protocol (PPP) ... Challenge Handshake Authentication Protocol (CHAP) and Password Authentication Protocol

Vanguard Applications WareBasic Protocols

Point-to-Point Protocol

Notice

©2008 Vanguard Networks.25 Forbes Boulevard Foxboro, Massachusetts 02035 Phone: (508) 964-6200Fax: 508-543-0237 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” in the software, as defined in the Federal Acquisition Regulation (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 LegendUse, 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-7013.

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

NoticeNotwithstanding 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, reproduction, and disclosure are as set forth in FAR 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 Vanguard Managed Solutions (or its Suppliers) and without the express prior permission of an officer of Vanguard Managed Solutions, 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. Use of software described in this document is subject to the terms and conditions of the Vanguard Managed Solutions Software License Agreement.

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

Part No. T0106-08, Rev IPublication Code TKFirst Printing November 1998Manual is current for Release 7.2 of Vanguard Applications Ware.

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

Contents

v

Point to Point Protocol (PPP) ....................................................................... 3Components .............................................................................................. 5Features .................................................................................................... 7

Typical PPP Over ISDN Application ........................................................... 10Typical PPP Over Serial Port Application .................................................... 11Typical PPP Over Ethernet (PPPoE) Application ........................................ 12

PPPoE Configuration Example ................................................................ 19Typical Multilink PPP Over Frame Relay (MLPoFR) and ATM (MLPoA)

Applications ............................................................................................. 22Typical PPP Over ATM and PPPoE over DSL Application ......................... 24Multilink PPP Over Frame Relay (MLPoFR) Application .......................... 25

MLPoFR Configuration Example ............................................................ 27Multilink PPP Over ATM (MLPoA) Application ........................................ 31PPPoA and PPPoEoA over DSL (G.SHDSL) .............................................. 33

PPPoEoA Configuration Example ........................................................... 35G.SHDSL Support .................................................................................... 37

Multilink Point to Point QoS (MLPPP QoS) ............................................... 38Multiclass and Voice Priority Overview............................................... 40Traffic Classification............................................................................. 44Multiclass Negotiation.......................................................................... 49Packet Segmentation/Reassembly ........................................................ 51Packet Queuing - Prioritization and Interleaving ................................. 54Flow Control ......................................................................................... 54Typical MLP QoS Application ............................................................. 55

Link Methods ................................................................................................ 57Single Link PPP ....................................................................................... 58MultiLink PPP .......................................................................................... 60

Multilink PPP (MLPPP, MLP, MLPPPoX) .......................................... 62Authentication Methods ............................................................................... 64

Single Link PPP ....................................................................................... 65MultiLink PPP .......................................................................................... 66

Configuration Examples ............................................................................... 69Single Direction Authentication Using CHAP ........................................ 70Bidirectional Authentication Using CHAP .............................................. 72Bridging .................................................................................................... 74Proprietary Compression .......................................................................... 76Synchronous Links in MultiLink PPP and IP over ISDN ........................ 78Asynchronous PPP, Windows 95 and Frame Relay ................................. 80Asynchronous PPP Using AT Dialer ........................................................ 81MultiLink PPP Over BRI ......................................................................... 85MultiLink PPP Over PRI ......................................................................... 87

Cascading Configuration .............................................................................. 89Configuring Point-to Point Protocol over Ethernet (PPPoE) Connections .. 93Configuring PPP Connections ...................................................................... 96

PPP Port Record ....................................................................................... 97PPP Parameters Record ............................................................................ 116PPP Profile Record ................................................................................... 118

PPP SNMP .................................................................................................... 132Statistics ........................................................................................................ 136

vi

Contents (continued)

Stacking State Values ............................................................................... 137Port Statistics ............................................................................................ 138PPP Connection Statistics ........................................................................ 146PPP QoS Connection Statistics ................................................................ 151Link Statistics ........................................................................................... 155PPP over Ethernet (PPPoE) Statistics ...................................................... 157

Diagnostics ................................................................................................... 161PPP over Ethernet (PPPoE) Diagnostics .................................................. 161

Point to Point Protocol 1

Point to Point Protocol

Overview

Introduction This manual describes how to configure and use Point to Point Protocol (PPP) and Multilink Point to Point Protocol (MLPPP) on Vanguard products.

Alarms & Reports Refer to the Applications Ware Alarms and Reports Manual (Part Number T0005) for details on alarms generated by a port configured for PPP and MLPPP operation.

In This Manual Topic See Page

Point to Point Protocol (PPP) ....................................................................... 3Components .............................................................................................. 5Features .................................................................................................... 7

Typical PPP Over ISDN Application ........................................................... 10Typical PPP Over Serial Port Application .................................................... 11Typical PPP Over Ethernet (PPPoE) Application ........................................ 12

PPPoE Configuration Example ................................................................ 19Typical Multilink PPP Over Frame Relay (MLPoFR) and ATM (MLPoA)

Applications ............................................................................................. 22Typical PPP Over ATM and PPPoE over DSL Application ......................... 24Multilink PPP Over Frame Relay (MLPoFR) Application .......................... 25

MLPoFR Configuration Example ............................................................ 27Multilink PPP Over ATM (MLPoA) Application ........................................ 31PPPoA and PPPoEoA over DSL (G.SHDSL) .............................................. 33

PPPoEoA Configuration Example ........................................................... 35G.SHDSL Support .................................................................................... 37

Multilink Point to Point QoS (MLPPP QoS) ............................................... 38Multiclass and Voice Priority Overview............................................... 40Traffic Classification............................................................................. 44Multiclass Negotiation.......................................................................... 49Packet Segmentation/Reassembly ........................................................ 51Packet Queuing - Prioritization and Interleaving ................................. 54Flow Control ......................................................................................... 54Typical MLP QoS Application ............................................................. 55

Link Methods ................................................................................................ 57Single Link PPP ....................................................................................... 58MultiLink PPP .......................................................................................... 60

Multilink PPP (MLPPP, MLP, MLPPPoX) .......................................... 62Authentication Methods ............................................................................... 64

Single Link PPP ....................................................................................... 65MultiLink PPP .......................................................................................... 66

Configuration Examples ............................................................................... 69Single Direction Authentication Using CHAP ........................................ 70Bidirectional Authentication Using CHAP .............................................. 72Bridging .................................................................................................... 74Proprietary Compression .......................................................................... 76Synchronous Links in MultiLink PPP and IP over ISDN ........................ 78

2 Point to Point Protocol

Asynchronous PPP, Windows 95 and Frame Relay ................................. 80Asynchronous PPP Using AT Dialer ........................................................ 81MultiLink PPP Over BRI ......................................................................... 85MultiLink PPP Over PRI ......................................................................... 87

Cascading Configuration .............................................................................. 89Configuring Point-to Point Protocol over Ethernet (PPPoE) Connections .. 93Configuring PPP Connections ...................................................................... 96

PPP Port Record ....................................................................................... 97PPP Parameters Record ............................................................................ 116PPP Profile Record ................................................................................... 118

PPP SNMP .................................................................................................... 132Statistics ........................................................................................................ 136

Stacking State Values ............................................................................... 137Port Statistics ............................................................................................ 138PPP Connection Statistics ........................................................................ 146PPP QoS Connection Statistics ................................................................ 151Link Statistics ........................................................................................... 155PPP over Ethernet (PPPoE) Statistics ...................................................... 157

Diagnostics ................................................................................................... 161PPP over Ethernet (PPPoE) Diagnostics .................................................. 161


T0106-08, Revision I Release 7.2

Point to Point Protocol (PPP)


What Is It? The Point to Point Protocol (PPP) is a WAN protocol that transports data over point to point links. PPP has three components:

• Link Control Protocol (LCP) used to establish, configure, and test a PPP link• Network Control Protocols (NCPs) for establishing and configuring different

network-layer protocols• Authentication method used to validate the remote connection

What Application Is It Suitable For?

PPP is suitable for low error rate links such as those provided by ISDN.PPP is simpler and more efficient than connection-oriented protocols like X.25 (which supports error detection and retransmission) because it does not have mechanisms to compensate for transmission errors. Like Frame Relay, it can detect link-level errors but does not support link-level retransmission. PPP’s simplicity uses fewer CPU resources and bandwidth to make sure the data arrives intact. It simply sends data through. PPP is suitable for carrying connectionless traffic (for example, LAN-type traffic such as IP) that provides its own transport mechanism to recover from packet corruption and loss. PPP is designed to handle only one physical link at at time.

What Platforms Support PPP?

These Vanguard products support PPP:

Platform Basic PPP Support

MultiLink PPP

Bandwidth on Demand

Basic Rate

Interface

Primary Rate

Interface

Channelized T1/E1

Interface34xx X X X X X X68xx X X X X X X73xx X X X X X X

Vanguard Sunset Products6560 X X X X X X6520 X X X X6500PLUS X XVanguard 6400 X X X X X XVanguard 320 X X X XVanguard 34x X X X XVanguard 312 X X X XVanguard 311 X X X XVanguard 305 X X X XVanguard 300 X X X X* Basic PPP Support includes: Serial SYNC/ASYNC LAN interfaces, IP/IPX Routing, and PAP/CHAP Authentication.



Vanguard 200 X XVanguard 100 X650 X

Platform (continued)

Basic PPP Support

MultiLink PPP

Bandwidth on Demand

Basic Rate

Interface

Primary Rate

Interface

Channelized T1/E1

Interface

* Basic PPP Support includes: Serial SYNC/ASYNC LAN interfaces, IP/IPX Routing, and PAP/CHAP Authentication.




Components

Introduction Each component in the PPP protocol plays a part in how a message is sent and received. This section summarizes the functions of the Link Control Protocol, the Network Control Protocols and Authentication methods as they are supported on Vanguard nodes.

Link Control Protocol

Link Control Protocol (LCP) handles encapsulation options, packet size, and configuration errors. LCP only manages the part of a PPP link that is independent of the network layer.LCP configures a link by exchanging Configure packets. Once both sides of the connection have acknowledged Configure packets, the connection enters an Open state, so the (Single or Multi-) link connection can be established. The network protocol layers and authentication are configured at the connection level.PPP LCP Echo SuppressionOnce PPP negotiates the link and session parameters with another node, an Echo Request message is used to detect the presence of that node. In some network configurations, this may result in lost buffers. To suppress these messages, you must enter this Customer Software Key (CSK): 824MKLAKE333ZL8P7554.

NoteRefer to the Vanguard Configuration Basics Manual, Part Number T0113 for instructions on entering a CSK.

Disabling the Echo Request messages effectively prevents backing up a permanent connection. Switched links (ISDN or DIMO) can be backed-up while the LCP Echo Request feature is disabled.The CSK Statistics screen identifies the status of this feature that is, PPP echo request Disabled.

Network Control Protocols

The Network Control Protocols (NCPs) handle specific layer protocols such as IP and IPX. Vanguard products support the following NCPs:

• IPCP - Internet Protocol Control Protocol• IPXCP - Internet Packet Exchange Control Protocol• CCP - Compression Control Protocol• BCP - Bridging Control Protocol

The routines that establish and maintain connections with NCPs are called state machines. (The phrase “state machines” is used routinely in statistics descriptions.) NCPs share a common control protocol and go through the same states as they make connections. When you view statistics for PPP, statistics that report on IPCP, IPXCP, CCP, and BCP options are reporting on the states of the connection since NCPs all operate at the connection level (as opposed to the link).



Authentication Methods

When the LCP configures a link, it can, if you want it to, go through a security routine called authentication. You must configure a port or profile to perform authentication if you want this option to be in effect. Vanguard products support both Challenge Handshake Authentication Protocol (CHAP) and Password Authentication Protocol (PAP) as defined in RFC1334. Each of these authentication methods have different advantages. The advantages of each method are as follows:

• PAP provides a simple authentication mechanism when establishing a PPP link. The PAP Password is the same for all remote nodes accessed.

• CHAP is a more secure method of authenticating. This implementation of CHAP allows a Secret to be unique for each location with which a node connects.




Features

Introduction Vanguard products offer the following functionality.

Auto Dialing A PPP connection can be established without the presence of network traffic. This feature lets you specify the number and the rate of call attempts.

AT Dialer AT Dialer allows asynchronous PPP connections to dial out over a modem using AT commands. The dial numbers are configured in the node allowing the modem to make both incoming and outgoing calls. This feature is supported on all platforms and modems with similar properties as the 3460 Fast’R Modem or standard Hayes compatible.For information on how configure your port for AT Dialer, see the “Asynchronous PPP Using AT Dialer” section on page 81.

Bandwidth on Demand

Bandwidth on Demand allows several router and bridge interfaces to shares PPP ports. The association of a PPP port and a router interface is established automatically on demand and is disconnected automatically when the demand for bandwidth on that interface drops. When PPP detects the presence of network traffic, Bandwidth on Demand allows it to automatically establish a connection to a remote node through a PPP link. Links can also be added to a connection based on the utilization of the current member links. If the current member links in a bundle receive throughput above their configured threshold, Bandwidth on Demand adds a link. The use of multiple PPP links complies with RFC1990. Bandwidth on Demand is applicable for PPP links operating over switched links such as ISDN.Parameters that enable Bandwidth on Demand should be configured so only one of the peers in a connection manages the link. Located in the PPP Profile Record, these parameters are:

• Add Bandwidth Threshold • Add Bandwidth Wait Time• Remove Bandwidth Wait Time• Idle Disconnect

Bridging The Bridging Control Protocol (BCP) configures the PPP link for bridging traffic. The current implementation only supports one BCP option, Mac Support. (This option is compatible with the Cisco and Ascend bridging implementations.) Mac Support advises the peer the types of MAC layers supported. The transmitter discards frames that are unsupported by the peer and thus makes more efficient use of the PPP bandwidth. The BCP feature supports Ethernet (IEEE 802.3). A port running BCP transmits Ethernet frames from the peer.For information on how configure your port for BCP, see the“Bridging” section on page 74.



Data Compression The Compression Control Protocol parameter on the PPP Port record enables or disables Proprietary Data Compression when running PPP. Data Compression offers the following functionality:

• Compresses data in a ratio of 2:1• Decreases the application’s need for bandwidth• Reduces transmission times

Make sure that compression is configured consistently in both the Network Services Feature table and the PPP Port record configuration as follows:

Parameter ValuesCompression OFF ONCompression Control Protocol (in PPP Port Configuration)

NONE PROP

Data Compression Level (in Network Services Feature Table)

DISABLED FORCE ON

MultiLink BRI/PRI The Vanguard 3400, 6800, and 7300 can run MultiLink PPP links over BRI (2 B channel) or PRI (23 B channel) ISDN lines. For examples of how to configure Vanguard devices for MultiLink BRI and PRI, see “MultiLink PPP Over BRI” section on page 85 and “MultiLink PPP Over PRI” section on page 87 respectively.For more information on BRI and PRI specific records, see the Vanguard ISDN Protocol Manual (Part No. T0103-06) in the Multi-Service Feature Protocols Manual (Part No. T0103).

Powerup Dialing Powerup Dialing provides the same functionality as the autodialer. However, it attempts to establish the PPP connection with an infinite number of attempts every 30 seconds. This feature is available for Single Link PPP only. It is enabled when the PPP Profile parameter Idle Disconnect is set to 0.

Remote Access to Multiple Locations

This feature allows switched ISDN B channels to connect dynamically with multiple remote sites. Based on the destination of network traffic, a connection can be dynamically created to any of four locations defined by the PPP Profiles. With an ISDN BRI interface, two remote locations can be accessed simultaneously or any of the four locations can be accessed using both B channels.The profiles allow the connection to be customized between two sites. For example:

• a connection from node A to node B could be used for IP traffic and be authenticated using CHAP

• a connection from node A to node C could be used for IP traffic and be authenticated using PAP

Bandwidth on Demand and reserved bandwidth are controlled independently for each connection.




Reserved Bandwidth

When you must guarantee connectivity to remote sites, a dedicated link can be reserved for exclusive use by the profile’s associated connection.By default, PPP links operating over ISDN are members of a pool of PPP links that are equally available to all PPP connections.Non-switched links must be configured to operate as single link PPP or they must be configured as a dedicated link in a PPP profile record.


Typical PPP Over ISDN Application

Typical PPP Over ISDN Application

How It Works In Figure 1, PPP support on a Vanguard router allows a remote office to connect to other ISDN routers, providing a solution for the telecommuter who dynamically connects to multiple central sites.In addition, Figure 1 demonstrates a situation in which Bandwidth on Demand could be employed. Based on the destination of network traffic, a connection can be dynamically created to any of four locations defined by the PPP Profiles.

Example Figure 1 shows an implementation of MultiLink PPP over ISDN. Two 64 Kbps ISDN B channels are used simultaneously to connect to a single location for a total of 128 Kbps of bandwidth. Furthermore, connectivity to two independent locations is provided, each with 64 Kbps of bandwidth.

PC

ISDNEthernet MPVanguard Vanguard

Router3rd Party

ISP

Vanguard

PC

Figure 1. Vanguard Router Connectivity with ISDN Routers



Typical PPP Over Serial Port Application

Typical PPP Over Serial Port Application

How It Works Figure 2 shows a Vanguard in an application that provides low cost access for companies communicating over a Public Switched Telephone Network (PSTN). It uses an economical network such as Frame Relay or X.25 for the long distance connection to an IP or IPX network.The Vanguard product line support PPP over asynchronous or synchronous lines. The Vanguard’s EIA interface supports either a modem or direct connection.

Example Figure 2 shows a Vanguard providing a single link, dedicated PPP connection to a PSTN network:

PC

X.25or

Frame Relay

Modem

PC

PC

PSTN

Vanguard

PPP

Modem

Modem

Modem

Modem

Figure 2. PPP Over Asynchronous or Synchronous BOP


Typical PPP Over Ethernet (PPPoE) Application


Introduction Many small offices and home users need to access the Internet or a corporate network. Internet Service Providers (ISPs) are using Point-to-Point Protocol over Ethernet (PPPoE) to provide residential Digital Subscriber Line (DSL) broadband Internet access. DSL is a broadband technology that uses existing twisted-pair telephone lines to transport high-bandwidth data. The term xDSL encompasses a number of similar (and competing) forms of DSL. A typical xDSL network is shown in Figure 3. The customer premises includes a Vanguard router with two Ethernet interfaces, a number of hosts (PCs) connected over the LAN to one Vanguard interface and a xDSL modem connected to another one. The modem acts as a MAC layer bridge, relaying traffic to a xDSL Access Multiplexer (DSLAM) in a phone company's central office over an ATM permanent virtual circuit (PVC). One PVC can support an arbitrary number of PPP sessions. From the central office to an Internet Service Provider or an enterprise facility, the connection may continue to run over ATM, or it may be converted to frame relay or a leased line TDM protocol for slower-speed links. No configuration of the xDSL modem is required at the customer site.

Vanguard DSL ModemDSLAM

CentralOffice

DataNetwork

ServiceProvider

RFC1483/1490 PVC

Internet

PPPoE Session

AccessConcentrator

CorporateGateway

Ethernet Ethernet

CustomerPremise

Figure 3. Typical PPPoE Application

ISPs use Point-to-Point Protocol over Ethernet (PPPoE) to allow multiple hosts (PCs) to share a single "always on" xDSL line. PPPoE provides the ability to connect a network of hosts over a DSL modem to a remote Access Concentrator (AC). Two widely accepted standards are used, Ethernet and PPP. Minimum configuration is required at customer premises and PPPoE maintains the existing dial-up operational model to users and ISPs. PPPoE integrates into the current networking infrastructure with minimal changes to existing equipment and operational systems.




Figure 3 shows a typical application where the Vanguard is the PPPoE client. PPPoE software is not required on the hosts (PCs). Multiple hosts connected to the Vanguard Ethernet interface are able to connect, across a PPPoE session, to a PPPoE server running on ISPs AC. The Ethernet simply carries PPP messages between the client and the server. Normally, a single IP address is assigned to the Vanguard node. In the case of multiple hosts the NAT feature is configured to share this single public address among internal users on the customer LAN. Access control, billing and type of service can be done on a per-session basis.

NotePoint-to-Point over Ethernet (PPPoE) is available with Release 6.2 and greater on the Vanguard 3400, 6800, and 7300 Series platforms and on specific sunset platforms (320, 34x, 6435, 6455). Release 6.4 and greater software supports PPPoEoA over DSL. Reference “Typical PPP Over ATM and PPPoE over DSL Application” sec-tion on page 24 for more information on connection options.

NoteInteroperability with industry standard DSL modems and servers are supported.

Benefits The importance of PPP over Ethernet is its ability to offer high speed access, and ease of use for consumers. PPPoE is seamless to integrate into the existing infrastructure for carriers and Internet Service Providers (ISPs). PPPoE may speed the widespread adoption of high-speed access services. PPP over Ethernet provides a major advantage for service providers by maximizing integration with, and minimizing disruption of, service providers' existing dial network infrastructures.Through tight integration with existing back office automation tools that ISPs have developed for dial customers, PPPoE enables rapid service deployment and cost savings. From authentication, accounting and secure access to configuration management, PPPoE supports a broad range of existing applications and services.

Protocol Stages PPPoE has two distinct stages: • Discovery • PPP Session

PPPoE is a client-initiated connection. When a host wishes to start a PPPoE session, it must first perform Discovery to identify the Ethernet MAC address of the peer and establish a PPPoE Session ID. While PPP defines a peer-to-peer relationship, Discovery is inherently a client-server relationship. In the Discovery process, the client discovers an Access Concentrator (the server). Based on the network topology, there may be more than one Access Concentrator that the Host can communicate with. The Discovery stage allows the host to discover all Access Concentrators and then select one. When Discovery completes successfully, both the host and the selected Access Concentrator have the information they use to build their point-to-point connection over Ethernet. Once the PPP stage begins, PPP data is sent like any other PPP encapsulation.Discovery session has four steps:1) The client initiates a session by broadcasting a PPPoE Active Discovery

Initiation (PADI) packet.2) All Access Concentrators which received a PADI packet and can serve it, reply

by sending a PPPoE Active Discovery Offer (PADO) packet to the client.



3) The client selects one Access Concentrator among the received PADO packets and sends a single PPPoE Active Discovery Request (PADR) packet to it. The choice is based on the AC name or on an offered service.

4) The Access Concentrator responds by sending PPPoE Active Discovery Session-confirmation (PADS) packet with a Session Identification that along with AC MAC address uniquely identifies this session.

Upon receiving a PADS packet from the selected AC server the client starts a normal PPP session. PPP authenticates the user, dynamically assigns an IP address and negotiates various other connectivity parameters.

PADI (Service-Name,...)

PADO (AC-Name, Service-Name,.....)

PADR (Service-Name,....)

PADS (Service-Name,....)

PADT ( )

PPPoE ActiveDiscovery Terminate(PADT) packet may

be sent anytime aftera session is

established by eitherthe client or AC

PPPoE ServerPPPoE Client

PADT ( )

PPP Packets

PPP Packets Regular PPPTraffic

Discovery Packets

DiscoveyStage

PPPStage

SessionTermination

Figure 4. Discovery Stage

Ver Type Session ID Length

Ethernet Payload

Stage Code

Discovery Stage

PADI - 0x09PADO - 0x07PADR - 0x19PADS - 0x65

PPP Session Stage 0x00

Ver = 0x1

Type = 0x1

Figure 5. PPP Session Stage




PPP Stack and PPP Session

One PPP stack and one PPP session are supported per Ethernet port. This session can be used to access one Access Concentrator (AC) Internet Service Provider by many hosts simultaneously. During the Discovery phase many ISPs can be accessed across many DSL modems but only one can be selected. Authentication and billing is provided per session.The Client PPPoE port is seen by the PPP stack as a regular port providing point-to- point connection. The peer termination point is provided by PPPoE server on the Access Concentrator.

PPPoE Features PPPoE implementation provides the following features:• Implementation of PPPoE in accordance with RFC 2516• Implementation of PPPoE in accordance with RFC 1483 (LLC/SNAP)• Interoperability with industry standard DSL modems and Access

Concentrator (AC) servers• Access to multiple DSL modems and selection one among many destinations

(ISPs) during the Discovery stage• Access to Internet and corporate networks for multiple users over a single

PPPoE session• On demand or auto connect PPPoE session setup• Link status monitoring and session reestablishment in case of connection loss

Functionality The PPPoE feature adds PPP connectivity over an Ethernet port to a Vanguard node and provides access to many destinations over a DSL modem. In addition to a PPPoE software component, Ethernet and PPP stacks shall be available in a node. For a typical application, where multiple users access PPPoE over a LAN, two Ethernet ports are required. To configure PPPoE, the PPP configuration parameter "Line Interface" is set to Ethernet. Regular PPP configuration shall then take place. Only the relevant parameters are shown. Some of parameters are set internally to appropriate values. For instance, MLPP is not applicable, so PPP mode is set internally to Singlelink. Upon completion of PPP configuration, four additional parameters, unique for PPPoE, shall be configured. During the Discovery stage, the Access Concentrator (AC) selection is based on pre-configured AC and service names. These names have to match corresponding tags in packets sent by the AC. If any of the configured names are blank, any available AC or service is accepted. For instance, if the AC name is blank the Access Concentrator, which sends the first reply, is accepted.No changes are required for Ethernet port configuration. PPPoE status, statistics and alarm messages are included in addition to existing PPP ones. Events like PPPoE session establishment, termination as well as error messages from the server and client are shown as alarms occur.

Ethernet Port Router LCON PPPoE Ethernet Port DSL Modem

LAN

Vanguard



Figure 6. Involved Protocol Stacks

NoteIP Maximum Transmission Unit (MTU) shall be no more than 1492 bytes. The Maximum-Receive-Unit (MRU) option must not be negotiated to a larger size than 1492 octets.

PPPoE Protocol Stack (G.SHDSL)

When a DSL modem is embedded in the router, an Ethernet connection is not required. The router encapsulates PPPoE frames. For MAC frames the de-facto encapsulation method is RFC1483 LLC/SNAP for Bridged PDU's.

IP

Ethernet DSL

ATM

Sonet/SDHSonet/SDH

ATM

Router With InternalDSL Modem

Central Office ATM NetworkIP

PPP

LLC/SNAP

AAL5

ATM

DSL

PPPoE

IP

PPP

LLC/SNAP

AAL5

ATM

DSL

PPPoE

Service Provider

Figure 7. PPPoE Protocol Stack

Limitations A PPPoE Client must not request any of the following options, and must reject a request for such an option:

• Field Check Sequence (FCS) Alternatives• Address-and-Control-Field-Compression (ACFC)• Asynchronous-Control-Character-Map (ACCM)




PPPoE Session Start

There are two options to start a PPPoE session: • Auto Connect - Permanent connection which enables session establishment

automatically after the PPP port boot.• On Demand - Establishes a PPP session when a host has data to transfer.

A session is terminated after the predetermined link idle period.When the Auto Connect option is enabled a permanent PPPoE session is established automatically after the PPP port boot. If this option is disabled a session is set up, on demand, when any host starts some traffic. Such a session is terminated after a predetermined time period without any outbound traffic. The time period is a configurable parameter. Both options are transparent for users. If an initial Discovery stage fails, unlimited attempts to establish a connection are made.

NoteDigital Subscriber Line (DSL) is an "always on" service.

Access Concentrator (AC) Response Time-out

During the Discovery stage, after a PPPoE client has sent a PADI or PADR packet, the client waits a specified amount of time for an AC response. If the reply packet has not been received within this time period, the time-out interval is doubled and a PADI or PADR packet is sent again. This procedure repeats until the maximum time interval are reached then PADI packets are sent periodically unlimited times.

Minimum and Maximum Values for AC Response Time-out

When a Vanguard does not receive a PADO or PADS packet within a specified amount of time, it resends its PADI or PADR packet and doubles the waiting period. This is repeated until expected packet is received or the predetermined maximum waiting period is reached. An alarm message is generated indicating that the Discovery session could not be completed and in either case PADI packets are resent periodically unlimited times, until the PPPoE session is successfully established.

AC Error Types In any packet (received by the AC) a tag can exist indicating some error condition. Three error types are specified:

Error Type IndicationService-Name-Error Requested Service-Name cannot be honored.AC-System-Error The Access Concentrator (AC) experienced some

error in performing the client request.Generic-Error Unrecoverable error occurred.

When any error tags are received, an alarm message is generated indicating the general type of the problem. When the length of the data section of the tag is non zero and the first octet is a printable character, the string is printed as part of the alarm message, assuming that the Access Concentrator (AC) provided information on the nature of the error. The length of the string shall be the value specified in the tag but no more than 32 octets.



Session Termination Alarm

When a PPPoE session is established, it may be terminated any time due to link problems or by sending PADT packets either by client or AC. Session termination is indicated by an alarm message.

Discovery Success When the Discovery stage is successfully completed, before the PPP Session Stage starts, an alarm message is generated with information about success.

Connection Loss Detection

During the PPP Session stage, PPPoE client is able to detect a connection loss with the server. Vanguard PPP implementation already supports detection of link down condition by sending periodically LCP Echo Request packets to the server. The Echo Request packets are sent out after each Echo Time-out period (three seconds) and server sends back some response (data, Echo-Reply or its own Echo Request packet) within this time interval. If no response has been received (five consecutive Echo Time-out periods) the PPPoE session is considered disconnected. This mechanism is used only during the PPP stage. When PPPoE client in PPP stage receives an Echo Request packet from the server, it responds immediately by sending an Echo-Reply packet.

Echo-Reply In the PPP Session stage, when Echo Request packets are received from the server, the PPPoE client responds immediately by sending an Echo-Reply packet.

Session Reestablishment

In the PPP Stage, when a session is terminated due to any other reason than Idle Disconnect, the PPPoE client shall immediately starts a new session if Auto Connect is enabled or it is disabled and there is at least one packet ready to be transmitted. If the session cannot be setup, due to any reason, PADI packets shall be sent out periodically following the procedure specified in the AC Response Time-out section.




PPPoE Configuration Example

PPPoE Configuration with NAT Translation (Dynamic)

Figure 8 shows a PPPoE configuration example:

Host 3

V340VANGUARD3 4

Host 1

Host 2

DSL Modem

ATMATM Temination

Internet

Bell Canada

PPPIP

PPPoE

10.10.10.x255.255.255.0

.1

.100

.101

.102

P8 P5

V6800

Figure 8. PPPoE Configuration

NoteUser ID’s and passwords are provided by the Internet Service Provider (ISP).Example: User ID: [email protected], Password: vanguardms

Node Record Node Name: vang6800Node Address: 6800Node Number: 6800Expanded Node Name: [email protected]

NoteIf the user ID is less than nine alphanumerics, the node name must match to the user ID.

Ethernet Port Record

Port Number: 5/[5] *Port Type: ETH/[5] *Port MAC Address: 00-00-00-00-00-00/[5] Transmit Queue Limit: 500/[5] *Bridge Link Number: 1/1[5] *Router Interface Number: 1/1



Port Number: 8/[8] *Port Type: ETH/[8] *Port MAC Address: 00-00-00-00-00-00/[8] Transmit Queue Limit: 500/[8] *Bridge Link Number: 2/2[8] *Router Interface Number: 1/2

PVC Setup Table Entry Number: 1/[1] *Source: lcon-1/[1] *Destination: ppp-100/

Port Information Port Number: 100/ [100] *Port Type: PPP/ [100] *Line Interface: ETH/ [100] Node Name Option: SHORT/LONG

NoteUse LONG when the user ID exceeds 8 alphanumerics

[100] Authentication Protocol: PAP_C/ [100] Client Password/Secret: vanguardms/ [100] Network Protocols: IP/ [100] IPCP options: ADDR/ [100] Local IP Address: 0.0.0.0/ [100] Remote IP Address: 0.0.0.0/ [100] Encapsulation: RFC1490/ [100] Auto Connect: Enabled/

NoteAfter accepting the port configuration settings, configure the PPPoE parameters:

Configure PPPoE parameters: [100] *Ethernet Port Number: 5/ [100] Access Concentrator Name: (blank)/ [100] Service Name: (blank)/

Router Interface Interface Number: 1/[1] *Interface State : Enabled/Interface Number: 2/[2] *Interface State : Enabled/Interface Number: 5/[5] *Interface State : Enabled/




IP Interface Entry Number: 1/[1] Interface Number: 2[1] IP Address : 10.10.10.1[1] IP Address Mask: 255.255.255.0/

Entry Number: 2/[2] Interface Number: 5[2] IP Address : 0.0.0.4[2] IP Address Mask: 255.255.255.0/

IP Parameters Default Gateway: 0.0.0.4

NAT Parameters NAT: Enabled/Internal Interfaces:2/Config Type: Advanced/NAT Debugging: Disabled/Bind Idle Timeout: 60/UDP Idle Timeout: 60/TCP Idle Timeout: 60/Enable Translators: FTP+ICMP+DNS/SESSION Idle Timeout: 15/NAPT Port Range: 6000 - 7000/RIP Advertisement: Enabled/

NAT Translation Table [DYNAMIC]

Entry Number: 1/[1] External Interface Numbers: 5/[1] External Address Type: DYNAMIC/[1] Binding Type: NAPT/[1] Internal Address Range: 10.10.10.1,10.10.10.100-10.10.10.102/[1] Overlap: Disabled/


Typical Multilink PPP Over Frame Relay (MLPoFR) and ATM (MLPoA) Applications


Introduction The following diagrams show typical MLPoFR and MLPoA applications used.• MLPoFR allows MLP connections across a Frame Relay or Frame Relay

ATM inter-working network over one or more Frame Relay Bypass stations. • MLPoA allows MLP connections across an ATM or ATM Frame Relay

inter-working network over one or more ATM stations.

ATM or Frame Relayport/station

ATM or Frame Relayport/station

ATM or Frame RelayNetwork

PVC

LAN

MLPPP

LCON

ROUTER

ETH

MLPPP

LCON

ROUTER

ETH

LAN

PVC

LFIEnabled

VoIP and Data

Figure 9. Voice over IP Across Medium to Low Speed Frame Relay or ATM Links

VoIP Across Medium To Low Speed WAN Links

Figure 9 shows Voice over IP (VoIP) over MLPoFR or MLPoATM with enabled multi-class support. Multilink PPP (MLP) over Frame Relay or ATM enables delay-sensitive real-time packets and non-real-time packets to share the same link by fragmenting large data packets into a sequence of smaller data packets (fragments). The fragments are then interleaved with the real-time packets. On the receiving side of the link, the fragments are reassembled and the packet reconstructed. Only one link per MLPPP bundle can be supported. If more than one link is used, there is no way of knowing which link is doing the LFI. This new feature enhances VoIP Quality of Service (QoS) by preventing delay, delay variation (jitter), and packet loss for voice traffic on low speed ATM-to-ATM, FR-to-FR and ATM-to-Frame Relay inter-working networks. MLPPP LFI mechanism is the only solution in cases when Frame Relay fragmentation and interleaving cannot be used (for example, in IP enabled Frame Relay networks). In ATM inter-working networks Frame Relay segmentation and interleaving can be enabled, but it only has effect between sending station and point of conversion in the network. After data packet reassembly, voice and large data packets are further forwarded to ATM. In ATM networks, ATM QoS is ineffective when voice and data are sent over the same VC.Without VOIP over MLPoATM or MLPoFR, customers with FR/ATM IW are forced to use less efficient Layer 3 fragmentation. The multi-class MLPP feature introduces common segmentation for both FR and ATM.

ATMstation/port

Frame Relaystation/port

Frame RelayNetwork

PVC

LAN

MLPPP

LCON

ROUTER

ETH

MLPPP

LCON

ROUTER

ETH

LAN

PVC

ATMNetwork

VoIP and Data

LFIEnabled




Figure 10. VoIP across ATM - Frame Relay Inter-working Network

Multilink PPP over Frame Relay and ATM

Using MLP over either FR or ATM opens some new opportunities. The total bandwidth available to MLP session may be increased by aggregating interfaces and VCs. This is especially useful in case of lower-speed ports.Multilink PPP load balancing techniques send packets across the individual links in a round robin fashion taking care about proper packet ordering. It also makes a multiple link bundle appear as one logical link to the upper layer protocols, requiring only one network address to be configured. In addition, enabling packet fragmentation can in many circumstances increase the efficiency of the multilink connection.Multilink PPP also offers significant link manageability by detecting failed links and removing them from the bundle and returning them back when the link is up. Also links can be added to or removed from the bundle in accordance with the current bandwidth requirements.

ATM or Frame Relaystations/ports

ATM or Frame Relaystations/ports

ATM or Frame RelayNetwork

Agregated Link

PVC

PVC

PVC

PVC

Agregated Link

1

2

3

MLPPP

LCON

ROUTER

1

2

3

MLPPP

LCON

ROUTER

PVC

PVC

PVC

PVC

Figure 11. MLPoFR or MLPoA Aggregated Link


Typical PPP Over ATM and PPPoE over DSL Application

Typical PPP Over ATM and PPPoE over DSL Application

PPPoA and PPPoE over DSL enables access to broadband services over the Vanguard router with an internal DSL modem. This an alternative technology to Frame Relay, ISDN and leased lines. Using lower cost bandwidth of DSL technologies with features provided by PPPoA/PPPoE, remote branch offices can integrate their voice and data services with Quality of Service (QoS) support.

VanguardDSLAM

CentralOffice

DataNetwork

ServiceProvider

Internet

ATM PVC RFC1483/2364

Internet

PPPoE or PPP Session

AccessConcentrator

CorporateGateway

EthernetPort

CustomerPremise

DSLModem

DSL

LAN

Figure 12. PPPoA and PPPoE over DSL



Multilink PPP Over Frame Relay (MLPoFR) Application


Introduction Multilink Point to Point Protocol over Frame Relay (MLPoFR) allows MLP connections across a Frame Relay or Frame Relay ATM inter-working network over one or more Frame Relay Bypass stations in accordance with RFC 1973. Bypass stations may be associated with one or more Frame Relay ports. Port physical interfaces may be the same or different types. This feature will enable PVC link aggregation and bandwidth increase under MLP control. Also MLP Link Fragmentation and Interleaving (LFI) will allow QoS support when FR mechanisms cannot be used.Vanguard supports PPP connections established over the permanent virtual circuit (PVC) only. FR SVCs are not supported. The Frame Relay VC can coexist with other circuits using different Frame Relay encapsulation methods, such as RFC 1490 over the same Frame Relay link. There can be multiple PPP-in-Frame Relay circuits existing on one Frame Relay link.

NoteMLPoFR is supported on the Vanguard 3400, 6800, and 7300 Series platforms and on specific sunset platforms (320, 34x, 6435, 6455)..

NoteInteroperability with Third Party Products is supported.

RFC 1973 RFC 1973 specifies that the Address and Control Field Compression must not be negotiated and the Protocol Field Compression should be negotiated. Magic Number and Protocol Field Compression are recommended and supported.

Frame Relay Stations

Frame Relay Bypass stations are supported. Annex-G stations are not supported. Stations associated to the MLP bundle are allowed to belong to the same or different FR ports.

Frame Relay Physical Interfaces

All Frame Relay physical interface types are supported. Links with different interface types can be associated to the same MLP bundle. Combining links with different speeds is not recommended.

Variable Link Speeds

FRI stations report to PPP the current and maximum speed. Speed can vary depending on congestion. Combining links with different speeds is not recommended.

MLP over Frame Relay Protocol Stack

The PPP over Frame Relay feature allows a router to establish end-to-end Point-to-Point Protocol (PPP) sessions over Frame Relay. PPP treats Frame Relay framing as a bit-synchronous link and can use Frame Relay as a framing mechanism, ignoring its other features. The link must be full-duplex. In general, it may be either dedicated (permanent) (PVC) or switched (SVC). The (ML)PPP link corresponds to an Frame relay virtual circuit (DLCI). IP datagrams are transported over the PPP link using RFC 1973 compliant Frame Relay framing. This feature is useful for remote users running MLPPP to access their Frame Relay corporate networks or an Internet Service Provider (ISP).



PPPoFR only supports PVC FR. If the PPPoFR port is not switched it must be a dedicated link.

(ML)PPPoFR

PHYPHY

(ML)PPPoFR

(ML)PPP

IP

Frame Relay Network

Frame Relay

IP

(ML)PPP

Frame Relay

PHY

Frame Relay

Figure 13. MLP over Frame Relay Protocol Stack




MLPoFR Configuration Example

The MLPPPoFR application with multiple links can be configured as follows:

LCON-1

MLPPP-1ETH-5

Router

PhysicalPort 5

PhysicalPort 1

Vanguard Node

NewStacking

Connection

PPP-100

FRI-1s1

FRI-1

NewStacking

Connection

PPP-101

FRI-2s1

FRI-2

NewStacking

Connection

PPP-102

FRI-7s1

FRI-7

PhysicalPort 2

PhysicalPort 7

Figure 14. MLPPPoFR Application with Multiple Links

PPP Port Configurations

Port Number: 1/100[100] *Port Type: PPP/[100] *Stacking Support: DOWN/[100] Stack Connection Identifier: FRI-1s1/[100] Stacking Mode: NORMAL/[100] Stack Encapsulation: RFC1294/[100] *PPP Operation: Multilink/

Port Number: 1/101[101] *Port Type: PPP/[101] *Stacking Support: DOWN/[101] Stack Connection Identifier: FRI-2s1/



[101] Stacking Mode: NORMAL/[101] Stack Encapsulation: RFC1294/[101] *PPP Operation: Multilink/

Port Number: 1/102[102] *Port Type: PPP/[102] *Stacking Support: DOWN/[102] Stack Connection Identifier: FRI-7s1/[102] Stacking Mode: NORMAL/[102] Stack Encapsulation: RFC1294/[102] *PPP Operation: Multilink/

FRI Port/Station Configurations

Port Number: 1/[1] *Port Type: FRI/

Port Number: 1/2[2] *Port Type: FRI/

Port Number: 1/7[7] *Port Type: FRI/

Port Number: 1/Station Number: 1/[1] *Station Type: BYPASS/[1] *Station Circuit Type: PVC/[1] Stacking Support: Enabled/[1] DLCI: 16/

Port Number: 1/2Station Number: 1/[1] *Station Type: BYPASS/[1] *Station Circuit Type: PVC/[1] Stacking Support: Enabled/[1] DLCI: 16/

Port Number: 1/7Station Number: 1/




[1] *Station Type: BYPASS/[1] *Station Circuit Type: PVC/[1] Stacking Support: Enabled/[1] DLCI: 16/

Ethernet Port Configurations:

Port Number: 1/5[5] *Port Type: ETH/…[5] *Router Interface Number: 1/

PPP Profile configurations:Entry Number: 1/[1] Account Name: N200/…[1] Dedicated Links: (blank)/ppp-100,ppp-101,ppp-102

PPP Parameter Configurations

PPP Node Name: N100/Authentication Protocol: CHAP_C+CHAP_S/PAP Password: remote/

NUI Table Configurations

Entry Number: 1/[1] Account Name: N200/[1] Password: remote/[1] PAD Prompt Number: 0/

Router Interface Configurations, Router Interface States

Interface Number: 1/1[1] *Interface State : Enabled/


Router Interface Configurations, IP Interfaces

Entry Number: 1/1[1] Interface Number: 1/[1] IP Address : 192.168.10.10/[1] IP Address Mask: 255.255.255.0/

Entry Number: 1/5[5] Interface Number: 5/



[5] IP Address : 192.168.11.10/[5] IP Address Mask: 255.255.255.0/

LAN Connection Configurations

Entry Number: 1/…[1] *Router Interface Number: 5/



Multilink PPP Over ATM (MLPoA) Application


Introduction Multilink Point to Point Protocol over ATM (MLPoA) allows MLP connections across an ATM or ATM Frame Relay inter-working network over one or more ATM station in accordance with RFC 2364. MLPoA allows MLP connections across an ATM or ATM/Frame Relay inter-working network over one or more ATM stations. Stations may be associated with one or more ATM ports over same or different interfaces types. Both, LLC/SNAP and VC MUX mode are available. When the PPPoA end point is inter-operating with an RFC 1973 end point only LLC/SNAP mode is supported, to preserve compliance with FRF.8.MLPoA enables PVC link aggregation and bandwidth increase under MLP control. MLP over a single VC allows QoS support for VoIP on lower speed connections. MLP over multiple high-speed VCs facilitates transporting both real-time and data traffic more efficiently by traffic load balancing. Vanguard software supports both Multilink PPP and AAL5 protocols. Only ATM PVCs are supported. ATM SVCs are not supported.

NoteMLPoA is supported on the Vanguard 3400, 6800, and 7300 Series platforms and on specific sunset platforms (320, 34x, 6435, 6455).


RFC 2364 RFC 2364 specifies that the Magic Number option is recommended and Protocol Field Compression options are not recommended. Field Check Sequence Alternatives, Address and Control Field Compression and Asynchronous Control Character Map options must not be negotiated.Supported:

• VC-Multiplexed PPP and LLC/SNAP encapsulated PPP • Magic Number configuration option

Protocol Field Compression, Field Check Sequence Alternatives, Address and Control Field Compression and Asynchronous Control Character Map options are not supported.

Frame Relay/ATM Inter-working

When a connection is through a Frame Relay (FR/ATM FRF.8) service inter-working unit, and the remote end point is RFC 1973 (PPPoFR) only LLC encapsulation shall be used.

ATM Stations Stations associated to the MLP bundle are allowed to belong to the same of different ATM ports.

ATM Physical Interfaces

All ATM physical interface types are supported. Although links with different interface types can be associated to the same MLP bundle, combining links with different speeds is not recommended.



Variable Link Speeds

AAM stations report to the PPP the current and maximum speed.

MLP over ATM Protocol Stack

MLPoA adds an encapsulation layer between PPP and ATM AAL5. The ATM Adaptation Layer 5 (AAL5) protocol is designed to provide virtual connections between end stations attached to the same network. PPP can use AAL5 as a framing mechanism (when an ATM network is configured with point-to-point connections). The PPP layer treats the underlying ATM AAL5 layer service as a bit- synchronous, point-to-point link. In this context, the (ML)PPP link corresponds to an ATM AAL5 virtual circuit. The virtual connection must be full-duplex, point to point, and it may be either dedicated (PVC) or switched (SVC), set up on demand. Framing is defined in RFC 2364 which closely resembles RFC 1483, supporting both virtual circuit multiplexed PPP payloads (VC-multiplexed PPP, VC-Mux mode) and LLC encapsulated PPP payloads on PVCs (LLC encapsulated PPP, LLC-SNAP).

IP

(ML)PPP

(ML)PPPoAAL5

AAL5

ATM

PHYPHY

ATM

PHY

(ML)PPPoAAL5

(ML)PPP

IP

ATM Network

AAL5

ATM

Figure 15. MLP over ATM Protocol Stack



PPPoA and PPPoEoA over DSL (G.SHDSL)


Introduction PPP over ATM (PPPoA) over DSL and PPPoEoA over DSL allows PPP and PPPoE connections over ATM DSL ports and stations.

NoteATM over DSL is G.SHDSL with ATM AAL5 interface support. For more information on DSL, refer to the G.SHDSL Manual (Part Number T0100-14). Release 6.4 and greater does not support a G.SHDSL module for the 7300, but PPPoA can work with interfaces that are T1 and T3.

PPPoEoA adds an encapsulation layer between PPPoE and ATM AAL5. Encapsulation support between the PPPoE and the ATM Layer is necessary to implement PPPoEoA. PPPoEoA complies with RFC 2516 (PPPoE) and RFC 1483 (LLC/SNAP).AAM stations report to the PPP the current and maximum speed.

NotePPPoA and PPPoE are supported on the Vanguard 3400, 6800, and 7300 Series platforms and on specific sunset platforms (320, 34x, 6435, 6455).


PPPoA and PPPoE over DSL

The Digital Subscriber Line (DSL) end-to-end service interoperability model is based on an end-to-end ATM network between the customer premise networks and the service provider networks (ISP, content provider and corporate networks). The ATM endpoints include all the devices at the customer premise (such as a PC, router incorporating a modem or external modem) and the service provider network (an access server or a router) that terminate this end-to-end ATM network. The ATM service may be SVC or PVC. The ATM over DSL architecture preserves the high-speed characteristics and guarantees QoS in the DSL environments without changing protocols. A typical DSL network consists on the customer premises, LAN, router and DSL modem. The modem acts as a MAC layer bridge, relaying traffic to a DSL Access Multiplexer (DSLAM) in a phone company's central office over an ATM Permanent Virtual Circuit (PVC). DSL modem can be separate device, connected to WAN Ethernet port of the router, or can be incorporated in the router. When DSL modem is part of the router there are two options to provide "dial-up" type of connections with ISP. PPPoA (PPP over ATM over DSL) and PPP over Ethernet (PPPoE) (PPPoE over ATM over DSL).

PPPoA PPPoA was initially developed to support DSL services. PPPoA architectures can be deployed using different scenarios depending on the service provider's business model. Only one PPP session can be established over a single VC. If the link has to be shared by multiple users that can be accomplished ether by running multiple PPP sessions over multiple VCs or multiplex multiple IP users in a single PPP session/VC via IP routing. User authentication and accounting is normally best handled by



using an industry standard RADIUS server, which can authenticate a user based on username or the virtual path identifier/virtual channel identifier (VPI/VCI) being used. Currently, most service providers offer different QoS on different PVCs. In PPPoA architecture, IP address allocation for the subscriber CPE uses IPCP negotiation, the same principle of PPP in dial mode.

ATM

AAL5

Service Provider

IP

Ethernet

IP

PPP

PPPoAAL5

AAL5

ATM

DSL DSL

ATM

Sonet/SDHSonet/SDH

ATM

Sonet/SDH

PPPoAAL5

PPP

IP

Router With InternalDSL Modem Central Office ATM Network

AAL5

ATM

Figure 16. PPPoA Protocol Stack




PPPoEoA Configuration Example

The PPPoEoA application can be configured as follows:

NewStacking

Connection

LCON-1

PPP-100 AAM-13s1

AAM-13

ETH-5

Router

PhysicalPort 5

PhysicalPort 13T1/E1

Vanguard Node

Figure 17. Application with one link

PPP Port Configurations

Port Number: 1/100[100] *Port Type: PPP/[100] *Stacking Support: DOWN/[100] Stack Connection Identifier: AAM-13s1/[100] Stacking Mode: NORMAL/PPPOE[100] Stack Encapsulation: NONE/RFC1483_LLC_SNAP[100] *PPP Operation: Multilink/Singlelink[100] *Node Name Option: SHORT/[100] Authentication Protocol: CHAP_S/CHAP_C[100] Client Password/Secret: (blank)/password

Configure PPPoE Parameters:

[101] Access Concentrator Name: (blank)/[101] Service Name: (blank)/[101] MAC Address: (blank)/00-08-D5-00-00-01

AAM Port/Station configurations

Port Number: 1/13[13] *Port Type: AAM/



Port Number: 1/13Station Number: 1/[1] Virtual Path Identifier (VPI): 0/[1] Virtual Channel Identifier (VCI): 32/[1] Link Assurance Method: DISABLED/[1] Traffic Service Category: UBR/[1] VCC Priority Level: NORMAL/[1] Stacking Support: Enabled/

T1/E1 Interface Configuration

Entry Number: 3/[3] *Interface Type: T1/[3] ATM Port: 13/

Ethernet Port Configurations

Port Number: 1/5[5] *Port Type: ETH/…[5] *Router Interface Number: 1/

Router Interface configurations, Router Interface States



Router Interface configurations, IP Interfaces



LAN Connection Configurations

Entry Number: 1/…[1] *Router Interface Number: 5/




G.SHDSL Support

Release 6.4 and greater supports the G.SHDSL/ATM hardware and software module. G.SHDSL is available for Vanguard 3400, 6800, and 7300 Series platforms and on specific sunset platforms (320, 34x, 6435, 6455). This module allows symmetrical DSL connectivity over regular ATM ports, stations and AAL5 protocol. Using either PPPoE or PPPoA encapsulation, a customer will have access to more bandwidth and integrate their network traffic on a single WAN link. This feature enables enterprise customers to subscribe to symmetrical connectivity at lower costs compared to most traditional WAN circuits.

Vanguard PPPoA over G.SHDSL Module

PPPoA over DSL (G.SHDSL) allows PPP connections over ATM-DSL port/stations in accordance with RFC 2364. Operation in either LLC-SNAP or VC-MUX mode is supported. SVCs are not supported.

NoteG.SHDSL is configurable over all AAL5 stations regardless of the physical interface type (T1, T3, DSL).

Vanguard PPPoE over G.SHDSL Module

Vanguard supports PPPoE over an external DSL modem, and PPPoE functionality over a G.SHDSL/ATM module:

• PPPoE implementation in accordance with RFC2516• Interoperability with industry standard Access Concentrator servers• Selection one among many destinations (ISPs) during Discovery stage• Access to Internet and corporate networks for multiple users over a single

PPPoE session• On demand or auto connect PPPoE session setup• Link status monitoring and session reestablishment in case of connection loss


Multilink Point to Point QoS (MLPPP QoS)


Introduction Multilink PPP support for IP Quality of Service (QoS) provides packet segmentation and segment size control, class based priority queuing, interleaving and lower priority class suspension by a higher priority one. QoS support enables strict prioritization of real-time traffic and minimizes delay and delay variation by interleaving higher priority packets among segments of lower priorities. Two interleaving modes (two levels of QoS support) are controlled by configuring the parameters MLP Multiclass and Priority.

• MLP Multiclass (MLPMC) - Multiclass mode provides fragmentation of packets of various priorities into multiple classes of fragments and sending high-priority packets between fragments of lower priority ones in accordance with RFC 2686.

• MLP Voice Priority (MLPVP) - Voice Priority mode allows voice prioritiza-tion and interleaving among fragmented non voice (data) packets. Additional configuration parameters, statistics and alarms are provided to control and monitor traffic and prioritization.

QoS support is provided for the MLP stack only. When the PPP port is configured as Singlelink, QoS support is not available. When QoS features are required over a single link PPP shall be configured as Multilink, consisting of only one member link.

NoteMLPPP QoS is supported on the Vanguard 3400, 6800, and 7300 Series platforms and on specific sunset platforms (320, 34x, 6435, 6455).

NoteInteroperability with Third Party Products and applications is supported.

Packet Delay To effectively transport voice traffic over IP, particular mechanisms are required that ensure reliable delivery of packets with low latency. There are two major sources of packet delay:

• Serialization • Queuing

Serialization delay is the amount of time a router takes to place a packet on a wire for transmission. Delay is especially noticeable when link speed is slow. Packet queuing is necessary to temporarily store packets during congestion and transmission of bursty traffic. When a high priority packet is queued after a large, normal priority packet(s) it has to wait until their transmission is completed.

Quality of Service Quality of Service (QoS) refers to the capability of a network to provide better service to selected network traffic over various underlying technologies. Primary goals of QoS include dedicated bandwidth, controlled jitter and latency (required by some real-time and interactive traffic), and improved loss characteristics. QoS achieves these goals by separating traffic into classes. QoS offers differentiated services to those classes by sharing the available resources between them.




Voice over IP Voice over IP (VoIP) is a Layer 3 network protocol that uses various Layer 2 (linklayer) protocols such as PPP, Frame Relay, or ATM for its transport. VoIP enables routers, access servers, and multiservice access concentrators to carry and send voice and fax traffic over an IP network. To be ready for IP, voice has to be digitized, compressed, framed and stored in voice packets. Normally voice conversations consume 64 kbps of network bandwidth. Compression can reduce the calls to sizes as small as 5.3 kbps for voice samples. Voice packets are transported via IP in compliance with a voice communications protocol or standard such as H.323, Media Gateway Control Protocol (MGCP), or Session Initiation Protocol (SIP). IP/UDP/ RTP headers inserted into every packet add a substantial amount of bandwidth (about 40 bytes per packet). Technologies such as RTP header compression, however, can reduce the IP header overhead to about two bytes. In addition, VAD does not send any packets unless there is active speech.

VoIP QoS over MLPPP

Running VoIP with MLPPP over a low bandwidth leased line, can cause excessive latency and jitter. QoS capability must be added to layer 2 to provide the required voice quality. Multilink PPP provides data packet segmentation so real-time frames can then be interleaved among the segmented data frames. Using techniques mentioned above, Multilink PPP can guarantee maximum delay that reduces the chances of voice packet delay. MLP QoS provides support for VoIP traffic in Multilink PPP. Based on higher layer traffic classification (IP QoS), packets are identified and grouped in up to 16 classes with different priority levels. Since voice is most delay sensitive, it is categorized into a class with the highest priority. Additional configuration parameters are provided to control and monitor QoS features.

Features Multilink Point to Point QoS features include:• Packet segmentation/reassembly with configurable segment size• Layer 3 QoS Priority Class Mapping• Class based priority queing• Interleaving of high priority packets among segmented lower priority traffic

- Multiclass interleavingCompliance with RFC 268Suspension of lower priority traffic by higher priority trafficUp to 16 levels of suspensionSimultaneous delivery of delay-sensitive data over multiple linksLCP negotiation of Multiclass option

- -Priority interleavingVoice traffic prioritizationVoice packet interleaving among data segments (one level of suspen-sion)-Increased throughput for data traffic when voice is not present

• QoS support for applications based on MLPoA and MLPoFR and IPeFR• Additional queue for Expedite Non Drop traffic to prevent packet dropping• Interoperability with third party vendors



Multiclass and Voice Priority Overview

Introduction There are two levels of class marking. Internally, between Layer 3 and Layer 2, outgoing traffic can always be mapped by QoS Kit to one of 16 MLP Priority Classes. Required Priority class is specified by setting a Class Mark field in the software packet header. This class marking is local to MLP. Suspension Class marking is another level, based on RFC 2686, and can be recognized by the peer. By setting a "cls" field in the packet MLP header ( to certain value) a transmitting peer can indicate to the receiving one the quality of service expected for the packet. Number of Suspendable levels is negotiated independently for each direction, per PPP session. When the negotiated number of suspension classes is less then 16, certain priority classes have to be mapped, by MLP, to the same suspension class. This mapping occurs automatically, based on predefined rules, when MLP gets a packet from Layer 3. Regarding QoS, MLP can be in one of the following modes:

TransmissionNormal There is no QoS support.

All packets are treated as class 0. Voice Priority (MLPVP)

Based on the packet Class Mark, two traffic classes can be dif-ferentiated, voice and data. Voice is always sent without any queuing, segmentation and without an MLP header.

Multiclass (MLPMC)

Based on the packet Class Mark, up to 16 classes can be differ-entiated. When the negotiated number of Suspension Classes is less than 16, some of Priority Classes will be mapped to the same Suspension Classes. All packets are transmitted with MLP header with the "cls" field set to appropriate Suspension Class. Multiclass support has to be negotiated by member ports.

ReceptionNormal Multiclass support is not negotiated. MLP handles packets with

MLP header, without checking the "cls" field. All packets are treated as class 0.

Voice Priority (MLPVP)

Multiclass support is not negotiated. MLP is always able to handle packets without an MLP header (voice) e.g. to differen-tiate voice packets, from data packets.

Multiclass (MLPMC)

Multiclass support is negotiated. Packet priority is based on the "cls" field. MLP differentiate negotiated number of Suspension classes.

Inbound and Outbound

There are two configuration parameters available to control bundle's QoS mode. The port Multiclass parameter controls inbound multiclass support. When it is enabled, port sends an LCP configuration request with a Multilink Header Format to initiate Multiclass negotiation. Port always accepts peer's request to send packets with multiclass header, regardless of the status of the multiclass parameter. Prioritization




and interleaving are controlled by bundle's Prioritization configuration parameter. This parameter affects outbound direction only. When it is enabled and ports negotiated multiclass, the bundle supports negotiated number of suspension levels (Multiclass mode), otherwise it differentiate only voice and non-voice traffic (Voice Priority mode). When it is disabled, there is no prioritization and all packets are transmitted as class 0 (Normal mode), regardless of the multiclass status.

Reception Local QoS Support Transmitter ModeLocal Prioritization Peer’s Multiclass

Disabled Disabled NormalEnabled Normal

(Multiclass is negotiated)Enabled Disabled MLPVP

Enabled MLPMC

Reception Local QoS Support Transmitter ModeLocal Prioritization Peer’s Multiclass

Enabled or Disabled Disabled MLPVPEnabled MLPMC

Packet Flow At Layer 2, when prioritization is enabled, outgoing packets are segmented to configured size. Then, packets/segment are queued, based on assigned link priority class. Each class has it's own input and output queue, segmenter/reassembler and sequence number space. Highest priority traffic is never segmented nor queued. Class Based Priority Queuing ensures that the higher priority packets are always de-queued before lower priority ones. Selected packet/segment are interleaved among lower priority packets and sent over one or more PPP links. In the inbound direction, received segments are sent to Reassembler and forwarded to Layer 3 after packets are successfully reassembled. Segments received over multiple links can be reordered. Out of order segments are queued temporarily to maintain proper sequencing. Highest priority packets always bypass the Reassembler. Internal models for both Multiclass and Voice Priority QoS modes are presented Figure 18 and Figure 19.



Figure 18. Multiclass Mode




Figure 19. Voice Priority Mode



Traffic Classification

Layer 3 Classification

MLP QoS support is based on the following Layer 3 (QoS Kit) functionalities:• Bandwidth control • Mapping IP Precedence/DiffServ to 16 link priority classes • Packet marking

For Traffic to be handled properly (at Layer 2 by MLP QoS) outgoing traffic has to be classified at Layer 3. Packets have to be identified, classified and marked in accordance with their IP Precendence/DiffServ values to 16 link Priority Classes. Layer 3 supports 16 link priority classes regardless of the current number supported by MLP. The actual number of Suspension classes for a particular MLP session will depend on MLP configuration and negotiation with the peer. Additional mapping to negotiated number of classes will be provided by MLP. Layer 3 provides bandwidth control by Priority Queuing and Credit Based Queuing. When QoS Kit is not enabled, MLP can provide prioritization for voice traffic based on existing Traffic Class marking.

MLP Classes andPrioritization

Layer 2 QoS support is based on bundle and port configurations as well as the packet priority class. Packets arriving from the Layer 3 to MLP have a valid internal Class Mark (in the software packet header) indicating their Priority Class. The value corresponds to one of sixteen priority levels. Class 15 is the highest priority and 0 the lowest one. Unrecognized classes are treated as the lowest priority traffic. The default value, identical to lowest priority, indicates that for the packet carrying that mark, best effort support is expected. Prioritization is provided only when a corresponding parameter is enabled. Then, if Multiclass is negotiated, a transmitter is able to support up to 16 levels of Suspension classes (MLPMC mode) depending on the peer's request. Each Priority Class (except class 15) has its own input (Reassembler) and output (priority) queue. Class 15 packets are forwarded from/to Layer 3, immediately after reception. When Multiclass is not negotiated (MLPVP mode), there is one output and one receive queue, for data segments. Voice packets are forwarded from/to Layer 3, immediately after reception. In both cases, packets received from the peer, without an MLP header, are treated as the highest priority/voice class.

NoteWhen Prioritization is disabled, all outbound packets are mapped to class 0.




The following table shows the treatment of incoming packets based on the presence of MLP header:

Table 1. Number of Supported Priority Classes in the Outbound DirectionConfiguration QoS Support

Priority Tx Multiclass Status Mode Number of PriorityClasses

Disabled Not Negotiated Normal Class 0Negotiated Normal Class 0Not Negotiated MLPVP 2 (voice/non voice)Negotiated MLPMC (Long

Sequence)Up to 16 (0 to 15)

The following table shows the treatment of incoming packets based on the presence of MLP header:

Table 2. Number of Supported Priority Classes in the Outbound DirectionConfiguration MLP Header Presence in the Received Packet

Priority Tx Multiclass Status Mode Number of PriorityClasses

Disabled or Enabled Not Negotiated Assign to packet Class Mark 15. (Treated as voice.)

Ignore the MC field in the MLP header. (Treated as non-voice.)

Negotiated Assign to packet Class Mark 15. (Treated as voice.)

Read the class field from the MLP header and assign a Class Mark to the packet accordingly.

MLP Mapping When negotiated number of Suspension levels is less than the number of Priority classes (16), MLP has to map unsupported classes in inbound and outbound direction, using predefined rules specified in Figure 20 and Figure 21. For instance, when 8 classes are negotiated for both transmission and reception, using rule from Figure 21, packets having Class Mark 7 are transmitted with value 3 in the header multiclass field. The same applies to Class Marks 8 to 11. That is, packets with classes between 7 to 11 are treated in the same way and directed to the same queue. In this case, the queue 7. When a received packet has a value 3 in the Multiclass field it is assigned Priority Class and Class Mark 7. Values 8 to 11 are never assigned and corresponding queues are never populated. Using the table in Figure 21, it can be also seen that, when for instance, 4 classes are negotiated, all traffic will be mapped to classes 15, 14, 13, 0 and corresponding queues. Suspension class (cls field in the MLP header) will be set to 3, 2, 1 and 0, respectively. In general, the biggest number in the "cls" field of an MLP header, can be calculated as negotiated number of classes minus one.



When MLPVC is enabled, the same rule applies to map Priority class 15 to voice and treat all other classes as data. No mapping in inbound direction is required. When the number of supported classes is one, no QoS support is provided. RFC 2686 allows sending packets without an MLP header. That introduces another 16th level of suspension. When MLPMC is enabled Vanguard MLP implementation does not send packets without an MLP header but is able to receive and handle them properly. MLPMC treats peer's packets without MLP header as highest priority one

Figure 20. Layer 2 Class Mapping Rules - Outbound




Figure 21. Layer 2 Class Mapping Rules - Inbound

Existing Classification

Prior the release 6.4, two traffic classes existed: Default and Voice. Packets were marked to indicate to underlying protocols and software prioritization was required in Voice over Frame Relay (VoFR) or Voice over IP (VoIP) applications. Even though the New Class Marking, has some meaning only between QoS Kit and MLP, there are cases when Priority Class and Traffic Class marking have to coexist. For instance in PPPoFR applications or in cases when QoS Kit is not active and MLP has to recognize voice Traffic Class to provide appropriate support. New Class Marking and existing Traffic Class classification share the same field in the softwares packet header. Voice Traffic Class and Priority class 15 have the same value as well as Default Traffic Class and the lowest Priority class.

Traffic Class and Priority Class Conversion

In PPPoFR applications, Class Marking of outgoing packets (from MLP to FRI) has to be converted to Traffic Class to use Frame Relay prioritization mechanism. For all non-voice packets Traffic Class is set to Default. In the inbound direction, if Frame Relay can differentiate voice from data traffic, Traffic Class is set appropriately. Otherwise, all traffic will be treated as Default. If Rx Multiclass is enabled, MLP will determine the proper class and overwrite Traffic Class, reading the "cls" field from the MLP header. When either MLPMC or MLPVP is enabled, before a packet is sent to or after it is received from Frame Relay the following conversion shall be done:

Traffic Direction PPP Frame RelayPPP to Frame Relay (Tx) Highest Priority Class (15) Traffic Class Voice

Other classes (0 to 14) Traffic Class DefaultFrame Relay to PPP (Rx) Highest Priority Class (15)

(Voice) Traffic Class Voice

This value is determined upon reading the "cls" field in the MLP header.

Traffic Class Default






Multiclass Negotiation

PPP LCP Multilink Header Option

MLP Multiclass support is an LCP negotiation option (RFC2686). The format of the LCP request is shown in Figure 22. Multiclass support, header format and number of suspension classes is negotiated individually for each direction, during the PPP port LCP phase, by sending configuration request with Multilink Header Format.

Figure 22. LCP Multiclass Option Format

Figure 23. LCP Multiclass Option Codes

When the Multiclass configuration parameter is enabled, a port initiates negotiation for each session. It informs the peer that it wishes to receive segments with a particular format and certain number of Suspension classes. The number of suspension levels can vary from session to session. The maximum number of Suspension classes that the receiver wishes to support is a configurable option. If the peer offers another value, the larger shall be rejected and the smaller one shall be accepted. The initiator specifies whether short or long sequence number fragment format with classes will be used. This implementation supports long sequence number fragment format only. Multiclass support is negotiated independently for each direction. Each receiving side requests its own options. This implementation always accepts, an LCP configuration request with a Multilink Header Format from the peer, regardless of the value of Multiclass configuration parameter. Multiclass support can be enabled in one direction and disabled in another. When MLPMC support is disabled, a port shall not request multiclass support.



When the first port with the negotiated multiclass support joins to the bundle, the bundle will support negotiated number of classes if it's Prioritization parameter is enabled. That is, the first port which joins to the bundle, defines the multiclass parameters. All subsequent ports that join to this bundle must have configured the same multiclass parameters. If the port which is about to join to the bundle has negotiated some values different than the first one, it has to be rejected.

PPP and Expedite Non Drop (END) Packets

MLP provides a special treatment to packets received from Layer 3, with the priority field set to Expedite Non Drop (IP RIP, OSPF, IPX RIP, IPX SAP, PIM-SM, BGP4). Currently, when the link is saturated by application data and Layer 3 QoS Kit is not set, it is common that normal packets, including control END packets, are discarded due to PPP protocol queue overflow. Providing a separate queue for END traffic and treating it as an individual protocol shall prevent END packet dropping.




Packet Segmentation/Reassembly

Introduction Vanguard MLP packet segmentation/reassembly is implemented in accordance with RFC1990. Depending on their size, packets can be transmitted as a single segment or multiple segments. A segment is always preceded by an MLP header (specified in RFC1990). Packets are split to number of segments of predetermined (different or equal) size sent over one or more available links. MLP header, inserted in front of every segment, consists of a sequence number, and information on a segment order (first, middle, last). At the receiving side, MLP reassembles packets, received over a single or multiple links. MLP Reassembler is able to identify first, last and intermediate segments and recombine them into the original packet. Reassembler is able to resolve segment reordering as well as to detect a segment loss. If the packet segment is out of order, it shall be queued. When a packet cannot be reassembled due to packet loss all segments belonging to that packet are discarded. Single segment packets are forwarded to Layer 3 upon removing the MLP header.

Figure 24. Long Sequence MLP Headers with Multiclass Bits

Segmentation/ Reassembly With Prioritization

When prioritization is enabled, the purpose of segmentation is to reduce the serialization delay of lower priority packets and maintain it in the range that highest priority traffic can tolerate. Segment size, together with the link speed, determines the serialization delay. High speed links are able to transmit bigger segments than slower ones, causing the same delay. Determining the proper segment size is crucial to keep serialization delay below the specified value. From operator standpoint, it is more convenient to specify the maximum allowed serialization delay than a segment size.



Segment Size Calculation

When prioritization is enabled, segment size is controlled with configuration parameter Maximum Serialization Delay When Voice Is Present. It keeps serialization delay in acceptable range when voice is present. In MLPVP mode, there is the second parameter, Maximum Serialization Delay When Voice Is Not Present which purpose is to enable higher data throughput when voice is not present, by sending more segments. The total serialization delay of all segments sent to one link in front of a voice packet shall be no bigger than value configured with the second parameter. The following formula is used to calculate the segment size: SSVP[bytes] = (Configured MSDVP[ms] * Link Speed[bits/sec])/ (8*1000) SSVP -Segment Size When Voice is Present MSDVP - Maximum Serialization Delay When Voice is Present For each bundle, there is specified a minimum segment size (MSS) that prevents any further packet size reduction when a packet or calculated segment size is smaller than this value. If the segment size is smaller than the configured MSS, then MSS is accepted as a segment size and the resulting serialization delay is larger. The segment sizes are (re)calculated whenever a new link is joined to or removed from the bundle, based on the bundle's slowest link speed.

PPP Link Speed [bps]

Maximum Serialization Delay [ms]

Segment Size [byte]

64000 5 40 64000 25 200 128000 5 80 128000 25 400 1 000 000 5 625 1 000 000 25 3125

Figure 25. Segment Size Samples

For example, if the configured Minimum Segment Size is 64, the segment size will be 64 and the resulting maximum serialization delay will be 8ms. To calculate a proper segment size, the link physical speed must be known by MLP. To calculate the number of segments to be sent over one link, the current link throughput must be known. Presently, PPP assumes that link speed is a constant value. In case of MLPoX applications that is not true. It is responsibility of the underlying protocol to indicate to MLP a throughput change.

Segmentation/ Reassembly with MLPMC

When MLPMC is enabled, segmentation and MLP header content complies with RFC2686, shown in Figure 24. Each class has to have its own sequence number space, reassembler and reassembly buffer. Packets belonging to the highest priority class are never broken into smaller pieces. All such packets/segments are preceded by an MLP header with the proper class number in the class field and BE bits indicate a single-segment packet. That is, the highest priority packet is always




transported as a single segment packet regardless of their size. At the receive side, segment's class is determined by reading the class field from the MLP header and the segment is forwarded to the corresponding class reassembly queue. Highest priority packets are forwarded to Layer 3 right after MLP header removal, bypassing reassembly.

Segmentation/ Reassembly with MLPVP

When MLPVP is enabled, only non-voice traffic is segmented and preceded with RFC1990 MLP header. The highest priority traffic (voice) is never segmented nor preceded by MLP header. That is, voice packets are never split to smaller pieces. At the receive side, packets without an MLP header are treated as a high priority traffic and they bypass MLP reassembly. Packets with MLP header are treated as segments and forwarded to Reassembler if they have an expected sequence number. In case of multiple links with various speeds, voice packets can be reordered at the receive side. Since no sequencing information is assigned to them by MLP, it is not possible to send more than one voice packet over multiple links in parallel and guaranty proper packet ordering.

Segmentation/ Reassembly without prioritization

When prioritization is disabled, packets are segmented and segments are sent over multiple links in parallel. In such a way, multiple physical links can be treated as a single logical link which bandwidth equals to sum of individual bandwidths. At the receive side, segments are reassembled into the original packet. Segment reception should be completed at the receive side approximately at same time, providing minimum overall transmission delay. When prioritization is disabled and multiple links are available, all packets whose size is above the configured minimum size are segmented and the segments are sent in parallel over all available links. Number of segments is equal to the number of links available at the instance of segmentation. If speed of member links are equal, packets are split to the same size segments to ensure (approximately) the same serialization delay for all segments. Equal packet splitting among available links ensures a minimum likelihood of segment reordering. If link speeds are not equal, segment size is modified individually for each link, based on the link speed.

Reassembler Timeout

In the inbound direction, packets/segments belonging to the same must be processed in strict order they were sent. When an out-of-order segment is received, it is queued and an MLP receiver waits for a packet/segments with the expected sequence number some time interval or until packet loss is detected. If one or more packets are lost all subsequent segments will be placed in the reassembly queue until early packet loss is detected or the queue becomes full. Then, cleaning procedure will take place and all segments belonging to uncompleted packet(s) will be discarded and all packets that can be reassembled will be completed. If transmitting side stops sending packets before the receiver detects the packet loss, queued segments and complete packets will be blocked until peer resumes transmission. To avoid that, a waiting period can be limited by configuring a timeout interval. Upon timer expiration, it can be considered that one or more packets are lost. Reassembler for affected class discards collected segments belonging to packet(s) that cannot be completed.



Packet Queuing - Prioritization and Interleaving

Link Class Based Priority Queuing

In the outbound direction, when prioritization is enabled, MLP provides class based priority queuing (CBPQ). Each class has to have its own queue. De-queuing of packets/segments waiting for transmission are based on strict priority. Packets/ segments from certain queue are sent only when all higher priority queues are empty. In the inbound direction, class based queuing is part of the reassembly mechanism. Each class has to have its own queue and Reassembler. Packets are sent to Layer 3 as soon as they are received or reassembled.

Traffic Suspension In the outbound direction, when prioritization is enabled, there is a mechanism to suspend lower priority traffic and insert higher priority packets/segments in between them. When MLPVP is enabled, there is one level of suspension. Voice packets are inserted in between non-voice segments. When MLPMC is enabled, there are up to 16 levels of suspension (including sending packets without the MLP header).

Packet Drop The maximum number of packets allowed to be queued (queue size) shall be a configurable option for each outbound queue. When an output queue is full, a tail drop mechanism takes place. That is, each new packet, whose all segments can't be queued completely shall be discarded. In inbound direction, lost packet(s) or segment(s) can stop de-queuing packets from a certain queue. When packet loss is detected, it must be cleared to enable processing of packets that can be completed. Only particular packets that cannot be reassembled are discarded.

Flow Control

Data Rate When Voice Is Not Present

When MLPVP is enabled, but high priority traffic is not present, the rate of the outgoing data traffic can be increased by sending more segments over each link. Data rate, when voice is not present can be controlled by configuration parameter Maximum Serialization Delay When Voice Is Not Present (SDVNP). When voice traffic starts, the rate of normal priority traffic is reduced to fewer number of segments per link. Value for SDVNP shall be selected carefully to avoid voice delay.

Driver Buffers When the protocol module completes packet processing in an outbound direction it forwards the packet/segment to the associated port driver. Ideally, as soon a packet is transmitted and the driver buffer descriptor ring is emptied, another packet should be forwarded from the protocol to driver. If the CPU scheduling cannot provide such responsiveness, gaps are inserted in between packets (which effectively reduces the transmission rate). To avoid starving, more packets are normally forwarded to the driver from the protocol queue(s) at once. On the other hand, accumulating too many data bytes in front of the delay sensitive packets can cause unacceptable serialization delays. To balance voice delay and data rate, MLP provides a configurable profile parameter: Driver Buffer Limit and a mechanism to control the amount of data that can be accumulated in driver's buffers.




Typical MLP QoS Application

VoIP Across Medium To Low Speed WAN Links

This application involves Voice over IP (VoIP) over MLPoATM or MLPoFR with enabled multi-class support. Multilink PPP (MLP) over Frame Relay or ATM enables delay-sensitive real-time packets and non-real-time packets to share the same link by fragmenting large data packets into a sequence of smaller data packets (fragments). The fragments are then interleaved with the real-time packets. On the receiving side of the link, the fragments are reassembled and the packet reconstructed. MLP QoS enhances VoIP Quality of Service (QoS) by preventing delay, delay variation (jitter), and packet loss for voice traffic on low speed ATM-to- ATM, FR-to-FR and ATM-to-Frame Relay inter-working networks. The MLPPP LFI mechanism is only a solution in cases when Frame Relay fragmentation and interleaving cannot be used (for example: in IP enabled Frame Relay networks).

Figure 26. VoIP Across Medium to Low Speed WAN Links

Without Multiclass MLPP customers with FR/ATM IW were forced to use less efficient Layer 3 fragmentation. The Multiclass MLPP feature introduces common segmentation for both FR and ATM. In ATM inter-working networks, Frame Relay segmentation and interleaving can be enabled, but it only has effect between the sending station and point of conversion in the network. After data packet reassembly, voice and the large data packets are further forwarded to ATM. In ATM networks, ATM QoS is ineffective when voice and data are sent over the same VC.

Figure 27. VoIP Across ATM / Frame Relay Inter-working Network



Video Traffic Across Medium To Low Speed WAN Links

MLPoFR and MLPoA with enabled multi-class support will enable applications involving video traffic (in scenarios similar to ones described in Figure 26). Video packets are sensitive to delay and delay variation and need a treatment similar to voice packets. Unlike small voice packets, which are never segmented, video packets must be segmented, particularly in presence of voice. With priority next to the voice, video segments are de-queued and interleaved among other packets and transmitted to the destination.



Link Methods

Link Methods

Introduction This section describes the characteristics of Single Link and MultiLink PPP. As well, it shows you configuration models that demonstrate the qualities of each link method.

Navigating the CTP Figure 28 shows how to navigate from the Configure CTP menu to the PPP records that are necessary to configure for MultiLink PPP operation:

Port Number: 2/100Port Type: PPP/Line Interface: ISDN/PPP Operation: Multilink/

PPP Node Name: New/Authentication Protocol: CHAP_S/PAP Password: Remote/

Entry Number: 1/Account Name: New/Authentication Protocol: CHAP_C/CHAP Secret: Remote/Network Protocols: IP/IPCP options: VJ/Encapsulation: RFC1490/Compression Control Protocol: NONE/Dial Number #1: (blank)/Dedicated Links: (blank)/Maximum Number of Switched Links: 2/Add Bandwidth Threshold: 60/Add Bandwidth Wait Time: 20/Remove Bandwidth Wait Time: 20/Idle Disconnect: 100/Auto Connect: Disabled/

Node: Address: Date: Time:Menu: Configure Path: (Main.6)

1. Node 19. BSTD Station Table2. Port 20. XDLC Port Stations3. Configure Network Services 21. Configure Bridge4. Inbound Call Translation Table 22. Configure LAN Connections5. Outbound Call Translation Table 23. Software Key Table6. PAD Prompt Table 24. Configure Router7. Calling Addr Translation Table 25. FRA Stations8. BSC/DSP3270 Device Table 26. LLC to SDLC Tables9. NUI/Password Table 27. ISDN Channels10. PAD Profile Table 28. DORA Record11. Remote PAD Parameter Table 29. Network NUIC Record12. Master MX25 Stations 30. Configure SNMP13. Node to node download 31. TCP14. SVC Broadcast Output Table 32. PPP Parameters15. PVC Broadcast Output Table 33. PPP Profiles16. SDLC Port Stations Table 34. Virtual Port Mapping17. FRI Stations Table 35. Configure SPFM Connection18. Internal DSD Table 36. SMDS Stations

#Enter Selection:

Figure 28. How to Find PPP Records


Link Methods

Single Link PPP

Description Single Link PPP establishes a single connection over a PPP link. It is used for a dedicated link, one that must be in place all the time, on legacy systems that are not capable of handling or configured for MultiLink connections.

NoteRemote nodes that are configured for MultiLink can negotiate a connection with a port configured for Single Link.

Programming Model

Figure 29 shows the programming model of PPP when operating in Single Link mode over ISDN passing LAN traffic.

PPP Port xx

PPPPort yy

LCON #1

LCON # 2

B

B

ISDN

ISDN BRI connection shown. Other alternatives are serial interfaces for Ports xx and yy.

ISDN BRI

Connection between ISDN and PPP port established via Vanguard ISDN record

Internal connection via PVC table entries

Each LCON/PPP Port represents a connection to a separate remote location.

You can configure up to two LCON/PPP Port combinations for the Vanguard ISDN. Additional LCON/PPP pairs are possible with a serial interface.

Figure 29. Single Link PPP Configuration Model With ISDN



Link Methods

Configuring Connections

When you are using a Single Link connection, you configure the parameters for authentication, Network Control Protocols (NCPs), dial up and bandwidth control in a virtual PPP port record. This table describes the procedure for configuring a Single Link PPP connection over Vanguard ISDN:

Step Action 1 Configure the Node Record. The Node Name parameter identifies the

node during authentication. The Max Frame Size parameter is used as MRU (Maximum receive Unit) during LCP negotiation. The Expanded Node Name parameter provides a longer name for PPP Authentication.

2 Configure the Port record(s). Configure the Port Type parameter with the PPP option and the PPP Operation parameter with the Singlelink option. Configure the Node Name Option (Long) when using the Expanded Node Name parameter. All network and dial on demand parameters are specified within the PPP Port record.

3 Configure the PPP Parameters record(s). Choose your method of authentication, CHAP or PAP, here.The NUI/Password Table is used by the authentication server to store the remote node’s Name and CHAP Secret or PAP Password.

4 Configure the ISDN Channel record. To configure a PPP connection, you must configure the Protocol Type parameter as PPP and the Virtual Port parameter with the number of a virtual port configured as a PPP port.For Single Link PPP, you also configure the remote node’s ISDN numbers (SPIDs) in the Vanguard ISDN record in the corresponding B Channel. When configuring the B Channel parameters:

• Dial Retry set to 0• Number of Call retries set to 1


Link Methods

MultiLink PPP

Description PPP was originally designed using a single link to connect two routers. However, it can also operate with multiple links. This enhancement is called MultiLink PPP (MP). MP brings up multiple connections over a PPP link.MP has the capabilities of Single Link PPP with these additional functions:

• operates with one or more links for each PPP connection• adds links dynamically with Bandwidth on Demand• shares switched PPP links among multiple connections

The main advantages of MP are that it passes data more quickly than Single Link PPP and allows for multiple connections dynamically. With MP, a large frame is segmented into smaller chunks and then distributed among the various PPP links connecting the two routers. The receiving routers recombine these frame segments to re-create the original frame.

Programming Model

Figure 30 shows the programming model of PPP when operating in MultiLink mode over ISDN passing LAN traffic.

Internal connection via PVC table entries.

PPP Prof #1

PPPProf #2

LCON #1

LCON # 2 B

ISDN

ISDN BRI connection shown. Other alternatives are serial interfaces for Ports xx and yy.

PPP Prof #3

PPPProf #4

LCON #1

LCON # 2

PPP (ML)Port xx

Port yy BPPP (ML)

Connection between ISDN and PPP port established via Vanguard ISDN record.

Each LCON/PPP Profile pair represents a connection to a separate remote location.

Up to four PPP Profiles are permitted per node. They contend for the two ISDN B channels on demand and on a first come, first served basis.

ISDN connections can be replaced by serial links with modems. The current MP supports modem dial-in for central sites but does not support dial out on other transmission devices except ISDN.

Figure 30. MultiLink PPP Configuration Model (Shown With ISDN)



Link Methods

Configuring Connections

When you are using MultiLink PPP, you configure the parameter for PPP operation in the port record, the parameters for authentication in the PPP parameters records, and the parameters for NCPs, dial up and bandwidth control in PPP profiles.This table describes the procedure for configuring a MultiLink PPP connection over Vanguard.

Step Action 1 Configure the Node Record. The Nodename parameter identifies the node

during authentication. The Max Frame Size parameter is used as MRU (Maximum Receive Unit) during LCP negotiation.

2 Configure the Port record(s). You must configure the Port Type parameter with the PPP option and the PPP Operation parameter with the Multilink option.

3 Configure the PPP Parameters record(s). You choose your method of authentication, CHAP or PAP, here. Note that the PPP Nodename is used to identify the node during authentication.The NUI/Password Table is used by the authentication server to store the remote node’s Name and CHAP Secret or PAP Password.

4 Configure the PPP Profile records. You can configure up to 4 PPP Profiles for each port. You must configure at least one for each remote location to which the node connects. The ISDN number of the remote nodes are configured in the corresponding PPP Profile only. In contrast, Single Link PPP requires the ISDN numbers be configured in the ISDN Record for Vanguard products.

5 Configure the ISDN Channel record. The Vanguard ISDN implementation provides dial control for protocols which assume the physical layer to be permanently available. In contrast, PPP’s bandwidth management requires more control over dial attempts and dial numbers.When operating PPP over ISDN, be sure that associated B channel parameters are configured with:

• Dial retry Interval set to 0• Number of Call Retries set to 1


Link Methods

Multilink PPP (MLPPP, MLP, MLPPPoX)

What is it? Release 6.4 and greater Multilink Point to Point Protocol (MLPPP, MLP or MLPPPoX) is a higher-level data link protocol that sits between PPP and the network protocol layer. MLPPP combines multiple, lower-speed links into a single, higher speed data path and gives the users extra bandwidth as needed. MLPPP allows routers and other access devices to combine multiple PPP links connected over various WAN interfaces into a logical pipe. MLPPP is designed to handle more than one physical link at a time. MLPPP has various components:

• Operates with one or more links for each PPP connection• Adds links dynamically with Bandwidth on Demand• Shares switched PPP links among multiple connections

Release 6.4 and greater supports:• Link Fragmentation and Interleaving (LFI)• Packet Sequencing• Cascading Configuration

What Application Is It Suitable For?

MLPPP is suitable for high level data links that require extra bandwidth. Release 6.4 and greater MLPPP features such as Link Fragmentation and Interleaving (LFI) and packet sequencing are very useful when connection is established over Frame Relay or ATM. These features enable level two Quality of Service (QoS) and load balancing which improves Voice over IP (VoIP) quality and link efficiency.Release 6.4 and greater supports:

• (ML)PPP Quality of Service - (MLPQoS)• Vanguard G.SHDSL hardware and software

Release 6.4 and greater software also supports (ML)PPPoX functionality. Where the(X) in (ML)PPPoX stands for a combination of either:

• (ML)PPP over Frame Relay - (MLPoFR)• (ML)PPP over ATM - (MLPoA)• PPP over ATM over DSL - (PPPoA over DSL)• (ML)PPP over ATM over DSL - ((ML)PPPoA over DSL)• PPP over Ethernet over ATM over DSL - (PPPoEoA over DSL)

NoteRelease 6.4 and greater supports Cascading Configuration (CCFG) through the Control Terminal Port (CTP). Cascading Configuration is designed to make the configuration of (ML)PPPo(X) features easier. Cascading configuration allows configuration of related items in sequence (without having to navigate through menus). Refer to the “Cascading Configuration” section on page 88 for more information.



Link Methods

MLPPPoX Chart MLPPoX is supported on the following Vanguard platforms in Release 6.4 and greater:

Vanguard Platform

MLPoFR MLPoA PPPoE PPPoA PPPoEoA PPPoA over DSL

PPPoEoA over DSL

3400 supported supported supported supported supported supported supported6800 supported supported supported supported supported supported supported7300 supported supported supported supported supported supported

Vanguard Sunset Products320 supported supported supported34x supported supported supported supported supported supported

6435, 6455 supported supported supported supported supported supported supported

NoteTo support PPPoA over DSL and PPPoEoA over DSL, the internal DSL modem is required. For more information on DSL reference the G.SHDSL Manual (Part Number T0100-14).

NoteATM over DSL in Release 6.4 and greater uses G.SHDSL with ATM AAL5 interface support.

MLPPPoX Implementation

MLPPPo(X) functionality is implemented in accordance with the following RFC’s:• Point to Point Protocol, RFC 1661, RFC 1990• PPPoE, RFC 2516• PPP in Frame Relay, RFC 1973• MLPoFR, RFC 1974• MLPoA and PPPoA (over AAL5), RFC 2364• Multiclass, RFC 2686• Multilink, RFC 1990• Multiprotocol Encapsulation over AAL5, RFC 1483




Introduction This section shows you how to configure authentication for Single Link and MultiLink connections.

NoteTo have no authentication applied to (either type of) link, it must be configured as a dedicated link in a profile. The same profile’s Authentication Protocol parameter must not have the CHAP_S or PAP_S options selected.

Navigating the CTP Figure 31 shows how to navigate from the Configure CTP menu to the records used in configuring authentication.

Node: Address: Date: Time:Menu: Configure Path: (Main.6)

1. Node 19. BSTD Station Table2. Port 20. XDLC Port Stations3. Configure Network Services 21. Configure Bridge4. Inbound Call Translation Table 22. Configure LAN Connections5. Outbound Call Translation Table 23. Software Key Table6. PAD Prompt Table 24. Configure Router7. Calling Addr Translation Table 25. FRA Stations8. BSC/DSP3270 Device Table 26. LLC to SDLC Tables9. NUI/Password Table 27. ISDN Channels10. PAD Profile Table 28. DORA Record11. Remote PAD Parameter Table 29. Network NUIC Record12. Master MX25 Stations 30. Configure SNMP13. Node to node download 31. TCP14. SVC Broadcast Output Table 32. PPP Parameters15. PVC Broadcast Output Table 33. PPP Profiles16. SDLC Port Stations 34. Virtual Port Mapping Table17. FRI Stations 35. Configure SPFM Connection Table18.Internal DSD Table 36. SMDS Stations

#Enter Selection:

Entry NumberAccount NamePassword

PPP Node Name Authentication Protocol

Password

Entry NumberAccount NameAuthentication ProtocolCHAP Secret

Figure 31. How to Find Records for Configuring Authentication




Single Link PPP

Description This section describes the relationship between authentication parameters on a unidirectional, single, dedicated link.

Authentication Figure 32 shows the relationship of configuration records. The arrows indicate the parameters that must be consistent between the two nodes.

PPP Port Record

Node Name Option

Node Record

LONG

NUI TableAccount Name Atlanta_Node_201;

Node: Authentication Server Node: Authentication Client

Password Boston_Tea_Party;

Node Name

Expanded Node Name

Atlanta

Atlanta_Node_201;

Node Record

Node Name

Expanded Node Name

Boston

Boston_Node_101;

PPP Operation Singlelink

PPP Port Type PPP

Authentication

Password/SecretCHAP_S or PAP_SN/A

PPP Port Record

Node Name Option LONG

PPP Operation Singlelink

PPP Port Type PPP

Authentication

Password/Secret

CHAP_C or PAP_C

Boston_Tea_Party;

Figure 32. CHAP/PAP Authentication for PPP (Single Link) Configura-tion

For Single Link PPP, configure the PPP Port Record parameter Authentication Protocol and either the CHAP Secret or PAP Password parameter. The Node Record parameter Expanded Node Name is used to identify a caller to the remote node.A PPP port acting as an authentication server (CHAP_S or PAP_S) references the NUI/Password table to authenticate its peer.

NoteUp to 64 character names and 32 character passwords/secrets are supported when operating as an authentication peer or server.



MultiLink PPP

Description This section describes the relationship of PPP parameters between two connecting nodes for CHAP and PAP authentication.

NoteUp to 64 character names and 32 character passwords/secrets are supported when operating as an authentication peer or server.

To have no authentication, you must have a dedicated link with the port parameter Authentication set to NONE.

CHAP Authentication

Figure 33 shows the parameters which are essential to CHAP authentication. The arrows indicate the parameters that must be consistent between the two nodes.

PPP Port Record

NUI TableAccount Name Atlanta_Node_201;

Password Boston_Tea_Party;

Node Record

Node Name Boston

PPP Operation Multilink

PPP Port Type PPP


PPP Parameters

PAP Password Boston_Tea_Party;

PPP Node Name Boston_Node_101;

Node Record

Node Name

Authentication CHAP_S

Account Name

CHAP Secret RemoteAuthentication CHAP_S

PPP Profile

Atlanta

PPP Port Record

PPP Operation Multilink

PPP Port Type PPP

PPP Parameters

PAP Password Boston_Tea_Party;

PPP Node Name Atlanta_Node_201;

Authentication CHAP_C

Account Name

CHAP SecretAuthentication CHAP_C

PPP ProfileAtlanta_Node_201; Boston_Node_101;

Boston_Tea_Party;

Figure 33. Configuration of CHAP Authentication

Node Authentication Peer:• Before a call is initiated, a profile is selected. The profile’s authentication

determines if it can be an authentication peer, such as a CHAP client (CHAP_C). This is specified in the PPP Parameters Record.

• The PPP Profile’s Account Name must be identical to the CHAP server’s PPP Node Name. This selects the profile.




Node Authentication Server:• A node that receives a call specifies an authentication server type, CHAP or

PAP. This is specified in the PPP Parameters Record.• Regarding NUI Table entries:

- Account Name must be identical to the Authentication Peer’s PPP Node Name.

- Password must be identical to the Authentication Peer’s CHAP Secret.• The PPP Profile’s Account Name must be identical to the Authentication

Peer’s PPP Node Name. This selects the profile.The Vanguard CHAP implementation allows a Secret to be unique for each remote node it connects with. The client’s Secret is located in the PPP Profile, where a unique profile is configured for each node it connects with. This uniqueness of CHAP Secrets prevents a remote node from using your Secret to access another site that you also access.

PAP Authentication Figure 34 shows the parameters which are essential to PAP authentication. The arrows indicate the parameters that must be consistent between the two nodes.

PPP Parameters

PPP ProfileNUI Table

PPP Node Name

Account Name

AuthenticationAccount Name

Password

PPP Parameters

PPP Node NameSan_Francisco;

Boston;

Boston;

PAP_CTea_Party

San_Francisco;

Authentication PAP_S

PPP Profile

Account Name Boston;


PAP Password Tea_Party;

Figure 34. Configuration of PAP Authentication

Node Authentication Peer• When initiating a call, a profile is selected before the call is initiated. The

profile’s authentication determines if it can be an authentication peer, such as a PAP client (PAP_C). This is shown in the Authentication Peer’s PPP Profile.

• The PPP Profile’s Account Name does not have to match the PAP server’s PPP Node Name. However consistent names allow a transition to CHAP to be simpler.



Node Authentication Server• A node that receives a call must specify a type of authentication server, either

CHAP or PAP. This is shown in the PPP Parameters.• The NUI Table entries are defined below:

- Account Name must be identical to the Authentication Peers PPP Node Name.

- Password must be identical to the PAP Password.• The PPP Profile’s Account Name must be identical to the PAP client’s PPP

Node Name. This is used to select the profile.



Configuration Examples


Introduction This section provides diagrams and parameter tables that show you how to configure Vanguard products to use PPP options and features. These examples include:

• Single Direction Authentication Using CHAP on page 70• Bidirectional Authentication Using CHAP on page 72• Bridging on page 74• Proprietary Compression on page 76• Synchronous Links in MultiLink PPP and IP over ISDN on page 78• Asynchronous PPP, Windows 95 and Frame Relay on page 80• Asynchronous PPP Using AT Dialer on page 81• MultiLink PPP Over BRI on page 85• MultiLink PPP Over PRI on page 87



Single Direction Authentication Using CHAP

Description In this example, the node answering the call initiates authentication. The node initiating the call trusts the ISDN service provider always routes the call correctly to the desired destination. Either of the 2 nodes may initiate a call. An IP router can only initiate a call if it has a configured route to the remote network, such as a default gateway or a static route. Both routers have their default gateway pointing to the adjacent network. Unnumbered IP interfaces are used to minimize the consumption of IP addresses.MultiLink PPP, using ISDN links, provides Bandwidth on Demand. Node 200, in Figure 35, is configured with bandwidth management parameters such that it adds the additional ISDN link.

Example Figure 35 shows how to configure Vanguard 312s to use single direction authentication over BRI ISDN.

BRI ISDN Interface*D Channel Port: 1Switch Type: NI-1*First B Channel Port: 2(First) Access Type: CMD(First) Line Speed: 64K(First) SPID: 416805161300(First) Local Subscriber

Directory Number: 8051613*Second B Channel Port: 3(Second) Access Type: CMD(Second) Line Speed: 64K(Second) SPID: 416805162900(Second) Local Subscriber

Directory Number: 8051629




VG34xxNode200

VG34xxNode100 ISDN

Server

PC192.0.0.1 192.0.1.1

Port Record[1]*Port Type: X25

[2]*Port Type: PPP[2]*Line Interface: ISDN[2]*PPP Operation: Multilink[3]*Port Type: PPP[3]*Line Interface: ISDN[3]*PPP Operation: Multilink

PPP ProfilesAccount Name: Node200;CHAP Secret: 100_200C;Network Protocols: IPIPCP options: ADDR+VJLocal IP Address: 192.0.0.1Remote IP Address: 192.0.1.1Dial Number #1: 98051613Dial Number #2: 98051629

Port Record[1]*Port Type: X25[2]*Port Type: PPP[2]*Line Interface: ISDN[2]*PPP Operation: Multilink[3]*Port Type: PPP[3]*Line Interface: ISDN[3]*PPP Operation: Multilink

PPP ProfilesAccount Name: Node100;CHAP Secret: 200_100C;Network Protocols: IPIPCP options: ADDR+VJLocal IP Address: 192.0.1.1Remote IP Address: 192.0.0.1Dial Number #1: 98059625Dial Number #2: 98050926Add Bandwidth Wait Time: 10Remove Bandwidth Wait Time: 10

PPP ParametersPPP Node Name: Node200;

NUI/Password TableAccount Name: Node100;Password: 100_200C;

LAN Connection Table[1] Encapsulation Type: RFC1294




PVC Setup Table*Source: LCON-1*Destination: MLPPP-1

Interfaces Table*Interface #1 State: Enabled*Interface #5 State: Enabled

IP Parameters*Internal IP Address: 192.0.0.1*Default Gateway: 0.0.0.4

IP Interface Configuration Table[1]*Interface Number: 1[1]*IP Address : 192.0.0.1

[2]*Interface Number: 5[2]*IP Address : 0.0.0.4

PVC Setup TableSource: LCON-1Destination: MLPPP-1



IP Interface Configuration Table[1]*Interface Number: 1[1]*IP Address : 192.0.1.1

[2]*Interface Number: 5[2]*IP Address : 0.0.0.4




]

Figure 35. Single Direction CHAP With Unnumbered IP



Bidirectional Authentication Using CHAP

Description In this example, both nodes initiate authentication regardless if they originated or answered the call. Either of the two nodes may initiate a call. An IP router can only initiate a call if it has a configured route to the remote network, such as a default gateway or a static route. Both routers have their default gateway pointing to the adjacent network. Unnumbered IP interfaces are used to minimize the consumption of IP addresses.MultiLink PPP, using ISDN links, provides Bandwidth on Demand. Node 200, in Figure 36, is configured with bandwidth management parameters such that it adds the additional ISDN link.




Example Figure 36 shows you how to configure Vanguard 3xxs to use bidirectional authentication over BRI ISDN.








PPP ProfilesAccount Name: Node100;Authentication Protocol:

CHAP_S+CHAP_CCHAP Secret: 200_100C;Network Protocols: IPIPCP options: ADDR+VJLocal IP Address: 192.0.1.1Remote IP Address: 192.0.0.1Dial Number #1: 98059625Dial Number #2: 98050926Add Bandwidth Wait Time:10Remove Bandwidth Wait Time:10

PPP ParametersPPP Node Name: Node200;Authentication Protocol:

CHAP_S+CHAP_CNUI/Password TableAccount Name: Node100;Password: 100_200C;


VG34xxNode200

VG34xxNode100 ISDN

Server

PC

192.0.0.1 192.0.1.1


PPP ProfilesAccount Name: Node200;Authentication Protocol:

CHAP_S+CHAP_CCHAP Secret: 100_200C;Network Protocols: IPIPCP options: ADDR+VJLocal IP Address: 192.0.0.1Remote IP Address: 192.0.1.1Dial Number #1: 98051613Dial Number #2: 98051629

PPP ParametersPPP Node Name: Node100;Authentication Protocol:

CHAP_S+CHAP_CNUI/Password TableAccount Name: Node200;Password: 200_100C;





IP Interface Configuration Table[1]*Interface Number: 1[1]*IP Address : 192.0.0.1[2]*Interface Number: 5[2]*IP Address : 0.0.0.4





Figure 36. Bidirectional CHAP With Unnumbered IP



Bridging

Description In this example, the node answering the call initiates authentication. The node initiating the call trusts the ISDN service provider always routes the call correctly to the desired destination. PPP’s Bridge Control Protocol (BCP) is used to do transparent bridging of Ethernet frames (IEEE 802.3). The LAN traffic at the server may include frequent UDP/IP broadcast traffic, ARP broadcasts and a generous amount of TCP/IP traffic destined for other PCs. This traffic requires filtering to ensure efficient use of the ISDN bandwidth. In contrast, the remote LAN traffic is primarily destined to the server or a router. No filtering is applied toward the server. Filtering applied at Node 100 does not allow it to originate a call using an ARP broadcast to locate the remote PC. Node 200 can originate a call at any time.MultiLink PPP, using ISDN links, provides Bandwidth on Demand. Node 200, in Figure 37, is configured with bandwidth management parameters such that it adds the additional ISDN link.

MAC Addressing In this example, you need to know the MAC (Media Access Control) Address for your PC to configure the Filter Table for Node 100. If you cannot identify the correct MAC Address:

Step Action 1 Connect the PC and Vanguard device to the same LAN segment. Ensure

that these are the only devices on the LAN.2 Using the ping utility, from the PC, to ping an IP address such as

192.0.0.1.3 Select TB Forwarding Table Stats from the Bridge Stats menu. The

displayed statistics indicates one MAC Address with the Learned status. This is the PC’s MAC Address.

4 Enter this MAC Address in the MAC Address Filter Table for Node 100.

Example Figure 37 shows you how to configure Vanguard 3xxs to use transparent bridging with PPP’s BCP option over BRI ISDN.

BRI ISDN Interface*D Channel Port: 1Switch Type: NI-1*First B Channel Port: 2(First) Access Type: CMD(First) Line Speed: 64K(First) SPID: 416805161300(First) Local Subscriber Directory

Number: 8051613*Second B Channel Port: 3(Second) Access Type: CMD(Second) Line Speed: 64K(Second) SPID: 4168051629000(Second) Local Subscriber Directory

Number: 8051629


PPP ProfilesAccount Name: Node100;CHAP Secret: 200_100C;Network Protocols: BridgeDial Number #1: 98059625Dial Number #2: 98050926Add Bandwidth Wait Time:10Remove Bandwidth Wait Time:10Idle Disconnect Timer: 5


BRI ISDN Interface*D Channel Port: 1Switch Type: NI-1*First B Channel Port: 2(First) Access Type: CMD(First) Line Speed: 64K(First) SPID: 416805962500(First) Local Subscriber Directory

Number: 8059625*Second B Channel Port: 3(Second) Access Type: CMD(Second) Line Speed: 64K(Second) SPID: 416805092600(Second) Local Subscriber Directory

Number: 8050926

VG34xxNode200

VG34xxNode100 ISDN

Server

PC


PPP ProfilesAccount Name: Node200;CHAP Secret: 100_200C;Network Protocols: BridgeDial Number #1: 98051613Dial Number #2: 98051629


PCRouter

Mac Address Filter Table[1] MAC Address: 00-AA-00-BA-55-3B[2] MAC Address: 00-AA-00-BA-55-3D


LAN Connection Table*LAN Forwarder Type: BRIDEncapsulation Type: RFC1294



Bridge ParametersBridged Protocols: IP

Bridge Link Table[1] “default record”[5] *Bridge Type: TB[5] MAC Address Filter Action: BLOCK

MAC Address Filters TableMAC Address: 00-AA-00-BA-55-3BIncoming Source Address Link Action: PASSLISTIncoming Source: List of Links: 5Outgoing Destination Address Link Action: PASSLISTOutgoing Destination: List of Links: 5

LAN Connection Table*LAN Forwarder Type: BRIDEncapsulation Type: RFC1294


Bridge ParametersBridged Protocols: IP

Bridge Link Table[1] “default record”[5] “default record”




Figure 37. Bridging With PPP’s Bridging Control Protocol



Proprietary Compression

Description Proprietary data compression (typically with a compression ratio of 2:1) allows increased throughput. However, you only use proprietary data compression in a network of Vanguard products. The architecture used for data compression allows Appletalk routing but only IP routing is shown in this example.In this example, the node answering the call initiates single direction authentication. The node initiating the call trusts the ISDN service provider always routes the call correctly to the desired destination. Either of the two nodes may initiate a call. An IP router can only initiate a call if it has a configured route to the remote network, such as a default gateway or a static route. Both routers have their default gateway pointing to the adjacent network. Unnumbered IP interfaces are used to minimize the consumption of IP addresses.MultiLink PPP, using ISDN links, provides Bandwidth on Demand. Node 200, in Figure 38, is configured with bandwidth management parameters such that it adds the additional ISDN link.

NoteWhen you are using data compression, Vanguard’s bridging capability is also available.

Example Figure 38 shows you how to configure proprietary compression on Vanguard 34xxs.



Directory Number: 8051629Port Record[1]*Port Type: X25[2]*Port Type: PPP[2]*Line Interface: ISDN[2]*PPP Operation: Multilink[3]*Port Type: PPP[3]*Line Interface: ISDN[3]*PPP Operation: Multilink




VG34xxNode200

VG34xxNode100 ISDN

Server

PC192.0.0.1

192.0.1.1


PPP ProfilesAccount Name: Node200;CHAP Secret: 100_200C;Network Protocols: IPIPCP options: ADDR+VJLocal IP Address: 192.0.0.1Remote IP Address: 192.0.1.1Compression Control Protocol:PROPDial Number #1: 98051613Dial Number #2: 98051629




PPP ProfilesAccount Name: Node100;CHAP Secret: 200_100C;Network Protocols: IPIPCP options: ADDR+VJLocal IP Address: 192.0.1.1Remote IP Address: 192.0.0.1Compression Control Protocol:PROPDial Number #1: 98059625Dial Number #2: 98050926Add Bandwidth Wait Time:10Remove Bandwidth Wait Time:10



Network Services Features TablePort/Station Identifier: LCON-1Data Compression Level: FORCE ON







Network Services Features TablePort/Station Identifier: LCON-1Data Compression Level: FORCE ON







Figure 38. Proprietary Compression



Synchronous Links in MultiLink PPP and IP over ISDN

Description In this example, a MultiLink PPP connection uses a permanent link between nodes 100 and 200. The permanent link can operate at speeds ranging from 16 Kbps to 256 Kbps although, at speeds of 64 Kbps or less, the propagation time of packets transmitted through the link is effected.The permanent link must be configured as a dedicated link in the PPP Profile. Since the permanent link is always associated with the same PPP Profile, the Authentication Protocol is defined by the PPP Profile. In this application, packets are configured as authentication clients so the dedicated links are not authenticated.The sunsetted Vanguard 320 and Vanguard 340/342 use the 5th SCC for ISDN D channel. This allocation permits a total of 2 ISDN B channels (only accessible by the CTP using Telnet) and 1 permanent serial link to be made available for a MultiLink PPP bundle.Only Node 200 is configured with a default gateway, therefore, only the PC on network 192.0.1.1 can initiate a call. Unnumbered IP interfaces are used to minimize the consumption of IP addresses.MultiLink PPP, uses the ISDN link as either:

• A dial backup when the permanent link fails.• Bandwidth on Demand.

Example Figure 39 shows you how to configure Vanguard 3400s to maintain synchronous links on a MP connection over BRI ISDN.




.

ISDN Channel *D Channel Port: 4Switch Type: NI-1*First B Channel Port 1(First) Access Type: CMD(First) Line Speed: 64K(First) SPID: 416805161300(First) Local Subscriber

Directory Number: 8051613*Second B Channel Port 2(Second) Access Type: CMD(Second) Line Speed: 64K(Second) SPID: 416805162900(Second) Local Subscriber


VG3400Node200

VG3400Node100 ISDN

Server

PC192.0.0.1

192.0.1.1

Port Record[1]*Port Type: PPP[1]*Line Interface: ISDN[2]*Port Type: PPP[2]*Line Interface: ISDN[3]*Port Type: PPP[3]*Line Interface: SYNC[3] Clock Source: INT[3] Clock Speed 8000[4]*Port Type: X25


PPP ProfilesAccount Name: Node100;CHAP Secret: 200_100C;Network Protocols: IPPCP options: ADDR+VJLocal IP Address: 192.0.1.1Remote IP Address: 192.0.0.1Dial Number #1: 98051825Dial Number #2: 98052366*Dedicated Links: PPP-3


Network Services PVC Table*Source: LCON-1*Destination: MLPPP-1




ISDN Channel *D Channel Port: 4Switch Type: NI-1*First B Channel Port 1(First) Access Type: CMD(First) Line Speed: 64K(First) SPID: 416805182500(First) Local Subscriber

Directory Number: 8051825*Second B Channel Port 2(Second) Access Type: CMD(Second) Line Speed: 64K(Second) SPID: 416805236600(Second) Local Subscriber


Port Record[1]*Port Type: PPP[1]*Line Interface: ISDN[2]*Port Type: PPP[2]*Line Interface: ISDN[3]*Port Type: PPP[3]*Line Interface: SYNC[3] Clock Source: EXT[3] Clock Speed 8000[4]*Port Type: X25

PPP ProfilesAccount Name: Node200;Network Protocols: IPPCP options: ADDR+VJLocal IP Address: 192.0.0.1Remote IP Address: 192.0.1.1Dial Number #1: 98051613Dial Number #2: 98051629*Dedicated Links: PPP-3


Network Services PVC Table*Source: LCON-1*Destination: MLPPP-1



IP Parameters*Internal IP Address: 192.0.0.1



Figure 39. MP IP Over ISDN



Asynchronous PPP, Windows 95 and Frame Relay

Description This example shows a permanent connection from a PC to a remote Router over Frame Relay.An IP connection over a serial port, using Windows 95, is available using it’s Dial-up Networking feature. Windows 95 assumes that it is connected to a modem supporting the AT command set. PPP works around this minor limitation by spoofing the AT dial sequence when configured as an asynchronous single link PPP port.

Example Figure 40 shows you how to configure Vanguards to establish an Asynchronous PPP connection so a Windows ‘95 workstation can use dial-up networking..

VG3400Node200

Frame

Server

PC

192.0.1.1

Port Record[2]*Port Type: PPP[2]*Line Interface: ASYNC[2] Clock Speed: 19200[2]*PPP Operation: Singlelink[2] Node Name Option: SHORT[2] Authentication Protocol:NONE[2] Networks Protocol: IP[2] IPCP options: ADDR+VJ[2] Local IP Address: 192.0.0.1[2] Remote IP Address: 192.0.0.2

[3]*Port Type: FRI[3]Clock Speed: 80000[3]Control Protocol Support:ANNEX_D

FRI Station*Station Type: BYPASSDLCI: 16Max Inbound Queue: 0

VG100PC* Relay

PVC Setup Table*Source: PPP*Destination: FRI-3S1

Port Record[3]*Port Type: FRI[3] Clock Source: INT[3]Clock Speed: 80000[3]Control Protocol Support:ANNEX_D

FRI Station*Station Type: BYPASSDLCI: 16Max Inbound Queue: 0

PVC Setup Table*Source: LCON-1*Destination: FRI-3S1



IP ParametersDefault Record


*Sunset Product

Figure 40. Asynchronous PPP, Windows 95, and Frame Relay




Asynchronous PPP Using AT Dialer

Description This example shows a PPP connection over a modem using the AT Dialer feature.

Example Figure 41 shows you how to configure Vanguards to establish an Asynchronous PPP connection over a modem using AT Dialer..

Port Record[1] *Port Type: PPP[1] *Line Interface: ASYNC[1] Connection Type: DIMOat[1] Flow control: HARDWARE[1] Primary Dial Number: 9,1-800-555-1234[1] Secondary Dial Number: 9,1-800-555-4321[1] Maximum Number of Retries: 3[1] Retry Interval: 30[1] Modem Initialize string:AT &F E0 X4 V1 &C1 &D2[1] Clock Speed: <baud rate>[1] Stop Bits: 1[1] *PPP Operation: Singlelink

PSTNPC1

PC2

User

ModemINT/EXT

AsyncPPP6800

Figure 41. Asynchronous PPP using AT Dialer

Port Configuration To enable the AT Dialer feature, configure the port as shown in Figure 41. For port record details, refer to the “PPP Port Record” section on page 97.

NoteAT Dialer supports only Single Link PPP.

Port Initialization During port initialization, the AT command entered in the Modem Initialize string is used to initialize the modem for dialing. Before dialing the number, the port sends the AT command configured in the Modem Initialize string to the modem. If the modem:

• is initialized successfully, it gives an OK response.• responds with an ERROR message or some other response, the port retries the

initialization based on the Maximum Number of Retries configured.• does not reply, the port times out and remains in INIT state. • response continues to fail after the specified number of retries, PPP discon-

nects and displays an error message.

Automatic Modem Initialization

When a modem is disconnected from the port or powered down, the port detects this change and sends the Modem Initialize string to the modem. It then follows the same initialize routine as mentioned above.



Dial Numbers At least one dial number (Primary or Secondary) must be configured for the modem to dial. Each phone number may have a maximum of 30 characters. Each number can be re-dialed up to the number configured in the Maximum Number of Retries. Retries are separated by the configured Retry Intervals. These input characters are supported:

Character Description0-9 numeric digits- group numbers (ignored)# used by telco, wait characterSPACE ignored

Incoming Call Figure 42 shows the sequence of events for an incoming call:

Raise RI lead

AckRaise DTR

Drop RIAck Raise DSR

Raise RTS

Raise CTSATA

CONNECT

Raise CD

Connected

Lower DTR & RTS

Lower DSR & CTS

Modem PPP

Figure 42. PPP Incoming Call




On ring detection the modem raises a ring indicator (RI) lead. PPP detects this change and waits for a RING message from the modem. PPP then raises a data terminal ready (DTR) and issues the command ATA to accept the call. The modem in turn drops the RI lead and raises a data set ready (DSR) to connect the call. Once the call is connected, the modem raises a data carrier direct (DCD). If DSR is not raised, then the port times out and lowers DTR. PPP waits for a request to send (RTS) and clear to send (CTS) indication before sending data.

NoteThe modem or PPP can disconnect the call by lowering either the DTR or DSR leads.

Outgoing Call Figure 43 shows the sequence of events for an outgoing call:

Raise DTR lead

AckRaise DSR

Raise RTS

Ack Raise CTS

Send AT

Send OK

Send phone#

Send ERROR

Connected

Lower DTR & CTS

Lower DSR & RTS

PPP Modem

retry#

Raise CD

Ack

Ack

Nack

send CONNECT

Figure 43. PPP Outgoing Call



PPP Outgoing Call PPP initiates an outgoing call by raising a DTR lead. The modem raises a DSR to indicate it is ready to receive commands. PPP sends an AT command to the modem to verify it is ready to receive. If the modem does not reply, a time out occurs. PPP sends the AT command again. The modem sends an OK. PPP receives the OK and waits (100ms) to send the first phone number from the port configuration.

NoteIf the PPP call fails to connect to the modem, it re-dials until the Retries parameter is reached for each dial number configured.




MultiLink PPP Over BRI

Description In this example, MultiLink PPP using an ISDN link provides Bandwidth on Demand. Node 200 is configured with bandwidth management parameters such that it is adding the additional ISDN link. Authentication is initiated by the node answering the call. The node initiating the call trusts the ISDN service provider always routes the call correctly to the desired destination.Node 200 is configured with a default gateway to Node 100. If your application requires Node 100 to initiate a call, a static route must be added for each remote network that needs to be accessed. Node 100 uses an LCON in a group configuration to minimize the consumption of IP addresses.

NoteVanguard 6520* and 6560* products use the ISDN channel record to associate a B channel to the PPP Port.*Vanguard 6520 and 6560 are sunset products.

Example Figure 44 shows how to configure a 6520* (Node 100) for MP over BRI ISDN.*Vanguard 6520 is a sunset product.

192.0.2.1 192.0.2.2VG312Node200

6520Node100 ISDN

Server

PC192.0.0.1 192.0.1.1

Port Record[19] Port Type: BRI[19] Switch Type: ETSI[19] TEI: 127[100] Port Type: PPP[100] Line Interface: ISDN[101] Port Type: PPP[101] Line Interface: ISDN

ISDN Channels[1] Local Subscriber Address: 4567894[1] Protocol Type: PPP[1] Virtual Port Number: 100[2] Local Subscriber Address: 7654398[2] Protocol Type: PPP[2] Virtual Port Number: 101

ISDN Channels*D Channel Port: 1Switch Type: ETSI*First B Channel Port: 2(First) Access Type: CMD(First) Line Speed: 64KSPID: 416712161300(First) Local Subscriber Directory Number: 7121613*Second B Channel Port: 3(Second) Access Type: CMD(Second) Line Speed: 64KSPID: 416712162900(Second) Local Subscriber Directory Number: 7121629

Port Record[1] Port Type: X25 [2] Port Type: PPP[2] Line Interface: ISDN[3] Port Type: PPP[3] Line Interface: ISDN

PPP ProfilesAccount Name: Node100;Authentication Protocol: CHAP_CCHAP Secret: 200_100C;Network Protocols: IPIPCP options: ADDR+VJLocal IP Address: 192.0.2.2Remote IP Address: 192.0.2.1Dial Number #1: 4567894Dial Number #2: 7654398Add Bandwidth Wait Time: 10Remove Bandwidth Wait Time: 10

PPP Profiles[1] Account Name: Node200;[1] CHAP Secret: 100_200C;[1] Network Protocols: IP[1] IPCP options: ADDR+VJ[1] Local IP Address: 192.0.2.1[1] Remote IP Address: 192.0.2.2Dial Number #1: 97121613Dial Number #2: 97121629[2] Account Name: Node300[2] Authentication Protocol:CHAP_C[2] CHAP Secret: 100_300C[2] Network Protocols: IP[2] IPCP options: ADDR+VJ[2] Local IP Address: 192.0.2.1[2] Remote IP Address: 192.0.2.3

PPP ParametersPPP Node Name: Node100;Authentication Protocol: CHAP_S

NUI/Password Table[1] Account Name: Node20;[1] Password: 200_100C;[2] Account Name: Node300;[2] Password: 300_100C;

LAN Connection Table[1] Lan Forwarder Type: ROUT[1] Lan Connection Type: GROUP[1] Router Interface Number:5[1] Encapsulation Type: RFC1294[1] Next Hop IP Address: 192.0.2.2[2] Lan Forwarder Type: ROUT[2] Lan Connection Type: GROUP[2] Router Interface Number:5[2] Encapsulation Type: RFC1294[2] Next Hop IP Address: 192.0.2.3

PVC Setup TableSource: LCON-1Destination: MLPPP-1Source: LCON-2Destination: MLPPP-2

Interfaces TableInterface #1 State: EnabledInterface #5 State: Enabled

IP ParametersDefault record

IP Interface Configuration Table[1] Interface Number: 1[1] IP Address : 192.0.0.1 [2] Interface Number: 5[2] IP Address : 192.0.2.1



IP Interface Configuration TableInterface Number: 1IP Address : 192.0.1.1 Interface Number: 5IP Address : 192.0.2.2


IP ParametersDefault Gateway: 192.0.2.1


BitSurfrNode 300192.0.2.3



Figure 44. MultiLink PPP Over BRI ISDN




MultiLink PPP Over PRI

Description In this example, MultiLink PPP using an ISDN link provides Bandwidth on Demand. Node 200 is configured with bandwidth management parameters such that it is adding the additional ISDN link. Authentication is initiated by the node answering the call. The node initiating the call trusts the ISDN service provider always routes the call correctly to the desired destination.Node 200 is configured with a default gateway to Node 100. If your application requires Node 100 to initiate a call, a static route must be added for each remote network that needs to be accessed. Node 100 uses an LCON in a group configuration to minimize the consumption of IP addresses.

NoteThe Vanguard 6520* uses the Virtual Port Mapping Table to associate a B channel to the PPP Port.*Vanguard 6520 is a sunset product.

Example Figure 45 shows how to configure a 6560* (Node 100) for MP over PRI ISDN.*Vanguard 6520 is a sunset product.

192.0.2.1 192.0.2.2VG320Node200

6400Node100 ISDN

Server

PC192.0.0.1 192.0.1.1

ISDN ChannelsD Channel Port: 1Switch Type: ETSIFirst B Channel Port: 2(First) Access Type: CMD(First) Line Speed: 64KSPID: 416805161300(First) Local Subscriber

Directory Number: 8051613Second B Channel Port: 3(Second) Access Type: CMD(Second) Line Speed: 64KSPID: 416805162900(Second) Local Subscriber

Directory Number: 8051629Port Record[1] Port Type: X25 [2] Port Type: PPP[2] Line Interface: ISDN[3] Port Type: PPP[3] Line Interface: ISDN

PPP ProfilesAccount Name: Node100;Authentication Protocol: CHAP_CCHAP Secret: 200_100C;Network Protocols: IPIPCP options: ADDR+VJLocal IP Address: 192.0.2.2Remote IP Address: 192.0.2.1Dial Number #1: 4567894Dial Number #2: 7654398Add Bandwidth Wait Time: 10Remove Bandwidth Wait Time: 10



IP Interface Configuration TableInterface Number: 1IP Address : 192.0.1.1 Interface Number: 5IP Address : 192.0.2.2


IP ParametersDefault Gateway: 192.0.2.1


PRI Table Entry[1]*Port Type: SWITCHED-DATA[1]*Virtual Port Number: 100[1]*Physical T1/E1 Port Number: 49[1]*DSO Rate: 56K[1]*Local Subscriber Address:5084567894[1]*Network Specific Call Feature:None[1]*Calling/Called Party Number Type:National[1]*Calling/Called Party Number Plan:ISDN

[2]*Virtual Port Number: 101[2]*Physical T1/E1 Port Number: 49[2]*DSO Rate: 56K[2]*Local Subscriber Address:5087654398[2]*Network Specific Call Feature:None[2]*Calling/Called Party Number Type:National[2]*Calling/Called Party Number Plan:ISDN

BitSurferNode 300

Port Record[100] Port Type: PPP[100] Line Interface: ISDN[101] Port Type: PPP]101] Line Interface: ISDN

PPP ProfilesAccount Name: Node200;CHAP Secret: 100_200C;Network Protocols: IPIPCP options: ADDR+VJLocal IP Address: 192.0.2.1Remote IP Address: 192.0.2.2Dial Number #1: 8051613Dial Number #2: 8051629Account Name: Node300;Authentication Protocol: CHAP_CCHAP Secret: 100_300C;Network Protocols: IPIPCP options: ADDR+VJLocal IP Address: 192.0.2.1Remote IP Address: 192.0.2.3


NUI/Password TableAccount Name: Node200;Password: 200_100C;Account Name: Node300;Password: 300_100C;

LAN Connection TableLan Forwarder Type: ROUTLan Connection Type: GROUPRouter Interface Number: 5Encapsulation Type: RFC1294Next Hop IP Address: 192.0.2.2Lan Forwarder Type: ROUTLan Connection Type: GROUPRouter Interface Number: 5Encapsulation Type: RFC1294Next Hop IP Address: 192.0.2.3PVC Setup Table

Source: LCON-1Destination: MLPPP-1Source: LCON-2Destination: MLPPP-2

Interfaces TableInterface #1 State: EnabledInterface #5 State: Enabled IP Parameters

Default record

IP Interface Configuration Table[1] Interface Number: 1[1] IP Address : 192.0.0.1 [2] Interface Number: 5[2] IP Address : 192.0.2.1

T1 /E1

Virtual Mapping



Figure 45. MultiLink PPP Over PRI



Cascading Configuration


Introduction Release 6.4 and greater supports Cascading Configuration (CCFG) through the Control Terminal Port (CTP). Cascading Configuration is designed to make the configuration of (ML) PPPo(X) features easier. Cascading configuration allows configuration of related items in sequence (without having to navigate through menus). For example, after configuring a PPP port with the interface type of FRI, the configuration for FRI port stations can be available to the user right after the PPP configuration (avoiding navigation through the CTP menu again).

Stacking (XoY) Release 6.4 and greater supports the architectural model where one protocol stack, X, encapsulates traffic over another protocol stack, Y. In a X over Y model (XoY), participating entities (modules, stacks) can belong to two adjacent or the same hierarchical level. Stacking is based on two new components, Stack socket and Stack Registry (STACKREG). Stack registry is a node wide module with the main role to assist in synchronization of dynamically booted and created entities. Alarms are generated by the STACKREG module.

Cascading Configuration Example

Cascading configuration example: PPPoFRLines in bold are prompts and warnings generated by CCFG.

Case 1: Configure All items

Port Number: 100/100[100] *Port Type: NULL/ppp[100] *Line Interface: ASYNC/fri[100] *Interface Identifier: (blank)/fri-1s1;[100] *PPP Operation: Multilink/;FRI line interface specified (fri-1s1).Would you like to configure fri-1 now? (y/n) y

[1] *Port Type: FRI/[1] Connection Type: SIMP/;Would you like to configure fri-1s1 now? (y/n) y

[1] *Station Type: ANNEX_G/bypass[1] *Station Circuit Type: PVC/[1] DLCI: 16/;



Case 2: Do Not Want to Configure FRI Port but it Doesn't Exist

Port Number: 100/100[100] *Port Type: NULL/ppp[100] *Line Interface: ASYNC/fri[100] *Interface Identifier: (blank)/fri-1s1;[100] *PPP Operation: Multilink/;

FRI line interface specified (fri-1s1).Would you like to configure fri-1 now? (y/n) nWARNING: fri-1 does not exist. Please configure for correct operation.

Case 3: Do Not Want to Configure FRI Port and it Already Exists

Port Number: 100/100[100] *Port Type: NULL/ppp[100] *Line Interface: ASYNC/fri[100] *Interface Identifier: (blank)/fri-1s1;[100] *PPP Operation: Multilink/;

FRI line interface specified (fri-1s1).fri-1 already configuredWould you like to configure fri-1 now? (y/n) n

fri-1s1 already configuredWould you like to configure fri-1s1 now? (y/n) y

[1] *Station Type: ANNEX_G/bypass[1] *Station Circuit Type: PVC/[1] DLCI: 16/;

The following table explains the cascading configuration sequence:

Step Procedure1 The user, through CTP menu interface, initiates the configuration of X..2 Control transfers to X which uses CTP table handling functions to per-

form X configuration.3 X sends request of configuration of a Y to CCFG.4 CCFG matches the type of Y to the function hook for configuration in its

database and invokes it to check for existence and configuration of the port.




5 Control transfers to Y, which uses CTP table handling functions to per-form Y configuration (if doesn't already exist or user requests it).

6 After Y configuration finishes, control reverts back to X and X sends request of configuration of Y station to CCFG.

7 CCFG matches the type of Y to the function hook for configuration in its database and invokes it to check for existence and configuration of the station.

8 Control transfers to Y, which uses CTP table handling functions to per-form Y station configuration (if doesn't already exist or user requests it).

9 After Y station configuration finishes, control reverts back to X and since X is finished, back up to CTP.

Step Procedure



Figure 46. Cascading Configuration Event/Control Flow



Configuring Point-to Point Protocol over Ethernet (PPPoE) Connections


Node Record Configuration

To configure Point-to-Point Protocol over Ethernet the PPP parameter, Line Interface, must be set to Ethernet. Figure 47 shows a Node Record configuration example and Figure 48 shows the Line Interface parameter set to ETH. Additional PPPoE parameters can be found on “PPPoE Parameters” section on page 113.

Node Name: nodename/ <--------------------------------------------

Node Address: 100/ Node Number: 100/ . . . *Outbound Call Translation Table Size: 64/ GSC Call Rate (Number of Calls per Sec.): 0/ Expanded Node Name: long_node_name/ <--------------------------- Call Redirection diagnostic code: BB/ Alarm Throttling: Disabled/

Figure 47. Node Record Configuration

NoteItems indicated by “<----” need to be set to the user name as provided by the Internet Service Provider (ISP). If the username is longer than eight characters, the Expanded Node Name needs to be set. If the username is shorter than eight characters, just the Node Name setting is sufficient. (See Node Name Option in PPP Port Configuration ).

PPP Port Configuration

Figure 48 shows a PPP Port configuration example:

Port Number: 1/100 [100] *Port Type: PPP/ [100] *Line Interface: ETH/ [100] Node Name Option: SHORT/ [100] Authentication Protocol: PAP_C/ [100] Client Password/Secret: password/ [100] Network Protocols: IP/ [100] IPCP options: ADDR/ [100] Local IP Address: 0.0.0.0/ [100] Remote IP Address: 0.0.0.0/ [100] Encapsulation: RFC1490/ [100] Auto Connect: Enabled/

after accepting the port configuration settings, PPPoE parameters will be asked for:

Configure PPPoE parameters: [100] *Ethernet Port Number: 5/ [100] Access Concentrator Name: (blank)/ [100] Service Name: (blank)/

Set toEthernet

Figure 48. PPP Port Configuration



NotePPPoE configuration procedures:• PPP port for PPPoE usage must be configured as a virtual port.• Node Name Option should be set to LONG if the username is longer than

eight characters. Setting Node Name to LONG causes the Expanded Node Name to be used instead of the normal Node Name. Both Expanded Node Name and Node Name are configured in Node Record Configuration.

• Access Concentrator Name and Service Name can be left blank to connect to any server. Specifying a value causes PPPoE to only connect to servers that match the corresponding Access Concentrator and or Service Name.

Ethernet Port Configuration

Ethernet Port Configurations can use default settings.

LAN Connection Configuration

LAN Connection Configurations can use default settings except for the Router Interface Number, which should correspond to the Router Interface being used.

Router Interface Configuration

Router Interface Configuration default settings can be used except for the IP Address, IP Address Mask, and the Interface Number settings. The Interface Number is the Router Interface number being configured and should match the Router Interface Number in the LAN Connection configuration. If the dynamic address negotiation is required, the IP Address should be set to unnumbered IP interface which is 0.0.0.N (where N is the Router Interface Number - 1). Example: If the Router Interface Number is 5, the IP Address should be set to 0.0.0.4.

PVC Setup Table configuration

Figure 49 shows a PVC Table configuration example:

Entry Number: 1/ [1] *Source: lcon-1/ [1] *Destination: ppp-100/

Figure 49. PVC Setup Table Configuration




NAT Parameters Configuration

In general, for PPPoE application, NAT will be used to share the interface with more than one devices. Figure 50 shows a NAT configuration example:

Configure NAT Parameters

NAT: Enabled/ Internal Interfaces: 2/ Config Type: Advanced/ NAT Debugging: Disabled/ Bind Idle Timeout: 60/ UDP Idle Timeout: 60/ TCP Idle Timeout: 60/ Enable Translators: FTP+ICMP+DNS/ SESSION Idle Timeout: 15/ NAPT Port Range: 6000 - 7000/ RIP Advertisement: Enabled/

Figure 50. NAT Configuration

NoteInternal Interfaces are the Router Interface numbers that are connected to the local network.Enable Translators is used to activate translation of various protocols. Currently only FTP, ICMP, and DNS are available and by default only FTP is enabled.

NAT Translation Table Configuration

Figure 51 shows a NAT Translation Table configuration example:

Configure NAT Translation Table

Entry Number: 1/ [1] External Interface Numbers: 5/ [1] External Address Type: DYNAMIC/ [1] Binding Type: NAPT/ [1] Internal Address Range: 192.168.0.0-192.168.255.255/ [1] Overlap: Disabled/

Figure 51. NAT Translation Table Configuration

NoteExternal Interfaces is the Router Interface number that is connected to the WAN network (the one connected to DSL modem).


Configuring PPP Connections


Introduction The parameters for PPP connection appear in three records:• PPP Port • PPP Parameters• PPP Profile

The PPP Profile record is only used to configure MultiLink connections.

NoteAny Vanguard 6520* or 6560 PPP* Port that is configured for ISDN, can only operate in MultiLink mode. This does not prohibit PPP from operating with one link, however, it is a configuration requirement that these parameters be configured when defining a connection.*Vanguard 6520 is a sunset product.

For more information on configuring Single Link and MultiLink connections, see the “Link Methods” section on page 57. For more information on configuring PAP or CHAP authentication, see “Authentication Methods” section on page 64.

NotePrior to Release 4.97 (or Release 5.0 for 6560), the PPP Port configuration allowed explicit configuration of Protocol Field Compression, Address/Control Field Compression, and Asynchronous Control Character Map. With Release 5.0, negotiation of these options are initiated with the peer. Also, the parameter MRU has been replaced with the Node Record parameter Max Frame Size.




PPP Port Record

Navigating the CTP Menu

Figure 52 shows the CTP path to the PPP Port Record parameters.

Node: Address: Date: Time: Menu: Main Path: (Main)

LogoutExamine

•••

Configure

NodePort

Port Number Port Type Stacking SupportStack Connection IdentifierStacking ModeStack Encapsulation*Line Interface Connection Type Flow Control Primary Dial NumberSecondary Dial NumberMaximum Number of RetriesRetry IntervalModem Initialize StringClock Source Clock Speed Stop Bits *PPP Operation *Maximum Number of Config Request AttemptsMLP MulticlassMaximum Number of Receiver Suspension ClassesInitial BandwidthNode Name OptionDebug OptionAuthentication Protocol Client Password/Secret Network Protocols IPCP Options Local IP Address Remote IP Address IPXCP Options Node Number Network Number Encapsulation TypeIdle Disconnect Timer

Figure 52. PPP Port Parameters



Parameters When you configure a PPP port, the following parameters appear:

Port Number Range: Contingent on platform.Default: n/aDescription: Specifies the number of the port which you are configuring.

Port Type Range: Contingent on software image.Default: n/aDescription: Specifies the type of port. For this software option, enter PPP.

Stacking SupportRange: NONE, DOWN, (UP, BOTH)Default: NONEDescription: This parameter specifies whether protocol stacking support is

enabled for the UP (to the layer above) and/or DOWN (to the layer below) connection. For multilink operation, only DOWN or NONE is supported. (For singlelink operation, UP and BOTH options are reserved for future use and will not be available for configuration. Currently, UP or BOTH is not configurable. In the future, if UP or BOTH are configured for multilink, NONE or DOWN respectively will be used instead.) For PPPoFR or PPPoA, the stack connection would connect to the FRI or ATM station.

This parameter needs to be set to DOWN (or BOTH) to support PPP over Frame Relay and PPP over ATM applications.-This parameter only appears for virtual ports.

Stack Connection IdentifierRange: 0 to 32 alphanumeric charactersDefault: blankDescription: This parameter specifies the destination identifier for the DOWN

connection when the Stacking Support is enabled.For example: fri-1s1

This parameter appears only if the Interface Stacking Support is set to DOWN (or BOTH).

Stacking ModeRange: NORMAL, PPPOEDefault: NORMALDescription: This parameter specifies the stacking mode:

NORMAL - Normal interface mode (for PPPoFR or PPPoA)PPPOE - PPPoE interface type used for PPPoEoA only

This parameter appears only if the Stacking Support is set to DOWN or BOTH.




Note

Note

Note

Stack EncapsulationRange: NONE, RFC1294, RFC1483_LLC_SNAP, RFC1483_VC_MUXDefault: NONEDescription: This parameter specifies the data encapsulation type used over the

DOWN connection. • NONE - No Encapsulation. • RFC1294 - RFC 1294 Multiprotocol Encapsulation.

(PPPoFR) • RFC1483_LLC_SNAP - RFC 1483 LLC/SNAP

Encapsulation. (PPPoA or PPPoEoA) • RFC1483_VC_MUX - RFC 1483 VC Based Multiplexing

Encapsulation. (PPPoA or PPPoEoA)

This parameter appears only if the Stacking Support is set to DOWN (or BOTH). -This encapsulation is different from the encapsulation set in the LCON configuration. The LCON encapsulation is only used internal to the node and is removed by PPP before processing. The encapsulation is used externally and is part of the data sent to the peer.



Note

*Line Interface Range:Range 7300:

ASYNC, SYNC, ISDN, T1E1, ETHSYNC, ISDN, T1E1, ETH(Do not use ASYNC on the 7300 Series)

Default: ASYNC SYNC for the 7300 Series

Description: Specifies the line interface type. The line interface is the physical interface on a port. Each physical interface looks for different signals to come from the port. Choose one of the following options:

• ASYNC: Serial Asynchronous line interface (do not use on the 7300 Series)

• SYNC: Serial Bit Oriented Synchronous line interface• ISDN: ISDN line interface• T1E1: Channelized T1E1 interface• ETH: Ethernet interface (PPPoE)

This parameter only appears if Stacking Support is set to NONE (or UP).

Do not use ASYNC on the 7300 Series Platform. Perform a Node boot to have changes to this parameter take effect.

Connection Type Range: SIMP, DTR, DIMO, DIMOatDefault: SIMPDescription: Specifies the control signal handshake and clocking required for a

connection to be made to this port:• SIMP: Simple, no control signals required• DTR: Dedicated, requires the data terminal ready signal

(DTR)• DIMO: Port handshakes with the attached dial modem• DIMOat: async modem connection (Flow control must be

Hardware)

This parameter appears only when Line Interface is ASYNC or SYNC. Perform a Port boot to have changes to this parameter take effect.




Note

Note

Note

Flow Control Range: NONE, HARDWAREDefault: NONEDescription: Specifies the type of flow control:

• NONE: No flow control• HARDWARE: Flow control using EIA signals

This parameter appears only when the Line Interface is ASYNC. Perform a Port boot to have changes to this parameter take effect.

Primary Dial NumberRange: 0 to 31 alphanumeric characters. Use the space bar to blank field. Default: (blank)Description: Specifies the telephone number for the modem to dial when

connection type is DIMOat. Maximum allowable size is 30 characters. Usable characters are: digits 0-9 #, - space. Example: 9,1-800-555-1234

Perform a Port boot to have changes to this parameter take effect.

Secondary Dial NumberRange: 0 to 31 alphanumeric characters. Use the space bar to blank field. Default: (blank)Description: Specifies the telephone number for the modem to dial when

connection type is DIMOat. Maximum allowable size is 30 characters. Usable characters are: digits 0-9 #, - space. Example: 9,1-800-555-1234


Maximum Number of RetriesRange: 1 to 5 Default: 3Description: Specifies the maximum retries per dial number.

This parameter appears only when the Connection Type is DIMOat. Perform a Port boot to have changes to this parameter take effect.



Note

Note

Note

Note

Retry IntervalRange: 5 to 120 Default: 30Description: Specifies the delay in seconds before re-dealing the number.


Modem Initialize StringRange: 0 to 50 alphanumeric characters. Use the space bar to blank field.Default: AT &F E0 X4 V1 &C1 &D2 Description: Specifies the initialize string for the dial modem. This parameter

must begin with AT.





NotePlease consult your modem’s manual and adjust the default initialization string to your required settings. Flow control must be set to RTS/CTS, this is usually the default for most modems. For example, the RTS/CTS Flow Control parameter for the 3460 Fast’R Modem is *FL3. The new initialization string for configuration would be AT &F E0 X4 V1 &C1 &D2 *FL3.

Clock Source Range: INT, EXTDefault: EXTDescription: Specifies the clock source:

• INT: Internal clock source• EXT: External clock source

This parameter appears only when Line Interface is SYNC. Perform a Port boot to have changes to this parameter take effect.

Note

Note

Note

Clock Speed Range: 1200 to 2048000 for SYNC

50 to 19200 for ASYNCDefault: 9600Description: Specifies the speed of the port in bits per second (baud rate). The

hardware configuration determines the physical limitations of the clock speed.

This parameter appears only when Line Interface is ASYNC or SYNC. Perform a Port boot to have changes to this parameter take effect.

Stop Bits Range: 1, 1.5, 2Default: 1Description: Specifies the number of stop bits:

• 1: 1 stop bit• 1.5 : 1.5 stop bits• 2: 2 stop bits

This parameter appears only when Line Interface is ASYNC. Perform a Port boot to have changes to this parameter take effect.

*PPP Operation Range: Singlelink, MultilinkDefault: MultilinkDescription: Determines if the link negotiates for MultiLink operation.

• Singlelink: The link is not used in a MultiLink operation.• Multilink: The link is negotiates MultiLink operation in both

directions. If the remote device attempts to negotiate to non-MultiLink operation in either direction, the MultiLink procedure does not occur.

Perform a Node boot to have changes to this parameter take effect.



Note

Note

Note

*Maximum Number of Config Request AttemptsRange: 0 to 32767Default: 10Description: This is the maximum number of Config Request sending attempts

that are made:• 0 - Unlimited attempts• 1 to 32767 - The node sends Config Request before this

number is exhausted.

When PPP Operation is Multilink, the remaining parameters in this record do not appear. Perform a Node boot to have changes to this parameter take effect.

MLP MulticlassRange: Enabled, DisabledDefault: DisabledDescription: This parameter specifies whether multiclass support shall be nego-

tiated. When it is enabled, it indicates to the peer that this port wishes to support multiclass suspension. It sends a request to the peer using configured numbers for suspension levels during negoti-ation. This parameter does not effect transmission. If the peer wishes to support multiclass its request is always accepted.

Perform a port boot to have changes to this parameter take effect.

Maximum Number of Receiver Suspension ClassesRange: 2, 4, 8, 16Default: 4Description: This parameter specifies the maximum number of suspension

classes this port wishes to receive. If the peer requires less then this parameter, the smaller number is accepted. Perform a port boot to have changes to this parameter take effect.

This parameter appears only when Multiclass is enabled.




Note

Note

Note

Initial BandwidthRange: 50 to 2048000 (Vanguard 320, 34x, 6435/55

50 to 8192000 (Vanguard 7300 Series)Default: 64Description: This parameter specifies bandwidth to be assumed for the port

when the true port speed is not available (this can occur for short time during and after initialization of the port). It is important to set this parameter to correct value of the remote or local clock source. Perform a port boot to have changes to this parameter take effect.

This parameter appears only when Multilink is enabled..

Node Name OptionRange: Short, LongDefault: ShortDescription: If configured as single link, these are the two node names that can

be used for authentication:• Short - The node name (up to 8 characters) are selected.• Long - The Expanded Node Name (up to 64 characters) are

selected. The Expanded Node Name in the Node Record must be configured.

Debug OptionRange: NONE, LCPDefault: NONEDescription: Enabling "LCP" turns on debug messaging to trace the link control

protocol negotiation.



Note

Authentication Protocol Range: NONE, PAP_S, CHAP_S, PAP_C, CHAP_CDefault: CHAP_SDescription: Specifies the authentication method for the server to negotiate.

Use the plus sign (+) to combine options:This node can act as an authenticator (Server) and/or peer (Client). If both PAP and CHAP are specified, then negotiation of CHAP is attempted first. NUI Table entries are used by the authentication server. The Password/Secret is used by the client.

• NONE: No authentication is provided.• PAP_S: Password Authentication Protocol server. The remote

device must send a user ID and Password.• CHAP_S: Challenge Authentication Protocol server. The

remote device must respond to the challenge.• PAP_C: Password Authentication Protocol client. This device

sends a user ID and Password (if requested).• CHAP_C: Challenge Authentication Protocol Client. This

device must respond to the challenge.

This parameter appears only when PPP Operation is Singlelink. Perform a Port boot to have changes to this parameter take effect.

Specify combinations of the above by summing (for example, CHAP_S+PAP_S).




Note

Note

Client Password/Secret Range: 0 to 32 alphanumeric characters. Use the space bar to blank field.Default: (blank)Description: Specifies use of the PPP Password for Authentication. Use any

character including a semicolon ( ; ) in the string. When terminating the string with a semicolon, precede it with a backslash ( \ ).Example: hello\; = hello;This parameter appears when the parameter Authentication Protocol is PAP_C or CHAP_C and when PPP Operation is Singlelink.


Network Protocols Range: NONE, IP, IPXDefault: IP+IPXDescription: Specifies the network protocols supported on this port.

• IP: IP protocol• IPX: Novell IPX • Bridging

This parameter appears only when PPP Operation is Singlelink. Perform a Port boot to have changes to this parameter take effect.

Specify combinations of the above by summing (for example, IP+IPX).



Note

Note

Note

IPCP Options Range: NONE, ADDR, VJDefault: VJDescription: Specifies the IPCP option.

• NONE: Disables all options.• ADDR: Enables IP address negotiation.• VJ: Enables Van Jacobson compression.

This parameter appears only if Network Protocols is IP and if PPP Operation is Singlelink. Perform a Port boot to have changes to this parameter take effect.

Specify combinations of the above by summing (for example, ADDR+VJ).

Local IP Address Range: A valid IP address in dotted notation.Default: 0.0.0.0Description: Specifies a local IP address used during IP address negotiation.

This parameter appears only if IPCP Options is ADDR and if PPP Operation is Singlelink. Perform a Port boot to have changes to this parameter take effect.

Remote IP Address Range: A valid IP address in dotted notation.Default: 0.0.0.0Description: Specifies a remote IP address used during IP address negotiation.

This parameter appears only if IPCP Options is ADDR and if PPP Operation is Singlelink. Perform a Port boot to have changes to this parameter take effect.




Note

Note

Note

Note

IPXCP Options Range: NONE, NODE, NETDefault: NONEDescription: Specifies IPCXP option:

• NONE: No option is enabled.• NODE: Enables node number negotiation.• NET: Enables network number negotiation.

Enter Node + Net to enable both.

This parameter appears only if Network Protocols is IPX and if PPP Operations is Singlelink. Perform a Port boot to have changes to this parameter take effect.

Node Number Range: 1 to 12 hexadecimal digits.Default: 0Description: Specifies a local IPX node number.

This parameter appears only if IPXCP Options is NODE and if PPP Operation is Singlelink.

Network Number Range: 1 to 8 hexadecimal digits. Default: 0Description: Specifies the network number used during network number

negotiation.

This parameter appears only if IPXCP Options is NET and if PPP Operation is Singlelink. Perform a Port boot to have changes to this parameter take effect.



Note

Note

Note

Encapsulation Type Range: PPP, RFC1490Default: RFC1490Description: Specifies the encapsulation used for internal adjacent connection

between PPP and other entities (LAN Connection Table, FRI bypass station, X.25 port, and so forth). Typically, this encapsulation is RFC1490.

• PPP: PPP encapsulation• RFC1490: RFC1490 encapsulation

This parameter appears only if the Line Interface is ASYNC and if PPP Operation is Singlelink. Perform a Port boot to have changes to this parameter take effect.

Compression Control Protocol Range: NONE, PROPDefault: NONEDescription: Specifies the compression protocol for this port. Configure this

parameter consistently with the compression option in the Network Services Feature Table.

• NONE: No data compression is enabled.• PROP: Vanguard Proprietary Data Compression is enabled.

This parameter appears only if Line Interface is SYNC or ISDN and if PPP Operation is Singlelink. Perform a Port boot to have changes to this parameter take effect.




Note

Note

Idle Disconnect Timer Range: 0 to 3200Default: 100Description: Specifies the time (in seconds) that the outgoing link must be idle

for automatic disconnection to occur. The timer is NOT restarted by inbound packets. The link will be terminated if inbound only traffic lasts longer than the specified timeout value. Any value above 0 enables Dial on Demand, where a call is initiated upon the arrival of application data. To disable this feature, set to 0 (zero)

• 1 to 3200: Enables Dial on Demand, where an ISDN call is initiated upon the arrival of application data.

• 0: Disables this feature.

This parameter appears only if Line Interface is SYNC or ISDN and if PPP Operation is Singlelink. Perform a Port boot to have changes to this parameter take effect.PPP Profile Record This parameter specifies the time, in seconds, that the outgoing link must be idle for automatic disconnection. The timer is NOT restarted by inbound packets. Link will be terminated if inbound only traffic lasts longer then the specified timeout value. To disable this feature, set it to 0. PPP Port Record This parameter specifies the time, in seconds, that the outgoing link must be idle for automatic disconnection. The timer is NOT restarted by inbound packets. Link will be terminated if inbound only traffic lasts longer then the specified timeout value. Any value above 0 enables Dial On Demand, where a call is initiated upon the arrival of application data. To disable this feature, set it to 0.



Note




PPPoE Parameters When the range on the parameter Line Interface is set to Ethernet, the following parameters appear on the PPPoE configuration.

Ethernet Port NumberRange: Valid port numbersDefault: 5

101 for the Vanguard 7300 SeriesDescription: Specifies the Ethernet port that this PPPoE session is associated to.

This parameter does not appear if stacking support is set to DOWN (or BOTH) for the PPP port.

Perform a port boot for changes to this parameter to take effect.

AC NameRange: 0 to 64 alphanumeric charactersDefault: (blank)Description: Specifies the Access Concentrator (AC) identification. It must

match the string in AC-Name tag, sent in the PADO packet, by the service provider. When no string is specified (blank), the first Access Concentrator responding with PADO packet is accepted.

This parameter appears for PPPoE configuration, only if the range on the parameter Line Interface is set to Ethernet.


Note

Note

Note

Note

Service NameRange: 0 to 64 alphanumeric charactersDefault: (blank)Description: Specifies the service identification. The string is sent to the service

provider in the PADI packet requesting certain types of service. It must be identical to the Service Name tag provided by the AC. When no string is specified (blank), any service specified by the service provider is accepted.



MAC AddressRange: Valid MAC Address or blankDefault: (blank)Description: This parameter specifies the MAC Address to use for PPPoE.

This parameter is required, there is not a physical Ethernet port associated with PPPoEoA. If the parameter is left blank, it will be generated internally using method similar to the following: 02-08-D5-XX-XX-XX where XX-XX-XX will be some unique identifier taken from the node, such as the serial number.

This parameter does not appear if stacking support is set to NONE (or UP) for the PPP port.

Auto ConnectRange: Enable, DisabledDefault: DisabledDescription: Specifies when a PPPoE session starts and terminates.

Enabled - PPPoE session starts after the port boot and lasts as long as the port is up.Disabled - PPPoE session is established when there is a need for a connection and terminates after the Idle Disconnect period.





Note

Note

Note

Note

Note




FRI Station Configuration Parameters

The following parameter appears on the FRI Station:

Stacking SupportRange: Enabled, DisabledDefault: DisabledDescription: This parameter specifies whether protocol stacking support is

enabled to receive stack connection requests. In the case of PPPoFR, this allows FRI station to receive stack connection request initiated by PPP.

This parameter needs to be enabled to support PPP over Frame Relay application. This parameter only appears for Bypass station

.

ATM Station Configuration Parameters

The following parameter appears on the ATM (AAM) Station:

Stacking SupportRange: Enabled, DisabledDefault: DisabledDescription: This parameter specifies whether protocol stacking support is

enabled to receive stack connection requests. In the case of PPPoA, this allows AAM station to receive stack connection request initiated by PPP.

This parameter needs to be enabled to support PPP over ATM application.

Note

Note



PPP Parameters Record


Figure 53 shows the CTP path to the PPP parameters.

Node: Address: Date: Time: Menu: Main Path: (Main)

LogoutExamine

•••

Configure

NodePort

•••

PPP Parameters

PPP Node NameAuthentication ProtocolPAP Password

Figure 53. PPP Parameters

Parameters These parameters are in the PPP Parameters Record:

PPP Node Name Range: 1 to 64 alphanumeric characters. Use the space bar to blank this

parameter.Default: NewDescription: Specifies the PPP Name that identifies the node during CHAP and

PAP procedures. Use any character including a semicolon ( ; ) in the string. When terminating the string with a semicolon, precede it with a backslash ( \ ).Example: hello\; = hello;

Perform a PPP Parameters and Profiles boot to have changes to this parameter take effect.

Note

Authentication Protocol Range: PAP_S, CHAP_S, PAP_C, CHAP_CDefault: CHAP_SDescription: Specifies the authentication method used on all dial-in links. Use

the plus sign (+) to combine options:This node can act as an authenticator (Server) and/or peer (Client). If both PAP and CHAP are specified, then negotiation of CHAP is attempted first. NUI Table entries are used by the Authentication Server. The authentication client uses either the Profile’s CHAP Secret or the PPP Parameter’s PAP Password.

• NONE: No authentication is required.• PAP_S: Password Authentication Protocol server. The remote

device must send a user ID and Password.• CHAP_S: Challenge Authentication Protocol server. The

remote device must respond to the challenge.• PAP_C: Password Authentication Protocol Client. This device



Specify combinations of the above by summing (for example, CHAP+PAP_C). Perform a PPP Parameters and Profiles boot to have changes to this parameter take effect.

PAP Password Range: 0 to 32 alphanumeric charactersDefault: RemoteDescription: Specifies the PPP Password for Authentication. When the node is

configured and negotiated as an authentication peer, this Password is sent to any PAP authenticators via a bundles member link. Use any character including a semicolon ( ; ) in the string. When terminating the string with a semicolon, precede it with a backslash ( \ ).Example: hello\; = hello;

Perform a PPP Parameters and Profiles boot to have changes to this parameter take effect.




Note

Note



PPP Profile Record


Figure 54 shows the CTP path to the PPP Profile parameters.

Entry NumberAccount NameAuthentication ProtocolCHAP SecretNetwork ProtocolsIPCP optionsTCP header compression max slot index Local IP AddressRemote IP AddressIPXCP optionsNode numberNetwork numberEncapsulationCompression Control ProtocolDial Number #1Dedicated LinksMaximum Number of Switched LinksTx CIR K bit/sec rate (when none zero) Add Bandwidth ThresholdAdd Bandwidth Wait TimeRemove Bandwidth Wait TimeIdle Disconnect TimerAuto Connect: DisabledPriority (Prioritization)Maximum Serialization Delay When Voice is PresentMaximum Serialization Delay When Voice is Not PresentMinimum Segment SizeRX Queue SizeTX Queue Size Suspendable clases 0-4TX Queue Size Suspendable clases 5-9TX Queue Size Suspendable clases 10-14Reassembly Timeout (Class Out/In)Driver Buffer LimitIPCP DebugIPHC Debug

Node: Address: Date: Time:Menu: Main Path: (Main)

LogoutExamine

•••

Configure

NodePort

•••

PPP Profiles

Figure 54. PPP Profile Parameters




Parameters These parameters are in the PPP Profile Record:

NoteUnless otherwise indicated, a PPP Profiles and Parameters boot must be performed for changes to parameters to take effect.

Entry NumberRange:Range - 7300:

1-600Vanguard 7300 Series maximum Multilink PPP Profiles Size has been increased from 600 to 1,000 with release 6.0.P02B and greater.

Default: 1Description: Specifies the entry number used to reference this table record.

NoteVanguard 320, 34x, 6435, and 6455 Maximum number of profiles is 60. A Vanguard 7300 Series platform is 1,000.

Account Name Range: 1 to 64 alphanumeric characters. Use the space bar to blank this

parameter.Default: NewDescription: Specifies the PPP Name for Identification. Use any character

including a semicolon ( ; ) in the string. When terminating the string with a semicolon, precede it with a backslash ( \ ).Example: hello\; = hello;

Authentication Protocol Range: NONE, PAP_S, CHAP_S, PAP_C, CHAP_CDefault: CHAP_CDescription: Specifies the authentication method for the server to negotiate.

Use the plus sign (+) to combine options:This node can function as an authentication (Server) and/or peer (Client). If you specify both PAP and CHAP, then negotiation of CHAP is attempted first. The Authentication Server uses NUI Table entries. The Authentication Client uses either the Profile’s CHAP Secret or the PPP Parameters' PAP Password.

• NONE: No authentication is provided.• PAP_S: Password Authentication Protocol server. The

Remote device must send a user ID and Password.• CHAP_S: Challenge Authentication Protocol server. The

Remote device must respond to the challenge.• PAP_C: Password Authentication Protocol client. This device



Specify combinations of the above by summing (for example, CHAP_C+PAP_C).

CHAP Secret Range: 0 to 32 alphanumeric charactersDefault: RemoteDescription: Specifies the PPP Password for Authentication. Use any character

including a semicolon ( ; ) in the string. When terminating the string with a semicolon, precede it with a backslash ( \ ).Example: hello\; = hello;

Use the space bar to blank field.



Note

Note

Network Protocols Range: NONE, IP, IPX, BridgeDefault: IPDescription: Specifies the network protocols supported on this port.

• IP : IP protocol• IPX: Novell IPX • Bridging

Specify combinations of the above by summing (for example, IP+Bridging).

IPCP Options Range: NONE, ADDR, VJ, IPHC, RUIHCDefault: NONEDescription: Specify IPCP options:

• ADDR - Enable IP address negotiation• VJ - Enable Van Jacobson header compression• IPHC - Enable IP header compression• RUIHC - Enable RTP header compression

These options can be combined using "+" sign.VJ cannot be com-bined with IPHC or RUIHC. Enter RUIHC+IPHC for all traffic to be sent with compressed headers. Enter RUIHC only for only RTP to be sent with compressed head-ers.

When RUIHC is configured in the PPP profile the associated LCON must be configured for RTP as the compression type. This parameter is only available by setting the RTP\UDP\IP Header Compression parameter to something other than disabled.




Note

Note

TCP Header Compression Max Slot Index Range: 0-255Default: 15



Description: Specify the maximum number of context slots for TCP header compression

NoteEnter 0 for one slot up to 255 for 256 slots

NoteWhen connecting to a Cisco device the Vanguard's max slot index must be less than or equal to the connecting device's setting.

Local IP Address Range: A valid IP address in dotted notation.Default: 0.0.0.0Description: Specifies a local IP address used during IP address negotiation.

This parameter appears only if IPCP Options is ADDR.

Remote IP Address Range: A valid IP address in dotted notation.Default: 0.0.0.0Description: Specifies a remote IP address used during IP address negotiation.

This parameter appears only if IPCP Options is ADDR.

IPXCP Options Range: NONE, NODE, NETDefault: NONEDescription: Specifies IPX Control Protocol option (IPXCP), the Network

Control Protocol for IPX. Use a plus sign (+) to combine options:• NONE: No option is enabled• NODE: Enables node number negotiation.• NET: Enables network number negotiation.

This parameter appears only if Network Protocols is IPX.

Specify combinations of the above by summing (for example, NODE+NET).

TCP Header Compression Max Slot Index

Note

Note

Note

Note

Node Number Range: 1 to 12 hexadecimal digits.Default: 0Description: Specifies a local IPX node number.

This parameter appears only if IPXCP Options is NODE.

Network Number Range: 1 to 8 hexadecimal digits. Default: 0Description: Specifies the network number used during network number

negotiation.

This parameter appears only if IPXCP Options is NET.

Encapsulation Range: PPP, RFC1490Default: RFC1490Description: Specifies the encapsulation for internal adjacent connection

between PPP and other entities (LAN Connection Table, FRI bypass station, X.25 port, and so forth). Typically, encapsulation between the Port and the WAN Adapter is RFC1490.

• PPP: PPP encapsulation• RFC1490: RFC1490 encapsulation

This parameter appears only if the Line Interface is ASYNC.

Compression Control Protocol Range: NONE, PROPDefault: NONEDescription: Specifies the compression protocol for this port. Configure this

parameter consistently with the compression option in the Network Services Feature Table.

• NONE: No data compression is enabled.• PROP: Vanguard Proprietary Data Compression is enabled.

This parameter appears only if the Line Interface is SYNC.




Note

Note

Note

Note

Dial Numbers #1/Dial Numbers #2 Range: 0 to 31 alphanumeric charactersDefault: (blank)Description: Specifies the telephone numbers used for dialing out.

• For demand operation, the numbers are used in the order specified. If fewer numbers are given than are required, the numbers are reused starting with the first one.

• If no telephone numbers are specified and if the Line Interface is ISDN, the numbers configured in the ISDN channel are used.



NoteTo use the Dial Number #2 parameter, you must enter and maintain a Dial Number #1 in the node’s PPP Profile Record.

*Dedicated Links Range: 0 to 32 alphanumeric characters. Use the space bar to blank this

parameter.Default: (blank)Description: Specifies the ports reserved for MultiLink operation. Dedicated

links (either switched or permanent connections) are dialled upon Node or Port boot, and are only available to the associated Virtual PPP Connection. The most common application for Dedicated Links is to specify any associated serial ports having permanent connections, such as SIMP. If a link with a switched interface, such as ISDN, is entered as a Dedicated Link, it cannot be used by other Virtual PPP Connections, and thus bandwidth is reserved for the connection.Reserved links are dial-up, at node or port boot, and may be either switched or permanent connections.

• Each reserved link name is separated by a comma (for example, PPP-2, PPP-3 indicates that PPP ports 2 and 3 are reserved).

• If the parameter Maximum Number of Switched Links is 0 (zero), you must specify at least one Dedicated Link for the Virtual PPP Connection.

Perform a Node boot to have changes to this parameter take effect.Note

Maximum Number of Switched Links Range: 0 to 2Default: 2




Description: Specifies the maximum number of switched links that this Virtual PPP Connection can obtain when allocating on-demand bandwidth. If no Dedicated Links are designated for the Virtual PPP Connection, you must set this parameter to 1 or 2.

Add Bandwidth Threshold Range: 0 to 100Default: 60Description: Specifies one of the criteria for determining when to add

bandwidth:• 0: All available bandwidth is added when data arrives.• 1 to 100: Additional bandwidth is added when link utilization

(in transmit direction) exceeds the value of this parameter and persists for the time specified by the Add Bandwidth Wait Time parameter.

Add Bandwidth Wait Time Range: 5 to 255Default: 20Description: Specifies one criteria for determining when to add bandwidth.

Additional bandwidth is added when link utilization exceeds the value of the parameter Add Bandwidth Threshold and persists for the time (in seconds) specified by this parameter.

Remove Bandwidth Wait Time Range: 5 to 255Default: 20Description: Indicates the amount of bandwidth that is removed when link

utilization (in both directions) drops below the value specified by the parameter Add Bandwidth Threshold and persists for the time (in seconds) specified by this parameter.

Maximum Number of Switched Links (continued)

Idle Disconnect Range: 0 to 3200Default 100



Description: Specifies the time (in seconds) that the outgoing link must be idle for automatic disconnection to occur. The timer is NOT restarted by inbound packets. The link will be terminated if inbound only traffic lasts longer than the specified timeout value. Any value above 0 enables Dial on Demand, where a call is initiated upon the arrival of application data. To disable this feature, set to 0 (zero)

Auto Connect Range: Disabled, EnabledDefault: DisabledDescription: Specifies how dialing occurs:

• Enabled: ISDN dialing (or EIA connection) occurs automatically upon disconnection, statistics reset, or upon arrival of data.

• Disabled: Only demand dialing occurs.

Maximum Number of Auto Connect Attempts Range: 0 to 255Default: 0Description: Specifies the maximum number of auto connect attempts. Once

the maximum number is reached, connection attempts resume only after PPP Statistics is reset. For unlimited connection attempts, set this parameter to 0 (zero).

This parameter appears only if Auto Connect is set to Enabled.

Auto Connect Retry Interval Range: 5 to 3600Default: 60Description: Specifies the time, (in seconds) between auto connect attempts

(when Auto Connect is enabled).

This parameter appears only if Auto Connect is set to Enabled.

Idle Disconnect

Note

Note




MLPPP Profile

Priority (Prioritization) Range: ENABLED, DISABLEDDefault: DISABLEDDescription: This parameter specifies whether prioritization support is required.

• ENABLE - allows traffic prioritization and interleaving. Reduce delay and delay variation for high priority traffic.

• DISABLE - provides backward compatibility with Vanguard Multilink PPP implementation. No support for the high prior-ity traffic is provided. Provides the best performance for the normal priority traffic.

Perform a profile boot to have changes to this parameter take effect.

If Multiclass is enabled in associated ports this parameter must beenabled.

TX CIR Kbit/sec rate (when none-zero)Range: 0-2048Default: 0Description: This parameter optionally specifies a Tx Committed Information

Rate. ENABLE - A non-zero CIR value (as kbits/sec) DISABLE - The default value of zero disables Transmit CIR enforcement

The PPP port(s) associated with this PPP/MLP profile must have MLP enabled

Note

Note

Maximum Serialization Delay When Voice is Present Range: 5 to 3600Default: 60



Description: When Priority is enabled, this parameter specifies the Maximum Serialization Delay of lower priority traffic that can be tolerated by delay sensitive traffic. Serialization delay is time required for data packet/segment of a certain size to be transmitted. Smaller delay improves voice performance but results in smaller segments, which lowers data throughput. When calculated segment size is smaller than the configured Minimum Segment Size the later will be taken as a segment size causing proportional increase in serial-ization delay.

NotePerform a profile boot to have changes to this parameter take effect.

NoteThis parameter appears only when Priority is enabled.

Maximum Serialization Delay When Voice is Not Present Range: 0 to 300 (ms)Default: 0Description: When Priority is enabled, this parameter specifies the Maximum

Serialization Delay in ms, that can be tolerated during time inter-vals when voice traffic is not present. Higher data rate can be then allowed and will be achieved by sending multiple segments. Spec-ified value shall be an integer multiple of Maximum Serialization Delay When Voice is Present (MSDVP). Otherwise it will be rounded to the closest lower value. When the configured value is less than the MSDVP it will be ignored. That is, traffic rate will not be changed. Perform a profile boot to have changes to this parameter take effect.

This parameter appears only when Prioritization is enabled and will have an effect only in MLPVP mode.

Maximum Serialization Delay When Voice is Present (continued)

Note

Minimum Segment Sizel Range: 32 to 1600Default: 32




Description: This parameter specifies the minimum segment size in bytes. When packet, or calculated segment size is equal to or smaller than this parameter, no further size reduction will take place. When prioritization is enabled, segment size will be set to this value if calculated segment size is smaller then this value.0 - This parameter will not have any effect. There is no limit for minimum segment size.Perform a profile boot to have changes to this parameter take effect.

NoteIf this parameter is set to value bigger then the negotiated MTU,no packet splitting will occur.

Rx Queue Size (one entry for all classes)l Range: 16 to 256Default: 64Description: Class Reassembly Queue Size parameter specifies the number of

packets/segments that are allowed to be queued in a particular queue. Input queue becomes full in case when one or more frag-ments are lost. All segments belonging to the incomplete packet(s) will be discarded when this number is reached for a queue.Perform a profile boot to have changes to this parameter take effect.

For all inbound (reassembly) queues, there is one parameter per bundle.

TX Queue Size Suspendable Classes 0-4Range: 64-2048Default: 512,512,512,512,512Description: This parameter specifies the number of packets that are allowed to

be queued for the outgoing suspendable class queue. When this number is reached for an output queue, ie. when the queue is full, all subsequent packet/segments targeted to this queue will be dis-carded. There are 15 queues which are configurable in groups of 5. Values can be left out if existing value is desired.For example, when current value is 70,70,50,50 entering ,,40,30 will result in a value of 70,70,40,30.Enter a blank line to reset to all defaults.

This parameter only appears when Prioritization is enabled

Minimum Segment Sizel (continued)

Note

Note







Reassembly Timeout (Class Out/In)l Range: 0 to 1000 (ms)Default: 1000 (ms)Description: This parameter specifies a time interval (in ms) that the MLP

receiver waits for the expected sequence number arrival after receiving an out-of-order segment.0 - Timeout disabled.

Perform a profile boot to have changes to this parameter take effect.



Note

Note

Note

Driver Buffer LimitRange: INTERNAL, 2Default: INTERNALDescription: This parameter specifies the maximum number of packets allowed

to be queued in the driver transmission buffer. A smaller number reduces delay of real-time traffic.INTERNAL - Internally set number (5 to 20) based on the driver type.

Perform a port boot to have changes to this parameter take effect.

This parameter appears only when Prioritization is enabled.

IPCP DebugRange: NONE, IPCP, MLP_QOS, VJ, ADDRESSDefault: NONEDescription: This parameter specifies the debug messages that are enabled.

NONE - No debug messages are enabled IPCP - IPCP debug messages are enabled ADDRESS - Address debug messages are enabled MLP_QOS - MLP_QOS debug messages are enabled VJ - MLP_QOS debug messages are enabled

IPHC DebugRange: NONE, ERRORS, FULL, TCP, UDP, RTP, NON_TCP, CON-

TEXTDefault: NONEDescription: This parameter specifies the debug messages that are enabled.

NONE - No debug messages are enabled IPHC - IPCP debug messages are enabled TCP - Address debug messages are enabled UDP - UDP compression debug messages are enabled NON_TCP - NON_TCP compression debug messages are enabled RTP - RTP compression debug messages are enabled CONTEXT - Context State debug messages are enabled FULL - FULL packet debug messages are enabled




Note

Note


PPP SNMP

PPP SNMP

Introduction SNMP support is available for release 6.4 and greater configuration and statistics.Stacking Support Configuration:

pppPCfgStackSupportenterprises codex cdxProductSpecific cdx6500 cdx6500Configuration cdx6500CfgProtocolGroup cdx6500PCTPortProtocolGroup cdx6500PPCTPPPPortTable cdx6500PPCTPPPPortEntry pppPCfgStackSupport

Stacking Connection Destination ID Configuration:

pppPCfgStackIDenterprises codex cdxProductSpecific cdx6500 cdx6500Configuration cdx6500CfgProtocolGroup cdx6500PCTPortProtocolGroup cdx6500PPCTPPPPortTable cdx6500PPCTPPPPortEntry pppPCfgStackID

Stacking mode configuration (normal/PPPoE):

pppPCfgStackModeenterprises codex cdxProductSpecific cdx6500 cdx6500Configuration cdx6500CfgProtocolGroup cdx6500PCTPortProtocolGroup cdx6500PPCTPPPPortTable cdx6500PPCTPPPPortEntry pppPCfgStackMode

Stacking encapsulation type configuration:

pppPCfgStack Encapsulationenterprises codex cdxProductSpecific cdx6500 cdx6500Configuration cdx6500CfgProtocolGroup cdx6500PCTPortProtocolGroup cdx6500PPCTPPPPortTable cdx6500PPCTPPPPortEntry pppPCfgStackEncapsulation

Current Stacking State:

pppPCfgStack Encapsulationenterprises codex cdxProductSpecific cdx6500 cdx6500Statistics cdx6500StatProtocolGroup cdx6500PSTPortProtocolGroup cdx6500PPSTPPPStatsTable cdx6500PPPPortTable cdx6500PPPPortEntry pppPStatsStackState



PPP SNMP

Current stacking Handshake State:

pppPStatsStackHandshakeStateenterprises codex cdxProductSpecific cdx6500 cdx6500Statistics cdx6500StatProtocolGroup cdx6500PSTPortProtocolGroup cdx6500PPSTPPPStatsTable cdx6500PPPPortTable cdx6500PPPPortEntry pppPStatsStackHandshakeState

Max link speed as reported by lower stack:

pppPStatsPortMaxSpeedenterprises codex cdxProductSpecific cdx6500 cdx6500Statistics cdx6500StatProtocolGroup cdx6500PSTPortProtocolGroup cdx6500PPSTPPPStatsTable cdx6500PPPPortTable cdx6500PPPPortEntry pppPStatsPortMaxSpeed

PPP MIBs (ppp_opt.mib)

MAC address to use when stacking support is enabled for this link:

pppoePCfgMyMacAddressenterprises codex cdxProductSpecific cdx6500 cdx6500Configuration cdx6500CfgProtocolGroup cdx6500PCTPortProtocolGroup cdx6500PPCTPPPoePortTable cdx6500PPCTPPPoePortEntry pppoePCfgMyMacAddress

MAC address being used for the link:

pppoePStatsMyMacAddressenterprises codex cdxProductSpecific cdx6500 cdx6500Statistics cdx6500StatProtocolGroup cdx6500PSTPortProtocolGroup cdx6500PPSTPPPoeStatsTable cdx6500PPPoePortTable cdx6500PPPoePortEntry pppoePStatsMyMacAddress

FRI MIBs (fri_opt.mib)

Stacking Support Configuration:

friSCfgStackingSupportenterprises codex cdxProductSpecific cdx6500 cdx6500Configuration cdx6500CfgProtocolGroup cdx6500PCTStationProtocolGroup cdx6500SPCTFRIStationTable cdx6500SPCTFRIStationEntry friSCfgStackingSupport


PPP SNMP

Identifier of the connected Stack:

friSStatsStackConnIDenterprises codex cdxProductSpecific cdx6500 cdx6500Statistics cdx6500StatProtocolGroup cdx6500PSTStationProtocolGroup cdx6500SPSTFRISStatsTable friSGenStatsTable cdx6500friSGenStatsEntry friSStatsStackConnID


friSStatsStackStateenterprises codex cdxProductSpecific cdx6500 cdx6500Statistics cdx6500StatProtocolGroup cdx6500PSTStationProtocolGroup cdx6500SPSTFRISStatsTable friSGenStatsTable cdx6500friSGenStatsEntry friSStatsStackState

ATM MIBs atm_opt.mib

Stacking Support Configuration:

atmSCfgStackingSupportenterprises codex cdxProductSpecific cdx6500 cdx6500Configuration cdx6500CfgProtocolGroup cdx6500PCTStationProtocolGroup cdx6500SPCTATMStationTable cdx6500SPCTATMStationEntry atmSCfgStackingSupport

Identifier of the connected stack:

atmSStatsStackConnIDenterprises codex cdxProductSpecific cdx6500 cdx6500Statistics cdx6500StatProtocolGroup cdx6500PSTStationProtocolGroup cdx6500SPSTATMSStatsTable atmSGenStatsTable cdx6500atmSGenStatsEntryatmSStatsStackConnID


atmSStatsStackStateenterprises codex cdxProductSpecific cdx6500 cdx6500Statistics cdx6500StatProtocolGroup cdx6500PSTStationProtocolGroup cdx6500SPSTATMSStatsTable atmSGenStatsTable cdx6500atmSGenStatsEntryatmSStatsStackConnID



PPP SNMP

Current Stacking Handshake State:

atmSStatsStackHandshakeStateenterprises codex cdxProductSpecific cdx650 cdx6500Statistic cdx6500StatProtocolGroup cdx6500PSTStationProtocolGroup cdx6500SPSTATMSStatsTable atmSGenStatsTable cdx6500atmSGenStatsEntryatmSStatsStackHandshakeState


Statistics

Statistics

Introduction This section describes the statistics available for a PPP connection. You can view these statistics from the CTP menu.

Navigating the CTP Figure 55 shows how to navigate the CTP and find statistics relevant to PPP operation.

Node: Address: Date: Time:Menu: Main Path: (Main)

1. Logout 2. Examine 3. List 4. Monitor 5. Status/statistics

Node: Address: Date: Time:Menu: Status/statistics Path: (Main.5)

1. Node Stat 19. Detailed DORM Statistics2. Detailed Port Stat 20. Reset DORM Statistics3. Flash to Flash Transfer Stat 21. Detailed NUIC Stats4. Detailed Link Stat 22. Reset NUIC Stats5. FRI Station Statistics 23. PPP Statistics6. Detailed Pad Stat 24. Reset PPP Statistics7. Network Services Stats 25. SPFM Connection Statistics8. Hardware Stats 26. (reserved)9. Lan Connection Statistics 27. (reserved)10. Reset Port Stats 28. (reserved)11. Reset All Stats 29. (reserved)12. Software Option Statistics 30. SNMP Statistics13. TFTP Stats14. Router Stats15. Detailed NCI Statistics16. Reset NCI Statistics17. Detailed DORA Statistics18. Reset DORA Statistics

#Enter Selection:

Detailed PPP Port StatisticsThese statistics pertain to the connection taking place on the physical port.

Detailed Link StatisticsThese statistics pertain to the links that support the connection bundle in a Multilink PPP connection.

Detailed PPP Connection Statistics These statistics pertain to the connection bundle in a Multilink PPP connection.

Figure 55. How To Find Statistics Screens For PPP Operation



Statistics

Stacking State Values

Introduction Release 6.4 and greater allows the PPP port, FRI station, and AAM station to include statistics to indicate the current state of the stack connection. The states will consist of WAIT FOR CONNECT, CONNECTED, and DISCONNECTING. For the CONNECTED state, additional state status is shown indicating the stacking state machine state: HANDSHAKING, READY.

State DescriptionWAIT FOR CONNECT

The stack layer is waiting for a stack connection to be established. Either this is a top socket waiting for an incoming stack connection, or it is a bottom socket wait-ing for a connection request.

CONNECTED

HANDSHAKING

Connection has been established with the destination stack.Handshaking is occurring with the connected stack to establish inter-stack communication.

CONNECTEDREADY

Connection has been established with the destination stack.Inter-stack communication has been established.This is the normal working state.

DISCONNECTING The connected stacks are being disconnected. This is usually due to port/station boot.

NoteIf the stacking state remains in any state other than CONNECTED/READY, check the destination stack layer to see if there are any problems including missing or wrong configuration. Remaining in CONNECTED/HANDSHAKING state or DISCONNECTING state may indicate Internal problems

.


Statistics

Port Statistics

Introduction Detailed PPP port statistics provide the status of port operations.

How To View Detailed Statistics

Follow these steps to view PPP port statistics during PPP operation.

Step Action 1 Select Status/Statistics, from the CTP Main menu.2 Select Detailed Port Statistics, from the Status/Statistics menu. 3 Enter the number of the PPP connection that you want statistics on, and

press Return.

PPP Port Statistics Stacking Enabled

PPP port statistics display the interface stacking state, if enabled.When stacking support is enabled for bottom socket, Interface summary in the PPP port statistics is replaced by the stacking statistics which indicates the stacking connection identifier and the current state of the connection: WAIT FOR CONNECT, CONNECTED, DISCONNECTING. For the CONNECTED state, additional state status is shown indicating the stacking state machine state: HANDSHAKING, READY.When stacking support is enabled for the bottom socket, Port Speed shows the current and maximum speed of the link. These values are communicated up from the lower layer and reflect the current and maximum possible speed for the link.

Node:100 Address:100 Date: 27-JUN-2003 Time: 12:06:33

Detailed PPP Port Statistics: Port 100 Page: 1 of 3

Port Speed: 32000 / 64000 Port Status: Up

Data Summary: In Out In Out

Frames: 30 32 Octets: 585 671

Octets/sec: 0 0 Utilization: 0 % 0 %

Stack ID: FRI-1S1

Stack State: CONNECTED / READY

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

Figure 56. PPP Port Statistics, Stacking Enabled



Statistics

Detailed Port Statistics - Page 1

Figure 57 shows an example of detailed PPP port statistics. Stacking is not enabled:

Node: Address: Date: Time: Detailed PPP Port Statistics: Port 3 Page: 1 of 3Port Speed: 9600 Port Status: Up Virtual PPP Connection: MLPPP-1

Adjacent Entity: Name: LCON-1 Type: PVC State: Connected Data Summary: In Out In Out

Frames: 0 6 Octets: 0 168Octets/sec: 0 0 Utilization: 0 % 0 %IP Packets: 0 0 IPX Packets: 0 0 Compr. Pkt: 0 0 BPDU Packets: 0 0

Discarded: 0 0

Physical Summary: Overrun: 0 Underrun: 0 CRC: 0 Non-Octet Aligned: 0

Interface Summary: EIA-232-D DCE INPUT OUTPUT DTR RTS MB P14 DSR DCD RI CTS State: Connected (SIMPLE) H H L H H H L H

Figure 57. Detailed Port Statistics Screen - Page 1


Statistics

Screen Terms - Page 1

This table describes the screen terms shown in Figure 57:

Screen Term Indicates... Port Speed Measured speed of the port.Port Status Status of the port:

• UP LCP is in an Open State and link is established.• DOWN: Link is not established.• DISABLED: Port is busy or unable to operate.

Virtual PPP Connection

The name of the connection associated with this link. This statistic appears only when Multilink is enabled.

Adjacent Entity Status of the connection with the internal adjacent entity. An adjacent entity is another software component which connects to the PPP link and manages information, like the LCON or the WAN Adapter. The adjacent entity is typically connected to a bridge or router on an access port.

• Name: name of the adjacent entity.• Type: type of connection:

– Permanent Virtual Circuit (PVC) – Switched Virtual Circuit (SVC)

• State: – WAIT_FOR_CALL: message from an adjacent entity

configured for SVC connections that means it is ready to receive a call.

– CONNECTED: message from an adjacent entity configured for SVC connections that means it is connected.

– HANDSHAKING: message from an adjacent entity configured for PVC connections that means it is not ready for data passing.

– WAIT_FOR_CLR_CONF: message from an adjacent entity configured for SVC connections that means it is waiting for X.25 clear confirm.

– WFCC_DISABLED: message from an adjacent entity configured for SVC connections that means it is waiting for X.25 clear confirm and PPP is disabled.

– DISABLED: Message that means the adjacent entity is disabled.



Statistics

Data Summary The amount of data being exchanged over this port since the last boot or statistic reset:

• Frames: the number of HDLC (High Level Data link) frames that are received (In) and sent (Out).

• Octets: the number of bytes that are received (In) and sent (Out).

• Octets/sec: the number of bytes per second that are received (In) and sent (Out).

• Utilization: the percentage of available bandwidth that is being used for an inbound (In) or (Outbound) connection.

• IP Packets: the number of IP packets being received (In) and sent (Out).

• IPX Packets: the number of IPX packets being received (In) and sent (Out).

• Compr. Pkts. (Compressed Packets): the number of compressed packets received (In) and sent (Out).

NoteVanguardMS only supports proprietary (CLZ ) data compression.

• BPDU Packets: the number of bridging BPDU frames (Bridging Protocol Data Units) being received (In) and sent (Out).

• Discarded: the number of packets discarded while being received (In) or sent (Out).

Physical Summary Summary of errors at the physical layer:• Overrun: a receive error.• Underrun: a transmission error.• CRC: received and discarded a corrupted frame.• Non-Octet Aligned: received and discarded invalid

frame.

Screen Term Indicates... (continued)


Statistics

Interface Summary The state of the interface:• Idle • Connected• Disconnected

The state of the interface for AT Dialer:• IDLE (DIMOat)• MODEM INIT (DIMOat)• DSRWAIT (DIMOat)• DTRWAIT (DIMOat)• ANSWAIT (DIMOat)• DIAL (DIMOat)• DATARDY (DIMOat)

The interface can be either EIA or ISDN. EIA and ISDN have different variables. The components of each are listed below.

• EIA Summary:– State: Connected/Disconnected– INPUT: DTR, RTS, MB, P14– OUTPUT: DSR, DCD, RI, CTS

• ISDN Summary:– TEI: Terminal End Identifier– State: ACTIVE/INACTIVE– SPBU: Enabled/Disabled– Channel: B1/B2/D




Statistics

Detailed Port Statistics - Page 2

Figure 58 shows an example of detailed PPP port statistics.

Node: Address: Date: Time: Detailed PPP Port Statistics: Port 3 Page: 2 of 3

LCP State: Opened LCP Options: Local Remote ACF Compression: ON ON PF Compression: ON ON ACCM: 00000000 FFFFFFFF MRU: 1620 1620 MRRU: 1620 1620 PAP: Off Off CHAP: Server Client: InitialCCP State:CCP Options: Not available



This table describes the screen terms shown in Figure 58.

Screen Term Indicates... LCP state State of the LCP state machine. If the state is Open, the line

is operational.For more information about LCP, see “Link Control Protocol” section on page 5. See RFC1661 for a definition of the PPP connection states.

LCP Options Negotiated values of LCP options: • ACF (Address/Control Field) Compression• PFC (Protocol Field) Compression• ACCM (Async Character Control Maps)• MRU (Maximum Receive Unit)• MRRU (Maximum Received Reconstructed Unit)• PAP (Password Authentication Protocol)• CHAP (Challenge Handshake Authentication Protocol)

CCP state State of the CCP state machine. If the state is Open, the line is operational. For more information about CCP, see “Network Control Protocols” section on page 5 or “Proprietary Compression” section on page 76. See RFC 1661 for a definition of the PPP connection states.


Statistics

Port Statistics - Page 3

Figure 59 shows an example of detailed PPP port statistics.

Node: Address: Date: Time: Detailed PPP Port Statistics: Port 3 Page: 3 of 3 NCP Information:

IPCP State: Opened IPCP Options: Local Remote IP Address: 0.0.0.0 0.0.0.0 VJ Compression: ON ON Slots: 16 16 CID Compression: ON ON

IPXCP State: Opened IPXCP Options: Local Remote Node number: 0 0 Net number: 0


CCP options Negotiated values for CLZ data compression. (Only proprietary compression is supported.)




Statistics


This table describes the screen terms shown in Figure 59.

Screen Term Indicates... NCP Information Network Control Protocol information refers to all statistics

below on IPCP and IPXCP states and options.IPCP state State of the IPCP state machine. If the state is Open, the line

is operational.For more information about IPCP, see “Network Control Protocols” section on page 5. See RFC1661 for a definition of the PPP connection states.

IPCP options Negotiated values of IPCP options:• VJ Compression• Number of Slots • CID compression• Local and remote IP addresses

IPXCP state State of the IPXCP state machine. If the connection state is Open the line is operational.For more information about IPXCP, see “Network Control Protocols” section on page 5. See RFC1661 for a definition of the PPP connection states.

IPXCP options Currently negotiated values of IPXCP options:• Local and Remote Node number• Net Number


Statistics

PPP Connection Statistics

Introduction The Detailed PPP Connection Statistics screen provides the connection states, data summaries, and details of Network Control Protocols. Detailed PPP Connections Statistics are only available for MultiLink connections.

How To View PPP Connection Statistics

Follow these steps to view PPP connection statistics during PPP operation:

Step Action 1 From the CTP Main menu, select Status/Statistics.2 Select Detailed PPP Connection Statistics from the Status/

Statistics menu. 3 Enter the number of the PPP connection that you want statistics on, and

press Return.

PPP Connection Statistics - Page 1

Figure 60 shows an example of PPP connection statistics.

Node: Address: Date: Time: Detailed PPP Connection Statistics Page: 1 of 3Virtual PPP Connection Number: 1 Number of Active Links: 2

Adjacent Entity: Name: LCON-1 Type: PVC State: Connected

Data Summary: In Out In OutIP Packets: 11127 11087 IPX Packets: 0 0 Compr. Pkt: 0 0 BPDU Packets: 0 0 Discarded: 0 0

Dial Management Summary: Last Inbound Link: PPP-3 Outbound Connection Attempts: Successful: 1 Failed: 0 Last Outbound Link: PPP-2 Status: Successful Dialed Number: 95551000

Figure 60. PPP Connection Statistics Screen - Page 1



Screen Term Indicates... Virtual PPP Connection

Name of the connection associated with this link. This statistic appears only when Multilink is enabled.



Statistics

Number of Active Links

Number of links that are active in the MultiLink connection bundle.

Adjacent Entity Status of the connection with the internal adjacent entity.• Name: the name of the adjacent entity.• Type: type of connection:

– Permanent Virtual Circuit (PVC)– Switched Virtual Circuit (SVC)

• State: – WAIT_FOR_CALL: message from an adjacent entity

configured for SVC connections that means it is ready to receive a call.

– CONNECTED: message from an adjacent entity configured for SVC connections that means it is connected.

– HANDSHAKING: message from an adjacent entity configured for PVC connections that means it is not ready for data passing.

– WAIT_FOR_CLR_CONF: message from an adjacent entity configured for SVC connections that means it is waiting for X.25 clear confirm.

– WFCC_DISABLED: message from an adjacent entity configured for SVC connections that means it is waiting for X.25 clear confirm and PPP is disabled.

– DISABLED: message that means the adjacent entity is disabled.

Data Summary The amount of data being exchanged over this port since the last boot or statistic reset:

• IP Packets: the number of IP packets being received (In) and sent (Out).

• IPX Packets: the number of IPX packets being received (In) and sent (Out).

• Compr. Pkts. (Compressed Packets): the number of compressed packets received (In) and sent (Out).

NoteVanguardMS only supports proprietary (CLZ ) data compression.

• BPDU Packets: the number of bridging BPDU frames (Bridging Protocol Data Units) being received (In) and sent (Out).

• Discarded: the number of packets discarded while being received (In) or sent (Out).



Statistics




CCP State: Initial CCP Options: Not available

NCP Information:

IPCP State: Opened IP Packets In: 23456 IP Packets Out: 67890 IPCP Options: Local Remote IP Address: 0.0.0.0 0.0.0.0 VJ Compression: ON ON Slots: 16 16 CID Compression: ON ON

IPXCP State: Opened IPX Packets In: 23456 IPX Packets Out: 67890 IPXCP Options: Local Remote Node number: 0 0 Net number: 0




Dial Management Summary

The links connected with the Dial on Demand utility:• Last Inbound Link: the last link connected, • Outbound Connection Attempts: the number of

successful and failed attempts to connect links• Last Outbound Link: the last link used as well as the

status and dial number connected



The name of the connection associated with this link. This status report appears only when Multilink is enabled.


The number of links that are active in the Multilink connection bundle.



Statistics

CCP State State of the CCP state machine. If the state is Open, the line is operational. For more information about CCP, see “Network Control Protocols” section on page 5 or “Proprietary Compression” section on page 76. See RFC 1661 for a definition of the PPP connection states.

CCP Options Negotiated values for CLZ compression. Only proprietary compression is supported.

NCP Information Network Control Protocol information refers to all statistics below on IPCP and IPXCP states and options.

IPCP State State of the IPCP state machine. If the state is Open, the line is operational.For more information about IPCP, see “Network Control Protocols” section on page 5. See RFC1661 for a definition of the PPP connection states.

IP Packets IP packets received (IN) and sent (OUT) on the port. “Not available” appears when Data Compression is operational.

IPCP Options Negotiated values of IPCP options:• VJ compression• Number of slots • CID compression• Local and remote IP addresses

IPXCP State State of the IPXCP state machine. If the state is Open, the line is operational.For more information about IPCP, see “Network Control Protocols” section on page 5. See RFC1661 for a definition of the PPP connection states.

IPX Packets IPX packets received (IN) and sent (OUT) on the port. “Not available” appears when Data Compression is operational.

IPXCP Options Currently negotiated values of IPXCP options:• Local and remote node numbers• Net number



Statistics




Summary of Associated Links: * = dedicated link

LCP Data Frames Utilization Link Speed Member State in/out in/out Current Maximum ======== ======== ============ =========== ================ *PPP-2 Opened 46912 87% 32000 64000 135780 3% PPP-3 Opened 12345 86% 32000 64000 65432 3%





Name of the connection associated with this link. This statistic appears only when Multilink is enabled.


Number of links that are active in the MultiLink connection bundle.

Summary of Associated Links

Summary of statistics for each link:• Member: the name of a link in the bundle.• Number of Active Links: state of the IPCP automaton.

(See RFC 1661 for a definition of the PPP connection states.) If the automaton state is Open, the line is operational.

• Data Frames in/out: the number of HDLC (High Level Data link) frames that are received (In) and sent (Out).

• Utilization in/out: the percentage of available bandwidth used for an inbound (In) or (Outbound) connection.

Link Speed Link Speed current and maximum values are available in the Summary of Associated Links with release 6.4 and greater. These values are communicated up from the lower layer and reflect the current and maximum possible speed for the link.



Statistics

PPP QoS Connection Statistics

Introduction The Detailed PPP Connection Statistics screen (6.4 and greater software) provides the connection states, data summaries, and details of Network Control Protocols. Detailed PPP Connections Statistics are only available for MultiLink connections.

How To View PPP Connection Statistics

Follow these steps to view PPP connection statistics during PPP operation:

Step Procedured1 From the CTP Main menu, select Status/Statistics.2 Select Detailed PPP Connection Statistics from the Status/ Statis-

tics menu.3 Enter the number of the PPP connection that you want statistics on, and

press Return.

Figure 63. PPP Connection Statistics Screen - Page 3 of 7

Figure 64. QoS Priority Classes Inbound Statistics - Page 4 of 7


Statistics

Figure 65. QoS Priority Classes Outbound Statistics- Page 5 of 7

Figure 66. Summary of Associated Links - Page 6 of 7

Screen Term Indicates...Priority Current Interleaving status: DISABLED/ENABLED.

High Priority Status Status of the highest priority (class 15/voice) traffic.ACTIVE - There have been some traffic within the last 30 seconds.INACTIVE - There have not been any traffic within the last 30 seconds.

Mode in/out Current MLP mode: normal/voice/multiclass.Bundle Classes out/ in

Number of suspension classes.

Total Packets out/in Total Packets out/in Total number of packets transmitted to and received from the peer.



Statistics

Total Bytes out/in Total number of bytes transmitted to and received from thepeer.

Bytes/sec out/in Bundle byte Output/Input rate.Packets/sec out/in Bundle packet Output/Input rate.Unknown Classes out/in

Number of unrecognized classes received by Layer 3 and the peer.

Segment size out/in Current Tx/Rx segment size for each bundle's PPP port.Number of Sessions Number of successfully established MLP Sessions.Session On Time period the current session is active. Format shall be

WW/DD/HH/MM/SS.Cls Total Packets out/in

The class total number of packets transmitted to and received from the peer.

Cls Total Bytes out/ in

Cls Bytes/sec out/in Class byte Output/Input rate.

Cls Packets/sec out/ in

Class packet Output/Input rate.

Cls Queue Current Packets out/in

Current number of packets/segments in the queue.

Cls Queue Max. Packets out/in

Maximum number of packets/segments in the queue.

Cls Queue Aver. Packets out/in

Average number of packets/segments in the queue.

Cls Queue Dis-carded Packets out/ in

Total number of discarded packets for the output or input queue.

Cls Out Queue Max Delay

Maximum Time Interval packets spent in the queue.

Cls Out Queue Aver-age Delay

Average Time Interval packets spent in the queue.

Cls Sequence out/in Current sent and received MLP sequence number.Cls Reassembler Sta-tus

Synchronized - Packet reassembling is successfulUnsynchronized - Reassembler is discarding segments.

Cls Lost Synchroni-zations

Total number of times class Reassembler has been Unsyn-chronized.

Screen Term Indicates...


Statistics

Values of all bundle's counting parameters, are accumulated after the last profile boot or statistics reset. All link class/queue counters except Queue Discard Packets shall be reset at the MLP session start.

Cls Lost Segments Total number of lost segments for a class - This number encompasses received and discarded segments as well as non-received segments that can be calculated.N.A. - Cannot be calculated.Number of non-received segments is calculated by detecting gaps in sequence numbers of received segments. It must be received at least one valid segment after a segment loss, to calculate the gap. When a packet loss is in progress, i.e. no valid segment has been received, this number is not valid. However, this parameter can be useful when normal recep-tion is disturbed by burst(s) of lost segments.

Screen Term Indicates...



Statistics

Link Statistics

Introduction Link Statistics provide a comparative profile of all the existing links in a MultiLink connection. Link Statistics are only available for MultiLink connections.

How To View Link Statistics

Follow these steps to view PPP link statistics during PPP operation:

Step Action 1 Select Status/Statistics from the CTP Main menu.2 Select Detailed Link Stat from the Status/Statistics menu. 3 Enter the number of the PPP connection that you want statistics on, and

press Return.

Detailed Link Statistics

PPP provides link statistics for each configured link. Figure 67 shows an example of a Link Statistics screen for a Vanguard 311 operating with two PPP links.

Node: Address: Date: Time: Detailed Link Statistics Page: 1 of 1 Type State CRC Link Data frames Utilizationentity subtype state speed date/time errors down in/out in/out====== ======== ===== ======= =========== ======= ====== =========== ===========p1 X25 down 16000 0 0 1556 0% 0 0%p2 MLPPP up 64000 03-JAN-1995 1 38 8275 87% isdn 10:03:42 8306 3%p3 MLPPP up 64000 03-JAN-1995 1 29 11308 86% isdn 10:03:10 11338 3%

Figure 67. Link Statistics Screen


Statistics

Screen Terms This table describes the screen terms shown in Figure 67:

Screen Term Indicates... Entity Port number.Type subtype Port type and subtype. These determine the type of link

(X.25, Frame Relay, PPP) maintained over this port. This statistic identifies whether a port is MP or (Single Link) PPP.

State Whether the LCP link is up or down.Speed Clocked transmission speed.State date/time When the current LCP link came up.CRC errors (Cyclic Redundancy Check errors)

Number of CRC that have occurred since the last port boot or statistic reset.

Link down Number of time the link has gone down since the last port boot or statistic reset.

Data frames in/out Number of data frames that have been received (in) and sent (out) since the last port boot or statistic reset.

Utilization in/out Percentage of the link bandwidth that is presently in use.



Statistics

PPP over Ethernet (PPPoE) Statistics

Introduction Detailed PPP port statistics provide the status of port operations.

How To View Detailed Statistics

Follow these steps to view PPPoE port statistics during PPP operation.

Step Action 1 Select Status/Statistics, from the CTP Main menu.2 Select Detailed Port Statistics, from the Status/Statistics menu. 3 Enter the number of the PPP connection that you want statistics on, and

press Return.

Figure 68 shows an example of a PPPoE Statistics screen.

Node: Address: 100 Date: 17-SEP-2002 Time: 17:19:17Detailed PPP Port Statistics: Port 100 Page: 4 of 9PPPoE Statistics: Session Status: PPP Session Session ID: 22 ETH Port: 5 Auto Connect: EnabledAC MAC address: 00-60-08-31-CD-41 Session ON Time: 0 days 0:18:55 Total ON Time: 0 days 0:18:55Service Name Errors: 0 in out AC System Errors: 0 PADT: 0 0 Generic Errors: 0 PADI: 1Connection Loss Cnt: 0 Sess. Establish Cnt: 1Service Name: service-name AC Name: ac-name

Figure 68. PPPoE Statistics Screen


Statistics

Stacking Support When stacking support is configured, the PPP port statistics display the MAC address being used. The PPPoE statistic page will not display the Ethernet Port when stacking support is configured.

Node:100 Address:100 Date: 27-JUN-2003 Time: 12:06:33Detailed PPP Port Statistics: Port 100 Page: 5 of 9PPPoE Statistics: MAC address: 02-08-D5-00-00-C0Session Status: ............. Session ID: .....

Auto Connect: Disabled ** DISABLED/IN DIAGNOSTICS MODE ** AC MAC address: 00-00-00-00-00-00 Session ON Time: 000 days 00:00:00 Total ON Time: 000 days 00:00:00 Service Name Errors: 0000000000 in out AC System Errors: 0000000000 PADT: 0000000000 0000000000 Generic Errors: 0000000000 PADI: 0000000000 Connection Loss Cnt: 0000000000 Sess. Establish Cnt: 0000000000 Service Name: ................................................................ AC Name: ................................................................

Figure 69. PPP Port Statistics (PPPoE) Stacking Enabled

PPPoE Terms

Screen Term Indicates... PPPoE Session Status

Current PPPoE session status:• Inactive - Waiting for host traffic to send PADI packet• Discovery Stage - Waiting for PADO packet• Discovery Stage - Waiting for PADS packet

Service-Name Current Session Service-Name.AC-Name Current Session AC-Name.PPPoE Session ID PPPoE Session ID sent by Service Provider.Number of PPPoE Sockets

Number of PPPoE sessions supported by that Ethernet port (at the moment).

Destination MAC address

Destination MAC address sent by Service Provider.

Service Name Errors

Total number of Service Name Errors received after the last sta-tus reset.

AC System Errors Total number of AC System Errors.Generic Errors Total number of Generic Errors received after the last status

reset.Session ON Time Current Session ON Time.Total Session ON time

Total Session ON time after the last status reset.



Statistics

Last Session Discovery Packets

Figure 70 through Figure 73 show the PADI, PADO, PADR and PADS packets captured in the last successful session as well as packet delay after PADI was sent.

Node: Address: 100 Date: 17-SEP-2002 Time: 17:20:02 Detailed PPP Port Statistics: Port 100 Page: 5 of 9 PPPoE Statistics - Last Session Discovery PacketsPADIAC MAC Address: FF-FF-FF-FF-FF-FF Ethernet Type: 0x8863Version: 01 Type: 01 Code: 0x09 Session ID: 0x0000 Length: 4TAG Type: 0x0101 (Service-Name ) TAG Length: 0TAG Value: service-namePress any key to continue ( ESC to exit ) ...

Figure 70. PADI

Session Count Total number of times a session was established after the last status reset.

PADT packet in/out

Total number of PADT packet received from and sent to AC, after the last port boot.

Connection Loss Count

Total number of times a connection loss was detected after the last port boot.

PADI Count Total number of PADI packets sent after the last session was terminated.

Auto Connect Current Auto Connect status. May be Enabled or Disabled.Last Session Discovery Packets

Fields of the PADI, PADO, PADR and PADS packets, captured in the last successful session as well as packet delay after PADI was sent.


Node: Address: 100 Date: 17-SEP-2002 Time: 17:20:24 Detailed PPP Port Statistics: Port 100 Page: 6 of 9PPPoE Statistics - Last Session Discovery PacketsPADO Packet Delay: +0:00:00.149AC MAC Address: 00-60-08-31-CD-41 Ethernet Type: 0x8863Version: 01 Type: 01 Code: 0x07 Session ID: 0x0000 Length: 51TAG Type: 0x0102 (AC-Name) TAG Length: 7TAG Value: ac-nameTAG Type: 0x0101 (Service-Name) TAG Length: 12TAG Value: service-nameTAG Type: 0x0104 (AC-Cookie) TAG Length: 20TAG Value: A2 BD B1 29 8F EB 91 05 1F 60 87 2F 82 FA 8F 71 A1 08 00 00Press any key to continue ( ESC to exit ) ...


Statistics

Figure 71. PADO

Node: Address: 100 Date: 17-SEP-2002 Time: 17:20:43 Detailed PPP Port Statistics: Port 100 Page: 7 of 9PPPoE Statistics - Last Session Discovery PacketsPADR Packet Delay: +0:00:00.149AC MAC Address: 08-00-3E-1B-5E-14 Ethernet Type: 0x8863Version: 01 Type: 01 Code: 0x19 Session ID: 0x0000 Length: 40TAG Type: 0x0101 (Service-Name ) TAG Length: 12TAG Value: service-nameTAG Type: 0x0104 (AC-Cookie) TAG Length: 20TAG Value: A2 BD B1 29 8F EB 91 05 1F 60 87 2F 82 FA 8F 71 A1 08 00 00Press any key to continue ( ESC to exit ) ...

Figure 72. PADR

Node: Address: 100 Date: 17-SEP-2002 Time: 17:26:07 Detailed PPP Port Statistics: Port 100 Page: 8 of 9PPPoE Statistics - Last Session Discovery PacketsPADS Packet Delay: +0:00:00.378AC MAC Address: 00-60-08-31-CD-41 Ethernet Type: 0x8863Version: 01 Type: 01 Code: 0x65 Session ID: 0x0016 Length: 16TAG Type: 0x0101 (Service-Name ) TAG Length: 12TAG Value: service-namePress any key to continue ( ESC to exit ) ...

Figure 73. PADS



Diagnostics

Diagnostics

introduction This section describes the diagnostics available for a PPPoE connection. You can view these Diagnostics from the CTP menu.

PPP over Ethernet (PPPoE) Diagnostics

Diagnostics menu option

Three commands are provided for PPPoE control and diagnostics. To start a Diagnostic session, an Ethernet port and an associated PPPoE stack shall exist. If not, an alarm message is generated. Figure 74 shows the diagnostic menu options available when you select:Diagnostics->PPPoE Diagnostics from the main menu.

Ethernet Port Number: 5/

1. Stop Regular PPPoE Session 2. Start Regular PPPoE Session 3. Start PPPoE Diagnostic Session

Enter Selection:

Figure 74. PPPoE Diagnostic Menu Options

Command ActionStop Regular Session

This command terminates the current PPPoE session or an attempt to establish a new session.

NoteThis command shall not cause any change in a CMEM record. Regular PPPoE activities may be resumed using "Start Regular Session" command or after a PPP port boot.

Start Regular Session

This command resumes all regular PPPoE activities.


Diagnostics

Figure 75. PPPoE Diagnostic Session Screen

Start Diagnostic Session

The purpose of this command is to display responses (content of PADO packets) from all ACs that can be accessed by the Vanguard at that moment. All received TAGs, which are normally invisible, shall be listed for each individual AC. If there is an active PPPoE session when this command is selected, the session is terminated with an appropriate warning. Diagnostic Sessions start with broadcasting a PADI packet with a blank Service-Name TAG. The content of each received PADO packet shall be displayed in order of arrival. Diagnostic Sessions may be terminated after a predetermined waiting period or by pressing the ESC key. An appropriate CTP mes-sage with the total number of received PADO packets shall be shown after a diagnostic session is completed and a new PPPoE session starts.

Command Action

Received:PADO Packet Delay: +0:00:00.300AC MAC Address: 00-60-08-31-CD-41 Ethernet Type: 0x8863Version: 01 Type: 01 Code: 0x07 Session ID: 0x0000 Length: 51TAG Type: 0x0102 (AC-Name) TAG Length: 7TAG Value: ac-nameTAG Type: 0x0101 (Service-Name) TAG Length: 12TAG Value: service-nameTAG Type: 0x0104 (AC-Cookie) TAG Length: 20TAG Value: A2 BD B1 29 8F EB 91 05 1F 60 87 2F 82 FA 8F 71 A1 08 00 00PADO Packet Delay: +0:00:00.305AC MAC Address: 00-60-08-31-CD-66 Ethernet Type: 0x8863Version: 01 Type: 01 Code: 0x07 Session ID: 0x0000 Length: 20TAG Type: 0x0102 (AC-Name) TAG Length: 4TAG Value: isp2TAG Type: 0x0101 (Service-Name) TAG Length: 8TAG Value: service2

Index

Index-1

A

Account Name 119Add Bandwidth Threshold 125Add Bandwidth Wait Time 125Adjacent Entity 140, 147Alarms 1Applications

Multilink PPP over ISDN 10PPP connection to a PSTN network 11Synchronous links on MP over ISDN 78

Authenticationbidirectional 73configuring 64None 66single direction 70

Authentication Methods 3, 6, 107Challenge Handshake Authentication

Protocol 6Password Authentication Protocol 6

Authentication Protocol 107, 120Auto Connect 126Auto Connect Retry Interval 126Auto dialer 8Auto Dialing 7

B

Bandwidth on Demand 7, 10, 85, 87BCP 5, 7, 74BRI ISDN 85

C

CCP 5, 8options 144, 149proprietary data compression 76state 143, 149

CHAP 6, 65, 66, 70, 72, 74, 76, 107, 116, 117, 120CHAP Secret 120Client Password/Secret 108Clock Source 103Clock Speed 104Compression Control Protocol 111, 123Connection 5Connection Type 101CRC errors 156

D

Data frames in/out 156Data Summary 141, 147dedicated link 9Dedicated Links 124Detailed Port Statistics

PPP port 136

Dial Management Summary 148Dial Numbers #1/Dial Numbers #2 124Dial on Demand 112, 148Dial-In Authentication Protocol 117

E

Encapsulation Type 111, 123Entity 156

F

Flow Control 102

I

Idle Disconnect 8, 125Idle Disconnect Timer 112Interface Summary 142IP Packets 149IPCP 5

options 109, 121, 122, 145, 149State 149state 145

IPCP Debug 131IPHC Debug 131IPX Packets 149IPXCP 5

options 110, 122, 123, 145, 149State 149state 145

ISDN 60, 74BRI 70, 74, 78, 85, 87Vanguard 58, 60

L

LCP 5options 143state 143

Line Interface 101, 102, 103, 104, 111, 112, 123Link 5Link Control Protocol 3, 5Link down 156Link Statistics 155Local IP Address 109, 122

M

Maximum Number of Auto Connect Attempts 126Maximum Number of Switched Links 124Maximum Serialization Delay When Voice is Not

Present 128Maximum Serialization Delay When Voice is

Present 127Minimum Segment Size 128MP 60

Index-2

MRU 96Multilink PPP 57, 60, 78, 104MultiLink PPP Over BRI 85, 86MultiLink PPP Over PRI 88Multilink PRI 8

N

NCP 5, 145Network Control Protocols 3, 5, 146

Bridging Control Protocol 5Compression Control Protocol 5Internet Packet Exchange Control Protocol 5Internet Protocol Control Protocol 5

Network Number 110, 123Network Protocols 108, 109, 110, 121, 122Network Services Feature Table 111Node Number 110, 123Number of Active Links 147, 148, 150

P

PAP 6, 65, 66, 107, 108, 116, 117, 120Permanent link 78Physical Summary 141Platforms

6520 85, 87Vanguard 312 70, 76, 78Vanguard 320 78

Point to Point Protocol 3suitability 3

Port Number 98Port Speed 140Port Statistics

Page 1 139Page 2 143Page 3 144

Port Status 140Port Type 98Powerup Dialing 8PPP Connection Statistics

Page 1 146Page 2 148Page 3 150

PPP Connections Statistics 146PPP Node Name 116PPP Operation 104, 105, 107, 108, 109, 110, 111,

112PPP over Ethernet (PPPoE) 12, 22

Configuration 93Diagnostics 161Statistics 157

PPP Parameters 116PPP Port 96, 97PPP Profile 78, 96, 118PPPoE Configuration Example 19PRI ISDN 87Priority (Prioritization) 127Proprietary Data Compression 111, 141, 147

Proprietary data compression 76

R

Reassembly Timeout (Class Out/In) 130Release 4.97 96Release 5. 96Remote Access to Multiple Locations 8Remote IP Address 109, 122Remove Bandwidth Wait Time 125Reserved Bandwidth 9RFC1334 6RFC1717 7Rx Queue Size (one entry for all classes) 129

S

Single Link PPP 57, 58authentication 65Power Up Dialing 8

Speed 156State 156State date/time 156state machine 5Stop Bits 104Summary of Associated Links 150

T

TCP Header Compression Max Slot Index 121TX CIR Kbit/sec rate (when none-zero) 127TX Queue Size Suspendable Classes 0-4 129TX Queue Size Suspendable Classes 10-14 130TX Queue Size Suspendable Classes 5-9 130Type subtype 156

U

Unnumbered IP 70, 72, 76, 78Utilization in/out 156

V

Van Jacobson compression 109Virtual Port Mapping 87Virtual PPP 125Virtual PPP Connection 140, 146, 148, 150

Vanguard Applications Ware Basic Protocols Point-to-Point ... · Point to Point Protocol (PPP) ... Challenge Handshake Authentication Protocol (CHAP) and Password Authentication Protocol

Documents