MALC Provisioning SE Training October 2005. Management There are three primary management...

MALC Provisioning

SE Training

October 2005

Management

There are three primary management interfaces:• Local Craft (serial) port for terminal access

• Ethernet port for standard IP address assignment and management

• RFC 1483 routed IP connection over the ATM interface (inband management)

Initial configuration must be done over the craft port. Once an IP address has been assigned, users can

manage the system using telnet (CLI), ZMS-LT, or ZMS. The MALC supports 5 concurrent telnet sessions and 1

console session.

Serial (Craft) Port

Communication parameters:• 9600 bps

• 8 data bits

• No parity

• 1 stop bit

• No flow control

(the default configuration of the serial port can be changed using an rs232-profile)

Login: admin Password: (default zhone)

• zSH> // CLI Prompt

To log out of the system use the “logout” command To enable or disable logging on the serial port:

• zSH> log session on | off

Exercise: Log into the serial port

Objective:• Log into the serial port (one session allowed)

using Hyperterminal or other terminal program

Configuring Management Interfaces

The MALC can be configured remotely using:

• Uplink card Ethernet Interface A single Ethernet interface on the Uplink card designed for

managing traffic

• ATM management connection Device terminates an ATM PVC and routes it over an

Ethernet interface for managing traffic

• ZMS ZMS communicates with the system using SNMP traps

Uplink Card Ethernet Interface

Ethernet interface on the Uplink card designed for management traffic.

The interface-add command specifies the basic parameters of the IP interface e.g. IP address and Netmask.

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.

Configuring the Ethernet IP Interface

The following examples configure the IP address for the system:

zSH> interface add 1-1-1-0/ethernetcsmacd 192.168.1.33/24

zSH> interface add 1-1-1-0/ethernetcsmacd vlan 999 192.168.1.33/24

zSH> interface show

In example 1, the IP address is untagged and in example 2, it is tagged using vlan id 999

Creating a default route

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

• route add default 192.168.1.1 1 Use the route show and route list commands to verify

that the route was added. Use the ping command to verify connectivity to the

default gateway. Use the interface show command

Exercise: Configure an Ethernet Interface and Route

Objective:• Provision the ip-interface-record for remote telnet

capability and add the default route• Use IP addresses provided by instructor• Log out of the console connection• Telnet to MALC using the IP address• Use the interface show command to verify that

the Ethernet interface was configured correctly• Use the route show/route list/interface show

commands to verify the route/connectivity• Use the ping command to verify connectivity to

the default gateway

Adding Users

• The adduser command creates a new user account and adds it to the database. The command also generates a random password which the user can change with the changepass command.

zSH> adduserPlease provide the following: [q]uit.User Name: jjsmithUser Prompt[zSH>]:Please select user access levels.admin: -------> {no}: yeszhonedebug: --> {no}:voice: -------> {no}:data: --------> {no}:manuf: -------> {no}:database: ----> {no}:systems: -----> {no}:tool: --------> {no}:useradmin: ---> {no}:..................................User name:(jjsmith) User prompt:(zSH>)Access Levels:(admin)Save new account? [s]ave, [c]hange or [q]uit: sUser record saved.TEMPORARY PASSWORD: sqgUr2J7

Changing Passwords

This command changes password for the current user.

zSH> changepassCurrent Password: New Password : Confirm New Password : Password change successful.

Updating Users

This command updates user privileges for an existing user.

Syntax updateuser usernameExample zSH> updateuser jjsmithUpdating access levels for user (jjsmith)Please provide the following: [q]uitadmin: -------> {yes}: nozhonedebug: --> {no}:voice: -------> {no}:data: --------> {no}:manuf: -------> {no}:database: ----> {no}:systems: -----> {no}:tool: --------> {no}:useradmin: ---> {yes}:Save changes? [s]ave, [c]hange or [q]uit: sUser record updated.

Exercise: Add Users/Change Passwords

Objective:• Via telnet session, add yourself as a user

• Use your first name as username

• Give yourself admin level privilege

• Change temporary password to your last name

• logout and log back in as a unique user

• showuser

• who

• msg

• changepass

• deleteuser

Note: logout + session # will terminate a telnet session.

Help

Displays help text for a command

Syntax: help [ -p ][ command ]

commandDisplays detailed help for the specified command.

-pDisplays the available commands, a brief explanation of the command,and the access level.

To get help on a particular command, enter the help command followed bythe name of the command. For example:

zSH> help slotsUse: slots [<slotNum>]This command displays the card type present in each slot. If <slotNum> is provided, it shows detailed information about the card.

Shortcuts

• Up/Down arrows

• Tab to auto complete some commands

• CTRL+U to clear line

• q to quit at any point in the command

• ESC+SHIFT A to place cursor at the far right

Other useful commands (not case sensit.)

Set2default Slotreboot Slots Log session on/off Msg (“msg all test” muestra un mensaje a todos los usr.) Disconnect Session # Timeout History (muestra los ultimos comandos ejecutados) Swversion Setdatetime Alarm show Showactivecards Showredundancy Showline Showlinestatus System-access Update system

Exercise: Set basic system parameters

Objective:• Provision the following parameters:

setdatetimeupdate system setcliprov timeout

CLI Basics

The CLI contains The CLI contains profilesprofiles, which are templates for , which are templates for configuring the system; configuring the system; recordsrecords, which are specific , which are specific instances of profiles; and instances of profiles; and commandscommands, which manipulate , which manipulate records or perform system functions (such as displaying records or perform system functions (such as displaying line status).line status).The 5 profile commands:

• list

• get

• update

• new

• delete

MALC Default Configuration

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

• A default system profile 0 exists with the following configuration: Authentication traps are not enabled ZMS communication is not configured

Profile Indexes

The CLI is based on profiles. These profiles are stored with an index. The index will either represent the physical port location or a user defined index number.

Indexes that represent a physical port location use the convention shelf-slot-port-subport/porttype

Examples:

1/10/5012= shelf/slot/cardid#1-1-1-0/ip - shelf/slot/port/subport

zSH> get if-translate 1-4-25-0/adsl -> s-s-p-s/t

zSH> get atm-traf-descr 99 -> user defined

List

The command list has two different functions: As a stand alone command, it will display all available

profiles list profile-type will list all instances of this “profile-

type:”

zSH> list if-translateif-translate 1-1-2-0/ethernetcsmacdif-translate 1-1-2-0-ethernetcsmacd/other2 entries found.

Get

The command get will retrieve a profile that exists on the device and display all of the configuration settings:

zSH> get system 0syscontact: -----------> {}sysname: --------------> {Z-Edge 64BH2A}syslocation: ----------> {}enableauthtraps: ------> {disabled}setserialno: ----------> {0}zmsexists: ------------> {false}zmsconnectionstatus: --> {inactive}zmsipaddress: ---------> {0.0.0.0}configsyncexists: -----> {false}configsyncoverflow: ---> {false}configsyncpriority: ---> {high}

Update

Update is used to make changes to the parameters of an existing profile:

zSH> update if-translate 1-12-3-0/voicefxsPlease provide the following: [q]uit.ifIndex: -----------> {43}: shelf: -------------> {1}: slot: --------------> {12}: port: --------------> {3}: subport: -----------> {0}: type: --------------> {voicefxs}:

adminstatus: -------> {down}: upphysical-flag: -----> {true}: iftype-extension: --> {none}: ifName: ------------> {1-12-3-0}: redundancy-param1: -> {0}:Save changes? [s]ave, [c]hange or [q]uit:s

New

The new command creates a new profile. Once this profile is saved, it is added to the working database. This is most commonly used with atm-vcl, atm-traf-descr, etc.

zSH> new atm-traf-descr 10Please provide the following: [q]uit.td_type: -----------------> {atmNoClpNoScr}: td_param1: ---------------> {0}: 3661td_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

Delete

Use delete in conjunction with a profile. The system will verify the delete before completing the command. Answering “[y]es” will delete the profile:

zSH> list atm-traf-descr atm-traf-descr 101 entry found.

zSH> delete atm-traf-descr 10atm-traf-descr 101 entry found.

Delete atm-traf-descr 10? [y]es, [n]o, [q]uit : yatm-traf-descr 10 deleted.

Show

The show command displays the default contents of profile and its parameter value ranges (partial ex.):

zSH> show ip-interface-recordvpi:---------------> {0 - 4095}vci:---------------> {0 - 65535}rdindex:-----------> {0 - 2147483647}dhcp:--------------> none client server bothaddr:--------------> {0 - -1}netmask:-----------> {0 - -1}bcastaddr:---------> {0 - -1}destaddr:----------> {0 - -1}farendaddr:--------> {0 - -1}mru:---------------> {0 - 2147483647}reasmmaxsize:------> {0 - 65535}ingressfiltername:-> {33}egressfiltername:--> {33}pointtopoint:------> no yes

Slots Command

Use the slots command to view all the cards in the system and their current state:

zSH> slots

1: MALC OC3F (RUNNING)

4: MALC GSHDSL (LOADING)

6: MALC XDSL 48 (LOADING)

Slots Command con’t

Use the Slots command with a slot number to get additional information:zSH> slots 8Type : MALC OLTCard Version : 11710100EEPROM Version : 1Serial # : 1640126CLEI Code : No CLEICard-Profile ID : 1/8/5031 Note the card profile IDShelf : 1Slot : 8State : LOADINGMode : NONEHeartbeat check : enabledLongest hbeat : 0Fault reset : enabled

Adding New Cards - MTAC

zSH> new card-profile 1/10/5003Please provide the following: [q]uit.sw-file-name: -----------> {}: malcmtac.binadmin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {false}: truesw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}: hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {unknowntype}: ds1card-atm-configuration: -> {notapplicable}:

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

Adding New Cards – Redundant UplinkzSH> new card-profile 1/2/5109Please provide the following: [q]uit.sw-file-name: -----------> {}: malcds3f.binadmin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {false}: truesw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}: 1 <- Must match active card (zero is

a valid ID)hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {unknowntype}: ds3card-atm-configuration: -> {notapplicable}: vbnrt65rt30 Must match

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

Adding New Cards – Voice Gateway

zSH> new card-profile 1/3/5040Please provide the following: [q]uit.sw-file-name: -----------> {}: malct1e132vg.binadmin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {false}: truesw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}: hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {unknowntype}: ds1card-atm-configuration: -> {notapplicable}:

Adding New Cards – ADSL 48

zSH> new card-profile 1/6/5036

Please provide the following: [q]uit.sw-file-name: -----------> {}: malcxdsl48ns.binadmin-status: -----------> {operational}:upgrade-sw-file-name: ---> {}:upgrade-vers: -----------> {}:admin-status-enable: ----> {enable}:sw-upgrade-admin: -------> {reloadcurrrev}:sw-enable: --------------> {false}: truesw-upgrade-enable: ------> {false}:card-group-id: ----------> {0}:hold-active: ------------> {false}:weight: -----------------> {nopreference}:card-line-type: ---------> {unknowntype}:card-atm-configuration: -> {notapplicable}:Save new record? [s]ave, [c]hange or [q]uit: s

Exercise: Create new card profiles

Objective:• Create new card-profiles for the system cards

Use the dir command to confirm the software is in the directory

Using the .bin image, create new card profiles for each card in the system

Use the showredundancy command for the uplinksConfirm the cards boot up properly

Note: • Card profile for slot 1 is automatically created• Redundant uplinks must have the same card-group-id

System Clocking

The MALC can receive system clocking from one of the following sources:• The DS1 interfaces on the T1/E1 Uplink card• The DS3 interface on DS3 Uplink card• The OC3-c/STM1 and OC12-c cards interfaces• The BITS clock source on the MTAC/Ring card

The system creates system-clock-profiles for each interface that can provide clocking for the system

If there are multiple active interfaces configured as eligible clock sources, the system selects a clock source based on the weight configured in the system-clock-profile

If a primary clock source is configured in the system profile – this clock source overrides all other clocks

Configuring System Clocking

Update the ds1-profile or sonet-profile or the ds3-profile to specify the type of clocking for the interface:• update ds1-profile shelf-slot-port-subport/ds1• update sonet-profile shelf-slot-port-subport/sonet• update ds3-profile shelf-slot-port-subport/ds3

Update the system-clock-profile to specify whether the clock is eligible and to assign a weight• update system-clock-profile shelf-slot-port-0/type

(type=ds1,ds3 or sonet)

To specify a system clock in the system-profile (clock-sources specified in the system-profile override settings in the system-clock-profiles):• update system 0

Clocking Parameters

transmit-clock-source (ds1-profile, ds3-profile or sonet profile) - there are three clocking options for DS1/DS3 interfaces

Values: • looptiming- The recovered receive clock from the line is

used as the transmit clock

• localtiming- A local clock source is used on the DS1/DS3 transmit signal

• throughtiming - The transmit clock is derived from the recovered receive clock of another interface

Default: looptiming (DS3), throughtiming (DS1)

Clocking Parameters - continued

primaryclocksource (in the system profile)• The shelf-slot-port-subport/type of an interface to provide

clocking for the system. For the BITS clock on the MTAC/Ring card, specify the address in the form shelf-slot-1-0/ds1

system-clock-eligibility (in the system-clock-profile)• Specifies whether the interface is eligible to provide clocking for

the system. Values: true false Default: false

system-clock-weight (in the system-clock-profile)• Assigns a weight to the clock source. If you assign weight to a

clock source that is higher than the currently active clock source, the system will switch over to that clock source.

• Values: 1 to 10 : 1 is the lowest priority, 10 is the highest Default: 5

Example: Configuring a OC3/STM1 Clock Source

Verify the clocking source interface is up and active Verify transmit-clock-source parameter in the sonet-profile is “looptiming” In the system-clock-profile enable the clock source – set the system-clock-

eligibility parameter to “true”

zSH> get sonet-profile 1-1-1-0/sonetmedium-type: -----------------> {sonet}medium-line-coding: ----------> {sonetmediumnrz}medium-line-type: ------------> {sonetshortsinglemode}medium-circuit-identifier: ---> {}medium-loopback-config: ------> {sonetnoloop}path-current-width: ----------> {sts3cstm1}clock-external-recovery: -----> {enabled}clock-transmit-source: -------> {looptiming}medium-cell-scramble-config: -> {true}medium-line-scramble-config: -> {true}

zSH> update system-clock-profile 1-1-1-0/sonetsystem-clock-eligibility: ---------------> {false}: truesystem-clock-weight: ---------------> {5}:

Revertive Clock Source

Redundant clock sources are revertive by default

If a standby clock source becomes active after the failure of a primary clock source – the system will revert to the primary clock source after the clock source becomes active

To disable revertive clock sources set the revertiveclocksource parameter in the system profile to “false”

Configuring a Clock Source in the System Profile

Clock sources configured in the system profile override settings in clock-source-profiles.

Typically, specifying a clock source in the system profile is not necessary, but can be use to manually change clock sources, or for testing purposes.

Configuring a Clock Source in the System Profile

The following example specifies that the first T1 interface on the Uplink card provides system clocking:

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 Raptor}: syslocation: ---------> {Oakland}: enableauthtraps: -----> {disabled}: primaryclocksource: --> {0/0/0/0/0}: 1-1-1-0/dslringsource: ----------> {internalringsourcelabel} revertiveclocksource -> {true}Save changes? [s]ave, [c]hange or [q]uit: s Record updated.

Viewing Clock Sources

Use the “clkmgrshow” command

Syntax:

• Clkmgrshow [current | eligible | list ] current – displays the current primary and secondary

clock sources eligible – displays only the eligible clock sources,

these are interfaces that are active and configured as eligible

list – lists the eligible and non-eligible clock sources

Exercise: Configuring System Clocking

Configure a DS1 or MTAC/Ring clock source:

• Verify that the interface is up and active with the showline command

• Set the transmit-clock-source parameter to looptiming with the update ds1-profile command

• Enable the clock source and change the default weight (if necessary) with the update system-clock-profile command

• Use the clkmgrshow command to ensure the clock is active

Review

ATM & ADSL Applications

ADSL technology ADSL turnup ATM technology ATM data

VP/VC cross-connects IMA

ATM voice

MALC ADSL/ATM Applications

xDSL Technology

xDSL Technology

Limitations include:

• Distance

• Gauge of copper wire

• Splices

• Interference

• Load coils

xDSL Types

Full Rate G.DMT G.Lite T1.413 G.hs ADSL2 ADSL2+ VDSL

xDSL Turnup

Admin Up the ADSL Port

zSH> update if-translate 1-5-1-0/adsl

Please provide the following: [q]uit.

ifIndex: -----------> {36}:

shelf: -------------> {1}:

slot: --------------> {5}:

port: --------------> {1}:

subport: -----------> {0}:

type: --------------> {adsl}:

adminstatus: -------> {down}: up

physical-flag: -----> {true}:

iftype-extension: --> {none}:

ifName: ------------> {1-5-1-0}:

redundancy-param1: -> {0}:

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

In single line format:

update if-translate adminstatus = up 1-5-1-0/adsl

Modify ADSL Transmission and Channel Mode

Modify/view the ADSL transmission and channel mode in the adsl-profile:

zSH> get adsl-profile 1/12/1adslLineConfProfile: ------------> {0000000088}adslAlarmConfProfile: -----------> {0000000088}adslTrellisModeEnabled: ---------> {true}adslNTRModeEnabled: -------------> {false}adslTransmissionMode: -----------> {autonegotiatemode}adslChannelMode: ----------------> {fastonly}adslMaxDownstreamToneIndex: -----> {511}adslMinDownstreamToneIndex: -----> {32}adslMaxUpstreamToneIndex: -------> {31}adslMinUpstreamToneIndex: -------> {6}adslPotsBypassRelayMaxDuration: -> {60}adslLineDMTConfMode: ------------> {freqdivmux}....................Save new record? [s]ave, [c]hange or [q]uit: sRecord updated.

Modify ADSL Port Speeds

Modify the ADSL downstream interface in the adsl-co-profile.

• zSH> update adsl-co-profile 1/12/1

Modify the ADSL upstream interface in the adsl-cpe-profile.

• zSH> update adsl-cpe-profile 1/12/1

Note that you can accept most of the default values.

Modify ADSL Port Speeds

Key fields in adsl-co-profile.• fastMinTxRate: ------------> {32000}

• interleaveMinTxRate: ------> {32000}

• fastMaxTxRate: ------------> {1536000}

• maxInterleaveDelay: -------> {63}

• interleaveMaxTxRate: ------> {1536000}

Key fields in adsl-cpe-profile.• fastMinTxRate: ------------> {32000}

• interleaveMinTxRate: ------> {32000}

• fastMaxTxRate: ------------> {1024000}

• interleaveMaxTxRate: ------> {512000}

Note that you can accept most of the default values.

View Modem Train Rate

zSH> dslstat 1-5-1-0/adslGeneral Stats:AdminStatus..................................UPDslUpLineRate (bitsPerSec)...................128000DslDownLineRate (bitsPerSec).................1024000DslMaxAttainableUpLineRate (bitsPerSec)......1184000DslMaxAttainableDownLineRate (bitsPerSec)....10528000Out Octets...................................0Out Discards.................................0Out Errors...................................0In Octets....................................0In Discards..................................0In Errors....................................0ATM OCD Count................................0ATM NCD Count................................0ATM HEC Count................................0ATM far-end OCD Count........................0ATM far-end NCD Count........................0ATM far-end HEC Count........................0<SPACE> for next page, <CR> for next line, A for all, Q to quit

View Port Status

zSH> showline 1 5Search in progress .........----------------------------------------------------------shelf = 1, slot = 5, line type = FASTline 1-12 ACT ----------------------------------------------------------shelf = 1, slot = 5, line type = DSLline 1-12 ACT OOS OOS OOS OOS OOS OOS OOS OOS OOS OOS OOS 13-24 OOS OOS OOS OOS OOS OOS OOS OOS OOS OOS OOS OOS ----------------------------------------------------------shelf = 1, slot = 5, line type = POTSline 1-12 ACT OOS OOS OOS OOS OOS OOS OOS OOS OOS OOS OOS 13-24 OOS OOS OOS OOS OOS OOS OOS OOS OOS OOS OOS

Exercise: Provision ADSL

Objective:Provision an ADSL circuit and connect modem.

Steps:update if-translate (admin up the ports)update adsl-profile (channel mode)update adsl-co-profile (downstream speeds)update adsl-cpe-profile (upstream speeds)dslstat (train rates)Showline (port status)

Connect modem to ADSL port before performing dslstat and showline commands.

ATM Technology

8

ATM Cell Structure

12345678

BIT

BYTE

1

2

3

4

5

6

53

Cell Payload(48 bytes)

GFC VPI

VPI VCI

VCI

VCI PT CLP

HEC

GFC: Generic Flow ControlVPI: Virtual Path IdentifierVCI: Virtual Channel IdentifierPT: Payload TypeCLP: Cell Loss PriorityHEC: Header Error Check

Cell Switching• Fixed size cells• 5 byte header, 48 byte payload

7

Cell Switching

Fixed size cells allow switching process to be optimized in hardware and introduce predictable delays in the network.

ATM switches examine only the cell header. 5 byte header introduces approx. 10% overhead in

every cell. Cells are identified and routed based on their VPI/VCI

numbers. Cells can support voice, video and bursty traffic by

interleaving different traffic types on the same physical link.

ATM Data

The MALC communicates with subscriber integrated access devices (IADs) or DSL modems using ATM over the DSL interface

Traffic is relayed to the uplink card which provides a high-speed interface to the ATM network

The system supports cross connects between DSL interfaces and the Uplink card, and between two VCLs on the same Uplink card. Cross connects between two DSL interfaces are not supported.

ATM Adaptation Layers (AAL)

AAL 1• Supports connection-oriented services (CBR, voice,

real-time video) AAL 2

• Supports connection-oriented services (VBR, voice, non-real-time video)

AAL 3/4• Supports connectionless and connection-oriented

services; not used in the U.S. AAL 5

• Used for data, high-speed internet, bursty, delay-tolerant traffic

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)

Service Categories

Service Category Description

CBR: Provides a fixed amount of bandwidth during the lifetime of the ATM connection. The CBR service category is intended to support real-time applications requiring tightly constrained delay variations, such as voice and video.

nrt-VBR: This category is intended for applications which have bursty traffic characteristics and do not have tight constraints on delay and delay variation.

Service Category Description

rt-VBR: This service is suitable for any application for which the end system can benefit from statistical multiplexing, by sending information at a variable rate. An example would be voice over ATM or video on demand applications.

UBR: This category represents a best effort attempt for traffic delivery. Examples of applications in this category are text, data and image applications. ADSL data traffic is typically UBR traffic.

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.

By default, oversubscription is not enabled and the cac-divider is set to 1.

For example, to oversubscribe bandwidth at a rate of 4:1, set cac-divider to 4 within the traffic descriptor.

The bandwidth allocated to ATM traffic types and used by CAC is specified in the card-atm-configuration parameter within the update card-profile command for the Uplink cards.

ATM Validation

The Zhone CLI performs the following validation on ATM Configurations:

• Virtual Channel Links (VCLs) cannot be created using Virtual Channel Identifiers (VCIs) in the reserved range (0 to 31)

• VCLs configured in a cross connect cannot be deleted. To delete a VCL, first delete the cross connect.

• ATM traffic descriptor used in a VCL cannot be modified

• A VCL can only be used in one cross connect

• If a VCL/VPL is updated with a new traffic descriptor, the VCL/VPL must be admin’d down, then admin’d up to update the policing value.

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 VPI only

A Virtual Channel Link (VCL) is used for VC switching – it is uniquely identified by an index in the form interface-index/VPI/VCI

A Virtual Path Link (VPL) is used for VP switching – it is uniquely identified buy an index in the form interface-index/atm/VPI

Virtual Channel and Virtual Path Switching

VPI and 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:

• Any VPI (0-255) and VCI (32-8,096) can be used for a VCL.

• After creating or modifying atm-vpi records, the card must be rebooted.

• A maximum of 256 VPIs can be created on a port.

• All MALC cards support 16,384 VC connections, except for the AAL5 cards, which support 32,768 connections.

VPI and VCI ranges

The traffic descriptor defines the characteristics of ATM traffic coming into the network and includes several negotiable traffic parameters: peak cell rate (PCR), sustained cell rate (SCR), and maximum burst size (MBS), etc.

These parameters define the average and peak bandwidth requirements

In the device, traffic descriptors are configured in using an atm-traf-descr record

A Traffic Descriptor in use cannot be modified

Traffic Descriptor

Traffic Descriptor

zSH> new atm-traf-descr 99


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:

ATM Cross-Connects

Crossconnect command usage• Requires pre-existing ATM Traffic Descriptor(s)• Creates the atm-vcl profiles for each side of the cross connect

as specified in the command• Creates the atm-cc profile to connect the two VCLs created• Creates the cross connect and admins it up

• Help cc – from the command line provides online help from the device on usage and parameters

crossconnect add 1-4-1-0/adsl vc 0/35 uplink1/atm vc 1/152 td 99

Interface VCL Status CC ID Status Interface VCL Status

1-4-1-0-adsl/atm 0/35 Up 1 Up uplink1/atm 1/152 Up

ATM Cross Connect

The “crossconnect” command can be shortened to “cc:”

zSH> cc add 1-4-3-0/adsl vc 0/35 uplink1/atm vc 1/152 td 99

zSH> cc show

ATM VCL CC ATM VCL

----------------------------------------------------------------------------



Exercise: Provision ATM cross-connects

Objective:Provision an ATM cross-connect.Steps:Create an ATM Traffic DescriptorUse the crossconnect add command to create the crossconnectUse the crossconnect show command to view CCsOther commands:

• list atm• list atm-vcl• get atm-vcl• update atm-cc 1 (index #)

Inverse Multiplexing over ATM (IMA)and ATM on uplink cards

Inverse Multiplexing & De-Multiplexing of ATM Cells

IMA Group IMA GroupPhysical link 00

Physical link 01

Physical link 02

IMA Virtual Link

Configuring IMA Groups

IMA involves inverse multiplexing and de-multiplexing of ATM cells in a cyclical fashion among physical links grouped to form a higher-bandwidth, virtual or logical link.

The rate of the logical link is approximately the sum of the rate of physical links in the IMA Group.

The IMA protocol is based on the inverse multiplexing of ATM cells over several physical links inter-connecting two nodes supporting the IMA protocol.

IMA groups terminate at each end of the IMA virtual link.

Configuring IMA Groups Con’t

For redundant systems, configure the IMA interfaces on both the active and standby cards.

The following MALC cards support IMA groups:

• T1/E1 IMA Uplink

• T1/E1-ATM-32 Before moving IMA links to another group, the system performs a CAC

calculation to determine whether moving the links will violate ATM QoS settings. If so, the link will not be moved.

If you do not want a link to belong to any IMA group, it is recommended that you admin down the interface in the if-translate profile.

Uplink must be set to the correct profile (card line type, ie: ds1-ima). Modify the card profile if necessary.

IMA provisioning steps

update if-translate (/ds1 ports and /atmima group) update ds1-profile update ima-group-profile imalink show

For 32 port T1 card, connect to the card (connect + slot #) then perform:

• imarpshow + ima group #

• ds1rpshow + ds1 (0 based)

Activating a DS1 Interface

zSH> update if-translate 1-3-1-0/ds1Please provide the following: [q]uit.ifindex: -----> {1}: . shelf: -------> {1}: slot: --------> {3}: port: --------> {1}: subport: -----> {0}: type: --------> {ds1}: adminstatus: -> {down}: up

physical-flag: ----> {true}: iftype-extension: -> {0}: ifName: -----------> {1-3-1-0}:Save changes? [s]ave, [c]hange or [q]uit: s

Updating a DS1 Profile

zSH> update ds1-profile 1-3-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: --------------------> {none}: 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}: Save changes? [s]ave, [c]hange or [q]uit: s

Updating ima-group Profiles

zSH> update ima-group-profile 1/3/1 (shelf/slot/port)


groupSymmetry: ---> {symmetricoperation}:

minNumTxLinks: ---> {1}: 4

minNumRxLinks: ---> {1}: 4

txClkMode: -------> {ctc}:

txImaId: ---------> {1}:

txFrameLength: ---> {m128}:

diffDelayMax: ----> {75}:

alphaValue: ------> {2}:

betaValue: -------> {2}:

gammaValue: ------> {1}:

testLinkIfIndex: -> {0/0/0/0/0}:

testPattern: -----> {-1}:

testProcStatus: --> {disabled}:

txTimingRefLink: -> {0}:

rxTimingRefLink: -> {0}:

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

Note: Typically you DO NOT want to udate the minimum number of links. This will cause IMA to fail if the minimum number is not met.

Showing IMA groups

zSH> imalink show 1-3-1-0/atmimaDS1 Links for IMA Group 1-3-1-0/atmima:If Index If Name--------- ---------------000736 1-3-1-0000737 1-3-2-0000738 1-3-3-0000739 1-3-4-0

Exercise: Provision IMA Groups

Objective:

Provision IMA groups.

Steps:

• update ds1-profile

• update if-translateFor DS1sFor the IMA group

• update ima-group-profile

• imalink show

ATM Uplinks

Uplink 1 and 2 on 2 port OC3/STM1 Uplink Uplink 1-4 on 4 port DS3/E3 Uplink card Change T1/E1 IMA card to UNI – now 8 uplinks Same on ATM/TDM uplink card (multiple uplinks on

ATM T1’s)

Regardless of interface type, they can generically be referred to as uplink1, uplink2, etc.

Used for redundancy (uplink1, uplink2, etc. become the corresponding ports on a redundant card when it is active)

ATM Voice Provisioning

ATM Voice

For voice traffic, the MALC supports derived voice using AAL2 over POTS interfaces (different from VG card)

The ATM traffic is sent to the Uplink card, then onto the ATM network.

The MALC supports 120 AAL2 VCLs.

Configure a POTS to AAL2 Subscriber

• Configure an ATM uplink

• Admin up the POTS port

• Create a new ATM traffic descriptor

• Add POTS subscriber with “voice” command

• View the voice subscribers

• Update the aal2-vcl-profile

• Update aal2-cid-profile

• Update analog FXS settings

ATM Traffic Descriptor

zSH> new atm-traf-descr 11Please provide the following: [q]uit.td_type: -----------------> {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}: 10td_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

Note: Parameters are based on the number of voice ports that will reside on the VC – see docs for guidelines.

Add POTS Subscriber

Use the “voice” command to create the AAL2 POTS subscriber. The following command will create a subscriber on card 5, port 3 and link that to the ATM uplink with VPI 0, VCI 40:

zSH> voice add pots 1-5-3-0/voicefxs aal2 uplink1/atm vc 0/40 td 1/1 cid 16Created subscriber 1/23Created subscriber-voice 1/23/1Created subscriber-voice-pots 1Created atm-vcl uplink1/atm/0/40Created aal2-cid-profile 26/0/40/16Created subscriber-voice-aal2 2

Exercise: Provision AAL2 voice

Objective:• Provision AAL2 voice service as instructed

GR-303

Full next generation Digital Loop Carrier (DLC)• Concurrent switching of TDM, Voice over ATM, and Voice over IP • Internal conversion from traditional access lines to packet formats• Line card investment protection:

Voice services trunked over TDM can be migrated to packet without change to line cards

Trunk-side Interfaces• TDM GR-303 and V5.2• Voice over ATM (AAL2)• Voice over IP (MGCP/SIP)

Line-side Interfaces• Analog POTS

Up to 432 subscribers in 7-U shelf Integrated ringer

• Voice specials Coin P-Phone ISDN

Overview of Functions: Voice

POTSISDN

Coin

Packet

P-PhoneCoin

Technical Detail TDM Voice

As a Traditional Digital Loop Carrier

• Supports POTS and Specials GR-303/V5.2 applications

• Up to 2 IG (interface groups) per MALC

• Call Progress1) Off-hook at premises

2) POTS terminated on MALC POTS card and A/D conversion

3) Echo cancellation on POTS card

4) Call traverses MALC TDM backplane

5) Out TDM functions on Uplink card

6) Call setup on GR303 or V5.2 out to Local Exchange switch for dial tone and call control

POTS

TDM Backplane

EchoCancellation

TDM on

UplinkPOTS

Card

Off-hook

PSTN

T1-GR303E1-V5.2

Class 5 / LECall Control

GR303 Configuration

303 Guidelines

The MALC TDM Uplink card supports GR-303 to a PSTN switch. The MALC can connect ATM or POTS subscriber interfaces to the PSTN.

GR-303 allows concentration from 1:1 to 44:1, a timeslot management channel (TMC) data link that uses messages for call setup and tear down, the use of signaling bits to indicate call control, and a separate embedded operations channel (EOC) data link.

The primary and secondary T1 circuits each carry the EOC and TMC for redundancy (timeslots 12 and 24)

Support for 2048 CRVs per interface group (IG) Two IGs supported 4096 CRVs per system

GR-303 Provisioning Steps

• Activate the DS1 interfaces

• Update the DS1 profiles

• Allow the system to accept clocking from the GR303 DS1s

• Verify the lineGroup ID for the DS1

• Create the GR303 Interface Group

• Activate the GR303 Interface Group

Activate the T1 Ports

zSH> update if-translate 1-1-1-0/ds1


ifIndex: -----------> {33}:

shelf: -------------> {1}:

slot: --------------> {1}:

port: --------------> {1}:

subport: -----------> {0}:

type: --------------> {ds1}:

adminstatus: -------> {down}: up

physical-flag: -----> {true}:

iftype-extension: --> {none}:

ifName: ------------> {1-3-1-0}:

redundancy-param1: -> {0}:

Update T1 SettingszSH> update ds1-profile 1-1-1-0/ds1Please 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}:cell-scramble: ------------------> {true}:coset-polynomial: ---------------> {true}:protocol-emulation: -------------> {network}:signal-type: --------------------> {loopstart}:ds1-group-number: ---------------> {0}:line-power: ---------------------> {disabled}:

System Clock Source

zSH> update system-clock-profile 1-1-1-0/ds1


system-clock-eligibility: -> {false}: true

system-clock-weight: ------> {5}:

Verify System Clock

zSH> clkmgrshow

Primary system clock is 1/1/1/0 : T1

Secondary system clock is 1/1/2/0 : T1

zSH> clkmgrshow list

eligible list has 2 entries

1 * eligible 1/1/1/0 ( 5) : T1 : ACTIVE : LOOP

2 eligible 1/1/2/0 ( 5) : T1 : ACTIVE : LOOP

ineligible list has 2 entries

1 not eligible 1/1/3/0 ( 5) : T1 : OOS : THROUGH

2 not eligible 1/1/4/0 ( 5) : T1 : OOS : THROUGH

Verify the T1 LineGroup Number

To configure the GR303 Interface Group, the LineGroup ID number is needed to attach the T1 to the Interface Group. This number is auto-assigned by the system.

zSH> lineGroup 1-3-1-0/ds1

lineGroupId: 34

zSH> linegroup 1-3-2-0/ds1

lineGroupId: 36

Configure the Interface Group Leave the Group out of service, we will go back at the end to enable.zSH> new gr303-interface-group 1Please provide the following: [q]uit.name-id: -----------------------> {}: gr303switch-type: -------------------> {lucent5ess}: norteldms100adminStatus: -------------------> {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 32 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? s

Configure the Interface Group Con’t

ds1LM[1]:

dsn-lg-id: ---------------------> {1}: 34 channel-number: ----------------> {1}:

role: --------------------------> {payload}: primary

logical-id: --------------------> {28}: 1

ds1-valid-flag: ----------------> {invalid}: valid

ds1LM[2]:

dsn-lg-id: ---------------------> {1}: 36 channel-number: ----------------> {1}:

role: --------------------------> {payload}: secondary

logical-id: --------------------> {28}: 2

ds1-valid-flag: ----------------> {invalid}: valid

Activate the Interface Group

After the Group is configured and saved, place it inservicezSH> update gr303-interface-group 1Please provide the following: [q]uit.name-id: -----------------------> {gr303}: switch-type: -------------------> {lucent5ess}:

adminStatus: -------------------> {outofservice}: inserviceworking-mode: ------------------> {active}: 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?

Modify [a]ll, [n]one, a [s]ubset, or [q]uit? nUsing current values for elements 1-28

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

303 Cross-Connects

Activate POTS port Add POTS subscriber with ‘voice’ command View voice subscribers Update analog FXS settings, if necessary

Activate the POTS Port

Perform this step for every POTS port you are going to use.

zSH> update if-translate 1-8-1-0/voicefxsPlease provide the following: [q]uit.ifIndex: -----------> {228}: shelf: -------------> {1}: slot: --------------> {8}: port: --------------> {1}: subport: -----------> {0}: type: --------------> {voicefxs}:

adminstatus: -------> {down}: upphysical-flag: -----> {true}: iftype-extension: --> {none}: ifName: ------------> {1-8-1-0}: redundancy-param1: -> {0}: ....................Save changes? [s]ave, [c]hange or [q]uit:

Add POTS cross-connect

Use the voice command to add the POTS to GR303 connection. This example creates a POTS to GR303 subscriber profile with IG 1

and CRV 2:

zSH> voice add pots 1-8-1-0/voicefxs gr303 1/2Created subscriber 1/13Created subscriber-voice 1/13/1Created subscriber-voice-pots 20Created gr303-ig-crv 1/2Created subscriber-voice-gr303 21

zSH> voice show 1-8-1-0/voicefxsSubscriber end-point Remote end-point Voice Prof Id STA------------------------------ ------------------------------ -------------- ---1-8-1-0/voicefxs GR303 Zhone/2 1/13/1 ENATotal number of voice connections : 1

Update Port Settings

If needed, the fxs ports can be modified with the following commands:

zSH> update analog-fxs-cfg-profile 1-8-1-0/voicefxs

zSH> update analog-if-cfg-profile 1-8-1-0/voicefxs

Exercise: Provision 303 IG and build cross-connects

Objective:• Provision a 303 interface group

• Provision 303 to POTS cross-connects

• Use rp303 show commands (0 based)

• Use ds1rpshow command

• Use showline command

Note: Use CRVs 4 and 5 for cross-connects

Team# POTS circuit CRV#

Module 4: Bridging

Technical Detail Ethernet Bridging

Technical Detail Ethernet (cont.) VLAN Capabilities of Uplinks (“IP/ATM” Cards)

• VLAN IEEE 802.3Q VLAN tagging to separate voice, data and video traffic Offer different QoS levels for different types of traffic

• VLAN tagging to separate data traffic for different applications Business subscribers may use VLAN to create virtual LANs Carriers may offer residential subscribers special services based on VLANs

• Specifications VLAN tagging on uplink and downlink ports Support for tagged and untagged interfaces Support for full range of 4,096 VLANs Learning or static bridging

ATM / Ethernet

VLAN 1

VLAN 2

VLAN 3

VLAN 1(Tagged)

VLAN 1VLAN 2VLAN 3

Technical Detail Ethernet Bridging

CPE

Packet Backplane

Ethernet/ATM

VLAN tag assigned

Router/SMSVLAN termination

Data

Ethernet/ATM

Switch

Ethernet/ATM

Tagged packets sent upstream

Uplinks support Ethernet Bridging• Terminate ATM VC’s on the Uplink

• Assign VLAN IDs on a per ATM VC basis Subtending ports can be assigned to forward VLAN traffic

without removing tags

• Forward frames based on Ethernet MAC address Forwarding table supports static and dynamic MAC address

entries

• Processed frames can be sent upstream over ATM interfaces (AAL5 VC) or Ethernet interfaces

PacketUplink

ATMLine Card

Bridging

Bridging involves configuring the MALC to direct traffic based on Ethernet MAC addresses.

The MALC supports the two types of bridges, tagged and untagged.

Tagged or Virtual LANs (VLANs) bridging 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 or transparent bridging 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.

Bridging

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.

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.

Configuring a VLAN bridge on the upstream interface

zSH> bridge add 1-1-2-0/ethernetcsmacd uplink zSH> list bridge-interface record This command adds a learning bridge that accepts VLAN

traffic and enables VLAN trunking on the MALC’s egress Ethernet port.

Configure the uplink interface to learn the VLAN IDs of all ingress Ethernet devices or a specific VLAN ID:

• zSH> bridge-path add ethernet1-2/bridge global

• zSH> bridge-path show The global setting specifies that the MALC should send

all VLAN traffic to this port. A VLAN [VLAN ID] setting can also be used when the MALC should send only traffic from a specific VLAN ID to this port.

Configuring a VLAN bridge on the downstream port

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, sets the parameters to the downlink settings, and assigns port VLAN ID 555.

bridge show

Test the bridge by pinging a device on the far end network and verifying that the bridge table is updated:

zSH> bridge showVLAN Bridge State Table Data-----------------------------------------------------------------0 1-8-2-0-adsl-0-101/bridge UP D 00:01:47:cf:ae:040 1-1-1-0-ethernetcsmacd/bridge UP D 00:01:02:70:03:a2

Exercise: Provision a Bridged Subscriber

Objective:• Provision a bridged subscriber as instructed

• Use the bridge delete command after completionEx: bridge delete ethernet1-2/bridgeEx: bridge delete 1-3-1-0/adsl vc 0/35/bridge

Note:

A traffic descriptor is required. Remember also to admin up ports.

-t is used for a constant ping

CTRL+C to stop ping

Module 5: IP

IP terminations Routing VoIP IGMP

MALC IP Applications

Technical Detail IP Data

CPE

Packet Backplane

Ethernet/ATM

IP addressing assigned

PacketUplink

DSLCard

Router

Data

Ethernet/ATM

Switch

Ethernet/ATM

IP packets routedupstream

Uplinks support IP routing functionality• Terminate ATM VC’s on the Uplink

• Assign IP addressing information on each ATM VC Support for host routes and IP subnets Support for static and dynamic address allocation

• Forward packets based on IP address

• Processed frames can be sent upstream over ATM interfaces (AAL5 VC) or Ethernet interfaces

The MALC provides the following IP services:• IP forwarding and routing• DHCP servers to simplify user IP address configuration.• IP filtering• 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.• ATM/IP Uplink cards are required for IP services. The ATM/IP Uplink

cards terminates the IP traffic.• DSL interfaces. IP on DSL runs over ATM PVCs using RFC 1483

encapsulation.

MALC IP Services

Unnumbered IP interfaces reduce the number of IP addresses used by adevice. 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 theip-interface-record.

Unnumbered IP Interfaces

Host-based routing takes advantage of IP unnumbered interfaces and sharedDHCP pools to conserve IP addresses. In the host-based routing with DSLbridges application, subscribers connected to the MALC are on the samesubnet as the MALC unnumbered interface.

Host-Based Routing w/ DSL bridges

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

Host-Based Routing w/ DSL routers

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

Network-Based Routing w/ DSL bridges

Network-based routing with DSL routers allows multiple statically assignedaddresses per customer. In this application, each remote router is on a subnetwith a numbered interface on the MALC.

Network-Based Routing w/ DSL routers

• 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, dhcp is not assigned and the customer must manually configure their device to match the MALC’s setting (typically used for DSL routers)

DHCP support within the MALC

DHCP Relay

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

DHCP Relay

• Provision an Uplink• Provision an ATM traffic descriptor• Provision the unnumbered, or floating interface• Provision the IP interface record• Provision DHCP server subnet groups• Provision the host connections• Add Routes• Verify provisioning

Provisioning for host-based routing

Provision an Uplink port:

Provision an Uplink

zSH> interface add 1-1-2-0/ethernetcsmacd static 192.168.40.200 255.255.255.0

created ip-interface-record ethernet1/ipzSH> interface show

Provision an atm-traf-descr for the unnumbered interfaces:

Provision an Traffic Descriptor

zSH> new atm-traf-descr 100Please provide the following: [q]uit.td_type: -----------------> {atmNoClpNoScr}:td_param1: ---------------> {0}: 106133td_param2: ---------------> {0}: 38td_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: sNew record saved.

Create an ip-interface-record for the IP address that is to be shared forall devices in the host-based routing subnet. The example uses the name/type syntax:

Provision the Unnumbered Interface

zSH> new ip-interface-record ptm1/ipPlease provide the following: [q]uit.vpi: ---------------> {0}:vci: ---------------> {0}:rdindex: -----------> {1}:dhcp: --------------> {none}: ** read-only **addr: --------------> {0.0.0.0}: 10.0.0.1netmask: -----------> {0.0.0.0}: 255.0.0.0bcastaddr: ---------> {0.0.0.0}: 10.255.255.255destaddr: ----------> {0.0.0.0}:farendaddr: --------> {0.0.0.0}:Save new record? [s]ave, [c]hange or [q]uit: sCannot determine binding for this IP interface.Could not automatically bind this IP InterfaceNew record saved.

Create an ip-unnumbered-record for the IP interface you just created.Enter the name/type used in for ip-interface-record (from previous step)

as the ipUnnumberedinterface value:

Provision the IP interface record

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

Create a dhcp-server-subnet record for each customer, specifying therange (or pool) of assignable addresses which that customer can beassigned: (This is shortened screen capture):

Provision the DHCP server subnets

zSH> new dhcp-server-subnet 1Please provide the following: [q]uit.network: ---------------> {0.0.0.0}: 10.0.0.0netmask: ---------------> {0.0.0.0}: 255.0.0.0domain: ----------------> {0}: 1range1-start: ----------> {0.0.0.0}: 10.0.0.10range1-end: ------------> {0.0.0.0}: 10.0.0.20bootfile: --------------> {}:default-router: --------> {0.0.0.0}: 10.0.0.1…subnetgroup: -----------> {0}: 1 This number does not have to match the subnet index

stickyaddr: ------------> {enable}:external-server: -------> {0.0.0.0}: Use this to specify a dhcp relay server – overrides all other settingsSave new record? [s]ave, [c]hange or [q]uit: s

The following example adds dynamically assigned hosts:

zSH> host add 1-11-1-0/adsl vc 0/35 txtd 100 rxtd 100 llc dynamic 1 3

Provision the host connections

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– uses atm-traf-descr 100– adds 3 host entries that will have their addresses assigned dynamically as defined by subnetgroup 1.

Verify that hosts have been added:

Provision the host connections

zSH> host showzSH> cc showzSH> host show interfacezSH> help host

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

route add destination mask next-hop cost

• 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

Note: The word default can be substituted for a 0.0.0.0 destinationand mask.

Add routes

• Objective:• Provision IP subscriber services as instructed• After provisioning, connect PC to modem and perform

release and renew to get a DHCP address from the MALC.

Exercise: Provision IP subscribers

VoIP Configuration

Verify voip-system Setup

On initial setup verify the MALC is set for SIP:

zSH> get voip-system 0

protocol: ------------------> {sip}

send-call-proceeding-tone: -> {false}

rtcp-enabled: --------------> {false}

rtcp-packet-interval: ------> {5000}

interdigit-timeout: --------> {10}

ip-tos: --------------------> {0}

system-domain-name: --------> {}

Management Address

If you haven’t already added an IP interface for VoIP trunking, use the “interface” command to add a new IP interface (can also be added to an Ethernet port):

zSH> interface add uplink1/atm vc 0/32 td 1 192.168.1.100/24

zSH> route add default 192.168.1.1 1

Add VOIP Server

As part of initial VOIP setup, add a proxy server:

zSH> new voip-system 0 protocol: ------------------> {sip} send-call-proceeding-tone: -> {false} rtcp-enabled: --------------> {false} rtcp-packet-interval: ------> {5000} interdigit-timeout: --------> {10} ip-tos: --------------------> {0} system-domain-name: --------> {davinci.datcon.co.uk}

VoIP Configuration

zSH> get voip-server-entry 1/1 zhoneVoipServerAddrType: ------> {ipv4} zhoneVoipServerAddr: ----------> {217.19.130.234} zhoneVoipServerUdpPortNumber: -> {5060} zhoneVoipServerId: ------------> {metaswitch}

VoIP Configuration

zSH> get sip-dialplan 2 match-string: ------------> {1530} sip-ip-address: ----------> {217.19.130.234} destination-name: --------> {} number-of-digits: --------> {11} prefix-strip: ------------> {0} prefix-add: --------------> {} dialplan-type: -----------> {normal} voip-server-entry-index: -> {1}

Turn Up the POTS Ports

Perform this step for every POTS port you are going to use:

zSH> update if-translate 1-5-1-0/voicefxsPlease provide the following: [q]uit.ifIndex: -----------> {228}: shelf: -------------> {1}: slot: --------------> {5}: port: --------------> {1}: subport: -----------> {0}: type: --------------> {voicefxs}: adminstatus: -------> {down}: upphysical-flag: -----> {true}: iftype-extension: --> {none}: ifName: ------------> {1-5-1-0}: redundancy-param1: -> {0}: ....................Save changes? [s]ave, [c]hange or [q]uit:

Single line command: update if-translate adminstatus = up 1-5-1-0/voicefxs

VoIP Configuration zSH> voice show Subscriber end-point Remote end-point Voice Prof Id STA ------------------------------ ------------------------------ -------------- --- 1-4-1-0/voicefxs ethernet2-304/ip DN 5305413001 1/4/7 ENA 1-4-2-0/voicefxs ethernet2-304/ip DN 5305413002 1/4/8 ENA Total number of voice connections : 2

zSH> voice add pots 1-4-3-0/voicefxs voip ethernet2-304/ip dn 5305473003 name 5305413

3003 pw zhonepw reg 1 Created subscriber-voice 1/4/9 Created subscriber-voice-pots 17 Created subscriber-voice-voip 18

zSH> voice show Subscriber end-point Remote end-point Voice Prof Id STA ------------------------------ ------------------------------ -------------- --- 1-4-1-0/voicefxs ethernet2-304/ip DN 5305413001 1/4/7 ENA 1-4-2-0/voicefxs ethernet2-304/ip DN 5305413002 1/4/8 ENA 1-4-3-0/voicefxs ethernet2-304/ip DN 5305473003 1/4/9 ENA Total number of voice connections : 3

Modify subscriber-voice Profiles

zSH> update subscriber-voice 1/5/1


voice-connection-type: --------> {voiptopots}: ** read-only **

voice-endpoint1-addr-index: ---> {2}: ** read-only **


voice-connection-description: -> {}:

voice-admin-status: -----------> {enabled}: disabled

huntgroup: --------------------> {false}: ** read-only **

features: ---------------------> {hookflash+onhooksignaling}:

....................


Modify subscriber-voice Profiles (cont.)

zSH> list subscriber-voice-voip subscriber-voice-voip 21 entry found.

zSH> update subscriber-voice-voip 2Please provide the following: [q]uit.voip-username: -------------> {5107771001}: directory-number: ----------> {5107771001}: ip-interface-index: --------> {uplink1-0-32/ip}: preferred-codec: -----------> {g711mu}: g711-fallback: -------------> {true}: frames-per-packet: ---------> {1}: 4g726-byte-order: -----------> {bigendian}: voip-password: -------------> {}: 5107771001voip-plar: -----------------> {false}: ** read-only **voip-plar-dest-ipaddrtype: -> {ipv4}: voip-plar-dest-ipaddr: -----> {}: voip-plar-udp-port: --------> {5060}: Save changes? [s]ave, [c]hange or [q]uit:

Modify subscriber-voice Profiles (cont.)

zSH> update subscriber-voice 1/5/1


voice-connection-type: --------> {voiptopots}: ** read-only **



voice-connection-description: -> {}:

voice-admin-status: -----------> {enabled}: enabled

huntgroup: --------------------> {false}: ** read-only **

features: ---------------------> {hookflash+onhooksignaling}:

....................


Add the SIP Dial Plan

zSH> new sip-dialplan 1


match-string: -----> {}: x

sip-ip-address: ---> {0.0.0.0}: 192.168.1.200

destination-name: -> {}:

number-of-digits: -> {0}: 10

prefix-strip: -----> {0}:

prefix-add: -------> {}:

....................

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

SIP Troubleshooting (Lab Only)

Make sure that the session logging is on:

zSH> log session on

Change the SIP logging level to debug:

zSH> log level sipstack infoModule: sipstack at level: infozSH>

To return the SIP message logging to normal:

zSH> log level sipstack errorModule: sipstack at level: errorzSH>

SIP Troubleshooting

To print the current SIP registration information use the sipstack reg command.

zSH> sipstack reg5107771047@(null) (TRUE/3600s/366s)5107771046@(null) (TRUE/3600s/366s)5107771045@(null) (TRUE/3600s/366s)5107771044@(null) (TRUE/3600s/361s)5107771043@(null) (TRUE/3600s/361s)5107771042@(null) (TRUE/3600s/361s)5107771041@(null) (TRUE/3600s/361s)5107771040@(null) (TRUE/3600s/361s)5107771039@(null) (TRUE/3600s/361s)5107771038@(null) (TRUE/3600s/361s)

There are 10 SIP Registrations

zSH>

SIP Troubleshooting

zSH> ccrp show terms

UP ACT VOIP:33:VOIP EndPtIdx-2 -> POTS:40:1:0:0:0

UP ACT VOIP:33:VOIP EndPtIdx-4 -> POTS:42:1:0:0:0

UP ACT POTS:40:1:0:0:0 -> VOIP:33:VOIP EndPtIdx-2

UP ACT POTS:42:1:0:0:0 -> VOIP:33:VOIP EndPtIdx-4

There are 4 terms

zSH>

Modify POTS Physical Settings (If Necessary)

You can modify the tlp settings to fix problems such as echo.

zSH> update analog-if-cfg-profile 1-5-1-0/voicefxs


if-cfg-impedence: ----------> {ohms900complex}:

if-cfg-receive-tlp: --------> {fxsrtlp0db}:

if-cfg-transmit-tlp: -------> {fxsttlp6db}:

if-cfg-trunk-conditioning: -> {idle}:

if-maintenance-mode: -------> {off}:

if-cfg-pcm-encoding: -------> {mulaw}:

if-cfg-receive-tlpNum: -----> {0}:

if-cfg-transmit-tlpNum: ----> {0}:

....................


MTAC Testing

To connect a port to the MTAC test port:zSH> update mtac-profile 1


ifIndex: ---> {0/0/0/0/0}: 1/5/1/0/adsl

test_mode: -> {mtacmodenone}: mtacmodelookout

....................


To disconnect a port from the MTAC test port:zSH> update mtac-profile 1


ifIndex: ---> {1-5-1-0/adsl}: 0/0/0/0/0

test_mode: -> {mtacmodelookout}: mtacmodenone

....................


Exercise: Provision VoIP

Objective:• Provision VoIP as instructed

Maintenance

Maintenance

Alarms Upgrades Backups Restores Trouble-shooting

Alarms

Alarm Commands:

• Alarm show

• Alarm show summary

Logging

To enable logging:

• zSH> log session on To disable logging:

• zSH> log session off

The “log serial” command enables/disables logging messages on the serial craft port.

To enable logging:

• zSH> log serial on To disable logging

• zSH> log serial off log display log cache

Setting up a TFTP server

Zhone recommends a TFTP server by 3Com: The path is:

• http://support.3com.com/software/utilities_for_windows_32_bit.htm

The file is called:3CDv2r10.zip

Follow the download instructions MALC software loads can be found at:

• ftp://ftp.zhone.com/support/software/MALC-RAPTOR/

File System

The Uplink card flash memory contains the file system that stores the system boot code, software images, and the system configuration.

The following commands can be used to access the file system:

• cd: change directory

• dir: lists the contents of the directory

• pwd: displays the current working directory

• image: verifies software image

• del: deletes a file

• ata: used to format or initialize a flash card.

Upgrade Overview

• Zhone recommends that you back-up your configuration to a TFTP server with the dump command before upgrading software.

• Use the restore command to return the configuration after the software upgrade.

• Both Uplink cards in a redundant pair must have flash cards of the same size and must be running the same software version.

• Ensure all redundant and spare uplink cards are upgraded to the current software version.

Backing Up & Restoring Configuration

The “dump” and “restore” commands allow users to save and restore the system configuration to/from console, a local file or the network

The command uses the following syntax:

• dump console (works in conjunction with the file capture utility of the terminal emulation software)

• dump file filename (specify a file name for the configuration – the file is saved on the local file system)

• dump network host filename (e.g. “dump network 192.168.8.21 device.cfg” – the configuration is saved to a file named device.cfg on the host 192.168.8.21)

Creating the onreboot directory

The MALC requires a directory called onreboot/ to be created in order to perform a restoration:

• Use the dir command to confirm if the directory exists

• If not, create a directory called onreboot: zSH> cd /card1 zSH> mkdir onreboot

Performing Backups and Restores

Backups can be performed locally (on the flash card) or to a TFTP server with the dump command.

To perform a local backup in the onreboot directory:• EX: dump file testtoday.cfg

Copy the backup into the onreboot directory and rename it ‘restore:”• zSH> copy testtoday.cfg /onreboot/restore

Or, to backup via an TFTP server:• dump network 192.168.40.69 testtoday.cfg

Copy the previously saved dump file (on the TFTP server) to the onreboot directory and rename it restore:• file download 192.168.40.69 testtoday.cfg onreboot/restore

Change directory to onreboot and list file:• cd onreboot then type dir

Use the set2default (or systemreboot) command to erase the system configuration and restore the configuration.

Performing Restores Con’t

During the reboot, the system will look for the file named restore in the onreboot directory. It will use this file to recreate the configuration files in the datastor directory.

After the restore is finished, it renames the restore file to restore.done.

• -rwxrwxrwx 1 0 0 31417 Aug 29 10:11 restore.done

Delete this restore file after reboot:

• zSH> del restore.done

Performing Upgrades with 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• image download 192.168.8.21 Raptort1ima.bin

Raptort1ima.bin Verify the image download:

• zSH> image verify Raptort1ima.binFile: Raptort1ima.binSize: 3186874 bytesHeader Version: 1Load Type: Raptor UPLINK NT1Load Address: 0x00010000Checksum: 0x0c847b68Image verify successful

Upgrade Procedure

1. Verify you are at the root of the flash card:zSH> cd /card1zSH> pwd/card1/

2. Back up the current configuration file to the flash card:zSH> mkdir onrebootzSH> cd onrebootzSH> dump file restoreThis file will be used to restore the system configuration or revert to aprevious release, if desired.

3. If desired, save the configuration file to a host on the network:

zSH> dump network 192.168.8.21 malc.cfg

4. Change directories to the root of the flash card:zSH> cd /card1zSH> pwd/card1/

Upgrade Procedure Con’t

5. If desired, save the existing software images on the flash card by copyingthem to a different file name. For example:zSH> copy malcpots.bin malcpots.bin.savCopy the rest of the software images in the same way.

6. Download the latest system image software for the Uplink cards to thesystem flash using the image command. The command uses the following syntax:image download TFTPserverAddress sourcefilename [destinationfilename]

7. Download the latest system image software for each slot card installed in the system using the image command. The command uses the following syntax:image download TFTPserverAddress sourcefilename destinationfilename

Upgrade Procedure Con’t

8. Initialize the flash card’s boot partition with the new image on both theprimary and standby Uplink card. For example:GE-2 Uplink:zSH> image flash malcrprgige.bin 1 all

9. Use the set2default command to erase the system configuration:zSH>set2defaultOk to reset to default (system will reboot) ? [yes] or[no]: yesDuring the reboot, the system will look for the file named restore in theonreboot directory, then use that file to recreate the configuration files inthe datastor directory. After the restore is finished, it renames the restorefile to restore.done.The system reboots again with the new configuration.

Caution: Do not leave a file named restore in the onrestoredirectory unless you are going to restore the system configurationfrom a previously saved configuration. Doing so may causeunintended results if you reboot the system.

Loopbacks

The Raptor/Malc supports: T1 , DS3 and SONET Loopbacks

The loopback-config parameter in the ds1-profile controls T1 loopbacks

The loopback-config parameter in the ds3-profile controls DS3 loopbacks

The medium-loopback-config parameter in the sonet-profile specifies the type of loopback

T1 Loopback Options

The loopback options that can be specified within the loopback-config are:

• noloop: not in the loopback state

• lineloop: the received signal on this interface does not go through the device (minimum penetration) but it is looped back

• payloadloop: the received signal on this interface does not go through the device (minimum penetration) but is looped back

Loopbacks disrupt interface traffic

Use the if-translate profile to set the adminstatus of the line to testing before initiating a loopback

Activating/Deactivating T1 Loopbacks

zSH> update ds1-profile 1-1-1-0/ds1


line-type: ----------------------> {esf}:

line-code: ----------------------> {b8zs}:

send-code: ----------------------> {sendnocode}:

circuit-id: ---------------------> {ds1}:

loopback-config: ----------------> {noloop}: lineloop



line-type: ----------------------> {esf}:

line-code: ----------------------> {b8zs}:

send-code: ----------------------> {sendlinecode}:

circuit-id: ---------------------> {ds1}:

loopback-config: ----------------> {lineloop}: noloop

BER Tests

The send-code parameter in the ds1-profile controls BER tests on the T1 interface – the BERT options are:

• sendQRSSPattern: sends a quasi-random signal as a test pattern

• send511Pattern: sends a 511 bit fixed test pattern

• send3in24pattern: sends a fixed test pattern of 3 bits set in 24

• send2047Pattern: send 2047 test pattern

• send1in2Pattern: sends alternate one/zero pattern

Activating/Deactivating BERT



line-type: ----------------------> {esf}:

line-code: ----------------------> {b8zs}:

send-code: ----------------------> {sendnocode}: sendqrsspattern

circuit-id: ---------------------> {ds1}:



line-type: ----------------------> {esf}:

line-code: ----------------------> {b8zs}:

send-code: ----------------------> {sendqrsspattern}: sendnocode

circuit-id: ---------------------> {ds1}:

Objectives:

•See ZMS general for “what is ZMS”

•Provisioning

ZMS LT

ZMS Provisioning

ZMS Connectivity

ZMS is a client / server based program. This means the user downloads the client application to talk to the server.

All configuration steps, device information, alarm management, etc. is done by the server.

Software upgrades are done on the server, and published to the clients.

ZMS Connectivity

In-band

• IP over ATM AAL5 VC terminated on uplink card

Out-of-band

• IP over 10/100 Ethernet connection on Uplink

ZMS Connectivity

If the ZMS server is not referenced by the network DNS server, then modify the local hosts file on the PC client – located in:

C:/winnt/system32/drivers/etc

Notepad the “hosts” file and provide the IP and hostname of the server. ZMS internally references the server name so this is required for ZMS operations.

ZMS Connectivity

Using a browser, open the browser to port 7001. In this case, the ZMS server is named:

znetra13

So the url is:

http://znetra13:7001/

At the index page, right click on the “HERE” links and select “Save as…” and save this to a local directory (any location is acceptable)

Common locations include the desktop or a c:\zhone directory.

ZMS Connectivity

Navigate to the directory where the ZMS files were placed. In this case:

C:\zms\znetra_eng

Double-click the “load_zms” file (depending on your computer settings, you may see the file as “load_zms.cmd”)

ZMS Connectivity

The ZMS client will automatically download all files necessary to run the application.

If the ZMS server is updated at a later date, the client will automatically update the next time it connects.

ZMS Connectivity

Login with the username and password credential provided by the ZMS administrator.

Default is:

admin/zhone

Creating a New User

Creating a New User

By default, the administrator login is:

admin/zhone

This user can only create users in the system and has no rights to modify objects or devices in the database. When you log in as the admin user, the tree display lists only groups andoperators. As the admin user, your permissions limit you to only managinggroups and users and assigning permissions.

Creating a New User

Creating a New User

The following screen will be presented showing the currently configured operators.

Right click on “Operators” and select “Add…” to begin adding new users to the system

Creating a New User

Create a new username, password, and set the account to active.

To create a user with only monitor privs, check the Read box in stead of the Write box.

The user created on the right has full privileges to all devices.

To complete, select the Add button. To add additional users, simply enter a new username/password and click on Add again.

You must exit the system and reenter with your unique username/password

Exercise: Creating a New User

Create a new user as instructed Logout as admin Login as first name/last name

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:

• Update the system profile to disable partial config syncs to ZMS by setting the zmsexists to false.

• The command is update system 0 After the CLI provisioning is complete, reset the zmsexists setting

to true and perform a full config sync from ZMS.

Main Map ViewPreliminary Configuration

Main Map View

After logging in, the default region will be displayed.

Devices

All devices are displayed in the expanded view under the device type.

Configuration

Expanding the device itself allows access to local configuration including:

Card locationTraffic DescriptorsRouting informationIP Filtersetc.

Cards

During the initial turn-up of a system, cards that are inserted need to be brought into service.

Note that the ADSL 48 port card is listed as inserted, but “(No Profile)

To perform this action, right click on the card, and select Add..

Follow the next screens to add the card.

Adding a Card

ZMS determines the correct card type and displays it in the right hand side.

Select the right arrow to continue.

Adding a Card

Typically no options need to be changed on this window, select the Add button to continue.

For the ADSL48 cards the file type needs to be changed to malcxdsl48ns.bin

Adding a Card

The card will now boot with the software specified

Adding a Card

Once the card boot cycle is complete, the state will change to “Running”

Uplink Port Configuration


To provision a uplink port, right click on the interface and choose Modify


Configure the desired settings.

By default, all uplink ports are Active.

Ensure the Cell Scramble setting matches the network configuration.

System Clock

To set the system clock, right-click on the MALC device name and choose modify

System Clock

System Clock

Select the uplink ports to add to the clock list.

Set preferences if needed.

Choose modify to apply the changes.

System:ADSL Port Turn-up

ADSL Turn-Up

To turn-up (activate) an ADSL port, expand the options to the desired slot and port. Right-click on the port to activate, and choose Modify.

ADSL Turn-Up

In the window that opens, change the Admin Status from Down to Up

ADSL Turn-Up

Clicking on Modify will turn up the port.

Additional ADSL settings such as upstream and downstream speed options can be configured by selecting the options on the left part of this window

ADSL Turn-Up

Click on the Transmit Rate under the Central Office Unit portion of the Tree menu to configure the downstream synch rates.

Adjust the speeds to match your service offerings if needed.

ADSL Turn-Up

The target Signal to Noise Ratio can also be set. Choose the Signal/Noise Margin option under the Central Office Unit to configure.

ADSL Turn-Up

The Upstream rates can be configured with the Transmit Rate, under the Customer Premise Unit options.

Set the desired rates as appropriate.

ADSL Turn-Up

The target Signal to Noise Ratio can also be set. Choose the Signal/Noise Margin option under the Customer Premise Unit to configure.

System:Adding New ATM VPI

ATM VPI

To add a new VPI to the uplink port, expand the configuration tree until the ATM VPI Profiles are displayed

Right-Click on ATM VPI Profiles and choose add to create a new ATM VPI

ATM VPI

The Switch Type option sets the VPI as either VC switched or VP switched.

If VC switched is selected, the Maximum VCI value needs to be set.

After selecting Add, the MALC device will need to be reset for these changes to take effect.

System:ATM Cross-Connects

ATM Cross-Connects

To create ATM Cross-Connects, Right-Click on the MALC device name in the configuration tree and choose “Manage ATM Connections”

ATM Cross-Connects

ATM Cross-Connects

Choose the Cross Connect Template

Enable the Cross connect

Choose the Uplink port (DS3 or T1-IMA port)

Choose the Uplink VPI/VCI

Traffic Descriptors

Choose the ATM Traffic Descriptor Template to use

Choose the ADSL port VPI/VCI pair to use. The same VPI/VCI will be applied to each ADSL port

Select the ADSL ports to configure.

System:ATM StatisticsDSL Statistics

ATM Statistics

To view the ATM statistics for a particular port,

expand the tree view to the physical port, ATM

VCL endpoints; right-click on the appropriate VPI/VCI and select

Statistics.

ATM Statistics

Click start to begin gathering ATM statistical data.

ADSL Statistics

To view ADSL port statistics, expand the

tree to the desired slot/port. Right-click on

the port and choose View.

ADSL Statistics

To see if the ADSL modem has synch, click on the Status option on the left side tree,

ADSL Statistics

To view the current synch downstream synch rates, go to CO Status in the tree menu

ADSL Statistics

To view the Upstream synch information, go to CPE Status under the tree menu.

System:Alarm Management

Alarm Management

The icon next to the device represents the highest level alarm that currently exists on the device. In the example, both Zhone Malc and malc-199 have Critical alarms present. Alarms are divided into:

CriticalMajorMinorWarningInformation

Alarm Management

To view the alarms on a device, highlight the device and click the Alarm button on the toolbar.

To view all alarms for the network, select the region (in this case, Default Region) and click on the Alarm button.

Alarm Management

Zhone Malc currently has Major and Critical alarms (highest severity is always shown in the previous screen). In this case, all alarms relate to the Sonet (OC12) port being out of service.

Alarm Management

Right click on an alarm and select “Acknowledge Selected” in the pulldown. This will flag the alarm as a known issue (alarm is still present)

Alarm Management

Alarms will be automatically removed from the window once the device informs ZMS that the alarm condition has cleared.

MALC Provisioning SE Training October 2005. Management There are three primary management...

Documents

Transcript of MALC Provisioning SE Training October 2005. Management There are three primary management...