For software version 1.15.1.131 December 2008
Oakland, CA 94621 USA
510.777.7000 www.zhone.com [email protected]
COPYRIGHT C2000-2008 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.
Bitstorm, EtherXtend, IMACS, MALC, MXK, Raptor, SLMS, Z-Edge, Zhone, ZMS, zNID 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, non infringement, 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.
About This Guide
...21Style and notation conventions...21
Typographical conventions...21
Related documentation...22
Acronyms...22
Contacting Global Service and Support...23
Technical support...24
Service requirements...24
MALC S
YSTEM
Chapter 1
Introduction to the MALC
...25MALC Overview...26
Locating configuration instructions...28
Features...29
IP and data services...29
Bridging ...30
Redundancy...31
Resilient Packet Ring (RPR) ...31
Uplink card redundancy ...31
APS...32
Working card and protection card ...33
SONET/SDH APS + card redundancy ...33
ATM...33
AAL2-BLES signaling ...34
IMA ...34
ATM cell relay ...34
Management PVC ...34
ATM-to-TDM interworking ...35
T1/E1 circuit emulation ...35
POTS voice ...35
VoIP ...35
MGCP overview...36
SIP overview ...36
GR-303 and V5.2 ...38
GR-303 overview ...39
ISDN overview...39
V5.2 overview ...40
SIP-PRI media gateway ...41
Packet voice support ...42
Management...43
Rate Limiting ...44
Chapter 2
Managing the MALC
...45SLMS command line interface...45
Logging into the serial (craft) port...45
Navigating the MALC ...46
MALC configuration and booting ...46
Monitoring the MALC via the serial craft port ...47
Command: slots ...47
Verifying the version of the software...49
Provisioning line cards: adding, changing and deleting card profiles...50
Commands: list, show, get, update...51
Commands: interface show, host show, bridge show, bond show ...56
Commands: bridge stats ...57
SLMS Web interface ...58
Managing the MALC using Zhone Web User Interface...58
Web UI card support ...59
Zhone Management System (ZMS)...61
Configuring other CLI management interfaces...62
Configuring Ethernet on the MALC ...62
Uplink card 10/100 BaseT Ethernet interface ...62
VLAN management interface ...64
IP on a bridge ...65
Configuring ATM management...67
CPE Manager ...69
Verifying CPE Manager ...71
Additional information about CPE manager...73
Finding the local IP address and CPE base port ...74
Chapter 3
Diagnostics and Administration
...75System administration...75
MALC file system...76
Accessing the flash card ...76
Using the ata command ...76
Using the image command ...77
Changing the serial craft port settings ...77
Deleting card profiles...78
User accounts ...82
Adding users...82
Changing default user passwords ...83
Deleting users ...83
Deleting the admin user account ...83
Resetting passwords ...84
Radius support ...84
Viewing chassis and slot information ...88
SNTP...89
System clocking ...90
Overview ...91
Controlling Telnet access...97
TFTP server support ...98
SFP presence and status ...98
Redundant Uplink cards...100
Dual, non-redundant Uplink cards ...108
Managing the MALC over a non-redundant Uplink ...111
SNMP...113
Creating SNMP community names and access lists ...113
Creating a community profile...113
Creating community access lists ...114
Configuring traps ...114
Statistics and alarms...115
Bulk statistics ...115
Bulk statistics file format ...116
IF-Name in bulk stats (32 character limit) ...120
T1/E1 Statistics ...121
Alarm manager...124
Supported alarms...125
ADSL low power alarm ...132
Alarm suppression ...133
Logging...134
Overview...136
Enabling/disabling logging ...136
Log message format ...136
Modifying logging levels ...138
Using the log cache ...139
Examples ...139
Viewing the persistent logs...140
Sending messages to a syslog server ...141
Specifying different log formats for system and syslog messages ...142
Example log messages ...144
DSL line down message ...144
Slot card up message ...144
Log filter command...145
MALC security (SSH and SFTP) ...146
Tested MALC SSH clients...148
DSA and RSA keys...149
Cipher suites...150
Encryption-key commands ...150
Testing...152
Activating or deactivating interfaces ...152
BER tests...153
IMA test pattern procedure ...155
Loopbacks ...159
T1 loopbacks ...159
SONET loopbacks ...161
DS3 loopbacks...163
ISDN loopbacks ...165
802.3ah Ethernet OAM loopback...166
SELT/DELT on MALC ADSL2+ Broadcom cards...169
Viewing IMA group status...173
C
ONFIGURING
DATA
Chapter 4
Configuring IP
...175 IP Overview...175 IP services ...176 IP protocols ...177 DNS ...177 DHCP ...177 RIP...177 IP TOS support ...178 Applications...180 Routing...180Host-based and network-based routing ...181
Host-based routing with DSL bridges ...182
Network-based routing with DSL bridges...184
Network-based routing with DSL routers ...185
IP filtering ...186
Unnumbered IP interfaces...187
IP provisioning procedures...188
Configuring a management IP interface ...188
Configuring host-based routing ...190
Configuring network-based routing ...195
Configuring RIP ...199
Configuring static routes...199
Adding routes ...200
Configuring the MALC as a DHCP server ...200
DHCP server profiles and scope ...200
DHCP relay ...207
DHCP relay examples ...209
TOS/COS processing ...212
802.1p priority queues ...212
Fields in IP header ...212
Fields in the VLAN header ...213
TOS/COS parameters ...213
Advanced IP provisioning procedures ...214
Advanced DHCP applications...214
Configuring DNS resolver...216
IP Service Level Agreement (IPSLA)...218
IP fallback route ...227
IP administrative procedures...232
Modifying profiles created by host/interface add commands...232
Displaying hosts...234
Displaying interfaces ...235
Displaying routing information...236
Displaying the routing table ...236
Displaying RIP information ...236
Deleting hosts...237
Deleting interfaces ...237
Deleting routes ...237
DHCP logging...237
Understanding DHCP server log messages...238
IP statistics commands ...240
Chapter 5
Configuring bridges
...241Overview...241
Bridges, bridge interfaces, and bridge paths ...242
Macro bridge commands: bridge add, bridge-path add ...243
bridge add ...243
bridge-path add...243
Upstream and downstream, uplinks and downlinks ...244
Asymmetric and symmetric bridges...245
Bridges: line concentrator, Internet access model, intralink, TLS, hub..245
Line concentrator ...246
Configuring the line concentrator...246
Broadcast, multicast, and unicast...247
Unicast...247
Broadcast ...247
Multicast ...248
The Internet access model...249
VLANs ...250
Configuring the Internet access model ...252
Configuring intralinked MALCs ...256
Transparent LAN service ...258
Configuring a TLS bridge ...259
Hub bridge ...260
Configuring a hub bridge ...261
Administrative commands ...261
Bridge delete command...261
Bridge show/showall commands...261
Bridge stats ...261
Advanced bridging configurations...263
Bridge commands to display bridges and bridge interfaces ...263
Bridge show...263
Verifying bridge interface settings ...264
Settings for asymmetric bridges...265
Settings for symmetric bridges ...266
Configuring a VLAN bridge with DSL ...267
VLAN single and double tagging ...270
Untagged VLAN bridges...272
Strip and Insert ...273
Double tagged bridges (Q-inQ or s-tag)...274
Bridge path support for s-tags ...278
TLS Bridging behavior for untagged, tagged, and s-tagged ...279
Shaping Traffic: Class of Service Queuing ...281
Configuring Class of Service ...283
Mechanism for multiple interface ingress filters ...285
Destination MAC swapping...287
Configuring destination MAC swapping ...288
Bandwidth limiting by port and service...288
Color blind rate limiting ...289
Configure color blind policing ...290
Color aware rate limiting...290
Bridge with DHCP relay ...291
DHCP on bridge packet rules (DHCP relay, Option 82, PPPoE vendor tag, Forbid OUI) 295 Access Control List...298
Ether Type filtering ...298
Destination MAC address filtering...299
Source MAC address filtering ...299
Allow or deny rules ...299
Using multiple ACL filters on an interface/ordering ACL filters ...300
ACL display, stats, clear commands ...302
Broadcasts in asymmetric bridges ...304
Video bridging...304
FloodUnknown for unknown unicast addresses ...308
FloodMulticast to all other ports in a VLAN...308
Dynamic IP filtering on a bridge (Secure DHCP) ...309
Broadcast suppression...312
RSTP support ...312
RPR ring topology...317
RPR ring topology with redundant GigE cards...320
RPR ring topology with redundant GigE cards and subtended MALCs...322
RPR configuration ...324
Linear GigaBit Ethernet...334
GigE-2 Uplink card redundant configuration in linear topology...335
GigE-2 card bridging ...336
PPPoA - PPPoE Conversion...339
PPPoE Intermediate Agent...342
Chapter 6
Configuring ATM
...345MALC ATM Overview...345
ATM overview...346
ATM data ...347
ATM voice ...347
ATM Video ...348
Cross connects ...348
Early packet discard (EPD) and partial packet discard (PPD)...348
Usage parameter control (UPC)...349
ATM validation...349
VPI and VCI ranges ...350
Virtual channel and virtual path links ...352
Service categories ...352
Constant bit rate (CBR)...352
Non-real-time variable bit rate (nrt-VBR)...353
Real-time variable bit rate (rt-VBR) ...353
Unspecified bit rate (UBR)...353
Traffic descriptors ...353
Configuring PCR and SCR...353
Traffic descriptor parameters ...354
Traffic descriptor configuration rules...356
Connection admission control (CAC)...356
CAC oversubscription ...357
Bandwidth allocation for ATM cards...358
Example CAC calculation ...359
ATM traffic policing...360
Enforcing SCR and MBS ...360
Enforcing PCR and CDVT...360
General policing rules ...361
Traffic shaping ...361
Shaping for non-ADSL2+ cards with GigE uplinks ...363
Traffic shaping for 1.13.x and higher mixed IP and ATM networks ...364
ATM statistics ...365
Overview...365
VPI/VCI ranges...366
Changing VPI/VCI ranges ...366
Configuration overview ...367
Configuring PCR and SCR values...368
Creating traffic descriptors...372
Creating VCLs and VPLs...374
Creating cross connects...378
Subtending ...380
C
ONFIGURING
VOICE
Chapter 7
Configuring Voice
...385Overview...385
Updating system settings...386
Setting a-law or mu-law and DSP settings ...386
Creating voice connections...387
DS1 voice gateway connections ...387
Voice over IP (VoIP) connections ...391
SIP server configuration ...393
MGCP configuration ...396
Additional VoIP features...403
DS1 to POTS connections ...416
Configuring CES connections...417
Creating CES connections ...419
CES signaling ...419
CES clocking ...420
CES configuration...421
Additional voice features...434
Setting ring cadence and call progress parameters ...436
Call progress tones for Canada ...439
Emergency StandAlone (ESA) SIP and TDM support ...440
Configuring VoIP ESA clusters...442
Configuring ESA for 911 calls ...444
Verifying ESA ...445
Configuring TDM ESA...445
T.38 fax...447
T.38 fax using VoIP ...447
T.38 fax using SIP PLAR to PSTN ...449
Configuring voice gateway connections...455
VoIP to voice gateway connections ...456
Overview ...456
Deleting voice gateway host and voice connection...462
Deleting voice connection ...462
Subtended MALC POTS VoIP voice gateway connections...462
Overview ...462
Deleting subtended voice connection ...464
AAL2 voice gateway connections ...464
Overview ...465
Deleting a voice connection ...475
Subtended MALC ISDN or POTS voice gateway connections...475
Configuring subtended AAL2 voice connection ...476
POTS cards running POTS to VoIP in same chassis as voicegateway card 478 Voicegateway configuration ...478
POTS to VOIP connections ...482
Configuring SIP-PRI media gateway...483
About the VoIP Endpoint...485
ISDN Signaling profile ...485
SIP trunks...485
Hardware requirements ...486
Chapter 9
Configuring GR-303 or V5.2 Interface Groups
...493Configuring a GR-303 interface ...493
Modifying a GR-303 interface group ...498
Displaying GR303 interface group status ...499
Configuring a V5.2 interface...499
Creating a V5.2 interface group...503
Finding the line group identifiers of the physical connection...504
Provisioning V5.2 links ...505
Adding C-channels within links...506
Provisioning C-paths...508
Activating the V5.2 IG...510
Modifying the v52-interface-group profile ...510
C
ONFIGURING
VIDEO
Chapter 10 Configuring the MALC for video
...513Video routing...513
Video bridging...518
Uplink and downlink video bridging ...519
IGMP snooping with proxy reporting...522
Join requests ...523
Leave requests ...523
IGMP snooping with proxy configuration commands ...524
IGMP snooping with proxy reporting...525
Join requests...526
Leave requests...527
IGMP snooping with proxy configuration commands...527
U
PLINK
CARDS
Chapter 11 Gigabit Ethernet Uplinks
...529Overview...530
Redundant MALC-UPLINK-2-GE uplink card cable ...533
Redundant MALC-UPLINK-2-FE/GE uplink card cable ...533
Redundant FE/GigE TDM port cabling ...533
GigE and FE/GigE uplink card configuration ...534
802.1p priority queuing...545
Small form factor pluggables...545
802.3ad link aggregation...546
Link resiliency ...547
Configuring interfaces for link aggregation...549
Bridge configurations ...549
Interface configurations...549
host configurations ...549
Commands for linkagg ...549
Chapter 12 DS3/E3 Uplinks
...551Overview...552
DS3/E3 card configuration...554
Configuring DS3/E3 interfaces...556
DS3/E3 Uplink cable...560
Chapter 13 OC-3C/STM1 Uplinks
...561APS...569
Chapter 14 TDM/ATM Uplinks
...573Overview...573
T1/E1 TDM Uplink card configuration...576
Configuring DS1/E1 interfaces...578
Configuring IMA groups...583
Overview...586
Configuring IMA groups ...587
T1/E1-ATM/TDM cables...588
Redundant TDM/ATM Uplink cable...588
Non-redundant TDM/ATM Uplink cable ...591
Chapter 15 T1/E1 Uplinks
...595Overview...595
T1/E1 ATM/IP card configuration...597
Configuring DS1/E1 interfaces...599
Configuring IMA groups...604
Best Practices for Setting Up an IMA Group ...604
Overview...608
Configuring IMA groups ...609
T1/E1 IMA cable and port pinouts...610
T1/E1-IMA Uplink port pinouts ...610
8-port T1/E1 to dual 50 pin connector cable ...611
Redundant 8-port T1/E1 to dual 50 pin connector cable ...614
L
INE
CARDS
Chapter 16 ADSL
...619 Overview...619 ADSL Cards...620 Transmission modes...621 Rate adaptation...621 Advanced Configurations ...622Fine Tuning ADSL Video Performance...622
Seamless Rate Adaptation ...625
Transport mode: Fast or Interleaved ...627
Fast and Interleaved Configuration Notes ...628
ADSL Bonding with Broadcom Based Cards ...630
48-port ADSL cards ...636
24-port ReachDSL cards (ReachDSL-24, ReachDSL+SPLTR-24-2s) ...640
Activating ADSL cards...643
Configuring ADSL interfaces...651
Overview...651
Configure ADSL2+ cards ...652
Configuring ADSL S=1/2 ...670
Overview ...670
Configuring ADSL 2 and ADSL 2+ ...676
Configure ADSL2+ interfaces ...682
Broadcom Phy-R™ parameters ...686
Updating ADSL Annex A card profiles...689
Configuring POTS ports...690
ADSL Testing...694
SELT (Single-End Loop Tests) ...694
DELT (Dual-End Loop Test)...697
ADSL cable and port pinouts...700
ADSL card port pinouts ...700
ADSL 24 port card pinouts ...700
MALC-ADSL-48 card pinouts...701
ADSL cable pinouts ...705
ADSL-48 to dual 50-pin connector cable ...705
Chapter 17 SHDSL
...711 Overview...711 MALC-G.SHDSL-4W-12 card...712 MALC-SHDSL-48...713 Activating SHDSL cards...714 Configuring SDSL interfaces...716Automatic baud rate adaption and fixed rate settings ...717
Configuration restrictions ...717
Configuring SHDSL interfaces...721
SHDSL pinouts...726
MALC-G.SHDSL-4W-12 pinouts ...726
MALC-SHDSL-48 pinouts...727
Delivering power and data to a Raptor 100 SHDSL-LP...731
Chapter 18 EFM-SHDSL
...733Overview...734
SHDSL network scenario ...735
Card profile information for SHDSL-24 cards ...735
Create card profiles for SHDSL-24 cards...736
Power and data connections for SHDSL CPE devices...739
Wiring connections for power and data ...739
Send power down the data line ...740
G.SHDSL line power removal ...741
G.SHDSL port troubleshooting...743
MTAC testing...744
Chapter 19 VDSL2
...745Overview...746
Configuring VDSL2 interfaces...749
VDSL2 24 port card pinouts...753
Chapter 20 POTS
...755Overview...755
24-port POTS card (MALC-POTS-GBL-TDM/PKT-24 and MALC-EBS-TDM/ PKT-24)...756
48-port POTS card ...758
Configuring POTS cards...759
Configuring 24-port POTS cards ...760
Configuring 48-port POTS cards ...774
Verifying the slot card installation...777
Configuring POTS ports...778
Enabling Dial Pulse on POTS and POTS combination cards...782
POTs card port pinouts...783
24-port POTS cards pinouts...783
48-port POTS card pinouts ...784
Chapter 21 Voice Gateway
...789Overview...789
Adding a voice gateway card...791
Adding a redundant voice gateway card...792
Removing a redundant voice gateway card ...794
Pinouts...794
Voice gateway non-redundant TDM cable ...794
Chapter 22 T1/E1 ATM
...807Overview...808
Configuring DS1/E1 interfaces...812
Configuring IMA groups...816
Overview...819
Configuring IMA groups ...820
T1/E1 32 port TDM cable...821
Chapter 23 T1/E1 CES
...829Overview...829
CES card configuration...830
Pinouts...832
Chapter 24 EFM T1/E1
...835Overview...836
T1/E1 Network Scenario...837
Card profile information for T1/E1-24 cards...837
Creating card profiles for T1/E1-24 cards...838
Verifying the slot card installation...838
Verifying the slot card presence...839
Displaying card-profile ...839
Configuring T1/E1 interfaces...840
Listing the profiles and running a get command ...840
Bond group/physical line stats (MALC-EFM-T1/E1-24 card)...844
Packet counts ...844
Bond group bandwidth ...845
EFM 802.3ah bonding...845
Creating bond groups ...846
Displaying bond groups ...846
Changing bond group type...847
Deleting bond groups...847
Displaying statistics ...848
802.3ah EFM OAM...848
T1/E1 24 port TDM cable...851
MALC-CBL-T1/E1-2-45DEG...851
Blunt cables...855
Chapter 25 DS3/E3
...861Overview ...862
Chapter 26 GPON card
...875Overview...875
Configuring a GPON interface...878
GPON configuration...882
Multiple GEM Ports...884
GPON alloc-ID profile...885
Modifying upstream bandwidths for GEM ports...885
GPON OMCI configuration...886
OMCI file...886
Service configuration ...888
Commands for GPON configurations...888
VLAN configuration ...892
Chapter 27 Active Ethernet
...893Active Ethernet 10 port card...894
Small form factor pluggables...896
Displaying and updating Ethernet interfaces ...898
Configuring Active Ethernet ports ...899
Active Ethernet with ATM and IP uplink cards ...899
Flexible configurations...899
Chapter 28 ISDN
...901Overview...901
MALC-ISDN-4B3T-24 ...902
MALC-ISDN-2B1Q-24...908
ISDN card pinouts...911
Chapter 29 Metallic Test Access
...913Overview...914
Connectors on the MTAC cards ...917
Metallic loop testing ...917
Internal look out line test...918
Cards supporting look-out test access ...918
Ring generator...919
Activating MTAC cards...919
Creating card profiles for MTAC cards ...919
Performing line test using MTAC cards with external testing set...924
Connecting the external test set to MTAC card...924
Connecting a console to the external test set control port ...928
Performing internal line test using MALC-MTAC/RING-ENH card...929
Working with the MTAC line test command ...929
Test IDs ...931
Metallic loop tests ...933
3 elements capacitance test...934
3 elements resistance test ...935
DC feed self-test ...936
DC loop resistance test ...937
Distance to open test...938
DTMF and pulse digit measurement test ...938
Foreign AC currents test...940
Foreign DC voltage test...940
Foreign AC voltage test...941
Howler test ...942
Metering self test ...942
Noise test ...943
On-Off hook transition test...943
Loop and battery condition test ...944
Receiver off-hook test ...945
Ringer equivalency number test ...945
Ringing self test...946
Ringing monitor test ...947
Tone generation test ...947
Trans-hybrid loss test ...947
Transmission self test ...948
Troubleshooting with metallic loop tests ...948
Auto-calibration ...952
Lookout block diagram ...952
Configuring external alarms...952
Configuring an external clock...953
Connecting an external ring source...953
MTAC cards pinouts...955
External ring generator input port pinouts ...956
External alarm sense pinouts ...957
Examples of alarms with specific pinouts ...959
Metallic test access port pinouts ...962
External test set control port pinouts ...964
External clock input port pinouts...965
This guide is intended for use by technicians, system administrators, network administrators. It explains how to configure the MALC software features. For information on installing the MALC chassis and cards, refer to the MALC Hardware Instlallation Guide.
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.
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.
Related documentation
Refer to the following publication for additional information:
MALC Hardware Installation Guide—explains how to install the chassis and cards. The HWIG also includes hardware specifications and maintenance procedures.
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).
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 Italic
Used in code examples for variable text typed by users.
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
CASE
Used for environment variables.
Command Syntax Brackets [ ] indicate optional syntax. Vertical bar | indicates the OR symbol.
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 CID Channel identifier DSL Digital subscriber line EFM Ethernet in the First Mile
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
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 issueTechnical 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:
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.
E-mail [email protected]
Telephone (North America) 877-ZHONE20 Telephone (International) 510-777-7133
1
I
NTRODUCTION
TO
THE
MALC
The Multi-Access Line Concentrator (MALC) platform provides low-cost, high-density subscriber access concentration in the Zhone Single Line Multi-Service (SLMS) architecture.
The MALC is a flexible Multi-Service Access Platform (MSAP) which is a chassis that supports a variety of uplink and line cards. These uplink and line cards provide the connection technologies, such as POTS, xDSL, xPON, EFM and Active Ethernet.
The MALC is designed for the classic line concentration scenario which has a high capacity uplink toward the high speed, high throughput Internet core and provides access to devices toward the network edge.
There are a number of MALC products: Malc723, Malc719, Malc319 and Malc XP. Unlike the Malc723, Malc719, and Malc319, the MALC XP is not a chassis based unit with the ability to add, remove or change uplink and downlink cards.
Given the flexibility of the MALC as a platform for numerous configuration options:
•
MALC Overview, page 26MALC Overview
The MALC MSAP carries voice, data and video services over multiple transport level technologies:
•
Fast Ethernet and Gigabit Ethernet (FE and FEGE) uplinks•
Internet Protocol (IP) uplinks•
Bridges•
Asynchronous Transfer Mode (ATM)•
Time-division multiplexing (TDM) uplinks Figure 1: MALC configurationsMALC uplinks are the primary communication channel between subscribers and upstream networking devices. The MALC aggregates local loop traffic from a variety of media and sends it to an upstream device, such as ATM switch, PSTN switch, or IP router. The MALC supports edge connection technologies:
•
ADSL•
SHDSL IP (layer 3) Bridging(layer 2) PSTN GR-303 or V5.2 TDM UplinkTDM Uplink card Class VSwitch
PSTN EFM SHDSL line cards
ADSL line cards
SHDSL line cards VDSL line card
T1/E1 line cards DS3/E3 line cards
GPON line card BPON line card Active Ethernet line cards ISDN line card POTS line cards POTS combo line cards Voice Gateway line card MTAC line card
FE/GE Uplink card OC-3/STM1 Uplink card DS3/E1 Uplink card T1/E1 Uplink card FE/GE Uplink card OC-3/STM1 Uplink card DS3/E1 Uplink card T1/E1 Uplink card FE/GE Uplink card OC-3/STM1 Uplink card DS3/E1 Uplink card T1/E1 Uplink card
Soft Switch SIP SIP - PLAR MGCP H.248
•
EFM SHDSL•
VDSL•
DS3/E3•
T1/E1•
GPON•
POTS•
Voice Gateway•
ISDN•
Active Ethernet•
MTAC (Metallic Test Access)The MALC can be deployed in Central Office environments, outdoor
cabinets, or controlled environmental vaults for remote terminal applications. The MALC is intended for restricted access locations only.
The single uplink from the MALC enables network providers to provision all classes of services in a single platform and leverage the existing copper infrastructure going to the Digital Loop Carrier (DLC) locations. MALC cards are divided into the following general types:
•
Uplink cards provide Ethernet, Gigabit Ethernet, ATM, TDM or IP uplinks•
Access line cards provide customer interfaces such as Plain Old Telephone Service (POTS) and Digital Subscriber Line (DSL).•
System services cards such as the Metallic Test Access (MTAC) cards provide services to the MALCThe MALC supports the following types of uplinks:
•
Ethernet•
Gigabit Ethernet•
T1/E1 User-Network Interface (UNI) mode•
T1/E1 Inverse Multiplexing over ATM (IMA)•
DS3/E3 UNI mode•
GR-303 or V5.2•
OC3C/STM1Figure 1 suggests the different types of network configurations and
Locating configuration instructions
Before locating the instructions needed for your scenario, please read through this quick introductory chapter to have an understanding of the basic
configuration fundaments of the MALC.
The following table describes where to find the information you need to configure the MALC.
Feature See
ADSL ADSL on page 619.
ATM cross connects Cross connects on page 348. ATM data Configuring ATM on page 345
ATM traffic descriptors Creating traffic descriptors on page 372. ATM VCLs and VPLs Creating VCLs and VPLs on page 374. Bridging Configuring bridges on page 241
Clocking System clocking on page 511. DS3/E3 Uplink card DS3/E3 Uplinks on page 551.
GigaBit Ethernet Gigabit Ethernet Uplinks on page 529. GR-303 Configuring a GR-303 interface on page 493
IMA groups Configuring IMA groups on page 604.
IP Configuring IP on page 175.
IP video Configuring the MALC for video, page 513. Linear GigaBit
Ethernet
Linear GigaBit Ethernet on page 334
Management interface Managing the MALC on page 45. MTAC/Ring card Metallic Test Access on page 913. OC3C/STM1 OC-3C/STM1 Uplinks on page 561.
PON GPON card on page 875.
POTS POTS on page 755.
RPR Ethernet RPR on page 317.
SHDSL card SHDSL on page 711.
SNMP SNMP on page 113.
Subtending Subtending on page 380.
T1/E1 CES Configuring CES connections on page 417 and T1/E1 CES on page 829.
Features
This section describes some key features of the MALC, including: Connectivity Features
•
IP and data services on page 29•
Bridging on page 30•
Redundancy on page 31•
Resilient Packet Ring (RPR) on page 31•
ATM on page 33•
ATM-to-TDM interworking on page 35•
T1/E1 circuit emulation on page 35•
GR-303 and V5.2 on page 38•
POTS voice on page 35•
VoIP on page 35•
Voice gateway on page 37•
SIP-PRI media gateway on page 41•
Packet voice support on page 42•
Management on page 43IP and data services
The MALC provides an access and aggregation routing functions to connect subscribers to the Internet or other large networks. The following MALC interfaces support IP traffic:
•
One Ethernet interface on the uplink card for management or data traffic.T1/E1 IMA and TDM Uplink cards
T1/E1 Uplinks on page 595 and TDM/ATM Uplinks on page 573.
V5.2 interface groups Configuring a V5.2 interface on page 499.
VDSL VDSL2 on page 745.
VLANs VLANs on page 250.
Voice Configuring Voice on page 385.
•
High speed IP uplink interfaces on the uplink cards. These include T1/E1, DS3/E3, Gigabit Ethernet, and OC3C/STM1 interfaces. The ATM/IP uplink card terminates the IP traffic and routes it to its destination. Note that the uplink card must be an ATM/IP card in order for it to support IP services. Contact your Zhone sales representative or GSS for further information.•
DSL or T1/E1 subscriber interfaces. IP on subscriber interfaces runs over ATM PVCs using RFC 1483 encapsulation.After terminating the ATM traffic, the MALC routes the IP traffic over its Ethernet interface to provide a connection to an IP network.
The MALC provides the following key data services:
•
IP forwarding and routing—incoming packets from an interface are forwarded to the appropriate output interface using the routing table rules.•
Routed or bridged encapsulation.•
Internet Group Management Protocol (IGMP) video. IGMP is used by IP hosts to register dynamic multicast group membership. For example, all members of one multicast group would view the same of video content.•
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.•
VLAN bridging.The MALC hardware supports the following standards:
•
Multicast (IGMPv1 / v2)•
RIP v1 (RFC 1058) RIPv2 (RFC 2453)•
RFC 1483/2684 encapsulation (Bridged and routed)•
DHCP server (RFC 2131, 2132)•
Bridging 802.1D support•
VLAN 802.1Q supportBridging
Bridging is based on Level 2 MAC addresses, rather than Level 3 IP addresses. Bridging provides an ease of use for subscriber administrators because bridging combined with VLANs provide the security of a true LAN, though geographically seperated across the Internet.
Redundancy
The MALC supports the following types of redundancy:
•
Uplink card•
APS for the OC3C/STM1 uplink cardsResilient Packet Ring (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.
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.
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 cableRPR can be deployed in a variety of topologies including ring, collapsed ring, star, linear and redundant card configurations.
Uplink card redundancy
The MALC supports uplink and MTAC/Ring card redundancy. Cards in a redundancy group share the same card-group-id. When you install a single card that supports redundancy, the system assigns that card to a default redundancy group.
To configure redundancy, assign a second card of the same type to the same card group and optionally assign each a weight. A Standby Ready trap is generated when the standby card is ready for service. Weights are used to specify a preference for a particular card to become active. By default, all cards have the same weight.
When the cards boot up, they elect an active and a standby card based on their respective weights. If the weights are equal, the card in the lower numbered slot becomes active.
If an active card fails, the standby takes over and becomes active. Note that redundancy is non-revertive. That is, a previously active card does not become active when it starts up again.
When the standby card comes up, the active card copies over the
configuration database, routing tables, and software binaries to the standby card. As configuration changes are made to the active card, the standby card is automatically updated.
APS
The OC3C/STM1 cards provide Automatic Protection Switch (APS) on their ports. APS allows the primary card to be backed up by the second card, and hence reduces the risk of loss of data due to cable cuts, degradation of signal, and card failure. APS also allows the far-end equipment to request for switch-over via the use of APS command.
The OC3C/STM1 card supports APS 1:1 protection.
In the 1:1 protection scheme, a working channel on one card carries the full traffic, while a protect channel on another card is either idle or reserved for low priority traffic. When a failure occurs on the working fiber, the
destination switch moves the data from the working fiber to the protect fiber. MALC-OC3C/STM1 card supports the following APS features:
•
Failures such as LOS, LOF, AIS-L, and hardware failure.•
APS 1:1 configuration.•
Linear APS mode.•
Uni-directional and bidirectional with non-revertive mode.Note: Two uplink cards are required for APS.
Overview of SONET/SDH APS
Due to the high speed nature of SONET/SDH, APS is designed as a high speed switching protocol to minimize the risk of out of service in the event of hardware failure or a cable cut. APS uses the SONET/SDH K1K2 byte to signal between the local and far-end equipment. Only the protection line exchanges the K1K2 byte between the local and far-end equipment. To ensure interoperability with other vendor’s equipment, the MALC APS implementation conforms to the Bellcore GR-253-CORE and ITU-T G.783 specifications.
•
Linear APS: Linear mode supports both APS 1:1 and 1+1 architecture. The architecture must be consistent between local and far-end equipment. Otherwise, an architecture mismatch will occur.•
Bi-directional mode: APS bi-directional mode allows negotiation between local and far-end equipment. The action performs by APS is based on event priority and acknowledgement from far-end.•
Uni-directional mode: APS uni-directional mode allows fast switching by eliminating the acknowledgement from far-end.•
Non-revertive modes: Only a manual switch-over or a fail-over will cause traffic to switch from one port to another. Switching does not take place based on restoring of the working port.Working card and protection card
The MALC defines the uplink card in slot 1 as the working card, and the uplink card in slot 2 as the protection card. The working card always has the APS working ports. The protection card always has the APS protection ports. The exchange of K1K2 byte takes place only on the protection card.
SONET/SDH APS + card redundancy
In APS + card redundancy, a line failure will cause the whole card to fail-over to another card. However, switching will not take place on the standby card. The following features are supported by APS + card redundancy:
•
Switching on loss of transmit/receive line (LOS, LOF, AIS-L)•
Switching on hot-swap card removal•
Switching on far-end APS command•
Switching on hardware failureATM
The MALC provides the following ATM support:
•
AAL2 termination and Broadband Loop Emulation Service (BLES) signaling for all POTS cards, provided by the uplink card.•
ATM cell relay functions between an ATM switch and ATM-based IADs. The MALC provides the Customer Premises Interworking Function (CP-IWF) functions of the AAL2 BLES specification.•
Unspecified bit rate (UBR), real-time variable bit rate-(rt-VBR), non real-time variable bit rate (nrt-VBR), and constant bit rate (CBR) traffic.•
Connection admission control (CAC) and provisioning ofoversubscription factors on a per port and per service category basis. The CAC functions on the uplink card will not accept new connections if they exceed the remaining virtual bandwidth.
•
Policing to enforce the service contracts specified in the ATM traffic descriptors.•
ATM User-Network Interface (UNI) 3.0 and 3.1, and portions of 4.0•
IMA functions to concentrate ATM traffic from up to T1/E1 lines on theuplink card or T1/E1 32 card to an ATM switch. The MALC supports multiple IMA groups, depending on the type of card installed in the system.
•
Administrative Permanent Virtual Circuit (PVC) for management and control.AAL2-BLES signaling
AAL2 is specified in ITU-T (International Telecommunication Union) recommendations I.363.2, I.366.1, and I.366.2. AAL2 is designed to support voice applications using higher layer requirements such as voice compression, silence detection/suppression, and idle channel removal. AAL2 uses four bytes of the forty-eight byte ATM payload, leaving forty-four bytes for data. Broadband Loop Emulation Service (BLES) is a DSL forum specification (DSL Forum TR-039 Annex A) that enables ATM-based IADs to offer Class 5 calling features and high-speed data services over a single DSL connection.
BLES provides management signaling for POTS interfaces using inband Channel Associated Signaling (CAS).
IMA
The T1/E1 uplink card and the T1/E1 32 port card provides T1/E1 IMA support for inverse-multiplexing multiple ATM cells from a number of links into a single large, virtual connection. The MALC supports IMA version 1.1, including support for fallback to version 1.0.
ATM cell relay
In a cell relay application, the MALC switches ATM cells from the uplink interface to the subscriber-side DSL interface, and vice-versa. On the network side, the uplink card connects to upstream ATM devices. On the
subscriber-side, it connects to a standards-based IAD or modem. The MALC supports both VP and VC switching.
Management PVC
The uplink card provides an ATM PVC interface for in-band management of the MALC. This PVC is terminated on the uplink card and can be used to route management traffic over the uplink card’s Ethernet port. This enables the MALC to provide a management interface other devices in the same location that have an Ethernet interface.
ATM-to-TDM interworking
The MALC provides an interface between TDM-based networks and ATM networks. It supports standard POTS interfaces on the subscriber side to provide traditional voice services. Ring voltage for the line is provided by the MALC ring voltage bus.
On the network side, The uplink card performs AAL2 Segmentation and Reassembly (SAR) and terminates the AAL2 LES traffic destined for the POTS cards. The uplink card then encodes the voice traffic in G.711, and puts it on the appropriate timeslot on the TDM bus to send it to the subscriber port. Each POTS channel is uniquely addressed by a shelf-slot-port and has an associated AAL2 LES channel identifier (CID).
The MALC can also concentrate voice traffic and send it over an uplink interface to a voice gateway such as a Zhone Sechtor 100ATM.
T1/E1 circuit emulation
Circuit Emulation Service (CES) allows T1/E1 circuits to be transparently extended across an ATM network. CES is based on the ATM Forum standard AF VTOA 0078.0000. Using constant bit rate (CBR) ATM permanent virtual circuits (PVCs), CES allows communication between non-ATM CBR circuits (such as T1, E1, E3, and T3) and ATM UNI interfaces.
There two types of CES: structured and unstructured. In unstructured emulation (also known as clear channel emulation) the entire services bandwidth is emulated and reproduced at the target port. Structured emulation service (also called channelized emulation) emulates a point-to-point
fractional T1/E1 (less than a full T1/E1 line) connections. The frame structure is maintained. Individual streams are visible and are byte aligned. This allows the T1/E1 trunks using the structured emulation service to break into multiple DS-0 channels towards different destinations.
POTS voice
The MALC supports standard POTS and ISDN interfaces to provide
traditional voice services. Ring voltage for the line is provided by the MALC ring voltage bus. The POTS cards support dual-tone multi-frequency (DTMF) dialing only. Pulse dialing is supported on the MALC-POTS-GBL-TDM/ PKT-24 card.
To support POTS functionality in the MALC chassis, an ATM voice gateway, is required in order for the MALC to connect to a Class 5 switch.
VoIP
Voice over IP, also known as Internet Telephony, supports full duplex transmission of voice traffic over IP networks. The MALC supports Media gateway control protocol (MGCP) and Session Initiation Protocol (SIP).
MGCP overview
Media gateway control protocol (MGCP) provides the means to interconnect a large number of IP telephony gateways. MGCP assumes that a call agent (CA) performs the intelligence of all call-control operations and that a media gateway (MG) carries out all media processing and conversion.
MGCP provides an internetworking control system to control telephony gateways from external call control elements are referred to as call agents. A telephony gateway is a network element that provides conversion between the audio signals carried on telephone circuits and data packets carried over the Internet or over other packet networks.
MGCP assumes a call control architecture in which the call control “intelligence” is outside the gateways and handled by external call control elements. The MGCP assumes that these call control elements, or Call Agents, will synchronize with each other to send coherent commands to the gateways under their control. MGCP does not define a mechanism for synchronizing Call Agents. MGCP is, in essence, a master/slave protocol, where the gateways are expected to execute commands sent by the Call Agents.
MGCP assumes a connection model constructed of endpoints and
connections. Endpoints are sources or sinks of data and could be physical or virtual.
Examples of physical endpoints are:
•
An interface on a gateway that terminates a trunk connected to PSTN switch (for example, a Class 5 or Class 4 switch). A gateway that terminates trunks is called a trunk gateway.•
An interface on a gateway that terminates an analog POTS connection to a phone, key system, PBX, etc. A gateway that terminates residential POTS lines (to phones) is called a residential gateway.•
An example of a virtual endpoint is an audio source in an audio-content (media) server.Creation of physical endpoints requires hardware installation, while creation of virtual endpoints can be done in software.
Connections may be either point-to-point or multipoint. A point-to-point connection is an association between two endpoints with the purpose of transmitting data between these endpoints. Once this association is
established for both endpoints, data transfer between these endpoints can take place.
The MALC also supports Megaco, H.248.
SIP overview
Session Initiation Protocol (SIP) is a signaling protocol that provides a mechanism for:
•
call establishment•
call teardown•
call control•
other supplementary services in an IP network.There are two major architectural components within SIP: the SIP user agent (UA) and the SIP network server. The UA is the end system component responsible to initiate and answer calls. The SIP server is the network device that handles the signaling associated with multiple calls.
The UA itself has a client element, the User Agent Client (UAC) and a server element, the User Agent Server (UAS). The client element initiates the calls and the server element answers the calls. This allows peer-to-peer calls to be made using a client-server protocol.
The main function of the SIP server is to provide name resolution and user location, since the caller is unlikely to know the IP address or host name of the called party, and to pass on messages to other servers or SIP endpoints. Other functions performed by the SIP servers are redirecting, forking, and
registration.
Together these components make up a basic SIP infrastructure. Application servers can sit above these components delivering SIP supplementary services to end users.
Voice gateway
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
Figure 2: Voice gateway overview
The MALC voice gateway card can also serve as an aggregation point for multiple downstream MALC or IAD systems aggregating multiple services ( SHDSL, T1/E1 ATM) or multiple voice lines on residential services (ADSL, ADSL2+, VDSL) over a single uplink connection.
Figure 3: Voice gateway aggregation point
GR-303 and V5.2
The MALC TDM uplink card supports GR-303 or V5.2 interfaces to a PSTN switch. The MALC can connect ATM or POTS subscriber interfaces to the PSTN. MALC with voice gateway
Packet
GR303 V5.2 Local Exchange SwitchTDM
IAD MALC withvoice gateway Local ExchangeSwitch
IP Network
GR-303 overview
GR-303 is a Bellcore-defined protocol that describes an Integrated Digital Loop Carrier System (IDLC) that operates on DS1 (T1) circuits. The GR-303 specification describes T1 circuits exiting an Integrated Digital Terminal (IDT) and going to remote digital terminal (RDT) equipment. Zhone products that support GR-303 act as RDTs.
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 GR-303 specification also provides for redundancy on the circuits that carry the data links. The primary and secondary T1 circuits each carry the TMC and EOC for redundancy.
Figure 4 shows how T1 (DS1) circuits leaving the local switch toward the
MALC are grouped into an interface group (IG). The primary DS1 channel carries the first TMC on DS0 24 and the first EOC on DS0 12. The secondary DS1 is a mirror image of the first, carrying the secondary TMC and EOC channels.
Figure 4: GR-303 circuits, channels, and CRVs
ISDN overview
ISDN BRI service provides a 144kbps line rate divided between two 64kbps B (or bearer) channels, which can carry voice calls or high-speed data, and one 16kbps D (or data) channel, which carries call-setup information and IDT Integrated Digital Terminal LDS Local Digital Switch
GR-303 IG
2048 Call Reference Values CRV IAD Primary DS1 Secondary DS1 Must be first DS1 TMC #1 on channel/DS0 24 EOC #1 on channel/DS0 12Can be any other DS1 TMC #2 on channel/DS0 24 EOC #2 on channel/DS0 12
signaling. ISDN BRI is often called 2B+D because of its three duplex channels. ISDN networks include terminal equipment (TE) such as phones and faxes; network terminators (NT), such as routers and IADS at the customer premises, which connect the four-wire subscriber wiring to the conventional two-wire local loop; terminal adapters (TA), which allow non-ISDN devices to access the ISDN network; and line termination (LT) equipment, which terminates the ISDN line at the local switch.
An NT1, or Network Termination-1, is required to connect ISDN terminal equipment to an ISDN line. The NT1 connects to customers’ phones with a two-wire line. This two-wire interface is referred to as the U interface or U reference point, and is accessible via a modular RJ-11or miniature 8-position (ISO 8877) jack. The connection point between the NT1 and terminal equipment is the S/T interface, which defines a four-wire line with separate transmit and receive pairs (and additional pairs for powering when required). The S/T interface is accessible through ISO 8877 jacks on the NT1 and terminal equipment.
V5.2 overview
The MALC supports the V5.2 European Telecommunications Standards Institute (ETSI) standards G.965 and ETSI EN 300 347-1 V2.2.2. These specify a set of electrical, physical, procedural, and protocol requirements for connecting an Access Node (AN) to a Local Exchange (LE). In this context the MALC acts as an AN.
The MALC system uses V5.2 for analog telephone (POTS) access and ISDN basic rate (BRI) access.
V5.2 services are supported by combinations of 64 Kbps V5 bearer channels, communication, and control protocols.
Each 2.048 Mbps E1 interface uses 32 timeslots. Timeslot 0 (zero) is used for frame alignment. Timeslot 16 of the first E1 link is used by the V5.2 control protocol.
C-paths (communications paths) are carried over C-channels
(communications channels). C-channels are used to carry signaling traffic. A V5.2 interface may contain up to 44 C-channels. C-channels are restricted to timeslots 15, 16, and 31 in accordance with the ETSI specification.
Figure 5: V5.2 links, C-channels, and C-paths
SIP-PRI media gateway
The MALC SIP-PRI media gateway feature enables you to convert TDM call signals from a T1/E1 PRI trunk into SIP (Session Initiation Protocol) VOIP packets. This feature leverages the emergence of SIP networking to unify multiple voice and packet network functions into one entity, providing a more tightly integrated voice and data network.
The SIP-PRI feature can be configured over a T1 or E1 connection. On a T1 connection, SIP-to-PRI is configured with 23 B (Bearer) channels and one D (Data) channel. On an E1 connection, it is configured with 31 B channels and 1 D channel. is configured with 23 bi-directional B (Bearer) channels and one D (Data) channel. SIP-to-PRI is unique in its ability to designate the D channel to handle all of the signaling and call control requirements and leave the remaining B channels free for any mix of voice and either virtual private line or circuit-switched data.
Figure 6: SIP to PRI environment
Packet voice support
For VoIP applications, the MALC supports packetizing voice traffic on POTS cards and sending it out the MALC voice gateway card. Table 2 describes VoIP support on the MALC POTS-capable cards.
PBX phones SIP phone
SIP phone
MALC with
Uplink-2-GigE card and MALC-VG-T1/E1-32-2S card IP Network PBX switch Soft Switch PRI ove r T1/E1 links GigE
Table 2: MALC POTS cards support
MALC egress Cards POTS TDM
only cards POTS TDM and packet cards Traffic path TDM Uplink Trunk UP-T1/E1-ATM/TDM/IP-16 UPLINK-2-GE
TDM > TDM TDM > TDM Traffic from TDM bus out TDM interface on uplink. VoIP on Non-Network Processor Based Uplinks UPLINK-DS3/E3-ATM/IP UPLINK-OC3C/STM1-ATM/IP UP-T1/E1-ATM/TDM/IP-16
Not supported Supported Traffic from the line card is packetized on the line card and routed to the uplink out an IP port.
The following POTS cards support TDM and packet voice:
•
MALC-ADSL+POTS-PKT-BCM-48A-2S•
MALC-ADSL+POTS-PKT-BCM-48B-2S•
MALC-ADSL+POTS-PKT-48A/M-2S•
MALC-POTS-GBL-TDM/PKT-24•
MALC-POTS-TDM/PKT-48Management
The MALC has two primary management interfaces: an ATM Virtual Channel (VC) which carries only Simple Network Management (SNMP) traffic, and a 1483-routed IP connection. Both connections are terminated on the uplink card.
After establishing a connection to the MALC, administrators can manage the device using the Command Line Interface (CLI), SNMP, or the ZMS. The uplink card also contains a serial (craft) session for local management.
VoIP on Network Processor Based Uplinks UPLINK-2-GE UPLINK-2-FE/GE
Not supported Supported Traffic from the line card is packetized on the line card and routed to the uplink out an IP port. VoIP (SIP PLAR) to Voice Gateway Local UPLINK-DS3/E3-ATM/IP UPLINK-OC3C/STM1-ATM/IP UP-T1/E1-ATM/TDM/IP-16 UPLINK-2-GE UPLINK-2-FE/GE
Not supported Supported Traffic from the line card is packetized on the line card and routed to the uplink then is routed back down the blackplane to a voice gateway card. VoATM (AAL2) to Voice gateway Local UPLINK-DS3/E3-ATM/IP UPLINK-OC3C/STM1-ATM/IP UP-T1/E1-ATM/TDM/IP-16
Not supported Supported Traffic from card to TDM bus to uplink then converted to AAL2 on uplink then cell switched back down the packet bus to the voice gateway card. Table 2: MALC POTS cards support (Continued)
MALC egress Cards POTS TDM
only cards
POTS TDM and packet cards
Rate Limiting
Rate limiting is a mechanism for controlling traffic and can include policing (dropping packets). You use rate limiting to control the rate of traffic sent or received on the ingress or the egress of both the logical port or the physical port on the MALC. Traffic that is less than or equal to the specified rate is sent and traffic that exceeds the rate is dropped. The rate limiting described here does not included queuing which delays packets in a buffer.
After configuring an interface with rate limiting, the traffic rate is monitored and metered to verify conformity with an established contract.
Non-conforming traffic is discarded, while conforming traffic passes through the interface without any changes. The MALC follows RFC 2697 for rate limiting on both the ingress and egress of the interface.
the rate limiting feature is support on the following cards:
•
MALC-UPLINK-2-FE/GE-TDM•
MALC-UPLINK-2-FE/GE•
MALC-GPON-SC-1•
MALC-VDSL17A-24•
MALC-EFM-SHDSL-24 NTWC•
MALC-EFM-SHDSL-24 NTP•
MALC-ACTIVE-ETH-10Other cards, such as the MALC ADSL line cards, use ATM traffic descriptors to control the rate of traffic.
2
M
ANAGING
THE
MALC
The MALC may be configured by different device management interfaces:
•
SLMS command line interface, page 45•
SLMS Web interface, page 58•
Zhone Management System (ZMS), page 61•
Configuring other CLI management interfaces, page 62•
CPE Manager, page 69This document describes fundamental principles about networking topics such as routing and bridging using the MALC. Examples in this document are shown using the CLI.
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.
SLMS command line interface
The MALC uses the Zhone SLMS command line interface (CLI). With SLMS the same command line interface is used for multiple Zhone devices (though each device will only show the commands which are appropriate to that device).
Logging into the serial (craft) port
The MALC unit provides an out-of-band RS232 D serial (craft) interface for managing the unit. The MALC supports 6 concurrent management sessions, 5 telnet sessions and a single local session through the serial (craft) port.
Note: Do not use the serial craft port of a standby card to modify its configuration.
To access the serial port, configure your terminal interface software with the following settings:
•
8 data bits•
No parity•
1 stop bit•
No flow controlTip: The serial (craft) port settings can be changed by modifying the rs232-profile.
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 Permanent Virtual Circuit (PVC).
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
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. To set the timeout to 20 minutes use
timeout 20. To turn the timer off, so it will not timeout, use
timeout off. Refer to Zhone CLI Reference Guide for information on the timeout command.
Navigating the MALC
The MALC is a passive chassis and the uplink card is also the controller card for the MALC. Along with the ability to display cards (both active and inactive) which are in the MALC, you can also see into the DOS file system which stores boot code, software images, and configurations. Please see MALC file system on page 380 for a description of commands which can be used to access the MALC file system.
MALC configuration and booting
The MALC must have at least one uplink card installed before the MALC will boot properly. The uplink card is also the controller card for the MALC chassis.
Slot cards (except the first uplink card in slot 1) must be provisioned with a card-profile before they will boot up.
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 Permanent Virtual Circuit (PVC).
MALC default configuration
Upon first login the MALC will be in a default state; the 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.•
A default system profile 0 exists with the following configuration: – Authentication traps are not enabled– ZMS communication is not configured
– Alarm notification and output are enabled for all severity levels
Monitoring the MALC via the serial craft port
The MALC can send messages to a console session, a log file, or to a syslog server and be configured to a number of system event levels — emergency, alert, critical, error, warning, notice, information, and debug.
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:
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.
Command: slots
The slots command shows the cards which are in the MALC and their state (running, loading, or not provisioned).