MALC Configuration Guide

MALC 723, MALC 719, and MALC 319

For software version 1.11.2

June 2005
Document Part Number: 830-00990-01
 Zhone Technologies
@Zhone Way
7001 Oakport Street
Oakland, CA 94621
USA
510.777.7000
www.zhone.com
[email protected]

COPYRIGHT ©2000-2005 Zhone Technologies, Inc. and its licensors. All rights reserved.
This publication is protected by copyright law. No part of this publication may be copied or
distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human
or computer language in any form or by any means, electronic, mechanical, magnetic, manual
or otherwise, or disclosed to third parties without the express written permission from Zhone
Technologies, Inc.
BAN, GigaMux, MALC, Raptor, SLMS, Z-Edge, Zhone, ZMS, and the Zhone logo are
trademarks of Zhone Technologies, Inc.
Zhone Technologies makes no representation or warranties with respect to the contents hereof
and specifically disclaims any implied warranties of merchantability, noninfringement, or
fitness for a particular purpose. Further, Zhone Technologies reserves the right to revise this
publication and to make changes from time to time in the contents hereof without obligation of
Zhone Technologies to notify any person of such revision or changes.

2 MALC Configuration Guide

CONTENTS

What’s new in this release .......................................................................................9

Style and notation conventions..............................................................................9
Typographical conventions.....................................................................................10
Acronyms....................................................................................................................10
Related documentation...........................................................................................11
Contacting Global Service and Support.............................................................12
Technical support....................................................................................................12
Service requirements...............................................................................................12

Chapter 1 Basic Configuration..............................................................................................13

Configuration overview...........................................................................................13
MALC default configuration ..................................................................................14
Logging into the serial (craft) port.......................................................................15
Configuring a management interface..................................................................16
Uplink card 10/100 BaseT Ethernet interface.........................................................16
ATM management connection................................................................................18
Managing the MALC with ZMS.............................................................................19

Chapter 2 MALC ATM overview ............................................................................................21

ATM overview ............................................................................................................21
ATM data .....................................................................................................................22
ATM voice ...................................................................................................................22
ATM Video ..................................................................................................................23
Cross connects .........................................................................................................23
Early packet discard (EPD) and partial packet discard (PPD)......................24
Usage parameter control (UPC)............................................................................24
ATM validation...........................................................................................................24
VPI and VCI ranges ..................................................................................................24
Virtual channel and virtual path links .................................................................25
Service categories....................................................................................................26
Constant bit rate (CBR) ..........................................................................................26

MALC Configuration Guide 3

Contents

Non-real-time variable bit rate (nrt-VBR) ..............................................................26

Real-time variable bit rate (rt-VBR) .......................................................................27
Unspecified bit rate (UBR) .....................................................................................27
Traffic descriptors ....................................................................................................27
Configuring PCR and SCR .....................................................................................27
Traffic descriptor parameters..................................................................................28
Traffic descriptor configuration rules .....................................................................30
Connection admission control (CAC) .................................................................30
CAC oversubscription.............................................................................................31
Bandwidth allocation for ATM cards .....................................................................31
Example CAC calculation.......................................................................................33
ATM traffic policing..................................................................................................33
Enforcing SCR and MBS........................................................................................33
Enforcing PCR and CDVT .....................................................................................34
General policing rules .............................................................................................34
ATM statistics ............................................................................................................34

Chapter 3 ATM Data Configuration .....................................................................................37

Configuration overview...........................................................................................37
Overview .....................................................................................................................38
VPI/VCI ranges...........................................................................................................38
Changing VPI/VCI ranges ......................................................................................38
Configuration overview ..........................................................................................39
Configuring PCR and SCR values........................................................................40
Creating traffic descriptors....................................................................................43
Creating VCLs and VPLs ........................................................................................46
Creating cross connects ........................................................................................50
Subtending .................................................................................................................52

Chapter 4 Configuring IP .........................................................................................................57

IP Overview ................................................................................................................57
DNS.........................................................................................................................58
DHCP......................................................................................................................58
RIP ..........................................................................................................................59
Applications ...............................................................................................................59
Routing....................................................................................................................60
Host-based and network-based routing ............................................................60
Host-based routing with DSL bridges.....................................................................61
Host-based routing with DSL routers .....................................................................62
Network-based routing with DSL bridges ..............................................................63
Network-based routing with DSL routers...............................................................63
IP filtering ..............................................................................................................64
Unnumbered IP interfaces.......................................................................................65

4 MALC Configuration Guide

 IP provisioning procedures ...................................................................................66
Configuring a management IP interface .................................................................66
Configuring host-based routing ..............................................................................67
Configuring network-based routing........................................................................74
Configuring RIP .....................................................................................................77
Configuring static routes.........................................................................................77
Adding routes ...................................................................................................77
Configuring the device as a DHCP server ..............................................................78
DHCP server profiles and scope ......................................................................78
Setting DHCP server options ...........................................................................79
Creating DHCP server subnet options..............................................................81
Enabling a DHCP server ..................................................................................83
DHCP relay.............................................................................................................84
Advanced IP provisioning procedures ...............................................................86
Advanced DHCP applications ................................................................................86
Creating dhcp-server-group profile ..................................................................87
Creating dhcp-server-host profile.....................................................................87
Configuring DNS resolver ......................................................................................88
Configuring IP filters ..............................................................................................90
Configuring the MALC for IP video......................................................................93
IP administrative procedures ................................................................................97
Modifying profiles created by host/interface add commands.................................97
Displaying hosts....................................................................................................100
Displaying interfaces ............................................................................................100
Displaying routing information.............................................................................100
Displaying the routing table ...........................................................................100
Displaying RIP information ...........................................................................101
Deleting hosts........................................................................................................101
Deleting interfaces ................................................................................................102
Deleting routes ......................................................................................................102
DHCP logging.......................................................................................................102
Understanding DHCP server log messages....................................................103

Chapter 5 Bridging ...................................................................................................................105

Overview ...................................................................................................................105
Broadcasts and bridging ......................................................................................106
VLANs ........................................................................................................................107
Untagged bridging..................................................................................................110
Ethernet RPR ...........................................................................................................112
Overview...............................................................................................................112
RPR ring topology..........................................................................................112
RPR ring topology with redundant GigE cards..............................................114
RPR ring topology with redundant GigE cards and subtended MALCs........116
RPR configuration ................................................................................................117
Linear GigaBit Ethernet ........................................................................................126
GigE-2 Uplink card redundant configuration in linear topology..........................128

MALC Configuration Guide 5

Contents

GigE-2 card bridging ............................................................................................129

Advanced bridging configurations ....................................................................131
Bridge configuration groups and records (Option 82 and Forbid OUI) ..............131
Tagged bridge—VLANs.......................................................................................133
Broadcast suppression...........................................................................................134
Administrative commands ...................................................................................135
Bridge delete command ........................................................................................135
Bridge show/showall commands ..........................................................................135

Chapter 6 Provisioning GR-303 or V5.2 Interface Groups ......................................137

Configuring a GR-303 interface .........................................................................137
Modifying a GR-303 interface group ...................................................................141
Configuring a V5.2 interface ................................................................................143
Creating a V5.2 interface group............................................................................146
Finding the line group identifiers of the physical connection...............................147
Provisioning V5.2 links ........................................................................................148
Adding C-channels within links............................................................................150
Provisioning C-paths.............................................................................................152
Activating the V5.2 IG..........................................................................................153
Modifying the v52-interface-group profile...........................................................154

Chapter 7 Adding Voice Connections..............................................................................155

Overview ...................................................................................................................155
Updating system settings ....................................................................................156
Setting a-law or mu-law and DSP settings (POTS) ..............................................156
Checking bandwidth before accepting a voice call (AAL2).................................156
Creating voice connections.................................................................................158
AAL2 connections ................................................................................................158
DS1 voice gateway connections ...........................................................................160
Voice over IP (VOIP) voice gateway connections ...............................................162
DS1 to POTS connections ....................................................................................166
Configuring CES connections ............................................................................168
Creating CES connections ....................................................................................170
CES signaling .................................................................................................170
CES clocking..................................................................................................171
CES configuration.................................................................................................172
Additional VOIP features ......................................................................................184
Configuring huntgroups ........................................................................................187
SIP dialing plans ...................................................................................................191
Malicious caller.....................................................................................................193
Additional voice features......................................................................................193

6 MALC Configuration Guide

Chapter 8 Voice Gateway Connections...........................................................................199
Overview ...................................................................................................................199
Configuring voice gateway connections .........................................................200
VOIP to voice gateway connections .....................................................................201
Overview ........................................................................................................202
Deleting voice gateway host and voice connection........................................205
Deleting voice connection ..............................................................................205
Subtended MALC POTS VOIP voice gateway connections................................205
Overview ........................................................................................................206
Deleting subtended voice connection ............................................................207
AAL2 voice gateway connections ........................................................................208
Overview ........................................................................................................208
Deleting voice connection ....................................................................................217
Subtended MALC ISDN or POTS voice gateway connections............................217
Configuring subtended AAL2 voice connection ...........................................218

Chapter 9 Diagnostics and Administration ...................................................................221

Logging .....................................................................................................................221
Overview...............................................................................................................221
Enabling/disabling logging ...................................................................................222
Log message format..............................................................................................222
Modifying logging levels......................................................................................223
Using the log cache...............................................................................................224
Examples ........................................................................................................225
Viewing the persistent logs...................................................................................225
Sending messages to a syslog server ....................................................................226
Specifying different log formats for system and syslog messages .......................227
Example log messages ..........................................................................................229
DSL line down message .................................................................................229
Slot card up message ......................................................................................229
SNMP..........................................................................................................................229
Creating SNMP community names and access lists .............................................230
Creating a community profile.........................................................................230
Creating community access lists ....................................................................230
Configuring traps ..................................................................................................231
Statistics and alarms .............................................................................................232
Bulk statistics ........................................................................................................232
Bulk statistics file format ...............................................................................233
Alarm manager......................................................................................................236
Supported alarms............................................................................................237
System maintenance .............................................................................................245
MALC file system.................................................................................................245
Accessing the flash card .................................................................................246
Using the ata command ..................................................................................246
Using the image command .............................................................................246
Changing the serial craft port settings ..................................................................247

MALC Configuration Guide 7

Contents

Deleting card profiles............................................................................................248

Manually binding interfaces ................................................................................248
Renaming interfaces..............................................................................................250
Saving and restoring configurations .....................................................................250
SNTP ..............................................................................................................251
User accounts ........................................................................................................252
Adding users...................................................................................................252
Changing default user passwords ...................................................................253
Deleting users .................................................................................................253
Deleting the admin user account ....................................................................253
Resetting passwords .......................................................................................254
Viewing chassis and slot information ...................................................................254
Controlling Telnet access......................................................................................255
Testing.......................................................................................................................257
Activating or deactivating interfaces ....................................................................257
BER tests...............................................................................................................258
IMA test pattern procedure ...................................................................................259
Loopbacks .............................................................................................................263
T1 loopbacks ..................................................................................................263
SONET loopbacks..........................................................................................265
DS3 loopbacks................................................................................................266
ISDN loopbacks .............................................................................................267
Viewing IMA group status....................................................................................268

Index ....................................................................................................................................................271

8 MALC Configuration Guide

ABOUT THIS GUIDE

This guide is intended for use by installation technicians, system

administrators, network administrators. It describes how to configure voice,
data, and video services on the MALC. For hardware installation, refer to the
MALC Hardware Installation Guide.

What’s new in this release

The following information is new in this manual:
• Bridging on page 105 explains how to configure bridge intralinks.
• Ethernet RPR on page 112 explains how to provision Resilient Packet
Ring (RPR) connections.
• Linear GigaBit Ethernet on page 126 explains how to configure linear
(non-RPR) GigaBit Ethernet connections with the GigE-2 card.
• Configuring CES connections on page 168 explains how to configure
CES over IP.
• Voice Gateway Connections on page 199 explains how to configure the
voice connections on the Voice Gateway card.

Style and notation conventions

The following conventions are used in this document to alert users to
information that is instructional, warns of potential damage to system
equipment or data, and warns of potential injury or death. Carefully read and
follow the instructions included in this document.

Caution: A caution alerts users to conditions or actions that could

damage equipment or data.

Note: A note provides important supplemental or amplified

information.

MALC Configuration Guide 9

About This Guide

Tip: A tip provides additional information that enables users to more

readily complete their tasks.

WARNING! A warning alerts users to conditions or actions that

could lead to injury or death.

WARNING! A warning with this icon alerts users to conditions or

actions that could lead to injury caused by a laser.

Typographical conventions

The following typographical styles are used in this guide to represent specific
types of information.

Bold Used for names of buttons, dialog boxes, icons, menus,

profiles when placed in body text, and property pages (or
sheets). Also used for commands, options, parameters in
body text, and user input in body text.
Fixed Used in code examples for computer output, file names, path
names, and the contents of online files or directories.

Fixed Bold Used in code examples for text typed by users.

Fixed Bold Used in code examples for variable text typed by users.
Italic

Italic Used for book titles, chapter titles, file path names, notes in
body text requiring special attention, section titles,
emphasized terms, and variables.

PLAIN UPPER Used for environment variables.

CASE

Acronyms
The following acronyms are related to Zhone products and may appear
throughout this manual:

Table 1: Acronyms and their descriptions

Acronym Description

ADSL Asymmetrical digital subscriber line

ARP Address resolution protocol

ATM Asynchronous Transfer Mode

BAN Broadband Access Node

10 MALC Configuration Guide

 Related documentation

Table 1: Acronyms and their descriptions (Continued)

Acronym Description

CID Channel identifier

DSL Digital subscriber line

SHDSL Symmetric high-bit-rate digital subscriber line

IAD Integrated access device

MALC Multi-access line concentrator

MIB Management information bases

MTAC Metallic Test Access Card

MTAC-FC Metallic Test Access Card with fan controller

PBX Private branch exchange

POTS Plain old telephone service

RIP Routing Information Protocol

SDSL Symmetric digital subscriber line

SHDSL Symmetric high-bit-rate digital subscriber line

SLMS Single Line Multi-Service

SNMP Simple Network Management Protocol

TFTP Trivial File Transfer Protocol

VCI Virtual channel identifier

VCL Virtual channel link

VPI Virtual path identifier

ZMS Zhone Management System

Related documentation
Refer to the following publication for additional information:
MALC Hardware Installation Guide—explains how to install the MALC
system and cards, and how to provision the physical interfaces.
Zhone CLI Reference Guide—explains how to use the Zhone command line
interface (CLI) and describes the system commands and parameters.
Refer to the release notes for software installation information and for
changes in features and functionality of the product (if any).

MALC Configuration Guide 11

About This Guide

Contacting Global Service and Support

Contact Global Service and Support (GSS) if you have any questions about
this or other Zhone products. Before contacting GSS, make sure you have the
following information:
• Zhone product you are using
• System configuration
• Software version running on the system
• Description of the issue

Technical support

If you require assistance with the installation or operation of your product, or

if you want to return a product for repair under warranty, contact GSS. The
contact information is as follows:

E-mail [email protected]
Telephone (North America) 877-ZHONE20
Telephone (International) 510-777-7133
Internet www.zhone.com/support

If you purchased the product from an authorized dealer, distributor, Value

Added Reseller (VAR), or third party, contact that supplier for technical
assistance and warranty support.

Service requirements

If the product malfunctions, all repairs must be performed by the

manufacturer or a Zhone-authorized agent. It is the responsibility of users
requiring service to report the need for service to GSS.

12 MALC Configuration Guide

1
BASIC CONFIGURATION

This chapter describes how to perform the basic configuration of the MALC,
including how to modify the default settings for the Uplink cards and how to
enable slot cards. It includes the following sections:
• Configuration overview, page 13
• Logging into the serial (craft) port, page 15
• Configuring a management interface, page 16

Configuration overview
Note: For redundant systems, you must configure the physical
interfaces on both the active and standby cards. In addition, you must
manually keep the configuration of the physical interfaces on the
active and standby cards in sync.

The following table describes where to find the information you need to
configure the MALC.

Feature See

ADSL The MALC Hardware Installation Guide.

ATM cross connects Creating cross connects on page 50.

ATM data MALC ATM overview on page 21 and ATM Data

Configuration on page 37

ATM traffic Creating traffic descriptors on page 43.

descritptors

ATM VCLs and VPLs Creating VCLs and VPLs on page 46.

Bridging Bridging on page 105

Clocking The MALC Hardware Installation Guide.

DS3/E3 Uplink card The MALC Hardware Installation Guide.

Ethernet interface The MALC Hardware Installation Guide.

GigaBit Ethernet The MALC Hardware Installation Guide.

MALC Configuration Guide 13

Basic Configuration

Feature See

GR-303 Provisioning GR-303 or V5.2 Interface Groups on

page 137
IMA groups The MALC Hardware Installation Guide.

IP Configuring IP on page 57.

IP video Configuring the MALC for IP video on page 93.

Linear GigaBit Linear GigaBit Ethernet on page 126

Ethernet

Management interface Configuring a management interface on page 16.

MTAC/Ring card The MALC Hardware Installation Guide.

OC-3c/STM1 and The MALC Hardware Installation Guide.

OC-12c/STM4

PON The MALC Hardware Installation Guide.

POTS The MALC Hardware Installation Guide.

RPR Ethernet RPR on page 112.

SHDSL card The MALC Hardware Installation Guide.

Slot cards The MALC Hardware Installation Guide.

SNMP SNMP on page 229.

Subtending Subtending on page 52.

T1/E1 CES Configuring CES connections on page 168.

T1/E1 IMA and TDM The MALC Hardware Installation Guide.

Uplink cards

V5.2 interface groups Configuring a V5.2 interface on page 143.

VDSL The MALC Hardware Installation Guide.

VLANs VLANs on page 107.

Voice Adding Voice Connections on page 155.

MALC default configuration

This default configuration of the MALC is as follows:

• Administrative user name is admin, password is zhone.
• Slot cards (except the Uplink card) must be enabled in a card-profile
before they will boot up.
• A single record for the Ethernet interface on the Uplink card exists. No
other profiles to configure physical interfaces exist.

14 MALC Configuration Guide

 Logging into the serial (craft) port

• A default system profile 0 exists with the following configuration:

– Authentication traps are not enabled
– ZMS communication is not configured

Logging into the serial (craft) port

Note: Do not use the serial craft port of a standby card to modify its
configuration.

The MALC unit provides an out-of-band RS232 D serial (craft) interface for
managing the unit. To access the serial port, configure your terminal interface
software with the following settings:
• 9600bps
• 8 data bits
• No parity
• 1 stop bit
• No flow control

Tip: The serial (craft) port settings can be changed by modifying the
rs232-profile.

You must perform the initial configuration of the system using the serial
(craft) interface. After you have completed the initial configuration, you can
manage the MALC unit over the network through a telnet session over the
Ethernet interface or over the management PVC.

Note: The MALC supports 6 concurrent management sessions, 5

telnet sessions and a single local session through the serial (craft)
port.

Logging in and out of the system

Log into the system (the default user name is admin, the default password
is zhone):
login:admin
password:
zSH>

To log out of the system, enter the logout command:

zSh> logout

MALC Configuration Guide 15

Basic Configuration

Tip: The system automatically logs you out after a period of

inactivity. The default logout time is 10 minutes, but can be changed
with the timeout command. Refer to the Zhone CLI Reference Guide
for information on the timeout command.

Enabling and disabling logging

By default logging is enabled on the serial craft port and disabled over
telnet sessions. To enable or disable logging for the session, using the
following command:
zSh> log session on | off
The log session command only applies to the current session. You can
also enable or disable logging for all serial craft port sessions using the
following command:
zSh> log serial on | off
This command setting persists across system reboots.

Configuring a management interface

This section describes how to configure the following interfaces to remotely
manage the MALC:
• Uplink card 10/100 BaseT Ethernet interface on page 16
• ATM management connection on page 18
• Managing the MALC with ZMS on page 19

Uplink card 10/100 BaseT Ethernet interface

The MALC has a 10/100 BaseT Ethernet interface on the Uplink card. The
ip-interface-record for the Uplink card is named ethernet1. This interface is
shared between the two Ethernet ports on redundant Uplink cards (if they
exist). The system can be reached using the address configured in the
ethernet1 ip-interface-record, no matter which card is active.

Caution: The Uplink card Ethernet interface must be configured

before any other interfaces on the system, even if you do not intend to
manage the unit over the Ethernet.

Configuring the Ethernet IP interface

The following example configures the IP address for the system:
zSH> interface add 1-1-1-0/ethernetcsmacd static 192.168.8.21 255.255.255.0
Created ip-interface-record ethernet1/ip

16 MALC Configuration Guide

 Configuring a management interface

Note: If you have problems with IP interfaces not automatically

binding, refer to for more information.

Verifying the interface

Use the interface show command to verify that the Ethernet interface was
configured correctly:
zSH> interface show
Interface Status Rd/Address Media/Dest Address IfName
---------------------------------------------------------------------------
1/1/1/0/ip UP 1 192.168.8.21/24 00:01:47:65:02:f2 1-1-1-0

Creating a default route

The following example creates a default route using the gateway
192.168.8.1 with a cost of 1 (one):
route add default 192.168.8.1 1

Verifying the route

Use the route show command to verify that the routes were added:
zSH> route show
Dest Nexthop Cost Owner
------------------------------------------------------------
0.0.0.0/0 192.168.8.1 1 STATICLOW
192.168.8.0/24 1/1/1/0/ip 1 LOCAL

Use the ping command to verify connectivity to the default gateway:

zSH> ping 192.168.8.1
PING 192.168.8.1: 64 data bytes
!!!!!
----192.168.8.1 PING Statistics----
5 packets transmitted, 5 packets received
round-trip (ms) min/avg/max = 0/0/0

To stop the ping, press CTRL+C.

Adding a route to the remote LAN

After creating the IP interface, you might need to create a route to the
remote device’s LAN interface using the route add command. The
command uses the following syntax:
route add destination mask next-hop cost

For example, in the following configuration, add a route to the

192.168.10.0 network using the MALC Uplink interface as the gateway.

MALC Configuration Guide 17

Basic Configuration

Figure 1: Adding a remote route to LAN

ATM

192.168.8.21 192.168.8.1
192.168.10.0

route add 192.168.10.0 255.255.255.0 192.168.8.1 1

ATM management connection

The MALC can terminate an ATM PVC and route it over an Ethernet
interface for management traffic.
The following table summarizes the configuration tasks for creating an ATM
management connection.

Task Command

Create a traffic descriptor. See new atm-traf-descr index

Creating the ATM traffic descriptor Multiple connections can use the same traffic descriptors and a single VCL
on page 18. must use the same traffic descriptor for both transmit and receive.

Create the VCL. See Creating the interface add interface/atm vc vpi/vci td td_index
ATM management VCL on page 19. static IpAddress Netmask
This command creates the ATM VCL and the IP interface for the
management PVC.

Add a route to the Ethernet route add destination netmask nexthop cost
interface. See Adding a default This enables the MALC to route from the IP management interface to the
route to the ATM network on Ethernet interface
page 19.

Creating the ATM traffic descriptor

Create a new atm-traf-descr profile and specify a unique index:
zSH> new atm-traf-descr 200
Please provide the following: [q]uit.
td_type: ------------- {atmNoClpNoScr}: enter traffic descriptor type
td_param1: ----------- {0}: enter PCR
td_param2: ----------- {0}: enter PCR (for CLP=0 traffic) or SCR
td_param3: ----------- {0}: enter MBS
td_param4: ----------- {0}: enter CDVT
td_param5: ----------- {0}:
cac-divider: -------------> {1}:
td_service_category: - {ubr}: rtvbr | nrtvbr | ubr | cbr
td_frame_discard: --------> {false}:
usage-parameter-control: -> {true}:

18 MALC Configuration Guide

 Configuring a management interface

....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Creating the ATM management VCL

The following example configures an ATM connection with a VPI/VCI of
0/35 that uses the atm-traf-descr profile you just configured (with an
index of 200). The VCL uses the Uplink interface:
zSH> interface add uplink1/atm vc 0/35 td 200 static 192.168.1.1 255.255.255.0
Created ip-interface-record uplink1-0-35/ip

This command creates the ip-interface-record and the associated VCL:

zSH> list ip-interface-record
ip-interface-record ethernet1/ip
ip-interface-record uplink1-0-35/ip
2 entries found.

zSH> list atm-vcl

atm-vcl uplink1/atm/0/35
1 entry found.

Adding a default route to the ATM network

After adding the IP interface for management, create a default route to the
ATM network:
route add default 192.168.1.254 1

Verifying the interface

Use the interface show command to verify that the interfaces are active:
zSH> interface show
Interface Status Rd/Address Media/Dest Address IfName
---------------------------------------------------------------------------------
1/1/1/0/ip UP 1 192.168.8.21/24 08:00:3e:03:02:01 1-1-1-0
1/1/2/0/ip UP 1 192.168.1.1/24 0/35 uplink1-0-35
---------------------------------------------------------------------------------
2 interfaces

Managing the MALC with ZMS

Note: For details on using ZMS, refer to the ZMS Administrator's

Guide and the NetHorizhon User's Guide.

The system profile contains parameters that configure the system contact
information for the MALC and connection information for the ZMS. This
profile does not need to be modified in order to manage the MALC with ZMS.

MALC Configuration Guide 19

Basic Configuration

CLI provisioning and ZMS

CLI configuration of a device being managed by the ZMS is disabled by
default. Attempting to configure the device results in an error:
zSH> update system 0
Provisioning via CLI is currently not available.
If you need to configure the device from the CLI, use the resetcliprov
command.
If you plan to use a script to provision the device from the CLI while it is
being managed by the ZMS:
1 Update the system profile to disable partial config syncs to ZMS:
zSH> update system 0
Please provide the following: [q]uit.
syscontact: ----------> {Zhone Global Services and Support 7001 Oakport
Road Oakland Ca. (877) Zhone20 (946-6320) Fax (510)777-7113
[email protected]}:
sysname: -------------> {Zhone MALC}:
syslocation: ---------> {Oakland}:
enableauthtraps: -----> {disabled}:
setserialno: ---------> {0}:
zmsexists: -----------> {true}: false
zmsconnectionstatus: -> {inactive}:
zmsipaddress: --------> {192.168.210.28}:
configsyncexists: ----> {false}:
configsyncoverflow: --> {false}:
configsyncpriority: --> {high}:
configsyncaction: ----> {noaction}:
configsyncfilename: --> {192.168.8.21_4_1014067321329}:
configsyncstatus: ----> {synccomplete}:
configsyncuser: ------> {cfgsync}:
configsyncpasswd: ----> {}: ** private **
numshelves: ----------> {1}:
shelvesarray: --------> {}:
numcards: ------------> {3}:
ipaddress: -----------> {192.168.8.21}:
alternateipaddress: --> {0.0.0.0}:
countryregion: -------> {us}:
primaryclocksource: --> {0/0/0/0/0}:
ringsource: ----------> {internalringsourcelabel}:
revertiveclocksource: -> {true}
voicebandwidthcheck: --> {false}
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

2 After the provisioning is complete, perform a full config sync from ZMS.

20 MALC Configuration Guide

2
MALC ATM OVERVIEW

This chapter describes ATM support on the MALC. It includes the following
sections:
• ATM overview, page 21
• ATM data, page 22
• ATM voice, page 22
• Cross connects, page 23
• Early packet discard (EPD) and partial packet discard (PPD), page 24
• Usage parameter control (UPC), page 24
• ATM validation, page 24
• VPI and VCI ranges, page 24
• Virtual channel and virtual path links, page 25
• Service categories, page 26
• Traffic descriptors, page 27
• Connection admission control (CAC), page 30
• ATM traffic policing, page 33
• ATM statistics, page 34

Note: Read this chapter before configuring your device.

ATM overview
The MALC supports voice, video, and data communications with different
networking requirements for each signaling type. Voice traffic is sensitive to
delay and transported by ATM Adaption Layer 2 (AAL2) at a Constant Bit
Rate (CBR). Data traffic is not sensitive to delay and is carried over ATM
Adaption Layer 5 (AAL5) at an Unspecified Bit Rate (UBR). Video streams
and video–on–demand applications use Variable Bit Rate–Real Time
(VBR-RT) over ATM Adaption Layer 5 (AAL5).

MALC Configuration Guide 21

MALC ATM overview

For VoATM traffic on the voice gateway card, ATM traffic destined for the
voice gateway card enters through one of the MALC uplink card’s ATM
interfaces and is terminated on the voice gateway card. It is sent as TDM
traffic to the local exchange switch.
Figure 2 illustrates ATM on the MALC.

Figure 2: ATM on the MALC

ATM

ATM

Local Exchange
Switch

Layer 3
IP

Layer 2
IP SAR ATM VCL/VPL ATM CC ATM VCL/VPL

Layer 1
IP DSL ATM UNI

Voice Gateway
ATM VCL/VPL TDM

ATM data
The MALC communicates with subscriber integrated access devices (IADs)
or DSL modems using ATM over DSL interfaces. The MALC relays the
traffic to the ATM Trunking card, which provides a high-speed interface to an
ATM network. The MALC can also terminate management traffic and route it
over the Ethernet to a management station.
The MALC supports LLC encapsulation for AAL5 connections that it
terminates.

ATM voice
For voice traffic, the MALC supports derived voice using AAL2 over DSL
interfaces. The ATM traffic is sent to the Uplink card, then onto the ATM
network.

22 MALC Configuration Guide

 ATM Video

On the MALC, voice is transported by ATM Adaption Layer 2 (AAL2) at a

Constant Bit Rate (CBR).
The MALC supports 120 AAL2 VCLs for POTS to AAL2 and ISDN to
AAL2 voice connections.
For VoATM traffic on the voice gateway card using VC-switching, the
maximum number of VCs that can be allocated to an individual VC-switched
VPI is determined by the zhoneAtmVpiMaxVci parameter in the atm-vpi
profile.
In VP-switching, the maximum VCI value that can be allocated to an
individual VP-switched VP on the voice gateway card is determined by the
zhoneAtmMaxVciPerVp parameter in the atm-vpi profile.

Note: For more information on ATM support for the Voice Gateway
card, see Voice Gateway Connections on page 199.

ATM Video
ATM video signaling has different networking requirements than voice and
data. Video streams and video–on–demand applications use Variable Bit
Rate–Real Time (VBR-RT) over ATM Adaption Layer 5 (AAL5).
Each video channel requires enough bandwidth to carry compressed video
plus the IP and ATM overhead. For example, if the video stream is 2.5 Mbps
with maximum packet size of 1316 bytes per packet, the formula for traffic
descriptor is as follows:
2500000 / 8 /1316 = 238 video packets per second
Total IP packet size = 1316 + 20 + 8 + 14 = 1358 bytes/packet
1358 bytes/packet / 48 bytes/cell = 28.333 cells/packet = 29 cells/packet
238 Packets/Sec * 29 Cells/Packet = 6902 cells/sec.
Therefore, the PCR on the traffic descriptor should be 7000.
If a system is deployed with 4 Video channels at 2.5 Mbps encoding, the
traffic descriptor should be:
4 * 7000 = 28000 cells/ sec rtvbr.

Cross connects
The MALC supports creating cross connects between any of its ATM-capable
ports.

MALC Configuration Guide 23

MALC ATM overview

Early packet discard (EPD) and partial packet discard (PPD)

In EPD, the ATM interface monitors the AAL5 traffic and discards an entire
data frame if its output buffers do not have the space to process it. In PPD, the
ATM interface drops the remaining cells of the frame if other cells of the
frame have already been dropped. Both of these techniques increase the
efficiency of the data transfer by dropping frames that have already been
determined to be errored and will have to be retransmitted. Both EPD and
PPD are disabled by default on the MALC.

Usage parameter control (UPC)

UPC is the process of monitoring and controlling the ATM traffic by
enforcing the traffic parameters. The MALC allows disabling of UPC on a
per-traffic descriptor basis. UPC is enabled by default.

ATM validation
The Zhone CLI performs the following validation on ATM configuration:
• VCLs cannot be created using VCIs in the reserved range (0 to 31), for
any VPI.
• VCLs being used in a cross connect cannot be deleted. To delete a VCL,
first delete the cross connect.
• ATM traffic descriptors used in VCLs cannot be modified.
• A VCL can be used in only one cross connect.

VPI and VCI ranges

The MALC supports configurable VPI/VCI ranges for all ATM-capable cards
except the T1/E1 32 port card. VPI/VCI ranges are configured in atm-vpi
records. Table 2 lists the VPI/VCI support for MALC cards.
Note the following about VPI/VCI ranges:
• After creating or modifying atm-vpi records, the card must be rebooted.
• A maximum of 256 VPIs can be created on a port.
As atm-vpi records are created, the system allocates connections from this
pool. Each VP-switched VP uses one connection and each VC-switched VP
uses one connection per allowable VC.

24 MALC Configuration Guide

 Virtual channel and virtual path links

Table 2: VPI/VCI ranges for MALC cards

Card Default ranges Supported ranges Maximum connections per

card

Uplink cards
DS3/E3 VPI: 0 to 3 VPI: 0 to 255 (per port) 16,384
VCI: 32 to 1,023 VCI: 32 to 4,095 (per VCI)

T1/E1 IMA and VPI: 0 to 3 VPI: 0 to 255 (per port) 16,384

T1/E1 ATM/TDM VCI: 32 to 511 VCI: 32 to 4,095 (per VCI)
OC-3c/STM1 and VPI: 0 to 7 VPI: 0 to 255 (per port) 16,384
OC-12c/STM4 VCI: 32 to 1,023 VCI: 32 to 4,095 (per VCI)

Line cards
DSL (except the VPI: 0 to 1 (per port) VPI: 0 to 255 (per port) 448 (VC-switched to Uplink)
ADSL 48 port VCI: 32 to 255 (per VCI) VCI: 32 to 1,023 (per VCI) 48 (VP-switched to Uplink)
card)

ADSL 48 port VPI: 0 to 11 (per port) VPI: 0 to 63 (per port) 448 (VC-switched to Uplink)
card VCI: 32 to 63 (per VCI) VCI: 32 to 63 (per VCI) 48 (VP-switched to Uplink)

PON OLT card VPI: 0 to 63 VPI: 0 to 255 448 (VC-switched to Uplink)

VCI: 32 to 255 VCI: 32 to 1,023 48 (VP-switched to Uplink)

T1/E1 12 CES VPI: 0 to 1 VPI: 0 to 255 (per port) 448 (VC-switched to Uplink)
VCI: 32 to 255 VCI: 32 to 1,023 (per VCI) 48 (VP-switched to Uplink)

T1/E1 ATM-32 VPI: 0 to 7 VPI: 0 to 7 224 (VC-switched to Uplink)

(per UNI interface or IMA VCI: 32 to 63 32 (VP-switched to Uplink)
group)
256 total per card
VCI: 32 to 63
(per UNI interface or IMA
group)

T1/E1 32VG VP-switched: VP-switched: 448 (VC-switched to Uplink)

VPI: 16 to 63 (per card) VPI: 16 to 63 (per card) 7,680 (VP-switched to
VCI: 32 to 8,192 (per card) VCI: 32 to 8,192 (per card) Uplink)
(no external ATM interface)

Virtual channel and virtual path links

The MALC supports both VC and VP switching. In VC switching, cells are
switched based on the VPI/VCI. In VP switching, cells are switched based on
the VPI only. The VCI remains the same on both the incoming and outgoing
interfaces.
A virtual channel link (VCL) used for VC switching. It is uniquely identified
by an index in the form interface-index/atm/VPI/VCI where:

MALC Configuration Guide 25

MALC ATM overview

• interface-index is the unique name or address of the ATM layer on a given

port. For example, 1-3-1-adsl/atm.
• VPI/VCI pair is a unique connection identifier on that port.
A virtual path link (VPL) is used for VP switching. It is uniquely identified by
an index in the form interface-index/atm/VPI where:
• interface-index is the unique name or address of the ATM layer on a given
port. For example, 1-3-1-adsl/atm.
• VPI is a unique connection identifier on that port.
VCLs/VPLs are provisioned according to RFCs 2514 and 2515. Each VCL/
VPL on the MALC requires a VCL or VPL record and an associated ATM
traffic descriptor.

Note: A VCL/VPL can be used in only one cross connect.

VCLs/VPLs being used in a cross connect cannot be deleted. To
delete a VCL/VPL, first delete the cross connect.
If a VCL/VPL is updated with a new traffic descriptor, the VCL/VPL
must be brought down, then back up to update the policing value.

Service categories
The MALC supports the following ATM service categories:
• constant bit rate (CBR)
• non-real-time variable bit rate (nrt-VBR)
• real-time variable bit rate (rt-VBR)
• unspecified bit rate (UBR)

Constant bit rate (CBR)

The CBR service category is used by connections that require a constant and
guaranteed cell rate during the lifetime of the connection. The sampling time
for CBR is constant, with no delay. Cells exceeding the provisioned PCR rate
are discarded.

Non-real-time variable bit rate (nrt-VBR)

The nrt-VBR service category is used by applications that are tolerant of

network delays and do not require a timing relationship on each side of the
connection. The nrt-VBR service supports somewhat bursty connections
having less-stringent delay requirements than rt-VBR and CBR, but still
require low cell loss. The source traffic descriptor is characterized by peak
cell rate (PCR), sustainable cell rate (SCR), and maximum burst size (MBS).

26 MALC Configuration Guide

 Traffic descriptors

Real-time variable bit rate (rt-VBR)

The rt-VBR service category is used by applications that require a tightly

constrained delay and delay variation. The source traffic descriptor is
characterized by peak cell rate (PCR), sustainable cell rate (SCR), and
maximum burst size (MBS).

Unspecified bit rate (UBR)

The UBR service category does not specify traffic-related guarantees. No

numerical commitments are made with respect to the cell loss ratio (CLR)
experienced by the connection, or the cell transfer delay (CTD) experienced
by the cells. With UBR service, the available bandwidth is fairly distributed to
the active UBR subscribers.

Traffic descriptors
Each ATM endpoint requires a traffic descriptor, which defines the traffic
parameters and type of service provided on ATM interfaces. Traffic
descriptors are configured in atm-traf-descr records.
Quality of Service (QoS) parameters such as max cell transfer delay
(maxCTD) and cell loss ratio (CLR) do not apply to a single node on the
network and so are not provisioned for individual VCs.

Configuring PCR and SCR

The atm-vcl-param profile defines the allowable values for the PCR and
SCR for certain traffic types. The values in this profile are used as follows:
• The SCR for rt-VBR traffic descriptors must use one of the first 16 rates
(vcl-rate-param1 through vcl-rate-param16)
• The PCR for CBR traffic descriptors can use any of the 32 rates.
• For a UBR traffic descriptor, if usage-parameter-control in an ATM
traffic descriptor is set to false, or if PCR is greater than modem trained
rate, then the UBR traffic is shaped to one of the 32 rates. The shaper will
pick a rate that is equal to or less than the modem trained rate. If there are
multiple rates less than the modem trained rate, the one closest to the
trained rate will be selected.
Each PVC on the MALC is assigned a PCR of 182 cells per second (for G.711
voice calls) or 91 CPS (for G.726 voice calls). An initial 182 CPS is needed to
support sending and receiving of CAS packets.
To support voice VCs use the following formulas:
For G.711 calls, use the formula:
• PCR = (CIDS per VC * 182) + 182

MALC Configuration Guide 27

MALC ATM overview

• SCR = (CIDS per VC * 3/5) + (CIDS per VC * 182)

For G.726, use the formula:
• PCR = (CIDS per VC * 91) + 91
• SCR = (CIDS per VC * 3/5) + (CIDS per VC * 91)
For example, 8 CID per VC produces the following values for PCR and SCR:
PCR=1638 CPSSCR=1460 CPS

Note: When fax and modems calls are connected on G.726 compress
mode, the full 182 CPS are used.

Traffic descriptor parameters

Table 3 shows the required parameters used to define MALC traffic

descriptors and the validation rules associated with them.
Table 3: ATM traffic descriptor parameters

Service TD type td_param1 td_param2 td_param3 td_param4

category

CBR atmNoClpNoScr PCR for CLP=0+1 Not used Not used Not used
UBR (TD type 2) traffic
OID 1.3.6.1.2.1.37.1.1.2 must be > 0
For CBR, must
match a value in
atm-vcl-param
profile

UBR atmClpTaggingNoScr PCR for CLP=0+1 PCR for CLP=0 Not used Not used
(TD type 4) traffic traffic, excess
OID 1.3.6.1.2.1.37.1.1.4 must be > 0 traffic tagged as
CLP=1
must be > 0
nrt-VBR atmClpNoTaggingScr PCR for CLP=0+1 SCR for CLP=0 MBS Not used
rt-VBR (TD type 6) traffic traffic must be > 1
OID 1.3.6.1.2.1.37.1.1.6 td_param1 > For rt-VBR, must
td_param2 match a value in
atm-vcl-param
profile
must be > 0

28 MALC Configuration Guide

 Traffic descriptors

Table 3: ATM traffic descriptor parameters (Continued)

Service TD type td_param1 td_param2 td_param3 td_param4

category

nrt-VBR atmClpTaggingScr PCR for CLP=0+1 SCR for CLP=0 MBS Not used
rt-VBR (TD type 7) traffic traffic, excess must be > 1
OID 1.3.6.1.2.1.37.1.1.7 td_param1 > traffic tagged as
td_param2 CLP=1
For rt-VBR, must
match a value in
atm-vcl-param
profile
must be > 0

CBR atmClpTransparentNoScr PCR CDVT Not used Not used

(TD Type 9) Must match a value must be > 0
OID 1.3.6.1.2.1.37.1.1.9 in atm-vcl-param
profile
must be > 0

nrt-VBR atmClpTransparentScr PCR for CLP=0+1 SCR for CLP=0 MBS CDVT
rt-VBR (TD Type 10) traffic traffic
OID 1.3.6.1.2.1.37.1.1.10 must be > 0 For rt-VBR, must
match a value in
atm-vcl-param
profile
must be > 0

CBR atmNoClpNoScrCdvt PCR CDVT Not used Not used

(TD Type 12) must be > 0 must be > 0
OID 1.3.6.1.2.1.37.1.1.12 Must match a value
in atm-vcl-param
profile

nrt-VBR atmClpNoTaggingScrCdvt PCR for CLP=0+1 SCR for CLP=0 MBS CDVT
rt-VBR (TD type 14) traffic traffic must be > 1
OID 1.3.6.1.2.1.37.1.1.14 td_param1 > For rt-VBR, must
td_param2 match a value in
atm-vcl-param
profile
must be > 0

nrt-VBR atmClpTaggingScrCdvt PCR for CLP=0+1 SCR for CLP=0 MBS CDVT
rt-VBR (TD type 15) traffic traffic, excess must be > 1
OID 1.3.6.1.2.1.37.1.1.15 td_param1 > traffic tagged as
td_param2 CLP=1
For rt-VBR, must
match a value in
atm-vcl-param
profile
must be > 0

MALC Configuration Guide 29

MALC ATM overview

Tip: Refer to the following specifications for more information about

traffic descriptors:
• ATM Forum, ATM User-Network Interface, Version 3.0 (UNI 3.0)
Specification, 1994.
• ATM Forum, ATM User-Network Interface, Version 3.1 (UNI 3.1)
Specification, November 1994.

Traffic descriptor configuration rules

Note: When configuring the traffic descriptors, it is important that

they follow the rules described in this section. A traffic descriptor
cannot be saved if the parameters violate these rules.

Note the following information about traffic descriptors on the MALC:

• ATM traffic descriptors used in active VCLs cannot be modified. To
modify a traffic descriptor, first bring down VCLs that use the descriptor.
• For atmNoClpNoScr with a service category of rtvbr, trnk-vcl-rate of
unused is allowed for backward compatibility. If set to unused, the
system uses a rate-16k for the purposes of CAC.

Connection admission control (CAC)

MALC Uplink cards support connection admission control (CAC) and
provisioning of oversubscription factors on a per port basis. The CAC
functions on the Uplink card will not accept new connections if they exceed
the remaining bandwidth. Note the following about CAC and service
categories:
• For CBR VCLs, the PCR value of each VCL is subtracted from the
available rt-VBR bandwidth to determine whether the VCL can be
created.
• For rt-VBR VCLs, the SCR value of each VCL is subtracted from the
available rt-VBR bandwidth to determine whether the VCL can be
created.
• For nrt-VBR VCLs, the SCR of each VCL is subtracted from the
available nrt-VBR bandwidth to determine whether the VCL can be
created.
• For UBR VCLs, CAC does not apply. The system will provide up to the
bandwidth configured for UBR connections, if the bandwidth is available.

30 MALC Configuration Guide

 Connection admission control (CAC)

CAC oversubscription

CAC enables the ATM interface to service more data VCL connections than
the bandwidth allows. Because not all connections are likely to be active at
the same time, an interface can support a larger number of PVCs.
When oversubscription is enabled, CAC calculates available bandwidth in the
system by dividing the SCR (for nrt-VBR or rt-VBR VCLs) value by the
cac-divider parameter in the atm-traf-descr. It then uses that value to
determine if the VCL can be created.
For example, to oversubscribe bandwidth at a rate of 4:1, set cac-divider to 4.
By default, oversubscription is not enabled and the cac-divider is set to 1.
Note that CAC oversubscription should not be used to oversubscribe AAL2
voice connections.

Bandwidth allocation for ATM cards

The bandwidth allocated to ATM traffic types and used by CAC is specified in
the card-atm-configuration parameter in the card-profile for the Uplink
cards. (See Table 4.)
Table 4: ATM bandwidth allocation

Setting DS3 E3 T1 E1 OC-3/STM1 OC-12/STM4

104,268 CPS 80,000 CPS 28,976 CPS 36,224 CPS 353,207 CPS 1,412,830 CPS
total (8 T1s)/ total (8 E1s)/
3622 each 4528 each

vbnrt95rt5
UBR 1% 1,042 CPS 800 CPS 289 CPS 362 CPS 3,532 CPS 14,128 CPS
nrt-VBR: 94% 98,011 CPS 75,200 CPS 27,237 CPS 34,050 CPS 332,014 CPS 1,328,060 CPS
CBR/rt-VBR: 5% 5,213 CPS 4,000 CPS 1,448 CPS 1,811 CPS 17, 660 CPS 70,642 CPS

vbnrt80rt15
UBR: 5% 5,213 CPS 4,000 CPS 1,448 CPS 1,811 CPS 17, 660 CPS 70,642 CPS
nrt-VBR: 80% 83,414 CPS 64,000 CPS 23,180 CPS 28,979 CPS 282,565 CPS 1,130,264 CPS
CBR/rt-VBR: 15% 15,640 CPS 12,000 CPS 4,346 CPS 5,433 CPS 52,981 CPS 211,925 CPS
vbnrt65rt30
UBR: 5% 5,213 CPS 4,000 CPS 1,448 CPS 1,812 CPS 17, 660 CPS 70,642 CPS
nrt-VBR: 65% 67,774 CPS 52,000 CPS 18,834 CPS 23,545 CPS 229,584 CPS 918,340 CPS
CBR/rt-VBR: 30% 31,280 CPS 24,000 CPS 8,692 CPS 10,867 CPS 105,962 CPS 423,849 CPS

vbnrt50rt45
UBR: 5% 5,213 CPS 4,000 CPS 1,448 CPS 1,811 CPS 17, 660 CPS 70,642 CPS
nrt-VBR: 50% 52,134 CPS 40,000 CPS 14,488 CPS 18,112 CPS 176,603 CPS 706,415 CPS
CBR/rt-VBR: 45% 46,920 CPS 36,000 CPS 13,039 CPS 16,300 CPS 158,943 CPS 635,774 CPS

MALC Configuration Guide 31

MALC ATM overview

Table 4: ATM bandwidth allocation (Continued)

Setting DS3 E3 T1 E1 OC-3/STM1 OC-12/STM4

104,268 CPS 80,000 CPS 28,976 CPS 36,224 CPS 353,207 CPS 1,412,830 CPS
total (8 T1s)/ total (8 E1s)/
3622 each 4528 each

vbnrt35rt60
UBR: 5% 5,213 CPS 4,000 CPS 1,448 CPS 1,811 CPS 17, 660 CPS 70,642 CPS
nrt-VBR: 35% 36,493 CPS 28,000 CPS 10,141 CPS 12,678 CPS 123,622 CPS 494,491 CPS
CBR/rt-VBR: 60% 62,560 CPS 48,000 CP 17,385 CPS 21,734 CPS 211,924 CPS 847,698 CPS

vbnrt20rt75
UBR: 5% 5,213 CPS 4,000 CPS 1,448 CPS 1,811 CPS 17, 660 CPS 70,642 CPS
nrt-VBR: 20% 20,853 CPS 16,000 CPS 5,795 CPS 7,244 CPS 70,641 CPS 282,566 CPS
CBR/rt-VBR: 75% 78,201 CPS 60,000 CPS 21,732 CPS 27,168 CPS 264,905 CPS 1,059,623 CPS

vbnrt5rt95
UBR: 1% 1,042 CPS 800 CPS 289 CPS 362 CPS 3,532 CPS 14,128 CPS
nrt-VBR: 5% 5,213 CPS 4,000 CPS 1,448 CPS 1,811 CPS 17, 660 CPS 70,642 CPS
CBR/rt-VBR: 94% 98,011 CPS 75,200 CPS 27,237 CPS 34,050 CPS 332,014 CPS 1,328,060 CPS

Table 5 shows the parameters used by CAC for specified service categories.
Table 5: Service category traffic descriptor parameters

Service category Parameters specified CAC

CBR td_param1 (peak cell rate (PCR)) td_param1

td_param2 (cell delay variation (PCR)
tolerance (CDVT))

nrt-VBR td_param1 (peak cell rate (PCR)) td_param2

td_param2 (sustained cell rate (SCR)) (SCR)
td_param3 (maximum burst size
(MBS))
td_param4 (cell delay variation
tolerance (CDVT))
rt-VBR td_param1 (peak cell rate (PCR)) td_param2
td_param2 (sustained cell rate (SCR)) (SCR)

td_param3 (maximum burst size

(MBS))
td_param4 (cell delay variation
tolerance (CDVT))

UBR td_param1 (peak cell rate (PCR)) N/A

32 MALC Configuration Guide

 ATM traffic policing

Example CAC calculation

The following is a sample calculation on DS3 Uplink card with a line speed of
104,268 CPS (the DS3 line rate of 45,000,000 bits/sec minus overhead) and
no oversubscription:
If the atm-configuration parameter is set to vbnrt20rt75, the ATM
bandwidth allocation is as follows:
104,268 * 0.20 = 20,853 CPS is allocated to nrt-VBR
104,268 * 0.75 = 78,201 CPS is allocated to rt-VBR
104,268 * 0.05 = 5,213 is allocated to UBR

Total bandwidth available for rt-VBR VCL 20,853 CPS

nrt-VBR VCL # 1 with SCR 12,000. Since -12,000 CPS
there is enough available bandwidth, CAC
allows the VCL
Remaining bandwidth for rt-VBR VCLS 8,853 CPS

nrt-VBR VCL # 2 with SCR of 9,000 -9000 CPS

VCL rejected by CAC, not enough available
bandwidth

For CBR or rt-VBR traffic, the CAC algorithm is the same.

ATM traffic policing

The MALC polices traffic using the ATM continuous-state leaky bucket
algorithm. It monitors the incoming ATM cells to ensure that they adhere to
the VCL traffic descriptors. If they do not, they are either dropped or tagged
with a lower cell loss priority (CLP), depending on which traffic descriptor is
in use for the VCL.

Tip: For more information about traffic policing, refer to ATM

Forum Traffic Management Specification Version 4.0 and ITU-T
I.371.

Enforcing SCR and MBS

Bucket B polices SCR and MBS parameters. It applies to the following TD

types:
• atmClp NoTagging Scr (TD type 6)
• atmClp Tagging Scr (TD type 7)
• atmClpNoTaggingScrCdvt (TD type 14)

MALC Configuration Guide 33

MALC ATM overview

• atmClpTagging ScrCdvt (TD type 15)

Bucket B uses the following formula:
cdvt_btB = 1,000,000/SCR + [(MBS - 1)*(1,000,000/SCR - 1,000,000/PCR)]
For these traffic descriptors, limit = cdvt_btB * F/68.
where F is
• 100 for MALC OC-3c/STM1 cards and MALC DS3/E3 cards
• 50 for DSL line cards and MALC T1/E1 IMA cards
Bucket B either drops or tags non-conforming cells, depending on the TD
type. It then passes the cells that have not been dropped to bucket A.

Enforcing PCR and CDVT

Bucket A polices PCR and CDVT parameters. It applies to all TD types.

Bucket A uses the following formula:
cdvt_btA = [(td_param2 or td_param4)/10.0]
where:
td_param2 is CDVT for CBR VCLs with the exception of AtmNoClpNoScr
traffic type
td_param4 is CDVT for rt-VBR VCLs
If the CDVT is not specified, the default value of 30000 (tenths of
microseconds) is used.
For these traffic descriptors, limit = cdvt_btA * F/68.
Bucket A drops cells that do not conform to the PCR.

General policing rules

ATM traffic descriptors must adhere to the following rules:

• The limit must be within the following range:
1 < limit < 1,966,080 (1.8751 * 0x100000)
• cdvt_btA and cdvt_btB must be greater than 68/F
where F is
• 100 for MALC OC-3c/STM1 cards and MALC DS3/E3 cards
• 50 for DSL line cards and MALC T1/E1 IMA cards

ATM statistics
Real-time ATM statistics on the MALC are provided through the
NetHorizhon ZMS client. ZMS supports the following ATM statistics:

34 MALC Configuration Guide

 ATM statistics

• ATM VCL
• ATM VPL
• AAL2
The ZMS performance manager periodically collects real-time statistical data.
You can monitor real-time data at a polling interval of your choice. For
information on how to access ZMS ATM statistics, refer to the NetHorizhon
User’s Guide and the NetHorizhon online help.

MALC Configuration Guide 35

MALC ATM overview

36 MALC Configuration Guide

3
ATM DATA CONFIGURATION

This chapter explains how to configure ATM cross connects on the MALC. It
includes the following sections:
• Configuration overview, page 37
• Overview, page 38
• VPI/VCI ranges, page 38
• Configuring PCR and SCR values, page 40
• Creating traffic descriptors, page 43
• Creating VCLs and VPLs, page 46
• Creating cross connects, page 50
• Subtending, page 52

Tip: For information about configuring ATM management

connections, see ATM management connection on page 18.
For important background information about ATM on the MALC, see
MALC ATM overview on page 21.

Configuration overview
This section provides an overview of how to configure MALC ATM data
connections references to where to find detailed information.
1. Modify the VPI/VCI ranges of the slot card, if necessary. See VPI/VCI
ranges on page 38.
2. Modify the allowable PCR and SCR values, if necessary. See Configuring
PCR and SCR values on page 40.
3. Create traffic descriptors. See Creating traffic descriptors on page 43.
4. Create VCLs or VPLs, as required.
– See Creating VCLs (VC switching) on page 48.
– See Creating VPLs (VP switching) on page 49
5. Create cross connects. See Creating cross connects on page 51.

Book Title 37
ATM Data Configuration

Overview
Figure 3 shows an overview of ATM on the MALC.

Figure 3: ATM cell relay on the MALC

ATM

ATM

Local Exchange
Switch

Layer 3
IP

Layer 2
IP SAR ATM VCL/VPL ATM CC ATM VCL/VPL

Layer 1
IP DSL ATM UNI

Voice Gateway
ATM VCL/VPL TDM

VPI/VCI ranges
The MALC supports configurable VPI/VCI ranges for all ATM-capable
cards. VPI/VCI ranges are configured in atm-vpi records.
Note the following about VPI/VCIs ranges:
• After creating or modifying atm-vpi records, the card must be rebooted.
• A maximum of 256 VPIs can be created on a port.
• As atm-vpi records are created, the system allocates connections from the
available pool of connections. Each VP-switched VP uses one connection
and each VC-switched VP uses one connection per allowable VC.

Changing VPI/VCI ranges

Note that although you can create switched VCs without modifying the VPI/
VCI ranges, if you create the first atm-vpi (to change the VPI/VCI ranges on
a card or to create a VP switched connection), the system automatically
creates an atm-vpi profile for each VPI used in existing cross connects.

38 Book Title
 VPI/VCI ranges

The system determines how many VCIs are assigned to each VPI, then
populates the zhoneAtmVpiMaxVci parameter in an atm-vpi record with the
value (in the form 2n) closest to that number. For example, if the system has
cross connects configured with the following VPI/VCI pairs:

VPI/VCI atm-vpi profile created Comment

VPI 0 VCI 100 atm-vpi interface-name/atm/0 zhoneAtmVpiMaxVci = 128 because 128 is
VPI 0 VCI 101 zhoneAtmVpiMaxVci: ---> {128} the smallest power of 2 that is greater than
VPI 0 VCI 102 the highest VCI (102) created using that VPI.
zhoneAtmVpiSwitched: -> {vc}

VPI 1 VCI 1001 atm-vpi interface-name/atm/1 zhoneAtmVpiMaxVci = 1024 because 1024

VPI 1 VCI 1001 zhoneAtmVpiMaxVci: ---> {1024} is the smallest power of 2 that is greater than
VPI 1 VCI 1002 the highest VCIs (1004) created using that
VPI 1 VCI 1003 zhoneAtmVpiSwitched: -> {vc} VPI.
VPI 1 VCI 1004

After the atm-vpi records have been created, you can update them to change
the default VCI values, if desired.

Configuration overview

The following table summarizes the configuration tasks for changing the VPI/
VCI ranges.

Task Command

Create an atm-vpi record. This specifies the maximum new atm-vpi index/atm/vpi
number of switched VCs on that connection (or 0 for Up to 256 VPIs can be created on a port.
VP switching) as well as whether the connection is VP
or VC switched.

Update the atm-vpi records if you want to change the update atm-vpi index/atm/vpi
default atm-vpi records the system creates.
Reboot the card. slotreboot slot

Changing VPI/VCI ranges

1 Create an atm-vpi record for the VP:
– If the VP is going to be switched, leave zhoneAtmVpiMaxVci at 0.
– If the VC is going to be switched, change zhoneAtmVpiMaxVci to
the number of VCs for that VP. Note that the value must be a power of
2 greater than 31.
The following example creates VPI 10 on an OC3-c/STM1 card, with
1024 allowable VCs:

Book Title 39
ATM Data Configuration

zSH> new atm-vpi 1-1-1-0-sonet/atm/10 interface-index/atm/

VPI
Please provide the following: [q]uit.
zhoneAtmVpiMaxVci: ---> {0}: 1024
zhoneAtmVpiSwitched: -> {vc}:
zhoneAtmMaxVciPerVp: -> {0}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

After the first atm-vpi record is saved, the system will automatically
create atm-vpi records for all VPIs used in existing cross connects. If you
need to modify the atm-vpi records the system has automatically created,
update the records as in the following example:
zSH> update atm-vpi 1-1-2-0-sonet/atm/11 interface-index/
atm/VPI
Please provide the following: [q]uit.
zhoneAtmVpiMaxVci: ---> {1024}: 2048
zhoneAtmVpiSwitched: -> {vc}:
zhoneAtmMaxVciPerVp: -> {0}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

2 After the system has finished creating the atm-vpi records and you have
finished updating them (if desired), reboot the slot card:
zSH> slotreboot 1

Configuring PCR and SCR values

The atm-vcl-param profile defines the allowable values for the PCR and
SCR for certain traffic types. The values in this profile are used as follows:
• The SCR for rt-VBR traffic descriptors must use one of the first 16 rates.
• The PCR for CBR traffic descriptors can use any of the 32 rates.
• For a UBR traffic descriptor, if usage-parameter-control in an ATM
traffic descriptor is set to false, or if PCR is greater than modem trained
rate, then the UBR traffic is shaped to one of the 32 rates. The shaper will
pick a rate that is equal to or less than the modem trained rate. If there are
multiple rates less than the modem trained rate, the one closest to the
trained rate will be selected.

Note: If your device is being managed by ZMS, changes to the

atm-vcl-param profile should be made using ZMS. If you use the
CLI to change the profile, perform a full config sync update after
making the change.

Note the following about the values in this profile:

40 Book Title
 Configuring PCR and SCR values

• Rates are in cells per second (CPS)

• Duplicate rates are not permitted
• Rates must be in ascending order within the first 16 rates and also within
the second 16 rates.
To view the default values for the atm-vcl-param profile use the get
command:
zSH> get atm-vcl-param 0
vcl-rate-param1: -------> {38}
vcl-rate-param2: -------> {76}
vcl-rate-param3: -------> {151}
vcl-rate-param4: -------> {189}
vcl-rate-parma5: -------> {302}
vcl-rate-param6: -------> {378}
vcl-rate-param7: -------> {604}
vcl-rate-param8: -------> {755}
vcl-rate-param9: -------> {1208}
vcl-rate-param10: ------> {1510}
vcl-rate-param11: ------> {3661}
vcl-rate-param12: ------> {4825}
vcl-rate-param13: ------> {28302}
vcl-rate-param14: ------> {37736}
vcl-rate-param15: ------> {106133}
vcl-rate-param16: ------> {365567}
vcl-rate-grp2-param1: --> {2264}
vcl-rate-grp2-param2: --> {3019}
vcl-rate-grp2-param3: --> {4151}
vcl-rate-grp2-param4: --> {7075}
vcl-rate-grp2-param5: --> {9434}
vcl-rate-grp2-param6: --> {11792}
vcl-rate-grp2-param7: --> {14151}
vcl-rate-grp2-param8: --> {16509}
vcl-rate-grp2-param9: --> {18868}
vcl-rate-grp2-param10: -> {23585}
vcl-rate-grp2-param11: -> {33019}
vcl-rate-grp2-param12: -> {56604}
vcl-rate-grp2-param13: -> {75472}
vcl-rate-grp2-param14: -> {150943}
vcl-rate-grp2-param15: -> {226415}
vcl-rate-grp2-param16: -> {301887}

Table 6 explains the atm-vcl-param default settings.

Book Title 41
ATM Data Configuration

Table 6: atm-vcl-param settings

Setting Application Cells per

second

38 1 to 2 DS0s 38 CPS
at 5:1 to 10:1 oversubscription

76 2 to 4 DS0s 76 CPS
at 5:1 to 10:1 oversubscription

151 4 to 8 DS0s 151 CPS

at 5:1 to 10:1 oversubscription

189 1 DS0 189 CPS

no oversubscription

302 8 to 16 DS0s 302 CPS

at 5:1 to 10:1 oversubscription

378 2 DS0 378 CPS

no oversubscription
604 16 to 32 DS0s 604 CPS
at 5:1 to 10:1 oversubscription

755 4 DS0 755 CPS

no oversubscription

1208 32 to 64 DS0s 1208 CPS

at 5:1 to 10:1 oversubscription

1510 8 DS0 1510 CPS

no oversubscription

3661 Full T1 3661 CPS

4825 Full E1 4825 CPS

28302 8 T1s 28,303 CPS

37736 8 E1s 37,736 CPS

106133 DS3 106,133 CPS

365567 O-C3c/STM1 365,567 CPS

Changing the atm-vcl-param profile values

Caution: Changing the values in the atm-vcl-param profile requires

a system reboot.

To update the atm-vcl-param profile with new values:

zSH> update atm-vcl-param 0
Please provide the following: [q]uit.
vcl-rate-param1: --> {38}:
vcl-rate-param2: --> {76}:

42 Book Title
 Creating traffic descriptors

vcl-rate-param3: --> {151}: 164

vcl-rate-param4: --> {189}: 196
vcl-rate-parma5: --> {302}:
vcl-rate-param6: --> {378}:
vcl-rate-param7: --> {604}:
vcl-rate-param8: --> {755}:
vcl-rate-param9: --> {1208}:
vcl-rate-param10: -> {1510}:
vcl-rate-param11: -> {3661}:
vcl-rate-param12: -> {4825}:
vcl-rate-param13: -> {28302}:
vcl-rate-param14: -> {37736}:
vcl-rate-param15: -> {106133}:
vcl-rate-param16: -> {365567}:
vcl-rate-grp2-param1: --> {2264}
vcl-rate-grp2-param2: --> {3019}
vcl-rate-grp2-param3: --> {4151}
vcl-rate-grp2-param4: --> {7075}
vcl-rate-grp2-param5: --> {9434}
vcl-rate-grp2-param6: --> {11792}
vcl-rate-grp2-param7: --> {14151}
vcl-rate-grp2-param8: --> {16509}
vcl-rate-grp2-param9: --> {18868}
vcl-rate-grp2-param10: -> {23585}
vcl-rate-grp2-param11: -> {33019}
vcl-rate-grp2-param12: -> {56604}
vcl-rate-grp2-param13: -> {75472}
vcl-rate-grp2-param14: -> {150943}
vcl-rate-grp2-param15: -> {226415}
vcl-rate-grp2-param16: -> {301887}
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Changing atm-vcl-param 0 will result in a system
reboot. Continue? [y]es or [n]o: y
Atm configuration changed system is rebooting
...Record updated.

Creating traffic descriptors

When you create a traffic descriptor, specify an index, which is used to
associate a traffic descriptor with an ATM virtual channel links (VCLs) in an
atm-vcl record.

Book Title 43
ATM Data Configuration

The following parameters of the default atm-traf-descr profile should be

modified to match your network:

Parameter Description

td_type Traffic descriptor type.

Values:
atmNoClpNoScr
(OID 1.3.6.1.2.1.37.1.1.2) No CLP and no sustained
cell rate.
atmClpTaggingNoScr
(OID 1.3.6.1.2.1.37.1.1.4) CLP with tagging and no
sustained cell rate.
atmClpNoTaggingScr
(OID 1.3.6.1.2.1.37.1.1.6) CLP with no tagging and
sustained cell rate.
atmClpTaggingScr
(OID 1.3.6.1.2.1.37.1.1.7) CLP with tagging and
sustained cell rate.
atmClpTransparentNoScr
(OID 1.3.6.1.2.1.37.1.1.9) CLP transparent with no
sustained cell rate.
atmClpTransparentScr
(OID 1.3.6.1.2.1.37.1.1.10) CLP transparent with
sustained cell rate.
atmNoClpNoScrCdvt
(OID 1.3.6.1.2.1.37.1.1.12) No CLP, no sustained
cell rate, and cell delay variation tolerance.
atmClpNoTaggingScrCdvt
(OID 1.3.6.1.2.1.37.1.1.14) CLP with no tagging,
sustained cell rate and cell delay variation tolerance.
atmClpTaggingScrCdvt
(OID 1.3.6.1.2.1.37.1.1.15) CLP with tagging,
sustained cell rate, and cell delay variation tolerance.

td_param1 Peak Cell Rate (PCR), measured in cells per second.

For CBR traffic, must match a value configured in
the atm-vcl-param profile.

td_param2 Sustainable cell rate (SCR), measured in cells per

second. For rt-VBR traffic, must match a value
configured in the atm-vcl-param profile.
PCR for atmClpTaggingNoScr traffic.
CDVT for atmClpTransparentNoScr and
atmNoClpNoScrCdvt traffic.
td_param3 Maximum burst size (MBS), measured in number of
cells.

td_param4 Cell delay variation tolerance (CDVT), measured in

10ths of microseconds.

44 Book Title
 Creating traffic descriptors

Parameter Description

cac-divider Enables oversubscription for an ATM VCL. During

CAC calculations, the system divides the PCR (for
CBR VCLs) or SCR (for nrt-VBR or rt-VBR VCLs)
bandwidth by the value specified in the cac-divider.
It then uses that value to determine if the VCL can be
created.
For example, to configure a 4:1 oversubscription, set
cac-divider to 4.
Default: 1

td_service_category The ATM service category.

Values:
cbr Constant bit rate
ubr - unspecified bit rate
rtvbr - Real time variable bit rate
nrtvbr Non-real time variable bit rate
Default: ubr

td_frame_discard Enables and disable early-packet-discard (EPD) and

partial-packet-discard (PPD). This allows selective
discarding of all cells in a frame if one cell is lost or
discarded.
Values:
true Indicates that the network is requested to treat
data for this connection, in the given direction, as
frames (that is, AAL5 CPCS PDUs) rather than as
individual cells. While the precise implementation is
network-specific, this treatment may involve
discarding entire frames during congestion, rather
than a few cells from many frames.
false This is the recommended setting for voice
connections.
Default: false
usage-parameter-control Enables or disables policing on the traffic descriptor.
Note that this must be set to true if the ATM service
category is CBR.
Values:
true
false
Default: true

Creating a traffic descriptor

1 List the atm-traf-descr records to see what is currently configured on the
system:
zSH> list atm-traf-descr

Book Title 45
ATM Data Configuration

0 entries found.

2 Create a traffic descriptor by specifying a traffic descriptor type and the

traffic parameters. For example:
zSH> new atm-traf-descr 100
Please provide the following: [q]uit.
td_type: ------------- {atmNoClpNoScr}: enter traffic descriptor
td_param1: ----------- {0}: enter PCR
td_param2: ----------- {0}: enter PCR (for CLP=0 traffic) or SCR
td_param3: ----------- {0}: enter MBS
td_param4: ----------- {0}: enter CDVT
td_param5: ----------- {0}:
cac-divider: -------------> {1}
td_service_category: - {ubr}: rtvbr | nrtvbr | ubr | cbr
td_frame_discard: --------> {false}
usage-parameter-control: -> {true}
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Note: Set the PCR to match the lowest speed in the cross connect.

Creating VCLs and VPLs

VCLs are used for VC switching. VPLs are used for VP switching.
The following table describes the supported parameters in the atm-vcl profile:

Parameter Description

vpi The VPI for this VCL. This must

match the remote end of the
connection.

vci The VCI for this VCL. This must

match the remote end of the
connection.

admin_status Administrative status of the link.

Values:
up
down
Default: down
receive_traffic_descr_index The index of the atm-traf-descr
profile used for this VCL.

transmit_traffic_descr_index The index of the atm-traf-descr

profile used for this VCL.

46 Book Title
 Creating VCLs and VPLs

Parameter Description

vcc_aal_type ATM adaption layer type.

Values:
aal5 for data
other For cell relay connections.
aal2 for voice
Default: aal5

vcc_aal5_encaps_type The type of data encapsulation used

over the AAL5 Service Specific
Convergence Sublayer (SSCS) layer.
The definitions reference RFC 1483
Multiprotocol Encapsulation over
ATM AAL5 and the ATM Forum LAN
Emulation specification.
Values:
llcencapsulation Used for an
LLC-encapsulated connection.
other Used for a bridged connection.

fault-detection-type Used to determine faults on the VCL.

Values:
disabled Fault detection is disabled.
oamF5Loopback On POTS-based
AAL2 connections, the unit sends an
OAM F5 loopback if the CAS does not
refresh after 10 seconds. If there is no
response to the F5 loopback, the VCL
is blocked and a trap is generated.
On ISDN-based AAL2 connections,
there is no CAS refresh; the unit sends
an F5 loopback every 5 seconds. If
there is no response to the F5
loopback, the VCL is blocked and a
trap is generated.
F5 loopbacks on AAL5 connections
are not supported.
Default: disabled

Book Title 47
ATM Data Configuration

The following table describes the supported parameters in the atm-vpl

profile:

Parameter Description

atmVplAdminStatus Administrative status of the VPL.

Values:
up
down
Default: down

atmVplReceiveTrafficDescrIndex Specifies the ATM traffic descriptor

which applies to the receive direction of
this VPL. Currently this value must be set
equal to the value used for the
atmVplTransmitTrafficDescrIndex.
Values:
The index value of an existing
atm-traf-descr.

atmVplTransmitTrafficDescrIndex Specifies the ATM traffic descriptor

which applies to the transmit direction of
this VPL. Currently this value must be set
equal to the value used for the
atmVplReceiveTrafficDescrIndex.
Values:
The index value of an existing
atm-traf-descr.

atmVplCastType Type of connection.

Values:
p2p Point-to-point.
atmVplConnKind The use of call control.
Values:
pvc

Creating VCLs (VC switching)

Create two VCLs for each cross connection. Each atm-vcl record defines an
endpoint for an ATM virtual cross connection (VCC).

Note: For a cell relay connection, set the vcl_aal_type to other,

which treats the connection endpoints as cell relay. The MALC will
not perform any segmentation or reassembly (SAR) on the data
stream.

1 The following example creates a VCL for a subscriber-side ADSL

interface in shelf 1, slot 12, port 1, with a VPI of 0 and a VCI of 35:
zSH> new atm-vcl 1-12-1-0-adsl/atm/0/35
Please provide the following: [q]uit.

48 Book Title
 Creating VCLs and VPLs

vpi: -----------------------------> {0}:

vci: -----------------------------> {0}:35
admin_status: --------------------> {up}:up
receive_traffic_descr_index: -----> {0}:100
transmit_traffic_descr_index: ----> {0}:100
vcc_aal_type: --------------------> {aal5}:other
vcc_aal5_cpcs_transmit_sdu_size: -> {9188}:
vcc_aal5_cpcs_receive_sdu_size: --> {9188}:
vcc_aal5_encaps_type: ------------>
{llcencapsulation}:
vcl_cast_type: -------------------> {p2p}:
vcl_conn_kind: -------------------> {pvc}:
fault-detection-type: ------------> {disabled}
traffic-container-index: ---------> {0}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record saved.

2 The following example creates a VCL for the Uplink card interface in
shelf 1, slot 1, port 1, with a VPI of 0 and a VCI of 101:
zSH> new atm-vcl uplink1/atm/0/101
Please provide the following: [q]uit.
vpi: -----------------------------> {0}:
vci: -----------------------------> {0}:101
admin_status: --------------------> {down}:up
receive_traffic_descr_index: -----> {0}:100
transmit_traffic_descr_index: ----> {0}:100
vcc_aal_type: --------------------> {aal5}:other
vcc_aal5_cpcs_transmit_sdu_size: -> {9188}:
vcc_aal5_cpcs_receive_sdu_size: --> {9188}:
vcc_aal5_encaps_type: ------------>
{llcencapsulation}:
vcl_cast_type: -------------------> {p2p}:
vcl_conn_kind: -------------------> {pvc}:
fault-detection-type: ------------> {disabled}
traffic-container-index: ---------> {0}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record saved.

Creating VPLs (VP switching)

Before creating VPLs, verify that an atm-vpi record exists for the VP you
want to switch. For details, see VPI/VCI ranges on page 38.
Create two VPLs for each cross connection. Each atm-vpl record defines an
endpoint for an ATM virtual cross connection (VCC).

Note: For a cell relay connection, set the vcl_aal_type to other,

which treats the connection endpoints as cell relay. The MALC will
not perform any segmentation or reassembly (SAR) on the data
stream.

Book Title 49
ATM Data Configuration

1 Create a VPL for the other end of the cross connect (in this example, an
ADSL port in slot 3, using VPI 2):
zSH> new atm-vpl 1-3-1-0-adsl/atm/2 interface-index/atm/VPI
Please provide the following: [q]uit.
atmVplAdminStatus: ---------------> {down}: up
atmVplReceiveTrafficDescrIndex: --> {0}: 1
atmVplTransmitTrafficDescrIndex: -> {0}: 1
atmVplCastType: ------------------> {p2p}:
atmVplConnKind: ------------------> {pvc}:
atmVplPonTrafficContainerIndex: --> {0}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

2 Create a VPL for one end of the cross connect (in this example, an Uplink
card using VPI 3)
zSH> new atm-vpl uplink1/atm/3 interface-index/atm/VPI
Please provide the following: [q]uit.
atmVplAdminStatus: ---------------> {down}: up
atmVplReceiveTrafficDescrIndex: --> {0}: 1
atmVplTransmitTrafficDescrIndex: -> {0}: 1
atmVplCastType: ------------------> {p2p}:
atmVplConnKind: ------------------> {pvc}:
atmVplPonTrafficContainerIndex: --> {0}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Next, create the cross connect.

Creating cross connects

To connect the two endpoints create a new atm-cc profile and specify an
index value (The cc-index is any number you choose.) The atm-cc record
uses the low-if-index and high-if-index values for VPI and VCI to bind VCC
endpoints.
The following parameters of the default atm-cc profile should be modified to
match your network:

Parameter Description

cc-index A unique value to identify this cross connect.

low-if-index The index (in the form shelf-slot-port-subport-interface/atm

or a user-defined string) of the ATM interface for this cross
connect. The low-if-index is arbitrary, but by convention it
indicates the ATM interface with a numerically lower
ifIndex value than the other ATM interface identified in the
same cross connect.
The low-if-index and the high-if-index cannot be equal.

50 Book Title
 Creating cross connects

Parameter Description

low-vpi The VPI value associated with the interface specified in the
low-if-index.
low-vci The VCI value associated with the interface specified in the
low-if-index. For VP switched connections, specify 0.

high-if-index The index (in the form shelf-slot-port-subport-interface/atm

or a user-defined string) of the ATM interface for this cross
connect. The high-if-index is arbitrary, but by convention it
indicates the ATM interface with a numerically higher
ifIndex value than the other ATM interface identified in the
same cross connect.
The low-if-index and the high-if-index cannot be equal.

high-vpi The VPI value associated with the interface specified in the
high-if-index

high-vci The VCI value associated with the interface specified in the
high-if-index. For VP switched connections, specify 0.

admin-status The desired administrative status of the cross connect.

Values:
up
down
Default: down

Creating cross connects

To create a VC-switched crossconnect, use the crossconnect command. This
command uses the following syntax:
crossconnect add interface1/type1 [vc] vpi1/vci1
interface2/type2 [vc] vpi2/vci2 td_val | txtd txtd_value
rxtd rxtd_val
The following example creates a VC switched cross connect between a
DSL port and an OC-3c/STM1 port (the VCL were created above):
zSH> crossconnect add 1-3-1-0-adsl/atm vc 1/35
uplink2/atm vc 1/101 100

The following example creates a VP switched cross connect between a

DSL port and the Uplink port:
zSH> new atm-cc 1
Please provide the following: [q]uit.
cc-index: ------> {0}: 1
low-if-index: --> {0/0/0/0/0}: 1-3-1-0-adsl/atm
low-vpi: -------> {0}: 2
low-vci: -------> {0}: leave at 0 for VP switching
high-if-index: -> {0/0/0/0/0}: uplink2/atm
high-vpi: ------> {0}: 3
high-vci: ------> {0}: leave at 0 for VP switching

Book Title 51
ATM Data Configuration

admin-status: --> {down}: up

....................
Save new record? [s]ave, [c]hange or [q]uit: s
Record saved.

Note: A VCL or VPL can be used in only one cross connect.

Subtending
Subtending allows you aggregate traffic from multiple MALC devices to
single MALC device’s ATM upstream interface.
In a typical subtended configuration, VPLs from downstream devices are
VP-switched to an upstream ATM device over a high-speed interface such as
OC-3c/STM1 or OC-12c/STM4.

Figure 4: Example subtending configuration

VPL 1-3-1-0-ds1/atm/1

Device A

T1/E1 32 ATM
card VPL uplink1/atm/1
Device C VPL uplink1/atm/2

VPL 1-3-2-0-ds1/atm/2

Device B

Subtending example
This example creates a subtended configuration from two downstream MALC
devices to a single MALC. The downstream devices are connected to MALC
T1/E1 ports and the traffic is VP switched to the Uplink interface (and then to
the upstream ATM network).
1 Create a traffic descriptors for the downstream and upstream interfaces:

52 Book Title
 Subtending

Downstream: (this example uses a UBR connection with a PCR of

3661 CPS (T1 line speed)):
zSH> new atm-traf-descr 100
Please provide the following: [q]uit.
td_type: -----------------> {atmNoClpNoScr}:
td_param1: ---------------> {0}: 3661
td_param2: ---------------> {0}:
td_param3: ---------------> {0}:
td_param4: ---------------> {0}:
td_param5: ---------------> {0}:
cac-divider: -------------> {1}:
td_service_category: -----> {ubr}:
td_frame_discard: --------> {false}:
usage-parameter-control: -> {true}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Upstream: (this example uses a UBR connection with a PCR of 28,303

CPS (line speed of 8 T1s)):
zSH> new atm-traf-descr 200
Please provide the following: [q]uit.
td_type: -----------------> {atmNoClpNoScr}:
td_param1: ---------------> {0}: 28303
td_param2: ---------------> {0}:
td_param3: ---------------> {0}:
td_param4: ---------------> {0}:
td_param5: ---------------> {0}:
cac-divider: -------------> {1}:
td_service_category: -----> {ubr}:
td_frame_discard: --------> {false}:
usage-parameter-control: -> {true}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

2 Create VPI profiles for each VPI you want to switch. These specify that
the MALC should VPI switch all traffic using this VPI:
a For the Uplink interface:
zSH> new atm-vpi uplink1/atm/1 interface-index/atm/VPI
Please provide the following: [q]uit.
zhoneAtmVpiMaxVci: ---> {0}:
zhoneAtmVpiSwitched: -> {vc}: vp
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

zSH> new atm-vpi uplink1/atm/2 interface-index/atm/VPI

Please provide the following: [q]uit.
zhoneAtmVpiMaxVci: ---> {0}:
zhoneAtmVpiSwitched: -> {vc}: vp

Book Title 53
ATM Data Configuration

....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

After the first atm-vpi record is saved, the system will automatically
create atm-vpi records for all VPIs used in existing cross connects, if
any.
b For the T1/E1 port connected to device A:
zSH> new atm-vpi 1-3-1-0-ds1/atm/1 interface-index/atm/
VPI
Please provide the following: [q]uit.
zhoneAtmVpiMaxVci: ---> {0}:
zhoneAtmVpiSwitched: -> {vc}: vp
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

c For the T1/E1 port connected to device B:

zSH> new atm-vpi 1-3-2-0-ds1/atm/2 interface-index/atm/
VPI
Please provide the following: [q]uit.
zhoneAtmVpiMaxVci: ---> {0}:
zhoneAtmVpiSwitched: -> {vc}: vp
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

d After the system has finished creating the atm-vpi records, reboot the
card:

Note: Rebooting the active Uplink card causes the system to

reboot (for a non-redundant system), or switchover to the standby
Uplink card (for a redundant system).

Uplink card:
zSH> slotreboot 1
T1/E1 32 card:
zSH> slotreboot 3
e If your system is redundant, configure a VPI profile on the second
Uplink card.
3 Create VPLs to each downstream MALC:
Device A:
zSH> new atm-vpl 1-3-1-0-ds1/atm/1 interface-index/atm/VPI
Please provide the following: [q]uit.
atmVplAdminStatus: ---------------> {down}: up
atmVplReceiveTrafficDescrIndex: --> {0}: 100
atmVplTransmitTrafficDescrIndex: -> {0}: 100

54 Book Title
 Subtending

atmVplCastType: ------------------> {p2p}:

atmVplConnKind: ------------------> {pvc}:
atmVplPonTrafficContainerIndex:--> {0}
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Device B:
zSH> new atm-vpl 1-3-2-0-ds1/atm/2 interface-index/atm/VPI
Please provide the following: [q]uit.
atmVplAdminStatus: ---------------> {down}: up
atmVplReceiveTrafficDescrIndex: --> {0}: 100
atmVplTransmitTrafficDescrIndex: -> {0}: 100
atmVplCastType: ------------------> {p2p}:
atmVplConnKind: ------------------> {pvc}:
atmVplPonTrafficContainerIndex:--> {0}
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

4 Create the VPLs for device C’s Uplink interface:

For VPI 1 (device A):
zSH> new atm-vpl uplink1/atm/1 interface-index/atm/VPI
Please provide the following: [q]uit.
atmVplAdminStatus: ---------------> {down}: up
atmVplReceiveTrafficDescrIndex: --> {0}: 200
atmVplTransmitTrafficDescrIndex: -> {0}: 200
atmVplCastType: ------------------> {p2p}:
atmVplConnKind: ------------------> {pvc}:
atmVplPonTrafficContainerIndex:--> {0}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

For VPI 2 (device B):

zSH> new atm-vpl uplink1/atm/2 interface-index/atm/VPI
Please provide the following: [q]uit.
atmVplAdminStatus: ---------------> {down}: up
atmVplReceiveTrafficDescrIndex: --> {0}: 200
atmVplTransmitTrafficDescrIndex: -> {0}: 200
atmVplCastType: ------------------> {p2p}:
atmVplConnKind: ------------------> {pvc}:
atmVplPonTrafficContainerIndex:--> {0}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

5 Create cross connects between the two downstream interfaces and the
Uplink interface:
From Device A to the Uplink VPL:

Book Title 55
ATM Data Configuration

zSH> new atm-cc 1

Please provide the following: [q]uit.
cc-index: ------> {0}: 1
low-if-index: --> {0/0/0/0/0}: atm-vcl 1-3-1-0/atm
low-vpi: -------> {0}: 1
low-vci: -------> {0}: leave at 0 for VP switching
high-if-index: -> {0/0/0/0/0}: uplink1/atm
high-vpi: ------> {0}: 1
high-vci: ------> {0}: leave at 0 for VP switching
admin-status: --> {down}: up
....................
Save new record? [s]ave, [c]hange or [q]uit: s
Record saved.

From Device B to the Uplink VPL:

zSH> new atm-cc 2
Please provide the following: [q]uit.
cc-index: ------> {0}: 2
low-if-index: --> {0/0/0/0/0}: atm-vcl 1-3-2-0/atm
low-vpi: -------> {0}: 2
low-vci: -------> {0}: leave at 0 for VP switching
high-if-index: -> {0/0/0/0/0}: uplink1/atm
high-vpi: ------> {0}: 2
high-vci: ------> {0}: leave at 0 for VP switching
admin-status: --> {down}: up
....................
Save new record? [s]ave, [c]hange or [q]uit: s
Record saved.

56 Book Title
4
CONFIGURING IP

This chapter explains IP services on the MALC. It includes the following

sections:
• IP Overview, page 57
• Applications, page 59
• IP provisioning procedures, page 66
• Advanced IP provisioning procedures, page 86
• Configuring the MALC for IP video, page 93
• IP administrative procedures, page 97

IP Overview
The MALC provides the following IP services:
• IP forwarding and routing—incoming packets from an interface are
forwarded to the appropriate output interface using the routing table rules.
• DHCP servers to simplify user IP address configuration.
• IP filtering. IP filtering is typically performed to enhance network
security by limiting access between two networks.
• Numbered or unnumbered interfaces
• Telnet client
The following MALC interfaces support IP traffic:
• One Ethernet interface on the Uplink card for management traffic or
subscriber traffic.
• The ATM/IP Uplink cards are required for IP services on MALC. The
ATM/IP Uplink card terminates the IP traffic.
• DSL interfaces. IP on DSL runs over ATM PVCs using RFC 1483
encapsulation.

Note: IP features may not be supported on your device. Contact GSS

about enabling IP features.

MALC Configuration Guide 57

Configuring IP

The Internet protocol (IP) allows devices to communicate over interconnected

networks. IP is a layer 3 protocol in the seven-layer Open Systems
Interconnection (OSI) model. Layer 3, or network layer, handles the delivery
of data packets from source to destination. Any device connected to a network
is considered a host or a node on that network. Zhone devices with IP
capability can act as routers to accept network traffic and forward it on to host
destinations based on IP addressing. To get from source to destination, the IP
packet passes through many nodes, or hops, along the way. All routers
maintain routing tables of the sequence of hops taken from source to
destination. The routing table is used by the router to direct datagrams most
efficiently. The routing table information is also shared with other routers on
the same network.

Figure 5: IP stacking on Zhone devices

IP

Layer 3
IP

Layer 2
ETHERNET SAR RFC1 483 ATM CC SAR ETHERNET

Layer 1
TWISTED DSL CATEGORY 5
PAIR CABLE

The following IP protocols are supported on the MALC.

DNS

Domain Name System (DNS) maps domain names to IP addresses, enabling

the system to reach destinations when it knows only the domain name of the
destination.

DHCP

The Dynamic Host Control Protocol (DHCP) provides a mechanism through

which client computers using TCP/IP can obtain configuration parameters

58 MALC Configuration Guide

 Applications

(such as the default router and the DNS server, subnet mask, gateway address,
and lease time) from a DHCP server. The most important configuration
parameter carried by DHCP is the IP address.
As a DHCP server, MALC can assign temporary (leased) IP addresses to
client PCs. Each DHCP client PC sends a request to the MALC for an IP
address lease. The MALC then assigns an IP address and lease time to the
client PC. The MALC keeps track of a range of assignable IP addresses from
a subnetwork.
Some customers prefer to have the same IP address every time their DHCP
lease renews. This is known as sticky IP addresses. By default, the MALC
attempts to assign the same IP address to the same client on DHCP lease
renewal.
With shared DHCP pools (or subnet groups), DHCP servers are not linked to
physical interfaces. Customers can easily configure an arbitrary number of
DHCP pools. Zhone devices can assign blocks of IP addresses specifically for
certain customers.

RIP

Routing Information Protocol (RIP), an interior gateway protocol (IGP), is

widely used for routing traffic on the Internet. RIP performs routing within a
single autonomous system. It is based on distance-vector algorithms that
measure the shortest path between two points on a network. The shortest path
is determined by the number of hops between those points. RIP routers
maintain only the best route (the route with the lowest metric value) to a
destination. After updating its routing table, the router immediately begins
transmitting routing updates to inform other network routers of the shortest
route.
Routing Information Protocol version 2 (RIPv2) is the latest enhancement to
RIP. RIPv2 allows more information to be included in RIP packets and
provides an authentication mechanism.

Applications
The following IP applications are supported on the MALC:
• Routing on page 60
• Host-based routing with DSL bridges on page 61
• Host-based routing with DSL routers on page 62
• Network-based routing with DSL bridges on page 63
• Network-based routing with DSL routers on page 63
• IP filtering on page 64
• Unnumbered IP interfaces on page 65

MALC Configuration Guide 59

Configuring IP

Routing

Routing is the process of selecting a next hop for forwarding data traffic. The
routing information base (RIB) contains all the information about the routes
in the system, including the preference values and interface states. The
forwarding information base (FIB) is derived from the RIB and only contains
the best route to a given destination.
IP routing through the system makes use of the following types of routes:
• Interface routes—These routes are defined by the addresses and netmasks
that are provisioned on the IP interfaces.
• Static routes—These routes are manually configured and define paths to
destinations in terms of an interface identifier or the IP address of a
next-hop router on a directly attached network. There are two kinds of
static routes:
– Low preference—These routes are only used to define default routes
(that is, routes of last resort) and are less preferable to most other
routes.
– Normal preference—All other static routes are considered more
preferable than other types of routes (with the exception of interface
routes).
• Dynamic routes—These routes are learned by running routing protocols,
such as RIP, and have varying preferences, depending on how they were
learned.
The following table describes the default routing preferences on the device.
These preferences cannot be overridden. Higher numbers indicate more
preferred route types:

Type of route Default preference

Local 10

Static 9

RIP 4

Static low 4
(used for default routes)

Host-based and network-based routing

The MALC supports both host-based routing and network-based (subnet)
routing.
Host-based routing uses a unnumbered interface and adds a single IP address
to the routing table for each route. This type of routing allows a granular
allocation of addresses based on the host floating (unnumbered) IP address
and the available subnetwork addresses. Routes are configured individually
using the host add command. For each configured route, an IP address is

60 MALC Configuration Guide

 Applications

added to the routing table. For example, an unnumbered host address of

10.10.10.1/24, adds one entry in the routing table for the address 10.10.10.1
and makes available a subnet of 254 addresses for individual route
configuration. When each host route is added, a new routing table entry is
created.
Network-based (subnet) routing uses a numbered interface and adds IP
network addresses with variable length subnet masks to the routing table. This
type of routing allows a single routing table entry to represent many
numbered host addresses. However, it does not allow for granular IP address
allocation. For example, an interface configured with 10.10.10.1/24 adds just
one entry to the routing table for 10.10.10.1/24. All 254 addresses in this
subnet are assigned to this interface, regardless of how many addresses in this
subnet are actually used.
The command used to create the IP interface depends on the application, IP
assignment, type of address allocation and interface type. Commands to add
an IP interface on page 61 shows the commands to add an IP interface and the
requirements.

Table 7: Commands to add an IP interface

Command Application IP Assignment Address Encapsulation Interface Type

Allocation

Host add Host-based Static/Dynamic Single per host For bridge: other Unnumbered
routing with add command For router: LLC
DSL bridge or
router

Interface add Network-based Static Multiple based For bridge: other Numbered
routing with on subnet mask For router: LLC
DSL bridge or length
router

Host-based routing with DSL bridges

Host-based routing takes advantage of IP unnumbered interfaces and shared

DHCP pools to conserve IP addresses. In the host-based routing with DSL
bridges application, subscribers connected to the MALC are on the same
subnet as the MALC unnumbered interface.

MALC Configuration Guide 61

Configuring IP

Figure 6: Host-based routing with DSL bridges

PC Bridge
subscriber A
x.x.y.2
IP

x.x.y.1

Bridge
PC

Host-based routing with DSL routers

In the host-based routing with DSL routers application, remote IADs (or
routers) are on the same subnet as the MALC unnumbered interface. The
IADs connect private networks to the MALC.

Figure 7: Host-based routing with DSL routers

Private network
Public subnet

x.x.y.2

x.x.a.1
NAT router

IP
x.x.a.2

Private network x.x.y.1

x.x.y.3
x.x.b.1

NAT router

62 MALC Configuration Guide

 Applications

Network-based routing with DSL bridges

Network-based routing is ideal for adding large numbers of IP addresses.

Unlike host-based routing, network based-routing requires numbered IP
interfaces on the MALC. In network-based routing with DSL bridges
application, each bridge is in the same network as one of the MALC
numbered interfaces.

Figure 8: Network-based routing with bridges

Bridge
x.x.y.2 x.x.y.1/24

IP

x.x.y.3

x.x.z.1/24
Bridge

x.x.z.2

x.x.z.3

Network-based routing with DSL routers

Network-based routing with DSL routers allows multiple statically assigned

addresses per customer. In this application, each remote router is on a subnet
with a numbered interface on the MALC.

MALC Configuration Guide 63

Configuring IP

Figure 9: Network-based routing with routers

Private network Public subnet

a.b.c.0/30

a.b.c.1
x.x.y.1
NAT router

IP
a.b.c.2

Private network
x.x.z.1

d.e.f.0/30

d.e.f.1

NAT router

d.e.f.2

IP filtering

IP filtering is typically performed to enhance network security by limiting

access between two networks. IP filtering is based on the recognition and
selective transmission or blocking of individual IP packets. Packets meeting
some criterion are forwarded, and those that fail are dropped. IP filtering is
used to block inbound traffic to the management network.

64 MALC Configuration Guide

 Applications

Figure 10: IP filtering

Management
Internet
network

Filter

Subscribers

IP filtering allows or denies IP packets based on:

• source IP address
• destination IP address
IP filtering can be provisioned from the CLI by using the filter command and
modifying the ip-interface-record where you wish to apply the filter.

Unnumbered IP interfaces

Unnumbered IP interfaces reduce the number of IP addresses used by a

device. Unnumbered interfaces are just like other point-to-point connections,
except a “floating” or virtual IP interface is used as the local IP address in the
ip-interface-record.

Figure 11: Unnumbered IP interfaces

Shared or “floating”
IP address
Unnumbered IP interface

Point to point connection

MALC Configuration Guide 65

Configuring IP

IP provisioning procedures
This section includes the following procedures:
• Configuring a management IP interface on page 66
• Configuring host-based routing on page 67
• Configuring network-based routing on page 74
• Configuring RIP on page 77
• Configuring static routes on page 77
• Deleting routes on page 102
• Configuring the device as a DHCP server on page 78

Configuring a management IP interface

Caution: The Uplink card Ethernet interface must be configured

before any other interfaces on the system, even if you do not intend to
manage the unit over the Ethernet.

Configuring an Ethernet connection

1 Enter the interface add command with the following options:
zSH> interface add 1-1-1-0/ethernetcsmacd 10.10.10.10 255.255.255.0
Created ip-interface-record ethernet1/ip

This example:
– creates an ip-interface-record on ethernet1/ip
– adds host 10.10.10.10.
– sets netmask as 255.255.255.0.
2 Verify that the Ethernet connection is active.
zSH> interface show
Interface Status Rd/Address Media/Dest Address IfName
--------------------------------------------------------------------------------
1/1/1/0/ip UP 1 10.10.10.10/24 00:01:47:bb:d5:f1 ethernet1
--------------------------------------------------------------------------------
1 interface

or ping the host

zSH> ping 10.10.10.10
PING 10.10.10.10: 64 data bytes
!!!!!

66 MALC Configuration Guide

 IP provisioning procedures

Note: If necessary, you can modify the ip-interface-record on

the Uplink card to change the settings created by the interface
add command.

Creating a default route

The following example creates a default route using the gateway
192.168.8.1 with a cost of 1 (one):
route add default 192.168.8.1 1

Verifying the route

Use the route show command to verify that the routes were added:
zSH> route show
Dest Nexthop Cost Owner
------------------------------------------------------------
0.0.0.0/0 192.168.8.1 1 STATICLOW
192.168.8.0/24 1/1/1/0/ip 1 LOCAL

Use the ping command to verify connectivity to the default gateway:

zSH> ping 192.168.8.1
PING 192.168.8.1: 64 data bytes
!!!!
----172.24.200.254 PING Statistics----
4 packets transmitted, 4 packets received
round-trip (ms) min/avg/max = 0/0/0

To stop the ping, press CTRL+C.

Configuring host-based routing

Host-based routing interoperates with DSL bridges and routers. The type of
AAL5 encapsulation determines interoperability with DSL routers or DSL
bridges. LLC encapsulation is used with DSL routers; RFC 1483
encapsulation is used with DSL bridges. Specify LLC encapsulation (llc) in
the command line for host-based routing to DSL routers. If no encapsulation
type is specified in the command line, RFC 1483 encapsulation (other) is the
default.

MALC Configuration Guide 67

Configuring IP

The following table summarizes the configuration tasks for configuring

host-based routing:

Task Command

Create an atm-traf-descr. new atm-traf-descr index

Where index is a user-defined value.

Create the IP interface record. new ip-interface-record index/ip

Where index is of the form shelf-slot-port-subport or a user-defined
string.

Create the unnumbered, or floating, new ip-unnumbered-record index

interface. Where index is a user-defined value.

Create subnet groups. new dhcp-server-subnet index

Where index is a user-defined value.
Configure a connection to a host. host add index/type vc vpi/vci td tdvalue other
| llc static x.x.x.x | dynamic subnetgroup count
This command creates the VCL and IP interface for the host route.

Verify provisioning host show index/type vc vpi/vci td tdvalue

dynamic subnetgroup count

Configuring host-based routing with DSL routers

1 Create an atm-traf-descr for unnumbered interfaces:
zSH> new atm-traf-descr 100
Please provide the following: [q]uit.
td_type: -----------------> {atmNoClpNoScr}:
td_param1: ---------------> {0}: 106133
td_param2: ---------------> {0}: 38
td_param3: ---------------> {0}:
td_param4: ---------------> {0}:
td_param5: ---------------> {0}:
cac-divider: -------------> {1}:
td_service_category: -----> {ubr}:
td_frame_discard: --------> {false}:
usage-parameter-control: -> {true}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

2 Create an ip-interface-record for the IP address that is to be shared for

all devices in the host-based routing subnet. The example uses the name/
type syntax.
zSH> new ip-interface-record ptm1/ip
Please provide the following: [q]uit.
vpi: ---------------> {0}:
vci: ---------------> {0}:
rdindex: -----------> {1}:

68 MALC Configuration Guide

 IP provisioning procedures

dhcp: --------------> {none}: ** read-only **

addr: --------------> {0.0.0.0}: 10.0.0.1
netmask: -----------> {0.0.0.0}: 255.0.0.0
bcastaddr: ---------> {0.0.0.0}: 10.255.255.255
destaddr: ----------> {0.0.0.0}:
farendaddr: --------> {0.0.0.0}:
mru: ---------------> {1500}:
reasmmaxsize: ------> {0}:
ingressfiltername: -> {}:
egressfiltername: --> {}:
pointtopoint: ------> {no}:
mcastenabled: ------> {yes}:
ipfwdenabled: ------> {yes}:
mcastfwdenabled: ---> {yes}:
natenabled: --------> {no}:
bcastenabled: ------> {yes}:
ingressfilterid: ---> {0}:
egressfilterid: ----> {0}:
ipaddrdynamic: -----> {static}:
dhcpserverenable: --> {false}:
subnetgroup: -------> {0}:
unnumberedindex: ---> {0}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
Cannot determine binding for this IP interface.
Could not automatically bind this IP Interface
New record saved.

Note: This is a virtual interface that will share its IP address;

binding the IP interface is not necessary.

3 Create an ip-unnumbered-record for the IP interface you just created.

Enter the name/type used in for ip-interface-record (from Step 2) as the
ipUnnumberedinterface value.
zSH> new ip-unnumbered-record 1
Please provide the following: [q]uit.
ipUnnumberedInterfaceName: -> { }: ptm1/ip
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

4 Create a dhcp-server-subnet record for each customer, specifying the

range (or pool) of assignable addresses which that customer can be
assigned.
zSH> new dhcp-server-subnet 99
Please provide the following: [q]uit.
network: ---------------> {0.0.0.0}: 10.0.0.0
netmask: ---------------> {0.0.0.0}: 255.0.0.0
domain: ----------------> {0}: 1
range1-start: ----------> {0.0.0.0}: 10.0.0.10
range1-end: ------------> {0.0.0.0}: 10.0.0.20

MALC Configuration Guide 69

Configuring IP

range2-start: ----------> {0.0.0.0}:

range2-end: ------------> {0.0.0.0}:
range3-start: ----------> {0.0.0.0}:
range3-end: ------------> {0.0.0.0}:
range4-start: ----------> {0.0.0.0}:
range4-end: ------------> {0.0.0.0}:
default-lease-time: ----> {-1}:
min-lease-time: --------> {-1}:
max-lease-time: --------> {-1}:
boot-server: -----------> {0.0.0.0}:
bootfile: --------------> {}:
default-router: --------> {0.0.0.0}: 10.0.0.1
primary-name-server: ---> {0.0.0.0}:
secondary-name-server: -> {0.0.0.0}:
domain-name: -----------> {}:
subnetgroup: -----------> {0}: 1 This number does not have to match the subnet index
stickyaddr: ------------> {enable}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

5 Issue the host add command to create the IP interface, ATM VCL, and IP
address for individual subscribers.
The following example adds dynamically assigned hosts:
zSH> host add 1-11-1-0/adsl vc 0/35 txtd 100 rxtd 1 llc dynamic 1 3

This example:
– creates an ip-interface-record on 1-11-1-0/adsl
– creates an atm-vcl with VPI/VCI=0/35 and LLC encapsulation of
AAL5 data, which accommodates DSL routers
– creates an ATM cross connect from the virtual interface on the Uplink
card to the designated slot card
– uses atm-traf-descr 100 for the transmit and atm-traf-descr 1 for
the receive sides of the connection since ADSL is an asymmetrical
connection
– adds 3 host entries that will have their addresses assigned
dynamically as defined by subnetgroup 1.

Note: Hosts that already have DHCP-assigned addresses will

need to renew those leases after the DHCP change. This is done
by rebooting the host.

The following example adds a statically assigned host:

zSH> host add 1-11-2-0/adsl vc 0/35 td 1 llc static 10.10.10.1

This example:
– creates an ip-interface-record on 1-11-2-0/adsl

70 MALC Configuration Guide

 IP provisioning procedures

– creates an atm-vcl with VPI/VCI=0/35 and LLC encapsulation of

AAL5 data
– creates an ATM cross connect from the virtual interface on the Uplink
card to the designated slot card
– uses atm-traf-descr 1 for the connection
– adds 1 host entry IP address 10.0.0.1.
6 Verify that hosts have been added:
zSH> host show
Rd/Address Interface Group T Host Address
--------------------------------------------------------------------------------
1 10.0.0.1 1-11-1-0-adsl-0-35 0/32 1 D <unassigned>
D <unassigned>
D <unassigned>

7 To find the other end of the ATM cross connect:

zSH> find-matching-data ATM 1-11-1-0-adsl/atm 0 35
VCL 1-11-1-0-adsl/atm 0 35 is used in atm-cc 1
The far end of this cross connect is
1-1-1-0-propvirtual/atm 0 32

8 To see the ATM virtual interfaces created by the host add command:
zSH> list atm-vcl
atm-vcl 1-11-1-0-adsl/atm/0/35
atm-vcl 1-1-1-0-propvirtual/atm/0/32
2 entries found.

9 To see the ATM cross connect created:

zSH> get atm-cc 1
cc-index: ------> {1}
low-if-index: --> {1-1-1-0-propvirtual/atm} virtual interface on the Uplink card
low-vpi: -------> {0}
low-vci: -------> {32}
high-if-index: -> {1-11-1-0-adsl/atm} the slot card
high-vpi: ------> {0}
high-vci: ------> {35}
admin-status: --> {up}

Configuring host-based routing with DSL bridges

1 Create an atm-traf-descr for unnumbered interfaces:
zSH> new atm-traf-descr 100
Please provide the following: [q]uit.
td_type: -----------------> {atmNoClpNoScr}:
td_param1: ---------------> {0}: 106133
td_param2: ---------------> {0}: 38
td_param3: ---------------> {0}:
td_param4: ---------------> {0}:

MALC Configuration Guide 71

Configuring IP

td_param5: ---------------> {0}:

cac-divider: -------------> {1}:
td_service_category: -----> {ubr}:
td_frame_discard: --------> {false}:
usage-parameter-control: -> {true}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

2 Create an ip-interface-record for the IP address that is to be shared for

all devices in the host-based routing subnet. The example uses the name/
type syntax.
zSH> new ip-interface-record ptm1/ip
Please provide the following: [q]uit.
vpi: ---------------> {0}:
vci: ---------------> {0}:
rdindex: -----------> {1}:
dhcp: --------------> {none}: ** read-only **
addr: --------------> {0.0.0.0}: 10.0.0.1
netmask: -----------> {0.0.0.0}: 255.0.0.0
bcastaddr: ---------> {0.0.0.0}: 10.255.255.255
destaddr: ----------> {0.0.0.0}:
farendaddr: --------> {0.0.0.0}:
mru: ---------------> {1500}:
reasmmaxsize: ------> {0}:
ingressfiltername: -> {}:
egressfiltername: --> {}:
pointtopoint: ------> {no}:
mcastenabled: ------> {yes}:
ipfwdenabled: ------> {yes}:
mcastfwdenabled: ---> {yes}:
natenabled: --------> {no}:
bcastenabled: ------> {yes}:
ingressfilterid: ---> {0}:
egressfilterid: ----> {0}:
ipaddrdynamic: -----> {static}:
dhcpserverenable: --> {false}:
subnetgroup: -------> {0}:
unnumberedindex: ---> {0}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
Cannot determine binding for this IP interface.
Could not automatically bind this IP Interface
New record saved.

Note: This is a virtual interface that will share its IP address;

binding the IP interface is not necessary.

3 Create an ip-unnumbered-record for the IP interface you just created.

Enter the name/type used in for ip-interface-record (from Step 2) as the
ipUnnumberedinterface value.

72 MALC Configuration Guide

 IP provisioning procedures

zSH> new ip-unnumbered-record 1

Please provide the following: [q]uit.
ipUnnumberedInterfaceName: -> { }: ptm1/ip
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

4 Create a dhcp-server-subnet record for each customer, specifying the

range (or pool) of assignable addresses which that customer can be
assigned.
zSH> new dhcp-server-subnet 99
Please provide the following: [q]uit.
network: ---------------> {0.0.0.0}: 10.0.0.0
netmask: ---------------> {0.0.0.0}: 255.0.0.0
domain: ----------------> {0}: 1
range1-start: ----------> {0.0.0.0}: 10.0.0.10
range1-end: ------------> {0.0.0.0}: 10.0.0.20
range2-start: ----------> {0.0.0.0}:
range2-end: ------------> {0.0.0.0}:
range3-start: ----------> {0.0.0.0}:
range3-end: ------------> {0.0.0.0}:
range4-start: ----------> {0.0.0.0}:
range4-end: ------------> {0.0.0.0}:
default-lease-time: ----> {-1}:
min-lease-time: --------> {-1}:
max-lease-time: --------> {-1}:
boot-server: -----------> {0.0.0.0}:
bootfile: --------------> {}:
default-router: --------> {0.0.0.0}: 10.0.0.1
primary-name-server: ---> {0.0.0.0}:
secondary-name-server: -> {0.0.0.0}:
domain-name: -----------> {}:
subnetgroup: -----------> {0}: 1 This number does not have to match the subnet index
stickyaddr: ------------> {enable}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

5 Issue the host add command to create the IP interface, ATM VCL, and IP
address for individual subscribers.
The following example adds dynamically assigned hosts:
zSH> host add 1-11-1-0/adsl vc 0/35 txtd 100 rxtd 1 dynamic 1 3

This example:
– creates an ip-interface-record on 1-11-1-0/adsl
– creates an atm-vcl with VPI/VCI=0/35 and RFC 1483 encapsulation
of AAL5 data, which accommodates DSL bridges
– creates an ATM cross connect from the virtual interface on the Uplink
card to the designated slot card

MALC Configuration Guide 73

Configuring IP

– uses atm-traf-descr 100 for the transmit and atm-traf-descr 1 for

the receive sides of the connection since ADSL is an asymmetrical
connection
– adds 3 host entries that will have their addresses assigned
dynamically as defined by subnetgroup 1.

Note: Hosts that already have DHCP-assigned addresses will

need to renew those leases after the DHCP change. This is done
by rebooting the host.

Configuring network-based routing

Similar to host-based routing, network-based routing interoperates with DSL

bridges and routers. The type of AAL5 encapsulation determines
interoperability with DSL routers or DSL bridges. LLC encapsulation is used
with DSL routers; RFC 1483 encapsulation is used with DSL bridges. Specify
bridge in the command line to connect to DSL bridges. If no encapsulation
type is specified in the command line, LLC encapsulation (llc) is the default.
The following table summarizes the configuration tasks for adding
network-based routes.

Task Command

Create an atm-traf-descr. new atm-traf-descr index

Where index is a user-defined value.

Configure a connection to routed interface add index/type vc vpi/vci td tdvalue |

subnets. txtd tdvalue rxtd tdvalue llc | other IPaddress
This command creates the VCL and IP interface for the host route.

Verify provisioning interface show

Configuring network-based routing with DSL routers

1 Create an atm-traf-descr for unnumbered interfaces:
zSH> new atm-traf-descr 100
Please provide the following: [q]uit.
td_type: -----------------> {atmNoClpNoScr}:
td_param1: ---------------> {0}: 106133
td_param2: ---------------> {0}: 38
td_param3: ---------------> {0}:
td_param4: ---------------> {0}:
td_param5: ---------------> {0}:
cac-divider: -------------> {1}:
td_service_category: -----> {ubr}:
td_frame_discard: --------> {false}:
usage-parameter-control: -> {true}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s

74 MALC Configuration Guide

 IP provisioning procedures

New record saved.

2 Issue the interface add command to create the IP interface, ATM VCL,
and IP address allocation:
zSH> interface add 1-5-1-0/adsl vc 0/35 td 1 10.10.10.10 255.255.255.0
Created ip-interface-record 1-5-1-0-adsl-0-35/ip

This example:
– creates an ip-interface-record on 1-5-1-0/adsl
– creates an atm-vcl with VPI/VCI=0/35 and LLC encapsulation of
AAL5 data, which accommodates DSL routers
– uses atm-traf-descr 1 for transmit and receive sides of the
connection
– creates an ATM cross connect from the virtual interface on the Uplink
card to the designated slot card
– adds IP address 10.0.0.1 with a subnetwork defined by the netmask.
3 Verify that interfaces have been added:
zSH> interface show
Interface Status Rd/Address Media/Dest Address IfName
--------------------------------------------------------------------------------
1/1/1/0/ip DOWN 1 10.10.10.10/24 0/36 1-5-1-0-adsl-0-35
--------------------------------------------------------------------------------

4 To find the other end of the ATM cross connect:

zSH> find-matching-data ATM 1-5-1-0-adsl/atm 0 35
VCL 1-5-1-0-adsl/atm 0 35 is used in atm-cc 5
The far end of this cross connect is 1-1-1-0-propvirtual/atm 0 36

5 To see the ATM virtual interfaces created by the interface add command:
zSH> list atm-vcl
atm-vcl 1-5-1-0-adsl/atm/0/35
atm-vcl 1-1-1-0-propvirtual/atm/0/36
2 entries found.

6 To see the ATM cross connect created:

zSH> get atm-cc 5
cc-index: ------> {5}
low-if-index: --> {1-1-1-0-propvirtual/atm} virtual interface on the Uplink card
low-vpi: -------> {0}
low-vci: -------> {36}
high-if-index: -> {1-5-1-0-adsl/atm} the slot card
high-vpi: ------> {0}
high-vci: ------> {39}
admin-status: --> {up}

MALC Configuration Guide 75

Configuring IP

Configuring network-based routing with DSL bridges

1 Create an atm-traf-descr for unnumbered interfaces:
zSH> new atm-traf-descr 100
Please provide the following: [q]uit.
td_type: -----------------> {atmNoClpNoScr}:
td_param1: ---------------> {0}: 106133
td_param2: ---------------> {0}: 38
td_param3: ---------------> {0}:
td_param4: ---------------> {0}:
td_param5: ---------------> {0}:
cac-divider: -------------> {1}:
td_service_category: -----> {ubr}:
td_frame_discard: --------> {false}:
usage-parameter-control: -> {true}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

2 Issue the interface add command to create the IP interface, ATM VCL,
and IP address allocation:
zSH> interface add 1-5-1-0/adsl vc 0/35 td 1 other 10.10.10.10 255.255.255.0
Created ip-interface-record 1-5-1-0-adsl-0-35/ip

This example:
– creates an ip-interface-record on 1-5-1-0/adsl
– creates an atm-vcl with VPI/VCI=0/35 and RFC 1483 encapsulation
of AAL5 data, which accommodates DSL bridges
– uses atm-traf-descr 1 for transmit and receive sides of the
connection
– creates an ATM cross connect from the virtual interface on the Uplink
card to the designated slot card
– adds IP address 10.0.0.1 with a subnetwork defined by the netmask.
3 Verify that interfaces have been added:
zSH> interface show
Interface Status Rd/Address Media/Dest Address IfName
--------------------------------------------------------------------------------
1/1/1/0/ip UP 1 10.10.10.10/24 0/35 multipoint 1-5-1-0-adsl-0-35
--------------------------------------------------------------------------------

4 To find the other end of the ATM cross connect:

zSH> find-matching-data ATM 1-5-1-0-adsl/atm 0 35
VCL 1-5-1-0-adsl/atm 0 35 is used in atm-cc 5
The far end of this cross connect is 1-1-1-0-propvirtual/atm 0 36

5 To see the ATM virtual interfaces created by the interface add command:

76 MALC Configuration Guide

 IP provisioning procedures

zSH> list atm-vcl

atm-vcl 1-5-1-0-adsl/atm/0/35
atm-vcl 1-1-1-0-propvirtual/atm/0/36
2 entries found.

6 To see the ATM cross connect created:

zSH> get atm-cc 5
cc-index: ------> {5}
low-if-index: --> {1-1-1-0-propvirtual/atm} virtual interface on the Uplink card
low-vpi: -------> {0}
low-vci: -------> {36}
high-if-index: -> {1-5-1-0-adsl/atm} the slot card
high-vpi: ------> {0}
high-vci: ------> {39}
admin-status: --> {up}

Configuring RIP

RIP behavior for the system as a whole is configured in the rip-global-config

profile. Each IP interface is then configured for RIP using the rip command.
Currently, the MALC supports RIP v1 and v2. Note that the only routing
domain currently supported is domain 1.

Configuring RIP global defaults

The following example configures RIP global behavior on the MALC:
1 Enable RIP for the system as a whole:
zSH> rip enable

2 To enable receipt of RIP version 1 or version 2 advertisements on an

interface, use the rip command and specify the interface and the type of
advertisements to receive:
zSH> rip interface 172.16.92.191 listen v1v2
3 To enable transmission of RIP advertisements on an interface:
a zSH> rip interface 172.16.92.191 talk v2
or
b zSH> rip interface 172.16.92.191 talk v1compat

Configuring static routes

Use the route command to add or delete static routes.

Adding routes
To add static routes, use the route add command. The command uses the
following syntax:

MALC Configuration Guide 77

Configuring IP

route add destination mask next-hop cost

Note: The word default can be substituted for a 0.0.0.0 destination

and mask.

The following example creates a network route to 192.178.21.0 using the

gateway 192.172.16.1:
route add 192.178.21.0 255.255.255.0 192.178.16.1 1
The following example creates a default route using the gateway
192.172.16.1:
route add default 192.178.16.1 1

Configuring the device as a DHCP server

The MALC DHCP supports the following types of DHCP configurations:

• Dynamic address allocation, where the server chooses and allocates an IP
address with a finite lease. By default, the MALC will attempt to assign
the same address (if available) to a device on lease renewal. This default
can be changed to force a new address to be assigned.
• Static address allocation, where the server allocates the same IP address
every time a device connects to the network.

DHCP server profiles and scope

Use the following profiles to configure the devices as a DHCP server:
• dhcp-server-options—Configures a default profile that is used to
generate default configurations for networks that are not explicitly
configured. See Setting DHCP server options on page 79 for more
information.
• dhcp-server-subnet—Defines options for a specific network that is being
managed by the DHCP server. Settings in the dhcp-server-subnet record
override the default address pool set up by the dhcp-server-options
record. See Creating DHCP server subnet options on page 81 for more
information.
• dhcp-server-group—Defines options for a set of clients in a given
domain. Inclusion of a given client into the group is based on a substring
match of either the client’s DHCP vendor class identifier, its DHCP client
identifier values, or both. The scope of a group object always overrides
those of a subnet object for any DHCP client lease. See Advanced DHCP
applications on page 86 for more information.
• dhcp-server-host—Defines options for a specific host within a given
domain. See Advanced DHCP applications on page 86 for more
information.

78 MALC Configuration Guide

 IP provisioning procedures

• ip-interface-record—enables DHCP on the interface. The IP address

defined in the ip-interface-record is used to determine the DHCP
address pool for the attached network. See Enabling a DHCP server on
page 83 for more information.
The DHCP server looks for configuration settings in order from the most
specific record (the dhcp-server-host) to the most general (the
dhcp-server-options record). It uses parameter settings in the following
order:
1. dhcp-server-host
2. dhcp-server-group
3. dhcp-server-subnet
4. dhcp-server-options
If a parameter is set in multiple profiles (for example, lease times or default
routers), the MALC uses the settings that are in the most specific record. This
means that the DHCP server could use parameter settings in multiple records
(if, for example, all client lease times were set in the dhcp-server-options
record, and address ranges were set in the dhcp-server-subnet records.)
If only the dhcp-server-options record exists, the MALC uses those settings
as the default for all DHCP server interfaces. For information about logging
DHCP requests, see DHCP logging on page 102.

Setting DHCP server options

At startup, the MALC creates a default dhcp-server-options record. This
profile defines global options for the MALC DHCP server.
The following example shows the dhcp-server-options profile with its
default values:
zSH> get dhcp-server-options 0
Please provide the following: [q]uit.
lease-time: -----> {43200}:
min-lease-time: -> {0}:
max-lease-time: -> {86400}:
reserve-start: --> {5}:
reserve-end: ----> {5}:
restart: --------> {no}:

MALC Configuration Guide 79

Configuring IP

The dhcp-server-options profile supports the following parameters (all

others should be left at their default values):

Parameter Description

lease-time The global default time in seconds that

will be assigned to a DHCP lease if the
client requesting the lease does not
request a specific expiration time.

min-lease-time The minimum expiration time in

seconds that will be assigned to a
DHCP lease by the server, regardless
of the value specified by a client.
Values:
-1 to 2147483647
-1 indicates the parameter should be
ignored.
Default: 0

max-lease-time The maximum time in seconds that

will be assigned to a lease regardless
of the value specified by a client.
Values:
-1 to 2147483647.
-1 indicates the parameter should be
ignored.
Default: 86400

reserve-start The default number of IP addresses, at

the beginning of the MALC subnet IP
address space, that are reserved by the
DHCP server. To override this default,
create a specific subnet rule for each
subnet that needs to be handled
differently.

reserve-end The default number of IP addresses at

the end of the MALC ‘s subnet IP
address space that are reserved by the
DHCP server. To override this default,
create a specific subnet rule for each
subnet that needs to be handled
differently.

The following example changes the dhcp-server-options record to specify

that each DHCP server reserve the first 10 addresses and the last 10 addresses
in a network and does not include them in the DHCP server address pool.
zSH> update dhcp-server-options 0
Please provide the following: [q]uit.
lease-time: -----> {43200}:
min-lease-time: -> {0}:

80 MALC Configuration Guide

 IP provisioning procedures

max-lease-time: -> {86400}:

reserve-start: --> {5}: 10
reserve-end: ----> {5}: 10
restart: --------> {no}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

In this example, if a DHCP server on the 192.168.9.0 network reserved the

first 10 addresses and last 10 addresses, it would assign addresses from
192.168.9.11 to 192.168.9.244.

Creating DHCP server subnet options

The dhcp-server-subnet profile allows you to define options for a specific
network that is being managed by the DHCP server. All subnets within a
routing domain must be unique, so a given subnet object will provide options
for exactly one connected network.
The dhcp-server-subnet profile supports the following parameters (all others
should be left at their default values):

Parameter Description

network The IP network address of this subnet.

netmask The subnet mask associated with the IP interface.

The value of the mask is an IP address with all the
network bits set to 1 and all the hosts bits set to 0.

domain The routing domain to which this subnet, group, or

host parameter applies.

range1-start, The starting IP address of an address pool in this

range2-start, subnet. If either the start or end range has a value of
range3-start, 0 then the entire address pool is ignored.
range4-start

range1-end, range2-end, The ending IP address of an address pool in this

range3-end, range4-end subnet. If either the start or end range has a value of
0, then the entire address pool is ignored.
default-lease-time The default time, in seconds assigned to a lease if
the client requesting the lease does not request a
specific expiration time.

min-lease-time See description in dhcp-server-options profile.

max-lease-time See description in dhcp-server-options profile.

boot-server The IP address of the server from which the initial

boot file (specified in the bootfile parameter) is to
be loaded.

MALC Configuration Guide 81

Configuring IP

Parameter Description

bootfile The name of the initial boot file loaded by the

client. The filename should be recognizable to the
file transfer protocol that the client will be using to
load the file.
default-router The IP address of the client default gateway.

primary-name-server The IP address of the primary domain name server

that the client should use for DNS resolution.

secondary-name-server The IP address of the secondary domain name

server that the client should use for DNS resolution.

domain-name The name of the DNS domain.

subnetgroup A number which indicates which DHCP subnet

group this pool is a member of. A value of 0
(default) indicates that the subnet is not a member
of any group.

stickyaddr The DHCP server attempts to assign the same IP

address to the same host, if possible, based on
hardware address.
Values:
disable
enable
Default: enable

The following example defines a DHCP server subnet profile that is set up as
follows:
• Defines a single DHCP address pool with 11 addresses.
• Defines a default router.
• Defines a boot server and a boot filename.
• Defines a domain name.
• Defines two DNS servers.
• Uses the minimum, maximum, and default lease time (by accepting the
default settings for the default-lease-time, min-lease-time, and
max-lease-time).
zSH> new dhcp-server-subnet 12
Please provide the following: [q]uit.
network: ---------------> {0.0.0.0}: 192.168.1.0
netmask: ---------------> {0.0.0.0}: 255.255.255.0
domain: ----------------> {0}: 1
range1-start: ----------> {0.0.0.0}: 192.168.1.10
range1-end: ------------> {0.0.0.0}: 192.168.1.20
range2-start: ----------> {0.0.0.0}:
range2-end: ------------> {0.0.0.0}:

82 MALC Configuration Guide

 IP provisioning procedures

range3-start: ----------> {0.0.0.0}:

range3-end: ------------> {0.0.0.0}:
range4-start: ----------> {0.0.0.0}:
range4-end: ------------> {0.0.0.0}:
default-lease-time: ----> {-1}:
min-lease-time: --------> {-1}:
max-lease-time: --------> {-1}:
boot-server: -----------> {0.0.0.0}: 192.168.1.55
bootfile: --------------> {}: filename.bin
default-router: --------> {0.0.0.0}: 192.168.1.1
primary-name-server: ---> {0.0.0.0}: 192.168.8.21
secondary-name-server: -> {0.0.0.0}: 201.23.20.2
domain-name: -----------> {}: zhone.com
subnetgroup: -----------> {0}:
stickyaddr: ------------> {enable}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Enabling a DHCP server

Modify the following parameters in the ip-interface-record to enable DHCP
server (all others should be left at their default values):

Parameter Description

dhcp Indicates whether this interface is a DHCP client, a

DHCP server, both, or neither.
Values:
none
client
server
both
Default: none

address The IP address of LAN port.

The following example enables the DHCP server on an IP-enabled interface

in MALC shelf 1, slot 1, port 2, and subport 0.
zSH> update ip-interface-record 1/1/2/0/ip
Please provide the following: [q]uit.
vpi: ---------------> {0}:
vci: ---------------> {0}:
rdindex: -----------> {1}:
dhcp: --------------> {none}: ** read-only **
addr: --------------> {172.24.200.162}:
netmask: -----------> {255.255.255.0}:
bcastaddr: ---------> {172.24.200.255}:
destaddr: ----------> {0.0.0.0}:
farendaddr: --------> {0.0.0.0}:

MALC Configuration Guide 83

Configuring IP

mru: ---------------> {1500}:

reasmmaxsize: ------> {0}:
ingressfiltername: -> {}:
egressfiltername: --> {}:
pointtopoint: ------> {no}:
mcastenabled: ------> {yes}:
ipfwdenabled: ------> {yes}:
mcastfwdenabled: ---> {yes}:
natenabled: --------> {no}:
bcastenabled: ------> {yes}:
ingressfilterid: ---> {0}:
egressfilterid: ----> {0}:
ipaddrdynamic: -----> {static}:
dhcpserverenable: --> {false}: true
subnetgroup: -------> {0}:
unnumberedindex: ---> {0}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

DHCP relay

The MALC supports DHCP relay. DHCP broadcast messages do not, by

default, cross the router interfaces. To solve the problem of DHCP broadcast
messages on multiple-subnet, the MALC can be configured as a DHCP relay
agent that communicates with a DHCP server and acts as a proxy for DHCP
broadcast messages that need to be routed to remote segments.
In DHCP relay scenarios, the MALC serves as a DHCP relay agent that
forwards broadcast DHCP discover and DHCP request packets to an external
DHCP server. It then forwards the unicast DHCP offer and DHCP ack/nak
replies to the requesting DHCP host.

84 MALC Configuration Guide

 IP provisioning procedures

Figure 12: DHCP relay

DHCP server

DHCP client

DHCP relay agent

Note the following requirements for DHCP relay:

• The external DHCP server must be configured to assign addresses on the
same subnet as the floating IP address used by the remote device.
• The external DHCP server must be configured with a static route for the
remote device’s subnet back to the MALC on which the relay agent is
running. (The DHCP server will send DHCP unicast packets to the relay
agent’s address, which is the first one in the subnet.)
• A separate DHCP server can be specified per subnet.

Specifying an external DHCP server

Configure DHCP relay in the dhcp-server-subnet. The following parameter
has been added to this profile:

Parameter Description

external-server Enable an external subnet server in order to

support DHCP relay agent.
Default: 0.0.0.0

To specify an external DHCP server:

1 Create a dhcp-server-subnet profile and specify the IP address of the
external server:
zSH> new dhcp-server-subnet 1
Please provide the following: [q]uit.
network: ---------------> {172.24.41.0}:
netmask: ---------------> {255.255.255.0}:
domain: ----------------> {1}:

MALC Configuration Guide 85

Configuring IP

range1-start: ----------> {172.24.41.11}:

range1-end: ------------> {172.24.41.100}:
range2-start: ----------> {0.0.0.0}:
range2-end: ------------> {0.0.0.0}:
range3-start: ----------> {0.0.0.0}:
range3-end: ------------> {0.0.0.0}:
range4-start: ----------> {0.0.0.0}:
range4-end: ------------> {0.0.0.0}:
default-lease-time: ----> {-1}:
min-lease-time: --------> {-1}:
max-lease-time: --------> {-1}:
boot-server: -----------> {172.24.38.102}:
bootfile: --------------> {i3micro/
etherboot-I3M-i.img}:
default-router: --------> {172.24.41.254}:
primary-name-server: ---> {172.24.38.102}:
secondary-name-server: -> {0.0.0.0}:
domain-name: -----------> {nat.myrio.net}:
subnetgroup: -----------> {1}:
stickyaddr: ------------> {enable}:
external-server: -------> {0.0.0.0}: 172.16.88.71
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

2 Create a host route and specify the subnet group. For example:
zSH> host add 1-1-1-0/adsl vc 0/36 td 200 dynamic 1 1

This specifies that the host route over the specified ATM interface uses
dynamic addressing and subnet group number 1.

Advanced IP provisioning procedures

The following advanced IP procedures are supported on the MALC:
• Advanced DHCP applications on page 86
• Configuring DNS resolver on page 88
• Configuring IP filters on page 90

Advanced DHCP applications

This section explains how to configure more advanced DHCP applications. It

includes the following sections:
• Creating dhcp-server-group profile on page 87
• Creating dhcp-server-host profile on page 87

86 MALC Configuration Guide

 Advanced IP provisioning procedures

Creating dhcp-server-group profile

The dhcp-server-group defines options for a set of clients in a given domain.
Inclusion of a given client into the group is based on a substring match of
either the client’s DHCP vendor class identifier, its DHCP client identifier
values, or both. The scope of a group object always overrides those of a
subnet object for any DHCP client lease.
Modify the following parameters to create a new dhcp-server-group profile:

Parameter Description

name The DHCP server group name.

vendor-match-string The vendor class identifier match

string that determines which clients
should be placed in the group.

client-match-string Client identifier match string that

determines which clients should be
placed in this group.

zSH> new dhcp-server-group 1

Please provide the following: [q]uit.
name: ------------------> {}: group1
domain: ----------------> {0}:
vendor-match-string: ---> {}: 'oakland' this is converted to an octet string
vendor-match-offset: ---> {0}:
vendor-match-length: ---> {-1}:
client-match-string: ---> {}: 'oakland'this is converted to an octet string
client-match-offset: ---> {0}:
client-match-length: ---> {-1}:
default-lease-time: ----> {-1}:
min-lease-time: --------> {-1}:
max-lease-time: --------> {-1}:
boot-server: -----------> {0.0.0.0}:
bootfile: --------------> {}:
default-router: --------> {0.0.0.0}:
primary-name-server: ---> {0.0.0.0}:
secondary-name-server: -> {0.0.0.0}:
domain-name: -----------> {}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
Record created.

Creating dhcp-server-host profile

The dhcp-server-host defines options for a specific host within a given
domain.
Set the following parameters in the dhcp-server-host profile:

MALC Configuration Guide 87

Configuring IP

Parameter Description

name The DHCP host name for the client

hwaddr The MAC address of the network

interface that was used to acquire the
lease.

clientId The DHCP client identifier

zSH> new dhcp-server-host 1

Please provide the following: [q]uit.
name: ------------------> {}: host1
domain: ----------------> {0}:
hardware-address: ------> {}: 09:00:07:A9:B2:EB
client-identifier: -----> {}: ‘clientgroup1’
ipaddr1: ---------------> {0.0.0.0}:
ipaddr2: ---------------> {0.0.0.0}:
ipaddr3: ---------------> {0.0.0.0}:
ipaddr4: ---------------> {0.0.0.0}:
default-lease-time: ----> {-1}:
min-lease-time: --------> {-1}:
max-lease-time: --------> {-1}:
boot-server: -----------> {0.0.0.0}:
bootfile: --------------> {}:
default-router: --------> {0.0.0.0}:
primary-name-server: ---> {0.0.0.0}:
secondary-name-server: -> {0.0.0.0}:
domain-name: -----------> {}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
Record created.

Configuring DNS resolver

Domain Name System (DNS) maps domain names to IP addresses, enabling

the system to reach destinations when it knows only the domain name of the
destination. DNS configuration uses the following profiles:
• resolver—Configures the global DNS resolver, including the DNS search
order, default domain name, and list of nameserver addresses. The DNS
settings in this record can be used for local applications by administrators
on the system, such as traceroute or ping.
• host-name—A replacement for the Unix local hosts table. Up to four host
aliases can be defined for each host entry. Settings in the resolver record
determine whether the hosts table is searched.

88 MALC Configuration Guide

 Advanced IP provisioning procedures

The resolver profile supports the following parameters (all others should be
left at their default values):

Parameter Description

query-order The kind of resolver query for this

routing domain.
Values:
hosts-first searches the local hosts
table first then the list of nameservers.
dns-first searches the list of
nameservers first then the local hosts
table.
dns-only searches only the list of
nameservers.
Default: hosts-first

domain The routing domain to which this host

parameter applies. The default is an
empty string.
The only routing domain supported is
domain 1.

first-nameserver The IP address of the first or primary

nameserver for this routing domain.
The default value is 0.0.0.0.

second-nameserver The IP address of the second or

secondary nameserver for this routing
domain. This nameserver is queried if
the first nameserver cannot resolve the
query. The default value is 0.0.0.0.

third-nameserver The IP address of the third or tertiary

nameserver for this routing domain.
This nameserver is queried if the first
nameserver cannot resolve the query.
The default value is 0.0.0.0.

The following example creates a resolver record for a routing domain:

zSH> new resolver 1
Please provide the following: [q]uit.
query-order: -------> {hosts-first}:
domain: ------------> {}: zhone.com
first-nameserver: --> {0.0.0.0}: 192.168.8.21
second-nameserver: -> {0.0.0.0}: 201.23.20.2
third-nameserver: --> {0.0.0.0}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
Record created.

MALC Configuration Guide 89

Configuring IP

Optionally, you can create a hosts profile after the resolver profile has been
created. The syntax is new host-name routingdomain/ipoctet1/ipoctet2/
ipoctet3/ipoctet4.
The host-name profile supports the following parameters (all others should
be left at their default values):

Parameter Description

hostname Client host name (if any) that the client

used to acquire its address. The default
is an empty string.

hostalias1 Host name alias for the specified host.

The default value is an empty string.

hostalias2 Secondary host name alias for the

specified host. The default value is an
empty string.

hostalias3 Tertiary host name alias for the

specified host. The default value is an
empty string.

hostalias4 Quaternary host name alias for the

specified host. The default value is an
empty string.

zSH> new host-name 1/192/168/8/32

Please provide the following: [q]uit.
hostname: ---> {}: www.zhone.com
ipaddress: --> {0.0.0.0}: 192.168.8.32
hostalias1: -> {}: engineering.zhone.com
hostalias2: -> {}: marketing.zhone.com
hostalias3: -> {}: sales.zhone.com
hostalias4: -> {}: gss.zhone.com
....................
Save new record? [s]ave, [c]hange or [q]uit: s
Record created.

Configuring IP filters

The following table summarizes the configuration tasks for configuring IP

filters.

Task Command

Create a new filter. filter new

Specify what to filter. filter add rule [from | to] [IP address] [permit
| deny]

Save the filter. filter save

Apply the filter to an IP interface. update ip-interface-record interface

90 MALC Configuration Guide

 Advanced IP provisioning procedures

Task Command

Show filters created. filter show index

Edit existing filters. filter load index

filter delete index

Configuring IP filters
Follow these steps to set up IP filtering:
1 Use the filter new command to create a new filter. The filter will be given
an index value which you can use to specify the filter. The example below
creates a filter with an index value of 5.
zSH> filter new
filter: 5 successfully created and loaded for editing

2 After creating the filter, rules must be applied to it. To do this, use the
filter add command. The syntax is:
filter add rule [from | to] [IP address] [permit | deny]

The rule is a user-defined value for the filtering rules to be applied.

The example below permits traffic from 192.168.1.15, but denies traffic
from all others:
zSH> filter add from 192.168.1.15 permit
5/101 from 192.168.1.15 permit
zSH> filter add deny
5/110 deny

You can also specify a range of IP addresses on which to filter:

zSH> filter add 102 from 10.0.0.1-10.0.0.254 permit
5/102 from 10.0.0.1-10.0.0.254 permit
zSH> filter add 192.168.1.15 permit
5/120 deny

You can also specify both source and destination addresses in the same
rule:
zSH> filter add 103 from 10.0.0.1-10.0.0.254 to 192.168.0.0-192.168.0.254 permit
5/103 from 10.0.0.1-10.0.0.254 to 192.168.0.0-192.168.0.254 permit
zSH> filter add 130 deny
5/130 deny

3 Once you have added rules to a filter, you must save it with the filter save
command:
zSH> filter save
Save loaded filter: 5 (it has been modified) yes/no [yes]? yes
filter: 5 has been saved

MALC Configuration Guide 91

Configuring IP

4 After you have saved your filter, you will need to apply it to an IP
interface. Update the ip-interface record where you wish to apply the
filter. Insert the filter index value in the ingressfilterid or egressfilterid
parameter:
zSH> update ip-interface-record 1/1/1/0/ip
Please provide the following: [q]uit.
vpi: ---------------> {0}:
vci: ---------------> {0}:
rdindex: -----------> {1}:
dhcp: --------------> {none}:
addr: --------------> {172.16.160.11}:
netmask: -----------> {255.255.255.0}:
bcastaddr: ---------> {172.16.160.255}:
destaddr: ----------> {0.0.0.0}:
farendaddr: --------> {0.0.0.0}:
mru: ---------------> {1500}:
reasmmaxsize: ------> {0}:
ingressfiltername: -> {}:
egressfiltername: --> {}:
pointtopoint: ------> {no}:
mcastenabled: ------> {yes}:
ipfwdenabled: ------> {yes}:
mcastfwdenabled: ---> {yes}:
natenabled: --------> {no}:
bcastenabled: ------> {yes}:
ingressfilterid: ---> {0}: 5 the number of the filter
egressfilterid: ----> {0}: 5 the number of the filter
ipaddrdynamic: -----> {static}
dhcpserverenable: --> {false}
subnetgroup: -------> {0}
unnumberedindex: ---> {0}
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated

5 Use the filter show command (with the filter index) to view created
filters:
zSH> filter show 5
Filter: 5
Line Rule ---- ----
101 from 192.168.1.15 permit
102 from 10.0.0.1-10.0.0.254 permit
103 from 10.0.0.1-10.0.0.254 to 192.168.0.0-192.168.0.254 permit
150 from 192.168.120.1-192.168.123.254 to 192.168.120.16 permit

6 If you wish to edit a filter, use the filter load filterID command to load the
filter for editing. Then use the filter delete RuleNum command to delete
rules from the filter.
zSH> filter load 5
filter: 5 successfully loaded for editing

92 MALC Configuration Guide

 Configuring the MALC for IP video

zSH> filter delete 101

5/101 from 192.168.1.15 permit
Delete rule: 5/101 yes/no [yes]? yes
rule: 5/101 deleted

Use the rule add command to add new rules, and the rule save command
to save filter rules. See Step 2 and Step 3.

Note: Refer to the Zhone CLI Reference Guide for full

explanations of the filter command options and variables.

Configuring the MALC for IP video

When configuring an interface for IP video, you should dedicate a VCL to
deliver the IP video to the subscriber. transmitting other types of traffic over
the same VCL as video could affect the quality of the video.
This section provides an example of how to create a video connection on the
MALC.

Configuring the MALC video interface

1 Create a traffic descriptor:
zSH> new atm-traf-descr 5 index can be any value
Please provide the following: [q]uit.
td_type: -----------------> {atmNoClpNoScr}:
td_param1: ---------------> {0}: 27864
td_param2: ---------------> {0}:
td_param3: ---------------> {0}:
td_param4: ---------------> {0}:
td_param5: ---------------> {0}:
cac-divider: -------------> {1}:
td_service_category: -----> {ubr}: cbr
td_frame_discard: --------> {false}:
usage-parameter-control: -> {true}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

2 Create a DHCP server address pool for the far end video device. This
network must specify the network for the video server. This example
configures the MALC for DHCP relay:
zSH> new dhcp-server-subnet 0
Please provide the following: [q]uit.
network: ---------------> {0.0.0.0}: 10.7.1.0
netmask: ---------------> {0.0.0.0}: 255.255.255.248
domain: ----------------> {0}:
range1-start: ----------> {0.0.0.0}: 10.7.1.2
range1-end: ------------> {0.0.0.0}: 10.7.1.6
range2-start: ----------> {0.0.0.0}:

MALC Configuration Guide 93

Configuring IP

range2-end: ------------> {0.0.0.0}:

range3-start: ----------> {0.0.0.0}:
range3-end: ------------> {0.0.0.0}:
range4-start: ----------> {0.0.0.0}:
range4-end: ------------> {0.0.0.0}:
default-lease-time: ----> {-1}:
min-lease-time: --------> {-1}:
max-lease-time: --------> {-1}:
boot-server: -----------> {0.0.0.0}:
bootfile: --------------> {}:
default-router: --------> {0.0.0.0}:
primary-name-server: ---> {0.0.0.0}:
secondary-name-server: -> {0.0.0.0}:
domain-name: -----------> {}:
subnetgroup: -----------> {0}:
stickyaddr: ------------> {enable}:
external-server: -------> {0.0.0.0}: 10.7.1.25 the
external DHCP server address
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

3 Add a host route for the video interface:

zSH> host add 1-5-1-0/adsl vc 0/38 td 1 llc dynamic 1 1

4 Create a multicast control list, which defines which multicast addresses

the remote end video can access. Multicast control lists enable IP hosts to
send packets to a single IP address that references a control list of
multiple addresses. Multicast control lists contain a starting IP address,
ending IP address, and increment value. Devices use the Internet Group
Management Protocol (IGMP) to discover whether neighboring devices
are configured in multicast control lists.
Configure multicast control list using the multicast-control-entry
profile. The following parameters are available in this profile:

Parameter Description

IP address IP address to receive the multicast.

type Defines the video stream type.
Values:
normal Join and leave when desired. Used
for video.
always-on Always joined. Meant for
Emergency Broadcast System (EBS)
channel, not video.
periodic Join and leave after task complete.
For example, download the tv guide. Not
meant for video.
Default: normal

94 MALC Configuration Guide

 Configuring the MALC for IP video

The following example adds two entries to multicast list 1:

zSH> new mcast-control-entry 1/1
Please provide the following: [q]uit.
ip-address: -> {0.0.0.0}: 224.1.1.1
type: -------> {normal}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

zSH> new mcast-control-entry 1/2

Please provide the following: [q]uit.
ip-address: -> {0.0.0.0}: 224.1.1.2
type: -------> {perodic}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

zSH> new mcast-control-entry 1/3

Please provide the following: [q]uit.
ip-address: -> {0.0.0.0}: 224.1.1.3
type: -------> {always-on}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Continue adding as many multicast entries as necessary.

To view the multicast control group, use the mcast command:
zSH> mcast show mcl 1
MCAST CONTROL LIST : 1
224.1.1.1 224.1.1.2 224.1.1.3 224.1.1.4
224.1.1.5 224.1.1.6 224.1.1.7 224.1.1.8
224.10.10.10 224.10.10.11 224.10.10.12 224.10.10.13

5 Next, find the top-level IP address of the interface you created in Step 3
and specify the multicast control group for it to use. For example:
zSH> list ip-interface-record
ip-interface-record 192.168.49.1/ip
ip-interface-record 1-18-1-1-adsl-0-38/ip
ip-interface-record 1-18-1-1-adsl-0-38-1/ip
ip-interface-record 1-18-1-1-adsl-0-38-2/ip
ip-interface-record 1-18-1-1-adsl-0-38-3/ip
ip-interface-record 1-18-1-1-adsl-0-38-4/
ip-interface-record 1-18-1-4-adsl-3-38/ip
ip-interface-record 1-18-1-4-adsl-3-38-1/ip
ip-interface-record 1-18-1-4-adsl-3-38-2/ip
ip-interface-record 1-18-1-4-adsl-3-38-3/ip
ip-interface-record 1-18-1-4-adsl-3-38-4/ip
ip-interface-record 1-18-1-3-adsl-2-38/ip
ip-interface-record 1-18-1-3-adsl-2-38-1/ip
ip-interface-record 1-18-1-3-adsl-2-38-2/ip
ip-interface-record 1-18-1-3-adsl-2-38-3/ip

MALC Configuration Guide 95

Configuring IP

ip-interface-record 1-18-1-3-adsl-2-38-4/ip
ip-interface-record 1-18-1-3-adsl-2-36/ip
ip-interface-record 1-18-1-3-adsl-2-36-1/ip
ip-interface-record ethernet1/ip
<SPACE> for next page, <CR> for next line, A for all, Q
to quit

In this example, use ip-interface-record 1-18-1-1-adsl-0-38/ip because

it’s the interface associated with the host route created in Step 3.
6 Update the interface to point to the multicast control list you just created:
zSH> update ip-interface-record 1-18-1-1-adsl-0-38/ip
Please provide the following: [q]uit.
vpi: ---------------> {0}:
vci: ---------------> {32}:
rdindex: -----------> {1}:
dhcp: --------------> {server}: ** read-only **
addr: --------------> {192.168.49.1}:
netmask: -----------> {255.255.255.255}:
bcastaddr: ---------> {0.0.0.0}:
destaddr: ----------> {0.0.0.0}:
farendaddr: --------> {255.255.255.0}:
mru: ---------------> {1500}:
reasmmaxsize: ------> {0}:
ingressfiltername: -> {}:
egressfiltername: --> {}:
pointtopoint: ------> {yes}:
mcastenabled: ------> {yes}:
ipfwdenabled: ------> {yes}:
mcastfwdenabled: ---> {yes}:
natenabled: --------> {no}:
bcastenabled: ------> {no}:
ingressfilterid: ---> {0}:
egressfilterid: ----> {0}:
ipaddrdynamic: -----> {unnumbered}:
dhcpserverenable: --> {true}:
subnetgroup: -------> {1}:
unnumberedindex: ---> {1}:
mcastcontrollist: --> {0}: 1
vlanid: ------------> {0}:
maxVideoStreams: ---> {0}: 4
....................
Save changes? [s]ave, [c]hange or [q]uit:
Record updated.

7 Create a mapping between the ATM VCL and the multicast address
space. This example uses the Uplink interface to reach the IP video server.
zSH> new atm-vcl-to-multicast-map-profile 1
Please provide the following: [q]uit.
routing-domain: ----> {0}: 1
multicast-address: -> {0.0.0.0}: 224.1.1.1
ifIndex: -----------> { }: uplinkatm1-1-101/ip

96 MALC Configuration Guide

 IP administrative procedures

vpi: ---------------> {0}:

vci: ---------------> {0}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

To use an Ethernet uplink to reach the IP video server, enter the interface
in the ifIndex parameter.

Note: You only need to enter the first multicast address in the
group.

IP administrative procedures
The following IP administrative procedures are supported on the MALC:
• Modifying profiles created by host/interface add commands on page 97
• Displaying hosts on page 100
• Displaying interfaces on page 100
• Displaying routing information on page 100
• Deleting hosts on page 101
• Deleting interfaces on page 102
• Deleting routes on page 102
• DHCP logging on page 102

Modifying profiles created by host/interface add commands

After profiles have been created by the host add and interface add
commands there are two methods of modifying the profiles:
• You can perform a host delete or interface delete, which deletes all
associated profiles, then re-create those profiles with another host add or
interface add command, specifying changes in the command line.
• You can modify the individual profiles which have been created by host
add and interface add commands.
For example, the command:
zSH> host add 1-8-1-0/adsl vc 0/35 td 1 dynamic 1 3

Creates the following profiles:

ip-interface-record 1-8-1-0-adsl-0-35/ip
ip-interface-record 1-8-1-0-adsl-0-35-1/ip
ip-interface-record 1-8-1-0-adsl-0-35-2/ip
ip-interface-record 1-8-1-0-adsl-0-35-3/ip

MALC Configuration Guide 97

Configuring IP

atm-vcl 1-8-1-0-adsl/atm/0/35
atm-vcl 1-1-1-0-propvirtual/atm/0/32
atm-cc 1

Note: You must disable the cross-connect and the ATM-VCL before
changing the AAL5 encapsulation type in active cross-connects.

Modifying individual profiles created by host/interface add

1 Before modifying ATM-VCLs, the cross-connect in which they are used,
must be disabled:
zSH> update atm-cc 1
Please provide the following: [q]uit.
cc-index: ------> {1}: ** read-only **
low-if-index: --> {1-1-1-0-propvirtual/atm}: ** read-only **
low-vpi: -------> {0}: ** read-only **
low-vci: -------> {32}: ** read-only **
high-if-index: -> {1-8-1-0-adsl/atm}: ** read-only **
high-vpi: ------> {0}: ** read-only **
high-vci: ------> {35}: ** read-only **
admin-status: --> {up}: down
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

2 Active VCLs must be disabled before making any modifications to them:

zSH> update atm-vcl 1-8-1-0-adsl/atm/0/35
Please provide the following: [q]uit.
vpi: -----------------------------> {0}: ** read-only **
vci: -----------------------------> {35}: ** read-only **
admin_status: --------------------> {up}: down
receive_traffic_descr_index: -----> {1}:
transmit_traffic_descr_index: ----> {1}:
vcc_aal_type: --------------------> {other}: ** read-only **
vcc_aal5_cpcs_transmit_sdu_size: -> {9188}:
vcc_aal5_cpcs_receive_sdu_size: --> {9188}:
vcc_aal5_encaps_type: ------------> {other}:
vcl_cast_type: -------------------> {p2p}:
vcl_conn_kind: -------------------> {pvc}:
fault-detection-type: ------------> {disabled}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

3 Make changes to the VCL:

zSH> update atm-vcl 1-8-1-0-adsl/atm/0/35
Please provide the following: [q]uit.
vpi: -----------------------------> {0}: ** read-only **
vci: -----------------------------> {35}: ** read-only **
admin_status: --------------------> {down}:

98 MALC Configuration Guide

 IP administrative procedures

receive_traffic_descr_index: -----> {1}:

transmit_traffic_descr_index: ----> {1}:
vcc_aal_type: --------------------> {other}: ** read-only **
vcc_aal5_cpcs_transmit_sdu_size: -> {9188}:
vcc_aal5_cpcs_receive_sdu_size: --> {9188}:
vcc_aal5_encaps_type: ------------> {other}: llcencapsulation
vcl_cast_type: -------------------> {p2p}:
vcl_conn_kind: -------------------> {pvc}:
fault-detection-type: ------------> {disabled}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

4 Re-enable the VCL:

zSH> update atm-vcl 1-8-1-0-adsl/atm/0/35
Please provide the following: [q]uit.
vpi: -----------------------------> {0}: ** read-only **
vci: -----------------------------> {35}: ** read-only **
admin_status: --------------------> {down}: up
receive_traffic_descr_index: -----> {1}:
transmit_traffic_descr_index: ----> {1}:
vcc_aal_type: --------------------> {other}: ** read-only **
vcc_aal5_cpcs_transmit_sdu_size: -> {9188}:
vcc_aal5_cpcs_receive_sdu_size: --> {9188}:
vcc_aal5_encaps_type: ------------> {llcencapsulation}:
vcl_cast_type: -------------------> {p2p}:
vcl_conn_kind: -------------------> {pvc}:
fault-detection-type: ------------> {disabled}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

5 Re-enable the cross-connect after changes have been made:

zSH> update atm-cc 1
Please provide the following: [q]uit.
cc-index: ------> {1}: ** read-only **
low-if-index: --> {1-1-1-0-propvirtual/atm}: **
read-only **
low-vpi: -------> {0}: ** read-only **
low-vci: -------> {32}: ** read-only **
high-if-index: -> {1-8-1-0-adsl/atm}: ** read-only
**
high-vpi: ------> {0}: ** read-only **
high-vci: ------> {35}: ** read-only **
admin-status: --> {down}: up
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

MALC Configuration Guide 99

Configuring IP

Displaying hosts

Issue the host show command to display hosts, which displays the IP address
of the unnumbered interface used in the host route, interface of the host route,
VPI/VCI of the internal VCL used to create the host, the subnet group to
which the host belongs, whether the host is dynamically or statically assigned,
and if the host has been assigned an IP address.
zSH> host show
Rd/Address Interface Group T Host Address
--------------------------------------------------------------------------------
1 10.0.0.1 1-11-1-0-adsl-0-35 0/32 1 D <unassigned>
D <unassigned>
D <unassigned>
S 192.168.11.5
1 192.168.11.1 1-8-6-0-adsl-0-35 0/33 0 S 192.168.11.6
1 192.168.11.1 1-8-2-0-adsl-0-35 0/35 0 S 192.168.11.55

Displaying interfaces

Issue the interface show command to display interfaces:

zSH> interface show
Interface Status Rd/Address Media/Dest Address IfName
--------------------------------------------------------------------------------
1/1/1/0/ip UP 1 [10.0.0.1] 0/35 multipoint 1-5-1-0-adsl-0-35
--------------------------------------------------------------------------------

Brackets around IP addresses in the output of the interface show command

indicate unnumbered interfaces.

Displaying routing information

The following commands display routing information:

• route show
• rip show

Displaying the routing table

To display the routing table, use the route show command:
zSH> route show
Dest Nexthop Cost Owner
------------------------------------------------------------
0.0.0.0/0 172.24.200.254 1 STATICLOW
172.24.200.162/32 1 LOCAL
172.24.200.0/24 1/1/1/0/ip 1 LOCAL

100 MALC Configuration Guide

 IP administrative procedures

Displaying RIP information

To display Routing Information Protocol (RIP) information, use the rip show
command:
zSH> rip show
RIP Globals
----------------------------------------------------------
Route Route Route Admin Update
Domain Changes Queries State Time
----------------------------------------------------------
1 0 0 disabled 30
----------------------------------------------------------
RIP Interface Statistics
------------------------------------------------------
Recv Bad Recv Bad Updates
IfName Packets Routes Sent To
------------------------------------------------------
1-1-1-0 0 0 0
uplink1 0 0 0
1-8-1-0-adsl-0-35 0 0 0
1-8-6-0-adsl-0-35 0 0 0
1-8-8-0-adsl-0-35 0 0 0
1-8-3-0-adsl-0-35 0 0 0
RIP Interface Configuration
--------------------------------------------------------------------------------
Auth Auth Default Src
IfName Type Key Talk Listen Metric Address
Static Poison
--------------------------------------------------------------------------------
1-1-1-0 none (write-only) disabled disabled 0 172.24.20
0.162 none disabled
uplink1 none (write-only) disabled disabled 0 219.200.1
62.2 none disabled
1-8-1-0-adsl-0-35 none (write-only) disabled disabled 0 192.168.1
1.1 none disabled
1-8-6-0-adsl-0-35 none (write-only) disabled disabled 0 0.0.0.0
none disabled
1-8-8-0-adsl-0-35 none (write-only) disabled disabled 0 0.0.0.0
none disabled
1-8-3-0-adsl-0-35 none (write-only) disabled disabled 0 0.0.0.0
none disabled
RIP Peers
--------------------------------------------------------------------------------
Route IP Last Recv Bad Recv Bad
Domain Address Update Version Packets Routes
--------------------------------------------------------------------------------

Deleting hosts

Issue the host delete command to delete hosts:

zSH> host delete 1-11-1-0/adsl vc 0/35 all

MALC Configuration Guide 101

Configuring IP

Deleting interfaces

Issue the interface delete command to delete interfaces:

zSH> interface delete 1-5-1-0/adsl vc 0/35
Delete complete

Deleting routes

To delete static routes, use the route delete command. The command uses the
following syntax:
zSH> route delete destination mask next-hop

The following example deletes the network route to 192.178.21.0 using the
gateway 192.172.16.1:
zSH> route delete 192.178.21.0 255.255.255.0 192.178.16.1

DHCP logging

The MALC provides a logging facility to monitor the DHCP packets it sends
and receives. By default, DHCP messages are not displayed.

Enabling DHCP logging

1 Enable the DHCP server log messages:
zSH> log level dhcpserver info
Module: dhcpserver at level: info

2 Enable logging for the session:

zSH> log session on
Logging enabled.

As DHCP server messages are sent and received, they are displayed on
the console.

Note: This setting does not persist across system reboots. You
must re-enable DHCP logging after a MALC reboot.

3 These messages can be captured to a file using your terminal’s capture

facility, or sent to a syslog server. For example:
zSH> new syslog-destination 1
Please provide the following: [q]uit.
address: --> {0.0.0.0}: 192.200.42.5 syslog server IP address
port: -----> {514}:
facility: -> {local0}:
severity: -> {debug}:info
....................

102 MALC Configuration Guide

 IP administrative procedures

Save new record? [s]ave, [c]hange or [q]uit: s

New record saved.

Understanding DHCP server log messages

When a device sends a DHCP server request to the MALC, a message similar
to the following is logged:
AUG 13 12:20:48: info : 1/1/1084: dhcpserver:
DhcpServerTask: DHCPREQUEST for 155.57.1.21 from
00:b0:d0:98:92:3d via if496

This message indicates that a request for the address 155.57.1.21 was received
by the device with the MAC address 00:b0:d0:98:92:3d. The request came in
over the interface number 496.
To find what physical interface this corresponds to, use the ifxlate command:
zSH> ifxlate 496
ifIndex: ----------> {496}
shelf: ------------> {1}
slot: -------------> {10}
port: -------------> {48}
subport: ----------> {0}
type: -------------> {hdsl2}
adminstatus: ------> {up}
physical-flag: ----> {true}
iftype-extension: -> {none}
ifName: -----------> {1-10-48-0}

The MALC sends the following message when it acknowledges the DHCP
request packet.
AUG 13 12:20:48: info : 1/1/1084: dhcpserver:
DhcpServerTask: DHCPACK on 155.5 7.1.21 to
00:b0:d0:98:92:3d via if496

Viewing client leases

When the MALC issues a DHCP client lease, it creates a dhcp-server-lease.
You can view these records to see the status of the lease:
1 List the current leases:
zSH> list dhcp-server-lease
dhcp-server-lease 0/155/57/1/10
dhcp-server-lease 0/155/57/1/11
dhcp-server-lease 0/155/57/1/12
dhcp-server-lease 0/155/57/1/13
dhcp-server-lease 0/155/57/1/14
dhcp-server-lease 0/155/57/1/15
dhcp-server-lease 0/155/57/1/17
dhcp-server-lease 0/155/57/1/18
dhcp-server-lease 0/155/57/1/19
dhcp-server-lease 0/155/57/1/16

MALC Configuration Guide 103

Configuring IP

dhcp-server-lease 0/155/57/1/20
dhcp-server-lease 0/155/57/1/21
dhcp-server-lease 0/155/57/1/22
dhcp-server-lease 0/155/57/1/23
14 entries found.

2 To view an individual record:

zSH> get dhcp-server-lease 0/155/57/1/10
starts: ------------> {1060700857}
ends: --------------> {1060700917}
flags: -------------> {0}
hardware-address: --> {00:00:c5:90:3b:08}
client-identifier: -> {}
client-hostname: ---> {}
hostname: ----------> {}
dns-fwd-name: ------> {}
dns-rev-name: ------> {}

Note that 0/155/57/1/10 represents routing domain 0, and the IP address

155.57.1.10.

104 MALC Configuration Guide

5
BRIDGING

This chapter explains how to configure bridging on the MALC. It includes the
following sections:
• Overview, page 105
• Broadcasts and bridging, page 106
• VLANs, page 107
• Untagged bridging, page 110
• Ethernet RPR, page 112
• Linear GigaBit Ethernet, page 126
• Advanced bridging configurations, page 131
• Administrative commands, page 135

Overview
Bridging involves configuring the MALC to direct traffic based on Ethernet
MAC addresses.
The MALC supports the two types of bridges:
• Tagged bridging
Tagged or Virtual LANs (VLANs) bridging, which forwards traffic based
on MAC addresses and allows the segregation of a single Ethernet
network into multiple virtual network segments by mapping ATM VCLS
to VLAN IDs.
• Untagged bridging
Untagged or transparent bridging which forwards traffic based on MAC
addresses but does not provide segregation of traffic. Traffic is broadcast
over the Ethernet port and is either accepted or rejected based on the
destination MAC address.

MALC Configuration Guide 105

Bridging

• Intralink bridging
Intralink bridging forwards traffic with unknown MAC addresses to the
configured bridge interface without attempting to learn the addresses of
the attached devices or network. Incoming broadcast or multicast traffic
received on an uplink is forwarded to all intralinks. If the intralinks are
designated with VLAN IDs, the traffic is forwarded to the appropriate
interface. Unicast packets that can not be resolved locally are also
forwarded on all intralinks.
A global intralink can also be defined, which receives all traffic that
cannot be resolved locally.
The bridged uplink traffic can then be transmitted and received using either
Ethernet (for tagged VLANs) or ATM (for untagged transparent traffic).
Bridges on the downlink and uplink interfaces are configured using the
bridge add command. This command assigns the bridge-interface-record
profile to the specified interface.To facilitate bridge setup, the MALC sets the
default values for this profile based on the usage of the downlink and uplink
command parameters. For VLAN bridges, use the downlink and uplink
parameters to create bridges on the interfaces with the default downlink and
uplink bridge settings. For transparent bridges, the downlink and uplink
parameter is omitted to create bridges on the interfaces with default
transparent bridge settings.

Note: The MALC ports can support both IP termination or bridging

on different virtual circuits. However, each virtual circuit must be
configured for either IP termination or bridging and cannot support
both at the same time.

Note: When routed and bridged traffic is configured for the same
uplink interface, VLAN tags must be used between both downlink
ports and the uplink interface for traffic differentiation. For routed
traffic, use the ip-interface-record profile to specify the VLAN ID.

Broadcasts and bridging

The MALC supports a modified form of broadcast suppression when
configured for bridge mode. The MALC configures ports as either uplinks or
downlinks. Uplink ports are those that connect to upstream devices, while
downlinks connect to subscribers.
In general, broadcasts sent from a downlink will traverse the uplink, but will
not be sent down other downlinks, even within the same VLAN. This
prevents subscribers from maliciously or unintentionally sending or receiving
broadcasts between ports on the same system.
Ports configured as uplinks will send broadcasts upstream, but by default will
not propagate broadcasts sent from the upstream down to the MALC. The
filterBroadcast parameter in the bridge-interface-record profile enables this

106 MALC Configuration Guide

 VLANs

filtering. This mechanism provides security benefits, as well as reducing

unnecessary traffic on low bandwidth interfaces.
One exception to the operational mode described above is ARP broadcast
support. When a MALC receives a broadcast frame, it is checked to determine
if it is an ARP protocol packet or not. If it is not, it is treated as above. If it is,
then the MALC compares and filters the requested IP address with the current
forwarding table. If a match is found, the ARP broadcast is forwarded out the
interface that has the appropriate host. This host will then reply to the ARP
with a standard response. If a match is not found, then the ARP is filtered and
it gets dropped as if it were a non-ARP broadcast. This setting is controlled by
the customARP parameter.
Another exception to this broadcast filtering is DCHP broadcast support.
When a MALC receives a broadcast DCHP OFFER message from a remote
DHCP server, if customDCHP is set to true, the broadcast messages are
forwarded to the source MAC address. Otherwise, the broadcast DHCP
messages are filtered.

VLANs
Figure 13 shows a typical VLAN configuration. On the access (subscriber)
side, VLANs 1 and 2 are separate DSL networks connected to the MALC via
Z-Edge devices. On the uplink side, VLANs 1 and 2 are on the same physical
Ethernet interface, but the traffic is separated based on the VLAN IDs.
The side of the connection closest to the subscriber is called the downlink
interface. The upstream egress is called the uplink interface. When the MALC
is in VLAN mode, it adds (tags) the VLAN ID to the Ethernet frame on the
uplink interface and strips (untags) the ID out on the downlink interface.
Although VLAN IDs are not typically required on downlink interfaces, you
can configure downlink interface as tagged. Tagged downlink interfaces can
be used for subtended MALCs or subscribers expecting tagged traffic with
Transparent LAN Server (TLS) service.

Note: The MALC supports VLAN IDs from 1 to 4096.

MALC Configuration Guide 107

Bridging

Figure 13: Example VLAN network

VLAN 1

VLAN 1

VLAN 2 VLAN 2
Downlink Uplink

Untagged Tagged

You can configure static VLAN bridge paths, which requires that you enter a
MAC address for every bridge on the Ethernet. Or, you can set up the MALC
Ethernet interface to learn the VLAN IDs when it receives a packet from a
downlink device.
Note that if the MALC receives a packet from an uplink interface before it has
learned the VLAN ID or MAC address, it will not deliver the packet.

Figure 14: Learning a VLAN ID

Packet for VLAN 2

Packet for VLAN 2 (Ethernet broadcast) VLAN 1
1 2

VLAN 2

VLAN 2 response
System learns VLAN 2
MAC address 3 VLAN 2

Configuring a VLAN bridge

To configure a VLAN bridge:

108 MALC Configuration Guide

 VLANs

1 Use the bridge add command to add a bridge for the downstream
connection:
zSH> bridge add 1-8-1-0/adsl vc 0/35 td 1 downlink vlan 555

This example adds a downlink VLAN interface to the ADSL modem in

shelf 1, slot 8, port 1 with a VLAN ID of 555. It uses the VCL 0/35 and
traffic descriptor 1 as a transport, sets the parameters to the downlink
settings, and assigns port VLAN ID 555.
The following bridge-interface-record is created with the downlink
default settings and shows the internal VPI/VCI cross connects. It is
recommended not to change the default settings unless advanced bridge
configuration is required.
zSH> get bridge-interface-record 1-8-1-0-adsl-0-35/bridge
vpi: ----------------------> {0}
vci: ----------------------> {53}
vlanId: -------------------> {555}
stripAndInsert: -----------> {true}
customARP: ----------------> {false}
filterBroadcast: ----------> {false}
learnIp: ------------------> {true}
learnUnicast: -------------> {true}
maxUnicast: ---------------> {5}
learnMulticast: -----------> {true}
forwardToUnicast: ---------> {false}
forwardToMulticast: -------> {false}
forwardToDefault: ---------> {true}
bridgeIfCustomDHCP: -------> {false}
bridgeIfConfigGroupIndex: -> {0}

2 Use the bridge add command to add a VLAN interface to the upstream
Ethernet interface:
zSH> bridge add 1-1-1-0/ethernetcsmacd uplink
This command adds a learning bridge that accepts VLAN traffic and
enables VLAN trunking on the MALC unit’s egress Ethernet port.
3 Configure the uplink interface to learn the VLAN IDs of all ingress
Ethernet devices or a specific VLAN ID:
zSH> bridge-path add ethernet1/bridge global
The global setting specifies that the MALC should send all VLAN traffic
to this port. A VLAN ID can also be used when the MALC should send
only traffic from a specific VLAN ID to this port. (The ethernet1
interface is the first Ethernet interface on the MALC.) It is recommended
not to change the default settings unless advanced bridge configuration is
required.
zSH> get bridge-interface-record ethernet1/bridge
vpi: ----------------------> {0}
vci: ----------------------> {0}
vlanId: -------------------> {0}

MALC Configuration Guide 109

Bridging

stripAndInsert: -----------> {false}

customARP: ----------------> {true}
filterBroadcast: ----------> {true}
learnIp: ------------------> {false}
learnUnicast: -------------> {false}
maxUnicast: ---------------> {0}
learnMulticast: -----------> {false}
forwardToUnicast: ---------> {true}
forwardToMulticast: -------> {true}
forwardToDefault: ---------> {false}
bridgeIfCustomDHCP: -------> {false}
bridgeIfConfigGroupIndex: -> {0}

4 Verify connectivity by pinging a far end device on the VLAN.

Untagged bridging
Configuring untagged or transparent bridging enables you to forward traffic
from a downlink interface through the MALC uplink interface based on the
destination MAC address without tagging or modification to the frame.

Configuring an untagged bridge

To add an untagged bridge:
1 Add an untagged bridge to the downstream DSL interface:
zSH> bridge add 1-8-2-0/adsl vc 0/101 td 1
Created bridge-interface-record 1-8-2-0-adsl-0-101/bridge

This example adds a default transparent bridge interface to the ADSL

modem in shelf 1, slot 8, port 2. It uses the VCL 0/101 and traffic
descriptor 1 as a transport and sets the parameters to the default
transparent bridge interface settings.
The following examples shows the default bridge-interface-record
settings with the internal vpi/vci cross connects. It is recommended not to
change the default settings unless advanced bridge configuration is
required.
zSH> get bridge-interface-record 1-8-1-0-adsl-0-35/bridge
vpi: ----------------------> {0}
vci: ----------------------> {53}
vlanId: -------------------> {0}
stripAndInsert: -----------> {true}
customARP: ----------------> {false}
filterBroadcast: ----------> {true}
learnIp: ------------------> {true}
learnUnicast: -------------> {true}
maxUnicast: ---------------> {5}
learnMulticast: -----------> {true}
forwardToUnicast: ---------> {false}
forwardToMulticast: -------> {false}

110 MALC Configuration Guide

 Untagged bridging

forwardToDefault: ---------> {true}

bridgeIfCustomDHCP: -------> {false}
bridgeIfConfigGroupIndex: -> {0}

2 Add a transparent bridge to the upstream Ethernet interface:

zSH> bridge add 1-1-1-0/ethernetcsmacd
Created bridge-interface-record 1-1-1-0-ethernetcsmacd/bridge

This command adds a bridge that accepts transparent/untagged traffic on

the MALC units’s egress Ethernet port.
The following shows the default transparent bridge-interface-record
settings for the uplink. It is recommended not to change the default
settings unless advanced bridge configuration is required.
zSH> get bridge-interface-record ethernet1/bridge
vpi: ----------------------> {0}
vci: ----------------------> {0}
vlanId: -------------------> {0}
stripAndInsert: -----------> {false}
customARP: ----------------> {true}
filterBroadcast: ----------> {true}
learnIp: ------------------> {false}
learnUnicast: -------------> {false}
maxUnicast: ---------------> {0}
learnMulticast: -----------> {false}
forwardToUnicast: ---------> {true}
forwardToMulticast: -------> {true}
forwardToDefault: ---------> {false}
bridgeIfCustomDHCP: -------> {false}
bridgeIfConfigGroupIndex: -> {0}

3 Verify that both sides of the bridge are present:

zSH> bridge show
VLAN Bridge State Table Data
-----------------------------------------------------------------
0 1-8-2-0-adsl-0-101/bridge UP
0 1-1-1-0-ethernetcsmacd/bridge UP

4 Test the bridge by pinging a device on the far end network and verifying e
that the bridge table is updated:
zSH> bridge show
VLAN Bridge State Table Data
-----------------------------------------------------------------
0 1-8-2-0-adsl-0-101/bridge UP D 00:01:47:cf:ae:04
0 1-1-1-0-ethernetcsmacd/bridge UP D 00:01:02:70:03:a2

MALC Configuration Guide 111

Bridging

Ethernet RPR
Ethernet Resilient Packet Ring (RPR) provides redundant Ethernet links
between MALC RPR nodes and an IP or outside network. Following the
IEEE 802.17 standard, Ethernet packets are inserted, stripped, and forwarded
between the RPR Uplink and ring nodes to create a resilient architecture with
high bandwidth utilization and less than 50ms protection switching.

Overview

An RPR configuration consists of an MALC RPR Uplink node that serves as

a gateway between the RPR ring and the Internet or outside network, and a
number of RPR ring nodes that process traffic between themselves and the
Uplink node. A dual counter-rotating ring is used so traffic can be transmitted
and received in both ring directions.
The RPR Uplink node must have two 2-port GigE Uplink cards connected
with a redundant RPR cable. Each ring node requires one 2-port GigE card
with an optional GigE card added for redundancy.

Note: See the MALC Hardware Installation Guide for more details
about adding redundant GigE-2 cards to the MALC.

The 2-port GigE card utilizes Small Form-factor Pluggable (SFPs) for flexible
deployment over fiber or copper media for data-only or integrated voice,
video, and data connections. SFP modules with the following Gigabit
Interface Convertors (GBICs) are available for a variety of transmission
choices:
• SX for 850nm with multimode fiber (MMF)
• LX for 1310nm with singlemode fiber (SMF)
• ZX for 1550nm with singlemode fiber (SMF)
• 1000B-T for copper cable
See the MALC Hardware Installation Guide for more details about the
supported SFPs.
RPR can be deployed in a variety of topologies including ring, collapsed ring,
star, linear and redundant card configurations. This section uses a basic
3-node ring topology as an example topology to demonstrate node
functionality and port connections.

RPR ring topology

In a basic RPR ring topology, MALC GigE cards are connected around the
ring in the east direction so that port 1-1-2-0/ethernetcsmacd on the active
RPR Uplink node connects to the port 1-1-3-0/ethernetcsmacd on the adjacent
ring node. On the redundant Uplink card, port 1-1-2-0/ethernetcsmacd

112 MALC Configuration Guide

 Ethernet RPR

connects in the west direction to the 1-1-2-0/ethernetcsmacd port on the

adjacent ring node.
Traffic to the IP or outside network goes through the primary RPR Uplink
node on active card port 1-1-3-0/ethernetcsmacd and redundant card port
1-2-3-0/ethernetcsmacd. A redundant cable connects RDNT ports between
the Uplink node’s redundant RPR GigE cards.
Neighbor RPR ring nodes connect in the east direction through port 1-1-3-0/
ethernetcsmacd to port 1-1-2-0/ethernetcsmad.
Figure 15 illustrates a 3 node RPR configuration and port connections.

Note: Because the MALC RPR ring uses dual counter-rotating rings,
each connecting line in this figure represents two actual fibers. Each
fiber transports send and receive traffic in a different direction around
the ring.
Interface 1-1-1-0 is assigned to the 10/100 Ethernet physical
interface. Interface 1-1-2-0 is assigned to physical port 1. Interface
1-1-3-0 is assigned to physical port 2.

MALC Configuration Guide 113

Bridging

Figure 15: RPR configuration

RPR uplink node

IP
or
Ethernet

RPR redundant
uplinks

RPR redundant cable

RDNT RDNT
1-1-2-0 1-2-2-0

1-1-3-0

1-2-3-0

RPR ring

1-1-2-0 1-1-2-0
1-1-3-0 1-1-3-0

RPR ring node RPR ring node

RPR ring topology with redundant GigE cards

Redundant GigE cards can also be used at each ring node to add an additional
level of equipment protection. Redundant cables connect RDNT ports
between the RPR ring nodes’ redundant GigE cards.
In this configuration, a different port connection strategy is used so that on the
RPR Uplink node the active card port 1-1-2-0/ethernetcsmacd connects in the
west direction to the adjacent RPR ring node port 1-1-2-0/ethernetcsmacd. On
the RPR Uplink node, the redundant card port 1-1-2-0/ethernetcsmacd
connects in the east direction to the adjacent RPR ring node port 1-1-2-0/
ethernetcsmacd. The neighbor RPR ring nodes connect through 1-1-2-0/
ethernetcsmacd ports, with 1-1-3-0/ethernetcsmacd ports reserved for
connections to subtended devices.
Traffic to the IP or outside network goes through the primary RPR Uplink
node on active card port 1-1-3-0/ethernetcsmacd and redundant card port

114 MALC Configuration Guide

 Ethernet RPR

1-2-3-0/ethernetcsmacd. An RPR redundant cable connects RDNT ports

between the Uplink node’s redundant RPR cards.
Figure 16 illustrates a basic RPR configuration with redundant cards on the
ring nodes.

Note: Because the MALC RPR ring uses dual counter-rotating rings,
each connecting line in this figure represents two actual fibers. Each
fiber transports send and receive traffic in a different direction around
the ring.
Interface 1-1-1-0 is assigned to the 10/100 Ethernet physical
interface. Interface 1-1-2-0 is assigned to physical port 1. Interface
1-1-3-0 is assigned to physical port 2.

Figure 16: RPR configuration with redundant ring nodes

Uplink node

IP or Ethernet

RPR redundant
uplinks

RPR redundant cable

1-1-2-0 1-2-2-0

1-1-3-0

1-2-3-0

RPR ring
with equipment
redundancy at each
RPR ring node

1-1-2-0 1-2-2-0 1-1-2-0 1-2-2-0

RPR ring node RPR ring node

MALC Configuration Guide 115

Bridging

RPR ring topology with redundant GigE cards and

subtended MALCs
In this configuration, the same port connection strategy is used as for
redundant card configuration so that on the RPR Uplink node the active card
port 1-1-2-0/ethernetcsmacd connects in the west direction to the adjacent
RPR ring node port 1-1-2-0/ethernetcsmacd. On the RPR uplink node, the
redundant card port 1-1-2-0/ethernetcsmacd connects in the east direction to
the adjacent RPR ring node port 1-1-2-0/ethernetcsmacd. The neighbor RPR
ring nodes connect through 1-1-2-0/ethernetcsmacd ports, with 1-1-3-0/
ethernetcsmacd ports reserved for connections to subtended devices.
Traffic to the IP or outside network goes through the primary RPR Uplink
node on active card port 1-1-3-0/ethernetcsmacd and redundant card port
1-2-3-0/ethernetcsmacd. An RPR redundant cable connects RDNT ports
between the Uplink node’s redundant RPR cards.
Figure 17 illustrates a basic RPR configuration with redundant cards on the
ring nodes and subtended MALCs.

Note: Because the MALC RPR ring uses dual counter-rotating rings,
each connecting line in this figure represents two actual fibers. Each
fiber transports send and receive traffic in a different direction around
the ring.
Interface 1-1-1-0 is assigned to the 10/100 Ethernet physical
interface. Interface 1-1-2-0 is assigned to physical port 1. Interface
1-1-3-0 is assigned to physical port 2.

116 MALC Configuration Guide

 Ethernet RPR

Figure 17: RPR configuration with redundant ring nodes and subtended MALC
Uplink node

IP or Ethernet

RPR redundant
uplinks

RPR redundant cable

1-1-2-0 1-2-2-0

1-1-3-0

1-2-3-0

RPR ring
with equipment
redundancy at each
RPR node and
subtended Ethernet
devices

1-1-2-0 1-2-2-0 1-1-2-0 1-2-2-0

1-1-3-0 1-2-3-0 1-1-3-0 1-2-3-0

RPR ring node RPR ring node

Subtended Ethernet Device Subtended Ethernet Device

RPR configuration

RPR basic configuration involves configuring the primary Uplink node with 2
GigE Uplink cards and then configuring each RPR ring node with a single
GigE Uplink card. Redundant GigE Uplink cards can also be added to RPR
ring nodes for additional card protection.
This section contains the following procedures:
• Configuring RPR protection switching on page 118
• Displaying RPR configuration on page 119

MALC Configuration Guide 117

Bridging

• Displaying RPR topology on page 120

• Displaying RPR status on page 122
• Displaying RPR statistics on page 123

Configuring RPR protection switching

MALC RPR configurations support less than 50ms protection switching for
fiber breaks or ring failures in the RPR ring.
RPR nodes support a Wrap protection strategy. This protection strategy
determines the timing and type of protection that is used when a span fault
occurs. When Wrap is configured as false (the default setting) and a ring
protection event occurs, the RPR node does not send traffic in the direction of
the ring failure. Instead, traffic is steered or redirected to the destination in the
opposite direction of the ring failure.
When Wrap is configured as true, the RPR node sends traffic out to the
destination even if it is in the direction of a ring failure. When the failure is
encountered, traffic wraps or returns in the other direction back through the
sending node to the destination.
The Wrap false setting offers lower packet latency as packets do not have to
travel to the ring failure and then traverse the ring in the opposite direction to
get to the destination. However, with this setting more packet loss may occur
as packets sent in the direction of a ring failure may be lost. The Wrap true
setting helps prevent packet loss, but increases packet latency as packets sent
in the direction of a ring failure are rerouted back to the destination in the
opposite direction.
Other protection switching options include:
• reversion mode
The reversion mode determines if traffic resumes processing in the
normal direction after a protection event is cleared.
• wait-to-restore (wtr) time
The wtr time determines how long the node waits after a protection event
is cleared before traffic processing reverts back to the normal direction.
• fast timer
This timer indicates how often in milliseconds the node sends out ‘fast’
status messages when a protection event occurs.
• slow timer
This timer indicates how often the node sends out ‘slow’ status messages
when a protection event occurs. This value is in 50 millisecond (ms)
intervals. For example, a value of 100 equals 5 seconds.
To change the protection switching options, update the rpr-config profile.
zSH> update rpr-config 1-1-2-0/ethernetcsmacd
Please provide the following: [q]uit.

118 MALC Configuration Guide

 Ethernet RPR

reversion-mode: --------> {true}:

protection-wtr: --------> {10}: 20
protection-fast-timer: -> {10}:
protection-slow-timer: -> {100}:
wrap-config: -----------> {false}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

Displaying RPR configuration

The MALC rpr show config command displays information about the
current RPR node configuration.
zSH> rpr show config
sysObject= 0x66bc578, systemId= 0, pParent= 0x7de9ba0, ethDrvNum= 0
rprStarted= 1, bridgeExists= 1
npRprContext= 0x100 (BrgExst,Steer,)
rprCtrlSema4= 0x492a740, taskIdSema4= 0x0, lastTaskIdSema4= 0x66b06e8
rprStationSema4= 0x4b43fd0, taskIdStationSema4= 0x0,
lastTaskIdStationSema4= 0x66b06e8
NpGigePacketWrap= 4/5, unitPhy= 0/1, outMacPort= 1/0
Encoding= 0xf810/0xf811, rxRegistered= 1/1
txSlowTimeout= 100ms, txFastTimeout= 10ms, ticksPer100ms= 10
atdTimerTimeout= 1000ms, lastAtdSentTime= 2687770
topoChanged= 0, protectChanged= 0
containmentActive= 0, containmentStart= 1055191, containmentDuration= 60ms

containmentCnt= 6, containmentTotal= 13310ms

newNeighbor= 0/0, revertive= 1, tossWrongRingletIDs= 0
lrttActive= 1, lrttComplete= 1, lrttContextId= 7
lrttTime= 1055197, lrttDuration= 210ms, lrttIncompletionTimeout= 1000ms
tvState= tvValid, tvTopoCheck= 3, stabilityTime= 1055192, instabilityTime=
1055191
stabilityTO= 40ms, instabilityTO= 10000ms
topologyValid= 1, topologyStable= 1, topologyUnstableTime= 1055191,
topologyUnstableDuration= 60ms
adminReqProtection= ???/???, spanProtAdmin= IDL/IDL
spanOperStatus= IDL/IDL, linkErrCode= UP
needSecondaryMacValidation= 1, cleavePt= 1/1
notifyCleavePtChange= 0/0, notifyTopoChange= 0/0
WTR[0]: time= 10541840, timeout= 10000ms, enabled= 1
WTR[1]: time= 237920, timeout= 10000ms, enabled= 1
tcState= tcReturn, puState= puReturn, ptpState= ptpReturn
Defect: miscabling= 0/0, Start= 0/0, Duration= 0ms/0ms
protMisconfig= 0, Start= 0, Duration= 0ms
topoEntryInvalid= 0, Start= 1054951, Duration= 60ms
maxStations= 0, Start= 0, Duration= 0ms
topoInconsist= 0, Start= 1042700, Duration= 340ms
topoInstab= 0, Start= 0, Duration= 0ms
nextLogId= 209, totalLogEntrys= 209
current time = 2687864 ticks (26878640ms)

MALC Configuration Guide 119

Bridging

Displaying RPR topology

MALC RPR topology displays information about an RPR ring for ring
diagnostics and management. From an RPR node’s perspective, other nodes
to in the west direction or left of the current node are on ringlet 0. Nodes in the
east direction or right of the current node are on ringlet 1. The number of hops
between nodes is determined by counting the number of nodes in a specified
ringlet or direction. The current node is always at hop 0.
This illustration shows an example 3-node topology.

RPR uplink node A

IP
or
Ethernet

RPR redundant
uplinks

RPR redundant cable

RDNT RDNT
1-1-2-0 1-2-2-0

1-1-3-0

1-2-3-0

RPR ring

1-1-2-0 1-1-2-0
1-1-3-0 1-1-3-0

RPR ring node B RPR ring node C

Ringlet 0 or Ringlet 1 or
West direction East direction

Using ring node B as the current node, ringlet 0 (zero) is in the west direction
or left. From node B, traffic on ringlet 0 travels to node A, to node C and back
to node B. In ringlet 0, node A is one hop from node B, while node C is two
hops away.
Ringlet 1 is in east direction or right. From node B, traffic on ringlet 1 travels
to node C, to node A and back to node B. In ringlet 1, node C is one hop from
node B, while node A is two hops away.

120 MALC Configuration Guide

 Ethernet RPR

Use the rpr show topo command to display topology, statistics,

configuration, and status information.
zSH> rpr show topo
total number of ring nodes= 3 (ringlet 0= 2, ringlet 1= 2)
ring protection= STEERING, ring topology= CLOSED ring
containment= NOT active, topology valid= true
link status: west(PSW)= Signal OK (IDL), east(PSE)= Signal OK (IDL)
R=reachable; WE=west/east edge state; PSW/PSE=west/east protect state
ring hop R WE PSW PSE -------MAC------- ------IP-------
0 3 t ff IDL IDL 00:01:47:5a:aa:2a 192.168.50.142
0 2 t ff IDL IDL 00:01:47:5a:aa:22 192.168.50.146
0 1 t ff IDL IDL 00:01:47:5a:aa:1a 192.168.50.144
**** 0 t ff IDL IDL 00:01:47:5a:aa:2a 192.168.50.142
1 1 t ff IDL IDL 00:01:47:5a:aa:22 192.168.50.146
1 2 t ff IDL IDL 00:01:47:5a:aa:1a 192.168.50.144
1 3 t ff IDL IDL 00:01:47:5a:aa:2a 192.168.50.142

This example topology uses node B as the current node. There are a total
of 3 nodes in the ring, the current node and 2 nodes in each ringlet. Ring
protection is set to Steering (Wrap=false). There are no protection events
so the ring is closed and containment is not active. Containment causes
data packets that are not strictly ordered to be discarded when a topology
change or protection event occurs. The current topology is valid. Causes
of invalid topology include miscabling, malfunctioning links, and other
connectivity issues.
For each node in the ring, the topology displays the following data:

Field Description
ring 0 indicates ringlet 0 and the east direction around ring.
1 indicates ringlet 1 and the west direction around ring.
**** indicates the current node.
hop Number of hops upstream and downstream from the current
node. The current node is always displayed with a hop count of
0. To validate the passing of traffic through the complete ring
and back to the current node, the current node also appears at
the last hop in both ringlets.
R Reachable. t indicates the connection to the node is valid and
reachable. f indicates the connection to the node is not valid and
is unreachable.
WE West and east span fault status. An edge indicates a span fault
occurred. t indicates an edge exists and the edge status is true. f
indicates an edge does not exist and the edge status is false.

MALC Configuration Guide 121

Bridging

Field Description
PSW/PSE The protection state on the west (PSW) and east (PSE) span.
Values:
IDL: Protection status is idle, signal OK. Link is up with
neighbor.
WTR: Wait-to-restore. The span has recovered from a fault but
it’s been configured to wait a period of time before restoring the
card’s connection. The wait-to-restore time is configured in the
protection-wtr parameter in the rpr-config profile.
MS: User has requested the span to deactivate. Not supported.
SD: Signal degraded. Not supported.
SF: Signal failure. Link is down with neighbor.
FS: User has forced span to deactivate. Not supported.
MAC The MAC address of the node.
IP IP address of the node. If the node has multiple IP interfaces on
the RPR port, the interface associated with the lowest VLAN ID
is displayed.

Displaying RPR status

The MALC rpr show status command displays status information about
the RPR ring for ring diagnostics and management.
zSH> rpr show status
sysObject= 0x66bc578, systemId= 0, pParent= 0x7de9ba0, ethDrvNum= 0
rprStarted= 1, bridgeExists= 1
npRprContext= 0x100 (BrgExst,Steer,)
rprCtrlSema4= 0x492a740, taskIdSema4= 0x0, lastTaskIdSema4= 0x4984b60
rprStationSema4= 0x4b43fd0, taskIdStationSema4= 0x0,
lastTaskIdStationSema4= 0x66b06e8
NpGigePacketWrap= 4/5, unitPhy= 0/1, outMacPort= 1/0
Encoding= 0xf810/0xf811, rxRegistered= 1/1
txSlowTimeout= 100ms, txFastTimeout= 10ms, ticksPer100ms= 10
atdTimerTimeout= 1000ms, lastAtdSentTime= 2752070
topoChanged= 0, protectChanged= 0
containmentActive= 0, containmentStart= 1055191, containmentDuration= 60ms
containmentCnt= 6, containmentTotal= 13310ms
newNeighbor= 0/0, revertive= 1, tossWrongRingletIDs= 0
lrttActive= 1, lrttComplete= 1, lrttContextId= 7
lrttTime= 1055197, lrttDuration= 210ms, lrttIncompletionTimeout= 1000ms
tvState= tvValid, tvTopoCheck= 3, stabilityTime= 1055192, instabilityTime=
1055191
stabilityTO= 40ms, instabilityTO= 10000ms
topologyValid= 1, topologyStable= 1, topologyUnstableTime= 1055191,
topologyUnstableDuration= 60ms
adminReqProtection= ???/???, spanProtAdmin= IDL/IDL
spanOperStatus= IDL/IDL, linkErrCode= UP
needSecondaryMacValidation= 1, cleavePt= 1/1
notifyCleavePtChange= 0/0, notifyTopoChange= 0/0
WTR[0]: time= 10541840, timeout= 10000ms, enabled= 1

122 MALC Configuration Guide

 Ethernet RPR

WTR[1]: time= 237920, timeout= 10000ms, enabled= 1

tcState= tcReturn, puState= puReturn, ptpState= ptpReturn
Defect: miscabling= 0/0, Start= 0/0, Duration= 0ms/0ms
protMisconfig= 0, Start= 0, Duration= 0ms
topoEntryInvalid= 0, Start= 1054951, Duration= 60ms
maxStations= 0, Start= 0, Duration= 0ms
topoInconsist= 0, Start= 1042700, Duration= 340ms
topoInstab= 0, Start= 0, Duration= 0ms
nextLogId= 209, totalLogEntrys= 209
current time = 2752107 ticks (27521070ms)

Displaying RPR statistics

The MALC rpr show stats command displays data about the RPR ring
performance for ring diagnostics and management.
This example shows statistics for an example 3-node topology. Using node B
as the current node, nodes A and B to the west or left are in ringlet 0 while
nodes B and A to the east or right are in Ringlet 1.
The rpr show stats optional argument clear will clear the statistics. The
noclr argument (the default) preserves the current statistics.
zSH> rpr show stats

TX: Requests= 108050, Ok= 108049, BadSrcMac= 0, Switch2Bridge= 0

Data: ip= 281, ucst= 41, bcst= 240, bridge= 107768, ec_so= 26
DstUnreachable= 0, Data_containment= 1
CtLrttReq: ok= 12, fail= 0
CtLrttRsp: ok= 12, fail= 0
CtTC: ok= 255833, fast= 35, fail= 0, triggers= 15
CtTP: ok= 255863, fast= 68, fail= 0, triggers= 17
CtATD: ok= 25554, fail= 0, nodata= 27
RX: Data: total= 263, bf= 263, ef= 0, containment= 0, ec_so= 25
Ct_badType= 0, Ct_badVersion= 0
CtTP: total= 1528081, ignore= 0, ignoreOthers= 0, suspect= 0
CtTP_redundant[ hop=1 ]: 254547, 255720
CtTP_redundant[ hop=2 ]: 254443, 254464
CtTP_redundant[ hop=3 ]: 254444, 254442
CtTC: total= 510161, bad= 0
CtLrttReq: total= 20, ignore= 8
CtATD: total= 101885, ignore= 0, dup= 0, badType= 0, badLen= 0
CtLrttRsp: total= 12, ignore= 0, exceed= 0, bad= 0
lrtt_starts= 7, lrtt_fails= 0, lrtt_stops= 6, lrtt_multiple= 0
contextChgs= 17, cleavePtChgs= 4/3, topoChgs= 4/5
linkChgs= 4/2, linkChgNotifies= 3
CDT: Add= 5, Add2= 6, Del= 2, Del2=3
Switches= 0, SwitchTreeHops1/2/3= 0/4/0
MacChgs= 0, Unexp1/2/3/4/5/6= 0/0/0/0/0/0
zSH>

MALC Configuration Guide 123

Bridging

Adding bridges to RPR ring

Bridges can be configured in a RPR ring so bridged subscriber traffic can be
transported across the ring and connected to the destination IP or outside
network.
The illustration below shows the bridge configurations in a 3-node RPR ring:
• Uplink node
The RPR Uplink node contains a bridge uplink and global bridge-path on
the GigE card’s second port (1-1-3-0) to direct all bridged traffic to the
outside or IP network. This node also contains a global-intralink on the
GigE card’s first port (1-1-2-0) so unknown traffic is sent to the ring, even
though address learning is not enabled.
• Ring node
This RPR ring node contains a bridge uplink on the GigE card’s second
port (1-1-3-0) to direct all outgoing bridged traffic to the RPR Uplink
node. This node also contains a bridge downlink on the ADSL card
1-1-5-0 so VLAN tags can be stripped and inserted for subscriber VLAN
participation.
• Ring node
This RPR ring node contains a bridge uplink on the GigE card’s second
port (1-1-3-0) to direct all outgoing bridged traffic to the RPR Uplink
node. This node also contains a bridge intralink to a subtended MALC. A
bridge intralink is used in place of a bridge downlink so unknown packets
are forwarded to subscribers without the need to learn all downlink
subscriber MAC addresses.

Note: If a subtended device is configured to request DHCP services

from a DHCP server through the IP or outside network, ensure that
the CustomDHCP setting is set to true in the bridge-interface-records
on the RPR Uplink node and ring node.

124 MALC Configuration Guide

 Ethernet RPR

IP

bridge uplink
bridge add 1-1-3-0/ethernetcsmacd uplink
bridge-path add ethernet3/bridge global

Intralink
bridge add 1-1-2-0/ethernetcsmacd intralink
bridge-path add ethernet2/bridge global-intralink

bridge uplink bridge uplink

bridge add 1-1-2-0/ethernetcsmacd uplink bridge add 1-1-2-0/ethernetcsmacd uplink
bridge-path add ethernet2/bridge global bridge-path add ethernet2/bridge global

bridge downlink
Intralink
bridge add 1-5-1/adsl vc 0/37
bridge add 1-1-2-0/ethernetcsmacd intralink
td 4000 downlink vlan 100 untagged
bridge-path add ethernet2/bridge global-intralink

To configure bridges in an RPR ring:

1 On the Uplink node
a Add a bridge interface to the second GigE port (this is the port
connected to the external network):
zSH> bridge add 1-1-3-0/ethernetcsmacd uplink

MALC Configuration Guide 125

Bridging

b Add a default bridge path for the ring over the second GigE port:
zSH> bridge-path add ethernet3/bridge global
All bridge traffic will be forwarded over this interface.
c Add an bridge intralink on the first GigE port:
zSH> bridge add 1-1-2-0/ethernetcsmacd intralink
zSH> bridge-path add ethernet2/bridge
global-intralink
Unlearned traffic received on this interface is forwarded to the
external network.
d Add a global bridge intralink path:
zSH> bridge-path add ethernet2/bridge
global-intralink
This interface is the global intralink for the ring.
2 On the RPR ring node to which subscribers are connected:
a Add an uplink bridged interface:
zSH> bridge add 1-1-2-0/ethernetcsmacd uplink
b Add a default bridge path that points to the Uplink node:
zSH> bridge-path add ethernet2/bridge global
c Add a downlink to the remote subscriber:
zSH> bridge add 1-5-1-0/adsl vc 0/37 td 4000
downlink vlan 100 untagged
3 On the RPR ring node to which a subtended MALC is connected:
a Add an uplink bridged interface:
zSH> bridge add 1-1-2-0/ethernetcsmacd uplink
b Add a default bridge path that points to the Uplink node:
zSH> bridge-path add ethernet2/bridge global
c Add an intralink to the remote MALC:
zSH> bridge add 1-1-2-0/ethernetcsmacd intralink
zSH> bridge-path add ethernet2/bridge
global-intralink

Linear GigaBit Ethernet

The MALC GigE-2 Uplink card also supports a linear topology in which
several MALC devices are daisy-chained together to pass traffic and provide
subscriber access. The card type in the card profile is used to differentiate
linear configuration from RPR ring configuration. Single card or redundant
card configurations can be used.

126 MALC Configuration Guide

 Linear GigaBit Ethernet

Figure 18 illustrates the GigE-2 card linear configuration using single GigE-2
Uplink cards. Additional MALC nodes can be added to the daisy-chained
linear topology by repeating this pattern of connections.

Note: Interface 1-1-1-0 is assigned to the 10/100 Ethernet physical

interface. Interface 1-1-2-0 is assigned to physical port 1. Interface
1-1-3-0 is assigned to physical port 2.

Figure 18: GigE linear configuration with single card

IP
or
Ethernet

1-1-2-0

1-1-3-0

Subscribers

1-1-2-0

1-1-3-0

Subscribers

Redundant GigE-2 cards can also be used to provide card-level redundancy.

Figure 19 illustrates the GigE-2 Uplink card linear configuration using
redundant cards.

MALC Configuration Guide 127

Bridging

Figure 19: GigE linear configuration with redundant cards

IP
or
Ethernet

1-1-2-0 1-2-2-0

1-1-3-0 1-2-3-0

Subscribers

1-1-2-0 1-2-2-0
1-2-3-0
1-1-3-0

Subscribers

GigE-2 Uplink card redundant configuration in linear topology

This section describes the optional configuration procedures for the GigE-2
Uplink redundant card configuration in a linear topology. These procedures
should be done before provisioning the system.
See the MALC Hardware Installation Guide for more details about adding
redundant GigE-2 cards to the MALC.

Configuring GigE-2 card redundancy

The GigE-2 card can be configured for redundancy so the GigE uplink card
switches to a standby GigE card when the active Ethernet link goes down.
Options for this card switchover include:
• switching timeout
The amount of time the active card waits when a failure occurs before
switching to the standby card.
• reversion mode

128 MALC Configuration Guide

 Linear GigaBit Ethernet

The reversion mode determines if traffic reverts back to the initial active
card after a protection event is cleared.
• restore timeout
After a switchover occurs, the amount of time the active card waits after
the protection event is cleared before reverting back to the other card.
1 To configure card redundancy, use the line-red command on the active
card.
zSH> line-red set ethernet1/ip timeout 30 revertive
timeout 600

This command sets card redundancy between the currently active GigE-2
card and the standby GigE-2 card. The switch timeout is set to 30 seconds
with the revertive option set to occur after a 600 second timeout.
The standby card must be in a running state for a switchover to occur.
2 Display the redundancy setting.
zSH> line-red show ethernet1/ip
redundacy status for ethernet1/ip:
REBOOT timeout 30 REVERTIVE revert timeout 600

GigE-2 card bridging

Within the linear topology, bridging can be configured to forward traffic

based on MAC address and VLAN ID to an IP or outside network. The node
connected to the network contains a bridge uplink and global bridge-path on
the GigE-2 card’s first port (1-1-2-0) to direct all bridged traffic to the outside
or IP network. This card also contains a global-intralink on the GigE-2 card’s
second port (1-1-3-0) so unknown traffic is sent to the downstream, even
though address learning is not enabled.
The second node in the daisy-chained linear topology contains a bridge uplink
on the GigE-2 card’s first port (1-1-2-0) to direct all outgoing bridged traffic
to the upstream node. This node also contains a bridge intralink on the second
port (1-1-3-0) so unknown traffic is sent to the downstream to another
network or subtended Ethernet device, even though address learning is not
enabled.
Additional MALC nodes can be added to the daisy-chained linear topology by
repeating this pattern of connections and bridging.
Figure 20 illustrates the GigE-2 card linear configuration using redundant
cards.

MALC Configuration Guide 129

Bridging

Figure 20: GigE linear configuration with single card and bridging

IP
or
Ethernet

bridge uplink
bridge add 1-1-2-0/ethernetcsmacd uplink
bridge-path add ethernet3/bridge global
1-1-2-0

1-1-3-0
Intralink
bridge add 1-1-3-0/ethernetcsmacd intralink bridge downlink
bridge-path add ethernet2/bridge global-intralink bridge add 1-5-1/adsl vc 0/37
td 4000 downlink vlan 100 untagged

bridge uplink
bridge add 1-1-2-0/ethernetcsmacd uplink
bridge-path add ethernet3/bridge global
1-1-2-0

Intralink 1-1-3-0
bridge add 1-1-3-0/ethernetcsmacd intralink
bridge-path add ethernet2/bridge global-intralink bridge downlink
bridge add 1-8-1/adsl vc 0/39
td 3000 downlink vlan 200 untagged

Configuring GigE-2 card bridging

1 On the node connected to the Ethernet or IP network
a Add a bridge interface to the first GigE-2 port (this is the port
connected to the external network):
zSH> bridge add 1-1-2-0/ethernetcsmacd uplink

b Add a default bridge path over the first GigE-2 port:

zSH> bridge-path add ethernet3/bridge global
All bridge traffic will be forwarded over this interface.
c Add an bridge intralink on the second GigE-2 port:
zSH> bridge add 1-1-3-0/ethernetcsmacd intralink
zSH> bridge-path add ethernet2/bridge
global-intralink
Unlearned traffic received on this interface is forwarded to the
external network.
This interface is the global intralink for the node.
d Add a downlink to the remote subscriber:
zSH> bridge add 1-5-1-0/adsl vc 0/37 td 4000
downlink vlan 100 untagged

130 MALC Configuration Guide

 Advanced bridging configurations

2 On the next node in the linear daisy-chain configuration:

a Add an uplink bridged interface:
zSH> bridge add 1-1-2-0/ethernetcsmacd uplink
b Add a default bridge path that points to the Uplink node:
zSH> bridge-path add ethernet2/bridge global
c Add an bridge intralink on the second GigE-2 port:
zSH> bridge add 1-1-3-0/ethernetcsmacd intralink
zSH> bridge-path add ethernet2/bridge
global-intralink
Unlearned traffic received on this interface is forwarded to the
external network.
This interface is the global intralink for the node.
d Add a downlink to the remote subscriber:
zSH> bridge add 1-8-1-0/adsl vc 0/39 td 3000
downlink vlan 200 untagged
3 Continue this configuration for all the nodes in the daisy-chain
connection.

Advanced bridging configurations

The default settings for bridge interfaces are created based on the usage of the
downlink and uplink parameters of the bridge add command. It is
recommended not to change the default settings unless advanced bridge
configuration is required. Examples of advanced bridge configurations
include:
• Bridge configuration groups and records (Option 82 and Forbid OUI) on
page 131
• Tagged bridge—VLANs on page 133
• Broadcast suppression on page 134

Bridge configuration groups and records (Option 82 and Forbid OUI)

The MALC supports bridge configuration groups and records so an

open-ended number of filter settings can be configured for a bridge interface.
The same filter settings can also be easily applied to multiple bridge
interfaces.
Bridge configuration records are typically assigned to bridge configuration
groups on downlink bridge interfaces. Each bridge configuration record
contains settings for type and value. The bridgeConfigType parameter
specifies the variety of filter to be applied to the interface. Type options are
bridgeinsertoption82 and bridgeforbidoui. The bridgeConfigValue
parameter specifies either a 3-byte hexadecimal vendor code used with the

MALC Configuration Guide 131

Bridging

Forbid OUI to forbid access on the interface or an identification text used with
Insert option 82 to identify the DHCP host.

Note: Bridge configuration record settings supersede the global filter

settings set using the bridge-path add filter command.

Configuring bridge configuration records

Create bridge configuration records using the bridge-config-record profile.
Specify group/instance index numbers to assign group and instance
identification.
Configure a new bridge-config-record for group1/instance2 and specify
the desired type and value settings:
zSH> new bridge-config-record 1/2
Please provide the following: [q]uit.
bridgeConfigType: --> {bridgeinsertoption82}: bridgeforbidoui
bridgeConfigValue: -> {}: 00:02:02
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

Configuring bridge interface record

Configure the bridge-interface-record to assign all instances of a given
bridge configuration group to a specified interface. Bridge configuration
groups are assigned to the interface records by setting the
bridgeIfConfigGroupIndex parameter.
To configure a bridge configuration group:
zSH> update bridge-interface-record 1-3-1-0-adsl-0-35/bridge
Please provide the following: [q]uit.
vpi: ----------------------> {0}:
vci: ----------------------> {39}:
vlanId: -------------------> {46}:
stripAndInsert: -----------> {true}:
customARP: ----------------> {false}:
filterBroadcast: ----------> {false}:
learnIp: ------------------> {true}:
learnUnicast: -------------> {true}:
maxUnicast: ---------------> {5}:
learnMulticast: -----------> {true}:
forwardToUnicast: ---------> {false}:
forwardToMulticast: -------> {false}:
forwardToDefault: ---------> {true}:
bridgeIfCustomDHCP: -------> {false}:
bridgeIfConfigGroupIndex: -> {0}: 1
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

132 MALC Configuration Guide

 Advanced bridging configurations

Enabling option 82 using bridge-path command

The option82 option is available in the bridge-path command to enable the
insertion of the option 82 information into the global DHCP offer requests.
To enable option 82 information:
1 Add two bridges, one connecting the remote host, the other connecting to
a remote bridge. For example:
zSH> bridge add 1-4-1-0/shdsl vc 0/35 td 1 remote device
zSH> bridge add 1-1-1-0/ethernetcsmacd uplink

2 View the bridges:

zSH> bridge show
VLAN Bridge State Table Data
-----------------------------------------------------------------
0 1-4-1-0-shdsl-0-35/bridge UP S Global default [3600 sec]
0 1-1-1-0-ethernetcsmacd/bridge UP

3 Then, create the bridge path with option82 specified:

zSH> bridge-path add 1-4-1-0-shdsl-0-35/bridge option82

4 View the bridge path:

zSH> bridge-path show
VLAN Bridge Address
-----------------------------------------------------------------
Global 1-1-1-0-ethernetcsmacd/bridge Default

Tagged bridge—VLANs

In most configurations, VLAN IDs should be stripped for traffic destined to

downlink interfaces and inserted for traffic destined for upstream interfaces.
Downlink interfaces typically do not need to know the VLAN ID since they
are on a single Ethernet. You can, however, specify that a downlink interface
be tagged, or an uplink interface be untagged. You might want this if you are
subtending MALC devices and aggregating Ethernet traffic.

Configuring stripAndInsert
Configure the bridge-interface-record to change the stripping and insert of
VLAN tags for a specified interface.
To change the stripAndInsert option:
zSH> update bridge-interface-record 1-3-1-0-adsl-0-35/bridge
Please provide the following: [q]uit.
vpi: ----------------------> {0}:
vci: ----------------------> {39}:
vlanId: -------------------> {46}:
stripAndInsert: -----------> {true}: false
customARP: ----------------> {false}:

MALC Configuration Guide 133

Bridging

filterBroadcast: ----------> {false}:

learnIp: ------------------> {true}:
learnUnicast: -------------> {true}:
maxUnicast: ---------------> {5}:
learnMulticast: -----------> {true}:
forwardToUnicast: ---------> {false}:
forwardToMulticast: -------> {false}:
forwardToDefault: ---------> {true}:
bridgeIfCustomDHCP: -------> {false}:
bridgeIfConfigGroupIndex: -> {0}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

Broadcast suppression

Broadcast suppression enables DHCP information to be relayed between

DHCP client and host while broadcast filtering is enabled.

CustomDHCP setting
The customDHCP setting enables bridge interfaces to pass DHCP
information independent of the filterBroadcast setting. Setting customDHCP
to TRUE will cause that bridge interface to pass DHCP OFFER and ACK
packets even though the filterBroadcast is set to TRUE.
To enable CustomDHCP:
For an existing bridge, update the bridge-interface-record.
zSH> update bridge-interface-record 1-3-1-0-adsl-0-35/bridge
Please provide the following: [q]uit.
vpi: ----------------------> {0}:
vci: ----------------------> {39}:
vlanId: -------------------> {46}:
stripAndInsert: -----------> {true}:
customARP: ----------------> {false}:
filterBroadcast: ----------> {false}:
learnIp: ------------------> {true}:
learnUnicast: -------------> {true}:
maxUnicast: ---------------> {5}:
learnMulticast: -----------> {true}:
forwardToUnicast: ---------> {false}:
forwardToMulticast: -------> {false}:
forwardToDefault: ---------> {true}:
bridgeIfCustomDHCP: -------> {false}: true
bridgeIfConfigGroupIndex: -> {0}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

134 MALC Configuration Guide

 Administrative commands

Administrative commands
The MALC provides the following administrative commands:
• bridge delete
• bridge show
• bridge showall
• bridge-path add
• bridge-path show
• bridge-path delete

Bridge delete command

The bridge delete command deletes a specific bridge entry from the system.

Bridge show/showall commands

The bridge show and bridge showall commands display either a single
bridge path entry or the entire bridge table.

MALC Configuration Guide 135

Bridging

136 MALC Configuration Guide

6
PROVISIONING GR-303 OR V5.2 INTERFACE
GROUPS

This section explains how to configure GR-303 and V5.2 interface groups on
the MALC and how to configure system settings for voice. It includes the
following information:
• Configuring a GR-303 interface, page 137
• Modifying a GR-303 interface group, page 141
• Configuring a V5.2 interface, page 143
• Modifying the v52-interface-group profile, page 154
After configuring the GR-303 or V5.2 interface, proceed to adding
subscribers, as explained in Voice Gateway Connections on page 199 or
Adding Voice Connections on page 155.

Note: The TDM/ATM Uplink card or the Voice Gateway card is

required for GR-303 and V5.2 support on the MALC.

Note: This chapter assumes you have configured the TDM/ATM

Uplink and the Voice Gateway card as explained in the MALC
Hardware Installation Guide.

The TDM/ATM Uplink card has 16 T1/E1 ports. The first eight ports are
ATM T1/E1 ports; the second eight are TDM T1/E1 ports.

Configuring a GR-303 interface

The following steps are necessary to configure GR-303 interface groups on
the MALC. Each step is explained in more detail in the sections that follow:
1. Update the system profile to specify the country the unit is operating in
and to enable voice bandwidth check. See Updating system settings on
page 156.
2. Find the line group identifier of the communication path (the DS1
interface on the TDM/ATM Uplink card).
3. Create the GR-303 Interface Group (IG). See Creating a GR-303
interface group on page 139.

MALC Configuration Guide 137

Provisioning GR-303 or V5.2 Interface Groups

4. Activate the GR-303 IG.

The following table summarizes the configuration tasks for creating a GR-303
interface.

Configuration Task Profile

Creating a GR-303 interface group on page 139. new gr303-interface-group GR303Index

Use the same GR303Index for the gr303-interface-group
and the CRVs in the gr303-ig-crv profile.

Modifying a GR-303 interface group on page 141 update gr303-interface-group GR303Index

Note: The sapi-1-n-200 and sapi-1-max-outstanding-frames

parameters automatically take the same values as the sapi-0-n-200
and sapi-0-max-outstanding-frames parameters.

The gr303-interface-group profile supports the following parameters.

Parameter Description and options

name-id A name assigned by the installer. It must be unique to the system. This
value is a string. This is a required field.

switch-type The name of the switch supplying the GR-303 circuits. This is a required
field.
Values:
lucent5Ess
nortelDms100
adminStatus The administrative status of the IG. This must be set to inservice for the IG
to function.
Values:
inservice
outofservice

working-mode Indicates whether the selected switch can configure the RDT using
common management information service (CMIS) over the Embedded
Operations Channel (EOC) channel.
Values:
active the selected switch can configure the RDT for Call Reference
Values (CRVs) over the EOC channel. Normally used for 5ESS switches.
passive CRVs can only be configured locally. Normally used for DMS
switch.

CrtlChannel: The IG control channel array.

ds1LM:array[1..28]: The array for T1/DS1 circuits. The maximum number of DS1 trunks
allowed per IG is 28. This array includes the dsn-lg-id, channel-number,
and role parameters.

138 MALC Configuration Guide

 Configuring a GR-303 interface

Parameter Description and options

dsn-lg-id The DS1 line group ID number. This must match the line group ID of the
physical interface on which you are provisioning GR-303 IGs.
channel-number Identifies the DS1 for the channelized DS3.
Values:
1 to 28
role The role this channel plays in the array. Must be set to primary for the first
DS1. One other DS1 must have the role parameter set to secondary. All
other DS1s have their role set to payload.
Values:
payload
secondary
primary
Default: payload

logical-id Identifies each physical DS1 within an Interface Group between RDT and
IDT. The value 1 is reserved for the primary DS1 and cannot be used by
any other DS1s. This field is mandatory.
Values:
1 to 28

ds1-valid-flag Whether this DS1 is valid or invalid. Must be set to valid to enable calls
over provisioned DS1s.
Values:
valid
invalid

Creating a GR-303 interface group

To create a GR-303 interface group:
1 List the ds1-profiles
zSH> list ds1-profile
if-translate 1-1-9-0/ds1
if-translate 1-1-10-0/ds1
if-translate 1-1-11-0/ds1
if-translate 1-1-12-0/ds1
if-translate 1-1-13-0/ds1
if-translate 1-1-14-0/ds1
if-translate 1-1-15-0/ds1
if-translate 1-1-16-0/ds1
...

Then enter the lineGroup command to find the line group identifiers for
the TDM T1/E1 ports. Make a note of the lineGroupIds of the TDM T1/
E1 ports; they will be used later.
zSH> linegroup 1-1-9-0/ds1
lineGroupId: 13

MALC Configuration Guide 139

Provisioning GR-303 or V5.2 Interface Groups

zSH> linegroup 1-1-10-0/ds1

lineGroupId: 15

zSH> linegroup 1-1-11-0/ds1

lineGroupId: 17

zSH> linegroup 1-1-12-0/ds1

lineGroupId: 19

zSH> linegroup 1-1-13-0/ds1

lineGroupId: 21

zSH> linegroup 1-1-14-0/ds1

lineGroupId: 23

zSH> linegroup 1-1-15-0/ds1

lineGroupId: 25

zSH> linegroup 1-1-16-0/ds1

lineGroupId: 27

2 Create a new GR-303 interface group. For example:

zSH> new gr303-interface-group 1 1 is a user-defined Index for this IG
Please provide the following: [q]uit.
name-id: -----------------------> {}: zhone
switch-type: -------------------> {lucent5ess}: lucent5ess | norteldms100
adminStatus: -------------------> {outofservice}: inservice
working-mode: ------------------> {passive}: active | passive
ctrlChannel:
control-channel-t303: ----------> {700}:
control-channel-t396: ----------> {14700}:
sapi-0-max-outstanding-frames: -> {7}:
sapi-0-n-200: ------------------> {3}:
sapi-0-t-200: ------------------> {150}:
sapi-0-t-203: ------------------> {30}:
sapi-0-pps-mode: ---------------> {notinhibited}:
sapi-1-max-outstanding-frames: -> {7}:
sapi-1-n-200: ------------------> {3}:
sapi-1-t-200: ------------------> {150}:
sapi-1-t-203: ------------------> {30}:
sapi-1-pps-mode: ---------------> {notinhibited}:
ds1LM has 28 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? s
Enter the array element to start: 1
ds1LM[1]:
dsn-lg-id: ---------------------> {1}: 13 linegroup ID of the first port on the TDM/ATM Uplink
channel-number: ----------------> {1}:
role: --------------------------> {payload}: primary
logical-id: --------------------> {28}: 1 1 is reserved for primary channels. Use numbers 2
to 28 for other types of channels.
ds1-valid-flag: ----------------> {invalid}: valid
ds1LM[3]:
dsn-lg-id: ---------------------> {1}: 15 linegroup ID of the second port on the TDM/ATM
Uplink

140 MALC Configuration Guide

 Configuring a GR-303 interface

channel-number: ----------------> {1}:

role: --------------------------> {payload}: secondary
logical-id: --------------------> {28}: 2
ds1-valid-flag: ----------------> {invalid}: valid
ds1LM[4]:
dsn-lg-id: ---------------------> {1}: 17 linegroup ID of the third port on the TDM/ATM
Uplink
channel-number: ----------------> {1}:
role: --------------------------> {payload}:
logical-id: --------------------> {28}: 3
ds1-valid-flag: ----------------> {invalid}: valid
ds1LM[5]:
dsn-lg-id: ---------------------> {1}: q
....................
Save record? [s]ave, [c]hange or [q]uit: s
New record saved.

3 Activate the GR-303 interface group (IG):

zSH> update gr303-interface-group 1
Please provide the following: [q]uit.
name-id: -----------------------> {zhone}:
switch-type: -------------------> {lucent5ess}:
adminStatus: -------------------> {outofservce}: inservice
working-mode: ------------------> {passive}:
ctrlChannel:
control-channel-t303: ----------> {700}:
control-channel-t396: ----------> {14700}:
sapi-0-max-outstanding-frames: -> {7}:
sapi-0-n-200: ------------------> {3}:
sapi-0-t-200: ------------------> {150}:
sapi-0-t-203: ------------------> {30}:
sapi-0-pps-mode: ---------------> {notinhibited}:
sapi-1-max-outstanding-frames: -> {7}:
sapi-1-n-200: ------------------> {3}:
sapi-1-t-200: ------------------> {150}:
sapi-1-t-203: ------------------> {30}:
sapi-1-pps-mode: ---------------> {notinhibited}:
ds1LM has 28 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n
Using default values for elements 1-28
....................
Save record? [s]ave, [c]hange or [q]uit: s
Record updated.

After the GR-303 IG is activated, proceed to configuring GR-303 subscribers.

For information, see Adding Voice Connections on page 155.

Modifying a GR-303 interface group

Caution: Removing an IG from service will cause all active calls to

be dropped.

MALC Configuration Guide 141

Provisioning GR-303 or V5.2 Interface Groups

To remove service from the IG:

zSH> update gr303-interface-group 1
Please provide the following: [q]uit.
name-id: -----------------------> {zhone}:
switch-type: -------------------> {lucent5ess}:
adminStatus: -------------------> {inservice}: outofservice
working-mode: ------------------> {passive}:
ctrlChannel:
control-channel-t303: ----------> {700}:
control-channel-t396: ----------> {14700}:
sapi-0-max-outstanding-frames: -> {7}:
sapi-0-n-200: ------------------> {3}:
sapi-0-t-200: ------------------> {150}:
sapi-0-t-203: ------------------> {30}:
sapi-0-pps-mode: ---------------> {notinhibited}:
sapi-1-max-outstanding-frames: -> {7}:
sapi-1-n-200: ------------------> {3}:
sapi-1-t-200: ------------------> {150}:
sapi-1-t-203: ------------------> {30}:
sapi-1-pps-mode: ---------------> {notinhibited}:
ds1LM has 28 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n
Using default values for elements 1-28
....................
Save record? [s]ave, [c]hange or [q]uit: s
Record updated.

To restore service to the IG:

zSH> update gr303-interface-group 1
Please provide the following: [q]uit.
name-id: -----------------------> {zhone}:
switch-type: -------------------> {lucent5ess}:
adminStatus: -------------------> {outofservce}: inservice
working-mode: ------------------> {passive}:
ctrlChannel:
control-channel-t303: ----------> {700}:
control-channel-t396: ----------> {14700}:
sapi-0-max-outstanding-frames: -> {7}:
sapi-0-n-200: ------------------> {3}:
sapi-0-t-200: ------------------> {150}:
sapi-0-t-203: ------------------> {30}:
sapi-0-pps-mode: ---------------> {notinhibited}:
sapi-1-max-outstanding-frames: -> {7}:
sapi-1-n-200: ------------------> {3}:
sapi-1-t-200: ------------------> {150}:
sapi-1-t-203: ------------------> {30}:
sapi-1-pps-mode: ---------------> {notinhibited}:
ds1LM has 28 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n
Using default values for elements 1-28
....................
Save record? [s]ave, [c]hange or [q]uit: s
Record updated.

142 MALC Configuration Guide

 Configuring a V5.2 interface

Configuring a V5.2 interface

The following steps are necessary to configure V5.2 interface groups on the
MALC. Each step is explained in more detail in the sections that follow:
1. Update the system profile to specify the country the unit is operating in
and to enable voice bandwidth check. See Updating system settings on
page 156.
2. Find the line group identifier of the communication path (the DS1
interface on the TDM/ATM Uplink card).
3. Create the V5.2 IG. See Creating a V5.2 interface group on page 146.
4. Provision the V5.2 links. See Provisioning V5.2 links on page 148.
5. Add C-channels within links. See Adding C-channels within links on
page 150.
6. Provision C-paths. See Provisioning C-paths on page 152.
7. Activate the V5.2 IG. See Activating the V5.2 IG on page 153.
The following table summarizes the tasks for configuring the V5.2 interface.

Configuration task Commands

Creating a V5.2 interface group on page 146 new v52-interface-group v52IgIndex

Finding the line group identifiers of the physical update v52-interface-group v52IgIndex
connection on page 147

Provisioning V5.2 links on page 148

Adding C-channels within links on page 150

Provisioning C-paths on page 152

Activating the V5.2 IG on page 153

The following sections describe in further detail each step necessary in the
configuration process.

Note: Although the v52-link, v52-c-channel and v52-c-path arrays

can be provisioned at the same time the v52-interface-group is
created, the steps are separated for clarity.

MALC Configuration Guide 143

Provisioning GR-303 or V5.2 Interface Groups

The following table describes the supported V5.2 parameters in the

v52-interface-group. The V5.2 interface group (IG) is configured using one
profile.

Parameter Options

name-id The name of the IG. Must be unique in the system. Use the same name for the
voice-v52-interface-name parameter in the subscriber-voice-v52 profile. This
value is a string.

local-interface-id The interface ID of the IG. Must be unique across the system. This value must
match the value on the switch.
Values:
0 to 16777215

local-prov-variant The prov(isioning) variant describes a type of provisioning. This value must
match the value on the switch.
Values:
0 to 127

admin-status The administrative status of the profile.

Values:
inservice
outofservice
deferredoutofservice
restart

pstn-layer-3-start-address The start address for PSTN users. When PSTN users are added, they must have
an address greater or equal to this one. This value must match the value on the
switch.
Values:
0 to 65535

isdn-env-func-start-address The start address for ISDN users. When ISDN users are added, they must have
an address greater or equal to this one. This value must match the value on the
switch.
Values:
0 to 8175
national-pstn-region Country setting. Sets up PSTN values for the specific country.

switch-vendor The switch vendor for the IG.

Values:
lucent, nortel, alcatel, ericsson, nokia, siemens, samsung.

protocol-spec Specifies which variation of the V5.2 protocol is to be used by this interface
group. This value must match the value on the switch.
Values:
edition1
edition2

144 MALC Configuration Guide

 Configuring a V5.2 interface

Parameter Options

v52-ig-lapv An array of V5.2 Lapv timer parameters. These configure retries and other
functions over the management links. This value must match the value on the
switch.

v52-link[1..16] This array is used to provision the E1circuits between the LE and the MALC
unit. There can be up to sixteen links. Each E1 link has 32 channels.

dsn-lg-id Describes the line group ID associated with the E1 link. Use the lineGroup
command to find the line group ID.
Values:
1 to 16

id The V5.2 link identifier.

Assigned by the Local Exchange (LE).
v52-c-channel: array [1..3] This array describes up to three control channels per link (E1). There can be up
to 3 of them on each of the16 links for a maximum of 48. C-channels are used
to pass management information between then LE and the MALC system.

time-slot-index The channel that the C-channel is running over. This value must match the
value on the switch.
Values:
15
16
31

logical-channel-id C-channels carry a group of one or more C-paths, excluding the C-paths used
for the protection protocol. A V5.2 interface may contain up to 44 logical
C-channels. Each logical C-channel on an interface is uniquely identified with a
16 bit logical C-channel identifier. This value must match the value on the
switch.
Values:
0 to 65535

protection-group The protection protocol ensures that other protocols can continue to operate in
case of equipment failure. This value must match the value on the switch.
Values:
none
group1
onetoonegroup2
mtongroup2

role The C-channel role. This value must match the value on the switch.
Values:
active
standby
switchtostandby
Default: active

MALC Configuration Guide 145

Provisioning GR-303 or V5.2 Interface Groups

Parameter Options

link-valid-flag Activates the E1 circuit.

Values:
valid
invalid

v52-c-path: array [1..48] This array describes communications paths. C-paths are used to specify the
type of information running between the MALC system and the LE. C-paths
run inside C-channels. There can be up to 48 C-paths inside each C-channel.
Values:
Use the logical-channel-id numbers created for the C-channels.

id The ID number of the communications path.

Values:
0 to 255

type The type of communications path. This tells the system how the management
information is communicated.
Values:
unknown
pstn POTS
ctrl control protocol
bcc bearer channel connection
lctl link control protocol
isdnds BRI voice data

logical-channel-id The logical C-channel ID that the C-path is using. This number must match the
logical-channel-id value of the C-channel that the C-path is running over.
Values:
0 to 65535

c-path-valid-flag When this parameter is set to valid, the C-path is active.

Values:
valid
invalid

Creating a V5.2 interface group

Note: While provisioning is being performed on the V5.2 interface,

the IG should be kept out of service.

The following example shows how to create a V5.2 IG named zhone.

zSH> new v52-interface-group 1
Please provide the following: [q]uit.
name-id: ---------------------> {}: zhone
local-interface-id: ----------> {0}: 1
local-prov-variant: ----------> {0}: 1
prov-variant-request: --------> {norequest}:

146 MALC Configuration Guide

 Configuring a V5.2 interface

admin-status: ----------------> {outofservice}:

pstn-layer-3-start-address: --> {0}: 1
isdn-env-func-start-address: -> {0}: 1
port-alignment-request: ------> {norequest}:
national-pstn-region: --------> {etsi}: germany match the country in the system profile
switch-vendor: ---------------> {ericsson}: siemens match switch
protocol-spec: ---------------> {edition2}:
startup-check-link-id: -------> {false}:
startup-unblock-user-ports: --> {false}:
link-oos-timer: --------------> {2500}:
link-is-timer: ---------------> {200}:
v52-ig-lapv:
max-outstanding-frames: ------> {7}: ** read-only **
n200: ------------------------> {3}: ** read-only **
n201: ------------------------> {260}: ** read-only **
t200: ------------------------> {1000}: ** read-only **
t203: ------------------------> {10}: ** read-only **
v52-link has 16 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n
Using default values for elements 1-16
v52-c-path has 48 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n
Using default values for elements 1-48
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Note: After creating the IG, certain parameters in the

v52-interface-group can only be modified with the v52config
command. For details, see Modifying the v52-interface-group profile
on page 154.

Finding the line group identifiers of the physical connection

List the ds1-profiles:

zSH> list ds1-profile
if-translate 1-1-9-0/ds1
if-translate 1-1-10-0/ds1
if-translate 1-1-11-0/ds1
if-translate 1-1-12-0/ds1
if-translate 1-1-13-0/ds1
if-translate 1-1-14-0/ds1
if-translate 1-1-15-0/ds1
if-translate 1-1-16-0/ds1
...

Then enter the lineGroup command to find the line group identifiers for the
TDM T1/E1 ports. Make a note of the lineGroupIds of the TDM T1/E1 ports;
they will be used later.
zSH> linegroup 1-1-9-0/ds1
lineGroupId: 13

MALC Configuration Guide 147

Provisioning GR-303 or V5.2 Interface Groups

zSH> linegroup 1-1-10-0/ds1

lineGroupId: 15

zSH> linegroup 1-1-11-0/ds1

lineGroupId: 17

zSH> linegroup 1-1-12-0/ds1

lineGroupId: 19

zSH> linegroup 1-1-13-0/ds1

lineGroupId: 21

zSH> linegroup 1-1-14-0/ds1

lineGroupId: 23

zSH> linegroup 1-1-15-0/ds1

lineGroupId: 25

zSH> linegroup 1-1-16-0/ds1

lineGroupId: 27

Make a note of the lineGroupIds of the TDM T1/E1 ports; they will be used
later.

Provisioning V5.2 links

This section explains how to provision individual E1 circuits or V5.2 links.

• To create V5.2 links, enter s for subset at the v52-link has 16 elements
Modify [a]ll, [n]one, a [s]ubset, or [q]uit? prompt
• For each E1 circuit, enter a unique dsn-lg-id number. Refer to Finding the
line group identifiers of the physical connection on page 147.
• Enter a link id number.
• Enter valid at the link-valid-flag prompt to turn the link up.
This example configures three links:
zSH> update v52-interface-group 1 the IG created earlier
Please provide the following: [q]uit.
name-id: ---------------------> {zhone}: ** read-only **
local-interface-id: ----------> {1}:
local-prov-variant: ----------> {1}:
prov-variant-request: --------> {norequest}:
admin-status: ----------------> {outofservice}:
pstn-layer-3-start-address: --> {1}:
isdn-env-func-start-address: -> {1}:
port-alignment-request: ------> {norequest}:
national-pstn-region: --------> {germany}:
switch-vendor: ---------------> {siemens}:
protocol-spec: ---------------> {edition2}:
startup-check-link-id: -------> {false}:
startup-unblock-user-ports: --> {false}:

148 MALC Configuration Guide

 Configuring a V5.2 interface

link-oos-timer: --------------> {2500}:

link-is-timer: ---------------> {200}:
v52-ig-lapv:
max-outstanding-frames: ------> {7}: ** read-only **
n200: ------------------------> {3}: ** read-only **
n201: ------------------------> {260}: ** read-only **
t200: ------------------------> {1000}: ** read-only **
t203: ------------------------> {10}: ** read-only **
v52-link has 16 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit?
Modify [a]ll, [n]one, a [s]ubset, or [q]uit? s to modfy the V5.2 links
Enter the array element to start: 1
v52-link[1]:
dsn-lg-id: -------------------> {1}: 13 linegroup ID of the first port on the TDM/
ATM Uplink
ds1-channel-number: ----------> {1}:
id: --------------------------> {0}: 1 identifier for first link, must match switch
check-id: --------------------> {notactivated}:
block: -----------------------> {unblocked}:
v52-c-channel has 3 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n
Using current values for elements 1-3
link-valid-flag: -------------> {invalid}: valid
v52-link[2]:
dsn-lg-id: -------------------> {1}: 15 linegroup ID of the second port on the TDM/
ATM Uplink
ds1-channel-number: ----------> {1}:
id: --------------------------> {0}: 2 identifier for second link, must match switch
check-id: --------------------> {notactivated}:
block: -----------------------> {unblocked}:
v52-c-channel has 3 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n
Using current values for elements 1-3
link-valid-flag: -------------> {invalid}: valid
v52-link[3]:
dsn-lg-id: -------------------> {1}: 17 linegroup ID of the third port on the TDM/
ATM Uplink
ds1-channel-number: ----------> {1}:
id: --------------------------> {0}: 3 identifier for third link, must match switch
check-id: --------------------> {notactivated}:
block: -----------------------> {unblocked}:
v52-c-channel has 3 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n
Using current values for elements 1-3
link-valid-flag: -------------> {invalid}: valid
v52-link[4]:
dsn-lg-id: -------------------> {1}: q
Using current values for elements 4-16
v52-c-path has 48 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n
Using current values for elements 1-48
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

MALC Configuration Guide 149

Provisioning GR-303 or V5.2 Interface Groups

Adding C-channels within links

This example shows how to configure control channels for links you created
in Provisioning V5.2 links on page 148. Control channels (C-channels) to pass
management information between the switch and the MALC. There can be up
to three C-channels per E1 link, on channel numbers 15, 16 and 31.
• Enter 15, 16 or 31 for the time-slot-index option.
• Enter the logical-channel-id. Each C-channel must have a unique
numerical identifier.
• Enter a protection-group name (optional).
• Specify the role.
• Set the c-channel-valid-flag to valid.
The following example shows one C-channel provisioned in v52-link number
one, one in link number two, and two C-channels provisioned in link number
three.
zSH> update v52-interface-group 1
Please provide the following: [q]uit.
name-id: ---------------------> {zhone}: ** read-only **
local-interface-id: ----------> {1}:
local-prov-variant: ----------> {1}:
prov-variant-request: --------> {norequest}:
admin-status: ----------------> {outofservice}:
pstn-layer-3-start-address: --> {1}:
isdn-env-func-start-address: -> {1}:
port-alignment-request: ------> {norequest}:
national-pstn-region: --------> {germany}:
switch-vendor: ---------------> {siemens}:
protocol-spec: ---------------> {edition2}:
startup-check-link-id: -------> {false}:
startup-unblock-user-ports: --> {false}:
link-oos-timer: --------------> {2500}:
link-is-timer: ---------------> {200}:
v52-ig-lapv:
max-outstanding-frames: ------> {7}: ** read-only **
n200: ------------------------> {3}: ** read-only **
n201: ------------------------> {260}: ** read-only **
t200: ------------------------> {1000}: ** read-only **
t203: ------------------------> {10}: ** read-only **
v52-link has 16 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? s
Enter the array element to start: 1
v52-link[1]:
dsn-lg-id: -------------------> {2}:
ds1-channel-number: ----------> {1}:
id: --------------------------> {1}:
check-id: --------------------> {notactivated}:
block: -----------------------> {unblocked}:
v52-c-channel has 3 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? s
Enter the array element to start: 1

150 MALC Configuration Guide

 Configuring a V5.2 interface

v52-c-channel[1]:
time-slot-index: -------------> {16}:
logical-channel-id: ----------> {0}: 1
protection-group: ------------> {none}: group1
role: ------------------------> {active}:
c-channel-valid-flag: --------> {invalid}: valid
v52-c-channel[2]:
time-slot-index: -------------> {16}: q
Using current values for elements 2-3
link-valid-flag: -------------> {valid}:
v52-link[2]:
dsn-lg-id: -------------------> {4}:
ds1-channel-number: ----------> {1}:
id: --------------------------> {2}:
check-id: --------------------> {notactivated}:
block: -----------------------> {unblocked}:
v52-c-channel has 3 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? s
Enter the array element to start: 1
v52-c-channel[1]:
time-slot-index: -------------> {16}:
logical-channel-id: ----------> {0}: 2
protection-group: ------------> {none}: group1
role: ------------------------> {active}: standby
c-channel-valid-flag: --------> {invalid}: valid
v52-c-channel[2]:
time-slot-index: -------------> {16}: q
Using current values for elements 2-3
link-valid-flag: -------------> {valid}:
v52-link[3]:
dsn-lg-id: -------------------> {6}:
ds1-channel-number: ----------> {1}:
id: --------------------------> {3}:
check-id: --------------------> {notactivated}:
block: -----------------------> {unblocked}:
v52-c-channel has 3 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? s
Enter the array element to start: 1
v52-c-channel[1]:
time-slot-index: -------------> {16}:
logical-channel-id: ----------> {0}: 3
protection-group: ------------> {none}:
role: ------------------------> {active}:
c-channel-valid-flag: --------> {invalid}: valid
v52-c-channel[2]:
time-slot-index: -------------> {16}: q
Using current values for elements 2-3
link-valid-flag: -------------> {valid}: q
Using current values for elements 4-16
v52-c-path has 48 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n
Using current values for elements 1-48
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

MALC Configuration Guide 151

Provisioning GR-303 or V5.2 Interface Groups

Provisioning C-paths

You can set how the management information in the C-channel is

communicated by provisioning the communication path (C-path). The C-path
array is provisioned within the C-channel array. The C-path
logical-channel-id number must match the logical-channel-id value you
assigned for the C-channel in the Adding C-channels within links on
page 150. For each C-path, follow these steps:
• Assign a unique id number for each C-path.
• Enter a type value. To communicate ISDN BRI management data for
voice calls, use the isdnds option.
• Assign the logical-channel-id number for the C-channel that the C-path
is running over.
• Each c-path-valid-flag must be set to valid to activate the C-path.
This example shows how to configure seven communications paths. The first
four are in C-channel number one, the fifth and sixth are created in channel
three, and the seventh is created in channel four.
zSH> update v52-interface-group 1
Please provide the following: [q]uit.
name-id: ---------------------> {zhone}: ** read-only **
local-interface-id: ----------> {1}:
local-prov-variant: ----------> {1}:
prov-variant-request: --------> {norequest}:
admin-status: ----------------> {outofservice}:
pstn-layer-3-start-address: --> {1}:
isdn-env-func-start-address: -> {1}:
port-alignment-request: ------> {norequest}:
national-pstn-region: --------> {germany}:
switch-vendor: ---------------> {siemens}:
protocol-spec: ---------------> {edition2}:
startup-check-link-id: -------> {false}:
startup-unblock-user-ports: --> {false}:
link-oos-timer: --------------> {2500}:
link-is-timer: ---------------> {200}:
v52-ig-lapv:
max-outstanding-frames: ------> {7}: ** read-only **
n200: ------------------------> {3}: ** read-only **
n201: ------------------------> {260}: ** read-only **
t200: ------------------------> {1000}: ** read-only **
t203: ------------------------> {10}: ** read-only **
v52-link has 16 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n
Using current values for elements 1-16
v52-c-path has 48 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? s
Enter the array element to start: 1
v52-c-path[1]:
id: --------------------------> {1}:
type: ------------------------> {unknown}: bcc bear channel connection
logical-channel-id: ----------> {0}: 1

152 MALC Configuration Guide

 Configuring a V5.2 interface

c-path-valid-flag: -----------> {invalid}: valid

v52-c-path[2]:
id: --------------------------> {1}: 2
type: ------------------------> {unknown}: ctrl control protocol
logical-channel-id: ----------> {0}: 1
c-path-valid-flag: -----------> {invalid}: valid
v52-c-path[3]:
id: --------------------------> {1}: 3
type: ------------------------> {unknown}: lctl link control protocol
logical-channel-id: ----------> {0}: 1
c-path-valid-flag: -----------> {invalid}: valid
v52-c-path[4]:
id: --------------------------> {1}: 4
type: ------------------------> {unknown}: pstn POTS signalling
logical-channel-id: ----------> {0}: 1
c-path-valid-flag: -----------> {invalid}: valid
v52-c-path[5]:
id: --------------------------> {1}: 5
type: ------------------------> {unknown}: isdnds ISDN data signaling
logical-channel-id: ----------> {0}: 1
c-path-valid-flag: -----------> {invalid}: valid
v52-c-path[6]:
id: --------------------------> {1}: q
Using current values for elements 6-48
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated

Activating the V5.2 IG

Activate the interface after provisioning is finished.

The example activates an IG number 1:
zSH> update v52-interface-group 1 V5.2 interface group number
Please provide the following: [q]uit.
name-id: ---------------------> {zhone}: ** read-only **
local-interface-id: ----------> {1}:
local-prov-variant: ----------> {1}:
prov-variant-request: --------> {norequest}:
admin-status: ----------------> {outofservice}: inservice
pstn-layer-3-start-address: --> {1}:
isdn-env-func-start-address: -> {1}:
port-alignment-request: ------> {norequest}:
national-pstn-region: --------> {germany}:
switch-vendor: ---------------> {siemens}:
protocol-spec: ---------------> {edition2}:
startup-check-link-id: -------> {false}:
startup-unblock-user-ports: --> {false}:
link-oos-timer: --------------> {2500}:
link-is-timer: ---------------> {200}:
v52-ig-lapv:
max-outstanding-frames: ------> {7}: ** read-only **
n200: ------------------------> {3}: ** read-only **

MALC Configuration Guide 153

Provisioning GR-303 or V5.2 Interface Groups

n201: ------------------------> {260}: ** read-only **

t200: ------------------------> {1000}: ** read-only **
t203: ------------------------> {10}: ** read-only **
v52-link has 16 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n
Using current values for elements 1-16
v52-c-path has 48 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n
Using current values for elements 1-48
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

After the V5.2 IG is activated, proceed to configuring V5.2 subscribers. For

information, see Adding Voice Connections on page 155.

Modifying the v52-interface-group profile

If you need to modify the following parameters in the v52-interface-group

profile, it can only be done using the v52config command:
• prov-variant-request
• admin-status (to set to restart only)
• port-alignment-request
• cchannelrole (to set to switchtostandby only)
The syntax of the command is as follows
v52config checklinkid/switchchan/restart/variant/block/
unblock INTERFACE_ID linkid/cchan/aligntype
The following table describes the arguments for the v52config command:

Argument Description

INTERFACE_ID The local interface ID number. This is the value of the

name-id parameter in the v52-interface-group profile.

linkid Used with the checklinkid argument.

cchan Used with the switchchan argument.

aligntype Used with the block and unblock arguments. Can be isdn,
pstn or all.

For example, to restart the interface (local-interface-id) named 100:

zSH> v52config restart 100
To run a check link id on the interface named 100, with a linkid of 4:
zSH> v52config checklinkid 100 4

154 MALC Configuration Guide

7
ADDING VOICE CONNECTIONS

This chapter explains how to configure voice connections between subscriber

endpoints and remote gateways and how to customize the voice parameters
when required. It includes the following sections:
• Overview, page 155
• Updating system settings, page 156
• Creating voice connections, page 158
• Configuring CES connections, page 168
• Additional VOIP features, page 184
• Additional voice features, page 193

Overview
The following types of voice connections between subscriber and remote
endpoints are supported:

Note: The voice gateway card requires MALC software version

1.11.1 or higher on the uplink cards.

Subscriber Gateway MALC Uplinks

endpoints endpoints

POTS AAL2 All

DS1 TDM, OC-12c/STM4, Gigabit Ethernet

GR303 TDM, OC-12c/STM4, Gigabit Ethernet

VOIP All

V5.2 TDM, OC-12c/STM4, Gigabit Ethernet

ISDN AAL2 All

V5.2 TDM, OC-12c/STM4, Gigabit Ethernet

VOIP GR303 All TDM IP (voice gateway card required)

V5.2 All TDM IP (voice gateway card required)

MALC Configuration Guide 155

Adding Voice Connections

Subscriber Gateway MALC Uplinks

endpoints endpoints

AAL2 GR303 All TDM ATM (voice gateway card required)

V5.2 All TDM ATM (voice gateway card required)

ALL2 V5.2 All TDM ATM (voice gateway card required)

ELCP

Note: This chapter assumes you have configured the required TDM/
ATM Uplink, POTS, and ISDN physical interfaces as explained in the
MALC Hardware Installation Guide.

Updating system settings

Prior to configuring a voice connection, ensure the system settings are
configured to support desired type of voice connection.
The system profile contains settings that configure country-specific settings
for voice calls and determines whether the system will reject incoming calls if
there isn’t enough bandwidth available.
Modifying the system profile ensures that the ring frequency and voice
encoding (A-law/Mu-law) are correctly set.
The show system command displays the available system profile settings.

Setting a-law or mu-law and DSP settings (POTS)

Note: The MALC supports A-Law or Mu-Law encoding, but they

cannot both be used simultaneously in a single chassis.

The countryregion parameter of the system profile specifies the country

where the device is operating. This parameter sets the companding mode
(A-Law or Mu-Law) and the ring frequency used by the voice network.
The A-law and Mu-law settings can also be set using the optional alaw and
mulaw parameters in the voice add command. See Creating voice
connections on page 158.

Checking bandwidth before accepting a voice call (AAL2)

In voice over ATM (VoATM) networks, the MALC is capable of

oversubscribing on AAL2 connections. If voice bandwidth checking is
enabled, the system will reject a call if there is not enough bandwidth. If a call
is rejected, the MALC sends a fast busy to the caller over the POTS line.
Bandwidth checking is recommended for voice connections.

156 MALC Configuration Guide

 Updating system settings

Note: Bandwidth calculations are enabled or disabled for the entire

system.

The bandwidth check is based on the configuration of the transmit and receive
ATM traffic descriptors for the ATM VC used by the call. The system uses the
following parameters to calculate the required bandwidth:
• rt-VBR traffic: SCR
• CBR traffic: PCR
• All other traffic types: calls are always accepted, there are no
voice-quality guarantees.
The system will reject calls if:
[Receive or transmit cell rate - (180*number of active calls on the VC)] < 180
(The bandwidth calculations assume that approximately 180 AAL2 cells per
second are used for each voice call.)

Updating the system profile

To update the system profile:
zSH> update system 0
Please provide the following: [q]uit.
syscontact: ----------> {Zhone Global Services and Support 7001 Oakport Road Oa
kland Ca. (877) Zhone20 (946-6320) Fax (510)777-7113 [email protected]}:
sysname: -------------> {Zhone Malc}:
syslocation: ---------> {Oakland}:
enableauthtraps: -----> {disabled}:
setserialno: ---------> {0}:
zmsexists: -----------> {false}:
zmsconnectionstatus: -> {inactive}:
zmsipaddress: --------> {0.0.0.0}:
configsyncexists: ----> {false}:
configsyncoverflow: --> {false}:
configsyncpriority: --> {high}:
configsyncaction: ----> {noaction}:
configsyncfilename: --> {}:
configsyncstatus: ----> {syncinitializing}:
configsyncuser: ------> {}:
configsyncpasswd: ----> {}:
numshelves: ----------> {1}:
shelvesarray: --------> {}:
numcards: ------------> {3}:
ipaddress: -----------> {0.0.0.0}:
alternateipaddress: --> {0.0.0.0}:
countryregion: -------> {us}: enter the country, if different from the default
primaryclocksource: --> {0/0/0/0/0}:
ringsource: ----------> {internalringsourcelabel}:
revertiveclocksource: -> {true}
voicebandwidthcheck: --> {false} true if bandwidth checking is desired
....................

MALC Configuration Guide 157

Adding Voice Connections

Save changes? [s]ave, [c]hange or [q]uit: s

Record updated.

Creating voice connections

Voice connections provide voice signaling connections between subscriber
endpoints and voice gateway endpoints.
The voice command can be used to add, delete, and show voice connection
settings. When a voice connection is added or deleted, the voice command
creates or deletes the related profiles for both the subscriber and remote
endpoints.
The voice command uses the following syntax
voice add subscriber-endpoint remote-endpoint [alaw |
mulaw] [enable]
This command automatically creates all the subscriber and ATM profiles
required by the voice connection. For POTS and AAL2 voice connections,
this command also optionally sets the PCM-encoding parameter to the
specified encoding method and enables the voice connection.
Note that in some cases the profiles with voice configuration parameters may
have to be updated to customize the voice configuration.
This section describes the procedures for configuring the following types of
gateway voice connections:
• AAL2 connections on page 158
• DS1 voice gateway connections on page 160
• Voice over IP (VOIP) voice gateway connections on page 162

AAL2 connections

This section explains the following:

• Creating an ATM traffic descriptor on page 158
• Configuring ISDN to AAL2 connections on page 159
• Configuring POTS to AAL2 connections on page 160

Creating an ATM traffic descriptor

Before configuring ISDN or POTS subscriber voice connections that utilize
remote ATM connections to an AAL2 voice gateway, the ATM traffic
descriptor must exist.

Note: See MALC ATM overview on page 21 for more information on

ATM traffic descriptors and parameters.

Create a new atm-traf-descr with a unique index for a voice connection.

158 MALC Configuration Guide

 Creating voice connections

zSH> new atm-traf-descr 1 index can be any value

Please provide the following: [q]uit.
td_type: -----------------> {atmNoClpNoScr}: atmClpNoTaggingScrCdvt
td_param1: ---------------> {0}: 4826 PCR .
td_param2: ---------------> {0}: 4825 SCR
td_param3: ---------------> {0}: 20 MBS
td_param4: ---------------> {0}: 15000 CDVT
td_param5: ---------------> {0}:
cac-divider: -------------> {1}: 10
td_service_category: -----> {ubr}: rtvbr for voice
td_frame_discard: --------> {false}:
usage-parameter-control: -> {true}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Configuring ISDN to AAL2 connections

This type of voice connection requires a ULC card.
For ISDN-to-AAL2 configurations, either a voice gateway (such as the
MALC Voice Gateway card) or a TDM/ATM Uplink card converts
AAL2-derived voice into TDM signaling. For AAL2 connections, the ATM
traffic descriptor is required before the voice connection can be configured.
The voice add command automatically creates the required VPI/VCI, CID,
and uplink VCL and sets the following ISDN parameters:
• atm-vcl profile: vcc aal5 cpcs transmit and receive sdu sizes
• aal2-vcl-profile: timer-cu, frame-mode-data, cas, trunk-type,
pcm-encoding, and ras-timer
• aal2-cid-profile: frame-mode-data, cas, and pcm-encoding
This voice add command example uses the ISDN interface 1-3-1-0/isdnu, sets
the VPI/VCI to 0/38, sets the CID to 127.
1 To configure a ISDN to AAL2 voice connection:
zSH> voice add isdn 1-3-1-0/isdnu aal2 uplink1/atm vc 0/38 cid 127 enable
Created subscriber-voice 1/5/4
Created subscriber-voice-isdn 65
Created aal2-cid-profile 38/0/38/127
Created subscriber-voice-aal2 66
Created subscriber-voice 1/5/5
Created subscriber-voice-isdn 67
Created subscriber-voice-aal2 68
Created subscriber-voice 1/5/6
Created subscriber-voice-isdn 69
Created subscriber-voice-aal2 70

2 View the voice connection

zSH> voice show
Subscriber end-point Remote end-point Voice Prof Id STA
------------------------------ ------------------------------ -------------- ---

MALC Configuration Guide 159

Adding Voice Connections

1-3-1-0/isdnu 1-1-1-0/ds1 VC 0/38 CID 127 1/5/4 ENA

1-3-1-0/isdnu 1-1-1-0/ds1 VC 0/38 CID 158 1/5/5 ENA
1-3-1-0/isdnu 1-1-1-0/ds1 VC 0/38 CID 159 1/5/6 ENA
Total number of voice connections : 3

Configuring POTS to AAL2 connections

For POTS-to-AAL2 configurations, either a voice gateway (such as the
MALC Voice Gateway card) or a TDM/ATM Uplink card can be used to
convert AAL2-derived voice into TDM signaling. For AAL2 connections, the
ATM traffic descriptor is required before the voice connection can be
configured. The voice add command automatically creates the required VPI/
VCI, CID, and uplink VCL.
This example adds a POTS to AAL2 connection over an ATM VCL with a
VPI/VCI of 0/38 and a CID of 16: The PCM-encoding is set to Alaw and the
the interface 1-5-24-0/voicefxs is enabled.
1 Use the voice command to add the POTS to AAL2 connection.
zSH> voice add pots 1-5-24-0/voicefxs alaw aal2 uplink1/atm vc 0/39 td 11/11 cid 16
enable
Created subscriber-voice 1/32/2
Created subscriber-voice-pots 10017
Created atm-vcl uplink1/atm/0/39
Created aal2-cid-profile 38/0/39/16
Created subscriber-voice-aal2 10018

2 View the voice connection.

zSH> voice show
Subscriber end-point Remote end-point Voice Prof Id STA
------------------------------ ------------------------------ -------------- ---
1-5-24-0/voicefxs 1-2-1-0/atmima VC 0/39 CID 16 1/32/2 ENA
Total number of voice connections : 1

DS1 voice gateway connections

DS1 voice connections use a direct channel map between the subscriber
signals and the voice uplink.

Note: DS1 voice connections are only supported with line type D4.

This section explains how to configure the following types of connections:

• Configuring POTS to GR303 connections on page 161
• ISDN to V5.2 connections on page 161
• Configuring POTS to V.52 connections on page 162

160 MALC Configuration Guide

 Creating voice connections

ISDN to V5.2 connections

For ISDN-to-V5.2 configurations, the MALC interconnects ISDN terminal
equipment directly to V.52 switches. The V5.2 IG must already exist before
the voice connection can be configured.
1 Use the voice command to add the ISDN to V5.2 connection. This
example uses the 1-3-1-0/isdnu physical interface and sets the required
fields in the atm-vcl, aal2-vcl-profile, and the aal2-cid-profile.
zSH> voice add isdn 1-3-1-0/isdnu v52 1/1 cpath 5
enable
Created subscriber-voice 1/13/25
Created subscriber-voice-isdn 49
Created v52-user-port 1/1/3
Created subscriber-voice-v52 50
Created subscriber-voice 1/13/26
Created subscriber-voice-isdn 51
Created subscriber-voice-v52 52
Created subscriber-voice 1/13/27
Created subscriber-voice-isdn 53
Created subscriber-voice-v52 54

2 View the voice connection.

zSH> voice show 1-3-1-0/isdnu
Subscriber end-point Remote end-point Voice Prof Id STA
--------------------------- --------------------------- -------------- ---
1-3-1-0/isdnu V52 1/1 3/32/13011 ENA
1-3-1-0/isdnu V52 1/1 3/32/13012 ENA
1-3-1-0/isdnu V52 1/1 3/32/13013 ENA

Configuring POTS to DS1 connections

POTS to DS1 voice connections.
1 Use the voice command to add the POTS to DS1 connection.
zSH> voice add pots 1-5-24-0/voicefxs ds1 1-1-9-0/ds1 ds0 24
Created subscriber-voice 1/21/25
Created subscriber-voice-pots 83
Created subscriber-voice-ds1 84

2 View the voice connections:

zSH> voice show
Subscriber end-point Remote end-point Voice Prof Id STA
------------------------------ ------------------------------ -------------- ---
1-5-24-0/voicefxs 1-1-9-0/ds1 DS0 24 1/21/25 ENA

Configuring POTS to GR303 connections

For GR303 voice connections, the GR303 interface with IG must already
exist. For POTS-to-GR303 configurations, the MALC interconnects POTS
equipment directly to GR-303 switches.

MALC Configuration Guide 161

Adding Voice Connections

This example creates a POTS to GR303 subscriber profile with IG 1 and CRV
2. It also sets the administrative status interface to up.
1 Use the voice command to add the POTS to GR303 connection.
zSH> voice add pots 1-8-1-0/voicefxs gr303 1/2 enable
Created subscriber 1/13
Created subscriber-voice 1/13/1
Created subscriber-voice-pots 20
Created gr303-ig-crv 1/2
Created subscriber-voice-gr303 21

2 View the voice connection:

zSH> voice show 1-8-1-0/voicefxs

Subscriber end-point Remote end-point Voice Prof Id STA

------------------------------ ------------------------------ -------------- ---
1-8-1-0/voicefxs GR303 Zhone/2 1/13/1 ENA
Total number of voice connections : 1

Configuring POTS to V.52 connections

The MALC interconnects POTS equipment directly to V5.2 switches. For
POTS subscriber to V5.2 voice gateway connections, the V5.2 IG must exist
before the voice connection can be configured.
1 Use the voice command to add the POTS to V5.2 connection.
zSH> voice add pots 1-8-1-0/voicefxs v52 1/28 cpath 1
Created subscriber 1/13
Created subscriber-voice 1/13/1
Created subscriber-voice-pots 10013
Created v52-user-port 1/28/2
Created subscriber-voice-v52 10014

2 View the voice connection.

zSH> voice show
Subscriber end-point Remote end-point Voice Prof Id STA
------------------------------ ------------------------------ -------------- ---
1-8-1-0/voicefxs V52 1/28 1/13/1 ENA
Total number of voice connections : 1

Voice over IP (VOIP) voice gateway connections

The following procedures describe how to configure each of the supported

types of VOIP subscriber voice connections. VOIP subscribers can be
connected to DS1, V5.2, POTS, and GR303 remote endpoints.
Before creating VOIP connections, ensure that the IP interface, VOIP system,
and VOIP server settings are configured properly.
This section contains the following procedures:

162 MALC Configuration Guide

 Creating voice connections

• Configuring VOIP system settings on page 163

• Configuring MGCP or SIP on page 164
• Creating POTS to VOIP connections on page 165

Configuring VOIP system settings

1 Configure an IP interface for VOIP. For example:
zSH> new ip-interface-record 1-1-1-0/ip
Please provide the following: [q]uit.
vpi: ---------------> {0}:
vci: ---------------> {0}:
rdindex: -----------> {1}:
dhcp: --------------> {none}: ** read-only **
addr: --------------> {0.0.0.0}: 192.168.87.2
netmask: -----------> {0.0.0.0}: 255.255.255.0
bcastaddr: ---------> {0.0.0.0}: 192.168.87.255
destaddr: ----------> {0.0.0.0}:
farendaddr: --------> {0.0.0.0}:
mru: ---------------> {1500}:
reasmmaxsize: ------> {0}:
ingressfiltername: -> {}:
egressfiltername: --> {}:
pointtopoint: ------> {no}:
mcastenabled: ------> {yes}:
ipfwdenabled: ------> {yes}:
mcastfwdenabled: ---> {yes}:
natenabled: --------> {no}:
bcastenabled: ------> {yes}:
ingressfilterid: ---> {0}:
egressfilterid: ----> {0}:
ipaddrdynamic: -----> {static}:
dhcpserverenable: --> {false}:
subnetgroup: -------> {0}:
unnumberedindex: ---> {0}:
mcastcontrollist: --> {}:
vlanid: ------------> {0}:
maxVideoStreams: ---> {0}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
Record updated.

2 Configure a system IP address:

zSH> update system 0
Please provide the following: [q]uit.
syscontact: -----------> {Zhone Technologies 7001
Oakport Street Oakland CA 94621}:
sysname: --------------> {Zhone Malc}}:
syslocation: ----------> {}:
enableauthtraps: ------> {disabled}:
setserialno: ----------> {0}:
zmsexists: ------------> {false}:

MALC Configuration Guide 163

Adding Voice Connections

zmsconnectionstatus: --> {inactive}:

zmsipaddress: ---------> {0.0.0.0}:
configsyncexists: -----> {false}:
configsyncoverflow: ---> {false}:
configsyncpriority: ---> {high}:
configsyncaction: -----> {noaction}:
configsyncfilename: ---> {}:
configsyncstatus: -----> {syncinitializing}:
configsyncuser: -------> {}:
configsyncpasswd: -----> {** private **}: **
read-only **
numshelves: -----------> {1}:
shelvesarray: ---------> {}:
numcards: -------------> {1}:
ipaddress: ------------> {0.0.0.0}: 192.168.7.45
alternateipaddress: ---> {0.0.0.0}:
countryregion: --------> {us}:
primaryclocksource: ---> {0/0/0/0/0}:
ringsource: -----------> {internalringsourcelabel}:
revertiveclocksource: -> {true}:
voicebandwidthcheck: --> {false}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

3 Update the voip-server-entry profile to specify a VOIP server:

zSH> update voip-server-entry 1/1
zhoneVoipServerAddrType: ------> {ipv4}
zhoneVoipServerAddr: ----------> {0.0.0.0}
206.229.26.54
zhoneVoipServerUdpPortNumber: -> {2727}
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

Configuring MGCP or SIP

The protocol setting can be configured as either Media Gateway Control
Protocol (MGCP) or Session Initiation Protocol (SIP) signaling. By default,
the MALC uses SIP signaling.

Note: Communication with SIP phones is only possible over one

interface of the MALC. Communication with SIP phones that are in
the same network as other interfaces on the MALC is not supported.

MGCP signalling establishes call control elements or call agents to handle

call control. MGCP devices execute the commands sent by the call agents.
SIP signalling identifies callers and callees by SIP addresses and allows
signals to be redirected to proxy servers.

164 MALC Configuration Guide

 Creating voice connections

Note: If all SIP calls do not register after a system reboot, increase
the server-max-timer value in the voice-system profile to a higher
value, for example 180 seconds. The default value is 20 seconds.

To change the setting to MGCP:

1 Update the voip-system profile to enable MGCP:
zSH> update voip-system 0
Please provide the following: [q]uit.
protocol: ------------------> {sip}: mgcp
send-call-proceeding-tone: -> {false}:
rtcp-enabled: --------------> {false}:
rtcp-packet-interval: ------> {5000}:
interdigit-timeout: --------> {10}:
ip-tos: --------------------> {0}:
system-domain-name: --------> {}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

2 The system will automatically reboot. After the reboot, verify that the
voip-system profile is configured for MGCP:
zSH> get voip-system 0
protocol: ------------------> {mgcp}:
send-call-proceeding-tone: -> {false}:
rtcp-enabled: --------------> {false}:
rtcp-packet-interval: ------> {5000}:
interdigit-timeout: --------> {10}:
ip-tos: --------------------> {0}:
system-domain-name: --------> {}:

Creating POTS to VOIP connections

This example creates a POTS to VOIP subscriber.
1 Use the voice command to add the POTS to VOIP connection. This
examples creates a connection with a directory number 510-522-0401 and
the name smith:
zSH> voice add pots 1-3-1-0/voicefxs voip uplink1/ip DN 5105220401 name
smith
Created subscriber-voice 1/2/1
Created subscriber-voice-pots 1004
Created subscriber-voice-voip 1005

2 View the voice connection.

zSH> voice show
Subscriber end-point Remote end-point Voice Prof Id STA
------------------------------ ------------------------------ -------------- ---
1-3-1-0/voicefxs uplink1/ip DN 5105220401 1/2/1 ENA
Total number of voice connections : 1

MALC Configuration Guide 165

Adding Voice Connections

DS1 to POTS connections

The MALC can act as a channel bank, interconnecting POTS channels to

DS0s on the TDM T1/E1 card or the T1/E1 interface on the OC12-c/STM4
Uplink card. Note that T1 CAS, GR-303, and V5.2 signaling cannot be active
on a card at the same time.

Adding a POTS to DS1 connection

To enable a POTS to DS1 connection, you must reset the line type on the T1/
E1 TDM card or OC12-c/STM4 Uplink card.

Caution: Changing the line type for the Uplink card requires a
system reboot and deletes the system configuration.
Back up your configuration using the dump command before
changing the line type.

1 Change the line type on the T1/E1 TDM card or OC12-c/STM4 Uplink
card.

Note: If there is a redundant Uplink card in the system, change

that line type for the redundant card before changing it for the
active card.

For the T1/E1 TDM card:

a Verify you are at the root of the flash card:
zSH> cd /card1
zSH> pwd
/card1/

b Back up the current configuration file to the flash card and store it in
the onreboot directory:
zSH> mkdir onreboot
zSH> cd onreboot
zSH> dump file restore

This file will be used to restore the system configuration or revert to a

previous release, if desired.
c If desired, save the configuration file to a host on the network. For
example:
zSH> dump network 192.168.8.21 malc.cfg
d Change directories to the root of the flash card:
zSH> cd /card1
zSH> pwd
/card1/

166 MALC Configuration Guide

 Creating voice connections

e Delete the Uplink card-profile:

zSH> delete card-profile 1/1/5114 shelf/slot/type

f Create a new Uplink card-profile and change the card-line-type:

zSH> new card-profile 1/1/5114
Please provide the following: [q]uit.
sw-file-name: ---------> {}: malcT1E1Tdmf.bin
admin-status: ---------> {operational}:
upgrade-sw-file-name: -> {}:
upgrade-vers: ---------> {}:
admin-status-enable: --> {operational}:
sw-upgrade-admin: -----> {reloadcurrrev}:
sw-enable: ------------> {false}: true
sw-upgrade-enable: ----> {false}:
card-group-id: --------> {1}:
hold-active: ----------> {false}:
weight: ---------------> {nopreference}:
card-line-type: -------> {unknowntype}: t1-uni-t1cas
card-atm-configuration: -> {notapplicable}
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

After saving the Uplink card-profile, the card will reboot and restore
the configuration saved to the onreboot directory. If this is a
redundant system, the standby card will take over. You must also
change the line type on the redundant card.
For the OC12-c/STM4 Uplink card:
a Verify you are at the root of the flash card:
zSH> cd /card1
zSH> pwd
/card1/

b Back up the current configuration file to the flash card and store it in
the onreboot directory:
zSH> mkdir onreboot
zSH> cd onreboot
zSH> dump file restore

This file will be used to restore the system configuration or revert to a

previous release, if desired.
c If desired, save the configuration file to a host on the network. For
example:
zSH> dump network 192.168.8.21 malc.cfg
d Change directories to the root of the flash card:
zSH> cd /card1
zSH> pwd

MALC Configuration Guide 167

Adding Voice Connections

/card1/

e Delete the Uplink card-profile:

zSH> delete card-profile 1/1/5029 shelf/slot/type

f Create a new Uplink card-profile and change the card-line-type:

zSH> new card-profile 1/1/5029
Please provide the following: [q]uit.
sw-file-name: ---------> {}: malcoc12.bin
admin-status: ---------> {operational}:
upgrade-sw-file-name: -> {}:
upgrade-vers: ---------> {}:
admin-status-enable: --> {operational}:
sw-upgrade-admin: -----> {reloadcurrrev}:
sw-enable: ------------> {false}: true
sw-upgrade-enable: ----> {false}:
card-group-id: --------> {1}:
hold-active: ----------> {false}:
weight: ---------------> {nopreference}:
card-line-type: -------> {unknowntype}: t1-uni-t1cas
card-atm-configuration: -> {notapplicable}
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

After saving the Uplink card-profile, the card will reboot and restore the
configuration saved to the onreboot directory. If this is a redundant
system, the standby card will take over. You must also change the line
type on the redundant card.
2 After the system has finished booting, create the voice connection. The
following example maps POTS port 24 to DS0 24 on the T1/E1 TDM
card:
zSH> voice add pots 1-5-24-0/voicefxs ds1 1-1-9-0/ds1 ds0 24
Created subscriber-voice 1/21/25
Created subscriber-voice-pots 83
Created subscriber-voice-ds1 84

3 View the voice connection:

zSH> voice show

Subscriber end-point Remote end-point Voice Prof Id STA

------------------------------ ------------------------------ -------------- ---
1-5-24-0/voicefxs 1-1-9-0/ds1 DS0 24 1/21/25 ENA
Total number of voice connections : 1

Configuring CES connections

CES circuit configuration involves:

168 MALC Configuration Guide

 Configuring CES connections

• Creating IP interface and unnumbered IP interface on page 169

• Creating CES connections on page 170
• Deleting cross connections and CES over ATM circuits on page 183

Creating IP interface and unnumbered IP interface

If using CES over IP, an IP interface and unnumbered IP interface record are
required before the CES over IP connection can be created:
1 Create the IP interface record.
zSH> new ip-interface-record ces/ip
Please provide the following: [q]uit.
vpi: ---------------> {0}:
vci: ---------------> {0}:
rdindex: -----------> {1}:
dhcp: --------------> {none}: ** read-only **
addr: --------------> {0.0.0.0}: 192.168.100.1
netmask: -----------> {0.0.0.0}: 255.255.255.0
bcastaddr: ---------> {0.0.0.0}: 192.168.100.255
destaddr: ----------> {0.0.0.0}:
farendaddr: --------> {0.0.0.0}:
mru: ---------------> {1500}:
reasmmaxsize: ------> {0}:
ingressfiltername: -> {}:
egressfiltername: --> {}:
pointtopoint: ------> {no}:
mcastenabled: ------> {yes}:
ipfwdenabled: ------> {yes}:
mcastfwdenabled: ---> {yes}:
natenabled: --------> {no}:
bcastenabled: ------> {yes}:
ingressfilterid: ---> {0}:
egressfilterid: ----> {0}:
ipaddrdynamic: -----> {static}:
dhcpserverenable: --> {false}:
subnetgroup: -------> {0}:
unnumberedindex: ---> {0}:
mcastcontrollist: --> {}:
vlanid: ------------> {0}:
maxVideoStreams: ---> {0}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
Could not find an appropropriate interface on which to
bind the IP record.
Could not automatically bind this IP Interface
New record saved.

2 Create IP unnumbered record.

zSH> new ip-unnumbered-record 1
Please provide the following: [q]uit.
ipUnnumberedInterfaceName: -> { }: ces/ip

MALC Configuration Guide 169

Adding Voice Connections

....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Creating CES connections

The cross connect command specifies the parameters for one side of the CES
connection over an ATM circuit.The traffic descriptor is used for internal
ATM processing. Generally, each CES connection endpoint resides on a
different MALC system and must be configured and deleted separately for
each side for the circuit.
The CES add command specifies the parameters for one side of the CES over
IP connection. Generally, each CES over IP endpoint resides on a different
MALC system and must be configured and deleted separately for each side
for the circuit.

CES signaling
CES connections support both Channel Associated Signaling (CAS) and
Common Channel Signaling (CCS) depending on the connection mode and
type.
For structured T1 circuits, the CES card supports CAS (robbedbit signaling)
for in-band signaling. CAS uses one bit out of every channel in the sixth T1
frame in order to transmit signaling messages. Unstructured T1 circuits
support CCS for out-of-band signaling that uses an entire channel of each T1
frame to transmit signaling.
For structured E1 circuits, CAS can be used to extract signaling information
from timeslot 16 and then reinsert signaling data at the other end of the
connection. Unstructured E1 circuits transmit all 32 timeslots transparently.
Signal mode is set in the ds1-profile.
zSH> update ds1-profile 1-4-1-0/ds1
Please provide the following: [q]uit.
line-type: ----------------------> {esf}:
line-code: ----------------------> {b8zs}:
send-code: ----------------------> {sendnocode}:
circuit-id: ---------------------> {ds1}:
loopback-config: ----------------> {noloop}:
signal-mode: --------------------> {robbedbit}: bitoriented
fdl: ----------------------------> {fdlnone}:
dsx-line-length: ----------------> {dsx0}:
line-status_change-trap-enable: -> {enabled}:
channelization: -----------------> {enabledds0}:
ds1-mode: -----------------------> {csu}:
csu-line-length: ----------------> {csu00}:
clock-source-eligible: ----------> {eligible}:
transmit-clock-source: ----------> {looptiming}:
cell-scramble: ------------------> {true}:
coset-polynomial: ---------------> {true}:

170 MALC Configuration Guide

 Configuring CES connections

protocol-emulation: -------------> {network}:

signal-type: --------------------> {loopstart}:
ds1-group-number: ---------------> {0}:
line-power: ---------------------> {disabled}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

CES clocking
The CES card supports two timing modes:
• Loop timing
• Through timing
Loop timing indicates that the timing source is coming from the line. Through
timing indicates that the timing sources is from the backplane. The backplane
can be set to receive its clocking signal from a port on an uplink card or ports
on a line card. When through timing is used, the other side of the CES circuit
should be set to loop timing.
If loop timing is used and the card loses its received clock signal, clocking
switches to the clock on the board.
Clock mode is set in the DS1-profile. Refer to the MALC Hardware
Installation Guide for the procedures on how configure MALC timing.
zSH> update ds1-profile 1-4-1-0/ds1
Please provide the following: [q]uit.
line-type: ----------------------> {esf}:
line-code: ----------------------> {b8zs}:
send-code: ----------------------> {sendnocode}:
circuit-id: ---------------------> {ds1}:
loopback-config: ----------------> {noloop}:
signal-mode: --------------------> {robbedbit}:
fdl: ----------------------------> {fdlnone}:
dsx-line-length: ----------------> {dsx0}:
line-status_change-trap-enable: -> {enabled}:
channelization: -----------------> {enabledds0}:
ds1-mode: -----------------------> {csu}:
csu-line-length: ----------------> {csu00}:
clock-source-eligible: ----------> {eligible}:
transmit-clock-source: ----------> {looptiming}: throughtiming
cell-scramble: ------------------> {true}:
coset-polynomial: ---------------> {true}:
protocol-emulation: -------------> {network}:
signal-type: --------------------> {loopstart}:
ds1-group-number: ---------------> {0}:
line-power: ---------------------> {disabled}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

MALC Configuration Guide 171

Adding Voice Connections

CES configuration

This section shows configuration examples for the following CES procedures:
• Adding unstructured T1 CES circuit on page 173
• Adding a structured T1 CES circuit with ds1esfcas signaling on page 174
• Adding a second DS0 bundle to a structured T1 CES circuit with
ds1esfcas signaling on page 175
• Adding unstructured E1 CES circuit on page 176
• Adding a structured E1 CES circuit with e1cas signaling on page 177
• Adding a second cross connect to a structured E1 CES circuit with e1cas
signaling on page 178
• Adding an unstructured T1/E1 CES over IP circuit on page 179
• Adding a structured T1/E1 CES over IP circuit with ds1esfcas signaling
on page 181
• Deleting cross connections and CES over ATM circuits on page 183
The CES circuit signaling type is specified in the cross connect command
used to create the connection. After cross connect configuration, the signaling
type can be modified by updating the ces-config profile.

Note: When required, CES virtual circuits (VCs) are auto-generated

from the cross connect command.
The default virtual circuit ranges are VPI 0-3 and VCI 32-127.

Table 8: Supported CES signaling types

Signaling Type Description

basic No CAS bits with a single 125 usec frame.

Default. Required for unstructured channels.

e1cas CAS bits used in E1 multiframe structure.

ds1esfcas CAS bits used in DS1 ESF multiframe

structure.

ds1sfcas CAS bits used in DS1 SF multiframe structure.

After the cross connect command is issued, the system automatically creates
the required ces-config profile with the specified signaling type and other
settings. The default signaling type basic is required for unstructured, single
channel signaling and is used if a signalling type is not specified in the cross
connect command. Table 8 on page 172 lists the supported signaling types.

172 MALC Configuration Guide

 Configuring CES connections

Note: Structured DS0 bundles in cross connects are specified by start

and length values and therefore contain contiguous DS0s. To use
non-contiguous DS0s, modify the DS0-bundle parameter in the
ces-config profile.

For the first DS0 bundle in a structured DS1 circuit, the frame type specified
in the cross connect command is written to the DS1 profile and becomes the
default frame type for that DS1 circuit. Subsequent DS0 bundles in the same
DS1 circuit use the default frame type regardless of the line type specified in
the cross connect command. If line type is not specified in the cross connect
command, the line type in the DS1 profile is used.

Note: A maximum of 4 structured DS0 bundles can be configured

per CES port.

Adding unstructured T1 CES circuit

To add a CES cross connection for an unstructured T1 CES circuit, repeat
these configuration steps for each endpoint of the circuit.
1 Specify cross connect command with the desired settings. This example
specifies an unstructured circuit (single channel). No signaling type or
line type are specified. Unstructured single channels require basic
signaling so the basic signaling type is used. The ds1unframed line type
from the DS1-profile is used.
zSH> cc add uplink2/atm 0/53 1-12-3-0/ds1 vc 1/33 ds0 1/24 unstr td 1

2 Display the configured cross connection.

zSH> cc show CES
ATM VCL CC ATM VCL
--------------------------------------------------------------------------
uplink2/atm 0/53 Up 1 Up 1-12-3-0-ds1/atm 1/33 Up

3 Display the DS1 profile for the configured T1 CES unstructured circuit.
zSH> get ds1-profile 1-12-3-0/ds1
line-type: ----------------------> {ds1unframed}
line-code: ----------------------> {b8zs}
send-code: ----------------------> {sendnocode}
circuit-id: ---------------------> {ds1}
loopback-config: ----------------> {noloop}
signal-mode: --------------------> {none}
fdl: ----------------------------> {fdlnone}
dsx-line-length: ----------------> {dsx0}
line-status_change-trap-enable: -> {enabled}
channelization: -----------------> {disabled}
ds1-mode: -----------------------> {csu}
csu-line-length: ----------------> {csu00}
clock-source-eligible: ----------> {eligible}
transmit-clock-source: ----------> {throughtiming}

MALC Configuration Guide 173

Adding Voice Connections

cell-scramble: ------------------> {true}

coset-polynomial: ---------------> {true}
protocol-emulation: -------------> {network}
signal-type: --------------------> {loopstart}
ds1-group-number: ---------------> {0}
line-power: ---------------------> {disabled}

4 Display the ces-config profile for the configured T1 CES unstructured

circuit.
zSH> get ces-config 1-12-3-0-ds1-1/ds0bundle
vpi: --------------------------> {1}
vci: --------------------------> {33}
cas: --------------------------> {basic}
partial-fill: -----------------> {0}
buf-max-size: -----------------> {128}
cell-loss-integration-period: -> {2500}
ds0-bundle: ------------------->
{1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+21
+22+23+24}

Adding a structured T1 CES circuit with ds1esfcas signaling

To add a CES cross connection for a structured T1 CES circuit with esfcas
signaling, repeat these configuration steps for each endpoint of the circuit.
1 Specify cross connect command with the desired settings. This example
command creates a structured circuit using 6 DS0s starting at DS0 1 with
ds1esfcas signaling. No line type is specified so the esf line type from the
DS1-profile is used.
zSH> cc add uplink2/atm 0/54 1-12-4-0/ds1 vc 1/34 ds0 1/6 str ds1esfcas td 1

2 Display the configured cross connections.

zSH> cc show CES
ATM VCL CC ATM VCL
--------------------------------------------------------------------------
uplink2/atm 0/53 Up 1 Up 1-12-3-0-ds1/atm 1/33 Up
uplink2/atm 0/54 Up 3 Up 1-12-4-0-ds1/atm 1/34 Up

3 Display the DS1 profile for the configured structured CES circuit.
zSH> get ds1-profile 1-12-4-0/ds1
line-type: ----------------------> {esf}
line-code: ----------------------> {b8zs}
send-code: ----------------------> {sendnocode}
circuit-id: ---------------------> {ds1}
loopback-config: ----------------> {noloop}
signal-mode: --------------------> {robbedbit}
fdl: ----------------------------> {fdlnone}
dsx-line-length: ----------------> {dsx0}
line-status_change-trap-enable: -> {enabled}
channelization: -----------------> {disabled}
ds1-mode: -----------------------> {csu}

174 MALC Configuration Guide

 Configuring CES connections

csu-line-length: ----------------> {csu00}

clock-source-eligible: ----------> {eligible}
transmit-clock-source: ----------> {throughtiming}
cell-scramble: ------------------> {true}
coset-polynomial: ---------------> {true}
protocol-emulation: -------------> {network}
signal-type: --------------------> {loopstart}
ds1-group-number: ---------------> {0}
line-power: ---------------------> {disabled}

4 Display the ces-config profile for the configured CES circuit.

zSH> get ces-config 1-12-4-0-ds1-1/ds0bundle
vpi: --------------------------> {1}
vci: --------------------------> {34}
cas: --------------------------> {ds1esfcas}
partial-fill: -----------------> {0}
buf-max-size: -----------------> {128}
cell-loss-integration-period: -> {2500}
ds0-bundle: -------------------> {1+2+3+4+5+6}

Adding a second DS0 bundle to a structured T1 CES circuit

with ds1esfcas signaling
To add a second DS0 bundle to a CES cross connection for a structured T1
CES circuit with ds1esfcas signaling, repeat these configuration steps for
each endpoint of the circuit.
1 Specify cross connect command with the desired settings. This example
command specifies 6 DS0s starting at DS0 7 in a structured circuit using
ds1esfcas signaling type. The line type for secondary DS0 bundles must
match the line type of the first bundle or be left unspecified so the esf line
type from the DS1-profile is used.
zSH> cc add uplink2/atm 0/55 1-12-5-0/ds1 vc 1/35 ds0 7/6 str ds1esfcas td 1

2 Display the configured cross connections.

zSH> cc show CES
ATM VCL CC ATM VCL
--------------------------------------------------------------------------
uplink2/atm 0/53 Up 1 Up 1-12-3-0-ds1/atm 1/33 Up
uplink2/atm 0/54 Up 2 Up 1-12-4-0-ds1/atm 1/34 Up
uplink2/atm 0/55 Up 3 Up 1-12-5-0-ds1/atm 1/35 Up

3 Display the DS1 profile for the configured structured CES circuit.
zSH> get ds1-profile 1-12-5-0/ds1
line-type: ----------------------> {esf}
line-code: ----------------------> {b8zs}
send-code: ----------------------> {sendnocode}
circuit-id: ---------------------> {ds1}
loopback-config: ----------------> {noloop}
signal-mode: --------------------> {robbedbit}

MALC Configuration Guide 175

Adding Voice Connections

fdl: ----------------------------> {fdlnone}

dsx-line-length: ----------------> {dsx0}
line-status_change-trap-enable: -> {enabled}
channelization: -----------------> {disabled}
ds1-mode: -----------------------> {csu}
csu-line-length: ----------------> {csu00}
clock-source-eligible: ----------> {eligible}
transmit-clock-source: ----------> {throughtiming}
cell-scramble: ------------------> {true}
coset-polynomial: ---------------> {true}
protocol-emulation: -------------> {network}
signal-type: --------------------> {loopstart}
ds1-group-number: ---------------> {0}
line-power: ---------------------> {disabled}

4 Display the ces-config profile for the configured CES circuit.

zSH> get ces-config 1-12-5-0-ds1-2/ds0bundle
vpi: --------------------------> {1}
vci: --------------------------> {35}
cas: --------------------------> {ds1esfcas}
partial-fill: -----------------> {0}
buf-max-size: -----------------> {128}
cell-loss-integration-period: -> {2500}
ds0-bundle: -------------------> {7+8+9+10+11+12}

Adding unstructured E1 CES circuit

To add a CES cross connection for an unstructured E1 CES circuit, repeat
these configuration steps for each endpoint of the circuit.
1 Specify cross connect command with the desired settings. This command
specifies an unstructured channel. Unstructured channels require the basis
signaling type. No line type is specified so the e1unframed line type
from the DS1-profile is used.
zSH> cc add uplink1/atm 0/61 1-6-1-0/ds1 vc 1/32 ds0 0/32 unstr td 1

2 Display the configured cross connection.

zSH> cc show CES
ATM VCL CC ATM VCL
--------------------------------------------------------------------------
uplink2/atm 0/61 Up 1 Up 1-6-1-0-ds1/atm 1/32 Up

3 Display the DS1 profile for the configured structured CES circuit.
zSH> get ds1-profile 1-6-1-0/ds1
line-type: ----------------------> {e1unframed}
line-code: ----------------------> {hdb3}
send-code: ----------------------> {sendnocode}
circuit-id: ---------------------> {e1}
loopback-config: ----------------> {noloop}
signal-mode: --------------------> {none}
fdl: ----------------------------> {fdlnone}

176 MALC Configuration Guide

 Configuring CES connections

dsx-line-length: ----------------> {dsx0}

line-status_change-trap-enable: -> {enabled}
channelization: -----------------> {disabled}
ds1-mode: -----------------------> {other}
csu-line-length: ----------------> {csu00}
clock-source-eligible: ----------> {eligible}
transmit-clock-source: ----------> {throughtiming}
cell-scramble: ------------------> {true}
coset-polynomial: ---------------> {true}
protocol-emulation: -------------> {network}
signal-type: --------------------> {loopstart}
ds1-group-number: ---------------> {0}
line-power: ---------------------> {disabled}

4 Display the ces-config profile for the configured CES circuit.

zSH> get ces-config 1-6-1-0-ds1-1/ds0bundle
vpi: --------------------------> {1}
vci: --------------------------> {32}
cas: --------------------------> {basic}
partial-fill: -----------------> {0}
buf-max-size: -----------------> {128}
cell-loss-integration-period: -> {2500}
ds0-bundle: ------------------->
{0+1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+
21+22+23+24+25+26+27+28+29+30+31}

Adding a structured E1 CES circuit with e1cas signaling

To add a CES cross connection for a structured E1 CES circuit with e1cas
signaling, repeat these configuration steps for each endpoint of the circuit.
1 Specify cross connect command with the desired settings. This example
specifies 6 DS0s starting at DS0 1 in a structured circuit with e1case
signaling type e1cas. The line type is unspecified so the e1 line type from
the DS1-profile is used.
zSH> cc add uplink1/atm 0/62 1-6-2-0/ds1 vc 1/33 ds0 1/6 str e1cas td 1

2 Display the configured cross connections.

zSH> cc show CES
ATM VCL CC ATM VCL
--------------------------------------------------------------------------
uplink2/atm 0/62 Up 2 Up 1-6-2-0-ds1/atm 1/33 Up

3 Display the DS1 profile for the configured structured CES circuit.
zSH> get ds1-profile 1-6-2-0/ds1
line-type: ----------------------> {e1}
line-code: ----------------------> {hdb3}
send-code: ----------------------> {sendnocode}
circuit-id: ---------------------> {e1}
loopback-config: ----------------> {noloop}
signal-mode: --------------------> {bitoriented}

MALC Configuration Guide 177

Adding Voice Connections

fdl: ----------------------------> {fdlnone}

dsx-line-length: ----------------> {dsx0}
line-status_change-trap-enable: -> {enabled}
channelization: -----------------> {disabled}
ds1-mode: -----------------------> {other}
csu-line-length: ----------------> {csu00}
clock-source-eligible: ----------> {eligible}
transmit-clock-source: ----------> {throughtiming}
cell-scramble: ------------------> {true}
coset-polynomial: ---------------> {true}
protocol-emulation: -------------> {network}
signal-type: --------------------> {loopstart}
ds1-group-number: ---------------> {0}
line-power: ---------------------> {disabled}

4 Display the ces-config profile for the configured CES circuit.

zSH> get ces-config 1-6-2-0-ds1-1/ds0bundle
vpi: --------------------------> {1}
vci: --------------------------> {33}
cas: --------------------------> {e1cas}
partial-fill: -----------------> {0}
buf-max-size: -----------------> {128}
cell-loss-integration-period: -> {2500}
ds0-bundle: -------------------> {1+2+3+4+5+6}

Adding a second cross connect to a structured E1 CES

circuit with e1cas signaling
To add a second CES cross connection for a structured E1 CES circuit with
e1cas signaling, repeat these configuration steps for each endpoint of the
circuit.
1 Specify cross connect command with the desired settings. This example
specifies 6 DS0s starting at DS0 7 in a structured circuit using e1cas
signaling type. The line type for secondary DS0 bundles must match the
line type of the first bundle or be left unspecified so the e1 line type from
the DS1-profile is used.
zSH> cc add uplink2/atm 0/63 1-6-3-0/ds1 vc 1/34 ds0 7/6 str e1cas td 1

2 Display the configured cross connections.

zSH> cc show CES
ATM VCL CC ATM VCL
--------------------------------------------------------------------------
uplink2/atm 0/61 Up 1 Up 1-6-1-0-ds1/atm 1/32 Up
uplink2/atm 0/62 Up 2 Up 1-6-2-0-ds1/atm 1/33 Up
uplink2/atm 0/63 Up 3 Up 1-6-3-0-ds1/atm 1/34 Up

3 Display the DS1 profile for the configured structured CES circuit.
zSH> get ds1-profile 1-6-3-0/ds1
line-type: ----------------------> {e1}

178 MALC Configuration Guide

 Configuring CES connections

line-code: ----------------------> {hdb3}

send-code: ----------------------> {sendnocode}
circuit-id: ---------------------> {e1}
loopback-config: ----------------> {noloop}
signal-mode: --------------------> {bitoriented}
fdl: ----------------------------> {fdlnone}
dsx-line-length: ----------------> {dsx0}
line-status_change-trap-enable: -> {enabled}
channelization: -----------------> {disabled}
ds1-mode: -----------------------> {other}
csu-line-length: ----------------> {csu00}
clock-source-eligible: ----------> {eligible}
transmit-clock-source: ----------> {throughtiming}
cell-scramble: ------------------> {true}
coset-polynomial: ---------------> {true}
protocol-emulation: -------------> {network}
signal-type: --------------------> {loopstart}
ds1-group-number: ---------------> {0}
line-power: ---------------------> {disabled}

4 Display the ces-config profile for the configured CES circuit.

zSH> get ces-config 1-6-3-0-ds1-2/ds0bundle
vpi: --------------------------> {1}
vci: --------------------------> {34}
cas: --------------------------> {e1cas}
partial-fill: -----------------> {0}
buf-max-size: -----------------> {128}
cell-loss-integration-period: -> {2500}
ds0-bundle: -------------------> {7+8+9+10+11+12}

Adding an unstructured T1/E1 CES over IP circuit

Note: This procedure assumes that the T1E1CES12 card is installed

and running on the current device, a valid traffic descriptor has been
configured, and the unnumbered IP interface record has been created.

To add a CES connection for an unstructured T1/E1 CES over IP circuit,

repeat these configuration steps for each endpoint of the circuit.
1 Specify ces add command with the desired settings for each side for the
CES circuit. This example specifies an unstructured T1 circuit (single
channel). No signaling type or line type are specified. Unstructured
channels required basic signaling so the basic signaling type is used. The
line type in the DS1-profile is set to ds1unframed. Because no line type
is specified in this command, the line type from the DS1-profile is used.
The traffic descriptor 102 is autocreated and used for internal processing.
Using slot 8, port 2 on the CES card, the static IP addressing is source IP
address 10.2.2.82. and destination IP address is 10.2.3.83. The source
UDP port number is 140. The destination UDP port number is 141.

MALC Configuration Guide 179

Adding Voice Connections

Note: Ensure the IP routes between the source and destination

subnetworks have been configured and are available.

zSH> ces add 1-8-2-0-ds1/atm ds0 1/24 unstr td 102 llc static 10.2.2.82
10.2.3.83 140 141
zSH> ces add 1-8-3-0-ds1/atm ds0 1/24 unstr td 102 llc static 10.2.3.83
10.2.2.82 141 140

2 Change the administrative status of the ports to up.

zSH> update if-translate 1-8-2-0/ds1
Please provide the following: [q]uit.
ifIndex: -----------> {200}:
shelf: -------------> {1}:
slot: --------------> {7}:
port: --------------> {1}:
subport: -----------> {0}:
type: --------------> {ds1}:
adminstatus: -------> {down}: up
physical-flag: -----> {true}:
iftype-extension: --> {none}:
ifName: ------------> {1-7-1-0}:
redundancy-param1: -> {0}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.zSH>

zSH> update if-translate 1-8-3-0/ds1

Please provide the following: [q]uit.
ifIndex: -----------> {200}:
shelf: -------------> {1}:
slot: --------------> {7}:
port: --------------> {1}:
subport: -----------> {0}:
type: --------------> {ds1}:
adminstatus: -------> {down}: up
physical-flag: -----> {true}:
iftype-extension: --> {none}:
ifName: ------------> {1-7-1-0}:
redundancy-param1: -> {0}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.zSH>

3 Display the configured cross connection.

zSH> cc show CES

CONNECTION CC CONNECTION
---------------------------------------------------------------------------
1-1-1-0-aal5proxy/atm 0/33 Up 2 Up 1-8-2-0/ds1 1/24 Up
1-1-1-0-aal5proxy/atm 0/34 Up 3 Up 1-8-3-0/ds1 1/24 Up

180 MALC Configuration Guide

 Configuring CES connections

4 Display the DS1 profile for the configured T1/E1 CES unstructured
circuit over IP.
zSH> get ds1-profile 1-8-2-0/ds1
line-type: ----------------------> {ds1unframed}
line-code: ----------------------> {b8zs}
send-code: ----------------------> {sendnocode}
circuit-id: ---------------------> {ds1}
loopback-config: ----------------> {noloop}
signal-mode: --------------------> {none}
fdl: ----------------------------> {fdlnone}
dsx-line-length: ----------------> {dsx0}
line-status_change-trap-enable: -> {enabled}
channelization: -----------------> {disabled}
ds1-mode: -----------------------> {csu}
csu-line-length: ----------------> {csu00}
clock-source-eligible: ----------> {eligible}
transmit-clock-source: ----------> {throughtiming}
cell-scramble: ------------------> {true}
coset-polynomial: ---------------> {true}
protocol-emulation: -------------> {network}
signal-type: --------------------> {loopstart}
ds1-group-number: ---------------> {0}
line-power: ---------------------> {disabled}

5 Display the ces-config profile for the configured T1/E1 CES unstructured
circuit.
zSH> get ces-config 1-8-2-0-ds1-1/ds0bundle
vpi: --------------------------> {1}
vci: --------------------------> {33}
cas: --------------------------> {basic}
partial-fill: -----------------> {0}
buf-max-size: -----------------> {128}
cell-loss-integration-period: -> {2500}
ds0-bundle: ------------------->
{1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+21
+22+23+24}
source-ip-address: ------------> {10.2.4.82}
destination-ip-address: -------> {10.2.4.83}
source-port: ------------------> {140}
destination-port: -------------> {141}

Adding a structured T1/E1 CES over IP circuit with

ds1esfcas signaling
To add a CES cross connection for a structured T1/E1 CES circuit with esfcas
signaling, repeat these configuration steps for each endpoint of the circuit.
1 Specify cross connect command with the desired settings for each side of
the CES circuit. This example command creates a structured T1 circuit
using 6 DS0s starting at DS0 1 with ds1esfcas signaling. No line type is
specified so the default esf line type from the DS1-profile is used. Traffic

MALC Configuration Guide 181

Adding Voice Connections

descriptor 1 is used. Using slot 7, port 1 on the CES card, the source IP
address is 192.168.11.101. The destination IP address is 192.168.12.102.
The source UDP port number is 140. The destination UDP port number is
141.

Note: Ensure the IP routes between the source and destination

subnetworks have been configured and are available.

zSH> ces add 1-7-1-0-ds1/atm ds0 1/6 struct ds1esfcas td 1 llc static
192.168.11.101 192.168.100.12 140 141
zSH> ces add 1-7-2-0-ds1/atm ds0 1/6 struct ds1esfcas td 1 llc static
192.168.12.102 192.168.11.101 141 140

2 Change the admin status of the ports to up:

zSH> update if-translate 1-7-1-0/ds1
Please provide the following: [q]uit.
ifIndex: -----------> {200}:
shelf: -------------> {1}:
slot: --------------> {7}:
port: --------------> {1}:
subport: -----------> {0}:
type: --------------> {ds1}:
adminstatus: -------> {down}: up
physical-flag: -----> {true}:
iftype-extension: --> {none}:
ifName: ------------> {1-7-1-0}:
redundancy-param1: -> {0}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

zSH> update if-translate 1-7-2-0/ds1

Please provide the following: [q]uit.
ifIndex: -----------> {200}:
shelf: -------------> {1}:
slot: --------------> {7}:
port: --------------> {1}:
subport: -----------> {0}:
type: --------------> {ds1}:
adminstatus: -------> {down}: up
physical-flag: -----> {true}:
iftype-extension: --> {none}:
ifName: ------------> {1-7-1-0}:
redundancy-param1: -> {0}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.zSH>

3 Display the configured cross connections.

zSH> cc show CES
CONNECTION CC CONNECTION

182 MALC Configuration Guide

 Configuring CES connections

---------------------------------------------------------------------------
1-1-1-0-aal5proxy/atm 0/35 Up 1 Up 1-7-1-0/ds1 1/6 Up
1-1-1-0-aal5proxy/atm 0/36 Up 2 Up 1-7-2-0/ds1 1/6 Up

4 Display the DS1 profile for the configured structured CES circuit over IP.
zSH> get ds1-profile 1-7-1-0/ds1
line-type: ----------------------> {esf}
line-code: ----------------------> {b8zs}
send-code: ----------------------> {sendnocode}
circuit-id: ---------------------> {ds1}
loopback-config: ----------------> {noloop}
signal-mode: --------------------> {robbedbit}
fdl: ----------------------------> {fdlnone}
dsx-line-length: ----------------> {dsx0}
line-status_change-trap-enable: -> {enabled}
channelization: -----------------> {disabled}
ds1-mode: -----------------------> {csu}
csu-line-length: ----------------> {csu00}
clock-source-eligible: ----------> {eligible}
transmit-clock-source: ----------> {throughtiming}
cell-scramble: ------------------> {true}
coset-polynomial: ---------------> {true}
protocol-emulation: -------------> {network}
signal-type: --------------------> {loopstart}
ds1-group-number: ---------------> {0}
line-power: ---------------------> {disabled}

5 Display the ces-config profile for the configured structured CES circuit
over IP.
zSH> get ces-config 1-7-1-0-ds1-1/ds0bundle
vpi: --------------------------> {1}
vci: --------------------------> {35}
cas: --------------------------> {ds1esfcas}
partial-fill: -----------------> {0}
buf-max-size: -----------------> {128}
cell-loss-integration-period: -> {2500}
ds0-bundle: -------------------> {1+2+3+4+5+6}
source-ip-address: ------------> {10.2.4.82}
source-port: ------------------> {140}
destination-ip-address: -------> {10.2.4.83}
destination-port: -------------> {141}

Deleting cross connections and CES over ATM circuits

To delete a configured CES over ATM cross connection, specify the delete
cross connect command.
This command uses either both sides of the cross connect or the cross
connect number to remove the entire cross connection. Repeat this
command on each circuit endpoint.
zSH> cc delete uplink2/atm 0/61 1-6-1-0-ds1/atm 1/32

MALC Configuration Guide 183

Adding Voice Connections

Delete complete

zSH> cc delete cc 1
Delete complete

Deleting CES over IP circuits

To delete a configured CES over IP circuit, repeat this command on each
circuit endpoint.
This command deletes only one endpoint of a CES over IP circuit. Repeat
this command on each endpoint to remove the entire circuit.
ZSH>ces delete 1-7-1-0-ds1/atm ds0 1/6 static
192.168.100.101

Additional VOIP features

This section describes the configurable VOIP features for VOIP-enabled
services.
• Setting VOIP features on page 184
• Changing the hookflash timer values on page 185
• Configuring always offhook on page 186
• Configuring huntgroups on page 187
• SIP dialing plans on page 191
• Malicious caller on page 193

Setting VOIP features

To configure VOIP features:
zSH> update subscriber-voice 1/2/1
Please provide the following: [q]uit.
voice-connection-type: --------> {voiptopots}: **
read-only **
voice-endpoint1-addr-index: ---> {1}: ** read-only **
voice-endpoint2-addr-index: ---> {1001}: **
read-only **
voice-connection-description: -> {}:
voice-admin-status: -----------> {enabled}:
huntgroup: --------------------> {false}: **
read-only **
features: --------------------->
{hookflash+onhooksignaling}: hookflash.
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

184 MALC Configuration Guide

 Additional VOIP features

Changing the hookflash timer values

The hookflash timer values can be configured to a specified range between
minimum and maximum values. If hookflash is enabled on a VOIP
subscriber, a hookflash is considered only if the onhook time is between the
minimum and maximum timer values. Any time less than the minimum time
setting is ignored and any time more than the maximum time setting is
considered to be onhook.
Modify the following parameters in the subscriber-voice profile to change
hookflash timer settings.

Parameter Description

hookFlashTimerMin Specifies the minimum hookflash

timer value in milliseconds.
Values:
0 to 2147483647
Default: 100 milliseconds

hookFlashTimerMax Specifies the maximum hookflash

timer value in milliseconds.
Values:
0 to 2147483647
Default: 1550 milliseconds

To change the hookflash timer values:

zSH> update voice-system 0
Please provide the following: [q]uit.
hookflash-max-timer: -> {1550}: 2000
hookflash-min-timer: -> {100}: 500
partial-dial-timeout: ------> {16}:
critical-dial-timeout: -----> {4}:
busy-tone-timeout: ---------> {30}:
dial-tone-timeout: ---------> {16}:
msg-wait-tone-timeout: -----> {16}:
offhook-warn-tone-timeout: -> {0}:
ringing-timeout: -----------> {180}:
ringback-timeout: ----------> {180}:
reorder-tone-timeout: ------> {30}:
stutter-tone-timeout: ------> {16}:
server-max-timer: ----------> {20}:
config-max1: ---------------> {5}:
config-max2: ---------------> {7}:
max1-enable: ---------------> {true}:
max2-enable: ---------------> {true}:
max-waiting-delay: ---------> {600}:
disconnection-wait-timer: --> {15}:
disconnection-min-timer: ---> {15}:
disconnection-max-timer: ---> {600}:
max-retransmit-timer: ------> {4}:
init-retransmit-timer: -----> {200}:

MALC Configuration Guide 185

Adding Voice Connections

keep-alive-timer: ----------> {60}:

no-response-timer: ---------> {30}:
call-wait-max-repeat: ------> {2}:
call-wait-delay: -----------> {10}:
pulse-inter-digit-timer: ---> {100}:
min-make-pulse-width: ------> {25}:
max-make-pulse-width: ------> {55}:
min-break-pulse-width: -----> {45}:
max-break-pulse-width: -----> {75}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

Configuring always offhook

Some subscribers require circuits to remain permanently offhook to enable
VOIP services such as two-way radio. Provision always offhook for MALC
E&M TO subscribers to enable receiving two-way radio calls. Any incoming
calls to this subscriber will be established right away.

Note: After setting always offhook, users cannot make outgoing

calls.

Modify the following parameter to configure always offhook:

Parameter Description

features Shows the set of VOIP features that are

enabled for the subscriber.
Hookflash is supported only on VOIP SIP
POTS subscribers. Onhook is supported
on all VOIP subscribers. Always offhook
is supported on FXS and E&M
(Z-Edge 6200) subscribers.
Values:
hookflash hookflash detection.
onhooksignaling onhook signaling.
alwaysoffhook call is established as
soon as incoming call initiation is made.
Default: hookflash+onhooksignaling
Options:
+ This parameter allows multiple settings
by using the + option.

1 Disable the subscriber and set always offhook:

zSH> update subscriber-voice 1/2/1
Please provide the following: [q]uit.
voice-connection-type: --------> {voiptopots}: ** read-only **
voice-endpoint1-addr-index: ---> {1}: ** read-only **
voice-endpoint2-addr-index: ---> {1001}: ** read-only **

186 MALC Configuration Guide

 Additional VOIP features

voice-connection-description: -> {}:

voice-admin-status: -----------> {enabled}: disabled
huntgroup: --------------------> {false}: ** read-only **
features: ---------------------> {hookflash+onhooksignaling}:
hookflash+onhooksignaling+alwaysoffhook
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

2 Re-enable the subscriber

zSH> update subscriber-voice 1/2/1
Please provide the following: [q]uit.
voice-connection-type: --------> {voiptopots}: ** read-only **
voice-endpoint1-addr-index: ---> {1}: ** read-only **
voice-endpoint2-addr-index: ---> {1001}: ** read-only **
voice-connection-description: -> {}:
voice-admin-status: -----------> {disabled}: enabled
huntgroup: --------------------> {false}: ** read-only **
features: --------------------->
{hookflash+onhooksignaling+alwaysoffhook}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
Record updated.

Configuring huntgroups

Huntgroups are used to specify a group of people to receive incoming calls

and determine which phone within that group will ring when a call comes in.
For example, a company’s technical support phone number is 555-8000 and
there are three members of the technical support team. Each one of the
technical support members has a separate phone number, which is not
555-8000. With huntgroups, incoming calls to 555-8000 are directed to one of
the technical support team.
When a call comes in on 555-8000, calls will be placed on E&M ports 1, 2, or
3 in a round-robin fashion: The first time a call comes in, the phone on port 1
will ring; the second time a call comes in, the phone on port 2 will ring; the
third time a call comes in, the phone on port 3 will ring, and fourth time a call
comes in, the phone on port 1 will ring again. Each subscriber can belong to
three huntgroups.

MALC Configuration Guide 187

Adding Voice Connections

Modify the huntgroup parameter in the subscriber-voice profile to enable

huntgroups:

Parameter Description

huntgroup Can be set to true only if the

voice-connection-type is siptopots or
siptods1. If it is set to true only
subscriber-voice-endpt1 gets
automatically created, but not
subscriber-voice-endpt2.
Values:
true
false
Default: false

Modify the following parameters in the subscriber-voice-pots profile to

enable huntgroups:

Parameter Description

hunt-group-index-1 The subscriber is part of this

huntgroup. The hunt group endpoint
index is derived from the
voice-endpoint2-addr-index of the
subscriber-voice connection which
has huntgroup set to true.

hunt-group-index-2 The subscriber is part of this

huntgroup. The hunt group endpoint
index is derived from the
voice-endpoint2-addr-index of the
subscriber-voice connection which
has huntgroup set to true.

hunt-group-index-3 The subscriber is part of this

huntgroup. The hunt group endpoint
index is derived from the
voice-endpoint2-addr-index of the
subscriber-voice connection which
has huntgroup set to true.

Modify the following parameters in the subscriber-voice-voip profile to

enable huntgroups:

Parameter Description

sip-uri A uniform resource identifier (URI)

which acts as a unique SIP identity for
the subscriber.

188 MALC Configuration Guide

 Additional VOIP features

Parameter Description

directory-number1 The phone number assigned to this

endpoint.
ip-interface-index Index of the interface through which
the SIP signalling and real time
protocol (RTP) traffic will flow.

Creating huntgroups on already existing subscribers built

with no huntgroups
To enable huntgroups on already-existing subscribers that do not have
huntgroups:
1 Create a subscriber-voice profile which can support huntgroups:
zSH> new subscriber-voice 1/132/1 subId/lineGroupId/subVoiceId
Please provide the following: (q=quit)
voice-connection-type: ---------->[NONE(0)]: siptopots
voice-endpoint1-addr-index: ----->[0]: 1 index for the subscriber-voice-voip profile
voice-endpoint2-addr-index: ----->[0]: 99 index for the huntgroup
voice-connection-description: --->[]:
voice-admin-status: ------------->[disabled]:
huntgroup:--------------------> [false]: true
.......................
Save new record? (s=save/c=change/q=quit): s
New record saved.

After creating the subscriber-voice-profile with the huntgroup

parameter set to true, the system automatically creates the associated
subscriber-voice-voip profile.
2 Update the SIP voice endpoint:
zSH> update subscriber-voice-voip 1
Please provide the following: [q]uit.
sip-uri: ------------> {}: support
directory-number: ---> {}: 5558000
ip-interface-index: -> {0/0/0/0/0}: 1/1/1/0/ip
preferred-code: -----> {g711mu}:
g711-fallback: ------> {true}:
frames-per-packet: --> {4}:
g726-byte-order: ----> {bigendian}:
sip-password: -------> {}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

3 Update one of the pre-existing subscriber-voice-pots profiles:

zSH> update subscriber-voice-pots 2
Please provide the following: [q]uit.
voice-pots-line-group-id: -> {2}
hunt-group-index-1: -------> {} 99 matches the voice-endpoint2-addr-index from subscriber-voice profile

MALC Configuration Guide 189

Adding Voice Connections

hunt-group-index-2: -------> {0}

hunt-group-index-3: -------> {0}
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

Creating subscribers built with pre-existing huntgroups

To enable huntgroups on already-existing subscribers that already have
huntgroups created in the subscriber-voice-pots profile:
1 Find the huntgroup index from the pre-existing subscriber-voice-pots
profile.
After creating the subscriber-voice-profile with the huntgroup
parameter is set to true, the system automatically creates the associated
subscriber-voice-voip profile.
2 Update the SIP voice endpoint:
zSH> update subscriber-voice-voip 2
Please provide the following: [q]uit.
sip-uri: ------------> {}: support
directory-number: ---> {}: 5558000
ip-interface-index: -> {0/0/0/0/0}: 1/1/1/0/ip
preferred-code: -----> {g711mu}:
g711-fallback: ------> {true}:
frames-per-packet: --> {4}:
g726-byte-order: ----> {bigendian}:
sip-password: -------> {}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

Creating new subscribers with huntgroups enabled

To create new subscribers with huntgroups enabled:
Create a subscriber-voice profile which can support huntgroups:
After creating the subscriber-voice-profile with the huntgroup parameter set
to true, the system automatically creates the associated
subscriber-voice-voip profile.
1 Update the SIP voice endpoint:
zSH> update subscriber-voice-voip 3
Please provide the following: [q]uit.
sip-uri: ------------> {}: support3
directory-number: ---> {}: 5559000
ip-interface-index: -> {0/0/0/0/0}: 1/1/1/0/ip
preferred-code: -----> {g711mu}:
g711-fallback: ------> {true}:
frames-per-packet: --> {4}:
g726-byte-order: ----> {bigendian}:
sip-password: -------> {}:

190 MALC Configuration Guide

 Additional VOIP features

....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

2 Create a subscriber-voice profile without huntgroups:

zSH> new subscriber-voice 1/132/99
Please provide the following: (q=quit)
voice-connection-type: ---------->{aal2togr303}: siptopots
voice-endpoint1-addr-index: ----->{0}: 8 index for the subscriber-voice-voip profile
voice-endpoint2-addr-index: ----->{0}: 9 index for the subscriber-voice-pots profile
voice-connection-description: --->{}:
voice-admin-status: ------------->{disabled}:
huntgroup:--------------------> {false}:
.......................
Save new record? (s=save/c=change/q=quit): s
New record saved.

3 Update the subscriber-voice-voip profile:

zSH> update subscriber-voice-voip 9
Please provide the following: [q]uit.
sip-uri: ------------> {}: johnsmith
directory-number: ---> {}: 5559999
ip-interface-index: -> {0/0/0/0/0}: 1/1/1/0/ip
preferred-code: -----> {g711mu}:
g711-fallback: ------> {true}:
frames-per-packet: --> {4}:
g726-byte-order: ----> {bigendian}:
sip-password: -------> {}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

4 Update the subscriber-voice-pots profile to match the huntgroup created:

zSH> update subscriber-voice-pots 9
Please provide the following: [q]uit.
voice-pots-line-group-id: -> {9}
hunt-group-index-1: -------> {} 88 matches the voice-endpoint2-addr-index from subscriber-voice profile
hunt-group-index-2: -------> {0}
hunt-group-index-3: -------> {0}
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

SIP dialing plans

A dialing plan for POTS-to-SIP outgoing calls consists of a series of

acceptable dial strings and the corresponding IP addresses to which SIP
control messages are sent to initiate the call.
Each dial string is represented as digits, wildcards, and
regular-expression-like patterns according to the following rules:

MALC Configuration Guide 191

Adding Voice Connections

• Digits 0 to 9 are allowed.

• A wildcard ? represents any digit 0 to 9
• A digit range can be specified using brackets [ ], as follows:
[135] means digits 1, 3, or 5.
[1-4] means digits 1, 2, 3, or 4.
Create a sip-dialplan profile for outgoing VOIP calls by modifying the
following parameters:

Parameter Description

match-string A dial string against which collected

digits are matched.

sip-ip-address Upon detecting a match between the

collected digits and the dial string, this
IP address is used for SIP negotiations
to initiate the call.

destination -name User-specified name of the destination

for the dial string.
number-of-digits Number of digits to wait for before
initiating the call.

prefix-strip Number of prefix digits to strip from

dialled digits.

prefix-add String to be added to the beginning of

the dialled digits before call initiation.

dialplan-type Type of the dial plan. Dialplan types

are:
• Normal
• Call Park

voip-server-entry-index An index to associated

voip-server-entry for this sip-dialplan.
This index references the registration
server specified in the
voip-server-entry profile.

zSH> new sip-dialplan 1

Please provide the following: [q]uit.
match-string: ------------> {}: 510555101[1-9]
sip-ip-address: ----------> {0.0.0.0}: 192.16.88.199
destination-name: --------> {}: caller
number-of-digits: --------> {0}: 10
prefix-strip: ------------> {0}: 1
prefix-add: --------------> {}: 0
dialplan-type: -----------> {normal}:
voip-server-entry-index: -> {0}: 1
....................
Save new record? [s]ave, [c]hange or [q]uit: s

192 MALC Configuration Guide

 Additional voice features

Record created.

Malicious caller

The malicious caller feature enables you to configure caller uniform resource
identifiers (URIs) so that incoming calls with the configured URIs will be
rejected.
The URI can be configured as either a telephone number (RFC 2806) or an
alphanumeric identification (RFC 2806). URI entries are case sensitive,
should not contain visual separations and must be the exact length as they
appear in incoming session notification’s (SIP INVITE) calling user’s
address-of-record (AOR).

Specifying a malicious caller

Configure malicious caller URIs in the malicious-caller profile. The
following parameters are supported in this profile:

Parameter Description

malicious-caller-uri The URI for which incoming calls will be

rejected. The network operator is responsible
for provisioning the URI exactly as per
appearance in the incoming session
notification (SIP INVITE) the calling user's
address-of-record (AOR) formatted as a SIP
URI.

reject-enabled Enables and disables the rejection of calls

matching the configured malicious caller
URI.
Default: true

To specify a malicious caller:

Create a new malicious-caller profile to reject a particular caller:
zSH> new malicious-caller 1
Please provide the following: [q]uit.
malicious-caller-uri: -> {}: [email protected]
reject-enabled: -------> {true}:
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

Additional voice features

This section describes additional voice settings you might need to configure,
depending on your network.

MALC Configuration Guide 193

Adding Voice Connections

Changing the jitter buffer

The type and size of the jitter buffer in the MALC can be configured. The
jitter buffer accommodates the AAL2 packets received, so that the
inter-arrival jitter of the packets received does not degrade the voice quality.
Without a jitter buffer, some inter-arrival jitter changes would be late, which
would have the same effect as lost packets. The jitter buffer also reorders the
out-of-order packets received.
Modify the following parameters in the voice-dsp-default-profile to change
jitter buffer:

Parameter Description

jitter-buffer-type There are two types of jitter

algorithms: static and dynamic.
Values:
static A static jitter buffer does not
change to compensate for inter-arrival
jitter changes. Default jitter buffer type
is static for VoATM applications.
dynamic Allows the jitter buffer to
grow and shrink as inter-arrival jitter
changes. Default jitter buffer type is
dynamic for VOIP applications.

jitter-buffer-size Specifies the size of the jitter buffer.

Values:
1 to 160 Note that changes to the
jitter buffer are based on 5 ms frame
sizes. For example:
1 to 5 = 5 ms
6 to 10 = 10 ms
11 to 15 = 15 ms
16 to 20 = 20 ms
...
146 to 150 = 150 ms
151 to 155 = 155 ms
156 to 160 = 160 ms
Default: 10

Note: Any changes made to jitter buffer size and jitter buffer type
take effect in the next call.

To change the type and size of the jitter buffer:

zSH> update voice-dsp-default-profile 0
Please provide the following: [q]uit.
redundancy-over-subscription-type: -> {high}:
jitter-buffer-type: ----------------> {dynamic}: static

194 MALC Configuration Guide

 Additional voice features

jitter-buffer-size:----------------> {10}: 22
inter-arriv-jit-threshold: ---------> {80}:
pkts-lost-threshold: ---------------> {600}:
echo-cancellation-type: ------------> {g165echotl16}:
silence-supression-type: -----------> {silsupoff}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

Setting South Africa dialing features

Certain features on the ULC card are designed for use in South African
telephone systems. These features are available on the ULC card. For more
information about this card, contact your Zhone Technologies sales
representative.

Caution: Changing the countryregion setting for the ULC card

requires a system reboot.

When you specify South Africa in the system profile, you have the option
of modifying the following dialing parameters in the voice-system
profile:
– hookflash-min-timer
– hookflash-max-timer
– pulse-inter-digit-timer
– min-make-pulse-width
– min-break-pulse-width
– max-break-pulse-width
These options are read only after they have been set.
To specify South Africa in the system profile:
zSH> update system 0
Please provide the following: [q]uit.
syscontact: -----------> {Zhone Global Services and Support 7001 Oakport
Street Oakland Ca. (877) Zhone20 (946-6320) Fax (510)777-7113
[email protected]}:
sysname: --------------> {malc-201}:
syslocation: ----------> {Oakland}:
enableauthtraps: ------> {disabled}:
setserialno: ----------> {0}:
zmsexists: ------------> {true}:
zmsconnectionstatus: --> {inactive}:
zmsipaddress: ---------> {192.168.89.12}:
configsyncexists: -----> {false}:
configsyncoverflow: ---> {false}:
configsyncpriority: ---> {high}:
configsyncaction: -----> {noaction}:
configsyncfilename: ---> {192.168.175.201_4_1115314335218}:
configsyncstatus: -----> {synccomplete}:

MALC Configuration Guide 195

Adding Voice Connections

configsyncuser: -------> {zmsftp}:

configsyncpasswd: -----> {** private **}: ** read-only **
numshelves: -----------> {1}:
shelvesarray: ---------> {}:
numcards: -------------> {3}:
ipaddress: ------------> {192.168.175.201}:
alternateipaddress: ---> {0.0.0.0}:
countryregion: --------> {us}: southafrica
primaryclocksource: ---> {0/0/0/0/0}:
ringsource: -----------> {internalringsourcelabel}:
revertiveclocksource: -> {true}:
voicebandwidthcheck: --> {false}:
....................
countryregion changed to southafrica
Load country's pulse dialing parameters in voice-system profile ? [y]es or
[n]o: y
voice-system profile updated with pulse dialing parameters for southafrica
sysMinBreakPulseWidth... 35 ms, sysMaxBreakPulseWidth... 75 ms
sysMinMakePulseWidth.... 100 ms, sysPulseInterDigitTimer. 25 ms
minHookFlash............ 80 ms, maxHookFlash............ 230 ms
southafrica uses a different PCM encoding type (ALAW) from us (MULAW).
Please reboot the system for this change to take effect.
Record updated.

Setting ring cadence and call progress parameters

The MALC enables the ring cadence and other call progress parameters to be
customized for VOIP MGCP and SIP calls.
The following call progress parameters can be set:
• callerid-dig-protocol
This object identifies the subscriber line protocol used for signaling
on-hook caller id information. Supported protocols are Frequency Shift
Keying (FSK) and Dual-Tone Multi-Frequency (DTMF).
• r0-ring-cadence to r7-ring-cadence
Customized ring cadences.
• ring cadence
Normal ring cadence
• clid-mode
The method of caller ID for on-hook caller ID.
• delay-before-clid-after-ring
The delay between the first ringing pattern and the start of the
transmission of the FSK containing the Caller ID information.
To customize ring cadence or change call progress parameters:
zSH> update voice-call-progress-config 0
Please provide the following: [q]uit.

196 MALC Configuration Guide

 Additional voice features

callerid-sig-protocol: -----------> {fsk}: dtml

r0-ring-cadence: -----------------> {r-2000:on-4000:off}:
r1-ring-cadence: -----------------> {r-2000:on-4000:off}:
r2-ring-cadence: -----------------> {r-800:on-400:off-800:on-4000:off}:
r3-ring-cadence: ----------------->
{r-400:on-200:off-400:on-200:off-800:on-4000:off}:
r4-ring-cadence: ----------------->
{r-300:on-200:off-1000:on-200:off-300:on-4000:off}:
r5-ring-cadence: -----------------> {nr-500:on}:
r6-ring-cadence: -----------------> {r-2000:on-4000:off}:
r7-ring-cadence: -----------------> {r-2000:on-4000:off}:
ring-cadence: --------------------> {r-2000:on-4000:off}:
ring-splash-cadence: -------------> {nr-500:on}:
power-ring-frequency: ------------> {f20hz}:
clid-mode: -----------------------> {duringringingets}:
delay-before-clid-after-ring: ----> {550}:
delay-before-clid-after-dtas: ----> {50}:
delay-before-clid-after-rpas: ----> {650}:
delay-after-clid-before-ring: ----> {250}:
delay-before-dtas-after-lr: ------> {250}:
vmwi-mode: -----------------------> {dtasets}:
delay-before-vmwi-after-dtas: ----> {50}:
delay-before-Vmwi-after-rpas: ----> {650}:
vmwi-delay-before-dtas-after-lr: -> {250}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

MALC Configuration Guide 197

Adding Voice Connections

198 MALC Configuration Guide

8
VOICE GATEWAY CONNECTIONS

This chapter describes how to configure the MALC voice gateway. It

includes:
• Overview, page 199
• Configuring voice gateway connections, page 200

Overview
The MALC voice gateway card (VG-T1/E1-32-2S) enables voice connections
from an ATM and IP voice network to a TDM local exchange switch using
GR-303 or V5.2 protocols. The following connection types are supported.
• Voice over ATM:
– BLES to GR-303 or V5.2
– ELCP to V5.2
• Voice over IP: SIP-PLAR to GR-303 or V5.2

Figure 21: Voice gateway overview

TDM

GR303

V5.2
Local Exchange
Switch
Packet MALC with
voice gateway

The MALC voice gateway card can also serve as an aggregation point for
multiple downstream MALC or IAD systems aggregating multiple services
(PON, SHDSL, T1/E1 ATM) or multiple voice lines on residential services
(ADSL, ADSL2+, VDSL) over a single uplink connection.

MALC Configuration Guide 199

Voice Gateway Connections

All the ATM/IP uplink cards can be used to connect VOIP traffic to the voice
gateway card.

Figure 22: Voice gateway aggregation point

IAD

IP Network

MALC with Local Exchange

voice gateway Switch

Configuring voice gateway connections

The voice gateway card configuration involves validating voice configuration
prerequisites, configuring the voice VPIs and VCIs as required, and adding
the desired voice connections. Procedures for verifying the voice connections
are also provided.
These configuration procedures require the MALC uplink and voice gateway
cards to be physically installed and running in the current system with
properly configured card profiles.

Note: The voice gateway card requires MALC software version

1.11.1 or higher on the uplink cards.

This section contains procedures for:

• Verifying voice configuration prerequisites on page 200
• VOIP to voice gateway connections on page 201
• Subtended MALC POTS VOIP voice gateway connections on page 205
• AAL2 voice gateway connections on page 208
• Subtended MALC ISDN or POTS voice gateway connections on page 217

Verifying voice configuration prerequisites

Before configuring the voice gateway connection, use the following
procedures to ensure that the configuration prerequisites have been
configured.

200 MALC Configuration Guide

 Configuring voice gateway connections

1 Use the slots command to verify the desired uplink and voice gateway
card installation and status. This example shows the Uplink-T1/E1-ATM/
TDM/IP-16 card running in slot 1 and the MALC voice gateway card
running in slot 3. Other line cards can be inserted and running in other
slots as desired.
zSH> slots
1: MALC UPLINK T1/E1 TDMF (RUNNING)
3: MALC T1E132VG (RUNNING)
13: MALC GSHDSL (RUNNING)
17: MALC ADSL + POTS AC6 (RUNNING)

2 Check the system settings to ensure the appropriate country coding and
other system-level settings are configured. See Updating system settings
on page 156 for details.
3 Create and activate a V5.2 or GR-303 interface group (IG). See
Provisioning GR-303 or V5.2 Interface Groups on page 137 for details.

Note: Up to 8 interface groups can be supported on each voice

gateway card.

4 Ensure there is an active system clock source. See the MALC Hardware
Installation Guide.
5 Create a new atm-traf-descr with a unique index for a voice connection.
For ELCP to V5.2 voice connections, both the VPL and VCL traffic
descriptors are required. See MALC ATM overview on page 21 for more
information on ATM traffic descriptors and parameters.
zSH> new atm-traf-descr 1 index can be any value
Please provide the following: [q]uit.
td_type: -----------------> {atmNoClpNoScr}: atmClpNoTaggingScrCdvt
td_param1: ---------------> {0}: 4826 PCR .
td_param2: ---------------> {0}: 4825 SCR
td_param3: ---------------> {0}: 20 MBS
td_param4: ---------------> {0}: 15000 CDVT
td_param5: ---------------> {0}:
cac-divider: -------------> {1}: 10
td_service_category: -----> {ubr}: rtvbr for voice
td_frame_discard: --------> {false}:
usage-parameter-control: -> {true}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

VOIP to voice gateway connections

This section contains the following procedures:

• Overview on page 202
• Creating an unnumbered interface for VOIP on page 202

MALC Configuration Guide 201

Voice Gateway Connections

• Configuring voice gateway host for VOIP connections

• Configuring voice connections for VOIP to GR303
• Configuring voice connections for VOIP to V5.2
• Deleting voice gateway host and voice connection

Overview
For VOIP to TDM voice connections, the MALC voice gateway card supports
multiple incoming VOIP voice lines going out a single TDM connection to a
local voice switch.

Figure 23: Voice gateway VOIP to TDM

IP Network

MALC with Local Exchange

voice gateway Switch

For VOIP to TDM connections on the voice gateway card, VOIP packets
destined for the voice gateway card enter through one of the MALC uplink
card interfaces (GigE, SONET, IP) and are terminated on the voice gateway
card. The voice signal is converted to TDM T1/E1 channels and sent to the
local switch for TDM voice processing. For traffic coming from the local
switch, the TDM voice signals are converted to VOIP packets by the voice
gateway card and routed back out the MALC uplink card to the configured
VOIP destination.
Configuring a VOIP to TDM voice gateway connection involves configuring
the voice gateway for a VOIP host and adding a VOIP to TDM voice
connection.

Note: Only one IP interface can be configured on the voice gateway

card.

Creating an unnumbered interface for VOIP

Before configuring a VOIP to TDM connection, create a new
ip-interface-record and unnumbered interface.
1 To create an IP interface record, use the new ip-interface-record
command.
zSH> new ip-interface-record vg/ip

202 MALC Configuration Guide

 Configuring voice gateway connections

vpi: ---------------> {0}:

vci: ---------------> {0}:
rdindex: -----------> {1}:
dhcp: --------------> {none}: ** read-only **
addr: --------------> {0.0.0.0}: 10.10.10.1
netmask: -----------> {0.0.0.0}: 255.255.255.0
bcastaddr: ---------> {0.0.0.0}: 10.10.10.255
destaddr: ----------> {0.0.0.0}:
farendaddr: --------> {0.0.0.0}:
mru: ---------------> {1500}:
reasmmaxsize: ------> {0}:
ingressfiltername: -> {}:
egressfiltername: --> {}:
pointtopoint: ------> {no}:
mcastenabled: ------> {yes}:
ipfwdenabled: ------> {yes}:
mcastfwdenabled: ---> {yes}:
natenabled: --------> {no}:
bcastenabled: ------> {yes}:
ingressfilterid: ---> {0}:
egressfilterid: ----> {0}:
ipaddrdynamic: -----> {static}:
dhcpserverenable: --> {false}:
subnetgroup: -------> {0}:
unnumberedindex: ---> {0}:
mcastcontrollist: --> {}:
vlanid: ------------> {0}:
maxVideoStreams: ---> {0}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
Could not find an appropropriate interface on which to
bind the IP record.

Could not automatically bind this IP Interface

New record saved.

2 To create an unnumbered IP interface record, use the new

ip-unnumbered-record command.
zSH> new ip-unnumbered-record 1
ipUnnumberedInterfaceName: -> { }: vg/ip
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Configuring voice gateway host for VOIP connections

The voice gateway VOIP to GR-303 and V5.2 configurations require
configuring the voice gateway as an AAL5 proxy on the voice gateway card
before adding a VOIP to GR-303 or VOIP to V5.2 voice connection.
1 Locate the if-translate record.
zSH> list if-translate 1-3-1-0/aal5proxy

MALC Configuration Guide 203

Voice Gateway Connections

if-translate 1-3-1-0/aal5proxy
1 entry found.

2 Verify that the desired ATM traffic descriptor is configured.

zSH> list atm-traf-descr
atm-traf-descr 1
1 entry found.

3 Use the voicegateway add command to create the voice gateway host
using the available physical interface and traffic descriptor.
zSH> voicegateway add 1-3-1-0/aal5proxy td 1
10.10.10.2

This adds an IP host on the voice gateway card in slot 3 and assigns the IP
address 10.10.10.2. The connection uses traffic descriptor 1 and an AAL5
physical interface of aal5proxy.

Note: The voicegateway add command automatically creates

the required ATM VCLs.

4 Use the voicegateway show command to display the voice gateway host.
zSH> voicegateway show 1-3-1-0/aal5proxy
Rd/Address Interface Group T Host Address
-----------------------------------------------------
1 10.10.10.1 1-3-1-0-aal5proxy-0-32 0/32 0 S 10.10.10.2

Configuring voice connections for VOIP to GR303

After configuring the voice gateway as an AAL5 proxy on the voice gateway
card, the voice connection for VOIP to GR-303 requires adding a VOIP to
GR-303 voice connection. This example uses the IP interface voip-1-3/ip
with the number 735-0025, name m143-301, destination IP address
172.24.200.143, GR-303 switch protocol, IG 1 and CRV 25. This command
also sets the VOIP password in the subscriber-voice-voip profile to
password.
1 Use the voice add command to add a VOIP to GR-303 voice connection
between the voice gateway card and the switch.
zSH> voice add voip voip-1-3/ip dn 7350025 name m143-301 plar 172.24.200.143
gr303 1/25 pw password
Created subscriber-voice 1/330/48
Created subscriber-voice-voip 173
Created gr303-ig-crv 1/25
Created subscriber-voice-gr303 174

2 Display the configured voice connection with the voice show command.
ZSH>voice show
Subscriber end-point Remote end-point Voice Prof Id STA
---------------------------- ----------------------------- --------------

204 MALC Configuration Guide

 Configuring voice gateway connections

voip-1-3/ip DN 7350025 GR303 one/25 1/330/25 ENA

Total number of voice connections : 1

Configuring voice connections for VOIP to V5.2

After configuring the voice gateway as an AAL5 proxy on the voice gateway
card, the voice connection VOIP to V5.2 requires adding a VOIP to V5.2
voice connection.
1 Use the voice add command to add a VOIP to V5.2 voice connection
between the voice gateway card and the switch using IG 4 and user port
99.
zSH> voice add voip ethernet1/ip dn 5107777428 name caller pw password v52
4/99 type pots
Created subscriber 1/2
Created subscriber-voice 1/2/1
Created subscriber-voice-voip 11
Created v52-user-port 4/99/2
Created subscriber-voice-v52 12

2 Display the configured voice connection with the voice show command.
zSH> voice show
Subscriber end-point Remote end-point Voice Prof Id STA
------------------------------ ------------------------ -------------- ---
ethernet1/ip DN 5107777428 V52 four/99/pots 1/2/1 ENA

Total number of voice connections : 1

Deleting voice gateway host and voice connection

To remove the configured voice gateway connection, use the voicegateway
delete command.
zSH> voicegateway delete 1-3-1-0/aal5proxy

Deleting voice connection

To remove the configured voice connection, use the voice delete command.
Do not attempt to manually remove or edit the related subscriber-voice
profiles.
zSH> voice delete voip ethernet1/ip DN 5107777428
Deleted v52-user-port 4/99/2
Deleted subscriber-voice 1/2/1 and its
subscriber-voice-xxx profiles

Subtended MALC POTS VOIP voice gateway connections

This section contains the following procedures:

• Overview on page 206

MALC Configuration Guide 205

Voice Gateway Connections

• Configuring subtended POTS to VOIP voice connection on page 207

• Deleting subtended voice connection on page 207

Overview
Using a subtended MALC, with an optional IAD, enables the MALC voice
gateway card to function as an aggregation point for multiple downstream
systems aggregating multiple services (PON, SHDSL, T1/E1 ATM) or
multiple voice lines on residential services (ADSL, ADSL2+, VDSL) over a
single MALC uplink and voice gateway connection.

Figure 24: Voice gateway VOIP to TDM with subtended MALC

IAD

IP Network

MALC with Local Exchange

voice gateway Switch

In a subtended MALC configuration, subscriber traffic passes through the

subtended MALC’s uplink card and is sent as VOIP packets to the MALC
with the voice gateway card. VOIP packets destined for the voice gateway
card enter through one of the MALC uplink card interfaces (GigE, SONET,
IP) and are terminated on the voice gateway card. The voice signal is
converted to TDM T1/E1 channels and sent to the local switch for TDM voice
processing. For traffic coming from the local switch, the TDM voice signals
are converted to VOIP packets by the voice gateway card and routed back out
the MALC’s uplink card, sent to the subtended MALC, and then routed to the
configured VOIP destination.
To configure the voice gateway card with a downstream MALC system, first
ensure the voice gateway card is configured for a VOIP to TDM connection.
See VOIP to voice gateway connections on page 201.
Then, use the voice add command to add a POTS to VOIP voice connection
on the subtended MALC. This voice connection transports the voice signals
between the subtended MALC and the VOIP interface on the voice gateway
card.

206 MALC Configuration Guide

 Configuring voice gateway connections

Configuring subtended POTS to VOIP voice connection

Configure a POTS to VOIP voice connection on the subtended MALC to send
its VOIP signals to the voice gateway card. The subtended MALC must have
a working Ethernet IP connection and an available IP route to the voice
gateway IP address. Also, a subscriber line POTS card should be installed
with the required ports enabled.
1 Create a non-subscriber VCL 0/34 on the MALC uplink card. The VCL 0/
34 is required for internal voice processing and must be configured once
for each uplink card that will connect to a voice connection from a
subtended MALC.
zSH> new atm-vcl 1-1-2-0-dspproxy/atm/0/34
vpi: -----------------------------> {0}
vci: -----------------------------> {34}
admin_status: --------------------> {up}
receive_traffic_descr_index: -----> {1}
transmit_traffic_descr_index: ----> {1}
vcc_aal_type: --------------------> {aal5}
vcc_aal5_cpcs_transmit_sdu_size: -> {9188}
vcc_aal5_cpcs_receive_sdu_size: --> {9188}
vcc_aal5_encaps_type: ------------>
{llcencapsulation}
vcl_cast_type: -------------------> {p2p}
vcl_conn_kind: -------------------> {pvc}
fault-detection-type: ------------> {disabled}
traffic-container-index: ---------> {0}

2 Reboot the MALC.

3 Use the voice add command on the subtended MALC to add the POTS to
VOIP connection. This example connects a POTS subscriber with
interface 1-3-1-0/voicefxs to VOIP interface ethernet1/ip with number
735-0025, name of m143-301, and destination IP address 10.177.1.2.
zSH> voice add pots 1-3-1-0/voicefxs voip ethernet1/ip dn 7350025 name
m143-301 plar 10.177.1.2
Created subscriber-voice 1/2/1
Created subscriber-voice-pots 1004
Created subscriber-voice-voip 1005

4 Verify the voice connection with the voice show command.

zSH> voice show
Subscriber end-point Remote end-point Voice Prof Id STA
------------------------------ ------------------------------ -------------- ---
1-3-1-0/voicefxs ethernet1/ip DN 7350025 1/2/1 ENA
Total number of voice connections : 1

Deleting subtended voice connection

To remove the configured voice connection, use the voice delete command.
zSH> voice delete pots 1-3-1-0/voicefxs

MALC Configuration Guide 207

Voice Gateway Connections

Deleted subscriber-voice 1/2/1 and its

subscriber-voice-xxx profiles

AAL2 voice gateway connections

This section contains the following information:

• Overview on page 208
• Configuring voice gateway for VoATM BLES to GR-303 (VC-switched) on
page 210
• Configuring voice gateway for VoATM BLES to GR303 (VP-switched) on
page 211
• Configuring voice gateway for VoATM BLES to V5.2 (VC-switched) on
page 212
• Configuring voice gateway for VoATM BLES to V5.2 (VP-switched) on
page 213
• Configuring voice gateway for VoATM ELCP to V5.2 (VC-switched)
ISDN signal on page 214
• Configuring voice gateway for VoATM ELCP to V5.2 (VP-switched) on
page 216
• Configuring subtended AAL2 voice connection on page 218

Overview
For VoATM to TDM voice connections, the MALC voice gateway supports
multiple ATM voice lines over the voice gateway card to a local TDM
(GR-303 or V5.2) switch.

Figure 25: Voice gateway VoATM to TDM

ATM

MALC with Local Exchange

voice gateway Switch

For VoATM traffic, ATM traffic destined for the voice gateway card enters
through one of the MALC uplink card’s ATM interfaces and is terminated on
the voice gateway card. The ATM voice signals are converted to TDM T1/E1
channels and sent to the local TDM switch for processing. For traffic coming

208 MALC Configuration Guide

 Configuring voice gateway connections

from the local switch, the TDM voice signals are converted to VoATM signals
by the voice gateway card and sent back out the MALC uplink card to
configured ATM destination.

Note: The voice gateway card does not support connection

admission control (CAC).

All uplink cards can be used for connecting VoATM traffic to the voice
gateway card.
The voice gateway card supports VoATM BLES to GR-303 or V5.2 and
VoATM ELCP to V5.2 connection types.
The MALC voice gateway card enables a combination of VP and VC
switching for flexible VoATM voice gateway configurations and maximum
subscriber support.
• VC-switched
In VC-switching, VCs are switched independently of each other based on
VPI and VCI value. The VP range of 0-7 is reserved for VC-switching on
the voice gateway card. The VCs in each VC-switched VP must start with
32 and can contain any number up to the maximum number of 448 VCs.
The maximum number of VCs that can be allocated to an individual
VC-switched VPI is determined by the zhoneAtmVpiMaxVci parameter
in the atm-vpi profile.
• VP-switched
In VP-switching, VCs are switched collectively in groups or Virtual Paths
(VPs) based on VPI value. The VP range of 16 to 63 is reserved for
VP-switching on the voice gateway card. Up to 48 VPs can be switched
from the MALC uplink card to a voice gateway card. The VCs in each
VP-switched VP must start with 32 and can contain any number up to the
maximum number of 7,680 VCs. The maximum VCI value that can be
allocated to an individual VP-switched VP is determined by the
zhoneAtmMaxVciPerVp parameter in the atm-vpi profile. For example,
if this parameter is set to 1023 for VPI 16, a VC with VPI/VCI 16/1024
will not be allowed even if it is the only VC configured on the voice
gateway card. The sum of this parameter in all VP-switched atm-vpi
profiles on the voice gateway card cannot exceed 7,680.
The voice vpladd command automatically increments the assigned VP
starting at 16.
Figure 26 illustrates the voice gateway support for VC-switching and
VP-switching.

MALC Configuration Guide 209

Voice Gateway Connections

Figure 26: Voice gateway VoATM VP/VC support

VP0-7 (VC Switched)

VC32-x VP0

VC32-x VP ...

VC32-x VP7
Maximum number of VCs in each VC-switched VP is set
Total VCs in VC-switched
VPs is 448. using the atm-vpi profile paramter ZhoneAtmVpiMaxVci.
TDM
VP16-63 (VP Switched)

VC32-x VP16

VC32-x VP ...

VC32-x VP63
Maximum VCI value that can be allocated in each
Total VCs in VP-switched
VP is 7680 VP-switched VP is set using the atm-vpi profile paramter
ZhoneAtmMaxVciPerVp.

Total VCs supported on the

voice gateway card is 8128.

The voice gateway card supports up to 8,128 virtual circuits (VCs). Each VC
represents a single IAD and supports from 1 to 768 physical or logical
telephones.
For VC-switching, configuring the voice gateway AAL2 voice connection
involves using the voicegateway add command to add the required VP, VC,
and AAL2 to GR-303 or V5.2 voice connection on the voice gateway card.
For VP-switching, configuring the voice gateway AAL2 voice connection
involves using the following commands:
• voice addvpi command builds the VPs on the uplink card interface and
voice gateway aal2proxy.
• voice addvpl command builds the VP links and ATM cross connect
• voice add command builds the shared VC and establishes the AAL2 to
GR-303 or V5.2 voice connection on the voice gateway card.

Configuring voice gateway for VoATM BLES to GR-303

(VC-switched)
This procedure explains how to configure a VC-switched VoATM BLES to
GR-303 voice connection on the voice gateway card.
1 Use the voice add command on the voice gateway card to add the voice
connection for the specified VC and CID to the GR-303 IG.
zSH> voice add aal2 1-4-1-0/ds1 vc 0/139 cid 48 gr303
1/131
Created subscriber-voice 1/266/6
Created aal2-cid-profile 340/0/32/48
Created subscriber-voice-aal2 171
Created gr303-ig-crv 1/131

210 MALC Configuration Guide

 Configuring voice gateway connections

Created subscriber-voice-gr303 172

This adds an ATM to GR-303 voice connection with the AAL2 interface
1-4-1-0 and assigns the virtual connection VPI 0, VCI 139 and CID 48.
The TDM connection uses GR-303 protocol and interface group 1 with
CRV 131.
2 Display the ATM to GR-303 voice connection with the voice show
command.
zSH> voice show
Subscriber end-point Remote end-point Voice Prof Id STA
-------------------------- --------------------------- ------------- ---
1-4-1-0/ds1 VC 0/139 CID 48 GR303 one/131 1/266/6 ENA
Total number of voice connections : 1
zSH>

Configuring voice gateway for VoATM BLES to GR303

(VP-switched)
This procedure explains how to configure a VP-switched VoATM BLES to
V5.2 voice connection on the voice gateway card. Use the voice vpiadd and
voice vpladd commands to build the ATM VP between the uplink card VP
and the voice gateway card aal2proxy using the same VC. Then, use the voice
add command to build the VCL on the aal2proxy with the same VC that was
configured on the uplink card. The allowed VP range on aal2proxy is 16 to
63.

Note: In addition to the GR-303 interface group, the required VPL

traffic descriptor and VCL traffic descriptor must be built before
performing this procedure.

1 Use the voice vpiadd command to build the ATM VPI for the uplink card
and the voice gateway card aal2proxy.
zSH> voice vpiadd uplink/atm 0 gr303 1 501
Created atm-vpi 1-3-3-0-aal2proxy/atm/16
Created atm-vpi uplink1/atm/0

This example uses the uplink interface uplink/atm with VP 0. The MALC
uplink cards support up 256 (0-255) VPs. The voice call type is GR-303
with IG 1. The maximum number of VCs allocated for the specified
VP-switched VPI is 512.
2 Reboot the system to install the configured VPIs.
zSH>systemreboot

3 Use the voice vpladd command to build the VPLs and cross connects
between the uplink card and aal2proxy.
zSH>voice vpladd uplink/atm 0 td 1/1 gr303 1
Created atm-vpl 1-3-3-0-aal2proxy/atm/16
Created atm-vpl uplink1/atm/0

MALC Configuration Guide 211

Voice Gateway Connections

Created atm-cc 6

This command builds atm-vpl uplink1/atm/0 on the uplink card using

traffic descriptor tx and rx 1/1 with atm-vpl 1-3-3-0-aal2proxy/atm/16
on the voice gateway card. VP 16 is the first available VP in the allowed
VP range on the voice gateway card.
4 Use the voice add command on the voice gateway card to add the voice
connection for the desired VC and CID to the GR-303 IG.
zSH> voice add atm uplink1/atm vp 0/101 td 1/1 cid 1
alaw gr303 1/1 type pots
Created subscriber-voice 1/51/2
Created aal2-cid 109/16/101/1/1
Created subscriber-voice-aal2 15
Created gr303-cid 1/1/2
Created subscriber-voice-gr303 16

This command creates a POTS to GR-303 voice connection between the

uplink interface uplink1 with VP 0 and VC 101 to the voice gateway card
CID 1 with VP 16 and shared VC 101.
5 Display the ATM to GR-303 voice connection with the voice show
command.
zSH> voice show
Subscriber end-point Remote end-point Voice Prof Id STA
-------------------------- --------------------------- ------------- ---
1-1-1-0/sonet VC 0/101 port 1 GR303 100 100/11/35/1 ENA

Total number of voice connections : 1

zSH>

Configuring voice gateway for VoATM BLES to V5.2

(VC-switched)
This procedure explains how to configure a VC-switched VoATM BLES to
V5.2 voice connection on the voice gateway card.
1 Use the voice add command on the voice gateway card to add the voice
connection for the specified VC and user port to the V5.2 IG.
zSH> voice add aal2 uplink1/atm vc 6/39 td 1/1 cid 16 v52 4/39 type pots
Created subscriber 1/57
Created subscriber-voice 1/57/1
Created atm-vcl uplink1/atm/6/39
Created atm-vcl 1-5-3-0-aal2proxy/atm/0/32
Created atm-cc 2
Created aal2-vcl-profile 1-5-3-0-aal2proxy/atm/0/32
Created aal2-cid-profile 99/0/32/16Created subscriber-voice-aal2 1
Created v52-user-port 4/39/2
Created subscriber-voice-v52 2

212 MALC Configuration Guide

 Configuring voice gateway connections

This adds an ATM to V5.2 voice connection with the uplink1 AAL2
interface and assigns the virtual connection VPI 6, VCI 39 and CID 16.
2 Display the ATM to V5.2 voice connection with the voice show
command.
zSH> voice show
Subscriber end-point Remote end-point Voice Prof Id STA
------------------------------ ------------------------ -------------- ---
1-1-1-0/sonet VC 6/39 CID 16 V52 four/39/pots 1/57/1 ENA

3 Delete the voice connection.

zSH> voice delete aal2 1-1-1-0/sonet VC 6/39 CID 16
Deleted aal2-cid-profile 99/0/32/16
Deleted v52-user-port 4/39/2
Deleted subscriber-voice 1/57/1 and its
subscriber-voice-xxx profiles
Deleted atm-vcl 99/0/32
Deleted atm-vcl 15/6/39
Deleted atm-cc 2

Configuring voice gateway for VoATM BLES to V5.2

(VP-switched)
This procedure explains how to configure a VoATM BLES to V5.2 voice
connection on the voice gateway card. Use the voice vpiadd and voice
vpladd commands to build the ATM VP between the uplink card VP and the
voice gateway card aal2proxy using the same VC. Then, use the voice add
command to build the VCL on the aal2proxy using the same VC that was
configured on the uplink card. The allowed VP range on aal2proxy is 16 to
63.

Note: In addition to the V5.2 interface group, the required VPL

traffic descriptor and VCL traffic descriptor for ELCP lines must be
built before performing this procedure.

1 Use the voice vpi add command to build the ATM VPI for the uplink card
VP and the voice gateway card aal2proxy.
zSH>voice vpiadd uplink/atm 0 v52 1 2000
Created atm-vpi 1-3-3-0-aal2proxy/atm/16
Created atm-vpi uplink1/atm/0

This example uses the uplink interface uplink/atm with VP 0. The MALC
uplink cards support up 256 (0-255) VPs. The voice call type is V5.2 with
IG 1. The maximum VCs allocated to the specified VP-switched VPI is
2048.
2 Reboot the system to install the configured VPIs.
zSH>systemreboot

3 Use the voice vpladd command to build the VPLs and cross connects.

MALC Configuration Guide 213

Voice Gateway Connections

zSH>voice vpladd uplink/atm 0 td 1/1 v52 1

Created atm-vpl 1-3-3-0-aal2proxy/atm/16
Created atm-vpl uplink1/atm/0
Created atm-cc 6

This command builds atm-vpl uplink1/atm/0 on the uplink card using

traffic descriptor 1 and atm-vpl 1-3-3-0-aal2proxy/atm/16 on the voice
gateway card. VP 16 is the first available VP in the allowed VP range on
the voice gateway card.
4 Use the voice add command with the VPL option on the voice gateway
card to add the voice connection for the specified VC and CID/port to the
V5.2 IG.
zSH> voice add atm uplink1/atm vp 0/101 td 1/1 port 1
alaw v52 1/1 type pots
Created subscriber-voice 1/51/2
Created aal2-port-profile 109/16/101/1/1
Created subscriber-voice-elcp-aal2 15
Created v52-user-port 1/1/2
Created subscriber-voice-v52 16

This command creates a voice connection between the uplink interface

uplink1 with VP 0 and VC 101 to the voice gateway card user port 1.
5 Display the ATM ELCP to V5.2 voice connection with the voice show
command.
zSH> voice show
Subscriber end-point Remote end-point Voice Prof Id STA
-------------------------- --------------------------- ------------- ---
1-1-1-0/sonet VC 0/101 port 1 V52 100 100/11/35/1 ENA

Total number of voice connections : 1

Configuring voice gateway for VoATM ELCP to V5.2

(VC-switched) ISDN signal
This procedure explains how to configure an ISDN signal over a VoATM
ELCP to V5.2 voice connection on the voice gateway card.
1 Use the cc add command on the voice gateway card to add the cross
connect for the specified VC and ISDN connection information using IG
4 and user port 41.
zSH> cc add elcp uplink2/atm vc 6/41 td 1/1 port 1 alaw
v52 4/41 type isdn cpath 4

This adds a cross connect between the uplink2 interface and the voice
gateway card using VC 7/111. The voice protocol is V5.2 and the
connection type is ISDN with Cpath 5.
2 Use the voice add command to specific the voice connection.

214 MALC Configuration Guide

 Configuring voice gateway connections

zSH> voice add elcp uplink1/atm vc 6/41 td 1/1 port 1

alaw v52 4/41 type isdn cpath 4
Created subscriber-voice 1/57/2
Created atm-vcl uplink1/atm/6/41
Created atm-vcl 1-5-3-0-aal2proxy/atm/0/32
Created atm-cc 2
Created aal2-vcl-profile 1-5-3-0-aal2proxy/atm/0/32
Created aal2-elcp-port 99/0/32/1/2
Created subscriber-voice-elcp-aal2 3
Created v52-user-port 4/41/3
Created subscriber-voice-v52 4
Created subscriber-voice 1/57/3
Created subscriber-voice-elcp-aal2 5
Created subscriber-voice-v52 6
Created subscriber-voice 1/57/4
Created subscriber-voice-elcp-aal2 7
Created subscriber-voice-v52 8

3 Display the ISDN to V5.2 voice connection with the voice show
command.
zSH> voice show
Subscriber end-point Remote end-point Voice Prof Id STA
------------------------- ----------------------------- ------------ ---
1-1-1-0/sonet VC 6/41 port 1 V52 four/41/isdn 1/57/2 ENA
1-1-1-0/sonet VC 6/41 port 1 V52 four/41/isdn 1/57/3 ENA
1-1-1-0/sonet VC 6/41 port 1 V52 four/41/isdn 1/57/4 ENA
Total number of voice connections : 3

Configuring voice gateway for VoATM ELCP to V5.2

(VC-switched) POTS signal
This procedure explains how to configure an POTS signal over a VoATM
ELCP to V5.2 voice connection on the voice gateway card.
1 Use the cc add command on the voice gateway card to add the cross
connect for the specified VC and POTS connection information. using IG
4 and user port 40.
zSH> cc add elcp uplink2/atm vc 6/40 td 1/1 port 1 alaw
v52 4/40 type pots

This adds a cross connect between the uplink2 interface and the voice
gateway card using VC 7/111. The voice protocol is V5.2 and the
connection type is POTS.
2 Use the voice add command to specific the voice connection.
zSH> voice add elcp uplink1/atm vc 6/40 td 1/1 port 1
alaw v52 4/40 type pots
Created subscriber-voice 1/57/5
Created atm-vcl uplink1/atm/6/40
Created atm-vcl 1-5-3-0-aal2proxy/atm/0/32
Created atm-cc 2

MALC Configuration Guide 215

Voice Gateway Connections

Created aal2-vcl-profile 1-5-3-0-aal2proxy/atm/0/32

Created aal2-elcp-port 99/0/32/1/1
Created subscriber-voice-elcp-aal2 9
Created v52-user-port 4/40/2
Created subscriber-voice-v52 10

3 Display the POTS to V5.2 voice connection with the voice show
command.
zSH> voice show
Subscriber end-point Remote end-point Voice Prof Id STA
------------------------------ ------------------------- -------------- ---
1-1-1-0/sonet VC 6/40 port 1 V52 four/40/pots 1/57/5 ENA
Total number of voice connections : 1

Configuring voice gateway for VoATM ELCP to V5.2

(VP-switched)
This procedure explains how to configure a VoATM ELCP to V5.2 voice
connection on the voice gateway card. Use the voice vpiadd and voice
vpladd commands to build the ATM VP between the uplink card VP and the
voice gateway card aal2proxy using the same VC. Then, use the voice add
command to build the VCL on the aal2proxy using the same VC that was
configured on the uplink card. The allowed VP range on aal2proxy is 16 to
63.

Note: In addition to the V5.2 interface group, the required VPL

traffic descriptor and VCL traffic descriptor for ELCP lines must be
built before performing this procedure.

1 Use the voice vpi add command to build the ATM VPI for the uplink card
VP and the voice gateway card aal2proxy.
zSH>voice vpiadd uplink/atm 0 v52 1 2004
Created atm-vpi 1-3-3-0-aal2proxy/atm/20
Created atm-vpi uplink1/atm/7

This example uses the uplink interface uplink/atm with VP 0. The MALC
uplink cards support up 256 (0-255) VPs. The voice call type is V5.2 with
IG 1. The maximum number of VCs allocated to the specified
VP-switched VPI is 2048.
2 Reboot the system to install the configured VPIs.
zSH>systemreboot

3 Use the voice vpladd command to build the VPLs and cross connects.
zSH>voice vpladd uplink/atm 0 td 1/1 v52 1
Created atm-vpl 1-3-3-0-aal2proxy/atm/20
Created atm-vpl uplink1/atm/7
Created atm-cc 6

216 MALC Configuration Guide

 Configuring voice gateway connections

This command builds atm-vpl uplink1/atm/0 on the uplink card using

traffic descriptor 1/1 and atm-vpl 1-3-3-0-aal2proxy/atm/16 on the voice
gateway card. VP 16 is the first available VP in the allowed VP range on
the voice gateway card.
4 Use the voice add command with the VPL option on the voice gateway
card to add the voice connection for the specified VP/VC, V5.2 IG and
user port.
zSH> voice add elcp uplink1/atm vp 0/101 td 1/1 port 1
alaw v52 1/1 type pots
Created subscriber-voice 1/51/2
Created aal2-elcp-port 109/16/101/1/1
Created subscriber-voice-elcp-aal2 15
Created v52-user-port 1/1/2
Created subscriber-voice-v52 16

5 Display the ATM ELCP to V5.2 voice connection with the voice show
command.
zSH> voice show
Subscriber end-point Remote end-point Voice Prof Id STA
-------------------------- --------------------------- ------------- ---
1-1-1-0/sonet VC 0/101 port 1 V52 100 100/11/35/1 ENA

Total number of voice connections : 1

zSH>

Deleting voice connection

To remove the configured voice connection, use the voice delete command.
zSH> voice delete elcp 1-1-1-0/sonet VC 6/41 port 1
Deleted aal2-elcp-port 99/0/32/12
Deleted v52-user-port 4/41/3
Deleted subscriber-voice 1/57/2 and its
subscriber-voice-xxx profiles
Deleted subscriber-voice 1/57/3 and its
subscriber-voice-xxx profiles
Deleted subscriber-voice 1/57/4 and its
subscriber-voice-xxx profiles
Deleted atm-vcl 99/0/32
Deleted atm-vcl 15/6/41

To remove the configured VP, use the voice vp delete command.

zSH> voice vpdelete uplink/atm/0

Subtended MALC ISDN or POTS voice gateway connections

In a subtended MALC configuration, subscriber traffic passes through the

subtended MALC uplink card and is sent as AAL2 packets to the MALC with
the voice gateway card. The MALC functions as an aggregation point for

MALC Configuration Guide 217

Voice Gateway Connections

multiple downstream MALC systems aggregating multiple ATM services

(PON, SHDSL, T1/E1 ATM) or multiple ATM voice lines on residential
services (ADSL, ADSL2+, VDSL) over a single uplink and voice gateway
connection.

Figure 27: Voice gateway VoATM to TDM with subtended MALC

IAD

ATM
MALC with Local Exchange
voice gateway Switch

In subtended MALC configuration, subscriber traffic passes through the

subtended MALC uplink card and is sent as AAL2 cells to the MALC with
the voice gateway card. AAL2 cells destined for the voice gateway card enter
through one of the MALC uplink card interfaces (GigE, SONET, IP) and are
terminated on the voice gateway card. The voice signal is converted to TDM
T1/E1 channels and sent to the local switch for TDM voice processing. For
traffic coming from the local switch, the TDM voice signals are converted to
AAL2 cells by the voice gateway card and sent back out the MALC uplink
card to the subtended MALC and then to the configured AAL2 destination.
Before configuring the AAL2 to TDM voice connection on the subtended
MALC, ensure the voice gateway AAL2 to GR-303 connection is configured
correctly. See AAL2 voice gateway connections on page 208.
Use these procedures to configure the voice connection on the subtended
MALC. For AAL2 connections to a voice gateway card, the subtended
MALC supports subscriber voice connections for ISDN to AAL2 and POTS
to AAL2.
• Configuring subtended AAL2 voice connection
• Deleting subtended voice connection

Configuring subtended AAL2 voice connection

Configure the subtended MALC AAL2 to sends its AAL2 signals to the voice
gateway. The AAL2 shelf should have a working ATM connection and an
available ATM circuit to the voice gateway card. Also, either a subscriber line
POTS or ISDN card should be installed with all the required ports enabled.

218 MALC Configuration Guide

 Configuring voice gateway connections

For subtended voice connections, the MALC voice card supports POTS to
AAL2 or ISDN to AAL2 voice connections. For more details about
configuring voice connections, see Adding Voice Connections on page 155.
For these voice configurations, the ATM traffic descriptor is required before
the voice connection can be configured.
The ISDN to AAL2 type of voice connection requires an ULC card.

Configuring POTS or ISDN to AAL2 voice connections

The voice add command automatically creates the required VPI/VCI, CID,
and uplink VCL.
1 Create a new atm-traf-descr with a unique index for a voice connection.
See MALC ATM overview on page 21 for more information on ATM
traffic descriptors and parameters.
zSH> new atm-traf-descr 1 index can be any value
Please provide the following: [q]uit.
td_type: -----------------> {atmNoClpNoScr}: atmClpNoTaggingScrCdvt
td_param1: ---------------> {0}: 4826 PCR .
td_param2: ---------------> {0}: 4825 SCR
td_param3: ---------------> {0}: 20 MBS
td_param4: ---------------> {0}: 15000 CDVT
td_param5: ---------------> {0}:
cac-divider: -------------> {1}: 10
td_service_category: -----> {ubr}: rtvbr for voice
td_frame_discard: --------> {false}:
usage-parameter-control: -> {true}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

2 Use the voice add command on the subtended MALC to configure an

ISDN to AAL2 or POTS to AAL2 voice connection.
For ISDN to AAL2:
zSH> voice add isdn 1-3-1-0/isdnu aal2 uplink1/atm vc 0/38 td 1/1 cid 127
Created subscriber-voice 1/5/4
Created subscriber-voice-isdn 65
Created aal2-cid-profile 38/0/38/127
Created subscriber-voice-aal2 66
Created subscriber-voice 1/5/5
Created subscriber-voice-isdn 67
Created subscriber-voice-aal2 68
Created subscriber-voice 1/5/6
Created subscriber-voice-isdn 69
Created subscriber-voice-aal2 70

This example adds an ISDN to AAL2 connection over an ATM VCL with
a VPI/VCI of 0/38, traffic descriptor 1, user port 1, and a CID of 16.
For POTS to AAL2:

MALC Configuration Guide 219

Voice Gateway Connections

zSH> voice add pots 1-5-24-0/voicefxs aal2 uplink1/atm vc 0/39 td 1/1 cid 16
Created subscriber-voice 1/32/2
Created subscriber-voice-pots 10017
Created atm-vcl uplink1/atm/0/39
Created aal2-cid-profile 38/0/39/16
Created subscriber-voice-aal2 10018

This example adds a POTS to AAL2 connection over an ATM VCL with
a VPI/VCI of 0/38, traffic descriptor 1, user port 1,and a CID of 16.
3 Display the voice connection with the voice show command.
zSH> voice show
Subscriber end-point Remote end-point Voice Prof Id STA
------------------------------ ------------------------------ -------------- ---
1-5-24-0/voicefxs 1-2-1-0/atmima VC 0/39 CID 16 1/32/2 ENA
1-3-1-0/isdnu 1-1-1-0/ds1 VC 0/38 CID 127 1/5/4 ENA
Total number of voice connections : 2

Deleting subtended voice connection

To remove a configured voice connection on the subtended MALC, use
the voice delete command.
zSH> voice delete isdn 1-3-1-0/isdnu
zSH> voice delete pots 1-5-24-0/voicefxs

220 MALC Configuration Guide

9
DIAGNOSTICS AND ADMINISTRATION

This chapter describes tasks you might need to perform to administer the
MALC. It includes the following information:
• Log message format, page 222
• SNMP, page 229
• Statistics and alarms, page 232
• System maintenance, page 245
• Testing, page 257

Logging
This section explains how to use logging on the MALC. It includes:
• Overview on page 221
• Enabling/disabling logging on page 222
• Log message format on page 222
• Modifying logging levels on page 223
• Using the log cache on page 224
• Sending messages to a syslog server on page 226
• Specifying different log formats for system and syslog messages on
page 227
• Example log messages on page 229

Overview

Logging enables administrators to monitor system events by generating

system messages. It sends these message to:
• A management session (either on the serial craft port or over a telnet
session)
• A log file on the device
• A syslog server (optional)

MALC Configuration Guide 221

Diagnostics and Administration

The type of information sent in these messages can be configured using the
log command. By default, the system sends the same type of information to
all log message destinations. If you want to send different types of messages
to the syslog daemon, use the syslog command.

Enabling/disabling logging

By default, log messages are enabled on the serial craft port. Use the log
session command and the log serial command to enable/disable logging:
The log session command enables/disables logging messages for that session
only. If the user logs out, the logging setting returns to the default. To enable
logging for the current session only:
zSH> log session on
To disable logging for the session:
zSH> log session off
The log serial command enables/disables logging messages for all sessions
on the serial craft port. This setting persists across system reboots. To enable/
disable logging for the serial craft port:
zSH> log serial on
To disable logging for the serial port:
zSH> log serial off

Log message format

Log messages contain the following information:

Table 9: Default log message fields

Option Description

Date Date stamp of log message. Enabled by default.

Time Time stamp of log message. Enabled by default.

Level Logging level of the message. Enabled by default.

Address The shelf and slot of the card causing the alarm,

Taskname Name of task that generated the log message. This is

generally useful only for Zhone development engineers.
Enabled by default.

Function Function that generated the log message. This is generally

useful only for Zhone development engineers.

Line Line in code that generated the log message. This is

generally useful only for Zhone development engineers.

Message text A description of the error that caused the alarm.

222 MALC Configuration Guide

 Logging

To change the information displayed in the log messages, use the log option
command. First, display the available options:
zSH> log option
Usage: log option < time | 1 > < on | off >
< date | 2 > < on | off >
< level | 3 > < on | off >
< taskname | 4 > < on | off >
< taskid | 5 > < on | off >
< file | 6 > < on | off >
< function | 7 > < on | off >
< line | 8 > < on | off >
< all | 9 > < on | off >
< default | 10 > < on | off >
time: date: level: address: log: taskname: (0xf)

Then, turn the option on or off. For example, the following command will
turn the task ID off in log messages:
zSH> log option taskid off
time: date: level: address: log: taskname: (0xf)

Modifying logging levels

To modify logging, use the log command. To modify syslog messages, use the
syslog command.
To display the current levels for all logging modules, use the log show
command:
zSH> log show
MODULE LEVEL STATUS
aal2approv error enabled
aal2aprec error enabled
aal2rp error enabled
aal2rpzccapi error enabled
aal2rpvcc error enabled
alarm_mgr error enabled
assert error enabled
atm_cc_mib_hdlr error enabled
atmmgr error enabled
atmmgragnt error enabled
bds error enabled
bds_client error enabled
callcontrolregistry error enabled
card error enabled
card_resource error enabled
carddeletehdlr error enabled
ccrp error enabled
cli error enabled
...
...
...

MALC Configuration Guide 223

Diagnostics and Administration

Logging levels determine the number of messages that are displayed on the
console. The higher the log level, the more messages are displayed. The
MALC supports the following log levels:
• 1: emergency
• 2: alert
• 3: critical
• 4: error
• 5: warning
• 6: notice
• 7: information
• 8: debug
To change the log level, use the log module level command. For example, the
following command changes the card module logging level to emergency:
zSH> log level card emergency
Module: card at level: emergency

To enable or disable log levels for a module, use the log enable or log disable
commands. For example:
zSH> log disable card
Module: card is now disabled

Using the log cache

The log cache command displays the non-persistent log messages. It uses the
following syntax:
log cache
Displays the log cache.
log cache max length
Sets the maximum number of log messages to store. The maximum log cache
size is 2147483647, depending in the amount of memory available.
log cache grep pattern
Searches through the log cache for the specified regular expression.
log cache clear
Clears the log cache.
log cache size
Sets the maximum amount of memory for the log cache. Without options,
displays the current log size.
log cache help
Displays help on the log cache command.

224 MALC Configuration Guide

 Logging

Examples
To change the current configured log cache size:
zSH> log cache max 200
Maximum number of log messages that can be saved: 200

The following example searches through the log cache for the string “Major”:
zSH> log cache grep Major
Searching for: "Major"
[1]: FEB 07 11:18:42: alert : 1/1/1025: alarm_mgr:
tLineAlarm: 01:01:01 Major D
S1 Down Line 1:1:1:0 (FarEnd Rx LOF)[2]: FEB 07 11:18:42:
alert : 1/1/1025: alarm_mgr: tLineAlarm: 01:01:02 Major
D
S1 Down Line 1:1:2:0 (FarEnd Rx LOF)[3]: FEB 07 11:18:42:
alert : 1/1/1025: alarm_mgr: tLineAlarm: 01:01:03 Major
D
S1 Down Line 1:1:3:0 (FarEnd Rx LOF)
...
...
...

Viewing the persistent logs

Use the log cache command to view the persistent logs. For example:
zSH> log cache
[1]: JAN 13 17:23:40: alert : 1/6/1025: alarm_mgr: tLineAlarm: 01:06:18 Minor D
SL Down DSL line
[2]: JAN 13 17:23:40: alert : 1/5/1025: alarm_mgr: tLineAlarm: 01:05:26 Minor D
SL Down DSL line
[3]: JAN 13 17:23:40: alert : 1/5/1025: alarm_mgr: tLineAlarm: 01:05:27 Minor D
SL Down DSL line
[4]: JAN 13 17:23:40: alert : 1/6/1025: alarm_mgr: tLineAlarm: 01:06:20 Minor D
SL Down DSL line
[5]: JAN 13 17:23:41: alert : 1/6/1025: alarm_mgr: tLineAlarm: 01:06:21 Minor D
SL Down DSL line
[6]: JAN 13 17:23:41: alert : 1/6/1025: alarm_mgr: tLineAlarm: 01:06:22 Minor D
SL Down DSL line
[7]: JAN 13 17:23:41: alert : 1/6/1025: alarm_mgr: tLineAlarm: 01:06:25 Minor D
SL Down DSL line
[8]: JAN 13 17:23:41: alert : 1/6/1025: alarm_mgr: tLineAlarm: 01:06:29 Minor D
SL Down DSL line
[9]: JAN 13 17:23:41: alert : 1/6/1025: alarm_mgr: tLineAlarm: 01:06:32 Minor D
SL Down DSL line
[10]: JAN 13 17:23:41: alert : 1/6/1025: alarm_mgr: tLineAlarm: 01:06:31 Minor
DSL Down DSL line
[11]: JAN 13 17:23:42: alert : 1/6/1025: alarm_mgr: tLineAlarm: 01:06:37 Minor
DSL Down DSL line
...
...
...

MALC Configuration Guide 225

Diagnostics and Administration

Sending messages to a syslog server

Modify the following parameters in the syslog-destination profile to send

messages to a syslog server.

Parameter Description

address The IP address of the machine hosting the

syslog server.
Default: 0.0.0.0
port The UDP port to which the syslog messages
will be sent.
Default: 514

facility The syslog facility to which the syslog

messages will be sent.
Values:
local0
local1
local2
local3
local4
local5
local6
local7
no-map
Default: local0

severity The severity level used to filter messages being

set to the syslog server.
Values:
emergency
alert
critical
error
warning
notice
info
debug
Default: debug

zSH> new syslog-destination 1

Please provide the following: [q]uit.
address: --> {0.0.0.0}: 192.200.42.5 IP address of the syslog server
port: -----> {514}: leave at default

226 MALC Configuration Guide

 Logging

facility: -> {local0}:

severity: -> {debug}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Specifying different log formats for system and syslog messages

The log-module profile supports the configuration of persistent log messages,

syslog messages, and persistent storage levels by module. You only need to
modify this profile if you want to send different messages to admin sessions,
the persistent logs, and the syslog server.

Parameter Description

name The name of the module whose logging is controlled by this

profile.
Default: logtest

display Controls the display of messages on the system. Messages

logged at this level and above will be displayed.
Values:
emergency
alert
critical
error
warning
notice
info
debug
Default: error

MALC Configuration Guide 227

Diagnostics and Administration

Parameter Description

syslog Controls the format of messages sent to the syslog server

described in the syslog-destination profile. This field is
similar to the display field, except for the trackdisplay
value.
Values:
emergency
alert
critical
error
warning
notice
info
debug
trackdisplay Messages logged at, and above, the level set
in the display parameter will also be recorded in the syslog
server.
Default: trackdisplay

store Controls the persistent storage of messages. This field is

similar to the display field, except for the trackdisplay
value.
Values:
emergency
alert
critical
error
warning
notice
info
debug
trackdisplay Messages logged at, and above, the level set
in the display parameter will also be recorded in the syslog
server.
Default: trackdisplay

zSH> new log-module 1

Please provide the following: [q]uit.
name: ----> {logtest}: test1
display: -> {error}: warning
syslog: --> {trackdisplay}:
store: ---> {trackdisplay}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

228 MALC Configuration Guide

 SNMP

Example log messages

This section provides examples of how to interpret log messages.

DSL line down message

The following message appears when a DSL line comes up or goes down.
.

Date and time Log level physical address (shelf/slot)

task name function name line number

[1]: JAN 07 09:25:42: alert : 1/8/1025: alarm_mgr: _laMgrLogMsg(): l=261 :

tLin eAlarm: 01:08:03 Minor DSL Down DSL line

Message text

The most important parts of the message are the date and time the event
occurred, the shelf/slot of the event, and the message text. The remainder of
the information is only useful for Zhone development engineers.

Slot card up message

The next message appears after a slot card has finished loading its software
and is ready to be provisioned.

Date and time Log level physical address (shelf/slot)

task name function name line number

[24]: JAN 05 20:12:28: notice : 1/2/12 : shelfctrl: _CardUpdateMsgProcess(): l= 381 :

tShelfCtrl: Card in slot 1 changed state to RUNNING.

Message text

The most important parts of the message are the date and time the event
occurred, the shelf/slot of the event, and the message text. The remainder of
the information is only useful for Zhone development engineers.

SNMP
This section describes the following:
• Creating SNMP community names and access lists, page 230
• Configuring traps, page 231

MALC Configuration Guide 229

Diagnostics and Administration

Creating SNMP community names and access lists

Note: By default, the MALC has a single SNMP community defined

with the name ZhonePrivate. This community has admin access to
the system. Zhone recommends that you configure community names
and access lists to prevent unauthorized access to the system.

The community-profile specifies the community name and an access level

for SNMP manager to access the system. It can also optionally specify a
community-access-profile which is used to verify the source IP address of
the SNMP manager. The system supports up to 50 different access lists.
The following community access levels are supported:
• noaccess—the community has no access.
• read—the community has read-only access to the system, with the
exception of information in the community-profile and
community-access-profile.
• readandwrite—the community has read/write access to the system, with
the exception of information in the community-profile and
community-access-profile.
• admin—the community has read and write access to the entire system,
including information in the community-profile and
community-access-profile. Note that the ZMS requires admin access to
manage the system.

Creating a community profile

Note: Configuring a community profile disables the ZhonePrivate

default community name. If you do change the community name, you
must change the name in ZMS or the device will become
unmangeable.

The following example defines a community name public with read-only

privileges:
zSH> new community-profile 1
Please provide the following: [q]uit.
community-name: -----> {}: public
permissions: --------> {read}:
access-table-index: -> {0}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Creating community access lists

The following example defines a community name private with read/write
privileges and also creates an access list to verify that the SNMP managers

230 MALC Configuration Guide

 SNMP

attempting to access the MALC are coming from known IP addresses

192.168.9.10 and 192.168.11.12:
First, create an access list for the first IP address:
zSH> new community-access-profile 2
Please provide the following: [q]uit.
access-table-index: -> {0}: 1
ip-address: ---------> {0.0.0.0}: 192.168.9.10
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Then, create an access list for the second IP address with the same
access-table-index (1):
zSH> new community-access-profile 3
Please provide the following: [q]uit.
access-table-index: -> {0}: 1
ip-address: ---------> {0.0.0.0}: 192.168.11.12
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Finally, create a community-profile that specifies the community name, and

uses the same access-table-index (1) as defined in the two
community-access-profiles you just created:
zSH> new community-profile 4
Please provide the following: [q]uit.
community-name: -----> {}: private ZMS must include this name
permissions: --------> {read}: readandwrite
access-table-index: -> {0}: 1
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Configuring traps

The trap-destination profile defines a trap recipient the MALC will send
traps to. To configure a trap destination you need to know:
• the IP address of the SNMP manager workstation
• the community name the trap recipient expects
Note that the resendseqno and ackedseqno parameters are set by the ZMS.
The other parameters in the trap-destination profile can be left at their
default values. The following example configures a trap recipient with the IP
address 192.168.3.21:
zSH> new trap-destination 32
Please provide the following: [q]uit.
trapdestination: -> {0.0.0.0}: 192.168.3.21
communityname: ---> {}: public

MALC Configuration Guide 231

Diagnostics and Administration

resendseqno: -----> {0}:

ackedseqno: ------> {0}:
traplevel: -------> {low}:
traptype: --------> {(null)}: 0
trapadminstatus: -> {enabled}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Statistics and alarms

This section describes the following:
• Bulk statistics on page 232
• Alarm manager on page 236

Bulk statistics

The MALC can be configured to collect statistics and transfer them to an FTP
server. Any supported SNMP OID can be collected.
1. Every 15 minutes, the MALC gathers the specified statistics.
If a statistic is not collected, the MALC sends a
ZhoneBulkStatisticsIndividualStatFailure trap to the designated trap
recipient.
2. The statistics files are stored on the local flash card with the following
filename:
Device-IP_timestamp
where timestamp is in the form YYYY.DD.MM.HH.MM in the device
local time. For example:192.168.80.291_2002.11.06.14.37
3. The MALC compresses the files and attempts to send them to the FTP
server.
– If the files transfer is successful, the files on the local flash card are
deleted.
– If the file transfer is not successful, the MALC will:
a. Send a ZhoneBulkStatisticsIntervalFailure trap to the designated trap
recipient.
b. Periodically attempt to reach the FTP server.
c. Continue to collect statistics every 15 minutes, writing a new
statistics file to the flash card for every interval, if there is sufficient
space on the flash disk.
d. When the FTP server is available, the MALC transfers all remaining
files to the FTP server and deletes them from the flash card.

232 MALC Configuration Guide

 Statistics and alarms

Bulk statistics file format

If the statistics collected include children, the bulk statistic file uses the
following format:
#Version#
#SysObjectOID
#BeginCollectionRecord*
<CollectionId><space><CollectionInterval><space><OID><space><InstanceId>
1=value1
2=value2
...
...
...
n=valuen
#EndCollectionRecord
#EndFile

where value1, value2, and so on are the SNMP instances for the OID.
If the statistics collected does not include children, the bulk statistic file uses
the following format:
#Version#
#SysObjectOID
#BeginCollectionRecord*
<CollectionId><space><CollectionInterval><space><OID><space><InstanceId>
#EndCollectionRecord
#EndFile

For example, if you set up the system collect statistics for an ATM VCL with
an Ifindex of 123 and a VPI/VCI of 0/36 and include the child objects, the
statistic file would look similar to the following:
#VersionNumber#
#Device 1.3.6.1.4.1.5504.4.2.2.5.1
#BeginCollectionRecord
1000 ZhoneAtmStatsExtEntry 123.0.36
1=135
2=15
3=8309
4=83209
5=23
6=787
7=843
8=38209
#EndCollectionRecord
#EndFile

Where values 1 to 8 are the ZhoneAtmStatsExtEntry entries:

zhoneAtmStatsTotalInitialCellsRx
zhoneAtmStatsTotalFabricCellsRx
zhoneAtmStatsTotalFinalCLP0CellsRx

MALC Configuration Guide 233

Diagnostics and Administration

zhoneAtmStatsTotalFinalCLP1CellsRx
zhoneAtmStatsTotalInitalCellsTx
zhoneAtmStatsTotalFabricCellsTx
zhoneAtmStatsTotalFinalCLP0CellsTx
zhoneAtmStatsTotalFinalCLP1CellsTx

Configuring bulk statistics

Note: You must configure the FTP password used by bulk statistics
using ZMS or the Zhone genSystem MIB.

To configure bulk statistics:

1 Create a bulk-statistic record for the statistics you want to gather. For
example, to collect ATM VCL statistics:
zSH> new bulk-statistic 1
Please provide the following: [q]uit.
enabled: ----------> {true}:
oid: --------------> {}: ZhoneAtmStatsExtEntry
instance: ---------> {}: 136 ifIndex of ATM interface
include-children: -> {false}: true
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

2 Update the bulk-statistics-config 0 profile to specify the FTP server

information:
zSH> update bulk-statistics-config 0
Please provide the following: [q]uit.
bulk-statistics-enabled: -> {false}: true
ftp-server-address: ------> {0.0.0.0}: 192.168.8.100
ftp-login: ---------------> {}: zhoneuser
ftp-password: ------------> {**private**}:**read-only** must be configured using
SNMP or ZMS
ftp-directory-path: ------> {}: /stats
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Bulk statistics example

This example explains how to configure bulk statistics to gather the following
SNMP statistics:
ZhoneAtmStatsExtEntry object in the comAtm MIB:
1: zhoneAtmStatsTotalInitialCellsRx
2: zhoneAtmStatsTotalFabricCellsRx

234 MALC Configuration Guide

 Statistics and alarms

3: zhoneAtmStatsTotalFinalCLP0CellsRx
4: zhoneAtmStatsTotalFinalCLP1CellsRx
5: zhoneAtmStatsTotalInitalCellsTx
6: zhoneAtmStatsTotalFabricCellsTx
7: zhoneAtmStatsTotalFinalCLP0CellsTx
8: zhoneAtmStatsTotalFinalCLP1CellsTx
zhoneDslPerfDataTotalEntry in the phyDsl MIB:
1: zhoneDslPerfTotalLofs
2: zhoneDslPerfTotalLoss
3: zhoneDslPerfTotalLols
4: zhoneDslPerfTotalInits
5: zhoneDslPerfTotalES
6: zhoneDslPerfTotalSES
7: zhoneDslPerfTotalCRCAnomalies
8: zhoneDslPerfTotalLOSWS
9: zhoneDslPerfTotalUAS
To get these statistics:
1 Get the ifIndex for the trunking interface:
zSH> ifxlate 1-1-1-0-sonet/atm
ifIndex: ----------> {8}
shelf: ------------> {1}
slot: -------------> {2}
port: -------------> {1}
subport: ----------> {0}
type: -------------> {sonet}
adminstatus: ------> {up}
physical-flag: ----> {true}
iftype-extension: -> {none}
ifName: -----------> {1-1-1-0}

2 Get the ifIndex for the subscriber interface:

zSH> ifxlate 1-7-1-0/adsl
ifIndex: ----------> {136}
shelf: ------------> {1}
slot: -------------> {7}
port: -------------> {1}
subport: ----------> {0}
type: -------------> {adsl}
adminstatus: ------> {up}
physical-flag: ----> {true}
iftype-extension: -> {none}
ifName: -----------> {1-7-1-0}

MALC Configuration Guide 235

Diagnostics and Administration

3 Update the bulk-statistics-config profile to specify the FTP server:

zSH> update bulk-statistics-config 0
Please provide the following: [q]uit.
bulk-statistics-enabled: -> {false}: true
ftp-server-address: ------> {0.0.0.0}: 192.168.80.201
ftp-login: ---------------> {}: username
ftp-password: ------------> {** private **}: ** read-only **
ftp-directory-path: ------> {}: stats
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

4 Modify the zhoneBulkStatsSystemFtpPassword object in the genSystem

MIB to change the FTP password.
5 Create a bulk-statistic profile for the trunking interface. Set
include-children to true to gather all the child statistics for this object:
zSH> new bulk-statistic 1
Please provide the following: [q]uit.
enabled: ----------> {true}:
oid: --------------> {}: zhoneAtmStatsExtEntry
instance: ---------> {}: 1635 ifIndex of the ATM interface
include-children: -> {false}: true
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

6 Create a bulk-statistic profile for the subscriber interface. Set

include-children to true to gather all the child statistics for this object:
zSH> new bulk-statistic 2
Please provide the following: [q]uit.
enabled: ----------> {true}:
oid: --------------> {}: zhoneDslPerfDataTotalEntry
instance: ---------> {}: 136 ifIndex of DSL interface
include-children: -> {false}: true
....................
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Alarm manager

The MALC central alarm manager includes the ability to view the active
alarms on the system (using the alarm command) and the ability to store
active alarms on the device. ZMS can use the alarms stored on the device to
recreate the state of the alarms if it becomes disconnected.
The alarm command uses the following syntax:
alarm show [summary]

236 MALC Configuration Guide

 Statistics and alarms

For example, the following command displays the number of current active
alarms, the total number of alarms, the number of cleared alarms, as well as
each active alarm and its severity:
zSH> alarm show
************ Central Alarm Manager ************
ActiveAlarmCurrentCount :21
ActiveAlarmTotalCount :42
ClearAlarmTotalCount :21
OverflowAlarmTableCount :0

ResourceId AlarmType AlarmSeverity

---------- --------- -------------
1-5-2-0/adsl linkDown minor
1-5-3-0/adsl linkDown minor
1-5-4-0/adsl linkDown minor
1-5-5-0/adsl linkDown minor
1-5-6-0/adsl linkDown minor
1-5-7-0/adsl linkDown minor
1-5-8-0/adsl linkDown minor
1-5-17-0/adsl linkDown minor
1-5-18-0/adsl linkDown minor
1-5-19-0/adsl linkDown minor
1-5-20-0/adsl linkDown minor
1-5-21-0/adsl linkDown minor
1-5-22-0/adsl linkDown minor
1-5-23-0/adsl linkDown minor
1-5-24-0/adsl linkDown minor
1-2-1-0/sonet linkDown critical
1-2-2-0/sonet linkDown critical
1-2-1-0/sonet sonetSectionStatusChange major
1-2-2-0/sonet sonetSectionStatusChange major
1-2-1-0/sonet sonetLineStatusChange major
1-2-2-0/sonet sonetLineStatusChange major

The summary option displays the number of current active alarms, the total
number of alarms, the number of cleared alarms:
zSH> alarm show summary

************ Central Alarm Manager ************

ActiveAlarmCurrentCount :3
ActiveAlarmTotalCount :3
ClearAlarmTotalCount :0
OverflowAlarmTableCount :0

Supported alarms
The alarms reported by the alarm show command are based on traps. When
these traps are received by ZMS, they generate ZMS alarms.
The following alarms are supported.

MALC Configuration Guide 237

Diagnostics and Administration

Table 10: Supported alarms

Alarm Description

aal2ExternalAIS Alarm Indication Signal associated with a

maintenance alarm detected.

aal2ExternalRAI Remote Alarm Indication detected to constitute

a received signal failure.

aal2InternalAIS Alarm Indication Signal detected affecting the

AAL type 2 connection.
aal2InternalRDI Remote Defect Indication detected affecting the
AAL type 2 connection.

aal2PerfCellLossThreshTrap A bad sequence error is detected when some

cells have been lost.

aal2PerfCongestionThreshTrap The number of congestion events exceed the

congestion threshold.

aal2PvcDown The status of AAL type 2 PVC has gone down.

adslAtucInitFailureTrap Near end modem (ATUC) failure during

initialization.

adslAtucPerfESsThreshTrap Errored Second 15-minute interval threshold

reached on near end modem (ATUC)

adslAtucPerfLofsThreshTrap Loss of Framing 15-minute interval threshold

reached on near end modem (ATUC)

adslAtucPerfLolsThreshTrap Loss of Link 15-minute interval threshold

reached on near end modem (ATUC)

adslAtucPerfLossThreshTrap Loss of Signal 15-minute interval threshold

reached on near end modem (ATUC)

adslAtucPerfLprsThreshTrap Loss of Power 15-minute interval threshold

reached on near end modem (ATUC)
adslAtucRateChangeTrap Near end modem (ATUC) transmit rate changed
from adslAtucChanPrevTxRate to
adslAtucChanCurrTxRate

adslAturPerfESsThreshTrap Errored Second 15-minute interval threshold

reached on far end modem (ATUR)

adslAturPerfLofsThreshTrap Loss of Framing 15-minute interval threshold

reached on far end modem (ATUR)

adslAturPerfLossThreshTrap Loss of Signal 15-minute interval threshold

reached on far end modem (ATUR)

adslAturPerfLprsThreshTrap Loss of Power 15-minute interval threshold

reached on far end modem (ATUR)

238 MALC Configuration Guide

 Statistics and alarms

Table 10: Supported alarms

Alarm Description

adslAturRateChangeTrap Far end modem (ATUR) transmit rate changed

from adslAturChanPrevTxRate to
adslAturChanCurrTxRate

apsEventChannelMismatch An APS channel mismatch between the

transmitted K1 channel and the received K2
channel has occurred.

apsEventFEPLF An APS Far-End Protection-Line Failure

(FEPLF) has occurred.
This condition is declared based on receiving
signal failure (SF) on the protection line in the
K1 byte.

apsEventModeMismatch An APS event mode mismatch has occurred.

A conflict between the current local mode and
the received K2 mode information constitutes a
mode mismatch.

apsEventPSBF An APS Protection Switch Byte Failure (PSBF)

has occurred.
This condition occurs when either an
inconsistent APS byte or an invalid code is
detected. An inconsistent APS byte occurs when
no three consecutive K1 bytes of the last 12
successive frames are identical, starting with the
last frame containing a previously consistent
byte. An invalid code occurs when the incoming
K1 byte contains an unused code or a code
irrelevant for the specific switching operation
(that is., Reverse Request while no switching
request is outstanding) in three consecutive
frames. An invalid code also occurs when the
incoming K1 byte contains an invalid channel
number in three consecutive frames.

apsEventSwitchover The number of times this channel has switched

to the protection line.

atmDsx3PlcpAlarmStatusChan The DS3 Physical Layer Convergence

ge Procedure (PLCP) has received an alarm.

atmInterfaceTCAlarmStateCha ATM Interface TC Sublayer is currently in the

nge Loss of Cell Delineation defect maintenance
state.
atmOamF4PingStatus Indicates whether an OAM F4 ping has
succeeded or failed.

atmOamF5PingStatus Indicates whether an OAM F5 ping has

succeeded or failed.

MALC Configuration Guide 239

Diagnostics and Administration

Table 10: Supported alarms

Alarm Description

atmVclBandwidthUnavailable Bandwidth specified in an ATM traffic

descriptor is not available. This alarm is sent
when either of the following conditions occurs:
• A VCL is activated with a traffic descriptor
that specifies a higher than available rate.
• A VCL is activated with a traffic descriptor
that specifies a vcl-rate value which will
cause available bandwidth to run out.
atmVclOperStatusChange Subscriber (Id: SubscriberID, Name:
SubscriberName) on Vcl (IfIndex: IfIndex, Vpi:
VPI, Vci: VCI) is affected
atmVpiAutoCreateComplete Indicates the system has completed creating
VPIs. The system automatically creates VPIs
for pre-existing VPLs and VCLs if the VPI/VCI
ranges for a card are changed.

atmVplOperStatusChange A VPL has changed state.

dhcpTrapZhoneCpeDetected An IP address is being offered to a Zhone CPE

device via DHCP.
dhcpTrapZhoneCpeSysObjectI The system Object ID of an attached Zhone
D CPE device that has obtained its address via
DHCP.

dhcpTrapZhoneIpAddressUpda An IP address has been assigned or modified via

te DHCP.

coldStart An SNMP entity on the system has reinitialized

and its configuration may have changed.

dhcpTrapZhoneCpeDetected An IP address is being offered to a Zhone CPE

device

dsx3LineStatusChange Status change for the DS3 interface.

fan_a_failure Fan A is in a fault state.

fan_a_ok Fan A operating normally.

fan_b_failure Fan B is in a fault state.

fan_b_ok Fan B operating normally.

fan_power_supply_a_failure Fan A power supply is in a fault state.

fan_power_supply_a_ok Fan A power supply is operating normally.

fan_power_supply_b_failure Fan B power supply is in a fault state.

fan_power_supply_b_ok Fan B power supply is operating normally.

fan_speed_error There is an irregular fan speed.

240 MALC Configuration Guide

 Statistics and alarms

Table 10: Supported alarms

Alarm Description

fan_speed_ok Fan speed is normal.

fan_tray_added Fan tray added to device.

fan_tray_removed Fan tray removed from device.

igCrvRemoteStateChange A remote GR-303 all reference value (CRV) has

changed state.
igCrvTmcStateChange A GR-303 timeslot management channel CRV
(TMC) has changed state.

igEocPrimaryStateChange A primary GR-303 embedded operations

channel (EOC) has changed state.

igEocSecondaryStateChange A secondary GR-303 embedded operations

channel (EOC) has changed state.

igOperStatusChange A GR-303 interface group (IG) has changed

state.

igSystemTimeChange A GR-303 IG system time has changed.

igTmcPrimaryStateChange A primary GR-303 TMC has changed state.

igTmcSecondaryStateChange A secondary GR-303 TMC has changed state.

isdnMibCallInformation This trap indicates the status of a connection
request. It is sent whenever:
• an incoming call is rejected
• an outgoing call attempt fails (if the call is
configured for retries, this trap is sent after
all retires fail)
• a call connects
Note that only one trap is sent for successful or
unsuccessful call attempts between two
neighbors; subsequent call attempts result in no
trap.
isdnTrapAmiViolations Bad Ami violation.

isdnTrapFECV Far end code violation.

isdnTrapFrameSynchLoss Driver receives three successive out of sync

frames.
isdnTrapUnbalancedFrame The number of unbalanced ISDN frames has
been exceeded.

left_outlet_temp_normal The system is reporting a the temperature on the

left outlet is within temperature specifications.

left_outlet_temp_over_limit The system is reporting a high temperature on

the left outlet.

MALC Configuration Guide 241

Diagnostics and Administration

Table 10: Supported alarms

Alarm Description

linkDown Communication link is about to enter the down

state.
power_supply_a_failure Power supply A is in a fault state.

power_supply_a_ok Power supply A is operating normally.

power_supply_b_failure Power supply B is in a fault state.

power_supply_b_ok Power supply B is operating normally.

power_supply_c_failure Power supply C is in a fault state.

power_supply_c_ok Power supply C is operating normally.

power_supply_d_failure Power supply D is in a fault state.

power_supply_d_ok Power supply D is operating normally.

right_outlet_temp_normal The system is reporting a the temperature on the

left outlet is within temperature specifications.

right_outlet_temp_over_limit The system is reporting a high temperature on

the right outlet.
sechtor100FanStatusChange The fan on a Zhone Sechtor 100 device has
changed state.

sechtor100ThermoStatusChang The temperature sensor in a Zhone Sechtor 100

e device has changed state.

shelf_controller_fault Shelf controller fault.

sipStatusCodeNotif Indicates a session initiation protocol (SIP)

status code has been sent or received by the
system.

sipStatusCodeThreshExceeded Indicates that a specific SIP status code was

Notif found to have been sent or received by the
system enough to exceed the configured
threshold.

sonetClockTransmitSourceCha Indicates the SONET clock external recovery or

nge clock transmit settings have been changed.This
could be caused by a change to the MALC
clocking configuration or a line failure.
sonetLineStatusChange A SONET line has changed state.

sonetPathStatusChange A SONET path has changed state.

sonetSectionStatusChange A SONET section has changed state.

temp_normal The temperature of the device is within
specifications.

242 MALC Configuration Guide

 Statistics and alarms

Table 10: Supported alarms

Alarm Description

temp_over_limit The temperature of the device is over

specifications.
temp_under_limit The temperature of the device is under
specifications.

v52CChannelStatusChange The V5.2 C channel has changed state.

v52CPathOperStatusChange The V5.2 path has changed state.

v52IgOperStatusChange The V5.2 IG has changed state.

v52IgPortAlignmentNotificatio A request has been initiated by the operator.

n

v52IgProvVariantRequestNotif A request has been initiated from the AN side.

ication

v52LinkBlockNotification A V5.2 link block request has been sent.

v52LinkCheckIdNotification A V5.2 check link ID request has been received.

v52ProtectionCPathOperStatus A V5.2 protection C path has changed state.

Change

voiceDspChannelInterArrvJitte This trap is sent whenever the

rTrigger channelInterArrvJitter exceeds the default
setting.

voiceDspChannelPktsLoss This trap is sent whenever the

channelPktsPktsLost exceeds the default
setting.

voiceDspReset Indicates a voice DSP has reset.

warmStart An SNMP entity on the system has reinitialized

and its configuration may have changed.

zapTrapZhoneBanDetected Sent when a BAN detects a MALC or Raptor

device.

zapTrapZhoneCpeConnection Sent when a Zhone CPE device is disconnected.

Down

zapTrapZhoneCpeDetected Sent when a Zhone CPE is detected for the first

time.

zapTrapZhoneMalcConnection A Zhone MALC device has been disconnected.

Down

zapTrapZhoneMalcDetected A Zhone MALC has been detected for the first

time.

zapTrapZhoneProvisioningDon Automatic provisioning is completed.

e

MALC Configuration Guide 243

Diagnostics and Administration

Table 10: Supported alarms

Alarm Description

zhoneAdslPotsBypassRelayCh A DSL bypass relay has changed state. This trap

angeNotification is sent on a per-port basis and only applies to the
MALC ADSL 32 + splitter cards.

zhoneBulkStatisticsIntervalFail Bulk statistics were not successfully gathered

ure for the current interval.
This could be caused by the statistics periods
overlapping (due to network congestion or too
many statistics being gathered), no disk space,
file write error, or an FTP error.

zhoneCardRedundancyStatusC The specified card has become active.

hange
zhoneCardServicesStatusChan Card service is inactive or unavailable (slot
ge SlotNumber)

zhoneDslLineAlarmStatusCha The SDSL and SHDSL interface has changed

nge state.

zhoneExternalAlarmTrap External relay is open or is not connected.

zhoneImaGroupDown IMA group has gone down.

zhoneLineStatusChange The DS1 interface has changed stated.

zhonePingTestCompleted A ping command has been successful.

zhoneTraceRoutePathChange The path for a traceroute has been changed.

zhoneTraceRouteTestFailed A traceroute command has failed.

zhoneTrapCardMemStatus The memory on a device has changed. This

could indicate RAM or flash memory is low or
not available.

zhoneTrapCardStatusChange Indicates a card state has changed. This could

indicate the card was added, removed, is in a
fault state, or has been reset.

zhoneTrapCardVersionCheck Card version CardVersion (SlotNumber) is

incompatible with that of active InfoServ card.
(BAN only)

zhoneTrapConfigSyncChange A partial config sync update has failed

zhoneTrapCpeConnectionDow Zhone CPE connection is down
n

zhoneTrapFlashCardStatusCha Indicates the flash card in the system has

nge changed state.

zhoneTrapShelfStatusChange A shelf has changed state.

zhoneTrapSnmpSATimeout The SNMP subagent on the system has timed

out.

244 MALC Configuration Guide

 System maintenance

Table 10: Supported alarms

Alarm Description

zhoneZmsBlockCliChange At least one CLI session has been unblocked or

all CLI sessions are blocked.
zrgBatteryRelayNotification Indicates the state of onboard ZRG battery.

System maintenance
This section describes the following:
• MALC file system on page 245
• Accessing the flash card on page 246
• Deleting card profiles on page 248
• Manually binding interfaces on page 248
• Renaming interfaces on page 250
• Saving and restoring configurations on page 250
• SNTP on page 251
• User accounts on page 252
• Viewing chassis and slot information on page 254
• Controlling Telnet access on page 255

MALC file system

The Uplink card flash memory contains DOS file system that stores the
system boot code, software images, and the configuration. During system
startup, the software images on the flash are decompressed and loaded into
memory.
The following commands can be used to access the file system:
• cd. Changes directory.
• dir. Lists the contents of the directory.
• pwd. Displays the current working directory.
• ata. Used to format or initialize a flash card. This is typically done only
for new cards or if you want to completely erase the flash card.
• image. Verifies software images and downloads software images on the
flash to system memory.

MALC Configuration Guide 245

Diagnostics and Administration

Accessing the flash card

Use the cd, dir, and pwd commands to list the contents of the file system, as
in the following example:
zSH> dir
Listing Directory .:
-rwxrwxrwx 1 0 0 639836 Nov 27 07:00 malct1imaraw.bin
-rwxrwxrwx 1 0 0 3321852 Nov 27 07:00 malct1ima.bin
-rwxrwxrwx 1 0 0 1032722 Nov 27 07:00 malcmtac.bin
drwxrwxrwx 1 0 0 2048 Nov 28 12:50 datastor/
-rwxrwxrwx 1 0 0 1682204 Nov 27 07:01 malcadslpots.bin
-rwxrwxrwx 1 0 0 3301097 Nov 27 07:01 malcds3.bin
-rwxrwxrwx 1 0 0 639756 Nov 27 07:01 malcds3raw.bin
-rwxrwxrwx 1 0 0 1510173 Nov 27 07:00 malcgshdsl.bin
-rwxrwxrwx 1 0 0 1441233 Dec 6 20001 malcadslac5.bin
75399168 bytes free

Using the ata command

The ata command formats and initializes flash cards. Formatting formats the
files system, but leaves the boot partition on the card intact. Initialization
reinitializes the boot partitions on the cards and formats the file system.
The following example formats flash card:
zSH> ata format 1
The following example initializes the flash card:
zSH> ata init 1

Using the image command

The MALC contains a TFTP server that enables you to download files from a
network to the flash card file system using the image command.
The image command uses the following syntax:
image download tftphost image-file destination
The following example downloads the image for the Uplink card
(malcoc3.bin) from host 192.168.8.21 to the root directory of the first flash
card:
image download 192.168.8.21 malcoc3.bin malcoc3.bin
The image command can also verify image files on the flash card. It reads the
contents of the file, verifies the file header, and verifies the file checksum. For
example:
zSH> image verify malcoc3.bin
File: malcoc3.bin
Size: 3186874 bytes
Header Version: 1
Load Type: MALC OC3
Load Address: 0x00010000
Checksum: 0x0c847b68

246 MALC Configuration Guide

 System maintenance

Image verify successful

The command reports any errors it finds in the file. Note that files are also
verified as part of the download process.

Changing the serial craft port settings

Tip: You only need to modify an rs232-profile if you want to change

the default configuration of the serial craft port.

The MALC rs232-profile can be used to configure serial craft ports on the
system.
The default settings for the MALC serial control ports are:
• 9600bps
• 8 data bits
• No parity
• 1 stop bit
• No flow control

Changing the serial control port settings

Caution: The serial craft port supports speeds of 9600, 19200,

38400, and 57600 bps. Do not set the speed to an unsupported
value. Doing so could render the serial craft port inaccessible.

Update an rs232-profile for the shelf and slot that contains the serial craft
port. The following example updates the profile for the serial craft port in
slot 1:
zSH> update rs232-profile 1-1-1-0/rs232
shelf-slot-port-subport/type
Please provide the following: [q]uit.
rs232PortInSpeed: -------> {9600}: 57600
rs232PortOutSpeed: ------> {9600}: 57600
rs232PortInFlowType: ----> {none}:
rs232PortOutFlowType: ---> {none}:
rs232AsyncPortBits: -----> {8}:
rs232AsyncPortStopBits: -> {one}:
rs232AsyncPortParity: ---> {none}:
rs232AsyncPortAutobaud: -> {disabled}:
....................
Save new record? [s]ave, [c]hange or [q]uit:
Record created.

The settings take effect after the profile is saved.

MALC Configuration Guide 247

Diagnostics and Administration

Note: If the rs232-profile is deleted, the port speed is set to the

last configured value.

Deleting card profiles

Caution: Before deleting card profiles, perform the following:

• Back up the MALC configuration. See the release notes for
information.
• Delete the ATM cross connects associated with the card.
• For voice cards, ensure all subscribers and voice profiles are
deleted before deleting the card.
• Remove the card from the system as explained in the MALC
Hardware Installation Guide.

Delete the card-profile for a card to delete all the profiles associated with a
card. After deleting a card-profile, the specified card reboots.

Caution: A delete card-profile command deletes profiles

associated with the card and may disrupt service until the system is
reprovisioned.

The delete command uses the following syntax:

delete card-profile 1/slot/type
Where slot is the location of the card and type is the Zhone type for the card.
the card.
The following example deletes an ADSL card (Zhone type 5004) in slot 13:
zSH> delete card-profile 1/13/5004
Delete card-profile 1/13/5004? [y]es, [n]o, [q]uit : y
card-profile 1/13/5004 deleted.

You can only delete one card-profile at a time. Wildcards are not supported
when deleting card profiles.

Manually binding interfaces

When creating ip-interface-record profiles, the syntax is name/type. The

name of the IP interface can be user-defined or match the naming of the
if-translate record for the physical interface. The system automatically binds
interfaces if the name of the new IP record matches the name of the
if-translate profile or if the syntax shelf/slot/port/subport/type is used. Enter a
list if-translate command to determine what if-translate records are
available on your system.

248 MALC Configuration Guide

 System maintenance

The example below shows a new ip-interface-record being created with a

user-defined name.
zSH> new ip-interface-record myip/ip
Please provide the following: [q]uit.
vpi: ---------------> {0}:
vci: ---------------> {0}:
rdindex: -----------> {1}:
dhcp: --------------> {none}: ** read-only **
addr: --------------> {0.0.0.0}: 192.168.88.200
netmask: -----------> {0.0.0.0}: 255.255.255.0
bcastaddr: ---------> {0.0.0.0}: 192.168.88.255
destaddr: ----------> {0.0.0.0}:
farendaddr: --------> {0.0.0.0}:
mru: ---------------> {1500}:
reasmmaxsize: ------> {0}:
ingressfiltername: -> {}:
egressfiltername: --> {}:
pointtopoint: ------> {no}:
mcastenabled: ------> {yes}:
ipfwdenabled: ------> {yes}:
mcastfwdenabled: ---> {yes}:
natenabled: --------> {no}:
bcastenabled: ------> {yes}:
ingressfilterid: ---> {0}:
egressfilterid: ----> {0}:
ipaddrdynamic: -----> {static}:
dhcpserverenable: --> {false}:
....................
Save new record? [s]ave, [c]hange or [q]uit: s
Cannot determine binding for this IP interface.
Could not automatically bind this IP Interface.
New record saved.

Since the system did not automatically bind the new IP interface, manually
bind the interface with the stack bind command:
zSH> stack bind
Enter the upper layer: myip/ip the IP interface created
Enter the lower layer: 1-1-1-0-ethernetcsmacd/other the line group associated with Ethernet
Stack bind successful.

Note: The stack bind command does not allow binding directly to
physical interfaces. You must bind two logical interfaces.

Enter the stack show command (with name/type syntax) to see interface
binding:
zSH> stack show myip/ip
Line Group: 1-1-1-0-ethernetcsmacd/other
Physical: 1/1/1/0/ethernetcsmacd

MALC Configuration Guide 249

Diagnostics and Administration

Renaming interfaces

Interfaces on the MALC can be renamed using the ifName parameter in the
if-translate profile for the interface.
For example, to rename an Uplink card T1 interface:
zSH> update if-translate 1-1-1-0/ds1
Please provide the following: [q]uit.
ifindex: -----> {1}: .
shelf: -------> {1}:
slot: --------> {1}:
port: --------> {1}:
subport: -----> {0}:
type: --------> {ds1}:
adminstatus: -> {up}:
physical-flag: ----> {true}:
iftype-extension: -> {0}:
ifName: -----------> {1-1-1-0}: uplink_ds1_1
redundancy-param1: -> {0}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

Saving and restoring configurations

The dump and restore commands enable you to save and restore the system
configuration. You can save the configuration to the console, a local file, or
the network.
The command uses the following syntax:
dump [console] [file filename] [network host filename ]
Passwords are encrypted when they are saved to the configuration file. The
encrypted passwords are used to restore the correct password, but cannot be
used to log in.

Note: The dump and restore commands use TFTP to transfer files to
the network. Set the TFTP server time-out value to at least 5 seconds,
and 5 retries to help prevent TFTP timeout or retry errors.

To save the configuration to a console:

1 Configure your terminal emulation software as follows:
– 9600bps
– 8 data bits
– No parity
– 1 stop bit
– No hardware flow control

250 MALC Configuration Guide

 System maintenance

– VT100
– Set Line Delay and Character Delay to 40 milliseconds
2 Turn on the file capture utility of your terminal emulation software.
3 Save the configuration by entering:
dump console
Do not press the Enter key.
4 Start the capture utility on your terminal emulation software and enter a
name for the file (use a .txt extension).
5 Press the Enter key.
The configuration file will be displayed on the screen.
6 When configuration file is finished, stop the capture utility.

Backing up the configuration to a local file

To dump the configuration to a local file:
Specify a file name for the configuration:
zSH> dump file filename

The file is saved on the MALC filesystem.

Backing up the configuration to the network

To back up the configuration to the network:
1 Create the file in the destination location of the TFTP server and make it
writeable.
2 Save the configuration. The following example saves the configuration to
a file named dvice.cfg on the host 192.168.8.21:
zSH> dump network 192.168.8.21 device.cfg

Restoring the configuration

For information on restoring your configuration, refer to the release notes
for your release.

SNTP
To set up the system to use SNTP:
Update the ntp-client-config profile. For example:
zSH> update ntp-client-config 0
Please provide the following: [q]uit.
primary-ntp-server-ip-address: ---> {0.0.0.0}: 192.168.8.100
secondary-ntp-server-ip-address: -> {0.0.0.0}:
local-timezone: ------------------> {gmt}: pacific

MALC Configuration Guide 251

Diagnostics and Administration

daylight-savings-time: -----------> {false}:

....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

User accounts

MALC users have access to the CLI and are able to configure and administer
the system.

Adding users
Every administrative user on the system must have a user account. The
account specifies their username and password, as well as their privilege
level, which determines their access to commands.
Users with admin privileges have access to all the administrative commands.
Users with user privileges have access to a very limited set of commands. The
highest level of access is useradmin, which allows the creation of user
accounts.

Note: When entering access level responses, enter yes completely or

the CLI interprets the response as no.

To add a user, enter the following commands:

zSH> adduser
Please provide the following: [q]uit.
User Name: jjsmith
User Prompt[zSH>]:

Please select user access levels.

admin: -------> {no}: yes
zhonedebug: --> {no}:
voice: -------> {no}:
data: --------> {no}:
manuf: -------> {no}:
database: ----> {no}:
systems: -----> {no}:
tool: --------> {no}:
useradmin: ---> {no}: yes
..................................
User name:(jjsmith) User prompt:(zSH>)
Access Levels:
(admin)(useradmin)
Save new account? [s]ave, [c]hange or [q]uit: s
User record saved.
TEMPORARY PASSWORD: hmj4mxFU

Commands with zhonedebug privilege levels are intended for use by Zhone
development only.

252 MALC Configuration Guide

 System maintenance

Immediately after activating the user account, you should change the
password something you can remember, as explained in the next section.

Changing default user passwords

When adding users, the system automatically assigns a temporary password to
each user. Most users will want to change their password. The changepass
command changes the password for the current logged in user. The following
is an example of changing a password:
zSH> changepass
Current Password:
New Password:
Confirm New Password:
Password change successful.

Deleting users
To delete a user, enter the deleteuser command and specify the username:
zSH> deleteuser jsmith
OK to delete this account? [yes] or [no]: yes
User record deleted.

Deleting the admin user account

In addition to deleting regular user accounts, you can also delete the admin
user account. This account is automatically created by the system and
provides full access to the CLI.

Note: You cannot delete the admin account (or any other user
account with useradmin privileges) if you are currently logged into
it.

To delete the admin account:

zSH> deleteuser admin
If desired, you can recreate an account named admin after deleting it:
zSH> adduser admin
Please provide the following: [q]uit.
User Name: admin
User Prompt[zSH>]:

Please select user access levels.

admin: -------> {no}: yes
zhonedebug: --> {no}:
voice: -------> {no}: yes
data: --------> {no}: yes
manuf: -------> {no}: yes
database: ----> {no}: yes
systems: -----> {no}: yes
tool: --------> {no}: yes

MALC Configuration Guide 253

Diagnostics and Administration

useradmin: ---> {no}: yes

..................................
User name:(admin) User prompt:(zSH>)
Access Levels:
(admin)(voice)(data)(manuf)(database)(systems)(tools)(use
radmin)
Save new account? [s]ave, [c]hange or [q]uit: s
User record saved.
TEMPORARY PASSWORD: hmj4mxFU

Resetting passwords
If a user forgets their password, an administrative user can reset the password
and generate a new one using the resetpass command, as in the following
example:
zSH> resetpass jsmith
Password:

Viewing chassis and slot information

The following commands display information about the status of the system:
• shelfctrl
• slots
To view overall status of the system, use the shelfctrl monitor command:
zSH> shelfctrl monitor
Shelf Monitor CPLD version: 1.2
Shelf Monitor Firmware version: 1.6
Inlet temperature 79 degrees.
Left outlet temperature sensor: 78 degrees (normal)
Right outlet temperature sensor: 78 degrees (normal)
Power Supply A: failure
Power Supply B: normal
Fan status: OK.
System: Critical alarm set.
Card 12: Critical alarm set.

To view general system statistics:

zSH> shelfctrl stats
Shelf Controller Message Statistics
-----------------------------------
Card updates: 42
Card ECHO: 0
Directory services messages: 2
Clock messages: 178707
Lease messages: 496
Heartbeat messages: 470902

Card update errors: 0

Card ECHO errors: 0

254 MALC Configuration Guide

 System maintenance

Directory services errors: 0

Clock errors: 0
Lease errors: 0
Heartbeat errors: 0
Receive errors: 0

To verify whether the shelf is active:

zSH> shelfctrl show
Shelf Controller Address: 01:02:12
Shelf Registry Address: 01:02:75
Lease ID: 0x022b0008_00000036
State: active

To view the system slot cards and their status:

zSH> slots
1: MALC OC3 (RUNNING)
5: MALC ADSL AC5 (RUNNING)
6: MALC ADSL AC5 (LOADING)
7: MALC ADSL AC5 (RUNNING)
8: MALC ADSL AC5 (RUNNING)
9: MALC ADSL (RUNNING)
13: MALC MTAC (RUNNING)
16: MALC ADSL AC6 (RUNNING)
20: MALC GSHDSL (RUNNING)
21: MALC GSHDSL (RUNNING)

To view information about a particular slot card, use the slots command and
specify a slot number. For example:
zSH> slots 1
Type : MALC OC3
Card Version : 1
EEPROM Version : 1
Serial # : 7714040
CLEI Code : No CLEI
Card-Profile ID : 1/1/5011
Shelf : 1
Slot : 1
State : RUNNING
Mode : FUNCTIONAL
Heartbeat check : enabled
Longest hbeat : 50
Fault reset : enabled
Uptime : 1 hour, 49 minutes

Controlling Telnet access

The port-access profile specifies from which IP addresses users can telnet to
the MALC. If a host’s IP address is not specified in a port-access profile,
users from that host cannot telnet to the MALC. These restrictions take effect
after the first port-access profile has been created.

MALC Configuration Guide 255

Diagnostics and Administration

By default, no port-access profiles are created, so telnet access is not

restricted.

Creating port-access profile entries

Up to 100 port-access profile entries can be created on a MALC. To create a
port-access profile entry:
Create a new port-access profile and specify the telnet port number, host/
network IP address to be granted access, and the netmask applied to the IP
address to allow access to a range of IP addresses.
This example creates port-access entry 1 on telnet port 23 and allows
hosts on the 172.16.41.xx network to telnet to the MALC.

Note: Typically, only port 23 is used for telnet access.

zSH> new port-access 1

Please provide the following: [q]uit.
portNumber: -> {0}: 23
portArg1: ---> {0.0.0.0}: 172.16.41.0
portArg2: ---> {0.0.0.0}: 255.255.255.0
....................S=
Save new record? [s]ave, [c]hange or [q]uit: s
New record saved.

Displaying port-access profile entries

To display configured port-access profile entries use the list command:
zSH> list port-access
port-access 1
1 entry found.

Modifying port-access profile entries

To modify a configured port-access profile entry use the update
command. The following example changes the entry’s source IP address
to 172.16.40.0:
zSH> update port-access 1
portNumber: -> {23}
portArg1: ---> {172.16.41.0} 172.16.40.0
portArg2: ---> {255.255.255.0}
1 entry found.
....................
Save new record? [s]ave, [c]hange or [q]uit: s
Updated record saved.

256 MALC Configuration Guide

 Testing

Testing
This section describes the following:
• Activating or deactivating interfaces on page 257
• BER tests on page 258
• IMA test pattern procedure on page 259
• Loopbacks on page 263
• Viewing IMA group status on page 268

Activating or deactivating interfaces

Physical interfaces on the MALC have associated if-translate profiles, which

enable or disable the interfaces. To change the state of an interface, use the
adminstatus parameter in the if-translate profile associated with the
interface. The if-translate profile uses the following syntax:
if-translate shelf-slot-port-subport/type

For example, to activate a MALC T1 interface:

zSH> update if-translate 1-1-1-0/ds1
Please provide the following: [q]uit.
ifindex: -----> {1}: .
shelf: -------> {1}:
slot: --------> {1}:
port: --------> {1}:
subport: -----> {0}:
type: --------> {ds1}:
adminstatus: -> {down}: up
physical-flag: ----> {true}:
iftype-extension: -> {0}:
ifName: -----------> {}:
redundancy-param1: -> {0}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

For example, to deactivate a MALC T1 interface:

zSH> update if-translate 1-1-1-0/ds1
Please provide the following: [q]uit.
ifindex: -----> {1}: .
shelf: -------> {1}:
slot: --------> {1}:
port: --------> {1}:
subport: -----> {0}:
type: --------> {ds1}:
adminstatus: -> {up}: down
physical-flag: ----> {true}:
iftype-extension: -> {0}:
ifName: -----------> {}:

MALC Configuration Guide 257

Diagnostics and Administration

redundancy-param1: -> {0}:

....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

BER tests

The send-code parameter in the ds1-profile controls loopbacks and BER tests
on the T1 interface. The following table describes the BERT options.

Parameter Description

send-code Indicates what type of code is being sent across the

DS1 interface by the device. Setting this parameter
causes the interface to send the requested code.
Values:
sendQRSSPattern Sends a Quasi-Random Signal
Source (QRSS) test pattern.
send511Pattern Sends a 511 bit fixed test pattern.
send3in24Pattern Sends a fixed test pattern of 3 bits
set in 24.
send2047Pattern Sends 2047 test pattern.
send1in2Pattern Sends alternate one, zero pattern

Activating a BER test

Note: BER tests disrupt traffic on the interface.

1 Update the ds1-profile to specify the BERT pattern:

zSH> update ds1-profile 1-1-1-0/ds1
Please provide the following: [q]uit.
line-type: ----------------------> {esf}:
line-code: ----------------------> {b8zs}:
send-code: ----------------------> {sendnocode}: sendqrsspattern
circuit-id: ---------------------> {ds1}:
loopback-config: ----------------> {noloop}:
signal-mode: --------------------> {robbedbit}:
fdl: ----------------------------> {fdlnone}:
dsx-line-length: ----------------> {dsx0}:
line-status_change-trap-enable: -> {enabled}:
channelization: -----------------> {enabledds0}:
ds1-mode: -----------------------> {csu}:
csu-line-length: ----------------> {csu00}:
clock-source-eligible: ----------> {noteligible}:
transmit-clock-source: ----------> {throughtiming}
cell-scramble: ------------------> {false}
coset-polynomial: ---------------> {true}:

258 MALC Configuration Guide

 Testing

protocol-emulation: -------------> {network}

signal-type: --------------------> {loopstart}
ds1-group-number: ---------------> {0}
line-power: ---------------------> {disabled}
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

2 To end a BER test:

zSH> update ds1-profile 1-1-1-0/ds1
Please provide the following: [q]uit.
line-type: ----------------------> {esf}:
line-code: ----------------------> {b8zs}:
send-code: ----------------------> {sendqrsspattern}: sendnocode
circuit-id: ---------------------> {ds1}:
loopback-config: ----------------> {noloop}:
signal-mode: --------------------> {robbedbit}:
fdl: ----------------------------> {fdlnone}:
dsx-line-length: ----------------> {dsx0}:
line-status_change-trap-enable: -> {enabled}:
channelization: -----------------> {enabledds0}:
ds1-mode: -----------------------> {csu}:
csu-line-length: ----------------> {csu00}:
clock-source-eligible: ----------> {noteligible}:
transmit-clock-source: ----------> {throughtiming
cell-scramble: ------------------> {false}
coset-polynomial: ---------------> {true}:
protocol-emulation: -------------> {network}
signal-type: --------------------> {loopstart}
ds1-group-number: ---------------> {0}
line-power: ---------------------> {disabled}
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

IMA test pattern procedure

The MALC supports IMA test pattern procedures to validate the status of the
IMA link. A test pattern sent over a transmit link is looped back over all
available receive interfaces. Test pattern procedures do not interrupt traffic.

MALC Configuration Guide 259

Diagnostics and Administration

The following table describes the test pattern procedure parameters in the
ima-group-profile.

Parameter Description

testLinkIfIndex Indicates the interface used to transmit the test pattern. The test
pattern is looped back from the far end device over each active
link in the IMA group. Note that this value is not the same as
the txImaId value.
Values:
A valid interface on the system in the form
shelf-slot-port-subport/type This is the link whose link
identifier (LID) value is inserted in the Tx LID field of the
transmitted ICP cells.
Default: 0

testPattern Specifies the transmit Test Pattern in an IMA group loopback

operation. A value in the range 0 to 254 designates a specific
pattern.
Values:
–1 to 254 –1 indicates that the test pattern is randomly
generated.
Default: –1
testProcStatus Enables or disables the Test Pattern Procedure.
Values:
disabled Deactivates the test pattern procedure.
operating Activates the test pattern procedure.
Default: disabled

Testing the IMA link with a random test pattern

A test pattern procedure with a random pattern will run continuously until it is
disabled. Use the imatppshow command to view the status of the test (as
explained in Viewing test procedure status on page 262).
To test the IMA link with a randomly generated test link and pattern (the
default):
1 Specify an interface to transmit the test over:
zSH> update ima-group-profile 1/1/1
Please provide the following: [q]uit.
groupSymmetry: ---> {symmetricoperation}:
minNumTxLinks: ---> {1}:
minNumRxLinks: ---> {1}:
txClkMode: -------> {ctc}:
txImaId: ---------> {1}:
txFrameLength: ---> {m128}:
diffDelayMax: ----> {75}:
alphaValue: ------> {2}:
betaValue: -------> {2}:
gammaValue: ------> {1}:

260 MALC Configuration Guide

 Testing

testLinkIfIndex: -> {0}: 1-1-1-0/ds1 IMA link to test

testPattern: -----> {-1}:
testProcStatus: --> {disabled}: operating
txTimingRefLink: -> {0}:
rxTimingRefLink: -> {0}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

2 To disable the test:

zSH> update ima-group-profile 1/1/1
Please provide the following: [q]uit.
groupSymmetry: ---> {symmetricoperation}:
minNumTxLinks: ---> {1}:
minNumRxLinks: ---> {1}:
txClkMode: -------> {ctc}:
txImaId: ---------> {1}:
txFrameLength: ---> {m128}:
diffDelayMax: ----> {75}:
alphaValue: ------> {2}:
betaValue: -------> {2}:
gammaValue: ------> {1}:
testLinkIfIndex: -> {1/1/1/0/ds1}:
testPattern: -----> {-1}:
testProcStatus: --> {enabled}: disabled
txTimingRefLink: -> {0}:
rxTimingRefLink: -> {0}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

Testing the IMA link with a specific test pattern

A test with a specified test pattern runs until it verifies link connectivity. Use
the imatppshow command to view the status of the test (as explained in
Viewing test procedure status on page 262).
1 To specify a particular test pattern (for example, 23):
zSH> update ima-group-profile 1/1/1
Please provide the following: [q]uit.
groupSymmetry: ---> {symmetricoperation}:
minNumTxLinks: ---> {1}:
minNumRxLinks: ---> {1}:
txClkMode: -------> {ctc}:
txImaId: ---------> {1}:
txFrameLength: ---> {m128}:
diffDelayMax: ----> {75}:
alphaValue: ------> {2}:
betaValue: -------> {2}:
gammaValue: ------> {1}:
testLinkIfIndex: -> {0}: 1-1-1-0/ds1 IMA link to test
testPattern: -----> {-1}: 23

MALC Configuration Guide 261

Diagnostics and Administration

testProcStatus: --> {disabled}: operating

txTimingRefLink: -> {0}:
rxTimingRefLink: -> {0}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

To run the test again, update the ima-group-profile without making any
changes.
2 To disable the test:
zSH> update ima-group-profile 1/1/1
Please provide the following: [q]uit.
groupSymmetry: ---> {symmetricoperation}:
minNumTxLinks: ---> {1}:
minNumRxLinks: ---> {1}:
txClkMode: -------> {ctc}:
txImaId: ---------> {1}:
txFrameLength: ---> {m128}:
diffDelayMax: ----> {75}:
alphaValue: ------> {2}:
betaValue: -------> {2}:
gammaValue: ------> {1}:
testLinkIfIndex: -> {1/1/1/0/ds1}:
testPattern: -----> {-1}:
testProcStatus: --> {enabled}: disabled
txTimingRefLink: -> {0}:
rxTimingRefLink: -> {0}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

Viewing test procedure status

Use the imatppshow command to view the status of the test:
If the test is successful, imaGroupTestProcStatus displays
OPERATING:
zSH> imatppshow 1
TestLink .....................: 2
imaGroupTestPattern ..........: 23
imaGroupTestProcStatus .......: OPERATING

If the test fails (if, for example, the remote link is down),
imaGroupTestProcStatus displays LINKFAIL:
zSH> imatppshow 1
TestLink .....................: 2
imaGroupTestPattern ..........: 71
imaGroupTestProcStatus .......: LINKFAIL

After the test is disabled, the imaGroupTestProcStatus displays

DISABLED:

262 MALC Configuration Guide

 Testing

zSH> imatppshow 1
TestLink .....................: 2
imaGroupTestPattern ..........: 23
imaGroupTestProcStatus .......: DISABLED

Loopbacks

The MALC support the following types of loopbacks:

• T1 loopbacks on page 263
• DS3 loopbacks on page 266
• SONET loopbacks on page 265
• ISDN loopbacks on page 267

T1 loopbacks
The loopback-config parameter in the ds1-profile controls T1 loopbacks.
The following table describes the loopback options.

Parameter Description

loopback-config The loopback configuration of the DS1 interface.

Values:
noloop Not in the loopback state. A device that is not
capable of performing a loopback on the interface
always returns this as its value.
lineloop The received signal on this interface does not
go through the device (minimum penetration) but is
looped back out.
payloadloop The received signal on this interface
does not go through the device (minimum penetration)
but is looped back out.
Default: noloop

Activating a T1 loopback

Note: Loopbacks disrupt traffic on the interface.

1 Specify the type of loopback:

zSH> update ds1-profile 1-1-1-0/ds1
Please provide the following: [q]uit.
line-type: ----------------------> {esf}:
line-code: ----------------------> {b8zs}:
send-code: ----------------------> {sendnocode}:
circuit-id: ---------------------> {ds1}:

MALC Configuration Guide 263

Diagnostics and Administration

loopback-config: ----------------> {noloop}: lineloop

signal-mode: --------------------> {robbedbit}:
fdl: ----------------------------> {fdlnone}:
dsx-line-length: ----------------> {dsx0}:
line-status_change-trap-enable: -> {enabled}:
channelization: -----------------> {enabledds0}:
ds1-mode: -----------------------> {csu}:
csu-line-length: ----------------> {csu00}:
clock-source-eligible: ----------> {noteligible}:
transmit-clock-source: ----------> {throughtiming}
cell-scramble: ------------------> {false}
coset-polynomial: ---------------> {true}:
protocol-emulation: -------------> {network}
signal-type: --------------------> {loopstart}
ds1-group-number: ---------------> {0}
line-power: ---------------------> {disabled}
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

Note: Only one loopback can be active at a time. If there is a

loopback running, a message similar to the following will appear
when you attempt to run another loopback:
1/1: ds1rp: : l=3278: Please disable any active
loopbacks on line 1:1:0:0

2 To stop the loopback:

zSH> update ds1-profile 1-1-1-0/ds1
Please provide the following: [q]uit.
line-type: ----------------------> {esf}:
line-code: ----------------------> {b8zs}:
send-code: ----------------------> {sendlinecode}:
circuit-id: ---------------------> {ds1}:
loopback-config: ----------------> {lineloop}: noloop
signal-mode: --------------------> {robbedbit}:
fdl: ----------------------------> {fdlnone}:
dsx-line-length: ----------------> {dsx0}:
line-status_change-trap-enable: -> {enabled}:
channelization: -----------------> {enabledds0}:
ds1-mode: -----------------------> {csu}:
csu-line-length: ----------------> {csu00}:
clock-source-eligible: ----------> {noteligible}:
transmit-clock-source: ----------> {throughtiming}
cell-scramble: ------------------> {false}
coset-polynomial: ---------------> {true}:
protocol-emulation: -------------> {network}
signal-type: --------------------> {loopstart}
ds1-group-number: ---------------> {0}
line-power: ---------------------> {disabled}
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

264 MALC Configuration Guide

 Testing

SONET loopbacks
A SONET terminal loopback is a SONET circuit with a loop that terminates
at the MALC OC3-c/STM1 interface.
The medium-loopback-config parameter in the sonet-profile specifies the
type of loopback:

Parameter Description

medium-loopback-config How the SONET loopback is configured.

Values:
sonetnoloop SONET circuit, with no loop.
sonetfacilityloop All incoming data on the Rx
interface is retransmitted out of the Tx interface.
Used to check the circuit between a remote device
and the MALC and to test the MALC optical
module.
sonetterminalloop All of the data transmitted on
the Tx interface is also internally looped back to
the Rx interface. Used to verify that the ATM and
PHY layers are communicating.
sonetotherloop All incoming data on the Rx
interface is retransmitted out of the Tx interface.
Used to check the circuit between the IAD and a
remote unit and to verify that the optical module
and the SONET PHY are working.

Looping back the SONET interface

The following example initiates SONET terminal loopbacks.
1 Set the interface to testing:
zSH> update if-translate 1-1-1-0/sonet
shelf-slot-port-subport/type
Please provide the following: [q]uit.
ifindex: -----> {232}: .
shelf: -------> {1}:
slot: --------> {1}:
port: --------> {1}:
subport: -----> {0}:
type: --------> {sonet}:
adminstatus: -> {down}: testing
physical-flag: ----> {false}:
iftype-extension: -> {none}:
ifName: -----------> {}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

2 Configure the type of loopback:

MALC Configuration Guide 265

Diagnostics and Administration

zSH> update sonet-profile 1-1-1-0/sonet

Please provide the following: [q]uit.
medium-type: ---------------> {sonet}:
medium-line-coding: --------> {sonetmediumnrz}:
medium-line-type: ----------> {sonetshortsinglemode}:
medium-circuit-identifier: -> {}:
medium-loopback-config: ----> {sonetnoloop}: sonetterminalloop
medium-scramble-config: ----> {sonetscrambleon}:
path-current-width: --------> {sts3cstm1}:
clock-external-recovery: ---> {enabled}:
clock-transmit-source: -----> {looptiming}:
medium-cell-scramble-config: -> {true}:
medium-line-scramble-config: -> {true}:
....................
Save changes? [s]ave, [c]hange or [q]uit: s
Record saved.

Note: The adminstatus of the SONET line remains up and

SONET communications continue during SONET terminal
loopbacks.

DS3 loopbacks
The loopback-config parameter in the ds3-profile controls DS3 loopbacks.
The following table describes the loopback options.

Parameter Description

loopback-config Specifies the loopback configuration of the

interface.
Values:
dsx3noloop The DS3 interface is not in the
loopback state.
dsx3payloadloop The received signal at the DS3
interface is looped through the system for
retransmission.
dsx3inwardloop The sent signal at the DS3
interface is looped back through the system.
dsx3lineloop The received signal at the DS3
interface does not go through the device before it is
looped.

Activating a DS3 loopback

Note: Loopbacks disrupt traffic on the interface.

1 Specify the type of loopback:

266 MALC Configuration Guide

 Testing

zSH> update ds3-profile 1-1-2-0/ds3

line-type: ---------------> {dsx3cbitparity}
line-coding: -------------> {dsx3b3zs}
send-code: ---------------> {dsx3sendnocode}
circuit-id: --------------> {}
loopback-config: ---------> {dsx3noloop} specify type of loopback
transmit-clock-source: ---> {looptiming}
line-length-meters: ------> {0}
line-status-trap-enable: -> {enabled}
channelization: ----------> {disabled}
ds1-for-remote-loop: -----> {0}
far-end-equip-code: ------> {}
far-end-loc-id-code: -----> {}
far-end-frame-id-code: ---> {}
far-end-unit-code: -------> {}
far-end-fac-id-code: -----> {}
medium-scramble-config: --> {true}
medium-frame-config: -----> {e3frameg832}
medium-atmframe-config: --> {dsx3atmframingdirectcellmapped}

Note: Only one loopback can be active at a time.

2 To stop the loopback:

zSH> update ds3-profile 1-1-2-0/ds3
line-type: ---------------> {dsx3cbitparity}
line-coding: -------------> {dsx3b3zs}
send-code: ---------------> {dsx3sendnocode}
circuit-id: --------------> {}
loopback-config: ---------> {dsx3payloadloop} dsx3noloop
transmit-clock-source: ---> {looptiming}
line-length-meters: ------> {0}
line-status-trap-enable: -> {enabled}
channelization: ----------> {disabled}
ds1-for-remote-loop: -----> {0}
far-end-equip-code: ------> {}
far-end-loc-id-code: -----> {}
far-end-frame-id-code: ---> {}
far-end-unit-code: -------> {}
far-end-fac-id-code: -----> {}
medium-scramble-config: --> {true}
medium-frame-config: -----> {e3frameg832}
medium-atmframe-config: --> {dsx3atmframingdirectcellmapped}

ISDN loopbacks
Loopbacks can be run on the ISDN B and D channels.

Note: Loopbacks disrupt traffic on the interface.

MALC Configuration Guide 267

Diagnostics and Administration

Modify the loopback parameter in the isdn-profile to configure ISDN

loopbacks:

Parameter Description

loopback Initiates ISDN loopback on the U interface.

Values:
loop-back-none no loop back
loop-back-b1-idl2-tr transparent loopback on the Interchip Digital Link,
Version 2 (IDL2), which is used for transporting the ISDN channels towards
the system (B1 channel)
loop-back-b1-idl2-nt non-transparent loopback on the IDL2 interface
towards the system (B1 channel)
loop-back-b2-idl2-tr transparent loopback on the IDL2 interface towards the
system (B2 channel)
loop-back-b2-idl2-nt non-transparent loopback on the IDL2 interface
towards the system (B2 channel)
loop-back-2bd-idl2-tr transparent loopback on the IDL2 towards the system
(2B + D channel)
loop-back-2bd-idl2-nt non-transparent loopback on the IDL2 towards the
system (2B + D channel)
loop-back-2bd-u-interface-tr transparent loopback on the U interface
towards the user (2B + D channel)
loop-back-2bd-u-interface-nt non-transparent loopback on the U interface
(2B + D channel)
loop-back-2bd-external-analog loopback on the external analog interface
towards the user (2B + D channel)
Default: loop-back-none

zSH> update isdn-profile 1-14-1-0/isdnu

Please provide the following: [q]uit.
line-term-class: ---> {class1}:
activation-timer2: -> {t2-50ms}:
loopback: ----------> {loop-back-none}: loop-back-b1-idl2-tr
Save changes? [s]ave, [c]hange or [q]uit: s
Record updated.

Viewing IMA group status

The imarpshow command displays information about the MALC IMA

group. The command uses the following syntax:
imarpshow [index]
where index is the IMA group number. For example:
zSH> imarpshow
RP Info:
rp state -------------------> RP_INITIALIZED
address --------------------> 01:01:113

268 MALC Configuration Guide

 Testing

rp shelf -------------------> 1
rp slot --------------------> 1
rp ima core started --------> TRUE
imaGrpProfLeaseId ----------> 0x02070000_00000057
LineRRProvLeaseId ----------> 0x02070000_00000055
LineRRClientLeaseId --------> 0x02070000_00000056
numImaGroups ---------------> 1
ImaGroupIndecies: 1

To display complete information about an IMA group, specify the group

number:
zSH> imarpshow 1
RP Info:
rp state -------------------> RP_INITIALIZED
address --------------------> 01:01:113
rp shelf -------------------> 1
rp slot --------------------> 1
rp ima core started --------> TRUE
imaGrpProfLeaseId ----------> 0x02070000_00000057
LineRRProvLeaseId ----------> 0x02070000_00000055
LineRRClientLeaseId --------> 0x02070000_00000056
numImaGroups ---------------> 1
ImaGroupIndecies: 1
IMA Group Index =1
..............................................
group status ==========> OOS
......................... group ne state -------->
INSUFFICIENTLINKS
group fe state --------> OPERATIONAL
.........................
group ctlr state ------> GRP_INITIALIZED
group ifIndex ---------> 11
group in service ------> TRUE
driver attached -------> TRUE
driver unit -----------> 0
auto-created ----------> FALSE
ifxLeaseId ------------> 0x02070000_00000057
lineProfLeaseId -------> 0x02070000_00000057
lineGrpLeaseId --------> 0x02070000_00000057
ifStackLeaseId --------> 0x02070000_00000057
ds1LeaseId ------------> 0x00000000_00000000
.........................
ifxlateProfValid ----------------> TRUE
ifxlatProf.ifIndex --------------> 11
ifxlatProf.shelf ----------------> 1
ifxlatProf.slot -----------------> 1
ifxlatProf.port -----------------> 2
ifxlatProf.ifType ---------------> ATMIMA
ifxlatProf.adminStatus ----------> UP
.........................
lineProfValid -------------------> TRUE
lineProf.profileName ------------> Atm IMA Group default line profile
lineProf.physicalAddress.shelf --> 1

MALC Configuration Guide 269

Diagnostics and Administration

lineProf.physicalAddress.slot ---> 1
lineProf.physicalAddress.port ---> 2
lineProf.lineGroupName ----------> 11
.........................
lineGrpProfValid ----------------> TRUE
lineGrpProf.groupName -----------> 1/1/1
lineGrpProf.primaryName ---------> 11
lineGrpProf.secondaryName -------> 0
lineGrpProf.primaryWeight -------> 0
lineGrpProf.secondaryWeight -----> 0
lineGrpProf.adminState ----------> UP
.........................
imaGrpProfValid -----------------> TRUE
imaGrpProf.groupSymmetry --------> SYMMETRICAL
imaGrpProf.minNumTxLinks --------> 1
imaGrpProf.minNumRxLinks --------> 1
imaGrpProf.txClkMode ------------> CTC
imaGrpProf.txImaId --------------> 1
imaGrpProf.txFrameLength --------> M128
imaGrpProf.diffDelayMax ---------> 75
imaGrpProf.alphaValue -----------> 1
imaGrpProf.betaValue ------------> 1
imaGrpProf.gammaValue -----------> 1
imaGrpProf.testLinkIfIndex ------> 0
imaGrpProf.testPattern ----------> -1
imaGrpProf.testProcStatus -------> DISABLED
imaGrpProf.txTimingRefLink ------> 0
imaGrpProf.rxTimingRefLink ------> 0
.........................
Link#1
linkType -----------> DS1_PROFILE_LINETYPE_ESF
ifIndex ------------> 2
framerstatus -------> OOS
netxlinkstatus -----> NOT-IN-GROUP
nerxlinkstatus -----> NOT-IN-GROUP
..........................
...
...
...

270 MALC Configuration Guide

INDEX

A traffic descriptor validation 34

traffic descriptors 27
accessing the flash card general rules 30
cd command 246 traffic policing 33
dir command 246 UBR and usage-parameter-control 40
pwd command 246 video 23
acronyms, described 10 voice overview 22
activating slot cards VPI/VCI ranges 24
ADSL cards 202, 206, 208, 217 ATM cell relay connection
adding a user, description of 252 configuration 37, 43
adding routes creating cross-connect 50, 51
description 77 creating traffic descriptor 37, 43
route add command 77 creating VCLs 48, 49
addresses creating VCLs and VPLs 46
assigned via DHCP 78 ATM cell termination connection
admin adding IP route to remote LAN 17
deleting user account of 253 configuration 18
administration creating IP interface 19
configuring traps 231 verifying IP interface 17
creating SNMP access lists 230 ATM data connection
creating SNMP community names 230 cell relay 37, 43
logging 221 configuration 22
saving and restoring configurations 250 data communications 22
user accounts 252 traffic descriptors 27
alarms VCLs 25
viewing card and shelf 254 VPLs 26
alarms, viewing 236 ATM management connection
A-Law creating IP interface 19
setting 156 ATM OC3-c interfaces
always offhook, configuring 186 loopbacks 265
ARP, broadcasts and bridging 107 ATM on Zhone devices
ata command, use of 246 data communications 22
ATM overview 22
bridging and IP support on VC 106 virtual channel links 25
CAC 31 virtual path links 26
cross connects 23 ATM traffic descriptor
EPD and PPD 24 creating 18
overview 21
PVCs supported per card 24 B
SCR and PCR 27
SCR and PCR, configuring allowable values BER test, described 258
for 40 binding interfaces 248
statistics 34 bootfile parameter 82
traffic descriptor configuration rules 28 boot-server parameter 82

MALC Configuration Guide 271

Index

bridging 107 host show 100

adding untagged bridge 110 ifxlate 19
administrative commands 135 image 246
ARP broadcast 107 interface add 74
broadcasts and 106 interface delete 102
custom DHCP server 134 interface show 100
forbid OUI 131 log 223
intralinks 106 log show 223
option 82 131, 133 mcast 95
overview 105 pwd 246
support on VC 106 rip 77
VLAN 108 rip show 100, 101
VLAN bridge-paths 108 route add 77
VLAN configuration 107 route delete 102
VLAN overview 107 route show 100
VLAN strip and insert 133 stack bind 249
broadcast suppression, described 134 configurable jitter buffer 194
configuration
C ATM cell relay connection 37, 43
ATM cell termination connection 18
CAC ATM data connection 22
described 31 ATM VCLs and VPLs 46
call progress parameters 196 CLI disabled 20
caller, rejecting malicious 193 creating DHCP server subnet options 81
caller-id-sig-protocol 196 creating dhcp-server-group profile 87
calls creating dhcp-server-host profile 87
checking bandwidth before accepting a call 156 DHCP server 78
cards DNS resolver 88
VG-T1/E1-32-2S 199 Ethernet management channel 66
cd command, use of 246 host-based routing 67
cdvt_btA, formula used to calculate 34 interface indexes 139, 147
cdvt_btB, formula used to calculate 34 IP filters 90
change default passwords, how to 253 local management channel 15
channel bank, configuring system 166 logging in 15
chassis logging out 15
viewing errors 254 network-based routing 74
viewing temperature 254 overview of profiles 13
clid-mode 196 RIP 77
client leases, DHCP 103 saving and restoring 250
clientId parameter 87 configuring ATM data connection
client-match-string parameter 87 ATM cell termination connection 18
clock ATM on Zhone devices 22
setting system using NTP 251 cell relay connections 51
commands configuring IP
ata 246 DHCP server 78
cd 246 displaying routing information 100
dir 246 DNS resolver 88
host add 67 host-based routing 67
host delete 101 IP filters 90
modifying host and interface routes 97

272 MALC Configuration Guide

 network-based routing 74 logging messages described 103
RIP 77 profiles 78
static routes 77 relay 84
configuring management interface setting server options 79
accessing the serial port 15 DHCP client leases 103
local management channel 15 DHCP server 59
logging in and out 15 DHCP server, enabling 83
configuring physical interfaces DHCP, description of 58
loopbacks 265 dhcp-server-group profile 87
configuring traps, description of 231 dhcp-server-host profile 78, 87
craft interface 15 dhcp-server-subnet profile 81
creating IP interface dialing plan 191
adding route to remote LAN 17 dir command, use of 246
description 19 displaying host information 100
ifxlate 19 displaying interface information 100
specifying VPI/VCI pair 19 displaying RIP information 101
verifying the interface 19 displaying routing information
creating IP management interface rip show command 100
description 19 route show command 100
creating SNMP access lists, description of 230 routing table 100
creating SNMP community names, description of DNS resolver configuration
230 creating a host profile 89
cross-connect, creation of 50, 51 creating a resolver record 89
DNS, description of 58
D Domain Name System, see DNS
domain parameter 82, 89
Data rate domain-name parameter 82
delay criteria 26 DS1 to POTS
throughput criteria 26 configuring connection 166
default configuration, description of 14 DS3
default passwords, changing 253 call admission control 30
default-lease-time parameter 82 dual counter rotating rings, RPR 113
default-router parameter 82 Dynamic Host Control Protocol, see DHCP
delay-before-clid-after-ring 196
deleting a user, description of 253 E
deleting hosts 101
deleting interfaces 102 encoding
deleting routes types supported 156
description 102 EPD, described 24
route delete command 102 errors, viewing system 254
DHCP Ethernet
address assignment 78 for IP video 97
advanced applications 86 Linear GigaBit configuration 126
broadcast suppression 134 Linear GigaBit redundancy configuration 128
creating subnet options 81 Resilient Packet Ring (RPR) 112
custom DHCP setting in bridge records 134 Ethernet interface
enabling a DHCP server 83 configuration 16
external server 85 creating a default route 17, 67
logging 102 creating a route from management PVC to 19

MALC Configuration Guide 273

Index

IP interface 16 commands
route show command 17, 67 interface show 100
verifying 17 interfaces
verifying the route 17, 67 renaming 250
Ethernet management channel 66 Intralinks
configuring 106
F IP
addresses for redundant Uplink cards 16
first-nameserver parameter 89 administrative procedures 97
advanced provisioning procedures 86
G applications 59
DHCP external server 85
GigE-2 card DHCP relay 84
Linear GigaBit Ethernet configuration 126 overview 57
Linear GigaBit Ethernet redundancy 128 provisioning procedures 66
GR-303 routing 60
configuring 138 support on VC 106
video, configuring 93
H IP filtering
description of 64
IP filters
hookflash
configuration 90
configuring 184
ISDN
configuring timers 185
loopbacks 267
host add command 67
host delete command 101
host profile 90 J
host show command 100
hostalias1 parameter 90 jitter buffer 194
hostalias2 parameter 90
hostalias3 parameter 90 L
hostalias4 parameter 90
host-based routing lease-time parameter 80
configuration 67 Linear GigaBit Ethernet, configuration 126
description of 61 Linear GigaBit Ethernet, redundancy configuration
hostname parameter 90 128
huntgroups 187 local management channel 15
hwaddr parameter 87 log messages, description of content for 221
logging
I description 221
DHCP 102
if-translate profile DHCP messages described 103
renaming interfaces in 250 displaying persistent logs 225
image command, use of 246 enabling/disabling 222
interface add command 74 enabling/disabling for session 16
interface delete command 102 enabling/disabling over the serial craft port 16
interface groups log messages 221
number supported on Voice Gateway card 201 modifying logging levels 223
interface indexes, configuration of 139, 147 syslog, configuring 226
interface show command 100 logging in and out

274 MALC Configuration Guide

 description 15 P
logout command 15
timeout command 15 parameters
logging in, restricting telnet access 255 bootfile 81
logging levels, log command and modifying 223 boot-server 81
logging out, described 15 clientId 87
loopbacks client-match-string 87
DS3 266 default-lease-time 81
ISDN 267 default-router 81
T1 266 domain 81, 89
loopbacks, SONET and 265 domain-name 81
first-nameserver 89
M hostalias1 90
hostalias2 90
malicious caller, rejecting 193 hostalias3 90
management hostalias4 90
configuring interface for 16 hostname 90
creating route from management PVC to hwaddr 87
Ethernet 19 lease-time 80
ZMS 19 max-lease-time 80, 81
max-lease-time parameter 80, 82 min-lease-time 80, 81
mcast command, described 95 name 87
MGCP netmask 81
configuring 163 network 81
min-lease-time parameter 80, 82 primary-name-server 81
Mu-Law query-order 89
setting 156 range1-end 81
multicast range1-start 81
creating control list 94 range2-end 81
range2-start 81
N range3-end 81
range3-start 81
name parameter 87 range4-end 81
netmask parameter 82 range4-start 81
network parameter 82 reserve-end 80
network-based routing reserve-start 80
configuration 74 secondary-name-server 81
description of 63 second-nameserver 89
NTP third-nameserver 89
configuring 251 vendor-match-string 87
passwords, changing default 253
O PCM encoding
type supported 156
option 82, bridging 133 persistent logs, displaying 225
option 82, described 131 policing, ATM 33
OUI forbin, described 131 POTS
DS1 to POTS 166
PPD, described 24
primary-name-server parameter 82

MALC Configuration Guide 275

Index

profiles configuring global defaults 77

dhcp-server-group 87 description 59
dhcp-server-host 78, 87 displaying information 101
host 90 rip command 77
overview of configuration 13 rip show command 101
resolver 89, 90 routing
protection switching, RPR 118 description 60
PVCs routing information base 60
number supported per card 24 routing in Zhone systems
pwd command, use of 246 route types 60
routing information base, description of 60
Q Routing Information Protocol, see RIP
routing table, displaying 100
QoS and traffic descriptors RPR 112
QoS categories
described 26 S
non-real-time variable bit rate 26
Quality of Service, see QoS Saving and restoring configurations 251
query-order parameter 89 saving and restoring configurations
description 247
R secondary-name-server parameter 82
second-nameserver parameter 89
range1-end parameter 82 security
range1-start parameter 82 restricting telnet access 255
range2-end parameter 82 server-max-timer, voice-system profile 165
range2-start parameter 82 Service, quality objectives 26
range3-end parameter 82 SIP
range3-start parameter 82 connections over different networks 164
range4-end parameter 82 SIP, calls not registering 165
range4-start parameter 82 sip-dialplan 191
redundancy SNMP
IP addresses and 16 statics, gathering 232
reserve-end parameter 80 SONET
reserve-start parameter 80 loopbacks 265
resetting passwords, description of 254 stack bind 249
Resilient Packet Ring (RPR) static routes
bridged traffic 124 adding routes 77
configuration 117 configuration 77
configuration display 119 deleting routes 102
overview 112 statistics
protection switching 118 ATM 34
ring status 122 bulk 232
statistics 123 strip and insert
topology 112 configuring 133
topology display 120 subtending, example
resolver profile 89, 90 ATM
ring cadence 196 subtending 52
RIP support, contacting 12
configuration 77 syslog server, configuring 226

276 MALC Configuration Guide

system user accounts
configuring ATM data connection 22 adding a user 252
configuring management interface 15 changing default passwords 253
data communications 22 deleting a user 253
default configuration 14 deleting admin 253
Ethernet interface 16 resetting passwords 254
logging out 15 using flash cards
management interface 16 using the ata command 246
Uplink cards 16 using the image command 246
system profile
voice configuration 156 V
T V5.2
activating the IG 153
T1 loopbacks C-channels 150
activating 263, 266 C-paths 152
tagged bridging IG 146
described 105 parameters 144
technical support, contacting 12 provisioning links 148
telnet V5.2 profile, configuring 143
restricting access 255 VCI
temperature, viewing chassis 254 allowed ranges 24
terminal interface, settings for 15 VCLs
third-nameserver parameter 89 creation 48, 49
traffic descriptors description 25
configuration rules 28 VCLs and VPLs
creation 37, 43 creation 46
description 27 vendor-match-string 87
QoS video
rules for 30 ATM 23
validation for 34 configuring IP 93
traps Ethernet uplink for 97
configuring 231 virtual channel link, see VCL
VLAN
U bridge-paths and 108
VLAN IDs supported 107
UBR VLANs
modem train rates and 40 adding bridge 108
ULC card configuring 107
South Africa phone support for 195 IDs supported 107
unnumbered IP interfaces overview 107
description of 65 strip and insert 133
untagged bridging VoATM to TDM voice connections 208
described 105 voice
Uplink card always offhook 186
redundancy and IP addresses 16 configuring MGCP 163
Uplink cards configuring VOIP 162
configuration 16 hookflash 184
VOIP support and 200 hookflash timers 185

MALC Configuration Guide 277

Index

POTS to DS1 166

POTS to VOIP 165
VoATM to TDM connections 208
voice gateway 199
VOIP to TDM connections 202
voice configuration
checking bandwidth before accepting a call 156
PCM encoding supported 156
system profile 156
voice gateway
configuration 200
overview 199
VoATM to TDM connections 208
VOIP to TDM connections 202
Voice Gateway card
number of IGs supported 201
Uplink cards supported with 200
VP- and VC-switching on 209
VOIP
always offhook, configuring 186
call progress parameters 196
configuring voice gateway connections 162
hookflash, configuring 184
hookflash, configuring timers 185
malicious caller 193
POTS to VOIP 165
ring cadence 196
SIP connections 164
Uplink cards that support 200
VOIP to TDM voice connections 202
VPI
allowed ranges 24
VPLs
description 26

Z
ZMS
CLI configuration disabled 20
managing device with 19

278 MALC Configuration Guide