Zhone's MALC series DSLAM configuration with ADSL, XDSL, SHDSL, SDSL, DS1, T1, and EOC (ethernet over copper) config...
MALC Configuration Guide MALC 723, MALC 719, and MALC 319
For software version 1.15.1.131 December 2008 Document Part Number: 830-00990-17
Zhone Technologies @Zhone Way 7001 Oakport Street 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.
2
MALC Configuration Guide
TABLE OF CONTENTS About This Guide .............................................................................................................................21 Style 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 SYSTEM Chapter 1
Introduction to the MALC ...................................................................................25 MALC 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 Voice gateway.........................................................................................................37
MALC Configuration Guide
3
Table of Contents
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 .............................................................................................45 SLMS 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 .....................................................................75 System 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 Manually binding interfaces ...................................................................................79
4
MALC Configuration Guide
Renaming interfaces................................................................................................80 Saving and restoring configurations .......................................................................80 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 features ........................................................................................146
MALC Configuration Guide
5
Table of Contents
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
CONFIGURING 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..................................................................................................................180 Host-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 Setting DHCP server options .........................................................................201
6
MALC Configuration Guide
Creating DHCP server subnet options............................................................203 Enabling a DHCP server ................................................................................205 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 ...........................................................................................241 Overview ...................................................................................................................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 Internet access model with intralinked MALCs ...................................................255
MALC Configuration Guide
7
Table of Contents
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 Commands for RSTP support.........................................................................315
8
MALC Configuration Guide
Ethernet RPR ...........................................................................................................317 Overview...............................................................................................................317 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 ..................................................................................................345 MALC 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 Configuration overview.........................................................................................365
MALC Configuration Guide
9
Table of Contents
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
CONFIGURING VOICE Chapter 7
Configuring Voice ...............................................................................................385 Overview ...................................................................................................................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 T.38 using SIP PLAR to POTS fax ......................................................................450
10
MALC Configuration Guide
Chapter 8
Configuring the Voice Gateway.....................................................................453 Overview ...................................................................................................................453 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 ........................................493 Configuring 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 Displaying V5.2 interface group status.................................................................511
MALC Configuration Guide
11
Table of Contents
CONFIGURING VIDEO Chapter 10 Configuring the MALC for video ...................................................................513 Video 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
UPLINK CARDS Chapter 11 Gigabit Ethernet Uplinks ..................................................................................529 Overview ...................................................................................................................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 .....................................................................................................551 Overview ...................................................................................................................552 DS3/E3 card configuration ...................................................................................554 Configuring DS3/E3 interfaces............................................................................556 DS3/E3 Uplink cable...............................................................................................560
Chapter 13 OC-3C/STM1 Uplinks ..........................................................................................561 Overview ...................................................................................................................562
12
MALC Configuration Guide
OC3C/STM1 Uplink card configuration.............................................................564 Configuring OC-3C/STM1 interfaces .................................................................565 APS.............................................................................................................................569
Chapter 14 TDM/ATM Uplinks ................................................................................................573 Overview ...................................................................................................................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 ........................................................................................................595 Overview ...................................................................................................................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
LINE CARDS Chapter 16 ADSL .........................................................................................................................619 Overview ...................................................................................................................619 ADSL Cards..........................................................................................................620 Transmission modes..............................................................................................621 Rate adaptation......................................................................................................621 Advanced Configurations .....................................................................................622 Fine 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 ADSL2+ bond cards ............................................................................................631
MALC Configuration Guide
13
Table of Contents
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...............................................................................716 Automatic 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............................................................................................................733 Overview ..................................................................................................................734 SHDSL network scenario .....................................................................................735 Card profile information for SHDSL-24 cards .....................................................735 Create card profiles for SHDSL-24 cards.........................................................736 Set wetting current ................................................................................................737
14
MALC Configuration Guide
Switch clocking source .........................................................................................737 SHDSL 24 port cable..............................................................................................738 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 .......................................................................................................................745 Overview ...................................................................................................................746 Configuring VDSL2 interfaces ............................................................................749 VDSL2 24 port card pinouts.................................................................................753
Chapter 20 POTS .........................................................................................................................755 Overview ...................................................................................................................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 ......................................................................................................789 Overview ...................................................................................................................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 Voice gateway redundant TDM cable............................................................800
MALC Configuration Guide
15
Table of Contents
Chapter 22 T1/E1 ATM ...............................................................................................................807 Overview ...................................................................................................................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 ...............................................................................................................829 Overview ...................................................................................................................829 CES card configuration.........................................................................................830 Pinouts ......................................................................................................................832
Chapter 24 EFM T1/E1 ..............................................................................................................835 Overview ..................................................................................................................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 .....................................................................................................................861 Overview ..................................................................................................................862 DS3 network examples .........................................................................................864
16
MALC Configuration Guide
Configuring DS3 cards..........................................................................................865
Chapter 26 GPON card ..............................................................................................................875 Overview ...................................................................................................................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 .....................................................................................................893 Active 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 ...........................................................................................................................901 Overview ...................................................................................................................901 MALC-ISDN-4B3T-24 .............................................................................................902 MALC-ISDN-2B1Q-24 .............................................................................................908 ISDN card pinouts ..................................................................................................911
Chapter 29 Metallic Test Access ..........................................................................................913 Overview ...................................................................................................................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 the test measurement device to the metallic test access port.............926
MALC Configuration Guide
17
Table of Contents
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
Index ....................................................................................................................................................967
18
MALC Configuration Guide
ABOUT THIS GUIDE
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.
MALC Configuration Guide
21
About This Guide
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.
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).
22
MALC Configuration Guide
Acronyms
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
MALC Configuration Guide
23
About This Guide
Contacting Global Service and Support Contact Global Service and Support (GSS) if you have any questions about this or other Zhone products. Before contacting GSS, make sure you have the following information:
•
Zhone product you are using
•
System configuration
•
Software version running on the system
•
Description of the issue
Technical support If you require assistance with the installation or operation of your product, or if you want to return a product for repair under warranty, contact GSS. The contact information is as follows: E-mail
[email protected]
Telephone (North America)
877-ZHONE20
Telephone (International)
510-777-7133
Internet
www.zhone.com/support
If you purchased the product from an authorized dealer, distributor, Value Added Reseller (VAR), or third party, contact that supplier for technical assistance and warranty support.
Service requirements If the product malfunctions, all repairs must be performed by the manufacturer or a Zhone-authorized agent. It is the responsibility of users requiring service to report the need for service to GSS.
24
MALC Configuration Guide
1
INTRODUCTION 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 26
•
Features, page 29
MALC Configuration Guide
25
Introduction to the MALC
MALC 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 configurations
Line cards
Uplink cards
VDSL line card DS3/E3 line cards T1/E1 line cards
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
GPON line card BPON line card
Soft Switch
P S T N
SHDSL line cards
FE/GE Uplink card OC-3/STM1 Uplink card DS3/E1 Uplink card T1/E1 Uplink card
B (la rid ye gin r g 2)
EFM SHDSL line cards
(la IP ye r 3)
ADSL line cards
SIP SIP - PLAR MGCP H.248
S
Class V Switch
P
TDM Uplink card ISDN line card
T
N
Active Ethernet line cards
GR-303 or V5.2 TDM Uplink
POTS line cards POTS combo line cards Voice Gateway line card MTAC line card
MALC 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:
26
MALC Configuration Guide
•
ADSL
•
SHDSL
MALC Overview
•
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 MALC
The 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/STM1
Figure 1 suggests the different types of network configurations and technologies supported by the MALC.
MALC Configuration Guide
27
Introduction to the MALC
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.
28
MALC Configuration Guide
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
Feature
See
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.
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 43
IP 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.
MALC Configuration Guide
29
Introduction to the MALC
•
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 support
Bridging 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.
30
MALC Configuration Guide
Features
Redundancy The MALC supports the following types of redundancy:
•
Uplink card
•
APS for the OC3C/STM1 uplink cards
Resilient 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 cable
RPR 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.
MALC Configuration Guide
31
Introduction to the MALC
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. SONET/SDH APS supports the following modes:
32
MALC Configuration Guide
Features
•
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 failure
ATM 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 of oversubscription 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.
MALC Configuration Guide
33
Introduction to the MALC
•
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 the uplink 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.
34
MALC Configuration Guide
Features
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).
MALC Configuration Guide
35
Introduction to the MALC
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:
36
MALC Configuration Guide
Features
•
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
Voice over IP: SIP-PLAR to GR-303 or V5.2
MALC Configuration Guide
37
Introduction to the MALC
Figure 2: Voice gateway overview
TDM GR303 V5.2
Packet
MALC with voice gateway
Local Exchange Switch
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
IAD
IP Network MALC with voice gateway
Local Exchange Switch
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.
38
MALC Configuration Guide
Features
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
GR-303 IG Primary DS1 Must be first DS1 TMC #1 on channel/DS0 24 EOC #1 on channel/DS0 12 IDT Integrated Digital Terminal
2048 Call Reference Values
LDS Local Digital Switch
IAD
CRV Secondary DS1 Can be any other DS1 TMC #2 on channel/DS0 24 EOC #2 on channel/DS0 12
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
MALC Configuration Guide
39
Introduction to the MALC
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 illustrates the relationship between links, C-channels, and C-paths.
40
MALC Configuration Guide
Features
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.
MALC Configuration Guide
41
Introduction to the MALC
Figure 6: SIP to PRI environment
Soft Switch IP Network
GigE
PRI o
ver T
MALC with Uplink-2-GigE card and MALC-VG-T1/E1-32-2S card
1/E1
lin k s
PBX switch SIP phone
SIP phone PBX phones
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. Table 2: MALC POTS cards support
42
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.
MALC Configuration Guide
Features
Table 2: MALC POTS cards support (Continued) MALC egress
Cards
POTS TDM only cards
POTS TDM and packet cards
Traffic path
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.
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-48
Management 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.
MALC Configuration Guide
43
Introduction to the MALC
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-10
Other cards, such as the MALC ADSL line cards, use ATM traffic descriptors to control the rate of traffic.
44
MALC Configuration Guide
2
MANAGING 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 69
This 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:
•
9600bps
MALC Configuration Guide
45
Managing the MALC
•
8 data bits
•
No parity
•
1 stop bit
•
No flow control Tip: The serial (craft) port settings can be changed by modifying the rs232-profile.
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.
46
MALC Configuration Guide
SLMS command line interface
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).
MALC Configuration Guide
47
Managing the MALC
zSH> slots Uplinks 1: MALC FEGE RPR (RUNNING) Cards 5: MALC NTN/EFM GSHDSL Bonded/with NTP (NOT_PROV) 6: MALC ADSL 48 ANNEX A/M Bonded (RUNNING) 7: MALC POTS 48/with Packet Voice (NOT_PROV) 11: MALC ACT ETH 10 (NOT_PROV) 17: MALC MTAC ENHANCED (NOT_PROV)
In this example there is a Fast Ethernet Gigabit Ethernet RPR capable card in slots 1 and it is running. Note that the controller for the MALC is in slot 1. Of the other cards in the MALC chassis, the ones in slot 5, 7, 11 and 17 have not yet been provisioned. The slots 1 command shows information about the uplink card in slot 1. Since the MALC is a passive chassis (it doesn’t have a controller built-in), the uplink card is a controller card. You can find the ROM and software version of the controller card. zSH> slots 1 Type : Card Version : EEPROM Version : Serial # : CLEI Code : Card-Profile ID : Shelf : Slot : ROM Version : Software Version: State : Mode : Heartbeat check : Longest hbeat : Fault reset : Uptime : Start time :
MALC FEGE RPR 24430302 1 1762420 No CLEI 1/1/5091 1 1 MALC CAN 1.14.1.105 development RUNNING FUNCTIONAL enabled 306 enabled 5 days, 4 hours, 28 minutes 1224671176
In this slots 1 example, we can learn information, such as the ROM version, software version and Card-Profile ID, which may be useful when troubleshooting the MALC. To display the cards in the MALC, use the slots command without any arguments. zSH> slots 1: 3: 5: 7:
48
MALC Configuration Guide
INFOSERVICES (RUNNING) ETHERNET (RUNNING) ATM TRNK CR/OC3 ATM SM (RUNNING) ATM TRNK/E3 ATM (RUNNING)
SLMS command line interface
9: HDSL2 (RUNNING) 10: ATM TRNK (LOADING) 12: ATM TRNK CR (LOADING) 15: ATM TRNK CR/T3 ATM (RUNNING)
In this example there are seven cards and they occupy slots, 1, 3, 5, 7, 9, 10, 12, and 15. To view information about a particular slot card, use the slots command and specify a slot number: Type:*MALC RPR GIGE Card Version: 1 EEPROM Version: 1 Serial #: 5010999 CLEI Code: No CLEI Card-Profile ID: 1/1/5041 Shelf: 1 Slot: 1 ROM Version: MALC REL 1.14.1.2 Software Version: development State: RUNNING Mode: FUNCTIONAL Heartbeat check: enabled Longest beat: 50 Fault reset: enabled Uptime: 4 days, 1 hour, 3 minutes Start time: 1185226538
The asterisk on the TYPE: shows that this card is the redundant card in a redundant configuration. There is information about the card, the slot the card occupies, the software version and the ROM version as well as the status of the card.
Verifying the version of the software The slots command also displays the version of the software in the ROM of the uplink card. zSH> slots 1 Type: *MALC RPR GIGE Card Version: 1 EEPROM Version: 1 Serial #: 5010999 CLEI Code: No CLEI Card-Profile ID: 1/1/5041 Upgrading the system software MALC 1.14.1.2 Release Notes 87 Shelf: 1 Slot: 1 ROM Version: MALC REL 1.14.1.2 Software Version: release 1. State: RUNNING Mode: FUNCTIONAL Heartbeat check: enabled
MALC Configuration Guide
49
Managing the MALC
Longest beat: 50 Fault reset: enabled Uptime: 4 days, 1 hour, 3 minutes Start time: 1185226538
Provisioning line cards: adding, changing and deleting card profiles The card command enables users to add, change, update, and delete card profiles. Optional parameters are available: software load filename, card group ID, linetype, line card voltage (ISDN cards only), and status. By default, new card profiles are enabled and use the system assigned software load file. When you have physically added a card to the MALC, you will need to provision the card with software.
Example: Provisioning an EFM card 1
Enter a slots command to see the card and which slot it occupies zSH> slots Uplinks 1: MALC FEGE RPR (RUNNING) Cards 5: MALC NTN/EFM GSHDSL Bonded/with NTP (NOT_PROV) 6: MALC ADSL 48 ANNEX A/M Bonded (RUNNING) 7: MALC POTS 48/with Packet Voice (NOT_PROV) 11: MALC ACT ETH 10 (NOT_PROV) 17: MALC MTAC ENHANCED (NOT_PROV)
We will be loading software onto the MALC NTN/EFM card in slot 5 2
Enter a card add command with the proper card profile zSH> card add 1/5/5074
When the card-profile is added a notice will be displayed to the terminal. new card-profile 1/5/5074 added, sw-file-name "malcgshdslbonded.bin"
3
If you enter another slots command you will see that the software is being loaded onto the card. zSH> slots Uplinks 1: MALC FEGE RPR (RUNNING) Cards 5: MALC NTN/EFM GSHDSL Bonded/with NTP (LOADING) 6: MALC ADSL 48 ANNEX A/M Bonded (RUNNING) 7: MALC POTS 48/with Packet Voice (NOT_PROV) 11: MALC ACT ETH 10 (NOT_PROV) 17: MALC MTAC ENHANCED (NOT_PROV)
50
MALC Configuration Guide
SLMS command line interface
When the software is loaded a notice will be displayed to the terminal. OCT 28 11:43:44: notice : 1/1/12 : shelfctrl: _CardUpdateMsgProcess(): l=487 : tShelfCtrl: Card in slot 5 changed state to RUNNING.
4
Once the software is loaded the state for the card will show running. zSH> slots Uplinks 1: MALC FEGE RPR (RUNNING) Cards 5: MALC NTN/EFM GSHDSL Bonded/with NTP (RUNNING) 6: MALC ADSL 48 ANNEX A/M Bonded (RUNNING) 7: MALC POTS 48/with Packet Voice (NOT_PROV) 11: MALC ACT ETH 10 (NOT_PROV) 17: MALC MTAC ENHANCED (NOT_PROV)
The card change command can be used to change a card profile settings, for example using a different card type. By default, the system validates that there is a match between the software load file and the card type. An optional parameter is available to override validation to use a software load file that does not match the card type. One use of this feature is to reuse profiles and configurations when replacing Annex A cards with Annex A/M cards. Replacement Annex A/M cards can be used as spares or backup for existing Annex A cards. The card update command can be used to modify card-profile settings after the initial card configuration. Refer to the Zhone CLI Reference Guide for a detailed command description
Commands: list, show, get, update The MALC is configured by information kept in profiles. These profiles provide access to the minute level detail of all features. Profiles configure everything from the system of the MALC to interfaces and bridges. While the profiles can be viewed (very useful for understanding configurations), the best way to configure the MALC is using CLI commands, rather than changing parameters in a profile. The CLI commands (sometimes called CLI macro commands) contain greater business intelligence about configurations and normally configure many elements in a profile or in multiple profiles. The list command shows the profiles available on the MALC (partial list shown): zSH> list aal2-audio-profile: audioProfileIdentifier/apIndex aal2-cid-profile: ifIndex/vpi/vci/cid aal2-elcp-port: ifIndex/vpi/vci/portId/portType aal2-vcl-profile: ifIndex/vpi/vci adsl-co-profile: shelf/slot/port adsl-cpe-profile: shelf/slot/port adsl-profile: shelf/slot/port
MALC Configuration Guide
51
Managing the MALC
alarm-config: ifIndex analog-fxo-cfg-profile: ifIndex analog-fxs-cfg-profile: ifIndex analog-if-cfg-profile: ifIndex atm-cc: atmVcCrossConnectIndex atm-if: ifIndex atm-if-stats: ifIndex atm-traf-descr: index atm-traf-descr-stats: index atm-vcl: ifIndex/vpi/vci atm-vcl-param: index atm-vcl-stats: ifIndex/vpi/vci atm-vpi: ifIndex/vpi atm-vpl: ifIndex/vpi bridge-interface-record: ifIndex bulk-statistic: index bulk-statistics-config: index card-profile: shelf/slot/cardType ces-config: ifIndex community-access-profile: community community-profile: community description: descriptionIndex device-codecs: index/codecType dhcp-server-group: index dhcp-server-host: index dhcp-server-lease: domain/ip-address-1/ip_address-2/ ip_address-3/ip_address-4 dhcp-server-options: index dhcp-server-subnet: index ds1-profile: index ds3-profile: ifIndex dsl-alarm: ifindex for next page, for next line, A for all, Q to quit
The list system command displays the list of system profiles. zSH> list system system 0 1 entry found.
As an example of showing a fuller list, in this case the list of bridge-interface-records currently on the MALC (partial list shown): zSH> list bridge-interface-record bridge-interface-record 1-6-1-0-adsl-0-35-1/bridge bridge-interface-record 1-6-1-0-adsl-0-35-2/bridge bridge-interface-record 1-6-1-0-adsl-0-35-3/bridge bridge-interface-record 1-6-1-0-adsl-0-35-4/bridge bridge-interface-record 1-6-1-0-adsl-0-35-5/bridge bridge-interface-record 1-6-1-0-adsl-0-35-6/bridge bridge-interface-record 1-6-1-0-adsl-0-35-7/bridge bridge-interface-record 1-6-1-0-adsl-0-35-8/bridge bridge-interface-record 1-6-1-0-adsl-0-35-9/bridge
52
MALC Configuration Guide
SLMS command line interface
bridge-interface-record 1-6-1-0-adsl-0-35-10/bridge bridge-interface-record 1-6-1-0-adsl-0-35-11/bridge bridge-interface-record 1-6-1-0-adsl-0-35-12/bridge bridge-interface-record 1-6-1-0-adsl-0-35-13/bridge bridge-interface-record 1-6-1-0-adsl-0-35-14/bridge bridge-interface-record 1-6-1-0-adsl-0-35-15/bridge bridge-interface-record 1-6-1-0-adsl-0-35-16/bridge bridge-interface-record 1-6-1-0-adsl-0-35-17/bridge bridge-interface-record 1-6-1-0-adsl-0-35-18/bridge bridge-interface-record 1-6-1-0-adsl-0-35-19/bridge for next page, for next line, A for all, Q to quit
The list profile-name command just shows the number of those profiles which exist. Other commands, such as the bridge show command for our example provide greater detail about the bridges. The show commands are useful for displaying all the options in a profile. If you need to find which country codes are available on the MALC, use the show system command. zSH> show system syscontact:-----------> {260} sysname:--------------> {260} syslocation:----------> {260} enableauthtraps:------> enabled disabled setserialno:----------> {0 - 2147483647} zmsexists:------------> true false zmsconnectionstatus:--> active inactive zmsipaddress:---------> {0 - 0} configsyncexists:-----> true false configsyncoverflow:---> true false configsyncpriority:---> none low medium high configsyncaction:-----> noaction createlist createfulllist configsyncfilename:---> {68} configsyncstatus:-----> synccomplete syncpending syncerror syncinitializing configsyncuser:-------> {36} configsyncpasswd:-----> {36} numshelves:-----------> {0 - 0}shelvesarray:---------> {36} numcards:-------------> {0 - 0} ipaddress:------------> {0 - 0} alternateipaddress:---> {0 - 0} countryregion:--------> argentina australia belgium china costarica finland france germany hongkong italy japan korea mexico netherlands newzealand singapore spain sweden switzerland uk us afghanistan albania algeria americansamoa andorra angola anguilla antarctica antiguabarbuda armenia aruba austria azerbaijan bahamas bahrain bangladesh barbados belarus belize benin bermuda bhutan bolivia bosniaherzegovina botswana bouvetisland brazil
MALC Configuration Guide
53
Managing the MALC
britishindianoceanterritory bruneidarussalam bulgaria burkinafaso burundi cambodia cameroon canada capeverde caymanislands centralafricanrepublic chad chile christmasisland cocosislands colombia comoros congo cookislands cotedivoire croatia cuba cyprus czechrepublic denmark djibouti dominica dominicanrepublic easttimor ecuador egypt elsalvador equatorialguinea eritrea estonia ethiopia falklandislands faroeislands fiji frenchguiana frenchpolynesia frenchsouthernterritories gabon gambia georgia ghana gibraltar greece greenland grenada guadeloupe guam guatemala guinea guineabissau guyana haiti heardislandmcdonaldislands holysee honduras hungary iceland india indonesia iran iraq ireland israel jamaica jordan kazakstan kenya kiribati northkorea kuwait kyrgyzstan lao latvia lebanon lesotho liberia libyanarabjamahiriya liechtenstein lithuania luxembourg macau macedonia madagascar malawi malaysia maldives mali malta marshallislands martinique mauritania mauritius mayotte micronesia moldova monaco mongolia montserrat morocco mozambique myanmar namibia nauru nepal netherlandsantilles newcaledonia nicaragua niger nigeria niue norfolkisland northernmarianaislands norway oman pakistan palau palestinianterritory panama papuanewguinea paraguay peru philippines pitcairn poland portugal puertorico qatar reunion romania russia rwanda sainthelena saintkittsnevis saintlucia saintpierremiquelon saintvincentthegrenadines samoa sanmarino saotomeprincipe saudiarabia senegal seychelles sierraleone slovakia slovenia solomonislands somalia southafrica southgeorgia srilanka sudan suriname svalbardjanmayen swaziland syria taiwan tajikistan tanzania thailand togo tokelau tonga trinidadtobago tunisia turkey turkmenistan turkscaicosislands uganda ukraine unitedarabemirates uruguay uzbekistan vanuatu venezuela vietnam virginislandsuk virginislandsus wallisfutuna westernsahara yemen yugoslavia zambia zimbabwe primaryclocksource:---> [Shelf {0-255}/Slot {0-21}/Port {0-500}/SubPort/Type] | [Name/Type] ringsource:-----------> internalringsourcelabel externalringsourcelabel revertiveclocksource:-> true false voicebandwidthcheck:--> true false alarm-levels-enabled:-> critical+major+minor+warning userauthmode:---------> local radius radiusthenlocal radiusauthindex:------> {0 - 2147483647} secure:---------------> enabled disabled webinterface:---------> enabled disabled
The get system 0 command displays the actual configuration of your MALC. The command shows the system 0 configuration, such as the syscontact,
54
MALC Configuration Guide
SLMS command line interface
sysname, syslocation; the country and other information about the system configuration. To update the system profile, like other profiles you use the update command. zSH> get system 0 system 0 syscontact: -----------> {Zhone Global Services and Support 7001 Oakport Street Oakland Ca. (877) Zhone20 (946-6320) Fax (510)777-7113
[email protected]} sysname: --------------> {Zhone Malc} syslocation: ----------> {Oakland} enableauthtraps: ------> {disabled} setserialno: ----------> {0} zmsexists: ------------> {false} zmsconnectionstatus: --> {inactive} zmsipaddress: ---------> {0.0.0.0} configsyncexists: -----> {false} configsyncoverflow: ---> {false} configsyncpriority: ---> {high} configsyncaction: -----> {noaction} configsyncfilename: ---> {} configsyncstatus: -----> {syncinitializing} configsyncuser: -------> {} configsyncpasswd: -----> ** private ** numshelves: -----------> {1} shelvesarray: ---------> {} numcards: -------------> {3} ipaddress: ------------> {0.0.0.0} alternateipaddress: ---> {0.0.0.0} countryregion: --------> {us} primaryclocksource: ---> {0/0/0/0/0} ringsource: -----------> {internalringsourcelabel} revertiveclocksource: -> {true} voicebandwidthcheck: --> {false} alarm-levels-enabled: -> {critical+major+minor+warning} userauthmode: ---------> {local} radiusauthindex: ------> {0} secure: ---------------> {disabled} webinterface: ---------> {enabled}
On the demonstration MALC the country region is set to us. You can find the syscontact information, or whether the MALC is configured to communicate with the Zhone Management System (ZMS — zmsexists, zmsconnectionstatus, zmsipaddress). The update system 0 command will allow you to walk through the profile to change specific fields. Caution: You should be very careful when altering profiles. Where available you should use CLI macro commands.
MALC Configuration Guide
55
Managing the MALC
Commands: interface show, host show, bridge show, bond show The interface show command displays the numbered or unnumbered (floating) IP interfaces currently available on the MALC. zSH> interface show 579 interfaces Interface Status Rd/Address Media/Dest Address IfName -------------------------------------------------------------------------------1/1/1/0/ip UP 1 192.24.200.223/24 00:01:47:43:c0:38 ethernet1 1/1/1/0/ip DOWN 1 [10.223.8.1] 0/772 multipoint 1-10-21-0-adsl-0-35 1/1/1/0/ip DOWN 1 [10.223.8.1] 0/764 multipoint 1-10-13-0-adsl-0-35 1/1/1/0/ip DOWN 1 [10.223.8.1] 0/756 multipoint 1-10-5-0-adsl-0-35 1/1/1/0/ip DOWN 1 [10.223.8.1] 0/614 multipoint 1-9-4-0-adsl-0-35 1/1/1/0/ip DOWN 1 [10.223.8.1] 0/530 multipoint 1-8-10-0-adsl-0-35 1/1/1/0/ip DOWN 1 [10.223.8.1] 0/472 multipoint 1-7-29-0-adsl-0-35 1/1/1/0/ip DOWN 1 [10.223.8.1] 0/446 multipoint 1-7-16-0-adsl-0-35 1/1/1/0/ip DOWN 1 [10.223.8.1] 0/388 multipoint 1-6-35-0-adsl-0-35 1/1/1/0/ip DOWN 1 [10.223.8.1] 0/304 multipoint 1-5-41-0-adsl-0-35 1/1/1/0/ip DOWN 1 [10.223.8.1] 0/240 multipoint 1-5-9-0-adsl-0-35 1/1/1/0/ip DOWN 1 [10.223.8.1] 0/220 multipoint 1-4-47-0-adsl-0-35 1/1/1/0/ip DOWN 1 [10.223.8.1] 0/156 multipoint 1-4-15-0-adsl-0-35 1/1/1/0/ip DOWN 1 [10.223.8.1] 0/72 multipoint 1-3-21-0-adsl-0-35 1/1/1/0/ip DOWN 1 [10.223.8.1] 0/1092 multipoint 1-14-44-0-adsl-0-35 1/1/1/0/ip DOWN 1 [10.223.8.1] 0/1044 multipoint 1-13-27-0-adsl-0-35 1/1/1/0/ip DOWN 1 [10.223.8.1] 0/960 multipoint 1-12-33-0-adsl-0-35 for next page, for next line, A for all, Q to quit
Table 3: Interface show column Column
Description
Interface
Shows the interface, the card and the physical port of the IP inteface.
Status
Shows whether the interface is up or down.
Rd/Address
The default gateway for the interface.
Media/Dest Address
Media/Dest Address is either the MAC address of a device (as shown in the first row), or as in the other cases shown here ATM multipoint connection.
IfName
the interface name. In the case of ATM cross connects it is the other end of the connection.
The host show command displays interfaces when the MALC is hosting a multi-point subnet as a DHCP server. zSH> host show Rd/Address Interface Group T Host Address --------------------------------------------------------------------------1 11.11.11.254 1-5-25-0-efmbond-7 1 D 11.11.11.1
56
MALC Configuration Guide
SLMS command line interface
1 11.11.11.254
1-5-26-0-efmbond-7
1
D
11.11.11.2
The bridge show command displays the bridge interfaces on the MALC. Note that a bridge is a combination of bridge interfaces working together. zSH>bridge show Type VLAN Bridge St Table Data ----------------------------------------------------------------------------upl Tagged ethernet1-1/bridge UP S Global default [U: 3600 sec, M: 150 sec, I: 0 sec] dwn Untagged 1-5-25-0-efmbond/bridge UP D 00:00:86:43:3c:e4 zSH> bridge show 1-5-25-0-efmbond/bridge Bridge interface: 1-5-25-0-efmbond Administrative status: up Operational status: up Type:dwn Untagged
Data: D 00:00:86:43:3c:e4 D 172.16.160.225
Physical interface: 1-5-25-0/efmbond Administrative status: up Operational status: Line Up Unicast packets received Multicast packets received Broadcast packets received Unicast packets sent Multicast packets sent Broadcast packets sent Packet transmit errors
594 0 13 605 0 0 0
= = = = = = =
1 0 1 1 0 0 0
per per per per per per per
second second second second second second second
When you have cards which support bonding, such as the EFM SHDSL, EFM T1/E1 or some of the ADSL cards, the bond show all command will show all the bond groups
Commands: bridge stats bridge stats
You can use the bridge stats command to view the packets being sent or received on bridge interfaces. If you add the name of a bridge you can see stats for that bridge. In this example we will check the activity on a bond group on an EFM SHDSL card. . zSH> bridge stats Interface Name ethernet1-1 1-5-25-0-efmbond
Received Packets UCast MCast BCast 1201 412 527 547 0 6
Transmitted Packets UCast MCast Bcast 2212 0 481 564 0 0
Error 0 0
The EFM SHDSL card is in slot 5 and the bond group ID is 25.It appears that this is a new bridge. The number six in the broadcast column shows that the
MALC Configuration Guide
57
Managing the MALC
MALC has only received 6 broadcast packets. These packets are probably either ARP or DHCP requests from a downstream device.
SLMS Web interface The MALC enables Web-based configuration using the Zhone SLMS Web Interface Tool. The Zhone SLMS Web Interface Tool supports Malc723, Malc719, Malc319 configuration and management using the following cards for 1.13.2 and earlier features:
Managing the MALC using Zhone Web User Interface To manage the MALC using the Zhone Web User Interface:
•
Add an IP address to the interface to be used for management. On the MALC-UPLINK-2-GE uplink or MALC-UPLINK-2-FE/FE uplink cards, the interface on the 10/100 Ethernet port or GigE ports can be used. Ensure that the IP address is in the same subnet as the client devices and is reachable through Telnet. This example adds an IP interface for 172.24.94.103 to the 10/100 Ethernet port using VLAN 94.
zSH> interface add 1-1-1-0/ethernetcsamcd vlan 94 172.24.94.103/24 Created ip-interface-record ethernet1-94/ip
•
Configure a default route to the IP interface. The default route enables connectivity to the IP interface.
zSH> route add default 94 172.24.94.103 metric 1
Note: A cross-over cable is required to manage the MALC from the 10/100 or GigE port. To launch the Zhone Web User Interface, in a browser URL address space on a PC with connectivity to the MALC, enter the IP address configured on the MALC. The Zhone Web User Interface launches and displays the Login window for the MALC.
58
MALC Configuration Guide
SLMS Web interface
Figure 7: Zhone Web User Interface Login Screen
On the Login page, enter the user name and password. The default user name is admin and the default password is zhone. Click the desired menu to display the management options. For online help, click the Help icon
or product title in any window.
Note: The del command can be used to delete all of the Zhone Web User Interface files if needed.
Web UI card support The Web UI supports the following cards: MALC uplink cards:
•
MALC-UPLINK-2-GE card
•
MALC-UPLINK-2-FE/GE card
MALC Configuration Guide
59
Managing the MALC
MALC downlink cards:
•
ADSL cards MALC-ADSL-48A (single slot ADSL Annex A) MALC-ADSL+POTS-TDM-48A-2S (two slot ADSL Annex A with TDM POTS) MALC-ADSL+POTS-TDM/PKT-48A-2S (two slot ADSL Annex A with TDM POTS and packet voice support) MALC-ADSL-48A/M MALC-ADSL+POTS-PKT-48A/M-2S (two slot ADSL Annex A with TDM POTS and packet voice support) MALC-ADSL+POTS-TDM-48-2S (two slot ADSL with TDM POTS) MALC-ADSL+SPLTR-48A/M-2S (two slot ADSL Annex A/M with splitter)
•
GPON cards MALC-GPON-SC1
•
G.SHDSL cards MALC-G.SHDSL-4W-12 MALC-SHDSL-48
•
MTAC cards MALC-MTAC/RING-ENH MALC-MTAC/RING-FC (MALC 319 only) MALC-MTAC/RING
•
POTS cards MALC-POTS-GBL-TDM/PKT-24 MALC-POTS-TDM/PKT-48 (single slot with POTS TDM and packet voice support)
•
T1/E1 cards MALC-T1/E1-ATM-32 MALC-T1/E1-CES-12 * No Add card or provisioning MALC-EFM-T1/E1-24 * No Add card or provisioning
•
Voicegateway cards MALC-VG-T1/E1-32-2S MALC-VG-T1/E1-8-2S
Features not currently supported in the Web Interface Tool:
•
60
MALC Configuration Guide
Voice connection through uplink RPR ports.
Zhone Management System (ZMS)
•
GR303 voice connection through uplink RPR ports. Only GR303-VG allowed.
•
V5.2 interface, voice provisioning, and connection table support.
•
VoIP to V5.2 provisioning.
•
ISDN port provisioning.
•
ISDN voice provisioning and connection table.
•
ATM T1 IMA provisioning.
•
AAL2 support.
Zhone Management System (ZMS) The system profile contains parameters that configure the system contact information for the MALC and connection information for the ZMS. This profile does not need to be modified in order to manage the MALC with ZMS. Note: For details on using ZMS, refer to the ZMS Administrator's Guide and the NetHorizhon User's Guide.
CLI provisioning and ZMS Making a change to the device configuration CLI configuration of a device being managed by the ZMS is disabled by default. Attempting to configure the device results in an error: If you plan to use a script to provision the device from the CLI while it is being managed by the ZMS: 1
Update the system profile to disable partial config syncs to ZMS:
zSH> update system 0 Please provide the following: [q]uit. syscontact: ----------> {Zhone Global Services and Support 7001 Oakport Road Oakland Ca. (877) Zhone20 (946-6320) Fax (510)777-7113
[email protected]}: sysname: -------------> {Zhone MALC}: syslocation: ---------> {Oakland}: enableauthtraps: -----> {disabled}: setserialno: ---------> {0}: zmsexists: -----------> {true}: false zmsconnectionstatus: -> {inactive}: zmsipaddress: --------> {192.168.210.28}: configsyncexists: ----> {false}: configsyncoverflow: --> {false}: configsyncpriority: --> {high}: configsyncaction: ----> {noaction}: configsyncfilename: --> {192.168.8.21_4_1014067321329}: configsyncstatus: ----> {synccomplete}:
MALC Configuration Guide
61
Managing the MALC
configsyncuser: ------> {cfgsync}: configsyncpasswd: ----> {}: ** private ** numshelves: ----------> {1}: shelvesarray: --------> {}: numcards: ------------> {3}: ipaddress: -----------> {192.168.8.21}: alternateipaddress: --> {0.0.0.0}: countryregion: -------> {us}: primaryclocksource: --> {0/0/0/0/0}: ringsource: ----------> {internalringsourcelabel}: revertiveclocksource: -> {true} voicebandwidthcheck: --> {false} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
2
After the provisioning is complete, perform a full config sync from ZMS.
Please refer to the ZMS Administrator’s Guide for further information. Note: For details on using ZMS, refer to the ZMS Administrator's Guide and the NetHorizhon User's Guide.
Configuring other CLI management interfaces This section describes how to configure the following interfaces to remotely manage the MALC:
•
VLAN management interface on page 64
•
Uplink card 10/100 BaseT Ethernet interface on page 62
•
Configuring ATM management on page 67 Note: Ethernet interfaces can be addressed as either eth or ethernetcsmacd. The eth abbreviation is used in command output.
Configuring Ethernet on the MALC Configuring Ethernet may be done by configuring the Ethernet interface and creating default routes, or by configuring the Ethernet interface, then adding a Virtual LAN (VLAN) management interface. The VLAN management interface provides a logical means to identify by a VLAN ID number rather than by MAC addresses.
Uplink card 10/100 BaseT Ethernet interface The 10/100 BaseT Ethernet Uplink cards have three Ethernet ports. the 10/ 100 port is eth1 and the Gigabit Ethernet (GigE) ports are eth1 and eth2.
62
MALC Configuration Guide
Configuring other CLI management interfaces
The ip-interface-record for the Uplink card is named ethernet1. This interface is shared between the two Ethernet ports on redundant Uplink cards (if they exist). The system can be reached using the address configured in the ethernet1 ip-interface-record, no matter which card is active. Caution: The Uplink card Ethernet interface must be configured before any other interfaces on the system, even if you do not intend to manage the unit over the Ethernet.
Configuring the Ethernet IP interface The following example configures the IP address for the system: zSH> interface add 1-1-1-0/ethernetcsmacd static 192.168.8.21 255.255.255.0 Created ip-interface-record ethernet1/ip
Note: If you have problems with IP interfaces not automatically binding, refer to for more information.
Verifying the interface Use the interface show command to verify that the Ethernet interface was configured correctly: zSH> interface show Interface Status Rd/Address Media/Dest Address IfName --------------------------------------------------------------------------1/1/1/0/ip UP 1 192.168.8.21/24 00:01:47:65:02:f2 1-1-1-0
Creating a default route The following example creates a default route using the gateway 192.168.8.1 with a cost of 1 (one): route add default 192.168.8.1 1
Verifying the route Use the route show command to verify that the routes were added: zSH> route show Dest Nexthop Cost Owner -----------------------------------------------------------0.0.0.0/0 192.168.8.1 1 STATICLOW 192.168.8.0/24 1/1/1/0/ip 1 LOCAL
Use the ping command to verify connectivity to the default gateway: zSH> ping 192.168.8.1 PING 192.168.8.1: 64 data bytes !!!!! ----192.168.8.1 PING Statistics---5 packets transmitted, 5 packets received
MALC Configuration Guide
63
Managing the MALC
round-trip (ms)
min/avg/max = 0/0/0
To stop the ping, press CTRL+C.
Adding a route to the remote LAN After creating the IP interface, you might need to create a route to the remote device’s LAN interface using the route add command. The command uses the following syntax: route add destination mask next-hop cost
For example, in the following configuration, add a route to the 192.168.10.0 network using the MALC Uplink interface as the gateway. Figure 8: Adding a remote route to LAN
ATM
192.168.8.1
192.168.8.21
192.168.10.0
route add 192.168.10.0 255.255.255.0 192.168.8.1 1
VLAN management interface VLAN management is much quicker and easier than setting up an Ethernet port and adding routes. To create a management interface over the first GigE port, use the interface add command and specify a VLAN: zSH> interface add 1-1-2-0/ethernetcsmacd vlan 99 10.10.10.1/24 Created ip-interface-record ethernet1-99/ip
64
MALC Configuration Guide
Configuring other CLI management interfaces
IP on a bridge IP on a bridge allows users to put an IP address on a bridged VLAN. This allows VLANs to be used to manage multiple MALCs or other devices. One IP on a bridge can be created on a MALC. User MALC or other Zhone SLMS device
VLAN 100 200
10.11.12.13/24
Create the IP on a bridge interface Create an IP on a bridge interface using the IP address of 10.11.12.13/24, and a logical port interface 6 with a VLAN 200 Note: The logical port interface for IP on a bridge must be 1-1-6-0/ ipobridge for correct transmission of IP packets. 1
Enter interface add interface/type with the type as ipobridge:
zSH> interface add 1-1-6-0/ipobridge vlan 200 10.11.12.13/24 Created ip-interface-record ipobridge-200/ip.
This command creates the new IP interface as well as a new bridge. The bridge created will be a Transparent LAN Service (TLS) bridge. 2
Enter interface show to verify the IP interface and then bridge show to verify the bridge:
zSH> interface show 2 interfaces Interface Status Rd/Address Media/Dest Address IfName -------------------------------------------------------------------------------1/1/2/0/ip UP 1 172.24.94.98/24 00:01:47:10:48:08 ethernet2-94 1/1/6/0/ip UP 1 10.11.12.13/24 00:01:47:10:48:07 ipobridge-200 --------------------------------------------------------------------------------
MALC Configuration Guide
65
Managing the MALC
zSH> bridge show Type VLAN Bridge St Table Data --------------------------------------------------------------------------------tls Tagged 200 ipobridge-200/bridge UP D 00:01:47:10:48:07
3
Create another bridge on an uplink port to manage traffic going to the uplink card with bridge add, then verify the bridge created with bridge show:
zSH> bridge add 1/1/1/0/eth tls vlan 200 tagged Adding bridge on 1/1/1/0/eth Created bridge-interface-record ethernet1-200/bridge zSH> bridge show Type VLAN Bridge St Table Data --------------------------------------------------------------------------------tls Tagged 200 ipobridge-200/bridge UP D 00:01:47:10:48:07 tls Tagged 200 ethernet1-200/bridge UP
The uplink card is now reachable from the upstream, and IP 10.11.12.13/ 24 can reach other upstream devices on the same VLAN.
Deleting IP on a bridge Delete the IP on a bridge interface, and the uplink bridge on the same VLAN when necessary. zSH> interface delete 1/1/6/0/ip vlan 200 Delete complete
Both the IP on a bridge interface is deleted and the ipo tls bridge are deleted. zSH> bridge show Type VLAN Bridge St Table Data --------------------------------------------------------------------------------zSH> interface show 1 interface Interface Status Rd/Address Media/Dest Address IfName -------------------------------------------------------------------------------1/1/2/0/ip UP 1 172.24.94.98/24 00:01:47:10:48:08 ethernet2-94 --------------------------------------------------------------------------------
Follow the same steps to create an IP on a bridge and bridges for downstream devices. Note: The IP on a bridge feature does not support SNMP.
66
MALC Configuration Guide
Configuring other CLI management interfaces
Configuring ATM management The MALC can terminate an Asynchronous Transfer Mode (ATM) permanent virtual circuit (PVC) and route it over an Ethernet interface for management traffic. The following table summarizes the configuration tasks for creating an ATM management connection. Task
Command
Create a traffic descriptor. See Creating the ATM traffic descriptor on page 67.
new atm-traf-descr index
Create the VCL. See Creating the ATM management VCL on page 67.
interface add interface/atm vc vpi/vci td td_index static IpAddress Netmask
Multiple connections can use the same traffic descriptors and a single VCL must use the same traffic descriptor for both transmit and receive.
This command creates the ATM VCL and the IP interface for the management PVC. Add a route to the Ethernet interface. See Adding a default route to the ATM network on page 68.
route add destination netmask nexthop cost This enables the MALC to route from the IP management interface to the Ethernet interface
Creating the ATM traffic descriptor Create a new atm-traf-descr profile and specify a unique index: zSH> new atm-traf-descr 200 Please provide the following: [q]uit. td_type: ------------- {atmNoClpNoScr}: enter traffic descriptor type td_param1: ----------- {0}: enter PCR td_param2: ----------- {0}: enter PCR (for CLP=0 traffic) or SCR td_param3: ----------- {0}: enter MBS td_param4: ----------- {0}: enter CDVT td_param5: ----------- {0}: cac-divider: -------------> {1}: td_service_category: - {ubr}: rtvbr | nrtvbr | ubr | cbr td_frame_discard: --------> {false}: usage-parameter-control: -> {true}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Creating the ATM management VCL The following example configures an ATM connection with a VPI/VCI of 0/35 that uses the atm-traf-descr profile you just configured (with an index of 200). The VCL uses the Uplink interface: zSH> interface add uplink1/atm vc 0/35 td 200 static 192.168.1.1 255.255.255.0 Created ip-interface-record uplink1-0-35/ip
MALC Configuration Guide
67
Managing the MALC
This command creates the ip-interface-record and the associated VCL: zSH> list ip-interface-record ip-interface-record ethernet1/ip ip-interface-record uplink1-0-35/ip 2 entries found. zSH> list atm-vcl atm-vcl uplink1/atm/0/35 1 entry found.
Adding a default route to the ATM network After adding the IP interface for management, create a default route to the ATM network: route add default 192.168.1.254 1
Verifying the interface Use the interface show command to verify that the interfaces are active: zSH> interface show Interface Status Rd/Address Media/Dest Address IfName --------------------------------------------------------------------------------1/1/1/0/ip UP 1 192.168.8.21/24 08:00:3e:03:02:01 1-1-1-0 1/1/2/0/ip UP 1 192.168.1.1/24 0/35 uplink1-0-35 --------------------------------------------------------------------------------2 interfaces
68
MALC Configuration Guide
Configuring other CLI management interfaces
CPE Manager The MALC’s CPE Manager provides a means for managing consumer premesis equipment (CPE) devices without requiring extra routable IP addresses to reach these CPE end-points. While the CPE Manager is specifically designed for Zhone’s EtherXtend family of CPE products, CPE Manager can be used with any CPE device which supports IP addresses on a VLAN. In many service provider networks, the increasing usage of IP-aware CPE devices creates an operational challenge for service providers because the number of devices which require IP addresses cause IP address space depletion, making it hard to assign routable addresses for these devices. A solution to this problem is the SLMS CPE Manager. CPE Manager adds proxy capability to SLMS, allowing one IP interface on the Zhone central office device to provide IP access to all the subtended CPE devices connected to it. This one IP interface is created on an upstream port which is routable on the service providers management network, and it provides IP address and protocol port translation when forwarding packets to and from managed CPE devices. In this way, IP can be used for CPE management without having to consume IP address space or having to add network routes for reachability of line side CPE devices.
Inside
CPE base port (51921) + public port offset (4 for telnet port)
translation table Keeps a translation of CPE base port to local ip address
hX
Et
hX
Dynamically creates a private VLAN network and assigns local IP addresses to CPE devices.
Et
hX
Et
hX
IP
Et
Outside
Et
hX
Et
hX
system 0 zmsipaddress 192.168.254.1
defaults VLAN 7 1.0.0.0
To access a CPE configured using CPE Manager, access the MALC through its IP address, however, instead of using the well known protocol ports, use the CPE's base public port plus an offset to the specific port used for the
MALC Configuration Guide
69
Managing the MALC
protocol desired. Supported protocols include Echo, FTP (data), FTP (control), SSH, Telnet, HTTP, SNMP and HTTPS. A list of offsets for public ports is given in Offsets for public ports, page 70. Note: Up to 480 CPE devices may be managed using the CPE manager from a single MALC. Table 4: Offsets for public ports Well known port
Type
Name
Public port offset
7
TCP, UDP
ECHO
+0
20
TCP
FTP - data
+1
21
TCP
FTP - control
+2
22
TCP, UDP
SSH
+3
23
TCP, UDP
Telnet
+4
80
TCP
HTTP
+5
81
TCP
HTTP
+6
161
TCP, UDP
SNMP
+7
443
TCP
HTTPS
+8
The private class A network is set up by default as 1.0.0.0/8 on VLAN 7. These defaults may be changed, see Changing the VLAN or class A network used as the CPE manager local network, page 71. The IP addresses given to CPEs follow the general guidelines: ...
By default we use the 1.0.0.0 class A network. In other words, a class A network is one that has an 8 bit mask which means only the first byte of the IP address is common between nodes in the network. If you execute the following command: cpe-mgr add local network 2.0.0.0, the class A network will be changed and all local IP will start with 2.
70
MALC Configuration Guide
Configuring other CLI management interfaces
Configuring the MALC as a CPE manager Setting up the CPE manager from the CLI is fairly simple. 1
Add a public address for the CPE manager
cpe-mgr add public 192.168.254.1
Adding the public address for the MALC requires that the MALC has already been given an IP address. 2
Add the local device to the CPE manager.
cpe-mgr add local 1-3-42-0/efmbond
Changing the VLAN or class A network used as the CPE manager local network Ordinarily the default settings are acceptable. However if you need to change the default class A network or VLAN ID you can use the following commands: 1
To change the VLAN ID for the CPE manager local private network
cpe-mgr add local vlan
If you were to manually set the VLAN ID to the default, you would use cpe-mgr add local vlan 7
2
To manually set the local network settings
cpe-mgr add local network
If you were to manually set the local network to the default, you would use cpe-mgr add local network 1.0.0.0
Note: You can only manually set the local network settings when no CPE devices are currently configured on the network.
Verifying CPE Manager To verify or troubleshoot CPE manager, you should understand what the two commands for CPE manager do. The first cpe-mgr add public command
•
Sets natenabled to “yes” in the ip-interface-record for the public address (in our example, the 192.168.254.1 address)
The second command, cpe-mgr add local:
•
Creates a floating ip-interface record with IP address of 1.0.0.1
•
Creates an ip-unnumbered-record for the floating ip-interface record
•
Creates a dhcp-server-subnet for the 1.0.0.0 network
MALC Configuration Guide
71
Managing the MALC
•
Creates a host ip-interface-record for the CPE on interface (in our example bond group) Assigns a local IP address based on the interface description (not routable, but may be reached from the private local network, or by telnet to the MALC, then telnetting from the MALC to the device)
•
Creates a pat-bind profile of type CPE manager Note: The ip-interface-record created is not a normal “host” record and cannot be seen using the host show command.
The pat-bind profile for the first device from the example contains the local IP address (1.3.0.42) and the CPE base port (51921): zSH> get pat-bind 1 pat-bind 1 public-ipaddr: -> public-port: ---> local-ipaddr: --> local-port: ----> portType: ------>
{192.168.254.1} {51921} {1.3.0.42} {9} {cpemgr}
The local address which is given is based on the interface in the form: ...
From our example bond group, 1-3-42-0/efmbond, the local IP address (as shown above in the pat-bind 1 profile) is 1.3.0.42. If you need to verify this number, do a get on the pat-bind profile.
72
MALC Configuration Guide
Configuring other CLI management interfaces
Additional information about CPE manager The first device will be accessible by the MALC’s public IP address and the CPE base port. The CPE base port for the first device is 51921. To reach one of the well known ports you then give the offset for the public port. Well known port (7) is for echo which has an offset of zero.
1st device
2nd device
3rd device
ECHO FTP (data) FTP (control) SSH Telnet HTTP HTTP SNMP HTTPS ECHO FTP (data) FTP (control) SSH Telnet HTTP HTTP SNMP HTTPS ECHO FTP (data) FTP (control) SSH Telnet HTTP HTTP SNMP HTTPS
+0 +1 +2 +3 +4 +5 +6 +7 +8 +0 +1 +2 +3 +4 +5 +6 +7 +8 +0 +1 +2 +3 +4 +5 +6 +7 +8
51921
51930
51938
To telnet to the first CPE via the well known port, 23, you would use the CPE base port plus the public port offset of 4; You would use the MALC’s address (192.168.254.1), then 51925 (51921 + 4) to telnet to the device. From a Unix or DOS prompt it would look like telnet 192.168.254.1 51925
To access the second device you need to start with the CPE base port for that device. Each device consumes nine public ports, so the first device has a port range from 51921 - 51929, the second device has a port range from 51930 51938, the third from 51939 - 51947 and so on. To access the HTTP port on the third device from a browser, you would start from the first public port address 51921 + 18 (the 51921 start point plus two times nine for the first two devices to get to the third device range) + 5 (to get to port 80, a HTTP port) or 51944.
MALC Configuration Guide
73
Managing the MALC
As CPE devices are deleted or added, holes will form in the list of CPE devices, so the order eventually becomes arbitrary, but is used in the discussion to elucidate how the mechanism works. To find the CPE base port you can do an interface show, then get pat-bind * to find the CPE device you want. The pat-bind profile’s public-port is the CPE base port for the device.
Finding the local IP address and CPE base port To find the local port to access a CPE device use the interface show command to find the IP address and get pat-bind * to find the CPE base port. zSH> interface show 5 interfaces Interface Status Rd/Address Media/Dest Address IfName -----------------------------------------------------------------------------------1/1/1/0/ip UP 1 192.168.254.108/24 00:01:47:05:9c:bd ethernet1-1 1/3/42/0/ip UP 1 2.2.2.1/24 1-3-42-0-efmbond 1/3/42/0/ip UP 1 [1.0.0.1] 1.3.0.42 1-3-42-0-efmbond-7 1/3/45/0/ip UP 1 [1.0.0.1] 1.3.0.45 1-3-45-0-efmbond-7 1/3/208/0/ip UP 1 [1.0.0.1] 1.3.0.208 1-3-208-0-n2nbond-7 ----------------------------------------------------------------------------zSH> get pat-bind * pat-bind 4 public-ipaddr: -> {192.168.254.108} public-port: ---> {51948} local-ipaddr: --> {1.3.0.42} local-port: ----> {9} portType: ------> {cpemgr}
74
MALC Configuration Guide
pat-bind 2 public-ipaddr: -> public-port: ---> local-ipaddr: --> local-port: ----> portType: ------>
{192.168.254.108} {51930} {1.3.0.208} {9} {cpemgr}
pat-bind 1 public-ipaddr: -> public-port: ---> local-ipaddr: --> local-port: ----> portType: ------>
{192.168.254.108} {51921} {1.3.0.45} {9} {cpemgr}
3
DIAGNOSTICS AND ADMINISTRATION This chapter describes tasks you might need to perform to administer the MALC. It includes the following information:
•
System administration, page 75
•
SNMP, page 113
•
Statistics and alarms, page 115
•
Logging, page 134
•
MALC security features, page 146
•
Testing, page 152
System administration This section describes the following:
•
MALC file system on page 76
•
Accessing the flash card on page 76
•
Deleting card profiles on page 78
•
Manually binding interfaces on page 79
•
Renaming interfaces on page 80
•
Saving and restoring configurations on page 80
•
SNTP on page 89
•
System clocking on page 90
•
User accounts on page 82
•
Viewing chassis and slot information on page 88
•
Controlling Telnet access on page 97
•
Redundant Uplink cards on page 100
•
Dual, non-redundant Uplink cards on page 108
MALC Configuration Guide
75
Diagnostics and Administration
MALC file system The Uplink card flash memory contains DOS file system that stores the system boot code, software images, and the configuration. During system startup, the software images on the flash are decompressed and loaded into memory. The following commands can be used to access the file system:
•
cd. Changes directory.
•
dir. Lists the contents of the directory.
•
pwd. Displays the current working directory.
•
ata. Used to format or initialize a flash card. This is typically done only for new cards or if you want to completely erase the flash card.
•
image. Verifies software images and downloads software images on the flash to system memory.
Accessing the flash card Use the cd, dir, and pwd commands to list the contents of the file system, as in the following example: zSH> dir Listing Directory .: -rwxrwxrwx 1 0 -rwxrwxrwx 1 0 -rwxrwxrwx 1 0 drwxrwxrwx 1 0 -rwxrwxrwx 1 0 -rwxrwxrwx 1 0 -rwxrwxrwx 1 0 -rwxrwxrwx 1 0 -rwxrwxrwx 1 0
0 0 0 0 0 0 0 0 0
639836 3321852 1032722 2048 1682204 3301097 639756 1510173 1441233 75399168
Nov 27 07:00 Nov 27 07:00 Nov 27 07:00 Nov 28 12:50 Nov 27 07:01 Nov 27 07:01 Nov 27 07:01 Nov 27 07:00 Dec 6 20001 bytes free
malct1imaraw.bin malct1ima.bin malcmtac.bin datastor/ malcadslpots.bin malcds3.bin malcds3raw.bin malcgshdsl.bin malcadslac5.bin
Using the ata command The ata command formats and initializes flash cards. Formatting formats the files system, but leaves the boot partition on the card intact. Initialization reinitializes the boot partitions on the cards and formats the file system. The following example formats flash card: zSH> ata format 1
The following example initializes the flash card: zSH> ata init 1
76
MALC Configuration Guide
System administration
Using the image command The MALC contains a TFTP server that enables you to download files from a network to the flash card file system using the image command. The image command uses the following syntax: image download tftphost image-file destination
The following example downloads the image for the Uplink card (malcoc3.bin) from host 192.168.8.21 to the root directory of the first flash card: image download 192.168.8.21 malcoc3.bin malcoc3.bin
The image command can also verify image files on the flash card. It reads the contents of the file, verifies the file header, and verifies the file checksum. For example: zSH> image verify malcoc3.bin File: malcoc3.bin Size: 3186874 bytes Header Version: 1 Load Type: MALC OC3 Load Address: 0x00010000 Checksum: 0x0c847b68 Image verify successful
The command reports any errors it finds in the file. Note that files are also verified as part of the download process.
Changing the serial craft port settings Tip: You only need to modify an rs232-profile if you want to change the default configuration of the serial craft port. The MALC rs232-profile can be used to configure serial craft ports on the system. The default settings for the MALC serial control ports are:
•
9600bps
•
8 data bits
•
No parity
•
1 stop bit
•
No flow control
MALC Configuration Guide
77
Diagnostics and Administration
Changing the serial control port settings Caution: The serial craft port supports speeds of 9600, 19200, 38400, and 57600 bps. Do not set the speed to an unsupported value. Doing so could render the serial craft port inaccessible. Update an rs232-profile for the shelf and slot that contains the serial craft port. The following example updates the profile for the serial craft port in slot 1: zSH> update rs232-profile 1-1-1-0/rs232 shelf-slot-port-subport/type Please provide the following: [q]uit. rs232PortInSpeed: -------> {9600}: 57600 rs232PortOutSpeed: ------> {9600}: 57600 rs232PortInFlowType: ----> {none}: rs232PortOutFlowType: ---> {none}: rs232AsyncPortBits: -----> {8}: rs232AsyncPortStopBits: -> {one}: rs232AsyncPortParity: ---> {none}: rs232AsyncPortAutobaud: -> {disabled}: .................... Save new record? [s]ave, [c]hange or [q]uit: Record created.
The settings take effect after the profile is saved. Note: If the rs232-profile is deleted, the port speed is set to the last configured value.
Deleting card profiles Caution: Before deleting card profiles, perform the following:
• Back up the MALC configuration. See the release notes for information.
• Delete the ATM cross connects associated with the card. • For voice cards, ensure all subscribers and voice profiles are deleted before deleting the card.
• Remove the card from the system as explained in the MALC Hardware Installation Guide. Delete the card-profile for a card to delete all the profiles associated with a card. After deleting a card-profile, the specified card reboots. Caution: A delete card-profile command deletes profiles associated with the card and may disrupt service until the system is reprovisioned.
78
MALC Configuration Guide
System administration
The delete command uses the following syntax: delete card-profile 1/slot/type
Where slot is the location of the card and type is the Zhone type for the card. the card. The following example deletes an ADSL card (Zhone type 5004) in slot 13: zSH> delete card-profile 1/13/5004 Delete card-profile 1/13/5004? [y]es, [n]o, [q]uit : y card-profile 1/13/5004 deleted.
You can only delete one card-profile at a time. Wildcards are not supported when deleting card profiles.
Manually binding interfaces When creating ip-interface-record profiles, the syntax is name/type. The name of the IP interface can be user-defined or match the naming of the if-translate record for the physical interface. The system automatically binds interfaces if the name of the new IP record matches the name of the if-translate profile or if the syntax shelf/slot/port/subport/type is used. Enter a list if-translate command to determine what if-translate records are available on your system. The example below shows a new ip-interface-record being created with a user-defined name. zSH> new ip-interface-record myip/ip Please provide the following: [q]uit. vpi: ---------------> {0}: vci: ---------------> {0}: rdindex: -----------> {1}: dhcp: --------------> {none}: ** read-only ** addr: --------------> {0.0.0.0}: 192.168.88.200 netmask: -----------> {0.0.0.0}: 255.255.255.0 bcastaddr: ---------> {0.0.0.0}: 192.168.88.255 destaddr: ----------> {0.0.0.0}: farendaddr: --------> {0.0.0.0}: mru: ---------------> {1500}: reasmmaxsize: ------> {0}: ingressfiltername: -> {}: egressfiltername: --> {}: pointtopoint: ------> {no}: mcastenabled: ------> {yes}: ipfwdenabled: ------> {yes}: mcastfwdenabled: ---> {yes}: natenabled: --------> {no}: bcastenabled: ------> {yes}: ingressfilterid: ---> {0}: egressfilterid: ----> {0}: ipaddrdynamic: -----> {static}: dhcpserverenable: --> {false}: ....................
MALC Configuration Guide
79
Diagnostics and Administration
Save new record? [s]ave, [c]hange or [q]uit: s Cannot determine binding for this IP interface. Could not automatically bind this IP Interface. New record saved.
Since the system did not automatically bind the new IP interface, manually bind the interface with the stack bind command: zSH> stack bind Enter the upper layer: myip/ip the IP interface created Enter the lower layer: 1-1-1-0-ethernetcsmacd/other the line group associated with Ethernet Stack bind successful.
Note: The stack bind command does not allow binding directly to physical interfaces. You must bind two logical interfaces. Enter the stack show command (with name/type syntax) to see interface binding: zSH> stack show myip/ip Line Group: 1-1-1-0-ethernetcsmacd/other Physical: 1/1/1/0/ethernetcsmacd
Renaming interfaces Interfaces on the MALC can be renamed using the ifName parameter in the if-translate profile for the interface. For example, to rename an Uplink card T1 interface: zSH> update if-translate 1-1-1-0/ds1 Please provide the following: [q]uit. ifindex: -----> {1}: . shelf: -------> {1}: slot: --------> {1}: port: --------> {1}: subport: -----> {0}: type: --------> {ds1}: adminstatus: -> {up}: physical-flag: ----> {true}: iftype-extension: -> {0}: ifName: -----------> {1-1-1-0}: uplink_ds1_1 redundancy-param1: -> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Saving and restoring configurations The dump and restore commands enable you to save and restore the system configuration. You can save the configuration to the console, a local file, or the network.
80
MALC Configuration Guide
System administration
The command uses the following syntax: dump
[console] [file filename] [network host filename ]
Passwords are encrypted when they are saved to the configuration file. The encrypted passwords are used to restore the correct password, but cannot be used to log in. Note: The dump and restore commands use TFTP to transfer files to the network. Set the TFTP server time-out value to at least 5 seconds, and 5 retries to help prevent TFTP timeout or retry errors.
To save the configuration to a console: 1
Configure your terminal emulation software as follows: –
9600bps
–
8 data bits
–
No parity
–
1 stop bit
–
No hardware flow control
–
VT100
–
Set Line Delay and Character Delay to 40 milliseconds
2
Turn on the file capture utility of your terminal emulation software.
3
Save the configuration by entering: dump console
Do not press the Enter key. 4
Start the capture utility on your terminal emulation software and enter a name for the file (use a .txt extension).
5
Press the Enter key. The configuration file will be displayed on the screen.
6
When configuration file is finished, stop the capture utility.
Backing up the configuration to a local file To dump the configuration to a local file: Specify a file name for the configuration: zSH> dump file filename
The file is saved on the MALC filesystem.
Backing up the configuration to the network To back up the configuration to the network:
MALC Configuration Guide
81
Diagnostics and Administration
1
Create the file in the destination location of the TFTP server and make it writeable.
2
Save the configuration. The following example saves the configuration to a file named device.cfg on the host 192.168.8.21: zSH> dump network 192.168.8.21 device.cfg
Restoring the configuration For information on restoring your configuration, refer to the release notes for your release.
User accounts MALC users have access to the CLI and are able to configure and administer the system.
Adding users Every administrative user on the system must have a user account. The account specifies their username and password, as well as their privilege level, which determines their access to commands. Users with admin privileges have access to all the administrative commands. Users with user privileges have access to a very limited set of commands. The highest level of access is useradmin, which allows the creation of user accounts. Note: When entering access level responses, enter yes completely or the CLI interprets the response as no. To add a user, enter the following commands: zSH> adduser Please provide the following: [q]uit. User Name: jjsmith User Prompt[zSH>]: Please select user access levels. admin: -------> {no}: yes zhonedebug: --> {no}: voice: -------> {no}: data: --------> {no}: manuf: -------> {no}: database: ----> {no}: systems: -----> {no}: tool: --------> {no}: useradmin: ---> {no}: yes .................................. User name:(jjsmith) User prompt:(zSH>) Access Levels: (admin)(useradmin)
82
MALC Configuration Guide
System administration
Save new account? [s]ave, [c]hange or [q]uit: s User record saved. TEMPORARY PASSWORD: hmj4mxFU
Commands with zhonedebug privilege levels are intended for use by Zhone development only. Immediately after activating the user account, you should change the password something you can remember, as explained in the next section.
Changing default user passwords When adding users, the system automatically assigns a temporary password to each user. Most users will want to change their password. The changepass command changes the password for the current logged in user. The following is an example of changing a password: zSH> changepass Current Password: New Password: Confirm New Password: Password change successful.
Deleting users To delete a user, enter the deleteuser command and specify the username: zSH> deleteuser jsmith OK to delete this account? [yes] or [no]: yes User record deleted.
Deleting the admin user account In addition to deleting regular user accounts, you can also delete the admin user account. This account is automatically created by the system and provides full access to the CLI. Note: You cannot delete the admin account (or any other user account with useradmin privileges) if you are currently logged into it. To delete the admin account: zSH> deleteuser admin
If desired, you can recreate an account named admin after deleting it: zSH> adduser admin Please provide the following: [q]uit. User Name: admin User Prompt[zSH>]: Please select user access levels. admin: -------> {no}: yes
MALC Configuration Guide
83
Diagnostics and Administration
zhonedebug: --> {no}: voice: -------> {no}: yes data: --------> {no}: yes manuf: -------> {no}: yes database: ----> {no}: yes systems: -----> {no}: yes tool: --------> {no}: yes useradmin: ---> {no}: yes .................................. User name:(admin) User prompt:(zSH>) Access Levels: (admin)(voice)(data)(manuf)(database)(systems)(tools)(use radmin) Save new account? [s]ave, [c]hange or [q]uit: s User record saved. TEMPORARY PASSWORD: hmj4mxFU
Resetting passwords If a user forgets their password, an administrative user can reset the password and generate a new one using the resetpass command, as in the following example: zSH> resetpass jsmith Password:
Radius support The MALC supports local and RADIUS (Remote Authentication Dial In User Service) access authentication. The MALC can be configured for local authentication, RADIUS authentication, or RADIUS then local authentication. RADIUS users are configured with the Service-Type attribute as Administrative-User or NAS-Prompt-User. RADIUS is used for only login authentication, not severity levels. Table 5 shows the mapping of service-type to MALC permissions. Table 5: Service type mapping to MALC permissions Service-Type Attribute
MALC permissions
Administrative-User
admin, zhonedebug, voice, data, manuf, database, systems, tools, useradmin
NAS-Prompt-User
admin, voice, data, manuf, database, systems, tools, useradmin
When establishing a connection to the MALC with RADIUS authentication, the MALC passes RADIUS information securely to the RADIUS server. The RADIUS server then authenicates the user and either allows or denies access to the MALC. If access is denied and the local authentication option is also configured, the MALC then authenticates access based on the locally
84
MALC Configuration Guide
System administration
configured users and passwords. For logins and failed logins, a console message is generated with user ID and IP address of the device from which the login originated. Failed logins also are logged as alert level messages in the MALC system log file. By default, RADIUS access uses the UDP port 1812 for authentication.This parameter can be changed in the radius-client profile. Figure 9: MALC RADIUS authentication
Telnet user
IP
Telnet
RADIUS server
MALC Console user
Local authentication RADIUS authentication
Note: Follow the RADIUS server guidelines for RADIUS configuration instructions. For example, when using the MALC with the FreeRadius server:
• Create only one entry in the clients.conf file for each subnet or individual MALC. For individual MALCs, the IP in this file must match the IP address of the outbound interface used by the MALC to connect to the RADIUS server.
• The MALC uses the value stored in the RADIUS system.sysname file for the NAS-Identifier attribute.
• The shared-secret in the MALC radius-client profile, must exactly match the shared-secret in the RADIUS client entry.
Configuring RADIUS support The MALC can be configured for local authentication, RADIUS authentication, or RADIUS then local authentication. Multiple radius-client profiles can be defined using the index and subindex numbers. This index scheme can be used to create index numbers for groups of RADIUS servers. When an index number is specified in the system profile, the MALC attempts authenication from each RADIUS server in that group in sequential order of the subindex numbers. To configure RADIUS support:
MALC Configuration Guide
85
Diagnostics and Administration
Note: Before beginning this procedure, ensure that the MALC has IP connectivity to the RADIUS server. 1
Update the RADIUS server with settings for the Zhone prompts.
2
Create a radius-client profile on the MALC with the desired index number and RADIUS settings for server name, shared secret, number of retries, and other parameters. The first number in the index is used to group radius-client profiles so multiple profiles can be assigned to a MALC. The second number in the index specifies the order in which radius-client profiles are referenced. This example specifies the radius-client 1/1 with server name radius1 and a shared-secret of secret. A DNS resolver must be configured in the system to resolve the server name and IP address.If a DNS resolver is not available, specify the IP address of the The index 1/1 specifies that this profile is the first profile in group 1.
zSH> new radius-client 1/1 Please provide the following: [q]uit. server-name: ----> {}: radius1.test.com [DNS resolver must be configured in the system.] udp-port: -------> {1812}: shared-secret: --> {** password **}: secret retry-count: ----> {5}: retry-interval: -> {1}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created.
Another method to reference the RADIUS server is by specifying the IP address. This example specifies the radius-client 1/1 with server IP address 172.24.36.148 and a shared-secret of secret. The index 1/1 specifies that this profile is the first profile in group 1. zSH> new radius-client 1/1 Please provide the following: [q]uit. server-name: ----> {}: 172.24.36.248 udp-port: -------> {1812}: shared-secret: --> {** password **}: secret retry-count: ----> {5}: retry-interval: -> {1}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created.
3
Create another radius-client profile on the MALC with the desired RADIUS settings for server name, shared secret, number of retries, and other parameters. This example specifies the radius-client 1/2 with server IP address 172.24.36.148 and a shared-secret of secret. The index 1/2 specifies that this profile is the second profile in group 1.
zSH> new radius-client 1/2 Please provide the following: [q]uit. server-name: ----> {}: 172.24.36.249 udp-port: -------> {1812}:
86
MALC Configuration Guide
System administration
shared-secret: --> {** password **}: secret retry-count: ----> {5}: retry-interval: -> {1}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created.
Create additional radius-client profiles for each additional RADIUS server to be assigned to this MALC. 4
In the system profile on the MALC, set the desired user authentication method and specify the index of the radius profile to use. This examples specifies the radiusauthindex of 1. This index is configured with two radius-client profiles (1/1, 1/2). The MALC first attempts authenication using the server specified in radius-client 1/1. If this authenitication fails, the MALC attempts authenication using radius-client 1/2 server. If this authentication also fails, the MALC then attempts authentication based on the authentication mode setting in the system profile. This example uses radiusthenlocal. Caution: If the radius authentication mode is used, local authentication is disabled so the MALC may become inaccessible if IP connectivity to the RADIUS server is lost or other changes prevent the MALC from receiving RADIUS authentication.
zSH> update system 0 Please provide the following: [q]uit. syscontact: -----------> {Zhone Global Services and Support 7001 Oakport Street Oakland Ca. (877) Zhone20 (946-6320) Fax (510)777-7113
[email protected]}: sysname: --------------> {Malc1}: syslocation: ----------> {Oakland}: enableauthtraps: ------> {disabled}: setserialno: ----------> {0}: zmsexists: ------------> {true}: zmsconnectionstatus: --> {inactive}: zmsipaddress: ---------> {172.16.49.76}: configsyncexists: -----> {false}: configsyncoverflow: ---> {false}: configsyncpriority: ---> {high}: configsyncaction: -----> {noaction}: configsyncfilename: ---> {172.16.88.14_4_1178142210378}: configsyncstatus: -----> {synccomplete}: configsyncuser: -------> {zmsftp}: configsyncpasswd: -----> {** private **}: ** read-only ** numshelves: -----------> {1}: shelvesarray: ---------> {}: numcards: -------------> {3}: ipaddress: ------------> {172.16.88.14}: alternateipaddress: ---> {0.0.0.0}: countryregion: --------> {us}: primaryclocksource: ---> {0/0/0/0/0}: ringsource: -----------> {internalringsourcelabel}:
MALC Configuration Guide
87
Diagnostics and Administration
revertiveclocksource: -> {true}: voicebandwidthcheck: --> {false}: alarm-levels-enabled: -> {critical+major+minor+warning}: userauthmode: ---------> {local}: radiusthenlocal radiusauthindex: ------> {0}: 1 .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated. zSH>
After completing the RADIUS configuration, the MALC displays console messages for RADIUS login and logout activity.
For users logging in through RADIUS, the system prompt appears as the username@systemname. For example, the system prompt for a basic user on a MALC using the default Zhone Malc system name will appear as basicuser@Zhone malc. The system name is configured using the sysname parameter in the System 0 profile.
Viewing chassis and slot information The following commands display information about the status of the system:
•
shelfctrl
•
slots
To view overall status of the system, use the shelfctrl monitor command: zSH> shelfctrl monitor Shelf Monitor CPLD version: 1.2 Shelf Monitor Firmware version: 1.6 Inlet temperature 79 degrees. Left outlet temperature sensor: 78 degrees (normal) Right outlet temperature sensor: 78 degrees (normal) Power Supply A: failure Power Supply B: normal Fan status: OK. System: Critical alarm set. Card 12: Critical alarm set.
To view general system statistics: zSH> shelfctrl stats Shelf Controller Message Statistics ----------------------------------Card updates: 42 Card ECHO: 0 Directory services messages: 2 Clock messages: 178707 Lease messages: 496 Heartbeat messages: 470902
88
MALC Configuration Guide
System administration
Card update errors: 0 Card ECHO errors: 0 Directory services errors: 0 Clock errors: 0 Lease errors: 0 Heartbeat errors: 0 Receive errors: 0
To verify whether the shelf is active: zSH> shelfctrl show Shelf Controller Address: 01:02:12 Shelf Registry Address: 01:02:75 Lease ID: 0x022b0008_00000036 State: active
To view the system slot cards and their status: zSH> slots 1: MALC OC3 (RUNNING) 5: MALC ADSL AC5 (RUNNING) 6: MALC ADSL AC5 (LOADING) 7: MALC ADSL AC5 (RUNNING) 8: MALC ADSL AC5 (RUNNING) 9: MALC ADSL (RUNNING) 13: MALC MTAC (RUNNING) 16: MALC ADSL AC6 (RUNNING) 20: MALC GSHDSL (RUNNING) 21: MALC GSHDSL (RUNNING)
To view information about a particular slot card, use the slots command and specify a slot number. For example: zSH> slots 1 Type Card Version EEPROM Version Serial # CLEI Code Card-Profile ID Shelf Slot State Mode Heartbeat check Longest hbeat Fault reset Uptime
: : : : : : : : : : : : : :
MALC OC3 1 1 7714040 No CLEI 1/1/5011 1 1 RUNNING FUNCTIONAL enabled 50 enabled 1 hour, 49 minutes
SNTP Simple Network Time Protocol (SNTP) is a method for synchronizing clock of networked systems. You can setup the MALC to access an SNTP server, so that the MALC’s date and time is given by the SNTP server.
MALC Configuration Guide
89
Diagnostics and Administration
To set up the system to use SNTP: Update the ntp-client-config profile. For example: zSH> update ntp-client-config 0 Please provide the following: [q]uit. primary-ntp-server-ip-address: ---> {0.0.0.0}: 192.168.8.100 secondary-ntp-server-ip-address: -> {0.0.0.0}: local-timezone: ------------------> {gmt}: pacific daylight-savings-time: -----------> {false}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
System clocking The following table summarizes the tasks for configuring system clocking on the MALC. Task
Command
Update the ds1-profile, sonet-profile, or ds3-profile to verify the type of clocking for the interface. See Configuring a DS1 or MTAC/Ring clock source on page 93
update ds1-profile shelf-slot-port-subport/ds1
Configuring a DS3 clock source on page 93,
or
Configuring an OC-3c/STM1 clock source on page 94. Update the system-clock-profile to specify whether the clock is eligible and to assign a weight. See Configuring a DS1 or MTAC/Ring clock source on page 93 Configuring a DS3 clock source on page 93. If required, specify a system clock in the system-profile. See Configuring a clock source in the system profile on page 96.
The MTAC/Ring card has a single ds1-profile for the BITS clock interface. or update ds3-profile shelf-slot-port-subport/ds3 update sonet-profile shelf-slot-port-subport/ sonet update system-clock-profile shelf-slot-port-0/ type Where type is ds1, ds3, or sonet. The MALC creates system-clock-profiles for each interface in the system that can provide clock. By default, interfaces are not eligible to provide clock and all interfaces have an equal weight of 5. update system 0 Clock sources specified in the system-profile always override settings in system-clock-profiles. Note: system-clock-profiles are recommended for configuring clock sources.
90
MALC Configuration Guide
System administration
Overview The MALC can receive system clocking from one of the following sources:
•
The DS1 interfaces on the T1/E1 Uplink card (MALC-UPLINK-T1/ E1-ATM/IP-16)
•
The DS3 interfaces on the DS3 Uplink card (MALC-UPLINK-DS3/ E3-ATM/IP)
•
OC3C/STM1 interfaces on the OC3C/STM1 Uplink card (MALC-UPLINK-OC3C/ATM1-ATM/IP)
•
The DS1 interfaces on the T1/E1 EFM card (MALC-EFM-T1/E1-24)
•
The DS1 interfaces on the voicegateway cards (MALC-VG-T1/E1-32-2S and MALC-VG-T1/E1-8-2S) Note: When a voicegateway card is used, the MALC system clock must receive timing from a DS1 interface on the voicegateway card.
•
The DS1 interfaces on the CES card (MALC-T1/E1-CES-12
•
The DS1 interfaces on the T1/E1/ATM card (MALC-T1/E1-ATM-32.
•
The BITS clock source on the MTAC/Ring cards (MALC-MTAC/RING, MALC-MTAC/RING-ENH, and MALC-MTAC/RING-FC) This clock source has a type of DS1. Note: Interfaces that are designated as eligible clock sources cannot be set to through timing
The MALC creates system-clock-profiles for each interface that can provide clock for the system. These profiles define the clock sources that are eligible to provide system clock and defines the weights for the clock on the interface. 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 has been configured in the system profile, this clock source overrides all other clocks. Note the following information about redundant clock sources on the MALC:
•
By default, interfaces are not eligible to provide clock.
•
The clock source with the highest weight becomes the primary clock source. Weights are from 1 (lowest priority) to 10 (highest priority).
MALC Configuration Guide
91
Diagnostics and Administration
•
If a clock source is defined in the primaryclocksource parameter in the system profile, that clock source takes precedence over the settings in the system-clock-source profiles, if any. Clock sources defined in the system profile are given a weight of 11.
•
If you assign weight to a clock source that is higher than the currently active clock source, or if you assign a clock source in the system profile, the system will switch over to the new clock source.
The following table describes the parameters used to provide clocking for the the system. Parameter
Description
transmit-clock-source
There are three clocking options for DS1/DS3 interfaces:
(ds1-profile, ds3-profile, or sonet-profile)
Values: looptiming The recovered receive clock from the DS1/DS3 is used as the transmit clock. localtiming A local (to the DS1/DS3 interface) clock source is used on the DS1/DS3 transmit signal. throughtiming The transmit DS1/DS3 clock is derived from the recovered receive clock of another DS1/DS3 interface. Interfaces that are designated as eligible clock sources cannot be set to through timing. Default: looptiming (DS3) throughtiming (DS1)
primaryclocksource (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. Note: If configured, the setting in the primaryclocksource parameter overrides settings in the system-clock-profile for all interfaces that provide clocking.
system-clock-eligibility (system-clock-profile)
Specifies whether the interface is eligible to provide clocking for the system. Values: true false Default: false
system-clock-weight (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
92
MALC Configuration Guide
System administration
Configuring a DS1 or MTAC/Ring clock source 1
Verify that the interface that is to provide clock is up and active.
2
Verify the transmit-clock-source parameter in the ds1-profile is set to looptiming:
zSH> update ds1-profile 1-1-1-0/ds1 for the MTAC/Ring card, enter the shelf-slot-port-subbport 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: -> {disabled} channelization: -----------------> {enabledds0} ds1-mode: -----------------------> {csu} csu-line-length: ----------------> {csu00} clock-source-eligible: ----------> {eligible} transmit-clock-source: ----------> {looptiming} cell-scramble: ------------------> {false} coset-polynomial: ---------------> {true}: protocol-emulation: -------------> {network} signal-type: --------------------> {loopstart} ds1-group-number: ---------------> {0} line-power: ---------------------> {disabled} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
3
In the system-clock-profile, enable the clock source and change the default weight (if necessary): zSH> update system-clock-profile 1-1-1-0/ds1 Please provide the following: [q]uit. system-clock-eligibility: -> {false}: true system-clock-weight: ------> {5}:modify the weight if necessary .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Configuring a DS3 clock source To configure a DS3 clock source: 1
Verify that the interface that is to provide clock is up and active.
2
Verify transmit-clock-source parameter in the ds3-profile is set to looptiming:
zSH> update ds3-profile 1-1-2-0/ds3 Please provide the following: [q]uit. line-type: ---------------> {dsx3cbitparity}: line-coding: -------------> {dsx3b3zs}:s
MALC Configuration Guide
93
Diagnostics and Administration
end-code: ---------------> {dsx3sendnocode}: circuit-id: --------------> {}: loopback-config: ---------> {dsx3noloop}: transmit-clock-source: ---> {looptiming}: line-length-meters: ------> {0}: line-status-trap-enable: -> {enabled}: channelization: ----------> {disabled}: ds1-for-remote-loop: -----> {0}: far-end-equip-code: ------> {}: far-end-loc-id-code: -----> {}: far-end-frame-id-code: ---> {}: far-end-unit-code: -------> {}: far-end-fac-id-code: -----> {}: medium-scramble-config: --> {true}: medium-frame-config: -----> {e3frameg832}: medium-atmframe-config: --> {dsx3atmframingdirectcellmapped}: Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
3
In the system-clock-profile, enable the clock source and change the default weight (if necessary): zSH> update system-clock-profile 1-1-2-0/ds3 Please provide the following: [q]uit. system-clock-eligibility: -> {false}: true system-clock-weight: ------> {5}:modify the wieght if necessary .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Configuring an OC-3c/STM1 clock source To configure a OC-3c/STM1 clock source: 1
Verify that the interface that is to provide clock is up and active.
2
Verify clock-transmit-source parameter in the sonet-profile is set looptiming:
zSH> get sonet-profile 1-1-1-0/sonet Please provide the following: [q]uit. medium-type: -----------------> {sonet}: medium-line-coding: ----------> {sonetmediumnrz}: medium-line-type: ------------> {sonetlongsinglemode}: medium-circuit-identifier: ---> {}: medium-loopback-config: ------> {sonetnoloop}: path-current-width: ----------> {sts12cstm4}: clock-external-recovery: -----> {enabled}: clock-transmit-source: -------> {looptiming}: medium-cell-scramble-config: -> {true}: medium-line-scramble-config: -> {true}:
3
94
MALC Configuration Guide
In the system-clock-profile, enable the clock source and change the default weight (if necessary):
System administration
zSH> update system-clock-profile 1-1-2-0/ds3 Please provide the following: [q]uit. system-clock-eligibility: -> {false}: true system-clock-weight: ------> {5}:modify the wieght if necessary .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
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 that clock source becomes active again. Note that the clock source must be active for 30 seconds before the system will revert back to the primary clock source. To disable revertive clock sources set the revertiveclocksource parameter in the system profile to false: zSH> update system 0 Please provide the following: [q]uit. syscontact: -----------> {Zhone Global Services and Support 7001 Oakport Street Oakland Ca. (877) Zhone20 (946-6320) Fax (510)777-7113
[email protected]}: sysname: --------------> {b142}: syslocation: ----------> {Oakland}: enableauthtraps: ------> {disabled}: setserialno: ----------> {0}: zmsexists: ------------> {true}: zmsconnectionstatus: --> {inactive}: zmsipaddress: ---------> {192.25.84.91}: configsyncexists: -----> {false}: configsyncoverflow: ---> {false}: configsyncpriority: ---> {high}: configsyncaction: -----> {noaction}: configsyncfilename: ---> {192.25.202.142_4_1028333450007}: configsyncstatus: -----> {synccomplete}: configsyncuser: -------> {cfgsync}: configsyncpasswd: -----> {** private **}: ** read-only ** numshelves: -----------> {1}: shelvesarray: ---------> {}: numcards: -------------> {3}: ipaddress: ------------> {192.25.200.142}: alternateipaddress: ---> {0.0.0.0}: countryregion: --------> {us}: primaryclocksource: ---> {0/0/0/0/0}: ringsource: -----------> {internalringsourcelabel}: revertiveclocksource: -> {true}: false voicebandwidthcheck: --> {false}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record saved.
MALC Configuration Guide
95
Diagnostics and Administration
Configuring a clock source in the system profile Note: system-clock-profiles are recommended for configuring clock sources. Clock sources configured in the system profile override settings in system-clock-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. Update the system profile to specify the clock source. 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 Malc}: syslocation: ---------> {Oakland}: enableauthtraps: -----> {disabled}: setserialno: ---------> {0}: zmsexists: -----------> {false}: zmsconnectionstatus: -> {inactive}: zmsipaddress: --------> {0.0.0.0}: configsyncexists: ----> {false}: configsyncoverflow: --> {false}: configsyncpriority: --> {high}: configsyncaction: ----> {noaction}: configsyncfilename: --> {}: configsyncstatus: ----> {syncinitializing}: configsyncuser: ------> {}: configsyncpasswd: ----> {**private**}: **read-only** numshelves: ----------> {1}: shelvesarray: --------> {}: numcards: ------------> {3}: ipaddress: -----------> {192.168.8.21}: alternateipaddress: --> {0.0.0.0}: countryregion: -------> {us}: primaryclocksource: --> {0/0/0/0/0}: 1-1-1-0/dsl ringsource: ----------> {internalringsourcelabel} revertiveclocksource: -> {true} voicebandwidthcheck: --> {false} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
As soon as the profile is saved, the clock source specified becomes active.
96
MALC Configuration Guide
System administration
Viewing clock source information To view the clock information on the system, use the clkmgrshow command. This command has the following syntax: clkmgrshow [current | eligible | list ]
–
current: displays the current primary and secondary clock sources.
–
eligible: displays only the eligible clock sources. Eligible clock sources are interfaces that are configured as eligible and are active.
–
list: lists the eligible and non-eligible clock sources. Non-eligible clock sources are interfaces that either not configured as eligible, or are not active.
For example, to display the eligible and non-eligible clock sources: zSH> clkmgrshow list eligible list has 0 entries ineligible list has 5 entries 1 not eligible (4) 1/1/2 (5) : DS3 : LOOP 2 not eligible (6) 1/1/3 (5) : DS3 : LOOP 3 not eligible (8) 1/1/4 (5) : DS3 : LOOP 4 not eligible (10) 1/1/5 (5) : DS3 : LOOP 5 not eligible (26) 1/21/1 (5) : T1 : LOCAL
Controlling Telnet access The port-access profile specifies from which IP addresses users can telnet to the MALC. If a host’s IP address is not specified in a port-access profile, users from that host cannot telnet to the MALC. These restrictions take effect after the first port-access profile has been created. By default, no port-access profiles are created, so telnet access is not restricted.
Creating port-access profile entries Up to 100 port-access profile entries can be created on a MALC. To create a port-access profile entry: Create a new port-access profile and specify the telnet port number, host/ network IP address to be granted access, and the netmask applied to the IP address to allow access to a range of IP addresses. This example creates port-access entry 1 on telnet port 23 and allows hosts on the 172.16.41.xx network to telnet to the MALC. Note: Typically, only port 23 is used for telnet access.
zSH> new port-access 1 Please provide the following: [q]uit.
MALC Configuration Guide
97
Diagnostics and Administration
portNumber: -> {0}: 23 portArg1: ---> {0.0.0.0}: 172.16.41.0 portArg2: ---> {0.0.0.0}: 255.255.255.0 ....................S= Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Displaying port-access profile entries To display configured port-access profile entries use the list command: zSH> list port-access port-access 1 1 entry found.
Modifying port-access profile entries To modify a configured port-access profile entry use the update command. The following example changes the entry’s source IP address to 172.16.40.0: zSH> update port-access 1 portNumber: -> {23} portArg1: ---> {172.16.41.0} 172.16.40.0 portArg2: ---> {255.255.255.0} 1 entry found. .................... Save new record? [s]ave, [c]hange or [q]uit: s Updated record saved.
TFTP server support By default, the MALC runs as an TFTP server enabling files stored in the root/pubs folder to be downloaded to other devices with connectivity to the MALC. The following example downloads the file file.bin from a MALC with the IP address 172.24.15.19. image download 172.24.15.19 /pub/file.bin file.bin
SFP presence and status The MALC FE/GE and GE uplink cards and the MALC Active Ethernet line card utilize Small Form Factor Pluggable (SFP) optics. If you need to verify the status of an SFP on an Ethernet port, use the sfp show command. This command also displays parameters of existing SFPs for diagnostics. To check for Ethernet interfaces on the MALC, enter list ether: zSH> list ether ether 1-1-1-0/eth ether 1-1-2-0/eth ether 1-1-3-0/eth
98
MALC Configuration Guide
System administration
3 entries found.
To view SFP parameters on an particular interface, enter sfp show interface/ type: zSH> sfp show 1-3-1-0/eth SFP Data for interface 1-3-1-0/eth vendorName vendorOui vendorPartNumber vendorRevisionLevel serialNumber manufacturingDateCode complianceCode connectorType transceiverType extendedIdentifier encodingAlgorithm channelLinkLength channelTransmitterTechnology channelTransmitterMedia channelSpeed nineTo125mmFiberLinkLengthKm nineTo125mmFiberLinkLength100m fiftyTo125mmFiberLinkLength10m sixtyTwoDot5To125mmFiberLinkLength10m nominalBitRate upperBitRateMarginPercentage lowerBitRateMarginPercentage copperLinkLength
FINISAR CORP. 00-90-65 FCLF-8521-3 A PD5371U 080131 base1000T (0x10000000) 0 sfp (3) 4 eightb10b (1) unknown value (0x0000) unknown value (0x0000) unknown value (0x0000) unknown value (0x0000) 0 0 0 0 12 0 0 100
To see if any SFPs are present on a MALC, enter the sfp show all: zSH> sfp show all SFP Data for interface 1-1-3-0/eth vendorName vendorOui vendorPartNumber vendorRevisionLevel serialNumber manufacturingDateCode complianceCode connectorType transceiverType extendedIdentifier encodingAlgorithm channelLinkLength channelTransmitterTechnology channelTransmitterMedia channelSpeed nineTo125mmFiberLinkLengthKm nineTo125mmFiberLinkLength100m fiftyTo125mmFiberLinkLength10m sixtyTwoDot5To125mmFiberLinkLength10m
FINISAR CORP. 00-90-65 FCMJ-8521-3 4 P9S0MKS 060705 base1000T (0x10000000) 0 sfp (3) 4 eightb10b (1) unknown value (0x0000) unknown value (0x0000) unknown value (0x0000) unknown value (0x0000) 0 0 0 0
MALC Configuration Guide
99
Diagnostics and Administration
nominalBitRate upperBitRateMarginPercentage lowerBitRateMarginPercentage copperLinkLength
12 0 0 100
SFP Data for interface 1-2-3-0/eth vendorName vendorOui vendorPartNumber vendorRevisionLevel serialNumber manufacturingDateCode complianceCode connectorType transceiverType extendedIdentifier encodingAlgorithm channelLinkLength channelTransmitterTechnology channelTransmitterMedia channelSpeed nineTo125mmFiberLinkLengthKm nineTo125mmFiberLinkLength100m fiftyTo125mmFiberLinkLength10m sixtyTwoDot5To125mmFiberLinkLength10m nominalBitRate upperBitRateMarginPercentage lowerBitRateMarginPercentage copperLinkLength
FINISAR CORP. 00-90-65 FCMJ-8521-3 4 P961A44 060305 base1000T (0x10000000) 0 sfp (3) 4 eightb10b (1) unknown value (0x0000) unknown value (0x0000) unknown value (0x0000) unknown value (0x0000) 0 0 0 0 12 0 0 100
Redundant Uplink cards The MALC supports Uplink card redundancy, in which two Uplink cards are installed in the system, one primary and one standby. The card installed in the lower slot becomes the primary card, and shares configuration information with the standby card. If the primary card goes down, the standby card takes over. After install an Uplink card in the MALC chassis, you can add a redundant Uplink by installing a card of the same type and creating a new card-profile for it. Caution: 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.
100
MALC Configuration Guide
System administration
The following table describes the parameters in the card-profile used to configure Uplink cards: Parameter
Description
card-group-id
The unique redundancy group to which the card is assigned. A card group can contain at most two cards and redundant card pairs must be in the same card group. Note that you cannot change a non-zero card-group-id. The card-profile must be deleted and reprovisioned. Values: 0 to 65535 Default: 1 (for Uplink cards) 2 (for MTAC/Ring cards) 0 (for non-redundant cards)
weight
A weight given to this card that determines whether this card should become the active card after both cards are reset. Cards in a card group negotiate which cards are active and standby by comparing weights. Cards with higher preferences become active. If multiple cards have the same weight, the card in the lower numbered slot becomes active. Values: noPreference No preference. neveractive The card never becomes active. slightpreference mediumpreference highpreference Default: noPreference
MALC Configuration Guide
101
Diagnostics and Administration
Parameter
Description
card-line-type
Specifies the line type of the card and the signaling that runs over it. Does not apply to OC3C/STM1 Uplink cards or OC12/S4/GE/TDM Uplink cards (for these cards, enter any value): Values: e1 E1 UNI mode (T1/E1 IMA Uplink card) ds1 DS1 UNI mode (T1/E1 IMA Uplink card) e1-ima E1 ATM IMA mode (T1/E1 IMA Uplink card) ds1-ima DS1 ATM IMA mode (T1/E1 IMA Uplink card) e3 E3 UNI mode (DS3/E3 Uplink card) ds3 DS3 UNI mode (DS3/E3 IMA Uplink card) t1-uni-gr303 T1 UNI mode of ATM and GR-303 TDM signaling (T1/E1 TDM Uplink card) t1-ima-gr303 T1 IMA mode of ATM and GR-303 TDM signaling (T1/E1 TDM Uplink card) t1-uni-v52 T1 UNI mode of ATM and V5.2 TDM signaling (T1/E1 TDM Uplink card) t1-ima-v52 T1 IMA mode of ATM and V5.2 TDM signaling (T1/E1 TDM Uplink card)
102
MALC Configuration Guide
System administration
Parameter
Description
card-atmconfiguration
Specifies the percentage of the uplink interfaces assigned to particular ATM service categories. Values: vbnrt95rt5 Specifies the following allocation:
• UBR: 1% • nrt-VBR: 94% • CBR/rt-VBR: 5% vbnrt80rt15 Specifies the following allocation:
• UBR: 5% • nrt-VBR: 80% • CBR/rt-VBR: 15% vbnrt65rt30 Specifies the following allocation:
• UBR: 5% • nrt-VBR: 65% • CBR/rt-VBR: 30% vbnrt50rt45 Specifies the following allocation:
• UBR: 5% • nrt-VBR: 50% • CBR/rt-VBR: 45% vbnrt35rt60 Specifies the following allocation:
• UBR: 5% • nrt-VBR: 35% • CBR/rt-VBR: 60% vbnrt20rt75 Specifies the following allocation:
• UBR: 5% • nrt-VBR: 20% • CBR/rt-VBR: 75% vbnrt5rt95 Specifies the following allocation:
• UBR: 1% • nrt-VBR: 5% • CBR/rt-VBR: 94%
MALC Configuration Guide
103
Diagnostics and Administration
Uplink cards on the MALC have the following types and software images. Refer to the MALC Release Notes for the complete list of support uplink cards: Table 6: MALC Uplink card types Card
Type
Name of software image
MALC-UPLINK-2-GE
5041
malcrprgige.bin malcrprgigeraw.bin (Boot partition image file)
MALC-UPLINK-2-GE-ONLY
5066
malcrprgigent.bin malcrprgigentraw.bin (Boot partition image file)
MALC-UPLINK-2-FE/GE-TDM
5090
malcUpFeGeRprTdm.bin malcUpFeGeRprTdmraw.bin (Boot partition image file)
MALC-UPLINK-2-FE/GE
5091
malcUpFeGeRpr.bin malcUpFeGeRprraw.bin (Boot partition image file)
MALC-UPLINK-DS3/E3-ATM/ IP CARD
5109
MALC-UPLINK-OC3C/ STM1-ATM/IP
5111
MALC-UP-T1/E1-ATM/TDM/ IP-16
5114
malcds3f.bin malcds3fraw.bin (Boot partition image file) malcoc3f.bin malcoc3fraw.bin (Boot partition image file) malct1e1tdmf.bin malct1e1tdmfraw.bin (Boot partition image file)
Configuring redundant Uplink cards Caution: You must configure redundant physical interfaces on both the active and standby cards. This applies to all Uplink cards. In addition, you must manually keep the configuration of the physical interfaces on the active and standby cards in sync. Note: When configuring the redundant Uplink card, the settings in the card-profile for the both cards must be identical. To add a redundant Uplink card to the system:
104
MALC Configuration Guide
1
Verify that active card has been configured with the same card-group-id that is to be used for the standby card.
2
Install a second Uplink card in slot 2.
System administration
3
Create a card-profile for the second Uplink card: To configure the card-profile for a standby DS3/E3 Uplink card:
zSH> card add 1/2/5009 linetype ds3 | e3
or zSH> new card-profile 1/2/5009 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {}: malcds3.bin or malcds3f.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {1}: enter the same redundancy group ID as the primary Uplink card hold-active: ----------> {false}: weight: ---------------> {nopreference}: assign a weight, if desired card-line-type: -------> {unknowntype}: ds3 | e3 card-atm-configuration: -> {notapplicable} .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
To configure the card-profile for a protection OC3C/STM1 Uplink card: zSH> card add 1/2/5011 linetype ds1 | e1
or zSH> new card-profile 1/2/5011 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {}: malcoc3.bin or malcoc3f.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {1}: enter the same redundancy group ID as the working Uplink card hold-active: ----------> {false}: weight: ---------------> {nopreference}: assign a weight, if desired card-line-type: -------> {unknowntype}: ds1 | e1 card-atm-configuration: -> {notapplicable} .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
To configure the card-profile for a protection OC12/STM4 Uplink card: zSH> card add 1/2/5029 linetype ds1
MALC Configuration Guide
105
Diagnostics and Administration
or zSH> new card-profile 1/2/5029 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {}: malcoc12.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {1}: enter the same redundancy group ID as the working Uplink card hold-active: ----------> {false}: weight: ---------------> {nopreference}: assign a weight, if desired card-line-type: -------> {unknowntype}: ds1 card-atm-configuration: -> {notapplicable} .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
To configure the card-profile for a standby T1/E1 IMA Uplink card: zSH> card add 1/2/5001 linetype e1 |ds1 | e1-ima | ds1-ima
or zSH> new card-profile 1/2/5001 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {}: malct1ima.bin or malct1imaf.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {1}: enter the same redundancy group ID as the primary Uplink card hold-active: ----------> {false}: weight: ---------------> {nopreference}: assign a weight, if desired card-line-type: -------> {unknowntype}: e1 | ds1 | e1-ima | ds1-ima card-atm-configuration: -> {notapplicable} .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
To configure the card-profile for a standby T1/E1 TDM Uplink card: zSH> card add 1/2/5114
or zSH> new card-profile 1/2/5114 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {}: malcT1E1Tdmf.bin
106
MALC Configuration Guide
System administration
admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {1}: enter the same redundancy group ID as the primary Uplink card hold-active: ----------> {false}: weight: ---------------> {nopreference}: assign a weight, if desired card-line-type: -------> {unknowntype}: card-atm-configuration: -> {notapplicable} .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Once the card-profile has been saved, the standby card comes up and the configuration and routing tables from the primary card are copied over. A Standby Ready trap is generated when the standby card is ready for service.
Verifying redundancy status The showactivecards and showredundancy commands display information about MALC redundancy. The showredundancy command displays the status of the Uplink card redundancy. A option for detailed redundancy information is also available. zSH> showredundancy Redundancy status for card 01:01 - Safe, all services have redundant peers 01:01 is active storage 01:02 is standby storage zSH> showredundancy -d Redundancy status for card 01:01 Taskname Active Addr ======== =========== RdsServer 01:01:03 InfoServer 01:01:02 zCardRed 01:01:26 tMAXTask 01:01:1036 trapSrv 01:01:25 tShelfRR 01:01:1035 NpRedSrv 01:01:58 LogServer 01:01:08 tFTD 01:01:67 tNumSrv 01:01:1030 DhcpServerTask 01:01:1033 filterupdate 01:01:1031 ifcfgtask 01:01:1038 Ccrr-1/1 01:01:64 MPRR-1/1 01:01:1044 CTRR-1/1 01:01:1045
Standby Addr ============ 01:02:03 01:02:02 01:02:26 01:02:1036 01:02:25 01:02:1035 01:02:58 01:02:08 01:02:67 01:02:1030 01:02:1033 01:02:1031 01:02:1038 01:02:64 01:02:1044 01:02:1045
Stdby Ready? ============ Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
MALC Configuration Guide
107
Diagnostics and Administration
VoiceCallSup 01:01:1046 01:02:1046 L-RR-1/1 01:01:1041 01:02:1041 TadSrvTask 01:01:1039 01:02:1039 tRprRP 01:01:63 01:02:63 tDS1RP 01:01:1061 01:02:1062 _RedSpawnSvrTask 01:01:1050 01:02:1050 connmgr 01:01:16 01:02:16 Safe, all services have redundant peers 01:01 is active storage 01:02 is standby storage
Yes Yes Yes Yes Yes Yes Yes
The showactivecards command displays the active cards for all redundancy groups on the system: zSH> showactivecards Shelf/Slot Group Id Card Type __________________________________ 2: 1/1 1 MALC DS3
Dual, non-redundant Uplink cards The MALC chassis can include two non-redundant DS3/E3 or OC3C/ STM1 Uplink cards. In this configuration, only cell relay is supported and there is no Uplink card redundancy.
Configuring non-redundant Uplink cards Caution: Changing to non-redundant Uplinks requires you to erase the system configuration and should only be done during a maintenance window. This procedure requires serial port access to the MALC. By default, two Uplink cards of the same type in the same chassis are part of a redundancy group. Converting these cards to non-redundant requires that you reassign these cards to the redundancy group 0 (which means they are not redundant). To add non-redundant Uplinks: 1
Back up the configuration. To back up the configuration to the network: a
Create the file in the destination location of the TFTP server and make it writable.
b
Save the configuration using the dump command. The following example saves the configuration to a file named malc.cfg on the host 192.168.8.21: zSH> dump network 192.168.8.21 malc.cfg
2
Erase the configuration: zSH> set2default
3
108
MALC Configuration Guide
Wait for the uplink card in slot 1 to reach the running state.
System administration
4
List the if-translate profiles. Note that the if-translate profile addresses are in the form uplink1/type for port 1 and uplink2/type for port 2, and so on. For example: zSH> list if-translate if-translate 1-1-1-0/ethernetcsmacd if-translate ethernet1/other if-translate 1-1-1-0/rs232 if-translate 1-1-1-0/sonet if-translate 1-1-2-0/sonet if-translate uplink1/other if-translate uplink2/other if-translate 1-1-1-0/propvirtual if-translate 1-1-1-0-propvirtual/other if-translate uplink1/atm if-translate uplink1/aal5 if-translate uplink1/rfc1483 if-translate uplink2/atm if-translate uplink2/aal5 if-translate uplink2/rfc1483 if-translate 1-1-1-0-propvirtual/atm if-translate 1-1-1-0-propvirtual/aal5 if-translate 1-1-1-0-propvirtual/rfc1483 18 entries found.
5
Update the card profile for slot 1 and set the card-group-id to 0. The following example uses an OC3C/STM1 ATM/IP card: zSH> update card-profile 1/1/5111 Please provide the following: [q]uit. sw-file-name: -----------> {malcoc3f.bin}: admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {true}: sw-upgrade-enable: ------> {false}: card-group-id: ----------> {1}: 0 hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {ds1}: ** read-only ** card-atm-configuration: -> {vbnrt65rt30}: .................... Save changes? [s]ave, [c]hange or [q]uit: s card redundancy group ID change to 0 This will cause the removal of all associated profilesand a slotreboot to create new if-translate profilesbased on "uplinkx-y" names. Continue? [y]es or [n]o: y Record updated.
The system removes the profiles for the card and then reboots the card.
MALC Configuration Guide
109
Diagnostics and Administration
6
Wait for the Uplink card in slot 1 to reach the RUNNING state.
7
List the if-translate profiles. Note that for a single Uplink card, the if-translate profiles addresses are in the form uplink1-1/type for port 1 and uplink1-2/type for port 2, and so on. For example: zSH> list if-translate if-translate 1-1-1-0/ethernetcsmacd if-translate ethernet1-1/other if-translate 1-1-1-0/rs232 if-translate 1-1-1-0/sonet if-translate 1-1-2-0/sonet if-translate uplink1-1/other if-translate uplink1-2/other if-translate 1-1-1-0/propvirtual if-translate 1-1-1-0-propvirtual/other if-translate uplink1-1/atm if-translate uplink1-1/aal5 if-translate uplink1-1/rfc1483 if-translate uplink1-2/atm if-translate uplink1-2/aal5 if-translate uplink1-2/rfc1483 if-translate 1-1-1-0-propvirtual/atm if-translate 1-1-1-0-propvirtual/aal5 if-translate 1-1-1-0-propvirtual/rfc1483 18 entries found.
8
Create a card-profile for slot 2, using 0 for the card-group-id.
zSH> card add 1/2/5111 linetype ds1 | e1
or zSH> new card-profile 1/2/5111 Please provide the following: [q]uit. sw-file-name: ---------> {}: malcoc3f.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {1}: 0 hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: ds1 | e1 enter line type of DS1 interface card-atm-configuration: -> {notapplicable} .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
9
110
MALC Configuration Guide
Wait for the Uplink card in slot 2 to reach the RUNNING state.
System administration
10 List the if-translate profiles. Note that the if-translate profiles addresses are now in the form uplink1-x/type for the Uplink card in slot 1 and uplink2-x/type for the Uplink card in slot 2, and so on. For example: zSH> list if-translate if-translate 1-1-1-0/ethernetcsmacd if-translate ethernet1-1/other if-translate 1-1-1-0/rs232 if-translate 1-1-1-0/sonet if-translate 1-1-2-0/sonet if-translate uplink1-1/other if-translate uplink1-2/other if-translate 1-1-1-0/propvirtual if-translate 1-1-1-0-propvirtual/other if-translate uplink1-1/atm if-translate uplink1-1/aal5 if-translate uplink1-1/rfc1483 if-translate uplink1-2/atm if-translate uplink1-2/aal5 if-translate uplink1-2/rfc1483 if-translate 1-1-1-0-propvirtual/atm if-translate 1-1-1-0-propvirtual/aal5 if-translate 1-1-1-0-propvirtual/rfc1483 if-translate 1-2-1-0/ethernetcsmacd if-translate ethernet2-1/other if-translate 1-2-1-0/rs232 if-translate 1-2-1-0/sonet if-translate 1-2-2-0/sonet if-translate uplink2-1/other if-translate uplink2-2/other if-translate 1-2-1-0/propvirtual if-translate 1-2-1-0-propvirtual/other if-translate uplink2-1/atm if-translate uplink2-1/aal5 if-translate uplink2-1/rfc1483 if-translate uplink2-2/atm if-translate uplink2-2/aal5 if-translate uplink2-2/rfc1483 if-translate 1-2-1-0-propvirtual/atm if-translate 1-2-1-0-propvirtual/aal5 if-translate 1-2-1-0-propvirtual/rfc1483 36 entries found.
Managing the MALC over a non-redundant Uplink In a dual, non-redundant configuration, the system is managed over only one of the Uplink cards a time. The first card active in the system (by default, the card in the first slot) contains the management channel. To maintain a management connection to the device, you should provision a management channel on both Uplink cards. In this case, if the Uplink card that is managing the MALC reboots, the other Uplink card takes over management of the system. The management channel can either be over the
MALC Configuration Guide
111
Diagnostics and Administration
Ethernet or an ATM PVC. In either case, the IP addresses for each of the Uplink cards must be on different subnets.
112
MALC Configuration Guide
SNMP
SNMP This section describes the following:
•
Creating SNMP community names and access lists, page 113
•
Configuring traps, page 114
Creating SNMP community names and access lists Note: By default, the MALC has a single SNMP community defined with the name ZhonePrivate. This community has admin access to the system. Zhone recommends that you configure community names and access lists to prevent unauthorized access to the system. The community-profile specifies the community name and an access level for SNMP manager to access the system. It can also optionally specify a community-access-profile which is used to verify the source IP address of the SNMP manager. The system supports up to 50 different access lists. The following community access levels are supported:
•
noaccess—the community has no access.
•
read—the community has read-only access to the system, with the exception of information in the community-profile and community-access-profile.
•
readandwrite—the community has read/write access to the system, with the exception of information in the community-profile and community-access-profile.
•
admin—the community has read and write access to the entire system, including information in the community-profile and community-access-profile. Note that the ZMS requires admin access to manage the system.
Creating a community profile Note: Configuring a community profile disables the ZhonePrivate default community name. If you do change the community name, you must change the name in ZMS or the device will become unmangeable. The following example defines a community name public with read-only privileges: zSH> new community-profile 1 Please provide the following: [q]uit. community-name: -----> {}: public permissions: --------> {read}: access-table-index: -> {0}:
MALC Configuration Guide
113
Diagnostics and Administration
.................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Creating community access lists The following example defines a community name private with read/write privileges and also creates an access list to verify that the SNMP managers attempting to access the MALC are coming from known IP addresses 192.168.9.10 and 192.168.11.12: First, create an access list for the first IP address: zSH> new community-access-profile 2 Please provide the following: [q]uit. access-table-index: -> {0}: 1 ip-address: ---------> {0.0.0.0}: 192.168.9.10 .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Then, create an access list for the second IP address with the same access-table-index (1): zSH> new community-access-profile 3 Please provide the following: [q]uit. access-table-index: -> {0}: 1 ip-address: ---------> {0.0.0.0}: 192.168.11.12 .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Finally, create a community-profile that specifies the community name, and uses the same access-table-index (1) as defined in the two community-access-profiles you just created: zSH> new community-profile 4 Please provide the following: [q]uit. community-name: -----> {}: private ZMS must include this name permissions: --------> {read}: readandwrite access-table-index: -> {0}: 1 .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Configuring traps The trap-destination profile defines a trap recipient the MALC will send traps to. To configure a trap destination you need to know:
114
MALC Configuration Guide
•
the IP address of the SNMP manager workstation
•
the community name the trap recipient expects
Statistics and alarms
Note that the resendseqno and ackedseqno parameters are set by the ZMS. The other parameters in the trap-destination profile can be left at their default values. The following example configures a trap recipient with the IP address 192.168.3.21: zSH> new trap-destination 32 Please provide the following: [q]uit. trapdestination: -> {0.0.0.0}: 192.168.3.21 communityname: ---> {}: public resendseqno: -----> {0}: ackedseqno: ------> {0}: traplevel: -------> {low}: traptype: --------> {(null)}: 0 trapadminstatus: -> {enabled}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Statistics and alarms This section describes the following:
•
Bulk statistics on page 115
•
T1/E1 Statistics on page 121
•
Alarm manager on page 124
•
Alarm suppression on page 133
•
ADSL low power alarm on page 132
Bulk statistics The MALC can be configured to collect statistics and transfer them to an FTP server. Any supported SNMP OID can be collected. 1. Every 15 minutes, the MALC gathers the specified statistics. If a statistic is not collected, the MALC sends a ZhoneBulkStatisticsIndividualStatFailure trap to the designated trap recipient. 2. The statistics files are stored on the local flash card with the following filename: Device-IP_timestamp where timestamp is in the form YYYY.DD.MM.HH.MM in the device local time. For example:192.168.80.291_2002.11.06.14.37 3. The MALC compresses the files and attempts to send them to the FTP server.
MALC Configuration Guide
115
Diagnostics and Administration
–
If the files transfer is successful, the files on the local flash card are deleted.
–
If the file transfer is not successful, the MALC will:
a. Send a ZhoneBulkStatisticsIntervalFailure trap to the designated trap recipient. b. Periodically attempt to reach the FTP server. c. Continue to collect statistics every 15 minutes, writing a new statistics file to the flash card for every interval, if there is sufficient space on the flash disk. d. When the FTP server is available, the MALC transfers all remaining files to the FTP server and deletes them from the flash card.
Bulk statistics file format If the statistics collected include children, the bulk statistic file uses the following format: #Version# #SysObjectOID #BeginCollectionRecord* 1=value1 2=value2 ... ... ... n=valuen #EndCollectionRecord #EndFile
where value1, value2, and so on are the SNMP instances for the OID. If the statistics collected does not include children, the bulk statistic file uses the following format: #Version# #SysObjectOID #BeginCollectionRecord* #EndCollectionRecord #EndFile
For example, if you set up the system collect statistics for an ATM VCL with an Ifindex of 123 and a VPI/VCI of 0/36 and include the child objects, the statistic file would look similar to the following: #VersionNumber# #Device 1.3.6.1.4.1.5504.4.2.2.5.1 #BeginCollectionRecord 1000 ZhoneAtmStatsExtEntry 123.0.36 1=135
116
MALC Configuration Guide
Statistics and alarms
2=15 3=8309 4=83209 5=23 6=787 7=843 8=38209 #EndCollectionRecord #EndFile
Where values 1 to 8 are the ZhoneAtmStatsExtEntry entries: zhoneAtmStatsTotalInitialCellsRx zhoneAtmStatsTotalFabricCellsRx zhoneAtmStatsTotalFinalCLP0CellsRx zhoneAtmStatsTotalFinalCLP1CellsRx zhoneAtmStatsTotalInitalCellsTx zhoneAtmStatsTotalFabricCellsTx zhoneAtmStatsTotalFinalCLP0CellsTx zhoneAtmStatsTotalFinalCLP1CellsTx
Configuring bulk statistics Note: You must configure the FTP password used by bulk statistics using ZMS or the Zhone genSystem MIB. To configure bulk statistics: 1
Create a bulk-statistic record for the statistics you want to gather. For example, to collect ATM VCL statistics: zSH> new bulk-statistic 1 Please provide the following: [q]uit. enabled: ----------> {true}: oid: --------------> {}: ZhoneAtmStatsExtEntry instance: ---------> {}: 136 ifIndex of ATM interface include-children: -> {false}: true .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
2
Update the bulk-statistics-config 0 profile to specify the FTP server information:
zSH> update bulk-statistics-config 0 Please provide the following: [q]uit. bulk-statistics-enabled: -> {false}: true ftp-server-address: ------> {0.0.0.0}: 192.168.8.100 ftp-login: ---------------> {}: zhoneuser ftp-password: ------------> {**private**}:**read-only** must be configured using SNMP or ZMS
MALC Configuration Guide
117
Diagnostics and Administration
ftp-directory-path: ------> {}: /stats .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Bulk statistics example This example explains how to configure bulk statistics to gather the following SNMP statistics: ZhoneAtmStatsExtEntry object in the comAtm MIB: 1: zhoneAtmStatsTotalInitialCellsRx 2: zhoneAtmStatsTotalFabricCellsRx 3: zhoneAtmStatsTotalFinalCLP0CellsRx 4: zhoneAtmStatsTotalFinalCLP1CellsRx 5: zhoneAtmStatsTotalInitalCellsTx 6: zhoneAtmStatsTotalFabricCellsTx 7: zhoneAtmStatsTotalFinalCLP0CellsTx 8: zhoneAtmStatsTotalFinalCLP1CellsTx zhoneDslPerfDataTotalEntry in the phyDsl MIB: 1: zhoneDslPerfTotalLofs 2: zhoneDslPerfTotalLoss 3: zhoneDslPerfTotalLols 4: zhoneDslPerfTotalInits 5: zhoneDslPerfTotalES 6: zhoneDslPerfTotalSES 7: zhoneDslPerfTotalCRCAnomalies 8: zhoneDslPerfTotalLOSWS 9: zhoneDslPerfTotalUAS To get these statistics: 1
Get the ifIndex for the trunking interface: zSH> ifxlate 1-1-1-0-sonet/atm ifIndex: ----------> {8} shelf: ------------> {1} slot: -------------> {2} port: -------------> {1} subport: ----------> {0} type: -------------> {sonet} adminstatus: ------> {up} physical-flag: ----> {true} iftype-extension: -> {none}
118
MALC Configuration Guide
Statistics and alarms
ifName: ----------->
2
{1-1-1-0}
Get the ifIndex for the subscriber interface: zSH> ifxlate 1-7-1-0/adsl ifIndex: ----------> {136} shelf: ------------> {1} slot: -------------> {7} port: -------------> {1} subport: ----------> {0} type: -------------> {adsl} adminstatus: ------> {up} physical-flag: ----> {true} iftype-extension: -> {none} ifName: -----------> {1-7-1-0}
3
Update the bulk-statistics-config profile to specify the FTP server:
zSH> update bulk-statistics-config 0 Please provide the following: [q]uit. bulk-statistics-enabled: -> {false}: true ftp-server-address: ------> {0.0.0.0}: 192.168.80.201 ftp-login: ---------------> {}: username ftp-password: ------------> {** private **}: ** read-only ** ftp-directory-path: ------> {}: stats .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
4
Modify the zhoneBulkStatsSystemFtpPassword object in the genSystem MIB to change the FTP password.
5
Create a bulk-statistic profile for the trunking interface. Set include-children to true to gather all the child statistics for this object: zSH> new bulk-statistic 1 Please provide the following: [q]uit. enabled: ----------> {true}: oid: --------------> {}: zhoneAtmStatsExtEntry instance: ---------> {}: 1635 ifIndex of the ATM interface include-children: -> {false}: true .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
6
Create a bulk-statistic profile for the subscriber interface. Set include-children to true to gather all the child statistics for this object: zSH> new bulk-statistic 2 Please provide the following: [q]uit. enabled: ----------> {true}: oid: --------------> {}: zhoneDslPerfDataTotalEntry instance: ---------> {}: 136 ifIndex of DSL interface include-children: -> {false}: true ....................
MALC Configuration Guide
119
Diagnostics and Administration
Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
IF-Name in bulk stats (32 character limit) The MALC supports customized interface names using up to 32 characters. The customized name appears in bulk statistics and other output displaying interface names. To customize an interface name, update the ifName parameter in the if-translate profile for the interface. zSH> update if-translate 1-1-1-0/eth if-translate 1-1-1-0/eth Please provide the following: [q]uit. ifIndex: -----------> {1}: shelf: -------------> {1}: slot: --------------> {1}: port: --------------> {1}: subport: -----------> {0}: type: --------------> {eth}: adminstatus: -------> {up}: physical-flag: -----> {true}: iftype-extension: --> {none}: ifName: ------------> {1-1-1-0}:[interfacename upto 32 characters] redundancy-param1: -> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Example bulk statistics with 1-1-1-0/eth interface name. 1.0 1.3.6.1.4.1.5504.1.6.2 #BeginCollectionRecord 1 15 ifHCOutUcastPkts 1(1-1-1-0/eth)=0,29154 #EndCollectionRecord #BeginCollectionRecord 2 15 ifHCInUcastPkts 1(1-1-1-0/eth)=0,23837 #EndCollectionRecord #BeginCollectionRecord 3 15 ifHCInOctets 1(1-1-1-0/eth)=0,2814554 #EndCollectionRecord
120
MALC Configuration Guide
Statistics and alarms
T1/E1 Statistics The ds1stats command displays statistics for any DS1 ports on the MALC. The industry standard statistics provided by the ds1stats command may be used to see how cleanly signals are being transmitted down the line, whether incoming packets are properly framed or may be used to identify trends on the performance of the signal lines. The DS1 statistics follow the standards set in RFC 1406. For more information, please see RFC 1406, Definitions of Managed Objects for DS1 and E1 Interface Types. Table 7: DS1stat Display Fields Field
Acronym
Description
INT
Interval
Intervals are 900 second (15 minute) buckets. You can gather up to 96 intervals (24 hours) of history.
PCV
Path Coding Violations
Frame synchonization errors in D4 and E1- no CRC formats; May also be a CRC error in ESF and E1 - CRC formats.
LCV
Line Code Violations
An LCV is the occurance of a Bipolar Violation (BPV) or Excessive Zeroes (EXZ) error event). A BPV error event occurs when two pulses of the same polarity occur without the opposite polarity occuring. With T1 pulses (represents ONE, no pulse represents ZERO) alternate polarity. If two pulses of the same polarity are received in succession, either bits were added or deleted from the signal. EXZ = If too many zeros (no pulse) are received in succession, this event can cause receiving equipment to lose synchornization with the sending equipment.
LES
Line Errored Seconds
The number of Line Errored Seconds (when one or more LCV violation events are detected in a second.
CSS
Controlled Slip Seconds
Controlled slip seconds when at least one controlled slip occurs. A controlled slip is when the detected error is in deletion or replication of a frame.
MALC Configuration Guide
121
Diagnostics and Administration
Table 7: DS1stat Display Fields Field
Acronym
Description
ES
Errored Seconds
An Errored Second has one or more Path Code Violation, one or more Out of Frame defects, one or more Controlled Slip events, or a detected Alarm Indication Signal (AIS) defect. AIS defects are sent to the receiver when a transmission interruption is detected from the device transmitting the signal or a device upstream which sends the signal which may be forwarded.
BES
Bursty Errored Seconds
The number of Bursty Error Seconds with 2 to 319 PCV error events, but no severely error frame defects and no detected incoming AIS defects.
SES
Severely Errored Seconds
A Severely Errored Second is a second with 320 or more Path Code Violation Error Events OR one or more Out of Frame (OOF) defects OR a detected AIS defects. Transmission performance is significantly degraded. For T1 links, an Out of Frame defect is declared when the receiver detects two or more framing errors within a 3 msec period for ESF signals and 0.75 msec for D4 signals, or two or more errors out of five or fewer consecutive framing-bits. For E1 links, an Out Of Frame defect is declared when three consecutive frame alignment signals have been received with an error.
122
MALC Configuration Guide
SEFS
Severely Errored Framing Seconds
SEFS are seconds with one or more Out of Frame defects or a detected AIS defect.
DM
Degraded Minutes
Degraded minutes are a range of errors per minute. Degraded Minutes are when the estimated error rate exceeds 1E-6 per minute, but does not exceed 1E-3 errors per minute.
UAS
Unavailable Seconds
The DS1 interface is considered unavailable when 10 contiguous SESs occur OR the onset of a failure condition (see RFC 1406 for a list of failure states).
Statistics and alarms
Example You identify the card and port using Zhone’s standard shelf-slot-card-port/ interface descriptor naming scheme. zSH> ds1stat 1-1-9-0/ds1examplecard Line Information: ----------------Alarm Status......................1 ->No Alarm Line Type..................E1CRC Ds1 Mode..........................Other Signal Type.......................Loop start Time Elapsed..................502 LineStatusLastChange..............627249 Transmit Clock Source.............Loop Timing Loopback Status................1 ->No Loopback **************** Pmon Statistics of Line 12 **************** INT PCV LCV LES CSS ES BES SES SEFS DM UAS ---------------------------------------------------------------Near-End Current Interval Stats: ----------------------------------0 0 0 40 40
0
0
0
Near-End Interval Stats: -----------------------Retrieving data in progress ...Done. 1 0 0 0 64 64 0 2 0 0 0 66 66 0 3 0 0 0 65 65 0 4 0 0 0 74 74 0 5 0 0 0 73 73 0 6 0 0 0 70 70 0 7 0 0 0 68 68 0 8 0 0 0 71 71 0 9 0 0 0 64 64 0 10 9330 0 0 113 623 592 11 10047 0 0 116 648 621 12 5274 1 1 97 378 330
0 0 0 0 0 0 0 0 0 0 0 1
0 0 0 0 0 0 0 0 0 0 0 1
0 0 0 0 0 0 0 0 0 13 13 8
0 0 0 0 0 0 0 0 0 0 0 107
Near-End Total Stats: ---------------------24651 1 1
1
1
34
107
941
************************
2264 End
0
1543
0
************************
In the example you can see that the Controlled Slip Seconds level is raised above zero. Since the interval is in 15 minute increments the range around 60 shows that there is a CSS error, either a deletion or replication of a frame about every 15 seconds. This level most likely means that the signal the T1 card is receiving from a network server is out of synch with the MALC’s
MALC Configuration Guide
123
Diagnostics and Administration
clock. The CSS errors are driving the Errored Seconds which is why they are the same. In the 15 minute buckets for intervals 10, 11, and 12 we introduced errors in the system to provide an example of what to look for when their is noise on the line. These heightened numbers show that there are loss of signal problems such as noise on the line or intermittent connection problems.
Alarm manager The MALC central alarm manager includes the ability to view the active alarms on the system (using the alarm command) and the ability to store active alarms on the device. ZMS can use the alarms stored on the device to recreate the state of the alarms if it becomes disconnected. The alarm command uses the following syntax: alarm show [summary]
For example, the following command displays the number of current active alarms, the total number of alarms, the number of cleared alarms, as well as each active alarm and its severity: zSH> alarm show ************ Central Alarm Manager ActiveAlarmCurrentCount ActiveAlarmTotalCount ClearAlarmTotalCount OverflowAlarmTableCount ResourceId ---------1-5-2-0/adsl 1-5-3-0/adsl 1-5-4-0/adsl 1-5-5-0/adsl 1-5-6-0/adsl 1-5-7-0/adsl 1-5-8-0/adsl 1-5-17-0/adsl 1-5-18-0/adsl 1-5-19-0/adsl 1-5-20-0/adsl 1-5-21-0/adsl 1-5-22-0/adsl 1-5-23-0/adsl 1-5-24-0/adsl 1-2-1-0/sonet 1-2-2-0/sonet 1-2-1-0/sonet 1-2-2-0/sonet 1-2-1-0/sonet 1-2-2-0/sonet
124
MALC Configuration Guide
************ :21 :42 :21 :0
AlarmType --------linkDown linkDown linkDown linkDown linkDown linkDown linkDown linkDown linkDown linkDown linkDown linkDown linkDown linkDown linkDown linkDown linkDown sonetSectionStatusChange sonetSectionStatusChange sonetLineStatusChange sonetLineStatusChange
AlarmSeverity ------------minor minor minor minor minor minor minor minor minor minor minor minor minor minor minor critical critical major major major major
Statistics and alarms
The summary option displays the number of current active alarms, the total number of alarms, the number of cleared alarms: zSH> alarm show summary ************ Central Alarm Manager ActiveAlarmCurrentCount ActiveAlarmTotalCount ClearAlarmTotalCount OverflowAlarmTableCount
************ :3 :3 :0 :0
Supported alarms The alarms reported by the alarm show command are based on traps. When these traps are received by ZMS, they generate ZMS alarms. The following alarms are supported. Table 8: Supported alarms Alarm
Description
aal2ExternalAIS
Alarm Indication Signal associated with a maintenance alarm detected.
aal2ExternalRAI
Remote Alarm Indication detected to constitute a received signal failure.
aal2InternalAIS
Alarm Indication Signal detected affecting the AAL type 2 connection.
aal2InternalRDI
Remote Defect Indication detected affecting the AAL type 2 connection.
aal2PerfCellLossThreshTrap
A bad sequence error is detected when some cells have been lost.
aal2PerfCongestionThreshTrap
The number of congestion events exceed the congestion threshold.
aal2PvcDown
The status of AAL type 2 PVC has gone down.
adslAtucInitFailureTrap
Near end modem (ATUC) failure during initialization.
adslAtucPerfESsThreshTrap
Errored Second 15-minute interval threshold reached on near end modem (ATUC)
adslAtucPerfLofsThreshTrap
Loss of Framing 15-minute interval threshold reached on near end modem (ATUC)
adslAtucPerfLolsThreshTrap
Loss of Link 15-minute interval threshold reached on near end modem (ATUC)
adslAtucPerfLossThreshTrap
Loss of Signal 15-minute interval threshold reached on near end modem (ATUC)
MALC Configuration Guide
125
Diagnostics and Administration
Table 8: Supported alarms (Continued) Alarm
Description
adslAtucPerfLprsThreshTrap
Loss of Power 15-minute interval threshold reached on near end modem (ATUC)
adslAtucRateChangeTrap
Near end modem (ATUC) transmit rate changed from adslAtucChanPrevTxRate to adslAtucChanCurrTxRate
adslAturPerfESsThreshTrap
Errored Second 15-minute interval threshold reached on far end modem (ATUR)
adslAturPerfLofsThreshTrap
Loss of Framing 15-minute interval threshold reached on far end modem (ATUR)
adslAturPerfLossThreshTrap
Loss of Signal 15-minute interval threshold reached on far end modem (ATUR)
adslAturPerfLprsThreshTrap
Loss of Power 15-minute interval threshold reached on far end modem (ATUR)
adslAturRateChangeTrap
Far end modem (ATUR) transmit rate changed from adslAturChanPrevTxRate to adslAturChanCurrTxRate
apsEventChannelMismatch
An APS channel mismatch between the transmitted K1 channel and the received K2 channel has occurred.
apsEventFEPLF
An APS Far-End Protection-Line Failure (FEPLF) has occurred. This condition is declared based on receiving signal failure (SF) on the protection line in the K1 byte.
apsEventModeMismatch
An APS event mode mismatch has occurred. A conflict between the current local mode and the received K2 mode information constitutes a mode mismatch.
126
MALC Configuration Guide
Statistics and alarms
Table 8: Supported alarms (Continued) Alarm
Description
apsEventPSBF
An APS Protection Switch Byte Failure (PSBF) has occurred. This condition occurs when either an inconsistent APS byte or an invalid code is detected. An inconsistent APS byte occurs when no three consecutive K1 bytes of the last 12 successive frames are identical, starting with the last frame containing a previously consistent byte. An invalid code occurs when the incoming K1 byte contains an unused code or a code irrelevant for the specific switching operation (that is., Reverse Request while no switching request is outstanding) in three consecutive frames. An invalid code also occurs when the incoming K1 byte contains an invalid channel number in three consecutive frames.
apsEventSwitchover
The number of times this channel has switched to the protection line.
atmDsx3PlcpAlarmStatusChan ge
The DS3 Physical Layer Convergence Procedure (PLCP) has received an alarm.
atmInterfaceTCAlarmStateCha nge
ATM Interface TC Sublayer is currently in the Loss of Cell Delineation defect maintenance state.
atmOamF4PingStatus
Indicates whether an OAM F4 ping has succeeded or failed.
atmOamF5PingStatus
Indicates whether an OAM F5 ping has succeeded or failed.
atmVclBandwidthUnavailable
Bandwidth specified in an ATM traffic descriptor is not available. This alarm is sent when either of the following conditions occurs:
•
A VCL is activated with a traffic descriptor that specifies a higher than available rate.
•
A VCL is activated with a traffic descriptor that specifies a vcl-rate value which will cause available bandwidth to run out.
atmVclOperStatusChange
Subscriber (Id: SubscriberID, Name: SubscriberName) on Vcl (IfIndex: IfIndex, Vpi: VPI, Vci: VCI) is affected
atmVpiAutoCreateComplete
Indicates the system has completed creating VPIs. The system automatically creates VPIs for pre-existing VPLs and VCLs if the VPI/VCI ranges for a card are changed.
atmVplOperStatusChange
A VPL has changed state.
MALC Configuration Guide
127
Diagnostics and Administration
Table 8: Supported alarms (Continued)
128
MALC Configuration Guide
Alarm
Description
dhcpTrapZhoneCpeDetected
An IP address is being offered to a Zhone CPE device via DHCP.
dhcpTrapZhoneCpeSysObjectI D
The system Object ID of an attached Zhone CPE device that has obtained its address via DHCP.
dhcpTrapZhoneIpAddressUpda te
An IP address has been assigned or modified via DHCP.
coldStart
An SNMP entity on the system has reinitialized and its configuration may have changed.
dhcpTrapZhoneCpeDetected
An IP address is being offered to a Zhone CPE device
dsx3LineStatusChange
Status change for the DS3 interface.
fan_a_failure
Fan A is in a fault state.
fan_a_ok
Fan A operating normally.
fan_b_failure
Fan B is in a fault state.
fan_b_ok
Fan B operating normally.
fan_power_supply_a_failure
Fan A power supply is in a fault state.
fan_power_supply_a_ok
Fan A power supply is operating normally.
fan_power_supply_b_failure
Fan B power supply is in a fault state.
fan_power_supply_b_ok
Fan B power supply is operating normally.
fan_speed_error
There is an irregular fan speed.
fan_speed_ok
Fan speed is normal.
fan_tray_added
Fan tray added to device.
fan_tray_removed
Fan tray removed from device.
igCrvRemoteStateChange
A remote GR-303 all reference value (CRV) has changed state.
igCrvTmcStateChange
A GR-303 timeslot management channel CRV (TMC) has changed state.
igEocPrimaryStateChange
A primary GR-303 embedded operations channel (EOC) has changed state.
igEocSecondaryStateChange
A secondary GR-303 embedded operations channel (EOC) has changed state.
igOperStatusChange
A GR-303 interface group (IG) has changed state.
igSystemTimeChange
A GR-303 IG system time has changed.
Statistics and alarms
Table 8: Supported alarms (Continued) Alarm
Description
igTmcPrimaryStateChange
A primary GR-303 TMC has changed state.
igTmcSecondaryStateChange
A secondary GR-303 TMC has changed state.
isdnMibCallInformation
This trap indicates the status of a connection request. It is sent whenever:
• •
an incoming call is rejected
•
a call connects
an outgoing call attempt fails (if the call is configured for retries, this trap is sent after all retires fail)
Note that only one trap is sent for successful or unsuccessful call attempts between two neighbors; subsequent call attempts result in no trap. isdnTrapAmiViolations
Bad Ami violation.
isdnTrapFECV
Far end code violation.
isdnTrapFrameSynchLoss
Driver receives three successive out of sync frames.
isdnTrapUnbalancedFrame
The number of unbalanced ISDN frames has been exceeded.
left_outlet_temp_normal
The system is reporting a the temperature on the left outlet is within temperature specifications.
left_outlet_temp_over_limit
The system is reporting a high temperature on the left outlet.
linkDown
Communication link is about to enter the down state.
power_supply_a_failure
Power supply A is in a fault state.
power_supply_a_ok
Power supply A is operating normally.
power_supply_b_failure
Power supply B is in a fault state.
power_supply_b_ok
Power supply B is operating normally.
power_supply_c_failure
Power supply C is in a fault state.
power_supply_c_ok
Power supply C is operating normally.
power_supply_d_failure
Power supply D is in a fault state.
power_supply_d_ok
Power supply D is operating normally.
right_outlet_temp_normal
The system is reporting a the temperature on the left outlet is within temperature specifications.
MALC Configuration Guide
129
Diagnostics and Administration
Table 8: Supported alarms (Continued)
130
MALC Configuration Guide
Alarm
Description
right_outlet_temp_over_limit
The system is reporting a high temperature on the right outlet.
sechtor100FanStatusChange
The fan on a Zhone Sechtor 100 device has changed state.
sechtor100ThermoStatusChang e
The temperature sensor in a Zhone Sechtor 100 device has changed state.
shelf_controller_fault
Shelf controller fault.
sipStatusCodeNotif
Indicates a session initiation protocol (SIP) status code has been sent or received by the system.
sipStatusCodeThreshExceeded Notif
Indicates that a specific SIP status code was found to have been sent or received by the system enough to exceed the configured threshold.
sonetClockTransmitSourceCha nge
Indicates the SONET clock external recovery or clock transmit settings have been changed.This could be caused by a change to the MALC clocking configuration or a line failure.
sonetLineStatusChange
A SONET line has changed state.
sonetPathStatusChange
A SONET path has changed state.
sonetSectionStatusChange
A SONET section has changed state.
temp_normal
The temperature of the device is within specifications.
temp_over_limit
The temperature of the device is over specifications.
temp_under_limit
The temperature of the device is under specifications.
v52CChannelStatusChange
The V5.2 C channel has changed state.
v52CPathOperStatusChange
The V5.2 path has changed state.
v52IgOperStatusChange
The V5.2 IG has changed state.
v52IgPortAlignmentNotificatio n
A request has been initiated by the operator.
v52IgProvVariantRequestNotif ication
A request has been initiated from the AN side.
v52LinkBlockNotification
A V5.2 link block request has been sent.
v52LinkCheckIdNotification
A V5.2 check link ID request has been received.
Statistics and alarms
Table 8: Supported alarms (Continued) Alarm
Description
v52ProtectionCPathOperStatus Change
A V5.2 protection C path has changed state.
voiceDspChannelInterArrvJitte rTrigger
This trap is sent whenever the channelInterArrvJitter exceeds the default setting.
voiceDspChannelPktsLoss
This trap is sent whenever the channelPktsPktsLost exceeds the default setting.
voiceDspReset
Indicates a voice DSP has reset.
warmStart
An SNMP entity on the system has reinitialized and its configuration may have changed.
zapTrapZhoneBanDetected
Sent when a BAN detects a MALC or Raptor device.
zapTrapZhoneCpeConnection Down
Sent when a Zhone CPE device is disconnected.
zapTrapZhoneCpeDetected
Sent when a Zhone CPE is detected for the first time.
zapTrapZhoneMalcConnection Down
A Zhone MALC device has been disconnected.
zapTrapZhoneMalcDetected
A Zhone MALC has been detected for the first time.
zapTrapZhoneProvisioningDon e
Automatic provisioning is completed.
zhoneAdslPotsBypassRelayCh angeNotification
A DSL bypass relay has changed state. This trap is sent on a per-port basis and only applies to the MALC ADSL 32 + splitter cards.
zhoneBulkStatisticsIntervalFail ure
Bulk statistics were not successfully gathered for the current interval. This could be caused by the statistics periods overlapping (due to network congestion or too many statistics being gathered), no disk space, file write error, or an FTP error.
zhoneCardRedundancyStatusC hange
The specified card has become active.
zhoneCardServicesStatusChan ge
Card service is inactive or unavailable (slot SlotNumber)
zhoneDslLineAlarmStatusCha nge
The SDSL and SHDSL interface has changed state.
zhoneExternalAlarmTrap
External relay is open or is not connected.
MALC Configuration Guide
131
Diagnostics and Administration
Table 8: Supported alarms (Continued) Alarm
Description
zhoneImaGroupDown
IMA group has gone down.
zhoneLineStatusChange
The DS1 interface has changed stated.
zhonePingTestCompleted
A ping command has been successful.
zhoneTraceRoutePathChange
The path for a traceroute has been changed.
zhoneTraceRouteTestFailed
A traceroute command has failed.
zhoneTrapCardMemStatus
The memory on a device has changed. This could indicate RAM or flash memory is low or not available.
zhoneTrapCardStatusChange
Indicates a card state has changed. This could indicate the card was added, removed, is in a fault state, or has been reset.
zhoneTrapCardVersionCheck
Card version CardVersion (SlotNumber) is incompatible with that of active InfoServ card. (BAN only)
zhoneTrapConfigSyncChange
A partial config sync update has failed
zhoneTrapCpeConnectionDow n
Zhone CPE connection is down
zhoneTrapFlashCardStatusCha nge
Indicates the flash card in the system has changed state.
zhoneTrapShelfStatusChange
A shelf has changed state.
zhoneTrapSnmpSATimeout
The SNMP subagent on the system has timed out.
zhoneZmsBlockCliChange
At least one CLI session has been unblocked or all CLI sessions are blocked.
zrgBatteryRelayNotification
Indicates the state of onboard ZRG battery.
ADSL low power alarm When the MALC detects the ADSL card is in a low power state, it sets all the active DSL ports to admin_down state. When the low power alarm is cleared, the DSL ports are set back to admin_up state. This feature saves back-up battery power until the chassis main power recovers. To enable this feature, configure one of the alarm contacts (1 to 12) to detect low-power alarms in the num2str-profile. The num2str-profile uses an index in the form: shelf/slot/282/alarm-contact
For example:
132
MALC Configuration Guide
Statistics and alarms
zSH> update num2str-profile 1/12/282/1 Please provide the following: [q]uit. name: -> {Relay 1}: low-power .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Alarm suppression The alarm suppression feature allows alarm/LED notification and output to be disabled based on alarm severity level for existing and future alarms. When an alarm level is disabled, all existing alarms of that type are cleared from the system. Future alarms of that type do not set LEDs or alarm relays and are not displayed in alarm output. Alarm suppression is also supported in ZMS. Table 9 lists the alarm suppression options and the resulting behaviors. By default, alarms for all severity levels are enabled. Table 9: Alarm suppression options Alarm Levels Enabled Setting
Alarm Behavior
critical+major+minor+warning
Enables all alarm levels. The default setting.
critical+major+minor
Disables all warning alarms.
critical+major
Disables all minor, and warning alarms.
critical+major+warning
Disables all minor alarms.
critical+minor+warning
Disables all major alarms.
critical+minor
Disables all major and warning alarms.
critical+warning
Disables all major and warning alarms.
critical
Disables all major, minor, and warning alarms.
major
Disables all critical, minor, and warning alarms.
major+minor+warning
Disables all critical alarms.
major+minor
Disables all critical and warning alarms.
major+warning
Disables all critical and minor alarms.
minor
Disables all critical, major, and warning alarms.
minor+warning
Disables all critical and major alarms.
(no levels)
Disables all alarm levels.
This example disables alarm/LED notification and output for all current and future alarms with the severity levels minor and warning. zSH> update system 0
MALC Configuration Guide
133
Diagnostics and Administration
Please provide the following: [q]uit. syscontact: -----------> {Zhone Global Services and Support 7001 Oakport Street Oakland Ca. (877) Zhone20 (946-6320) Fax (510)777-7113
[email protected]}: sysname: --------------> {Malc-M22}: syslocation: ----------> {Oakland}: enableauthtraps: ------> {disabled}: setserialno: ----------> {0}: zmsexists: ------------> {true}: zmsconnectionstatus: --> {inactive}: zmsipaddress: ---------> {172.16.80.160}: configsyncexists: -----> {false}: configsyncoverflow: ---> {true}: configsyncpriority: ---> {high}: configsyncaction: -----> {noaction}: configsyncfilename: ---> {172.16.80.160_4_1149144921639}: configsyncstatus: -----> {synccomplete}: configsyncuser: -------> {zmsftp}: configsyncpasswd: -----> {** private **}: ** read-only ** numshelves: -----------> {1}: shelvesarray: ---------> {}: numcards: -------------> {3}: ipaddress: ------------> {172.16.80.160}: alternateipaddress: ---> {0.0.0.0}: countryregion: --------> {us}: primaryclocksource: ---> {0/0/0/0/0}: ringsource: -----------> {internalringsourcelabel}: revertiveclocksource: -> {true}: voicebandwidthcheck: --> {false}: alarm-levels-enabled: -> {critical+major+minor+warning}: critical+major .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated. zSH>
Logging This section explains how to use logging on the MALC. It includes:
134
MALC Configuration Guide
•
Overview on page 136
•
Enabling/disabling logging on page 136
•
Log message format on page 136
•
Modifying logging levels on page 138
•
Using the log cache on page 139
•
Sending messages to a syslog server on page 141
•
Specifying different log formats for system and syslog messages on page 142
•
Example log messages on page 144
Logging
•
Log filter command on page 145
MALC Configuration Guide
135
Diagnostics and Administration
Overview Logging enables administrators to monitor system events by generating system messages. It sends these message to:
•
A management session (either on the serial craft port or over a telnet session)
•
A log file on the device
•
A syslog server (optional)
The type of information sent in these messages can be configured using the log command. By default, the system sends the same type of information to all log message destinations. If you want to send different types of messages to the syslog daemon, use the syslog command.
Enabling/disabling logging By default, log messages are enabled on the serial craft port. Use the log session command and the log serial command to enable/disable logging: The log session command enables/disables logging messages for that session only. If the user logs out, the logging setting returns to the default. To enable logging for the current session only: zSH> log session on
To disable logging for the session: zSH> log session off
The log serial command enables/disables logging messages for all sessions on the serial craft port. This setting persists across system reboots. To enable/ disable logging for the serial craft port: zSH> log serial on
To disable logging for the serial port: zSH> log serial off
Log message format Log messages contain the following information: Table 10: Default log message fields
136
MALC Configuration Guide
Option
Description
Date
Date stamp of log message. Enabled by default.
Time
Time stamp of log message. Enabled by default.
Ticks
Current tick count. When the tick option is used, the date and time fields are not displayed.
Level
Logging level of the message. Enabled by default.
Logging
Table 10: Default log message fields (Continued) Option
Description
Address
The shelf and slot of the card causing the alarm,
Taskname
Name of task that generated the log message. This is generally useful only for Zhone development engineers. Enabled by default.
Function
Function that generated the log message. This is generally useful only for Zhone development engineers.
Line
Line in code that generated the log message. This is generally useful only for Zhone development engineers.
Port
Port related to the log message.
Category
Category of the log message.
System
System related to the log message.
All
Controls all log message options.
Default
Controls the default log message options.
Message text
A description of the error that caused the alarm.
To change the information displayed in the log messages, use the log option command. First, display the available options: zSH> log option Usage: log option
< time | 1 > < on | off > < date | 2 > < on | off > < level | 3 > < on | off > < taskname | 4 > < on | off > < taskid | 5 > < on | off > < file | 6 > < on | off > < function | 7 > < on | off > < line | 8 > < on | off > < port | 9 > < on | off > < category | 10 > < on | off > < system | 11 > < on | off > < ticks | 12 > < on | off > < all | 13 > < on | off > < default | 14 > < on | off > time: date: level: address: log: port: category: system:
(0x707)
Then, turn the option on or off. For example, the following command will turn the task ID off in log messages: zSH> log option taskid off time: date: level: address: log: taskname:
(0xf)
The following commands will turn ton/off the tick count display in log messages:
MALC Configuration Guide
137
Diagnostics and Administration
zSH> log option ticks on time: date: level: address: log: port: category: system: ticks: (0xf07) zSH> log option ticks off time: date: level: address: log: port: category: system: (0x707)
The following command will turn all options on in log messages: zSH> log option all on time: date: level: address: log: taskname: taskid: file: function: line: port: category: system: ticks: (0xfff)
Modifying logging levels To modify logging, use the log command. To modify syslog messages, use the syslog command. To display the current levels for all logging modules, use the log show command: zSH> log show MODULE aal2approv aal2aprec aal2rp aal2rpzccapi aal2rpvcc alarm_mgr assert atm_cc_mib_hdlr atmmgr atmmgragnt bds bds_client callcontrolregistry card card_resource carddeletehdlr ccrp cli ... ... ...
LEVEL error error error error error error error error error error error error error error error error error error
STATUS enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled
Logging levels determine the number of messages that are displayed on the console. The higher the log level, the more messages are displayed. The MALC supports the following log levels:
138
MALC Configuration Guide
•
1: emergency
•
2: alert
Logging
•
3: critical
•
4: error
•
5: warning
•
6: notice
•
7: information
•
8: debug
To change the log level, use the log module level command. For example, the following command changes the card module logging level to emergency: zSH> log level card emergency Module: card at level: emergency
To enable or disable log levels for a module, use the log enable or log disable commands. For example: zSH> log disable card Module: card is now disabled
Using the log cache The log cache command displays the non-persistent log messages. It uses the following syntax: log cache
Displays the log cache. log cache max length
Sets the maximum number of log messages to store. The maximum log cache size is 2147483647, depending in the amount of memory available. log cache grep pattern
Searches through the log cache for the specified regular expression. log cache clear
Clears the log cache. log cache size
Sets the maximum amount of memory for the log cache. Without options, displays the current log size. log cache help
Displays help on the log cache command.
Examples To change the current configured log cache size: zSH> log cache max 200 Maximum number of log messages that can be saved: 200
MALC Configuration Guide
139
Diagnostics and Administration
The following example searches through the log cache for the string “Major”: zSH> log cache grep Major Searching for: "Major" [1]: FEB 07 11:18:42: alert : 1/1/1025: alarm_mgr: tLineAlarm: 01:01:01 Major D S1 Down Line 1:1:1:0 (FarEnd Rx LOF)[2]: FEB 07 11:18:42: alert : 1/1/1025: alarm_mgr: tLineAlarm: 01:01:02 Major D S1 Down Line 1:1:2:0 (FarEnd Rx LOF)[3]: FEB 07 11:18:42: alert : 1/1/1025: alarm_mgr: tLineAlarm: 01:01:03 Major D S1 Down Line 1:1:3:0 (FarEnd Rx LOF) ... ... ...
Viewing the persistent logs Use the log cache command to view the persistent logs. For example: zSH> log cache [1]: JAN 13 17:23:40: alert SL Down DSL line [2]: JAN 13 17:23:40: alert SL Down DSL line [3]: JAN 13 17:23:40: alert SL Down DSL line [4]: JAN 13 17:23:40: alert SL Down DSL line [5]: JAN 13 17:23:41: alert SL Down DSL line [6]: JAN 13 17:23:41: alert SL Down DSL line [7]: JAN 13 17:23:41: alert SL Down DSL line [8]: JAN 13 17:23:41: alert SL Down DSL line [9]: JAN 13 17:23:41: alert SL Down DSL line [10]: JAN 13 17:23:41: alert DSL Down DSL line [11]: JAN 13 17:23:42: alert DSL Down DSL line ... ... ...
140
MALC Configuration Guide
: 1/6/1025: alarm_mgr: tLineAlarm: 01:06:18 Minor D : 1/5/1025: alarm_mgr: tLineAlarm: 01:05:26 Minor D : 1/5/1025: alarm_mgr: tLineAlarm: 01:05:27 Minor D : 1/6/1025: alarm_mgr: tLineAlarm: 01:06:20 Minor D : 1/6/1025: alarm_mgr: tLineAlarm: 01:06:21 Minor D : 1/6/1025: alarm_mgr: tLineAlarm: 01:06:22 Minor D : 1/6/1025: alarm_mgr: tLineAlarm: 01:06:25 Minor D : 1/6/1025: alarm_mgr: tLineAlarm: 01:06:29 Minor D : 1/6/1025: alarm_mgr: tLineAlarm: 01:06:32 Minor D : 1/6/1025: alarm_mgr: tLineAlarm: 01:06:31 Minor : 1/6/1025: alarm_mgr: tLineAlarm: 01:06:37 Minor
Logging
Sending messages to a syslog server Modify the following parameters in the syslog-destination profile to send messages to a syslog server. Parameter
Description
address
The IP address of the machine hosting the syslog server. Default: 0.0.0.0
port
The UDP port to which the syslog messages will be sent. Default: 514
facility
The syslog facility to which the syslog messages will be sent. Values: local0 local1 local2 local3 local4 local5 local6 local7 no-map Default: local0
severity
The severity level used to filter messages being set to the syslog server. Values: emergency alert critical error warning notice info debug Default: debug
zSH> new syslog-destination 1 Please provide the following: [q]uit. address: --> {0.0.0.0}: 192.200.42.5 IP address of the syslog server port: -----> {514}: leave at default
MALC Configuration Guide
141
Diagnostics and Administration
facility: -> {local0}: severity: -> {debug}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Specifying different log formats for system and syslog messages The log-module profile supports the configuration of persistent log messages, syslog messages, and persistent storage levels by module. You only need to modify this profile if you want to send different messages to admin sessions, the persistent logs, and the syslog server. Parameter
Description
name
The name of the module whose logging is controlled by this profile. Default: logtest
display
Controls the display of messages on the system. Messages logged at this level and above will be displayed. Values: emergency alert critical error warning notice info debug Default: error
142
MALC Configuration Guide
Logging
Parameter
Description
syslog
Controls the format of messages sent to the syslog server described in the syslog-destination profile. This field is similar to the display field, except for the trackdisplay value. Values: emergency alert critical error warning notice info debug trackdisplay Messages logged at, and above, the level set in the display parameter will also be recorded in the syslog server. Default: trackdisplay
store
Controls the persistent storage of messages. This field is similar to the display field, except for the trackdisplay value. Values: emergency alert critical error warning notice info debug trackdisplay Messages logged at, and above, the level set in the display parameter will also be recorded in the syslog server. Default: trackdisplay
zSH> new log-module 1 Please provide the following: [q]uit. name: ----> {logtest}: test1 display: -> {error}: warning syslog: --> {trackdisplay}: store: ---> {trackdisplay}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
MALC Configuration Guide
143
Diagnostics and Administration
Example log messages
1
This section provides examples of how to interpret log messages.
DSL line down message The following message appears when a DSL line comes up or goes down. . Log level
Date and time
physical address (shelf/slot) task name
function name
line number
[1]: JAN 07 09:25:42: alert : 1/8/1025: alarm_mgr: _laMgrLogMsg(): l=261 : tLin eAlarm: 01:08:03 Minor DSL Down DSL line
Message text
The most important parts of the message are the date and time the event occurred, the shelf/slot of the event, and the message text. The remainder of the information is only useful for Zhone development engineers.
Slot card up message The next message appears after a slot card has finished loading its software and is ready to be provisioned. Log level
Date and time
physical address (shelf/slot) task name
function name
line number
[24]: JAN 05 20:12:28: notice : 1/2/12 : shelfctrl: _CardUpdateMsgProcess(): l= 381 : tShelfCtrl: Card in slot 1 changed state to RUNNING.
Message text
The most important parts of the message are the date and time the event occurred, the shelf/slot of the event, and the message text. The remainder of the information is only useful for Zhone development engineers.
144
MALC Configuration Guide
Logging
Log filter command The log filter command is available as part of the log command functionality. This command enables users to show, set and delete log filters. Log filters limit the scope of log messages to a specific entity for troubleshooting and diagnostics. When a log filter is set, the filter is assigned an index number and only messages relate the specified entity are displayed. Filters can be set for an specific ifindex, slot/port, VCL, or subscriber.
log filter Restrict the display of log messages to only the log messages for a specified entity. Syntax log filter show | set (ifindex|port slotport|vcl ifindex vpi vci|subscriber endpoint)| delete zSH> log filter set ifindex 12 New filter saved. zSH> log filter set port 5 24 New filter saved. zSH> log filter set vcl 100 0 1 New filter saved. zSH> log filter set subscriber 22 New filter saved. zSH> log filter show Index Type Filter Parameters ------ ---------------------------------------1 Port slot=1, port=1 2 Port slot=1, port=4 3 IfIndex IfIndex=12 4 Port slot=5, port=24 5 ATM VCL IfIndex=100, vpi=0, vci=1 6 IfIndex IfIndex=100 7 IfIndex IfIndex=104 8 IfIndex IfIndex=109 9 IfIndex IfIndex=103 10 IfIndex IfIndex=107 zSH> log filter delete 10 Log filter 10 deleted
MALC Configuration Guide
145
Diagnostics and Administration
MALC security features This section describes the MALC’s security features Secure Shell (SSH) and Secure File Transfer Protocol (SFTP).
•
MALC security (SSH and SFTP) on page 146
•
Tested MALC SSH clients on page 148
•
DSA and RSA keys on page 149
•
Cipher suites on page 150
•
Encryption-key commands on page 150 Note: For security reasons, host keys are not accessible via SNMP and cannot be saved/restored with the dump command.
MALC security (SSH and SFTP) The system 0 profile provides a secure parameter which allows only secure communication for management activities. When security is enabled, the MALC uses the following protocols:
•
Secure File Transfer Protocol (SFTP)
•
Secure shell (SSH)
Table 11 describes which protocols are allowed when the secure parameter is enabled and which protocols are allowed when the secure parameter is disabled. Table 11: Protocols for the secure parameter
146
MALC Configuration Guide
Disabled
Enabled
TFTP, FTP, SFTP
SFTP
Telnet, SSH
SSH
MALC security features
Enabling security on the MALC 1
To enable the security parameter enter update system 0 on the MALC, change the secure parameter from disabled to enabled, then save the file:
zSH> update system 0 system 0 Please provide the following: [q]uit. syscontact: -----------> {Zhone Global Services and Support 7001 Oakport Street Oakland Ca. (877) Zhone20 (946-6320) Fax (510)777-7113
[email protected]}: sysname: --------------> {raptorXP170}: syslocation: ----------> {Oakland}: enableauthtraps: ------> {disabled}: setserialno: ----------> {0}: zmsexists: ------------> {false}: zmsconnectionstatus: --> {inactive}: zmsipaddress: ---------> {0.0.0.0}: configsyncexists: -----> {false}: configsyncoverflow: ---> {false}: configsyncpriority: ---> {high}: configsyncaction: -----> {noaction}: configsyncfilename: ---> {}: configsyncstatus: -----> {syncinitializing}: configsyncuser: -------> {}: configsyncpasswd: -----> {** private **}: ** read-only ** numshelves: -----------> {1}: shelvesarray: ---------> {}: numcards: -------------> {1}: ipaddress: ------------> {0.0.0.0}: alternateipaddress: ---> {0.0.0.0}: countryregion: --------> {us}: primaryclocksource: ---> {0/0/0/0/0}: ringsource: -----------> {internalringsourcelabel}: revertiveclocksource: -> {true}: voicebandwidthcheck: --> {false}: alarm-levels-enabled: -> {critical+major+minor+warning}: userauthmode: ---------> {local}: radiusauthindex: ------> {0}: secure: ---------------> {disabled}: enabled webinterface: ---------> {enabled}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
2
To verify the change, enter get system 0:
zSH> get system 0 system 0 syscontact: -----------> {Zhone Global Services and Support 7001 Oakport Street Oakland Ca. (877) Zhone20 (946-6320) Fax (510)777-7113
[email protected]} sysname: --------------> {Zhone Malc} syslocation: ----------> {Oakland}
MALC Configuration Guide
147
Diagnostics and Administration
enableauthtraps: ------> setserialno: ----------> zmsexists: ------------> zmsconnectionstatus: --> zmsipaddress: ---------> configsyncexists: -----> configsyncoverflow: ---> configsyncpriority: ---> configsyncaction: -----> configsyncfilename: ---> configsyncstatus: -----> configsyncuser: -------> configsyncpasswd: -----> numshelves: -----------> shelvesarray: ---------> numcards: -------------> ipaddress: ------------> alternateipaddress: ---> countryregion: --------> primaryclocksource: ---> ringsource: -----------> revertiveclocksource: -> voicebandwidthcheck: --> alarm-levels-enabled: -> userauthmode: ---------> radiusauthindex: ------> secure: ---------------> webinterface: --------->
{disabled} {0} {false} {inactive} {0.0.0.0} {false} {false} {high} {noaction} {} {syncinitializing} {} ** private ** {1} {} {3} {0.0.0.0} {0.0.0.0} {us} {0/0/0/0/0} {internalringsourcelabel} {true} {false} {critical+major+minor+warning} {local} {0} {enabled} {enabled}
Tested MALC SSH clients Secure Shell (SSH) is a command interface and protocol for securely getting access to a remote computer. SSH commands are encrypted and secure in two ways. Both ends of the client/server connection are authenticated using a digital certificate, and passwords are protected by being encrypted. You can now connect to a MALC using the SSH client of your choice to encrypt the session. The MALC supports the following:
•
148
MALC Configuration Guide
OpenSSH –
cygwin
–
Linux
–
Solaris
•
Putty
•
Teraterm
•
SecureCRT
•
Absolute Telent
MALC security features
DSA and RSA keys The MALC automatically creates a Digital Signature Algorithm (DSA), a standard for digital signatures, and supports RSA, an algorithm for public-key cryptography. The DSA and RSA host keys for the server are persistently stored in the encryption-key profile. In order to manage the host keys, use the CLI command encryption-key. RSA involves a public key and a private key. The public key can be known to everyone and is used for encrypting messages. Messages encrypted with the public key can only be decrypted using the private key When the system first boots, it will try to load the existing DSA and RSA keys. If they do not exist, the system creates a 512 bit DSA key. The CLI encryption-key command can be used to view current keys, create a new key, regenerate keys that may have been compromised, and delete keys. To create a new key enter: zSH> encryption-key add rsa 1024 Generating key, please wait ... done. zSH>
Note: Generating keys is computationally intensive. The longer the key, the longer it takes to generate. Wait until the system shows that key generation is completed before you continue. To view the new key just created enter: Note: The encryption-key show command displays the keys that were generated and are available for use. The command does not show the actual keys. zSH> encryption-key show Index Type Length ----- ---------- -----1 dsa 512 2 rsa 1024
To regenerate a key that might have been compromised enter: zSH> encryption-key renew dsa Generating key, please wait ... done.
To delete an encryption key enter: zSH> encryption-key delete dsa
MALC Configuration Guide
149
Diagnostics and Administration
Cipher suites The MALC supports several ciphers for SSH. Table 12: MALC ciphers Cipher
Key size
aes256-cbc
32 bytes (256 bits)
rijndael256-cbc
32 bytes (256 bits)
aes192-cbc
24 bytes (192 bits)
rijndael192-cbc
24 bytes (192 bits)
aes128-cbc
16 bytes (128 bits)
rinjdael128-cbc
16 bytes (128 bits)
blowfish-cbc
16 bytes (128 bits)
3des-cbc
24 bytes (192 bits)
arcfour
16 bytes (128 bits)
Encryption-key commands encryption-key add Adds an encryption key to the encryption-key profile. Syntax encryption-key add [rsa|dsa] [512|768|1024|2048] Options
rsa|dsa Name and type of the encryption key. 512|768|1024|2048
The number of bytes the key is set to.
encryption-key delete Deletes an encryption key from the encryption-key profile. Syntax encryption-key delete [rsa|dsa] Options
rsa|dsa Name and type of the encryption key.
encryption-key renew Regenerates a compromised encryption key. Syntax encryption-key renew [rsa|dsa] Options
150
MALC Configuration Guide
rsa|dsa Name and type of the encryption key.
MALC security features
encryption-key show Displays the current encryption keys. Syntax encryption-key show
MALC Configuration Guide
151
Diagnostics and Administration
Testing This section describes the following:
•
Activating or deactivating interfaces on page 152
•
BER tests on page 153
•
IMA test pattern procedure on page 155
•
Loopbacks on page 159
•
Viewing IMA group status on page 173
Activating or deactivating interfaces Physical interfaces on the MALC have associated if-translate profiles, which enable or disable the interfaces. To change the state of an interface, use the adminstatus parameter in the if-translate profile associated with the interface. The if-translate profile uses the following syntax: if-translate shelf-slot-port-subport/type
For example, to activate a MALC T1 interface: zSH> update if-translate 1-1-1-0/ds1 Please provide the following: [q]uit. ifindex: -----> {1}: . shelf: -------> {1}: slot: --------> {1}: port: --------> {1}: subport: -----> {0}: type: --------> {ds1}: adminstatus: -> {down}: up physical-flag: ----> {true}: iftype-extension: -> {0}: ifName: -----------> {}: redundancy-param1: -> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
For example, to deactivate a MALC T1 interface: zSH> update if-translate 1-1-1-0/ds1 Please provide the following: [q]uit. ifindex: -----> {1}: . shelf: -------> {1}: slot: --------> {1}: port: --------> {1}: subport: -----> {0}: type: --------> {ds1}: adminstatus: -> {up}: down physical-flag: ----> {true}: iftype-extension: -> {0}: ifName: -----------> {}:
152
MALC Configuration Guide
Testing
redundancy-param1: -> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
BER tests The send-code parameter in the ds1-profile controls loopbacks and BER tests on the T1 interface. The following table describes the BERT options. Parameter
Description
send-code
Indicates what type of code is being sent across the DS1 interface by the device. Setting this parameter causes the interface to send the requested code. Values: sendQRSSPattern Sends a Quasi-Random Signal Source (QRSS) test pattern. send511Pattern Sends a 511 bit fixed test pattern. send3in24Pattern Sends a fixed test pattern of 3 bits set in 24. send2047Pattern Sends 2047 test pattern. send1in2Pattern Sends alternate one, zero pattern
Activating a BER test Note: BER tests disrupt traffic on the interface.
1
Update the ds1-profile to specify the BERT pattern:
zSH> update ds1-profile 1-1-1-0/ds1 Please provide the following: [q]uit. line-type: ----------------------> {esf}: line-code: ----------------------> {b8zs}: send-code: ----------------------> {sendnocode}: sendqrsspattern circuit-id: ---------------------> {ds1}: loopback-config: ----------------> {noloop}: signal-mode: --------------------> {robbedbit}: fdl: ----------------------------> {fdlnone}: dsx-line-length: ----------------> {dsx0}: line-status_change-trap-enable: -> {enabled}: channelization: -----------------> {enabledds0}: ds1-mode: -----------------------> {csu}: csu-line-length: ----------------> {csu00}: clock-source-eligible: ----------> {noteligible}: transmit-clock-source: ----------> {throughtiming} cell-scramble: ------------------> {false} coset-polynomial: ---------------> {true}:
MALC Configuration Guide
153
Diagnostics and Administration
protocol-emulation: -------------> {network} signal-type: --------------------> {loopstart} ds1-group-number: ---------------> {0} line-power: ---------------------> {disabled} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
2
To end a BER test:
zSH> update ds1-profile 1-1-1-0/ds1 Please provide the following: [q]uit. line-type: ----------------------> {esf}: line-code: ----------------------> {b8zs}: send-code: ----------------------> {sendqrsspattern}: sendnocode circuit-id: ---------------------> {ds1}: loopback-config: ----------------> {noloop}: signal-mode: --------------------> {robbedbit}: fdl: ----------------------------> {fdlnone}: dsx-line-length: ----------------> {dsx0}: line-status_change-trap-enable: -> {enabled}: channelization: -----------------> {enabledds0}: ds1-mode: -----------------------> {csu}: csu-line-length: ----------------> {csu00}: clock-source-eligible: ----------> {noteligible}: transmit-clock-source: ----------> {throughtiming cell-scramble: ------------------> {false} coset-polynomial: ---------------> {true}: protocol-emulation: -------------> {network} signal-type: --------------------> {loopstart} ds1-group-number: ---------------> {0} line-power: ---------------------> {disabled} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
154
MALC Configuration Guide
Testing
IMA test pattern procedure The MALC supports IMA test pattern procedures to validate the status of the IMA link. A test pattern sent over a transmit link is looped back over all available receive interfaces. Test pattern procedures do not interrupt traffic. The following table describes the test pattern procedure parameters in the ima-group-profile. Parameter
Description
testLinkIfIndex
Indicates the interface used to transmit the test pattern. The test pattern is looped back from the far end device over each active link in the IMA group. Note that this value is not the same as the txImaId value. Values: A valid interface on the system in the form shelf-slot-port-subport/type This is the link whose link identifier (LID) value is inserted in the Tx LID field of the transmitted ICP cells. Default: 0
testPattern
Specifies the transmit Test Pattern in an IMA group loopback operation. A value in the range 0 to 254 designates a specific pattern. Values: –1 to 254 –1 indicates that the test pattern is randomly generated. Default: –1
testProcStatus
Enables or disables the Test Pattern Procedure. Values: disabled Deactivates the test pattern procedure. operating Activates the test pattern procedure. Default: disabled
Testing the IMA link with a random test pattern A test pattern procedure with a random pattern will run continuously until it is disabled. Use the imatppshow command to view the status of the test (as explained in Viewing test procedure status on page 157). To test the IMA link with a randomly generated test link and pattern (the default): 1
Specify an interface to transmit the test over: zSH> update ima-group-profile 1/1/1 Please provide the following: [q]uit. groupSymmetry: ---> {symmetricoperation}: minNumTxLinks: ---> {1}: minNumRxLinks: ---> {1}:
MALC Configuration Guide
155
Diagnostics and Administration
txClkMode: -------> {ctc}: txImaId: ---------> {1}: txFrameLength: ---> {m128}: diffDelayMax: ----> {75}: alphaValue: ------> {2}: betaValue: -------> {2}: gammaValue: ------> {1}: testLinkIfIndex: -> {0}: 1-1-1-0/ds1 IMA link to test testPattern: -----> {-1}: testProcStatus: --> {disabled}: operating txTimingRefLink: -> {0}: rxTimingRefLink: -> {0}: groupRestoreNumRetry: -> {3}: groupRestoreNumDelay: -> {3600}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
2
To disable the test: zSH> update ima-group-profile 1/1/1 Please provide the following: [q]uit. groupSymmetry: ---> {symmetricoperation}: minNumTxLinks: ---> {1}: minNumRxLinks: ---> {1}: txClkMode: -------> {ctc}: txImaId: ---------> {1}: txFrameLength: ---> {m128}: diffDelayMax: ----> {75}: alphaValue: ------> {2}: betaValue: -------> {2}: gammaValue: ------> {1}: testLinkIfIndex: -> {1/1/1/0/ds1}: testPattern: -----> {-1}: testProcStatus: --> {enabled}: disabled txTimingRefLink: -> {0}: rxTimingRefLink: -> {0}: groupRestoreNumRetry: -> {3}: groupRestoreNumDelay: -> {3600}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Testing the IMA link with a specific test pattern A test with a specified test pattern runs until it verifies link connectivity. Use the imatppshow command to view the status of the test (as explained in Viewing test procedure status on page 157). 1
To specify a particular test pattern (for example, 23): zSH> update ima-group-profile 1/1/1 Please provide the following: [q]uit. groupSymmetry: ---> {symmetricoperation}:
156
MALC Configuration Guide
Testing
minNumTxLinks: ---> {1}: minNumRxLinks: ---> {1}: txClkMode: -------> {ctc}: txImaId: ---------> {1}: txFrameLength: ---> {m128}: diffDelayMax: ----> {75}: alphaValue: ------> {2}: betaValue: -------> {2}: gammaValue: ------> {1}: testLinkIfIndex: -> {0}: 1-1-1-0/ds1 IMA link to test testPattern: -----> {-1}: 23 testProcStatus: --> {disabled}: operating txTimingRefLink: -> {0}: rxTimingRefLink: -> {0}: groupRestoreNumRetry: -> {3}: groupRestoreNumDelay: -> {3600}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
To run the test again, update the ima-group-profile without making any changes. 2
To disable the test: zSH> update ima-group-profile 1/1/1 Please provide the following: [q]uit. groupSymmetry: ---> {symmetricoperation}: minNumTxLinks: ---> {1}: minNumRxLinks: ---> {1}: txClkMode: -------> {ctc}: txImaId: ---------> {1}: txFrameLength: ---> {m128}: diffDelayMax: ----> {75}: alphaValue: ------> {2}: betaValue: -------> {2}: gammaValue: ------> {1}: testLinkIfIndex: -> {1/1/1/0/ds1}: testPattern: -----> {-1}: testProcStatus: --> {enabled}: disabled txTimingRefLink: -> {0}: rxTimingRefLink: -> {0}: groupRestoreNumRetry: -> {3}: groupRestoreNumDelay: -> {3600}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Viewing test procedure status Use the imatppshow command to view the status of the test: If the test is successful, imaGroupTestProcStatus displays OPERATING:
MALC Configuration Guide
157
Diagnostics and Administration
zSH> imatppshow 1 TestLink .....................: 2 imaGroupTestPattern ..........: 23 imaGroupTestProcStatus .......: OPERATING
If the test fails (if, for example, the remote link is down), imaGroupTestProcStatus displays LINKFAIL: zSH> imatppshow 1 TestLink .....................: 2 imaGroupTestPattern ..........: 71 imaGroupTestProcStatus .......: LINKFAIL
After the test is disabled, the imaGroupTestProcStatus displays DISABLED: zSH> imatppshow 1 TestLink .....................: 2 imaGroupTestPattern ..........: 23 imaGroupTestProcStatus .......: DISABLED
158
MALC Configuration Guide
Testing
Loopbacks The MALC support the following types of loopbacks:
•
T1 loopbacks on page 159
•
DS3 loopbacks on page 163
•
SONET loopbacks on page 161
•
ISDN loopbacks on page 165
•
802.3ah Ethernet OAM loopback on page 166
•
SELT/DELT on MALC ADSL2+ Broadcom cards on page 169
T1 loopbacks The loopback-config parameter in the ds1-profile controls T1 loopbacks. The following table describes the loopback options. Parameter
Description
loopback-config
The loopback configuration of the DS1 interface. Values: noloop Not in the loopback state. A device that is not capable of performing a loopback on the interface always returns this as its value. lineloop The received signal at this interface is looped through the device. Typically the received signal is looped back for retransmission after it has passed through the device's framing function. payloadloop The received signal on this interface does not go through the device (minimum penetration) but is looped back out. Default: noloop
Activating a T1 loopback Note: Loopbacks disrupt traffic on the interface.
1
Specify the type of loopback: zSH> update ds1-profile 1-1-1-0/ds1 Please provide the following: [q]uit. line-type: ----------------------> {esf}: line-code: ----------------------> {b8zs}: send-code: ----------------------> {sendnocode}: circuit-id: ---------------------> {ds1}: loopback-config: ----------------> {noloop}: lineloop
MALC Configuration Guide
159
Diagnostics and Administration
signal-mode: --------------------> {robbedbit}: fdl: ----------------------------> {fdlnone}: dsx-line-length: ----------------> {dsx0}: line-status_change-trap-enable: -> {enabled}: channelization: -----------------> {enabledds0}: ds1-mode: -----------------------> {csu}: csu-line-length: ----------------> {csu00}: clock-source-eligible: ----------> {noteligible}: transmit-clock-source: ----------> {throughtiming} cell-scramble: ------------------> {false} coset-polynomial: ---------------> {true}: protocol-emulation: -------------> {network} signal-type: --------------------> {loopstart} ds1-group-number: ---------------> {0} line-power: ---------------------> {disabled} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Note: Only one loopback can be active at a time. If there is a loopback running, a message similar to the following will appear when you attempt to run another loopback: 1/1: ds1rp: : l=3278: Please disable any active loopbacks on line 1:1:0:0
2
To stop the loopback: zSH> update ds1-profile 1-1-1-0/ds1 Please provide the following: [q]uit. line-type: ----------------------> {esf}: line-code: ----------------------> {b8zs}: send-code: ----------------------> {sendlinecode}: circuit-id: ---------------------> {ds1}: loopback-config: ----------------> {lineloop}: noloop signal-mode: --------------------> {robbedbit}: fdl: ----------------------------> {fdlnone}: dsx-line-length: ----------------> {dsx0}: line-status_change-trap-enable: -> {enabled}: channelization: -----------------> {enabledds0}: ds1-mode: -----------------------> {csu}: csu-line-length: ----------------> {csu00}: clock-source-eligible: ----------> {noteligible}: transmit-clock-source: ----------> {throughtiming} cell-scramble: ------------------> {false} coset-polynomial: ---------------> {true}: protocol-emulation: -------------> {network} signal-type: --------------------> {loopstart} ds1-group-number: ---------------> {0} line-power: ---------------------> {disabled} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
160
MALC Configuration Guide
Testing
SONET loopbacks A SONET terminal loopback is a SONET circuit with a loop that terminates at the MALC OC3-c/STM1 interface. The medium-loopback-config parameter in the sonet-profile specifies the type of loopback: Parameter
Description
medium-loopback-config
How the SONET loopback is configured. Values: sonetnoloop SONET circuit, with no loop. sonetfacilityloop All incoming data on the Rx interface is retransmitted out of the Tx interface. Used to check the circuit between a remote device and the MALC and to test the MALC optical module. sonetterminalloop All of the data transmitted on the Tx interface is also internally looped back to the Rx interface. Used to verify that the ATM and PHY layers are communicating. sonetotherloop All incoming data on the Rx interface is retransmitted out of the Tx interface. Used to check the circuit between the IAD and a remote unit and to verify that the optical module and the SONET PHY are working.
Looping back the SONET interface The following example initiates SONET terminal loopbacks. 1
Set the interface to testing: zSH> update if-translate 1-1-1-0/sonet shelf-slot-port-subport/type Please provide the following: [q]uit. ifindex: -----> {232}: . shelf: -------> {1}: slot: --------> {1}: port: --------> {1}: subport: -----> {0}: type: --------> {sonet}: adminstatus: -> {down}: testing physical-flag: ----> {false}: iftype-extension: -> {none}: ifName: -----------> {}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
2
Configure the type of loopback:
MALC Configuration Guide
161
Diagnostics and Administration
zSH> update sonet-profile 1-1-1-0/sonet Please provide the following: [q]uit. medium-type: ---------------> {sonet}: medium-line-coding: --------> {sonetmediumnrz}: medium-line-type: ----------> {sonetshortsinglemode}: medium-circuit-identifier: -> {}: medium-loopback-config: ----> {sonetnoloop}: sonetterminalloop medium-scramble-config: ----> {sonetscrambleon}: path-current-width: --------> {sts3cstm1}: clock-external-recovery: ---> {enabled}: clock-transmit-source: -----> {looptiming}: medium-cell-scramble-config: -> {true}: medium-line-scramble-config: -> {true}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record saved.
Note: The adminstatus of the SONET line remains up and SONET communications continue during SONET terminal loopbacks.
162
MALC Configuration Guide
Testing
DS3 loopbacks The loopback-config parameter in the ds3-profile controls DS3 loopbacks. The following table describes the loopback options.
Parameter
Description
loopback-config
Specifies the loopback configuration of the interface. Values: dsx3noloop The DS3 interface is not in the loopback state. dsx3payloadloop The received signal at the DS3 interface is looped through the system for retransmission. dsx3inwardloop The sent signal at the DS3 interface is looped back through the system. dsx3lineloop The received signal at the DS3 interface does not go through the device before it is looped.
Activating a DS3 loopback Note: Loopbacks disrupt traffic on the interface.
1
Specify the type of loopback:
zSH> update ds3-profile 1-1-2-0/ds3 line-type: ---------------> {dsx3cbitparity} line-coding: -------------> {dsx3b3zs} send-code: ---------------> {dsx3sendnocode} circuit-id: --------------> {} loopback-config: ---------> {dsx3noloop} specify type of loopback transmit-clock-source: ---> {looptiming} line-length-meters: ------> {0} line-status-trap-enable: -> {enabled} channelization: ----------> {disabled} ds1-for-remote-loop: -----> {0} far-end-equip-code: ------> {} far-end-loc-id-code: -----> {} far-end-frame-id-code: ---> {} far-end-unit-code: -------> {} far-end-fac-id-code: -----> {} medium-scramble-config: --> {true} medium-frame-config: -----> {e3frameg832} medium-atmframe-config: --> {dsx3atmframingdirectcellmapped}
MALC Configuration Guide
163
Diagnostics and Administration
Note: Only one loopback can be active at a time.
2
To stop the loopback:
zSH> update ds3-profile 1-1-2-0/ds3 line-type: ---------------> {dsx3cbitparity} line-coding: -------------> {dsx3b3zs} send-code: ---------------> {dsx3sendnocode} circuit-id: --------------> {} loopback-config: ---------> {dsx3payloadloop} dsx3noloop transmit-clock-source: ---> {looptiming} line-length-meters: ------> {0} line-status-trap-enable: -> {enabled} channelization: ----------> {disabled} ds1-for-remote-loop: -----> {0} far-end-equip-code: ------> {} far-end-loc-id-code: -----> {} far-end-frame-id-code: ---> {} far-end-unit-code: -------> {} far-end-fac-id-code: -----> {} medium-scramble-config: --> {true} medium-frame-config: -----> {e3frameg832} medium-atmframe-config: --> {dsx3atmframingdirectcellmapped}
164
MALC Configuration Guide
Testing
ISDN loopbacks Loopbacks can be run on the ISDN B and D channels. Note: Loopbacks disrupt traffic on the interface. Modify the loopback parameter in the isdn-profile to configure ISDN loopbacks: Parameter
Description
loopback
Initiates ISDN loopback on the U interface. Values: loop-back-none no loop back loop-back-b1-idl2-tr transparent loopback on the Interchip Digital Link, Version 2 (IDL2), which is used for transporting the ISDN channels towards the system (B1 channel) loop-back-b1-idl2-nt non-transparent loopback on the IDL2 interface towards the system (B1 channel) loop-back-b2-idl2-tr transparent loopback on the IDL2 interface towards the system (B2 channel) loop-back-b2-idl2-nt non-transparent loopback on the IDL2 interface towards the system (B2 channel) loop-back-2bd-idl2-tr transparent loopback on the IDL2 towards the system (2B + D channel) loop-back-2bd-idl2-nt non-transparent loopback on the IDL2 towards the system (2B + D channel) loop-back-2bd-u-interface-tr transparent loopback on the U interface towards the user (2B + D channel) loop-back-2bd-u-interface-nt non-transparent loopback on the U interface (2B + D channel) loop-back-2bd-external-analog loopback on the external analog interface towards the user (2B + D channel) Default: loop-back-none
zSH> update isdn-profile 1-14-1-0/isdnu Please provide the following: [q]uit. line-term-class: ---> {class1}: activation-timer2: -> {t2-50ms}: loopback: ----------> {loop-back-none}: loop-back-b1-idl2-tr Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
MALC Configuration Guide
165
Diagnostics and Administration
802.3ah Ethernet OAM loopback The Ethernet OAM loopback feature is available on all MALC SLMS devices that support Ethernet 802.3ah OAM. You can use Ethernet 802.3ah OAM loopback to test link integrity. Configuring Ethernet OAM loopback on a link interrupts normal service on the link. All traffic that is received, except for OAMPDUs, will either be looped back onto the transmit or dropped depending on which end is set to local loopback. When configuring loopback, the interface set to local loopback loops all received packets back out the transmit side of the interface. The interface set to remote loopback transmits traffic normally bridged or routed out this interface, and drops all received traffic. Because there is no traffic generation, it is recommended that you enable loopback on the peer device, clear statistics, then watch to see if packet counters increase on the local receiver. Before setting a peer device to loopback mode, a connection must exist between the devices.
Configuring Ethernet OAM loopback To configure Ethernet OAM loopback, the device that sends the loopback command must be set to active mode, and the device that receives the loopback command must have OamLoopbackIgnoreRx set to process. For Ethernet OAM loopback to work, parameters on both the MALC and remote device must be set as follows: Note: You can also use the eth-oam modify command on existing ether-oam profile interfaces. 1
To set the mode to active in the ether-oam profile on the MALC enter eth-oam add interface/type active: zSH> eth-oam add 1-16-201-0/efmbond active
2
To set the mode to passive in the ether-oam profile on the peer device, in this case an EtherXtend, enter eth-oam add interface/type passive: zSH> eth-oam add 1-1-204-0/efmbond passive
Or: If the devices at both ends are set to active, and you want to send a loopback command to a peer device, the OamLoopbackIgnoreRx must be set to process on that peer device. Use eth-oam modify interface/type loopbackignore false to set OamLoopbackIgnoreRx to process: zSH> eth-oam modify 1-1-204-0/efmbond loopbackignore false
166
MALC Configuration Guide
Testing
3
To view the local and remote status of the OAM loopback status parameter on the MALC, enter eth-oam show interface/type:
Malc> eth-oam show 1-16-201-0/efmbond ********** Ethernet OAM Profile for interface 1-16-201-0/efmbond (1187) ************ OperationalState Operational OamMode active MaxOamPduSize 1518 ConfigurationRevision 4 FunctionsSupported (loopback)(events) OamLoopbackStatus no loopback OamLoopbackIgnoreRx ignore ErroredFrame Window 10 ErroredFrame Threshold 1 ErroredFrame Notify enabled ErroredFramePeriod Window 4294967295 ErroredFramePeriod Threshold 1 ErroredFramePeriod Notify disabled ErroredFrameSecondsSummary Window 100 ErroredFrameSecondsSummary Threshold 1 ErroredFrameSecondsSummary Notify disabled DyingGaspEnable disabled CriticalEventEnable disabled
4
To view the status of the OAM loopback status parameter on the EtherXtend, enter eth-oam show interface/type:
zSH> eth-oam show 1-1-204-0/efmbond ********** Ethernet OAM Profile for interface 1-1-204-0/efmbond (21) ************ OperationalState Operational OamMode passive MaxOamPduSize 1518 ConfigurationRevision 2 FunctionsSupported (loopback)(events) OamLoopbackStatus no loopback OamLoopbackIgnoreRx process ErroredFrame Window 10 ErroredFrame Threshold 1 ErroredFrame Notify enabled ErroredFramePeriod Window 4294967295 ErroredFramePeriod Threshold 1 ErroredFramePeriod Notify disabled ErroredFrameSecondsSummary Window 100 ErroredFrameSecondsSummary Threshold 1 ErroredFrameSecondsSummary Notify disabled DyingGaspEnable disabled CriticalEventEnable disabled
5
To change the OAM loopback status parameter on the MALC to remote you must enter eth-oam peer interface/type loopback true: Malc> eth-oam peer 1-16-201-0/efmbond loopback true
MALC Configuration Guide
167
Diagnostics and Administration
6
To view the new status of the OAM loopback status parameter on the MALC enter eth-oam show interface/type:
Malc> eth-oam show 1-16-201-0/efmbond ********** Ethernet OAM Profile for interface 1-16-201-0/efmbond (1187) ************ OperationalState Operational OamMode active MaxOamPduSize 1518 ConfigurationRevision 2 FunctionsSupported (loopback)(events) OamLoopbackStatus remote loopback OamLoopbackIgnoreRx ignore ErroredFrame Window 10 ErroredFrame Threshold 1 ErroredFrame Notify enabled ErroredFramePeriod Window 4294967295 ErroredFramePeriod Threshold 1 ErroredFramePeriod Notify disabled ErroredFrameSecondsSummary Window 100 ErroredFrameSecondsSummary Threshold 1 ErroredFrameSecondsSummary Notify disabled DyingGaspEnable disabled CriticalEventEnable disabled
7
To view the new status of the OAM loopback status parameter on the EtherXtend, enter eth-oam show interface/type:
zSH> eth-oam show 1-1-204-0/efmbond ********** Ethernet OAM Profile for interface 1-1-204-0/efmbond (21) ************ OperationalState Operational OamMode passive MaxOamPduSize 1518 ConfigurationRevision 1 FunctionsSupported (loopback)(events) OamLoopbackStatus local loopback OamLoopbackIgnoreRx process ErroredFrame Window 10 ErroredFrame Threshold 1 ErroredFrame Notify enabled ErroredFramePeriod Window 4294967295 ErroredFramePeriod Threshold 1 ErroredFramePeriod Notify disabled ErroredFrameSecondsSummary Window 100 ErroredFrameSecondsSummary Threshold 1 ErroredFrameSecondsSummary Notify disabled DyingGaspEnable disabled CriticalEventEnable disabled
8
To release the loopback from the MALC enter eth-oam peer interface/ type loopback false: Malc> eth-oam peer 1-16-201-0/efmbond loopback false
168
MALC Configuration Guide
Testing
SELT/DELT on MALC ADSL2+ Broadcom cards SELT (Single-End Loop Tests) Single End Loop Test, SELT, tests a copper loop from the ADSL2+ card to eliminate the need for external test equipment at the CO or a CPE at the remote end of the loop. Use SELT in advance to see if a loop is capable of supporting ADSL2+ by determining the distance, wire gauge, noise, and attenuation of the line; loop conditions that can be fixed before rolling a truck to the customer premises. Before running SELT, you must admin down the port before running the test by entering: zSH> port down interface/type
Note: SELT does not indicate when the tests are finished. Typically a test takes 2-3 minutes.
Configuring SELT The MALC supports the following SELT commands
•
selt start Starts a SELT test on an interface: zSH> selt start 1-3-8-0/adsl Selt test started on interface 1-3-8-0/adsl
•
selt abort Terminates a SELT test on an interface.
•
selt clear Clear SELT results for an interface.
•
selt set units Set the SELT display units for all interfaces.
•
selt set max-duration Sets the maximum amount of time a SELT test can run.
•
selt gauge Sets the expected diameter of the wire connected to an interface. The diameter may be set using any units, regardless of the display units set with the selt set units command. The wire-gauge option must use one of these settings: –
unknown - unknown wire gauge
–
awg19 - 19 gauge
MALC Configuration Guide
169
Diagnostics and Administration
–
awg22 - 22 gauge
–
awg24 - 24 gauge
–
awg26 - 26 gauge
–
32mm - 0.32 millimeters
–
40mm - 0.40 millimeters
–
50mm - 0.50 millimeters
–
63mm - 0.63 millimeters
–
65mm - 0.65 millimeters
–
90mm - 0.90 millimeters
The chip used to implement the selt test may restrict which values can be configured.
•
selt cable Sets the type of cable being tested, real or simulated. The real setting indicates that an actual physical cable is connected to the interface. In a lab or test environment, the cable may be simulated and use the dsl90 or dsl400 setting.
•
–
real: indicates a physical cable is connected to the interface.
–
dsl90: a Consultronics/Spirent DLS90 is simulating the cable.
–
dsl400: a Consultronics/Spirent DLS400 is simulating the cable.
selt show status Displays SELT test progress: zSH> selt show status 1-3-8-0/adsl status: complete max-duration: disabled cfg-gauge: awg26 cfg-cable: real time-left: 0 seconds device: broadcom-6411 bridge-taps: not-supported date-time: results generated 24 jun 2008, 20:46:45 length: 9294 feet gauge: awg24
•
selt show noise [start-index [num-vals]] Displays SELT noise floor per subcarrier.
The can be in the form of ifIndex (432), name/type (1-4-1-0/adsl) or shelf/slot/port/subport/type (1/4/1/0/adsl0. To configure SELT, enter the desired SELT test commands. The following example contains the commands for setting units, max-duration, starting a test, stopping a test, displaying status, clearing test data, and displaying noise.
170
MALC Configuration Guide
Testing
DELT (Dual-End Loop Test) DELT is a dual-ended test that requires equipment at both ends of the copper loop. While this prevents DELT from being used on loops where no CPE has yet been deployed, DELT offers a deeper set of loop tests, and can provide very valuable information on the condition of a copper loop. You use DELT primarily for reactive tests on a loop after a modem has been deployed to either help troubleshoot a line or capture a baseline of loop characteristics. In addition, DELT can assist in predetermining line capability to support new services, such as voice and video. Note: To run DELT commands, the port does not have to be down.
Configuring DELT The MALC supports the following SELT commands:
•
delt start Starts a DELT test on an interface: zSH> delt start 1-3-2-0/adsl Delt test started on interface 1-3-2-0/adsl
•
delt abort Terminates a DELT test on an interface: zSH> delt abort 1-3-2-0/adsl Delt test aborted on interface 1-3-2-0/adsl
•
delt clear Clear DELT results for an interface: zSH> delt clear 1-3-2-0/adsl Delt results cleared on interface 1-3-2-0/adsl
•
delt show status Displays DELT test progress:
zSH> delt show status 1-3-2-0/adsl Status: success Device: broadcom-6411 Delt results generated 24 jun 2008, 15:33:34.
Attainable Bit Rate (bps) Loop Attenuation (dB) Signal Attenuation (dB) SNR Margin (dB)
Downstream -----------6588000 38.5 38.5 5.8
Upstream -----------1064000 20.5 19.5 6.0
MALC Configuration Guide
171
Diagnostics and Administration
Actual Transmit Power (dBm)
•
19.9
12.3
delt show noise [start-index [num-vals]] Displays DELT noise floor per subcarrier.
The can be in the form of ifIndex (432), name/type (1-4-1-0/adsl) or shelf/slot/port/subport/type (1/4/1/0/adsl0. To configure DELT, enter the desired DELT test commands. The following example contains the commands for setting units, max-duration, starting a test, stopping a test, displaying status, clearing test data, and displaying noise. zSH> delt show noise 1-3-2-0/adsl Delt results generated 24 jun 2008, 15:33:34. Tone Tone Freq Attenuation (dB) Noise (dBm/Hz) SNR (dB) Index (kHz) dnstream upstream dnstream upstream dnstream upstream ----- ---------------- --------------- --------------- -------0 4.3125 no data -51.1 -106.0 -146.0 0.0 no data 1 8.6250 -74.7 no data -135.0 -133.0 0.0 no data 2 12.9375 -77.1 no data -138.0 -133.0 0.0 no data 3 17.2500 -77.1 no data -139.0 -131.5 0.0 no data 4 21.5625 -80.5 -85.9 -140.0 -132.5 0.0 no data 5 25.8750 -80.5 -82.2 -141.0 -129.5 0.0 no data 6 30.1875 -80.5 -34.6 -141.0 -127.5 0.0 no data 7 34.5000 -80.5 -26.0 -140.0 -119.5 0.0 31.0 8 38.8125 -80.5 -19.4 -141.0 -117.0 0.0 37.5 9 43.1250 -86.1 -15.8 -141.0 -112.0 0.0 43.0 10 47.4375 -86.1 -14.8 -140.0 -112.0 0.0 46.0 11 51.7500 -79.4 -14.9 -140.0 -115.0 0.0 49.0 12 56.0625 no data -15.4 -140.0 -117.5 0.0 50.5 13 60.3750 -79.4 -16.0 -139.0 -116.5 0.0 51.5 14 64.6875 -79.4 -16.5 -138.0 -116.0 0.0 52.5 15 69.0000 -79.6 -17.1 -136.0 -117.5 0.0 52.5 for next page, for next line, A for all, Q to quit zSH> delt show noise 1-3-2-0/adsl 253 6 Delt results generated 24 jun 2008, 15:33:34. Tone Index ----253 254 255 256 257 258 259
172
Tone Freq (kHz) --------1095.3750 1099.6875 1104.0000 1108.3125 1112.6250 1116.9375 1121.2500
MALC Configuration Guide
Attenuation (dB) dnstream upstream -------- -------6.0 no data 6.0 no data 6.0 no data -40.7 no data -40.9 no data -41.1 no data -41.2 no data
Noise (dBm/Hz) dnstream upstream -------- --------126.0 no data -126.0 no data -125.0 no data -126.0 no data -126.0 no data -126.0 no data -125.0 no data
SNR (dB) dnstream upstream -------- -------24.0 no data 23.5 no data 24.5 no data 24.5 no data 24.0 no data 22.5 no data 22.0 no data
Testing
Viewing IMA group status The imarpshow command displays information about the MALC IMA group. The command uses the following syntax: imarpshow [index]
where index is the IMA group number. For example: zSH> imarpshow RP Info: rp state -------------------> address --------------------> rp shelf -------------------> rp slot --------------------> rp ima core started --------> imaGrpProfLeaseId ----------> LineRRProvLeaseId ----------> LineRRClientLeaseId --------> numImaGroups ---------------> ImaGroupIndecies: 1
RP_INITIALIZED 01:01:113 1 1 TRUE 0x02070000_00000057 0x02070000_00000055 0x02070000_00000056 1
To display complete information about an IMA group, specify the group number: zSH> imarpshow 1 RP Info: rp state -------------------> RP_INITIALIZED address --------------------> 01:01:113 rp shelf -------------------> 1 rp slot --------------------> 1 rp ima core started --------> TRUE imaGrpProfLeaseId ----------> 0x02070000_00000057 LineRRProvLeaseId ----------> 0x02070000_00000055 LineRRClientLeaseId --------> 0x02070000_00000056 numImaGroups ---------------> 1 ImaGroupIndecies: 1 IMA Group Index =1 .............................................. group status ==========> OOS ......................... group ne state --------> INSUFFICIENTLINKS group fe state --------> OPERATIONAL ......................... group ctlr state ------> GRP_INITIALIZED group ifIndex ---------> 11 group in service ------> TRUE driver attached -------> TRUE driver unit -----------> 0 auto-created ----------> FALSE ifxLeaseId ------------> 0x02070000_00000057 lineProfLeaseId -------> 0x02070000_00000057 lineGrpLeaseId --------> 0x02070000_00000057 ifStackLeaseId --------> 0x02070000_00000057 ds1LeaseId ------------> 0x00000000_00000000
MALC Configuration Guide
173
Diagnostics and Administration
......................... ifxlateProfValid ----------------> TRUE ifxlatProf.ifIndex --------------> 11 ifxlatProf.shelf ----------------> 1 ifxlatProf.slot -----------------> 1 ifxlatProf.port -----------------> 2 ifxlatProf.ifType ---------------> ATMIMA ifxlatProf.adminStatus ----------> UP ......................... lineProfValid -------------------> TRUE lineProf.profileName ------------> Atm IMA Group default line profile lineProf.physicalAddress.shelf --> 1 lineProf.physicalAddress.slot ---> 1 lineProf.physicalAddress.port ---> 2 lineProf.lineGroupName ----------> 11 ......................... lineGrpProfValid ----------------> TRUE lineGrpProf.groupName -----------> 1/1/1 lineGrpProf.primaryName ---------> 11 lineGrpProf.secondaryName -------> 0 lineGrpProf.primaryWeight -------> 0 lineGrpProf.secondaryWeight -----> 0 lineGrpProf.adminState ----------> UP ......................... imaGrpProfValid -----------------> TRUE imaGrpProf.groupSymmetry --------> SYMMETRICAL imaGrpProf.minNumTxLinks --------> 1 imaGrpProf.minNumRxLinks --------> 1 imaGrpProf.txClkMode ------------> CTC imaGrpProf.txImaId --------------> 1 imaGrpProf.txFrameLength --------> M128 imaGrpProf.diffDelayMax ---------> 75 imaGrpProf.alphaValue -----------> 1 imaGrpProf.betaValue ------------> 1 imaGrpProf.gammaValue -----------> 1 imaGrpProf.testLinkIfIndex ------> 0 imaGrpProf.testPattern ----------> -1 imaGrpProf.testProcStatus -------> DISABLED imaGrpProf.txTimingRefLink ------> 0 imaGrpProf.rxTimingRefLink ------> 0 ......................... Link#1 linkType -----------> DS1_PROFILE_LINETYPE_ESF ifIndex ------------> 2 framerstatus -------> OOS netxlinkstatus -----> NOT-IN-GROUP nerxlinkstatus -----> NOT-IN-GROUP .......................... ... ... ...
174
MALC Configuration Guide
4
CONFIGURING IP This chapter explains IP services on the MALC. It includes the following sections:
•
IP Overview, page 175
•
Applications, page 180
•
IP provisioning procedures, page 188
•
Advanced IP provisioning procedures, page 214
•
IP administrative procedures, page 232
Other IP related information may be found in the following sections:
•
Configuring the MALC for video, page 513
IP Overview The Internet protocol (IP) allows devices to communicate over interconnected networks. IP is a layer 3 protocol in the seven-layer Open Systems Interconnection (OSI) model. It should be understood that the MALC can be configured as a bridge (layer 2 device) or a router (layer 3 device) or both at the same time. Layer 2, the lower level, also called the logical link layer uses Media Access Control (MAC) Addresses to direct traffic. Layer 2 uses IP Addresses to direct traffic. Even though the MALC may do both bridging and routing, configurations for IP termination (basically routing) or bridging must be on different circuits. Each configuration requires at least two interfaces to work together, however each interface must be configured for either IP termination or bridging and cannot support both at the same time. Layer 3, the network layer, handles the delivery of data packets from source to destination. Any device connected to a network is considered a host or a node on that network. Zhone devices with IP capability can act as routers to accept network traffic and forward it on to host destinations based on IP addresses. To get from source to destination, the IP packet passes through many nodes, or hops, along the way. All routers maintain routing tables of the sequence of hops taken from source to destination. The routing table is used by the router to direct datagrams most efficiently. The routing table information is also shared with other routers on the same network.
MALC Configuration Guide
175
Configuring IP
Figure 10: IP stacking on Zhone devices
ADSL Modem
IP
ADSL Modem
Layer 3
IP Layer 2
Ethernet
SAR
RFC 1483
ATM CC
SAR
Ethernet Layer 1
Twisted Pair
DSL
Category 5 Cable
IP services The MALC provides the following IP services:
176
MALC Configuration Guide
•
IP forwarding and routing—incoming packets from an interface are forwarded to the appropriate output interface using the routing table rules.
•
IP filtering. IP filtering is typically performed to enhance network security by limiting access between two networks.
•
DHCP servers to simplify user IP address configuration.
•
DHCP relay to provide access to upstream DHCP servers
•
Source address based routing
•
Numbered or unnumbered (floating) interfaces
•
IP TOS
•
IP redundancy
IP Overview
IP protocols The following IP protocols are supported on the MALC.
DNS Domain Name System (DNS) maps domain names to IP addresses, enabling the system to reach destinations when it knows only the domain name of the destination.
DHCP Dynamic Host Control Protocol (DHCP) is the means for assigning IP addresses dynamically. Basically a DHCP server has a pool of IP addresses that can be assigned to physical devices. This mechanism conserves the number of IP addresses required for a network. A physical device will maintain its MAC address, but may have a different IP address each time it connects to the network. DHCP simplifies network administration since the software tracks the used and unused IP addresses. DHCP provides a mechanism through which client computers using TCP/IP can obtain configuration parameters (such as the default router and the DNS server, subnet mask, gateway address, and lease time) from a DHCP server. The most important configuration parameter carried by DHCP is the IP address. As a DHCP server, MALC can assign temporary (leased) IP addresses to client PCs. Each DHCP client PC sends a request to the MALC for an IP address lease. The MALC then assigns an IP address and lease time to the client PC. The MALC keeps track of a range of assignable IP addresses from a subnetwork. Some customers prefer to have the same IP address every time their DHCP lease renews. This is known as sticky IP addresses. By default, the MALC attempts to assign the same IP address to the same client on DHCP lease renewal. With shared DHCP pools (or subnet groups), DHCP servers are not linked to physical interfaces. Customers can easily configure an arbitrary number of DHCP pools. Zhone devices can assign blocks of IP addresses specifically for certain customers. The MALC may also act as a DHCP relay agent, supporting DHCP requests from downstream devices to upstream DHCP servers. The MALC supports both primary and alternate DHCP servers.
RIP Routing Information Protocol (RIP), an interior gateway protocol (IGP), is widely used for routing traffic on the Internet. RIP performs routing within a single autonomous system. It is based on distance-vector algorithms that measure the shortest path between two points on a network. The shortest path
MALC Configuration Guide
177
Configuring IP
is determined by the number of hops between those points. RIP routers maintain only the best route (the route with the lowest metric value) to a destination. After updating its routing table, the router immediately begins transmitting routing updates to inform other network routers of the shortest route. Routing Information Protocol version 2 (RIPv2) is the latest enhancement to RIP. RIPv2 allows more information to be included in RIP packets and provides an authentication mechanism.
IP TOS support The MALC supports IP QOS. This service enables you to assign a service level or type of service (TOS) to an IP interface. The configured TOS level specifies the packet priority and queueing methods used to transport the packet through the IP network. The MALC originates and preserves the TOS settings to ensure these settings are passed to other IP devices in the network.
Fields in IP header IP packets have a TOS byte in their headers that contains information about relative priority. The TOS byte is divided into two fields called IP Precedence and TOS. The IP Precedence field contains a 3-bit priority designation. Most normal traffic has an IP Precedence value of zero. Higher values in this field indicate that traffic is more important and that it requires special treatment. IP Precedence values greater than 5 are reserved for network functions. The TOS field indicates the queueing priority or Class of Service (COS) value based on eight (0-7) levels of service. This field contains information about how the traffic should be forwarded. The MALC supports basic TOS marking without queue servicing options in the ip-interface-record profile. Packets marked based on a configurable profile to let the system know which bits use which queue. Note: TOS bits are not altered for VoIP Real Time Transport Protocol (RTP) packets, which have their own TOS bit settings set in the voip-server-entry profile regardless of the TOS setting on the outgoing interface. Table 13 specifies the IP TOS settings used in the voip-server-entry profile based on IP Precedence bits. Table 13: IP TOS settings and IP Precedence bits
178
MALC Configuration Guide
Precedence Bits
TOS value
0 (Routine)
0
1 (Priority)
32
2 (Immediate)
64
IP Overview
Table 13: IP TOS settings and IP Precedence bits Precedence Bits
TOS value
3 (Flash)
96
4 (Flash override)
128
5 (CRITIC/ECP.)
160
6 (Internetwork control)
192
7 (Network control)
224
MALC Configuration Guide
179
Configuring IP
Applications The following IP applications are supported on the MALC:
•
Routing on page 180
•
Host-based and network-based routing on page 181
•
Host-based routing with DSL bridges on page 182
•
Network-based routing with DSL bridges on page 184
•
Network-based routing with DSL routers on page 185
•
IP filtering on page 186
•
Unnumbered IP interfaces on page 187
Routing Routing is the process of selecting a next hop for forwarding data traffic. The routing information base (RIB) contains all the information about the routes in the system, including the preference values and interface states. The forwarding information base (FIB) is derived from the RIB and only contains the best route to a given destination. IP routing through the system makes use of the following types of routes:
•
Interface routes—These routes are defined by the addresses and netmasks that are provisioned on the IP interfaces.
•
Static routes—These routes are manually configured as either destination based or source address based routes (SABR). Destination routes define paths to destinations in terms of an interface identifier or the IP address of a next-hop router on a directly attached network. SABR enables the forwarding of outbound VoIP SIP traffic based on a specific source IP address of a data packet instead of the destination IP address.With SABR routing, the source IP address or subnet address of a data packet is examined before packet forwarding. If the device finds a matching source route in the source routing table, the packet is forwarded according to the matched source route. If the device does not find a matching source route, destination routing is performed based on the destination routing table and if necessary the configured default route. There are two kinds of static routes:
180
MALC Configuration Guide
–
Low preference—These routes are only used to define default routes (that is, routes of last resort) and are less preferable to most other routes.
–
Normal preference—All other static routes are considered more preferable than other types of routes (with the exception of interface routes).
Applications
•
Dynamic routes—These routes are learned by running routing protocols, such as RIP, and have varying preferences, depending on how they were learned.
The following table describes the default routing preferences on the device. These preferences cannot be overridden. Higher numbers indicate more preferred route types: Type of route
Default preference
Local
10
Static
9
RIP
4
Static low
4
(used for default routes)
Host-based and network-based routing The MALC supports both host-based routing and network-based (subnet) routing. Host-based routing uses a unnumbered interface and adds a single IP address to the routing table for each route. This type of routing allows a granular allocation of addresses based on the host floating (unnumbered) IP address and the available subnetwork addresses. Routes are configured individually using the host add command. For each configured route, an IP address is added to the routing table. For example, an unnumbered host address of 10.10.10.1/24, adds one entry in the routing table for the address 10.10.10.1 and makes available a subnet of 254 addresses for individual route configuration. When each host route is added, a new routing table entry is created. The host add command can also assign VLAN, SLAN, and COS values to the host interface. In the host add, host modify and host delete commands, and may be replaced with brackets containing numbers in series and/or (dash-separated) ranges; may be replaced with wildcard '*' for all ports on the card. The host modify command enables you to change individually configured routes for a host-based routing environment by altering values in the existing routing table entry. Refer to the CLI Reference Guide for a complete description of the command options and syntax. Note: In the host modify command, and may be replaced with brackets containing numbers in series and/or (dash-separated) ranges; may be replaced with wildcard ‘*’ for all ports on the card. Examples: 1-[10-13]-[1,3-5,21]-0/ds3 specifies DS3 ports 1,3,4,5,21 on cards 10,11,12, and 13. 1-[6,7,9]-*-0/adsl specifies all ADSL ports on cards 6, 7, and 9
MALC Configuration Guide
181
Configuring IP
Network-based (subnet) routing uses a numbered interface and adds IP network addresses with variable length subnet masks to the routing table. This type of routing allows a single routing table entry to represent many numbered host addresses. However, it does not allow for granular IP address allocation. For example, an interface configured with 10.10.10.1/24 adds just one entry to the routing table for 10.10.10.1/24. All 254 addresses in this subnet are assigned to this interface, regardless of how many addresses in this subnet are actually used. The command used to create the IP interface depends on the application, IP assignment, type of address allocation and interface type. Commands to add an IP interface on page 182 shows the commands to add an IP interface and the requirements. Table 14: Commands to add an IP interface Command
Application
IP Assignment
Address Allocation
Encapsulation
Interface Type
Host add
Host-based routing with DSL bridge or router
Static/Dynamic
Single per host add command
For bridge: other
Unnumbered
Network-based routing with DSL bridge or router
Static
Multiple based on subnet mask length
For bridge: other
Interface add
For router: LLC
Numbered
For router: LLC
Host-based routing with DSL bridges Host-based routing takes advantage of IP unnumbered interfaces and shared DHCP pools to conserve IP addresses. In the host-based routing with DSL bridges application, subscribers connected to the MALC are on the same subnet as the MALC unnumbered interface.
182
MALC Configuration Guide
Applications
Figure 11: Host-based routing with DSL bridges
Bridge
PC x.x.y.2
subscriber A IP
x.x.y.1
Bridge PC x.x.y.3
subscriber B
In the host-based routing with DSL routers application, remote IADs (or routers) are on the same subnet as the MALC unnumbered interface. The IADs connect private networks to the MALC. Figure 12: Host-based routing with DSL routers Private network
Public subnet x.x.y.2
x.x.a.1 NAT router IP x.x.a.2 x.x.y.1
Private network
x.x.y.3
x.x.b.1 NAT router
x.x.b.2
MALC Configuration Guide
183
Configuring IP
Network-based routing with DSL bridges Network-based routing is ideal for adding large numbers of IP addresses. Unlike host-based routing, network based-routing requires numbered IP interfaces on the MALC. In network-based routing with DSL bridges application, each bridge is in the same network as one of the MALC numbered interfaces. Figure 13: Network-based routing with bridges
Bridge x.x.y.2
x.x.y.1/24
IP x.x.y.3
x.x.z.1/24 Bridge x.x.z.2
Network-based routing with DSL routers allows multiple statically assigned addresses per customer. In this application, each remote router is on a subnet with a numbered interface on the MALC. Figure 14: Network-based routing with routers Private network
Public subnet
a.b.c.0/30 a.b.c.1 x.x.y.1 NAT router IP a.b.c.2 Private network
x.x.z.1
d.e.f.0/30 d.e.f.1 NAT router
d.e.f.2
184
MALC Configuration Guide
Applications
Network-based routing with DSL routers Network-based routing with DSL routers allows multiple statically assigned addresses per customer. In this application, each remote router is on a subnet with a numbered interface on the MALC. Figure 15: Network-based routing with routers Private network
Public subnet
a.b.c.0/30 a.b.c.1 x.x.y.1 NAT router IP a.b.c.2 Private network
x.x.z.1
d.e.f.0/30 d.e.f.1 NAT router
d.e.f.2
MALC Configuration Guide
185
Configuring IP
IP filtering IP filtering is typically performed to enhance network security by limiting access between two networks. IP filtering is based on the recognition and selective transmission or blocking of individual IP packets. Packets meeting some criterion are forwarded, and those that fail are dropped. IP filtering is used to block inbound traffic to the management network. Figure 16: IP filtering
Management network
Internet
Filter
Subscribers
IP filtering allows or denies IP packets based on:
•
source IP address
•
destination IP address
IP filtering can be provisioned from the CLI by using the filter command and modifying the ip-interface-record where you wish to apply the filter.
186
MALC Configuration Guide
Applications
Unnumbered IP interfaces Unnumbered IP interfaces reduce the number of IP addresses used by a device. Unnumbered interfaces are just like other point-to-point connections, except a “floating” or virtual IP interface is used as the local IP address in the ip-interface-record. Figure 17: Unnumbered IP interfaces Shared or “floating” IP address Unnumbered IP interface Point to point connection
MALC Configuration Guide
187
Configuring IP
IP provisioning procedures This section includes the following procedures:
•
Configuring a management IP interface on page 188
•
Configuring host-based routing on page 190
•
Configuring network-based routing on page 195
•
Configuring RIP on page 199
•
Configuring static routes on page 199
•
Configuring the MALC as a DHCP server on page 200
•
TOS/COS processing on page 212
•
IP fallback route on page 227 Note: Ethernet interfaces can be addressed as either eth or ethernetcsmacd. The eth abbreviation is used in command output.
Configuring a management IP interface Caution: The Uplink card Ethernet interface must be configured before any other interfaces on the system, even if you do not intend to manage the unit over the Ethernet.
Configuring an Ethernet connection 1
Enter the interface add command with the following options. Refer to the CLI Reference Guide for a complete description of the command options and syntax.
zSH> interface add 1-1-1-0/ethernetcsmacd 10.10.10.10 255.255.255.0 Created ip-interface-record ethernet1/ip
This example:
2
–
creates an ip-interface-record on ethernet1/ip
–
adds host 10.10.10.10.
–
sets netmask as 255.255.255.0.
Verify that the Ethernet connection is active.
zSH> interface show Interface Status Rd/Address Media/Dest Address IfName -------------------------------------------------------------------------------1/1/1/0/ip UP 1 10.10.10.10/24 00:01:47:bb:d5:f1 ethernet1 -------------------------------------------------------------------------------1 interface
188
MALC Configuration Guide
IP provisioning procedures
or ping the host zSH> ping 10.10.10.10 PING 10.10.10.10: 64 data bytes !!!!!
Note: If necessary, you can modify the ip-interface-record on the Uplink card to change the settings created by the interface add command.
Creating a default route The following example creates a default route using the gateway 192.168.8.1 with a cost of 1 (one): route add default 192.168.8.1 1
Verifying the route 1
Use the route show command to verify that the routes were added:
zSH> route show Dest Nexthop Cost Owner -----------------------------------------------------------0.0.0.0/0 192.168.8.1 1 STATICLOW 192.168.8.0/24 1/1/1/0/ip 1 LOCAL
Use the ping command to verify connectivity to the default gateway: zSH> ping 192.168.8.1 PING 192.168.8.1: 64 data bytes !!!! ----172.24.200.254 PING Statistics---4 packets transmitted, 4 packets received round-trip (ms) min/avg/max = 0/0/0
The ping command stops after 5 transmits. 2
Use the route list command to display all configured static routes.
zSH> route list Domain Dest Mask Nexthop IfNum Cost Enable --------------------------------------------------------------------------------1 0.0.0.0 0.0.0.0 172.24.94.254 0 1 enabled 1 172.24.64.0 255.255.255.0 172.25.64.64 0 1 enabled 1 172.24.64.0 255.255.255.0 172.25.64.129 0 2 enabled 1 10.212.0.0 255.255.0.0 10.2.1.254 0 1 enabled
MALC Configuration Guide
189
Configuring IP
Configuring host-based routing Host-based routing interoperates with DSL bridges and routers. The type of AAL5 encapsulation determines interoperability with DSL routers or DSL bridges. LLC encapsulation is used with DSL routers; RFC 1483 encapsulation is used with DSL bridges. Specify LLC encapsulation (llc) in the command line for host-based routing to DSL routers. If no encapsulation type is specified in the command line, RFC 1483 encapsulation (other) is the default. The following table summarizes the configuration tasks for configuring host-based routing: Task
Command
Create an atm-traf-descr.
new atm-traf-descr index Where index is a user-defined value.
Create the IP interface record for the specified unnumbered (floating) interface.
interface add float interfacename IPaddr netmask
Create subnet groups.
dhcp-relay add index
Where interfacename is the name assigned to the IP record and IPaddr and netmask are the IP address and network mask assigned to the interface.
Where index is a user-defined value. Configure a connection to a host.
host add index/type vc vpi/vci td tdvalue other | llc static x.x.x.x | dynamic subnetgroup count This command creates the VCL and IP interface for the host route.
Verify provisioning
host show index/type vc vpi/vci td tdvalue dynamic subnetgroup count
Configuring host-based routing with DSL routers 1
Create an atm-traf-descr for unnumbered interfaces:
zSH> new atm-traf-descr 100 Please provide the following: [q]uit. td_type: -----------------> {atmNoClpNoScr}: td_param1: ---------------> {0}: 106133 td_param2: ---------------> {0}: 38 td_param3: ---------------> {0}: td_param4: ---------------> {0}: td_param5: ---------------> {0}: cac-divider: -------------> {1}: td_service_category: -----> {ubr}: td_frame_discard: --------> {false}: usage-parameter-control: -> {true}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
190
MALC Configuration Guide
IP provisioning procedures
2
Create an floating (unnumbered) IP interface with the desired IP interface record for the IP address that is to be shared for all devices in the host-based routing subnet. The example uses ptm1 as the interface name and 10.0.0.1 as the IP address and 255.0.0.0 as the subnet mask.
zSH> interface add float ptm1 10.0.0.1 255.0.0.0 Created ip-interface-record Zhone1/ip
Note: This is a virtual interface that will share its IP address; binding the IP interface is not necessary. 3
Create a DHCP relay for each customer, use the dhcp-relay command to create a relay agent. The subnet address/mask will be derived from the system's floating IP address, if present, or may be specified NULL for use only with bridged interfaces. If multiple floating IP records are present, the desired / may be specified. The range (or pool) of assignable addresses which that customer can be assigned can be specified in the dhcp-server-subnet profile. zSH> dhcp-relay add 255.0.0.0 172.16.80.20 Created DHCP Relay Agent number 99.
zSH> update dhcp-server-subnet 99 Please provide the following: [q]uit. network: ---------------> {0.0.0.0}: 10.0.0.0 netmask: ---------------> {0.0.0.0}: 255.0.0.0 domain: ----------------> {0}: 1 range1-start: ----------> {0.0.0.0}: 10.0.0.10 range1-end: ------------> {0.0.0.0}: 10.0.0.20 range2-start: ----------> {0.0.0.0}: range2-end: ------------> {0.0.0.0}: range3-start: ----------> {0.0.0.0}: range3-end: ------------> {0.0.0.0}: range4-start: ----------> {0.0.0.0}: range4-end: ------------> {0.0.0.0}: default-lease-time: ----> {-1}: min-lease-time: --------> {-1}: max-lease-time: --------> {-1}: boot-server: -----------> {0.0.0.0}: bootfile: --------------> {}: default-router: --------> {0.0.0.0}: 10.0.0.1 primary-name-server: ---> {0.0.0.0}: secondary-name-server: -> {0.0.0.0}: domain-name: -----------> {}: subnetgroup: -----------> {0}: 1 This number does not have to match the subnet index stickyaddr: ------------> {enable}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
MALC Configuration Guide
191
Configuring IP
4
Issue the host add command to create the IP interface, ATM VCL, and IP address for individual subscribers. Also assigns VLAN and SLAN settings. The host add and host delete commands, and may be replaced with brackets containing numbers in series and/or (dash-separated) ranges; may be replaced with wildcard '*' for all ports on the card. The following example adds dynamically assigned hosts:
zSH> host add 1-11-1-0/adsl vc 0/35 txtd 100 rxtd 1 tpid 0x8200 vlan 100 slan 10 cos 2 scos 3 llc dynamic 1 3
This example: –
creates an ip-interface-record on 1-11-1-0/adsl
–
creates an atm-vcl with VPI/VCI=0/35 and LLC encapsulation of AAL5 data, which accommodates DSL routers
–
creates an ATM cross connect from the virtual interface on the Uplink card to the designated slot card
–
specifies the TAG protocol identifier (TPID) to identify the type of VLAN used.
–
assigns VLAN ID 100.
–
assigns SLAN ID 10.
–
assigns COS value of 2 to VLAN 100.
–
assigns COS value of 3 to SLAN 2.
–
uses atm-traf-descr 100 for the transmit and atm-traf-descr 1 for the receive sides of the connection since ADSL is an asymmetrical connection
–
adds 3 host entries that will have their addresses assigned dynamically as defined by subnetgroup 1. Note: Hosts that already have DHCP-assigned addresses will need to renew those leases after the DHCP change. This is done by rebooting the host.
The following example adds a statically assigned host: zSH> host add 1-11-2-0/adsl vc 0/35 td 1 llc static 10.10.10.1
This example:
192
MALC Configuration Guide
–
creates an ip-interface-record on 1-11-2-0/adsl
–
creates an atm-vcl with VPI/VCI=0/35 and LLC encapsulation of AAL5 data
–
creates an ATM cross connect from the virtual interface on the Uplink card to the designated slot card
–
uses atm-traf-descr 1 for the connection
IP provisioning procedures
– 5
adds 1 host entry IP address 10.0.0.1.
Verify that hosts have been added:
zSH> host show Rd/Address Interface Group T Host Address -------------------------------------------------------------------------------1 10.0.0.1 1-11-1-0-adsl-0-35 0/32 1 D D D
6
To find the other end of the ATM cross connect: zSH> find-matching-data ATM 1-11-1-0-adsl/atm 0 35 VCL 1-11-1-0-adsl/atm 0 35 is used in atm-cc 1 The far end of this cross connect is 1-1-1-0-propvirtual/atm 0 32
7
To see the ATM virtual interfaces created by the host add command: zSH> list atm-vcl atm-vcl 1-11-1-0-adsl/atm/0/35 atm-vcl 1-1-1-0-propvirtual/atm/0/32 2 entries found.
8 zSH> get atm-cc 1 cc-index: ------> low-if-index: --> low-vpi: -------> low-vci: -------> high-if-index: -> high-vpi: ------> high-vci: ------> admin-status: --> handle-id: ----->
To see the ATM cross connect created:
{1} {1-1-1-0-propvirtual/atm} virtual interface on the Uplink card {0} {32} {1-11-1-0-adsl/atm} the slot card {0} {35} {up} {handle_1}:
Configuring host-based routing with DSL bridges 1
Create an atm-traf-descr for unnumbered interfaces:
zSH> new atm-traf-descr 100 Please provide the following: [q]uit. td_type: -----------------> {atmNoClpNoScr}: td_param1: ---------------> {0}: 106133 td_param2: ---------------> {0}: 38 td_param3: ---------------> {0}: td_param4: ---------------> {0}: td_param5: ---------------> {0}: cac-divider: -------------> {1}: td_service_category: -----> {ubr}: td_frame_discard: --------> {false}: usage-parameter-control: -> {true}: ....................
MALC Configuration Guide
193
Configuring IP
Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
2
Create an floating (unnumbered) IP interface the desired IP interface record for the IP address that is to be shared for all devices in the host-based routing subnet. The example uses ptm1 as the interface name and 10.0.0.1 as the IP address and 255.0.0.0 as the subnet mask.
zSH> interface add float ptm1 10.0.0.1 255.0.0.0 Created ip-interface-record Zhone1/ip
Note: This is a virtual interface that will share its IP address; binding the IP interface is not necessary. 3
Create a DHCP relay for each customer, use the dhcp-relay command to create a relay agent. The subnet address/mask will be derived from the system's floating IP address, if present, or may be specified NULL for use only with bridged interfaces. If multiple floating IP records are present, the desired / may be specified. The range (or pool) of assignable addresses which that customer can be assigned can be specified in the dhcp-server-subnet profile. zSH> dhcp-relay add Operation completed successfully.
For advanced DHCP setting changes, edit the dhcp-server-subnet profile. zSH> update dhcp-server-subnet 99 Please provide the following: [q]uit. network: ---------------> {0.0.0.0}: 10.0.0.0 netmask: ---------------> {0.0.0.0}: 255.0.0.0 domain: ----------------> {0}: 1 range1-start: ----------> {0.0.0.0}: 10.0.0.10 range1-end: ------------> {0.0.0.0}: 10.0.0.20 range2-start: ----------> {0.0.0.0}: range2-end: ------------> {0.0.0.0}: range3-start: ----------> {0.0.0.0}: range3-end: ------------> {0.0.0.0}: range4-start: ----------> {0.0.0.0}: range4-end: ------------> {0.0.0.0}: default-lease-time: ----> {-1}: min-lease-time: --------> {-1}: max-lease-time: --------> {-1}: boot-server: -----------> {0.0.0.0}: bootfile: --------------> {}: default-router: --------> {0.0.0.0}: 10.0.0.1 primary-name-server: ---> {0.0.0.0}: secondary-name-server: -> {0.0.0.0}: domain-name: -----------> {}: subnetgroup: -----------> {0}: 1 This number does not have to match the subnet index stickyaddr: ------------> {enable}: ....................
194
MALC Configuration Guide
IP provisioning procedures
Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
4
Issue the host add command to create the IP interface, ATM VCL, and IP address for individual subscribers. The host add,and host delete commands, and may be replaced with brackets containing numbers in series and/or (dash-separated) ranges; may be replaced with wildcard '*' for all ports on the card. The following example adds dynamically assigned hosts:
zSH> host add 1-11-1-0/adsl vc 0/35 txtd 100 rxtd 1 dynamic 1 3
This example: –
creates an ip-interface-record on 1-11-1-0/adsl
–
creates an atm-vcl with VPI/VCI=0/35 and RFC 1483 encapsulation of AAL5 data, which accommodates DSL bridges
–
creates an ATM cross connect from the virtual interface on the Uplink card to the designated slot card
–
uses atm-traf-descr 100 for the transmit and atm-traf-descr 1 for the receive sides of the connection since ADSL is an asymmetrical connection
–
adds 3 host entries that will have their addresses assigned dynamically as defined by subnetgroup 1. Note: Hosts that already have DHCP-assigned addresses will need to renew those leases after the DHCP change. This is done by rebooting the host.
Configuring network-based routing Similar to host-based routing, network-based routing interoperates with DSL bridges and routers. The type of AAL5 encapsulation determines interoperability with DSL routers or DSL bridges. LLC encapsulation is used with DSL routers; RFC 1483 encapsulation is used with DSL bridges. Specify bridge in the command line to connect to DSL bridges. If no encapsulation type is specified in the command line, LLC encapsulation (llc) is the default. Refer to the CLI Reference Guide for a complete description of the command options and syntax.
MALC Configuration Guide
195
Configuring IP
The following table summarizes the configuration tasks for adding network-based routes. Task
Command
Create an atm-traf-descr.
new atm-traf-descr index Where index is a user-defined value.
Configure a connection to routed subnets.
interface add index/type vc vpi/vci td tdvalue | txtd tdvalue rxtd tdvalue llc | other IPaddress This command creates the VCL and IP interface for the host route.
Verify provisioning
interface show
Configuring network-based routing with DSL routers 1
Create an atm-traf-descr for unnumbered interfaces:
zSH> new atm-traf-descr 100 Please provide the following: [q]uit. td_type: -----------------> {atmNoClpNoScr}: td_param1: ---------------> {0}: 106133 td_param2: ---------------> {0}: 38 td_param3: ---------------> {0}: td_param4: ---------------> {0}: td_param5: ---------------> {0}: cac-divider: -------------> {1}: td_service_category: -----> {ubr}: td_frame_discard: --------> {false}: usage-parameter-control: -> {true}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
2
Issue the interface add command to create the IP interface, ATM VCL, and IP address allocation:
zSH> interface add 1-5-1-0/adsl vc 0/35 td 1 10.10.10.10 255.255.255.0 Created ip-interface-record 1-5-1-0-adsl-0-35/ip
This example:
3
196
MALC Configuration Guide
–
creates an ip-interface-record on 1-5-1-0/adsl
–
creates an atm-vcl with VPI/VCI=0/35 and LLC encapsulation of AAL5 data, which accommodates DSL routers
–
uses atm-traf-descr 1 for transmit and receive sides of the connection
–
creates an ATM cross connect from the virtual interface on the Uplink card to the designated slot card
–
adds IP address 10.0.0.1 with a subnetwork defined by the netmask.
Verify that interfaces have been added:
IP provisioning procedures
zSH> interface show Interface Status Rd/Address Media/Dest Address IfName -------------------------------------------------------------------------------1/1/1/0/ip DOWN 1 10.10.10.10/24 0/36 1-5-1-0-adsl-0-35 --------------------------------------------------------------------------------
4
To find the other end of the ATM cross connect:
zSH> find-matching-data ATM 1-5-1-0-adsl/atm 0 35 VCL 1-5-1-0-adsl/atm 0 35 is used in atm-cc 5 The far end of this cross connect is 1-1-1-0-propvirtual/atm 0 36
5
To see the ATM virtual interfaces created by the interface add command: zSH> list atm-vcl atm-vcl 1-5-1-0-adsl/atm/0/35 atm-vcl 1-1-1-0-propvirtual/atm/0/36 2 entries found.
6 zSH> get atm-cc 5 cc-index: ------> low-if-index: --> low-vpi: -------> low-vci: -------> high-if-index: -> high-vpi: ------> high-vci: ------> admin-status: --> handle-id: ----->
To see the ATM cross connect created:
{5} {1-1-1-0-propvirtual/atm} virtual interface on the Uplink card {0} {36} {1-5-1-0-adsl/atm} the slot card {0} {39} {up} {handle_5}
Configuring network-based routing with DSL bridges 1
Create an atm-traf-descr for unnumbered interfaces:
zSH> new atm-traf-descr 100 Please provide the following: [q]uit. td_type: -----------------> {atmNoClpNoScr}: td_param1: ---------------> {0}: 106133 td_param2: ---------------> {0}: 38 td_param3: ---------------> {0}: td_param4: ---------------> {0}: td_param5: ---------------> {0}: cac-divider: -------------> {1}: td_service_category: -----> {ubr}: td_frame_discard: --------> {false}: usage-parameter-control: -> {true}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
2
Issue the interface add command to create the IP interface, ATM VCL, and IP address allocation:
MALC Configuration Guide
197
Configuring IP
zSH> interface add 1-5-1-0/adsl vc 0/35 td 1 other 10.10.10.10 255.255.255.0 Created ip-interface-record 1-5-1-0-adsl-0-35/ip
This example:
3
–
creates an ip-interface-record on 1-5-1-0/adsl
–
creates an atm-vcl with VPI/VCI=0/35 and RFC 1483 encapsulation of AAL5 data, which accommodates DSL bridges
–
uses atm-traf-descr 1 for transmit and receive sides of the connection
–
creates an ATM cross connect from the virtual interface on the Uplink card to the designated slot card
–
adds IP address 10.0.0.1 with a subnetwork defined by the netmask.
Verify that interfaces have been added:
zSH> interface show Interface Status Rd/Address Media/Dest Address IfName -------------------------------------------------------------------------------1/1/1/0/ip UP 1 10.10.10.10/24 0/35 multipoint 1-5-1-0-adsl-0-35 --------------------------------------------------------------------------------
4
To find the other end of the ATM cross connect:
zSH> find-matching-data ATM 1-5-1-0-adsl/atm 0 35 VCL 1-5-1-0-adsl/atm 0 35 is used in atm-cc 5 The far end of this cross connect is 1-1-1-0-propvirtual/atm 0 36
5
To see the ATM virtual interfaces created by the interface add command: zSH> list atm-vcl atm-vcl 1-5-1-0-adsl/atm/0/35 atm-vcl 1-1-1-0-propvirtual/atm/0/36 2 entries found.
6 zSH> get atm-cc 5 cc-index: ------> low-if-index: --> low-vpi: -------> low-vci: -------> high-if-index: -> high-vpi: ------> high-vci: ------> admin-status: --> handle-id: ----->
198
MALC Configuration Guide
To see the ATM cross connect created:
{5} {1-1-1-0-propvirtual/atm} virtual interface on the Uplink card {0} {36} {1-5-1-0-adsl/atm} the slot card {0} {39} {up} {handle_5}
IP provisioning procedures
Configuring RIP RIP behavior for the system as a whole is configured in the rip-global-config profile. Each IP interface is then configured for RIP using the rip command. Currently, the MALC supports RIP v1 and v2. Note that the only routing domain currently supported is domain 1.
Configuring RIP global defaults The following example configures RIP global behavior on the MALC: 1
Enable RIP for the system as a whole: zSH> rip enable
2
To enable receipt of RIP version 1 or version 2 advertisements on an interface, use the rip command and specify the interface and the type of advertisements to receive: zSH> rip interface 172.16.92.191 listen v1v2
3
To enable transmission of RIP advertisements on an interface: a
zSH> rip interface 172.16.92.191 talk v2
or b
zSH> rip interface 172.16.92.191 talk v1compat
Configuring static routes Use the route command to add or delete static routes. The MALC supports both destination and Source Address Based Routing (SABR). SABR adds flexibility to route planning for network administrators and allows the MALC to forward outbound VoIP SIP traffic based on a specific source IP address of a data packet instead of the destination IP address.With SABR routing, the source IP address or subnet address of a data packet is examined before packet forwarding. If the device finds a matching source route in the source routing table, the packet is forwarded according to the matched source route. If the device does not find a matching source route, destination routing is performed based on the destination routing table and if necessary the configured default route. Note the following about SABR support on the MALC:
•
SABR routing is only supported on AAL5 VCLs using LLC encapsulation.
•
The route, ping and traceroute commands support SABR.
•
SABR is only supported for VoIP SIP.
MALC Configuration Guide
199
Configuring IP
Adding routes To add static routes, use the route add command. The command uses the following syntax: route [source] add destination mask next-hop cost
Note: The word default can be substituted for a 0.0.0.0 destination and mask. The following example creates a network route to 192.178.21.0 using the gateway 192.172.16.1: route add 192.178.21.0 255.255.255.0 192.178.16.1 1
The following example creates a default route using the gateway 192.172.16.1: route add default 192.178.16.1 1
The following example creates a SABR route to 198.168.1.1 on the interface 198.168.1.101. The interface is the name of the outbound (egress) interface for this route (minus the /ip suffix). zSH> route add source 198.168.1.1 255.255.255.255 198.168.1.101 1 uplink1-0-36
Configuring the MALC as a DHCP server The MALC DHCP supports the following types of DHCP configurations:
•
Dynamic address allocation, where the server chooses and allocates an IP address with a finite lease. By default, the MALC will attempt to assign the same address (if available) to a device on lease renewal. This default can be changed to force a new address to be assigned.
•
Static address allocation, where the server allocates the same IP address every time a device connects to the network.
DHCP server profiles and scope Use the following profiles to configure the devices as a DHCP server:
200
MALC Configuration Guide
•
dhcp-server-options—Configures a default profile that is used to generate default configurations for networks that are not explicitly configured. See Setting DHCP server options on page 201 for more information.
•
dhcp-server-subnet—Defines options for a specific network that is being managed by the DHCP server. Settings in the dhcp-server-subnet record override the default address pool set up by the dhcp-server-options record. See Creating DHCP server subnet options on page 203 for more information.
IP provisioning procedures
•
dhcp-server-group—Defines options for a set of clients in a given domain. Inclusion of a given client into the group is based on a substring match of either the client’s DHCP vendor class identifier, its DHCP client identifier values, or both. The scope of a group object always overrides those of a subnet object for any DHCP client lease. See Advanced DHCP applications on page 214 for more information.
•
dhcp-server-host—Defines options for a specific host within a given domain. See Advanced DHCP applications on page 214 for more information.
•
ip-interface-record—enables DHCP on the interface. The IP address defined in the ip-interface-record is used to determine the DHCP address pool for the attached network. See Enabling a DHCP server on page 205 for more information.
The DHCP server looks for configuration settings in order from the most specific record (the dhcp-server-host) to the most general (the dhcp-server-options record). It uses parameter settings in the following order: 1. dhcp-server-host 2. dhcp-server-group 3. dhcp-server-subnet 4. dhcp-server-options If a parameter is set in multiple profiles (for example, lease times or default routers), the MALC uses the settings that are in the most specific record. This means that the DHCP server could use parameter settings in multiple records (if, for example, all client lease times were set in the dhcp-server-options record, and address ranges were set in the dhcp-server-subnet records.) If only the dhcp-server-options record exists, the MALC uses those settings as the default for all DHCP server interfaces. For information about logging DHCP requests, see DHCP logging on page 237.
Setting DHCP server options At startup, the MALC creates a default dhcp-server-options record. This profile defines global options for the MALC DHCP server. The following example shows the dhcp-server-options profile with its default values: zSH> get dhcp-server-options 0 Please provide the following: [q]uit. lease-time: -----> {43200}: min-lease-time: -> {0}: max-lease-time: -> {86400}: reserve-start: --> {5}: reserve-end: ----> {5}: restart: --------> {no}:
MALC Configuration Guide
201
Configuring IP
The dhcp-server-options profile supports the following parameters (all others should be left at their default values): Parameter
Description
lease-time
The global default time in seconds that will be assigned to a DHCP lease if the client requesting the lease does not request a specific expiration time.
min-lease-time
The minimum expiration time in seconds that will be assigned to a DHCP lease by the server, regardless of the value specified by a client. Values: -1 to 2147483647 -1 indicates the parameter should be ignored. Default: 0
max-lease-time
The maximum time in seconds that will be assigned to a lease regardless of the value specified by a client. Values: -1 to 2147483647. -1 indicates the parameter should be ignored. Default: 86400
reserve-start
The default number of IP addresses, at the beginning of the MALC subnet IP address space, that are reserved by the DHCP server. To override this default, create a specific subnet rule for each subnet that needs to be handled differently.
reserve-end
The default number of IP addresses at the end of the MALC ‘s subnet IP address space that are reserved by the DHCP server. To override this default, create a specific subnet rule for each subnet that needs to be handled differently.
The following example changes the dhcp-server-options record to specify that each DHCP server reserve the first 10 addresses and the last 10 addresses in a network and does not include them in the DHCP server address pool. zSH> update dhcp-server-options 0 Please provide the following: [q]uit. lease-time: -----> {43200}: min-lease-time: -> {0}:
202
MALC Configuration Guide
IP provisioning procedures
max-lease-time: -> {86400}: reserve-start: --> {5}: 10 reserve-end: ----> {5}: 10 restart: --------> {no}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
In this example, if a DHCP server on the 192.168.9.0 network reserved the first 10 addresses and last 10 addresses, it would assign addresses from 192.168.9.11 to 192.168.9.244.
Creating DHCP server subnet options The dhcp-relay command enables you to create, modify, delete and show DHCP relay agents. The subnet address/mask will be derived from the system's floating IP address, if present, or may be specified NULL for use only with bridged interfaces. If multiple floating IP records are present, the desired / may be specified. The dhcp-server-subnet profile allows you to edit the options for a specific network that is being managed by the DHCP server. All subnets within a routing domain must be unique, so a given subnet object will provide options for exactly one connected network. The dhcp-server-subnet profile supports the following parameters (all others should be left at their default values): Parameter
Description
network
The IP network address of this subnet.
netmask
The subnet mask associated with the IP interface. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.
domain
The routing domain to which this subnet, group, or host parameter applies.
range1-start, range2-start, range3-start, range4-start
The starting IP address of an address pool in this subnet. If either the start or end range has a value of 0 then the entire address pool is ignored.
range1-end, range2-end, range3-end, range4-end
The ending IP address of an address pool in this subnet. If either the start or end range has a value of 0, then the entire address pool is ignored.
default-lease-time
The default time, in seconds assigned to a lease if the client requesting the lease does not request a specific expiration time.
min-lease-time
See description in dhcp-server-options profile.
max-lease-time
See description in dhcp-server-options profile.
MALC Configuration Guide
203
Configuring IP
Parameter
Description
boot-server
The IP address of the server from which the initial boot file (specified in the bootfile parameter) is to be loaded.
bootfile
The name of the initial boot file loaded by the client. The filename should be recognizable to the file transfer protocol that the client will be using to load the file.
default-router
The IP address of the client default gateway.
primary-name-server
The IP address of the primary domain name server that the client should use for DNS resolution.
secondary-name-server
The IP address of the secondary domain name server that the client should use for DNS resolution.
domain-name
The name of the DNS domain.
subnetgroup
A number which indicates which DHCP subnet group this pool is a member of. A value of 0 (default) indicates that the subnet is not a member of any group.
stickyaddr
The DHCP server attempts to assign the same IP address to the same host, if possible, based on hardware address. Values: disable enable Default: enable
The following example defines a DHCP server subnet profile that is set up as follows:
•
Defines a single DHCP address pool with 11 addresses.
•
Defines a default router.
•
Defines a boot server and a boot filename.
•
Defines a domain name.
•
Defines two DNS servers.
•
Uses the minimum, maximum, and default lease time (by accepting the default settings for the default-lease-time, min-lease-time, and max-lease-time).
zSH> new dhcp-server-subnet 12 Please provide the following: [q]uit. network: ---------------> {0.0.0.0}: 192.168.1.0 netmask: ---------------> {0.0.0.0}: 255.255.255.0 domain: ----------------> {0}: 1 range1-start: ----------> {0.0.0.0}: 192.168.1.10
204
MALC Configuration Guide
IP provisioning procedures
range1-end: ------------> {0.0.0.0}: 192.168.1.20 range2-start: ----------> {0.0.0.0}: range2-end: ------------> {0.0.0.0}: range3-start: ----------> {0.0.0.0}: range3-end: ------------> {0.0.0.0}: range4-start: ----------> {0.0.0.0}: range4-end: ------------> {0.0.0.0}: default-lease-time: ----> {-1}: min-lease-time: --------> {-1}: max-lease-time: --------> {-1}: boot-server: -----------> {0.0.0.0}: 192.168.1.55 bootfile: --------------> {}: filename.bin default-router: --------> {0.0.0.0}: 192.168.1.1 primary-name-server: ---> {0.0.0.0}: 192.168.8.21 secondary-name-server: -> {0.0.0.0}: 201.23.20.2 domain-name: -----------> {}: zhone.com subnetgroup: -----------> {0}: stickyaddr: ------------> {enable}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Enabling a DHCP server Modify the following parameters in the ip-interface-record to enable DHCP server (all others should be left at their default values): Parameter
Description
dhcp
Indicates whether this interface is a DHCP client, a DHCP server, both, or neither. Values: none client server both Default: none
address
The IP address of LAN port.
The following example enables the DHCP server on an IP-enabled interface in MALC shelf 1, slot 1, port 2, and subport 0. zSH> update ip-interface-record 1/1/2/0/ip Please provide the following: [q]uit. vpi: ---------------> {0}: vci: ---------------> {0}: rdindex: -----------> {1}: dhcp: --------------> {none}: ** read-only ** addr: --------------> {172.24.200.162}: netmask: -----------> {255.255.255.0}:
MALC Configuration Guide
205
Configuring IP
bcastaddr: ---------> {172.24.200.255}: destaddr: ----------> {0.0.0.0}: farendaddr: --------> {0.0.0.0}: mru: ---------------> {1500}: reasmmaxsize: ------> {0}: ingressfiltername: -> {}: egressfiltername: --> {}: pointtopoint: ------> {no}: mcastenabled: ------> {yes}: ipfwdenabled: ------> {yes}: mcastfwdenabled: ---> {yes}: natenabled: --------> {no}: bcastenabled: ------> {yes}: ingressfilterid: ---> {0}: egressfilterid: ----> {0}: ipaddrdynamic: -----> {static}: dhcpserverenable: --> {false}: true subnetgroup: -------> {0}: unnumberedindex: ---> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
206
MALC Configuration Guide
IP provisioning procedures
DHCP relay The MALC supports DHCP relay. In DHCP relay scenarios, the MALC serves as a DHCP relay agent that forwards broadcast DHCP discover and DHCP request packets to an external DHCP server. It then forwards the unicast DHCP offer and DHCP ack/nak replies to the requesting DHCP host. DHCP broadcast messages do not, by default, cross the router interfaces. To solve the problem of DHCP broadcast messages on multiple subnets, 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 downstream segments. Figure 18: DHCP relay DHCP server
DHCP client
DHCP relay agent
Note the following requirements for DHCP relay:
•
The external DHCP server must be configured to assign addresses on the same subnet as the floating IP address used by the remote device.
•
The external DHCP server must be configured with a static route for the remote device’s subnet back to the MALC on which the relay agent is running. (The DHCP server will send DHCP unicast packets to the relay agent’s address, which is the first one in the subnet.)
•
A separate DHCP server can be specified per subnet.
Specifying a primary and alternate external DHCP server From the dhcp-relay CLI macro command you can add, delete or modify the primary DHCP server or an alternate DHCP server. The external-server and external-server-alt fields in the dhcp-server-subnet profile hold the IP addresses of the DHCP servers. The alternate DHCP server will be forwarded DHCP requests as well as the primary DHCP server. dhcp-relay [] alt
MALC Configuration Guide
207
Configuring IP
Note: When using the alternate DHCP server option, you should configure your DHCP servers in a mirrored configuration so they are communicating with each other and that both are not simultaneously giving out addresses to the same device. You can only add an alternate DHCP server if the primary DHCP server (external-server field) contains an address.
Specifying an external and alternate DHCP server in the profile Use the dhcp-relay command to configure, modify, delete and show the DHCP relay. The subnet address/mask will be derived from the system's floating IP address, if present, or may be specified NULL for use only with bridged interfaces. If multiple floating IP records are present, the desired / may be specified. The dhcp-server-subnet profile is available for advanced DHCP configuration changes. The following parameter has been added to this profile: Parameter
Description
external-server
Enable a primary external subnet server in order to support DHCP relay agent. Default: 0.0.0.0
external-server-alt
Enable an alternate external subnet server in order to support DHCP relay agent. Default: 0.0.0.0
To specify a primary and alternate external DHCP server in the dhcp-server-subnet profile: 1
Create a dhcp-server-subnet profile and specify the IP address of the external server: zSH> new dhcp-server-subnet 1 Please provide the following: [q]uit.
208
MALC Configuration Guide
network: --------------->
{172.24.41.0}:
netmask: --------------->
{255.255.255.0}:
domain: ---------------->
{1}:
range1-start: ---------->
{172.24.41.11}:
range1-end: ------------>
{172.24.41.100}:
range2-start: ---------->
{0.0.0.0}:
range2-end: ------------>
{0.0.0.0}:
range3-start: ---------->
{0.0.0.0}:
IP provisioning procedures
range3-end: ------------>
{0.0.0.0}:
range4-start: ---------->
{0.0.0.0}:
range4-end: ------------>
{0.0.0.0}:
default-lease-time: ---->
{-1}:
min-lease-time: -------->
{-1}:
max-lease-time: -------->
{-1}:
boot-server: ----------->
{172.24.38.102}:
bootfile: --------------> etherboot-I3M-i.img}:
{i3micro/
default-router: -------->
{172.24.41.254}:
primary-name-server: --->
{172.24.38.102}:
secondary-name-server: ->
{0.0.0.0}:
domain-name: ----------->
{nat.myrio.net}:
subnetgroup: ----------->
{1}:
stickyaddr: ------------> external-server: -------> external-server-alt: --->
{enable}: {0.0.0.0}: 172.16.88.71 {0.0.0.0}: 172.16.89.25
.................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
2
Create a host route and specify the subnet group. For example: zSH> host add 1-1-1-0/adsl vc 0/36 td 200 dynamic 1 1
This example specifies that the host route over the specified ATM interface uses dynamic addressing and subnet group number 1.
DHCP relay examples The following examples show how to add, delete, modify and display the dhcp-server-subnet profile which configures the dhcp-relay service. Command: dhcp-relay add
Add a dhcp-server-subnet profile with a primary and alternate server. See DHCP relay, page 207 for the default dhcp-server-subnet profile. zSH> dhcp-relay add 1 192.168.1.1 alt 192.168.1.3 Created DHCP Relay Agent number 1
Command: dhcp-relay show
MALC Configuration Guide
209
Configuring IP
Show the existing dhcp-relay agents, their subnets, network mask and primary and external dhcp server IP addresses. zSH> dhcp-relay show subnetgroup external-server alternate-server network_address/mask --------------------------------------------------------------------------1 192.168.1.1 255.255.255.0
192.168.1.3
1.1.1.0/
Command dhcp-relay delete
Delete a dhcp-relay by the dhcp-server-subnet ID. You can find the subnet group by using the dhcp-relay show command. zSH> dhcp-relay delete 1 Deleted DHCP Relay Agent number 1
Verifying the dhcp-server-subnet profile
The dhcp-relay add command creates a dhcp-server-subnet profile with default parameters — network, subnet mask (netmask) and default gateway (default-router) — and the subnet ID, primary and alternate dhcp-servers, all shown in bold. zSH> get dhcp-server-subnet 1 dhcp-server-subnet
210
MALC Configuration Guide
1
network: --------------->
{1.1.1.0}
netmask: --------------->
{255.255.255.0}
domain: ---------------->
{0}
range1-start: ---------->
{0.0.0.0}
range1-end: ------------>
{0.0.0.0}
range2-start: ---------->
{0.0.0.0}
range2-end: ------------>
{0.0.0.0}
range3-start: ---------->
{0.0.0.0}
range3-end: ------------>
{0.0.0.0}
range4-start: ---------->
{0.0.0.0}
range4-end: ------------>
{0.0.0.0}
default-lease-time: ---->
{-1}
min-lease-time: -------->
{-1}
IP provisioning procedures
max-lease-time: -------->
{-1}
boot-server: ----------->
{0.0.0.0}
bootfile: -------------->
{}
default-router: -------->
{1.1.1.0}
primary-name-server: --->
{0.0.0.0}
secondary-name-server: ->
{0.0.0.0}
domain-name: ----------->
{}
subnetgroup: ----------->
{1}
stickyaddr: ------------>
{enable}
external-server: ------->
{192.168.1.1}
external-server-alt: --->
{192.168.1.3}
Command: dhcp-relay modify The dhcp-relay modify command uses the same parameters as the dhcp-relay command, changing only the identified parameters. zSH> dhcp-relay modify 1 alt 192.168.1.12 Updated DHCP Relay Agent number 1
To modify parameters of the dhcp-server-subnet profile which are not in the dhcp-relay command, such as setting the default-router, give the update dhcp-server subnet command with the appropriate index, then give carriage returns until you are at the appropriate parameter (such as default-router) enter the appropriate information, carriage return until the end of the profile, then enter “s” to save the profile.
MALC Configuration Guide
211
Configuring IP
TOS/COS processing The MALC supports the marking and remarking of TOS values in IP packets and COS values in Ethernet VLAN headers as defined by IETF RFC1349 and IEEE 802.1p respectively. The configured TOS and COS levels specify the packet priority and queueing methods used to transport the packet through the IP and Ethernet networks. The MALC sets and transports the TOS/COS values, while the switches and routers connected to the MALC perform the queuing services and packet QOS processing. Note: TOS bits are not altered for VoIP Real Time Transport Protocol (RTP) packets, which have their own TOS bit settings set in the voip-server-entry profile regardless of the TOS setting on the outgoing interface. This service enables you to:
•
Add IP packet TOS values and VLAN header COS values to packets originating from the MALC.
•
Overwrite existing IP packet TOS values and VLAN header COS values that are transported through the MALC.
•
Leave existing IP packet TOS values and VLAN header COS values unchanged in all packets.
802.1p priority queues Multi-media Traffic Management (MTM), is a rules-based policy enforcement mechanism for SLMS systems. The MALC MTM is used to mark packet priorities and service queues. The MALC will support 4 (four) strict priority queues (served until emptied) as part of the MALC's implementation of the MTM feature set for QoS. New line cards supporting 802.1p priority queues are: MALC-ACTIVE-ETH-10, MALC-GPON-SC1, MALC-VDSL2-24 DMT, MALC-EFM-SHDSL-24, and MALC-EFM-T1/E1-24. Existing line cards supporting 802.1p priority queues are: MALC-ADSL-48B, MALC-ADSL-48A, MALC-ADSL+POTS-TDM-48A-2S, MALC-ADSL+POTS-TDM/PKT-48A-2S, MALC-ADSL-48A/M, MALC-ADSL+POTS-PKT-48A/M-2S, MALC-ADSL+POTS-TDM-48-2S
Fields in IP header IP packets have a TOS byte in their headers that contains information about relative priority. The TOS byte is divided into two fields called IP Precedence and TOS. The IP Precedence field contains a 3-bit priority designation. Most
212
MALC Configuration Guide
IP provisioning procedures
normal traffic has an IP Precedence value of zero. Higher values in this field indicate that traffic is more important and that it requires special treatment. IP Precedence values greater than 5 are reserved for network functions.
Fields in the VLAN header The VLAN header in Ethernet packets contains a COS field for queueing priority or Class of Service (COS) values based on eight (0-7) levels of service. This field contains information about how the traffic should be forwarded. The MALC supports basic COS marking and remarking without any queue servicing options. Packets marked or remarked based on a configurable profile to let the system know which bits use which queue.
TOS/COS parameters The following parameters in the IP interface record are used for TOS and COS support. Parameter
Description
tosOption
Specifies how to handle the IP TOS precedence and VLAN header COS bits. Values: Disable Leave any existing TOS and COS values unchanged. The default setting. Originate Replace the current TOS and COS values in all packets originating from the current device. TOS and COS values in packets that are transported through (not originating on) this MALC are not affected. The TOS value is specified in the tosCos field. The COS value is specified in the vlanCOS field. All Replace the current TOS and COS values in all packets originating and transported through this device. The TOS value is specified in the tosCos field. The COS value is specified in the vlanCOS field.This setting has no affect on VoIP RTP packets originated from this interface.
tosCOS
Specifies the value loaded into the TOS precedence bits in the IP header for packets originating and transported through the current device. Value range is 0 to 7. Default is 0.
vlanCOS
Specifies the value loaded into the COS field of the VLAN header for packets originating and transported through the current device. Value range is 0 to 7. Default is 0.
To display the TOS/COS settings in the ip-interface-record profile, enter the show ip-interface-record command. zSH> show ip-interface-record vpi:---------------> {0} vci:---------------> {0}
MALC Configuration Guide
213
Configuring IP
rdindex:-----------> dhcp:--------------> addr:--------------> netmask:-----------> bcastaddr:---------> destaddr:----------> farendaddr:--------> mru:---------------> reasmmaxsize:------> ingressfiltername:-> egressfiltername:--> pointtopoint:------> mcastenabled:------> ipfwdenabled:------> mcastfwdenabled:---> natenabled:--------> bcastenabled:------> ingressfilterid:---> egressfilterid:----> ipaddrdynamic:-----> unnumbered dhcpserverenable:--> subnetgroup:-------> unnumberedindex:---> mcastcontrollist:--> vlanid:------------> maxVideoStreams:---> tosOption:---------> tosCOS:------------> vlanCOS:----------->
{0 - 2147483647} none client server both {0 - -1} {0 - -1} {0 - -1} {0 - -1} {0 - -1} {0 - 2147483647} {0 - 65535} {33} {33} no yes no yes no yes no yes no yes no yes {0 - 2147483647} {0 - 2147483647} static ppp dhcpclient true false {0 - 2147483647} {0 - 2147483647} {264} {0 - 4095} {0 - 210} disable originate {0 - 7 {0 - 7}
all
Note: TOS bits are not altered for VoIP Real Time Transport Protocol (RTP) packets, which have their own TOS bit settings set in the voip-server-entry profile regardless of the TOS setting on the outgoing interface.
Advanced IP provisioning procedures The following advanced IP procedures are supported on the MALC:
•
Advanced DHCP applications on page 214
•
Configuring DNS resolver on page 216
•
IP Service Level Agreement (IPSLA) on page 218
Advanced DHCP applications This section explains how to configure more advanced DHCP applications. It includes the following sections:
•
214
MALC Configuration Guide
Creating dhcp-server-group profile on page 215
IP provisioning procedures
•
Creating dhcp-server-host profile on page 215
Creating dhcp-server-group profile The dhcp-server-group defines options for a set of clients in a given domain. Inclusion of a given client into the group is based on a substring match of either the client’s DHCP vendor class identifier, its DHCP client identifier values, or both. The scope of a group object always overrides those of a subnet object for any DHCP client lease. Modify the following parameters to create a new dhcp-server-group profile: Parameter
Description
name
The DHCP server group name.
vendor-match-string
The vendor class identifier match string that determines which clients should be placed in the group.
client-match-string
Client identifier match string that determines which clients should be placed in this group.
zSH> new dhcp-server-group 1 Please provide the following: [q]uit. name: ------------------> {}: group1 domain: ----------------> {0}: vendor-match-string: ---> {}: 'oakland' this is converted to an octet string vendor-match-offset: ---> {0}: vendor-match-length: ---> {-1}: client-match-string: ---> {}: 'oakland'this is converted to an octet string client-match-offset: ---> {0}: client-match-length: ---> {-1}: default-lease-time: ----> {-1}: min-lease-time: --------> {-1}: max-lease-time: --------> {-1}: boot-server: -----------> {0.0.0.0}: bootfile: --------------> {}: default-router: --------> {0.0.0.0}: primary-name-server: ---> {0.0.0.0}: secondary-name-server: -> {0.0.0.0}: domain-name: -----------> {}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created.
Creating dhcp-server-host profile The dhcp-server-host defines options for a specific host within a given domain. Set the following parameters in the dhcp-server-host profile:
MALC Configuration Guide
215
Configuring IP
Parameter
Description
name
The DHCP host name for the client
hwaddr
The MAC address of the network interface that was used to acquire the lease.
clientId
The DHCP client identifier
zSH> new dhcp-server-host 1 Please provide the following: [q]uit. name: ------------------> {}: host1 domain: ----------------> {0}: hardware-address: ------> {}: 09:00:07:A9:B2:EB client-identifier: -----> {}: ‘clientgroup1’ ipaddr1: ---------------> {0.0.0.0}: ipaddr2: ---------------> {0.0.0.0}: ipaddr3: ---------------> {0.0.0.0}: ipaddr4: ---------------> {0.0.0.0}: default-lease-time: ----> {-1}: min-lease-time: --------> {-1}: max-lease-time: --------> {-1}: boot-server: -----------> {0.0.0.0}: bootfile: --------------> {}: default-router: --------> {0.0.0.0}: primary-name-server: ---> {0.0.0.0}: secondary-name-server: -> {0.0.0.0}: domain-name: -----------> {}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created.
Configuring DNS resolver Domain Name System (DNS) maps domain names to IP addresses, enabling the system to reach destinations when it knows only the domain name of the destination. DNS configuration uses the following profiles:
216
MALC Configuration Guide
•
resolver—Configures the global DNS resolver, including the DNS search order, default domain name, and list of nameserver addresses. The DNS settings in this record can be used for local applications by administrators on the system, such as traceroute or ping.
•
host-name—A replacement for the Unix local hosts table. Up to four host aliases can be defined for each host entry. Settings in the resolver record determine whether the hosts table is searched.
IP provisioning procedures
The resolver profile supports the following parameters (all others should be left at their default values): Parameter
Description
query-order
The kind of resolver query for this routing domain. Values: hosts-first searches the local hosts table first then the list of nameservers. dns-first searches the list of nameservers first then the local hosts table. dns-only searches only the list of nameservers. Default: hosts-first
domain
The routing domain to which this host parameter applies. The default is an empty string. The only routing domain supported is domain 1.
first-nameserver
The IP address of the first or primary nameserver for this routing domain. The default value is 0.0.0.0.
second-nameserver
The IP address of the second or secondary nameserver for this routing domain. This nameserver is queried if the first nameserver cannot resolve the query. The default value is 0.0.0.0.
third-nameserver
The IP address of the third or tertiary nameserver for this routing domain. This nameserver is queried if the first nameserver cannot resolve the query. The default value is 0.0.0.0.
The following example creates a resolver record for a routing domain: zSH> new resolver 1 Please provide the following: [q]uit. query-order: -------> {hosts-first}: domain: ------------> {}: zhone.com first-nameserver: --> {0.0.0.0}: 192.168.8.21 second-nameserver: -> {0.0.0.0}: 201.23.20.2 third-nameserver: --> {0.0.0.0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created.
MALC Configuration Guide
217
Configuring IP
Optionally, you can create a hosts profile after the resolver profile has been created. The syntax is new host-name routingdomain/ipoctet1/ipoctet2/ ipoctet3/ipoctet4. The host-name profile supports the following parameters (all others should be left at their default values): Parameter
Description
hostname
Client host name (if any) that the client used to acquire its address. The default is an empty string.
hostalias1
Host name alias for the specified host. The default value is an empty string.
hostalias2
Secondary host name alias for the specified host. The default value is an empty string.
hostalias3
Tertiary host name alias for the specified host. The default value is an empty string.
hostalias4
Quaternary host name alias for the specified host. The default value is an empty string.
zSH> new host-name 1/192/168/8/32 Please provide the following: [q]uit. hostname: ---> {}: www.zhone.com ipaddress: --> {0.0.0.0}: 192.168.8.32 hostalias1: -> {}: engineering.zhone.com hostalias2: -> {}: marketing.zhone.com hostalias3: -> {}: sales.zhone.com hostalias4: -> {}: gss.zhone.com .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created.
IP Service Level Agreement (IPSLA) The IP Service Level Agreement (IPSLA) feature assists service providers and network operators with enforcing and monitoring access network connections and performance. IPSLA uses ICMP Ping messages over configured IPSLA paths to track Round Trip Times (RTTs) and EHCO REQs/ RSPs between initiator and responder devices to determine network performance and delays. Typically, one initiator device is used to monitor other responder devices in the network. A maximum of 32 IPSLA paths can be configured per MALC and 4 IPSLA paths per EtherXtend. Initiator devices must be running IPSLA to request data for a responder device. Responder devices must be accessible through the ping command in the IP network , but do not need to run IPSLA. Responder devices not running
218
MALC Configuration Guide
IP provisioning procedures
IPSLA display limited statistical data and functionality. EtherXtend can function as either an initiator or responder device. Note: Networks must support CoS queues and DSCP to provide valid per CoS statistics. Otherwise, all statistics are sent to the default CoS queue. Default CoS-actions are assigned to each CoS queue so threshold crossing alarms can be configured to generate system alarms when thresholds are crossed for uptime, latency, jitter, and packet size. Data based on received/sent packets and train rates is collected and displayed as real-time statistics for the current 15 minute interval as well as over 96 15-minute intervals for 24 hour historical statistics. By default, IPSLA is disabled on all EtherXtend, MALC card ports and other SLMS devices. Figure 19: IPSLA
MALC as IPSLA Initiator
IP Network
MALC as IPSLA Responder
IPSLA Path for ICMP Pings
IPSLA Path for ICMP Pings
IPSLA Path for ICMP Pings
EtherXtend as IPSLA Responder
EtherXtend as IPSLA Responder
Configuring IPSLA IPSLA requires the following configuration steps:
•
Set ipsla-global settings to enable device state and optionally set polling interval
•
Create ICMP path between devices
•
Optionally, modify COS actions for the desired COS queues
•
Optionally modify COS map for Diff Server Control Point (DSCP) mappings
To configure IPSLA: 1
Display the global IPSLA settings and update the state and polling interval. The polling interval (60 to 3600 seconds) is used for real-time and historical statistics.
MALC Configuration Guide
219
Configuring IP
zSH> ipsla show global state: -------> {disabled} pollSeconds: -> {60}
Using the IPSLA command, enable IPSLA and set the polling interval to 120 seconds. zSH> ipsla modify global state enabled pollseconds 120
2
Create a ICMP path between devices. The device on which this command is entered becomes the initiator device, while the device for which an IP address is entered becomes the responder device. Typically, one initiator device can be used to monitor other responder devices in the network over a maximum of 32 MALC and 4 EtherXtend IPSLA paths per device. zSH> ipsla add path 172.16.78.11
zSH> ipsla show path Path configuration for ipAddress: 172.16.78.11 forwarding: -> {disabled} state: ------> {enabled}
Modify the path using the IPSLA modify path command. This example disables the static path on device 192.168.254.17. zSH> ipsla modify path ipaddress 192.168.254.17 state disabled
Delete a path using the IPSLA delete command. zSH> ipsla delete path ipaddress 192.168.254.17
Note: Disabling or deleting the path or globally disabling the IPSLA feature will reset historical data. 3
220
MALC Configuration Guide
Modify the default CoS actions to specify the response and threshold behavior for each CoS Action Index (1-8). These CoS actions map respectively to the CoS queues (0-7). The following CoS actions are defined by default.
Default Name
CoS Action Index
CoS Queue
Default
1
0
AFClass 1
2
1
AFClass 2
3
2
AFClass 3
4
3
AFClass4
5
4
Cos-5
6
5
IP provisioning procedures
Default Name
CoS Action Index
CoS Queue
ExpFwd
7
6
NetwCtrl
8
7
Each COS action contains the following parameters:
Parameter
Description
Default
Name
Name of the IPSLA CoS action, up to 9 characters in length.
(1) Default, (2) AFClass1, (3) AFClass2, (4) AFClass3, (5) AFClass4, (6) Cos-5, (7) ExpFwd, (8) NetwCtrl.
Traps
Specifies whether a trap is issued when any SLA performance error threshold within this CoS is crossed.
Disabled
Timeouts
Specifies the number of consecutive missed IP SLA responses within this CoS before a zhoneIpSLATimeoutTrap is issued.
3 timeouts
Timeout Clear
Specifies the number of consecutive IPSLA responses within this CoS which must be received before the timeout error condition is cleared.
1 sample
Latency
Specifies the 15 sample average roundtrip latency value which must be exceeded within this CoS before a zhoneIpSLALatencyTrap is issued.
10000 milliseconds
Latency Clear
Specifies the number of consecutive IPSLA latency samples for which the 15 sample average roundtrip latency must be below the configured SLA latency error threshold within this CoS before the latency error condition is cleared.
1 sample
Jitter
Specifies the 15 sample roundtrip jitter value which must be exceeded within this CoS before a zhoneIpSLAJitterTrap is issued.
10000 milliseconds
Jitter Clear
Specifies the number of consecutive IPSLA RTT samples for which the 15 sample roundtrip jitter must be below the configured SLA jitter error threshold within this CoS before the jitter error condition is cleared.
1 sample
Packetsize
Specifies the minimum IPSLA Ping packet size in bytes. The range is 64 thru 2048 if the target IP device is running IPSLA, 64 thru 512 otherwise.
64 bytes
Display the settings for an individual CoS action. zSH> ipsla show cos-action cosactionindex 1 Cos Action Configuration for cosActionIndex: 1: name: -------> {Default} traps: ------> {disabled} timeOuts: ---> {3} latency: ----> {10000}
MALC Configuration Guide
221
Configuring IP
jitter: -----> packetSize: ->
{10000} {64}
Display the settings for all CoS actions (1-8). zSH> ipsla show cos-action Cos Action Configuration for cosActionIndex: 1: name: -------> {Default} traps: ------> {disabled} timeOuts: ---> {3} latency: ----> {10000} jitter: -----> {10000} packetSize: -> {64} Cos Action Configuration for cosActionIndex: 2: name: -------> {AFClass1} traps: ------> {disabled} timeOuts: ---> {3} latency: ----> {10000} jitter: -----> {10000} packetSize: -> {64} Cos Action Configuration for cosActionIndex: 3: name: -------> {AFClass2} traps: ------> {disabled} timeOuts: ---> {3} latency: ----> {10000} jitter: -----> {10000} packetSize: -> {64} Cos Action Configuration for cosActionIndex: 4: name: -------> {AFClass3} traps: ------> {disabled} timeOuts: ---> {3} latency: ----> {10000} jitter: -----> {10000} packetSize: -> {64} Cos Action Configuration for cosActionIndex: 5: name: -------> {AFClass4} traps: ------> {disabled} timeOuts: ---> {3} latency: ----> {10000} jitter: -----> {10000} packetSize: -> {64} Cos Action Configuration for cosActionIndex: 6: name: -------> {Cos-5} traps: ------> {disabled} timeOuts: ---> {3} latency: ----> {10000} jitter: -----> {10000} packetSize: -> {64}
222
MALC Configuration Guide
IP provisioning procedures
Cos Action Configuration for cosActionIndex: 7: name: -------> {ExpFwd} traps: ------> {disabled} timeOuts: ---> {3} latency: ----> {10000} jitter: -----> {10000} packetSize: -> {64} Cos Action Configuration for cosActionIndex: 8: name: -------> {NetwCtrl} traps: ------> {disabled} timeOuts: ---> {3} latency: ----> {10000} jitter: -----> {10000} packetSize: -> {64}
To modify a cos-action, specify the desired parameters to change in the command line. This example enables traps for cosActionIndex 1. zSH> ipsla modify cos-action cosactionIndex 1 traps enabled
4
Configured the desired COS maps to modify the default DSCP to COS Action Index mappings. By default, DSCP are mapped to COS Action Index entries based of RFC 2599. The following tables shows the default mappings. A COS Action Index of 0 indicates that the DSCP is not used.
DSCP
COS Action Index
1
8
11, 13, 15
7
19, 21, 23,
6
27, 29, 31
5
35, 37, 39
4
41
3
47
2
49, 57
1
2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 14, 16, 17, 18, 20, 22, 24, 25, 26, 28, 30, 32, 33, 34, 36, 38, 40, 42, 43, 44, 45, 46 ,48, 50, 51, 52, 53, 54, 55, 56, 58, 59, 60, 61, 62, 63, 64
0
Display the CoS map for an individual CoS action or for all CoS actions. zSH> ipsla dscpIndex: dscpIndex: dscpIndex: dscpIndex:
show 1 2 3 4
cos-map cosActionIndex: cosActionIndex: cosActionIndex: cosActionIndex:
1 0 0 0
MALC Configuration Guide
223
Configuring IP
dscpIndex: dscpIndex: dscpIndex: dscpIndex: dscpIndex: dscpIndex: dscpIndex: dscpIndex: dscpIndex: dscpIndex: dscpIndex: dscpIndex: dscpIndex: dscpIndex: dscpIndex: Type A stop:
5 cosActionIndex: 0 6 cosActionIndex: 0 7 cosActionIndex: 0 8 cosActionIndex: 0 9 cosActionIndex: 0 10 cosActionIndex: 0 11 cosActionIndex: 2 12 cosActionIndex: 0 13 cosActionIndex: 2 14 cosActionIndex: 0 15 cosActionIndex: 2 16 cosActionIndex: 0 17 cosActionIndex: 0 18 cosActionIndex: 0 19 cosActionIndex: 3 to print all, to continue, Q to
Specify the desired index values in the command line to change the mapping of the DSCP index 1 to COS queue 7. This example changes the mapping of DSCP index 1 to COS queue 7. zSH> ipsla modify cos-map dscpindex 1 cosactionindex 7
To clear a CoS map, specify the desired index values in the IPSLA command to delete the mapping of the DSCP index for the COS queue. This example clears the mapping of DSCP index 1 and resets it to the COS queue 0. zSH> ipsla modify cos-map dscpindex 1 cosactionindex 0
5
Display real-time statistics for path or COS queue. Real-time statistics represent minimum, maximum, average, and current values over the current 15 minute polling period based on data collected for each polling intervals. For example, if the polling interval is configured for 60 seconds, the real-time statistics display the data compiled from the latest 15 60-second polling intervals contained in the current polling period. Note: RTT values of 0 (zero) indicate a lack of data, while sub-millisecond RTTs are reported as 1. These statistics can be displayed individually or collectively for a specified IP address or for all configured paths. Note: When a card swact occurs, historical data does not failover and data for the15-minute interval during which the swact occurred may be lost. Current and historical statistics on redundant uplinks are not supported. On switchovers, these statistics are reset to 0.
zSH> ipsla stats path ipaddress 192.168.254.15
224
MALC Configuration Guide
IP provisioning procedures
zSH> ipsla stats path
The table below explains the statistics for the configured paths.
Path Statistic
Description
Target IP Address
IP Address of the device which is at the other end of the path.
Target Name
Name of the remote device.
Target Type
Type of the remote device.
ACT
Availability status of the remote device.
Source IP
IP Address of the discovery source device.
CNX
Type of path either static or dynamic.
UpTime (secs)
Amount of time in seconds that elapsed since the last transition from Inactive to Active.
I/R
Role played by the local device in collection of latency and availability statistics. Initiator - Device that initiates the IPSLA ping packet used for statistics collection; Responder - Device that returns the IPSLA ping packet sent by the Initiator.
CoS Mismatch
Number of IPSLA ping packets received which indicate a mismatch between the Class Of Service (CoS) definitions at the remote unit and those of the source unit.
Display real-time CoS statistics individually or collectively by CoS action index, IP address or all CoS actions. zSH> ipsla stats cos cosactionindex 1
zSH> ipsla stats cos ipaddress 10.2.1.254
zSH> ipsla stats cos
The table below explains the CoS Action Index statistics.
COS Action Index Statistic
Description
CoS Index
Index number of the CoS Action Index.
Target IP Address
IP Address of the device which is at the other end of the path.
Last RTT
RTT reported in the most recent successful ping attempt.
Min RTT
Smallest RTT since this statistic was last cleared to a zero value.
Avg RTT
Average RTT since this statistic was last cleared to a zero value. Calculated as (RTT1 + RTT2 + RTT3 + …….+RTTn)/n where n equals the number of successful ping attempts since this statistic was last cleared to a zero value.
MALC Configuration Guide
225
Configuring IP
COS Action Index Statistic
Description
Max RTT
Largest RTT since this statistic was last cleared to a zero value.
Drop Resp
Number of failed pings since this statistic was last cleared to a zero value.
Display historical statistics individually or collectively based on IP address, CoS action index, and index value of a 15 minute interval. Historical statistics are displayed for the latest 24 hour period or a specified 15 minute interval within the latest 24 hour period. For historical statistics, IPSLA averages values for the most recent 96 15-minute intervals and displays the minimum, maximum, average and current values in a table for a 24 hour summary. zSH> ipsla stats history cosactionindex 1 Up to 96 intervals....
zSH> ipsla stats history ipaddress 10.2.1.254
zSH> ipsla stats history index 1
zSH> ipsla stats history Up to 96 intervals....
Each bulk statistic relies on a bulk-statistics profile to define the OID, instance and other MIB information used to collect and display the data. When a IPSLA path is modified or deleted during the process of data collection, the related bulk-statistics profiles may lose their association and become dangling profiles. The bulkstats audit command enables users to check for and delete dangling bulk-statistics profiles. The bulkstats audit command provides an interactive and repair option. The interactive option lists all dangling profiles with the option to modify or delete the profile. The repair option prompts for profile deletion. bulkstats audit -interactive | repair To display and repair dangling bulk-statistics profiles, enter the bulkstats audit command. zSH> bulkstats audit -interactive Checking validity............ 3 dangling profiles found. bulk-statistic 5 enabled: ---------->
226
MALC Configuration Guide
{true}
IP provisioning procedures
oid: --------------> instance: ---------> include-children: ->
{zhoneIpSLAPathStatByCOSAvgRTT} {6.1.11.1.15.253} {false}
[d]elete, [m]odify, [n]ext, [p]revious, [h]elp, [q]uit ? d bulk-statistic 55 enabled: ----------> oid: --------------> instance: ---------> include-children: ->
{true} {zhoneIpSLAPathStatByCOSAvgRTT} {2.1.173.24.95.2} {false}
[d]elete, [m]odify, [n]ext, [p]revious, [h]elp, [q]uit ? d bulk-statistic 555 enabled: ----------> {true} oid: --------------> {zhoneIpSLAPathStatByCOSAvgRTT} instance: ---------> {2.1.173.24.72.103} include-children: -> {false} [d]elete, [m]odify, [n]ext, [p]revious, [h]elp, [q]uit d
zSH> bulkstats audit -repair Checking validity............ 1 dangling profile found. Delete profile? { [y]es or [n]o } y
IP fallback route The MALC supports IP redundancy or fallback IP routes. A fallback route is a second static route with the same destination and netmask of an existing route but with a different nexthop destination. The redundant or fallback route is used when the original nexthop destination is unavailable. The fallback route continues to be used until the revertive period expires. At that time, traffic switches back to the primary route. A ping interval and ping retry count are use to determine route availability. The MALC pings the active nexthop router once during each ping interval. The ping-interval is specified in milliseconds and has a minimum value of 500 milliseconds or 1/2 second. If the number of ping failures to the current nexthop destination exceed the ping-fail-max setting, the current nexthop destination is replaced in the routing table with the fallback nexthop destination.The system begins pinging the new nexthop router and monitoring the number of ping failures. The revertive period is set by the system based on a multiple of the ping interval and retry count.
MALC Configuration Guide
227
Configuring IP
Note: The cost (metric) of the fallback route is automatically calculated to be one more than the cost of the first active route.
Configuring IP redundancy To configure IP redundancy: 1
Add a route with the IP addresses of the nexthop router and fallback router.
zSH> route add default 192.168.34.254 1 fallback 192.168.34.201 2000 3 zSH> route add 10.10.1.0 255.255.255.0 192.168.34.254 1 fallback 192.168.34.201 3000 5
2
Display the configured IP routes.
zSH> route show ... Source Routing Table Dest Nexthop Cost Owner Interface --------------------------------------------------------------------------Destination Routing Table Dest
Nexthop
Cost
Owner
Fallback
--------------------------------------------------------------------------0.0.0.0/0 192.168.34.254 1 STATICLOW 10.10.1.0/24 192.168.34.254 1 STATIC 192.168.34.201 192.168.34.0/24 1/1/1/0/ip 1 LOCAL
3
To delete the primary and fallback routes:
zSH> route delete 10.10.1.0 255.255.255.0 192.168.34.254 fallback 192.168.34.201
route command updates Administers the routing information base (RIB). The route add and route delete commands take a keyword called source which indicates that a source route is used and must to added or removed from the source routing table. The user must also specify the IP interfaces of the next hop.The route show command now accepts an optional keyword of either source or destination which specifies the type of routing table is to be displayed. If the keyword is not used, both source and destination routing tables are displayed. Syntax The following command displays the forwarding information base. route [domain domain-spec] show [source|destination]
domain domain-spec
228
MALC Configuration Guide
IP provisioning procedures
Specifies the routing domain. Only domain 1 is supported. show Displays the routes in the route domain for source and destination routing. Syntax The following command adds a high-preference static route for the
destination IP address with the specified network mask (dotted decimal format) to the specified next hop with the specified routing cost. The word ‘default’ may be substituted for a 0.0.0.0 destination and mask. If a ‘fallback’ route is also specified, a second next hop, ping interval (in milliseconds), and ping maximum failure count must be specified. Fallback routes have the same destination and mask as the original route, but use a different next hop. After a route and fallback route are configured, the current next hop is pinged once every ping interval. If the number of ping maximum failures is exceeded, the fallback next hop becomes the current next hop. The next hop validation continues once every ping interval. route [ domain domain-spec ] add [source] destination-address netmask nexthop-address nexthop-interface metric [fallback nexthop2 ping-interval ping-fail-max]
domain domain-spec Specifies the routing domain. Only domain 1 is supported. source Indicates that a source address based route is being added. The interface is the name of the outbound (egress) interface for this route (minus the /ip suffix). destination-address netmask Adds a static route with the specified destination and network mask. nexthop-address IP address of the next hop. nexthop-interface Interface for the next hop. This is valid only when the next-hop address is 0.0.0.0. Otherwise, this should be 0 (zero). This option is currently unsupported. metric A numeric value specifying the metric for the route. Lower metrics indicate more preferred routes. nexthop2 IP address of the fallback or redundant next hop. ping-interval The ping interval with a minimum value of 500 milliseconds. maxretry The max retry (fail) count for the pings. When this limit is reached, the fallback nexthop is used.
MALC Configuration Guide
229
Configuring IP
Syntax The following command deletes a static route from the system routing table.
The word ‘default’ may be substituted for a 0.0.0.0 destination and mask. The fallback and nexthop2 options must be specified to delete routes configured with fallback routes. route [ domain domain-spec ] delete [source] destination-address netmask nexthop-address nexthop-interface [fallback nexthop2 ping-interval ping-fail-max]
domain domain-spec Specifies the routing domain. Only domain 1 is supported. source Specifies that a source address based route is being removed. The interface is the name of the outbound (egress) interface for this route (without the /ip suffix). destination-address netmask Deletes the destination address and netmask from the routing table. nexthop-address IP address of the next hop address. nexthop-interface Interface for the next hop. This is valid only when the next-hop address is 0.0.0.0. Otherwise, this should be 0 (zero). This option is currently unsupported. nexthop2 IP address of the fallback or redundant next hop. ping-interval The ping interval with a minimum value of 500 milliseconds. maxretry The max retry (fail) count for the pings. When this limit is reached, the fallback nexthop is used. Example zSH> route show Source Routing Table Dest Nexthop Cost Owner Interface -----------------------------------------------------------------------------10.10.201.2/32 10.10.201.1 1 STATIC 1/1/1/0/ip 10.10.204.2/32 10.10.204.1 1 STATIC 1/1/1/0/ip Destination Routing Table Dest Nexthop Cost Owner ------------------------------------------------------------0.0.0.0/0 172.24.94.254 1 STATICLOW 10.10.201.2/32 1/1/1/0/ip 1 LOCAL 10.10.204.0/30 1/1/1/0/ip 1 LOCAL 172.24.94.0/24 1/1/1/0/ip 1 LOCAL 172.16.80.0/24 172.24.94.254 1 STATIC
230
MALC Configuration Guide
IP provisioning procedures
zSH> route show source Source Routing Table Dest Nexthop Cost Owner Interface -----------------------------------------------------------------------------10.10.201.2/32 10.10.201.1 1 STATIC 1/1/1/0/ip 10.10.204.2/32 10.10.204.1 1 STATIC 1/1/1/0/ip zSH> route show destination Destination Routing Table Dest Nexthop Cost Owner ------------------------------------------------------------0.0.0.0/0 172.24.94.254 1 STATICLOW 10.10.201.2/32 1/1/1/0/ip 1 LOCAL 10.10.204.0/30 1/1/1/0/ip 1 LOCAL 172.24.94.0/24 1/1/1/0/ip 1 LOCAL 172.16.80.0/24 172.24.94.254 1 STATIC zSH> zSH> route add source 198.168.1.1 255.255.255.255 198.168.1.101 1 uplink1-0-36 zSH> route add default 192.168.34.254 1 fallback 192.168.34.201 2000 3 zSH> route add 10.10.1.0 255.255.255.0 192.168.34.254 1 fallback 192.168.34.201 3000 5 zSH> route show ... Source Routing Table Dest Nexthop Cost Owner Interface --------------------------------------------------------------------------Destination Routing Table Dest
Nexthop
Cost
Owner
Fallback
--------------------------------------------------------------------------0.0.0.0/0 192.168.34.254 1 STATICLOW 10.10.1.0/24 192.168.34.254 1 STATIC 192.168.34.201 192.168.34.0/24 1/1/1/0/ip 1 LOCAL zSH> route delete source 198.168.1.1 255.255.255.255 198.168.1.101 uplink1-0-36 zSH> zSH> route delete 10.10.1.0 255.255.255.0 192.168.34.254 fallback 192.168.34.201 Access Level admin Products BAN, MALC, Raptor 100, Raptor 319, Raptor 719, Raptor 723, Sechtor
100A, Z-Edge 64 See Also rip
MALC Configuration Guide
231
Configuring IP
IP administrative procedures The following IP administrative procedures are supported on the MALC:
•
Modifying profiles created by host/interface add commands on page 232
•
Displaying hosts on page 234
•
Displaying interfaces on page 235
•
Displaying routing information on page 236
•
Deleting hosts on page 237
•
Deleting interfaces on page 237
•
Deleting routes on page 237
•
DHCP logging on page 237
•
IP statistics commands on page 240
Modifying profiles created by host/interface add commands After profiles have been created by the host add and interface add commands there are two methods of modifying the profiles:
•
You can perform a host delete or interface delete, which deletes all associated profiles, then re-create those profiles with another host add or interface add command, specifying changes in the command line.
•
You can modify the individual profiles which have been created by host add and interface add commands.
For example, the command: zSH> host add 1-8-1-0/adsl vc 0/35 td 1 dynamic 1 3
Creates the following profiles: ip-interface-record 1-8-1-0-adsl-0-35/ip ip-interface-record 1-8-1-0-adsl-0-35-1/ip ip-interface-record 1-8-1-0-adsl-0-35-2/ip ip-interface-record 1-8-1-0-adsl-0-35-3/ip atm-vcl 1-8-1-0-adsl/atm/0/35 atm-vcl 1-1-1-0-propvirtual/atm/0/32 atm-cc 1
Note: You must disable the cross-connect and the ATM-VCL before changing the AAL5 encapsulation type in active cross-connects. The host add, and host delete commands, and may be replaced with brackets containing numbers in series and/or (dash-separated) ranges; may be replaced with wildcard '*' for all ports on the card. Refer to the CLI Reference Guide for a complete description of the command options and syntax.
232
MALC Configuration Guide
IP administrative procedures
Modifying individual profiles created by host/interface add 1
Before modifying ATM-VCLs, the cross-connect in which they are used, must be disabled:
zSH> update atm-cc 1 Please provide the following: [q]uit. cc-index: ------> {1}: ** read-only ** low-if-index: --> {1-1-1-0-propvirtual/atm}: ** read-only ** low-vpi: -------> {0}: ** read-only ** low-vci: -------> {32}: ** read-only ** high-if-index: -> {1-8-1-0-adsl/atm}: ** read-only ** high-vpi: ------> {0}: ** read-only ** high-vci: ------> {35}: ** read-only ** admin-status: --> {up}: down handle-id: -----> {handle_1}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
2
Active VCLs must be disabled before making any modifications to them:
zSH> update atm-vcl 1-8-1-0-adsl/atm/0/35 Please provide the following: [q]uit. vpi: -----------------------------> {0}: ** read-only ** vci: -----------------------------> {35}: ** read-only ** admin_status: --------------------> {up}: down receive_traffic_descr_index: -----> {1}: transmit_traffic_descr_index: ----> {1}: vcc_aal_type: --------------------> {other}: ** read-only ** vcc_aal5_cpcs_transmit_sdu_size: -> {9188}: vcc_aal5_cpcs_receive_sdu_size: --> {9188}: vcc_aal5_encaps_type: ------------> {other}: vcl_cast_type: -------------------> {p2p}: vcl_conn_kind: -------------------> {pvc}: fault-detection-type: ------------> {disabled}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
3
Make changes to the VCL:
zSH> update atm-vcl 1-8-1-0-adsl/atm/0/35 Please provide the following: [q]uit. vpi: -----------------------------> {0}: ** read-only ** vci: -----------------------------> {35}: ** read-only ** admin_status: --------------------> {down}: receive_traffic_descr_index: -----> {1}: transmit_traffic_descr_index: ----> {1}: vcc_aal_type: --------------------> {other}: ** read-only ** vcc_aal5_cpcs_transmit_sdu_size: -> {9188}: vcc_aal5_cpcs_receive_sdu_size: --> {9188}: vcc_aal5_encaps_type: ------------> {other}: llcencapsulation vcl_cast_type: -------------------> {p2p}: vcl_conn_kind: -------------------> {pvc}:
MALC Configuration Guide
233
Configuring IP
fault-detection-type: ------------> {disabled}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
4
Re-enable the VCL:
zSH> update atm-vcl 1-8-1-0-adsl/atm/0/35 Please provide the following: [q]uit. vpi: -----------------------------> {0}: ** read-only ** vci: -----------------------------> {35}: ** read-only ** admin_status: --------------------> {down}: up receive_traffic_descr_index: -----> {1}: transmit_traffic_descr_index: ----> {1}: vcc_aal_type: --------------------> {other}: ** read-only ** vcc_aal5_cpcs_transmit_sdu_size: -> {9188}: vcc_aal5_cpcs_receive_sdu_size: --> {9188}: vcc_aal5_encaps_type: ------------> {llcencapsulation}: vcl_cast_type: -------------------> {p2p}: vcl_conn_kind: -------------------> {pvc}: fault-detection-type: ------------> {disabled}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
5
Re-enable the cross-connect after changes have been made: zSH> update atm-cc 1 Please provide the following: [q]uit. cc-index: ------> {1}: ** read-only ** low-if-index: --> {1-1-1-0-propvirtual/atm}: ** read-only ** low-vpi: -------> {0}: ** read-only ** low-vci: -------> {32}: ** read-only ** high-if-index: -> {1-8-1-0-adsl/atm}: ** read-only ** high-vpi: ------> {0}: ** read-only ** high-vci: ------> {35}: ** read-only ** admin-status: --> {down}: up handle-id: -----> {handle_1}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Displaying hosts Issue the host show command to display hosts, which displays the IP address of the unnumbered interface used in the host route, interface of the host route, VPI/VCI of the internal VCL used to create the host, the subnet group to which the host belongs, whether the host is dynamically or statically assigned, and if the host has been assigned an IP address. zSH> host show
234
MALC Configuration Guide
IP administrative procedures
Rd/Address Interface Group T Host Address -------------------------------------------------------------------------------1 10.0.0.1 1-11-1-0-adsl-0-35 0/32 1 D D D S 192.168.11.5 1 192.168.11.1 1-8-6-0-adsl-0-35 0/33 0 S 192.168.11.6 1 192.168.11.1 1-8-2-0-adsl-0-35 0/35 0 S 192.168.11.55
Displaying interfaces Issue the interface show command to display interfaces: zSH> interface show Interface Status Rd/Address Media/Dest Address IfName -------------------------------------------------------------------------------1/1/1/0/ip UP 1 [10.0.0.1] 0/35 multipoint 1-5-1-0-adsl-0-35 --------------------------------------------------------------------------------
Brackets around IP addresses in the output of the interface show command indicate unnumbered interfaces.
MALC Configuration Guide
235
Configuring IP
Displaying routing information The following commands display routing information:
•
route show
•
rip show
Displaying the routing table To display the routing table, use the route show command: zSH> route show Dest Nexthop Cost Owner -----------------------------------------------------------0.0.0.0/0 172.24.200.254 1 STATICLOW 172.24.200.162/32 1 LOCAL 172.24.200.0/24 1/1/1/0/ip 1 LOCAL
Displaying RIP information To display Routing Information Protocol (RIP) information, use the rip show command: zSH> rip show RIP Globals ---------------------------------------------------------Route Route Route Admin Update Domain Changes Queries State Time ---------------------------------------------------------1 0 0 disabled 30 ---------------------------------------------------------RIP Interface Statistics -----------------------------------------------------Recv Bad Recv Bad Updates IfName Packets Routes Sent To -----------------------------------------------------1-1-1-0 0 0 0 uplink1 0 0 0 1-8-1-0-adsl-0-35 0 0 0 1-8-6-0-adsl-0-35 0 0 0 1-8-8-0-adsl-0-35 0 0 0 1-8-3-0-adsl-0-35 0 0 0 RIP Interface Configuration -------------------------------------------------------------------------------Auth Auth Default Src IfName Type Key Talk Listen Metric Address Static Poison -------------------------------------------------------------------------------1-1-1-0 none (write-only) disabled disabled 0 172.24.20 0.162 none disabled uplink1 none (write-only) disabled disabled 0 219.200.1 62.2 none disabled 1-8-1-0-adsl-0-35 none (write-only) disabled disabled 0 192.168.1
236
MALC Configuration Guide
IP administrative procedures
1.1 none disabled 1-8-6-0-adsl-0-35 none (write-only) disabled disabled 0 0.0.0.0 none disabled 1-8-8-0-adsl-0-35 none (write-only) disabled disabled 0 0.0.0.0 none disabled 1-8-3-0-adsl-0-35 none (write-only) disabled disabled 0 0.0.0.0 none disabled RIP Peers -------------------------------------------------------------------------------Route IP Last Recv Bad Recv Bad Domain Address Update Version Packets Routes --------------------------------------------------------------------------------
Deleting hosts Issue the host delete command to delete hosts. The host add, and host delete commands, and may be replaced with brackets containing numbers in series and/or (dash-separated) ranges; may be replaced with wildcard '*' for all ports on the card. zSH> host delete 1-11-1-0/adsl vc 0/35 all
Deleting interfaces Issue the interface delete command to delete interfaces: zSH> interface delete 1-5-1-0/adsl vc 0/35 Delete complete
Deleting routes To delete static routes, use the route delete command. The command uses the following syntax: zSH> route delete destination mask next-hop
The following example deletes the network route to 192.178.21.0 using the gateway 192.172.16.1: zSH> route delete 192.178.21.0 255.255.255.0 192.178.16.1
DHCP logging The MALC provides a logging facility to monitor the DHCP packets it sends and receives. By default, DHCP messages are not displayed.
Enabling DHCP logging 1
Enable the DHCP server log messages: zSH> log level dhcpserver info Module: dhcpserver at level: info
MALC Configuration Guide
237
Configuring IP
2
Enable logging for the session: zSH> log session on Logging enabled.
As DHCP server messages are sent and received, they are displayed on the console. Note: This setting does not persist across system reboots. You must re-enable DHCP logging after a MALC reboot. 3
These messages can be captured to a file using your terminal’s capture facility, or sent to a syslog server. For example: zSH> new syslog-destination 1 Please provide the following: [q]uit. address: --> {0.0.0.0}: 192.200.42.5 syslog server IP address port: -----> {514}: facility: -> {local0}: severity: -> {debug}:info .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Understanding DHCP server log messages When a device sends a DHCP server request to the MALC, a message similar to the following is logged: AUG 13 12:20:48: info : 1/1/1084: dhcpserver: DhcpServerTask: DHCPREQUEST for 155.57.1.21 from 00:b0:d0:98:92:3d via if496
This message indicates that a request for the address 155.57.1.21 was received by the device with the MAC address 00:b0:d0:98:92:3d. The request came in over the interface number 496. To find what physical interface this corresponds to, use the ifxlate command: zSH> ifxlate 496 ifIndex: ----------> shelf: ------------> slot: -------------> port: -------------> subport: ----------> type: -------------> adminstatus: ------> physical-flag: ----> iftype-extension: -> ifName: ----------->
{496} {1} {10} {48} {0} {hdsl2} {up} {true} {none} {1-10-48-0}
The MALC sends the following message when it acknowledges the DHCP request packet.
238
MALC Configuration Guide
IP administrative procedures
AUG 13 12:20:48: info : 1/1/1084: dhcpserver: DhcpServerTask: DHCPACK on 155.5 7.1.21 to 00:b0:d0:98:92:3d via if496
Viewing client leases When the MALC issues a DHCP client lease, it creates a dhcp-server-lease. You can view these records to see the status of the lease: 1
List the current leases: zSH> list dhcp-server-lease dhcp-server-lease 0/155/57/1/10 dhcp-server-lease 0/155/57/1/11 dhcp-server-lease 0/155/57/1/12 dhcp-server-lease 0/155/57/1/13 dhcp-server-lease 0/155/57/1/14 dhcp-server-lease 0/155/57/1/15 dhcp-server-lease 0/155/57/1/17 dhcp-server-lease 0/155/57/1/18 dhcp-server-lease 0/155/57/1/19 dhcp-server-lease 0/155/57/1/16 dhcp-server-lease 0/155/57/1/20 dhcp-server-lease 0/155/57/1/21 dhcp-server-lease 0/155/57/1/22 dhcp-server-lease 0/155/57/1/23 14 entries found.
2
To view an individual record: zSH> get dhcp-server-lease 0/155/57/1/10 starts: ------------> {1060700857} ends: --------------> {1060700917} flags: -------------> {0} hardware-address: --> {00:00:c5:90:3b:08} client-identifier: -> {} client-hostname: ---> {} hostname: ----------> {} dns-fwd-name: ------> {} dns-rev-name: ------> {}
Note that 0/155/57/1/10 represents routing domain 0, and the IP address 155.57.1.10.
MALC Configuration Guide
239
Configuring IP
IP statistics commands The following IP commands are available to users with administrative privileges.
•
ip icmpstat Displays ICMP statistics.
•
ip ifstat Displays interface statistics.
•
ip ifsum Displays a summarized list of known interfaces.
•
ip inetstat Displays the active TCP/UDP/RAW endpoints terminating on the card.
•
ip ipstat Displays IP statistics.
•
ip tcpstat Displays TCP statistics.
•
ip udpstat Displays UDP statistics.
•
ip arpdelete Deletes an entry from the ARP table.
•
ip arpflush Flushes the ARP table of all entries.
•
ip arpshow Displays the ARP table.
240
MALC Configuration Guide
5
CONFIGURING BRIDGES This chapter explains how to configure bridging on the MALC. It includes the following sections:
•
•
Overview, page 241
•
Bridges, bridge interfaces, and bridge paths, page 242
•
Macro bridge commands: bridge add, bridge-path add, page 243
•
Upstream and downstream, uplinks and downlinks, page 244
•
Bridges: line concentrator, Internet access model, intralink, TLS, hub, page 245
•
The Internet access model, page 249
•
VLANs, page 250
•
Internet access model with intralinked MALCs, page 255
•
Transparent LAN service, page 258
•
Hub bridge, page 260
•
Bridge show/showall commands, page 261
Advanced bridging configurations, page 263
Overview Bridges are ISO layer two functions which connect network segments and direct traffic based on Ethernet Media Access Control (MAC) addresses. MAC addresses are a unique address per physical device. Manufacturers buy MAC addresses from the IEEE, so MAC addresses are kept unique. Routers are layer three devices which use IP Addresses to direct packets. Bridges direct packets based on address information in the packets as well as information learned from the processing and directing of other packets. The processing and directing of packets is the learning, forwarding, or filtering that is done by the device. The amount of processing and information read from the packet is kept to a minimum to enhance the throughput speed of the device. The flexibility of the MALC allows it to function both as a router and as a bridge. This chapter describes bridging.
MALC Configuration Guide
241
Configuring bridges
Note: The MALC ports can support both routing and bridging on different circuits. Each configuration requires at least two interfaces to work together, however each interface must be configured for either IP termination or bridging and cannot support both at the same time.
Bridges, bridge interfaces, and bridge paths Bridges connect network segments. These network segments are physically attached to the MALC through interfaces on the uplink and line cards inserted into the MALC. These uplink and line cards need to be configured to pass traffic. The mechanism for configuring the cards is the bridge interface record. The bridge interface (as created in the bridge command) is what you configure to set up bridges on the MALC. Bridge interface records are set from the CLI to set up bridges. Within the MALC, bridges define the behaviors between or among physical connections. In this chapter we will configure a line concentrator, an Internet access model with downlinks, an Internet access model with intralinks, a TLS bridge and a hub bridge. The bridge path defines the upstream path when sending packets upstream from the MALC. Figure 20: A bridge is a combination of interfaces working in combination bridge interface record bridge interface record bridge interface record
A bridge is a combindation of bridge interface records
bridge interface record
In the first section we will discuss the macro commands, these are the bridge add and bridge modify commands where you enter information in the CLI, rather than directly modifying the micro parameters in the bridge interface record.
242
MALC Configuration Guide
Overview
Macro bridge commands: bridge add, bridge-path add Bridges are configured using the Command Line Interface (CLI) bridge add command or the bridge modify command. This section introduces the commands. The following sections will mainly use the bridge add and bridge-path add commands to configure common bridges.
bridge add The bridge add command defines the desired bridge interface type (upl for uplink, dwn for downlink, int for intralink, tls for TLS, hub for hub, and no type for transparent. bridge add interface/type
For transparent bridges, the type parameter is omitted to create bridges on the interfaces with default transparent bridge settings. To introduce the bridge add command we will show a realistic example. The bridge add command is used to create the uplink and a couple of downlinks for a line concentrator bridge. bridge add 1-1-2-0/eth uplink bridge add 1-4-1-0/eth downlink bridge add 1-4-3-0/eth downlink
The line concentrator requires uplinks and downlinks to be identified since uplinks and downlinks have different behaviors. In following sections we will discuss building line concentrators, Internet access, TLS and other bridges. For more on line concentrators, please see Line concentrator, page 246. To facilitate bridge setup, the MALC sets the default bridge interface record profiles based on the downlink and uplink command parameters. In the bridge add and bridge delete commands, and may be replaced with brackets containing numbers in series and/or (dash-separated) ranges; may be replaced with wildcard '*' for all ports on the card. Refer to the CLI Reference Guide for a complete description of the command options and syntax and for a detailed explanation of the available bridge commands.
bridge-path add Bridge-paths define where traffic should be transmitted for asymmetric bridges. See Configuring the Internet access model, page 252 and Configuring intralinked MALCs, page 256 for examples of the use of the bridge-path add command. The bridge-path command adds, modifies, displays or deletes static bridges.
MALC Configuration Guide
243
Configuring bridges
Note: When routed and bridged traffic is configured for the same uplink interface, VLAN tags must be used between both downlink ports and the uplink interface for traffic differentiation. For routed traffic, use the ip-interface-record profile to specify the VLAN ID.
Upstream and downstream, uplinks and downlinks Upstream and downstream, uplink and downlink are closely related terms. Uplink and downlink describe the bridge interface type. We also use the term, uplink, to refer to a specific type of card used in the MALC. Upstream and downstream are situational terms to help discuss the scenario in which the MALC is placed. Figure 20 shows the logical arrangement of uplinks at the top. In this classic configuration the Uplink connections are upstream or toward the network core. The downlinks are pointed downstream or toward the network edge where devices which require network access reside. These devices would be phone handsets, laptops, Internet capable security monitors or the multitude of products which now connect to the Internet. Each card may have multiple physical connectors. There is not a one to one correspondence of physical interface and logical interface. For example an ADSL card with 48 ports may provide 48 connection lines out. With bonding some of those connection lines may be bonded to work together as a single logical connection. The distinction between physical configuration and logical setup is an important one. Figure 20 shows the difference between the hardware configuration of the MALC and how we display the logical configurations in the documentation. In the physical MALC all connections are on the front. The uplink/controller cards are in the left most two slots. Normally an uplink card will be assigned an uplink bridge interface and ports on the line cards will be assigned downlink bridge interfaces. Sometimes a MALC will be subtended off one of the line card ports. In this case the upstream MALC port will normally be assigned an interlink bridge interface while the downstream MALC connection will be assigned the uplink bridge interface. While the normal configuration has uplink interfaces on the uplink card, it is not required that an uplink interface be associated with an uplink card. Although rare, it is possible that a subtended MALC may be connected to another MALC via a line card on the subtended MALC rather than the uplink, so for the subtended MALC the interface would be through a line card configured as an uplink. Uplink cards are also the controller card for the MALC. The Uplink ard is required for the MALC to function. It contains all software files plus the configuration database.
244
MALC Configuration Guide
Bridges: line concentrator, Internet access model, intralink, TLS, hub
Figure 21: Physical MALC with cards inserted and logical connections
uplink/controller cards
Iine cards
uplink connecting upstream (towards network or Internet) core
downlinks connecting downstream (toward network edge/ actual end users of access — PCs, laptops, or other devices which require network access)
Asymmetric and symmetric bridges Zhone uses the terms asymmetric and symmetric to define two basic behaviors of bridges. Bridges are made up of two or more interfaces— the physical ports connecting the network portions or segments and the possibly multiple logical interfaces for the physical ports. Bridges are defined by how the bridge interfaces are configured to work together and the bridge path defined. Bridges learn where to forward or filter packets. See Broadcast, multicast, and unicast, page 247 for descriptions of learning and forwarding behavior. The difference between symmetric and asymmetric bridges is the learning behaviors of the uplinks and downlinks of the bridge. Uplinks and downlinks have different learning behaviors so they are considered asymmetric. Both the line concentrator and the Internet access model use uplinks and downlinks. In a symmetric bridge all the interfaces are configured so they have the same learning and forwarding behavior. With Asymmetric bridges the interfaces are configured uniquely, though uplink/downlink asymmetric bridges have one interface, the uplink which is configured uniquely from the others. As shown in Figure 21, the line concentrator/Internet access model, the downlink interfaces, which connect downstream toward user devices, because they are downlink interfaces, are configured with the same learning behavior as each other. There are three different bridge interface types for asymmetric bridges — uplink, downlink, and intralink. Uplink and downlink work together to learn and direct packets within the MALC or upstream from the MALC. This learning from downlinks creates a database of connected devices. Intralinks address scenarios where you need to forward traffic to another MALC.
Bridges: line concentrator, Internet access model, intralink, TLS, hub The most common bridge types are the Internet access model, TLS bridges, and hub bridges. We will start with a line concentrator which is simpler but
MALC Configuration Guide
245
Configuring bridges
only slightly different than the Internet access model. We will also discuss a more advanced line concentrator model using multiple MALCs chained together using an intralink bridge interface to manage the traffic among the MALCs.
Line concentrator When setting up for data Internet access for multiple subscribers you configure the MALC as a line concentrator. With this Internet access/line concentrator model you create an asymmetric bridge with a high capacity link upstream configured to be the uplink, and have many downlinks configured for the subscribers. Figure 22: The line concentrator model
network or Internet core
high capacity uplink upstream
multiple downlinks to subsribers
Configuring the line concentrator For the line concentrator you need to specify an uplink, a bridge-path to send packets recieved on the downlinks. With the line concentrator all bridged traffic is shared, so this model has less security protection than the example we will discuss next, the Internet access model. With the Internet access model you use the Virtual LAN mechanism to keep subscribers traffic separated from each other. 1
Add a bridge interface on the uplink card bridge add 1-1-2-0/eth uplink
The “1-1-2-0” string defines the MALC-slot-port-interface. This bridge add command says that for port 2 of the card in slot 1, to make the bridge interface be an ethernet uplink. 2
Add a global bridge path so that all traffic from the downlinks are forwarded out the uplink bridge-path add ethernet2-0/bridge global
246
MALC Configuration Guide
Bridges: line concentrator, Internet access model, intralink, TLS, hub
The bridge-path add command defines where to send traffic from the downlinks. The global option means that all traffic from the downlinks are forwarded out the uplink. 3
Add bridge interfaces on the downlink cards Note that the card in slot 4, port 1 can be configured so that multiple VLANs may be on a single port. bridge add 1-4-1-0/eth downlink bridge add 1-4-3-0/eth downlink
This configuration has one uplink and two downlinks.
Broadcast, multicast, and unicast Bridges transmit packets. In general, packets are received on one interface, then transmitted out on one or more interfaces. There are three general ways to transmit packets. Packets are sent broadcast, multicast or unicast. Unicast packets are sent to a specific address. Multicast packets are sent to a limited number of entities. Broadcasts are sent to all available entities, usually all devices in a subnet as they can be a reasonably limited set of entities. Based on the type of bridge there is different behavior on the learning and forwarding of the packets. Understanding the different behaviors in the learning and forwarding behavior of bridges we will discuss — Line concentrator, Internet access model, intralink bridges, TLS bridges, and hub bridges — is a good means to understanding the bridging options. For the purposes of discussion we will talk about how unicast, broadcast and multicast packets are handled with an uplink/downlink asymmetric bridge, the basic Internet access model. Figure 23 shows a graphic representation of the forwarding and learning behaviors for an asymmetric bridge.
Unicast Unicast sends to a specific address. In an uplink/downlink asymmetric bridge if the MAC address is in the database of learned addresses then the packet is sent to the appropriate downlink card and out to the device. If the MAC address is not in the database, then the packet is discarded.
Broadcast Broadcast packets have a special code in the address portion of the packet which identify it as a broadcast packet. These packets are normally duplicated and sent to all devices. Broadcast packets in an asymmetric bridge are blocked. Address Resolution Protocol (ARP) and Dynamic Host Configuration Protocol (DHCP) both are broadcast packets in that they use the special broadcast code in the address portion of the Ethernet packet but are dealt with as exceptions.
MALC Configuration Guide
247
Configuring bridges
ARP looks up an IP address in a database which maintains learned IP addresses. In this way ARP is actually a mixture of level 2 (Logical Link with MAC addresses) and Level 3 (Network IP with IP addresses).If the packet is an ARP packet, then the MALC compares and filters the requested IP address with the current forwarding table. If a match is found, the ARP broadcast is forwarded out the interface that has the appropriate host. This host will then reply to the ARP with a standard response. If a match is not found, then the ARP is filtered and it gets dropped as if it were a non-ARP broadcast. This setting is controlled by the customARP parameter. DHCP Servers provide a pool of IP addresses, and upon request provide the proper IP address for a device. When a MALC receives a broadcast DHCP OFFER message from a remote DHCP server the broadcast messages are forwarded to the source MAC address if customDHCP is set to true. Otherwise, the broadcast DHCP messages are filtered.
Multicast Multicast is used when the same data is required by a group of clients at the same time. Unlike broadcast which sends to all devices, multicast provides content to a limited number of devices simultaneously. A common use of multicast would be a video server. Receiving, duplicating and transmitting packets for high quality video to a large number of devices is processing time and capacity intensive. In multicast the number of recipients is guided by the multicast clients requesting to receive the multicast. Figure 23: Forwarding and learning behavior for an asymmetric bridge message in
message out Unicast
Multicast Broadcast
uplink forwards
Multicast Broadcast
uplink forwards
forwarding database
forwarding database downlink forwards
downlinks learn Unicast
Unicast
Multicast Broadcast
multicast and broadcast* blocked
Unicast
Multicast
Broadcast
* broadcast exceptions: DHCP, ARP
In an asymmetric bridge the general rule is that the source address of packets received on the downlinks are learned and the packets are sent out the uplink. Unicast packets received on the uplink are forwarded if found in the forwarding table, discarded if not. Multicasts and broadcasts received on the uplink are not forwarded with the DHCP and ARP exceptions noted above. As we walk through the different bridges these behaviors will become more understandable.
248
MALC Configuration Guide
Bridges: line concentrator, Internet access model, intralink, TLS, hub
The Internet access model The most common asymmetric bridge is the standard Internet access model (which shares the same fundamental physical connections as the line concentrator). The line concentrator model has a high capacity connection upstream and multiple subscribers downstream. To build the line concentrator you would use two bridge interface types — uplink and downlinks. You would configure an uplink bridge interface on the high speed upstream connection and downlinks on the downstream connections to subscribers. The Internet access model presumes that the downstream subscribers do not share any traffic. Figure 24: The Line concentrator model without VLANs is one bridge
Packet out
source addresses to database
uplink
downlink
Packet in uplink
downlinks
Learns source address on ingress on the dowlink interface
Packet in
downlink
downlinks
finds address in learned MAC address database Send out to interface where address was learned
Packet out
(With Ethernet and no VLAN mapping all interfaces are set up as the one bridge)
In the Internet access/line concentrator model packets sent from devices downstream have the source MAC address learned. All packets received on downlinks are forwarded to the uplink. When a unicast packet (a packet that is supposed to go to one address) is received from upstream and the address matches a learned MAC address, then the packet is forwarded to that address. Unknown unicast packets recieved on the uplink are discarded. Note: When routed and bridged traffic is configured for the same uplink interface, VLAN tags must be used between both downlink ports and the uplink interface for traffic differentiation. For routed traffic, use the ip-interface-record profile to specify the VLAN ID. If you have a line concentrator without having some differentiation mechanism to segregate traffics or networks, such as a Virtual Local Area Network (VLAN) identifier all physical bridge interfaces added will be part
MALC Configuration Guide
249
Configuring bridges
of the same bridge. So the line concentrator is creating a Local Area Network (LAN), albeit with a powerful uplink toward the Internet and little security.
VLANs In the Internet access model, security is extremely important. Subscribers should not have any access to information from other subscribers. Without the VLAN segregator all devices physically connected share traffic. For example; with VLANs, you can segregate traffic, so a group of point of purchase devices on the pumps at gas stations can be segregated from residential customers or other business customers which may be physically connected to the same MALC To build the Internet access model you would use two asymmetric bridge interface types — uplink and downlinks. Like the line concentrator you would configure an uplink bridge interface on the high speed upstream connection and downlinks on the downstream connections to subscribers. In addition you would define the downlinks, the connections pointing to subscribers with unique VLAN IDs. These VLAN identifiers allow several subscribers to use the same physical interfaces, but only be able to access traffic which belongs to them (as defined by the VLAN ID). VLANs provide a secure network which appears like a LAN only that the network is not local, but may be distributed across the Internet. Tagging is the mechanism for segregating layer 2 traffic without leaking information between networks.
250
MALC Configuration Guide
Bridges: line concentrator, Internet access model, intralink, TLS, hub
Figure 25: With the VLAN mechanism traffic is segregated
VLAN 100 Packet out
Packet in
source addresses to database
uplink
uplink
VLAN 100
downlinks
VLAN 100
Learns source address on ingress on the dowlink interface
Packet in If downstream device is not tagged MALC adds tag, and packet with tag is sent out the uplink
Packet out
downlinks
finds address in learned MAC address database Send out to interface where address was learned (With Ethernet and VLAN mapping only possible locations are matching VLAN ID locations)
If a downstream device on a downlink is not tagged as a VLAN and the downlink interface is set as a VLAN and is the only VLAN on that interface — traffic which enters on that interface will be given the VLAN tag and the packet with the VLAN tag inserted will be transmitted on the uplink. The downlink bridge add command would have “downlink vlan xxx,” where xxx is the VLAN ID. This command sets the downlink, both for packets received on the uplink to forward to the proper downlink as well as the source packets received on the downlink. For an example see Configuring the Internet access model, page 252, step 3. The uplink command by default leaves the inserted tag for transmission on the uplink. If the downlink is configured to expect tagged traffic by using the downlink command with “downlink vlan xxx tagged,” then the downlink interface will only accept packets which have the appropriate tag. The dowlink will not insert a tag; the packet will be discarded. For an example see Configuring the line concentrator, page 246, step 4.
MALC Configuration Guide
251
Configuring bridges
Figure 26: Example VLAN network
You can configure static VLAN bridge paths, which requires that you enter a MAC address for every bridge on the Ethernet. Or, you can set up the MALC Ethernet interface to learn the VLAN IDs when it receives a packet from a downlink device. Note that if the MALC receives a packet from an uplink interface before it has learned the VLAN ID or MAC address, it will not deliver the packet. Figure 27: Learning a VLAN ID
Configuring the Internet access model For the Internet access model you need to specify an uplink, the downlinks and a bridge-path to send packets received on the downlinks. To provide the secure segregation of traffic you need to designate VLANs. Without VLANs all traffic would be shared. 1
Add a bridge interface on the uplink card bridge add 1-1-2-0/eth uplink
252
MALC Configuration Guide
Bridges: line concentrator, Internet access model, intralink, TLS, hub
2
Add a global bridge path so that all traffic from the downlinks are forwarded out the uplink bridge-path add ethernet2-0/bridge global
3
Add bridge interfaces on the downlink cards and associate VLAN IDs Note that the card in slot 4, port 1 can be configured so that multiple VLANs may be on a single port. bridge add 1-4-1-0/eth downlink vlan 100 bridge add 1-4-1-0/eth downlink vlan 200 bridge add 1-4-3-0/eth downlink vlan 200
The port 1 on the card in slot 4 has two VLANs. This configuration displays that traffic on a single port can be segregated to multiple VLANs. 4
Add a downlink interface This example shows how to extend this model with another line concentrator downstream. bridge add 1-4-4-0/eth downlink tagged vlan 500
What the “tagged vlan 500” means is that the interface will only accept traffic which is already tagged and the VLAN identifier is “500.” All other traffic on that interface, as it is configured in this example, would be discarded. Figure 28: A VLAN configuration including tagged VLAN on downlink
on VLAN 100 Uplink
Downlink to another MALC
VLAN 100 VLAN 200
VLAN 500 Downlinks
on VLAN 100
on VLAN 200
on VLAN 500
MALC Configuration Guide
253
Configuring bridges
The device which is downstream which may be another MALC must be configured with a downlink with vlan 500. Other devices on the Internet which are designated to share that same VLAN ID will be able to share traffic.
254
MALC Configuration Guide
Bridges: line concentrator, Internet access model, intralink, TLS, hub
Internet access model with intralinked MALCs The common case for an asymmetric bridge has the downlinks learning on sending and the uplinks forwarding on reception from outside of the MALC. If a packet is sent from a downlink, the MAC address is learned. If the packet in on the uplink has a known address it is forwarded to that address. If the packet is unknown it is discarded. This situation does not satisfy all configurations. The intralink bridge interface addresses another case. In a case where you have multiple line concentrators linked, one below another, it is possible for the forwarding table on the head MALC in the chain or the upper MALCs to grow to an unmanageable size because they would be learning the MAC addresses of all devices downstream as they send packets. If you add an intralink bridge interface, rather than learning the addresses connected to the intralink interface as they would from a downlink, they merely send all packets from the intralink interface to the uplink. Packets with unknown addresses received on the uplink interface are sent down the intralink interface. Unlike the example in Figure 28, which had a MALC setup as a downlink, so the upper MALC learned the MAC addresses of all devices sending on that downlink (all the devices on the lower MALC), the intralink does not build up a forwarding table. Figure 29: Line concentrator model with intralinks
Intralink Uplink
Downlinks
MALC Configuration Guide
255
Configuring bridges
An intralink bridge interface is used in conjunction with an uplink bridge interface, where the uplink bridge is the path upstream to the network. The intralink interface forwards traffic with unknown MAC addresses or multicasts to the configured bridge interface without attempting to learn the addresses of the attached devices or network. Traffic coming into the intralink interface is forwarded to the uplink regardless of the destination MAC address. Broadcasts, multicasts, and unicasts (known and unknown) will be sent out the default interface, which is the uplink bridge for the VLAN. In other words source addresses from an intralink interface are not learned, so the database of learned addresses will not add the address. Likewise when an unknown unicast packet is received on the uplink interface it will be transmitted to the intralink interface. Somewhere down the chain, the address may be known. Intralinks can be and normally are used in conjunction with Uplinks and can be used with downlinks, see the figure: Line concentrator model with intralinks, page 255. Intralink bridge interfaces require an additional configuration to take effect, which is a bridge-path. The bridge-path sets a default intralink path for either a specific VLAN or a global intralink for the system onto the intralink bridge. If an intralink is missing this configuration, traffic will not flow across the asymmetric VLAN. All three asymmetric bridge interface types — uplink, downlink, and intralink — may be used in a single bridge. Figure 30: The intralink portion of an asymmetric bridge message in
message out Unicast
Multicast Broadcast
uplink forwards
Unicast
Multicast Broadcast
uplink forwards
forwarding database
forwarding database downlinks forward
downlink forwards
Unicast
Multicast Broadcast
Unicast
Multicast
Broadcast
The general rule for intralinks is that input on the intralink is forwarded without the source address being learned. All packets with unknown addresses are forwarded to the intralink interface.
Configuring intralinked MALCs This example adds an intralink bridge interface to an asymmetric uplink/ downlink bridge. 1
Add a bridge interface on the uplink card bridge add 1-1-2-0/eth uplink
256
MALC Configuration Guide
Bridges: line concentrator, Internet access model, intralink, TLS, hub
2
Add a global bridge-path so the downlinks forward all packets to the uplink bridge-path add ethernet2-0/bridge global
3
Add a couple of downlinks Since the downlinks used in this example are DSL downlinks a few parameters need to be added to the bridge add command. “vc 0/35” defines the Virtual Path Identifier (VPI) and Virtual Circuit Identifier (VCI) values to configure the virtual circuit, since DSL is a circuit based technology. “td 1” defines the transport for the traffic. Other than additional settings for vc and td DSL connections use the same parameters. bridge add 1-5-1-0/shdsl vc 0/35 td 1 downlink vlan 100 bridge add 1-5-1-0/shdsl vc 0/38 td 2 downlink vlan 200
4
Add a bridge interface for the intralink bridge add 1-1-2-0/eth intralink
This command mainly defines the behavior that source addresses from the intalink will not be learned. 5
Add a bridge path bridge-path add ethernet2/bridge global-intralink
This command mainly defines the behavior that any packets with unknown addresses will be sent to the interlink.
MALC Configuration Guide
257
Configuring bridges
Transparent LAN service Transparent LAN services (TLS) are used when you want traffic freely flowing among a community of users. Much like asymmetric bridges TLS bridges normally use a VLAN ID to segregate traffic. Without VLANs a TLS bridge share traffic on all bridges, just like on a LAN. The VLAN segregates traffic for an extra A school district may use a TLS bridge with VLAN so that their users have access to the other users as if they were together on their own LAN. Unlike the asymmetric bridges, all interfaces in a TLS are treated the same. There is no designation of an uplink or a downlink. When describing the equal interfaces of a TLS bridge it is helpful to think in terms of ingress or egress on an interface. Figure 31: In a TLS bridge all interfaces learn & forward the same
VLAN 100
VLAN 100
Packet in Packet out ingress
downlinks VLAN 100
VLAN 100 source address learned finds MAC address database Send out to interface where address was learned
Packet out
(With Ethernet and VLAN mapping only possible locations are matching VLAN ID locations)
ingress
VLAN 100
Packet in
downlinks VLAN 100
source address learned finds MAC address database Send out to interface where address was learned
Packets entering the system on TLS interface have their source MAC addresses learned and associated with the interface so that frames from the network that come in on other TLS bridges in the VLAN can be sent to the correct interface.
258
MALC Configuration Guide
Bridges: line concentrator, Internet access model, intralink, TLS, hub
Figure 32: With TLS bridges all interfaces learn on ingress
message in
message out Unicast
Multicast Broadcast
Unicast
ingress learns
Multicast Broadcast
ingress learns
forwarding database
forwarding database egress forwards
egress forwards
Unicast
Multicast Broadcast
Unicast
Multicast Broadcast
Broadcasts and unknown multicasts are flooded out all interfaces except for the interface where received
A TLS bridge is used with only other TLS bridges. TLS bridges should not be used with any asymmetrical bridges. TLS bridges learn MAC addresses and forward packets to learned destinations. Broadcasts and unknown unicasts are flooded out all interfaces except the ingress interface.
Configuring a TLS bridge In this example we are adding a vlan member to a vlan (VLAN 200) which already has members on other devices. •
For each connection to the tls bridge add a tls bridge interface bridge bridge bridge bridge
add add add add
1-6-48-0/eth 1-3-22-0/eth 1-3-22-0/eth 1-4-17-0/eth
tls tls tls tls
vlan vlan vlan vlan
100 100 200 100
TLS bridges can be thought of as a community since they share traffic much in the way a physical LAN shares traffic.
MALC Configuration Guide
259
Configuring bridges
Hub bridge Like a TLS bridge all ports have the same learning and forwarding behavior, but in a hub bridge configuration there is no learning. With a hub bridge all traffic in on one interface is sent out on all other interface members of the hub, so no learning is necessary. A hub bridge interface connects only with other hub bridge interfaces. They are always used with VLANs to segregate traffic. Figure 33: All packets received are sent out all other interfaces
Packet in
Packet out no learning of source addresses to database
Packet in
Packet out Packet out
Packet out
Packet out Packet out
Packets entering the system on this interface do not have their source MAC addresses learned. Hub bridges flood packets of all types to every other hub bridge interface in the VLAN, where all ports receive every frame received on the hub interface. Figure 34: Hubs provide a straight through connection with no learning message in
message out Unicast
Multicast Broadcast
egress forwards
ingress forwards Unicast
Unicast
Multicast Broadcast
ingress forwads
egress forwards Multicast Broadcast
Unicast
Multicast Broadcast
All traffic recieved on any interface is transmitted out all other interfaces.
260
MALC Configuration Guide
Bridges: line concentrator, Internet access model, intralink, TLS, hub
Because the nature of a hub is to receive packets on one interface, then duplicate that packet to send out to all other members of the hub, the hub bridge requires a large amount of processing time and may affect the overall performance of the MALC.
Configuring a hub bridge This example shows three ports on two cards for the members of the hub bridge. Use the hub parameter to identify each member of the hub bridge. bridge add 1-6-48-0/eth hub vlan 100 bridge add 1-8-48-0/eth hub vlan 100 bridge add 1-8-47-0/eth hub vlan 100
Administrative commands The MALC provides the following administrative commands:
•
bridge delete
•
bridge show
•
bridge showall
•
bridge-path add
•
bridge-path show
•
bridge-path delete
•
bridge stats
•
bridge flush
Refer to the MALC CLI Reference Guide for a detailed explanation of the available bridge commands.
Bridge delete command The bridge delete command deletes a specific bridge entry from the system.
Bridge show/showall commands The bridge show and bridge showall commands display either a single bridge path entry or the entire bridge table.
Bridge stats The bridge stats command displays and clear bridge interface statistics for all bridges, bridges associated with a specified VLAN ID, and a specified bridge interface. zSH> bridge stats
MALC Configuration Guide
261
Configuring bridges
262
Interface Name 1-16-8-0-shdsl-0-35-835 1-16-8-0-shdsl-0-35-635 1-16-24-0-shdsl-0-35-835
Received Packets UCast MCast BCast 0 0 1 0 0 0 0 0 0
Transmitted Packets UCast MCast Bcast 0 0 0 0 0 0 0 0 0
Error 0 0 1
zSH> bridge stats vlan 835 Interface Name 1-16-8-0-shdsl-0-35-835 1-16-24-0-shdsl-0-35-835
Received Packets UCast MCast BCast 0 0 1 0 0 0
Transmitted Packets UCast MCast Bcast 0 0 0 0 0 0
Error 0 1
MALC Configuration Guide
Advanced bridging configurations
Advanced bridging configurations The options for the bridge add allow you to create the most common and most standard bridges. The macro commands create common and standard bridge interface records. However there is a greater level of control by modifying the parameters in the bridge interface record directly. This advanced section includes the following topics:
•
Bridge commands to display bridges and bridge interfaces, page 263
•
Settings for asymmetric bridges, page 265
•
Settings for symmetric bridges, page 266
•
VLAN single and double tagging, page 270
•
Shaping Traffic: Class of Service Queuing, page 281
•
Mechanism for multiple interface ingress filters, page 285
•
Destination MAC swapping, page 287
•
Bandwidth limiting by port and service, page 288
•
Broadcasts in asymmetric bridges, page 304
•
Bridge with DHCP relay, page 291
•
DHCP on bridge packet rules (DHCP relay, Option 82, PPPoE vendor tag, Forbid OUI), page 295
•
Access Control List, page 298
•
Broadcast suppression, page 312
•
RSTP support, page 312
•
Ethernet RPR, page 317
•
Linear GigaBit Ethernet, page 334
•
PPPoA - PPPoE Conversion, page 339
•
PPPoE Intermediate Agent, page 342
Bridge commands to display bridges and bridge interfaces Bridge show The bridge show command displays a single bridge path entry. The bridge show all displays the entire bridge table. zSH> bridge show Typ VLAN Bridge State Table Data -----------------------------------------------------------------------------------upl Tagged ethernet1/bridge UP S Global default [U: 3600 sec, M: 150 sec, I: 0 sec] 0 1-8-5-0-adsl-0-32/bridge PENDING
MALC Configuration Guide
263
Configuring bridges
dwn dwn dwn dwn dwn
0 0 0 0 0 0
1-8-4-0-adsl-0-32/bridge 1-8-10-0-adsl-0-35/bridge 1-8-11-0-adsl-0-35/bridge 1-12-1-0-shdsl-0-35/bridge 1-12-2-0-shdsl-0-35/bridge 1-9-1-0-adsl-0-35/bridge
PENDING PENDING PENDING PENDING PENDING DOWN
Verifying bridge interface settings To verify bridge settings, use the get bridge-interface-record command for each bridge interface, which displays the settings for the bridge interface. zSH> get bridge-interface-record ethernet1/bridge vpi: ----------------------> {0} vci: ----------------------> {0} vlanId: -------------------> {0} stripAndInsert: -----------> {false} customARP: ----------------> {true} filterBroadcast: ----------> {true} learnIp: ------------------> {false} learnUnicast: -------------> {false} maxUnicast: ---------------> {0} learnMulticast: -----------> {false} forwardToUnicast: ---------> {true} forwardToMulticast: -------> {true} forwardToDefault: ---------> {false} bridgeIfCustomDHCP: -------> {true} bridgeIfConfigGroupIndex: -> {0} vlanIdCOS: ----------------> {0} outgoingCOSOption: --------> {disable} outgoingCOSValue: ---------> {0} s-tagTPID: ----------------> {0x8100} s-tagId: ------------------> {0} s-tagStripAndInsert: ------> {false} s-tagOutgoingCOSOption: ---> {s-tagdisable} s-tagIdCOS: ---------------> {0} s-tagOutgoingCOSValue: ----> {0}
A bridge interface record is a set of parameters. The configuration of the different bridge interface parameters defines the behavior of the bridge interface. Bridge interfaces work together and the combination of the bridge interfaces is considered a bridge. Refer to the CLI Reference Guide for a complete description of the command options and syntax.
264
MALC Configuration Guide
Advanced bridging configurations
Settings for asymmetric bridges Table 15 lists the default asymmetric bridge-interface-record settings for the supported bridge options. Table 15: Default values for asymmetric bridge-interface-record Parameter
Uplink
Downlink
Downlink Tagged
Intralink
vpi
0 for Ethernet interfaces. As specified for other interfaces.
0 for Ethernet interfaces. As specified for other interfaces.
0 for Ethernet interfaces. As specified for other interfaces.
0 for Ethernet interfaces. As specified for other interfaces.
vci
0 for Ethernet interfaces. As specified for other interfaces.
0 for Ethernet interfaces. As specified for other interfaces.
0 for Ethernet interfaces. As specified for other interfaces.
0 for Ethernet interfaces. As specified for other interfaces.
vlanId
0
As specified
As specified
0
stripAndInsert
False
True
False
False
customARP
True
False
False
False
filterBroadcast
True
False
False
False
learnIP
False
True
True
False
learnUnicast
False
True
True
False
maxUnicast
0
5
5
0
learnMulticast
False
True
True
False
forwardToUnicast
True
False
False
False
forwardToMulticast
True
False
False
False
forwardToDefault
False
True
True
True
floodUnknown
False
False
False
False
floodMulticast
False
False
False
False
valndIdCOS
0
0
0
0
outgoingCOSOption
Disable
Disable
Disable
Disable
outgoingCOSValue
0
0
0
0
s-tagTPID
0x8100
0x8100
0x8100
0x8100
s-tagId
0
0
0
0
s-tagStripAndInsert
False
False
False
False
s-tagOutgoingCOSOption
s-tagdisable
s-tagdisable
s-tagdisable
s-tagdisable
s-tagIdCOS
0
0
0
0
MALC Configuration Guide
265
Configuring bridges
Table 15: Default values for asymmetric bridge-interface-record Parameter
Uplink
Downlink
Downlink Tagged
Intralink
s-tagOutgoingCOSValue
0
0
0
0
Settings for symmetric bridges Table 16 lists the default bridge-interface-record settings for the supported symmetric bridge options. Table 16: Default values for symmetric bridge-interface-record
266
Parameter
Tranparent
TLS
Hub
vpi
0 for Ethernet interfaces. As specified for other interfaces.
0 for Ethernet interfaces. As specified for other interfaces.
0 for Ethernet interfaces. As specified for other interfaces.
vci
0 for Ethernet interfaces. As specified for other interfaces.
0 for Ethernet interfaces. As specified for other interfaces.
0 for Ethernet interfaces. As specified for other interfaces.
vlanId
0
As specied
As specified
stripAndInsert
True
True
True
customARP
False
False
False
filterBroadcast
False
False
False
learnIP
False
False
True
learnUnicast
Truee
True
False
maxUnicast
5
100
0
learnMulticast
False
False
False
forwardToUnicast
True
True
False
forwardToMulticast
False
False
False
forwardToDefault
False
False
True
floodUnknown
False
True
True
floodMulticast
False
True
True
bridgeIfCustomDHCP
False
False
False
bridgeIfConfigGroupIndex
0
0
0
valndIdCOS
0
0
0
outgoingCOSOption
Disable
Disable
Disable
MALC Configuration Guide
Advanced bridging configurations
Table 16: Default values for symmetric bridge-interface-record Parameter
Tranparent
TLS
Hub
outgoingCOSValue
0
0
0
s-tagTPID
0x8100
0x8100
0x8100
s-tagId
0
0
0
s-tagStripAndInsert
False
False
False
s-tagOutgoingCOSOption
s-tagdisable
s-tagdisable
s-tagdisable
s-tagIdCOS
0
0
0
s-tagOutgoingCOSValue
0
0
0
The bridge show command displays the bridge type. zSH> bridge show Typ VLAN Bridge State Table Data -----------------------------------------------------------------------------------upl Tagged ethernet1/bridge UP S Global default [U: 3600 sec, M: 150 sec, I: 0 sec] 0 1-8-5-0-adsl-0-32/bridge PENDING 0 1-8-4-0-adsl-0-32/bridge PENDING dwn 0 1-8-10-0-adsl-0-35/bridge PENDING dwn 0 1-8-11-0-adsl-0-35/bridge PENDING dwn 0 1-12-1-0-shdsl-0-35/bridge PENDING dwn 0 1-12-2-0-shdsl-0-35/bridge PENDING dwn 0 1-9-1-0-adsl-0-35/bridge DOWN
Configuring a VLAN bridge with DSL Use the bridge add command to add a bridge for the downstream connection. Multiple VLAN interfaces can be added to the same physical port and VC. zSH> bridge add 1-8-1-0/adsl vc 0/35 td 1 downlink vlan 555 zSH> bridge add 1-8-1-0/adsl vc 0/36 td 1 downlink vlan 777
This example adds downlink VLAN interfaces to the ADSL modem in shelf 1, slot 8, port 1 with VLAN IDs of 555 and 777. It uses the VCLs 0/35 and 0/ 36, traffic descriptor 1 as a transport, sets the parameters to the downlink settings, and assigns port VLAN ID 555 and 777. The following bridge-interface-record is created with the downlink default settings and shows the internal VPI/VCI cross connects. It is recommended not to change the default settings unless advanced bridge configuration is required. zSH> get bridge-interface-record 1-8-1-0-adsl-0-35-555/bridge vpi: ----------------------> {0} vci: ----------------------> {35} vlanId: -------------------> {555} stripAndInsert: -----------> {true}
MALC Configuration Guide
267
Configuring bridges
customARP: ----------------> filterBroadcast: ----------> learnIp: ------------------> learnUnicast: -------------> maxUnicast: ---------------> learnMulticast: -----------> forwardToUnicast: ---------> forwardToMulticast: -------> forwardToDefault: ---------> bridgeIfCustomDHCP: -------> bridgeIfConfigGroupIndex: -> vlanIdCOS: ----------------> outgoingCOSOption: --------> outgoingCOSValue: ---------> s-tagTPID: ----------------> s-tagId: ------------------> s-tagStripAndInsert: ------> s-tagOutgoingCOSOption: ---> s-tagIdCOS: ---------------> s-tagOutgoingCOSValue: ----> mcastControlList: ---------> maxVideoStreams: ----------> isPPPoA: ------------------> floodUnknown: -------------> floodMulticast: ----------->
{false} {false} {true} {true} {5} {true} {false} {false} {true} {false} {0} {0} {disable} {0} {0x8100} {0} {false} {s-tagdisable} {0} {0} {0} {0} {false} {false} {false}
zSH> get bridge-interface-record 1-8-1-0-adsl-0-35-777/bridge vpi: ----------------------> {0} vci: ----------------------> {35} vlanId: -------------------> {777} stripAndInsert: -----------> {true} customARP: ----------------> {false} filterBroadcast: ----------> {false} learnIp: ------------------> {true} learnUnicast: -------------> {true} maxUnicast: ---------------> {5} learnMulticast: -----------> {true} forwardToUnicast: ---------> {false} forwardToMulticast: -------> {false} forwardToDefault: ---------> {true} bridgeIfCustomDHCP: -------> {false} bridgeIfConfigGroupIndex: -> {0} vlanIdCOS: ----------------> {0} outgoingCOSOption: --------> {disable} outgoingCOSValue: ---------> {0} s-tagTPID: ----------------> {0x8100} s-tagId: ------------------> {0} s-tagStripAndInsert: ------> {false} s-tagOutgoingCOSOption: ---> {s-tagdisable} s-tagIdCOS: ---------------> {0} s-tagOutgoingCOSValue: ----> {0} mcastControlList: ---------> {0} maxVideoStreams: ----------> {0} isPPPoA: ------------------> {false}
268
MALC Configuration Guide
Advanced bridging configurations
floodUnknown: -------------> floodMulticast: ----------->
{false} {false}
Use the bridge add command to add a VLAN interface to the upstream Ethernet interface: zSH> bridge add 1-1-1-0/ethernetcsmacd uplink
This command adds a learning bridge that accepts VLAN traffic and enables VLAN trunking on the MALC unit’s egress Ethernet port. Configure the uplink interface to learn the VLAN IDs of all ingress Ethernet devices or a specific VLAN ID: zSH> bridge-path add ethernet1/bridge global
The global setting specifies that the MALC should send all VLAN traffic to this port. A VLAN ID can also be used when the MALC should send only traffic from a specific VLAN ID to this port. (The ethernet1 interface is the first Ethernet interface on the MALC.) It is recommended not to change the default settings unless advanced bridge configuration is required. zSH> get bridge-interface-record ethernet1/bridge vpi: ----------------------> {0} vci: ----------------------> {0} vlanId: -------------------> {0} stripAndInsert: -----------> {false} customARP: ----------------> {true} filterBroadcast: ----------> {true} learnIp: ------------------> {false} learnUnicast: -------------> {false} maxUnicast: ---------------> {0} learnMulticast: -----------> {false} forwardToUnicast: ---------> {true} forwardToMulticast: -------> {true} forwardToDefault: ---------> {false} bridgeIfCustomDHCP: -------> {false} bridgeIfConfigGroupIndex: -> {0} vlanIdCOS: ----------------> {0} outgoingCOSOption: --------> {disable} outgoingCOSValue: ---------> {0} s-tagTPID: ----------------> {0x8100} s-tagId: ------------------> {0} s-tagStripAndInsert: ------> {false} s-tagOutgoingCOSOption: ---> {s-tagdisable} s-tagIdCOS: ---------------> {0} s-tagOutgoingCOSValue: ----> {0} mcastControlList: ---------> {} maxVideoStreams: ----------> {0} isPPPoA: ------------------> {false} floodUnknown: -------------> {false} floodMulticast: -----------> {false}
Verify connectivity by pinging a far end device on the VLAN.
MALC Configuration Guide
269
Configuring bridges
VLAN single and double tagging Packets which have a VLAN ID are tagged packets. Packets which have both a VLAN ID and a second tag, an SLAN ID are double-tagged (or also called s-tagged or Q in Q). If the packet does not have a VLAN ID or SLAN ID then the packet is untagged. There are three distinct cases of tagging (including untagged):
•
Untagged packets Untagged bridges forward traffic based on MAC addresses but do not further segregate traffic. Traffic is broadcast over the Ethernet port and is either accepted or rejected based on the destination MAC address. In other words, there is no VLAN tagging; all ports are learning and forwarding without restriction and without broadcast suppression. Forwarding to a default port is not allowed.
•
Tagged packets Tagged bridges forward traffic based on the logical VLAN ID number. This tagging allows the segregation of a single Ethernet network into multiple virtual network segments.
•
Double tagged packets Double tagging expands the VLAN space in the Ethernet frame, so that you may further segregate traffic. The packet is differentiated by VLAN ID and SLAN ID. This second tag gives a whole other layer, so you can have VLAN 100 which may be a department in a global organization, and VLAN 100, SLAN 200 be one group within that department.
The packets which come into the MALC are untagged, tagged and double tagged. The tagged values will be from 1 to 4094. VLAN packets are tagged, however that is half of the solution, the bridges to the destination, or more precisely, the bridge interfaces must be configured to accept packets. In the bridge add command you define the VLAN ID and SLAN ID using the vlan parameter and the slan parameter: zSH> bridge add 1-3-1-0/adsl downlink vlan 500 slan 120
You may also set bridge interfaces to accept wildcards. You can set the VLAN ID (vlanID parameter in the bridge interface record) and the SLAN ID (s-tagId) to zero. Zero is a value that cannot be in the packet, but is used like a wildcard (much like * in Unix or Windows searches). If the VLAN ID is set to 100 and the SLAN ID is set to zero, it means that bridge interface will accept any packets which have VLAN ID 100. If another bridge interface is set to VLAN ID 100 and SLAN ID 200, it will only accept packets which meet both criteria. The following snippets from a bridge interface record show the case where both VLAN ID and SLAN ID are set to zero. On this interface it will accept all packets which are either single tagged or double tagged.
270
MALC Configuration Guide
Advanced bridging configurations
vlanId: -------------------> stripAndInsert: -----------> ...
{0} {false}
s-tagTPID: ----------------> {0x8100} s-tagId: ------------------> {0} s-tagStripAndInsert: ------> {false} s-tagOutgoingCOSOption: ---> {s-tagdisable} s-tagIdCOS: ---------------> {0} s-tagOutgoingCOSValue: ----> {0} To configure the bridge interface record, you omit the VLAN or SLAN ID when using the tagged or stagged parameters in the bridge add command. To configure the bridge interface record for VLAN 100, SLAN 200 zSH> bridge add 1-3-*-0/adsl downlink vlan 500 slan 200
To configure the bridge interface record for VLAN 100, SLAN 0 zSH> bridge add 1-3-*-0/adsl downlink vlan 500 stagged
To configure the bridge interface record for VLAN 0, SLAN 200 zSH> bridge add 1-3-*-0/adsl downlink vlan 500 stagged
To configure the bridge interface record for VLAN 0, SLAN 0 zSH> bridge add 1-3-*-0/adsl downlink stagged
Note: The MALC ports can support both IP termination or bridging on different virtual circuits. However, each virtual circuit must be configured for either IP termination or bridging and cannot support both at the same time. Note: When routed and bridged traffic is configured for the same uplink interface, VLAN tags must be used between both downlink ports and the uplink interface for traffic differentiation. For routed traffic, use the ip-interface-record profile to specify the VLAN ID. Figure 26 shows a typical VLAN configuration. On the access (subscriber) side, VLANs 1 and 2 are separate DSL networks connected to the MALC via Ethernet access devices. On the uplink side, VLANs 1 and 2 are on the same physical Ethernet interface, but the traffic is separated based on the VLAN IDs. The side of the connection closest to the subscriber is called the downlink interface. The upstream egress is called the uplink interface. When the MALC is in VLAN mode, it adds (tags) the VLAN ID to the Ethernet frame on the uplink interface and strips (untags) the ID out on the downlink interface. Note: The MALC supports VLAN IDs from 1 to 4096. Multiple VLAN interfaces can be added to the same physical port and VC.
MALC Configuration Guide
271
Configuring bridges
Untagged VLAN bridges Untagged VLAN bridges enable you to forward traffic from a downlink interface through the MALC uplink interface based on the destination MAC address without tagging or modification to the frame. Refer to the CLI Reference Guide for a complete description of the command options and syntax. Note: Ethernet interfaces can be addressed as either eth or ethernetcsmacd. The eth abbreviation is used in command output.
Configuring an untagged bridge To add an untagged bridge: 1
Add an untagged bridge to the downstream DSL interface:
zSH> bridge add 1-8-2-0/adsl vc 0/101 td 1 Created bridge-interface-record 1-8-2-0-adsl-0-101/bridge
This example adds a default transparent bridge interface to the ADSL modem in shelf 1, slot 8, port 2. It uses the VCL 0/101 and traffic descriptor 1 as a transport and sets the parameters to the default transparent bridge interface settings. The following examples shows the default bridge-interface-record settings with the internal vpi/vci cross connects. It is recommended not to change the default settings unless advanced bridge configuration is required. zSH> get bridge-interface-record 1-8-2-0-adsl-0-101/bridge vpi: ----------------------> {0} vci: ----------------------> {101} vlanId: -------------------> {0} stripAndInsert: -----------> {true} customARP: ----------------> {false} filterBroadcast: ----------> {true} learnIp: ------------------> {true} learnUnicast: -------------> {true} maxUnicast: ---------------> {5} learnMulticast: -----------> {true} forwardToUnicast: ---------> {false} forwardToMulticast: -------> {false} forwardToDefault: ---------> {true} bridgeIfCustomDHCP: -------> {false} bridgeIfConfigGroupIndex: -> {0}
2
Add a transparent bridge to the upstream Ethernet interface:
zSH> bridge add 1-1-1-0/ethernetcsmacd Created bridge-interface-record 1-1-1-0-ethernetcsmacd/bridge
272
MALC Configuration Guide
Advanced bridging configurations
This command adds a bridge that accepts transparent/untagged traffic on the MALC units’s egress Ethernet port. The following shows the default transparent bridge-interface-record settings for the uplink. It is recommended not to change the default settings unless advanced bridge configuration is required. zSH> get bridge-interface-record ethernet1/bridge vpi: ----------------------> {0} vci: ----------------------> {0} vlanId: -------------------> {0} stripAndInsert: -----------> {false} customARP: ----------------> {true} filterBroadcast: ----------> {true} learnIp: ------------------> {false} learnUnicast: -------------> {false} maxUnicast: ---------------> {0} learnMulticast: -----------> {false} forwardToUnicast: ---------> {true} forwardToMulticast: -------> {true} forwardToDefault: ---------> {false} bridgeIfCustomDHCP: -------> {false} bridgeIfConfigGroupIndex: -> {0}
3
Verify that both sides of the bridge are present:
zSH> bridge show Typ VLAN Bridge State Table Data ----------------------------------------------------------------dwn 0 1-8-2-0-adsl-0-101/bridge UP upl 0 1-1-1-0-ethernetcsmacd/bridge UP
4
Test the bridge by pinging a device on the far end network and verifying e that the bridge table is updated:
zSH> bridge show Typ VLAN Bridge State Table Data ----------------------------------------------------------------dwn 0 1-8-2-0-adsl-0-101/bridge UP D 00:01:47:cf:ae:04 upl 0 1-1-1-0-ethernetcsmacd/bridge UP D 00:01:02:70:03:a2
Strip and Insert The stripAndInsert parameter is used to change the stripping and inserting of VLAN tags. All packets within the MALC are double tagged upon entering the MALC for performance reasons even if the received packet is untagged or single tagged. If a tag is missing it is given a unique tag to denote the tag is missing. In this manner all packets without tags are handled similarly. In most configurations, VLAN IDs should be stripped for traffic destined to downlink interfaces and inserted for traffic destined for upstream interfaces. Downlink interfaces typically do not need to know the VLAN ID since they are on a single Ethernet. You can, however, specify that a downlink interface be tagged, or an uplink interface be untagged.
MALC Configuration Guide
273
Configuring bridges
You might want to have downlink interfaces to be tagged if you are subtending MALC devices and uplinks to be untagged if you are aggregating Ethernet traffic.
Configuring stripAndInsert Configure the bridge-interface-record to change the stripping and insert of VLAN tags for a specified interface. To change the stripAndInsert option: zSH> update bridge-interface-record 1-3-1-0-adsl-0-35/bridge Please provide the following: [q]uit. vpi: ----------------------> {0}: vci: ----------------------> {39}: vlanId: -------------------> {46}: stripAndInsert: -----------> {true}: false customARP: ----------------> {false}: filterBroadcast: ----------> {false}: learnIp: ------------------> {true}: learnUnicast: -------------> {true}: maxUnicast: ---------------> {5}: learnMulticast: -----------> {true}: forwardToUnicast: ---------> {false}: forwardToMulticast: -------> {false}: forwardToDefault: ---------> {true}: bridgeIfCustomDHCP: -------> {false}: bridgeIfConfigGroupIndex: -> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Double tagged bridges (Q-inQ or s-tag) The IEEE 802.1Q-in-Q VLAN tagging expands the VLAN space in the Ethernet frame to support the tagging of previously tagged packets. This second tag (SLAN) creates a "double-tagged" Ethernet frame. The double-tagged Ethernet frame enables service providers to offer additional services, such as Internet access on specific SLANs for specific customers, while still providing single-tagged VLAN services. The MALC also supports setting COS values in the Ethernet SLAN headers for bridged packets. This service enables you to assign a service level or class of service (COS) to an Ethernet SLAN that is transported across a uplink, intralink, or downlinked s-tagged bridge. The configured COS level specifies the packet priority and queueing methods used to transport the packet through the Ethernet network. The MALC sets and preserves the COS settings to ensure these settings are passed to other Ethernet devices in the network for QOS processing. Note: Ethernet interfaces can be addressed as either eth or ethernetcsmacd. The eth abbreviation is used in command output.
274
MALC Configuration Guide
Advanced bridging configurations
Figure 35 illustrates a network of MALC devices configured to support separate SLANs per MALC while also providing individual VLANs per customer port. Figure 35: Q-in-Q Bridging
MALC Configuration Guide
275
Configuring bridges
Configuring Q-in-Q using the Bridge command For Q-in-Q VLAN tagging, the bridge profile supports the following parameters:
•
s-tagTPID Identifies the type of VLAN ID used. Typically set to 8100.
•
s-tagID Specifies the SLAN ID assigned to an Ethernet frame.
•
s-tagStripAndInsert Specifies whether to strip and insert s-tag values in Ethernet frames received and transmitted on the bridge interface.
•
s-tagOutgoingCOSOption Specifies whether to insert COS value bits on outgoing s-tag packets.
•
s-tagIDCOS Specifies the COS ID associated with the SLAN ID
•
s-tagOutgoingCOSValue Specifies the value used to overwrite any existing COS value in outgoing s-tag packets.
Syntax bridge add The bridge command supports adding s-tagIDs from the command line. This example adds interface 1-8-22-0/adsl with VLAN 100, SLAN 101, COS value of 7 and sCOS value of 8. bridge add 1-8-22-0/adsl vc 0/35 td 20000 downlink vlan 100 slan 200 tagged COS 7 scos 8
To display the bridge-record profile, enter the show bridge-interface-record or bridge show command. zSH> show bridge-interface-record 1-8-22-0-adsl-0-35/bridge vpi: ----------------------> {0} vci: ----------------------> {32} vlanId: -------------------> {100} stripAndInsert: -----------> {true} customARP: ----------------> {false} filterBroadcast: ----------> {false} learnIp: ------------------> {true} learnUnicast: -------------> {true} maxUnicast: ---------------> {5} learnMulticast: -----------> {false} forwardToUnicast: ---------> {false} forwardToMulticast: -------> {false} forwardToDefault: ---------> {true} bridgeIfCustomDHCP: -------> {false} bridgeIfConfigGroupIndex: -> {0}
276
MALC Configuration Guide
Advanced bridging configurations
vlanIdCOS: ----------------> outgoingCOSOption: --------> outgoingCOSValue: ---------> s-tagTPID: ----------------> s-tagId: ------------------> s-tagStripAndInsert: ------> s-tagOutgoingCOSOption: ---> s-tagIdCOS: ---------------> s-tagOutgoingCOSValue: ----> mcastControlList: ---------> maxVideoStreams: ----------> isPPPoA: ------------------> floodUnknown: -------------> floodMulticast: ----------->
{7} {disable} {0} {0x8100} {200} {true} {s-tagdisable} {8} {0} {0} {0} {false} {false} {false}
zSH> bridge show Typ VLAN Bridge State Table Data ----------------------------------------------------------------100/200 ethernet1/bridge UP D 00:50:04:df:c0:7a Upl Tagged uplink1-0-101/bridge UP S VLAN 100 default [3600 sec]
Configuring Q-in-Q using the Interface command For Q-in-Q VLAN tagging, the interface profile supports the following parameters:
•
s-tagTPID Identifies the type of VLAN ID used. Typically set to 8100.
•
s-tagID Specifies the SLAN ID assigned to an Ethernet frame.
•
s-tagIDCOS Specifies the COS ID associated with the SLAN ID
The interface command supports adding s-tagIDs from the command line. This example adds interface ethernet1 with VLAN 100, SLAN 200, COS value of 7 and sCOS value of 8. interface add ethernet1/ip vc 0/35 td 20000 other vlan 100 slan 200 cos 7 scos 8 172.16.88.46 255.255.255.0 zSH> get ip-interface-record ethernet1/ip vpi: ---------------> {0} vci: ---------------> {0} rdindex: -----------> {1} dhcp: --------------> {none} addr: --------------> {172.16.88.46} netmask: -----------> {255.255.255.0} bcastaddr: ---------> {172.16.88.255} destaddr: ----------> {0.0.0.0} farendaddr: --------> {0.0.0.0}
MALC Configuration Guide
277
Configuring bridges
mru: ---------------> reasmmaxsize: ------> ingressfiltername: -> egressfiltername: --> pointtopoint: ------> mcastenabled: ------> ipfwdenabled: ------> mcastfwdenabled: ---> natenabled: --------> bcastenabled: ------> ingressfilterid: ---> egressfilterid: ----> ipaddrdynamic: -----> dhcpserverenable: --> subnetgroup: -------> unnumberedindex: ---> mcastcontrollist: --> vlanid: ------------> maxVideoStreams: ---> tosOption: ---------> tosCOS: ------------> vlanCOS: -----------> s-tagTPID: ---------> s-tagId: -----------> s-tagIdCOS: -------->
{1500} {0} {} {} {no} {yes} {yes} {yes} {no} {yes} {0} {0} {static} {false} {0} {0} {} {100} {0} {disable} {7} {0} {0x8100} {200} {8}
Bridge path support for s-tags For Q-in-Q VLAN tagging, the bridge path profile supports the s-tagID parameter to specifies the SLAN ID assigned to an Ethernet frame in static bridge configurations. The bridge-path command supports adding s-tagIDs from the command line. This example creates a static bridge between an interface and a specific IP address and VLAN 300. It also adds an SLAN of 400 zSH> bridge-path add 1-1-4-0/ds3 vlan 300 slan 400 ip 192.16.80.1
To display bridge-path interface records with vlan and slan values, use the bridge-path show command. zSH> bridge-path show Typ VLAN/SLAN Bridge Address -------------------------------------------------------------------Upl 300/400 uplink1-0-101/bridge Default
278
MALC Configuration Guide
Advanced bridging configurations
TLS Bridging behavior for untagged, tagged, and s-tagged Bridges also utilize VLAN and SLAN tagging for untagged, tagged, and s-tagged traffic segregation.
•
Untagged bridging On a TLS bridge untagged bridging accepts and sends traffic based on MAC addresses but does not provide further traffic segregation like with an asymmetric bridge. Traffic is broadcast over the Ethernet port and is either accepted or rejected based on the destination MAC address. There is no VLAN tagging; all ports are learning and forwarding without restriction, without broadcast suppression. Forwarding to a default port is not allowed. If bridge forwarding selects a single or double-tagged egress interface, the configured VLAN and SLAN tags will be inserted in to packets destined for this interface. Only non-zero values are recommended for VLAN and SLAN settings of untagged bridges.
•
Tagged bridging Tagged bridging, accepts single-tagged packets based on MAC addresses and allows the segregation of a single Ethernet network into multiple virtual network segments by mapping packets based on the VLAN ID. The VLAN value 0 is used as a default VLAN designation. If a VLAN of 0 (zero) is configured, the interface accepts all VLAN tagged packets not matching any configured VLANs on the same interface. If a non-zero VLAN ID is configured the segregation proceeds normally, the interface accepts only tagged packets matching the VLAN ID.
•
Double tagged (s-tagged) Double-tagged or Service LANs (SLANs) bridging, accepts and sends double-tagged traffic based on MAC addresses and allows the segregation of a single Ethernet network into multiple virtual network segments by mapping packets based on VLAN ID and SLAN ID. Zero values for VLAN and SLAN IDs create a default VLAN and SLAN designation. If a VLAN of 0 (zero) is configured with a non-zero SLAN ID, the interface accepts and sends only double-tagged packets matching the SLAN and any VLAN tagged packets not destined to another client on the same interface. If non-zero VLAN ID and SLAN ID are configured, the interface accepts and sends only tagged packets matching both VLAN ID and SLAN ID. When both the VLAN and SLAN tags are zero (0), the bridge accepts all single or double tagged packets not destined to another client on the same interface. A configured SLAN tag is inserted into outgoing packets when bridge forwarding selects a double-tagged egress interface. Only non-zero SLAN values are recommended for tagged bridges.
MALC Configuration Guide
279
Configuring bridges
Tagged, VLAN tagged, and SLAN tagged examples For VLAN tagged (single tagged) bridges, the bridge interface name includes the VLAN ID, even the default VLAN ID of 0. Other examples of a single tagged bridge also show a tagged bridge with VLAN 4000 and a tagged bridge with VLAN 1000 and SLAN 17. zSH> bridge add 1-3-5-0/eth tagged zSH> bridge add 1-3-5-0/eth vlan 4000 tagged zSH> bridge add 1-3-5-0/eth vlan 1000 slan 17 tagged zSH> bridge show Typ VLAN Bridge State Table Data -----------------------------------------------------------------------------Tagged 1-3-5-0-eth-0/bridge PENDING Tagged 4000 1-3-5-0-eth-4000/bridge PENDING Tg 1000/17 1-3-5-0-eth-1000/bridge PENDING
For VLAN and SLAN tagged (double tagged) bridges, the bridge interface name includes the VLAN ID and SLAN ID, even the default VLAN ID of 0 and the default SLAN of 0. Other examples of doubled tagged bridges also show a bridge with VLAN 4094 and SLAN 4094, a bridge with VLAN 0 and SLAN 17, and a bridge with VLAN 500 and default SLAN. zSH> zSH> zSH> zSH>
bridge bridge bridge bridge
add add add add
1-3-5-0/eth 1-3-5-0/eth 1-3-5-0/eth 1-3-5-0/eth
vlan 4094 slan 4094 stagged vlan 0 slan 17 stagged stagged vlan 500 stagged
zSH> bridge show Typ VLAN Bridge State Table Data -----------------------------------------------------------------------------ST 4094/4094 1-3-5-0-eth-4094-4094/bridge PENDING ST 0/17 1-3-5-0-eth-0-17/bridge PENDING stagged 1-3-5-0-eth-0-0/bridge PENDING Tagged 500 1-3-5-0-eth-500-0/bridge PENDING
Bridges can be deleted by specified VLAN ID, SLAN ID, type of tagging, and all option. Specifying a VLAN ID all single and double tagged bridges configured for that VLAN. To delete a bride by a specific SLAN tag: zSH> bridge delete 1-3-5-0/eth slan 17
To delete a bridge by a specific VLAN tag or tag type: zSH> bridge delete 1-3-5-0/eth vlan 500 zSH> bridge delete 1-3-5-0/eth tagged
To delete all s-tagged bridges on a port: zSH> bridge delete 1-3-5-0/eth stagged all
280
MALC Configuration Guide
Advanced bridging configurations
To delete all VLAN 0 bridges on a port: zSH> bridge delete 1-3-5-0/eth vlan 0 all
Shaping Traffic: Class of Service Queuing Class of Service (CoS) queuing controls traffic to optimize or guarantee performance. This shaping of traffic generally exists to increase bandwidth so you can get more throughput to a device, or to decrease latency, so you do not have jitter in time sensitive data streams as in voice or video. Congestion happens for various reasons. If you have a higher bandwidth line feeding into a smaller bandwidth line, or if you have multiple similar size lines feeding into a single line. Both of these can be considered feeding too much data (a big pipe) into a small pipe. Queuing defines which VLAN will be able to use how much of the physical interface. The MALC supports setting CoS values in Ethernet VLAN headers for bridged packets. This service enables you to assign a service level or CoS to an Ethernet VLAN interface that is transported across a uplink, intralink, or downlinked tagged bridge. The configured CoS level specifies the packet priority and queueing methods used to transport the packet through the Ethernet network. The MALC sets and preserves the CoS settings to ensure these settings are passed to other Ethernet devices in the network for QoS processing. CoS values range from 0 — 7, with the lowest priority being 0 and the highest priority 7. However, the MALC support four queues per physical interface, so frames with a 0 or 1 CoS value are put into queue number 1; frames with a 2 or 3 CoS value are put into queue number 2; frames with a 4 or 5 in queue number three; and 6 or 7 in queue number 4. These are strict priority queues which mean that everything is cleared out of the high priority queue first (queue number 4 with CoS values 6 or 7) Only after that queue is empty is the next queue (number 3) serviced. Since these are strict priority queues it is possible that the lower priority queues may get overloaded while the higher priority queues are being cleared. Frames which require the highest throughput or are sensitive to latency (the amount of time between received packets) should be in higher priority queues. Since queuing is relative to the type of traffic, the priority settings depend on the type of traffic. Normally video and voice are more sensitive to throughput and latency issues.
MALC Configuration Guide
281
Configuring bridges
Figure 36: Setting queue priorities
Data
Video/Voice
lowest priority
highest priority
Queue Queue Queue Queue 1 2 3 4
Where CoS queuing takes place is dependent on the cards involved. GPON and Active Ethernet cards have queuing performed on the line card. For ADSL the queuing takes place on the uplink card. Figure 37: Where queuing takes place is card dependent
GPON and Active Ethernet VLAN 1
VLAN 2
VLAN 3
Physical Interface
282
MALC Configuration Guide
ADSL
VLAN 4
VLAN 1
VLAN 2
VLAN 3
Physical Interface
Advanced bridging configurations
Configuring Class of Service The following parameters in the bridge interface record are used for Ethernet COS support. Parameter
Description
vlanIdCOS
Specifies the value loaded into the COS field of the VLAN header when an untagged packet received on this interface is tagged (VLAN ID inserted) for bridging. Value range is 0 to 7. Default is 0.
outgoingCOSOption
Specifies whether to insert the VLAN COS bits on packets bridged through this interface. Values: Disable Leave any existing COS values unchanged. This is the default value. All Replace the current COS values in all VLAN headers in tagged and untagged packets originating and transported through this device.
outgoingCOSValue
For outgoing tagged packets, specifies the value used to overwrite any existing COS value in the VLAN header. Value range is 0 to 7. Default is 0.
To display the bridge-record profile, enter the show bridge-interface-record command. rpr-uplink-zSH> show bridge-interface-record vpi:----------------------> {0} vci:----------------------> {0} vlanId:-------------------> {0 - 2147483647} stripAndInsert:-----------> false true customARP:----------------> false true filterBroadcast:----------> false true learnIp:------------------> false true learnUnicast:-------------> false true maxUnicast:---------------> {0 - 2147483647} learnMulticast:-----------> false true forwardToUnicast:---------> false true forwardToMulticast:-------> false true forwardToDefault:---------> false true bridgeIfCustomDHCP:-------> false true bridgeIfConfigGroupIndex:-> {0 - 2147483647} vlanIdCOS:----------------> {0 - 7} outgoingCOSOption:--------> disable all outgoingCOSValue:---------> {0 - 7}
Adding an interface with a CoS value This example adds interface 1-1-1-0/adsl with a COS value of 7. interface add 1-1-1-0/adsl other vlan 1 cos 7 23.23.23.23 255.255.255.0
MALC Configuration Guide
283
Configuring bridges
This example adds interface 1-1-1-0/adsl with a COS value of 1 and specifies to add this value to all packets originating from this interface. interface add 1-1-1-0/adsl other vlan 1 cos 1 tosOrig 1 23.23.23.23 255.255.255.0
This example adds interface 1-1-1-0/adsl with a COS value of 5 and specifies to add the value to all outgoing packets on this interface. interface add 1-1-1-0/adsl other tos all cos 5 23.23.23.23 255.255.255.0
This example adds interface 1-1-1-0/adsl and disables the TOS feature. interface add 1-1-1-0/adsl other tosDisable 23.23.23.23 255.255.255.0
Adding a bridge with a CoS value This example adds interface 1-1-1-0/adsl with a vlanIDCOS value of 7. This value is inserted into the priority field of the VLAN header when an untagged packet received on this interface is tagged (VLAN ID inserted) for bridging. bridge add 1-1-1-0/adsl downlink vlan 100 tagged COS 7
This example adds interface 1-1-1-0/adsl with a vlanIDCOS value of 7 and enables the overwriting of the VLAN ID in all outgoing packets with the value of 7. bridge add 1-1-1-0/adsl downlink vlan 100 tagged COS 7 outCOS all 7
284
MALC Configuration Guide
Advanced bridging configurations
Mechanism for multiple interface ingress filters The SLMS CLI architecture has a mechanism for adding multiple filters for ingress interfaces by grouping packet-rule-records. In the bridge interface record you configure the ingress interface packet rule group index. Multiple bridges may use the same ingress interface packet rule group index. bridge-interface-record 1-6-1-0-adsl-0-37/bridge ... bridgeIfIngressPacketRuleGroupIndex -> {10} ...
packet-rule-record
10/1
packetRuleType: ---->{bridgedhcprelay} packetRuleValue: --->{20} ... packet-rule-record
10/2
packetRuleType: ---->{bridgeinsertoption82} packetRuleValue: --->{CircuitIDExample} ... packet-rule-record
10/3
packetRuleType: ---->{ratelimitdiscard} packetRuleValue: --->{??} ... packet-rule-record
10/4
packetRuleType: ---->{dstmacswapdynamic} packetRuleValue: --->{??} ... dhcp-server-subnet
20
... subnetgroup: ------->{20} ... external server: --->{11.1.1.1} ...
You can add multiple filters with the rule add command by supplying both the group index and the member index when you add a rule. The bridge-interface-record accesses rules by the group index number. rule add
The packetRuleValue options depend on the packetRuleType selected. The packetRuleTypes. For example when using bridgeinsertoption82, you have one or two packetRuleValues, one for circuit ID and one for remote ID. zSH> rule add bridgeinsertoption82 10/2 “circuitIDExample”
MALC Configuration Guide
285
Configuring bridges
zSH> rule add bridgeinsertoption82 10/2 “circuitIDExample” “remoteIDExample“
The bridge add command then has a parameter which refers to the group with the ipktrule parameter. See To add a packet-rule-record and packet rule group, page 286 for an example. zSH> bridge add 1-5-1-0/adsl vc 0/37 td 95000 downlink vlan 777 ipktrule 2
Packet rules are used for the following features and their options:
•
Destination MAC swapping, page 287
•
Bandwidth limiting by port and service, page 288
•
Configuring bridges to support DHCP relay, page 292
•
DHCP on bridge packet rules (DHCP relay, Option 82, PPPoE vendor tag, Forbid OUI), page 295
•
Access Control List, page 298
To add a packet-rule-record and packet rule group 1
Use the rule add command to add the rule giving a group index and member index, rule type and the parameters which that rule type requires. In this first example we will create a member for the IP packet group with the index of “2”. The dstmacswappingstatic rule shown requires a parameter which is a MAC address.
zSH> rule add dstmacswapstatic 2/1 08:00:20:bc:8b:8c Created packet-rule-record 2/1 (dstmacswapstatic)
2
Create the bridge and include the IP packet rule group
zSH> bridge add 1-5-1-0/adsl vc 0/37 td 95000 downlink vlan 777 ipktrule 2 Adding bridge on 1-5-1-0/adsl Creating bridge-interface-record 1-5-1-0-adsl-0-37/bridge
To delete a packet rule Use the rule delete command to delete the rule zSH> rule delete 1/1 packet-rule-record 1/1 Delete complete
To delete a group of packet rules, delete the records
To verify packet rule groups: Use the rule show command to display all the rules zSH> rule show Group/Member Type Value(s) ----------------------------------------------------------------------
286
MALC Configuration Guide
Advanced bridging configurations
10/1 10/2 10/4 3 record(s) found
bridgedhcprelay 20 bridgeinsertoption82 circuitIDexample dstmacswapdynamic 00:00:00:00:00:80
Destination MAC swapping The destination MAC swapping feature provides a security enhancement which prevents port-to-port communications between users sharing a VLAN for Internet access when the user-to-user traffic spans multiple MALC shelves.
Subscriber 1 Subscriber 2 Subscriber 3
Switch
Router
Subscriber 4 Subscriber 5 Subscriber 6
When enabled, this feature modifies the destination MAC address portion of unicast frames (Ethernet frames not using a multicast or broadcast destination MAC) that traverse the MALC so that the destination MAC is changed to the MAC address of the next-hop router in the access network. This address modification ensures that all frames in the access network are forwarded to the access router regardless of how the frame originated. Broadcast, multicast, and Ethernet frames with a destination MAC address of the next hop router are forwarded without MAC swapping. The MALC retrieves the MAC address of the next hop router to correctly swap into unicast frames through dynamically snooping DHCP ACK messages or a static user-specified entry.
•
Dynamically snooping DHCP ACK messages The MALC snoops DHCP ACK messages received on the bridge interface that is configured as the default (VLAN or global bridge). The source MAC address from this frame is swapped into for frames received on interfaces configured for destination MAC swapping. This address is stored in the database and persists across reboots. When a new DHCP ACK message is received in the same VLAN, its source is checked, and if different, the newer MAC address is used. This option requires that DHCP server services are used in the network and that the next hop router is the default router between the MALC and the DHCP server.
MALC Configuration Guide
287
Configuring bridges
•
Static user-specified entry The MALC inserts the user-specified valid 6-byte hexadecimal MAC address into unicast frames not matching the static entry.
Note that Destination MAC swapping is not supported on TLS, HUB, and symmetric bridges. It is not supported if the downlink traffic is PPPoE.
Configuring destination MAC swapping Use the rule add command to create either the dynamic or static destination MAC swapping rule: rule add
The rule for dynamic MAC swapping does not have a parameter. The rule for static MAC swapping requires a parameter, the MAC address to match rule add dstmacswapdynamic groupindex/Memberindex rule add dstmacswapstatic groupindex/Memberindex macaddress Options dstmacswapdynamic
Dynamic MAC swapping reads the source MAC address from the default (VLAN or global bridge) to swap into the packet, so you just need to define which bridge interface to associate with the rule. dstmacswapstatic
Static MAC swapping requires a MAC address to be swapped into the packet which you must supply. Example 1 For dynamic MAC swapping: zSH> rule add dstmacswapdynamic 1/1 Created packet-rule-record 1/1 (dstmacswapdynamic) Example 2 For static MAC swapping: zSH> rule add dstmacswapstatic 2/1 08:00:20:bc:8b:8c Created packet-rule-record 2/1 (dstmacswapstatic)
Bandwidth limiting by port and service Rate limiting is typically used when a service provider needs to provide customer services with limited bandwidth and needs to create a priority for which type of packets — date, voice, or video — have priority when there is bandwidth contention. In other words, a service provider may need to ensure that video traffic get to the user at the expense of data or voice traffic. 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 or delayed.
288
MALC Configuration Guide
Advanced bridging configurations
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 two modes of rate limiting are:
•
Color blind Rate limiting is performed on the interface without using the frame's Class of Service (COS) by assuming that all packets of a flow are “uncolored” and are treated equally. Color blind mode is most commonly used for a single service per VLAN.
•
Color aware Rate limiting observes that the incoming packet flow is colored and each packet is marked green, yellow, or red to signify if a packet has high, medium, or low priority.The color field maps to the priority COS value in tagged packets and the IP precedence TOS value in untagged packets. Color aware mode is most commonly used for multiple services on a single VLAN to ensure that the higher priority packets get through if there is bandwidth contention. Note: Color values are not supported on egress ports.
Color blind rate limiting Color blind rate limiting is usually set when one service is supplied per VLAN. The rate limit, Committed Information Rate (CIR), is set in bytes per second. For any rate above the set CIR, packets will drop. For example, in Figure 38, you would use the color blind method to set VLAN 100 to drop packets when the rate exceeds 5 Mbps, VLAN 200 to drop packets when the rate exceeds 3 Mbps, and VLAN 200 to drop packets when the rate exceeds 6 Mbps. Figure 38: One service per VLAN on an interface VLAN 100 voice 5 Mbps
VLAN 200 data 3 Mbps interface VLAN 200 video 6 Mbps
MALC Configuration Guide
289
Configuring bridges
Configure color blind policing The rule add ratelimitdiscard command sets the rate above which packets will be dropped. Note: The default values for CBS and EBS are good for most situations. Only advanced users should change these values. rule add ratelimitdiscard rate [cbs ] [ebs ]
For example, zSH> rule add ratelimitdiscard 4/1 rate 1300000 Created packet-rule-record 4/1 (ratelimitdiscard)
To view all created rules enter: zSH> rule show Group/Member Type Value(s) ---------------------------------------------------------------------1/2 bridgeinsertpppoevendortag 1/3 bridgeinsertoption82 4/1 ratelimitdiscard 1300000 400000 400000 3 record(s) found
To view just the ratelimitdiscard rules enter: (value1 is CIR, value2 is CBS, value3 is EBS) zSH> rule show ratelimitdiscard Group/Member Type Value(s) ---------------------------------------------------------------------4/1 ratelimitdiscard 1300000 400000 400000 1 record(s) found
Color aware rate limiting Note: Not commonly used except when performing advanced configurations.
Color aware bandwidth limiting is usually used when multiple services with different priorities are offered on a single VLAN. The colors green, yellow, and red are used for metering traffic and the colors correspond to COS values that range from 0-7. You can set which colors correspond to which COS value. Color Aware Policing is based on the idea that upstream devices are policing and marking frames based on a set of rules. A green packet is well behaved. A yellow packet has misbehaved at some point so if there is a bandwidth congestion it should be dropped before a green frame. A red packet has
290
MALC Configuration Guide
Advanced bridging configurations
violated a rule and should be dropped. This means that green packets are serviced first, then if there is enough room, the yellow packets are serviced. Red packets are always dropped. Table 17 shows the default mapping of COS value to color. Table 17: Default Color to COS/TOS values COS value
Color
7
green
6
green
5
green
4
green
3
yellow
2
yellow
1
yellow
0
yellow
Configure color aware policing The rule add colorawareratelimitdiscard command sets the color priority and the rate above which packets will be dropped. rule add colorawareratelimitdiscard rate [cbs ] [ebs ] [hi-priority ] [low-priority ]
For example, zSH> rule add colorawareratelimitdiscard 5/1 rate 1300000 Created packet-rule-record 5/1 (colorawareratelimitdiscard
Value1 is CIR, value2 is CBS, value3 is EBS, value4 is hi-priority, value5 is low-priority. To view just the colorawareratelimitdiscard rules just created enter: zSH> rule show colorawareratelimitdiscard Group/Member Type Value(s) ---------------------------------------------------------------------5/1 colorawareratelimitdiscard 1300000 400000 400000 4 0 1 record(s) found
Bridge with DHCP relay The MALC enables bridges to be configured as DHCP relay agents. All DHCP messages on the bridge will have Option 82 information inserted to be passed up through an IP interface to a external DHCP server.
MALC Configuration Guide
291
Configuring bridges
The MALC supports primary and alternate DHCP servers, see DHCP relay, page 207. Figure 39 illustrates the traffic flow when the MALC is configured with a bridge to support DHCP relay. Figure 39: Bridge supported DHCP relay
downstream bridge interface (normally toward subscribers)
upstream bridge interface (normally toward Internet core)
Host
DHCP unicast
External DHCP Serve
Configuring bridges to support DHCP relay This procedure describes how to configure bridges on the MALC to support DHCP relay. You add the DHCP relay as you create the bridge using the bridge add command by adding the dhcp-relay rule. Before you add DHCP relay you should have an IP interface on the MALC with a route available to the DHCP server. There is a mechanism for add Once the above elements are configured, to configure bridge support use the dhcp-relay add command. 1
To configure support for DHCP relay on a bridge use the dhcp-relay add command which uses the subnetgroup parameter as an identifier:
dhcp-relay add [] NULL
The subnetgroup parameter is the index identifier of the the dhcp-server subnet. The ip-address parameter is the address of the external DHCP server. For DHCP relay on bridges you add the NULL parameter
292
MALC Configuration Guide
2
Add the dhcp-relay rule using the rule add command which defines that the subnetgroup identifier is in the packet rule group.
3
Create bridge (or modify an existing bridge) to include the packet rule group.
Advanced bridging configurations
Example DHCP relay support on a bridge 1
Configure DHCP relay support on the bridge using the dhcp-relay add command
zSH> dhcp-relay add 20 11.1.1.1 NULL Operation completed successfully. This DHCP Relay Agent is available only for bridged connections; Routed interfaces will not be able to use it. Created DHCP Relay Agent number 20
2
Add the dhcp-relay rule to the IP packet rule group. zSH> rule add bridgedhcprelay 10/1 20 Created packet-rule-record 10/1 (bridgedhcprelay)
3
Create bridge and include IP packet rule group.
zSH> bridge add 1-6-1-0/adsl vc 0/37 td 95000 downlink vlan 777 ipktrule 10 Adding bridge on 1-6-1-0/adsl Created bridge-interface-record 1-6-1-0-adsl-0-37/bridge
You can verify the information in the profiles:
•
verify the dhcp-server-subnet subnet group zSH> get dhcp-server-subnet 20 dhcp-server-subnet 20 network: ---------------> {0.0.0.0} netmask: ---------------> {0.0.0.0} domain: ----------------> {0} range1-start: ----------> {0.0.0.0} range1-end: ------------> {0.0.0.0} range2-start: ----------> {0.0.0.0} range2-end: ------------> {0.0.0.0} range3-start: ----------> {0.0.0.0} range3-end: ------------> {0.0.0.0} range4-start: ----------> {0.0.0.0} range4-end: ------------> {0.0.0.0} default-lease-time: ----> {-1} min-lease-time: --------> {-1} max-lease-time: --------> {-1} boot-server: -----------> {0.0.0.0} bootfile: --------------> {} default-router: --------> {0.0.0.0} primary-name-server: ---> {0.0.0.0} secondary-name-server: -> {0.0.0.0} domain-name: -----------> {} subnetgroup: -----------> {20} stickyaddr: ------------> {enable} external-server: -------> {11.1.1.1} external-server-alt: ---> {0.0.0.0}
•
verify the rule exists (also a good way to find the group number)
MALC Configuration Guide
293
Configuring bridges
zSH> rule show Group/Member Type Value(s) ---------------------------------------------------10/1 bridgedhcprelay 20
•
verify the packet-rule record links to the DHCP server subnet group zSH> get packet-rule-record 10/1 packet-rule-record 10/1 packetRuleType: ---> {bridgedhcprelay} packetRuleValue: --> {20} packetRuleValue2: -> {} packetRuleValue3: -> {} packetRuleValue4: -> {} packetRuleValue5: -> {}
•
verify the bridge-interface-record contains the packet rule group
zSH> get bridge-interface-record 1-6-1-0-adsl-0-37/bridge bridge-interface-record 1-6-1-0-adsl-0-37/bridge vpi: ---------------------------------> {0} vci: ---------------------------------> {37} vlanId: ------------------------------> {777} stripAndInsert: ----------------------> {true} customARP: ---------------------------> {false} filterBroadcast: ---------------------> {false} learnIp: -----------------------------> {true} learnUnicast: ------------------------> {true} maxUnicast: --------------------------> {5} learnMulticast: ----------------------> {true} forwardToUnicast: --------------------> {false} forwardToMulticast: ------------------> {false} forwardToDefault: --------------------> {true} bridgeIfCustomDHCP: ------------------> {false} bridgeIfIngressPacketRuleGroupIndex: -> {10} vlanIdCOS: ---------------------------> {0} outgoingCOSOption: -------------------> {disable} outgoingCOSValue: --------------------> {0} s-tagTPID: ---------------------------> {0x8100} s-tagId: -----------------------------> {0} s-tagStripAndInsert: -----------------> {true} s-tagOutgoingCOSOption: --------------> {s-tagdisable} s-tagIdCOS: --------------------------> {0} s-tagOutgoingCOSValue: ---------------> {0} mcastControlList: --------------------> {} maxVideoStreams: ---------------------> {0} isPPPoA: -----------------------------> {false} floodUnknown: ------------------------> {false} floodMulticast: ----------------------> {false} bridgeIfEgressPacketRuleGroupIndex: --> {0} bridgeIfTableBasedFilter: ------------> {NONE(0)} bridgeIfDhcpLearn: -------------------> {NONE(0)}
294
MALC Configuration Guide
Advanced bridging configurations
DHCP on bridge packet rules (DHCP relay, Option 82, PPPoE vendor tag, Forbid OUI) The MALC supports multiple packet-rule records via a grouping mechanism so an open-ended number of filter settings can be configured for a bridge interface (see the example in Bridge with DHCP relay, page 291). The same filter settings can also be easily applied to multiple bridge interfaces. In uplink and downlink bridges packet-rule-records are typically assigned to bridge configuration groups on downlink bridge interfaces. Add the DHCP packet rule options using the rule add command to specify the packet rule option and which packet-rule-record group.
General case of adding DHCP packet rules 1
Use the rule add command with the appropriate packetRuleType and packetRuleValue(s) and packet rule group.
2
Create bridge (or modify an existing bridge) to include the packet rule group.
The bridge-interface-record contains a reference to the packet-rule-record . Multiple packet-rule-records may be put into a packet rule group by using a m/n identifier, where m is the identifier of the group and n is the identifier for the specific packet-rule-record. the packetRuleType and, where appropriate a packetRuleValue parameter or parameters which specify the variety of filter to be applied to the interface. Use the command: zSH> rule add ...
See the following DHCP packet rule records for appropriate packetRuleType and packetRuleValues for the rule add command:
•
bridgeddhcprelay: packetRuleValue contains the DHCP subnet group ID. If only the DHCP relay option is used, option82 information is displayed in hex format as slot port shelf vlan. See Configuring bridges to support DHCP relay, page 292. zSH> dhcp-relay add 20 11.1.1.1 NULL zSH> rule add bridgedhcprelay 10/1 20
•
bridgeinsertoption82: You can define textual values for two items of textual information: circuit ID and remote ID.
MALC Configuration Guide
295
Configuring bridges
If the first value is set it is taken as a literal text string to be used as the suboption 1 field in the DHCP packet. If it is not set a text string identifying the box and interface which received the packet is used. If the second value is set is it taken as a literal text string to be used as the suboption 2 field in the DHCP packet. If it is not set no suboption2 is provided. Use of this feature will usually require a distinct rule group for each interface since the circuit and remote Id values associated with suboptions 1 and 2 are distinct for each interface. DHCP option 82 provides the means for a DHCP relay agent to insert circuit specific information into DHCP messages which are forwarded on to the upstream DHCP server. There are two sub-options for DHCP option 82 insert — Circuit ID and Remote ID. Both of these fields are text fields, though they were designed to carry specific information. It is up to your implementation plans to define how to use the option 82 inserts. Circuit ID is meant to provide information about the circuit which the request came in on. It is normally the port and interface information. RFC 3046 describes possible uses of the Circuit ID field: –
Router interface number
–
Switching Hub port number
–
Remote Access Server port number
–
Frame Relay DLCI
–
ATM virtual circuit number
–
Cable Data virtual circuit number
Remote ID is meant to provide information about the remote host end of the circuit, however in practice the sub-option usually contains information about the relay agent. RFC 3046 describes possible uses of the Remote ID field: –
a "caller ID" telephone number for dial-up connection
–
a "user name" prompted for by a Remote Access Server
–
a remote caller ATM address
–
a "modem ID" of a cable data modem
–
the remote IP address of a point-to-point link
–
a remote X.25 address for X.25 connections
Since both fields support textual insertions on the MALC, please research RFC 3046 for further details regarding field format. To specify neither circuit ID or remote ID value: zSH> rule add bridgeinsertoption82 1/1 ""
To specify only the first circuit ID value:
296
MALC Configuration Guide
Advanced bridging configurations
zSH> rule add bridgeinsertoption82 1/1 CircuitIdText
To specify only the second remote ID value: zSH> rule add bridgeinsertoption82 1/1 "" RemoteIdText
To specify both values: zSH> rule add bridgeinsertoption82 1/1 “CircuitIdText” “RemoteIdText”
•
bridgeinsertpppoevendortag packetRuleValue contains optional identification string that is converted to TR101 compliant data. zSH>rule add bridgeinsertpppoevendortag 1/1
•
bridgeforbidoui packetRuleValue contains a 3-byte hexadecimal vendor code used with the Forbid OUI to forbid access on the interface. zSH>rule add bridgeforbidoui 1/1 AA:BB:CC
Packets from a device with a MAC address which begins with “AA:BB:CC” the hexadecimal vendor code (OUI — Organizational Unique Identifier) will be blocked.
MALC Configuration Guide
297
Configuring bridges
Access Control List The Access Control List (ACL) filters allow you to block packets or allow packets based on the source MAC address, Destination MAC address or Ethernet type. The ACL filters are configured using packet rule records. The ACL filtering options include
•
allow/deny based on Ethernet types
•
allow/deny based on destination MAC address
•
allow/deny based on source MAC address
ACL filtering is supported only
•
on systems with FE/GE or GE uplink/controller cards
•
on the Ingress port of line cards only and does not block any traffic on egress port (toward the subscriber)
•
on downlink and TLS bridge typese.
Ether Type filtering You can allow packets to pass or deny packets from passing by adding ethtype rules. You can use numeric codes to define which Ethernet packets to allow or deny. The 13th and 14th octets of an Ethernet (IEEE 802.3) packet after the preamble consists of the Ethernet Type or the IEEE 802.3 length field. Some of the more popular Ethernet types may also be designated by name (arp, ip) Preamble
Destination MAC addr
Source MAC addr
Ether Type
Payload
CRC32
Interframe gap
7 octets
6 octets
6 octets
2 octets
46-1500 octets
4 octets
12 octets
Numeric values must be hexadecimal. Prepend the "0x" prefix to the Ethernet Type code, so that for IP (Ethernet Type code 0800) you would use 0x0800. Using the numeric keyword for an ethType allows you to filter based on any Ethernet Type. Table 18: Common ethTypes
298
MALC Configuration Guide
Ethernet Type
Keyword
Numeric code
PPPoE Discovery
pppoediscovery
0x8863
PPPoE Data or session
pppoedata
0x8864
Address Resolution Protocol (ARP)
arp
0x0806
IP
ip
0x0800
Advanced bridging configurations
Note: PPPoE filtering only, not PPPoA filtering is supported.
Destination MAC address filtering You can allow or deny packets to pass based on the destination MAC address. There are a maximum of five Destination MAC address filters per interface and up to 1000 destination MAC address filters per system.
Source MAC address filtering You can allow or deny packets to pass based on the source MAC address of the packet. There are a maximum of 5 source MAC address filters per interface and up to 1000 source MAC address filters per system.
Allow or deny rules If no allow or deny rule is given, access is allowed and all packets would be passed. However if any allow or deny rule types are given all other access is denied, unless an allow all command is given. For example if you have the command which denies access based on the source MAC address: rule add deny 1/1 srcmac 00:01:02:03:04:05
The addition of this first rule would not only deny access to packets with that particular source MAC address, but all packets. To deny access just to packets with that particular source MAC address and allow access to all other packets you would need to add another rule to allow all packets, as shown in the following example. rule add deny 1/1 srcmac 00:01:02:03:04:05 rule add allow 1/2 all
In most (if not all) applications of the ACL rules, the allow all or deny all will be the last rule in the group. If an allow all or deny all rule is not present implicit deny all rule is executed. It is best programming practice to explicitly add the deny all rule. Please note that the allow all and deny all rules will not affect the regular transmission of broadcast and multicast frames on downlink bridge interfaces, so normal bridge functions will continue. Since TLS bridge interfaces normally allow all packets, the allow all and deny all rules will affect all the packets.
MALC Configuration Guide
299
Configuring bridges
Using multiple ACL filters on an interface/ordering ACL filters All of the filters work independently of the other filters and may be applied to the same interfaces. The filters are supposed to work together for maximum flexibility and control. Rule order is important. Rule order is defined by their membership index. Rules with the lowest memberIndex have the highest priority. Execution of the filtering terminates upon the first successful match. If your packet rules are the following rule add deny 1/10 srcmac 06:05:04:03:02:01 rule add allow 1/20 dstmac 00:01:02:03:04:05 rule add allow 1/30 all
and a packet is encountered which has a source MAC address of 06:05:04:03:02:01 and a destination MAC address of 00:01:02:03:04:05, the packet will be blocked (discarded) because the deny rule was matched. If the order were different, so that the allow rule had a groupIndex/memberIndex of 1/10 then the packet would be allowed. If allow all was 1/10, all of the packets would be allowed and none of the other rules would ever be executed, so the intelligent ordering of the ACL rules is important. It is good programming practice to leave available spots for the ordering of the ACL packet rules, so that you can add rules before or between existing rules without needing to change the numbers of existing rules.
To deny based on wild cards within the MAC address You can create a rule to filter out (or in) packets based on portions of the MAC address. The most common would be to create a filter which works like the bridgeforbidoui rule. See bridgeforbidoui, page 297 for an example. While ACLs may be used like the bridgeforbidoui rule, they provide a mechanism for handling the general case of filtering with wild cards and are much more powerful. To create a rule which works like the bridgeforbidoui rule works you may use a type of wild card to define which significant bits to filter for a MAC address. The bridgeforbidoui rule denies access based on the Organizationally Unique Identifier (OUI). An organization's OUI is the first bytes of the MAC address. For example the rule rule add deny 1/1 srcmac 00:01:02:00:00:00/24 would deny access for packets from a device whose source MAC address starts with 00:01:02. It is these first three bytes (24 bits) which supply the OUI for the device. Note: The bridgeforbidoui rule will not change and is being kept for legacy reasons, so if you have bridgeforbidoui rules, you need not change them.
300
MALC Configuration Guide
Advanced bridging configurations
If you needed to deny access based on the first four bytes you would use a command like rule add deny 1/1 srcmac 00:01:02:03:00:00/16
Even though the examples show 00s for the bits which we do not care what their value is, the “/24” is what defines the filter bits. The examples use “00” for the bits which we do not care about their value as a programming practice. If you want no mask you can use the “/48” on the MAC address, or leave the mask off.
To deny all multicast IP traffic Multicast traffic has its own OUI, 01:00:5e, so it is easy to deny multicast IP traffic. rule add deny 1/1 dstmac 01:00:5e:00:00:00/24
Note that downlink bridge interfaces drop upstream multicast traffic by default.
To limit traffic to PPPoE rule add allow 1/10 ethtype pppoediscovery rule add allow 1/20 ethtype pppoedata rule add deny 1/30 all
Note that the deny all is not necessary, but still a best programming practice.
Creating rules with AND operations When rules are combined in a single command, the rules are ANDed, so to limit traffic to PPPoE discovery broadcast and data packets for a specific MAC address you put them in a single command: rule add allow 1/20 dstmac 00:01:02:03:04:05 ethtype pppoediscovery rule add allow 1/30 dstmac 00:01:02:03:04:05 ethtype pppoedata rule add deny 1/100 all
Using Ethernet Type codes You may use the common name or numeric Ethernet type code. To limit traffic to PPPoE packets and two destination MAC addresses: rule rule rule rule rule
add add add add add
allow 1/20 allow 1/30 allow 1/40 allow 1/50 deny 1/100
dstmac 00:01:02:03:04:05 ethtype pppoediscovery dstmac 00:01:02:03:04:05 ethtype pppoedata ethtype 0x8863 dstmac 00:01:02:03:04:06 dstmac 00:01:02:03:04:06 ethtype 0x8864 all
Note that order of the commands in the single rule command is not important.
MALC Configuration Guide
301
Configuring bridges
ACL display, stats, clear commands ACL rule add commands The ruleType for ACL commands is allow or deny (other than bridgeforbidoui which is an implied deny without explicitly stating as the other ACL commands). rule add
The next parameter is one of the following keywords: dstmac, srcmac, ethtype, or all. rule add
Table 19: ACL ruleType keywords Keyword
Value(s)
Bits (default)
dstmac
hh:hh:hh:hh:hh:hh broadcast (ff:ff:ff:ff:ff:ff)
(48)
srcmac
hh:hh:hh:hh:hh:hh
(48)
ethtype
numeric
(16)
arp (0x0806) ip (0x0800) pppoediscovery (0x8863) pppoedata (0x8864) all
all packet conditions will be addressed by the final default condition (whether allow or deny).
Please note that once a single ACL allow or deny ruleType is used, there is an implicit unstated deny all rule. You can block all traffic if you do not add an allow all rule at the end of the group.
ACL rule show command Syntax: rule show acl [[/]]
Omission of groupIndex/memberIndex displays all ACL rules. Omission of just memberIndex displays all ACL rules matching the given groupIndex. Examples: rule show acl rule show acl 1 rule show acl 1/5
302
MALC Configuration Guide
Advanced bridging configurations
The rule show acl commands display only ACL related rules (ie. those with rule types allow, deny, or bridgeforbidoui). The rule show acl commands display a HitCount column which shows the number of times a rule was matched. Counts are held in a 64 bit format. Both HOST and NP (or equivalent) generated counts are aggregated together. If count exceeds 1T (10**12), display will show "n.nnnT", if count exceeds 1G (10**9), display will show "n.nnnG", else it will display a 10 digit number. Group/Member
Type
HitCount Value(s)
---------------------------------------------------------------------1/1 allow 0 dstmac bcast (ff:ff:ff:ff:ff:ff) ethtype pppoedisc (0x8863) 1/2 allow 1234567890 dstmac 00:01:02:03:04:05 ethtype pppoedisc (0x8863) 1/10 deny 517691 all 19/2 bridgeforbidoui 1.001G 00:81:80 19/5 bridgeforbidoui 2.123T 00:80:80
The older existing rule bridgeforbidoui is technically a deny specific rule, so it is displayed with the ACL rules. The bridgeforbidoui rule provides a means to block devices based on their OUI which are incompatible on the network or for other security reasons. The same filtering may be done with the allow/deny ACL rules, though you do not need to change existing rules. The bridgeforbidoui rule is kept for backward compatibility.
ACL rule stats The rule stats acl command displays or clears the ACL stats. Syntax: rule stats acl [[/]]
Omission of groupIndex/memberIndex displays all ACL rules. Omission of just memberIndex displays all ACL rules matching the given groupIndex. Example: rule stats acl rule stats acl 1 rule stats acl 1/15
Display is identical to that of "rule show acl".
MALC Configuration Guide
303
Configuring bridges
rule stats acl clear The rule stats acl clear command, clears the hit counts on all selected ACL rules. Syntax: rule stats acl clear [[/]]
Omission of groupIndex/memberIndex clears all ACL rules. Omission of just memberIndex clears all ACL rules matching the given groupIndex. Example: rule stats acl clear rule stats acl clear 1 rule stats acl clear 1/15
Broadcasts in asymmetric bridges In general, broadcasts sent from a downlink will traverse the uplink, but will not be sent down other downlinks, even within the same VLAN. This prevents subscribers from maliciously or unintentionally sending or receiving broadcasts between ports on the same system. Ports configured as uplinks will send broadcasts upstream, but by default will not propagate broadcasts sent from upstream down to the MALC. The filterBroadcast parameter set to “true” in the bridge-interface-record profile enables this filtering. This mechanism provides security benefits, as well as reducing unnecessary traffic on low bandwidth interfaces. Video bridging, a common use of multicast, uses the configuration of the forwardToMulticast on the uplink and learnMulticast on the downlink to transmit multicast traffic. Bridges can also enable VPN-like services using the floodUnknown and floodMulticast parameters. These parameters enable the MALC to forward unknown traffic to all bridge interfaces within the VLAN.
Video bridging Video bridging on the MALC provides the ability to integrate video streams for multiple sources into one conduit. Video bridging enables video packets to be forwarded over a Layer 2 bridge from a host to a subscriber. As a result, the video travels from its source, or head-end device, and passes through the MALC in a passive manner with only one video stream across the backplane, reducing bandwidth required for video packets to traverse a MALC. Video bridging requires you to configure both an uplink bridge and a downlink bridge. On the uplink bridge, the forwardToMulticast function is associated with a location that contains video content and allows the MALC to receive video groups from the network. An interface with this value set to
304
MALC Configuration Guide
Advanced bridging configurations
true should only transmit multicast traffic for which a JOIN request has been received. Any bridge interface with the forwardToMulticast parameter set to false discards multicast IP traffic. By default, the forwardToMulticast parameter is set to true on uplink bridges. On the downlink bridge, the learnMulticast function is associated with interfaces that have hosts connected to them and allows the MALC to send video groups from downlink interfaces to the network. By default, the learnMulticast parameter is set to true on downlink bridges. Note that JOIN operations enter on a learnMulticast interface associated with a downlink bridge and pass through on a forwardToMulticast interface associated with an uplink bridge. The following table details various video bridge behaviors associated with different combinations of settings for the bridge parameters. Table 20: learnMulticast-forwardToMulticast Combinations and Behavior learnMulticast
forwardToMultic ast
Behavior
False
False
The interface discards all incoming multicast packets and does not forward any of the packets.
True
False
The interface forwards both default multicast signaling packets an control multicast packets.
True
False
The interface discards incoming multicast content groups and forwards requested content groups.
False
True
The interface forwards control packets received on this interface to all other interfaces that have the learnMulticast field set to true.
False
True
The interface forwards content groups only to interfaces that have sent JOIN messages for a group.
True
True
Treat the same as an interface with the learnMulticast field set to false and the forwardToMulticast field set to true.
The following video bridge example creates a video bridge on a MALC-Uplink-2-GE uplink card using the first GigE interface as the uplink bridge. It also creates a bridge path on that interface. The downlink bridge uses ADSL interface in shelf 1, slot 3, port 1 and assigns VCI/VPI 0/37 with traffic descriptor 1 and VLAN 800 to the downlink interface. For the uplink bridge:
MALC Configuration Guide
305
Configuring bridges
zSH> bridge add 1-1-2-0/ethernetcsmacd uplink Adding bridge on 1-1-2-0/ethernetcsmacd Created bridge-interface-record 1-1-2-0-ethernet2/bridge
For the uplink bridge path, add a bridge path and a multicast aging period and IGMP query interval. zSH> bridge-path add ethernet2/bridge global mcastage 90 igmpqueryinterval 30
For the downlink bridge, add a downlink bridge and specify a maximum number of video streams and multicast control list. Members of the multicast control list must be defined to receive the video signal. zSH> bridge add 1-3-1-0/adsl vc 0/37 td 1 downlink vlan 800 video maxvideostreams 2 mcastctrl 1 Adding bridge on 1-3-1-0/adsl Created bridge-interface-record 1-3-1-0-adsl-0-37
Verifying bridge settings To verify bridge settings, use the get bridge-interface-record command for each bridge. This command displays the bridge settings, including the learnMulticast and forwardToMulticast. For the uplink bridge, note that the forwardToMulticast setting is true and the learnMulticast setting is false. zSH> get bridge-interface-record ethernet2/bridge vpi: ----------------------> {0} vci: ----------------------> {0} vlanId: -------------------> {0} stripAndInsert: -----------> {false} customARP: ----------------> {true} filterBroadcast: ----------> {true} learnIp: ------------------> {false} learnUnicast: -------------> {false} maxUnicast: ---------------> {0} learnMulticast: -----------> {false} forwardToUnicast: ---------> {true} forwardToMulticast: -------> {true} forwardToDefault: ---------> {false} bridgeIfCustomDHCP: -------> {true} bridgeIfConfigGroupIndex: -> {0} vlanIdCOS: ----------------> {0} outgoingCOSOption: --------> {disable} outgoingCOSValue: ---------> {0} s-tagTPID: ----------------> {0x8100} s-tagId: ------------------> {0} s-tagStripAndInsert: ------> {false} s-tagOutgoingCOSOption: ---> {s-tagdisable} s-tagIdCOS: ---------------> {0} s-tagOutgoingCOSValue: ----> {0}
306
MALC Configuration Guide
Advanced bridging configurations
For the downlink bridge, note that the forwardToMulticast setting is false and the learnMulticast setting is true. zSH> get bridge-interface-record 1-3-1-0-adsl-0-37/bridge vpi: ----------------------> {0} vci: ----------------------> {37} vlanId: -------------------> {800} stripAndInsert: -----------> {true} customARP: ----------------> {false} filterBroadcast: ----------> {false} learnIp: ------------------> {true} learnUnicast: -------------> {true} maxUnicast: ---------------> {5} learnMulticast: -----------> {true} forwardToUnicast: ---------> {false} forwardToMulticast: -------> {false} forwardToDefault: ---------> {true} bridgeIfCustomDHCP: -------> {false} bridgeIfConfigGroupIndex: -> {0} vlanIdCOS: ----------------> {0} outgoingCOSOption: --------> {disable} outgoingCOSValue: ---------> {0} s-tagTPID: ----------------> {0x8100} s-tagId: ------------------> {0} s-tagStripAndInsert: ------> {false} s-tagIdCOS: ---------------> {0} s-tagOutgoingCOSValue: ----> {0} maxvideostreams: ----------> {0} mcasctrl: -----------------> {0}
In addition, you can run a bridge igmp command to determine whether IGMP is running on the system. zSH> bridge igmp VlanID MAC Address MCAST IP Ifndx Host MAC Last Join ---------------------------------------------------------------------------999 01:00:5e:02:7f:fe 224.2.127.254 921 00:02:02:0b:4a:a0 2 999 01:00:5e:02:7f:fe 224.2.127.254 922 00:02:02:0a:bb:6d 106 999 01:00:5e:02:7f:fe 224.2.127.254 923 00:02:02:0a:c0:b7 87 999 01:00:5e:02:7f:fe 224.2.127.254 924 00:02:02:0b:4e:c5 172 999 01:00:5e:02:7f:fe 224.2.127.254 925 00:02:02:0b:4c:7e 65 999 01:00:5e:02:7f:fe 224.2.127.254 926 00:02:02:0b:4f:08 46 999 01:00:5e:02:7f:fe 224.2.127.254 927 00:02:02:09:c1:7d 90 999 01:00:5e:02:7f:fe 224.2.127.254 928 00:02:02:0b:44:cd 71 999 01:00:5e:02:7f:fe 224.2.127.254 929 00:02:02:0b:4c:ca 61 999 01:00:5e:02:7f:fe 224.2.127.254 930 00:02:02:0b:47:bd 7 999 01:00:5e:02:7f:fe 224.2.127.254 931 00:02:02:0b:47:c7 177 999 01:00:5e:02:7f:fe 224.2.127.254 932 00:02:02:0b:4d:35 181 999 01:00:5e:02:7f:fe 224.2.127.254 933 00:02:02:0b:4d:5b 144 999 01:00:5e:02:7f:fe 224.2.127.254 934 00:02:02:0b:4a:a5 59 999 01:00:5e:02:7f:fe 224.2.127.254 935 00:02:02:0b:4c:9e 3 999 01:00:5e:02:7f:fe 224.2.127.254 936 00:02:02:09:c1:78 6 999 01:00:5e:02:7f:fe 224.2.127.254 937 00:02:02:0a:c0:ca 131
MALC Configuration Guide
307
Configuring bridges
FloodUnknown for unknown unicast addresses When a packet comes into the MALC which is not in the learned MAC addresses DB, there are two options, to discard the packet or to attempt to discover the address where the packet should go. With unicast you want the packet to only go to the unique entity it was addressed to reach. In a normal line concentrator model the downlinks learned the MAC address when the source of the packet is from one of their interfaces. These learned addresses are not maintained indefinetly. The database is cleared of old addresses. When a packet comes in that is not in the learned addresses it is possible to discover where the packet should go by sending the packet to all devices in the hope that a device will send back a message. This process means that a packet will be sent to a number of entities. This ability to send to addresses other than the one intended (albeit in hopes of finding the proper entity) is against the exclusivity of one recipient of unicast and so is less secure. However with FloodUnknown true packets may be dropped. The FloodUknown parameter provides the ability to toggle the flooding of unknown unicast destination frames. When the FloodUnknown parameter is set to false, the MALC discards frames with an unknown unicast MAC. When Floodunknown is set to true, the MALC forwards frames with an unknown unicast MAC. For transparent bridges, the default setting for this parameter is true. For uplink bridges, the default setting for this parameter is false.
FloodMulticast to all other ports in a VLAN The FloodMulticast parameter allows the MALC to flood all multicast traffic received on a bridge out to all other ports in the VLAN. This is useful for architectures where the MALC is acting as an aggregation point with no user interfaces. By default, this parameter is set to false for all bridge types. When set to true, this parameter causes all multicast frames to be forwarded out all of the bridge interfaces within the VLAN, except the interface where the multicast was received. zSH> update bridge-interface-record 1-8-1-0-ethernetcsmacd/bridge Please provide the following: [q]uit. vpi: ----------------------> {0}: vci: ----------------------> {0}: vlanId: -------------------> {500}: stripAndInsert: -----------> {false}: customARP: ----------------> {false}: filterBroadcast: ----------> {false}: learnIp: ------------------> {true}: learnUnicast: -------------> {true}: maxUnicast: ---------------> {10000}: learnMulticast: -----------> {true}:
308
MALC Configuration Guide
Advanced bridging configurations
forwardToUnicast: ---------> {false}: forwardToMulticast: -------> {false}: forwardToDefault: ---------> {true}: bridgeIfCustomDHCP: -------> {false}: bridgeIfConfigGroupIndex: -> {0}: vlanIdCOS: ----------------> {0}: outgoingCOSOption: --------> {disable}: outgoingCOSValue: ---------> {0}: s-tagTPID: ----------------> {0x8100}: s-tagId: ------------------> {0}: s-tagStripAndInsert: ------> {false}: s-tagOutgoingCOSOption: ---> {s-tagdisable}: s-tagIdCOS: ---------------> {0}: s-tagOutgoingCOSValue: ----> {0}: mcastControlList: ---------> {}: maxVideoStreams: ----------> {0}: isPPPoA: ------------------> {false}: floodUnknown: -------------> {false}: floodMulticast: -----------> {false}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created.
Dynamic IP filtering on a bridge (Secure DHCP) The MALC enables secure DHCP settings on downlink bridges to prevent users with a statically configured IP address from bypassing DHCP security enforcement. This filter blocks users from accessing the network using anything other than valid DHCP offered IP address. When packets are received or sent out a secure downlink bridge interface, the MALC checks the IP address against the dynamic IP bridge filter. If a match is found (the address was provided by the DHCP server), the packet is allowed to pass through the filter. Otherwise, it is blocked. The unicast aging setting for allowed packets is determined based on the DHCP lease time.
Configuring a dynamic IP filter on a bridge A dynamic IP filter can be configured, modified, and deleted using the bridge add, modify, and delete commands. 1
Create a downlink bridge using the bridge add command with the secure option to create the dynamic IP filter. The secure option creates two static bridge paths (MAC and IP) for each host on the bridge that successfully negotiates its IP address from the DHCP server.
zsh> bridge add 1-6-1-0/adsl vc 0/35 td 500 downlink vlan 500 secure zSH> bridge show 1-6-1-0-adsl-0-35/bridge Typ VLAN Bridge St Table Data ---------------------------------------------------------------------------------
MALC Configuration Guide
309
Configuring bridges
dwn
500
1-6-1-0-adsl-0-35/bridge
2
UP
D 00:01:38:31:f4:35 S 00:01:38:31:f4:35 (Secure, TimeLeft: 3293 secs) S 10.1.11.245 (Secure, TimeLeft: 3294 secs)
Display the bridge-interface-record for the configured downlink bridge to view the detailed bridge settings.
zSH> get bridge-interface-record 1-6-1-0-adsl-0-35/bridge vpi: ---------------------------------> {0} vci: ---------------------------------> {35} vlanId: ------------------------------> {500} stripAndInsert: ----------------------> {true} customARP: ---------------------------> {false} filterBroadcast: ---------------------> {false} learnIp: -----------------------------> {true} learnUnicast: ------------------------> {true} maxUnicast: --------------------------> {5} learnMulticast: ----------------------> {true} forwardToUnicast: --------------------> {false} forwardToMulticast: ------------------> {false} forwardToDefault: --------------------> {true} bridgeIfCustomDHCP: ------------------> {false} bridgeIfIngressPacketRuleGroupIndex: -> {0} vlanIdCOS: ---------------------------> {0} outgoingCOSOption: -------------------> {disable} outgoingCOSValue: --------------------> {0} s-tagTPID: ---------------------------> {0x8100} s-tagId: -----------------------------> {0} s-tagStripAndInsert: -----------------> {true} s-tagOutgoingCOSOption: --------------> {s-tagdisable} s-tagIdCOS: --------------------------> {0} s-tagOutgoingCOSValue: ---------------> {0} mcastControlList: --------------------> {} maxVideoStreams: ---------------------> {0} isPPPoA: -----------------------------> {false} floodUnknown: ------------------------> {false} floodMulticast: ----------------------> {false} bridgeIfEgressPacketRuleGroupIndex: --> {0} bridgeIfTableBasedFilter: ------------> {mac+ip} bridgeIfDhcpLearn: -------------------> {mac+ip}
3
Use the bridge modify command to add a dynamic IP filter to an existing bridge or remove a dynamic IP filter from a secure bridge.
zSH> bridge modify 1-5-1-0/adsl vc 0/36 secure zSH> bridge modify 1-5-1-0/adsl vc 0/36 non-secure
4
To delete a bridge configured with a dynamic IP filter, use the bridge flush command to remove the bridge paths. Then, delete the bridge.
zSH> bridge flush 1-5-1-0/adsl vc 0/36 secure
310
MALC Configuration Guide
Advanced bridging configurations
zSH> bridge delete 1-5-1-0/adsl vc 0/36
MALC Configuration Guide
311
Configuring bridges
Broadcast suppression Broadcast suppression enables DHCP information to be relayed between DHCP client and host while broadcast filtering is enabled.
CustomDHCP setting The customDHCP setting enables bridge interfaces to pass DHCP information independent of the filterBroadcast setting. Setting customDHCP to TRUE will cause that bridge interface to pass DHCP OFFER and ACK packets even though the filterBroadcast is set to TRUE. To enable CustomDHCP: For an existing bridge, update the bridge-interface-record. zSH> update bridge-interface-record 1-3-1-0-adsl-0-35/bridge Please provide the following: [q]uit. vpi: ----------------------> {0}: vci: ----------------------> {39}: vlanId: -------------------> {46}: stripAndInsert: -----------> {true}: customARP: ----------------> {false}: filterBroadcast: ----------> {false}: learnIp: ------------------> {true}: learnUnicast: -------------> {true}: maxUnicast: ---------------> {5}: learnMulticast: -----------> {true}: forwardToUnicast: ---------> {false}: forwardToMulticast: -------> {false}: forwardToDefault: ---------> {true}: bridgeIfCustomDHCP: -------> {false}: true bridgeIfConfigGroupIndex: -> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
RSTP support Rapid Spanning Tree Protocol (RSTP, IEEE 802.1W) is supported on GIGE port on the following MALC FE/GE, GE uplink cards:
•
MALC-UPLINK-2-FE/GE
•
MALC-UPLINK-2-FE/GE-TDM
•
MALC-UPLINK-2-GE
•
MALC-UPLINK-2-GE-ONLY.
Use the stp-bridge add command to add a GIGE uplink port under the control of RSTP.
312
MALC Configuration Guide
Advanced bridging configurations
Configuring RSTP To configure RSTP, perform the following tasks: 1
Create STP bridges on ports 1-1-2-0 and 1-1-3-0.
zSH> stp-bridge add 1-1-2-0/eth uplink vlan 500 tagged Adding bridge on 1-1-2-0/ethernetcsmacd Created bridge-interface-record ethernet2-500/bridge zSH> stp-bridge add 1-1-3-0/eth uplink vlan 500 tagged Adding bridge on 1-1-3-0/ethernetcsmacd Created bridge-interface-record ethernet3-500/bridge
2
Add bridge path to each bridge.
zSH> bridge-path add ethernet2-500/bridge global Bridge-path added successfully zSH> bridge-path add ethernet3-500/bridge global Bridge-path added successfully
3
Show the bridges. When a bridge is up and under control of RSTP, its St (State) field shows one of the following RSTP state: –
DIS : RSTP discarding
–
LRN : RSTP learning (a transitional state)
–
FWD: RSTP forwarding (a normal operational state)
zSH> bridge show Typ VLAN Bridge St Table Data --------------------------------------------------------------------------upl Tg 500/10 ethernet2-500/bridge DIS S VLAN 500 default [U:3600 sec, M: 150 sec, I: 0 sec] get stp-bind ethernet2/linegroup/0 stp-bind ethernet2/linegroup/0 portPriority: -> {144} zSH> get stp-bind ethernet3/linegroup/0 stp-bind ethernet3/linegroup/0 portPriority: -> {128}
6
Now use the bridgeshow ports command to verify that 'ethernet3' is the active port.
zSH> bridgeshow ports ifIndex 2244 Phys ifIndex 3 LG ifIndex 4 externalVpi 0 - externalVci 0 shelf 1 - slot 1 - port 2 - subport 0 isUp Up - ifUnit 0 - ifType 6 - lineRRReg Line Up - speed 1000000000 portGroupIndex 0 - index 49 - *pBridgeCookie 0x3F3FBC4 flags 9 Attached StpEnabled ethernet2-500: is a ALTERNATE PORT in DISCARDING state Root bridge has priority 32768, address 00:02:16:3d:11:40 Designated bridge has priority 32768, address 00:0c:db:e8:7e:00 Designated Port id is 32917:128, root path cost is 4 Timers: forward delay is 15, hello time is 2, message age is 1 sync: 0 synced: 1 reRoot: 0 rrWhile: 0 operEdge: 0 fdWhile: 14 learn: 0 forward: 0 agreed: 0 learning: 0 forwarding: 0 updtInfo: 0 selected: 1 1 bridge(s) present first-> ethernet3-500: is a ROOT PORT in FORWARDING state Root bridge has priority 32768, address 00:02:16:3d:11:40 Designated bridge has priority 32768, address 00:0c:db:e8:7e:00 Designated Port id is 32915:160, root path cost is 4 Timers: forward delay is 15, hello time is 2, message age is 1 sync: 0 synced: 0 reRoot: 0 rrWhile: 15 operEdge: 0 fdWhile: 0
314
MALC Configuration Guide
Advanced bridging configurations
learn: 1 forward: 1 agreed: 0 learning: 1 forwarding: 1 updtInfo: 0 selected: 1
8 zSH>get stp-params name: -----------> revision: -------> bridgePriority: -> forceVersion: ---> fwdDelay: -------> helloTime: ------> migrateTime: ----> txHoldCount: ----> maxAge: --------->
To show the global RSTP parameters, view the stp-parameter profiles. 0 {} {0} {36000} {2} {15} {2} {3} {3} {20}
9
To modify the global RSTP parameters, update the stp-parameter profiles.
zSH>update stp-params 0 name: -----------> {} revision: -------> {0} bridgePriority: -> {36000} forceVersion: ---> {2} fwdDelay: -------> {15} helloTime: ------> {2}5 migrateTime: ----> {3} txHoldCount: ----> {3} maxAge: ---------> {20}
10 To delete an RSTP bridge, delete the bridge path first, then delete the stp-bridge on the port: zSH> bridge-path delete ethernet2-500/bridge Delete complete zSH> stp-bridge delete 1-1-2-0/eth uplink vlan 500 Delete complete
Commands for RSTP support stp-bridge add | delete Add and delete a RSTP bridge. Syntax stp-bridge add | delete Options add | delete
Specifies the action applied to the specified RSTP bridge.
get stp-bind Show the RSTP bind profile on the port. The port priority is displayed in the RSTP bind profile.
MALC Configuration Guide
315
Configuring bridges
Syntax get stp-bridge
update stp-bind Modify the port priority value in the RSTP bind profile on the port. Syntax update stp-bridge
get stp-params Show the global RSTP parameters. Syntax get stp-params
update stp-params Modify the global RSTP parameters. Syntax update stp-params
stp-bridge show Show the detailed information about the status of RSTP enabled links. Syntax stp-bridge show
316
MALC Configuration Guide
Ethernet RPR
Ethernet RPR Ethernet Resilient Packet Ring (RPR) provides redundant Ethernet links between MALC RPR nodes and an IP or outside network. Following the IEEE 802.17 standard, Ethernet packets are inserted, stripped, and forwarded between the RPR Uplink and ring nodes to create a resilient architecture with high bandwidth utilization and less than 50ms protection switching.
Overview An RPR configuration consists of an MALC RPR Uplink node that serves as a gateway between the RPR ring and the Internet or outside network, and a number of RPR ring nodes that process traffic between themselves and the Uplink node. A dual counter-rotating ring is used so traffic can be transmitted and received in both ring directions. The RPR Uplink node must have two 2-port GigE Uplink cards connected with a redundant RPR cable. Each ring node requires one 2-port GigE card with an optional GigE card added for redundancy. Note: See the MALC Hardware Installation Guide for more details about adding redundant GigE-2 cards to the MALC. The 2-port GigE card utilizes Small Form-factor Pluggable (SFPs) for flexible deployment over fiber or copper media for data-only or integrated voice, video, and data connections. SFP modules with the following Gigabit Interface Convertors (GBICs) are available for a variety of transmission choices:
•
SX for 850nm with multimode fiber (MMF)
•
LX for 1310nm with singlemode fiber (SMF)
•
ZX for 1550nm with singlemode fiber (SMF)
•
1000B-T for copper cable
See the MALC Hardware Installation Guide for more details about the supported SFPs. RPR can be deployed in a variety of topologies including ring, collapsed ring, star, linear and redundant card configurations. This section uses a basic 3-node ring topology as an example topology to demonstrate node functionality and port connections.
RPR ring topology In RPR ring topologies, two physical ports on the GigE cards are used as a single logical RPR ring port. For redundant GigE cards, including as the two GigE cards used in the RPR uplink node, the physical ports labeled port 1 on the redundant cards form the single logical RPR port. For non-redundant
MALC Configuration Guide
317
Configuring bridges
GigE cards, the ports labeled port 1 and port 2 on the single GigE card form the single logical RPR port. In other words, if two uplink cards are used in RPR mode, one link will act as a logical interface. However, each of the cards and their ports are still accessible uniquely. Using the shelf-slot-port-interface/interface type notation may help clarify how the ports are identified when RPR is used as opposed to the non redundant use of the card. Please see Table 21. Table 21: Gigabit Ethernet uplink card ports with and without RPR Physical Port
Description
Card 1 with RPR
Card 2 with RPR
Card 1 no RPR
Card 2 no RPR
10/100
Out of band management port
1-1-1-0/eth
1-1-1-0/eth
1-1-1-0/eth
1-2-1-0/eth
Port 1
Top GigE port if not RPR. If RPR, RPR port
1-1-1-0/rpr
1-2-1-0/rpr
1-1-2-0/eth
1-2-2-0/eth
Port 2
Bottom GigE port if not RPR. If RPR, Uplink port
1-1-3-0/eth
1-2-3-0/eth
1-1-3-0/eth
1-2-3-0/eth
Note: The recommended maximum number of nodes in an RPR ring is 16. In RPR configurations, the following logical interfaces are used:
•
interface 1-1-1-0 /eth (1-2-1-0/eth for the card in slot 2) uses the first physical port labeled 10/100 for the 10/100 Ethernet physical interface.
•
interface 1-1-1-0/rpr (1-2-1-0/rpr for the card in slot 2) uses the two physical ports assigned to the logical RPR port. In redundant GigE card configurations, the physical ports labeled port 1 on the redundant cards form the single logical RPR port and is logically identified as port 1 for the RPR (the out of band management port is still port 1 for eth). In non-redundant GigE card configurations, the physical ports labeled port 1 and port 2 on the same card are ports 2 and 3.
•
318
MALC Configuration Guide
interface 1-1-3-0 is assigned to physical port 2 in redundant GigE card configurations for upstream or subtended GigE connections.
Ethernet RPR
Figure 40: RPR logical ports
RPR port
RPR port
1-1-1-0/rpr
1-2-1-0/rpr
RDNT
RDNT
Card1-Port 1
Card2-Port 1
Card1-Port 2
Card2-Port 2
RPR port
RPR port
1-1-1-0/rpr
1-1-1-0/rpr
Port 1 Port 2
RPR ring node
Port 1 Port 2
RPR ring node
Physical ports are connected around the ring in the east direction so that port 1 on the active RPR Uplink node connects to the port 2 on the adjacent ring node. On the redundant RPR Uplink node card, port 1 connects in the west direction to the port 1 on the adjacent ring node. Traffic to the IP or outside network goes through the interface 1-1-3-0 assigned to physical port 2 on the RPR Uplink node’s active and standby cards. A redundant cable connects the physical RDNT ports between the RPR Uplink node’s active and redundant GigE cards. Neighbor RPR ring nodes with single GigE cards connect in the east direction through physical port 1 to facial port 2. Figure 41 illustrates a 3 node RPR configuration and physical port connections.
MALC Configuration Guide
319
Configuring bridges
Note: Because the MALC RPR ring uses dual counter-rotating rings, each connecting line in this figure represents two actual fibers. Each fiber transports send and receive traffic in a different direction around the ring. Figure 41: RPR configuration
RPR ring topology with redundant GigE cards Redundant GigE cards can also be used at each ring node to add an additional level of equipment protection. As with the RPR uplink node, redundant cables connect RDNT ports between the RPR ring nodes. Also in the RPR ring nodes, the physical ports labeled port 1 on the active and standy cards form the single logical RPR port interface 1-1-1-0/rpr (1-2-1-0/rpr on card 2). Physical port 2 on the active and standby cards in the ring nodes can be unconnected or connected to subtended nodes.
320
MALC Configuration Guide
Ethernet RPR
For the physical connections in this configuration, connect the physical ports so that on the RPR Uplink node the active card port 1 connects in the west direction to the adjacent RPR ring node port 1. On the redundant card in the Uplink node, port 1 connects in the east direction to the adjacent RPR ring node port 1.The neighbor RPR ring nodes connect through the physical ports labeled port 1. Physical ports labeled port 2 are not connected or may be used for GigE connections to subtended devices. Traffic to the IP or upstream network goes through the primary RPR Uplink node on active and standby card’s physical port 2. Figure 42 illustrates a basic RPR configuration with redundant cards on the ring nodes. Note: Because the MALC RPR ring uses dual counter-rotating rings, each connecting line in this figure represents two actual fibers. Each fiber transports send and receive traffic in a different direction around the ring. Interface 1-1-1-0/ethernetcsmacd is assigned to the 10/100 Ethernet physical interface.
MALC Configuration Guide
321
Configuring bridges
Figure 42: RPR configuration with redundant ring nodes &
! "$
%
RPR ring topology with redundant GigE cards and subtended MALCs In this configuration, redundant cables also connect RDNT ports between the RPR ring nodes. Also in the RPR ring nodes, the physical ports labeled port 1 on the active and standy cards form the single logical RPR port interface 1-1-1-0/rpr (1-2-1-0/rpr on card 2). For the physical connections in this configuration, connect the physical ports so that on the RPR Uplink node the active card port 1 connects in the west direction to the adjacent RPR ring node port 1. On the redundant card in the Uplink node, port 1 connects in the east direction to the adjacent RPR ring node port 1.The neighbor RPR ring nodes connect through the physical ports labeled port 1.
322
MALC Configuration Guide
Ethernet RPR
Physical ports labeled 2 on the active and standby cards function as the subtended GigE connection and use interface 1-1-3-0/ethernetcsmacd. Traffic to the IP or upstream network goes through the RPR Uplink node on active and standby card’s physical port 2 using interface 1-1-3-0/ ethernetcsmacd (1-2-3-0/ethernetcsmacd on card 2). Figure 43 illustrates a basic RPR configuration with redundant cards on the ring nodes and subtended MALCs. Note: Because the MALC RPR ring uses dual counter-rotating rings, each connecting line in this figure represents two actual fibers. Each fiber transports send and receive traffic in a different direction around the ring. Interface 1-1-1-0/ethernetcsmacd is assigned to the 10/100 Ethernet physical interface.
MALC Configuration Guide
323
Configuring bridges
Figure 43: RPR configuration with redundant ring nodes and subtended MALC &
! "$
%
'
(
'
(
'
RPR configuration RPR basic configuration involves configuring the primary Uplink node with 2 GigE Uplink cards and then configuring each RPR ring node with a single GigE Uplink card. Redundant GigE Uplink cards can also be added to RPR ring nodes for additional card protection. This section contains the following procedures:
324
MALC Configuration Guide
•
Configuring RPR protection switching on page 325
•
Displaying RPR configuration on page 326
Ethernet RPR
•
Displaying RPR topology on page 327
•
Displaying RPR status on page 329
•
Displaying RPR statistics on page 330
Configuring RPR protection switching MALC RPR configurations support less than 50ms protection switching for fiber breaks or ring failures in the RPR ring. RPR nodes support a Wrap protection strategy. This protection strategy determines the timing and type of protection that is used when a span fault occurs. When Wrap is configured as false (the default setting) and a ring protection event occurs, the RPR node does not send traffic in the direction of the ring failure. Instead, traffic is steered or redirected to the destination in the opposite direction of the ring failure. When Wrap is configured as true, the RPR node sends traffic out to the destination even if it is in the direction of a ring failure. When the failure is encountered, traffic wraps or returns in the other direction back through the sending node to the destination. The Wrap false setting offers lower packet latency as packets do not have to travel to the ring failure and then traverse the ring in the opposite direction to get to the destination. However, with this setting more packet loss may occur as packets sent in the direction of a ring failure may be lost. The Wrap true setting helps prevent packet loss, but increases packet latency as packets sent in the direction of a ring failure are rerouted back to the destination in the opposite direction. Other protection switching options include:
•
reversion mode The reversion mode determines if traffic resumes processing in the normal direction after a protection event is cleared.
•
wait-to-restore (wtr) time The wtr time determines how long the node waits after a protection event is cleared before traffic processing reverts back to the normal direction.
•
fast timer This timer indicates how often in milliseconds the node sends out ‘fast’ status messages when a protection event occurs.
•
slow timer This timer indicates how often the node sends out ‘slow’ status messages when a protection event occurs. This value is in 50 millisecond (ms) intervals. For example, a value of 100 equals 5 seconds. To change the protection switching options, update the rpr-config profile. zSH> update rpr-config 1-1-1-0/rpr Please provide the following: [q]uit.
MALC Configuration Guide
325
Configuring bridges
reversion-mode: --------> {true}: protection-wtr: --------> {10}: 20 protection-fast-timer: -> {10}: protection-slow-timer: -> {100}: wrap-config: -----------> {false}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Displaying RPR configuration The MALC rpr show config command displays information about the current RPR node configuration. zSH> rpr show config sysObject= 0x66bc578, systemId= 0, pParent= 0x7de9ba0, ethDrvNum= 0 rprStarted= 1, bridgeExists= 1 npRprContext= 0x100 (BrgExst,Steer,) rprCtrlSema4= 0x492a740, taskIdSema4= 0x0, lastTaskIdSema4= 0x66b06e8 rprStationSema4= 0x4b43fd0, taskIdStationSema4= 0x0, lastTaskIdStationSema4= 0x66b06e8 NpGigePacketWrap= 4/5, unitPhy= 0/1, outMacPort= 1/0 Encoding= 0xf810/0xf811, rxRegistered= 1/1 txSlowTimeout= 100ms, txFastTimeout= 10ms, ticksPer100ms= 10 atdTimerTimeout= 1000ms, lastAtdSentTime= 2687770 topoChanged= 0, protectChanged= 0 containmentActive= 0, containmentStart= 1055191, containmentDuration= 60ms containmentCnt= 6, containmentTotal= 13310ms newNeighbor= 0/0, revertive= 1, tossWrongRingletIDs= 0 lrttActive= 1, lrttComplete= 1, lrttContextId= 7 lrttTime= 1055197, lrttDuration= 210ms, lrttIncompletionTimeout= 1000ms tvState= tvValid, tvTopoCheck= 3, stabilityTime= 1055192, instabilityTime= 1055191 stabilityTO= 40ms, instabilityTO= 10000ms topologyValid= 1, topologyStable= 1, topologyUnstableTime= 1055191, topologyUnstableDuration= 60ms adminReqProtection= ???/???, spanProtAdmin= IDL/IDL spanOperStatus= IDL/IDL, linkErrCode= UP needSecondaryMacValidation= 1, cleavePt= 1/1 notifyCleavePtChange= 0/0, notifyTopoChange= 0/0 WTR[0]: time= 10541840, timeout= 10000ms, enabled= 1 WTR[1]: time= 237920, timeout= 10000ms, enabled= 1 tcState= tcReturn, puState= puReturn, ptpState= ptpReturn Defect: miscabling= 0/0, Start= 0/0, Duration= 0ms/0ms protMisconfig= 0, Start= 0, Duration= 0ms topoEntryInvalid= 0, Start= 1054951, Duration= 60ms maxStations= 0, Start= 0, Duration= 0ms topoInconsist= 0, Start= 1042700, Duration= 340ms topoInstab= 0, Start= 0, Duration= 0ms nextLogId= 209, totalLogEntrys= 209 current time = 2687864 ticks (26878640ms)
326
MALC Configuration Guide
Ethernet RPR
Displaying RPR topology MALC RPR topology displays information about an RPR ring for ring diagnostics and management. From an RPR node’s perspective, other nodes to in the west direction or left of the current node are on ringlet 0. Nodes in the east direction or right of the current node are on ringlet 1. The number of hops between nodes is determined by counting the number of nodes in a specified ringlet or direction. The current node is always at hop 0. This illustration shows an example 3-node topology.
+
) *
Using ring node B as the current node, ringlet 0 (zero) is in the west direction or left. From node B, traffic on ringlet 0 travels to node A, to node C and back to node B. In ringlet 0, node A is one hop from node B, while node C is two hops away. Ringlet 1 is in east direction or right. From node B, traffic on ringlet 1 travels to node C, to node A and back to node B. In ringlet 1, node C is one hop from node B, while node A is two hops away.
MALC Configuration Guide
327
Configuring bridges
Use the rpr show topo command to display topology, statistics, configuration, and status information. zSH> rpr show topo total number of ring nodes= 3 (ringlet 0= 2, ringlet 1= 2) ring protection= STEERING, ring topology= CLOSED ring containment= NOT active, topology valid= true link status: west(PSW)= Signal OK (IDL), east(PSE)= Signal OK (IDL) R=reachable; WE=west/east edge state; PSW/PSE=west/east protect state ring hop R WE PSW PSE -------MAC------- ------IP------0 3 t ff IDL IDL 00:01:47:5a:aa:2a 192.168.50.142 0 2 t ff IDL IDL 00:01:47:5a:aa:22 192.168.50.146 0 1 t ff IDL IDL 00:01:47:5a:aa:1a 192.168.50.144 **** 0 t ff IDL IDL 00:01:47:5a:aa:2a 192.168.50.142 1 1 t ff IDL IDL 00:01:47:5a:aa:22 192.168.50.146 1 2 t ff IDL IDL 00:01:47:5a:aa:1a 192.168.50.144 1 3 t ff IDL IDL 00:01:47:5a:aa:2a 192.168.50.142
This example topology uses node B as the current node. There are a total of 3 nodes in the ring, the current node and 2 nodes in each ringlet. Ring protection is set to Steering (Wrap=false). There are no protection events so the ring is closed and containment is not active. Containment causes data packets that are not strictly ordered to be discarded when a topology change or protection event occurs. The current topology is valid. Causes of invalid topology include miscabling, malfunctioning links, and other connectivity issues. For each node in the ring, the topology displays the following data:
328
MALC Configuration Guide
Field
Description
ring
0 indicates ringlet 0 and the east direction around ring. 1 indicates ringlet 1 and the west direction around ring. **** indicates the current node.
hop
Number of hops upstream and downstream from the current node. The current node is always displayed with a hop count of 0. To validate the passing of traffic through the complete ring and back to the current node, the current node also appears at the last hop in both ringlets.
R
Reachable. t indicates the connection to the node is valid and reachable. f indicates the connection to the node is not valid and is unreachable.
WE
West and east span fault status. An edge indicates a span fault occurred. t indicates an edge exists and the edge status is true. f indicates an edge does not exist and the edge status is false.
Ethernet RPR
Field
Description
PSW/PSE
The protection state on the west (PSW) and east (PSE) span. Values: IDL: Protection status is idle, signal OK. Link is up with neighbor. WTR: Wait-to-restore. The span has recovered from a fault but it’s been configured to wait a period of time before restoring the card’s connection. The wait-to-restore time is configured in the protection-wtr parameter in the rpr-config profile. MS: User has requested the span to deactivate. Not supported. SD: Signal degraded. Not supported. SF: Signal failure. Link is down with neighbor. FS: User has forced span to deactivate. Not supported.
MAC
The MAC address of the node.
IP
IP address of the node. If the node has multiple IP interfaces on the RPR port, the interface associated with the lowest VLAN ID is displayed.
Displaying RPR status The MALC rpr show status command displays status information about the RPR ring for ring diagnostics and management. zSH> rpr show status sysObject= 0x66bc578, systemId= 0, pParent= 0x7de9ba0, ethDrvNum= 0 rprStarted= 1, bridgeExists= 1 npRprContext= 0x100 (BrgExst,Steer,) rprCtrlSema4= 0x492a740, taskIdSema4= 0x0, lastTaskIdSema4= 0x4984b60 rprStationSema4= 0x4b43fd0, taskIdStationSema4= 0x0, lastTaskIdStationSema4= 0x66b06e8 NpGigePacketWrap= 4/5, unitPhy= 0/1, outMacPort= 1/0 Encoding= 0xf810/0xf811, rxRegistered= 1/1 txSlowTimeout= 100ms, txFastTimeout= 10ms, ticksPer100ms= 10 atdTimerTimeout= 1000ms, lastAtdSentTime= 2752070 topoChanged= 0, protectChanged= 0 containmentActive= 0, containmentStart= 1055191, containmentDuration= 60ms containmentCnt= 6, containmentTotal= 13310ms newNeighbor= 0/0, revertive= 1, tossWrongRingletIDs= 0 lrttActive= 1, lrttComplete= 1, lrttContextId= 7 lrttTime= 1055197, lrttDuration= 210ms, lrttIncompletionTimeout= 1000ms tvState= tvValid, tvTopoCheck= 3, stabilityTime= 1055192, instabilityTime= 1055191 stabilityTO= 40ms, instabilityTO= 10000ms topologyValid= 1, topologyStable= 1, topologyUnstableTime= 1055191, topologyUnstableDuration= 60ms adminReqProtection= ???/???, spanProtAdmin= IDL/IDL spanOperStatus= IDL/IDL, linkErrCode= UP needSecondaryMacValidation= 1, cleavePt= 1/1 notifyCleavePtChange= 0/0, notifyTopoChange= 0/0 WTR[0]: time= 10541840, timeout= 10000ms, enabled= 1
MALC Configuration Guide
329
Configuring bridges
WTR[1]: time= 237920, timeout= 10000ms, enabled= 1 tcState= tcReturn, puState= puReturn, ptpState= ptpReturn Defect: miscabling= 0/0, Start= 0/0, Duration= 0ms/0ms protMisconfig= 0, Start= 0, Duration= 0ms topoEntryInvalid= 0, Start= 1054951, Duration= 60ms maxStations= 0, Start= 0, Duration= 0ms topoInconsist= 0, Start= 1042700, Duration= 340ms topoInstab= 0, Start= 0, Duration= 0ms nextLogId= 209, totalLogEntrys= 209 current time = 2752107 ticks (27521070ms)
Displaying RPR statistics The MALC rpr show stats command displays both RPR transmit and receive statistics about the RPR ring performance for ring diagnostics and management. The rpr show stats optional argument clear will clear the statistics. The noclr argument (the default) preserves the current statistics. rpr-node2-zSH> rpr show stats TX: Requests= 3604, Ok= 3604, BadSrcMac= 0, Switch2Bridge= 8 Data: ip= 3596, ucst= 2963, bcst= 633, bridge= 8, ec_so= 0 DstUnreachable= 0, Data_containment= 0 CtLrttReq: ok= 270, fail= 0 CtLrttRsp: ok= 200, fail= 0 CtTC: ok= 3312442, fast= 718, fail= 0, triggers= 290 CtTP: ok= 3312625, fast= 901, fail= 0, triggers= 192 CtATD: ok= 331153, fail= 0, nodata= 30 Idle: ok= 0, fail= 0 Fairness: ok= 0, fail= 0 RX: Data: total= 1306065, bf= 1574, ef= 1304491, containment= 0, ec_so= 1304491 Idle= 0, Fairness= 0 Ct= 17571585, Ct_badType= 0, Ct_badVersion= 0 CtTP: total= 11741085, ignore= 0, ignoreOthers= 0, suspect= 0 CtTP_redundant[ hop=1 ]: 1689268, 3311135 CtTP_redundant[ hop=2 ]: 1684453, 1686970 CtTP_redundant[ hop=3 ]: 1684482, 1684478 CtTC: total= 4997664, bad= 0 CtLrttReq: total= 214, ignore= 14 CtATD: total= 832407, ignore= 0, dup= 0, badType= 0, badLen= 0 ZhOrg= 0, badZhType= 0, badZhLen= 0 CtLrttRsp: total= 215, ignore= 0, exceed= 0, bad= 0 lrtt_starts= 108, lrtt_fails= 0, lrtt_stops= 107, lrtt_multiple= 0 contextChgs= 218, cleavePtChgs= 7/51, topoChgs= 79/57 linkChgs= 52/4, linkChgNotifies= 56 CDT: Add= 29, Add2= 54, Del= 26, Del2=104
330
MALC Configuration Guide
Ethernet RPR
Switches= 54, SwitchTreeHops1/2/3= 1/78/0 MacChgs= 0, Unexp1/2/3/4/5/6= 0/0/0/0/0/0
Adding bridges to RPR ring Bridges can be configured in a RPR ring so bridged subscriber traffic can be transported across the ring and connected to the destination IP or outside network. The illustration below shows the bridge configurations in a 3-node RPR ring:
•
Uplink node The RPR Uplink node contains a bridge uplink and global bridge-path on the redundant GigE active and standy card ports labelled port 2 (1-1-3-0/ ethernetcsmacd) to direct all bridged traffic to the outside or IP network. The RPR Uplink node also contains a global-intralink on the GigE active and standby card ‘s logical RPR ports (1-1-1-0/rpr) so unknown traffic is sent to the ring, even though address learning is not enabled.
•
Ring node 1 This RPR ring node contains a bridge uplink on the redundant GigE card’s logical RPR port (1-1-1-0/rpr) to direct all outgoing bridged traffic to the RPR Uplink node. This node also contains a bridge downlink on the ADSL card 1-1-5-0 so VLAN tags can be stripped and inserted for subscriber VLAN participation.
•
Ring node 2 This RPR ring node contains a bridge uplink on the redundant GigE card’s logical RPR port (1-1-1-0/rpr) to direct all outgoing bridged traffic to the RPR Uplink node. This node also contains a bridge intralink on port 2 (1-3-1-0/ethernetcsmacd) to a subtended MALC. A bridge intralink is used in place of a bridge downlink so unknown packets are forwarded to subscribers without the need to learn all downlink subscriber MAC addresses. Note: If a subtended device is configured to request DHCP services from a DHCP server through the IP or outside network, ensure that the CustomDHCP setting is set to true in the bridge-interface-records on the RPR Uplink and ring nodes.
MALC Configuration Guide
331
Configuring bridges
To configure bridges in an RPR ring: 1
On the Uplink node a
Add a bridge interface to the second GigE port (this is the port connected to the external network): zSH> bridge add 1-1-3-0/ethernetcsmacd uplink
b
Add a default bridge path for the ring over the second GigE port: zSH> bridge-path add ethernet3/bridge global
All bridge traffic will be forwarded over this interface. c
Add an bridge intralink on the logical RPR port: zSH> bridge add 1-1-1-0/rpr intralink
332
MALC Configuration Guide
Ethernet RPR
zSH> bridge-path add rpr1/bridge global-intralink
Unlearned traffic received on this interface is forwarded to the external network. d
Add a global bridge intralink path: zSH> bridge-path add rpr1/bridge global-intralink
This interface is the global intralink for the ring. 2
On the RPR ring node to which subscribers are connected: a
Add an uplink bridged interface on the logical RPR port: zSH> bridge add 1-1-1-0/rpr uplink
b
Add a default bridge path that points to the Uplink node: zSH> bridge-path add rpr1/bridge global
c
Add a downlink to the remote subscriber: zSH> bridge add 1-5-1-0/adsl vc 0/37 td 4000 downlink vlan 100
3
On the other RPR ring node to which a subtended MALC is connected: a
Add an uplink bridged interface on the logical RPR port: zSH> bridge add 1-1-1-0/rpr uplink
b
Add a default bridge path that points to the Uplink node: zSH> bridge-path add rpr1/bridge global
c
Add an intralink to the subtended MALC: zSH> bridge add 1-1-3-0/ethernetcsmacd intralink zSH> bridge-path add ethernet3/bridge global-intralink
4
On the RPR ring node to which subscribers are connected from the subtended MALC: a
Add an uplink bridged interface on the logical RPR port: zSH> bridge add 1-1-1-0/rpr uplink
b
Add a default bridge path that points to the Uplink node: zSH> bridge-path add rpr1/bridge global
c
Add a downlink to the remote subscriber: zSH> bridge add 1-7-1-0/adsl vc 0/37 td 4000 downlink vlan 200
MALC Configuration Guide
333
Configuring bridges
Linear GigaBit Ethernet The MALC GigE-2 Uplink card also supports a linear topology in which several MALC devices are daisy-chained together to pass traffic and provide subscriber access. The card type in the card profile is used to differentiate linear configuration from RPR ring configuration. In linear configurations, all ports are ethernetcsmacd ports as described below. Single card or redundant card configurations can be used. Figure 44 illustrates the GigE-2 card linear configuration using single GigE-2 Uplink cards. Additional MALC nodes can be added to the daisy-chained linear topology by repeating this pattern of connections. Note: Interface 1-1-1-0 is assigned to the 10/100 Ethernet physical interface. Interface 1-1-2-0 is assigned to physical port 1. Interface 1-1-3-0 is assigned to physical port 2. Figure 44: GigE linear configuration with single card
Redundant GigE-2 cards can also be used to provide card-level redundancy. Figure 45 illustrates the GigE-2 Uplink card linear configuration using redundant cards.
334
MALC Configuration Guide
Linear GigaBit Ethernet
Figure 45: GigE linear configuration with redundant cards
GigE-2 Uplink card redundant configuration in linear topology This section describes the optional configuration procedures for the GigE-2 Uplink redundant card configuration in a linear topology. These procedures should be done before provisioning the system. See the MALC Hardware Installation Guide for more details about adding redundant GigE-2 cards to the MALC.
Configuring GigE-2 card redundancy The GigE-2 card can be configured for redundancy so the GigE uplink card switches to a standby GigE card when the active Ethernet link goes down. Options for this card switchover include:
•
switching timeout The amount of time the active card waits when a failure occurs before switching to the standby card.
•
reversion mode
MALC Configuration Guide
335
Configuring bridges
The reversion mode determines if traffic reverts back to the initial active card after a protection event is cleared.
•
restore timeout After a switchover occurs, the amount of time the active card waits after the protection event is cleared before reverting back to the other card.
1
To configure card redundancy, use the line-red command on the active card. zSH> line-red set ethernet1/ip timeout 30 revertive timeout 600
This command sets card redundancy between the currently active GigE-2 card and the standby GigE-2 card. The switch timeout is set to 30 seconds with the revertive option set to occur after a 600 second timeout. The standby card must be in a running state for a switchover to occur. 2
Display the redundancy setting. zSH> line-red show ethernet1/ip redundacy status for ethernet1/ip: REBOOT timeout 30 REVERTIVE revert timeout 600
GigE-2 card bridging Within the linear topology, bridging can be configured to forward traffic based on MAC address and VLAN ID to an IP or outside network. The node connected to the network contains a bridge uplink and global bridge-path on the GigE-2 card’s first port (1-1-2-0) to direct all bridged traffic to the outside or IP network. This card also contains a global-intralink on the GigE-2 card’s second port (1-1-3-0) so unknown traffic is sent to the downstream, even though address learning is not enabled. The second node in the daisy-chained linear topology contains a bridge uplink on the GigE-2 card’s first port (1-1-2-0) to direct all outgoing bridged traffic to the upstream node. This node also contains a bridge intralink on the second port (1-1-3-0) so unknown traffic is sent to the downstream to another network or subtended Ethernet device, even though address learning is not enabled. Additional MALC nodes can be added to the daisy-chained linear topology by repeating this pattern of connections and bridging. Note: The GigE card on the MALC should be configured with a card-line-type of ds1 for T1, e1 for E1, or t1cas for T1 channel bank support. Figure 46 illustrates the GigE-2 card linear configuration using redundant cards.
336
MALC Configuration Guide
Linear GigaBit Ethernet
Figure 46: GigE linear configuration with single card and bridging
Configuring GigE-2 card bridging 1
On the node connected to the Ethernet or IP network a
Add a bridge interface to the first GigE-2 port (this is the port connected to the external network): zSH> bridge add 1-1-2-0/ethernetcsmacd uplink
b
Add a default bridge path over the first GigE-2 port: zSH> bridge-path add ethernet2/bridge global
All bridge traffic will be forwarded over this interface. c
Add an bridge intralink on the second GigE-2 port: zSH> bridge add 1-1-3-0/ethernetcsmacd intralink zSH> bridge-path add ethernet3/bridge global-intralink
Unlearned traffic received on this interface is forwarded to the external network. This interface is the global intralink for the node. d
Add a downlink to the remote subscriber: zSH> bridge add 1-5-1-0/adsl vc 0/37 td 4000 downlink vlan 100
2
On the next node in the linear daisy-chain configuration:
MALC Configuration Guide
337
Configuring bridges
a
Add an uplink bridged interface: zSH> bridge add 1-1-2-0/ethernetcsmacd uplink
b
Add a default bridge path that points to the Uplink node: zSH> bridge-path add ethernet2/bridge global
c
Add an bridge intralink on the second GigE-2 port: zSH> bridge add 1-1-3-0/ethernetcsmacd intralink zSH> bridge-path add ethernet3/bridge global-intralink
Unlearned traffic received on this interface is forwarded to the external network. This interface is the global intralink for the node. d
Add a downlink to the remote subscriber: zSH> bridge add 1-8-1-0/adsl vc 0/39 td 3000 downlink vlan 200
3
338
MALC Configuration Guide
Continue this configuration for all the nodes in the daisy-chain connection.
PPPoA - PPPoE Conversion
PPPoA - PPPoE Conversion The MALC supports PPPoA to PPPoE internetworking for connections to a Broadband Remote Access Server (BRAS) using a PPP tunnel. Upon detecting PPPoA traffic, the MALC initiates a PPPoE session with the Broadband Remote Access Server (BRAS). PPP traffic between the CPE and the BRAS is tunneled over this PPPoE session. The MALC autosenses the type of PPPoA encapsulation as either VCMUX or LLC. An inactivity timeout occurs when a lack of activity is detected on the PPPoA connection for 30-80 seconds, while upstream PPPoE packets are received. When this occurs, the PPPoE session is terminated. Figure 47: PPPoA to PPPoE Internetworking
IP PC
MALC
BRAS PPPoE
PPPoA
Radius server
Enabling PPPoA to PPPoE Internetworking 1
Add a downlink bridge using the bridge configuration record with the PPPoA parameter. The bridge command supports enabling PPPoA internet working from the command line. This example adds interface 1-5-24-0/adsl with VLAN 500, and PPPoA to PPPoE internet working enabled.
zSH> bridge add 1-5-24-0/adsl vc 0/35 td 20000 downlink vlan 500 pppoa
This automatically updates the bridge-interface record Note: The following message may appear if the CPE device is not properly configured for PPPoA connections. FEB 01 15:59:22: error : 1/1/9 : bridge: _afsmChkRcvEncaps(): l=1811: tNetTask: AFSM-6313: port 1-7-2-0-adsl-0-35 misconfigured for PPPoA
MALC Configuration Guide
339
Configuring bridges
zSH> get bridge-interface-record 1-5-24-0-adsl-0-35/bridge Please provide the following: [q]uit. vpi: ----------------------> {0}: vci: ----------------------> {35}: vlanId: -------------------> {500}: stripAndInsert: -----------> {true}: customARP: ----------------> {false}: filterBroadcast: ----------> {false}: learnIp: ------------------> {false}: learnUnicast: -------------> {false}: maxUnicast: ---------------> {5}: learnMulticast: -----------> {false}: forwardToUnicast: ---------> {false}: forwardToMulticast: -------> {false}: forwardToDefault: ---------> {true}: bridgeIfCustomDHCP: -------> {false}: bridgeIfConfigGroupIndex: -> {0}: vlanIdCOS: ----------------> {0}: outgoingCOSOption: --------> {disable}: outgoingCOSValue: ---------> {0}: s-tagTPID: ----------------> {0x8100}: s-tagId: ------------------> {0}: s-tagStripAndInsert: ------> {false}: s-tagOutgoingCOSOption: ---> {s-tagdisable}: s-tagIdCOS: ---------------> {0}: s-tagOutgoingCOSValue: ----> {0}: mcastControlList: ---------> {}: maxVideoStreams: ----------> {0}: isPPPoA: ------------------> {true}: (enables the PPPoA session)
2
Display the bridge data. PPPoA port states are INITIAL (INI), PENDING (PND), DOWN (DWN), READY (RDY), DISCRVY (DSC), and UP. The new states available for PPPoA internet working are: –
READY (RDY) Waiting for PPPoA packet to initiate PPPoE discovery.
–
DISCVRY (DSC) PPPoE discovery initiated. Waiting for session ID to be obtained.
The A indicates that the port is a PPPoA port. When the PPPoA port status is UP, the BRAS MAC address and PPPoE session ID are also displayed. zSH> bridge show VLAN Bridge State Table Data --------------------------------------------------------------------Tagged ethernet2/bridge UP S Global default [U: 3600 sec, M: 120 sec, I: 60 sec] 500 1-7-48-0-adsl-0-35/bridge UP A 00:19:aa:3b:83:24 51758 500 1-7-1-0-adsl-0-35/bridge PND 500 1-7-2-0-adsl-0-35/bridge RDY A 500 1-7-3-0-adsl-0-35/bridge UP A 00:19:aa:3b:83:24 51768 500 1-7-4-0-adsl-0-35/bridge UP A 00:19:aa:3b:83:24 51788
340
MALC Configuration Guide
PPPoA - PPPoE Conversion
500 500 500 500 500 500 500
1-7-5-0-adsl-0-35/bridge 1-7-6-0-adsl-0-35/bridge 1-7-7-0-adsl-0-35/bridge 1-7-8-0-adsl-0-35/bridge 1-7-9-0-adsl-0-35/bridge 1-7-10-0-adsl-0-35/bridge 1-7-11-0-adsl-0-35/bridge
UP UP UP UP UP UP UP
A A A A A A A
00:19:aa:3b:83:24 00:19:aa:3b:83:24 00:19:aa:3b:83:24 00:19:aa:3b:83:24 00:19:aa:3b:83:24 00:19:aa:3b:83:24 00:19:aa:3b:83:24
51756 51796 51759 51754 51789 51755 51774
The bridgeshow ports command displays the following new fields: –
isPPPoA Indicates if interface is PPPoA or not.
–
aHdl For PPPoA interfaces, displays the handle address to PPPoA. Otherwise, 0x0 is displayed.
–
encapLLC Shows ‘Yes’ if PPPoA encapsulation is LLC or ‘No’ for VCMU encapsulation.
zSH> bridgeshow ports isPPPoA Yes, aHdl 0x6e6ac90, encapLLC No ifIndex 6351 externalVpi 0 - externalVci 35 shelf 1 - slot 7 - port 40 - subport 0 isUp Up - ifUnit 0 - ifType 159 - lineRRReg Line Up portGroupIndex 0 - index 45 - *pBridgeCookie 0x31E64D4 flags 5 Attached ValidAAL5 notReady 0, xmitError 0 - xmitOK 0 pktRcvd 1 localPktRcvd 0 mcastPktRcvd 0 bcastPktRcvd 0 ucastPktSent 0 mcastPktSent 0 bcastPktSent 0 pppoeTransitAddFail 0 macLen 6 - macAddr[6] 00.01.47.b1.19.a0 drvName[8] bridge aal5Data vpi 0 vci 273 aal5Port 0 extVpi 0 - extVci 0 netSvcType 2453 encapType 1 - port 40 - pcr 0 txTraffDescrIndex 0 - ifType 0 endPtLineStatus 1 drvHandle 0x6ada2c0, cmd 3, appHandle: 0x4055f68 bindSet 1 - ifaceSet 1 - xlateSet 1 bridgeRec vpi 0 - vci 35 - vlan/SlanId 500/0 - stripAndInsert Yes customARP No - filterBroadcast No learnIp No learnUnicast No maxUnicast 5 learnMcast No forwardToUnicast No forwardToMcast No forwardToDefault Yes vlanIdCOS 0 outgoingCOSOption disable outgoingCOSValue 0 isTkDrv Yes - ifIndexToBindTo 33 pDevice[256] - unit 0 - physIfType 125 - seqNumber 0x000000000 s_vlanInfoSent T, s/vlanIdSent 0/0, outCosValue 0x0 circuitId = 172.24.94.224:1-7-40-0-adsl-0-35 IGMP: initInjectCnt 3, lastInitQueryTick 0, lastQueryTick 0 lastIgmpJoinTick 0, lastIgmpLeaveTick 0
MALC Configuration Guide
341
Configuring bridges
PPPoE Intermediate Agent The MALC supports inserting port information into PPPoE packets that transit a MALC bridge interface. When the MALC receives a PPPoE Active Discovery Initiation (PADI) packet or a PPPoE Active Discovery Request (PADR) packet, the MALC can be configured to insert a customized string along with default port/slot identification into the vendor-specific portion of the PPPoE packet. The customized identification string can be 0 to 48 characters. The inserted information is TR-101 compliant and formatted as: eth slot/port[[:stagID]:vlan-tag]
The slot/port values identify the ingress slot/port on the MALC where the packet was received. If the packet is tagged with a VLAN tag, the VLAN tag is also added to the packet on ingress. If the packet is tagged with a SLAN tag, the SLAN tag is also added to the packet on ingress.
•
Untagged packet no customized string from slot 5 port 2: eth 5/2
•
VLAN 500 tagged packet no customized string from slot 5 port 2: eth 5/2 :500
•
VLAN 500 tagged, SLAN 4 tagged packet no customized string from slot 5 port 2: eth 5/2 :4 :500
•
VLAN 500 tagged, SLAN 4 tagged packet with customized string of “172.42.10.5” from slot 5 port 2: 172.42.10.4 eth 5/2 :4 :500
Note: For configurations with bridge intralinks or subtended MALC/ Raptor devices, ensure that the PPPoE intermediate agent feature is enabled on only the subtended devices.
Configuring bridge configuration records The MALC supports bridge configuration groups and records so an open-ended number of filter settings can be configured for a bridge interface. The same filter settings can also be easily applied to multiple bridge interfaces. Bridge configuration records for the intermediate agent options are assigned to bridge configuration groups on downlink bridge interfaces. Each bridge configuration record contains settings for type and value. The bridgeConfigType parameter specifies the bridgeinsertpppoevendortag option to enable the intermediate agent feature. The bridgeConfigValue parameter specifies the 0 to 48 character customized string to insert into PADI and PADR packets. Create bridge configuration records using the bridge-config-record profile. Specify group/instance index numbers to assign group and instance identification.
342
MALC Configuration Guide
PPPoE Intermediate Agent
1
Configure a new bridge-config-record for group1/instance1 and specifies the option to insert a PPPoE vendor tag with a customized prefix of ‘Malc123’.
zSH> new bridge-config-record 1/1 Please provide the following: [q]uit. bridgeConfigType: --> {bridgeinsertoption82}: bridgeinsertpppoevendortag bridgeConfigValue: -> {}: Malc123 .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
2
Use the config parameter of the bridge add command to create a bridge with the assigned bridge-config-record of group 1 instance 1. zSH>bridge add 1-4-1-0/adsl vc 0/35 td 1 config 1/1
Displaying port information The bridgeshow ports command displays a new field for pppoeTransitAddFail to help track the data insertion failures. To display port data, use the bridgeshow ports command. zSH>bridgeshow ports isPPPoA Yes, aHdl 0x6e6ac90, encapLLC No ifIndex 6351 externalVpi 0 - externalVci 35 shelf 1 - slot 7 - port 40 - subport 0 isUp Up - ifUnit 0 - ifType 159 - lineRRReg Line Up portGroupIndex 0 - index 45 - *pBridgeCookie 0x31E64D4 flags 5 Attached ValidAAL5 notReady 0, xmitError 0 - xmitOK 0 pktRcvd 1 localPktRcvd 0 mcastPktRcvd 0 bcastPktRcvd 0 ucastPktSent 0 mcastPktSent 0 bcastPktSent 0 pppoeTransitAddFail 0 macLen 6 - macAddr[6] 00.01.47.b1.19.a0 drvName[8] bridge aal5Data vpi 0 vci 273 aal5Port 0 extVpi 0 - extVci 0 netSvcType 2453 encapType 1 - port 40 - pcr 0 txTraffDescrIndex 0 - ifType 0 endPtLineStatus 1 drvHandle 0x6ada2c0, cmd 3, appHandle: 0x4055f68 bindSet 1 - ifaceSet 1 - xlateSet 1 bridgeRec vpi 0 - vci 35 - vlan/SlanId 500/0 - stripAndInsert Yes customARP No - filterBroadcast No learnIp No learnUnicast No maxUnicast 5 learnMcast No forwardToUnicast No forwardToMcast No forwardToDefault Yes vlanIdCOS 0 outgoingCOSOption disable outgoingCOSValue 0 isTkDrv Yes - ifIndexToBindTo 33 pDevice[256] - unit 0 - physIfType 125 - seqNumber 0x000000000 s_vlanInfoSent T, s/vlanIdSent 0/0, outCosValue 0x0 circuitId = 172.24.94.224:1-7-40-0-adsl-0-35 IGMP: initInjectCnt 3, lastInitQueryTick 0, lastQueryTick 0 lastIgmpJoinTick 0, lastIgmpLeaveTick 0
MALC Configuration Guide
343
Configuring bridges
344
MALC Configuration Guide
6
CONFIGURING ATM This chapter explains how to configure ATM cross connects on the MALC. It includes the following sections:
•
Configuration overview, page 365
•
Overview, page 365
•
VPI/VCI ranges, page 366
•
Configuring PCR and SCR values, page 368
•
Creating traffic descriptors, page 372
•
Creating VCLs and VPLs, page 374
•
Creating cross connects, page 378
•
Subtending, page 380 Tip: For information about configuring ATM management connections, see Configuring ATM management on page 29. For important background information about ATM on the MALC, see MALC ATM Overview on page 425.
MALC ATM Overview This chapter describes ATM support on the MALC. It includes the following sections:
•
ATM overview, page 346
•
ATM data, page 347
•
ATM voice, page 347
•
Cross connects, page 348
•
Early packet discard (EPD) and partial packet discard (PPD), page 348
•
Usage parameter control (UPC), page 349
•
ATM validation, page 349
•
VPI and VCI ranges, page 350
•
Virtual channel and virtual path links, page 352
MALC Configuration Guide
345
Configuring ATM
•
Service categories, page 352
•
Traffic descriptors, page 353
•
Connection admission control (CAC), page 356
•
ATM traffic policing, page 360
•
ATM statistics, page 365 Note: Read this chapter before configuring your device.
ATM overview The MALC supports voice, video, and data communications with different networking requirements for each signaling type. Voice traffic is sensitive to delay and transported by ATM Adaption Layer 2 (AAL2) at a Constant Bit Rate (CBR). Data traffic is not sensitive to delay and is carried over ATM Adaption Layer 5 (AAL5) at an Unspecified Bit Rate (UBR). Video streams and video–on–demand applications use Variable Bit Rate–Real Time (VBR-RT) over ATM Adaption Layer 5 (AAL5). For VoATM traffic on the voice gateway card, ATM traffic destined for the voice gateway card enters through one of the MALC uplink card’s ATM interfaces and is terminated on the voice gateway card. It is sent as TDM traffic to the local exchange switch. Figure 49 illustrates ATM on the MALC.
346
MALC Configuration Guide
MALC ATM Overview
Figure 48: ATM on the MALC
ATM
ATM
Local Exchange Switch
Layer 3 IP Layer 2 IP
SAR
ATM VCL/VPL
ATM CC
ATM VCL/VPL Layer 1
IP
DSL
ATM UNI Voice Gateway
ATM VCL/VPL
TDM
ATM data The MALC communicates with subscriber integrated access devices (IADs) or DSL modems using ATM over DSL interfaces. The MALC relays the traffic to the ATM Trunking card, which provides a high-speed interface to an ATM network. The MALC can also terminate management traffic and route it over the Ethernet to a management station. The MALC supports LLC encapsulation for AAL5 connections that it terminates.
ATM voice For voice traffic, the MALC supports derived voice using AAL2 over DSL interfaces. The ATM traffic is sent to the Uplink card, then onto the ATM network. On the MALC, voice is transported by ATM Adaption Layer 2 (AAL2) at a Constant Bit Rate (CBR). The MALC supports 120 AAL2 VCLs for POTS to AAL2 and ISDN to AAL2 voice connections. For VoATM traffic on the voice gateway card using VC-switching, the maximum number of VCs that can be allocated to an individual VC-switched VPI is determined by the zhoneAtmVpiMaxVci parameter in the atm-vpi profile.
MALC Configuration Guide
347
Configuring ATM
In VP-switching, the maximum VCI value that can be allocated to an individual VP-switched VP on the voice gateway card is determined by the zhoneAtmMaxVciPerVp parameter in the atm-vpi profile. Note: For more information on ATM support for the Voice Gateway card, see the MALC Hardware Installation Guide.
ATM Video ATM video signaling has different networking requirements than voice and data. Video streams and video–on–demand applications use Variable Bit Rate–Real Time (VBR-RT) over ATM Adaption Layer 5 (AAL5). Each video channel requires enough bandwidth to carry compressed video plus the IP and ATM overhead. For example, if the video stream is 2.5 Mbps with maximum packet size of 1316 bytes per packet, the formula for traffic descriptor is as follows: 2500000 / 8 /1316 = 238 video packets per second Total IP packet size = 1316 + 20 + 8 + 14 = 1358 bytes/packet 1358 bytes/packet / 48 bytes/cell = 28.333 cells/packet = 29 cells/packet 238 Packets/Sec * 29 Cells/Packet = 6902 cells/sec. Therefore, the PCR on the traffic descriptor should be 7000. If a system is deployed with 4 Video channels at 2.5 Mbps encoding, the traffic descriptor should be: 4 * 7000 = 28000 cells/ sec rtvbr.
Cross connects The MALC supports creating cross connects between any of its ATM-capable ports.
Early packet discard (EPD) and partial packet discard (PPD) In EPD, the ATM interface monitors the AAL5 traffic and discards an entire data frame if its output buffers do not have the space to process it. In PPD, the ATM interface drops the remaining cells of the frame if other cells of the frame have already been dropped. Both of these techniques increase the efficiency of the data transfer by dropping frames that have already been determined to be errored and will have to be retransmitted. Both EPD and PPD are disabled by default on the MALC.
348
MALC Configuration Guide
MALC ATM Overview
Usage parameter control (UPC) UPC is the process of monitoring and controlling the ATM traffic by enforcing the traffic parameters. The MALC allows disabling of UPC on a per-traffic descriptor basis. UPC is enabled by default.
ATM validation The Zhone CLI performs the following validation on ATM configuration:
•
VCLs cannot be created using VCIs in the reserved range (0 to 31), for any VPI.
•
VCLs being used in a cross connect cannot be deleted. To delete a VCL, first delete the cross connect.
•
ATM traffic descriptors used in VCLs cannot be modified.
•
A VCL can be used in only one cross connect.
MALC Configuration Guide
349
Configuring ATM
VPI and VCI ranges The MALC supports configurable VPI/VCI ranges for all ATM-capable cards except the T1/E1 32 port card. VPI/VCI ranges are configured in atm-vpi records. Table 22 lists the VPI/VCI support for MALC cards. Note the following about VPI/VCI ranges:
•
After creating or modifying atm-vpi records, the card must be rebooted.
•
A maximum of 256 VPIs can be created on a port.
As atm-vpi records are created, the system allocates connections from this pool. Each VP-switched VP uses one connection and each VC-switched VP uses one connection per allowable VC. Table 22: VPI/VCI ranges for MALC cards Card
Default ranges
Supported ranges
Maximum connections per card
MALC-UPLINK-DS3/ E3-ATM/IP
VPI: 0 to 3
VPI: 0 to 255 (per port)
16,384
VCI: 32 to 1,023
VCI: 32 to 4,095 (per VCI)
MALC-UPLINK-T1/ E1-ATM/TDM/IP-16
VPI: 0 to 3
VPI: 0 to 255 (per port)
VCI: 32 to 511
VCI: 32 to 4,095 (per VCI)
MALC-UPLINK-OC-3C/ STM1-ATM/IP
VPI: 0 to 7
VPI: 0 to 255 (per port)
VCI: 32 to 1,023
VCI: 32 to 4,095 (per VCI)
DSL (except the ADSL 48 port card)
VPI: 0 to 1 (per port)
VPI: 0 to 255 (per port)
448 (VC-switched to Uplink)
VCI: 32 to 255 (per VCI)
VCI: 32 to 1,023 (per VCI)
48 (VP-switched to Uplink)
MALC-ADSL-48B cards
VPI: 0 to 7 (per port)
VPI: 0 to 15 (per port)
448 (VC-switched to Uplink)
VCI: 32 to 63 (per VCI)
VCI: 32 to 127 (per VCI)
48 (VP-switched to Uplink)
VPI: 0-15
VPI: 0-15
448 (VC-switched to Uplink)
VCI: 32-63
VCI: 32-127
48 (VP-switched to Uplink)
MALC-ADSL+SPLTR-48 A/M-2S
VPI: 0 to 15 (per port)
VPI: 0 to 15 (per port)
448 (VC-switched to Uplink)
VCI: 32 to 63 (per VCI)
VCI: 32 to 127(per VCI)
48 (VP-switched to Uplink)
MALC-T1/E1-CES-12
VPI: 0 to 1
VPI: 0 to 255 (per port)
448 (VC-switched to Uplink)
VCI: 0 to 255
VCI: 0 to 1,023 (per VCI)
48 (VP-switched to Uplink)
VPI: 0 to 7 (one VPI for each UNI interface or IMA group )
VPI: 0 to 7
448 (VC-switched to Uplink)
VCI: 32 to 63
48 (VP-switched to Uplink)
Uplink cards
16,384
16,384
Line cards
MALC-ADSL-48-A/M
MALC-T1/E1-ATM-32
VCI: 32 to 63 (one VCI for each UNI interface or IMA group)
350
MALC Configuration Guide
496 total per card
VPI and VCI ranges
Table 22: VPI/VCI ranges for MALC cards (Continued) Card
Default ranges
Supported ranges
Maximum connections per card
MALC-VG-T1/E1-32-2ST1/ E1 32VG MALC-VG-T1/E1-8-2S
VP-switched:
VP-switched:
448 (VC-switched to Uplink)
VPI: 16 to 63 (per card)
VPI: 16 to 63 (per card)
VCI: 32 to 8,192 (per card)
VCI: 32 to 8,192 (per card)
7,680 (VP-switched to Uplink) (no external ATM interface)
MALC-ReachDSL-24
VPI: 0-7
VPI: 0-63
224 (VC-switched to Uplink)
VCI: 32-63
VCI: 32-63
24 (VP-switched to Uplink) 248 total per card
MALC-G.SHDSL-48
MALC-G.SHDLS-4W-12
VPI: 0-7
VPI: 0-63
448 (VC-switched to Uplink)
VCI: 32-127
VCI: 32-127
48 (VP-switched to Uplink)
VPI: 0-15
VPI: 0-63
224 (VC-switched to Uplink)
VCI: 32-63
VCI: 32-63
24 (VP-switched to Uplink) 248 total per card
ADSL+POTS-TDM/ PKT-48A/M-2S
Not Applicable
Not Applicable
Not Applicable
ADSL+POTS-TDM-48A/ M-2S
Not Applicable
Not Applicable
Not Applicable
MALC- ISDN 4B3T-24
Not Applicable
Not Applicable
Not Applicable
MALC-ISDN 2B1Q-24
Not Applicable
Not Applicable
Not Applicable
MALC- POTS-GBL-TDM/ PKT-24
Not Applicable
Not Applicable
Not Applicable
MALC-VDSL2-24
Not Applicable
Not Applicable
Not Applicable
MALC-ACTIVE-ETH-10
Not Applicable
Not Applicable
Not Applicable
MALC-DS3/E3-4
VPI: 0-3
VPI: 0-255
VCI: 32-1,023
VCI: 32-1,023
Not Applicable
Not Applicable
MALC-EFM-T1/E1-24
Not Applicable
MALC Configuration Guide
351
Configuring ATM
Virtual channel and virtual path links The MALC supports both VC and VP switching. In VC switching, cells are switched based on the VPI/VCI. In VP switching, cells are switched based on the VPI only. The VCI remains the same on both the incoming and outgoing interfaces. A virtual channel link (VCL) used for VC switching. It is uniquely identified by an index in the form interface-index/atm/VPI/VCI where:
•
interface-index is the unique name or address of the ATM layer on a given port. For example, 1-3-1-adsl/atm.
•
VPI/VCI pair is a unique connection identifier on that port.
A virtual path link (VPL) is used for VP switching. It is uniquely identified by an index in the form interface-index/atm/VPI where:
•
interface-index is the unique name or address of the ATM layer on a given port. For example, 1-3-1-adsl/atm.
•
VPI is a unique connection identifier on that port.
VCLs/VPLs are provisioned according to RFCs 2514 and 2515. Each VCL/ VPL on the MALC requires a VCL or VPL record and an associated ATM traffic descriptor. Note: A VCL/VPL can be used in only one cross connect. VCLs/VPLs being used in a cross connect cannot be deleted. To delete a VCL/VPL, first delete the cross connect. If a VCL/VPL is updated with a new traffic descriptor, the VCL/VPL must be brought down, then back up to update the policing value.
Service categories The MALC supports the following ATM service categories:
•
constant bit rate (CBR)
•
non-real-time variable bit rate (nrt-VBR)
•
real-time variable bit rate (rt-VBR)
•
unspecified bit rate (UBR)
Constant bit rate (CBR) The CBR service category is used by connections that require a constant and guaranteed cell rate during the lifetime of the connection. The sampling time for CBR is constant, with no delay. Cells exceeding the provisioned PCR rate are discarded.
352
MALC Configuration Guide
Virtual channel and virtual path links
Non-real-time variable bit rate (nrt-VBR) The nrt-VBR service category is used by applications that are tolerant of network delays and do not require a timing relationship on each side of the connection. The nrt-VBR service supports somewhat bursty connections having less-stringent delay requirements than rt-VBR and CBR, but still require low cell loss. The source traffic descriptor is characterized by peak cell rate (PCR), sustainable cell rate (SCR), and maximum burst size (MBS).
Real-time variable bit rate (rt-VBR) The rt-VBR service category is used by applications that require a tightly constrained delay and delay variation. The source traffic descriptor is characterized by peak cell rate (PCR), sustainable cell rate (SCR), and maximum burst size (MBS).
Unspecified bit rate (UBR) The UBR service category does not specify traffic-related guarantees. No numerical commitments are made with respect to the cell loss ratio (CLR) experienced by the connection, or the cell transfer delay (CTD) experienced by the cells. With UBR service, the available bandwidth is fairly distributed to the active UBR subscribers.
Traffic descriptors Each ATM endpoint requires a traffic descriptor, which defines the traffic parameters and type of service provided on ATM interfaces. Traffic descriptors are configured in atm-traf-descr records. Quality of Service (QoS) parameters such as max cell transfer delay (maxCTD) and cell loss ratio (CLR) do not apply to a single node on the network and so are not provisioned for individual VCs.
Configuring PCR and SCR The atm-vcl-param profile defines the allowable values for the PCR and SCR for certain traffic types. The values in this profile are used as follows:
•
The SCR for rt-VBR traffic descriptors must use one of the first 16 rates (vcl-rate-param1 through vcl-rate-param16)
•
The PCR for CBR traffic descriptors can use any of the 32 rates.
•
For a UBR traffic descriptor, if usage-parameter-control in an ATM traffic descriptor is set to false, or if PCR is greater than the modem trained rate, then the UBR traffic is shaped to one of the 32 rates. The shaper will pick a rate that is equal to or less than the modem trained rate. If there are multiple rates less than the modem trained rate, the one closest to the trained rate will be selected.
MALC Configuration Guide
353
Configuring ATM
Each PVC on the MALC is assigned a PCR of 182 cells per second (for G.711 voice calls) or 91 CPS (for G.726 voice calls). An initial 182 CPS is needed to support sending and receiving of CAS packets. To support voice VCs use the following formulas: For G.711 calls, use the formula:
•
PCR = (CIDS per VC * 182) + 182
•
SCR = (CIDS per VC * 3/5) + (CIDS per VC * 182)
For G.726, use the formula:
•
PCR = (CIDS per VC * 91) + 91
•
SCR = (CIDS per VC * 3/5) + (CIDS per VC * 91)
For example, 8 CID per VC produces the following values for PCR and SCR: PCR=1638 CPSSCR=1460 CPS Note: When fax and modems calls are connected on G.726 compress mode, the full 182 CPS are used.
Traffic descriptor parameters Table 23 shows the required parameters used to define MALC traffic descriptors and the validation rules associated with them. Table 23: ATM traffic descriptor parameters Service category
TD type
td_param1
td_param2
td_param3
td_param4
CBR
atmNoClpNoScr (TD type 2) OID 1.3.6.1.2.1.37.1.1.2
PCR for CLP=0+1 traffic
Not used
Not used
Not used
PCR for CLP=0 traffic, excess traffic tagged as CLP=1
Not used
Not used
UBR
must be > 0 For CBR, must match a value in atm-vcl-param profile
UBR
atmClpTaggingNoScr (TD type 4)
PCR for CLP=0+1 traffic
OID 1.3.6.1.2.1.37.1.1.4
must be > 0
must be > 0
354
MALC Configuration Guide
Virtual channel and virtual path links
Table 23: ATM traffic descriptor parameters (Continued) Service category
TD type
td_param1
td_param2
td_param3
td_param4
nrt-VBR
atmClpNoTaggingScr (TD type 6)
PCR for CLP=0+1 traffic
SCR for CLP=0 traffic
MBS
Not used
OID 1.3.6.1.2.1.37.1.1.6
td_param1 > td_param2
For rt-VBR, must match a value in atm-vcl-param profile
rt-VBR
must be > 1
must be > 0 nrt-VBR rt-VBR
atmClpTaggingScr (TD type 7)
PCR for CLP=0+1 traffic
OID 1.3.6.1.2.1.37.1.1.7
td_param1 > td_param2
SCR for CLP=0 traffic, excess traffic tagged as CLP=1
MBS
Not used
must be > 1
For rt-VBR, must match a value in atm-vcl-param profile must be > 0 CBR
atmClpTransparentNoScr (TD Type 9) OID 1.3.6.1.2.1.37.1.1.9
PCR Must match a value in atm-vcl-param profile
CDVT
Not used
Not used
MBS
CDVT
Not used
Not used
must be > 0
must be > 0 nrt-VBR rt-VBR
atmClpTransparentScr (TD Type 10) OID 1.3.6.1.2.1.37.1.1.10
PCR for CLP=0+1 traffic
SCR for CLP=0 traffic
must be > 0
For rt-VBR, must match a value in atm-vcl-param profile must be > 0
CBR
atmNoClpNoScrCdvt (TD Type 12)
PCR
CDVT
must be > 0
must be > 0
OID 1.3.6.1.2.1.37.1.1.12
Must match a value in atm-vcl-param profile
MALC Configuration Guide
355
Configuring ATM
Table 23: ATM traffic descriptor parameters (Continued) Service category
TD type
td_param1
td_param2
td_param3
td_param4
nrt-VBR
atmClpNoTaggingScrCdvt (TD type 14)
PCR for CLP=0+1 traffic
SCR for CLP=0 traffic
MBS
CDVT
OID 1.3.6.1.2.1.37.1.1.14
td_param1 > td_param2
For rt-VBR, must match a value in atm-vcl-param profile
rt-VBR
must be > 1
must be > 0 nrt-VBR rt-VBR
atmClpTaggingScrCdvt (TD type 15)
PCR for CLP=0+1 traffic
OID 1.3.6.1.2.1.37.1.1.15
td_param1 > td_param2
SCR for CLP=0 traffic, excess traffic tagged as CLP=1
MBS
CDVT
must be > 1
For rt-VBR, must match a value in atm-vcl-param profile must be > 0
Tip: Refer to the following specifications for more information about traffic descriptors:
• ATM Forum, ATM User-Network Interface, Version 3.0 (UNI 3.0) Specification, 1994.
• ATM Forum, ATM User-Network Interface, Version 3.1 (UNI 3.1) Specification, November 1994.
Traffic descriptor configuration rules Note: When configuring the traffic descriptors, it is important that they follow the rules described in this section. A traffic descriptor cannot be saved if the parameters violate these rules. Note the following information about traffic descriptors on the MALC:
•
ATM traffic descriptors used in active VCLs cannot be modified. To modify a traffic descriptor, first bring down VCLs that use the descriptor.
•
For atmNoClpNoScr with a service category of rtvbr, trnk-vcl-rate of unused is allowed for backward compatibility. If set to unused, the system uses a rate-16k for the purposes of CAC.
Connection admission control (CAC) MALC Uplink cards support connection admission control (CAC) and provisioning of oversubscription factors on a per port basis. The CAC
356
MALC Configuration Guide
Virtual channel and virtual path links
functions on the Uplink card will not accept new connections if they exceed the remaining bandwidth. Note the following about CAC and service categories:
•
For CBR VCLs, the PCR value of each VCL is subtracted from the available rt-VBR bandwidth to determine whether the VCL can be created.
•
For rt-VBR VCLs, the SCR value of each VCL is subtracted from the available rt-VBR bandwidth to determine whether the VCL can be created.
•
For nrt-VBR VCLs, the SCR of each VCL is subtracted from the available nrt-VBR bandwidth to determine whether the VCL can be created.
•
For UBR VCLs, CAC does not apply. The system will provide up to the bandwidth configured for UBR connections, if the bandwidth is available.
CAC oversubscription CAC enables the ATM interface to service more data VCL connections than the bandwidth allows. Because not all connections are likely to be active at the same time, an interface can support a larger number of PVCs. When oversubscription is enabled, CAC calculates available bandwidth in the system by dividing the SCR (for nrt-VBR or rt-VBR VCLs) value by the cac-divider parameter in the atm-traf-descr. It then uses that value to determine if the VCL can be created. For example, to oversubscribe bandwidth at a rate of 4:1, set cac-divider to 4. By default, oversubscription is not enabled and the cac-divider is set to 1. Note that CAC oversubscription should not be used to oversubscribe AAL2 voice connections.
MALC Configuration Guide
357
Configuring ATM
Bandwidth allocation for ATM cards The bandwidth allocated to ATM traffic types and used by CAC is specified in the card-atm-configuration parameter in the card-profile for the Uplink cards. (See Table 24.) Table 24: ATM bandwidth allocation Setting
DS3
E3
T1
E1
OC-3/STM1
104,268 CPS
80,000 CPS
28,976 CPS total (8 T1s)/ 3622 each
36,224 CPS total (8 E1s)/ 4528 each
353,207 CPS
UBR 1%
1,042 CPS
800 CPS
289 CPS
362 CPS
3,532 CPS
nrt-VBR: 94%
98,011 CPS
75,200 CPS
27,237 CPS
34,050 CPS
332,014 CPS
CBR/rt-VBR: 5%
5,213 CPS
4,000 CPS
1,448 CPS
1,811 CPS
17, 660 CPS
UBR: 5%
5,213 CPS
4,000 CPS
1,448 CPS
1,811 CPS
17, 660 CPS
nrt-VBR: 80%
83,414 CPS
64,000 CPS
23,180 CPS
28,979 CPS
282,565 CPS
CBR/rt-VBR: 15%
15,640 CPS
12,000 CPS
4,346 CPS
5,433 CPS
52,981 CPS
UBR: 5%
5,213 CPS
4,000 CPS
1,448 CPS
1,812 CPS
17, 660 CPS
nrt-VBR: 65%
67,774 CPS
52,000 CPS
18,834 CPS
23,545 CPS
229,584 CPS
CBR/rt-VBR: 30%
31,280 CPS
24,000 CPS
8,692 CPS
10,867 CPS
105,962 CPS
UBR: 5%
5,213 CPS
4,000 CPS
1,448 CPS
1,811 CPS
17, 660 CPS
nrt-VBR: 50%
52,134 CPS
40,000 CPS
14,488 CPS
18,112 CPS
176,603 CPS
CBR/rt-VBR: 45%
46,920 CPS
36,000 CPS
13,039 CPS
16,300 CPS
158,943 CPS
UBR: 5%
5,213 CPS
4,000 CPS
1,448 CPS
1,811 CPS
17, 660 CPS
nrt-VBR: 35%
36,493 CPS
28,000 CPS
10,141 CPS
12,678 CPS
123,622 CPS
CBR/rt-VBR: 60%
62,560 CPS
48,000 CP
17,385 CPS
21,734 CPS
211,924 CPS
UBR: 5%
5,213 CPS
4,000 CPS
1,448 CPS
1,811 CPS
17, 660 CPS
nrt-VBR: 20%
20,853 CPS
16,000 CPS
5,795 CPS
7,244 CPS
70,641 CPS
CBR/rt-VBR: 75%
78,201 CPS
60,000 CPS
21,732 CPS
27,168 CPS
264,905 CPS
UBR: 1%
1,042 CPS
800 CPS
289 CPS
362 CPS
3,532 CPS
nrt-VBR: 5%
5,213 CPS
4,000 CPS
1,448 CPS
1,811 CPS
17, 660 CPS
CBR/rt-VBR: 94%
98,011 CPS
75,200 CPS
27,237 CPS
34,050 CPS
332,014 CPS
vbnrt95rt5
vbnrt80rt15
vbnrt65rt30
vbnrt50rt45
vbnrt35rt60
vbnrt20rt75
vbnrt5rt95
358
MALC Configuration Guide
Virtual channel and virtual path links
Table 25 shows the parameters used by CAC for specified service categories. Table 25: Service category traffic descriptor parameters Service category
Parameters specified
CAC
CBR
td_param1 (peak cell rate (PCR))
td_param1 (PCR)
td_param2 (cell delay variation tolerance (CDVT)) nrt-VBR
td_param1 (peak cell rate (PCR)) td_param2 (sustained cell rate (SCR))
td_param2 (SCR)
td_param3 (maximum burst size (MBS)) td_param4 (cell delay variation tolerance (CDVT)) rt-VBR
td_param1 (peak cell rate (PCR)) td_param2 (sustained cell rate (SCR))
td_param2 (SCR)
td_param3 (maximum burst size (MBS)) td_param4 (cell delay variation tolerance (CDVT)) UBR
td_param1 (peak cell rate (PCR))
N/A
Example CAC calculation The following is a sample calculation on DS3 Uplink card with a line speed of 104,268 CPS (the DS3 line rate of 45,000,000 bits/sec minus overhead) and no oversubscription: If the atm-configuration parameter is set to vbnrt20rt75, the ATM bandwidth allocation is as follows: 104,268 * 0.20 = 20,853 CPS is allocated to nrt-VBR 104,268 * 0.75 = 78,201 CPS is allocated to rt-VBR 104,268 * 0.05 = 5,213 is allocated to UBR Total bandwidth available for rt-VBR VCL
20,853 CPS
nrt-VBR VCL # 1 with SCR 12,000. Since there is enough available bandwidth, CAC allows the VCL
-12,000 CPS
Remaining bandwidth for rt-VBR VCLS
8,853 CPS
nrt-VBR VCL # 2 with SCR of 9,000
-9000 CPS
VCL rejected by CAC, not enough available bandwidth
For CBR or rt-VBR traffic, the CAC algorithm is the same.
MALC Configuration Guide
359
Configuring ATM
ATM traffic policing The MALC polices traffic using the ATM continuous-state leaky bucket algorithm. It monitors the incoming ATM cells to ensure that they adhere to the VCL traffic descriptors. If they do not, they are either dropped or tagged with a lower cell loss priority (CLP), depending on which traffic descriptor is in use for the VCL. Tip: For more information about traffic policing, refer to ATM Forum Traffic Management Specification Version 4.0 and ITU-T I.371.
Enforcing SCR and MBS Bucket B polices SCR and MBS parameters. It applies to the following TD types:
•
atmClp NoTagging Scr (TD type 6)
•
atmClp Tagging Scr (TD type 7)
•
atmClpNoTaggingScrCdvt (TD type 14)
•
atmClpTagging ScrCdvt (TD type 15)
Bucket B uses the following formula: cdvt_btB = 1,000,000/SCR + [(MBS - 1)*(1,000,000/SCR - 1,000,000/PCR)] For these traffic descriptors, limit = cdvt_btB * F/68. where F is
•
100 for MALC OC-3c/STM1 cards and MALC DS3/E3 cards
•
50 for DSL line cards and MALC T1/E1 IMA cards
Bucket B either drops or tags non-conforming cells, depending on the TD type. It then passes the cells that have not been dropped to bucket A.
Enforcing PCR and CDVT Bucket A polices PCR and CDVT parameters. It applies to all TD types. Bucket A uses the following formula: cdvt_btA = [(td_param2 or td_param4)/10.0] where: td_param2 is CDVT for CBR VCLs with the exception of AtmNoClpNoScr traffic type td_param4 is CDVT for rt-VBR VCLs If the CDVT is not specified, the default value of 30000 (tenths of microseconds) is used. For these traffic descriptors, limit = cdvt_btA * F/68.
360
MALC Configuration Guide
Virtual channel and virtual path links
Bucket A drops cells that do not conform to the PCR.
General policing rules ATM traffic descriptors must adhere to the following rules:
•
The limit must be within the following range: 1 < limit < 1,966,080 (1.8751 * 0x100000)
•
cdvt_btA and cdvt_btB must be greater than 68/F
where F is
•
100 for MALC OC-3c/STM1 cards and MALC DS3/E3 cards
•
50 for DSL line cards and MALC T1/E1 IMA cards
Traffic shaping The MALC provides traffic shaping features for most uplink cards that protects the cards from being disabled by data flooding. Each uplink card has a limit to the amount of incoming data that can enter it in a given time interval. Once the threshold of maximum data allowed into the card has been exceeded, the uplink port will partition or become disabled. Two types of instances exist where port disabling can occur because of data overflow.
•
benevolent transmissions are sent to the card that contains large amounts of oversize packets or cells, for video and voice data for use by the customer. Sometimes, the amount of data exceeds the amount of incoming packets or cells that the port can handle, inadvertently disabling the port.
•
malicious transmissions are sent to the card that contain deliberately large amounts of oversize packets or cells for any application, designed explicitly to bring down the network. The amount of data exceeds the amount of incoming packets or cells that the port can handle, maliciously disabling the port.
The MALC provides automatic traffic shaping that helps manage the flow of packets or cells sent to the uplink card.Using defined service categories, the MALC now ensures that the uplink card port cannot be overloaded and disabled. The MALC uses the service categories described in the following table to perform the traffic shaping:
MALC Configuration Guide
361
Configuring ATM
Table 26: Common Service Category Values Service Category
Description
CBR
Constant bit rate. Used by connections that require a constant and guaranteed cell rate during the lifetime of the connection.
nrt-VBR
Non-real-time variable bit rate. Used by applications that are tolerant of network delays and do not require a timing relationship on each side of the connection.
rt-VBR
Real-time variable bit rate. Used by applications that require a tightly constrained delay and delay variation.
UBR
Unspecified bit rate. Does not specify traffic-related guarantees.
CBR, nrt-VBR, and rt-VBR each enable traffic shaping that will limit incoming packets to the uplink port. Note that if you have the UBR value specified as the Service Category in the profile, traffic shaping will be disabled and no rate limiting will be applied to incoming packets. Other traffic descriptor variables related to service are described in the following table. Table 27: Traffic Descriptor Variables for Traffic Shaping Variable
Description
PCR
Peak Cell Rate. This variable indicates the top-level threshold that identifies the most amount of traffic in Mbps that can enter the uplink port. Maps to the td_param1.
SCR
Sustained Cell Rate. This variable is time-oriented, indicating the maximum amount of traffic in Mbps that can pass through the uplink port over a preset period of time. Maps to td_param2.
CVR
Cell Variation Delay. This variable indicates the amount of time that the uplink can wait to accept traffic. Maps to td_param3.
Listing traffic descriptors and Peak Cell Rates To configure traffic shaping limits, you need to change PCRs (Peak Cell Rates) in the traffic descriptor associated with the card. To identify the traffic descriptor you need to change, display existing traffic descriptors by issuing the list atm-traf-descr command. To list ATM traffic descriptors issue the list atm-traf-descr command: zSH> list atm-traf-descr atm-traf-descr 1 atm-traf-descr 49050
362
MALC Configuration Guide
Virtual channel and virtual path links
atm-traf-descr 1210 atm-traf-descr 2000
Configuring traffic shaping in traffic descriptors To change the PCR values of the traffic descriptor, display the contents of the desired descriptor using the get command. The following example presupposes you want to perform traffic shaping on the traffic descriptor with the 49050 value. 1
To display traffic descriptor values: zSH> get atm-traf-descr 49050 td_type: ----------------------> td_param1: --------------------> td_param2: --------------------> td_param3: --------------------> td_param4: --------------------> td_param5: --------------------> cac-divider: ------------------> td_service_catgory: -----------> td_frame_discard --------------> usage-parameter-control ------->
{atmNoClpNoScr} {49050} {0} {0} {0} {0} {1} {ubr} {false} {true}
Note that td_param1 is the variable that contains the PCR value for this traffic descriptor. You have now changed the PCR from 49,050 Mbps to 500 Mbps. 2
To change the PCR value, issue the update atm-traf-descr command. This example shows limiting the allowable incoming traffic rate (PCR) of 500 Mbps. zSH> update atm-traf-descr 49050 Please provide the following: [q]uit td_type: ----------------------> {atmNoClpNoScr}: td_param1: --------------------> {49050}: 500 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 changes? [s]ave, [c]hange or [q]uit: s
Shaping for non-ADSL2+ cards with GigE uplinks Shaping for non-ADSL2+ cards with GigE uplinks is performed on the GigE uplink card (MALC-UPLINK-2-GE, MALC-UPLINK-GE). Constant Bit Rate (Cbr) is the highest priority.
MALC Configuration Guide
363
Configuring ATM
For Unspecified Bit Rate (Ubr), the Peak Cell Rate (Pcr) as specified in the traffic descriptor parameter td-param1 is enforced. For Variable Bit Rates (Vbr-nt, Vbr-Nrt), the Peak Cell Rate (Pcr) as specified in the traffic descriptor parameter td-param1 and Sustained Cell Rate (Scr) as specified in the traffic descriptor parameter td-param2. Burst up to the Pcr are allowed with regular traffic at the Scr. The minimum scheduler rate is restricted to multiples of 167 frames per second and 535 frames per second for depending on the type of line card to which traffic is sent. Line cards with rates restricted to multiples of 167 frames per second:
•
MALC-ADSL-48A, MALC-ADSL+POTS-TDM-48A-2S, MALC-ADSL+POTS-TDM/PKT-48A-2S
•
MALC-ADSL-48B
Line cards with rates restricted to multiples of 535 frames per second:
•
MALC-DS3/E3-4
•
MALC-POTS-GBL-TDM/PKT-24
•
MALC-ISDN4B3T-24
•
MALC-ISDN2B1Q-24
•
MALC-SHDSL-48
•
MALC-G.SHDSL-4W-12
For all types of rates, the rate specified for the traffic descriptor parameters is rounded up to the next multiple of the minimum rate.
Traffic shaping for 1.13.x and higher mixed IP and ATM networks When the MALC SLMS software loads transitioned from Release 1.12.x to 1.13.x, traffic descriptor orientations changed so that the concept of an ATM uplink with TX and RX directions do not exist. Instead, the MALC uses the ATM TX and RX settings of the line card and then reflects them, in reverse for the uplink side. For example:
•
Line card ATM TX = 4000, RX= 8000
•
Uplink ATM TX = 8000, RX = 4000
The required upstream and downstream DSL maximum line rates (service guaranteed rate) should equal the TD rate plus 15% for margin. Also, recommended is to set the asymmetrical min and max rates at the same number creating both a stable and predictable flow control. The MALC shapes UBR traffic in the downstream direction using the td-param1 traffic descriptor that's set for a particular port. The subscriber will be able to send traffic at the provisioned and trained line rate.
•
364
MALC Configuration Guide
Downstream Direction = ADSL port at 115% of required downstream line rate. Traffic regulated with the UBR ATM traffic descriptor at 100%
Configuration overview
•
Upstream Direction = ADSL port set to 115% of required upstream line rate. UBR ATM traffic descriptor is not used and should be set to match the downstream.
Symmetrical (Upstream and Downstream) traffic descriptors are strongly recommend to simplify the TX and RX calculations.
ATM statistics Real-time ATM statistics on the MALC are provided through the NetHorizhon ZMS client. ZMS supports the following ATM statistics:
•
ATM VCL
•
ATM VPL
•
AAL2
The ZMS performance manager periodically collects real-time statistical data. You can monitor real-time data at a polling interval of your choice. For information on how to access ZMS ATM statistics, refer to the NetHorizhon User’s Guide and the NetHorizhon online help.
Configuration overview This section provides an overview of how to configure MALC ATM data connections references to where to find detailed information. 1. Modify the VPI/VCI ranges of the slot card, if necessary. See VPI/VCI ranges on page 366. 2. Modify the allowable PCR and SCR values, if necessary. See Configuring PCR and SCR values on page 368. 3. Create traffic descriptors. See Creating traffic descriptors on page 372. 4. Create VCLs or VPLs, as required. –
See Creating VCLs (VC switching) on page 376.
–
See Creating VPLs (VP switching) on page 377
5. Create cross connects. See Creating cross connects on page 379.
Overview Figure 49 shows an overview of ATM on the MALC.
MALC Configuration Guide
365
Configuring ATM
Figure 49: ATM cell relay on the MALC
ATM
ATM
Local Exchange Switch
Layer 3 IP Layer 2 IP
SAR
ATM VCL/VPL
ATM CC
ATM VCL/VPL Layer 1
IP
DSL
ATM UNI Voice Gateway
ATM VCL/VPL
TDM
VPI/VCI ranges The MALC supports configurable VPI/VCI ranges for all ATM-capable cards. VPI/VCI ranges are configured in atm-vpi records. Note the following about VPI/VCIs ranges:
•
After creating or modifying atm-vpi records, the card must be rebooted.
•
A maximum of 256 VPIs can be created on a port.
•
As atm-vpi records are created, the system allocates connections from the available pool of connections. Each VP-switched VP uses one connection and each VC-switched VP uses one connection per allowable VC.
Changing VPI/VCI ranges Note that although you can create switched VCs without modifying the VPI/ VCI ranges, if you create the first atm-vpi (to change the VPI/VCI ranges on a card or to create a VP switched connection), the system automatically creates an atm-vpi profile for each VPI used in existing cross connects. The system determines how many VCIs are assigned to each VPI, then populates the zhoneAtmVpiMaxVci parameter in an atm-vpi record with the value (in the form 2n) closest to that number. For example, if the system has cross connects configured with the following VPI/VCI pairs:
366
MALC Configuration Guide
VPI/VCI ranges
VPI/VCI
atm-vpi profile created
Comment
VPI 0 VCI 100 VPI 0 VCI 101 VPI 0 VCI 102
atm-vpi interface-name/atm/0
zhoneAtmVpiMaxVci = 128 because 128 is the smallest power of 2 that is greater than the highest VCI (102) created using that VPI.
VPI 1 VCI 1001 VPI 1 VCI 1001 VPI 1 VCI 1002 VPI 1 VCI 1003 VPI 1 VCI 1004
atm-vpi interface-name/atm/1
zhoneAtmVpiMaxVci: --->
{128}
zhoneAtmVpiSwitched: ->
{vc}
zhoneAtmVpiMaxVci: --->
{1024}
zhoneAtmVpiSwitched: ->
{vc}
zhoneAtmVpiMaxVci = 1024 because 1024 is the smallest power of 2 that is greater than the highest VCIs (1004) created using that VPI.
After the atm-vpi records have been created, you can update them to change the default VCI values, if desired.
Configuration overview The following table summarizes the configuration tasks for changing the VPI/ VCI ranges. Task
Command
Create an atm-vpi record. This specifies the maximum number of switched VCs on that connection (or 0 for VP switching) as well as whether the connection is VP or VC switched.
new atm-vpi index/atm/vpi Up to 256 VPIs can be created on a port.
Update the atm-vpi records if you want to change the default atm-vpi records the system creates.
update atm-vpi index/atm/vpi
Reboot the card.
slotreboot slot
Changing VPI/VCI ranges 1
Create an atm-vpi record for the VP: –
If the VP is going to be switched, leave zhoneAtmVpiMaxVci at 0.
–
If the VC is going to be switched, change zhoneAtmVpiMaxVci to the number of VCs for that VP. Note that the value must be a power of 2 greater than 31. For example, 32, 64, 128, 256, 512, 1028, or 2048.
The following example creates VPI 10 on an OC3-c/STM1 card, with 1024 allowable VCs: zSH> new atm-vpi 1-1-1-0-sonet/atm/10 interface-index/atm/ VPI Please provide the following: [q]uit. zhoneAtmVpiMaxVci: ---> {0}: 1024 zhoneAtmVpiSwitched: -> {vc}: zhoneAtmMaxVciPerVp: -> {0}:
MALC Configuration Guide
367
Configuring ATM
.................... Save new record? [s]ave, [c]hange or [q]uit: New record saved.
s
Note: For VP-switched connections, change the zhoneAtmVpiSwitched parameter to vp. After the first atm-vpi record is saved, the system will automatically create atm-vpi records for all VPIs used in existing cross connects. If you need to modify the atm-vpi records the system has automatically created, update the records as in the following example: zSH> update atm-vpi 1-1-2-0-sonet/atm/11 interface-index/ atm/VPI Please provide the following: [q]uit. zhoneAtmVpiMaxVci: ---> {1024}: 2048 zhoneAtmVpiSwitched: -> {vc}: zhoneAtmMaxVciPerVp: -> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
2
After the system has finished creating the atm-vpi records and you have finished updating them (if desired), reboot the slot card: zSH> slotreboot 1
Configuring PCR and SCR values The atm-vcl-param profile defines the allowable values for the PCR and SCR for certain traffic types. The values in this profile are used as follows:
•
The SCR for rt-VBR traffic descriptors must use one of the first 16 rates.
•
The PCR for CBR traffic descriptors can use any of the 32 rates.
•
For a UBR traffic descriptor, if usage-parameter-control in an ATM traffic descriptor is set to false, or if PCR is greater than modem trained rate, then the UBR traffic is shaped to one of the 32 rates. The shaper will pick a rate that is equal to or less than the modem trained rate. If there are multiple rates less than the modem trained rate, the one closest to the trained rate will be selected. Note: If your device is being managed by ZMS, changes to the atm-vcl-param profile should be made using ZMS. If you use the CLI to change the profile, perform a full config sync update after making the change.
Note the following about the values in this profile:
368
MALC Configuration Guide
•
Rates are in cells per second (CPS)
•
Duplicate rates are not permitted
Configuring PCR and SCR values
•
Rates must be in ascending order within the first 16 rates and also within the second 16 rates.
To view the default values for the atm-vcl-param profile use the get command: zSH> get atm-vcl-param 0 vcl-rate-param1: -------> vcl-rate-param2: -------> vcl-rate-param3: -------> vcl-rate-param4: -------> vcl-rate-parma5: -------> vcl-rate-param6: -------> vcl-rate-param7: -------> vcl-rate-param8: -------> vcl-rate-param9: -------> vcl-rate-param10: ------> vcl-rate-param11: ------> vcl-rate-param12: ------> vcl-rate-param13: ------> vcl-rate-param14: ------> vcl-rate-param15: ------> vcl-rate-param16: ------> vcl-rate-grp2-param1: --> vcl-rate-grp2-param2: --> vcl-rate-grp2-param3: --> vcl-rate-grp2-param4: --> vcl-rate-grp2-param5: --> vcl-rate-grp2-param6: --> vcl-rate-grp2-param7: --> vcl-rate-grp2-param8: --> vcl-rate-grp2-param9: --> vcl-rate-grp2-param10: -> vcl-rate-grp2-param11: -> vcl-rate-grp2-param12: -> vcl-rate-grp2-param13: -> vcl-rate-grp2-param14: -> vcl-rate-grp2-param15: -> vcl-rate-grp2-param16: ->
{38} {76} {151} {189} {302} {378} {604} {755} {1208} {1510} {3661} {4825} {28302} {37736} {106133} {365567} {2264} {3019} {4151} {7075} {9434} {11792} {14151} {16509} {18868} {23585} {33019} {56604} {75472} {150943} {226415} {301887}
Table 28 explains the atm-vcl-param default settings. Table 28: atm-vcl-param settings Setting
Application
Cells per second
38
1 to 2 DS0s at 5:1 to 10:1 oversubscription
38 CPS
76
2 to 4 DS0s at 5:1 to 10:1 oversubscription
76 CPS
151
4 to 8 DS0s at 5:1 to 10:1 oversubscription
151 CPS
MALC Configuration Guide
369
Configuring ATM
Table 28: atm-vcl-param settings (Continued) Setting
Application
Cells per second
189
1 DS0 no oversubscription
189 CPS
302
8 to 16 DS0s at 5:1 to 10:1 oversubscription
302 CPS
378
2 DS0 no oversubscription
378 CPS
604
16 to 32 DS0s at 5:1 to 10:1 oversubscription
604 CPS
755
4 DS0 no oversubscription
755 CPS
1208
32 to 64 DS0s at 5:1 to 10:1 oversubscription
1208 CPS
1510
8 DS0 no oversubscription
1510 CPS
3661
Full T1
3661 CPS
4825
Full E1
4825 CPS
28302
8 T1s
28,303 CPS
37736
8 E1s
37,736 CPS
106133
DS3
106,133 CPS
365567
O-C3c/STM1
365,567 CPS
Changing the atm-vcl-param profile values Caution: Changing the values in the atm-vcl-param profile requires a system reboot. To update the atm-vcl-param profile with new values: zSH> update atm-vcl-param 0 Please provide the following: [q]uit. vcl-rate-param1: --> {38}: vcl-rate-param2: --> {76}: vcl-rate-param3: --> {151}: 164 vcl-rate-param4: --> {189}: 196 vcl-rate-parma5: --> {302}: vcl-rate-param6: --> {378}: vcl-rate-param7: --> {604}: vcl-rate-param8: --> {755}: vcl-rate-param9: --> {1208}: vcl-rate-param10: -> {1510}: vcl-rate-param11: -> {3661}:
370
MALC Configuration Guide
Configuring PCR and SCR values
vcl-rate-param12: -> {4825}: vcl-rate-param13: -> {28302}: vcl-rate-param14: -> {37736}: vcl-rate-param15: -> {106133}: vcl-rate-param16: -> {365567}: vcl-rate-grp2-param1: --> {2264} vcl-rate-grp2-param2: --> {3019} vcl-rate-grp2-param3: --> {4151} vcl-rate-grp2-param4: --> {7075} vcl-rate-grp2-param5: --> {9434} vcl-rate-grp2-param6: --> {11792} vcl-rate-grp2-param7: --> {14151} vcl-rate-grp2-param8: --> {16509} vcl-rate-grp2-param9: --> {18868} vcl-rate-grp2-param10: -> {23585} vcl-rate-grp2-param11: -> {33019} vcl-rate-grp2-param12: -> {56604} vcl-rate-grp2-param13: -> {75472} vcl-rate-grp2-param14: -> {150943} vcl-rate-grp2-param15: -> {226415} vcl-rate-grp2-param16: -> {301887} .................... Save changes? [s]ave, [c]hange or [q]uit: s Changing atm-vcl-param 0 will result in a system reboot. Continue? [y]es or [n]o: y Atm configuration changed system is rebooting ...Record updated.
MALC Configuration Guide
371
Configuring ATM
Creating traffic descriptors When you create a traffic descriptor, specify an index which is used to associate a traffic descriptor with an ATM virtual channel links (VCLs) in an atm-vcl record. The following parameters of the default atm-traf-descr profile should be modified to match your network: Parameter
Description
td_type
Traffic descriptor type. Values: atmNoClpNoScr (OID 1.3.6.1.2.1.37.1.1.2) No CLP and no sustained cell rate. atmClpTaggingNoScr (OID 1.3.6.1.2.1.37.1.1.4) CLP with tagging and no sustained cell rate. atmClpNoTaggingScr (OID 1.3.6.1.2.1.37.1.1.6) CLP with no tagging and sustained cell rate. atmClpTaggingScr (OID 1.3.6.1.2.1.37.1.1.7) CLP with tagging and sustained cell rate. atmClpTransparentNoScr (OID 1.3.6.1.2.1.37.1.1.9) CLP transparent with no sustained cell rate. atmClpTransparentScr (OID 1.3.6.1.2.1.37.1.1.10) CLP transparent with sustained cell rate. atmNoClpNoScrCdvt (OID 1.3.6.1.2.1.37.1.1.12) No CLP, no sustained cell rate, and cell delay variation tolerance. atmClpNoTaggingScrCdvt (OID 1.3.6.1.2.1.37.1.1.14) CLP with no tagging, sustained cell rate and cell delay variation tolerance. atmClpTaggingScrCdvt (OID 1.3.6.1.2.1.37.1.1.15) CLP with tagging, sustained cell rate, and cell delay variation tolerance.
td_param1
Peak Cell Rate (PCR), measured in cells per second. For CBR traffic, must match a value configured in the atm-vcl-param profile.
td_param2
Sustainable cell rate (SCR), measured in cells per second. For rt-VBR traffic, must match a value configured in the atm-vcl-param profile. PCR for atmClpTaggingNoScr traffic. CDVT for atmClpTransparentNoScr and atmNoClpNoScrCdvt traffic.
372
MALC Configuration Guide
Creating traffic descriptors
Parameter
Description
td_param3
Maximum burst size (MBS), measured in number of cells.
td_param4
Cell delay variation tolerance (CDVT), measured in 10ths of microseconds.
cac-divider
Enables oversubscription for an ATM VCL. During CAC calculations, the system divides the PCR (for CBR VCLs) or SCR (for nrt-VBR or rt-VBR VCLs) bandwidth by the value specified in the cac-divider. It then uses that value to determine if the VCL can be created. For example, to configure a 4:1 oversubscription, set cac-divider to 4. Default: 1
td_service_category
The ATM service category. Values: cbr Constant bit rate ubr - unspecified bit rate rtvbr - Real time variable bit rate nrtvbr Non-real time variable bit rate Default: ubr
td_frame_discard
Enables and disable early-packet-discard (EPD) and partial-packet-discard (PPD). This allows selective discarding of all cells in a frame if one cell is lost or discarded. Values: true Indicates that the network is requested to treat data for this connection, in the given direction, as frames (that is, AAL5 CPCS PDUs) rather than as individual cells. While the precise implementation is network-specific, this treatment may involve discarding entire frames during congestion, rather than a few cells from many frames. false This is the recommended setting for voice connections. Default: false
usage-parameter-control
Enables or disables policing on the traffic descriptor. Note that this must be set to true if the ATM service category is CBR. Values: true false Default: true
MALC Configuration Guide
373
Configuring ATM
Creating a traffic descriptor 1
List the atm-traf-descr records to see what is currently configured on the system: zSH> list atm-traf-descr 0 entries found.
2
Create a traffic descriptor by specifying a traffic descriptor type and the traffic parameters. For example:
zSH> new atm-traf-descr 100 Please provide the following: [q]uit. td_type: ------------- {atmNoClpNoScr}: enter traffic descriptor td_param1: ----------- {0}: enter PCR td_param2: ----------- {0}: enter PCR (for CLP=0 traffic) or SCR td_param3: ----------- {0}: enter MBS td_param4: ----------- {0}: enter CDVT td_param5: ----------- {0}: cac-divider: -------------> {1} td_service_category: - {ubr}: rtvbr | nrtvbr | ubr | cbr td_frame_discard: --------> {false} usage-parameter-control: -> {true} .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Note: Set the PCR to match the lowest speed in the cross connect.
Creating VCLs and VPLs VCLs are used for VC switching. VPLs are used for VP switching. The following table describes the supported parameters in the atm-vcl profile: Parameter
Description
vpi
The VPI for this VCL. This must match the remote end of the connection.
vci
The VCI for this VCL. This must match the remote end of the connection.
admin_status
Administrative status of the link. Values: up down Default: down
374
MALC Configuration Guide
Creating VCLs and VPLs
Parameter
Description
receive_traffic_descr_index
The index of the atm-traf-descr profile used for this VCL.
transmit_traffic_descr_index
The index of the atm-traf-descr profile used for this VCL.
vcc_aal_type
ATM adaption layer type. Values: aal5 for data other For cell relay connections. aal2 for voice Default: aal5
vcc_aal5_encaps_type
The type of data encapsulation used over the AAL5 Service Specific Convergence Sublayer (SSCS) layer. The definitions reference RFC 1483 Multiprotocol Encapsulation over ATM AAL5 and the ATM Forum LAN Emulation specification. Values: llcencapsulation Used for an LLC-encapsulated connection. other Used for a bridged connection.
fault-detection-type
Used to determine faults on the VCL. Values: disabled Fault detection is disabled. oamF5Loopback On POTS-based AAL2 connections, the unit sends an OAM F5 loopback if the CAS does not refresh after 10 seconds. If there is no response to the F5 loopback, the VCL is blocked and a trap is generated. On ISDN-based AAL2 connections, there is no CAS refresh; the unit sends an F5 loopback every 5 seconds. If there is no response to the F5 loopback, the VCL is blocked and a trap is generated. F5 loopbacks on AAL5 connections are not supported. Default: disabled
MALC Configuration Guide
375
Configuring ATM
The following table describes the supported parameters in the atm-vpl profile: Parameter
Description
atmVplAdminStatus
Administrative status of the VPL. Values: up down Default: down
atmVplReceiveTrafficDescrIndex
Specifies the ATM traffic descriptor which applies to the receive direction of this VPL. Currently this value must be set equal to the value used for the atmVplTransmitTrafficDescrIndex. Values: The index value of an existing atm-traf-descr.
atmVplTransmitTrafficDescrIndex
Specifies the ATM traffic descriptor which applies to the transmit direction of this VPL. Currently this value must be set equal to the value used for the atmVplReceiveTrafficDescrIndex. Values: The index value of an existing atm-traf-descr.
atmVplCastType
Type of connection. Values: p2p Point-to-point.
atmVplConnKind
The use of call control. Values: pvc
Creating VCLs (VC switching) Create two VCLs for each cross connection. Each atm-vcl record defines an endpoint for an ATM virtual cross connection (VCC). Note: For a cell relay connection, set the vcl_aal_type to other, which treats the connection endpoints as cell relay. The MALC will not perform any segmentation or reassembly (SAR) on the data stream. 1
The following example creates a VCL for a subscriber-side ADSL interface in shelf 1, slot 12, port 1, with a VPI of 0 and a VCI of 35: zSH> new atm-vcl 1-12-1-0-adsl/atm/0/35 Please provide the following: [q]uit.
376
MALC Configuration Guide
Creating VCLs and VPLs
vpi: -----------------------------> {0}: vci: -----------------------------> {0}:35 admin_status: --------------------> {up}:up receive_traffic_descr_index: -----> {0}:100 transmit_traffic_descr_index: ----> {0}:100 vcc_aal_type: --------------------> {aal5}:other vcc_aal5_cpcs_transmit_sdu_size: -> {9188}: vcc_aal5_cpcs_receive_sdu_size: --> {9188}: vcc_aal5_encaps_type: ------------> {llcencapsulation}: vcl_cast_type: -------------------> {p2p}: vcl_conn_kind: -------------------> {pvc}: fault-detection-type: ------------> {disabled} traffic-container-index: ---------> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record saved.
2
The following example creates a VCL for the Uplink card interface in shelf 1, slot 1, port 1, with a VPI of 0 and a VCI of 101: zSH> new atm-vcl uplink1/atm/0/101 Please provide the following: [q]uit. vpi: -----------------------------> {0}: vci: -----------------------------> {0}:101 admin_status: --------------------> {down}:up receive_traffic_descr_index: -----> {0}:100 transmit_traffic_descr_index: ----> {0}:100 vcc_aal_type: --------------------> {aal5}:other vcc_aal5_cpcs_transmit_sdu_size: -> {9188}: vcc_aal5_cpcs_receive_sdu_size: --> {9188}: vcc_aal5_encaps_type: ------------> {llcencapsulation}: vcl_cast_type: -------------------> {p2p}: vcl_conn_kind: -------------------> {pvc}: fault-detection-type: ------------> {disabled} traffic-container-index: ---------> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record saved.
Creating VPLs (VP switching) Before creating VPLs, verify that an atm-vpi record exists for the VP you want to switch. For details, see VPI/VCI ranges on page 366. Create two VPLs for each cross connection. Each atm-vpl record defines an endpoint for an ATM virtual cross connection (VCC). Note: For a cell relay connection, set the vcl_aal_type to other, which treats the connection endpoints as cell relay. The MALC will not perform any segmentation or reassembly (SAR) on the data stream.
MALC Configuration Guide
377
Configuring ATM
1
Create a VPL for the other end of the cross connect (in this example, an ADSL port in slot 3, using VPI 2): zSH> new atm-vpl 1-3-1-0-adsl/atm/2 interface-index/atm/VPI Please provide the following: [q]uit. atmVplAdminStatus: ---------------> {down}: up atmVplReceiveTrafficDescrIndex: --> {0}: 1 atmVplTransmitTrafficDescrIndex: -> {0}: 1 atmVplCastType: ------------------> {p2p}: atmVplConnKind: ------------------> {pvc}: atmVplPonTrafficContainerIndex: --> {0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
2
Create a VPL for one end of the cross connect (in this example, an Uplink card using VPI 3) zSH> new atm-vpl uplink1/atm/3 interface-index/atm/VPI Please provide the following: [q]uit. atmVplAdminStatus: ---------------> {down}: up atmVplReceiveTrafficDescrIndex: --> {0}: 1 atmVplTransmitTrafficDescrIndex: -> {0}: 1 atmVplCastType: ------------------> {p2p}: atmVplConnKind: ------------------> {pvc}: atmVplPonTrafficContainerIndex: --> {0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
3
Next, create the cross connect.
Creating cross connects To connect the two endpoints create a new atm-cc profile and specify an index value (The cc-index is any number you choose.) The atm-cc record uses the low-if-index and high-if-index values for VPI and VCI to bind VCC endpoints. The following parameters of the default atm-cc profile should be modified to match your network: Parameter
Description
cc-index
A unique value to identify this cross connect.
low-if-index
The index (in the form shelf-slot-port-subport-interface/atm or a user-defined string) of the ATM interface for this cross connect. The low-if-index is arbitrary, but by convention it indicates the ATM interface with a numerically lower ifIndex value than the other ATM interface identified in the same cross connect. The low-if-index and the high-if-index cannot be equal.
378
MALC Configuration Guide
Creating VCLs and VPLs
Parameter
Description
low-vpi
The VPI value associated with the interface specified in the low-if-index.
low-vci
The VCI value associated with the interface specified in the low-if-index. For VP switched connections, specify 0.
high-if-index
The index (in the form shelf-slot-port-subport-interface/atm or a user-defined string) of the ATM interface for this cross connect. The high-if-index is arbitrary, but by convention it indicates the ATM interface with a numerically higher ifIndex value than the other ATM interface identified in the same cross connect. The low-if-index and the high-if-index cannot be equal.
high-vpi
The VPI value associated with the interface specified in the high-if-index
high-vci
The VCI value associated with the interface specified in the high-if-index. For VP switched connections, specify 0.
admin-status
The desired administrative status of the cross connect. Values: up down Default: down
Creating cross connects To create a VC-switched crossconnect, use the crossconnect command. This command uses the following syntax: crossconnect add interface1/type1 [vc] vpi1/vci1 interface2/type2 [vc] vpi2/vci2 td_val | txtd txtd_value rxtd rxtd_val
The following example creates a VC switched cross connect between a DSL port and an OC-3c/STM1 port (the VCL were created above): zSH> crossconnect add 1-3-1-0-adsl/atm vc 1/35 uplink2/atm vc 1/101 100
The following example creates a VP switched cross connect between a DSL port and the Uplink port: zSH> new atm-cc 1 Please provide the cc-index: ------> low-if-index: --> low-vpi: -------> low-vci: -------> high-if-index: -> high-vpi: ------> high-vci: ------>
following: [q]uit. {0}: 1 {0/0/0/0/0}: 1-3-1-0-adsl/atm {0}: 2 {0}: leave at 0 for VP switching {0/0/0/0/0}: uplink2/atm {0}: 3 {0}: leave at 0 for VP switching
MALC Configuration Guide
379
Configuring ATM
admin-status: --> {down}: up .................... Save new record? [s]ave, [c]hange or [q]uit: s Record saved.
Note: A VCL or VPL can be used in only one cross connect.
Subtending Subtending allows you aggregate traffic from multiple MALC devices to single MALC device’s ATM upstream interface.
1
In a typical subtended configuration, VPLs from downstream devices are VP-switched to an upstream ATM device over a high-speed interface such as OC-3c/STM1. Figure 50: Example subtending configuration
VPL 1-3-1-0-ds1/atm/1 Device A
ATM
T1/E1 32 card
VPL uplink1/atm/1 Device C
VPL uplink1/atm/2
VPL 1-3-2-0-ds1/atm/2
Device B
Subtending example This example creates a subtended configuration from two downstream MALC devices to a single MALC. The downstream devices are connected to MALC T1/E1 ports and the traffic is VP switched to the Uplink interface (and then to the upstream ATM network). 1
Create a traffic descriptors for the downstream and upstream interfaces: Downstream: (this example uses a UBR connection with a PCR of 3661 CPS (T1 line speed)):
380
MALC Configuration Guide
Creating VCLs and VPLs
zSH> new atm-traf-descr 100 Please provide the following: [q]uit. td_type: -----------------> {atmNoClpNoScr}: td_param1: ---------------> {0}: 3661 td_param2: ---------------> {0}: td_param3: ---------------> {0}: td_param4: ---------------> {0}: td_param5: ---------------> {0}: cac-divider: -------------> {1}: td_service_category: -----> {ubr}: td_frame_discard: --------> {false}: usage-parameter-control: -> {true}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Upstream: (this example uses a UBR connection with a PCR of 28,303 CPS (line speed of 8 T1s)): zSH> new atm-traf-descr 200 Please provide the following: [q]uit. td_type: -----------------> {atmNoClpNoScr}: td_param1: ---------------> {0}: 28303 td_param2: ---------------> {0}: td_param3: ---------------> {0}: td_param4: ---------------> {0}: td_param5: ---------------> {0}: cac-divider: -------------> {1}: td_service_category: -----> {ubr}: td_frame_discard: --------> {false}: usage-parameter-control: -> {true}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
2
Create VPI profiles for each VPI you want to switch. These specify that the MALC should VPI switch all traffic using this VPI: a
For the Uplink interface: zSH> new atm-vpi uplink1/atm/1 interface-index/atm/VPI Please provide the following: [q]uit. zhoneAtmVpiMaxVci: ---> {0}: zhoneAtmVpiSwitched: -> {vc}: vp .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved. zSH> new atm-vpi uplink1/atm/2 interface-index/atm/VPI Please provide the following: [q]uit. zhoneAtmVpiMaxVci: ---> {0}: zhoneAtmVpiSwitched: -> {vc}: vp .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
MALC Configuration Guide
381
Configuring ATM
After the first atm-vpi record is saved, the system will automatically create atm-vpi records for all VPIs used in existing cross connects, if any. b
For the T1/E1 port connected to device A: zSH> new atm-vpi 1-3-1-0-ds1/atm/1 interface-index/atm/ VPI Please provide the following: [q]uit. zhoneAtmVpiMaxVci: ---> {0}: zhoneAtmVpiSwitched: -> {vc}: vp .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
c
For the T1/E1 port connected to device B: zSH> new atm-vpi 1-3-2-0-ds1/atm/2 interface-index/atm/ VPI Please provide the following: [q]uit. zhoneAtmVpiMaxVci: ---> {0}: zhoneAtmVpiSwitched: -> {vc}: vp .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
d
After the system has finished creating the atm-vpi records, reboot the card: Note: Rebooting the active Uplink card causes the system to reboot (for a non-redundant system), or switchover to the standby Uplink card (for a redundant system). Uplink card: zSH> slotreboot 1
T1/E1 32 card: zSH> slotreboot 3
e 3
If your system is redundant, configure a VPI profile on the second Uplink card.
Create VPLs to each downstream MALC: Device A: zSH> new atm-vpl 1-3-1-0-ds1/atm/1 interface-index/atm/VPI Please provide the following: [q]uit. atmVplAdminStatus: ---------------> {down}: up atmVplReceiveTrafficDescrIndex: --> {0}: 100 atmVplTransmitTrafficDescrIndex: -> {0}: 100 atmVplCastType: ------------------> {p2p}: atmVplConnKind: ------------------> {pvc}: atmVplPonTrafficContainerIndex:--> {0} ....................
382
MALC Configuration Guide
Creating VCLs and VPLs
Save new record? [s]ave, [c]hange or [q]uit: New record saved.
s
Device B: zSH> new atm-vpl 1-3-2-0-ds1/atm/2 interface-index/atm/VPI Please provide the following: [q]uit. atmVplAdminStatus: ---------------> {down}: up atmVplReceiveTrafficDescrIndex: --> {0}: 100 atmVplTransmitTrafficDescrIndex: -> {0}: 100 atmVplCastType: ------------------> {p2p}: atmVplConnKind: ------------------> {pvc}: atmVplPonTrafficContainerIndex:--> {0} .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
4
Create the VPLs for device C’s Uplink interface: For VPI 1 (device A): zSH> new atm-vpl uplink1/atm/1 interface-index/atm/VPI Please provide the following: [q]uit. atmVplAdminStatus: ---------------> {down}: up atmVplReceiveTrafficDescrIndex: --> {0}: 200 atmVplTransmitTrafficDescrIndex: -> {0}: 200 atmVplCastType: ------------------> {p2p}: atmVplConnKind: ------------------> {pvc}: atmVplPonTrafficContainerIndex:--> {0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
For VPI 2 (device B): zSH> new atm-vpl uplink1/atm/2 interface-index/atm/VPI Please provide the following: [q]uit. atmVplAdminStatus: ---------------> {down}: up atmVplReceiveTrafficDescrIndex: --> {0}: 200 atmVplTransmitTrafficDescrIndex: -> {0}: 200 atmVplCastType: ------------------> {p2p}: atmVplConnKind: ------------------> {pvc}: atmVplPonTrafficContainerIndex:--> {0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
5
Create cross connects between the two downstream interfaces and the Uplink interface: From Device A to the Uplink VPL: zSH> new atm-cc 1 Please provide the following: [q]uit. cc-index: ------> {0}: 1 low-if-index: --> {0/0/0/0/0}: atm-vcl 1-3-1-0/atm
MALC Configuration Guide
383
Configuring ATM
low-vpi: -------> {0}: 1 low-vci: -------> {0}: leave at 0 for VP switching high-if-index: -> {0/0/0/0/0}: uplink1/atm high-vpi: ------> {0}: 1 high-vci: ------> {0}: leave at 0 for VP switching admin-status: --> {down}: up .................... Save new record? [s]ave, [c]hange or [q]uit: s Record saved.
From Device B to the Uplink VPL: zSH> new atm-cc 2 Please provide the following: [q]uit. cc-index: ------> {0}: 2 low-if-index: --> {0/0/0/0/0}: atm-vcl 1-3-2-0/atm low-vpi: -------> {0}: 2 low-vci: -------> {0}: leave at 0 for VP switching high-if-index: -> {0/0/0/0/0}: uplink1/atm high-vpi: ------> {0}: 2 high-vci: ------> {0}: leave at 0 for VP switching admin-status: --> {down}: up .................... Save new record? [s]ave, [c]hange or [q]uit: s Record saved.
384
MALC Configuration Guide
7
CONFIGURING VOICE This chapter explains how to configure voice connections between subscriber endpoints and remote gateways and how to customize the voice parameters when required. It includes the following sections:
•
Overview, page 385
•
Updating system settings, page 386
•
Creating voice connections, page 387
•
Additional VoIP features, page 403
•
Configuring CES connections, page 417
•
Additional voice features, page 434
•
Emergency StandAlone (ESA) SIP and TDM support, page 440
•
Configuring T.38 fax service, page 448
Overview The following types of voice connections between subscriber and remote endpoints are supported: Note: The voice gateway card requires MALC software version 1.11.1 or higher on the Uplink cards.
Subscriber endpoints
Gateway endpoints
MALC Uplinks
POTS
AAL2
All
DS1
TDM, Gigabit Ethernet
GR303
TDM, Gigabit Ethernet
VoIP
All
V5.2
TDM, Gigabit Ethernet
AAL2
All
V5.2
TDM, Gigabit Ethernet
ISDN
MALC Configuration Guide
385
Configuring Voice
Subscriber endpoints
Gateway endpoints
MALC Uplinks
VoIP
GR303
All TDM IP (voice gateway card required)
V5.2
All TDM IP (voice gateway card required)
GR303
All TDM ATM (voice gateway card required)
V5.2
All TDM ATM (voice gateway card required)
V5.2
All TDM ATM (voice gateway card required)
AAL2
AAL2 ELCP
Note: This chapter assumes you have configured the required TDM/ ATM Uplink, POTS, and ISDN physical interfaces as explained in the MALC Hardware Installation Guide.
Updating system settings Prior to configuring a voice connection, ensure the system settings are configured to support desired type of voice connection. The system profile contains settings that configure country-specific settings for voice calls and determines whether the system will reject incoming calls if there isn’t enough bandwidth available.
Setting a-law or mu-law and DSP settings Note: The MALC supports A-Law or Mu-Law encoding, but they cannot both be used simultaneously in a single chassis. Modifying the countryregion parameter of the system profile ensures that the ring frequency and voice encoding (A-law/Mu-law) are correctly set. The A-law and Mu-law settings can also be set using the optional alaw and mulaw parameters in the voice add command. See Creating voice connections on page 387. The show system command displays the available system profile settings. The voice add command does not allow the alaw/mulaw argument with POTS voice connections. If it is entered for a POTS voice connection, it is ignored. However, the alaw/mulaw argument can be used for the AAL2 remote end of a voice connection. For VoIP calls, if codec argument is not specified, the country code settings determines the default preferred-codec as g711mu or g711a.
386
MALC Configuration Guide
Creating voice connections
Creating voice connections Voice connections provide voice signaling connections between subscriber endpoints and voice gateway endpoints. The voice command can be used to add, delete, and show voice connection settings. When a voice connection is added or deleted, the voice command creates or deletes the related profiles for both the subscriber and remote endpoints. Refer to the CLI Reference Guide for a complete description of the command options and syntax. The voice command uses the following syntax voice add subscriber-info remote-info [sub descr] [enable]
This command automatically creates all the subscriber and ATM profiles required by the voice connection. For POTS and AAL2 voice connections, this command also optionally sets the PCM-encoding parameter to the specified encoding method and enables the voice connection. Note that in some cases the profiles with voice configuration parameters may have to be updated to customize the voice configuration. The voice show command can be used to display voice connection status for all calls or only voice connection data for a specific endpoint. This section describes the procedures for configuring the following types of gateway voice connections:
•
DS1 voice gateway connections on page 387
•
Voice over IP (VoIP) connections on page 391
•
DS1 to POTS connections on page 416
DS1 voice gateway connections DS1 voice connections use a direct channel map between the subscriber signals and the voice uplink. Note: DS1 voice connections are only supported with line type D4.
This section explains how to configure the following types of connections:
•
Configuring POTS to GR303 connections on page 389
•
ISDN to V5.2 connections on page 388
•
Configuring POTS to V.52 connections on page 390
MALC Configuration Guide
387
Configuring Voice
ISDN to V5.2 connections For ISDN-to-V5.2 configurations, the MALC interconnects ISDN terminal equipment directly to V.52 switches. The V5.2 IG must already exist before the voice connection can be configured. The elcp-trap parameter is available in the aal2-vcl profile. This parameter allows operators to turn ELCP traps on/off for particular AAL2 VCLs. All users on the provisioned AAL2 VCL will have their ELCP trap alerts turned either on or off. 1
Use the voice command to add the ISDN to V5.2 connection. This example uses the 1-3-1-0/isdnu physical interface and sets the required fields in the atm-vcl, aal2-vcl-profile, and the aal2-cid-profile. zSH> voice add isdn 1-3-1-0/isdnu v52 1/1 cpath 5 enable Created subscriber-voice 1/13/25 Created subscriber-voice-isdn 49 Created v52-user-port 1/1/3 Created subscriber-voice-v52 50 Created subscriber-voice 1/13/26 Created subscriber-voice-isdn 51 Created subscriber-voice-v52 52 Created subscriber-voice 1/13/27 Created subscriber-voice-isdn 53 Created subscriber-voice-v52 54
2
View the voice connection.
zSH> voice show 1-3-1-0/isdnu Subscriber end-point Remote end-point --------------------------- --------------------------1-3-1-0/isdnu V52 1/1 1-3-1-0/isdnu V52 1/1 1-3-1-0/isdnu V52 1/1
Voice Prof Id -------------3/32/13011 3/32/13012 3/32/13013
STA --ENA ENA ENA
Configuring POTS to DS1 connections POTS to DS1 voice connections. 1
Use the voice command to add the POTS to DS1 connection. The voice ring command can be used to verify a POTS voice connection without placing a call. The voice status command can be used to display runtime voice port status and to verify the phone’s ring status if the ringing cannot be heard.
zSH> voice add pots 1-5-24-0/voicefxs ds1 1-1-9-0/ds1 ds0 24 Created subscriber-voice 1/21/25 Created subscriber-voice-pots 83 Created subscriber-voice-ds1 84
388
MALC Configuration Guide
Creating voice connections
2
View the voice connections:
zSH> voice show Subscriber end-point Remote end-point Voice Prof Id STA ------------------------------ ------------------------------ -------------- --1-5-24-0/voicefxs 1-1-9-0/ds1 DS0 24 1/21/25 ENA
Configuring POTS to GR303 connections For GR303 voice connections, the GR303 interface with IG must already exist. For POTS-to-GR303 configurations, the MALC interconnects POTS equipment directly to GR-303 switches. This example creates a POTS to GR303 subscriber profile with IG 1 and CRV 2. It also sets the administrative status interface to up. The voice ring command can be used to verify a POTS voice connection without placing a call. The voice status command can be used to display runtime voice port status, verify the phone’s ring status if the ringing cannot be heard, and display interface group status. The voice add command supports an gnd option for POTS endpoints to set the groundstart option for voice connections using the POTS ULCS card with pots subtype. If the farend of the voice connection is GR303, this option also sets the groundstart setting in the gr303-ig-crv profile. If the farend of the voice connection is AAL2, this option also sets the groundstart setting in the aal2-vcl profile. When the gnd option is not used for the Global POTS or ULCS cards with pots subtype, the groundstart setting in the analog-fxs-cfg-profile is used. The default is loopstart. 1
Use the voice command to add the POTS to GR303 connection. zSH> voice add pots 1-8-1-0/voicefxs gr303 1/2 enable Created subscriber 1/13 Created subscriber-voice 1/13/1 Created subscriber-voice-pots 20 Created gr303-ig-crv 1/2 Created subscriber-voice-gr303 21 zSH> voice add pots 1-5-2-0/voicefxs Created subscriber-voice 1/13/21 Created subscriber-voice-pots 41 Created gr303-ig-crv 1/4 Created subscriber-voice-gr303 42
gr303 1/4
zSH> voice add pots 1-5-3-0/voicefxs gnd aal2 uplinkima3/atm vc 0/36 td 1/1 cid 16 Created subscriber-voice 1/34/2 Created subscriber-voice-pots 45 Created atm-vcl uplinkima3/atm/0/36 Created aal2-cid-profile 43/0/36/16 Created subscriber-voice-aal2 46
MALC Configuration Guide
389
Configuring Voice
2
View the voice connection:
zSH> voice show 1-8-1-0/voicefxs Subscriber end-point Remote end-point Voice Prof Id STA ------------------------------ ------------------------------ -------------- --1-8-1-0/voicefxs GR303 Zhone/2 1/13/1 ENA Total number of voice connections : 1
Configuring POTS to V.52 connections The MALC interconnects POTS equipment directly to V5.2 switches. For POTS subscriber to V5.2 voice gateway connections, the V5.2 IG must exist before the voice connection can be configured. The voice ring command can be used to verify a POTS voice connection without placing a call. The voice status command can be used to display runtime voice port status, verify the phone’s ring status if the ringing cannot be heard, and display interface group status. 1
Use the voice command to add the POTS to V5.2 connection. zSH> voice add pots 1-8-1-0/voicefxs v52 1/28 type pots Created subscriber 1/13 Created subscriber-voice 1/13/1 Created subscriber-voice-pots 10013 Created v52-user-port 1/28/2 Created subscriber-voice-v52 10014
2
View the voice connection.
zSH> voice show Subscriber end-point Remote end-point Voice Prof Id STA ------------------------------ ------------------------------ -------------- --1-8-1-0/voicefxs V52 1/28 1/13/1 ENA Total number of voice connections : 1
390
MALC Configuration Guide
Creating voice connections
Voice over IP (VoIP) connections The following procedures describe how to configure POTS to VoIP subscriber voice connections. POTS subscribers can be connected to VoIP remote endpoints. For VoIP voice connections, several optional arguments such as codec are supported in the remote information of the voice add command. Supported codecs are:
•
g711mu (the default setting)
•
g711a
•
g726
•
g729a
•
g723
The MALC G.729A VoIP compression provides an optional fallback mode to G.711. The parameter for the fallback mode is g711-fallback and is set in the subscriber-voice-voip profile.The default settings for the subscriber-voice-voip profile are:
•
preferred-codec: g711mu
•
g711-fallback: true
•
frames-per-packet: 4
•
g726-byte-order: bigendian
•
voip-password: password
The following VoIP remote information is available: voip IpIfname dn dir-num [name username] [pw password] [plar dest-ipaddr] [reg serverId] [codec pref-codec] Note: For MGCP and Megaco calls, the MALC ignores the preferred-codec setting and selects the codec from a list provided by the MGCP server or media gateway controller. Before creating VoIP connections, ensure that the IP interface, VoIP system, and VoIP server settings are configured properly. This section contains the following procedures:
•
Configuring VoIP interface on page 392
•
Configuring SIP and SIP PLAR servers on page 393
•
Configuring MGCP on page 396
•
Configuring MEGACO (H.248) on page 399
•
Creating POTS to VoIP connections on page 402
MALC Configuration Guide
391
Configuring Voice
Note: Communication with SIP phones is only possible over one interface of the MALC. Communication with SIP phones that are in the same network as other interfaces on the MALC is not supported.
Configuring VoIP interface 1
Configure an IP interface for VoIP. For example: zSH> new ip-interface-record 1-1-1-0/ip Please provide the following: [q]uit. vpi: ---------------> {0}: vci: ---------------> {0}: rdindex: -----------> {1}: dhcp: --------------> {none}: ** read-only ** addr: --------------> {0.0.0.0}: 192.168.87.2 netmask: -----------> {0.0.0.0}: 255.255.255.0 bcastaddr: ---------> {0.0.0.0}: 192.168.87.255 destaddr: ----------> {0.0.0.0}: farendaddr: --------> {0.0.0.0}: mru: ---------------> {1500}: reasmmaxsize: ------> {0}: ingressfiltername: -> {}: egressfiltername: --> {}: pointtopoint: ------> {no}: mcastenabled: ------> {yes}: ipfwdenabled: ------> {yes}: mcastfwdenabled: ---> {yes}: natenabled: --------> {no}: bcastenabled: ------> {yes}: ingressfilterid: ---> {0}: egressfilterid: ----> {0}: ipaddrdynamic: -----> {static}: dhcpserverenable: --> {false}: subnetgroup: -------> {0}: unnumberedindex: ---> {0}: mcastcontrollist: --> {}: vlanid: ------------> {0}: maxVideoStreams: ---> {0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Record updated.
2
Configure a system IP address: zSH> update system 0 Please provide the following: [q]uit. syscontact: -----------> {Zhone Technologies 7001 Oakport Street Oakland CA 94621}: sysname: --------------> {Zhone Malc}}: syslocation: ----------> {}: enableauthtraps: ------> {disabled}: setserialno: ----------> {0}: zmsexists: ------------> {false}:
392
MALC Configuration Guide
Creating voice connections
zmsconnectionstatus: --> {inactive}: zmsipaddress: ---------> {0.0.0.0}: configsyncexists: -----> {false}: configsyncoverflow: ---> {false}: configsyncpriority: ---> {high}: configsyncaction: -----> {noaction}: configsyncfilename: ---> {}: configsyncstatus: -----> {syncinitializing}: configsyncuser: -------> {}: configsyncpasswd: -----> {** private **}: ** read-only ** numshelves: -----------> {1}: shelvesarray: ---------> {}: numcards: -------------> {1}: ipaddress: ------------> {0.0.0.0}: 192.168.7.45 alternateipaddress: ---> {0.0.0.0}: countryregion: --------> {us}: primaryclocksource: ---> {0/0/0/0/0}: ringsource: -----------> {internalringsourcelabel}: revertiveclocksource: -> {true}: voicebandwidthcheck: --> {false}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
SIP server configuration Configuring SIP and SIP PLAR servers The VOIP protocol setting can be configured as either Media Gateway Control Protocol (MGCP) or Session Initiation Protocol (SIP) signaling. By default, the MALC uses SIP signaling. Note: Redundant SIP server support is implemented through DNS lookups for only BroadSoft software configurations. SIP signalling identifies callers and callees by SIP addresses and allows signals to be redirected to proxy servers. The MALC supports single softswitch configurations. Note: If all SIP calls do not register after a system reboot, increase the server-max-timer value in the voice-system profile to a higher value, for example 180 seconds. The default value is 20 seconds. To configure SIP: 1
Create the voip-server-entry profiles to specify the VOIP server groups and IDs. The voip-server-entry profiles is specified with server group and server ID numbers. This example configures a SIP server in server group 1 with server ID 1.
MALC Configuration Guide
393
Configuring Voice
zSH> new voip-server-entry 1/1 zhoneVoipServerAddrType: ----------> {ipv4}: zhoneVoipServerAddr: --------------> {0.0.0.0}: zhoneVoipServerUdpPortNumber: -----> {5060}: zhoneVoipServerId: ----------------> {generic}: protocol: -------------------------> {sip}: sendCallProceedingTone: -----------> {false}: rtcpEnabled: ----------------------> {false}: rtcpPacketInterval: ---------------> {5000}: interdigitTimeOut: ----------------> {10}: ipTos: ----------------------------> {0}: systemDomainName: -----------------> {}: expires-invite-value: -------------> {3600}: expires-register-value: -----------> {3600}: expires-header-method: ------------> {register}: session-timer: --------------------> {off}: session-expiration: ---------------> {180}: session-min-session-expiration: ---> {180}: session-caller-request-timer: -----> {no}: session-callee-request-timer: -----> {no}: session-caller-specify-refresher: -> {omit}: session-callee-specify-refresher: -> {uac}: dtmf-mode: ------------------------> {rfc2833}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created.
SIP PLAR voice connections require the entry of the profile voip-server-entry 255/255. This entry serves as the default server entry. The zhoneVoipServerAddr must be 0.0.0.0. zSH> new voip-server-entry 255/255 zhoneVoipServerAddrType: ----------> zhoneVoipServerAddr: --------------> zhoneVoipServerUdpPortNumber: -----> zhoneVoipServerId: ----------------> protocol: -------------------------> sendCallProceedingTone: -----------> rtcpEnabled: ----------------------> rtcpPacketInterval: ---------------> interdigitTimeOut: ----------------> ipTos: ----------------------------> systemDomainName: -----------------> expires-invite-value: -------------> expires-register-value: -----------> expires-header-method: ------------> session-timer: --------------------> session-expiration: ---------------> session-min-session-expiration: ---> session-caller-request-timer: -----> session-callee-request-timer: -----> session-caller-specify-refresher: -> session-callee-specify-refresher: -> dtmf-mode: ------------------------>
394
MALC Configuration Guide
{ipv4}: {0.0.0.0}: {5060}: {generic}: {sip}: {false}: {false}: {5000}: {10}: {0}: {}: {3600}: {3600}: {register}: {off}: {180}: {180}: {no}: {no}: {omit}: {uac}: {rfc2833}:
Creating voice connections
.................... Save new record? [s]ave, [c]hange or [q]uit: s Record created.
Note: The voip-system profile is no longer used.
2
Verify that the voip-server-entry profile configuration:
zSH> get voip-server-entry 255/255 Please provide the following: [q]uit. zhoneVoipServerAddrType: ----------> zhoneVoipServerAddr: --------------> zhoneVoipServerUdpPortNumber: -----> zhoneVoipServerId: ----------------> protocol: -------------------------> sendCallProceedingTone: -----------> rtcpEnabled: ----------------------> rtcpPacketInterval: ---------------> interdigitTimeOut: ----------------> ipTos: ----------------------------> systemDomainName: -----------------> expires-invite-value: -------------> expires-register-value: -----------> expires-header-method: ------------> session-timer: --------------------> session-expiration: ---------------> session-min-session-expiration: ---> session-caller-request-timer: -----> session-callee-request-timer: -----> session-caller-specify-refresher: -> session-callee-specify-refresher: -> dtmf-mode: ------------------------> zSH>
{ipv4}: {0.0.0.0}: {5060}: {generic}: {sip}: {false}: {false}: {5000}: {10}: {0}: {}: {3600}: {3600}: {register}: {off}: {180}: {180}: {no}: {no}: {omit}: {uac}: {rfc2833}:
Table 29 specifies the IP TOS settings used in the voip-server-entry profile based on IP Precedence bits. For IP TOS details, see TOS/COS processing on page 212. Table 29: IP TOS settings and IP Precedence bits Precedence Bits
TOS value
0 (Routine)
0
1 (Priority)
32
2 (Immediate)
64
3 (Flash)
96
4 (Flash override)
128
5 (CRITIC/ECP.)
160
MALC Configuration Guide
395
Configuring Voice
Table 29: IP TOS settings and IP Precedence bits Precedence Bits
TOS value
6 (Internetwork control)
192
7 (Network control)
224
3
Create a SIP dialplan for the SIP server. In each dialplan, specify the desired call parameters and use the voip-server-entry parameter to identify the server group for which the dialplan is used. This example references server group 1. zSH> new sip-dialplan 1 Please provide the following: [q]uit. match-string: ----------------> {}: xT sip-ip-address: --------------> {0.0.0.0}: 192.16.88.199 destination-name: ------------> {}: number-of-digits: ------------> {0}: 31 prefix-strip: ----------------> {0}: prefix-add: ------------------> {}: dialplan-type: ---------------> {normal}: voip-server-entry-index: -----> {0}: 1 override-interdigit-timeout:--> {0}: 3 .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created.
MGCP configuration Configuring MGCP The protocol setting can be configured as either Media Gateway Control Protocol (MGCP), Megaco (H.248), or Session Initiation Protocol (SIP) signaling. By default, the MALC uses SIP signaling. For H.248 procedures, see Configuring MEGACO (H.248) on page 399. MGCP signalling establishes call control elements or call agents to handle call control. MGCP devices execute the commands sent by the call agents. The MALC supports the voice message waiting indicator (VMWI) for MGCP connections. The MALC supports two MGCP servers per VoIP system. In order to support multiple MGCP servers, the servers must be configured as redundant MGCP servers with redundant peer support enabled. During the MALC system boot up, the MALC determines which redundant MGCP server to use. Then, during operations the MALC sends data to both the primary and the standy MGCP servers so that both MGCP servers are properly configured should a switch-over occur. To support multiple MGCP servers, create a voip-server-entry profile with a server group and server ID for each MGCP server.The first number in the
396
MALC Configuration Guide
Creating voice connections
ifIndex is for server group id and the second number is for the server ID. For example, 1/2 means server group 1 and server ID 2. The voip-server-entry profiles must use the same server group. Note: Redundant MGCP softswitch configuration for Metaswitch ESA is configured by creating voip-server-entry profiles for each softswitch This example creates voip-server-entry profiles for two MGCP servers using server group 1 and server IDs 1 and 2. Note: The MGCP max call limiter is set at 288 calls. When the maximum number of allowable active calls is reach, the outgoing caller hears a congestion tone. For the incoming call, the phone does not ring. To change the setting to MGCP: 1
Create the voip-server-entry profiles to enable MGCP:
zSH> new voip-server-entry 1/1 Please provide the following: [q]uit. zhoneVoipServerAddrType: ----------> {ipv4}: zhoneVoipServerAddr: --------------> {}: 172.16.60.1 zhoneVoipServerUdpPortNumber: -----> {5060}: 2727 zhoneVoipServerId: ----------------> {generic}: metaswitch protocol: -------------------------> {sip}: mgcp sendCallProceedingTone: -----------> {false}: rtcpEnabled: ----------------------> {false}: rtcpPacketInterval: ---------------> {5000}: interdigitTimeOut: ----------------> {10}: ipTos: ----------------------------> {0}: systemDomainName: -----------------> {}: expires-invite-value: -------------> {3600} expires-register-value: -----------> {3600} expires-header-method: ------------> {register} session-expiration: ---------------> {80} session-min-SE: -------------------> {180} session-caller-request-timer: -----> {no} session-callee-request-timer: -----> {no} session-caller-specify-refresher: -> {omit} session-callee-specify-refresher: -> {uac} dtmf-mode:------------------------> (rfc2833) .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created. zSH> new voip-server-entry 1/2 Please provide the following: [q]uit. zhoneVoipServerAddrType: --------> {ipv4}: zhoneVoipServerAddr: ------------> {}: 172.16.60.3 zhoneVoipServerUdpPortNumber: ---> {5060}: 2727 zhoneVoipServerId: --------------> {generic}: metaswitch
MALC Configuration Guide
397
Configuring Voice
protocol: -------------------------> {sip}: mgcp sendCallProceedingTone: -----------> {false}: rtcpEnabled: ----------------------> {false}: rtcpPacketInterval: ---------------> {5000}: interdigitTimeOut: ----------------> {10}: ipTos: ----------------------------> {0}: systemDomainName: -----------------> {}: expires-invite-value: -------------> {3600} expires-register-value: -----------> {3600} expires-header-method: ------------> {register} session-expiration: ---------------> {80} session-min-SE: -------------------> {180} session-caller-request-timer: -----> {no} session-callee-request-timer: -----> {no} session-caller-specify-refresher: -> {omit} session-callee-specify-refresher: -> {uac} dtmf-mode:------------------------> (rfc2833) .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created.
2
The system will automatically reboot if the voice protocol is changed. After the reboot, verify that the voip-server-entry profile is configured for MGCP:
zSH> get voip-server-entry 1/1 Please provide the following: [q]uit. zhoneVoipServerAddrType: ----------> {ipv4}: zhoneVoipServerAddr: --------------> {172.16.60.1}: zhoneVoipServerUdpPortNumber: -----> {2472}: zhoneVoipServerId: ----------------> {tekelec-t6000}: protocol: -------------------------> {mgcp}: sendCallProceedingTone: -----------> {false}: rtcpEnabled: ----------------------> {false}: rtcpPacketInterval: ---------------> {5000}: interdigitTimeOut: ----------------> {10}: ipTos: ----------------------------> {0}: systemDomainName: -----------------> {}: expires-invite-value: -------------> {3600} expires-register-value: -----------> {3600} expires-header-method: ------------> {register} session-expiration: ---------------> {0} session-min-SE: -------------------> {-606348325} session-caller-request-timer: -----> {no} session-callee-request-timer: -----> {no} session-caller-specify-refresher: -> {omit} session-callee-specify-refresher: -> {uac} omitsession-callee-specify-refresher:-> (uac) dtmf-mode:------------------------> (inband)
398
MALC Configuration Guide
Creating voice connections
Configuring MEGACO (H.248) The protocol setting can be configured as either Media Gateway Control Protocol (MGCP), MEGACO (H2.48), or Session Initiation Protocol (SIP) signaling. By default, the MALC uses SIP signaling. The MEGACO protocol is used between elements of a physically decomposed multimedia gateway. The distributed multimedia gateway sub-components create a general framework used for gateways, multipoint control units and interactive voice response units (IVRs). Redundant Megaco servers are supported. The MALC supports two VoIP servers per VoIP system. In order to support multiple VoIP servers, the servers must be configured as redundant VoIP servers with redundant peer support enabled. During the MALC system boot up, the MALC determines which redundant VoIP server to use. Then, during operations the MALC sends data to both the primary and the standy VoIP servers so that both servers are properly configured should a switch-over occur. To support multiple VoIP servers, create a voip-server-entry profile with a server group and server ID for each server.The first number in the ifIndex is for server group id and the second number is for the server ID. For example, 1/2 means server group 1 and server ID 2. The voip-server-entry profiles must use the same server group. This example creates voip-server-entry profiles for two VoIP servers using server group 1 and server IDs 1 and 2. To change the setting to MEGACO: 1
Create the voip-server-entry profiles to enable Megaco:
zSH> new voip-server-entry 1/1 Please provide the following: [q]uit. zhoneVoipServerAddrType: ----------> zhoneVoipServerAddr: --------------> zhoneVoipServerUdpPortNumber: -----> zhoneVoipServerId: ----------------> protocol: -------------------------> sendCallProceedingTone: -----------> rtcpEnabled: ----------------------> rtcpPacketInterval: ---------------> interdigitTimeOut: ----------------> ipTos: ----------------------------> systemDomainName: -----------------> expires-invite-value: -------------> expires-register-value: -----------> expires-header-method: ------------> session-expiration: ---------------> session-min-SE: -------------------> session-caller-request-timer: -----> session-callee-request-timer: -----> session-caller-specify-refresher: -> session-callee-specify-refresher: ->
{ipv4}: {}: 172.16.60.1 {5060}: 2944 {generic}: {sip}: megaco {false}: {false}: {5000}: {10}: {0}: {}: {3600} {3600} {register} {0} 180 {-606348325} 180 {no} {no} {omit} {uac}
MALC Configuration Guide
399
Configuring Voice
omitsession-callee-specify-refresher:-> (uac) dtmf-mode:------------------------> (inband) rfc2833 .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created. zSH> new voip-server-entry 1/2 Please provide the following: [q]uit. zhoneVoipServerAddrType: --------> {ipv4}: zhoneVoipServerAddr: ------------> {}: 172.16.60.3 zhoneVoipServerUdpPortNumber: ---> {5060}: 2944 zhoneVoipServerId: --------------> {generic}: protocol: -------------------------> {sip}: megaco sendCallProceedingTone: -----------> {false}: rtcpEnabled: ----------------------> {false}: rtcpPacketInterval: ---------------> {5000}: interdigitTimeOut: ----------------> {10}: ipTos: ----------------------------> {0}: systemDomainName: -----------------> {}: expires-invite-value: -------------> {3600} expires-register-value: -----------> {3600} expires-header-method: ------------> {register} session-expiration: ---------------> {0} 180 session-min-SE: -------------------> {-606348325} 180 session-caller-request-timer: -----> {no} session-callee-request-timer: -----> {no} session-caller-specify-refresher: -> {omit} session-callee-specify-refresher: -> {uac} omitsession-callee-specify-refresher:-> (uac) dtmf-mode:------------------------> (inband) rfc2833 .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created.
2
The system will automatically reboot if the voice protocol is changed. After the reboot, verify that the voip-server-entry profile is configured for MEGACO:
zSH> get voip-server-entry 1/1 Please provide the following: [q]uit. zhoneVoipServerAddrType: ----------> zhoneVoipServerAddr: --------------> zhoneVoipServerUdpPortNumber: -----> zhoneVoipServerId: ----------------> protocol: -------------------------> sendCallProceedingTone: -----------> rtcpEnabled: ----------------------> rtcpPacketInterval: ---------------> interdigitTimeOut: ----------------> ipTos: ----------------------------> systemDomainName: -----------------> expires-invite-value: -------------> expires-register-value: -----------> expires-header-method: ------------>
400
MALC Configuration Guide
{ipv4}: {172.16.60.1}: {2944}: {generic}: {megaco}: {false}: {false}: {5000}: {10}: {0}: {}: {3600} {3600} {register}
Creating voice connections
session-expiration: ---------------> {180} session-min-SE: -------------------> {180} session-caller-request-timer: -----> {no} session-callee-request-timer: -----> {no} session-caller-specify-refresher: -> {omit} session-callee-specify-refresher: -> {uac} omitsession-callee-specify-refresher:-> (uac) dtmf-mode:------------------------> (rfc2833)
3
Set the keep alive timer for VoIP servers in the voice-system profile. The server-max-timer specifies the period between ServiceChange request messages. The keep alive timer specifies how often the MALC expects keep alive messages from the Gateway Controller. If the MALC does not receive a keep alive message from the Gateway Controller in this interval, it sends an empty NTFY message to the controller. This should cause the controller to send a response. If the MALC still does not receive a response to the NTFY message in a period equal to 4 times the keep-alive-timer, it will send a ServiceChange message to the Gateway Controller at an interval equal to the keep-alive-timer. zSh> update voice-system 0 Please provide the following: [q]uit. hookflash-min-timer: -------> {100}: hookflash-max-timer: -------> {1550}: partial-dial-timeout: ------> {16}: critical-dial-timeout: -----> {4}: busy-tone-timeout: ---------> {30}: dial-tone-timeout: ---------> {16}: msg-wait-tone-timeout: -----> {16}: offhook-warn-tone-timeout: -> {0}: ringing-timeout: -----------> {180}: ringback-timeout: ----------> {180}: reorder-tone-timeout: ------> {30}: stutter-tone-timeout: ------> {16}: server-max-timer: ----------> {20}: config-max1: ---------------> {5}: config-max2: ---------------> {7}: max1-enable: ---------------> {true}: max2-enable: ---------------> {true}: max-waiting-delay: ---------> {600}: disconnection-wait-timer: --> {15}: disconnection-min-timer: ---> {15}: disconnection-max-timer: ---> {600}: max-retransmit-timer: ------> {4}: init-retransmit-timer: -----> {200}: keep-alive-timer: ----------> {60}: no-response-timer: ---------> {30}: call-wait-max-repeat: ------> {2}: call-wait-delay: -----------> {10}: pulse-inter-digit-timer: ---> {100}: min-make-pulse-width: ------> {25}:
MALC Configuration Guide
401
Configuring Voice
max-make-pulse-width: ------> min-break-pulse-width: -----> max-break-pulse-width: -----> server-max-timer: ----------> keep-alive-timer: ----------> .................... Save changes? [s]ave, [c]hange Record updated.
{55}: {45}: {75}: {20} {60} 90 or [q]uit: s
Creating POTS to VoIP connections This example creates a POTS to VoIP subscriber. 1
Use the voice command to add the POTS to VoIP connection. This examples creates a connection with a directory number 510-522-0401 and the name smith. The VoIP endpoint user name is case sensitive and must match the voice switch requirements, for example AAL/1 for MGCP with the Tekelec T6000 or TP/0001 for Megaco with Nortel CS2K. Note: For MGCP and Megaco calls, the MALC ignores the preferred-codec setting and selects the codec from a list provided by the MGCP server or media gateway controller.
zSH> voice add pots 1-3-1-0/voicefxs voip ethernet3-100/ip DN 5105220401 name smith Created subscriber-voice 1/2/1 Created subscriber-voice-pots 1004 Created subscriber-voice-voip 1005
2
View the voice connection.
zSH> voice show Subscriber end-point Remote end-point Voice Prof Id ------------------------------ ------------------------------ ----------1-3-1-0/voicefxs ethernet3-100/ip DN 5105220401 1/2/1 Total number of voice connections : 1
STA --ENA
Caution: Avoid changes or deletions to the ip-interface-record profile after creating a voice connection on that interface.
402
MALC Configuration Guide
Creating voice connections
Additional VoIP features This section describes the configurable VoIP features for VoIP-enabled services.
•
Setting VoIP features on page 403
•
Changing the hookflash timer values on page 404
•
Configuring always offhook on page 405
•
Configuring huntgroups on page 406
•
SIP dialing plans on page 410
•
Malicious caller on page 412
•
Call conferencing on page 413
Setting VoIP features To configure VoIP features: zSH> update subscriber-voice 1/2/1 Please provide the following: [q]uit. voice-connection-type: --------> {voiptopots}: ** read-only ** voice-endpoint1-addr-index: ---> {1}: ** read-only ** voice-endpoint2-addr-index: ---> {1001}: ** read-only ** voice-connection-description: -> {}: voice-admin-status: -----------> {enabled}: huntgroup: --------------------> {false}: ** read-only ** features: ---------------------> {hookflash+onhooksignaling}: hookflash. Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
MALC Configuration Guide
403
Configuring Voice
Changing the hookflash timer values The hookflash timer values can be configured to a specified range between minimum and maximum values. If hookflash is enabled on a VoIP subscriber, a hookflash is considered only if the onhook time is between the minimum and maximum timer values. Any time less than the minimum time setting is ignored and any time more than the maximum time setting is considered to be onhook. Modify the following parameters in the subscriber-voice profile to change hookflash timer settings. Parameter
Description
hookFlashTimerMin
Specifies the minimum hookflash timer value in milliseconds. Values: 0 to 2147483647 Default: 100 milliseconds
hookFlashTimerMax
Specifies the maximum hookflash timer value in milliseconds. Values: 0 to 2147483647 Default: 1550 milliseconds
To change the hookflash timer values: zSH> update voice-system 0 Please provide the following: [q]uit. hookflash-max-timer: -> {1550}: 2000 hookflash-min-timer: -> {100}: 500 partial-dial-timeout: ------> {16}: critical-dial-timeout: -----> {4}: busy-tone-timeout: ---------> {30}: dial-tone-timeout: ---------> {16}: msg-wait-tone-timeout: -----> {16}: offhook-warn-tone-timeout: -> {0}: ringing-timeout: -----------> {180}: ringback-timeout: ----------> {180}: reorder-tone-timeout: ------> {30}: stutter-tone-timeout: ------> {16}: server-max-timer: ----------> {20}: config-max1: ---------------> {5}: config-max2: ---------------> {7}: max1-enable: ---------------> {true}: max2-enable: ---------------> {true}: max-waiting-delay: ---------> {600}: disconnection-wait-timer: --> {15}: disconnection-min-timer: ---> {15}: disconnection-max-timer: ---> {600}: max-retransmit-timer: ------> {4}: init-retransmit-timer: -----> {200}:
404
MALC Configuration Guide
Creating voice connections
keep-alive-timer: ----------> no-response-timer: ---------> call-wait-max-repeat: ------> call-wait-delay: -----------> pulse-inter-digit-timer: ---> min-make-pulse-width: ------> max-make-pulse-width: ------> min-break-pulse-width: -----> max-break-pulse-width: -----> .................... Save changes? [s]ave, [c]hange Record updated.
{60}: {30}: {2}: {10}: {100}: {25}: {55}: {45}: {75}: or [q]uit: s
Configuring always offhook Some subscribers require circuits to remain permanently offhook to enable VoIP services such as two-way radio. Provision always offhook for MALC E&M TO subscribers to enable receiving two-way radio calls. Any incoming calls to this subscriber will be established right away. Note: After setting always offhook, users cannot make outgoing calls. Modify the following parameter to configure always offhook: Parameter
Description
features
Shows the set of VoIP features that are enabled for the subscriber. Hookflash is supported only on VoIP SIP POTS subscribers. Onhook is supported on all VoIP subscribers. Always offhook is supported on FXS and E&M (Z-Edge 6200) subscribers. Values: hookflash hookflash detection. onhooksignaling onhook signaling. alwaysoffhook call is established as soon as incoming call initiation is made. Default: hookflash+onhooksignaling Options: + This parameter allows multiple settings by using the + option.
1
Disable the subscriber and set always offhook:
zSH> update subscriber-voice 1/2/1 Please provide the following: [q]uit. voice-connection-type: --------> {voiptopots}: ** read-only ** voice-endpoint1-addr-index: ---> {1}: ** read-only ** voice-endpoint2-addr-index: ---> {1001}: ** read-only **
MALC Configuration Guide
405
Configuring Voice
voice-connection-description: -> {}: voice-admin-status: -----------> {enabled}: disabled huntgroup: --------------------> {false}: ** read-only ** features: ---------------------> {hookflash+onhooksignaling}: hookflash+onhooksignaling+alwaysoffhook .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
2
Re-enable the subscriber
zSH> update subscriber-voice 1/2/1 Please provide the following: [q]uit. voice-connection-type: --------> {voiptopots}: ** read-only ** voice-endpoint1-addr-index: ---> {1}: ** read-only ** voice-endpoint2-addr-index: ---> {1001}: ** read-only ** voice-connection-description: -> {}: voice-admin-status: -----------> {disabled}: enabled huntgroup: --------------------> {false}: ** read-only ** features: ---------------------> {hookflash+onhooksignaling+alwaysoffhook}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Record updated.
Configuring huntgroups Huntgroups are used to specify a group of people to receive incoming calls and determine which phone within that group will ring when a call comes in. For example, a company’s technical support phone number is 555-8000 and there are three members of the technical support team. Each one of the technical support members has a separate phone number, which is not 555-8000. With huntgroups, incoming calls to 555-8000 are directed to one of the technical support team. When a call comes in on 555-8000, calls will be placed on E&M ports 1, 2, or 3 in a round-robin fashion: The first time a call comes in, the phone on port 1 will ring; the second time a call comes in, the phone on port 2 will ring; the third time a call comes in, the phone on port 3 will ring, and fourth time a call comes in, the phone on port 1 will ring again. Each subscriber can belong to three huntgroups.
406
MALC Configuration Guide
Creating voice connections
Modify the huntgroup parameter in the subscriber-voice profile to enable huntgroups: Parameter
Description
huntgroup
Can be set to true only if the voice-connection-type is siptopots or siptods1. If it is set to true only subscriber-voice-endpt1 gets automatically created, but not subscriber-voice-endpt2. Values: true false Default: false
Modify the following parameters in the subscriber-voice-pots profile to enable huntgroups: Parameter
Description
hunt-group-index-1
The subscriber is part of this huntgroup. The hunt group endpoint index is derived from the voice-endpoint2-addr-index of the subscriber-voice connection which has huntgroup set to true.
hunt-group-index-2
The subscriber is part of this huntgroup. The hunt group endpoint index is derived from the voice-endpoint2-addr-index of the subscriber-voice connection which has huntgroup set to true.
hunt-group-index-3
The subscriber is part of this huntgroup. The hunt group endpoint index is derived from the voice-endpoint2-addr-index of the subscriber-voice connection which has huntgroup set to true.
Modify the following parameters in the subscriber-voice-voip profile to enable huntgroups: Parameter
Description
sip-uri
A uniform resource identifier (URI) which acts as a unique SIP identity for the subscriber.
MALC Configuration Guide
407
Configuring Voice
Parameter
Description
directory-number1
The phone number assigned to this endpoint.
ip-interface-index
Index of the interface through which the SIP signalling and real time protocol (RTP) traffic will flow.
Creating huntgroups on already existing subscribers built with no huntgroups To enable huntgroups on already-existing subscribers that do not have huntgroups: 1
Create a subscriber-voice profile which can support huntgroups:
zSH> new subscriber-voice 1/132/1 subId/lineGroupId/subVoiceId Please provide the following: (q=quit) voice-connection-type: ---------->[NONE(0)]: siptopots voice-endpoint1-addr-index: ----->[0]: 1 index for the subscriber-voice-voip profile voice-endpoint2-addr-index: ----->[0]: 99 index for the huntgroup voice-connection-description: --->[]: voice-admin-status: ------------->[disabled]: huntgroup:--------------------> [false]: true ....................... Save new record? (s=save/c=change/q=quit): s New record saved.
After creating the subscriber-voice-profile with the huntgroup parameter set to true, the system automatically creates the associated subscriber-voice-voip profile. 2
Update the SIP voice endpoint: zSH> update subscriber-voice-voip 1 Please provide the following: [q]uit. sip-uri: ------------> {}: support directory-number: ---> {}: 5558000 ip-interface-index: -> {0/0/0/0/0}: 1/1/1/0/ip preferred-code: -----> {g711mu}: g711-fallback: ------> {true}: frames-per-packet: --> {4}: g726-byte-order: ----> {bigendian}: sip-password: -------> {}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
3
Update one of the pre-existing subscriber-voice-pots profiles:
zSH> update subscriber-voice-pots 2 Please provide the following: [q]uit. voice-pots-line-group-id: -> {2} hunt-group-index-1: -------> {} 99 matches the voice-endpoint2-addr-index from subscriber-voice profile
408
MALC Configuration Guide
Creating voice connections
hunt-group-index-2: -------> {0} hunt-group-index-3: -------> {0} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Creating subscribers built with pre-existing huntgroups To enable huntgroups on already-existing subscribers that already have huntgroups created in the subscriber-voice-pots profile: 1
Find the huntgroup index from the pre-existing subscriber-voice-pots profile. After creating the subscriber-voice-profile with the huntgroup parameter is set to true, the system automatically creates the associated subscriber-voice-voip profile.
2
Update the SIP voice endpoint:
zSH> update subscriber-voice-voip 2 Please provide the following: [q]uit. sip-uri: ------------> {}: support directory-number: ---> {}: 5558000 ip-interface-index: -> {0/0/0/0/0}: 1/1/1/0/ip preferred-code: -----> {g711mu}: g711-fallback: ------> {true}: frames-per-packet: --> {4}: g726-byte-order: ----> {bigendian}: sip-password: -------> {}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Creating new subscribers with huntgroups enabled To create new subscribers with huntgroups enabled: Create a subscriber-voice profile which can support huntgroups: After creating the subscriber-voice-profile with the huntgroup parameter set to true, the system automatically creates the associated subscriber-voice-voip profile. 1
Update the SIP voice endpoint: zSH> update subscriber-voice-voip 3 Please provide the following: [q]uit. sip-uri: ------------> {}: support3 directory-number: ---> {}: 5559000 ip-interface-index: -> {0/0/0/0/0}: 1/1/1/0/ip preferred-code: -----> {g711mu}: g711-fallback: ------> {true}: frames-per-packet: --> {4}: g726-byte-order: ----> {bigendian}: sip-password: -------> {}:
MALC Configuration Guide
409
Configuring Voice
.................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
2
Create a subscriber-voice profile without huntgroups:
zSH> new subscriber-voice 1/132/99 Please provide the following: (q=quit) voice-connection-type: ---------->{aal2togr303}: siptopots voice-endpoint1-addr-index: ----->{0}: 8 index for the subscriber-voice-voip profile voice-endpoint2-addr-index: ----->{0}: 9 index for the subscriber-voice-pots profile voice-connection-description: --->{}: voice-admin-status: ------------->{disabled}: huntgroup:--------------------> {false}: ....................... Save new record? (s=save/c=change/q=quit): s New record saved.
3
Update the subscriber-voice-voip profile: zSH> update subscriber-voice-voip 9 Please provide the following: [q]uit. sip-uri: ------------> {}: johnsmith directory-number: ---> {}: 5559999 ip-interface-index: -> {0/0/0/0/0}: 1/1/1/0/ip preferred-code: -----> {g711mu}: g711-fallback: ------> {true}: frames-per-packet: --> {4}: g726-byte-order: ----> {bigendian}: sip-password: -------> {}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
4
Update the subscriber-voice-pots profile to match the huntgroup created:
zSH> update subscriber-voice-pots 9 Please provide the following: [q]uit. voice-pots-line-group-id: -> {9} hunt-group-index-1: -------> {} 88 matches the voice-endpoint2-addr-index from subscriber-voice profile hunt-group-index-2: -------> {0} hunt-group-index-3: -------> {0} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
SIP dialing plans A dialing plan for POTS-to-SIP outgoing calls consists of a series of acceptable dial strings and the corresponding IP addresses to which SIP control messages are sent to initiate the call. Each dial string is represented as digits, wildcards, and regular-expression-like patterns according to the following rules:
410
MALC Configuration Guide
Creating voice connections
•
Digits 0 to 9 are allowed as well as * and #.
•
A wildcard ? represents any digit 0 to 9
•
The character x to indicate a wildcard for 0 or more digits between 0-9.
•
A dial-string character T can be used in the override-interdigit-timeout parameter value in the SIP dialplan. Examples: –
0T for the number zero and nothing else.
–
011T for numbers 011 then any number of digits before the interdigit time out.
–
9T for the number 9 and any number of digits before the interdigit time out.
–
#T anything followed by a # and an interdigit time out.
•
A digit range can be specified using brackets [ ], as follows: [135] means digits 1, 3, or 5. [1-4] means digits 1, 2, 3, or 4.
•
MGCP-style digit mapping where a period ‘.’ represents any digit and a | character indicates an inclusive OR. Examples: –
.T for any number of digits before the interdigit timeout.
–
*x.T | x.T indicates star plus any number of digits followed by the inter-digit timeout or any number of digits followed by the inter-digit timeout.
–
*.xT | x.T | [2-9]11 indicates star plus any number of digits followed by the inter-digit timeout or any number of digits followed by the inter-digit timeout. or digits 2 to 9 followed by 11. The [2-9]11 explicit digit matching enables expedited call connections for emergency calls.
Create a sip-dialplan profile for outgoing VoIP calls by modifying the following parameters: Parameter
Description
match-string
A dial string against which collected digits are matched.
sip-ip-address
Upon detecting a match between the collected digits and the dial string, this IP address is used for SIP negotiations to initiate the call.
destination -name
User-specified name of the destination for the dial string.
MALC Configuration Guide
411
Configuring Voice
Parameter
Description
number-of-digits
Number of digits to wait for before initiating the call.
prefix-strip
Number of prefix digits to strip from dialled digits.
prefix-add
String to be added to the beginning of the dialled digits before call initiation.
dialplan-type
Type of the dial plan. Dialplan types are:
• •
Normal Call Park
voip-server-entry-index
An index to associated voip-server-entry for this sip-dialplan. This index references the registration server specified in the voip-server-entry profile.
override-interdigit-timeout
Override the partial-dial-timeout value in voice-system profile.
zSH> new sip-dialplan 1 Please provide the following: [q]uit. match-string: ----------------> {}: 510555101[1-9] sip-ip-address: --------------> {0.0.0.0}: 192.16.88.199 destination-name: ------------> {}: caller number-of-digits: ------------> {0}: 10 prefix-strip: ----------------> {0}: 1 prefix-add: ------------------> {}: 0 dialplan-type: ---------------> {normal}: voip-server-entry-index: -----> {0}: 1 override-interdigit-timeout:--> {0}: 22 .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created.
Malicious caller The malicious caller feature enables you to configure caller uniform resource identifiers (URIs) so that incoming calls with the configured URIs will be rejected. The URI can be configured as either a telephone number (RFC 2806) or an alphanumeric identification (RFC 2806). URI entries are case sensitive, should not contain visual separations and must be the exact length as they appear in incoming session notification’s (SIP INVITE) calling user’s address-of-record (AOR).
412
MALC Configuration Guide
Call conferencing
Specifying a malicious caller Configure malicious caller URIs in the malicious-caller profile. The following parameters are supported in this profile: Parameter
Description
malicious-caller-uri
The URI for which incoming calls will be rejected. The network operator is responsible for provisioning the URI exactly as per appearance in the incoming session notification (SIP INVITE) the calling user's address-of-record (AOR) formatted as a SIP URI.
reject-enabled
Enables and disables the rejection of calls matching the configured malicious caller URI. Default: true
To specify a malicious caller: Create a new malicious-caller profile to reject a particular caller: zSH> new malicious-caller 1 Please provide the following: [q]uit. malicious-caller-uri: -> {}:
[email protected] reject-enabled: -------> {true}: Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Call conferencing The MALC call conferencing feature enables three-way conference calls during which three parties can use one calling session to communicate. The MALC POTS-TDM-/PKT-48 card and the ADSL+POTS TDM/PKT-48A-2S combination cards support call conferencing. These cards work with any VOIP-enabled uplink card installed in the MALC. The MALC call conferencing feature deploys an efficient end-mixing conference call technology, avoiding the overhead of the centralized conference server. Three-way call conferencing follows the Telcordia (Bellcore) three-way calling standard called Telcordia - TR - TSY - 000577, Three-Way Calling. Configuring call conferencing on the MALC. The call conference feature is enabled through the features parameter in the subscriber-voice profile for callers using the specified port on a MALC POTS-TDM-/PKT-48 card or ADSL+POTS TDM/PKT-48A-2S card. By default, this feature is disabled.
MALC Configuration Guide
413
Configuring Voice
To enable conferencing, use the voice show command to identify voice ID for the desired voice subscriber. Then, update the subscriber-voice profile for the desired subscriber with support for hookflash and conference. Additional features such as onhooksignaling and call waiting can also be added. The following example configures call conferencing along with onhooksignaling and call waiting for the voice subscriber 1/3/1. zSH> voice show Subscriber end-point Remote end-point Voice Prof Id STA ---------------------------- ------------------------------ -------------- --1-10-1-0/voicefxs ethernet1-2/ip DN 2408881694 1/3/1 ENA
…………………… zSH> update subscriber-voice 1/3/1 Please provide the following: [q]uit. voice-connection-type: --------> {voiptopots}: ** read-only ** voice-endpoint1-addr-index: ---> {2}: ** read-only ** voice-endpoint2-addr-index: ---> {1}: ** read-only ** voice-connection-description: -> {}: voice-admin-status: -----------> {enabled}: huntgroup: --------------------> {false}: ** read-only ** features: ---------------------> {hookflash+onhooksignaling+callwait}: hookflash+onhooksignaling+callwait+conference .................... Save changes? [s]ave, [c]hange or [q]uit: s
Connecting three-way conference calls. The process of connecting a three-way conference call involves the following steps:
•
Caller dials the phone number of the first conference participate. This establishes a two-way speech path between the caller and the first participate.
•
After establishing the call, the caller presses the Flash button or provides hookflash. This place the first participate on hold and sends a hookflash signal to the MALC for a second dial tone.
•
Caller dials the phone number of the second conference participate. This establishes a two-way speech path between the caller and the second participate.
•
After establishing the second call, the caller presses the Flash button or provides hookflash. This establishes the three-way conference call.
414
MALC Configuration Guide
Call conferencing
Note: If the call conference features is not enabled on the MALC and a caller issues a hookflash signal while on an established call, the MALC places the current call on hold and provides a dial-tone for a second call. Subsequent hookflash signals, toggle between the two established calls. If a hookflash signal is issued during a three-way conference call, the last conference participate is dropped and the call becomes a two-way call.
To disconnect from a three-way conference call:
•
The originating caller hangs up, all members of the conference call are disconnected.
•
A caller other than the originating caller hangs up, a two-way call between the originating caller and the other caller remains in progress.
Current call conferencing limitations. The following are current limitations to the call conferencing feature:
•
Only SIP is supported for conferencing.
•
For resource utilization, three-party call conferencing divides the available 48 port resources in to 8 groups of 6 sequential port resources based on physical port number (1-6, 7-12, ... ,43-48). Within a port resource group, any idle port resource may be used for a call, including conference sessions. For a two-way call, one port resource is used. For a three-way conference call, two port resources are used. If an idle port resource is unavailable because of an on-going conference call within a port resource group, any new two-way call attempts receive a fast-busy tone and any three-way conference call attempts will not succeed. Three-way conference call attempts are restricted to toggling between the established two-way calls. To minimize call blockage, configure ports in sequence leaving three ports idle in each port resource group. For example: –
Activate ports: 1,2,3,7,8,9,13,14,15,19,20,21,25,26,27,31,32,33,37,38,39,43,44,45,
–
Idle ports: 4,5,6,10,11,12,16,17,18,22,23,24,28,29,30,34,35,36,40,41,42,46,47, 48
As more ports are required, add an additional port from each sequential port resource group until all necessary ports are configured.
MALC Configuration Guide
415
Configuring Voice
DS1 to POTS connections The MALC can act as a channel bank, interconnecting POTS channels to DS0s on the TDM T1/E1 Uplink card. Note that T1 CAS, GR-303, and V5.2 signaling cannot be active on a card at the same time.
Adding a POTS to DS1 connection To enable a POTS to DS1 connection, you must reset the line type on the T1/ E1 TDM card. Caution: Changing the line type for the Uplink card requires a system reboot and deletes the system configuration. Back up your configuration using the dump command before changing the line type. 1
Change the line type on the T1/E1 TDM card. Note: If there is a redundant Uplink card in the system, change that line type for the redundant card before changing it for the active card. For the T1/E1 TDM card: a
Verify you are at the root of the flash card: zSH> cd /card1 zSH> pwd /card1/
b
Back up the current configuration file to the flash card and store it in the onreboot directory: zSH> mkdir onreboot zSH> cd onreboot zSH> dump file restore
This file will be used to restore the system configuration or revert to a previous release, if desired. c
If desired, save the configuration file to a host on the network. For example: zSH> dump network 192.168.8.21 malc.cfg
d
Change directories to the root of the flash card: zSH> cd /card1 zSH> pwd /card1/
e
Delete the Uplink card-profile: zSH> delete card-profile 1/1/5114 shelf/slot/type
416
MALC Configuration Guide
Configuring CES connections
f
Create a new Uplink card-profile and change the card-line-type:
zSH> card add 1/1/5114 linetype t1-uni-t1cas
or zSH> new card-profile 1/1/5114 Please provide the following: [q]uit. sw-file-name: ---------> {}: malcT1E1Tdmf.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {false}: true sw-upgrade-enable: ----> {false}: card-group-id: --------> {1}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: t1-uni-t1cas card-atm-configuration: -> {notapplicable} .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
After saving the Uplink card-profile, the card will reboot and restore the configuration saved to the onreboot directory. If this is a redundant system, the standby card will take over. You must also change the line type on the redundant card. 2
After the system has finished booting, create the voice connection. The following example maps POTS port 24 to DS0 24 on the T1/E1 TDM card:
zSH> voice add pots 1-5-24-0/voicefxs ds1 1-1-9-0/ds1 ds0 24 Created subscriber-voice 1/21/25 Created subscriber-voice-pots 83 Created subscriber-voice-ds1 84
3
View the voice connection:
zSH> voice show Subscriber end-point Remote end-point Voice Prof Id STA ------------------------------ ------------------------------ -------------- --1-5-24-0/voicefxs 1-1-9-0/ds1 DS0 24 1/21/25 ENA Total number of voice connections : 1
Configuring CES connections Circuit Emulation Service (CES) circuit configuration involves:
•
Creating IP interface and unnumbered IP interface on page 418
•
Creating CES connections on page 419
MALC Configuration Guide
417
Configuring Voice
•
Deleting cross connections and CES over ATM circuits on page 433
Creating IP interface and unnumbered IP interface If using CES over IP, an IP interface and unnumbered IP interface record are required before the CES over IP connection can be created: Note: CES over IP is only supported on RPR GigE uplinks.
1
Create the IP interface record. zSH> new ip-interface-record ces/ip Please provide the following: [q]uit. vpi: ---------------> {0}: vci: ---------------> {0}: rdindex: -----------> {1}: dhcp: --------------> {none}: ** read-only ** addr: --------------> {0.0.0.0}: 192.168.100.1 netmask: -----------> {0.0.0.0}: 255.255.255.0 bcastaddr: ---------> {0.0.0.0}: 192.168.100.255 destaddr: ----------> {0.0.0.0}: farendaddr: --------> {0.0.0.0}: mru: ---------------> {1500}: reasmmaxsize: ------> {0}: ingressfiltername: -> {}: egressfiltername: --> {}: pointtopoint: ------> {no}: mcastenabled: ------> {yes}: ipfwdenabled: ------> {yes}: mcastfwdenabled: ---> {yes}: natenabled: --------> {no}: bcastenabled: ------> {yes}: ingressfilterid: ---> {0}: egressfilterid: ----> {0}: ipaddrdynamic: -----> {static}: dhcpserverenable: --> {false}: subnetgroup: -------> {0}: unnumberedindex: ---> {0}: mcastcontrollist: --> {}: vlanid: ------------> {0}: maxVideoStreams: ---> {0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Could not find an appropropriate interface on which to bind the IP record. Could not automatically bind this IP Interface New record saved.
2
Create IP unnumbered record. zSH> new ip-unnumbered-record 1 Please provide the following: [q]uit.
418
MALC Configuration Guide
Configuring CES connections
ipUnnumberedInterfaceName: -> { }: ces/ip .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Creating CES connections The CES add command specifies the parameters for one side of the CES over IP connection. Generally, each CES over IP endpoint resides on a different MALC system and must be configured and deleted separately for each side for the circuit. The cross connect command specifies the parameters for one side of the CES connection over an ATM circuit.The traffic descriptor is used for internal ATM processing. Generally, each CES connection endpoint resides on a different MALC system and must be configured and deleted separately for each side for the circuit.
CES signaling CES connections support both Channel Associated Signaling (CAS) and Common Channel Signaling (CCS) depending on the connection mode and type. For structured T1 circuits, the CES card supports CAS (robbedbit signaling) for in-band signaling. CAS uses one bit out of every channel in the sixth T1 frame in order to transmit signaling messages. Unstructured T1 circuits support CCS for out-of-band signaling that uses an entire channel of each T1 frame to transmit signaling. For structured E1 circuits, CAS can be used to extract signaling information from timeslot 16 and then reinsert signaling data at the other end of the connection. Unstructured E1 circuits transmit all 32 timeslots transparently. Signal mode is set in the ds1-profile. zSH> update ds1-profile 1-4-1-0/ds1 Please provide the following: [q]uit. line-type: ----------------------> {esf}: line-code: ----------------------> {b8zs}: send-code: ----------------------> {sendnocode}: circuit-id: ---------------------> {ds1}: loopback-config: ----------------> {noloop}: signal-mode: --------------------> {robbedbit}: bitoriented fdl: ----------------------------> {fdlnone}: dsx-line-length: ----------------> {dsx0}: line-status_change-trap-enable: -> {enabled}: channelization: -----------------> {enabledds0}: ds1-mode: -----------------------> {csu}: csu-line-length: ----------------> {csu00}: clock-source-eligible: ----------> {eligible}: transmit-clock-source: ----------> {looptiming}: cell-scramble: ------------------> {true}:
MALC Configuration Guide
419
Configuring Voice
coset-polynomial: ---------------> {true}: protocol-emulation: -------------> {network}: signal-type: --------------------> {loopstart}: ds1-group-number: ---------------> {0}: line-power: ---------------------> {disabled}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
CES clocking The CES card supports two timing modes:
•
Loop timing
•
Through timing
Loop timing indicates that the timing source is coming from the line. Through timing indicates that the timing sources is from the backplane. The backplane can be set to receive its clocking signal from a port on an uplink card or ports on a line card. When through timing is used, the other side of the CES circuit should be set to loop timing. If loop timing is used and the card loses its received clock signal, clocking switches to the clock on the board. Clock mode is set in the DS1-profile. Refer to the MALC Hardware Installation Guide for the procedures on how configure MALC timing. zSH> update ds1-profile 1-4-1-0/ds1 Please provide the following: [q]uit. line-type: ----------------------> {esf}: line-code: ----------------------> {b8zs}: send-code: ----------------------> {sendnocode}: circuit-id: ---------------------> {ds1}: loopback-config: ----------------> {noloop}: signal-mode: --------------------> {robbedbit}: fdl: ----------------------------> {fdlnone}: dsx-line-length: ----------------> {dsx0}: line-status_change-trap-enable: -> {enabled}: channelization: -----------------> {enabledds0}: ds1-mode: -----------------------> {csu}: csu-line-length: ----------------> {csu00}: clock-source-eligible: ----------> {eligible}: transmit-clock-source: ----------> {looptiming}: throughtiming cell-scramble: ------------------> {true}: coset-polynomial: ---------------> {true}: protocol-emulation: -------------> {network}: signal-type: --------------------> {loopstart}: ds1-group-number: ---------------> {0}: line-power: ---------------------> {disabled}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
420
MALC Configuration Guide
Configuring CES connections
CES configuration This section shows configuration examples for the following CES procedures:
•
Adding an unstructured T1/E1 CES over IP circuit on page 422
•
Adding a structured T1/E1 CES over IP circuit with ds1esfcas signaling on page 424
•
Adding unstructured T1 CES circuits on page 427
•
Adding a structured T1 CES circuit with ds1esfcas signaling on page 428
•
Adding a second DS0 bundle to a structured T1 CES circuit with ds1esfcas signaling on page 429
•
Adding unstructured E1 CES circuits on page 430
•
Adding a structured E1 CES circuit with e1cas signaling on page 431
•
Adding a second cross connect to a structured E1 CES circuit with e1cas signaling on page 432
•
Deleting cross connections and CES over ATM circuits on page 433
The CES circuit signaling type is specified in the cross connect command used to create the connection. After cross connect configuration, the signaling type can be modified by updating the ces-config profile. Note: When required, CES virtual circuits (VCs) are auto-generated from the cross connect command. The default virtual circuit ranges are VPI 0-3 and VCI 32-127. Table 30: Supported CES signaling types Signaling Type
Description
basic
No CAS bits with a single 125 usec frame. Default. Required for unstructured channels.
e1cas
CAS bits used in E1 multiframe structure.
ds1esfcas
CAS bits used in DS1 ESF multiframe structure.
ds1sfcas
CAS bits used in DS1 SF multiframe structure.
After the cross connect command is issued, the system automatically creates the required ces-config profile with the specified signaling type and other settings. The default signaling type basic is required for unstructured, single channel signaling and is used if a signalling type is not specified in the cross connect command. Table 30 on page 421 lists the supported signaling types.
MALC Configuration Guide
421
Configuring Voice
Note: Structured DS0 bundles in cross connects are specified by start and length values and therefore contain contiguous DS0s. To use non-contiguous DS0s, modify the DS0-bundle parameter in the ces-config profile. For the first DS0 bundle in a structured DS1 circuit, the frame type specified in the cross connect command is written to the DS1 profile and becomes the default frame type for that DS1 circuit. Subsequent DS0 bundles in the same DS1 circuit use the default frame type regardless of the line type specified in the cross connect command. If line type is not specified in the cross connect command, the line type in the DS1 profile is used. Note: A maximum of 4 structured DS0 bundles can be configured per CES port.
Adding an unstructured T1/E1 CES over IP circuit Note: This procedure assumes that the T1E1CES12 card is installed and running on the current device, a valid traffic descriptor has been configured, and the unnumbered IP interface record has been created. To add a CES connection for an unstructured T1/E1 CES over IP circuit, repeat these configuration steps for each endpoint of the circuit. 1
Specify ces add command with the desired settings for each side for the CES circuit. This example specifies an unstructured T1 circuit (single channel). No signaling type or line type are specified. Unstructured channels required basic signaling so the basic signaling type is used. The line type in the DS1-profile is set to ds1unframed. Because no line type is specified in this command, the line type from the DS1-profile is used. The traffic descriptor 102 is autocreated and used for internal processing. Using slot 8, port 2 on the CES card, the static IP addressing is source IP address 10.2.2.82. and destination IP address is 10.2.3.83. The source UDP port number is 48001. The destination UDP port number is 48201. Note: Ensure the IP routes between the source and destination subnetworks have been configured and are available. UPD port numbers must be between 48000 and 48300.
zSH> ces add 1-8-2-0-ds1/atm ds0 1/24 unstr td 102 llc static 10.2.2.82 10.2.3.83 48001 48002 zSH> ces add 1-8-3-0-ds1/atm ds0 1/24 unstr td 102 llc static 10.2.3.83 10.2.2.82 48002 48001
2
Change the administrative status of the ports to up. zSH> update if-translate 1-8-2-0/ds1 Please provide the following: [q]uit. ifIndex: -----------> {200}: shelf: -------------> {1}:
422
MALC Configuration Guide
Configuring CES connections
slot: --------------> {7}: port: --------------> {1}: subport: -----------> {0}: type: --------------> {ds1}: adminstatus: -------> {down}: up physical-flag: -----> {true}: iftype-extension: --> {none}: ifName: ------------> {1-7-1-0}: redundancy-param1: -> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.zSH> zSH> update if-translate 1-8-3-0/ds1 Please provide the following: [q]uit. ifIndex: -----------> {200}: shelf: -------------> {1}: slot: --------------> {7}: port: --------------> {1}: subport: -----------> {0}: type: --------------> {ds1}: adminstatus: -------> {down}: up physical-flag: -----> {true}: iftype-extension: --> {none}: ifName: ------------> {1-7-1-0}: redundancy-param1: -> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.zSH>
3
Display the configured cross connection.
zSH> cc show CES CONNECTION CC CONNECTION --------------------------------------------------------------------------1-1-1-0-aal5proxy/atm 0/33 Up 2 Up 1-8-2-0/ds1 1/24 Up 1-1-1-0-aal5proxy/atm 0/34 Up 3 Up 1-8-3-0/ds1 1/24 Up
4
Display the DS1 profile for the configured T1/E1 CES unstructured circuit over IP. zSH> get ds1-profile 1-8-2-0/ds1 line-type: ----------------------> line-code: ----------------------> send-code: ----------------------> circuit-id: ---------------------> loopback-config: ----------------> signal-mode: --------------------> fdl: ----------------------------> dsx-line-length: ----------------> line-status_change-trap-enable: -> channelization: -----------------> ds1-mode: ----------------------->
{ds1unframed} {b8zs} {sendnocode} {ds1} {noloop} {none} {fdlnone} {dsx0} {enabled} {disabled} {csu}
MALC Configuration Guide
423
Configuring Voice
csu-line-length: ----------------> clock-source-eligible: ----------> transmit-clock-source: ----------> cell-scramble: ------------------> coset-polynomial: ---------------> protocol-emulation: -------------> signal-type: --------------------> ds1-group-number: ---------------> line-power: --------------------->
5
{csu00} {eligible} {throughtiming} {true} {true} {network} {loopstart} {0} {disabled}
Display the ces-config profile for the configured T1/E1 CES unstructured circuit. Note: The default number of UDP ports available for the source-port and destination-port in ces-config profile are 48000 48300. The number of available ports does not impact the CES behavior or provisioning. zSH> get ces-config 1-8-2-0-ds1-1/ds0bundle vpi: --------------------------> {1} vci: --------------------------> {33} cas: --------------------------> {basic} partial-fill: -----------------> {0} buf-max-size: -----------------> {128} cell-loss-integration-period: -> {2500} ds0-bundle: -------------------> {1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+21 +22+23+24} source-ip-address: ------------> {10.2.4.82} destination-ip-address: -------> {10.2.4.83} source-port: ------------------> {48001} destination-port: -------------> {48002}
Adding a structured T1/E1 CES over IP circuit with ds1esfcas signaling To add a CES cross connection for a structured T1/E1 CES circuit with esfcas signaling, repeat these configuration steps for each endpoint of the circuit. 1
Specify cross connect command with the desired settings for each side of the CES circuit. This example command creates a structured T1 circuit using 6 DS0s starting at DS0 1 with ds1esfcas signaling. No line type is specified so the default esf line type from the DS1-profile is used. Traffic descriptor 1 is used. Using slot 7, port 1 on the CES card, the source IP address is 192.168.11.101. The destination IP address is 192.168.12.102. The source UDP port number is 48002. The destination UDP port number is 48202. Note: Ensure the IP routes between the source and destination subnetworks have been configured and are available. UPD port numbers must be between 48000 and 48300.
424
MALC Configuration Guide
Configuring CES connections
zSH> ces add 1-7-1-0-ds1/atm ds0 1/6 struct ds1esfcas td 1 llc static 192.168.11.101 192.168.100.12 48003 48004 zSH> ces add 1-7-2-0-ds1/atm ds0 1/6 struct ds1esfcas td 1 llc static 192.168.12.102 192.168.11.101 48004 48003
2
Change the admin status of the ports to up: zSH> update if-translate 1-7-1-0/ds1 Please provide the following: [q]uit. ifIndex: -----------> {200}: shelf: -------------> {1}: slot: --------------> {7}: port: --------------> {1}: subport: -----------> {0}: type: --------------> {ds1}: adminstatus: -------> {down}: up physical-flag: -----> {true}: iftype-extension: --> {none}: ifName: ------------> {1-7-1-0}: redundancy-param1: -> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated. zSH> update if-translate 1-7-2-0/ds1 Please provide the following: [q]uit. ifIndex: -----------> {200}: shelf: -------------> {1}: slot: --------------> {7}: port: --------------> {1}: subport: -----------> {0}: type: --------------> {ds1}: adminstatus: -------> {down}: up physical-flag: -----> {true}: iftype-extension: --> {none}: ifName: ------------> {1-7-1-0}: redundancy-param1: -> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.zSH>
MALC Configuration Guide
425
Configuring Voice
3
Display the configured cross connections.
zSH> cc show CES CONNECTION CC CONNECTION --------------------------------------------------------------------------1-1-1-0-aal5proxy/atm 0/35 Up 1 Up 1-7-1-0/ds1 1/6 Up 1-1-1-0-aal5proxy/atm 0/36 Up 2 Up 1-7-2-0/ds1 1/6 Up
4
Display the DS1 profile for the configured structured CES circuit over IP. zSH> get ds1-profile 1-7-1-0/ds1 line-type: ----------------------> line-code: ----------------------> send-code: ----------------------> circuit-id: ---------------------> loopback-config: ----------------> signal-mode: --------------------> fdl: ----------------------------> dsx-line-length: ----------------> line-status_change-trap-enable: -> channelization: -----------------> ds1-mode: -----------------------> csu-line-length: ----------------> clock-source-eligible: ----------> transmit-clock-source: ----------> cell-scramble: ------------------> coset-polynomial: ---------------> protocol-emulation: -------------> signal-type: --------------------> ds1-group-number: ---------------> line-power: --------------------->
5
{esf} {b8zs} {sendnocode} {ds1} {noloop} {robbedbit} {fdlnone} {dsx0} {enabled} {disabled} {csu} {csu00} {eligible} {throughtiming} {true} {true} {network} {loopstart} {0} {disabled}
Display the ces-config profile for the configured structured CES circuit over IP. Note: The default number of UDP ports available for the source-port and destination-port in ces-config profile are 48000 48300. The number of available ports does not impact the CES behavior or provisioning. zSH> get ces-config 1-7-1-0-ds1-1/ds0bundle vpi: --------------------------> {1} vci: --------------------------> {35} cas: --------------------------> {ds1esfcas} partial-fill: -----------------> {0} buf-max-size: -----------------> {128} cell-loss-integration-period: -> {2500} ds0-bundle: -------------------> {1+2+3+4+5+6} source-ip-address: ------------> {10.2.4.82} source-port: ------------------> {140} destination-ip-address: -------> {10.2.4.83} destination-port: -------------> {48004}
426
MALC Configuration Guide
Configuring CES connections
Adding unstructured T1 CES circuits To add a CES cross connection for an unstructured T1 CES circuit, repeat these configuration steps for each endpoint of the circuit. 1
Specify cross connect command with the desired settings. This example specifies an unstructured circuit (single channel). No signaling type or line type are specified. Unstructured single channels require basic signaling so the basic signaling type is used. The ds1unframed line type from the DS1-profile is used.
zSH> cc add uplink2/atm 0/53 1-12-3-0/ds1 vc 1/33 ds0 1/24 unstr td 1
2
Display the configured cross connection.
zSH> cc show CES ATM VCL CC ATM VCL -------------------------------------------------------------------------uplink2/atm 0/53 Up 1 Up 1-12-3-0-ds1/atm 1/33 Up
3
Display the DS1 profile for the configured T1 CES unstructured circuit. zSH> get ds1-profile 1-12-3-0/ds1 line-type: ----------------------> line-code: ----------------------> send-code: ----------------------> circuit-id: ---------------------> loopback-config: ----------------> signal-mode: --------------------> fdl: ----------------------------> dsx-line-length: ----------------> line-status_change-trap-enable: -> channelization: -----------------> ds1-mode: -----------------------> csu-line-length: ----------------> clock-source-eligible: ----------> transmit-clock-source: ----------> cell-scramble: ------------------> coset-polynomial: ---------------> protocol-emulation: -------------> signal-type: --------------------> ds1-group-number: ---------------> line-power: --------------------->
4
{ds1unframed} {b8zs} {sendnocode} {ds1} {noloop} {none} {fdlnone} {dsx0} {enabled} {disabled} {csu} {csu00} {eligible} {throughtiming} {true} {true} {network} {loopstart} {0} {disabled}
Display the ces-config profile for the configured T1 CES unstructured circuit. zSH> get ces-config 1-12-3-0-ds1-1/ds0bundle vpi: --------------------------> {1} vci: --------------------------> {33} cas: --------------------------> {basic} partial-fill: -----------------> {0} buf-max-size: -----------------> {128} cell-loss-integration-period: -> {2500} ds0-bundle: -------------------> {1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+21+ 22+23+24}
MALC Configuration Guide
427
Configuring Voice
Adding a structured T1 CES circuit with ds1esfcas signaling To add a CES cross connection for a structured T1 CES circuit with esfcas signaling, repeat these configuration steps for each endpoint of the circuit. 1
Specify cross connect command with the desired settings. This example command creates a structured circuit using 6 DS0s starting at DS0 1 with ds1esfcas signaling. No line type is specified so the esf line type from the DS1-profile is used.
zSH> cc add uplink2/atm 0/54 1-12-4-0/ds1 vc 1/34 ds0 1/6 str ds1esfcas td 1
2
Display the configured cross connections.
zSH> cc show CES ATM VCL CC ATM VCL -------------------------------------------------------------------------uplink2/atm 0/53 Up 1 Up 1-12-3-0-ds1/atm 1/33 Up uplink2/atm 0/54 Up 3 Up 1-12-4-0-ds1/atm 1/34 Up
3
Display the DS1 profile for the configured structured CES circuit. zSH> get ds1-profile 1-12-4-0/ds1 line-type: ----------------------> line-code: ----------------------> send-code: ----------------------> circuit-id: ---------------------> loopback-config: ----------------> signal-mode: --------------------> fdl: ----------------------------> dsx-line-length: ----------------> line-status_change-trap-enable: -> channelization: -----------------> ds1-mode: -----------------------> csu-line-length: ----------------> clock-source-eligible: ----------> transmit-clock-source: ----------> cell-scramble: ------------------> coset-polynomial: ---------------> protocol-emulation: -------------> signal-type: --------------------> ds1-group-number: ---------------> line-power: --------------------->
4
{esf} {b8zs} {sendnocode} {ds1} {noloop} {robbedbit} {fdlnone} {dsx0} {enabled} {disabled} {csu} {csu00} {eligible} {throughtiming} {true} {true} {network} {loopstart} {0} {disabled}
Display the ces-config profile for the configured CES circuit. zSH> get ces-config 1-12-4-0-ds1-1/ds0bundle vpi: --------------------------> {1} vci: --------------------------> {34} cas: --------------------------> {ds1esfcas} partial-fill: -----------------> {0} buf-max-size: -----------------> {128} cell-loss-integration-period: -> {2500} ds0-bundle: -------------------> {1+2+3+4+5+6}
428
MALC Configuration Guide
Configuring CES connections
Adding a second DS0 bundle to a structured T1 CES circuit with ds1esfcas signaling To add a second DS0 bundle to a CES cross connection for a structured T1 CES circuit with ds1esfcas signaling, repeat these configuration steps for each endpoint of the circuit. 1
Specify cross connect command with the desired settings. This example command specifies 6 DS0s starting at DS0 7 in a structured circuit using ds1esfcas signaling type. The line type for secondary DS0 bundles must match the line type of the first bundle or be left unspecified so the esf line type from the DS1-profile is used.
zSH> cc add uplink2/atm 0/55 1-12-5-0/ds1 vc 1/35 ds0 7/6 str ds1esfcas td 1
2
Display the configured cross connections.
zSH> cc show CES ATM VCL CC ATM VCL -------------------------------------------------------------------------uplink2/atm 0/53 Up 1 Up 1-12-3-0-ds1/atm 1/33 Up uplink2/atm 0/54 Up 2 Up 1-12-4-0-ds1/atm 1/34 Up uplink2/atm 0/55 Up 3 Up 1-12-5-0-ds1/atm 1/35 Up
3
Display the DS1 profile for the configured structured CES circuit. zSH> get ds1-profile 1-12-5-0/ds1 line-type: ----------------------> line-code: ----------------------> send-code: ----------------------> circuit-id: ---------------------> loopback-config: ----------------> signal-mode: --------------------> fdl: ----------------------------> dsx-line-length: ----------------> line-status_change-trap-enable: -> channelization: -----------------> ds1-mode: -----------------------> csu-line-length: ----------------> clock-source-eligible: ----------> transmit-clock-source: ----------> cell-scramble: ------------------> coset-polynomial: ---------------> protocol-emulation: -------------> signal-type: --------------------> ds1-group-number: ---------------> line-power: --------------------->
4
{esf} {b8zs} {sendnocode} {ds1} {noloop} {robbedbit} {fdlnone} {dsx0} {enabled} {disabled} {csu} {csu00} {eligible} {throughtiming} {true} {true} {network} {loopstart} {0} {disabled}
Display the ces-config profile for the configured CES circuit. zSH> get ces-config 1-12-5-0-ds1-2/ds0bundle vpi: --------------------------> {1} vci: --------------------------> {35} cas: --------------------------> {ds1esfcas} partial-fill: -----------------> {0}
MALC Configuration Guide
429
Configuring Voice
buf-max-size: -----------------> cell-loss-integration-period: -> ds0-bundle: ------------------->
{128} {2500} {7+8+9+10+11+12}
Adding unstructured E1 CES circuits To add a CES cross connection for an unstructured E1 CES circuit, repeat these configuration steps for each endpoint of the circuit. 1
Specify cross connect command with the desired settings. This command specifies an unstructured channel. Unstructured channels require the basis signaling type. No line type is specified so the e1unframed line type from the DS1-profile is used.
zSH> cc add uplink1/atm 0/61 1-6-1-0/ds1 vc 1/32 ds0 0/32 unstr
2
td 1
Display the configured cross connection.
zSH> cc show CES ATM VCL CC ATM VCL -------------------------------------------------------------------------uplink2/atm 0/61 Up 1 Up 1-6-1-0-ds1/atm 1/32 Up
3
Display the DS1 profile for the configured structured CES circuit. zSH> get ds1-profile 1-6-1-0/ds1 line-type: ----------------------> line-code: ----------------------> send-code: ----------------------> circuit-id: ---------------------> loopback-config: ----------------> signal-mode: --------------------> fdl: ----------------------------> dsx-line-length: ----------------> line-status_change-trap-enable: -> channelization: -----------------> ds1-mode: -----------------------> csu-line-length: ----------------> clock-source-eligible: ----------> transmit-clock-source: ----------> cell-scramble: ------------------> coset-polynomial: ---------------> protocol-emulation: -------------> signal-type: --------------------> ds1-group-number: ---------------> line-power: --------------------->
4
{e1unframed} {hdb3} {sendnocode} {e1} {noloop} {none} {fdlnone} {dsx0} {enabled} {disabled} {other} {csu00} {eligible} {throughtiming} {true} {true} {network} {loopstart} {0} {disabled}
Display the ces-config profile for the configured CES circuit. zSH> get ces-config 1-6-1-0-ds1-1/ds0bundle vpi: --------------------------> {1} vci: --------------------------> {32} cas: --------------------------> {basic} partial-fill: -----------------> {0} buf-max-size: -----------------> {128}
430
MALC Configuration Guide
Configuring CES connections
cell-loss-integration-period: -> {2500} ds0-bundle: -------------------> {0+1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+ 21+22+23+24+25+26+27+28+29+30+31}
Adding a structured E1 CES circuit with e1cas signaling To add a CES cross connection for a structured E1 CES circuit with e1cas signaling, repeat these configuration steps for each endpoint of the circuit. 1
Specify cross connect command with the desired settings. This example specifies 6 DS0s starting at DS0 1 in a structured circuit with e1case signaling type e1cas. The line type is unspecified so the e1 line type from the DS1-profile is used.
zSH> cc add uplink1/atm 0/62 1-6-2-0/ds1 vc 1/33 ds0 1/6 str e1cas td 1
2
Display the configured cross connections.
zSH> cc show CES ATM VCL CC ATM VCL -------------------------------------------------------------------------uplink2/atm 0/62 Up 2 Up 1-6-2-0-ds1/atm 1/33 Up
3
Display the DS1 profile for the configured structured CES circuit. zSH> get ds1-profile 1-6-2-0/ds1 line-type: ----------------------> line-code: ----------------------> send-code: ----------------------> circuit-id: ---------------------> loopback-config: ----------------> signal-mode: --------------------> fdl: ----------------------------> dsx-line-length: ----------------> line-status_change-trap-enable: -> channelization: -----------------> ds1-mode: -----------------------> csu-line-length: ----------------> clock-source-eligible: ----------> transmit-clock-source: ----------> cell-scramble: ------------------> coset-polynomial: ---------------> protocol-emulation: -------------> signal-type: --------------------> ds1-group-number: ---------------> line-power: --------------------->
4
{e1} {hdb3} {sendnocode} {e1} {noloop} {bitoriented} {fdlnone} {dsx0} {enabled} {disabled} {other} {csu00} {eligible} {throughtiming} {true} {true} {network} {loopstart} {0} {disabled}
Display the ces-config profile for the configured CES circuit. zSH> get ces-config 1-6-2-0-ds1-1/ds0bundle vpi: --------------------------> {1} vci: --------------------------> {33} cas: --------------------------> {e1cas} partial-fill: -----------------> {0}
MALC Configuration Guide
431
Configuring Voice
buf-max-size: -----------------> cell-loss-integration-period: -> ds0-bundle: ------------------->
{128} {2500} {1+2+3+4+5+6}
Adding a second cross connect to a structured E1 CES circuit with e1cas signaling To add a second CES cross connection for a structured E1 CES circuit with e1cas signaling, repeat these configuration steps for each endpoint of the circuit. 1
Specify cross connect command with the desired settings. This example specifies 6 DS0s starting at DS0 7 in a structured circuit using e1cas signaling type. The line type for secondary DS0 bundles must match the line type of the first bundle or be left unspecified so the e1 line type from the DS1-profile is used.
zSH> cc add uplink2/atm 0/63 1-6-3-0/ds1 vc 1/34 ds0 7/6 str e1cas td 1
2
Display the configured cross connections.
zSH> cc show CES ATM VCL CC ATM VCL -------------------------------------------------------------------------uplink2/atm 0/61 Up 1 Up 1-6-1-0-ds1/atm 1/32 Up uplink2/atm 0/62 Up 2 Up 1-6-2-0-ds1/atm 1/33 Up uplink2/atm 0/63 Up 3 Up 1-6-3-0-ds1/atm 1/34 Up
3
Display the DS1 profile for the configured structured CES circuit. zSH> get ds1-profile 1-6-3-0/ds1 line-type: ----------------------> line-code: ----------------------> send-code: ----------------------> circuit-id: ---------------------> loopback-config: ----------------> signal-mode: --------------------> fdl: ----------------------------> dsx-line-length: ----------------> line-status_change-trap-enable: -> channelization: -----------------> ds1-mode: -----------------------> csu-line-length: ----------------> clock-source-eligible: ----------> transmit-clock-source: ----------> cell-scramble: ------------------> coset-polynomial: ---------------> protocol-emulation: -------------> signal-type: --------------------> ds1-group-number: ---------------> line-power: --------------------->
432
MALC Configuration Guide
{e1} {hdb3} {sendnocode} {e1} {noloop} {bitoriented} {fdlnone} {dsx0} {enabled} {disabled} {other} {csu00} {eligible} {throughtiming} {true} {true} {network} {loopstart} {0} {disabled}
Configuring CES connections
4
Display the ces-config profile for the configured CES circuit. zSH> get ces-config 1-6-3-0-ds1-2/ds0bundle vpi: --------------------------> {1} vci: --------------------------> {34} cas: --------------------------> {e1cas} partial-fill: -----------------> {0} buf-max-size: -----------------> {128} cell-loss-integration-period: -> {2500} ds0-bundle: -------------------> {7+8+9+10+11+12}
Deleting CES over IP circuits To delete a configured CES over IP circuit, repeat this command on each circuit endpoint. This command deletes only one endpoint of a CES over IP circuit. Repeat this command on each endpoint to remove the entire circuit. ZSH>ces delete 1-7-1-0-ds1/atm ds0 1/6 static 192.168.100.101
Deleting cross connections and CES over ATM circuits To delete a configured CES over ATM cross connection, specify the delete cross connect command. This command uses either both sides of the cross connect or the cross connect number to remove the entire cross connection. Repeat this command on each circuit endpoint. zSH> cc delete uplink2/atm 0/61 1-6-1-0-ds1/atm 1/32 Delete complete zSH> cc delete cc 1 Delete complete
MALC Configuration Guide
433
Configuring Voice
Additional voice features This section describes additional voice settings you might need to configure, depending on your network.
Changing the jitter buffer The type and size of the jitter buffer in the MALC can be configured. The jitter buffer accommodates the packets received, so that the inter-arrival jitter of the packets received does not degrade the voice quality. Without a jitter buffer, some inter-arrival jitter changes would be late, which would have the same effect as lost packets. The jitter buffer also reorders the out-of-order packets received. Modify the following parameters in the voice-dsp-default-profile to change jitter buffer: Parameter
Description
jitter-buffer-type
There are two types of jitter algorithms: static and dynamic. Values: static A static jitter buffer does not change to compensate for inter-arrival jitter changes. Default jitter buffer type is static for VoATM applications. dynamic Allows the jitter buffer to grow and shrink as inter-arrival jitter changes. Default jitter buffer type is dynamic for VoIP applications.
jitter-buffer-size
Specifies the size of the jitter buffer. Values: 1 to 160 Note that changes to the jitter buffer are based on 5 ms frame sizes. For example: 1 to 5 = 5 ms 6 to 10 = 10 ms 11 to 15 = 15 ms 16 to 20 = 20 ms ... 146 to 150 = 150 ms 151 to 155 = 155 ms 156 to 160 = 160 ms Default: 10
Note: Any changes made to jitter buffer size and jitter buffer type take effect in the next call.
434
MALC Configuration Guide
Additional voice features
To change the type and size of the jitter buffer: zSH> update voice-dsp-default-profile 0 Please provide the following: [q]uit. redundancy-over-subscription-type: -> {high}: jitter-buffer-type: ----------------> {dynamic}: static jitter-buffer-size:----------------> {10}: 22 inter-arriv-jit-threshold: ---------> {80}: pkts-lost-threshold: ---------------> {600}: echo-cancellation-type: ------------> {g165echotl48}: silence-supression-type: -----------> {silsupoff}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Setting country-specific dialing features for VoIP Certain features on the POTS card are designed for use in telephone systems located outside of North America. These features are available on the MALC-POTS-TDM/PKT-48, MALC-POTS-GLB-TDM/PKT, and MALC-ADSL+POTS-PKT cards. For more information about this card, contact your Zhone Technologies sales representative. Caution: Changing the countryregion setting for the Global POTS card requires a system reboot. When you specify another country, such as South Africa, in the system profile, you have the option of modifying the following dialing parameters in the voice-system profile: –
hookflash-min-timer
–
hookflash-max-timer
–
pulse-inter-digit-timer
–
min-make-pulse-width
–
min-break-pulse-width
–
max-break-pulse-width
These options are read only after they have been set. To specify another country, such as South Africa, in the system profile: zSH> update system 0 Please provide the following: [q]uit. syscontact: -----------> {Zhone Global Services and Support 7001 Oakport Street Oakland Ca. (877) Zhone20 (946-6320) Fax (510)777-7113
[email protected]}: sysname: --------------> {malc-201}: syslocation: ----------> {Oakland}: enableauthtraps: ------> {disabled}: setserialno: ----------> {0}: zmsexists: ------------> {true}: zmsconnectionstatus: --> {inactive}:
MALC Configuration Guide
435
Configuring Voice
zmsipaddress: ---------> {192.168.89.12}: configsyncexists: -----> {false}: configsyncoverflow: ---> {false}: configsyncpriority: ---> {high}: configsyncaction: -----> {noaction}: configsyncfilename: ---> {192.168.175.201_4_1115314335218}: configsyncstatus: -----> {synccomplete}: configsyncuser: -------> {zmsftp}: configsyncpasswd: -----> {** private **}: ** read-only ** numshelves: -----------> {1}: shelvesarray: ---------> {}: numcards: -------------> {3}: ipaddress: ------------> {192.168.175.201}: alternateipaddress: ---> {0.0.0.0}: countryregion: --------> {us}: southafrica primaryclocksource: ---> {0/0/0/0/0}: ringsource: -----------> {internalringsourcelabel}: revertiveclocksource: -> {true}: voicebandwidthcheck: --> {false}: .................... countryregion changed to southafrica Load country's pulse dialing parameters in voice-system profile ? [y]es or [n]o: y voice-system profile updated with pulse dialing parameters for southafrica sysMinBreakPulseWidth... 35 ms, sysMaxBreakPulseWidth... 75 ms sysMinMakePulseWidth.... 100 ms, sysPulseInterDigitTimer. 25 ms minHookFlash............ 80 ms, maxHookFlash............ 230 ms southafrica uses a different PCM encoding type (ALAW) from us (MULAW). Please reboot the system for this change to take effect. Record updated.
Setting ring cadence and call progress parameters The MALC enables the ring cadence and other call progress parameters to be set for customized signal timing for VoIP MGCP and SIP calls. By default, ring cadences are set to standard United States settings. For Japan, other ring cadences are used that are not user-configurable. For other country-specific ring cadences, manually configure the ring cadences R0-R7 based on the country’s requirements. Table 31 lists the parameters that can be set. The following types of alert signal are used for on-hook signaling to wake up the caller ID device:
•
During Ringing The first ring is the alert signal, meaning the caller ID device is woken up to receive CLID data, when MALC provides the first ring.
•
Prior Ring with Dual Tone (DT) Wake Up (WU) A particular dual tone (2130Hz+2750Hz for 100ms) wakes up the caller ID CPE device for caller ID transmission. The tone and the caller ID signal are sent to prior to ringing.
436
MALC Configuration Guide
Additional voice features
•
Prior Ring with Ring Pulse (RP) Wake Up (WU) A short ring pulse (between 200ms and 300ms) wakes up the caller ID CPE device. Then, the caller ID signal transmission follows.
•
Prior Ring with Line Reversal (LR) Wake Up (WU) A line reversal (polarity change in DC voltage of the line, wakes up the caller ID device. Then, the caller ID signal transmission follows.
•
No Ring with Dual Tone (DT) Wake Up (WU) A particular dual tone (2130Hz+2750Hz for 100ms) wakes up the caller ID CPE device for caller ID transmission. Not associated with ringing.
•
No Ring with Ring Pules (RP) Wake Up (WU) A short ring pulse (between 200ms and 300ms) wakes up the caller ID CPE device. Not associated with ringing.
•
No Ring with Line Reversal (LR) Wake Up (WU) A line reversal (polarity change in DC voltage of the line, wakes up the caller ID device. Not associated with ringing.
Table 31: Ring cadence and call progress parameters Parameter
Description
callerid-dig-protocol
Identifies the subscriber line protocol used for signaling on-hook caller id information.Different countries define different caller id signaling protocols to support caller identification. Supported protocols are Frequency Shift Keying (FSK) and Dual-Tone Multi-Frequency (DTMF).
r0-ring-cadence to r7-ring-cadence
Customized ring cadences. Ring cadence is required for the L line package.
ring cadence
Normal ring cadence
ring-splash-cadence power-ring frequency
the frequency at which the sinusoidal voltage must travel down the twisted pair to make terminal equipment ring. Different countries define different electrical characteristics to make terminal equipment ring. The f##Hz setting corresponds to a power ring frequency of ## Hertz. For example, the f25Hz setting corresponds to a power ring frequency of 25 Hertz. The f33Point33Hz setting corresponds to a power ring frequency of 33.33 Hertz.
MALC Configuration Guide
437
Configuring Voice
Table 31: Ring cadence and call progress parameters
438
MALC Configuration Guide
Parameter
Description
clid-mode
The method of caller ID for on-hook caller ID. The Frequency Shift Keying (FSK) containing the Caller ID information is sent between the first and second ring pattern. For the dtas, rpas, and lr methods, the FSK containing the Caller ID information is sent before the first ring pattern. For the dtas method, the FSK is sent after the Dual Tone Alert Signal. For the rpas method, the FSK is sent after a Ring Pulse. For the lr method, the Line Reversal occurs first, then the Dual Tone Alert Signal, and finally the FSK is sent.
delay-before-clid-afterring
The delay between the first ringing pattern and the start of the transmission of the FSK containing the Caller ID information. It is only used when CIDMode is duringRingingETS. The default value is 550 ms.
delay-before-clid-afterdtas
The delay between the end of the Dual Tone Alert Signal (DT-AS) and the start of the transmission of the FSK containing the Caller ID information. It is only used when CIDMode is dtas or lr. The default value is 50 ms.
delay-before-clid-afterrpas
The delay between the end of the Ring Pulse Alert Signal (RP-AS) and the start of the transmission of the FSK containing the Caller ID information. It is only used when CIDMode is rpas. The default value is 650 ms.
delay-after-clid-beforering
The delay between the end of the complete transmission of the FSK containing the Caller ID information and the start of the first ring pattern. It is only used when CIDMode is dtas, rpas or lr. The default value is 250 ms.
delay-before-dtas-afterlr
The delay between the end of the Line Reversal and the start of the Dual Tone Alert Signal (DT-AS). It is only used when CIDMode is lr. The default value is 250 ms.
delay-before-vmwi-afte r-dtas
The delay between the end of the Dual Tone Alert Signal (DT-AS) and the start of the transmission of the FSK containing the VMWI information. It is only used when VmwiMode is dtas or lr. The default is 50 ms.
delay-before-vmwi-afte r-rpas
The delay between the end of the Ring Pulse Alert Signal (RP-AS) and the start of the transmission of the FSK containing the VMWI information. It is only used when VmwiMode is rpas. The default is 650 ms.
vmwi-delay-before-dtas -after-lr
The delay between the end of the Line Reversal and the start of the Dual Tone Alert Signal (DT-AS) for VMWI information. It is only used when VmwiMode is lr. The default is 250 ms.
Additional voice features
Customizing ring cadence and changing call progress parameters To customize ring cadence or change call progress parameters for SIP and MGCP VoIP calls. For MGCP systems, The MGCP switch determines which ring cadence to use. For SIP systems, normal ring cadence or ring splash are used. For SIP PLAR systems, the class 5 switch determines the ring cadences, directly for GR303 and indirectly for V5.2 calls. zSH> update voice-call-progress-config 0 Please provide the following: [q]uit. callerid-sig-protocol: -----------> {fsk}: dtmf r0-ring-cadence: -----------------> {r-2000:on-4000:off}: r1-ring-cadence: -----------------> {r-2000:on-4000:off}: r2-ring-cadence: -----------------> {r-800:on-400:off-800:on-4000:off}: r3-ring-cadence: -----------------> {r-400:on-200:off-400:on-200:off-800:on-4000:off}: r4-ring-cadence: -----------------> {r-300:on-200:off-1000:on-200:off-300:on-4000:off}: r5-ring-cadence: -----------------> {nr-500:on}: r6-ring-cadence: -----------------> {r-2000:on-4000:off}: r7-ring-cadence: -----------------> {r-2000:on-4000:off}: ring-cadence: --------------------> {r-2000:on-4000:off}: ring-splash-cadence: -------------> {nr-500:on}: power-ring-frequency: ------------> {f20hz}: clid-mode: -----------------------> {duringringingets}: delay-before-clid-after-ring: ----> {550}: delay-before-clid-after-dtas: ----> {50}: delay-before-clid-after-rpas: ----> {650}: delay-after-clid-before-ring: ----> {250}: delay-before-dtas-after-lr: ------> {250}: vmwi-mode: -----------------------> {dtasets}: delay-before-vmwi-after-dtas: ----> {50}: delay-before-Vmwi-after-rpas: ----> {650}: vmwi-delay-before-dtas-after-lr: -> {250}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Call progress tones for Canada The MALC now includes support for call progress tones and ring frequencies for Canada as specified in ITU E.180 Supp.2. Common call progress tones are dial tone, busy tone, call waiting tone, ring tone, and special information tone. To change the call progress tones to Canada: zSH> update system 0 Please provide the following: [q]uit. syscontact: -----------> {}: sysname: --------------> {MALC}: syslocation: ----------> {Oakland}: enableauthtraps: ------> {disabled}:
MALC Configuration Guide
439
Configuring Voice
setserialno: ----------> {0}: zmsexists: ------------> {false}: zmsconnectionstatus: --> {inactive}: zmsipaddress: ---------> {172.24.84.80}: configsyncexists: -----> {false}: configsyncoverflow: ---> {false}: configsyncpriority: ---> {high}: configsyncaction: -----> {noaction}: configsyncfilename: ---> {172.24.200.191_4_1129917707613}: configsyncstatus: -----> {synccomplete}: configsyncuser: -------> {cfgsync}: configsyncpasswd: -----> {** private **}: ** read-only ** numshelves: -----------> {1}: shelvesarray: ---------> {}: numcards: -------------> {3}: ipaddress: ------------> {172.24.200.191}: alternateipaddress: ---> {0.0.0.0}: countryregion: --------> {us}: canada primaryclocksource: ---> {0/0/0/0/0}: ringsource: -----------> {internalringsourcelabel}: revertiveclocksource: -> {true}: voicebandwidthcheck: --> {false}: ....................Save changes? [s]ave, [c]hange or [q]uit: s New record saved.
Emergency StandAlone (ESA) SIP and TDM support For VoIP SIP or SIP PLAR and POTS to GR303 voice connections, the MALC provides emergency calling services during network or equipment failures that cause a loss of connection to the configured TDM switch or SIP server. For VoIP SIP or SIP PLAR connections, the ESA feature enables numbers configured within ESA dialplans to communicate with any residences or businesses specified as the destination of the dialplans in an ESA cluster of MALC devices. For POTS to GR303 connections, the ESA feature enables numbers configured within the same dialplan using the same MALC device to communicate with any residences or businesses sharing that dialplan. Incoming calls from outside the ESA group and outgoing calls to numbers outside the SIP dialplan receive a fast-busy signal. When ESA is activated, call features, such as call waiting, are not supported. Note: After a loss of connection to the SIP server, there may be a delay up to 5 minutes before ESA notification is received and ESA features are accessible. There maybe a similar delay before resuming normal calling after the outage is restored.
440
MALC Configuration Guide
Emergency StandAlone (ESA) SIP and TDM support
Figure 51 illustrates ESA support for VoIP SIP or SIP PLAR connections. Figure 51: ESA for VoIP SIP or SIP PLAR connections IP Packet Transport
Figure 52 illustrates ESA support for POTS to GR303 or V5.2 connections.
MALC Configuration Guide
441
Configuring Voice
Figure 52: ESA for POTS to GR303 connections
ESA
Configuring VoIP ESA clusters To configure ESA clusters for VoIP connections, configure a VoIP server and create a dialplan for the VOIP server. Also, create an ESA dialplan for each of the MALC devices participating in the ESA cluster. For each ESA dialplan, enter the IP addresses of the desired MALC in the sip-ip-address field and change the dialplan-type to esa. Also, if desired, change the destination-name to the target MALC. When in ESA mode, the MALC sequentially checks the configured dialplans for a matching string starting with the lowest number to the highest number dialplan. If a match is found, the call connection process is initiated immediately. If a match is not found, the next sequential dialplan is checked until all configured dialplans have been checked. Calls with unmatched strings are then terminated. It is recommended to configure lower number dialplans for more frequently called nodes and higher number dialplans for less frequently called nodes. This example creates VoIP server 1/1 and creates SIP dialplan O for the VoIP server. SIP dialplan 1 is used on MALC 1 with IP address 172.24.94.219; SIP
442
MALC Configuration Guide
Emergency StandAlone (ESA) SIP and TDM support
dialplan 2 is used on MALC 2 with IP address 172.24.94.222. SIP dialplan 3 is used on MALC 3 with IP address 172.24.94.223.It also sets the match-string to ‘x’ to accept all numbers, the number of digits to 7, and the dialplan type to ESA. This dialplan enables ESA calls to connect to other subscribers within the same MALC. Additional dialplans are created for each of the neighboring MALC nodes. Note: A SIP dialplan of type normal should be configured and connected to a VoIP SIP server for non-ESA calls. zSH> new voip-server-entry 1/1 Please provide the following: [q]uit. zhoneVoipServerAddrType: ----------> {ipv4}: zhoneVoipServerAddr: --------------> {}: 172.16.60.1 zhoneVoipServerUdpPortNumber: -----> {5060}: zhoneVoipServerId: ----------------> {generic}: protocol: -------------------------> {sip}: sendCallProceedingTone: -----------> {false}: rtcpEnabled: ----------------------> {false}: rtcpPacketInterval: ---------------> {5000}: interdigitTimeOut: ----------------> {10}: ipTos: ----------------------------> {0}: systemDomainName: -----------------> {}: expires-invite-value: -------------> {3600} expires-register-value: -----------> {3600} expires-header-method: ------------> {register} session-expiration: ---------------> {0} session-min-SE: -------------------> {-606348325} session-caller-request-timer: -----> {no} session-callee-request-timer: -----> {no} session-caller-specify-refresher: -> {omit} session-callee-specify-refresher: -> {uac} omitsession-callee-specify-refresher:-> (uac) dtmf-mode:------------------------> (inband) .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created. zSH> new sip-dialplan 0 match-string: ----------------> sip-ip-address: --------------> destination-name: ------------> number-of-digits: ------------> prefix-strip: ----------------> prefix-add: ------------------> dialplan-type: ---------------> voip-server-entry-index: -----> override-interdigit-timeout: ->
{x} {0} 172.16.60.1 {}VoIP Server {0}7 {0} {} {normal} {0} 1 {0}
zSH> new sip-dialplan 1 match-string: ----------------> sip-ip-address: --------------> destination-name: ------------>
{x} {0} 172.24.94.219 {}MALC#1
MALC Configuration Guide
443
Configuring Voice
number-of-digits: ------------> prefix-strip: ----------------> prefix-add: ------------------> dialplan-type: ---------------> voip-server-entry-index: -----> override-interdigit-timeout: ->
{0}7 {0} {} {normal}esa {0} {0}
Create additional SIP dialplans for so ESA calls can connect to subscribers on other MALC devices. This dialplan allows ESA calls to connect to subscribers on MALC 2. zSH> new sip-dialplan 2 match-string: ----------------> sip-ip-address: --------------> destination-name: ------------> number-of-digits: ------------> prefix-strip: ----------------> prefix-add: ------------------> dialplan-type: ---------------> voip-server-entry-index: -----> override-interdigit-timeout: ->
{x} {0} 172.24.94.222 {} MALC#2 {0}7 {0} {} {normal}esa {0} {0}
This dialplan allows ESA calls to connect to subscribers on MALC 3. zSH> new sip-dialplan 3 match-string: ----------------> sip-ip-address: --------------> destination-name: ------------> number-of-digits: ------------> prefix-strip: ----------------> prefix-add: ------------------> dialplan-type: ---------------> voip-server-entry-index: -----> override-interdigit-timeout: ->
{x} {0} 172.24.94.223 {} MALC#3 {0}7 {0} {} {normal}esa {0} {0}
Configuring ESA for 911 calls To configure ESA for VoIP connections for 911 calls, create an ESA dialplan with a match-string of 911 and the IP address of the MALC shelf in the sip-ip-address field. Also, change the number of digits and prefix-strip to 3. The prefix-strip setting deletes the dialed 911 numbers. Enter the desired phone number to be called in the prefix-add field. This number must be a valid voicefxs line in the same MALC shelf. Change the dial-plan type to esa. This example creates a SIP dialplan called 911on the MALC with IP address 172.24.94.219. It replaces the dialed 911 number with the phone number 7281001 and changes the dialplan type to ESA. zSH> new sip-dialplan 911 match-string: ----------------> sip-ip-address: --------------> destination-name: ------------> number-of-digits: ------------>
444
MALC Configuration Guide
{}911 {0} 172.24.94.219 {} {0}3
Emergency StandAlone (ESA) SIP and TDM support
prefix-strip: ----------------> prefix-add: ------------------> dialplan-type: ---------------> voip-server-entry-index: -----> override-interdigit-timeout: ->
{0}3 {}7280004 {normal}esa {0} {0}
Verifying ESA To verify whether ESA support is in-use, enter the voice status command. This command lists the voice port, destination, call state, and ESA state along with other status information. zSH> voice status port term state ------------1-6-1-0/voicefxs UP 1-6-2-0/voicefxs UP 1-6-3-0/voicefxs UP
destination call state hook -------------------- ---VoIP:69:VoIP EndPtIdx-152 No call ON VoIP:69:VoIP EndPtIdx-154 No call ON GR303:IG-one:CRV-3 No call ON
ring ESA -----NoRing ON NoRing ON NoRing N/A
Configuring TDM ESA Voice add command for TDM ESA The voice add command allows the configuration of a Emergency Stand Alone (ESA) endpoint for POTS to GR303 voice connections. For these POTS voice connections, the MALC enables a VoIP endpoint for emergency calling services during network or equipment failures that cause a loss of connection to a configured GR-303 interface. The ESA feature enables numbers configured within the same ESA dialplan using the same MALC shelf to communicate with any residences or businesses sharing that dialplan. Incoming calls from outside the ESA group and outgoing calls to numbers outside the SIP dialplan receive a fast-busy signal. Syntax Voice add pots subscriberinterface gr303|v52 remoteinterface voip [ESAinterface] Example 1 zSH> voice add pots 1-4-4-0/voicefxs gr303 1/4 esa ethernet1/ip dn 7821004 Created subscriber-voice 1/378/5 Created subscriber-voice-pots 88 Created gr303-ig-crv 1/4 Created subscriber-voice-gr303 89 Created subscriber-voice 1/3/15 Created subscriber-voice-voip 90 zSH> zSH> voice show Subscriber end-point Remote end-point Voice Prof Id STA ----------------------------- ----------------------------- -------------- ---
MALC Configuration Guide
445
Configuring Voice
1-4-4-0/voicefxs GR303 one/4 1-4-4-0/voicefxs ethernet1/ip DN 7281004 Total number of voice connections : 2
1
1/378/5 1/3/15
ENA ENA
zSH> voice delete pots 1-4-4-0/voicefxs Deleted gr303-ig-crv 1/4 Deleted subscriber-voice 1/378/5 and its subscriber-voice-xxx profiles Deleted subscriber-voice 1/3/15 and its subscriber-voice-xxx profiles zSH> voice show Total number of voice connections: 0 zSH> Example 2 zSH> voice show esa ethernet1/ip DN 7281005 INPUT: profile type: subscriber-voice-voip logical address: LGId: 69 EndPtIdx: 103 profile address: 103 subscriber-voice INFO: voice-connection-type = VoIPTOPOTS voice-endpoint1-addr-index = 103 voice-endpoint2-addr-index = 101 voice-admin-status = Enabled subscriber-voice addr: subId: 1 LGId: 3 subVoiceId: 19 MATCHING: profile type: subscriber-voice-pots logical address: LGId: 195 PotsNumber: 1 profile address: 101 Notes The voice show and voice delete commands display and remove the ESA
endpoint along with the primary voice connections.
446
MALC Configuration Guide
T.38 fax
T.38 fax T.38 fax service enables fax messages to be transported across VoIP networks between G3 fax terminals. When configured for VoIP or SIP PLAR and T.38, MALC provides a T.38 fax relay service between two devices configured for the same VoIP protocol. If one side of the T.38 connection is not configured for T.38 support, the fax call reverts to g.711 pass through when this option is configured. Otherwise, the fax may not go through. By default, T.38 fax service is disabled. This section contains the following procedures;
•
T.38 fax using VoIP
•
T.38 fax using SIP PLAR to PSTN
•
T.38 using SIP PLAR to POTS fax Note: The MALC supports T.38 fax relay for SIP and MGCP. Please follow the procedure Configuring T.38 fax service, page 448 for configuring for SIP and MGCP. Note: The T.38 fax service can also be configured on VoIP connections using the voicegateway card. Note: When using T.38 fax, be sure that all the devices on the network which are involved in the T.38 transmission/reception are correctly configured for T.38 fax service.
T.38 fax using VoIP The MALC supports T.38 fax streams across a VoIP network. The MALC can be connected to another MALC or a VoIP IAD device. Figure 53 illustrates the T.38 fax streams using VoIP between MALC devices, and between a MALC and aVoIP IAD configured for T.38. Figure 53: SIP T.38 between MALC devices or VoIP IAD
VoIP
POTS
POTS Fax
Fax MALC
MALC
POTS
VoIP
POTS Fax
T.38 Fax Stream using VoIP
VoIP IAD MALC
Fax
T.38 Fax Stream using VoIP
MALC Configuration Guide
447
Configuring Voice
Configuring T.38 fax service The MALC supports T.38 service options for either t38udptl or t38none. The t38udptl options enables T.38 service using UDP IP packets. The t38none option disables the service. Note: The t38rtp option is currently not supported.
To enable T.38 fax service for VoIP connections: Specify the T.38 option when configuring a voice call with the voice add command for the POTS and VoIP connections. The subscriber-voice-voip profile settings are updated based on the command options. voice add pots 1-voice add pots 1-5-3-0/voicefxs voip 1/6 ethernet1/ip dn 5105330203 name 5105330203 codec g729a t38fax t38udptl reg 1
Caution: Avoid changes or deletions to the ip-interface-record profile after creating a voice connection on that interface. The subscriber-voice-voip profile can also be updated to enable the T.38 fax service. After updating the subscriber-voice-voip profile, the voice subscriber must be disabled and then re-enabled for the changes to be effective. zSH> list subscriber-voice subscriber-voice 1/2/26 subscriber-voice 1/2/27 2 entries found. zSH> update subscriber-voice 1/2/26 Please provide the following: [q]uit. voice-connection-type: --------> {voiptopots}: ** read-only ** voice-endpoint1-addr-index: ---> {52}: ** read-only ** voice-endpoint2-addr-index: ---> {51}: ** read-only ** voice-connection-description: -> {}: voice-admin-status: -----------> {enabled}: disabled huntgroup: --------------------> {false}: ** read-only ** features: ---------------------> {hookflash+onhooksignaling+callwait}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated. zSH> update subscriber-voice-voip 52 (the endpoint1-addr-index in subscriber-voice profile.) Please provide the following: [q]uit. voip-username: -------------> {9990002}: directory-number: ----------> {9990002}: ip-interface-index: --------> {ethernet2-2/ip}: preferred-codec: -----------> {g729a}: g711-fallback: -------------> {true}:
448
MALC Configuration Guide
T.38 fax
frames-per-packet: ---------> {4}: g726-byte-order: -----------> {bigendian}: voip-password: -------------> {}: voip-plar: -----------------> {false}:** read-only ** voip-plar-dest-ipaddrtype: -> {ipv4}: voip-plar-dest-ipaddr: -----> {}: voip-plar-udp-port: --------> {5060}: registration-server: -------> {0}: t38-fax: -------------------> {t38none}:t38udptl .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created. zSH> update subscriber-voice 1/2/26 Please provide the following: [q]uit. voice-connection-type: --------> {voiptopots}: ** read-only ** voice-endpoint1-addr-index: ---> {52}: ** read-only ** voice-endpoint2-addr-index: ---> {51}: ** read-only ** voice-connection-description: -> {}: voice-admin-status: -----------> {disabled}: enabled huntgroup: --------------------> {false}: ** read-only ** features: ---------------------> {hookflash+onhooksignaling+callwait}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
T.38 fax using SIP PLAR to PSTN The MALC supports T.38 fax streams across a VoIP network using SIP PLAR. In this configuration, the fax signal is sent to the MALC with the voicegateway card, and then forwarded to the PSTN as either an GR-303 or V5.2 fax signal. Figure 54 illustrates the T.38 fax stream using SIP PLAR between MALC devices with the voicegateway card connected to a class V switch and the PSTN. Figure 54: SIP PLAR T.38 between MALC and MALC Voicegateway to PSTN
VoIP
POTS
PSTN
Fax MALC
T.38 Fax Stream using SIP PLAR
MALC with voicegateway
Fax
Class V switch
Configuring T.38 using SIP PLAR to PSTN The MALC supports T.38 fax streams across a VoIP network using SIP PLAR. In this configuration, one MALC converts the POTS signal to VoIP
MALC Configuration Guide
449
Configuring Voice
and sends the T.38 fax signal across the VoIP network. Another MALC with the voicegateway card receives the T.38 signal and sends it to the Class V switch for processing across the PSTN. 1
On the MALC converting the POTS to VOIP signal, specify the T.38 option when configuring a voice call with the voice add command for the POTS and SIP connections. The subscriber-voice-voip profile settings are updated based on the command options.
voice add pots 1-voice add pots 1-5-3-0/voicefxs voip 1/6 ethernet1/ip dn 5105330203 name 5105330203 codec g729a t38fax t38udptl reg 1
2
On the MALC with the voicegateway card, use the voice add command to configure the connection for VoIP to GR303 or VoIP to V5.2. For GR303 connections:
voice add voip voip-1-3/ip dn 7350025 name m143-301 plar 172.24.200.143 t38fax t38udptl gr303 1/25
For V5.2 connections: voice add voip voip-1-3/ip dn 5107777428 name caller plar 172.24.200.143 t38fax t38udptl v52 4/99 type pots
T.38 using SIP PLAR to POTS fax The MALC supports T.38 fax streams across a VoIP network using SIP PLAR to another MALC device in the network. In this configuration, the fax signal is sent to the MALC with the voicegateway card, and then forwarded to the Class V switch, which routes the call back through the VoIP network to another MALC. Figure 55 illustrates the T.38 fax stream using SIP PLAR between a MALC connected to a MALC with the voicegateway card. When the signal reaches the MALC with the voicegateway card, the Class V switch routes the signal to another MALC in the VoIP network to process the POTS fax.
450
MALC Configuration Guide
T.38 fax
Figure 55: SIP PLAR T.38 between MALC and MALC Voicegateway to POTS fax
VoIP
POTS
GR303/ V5.2
Fax MALC
T.38 Fax Stream using SIP PLAR
Class V switch
MALC with voicegateway
MALC POTS
Fax
Configuring T.38 using SIP PLAR to POTS fax 1
On the MALC devices converting the POTS to VOIP signal, specify the T.38 option when configuring a voice call with the voice add command for the POTS and voice connections. The subscriber-voice-voip profile settings are updated based on the command options.
voice add pots 1-voice add pots 1-5-3-0/voicefxs voip 1/6 ethernet1/ip dn 5105330203 name 5105330203 codec g729a t38fax t38udptl reg 1
2
On the MALC with the voicegateway card, use the voice add command to configure the T.38 connection for VoIP to GR303 or VoIP to V5.2. For GR303 connections:
voice add voip voip-1-3/ip dn 7350025 name 7350025 plar 172.24.200.143 t38fax t38udptl gr303 1/25
For V5.2 connections: voice add voip voip-1-3/ip dn 5107777428 name 5107777428 plar 172.24.200.143 t38fax t38udptl v52 4/99 type pots
Caution: Avoid changes or deletions to the ip-interface-record profile after creating a voice connection on that interface.
MALC Configuration Guide
451
Configuring Voice
452
MALC Configuration Guide
8
CONFIGURING THE VOICE GATEWAY This chapter describes how to configure the MALC voice gateway. It includes:
•
Overview, page 453
•
Configuring voice gateway connections, page 455
•
POTS cards running POTS to VoIP in same chassis as voicegateway card, page 478
•
Configuring SIP-PRI media gateway, page 483
Overview The MALC voice gateway card (VG-T1/E1-32-2S) enables voice connections from an ATM and IP voice network to a TDM local exchange switch using GR-303 or V5.2 protocols. The following connection types are supported.
•
Voice over IP: SIP-PLAR to GR-303 or V5.2
•
Voice over ATM: –
BLES to GR-303 or V5.2
–
ELCP to V5.2
Figure 56: Voice gateway overview
TDM GR303 V5.2
Packet
Local Exchange Switch MALC with voice gateway
MALC Configuration Guide
453
Configuring the Voice Gateway
The MALC voice gateway card can also serve as an aggregation point for multiple downstream MALC or IAD systems aggregating multiple services (PON, SHDSL, T1/E1 ATM) or multiple voice lines on residential services (ADSL, ADSL2+, VDSL) over a single uplink connection. All the ATM/IP uplink cards can be used to connect VoIP traffic to the voice gateway card. Figure 57: Voice gateway aggregation point
IAD
IP Network MALC with voice gateway
Local Exchange Switch
The MALC now supports a feature bit used to optimize voice gateway performance. When this feature bit is enabled, the MALC supports up to 4 redundant voice gateway cards.
454
MALC Configuration Guide
Configuring voice gateway connections
Configuring voice gateway connections The voice gateway card configuration involves validating voice configuration prerequisites, configuring the voice VPIs and VCIs as required, and adding the desired voice connections. Procedures for verifying the voice connections are also provided. These configuration procedures require the MALC uplink and voice gateway cards to be physically installed and running in the current system with properly configured card profiles. Note: The voice gateway card requires MALC software version 1.11.1 or higher on the uplink cards. This section contains procedures for:
•
Verifying voice configuration prerequisites on page 455
•
VoIP to voice gateway connections on page 456
•
Subtended MALC POTS VoIP voice gateway connections on page 462
•
AAL2 voice gateway connections on page 464
•
Subtended MALC ISDN or POTS voice gateway connections on page 475
Verifying voice configuration prerequisites Before configuring the voice gateway connection, use the following procedures to ensure that the configuration prerequisites have been configured. 1
Use the slots command to verify the desired uplink and voice gateway card installation and status. This example shows the Uplink-T1/E1-ATM/ TDM/IP-16 card running in slot 1 and the MALC voice gateway card running in slot 3. Other line cards can be inserted and running in other slots as desired. zSH> slots 1: MALC UPLINK T1/E1 TDMF (RUNNING) 3: MALC T1E132VG (RUNNING) 13: MALC GSHDSL (RUNNING) 17: MALC ADSL + POTS AC6 (RUNNING)
2
Check the system settings to ensure the appropriate country coding and other system-level settings are configured. See Updating system settings on page 386for details.
3
Create and activate a V5.2 or GR-303 interface group (IG). See Configuring GR-303 or V5.2 Interface Groups on page 213 for details. Note: Up to 8 interface groups can be supported on each voice gateway card.
MALC Configuration Guide
455
Configuring the Voice Gateway
4
Ensure there is an active system clock source. See the MALC Hardware Installation Guide.
5
Create a new atm-traf-descr with a unique index for a voice connection. For ELCP to V5.2 voice connections, both the VPL and VCL traffic descriptors are required. See Configuring ATM on page 193 for more information on ATM traffic descriptors and parameters.
zSH> new atm-traf-descr 1 index can be any value Please provide the following: [q]uit. td_type: -----------------> {atmNoClpNoScr}: atmClpNoTaggingScrCdvt td_param1: ---------------> {0}: 4826 PCR . td_param2: ---------------> {0}: 4825 SCR td_param3: ---------------> {0}: 20 MBS td_param4: ---------------> {0}: 15000 CDVT td_param5: ---------------> {0}: cac-divider: -------------> {1}: 10 td_service_category: -----> {ubr}: rtvbr for voice td_frame_discard: --------> {false}: usage-parameter-control: -> {true}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
VoIP to voice gateway connections This section contains the following procedures:
•
Overview on page 456
•
Creating an unnumbered interface for VoIP on page 457
•
Configuring voice gateway host for VoIP connections
•
Configuring voice connections for VoIP to GR303
•
Configuring voice connections for VoIP to V5.2
•
Configuring T.38 service on the voicegateway connections
•
Deleting voice gateway host and voice connection
Overview For VoIP to TDM voice connections, the MALC voice gateway card supports multiple incoming VoIP voice lines going out a single TDM connection to a local voice switch.
456
MALC Configuration Guide
Configuring voice gateway connections
Figure 58: Voice gateway VoIP to TDM
IP Network MALC with voice gateway
Local Exchange Switch
For VoIP to TDM connections on the voice gateway card, VoIP packets destined for the voice gateway card enter through one of the MALC uplink card interfaces (GigE, SONET, IP) and are terminated on the voice gateway card. The voice signal is converted to TDM T1/E1 channels and sent to the local switch for TDM voice processing. For traffic coming from the local switch, the TDM voice signals are converted to VoIP packets by the voice gateway card and routed back out the MALC uplink card to the configured VoIP destination. Configuring a VoIP to TDM voice gateway connection involves configuring the voice gateway for a VoIP host and adding a VoIP to TDM voice connection. Note: Only one IP interface can be configured on the voice gateway card.
Creating an unnumbered interface for VoIP Before configuring a VoIP to TDM connection, create a new ip-interface-record and unnumbered interface. 1
To create an IP interface record, use the new ip-interface-record command. zSH> new ip-interface-record vg/ip vpi: ---------------> {0}: vci: ---------------> {0}: rdindex: -----------> {1}: dhcp: --------------> {none}: ** read-only ** addr: --------------> {0.0.0.0}: 10.10.10.1 netmask: -----------> {0.0.0.0}: 255.255.255.0 bcastaddr: ---------> {0.0.0.0}: 10.10.10.255 destaddr: ----------> {0.0.0.0}: farendaddr: --------> {0.0.0.0}: mru: ---------------> {1500}: reasmmaxsize: ------> {0}: ingressfiltername: -> {}: egressfiltername: --> {}: pointtopoint: ------> {no}: mcastenabled: ------> {yes}:
MALC Configuration Guide
457
Configuring the Voice Gateway
ipfwdenabled: ------> {yes}: mcastfwdenabled: ---> {yes}: natenabled: --------> {no}: bcastenabled: ------> {yes}: ingressfilterid: ---> {0}: egressfilterid: ----> {0}: ipaddrdynamic: -----> {static}: dhcpserverenable: --> {false}: subnetgroup: -------> {0}: unnumberedindex: ---> {0}: mcastcontrollist: --> {}: vlanid: ------------> {0}: maxVideoStreams: ---> {0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Could not find an appropropriate interface on which to bind the IP record. Could not automatically bind this IP Interface New record saved.
2
To create an unnumbered IP interface record, use the new ip-unnumbered-record command. zSH> new ip-unnumbered-record 1 ipUnnumberedInterfaceName: -> { }: vg/ip .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Configuring voice gateway host for VoIP connections The voice gateway VoIP to GR-303 and V5.2 configurations require configuring the voice gateway as an AAL5 proxy on the voice gateway card before adding a VoIP to GR-303 or VoIP to V5.2 voice connection. 1
Locate the if-translate record. zSH> list if-translate 1-3-1-0/aal5proxy if-translate 1-3-1-0/aal5proxy 1 entry found.
2
Verify that the desired ATM traffic descriptor is configured. zSH> list atm-traf-descr atm-traf-descr 1 1 entry found.
3
Use the voicegateway add command to create the voice gateway host using the available physical interface or slot number of the voicegateway card and traffic descriptor. zSH> voicegateway add 3 td 1 10.10.10.2
458
MALC Configuration Guide
Configuring voice gateway connections
zSH> voicegateway add 1-3-1-0/aal5proxy td 1 10.10.10.2
This adds an IP host on the voice gateway card in slot 3 and assigns the IP address 10.10.10.2. The connection uses traffic descriptor 1 and an AAL5 physical interface of aal5proxy. Use the new voip-server-entry command to add the voip-server-entry 255/255 for SIP binding group and multiple SIP server support if that voip-server-entry profile does not already exist. Note: The voicegateway add command automatically creates the required ATM VCLs if they do not already exist. 4
Use the voicegateway show command to display the voice gateway host using the slot number of the voicegateway card or the AAL5 physical interface.
zSH> voicegateway show 3 Rd/Address Interface Group T Host Address -----------------------------------------------------------------------1 10.10.10.1 1-3-1-0-aal5proxy-0-32 0/32 0 S 10.10.10.2 zSH> voicegateway show 1-3-1-0/aal5proxy Rd/Address Interface Group T Host Address ------------------------------------------------------------------------1 10.10.10.1 1-3-1-0-aal5proxy-0-32 0/32 0 S 10.10.10.2
Configuring voice connections for VoIP to GR303 After configuring the voice gateway as an AAL5 proxy on the voice gateway card, the voice connection for VoIP to GR-303 requires adding a VoIP to GR-303 voice connection. This example uses the IP interface voip-1-3/ip with the number 735-0025, name m143-301, destination IP address 172.24.200.143, GR-303 switch protocol, IG 1 and CRV 25. This command also sets the VoIP password in the subscriber-voice-voip profile to password. 1
Use the voice add command to add a VoIP to GR-303 voice connection between the voice gateway card and the switch. An optional password is used.
zSH> voice add voip voip-1-3/ip dn 7350025 name m143-301 plar 172.24.200.143 gr303 1/25 pw password Created subscriber-voice 1/330/48 Created subscriber-voice-voip 173 Created gr303-ig-crv 1/25 Created subscriber-voice-gr303 174
MALC Configuration Guide
459
Configuring the Voice Gateway
2
Display the configured voice connection with the voice show command.
ZSH>voice show Subscriber end-point Remote end-point Voice Prof Id STA ---------------------------- ----------------------------- -------------voip-1-3/ip DN 7350025 GR303 one/25 1/330/25 ENA Total number of voice connections : 1
Configuring voice connections for VoIP to V5.2 After configuring the voice gateway as an AAL5 proxy on the voice gateway card, the voice connection VoIP to V5.2 requires adding a VoIP to V5.2 voice connection. 1
Use the voice add command to add a VoIP to V5.2 voice connection between the voice gateway card and the switch using IG 4 and user port 99. By default, the registration server is set to 0 and the preferred codec is G.711a. An option password is used.
zSH> voice add voip voip-1-3/ip dn 5107777428 name caller pw password v52 4/ 99 type pots Created subscriber 1/2 Created subscriber-voice 1/2/1 Created subscriber-voice-voip 11 Created v52-user-port 4/99/2 Created subscriber-voice-v52 12
2
Display the configured voice connection with the voice show command.
zSH> voice show Subscriber end-point Remote end-point Voice Prof Id STA ------------------------------ ------------------------ -------------- --voip-1-3/ip DN 5107777428 V52 four/99/pots 1/2/1 ENA Total number of voice connections : 1
Configuring T.38 service on the voicegateway connections Specify the T.38 option when configuring a voice call with the voice add command. The subscriber-voice-voip profile settings are updated based on the command options. voice add voip voip-1-3/ip dn 7350025 name m143-301 plar 172.24.200.143 t38fax t38udptl gr303 1/25 voice add voip voip-1-3/ip dn 5107777428 name caller plar 172.24.200.143 t38fax t38udptl v52 4/99 type pots
Caution: Avoid changes or deletions to the ip-interface-record profile after creating a voice connection on that interface.
460
MALC Configuration Guide
Configuring voice gateway connections
The subscriber-voice-voip profile can also be updated to enable the T.38 fax service. After updating the subscriber-voice-voip profile, the voice subscriber must be disabled and then re-enabled for the changes to be effective. zSH> list subscriber-voice subscriber-voice 1/2/26 subscriber-voice 1/2/27 2 entries found. zSH> update subscriber-voice 1/2/26 Please provide the following: [q]uit. voice-connection-type: --------> {voiptopots}: ** read-only ** voice-endpoint1-addr-index: ---> {52}: ** read-only ** voice-endpoint2-addr-index: ---> {51}: ** read-only ** voice-connection-description: -> {}: voice-admin-status: -----------> {enabled}: disabled huntgroup: --------------------> {false}: ** read-only ** features: ---------------------> {hookflash+onhooksignaling+callwait}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated. zSH> update subscriber-voice-voip 52 (the endpoint1-addr-index in subscriber-voice profile.) Please provide the following: [q]uit. voip-username: -------------> {9990002}: directory-number: ----------> {9990002}: ip-interface-index: --------> {ethernet2-2/ip}: preferred-codec: -----------> {g729a}: g711-fallback: -------------> {true}: frames-per-packet: ---------> {4}: g726-byte-order: -----------> {bigendian}: voip-password: -------------> {}: voip-plar: -----------------> {false}:** read-only ** voip-plar-dest-ipaddrtype: -> {ipv4}: voip-plar-dest-ipaddr: -----> {}: voip-plar-udp-port: --------> {5060}: registration-server: -------> {0}: t38-fax: -------------------> {t38none}:t38udptl .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created. zSH> update subscriber-voice 1/2/26 Please provide the following: [q]uit. voice-connection-type: --------> {voiptopots}: ** read-only ** voice-endpoint1-addr-index: ---> {52}: ** read-only ** voice-endpoint2-addr-index: ---> {51}: ** read-only ** voice-connection-description: -> {}: voice-admin-status: -----------> {disabled}: enabled huntgroup: --------------------> {false}: ** read-only ** features: ---------------------> {hookflash+onhooksignaling+callwait}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
MALC Configuration Guide
461
Configuring the Voice Gateway
Deleting voice gateway host and voice connection To remove the configured voice gateway connection, use the voicegateway delete command with the slot number of the voicegateway card or the AAL5 physical interface. zSH> voicegateway delete 3 zSH> voicegateway delete 1-3-1-0/aal5proxy
Deleting voice connection To remove the configured voice connection, use the voice delete command. Do not attempt to manually remove or edit the related subscriber-voice profiles. zSH> voice delete voip ethernet1/ip DN 5107777428 Deleted v52-user-port 4/99/2 Deleted subscriber-voice 1/2/1 and its subscriber-voice-xxx profiles
Subtended MALC POTS VoIP voice gateway connections This section contains the following procedures:
•
Overview on page 462
•
Configuring subtended POTS to VoIP voice connection on page 463
•
Deleting subtended voice connection on page 464
Overview Using a subtended MALC, with an optional IAD, enables the MALC voice gateway card to function as an aggregation point for multiple downstream systems aggregating multiple services (PON, SHDSL, T1/E1 ATM) or multiple voice lines on residential services (ADSL, ADSL2+, VDSL) over a single MALC uplink and voice gateway connection.
462
MALC Configuration Guide
Configuring voice gateway connections
Figure 59: Voice gateway VoIP to TDM with subtended IAD
IAD
IP Network MALC with voice gateway
Local Exchange Switch
In a subtended MALC configuration, subscriber traffic passes through the subtended MALC’s uplink card and is sent as VoIP packets to the MALC with the voice gateway card. VoIP packets destined for the voice gateway card enter through one of the MALC uplink card interfaces (GigE, SONET, IP) and are terminated on the voice gateway card. The voice signal is converted to TDM T1/E1 channels and sent to the local switch for TDM voice processing. For traffic coming from the local switch, the TDM voice signals are converted to VoIP packets by the voice gateway card and routed back out the MALC’s uplink card, sent to the subtended MALC, and then routed to the configured VoIP destination. To configure the voice gateway card with a downstream MALC system, first ensure the voice gateway card is configured for a VoIP to TDM connection. See VoIP to voice gateway connections on page 456. Then, use the voice add command to add a POTS to VoIP voice connection on the subtended MALC. This voice connection transports the voice signals between the subtended MALC and the VoIP interface on the voice gateway card.
Configuring subtended POTS to VoIP voice connection Configure a POTS to VoIP voice connection on the subtended MALC to send its VoIP signals to the voice gateway card. The subtended MALC must have a working Ethernet IP connection and an available IP route to the voice gateway IP address. Also, a subscriber line POTS card should be installed with the required ports enabled. 1
Create a non-subscriber VCL 0/34 on the MALC uplink card. The VCL 0/ 34 is required for internal voice processing and must be configured once for each uplink card that will connect to a voice connection from a subtended MALC. zSH> new atm-vcl 1-1-2-0-dspproxy/atm/0/34 vpi: -----------------------------> {0}
MALC Configuration Guide
463
Configuring the Voice Gateway
vci: -----------------------------> admin_status: --------------------> receive_traffic_descr_index: -----> transmit_traffic_descr_index: ----> vcc_aal_type: --------------------> vcc_aal5_cpcs_transmit_sdu_size: -> vcc_aal5_cpcs_receive_sdu_size: --> vcc_aal5_encaps_type: ------------> {llcencapsulation} vcl_cast_type: -------------------> vcl_conn_kind: -------------------> fault-detection-type: ------------> traffic-container-index: --------->
{34} {up} {1} {1} {aal5} {9188} {9188}
{p2p} {pvc} {disabled} {0}
2
Reboot the MALC.
3
Use the voice add command on the subtended MALC to add the POTS to VoIP connection. This example connects a POTS subscriber with interface 1-3-1-0/voicefxs to VoIP interface ethernet1/ip with number 735-0025, name of m143-301, and destination IP address 10.177.1.2.
zSH> voice add pots 1-3-1-0/voicefxs voip ethernet1/ip dn 7350025 name m143-301 plar 10.177.1.2 Created subscriber-voice 1/2/1 Created subscriber-voice-pots 1004 Created subscriber-voice-voip 1005
4
Verify the voice connection with the voice show command.
zSH> voice show Subscriber end-point Remote end-point Voice Prof Id STA ------------------------------ ------------------------------ -------------- --1-3-1-0/voicefxs ethernet1/ip DN 7350025 1/2/1 ENA Total number of voice connections : 1
Deleting subtended voice connection To remove the configured voice connection, use the voice delete command. zSH> voice delete pots 1-3-1-0/voicefxs Deleted subscriber-voice 1/2/1 and its subscriber-voice-xxx profiles
AAL2 voice gateway connections This section contains the following information:
464
MALC Configuration Guide
•
Overview on page 465
•
Configuring voice gateway for VoATM BLES to GR-303 (VC-switched) on page 467
•
Configuring voice gateway for VoATM BLES to GR303 (VP-switched) on page 468
Configuring voice gateway connections
•
Configuring voice gateway for VoATM BLES to V5.2 (VC-switched) on page 469
•
Configuring voice gateway for VoATM BLES to V5.2 (VP-switched) on page 470
•
Configuring voice gateway for VoATM ELCP to V5.2 (VC-switched) ISDN signal on page 471
•
Configuring voice gateway for VoATM ELCP to V5.2 (VP-switched) on page 473
•
Configuring subtended AAL2 voice connection on page 476
Overview For VoATM to TDM voice connections, the MALC voice gateway supports multiple ATM voice lines over the voice gateway card to a local TDM (GR-303 or V5.2) switch. Figure 60: Voice gateway VoATM to TDM
ATM MALC with voice gateway
Local Exchange Switch
For VoATM traffic, ATM traffic destined for the voice gateway card enters through one of the MALC uplink card’s ATM interfaces and is terminated on the voice gateway card. The ATM voice signals are converted to TDM T1/E1 channels and sent to the local TDM switch for processing. For traffic coming from the local switch, the TDM voice signals are converted to VoATM signals by the voice gateway card and sent back out the MALC uplink card to configured ATM destination. Note: The voice gateway card does not support connection admission control (CAC). All uplink cards can be used for connecting VoATM traffic to the voice gateway card. The voice gateway card supports VoATM BLES to GR-303 or V5.2 and VoATM ELCP to V5.2 connection types.
MALC Configuration Guide
465
Configuring the Voice Gateway
The MALC voice gateway card enables a combination of VP and VC switching for flexible VoATM voice gateway configurations and maximum subscriber support.
•
VC-switched In VC-switching, VCs are switched independently of each other based on VPI and VCI value. The VP range of 0-7 is reserved for VC-switching on the voice gateway card. The VCs in each VC-switched VP must start with 32 and can contain any number up to the maximum number of 448 VCs. The maximum number of VCs that can be allocated to an individual VC-switched VPI is determined by the zhoneAtmVpiMaxVci parameter in the atm-vpi profile.
•
VP-switched In VP-switching, VCs are switched collectively in groups or Virtual Paths (VPs) based on VPI value. The VP range of 16 to 63 is reserved for VP-switching on the voice gateway card. Up to 48 VPs can be switched from the MALC uplink card to a voice gateway card. The VCs in each VP-switched VP must start with 32 and can contain any number up to the maximum number of 7,680 VCs. The maximum VCI value that can be allocated to an individual VP-switched VP is determined by the zhoneAtmMaxVciPerVp parameter in the atm-vpi profile. For example, if this parameter is set to 1023 for VPI 16, a VC with VPI/VCI 16/1024 will not be allowed even if it is the only VC configured on the voice gateway card. The sum of this parameter in all VP-switched atm-vpi profiles on the voice gateway card cannot exceed 7,680. The voice vpladd command automatically increments the assigned VP starting at 16.
Figure 61 illustrates the voice gateway support for VC-switching and VP-switching.
466
MALC Configuration Guide
Configuring voice gateway connections
Figure 61: Voice gateway VoATM VP/VC support
VP0-7 (VC Switched) VP0
VC32-x VC32-x
VP ... VP7
VC32-x
Maximum number of VCs in each VC-switched VP is set
Total VCs in VC-switched VPs is 448.
using the atm-vpi profile paramter ZhoneAtmVpiMaxVci.
TDM
VP16-63 (VP Switched) VC32-x VC32-x
VP16 VP ... VP63
VC32-x Total VCs in VP-switched VP is 7680
Maximum VCI value that can be allocated in each VP-switched VP is set using the atm-vpi profile paramter ZhoneAtmMaxVciPerVp.
Total VCs supported on the voice gateway card is 8128.
The voice gateway card supports up to 8,128 virtual circuits (VCs). Each VC represents a single IAD and supports from 1 to 8 physical or logical telephones. With 32 DS1 ports, a maximum of 768 (32DS1s x 24 DS0’s) voice subscribers are supported. With 32 E1 ports, a maximum or 960 (32 E1’s x 31 DS0’s) voice subscribers are supported. For VC-switching, configuring the voice gateway AAL2 voice connection involves using the voicegateway add command to add the required VP, VC, and AAL2 to GR-303 or V5.2 voice connection on the voice gateway card. For VP-switching, configuring the voice gateway AAL2 voice connection involves using the following commands:
•
voice addvpi command builds the VPs on the uplink card interface and voice gateway aal2proxy.
•
voice addvpl command builds the VP links and ATM cross connect
•
voice add command builds the shared VC and establishes the AAL2 to GR-303 or V5.2 voice connection on the voice gateway card.
Configuring voice gateway for VoATM BLES to GR-303 (VC-switched) This procedure explains how to configure a VC-switched VoATM BLES to GR-303 voice connection on the voice gateway card. 1
Use the voice add command on the voice gateway card to add the voice connection for the specified VC and CID to the GR-303 IG. zSH> voice add aal2 1-4-1-0/ds1 vc 0/139 cid 48 gr303 1/131 Created subscriber-voice 1/266/6 Created aal2-cid-profile 340/0/32/48
MALC Configuration Guide
467
Configuring the Voice Gateway
Created subscriber-voice-aal2 171 Created gr303-ig-crv 1/131 Created subscriber-voice-gr303 172
This adds an ATM to GR-303 voice connection with the AAL2 interface 1-4-1-0 and assigns the virtual connection VPI 0, VCI 139 and CID 48. The TDM connection uses GR-303 protocol and interface group 1 with CRV 131. 2
Display the ATM to GR-303 voice connection with the voice show command.
zSH> voice show Subscriber end-point Remote end-point Voice Prof Id STA -------------------------- --------------------------- ------------- --1-4-1-0/ds1 VC 0/139 CID 48 GR303 one/131 1/266/6 ENA Total number of voice connections : 1 zSH>
Configuring voice gateway for VoATM BLES to GR303 (VP-switched) This procedure explains how to configure a VP-switched VoATM BLES to V5.2 voice connection on the voice gateway card. Use the voice vpiadd and voice vpladd commands to build the ATM VP between the uplink card VP and the voice gateway card aal2proxy using the same VC. Then, use the voice add command to build the VCL on the aal2proxy with the same VC that was configured on the uplink card. The allowed VP range on aal2proxy is 16 to 63. Note: In addition to the GR-303 interface group, the required VPL traffic descriptor and VCL traffic descriptor must be built before performing this procedure. 1
Use the voice vpiadd command to build the ATM VPI for the uplink card and the voice gateway card aal2proxy. zSH> voice vpiadd uplink/atm 0 gr303 1 501 Created atm-vpi 1-3-3-0-aal2proxy/atm/16 Created atm-vpi uplink1/atm/0
This example uses the uplink interface uplink/atm with VP 0. The MALC uplink cards support up 256 (0-255) VPs. The voice call type is GR-303 with IG 1. The maximum number of VCs allocated for the specified VP-switched VPI is 512. 2
Reboot the system to install the configured VPIs. zSH>systemreboot
3
Use the voice vpladd command to build the VPLs and cross connects between the uplink card and aal2proxy. zSH>voice vpladd uplink/atm 0 td 1/1 gr303 1
468
MALC Configuration Guide
Configuring voice gateway connections
Created atm-vpl 1-3-3-0-aal2proxy/atm/16 Created atm-vpl uplink1/atm/0 Created atm-cc 6
This command builds atm-vpl uplink1/atm/0 on the uplink card using traffic descriptor tx and rx 1/1 with atm-vpl 1-3-3-0-aal2proxy/atm/16 on the voice gateway card. VP 16 is the first available VP in the allowed VP range on the voice gateway card. 4
Use the voice add command on the voice gateway card to add the voice connection for the desired VC and CID to the GR-303 IG. zSH> voice add atm uplink1/atm vp 0/101 td 1/1 cid 1 alaw gr303 1/1 type pots Created subscriber-voice 1/51/2 Created aal2-cid 109/16/101/1/1 Created subscriber-voice-aal2 15 Created gr303-cid 1/1/2 Created subscriber-voice-gr303 16
This command creates a POTS to GR-303 voice connection between the uplink interface uplink1 with VP 0 and VC 101 to the voice gateway card CID 1 with VP 16 and shared VC 101. 5
Display the ATM to GR-303 voice connection with the voice show command.
zSH> voice show Subscriber end-point Remote end-point Voice Prof Id STA -------------------------- --------------------------- ------------- --1-1-1-0/sonet VC 0/101 port 1 GR303 100 100/11/35/1 ENA Total number of voice connections : 1 zSH>
Configuring voice gateway for VoATM BLES to V5.2 (VC-switched) This procedure explains how to configure a VC-switched VoATM BLES to V5.2 voice connection on the voice gateway card. 1
Use the voice add command on the voice gateway card to add the voice connection for the specified VC and user port to the V5.2 IG.
zSH> voice add aal2 uplink1/atm vc 6/39 td 1/1 cid 16 v52 4/39 type pots Created subscriber 1/57 Created subscriber-voice 1/57/1 Created atm-vcl uplink1/atm/6/39 Created atm-vcl 1-5-3-0-aal2proxy/atm/0/32 Created atm-cc 2 Created aal2-vcl-profile 1-5-3-0-aal2proxy/atm/0/32 Created aal2-cid-profile 99/0/32/16Created subscriber-voice-aal2 1 Created v52-user-port 4/39/2 Created subscriber-voice-v52 2
MALC Configuration Guide
469
Configuring the Voice Gateway
This adds an ATM to V5.2 voice connection with the uplink1 AAL2 interface and assigns the virtual connection VPI 6, VCI 39 and CID 16. 2
Display the ATM to V5.2 voice connection with the voice show command.
zSH> voice show Subscriber end-point Remote end-point Voice Prof Id STA ------------------------------ ------------------------ -------------- --1-1-1-0/sonet VC 6/39 CID 16 V52 four/39/pots 1/57/1 ENA
3
Delete the voice connection. zSH> voice delete aal2 1-1-1-0/sonet VC 6/39 CID 16 Deleted aal2-cid-profile 99/0/32/16 Deleted v52-user-port 4/39/2 Deleted subscriber-voice 1/57/1 and its subscriber-voice-xxx profiles Deleted atm-vcl 99/0/32 Deleted atm-vcl 15/6/39 Deleted atm-cc 2
Configuring voice gateway for VoATM BLES to V5.2 (VP-switched) This procedure explains how to configure a VoATM BLES to V5.2 voice connection on the voice gateway card. Use the voice vpiadd and voice vpladd commands to build the ATM VP between the uplink card VP and the voice gateway card aal2proxy using the same VC. Then, use the voice add command to build the VCL on the aal2proxy using the same VC that was configured on the uplink card. The allowed VP range on aal2proxy is 16 to 63. Note: In addition to the V5.2 interface group, the required VPL traffic descriptor and VCL traffic descriptor for ELCP lines must be built before performing this procedure. 1
Use the voice vpi add command to build the ATM VPI for the uplink card VP and the voice gateway card aal2proxy. zSH>voice vpiadd uplink/atm 0 v52 1 2000 Created atm-vpi 1-3-3-0-aal2proxy/atm/16 Created atm-vpi uplink1/atm/0
This example uses the uplink interface uplink/atm with VP 0. The MALC uplink cards support up 256 (0-255) VPs. The voice call type is V5.2 with IG 1. The maximum VCs allocated to the specified VP-switched VPI is 2048. 2
Reboot the system to install the configured VPIs. zSH>systemreboot
3
470
MALC Configuration Guide
Use the voice vpladd command to build the VPLs and cross connects.
Configuring voice gateway connections
zSH>voice vpladd uplink/atm 0 td 1/1 v52 1 Created atm-vpl 1-3-3-0-aal2proxy/atm/16 Created atm-vpl uplink1/atm/0 Created atm-cc 6
This command builds atm-vpl uplink1/atm/0 on the uplink card using traffic descriptor 1 and atm-vpl 1-3-3-0-aal2proxy/atm/16 on the voice gateway card. VP 16 is the first available VP in the allowed VP range on the voice gateway card. 4
Use the voice add command with the VPL option on the voice gateway card to add the voice connection for the specified VC and CID/port to the V5.2 IG. zSH> voice add atm uplink1/atm vp 0/101 td 1/1 port 1 alaw v52 1/1 type pots Created subscriber-voice 1/51/2 Created aal2-port-profile 109/16/101/1/1 Created subscriber-voice-elcp-aal2 15 Created v52-user-port 1/1/2 Created subscriber-voice-v52 16
This command creates a voice connection between the uplink interface uplink1 with VP 0 and VC 101 to the voice gateway card user port 1. 5
Display the ATM ELCP to V5.2 voice connection with the voice show command.
zSH> voice show Subscriber end-point Remote end-point Voice Prof Id STA -------------------------- --------------------------- ------------- --1-1-1-0/sonet VC 0/101 port 1 V52 100 100/11/35/1 ENA Total number of voice connections : 1
Configuring voice gateway for VoATM ELCP to V5.2 (VC-switched) ISDN signal This procedure explains how to configure an ISDN signal over a VoATM ELCP to V5.2 voice connection on the voice gateway card. Note: The elcp-trap parameter is available in the aal2-vcl profile. This parameter allows operators to turn ELCP traps on/off for particular AAL2 VCLs. All users on the provisioned AAL2 VCL will have their ELCP trap alerts turned either on or off. 1
Use the cc add command on the voice gateway card to add the cross connect for the specified VC and ISDN connection information using IG 4 and user port 41. zSH> cc add elcp uplink2/atm vc 6/41 td 1/1 port 1 alaw v52 4/41 type isdn cpath 4
MALC Configuration Guide
471
Configuring the Voice Gateway
This adds a cross connect between the uplink2 interface and the voice gateway card using VC 7/111. The voice protocol is V5.2 and the connection type is ISDN with Cpath 5. 2
Use the voice add command to specific the voice connection. zSH> voice add elcp uplink1/atm vc 6/41 td 1/1 port 1 alaw v52 4/41 type isdn cpath 4 Created subscriber-voice 1/57/2 Created atm-vcl uplink1/atm/6/41 Created atm-vcl 1-5-3-0-aal2proxy/atm/0/32 Created atm-cc 2 Created aal2-vcl-profile 1-5-3-0-aal2proxy/atm/0/32 Created aal2-elcp-port 99/0/32/1/2 Created subscriber-voice-elcp-aal2 3 Created v52-user-port 4/41/3 Created subscriber-voice-v52 4 Created subscriber-voice 1/57/3 Created subscriber-voice-elcp-aal2 5 Created subscriber-voice-v52 6 Created subscriber-voice 1/57/4 Created subscriber-voice-elcp-aal2 7 Created subscriber-voice-v52 8
3
Display the ISDN to V5.2 voice connection with the voice show command.
zSH> voice show Subscriber end-point Remote end-point Voice Prof Id STA ------------------------- ----------------------------- ------------ --1-1-1-0/sonet VC 6/41 port 1 V52 four/41/isdn 1/57/2 ENA 1-1-1-0/sonet VC 6/41 port 1 V52 four/41/isdn 1/57/3 ENA 1-1-1-0/sonet VC 6/41 port 1 V52 four/41/isdn 1/57/4 ENA Total number of voice connections : 3
Configuring voice gateway for VoATM ELCP to V5.2 (VC-switched) POTS signal This procedure explains how to configure an POTS signal over a VoATM ELCP to V5.2 voice connection on the voice gateway card. Note: The elcp-trap parameter is available in the aal2-vcl profile. This parameter allows operators to turn ELCP traps on/off for particular AAL2 VCLs. All users on the provisioned AAL2 VCL will have their ELCP trap alerts turned either on or off. 1
Use the cc add command on the voice gateway card to add the cross connect for the specified VC and POTS connection information. using IG 4 and user port 40. zSH> cc add elcp uplink2/atm vc 6/40 td 1/1 port 1 alaw v52 4/40 type pots
472
MALC Configuration Guide
Configuring voice gateway connections
This adds a cross connect between the uplink2 interface and the voice gateway card using VC 7/111. The voice protocol is V5.2 and the connection type is POTS. 2
Use the voice add command to specific the voice connection. zSH> voice add elcp uplink1/atm vc 6/40 td 1/1 port 1 alaw v52 4/40 type pots Created subscriber-voice 1/57/5 Created atm-vcl uplink1/atm/6/40 Created atm-vcl 1-5-3-0-aal2proxy/atm/0/32 Created atm-cc 2 Created aal2-vcl-profile 1-5-3-0-aal2proxy/atm/0/32 Created aal2-elcp-port 99/0/32/1/1 Created subscriber-voice-elcp-aal2 9 Created v52-user-port 4/40/2 Created subscriber-voice-v52 10
3
Display the POTS to V5.2 voice connection with the voice show command.
zSH> voice show Subscriber end-point Remote end-point Voice Prof Id STA ------------------------------ ------------------------- -------------- --1-1-1-0/sonet VC 6/40 port 1 V52 four/40/pots 1/57/5 ENA Total number of voice connections : 1
Configuring voice gateway for VoATM ELCP to V5.2 (VP-switched) This procedure explains how to configure a VoATM ELCP to V5.2 voice connection on the voice gateway card. Note: The elcp-trap parameter is available in the aal2-vcl profile. This parameter allows operators to turn ELCP traps on/off for particular AAL2 VCLs. All users on the provisioned AAL2 VCL will have their ELCP trap alerts turned either on or off. Use the voice vpiadd and voice vpladd commands to build the ATM VP between the uplink card VP and the voice gateway card aal2proxy using the same VC. Then, use the voice add command to build the VCL on the aal2proxy using the same VC that was configured on the uplink card. The allowed VP range on aal2proxy is 16 to 63. Note: In addition to the V5.2 interface group, the required VPL traffic descriptor and VCL traffic descriptor for ELCP lines must be built before performing this procedure. 1
Use the voice vpi add command to build the ATM VPI for the uplink card VP and the voice gateway card aal2proxy. zSH>voice vpiadd uplink/atm 0 v52 1 2004 Created atm-vpi 1-3-3-0-aal2proxy/atm/20
MALC Configuration Guide
473
Configuring the Voice Gateway
Created atm-vpi uplink1/atm/7
This example uses the uplink interface uplink/atm with VP 0. The MALC uplink cards support up 256 (0-255) VPs. The voice call type is V5.2 with IG 1. The maximum number of VCs allocated to the specified VP-switched VPI is 2048. 2
Reboot the system to install the configured VPIs. zSH>systemreboot
3
Use the voice vpladd command to build the VPLs and cross connects. zSH>voice vpladd uplink/atm 0 td 1/1 v52 1 Created atm-vpl 1-3-3-0-aal2proxy/atm/20 Created atm-vpl uplink1/atm/7 Created atm-cc 6
This command builds atm-vpl uplink1/atm/0 on the uplink card using traffic descriptor 1/1 and atm-vpl 1-3-3-0-aal2proxy/atm/16 on the voice gateway card. VP 16 is the first available VP in the allowed VP range on the voice gateway card. 4
Use the voice add command with the VPL option on the voice gateway card to add the voice connection for the specified VP/VC, V5.2 IG and user port. zSH> voice add elcp uplink1/atm vp 0/101 td 1/1 port 1 alaw v52 1/1 type pots Created subscriber-voice 1/51/2 Created aal2-elcp-port 109/16/101/1/1 Created subscriber-voice-elcp-aal2 15 Created v52-user-port 1/1/2 Created subscriber-voice-v52 16
5
Display the ATM ELCP to V5.2 voice connection with the voice show command.
zSH> voice show Subscriber end-point Remote end-point Voice Prof Id STA -------------------------- --------------------------- ------------- --1-1-1-0/sonet VC 0/101 port 1 V52 100 100/11/35/1 ENA Total number of voice connections : 1 zSH>
474
MALC Configuration Guide
Configuring voice gateway connections
Deleting a voice connection To remove the configured voice connection, use the voice delete command. zSH> voice delete elcp 1-1-1-0/sonet VC 6/41 port 1 Deleted aal2-elcp-port 99/0/32/12 Deleted v52-user-port 4/41/3 Deleted subscriber-voice 1/57/2 and its subscriber-voice-xxx profiles Deleted subscriber-voice 1/57/3 and its subscriber-voice-xxx profiles Deleted subscriber-voice 1/57/4 and its subscriber-voice-xxx profiles Deleted atm-vcl 99/0/32 Deleted atm-vcl 15/6/41
To remove the configured VP, use the voice vp delete command. zSH> voice vpdelete uplink/atm/0
Subtended MALC ISDN or POTS voice gateway connections In a subtended MALC configuration, subscriber traffic passes through the subtended MALC uplink card and is sent as AAL2 packets to the MALC with the voice gateway card. The MALC functions as an aggregation point for multiple downstream MALC systems aggregating multiple ATM services (PON, SHDSL, T1/E1 ATM) or multiple ATM voice lines on residential services (ADSL, ADSL2+, VDSL) over a single uplink and voice gateway connection. Figure 62: Voice gateway VoATM to TDM with subtended IAD
IAD
ATM MALC with voice gateway
Local Exchange Switch
In subtended MALC configuration, subscriber traffic passes through the subtended MALC uplink card and is sent as AAL2 cells to the MALC with the voice gateway card. AAL2 cells destined for the voice gateway card enter through one of the MALC uplink card interfaces (GigE, SONET, IP) and are
MALC Configuration Guide
475
Configuring the Voice Gateway
terminated on the voice gateway card. The voice signal is converted to TDM T1/E1 channels and sent to the local switch for TDM voice processing. For traffic coming from the local switch, the TDM voice signals are converted to AAL2 cells by the voice gateway card and sent back out the MALC uplink card to the subtended MALC and then to the configured AAL2 destination. Before configuring the AAL2 to TDM voice connection on the subtended MALC, ensure the voice gateway AAL2 to GR-303 connection is configured correctly. See AAL2 voice gateway connections on page 464. Use these procedures to configure the voice connection on the subtended MALC. For AAL2 connections to a voice gateway card, the subtended MALC supports subscriber voice connections for ISDN to AAL2 and POTS to AAL2.
•
Configuring subtended AAL2 voice connection
•
Deleting subtended voice connection
Configuring subtended AAL2 voice connection Configure the subtended MALC AAL2 to sends its AAL2 signals to the voice gateway. The AAL2 shelf should have a working ATM connection and an available ATM circuit to the voice gateway card. Also, either a subscriber line POTS or ISDN card should be installed with all the required ports enabled. For subtended voice connections, the MALC voice card supports POTS to AAL2 or ISDN to AAL2 voice connections. For more details about configuring voice connections, see Configuring Voice on page 385. For these voice configurations, the ATM traffic descriptor is required before the voice connection can be configured. The ISDN to AAL2 type of voice connection requires an ULC card.
Configuring POTS or ISDN to AAL2 voice connections The voice add command automatically creates the required VPI/VCI, CID, and uplink VCL. 1
Create a new atm-traf-descr with a unique index for a voice connection. See Configuring ATM on page 193 for more information on ATM traffic descriptors and parameters.
zSH> new atm-traf-descr 1 index can be any value Please provide the following: [q]uit. td_type: -----------------> {atmNoClpNoScr}: atmClpNoTaggingScrCdvt td_param1: ---------------> {0}: 4826 PCR . td_param2: ---------------> {0}: 4825 SCR td_param3: ---------------> {0}: 20 MBS td_param4: ---------------> {0}: 15000 CDVT td_param5: ---------------> {0}: cac-divider: -------------> {1}: 10 td_service_category: -----> {ubr}: rtvbr for voice td_frame_discard: --------> {false}:
476
MALC Configuration Guide
Configuring voice gateway connections
usage-parameter-control: -> {true}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
2
Use the voice add command on the subtended MALC to configure an ISDN to AAL2 or POTS to AAL2 voice connection. For ISDN to AAL2:
zSH> voice add isdn 1-3-1-0/isdnu aal2 uplink1/atm vc 0/38 td 1/1 cid 127 Created subscriber-voice 1/5/4 Created subscriber-voice-isdn 65 Created aal2-cid-profile 38/0/38/127 Created subscriber-voice-aal2 66 Created subscriber-voice 1/5/5 Created subscriber-voice-isdn 67 Created subscriber-voice-aal2 68 Created subscriber-voice 1/5/6 Created subscriber-voice-isdn 69 Created subscriber-voice-aal2 70
This example adds an ISDN to AAL2 connection over an ATM VCL with a VPI/VCI of 0/38, traffic descriptor 1, user port 1, and a CID of 16. For POTS to AAL2: zSH> voice add pots 1-5-24-0/voicefxs aal2 uplink1/atm vc 0/39 td 1/1 cid 16 Created subscriber-voice 1/32/2 Created subscriber-voice-pots 10017 Created atm-vcl uplink1/atm/0/39 Created aal2-cid-profile 38/0/39/16 Created subscriber-voice-aal2 10018
This example adds a POTS to AAL2 connection over an ATM VCL with a VPI/VCI of 0/38, traffic descriptor 1, user port 1,and a CID of 16. 3
Display the voice connection with the voice show command.
zSH> voice show Subscriber end-point Remote end-point ------------------------------ -----------------------------1-5-24-0/voicefxs 1-2-1-0/atmima VC 0/39 CID 16 1-3-1-0/isdnu 1-1-1-0/ds1 VC 0/38 CID 127 Total number of voice connections : 2
Voice Prof Id -------------1/32/2 1/5/4
STA --ENA ENA
Deleting subtended voice connection To remove a configured voice connection on the subtended MALC, use the voice delete command. zSH> voice delete isdn 1-3-1-0/isdnu zSH> voice delete pots 1-5-24-0/voicefxs
MALC Configuration Guide
477
Configuring the Voice Gateway
POTS cards running POTS to VoIP in same chassis as voicegateway card ADSL+POTS cards can run POTS to VoIP connections in the same chassis as the voicegateway card running VOIP to GR-303 or V5.2.
Voicegateway configuration Voicegateway card configuration contains the same steps used when this card is configured in a separate system.
•
Creating an unnumbered interface for VoIP on page 457
•
Configuring voice gateway host for VoIP connections on page 458
•
Configuring voice connections for VoIP to GR303 on page 459
•
Configuring voice connections for VoIP to V5.2 on page 460
Creating an unnumbered interface for VoIP Before configuring a VoIP to TDM connection, create a new ip-interface-record and unnumbered interface. 1
To create an IP interface record, use the new ip-interface-record command. zSH> new ip-interface-record vg/ip vpi: ---------------> {0}: vci: ---------------> {0}: rdindex: -----------> {1}: dhcp: --------------> {none}: ** read-only ** addr: --------------> {0.0.0.0}: 10.10.10.1
478
MALC Configuration Guide
POTS cards running POTS to VoIP in same chassis as voicegateway card
netmask: -----------> {0.0.0.0}: 255.255.255.0 bcastaddr: ---------> {0.0.0.0}: 10.10.10.255 destaddr: ----------> {0.0.0.0}: farendaddr: --------> {0.0.0.0}: mru: ---------------> {1500}: reasmmaxsize: ------> {0}: ingressfiltername: -> {}: egressfiltername: --> {}: pointtopoint: ------> {no}: mcastenabled: ------> {yes}: ipfwdenabled: ------> {yes}: mcastfwdenabled: ---> {yes}: natenabled: --------> {no}: bcastenabled: ------> {yes}: ingressfilterid: ---> {0}: egressfilterid: ----> {0}: ipaddrdynamic: -----> {static}: dhcpserverenable: --> {false}: subnetgroup: -------> {0}: unnumberedindex: ---> {0}: mcastcontrollist: --> {}: vlanid: ------------> {0}: maxVideoStreams: ---> {0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Could not find an appropropriate interface on which to bind the IP record. Could not automatically bind this IP Interface New record saved.
2
To create an unnumbered IP interface record, use the new ip-unnumbered-record command. zSH> new ip-unnumbered-record 1 ipUnnumberedInterfaceName: -> { }: vg/ip .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Configuring voice gateway host for VoIP connections The voice gateway VoIP to GR-303 and V5.2 configurations require configuring the voice gateway as an AAL5 proxy on the voice gateway card before adding a VoIP to GR-303 or VoIP to V5.2 voice connection. 1
Locate the if-translate record. zSH> list if-translate 1-3-1-0/aal5proxy if-translate 1-3-1-0/aal5proxy 1 entry found.
MALC Configuration Guide
479
Configuring the Voice Gateway
2
Verify that the desired ATM traffic descriptor is configured. zSH> list atm-traf-descr atm-traf-descr 1 1 entry found.
3
Create and activate a V5.2 or GR-303 interface group (IG). See Configuring GR-303 or V5.2 Interface Groups on page 213 for details.
4
Use the voicegateway add command to create the voice gateway host using the available physical interface or slot number of the voicegateway card and traffic descriptor. zSH> voicegateway add 3 td 1 10.10.10.2 zSH> voicegateway add 1-3-1-0/aal5proxy td 1 10.10.10.2
This adds an IP host on the voice gateway card in slot 3 and assigns the IP address 10.10.10.2. The connection uses traffic descriptor 1 and an AAL5 physical interface of aal5proxy. Use the new voip-server-entry command to add the voip-server-entry 255/255 for SIP binding group and multiple SIP server support if that voip-server-entry profile does not already exist. The logical VoIP interface of voip-1-3/ip is created. Note: The voicegateway add command automatically creates the required ATM VCLs if they do not already exist. Voicegateway connections created from ZMS create a logical VoIP interface with AAL5 proxy in the name, 1-3-1-0-aal5proxy-0-32. 5
Use the voicegateway show command to display the voice gateway host using the slot number of the voicegateway card or the AAL5 physical interface.
zSH> voicegateway show 3 Rd/Address Interface Group ----------------------------------------------------1 10.10.10.1 1-3-1-0-aal5proxy-0-32 0/32 0 zSH> voicegateway show 1-3-1-0/aal5proxy Rd/Address Interface Group ----------------------------------------------------1 10.10.10.1 1-3-1-0-aal5proxy-0-32 0/32 0
480
MALC Configuration Guide
T Host Address S
10.10.10.2
T Host Address S
10.10.10.2
POTS cards running POTS to VoIP in same chassis as voicegateway card
Configuring voice connections for VoIP to GR303 After configuring the voice gateway as an AAL5 proxy on the voice gateway card, the voice connection for VoIP to GR-303 requires adding a VoIP to GR-303 voice connection. This example uses the IP interface voip-1-3/ip with the number 735-0025, name m143-301, destination IP address 172.24.200.143, GR-303 switch protocol, IG 1 and CRV 25. This command also sets the VoIP password in the subscriber-voice-voip profile to password. 1
Use the voice add command to add a VoIP to GR-303 voice connection between the voice gateway card and the switch. Specify the logical VoIP interface (voi-1-3/ip) created with the voicegateway add command. For the PLAR connection, enter the IP address of the GigE port on the uplink card, 172.24.200.143. An optional password is used.
zSH> voice add voip voip-1-3/ip dn 7350025 name m143-301 plar 172.24.200.143 gr303 1/25 pw password Created subscriber-voice 1/330/48 Created subscriber-voice-voip 173 Created gr303-ig-crv 1/25 Created subscriber-voice-gr303 174
2
Display the configured voice connection with the voice show command.
ZSH>voice show Subscriber end-point Remote end-point Voice Prof Id STA ---------------------------- ----------------------------- -------------voip-1-3/ip DN 7350025 GR303 one/25 1/330/25 ENA Total number of voice connections : 1
Configuring voice connections for VoIP to V5.2 After configuring the voice gateway as an AAL5 proxy on the voice gateway card, the voice connection VoIP to V5.2 requires adding a VoIP to V5.2 voice connection. 1
Use the voice add command to add a VoIP to V5.2 voice connection between the voice gateway card and the switch using IG 4 and user port 99. By default, the registration server is set to 0 and the preferred codec is G.711a. An option password is used.
zSH> voice add voip voip-1-3/ip dn 5107777428 name caller pw password v52 4/ 99 type pots Created subscriber 1/2 Created subscriber-voice 1/2/1 Created subscriber-voice-voip 11 Created v52-user-port 4/99/2 Created subscriber-voice-v52 12
2
Display the configured voice connection with the voice show command.
zSH> voice show Subscriber end-point Remote end-point Voice Prof Id STA ------------------------------ ------------------------ -------------- --voip-1-3/ip DN 5107777428 V52 four/99/pots 1/2/1 ENA
MALC Configuration Guide
481
Configuring the Voice Gateway
Total number of voice connections : 1
POTS to VOIP connections Configure VoIP server and other VoIP feautures as specified in the Voice over IP (VoIP) connections on page 391. Then, create the POTS to VoIP connection sending calls to the IP address of the voicegateway card (in this example 10.10.10.2)
Creating POTS to VoIP connections This example creates a POTS to VoIP subscriber. 1
Use the voice command to add the POTS to VoIP connection. This examples creates a connection with a directory number 510-522-0401 and the name smith. The POTS calls are mapped to the GigE port (ethernet-3) on the uplink card using VLAN100. The VoIP endpoint user name is case sensitive and must match the voice switch requirements, for example AAL/1 for MGCP with the Tekelec T6000 or TP/0001 for Megaco with Nortel CS2K. The PLAR address refers to the unnumbered IP address configured for the voicegateway card. Note: For MGCP and Megaco calls, the MALC ignores the preferred-codec setting and selects the codec from a list provided by the MGCP server or media gateway controller.
zSH> voice add pots 1-8-1-0/voicefxs voip ethernet3-100/ip DN 5105220401 name smith plar 10.10.10.2 reg 0 enable Created subscriber-voice 1/2/1 Created subscriber-voice-pots 1004 Created subscriber-voice-voip 1005
2
View the voice connection.
zSH> voice show Subscriber end-point Remote end-point Voice Prof Id ------------------------------ ------------------------------ ----------1-8-1-0/voicefxs ethernet3-100/ip DN 5105220401 1/2/1 Total number of voice connections : 1
STA --ENA
Caution: Avoid changes or deletions to the ip-interface-record profile after creating a voice connection on that interface. When running POTS and voicegateway cards in the same chassis, delete all local voice connections before deleting any cards. .
482
MALC Configuration Guide
Configuring SIP-PRI media gateway
Configuring 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. On an T1 connection, it 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. SIP-to-PRI uses the Voice Gateway (VG) card on the MALC to connects two entities:
•
VOIP endpoint
•
SIP-to-PRI endpoint
The VOIP endpoint can be a SIP phone or soft switch on the other side of the IP network. The SIP-to-PRI endpoint is the far side of the PBX switch where the TDM call signal is converted to an IP packet. The ISDN portion of the entity specifies the PBX endpoint to which the call is connected. The softswitch running VOIP translates the PBX phone number to the IP address targeted for the SIP phone, enabling a phone session over the Internet. The TDM call data that has been converted into IP packets now is sent to a soft switch instead of the traditional Class V switch. The soft switch treats this data as an VOIP endpoint, instead of a POTS call.
MALC Configuration Guide
483
Configuring the Voice Gateway
Figure 63: SIP to PRI environment
Soft Switch IP Network
GigE
PRI o
ver T
MALC with Uplink-2-GigE card and MALC-VG-T1/E1-32-2S card
1/E1
lin k s
PBX switch SIP phone
SIP phone PBX phones
SIP-PRI configuration involves the following procedures:
484
MALC Configuration Guide
•
Configuring ISDN signaling and DS1 profiles on page 486
•
Verifying voice configuration prerequisites on page 487
•
Configure SIP, voicegateway and voice connections on page 488
Configuring SIP-PRI media gateway
About the VoIP Endpoint The primary task in creating a SIP-to-ISDN-PRI network is to create a VOIP endpoint on the MALC. Use both the vg add and voice add commands to create a VOIP endpoint on the MALC. The vg add command specifies an IP address that acts as the identifier for the card. This information is forwarded either to a soft switch or a SIP phone. This vg command creates connections between the SIP-to-PRI entity and the VOIP interface on the card. The voice add command includes a directory number, a name, an ISDN signalling profile index, and VoIP server index. The voice add command links the DN on a VOIP connection to a specific SIP-to-PRI port. It correlates a specified value on the VOIP network with a specific SIP-to-PRI. There are up to 32 physical ports on a VG card. Each port can represent a specific SIP-to-PRI.
ISDN Signaling profile An ISDN signaling profile is used to specified the type of ISDN signaling used between the MALC and a PBX switch. The isdn-signaling record contains the setting for the switch type. A unique ISDN signaling profile should be configured for each voicegateway card in the MALC. The ISDN signaling profile is specified in the voice add command to map the PRI’s on the PBX to a the voicegateway card. The ds1-group-number field in the ds1-profile record corresponds to the ISDN signaling profile record. Note: The MALC currently supports SIP to PRI for NI2 switches.
SIP trunks SIP-to-ISDN-PRI involves the concept of SIP trunking. The logical voice channel established between carrier voice equipment and an enterprise voice device is called a SIP trunk. SIP trunks enable enterprises to create a single IP connection to carrier networks. An enterprise TDM PBX peers with a carrier SIP server (soft switch) with the appropriate groupings and security between them. SIP sets up and tears down voice calls to and from the enterprise PBX, converting the Q.931 ISDN call setup and release messages to SIP over the IP data network. A distinguishing characteristic of a PRI trunk is that it has multiple numbers associated with it. This enables you to aggregate more information than was possible using the standard POTS method that associated only one number per connection.
MALC Configuration Guide
485
Configuring the Voice Gateway
Hardware requirements For SIP-to-PRI configurations on a MALC, you need a Voice Gateway (VG) card (for example, MALC-VG-T1/E1-32-2S) installed and an Uplink card with GigE support (for example, MALC-UPLINK-2-GE). Use a TelcoT1 cable to connect the ports on the PBX card to the ports on the VG card. The following messages appears on the MALC console when the ports are connected: SEP 06 13:23:31: alert : 1/14/1025: alarm_mgr: alarmMgr.c: _laMgrLogMsg(): l=273 : tLineAlarm: 01:14:02 Critical T1 Up Line 1:14:2:0 (Alarm Cleared)
The showline and showlinestatus commands can also be used to verify the line status.
Configuring ISDN signaling and DS1 profiles 1
Using the new isdn-signaling command, create an ISDN signaling profile for each type of ISDN signaling used between the MALC and the PBX. The MALC currently supports NI2 switch type. The following example creates a signaling value of 1. The isdn-signaling profile ID is used as the isdnsig value in the voice add voip command. zSH> new isdn-signaling 1 Please provide the following: [q]uit. active-dchannel-location: -> {1}: ** read-only ** switch-type: --------------> {NONE(0)}: ni2 calling-address: ----------> {}: "" sub-address: --------------> {}: "" number-of-bchannels: ------> {24}: enable-traps: -------------> {disabled}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
2
Associate each DS1 profile to a ISDN signal profile based on the ds1-group-number in the ds1-profile. This association maps the PRIs on the PBX to the configured voice gateway card.
zSH> new ds1-profile 1-3-1-0/ds1 line-type: ----------------------> line-code: ----------------------> send-code: ----------------------> circuit-id: ---------------------> loopback-config: ----------------> signal-mode: --------------------> fdl: ----------------------------> dsx-line-length: ----------------> line-status_change-trap-enable: -> channelization: -----------------> ds1-mode: ----------------------->
486
MALC Configuration Guide
{esf} {b8zs} {sendnocode} {ds1} {noloop} {robbedbit} messageoriented {fdlnone} {dsx0} {enabled} {enabledds0} {csu}
Configuring SIP-PRI media gateway
csu-line-length: ----------------> {csu00} clock-source-eligible: ----------> {eligible} noteligible transmit-clock-source: ----------> {looptiming} cell-scramble: ------------------> {true} coset-polynomial: ---------------> {true} protocol-emulation: -------------> {network} signal-type: --------------------> {loopstart} ds1-group-number: ---------------> {0} 1 (maps to ISDN signal profile) line-power: ---------------------> {disabled} timeslot-assignment: ------------> {0+1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23} .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
3
Verify D channel status. zSH> isdnsigctrp show dchan 1 unit 1: D-Channel UP [ifIndex 683]
Verifying voice configuration prerequisites Before configuring the voice gateway connection, use the following procedures to ensure that the configuration prerequisites have been configured. 1
Use the slots command to verify the desired uplink and voice gateway card installation and status. This example shows the Uplink-T1/E1-ATM/ TDM/IP-16 card running in slot 1 and the MALC voice gateway card running in slot 3. Other line cards can be inserted and running in other slots as desired. zSH> slots 1: MALC UPLINK T1/E1 TDMF (RUNNING) 3: MALC T1E132VG (RUNNING) 13: MALC GSHDSL (RUNNING) 17: MALC ADSL + POTS AC6 (RUNNING)
2
Check the system settings to ensure the appropriate country coding and other system-level settings are configured. See Updating system settings on page 386for details.
3
Ensure there is an active system clock source. See the MALC Hardware Installation Guide.
4
Create a new atm-traf-descr with a unique index for a voice connection.
zSH> new atm-traf-descr 1 index can be any value Please provide the following: [q]uit. td_type: -----------------> {atmNoClpNoScr}: atmClpNoTaggingScrCdvt td_param1: ---------------> {0}: 4826 PCR . td_param2: ---------------> {0}: 4825 SCR td_param3: ---------------> {0}: 20 MBS td_param4: ---------------> {0}: 15000 CDVT td_param5: ---------------> {0}:
MALC Configuration Guide
487
Configuring the Voice Gateway
cac-divider: -------------> {1}: 10 td_service_category: -----> {ubr}: rtvbr for voice td_frame_discard: --------> {false}: usage-parameter-control: -> {true}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Configure SIP, voicegateway and voice connections This procedure creates the voip-server-entry, SIP dialplans, and configures the voicegateway and voice connections. 1
Create a VOIP server ID, using the new voip-server-entry command. A VOIP server entry describes a particular soft switch which handles a VOIP protocol like SIP, MGCP, or Megaco. The following example assumes an entry of 255/255 for a SIP binding group.
zSH> new voip-server-entry 255/255 Please provide the following: [q]uit. zhoneVoipServerAddrType: ----------> {ipv4}: zhoneVoipServerAddr: --------------> {}: 172.16.88.9 zhoneVoipServerUdpPortNumber: -----> {5060}: zhoneVoipServerId: ----------------> {generic}: metaswitch protocol: -------------------------> {sip}: sendCallProceedingTone: -----------> {false}: rtcpEnabled: ----------------------> {false}: rtcpPacketInterval: ---------------> {5000}: interdigitTimeOut: ----------------> {10}: ipTos: ----------------------------> {0}: systemDomainName: -----------------> {}: expires-invite-value: -------------> {3600}: expires-register-value: -----------> {3600}: expires-header-method: ------------> {register}: session-timer: --------------------> {off}: session-expiration: ---------------> {180}: session-min-session-expiration: ---> {180}: session-caller-request-timer: -----> {no}: session-callee-request-timer: -----> {no}: session-caller-specify-refresher: -> {omit}: session-callee-specify-refresher: -> {uac}: dtmf-mode: ------------------------> {rfc2833}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
2
488
MALC Configuration Guide
Create a SIP dial plan using the new sip-dialplan command. A SIP dial plan maps incoming digits to a particular VOIP server. The dial plans allow the MALC to establish the VOIP end of the call. Based on the dial plan, the MALC also rejects digit strings that don’t match those specified
Configuring SIP-PRI media gateway
in the dial plan. The dial plan also enables communication between the SIP phone and the provisioned soft switch. The following example uses 1 as the ID of the SIP dial plan and specifies a voip-server-entry-index of 0 to reference the SIP binding group. zSH> new sip-dialplan 1 Please provide the following: [q]uit. match-string: ----------------> {}: 0 sip-ip-address: --------------> {0.0.0.0}: 172.16.88.9 destination-name: ------------> {}: number-of-digits: ------------> {0}: 10 prefix-strip: ----------------> {0}: prefix-add: ------------------> {}: 510777395 dialplan-type: ---------------> {normal}: voip-server-entry-index: -----> {0}: (0 indicates SIP binding group) override-interdigit-timeout: -> {0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
3
To create an IP interface record, use the new ip-interface-record command. zSH> new ip-interface-record vg/ip vpi: ---------------> {0}: vci: ---------------> {0}: rdindex: -----------> {1}: dhcp: --------------> {none}: ** read-only ** addr: --------------> {0.0.0.0}: 10.10.10.1 netmask: -----------> {0.0.0.0}: 255.255.255.0 bcastaddr: ---------> {0.0.0.0}: 10.10.10.255 destaddr: ----------> {0.0.0.0}: farendaddr: --------> {0.0.0.0}: mru: ---------------> {1500}: reasmmaxsize: ------> {0}: ingressfiltername: -> {}: egressfiltername: --> {}: pointtopoint: ------> {no}: mcastenabled: ------> {yes}: ipfwdenabled: ------> {yes}: mcastfwdenabled: ---> {yes}: natenabled: --------> {no}: bcastenabled: ------> {yes}: ingressfilterid: ---> {0}: egressfilterid: ----> {0}: ipaddrdynamic: -----> {static}: dhcpserverenable: --> {false}: subnetgroup: -------> {0}: unnumberedindex: ---> {0}: mcastcontrollist: --> {}: vlanid: ------------> {0}: maxVideoStreams: ---> {0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s
MALC Configuration Guide
489
Configuring the Voice Gateway
Could not find an appropropriate interface on which to bind the IP record. Could not automatically bind this IP Interface New record saved.
4
To create an unnumbered IP interface record, use the new ip-unnumbered-record command. zSH> new ip-unnumbered-record 1 ipUnnumberedInterfaceName: -> { }: vg/ip .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
5
Assign an address and add values to the VG card by issuing the vg add command. The following example uses an VG IP address of 10.10.10.1 and a TD of 1. zSH> vg add -v 14 td 1 10.10.10.1 Reading unnumbered profile 1 Reading ip-interface profile ifIndex 773 Reading unnumbered profile 2 Reading ip-interface profile ifIndex 1053 Using UNI record 2, ip interface record IfIndex 1053 Created proxy atm-vcl 1-1-1-0-aal5proxy VC 0/34 Created remote atm-vcl 1-14-1-0-aal5proxy VC 0/32 Created cross connect index 5 IP record IfIndex is 1054 Created near end ip-interface-record 1-14-1-0-aal5proxy-0-34/ip Stack bind near end i/f 1-14-1-0-aal5proxy-0-34/ip to RFC1483 1-1-1-0-aal5proxy successful Checking to see if 1-14-1-0-aal5proxy-0-34-1/ip exists. Interface 1-14-1-0-aal5proxy-0-34-1/ip does not exist IfIndex voice add voip voip-1-14/ip dn 5107773950 name 5107773950 reg 0 isdnsig 1 Created subscriber 1/642 Created subscriber-voice 1/642/1 Created subscriber-voice-voip 11 Created subscriber-voice-isdnsig 12
490
MALC Configuration Guide
Configuring SIP-PRI media gateway
7
Display the subscriber voice ISDN signature by issuing the get subscriber-voice-isdnsig command. The following example assumes a subscriber voice ISDN signature of 12. The ISDN signature is displayed in the output of the voice add voip command. zSH> get subscriber-voice-isdnsig 12 voice-isdn-sig-index: -> {1} directory-number: -----> {5107773950 hunt-group-index-1: ---> {0} hunt-group-index-2: ---> {0} hunt-group-index-3: ---> {0}
The SIP-to-PRI feature enables you to convert TDM call signals from a T1/E1 PRI trunk into SIP (Session Initiation Protocol) VOIP packets. It takes advantage of the emergence of SIP networking and how it can achieve new efficiencies in network use and application deployment.
MALC Configuration Guide
491
Configuring the Voice Gateway
492
MALC Configuration Guide
9
CONFIGURING GR-303 OR V5.2 INTERFACE GROUPS This section explains how to configure GR-303 and V5.2 interface groups on the MALC and how to configure system settings for voice. It includes the following information:
•
Configuring a GR-303 interface, page 493
•
Modifying a GR-303 interface group, page 498
•
Configuring a V5.2 interface, page 499
•
Modifying the v52-interface-group profile, page 510
After configuring the GR-303 or V5.2 interface, proceed to adding subscribers, as explained in Configuring the Voice Gateway on page 301 or Configuring Voice on page 385. Note: The TDM/ATM Uplink card or the Voice Gateway card is required for GR-303 and V5.2 support on the MALC. Note: This chapter assumes you have configured the TDM/ATM Uplink and the Voice Gateway card as explained in the MALC Hardware Installation Guide. The TDM/ATM Uplink card has 16 T1/E1 ports. The first eight ports are ATM T1/E1 ports; the second eight are TDM T1/E1 ports.
Configuring a GR-303 interface The following steps are necessary to configure GR-303 interface groups on the MALC. Each step is explained in more detail in the sections that follow: 1. Update the system profile to specify the country the unit is operating in and to enable voice bandwidth check. See Updating system settings on page 386. 2. Find the line group identifier of the communication path (the DS1 interface on the TDM/ATM Uplink card). 3. Create the GR-303 Interface Group (IG). See Creating a GR-303 interface group on page 495.
MALC Configuration Guide
493
Configuring GR-303 or V5.2 Interface Groups
4. Activate the GR-303 IG. The following table summarizes the configuration tasks for creating a GR-303 interface.
Configuration Task
Profile
Creating a GR-303 interface group on page 495.
new gr303-interface-group GR303Index Use the same GR303Index for the gr303-interface-group and the CRVs in the gr303-ig-crv profile.
Modifying a GR-303 interface group on page 498
update gr303-interface-group GR303Index
Displaying GR303 interface group status on page 499
voice status ig gr303 groupname
Note: The sapi-1-n-200 and sapi-1-max-outstanding-frames parameters automatically take the same values as the sapi-0-n-200 and sapi-0-max-outstanding-frames parameters. The gr303-interface-group profile supports the following parameters. Parameter
Description and options
name-id
A name assigned by the installer. It must be unique to the system. This value is a string. This is a required field.
switch-type
The name of the switch supplying the GR-303 circuits. This is a required field. Values: lucent5Ess nortelDms100
adminStatus
The administrative status of the IG. This must be set to inservice for the IG to function. Values: inservice outofservice
working-mode
Indicates whether the selected switch can configure the RDT using common management information service (CMIS) over the Embedded Operations Channel (EOC) channel. Values: active the selected switch can configure the RDT for Call Reference Values (CRVs) over the EOC channel. Normally used for 5ESS switches. passive CRVs can only be configured locally. Normally used for DMS switch.
CrtlChannel:
494
MALC Configuration Guide
The IG control channel array.
Configuring a GR-303 interface
Parameter
Description and options
ds1LM:array[1..28]:
The array for T1/DS1 circuits. The maximum number of DS1 trunks allowed per IG is 28. This array includes the dsn-lg-id, channel-number, and role parameters.
dsn-lg-id
The DS1 line group ID number. This must match the line group ID of the physical interface on which you are provisioning GR-303 IGs.
channel-number
Identifies the DS1 for the channelized DS3. Values: 1 to 28
role
The role this channel plays in the array. Must be set to primary for the first DS1. One other DS1 must have the role parameter set to secondary. All other DS1s have their role set to payload. Values: payload secondary primary Default: payload
logical-id
Identifies each physical DS1 within an Interface Group between RDT and IDT. The value 1 is reserved for the primary DS1 and cannot be used by any other DS1s. This field is mandatory. Values: 1 to 28
ds1-valid-flag
Whether this DS1 is valid or invalid. Must be set to valid to enable calls over provisioned DS1s. Values: valid invalid
Creating a GR-303 interface group To create a GR-303 interface group: 1
List the ds1-profiles zSH> list ds1-profile if-translate 1-1-9-0/ds1 if-translate 1-1-10-0/ds1 if-translate 1-1-11-0/ds1 if-translate 1-1-12-0/ds1 if-translate 1-1-13-0/ds1 if-translate 1-1-14-0/ds1 if-translate 1-1-15-0/ds1 if-translate 1-1-16-0/ds1 ...
MALC Configuration Guide
495
Configuring GR-303 or V5.2 Interface Groups
Then enter the lineGroup command to find the line group identifiers for the TDM T1/E1 ports. Make a note of the lineGroupIds of the TDM T1/ E1 ports; they will be used later. zSH> linegroup 1-1-9-0/ds1 lineGroupId: 13 zSH> linegroup 1-1-10-0/ds1 lineGroupId: 15 zSH> linegroup 1-1-11-0/ds1 lineGroupId: 17 zSH> linegroup 1-1-12-0/ds1 lineGroupId: 19 zSH> linegroup 1-1-13-0/ds1 lineGroupId: 21 zSH> linegroup 1-1-14-0/ds1 lineGroupId: 23 zSH> linegroup 1-1-15-0/ds1 lineGroupId: 25 zSH> linegroup 1-1-16-0/ds1 lineGroupId: 27
2
Create a new GR-303 interface group. For example:
zSH> new gr303-interface-group 1 1 is a user-defined Index for this IG Please provide the following: [q]uit. name-id: -----------------------> {}: zhone switch-type: -------------------> {lucent5ess}: lucent5ess | norteldms100 adminStatus: -------------------> {outofservice}: inservice working-mode: ------------------> {passive}: active | passive ctrlChannel: control-channel-t303: ----------> {700}: control-channel-t396: ----------> {14700}: sapi-0-max-outstanding-frames: -> {7}: sapi-0-n-200: ------------------> {3}: sapi-0-t-200: ------------------> {150}: sapi-0-t-203: ------------------> {30}: sapi-0-pps-mode: ---------------> {notinhibited}: sapi-1-max-outstanding-frames: -> {7}: sapi-1-n-200: ------------------> {3}: sapi-1-t-200: ------------------> {150}: sapi-1-t-203: ------------------> {30}: sapi-1-pps-mode: ---------------> {notinhibited}: ds1LM has 28 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? s Enter the array element to start: 1 ds1LM[1]: dsn-lg-id: ---------------------> {1}: 13 linegroup ID of the first port on the TDM/ATM Uplink channel-number: ----------------> {1}:
496
MALC Configuration Guide
Configuring a GR-303 interface
role: --------------------------> {payload}: primary logical-id: --------------------> {28}: 1 1 is reserved for primary channels. Use numbers 2 to 28 for other types of channels. ds1-valid-flag: ----------------> {invalid}: valid ds1LM[3]: dsn-lg-id: ---------------------> {1}: 15 linegroup ID of the second port on the TDM/ATM Uplink channel-number: ----------------> {1}: role: --------------------------> {payload}: secondary logical-id: --------------------> {28}: 2 ds1-valid-flag: ----------------> {invalid}: valid ds1LM[4]: dsn-lg-id: ---------------------> {1}: 17 linegroup ID of the third port on the TDM/ATM Uplink channel-number: ----------------> {1}: role: --------------------------> {payload}: logical-id: --------------------> {28}: 3 ds1-valid-flag: ----------------> {invalid}: valid ds1LM[5]: dsn-lg-id: ---------------------> {1}: q .................... Save record? [s]ave, [c]hange or [q]uit: s New record saved.
3
Activate the GR-303 interface group (IG):
zSH> update gr303-interface-group 1 Please provide the following: [q]uit. name-id: -----------------------> {zhone}: switch-type: -------------------> {lucent5ess}: adminStatus: -------------------> {outofservce}: inservice working-mode: ------------------> {passive}: ctrlChannel: control-channel-t303: ----------> {700}: control-channel-t396: ----------> {14700}: sapi-0-max-outstanding-frames: -> {7}: sapi-0-n-200: ------------------> {3}: sapi-0-t-200: ------------------> {150}: sapi-0-t-203: ------------------> {30}: sapi-0-pps-mode: ---------------> {notinhibited}: sapi-1-max-outstanding-frames: -> {7}: sapi-1-n-200: ------------------> {3}: sapi-1-t-200: ------------------> {150}: sapi-1-t-203: ------------------> {30}: sapi-1-pps-mode: ---------------> {notinhibited}: ds1LM has 28 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n Using default values for elements 1-28 .................... Save record? [s]ave, [c]hange or [q]uit: s Record updated.
After the GR-303 IG is activated, proceed to configuring GR-303 subscribers. For information, see Updating system settings on page 386.
MALC Configuration Guide
497
Configuring GR-303 or V5.2 Interface Groups
Modifying a GR-303 interface group Caution: Removing an IG from service will cause all active calls to be dropped. To remove service from the IG: zSH> update gr303-interface-group 1 Please provide the following: [q]uit. name-id: -----------------------> {zhone}: switch-type: -------------------> {lucent5ess}: adminStatus: -------------------> {inservice}: outofservice working-mode: ------------------> {passive}: ctrlChannel: control-channel-t303: ----------> {700}: control-channel-t396: ----------> {14700}: sapi-0-max-outstanding-frames: -> {7}: sapi-0-n-200: ------------------> {3}: sapi-0-t-200: ------------------> {150}: sapi-0-t-203: ------------------> {30}: sapi-0-pps-mode: ---------------> {notinhibited}: sapi-1-max-outstanding-frames: -> {7}: sapi-1-n-200: ------------------> {3}: sapi-1-t-200: ------------------> {150}: sapi-1-t-203: ------------------> {30}: sapi-1-pps-mode: ---------------> {notinhibited}: ds1LM has 28 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n Using default values for elements 1-28 .................... Save record? [s]ave, [c]hange or [q]uit: s Record updated.
To restore service to the IG: zSH> update gr303-interface-group 1 Please provide the following: [q]uit. name-id: -----------------------> {zhone}: switch-type: -------------------> {lucent5ess}: adminStatus: -------------------> {outofservce}: inservice working-mode: ------------------> {passive}: ctrlChannel: control-channel-t303: ----------> {700}: control-channel-t396: ----------> {14700}: sapi-0-max-outstanding-frames: -> {7}: sapi-0-n-200: ------------------> {3}: sapi-0-t-200: ------------------> {150}: sapi-0-t-203: ------------------> {30}: sapi-0-pps-mode: ---------------> {notinhibited}: sapi-1-max-outstanding-frames: -> {7}: sapi-1-n-200: ------------------> {3}: sapi-1-t-200: ------------------> {150}: sapi-1-t-203: ------------------> {30}: sapi-1-pps-mode: ---------------> {notinhibited}:
498
MALC Configuration Guide
Configuring a V5.2 interface
ds1LM has 28 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n Using default values for elements 1-28 .................... Save record? [s]ave, [c]hange or [q]uit: s Record updated.
Displaying GR303 interface group status The voice status command can be used to display GR303 IG status. zSH> voice status ig gr303 test Status for gr303 interface group test: Admin status = in service Oper status = inoperable Active calls = 0 Switch type = norteldms100 TMC primary state = out of service TMC secondary state = out of service EOC primary state = out of service EOC secondary state = out of service
Configuring a V5.2 interface The following steps are necessary to configure V5.2 interface groups on the MALC. Each step is explained in more detail in the sections that follow: 1. Update the system profile to specify the country the unit is operating in and to enable voice bandwidth check. See Updating system settings on page 386. 2. Find the line group identifier of the communication path (the E1 interface on the TDM/ATM Uplink card). 3. Create the V5.2 IG. See Creating a V5.2 interface group on page 503. 4. Provision the V5.2 links. See Provisioning V5.2 links on page 505. 5. Add C-channels within links. See Adding C-channels within links on page 506. 6. Provision C-paths. See Provisioning C-paths on page 508. 7. Activate the V5.2 IG. See Activating the V5.2 IG on page 510. The following table summarizes the tasks for configuring the V5.2 interface.
Configuration task
Commands
Creating a V5.2 interface group on page 503
new v52-interface-group v52IgIndex
MALC Configuration Guide
499
Configuring GR-303 or V5.2 Interface Groups
Configuration task
Commands
Finding the line group identifiers of the physical connection on page 504
update v52-interface-group v52IgIndex
Provisioning V5.2 links on page 505 Adding C-channels within links on page 506 Provisioning C-paths on page 508 Activating the V5.2 IG on page 510 Displaying V5.2 interface group status on page 511
voice status ig v52 groupname
The following sections describe in further detail each step necessary in the configuration process. Note: Although the v52-link, v52-c-channel and v52-c-path arrays can be provisioned at the same time the v52-interface-group is created, the steps are separated for clarity. The following table describes the supported V5.2 parameters in the v52-interface-group. The V5.2 interface group (IG) is configured using one profile. Parameter
Options
name-id
The name of the IG. Must be unique in the system. Use the same name for the voice-v52-interface-name parameter in the subscriber-voice-v52 profile. This value is a string.
local-interface-id
The interface ID of the IG. Must be unique across the system. This value must match the value on the switch. Values: 0 to 16777215
local-prov-variant
The prov(isioning) variant describes a type of provisioning. This value must match the value on the switch. Values: 0 to 127
admin-status
The administrative status of the profile. Values: inservice outofservice deferredoutofservice restart
500
MALC Configuration Guide
Configuring a V5.2 interface
Parameter
Options
pstn-layer-3-start-address
The start address for PSTN users. When PSTN users are added, they must have an address greater or equal to this one. This value must match the value on the switch. Values: 0 to 65535
isdn-env-func-start-address
The start address for ISDN users. When ISDN users are added, they must have an address greater or equal to this one. This value must match the value on the switch. Values: 0 to 8175
national-pstn-region
Country setting. Sets up PSTN values for the specific country.
switch-vendor
The switch vendor for the IG. Values: lucent, nortel, alcatel, ericsson, nokia, siemens, samsung.
protocol-spec
Specifies which variation of the V5.2 protocol is to be used by this interface group. This value must match the value on the switch. Values: edition1 edition2
v52-ig-lapv
An array of V5.2 Lapv timer parameters. These configure retries and other functions over the management links. This value must match the value on the switch.
v52-link[1..16]
This array is used to provision the E1circuits between the LE and the MALC unit. There can be up to sixteen links. Each E1 link has 32 channels.
dsn-lg-id
Describes the line group ID associated with the E1 link. Use the lineGroup command to find the line group ID. Values: 1 to 16
id
The V5.2 link identifier. Assigned by the Local Exchange (LE).
v52-c-channel: array [1..3]
This array describes up to three control channels per link (E1). There can be up to 3 of them on each of the16 links for a maximum of 48. C-channels are used to pass management information between then LE and the MALC system.
time-slot-index
The channel that the C-channel is running over. This value must match the value on the switch. Values: 15 16 31
MALC Configuration Guide
501
Configuring GR-303 or V5.2 Interface Groups
Parameter
Options
logical-channel-id
C-channels carry a group of one or more C-paths, excluding the C-paths used for the protection protocol. A V5.2 interface may contain up to 44 logical C-channels. Each logical C-channel on an interface is uniquely identified with a 16 bit logical C-channel identifier. This value must match the value on the switch. Values: 0 to 65535
protection-group
The protection protocol ensures that other protocols can continue to operate in case of equipment failure. This value must match the value on the switch. Values: none group1 onetoonegroup2 mtongroup2
role
The C-channel role. This value must match the value on the switch. Values: active standby switchtostandby Default: active
link-valid-flag
Activates the E1 circuit. Values: valid invalid
v52-c-path: array [1..48]
This array describes communications paths. C-paths are used to specify the type of information running between the MALC system and the LE. C-paths run inside C-channels. There can be up to 48 C-paths inside each C-channel. Values: Use the logical-channel-id numbers created for the C-channels.
id
The ID number of the communications path. Values: 0 to 255
type
The type of communications path. This tells the system how the management information is communicated. Values: unknown pstn POTS ctrl control protocol bcc bearer channel connection lctl link control protocol isdnds BRI voice data
502
MALC Configuration Guide
Configuring a V5.2 interface
Parameter
Options
logical-channel-id
The logical C-channel ID that the C-path is using. This number must match the logical-channel-id value of the C-channel that the C-path is running over. Values: 0 to 65535
c-path-valid-flag
When this parameter is set to valid, the C-path is active. Values: valid invalid
Creating a V5.2 interface group Note: While provisioning is being performed on the V5.2 interface, the IG should be kept out of service. The following example shows how to create a V5.2 IG named zhone. zSH> new v52-interface-group 1 Please provide the following: [q]uit. name-id: ---------------------> {}: zhone local-interface-id: ----------> {0}: 1 local-prov-variant: ----------> {0}: 1 prov-variant-request: --------> {norequest}: admin-status: ----------------> {outofservice}: pstn-layer-3-start-address: --> {0}: 1 isdn-env-func-start-address: -> {0}: 1 port-alignment-request: ------> {norequest}: national-pstn-region: --------> {etsi}: germany match the country in the system profile switch-vendor: ---------------> {ericsson}: siemens match switch protocol-spec: ---------------> {edition2}: startup-check-link-id: -------> {false}: startup-unblock-user-ports: --> {false}: link-oos-timer: --------------> {2500}: link-is-timer: ---------------> {200}: v52-ig-lapv: max-outstanding-frames: ------> {7}: ** read-only ** n200: ------------------------> {3}: ** read-only ** n201: ------------------------> {260}: ** read-only ** t200: ------------------------> {1000}: ** read-only ** t203: ------------------------> {10}: ** read-only ** v52-link has 16 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n Using default values for elements 1-16 v52-c-path has 48 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n Using default values for elements 1-48 .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
MALC Configuration Guide
503
Configuring GR-303 or V5.2 Interface Groups
Note: After creating the IG, certain parameters in the v52-interface-group can only be modified with the v52config command. For details, see Modifying the v52-interface-group profile on page 510.
Finding the line group identifiers of the physical connection List the ds1-profiles: zSH> list ds1-profile if-translate 1-1-9-0/ds1 if-translate 1-1-10-0/ds1 if-translate 1-1-11-0/ds1 if-translate 1-1-12-0/ds1 if-translate 1-1-13-0/ds1 if-translate 1-1-14-0/ds1 if-translate 1-1-15-0/ds1 if-translate 1-1-16-0/ds1 ...
Then enter the lineGroup command to find the line group identifiers for the TDM T1/E1 ports. Make a note of the lineGroupIds of the TDM T1/E1 ports; they will be used later. zSH> linegroup 1-1-9-0/ds1 lineGroupId: 13 zSH> linegroup 1-1-10-0/ds1 lineGroupId: 15 zSH> linegroup 1-1-11-0/ds1 lineGroupId: 17 zSH> linegroup 1-1-12-0/ds1 lineGroupId: 19 zSH> linegroup 1-1-13-0/ds1 lineGroupId: 21 zSH> linegroup 1-1-14-0/ds1 lineGroupId: 23 zSH> linegroup 1-1-15-0/ds1 lineGroupId: 25 zSH> linegroup 1-1-16-0/ds1 lineGroupId: 27
Make a note of the lineGroupIds of the TDM T1/E1 ports; they will be used later.
504
MALC Configuration Guide
Configuring a V5.2 interface
Provisioning V5.2 links This section explains how to provision individual E1 circuits or V5.2 links.
•
To create V5.2 links, enter s for subset at the v52-link has 16 elements Modify [a]ll, [n]one, a [s]ubset, or [q]uit? prompt
•
For each E1 circuit, enter a unique dsn-lg-id number. Refer to Finding the line group identifiers of the physical connection on page 504.
•
Enter a link id number.
•
Enter valid at the link-valid-flag prompt to turn the link up.
This example configures three links: zSH> update v52-interface-group 1 the IG created earlier Please provide the following: [q]uit. name-id: ---------------------> {zhone}: ** read-only ** local-interface-id: ----------> {1}: local-prov-variant: ----------> {1}: prov-variant-request: --------> {norequest}: admin-status: ----------------> {outofservice}: pstn-layer-3-start-address: --> {1}: isdn-env-func-start-address: -> {1}: port-alignment-request: ------> {norequest}: national-pstn-region: --------> {germany}: switch-vendor: ---------------> {siemens}: protocol-spec: ---------------> {edition2}: startup-check-link-id: -------> {false}: startup-unblock-user-ports: --> {false}: link-oos-timer: --------------> {2500}: link-is-timer: ---------------> {200}: v52-ig-lapv: max-outstanding-frames: ------> {7}: ** read-only ** n200: ------------------------> {3}: ** read-only ** n201: ------------------------> {260}: ** read-only ** t200: ------------------------> {1000}: ** read-only ** t203: ------------------------> {10}: ** read-only ** v52-link has 16 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? Modify [a]ll, [n]one, a [s]ubset, or [q]uit? s to modfy the V5.2 links Enter the array element to start: 1 v52-link[1]: dsn-lg-id: -------------------> {1}: 13 linegroup ID of the first port on the TDM/ ATM Uplink ds1-channel-number: ----------> {1}: id: --------------------------> {0}: 1 identifier for first link, must match switch check-id: --------------------> {notactivated}: block: -----------------------> {unblocked}: v52-c-channel has 3 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n Using current values for elements 1-3 link-valid-flag: -------------> {invalid}: valid v52-link[2]: dsn-lg-id: -------------------> {1}: 15 linegroup ID of the second port on the TDM/ ATM Uplink
MALC Configuration Guide
505
Configuring GR-303 or V5.2 Interface Groups
ds1-channel-number: ----------> {1}: id: --------------------------> {0}: 2 identifier for second link, must match switch check-id: --------------------> {notactivated}: block: -----------------------> {unblocked}: v52-c-channel has 3 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n Using current values for elements 1-3 link-valid-flag: -------------> {invalid}: valid v52-link[3]: dsn-lg-id: -------------------> {1}: 17 linegroup ID of the third port on the TDM/ ATM Uplink ds1-channel-number: ----------> {1}: id: --------------------------> {0}: 3 identifier for third link, must match switch check-id: --------------------> {notactivated}: block: -----------------------> {unblocked}: v52-c-channel has 3 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n Using current values for elements 1-3 link-valid-flag: -------------> {invalid}: valid v52-link[4]: dsn-lg-id: -------------------> {1}: q Using current values for elements 4-16 v52-c-path has 48 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n Using current values for elements 1-48 .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Adding C-channels within links This example shows how to configure control channels for links you created in Provisioning V5.2 links on page 505. Control channels (C-channels) to pass management information between the switch and the MALC. There can be up to three C-channels per E1 link, on channel numbers 15, 16 and 31.
•
Enter 15, 16 or 31 for the time-slot-index option.
•
Enter the logical-channel-id. Each C-channel must have a unique numerical identifier.
•
Enter a protection-group name (optional).
•
Specify the role.
•
Set the c-channel-valid-flag to valid.
The following example shows one C-channel provisioned in v52-link number one, one in link number two, and two C-channels provisioned in link number three. zSH> update v52-interface-group 1 Please provide the following: [q]uit. name-id: ---------------------> {zhone}: ** read-only ** local-interface-id: ----------> {1}: local-prov-variant: ----------> {1}: prov-variant-request: --------> {norequest}: admin-status: ----------------> {outofservice}:
506
MALC Configuration Guide
Configuring a V5.2 interface
pstn-layer-3-start-address: --> {1}: isdn-env-func-start-address: -> {1}: port-alignment-request: ------> {norequest}: national-pstn-region: --------> {germany}: switch-vendor: ---------------> {siemens}: protocol-spec: ---------------> {edition2}: startup-check-link-id: -------> {false}: startup-unblock-user-ports: --> {false}: link-oos-timer: --------------> {2500}: link-is-timer: ---------------> {200}: v52-ig-lapv: max-outstanding-frames: ------> {7}: ** read-only ** n200: ------------------------> {3}: ** read-only ** n201: ------------------------> {260}: ** read-only ** t200: ------------------------> {1000}: ** read-only ** t203: ------------------------> {10}: ** read-only ** v52-link has 16 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? s Enter the array element to start: 1 v52-link[1]: dsn-lg-id: -------------------> {2}: ds1-channel-number: ----------> {1}: id: --------------------------> {1}: check-id: --------------------> {notactivated}: block: -----------------------> {unblocked}: v52-c-channel has 3 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? s Enter the array element to start: 1 v52-c-channel[1]: time-slot-index: -------------> {16}: logical-channel-id: ----------> {0}: 1 protection-group: ------------> {none}: group1 role: ------------------------> {active}: c-channel-valid-flag: --------> {invalid}: valid v52-c-channel[2]: time-slot-index: -------------> {16}: q Using current values for elements 2-3 link-valid-flag: -------------> {valid}: v52-link[2]: dsn-lg-id: -------------------> {4}: ds1-channel-number: ----------> {1}: id: --------------------------> {2}: check-id: --------------------> {notactivated}: block: -----------------------> {unblocked}: v52-c-channel has 3 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? s Enter the array element to start: 1 v52-c-channel[1]: time-slot-index: -------------> {16}: logical-channel-id: ----------> {0}: 2 protection-group: ------------> {none}: group1 role: ------------------------> {active}: standby c-channel-valid-flag: --------> {invalid}: valid v52-c-channel[2]: time-slot-index: -------------> {16}: q Using current values for elements 2-3 link-valid-flag: -------------> {valid}:
MALC Configuration Guide
507
Configuring GR-303 or V5.2 Interface Groups
v52-link[3]: dsn-lg-id: -------------------> {6}: ds1-channel-number: ----------> {1}: id: --------------------------> {3}: check-id: --------------------> {notactivated}: block: -----------------------> {unblocked}: v52-c-channel has 3 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? s Enter the array element to start: 1 v52-c-channel[1]: time-slot-index: -------------> {16}: logical-channel-id: ----------> {0}: 3 protection-group: ------------> {none}: role: ------------------------> {active}: c-channel-valid-flag: --------> {invalid}: valid v52-c-channel[2]: time-slot-index: -------------> {16}: q Using current values for elements 2-3 link-valid-flag: -------------> {valid}: q Using current values for elements 4-16 v52-c-path has 48 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n Using current values for elements 1-48 .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Provisioning C-paths You can set how the management information in the C-channel is communicated by provisioning the communication path (C-path). The C-path array is provisioned within the C-channel array. The C-path logical-channel-id number must match the logical-channel-id value you assigned for the C-channel in the Adding C-channels within links on page 506. For each C-path, follow these steps:
•
Assign a unique id number for each C-path.
•
Enter a type value. To communicate ISDN BRI management data for voice calls, use the isdnds option.
•
Assign the logical-channel-id number for the C-channel that the C-path is running over.
•
Each c-path-valid-flag must be set to valid to activate the C-path.
This example shows how to configure seven communications paths. The first four are in C-channel number one, the fifth and sixth are created in channel three, and the seventh is created in channel four. zSH> update v52-interface-group 1 Please provide the following: [q]uit. name-id: ---------------------> {zhone}: ** read-only ** local-interface-id: ----------> {1}: local-prov-variant: ----------> {1}: prov-variant-request: --------> {norequest}:
508
MALC Configuration Guide
Configuring a V5.2 interface
admin-status: ----------------> {outofservice}: pstn-layer-3-start-address: --> {1}: isdn-env-func-start-address: -> {1}: port-alignment-request: ------> {norequest}: national-pstn-region: --------> {germany}: switch-vendor: ---------------> {siemens}: protocol-spec: ---------------> {edition2}: startup-check-link-id: -------> {false}: startup-unblock-user-ports: --> {false}: link-oos-timer: --------------> {2500}: link-is-timer: ---------------> {200}: v52-ig-lapv: max-outstanding-frames: ------> {7}: ** read-only ** n200: ------------------------> {3}: ** read-only ** n201: ------------------------> {260}: ** read-only ** t200: ------------------------> {1000}: ** read-only ** t203: ------------------------> {10}: ** read-only ** v52-link has 16 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n Using current values for elements 1-16 v52-c-path has 48 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? s Enter the array element to start: 1 v52-c-path[1]: id: --------------------------> {1}: type: ------------------------> {unknown}: bcc bear channel connection logical-channel-id: ----------> {0}: 1 c-path-valid-flag: -----------> {invalid}: valid v52-c-path[2]: id: --------------------------> {1}: 2 type: ------------------------> {unknown}: ctrl control protocol logical-channel-id: ----------> {0}: 1 c-path-valid-flag: -----------> {invalid}: valid v52-c-path[3]: id: --------------------------> {1}: 3 type: ------------------------> {unknown}: lctl link control protocol logical-channel-id: ----------> {0}: 1 c-path-valid-flag: -----------> {invalid}: valid v52-c-path[4]: id: --------------------------> {1}: 4 type: ------------------------> {unknown}: pstn POTS signalling logical-channel-id: ----------> {0}: 1 c-path-valid-flag: -----------> {invalid}: valid v52-c-path[5]: id: --------------------------> {1}: 5 type: ------------------------> {unknown}: isdnds ISDN data signaling logical-channel-id: ----------> {0}: 1 c-path-valid-flag: -----------> {invalid}: valid v52-c-path[6]: id: --------------------------> {1}: q Using current values for elements 6-48 .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated
MALC Configuration Guide
509
Configuring GR-303 or V5.2 Interface Groups
Activating the V5.2 IG Activate the interface after provisioning is finished. The example activates an IG number 1: zSH> update v52-interface-group 1 V5.2 interface group number Please provide the following: [q]uit. name-id: ---------------------> {zhone}: ** read-only ** local-interface-id: ----------> {1}: local-prov-variant: ----------> {1}: prov-variant-request: --------> {norequest}: admin-status: ----------------> {outofservice}: inservice pstn-layer-3-start-address: --> {1}: isdn-env-func-start-address: -> {1}: port-alignment-request: ------> {norequest}: national-pstn-region: --------> {germany}: switch-vendor: ---------------> {siemens}: protocol-spec: ---------------> {edition2}: startup-check-link-id: -------> {false}: startup-unblock-user-ports: --> {false}: link-oos-timer: --------------> {2500}: link-is-timer: ---------------> {200}: v52-ig-lapv: max-outstanding-frames: ------> {7}: ** read-only ** n200: ------------------------> {3}: ** read-only ** n201: ------------------------> {260}: ** read-only ** t200: ------------------------> {1000}: ** read-only ** t203: ------------------------> {10}: ** read-only ** v52-link has 16 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n Using current values for elements 1-16 v52-c-path has 48 elements. Modify [a]ll, [n]one, a [s]ubset, or [q]uit? n Using current values for elements 1-48 .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
After the V5.2 IG is activated, proceed to configuring V5.2 subscribers. For information, see Configuring Voice on page 385.
Modifying the v52-interface-group profile If you need to modify the following parameters in the v52-interface-group profile, it can only be done using the v52config command:
•
prov-variant-request
•
admin-status (to set to restart only)
•
port-alignment-request
•
cchannelrole (to set to switchtostandby only)
The syntax of the command is as follows
510
MALC Configuration Guide
Configuring a V5.2 interface
v52config checklinkid/switchchan/restart/variant/block/ unblock INTERFACE_ID linkid/cchan/aligntype
The following table describes the arguments for the v52config command: Argument
Description
INTERFACE_ID
The local interface ID number. This is the value of the name-id parameter in the v52-interface-group profile.
linkid
Used with the checklinkid argument.
cchan
Used with the switchchan argument.
aligntype
Used with the block and unblock arguments. Can be isdn, pstn or all.
For example, to restart the interface (local-interface-id) named 100: zSH> v52config restart 100
To run a check link id on the interface named 100, with a linkid of 4: zSH> v52config checklinkid 100 4
Displaying V5.2 interface group status The voice status command can be used to display V5.2 IG status. zSH> voice status ig v52 one Status for v52 interface group one: Admin status = in service Oper status = inoperable Oper status cause = local disable Active calls = 0 Switch vendor = ericsson LinkId 0 TS 15 Channel status failed LinkId 0 TS 16 Channel status failed LinkId 1 TS 15 Channel status failed LinkId 1 TS 16 Channel status failed CPath 1 Oper status down CPath 2 Oper status down CPath 3 Oper status down CPath 4 Oper status down CPath 5 Oper status down zSH>
MALC Configuration Guide
511
Configuring GR-303 or V5.2 Interface Groups
512
MALC Configuration Guide
10
CONFIGURING THE MALC FOR VIDEO This chapter explains how to configure the MALC for video and includes the following sections:
•
Video routing, page 513
•
Video bridging, page 518
•
IGMP snooping with proxy reporting, page 522
Video routing When configuring an interface for IP video, you should dedicate a virtual circuit (vci/vpi for dsl and atm based transmissions) or VLANs (for Ethernet based transmissions) to deliver the IP video to the subscriber. Transmitting other types of traffic over the same virtual circuit or VLAN as video could affect the quality of the video. For bridged video, see Video bridging on page 518. Figure 64 shows a MALC video configuration. Figure 64: MALC video configuration
EPG server
Video
(Ethernet or DSL based)
CPE
MALC IP video server
MALC Configuration Guide
513
Configuring the MALC for video
Configuring an IP video connection between the MALC and the CPE The following example configures an IP video connection between the MALC and the CPE over an ADSL interface. The video is delivered over a bridged connection and the IP video server is reached via a GigaBit Ethernet uplink card. All these procedures are done on the MALC. 1
Create an IP interface on the MALC GigaBit Ethernet port with VLAN ID 999 for the IP video:
zSH> interface add 1-1-2-0/eth vlan 999 192.168.1.14/24 Created ip-interface-record ethernet2-999/ip
2
Create a mapping between the video connection and the multicast address space. The video-source profile specifies the interface the MALC uses to reach the IP video server. (The following example uses the uplink interface to reach the IP video server). Multisource multicast enables IGMP join/leaves to the video headend for each configured video-source profile. One video-source profile is assigned to each GigE uplink interface. zSH> new video-source 1 Please provide the following: [q]uit. routing-domain: ----> {0}: 1 multicast-address: -> {0.0.0.0}: 224.1.1.1 ifIndex: -----------> { }: ethernet2-999/ip vpi: ---------------> {0}: vci: ---------------> {0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Note: You only need to enter the first multicast address in the group. You can also use the videosource command to configure the mapping between the video connection and the multicast address space. zSH> videosource add 224.1.1.1 1-1-2-0/ip Added video-source profile zSH> videosource show Domain: 0 multicastAddr: 224.1.1.1 IfName: 1-1-2-0/ip zSH> get video-source 1 Please provide the following: [q]uit. routing-domain: ----> {1}: multicast-address: -> {224.1.1.1}: ifIndex: -----------> {ethernet2-999/ip}: vpi: ---------------> {0}: vci: ---------------> {0}: ....................
514
MALC Configuration Guide
Video routing
Use the videosource delete command to remove a video source: zSH> videosource delete 224.1.1.1 1-1-2-0/ip Deleted video-source profile
3
Create a traffic descriptor for IP video (this example is for ADSL2+): zSH> new atm-traf-descr 2 index can be any value Please provide the following: [q]uit. td_type: -----------------> {atmNoClpNoScr}: td_param1: ---------------> {0}: 44080 td_param2: ---------------> {0}: td_param3: ---------------> {0}: td_param4: ---------------> {0}: td_param5: ---------------> {0}: cac-divider: -------------> {1}: td_service_category: -----> {ubr}: cbr td_frame_discard: --------> {false}: usage-parameter-control: -> {true}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
4
Create an IP unnumbered interface. This is the interface that video set top boxes will use for their far end address. zSH> new ip-interface-record 192.168.49.1/ip Please provide the following: [q]uit. vpi: ---------------> {0}: vci: ---------------> {0}: rdindex: -----------> {1}: dhcp: --------------> {none}: ** read-only ** addr: --------------> {0.0.0.0}: 192.168.49.1 netmask: -----------> {0.0.0.0}: 255.255.255.0 bcastaddr: ---------> {0.0.0.0}: 192.168.49.255 destaddr: ----------> {0.0.0.0}: farendaddr: --------> {0.0.0.0}: mru: ---------------> {1500}: reasmmaxsize: ------> {0}: ingressfiltername: -> {}: egressfiltername: --> {}: pointtopoint: ------> {no}: mcastenabled: ------> {yes}: ipfwdenabled: ------> {yes}: mcastfwdenabled: ---> {yes}: natenabled: --------> {no}: bcastenabled: ------> {yes}: ingressfilterid: ---> {0}: egressfilterid: ----> {0}: ipaddrdynamic: -----> {static}: dhcpserverenable: --> {false}: subnetgroup: -------> {0}: unnumberedindex: ---> {0}: mcastcontrollist: --> {}:
MALC Configuration Guide
515
Configuring the MALC for video
vlanid: ------------> {0}: maxVideoStreams: ---> {0}: tosOption:---------> disable originate all tosCOS:------------> {0 - 7 vlanCOS:-----------> {0 - 7} .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Note: The MALC may display a message that there is nothing to bind to. This message is informational. Continue with this procedure. zSH> new ip-unnumbered-record 2 Please provide the following: [q]uit. ipUnnumberedInterfaceName: -> { }: 192.168.49.1/ip .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
5
To create a DHCP server address pool for the far end video set top device, use the dhcp-relay command to create a relay agent. The subnet address/ mask will be derived from the system's floating IP address, if present, or may be specified NULL for use only with bridged interfaces. If multiple floating IP records are present, the desired / may be specified. The range (or pool) of assignable addresses which that customer can be assigned can be specified in the dhcp-server-subnet profile. zSH> dhcp-relay add Operation completed successfully.
This network must specify the network for the IP video server. This example configures the MALC for DHCP relay on subnet 2 using Myrio server (192.168.88.73) at domain nat.myrio.net. The unnumbered IP address of the default router is 192.168.49.1. To make advanced modifications to the DHCP settings, edit the dhcp-server-subnet profile. zSH> update dhcp-server-subnet 2 Please provide the following: [q]uit. network: ---------------> {0.0.0.0}: netmask: ---------------> {0.0.0.0}: domain: ----------------> {0}: range1-start: ----------> {0.0.0.0}: range1-end: ------------> {0.0.0.0}: range2-start: ----------> {0.0.0.0}: range2-end: ------------> {0.0.0.0}: range3-start: ----------> {0.0.0.0}: range3-end: ------------> {0.0.0.0}: range4-start: ----------> {0.0.0.0}:
516
MALC Configuration Guide
192.168.49.0 255.255.255.0 192.168.49.5 192.168.49.10
Video routing
range4-end: ------------> {0.0.0.0}: default-lease-time: ----> {-1}: min-lease-time: --------> {-1}: max-lease-time: --------> {-1}: boot-server: -----------> {0.0.0.0}: 192.168.88.73 bootfile: --------------> {}: default-router: --------> {0.0.0.0}: 192.168.49.1 ip-unnumbered interface primary-name-server: ---> {0.0.0.0}: boot-server: -----------> {0.0.0.0}: 192.168.88.73 secondary-name-server: -> {0.0.0.0}: domain-name: -----------> {}: nat.myrio.net subnetgroup: -----------> {0}: 2 stickyaddr: ------------> {enable}: external-server: -------> {0.0.0.0}: 192.168.88.73 external DHCP server address .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
6
Create a multicast control list, which defines which multicast addresses the remote end video can access. A multicast control list entry of 0 enables subscriptions up to the number of maximum video streams on the interface without control list checking. Video streams can be configured on GigE and other interfaces. The following example adds three entries to multicast list 1: zSH> new mcast-control-entry 1/1 Please provide the following: [q]uit. ip-address: -> {0.0.0.0}: 224.1.1.1 type: -------> {normal}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved. zSH> new mcast-control-entry 1/2 Please provide the following: [q]uit. ip-address: -> {0.0.0.0}: 224.1.1.2 type: -------> {perodic}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved. zSH> new mcast-control-entry 1/3 Please provide the following: [q]uit. ip-address: -> {0.0.0.0}: 224.1.1.3 type: -------> {always-on}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Continue adding as many multicast entries as necessary.
MALC Configuration Guide
517
Configuring the MALC for video
To view the multicast control group, use the mcast show command: zSH> mcast show mcl 1 MCAST CONTROL LIST : 1 224.1.1.1 224.1.1.5 224.10.10.10
224.1.1.2 224.1.1.6 224.10.10.11
224.1.1.3 224.1.1.7 224.10.10.12
224.1.1.4 224.1.1.8 224.10.10.13
Note: The ip igmpstat command displays the ports receiving multicast traffic and the joined multicast group(s). 7
Add a host route for the video interface. A multicast control list entry of 0 (for example, video 0/100) enables subscriptions up to the number of maximum video streams on the interface without control list checking. For ADSL:
zSH> host add 1-1-5-0/adsl vc 0/36 td 2 dynamic 1 4 video 1/4
These examples assume 1 is the multicast control list index and 4 is the maximum number of IP video streams (from the IP interface record). 8
Activate the MALC port. ADSL: zSH> update if-translate 1-1-5-0/adsl Please provide the following: [q]uit. ifIndex: -----------> {38}: shelf: -------------> {1}: slot: --------------> {4}: port: --------------> {1}: subport: -----------> {0}: type: --------------> {adsl}: adminstatus: -------> {down}: up physical-flag: -----> {true}: iftype-extension: --> {none}: ifName: ------------> {1-4-1-0}: redundancy-param1: -> {0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Video bridging Video bridging enables video packets to be forwarded over bridges from a headend device down to a host. In this case, the video travels from the source, or head-end device, using one video stream to passively traverse the MALC backplane. This lowers the bandwidth requirements for video packets traversing the MALC.
518
MALC Configuration Guide
Video bridging
Uplink and downlink video bridging Video bridging requires configuring an uplink bridge and a downlink bridge. On the uplink bridge, the forwardToMulticast function is associated with a location that contains video content allowing the MALC to receive video streams from the network. An interface with this value set to true only transmits multicast traffic for which a JOIN request was received. A bridge interface with the forwardToMulticast parameter set to false discards multicast traffic. By default, the forwardToMulticast parameter is set to true on uplink bridges. On the downlink bridge, the learnMulticast function is associated with interfaces that have hosts connected to them and allows the MALC to send video groups from downlink interfaces to the network. By default, the learnMulticast parameter is set to true on downlink bridges. Note that JOIN operations enter on a learnMulticast interface associated with a downlink bridge and pass through on a forwardToMulticast interface associated with an uplink bridge. Table 32 details various video bridge behaviors associated with different combinations of settings for the bridge parameters. Table 32: learnMulticast-forwardToMulticast combinations and behavior learnMulticast
forwardToMulticast
Behavior
False
False
The interface discards all incoming multicast packets and does not forward any of the packets.
True
False
The interface forwards both default multicast signaling packets an control multicast packets.
True
False
The interface discards incoming multicast content groups and forwards requested content groups.
False
True
The interface forwards control packets received on this interface to all other interfaces that have the learnMulticast field set to true.
False
True
The interface forwards content groups only to interfaces that have sent JOIN messages for a group.
True
True
Treat the same as an interface with the learnMulticast field set to false and the forwardToMulticast field set to true.
The following video bridge example creates a video bridge on a uplink card using a uplink GigE interface as the uplink bridge. To create the bridge path on an interface, enter the multicast aging period and the IGMP query interval. Create the uplink bridge: zSH> bridge add 1-1-2-0/eth uplink vlan 77 Adding bridge on 1-1-2-0/eth
MALC Configuration Guide
519
Configuring the MALC for video
Created bridge-interface-record ethernet2-77/bridge
Add the bridge path and a multicast aging period and IGMP query interval. zSH> bridge-path add ethernet2-77/bridge vlan 77 default mcast 90 igmpqueryinterval 30 Bridge-path added successfully
For the downlink bridge, add a downlink bridge and specify a maximum number of video streams and multicast control list. To do so, add the values for the multicast control list and the maximum video streams in the m/n format. Set the multicast control list first and the maximum video streams second. Members of the multicast control list must be defined to receive the video signal. In this case a downlink bridge is created first for data and then on the same downlink and the same VLAN ID for video: First for data: zSH> bridge add 1-1-4-0/adsl vc 0/35 td 1 downlink vlan 55 Adding bridge on 1-1-4-0/adsl Created bridge-interface-record 1-1-4-0-adsl-0-35/bridge
Then for video: zSH> bridge add 1-1-4-0/adsl vc 0/36 td 2 downlink vlan 55 video 1/2 Adding bridge on 1-1-4-0/adsl Created bridge-interface-record 1-1-4-0-adsl-0-36/bridge
To verify bridge settings, use the get bridge-interface-record command for each bridge. This command displays the bridge settings, including the learnMulticast and forwardToMulticast. For the uplink bridge, note that the forwardToMulticast setting is true and the learnMulticast setting is false. zSH> get bridge-interface-record ethernet2-77/bridge bridge-interface-record ethernet2-77/bridge vpi: ---------------------------------> {0} vci: ---------------------------------> {0} vlanId: ------------------------------> {77} stripAndInsert: ----------------------> {false} customARP: ---------------------------> {true} filterBroadcast: ---------------------> {true} learnIp: -----------------------------> {false} learnUnicast: ------------------------> {false} maxUnicast: --------------------------> {0} learnMulticast: ----------------------> {false} forwardToUnicast: --------------------> {true} forwardToMulticast: ------------------> {true} forwardToDefault: --------------------> {false} bridgeIfCustomDHCP: ------------------> {true} bridgeIfIngressPacketRuleGroupIndex: -> {0} vlanIdCOS: ---------------------------> {0} outgoingCOSOption: -------------------> {disable}
520
MALC Configuration Guide
Video bridging
outgoingCOSValue: --------------------> s-tagTPID: ---------------------------> s-tagId: -----------------------------> s-tagStripAndInsert: -----------------> s-tagOutgoingCOSOption: --------------> s-tagIdCOS: --------------------------> s-tagOutgoingCOSValue: ---------------> mcastControlList: --------------------> maxVideoStreams: ---------------------> isPPPoA: -----------------------------> floodUnknown: ------------------------> floodMulticast: ----------------------> bridgeIfEgressPacketRuleGroupIndex: --> bridgeIfTableBasedFilter: ------------> bridgeIfDhcpLearn: ------------------->
{0} {0x8100} {0} {true} {s-tagdisable} {0} {0} {} {0} {false} {false} {false} {0} {NONE(0)} {NONE(0)}
For the downlink bridge, note that the forwardToMulticast setting is false and the learnMulticast setting is true. zSH> get bridge-interface-record 1-1-4-0-adsl-0-36/bridge bridge-interface-record 1-1-4-0-adsl-0-36/bridge vpi: ---------------------------------> {0} vci: ---------------------------------> {36} vlanId: ------------------------------> {55} stripAndInsert: ----------------------> {true} customARP: ---------------------------> {false} filterBroadcast: ---------------------> {false} learnIp: -----------------------------> {true} learnUnicast: ------------------------> {true} maxUnicast: --------------------------> {5} learnMulticast: ----------------------> {true} forwardToUnicast: --------------------> {false} forwardToMulticast: ------------------> {false} forwardToDefault: --------------------> {true} bridgeIfCustomDHCP: ------------------> {false} bridgeIfIngressPacketRuleGroupIndex: -> {0} vlanIdCOS: ---------------------------> {0} outgoingCOSOption: -------------------> {disable} outgoingCOSValue: --------------------> {0} s-tagTPID: ---------------------------> {0x8100} s-tagId: -----------------------------> {0} s-tagStripAndInsert: -----------------> {true} s-tagOutgoingCOSOption: --------------> {s-tagdisable} s-tagIdCOS: --------------------------> {0} s-tagOutgoingCOSValue: ---------------> {0} mcastControlList: --------------------> {1} maxVideoStreams: ---------------------> {2} isPPPoA: -----------------------------> {false} floodUnknown: ------------------------> {false} floodMulticast: ----------------------> {false} bridgeIfEgressPacketRuleGroupIndex: --> {0} bridgeIfTableBasedFilter: ------------> {NONE(0)} bridgeIfDhcpLearn: -------------------> {NONE(0)}
MALC Configuration Guide
521
Configuring the MALC for video
In addition, you can run a bridge igmp command to determine whether IGMP is running on the system. zSH> bridge igmp VlanID MAC Address MCAST IP Ifndx Host MAC Last Join ---------------------------------------------------------------------------999 01:00:5e:02:7f:fe 224.2.127.254 921 00:02:02:0b:4a:a0 2 999 01:00:5e:02:7f:fe 224.2.127.254 922 00:02:02:0a:bb:6d 106 999 01:00:5e:02:7f:fe 224.2.127.254 923 00:02:02:0a:c0:b7 87 999 01:00:5e:02:7f:fe 224.2.127.254 924 00:02:02:0b:4e:c5 172 999 01:00:5e:02:7f:fe 224.2.127.254 925 00:02:02:0b:4c:7e 65 999 01:00:5e:02:7f:fe 224.2.127.254 926 00:02:02:0b:4f:08 46 999 01:00:5e:02:7f:fe 224.2.127.254 927 00:02:02:09:c1:7d 90 999 01:00:5e:02:7f:fe 224.2.127.254 928 00:02:02:0b:44:cd 71 999 01:00:5e:02:7f:fe 224.2.127.254 929 00:02:02:0b:4c:ca 61 999 01:00:5e:02:7f:fe 224.2.127.254 930 00:02:02:0b:47:bd 7 999 01:00:5e:02:7f:fe 224.2.127.254 931 00:02:02:0b:47:c7 177 999 01:00:5e:02:7f:fe 224.2.127.254 932 00:02:02:0b:4d:35 181 999 01:00:5e:02:7f:fe 224.2.127.254 933 00:02:02:0b:4d:5b 144 999 01:00:5e:02:7f:fe 224.2.127.254 934 00:02:02:0b:4a:a5 59 999 01:00:5e:02:7f:fe 224.2.127.254 935 00:02:02:0b:4c:9e 3 999 01:00:5e:02:7f:fe 224.2.127.254 936 00:02:02:09:c1:78 6 999 01:00:5e:02:7f:fe 224.2.127.254 937 00:02:02:0a:c0:ca 131
IGMP snooping with proxy reporting IGMP snooping applies to bridged video. Enabling IGMP snooping reduces traffic between the MALC and the upstream multicast headend device by changing the behavior of the MALC. MALC IGMP snooping also supports the following:
522
MALC Configuration Guide
•
Solicited or unsolicited query reports.
•
Ability to configure the MALC to send queries to hosts; by default the MALC does not.
•
Queries are sent only to hosts that have sent a join request.
•
Compliance with rfc4541 regarding IGM forwarding and data rules.
•
Information table is available during redundant uplink card switchovers.
•
Membership reports on downlink bridges are not forwarded.
•
When join requests are received without a leave, it is assumed that the set top box is watching both channel.
•
MALC IGMP snooping supports existing Max Video Streams and Multicast Control List functionality.
•
Using the IP on a bridge IP address when a join request is sent to the upstream multicast headend device.
Video bridging
Join requests When you enable IGMP snooping, join requests from hosts are not forwarded by the MALC to the multicast headend device, but are tracked by the MALC in an information table where hosts are organized into a group. When a host sends a join request that is the first join request of the group, the MALC terminates the join request from the host then originates a join request and sends it to the multicast headend device along with an IP address of 0.0.0.0 and a MAC address. Note: The configured IP on a bridge IP address can be sent instead of 0.0.0.0. This provides the upstream multicast headend device the ability to distinguish between downstream MALCs for debugging purposes. Figure 65: MALC and multicast head end device join and leave requests Multicast headend device
MALC
Host 1
Host 2
Host 3
Leave requests When you enable IGMP snooping, leave requests from hosts are not forwarded by the MALC to the multicast headend device, but are tracked by the MALC in an information table where hosts are organized into a group. When a host sends a leave request that is the last leave request of the group, the MALC terminates the leave request from the host then originates a leave request and sends it to the multicast headend device. All leave requests, regardless of whether they are the last leave request of the group, or any earlier leave requests, are terminated on the MALC. In this way, the multicast headend device starts and stops video transmission by processing requests sent directly from the MALC and not from downstream hosts.
MALC Configuration Guide
523
Configuring the MALC for video
IGMP snooping with proxy configuration commands Enabling IGMP snooping To enable IGMP snooping with proxy, enter bridge-path-add interface/type vlan vlan-id igmpsnooping enable: The default is disable. zSH> bridge-path add vlan default igmpsnooping enable| disable
For example, first create an uplink bridge, then enable igmpsnooping when adding the bridge path: zSH> bridge add 1-1-2-0/eth uplink vlan 80 Adding bridge on 1-1-2-0/eth Created bridge-interface-record ethernet2-80/bridge zSH> bridge-path add ethernet2-80/bridge vlan 80 default igmpsnooping enable Bridge-path added successfully
Implementing IGMP query To enable sending query messages to the host and to display the video streams the system, line card, port, or host are viewing, enter bridge-path-add enable igmpqueryinterval timer: The igmpqueryinterval indicates a time value in milliseconds. This value should be greater than 0. If you enter 0, the querying function is disabled. zSH> bridge-path add vlan default igmpsnooping enable igmpqueryinterval
For example, first create the uplink bridge, then enable igmpsnooping and set the igmpqueryinterval timer: zSH> bridge add 1-1-2-0/eth uplink vlan 200 Adding bridge on 1-1-2-0/eth Created bridge-interface-record ethernet2-200/bridge zSH> bridge-path add ethernet2-200/bridge vlan 200 default igmpsnooping enable igmpqueryinterval 1 Bridge-path added successfully
Enabling IGMP send IP address To enable the MALC to send the IP address used for IP on a bridge instead of 0.0.0.0, enter bridge-path-add vlan
524
MALC Configuration Guide
IGMP snooping with proxy reporting
igmpsnooping enable igmpsendip enable | disable and set the igmpsendip parameter to enable as follows: Note: If you have not configured IP on a bridge on this MALC, a warning is displayed that there is no IP address to use. zSH> bridge-path-add vlan default igmpsnooping enable igmpsendip enable
To disable igmpsendip, enter disable. To send the IP address of 0.0.0.0 enter igmpsendip disable.
Displaying igmp bridge statistics To display statistics for the IGMP bridge, enter bridge show igmpstats : zSH> bridge show igmpstats
Displaying video streams and the number of viewers viewing each stream 1
To view the streams and the number of subscribers viewing each stream, enter bridge show igmpstats streams:
zSH> bridge show igmpstats streams
2
To view each stream, the number of subscribers, and a list of subscribers for each stream enter bridge show igmpstats streams verbose:
zSH> bridge show igmpstats streams verbose
Displaying the video stream watched by a specified user Enter bridge show igmpstats : zSH> bridge show igmpstats
IGMP snooping with proxy reporting IGMP snooping applies to bridged video. Enabling IGMP snooping reduces traffic between the MALC and the upstream multicast headend device by changing the behavior of the MALC. MALC IGMP snooping also supports the following:
•
Solicited or unsolicited query reports.
•
Ability to configure the MALC to send queries to hosts; by default the MALC does not.
•
Queries are sent only to hosts that have sent a join request.
MALC Configuration Guide
525
Configuring the MALC for video
•
Compliance with rfc4541 regarding IGM forwarding and data rules.
•
Information table is available during redundant uplink card switchovers.
•
Membership reports on downlink bridges are not forwarded.
•
When join requests are received without a leave, it is assumed that the set top box is watching both channel.
•
MALC IGMP snooping supports existing Max Video Streams and Multicast Control List functionality.
•
Using the IP on a bridge IP address when a join request is sent to the upstream multicast headend device.
Join requests When you enable IGMP snooping, join requests from hosts are not forwarded by the MALC to the multicast headend device, but are tracked by the MALC in an information table where hosts are organized into a group. When a host sends a join request that is the first join request of the group, the MALC terminates the join request from the host then originates a join request and sends it to the multicast headend device along with an IP address of 0.0.0.0 and a MAC address. Note: The configured IP on a bridge IP address can be sent instead of 0.0.0.0. This provides the upstream multicast headend device the ability to distinguish between downstream MALCs for debugging purposes. Figure 66: MALC and multicast head end device join and leave requests Multicast headend device
MALC
Host 1
526
MALC Configuration Guide
Host 2
Host 3
IGMP snooping with proxy reporting
Leave requests When you enable IGMP snooping, leave requests from hosts are not forwarded by the MALC to the multicast headend device, but are tracked by the MALC in an information table where hosts are organized into a group. When a host sends a leave request that is the last leave request of the group, the MALC terminates the leave request from the host then originates a leave request and sends it to the multicast headend device. All leave requests, regardless of whether they are the last leave request of the group, or any earlier leave requests, are terminated on the MALC. In this way, the multicast headend device starts and stops video transmission by processing requests sent directly from the MALC and not from downstream hosts.
IGMP snooping with proxy configuration commands Enabling IGMP snooping To enable IGMP snooping with proxy, enter bridge-path-add interface/type vlan vlan-id igmpsnooping enable: The default is disable. zSH> bridge-path add vlan default igmpsnooping enable| disable
For example, first create an uplink bridge, then enable igmpsnooping when adding the bridge path: zSH> bridge add 1-1-2-0/eth uplink vlan 80 Adding bridge on 1-1-2-0/eth Created bridge-interface-record ethernet2-80/bridge zSH> bridge-path add ethernet2-80/bridge vlan 80 default igmpsnooping enable Bridge-path added successfully
Implementing IGMP query To enable sending query messages to the host and to display the video streams the system, line card, port, or host are viewing, enter bridge-path-add enable igmpqueryinterval timer: The igmpqueryinterval indicates a time value in milliseconds. This value should be greater than 0. If you enter 0, the querying function is disabled. zSH> bridge-path add vlan default igmpsnooping enable igmpqueryinterval
For example, first create the uplink bridge, then enable igmpsnooping and set the igmpqueryinterval timer:
MALC Configuration Guide
527
Configuring the MALC for video
zSH> bridge add 1-1-2-0/eth uplink vlan 200 Adding bridge on 1-1-2-0/eth Created bridge-interface-record ethernet2-200/bridge zSH> bridge-path add ethernet2-200/bridge vlan 200 default igmpsnooping enable igmpqueryinterval 1 Bridge-path added successfully
Enabling IGMP send IP address To enable the MALC to send the IP address used for IP on a bridge instead of 0.0.0.0, enter bridge-path-add vlan igmpsnooping enable igmpsendip enable | disable and set the igmpsendip parameter to enable as follows: Note: If you have not configured IP on a bridge on this MALC, a warning is displayed that there is no IP address to use. zSH> bridge-path-add vlan default igmpsnooping enable igmpsendip enable
To disable igmpsendip, enter disable. To send the IP address of 0.0.0.0 enter igmpsendip disable.
Displaying igmp bridge statistics To display statistics for the IGMP bridge, enter bridge show igmpstats : zSH> bridge show igmpstats
Displaying video streams and the number of viewers viewing each stream 1
To view the streams and the number of subscribers viewing each stream, enter bridge show igmpstats streams:
zSH> bridge show igmpstats streams
2
To view each stream, the number of subscribers, and a list of subscribers for each stream enter bridge show igmpstats streams verbose:
zSH> bridge show igmpstats streams verbose
Displaying the video stream watched by a specified user Enter bridge show igmpstats : zSH> bridge show igmpstats
528
MALC Configuration Guide
11
GIGABIT ETHERNET UPLINKS This chapter describes the MALC-UPLINK-2-GE and MALC-UPLINK-2-FE/GE uplink cards and explains how to configure them. It includes:
•
Overview, page 530
•
GigE and FE/GigE uplink card configuration, page 534
•
Small form factor pluggables, page 545
•
802.3ad link aggregation, page 546 Note: Uplink cards must be installed in slot 1 or slot 2 of the MALC chassis.
MALC Hardware Installation Guide
529
Gigabit Ethernet Uplinks
active fault pwr fail
active fault pwr fail
active fault pwr fail
Overview
2 P O R T F E/ G E T D M U P
Gigabit Ethernet Uplink
8X T1
2 Port FE/GE UPLINK
E1 T D M
C R A F T
C R A F T
C R A F T
10 100
10 100
R D N T A
R D N T A
100
R D N T
R D N T B
R D N T B
P O R T 1
P O R T 1
P O R T 1
P O R T 2
ma0526
2 Port FE/GE TDM UP
ma0501
P O R T 2
P O R T 2
2 Port FE/GE UPLINK ma0501
10
The MALC supports the following GigE cards:
•
MALC-UPLINK-2-GE-ONLY (without TDM ports)
•
MALC-UPLINK-2-GE (with TDM ports)
•
MALC-UPLINK-2-FE/GE (without TDM ports)
•
MALC-UPLINK-2-FE/GE-TDM (with TDM ports)
The MALC-Uplink-2-GE and MALC-Uplink-2-GE-ONLY uplink cards provide high-speed GigaBit Ethernet interfaces for resilient packet ring (RPR) networks. The MALC-UPLINK-2-FE/GE and MALC-UPLINK-2-FE/ GE-TDM cards provide the same functionality as with the addition for 100 Mbps Fast Ethernet (FE) uplink support. These GE and FE/GE cards provide the following interfaces:
530
MALC Hardware Installation Guide
Overview
•
One 10/100 Ethernet interface for management.
•
Two Gigabit Ethernet interfaces. These interfaces can be used for RPR or high speed data applications. The interfaces support a number of small form factor pluggables (SFPs) that enable the card to interface with a variety of media types. (For more information see Small form factor pluggables on page 545.)
•
Card redundancy On the MALC-Uplink-2-GE and MALC-Uplink-2-GE-ONLY cards, redundancy is supported through a redundant cable connecting the RDNT ports. On the MALC-UPLINK-2-FE/GE cards redundancy is supported through a redundant cross-over cable connecting the RDNT A and RDNT B ports.
•
Optional TDM connector for eight T1/E1 TDM ports that support either GR-303 or V5.2. Available on only the MALC-UPLINK-2-GE and MALC-UPLINK-2-FE/GE-TDM cards. Note: Pulse dialing is not supported on the TDM/ATM uplink card.
Table 33: Uplink-2-GE and Uplink-2-FE/GE specifications Specification
Description
Size
1 slot
Physical interfaces
TDM T1/E1: DB 44 pin connector. (only on cards with TDM support) Two Gigabit Ethernet ports with SFPs. Additional 100 Mbps support on the MALC-UPLINK-2-FE/GE cards. The SFPs can be twisted pair 1000baseT or fiber (SX, LX or ZX). See Small form factor pluggables on page 545. The optical interfaces are class 1 Laser International Safety Standard IEC 825 compliant RJ45 Ethernet 10/100 Ethernet interface for management RS232D serial craft interface
Standards supported
AF-PHY-0086.001 GR-303-CORE G.965 and ETSI EN 300 347-1 V2.2.2 (V5.2) Gigabit Ethernet (GE) IEEE 802.3
TDM line characteristics
Supervisory signaling is Extended Superframe (ESF) – CAS signaling
MALC Hardware Installation Guide
531
Gigabit Ethernet Uplinks
Table 33: Uplink-2-GE and Uplink-2-FE/GE specifications (Continued) Specification
Description
TDM capacity
2 GR-303 interface groups (IGs) 8 channelized T1s per card 4096 maximum GR-303 call reference values (CRVs) per system
Voice processing
AAL2 SAR for converting TDM bus voice traffic to ATMG.711 encoding only ATMF Loop Emulation Standard
Management interface
RS-232D serial craft port AAL5 Management VC termination (RFC 1483 routed) for ATM in-band management Management Ethernet 10/100 port routable for connecting to other Ethernet devices SNMP
Redundancy
Card redundancy 1+1 TDM T1/E1 interface redundancy (with Y cable). APS 1:1 bi-directional and 1+1 (with Y cable).
Power consumption
50 W
The following card-line-types are supported:
•
rpr: RPR data-only mode (default)
•
rpr-t1-gr303: RPR with data and GR-303 voice
•
rpr-e1-v52: RPR with data and V5.2 voice
•
rpr-t1cas: RPR with data and T1 CAS voice
•
ds1: linear Ethernet with T1s.
•
e1: linear Ethernet with E1s.
•
t1cas: linear Ethernet with T1 channel banks.
Table 34 provides the card types for the MALC FE/GE uplink cards. Table 34: FE/GE uplink card types
532
Card
Type
MALC-UPLINK-2-GE-ONLY (without TDM ports)
5066
MALC-UPLINK-2-GE (with TDM ports)
5041
MALC-UPLINK-2-FE/GE (without TDM ports)
5091
MALC-UPLINK-2-FE/GE-TDM (with TDM ports)
5090
MALC Hardware Installation Guide
Overview
Redundant MALC-UPLINK-2-GE uplink card cable On the MALC -UPLINK-2-GE cards, use the redundant GigE uplink card cable (MALC-CBL-GE-RED) (Figure 67) to connect the RDNT port on the active GigE uplink card to the RDNT port on the redundant GigE uplink card in RPR configurations. Figure 67: Redundant GE uplink card cable
R D N T
ma0701
R D N T
Redundant MALC-UPLINK-2-FE/GE uplink card cable On the MALC -UPLINK-2-FE/GE cards, use a standard crossover Ethernet cable (MALC-CBL-FE/GE-RED) (Figure 68) to connect the RDNT A and RDNT B ports on the active GigE uplink card to the RDNT B and RDNT A ports on the redundant GigE uplink card for redundant RPR configurations. Figure 68: Redundant FE/GE uplink card cable
R D N T A
R D N T B
ma0710
R D N T B
R D N T A
Redundant FE/GigE TDM port cabling For TDM port redundancy on the MALC FE/GigE cards with TDM support, use the MALC-CBL-GE/O12CRD-TDM-8-R cable. Connector P1 connects to the active FE/GigE uplink card. Connector P4 connects to the redundant
MALC Hardware Installation Guide
533
Gigabit Ethernet Uplinks
FE/GigE uplink card. Connectors P2 and P3 connect to the subscriber ports. For connector pinouts, see Redundant GigE port pinouts on page 90. Figure 69: Redundant FE/GigE TDM port cable
r ts Po
7-8
P3
P4
r ts Po
1-6
P2
ma
1
06
06
P1
25 1
15
16
30
31
44
50
26
GigE and FE/GigE uplink card configuration This section describes configuration procedures for the GigE and FE/Gige uplink card. If these procedures are required, they should be done before provisioning the system. This section includes:
•
Configuring redundant uplink cards on page 535
•
Adding GigE and FE/GigE cards to the primary uplink node on page 537
•
Adding redundant uplink cards to RPR nodes on page 539
•
Adding Gigabit Ethernet uplink cards in linear mode on page 539
•
Configuring redundant uplink cards in linear mode on page 541
•
Changing the RPR line type on page 542
•
Enabling clocking for GigE and FE/GigE uplink cards on page 543 Note: For information about creating an RPR ring, refer to the MALC Configuration Guide.
534
MALC Hardware Installation Guide
GigE and FE/GigE uplink card configuration
Configuring redundant uplink cards Caution: When adding redundant uplink cards, note the following: You must configure redundant physical interfaces on both the active and standby cards. This applies to all uplink cards. In addition, you must manually keep the configuration of the physical interfaces on the active and standby cards in sync. Redundant uplink cards must be of the same type. Each card must be running the same software version and have the same size flash card. Note: When configuring the redundant uplink card, the settings in the card-profile for the both cards must be identical. To add a redundant uplink card to the system: 1
Verify that active card has been configured with the same card-group-id that is to be used for the standby card.
2
Install a second uplink card in slot 2.
3
Create a card-profile for the second uplink card: By default, the GigE and FE/GigE cards are configured to carry data-only traffic. You can modify the GigE and FE/GigE cards to specify that the RPR ring carry voice and data traffic by modifying the card-line-type in the card-profile. The following line types are supported:
zSH> card add
–
rpr: RPR data-only mode (default)
–
rpr-t1-gr303: RPR with data and GR-303 voice
–
rpr-e1-v52: RPR with data and V5.2 voice
–
rpr-t1cas: RPR with data and T1 CAS voice
–
ds1: linear Ethernet with T1s.
–
e1: linear Ethernet with E1s.
–
t1cas: linear Ethernet with channel banks.
1/2/5041linetype rpr
or zSH> new card-profile 1/2/5041 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {malcrprgige.bin}: admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}:
MALC Hardware Installation Guide
535
Gigabit Ethernet Uplinks
card-group-id: --------> {1}: enter the same redundancy group ID as the working uplink card hold-active: ----------> {false}: weight: ---------------> {nopreference}: assign a weight, if desired card-line-type: -------> {unknowntype}: rpr card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Optionally, using the MALC-UPLINK-2-GE-ONLY card: zSH> card add 1/2/5066
or zSH> new card-profile 1/2/5066 Please provide the following: [q]uit. sw-file-name: -----------> {malcrprgigent.bin}: admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {true}: sw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}:enter the same redundancy group ID as the working uplink card hold-active: ------------> {false}: weight: -----------------> {nopreference}: assign a weight, if desired card-line-type: ---------> {unknowntype}: card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: maxvpi-maxvci: ----------> {notapplicable}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Optionally, using the MALC-UPLINK-2-FE/GE card: zSH> card add 1/2/5090
or zSH> new card-profile 1/2/5090 Please provide the following: [q]uit. sw-file-name: -----------> {malcupfegerprtdm.bin}: admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {true}: sw-upgrade-enable: ------> {false}:
536
MALC Hardware Installation Guide
GigE and FE/GigE uplink card configuration
card-group-id: ----------> {0}:enter the same redundancy group ID as the working uplink card hold-active: ------------> {false}: weight: -----------------> {nopreference}: assign a weight, if desired card-line-type: ---------> {unknowntype}: card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: maxvpi-maxvci: ----------> {notapplicable}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
4
Connect the redundant cables.
Once the card-profile has been saved, the standby card comes up and the configuration and routing tables from the primary card are copied over.
Adding GigE and FE/GigE cards to the primary uplink node RPR requires two uplink cards in the MALC functioning as the primary uplink node. Each of these uplink cards in the primary uplink node must use the same card-group-id and the same card-line-type. This example configuration uses the MALC-UPLINK-2-GE card. 1
Update the card profile for the uplink card:
zSH> update card-profile 1/1/5041 shelf/slot/type Please provide the following: [q]uit. sw-file-name: -----------> {malcrprgige.bin}: admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {true}: sw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}: 1 hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {rpr}: rpr|rpr-t1-gr303|rpr-e1-v52|rpr-t1cas card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save changes? [s]ave, [c]hange or [q]uit: s card redundancy group ID change to 1 This will cause the removal of all associated profiles and a slotreboot to create new if-translate profilesbased on "uplinkx-y" names. Continue? [y]es or [n]o: y Record updated.
After saving the uplink card-profile, the system will reboot. 2
Add a second uplink card to the primary uplink node.
MALC Hardware Installation Guide
537
Gigabit Ethernet Uplinks
Set the second uplink card to the same card-group-id and line type as the first uplink card. zSH> card add 1/2/5041 linetype rpr | rpr-t1-gr303|rpr-e1-v52
or zSH> new card-profile 1/2/5041 shelf/slot/type Please provide the following: [q]uit. sw-file-name: -----------> {}: malcrprgige.bin admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {true}: sw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}: 1 hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {unknowntype}:rpr|rpr-t1-gr303|rpr-e1-v52| rpr-t1cas card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save changes? [s]ave, [c]hange or [q]uit: s card redundancy group ID change to 1 This will cause the removal of all associated profiles and a slotreboot to create new if-translate profilesbased on "uplinkx-y" names. Continue? [y]es or [n]o: y Record updated.
3
Connect the uplink card RDNT ports with the RPR redundant cable.
4
Modify the rpr-config profile to specify how the RPR ring should handle redundancy switches. See the MALC Configuration Guide for a detailed explanation of these protection settings. zSH> new rpr-config 1-1-2-0/eth Please provide the following: [q]uit. reversion-mode: --------> {true}: protection-wtr: --------> {10}: protection-fast-timer: -> {10}: protection-slow-timer: -> {100}: wrap-config: -----------> {false}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
5
538
MALC Hardware Installation Guide
Repeat these steps to add GigE cards to the RPR ring nodes.
GigE and FE/GigE uplink card configuration
Adding redundant uplink cards to RPR nodes To add a redundant uplink card into an RPR (non-uplink) node: 1
Assign both cards to card-group-id 1.
2
Connect the cards with an intercard connector.
3
Do not connect the GigE port 2 to the ring.
Adding Gigabit Ethernet uplink cards in linear mode To add a Gigabit Ethernet uplink card to the system: 1
Install the uplink card in slot 1.
2
Create a card-profile for the uplink card: Note: The card line type for Gigabit Ethernet cards in a linear topology is ds1.
zSH> card add 1/1/5041 linetype ds1
or zSH> new card-profile 1/1/5041 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {malcrprgige.bin}: admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {1}: enter the same redundancy group ID as the working uplink card hold-active: ----------> {false}: weight: ---------------> {nopreference}: assign a weight, if desired card-line-type: -------> {unknowntype}: ds1 card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Optionally, using the MALC-UPLINK-2-GE-ONLY card: zSH> card add 1/5/5066
or zSH> new card-profile 1/5/5066 Please provide the following: [q]uit. sw-file-name: -----------> {malcrprgigent.bin}: admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}:
MALC Hardware Installation Guide
539
Gigabit Ethernet Uplinks
upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {true}: sw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}:enter the same redundancy group ID as the working uplink card hold-active: ------------> {false}: weight: -----------------> {nopreference}: assign a weight, if desired card-line-type: ---------> {unknowntype}: card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: maxvpi-maxvci: ----------> {notapplicable}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Optionally, using the MALC-UPLINK-2-FE/GE cards: zSH> card add 1/5/5090
or zSH> new card-profile 1/5/5090 Please provide the following: [q]uit. sw-file-name: -----------> {malcrprgigent.bin}: admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {true}: sw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}:enter the same redundancy group ID as the working uplink card hold-active: ------------> {false}: weight: -----------------> {nopreference}: assign a weight, if desired card-line-type: ---------> {unknowntype}: card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: maxvpi-maxvci: ----------> {notapplicable}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
3
540
MALC Hardware Installation Guide
Connect the cables.
GigE and FE/GigE uplink card configuration
Configuring redundant uplink cards in linear mode Caution: When adding redundant uplink cards, note the following You must configure redundant physical interfaces on both the active and standby cards. This applies to all uplink cards. In addition, you must manually keep the configuration of the physical interfaces on the active and standby cards in sync. Each card must be running the same software version and have the same size flash card. Note: When configuring the redundant uplink card, the settings in the card-profile for the both cards must be identical. To add a redundant uplink card to the system: 1
Verify that active card has been configured with the same card-group-id that is to be used for the standby card.
2
Install a second uplink card in slot 2.
3
Create a card-profile for the second uplink card: Note: The card line type for GigE and FE/GigE cards in a linear topology is t1cas.
zSH> card add 1/2/5041 linetype t1cas
or zSH> new card-profile 1/2/5041 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {}: malcrprgige.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {1}: enter the same redundancy group ID as the working uplink card hold-active: ----------> {false}: weight: ---------------> {nopreference}: assign a weight, if desired card-line-type: -------> {unknowntype}: t1cas card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
4
Connect the redundant cables.
MALC Hardware Installation Guide
541
Gigabit Ethernet Uplinks
Once the card-profile has been saved, the standby card comes up and the configuration and routing tables from the primary card are copied over.
Changing the RPR line type If, after configuring the line type for a GigE or FE/GigE card, you need to change the line type, delete the uplink card-profile and recreate it. Caution: Changing the line type for the uplink card requires a system reboot and deletes the system configuration. Back up your configuration using the dump command before changing the line type. By default, the GigE and FE/GigE-2 cards are configured to carry data only. You can modify the GigE and FE/GigE-2 cards so that the T1/E1 TDM ports can be configured to carry voice traffic. To do this, modify the card-line-type in the card-profile. The following line types are supported:
•
rpr: RPR data-only mode (default)
•
rpr-t1-gr303: RPR with data and GR-303 voice
•
rpr-e1-v52: RPR with data and V5.2 voice
•
rpr-t1cas: RPR with data and T1 CAS voice
•
t1cas: linear Ethernet
1
Delete the card-profile for the uplink card: zSH> delete card-profile 1/1/5041 shelf/slot/type
2
Create the uplink card-profile and change the card-line-type:
zSH> update card-profile 1/1/5041shelf/slot/type Please provide the following: [q]uit. sw-file-name: -----------> {}: malcrprgige.bin admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {true}: sw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}: 1 hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {rpr}: rpr|rpr-t1-gr303|rpr-e1-v52|rpr-t1cas card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
After saving the uplink card-profile, the system will reboot.
542
MALC Hardware Installation Guide
GigE and FE/GigE uplink card configuration
Enabling clocking for GigE and FE/GigE uplink cards 1
Use the slots command to verify the GigE or FE/GigE-2 uplink card and T1/E1 line card is running. zSH> slots 1:*MALC RPR GIGE 2nd generation (RUNNING) 14: MALC T1E1ATM32 (RUNNING) zSH>
2
Update the transmit clock source in the DS1 profile to looptiming.
zSH> update ds1-profile 1/14/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: -----------------------> {csu}: csu-line-length: ----------------> {csu00}: system-clock-source-eligible: ----------> {eligible}: transmit-clock-source: ----------> {throughtiming}: looptiming cell-scramble: ------------------> {true}: coset-polynomial: ---------------> {true}: protocol-emulation: -------------> {network}: signal-type: --------------------> {loopstart}: ds1-group-number: ---------------> {0}: line-power: ---------------------> {disabled}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
3
Change the admin status of the line card to up. zSH> update if-translate 1/14/1/0/ds1 Please provide the following: [q]uit. ifIndex: -----------> {18}: shelf: -------------> {1}: slot: --------------> {14}: port: --------------> {1}: subport: -----------> {0}: type: --------------> {ds1}: adminstatus: -------> {down}: up physical-flag: -----> {true}: iftype-extension: --> {none}: ifName: ------------> {1-14-1-0}: redundancy-param1: -> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s
MALC Hardware Installation Guide
543
Gigabit Ethernet Uplinks
Record updated.
4
Enable system clock eligibility on the line card.
zSH> update system-clock-profile 1/14/1/0/ds1 Please provide the following: [q]uit. system-clock-eligibility: -> {false}: true system-clock-weight: ------> {5}: .................... Save changes? [s]ave, [c]hange or [q]uit: s MAY 28 02:00:37: warning: 1/1/1054: clkmgr: _ClkMgrClockingConfigure(): l=4500: tClkMgr: Secondary clock source set to 1/14/1/0 Record updated. zSH>
5
Update the primary clock source in the system profile to point to the line card. zSH> update system 0 Please provide the following: [q]uit. syscontact: -----------> {Zhone Global Services ... sysname: --------------> {Zhone Malc}: syslocation: ----------> {Oakland}: enableauthtraps: ------> {disabled}: setserialno: ----------> {0}: zmsexists: ------------> {false}: zmsconnectionstatus: --> {inactive}: zmsipaddress: ---------> {0.0.0.0}: configsyncexists: -----> {false}: configsyncoverflow: ---> {false}: configsyncpriority: ---> {high}: configsyncaction: -----> {noaction}: configsyncfilename: ---> {}: configsyncstatus: -----> {syncinitializing}: configsyncuser: -------> {}: configsyncpasswd: -----> {** private **}: ** read-only ** numshelves: -----------> {1}: shelvesarray: ---------> {}: numcards: -------------> {3}: ipaddress: ------------> {0.0.0.0}: alternateipaddress: ---> {0.0.0.0}: countryregion: --------> {us}: primaryclocksource: ---> {0/0/0/0/0}: 1/14/1/0/ds1 ringsource: -----------> {internalringsourcelabel}: revertiveclocksource: -> {true}: voicebandwidthcheck: --> {false}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated. zSH>
6
544
MALC Hardware Installation Guide
Use the clkmgrshow command to verify the clock source of the GigE uplink card.
Small form factor pluggables
zSH> clkmgrshow current Primary system clock is 1/14/1/0 : T1 Secondary system clock is LOCAL timing zSH>
802.1p priority queuing The MALC supports 802.1p priority queuing on the MALC-UPLINK-GE, MALC-UPLINK-GE-ONLY, MALC-UPLINK-2-FE/GE, and MALC-UPLINK-2-FE/GE-TDM uplink cards and on unicast connections on the all MALC downlink cards. Table 35: COS/TOS mapping COS
TOS
QoS Description
0
0
Default - best effort.
1
1
background, routine
2
2
spare, immediate
3
3
excellent effort
4
4
controlled load
5
5
video ( {malcrprgige.bin}: admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {1}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: linkagg-t1-gr303 card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Optionally, using the card update command: zSH> card update 1/21/5041 linetype linkagg-t1-gr303
2
Verify the card line type is correct. zSH> get card-profile 1/1/5041 sw-file-name: -----------> {malcrprgige.bin} admin-status: -----------> {operational} upgrade-sw-file-name: ---> {} upgrade-vers: -----------> {} admin-status-enable: ----> {enable} sw-upgrade-admin: -------> {reloadcurrrev}
548
MALC Hardware Installation Guide
802.3ad link aggregation
sw-enable: --------------> sw-upgrade-enable: ------> card-group-id: ----------> hold-active: ------------> weight: -----------------> card-line-type: ---------> card-atm-configuration: -> card-line-voltage: ------> maxvpi-maxvci: ----------> card-init-string: -------> zSH>
{true} {false} {0} {false} {nopreference} {linkagg-t1-gr303} {notapplicable} {not-used} {notapplicable} {}
Configuring interfaces for link aggregation Interfaces can be added to link aggregation ports for bridging and IP routing.
Bridge configurations To add an bridge intralink on the logical link aggregation port: zSH> bridge add 1-1-1-0/linkagg intralink zSH> bridge-path add linkagg1/bridge global-intralink
Unlearned traffic received on this interface is forwarded to the external network.
Interface configurations To add an interface on the logical link aggregation port: zSH> interface add 1-1-1-0/linkagg 10.10.10.1 255.255.255.0 zSH> interface show
This creates an IP interface on the link aggregation port with an IP address of 10.10.10.1, with a subnet mask of 255.255.255.0.
host configurations To add a host on the logical link aggregation port: zSH> host add 1-1-1-0/linkagg 192.24.17.10 zSH> host show
This creates a host 192.24.17.10 on the link aggregation port.
Commands for linkagg The following new commands are available for link aggregation.
•
linkagg show
•
linkagg stats
MALC Hardware Installation Guide
549
Gigabit Ethernet Uplinks
linkagg show command The linkagg show command displays zSH> linkagg show Link Aggregation Status: state: LINK 1 UP, LINK 2 DOWN ifIndex: 2 lineGrpIfIndex: 4 shelf: 1 (1) slot: 1 (2) port: 1 (1) redundancy: ACTIVE link status: UP opMode REDUNDANT_LAG (5)
linkagg stats command The linkagg stats command displays statistics for the aggregated port traffic. zSH> linkagg stats LinkAgg Port Number = Ether_Stats_Vars.StatsIndex = Ether_Stats_Vars.dot3Stats.alignmentErrors = Ether_Stats_Vars.dot3Stats.FCSErrors = Ether_Stats_Vars.dot3Stats.singleCollisionFrames = Ether_Stats_Vars.dot3Stats.multipleCollisionFrames = Ether_Stats_Vars.dot3Stats.lateCollisions = Ether_Stats_Vars.dot3Stats.ExcessiveCollisions = Ether_Stats_Vars.dot3Stats.internalMacTransmitErrors = Ether_Stats_Vars.dot3Stats.carrierSenseErrors = Ether_Stats_Vars.dot3Stats.frameTooLongs = Ether_Stats_Vars.dot3Stats.internalMacReceiveErrors = Ether_Stats_Vars.dot3Stats.symbolErrors = Ether_Stats_Vars.dot3Stats.Ether_Stats_DuplexStatus = Ether_Stats_Vars.SQETestErrors = Ether_Stats_Vars.DeferredTransmissions =
550
MALC Hardware Installation Guide
1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
12
DS3/E3 UPLINKS This chapter describes the MALC DS3/E3 Uplink card (Uplink-DS3/E3) and explains how to configure it. It includes:
•
Overview, page 552
•
DS3/E3 card configuration, page 554
•
Configuring DS3/E3 interfaces, page 556
•
DS3/E3 Uplink cable, page 560
MALC Hardware Installation Guide
551
DS3/E3 Uplinks
Overview The MALC Uplink-DS3/E3 card has two active DS3/E3 interfaces (with an option to activate up to 4 interfaces). It provides similar services and functionality as the T1/ E1 Uplink card, but with a higher capacity interface. Note that the DS3/E3 Uplink card is unchannelized that is, it does not support separate DS1 connections. The DS3/E3 Uplink card contains an Ethernet port for local management, local LAN connectivity, or IP uplinks; a DS3/ E3 interface for user traffic; and a serial (craft) port for local management.
Table 36: Uplink-DS3/E3 specifications
552
Specification
Description
Size
1 slot
Density
4 ports
Physical interface
Custom high density connector
MALC Hardware Installation Guide
Provided cable breaking out to 4 pairs BNC Coax connectors
Overview
Table 36: Uplink-DS3/E3 specifications (Continued) Specification
Description
ATM support
MALC performs ATM cell relay functions between cell based line cards (such as ADSL or G.SHDSL) and the Uplink card. The Uplink card performs cell relay function for the ATM traffic on the backplane. ATM Quality of Service types supported:
• • •
CBR, rt-VBR, nrt-VBR, UBR Fair Weighted Queuing Per VC and per QoS buffering
ATM Forum specifications:
•
UNI 3.0, UNI 3.1 compliant. Note that ILMI, SVCs, point-to-multipoint are currently not supported.
•
UNI 4.0 compliant for PVC features only. Note that ABR, SVCs, SPVCs, Multicast, and Anycast are not currently supported.
•
Partial support for Traffic Management 4.0 including: –
QOS levels described above
–
Connection Admission Control
–
Traffic descriptor specification
Default VPI/VCI ranges:
• •
VPI: 0 to 3 VCI: 32 to 1023
AAL2 and AAL5 termination:
• • • Voice processing
AAL2 SAR for MALC POTS lines AAL5 SAR for in-band management VC termination RFC 1483 routed termination supported
AAL2 SAR for subscriber lines on POTS cards Supports AAL2 BLES standard, compatible with standards based Voice Gateways G.711 encoding of voice calls on the MALC TDM bus
Management interfaces
RS-232D serial craft port AAL5 Management VC termination (RFC 1483 routed) for ATM in-band management Management Ethernet 10/100 port routable for connecting to other Ethernet devices SNMP
Redundancy
1+1 card redundancy (with Y cable).
Power
30 W
MALC Hardware Installation Guide
553
DS3/E3 Uplinks
DS3/E3 card configuration This section describes optional configuration procedures for the DS3/E3 card. If these procedures are required, they should be done before provisioning the system.
Configuring ATM settings for DS3/E3 Uplink cards To configure DS3/E3 IP Uplink cards: zSH> update card-profile 1/1/5109 shelf/slot/type (type is 5109 for DS3/E3 IP Uplink cards) Please provide the following: [q]uit. sw-file-name: ---------> {malcds3f.bin}: admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {1}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {ds3}: card-atm-configuration: -> {vbnrt65rt30} change the bandwidth allocation, if desired card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Changing atm configuration will result in a system reboot. Continue? [y]es or [n]o: y Atm configuration changed system is rebooting ...Record updated.
Changing the DS3 Uplink card line type If, after configuring the line type for a DS3/E3 Uplink card, you need to change the line type, delete the Uplink card-profile and recreate it. Caution: Changing the line type for the Uplink card requires a system reboot and deletes the system configuration. Back up your configuration using the dump command before changing the line type. 1
Save the device configuration. For example: a
Verify you are at the root of the flash card: zSH> cd /card1 zSH> pwd /card1/
b
554
MALC Hardware Installation Guide
Back up the current configuration file to the flash card and store it in the onreboot directory:
DS3/E3 card configuration
zSH> mkdir onreboot zSH> cd onreboot zSH> dump file restore
This file will be used to restore the system configuration or revert to a previous release, if desired. c
If desired, save the configuration file to a host on the network. For example: zSH> dump network 192.168.8.21 malc.cfg
d
Change directories to the root of the flash card: zSH> cd /card1 zSH> pwd /card1/
2
Delete the card-profile for the DS3/E3 Uplink card: zSH> delete card-profile 1/1/5109
3
Create the Uplink card-profile and change the card-line-type to ds3 or e3:
zSH> card add 1/1/5109 linetype ds3 | e3
or zSH> new card-profile 1/1/5109 shelf/slot/type (5109 for DS3 Uplink cards) Please provide the following: [q]uit. sw-file-name: ---------> {}: malcds3f.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {1}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: ds3 | e3 card-atm-configuration: -> {notapplicable} enter the bandwidth allocation card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
After saving the Uplink card-profile, the system will reboot and restore the configuration saved to the onreboot directory.
MALC Hardware Installation Guide
555
DS3/E3 Uplinks
Connecting redundant DS3/E3 cards 1
Attach the MALC DS3/E3 redundant cable (MALC-CBL-DS3/ E3-10M-1P-R (30-feet, 1 port), or the MALC-CBL-DS3/E3-10M-R (30feet, 1 port), or the MALC-CBL-DS3/E3-R (6-inch cable)) to each of the DS3/E3 Uplink cards.
2
Connect the individual BNC connectors from each card using a T-connector. (See Figure 73.) Note: Redundant DS3/E3 connections are only supported with the 6-inch redundant DS3/E3 cable. Do not attempt to connect redundant cards with the 6-foot DS3/E3 cable.
Figure 73: Connecting redundant DS3/E3 Uplink cards
Configuring DS3/E3 interfaces Note: For redundant systems, configure the DS3/E3 interfaces on both the active and standby cards.
556
MALC Hardware Installation Guide
Configuring DS3/E3 interfaces
The following table summarizes the commands required to configure DS3 uplink interfaces on the MALC: Action
Command
Update the DS3/E3 interfaces, which specify the basic parameters of the DS3 line, including line type, encoding, and clocking. See Configuring DS3/E3 interfaces on page 556.
update ds3-profile 1-1-port-0/ds3
Activate the DS1 interfaces in the if-translate profile. See Activating the DS3 interface on page 558.
update if-translate 1-1-port-0/ds3
where port is from 1 to 4 If your system is redundant, configure the DS3/E3 interfaces on both the active and standby cards.
where port is from 1 to 4
When the DS3 card starts up, it creates four ds3-profiles. To view the DS3s on the system, use the list command: zSH> list ds3-profile ds3-profile 1-1-2-0/ds3 ds3-profile 1-1-3-0/ds3 ds3-profile 1-1-4-0/ds3 ds3-profile 1-1-5-0/ds3 4 entries found.
The ds3-profile specifies the basic operating parameters of the interface. The following table describes the supported ds3-profile parameters. Parameter
Description
line-type
Specifies the line type. dsx3cbitparity (C-bit parity). dsx3m23 (M23) Default: dsx3cbitparity
line-coding
dsx3b3zs is the only supported value.
circuit-id
A description of the circuit.
line-length-meters
The length of the DS3 line in meters. Valid values are 0 - 137 m. One meters is equal to 3.28 feet. Default: 0
loopback-config
This parameter is used for loopback testing. For information, see the MALC Configuration Guide.
medium-scramble-config
True: payload scramble is on. False: payload scramble is off. Default: True
transmit-clock-source
Specifies the clock source for the interface. See for information about configuring the system clock.
MALC Hardware Installation Guide
557
DS3/E3 Uplinks
Parameter
Description
medium-frame-config
The E3 framing mode. Values: e3FrameOther An option other than e3FrameG832 or e3FrameG751. e3FrameG832 E3 framing format will be G832. e3FrameG751 E3 framing format will be G751. Default: e3FrameG832
medium-atmframe-config
Specifies the type of ATM framing. Values: dsx3atmframingplcp Uses PLCP framing. dsx3AtmFramingDirectCellMapped Uses direct cell mapping. Default: dsx3AtmFramingDirectCellMapped
Configuring a DS3 interface The default values are appropriate for most applications. If you need to change them, update the ds3-profile for the interface: zSH> update ds3-profile 1-1-1-0/ds3 line-type: ---------------> {dsx3cbitparity} line-coding: -------------> {dsx3b3zs} send-code: ---------------> {dsx3sendnocode} circuit-id: --------------> {} loopback-config: ---------> {dsx3noloop} transmit-clock-source: ---> {looptiming} throughtiming line-length-meters: ------> {0} line-status-trap-enable: -> {enabled} channelization: ----------> {disabled} ds1-for-remote-loop: -----> {0} far-end-equip-code: ------> {} far-end-loc-id-code: -----> {} far-end-frame-id-code: ---> {} far-end-unit-code: -------> {} far-end-fac-id-code: -----> {} medium-scramble-config: --> {true} medium-frame-config: -----> {e3frameg832} medium-atmframe-config: --> {dsx3atmframingdirectcellmapped} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Activating the DS3 interface Update the if-translate record for the DS3 interface to enable the line. The if-translate record uses an index in the form shelf-slot-port-subport/ type.
558
MALC Hardware Installation Guide
Configuring DS3/E3 interfaces
The following example activates the first DS3 interface on the slot card located in shelf 1 slot 1: zSH> update if-translate 1-1-1-0/ds3 Please provide the following: [q]uit. ifIndex: ----------> {154}: shelf: ------------> {1}: slot: -------------> {1}: port: -------------> {1}: subport: ----------> {0}: type: -------------> {ds3}: adminstatus: ------> {down}: up physical-flag: ----> {true}: iftype-extension: -> {0}: ifName: -----------> {1-1-1-0}: redundancy-param1: -> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
MALC Hardware Installation Guide
559
DS3/E3 Uplinks
DS3/E3 Uplink cable Figure 74 shows the 6-foot DS3 Uplink cable (MALC-CBL-DS3/E3). Table 37 lists the pinouts. Note: Redundant DS3/E3 connections are only supported with the 6-inch redundant DS3/E3 cable. Do not attempt to connect redundant cards with the 6-foot DS3/E3 cable. Figure 74: DS3 Uplink cable
Table 37: DS3/E3 Uplink cable pinouts
560
BNC
Function
1
TX 1
2
RX 1
3
TX 2
4
RX 2
5
TX 3
6
RX 3
7
TX 4
8
RX 4
MALC Hardware Installation Guide
13
OC-3C/STM1 UPLINKS This chapter describes the MALC OC3C/STM1 Uplink card (Uplink-OC3C/ STM1) and explains how to configure it. It includes:
•
Overview, page 562
•
OC3C/STM1 Uplink card configuration, page 564
•
Configuring OC-3C/STM1 interfaces, page 565
•
Configuring APS, page 569
MALC Hardware Installation Guide
561
OC-3C/STM1 Uplinks
Overview The MALC OC3C/STM1 card provides two single-mode optical interfaces, as well as a serial craft port and an Ethernet port for management or IP uplinks. The MALC supports Automatic Protection Switching (APS) when 2 cards are installed in the system to provide card-level redundancy for the optical interfaces.
562
MALC Hardware Installation Guide
Overview
Table 38: Uplink-OC-3c/STM1-ATM/IP specifications Specification
Description
Size
1 slot
Density
2 ports
Physical interface
SC connector (Class 1 Laser International Safety Standard IEC 825 compliant)
• • • • •
Single mode fiber Intermediate Reach IR-1optics 1300 nM SC connector Tx min: -15 dBM, max: -8 dBM
RJ45 Management 10/100 Ethernet Interface RS232D serial craft interface ATM support
MALC performs ATM cell relay functions between cell based line cards (such as ADSL or G.SHDSL) and the Uplink card. The Uplink card performs cell relay function for the ATM traffic on the backplane. ATM Quality of Service types supported:
• • •
CBR, rt-VBR, nrt-VBR, UBR Fair Weighted Queuing Per VC and per QoS buffering
ATM Forum specifications:
•
UNI 3.0, UNI 3.1 compliant. Note that ILMI, SVCs, point-to-multipoint are currently not supported.
•
UNI 4.0 compliant for PVC features only. Note that ABR, SVCs, SPVCs, Multicast, and Anycast are not currently supported.
•
Partial support for Traffic Management 4.0 including: –
QOS levels described above
–
Connection Admission Control
–
Traffic descriptor specification
Default VPI/VCI ranges:
• •
VPI: 0 to 7 VCI: 32 to 1023
AAL2 and AAL5 termination:
• •
AAL2 SAR for MALC POTS lines
•
RFC 1483 routed termination supported
AAL5 SAR for in-band management VC termination
MALC Hardware Installation Guide
563
OC-3C/STM1 Uplinks
Table 38: Uplink-OC-3c/STM1-ATM/IP specifications (Continued) Specification
Description
Voice processing
AAL2 SAR for converting TDM bus voice traffic to ATMG.711 encoding only ATMF Loop Emulation Standard
Management interface
RS-232D serial craft port AAL5 Management VC termination (RFC 1483 routed) for ATM in-band management Management Ethernet 10/100 port routable for connecting to other Ethernet devices SNMP
Redundancy
Card and link redundancy with separate fiber uplink to standby card APS 1:1 bi-directional, compatible with 1+1 APS switches
Power consumption
33 W
OC3C/STM1 Uplink card configuration This section describes optional configuration procedures for the OC3C/STM1 Uplink card. If these procedures are required, they should be done before provisioning the system.
Configuring ATM settings for OC3C/STM1 uplink cards To configure OC3C/STM1 IP Uplink cards: zSH> update card-profile 1/1/5111 shelf/slot/type (type is 5111 for OC3C/STM1 IP Uplink cards) Please provide the following: [q]uit. sw-file-name: ---------> {malcoc3f.bin}: admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {1}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {ds1}: card-atm-configuration: -> {vbnrt65rt30} change the bandwidth allocation, if desired card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Changing atm configuration will result in a system reboot. Continue? [y]es or [n]o: y
564
MALC Hardware Installation Guide
Configuring OC-3C/STM1 interfaces
Atm configuration changed system is rebooting ...Record updated.
Configuring OC-3C/STM1 interfaces Note: For systems configured for APS, configure the OC3C/STM1 interfaces on both the active and standby cards. Note: Ensure that the APS working and protection configuration is consistent between the MALC and the far end OC3C/STM1 interface. This may require manual intervention on the MALC so that both sides agree on which interface is working and which is protection. The following table summarizes the commands required to configure OC3C/ STM1 uplink interfaces on the MALC: Action
Command
Configure the OC3C/STM1 interfaces, which specify the basic parameters of the interface, including line coding, and clocking. See Configuring the OC3C/ STM1 interface on page 568.
update sonet-profile 1-1-port-0/sonet
Activate the interfaces in the if-translate profile. See Enabling/disabling the SONET interface on page 568. Configure APS (if desired). See Configuring APS on page 569.
where port is from 1 to 2 If your system is redundant, configure the OC3C/STM1 interfaces on both the active and standby cards. update if-translate 1-1-port-0/sonet where port is 1 or 2 update aps-channel 1-1-port-0/sonet update aps-group group where group is 1 or 2
Note: For short distance connections, you may need to add attenuation to the OC3C/STM1 interface.
MALC Hardware Installation Guide
565
OC-3C/STM1 Uplinks
The following table describes the supported sonet-profile parameters. Parameter
Description
medium-type
The type of SONET signaling. Values: sonet Synchronous Optical Network (North America) sdh Synchronous Digital Hierarchy (Europe) Default: sonet
medium-line-coding
Line coding for this interface. Values: sonetMediumOther sonetMediumB3ZS Used for STS-1 and STS-3 electrical SONET/SDH signaling. sonetMediumCMI Used for STS-1 and STS-3 electrical SONET/SDH signaling. sonetMediumNRZ Non-Return to Zero. Used for optical SONET/SDH signals. sonetMediumRZ Return to Zero. Used for optical SONET/SDH signals. Default: sonetmediumnrz
medium-line-type
Describes the line type for this interface. Values: sonetMultiMode sonetShortSingleMode Default: sonetshortsinglemode
medium-circuit-identifier
The SONET circuit identifier, determined by the system installer. Values: string of up to 260 characters
566
MALC Hardware Installation Guide
Configuring OC-3C/STM1 interfaces
Parameter
Description
medium-loopback-config
How the SONET loopback is configured. Values: sonetnoloop SONET circuit, with no loop. sonetfacilityloop All incoming data on the Rx interface is retransmitted out of the Tx interface. Used to check the circuit between a remote device and the MALC and to test the MALC optical module. sonetterminalloop All of the data transmitted on the Tx interface is also internally looped back to the Rx interface. Used to verify that the ATM and PHY layers are communicating. sonetotherloop All incoming data on the Rx interface is retransmitted out of the Tx interface. Used to check the circuit between the IAD and a remote unit and to verify that the optical module and the SONET PHY are working.
path-current-width
Indicates the type of the SONET/SDH path. Values: sts1 sts12cSTM4 sts3cSTM1
clock-external-recovery
Whether internal clocking can be recovered from an external source. Values: enabled disabled
clock-transmit-source
The clocking source. Values: external155mhz Transmit clock synthesized from an external 155.52 MHz source. looptiming Uses the recovered receive clock as the transmit clock. localtiming Either uses a local clock source or an external clock which is attached to the device containing the interface. throughtiming Uses a transmit clock derived from the recovered receive clock of another interface.
medium-cell-scrambleconfig
Specifies whether SONET scramble mode is enabled.
medium-line-scrambleconfig
Specifies whether the line-level SONET scramble mode is enabled.
MALC Hardware Installation Guide
567
OC-3C/STM1 Uplinks
Configuring the OC3C/STM1 interface To view the OC3C/STM1 interfaces on the system, use the list command: zSH> list sonet-profile sonet-profile 1-1-1-0/sonet sonet-profile 1-1-2-0/sonet
To display the default sonet-profile for an interface, use the get command: zSH> get sonet-profile 1-1-1-0/sonet medium-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> get sonet-profile 1-1-2-0/sonet medium-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}:
If you need to make changes to the default configuration, use the update command.
Enabling/disabling the SONET interface By default, the OC3C/STM1 interface is inactive. During maintenance, or if the port is not in use, the SONET interface should be in the down state. The following example enables the SONET interface in shelf 1, slot 1, port 1: zSH> update if-translate 1-1-1-0/sonet Please provide the following: [q]uit. ifIndex: ----------> {12}: shelf: ------------> {1}: slot: -------------> {1}: port: -------------> {1}: subport: ----------> {0}:
568
MALC Hardware Installation Guide
APS
type: -------------> adminstatus: ------> physical-flag: ----> iftype-extension: -> ifName: -----------> redundancy-param1: -> .................... Save changes? [s]ave, Record updated.
{sonet}: {down}: up {true}: {0}: {}: {0}: [c]hange or [q]uit: s
To disable the interface: zSH> update if-translate 1-1-1-0/sonet Please provide the following: [q]uit. ifIndex: ----------> {12}: shelf: ------------> {1}: slot: -------------> {1}: port: -------------> {1}: subport: ----------> {0}: type: -------------> {sonet}: adminstatus: ------> {up}: down physical-flag: ----> {true}: iftype-extension: -> {0}: ifName: -----------> {}: redundancy-param1: -> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
APS Configuring APS The system automatically creates the following APS profiles for SONET/ SDH OC3C/STM1 uplink cards:
•
aps-channel: configures the APS channels. There are two APS channel per port. OC3C/STM1 cards have 2 ports and therefore four APS channels.
•
aps-group: configures the APS groups. There are up to two APS groups on the system. Each APS group contains a working and protect channel.
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. The following tables describe how the SONET/SDH cards and ports are assigned to APS groups and channels. These values cannot be changed. The OC3C/STM1 card has 2 ports per card and requires assignments for each port.
MALC Hardware Installation Guide
569
OC-3C/STM1 Uplinks
Table 39: OC3C/STM1 Card APS Assignments Slot
Port
APS group
APS channel
1
1
1
1
1
2
2
1
2
1
1
0
2
2
2
0
Note: The APS protocol runs on the protect or second SONET/SDH card. To configure APS: 1
Verify both the working and protect SONET/SDH interfaces are configured identically, including the same card-group-id, and both are enabled.
2
Verify that the MALC working ports are connected to the working ports on the SONET/SDH switch and the MALC protection ports are connected to the protection ports on the SONET/SDH switch.
3
Activate the APS channels for the APS groups:
zSH> update aps-channel 1-1-1-0/sonet Please provide the following: [q]uit. apsChanConfigGroupName: ---> {group1}: **read-only ** apsChanConfigNumber: ------> {1}: ** read-only ** apsChanConfigAdminStatus: -> {notinservice}: inservice apsChanConfigPriority: ----> {low}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated. zSH> update aps-channel 1-2-1-0/sonet Please provide the following: [q]uit. apsChanConfigGroupName: ---> {group1}: **read-only ** apsChanConfigNumber: ------> {0}: ** read-only ** apsChanConfigAdminStatus: -> {notinservice}: inservice apsChanConfigPriority: ----> {low}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
4
Activate the APS groups: zSH> update aps-group 1 Please provide the following: [q]uit. apsConfigName: -----------> {group1}: ** read-only ** apsConfigAdminStatus: ----> {notinservice}: inservice apsConfigMode: -----------> {oneton}: oneplusone apsConfigRevert: ---------> {nonrevertive}: apsConfigDirection: ------> {unidirectional}:
570
MALC Hardware Installation Guide
APS
apsConfigExtraTraffic: ---> {disabled}: apsConfigSdBerThreshold: -> {6}: apsConfigSfBerThreshold: -> {3}: apsConfigWaitToRestore: --> {300}: apsConfigCreationTime: ---> {0}: ** read-only ** .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated. zSH> update aps-group 2 Please provide the following: [q]uit. apsConfigName: -----------> {group2}: ** read-only ** apsConfigAdminStatus: ----> {notinservice}: inservice apsConfigMode: -----------> {oneton}: oneplusone apsConfigRevert: ---------> {nonrevertive}: apsConfigDirection: ------> {unidirectional}: apsConfigExtraTraffic: ---> {disabled}: apsConfigSdBerThreshold: -> {6}: apsConfigSfBerThreshold: -> {3}: apsConfigWaitToRestore: --> {300}: apsConfigCreationTime: ---> {0}: ** read-only ** .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
MALC Hardware Installation Guide
571
OC-3C/STM1 Uplinks
572
MALC Hardware Installation Guide
14
TDM/ATM UPLINKS This chapter describes the MALC TDM/ATM Uplink card (Uplink-T1/ E1-TDM/ATM/IP) and explains how to configure it. It includes:
•
Overview, page 573
•
T1/E1 TDM Uplink card configuration, page 576
•
Configuring DS1/E1 interfaces, page 578
•
Configuring IMA groups, page 583
Overview The TDM/ATM Uplink card provides GR-303 and V5.2 support for the MALC. The card occupies a single slot in the MALC chassis and has 16 T1/E1 ports. The first eight ports are ATM T1/E1 ports; the second eight are TDM T1/ E1 ports. The ATM ports provide multiplexing and demultiplexing of ATM traffic on the cell level as described in the ATM Forum AF-PHY-0086.001. The Uplink card also contains an Ethernet port for local management, local LAN connectivity, or IP uplink; and a serial (craft) port for local management. The TDM ports receive GR-303 or V5.2 signaling and convert it to PSTN analog signaling. Note: Pulse dialing is not supported on the TDM/ATM Uplink card.
MALC Hardware Installation Guide
573
TDM/ATM Uplinks
Table 40: Uplink-T1/E1-TDM/ATM specifications Specification
Description
Size
1 slot
Density
16 ports: 8 ATM T1/E1 ports (ports 1 through 8) 8 TDM T1/E1 ports (ports 9 through 16)
Connectors
One (1) 96-pin telco connector One Ethernet 10/100 port One RS-232D serial craft port
574
Standards supported
AF-PHY-0086.001
Supported line rates
T1: 1.544 Mbps
MALC Hardware Installation Guide
GR-303-CORE
E1: 2.048 Mbps
Overview
Table 40: Uplink-T1/E1-TDM/ATM specifications (Continued) Specification
Description
ATM support
MALC performs ATM cell relay functions between cell based line cards (such as ADSL or G.SHDSL) and the Uplink card. The Uplink card performs cell relay function for the ATM traffic on the backplane. ATM Quality of Service types supported:
• • •
CBR, rt-VBR, nrt-VBR, UBR Fair Weighted Queuing Per VC and per QoS buffering
ATM Forum specifications:
•
UNI 3.0, UNI 3.1 compliant. Note that ILMI, SVCs, point-to-multipoint are currently not supported.
•
UNI 4.0 compliant for PVC features only. Note that ABR, SVCs, SPVCs, Multicast, and Anycast are not currently supported. 16 IMA groups are supported, as described in the ATM forum AF-PHY-0086.001. Note that UNI and IMA mode are not currently supported on the same card.
•
Partial support for Traffic Management 4.0 including: –
QOS levels described above
–
Connection Admission Control
–
Traffic descriptor specification
VPI/VCI ranges:
• •
VPI: 0 to 3 VCI: 32 to 511
AAL2 and AAL5 termination:
• •
AAL2 SAR for MALC POTS lines
•
RFC 1483 routed termination supported
AAL5 SAR for in-band management VC termination
Redundancy
1+1 card redundancy (with Y cable).
TDM line characteristics
Supervisory signaling is Extended Superframe (ESF) – CAS signaling
TDM capacity
2 GR-303 interface groups (IGs) 8 channelized T1s per card 4096 maximum GR-303 call reference values (CRVs) per system
Power consumption
36 W
MALC Hardware Installation Guide
575
TDM/ATM Uplinks
T1/E1 TDM Uplink card configuration This section describes optional configuration procedures for the T1/E1 TDM Uplink card. If these procedures are required, they should be done before provisioning the system.
Configuring ATM settings for T1/E1 ATM/TDM Uplink cards To change the ATM bandwidth settings for the first 8 ports of the T1/E1 TDM IP Uplink cards: zSH> update card-profile 1/1/5114 shelf/slot/type (type is 5114 for T1/E1 TDM IP Uplink cards) Please provide the following: [q]uit. sw-file-name: ---------> {malcT1E1Tdmf.bin}: admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {1}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: card-atm-configuration: -> {vbnrt65rt30} change the bandwidth allocation, if desired card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Changing atm configuration will result in a system reboot. Continue? [y]es or [n]o: y Atm configuration changed system is rebooting ...Record updated.
Changing the T1/E1 ATM/TDM Uplink card line type If, after configuring the line type for a T1/E1 TDM Uplink card, you need to change the line type, delete the Uplink card-profile and recreate it. Caution: Changing the line type for the Uplink card requires a system reboot and deletes the system configuration. Back up your configuration using the dump command before changing the line type. 1
Save the device configuration. For example: a
Verify you are at the root of the flash card: zSH> cd /card1 zSH> pwd /card1/
b
576
MALC Hardware Installation Guide
Back up the current configuration file to the flash card and store it in the onreboot directory:
T1/E1 TDM Uplink card configuration
zSH> mkdir onreboot zSH> cd onreboot zSH> dump file restore
This file will be used to restore the system configuration or revert to a previous release, if desired. c
If desired, save the configuration file to a host on the network. For example: zSH> dump network 192.168.8.21 malc.cfg
d
Change directories to the root of the flash card: zSH> cd /card1 zSH> pwd /card1/
2
Delete the card-profile for the Uplink card: zSH> delete card-profile 1/1/5114 shelf/slot/type
3
Create the Uplink card-profile and change the card-line-type and specify the ATM bandwidth allocation:
zSH> card add 1/1/5114 linetype el | dsl
or zSH> new card-profile 1/1/5114 Please provide the following: [q]uit. sw-file-name: ---------> {}: malcT1E1Tdmf.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {1}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: e1 | ds1 card-atm-configuration: -> {notapplicable} enter the bandwidth allocation card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
After saving the Uplink card-profile, the system will reboot and restore the configuration saved to the onreboot directory.
MALC Hardware Installation Guide
577
TDM/ATM Uplinks
Connecting redundant T1/E1 ATM/TDM Uplink cards The T1/E1 TDM Uplink card has a redundant Y cable to provide card redundancy. To connect the redundant cables: 1
Attach the 96-pin connector to the uplink connector on the Uplink card.
2
Attach the 50-pin connectors to the appropriate network interface. (See Figure 75.)
Figure 75: Connecting redundant T1/E1 TDM Uplink cards
For pinout information about the redundant T1/E1 TDM cable, see T1/ E1-ATM/TDM cables, page 588.
Configuring DS1/E1 interfaces This section explains how to configure DS1/E1 interfaces. It applies to the TDM Uplink card (ports 9 through 16) the T1/E1 IMA card, and the T1/E1 32 port card. Note: For redundant systems, configure the DS1 interfaces on both the active and standby cards.
578
MALC Hardware Installation Guide
Configuring DS1/E1 interfaces
The following table summarizes the commands required to configure DS1 uplink interfaces on the MALC: Action
Command
Update the DS1 interfaces, which specify the basic parameters of the DS1 line, including framing, encoding, and clocking. See Configuring DS1/E1 interfaces on page 578.
update ds1-profile 1-1-port-0/ds1 where port is from 1 to 8 (for the IMA Uplink card) 9 to 16 (for the TDM Uplink card) 1 to 32 (for the T1/E1 32 card) If your system is redundant, configure the DS1 interfaces on both the active and standby cards.
Activate the DS1 interfaces in the if-translate and line-group profiles. See Activating a DS1 interface on page 582.
update if-translate 1-1-port-0/ds1 where port is from 1 to 8 for the T1/E1 IMA Uplink card or 1 to 16 for the T1/E1 TDM Uplink card 1 to 32 (for the T1/E1 32 card)
The ds1-profile configures both T1 and E1 interfaces. T1 interfaces on the MALC have the following defaults:
•
ESF framing
•
B8ZS coding
•
Robbed bit signaling
•
CSU mode
•
Line build out of 0 feet
E1 interfaces on the MALC have the following defaults:
•
E1-CRCMF line type
•
HDB3 coding
•
Line build out of 0 feet
MALC Hardware Installation Guide
579
TDM/ATM Uplinks
The following table describes the supported ds1-profile parameters. Parameter
Options
line-type
The type of DS1 circuit. Values: esf Extended Super Frame. e1Mf : G.704, table 4a, with TS16 multiframing enabled for E1 circuits. e1CrcMf : G.704, table 4b, with TS16 multiframing enabled for E1 circuits. Default: esf for T1 e1 for E1
line-code
The type of Zero Code Suppression used on the interface. b8zs: a specific pattern of normal bits and bipolar violations used to replace a sequence of eight zero bits. hdb3: High Density Bipolar of order 3. A code used for E1. Default: b8zs for T1 hdb3 for E1
send-code
This parameter is used for bit error rate (BER) testing. For information, see the MALC Configuration Guide.
circuit-id
Enter a circuit identifier for the interface, up to 36 characters.
loopback-config
This parameter is used for loopback testing. For information, see MALC Configuration Guide.
dsx-line-length
The length of the DSX WAN interface in feet. This parameter provides information for line build out circuitry. Values: Dsx0 0 feet for the line build out (LBO) setting. Dsx133 133 feet for the LBO. Dsx266 266 feet for the LBO. Dsx399 399 feet for the LBO. Dsx533 533 feet for the LBO. Dsx655 655 feet for the LBO. Default: 0
580
MALC Hardware Installation Guide
Configuring DS1/E1 interfaces
Parameter
Options
line-status-change-trap -enable
Specifies whether a trap is generated whenever the line state changes. Values: enabled disabled Default: enabled
ds1-mode
Type of interface. Values: dsx DS1 interface is DSX csu DS1 interface is CSU other Interface is neither CSU nor DSX Default: csu
csu-line-length
This parameter provides information for line build out circuitry. Values: csu00 0 dB line build out. csu75 -7.5 dB line build out. csu150 -15.0 dB line build out. csu225 -22.5 dB line build out. Default: csu00
transmit-clock-source
Specifies the clock source for the interface. See for information about configuring the system clock.
cell-scramble
Indicates whether ATM cell scrambling is enabled for this interface. Both sides of the connection must agree on whether scrambling is enabled. Values: true Cell scrambling enabled. false Cell scrambling disabled. Default: true
coset-polynomial
Indicates whether the coset polynomial is used to calculate the ATM header error control (HEC) value. Both sides of the connection must agree on the method of calculating the HEC value. Values: true The coset polynomial is used to calculate the HEC value. false The coset polynomial is not used to calculate the HEC value. Default: true
MALC Hardware Installation Guide
581
TDM/ATM Uplinks
Configuring a DS1 interface The default values are appropriate for most applications. If you need to change them, update the ds1-profile for the interface: zSH> update ds1-profile 1-1-1-0/ds1 Please provide the following: [q]uit. line-type: ----------------------> {esf}: line-code: ----------------------> {b8zs}: send-code: ----------------------> {sendnocode}: circuit-id: ---------------------> {ds1}: 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}: protocol-emulation: -------------> {network} signal-type: --------------------> {loopstart} ds1-group-number: ---------------> {0} line-power: ---------------------> {disabled} Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Activating a DS1 interface Activate each DS1 interface by updating its if-translate profile: zSH> update if-translate 1-1-1-0/ds1 Please provide the following: [q]uit. ifindex: -----> {1}: . shelf: -------> {1}: slot: --------> {1}: port: --------> {1}: subport: -----> {0}: type: --------> {ds1}: adminstatus: -> {down}: up physical-flag: ----> {true}: iftype-extension: -> {0}: ifName: -----------> {1-1-1-0}: redundancy-param1: -> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
After you update the profile, a log message appears indicating the line is active:
582
MALC Hardware Installation Guide
Configuring IMA groups
1/1: alarm_mgr: : l=167: 01:01:01 Major T1 Up Line 1:1:1:0
Continue updating each DS1 interface. When all the interfaces are active, proceed to configuring the IMA groups.
Configuring IMA groups Note: For redundant systems, configure the IMA interfaces and links on both the active and standby cards. For more information about IMA, refer to the ATM Forum Inverse Multiplexing for ATM (IMA) Specification Version 1.1 (AF-PHY-0086.001). The following table summarizes the commands required to configure IMA groups on the MALC: Action
Command
(Optional) Update the ima-group-profile, which specifies the basic settings of the IMA group, including the number of transmit and receive links and the clocking. See Configuring IMA groups on page 587.
update ima-group-profile 1/slot/1 If your system is redundant, configure the IMA group on both the active and standby cards.
(Optional) Move the default IMA links to different groups. See Moving IMA links on page 587.
imalink move SourceIMAGroup DestinationIMAGroup ds1Interface
where slot the slot that contains the card).
MALC Hardware Installation Guide
583
TDM/ATM Uplinks
The following table describes the supported parameters in the ima-group-profile. Parameter
Description
groupSymmetry
The symmetry of the Inverse Multiplexing over ATM (IMA) group. Symmetry determines whether the transmit and receive sides of the IMA link must be configured and how traffic is sent over the links. Values: symmetricOperation Both transmit and receive IMA links must be configured and the system can transmit and receive traffic only if both sides of the connection are active. asymmetricOperation Both transmit and receive IMA links must be configured, but the system can transmit and receive traffic even if both sides of the connection are not active. asymmetricConfiguration Transmit and receive links do not have to be configured and the system can transmit and receive traffic even if both sides of the connection are not active. Default: symmetricOperation
minNumTxLinks
Minimum number of transmit links required to be Active for the IMA group to be in the Operational state. If the number of active links falls below this value, the link drops and the redundant link (if any) takes over. Values: 1 to 8 Default: 1
minNumRxLinks
Minimum number of receive links required to be active for the IMA group to be in the operational state. If the number of active links falls below this value, the link drops and the redundant link (if any) takes over. Values: 1 to 8 Default: 1
txClkMode
Transmit clocking mode used by the near-end IMA group. Values: itc Independent Transmit Clock. Indicates that IMA links do not all use the same transmit clock. Each IMA link derives clock from its associated DS1 interface. ctc Common Transmit Clock. Indicates the transmit clock of all IMA links are derived from the same source. When set to ctc, the MALC derives the IMA clocking from the system clock. Default: ctc
584
MALC Hardware Installation Guide
Configuring IMA groups
Parameter
Description
txImaId
The IMA ID currently in use by the near-end IMA interface. Values: 0 to 255 Default: 1
txFramLength
The frame length to be used by the IMA group in the transmit direction. Can only be set when the IMA group is startup. Values: m32 32 cells m64 64 cells m128 128 cells m256 256 cells Default: m128
diffDelayMax
The maximum number of milliseconds of differential delay among the links that can be tolerated on this interface. Values: 0 to 100 Default: 25
alphaValue
The number of consecutive invalid ICP cells allowed before the system changes from a Sync state to a Hunt state. Values: 1 or 2 Default: 2
betaValue
The number of consecutive errored ICP cells allowed before the system changes from a Sync state to a Hunt state. Values: 1 to 5 Default: 2
gammaValue
The number of consecutive valid ICP cells allowed before the system changes from a PreSync state to the Sync state. Values: 1 to 5 Default: 1
testLinkIfIndex
This parameter is used for testing the IMA link. See MALC Configuration Guide for information.
MALC Hardware Installation Guide
585
TDM/ATM Uplinks
Parameter
Description
testPattern
This parameter is used for testing the IMA link. See MALC Configuration Guide for information.
testProcStatus
This parameter is used for testing the IMA link. See MALC Configuration Guide for information.
Overview The following MALC cards support IMA groups:
•
T1/E1 IMA Uplink
•
T1/E1-ATM-32
Each card supports 16 IMA groups. The MALC T1/E1-ATM-32 card provides 32 T1/E1 UNI or IMA ports. All ports must be configured as either UNI or IMA. When these cards boot up, the system creates the IMA groups and assigns the T1/E1 links to the following groups: Links
IMA group
1-4
1
5-8
2
9 - 12
3
13 - 16
4
17 - 20
9
21 - 24
10
25 - 28
11
29 -32
12
Note: (T1/E1 32 card only) IMA links 1-16 can only belong to IMA groups 1-8 and links 17-32 can only belong to IMA groups 9-16. Note the following about multiple IMA groups:
586
•
In a redundant Uplink configuration, you must configure IMA groups on both the active and standby cards
•
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. Do not use the imalink remove command unless requested to by Zhone GSS.
MALC Hardware Installation Guide
Configuring IMA groups
Configuring IMA groups The following example updates an IMA group to change the minimum number of links in the group: zSH> update ima-group-profile 1/1/1 shelf/slot/port Please provide the following: [q]uit. 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}: groupRestoreNumRetry:--> {4} groupRestoreDelaySecs:-> {3600} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Moving IMA links To move IMA links from one group to another, use the imalink move command. For example: zSH> imalink move 1-1-1-0/atmima 1-1-2-0/atmima 1-1-1-0/ds1 Stack unbind successful. Link moved successfully.
This command moves the DS1 interface 1-1-1-0/ds1 from IMA group 1-1-1-0/atm to IMA group 1-1-2-0/atmima. If this is a redundant configuration, also move the IMA link on the standby card: zSH> imalink move 1-2-1-0/atmima 1-2-2-0/atmima 1-2-1-0/ds1 Stack unbind successful. Link moved successfully.
After moving the links, you can use the imalink show command to view the links in the group: zSH> imalink show 1-3-1-0/atmima DS1 Links for IMA Group 1-3-1-0/atmima: If Index If Name -----------------------
MALC Hardware Installation Guide
587
TDM/ATM Uplinks
000736 000737 000738 000739
1-3-1-0 1-3-2-0 1-3-3-0 1-3-4-0
T1/E1-ATM/TDM cables This section describes the following T1/E1-ATM/TDM cables available from Zhone Technologies:
•
Redundant TDM/ATM Uplink cable on page 588
•
Non-redundant TDM/ATM Uplink cable on page 591
Redundant TDM/ATM Uplink cable The TDM/ATM Uplink card can be redundantly configured by using active and standby cards connected with a “Y” cable. Figure 76 shows the 96-pin-to-three-50-pin, redundant TDM/ATM Uplink cable (MALC-CBL-T1/ E1-ATM/TDM-16-R, MALC-CBL-T1/E1-16-45DEG-R). Table 41 lists the pinouts. Figure 76: Redundant TDM/ATM Uplink cable
588
MALC Hardware Installation Guide
T1/E1-ATM/TDM cables
Table 41: Redundant TDM/ATM uplink cable pinouts Port
Pair
Signal
Color
From
To
1
TX 1 Ring
Blue/White
P1-1 and P2-1
P3-1
TX 1 Tip
White/Blue
P1-2 and P2-2
P3-26
RX 1 Ring
Orange/White
P1-3 and P2-3
P3-27
RX 1 Tip
White/Orange
P1-4 and P2-4
P3-2
TX 2 Ring
Green/White
P1-5 and P2-5
P3-5
TX 2 Tip
White/Green
P1-6 and P2-6
P3-30
RX 2 Ring
Brown/White
P1-7 and P2-7
P3-31
RX 2 Tip
White/Brown
P1-8 and P2-8
P3-6
TX 3 Ring
Slate/White
P1-9 and P2-9
P3-39
TX 3 Tip
White/Slate
P1-10 and P2-10
P3-34
RX 3 Ring
Blue/Red
P1-11 and P2-11
P3-35
RX 3 Tip
Red/Blue
P1-12 and P2-12
P3-10
TX 4 Ring
Orange/Red
P1-13 and P2-13
P3-13
TX 4 Tip
Red/Orange
P1-14 and P2-14
P3-38
RX 4 Ring
Green/Red
P1-15 and P2-15
P3-39
RX 4 Tip
Red/Green
P1-16 and P2-16
P3-14
TX 5 Ring
Brown/Red
P1-17 and P2-17
P3-17
TX 5 Tip
Red/Brown
P1-18 and P2-18
P3-42
RX 5 Ring
Slate/Red
P1-19 and P2-19
P3-43
RX 5 Tip
Red/Slate
P1-20 and P2-20
P3-18
TX 6 Ring
Blue/Black
P1-21 and P2-21
P3-21
TX 6 Tip
Black/Blue
P1-22 and P2-22
P3-46
RX 6 Ring
Orange/Black
P1-23 and P2-23
P3-47
RX 6 Tip
Black/Orange
P1-24 and P2-24
P3-22
TX 7 Ring
Blue/White
P1-25 and P2-25
P4-1
TX 7 Tip
White/Blue
P1-26 and P2-26
P4-26
RX 7 Ring
Orange/White
P1-27 and P2-27
P4-27
RX 7 Tip
White/Orange
P1-28 and P2-28
P4-2
TX 8 Ring
Green/White
P1-29 and P2-29
P4-5
TX 8 Tip
White/Green
P1-30 and P2-30
P4-30
1 2
3 2 4
5 3 6
7 4 8
9 5 10
11 6 12
13 7 14
15 8
MALC Hardware Installation Guide
589
TDM/ATM Uplinks
Table 41: Redundant TDM/ATM uplink cable pinouts (Continued) Port
Pair
Signal
Color
From
To
16
RX 8 Ring
Brown/White
P1-31 and P2-31
P4-31
RX 8 Tip
White/Brown
P1-32 and P2-32
P4-6
TX 9 Ring
Slate/White
P1-33 and P2-33
P4-9
TX 9 Tip
White/Slate
P1-34 and P2-34
P4-34
RX 9 Ring
Blue/Red
P1-35 and P2-35
P4-35
RX 9 Tip
Red/Blue
P1-36 and P2-36
P4-10
TX 10 Ring
Orange/Red
P1-37 and P2-37
P4-13
TX 10 Tip
Red/Orange
P1-38 and P2-38
P4-38
RX 10 Ring
Green/Red
P1-39 and P2-39
P4-39
RX 10 Tip
Red/Green
P1-40 and P2-40
P4-14
TX 11 Ring
Brown/Red
P1-41 and P2-41
P4-17
TX 11 Tip
Red/Brown
P1-42 and P2-42
P4-42
RX 11 Ring
Slate/Red
P1-43 and P2-43
P4-43
RX 11 Tip
Red/Slate
P1-44 and P2-44
P4-18
TX 12 Ring
Blue/Black
P1-45 and P2-45
P4-21
TX 12 Tip
Black/Blue
P1-46 and P2-46
P4-46
RX 12 Ring
Orange/Black
P1-47 and P2-47
P4-47
RX 12 Tip
Black/Orange
P1-48 and P2-48
P4-22
TX 13 Ring
Blue/White
P1-49 and P2-49
P5-1
TX 13 Tip
White/Blue
P1-50 and P2-50
P5-26
RX 13 Ring
Orange/White
P1-51 and P2-51
P5-27
RX 13 Tip
White/Orange
P1-52 and P2-52
P5-2
TX 14 Ring
Green/White
P1-53 and P2-53
P5-5
TX 14 Tip
White/Green
P1-54 and P2-54
P5-30
RX 14 Ring
Brown/White
P1-55 and P2-55
P5-31
RX 14 Tip
White/Brown
P1-56 and P2-56
P5-6
TX 15 Ring
Slate/White
P1-57 and P2-57
P5-9
TX 15 Tip
White/Slate
P1-58 and P2-58
P5-34
RX 15 Ring
Blue/Red
P1-59 and P2-59
P5-35
RX 15 Tip
Red/Blue
P1-60 and P2-60
P5-10
17 9 18
19 10 20
21 11 22
23 12 24
25 13 26
27 14 28
29 15 30
590
MALC Hardware Installation Guide
T1/E1-ATM/TDM cables
Table 41: Redundant TDM/ATM uplink cable pinouts (Continued) Port
Pair
Signal
Color
From
To
31
TX 16 Ring
Orange/Red
P1-61 and P2-61
P5-13
TX 16 Tip
Red/Orange
P1-62 and P2-62
P5-38
RX 16 Ring
Green/Red
P1-63 and P2-63
P5-34
RX 16 Tip
Red/Green
P1-64 and P2-64
P5-14
16 32
Non-redundant TDM/ATM Uplink cable Figure 77 shows the 96-pin-to-three-50-pin, non-redundant TDM/ATM Uplink cable (MALC-CBL-T1/E1-16-45DEG, MALC-CBL-T1/E1-ATM/ TDM-16). Table 42 lists the pinouts. Figure 77: Non-Redundant TDM/ATM Uplink cable
Table 42: Non-redundant TDM/ATM uplink cable pinouts Port
Pair
Signal
Color
From
To
1
TX 1 Ring
Blue/White
P1-1
P2-1
TX 1 Tip
White/Blue
P1-2
P2-26
RX 1 Ring
Orange/White
P1-3
P2-27
RX 1 Tip
White/Orange
P1-4
P2-2
1 2
MALC Hardware Installation Guide
591
TDM/ATM Uplinks
Table 42: Non-redundant TDM/ATM uplink cable pinouts (Continued) Port
Pair
Signal
Color
From
To
3
TX 2 Ring
Green/White
P1-5
P2-5
TX 2 Tip
White/Green
P1-6
P2-30
RX 2 Ring
Brown/White
P1-7
P2-31
RX 2 Tip
White/Brown
P1-8
P2-6
TX 3 Ring
Slate/White
P1-9
P2-39
TX 3 Tip
White/Slate
P1-10
P2-34
RX 3 Ring
Blue/Red
P1-11
P2-35
RX 3 Tip
Red/Blue
P1-12
P2-10
TX 4 Ring
Orange/Red
P1-13
P2-13
TX 4 Tip
Red/Orange
P1-14
P2-38
RX 4 Ring
Green/Red
P1-15
P2-39
RX 4 Tip
Red/Green
P1-16
P2-14
TX 5 Ring
Brown/Red
P1-17
P2-17
TX 5 Tip
Red/Brown
P1-18
P2-42
RX 5 Ring
Slate/Red
P1-19
P2-43
RX 5 Tip
Red/Slate
P1-20
P2-18
TX 6 Ring
Blue/Black
P1-21
P2-21
TX 6 Tip
Black/Blue
P1-22
P2-46
RX 6 Ring
Orange/Black
P1-23
P2-47
RX 6 Tip
Black/Orange
P1-24
P2-22
TX 7 Ring
Blue/White
P1-25
P3-1
TX 7 Tip
White/Blue
P1-26
P3-26
RX 7 Ring
Orange/White
P1-27
P3-27
RX 7 Tip
White/Orange
P1-28
P3-2
TX 8 Ring
Green/White
P1-29
P3-5
TX 8 Tip
White/Green
P1-30
P3-30
RX 8 Ring
Brown/White
P1-31
P3-31
RX 8 Tip
White/Brown
P1-32
P3-6
TX 9 Ring
Slate/White
P1-33
P3-9
TX 9 Tip
White/Slate
P1-34
P3-34
2 4
5 3 6
7 4 8
9 5 10
11 6 12
13 7 14
15 8 16
17 9
592
MALC Hardware Installation Guide
T1/E1-ATM/TDM cables
Table 42: Non-redundant TDM/ATM uplink cable pinouts (Continued) Port
Pair
Signal
Color
From
To
18
RX 9 Ring
Blue/Red
P1-35
P3-35
RX 9 Tip
Red/Blue
P1-36
P3-10
TX 10 Ring
Orange/Red
P1-37
P3-13
TX 10 Tip
Red/Orange
P1-38
P3-38
RX 10 Ring
Green/Red
P1-39
P3-39
RX 10 Tip
Red/Green
P1-40
P3-14
TX 11 Ring
Brown/Red
P1-41
P3-17
TX 11 Tip
Red/Brown
P1-42
P3-42
RX 11 Ring
Slate/Red
P1-43
P3-43
RX 11 Tip
Red/Slate
P1-44
P3-18
TX 12 Ring
Blue/Black
P1-45
P3-21
TX 12 Tip
Black/Blue
P1-46
P3-46
RX 12 Ring
Orange/Black
P1-47
P3-47
RX 12 Tip
Black/Orange
P1-48
P3-22
TX 13 Ring
Blue/White
P1-49
P4-1
TX 13 Tip
White/Blue
P1-50
P4-26
RX 13 Ring
Orange/White
P1-51
P4-27
RX 13 Tip
White/Orange
P1-52
P4-2
TX 14 Ring
Green/White
P1-53
P4-5
TX 14 Tip
White/Green
P1-54
P4-30
RX 14 Ring
Brown/White
P1-55
P4-31
RX 14 Tip
White/Brown
P1-56
P4-6
TX 15 Ring
Slate/White
P1-57
P4-9
TX 15 Tip
White/Slate
P1-58
P4-34
RX 15 Ring
Blue/Red
P1-59
P4-35
RX 15 Tip
Red/Blue
P1-60
P4-10
TX 16 Ring
Orange/Red
P1-61
P4-13
TX 16 Tip
Red/Orange
P1-62
P4-38
RX 16 Ring
Green/Red
P1-63
P4-34
RX 16 Tip
Red/Green
P1-64
P4-14
19 10 20
21 11 22
23 12 24
25 13 26
27 14 28
29 15 30
31 16 32
MALC Hardware Installation Guide
593
TDM/ATM Uplinks
594
MALC Hardware Installation Guide
15
T1/E1 UPLINKS This chapter describes the MALC T1/E1 Uplink card (UPLINK-T1/E1-IMA) and explains how to configure it. It includes:
•
Overview, page 595
•
Configuring DS1/E1 interfaces, page 599
•
Configuring IMA groups, page 604
•
T1/E1 IMA cable and port pinouts, page 610
Overview IMA provides multiplexing and demultiplexing of ATM traffic on the cell level as described in the ATM forum AF-PHY-0086.001. On the subscriber side, the Uplink card provides ATM Adaptation Layer 2 (AAL2) termination for POTS cards. The Uplink card also provides system management services such as software and configuration database storage, management, and monitoring. The T1/E1 Uplink card supports both IMA and UNI mode. The Uplink card contains an Ethernet port for local management, local LAN connectivity, or IP uplink; a T1/ E1 IMA interface for user traffic; and a serial (craft) port for local management.
MALC Hardware Installation Guide
595
T1/E1 Uplinks
Table 43: Uplink-T1/E1 ATM/IP specifications Specification
Description
Size
1 slot
Density
8 ports
Physical interface
Custom 36-pin amphenol connector
ATM support
MALC performs ATM cell relay functions between cell based line cards (such as ADSL or SHDSL) and the Uplink card. The Uplink card performs cell relay function for the ATM traffic on the backplane.
Provided cable breaking out to 2 50-pin telco connectors
ATM Quality of Service types supported:
• • •
CBR, rt-VBR, nrt-VBR, UBR Fair Weighted Queuing Per VC and per QoS buffering
ATM Forum specifications:
•
UNI 3.0, UNI 3.1 compliant. Note that ILMI, SVCs, point-to-multipoint are currently not supported.
•
UNI 4.0 compliant for PVC features only. Note that ABR, SVCs, SPVCs, Multicast, and Anycast are not currently supported. 8 IMA groups are supported, as described in the ATM forum AF-PHY-0086.001. Note that UNI and IMA mode are not currently supported on the same card.
•
Partial support for Traffic Management 4.0 including: –
QOS levels described above
–
Connection Admission Control
–
Traffic descriptor specification
VPI/VCI ranges:
• •
VPI: 0 to 3 VCI: 32 to 511
AAL2 and AAL5 termination:
• • • Voice processing
AAL2 SAR for MALC POTS lines AAL5 SAR for in-band management VC termination RFC 1483 routed termination supported
AAL2 SAR for subscriber lines on POTS cards Supports AAL2 BLES standard, compatible with standards based Voice Gateways G.711 encoding of voice calls on the MALC TDM bus
596
MALC Hardware Installation Guide
T1/E1 ATM/IP card configuration
Table 43: Uplink-T1/E1 ATM/IP specifications (Continued) Specification
Description
Management interfaces
RS-232D serial craft port AAL5 Management VC termination (RFC 1483 routed) for ATM in-band management Management Ethernet 10/100 port routable for connecting to other Ethernet devices SNMP
Redundancy
1+1 card redundancy (with Y cable).
Uplink-T1/ E1-IMA-8
30 W
T1/E1 ATM/IP card configuration This section describes optional configuration procedures for the T1/E1 ATM/ IP card. These procedures should be done before provisioning the system.
Configuring ATM settings for T1/E1 ATM/IP Uplink cards To configure T1/E1 IP Uplink cards: zSH> update card-profile 1/1/5101 shelf/slot/type (type is 5101 for T1/E1 IP Uplink cards) Please provide the following: [q]uit. sw-file-name: ---------> {malct1imaf.bin}: admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {1}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: card-atm-configuration: -> {vbnrt65rt30} change the bandwidth allocation, if desired card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Changing atm configuration will result in a system reboot. Continue? [y]es or [n]o: y Atm configuration changed system is rebooting ...Record updated.
Changing the T1/E1 IMA Uplink card line type If, after configuring the line type for a T1/E1 Uplink card, you need to change the line type, delete the Uplink card-profile and recreate it.
MALC Hardware Installation Guide
597
T1/E1 Uplinks
Caution: Changing the line type for the Uplink card requires a system reboot and deletes the system configuration. Back up your configuration using the dump command before changing the line type. 1
Save the device configuration. For example: a
Verify you are at the root of the flash card: zSH> cd /card1 zSH> pwd /card1/
b
Back up the current configuration file to the flash card and store it in the onreboot directory: zSH> mkdir onreboot zSH> cd onreboot zSH> dump file restore
This file will be used to restore the system configuration or revert to a previous release, if desired. c
If desired, save the configuration file to a host on the network. For example: zSH> dump network 192.168.8.21 malc.cfg
d
Change directories to the root of the flash card: zSH> cd /card1 zSH> pwd /card1/
2
Delete the card-profile for the Uplink card: zSH> delete card-profile 1/1/5101 shelf/slot/type
3
Create the Uplink card-profile and change the card-line-type and specify the ATM bandwidth allocation:
zSH> card add 1/1/5101 linetype e1 | e1-ima | ds1 | ds1-ima
or zSH> new card-profile 1/1/5101 Please provide the following: [q]uit. sw-file-name: ---------> {}: malct1imaf.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {1}:
598
MALC Hardware Installation Guide
Configuring DS1/E1 interfaces
hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: e1 | e1-ima | ds1 | ds1-ima card-atm-configuration: -> {notapplicable} enter the bandwidth allocation card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
After saving the Uplink card-profile, the system will reboot and restore the configuration saved to the onreboot directory.
Connecting redundant T1/E1 Uplink cards The T1/E1 ATM/IP Uplink card has a redundant Y cable to provide card redundancy. To connect the redundant cables: 1
Attach each 36-pin connector to the uplink connector on the Uplink card.
2
Attach the 50-pin connectors to the appropriate network interface. (See Figure 78.)
Figure 78: Connecting redundant T1/E1 Uplink cards
For pinout information about the redundant T1/E1 IMA cable, see T1/E1 IMA cable and port pinouts, page 610.
Configuring DS1/E1 interfaces This section explains how to configure DS1/E1 interfaces. It applies to the TDM Uplink card (ports 9 through 16) the T1/E1 IMA card, and the T1/E1 32 port card.
MALC Hardware Installation Guide
599
T1/E1 Uplinks
Note: For redundant systems, configure the DS1 interfaces on both the active and standby cards. The following table summarizes the commands required to configure DS1 uplink interfaces on the MALC: Action
Command
Update the DS1 interfaces, which specify the basic parameters of the DS1 line, including framing, encoding, and clocking. See Configuring a DS1 interface on page 603.
update ds1-profile 1-1-port-0/ds1 where port is from 1 to 8 (for the IMA Uplink card) 9 to 16 (for the TDM Uplink card) 1 to 32 (for the T1/E1 32 card) If your system is redundant, configure the DS1 interfaces on both the active and standby cards.
Activate the DS1 interfaces in the if-translate and line-group profiles. See Activating a DS1 interface on page 603.
update if-translate 1-1-port-0/ds1 where port is from 1 to 8 for the T1/E1 IMA Uplink card or 1 to 16 for the T1/E1 TDM Uplink card 1 to 32 (for the T1/E1 32 card)
The ds1-profile configures both T1 and E1 interfaces. T1 interfaces on the MALC have the following defaults:
•
ESF framing
•
B8ZS coding
•
Robbed bit signaling
•
CSU mode
•
Line build out of 0 feet
E1 interfaces on the MALC have the following defaults:
600
•
E1-CRCMF line type
•
HDB3 coding
•
Line build out of 0 feet
MALC Hardware Installation Guide
Configuring DS1/E1 interfaces
The following table describes the supported ds1-profile parameters. Parameter
Options
line-type
The type of DS1 circuit. Values: esf Extended Super Frame. e1Mf : G.704, table 4a, with TS16 multiframing enabled for E1 circuits. e1CrcMf : G.704, table 4b, with TS16 multiframing enabled for E1 circuits. Default: esf for T1 e1 for E1
line-code
The type of Zero Code Suppression used on the interface. b8zs: a specific pattern of normal bits and bipolar violations used to replace a sequence of eight zero bits. hdb3: High Density Bipolar of order 3. A code used for E1. Default: b8zs for T1 hdb3 for E1
send-code
This parameter is used for bit error rate (BER) testing. For information, see the MALC Configuration Guide.
circuit-id
Enter a circuit identifier for the interface, up to 36 characters.
loopback-config
This parameter is used for loopback testing. For information, see the MALC Configuration Guide.
dsx-line-length
The length of the DSX WAN interface in feet. This parameter provides information for line build out circuitry. Values: Dsx0 0 feet for the line build out (LBO) setting. Dsx133 133 feet for the LBO. Dsx266 266 feet for the LBO. Dsx399 399 feet for the LBO. Dsx533 533 feet for the LBO. Dsx655 655 feet for the LBO. Default: 0
MALC Hardware Installation Guide
601
T1/E1 Uplinks
Parameter
Options
line-status-change-trap -enable
Specifies whether a trap is generated whenever the line state changes. Values: enabled disabled Default: enabled
ds1-mode
Type of interface. Values: dsx DS1 interface is DSX csu DS1 interface is CSU other Interface is neither CSU nor DSX Default: csu
csu-line-length
This parameter provides information for line build out circuitry. Values: csu00 0 dB line build out. csu75 -7.5 dB line build out. csu150 -15.0 dB line build out. csu225 -22.5 dB line build out. Default: csu00
transmit-clock-source
Specifies the clock source for the interface.
cell-scramble
Indicates whether ATM cell scrambling is enabled for this interface. Both sides of the connection must agree on whether scrambling is enabled. Values: true Cell scrambling enabled. false Cell scrambling disabled. Default: true
coset-polynomial
Indicates whether the coset polynomial is used to calculate the ATM header error control (HEC) value. Both sides of the connection must agree on the method of calculating the HEC value. Values: true The coset polynomial is used to calculate the HEC value. false The coset polynomial is not used to calculate the HEC value. Default: true
602
MALC Hardware Installation Guide
Configuring DS1/E1 interfaces
Configuring a DS1 interface The default values are appropriate for most applications. If you need to change them, update the ds1-profile for the interface: zSH> update ds1-profile 1-1-1-0/ds1 Please provide the following: [q]uit. line-type: ----------------------> {esf}: line-code: ----------------------> {b8zs}: send-code: ----------------------> {sendnocode}: circuit-id: ---------------------> {ds1}: 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}: protocol-emulation: -------------> {network}signal-type: --------------------> {loopstart} Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Activating a DS1 interface Activate each DS1 interface by updating its if-translate profile: zSH> update if-translate 1-1-1-0/ds1 Please provide the following: [q]uit. ifindex: -----> {1}: . shelf: -------> {1}: slot: --------> {1}: port: --------> {1}: subport: -----> {0}: type: --------> {ds1}: adminstatus: -> {down}: up physical-flag: ----> {true}: iftype-extension: -> {0}: ifName: -----------> {1-1-1-0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
After you update the profile, a log message appears indicating the line is active: 1/1: alarm_mgr: : l=167: 01:01:01 Major T1 Up Line 1:1:1:0
MALC Hardware Installation Guide
603
T1/E1 Uplinks
Continue updating each DS1 interface. When all the interfaces are active, proceed to configuring the IMA groups.
Configuring IMA groups Note: For redundant systems, configure the IMA interfaces and links on both the active and standby cards.
Best Practices for Setting Up an IMA Group The following procedure recommends a best practices way to set up an Inverse Multiplexing over ATM (IMA) group. Note that the T1E1ATM32 line card and the NT1F8 and TDMF uplink cards all support IMA groups. You can set two modes in the card profiles: IMA only and mixed IMA-Uni. Note: If you add a DS1 to an IMA group that has no existing DS1s, you need to reboot the card before the IMA group can be used.
Best Practices for Setting Up an IMA Group 1
Use the command imalink show to view the DS1 links being used in each IMA group.
2
Be sure to add or move at least one DS1 link into the IMA group before using the IMA group. Reboot the card after adding the first DS1 link.
3
Always match the number of DS1 links provisioned in the IMA group on the MALC with the IMA group on the far end ATM equipment.
4
When using redundant uplink cards, always match the number of Ds1 links in the IMA groups on both the Active and Standby uplink cards.
5
Remember that the IMA group itself must be provisioned Up, as well as provisioning Up the individual DS1 links in the IMA group, on both the active and standby uplink cards.
6 Note: Make sure that the DS1 you are moving to the IMA group does not have a cross-connect already provisioned to it. 7
Provision the ATM VPI value to be used, if needed. Perform a system reboot after adding any ATM VPI values. Note: Not all DS1 links can be added to all IMA groups. The lower IMA groups use the lower DS1 links, and the upper IMA groups use the upper DS1 links.
8
604
MALC Hardware Installation Guide
Add an IP interface or cross-connect to the IMA group, as needed for your application.
Configuring IMA groups
Best Practices for Tearing Down an IMA Group 1
Delete any voice connections to an IP interface on an IMA group.
2
Delete any IP interfaces on the IMA group.
3
Delete any cross-connects to the IMA group.
4
Remove any ATM VPI objects configured for the IMA group.
5
Perform a system reboot to reset the ATM VPI table.
6
Move or delete the DS1 links from the IMA group.
7
Perform a system reboot if any DS1 links have moved from IMA to Uni.
For more information about IMA, refer to the ATM Forum Inverse Multiplexing for ATM (IMA) Specification Version 1.1 (AF-PHY-0086.001). The following table summarizes the commands required to configure IMA groups on the MALC: Action
Command
(Optional) Update the ima-group-profile, which specifies the basic settings of the IMA group, including the number of transmit and receive links and the clocking. See Configuring IMA groups on page 609.
update ima-group-profile 1/slot/1 If your system is redundant, configure the IMA group on both the active and standby cards.
(Optional) Move the default IMA links to different groups. See Moving IMA links on page 610.
imalink move SourceIMAGroup DestinationIMAGroup ds1Interface
where slot the slot that contains the card).
MALC Hardware Installation Guide
605
T1/E1 Uplinks
The following table describes the supported parameters in the ima-group-profile. Parameter
Description
groupSymmetry
The symmetry of the Inverse Multiplexing over ATM (IMA) group. Symmetry determines whether the transmit and receive sides of the IMA link must be configured and how traffic is sent over the links. Values: symmetricOperation Both transmit and receive IMA links must be configured and the system can transmit and receive traffic only if both sides of the connection are active. asymmetricOperation Both transmit and receive IMA links must be configured, but the system can transmit and receive traffic even if both sides of the connection are not active. asymmetricConfiguration Transmit and receive links do not have to be configured and the system can transmit and receive traffic even if both sides of the connection are not active. Default: symmetricOperation
minNumTxLinks
Minimum number of transmit links required to be Active for the IMA group to be in the Operational state. If the number of active links falls below this value, the link drops and the redundant link (if any) takes over. Values: 1 to 8 Default: 1
minNumRxLinks
Minimum number of receive links required to be active for the IMA group to be in the operational state. If the number of active links falls below this value, the link drops and the redundant link (if any) takes over. Values: 1 to 8 Default: 1
txClkMode
Transmit clocking mode used by the near-end IMA group. Values: itc Independent Transmit Clock. Indicates that IMA links do not all use the same transmit clock. Each IMA link derives clock from its associated DS1 interface. ctc Common Transmit Clock. Indicates the transmit clock of all IMA links are derived from the same source. When set to ctc, the MALC derives the IMA clocking from the system clock. Default: ctc
606
MALC Hardware Installation Guide
Configuring IMA groups
Parameter
Description
txImaId
The IMA ID currently in use by the near-end IMA interface. Values: 0 to 255 Default: 1
txFramLength
The frame length to be used by the IMA group in the transmit direction. Can only be set when the IMA group is startup. Values: m32 32 cells m64 64 cells m128 128 cells m256 256 cells Default: m128
diffDelayMax
The maximum number of milliseconds of differential delay among the links that can be tolerated on this interface. Values: 0 to 100 Default: 25
alphaValue
The number of consecutive invalid ICP cells allowed before the system changes from a Sync state to a Hunt state. Values: 1 or 2 Default: 2
betaValue
The number of consecutive errored ICP cells allowed before the system changes from a Sync state to a Hunt state. Values: 1 to 5 Default: 2
gammaValue
The number of consecutive valid ICP cells allowed before the system changes from a PreSync state to the Sync state. Values: 1 to 5 Default: 1
testLinkIfIndex
This parameter is used for testing the IMA link.
testPattern
This parameter is used for testing the IMA link.
testProcStatus
This parameter is used for testing the IMA link.
MALC Hardware Installation Guide
607
T1/E1 Uplinks
Parameter
Description
groupRestoreNumR etry
The number of times an IMA group recovery takes place. Values: 0 to 4 Default: 0 3 retrys
groupRestoreNumD elay
The delay, in seconds, before a recovery attempt takes place, and the interval between subsequent recovery attempts. Values: 0 to 3600 Default: 0 3600 seconds
Overview The following MALC cards support IMA groups:
•
UPLINK-T1/E1-IMA
•
MALC-T1/E1-ATM-32
Each card supports 16 IMA groups. The MALC T1/E1-ATM-32 card provides 32 T1/E1 UNI or IMA ports. All ports must be configured as either UNI or IMA. When these cards boot up, the system creates the IMA groups and assigns the T1/E1 links to the following groups:
608
Links
IMA group
1-4
1
5-8
2
9 - 12
3
13 - 16
4
Empty
5
Empty
6
Empty
7
Empty
8
17 - 20
9
21 - 24
10
25 - 28
11
29 -32
12
Empty
13
MALC Hardware Installation Guide
Configuring IMA groups
Links
IMA group
Empty
14
Empty
15
Empty
16
Note: (T1/E1 32 card only) IMA links 1-16 can only belong to IMA groups 1-8 and links 17-32 can only belong to IMA groups 9-16. Note the following about multiple IMA groups:
•
In a redundant Uplink configuration, you must configure IMA groups on both the active and standby cards
•
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. Do not use the imalink remove command unless requested to by Zhone GSS.
Configuring IMA groups The following example updates an IMA group to change the minimum number of links in the group: zSH> update ima-group-profile 1/1/1 shelf/slot/port Please provide the following: [q]uit. 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}: groupRestoreNumRetry:--> {4} groupRestoreDelaySecs:-> {3600} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
MALC Hardware Installation Guide
609
T1/E1 Uplinks
Moving IMA links To move IMA links from one group to another, use the imalink move command. For example: zSH> imalink move 1-1-1-0/atmima 1-1-2-0/atmima 1-1-1-0/ds1 Stack unbind successful. Link moved successfully.
This command moves the DS1 interface 1-1-1-0/ds1 from IMA group 1-1-1-0/atm to IMA group 1-1-2-0/atmima. If this is a redundant configuration, also move the IMA link on the standby card: zSH> imalink move 1-2-1-0/atmima 1-2-2-0/atmima 1-2-1-0/ds1 Stack unbind successful. Link moved successfully.
After moving the links, you can use the imalink show command to view the links in the group: zSH> imalink show 1-3-1-0/atmima DS1 Links for IMA Group 1-3-1-0/atmima: If Index If Name ----------------------000736 1-3-1-0 000737 1-3-2-0 000738 1-3-3-0 000739 1-3-4-0
T1/E1 IMA cable and port pinouts This section describes the T1/E1 IMA cables available from Zhone Technologies and the T1/E1 IMA port pinouts:
•
T1/E1-IMA Uplink port pinouts on page 610
•
8-port T1/E1 to dual 50 pin connector cable on page 611
•
Redundant 8-port T1/E1 to dual 50 pin connector cable on page 614
T1/E1-IMA Uplink port pinouts Figure 79 shows the location of pin 1 on the T1/E1-IMA Uplink connector.
610
MALC Hardware Installation Guide
T1/E1 IMA cable and port pinouts
Figure 79: T1/E1 Uplink connector pin 1
Pin 1
Table 44 lists the T1/E1 uplink port pinouts. Table 44: Uplink-T1/E1-IMA-8 uplink port pinouts Function
Pin
Function
Pin
Tx ring 1
1
Rx ring 1
19
Tx tip 1
10
Rx tip 1
28
Tx ring 2
2
Rx ring 2
20
Tx tip 2
11
Rx tip 2
29
Tx ring 3
3
Rx ring 3
21
Tx tip 3
12
Rx tip 3
30
Tx ring 4
4
Rx ring 4
22
Tx tip 4
13
Rx tip 4
31
Tx ring 5
5
Rx ring 5
23
Tx tip 5
14
Rx tip 5
32
Tx ring 6
6
Rx ring 6
24
Tx tip 6
15
Rx tip 6
33
Tx ring 7
7
Rx ring 7
25
Tx tip 7
16
Rx tip 7
34
Tx ring 8
8
Rx ring 8
26
Tx tip 8
17
Rx tip 8
35
8-port T1/E1 to dual 50 pin connector cable Figure 80 shows the 8 port T1/E1 to dual 50-pin connector cable MALC-CBL-T1/E1-IMA). This cable is used with the T1/E1 IMA Uplink card. Table 45 lists the pinouts.
MALC Hardware Installation Guide
611
T1/E1 Uplinks
This cable is also available as
•
MALC-CBL-T1/E1-UP-90DEG-3M for (2) 36 pin connectors (8 port redundant T1/E1) 9.8FT/3M
•
MALC-CBL-T1/E1-UP-90DEG-3M-R for:(2) 36 pin to (2) 50 pin connectors (8 port redundant T1/E1), 9.8FT/3M
•
MALC-CBL-T1/E1-50FT-DSX-R for 36 pin to blunt end (8 port redundant T1/E1) 50FT/15.24M,
Figure 80: 8-port T1 to dual 50 pin connector cable
Table 45: 8-port T1/E1 to dual 50 pin connector cable pinouts Pair
Signal
Color
From
To
1
TX 1 (tip)
White/Blue
P1-10
P2-26
TX 1 (ring)
Blue/White
P1-1
P2-1
RX 1 (tip)
White/Orange
P1-28
P2-2
RX 1 (ring)
Orange/White
P1-19
P2-27
TX 2 (tip)
White/Green
P1-11
P2-30
TX 2 (ring)
Green/White
P1-2
P2-5
RX 2 (tip)
White/Brown
P1-29
P2-6
RX 2 (ring)
Brown/White
P1-20
P2-31
TX 3 (tip)
White/Slate
P1-12
P2-34
TX 3 (ring)
Slate/White
P1-3
P2-9
2
3
4
5
612
MALC Hardware Installation Guide
T1/E1 IMA cable and port pinouts
Table 45: 8-port T1/E1 to dual 50 pin connector cable pinouts (Continued) Pair
Signal
Color
From
To
6
RX 3 (tip)
Red/Blue
P1-30
P2-10
RX 3 (ring)
Blue/Red
P1-21
P2-35
TX 4 (tip)
Red/Orange
P1-13
P2-38
TX 4 (ring)
Orange/Red
P1-4
P2-13
RX 4 (tip)
Red/Green
P1-31
P2-14
RX 4 (ring)
Green/Red
P1-22
P2-39
TX 5 (tip)
Red/Brown
P1-14
P2-42
TX 5 (ring)
Brown/Red
P1-5
P2-17
RX 5 (tip)
Red/Slate
P1-32
P2-18
RX 5 (ring)
Slate/Red
P1-23
P2-43
TX 6 (tip)
Black/Blue
P1-15
P2-46
TX 6 (ring)
Blue/Black
P1-6
P2-21
RX 6 (tip)
Black/Orange
P1-33
P2-22
RX 6 (ring)
Orange/Black
P1-24
P2-47
TX 7 (tip)
Black/Green
P1-16
P3-26
TX 7 (ring)
Green/Black
P1-7
P3-1
RX 7 (tip)
Black/Brown
P1-34
P3-2
RX 7 (ring)
Brown/Black
P1-25
P3-27
TX 8 (tip)
Black/Slate
P1-17
P3-30
TX 8 (ring)
Slate/Black
P1-8
P3-5
RX 8 (tip)
Yellow/Blue
P1-35
P3-6
RX 8 (ring)
Blue/Yellow
P1-26
P3-31
17
not used
not used
not used
not used
18
not used
not used
not used
not used
19
not used
not used
not used
not used
20
not used
not used
not used
not used
21
not used
not used
not used
not used
22
not used
not used
not used
not used
23
not used
not used
not used
not used
7
8
9
10
11
12
13
14
15
16
MALC Hardware Installation Guide
613
T1/E1 Uplinks
Table 45: 8-port T1/E1 to dual 50 pin connector cable pinouts (Continued) Pair
Signal
Color
From
To
24
not used
not used
not used
not used
25
not used
not used
not used
not used
Redundant 8-port T1/E1 to dual 50 pin connector cable There are two cables used for redundant T1/E1 Uplink cards. Figure 80 shows the dual 8-port T1/E1 to dual 50-pin connector cable (MALC-CBL-T1/ E1-IMA-R). Figure 82 shows the 50-foot dual 8-port cable. Both cables have the same pinouts. Table 46 lists the pinouts. Figure 81: Dual 8-port T1/E1 to dual 50-pin connector cable
614
MALC Hardware Installation Guide
T1/E1 IMA cable and port pinouts
Figure 82: 50-foot dual 8-port T1/E1 cable
Table 46: Cable 1: P1 to P2 pinouts Pair
Signal
Color
From
To
1
TX 1 (tip)
White/Blue
P1-10
P2-10
TX 1 (ring)
Blue/White
P1-1
P2-1
RX 1 (tip)
White/Orange
P1-28
P2-28
RX 1 (ring)
Orange/White
P1-19
P2-19
TX 2 (tip)
White/Green
P1-11
P2-11
TX 2 (ring)
Green/White
P1-2
P2-2
RX 2 (tip)
White/Brown
P1-29
P2-29
RX 2 (ring)
Brown/White
P1-20
P2-20
TX 3 (tip)
White/Slate
P1-12
P2-12
TX 3 (ring)
Slate/White
P1-3
P2-3
RX 3 (tip)
Red/Blue
P1-30
P2-30
RX 3 (ring)
Blue/Red
P1-21
P2-21
TX 4 (tip)
Red/Orange
P1-13
P2-13
TX 4 (ring)
Orange/Red
P1-4
P2-4
RX 4 (tip)
Red/Green
P1-31
P2-31
RX 4 (ring)
Green/Red
P1-22
P2-22
TX 5 (tip)
Red/Brown
P1-14
P2-14
TX 5 (ring)
Brown/Red
P1-5
P2-5
2
3
4
5
6
7
8
9
MALC Hardware Installation Guide
615
T1/E1 Uplinks
Table 46: Cable 1: P1 to P2 pinouts (Continued) Pair
Signal
Color
From
To
10
RX 5 (tip)
Red/Slate
P1-32
P2-32
RX 5 (ring)
Slate/Red
P1-23
P2-23
TX 6 (tip)
Black/Blue
P1-15
P2-15
TX 6 (ring)
Blue/Black
P1-6
P2-6
RX 6 (tip)
Black/Orange
P1-33
P2-33
RX 6 (ring)
Orange/Black
P1-24
P2-24
11
12
Table 47: Cable 2: P2 to P1 pinouts Pair
Signal
Color
From
To
1
TX 7 (tip)
White/Blue
P2-16
P1-16
TX 7 (ring)
Blue/White
P2-7
P1-7
RX 7 (tip)
White/Orange
P2-34
P1-34
RX 7 (ring)
Orange/White
P2-25
P1-25
TX 8 (tip)
White/Green
P2-17
P1-17
TX 8 (ring)
Green/White
P2-8
P1-8
RX 8 (tip)
White/Brown
P2-35
P1-35
RX 8 (ring)
Brown/White
P2-26
P1-26
2
3
4
Table 48: Cable 3: P1 to P3 pinouts Pair
Signal
Color
From
To
1
TX 1 (tip)
White/Blue
P1-10
P3-26
TX 1 (ring)
Blue/White
P1-1
P3-1
RX 1 (tip)
White/Orange
P1-28
P3-2
RX 1 (ring)
Orange/White
P1-19
P3-27
TX 2 (tip)
White/Green
P1-11
P3-30
TX 2 (ring)
Green/White
P1-2
P3-5
RX 2 (tip)
White/Brown
P1-29
P3-6
RX 2 (ring)
Brown/White
P1-20
P3-31
TX 3 (tip)
White/Slate
P1-12
P3-34
TX 3 (ring)
Slate/White
P1-3
P3-9
2
3
4
5
616
MALC Hardware Installation Guide
T1/E1 IMA cable and port pinouts
Table 48: Cable 3: P1 to P3 pinouts (Continued) Pair
Signal
Color
From
To
6
RX 3 (tip)
Red/Blue
P1-30
P3-10
RX 3 (ring)
Blue/Red
P1-21
P3-35
TX 4 (tip)
Red/Orange
P1-13
P3-38
TX 4 (ring)
Orange/Red
P1-4
P3-13
RX 4 (tip)
Red/Green
P1-31
P3-14
RX 4 (ring)
Green/Red
P1-22
P3-39
TX 5 (tip)
Red/Brown
P1-14
P3-42
TX 5 (ring)
Brown/Red
P1-5
P3-17
RX 5 (tip)
Red/Slate
P1-32
P3-18
RX 5 (ring)
Slate/Red
P1-23
P3-43
TX 6 (tip)
Black/Blue
P1-15
P3-46
TX 6 (ring)
Blue/Black
P1-6
P3-21
RX 6 (tip)
Black/Orange
P1-33
P3-22
RX 6 (ring)
Orange/Black
P1-24
P3-47
7
8
9
10
11
12
Table 49: Cable 4: P2 to P4 pinouts Pair
Signal
Color
From
To
1
TX 7 (tip)
White/Blue
P2-16
P4-26
TX 7 (ring)
Blue/White
P2-7
P4-1
RX 7 (tip)
White/Orange
P2-34
P4-2
RX 7 (ring)
Orange/White
P2-25
P4-27
TX 8 (tip)
White/Green
P2-17
P4-30
TX 8 (ring)
Green/White
P2-8
P4-5
RX 8 (tip)
White/Brown
P2-35
P4-6
RX 8 (ring)
Brown/White
P2-26
P4-31
2
3
4
MALC Hardware Installation Guide
617
T1/E1 Uplinks
618
MALC Hardware Installation Guide
16 ADSL
This chapter describes the MALC ADSL cards and explains how to configure them. It includes:
•
Overview, page 619
•
ADSL Cards, page 620
•
Activating ADSL cards, page 643
•
Configuring ADSL interfaces, page 651
•
Updating ADSL Annex A card profiles, page 689
•
ADSL Testing, page 694
•
ADSL cable and port pinouts, page 700
Overview MALC ADSL interfaces provide a standards-based, high-speed DSL interface between the MALC and CPE devices. Asymmetric Digital Subscriber Line (ADSL) is one of the flavors of DSL. DSL is a prominent transmission technology because DSL uses existing telephone lines to solve the first mile connection issue. It has proven to be more expensive to dig trenches and lay fiber than to deploy the technology to make more use of the twisted wire pairs of existing telephone lines. A voice signal uses only a portion of the frequencies which can be sent on a twisted wire pair. Voice uses a frequency range of below 4kHz while ADSL uses above 25kHz. ADSL is called Asymmetric because the data flow is greater in one direction. The range of frequencies used by ADSL is separated into two frequency bands — the upstream band to the central office and the downstream band to the end user. The downstream band is larger, hence downloads to a home computer are faster than uploads. Signals sent down copper wire may be impaired by distance from the central office, noise on the wire, and radio interference from AM radio stations. ADSL devices can adjust to signal conditions to achieve the highest possible speeds, so usually no adjustment is needed. This ability to adjust to signal conditions is called “training.” The default settings which are used for ADSL
MALC Hardware Installation Guide
619
ADSL
cards in the MALC are suitable for most cases, though for fine tuning the ADSL2+ connection there are some configuration options. To deal with accuracy of transmission of packets, and overall throughput ADSL2+ offers a number of options which are configurable on the MALC: Signal to Noise Ratio
Provides a mechanism to adjust the robustness of the ADSL Link and hence the speed.
Transport Mode
Defines how packets are sent down the line. Fast provides a simple contiguous message which does not require much processing time to disassemble and reassemble packets. Interleaved provides greater protection from short bursts of noise that can result in lost packets
Bonding
Bonding is the ability to have multiple ports work together, so they appear as one larger pipe. ADSL bonding allows combining two ports.
ADSL Cards The following cards provide ADSL interfaces:
•
ADSL2+ Bond cards: MALC-ADSL-BCM-48A, MALC-ADSL+SPLTR-BCM-48A-2S MALC-ADSL-BCM-48B, MALC-ADSL+POTS-PKT-BCM-48A-2S, and MALC-ADSL+POTS-PKT-BCM-48B-2S: 48 ADSL interfaces in single-slot and dual slot card that supports ADSL2+ Annex A/M or ADSL Annex B; variants include POTS splitter or POTS interfaces. See ADSL2+ bond cards on page 631.
•
ADSL 2+ cards (no bonding): MALC-ADSL-A/M, MALC-ADSL-48B, MALC-ADSL + SPLTR-48A/ M-2S, MALC-ADSL+POTS-TDM/PKT-48A/M-2S: 48 ADSL interfaces in single-slot card that supports ADSL2+ Annex A/M or ADSL Annex B; variants include POTS splitter or POTS interfaces. See 48-port ADSL cards on page 636
•
MALC-ReachDSL-24: 24-port single-slot ReachDSL card and 24-port ReachDSL splitter card with POTS which support both ADSL and ReachDSL technologies. See 24-port ReachDSL cards (ReachDSL-24, ReachDSL+SPLTR-24-2s) on page 640
620
MALC Hardware Installation Guide
Overview
Transmission modes Zhone ADSL cards support the following transmission modes. Transmission Mode Description ADSL2
The modem negotiates rates up to 12 Mbps downstream and 3.5 Mbps upstream.G.992.3 ADSL2.
ADSL2plus
The modem negotiates rates up to 24 Mbps downstream and 1 Mbps upstream (Annex M allows upstream up to 3.5 Mbps) G.992.5 ADSL2+.
Autonegotiate
The modem automatically negotiates all supported transmission modes. The modem uses the G.hs protocol to negotiate a transmission mode in this order: T1.413, then G.dmt, then G.lite.
Full rate
Full rate T1 ADSL modem. This is used for connecting to full rate T1.413 issue 2 modems.
G.dmt
G.dmt is a higher-bandwidth variant of G.lite that provides for downstream speeds of up to 8160 Kbps. G.dmt is defined in ITU specification G.992.1.
G.hs
The modem negotiates only G.dmt and G.lite modes. G.dmt has priority over G.lite
G.lite
The modem negotiates rates up to 1536 Kbps upstream and 512 Kbps downstream (G.992.2)
Rate adaptation The ADSL cards support rate adaptation, which enables them to respond to changing line conditions by adjusting the line rate. At startup, ADSL modems may negotiate a data rate. The rateMode parameter allows the selection of three types of rate adaption. The following types of rate adaption are supported:
•
fixed: rate is fixed at the max configured rate.
•
adaptatstartup: rate is set to the best possible speed (between min and max) during training and does not change afterward.
•
adaptatruntime: rate is set to the best possible speed (between min and max) during training and can change afterward based on changing conditions
The default option is adaptatruntime, so the rate can change based on changing conditions.
MALC Hardware Installation Guide
621
ADSL
Advanced Configurations ADSL modems use signal-to-noise ratio (SNR) measurements to adjust signal transmission to achieve greater performance. The Zhone default settings for SNR parameters normally provide an excellent throughput rate for most applications.
Fine Tuning ADSL Video Performance The parameters for tuning performance may be adjusted for video. However, the parameters are part of a complex system, so before you make changes to the default settings you should understand the SNR parameters and how they work together. This section describes guidelines for adjusting SNR settings and will not be correct for every deployed line. Subscribers with “noisy” lines may need to have their ADSL2+ parameters adjusted so that the train rates are high enough to meet the service bandwidth requirements. This section discusses how adjusting SNR Margins can increase train rates while keeping errors on the line to a minimum. SNR compares the level of the desired signal to the level of background noise. The better the signal and the less obtrusive the background noise, the higher the ratio. The lower the SNR, the greater effect noise will have on the ADSL2+ signal. Noise is anything that will corrupt the sent signal and is normally from AM radio transmissions, though poor physical connections, deformities in the line, transformers, and even appliances may introduce noise. If it weren’t for noise you could set the SNR very high and not be worried about signal degradation. Unfortunately in the field, not all ADSL2+ lines will train when the SNR margin target is set high. With the target SNR margin set too high, the ADSL2+ training algorithm would try to make the line so clean (no noise) that the train rate would be very low and not capable of supporting the services sold. Figure 83: Bins shown with SNR Margin set to 9.0 dB SNR Margin
6.0 dB
3.0 dB
POTS & Upstream Data
9.0 dB
bins 0 -31
622
MALC Hardware Installation Guide
bins 32 - 511 (not to scale)
Frequency Ranges (bins)
Overview
The frequency bands on DSL lines are segmented into small frequency ranges called bins or tones. These small ranges make it so the frequency can be sampled to judge the value. There are 512 bins in a signal. The voice and upstream data traffic use only a small portion (bins 0-31) and are not relevant to this discussion. Bins 32-511 are used for downstream data traffic. If the SNR is dropped to a lower rate with the same signal to noise ratio, more of the sampled bins are used. Figure 84: Bins shown with SNR Margin set to 6.0 dB SNR Margin
6.0 dB
3.0 dB
POTS & Upstream Data
9.0 dB
bins 0 -31
bins 32 - 511 (not to scale)
Frequency Ranges (bins)
Figure 83 and Figure 84 show a snapshot of the signal. There are three parameters in the adsl-co-profile and the adsl-cpe-profile which define the training speeds: targetSnrMgn, maxSnrMgn, and minSnrMgn. Parameter
Profile
Description
targetSnrMgn
adsl-co-profile, adsl-cpe-profile
The Target SNR Margin (targetSnrMgn) is the SNR Margin targeted when training. Values are from 0 to 310 in tenths of dBs. A value of 60 would mean 6.0 dB SNR Default: 0 Recommendation for Video: 60
maxSnrMgn
adsl-co-profile, adsl-cpe-profile
Maximum SNR Margin (maxSnrMgn) is the maximum SNR Margin allowed on the link before a retrain is forced. Values are from 0 to 310 in tenths of dBs. A value of 150 would mean 15.0 dB SNR. Default: 0 Recommendation for Video: 150
minSnrMgn
adsl-co-profile, adsl-cpe-profile
Minimum SNR Margin (minSnrMgn) is the minimum SNR Margin allowed on the link before a retrain is forced. Values are from 0 to 310 in tenths of dBs. Default: 0 Recommendation for Video: 30
MALC Hardware Installation Guide
623
ADSL
SNR performance is monitored to maintain a bit error rate (BER) of 10-7 or better. The minimum margin is the floor at which the modem will maintain a connection. The maximum margin is the ceiling for power cutback. The target margin is the lowest margin that the modem tries to achieve when training and adapting. Figure 85: Signal-to-noise margins
connection drops and retrains
signal-to-noise margin
maximum modem reduces power to maintain connection
target
level the modem trains to modem attempts to increase margin
minimum
connection drops and retrains
These three values alone allow the ADSL2+ line to train to a maximum rate given the target SNR Margin value. That initial train rate would remain unless the SNR Margin moves beyond the Minimum or Maximum SNR Margin. At that time the link is forced to retrain. The system will try to attain the target signal-to-noise margin when training. If the line reaches the maximum bit rate and the actual margin is below the maximum margin, the line operates normally. If the margin rises above the target margin, the modem drops the connection and retrains once, then drops the power to enforce the maximum margin. If, after a connection is made, the margin drops below the target margin, the modem attempts to increase the margin. If the minimum margin cannot be kept, the modem drops the connection and retrains. Note within the above table are the Zhone recommended values for video. These SNR Margin values may not be appropriate on every link, but based on Zhone’s testing they result in high train rates and low error rates on most lines. For loops with excessive noise which prevents the necessary data rate for video services, adjust the targetSnrMgn to 60. Lowering the Target SNR Margin should allow the line to train higher. Retraining the signal takes a considerable amount of time (as much as 30 seconds). An ADSL2+ feature Seamless Rate Adaption (SRA) can make more minute adjustments within the minimum and maximum SNR margins without the end user being aware of the rate changes or time to retrain.
624
MALC Hardware Installation Guide
Overview
Seamless Rate Adaptation After an ADSL2+ link trains the noise conditions on the line could improve. Seamless Rate Adaptation allows the ADSL2 link to take advantage of the lower noise and will increase the rate of the link without the need for a retrain. SRA may also reduce the rate on the line when noise levels increase slightly. The Upshift SNR Margin (upshiftSnrMgn) and Downshift SNR Margin (downshiftSnrMgn) are used to determine the values to conduct the rate adaptation by adding or removing bins to stay at the target SNR. Time parameters work with the Upshift and Downshift SNR Margins, Minimum Upshift SNR Time (minUpshiftTime) and Minimum Downshift Time (minDownshiftTime) for the Central Office (adsl-co-profile) and Minimum Upshift SNR Margin (minUpshiftSnrMgn) and Minimum Upshift SNR Margin (minDownshiftSnrMgn), which are also for the modem side of the connection (adsl-cpe-profile). The CO profile and CPE profile use different names for the similar parameter because the CO is the head of the connection and accepts requests from the CPE devices, but can determine the minimum time to conduct the SRA. All of these parameters work together in a system. When the SNR rises above the Upshift SNR Margin and stays there for a specified amount of time (from the minUpshiftTime and minUpshirtSnrMgn) it is assumed that the noise level has improved and the rate is allowed to increase. As the SNR moves below the Downshift SNR Margin value and stays there for a specified amount of time, the noise level has increased and the current noise level can not sustain the current downstream rate without increased errors so the rate is decreased. The increases and decreases in rate are done “seamlessly” and without the need to retrain the line.
MALC Hardware Installation Guide
625
ADSL
Figure 86: SNR Margins working as a system SNR Margin maxSnrMgn (150 = 15 dB)
15.0 dB
minDownshiftSnrMgn 12.0 dB
no change
1
seamless upshift upshiftSnrMgn (100 = 10 dB) targetSnrMgn
3
9.0 dB
2 6.0 dB
downshiftSnrMgn (100 = 10 dB)
seamless downshift
minUpshiftSnrMgn
4
3.0 dB
minSnrMgn (30 = 3 dB)
forced retrain Time
In Figure 86 we see the Zhone default values for the SNR Margin profile fields in context. This figure shows how the five SNR Margin parameters work as a system to ensure the best train rate possible within the given parameters. The red line represents how the SNR changes over time. The SNR Margin increases, but does not move past the Upshift SNR Margin at (1) so the train rate remains the same. At (2) on the graph the SNR Margin has dipped below the Downshift SNR Margin and stays below downshiftSnrMgn longer than the minimum downshift margin time. This situation results in a removal of bins in order to return to the Target SNR Margin. This change is a seamless decrease in the data rate from the user’s perspective. The SNR Margin then rises and moves above the Upshift SNR Margin for longer than minUpshiftSnrMgn period resulting in a seamless increase in the rate at (3). In this situation bins are added to get back to the Target SNR Margin. The SNR then moves down quickly below the Min SNR Margin which forces a retrain at (4). It is important to understand that each parameter plays an important role in the training of the ADSL2+ line. The SNR margins should always have maxSnrMgn > upshiftSnrMgn > targetSnrMgn > downshiftSnrMgn > minSnrMgn. If the Mininimum and Maximum SNR Margins are brought too close to the target SNR Margin on a line which has changing SNR, there could be excessive retraining. If the SRA values Upshift SNR Margin and Downshift SNR Margin are too close to the Maximum and Minimum SNR values, SRA will not be useful, the line will retrain by the Minimum and Maximum SNR values.
626
MALC Hardware Installation Guide
Overview
Setting the SRA shift values too high for the upshift and too low for the downshift makes the probability of an SRA shift unlikely. A good configuration rule for determining downshiftSnrMgn and upshiftSnrMgn: • •
downshiftSnrMgn = targetSnrMgn + 10 upshiftSnrMgn = targetSnrMgn - 10
SRA is only supported in the downstream data direction and the CPE is the controlling device for the feature. SRA is configured in the adsl-cpe-profile. Changes to the adsl-coprofile are ignored. There are two timers used to space SRA events. The downstream (CO to CPE) SRA timers are located in the adsl-cpe-profile. The SRA timers are in units of seconds so a value of 60 means an SRA event can only occur every 60 seconds. Zhone’s recommended settings are: • •
minUpshiftSnrMgn = 30 minDownshiftSnrMgn = 30
The SRA timers start after the first SRA action which means that an SRA rate shift can occur immediately after initial train up. For SRA to operate the CPE must support SRA and must have SRA enabled.
Transport mode: Fast or Interleaved ADSL2+ operates in one of two modes: Fast or Interleaved. In Fast mode data packets are placed on the ADSL2+ line contiguously, so the data is provided in a sequential stream. The other end of the ADSL2+ line takes off the data packets in order and moves them up the protocol stack for processing. In Interleaved mode the data packets are broken into smaller segments, and then sent down the line. The advantage of fast mode is that the data is streamed directly as it is needed, so there is no disassembly and assembly processing. However a short burst of noise on the line can corrupt enough data that the far end device can not correct the errors. ADSL2+ modems have the ability to correct errors; however error correction works well when there are a small number of errors to correct. Too many bit errors in a packet can mean the errors can not be corrected and result in lost data packets. Lost data packets require that the same data packet be retransmitted. With the smaller segments used with the interleaving mode, the segements may be intermixed with segments from other packets before being placed on the ADSL2+ line. If a burst of noise causes corruption, each entire larger pre-disassembled packet is not affected as much, but the smaller pieces which could belong to several different packets are affected. Because only smaller segments of the larger packet are affected, error correction is more likely to have enough information to build the packet correctly on reassembly. The data packets handed up the stack will have no issues.
MALC Hardware Installation Guide
627
ADSL
Figure 87: Fast and interleaved mode whole larger segment affected
Fast mode
Large noise burst Interleaved mode
most of larger segment remains intact
Assembly
Reassembly
The drawback with Interleaving is that the process of interleaving the small data blocks and reassembling the data packets at the far end introduce some delay and lowers the data rate. It is recommended to use Fast mode with data applications. Interleaved mode should be used with video applications. Video applications usually do not support retransmissions. If a data packet is corrupted it is discarded and will not be retransmitted so it is important that as many packets as possible arrive in good condition.
Fast and Interleaved Configuration Notes On the MALC Fast and Interleave modes are configured using the adslChannelMode field in the adsl-profile. The following settings are only used during Fast operations: Parameter
Profile
Description
fastMinTxRate
adsl-co-profile, adsl-cpe-profile
Minimum transmit rate in bits per second (bps) for channels configured for fast transmission mode. fastMinTxRate must be less than fastMaxTxRate. Default: 0
fastMaxTxRate
adsl-co-profile, adsl-cpe-profile
Configured maximum transmit rate (bps) for ADSL Fast channels. fastMaxTxRate must be greater than fastMinTxRate. Default: 8460Kbps
628
MALC Hardware Installation Guide
Overview
Parameter
Profile
Description
threshFastRateUp
adsl-co-profile, adsl-cpe-profile
Not currently used. The change in the configured rate that causes the system to send an adslAtucRateChangeTrap.The system sends a trap whenever: ChanCurrTxRate bond add member 1-7-1-0/gbond 1-7-1-0/adsl zSH> bond add member 1-7-1-0/gbond 1-7-2-0/adsl
To delete a member of a gbond group: Used the bond delete member command SH> bond delete member 1-7-1-0/gbond 1-7-2-0/adsl
To delete a gbond group: Use the bond delete group command to delete a bond group zzSH> bond delete group 1-7-1-0/gbond
To move members of a gbond group: In the following example we will create two bond groups. Group 60 with two members, ports 1 and 2, and group 61 with one member, port 3. Note that we can move port 2 into the group with port 3 because they are contiguous ports. zSH> bond add group 1-7-10-0/gbond zSH> bond add group 1-7-11-0/gbond zSH> bond add member 1-7-10-0/gbond 1-7-1-0/adsl zSH> bond add member 1-7-10-0/gbond 1-7-2-0/adsl zSH> bond add member 1-7-11-0/gbond 1-7-3-0/adsl zSH> bond move 1-7-10-0/gbond 1-7-11-0/gbond 1-7-2-0/ adsl
The result of this example is that group 10 has one member, port 1, and that group 11 has two members, ports 2 and 3.
ADSL2+ bond cards This chapter includes the MALC ADSL2+ Broadcom bond cards with POTS and with splitters and describes how to configure them. The MALC supports the following ADSL2+ bond cards:
•
MALC-ADSL-BCM-48A
•
MALC-ADSL-BCM-48B
•
MALC-ADSL+POTS-PKT-BCM-48A-2S
•
MALC-ADSL+POTS-PKT-BCM-48B-2S
•
MALC-ADSL+SPLTR-BCM-48A-2S
MALC Hardware Installation Guide
631
active fault pwr fail 1- 48 LINE
ADSL48 Bond ANNEX A & POTS VOIP
ADSL48 Bond ANNEX A & SPLITTER
ADSL48 Bond ANNEX B & POTS VOIP
ma0505
ADSL 48 Bond Annex B
1- 48 LINE
ma0505
ADSL 48 Bond Annex A
active fault pwr fail
ADSL
The ADSL2+ Bond Annex A/M card (MALC-ADSL-BCM-48A) and the ADSL2+ Bond Annex B card (MALC-ADSL-BCM-48B) are 48-port cards that occupy a single slot in the MALC chassis. These cards respectively support ADSL2+ Annex A/M and ADSL2+ Annex B. The standards supported are ANSI T1.413 Issue 2, G.992.1 (G.dmt), G.992.2 (G.lite), and ADSL2+ (G.992.5) standards. The ADSL2+ Bond Annex A/M card (MALC-ADSL+SPLTR-BCM-48A-2S) is a two-slot card with integrated POTS splitters to allow up to 48 POTS lines to be connected into the card. Each of these lines are combined with the ADSL2+ signal internally and exits the line card in the subscriber direction with both ADSL and POTS on the loop. In the network direction the POTS is split from the ADSL signal keeping POTS on copper pairs and placing the ADSL data information on the ATM or IP network. Each 48-port ADSL+POTS cards occupies two slots in the MALC chassis and provides 48 ports of integrated ADSL and POTS service. It supports the ANSI T1.413 Issue 2, G.992.1 (G.dmt) and G.992.2 (G.lite), G.992.3 and
632
MALC Hardware Installation Guide
Overview
G.992.4 (ADSL2), G.992.5 (ADSL2+), Annex A, and Annex M ADSL standards. The MALC-ADSL+POTS-PKT-BCM-48A-2S and MALC-ADSL+POTS-PKT-BCM-48B-2S cards support traditional TDM POTS services as well packet voice for use in a VoIP network. Table 50: ADSL-48-BCM specifications Specification
Description
Size
1 slot: MALC-ADSL-BCM-48A, MALC-ADSL-BCM-48B 2 slot: MALC-ADSL+POTS-PKT-BCM-48A-2S, MALC-ADSL+POTS-PKT-BCM-48B-2S, MALC-ADSL+SPLTR-BCM-48A-2S
Density
48 ports ADSL
Connectors
One (1) Champ 96-pin telco connector
Standards supported
ANSI T1.413.2 (auto-detected) G.992.1 (G.DMT) (auto-detected) G.992.2 (G.Lite) G.994.1 (G.hs) G.992.3 and G.992.4 (ADSL2) G.992.5 (ADSL2+)
Line characteristics
Annex A supported (ADSL2+ over POTS) Annex B supported (ADSL2+ over ISDN) Annex A/M supported (ADSL2/ADSL2+) Fast Path or Interleaved mode supported on a per port basis Fast Retrain supported
MALC Hardware Installation Guide
633
ADSL
Table 50: ADSL-48-BCM specifications (Continued) Specification
Description
Supported line rates
T1.413:
• •
32 Kbps to 12 Mbps downstream 32 Kbps to 1024 Kbps upstream
G.lite:
• •
64 Kbps to 4 Mbps downstream 32 Kbps to 1024 Kbps upstream
ADSL2
• • • •
Annex A: 32 Kbps to 10 Mbps downstream Annex A: 32 Kbps to 1.2 Mbps upstream Annex B: 32 Kbps to 10 Mbps downstream Annex B: 32 Kbps to 1.2 Mbps upstream
ADSL2+:
• • • • • • ATM support
Annex A: 32 Kbps to 28 Mbps downstream Annex A: 32 Kbps to 1.2 Mbps upstream Annex B: 32 Kbps to 28 Mbps downstream Annex B: 32 Kbps to 1.2 Mbps upstream Annex M: 32 Kbps to 26 Mbps downstream Annex M: 32 Kbps to 3 Mbps upstream
Cell Relay switching onto ATM bus to Uplink card Default VPI/VCI ranges (per port):
• •
VPI: 0 to 15 VCI: 0 to 63
Metallic test function
Look-out test
Power ADSL 2+
23 Watts nominal 38.16 W maximum total. This is at maximum distance with all ports trained at ADSL2+ rates
634
Power ADSL 2+ splitter
23 Watts nominal
Power ADSL
23 Watts nominal
2+ combo
114 W maximum
Chip set
Broadcom
MALC Hardware Installation Guide
38.16 W maximum total. This is at maximum distance with all ports trained at ADSL2+ rates
Overview
These cards support Annex A/M, Annex B, Annex A with POTS splitter, Annex A with POTS packet VoIP support, and Annex B with POTS packet VoIP support. The ADSL2+ bond cards on the MALC have the following types and software images: Table 51: MALC bond card types software images Card
Type
Name of software image
MALC-ADSL-BCM-48A (single slot ADSL Annex A/M Bond)
5080
malcadsl48anxabond.bin
5081
malcadsl48anxbbond.bin
MALC-ADSL+POTS-PKT-BCM-48A-2S (double slot ADSL Annex A/M POTS VoIP) MALC-ADSL+SPLTR-BCM-48A-2S (double slot ADSL Annex A/M POTS Splitter) MALC-ADSL-BCM-48B (single slot ADSL Annex B Bond) MALC-ADSL+POTS-PKT-BCM-48B-2S (double slot ADSL Annex B POTS VoIP)
MALC Hardware Installation Guide
635
ADSL
48-port ADSL cards The ADSL 48 port cards are based on the Conexant chip set and do not support ADSL bonding
active fault pwr fail
.
1- 48 LINE
ADSL 48 Annex B
ADSL+POTS 48 ANNEX A/M
ma0669ADSLcnxnt
ADSL 48 Annex A/M
The Conexant chipset based 48-port ADSL cards support ADSL Annex B (MALC-ADSL-48B) and Annex A/Annex M (MALC-ADSL-48A/M, MALC-ADSL + SPLTR-48A/M-2S, MALC-ADSL+POTS-TDM/ PKT-48A/ M-2S). Annex A/M is used for ADSL service functioning over POTS. Annex M is an enhancement to Annex A to improve upstream bandwidth. Annex B is used for ADSL service over ISDN Digital Phone services. For Annex A and Annex M the discrete multitone (DMT) modulation technique used in ADSL2+ modems modulates user data into as many as 511 separate frequency-division multiplexed modem channels. Each modem channel (or tone) occupies approximately 4KHz of analog bandwidth. The ADSL DMT modem does not use the first 25KHz of the signal, which are the
636
MALC Hardware Installation Guide
Overview
frequencies POTS lines use. The ADSL card has an optional integrated splitter. For Annex B, the discrete multitone (DMT) modulation technique used in G.dmt and G.lite modems modulates user data into as many as 255 separate frequency-division multiplexed modem channels. Each modem channel (or tone) occupies approximately 4KHz of analog bandwidth. The ADSL DMT modem does not use the first 128 KHz of the signal, which are the frequencies ISDN lines use. This ADSL card does not have an integrated splitter. It requires an external splitter. The ADSL Annex B card (MALC-ADSL-48B) and ADSL Annex A/M card (MALC-ADSL-48A/M) are 48-port cards which occupy a single slot in the MALC chassis. The ADSL/POTS Splitter card (MALC-ADSL + SPLTR-48A/M-2S), and ADSL and POTS combination card (MALC-ADSL+POTS-TDM/ PKT-48A/ M-2S) are 48-port cards which occupy two slots in the MALC chassis. The ADSL/POTS Splitter card (MALC-ADSL + SPLTR-48A/M-2S) provides 48 ADSL ports and 48 POTS ports separately. The ADSL/POTS combination cards provide integrated ADSL and POTS service. Table 52: ADSL-48 specifications Specification
Description
Size
1 slot: MALC-ADSL-48A/M, MALC-ADSL-48B 2 slots: MALC-ADSL + SPLTR-48A/M-2S, MALC-ADSL+POTS-TDM/ PKT-48A/M-2S
Density
48 ports ADSL: MALC-ADSL-48A/M, MALC-ADSL-48B, MALC-ADSL + SPLTR-48A/M-2S 48 ports ADSL and 48 ports POTS: MALC-ADSL+POTS-TDM/ PKT-48A/M-2S
Connectors
One (1) 96-pin telco connector: MALC-ADSL-48A/M, MALC-ADSL-48B, MALC-ADSL+POTS-TDM/ PKT-48A/ M-2S Two (2) 96-pin telco connectors: MALC-ADSL + SPLTR-48A/M-2S
Standards supported
ANSI T1.413.2 (auto-detected) G.992.1 (G.DMT) (auto-detected) G.992.2 (G.Lite) G.994.1 (G.hs) G.992.3 and G.992.4 (ADSL2) G.992.5 (ADSL2+) Annex M, Annex L Reach Extended ADSL2 (READSL2)
MALC Hardware Installation Guide
637
ADSL
Table 52: ADSL-48 specifications (Continued) Specification
Description
Line characteristics
Annex A supported (ADSL2+ over POTS) Annex B supported (ADSL2+ over ISDN) Fast Path or Interleaved mode supported on a per port basis Fast Retrain supported
Supported line rates
T1.413:
• •
32 Kbps to 12 Mbps downstream 32 Kbps to 1024 Kbps upstream
G.lite:
• •
64 Kbps to 4 Mbps downstream 32 Kbps to 1024 Kbps upstream
ADSL2
• •
Annex A: 32 Kbps to 12 Mbps downstream
• • • •
Annex M: 32 Kbps to 10 Mbps downstream
Annex A: 32 Kbps to 1024 Kbps (512 Kbps for G.lite) upstream
Annex M: 32 Kbps to 2.4 Mbps upstream Annex B: 32 Kbps to 10 Mbps downstream Annex B: 32 Kbps to 2.4 Mbps upstream
ADSL2+:
ATM support
• •
Annex A: 32 Kbps to 24 Mbps downstream
• • •
Annex M: 32 Kbps to 22 Mbps downstream
•
Annex B: 32 Kbps to 2.4 Mbps upstream
Annex A: 32 Kbps to 1024 Kbps (512 Kbps for G.lite) upstream
Annex M: 32 Kbps to 2.4 Mbps upstream Annex B: 32 Kbps to 22 Mbps downstream
Cell Relay switching onto ATM bus to Uplink card Default VPI/VCI ranges (per port):
• •
638
VPI: 0 to 15 VCI: 0 to 63
Metallic test function
Look-out test
Main components
ADSL chipset, 8 ports each
MALC Hardware Installation Guide
Overview
Table 52: ADSL-48 specifications (Continued) Specification
Description
Power
MALC-ADSL-48A/M, MALC-ADSL-48B, MALC-ADSL + SPLTR-48A/M-2S 23 Watts nominal plus .72 W additional per active ADSL2+ port .67 Watts additional per active ADSL port 57.5 W typical 57.5 W maximum total. This is at maximum distance with all ports trained at ADSL2+ rates MALC-ADSL+POTS-TDM/ PKT-48A/M-2S 90 Watts typical 133 Watts maximum
Chip set
Conexant
MALC Hardware Installation Guide
639
ADSL
The 24-port single-slot ReachDSL card (ReachDSL-24) and double-slot ReachDSL+Splitter card (ReachDSL+SPLTR-24-2s) support both ADSL and ReachDSL technologies.
active fault pwr fail
active fault pwr fail
24-port ReachDSL cards (ReachDSL-24, ReachDSL+SPLTR-24-2s)
•
activation or handshake
•
training
•
channel analysis
•
exchange
ma 0 5 2 4
ma0709
ReachDSL technology addresses the severe challenges facing mass deployment in non-loaded loops that support POTS regardless of distance, bridged taps, and premises wiring. ReachDSL is strong as a high performance subscriber line solution that allows consistent delivery of services to markets, at distances often as great as 70,000 feet. 1 - 24 1 - 24 1 - 24 Line POTS By using the lower portion of the frequency spectrum, ReachDSL provides simultaReachDSL neous POTS and broadband data services ReachDSL +SPLITTER 24 over even the worst loop plant and premises wiring imaginable. ReachDSL reliably delivers high-speed service to customers that no other DSL technology can reach with data rates up to 2.2 Mbps upstream and downstream. ReachDSL technology opens new markets and allows service providers to cost effectively serve markets previously unreachable. ReachDSL delivers up to 2.2 Mbps throughput, upstream and downstream, and capability to provide that bandwidth symmetrically or asymmetrically. This enables providers to provision traditional residential and business services over the same technology. The 24-port ReachDSL card occupies a single slot in the MALC chassis. It supports the ANSI T1.413 Issue 2, G.992.1 (G.dmt) and G.992.2 (G.lite) ADSL standards and ReachDSL. When the ReachDSL modem is started, it performs a sequence of operations known as the startup phase. This sequence consists of four principal stages:
During activation phase, the modem identifies the remote modem and prepares for the next stages of startup. During training phase, the modem sets the receiver gain and the transmitter level. It also configures the equalizer and the echo cancellation unit.
640
MALC Hardware Installation Guide
Overview
In channel analysis phase, the modem measures the channel’s characteristics in order to set the appropriate bit load and gain for each tone. In this phase, all channel parameters are taken into account in order to optimize the modem performance for the channel conditions that were detected. During the exchange stage, the modem exchanges information with the remote modem to settle the transmit and receive parameters that are accepted on both sides. After this, the data transfer process begins. When the ReachDSL card and modem connect, they attempt to establish the highest line rate for the connection. The highest line rate may be up to 8 Mbps ADSL and 2.2 Mbps in ReachDSL operation. Table 53: ReachDSL specifications Specification
Description
Size
1 slot
Density
24 ports ADSL
Connectors
One (1) RJ-21X 50-pin telco connector
Standards supported
ANSI T1.413.2 (auto-detected) G.992.1 (G.DMT) (auto-detected) G.992.2 (G.Lite) G.994.1 (G.hs) ReachDSL
Line characteristics
Annex A supported (ADSL over POTS) Fast Path or Interleaved mode supported on a per port basis Fast Retrain supported
MALC Hardware Installation Guide
641
ADSL
Table 53: ReachDSL specifications (Continued) Specification
Description
Supported line rates
32 Kbps to 8160 Kbps ADSL (2. 2 Mbps ReachDSL mode) downstream 32 Kbps to 2197 Kbps (2. 2 Mbps ReachDSL mode) upstream Maximum reach distances decrease with plant construction including aerial feeder cables, finer gauges and presence of any noise, power influence, RF egress and outside plant or inside wire bridge taps. Successful synchronization and delivery of a minimum rate has been reported on 19 gauge copper rural loops as long as 70,000 feet, or up to 21 kilometers. This is obtained by transmitting and receiving at overlapped frequencies from 20 to 120 KHz. To accomplish this an active digital signal echo canceller is used instead of frequency division so near-end cross talk is a limit as it randomly causes errors as the signal level drops. If POTS service is coexistent on the plant and the cable feeder plant was loaded, use of a smart coil for good voice frequency performance is recommended versus unloaded the plant. Gauge
Est. Max length
26 < 20 Kft 24 < 30 Kft 22 < 45 Kft 19 < 60 Kft Gauge/length estimates assume single gauge screened PIC cable (no interferes, i.e. digital circuits) Buried distances @ 70 degrees Fahrenheit (no Bridge Taps). ATM support
Cell Relay switching onto ATM bus to Uplink card Default VPI/VCI ranges (per port):
• •
642
VPI: 0 to 7 VCI: 32 to 63
Metallic test function
Look-out test
Redundancy
None
Main components
ADSL chipset, 8 ports each
Power consumption
30 W nominal (all ports initialized, no ports trained) plus 1.1 W additional per active ADSL interface 56.4 W maximum
MALC Hardware Installation Guide
Activating ADSL cards
Activating ADSL cards Each card installed in the system must have a card-profile. Each type of slot card requires different settings in the card-profile. Tip: You can specify the name of the software image for a card in a card-profile or a type-module. Each card of a particular type can share a single type-module. Settings in type-modules can be overridden by settings in card-profiles. For 1.12.x modules, the default image name is automatically added as the sw-file-name parameter in the card-profile. ADSL slot cards on the MALC have the following types and software images: Table 54: MALC ADSL card types Card
Type
Name of software image
MALC-ADSL-BCM-48A (single slot ADSL Annex A/M Bond)
5080
malcadsl48anxabond.bin
5065
malcxdsl48anxam.bin
MALC-ADSL-48B (single slot ADSL Annex B)
5039
malcxdsl48anxb.bin
MALC-ReachDSL-24
5064
malcreachdsl.bin
MALC-ReachDS+SPLTRL-24-2S
5075
malcreachdsl.bin
MALC-ADSL-BCM-48B (single slot ADSL Annex B Bond) MALC-ADSL+SPLTR-BCM-48A-2S (dual slot ADSL Annex A/M Bond with POTS splitter) MALC-ADSL+POTS-PKT-BCM-48A-2S (dual slot ADSL Annex A/M Bond with POTs VoIP) MALC-ADSL+POTS-PKT-BCM-48B-2S (dual slot ADSL Annex B Bond with POTs VoIP) MALC-ADSL-48A/M (single slot ADSL Annex A/Annex M) MALC-ADSL+POTS-48 TDM/ PKT-48A/M-2S (two slot ADSL Annex A/Annex M with TDM POTS and packet voice support)
MALC Hardware Installation Guide
643
ADSL
Creating a card-profile for bonded ADSL2+ cards Create a new card profile for an ADSL2+ bonded card, in this case an ADSL Annex A/M card in slot 9. 1
Enter slots to view what cards are provisioned in which slot. zSH> slots Uplinks 2:*MALC FEGE RPR TDM (RUNNING) Cards 7: MALC XDSL 48 ANNEX A/M (NOT_PROV) 9: MALC ADSL 48 ANNEX A/M Bonded (NOT_PROV) 10: MALC ADSL 48 ANNEX A/M Bonded/with Packet Voice POTS (NOT_PROV) 13: MALC NTN/EFM GSHDSL Bonded/with NT (RUNNING) 16: MALC POTS 48/with Packet Voice (NOT_PROV)
2
Enter new card- profile shelf/slot/type to provision the MALC ADSL2+ Annex A/M card in slot 9.
zSH> new card-profile 1/9/5080 card-profile 1/9/5080 Please provide the following: [q]uit. sw-file-name: -----------> {malcadsl48anxabond.bin}: admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {true}: sw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}: hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {unknowntype}: card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: maxvpi-maxvci: ----------> {notapplicable}: card-init-string: -------> {}: wetting-current: --------> {disabled}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
3
Enter slots to verify the provisioning. zSH> slots Uplinks 2:*MALC FEGE RPR TDM (RUNNING) Cards 7: MALC XDSL 48 ANNEX A/M (NOT_PROV) 9: MALC ADSL 48 ANNEX A/M Bonded (RUNNING) 10: MALC ADSL 48 ANNEX A/M Bonded/with Packet Voice POTS (NOT_PROV)
644
MALC Hardware Installation Guide
Activating ADSL cards
13: MALC NTN/EFM GSHDSL Bonded/with NT (RUNNING) 16: MALC POTS 48/with Packet Voice (NOT_PROV)
Creating card-profiles for 48-port ADSL cards The 48 port ADSL cards with the conexant chip set use the same card type and software image: After specifying the image name, assign a card-line-type to indicate the type of card:
•
unknowntype (the default): ADSL only
•
adsl-pots: ADSL and TDM-based POTS
•
adsl-pots-pv: ADSL and packet-based POTS
•
adsl-splitter: ADSL+splitter The following example creates a card-profile for an MALC-ADSL-48A card in shelf 1, slot 12 and changes the VPI range to 0-7 and the VCI range to 0-127: zSH> card add 1/12/5036
or zSH> new card-profile 1/12/5036 shelf/slot/type sw-file-name: -----------> {} malcxdsl48anxam.bin admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {operational}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {false}: true sw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}: hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {unknowntype}: card-atm-configuration: -> {notapplicable} card-line-voltage: ------> {not-used}: maxvpi-maxvci: --------> {notapplicable}: vpi7-vci127 .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Creating an ADSL+POTS 48 card with TDM voice 1
View the type of card installed in the system: zSH> slots 1: MALC DS3 F (RUNNING) 2: MALC DS3 F (LOADING) 4: MALC XDSL 48 POTS (LOADING) 10: MALC MTAC FC (RUNNING)
MALC Hardware Installation Guide
645
ADSL
The POTS card in slot 4 is a MALC-ADSL+POTS-TDM-48-2S card, which supports TDM voice only. 2
Create a card-profile for the ADSL+POTS card and change the VPI range to 0-7 and the VCI range to 0-127:
zSh> card add 1/4/5036 linetype adsl-pots
or zSH> new card-profile 1/4/5036 slot 4 Please provide the following: [q]uit. sw-file-name: ---------> {}: malcxdsl48.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {0}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: adsl-pots indicates TDM voice only card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: maxvpi-maxvci: --------> {notapplicable}: vpi7-vci127 .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Creating an ADSL+POTS 48 card for packet voice 1
View the type of card installed in the system: zSH> slots 1: MALC DS3 F (RUNNING) 2: MALC DS3 F (LOADING) 6: MALC XDSL 48/with Packet Voice POTS 10: MALC MTAC FC (RUNNING)
The POTS card in slot 6 is a MALC-ADSL+POTS-48 TDM/PKT card, which supports packet voice only. 2
Create a card-profile for the ADSL+POTS card and change the VPI range to 0-7 and the VCI range to 0-127:
zSH> card add 1/6/5036 linetype adsl-pots-pv
or zSH> new card-profile 1/6/5036 slot 6 Please provide the following: [q]uit. sw-file-name: ---------> {}: malcxdsl48.bin admin-status: ---------> {operational}:
646
MALC Hardware Installation Guide
Activating ADSL cards
upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {0}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: adsl-pots-pv indicates packet voice card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: maxvpi-maxvci: --------> {notapplicable}: vpi7-vci127 .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Creating a 48-port ADSL Annex B card Create a card-profile for the MALC-ADSL-48B card and change the VPI range to 0-15 and the VCI range to 0-63: zSH> card add 1/4/5039
or zSH> new card-profile 1/4/5039 slot 4 Please provide the following: [q]uit. sw-file-name: ---------> {}: malcxdsl48anxb.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {0}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: maxvpi-maxvci: --------> {notapplicable}: vpi15-vci63 .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Creating a 48-port ADSL+Splitter card Create a card-profile for the ADSL+splitter and change the VPI range to 0-7 and the VCI range to 0-127: zSH> card add 1/4/5038 linetype adsl-splitter
MALC Hardware Installation Guide
647
ADSL
or zSH> new card-profile 1/4/5038 slot 4 Please provide the following: [q]uit. sw-file-name: ---------> {}: malcxdslspltanxa.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {0}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: adsl-splitter card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: maxvpi-maxvci: --------> {notapplicable}: vpi7-vci127 .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Creating a 48-port ADSL Annex A/M cards Create a card-profile for the MALC-ADSL-48A/M card and change the VPI range to 0-7 and the VCI range to 0-127: zSH> card add 1/5/5065
or zSH> new card-profile 1/5/5065 Please provide the following: [q]uit. sw-file-name: -----------> {malcxdsl48anxam.bin}: admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {false}: sw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}: hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {unknowntype}: card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: maxvpi-maxvci: --------> {notapplicable}: vpi7-vci127 .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
648
MALC Hardware Installation Guide
Activating ADSL cards
Creating card-profiles for MALC-ReachDSL-24 cards 1
The following example creates a card-profile for a MALCReachDSL-24 card in shelf 1, slot 16:
zSH> card add 1/16/5064
or zSH> new card-profile 1/16/5064 shelf/slot/type sw-file-name: -----------> {} malcreachdsl.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {0}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: card-atm-configuration: -> {notapplicable} card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
2
The following example creates a card-profile for a MALCReachDSL+SPLTR-24-2S card in shelf 1, slot 18:
zSH> card add 1/18/5075
or zSH> new card-profile 1/18/5075 shelf/slot/type Please provide the following: [q]uit. sw-file-name: -----------> {}: malcreachdsl.bin admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {true}: sw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}: hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {unknowntype}: card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: maxvpi-maxvci: ----------> {notapplicable}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
MALC Hardware Installation Guide
649
ADSL
Verifying the slot card installation After you save the card-profile record, the slot card in that slot resets and the begins downloading their software image from the flash card. This could take a few moments. When the card has finished loading, a log message similar to the following is displayed (if logging is enabled): zSH> Card in slot slot-number changed state to RUNNING
You can also use the slots command and specify the slot number of the card to view the state of the card. For example: zSH> slots 9 Type Card Version EEPROM Version Serial # CLEI Code Card-Profile ID Shelf Slot State Mode Heartbeat check Longest hbeat Fault reset Uptime
: : : : : : : : : : : : : :
MALC ADSL ANNEX A AC5 1 2 110011 No CLEI 1/15/5013 1 15 LOADING indicates the card is booting up FUNCTIONAL enabled 51 enabled 0 hours, 0 minutes
zSH> slots 9 Type Card Version EEPROM Version Serial # CLEI Code Card-Profile ID Shelf Slot State Mode Heartbeat check Longest hbeat Fault reset Uptime
: : : : : : : : : : : : : :
MALC ADSL ANNEX A AC5 1 2 110011 No CLEI 1/15/5013 1 15 RUNNING indicates the card is active FUNCTIONAL enabled 51 enabled 0 hours, 5 minutes
To view the status of all the cards, use the slots command without any arguments: zSH> slots 1: MALC DS3 (RUNNING) 9: MALC ADSL (RUNNING) 15: MALC MTAC (RUNNING)
650
MALC Hardware Installation Guide
Configuring ADSL interfaces
Configuring ADSL interfaces This section explains how to configure ADSL connections on the MALC. It contains the following sections:
•
Overview on page 651
•
Configuring ADSL S=1/2 on page 670
•
Configuring ADSL 2 and ADSL 2+ on page 676
•
Broadcom Phy-R™ parameters on page 686 Note: ADSL connections on the ADSL card and the ADSL + POTS cards are configured in the same way.
Overview The following table summarizes the commands required to configure ADSL interfaces on the MALC: Action
Command
Configure the type of ADSL interface. See Configuring the ADSL transmission and channel mode on page 653.
update adsl-profile shelf/slot/port
Configure the downstream interface. See Configuring an ADSL downstream interface on page 656.
update adsl-co-profile shelf/slot/ port
Configure the upstream interface. See Configuring an ADSL upstream interface on page 660
update adsl-cpe-profile shelf/slot/ port
Configuring ADSL S=1/2. See Configuring ADSL S=1/2 on page 670.
update adsl-profile shelf/slot/port
Configuring ADSL2 or ADSL2+. See Configuring ADSL 2 and ADSL 2+ on page 676.
update adsl-profile shelf/slot/port
where port is from: 1 to 48 (for 48 port ADSL cards)
update adsl-co-profile shelf/slot/ port
update adsl-co-profile shelf/slot/ port
Note: To enable dial pulse on POTS combo cards please refer to Enabling Dial Pulse on POTS and POTS combination cards on page 354.
MALC Hardware Installation Guide
651
ADSL
Configure ADSL2+ cards Each card installed in the system must have a card-profile. Each slot card has a designated type and software image that requires different settings in the card-profile.
Creating a card-profile for ADSL2+ cards Create a new card profile for an ADSL2+ card, in this case an ADSL Annex B card in slot 9. 1
Enter slots to view what cards are provisioned in which slot. zSH> slots Uplinks 2:*MALC FEGE RPR TDM (RUNNING) Cards 7: MALC XDSL 48 ANNEX A/M (NOT_PROV) 8: MALC ADSL 48 ANNEX A/M Bonded (RUNNING) 9: MALC ADSL 48 ANNEX B Bonded (NOT_PROV) 10: MALC ADSL 48 ANNEX A/M Bonded/with Packet Voice POTS (NOT_PROV) 13: MALC NTN/EFM GSHDSL Bonded/with NT (RUNNING) 16: MALC POTS 48/with Packet Voice (NOT_PROV)
2
Enter new card- profile shelf/slot/type to provision the MALC ADSL2+ Annex B card in slot 9.
zSH> new card-profile 1/9/5081 card-profile 1/9/5081 Please provide the following: [q]uit. sw-file-name: -----------> {malcadsl48anxbbond.bin}: admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {true}: sw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}: hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {unknowntype}: card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: maxvpi-maxvci: ----------> {notapplicable}: card-init-string: -------> {}: wetting-current: --------> {disabled}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
3
652
MALC Hardware Installation Guide
Enter slots to verify the provisioning.
Configuring ADSL interfaces
zSH> slots Uplinks 2:*MALC FEGE RPR TDM (RUNNING) Cards 7: MALC XDSL 48 ANNEX A/M (NOT_PROV) 8: MALC ADSL 48 ANNEX A/M Bonded (RUNNING) 9: MALC ADSL 48 ANNEX B Bonded (RUNNING) 10: MALC ADSL 48 ANNEX A/M Bonded/with Packet Voice POTS (NOT_PROV) 13: MALC NTN/EFM GSHDSL Bonded/with NT (RUNNING) 16: MALC POTS 48/with Packet Voice (NOT_PROV)
Configuring the ADSL transmission and channel mode Configure the ADSL transmission and channel mode in the adsl-profile. The following parameters are supported in this profile: Parameter
Description
adslTrellisModeEnabled
Enables or disables trellis mode.
adslTransmissionMode
ADSL transmission mode. Supported values: Values: adsl2mode The modem negotiates rates up to G.992.3 and G.992.4 ADSL2. ADSL2plusmode The modem negotiates rates up to G.992.5
(ADSL2+). autonegotiatemode : automatically negotiates all supported transmission modes. The modem uses the G.hs protocol to negotiate a transmission mode in this order: T1.413, then G.dmt, then G.lite. fullratemode : automatically negotiates full rate modes (G.dmt and T1 mode). G.dmt has priority over T1 mode. glitemode : G.lite. Supports only interleave mode. t1mode : Full rate T1 gdmtmode : G.dmt ghsmode : the modem negotiates only G.dmt and G.lite modes. G.dmt has priority over G.lite. reachonlymode the modem negotiates only reach DSL mode. Default: automegotiatemode adslChannelMode
Specifies the channelization of the ADSL line. Supported values: Values: fastonly No impulse noise protection, but lowest possible latency. Recommended only where lowest possible latency is required (for example, gaming) interleavedonly Better impulse noise protection with higher latency. Recommended for all voice, video, and/or data deployments. Default: fastonly
MALC Hardware Installation Guide
653
ADSL
Parameter
Description
adslMaxDownstreamToneIndex
Specifies the maximum downstream active tone. Values: 32 (128KHz) to 511 (2044KHz) Each value represents 4KHz. Default: 255
• adslMinDownstreamToneIndex
Changing this value causes the DSL modems to retrain.
Specifies the minimum downstream active tone. Values: 32 (128KHz) to 255 (1020KHz) Each value represents 4KHz. Default: 511
• • adslMaxUpstreamToneIndex
Changing this value causes the DSL modems to retrain. For Annex B and Annex M configurations, this value should be set to 64.
Specifies the maximum upstream active tone. Values: 6 (24KHz) to 30 (120KHz) Each value represents 4KHz. Default: 3‘
• • adslMinUpstreamToneIndex
Changing this value causes the DSL modems to retrain. For Annex B and Annex M configurations, this value should be set to 63.
Specifies the minimum upstream active tone. Values: 6 (24KHz) to 30 (120KHz) Each value represents 4KHz. Default: 6
• adslPotsBypassRelayMaxDuration
Changing this value causes the DSL modems to retrain.
Not currently used. The maximum duration in seconds that an ADSL POTS low-pass filter bypass relay will remain active (closed). The relay will automatically return a line back to normal (open) mode when this timer has expired. Values: 1 to 300 Default: 60 Only valid for ADSL-SPLTR-32 cards.
adslLineDMTConfMode
Specifies the type of Discrete Multi-Tone used (echocancel or freqdivmux). Default: freqdivmux
654
MALC Hardware Installation Guide
Configuring ADSL interfaces
Parameter
Description
adslPotsBypassRelayMaxDuration
Specifies the manximum delay for the POTS bypass. Default: 60
annexMModeEnabled
Specifies whether annex M mode is enabled. This parameter can only be set to true when the adslTransmissionMode parameter is set to autonegotiate, adsl2mode, or adsl2plusmode. Defualt: false The parameter is displayed for all ADSL cards, but only valid for cards which support
The following example accepts the defaults, which are appropriate for most applications: zSH> update adsl-profile 1/12/1 adslLineConfProfile: ------------> {0000000091} adslAlarmConfProfile: -----------> {0000000091} adslTrellisModeEnabled: ---------> {true} adslNTRModeEnabled: -------------> {false} adslTransmissionMode: -----------> {autonegotiatemode} adslChannelMode: ----------------> {fastonly} adslMaxDownstreamToneIndex: -----> {511} adslMinDownstreamToneIndex: -----> {32} adslMaxUpstreamToneIndex: -------> {31} adslMinUpstreamToneIndex: -------> {6} adslPotsBypassRelayMaxDuration: -> {60} adslLineDMTConfMode: ------------> {freqdivmux} adslAnnexMModeEnabled: ----------> {false} .................... Save new record? [s]ave, [c]hange or [q]uit: s Record updated.
Configuring ADSL tone ranges The MALC supports setting the active upstream and downstream tone ranges for ADSL modems. Although this is not typically required, changing the range of tones can affect the maximum throughput of the channel as well as providing isolation from certain interference. The following parameters in the adsl-profile specify the range of active tones for the DSL modem: –
AdslMaxDownstreamToneIndex
–
AdslMinDownstreamToneIndex
–
AdslMaxUpstreamToneIndex
–
AdslMinUpstreamToneIndex
For POTS lines, the valid frequency range in the downstream direction is 128 KHz to 1020 KHz. In the upstream direction valid frequency range is 24 KHz to 120 KHz.
MALC Hardware Installation Guide
655
ADSL
ADSL occupies from about 24KHz to 1100KHz. (The theoretical limit is 15 bits/Hz.) Note: Changing of any of these parameters will cause the modem to retrain.
Configuring an ADSL downstream interface Configure the ADSL downstream interface in the adsl-co-profile. The following parameters are supported in this profile: Parameter
Description
rateMode
The transmit rate adaptation configured on this modem. Supported values: fixed: The rate is negotiated at startup and remains fixed. Modem speed is determined by the fastMaxTxRate or interleaveMaxTxRate parameters. adaptatstartup: The rate is negotiated at startup and remains fixed. Modem speed is determined by the fastMaxTxRate or interleaveMaxTxRate parameters. If the line is able to support a higher rate, the rate above the minimum is assigned to the available channel (either fast or interleave). adaptatruntime: The rate is negotiated dynamically and can vary between the maximum and minimum configured rates. If the line conditions change during runtime, the line speed is adjusted. Recommended for video. Default: adaptatruntime
rateChanRatio
Configured allocation ratio of excess transmit bandwidth between fast and interleaved channels. Default: 50
targetSnrMgn
Target signal to noise margin (in tenths of dBs). This is the noise margin the modem must achieve with a BER of 10-7 or better to successfully complete initialization. Suggested values are 6 dB for data-only or data-voice service and 10 dB for video service with better protection against noise which causes tiling. Default: 60
maxSnrMgn
Maximum acceptable signal/noise margin (in tenths of dBs). If the noise margin rises above this the modem attempts to reduce its power output to optimize its operation. Reduces crosstalk into other ADSL circuits by not transmitting at an unnecessarily high level. For video, suggested values are 31 for both upstream and downstream. Default: 310
minSnrMgn
Minimum acceptable signal to noise margin (in tenths of dBs). If the noise margin falls below this level, the modem attempts to increase its power output. If that is not possible the modem will attempt to re-initialize or shut down. For video, use 2 downstream and 0 upstream and adjust downstream rate proactively just before video degrades. default: 0
656
MALC Hardware Installation Guide
Configuring ADSL interfaces
Parameter
Description
downshiftSnrMgn
Configured Signal/Noise Margin for rate downshift. If the noise margin falls below this level, the modem should attempt to decrease its transmit rate. default: 0
upshiftSnrMgn
Configured Signal/Noise Margin for rate upshift. If the noise margin rises above this level, the modem should attempt to increase its transmit rate. default: 0
minUpshiftTime
Minimum time that the current margin is above UpshiftSnrMgn before an upshift occurs. default: 0
minDownshiftTime
Minimum time that the current margin is below DownshiftSnrMgn before a downshift occurs. default: 0
fastMinTxRate
Minimum transmit rate (in bps) for channels configured for fast transmission mode. For a CO interface, the range is 32Kbps to 8160Kbps (1536Kbps for G.Lite). Default: 32 Kbps
interleaveMinTxRate
Minimum transmit rate (in bps) for channels configured for interleaved transmission mode. For a CO interface, the range is 32Kbps to 8160Kbps (1536Kbps for G.Lite). Default: 32 Kbps
fastMaxTxRate
Maximum transmit rate (in bps) for channels configured for fast transmission mode. For a CO interface, the range is 32Kbps to 8160Kbps (1536Kbps for G.Lite). Default: 32 Kbps
MALC Hardware Installation Guide
657
ADSL
Parameter
Description
maxInterleaveDelay
Maximum interleave delay for this channel. Interleave delay applies only to the interleave channel and defines the mapping (relative spacing) between subsequent input bytes at the interleaver input and their placement in the bit stream at the interleaver output. Larger numbers provide greater separation between consecutive input bytes in the output bit stream allowing for improved impulse noise immunity, but at the expense of payload latency. For video, to maximize protection of downstream signal (where impulse problems occur), minimize round-trip latency by minimizing upstream delay use 1 ms upstream and 16 ms downstream. Values: 0 0.5 ms 1 1 ms 2 2 ms 4 4 ms 8 8 ms 16 16 ms 32 32 ms 63 63 ms Default: 63 ms
interleaveMaxTxRate
Maximum transmit rate (in bps) for channels configured for interleaved transmission mode. For a CO interface, the range is 32Kbps to 8160Kbps (1536Kbps for G.Lite). Default: 32 Mbps
thresh15MinLofs
The number of Loss of Frame Seconds encountered by an ADSL interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send an adslAtucPerfLofsThreshTrap. Default: 0
thresh15MinLoss
The number of Loss of Signal Seconds ecountered by an ADSL interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send an adslAtucPerfLossThreshTrap. Default: 0
thresh15MinLols
The number of Loss of Link Seconds encountered by an ADSL interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send an adslAtucPerfLolsThreshTrap. Default: 0
thresh15MinLprs
Not currently used. The number of Loss of Power Seconds encountered by an ADSL interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send an adslAtucPerfLprsThreshTrap. Default: 0
658
MALC Hardware Installation Guide
Configuring ADSL interfaces
Parameter
Description
thresh15MinESs
The number of Errored Seconds encountered by an ADSL interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send an adslAtucPerfESsThreshTrap. Default: 0
threshFastRateUp
Not currently used. Applies to `Fast' channels only. Configured change in rate causing an adslAtucRateChangeTrap. Default: 0
threshInterleaveRateUp
Not currently used. For `Interleave' channels only. Configured change in rate causing an adslAtucRateChangeTrap. Default: 0
threshFastRateDown
Not currently used. For `Fast' channels only. Configured change in rate causing an adslAtucRateChangeTrap. Default: 0
threshInterleaveRateDown
Not currently used. For `Interleave' channels only. Configured change in rate causing an adslAtucRateChangeTrap. Default: 0
initFailureTrapEnable
Not currently used. Enables and disables the InitFailureTrap.This trap controls whether line up or line down traps are sent while the system is booting up. Default: disabled
reachextendedAdsl2
Enables and disables extended reach. Default: enabled
minTxThresholdRateAlarm
Enables the CO (downstream) transmission rate threshold value. If the rate falls below this value, the device sends a trap and an alarm. Default: 0
Note: If the interface is configured for G.lite, change the interleaveMaxTxRate parameter to a valid value for G.lite (1536 Kbps or less). The following example configures an ADSL downstream interface. Note that you can accept most of the default values. zSH> update adsl-co-profile 1/12/1 Please provide the following: [q]uit. rateMode: -----------------> {adaptatruntime} rateChanRatio: ------------> {50} targetSnrMgn: -------------> {60} maxSnrMgn: ----------------> {310} minSnrMgn: ----------------> {0} downshiftSnrMgn: ----------> {0} upshiftSnrMgn: ------------> {0} minUpshiftTime: -----------> {0} minDownshiftTime: ---------> {0}
MALC Hardware Installation Guide
659
ADSL
fastMinTxRate: ------------> {32000} interleaveMinTxRate: ------> {32000} fastMaxTxRate: ------------> {32736000} maxInterleaveDelay: -------> {63} interleaveMaxTxRate: ------> {32736000} thresh15MinLofs: ----------> {0} thresh15MinLoss: ----------> {0} thresh15MinLols: ----------> {0} thresh15MinLprs: ----------> {0} thresh15MinESs: -----------> {0} threshFastRateUp: ---------> {0} threshInterleaveRateUp: ---> {0} threshFastRateDown: -------> {0} threshInterleaveRateDown: -> {0} initFailureTrapEnable: ----> {disable} reachExtendedAdsl2: -------> {enable} minTxThresholdRateAlarm: --> {0} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Configuring an ADSL upstream interface Note: If the interface is configured for G.lite, change the interleaveMaxTxRate parameter to a valid value of 512 Kbps or less). If the interface is configured for Annex M, ensure the fastMaxTxRate and interleaveMaxTxRate parameters to valid values. Configure the ADSL upstream interface in the adsl-cpe-profile. The supported parameters in the upstream profile are identical to the CO profile, with the following exceptions:
Parameter
Description
rateMode
The transmit rate adaptation configured on this modem. Supported values: fixed: The rate is negotiated at startup and remains fixed. Modem speed is determined by the fastMaxTxRate or interleaveMaxTxRate parameters. adaptatstartup: The rate is negotiated at startup and remains fixed. Modem speed is determined by the fastMaxTxRate or interleaveMaxTxRate parameters. If the line is able to support a higher rate, the rate above the minimum is assigned to the available channel (either fast or interleave). adaptatruntime: The rate is negotiated dynamically and can vary between the maximum and minimum configured rates. If the line conditions change during runtime, the line speed is adjusted. Default: adaptatruntime
rateChanRatio
Configured allocation ratio of excess transmit bandwidth between fast and interleaved channels. Default: 50
660
MALC Hardware Installation Guide
Configuring ADSL interfaces
Parameter
Description
targetSnrMgn
Target signal to noise margin (in tenths of dBs). This is the noise margin the modem must achieve with a BER of 10-7 or better to successfully complete initialization. Default: 60
maxSnrMgn
Maximum acceptable signal/noise margin (in tenths of dBs). If the noise margin rises above this the modem attempts to reduce its power output to optimize its operation. Default: 310
minSnrMgn
Configured Signal/Noise Margin for rate downshift. If the noise margin falls below this level, the modem should attempt to decrease its transmit rate. default: 0
downshiftSnrMgn
Configured Signal/Noise Margin for rate upshift. If the noise margin rises above this level, the modem should attempt to increase its transmit rate. default: 0
upshiftSnrMgn
Minimum time that the current margin is above UpshiftSnrMgn before an upshift occurs. default: 0
minUpshiftSnrMgn
Minimum time that the current margin is below DownshiftSnrMgn before a downshift occurs. default: 0
minDownshiftSnrMgn
Configured Signal/Noise Margin for rate downshift. If the noise margin falls below this level, the modem should attempt to decrease its transmit rate. default: 0
fastMinTxRate
Minimum transmit rate (in bps) for channels configured for fast transmission mode. For a CPE interface, the range is 32 Kbps to 896 Kbps (512 Kbps for G.lite). Default: 32 Kbps
interleaveMinTxRate
Minimum transmit rate (in bps) for channels configured for interleaved transmission mode. For a CPE interface, the range is 32 Kbps to 896 Kbps (512 Kbps for G.lite). Default: 32 Kbps
fastMaxTxRate
Maximum transmit rate (in bps) for channels configured for fast transmission mode. For a CPE interface, the range is 32 Kbps to 1024 Kbps (512 Kbps for G.lite). Default: 1024 Kbps
interleaveMaxTxRate
Maximum transmit rate (in bps) for channels configured for interleaved transmission mode. For a CPE interface, the range is 32 Kbps to 1536 Kbps (512 Kbps for G.lite). Default: 1536 Kbps
MALC Hardware Installation Guide
661
ADSL
Parameter
Description
minTxThresholdRateAlarm
Enables the CPE (upstream) transmission rate threshold value. If the rate falls below this value, the device sends a trap and an alarm. Default: 16
thresh15MinLofs
The number of Loss of Frame Seconds encountered by an ADSL interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send an adslAtucPerfLofsThreshTrap. Default: 0
thresh15MinLoss
The number of Loss of Signal Seconds ecountered by an ADSL interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send an adslAtucPerfLossThreshTrap. Default: 0
thresh15MinLprs
The number of Loss of Power Seconds encountered by an ADSL interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send an adslAtucPerfLprsThreshTrap. Default: 0
thresh15MinESs
The number of Errored Seconds encountered by an ADSL interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send an adslAtucPerfESsThreshTrap. Default: 0
threshFastRateUp
Applies to `Fast' channels only. Configured change in rate causing an adslAtucRateChangeTrap. Default: 0
threshInterleaveRateUp
For `Interleave' channels only. Configured change in rate causing an adslAtucRateChangeTrap. Default: 0
threshFastRateDown
For `Fast' channels only. Configured change in rate causing an adslAtucRateChangeTrap. Default: 0
threshInterleaveRateDown
For `Interleave' channels only. Configured change in rate causing an adslAtucRateChangeTrap. Default: 0
minTxThresholdRateAlarm
Enables the CO (downstream) transmission rate threshold value. If the rate falls below this value, the device sends a trap and an alarm. Default: 0
The following example configures an ADSL upstream interface. Note that you can accept most of the default values. zSH> update adsl-cpe-profile 1/12/1 Please provide the following: [q]uit. rateMode: -----------------> {adaptatruntime} rateChanRatio: ------------> {50}
662
MALC Hardware Installation Guide
Configuring ADSL interfaces
targetSnrMgn: -------------> {60} maxSnrMgn: ----------------> {310} minSnrMgn: ----------------> {0} downshiftSnrMgn: ----------> {30} upshiftSnrMgn: ------------> {90} minUpshiftSnrMgn: ---------> {60} minDownshiftSnrMgn: -------> {60} fastMinTxRate: ------------> {32000} interleaveMinTxRate: ------> {32000} fastMaxTxRate: ------------> {1024000} interleaveMaxTxRate: ------> {1536000} maxInterleaveDelay: -------> {16} thresh15MinLofs: ----------> {0} thresh15MinLoss: ----------> {0} thresh15MinLprs: ----------> {0} thresh15MinESs: -----------> {0} threshFastRateUp: ---------> {0} threshInterleaveRateUp: ---> {0} threshFastRateDown: -------> {0} threshInterleaveRateDown: -> {0} minTxThresholdRateAlarm: --> {0} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Verifying the interface Use the dslstat command to displays the status of the interface: zSH> dslstat 1-12-1-0/adsl General Stats: ------------AdminStatus..................................UP Line uptime(DD:HH:MM:SS)....................0:02:27:52 DslUpLineRate (bitsPerSec)...................512000 DslDownLineRate (bitsPerSec).................8064000 DslMaxAttainableUpLineRate (bitsPerSec)......565333 DslMaxAttainableDownLineRate (bitsPerSec)....856000 Out Octets...................................286571 Out Discards.................................0 Out Errors...................................0 In Octets....................................286571 In Discards..................................0 In Errors....................................0 ATM OCD Count................................0 ATM NCD Count................................0 ATM HEC Count................................0 ATM far-end OCD Count........................0 ATM far-end NCD Count........................0 ATM far-end HEC Count........................0 ADSL Physical Stats: -----------------Actual Transmission connection standard......G.dmt
MALC Hardware Installation Guide
663
ADSL
AdslAtucCurrLineSnrMgn (tenths dB)...........310 AdslAtucCurrLineAtn (tenths dB)..............135 AdslAtucCurrOutputPwr (tenths dB)............70 AdslAturCurrLineSnrMgn (tenths dB)...........90 AdslAturCurrLineAtn (tenths dB)..............135 AdslAturCurrOutputPwr (tenths dB)............103 LOFS.........................................0 LOLS.........................................0 LOSS.........................................0 ESS..........................................0 Inits........................................1 Adsl connects................................1 Adsl disconnects.............................5407 near-end statistics: ------------------blocks received..............................147087 errored blocks received......................0 CRC errors on interleaved buffer.............0 CRC errors on fast buffer....................0 FEC corrected errors on interleaved buffer...0 FEC corrected errors on fast buffer..........0 background errored blocks received...........0 non-SES blocks received......................0 Severely Errored Seconds.....................0 Unavailable Seconds..........................59 Loss of Signal Seconds.......................0 Seconds with one/more FECs...................0 Seconds declared as high BER.................0 far-end statistics: ------------------blocks received..............................147205 errored blocks received......................1 CRC errors on interleaved buffer.............0 CRC errors on fast buffer....................1 FEC corrected errors on interleaved buffer...0 FEC corrected errors on fast buffer..........0 background errored blocks received...........0 non-SES blocks received......................0 Severely Errored Seconds.....................0 Unavailable Seconds..........................0 Loss of Signal Seconds.......................0 Seconds with one/more FECs...................0 Loss of Power (dying gasps)..................0 Seconds declared as high BER.................0 Fast retrains................................0 Fast retrain failures........................0
664
MALC Hardware Installation Guide
Configuring ADSL interfaces
Table 55: DSL statistics General Stats:
Description
AdminStatus
Administrative status of the port: Values: Up Interface is ready to pass packets. Down Interface is unable to pass packets. Testing Interface is in a special testing state and is unable to pass packets.
Line uptime(DD:HH:MM:SS)
How long the interface has been up in dd hh mm (day, hour, minute, second) format.
DslUpLineRate (bitsPerSec)
Displays the DSL upstream (customer premise > central office) line rate on this interface.
DslDownLineRate (bitsPerSec)
Displays the DSL downstream (central office > customer premise) line rate on this interface.
DslMaxAttainableUpLineRate (bitsPerSec)
Displays the maximum line rate that can be supported on this line in the upstream direction.
DslMaxAttainableDownLine Rate (bitsPerSec)
Displays the maximum line rate that can be supported on this line in the downstream direction.
Out Octets
Number of transmitted octets.
Out Discards
Number of transmission discards.
Out Errors
Number of transmission errors.
In Octets
Number of received octets.
In Discards
Number of received discards.
In Errors
Number of receive errors.
ATM OCD Count
The number Out of Cell Delineation (OCD) events. An Out of Cell Delineation event is defined as seven consecutive ATM cells with Header Error Control (HEC) violations. A high number of these events may indicate a problem with the ATM TC sublayer.
ATM NCD Count
The number of far end No Cell Delineation (NCD) events on the far end.
ATM HEC Count
Number of corrected HEC cells.
ATM far-end OCD Count
The number Out of Cell Delineation (OCD) events. An Out of Cell Delineation event is defined as seven consecutive ATM cells with Header Error Control (HEC) violations. A high number of these events may indicate a problem with the ATM TC sublayer.
ATM far-end NCD Count
The number of far end No Cell Delineation (NCD) events on the far end.
ATM far-end HEC Count
Number of corrected HEC cells at the far-end.
ADSL Physical Stats:
MALC Hardware Installation Guide
665
ADSL
Table 55: DSL statistics General Stats:
Description
Actual Transmission connection standard
Displays the maximum line rate that can be supported on this line in the downstream direction. Values: GHS GDMT T1 GLite Full Rate AutoNegotiate
AdslAtucCurrLineSnrMgn (tenths dB)
SNR Margin is the maximum increase in dB of the noise power received at the ATU-C on upstream direction), such that the BER requirements are met for all bearer channels received at the ATU. It ranges from 640 to 630 units of 0.1 dB (Physical values are -64 to 63 dB).
AdslAtucCurrLineAtn (tenths dB)
Measured difference in the total power transmitted by the peer ATU-C and the total power received by this ATU.
AdslAtucCurrOutputPwr (tenths dB)
Actual Aggregate Transmit Power from the ATU-C on upstream direction at the instant of measurement. It ranges from -310 to 310 units of 0.1 dB (Physical values are -31 to 31 dBm).
AdslAturCurrLineSnrMgn (tenths dB)
SNR Margin is the maximum increase in dB of the noise power received at the ATU (ATU-R on downstream direction , such that the BER requirements are met for all bearer channels received at the ATU. It ranges from 640 to 630 units of 0.1 dB (Physical values are -64 to 63 dB).
AdslAturCurrLineAtn (tenths dB)
Measured difference in the total power transmitted by he peer ATU-R and the total power received by this ATU.
AdslAturCurrOutputPwr (tenths dB)
Actual Aggregate Transmit Power from the ATU (ATU-R on downstream direction at the instant of measurement. It ranges from -310 to 310 units of 0.1 dB (Physical values are -31 to 31 dBm).
LOFS
Number of Loss of Frame Seconds.
LOLS
Number of Loss of Line Seconds.
LOSS
Number of Loss of Signal Seconds.
ESS
Number of errored seconds (the number of one-second intervals containing one or more CRC anomalies or one or more Los or Sef defects) that has been reported in the current 15-minute interval.
Inits
Number of line initialization attempts, including both successful and failed attempts.
Adsl connects
Number of successful connects at the near end since the agent reset.
Adsl disconnects
Number of disconnects at the near end since the agent reset.
near-end statistics:
666
MALC Hardware Installation Guide
Configuring ADSL interfaces
Table 55: DSL statistics General Stats:
Description
blocks received
Number of received blocks at the near end. This statistic is not incremented while there is a UAS or SES error on the interface.
errored blocks received
Number of background errored blocks at the near end. A background block error is an errored block that does not occur as part of a SES. A block refers to Reed Solomon error correction blocks. They are typically 255 bytes of data, and may span several symbols of data, regardless of how may or what parts of ATM cells they represent. This statistic is not incremented while there is a UAS or SES error on the interface.
CRC errors on interleaved buffer
Number of cyclic redundancy check (CRC) errors on interleaved buffer at the near end. This statistic is not incremented while there is a UAS or SES error on the interface.
CRC errors on fast buffer
Number of cyclic redundancy check (CRC) errors on fast buffer at the near end. This statistic is not incremented while there is a UAS or SES error on the interface.
FEC corrected errors on interleaved buffer
Number of forward error corrections (FECs) on interleaved buffer at the near end. Forward error correction (Reed Solomon) is applied to the transported data. This process obtains coding gain, resulting in the link requiring lower signal-to-noise rations (SNRs) for a given data and error rate. This process allows an increase in the data rate under given loop conditions. In addition, interleaving can be applied on top of error correction to obtain a higher degree of protection against error bursts or temporary loss of the data signal. The interleave distributes the data errors over multiple symbols. This action is intended to reduce the number of errors per Reed Solomon codeword to a number within the correction capability of the code. This statistic is not incremented while there is a UAS or SES error on the interface.
FEC corrected errors on fast buffer
Number of forward error corrections (FECs) on fast buffer at the near end. This statistic is not incremented while there is a UAS or SES error on the interface. Fast Buffer—Each ADSL frame consists of two parts, one from each of two buffers: the fast buffer and the interleaved buffer. The fast buffer, in addition to user data, may contain CRC error checking bits, and forward error correcting bits. The fast byte in frame 1, 34, and 35 contain indicator bits used for administrative functions. The interleaved buffer contains purely data.
background errored blocks received
Background errored blocks at near end. A background block error is an errored block that does not occur as part of a SES. A block refers to Reed Solomon error correction blocks. They are typically 255 bytes of data, and may span several symbols of data, regardless of how may or what parts of ATM cells they represent. This statistic is not incremented while there is a UAS or SES error on the interface.
non-SES blocks received
Number of non severely errored seconds (SES) blocks received at the near end.
MALC Hardware Installation Guide
667
ADSL
Table 55: DSL statistics General Stats:
Description
Severely Errored Seconds
Number of severely errored seconds (SES) at the near end. This is the number of 1-second intervals with any of the following error conditions: 18 or more CRC-8 anomalies (over over all received channels). If a CRC occurs over multiple bearer channels, then each related CRC-8 anomaly is counted only once for the whole set of bearer channels over which the CRC is applied. one or more LOS defects one or more SEF defects one or more LPR defects
Unavailable Seconds
Number of unavailable seconds (UAS) at the near end. This is the number of 1-second intervals for which the ADSL line is unavailable. The ADSL line becomes unavailable after the onset of 10 consecutive severely errored seconds (SESs). Note that the 10 SESs are included in unavailable time. The ADSL line becomes available after 10 consecutive seconds with no SESs. Note that the 10 seconds with no SESs are excluded from unavailable time.
Loss of Signal Seconds
Retrieved via OAM. Count of 1-second intervals containing one or more near end loss of signal (LOS) defects. An LOS failure is declared for either of the following reasons: after 2.5 ± 0.5 seconds of continuos LOS defects if LOS defect is present when a LOF occurs. A line circuit reports a LOS defect when the received power has fallen below the threshold. The threshold is set at 6 dB below the reference power. A LOS failure is cleared after 10 ± 0.5 seconds of no LOS defects. The most common cause for this fault is that the customer premises equipment (CPE) has been turned off. Supported for ADSL2/ADSL2plus only. This statistic is not incremented while there is a UAS or SES error on the interface.
Seconds with one/more FECs
Number of seconds with one or more forward error corrections (FECs) at the near end. These blocks are passed on as good data. This statistic is not incremented while there is a UAS or SES error on the interface.
Seconds declared as high BER
Number of seconds with high Bit Error Rate (BER).
far-end statistics: blocks received
Number of received blocks at the far end. This statistic is not incremented while there is a UAS or SES error on the interface.
errored blocks received
Number of background errored blocks at the far end. A background block error is an errored block that does not occur as part of a SES. A block refers to Reed Solomon error correction blocks. They are typically 255 bytes of data, and may span several symbols of data, regardless of how may or what parts of ATM cells they represent. This statistic is not incremented while there is a UAS or SES error on the interface.
668
MALC Hardware Installation Guide
Configuring ADSL interfaces
Table 55: DSL statistics General Stats:
Description
CRC errors on interleaved buffer
Number of cyclic redundancy check (CRC) errors on interleaved buffer at the far end.
CRC errors on fast buffer
Number of cyclic redundancy check (CRC) errors on fast buffer at the far end.
This statistic is not incremented while there is a UAS or SES error on the interface.
This statistic is not incremented while there is a UAS or SES error on the interface. FEC corrected errors on interleaved buffer
Number of forward error corrections (FECs) on interleaved buffer at the far end. Forward error correction (Reed Solomon) is applied to the transported data. This process obtains coding gain, resulting in the link requiring lower signal-to-noise rations (SNRs) for a given data rate and error rate. This process allows an increase in the data rate under given loop conditions. In addition, interleaving can be applied on top of error correction to obtain a higher degree of protection against error bursts or temporary loss of the data signal. The interleave distributes the data errors over multiple symbols. This action is intended to reduce the number of errors per Reed Solomon codeword to a number within the correction capability of the code. This statistic is not incremented while there is a UAS or SES error on the interface.
FEC corrected errors on fast buffer
Number of forward error corrections (FECs) on fast buffer at the far end. This statistic is not incremented while there is a UAS or SES error on the interface. Fast Buffer—Each ADSL frame consists of two parts, one from each of two buffers: the fast buffer and the interleaved buffer. The fast buffer, in addition to user data, may contain CRC error checking bits, and forward error correcting bits. The fast byte in frame 1, 34, and 35 contain indicator bits used for administrative functions. The interleaved buffer contains purely data.
background errored blocks received
Number of background errored blocks at the far end. A background block error is an errored block that does not occur as part of a SES. A block refers to Reed Solomon error correction blocks. They are typically 255 bytes of data, and may span several symbols of data, regardless of how may or what parts of ATM cells they represent. This statistic is not incremented while there is a UAS or SES error on the interface.
non-SES blocks received
Number of non severely errored seconds (SES) blocks received at the far end.
Severely Errored Seconds
Number of errored seconds (the number of one-second intervals containing one or more cyclic redundancy check [CRC] anomalies or one or more loss of signal [LOS] defects) that has been reported in the current 15-minute interval. This statistic is not incremented while there is a UAS or SES error on the interface.
Unavailable Seconds
Number of unavailable seconds (UAS) at the far end. This is the number of 1-second intervals for which the ADSL line is unavailable. The ADSL line becomes unavailable after the onset of 10 consecutive severely errored seconds (SESs). Note that the 10 SESs are included in unavailable time. The ADSL line becomes available after 10 consecutive seconds with no SESs. Note that the 10 seconds with no SESs are excluded from unavailable time.
Loss of Signal Seconds
Loss of signal seconds at the near end.
MALC Hardware Installation Guide
669
ADSL
Table 55: DSL statistics General Stats:
Description
Seconds with one/more FECs
Number of seconds with one or more forward error corrections (FECs) at the far end. These blocks are passed on as good data. This statistic is not incremented while there is a UAS or SES error on the interface.
Loss of Power (dying gasps)
The ATU-R (remote) device sends a dying-gasp message before it goes down so that the ATU-C (central office) device can differentiate between line down and ATU-R device down events.
Seconds declared as high BER
Seconds declared as high BER by the far end.
Fast retrains
Number of fast retrains.
Fast retrain failures
Number of fast retrain failures.
Configuring ADSL S=1/2 This section describes S=1/2 mode transmission on ADSL line cards. The ADSL S=1/2 specification, as defined in the ITU standard G.992.2, is a transmission mode that supports downstream data rates up to 12 Mbps at distances of 6,000 feet or less. The following ADSL 32-port and cards support S=1/2 mode transmission:
•
MALC-ADSL-32A
•
ADSL-48
Overview There are two ADSL S=1/2 configurations:
•
Configuring the ADSL transmission and channel mode on page 653
•
Configuring S=1/2 transmission mode for interleaved mode on page 674
Modify the following parameters to enable S=1/2 transmission. Configure interleaved channels in the adsl-profile: Table 56: ADSL-Profile
670
adsl-profile
Description Both ATU-C and ATU-R
MALC Support
Range supported
Default
adslLineConfProfile
Read-Only
PARTIAL
260 only
260
adslAlarmConfProfile
Read-Only
PARTIAL
261 only
260
adslTrellisModeEnabled
Enable/Disable Trellis Mode
Yes
Enable=TRUE/ Disable=FALSE
TRUE
adslNTRModeEnabled
Network Timing Recovery
Not Used
Enable=TRUE/ Disable=FALSE
TRUE
MALC Hardware Installation Guide
Configuring ADSL interfaces
Table 56: ADSL-Profile (Continued) adsl-profile
Description Both ATU-C and ATU-R
MALC Support
Range supported
Default
adslTransmissionMode
Sets Transmission Mode
Yes
Yes
Yes
adslChannelMode
Specifies Channelization (Fast/Interleave)
Per line (not per channel)
fastonly interleavedonly
fastonly
adslMaxDownstreamToneIndex
Maximum Downstream Active Tones
Yes
6 to 1023
511
adslMinDownstreamToneIndex
Minimum Downstream Active Tones
Yes
6 to 1023
32
adslMaxUpstreamToneIndex
Maximum Upstream Active Tones
Yes
1 to 63
31
adslMinUpstreamToneIndex
Minimum Upstream Active Tones
Yes
1 to 63
6
adslPotsBypassRelayMaxDuration
Not Used
Not Used
1 to 300
Not Used
adslLineDMTConfMode
DMT Mode - Echo Cancel or Freq Div Mux
Freq Div Mux Only
Freq Div Mux Only
Freq Div Mux
adslAnnexMModeEnabled
Enable/Disable Annex-M
Yes
Enable=TRUE/ Disable=FALSE
FALSE
Set the maximum transmit rate in the adsl-co-profile: Table 57: ADSL-CO-Profile adsl-co-profile
ATU-C
SLMS Supported
SLMS Range supported
SLMS Default
rateMode
Transmit Rate Adaptation
Yes
AdaptAtRuntime Only
AdaptAtRuntime
rateChanRatio
Ratio of avail versus min rates
Defaulted
0 to 100
Defaulted
targetSnrMgn
Target Signal to Noise Ratio (SNR)
Yes
Yes
Yes
maxSnrMgn
Maximum SNR
Yes
Yes
Yes
minSnrMgn
Minimum SNR
Yes
Yes
Yes
downshiftSnrMgn
Seamless Rate Adaptation
no
NA
no
upshiftSnrMgn
Seamless Rate Adaptation
no
NA
no
minUpshiftTime
Seamless Rate Adaptation
no
NA
no
minDownshiftTime
Seamless Rate Adaptation
no
NA
no
fastMinTxRate
Minimum Transmit Rate for channels configured as Fast
Yes
Yes
Yes
MALC Hardware Installation Guide
671
ADSL
Table 57: ADSL-CO-Profile (Continued) adsl-co-profile
ATU-C
SLMS Supported
SLMS Range supported
SLMS Default
interleaveMinTxRate
Minimum Transmit Rate for channels configured as Interleaved
Yes
Yes
Yes
fastMaxTxRate
Maximum Transmit Rate for channels configured as Fast
Yes
Yes
Yes
maxInterleaveDelay
Maximum Interleave Delay for channel(s) configured as Interleaved
Yes
1 to 63
63 when in ADSL2+ Annex A
interleaveMaxTxRate
Maximum Transmit Rate for channels configured as Interleaved
Yes
Yes
Yes
thresh15MinLofs
Loss of Frame event count
Yes
Yes
Yes
thresh15MinLoss
Loss of signal event count
Yes
Yes
Yes
thresh15MinLols
Loss of link event count
Yes
Yes
Yes
thresh15MinLprs
Loss of Loss of Power Seconds event count
Defaulted
Defaulted
Defaulted
thresh15MinESs
Errored Seconds event count
Yes
Yes
Yes
threshFastRateUp
Threshold time for increase rate on channels configured as Fast
Defaulted
Defaulted
Defaulted
Configuring S=1/2 transmission mode for fast mode 1
Verify that the adminstatus of the if-translate profile for the ADSL port is up: zSH> update if-translate 1-12-1-0/adsl ifIndex: ----------> {505} shelf: ------------> {1} slot: -------------> {12} port: -------------> {1} subport: ----------> {0} type: -------------> {adsl} adminstatus: ------> {down} up physical-flag: ----> {true} iftype-extension: -> {none} ifName: -----------> {1-12-1-0} redundancy-param1: -> {0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Record updated.
672
MALC Hardware Installation Guide
Configuring ADSL interfaces
2
Verify that the ADSL channelization is set to fast:
zSH> update adsl-profile 1/12/1 adslLineConfProfile: ------------> {0} adslAlarmConfProfile: -----------> {0} adslTrellisModeEnabled: ---------> {true} adslNTRModeEnabled: -------------> {true} adslTransmissionMode: -----------> {autonegotiatemode} adslChannelMode: ----------------> {fastonly} adslMaxDownstreamToneIndex: -----> {511} adslMinDownstreamToneIndex: -----> {32} adslMaxUpstreamToneIndex: -------> {31} adslMinUpstreamToneIndex: -------> {6} adslPotsBypassRelayMaxDuration: -> {60} adslLineDMTConfMode: ------------> {freqdivmux} adslAnnexMModeEnabled: ----------> {false} .................... Save new record? [s]ave, [c]hange or [q]uit: s Record updated.
3
Set the maximum transmit rate to 12 Mbps for fast ADSL channel modes. This forces the ADSL port into S=1/2 transmission mode.
zSH> update adsl-co-profile 1/12/1 Please provide the following: [q]uit. rateMode: -----------------> {adaptatstartup}: rateChanRatio: ------------> {50}: targetSnrMgn: -------------> {60}: maxSnrMgn: ----------------> {310}: minSnrMgn: ----------------> {0}: downshiftSnrMgn: ----------> {0}: upshiftSnrMgn: ------------> {0}: minUpshiftTime: -----------> {0}: minDownshiftTime: ---------> {0}: fastMinTxRate: ------------> {32000}: interleaveMinTxRate: ------> {32000}: fastMaxTxRate: ------------> {8160000}: 12000000 12Mbps maxInterleaveDelay: -------> {24}: interleaveMaxTxRate: ------> {8160000}: thresh15MinLofs: ----------> {0}: thresh15MinLoss: ----------> {0}: thresh15MinLols: ----------> {0}: thresh15MinLprs: ----------> {0}: thresh15MinESs: -----------> {0}: threshFastRateUp: ---------> {0}: threshInterleaveRateUp: ---> {0}: threshFastRateDown: -------> {0}: threshInterleaveRateDown: -> {0}: initFailureTrapEnable: ----> {disable} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
MALC Hardware Installation Guide
673
ADSL
Configuring S=1/2 transmission mode for interleaved mode 1
Ensure the adminstatus of the if-translate profile for the ADSL port is up: zSH> update if-translate 1-12-1-0/adsl ifIndex: ----------> {505} shelf: ------------> {1} slot: -------------> {12} port: -------------> {1} subport: ----------> {0} type: -------------> {adsl} adminstatus: ------> {down} up physical-flag: ----> {true} iftype-extension: -> {none} ifName: -----------> {1-12-1-0} redundancy-param1: -> {0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Record updated.
2
Set the ADSL channelization to interleaved:
zSH> update adsl-profile 1/12/1 adslLineConfProfile: ------------> {0} adslAlarmConfProfile: -----------> {0} adslTrellisModeEnabled: ---------> {true} adslNTRModeEnabled: -------------> {true} adslTransmissionMode: -----------> {autonegotiatemode} adslChannelMode: ----------------> {fastonly}interleaveonly adslMaxDownstreamToneIndex: -----> {511} adslMinDownstreamToneIndex: -----> {32} adslMaxUpstreamToneIndex: -------> {31} adslMinUpstreamToneIndex: -------> {6} adslPotsBypassRelayMaxDuration: -> {60} adslLineDMTConfMode: ------------> {freqdivmux} adslAnnexMModeEnabled: ----------> {false} .................... Save new record? [s]ave, [c]hange or [q]uit: s Record updated.
3
Set the maximum transmit rate to 12 Mbps for interleaved ADSL channel mode. This forces the ADSL port into S=1/2 transmission mode.
zSH> update adsl-co-profile 1/12/1 Please provide the following: [q]uit. rateMode: -----------------> {adaptatstartup}: rateChanRatio: ------------> {50}: targetSnrMgn: -------------> {60}: maxSnrMgn: ----------------> {310}: minSnrMgn: ----------------> {0}: downshiftSnrMgn: ----------> {0}: upshiftSnrMgn: ------------> {0}: minUpshiftTime: -----------> {0}: minDownshiftTime: ---------> {0}:
674
MALC Hardware Installation Guide
Configuring ADSL interfaces
fastMinTxRate: ------------> {32000}: interleaveMinTxRate: ------> {32000}: fastMaxTxRate: ------------> {8160000}: maxInterleaveDelay: -------> {24}: interleaveMaxTxRate: ------> {8160000}: 12000000 12Mbps thresh15MinLofs: ----------> {0}: thresh15MinLoss: ----------> {0}: thresh15MinLols: ----------> {0}: thresh15MinLprs: ----------> {0}: thresh15MinESs: -----------> {0}: threshFastRateUp: ---------> {0}: threshInterleaveRateUp: ---> {0}: threshFastRateDown: -------> {0}: threshInterleaveRateDown: -> {0}: initFailureTrapEnable: ----> {disable} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
MALC Hardware Installation Guide
675
ADSL
Configuring ADSL 2 and ADSL 2+ ADSL 2 and ADSL 2+ is supported on MALC ADSL 48 port cards only.
Configuring the ADSL 2 and ADSL 2+ interfaces The following parameters are used to configure ADSL 2 and ADSL 2+ interfaces: Table 58: ADSL2/2+ interface parameters Parameter
Description
adslTransmissionMode
ADSL transmission mode. Supported values:
(adsl-profile)
Values: autonegotiatemode : automatically negotiates all supported transmission modes. The modem uses the G.hs protocol to negotiate a transmission mode in this order: ADSL2+, ADSL2, then G.dmt. fullratemode : automatically negotiates full rate modes (G.dmt and T1 mode). G.dmt has priority over T1 mode. glitemode : G.lite. Supports only interleaved mode. t1mode : Full rate T1 gdmtmode : G.dmt ghsmode :The modem uses the G.hs protocol to negotiate a transmission mode in this order: T1.413, G.dmt, then G.lite. adsl2Mode the modem negotiates ADSL2 only. Supports Annex M. adsl2PlusMode the modem negotiates ADSL2+ only. Supports Annex M. Default: autonegotiatemode
adslLineDMTConfMode (adsl-profile)
Selects whether there is overlap of ADSL Discrete Multi-Tone (DMT) frequency bins. Values: echoCancel overlap of DMT frequency bins. Only supported by g.dmt Annex A. freqDivMux no overlap of DMT frequency bins. Separates downstream and upstream transmission. Default: freqDivMux
reachExtendedAdsl2 (adsl-co-profile)
Defines whether downstream reach extended ADSL2 (READSL2) operation should be enforced by the ATU-C. Only enable for ADSL2 and ADSL2+ Values: enable disable Default: enable
676
MALC Hardware Installation Guide
Configuring ADSL interfaces
1
There is typically no need to change the settings in ADSL profiles to configure ADSL 2 or ADSL 2+. But if your setup requires it, use the update command: Note: For Annex M configurations, in the adsl-profile, set adslMinDownstreamToneIndex to 64 and adslMaxUpstreamToneIndex to 63. Also, in the adsl-cpe-profile, set valid values for fastMaxTxRate and interleaveMaxTxRate. If Annex M mode is disabled, these values should be reset.
zSH> update adsl-profile 1/3/1 Please provide the following: [q]uit. adslLineConfProfile: ------------> {0000000334}: adslAlarmConfProfile: -----------> {0000000334}: adslTrellisModeEnabled: ---------> {true}: adslNTRModeEnabled: -------------> {false}: adslTransmissionMode: -----------> {autonegotiatemode}: adslChannelMode: ----------------> {fastonly}: adslMaxDownstreamToneIndex: -----> {511}: adslMinDownstreamToneIndex: -----> {32}: adslMaxUpstreamToneIndex: -------> {31}: adslMinUpstreamToneIndex: -------> {6}: adslPotsBypassRelayMaxDuration: -> {60}: adslLineDMTConfMode: ------------> {freqdivmux}: adslAnnexMModeEnabled: ----------> {false} .................... Save new record? [s]ave, [c]hange or [q]uit: s Record updated.
2
Update the downstream interface to specify a line speed: zSH> update adsl-co-profile 1/3/1 Please provide the following: [q]uit. rateMode: -----------------> {adaptatruntime}: rateChanRatio: ------------> {50}: targetSnrMgn: -------------> {60}: maxSnrMgn: ----------------> {310}: minSnrMgn: ----------------> {0}: downshiftSnrMgn: ----------> {0}:upshiftSnrMgn: ------------> {0}: minUpshiftTime: -----------> {0}: minDownshiftTime: ---------> {0}: fastMinTxRate: ------------> {32000}: interleaveMinTxRate: ------> {32000}: fastMaxTxRate: ------------> {32736000}: maxInterleaveDelay: -------> {63}: interleaveMaxTxRate: ------> {32736000}: thresh15MinLofs: ----------> {0}: thresh15MinLoss: ----------> {0}: thresh15MinLols: ----------> {0}: thresh15MinLprs: ----------> {0}: thresh15MinESs: -----------> {0}:
MALC Hardware Installation Guide
677
ADSL
threshFastRateUp: ---------> {0}: threshInterleaveRateUp: ---> {0}: threshFastRateDown: -------> {0}: threshInterleaveRateDown: -> {0}: initFailureTrapEnable: ----> {disable}: reachExtendedAdsl2: -------> {enable}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
3
There is typically no need to change the settings for the upstream interface, unless you want to configure trap thresholds. If your setup requires it, use the update command: zSH> update adsl-cpe-profile 1/3/1 Please provide the following: [q]uit. rateMode: -----------------> {adaptatruntime}: rateChanRatio: ------------> {50}: targetSnrMgn: -------------> {60}: maxSnrMgn: ----------------> {310}: minSnrMgn: ----------------> {0}: downshiftSnrMgn: ----------> {30}: upshiftSnrMgn: ------------> {90}: minUpshiftSnrMgn: ---------> {60}: minDownshiftSnrMgn: -------> {60}: fastMinTxRate: ------------> {32000}: interleaveMinTxRate: ------> {32000}: fastMaxTxRate: ------------> {1024000}: interleaveMaxTxRate: ------> {1536000}: maxInterleaveDelay: -------> {16}: thresh15MinLofs: ----------> {0}: thresh15MinLoss: ----------> {0}: thresh15MinLprs: ----------> {0}: thresh15MinESs: -----------> {0}: threshFastRateUp: ---------> {0}: threshInterleaveRateUp: ---> {0}: threshFastRateDown: -------> {0}: threshInterleaveRateDown: -> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
4
Use the dslstat command to displays the status of the interface: zSH> dslstat 1-3-1-0/adsl General Stats: ------------AdminStatus..................................UP Line uptime (DD:HH:MM:SS)....................0:04:27:52 DslUpLineRate (bitsPerSec)...................512000 DslDownLineRate (bitsPerSec).................8064000 DslMaxAttainableUpLineRate (bitsPerSec)......565333 DslMaxAttainableDownLineRate (bitsPerSec)....856000
678
MALC Hardware Installation Guide
Configuring ADSL interfaces
Out Octets...................................286571 Out Discards.................................0 Out Errors...................................0 In Octets....................................286571 In Discards..................................0 In Errors....................................0 ATM OCD Count................................0 ATM NCD Count................................0 ATM HEC Count................................0 ATM far-end OCD Count........................0 ATM far-end NCD Count........................0 ATM far-end HEC Count........................0 ADSL Physical Stats: -----------------Actual Transmission connection standard......G.dmt AdslAtucCurrLineSnrMgn (tenths dB)...........310 AdslAtucCurrLineAtn (tenths dB)..............135 AdslAtucCurrOutputPwr (tenths dB)............70 AdslAturCurrLineSnrMgn (tenths dB)...........90 AdslAturCurrLineAtn (tenths dB)..............135 AdslAturCurrOutputPwr (tenths dB)............103 LOFS.........................................0 LOLS.........................................0 LOSS.........................................0 ESS..........................................0 Inits........................................1 Adsl connects................................1 Adsl disconnects.............................5407 near-end statistics: ------------------blocks received..............................147087 errored blocks received......................0 CRC errors on interleaved buffer.............0 CRC errors on fast buffer....................0 FEC corrected errors on interleaved buffer...0 FEC corrected errors on fast buffer..........0 background errored blocks received...........0 non-SES blocks received......................0 Severely Errored Seconds.....................0 Unavailable Seconds..........................59 Loss of Signal Seconds.......................0 Seconds with one/more FECs...................0 Seconds declared as high BER.................0 far-end statistics: ------------------blocks received..............................147205 errored blocks received......................1 CRC errors on interleaved buffer.............0 CRC errors on fast buffer....................1 FEC corrected errors on interleaved buffer...0 FEC corrected errors on fast buffer..........0
MALC Hardware Installation Guide
679
ADSL
background errored blocks received...........0 non-SES blocks received......................0 Severely Errored Seconds.....................0 Unavailable Seconds..........................0 Loss of Signal Seconds.......................0 Seconds with one/more FECs...................0 Loss of Power (dying gasps)..................0 Seconds declared as high BER.................0 Fast retrains................................0 Fast retrain failures........................0
Table 59: ADSL-CPE-Profile
680
adsl-cpe-profile
ATU-R
SLMS Supported
SLMS Range supported
SLMS Default
maxInterleaveDelay
Maximum Interleave Delay for channel(s) configured as Interleaved
Yes
1 to 63
16 when in ADSL2+ Annex A
thresh15MinLofs
Loss of Frame event count
Yes
0 to 900
0
thresh15MinLoss
Loss of signal event count
Yes
0 to 900
0
thresh15MinLprs
Loss of Loss of Power Seconds event count
Yes
0 to 900
0
thresh15MinESs
Errored Seconds event count
Yes
0 to 900
0
threshFastRateUp
Threshold time for increase rate on channels configured as Fast
no
0
0
threshInterleaveRateUp
Threshold time for increase rate on channels configured as Interleaved
no
0
0
threshFastRateDown
Threshold time for decrease rate on channels configured as fast
no
0
0
threshInterleaveRateDo wn
Threshold time for decrease rate on channels configured as Interleaved
no
0
0
minTxThresholdRateAl arm
Threshold point to alarm on minimum rate
Yes
0 to 2,147,483,647
Yes
maxInterleaveDelay
Maximum Interleave Delay for channel(s) configured as Interleaved
Yes
1 to 63
16 when in ADSL2+ Annex A
thresh15MinLofs
Loss of Frame event count
Yes
0 to 900
0
thresh15MinLoss
Loss of signal event count
Yes
0 to 900
0
MALC Hardware Installation Guide
Configuring ADSL interfaces
Table 59: ADSL-CPE-Profile adsl-cpe-profile
ATU-R
SLMS Supported
SLMS Range supported
SLMS Default
thresh15MinLprs
Loss of Loss of Power Seconds event count
Yes
0 to 900
0
thresh15MinESs
Errored Seconds event count
Yes
0 to 900
0
threshFastRateUp
Threshold time for increase rate on channels configured as Fast
no
0
0
threshInterleaveRateUp
Threshold time for increase rate on channels configured as Interleaved
no
0
0
threshFastRateDown
Threshold time for decrease rate on channels configured as fast
no
0
0
threshInterleaveRateDo wn
Threshold time for decrease rate on channels configured as Interleaved
no
0
0
minTxThresholdRateAl arm
Threshold point to alarm on minimum rate
Yes
0 to 2,147,483,647
Yes
MALC Hardware Installation Guide
681
ADSL
Configure ADSL2+ interfaces Table 60 describes the ADSL2+ parameters. Table 60: ADSL2/2+ interface parameters Parameter
Description
adslTransmissionMode
ADSL2+ transmission mode. Supported values:
(adsl-profile)
Values: autonegotiatemode : automatically negotiates all supported transmission modes. The modem uses the G.hs protocol to negotiate a transmission mode in this order: ADSL2+, ADSL2, then G.dmt. fullratemode : automatically negotiates full rate modes (G.dmt and T1 mode). G.dmt has priority over T1 mode. glitemode : G.lite. Supports only interleaved mode. t1mode : Full rate T1 gdmtmode : G.dmt ghsmode :The modem uses the G.hs protocol to negotiate a transmission mode in this order: T1.413, G.dmt, then G.lite. adsl2Mode the modem negotiates ADSL2 only. Supports Annex M. adsl2PlusMode the modem negotiates ADSL2+ only. Supports Annex M. Default: autonegotiatemode
adslLineDMTConfMode (adsl-profile)
Selects whether there is overlap of ADSL Discrete Multi-Tone (DMT) frequency bins. Values: echoCancel overlap of DMT frequency bins. Only supported by g.dmt Annex A. freqDivMux no overlap of DMT frequency bins. Separates downstream and upstream transmission. Default: freqDivMux
reachExtendedAdsl2 (adsl-co-profile)
Defines whether downstream reach extended ADSL2 (READSL2) operation should be enforced by the ATU-C. Only enable for ADSL2 and ADSL2+ Values: enable disable Default: enable
Usually there is no need to change the default settings in ADSL2+ profiles to configure ADSL2+. If you do need to change the default settings, use update:
682
MALC Hardware Installation Guide
Configuring ADSL interfaces
Note: For Annex M configurations, in the adsl-profile, set adslMinDownstreamToneIndex to 64 and adslMaxUpstreamToneIndex to 63. Also, in the adsl-cpe-profile set valid values for fastMaxTxRate. If Annex M mode is disabled, these values should be reset. zSH> update adsl-profile 1/9/1 adsl-profile 1/9/1 Please provide the following: [q]uit. adslLineConfProfile: ------------> {0000000422}: ** read-only ** adslAlarmConfProfile: -----------> {0000000422}: ** read-only ** adslTrellisModeEnabled: ---------> {true}: adslNTRModeEnabled: -------------> {false}: adslTransmissionMode: -----------> {autonegotiatemode}: adslChannelMode: ----------------> {fastonly}: adslMaxDownstreamToneIndex: -----> {511}: adslMinDownstreamToneIndex: -----> {64}: adslMaxUpstreamToneIndex: -------> {63}: adslMinUpstreamToneIndex: -------> {33}: adslPotsBypassRelayMaxDuration: -> {60}: adslLineDMTConfMode: ------------> {freqdivmux}: adslAnnexMModeEnabled: ----------> {false}: adslAnnexMPSDMask:--------------> {eu64 eu60 eu56 eu52 eu48 eu44 eu36 eu32 all} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
eu40
Update the downstream interface to specify a line speed: zSH> update adsl-co-profile 1/9/1 adsl-co-profile 1/9/1 Please provide the following: [q]uit. rateMode: -----------------> {adaptatruntime}: rateChanRatio: ------------> {50}: targetSnrMgn: -------------> {60}: maxSnrMgn: ----------------> {310}: minSnrMgn: ----------------> {0}: downshiftSnrMgn: ----------> {0}: upshiftSnrMgn: ------------> {0}: minUpshiftTime: -----------> {0}: minDownshiftTime: ---------> {0}: fastMinTxRate: ------------> {32000}: interleaveMinTxRate: ------> {32000}: fastMaxTxRate: ------------> {32736000}: maxInterleaveDelay: -------> {63}: interleaveMaxTxRate: ------> {32736000}: thresh15MinLofs: ----------> {0}: thresh15MinLoss: ----------> {0}: thresh15MinLols: ----------> {0}: thresh15MinLprs: ----------> {0}: thresh15MinESs: -----------> {0}: threshFastRateUp: ---------> {0}:
MALC Hardware Installation Guide
683
ADSL
threshInterleaveRateUp: ---> {0}: threshFastRateDown: -------> {0}: threshInterleaveRateDown: -> {0}: initFailureTrapEnable: ----> {disable}: reachExtendedAdsl2: -------> {enable}: minTxThresholdRateAlarm: --> {0}: minINP: -------------------> {0} phyRSupport: --------------> {disable} phyRmaxINP: ---------------> {0} phyRminRSoverhead: --------> {0} phyRRtxRatio: -------------> {0} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
There is typically no need to change the settings for the upstream interface, unless you want to configure trap thresholds. If your setup requires it, use the update command: zSH> update adsl-cpe-profile 1/9/1 Please provide the following: [q]uit. rateMode: -----------------> {adaptatruntime}: rateChanRatio: ------------> {50}: targetSnrMgn: -------------> {60}: maxSnrMgn: ----------------> {310}: minSnrMgn: ----------------> {0}: downshiftSnrMgn: ----------> {30}: upshiftSnrMgn: ------------> {90}: minUpshiftSnrMgn: ---------> {60}: minDownshiftSnrMgn: -------> {60}: fastMinTxRate: ------------> {32000}: interleaveMinTxRate: ------> {32000}: fastMaxTxRate: ------------> {1024000}: interleaveMaxTxRate: ------> {1536000}: maxInterleaveDelay: -------> {16}: thresh15MinLofs: ----------> {0}: thresh15MinLoss: ----------> {0}: thresh15MinLprs: ----------> {0}: thresh15MinESs: -----------> {0}: threshFastRateUp: ---------> {0}: threshInterleaveRateUp: ---> {0}: threshFastRateDown: -------> {0}: threshInterleaveRateDown: -> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Use the dslstat command to displays the status of the interface: zSH> dslstat 1-3-1-0/adsl General Stats: ------------AdminStatus..................................UP
684
MALC Hardware Installation Guide
Configuring ADSL interfaces
Line uptime (DD:HH:MM:SS)....................0:04:27:52 DslUpLineRate (bitsPerSec)...................512000 DslDownLineRate (bitsPerSec).................8064000 DslMaxAttainableUpLineRate (bitsPerSec)......565333 DslMaxAttainableDownLineRate (bitsPerSec)....856000 Out Octets...................................286571 Out Discards.................................0 Out Errors...................................0 In Octets....................................286571 In Discards..................................0 In Errors....................................0 ATM OCD Count................................0 ATM NCD Count................................0 ATM HEC Count................................0 ATM far-end OCD Count........................0 ATM far-end NCD Count........................0 ATM far-end HEC Count........................0 ADSL Physical Stats: -----------------Actual Transmission connection standard......G.dmt AdslAtucCurrLineSnrMgn (tenths dB)...........310 AdslAtucCurrLineAtn (tenths dB)..............135 AdslAtucCurrOutputPwr (tenths dB)............70 AdslAturCurrLineSnrMgn (tenths dB)...........90 AdslAturCurrLineAtn (tenths dB)..............135 AdslAturCurrOutputPwr (tenths dB)............103 LOFS.........................................0 LOLS.........................................0 LOSS.........................................0 ESS..........................................0 Inits........................................1 Adsl connects................................1 Adsl disconnects.............................5407 near-end statistics: ------------------blocks received..............................147087 errored blocks received......................0 CRC errors on interleaved buffer.............0 CRC errors on fast buffer....................0 FEC corrected errors on interleaved buffer...0 FEC corrected errors on fast buffer..........0 background errored blocks received...........0 non-SES blocks received......................0 Severely Errored Seconds.....................0 Unavailable Seconds..........................59 Loss of Signal Seconds.......................0 Seconds with one/more FECs...................0 Seconds declared as high BER.................0 far-end statistics: -------------------
MALC Hardware Installation Guide
685
ADSL
blocks received..............................147205 errored blocks received......................1 CRC errors on interleaved buffer.............0 CRC errors on fast buffer....................1 FEC corrected errors on interleaved buffer...0 FEC corrected errors on fast buffer..........0 background errored blocks received...........0 non-SES blocks received......................0 Severely Errored Seconds.....................0 Unavailable Seconds..........................0 Loss of Signal Seconds.......................0 Seconds with one/more FECs...................0 Loss of Power (dying gasps)..................0 Seconds declared as high BER.................0 Fast retrains................................0 Fast retrain failures........................0
Broadcom Phy-R™ parameters Setting the Broadcom Phy-R™ parameters in the co and cpe ADSL2+ profiles is for advanced users. Note: The Phy-R™ parameter in the ADSL2+ co profile cannot be used unless there is a Broadcom CPE modem at the customer site with Phy-R™ parameters in the ADSL2+ cpe profile. Table 61 describes the ADSL2+ parameters that are relevant to the new Phy-R™ parameters, and the Phy-R™ parameters. Table 61: Broadcom Phy-R™ parameters and relevant ADSL2+ parameters
686
Parameter
Definition
maxInterleaveDelay (already used in the case of normal interleaving)
This parameter (already used in the case of normal interleaving) defines the maximum allowed nominal delay. It is used by the modem to set an upper bound on the allowed receiver retransmission queue size. Since it must be at least equal to the round trip delay, retransmission cannot be activated if the maxDelay configured is lower than 4ms.
minrate (already used in the case of normal interleaving)
This parameter (already used in the case of normal interleaving) defines the minimum guaranteed user data rate. The available bandwidth for retransmission is equal to the difference between the current data rate on the line and the minimum rate configured.
MALC Hardware Installation Guide
Configuring ADSL interfaces
Table 61: Broadcom Phy-R™ parameters and relevant ADSL2+ parameters Parameter
Definition
INPmin (already used in the case of normal interleaving)
This parameter (already used in the case of normal interleaving) defines the minimal guaranteed impulse noise protection, provided that the available data bandwidth allowed for retransmissions is not exceeded.
phyRSupport
Enable to turn on Phy-R™ parameters. Disable to turn off Phy-R™ parameters. Default is disable.
INPmax
This parameter defines the maximum number of consecutive retransmissions that may take place and therefore bounds the maximal jitter due to retransmissions. A default value of zero doesn't bound the number of consecutive retransmissions (that will however never exceed maxDelay * 4 symbols).
minRSoverhead
This new parameter allows to force a minimum amount of RS overhead. This can be used to guarantee a given amount of steady state error correction capability. A default of zero doesn't force the use of RS overhead.
minRtxRatio
This parameter allows to provision a minimal guaranteed retransmission bandwidth, on top of the minimum rate. In case of the repetitive impulses of known maximal length and periodicity, this parameter can be used to guarantee that the repetitive impulse noise can be corrected. A default of zero doesn't force any extra guaranteed data bandwidth for retransmissions
Enabling Phy-R ™ parameters Zhone recommends setting the minINP parameter to 20, the maxInterleaveDelay of at least 4, and the phyRSupport to enable in both the CO and CPE adsl profiles. zSH> update adsl-co-profile 1/3/2 adsl-co-profile 1/3/2 Please provide the following: [q]uit. rateMode: -----------------> {adaptatruntime}: rateChanRatio: ------------> {50}: targetSnrMgn: -------------> {60}: maxSnrMgn: ----------------> {310}: minSnrMgn: ----------------> {0}: downshiftSnrMgn: ----------> {0}: upshiftSnrMgn: ------------> {0}: minUpshiftTime: -----------> {0}:
MALC Hardware Installation Guide
687
ADSL
minDownshiftTime: ---------> {0}: fastMinTxRate: ------------> {32000}: interleaveMinTxRate: ------> {32000}: fastMaxTxRate: ------------> {32736000}: maxInterleaveDelay: -------> {8}: interleaveMaxTxRate: ------> {32736000}: thresh15MinLofs: ----------> {0}: thresh15MinLoss: ----------> {0}: thresh15MinLols: ----------> {0}: thresh15MinLprs: ----------> {0}: thresh15MinESs: -----------> {0}: threshFastRateUp: ---------> {0}: threshInterleaveRateUp: ---> {0}: threshFastRateDown: -------> {0}: threshInterleaveRateDown: -> {0}: initFailureTrapEnable: ----> {disable}: reachExtendedAdsl2: -------> {enable}: minTxThresholdRateAlarm: --> {0}: minINP: -------------------> {0}: 20 phyRSupport: --------------> {disable}: enable phyRmaxINP: ---------------> {0}: phyRminRSoverhead: --------> {0}: phyRRtxRatio: -------------> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated. zSH> update adsl-cpe-profile 1/3/2 adsl-cpe-profile 1/3/2 Please provide the following: [q]uit. rateMode: -----------------> {adaptatruntime}: rateChanRatio: ------------> {50}: targetSnrMgn: -------------> {60}: maxSnrMgn: ----------------> {310}: minSnrMgn: ----------------> {0}: downshiftSnrMgn: ----------> {30}: upshiftSnrMgn: ------------> {90}: minUpshiftSnrMgn: ---------> {60}: minDownshiftSnrMgn: -------> {60}: fastMinTxRate: ------------> {32000}: interleaveMinTxRate: ------> {32000}: fastMaxTxRate: ------------> {1024000}: interleaveMaxTxRate: ------> {1536000}: maxInterleaveDelay: -------> {8}: thresh15MinLofs: ----------> {0}: thresh15MinLoss: ----------> {0}: thresh15MinLprs: ----------> {0}: thresh15MinESs: -----------> {0}: threshFastRateUp: ---------> {0}: threshInterleaveRateUp: ---> {0}: threshFastRateDown: -------> {0}: threshInterleaveRateDown: -> {0}: minTxThresholdRateAlarm: --> {0}: minINP: -------------------> {0}: 20
688
MALC Hardware Installation Guide
Configuring ADSL interfaces
phyRSupport: --------------> {disable}: enable phyRmaxINP: ---------------> {0}: phyRminRSoverhead: --------> {0}: phyRRtxRatio: -------------> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Updating ADSL Annex A card profiles The card change command updates a card profile for a new card type. By default, the system validates that there is a match between the software load file and the card type. An optional parameter is available to override validation to use a software load file that does not match the card type. The MALC allows the reuse of profiles and configurations when replacing Annex A cards with Annex A/M cards. Replacement Annex A/M cards can be used as spares or backup for existing Annex A cards. Table 62 lists legacy Annex A cards and the corresponding Annex A/M cards. Table 62: Annex A and Annex A/M Cards Annex A Card
Annex A/M Card
MALC-ADSL-48-A
MALC-ADSL-48-A/M
MALC-ADSL+SPLTR-48A-2S
MALC-ADSL+SPLTR-48A/M-2S
MALC-ADSL+POTS-TDM/PKT-48A-2S
MALC-ADSL+POTS-TDM/PKT-48A/M-2S
Updating card profiles from ADSL-48A to ADSL-48A/M To use the card change command to change the card type from MALC-ADSL-48A to MALC-ADSL-48A/M 1
Download the software image for the MALC-ADSL-48A/M card: image download TFTPserverAddress malcxdsl48anxam.bin
2
Remove the MALC-ADSL-48A card.
3
Enter the command to change the card type to MALC-ADSL-48A/M: card change 1//5036 5065
4
Insert the MALC-ADSL-48A/M card.
5
Wait for the card to come up running, then perform a Configuration Sync in ZMS.
MALC Hardware Installation Guide
689
ADSL
Configuring POTS ports The following table summarizes how to configure a POTS interfaces on the MALC: Action
Command
Configure the POTS gain settings. See Configuring POTS settings on page 690.
update analog-if-cfg-profile index/voicefxs Where index is of the form shelf-slot-port-subport or a user-defined string. For typical applications, the settings in this profile do not need to be modified.
Configure the POTS signaling. See Configuring signal type and ring frequency on page 693.
update analog-fxs-cfg-profile index/voicefxs
Activate the POTS interfaces in the if-translate profiles. See Activating POTS interfaces on page 694.
update if-translate index/voicefxs
For typical applications, the settings in this profile do not need to be modified.
Configuring POTS settings Modify the following parameters in the analog-if-cfg-profile if you need to change the gain settings for each voice line:
690
MALC Hardware Installation Guide
Configuring POTS ports
Parameter
Description
if-cfg-impedence
Specifies the terminating impedance of analog voice interfaces. Values: ohms600complex 600 Ohms + 2.16uF ohms900complex 00 Ohms + 2.16uF Default: ohms600complex
if-cfg-receive-tlp
The receive TLP is the signal level to the customer premises equipment (CPE). The receive signal range is +3 dB to -9 dB. A positive number adds gain, a negative number adds loss to the analog signal after decoding from PCM. For example, a receive TLP setting of -6 dB will generate a voice signal at -6 dB level. Values: fxsrtlpn9db fxsrtlpn8db fxsrtlpn7db fxsrtlpn6db fxsrtlpn5db fxsrtlpn4db fxsrtlpn3db (not supported on the POTS 900 card) fxsrtlpn2db (not supported on the POTS 900 card) fxsrtlpn1db fxsrtlp0db fxsrtlp1db fxsrtlp2db fxsrtlp3db rtlpnummeric Default: fxsrtlpn6db
MALC Hardware Installation Guide
691
ADSL
Parameter
Description
if-cfg-transmit-tlp
The transmit TLP is the signal level from the customer premises equipment (CPE). The transmit signal range is +9 dB to -3 dB. A positive number adds loss, a negative number adds gain to the analog signal before encoding to PCM. For example, a transmit TLP setting of +3 dB will set a loss of 3 dB to generate a 0 dB PCM signal. Values: fxsTtlp9db (not supported on the POTS 900 card) fxsTtlp8db (not supported on the POTS 900 card) fxsTtlp7db fxsTtlp6db fxsTtlp5db fxsTtlp4db fxsTtlp3db fxsTtlp2db fxsTtlp1db fxsTtlp0db fxsTtlpN1db fxsTtlpN2db fxsTtlpN3db Default: fxsTtlp0db
if-cfg-pcm-encoding
Line encoding. Values: alaw for E1. mulaw for T1.
if-cfg-receive-tlpNum
Receive Transmission Level Point (RTLP) settings control the amount gain or loss added to the incoming signal after it is decoded to analog. To increase the signal level set the RTLP setting to higher values. The default is 0 dB. Values: -160 to 85 (in tenths of dB) Default: 0 dB
if-cfg-transmit-tlpNum
Transmit Transmission Level Point (TTLP) controls the amount of gain or loss added to a voice signal before it is encoded to digital PCM. To increase the signal level, reduce the TTLP setting to lower value. Values: -175 to 70 (in tenths of dB) Default: 0 dB
If you need to modify the gain settings, update the analog-if-cfg-profile for each interface. For example;: zSH> update analog-if-cfg-profile 1-3-1-0/voicefxs Please provide the following: (q=quit) if-cfg-impedence: ------------>{ohms600complex}: modify if required if-cfg-receive-tlp: ---------->{fxsrtlp0db}: modify if required
692
MALC Hardware Installation Guide
Configuring POTS ports
if-cfg-transmit-tlp: --------->{fxsttlp0db}: modify if required if-cfg-trunk-conditioning: --->{idle}: if-maintenance-mode: --->{off}: if-cfg-pcm-encoding: --->{mulaw}: alaw | mulaw if-cfg-receive-tlpNum: -----> {0}: if-cfg-transmit-tlpNum: ----> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Configuring signal type and ring frequency Modify the following parameters in the analog-fxs-cfg-profile if you need to change signalling type and ring frequency for each voice line: Parameter
Description
signal-type
The method by which an off-hook condition is indicated. Values: fxsloopstart Default: fxsloopstart
ring-frequency
Rate in cycles per second (Hertz) at which polarity reversal occurs on ringing. Values: ringfrequency20 ringfrequency25 ringfrequency30 ringfrequency50 Default: ringfrequency20
ring-back
The ring back is requested if this variable is set to on. Values: on off Default: off
If you need to modify the signaling and ring frequency, update the analog-fxs-cfg-profile for each interface. For example;: zSH> update analog-fxs-cfg-profile 1-3-1-0/voicefxs signal-type: ----> {fxsloopstart} ring-frequency: -> {ringfrequency20} modify if required ring-back: ------> {off} modify if required .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
MALC Hardware Installation Guide
693
ADSL
Activating POTS interfaces Update the if-translate records for the POTS interface to enable the line. The following example activates the first POTS interface on the slot card located in shelf 1 slot 3: zSH> update if-translate 1-3-1-0/voicefxs Please provide the following: [q]uit. ifIndex: ----------> {132}: shelf: ------------> {1}: slot: -------------> {3}: port: -------------> {1}: subport: ----------> {0}: type: -------------> {voicefxs}: adminstatus: ------> {down}: up physical-flag: ----> {true}: iftype-extension: -> {0}: ifName: -----------> {1-3-1-0}: redundancy-param1: -> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Activate the rest of the interfaces similarly.
ADSL Testing SELT and DELT are loop tests which can be used to proactively pre-qualify a loop (SELT) or reactively test a loop after a modem has been deployed (DELT).
SELT (Single-End Loop Tests) SELT is a single-ended test. A copper loop can be tested from the MALC only, without the need for any external test equipment in either the CO or at the remote end of the loop. SELT is primarily used for proactive loop pre-qualification. For example, by checking in advance if a loop is capable of supporting ADSL2+ by determining distance, wire gauge and noise, any loop conditions can be fixed prior to rolling a truck to the customer premise. Note: Test limitations:
• Test range is 600 to 9000 feet. • Mixed gauge wire is not supported. • Results have +/- 10% variance. Configuring SELT The MALC supports the following SELT commands
694
MALC Hardware Installation Guide
ADSL Testing
•
selt start Starts a SELT test on an interface.
•
selt abort Terminates a SELT test on an interface.
•
selt clear Clear SELT results for an interface.
•
selt set units Set the SELT display units for all interfaces.
•
selt set max-duration Sets the maximum amount of time a SELT test can run.
•
selt gauge Sets the expected diameter of the wire connected to an interface. The diameter may be set using any units, regardless of the display units set with the selt set units command. The wire-gauge option must use one of these settings: –
unknown - unknown wire gauge
–
awg19 - 19 gauge
–
awg22 - 22 gauge
–
awg24 - 24 gauge
–
awg26 - 26 gauge
–
32mm - 0.32 millimeters
–
40mm - 0.40 millimeters
–
50mm - 0.50 millimeters
–
63mm - 0.63 millimeters
–
65mm - 0.65 millimeters
–
90mm - 0.90 millimeters
The chip used to implement the selt test may restrict which values can be configured. The Conexant-g24 chip accepts these settings:
•
–
awg24
–
awg26
–
40mm (as an alias for awg26)
–
50mm (as an alias for awg24)
selt cable
MALC Hardware Installation Guide
695
ADSL
Sets the type of cable being tested, real or simulated. The real setting indicates that an actual physical cable is connected to the interface. In a lab or test environment, the cable may be simulated and use the dsl90 or dsl400 setting.
•
–
real: indicates a physical cable is connected to the interface.
–
dsl90: a Consultronics/Spirent DLS90 is simulating the cable.
–
dsl400: a Consultronics/Spirent DLS400 is simulating the cable.
selt show status Displays SELT test progress.
•
selt show noise [start-index [num-vals]] Displays SELT noise floor per subcarrier.
The can be in the form of ifIndex (432), name/type (1-4-1-0/adsl) or shelf/slot/port/subport/type (1/4/1/0/adsl0. To configure SELT, enter the desired SELT test commands. The following example contains the commands for setting units, max-duration, starting a test, stopping a test, displaying status, clearing test data, and displaying noise. zSH> selt set units awg Selt information will be displayed in awg units zSH> selt set max-duration 1-4-3-0/adsl 60 Selt test timeout on interface 1-4-3-0/adsl set to 60 seconds. zSH> selt start 1-4-3-0/adsl Selt test started on interface 1-4-3-0/adsl zSH> selt abort 1-4-3-0/adsl Selt test aborted on interface 1-4-3-0/adsl zSH> selt show status 1-4-3-0/adsl status: complete max-duration: disabled time-left: 0 seconds device: conexant-g24 bridge-taps: not-supported date-time: results generated 10 sep 2006, 14:55:34 length: 405 feet gauge: awg26 zSH> selt clear 1-4-3-0/adsl Selt results cleared on interface 1-4-3-0/adsl zSH> selt show noise 1-4-1-0/adsl Results generated 10 sep 2006, 14:35:56. Tone Tone Freq Noise Index (kHz) (dBm/Hz) ----- --------- --------
696
MALC Hardware Installation Guide
ADSL Testing
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 [etc, up
4.3125 -95.7 8.6250 -118.3 12.9375 -121.4 17.2500 -123.8 21.5625 -124.9 25.8750 -126.3 30.1875 -125.5 34.5000 -121.8 38.8125 -113.6 43.1250 -125.9 47.4375 -127.7 51.7500 -128.4 56.0625 -128.3 60.3750 -128.5 64.6875 -128.3 69.0000 -124.4 to index 511]
zSH> selt show noise 1-4-1-0/adsl 253 6 Results generated 10 sep 2006, 14:35:56. Tone Tone Freq Noise Index (kHz) (dBm/Hz) ----- --------- -------253 1095.3750 -122.0 254 1099.6875 -122.6 255 1104.0000 -121.9 256 1108.3125 no measurement 257 1112.6250 no measurement 258 1116.9375 no measurement 259 1121.2500 no measurement
DELT (Dual-End Loop Test) DELT is a dual-ended test that requires equipment at both ends of the copper loop. While this prevents DELT from being used on loops where no CPE has yet been deployed, DELT offers a deeper set of loop tests, and can provide very valuable information on the condition of a copper loop. DELT is primarily used for reactive tests on a loop after a modem has been deployed to either help troubleshoot a line or capture a baseline of loop characteristics. In addition, DELT can assist in predetermining line capability to support new services, such as voice and video. Note: Test limitations:
• Test range is 600 to 9000 feet. • Mixed gauge wire is not supported. • Results have +/- 10% variance.
MALC Hardware Installation Guide
697
ADSL
Configuring DELT The MALC supports the following SELT commands
•
delt start Starts a DELT test on an interface.
•
delt abort Terminates a DELT test on an interface.
•
delt clear Clear DELT results for an interface.
•
delt show status Displays DELT test progress.
•
delt show noise [start-index [num-vals]] Displays DELT noise floor per subcarrier.
The can be in the form of ifIndex (432), name/type (1-4-1-0/adsl) or shelf/slot/port/subport/type (1/4/1/0/adsl0. To configure DELT, enter the desired DELT test commands. The following example contains the commands for setting units, max-duration, starting a test, stopping a test, displaying status, clearing test data, and displaying noise. zSH> delt start 1-4-1-0/adsl Delt test started on interface 1-4-1-0/adsl zSH> delt show status 1-4-1-0/adsl Status success Device: conexant-g24 Delt results generated 14 sep 2006, 21:26:05. Downstream Upstream ----------------------Attainable Bit Rate (bps) 9300000 1088000 Loop Attenuation (dB) 19.0 0.0 Signal Attenuation (dB) 19.0 0.0 SNR Margin (dB) 0.0 6.0 Actual Transmit Power (dBm) 29.1 11.8 zSH> delt abort 1-4-1-0/adsl Delt test aborted on interface 1-4-1-0/adsl zSH> delt clear 1-4-1-0/adsl Selt results cleared on interface 1-4-1-0/adsl zSH> delt show noise 1-4-2-0/adsl Delt results generated 14 sep 2006, 22:56:44. Tone Tone Freq Attenuation (dB) Noise (dBm/Hz) Index (kHz) dnstream upstream dnstream upstream ----- ---------------- --------------- -------0 4.3125 no data no data -85.0 no data
698
MALC Hardware Installation Guide
SNR (dB) dnstream upstream -------- -------0.0 no data
ADSL Testing
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 [etc, up
8.6250 -80.1 12.9375 -84.6 17.2500 -88.1 21.5625 -88.1 25.8750 -88.1 30.1875 -88.1 34.5000 -88.1 38.8125 -94.1 43.1250 -94.1 47.4375 -88.1 51.7500 -88.1 56.0625 -94.1 60.3750 -94.1 64.6875 -94.1 69.0000 -94.1 73.3125 -88.1 77.6250 -91.1 81.9375 -91.1 86.2500 -91.1 90.5625 -91.1 94.8750 -88.1 to index 511]
no data no data no data no data no data -28.7 -22.1 -16.2 -11.2 -8.0 -6.9 -6.9 -7.3 -7.6 -8.0 -8.5 -9.2 -10.0 -10.9 -11.9 -12.8
-137.0 -139.0 -140.0 -141.0 -141.0 -141.0 -141.0 -141.0 -141.0 -141.0 -141.0 -142.0 -142.0 -141.0 -142.0 -141.0 -142.0 -141.0 -141.0 -141.0 -140.0
no data no data no data no data no data -105.5 -111.0 -112.0 -112.0 -108.5 -109.5 -111.5 -111.5 -111.5 -110.0 -108.5 -111.0 -111.5 -110.5 -109.5 -106.0
zSH> delt show noise 1-4-2-0/adsl 253 6 Delt results generated 14 sep 2006, 22:56:44. Tone Tone Freq Attenuation (dB) Noise (dBm/Hz) Index (kHz) dnstream upstream dnstream upstream ----- ---------------- --------------- -------253 1095.3750 -24.7 no data -118.0 no data 254 1099.6875 -25.1 no data -119.0 no data 255 1104.0000 -25.4 no data -118.0 no data 256 1108.3125 no data no data no data no data 257 1112.6250 no data no data no data no data 258 1116.9375 no data no data no data no data 259
1121.2500
no data
no data
no data
no data
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
no no no no no
data data data data data 21.0 29.0 34.5 38.5 41.5 43.0 46.0 47.5 49.5 50.0 50.0 50.0 50.0 50.0 50.0 50.0
SNR (dB) dnstream upstream -------- -------33.5 no data 31.5 no data 0.0 no data no data no data no data no data no data no data no data
no data
MALC Hardware Installation Guide
699
ADSL
ADSL cable and port pinouts This section describes the ADSL cables available from Zhone Technologies and the ADSL port pinouts.
•
MALC-ADSL-48 card pinouts on page 701
•
ADSL cable pinouts on page 705
ADSL card port pinouts This section describes the following ADSL port pinouts:
•
ADSL 24 port card pinouts on page 700
•
MALC-ADSL-48 card pinouts on page 701
ADSL 24 port card pinouts The MALC-ReachDSL-24 card uses standard RJ-21X pinouts. Table 63 lists the port pinouts. Table 63: MALC-ReachDSL-24 pinouts
700
Pin
Function
Pin
Function
1
Channel 1 ring
26
Channel 1 tip
2
Channel 2 ring
27
Channel 2 tip
3
Channel 3 ring
28
Channel 3 tip
4
Channel 4 ring
29
Channel 4 tip
5
Channel 5 ring
30
Channel 5 tip
6
Channel 6 ring
31
Channel 6 tip
7
Channel 7 ring
32
Channel 7 tip
8
Channel 8 ring
33
Channel 8 tip
9
Channel 9 ring
34
Channel 9 tip
10
Channel 10 ring
35
Channel 10 tip
11
Channel 11 ring
36
Channel 11 tip
12
Channel 12 ring
37
Channel 12 tip
13
Channel 13 ring
38
Channel 13 tip
14
Channel 14 ring
39
Channel 14 tip
15
Channel 15 ring
40
Channel 15 tip
16
Channel 16 ring
41
Channel 16 tip
17
Channel 17 ring
42
Channel 17 tip
MALC Hardware Installation Guide
ADSL cable and port pinouts
Table 63: MALC-ReachDSL-24 pinouts (Continued) Pin
Function
Pin
Function
18
Channel 18 ring
43
Channel 18 tip
19
Channel 19 ring
44
Channel 19 tip
20
Channel 20 ring
45
Channel 20 tip
21
Channel 21 ring
46
Channel 21 tip
22
Channel 22 ring
47
Channel 22 tip
23
Channel 23 ring
48
Channel 23 tip
24
Channel 24 ring
49
Channel 24 tip
25
Not used
50
Not used
MALC-ADSL-48 card pinouts Table 64 lists the MALC-ADSL-48 card pinouts. Table 64: MALC-ADSL-48 card pinouts Port
Signal
Pin
1
Tip
J7-2
Ring
J7-1
Tip
J7-4
Ring
J7-3
Tip
J7-6
Ring
J7-5
Tip
J7-8
Ring
J7-7
Tip
J7-10
Ring
J7-9
Tip
J7-12
Ring
J7-11
Tip
J7-14
Ring
J7-13
Tip
J7-16
Ring
J7-15
2
3
4
5
6
7
8
MALC Hardware Installation Guide
701
ADSL
Table 64: MALC-ADSL-48 card pinouts (Continued) Port
Signal
Pin
9
Tip
J7-18
Ring
J7-17
Tip
J7-20
Ring
J7-19
Tip
J7-22
Ring
J7-21
Tip
J7-24
Ring
J7-23
Tip
J7-26
Ring
J7-25
Tip
J7-28
Ring
J7-27
Tip
J7-30
Ring
J7-29
Tip
J7-32
Ring
J7-31
Tip
J7-34
Ring
J7-33
Tip
J7-36
Ring
J7-35
Tip
J7-38
Ring
J7-37
Tip
J7-40
Ring
J7-39
Tip
J7-42
Ring
J7-41
Tip
J7-44
Ring
J7-43
Tip
J7-46
Ring
J7-45
10
11
12
13
14
15
16
17
18
19
20
21
22
23
702
MALC Hardware Installation Guide
ADSL cable and port pinouts
Table 64: MALC-ADSL-48 card pinouts (Continued) Port
Signal
Pin
24
Tip
J7-48
Ring
J7-47
Tip
J7-50
Ring
J7-49
Tip
J7-52
Ring
J7-51
Tip
J7-54
Ring
J7-53
Tip
J7-56
Ring
J7-55
Tip
J7-58
Ring
J7-57
Tip
J7-60
Ring
J7-59
Tip
J7-62
Ring
J7-61
Tip
J7-64
Ring
J7-63
Tip
J7-66
Ring
J7-65
Tip
J7-68
Ring
J7-67
Tip
J7-70
Ring
J7-69
Tip
J7-72
Ring
J7-71
Tip
J7-74
Ring
J7-73
Tip
J7-76
Ring
J7-75
25
26
27
28
29
30
31
32
33
34
35
36
37
38
MALC Hardware Installation Guide
703
ADSL
Table 64: MALC-ADSL-48 card pinouts (Continued) Port
Signal
Pin
39
Tip
J7-78
Ring
J7-77
Tip
J7-80
Ring
J7-79
Tip
J7-82
Ring
J7-81
Tip
J7-84
Ring
J7-83
Tip
J7-86
Ring
J7-85
Tip
J7-88
Ring
J7-87
Tip
J7-90
Ring
J7-89
Tip
J7-92
Ring
J7-91
Tip
J7-94
Ring
J7-93
Tip
J7-96
Ring
J7-95
40
41
42
43
44
45
46
47
48
704
MALC Hardware Installation Guide
ADSL cable and port pinouts
ADSL cable pinouts This section describes the ADSL-48 to dual 50-pin connector cable on page 705
ADSL-48 to dual 50-pin connector cable Figure 88 shows the ADSL-48 to dual 50-pin connector cable (MALC-CBL-ADSL-48). Table 65 on page 706 lists the ADSL-48 card pinouts. Table 66 on page 710 lists additional ADSL-48 to dual 50-pin connector cables. Table 67 on page 710 lists variations of these cables. Figure 88: 48-port ADSL to dual 50-pin cable
MALC Hardware Installation Guide
705
ADSL
Table 65: 48-port ADSL to dual-50-pin cable pinouts Pair
Signal
Color
From
To
Binder group
1
Tip
White/Blue
P1-2
P2-26
1 (Blue)
Ring
Blue/White
P1-1
P2-1
Tip
White/Orange
P1-4
P2-27
Ring
Orange/White
P1-3
P2-2
Tip
White/Green
P1-6
P2-28
Ring
Green/White
P1-5
P2-3
Tip
White/Brown
P1-8
P2-29
Ring
Brown/White
P1-7
P2-4
Tip
White/Slate
P1-10
P2-30
Ring
Slate/White
P1-9
P2-5
Tip
Red/Blue
P1-12
P2-31
Ring
Blue/Red
P1-11
P2-6
Tip
Red/Orange
P1-14
P2-32
Ring
Orange/Red
P1-13
P2-7
Tip
Red/Green
P1-16
P2-33
Ring
Green/Red
P1-15
P2-8
Tip
Red/Brown
P1-18
P2-34
Ring
Brown/Red
P1-17
P2-9
Tip
Red/Slate
P1-20
P2-35
Ring
Slate/Red
P1-19
P2-10
Tip
Black/Blue
P1-22
P2-36
Ring
Blue/Black
P1-21
P2-11
Tip
Black/Orange
P1-24
P2-37
Ring
Orange/Black
P1-23
P2-12
2
3
4
5
6
7
8
9
10
11
12
706
MALC Hardware Installation Guide
ADSL cable and port pinouts
Table 65: 48-port ADSL to dual-50-pin cable pinouts (Continued) Pair
Signal
Color
From
To
Binder group
13
Tip
White/Blue
P1-26
P2-38
2 (Orange)
Ring
Blue/White
P1-25
P2-13
Tip
White/Orange
P1-28
P2-39
Ring
Orange/White
P1-27
P2-14
Tip
White/Green
P1-30
P2-40
Ring
Green/White
P1-29
P2-15
Tip
White/Brown
P1-32
P2-41
Ring
Brown/White
P1-31
P2-16
Tip
White/Slate
P1-34
P2-42
Ring
Slate/White
P1-33
P2-17
Tip
Red/Blue
P1-36
P2-43
Ring
Blue/Red
P1-35
P2-18
Tip
Red/Orange
P1-38
P2-44
Ring
Orange/Red
P1-37
P2-19
Tip
Red/Green
P1-40
P2-45
Ring
Green/Red
P1-39
P2-20
Tip
Red/Brown
P1-42
P2-46
Ring
Brown/Red
P1-41
P2-21
Tip
Red/Slate
P1-44
P2-47
Ring
Slate/Red
P1-43
P2-22
Tip
Black/Blue
P1-46
P2-48
Ring
Blue/Black
P1-45
P2-23
Tip
Black/Orange
P1-48
P2-49
Ring
Orange/Black
P1-47
P2-24
14
15
16
17
18
19
20
21
22
23
24
MALC Hardware Installation Guide
707
ADSL
Table 65: 48-port ADSL to dual-50-pin cable pinouts (Continued) Pair
Signal
Color
From
To
Binder group
25
Tip
White/Blue
P1-50
P3-26
3 (Green)
Ring
Blue/White
P1-49
P3-1
Tip
White/Orange
P1-52
P3-27
Ring
Orange/White
P1-51
P3-2
Tip
White/Green
P1-54
P3-28
Ring
Green/White
P1-53
P3-3
Tip
White/Brown
P1-56
P3-29
Ring
Brown/White
P1-55
P3-4
Tip
White/Slate
P1-58
P3-30
Ring
Slate/White
P1-57
P3-5
Tip
Red/Blue
P1-60
P3-31
Ring
Blue/Red
P1-59
P3-6
Tip
Red/Orange
P1-62
P3-32
Ring
Orange/Red
P1-61
P3-7
Tip
Red/Green
P1-64
P3-33
Ring
Green/Red
P1-63
P3-8
Tip
Red/Brown
P1-66
P3-34
Ring
Brown/Red
P1-65
P3-9
Tip
Red/Slate
P1-68
P3-35
Ring
Slate/Red
P1-67
P3-10
Tip
Black/Blue
P1-70
P3-36
Ring
Blue/Black
P1-69
P3-11
Tip
Black/Orange
P1-72
P3-37
Ring
Orange/Black
P1-71
P3-12
26
27
28
29
30
31
32
33
34
35
36
708
MALC Hardware Installation Guide
ADSL cable and port pinouts
Table 65: 48-port ADSL to dual-50-pin cable pinouts (Continued) Pair
Signal
Color
From
To
Binder group
37
Tip
White/Blue
P1-74
P3-38
4 (Brown)
Ring
Blue/White
P1-73
P3-13
Tip
White/Orange
P1-76
P3-39
Ring
Orange/White
P1-75
P3-14
Tip
White/Green
P1-78
P3-40
Ring
Green/White
P1-77
P3-15
Tip
White/Brown
P1-80
P3-41
Ring
Brown/White
P1-79
P3-16
Tip
White/Slate
P1-82
P3-42
Ring
Slate/White
P1-81
P3-17
Tip
Red/Blue
P1-84
P3-43
Ring
Blue/Red
P1-83
P3-18
Tip
Red/Orange
P1-86
P3-44
Ring
Orange/Red
P1-85
P3-19
Tip
Red/Green
P1-88
P3-45
Ring
Green/Red
P1-87
P3-20
Tip
Red/Brown
P1-90
P3-46
Ring
Brown/Red
P1-89
P3-21
Tip
Red/Slate
P1-92
P3-47
Ring
Slate/Red
P1-91
P3-22
Tip
Black/Blue
P1-94
P3-48
Ring
Blue/Black
P1-93
P3-23
Tip
Black/Orange
P1-96
P3-49
Ring
Orange/Black
P1-95
P3-24
38
39
40
41
42
43
44
45
46
47
48
MALC Hardware Installation Guide
709
ADSL
Table 66: Additional 48-port ADSL to dual 50-pin connector cables MALC CABLE PART NAME
DESCRIPTION
MALC-CBL-ADSL-48
96 PIN TO (2) 50-PIN CONNECTOR, 48-PORT CARDS, 10 FT/3.05M
MALC-CBL-ADSL-48-10FTF
96PIN TO 2 50PIN FEMALE CONNECTOR, 10FT/3.05M
MALC-CBL-ADSL-48-15FT
96 PIN TO (2) 50-PIN CONNECTOR, 48-PORT CARDS, 15 FT/4.57M
MALC-CBL-ADSL-48-30M
96 PIN TO (2) 50-PIN CONNECTOR, 48-PORT CARDS, 98.4 FT/30M
MALC-CBL-ADSL-48-30MF
96 PIN TO (2) 50-PIN FEMALE CONNECTOR, 98.4FT/30M LENGTH
MALC-CBL-ADSL-48-4FT
96 PIN TO (2) 50-PIN CONNECTOR, 48-PORT CARDS, 4 FT/1.22M
MALC-CBL-ADSL-48-50M
96 PIN TO (2) 50-PIN CONNECTOR, 48-PORT CARDS, 164 FT/50M
MALC-CBL-ADSL-48-50FTF
96PIN TO 92) 50PIN CONNECTOR, 48-PORT CARDS, 50FT/ 15.24M
MALC-CBL-ADSL-48-70M
96 PIN TO (2) 50-PIN CONNECTOR, 48-PORT CARDS, 229 FT/70M
MALC-CBL-ADSL-48-125FTF
96PIN TO (2) 50PIN CONNECTOR, 48-PORT CARDS, 125FT/38.1M
MALC-CBL-ADSL-48-90DEG-10FT
96 PIN TO (2) 50-PIN CONNECTOR, 48-PORT CARDS, 90 DEGREES, 10 FT/3.05M
MALC-CBL-ADSL-48-90DEG-4FT
96 PIN TO (2) 50-PIN CONNECTOR, 48-PORT CARDS, 90 DEGREES, 4 FT/1.22M
MALC-CBL-ADSL-48-UP-30FT
96 PIN TO (2) 50-PIN CONNECTOR, 48-PORT CARDS, ROUTES UPWARDS, 30 FT/9.1M
MALC-CBL-ADSL-48-UP-60FT
96 PIN TO (2) 50-PIN CONNECTOR, 48-PORT CARDS, ROUTES UPWARDS, 60 FT/18.28M
Table 67 lists variations of the 48-port ADSL to dual 50-pin connector cables. These cables use the pinouts listed in Table 67 on page 710. Table 67: Variations of 48-port ADSL to dual 50-pin connector cables
710
MALC CABLE PART NAME
DESCRIPTION
MALC-CBL-ADSL-48-100FT-BLUNT
96 PIN TO BLUNT END, 100 FT/30.5M
MALC-CBL-ADSL-48-350FT-BLUNT
96 PIN TO BLUNT END, 350 FT/106.7M
MALC Hardware Installation Guide
17 SHDSL
This chapter describes the MALC SHDSL cards and explains how to configure them. It includes:
•
Overview, page 711
•
Activating SHDSL cards, page 714
•
Configuring SDSL interfaces, page 716
•
Configuring SHDSL interfaces, page 721
•
SHDSL pinouts, page 726
•
Delivering power and data to a Raptor 100 SHDSL-LP, page 731
Overview This section describes the following SHDSL cards:
•
MALC-G.SHDSL-4W-12 card on page 712
•
MALC-SHDSL-48 on page 713
MALC Hardware Installation Guide
711
SHDSL
MALC-G.SHDSL-4W-12 card The MALC-G.SHDSL-4W-12 card provides longer reach and higher line rates than the existing 2-wire SHDSL-24 card. Combining two channels for one subscriber line provides twice the bandwidth. The channels that can be combined must be consecutive pairs (for example, 1 and 2, 3 and 4, 23 and 24). Table 68: MALC-G.SHDSL-4W-12 specifications Specification
Value
Density
12 subscriber lines
Physical interfaces
One (1) RJ-21X Champ 50-pin connector
Line characteristics
ITU G.991.2 SHDSL
Redundancy
None
Nominal line rate
Symmetric rate increments up to 4.6 Mbps
ATM support
Default VPI/VCI ranges (per port): VPI: 0 to 1 VCI: 32 to 255
Power consumption
34.0 W nominal (all port initialized, no ports trained) plus 0.79 W additional per active SHDSL interface 43.48 W maximum
712
MALC Hardware Installation Guide
Overview
MALC-SHDSL-48
active fault pwr fail
The MALC-SHDSL-48 card supports the G.991.2 (SHDSL) standard.
1- 48
ma 0 6 0 7
SHDSL 48
Table 69: MALC-SHDSL-48 specifications Specification
Description
Size
1 slot
Density
48 ports
Physical interfaces
One (1) 96-pin telco connector
Standards supported
ITU G.991.2
Supported line rates
192 Kbps to 2320 Kbps
ATM support
Cell Relay switching onto ATM bus to Uplink card Default VPI/VCI ranges (per port):
• •
VPI: 0 to 1 VCI: 32 to 255
MALC Hardware Installation Guide
713
SHDSL
Table 69: MALC-SHDSL-48 specifications (Continued) Specification
Description
Metallic test functions
Look-in test
Redundancy
None
Main components
DSL chipset 8 pin, SHDSL line interfaces and transceivers
Power consumption
34.0 W nominal (all port initialized, no ports trained) plus 0.79 W additional per active SHDSL interface 52.96 W maximum
Activating SHDSL cards Each card installed in the system must have a card-profile. Each type of slot card requires different settings in the card-profile. Tip: You can specify the name of the software image for a card in a card-profile or a type-module. Each card of a particular type can share a single type-module. Settings in type-modules can be overridden by settings in card-profiles. The slots cards on the MALC have the following types and software images: Table 70: MALC card types Card
Type
Name of software image
MALC-G.SHDSL-4W-12
5030
malcgshdsl4w.bin
MALC-SHDSL-48
5069
malcgshdsl48.bin
Creating card-profiles for SHDSL 4-wire cards The following example creates a card-profile for a 4 wire SHDSL card in shelf 1, slot 19: zsh> card add 1/19/5030
or zSH> new card-profile 1/19/5030 shelf/slot/type Please provide the following: [q]uit. sw-file-name: -----------> {}: malcgshdsl4w.bin admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}:
714
MALC Hardware Installation Guide
Activating SHDSL cards
sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {true}: sw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}: hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {unknowntype}: card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created.
Verifying the slot card installation After you save the card-profile record, the slot card in that slot resets and the begins downloading their software image from the flash card. This could take a few moments. When the card has finished loading, the card state displays the state of the card. For example: State
: LOADING
You can also use the slots command and specify the slot number of the card to view the state of the card and other information about the card. For example: zSH> slots 13 Type Card Version EEPROM Version Serial # CLEI Code Card-Profile ID Shelf Slot State Mode Heartbeat check Longest hbeat
: : : : : : : : : : : :
MALC ADSL 1 2 110006 No CLEI 1/13/5004 1 13 LOADING indicates the card is still initializing FUNCTIONAL enabled 0
zSH> slots 13 Type Card Version EEPROM Version Serial # CLEI Code Card-Profile ID Shelf Slot State Mode Heartbeat check Longest hbeat
: : : : : : : : : : : :
MALC ADSL 1 2 110006 No CLEI 1/13/5004 1 13 RUNNING indicates the card is functional FUNCTIONAL enabled 59
MALC Hardware Installation Guide
715
SHDSL
Fault reset Uptime
: enabled : 1 minute
To view the status of all the cards, use the slots command without any arguments: zSH> slots 1: MALC DS3 (RUNNING) 13: MALC ADSL (RUNNING) 15: MALC MTAC (RUNNING)
Viewing active redundant cards Use the showactivecards command to view all active cards in the system that are part of a redundant card group: zSH> showactivecards Shelf/Slot Group Id Card Type __________________________________ 1: 1/5 2 MALC T1E1VG 2: 1/1 1 MALC RPR GIGE
Configuring SDSL interfaces The following table summarizes the commands required to configure SDSL interfaces on the MALC: Action
Command
Configure the type of SDSL interface and whether it is acting as a CO or CPE device. See Specifying the type of DSL interface on page 718.
update dsl-config index/sdsl Where index is of the form shelf-slot-port-subport or a user-defined string.
Configure specific DSL interface settings, such as framing and compatibility. See Configuring an SDSL interface on page 719.
update sdsl-config index/sdsl
Verify the type of SHDSL interface. See Verifying the interface on page 720.
update dsl-config index/shdsl
Verify the interface is active. See Verifying the interface on page 720
showlinestatus shelf slot port
Where index is of the form shelf-slot-port-subport or a user-defined string.
Note: The SHDSL interfaces for the G.SHDSL-48 card do not support CPE mode so each port must be configured as unit-mode CO.
716
MALC Hardware Installation Guide
Configuring SDSL interfaces
Automatic baud rate adaption and fixed rate settings When you select the sdsllatest line type for SDSL interface, or shdsllatest for a SHDSL interface), the MALC can perform automatic baud rate adaption. This allows receiving devices to communicate with transmitting devices operating at different baud rates without the need to establish data rates in advance. By determining the baud rate from the transmitting device, the receiving MALC automatically trains to match the line rate of the incoming data. The automatic baud rate adaption process may take several minutes. This is because the CO and CPE device modems use an algorithm to step through a sequence of baud rates, where the devices establish a connection at each line rate and then move to the next higher rate until they reach the final rate they agree upon. The following table describes how the fixed-bit-rate settings in the sdsl-config and shdsl-config profiles affect training rates. Table 71: Fix-bit-rate settings and modem train rates CO
CPE
Then
Disabled
Disabled
highest available rate is negotiated.
Disabled
Enabled
Modems train at CPE’s fixed rate.
Enabled
Disabled
Modems train at CO’s fixed rate.
Enabled
Enabled
Modems train at lowest fixed rate.
Configuration restrictions The same card can support a combination of SDSL and SHDSL ports with the following restrictions:
•
Configure the DSL modem in pairs (modems 1 and 2, modems 3 and 4, and so on).
•
Adjacent modems (ports 1 and 2, 3 and 4, and so on) must have the same line-type. Each DSL modem supports 2 DSL ports.
•
Adjacent modems must have the same framer-type (if configured for SDSL).
•
Adjacent modems must have the same unit-mode setting.
•
Adjacent modems must have the same network timing recovery setting.
Other configuration settings, such as line speed, can differ for each line on the card.
MALC Hardware Installation Guide
717
SHDSL
Specifying the type of DSL interface Note: The IANA-ifType for SDSL interfaces is shdsl. The interface name appears in profile indexes and system output. The dsl-config profile supports the following parameters: Parameter
Description
line-type
The DSL type supported on this interface. Values: shdsl SHDSL. Not compatible with shdsllatest firmware. sdsl SDSL. Not compatible with sdsllatest firmware. shdsllatest Compatible with future versions of firmware code. Required for autobaud. sdsllatest Compatible with future versions of firmware code. Required for autobaud. Default: shdsllatest Refer to the release notes for your device firmware revision levels.
unit-mode
Specifies whether the unit is configured as a CO or CPE device. Values: co cpe Default: co
line-status-trap -enable
Specifies whether a line status trap should be sent whenever the DSL line goes up or down. Note that this setting does not apply to line status traps sent during system bootup. During bootup, line status traps are not sent. A DSL link down trap has a moderate severity level and a link up trap has a low severity. Default: enabled
To specify the interface as an SDSL line, set the line-type in the dsl-config profile: zSH> update dsl-config 1-1-1-0/shdsl line-type: -> {sdsl}: sdsl | sdsllatest unit-mode: -> {coe}: line-status-trap-enable: -> {enabled} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
718
MALC Hardware Installation Guide
Configuring SDSL interfaces
Configuring an SDSL interface By default, MALC DSL interfaces are configured as SDSL CO interfaces with a line rate of 1,552 Kbps. The sdsl-config profile supports the following parameters (all others should be left at their default values): Parameter
Description
config-line-rate
The line rate. Values: line-rate-144kbps, line-rate-160kbps, line-rate-192kbps, line-rate-208kbps, line-rate-224kbps, line-rate-256kbps, line-rate-272kbps, line-rate-320kbps, line-rate-368kbps, line-rate-384kbps, line-rate-400kbps, line-rate-416kbps, line-rate-528kbps, line-rate-768kbps, line-rate-784kbps, line-rate-1040kbps, line-rate-1152kbps, line-rate-1168kbps, line-rate-1536kbps, line-rate-1552kbps, line-rate-1568kbps, line-rate-2320kbps, line-rate-176kbps, line-rate-240kbps, line-rate-288kbps, line-rate-304kbps, line-rate-336kbps, line-rate-352kbps, line-rate-432kbps, line-rate-464kbps, line-rate-496kbps, line-rate-560kbps, line-rate-592kbps, line-rate-624kbps, line-rate-656kbps, line-rate-688kbps, line-rate-720kbps, line-rate-752kbps, line-rate-816kbps, line-rate-848kbps, line-rate-880kbps, line-rate-912kbps, line-rate-944kbps, line-rate-976kbps, line-rate-1008kbps, line-rate-1072kbps, line-rate-1104kbps, line-rate-1136kbps, line-rate-1200kbps, line-rate-1232kbps, line-rate-1264kbps, line-rate-1296kbps, line-rate-1328kbps, line-rate-1360kbps, line-rate-1392kbps, line-rate-1424kbps, line-rate-1456kbps, line-rate-1488kbps, line-rate-1520kbps, line-rate-1584kbps, line-rate-1616kbps, line-rate-1648kbps, line-rate-1680kbps, line-rate-1712kbps, line-rate-1744kbps, line-rate-1776kbps, line-rate-1808kbps, line-rate-1840kbps, line-rate-1872kbps, line-rate-1904kbps, line-rate-1936kbps, line-rate-1968kbps, line-rate-2000kbps, line-rate-2032kbps, line-rate-2064kbps, line-rate-2096kbps, line-rate-2128kbps, line-rate-2160kbps, line-rate-2192kbps, line-rate-2224kbps, line-rate-2256kbps, line-rate-2288kbps Default: line-rate-1552kbps
fix-bit-rate
Enables or disables automatic baud rate adaption. Values: fix-bit-disable This value enables automatic baud rate adaption. If the CO and CPE devices have different line rates at startup, the lower of the two rates will be selected. fix-bit-enable This value is used for static (set) baud rates.
MALC Hardware Installation Guide
719
SHDSL
Parameter
Description
ntr
Network timing recovery (NTR) specifies that the system synchronizes with an external (network) clocking source. The port settings for ports 1-24 and ports 25-48 are set collectively. Changing the setting on one port in a group changes the settings on all ports in that group. Values: ntr-enable the system synchronizes with the network. ntr-disable the system relies on its own clocking source. Default: ntr-disable
power-scale
Adjusts transmit power in small increments to compensate for minor differences on power between units. Values: 17664 For loop lengths from 0 to 10 feet (0 to 3.05 meters). Equivalent to -3.39db. 20992 For loop lengths less than 4000 feet (1219.2 meters). Equivalent to -1.9db. 29952 For loop lengths greater than 4000 feet (1219.2 meters). Equivalent to 1.19db.
Note: If SDSL ports require network timing, network timing recovery must be enabled for each port by setting the ntr parameter in to ntr-enable. The default sdsl-config profile enables automatic baud rate detection (if the DSL line-type is sdsllatest). To specify a particular line rate, update the profile: zSH> update sdsl-config 1-15-1-0/shdsl Please provide the following: ([q]uit) config-line-rate: -> {line-rate-1552kbps}: line-rate-752kbps fix-bit-rate: -> {fix-bit-disable}: fix-bit-enable connect-mode: -> {flowpoint-mode}: ntr: ---------> {ntr-disable}: framer-type: -> {atm-clear-channel}: power-scale: -> {17664}: 20992 .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Note: If you are setting a fixed rate for the interface, both sides must have the same setting or the line will not train.
Verifying the interface The showlinestatus command displays the status of the interfaces in the system. The following example displays the status of the line in shelf, slot 15, port 1: zSH> showlinestatus 1 15 1 Search in progress .........
720
MALC Hardware Installation Guide
Configuring SHDSL interfaces
................. GroupId --------> Status ---------> TxClk ----------> RefClkSrc ------> If_index -------> Peer If_Index --> Shelf ----------> Slot -----------> Port -----------> SubPort -------->
129 ACTIVE (1) NONE (1) NO 128 0 1 15 1 0
Configuring SHDSL interfaces The MALC supports 2-wire and 4-wire SHDSL cards. These cards support SHDSL as defined in ITU G.991.2. The cards are configured in the same way, except that the line rates for the 4-wire card are different. The following table summarizes the commands required to configure SHDSL interfaces on the MALC: Action
Command
Configure the type of SHDSL interface and whether it is acting as a CO or CPE device. See Specifying the type of DSL interface on page 718.
update dsl-config index/shdsl Where index is of the form shelf-slot-port-subport or a user-defined string.
Configure specific DSL interface settings, such as framing and compatibility. See Configuring an SDSL interface on page 719.
update shdsl-config index/shdsl
Verify the interface is active. See Verifying the interface on page 720
showlinestatus shelf slot port
Verify the type of SHDSL interface. See Verifying the type of DSL interface on page 726.
update dsl-config index/shdsl Where index is of the form shelf-slot-port-subport or a user-defined string.
Specifying the type of DSL interface The system creates dsl-config profiles for SHDSL cards with the appropriate settings. zSH> get dsl-config 1-6-1-0/shdsl line-type: -> {shdsllatest}: unit-mode: -> {co}: line-status-trap-enable: -> {enabled}
See Configuring SDSL interfaces on page 716 for a description of the values in the dsl-config profile. SHDSL interfaces have the same configuration restrictions as SDSL interfaces. For details, see Specifying the type of DSL interface on page 718.
MALC Hardware Installation Guide
721
SHDSL
Configuring a SHDSL line The shdsl-config profile supports the following parameters (all others should be left at their default values): Parameter
Description
shdsl-config-line-rate
The line rate. If the shdsl-fix-bit-rate parameter is enabled, the line will attempt to train at this rate. Note that the DSL modem uses 8kbps for ATM framing and other ATM overhead, so that effective line rate is 8kbps less that the configured rate. Note that some of these rates (indicated by line-rate-4w) are only supported on the 4-wire SHDSL card. Values: line-rate-72kbps, line-rate-80kbps, line-rate-136kbps, line-rate-144kbps, line-rate-200kbps, line-rate-208kbps, line-rate-264kbps, line-rate-272kbps, line-rate-328kbps, line-rate-336kbps, line-rate-392kbps, line-rate-400kbps, line-rate-456kbps, line-rate-464kbps, line-rate-520kbps, line-rate-528kbps, line-rate-584kbps, line-rate-592kbps, line-rate-648kbps, line-rate-656kbps, line-rate-712kbps, line-rate-720kbps, line-rate-776kbps, line-rate-784kbps, line-rate-840kbps, line-rate-848kbps, line-rate-904kbps, line-rate-912kbps, line-rate-968kbps, line-rate-976kbps, line-rate-1032kbps, line-rate-1040kbps, line-rate-1096kbps, line-rate-1104kbps, line-rate-1160kbps, line-rate-1168kbps, line-rate-1224kbps, line-rate-1232kbps, line-rate-1288kbps, line-rate-1296kbps, line-rate-1352kbps, line-rate-1360kbps, line-rate-1416kbps, line-rate-1424kbps, line-rate-1480kbps, line-rate-1488kbps, line-rate-1544kbps, line-rate-1552kbps, line-rate-1608kbps, line-rate-1616kbps, line-rate-1672kbps, line-rate-1680kbps, line-rate-1736kbps, line-rate-1744kbps, line-rate-1800kbps, line-rate-1808kbps, line-rate-1864kbps, line-rate-1872kbps, line-rate-1928kbps, line-rate-1936kbps, line-rate-1992kbps, line-rate-2000kbps, line-rate-2056kbps, line-rate-2064kbps, line-rate-2120kbps, line-rate-2128kbps, line-rate-2184kbps, line-rate-2192kbps, line-rate-2248kbps, line-rate-2256kbps, line-rate-2312kbps, line-rate-2320kbps, line-rate-2368kbps line-rate-4w-384kbps line-rate-4w-512kbps line-rate-4w-640kbps line-rate-4w-768kbps line-rate-4w-896kbps line-rate-4w-1024kbps line-rate-4w-1152kbps line-rate-4w-1280kbps line-rate-4w-1408kbps line-rate-4w-1536kbps line-rate-4w-1664kbps line-rate-4w-1792kbps line-rate-4w-1920kbps line-rate-4w-2048kbps line-rate-4w-2176kbps line-rate-4w-2304kbps line-rate-4w-2432kbps line-rate-4w-2560kbps line-rate-4w-2688kbps line-rate-4w-2816kbps line-rate-4w-2944kbps line-rate-4w-3072kbps line-rate-4w-3200kbps line-rate-4w-3328kbps line-rate-4w-3456kbps line-rate-4w-3584kbps line-rate-4w-3712kbps line-rate-4w-3840kbps line-rate-4w-3968kbps line-rate-4w-4096kbps line-rate-4w-4224kbps line-rate-4w-4352kbps line-rate-4w-4480kbps line-rate-4w-4608kbps Default: line-rate-2320kbps
shdsl-transmit-powerback-off-mode
Indicates if transmit power backoff is used on the other end of the loop. When enabled, the transmit power is reduced in steps of 1dB from 0 to 6 dB according to the received power. Values: backoffdisable backoffenable Default: backoffenable
722
MALC Hardware Installation Guide
Configuring SHDSL interfaces
Parameter
Description
shdsl-fix-bit-rate
Normally, if the CO side and CPE side select different line rates at startup, the lower of the two rates will be selected. By using the fix bit rate the CO side can override the default procedure and require startup at the rate specified in the shdsl-config-line-rate. Values: fix-bit-disable This value enables automatic baud rate adaption, where the DSL modem will train at the best achievable rate. If the CO and CPE devices have different line rates at startup, the line will train up to the highest rate supported by both devices. fix-bit-enable This value is used for static (set) baud rates. With this option, the line will attempt to connect at the rate configured in the shdsl-config-line-rate. Default: fix-bit-disable
shdsl-ntr
Determines the clocking on the SHDSL line. Values: ntr-local-osc The line uses the system’s internal clock. Also known as local timing. ntr-refck-8KHz The line uses an 8KHZ clock derived from a timing source such a T1/E1 interface. Default: ntr-local-osc
shdsl-clock-offset
This parameter is used to help achieve a low frequency wander and jitter between network and DSL system clock. This value can only be set on devices configured as CO in the dsl-config profile. Values: -100 to 100 (in parts per million) Default: 0
shdsl-repeater-id
This value identifies if the STU is being used as a repeater. Values: noChangeRepeater repeaterDisable repeaterEnable Default: repeaterDisable This parameter is not supported on G.SHDSL 48 cards.
shdsl-standard
Determines the SHDSL standard used. Values: annex-a G.991.2 Annex A. Typically used in the United States. annex-b G.991.2 Annex B. Typically used outside the United States. Default: annex-b
shdsl-startup-margin
Specifies the minimum desired target margin in dB for the local line conditions during startup. Used to negotiate the bit rate during startup. Values: 0 to 10 Default: 6
MALC Hardware Installation Guide
723
SHDSL
Parameter
Description
shdsl-wire-mode
This setting disables or enables 4-wire-framing. Values: four-wire-disable Four wire framing is disabled. Use this setting for the 2 wire SHDSL card. four-wire-enable-bit-interleave Sends one bit on channel 1, then one bit on channel 2, as described in the ITU-T G.991.2, section E.2. four-wire-enable-byte-interleave sends one byte on channel 1, and then one byte on channel 2, as described in ITU-T G.991.2, section E.7 four-wire-enable-non-interleave Sends 12 bytes on channel 1, 12 bytes on second channel 2. Default: four-wire-disable
shdsl-frame-sync
Not supported.
shdsl-decoder-coeffA
21 bit value corresponding to the decoder coefficient A or B, as defined in the G.991.2 standard. Note that the default value is bit-reversed, when compared against the recommended polynomials in the G.991.2 standard. Thus when you enter the 21-bit value, it should be written bit-reversed also.
shdsl-decoder-coeffB
Values: 0 to 2097151 Default: 366 (for shdsl-decoder-coeffA) 817 (for shdsl-decoder-coeffB) shdsl-power-scale
Adjusts transmit power in small increments to compensate for minor differences in power between units. The formula for the adjustment is: adjustment (in dB) = 29952 * 10(shdsl-power-scale / 20) The following values are recommended for different loop lengths. Values: 17664 For loop lengths from 0 to 10 feet (0 to 3.05 meters). Corresponds to -3.39dB. 20992 For loop lengths less than 4000 feet (1219 meters). Corresponds to -1.9dB. 29952 For loop lengths greater than 4000 feet (1219 meters). Corresponds to -1.19dB. Default: 29298
To configure an SHDSL interface update the shdsl-config profile: For a 2-wire interface: zSH> update shdsl-config 1-6-1-0/shdsl Please provide the following: [q]uit. shdsl-config-line-rate: -------------> shdsl-transmit-power-back-off-mode: -> shdsl-fix-bit-rate: -----------------> shdsl-ntr: --------------------------> shdsl-clock-offset: -----------------> shdsl-repeater-id: ------------------> shdsl-standard: ---------------------> shdsl-startup-margin: --------------->
724
MALC Hardware Installation Guide
{line-rate-2320kbps}: line-rate-1552kbps {backoffenable}: {fix-bit-disable}: {ntr-local-osc}: {0}: {repeaterdisable}: {annex-b}: {6}:
Configuring SHDSL interfaces
shdsl-wire-mode: --------------------> {four-wire-disable}: shdsl-frame-sync: -------------------> {45}: shdsl-decoder-coeffA: ---------------> {366}: shdsl-decoder-coeffB: ---------------> {817}: shdsl-power-scale: ------------------> {29298}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
To configure a 4-wire SHDSL interface update the shdsl-config profile: zSH> update shdsl-config 1-6-1-0/shdsl Please provide the following: [q]uit. shdsl-config-line-rate: -------------> {line-rate-2320kbps}: line-rate-4w-4608kbps shdsl-transmit-power-back-off-mode: -> {backoffenable}: shdsl-fix-bit-rate: -----------------> {fix-bit-disable}: shdsl-ntr: --------------------------> {ntr-local-osc}: shdsl-clock-offset: -----------------> {0}: shdsl-repeater-id: ------------------> {repeaterdisable}: shdsl-standard: ---------------------> {annex-b}: shdsl-startup-margin: ---------------> {6}: shdsl-wire-mode: --------------------> {four-wire-disable}: four-wire-enable-byte-interleave shdsl-frame-sync: -------------------> {45}: shdsl-decoder-coeffA: ---------------> {366}: shdsl-decoder-coeffB: ---------------> {817}: shdsl-power-scale: ------------------> {29298}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Verifying the interface Use the dslstat command to displays the status of the interface: zSH> dslstat 1-6-1-0/shdsl General Stats: ------------AdminStatus..................................UP DslUpLineRate (bitsPerSec)...................2320 DslDownLineRate (bitsPerSec).................2320 DslMaxAttainableUpLineRate (bitsPerSec)......2320 DslMaxAttainableDownLineRate (bitsPerSec)....2320 Out Octets...................................1921747131 Out Discards.................................0 Out Errors...................................0 In Octets....................................1921797746 In Discards..................................0 In Errors....................................0 ATM LCD Count................................1 DSL Physical Stats:
MALC Hardware Installation Guide
725
SHDSL
-----------------DslLineSnrMgn (tenths dB)....................384 DslLineAtn (tenths dB).......................246 DslCurrOutputPwr (tenths dB).................75 LOFS.........................................1 LOLS.........................................1 LOSS.........................................1 ESS..........................................9 CRC Errors...................................0 Inits........................................1
Verifying the type of DSL interface The system creates dsl-config profiles for SHDSL cards with the appropriate settings. zSH> get dsl-config 1-6-1-0/shdsl line-type: -> {shdsllatest}: unit-mode: -> {co}: line-status-trap-enable: -> {enabled}
SHDSL pinouts This section describes the following pinouts on the SHSDL cards:
•
MALC-G.SHDSL-4W-12 pinouts on page 726
•
MALC-SHDSL-48 pinouts on page 727
MALC-G.SHDSL-4W-12 pinouts The 4- wire SHDSL-12 cards use standard RJ-21X pinouts. Table 72 lists the port pinouts. Table 72: 4- wire SHDSL-12 pinouts
726
Pin
Function
Pin
Function
1
Port 1 ring
26
Port 1 tip
2
Port 13 ring
27
Port 13 tip
3
Port 2 ring
28
Port 2 tip
4
Port 14 ring
29
Port 14 tip
5
Port 3 ring
30
Port 3 tip
6
Port 15 ring
31
Port 15 tip
7
Port 4 ring
32
Port 4 tip
8
Port 16 ring
33
Port 16 tip
MALC Hardware Installation Guide
SHDSL pinouts
Table 72: 4- wire SHDSL-12 pinouts (Continued) Pin
Function
Pin
Function
9
Port 5 ring
34
Port 5 tip
10
Port 17 ring
35
Port 17 tip
11
Port 6 ring
36
Port 6 tip
12
Port 18 ring
37
Port 18 tip
13
Port 7 ring
38
Port 7 tip
14
Port 19 ring
39
Port 19 tip
15
Port 8 ring
40
Port 8 tip
16
Port 20 ring
41
Port 20 tip
17
Port 9 ring
42
Port 9 tip
18
Port 21 ring
43
Port 21 tip
19
Port 10 ring
44
Port 10 tip
20
Port 22 ring
45
Port 22 tip
21
Port 11 ring
46
Port 11 tip
22
Port 23 ring
47
Port 23 tip
23
Port 12 ring
48
Port 12 tip
24
Port 24 ring
49
Port 24 tip
25
Not used
50
Not used
MALC-SHDSL-48 pinouts The MALC-SHDSL-48 card uses 96-pin telco pinouts. Table 73 lists the port pinouts. Table 73: 48-port SHDSL card pinouts Port
Signal
Pin
1
Tip
J7-2
Ring
J7-1
Tip
J7-4
Ring
J7-3
Tip
J7-6
Ring
J7-5
2
3
MALC Hardware Installation Guide
727
SHDSL
Table 73: 48-port SHDSL card pinouts (Continued) Port
Signal
Pin
4
Tip
J7-8
Ring
J7-7
Tip
J7-10
Ring
J7-9
Tip
J7-12
Ring
J7-11
Tip
J7-14
Ring
J7-13
Tip
J7-16
Ring
J7-15
Tip
J7-18
Ring
J7-17
Tip
J7-20
Ring
J7-19
Tip
J7-22
Ring
J7-21
Tip
J7-24
Ring
J7-23
Tip
J7-26
Ring
J7-25
Tip
J7-28
Ring
J7-27
Tip
J7-30
Ring
J7-29
Tip
J7-32
Ring
J7-31
Tip
J7-34
Ring
J7-33
Tip
J7-36
Ring
J7-35
5
6
7
8
9
10
11
12
13
14
15
16
17
18
728
MALC Hardware Installation Guide
SHDSL pinouts
Table 73: 48-port SHDSL card pinouts (Continued) Port
Signal
Pin
19
Tip
J7-38
Ring
J7-37
Tip
J7-40
Ring
J7-39
Tip
J7-42
Ring
J7-41
Tip
J7-44
Ring
J7-43
Tip
J7-46
Ring
J7-45
Tip
J7-48
Ring
J7-47
Tip
J7-50
Ring
J7-49
Tip
J7-52
Ring
J7-51
Tip
J7-54
Ring
J7-53
Tip
J7-56
Ring
J7-55
Tip
J7-58
Ring
J7-57
Tip
J7-60
Ring
J7-59
Tip
J7-62
Ring
J7-61
Tip
J7-64
Ring
J7-63
Tip
J7-66
Ring
J7-65
20
21
22
23
24
25
26
27
28
29
30
31
32
33
MALC Hardware Installation Guide
729
SHDSL
Table 73: 48-port SHDSL card pinouts (Continued) Port
Signal
Pin
34
Tip
J7-68
Ring
J7-67
Tip
J7-70
Ring
J7-69
Tip
J7-72
Ring
J7-71
Tip
J7-74
Ring
J7-73
Tip
J7-76
Ring
J7-75
Tip
J7-78
Ring
J7-77
Tip
J7-80
Ring
J7-79
Tip
J7-82
Ring
J7-81
Tip
J7-84
Ring
J7-83
Tip
J7-86
Ring
J7-85
Tip
J7-88
Ring
J7-87
Tip
J7-90
Ring
J7-89
Tip
J7-92
Ring
J7-91
Tip
J7-94
Ring
J7-93
Tip
J7-96
Ring
J7-95
35
36
37
38
39
40
41
42
43
44
45
46
47
48
730
MALC Hardware Installation Guide
Delivering power and data to a Raptor 100 SHDSL-LP
Delivering power and data to a Raptor 100 SHDSL-LP This section describes how to connect the MALC SHDSL-LP card to a Zhone Raptor 100 SHDSL-LP device. The MALC SHDSL-LP card delivers power and data on the same wires. For distances of 10,000 feet (3,048 meters), two pairs of wires delivering power are required. The specifications for the cables delivering power are as follows:
•
2 wires per port
•
26 AWG (0.4 mm) or 24 AWG (0.5 mm)
The LP IN port on the MALC SHDSL-24-LP card provides 12 pairs of wires to deliver power. The power is combined with the data and sent out over the 24 SHDSL ports to downstream Raptor 100 SHDSL-LP devices. One MALC SHDSL-LP card can provide power and data for 6 Raptor 100 devices. The wiring diagram below illustrates the wiring connections for power and data being transmitted over the same pair of wires to a single MALC. To power multiple MALC devices, uses the pinouts described in Table 68 on page 712 to match SHDSL ports to the power pairs. Each set of four pins can power a single Raptor 100. For the SHDSL data connector pinouts, see SHDSL pinouts on page 726. Figure 89: Example power and data delivered over the same wire pairs for one Raptor 100
MALC Hardware Installation Guide
731
SHDSL
732
MALC Hardware Installation Guide
18
EFM-SHDSL This chapter describes the MALC-EFM-SHDSL-24-NTP and the MALC-EFM-SHDSL-24-NTWC cards and how to configure them including:
•
Overview, page 734
•
Create card profiles for SHDSL-24 cards, page 736
•
SHDSL 24 port cable, page 738
•
Power and data connections for SHDSL CPE devices, page 739
•
G.SHDSL port troubleshooting, page 743
•
MTAC testing, page 744
MALC Hardware Installation Guide
733
EFM-SHDSL
Overview The MALC EFM SHDSL cards provide 24 SHDSL bondable ports and support IP and bridging features. The MALC EFM SHDSL cards are
• MALC-EFM-SHDSL-24-NTWC •MALC-EFM-SHDSL-24-NTP These MALC EFM SHDSL cards support Ethernet bonding with a maximum of eight ports per bonded group and a maximum of 24 bonded groups.
EFM NT
EFM NTP
This Ethernet bonding support enables up to three bond groups of eight ports for 8-port EtherXtend devices, up to six bond groups of four ports for 4-port EtherXtend devices, and up to 24 bond groups using one port for each EtherXtend. The MALC EFM SHDSL cards are supported by the MALC-UPLINK-2-FE/GE uplink cards and do not support cell relay. The MALC EFM SHDSL cards provide Ethernet over SHDSL links to Zhone EtherXtend and EFM and N2N CPE devices. The SHDSL links can be added or removed as the network is configured. The card automatically performs load balancing over the links.
The MALC-EFM-SHDSL-24-NTWC card provides network timing reference and wetting current. The network timing reference allows SHDSL lines to use the backplane clock to clock T1/E1 traffic eliminating the need for a clock source at each location where remote devices are installed. The MALC-EFM-SHDSL-24-NTP card provides network timing reference and line power. The timing reference enables the card to use the MALC timing as the SHDSL line clocking. This allows an SHDSL CPE to derive timing from the input of the SHDSL lines. It then can use that timing/clocking to provide timing to other subtended devices.The line power feature can be used to power CPEs such as the SkyZhone to eliminate the need for local power. The power is combined with the data and sent out over the 24 SHDSL ports to downstream CPE devices such as the SkyZhone. One MALC-EFM-SHDSL-24-NTP line card can provide power and data for up to 12 CPE devices. Table 74 describes the bonding specification for the MALC EFM SHDSL bonding cards.
734
MALC Hardware Installation Guide
Overview
Table 74: MALC-EFM-SHDSL-24 bonding specifications Specification
Description
Density
24 ports
Physical interface
Standard telco connector
Size
1 slot
Connectors
One (1) Champ 50-pin telco connector
Line characteristics
ITU G.991.2 SHDSL
Supported line rates
Symmetric rate increments up to 5.7 Mbps
Power consumption
34.0 W nominal (all port initialized, no ports trained) plus 0.79 W additional per active SHDSL interface 43.48 W maximum
SHDSL network scenario Figure 90 shows a typical SHDSL network scenario. Figure 90: SHDSL network illustration
ma 0 6 6 0
SHDSL EtherXtend
Ethernet Network
MALC EFM SHDSL-24 Bonded Card
Ethernet Network
Card profile information for SHDSL-24 cards Each card installed in the system must have a card-profile. Each type of slot card requires different settings in the card-profile.
MALC Hardware Installation Guide
735
EFM-SHDSL
Table 75 describes the card type and software images for the MALC-EFM-SHDSL-24 cards: Table 75: Card type and software image Card
Type
Name of software image
MALC-EFM-SHDSL-24-NTP
5074
malcgshdslbonded.bin
MALC-EFM-SHDSL-24-NTWC
5074
malcgshdslbonded.bin
Use the slots command to display the currently installed cards. zSH> slots Uplinks 1:*MALC RPR GIGE NT (RUNNING) 2: MALC RPR GIGE NT (RUNNING) Cards 7: MALC NTN/EFM GSHDSL Bonded/with NTWC (RUNNING) 9: MALC NTN/EFM GSHDSL Bonded/with NTP (RUNNING)
Create card profiles for SHDSL-24 cards The following example creates a card-profile for a MALC-SHDSL-24 card in shelf 1, slot 13. zSH> card add 1/13/5074 linetype gshdsl
or zSH> new card-profile 1/13/5074 card-profile 1/13/5074 Please provide the following: [q]uit. sw-file-name: -----------> {}: malcgshdslbonded.bin admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {true}: sw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}: hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {unknowntype}:gshdsl card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: maxvpi-maxvci: ----------> {notapplicable}: card-init-string: -------> {}: wetting-current: --------> {disabled}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
736
MALC Hardware Installation Guide
Create card profiles for SHDSL-24 cards
Set wetting current The following example enables the wetting current feature.Wetting current provides 10-15 mA per G.SHDSL line. The default setting for the wetting-current parameter is disabled. Note: Enabling wetting current from ZMS cause the card to reboot.
Setting wetting current for the MALC-EFM-SHDSL-24-NTWC card To enable this feature, change the wetting-current parameter to standard. zSH> update card-profile 1/13/5074 card-profile 1/13/5074 Please provide the following: [q]uit. sw-file-name: -----------> {malcgshdslbonded.bin}: admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {true}: sw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}: hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {gshdsl}: card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: maxvpi-maxvci: ----------> {notapplicable}: card-init-string: -------> {}: wetting-current: --------> {disabled}:standard .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Switch clocking source Switching clocking for the MALC-EFM-SHDSL-24-NT/NTP cards The default clock source setting is ntr-local-osc.To change the default setting for the NTR setting, enter the parameter ntr-refck-8khz. The clock source will switch from the local oscillator to the backplane 8Kz reference clock. This affects all ports on the card. Enter ntr-refck-8khz in the efmCuPmeNtr parameter field. zSH> update pme-profile 1-13-1-0/shdsl pme-profile 1-13-1-0/shdsl Please provide the following: [q]uit.
MALC Hardware Installation Guide
737
EFM-SHDSL
efmCuPmeAdminSubType: -----------> {ieee2basetlr}: efmCuPmeAdminProfile: -----------> {0}: efmCuPAFRemoteDiscoveryCode: ----> {}: efmCuPmeThreshLineAtn: ----------> {0}: efmCuPmeThreshSnrMgn: -----------> {0}: efmCuPmeLineAtnCrossingEnable: --> {false}: efmCuPmeSnrMgnCrossingEnable: ---> {false}: efmCuPmeDeviceFaultEnable: ------> {false}: efmCuPmeConfigInitFailEnable: ---> {false}: efmCuPmeProtocolInitFailEnable: -> {false}: efmCuPme2BProfileDescr: ---------> {}: efmCuPme2BRegion: ---------------> {region1}: efmCuPme2BDataRate: -------------> {0}: efmCuPme2BPower: ----------------> {0}: efmCuPme2BConstellation: --------> {adaptive}: efmCuPme2BProfileRowStatus: -----> {active}: efmCuPmeNtr: --------------------> {ntr-local-osc}: ntr-refck-8khz .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
SHDSL 24 port cable The EFM-SHDSL-24 cards use a 24-port cable. Table 76 lists the pinouts. The MALC-EFM-SHDSL-24 cards use standard RJ-21X pinouts. Table 76 lists the port pinouts. Table 76: MALC-EFM-SHDSL-24 pinouts
738
Port
Pin Ring
Pin Tip
1
1
26
2
2
27
3
3
28
4
4
29
5
5
30
6
6
31
7
7
32
8
8
33
9
9
34
10
10
35
11
11
36
12
12
37
MALC Hardware Installation Guide
Power and data connections for SHDSL CPE devices
Table 76: MALC-EFM-SHDSL-24 pinouts (Continued) Port
Pin Ring
Pin Tip
13
13
38
14
14
39
15
15
40
16
16
41
17
17
42
18
18
43
19
19
44
20
20
45
21
21
46
22
22
47
23
23
48
24
24
49
Note: Pins 25 and 50 are not used.
Power and data connections for SHDSL CPE devices This section describes the power connections on the MALC-EFM-SHDSL-24-NTP card that enable power to be delivered to Zhone SHDSL CPE devices and includes:
•
Wiring connections for power and data on page 739
•
Send power down the data line on page 740
•
G.SHDSL line power removal on page 741
Wiring connections for power and data The MALC-EFM-SHDSL-24-NTP card delivers power and data on the same wires. To deliver power and data to the CPE, two pairs of wires (four wires total) are required. The specifications for the cables delivering power are as follows:
•
2 wires per port
•
26 AWG (0.4 mm) or 24 AWG (0.5 mm)
MALC Hardware Installation Guide
739
EFM-SHDSL
Figure 91 illustrates the wiring connections for power and data being transmitted over the same pair of wires to a single CPE port. To power multiple CPE devices, use the pinouts described in Table 76 to match SHDSL ports to the power pairs. Each set of four pins can power a single SHDSL CPE. The LP IN port on the MALC-EFM-SHDSL-24-NTP card provides 12 pairs of wires to deliver power. The power is combined with the data and sent out over the 24 SHDSL ports to downstream CPE devices. One MALC-EFM-SHDSL-24-NTP card can provide power and data for up to 12 SHDSL CPE devices. Figure 91: Example power and data delivered over the same wire pairs
MALC SHDSL EFM NTP
CPE
SHDSL EFM NTP
Send power down the data line The line power feature is set in the adminstatus parameter of if-translate. The adminstatus default is up. This means that voltage is set to be sent down the data line. This voltage comes from an external power supply as shown in Figure 91. If the external power supply is not connected or turned off, voltage will simply not be supplied to the data line. However, the data stream will continue to be sent. To view the status of the adminstatus parameter enter: zSH> get if-translate 1-13-1-0/shdsl if-translate 1-13-1-0/shdsl ifIndex: -----------> {1421} shelf: -------------> {1} slot: --------------> {13} port: --------------> {1} subport: -----------> {0}
740
MALC Hardware Installation Guide
Power and data connections for SHDSL CPE devices
type: --------------> adminstatus: -------> physical-flag: -----> iftype-extension: --> ifName: ------------> redundancy-param1: ->
{shdsl} {up} {true} {none} {1-13-1-0} {0}
If someone needs to work on the line, voltage is removed from that line by setting adminstatus to maintenance. Maintenance mode stops the data stream and the voltage. Note: When a port is set to maintenance mode, any MTAC testing that may be running on any port is turned off. Maintenance mode always has top priority. zSH> update if-translate 1-13-1-0/shdsl if-translate 1-13-1-0/shdsl ifIndex: -----------> {1421} shelf: -------------> {1} slot: --------------> {13} port: --------------> {1} subport: -----------> {0} type: --------------> {shdsl} adminstatus: -------> {up} maintenance physical-flag: -----> {true} iftype-extension: --> {none} ifName: ------------> {1-13-1-0} redundancy-param1: -> {0}
Note: The SHDSL line power feature requires that two lines are used together and both must be set to up in the adminstatus field. The lines do not need to be adjacent.
G.SHDSL line power removal The line power provided by the MALC-EFM-SHDSL-24 NTP card is set in the adminstatus parameter of the if-translate profile for the SHDSL port. The default for adminstatus is set to up. This means that voltage is set to be sent down the data line. To view the default settings for the if-translate profile, enter get if-translate shelf-slot-port-subport/type: zSH> get if-translate 1-5-2-0/shdsl if-translate 1-5-2-0/shdsl ifIndex: -----------> {249} shelf: -------------> {1} slot: --------------> {5} port: --------------> {2} subport: -----------> {0} type: --------------> {shdsl}
MALC Hardware Installation Guide
741
EFM-SHDSL
adminstatus: -------> physical-flag: -----> iftype-extension: --> ifName: ------------> redundancy-param1: -> description-index: ->
{up} {true} {none} {1-5-2-0} {0} {-303174163}
If work needs to be performed on the line and you need to remove voltage from the line, you must change the adminstatus parameter from up to maintenance. Note: The SHDSL line power feature requires that two lines are used together. The adminstatus parameter for both lines must match. To change the adminstatus parameter from up to maintenance, enter update if-translate shelf-slot-port-subport/type: zSH> update if-translate 1-5-1-0/shdsl if-translate 1-5-1-0/shdsl Please provide the following: [q]uit. ifIndex: -----------> {247}: shelf: -------------> {1}: slot: --------------> {5}: port: --------------> {1}: subport: -----------> {0}: type: --------------> {shdsl}: adminstatus: -------> {up}: maintenance physical-flag: -----> {true}: iftype-extension: --> {none}: ifName: ------------> {1-5-1-0}: redundancy-param1: -> {0}: description-index: -> {-303174163}: Invalid entry: description-index range: [0 to 2147483647] description-index: -> {-303174163}: 0 .................... Save changes? [s]ave, [c]hange or [q]uit: s Setting the adminStatus to maintenance will result with the termination of the MTAC test. Continue? [y]es or [n]o: y Record updated.
Setting the adminstatus parameter to maintenance stops both the voltage and the data flow. Note: When a port is set to maintenance, all MTAC testing running on any port is turned off. The maintenance setting always has top priority.
742
MALC Hardware Installation Guide
G.SHDSL port troubleshooting
G.SHDSL port troubleshooting The MALC provides the following commands for G.SHDSL lines you can use to bring a line up or down for testing or retraining:
•
port up shelf-slot-port-subport/type
•
port down shelf-slot-port-subport/type
•
port bounce shelf-slot-port-subport/type
Enter port up to change the administrative state of a G.SHDSL line from down to up: zSH> port up 1-1-1-0/shdsl 1-1-1-0/shdsl set to admin state UP
Enter port down to change the administrative state of a G.SHDSL line from up to down: zSH> port down 1-1-1-0/shdsl 1-1-1-0/shdsl set to admin state DOWN
Bringing the G.SHDSL line down and up could be useful for troubleshooting, forcing a retrain, or tracing a wire. Enter port bounce to bring the administrative state of the G.SHDSL line down then up: zSH> port bounce 1-1-1-0/shdsl 1-1-1-0/shdsl set to admin state DOWN 1-1-1-0/shdsl set to admin state UP
To view the status of the G.SHDSL lines, enter showline 1 1: zSH> showline 1 1 Search in progress ......... -----------------------------------------------------------------------shelf = 1, slot = 1, line type = EFMBOND line 1-12 NONE NONE NONE NONE NONE NONE NONE NONE NONE NONE NONE NONE 13-24 NONE NONE NONE NONE NONE NONE NONE NONE NONE NONE NONE NONE 25-36 ACT ACT ACT -----------------------------------------------------------------------shelf = 1, slot = 1, line type = SHDSL line 1-12 OOS ACT ACT ACT ACT ACT ACT ACT ACT ACT ACT ACT 13-24 ACT ACT ACT ACT ACT ACT ACT ACT ACT ACT ACT ACT -----------------------------------------------------------------------shelf = 1, slot = 1, line type = IPOBRIDGE line 1-12 NONE NONE NONE NONE NONE OOS -----------------------------------------------------------------------shelf = 1, slot = 1, line type = ETHERNET line 1-12 ACT -----------------------------------------------------------------------shelf = 1, slot = 1, line type = RPR line
MALC Hardware Installation Guide
743
EFM-SHDSL
1-12
ACT
MTAC testing The line power feature on the MALC-EFM-SHDSL-24-NTP card is mutually exclusive with MTAC testing and takes precedence over MTAC. When the line power feature is being used, MTAC testing cannot occur.To run MTAC testing, no ports on the MALC-EFM-SHDSL-24-NTP card can be in maintenance mode.
744
MALC Hardware Installation Guide
19 VDSL2
This chapter describes the MALC VDSL2-17A card and explains how to configure it. VDSL2-17A supports the VDSL2 12a profile in the 1.15.x release. 17a will be added in a later release. VDSL2 specifies eight profiles, based on upstream and downstream bandwidth. Profile 12a incorporates longer reach capabilities. 17a incorporates longer reach with greater transmission rates/ This chapter includes:
•
Overview, page 746
•
Configuring VDSL2 interfaces, page 749
•
VDSL2 24 port card pinouts, page 753
MALC Hardware Installation Guide
745
VDSL2
Overview active fault pwr fail
Very high bit rate DSL (VDSL) transmits high speed data over short reaches of twisted-pair copper wire. The shorter the distance, the faster the connection rate. The VDSL2-17A-24 is a single-slot 24-port VDSL2 subscriber line card, which provides increased bandwidth (up to 100 Mbps downstream and 50 Mbps upstream over short distances) to accommodate video applications. Loop access for metallic test functions is provided. The VDSL2-17A-24 card can be used with the Zhone VDSL2 CPE devices. This architecture allows VDSL2 users to access the maximum bandwidth available over twisted-pair, copper phone lines.
1 - 24
ma0525
VDSL2 17A
Table 77: MALC-VDSL2-17A-24 card specifications
746
Specification
Value
Density
24 ports
Physical interfaces
One (1) RJ-21X Champ 50-pin connector
Line characteristics
Discrete multi-tone (DMT) modulation
Redundancy
None
Nominal line rate
Up to 50 Mbps downstream and 20 Mbps upstream
MALC Hardware Installation Guide
Reed-Solomon interleaved forward error correction (FEC)
Overview
Table 77: MALC-VDSL2-17A-24 card specifications (Continued) Specification
Value
Power consumption
35W nominal plus 0.3W per active port 48 W maximum
Compliance
ITU-T G.993.2 VDSL 2
Creating card-profiles for VDSL2-17A-24 cards Each card installed in the system must have a card-profile. Each type of slot card requires different settings in the card-profile. Tip: You can specify the name of the software image for a card in a card-profile or a type-module. Each card of a particular type can share a single type-module. Settings in type-modules can be overridden by settings in card-profiles. VDSL2-24 cards on the MALC have the following types and software images: Table 78: MALC-VDSL2-24 card type and software image Card
Type
Name of software image
VDSL2-17A-24
5067
malcvdsl17a.bin
The following example creates a card-profile for a VDSL2--17A-24 card in shelf 1, slot 7: zSH> card add 1/7/5026
or zSH> new card-profile 1/7/5026 shelf/slot/type Please provide the following: [q]uit. sw-file-name: -----------> {}: malcvdsl17a.bin admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {true}: sw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}: hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {unknowntype}: card-atm-configuration: -> {notapplicable}:
MALC Hardware Installation Guide
747
VDSL2
card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created.
Verifying the slot card installation After you save the card-profile record, the slot card in that slot resets and the begins downloading their software image from the flash card. This could take a few moments. When the card has finished loading, a log message similar to the following is displayed (if logging is enabled): zSH> Card in slot slot-number changed state to RUNNING
You can also use the slots command and specify the slot number of the card to view the state of the card. For example: zSH> slots 7 Type : Card Version : EEPROM Version : Serial # : CLEI Code : Card-Profile ID : Shelf : Slot : ROM Version : Software Version: State : Mode : Heartbeat check : Longest hbeat : Fault reset : Uptime :
MALC VDSL2 1 1 1010001 No CLEI 1/7/5067 1 7 development MALC CAN 1.14.2.310 RUNNING FUNCTIONAL enabled 8593 enabled 22 minutes
To view the status of all the cards, use the slots command without any arguments: zSH> slots 1:*MALC GIGE (RUNNING) 2: MALC GIGE (RUNNING) 5: MALC NTN/EFM GSHDSL Bonded/with NTP (RUNNING) 6: MALC ADSL 48 ANNEX A/M Bonded (RUNNING) 7: MALC POTS 48/with Packet Voice (RUNNING) 7: MALC VDSL2 (RUNNING)
748
MALC Hardware Installation Guide
Configuring VDSL2 interfaces
Configuring VDSL2 interfaces The following table summarizes how to configure a VDSL2 interfaces on the MALC: Action
Command
Configure the VDSL2 settings. See Configuring VDSL2 interfaces on page 749.
update vdsl-config index/vdsl Where index is of the form shelf-slot-port-subport or a user-defined string. update vdsl-co-profile index/vdsl Where index is of the form shelf-slot-port-subport or a user-defined string. Specifies downstream line speed. update vdsl-cpe-profile index/vdsl Where index is of the form shelf-slot-port-subport or a user-defined string. Specifies upstream threshold values.
Configuring VDSL2 interfaces 1
Update the vdsl-config profile. Make sure the mode parameter is set to vtu-o. Also set the maximum constellation (us-max-const) to 64 Mbps on both ends of the VDSL connection.
zSH> update vdsl-config 1-7-1-0/vdsl transmit-mode: -----------> {autonegotiatemode} line-type: ---------------> {fastonly} vdsl2-profile: -----------> {g993-2-12a} vdsl-mode: ---------------> {standard} applicable-standard: -----> {ansi} band-plan: ---------------> {bandplan998} band-plan-fx: ------------> {3750} deploy-scenario: ---------> {fttcab} band-opt-usage: ----------> {unused} pbo-electrical-override: -> {256} auto-mode-crtrn: ---------> {optimize-us} network-timing-ref: ------> {disable} adsl-band-mode: ----------> {allowed} adsl-band-mode-end-freq: -> {1104} selt-echo-measure-time: --> {50} selt-noise-measure-time: -> {50} selt-agc: ----------------> {0} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
2
Verify the VDSL2 interface is active: zSH> get if-translate 1-7-1-0/vdsl Please provide the following: [q]uit. ifIndex: ----------> {222}: shelf: ------------> {1}: slot: -------------> {7}:
MALC Hardware Installation Guide
749
VDSL2
port: -------------> subport: ----------> type: -------------> adminstatus: ------> physical-flag: ----> iftype-extension: -> ifName: -----------> redundancy-param1: ->
3
{1}: {0}: {vdsl}: {up}: {true}: {none}: {1-7-1-0}: {0}:
Update the downstream interface to specify a line speed: zSH> update vdsl-co-config 1-4-19-0/vdsl Please provide the following: [q]uit. fast-max-rate: ----------------> {200000}: fast-min-rate: ----------------> {0}: interleave-max-rate: ----------> {200000}: interleave-min-rate: ----------> {0}: rate-mode: --------------------> {adapt-at-init}: max-power: --------------------> {58}: max-snr-mgn: ------------------> {127}: min-snr-mgn: ------------------> {0}: target-snr-mgn: ---------------> {24}: max-interleave-delay: ---------> {80}: thresh15min-lofs: -------------> {0}: thresh15min-loss: -------------> {0}: thresh15min-lptrs: ------------> {0}: thresh15min-lols: -------------> {0}: thresh15min-ess: --------------> {0}: thresh15min-sess: -------------> {0}: thresh15min-uass: -------------> {0}: thresh1day-lofs: --------------> {0}: thresh1day-loss: --------------> {0}: thresh1day-lprs: --------------> {0}: thresh1day-lols: --------------> {0}: thresh1day-ess: ---------------> {0}: thresh1day-sess: --------------> {0}: thresh1day-uass: --------------> {0}: init-failure: -----------------> {false}: thresh1day-init-failure: ------> {false}: rate-ratio: -------------------> {50}: trellis: ----------------------> {disable}: pbo-control: ------------------> {auto}: pbo-level: --------------------> {0}: psd-template: -----------------> {ansi-fftcab-m1}: target-interleave-burst: ------> {5}: max-fast-fec: -----------------> {0}: max-aggregate-tx-pwr: ---------> {unlimited}: max-psd: ----------------------> {-1}: psd-shape: --------------------> {region-a-psd}: virtual-noise-snr-mode: -------> {mode1}: erasure-detection-fast: -------> {enable}: erasure-detection-interleave: -> {enable}: ghs-a43-tone-pwr: -------------> {default}:
750
MALC Hardware Installation Guide
Configuring VDSL2 interfaces
ghs-b43-tone-pwr: -------------> ghs-a43c-tone-pwr: ------------> ghs-v43-tone-pwr: -------------> ghs-a43-tone-pwr-max-level: ---> ghs-b43-tone-pwr-max-level: ---> ghs-a43c-tone-pwr-max-level: --> ghs-v43-tone-pwr-max-level: ---> rs-coding: --------------------> .................... Save changes? [s]ave, [c]hange or Record updated.
4
{default}: {default}: {default}: {-40}: {-40}: {-40}: {-40}: {disable}: [q]uit: s
There is typically no need to change the settings for the upstream interface, unless you want to configure trap thresholds. If your setup requires it, use the update command: zSH> update vdsl-cpe-config 1-4-19-0/vdsl Please provide the following: [q]uit. fast-max-rate: ----------------> {200000}: fast-min-rate: ----------------> {0}: interleave-max-rate: ----------> {200000}: interleave-min-rate: ----------> {0}: rate-mode: --------------------> {adapt-at-init}: max-power: --------------------> {58}: max-snr-mgn: ------------------> {127}: min-snr-mgn: ------------------> {0}: target-snr-margin: ------------> {24}: max-interleave-delay: ---------> {80}: rate-ratio: -------------------> {0}: trellis: ----------------------> {disable}: pbo-control: ------------------> {auto}: pbo-level: --------------------> {0}: psd-template: -----------------> {ansi-fftex-m1}: target-interleave-burst: ------> {5}: max-fast-fec: -----------------> {0}: max-aggregate-tx-pwr: ---------> {unlimited}: max-psd: ----------------------> {-1}: psd-shape: --------------------> {region-a-psd}: virtual-noise-snr-mode: -------> {mode1}: erasure-detection-fast: -------> {enable}: erasure-detection-interleave: -> {enable}: rs-coding: --------------------> {disable}: pbo-psd-template: -------------> {ansi-a}: pbo-psd-param-a1: -------------> {4000}: pbo-psd-param-a2: -------------> {4000}: pbo-psd-param-b1: -------------> {4000}: pbo-psd-param-b2: -------------> {4000}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
5
Display VDSL2 status. Use the dslstat command to displays the status of the interface:
MALC Hardware Installation Guide
751
VDSL2
zSH> dslstat 1-7-1-0/adsl General Stats: ------------AdminStatus.....................................UP LineStatus....................................DATA Line uptime (DD:HH:MM:SS)...............0:00:25:24 DslUpLineRate (bitsPerSec)................31992000 DslDownLineRate (bitsPerSec)..............63984000 DslMaxAttainableUpLineRate (bitsPerSec)...44144000 DslMaxAttainableDownLineRate (bitsPerSec).65536000 Out Octets.................................1525000 Out Pkts/Cells.............................1525000 Out Discards.....................................0 Out Errors.......................................0 In Octets...................................507825 In Pkts/Cells...............................507825 In Discards......................................0 In Errors........................................0 DSL Physical Stats: -----------------Actual Transmission connection standard......VDSL2 Vdsl2CurrentProfile......................g993-2-12a DslLineSnrMgn (tenths dB)........................86 DslLineAtn (tenths dB)...........................30 DslCurrOutputPwr (tenths dB)....................139 LOFS..............................................0 LOLS..............................................0 LOSS..............................................0 ESS...............................................0 CRC Errors........................................0 Inits.............................................2 near-end statstics: -----------------Loss of Frame Seconds.............................0 Loss of Signal Seconds............................0 Loss of Link Seconds..............................0 Severely Errored Seconds..........................0 Unavailable Seconds................................0 far-end statstics: ----------------Loss of Frame Seconds.............................0 Loss of Signal Seconds............................0 Loss of Link Seconds..............................0 Severely Errored Seconds..........................0 Unavailable Seconds..............................26 Loss of Power (dying gasps).......................0 XTUC PHY Stats: -------------serialNumber...................................... vendorId..........................................
752
MALC Hardware Installation Guide
VDSL2 24 port card pinouts
versionNumber...............................2.62.4 curSnrMargin (tenths dB)........................86 currAtn (tenths dB).............................30 currStatus...............................NO DEFECT currOutputPwr (tenths dB)......................139 currAttainableRate (bitsPerSec)...........65536000 currLineRate (bitsPerSec).................67424000 XTUC CHAN Stats: ---------------interleaveDelay (tenths milliseconds).............5 crcBlockLength (bytes)........................14592 currTxRate (bitsPerSec)....................63984000 XTUR PHY Stats: --------------serialNumber....................................... vendorId........................................... versionNumber...................................... curSnrMargin (tenths dB)........................164 currAtn (tenths dB)..............................18 currOutputPwr (tenths dB).......................120 currAttainableRate (bitsPerSec)............44144000 currLineRate (bitsPerSec)..................34176000 XTUR CHAN Stats: ---------------interleaveDelay (tenths milliseconds).............0 crcBlockLength (bytes)........................13440 currTxRate (bitsPerSec)....................31992000
VDSL2 24 port card pinouts VDSL2 24 port cards use standard RJ-21X pinouts. Table 79 lists the port pinouts. Table 79: VDSL2 24 port card pinouts Pin
Function
Pin
Function
1
Channel 1 ring
26
Channel 1 tip
2
Channel 2 ring
27
Channel 2 tip
3
Channel 3 ring
28
Channel 3 tip
4
Channel 4 ring
29
Channel 4 tip
5
Channel 5 ring
30
Channel 5 tip
6
Channel 6 ring
31
Channel 6 tip
7
Channel 7 ring
32
Channel 7 tip
MALC Hardware Installation Guide
753
VDSL2
Table 79: VDSL2 24 port card pinouts (Continued)
754
Pin
Function
Pin
Function
8
Channel 8 ring
33
Channel 8 tip
9
Channel 9 ring
34
Channel 9 tip
10
Channel 10 ring
35
Channel 10 tip
11
Channel 11 ring
36
Channel 11 tip
12
Channel 12 ring
37
Channel 12 tip
13
Channel 13 ring
38
Channel 13 tip
14
Channel 14 ring
39
Channel 14 tip
15
Channel 15 ring
40
Channel 15 tip
16
Channel 16 ring
41
Channel 16 tip
17
Channel 17 ring
42
Channel 17 tip
18
Channel 18 ring
43
Channel 18 tip
19
Channel 19 ring
44
Channel 19 tip
20
Channel 20 ring
45
Channel 20 tip
21
Channel 21 ring
46
Channel 21 tip
22
Channel 22 ring
47
Channel 22 tip
23
Channel 23 ring
48
Channel 23 tip
24
Channel 24 ring
49
Channel 24 tip
25
Not used
50
Not used
MALC Hardware Installation Guide
20 POTS
This chapter describes the MALC POTS card and explains how to configure it. It includes:
•
24-port POTS card (MALC-POTS-GBL-TDM/PKT-24 and MALC-EBS-TDM/PKT-24), page 756
•
48-port POTS card, page 758
•
Configuring POTS cards, page 759
•
Configuring POTS ports, page 778
•
POTs card port pinouts, page 783
Overview The following cards provide POTS interfaces:
•
POTS 24. See 24-port POTS card (MALC-POTS-GBL-TDM/PKT-24 and MALC-EBS-TDM/PKT-24) on page 756
•
POTS 48. See 48-port POTS card on page 758.
Please note that POTS interfaces are also available in combination with ADSL and are described in ADSL on page 619.
MALC Hardware Installation Guide
755
POTS
24-port POTS card (MALC-POTS-GBL-TDM/PKT-24 and MALC-EBS-TDM/PKT-24)
There are two models of 24-port POTS cards: active fault pwr fail
•MALC-POTS-GBL-TDM/PKT-24 supports traditional TDM voice (using GR303 or V5.2 protocols) as well as packetized voice for use in a VoIP network. This card supports loop start, ground start, dial pulse (using SIP PLAR or SIP), and provides echo cancellation. It communicates with the Uplink card over the MALC packet bus and the control bus. POTS voice traffic is packetized on the card and sent to a standards-based voice gateway, such as the MALC voice gateway card. There the voice traffic is converted back to TDM and forwarded it to a class 5 switch. It also supports international metering.
1-2 4 POTS GLOBAL 24
•MALC-EBS-TDM/PKT-24 (P-Phone card)
ma0521
is the enhance version of the global POTs card, it supports P-phone feature within the SLMS system. The P-phone is a signaling standard developed by Bell North Research (now Nortel) officially called Electronic Business Set (EBS).
Table 80: MALC POTS 24 cards specifications
756
Specification
Value
Size
1 slot
Density
24 ports
Physical interfaces
One (1) RJ-21X Champ 50-pin connector
Redundancy
None
Nominal line rate
80 kbps 5 ppm
Longitudinal balance:
500 Hz to 40 kHz: greater than 55 dB
MALC Hardware Installation Guide
40 kHz to 1 MHz: roll-off -20 dB per decade
Overview
Table 80: MALC POTS 24 cards specifications (Continued) Specification
Value
Input return loss
greater than 20 dB, 10 kHz to 25 kHz roll-off 20 dB per decade to 1 kHz and 250 kHz
Free-run line rate (Stratum 4) if timing reference is lost
80 kbps 32 ppm
Metallic test functions
Look-out tests
Ring generation
Ring voltage supplied through Ring Voltage bus Ring Voltage Generator located on MT/Ringer/Alarm card External generation possible through Ring Generator access port on MTAC/Ring card. Note that P-Phone card does not support ring generation.
Power consumption
45 watts
MALC Hardware Installation Guide
757
POTS
48-port POTS card
The MALC supports the 48 port POTS card:
•MALC-POTS-TDM/PKT-48 supports traditional TDM voice as well as packetized voice for use in a VoIP network. This card supports loop start and provides echo cancellation. It communicates with the Uplink card over the MALC packet bus and the control bus. POTS voice traffic is packetized on the card and sent to a standards-based voice gateway, such as the MALC voice gateway card. There the voice traffic is converted back to TDM and forwarded it to a class 5 switch. Note that pulse dialing is an optional feature for 48-port POTS cards, by default it is disabled.
Table 81: MALC POTS 48 cards specifications Specification
Density
Size
1 slot
Density
48 ports
Physical interfaces
One (1) 96-pin telco connector
Line characteristics
2 wire POTS, Loop Start
Metallic test functions
Look-out tests
Ring generation
Ring voltage supplied through Ring Voltage bus Ring Voltage Generator located on MT/Ringer/Alarm card External generation possible through Ring Generator access port on MTAC/Ring card.
758
MALC Hardware Installation Guide
Redundancy
None
Power consumption
32 watts maximum
Configuring POTS cards
Configuring POTS cards This section describes how to configure POTS cards for TDM or packet voice. It includes:
•
Configuring 24-port POTS cards on page 760
•
Configuring 48-port POTS cards on page 774
•
Verifying the slot card installation on page 777
Each card installed in the system must have a card-profile. Each type of slot card requires different settings in the card-profile. Tip: You can specify the name of the software image for a card in a card-profile or a type-module. Each card of a particular type can share a single type-module. Settings in type-modules can be overridden by settings in card-profiles. The POTS slot cards on the MALC have the following types and software images: Table 82: MALC card types Card
Type
Name of software image
MALC-POTS-GBL-TDM/PKT-24
5049
malculcs.bin
MALC-EBS-TDM/PKT-24
5049
malculcs.bin
MALC-POTS-TDM/PKT-48
5047
malcpots48.bin
MALC Hardware Installation Guide
759
POTS
Configuring 24-port POTS cards This section describes how to configure global POTS card and P-phone card for TDM or packet voice. It includes:
•
Configuring a 24-port global POTS card for TDM voice on page 760
•
Configuring a 24-port global POTS card for packet voice on page 763
•
Configuring a P-phone card for TDM voice on page 764
•
Configuring a P-phone card for packet voice on page 769
Global POTS can be configured for POTS or packet voice support in the card profile. POTS is used if the call is being routed out a TDM interface. Packet voice is used if POTS calls are to be routed through a MALC voice gateway card. P-phone card is specially designed for the end users use the EBS phones (P-phones) and attendant console (key sets). P-phone card supports both TDM voice and packet voice. The following table describes the parameters in the card-profile for the 24-port POTS card: Parameter
Description
sw-file-name
Software image for the card. The MALC-ISDN-2B1Q-24, MALC-ISDN4B3T-24, MALC-POTS-GBL-TDM/PKT-24, and MALC-EBS-TDM/PKT-24 cards all use the same image. Values: malculcs.bin
card-line-type
The type of calls supported on this card. Values: pots TDM POTS. pots-pv POTS over packet voice. ebs TDM P-phone. ebs-pv P-phone over packet voice.
Configuring a 24-port global POTS card for TDM voice The following example configure a MALC-POTS-GBL-TDM/PKT-24 card for TDM voice through V5.2: 1
View the type of card installed in the system: zSH> slots Uplinks 1: MALC RPR GIGE (RUNNING) Cards 9: MALC XDSL 48/with Packet Voice POTS (RUNNING)
760
MALC Hardware Installation Guide
Configuring POTS cards
16: MALC ULCS/POTS (NOT_PROV) 20: MALC MTAC (RUNNING)
The POTS card in slot 16 is a MALC-POTS-GBL-TDM/PKT-24 card, and it supports TDM voice only. 2
Creates a card-profile for a MALC-POTS-GBL-TDM/PKT-24 card in shelf 1, slot 16: zsh> card add 1/16/5049 linetype pots
or zSH> new card-profile 1/16/5049 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {}: malculcs.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {0}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: pots indicates TDM voice only card-atm-configuration: -> {notapplicable} card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
After you save the card-profile record, the slot card in that slot resets and the begins downloading their software image from the flash card. This could take a few moments. When the card has finished loading, a log message similar to the following is displayed (if logging is enabled): zSH> Card in slot slot-number changed state to RUNNING
3
Use the slots command and specify the slot number of the card to view the state of the card: zSH> slots 16 Type Sub-Type Card Version EEPROM Version Serial # CLEI Code Card-Profile ID Shelf Slot
: : : : : : : : :
MALC ULCS POTS 1 1 7778850 No CLEI 1/16/5049 1 16
MALC Hardware Installation Guide
761
POTS
ROM Version : Software Version: State : Mode : Heartbeat check : Longest hbeat : Fault reset : Uptime :
4
development release 1.12 RUNNING FUNCTIONAL enabled 6118 enabled 2 days, 20 hours, 32 minutes
If you need to modify the signaling and ring frequency, update the analog-fxs-cfg-profile for each interface. For example:
zSH> update analog-fxs-cfg-profile 1-16-1-0/voicefxs signal-type: ----> {fxsloopstart} fxsloopstart | fxsgroundstart ring-frequency: -> {ringfrequency20} ring-back: ------> {off} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
5
To create a POTS to V5.2 connection, enter the following command. Refer to the CLI Reference Guide for a complete description of the command options and syntax.
zSH> voice add pots 1-16-3-0/voicefxs v52 1/22 type pots cpath 1 Created subscriber-voice 1/21/381 Created subscriber-voice-pots 761 Created v52-user-port 1/22/2 Created subscriber-voice-v52 762
6
To view the connection:
zSH> voice show v52 1/22 type pots INPUT: profile type: subscriber-voice-v52 logical address: IfName: one UserId: 22 IsdnBChannelId: 0 profile address: 762 subscriber-voice INFO: voice-connection-type = POTSTOV52 voice-endpoint1-addr-index = 761 voice-endpoint2-addr-index = 762 voice-admin-status = Enabled subscriber-voice addr: subId: 1 LGId: 21 subVoiceId: 381 MATCHING: profile type: subscriber-voice-pots logical address: LGId: 585 PotsNumber: 1 profile address: 761
762
MALC Hardware Installation Guide
Configuring POTS cards
Configuring a 24-port global POTS card for packet voice The following example configure a MALC-POTS-GBL-TDM/PKT-24 card for packet voice: 1
View the type of card installed in the system: zSH> slots Uplinks 1: MALC RPR GIGE (RUNNING) Cards 9: MALC XDSL 48/with Packet Voice POTS (RUNNING) 16: MALC ULCS/POTS with Packet Voice(NOT_PROV) 20: MALC MTAC (RUNNING)
The POTS card in slot 16 is a MALC-POTS-GBL-TDM/PKT-24 card, and it supports packet voice only. 2
Creates a card-profile for the MALC-POTS-GBL-TDM/PKT-24 card in shelf 1, slot 16, and specify the card-line-type to packet voice service: zsh> card add 1/16/5049 linetype pots
or zSH> new card-profile 1/16/5049 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {}: malculcs.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {0}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: pots-pv indicates packet voice only card-atm-configuration: -> {notapplicable} card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
3
If you need to modify the signaling and ring frequency, update the analog-fxs-cfg-profile for each interface. For example:
zSH> update analog-fxs-cfg-profile 1-16-1-0/voicefxs signal-type: ----> {fxsloopstart} fxsloopstart | fxsgroundstart ring-frequency: -> {ringfrequency20} ring-back: ------> {off} .................... Save changes? [s]ave, [c]hange or [q]uit: s
MALC Hardware Installation Guide
763
POTS
Record updated.
4
To create a VOIP to POTS connection, enter the following command. Refer to the CLI Reference Guide for a complete description of the command options and syntax.
zSH> voice add pots 1-16-3-0/voicefxs voip ethernet3/ip dn 5551001 name 5551001 pw password enable Created subscriber-voice 1/6/8 Created subscriber-voice-pots 15 Created subscriber-voice-voip 16 Interface 1-16-3-0/voicefxs's admin status is set to ENABLED
5
To view the connection:
zSH> voice show voip ethernet3/ip dn 5551001 INPUT: profile type: subscriber-voice-voip logical address: LGId: 154 EndPtIdx: 16 profile address: 16 subscriber-voice INFO: voice-connection-type = VOIPTOPOTS voice-endpoint1-addr-index = 16 voice-endpoint2-addr-index = 15 voice-admin-status = Enabled subscriber-voice addr: subId: 1 LGId: 6 subVoiceId: 8 MATCHING: profile type: subscriber-voice-pots logical address: LGId: 149 PotsNumber: 1 profile address: 15
Configuring a P-phone card for TDM voice The P-phone card (MALC-EBS-TDM/PKT-24) can provide the TDM voice through GR 303. Figure 92: P-phone support TDM voice GR303 IG with EBS support
Class 5 switch MALC with P-phone card EBSs
The following example configure a MALC-EBS-TDM/PKT-24 card for TDM voice service through GR303:
764
MALC Hardware Installation Guide
Configuring POTS cards
1
To configure the MALC with voicegateway card: a
Create an uplink card card-profile for the MALC-UPLINK-2-FE/GE with the card-line-type parameter of rpr-t1-gr303.
b
Make sure all T1s on uplinks are up as by default they are down.
c
Update ds1-profile to looptiming on all T1s.
d
Use the update system-clock-profile command to modify the system-clock-eligibility to true and system-clock-weight to 9. zsh> update system-clock-profile 1-1-2-0/ds1 system-clock-profile 1-1-2-0/ds1 Please provide the following: [q]uit. system-clock-eligibility: -> {false}: true system-clock-weight: ------> {5}: 9
e
Check clkmgrshow. zsh> clkmgrshow Primary system clock is 1/1/1/0 : T1 Secondary system clock is 1/1/2/0: T1
f
Use the new gr303-interface-group command to create a GR-303 interface group on the VG card.
zsh> new gr303-interface-group 1 gr303-interface-group 1 Please provide the following: [q]uit. name-id: -----------------------> {}: zhone switch-type: -------------------> {}: norteldms100 adminStatus: -------------------> {}: inservice working-mode: ------------------> {}: passive ctrlChannel: control-channel-t303: ----------> {700} control-channel-t396: ----------> {14700} sapi-0-max-outstanding-frames: -> {7} sapi-0-n-200: ------------------> {3} sapi-0-t-200: ------------------> {150} sapi-0-t-203: ------------------> {30} sapi-0-pps-mode: ---------------> {notinhibited} sapi-1-max-outstanding-frames: -> {7} sapi-1-n-200: ----> {3} sapi-1-t-200: ----> {150} sapi-1-t-203: ----> {30} sapi-1-pps-mode: -> {notinhibited} ds1LM has 32 elements. Display [a]ll, [n]one, a [s]ubset, or [q]uit? ...
s
Refer to Configuring a GR-303 interface on page 177 for the overal configuration procedure. g
Use the new atm-traf-descr command to create a new ATM traffic descriptor with a unique index for a voice connection.
MALC Hardware Installation Guide
765
POTS
h
Use new ip-interface-record vg/ip and new ip-unnumbered-record commands to create an unnumbered interface for VoIP. zSH> new ip-interface-record ebs/ip vpi: ---------------> {0}: vci: ---------------> {0}: rdindex: -----------> {1}: dhcp: --------------> {none} addr: --------------> {10.235.9.1} netmask: -----------> {255.255.255.0} bcastaddr: ---------> {10.235.9.255} destaddr: ----------> {0.0.0.0}: farendaddr: --------> {0.0.0.0}: mru: ---------------> {1500}: reasmmaxsize: ------> {65535}: ingressfiltername: -> {}: egressfiltername: --> {}: pointtopoint: ------> {no}: mcastenabled: ------> {yes}: ipfwdenabled: ------> {yes}: mcastfwdenabled: ---> {yes}: natenabled: --------> {no}: bcastenabled: ------> {yes}: ingressfilterid: ---> {0}: egressfilterid: ----> {0}: ipaddrdynamic: -----> {static}: dhcpserverenable: --> {false}: subnetgroup: -------> {0}: unnumberedindex: ---> {0}: mcastcontrollist: --> {}: vlanid: ------------> {0}: maxVideoStreams: ---> {0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s zSH> new ip-unnumbered-record 1 ipUnnumberedInterfaceName: -> { }: ebs/ip .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
i
Use the voicegateway add command to create the voicegateway host using the available physical interface or slot number of the voicegateway card and traffic descriptor. zSH> voicegateway add -v 13 td 172.25.39.2
j
Check voice gateways.
zSH> vg show 14 Rd/Address Interface Group T Host Address ------------------------------------------------------------------1 10.235.9.1 1-14-1-0-aal5proxy-0-32 0/32 0 S 10.235.9.2
766
MALC Hardware Installation Guide
Configuring POTS cards
k
View the type of card installed in the system:
zSH> slots Uplinks 1: MALC RPR GIGE (RUNNING) Cards 9: MALC XDSL 48/with Packet Voice POTS (RUNNING) 12: MALC ULCS/EBS (NOT_PROV) 20: MALC MTAC (RUNNING)
The POTS card in slot 12 is a MALC-EBS-TDM/PKT-24 card and it supports TDM voice only. 2
Configuration of the P-phone card: a
Creates a card-profile for the MALC-EBS-TDM/PKT-24 card in shelf 1, slot 12, and specify the card-line-type to P-phone voice service: zsh> card add 1/12/5049 linetype ebs
or zSH> new card-profile 1/12/5049 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {}: malculcs.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {0}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: ebs indicates p-phone voice only card-atm-configuration: -> {notapplicable} card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
b
Use the voice add command to add the VoIP to GR-303 voice connection between the voice gateway card and the switch for P-phone/ EBS packet voice.
zSH> voice add voip voip-1-14/ip dn 7311801 name 7311801 plar 172.24.200.52 reg 0 gr303 2/1801 ebs sub 7311801
MALC Hardware Installation Guide
767
POTS
c
If you want to delete a P-phone to GR303 connection on the VG MALC, enter the following command. zSH>
d
voice delete voip voip-1-14/ip dn 7311801
Create a GR303 interface group for P-phone:
zsh> new gr303-interface-group 1 gr303-interface-group 1 Please provide the following: [q]uit. name-id: -----------------------> {}: zhone switch-type: -------------------> {}: norteldms100 adminStatus: -------------------> {}: inservice working-mode: ------------------> {}: passive ctrlChannel: control-channel-t303: ----------> {700} control-channel-t396: ----------> {14700} sapi-0-max-outstanding-frames: -> {7} sapi-0-n-200: ------------------> {3} sapi-0-t-200: ------------------> {150} sapi-0-t-203: ------------------> {30} sapi-0-pps-mode: ---------------> {notinhibited} sapi-1-max-outstanding-frames: -> {7} sapi-1-n-200: ----> {3} sapi-1-t-200: ----> {150} sapi-1-t-203: ----> {30} sapi-1-pps-mode: -> {notinhibited} ds1LM has 32 elements. Display [a]ll, [n]one, a [s]ubset, or [q]uit? ...
s
For the rest of command refer to Configuring a GR-303 interface on page 177. e
zSH>
voice add ebs 1-12-1-0/voiceebs gr303 1/1801
f zSH>
To create a P-phone to GR303 connection, enter the following command. Refer to the CLI Reference Guide for a complete description of the command options and syntax.
If you want to delete a P-phone to GR303 connection, enter the following command.
voice delete ebs 1-12-1-0/voiceebs
3
Create EBS voice connections in DMS 100 class 5 switch.
4
To view all the subscriber voice GR 303:
zSH> list subscriber-voice-gr303 subscriber-voice-gr303 246 ...
5
To view the detail information for the subscriber voice GR303 index 246:
zSH> get subscriber-voice-gr303
768
MALC Hardware Installation Guide
246
Configuring POTS cards
subscriber-voice-gr303 246 voice-GR303-ig-name: -> {zhone} voice-GR303-ig-crv: --> {1801}
6
To view the detail information for the voice status (GR303 only):
zSH> voice status Port term state destination Call state hook ring ESA ------------------------------------ --- -------------- ----------------1-12-1-0/voiceebs UP GR303:IG-1:CRV-1801 No call OFF NoRing N/A 1-12-2-0/voiceebs UP GR303:IG-1:CRV-1802 No call OFF NoRing N/A 1-12-3-0/voiceebs UP GR303:IG-1:CRV-1803 No call OFF NoRing N/A
Configuring a P-phone card for packet voice The P-phone card (MALC-EBS-TDM/PKT-24) can provide the packet voice through GR 303. Figure 93: P-phone support packet voice GR303 IG with EBS support
Class 5 switch Packetized P-phone over Ethernet using SIP-PAR
MALC with voicegateway card
Remote MALC with P-phone card EBSs
Configure a P-phone card for packet voice, perform the following tasks: 1
To configure the MALC with voicegateway card: a
Connect the physical T1 lines between the voicegateway card ports and the class 5 switch. This example uses a MALC-VG-T1/E1-32-2S card.
b
Create an uplink card card-profile for the MALC-UPLINK-2-FE/GE with the card-line-type parameter of rpr-t1-gr303. This uplink card on the MALC is connected to the same type uplink card on the remote MALC.
c
Create the voicegateway card card-profile with the card-line-type parameter of ds1. This reboots the voicegateway card.
MALC Hardware Installation Guide
769
POTS
d
Make sure all T1s are up on VG as by default they are down.
e
Use the update system-clock-profile command to update the system-clock-eligibility to true and system-clock-weight to 9. zsh> update system-clock-profile 1-1-2-0/ds1 system-clock-profile 1-1-2-0/ds1 Please provide the following: [q]uit. system-clock-eligibility: -> {false}: true system-clock-weight: ------> {5}: 9
f
Check clkmgrshow. zsh> clkmgrshow Primary system clock is 1/1/1/0 : T1 Secondary system clock is 1/1/2/0: T1
g
Use the new gr303-interface-group command to create a GR-303 interface group on the VG card.
zsh> new gr303-interface-group 1 gr303-interface-group 1 Please provide the following: [q]uit. name-id: -----------------------> {}: zhone switch-type: -------------------> {}: norteldms100 adminStatus: -------------------> {}: inservice working-mode: ------------------> {}: passive ctrlChannel: control-channel-t303: ----------> {700} control-channel-t396: ----------> {14700} sapi-0-max-outstanding-frames: -> {7} sapi-0-n-200: ------------------> {3} sapi-0-t-200: ------------------> {150} sapi-0-t-203: ------------------> {30} sapi-0-pps-mode: ---------------> {notinhibited} sapi-1-max-outstanding-frames: -> {7} sapi-1-n-200: ----> {3} sapi-1-t-200: ----> {150} sapi-1-t-203: ----> {30} sapi-1-pps-mode: -> {notinhibited} ds1LM has 32 elements. Display [a]ll, [n]one, a [s]ubset, or [q]uit? ...
s
Refer to Configuring a GR-303 interface on page 177 for the overall configuration procedure. h
Create the entry of the profile voip-server-entry 255/255 with zhoneVoipServerAddr as 0.0.0.0 for the SIP PLAR voice connections. zSH> new voip-server-entry 255/255 Please provide the following: [q]uit. zhoneVoipServerAddrType: ----------> zhoneVoipServerAddr: --------------> zhoneVoipServerUdpPortNumber: -----> zhoneVoipServerId: ---------------->
770
MALC Hardware Installation Guide
{ipv4}: {}: 0.0.0.0 {5060}: {generic}:
Configuring POTS cards
protocol: -------------------------> {sip}: sendCallProceedingTone: -----------> {false}: rtcpEnabled: ----------------------> {false}: rtcpPacketInterval: ---------------> {5000}: interdigitTimeOut: ----------------> {10}: ipTos: ----------------------------> {0}: systemDomainName: -----------------> {}: expires-invite-value: -------------> {3600}: expires-register-value: -----------> {3600}: expires-header-method: ------------> {register}: session-timer: --------------------> {off}: session-expiration: ---------------> {180}: session-min-session-expiration: ---> {180}: session-caller-request-timer: -----> {no}: session-callee-request-timer: -----> {no}: session-caller-specify-refresher: -> {omit}: session-callee-specify-refresher: -> {uac}: dtmf-mode: ------------------------> {rfc2833}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
i
Use the new atm-traf-descr command to create a new ATM traffic descriptor with a unique index for a voice connection.
j
Use new ip-interface-record vg/ip and new ip-unnumbered-record commands to create an unnumbered interface for VoIP. zSH> new ip-interface-record ebs/ip vpi: ---------------> {0}: vci: ---------------> {0}: rdindex: -----------> {1}: dhcp: --------------> {none} addr: --------------> {10.235.9.1} netmask: -----------> {255.255.255.0} bcastaddr: ---------> {10.235.9.255} destaddr: ----------> {0.0.0.0}: farendaddr: --------> {0.0.0.0}: mru: ---------------> {1500}: reasmmaxsize: ------> {65535}: ingressfiltername: -> {}: egressfiltername: --> {}: pointtopoint: ------> {no}: mcastenabled: ------> {yes}: ipfwdenabled: ------> {yes}: mcastfwdenabled: ---> {yes}: natenabled: --------> {no}: bcastenabled: ------> {yes}: ingressfilterid: ---> {0}: egressfilterid: ----> {0}: ipaddrdynamic: -----> {static}: dhcpserverenable: --> {false}: subnetgroup: -------> {0}: unnumberedindex: ---> {0}:
MALC Hardware Installation Guide
771
POTS
mcastcontrollist: --> {}: vlanid: ------------> {0}: maxVideoStreams: ---> {0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s zSH> new ip-unnumbered-record 1 ipUnnumberedInterfaceName: -> { }: ebs/ip .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
k
Use the voicegateway add command to create the voicegateway host using the available physical interface or slot number of the voicegateway card and traffic descriptor. zSH> voicegateway add -v 14 td 172.25.39.2
l
Check voice gateways.
zSH> vg show 14 Rd/Address Interface Group T Host Address ------------------------------------------------------------------1 10.235.9.1 1-14-1-0-aal5proxy-0-32 0/32 0 S 10.235.9.2
m Use the voice add command to add the VoIP to GR-303 voice connection between the voice gateway card and the switch for P-phone/ EBS packet voice. zSH> voice add voip voip-1-14/ip dn 7311801 name 7311801 plar 172.24.200.52 reg 0 gr303 2/1801 ebs sub 7311801
n
If you want to delete a P-phone to GR303 connection on the VG MALC, enter the following command. zSH>
2
voice delete voip voip-1-14/ip dn 7311801
Configuration in the remote MALC with P-phone card: a
Create a uplink card card-profile for the MALC-UPLINK-2-FE/GE on the remote MALC.
b
View the type of card installed in the system:
zSH> slots Uplinks 1: MALC RPR GIGE (RUNNING) Cards 9: MALC XDSL 48/with Packet Voice POTS (RUNNING) 11: MALC ULCS/EBS with Packt Voice(NOT_PROV) 20: MALC MTAC (RUNNING)
The POTS card in slot 11 is a MALC-EBS-TDM/PKT-24 card and it supports packet voice only.
772
MALC Hardware Installation Guide
Configuring POTS cards
c
Creates a card-profile for the MALC-EBS-TDM/PKT-24 card in shelf 1, slot 11, and specify the card-line-type to packet voice service (ebs-pv): zSH> card add 1/11/5049 linetype ebs-pv
or zSH> new card-profile 1/11/5049 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {}: malculcs.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {0}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: ebs-pv indicates plar packet voice card-atm-configuration: -> {notapplicable} card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
d
In the remote MALC, use the voice add command to add the SIP-PLAR voice connection between the remote subtended MALC and the MALC with VG.
zSH> voice add ebs 1-11-1-0/voiceebs voip ethernet1-1/ip dn 7311801 name 7311801 plar 10.235.9.2 reg 0 sub 7311801 enable
e zSH>
If you want to delete a P-phone to GR303 connection on the remote MALC, enter the following command.
voice delete ebs 1-11-1-0/voiceebs
3
Create EBS voice connections in DMS 100 class 5 switch.
4
To view the detail information for the voice status (PLAR):
zSH> voice status Port term state destination Call state hook ring ESA -------------------------------------------------------------------------------1-11-1-0/voiceebs UP VOIO:84:VOIP EndPtIdx-354 No call OFF NoRing OFF 1-11-2-0/voiceebs
UP
VOIO:84:VOIP EndPtIdx-404
No call OFF NoRing OFF
1-11-3-0/voiceebs
UP
VOIO:84:VOIP EndPtIdx-406
No call OFF NoRing OFF
MALC Hardware Installation Guide
773
POTS
Configuring 48-port POTS cards This section describes how to configure 48-port POTS card for TDM or packet voice. It includes:
•
Configuring a 48-port POTS card for TDM voice on page 774
•
Configuring a 48-port POTS card for packet voice on page 775
•
Configuring a 48-port POTS card for dial pulse on page 776
MALC cards with 48 POTS ports can be configured to operate in TDM mode or in packet voice mode, depending on the model of card installed. This requires setting the card-line-type in the card-profile. The following table describes the parameters in the card-profile for the 48-port POTS card: Parameter
Description
sw-file-name
Software image for the card. Values: malcpots48.bin
card-line-type
The type of calls supported on this card. Values: pots TDM POTS. pots-pv POTS over packet voice.
card-init-string
Enable or disable dial pulse for the card. Values: empty string By default, the dial pulse feature is disabled, thus there is no value displayed for the card-init-string. dialpulse The dial pulse feature is enabled. Note that, the 48-port POTS card must be rebooted for dial pulse to take effect.
Configuring a 48-port POTS card for TDM voice The following example configure a MALC-POTS-TDM/PKT-48 card for TDM voice: 1
View the type of card installed in the system: zSH> slots Uplinks 1: MALC RPR GIGE (RUNNING) Cards 7: MALC XDSL 48/with Packet Voice POTS (RUNNING) 8: MALC POTS 48/with Packet Voice (NOT_PROV) 20: MALC MTAC (RUNNING)
774
MALC Hardware Installation Guide
Configuring POTS cards
The POTS card in slot 8 is a POTS-TDM-48 card, which supports TDM voice only. 2
Create a card-profile for the card in slot 8:
zsh> card add 1/8/5047 linetype pots
or zSH> new card-profile 1/8/5047 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {}: malcpots48.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {0}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: pots indicates TDM voice only card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Configuring a 48-port POTS card for packet voice The following example configure a MALC-POTS-TDM/PKT-48 card for packet voice: 1
View the type of card installed in the system: zSH> slots Uplinks 1: MALC RPR GIGE (RUNNING) Cards 5: MALC XDSL 48/with Packet Voice POTS (RUNNING) 6: MALC POTS 48/with Packet Voice (NOT_PROV) 20: MALC MTAC (RUNNING)
The POTS card in slot 6 is a MALC-POTS-TDM/PKT-48 card, which supports packet voice. 2
Create a card-profile for the MALC-POTS-TDM/PKT-48 card in slot 6:
zsh> card add 1/6/5047 linetype pots-pv
or zSH> new card-profile 1/6/5047 shelf/slot/type Please provide the following: [q]uit.
MALC Hardware Installation Guide
775
POTS
sw-file-name: ---------> {}: malcpots48.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {0}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: pots-pv indicates packet voice card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Configuring a 48-port POTS card for dial pulse The following example configure a MALC-POTS-TDM/PKT-48 card for dial pulse: 1
Enable dial pulse in card-profile for the MALC-POTS-TDM/PKT-48 card in slot 6:
zSH> update card-profile 1/6/5047 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {malcpots48.bin}: admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {enable}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {0}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {pots-pv}: card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: maxvpi-maxvci: ----------> {notapplicable}: card-init-string: -------> {}: dialpulse enable the dialpulse .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
2
Reboot the MALC-POTS-TDM/PKT-48 card for dial pulse to take effect. zSH> slotreboot 6 Do you want to reboot slot 6? (yes or no) [no] yes Do you want to exit from this request? (yes or no) [yes] no
776
MALC Hardware Installation Guide
Configuring POTS cards
Are you sure? (yes or no) [no] yes JUN 19 17:56:25: critical: 1/1/1027: rebootserver: * * * * Slot Reboot : type = 2, shelf = 1, slot = 6
3
Change the pulse-inter-digit-timer, min-make-pulse-width, and min-break-pulse-width parameters in the voice-system with the recommended values. zSH> update voice-system 0 voice-system 0 Please provide the following: [q]uit. hookflash-min-timer: -------> {100}: hookflash-max-timer: -------> {1550}: partial-dial-timeout: ------> {16}: critical-dial-timeout: -----> {4}: busy-tone-timeout: ---------> {30}: dial-tone-timeout: ---------> {16}: msg-wait-tone-timeout: -----> {16}: offhook-warn-tone-timeout: -> {0}: ringing-timeout: -----------> {180}: ringback-timeout: ----------> {180}: reorder-tone-timeout: ------> {30}: stutter-tone-timeout: ------> {16}: server-max-timer: ----------> {20}: config-max1: ---------------> {5}: config-max2: ---------------> {7}: max1-enable: ---------------> {true}: max2-enable: ---------------> {true}: max-waiting-delay: ---------> {600}: disconnection-wait-timer: --> {15}: disconnection-min-timer: ---> {15}: disconnection-max-timer: ---> {600}: max-retransmit-timer: ------> {4}: init-retransmit-timer: -----> {200}: keep-alive-timer: ----------> {60}: no-response-timer: ---------> {30}: call-wait-max-repeat: ------> {2}: call-wait-delay: -----------> {10}: pulse-inter-digit-timer: ---> {100}: 240 min-make-pulse-width: ------> {25}: 15 max-make-pulse-width: ------> {55}: min-break-pulse-width: -----> {45}: 35 max-break-pulse-width: -----> {75}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Verifying the slot card installation After you save the card-profile record, the slot card in that slot resets and the begins downloading their software image from the flash card. This could take a few moments.
MALC Hardware Installation Guide
777
POTS
When the card has finished loading, a log message similar to the following is displayed (if logging is enabled): zSH> Card in slot slot-number changed state to RUNNING
Configuring POTS ports This section describes how to configure POTS ports. It includes:
•
Configuring POTS settings on page 779
•
Configuring signal type and ring frequency on page 781
The following table summarizes how to configure a POTS interfaces on the MALC: Action
Command
Configure the POTS gain settings. See Configuring POTS settings on page 779.
update analog-if-cfg-profile index/voicefxs Where index is of the form shelf-slot-port-subport or a user-defined string. For typical applications, the settings in this profile do not need to be modified.
Configure the POTS signaling. See Configuring signal type and ring frequency on page 781.
778
MALC Hardware Installation Guide
update analog-fxs-cfg-profile index/voicefxs For typical applications, the settings in this profile do not need to be modified.
Configuring POTS ports
Configuring POTS settings Modify the following parameters in the analog-if-cfg-profile if you need to change the gain settings for each voice line:
Parameter
Description
if-cfg-impedence
Specifies the terminating impedance of analog voice interfaces. Values: ohms600complex 600 Ohms + 2.16uF ohms900complex 00 Ohms + 2.16uF Default: ohms600complex
if-cfg-receive-tlp
The receive TLP is the signal level to the customer premises equipment (CPE). The receive signal range is +3 dB to -9 dB. A positive number adds gain, a negative number adds loss to the analog signal after decoding from PCM. For example, a receive TLP setting of -6 dB will generate a voice signal at -6 dB level. Values: fxsrtlpn9db fxsrtlpn8db fxsrtlpn7db fxsrtlpn6db fxsrtlpn5db fxsrtlpn4db fxsrtlpn3db (not supported on the POTS 900 card) fxsrtlpn2db (not supported on the POTS 900 card) fxsrtlpn1db fxsrtlp0db fxsrtlp1db fxsrtlp2db fxsrtlp3db rtlpnummeric Default: fxsrtlpn6db
MALC Hardware Installation Guide
779
POTS
Parameter
Description
if-cfg-transmit-tlp
The transmit TLP is the signal level from the customer premises equipment (CPE). The transmit signal range is +9 dB to -3 dB. A positive number adds loss, a negative number adds gain to the analog signal before encoding to PCM. For example, a transmit TLP setting of +3 dB will set a loss of 3 dB to generate a 0 dB PCM signal. Values: fxsTtlp9db (not supported on the POTS 900 card) fxsTtlp8db (not supported on the POTS 900 card) fxsTtlp7db fxsTtlp6db fxsTtlp5db fxsTtlp4db fxsTtlp3db fxsTtlp2db fxsTtlp1db fxsTtlp0db fxsTtlpN1db fxsTtlpN2db fxsTtlpN3db Default: fxsTtlp0db
if-cfg-pcm-encoding
Line encoding. Values: alaw for E1. mulaw for T1.
if-cfg-receive-tlpNum
Receive Transmission Level Point (RTLP) settings control the amount gain or loss added to the incoming signal after it is decoded to analog. To increase the signal level set the RTLP setting to higher values. The default is 0 dB. Values: -160 to 85 (in tenths of dB) Default: 0 dB
if-cfg-transmit-tlpNum
Transmit Transmission Level Point (TTLP) controls the amount of gain or loss added to a voice signal before it is encoded to digital PCM. To increase the signal level, reduce the TTLP setting to lower value. Values: -175 to 70 (in tenths of dB) Default: 0 dB
If you need to modify the gain settings, update the analog-if-cfg-profile for each interface. For example: zSH> update analog-if-cfg-profile 1-3-1-0/voicefxs Please provide the following: (q=quit) if-cfg-impedence: ------------>{ohms600complex}: modify if required if-cfg-receive-tlp: ---------->{fxsrtlp0db}: modify if required
780
MALC Hardware Installation Guide
Configuring POTS ports
if-cfg-transmit-tlp: --------->{fxsttlp0db}: modify if required if-cfg-trunk-conditioning: --->{idle}: if-maintenance-mode: --->{off}: if-cfg-pcm-encoding: --->{mulaw}: alaw | mulaw if-cfg-receive-tlpNum: -----> {0}: if-cfg-transmit-tlpNum: ----> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Configuring signal type and ring frequency Modify the following parameters in the analog-fxs-cfg-profile if you need to change signalling type and ring frequency for each voice line: Parameter
Description
signal-type
The method by which an off-hook condition is indicated. Values: fxsloopstart fxsgroundstart Ground start is only supported on ULCS cards. Default: fxsloopstart
ring-frequency
Rate in cycles per second (Hertz) at which polarity reversal occurs on ringing. Values: ringfrequency20 ringfrequency25 ringfrequency30 ringfrequency50 Default: ringfrequency20
ring-back
The ring back is requested if this variable is set to on. Values: on off Default: off
If you need to modify the signaling and ring frequency, update the analog-fxs-cfg-profile for each interface. For example: zSH> update analog-fxs-cfg-profile 1-3-1-0/voicefxs signal-type: ----> {fxsloopstart} ring-frequency: -> {ringfrequency20} modify if required ring-back: ------> {off} modify if required .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
MALC Hardware Installation Guide
781
POTS
Enabling Dial Pulse on POTS and POTS combination cards The ability to enable or disable dial pulse on POTs cards and POTs combination cards is by setting the card-init-string in the line card-profile. If “dialpulse” is entered in the card-init-string paramet dial pulse is enable. Otherwise dial pulse is not enabled.
To enable Dial Pulse on POTS and POTS combination cards 1
Login, locate the appropriate card and find the proper identifier (using the slots command, then list card-profile)
2
Update the card profile for the appropriate identifier (in this case card-profile 1/6/5047)
3
For the card-init-string parameter, enter dialpulse zSH> update card-profile 1/6/5047 card-profile 1/6/5047 Please provide the following: [q]uit. sw-file-name: -----------> admin-status: -----------> upgrade-sw-file-name: ---> upgrade-vers: -----------> admin-status-enable: ----> sw-upgrade-admin: -------> sw-enable: --------------> sw-upgrade-enable: ------> card-group-id: ----------> hold-active: ------------> weight: -----------------> card-line-type: ---------> card-atm-configuration: -> card-line-voltage: ------> maxvpi-maxvci: ----------> card-init-string: -------> wetting-current: --------> zSH>
4
{malcpots48.bin} {operational} {} {} {enable} {reloadcurrrev} {true} {false} {0} {false} {nopreference} {pots-pv} {notapplicable} {not-used} {notapplicable} {dialpulse} {disabled}
Reboot the card for dial pulse to take effect. zSH> slotreboot 6 Do you want to reboot slot 6? (yes or no) [no] yes Do you want to exit from this request? (yes or no) [yes] no Are you sure? (yes or no) [no] yes JUN 19 17:56:25: critical: 1/1/1027: rebootserver: * * * * Slot Reboot : type = 2, shelf = 1, slot = 6
782
MALC Hardware Installation Guide
POTs card port pinouts
POTs card port pinouts This section describes the POTS cards port pinouts.
•
24-port POTS cards pinouts on page 783
•
48-port POTS card pinouts on page 784
24-port POTS cards pinouts The MALC-POTS-GBL-TDM/PKT-24 card and MALC-EBS-TDM/PKT-24 card use standard RJ-21X pinouts. Figure 94 shows the location of pinouts on the POTS 24 card connector.
active fault pwr fail
Figure 94: 24-port POTS card connector pinouts
5
5
1-2 4
Table 83 lists the port pinouts. Table 83: 24-port POTS card pinouts Pin
Function
Pin
Function
1
Channel 1 ring
26
Channel 1 tip
2
Channel 2 ring
27
Channel 2 tip
3
Channel 3 ring
28
Channel 3 tip
4
Channel 4 ring
29
Channel 4 tip
5
Channel 5 ring
30
Channel 5 tip
6
Channel 6 ring
31
Channel 6 tip
7
Channel 7 ring
32
Channel 7 tip
8
Channel 8 ring
33
Channel 8 tip
9
Channel 9 ring
34
Channel 9 tip
MALC Hardware Installation Guide
783
POTS
Table 83: 24-port POTS card pinouts (Continued) Pin
Function
Pin
Function
10
Channel 10 ring
35
Channel 10 tip
11
Channel 11 ring
36
Channel 11 tip
12
Channel 12 ring
37
Channel 12 tip
13
Channel 13 ring
38
Channel 13 tip
14
Channel 14 ring
39
Channel 14 tip
15
Channel 15 ring
40
Channel 15 tip
16
Channel 16 ring
41
Channel 16 tip
17
Channel 17 ring
42
Channel 17 tip
18
Channel 18 ring
43
Channel 18 tip
19
Channel 19 ring
44
Channel 19 tip
20
Channel 20 ring
45
Channel 20 tip
21
Channel 21 ring
46
Channel 21 tip
22
Channel 22 ring
47
Channel 22 tip
23
Channel 23 ring
48
Channel 23 tip
24
Channel 24 ring
49
Channel 24 tip
25
Not used
50
Not used
48-port POTS card pinouts Table 84 lists the MALC-POTS-TDM/PKT-4 card pinouts. Table 84: 48-port POTS card pinouts Port
Signal
Pin
1
Tip
J5-2
Ring
J5-1
Tip
J5-4
Ring
J5-3
Tip
J5-6
Ring
J5-5
Tip
J5-8
Ring
J5-7
2
3
4
784
MALC Hardware Installation Guide
POTs card port pinouts
Table 84: 48-port POTS card pinouts (Continued) Port
Signal
Pin
5
Tip
J5-10
Ring
J5-9
Tip
J5-12
Ring
J5-11
Tip
J5-14
Ring
J5-13
Tip
J5-16
Ring
J5-15
Tip
J5-18
Ring
J5-17
Tip
J5-20
Ring
J5-19
Tip
J5-22
Ring
J5-21
Tip
J5-24
Ring
J5-23
Tip
J5-26
Ring
J5-25
Tip
J5-28
Ring
J5-27
Tip
J5-30
Ring
J5-29
Tip
J5-32
Ring
J5-31
Tip
J5-34
Ring
J5-33
Tip
J5-36
Ring
J5-35
Tip
J5-38
Ring
J5-37
6
7
8
9
10
11
12
13
14
15
16
17
18
19
MALC Hardware Installation Guide
785
POTS
Table 84: 48-port POTS card pinouts (Continued) Port
Signal
Pin
20
Tip
J5-40
Ring
J5-39
Tip
J5-42
Ring
J5-41
Tip
J5-44
Ring
J5-43
Tip
J5-46
Ring
J5-45
Tip
J5-48
Ring
J5-47
Tip
J5-50
Ring
J5-49
Tip
J5-52
Ring
J5-51
Tip
J5-54
Ring
J5-53
Tip
J5-56
Ring
J5-55
Tip
J5-58
Ring
J5-57
Tip
J5-60
Ring
J5-59
Tip
J5-62
Ring
J5-61
Tip
J5-64
Ring
J5-63
Tip
J5-66
Ring
J5-65
Tip
J5-68
Ring
J5-67
21
22
23
24
25
26
27
28
29
30
31
32
33
34
786
MALC Hardware Installation Guide
POTs card port pinouts
Table 84: 48-port POTS card pinouts (Continued) Port
Signal
Pin
35
Tip
J5-70
Ring
J5-69
Tip
J5-72
Ring
J5-71
Tip
J5-74
Ring
J5-73
Tip
J5-76
Ring
J5-75
Tip
J5-78
Ring
J5-77
Tip
J5-80
Ring
J5-79
Tip
J5-82
Ring
J5-81
Tip
J5-84
Ring
J5-83
Tip
J5-86
Ring
J5-85
Tip
J5-88
Ring
J5-87
Tip
J5-90
Ring
J5-89
Tip
J5-92
Ring
J5-91
Tip
J5-94
Ring
J5-93
Tip
J5-96
Ring
J5-95
36
37
38
39
40
41
42
43
44
45
46
47
48
MALC Hardware Installation Guide
787
POTS
788
MALC Hardware Installation Guide
21
VOICE GATEWAY This chapter describes the MALC Voice Gateway card (VG-T1/E1-32-2S) and explains how to configure it. It includes:
•
Overview, page 789
•
Adding a voice gateway card, page 791
•
Adding a redundant voice gateway card, page 792
•
Pinouts, page 794 Note: For information on the slot cards supported with the voice gateway card, see Packet voice support on page 32.
Overview The voice gateway card is a 2-slot card and is available in 8 or 32 port configurations for flexible TDM access off of Resilient Packet Ring (RPR), IP or ATM networks. This card supports up to 32 T1/E1s for concurrent voice calls (128 protected 1+1 T1/E1 ports or four cards per chassis). For ATM voice networks, the voice gateway card supports Broadband Loop Emulation Service (BLES) to either GR-303 or V5.2 signals as well as Emulation Loop Control Protocol (ELCP) to V5.2 signals on the local exchange switch. For IP access, the voice gateway card supports Session Initiation Protocol Private Line Automatic Ringdown (SIP-PLAR) to either GR-303 or V5.2 signals on the local switch. Both VoIP and VoATM voice connections can be run exclusively or concurrently on the same MALC system and voice gateway card. A MALC system also supports simultaneous voice gateway connections and subscriber line connections that use the same uplink card. However, subscriber line
MALC Hardware Installation Guide
789
Voice Gateway
POTS or ISDN connections cannot be directly connected to the voice gateway card on the same MALC system. The following connection types are supported.
•
Voice over ATM:
•
–
BLES to GR-303 or V5.2
–
ELCP to V5.2
Voice over IP: SIP-PLAR to GR-303 or V5.2
Table 85: Voice gateway card specifications Specification
Description
Size
2 slots
Density
8, or 32 ports
Connectors
One (1) Champ 128-pin telco connector Ethernet connector
Standards supported
ITU-T G.703
Supported line rates
1.544 MHz, 2.048 MHz
Metallic test function
Look-out test Metallic loopback relay
Redundancy
Card redundancy
Power
55 watts
General
100/120 ohm balance
ITU-T G.704
Support for 8 IG over 32 T1/E1 facilities 960 call capacity for concurrent off-hook DS0s
790
MALC Hardware Installation Guide
Adding a voice gateway card
Table 85: Voice gateway card specifications (Continued) Specification
Description
ISDN
Allows ISDN telephony over packet networks
VoIP
SIP PLAR support for VoIP:
• • • • • •
G.711, G.729a, and G.726 encoding
• • •
Configurable static or dynamic jitter buffer
Silence suppression Echo cancellation (48ms tail echo) Distributed SIP stack and RTP on every card CAS and CCS Auto detect fax/modem calls and switch to G.711, disable echo cancel/silence suppression
RFC2833 CAS transmission Configurable packet payload size
Adding a voice gateway card To add a voice gateway card to the MALC, physically install the voice gateway card in the desired slot location. Voice gateway cards are double-slot cards that can be inserted into any slot except the first slot. After the card is installed, create a card profile. Note: When a voicegateway card is used, the MALC system clock must receive timing from a DS1 interface on the voicegateway card. Refer to System clocking on page 205 for details system clock settings. This example adds the voice gateway card to slot 3 and specifies the binary file malct1e132vg.bin (for T1 connections). For E1 connections, specify the malct1e132vgv52.bin file. zsh> card add 1/3/5006 linetype ds1
or zSH> new card-profile 1/3/5040 sw-file-name: -----------> {} malct1e132vg.bin admin-status: -----------> {operational} upgrade-sw-file-name: ---> {} upgrade-vers: -----------> {} admin-status-enable: ----> {enable} sw-upgrade-admin: -------> {reloadcurrrev} sw-enable: --------------> {false} true sw-upgrade-enable: ------> {false}
MALC Hardware Installation Guide
791
Voice Gateway
card-group-id: ----------> {0} hold-active: ------------> {false} weight: -----------------> {nopreference} card-line-type: ---------> {unknowntype} ds1 card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Adding a redundant voice gateway card The voice gateway card supports card-level redundancy. Configuring redundant voice gateway cards requires 2 separate voice gateway cards with a redundant TDM cable between Telco connectors and a standard Category 5 Ethernet crossover cable of 1 foot or less between the peer connectors. Caution: Both cards in a redundant pair must be running the same software version. Caution: Both cards in a redundant pair must be the same type. Only a 32 port card can backup another 32 port card, and only a 8 port card can backup another 8 port card. You can have 8 port cards and 32 port cards in the same chassis, but they can not be the redundant of each other. Although it may be helpful to place the redundant voice gateway cards close to each other, redundant voice gateway cards do not need to be in contiguous slot locations. Figure 95 shows redundant voice gateway cards with intercard cabling installed.
792
MALC Hardware Installation Guide
Adding a redundant voice gateway card
active fault pwr fail
active fault pwr fail
Figure 95: Redundant voice gateway card cabling
8X T1 E1
8X
T D M
T1 E1
ma0503
T D M
Configuring redundant voice gateway cards Caution: You must configure redundant physical interfaces on both the active and standby cards. This applies to all redundant cards. In addition, you must manually keep the configuration of the physical interfaces on the active and standby cards in sync. Note: When configuring the redundant voice gateway card, the settings in the card-profile for the both cards must be identical. To add a redundant card to the system: 1
Verify that active card has been configured with the same card-group-id that is to be used for the standby card.
2
Install a second voice gateway card in an adjacent slot.
3
Create a card-profile for the second card:
zsh> card add 1/3/5040 linetype ds1
or
MALC Hardware Installation Guide
793
Voice Gateway
zSH> new card-profile 1/3/5040 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {}: malct1e132vg.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {1}: enter the same redundancy group ID as the primary card hold-active: ----------> {false}: weight: ---------------> {nopreference}: assign a weight, if desired card-line-type: -------> {unknowntype}: ds1 card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Once the card-profile has been saved, the standby card comes up and the configuration and routing tables from the primary card are copied over.
Removing a redundant voice gateway card To remove a redundant voice card, first put the redundant card into reset hold mode, then disconnect the Ethernet cable used for the redundant connection between the active and redundant voice gateway cards. Then, pull the redundant voice gateway card out of the chassis. Caution: Removing the Ethernet cable used for the redundant connection before setting the redundant voice gateway card to reset hold, causes the standby voice gateway card to reboot as active.
Pinouts This section provides the pinout for the following voice gateway cables:
•
Voice gateway non-redundant TDM cable on page 794
•
Voice gateway redundant TDM cable on page 800
Voice gateway non-redundant TDM cable Figure 96 shows the MALC voice gateway cable (MALC-CBL-T1/E1-32, MALC-CBL-T1/E1-32-30M-DSX). Tables 86- 89 list the pinouts.
794
MALC Hardware Installation Guide
Pinouts
Figure 96: MALC voice gateway cable
Table 86: P1 to channels 1-8 Pair
Signal
Color
From
Binder
1
TX 1 (tip)
White/Blue
P1-106
Blue
TX 1 (ring)
Blue/White
P1-105
Blue
RX 1 (tip)
White/Orange
P1-108
Blue
RX 1 (ring)
Orange/White
P1-107
Blue
TX 2 (tip)
White/Green
P1-110
Blue
TX 2 (ring)
Green/White
P1-109
Blue
RX 2 (tip)
White/Brown
P1-112
Blue
RX 2 (ring)
Brown/White
P1-111
Blue
TX 3 (tip)
White/Slate
P1-114
Blue
TX 3 (ring)
Slate/White
P1-113
Blue
RX 3 (tip)
Red/Blue
P1-116
Blue
RX 3 (ring)
Blue/Red
P1-115
Blue
TX 4 (tip)
Red/Orange
P1-27
Blue
TX 4 (ring)
Orange/Red
P1-1
Blue
RX 4 (tip)
Red/Green
P1-79
Blue
RX 4 (ring)
Green/Red
P1-53
Blue
2
3
4
5
6
7
8
MALC Hardware Installation Guide
795
Voice Gateway
Table 86: P1 to channels 1-8 (Continued) Pair
Signal
Color
From
Binder
9
TX 5 (tip)
Red/Brown
P1-28
Blue
TX 5 (ring)
Brown/Red
P1-2
Blue
RX 5 (tip)
Red/Slate
P1-80
Blue
RX 5 (ring)
Slate/Red
P1-54
Blue
TX 6 (tip)
Black/Blue
P1-29
Blue
TX 6 (ring)
Blue/Black
P1-3
Blue
RX 6 (tip)
Black/Orange
P1-81
Blue
RX 6 (ring)
Orange/Black
P1-55
Blue
TX 7 (tip)
Black/Green
P1-30
Blue
TX 7 (ring)
Green/Black
P1-4
Blue
RX 7 (tip)
Black/Brown
P1-82
Blue
RX 7 (ring)
Brown/Black
P1-56
Blue
TX 8 (tip)
Black/Slate
P1-31
Blue
TX 8 (ring)
Slate/Black
P1-5
Blue
RX 8 (tip)
Yellow/Blue
P1-83
Blue
RX 8 (ring)
Blue/Yellow
P1-57
Blue
10
11
12
13
14
15
16
Table 87: P1 to channels 9-16 Pair
Signal
Color
From
To
17
TX 9 (tip)
Yellow/Orange
P1-32
Blue
TX 9 (ring)
Orange/Yellow
P1-6
Blue
RX 9 (tip)
Yellow/Green
P1-84
Blue
RX 9 (ring)
Green/Yellow
P1-58
Blue
TX 10 (tip)
Yellow/Brown
P1-33
Blue
TX 10 (ring)
Brown/Yellow
P1-7
Blue
RX 10 (tip)
Yellow/Slate
P1-85
Blue
RX 10 (ring)
Slate/Yellow
P1-59
Blue
TX 11 (tip)
Violet/Blue
P1-34
Blue
TX 11 (ring)
Blue/Violet
P1-8
Blue
18
19
20
21
796
MALC Hardware Installation Guide
Pinouts
Table 87: P1 to channels 9-16 (Continued) Pair
Signal
Color
From
To
22
RX 11 (tip)
Violet/Orange
P1-86
Blue
RX 11 (ring)
Orange/Violet
P1-60
Blue
TX 12 (tip)
Violet/Green
P1-35
Blue
TX 12 (ring)
Green/Violet
P1-9
Blue
RX 12 (tip)
Violet/Brown
P1-87
Blue
RX 12 (ring)
Brown/Violet
P1-61
Blue
TX 13 (tip)
Violet/Slate
P1-36
Blue
TX 13 (ring)
Slate/Violet
P1-10
Blue
TX 13 (tip)
White/Blue
P1-88
Orange
TX 13 (ring)
Blue/White
P1-62
Orange
RX 14 (tip)
White/Orange
P1-37
Orange
RX 14 (ring)
Orange/White
P1-11
Orange
TX 14 (tip)
White/Green
P1-89
Orange
TX 14 (ring)
Green/White
P1-63
Orange
RX 15 (tip)
White/Brown
P1-38
Orange
RX 15 (ring)
Brown/White
P1-12
Orange
TX 15 (tip)
White/Slate
P1-90
Orange
TX 15 (ring)
Slate/White
P1-64
Orange
RX 16 (tip)
Red/Blue
P1-39
Orange
RX 16 (ring)
Blue/Red
P1-13
Orange
TX 16 (tip)
Red/Orange
P1-91
Orange
TX 16 (ring)
Orange/Red
P1-65
Orange
23
24
25
26
27
28
29
30
31
32
Table 88: P1 to channels 17-24 Pair
Signal
Color
From
Binder
33
RX 17 (tip)
Red/Green
P1-40
Orange
RX 17 (ring)
Green/Red
P1-14
Orange
TX 17 (tip)
Red/Brown
P1-92
Orange
TX 17 (ring)
Brown/Red
P1-66
Orange
34
MALC Hardware Installation Guide
797
Voice Gateway
Table 88: P1 to channels 17-24 (Continued) Pair
Signal
Color
From
Binder
35
RX 18 (tip)
Red/Slate
P1-41
Orange
RX 18 (ring)
Slate/Red
P1-15
Orange
TX 18 (tip)
Black/Blue
P1-93
Orange
TX 18 (ring)
Blue/Black
P1-67
Orange
RX 19 (tip)
Black/Orange
P1-42
Orange
RX 19 (ring)
Orange/Black
P1-16
Orange
TX 19 (tip)
Black/Green
P1-94
Orange
TX 19 (ring)
Green/Black
P1-68
Orange
RX 20 (tip)
Black/Brown
P1-43
Orange
RX 20 (ring)
Brown/Black
P1-17
Orange
TX 20 (tip)
Black/Slate
P1-95
Orange
TX 20 (ring)
Slate/Black
P1-69
Orange
RX 21 (tip)
Yellow/Blue
P1-44
Orange
RX 21 (ring)
Blue/Yellow
P1-18
Orange
RX 21 (tip)
Yellow/Orange
P1-96
Orange
RX 21 (ring)
Orange/Yellow
P1-70
Orange
TX 22 (tip)
Yellow/Green
P1-45
Orange
TX 22 (ring)
Green/Yellow
P1-19
Orange
RX 22 (tip)
Yellow/Brown
P1-97
Orange
RX 22 (ring)
Brown/Yellow
P1-71
Orange
TX 23 (tip)
Yellow/Slate
P1-46
Orange
TX 23 (ring)
Slate/Yellow
P1-20
Orange
RX 23 (tip)
Violet/Blue
P1-98
Orange
RX 23 (ring)
Blue/Violet
P1-72
Orange
TX 24 (tip)
Violet/Orange
P1-47
Orange
TX 24 (ring)
Orange/Violet
P1-21
Orange
RX 24 (tip)
Violet/Green
P1-99
Orange
RX 24 (ring)
Green/Violet
P1-73
Orange
36
37
38
39
40
41
42
43
44
45
46
47
48
798
MALC Hardware Installation Guide
Pinouts
Table 89: P1 to channels 25-32 Pair
Signal
Color
From
Binder
49
RX 25 (tip)
Violet/Brown
P1-48
Orange
RX 25 (ring)
Brown/Violet
P1-22
Orange
TX 25 (tip)
Violet/Slate
P1-100
Orange
TX 25 (ring)
Slate/Violet
P1-74
Orange
TX 26 (tip)
White/Blue
P1-49
Green
TX 26 (ring)
Blue/White
P1-23
Green
RX 26 (tip)
White/Orange
P1-101
Green
RX 26 (ring)
Orange/White
P1-75
Green
TX 27 (tip)
White/Green
P1-50
Green
TX 27 (ring)
Green/White
P1-24
Green
RX 27 (tip)
White/Brown
P1-102
Green
RX 27 (ring)
Brown/White
P1-76
Green
TX 28 (tip)
White/Slate
P1-51
Green
TX 28 (ring)
Slate/White
P1-25
Green
RX 28 (tip)
Red/Blue
P1-103
Green
RX 28 (ring)
Blue/Red
P1-77
Green
TX 29 (tip)
Red/Orange
P1-52
Green
TX 29 (ring)
Orange/Red
P1-26
Green
RX 29 (tip)
Red/Green
P1-104
Green
RX 29 (ring)
Green/Red
P1-78
Green
TX 30 (tip)
Red/Brown
P1-118
Green
TX 30 (ring)
Brown/Red
P1-117
Green
RX 30 (tip)
Red/Slate
P1-120
Green
RX 30 (ring)
Slate/Red
P1-119
Green
TX 31 (tip)
Black/Blue
P1-122
Green
TX 31 (ring)
Blue/Black
P1-121
Green
RX 31 (tip)
Black/Orange
P1-124
Green
RX 31 (ring)
Orange/Black
P1-123
Green
TX 32 (tip)
Black/Green
P1-128
Green
TX 32 (ring)
Green/Black
P1-127
Green
50
51
52
53
54
55
56
57
58
59
60
61
62
63
MALC Hardware Installation Guide
799
Voice Gateway
Table 89: P1 to channels 25-32 (Continued) Pair
Signal
Color
From
Binder
64
RX 32 (tip)
Black/Brown
P1-126
Green
RX 32 (ring)
Brown/Black
P1-125
Green
No connection
P-129 P-130
Voice gateway redundant TDM cable Figure 97 shows the Voice gateway redundant TDM cable (MALC-CBL-T1/ E1-32-VG-REDUNDANT, MALC-CBL-T1/E1-32-VG-RED-25M). Tables 86- 89 list the pinouts. Figure 97: MALC redundant voice gateway cable 1Ð8 9Ð16
17Ð24 32 ma0503
25Ð
1
26
105
130
130
105
26
1
Table 90: P1 (P2) to channels 1-8 Pair
Signal
Color
From
Binder
1
TX 1 (tip)
White/Blue
P1(P2)-106
Blue
TX 1 (ring)
Blue/White
P1(P2)-105
Blue
RX 1 (tip)
White/Orange
P1(P2)-108
Blue
RX 1 (ring)
Orange/White
P1(P2)-107
Blue
2
800
MALC Hardware Installation Guide
Pinouts
Table 90: P1 (P2) to channels 1-8 (Continued) Pair
Signal
Color
From
Binder
3
TX 2 (tip)
White/Green
P1(P2)-110
Blue
TX 2 (ring)
Green/White
P1(P2)-109
Blue
RX 2 (tip)
White/Brown
P1(P2)-112
Blue
RX 2 (ring)
Brown/White
P1(P2)-111
Blue
TX 3 (tip)
White/Slate
P1(P2)-114
Blue
TX 3 (ring)
Slate/White
P1(P2)-113
Blue
RX 3 (tip)
Red/Blue
P1(P2)-116
Blue
RX 3 (ring)
Blue/Red
P1(P2)-115
Blue
TX 4 (tip)
Red/Orange
P1(P2)-27
Blue
TX 4 (ring)
Orange/Red
P1(P2)-1
Blue
RX 4 (tip)
Red/Green
P1(P2)-79
Blue
RX 4 (ring)
Green/Red
P1(P2)-53
Blue
TX 5 (tip)
Red/Brown
P1(P2)-28
Blue
TX 5 (ring)
Brown/Red
P1(P2)-2
Blue
RX 5 (tip)
Red/Slate
P1(P2)-80
Blue
RX 5 (ring)
Slate/Red
P1(P2)-54
Blue
TX 6 (tip)
Black/Blue
P1(P2)-29
Blue
TX 6 (ring)
Blue/Black
P1(P2)-3
Blue
RX 6 (tip)
Black/Orange
P1(P2)-81
Blue
RX 6 (ring)
Orange/Black
P1(P2)-55
Blue
TX 7 (tip)
Black/Green
P1(P2)-30
Blue
TX 7 (ring)
Green/Black
P1(P2)-4
Blue
RX 7 (tip)
Black/Brown
P1(P2)-82
Blue
RX 7 (ring)
Brown/Black
P1(P2)-56
Blue
TX 8 (tip)
Black/Slate
P1(P2)-31
Blue
TX 8 (ring)
Slate/Black
P1(P2)-5
Blue
RX 8 (tip)
Yellow/Blue
P1(P2)-83
Blue
RX 8 (ring)
Blue/Yellow
P1(P2)-57
Blue
4
5
6
7
8
9
10
11
12
13
14
15
16
MALC Hardware Installation Guide
801
Voice Gateway
Table 91: P1 (P) to channels 9-16 Pair
Signal
Color
From
To
17
TX 9 (tip)
Yellow/Orange
P1(P2)-32
Blue
TX 9 (ring)
Orange/Yellow
P1(P2)-6
Blue
RX 9 (tip)
Yellow/Green
P1(P2)-84
Blue
RX 9 (ring)
Green/Yellow
P1(P2)-58
Blue
TX 10 (tip)
Yellow/Brown
P1(P2)-33
Blue
TX 10 (ring)
Brown/Yellow
P1(P2)-7
Blue
RX 10 (tip)
Yellow/Slate
P1(P2)-85
Blue
RX 10 (ring)
Slate/Yellow
P1(P2)-59
Blue
TX 11 (tip)
Violet/Blue
P1(P2)-34
Blue
TX 11 (ring)
Blue/Violet
P1(P2)-8
Blue
RX 11 (tip)
Violet/Orange
P1(P2)-86
Blue
RX 11 (ring)
Orange/Violet
P1(P2)-60
Blue
TX 12 (tip)
Violet/Green
P1(P2)-35
Blue
TX 12 (ring)
Green/Violet
P1(P2)-9
Blue
RX 12 (tip)
Violet/Brown
P1(P2)-87
Blue
RX 12 (ring)
Brown/Violet
P1(P2)-61
Blue
TX 13 (tip)
Violet/Slate
P1(P2)-36
Blue
TX 13 (ring)
Slate/Violet
P1(P2)-10
Blue
TX 13 (tip)
White/Blue
P1(P2)-88
Orange
TX 13 (ring)
Blue/White
P1(P2)-62
Orange
RX 14 (tip)
White/Orange
P1(P2)-37
Orange
RX 14 (ring)
Orange/White
P1(P2)-11
Orange
TX 14 (tip)
White/Green
P1(P2)-89
Orange
TX 14 (ring)
Green/White
P1(P2)-63
Orange
RX 15 (tip)
White/Brown
P1(P2)-38
Orange
RX 15 (ring)
Brown/White
P1(P2)-12
Orange
TX 15 (tip)
White/Slate
P1(P2)-90
Orange
TX 15 (ring)
Slate/White
P1(P2)-64
Orange
RX 16 (tip)
Red/Blue
P1(P2)-39
Orange
RX 16 (ring)
Blue/Red
P1(P2)-13
Orange
18
19
20
21
22
23
24
25
26
27
28
29
30
31
802
MALC Hardware Installation Guide
Pinouts
Table 91: P1 (P) to channels 9-16 (Continued) Pair
Signal
Color
From
To
32
TX 16 (tip)
Red/Orange
P1(P2)-91
Orange
TX 16 (ring)
Orange/Red
P1(P2)-65
Orange
Table 92: P1 (P2) to channels 17-24 Pair
Signal
Color
From
Binder
33
RX 17 (tip)
Red/Green
P1(P2)-40
Orange
RX 17 (ring)
Green/Red
P1(P2)-14
Orange
TX 17 (tip)
Red/Brown
P1(P2)-92
Orange
TX 17 (ring)
Brown/Red
P1(P2)-66
Orange
RX 18 (tip)
Red/Slate
P1(P2)-41
Orange
RX 18 (ring)
Slate/Red
P1(P2)-15
Orange
TX 18 (tip)
Black/Blue
P1(P2)-93
Orange
TX 18 (ring)
Blue/Black
P1(P2)-67
Orange
RX 19 (tip)
Black/Orange
P1(P2)-42
Orange
RX 19 (ring)
Orange/Black
P1(P2)-16
Orange
TX 19 (tip)
Black/Green
P1(P2)-94
Orange
TX 19 (ring)
Green/Black
P1(P2)-68
Orange
RX 20 (tip)
Black/Brown
P1(P2)-43
Orange
RX 20 (ring)
Brown/Black
P1(P2)-17
Orange
TX 20 (tip)
Black/Slate
P1(P2)-95
Orange
TX 20 (ring)
Slate/Black
P1(P2)-69
Orange
RX 21 (tip)
Yellow/Blue
P1(P2)-44
Orange
RX 21 (ring)
Blue/Yellow
P1(P2)-18
Orange
RX 21 (tip)
Yellow/Orange
P1(P2)-96
Orange
RX 21 (ring)
Orange/Yellow
P1(P2)-70
Orange
TX 22 (tip)
Yellow/Green
P1(P2)-45
Orange
TX 22 (ring)
Green/Yellow
P1(P2)-19
Orange
RX 22 (tip)
Yellow/Brown
P1(P2)-97
Orange
RX 22 (ring)
Brown/Yellow
P1(P2)-71
Orange
34
35
36
37
38
39
40
41
42
43
44
MALC Hardware Installation Guide
803
Voice Gateway
Table 92: P1 (P2) to channels 17-24 (Continued) Pair
Signal
Color
From
Binder
45
TX 23 (tip)
Yellow/Slate
P1(P2)-46
Orange
TX 23 (ring)
Slate/Yellow
P1(P2)-20
Orange
RX 23 (tip)
Violet/Blue
P1(P2)-98
Orange
RX 23 (ring)
Blue/Violet
P1(P2)-72
Orange
TX 24 (tip)
Violet/Orange
P1(P2)-47
Orange
TX 24 (ring)
Orange/Violet
P1(P2)-21
Orange
RX 24 (tip)
Violet/Green
P1(P2)-99
Orange
RX 24 (ring)
Green/Violet
P1(P2)-73
Orange
46
47
48
Table 93: P1 (P2) to channels 25-32 Pair
Signal
Color
From
Binder
49
RX 25 (tip)
Violet/Brown
P1(P2)-48
Orange
RX 25 (ring)
Brown/Violet
P1(P2)-22
Orange
TX 25 (tip)
Violet/Slate
P1(P2)-100
Orange
TX 25 (ring)
Slate/Violet
P1(P2)-74
Orange
TX 26 (tip)
White/Blue
P1(P2)-49
Green
TX 26 (ring)
Blue/White
P1(P2)-23
Green
RX 26 (tip)
White/Orange
P1(P2)-101
Green
RX 26 (ring)
Orange/White
P1(P2)-75
Green
TX 27 (tip)
White/Green
P1(P2)-50
Green
TX 27 (ring)
Green/White
P1(P2)-24
Green
RX 27 (tip)
White/Brown
P1(P2)-102
Green
RX 27 (ring)
Brown/White
P1(P2)-76
Green
TX 28 (tip)
White/Slate
P1(P2)-51
Green
TX 28 (ring)
Slate/White
P1(P2)-25
Green
RX 28 (tip)
Red/Blue
P1(P2)-103
Green
RX 28 (ring)
Blue/Red
P1(P2)-77
Green
TX 29 (tip)
Red/Orange
P1(P2)-52
Green
TX 29 (ring)
Orange/Red
P1(P2)-26
Green
50
51
52
53
54
55
56
57
804
MALC Hardware Installation Guide
Pinouts
Table 93: P1 (P2) to channels 25-32 (Continued) Pair
Signal
Color
From
Binder
58
RX 29 (tip)
Red/Green
P1(P2)-104
Green
RX 29 (ring)
Green/Red
P1(P2)-78
Green
TX 30 (tip)
Red/Brown
P1(P2)-118
Green
TX 30 (ring)
Brown/Red
P1(P2)-117
Green
RX 30 (tip)
Red/Slate
P1(P2)-120
Green
RX 30 (ring)
Slate/Red
P1(P2)-119
Green
TX 31 (tip)
Black/Blue
P1(P2)-122
Green
TX 31 (ring)
Blue/Black
P1(P2)-121
Green
RX 31 (tip)
Black/Orange
P1(P2)-124
Green
RX 31 (ring)
Orange/Black
P1(P2)-123
Green
TX 32 (tip)
Black/Green
P1(P2)-128
Green
TX 32 (ring)
Green/Black
P1(P2)-127
Green
RX 32 (tip)
Black/Brown
P1(P2)-126
Green
RX 32 (ring)
Brown/Black
P1(P2)-125
Green
P2-130
Black/Slate
P-129
Green
P2-129
Slate/Black
P-130
Green
59
60
61
62
63
64
Cross connect between P1 and P2
MALC Hardware Installation Guide
805
Voice Gateway
806
MALC Hardware Installation Guide
22 T1/E1 ATM
This chapter describes the MALC-T1/E1-ATM-32 card and explains how to configure it. It includes:
•
Overview, page 808
•
Configuring DS1/E1 interfaces, page 812
•
Configuring IMA groups, page 820
•
T1/E1 32 port TDM cable, page 821
MALC Hardware Installation Guide
807
T1/E1 ATM
Overview The MALC-T1/E1-ATM-32 card provides 32 T1/E1 UNI or IMA ports. All ports must be configured as either UNI or IMA.
Table 94: T1/E1 32 specifications
808
Specification
Description
Density
32 ports
Physical interface
Custom 130-pin amphenol connector
MALC Hardware Installation Guide
A cable is provided that breaks out to 4 non-terminated wire bundles for connecting to patch panels.
Overview
Table 94: T1/E1 32 specifications (Continued) Specification
Description
ATM support
ATM Quality of Service types supported:
• • •
CBR, rt-VBR, nrt-VBR, UBR Fair Weighted Queuing Per VC and per QoS buffering
ATM Forum specifications:
•
UNI 3.0, UNI 3.1 compliant. Note that ILMI, SVCs, point-to-multipoint are currently not supported.
•
UNI 4.0 compliant for PVC features only. Note that ABR, SVCs, SPVCs, Multicast, and Anycast are not currently supported.
•
Partial support for Traffic Management 4.0 including:
•
–
QOS levels described above
–
Connection Admission Control
–
Traffic descriptor specification
VPI/VCI ranges: VPI: 0-7, VCI: 32-63 per UNI interface or IMA group. These values cannot be changed.
•
Number of supported connections: VCLs: 224 per card VPLs: 32 per card Total ATM connections: 256 per card
AAL5 termination:
• •
AAL5 SAR for in-band management VC termination RFC 1483 routed termination supported
16 IMA groups are supported, as described in the ATM forum AF-PHY-0086.001. Note that UNI and IMA mode are not currently supported on the same card. Redundancy
None
Power consumption
27 watts
Creating card-profiles for T1/E1-ATM-32 cards Each card installed in the system must have a card-profile. Each type of slot card requires different settings in the card-profile.
MALC Hardware Installation Guide
809
T1/E1 ATM
Tip: You can specify the name of the software image for a card in a card-profile or a type-module. Each card of a particular type can share a single type-module. Settings in type-modules can be overridden by settings in card-profiles. T1/E1 ATM 32 cards on the MALC have the following types and software images: Table 95: MALC card types Card
Type
Name of software image
MALC-T1/E1-ATM-32
5032
malct1e1atm32.bin
The following example creates a card-profile for a T1/E1-ATM-32 card in shelf 1, slot 15: zSH> card add 1/15/5032 linetype e1 | ds1 | e1-ima | ds1-ima
or zSH> new card-profile 1/15/5032 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {}: malct1e1atm32.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {0}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: e1 | ds1 | e1-ima |ds1-ima card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Note: To change from a T1 to an E1 interface in an existing card-profile record, first delete the card-profile record, create a different card-profile record with the desired card-line-type setting, and then save the new record.
Verifying the slot card installation After you save the card-profile record, the slot card in that slot resets and the begins downloading their software image from the flash card. This could take a few moments.
810
MALC Hardware Installation Guide
Overview
When the card has finished loading, a log message similar to the following is displayed (if logging is enabled): zSH> Card in slot slot-number changed state to RUNNING
You can also use the slots command and specify the slot number of the card to view the state of the card. For example: zSH> slots 13 Type Card Version EEPROM Version Serial # CLEI Code Card-Profile ID Shelf Slot State Mode Heartbeat check Longest hbeat
: : : : : : : : : : : :
MALC ADSL 1 2 110006 No CLEI 1/13/5004 1 13 LOADING indicates the card is still initializing FUNCTIONAL enabled 0
zSH> slots 13 Type Card Version EEPROM Version Serial # CLEI Code Card-Profile ID Shelf Slot State Mode Heartbeat check Longest hbeat Fault reset Uptime
: : : : : : : : : : : : : :
MALC ADSL 1 2 110006 No CLEI 1/13/5004 1 13 RUNNING indicates the card is functional FUNCTIONAL enabled 59 enabled 1 minute
To view the status of all the cards, use the slots command without any arguments: zSH> slots 1: MALC DS3 (RUNNING) 13: MALC ADSL (RUNNING) 15: MALC MTAC (RUNNING)
Viewing active redundant cards Use the showactivecards command to view all active cards in the system that are part of a redundant card group: zSH> showactivecards Shelf/Slot Group Id Card Type __________________________________ 1: 1/14 333 MALC MTAC
MALC Hardware Installation Guide
811
T1/E1 ATM
Configuring DS1/E1 interfaces This section explains how to configure DS1/E1 interfaces. It applies to the TDM Uplink card (ports 9 through 16) the T1/E1 IMA card, and the T1/E1 32 port card. Note: For redundant systems, configure the DS1 interfaces on both the active and standby cards. The following table summarizes the commands required to configure DS1 uplink interfaces on the MALC: Action
Command
Update the DS1 interfaces, which specify the basic parameters of the DS1 line, including framing, encoding, and clocking. See Configuring DS1/E1 interfaces on page 812.
update ds1-profile 1-1-port-0/ds1 where port is from 1 to 8 (for the IMA Uplink card) 9 to 16 (for the TDM Uplink card) 1 to 32 (for the T1/E1 32 card) If your system is redundant, configure the DS1 interfaces on both the active and standby cards.
Activate the DS1 interfaces in the if-translate and line-group profiles. See Activating a DS1 interface on page 816.
update if-translate 1-1-port-0/ds1 where port is from 1 to 8 for the T1/E1 IMA Uplink card or 1 to 16 for the T1/E1 TDM Uplink card 1 to 32 (for the T1/E1 32 card)
The ds1-profile configures both T1 and E1 interfaces. T1 interfaces on the MALC have the following defaults:
•
ESF framing
•
B8ZS coding
•
Robbed bit signaling
•
CSU mode
•
Line build out of 0 feet
•
clock source is eligible
E1 interfaces on the MALC have the following defaults:
812
•
E1-CRCMF line type
•
HDB3 coding
•
Line build out of 0 feet
•
clock source is not eligible
MALC Hardware Installation Guide
Configuring DS1/E1 interfaces
The following table describes the supported ds1-profile parameters. Parameter
Options
line-type
The type of DS1 circuit. Values: esf Extended Super Frame. e1Mf : G.704, table 4a, with TS16 multiframing enabled for E1 circuits. e1CrcMf : G.704, table 4b, with TS16 multiframing enabled for E1 circuits. Default: esf for T1 e1 for E1
line-code
The type of Zero Code Suppression used on the interface. b8zs: a specific pattern of normal bits and bipolar violations used to replace a sequence of eight zero bits. hdb3: High Density Bipolar of order 3. A code used for E1. Default: b8zs for T1 hdb3 for E1
send-code
This parameter is used for bit error rate (BER) testing.
circuit-id
Enter a circuit identifier for the interface, up to 36 characters.
loopback-config
This parameter is used for loopback testing.
signal mode
Specifies the signaling mode. Default: messageoriented for E1 robbedbit for T1
dsx-line-length
The length of the DSX WAN interface in feet. This parameter provides information for line build out circuitry. Values: Dsx0 0 feet for the line build out (LBO) setting. Dsx133 133 feet for the LBO. Dsx266 266 feet for the LBO. Dsx399 399 feet for the LBO. Dsx533 533 feet for the LBO. Dsx655 655 feet for the LBO. Default: 0
MALC Hardware Installation Guide
813
T1/E1 ATM
Parameter
Options
line-status-change-trap -enable
Specifies whether a trap is generated whenever the line state changes. Values: enabled disabled Default: enabled
ds1-mode
Type of interface. Values: dsx DS1 interface is DSX csu DS1 interface is CSU other Interface is neither CSU nor DSX Default: csu
csu-line-length
This parameter provides information for line build out circuitry. Values: csu00 0 dB line build out. csu75 -7.5 dB line build out. csu150 -15.0 dB line build out. csu225 -22.5 dB line build out. Default: csu00
transmit-clock-source
Specifies the clock source for the interface. See System clocking on page 205 for information about configuring the system clock.
clock-source-eligible
Specifies whether clock source is allowed. Default: noteligible for E1 eligible for T1
814
MALC Hardware Installation Guide
Configuring DS1/E1 interfaces
Parameter
Options
cell-scramble
Indicates whether ATM cell scrambling is enabled for this interface. Both sides of the connection must agree on whether scrambling is enabled. Values: true Cell scrambling enabled. false Cell scrambling disabled. Default: true
coset-polynomial
Indicates whether the coset polynomial is used to calculate the ATM header error control (HEC) value. Both sides of the connection must agree on the method of calculating the HEC value. Values: true The coset polynomial is used to calculate the HEC value. false The coset polynomial is not used to calculate the HEC value. Default: true
Configuring a DS1 interface The default values are appropriate for most applications. If you need to change them, update the ds1-profile for the interface: zSH> update ds1-profile 1-1-1-0/ds1 Please provide the following: [q]uit. line-type: ----------------------> {esf}: line-code: ----------------------> {b8zs}: send-code: ----------------------> {sendnocode}: circuit-id: ---------------------> {ds1}: 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}: protocol-emulation: -------------> {network} signal-type: --------------------> {loopstart} ds1-group-number: ---------------> {0} line-power: ---------------------> {disabled} Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
MALC Hardware Installation Guide
815
T1/E1 ATM
Activating a DS1 interface Activate each DS1 interface by updating its if-translate profile: zSH> update if-translate 1-1-1-0/ds1 Please provide the following: [q]uit. ifindex: -----> {1}: . shelf: -------> {1}: slot: --------> {1}: port: --------> {1}: subport: -----> {0}: type: --------> {ds1}: adminstatus: -> {down}: up physical-flag: ----> {true}: iftype-extension: -> {0}: ifName: -----------> {1-1-1-0}: redundancy-param1: -> {0} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
After you update the profile, a log message appears indicating the line is active: 1/1: alarm_mgr: : l=167: 01:01:01 Major T1 Up Line 1:1:1:0
Continue updating each DS1 interface. When all the interfaces are active, proceed to configuring the IMA groups.
Configuring IMA groups Note: For redundant systems, configure the IMA interfaces on both the active and standby cards. For more information about IMA, refer to the ATM Forum Inverse Multiplexing for ATM (IMA) Specification Version 1.1 (AF-PHY-0086.001). The following table summarizes the commands required to configure IMA groups on the MALC:
816
Action
Command
(Optional) Update the ima-group-profile, which specifies the basic settings of the IMA group, including the number of transmit and receive links and the clocking. See Configuring IMA groups on page 820.
update ima-group-profile 1/slot/1 If your system is redundant, configure the IMA group on both the active and standby cards.
(Optional) Move the default IMA links to different groups. See Moving IMA links on page 821.
imalink move SourceIMAGroup DestinationIMAGroup ds1Interface
MALC Hardware Installation Guide
where slot the slot that contains the card).
Configuring IMA groups
The following table describes the supported parameters in the ima-group-profile. Parameter
Description
groupSymmetry
The symmetry of the Inverse Multiplexing over ATM (IMA) group. Symmetry determines whether the transmit and receive sides of the IMA link must be configured and how traffic is sent over the links. Values: symmetricOperation Both transmit and receive IMA links must be configured and the system can transmit and receive traffic only if both sides of the connection are active. asymmetricOperation Both transmit and receive IMA links must be configured, but the system can transmit and receive traffic even if both sides of the connection are not active. asymmetricConfiguration Transmit and receive links do not have to be configured and the system can transmit and receive traffic even if both sides of the connection are not active. Default: symmetricOperation
minNumTxLinks
Minimum number of transmit links required to be Active for the IMA group to be in the Operational state. If the number of active links falls below this value, the link drops and the redundant link (if any) takes over. Values: 1 to 8 Default: 1
minNumRxLinks
Minimum number of receive links required to be active for the IMA group to be in the operational state. If the number of active links falls below this value, the link drops and the redundant link (if any) takes over. Values: 1 to 8 Default: 1
txClkMode
Transmit clocking mode used by the near-end IMA group. Values: itc Independent Transmit Clock. Indicates that IMA links do not all use the same transmit clock. Each IMA link derives clock from its associated DS1 interface. ctc Common Transmit Clock. Indicates the transmit clock of all IMA links are derived from the same source. When set to ctc, the MALC derives the IMA clocking from the system clock. Default: ctc
MALC Hardware Installation Guide
817
T1/E1 ATM
Parameter
Description
txImaId
The IMA ID currently in use by the near-end IMA interface. Values: 0 to 255 Default: 1
txFramLength
The frame length to be used by the IMA group in the transmit direction. Can only be set when the IMA group is startup. Values: m32 32 cells m64 64 cells m128 128 cells m256 256 cells Default: m128
diffDelayMax
The maximum number of milliseconds of differential delay among the links that can be tolerated on this interface. Values: 0 to 100 Default: 25
alphaValue
The number of consecutive invalid ICP cells allowed before the system changes from a Sync state to a Hunt state. Values: 1 or 2 Default: 2
betaValue
The number of consecutive errored ICP cells allowed before the system changes from a Sync state to a Hunt state. Values: 1 to 5 Default: 2
gammaValue
The number of consecutive valid ICP cells allowed before the system changes from a PreSync state to the Sync state. Values: 1 to 5 Default: 1
818
testLinkIfIndex
This parameter is used for testing the IMA link.
testPattern
This parameter is used for testing the IMA link.
testProcStatus
This parameter is used for testing the IMA link.
MALC Hardware Installation Guide
Configuring IMA groups
Parameter
Description
groupRestoreNumR etry
The number of times an IMA group recovery takes place. Values: 0 to 4 Default: 0 3 retrys
groupRestoreNumD elay
The delay, in seconds, before a recovery attempt takes place, and the interval between subsequent recovery attempts. Values: 0 to 3600 Default: 0 3600 seconds
Overview Inverse Multiplexing over ATM (IMA) is a mechanism for combining links. IMA combines multiple circuits into a single data pipe, spreading the data stream across multiple circuits for transmission and combining them at the other end. The MALC-T1/E1-ATM-32 card supports IMA groups. Each card supports 16 IMA groups. The MALC-T1/E1-ATM-32 card provides 32 T1/E1 UNI or IMA ports. All ports must be configured as either UNI or IMA. IMA are groups. UNI are single ports. When these cards boot up, the system creates the IMA groups and assigns the T1/E1 links to the following groups: Links
IMA group
1-4
1
5-8
2
9 - 12
3
13 - 16
4
Empty
5
Empty
6
Empty
7
Empty
8
17 - 20
9
21 - 24
10
25 - 28
11
MALC Hardware Installation Guide
819
T1/E1 ATM
Links
IMA group
29 -32
12
Empty
13
Empty
14
Empty
15
Empty
16
Note: (T1/E1 32 card only) IMA links 1-16 can only belong to IMA groups 1-8 and links 17-32 can only belong to IMA groups 9-16. Note the following about multiple IMA groups:
•
In a redundant Uplink configuration, you must configure IMA groups on both the active and standby cards
•
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. Do not use the imalink remove command unless requested to by Zhone GSS.
Configuring IMA groups The following example updates an IMA group to change the minimum number of links in the group: zSH> update ima-group-profile 1/1/1 shelf/slot/port Please provide the following: [q]uit. 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}: groupRestoreNumRetry:--> {4} groupRestoreDelaySecs:-> {3600} .................... Save changes? [s]ave, [c]hange or [q]uit: s
820
MALC Hardware Installation Guide
T1/E1 32 port TDM cable
Record updated.
Moving IMA links To move IMA links from one group to another, use the imalink move command. For example: zSH> imalink move 1-1-1-0/atmima 1-1-2-0/atmima 1-1-1-0/ds1 Stack unbind successful. Link moved successfully.
This command moves the DS1 interface 1-1-1-0/ds1 from IMA group 1-1-1-0/atm to IMA group 1-1-2-0/atmima. If this is a redundant configuration, also move the IMA link on the standby card: zSH> imalink move 1-2-1-0/atmima 1-2-2-0/atmima 1-2-1-0/ds1 Stack unbind successful. Link moved successfully.
After moving the links, you can use the imalink show command to view the links in the group: zSH> imalink show 1-3-1-0/atmima DS1 Links for IMA Group 1-3-1-0/atmima: If Index If Name ----------------------000736 1-3-1-0 000737 1-3-2-0 000738 1-3-3-0 000739 1-3-4-0
T1/E1 32 port TDM cable Figure 98 shows the MALC T1/E1 32 port cable (MALC-CBL-T1/E1-32, MALC-CBL-T1/E1-32-30M-DSX). Tables 96- 99 list the pinouts.
MALC Hardware Installation Guide
821
T1/E1 ATM
Figure 98: MALC T1/E1 32 port cable
Table 96: P1 to channels 1-8 Pair
Signal
Color
From
Binder
1
TX 1 (tip)
White/Blue
P1-106
Blue
TX 1 (ring)
Blue/White
P1-105
Blue
RX 1 (tip)
White/Orange
P1-108
Blue
RX 1 (ring)
Orange/White
P1-107
Blue
TX 2 (tip)
White/Green
P1-110
Blue
TX 2 (ring)
Green/White
P1-109
Blue
RX 2 (tip)
White/Brown
P1-112
Blue
RX 2 (ring)
Brown/White
P1-111
Blue
TX 3 (tip)
White/Slate
P1-114
Blue
TX 3 (ring)
Slate/White
P1-113
Blue
RX 3 (tip)
Red/Blue
P1-116
Blue
RX 3 (ring)
Blue/Red
P1-115
Blue
TX 4 (tip)
Red/Orange
P1-27
Blue
TX 4 (ring)
Orange/Red
P1-1
Blue
RX 4 (tip)
Red/Green
P1-79
Blue
RX 4 (ring)
Green/Red
P1-53
Blue
2
3
4
5
6
7
8
822
MALC Hardware Installation Guide
T1/E1 32 port TDM cable
Table 96: P1 to channels 1-8 (Continued) Pair
Signal
Color
From
Binder
9
TX 5 (tip)
Red/Brown
P1-28
Blue
TX 5 (ring)
Brown/Red
P1-2
Blue
RX 5 (tip)
Red/Slate
P1-80
Blue
RX 5 (ring)
Slate/Red
P1-54
Blue
TX 6 (tip)
Black/Blue
P1-29
Blue
TX 6 (ring)
Blue/Black
P1-3
Blue
RX 6 (tip)
Black/Orange
P1-81
Blue
RX 6 (ring)
Orange/Black
P1-55
Blue
TX 7 (tip)
Black/Green
P1-30
Blue
TX 7 (ring)
Green/Black
P1-4
Blue
RX 7 (tip)
Black/Brown
P1-82
Blue
RX 7 (ring)
Brown/Black
P1-56
Blue
TX 8 (tip)
Black/Slate
P1-31
Blue
TX 8 (ring)
Slate/Black
P1-5
Blue
RX 8 (tip)
Yellow/Blue
P1-83
Blue
RX 8 (ring)
Blue/Yellow
P1-57
Blue
10
11
12
13
14
15
16
Table 97: P1 to channels 9-16 Pair
Signal
Color
From
To
17
TX 9 (tip)
Yellow/Orange
P1-32
Blue
TX 9 (ring)
Orange/Yellow
P1-6
Blue
RX 9 (tip)
Yellow/Green
P1-84
Blue
RX 9 (ring)
Green/Yellow
P1-58
Blue
TX 10 (tip)
Yellow/Brown
P1-33
Blue
TX 10 (ring)
Brown/Yellow
P1-7
Blue
RX 10 (tip)
Yellow/Slate
P1-85
Blue
RX 10 (ring)
Slate/Yellow
P1-59
Blue
TX 11 (tip)
Violet/Blue
P1-34
Blue
TX 11 (ring)
Blue/Violet
P1-8
Blue
18
19
20
21
MALC Hardware Installation Guide
823
T1/E1 ATM
Table 97: P1 to channels 9-16 (Continued) Pair
Signal
Color
From
To
22
RX 11 (tip)
Violet/Orange
P1-86
Blue
RX 11 (ring)
Orange/Violet
P1-60
Blue
TX 12 (tip)
Violet/Green
P1-35
Blue
TX 12 (ring)
Green/Violet
P1-9
Blue
RX 12 (tip)
Violet/Brown
P1-87
Blue
RX 12 (ring)
Brown/Violet
P1-61
Blue
TX 13 (tip)
Violet/Slate
P1-36
Blue
TX 13 (ring)
Slate/Violet
P1-10
Blue
RX 13 (tip)
White/Blue
P1-88
Orange
RX 13 (ring)
Blue/White
P1-62
Orange
TX 14 (tip)
White/Orange
P1-37
Orange
TX 14 (ring)
Orange/White
P1-11
Orange
RX 14 (tip)
White/Green
P1-89
Orange
RX 14 (ring)
Green/White
P1-63
Orange
TX 15 (tip)
White/Brown
P1-38
Orange
TX 15 (ring)
Brown/White
P1-12
Orange
RX 15 (tip)
White/Slate
P1-90
Orange
RX 15 (ring)
Slate/White
P1-64
Orange
TX 16 (tip)
Red/Blue
P1-39
Orange
TX 16 (ring)
Blue/Red
P1-13
Orange
RX 16 (tip)
Red/Orange
P1-91
Orange
RX 16 (ring)
Orange/Red
P1-65
Orange
23
24
25
26
27
28
29
30
31
32
Table 98: P1 to channels 17-24 Pair
Signal
Color
From
Binder
33
TX 17(tip)
Red/Green
P1-40
Orange
TX 17 (ring)
Green/Red
P1-14
Orange
RX 17 (tip)
Red/Brown
P1-92
Orange
RX 17 (ring)
Brown/Red
P1-66
Orange
34
824
MALC Hardware Installation Guide
T1/E1 32 port TDM cable
Table 98: P1 to channels 17-24 (Continued) Pair
Signal
Color
From
Binder
35
TX 18 (tip)
Red/Slate
P1-41
Orange
TX 18 (ring)
Slate/Red
P1-15
Orange
RX 18 (tip)
Black/Blue
P1-93
Orange
RX 18 (ring)
Blue/Black
P1-67
Orange
TX 19 (tip)
Black/Orange
P1-42
Orange
TX 19 (ring)
Orange/Black
P1-16
Orange
RX 19 (tip)
Black/Green
P1-94
Orange
RX 19 (ring)
Green/Black
P1-68
Orange
TX 20 (tip)
Black/Brown
P1-43
Orange
TX 20 (ring)
Brown/Black
P1-17
Orange
RX 20 (tip)
Black/Slate
P1-95
Orange
RX 20 (ring)
Slate/Black
P1-69
Orange
TX 21 (tip)
Yellow/Blue
P1-44
Orange
TX 21 (ring)
Blue/Yellow
P1-18
Orange
RX 21 (tip)
Yellow/Orange
P1-96
Orange
RX 21 (ring)
Orange/Yellow
P1-70
Orange
TX 22 (tip)
Yellow/Green
P1-45
Orange
TX 22 (ring)
Green/Yellow
P1-19
Orange
RX 22 (tip)
Yellow/Brown
P1-97
Orange
RX 22 (ring)
Brown/Yellow
P1-71
Orange
TX 23 (tip)
Yellow/Slate
P1-46
Orange
TX 23 (ring)
Slate/Yellow
P1-20
Orange
RX 23 (tip)
Violet/Blue
P1-98
Orange
RX 23 (ring)
Blue/Violet
P1-72
Orange
TX 24 (tip)
Violet/Orange
P1-47
Orange
TX 24 (ring)
Orange/Violet
P1-21
Orange
RX 24 (tip)
Violet/Green
P1-99
Orange
RX 24 (ring)
Green/Violet
P1-73
Orange
36
37
38
39
40
41
42
43
44
45
46
47
48
MALC Hardware Installation Guide
825
T1/E1 ATM
Table 99: P1 to channels 25-32 Pair
Signal
Color
From
Binder
49
RX 25 (tip)
Violet/Brown
P1-48
Orange
RX 25 (ring)
Brown/Violet
P1-22
Orange
TX 25 (tip)
Violet/Slate
P1-100
Orange
TX 25 (ring)
Slate/Violet
P1-74
Orange
RX 26 (tip)
White/Blue
P1-49
Green
RX 26 (ring)
Blue/White
P1-23
Green
TX 26 (tip)
White/Orange
P1-101
Green
TX 26 (ring)
Orange/White
P1-75
Green
RX 27 (tip)
White/Green
P1-50
Green
RX 27 (ring)
Green/White
P1-24
Green
TX 27 (tip)
White/Brown
P1-102
Green
TX 27 (ring)
Brown/White
P1-76
Green
RX 28 (tip)
White/Slate
P1-51
Green
RX 28 (ring)
Slate/White
P1-25
Green
TX 28 (tip)
Red/Blue
P1-103
Green
TX 28 (ring)
Blue/Red
P1-77
Green
RX 29 (tip)
Red/Orange
P1-52
Green
RX 29 (ring)
Orange/Red
P1-26
Green
TX 29 (tip)
Red/Green
P1-104
Green
TX 29 (ring)
Green/Red
P1-78
Green
RX 30 (tip)
Red/Brown
P1-118
Green
RX 30 (ring)
Brown/Red
P1-117
Green
TX 30 (tip)
Red/Slate
P1-120
Green
TX 30 (ring)
Slate/Red
P1-119
Green
RX 31 (tip)
Black/Blue
P1-122
Green
RX 31 (ring)
Blue/Black
P1-121
Green
TX 31 (tip)
Black/Orange
P1-124
Green
TX 31 (ring)
Orange/Black
P1-123
Green
RX 32 (tip)
Black/Green
P1-128
Green
RX 32 (ring)
Green/Black
P1-127
Green
50
51
52
53
54
55
56
57
58
59
60
61
62
63
826
MALC Hardware Installation Guide
T1/E1 32 port TDM cable
Table 99: P1 to channels 25-32 (Continued) Pair
Signal
Color
From
Binder
64
TX 32 (tip)
Black/Brown
P1-126
Green
TX 32 (ring)
Brown/Black
P1-125
Green
No connection
P-129 P-130
MALC Hardware Installation Guide
827
T1/E1 ATM
828
MALC Hardware Installation Guide
23 T1/E1 CES
This chapter describes the MALC-T1/E1-CES-12 card. It includes:
•
Overview, page 829
•
CES card configuration, page 830
•
Pinouts, page 832
Overview Circuit Emulation Service (CES) allows T1/E1 circuits to be transparently extended across an ATM network or IP routed network. CES across an ATM network 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 T1/E1 interfaces (such as T1, E1, E3, and T3). CES over an IP network transports T1/ E1 circuit data over an static IP routed network between Zhone equipment endpoints and delivers the data to the destination T1/E1 circuit. 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). 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 DS0 channels towards different destinations.
MALC Hardware Installation Guide
829
T1/E1 CES
Table 100: MALC-T1/E1-CES-12 port card specifications Specification
Description
Size
1 slot
Density
12 ports T1/E1
Connectors
One (1) Champ 50-pin telco connector
Standards supported
ITU-T G.704 ITU-T G.706 ITU-T G.703 (120 ohm balanced) ATM Forum standard af.vtoa.0078.0000
Line characteristics
B8ZS HDB3 AMI D4 ESF SF
Supported line rates
1.544 MHz, 2.048 MHz
ATM support
AAL1 circuit emulation
Metallic test function
Look-out test Metallic loopback relay
Redundancy
None
Power
15 Watts nominal
Default ranges: VPI 0-1, VCI 0-255
plus 0.75 W additional per active port 24 W maximum total.
CES card configuration This section includes:
•
Creating card-profiles for MALC-T1/E1-CES-12-port cards on page 830
•
Configuring and activating the T1/E1 CES interface on page 831
Creating card-profiles for MALC-T1/E1-CES-12-port cards The following example creates a card-profile for an T1/E1 CES 12-port card in shelf 1, slot 12: zSH> card add 1/12/5034 linetype e1
830
MALC Hardware Installation Guide
CES card configuration
or zSH> new card-profile 1/12/5034 shelf/slot/type sw-file-name: ----------->{}: malct1e1ces12.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {1}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: e1 card-atm-configuration: -> {vbnrt65rt30}: card-line-voltage: ------> {not-used}: ...................: Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Configuring and activating the T1/E1 CES interface The CES circuit frame type can be set in the ds1-profile during interface configuration or in the cross connect command used to create the connection. Table 101: Supported frame types Line type
Description
Bundle format
e1
ITU-T G.704 without CRC-4
Structured
e1crc
ITU-T G.704 with CRC-4
Structured
e1mf
G.704 multiframing enabled
Structured
e1crcmf
G.704 multiframing enabled and crc enabled
Structured
esf
Extended SuperFrame DS1 (T1.107)
Structured
d4
AT&T D4 format DS1 (T1.107)
Structured
e1unframed
E1 signal without frame synchronization.
Unstructured
ds1unframed
T1 signal without frame synchronization.
Unstructured
To configure a T1/E1 interface: 1
Update the DS1 profile to specify an unframed line type: zSH> update ds1-profile 1-12-1-0/ds1 Please provide the following: [q]uit. line-type: ----------------------> {e1}: e1unframed line-code: ----------------------> {hdb3}: send-code: ----------------------> {sendnocode}:
MALC Hardware Installation Guide
831
T1/E1 CES
circuit-id: ---------------------> {e1}: loopback-config: ----------------> {noloop}: signal-mode: --------------------> {none}: fdl: ----------------------------> {fdlnone}: dsx-line-length: ----------------> {dsx0}: line-status_change-trap-enable: -> {enabled}: channelization: -----------------> {disabled}: ds1-mode: -----------------------> {csu}: csu-line-length: ----------------> {csu00}: clock-source-eligible: ----------> {eligible}: transmit-clock-source: ----------> {throughtiming}: cell-scramble: ------------------> {true}: coset-polynomial: ---------------> {true}: protocol-emulation: -------------> {network}: signal-type: --------------------> {loopstart}: ds1-group-number: ---------------> {0}: line-power: ---------------------> {disabled}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
2
Activate the interface: zSH> update if-translate 1-12-1-0/ds1 Please provide the following: [q]uit. ifIndex: -----------> {321}: shelf: -------------> {1}: slot: --------------> {7}: port: --------------> {1}: subport: -----------> {0}: type: --------------> {ds1}: adminstatus: -------> {down}: up physical-flag: -----> {true}: iftype-extension: --> {none}: ifName: ------------> {1-12-1-0}: redundancy-param1: -> {0}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
3
Update and activate the rest of the interfaces, as required.
Pinouts Table 102 describes the T1/E1 CES port pinouts. This card uses a 50 position female champ connector.
832
MALC Hardware Installation Guide
Pinouts
Table 102: T1/E1 CES port pinouts Port
Pair
Signal
To
1
TX 1 Ring
1
TX 1 Tip
26
RX 1 Ring
2
RX 1 Tip
27
TX 2 Ring
3
TX 2 Tip
28
RX 2 Ring
4
RX 2 Tip
29
TX 3 Ring
5
TX 3 Tip
30
RX 3 Ring
6
RX 3 Tip
31
TX 4 Ring
7
TX 4 Tip
32
RX 4 Ring
8
RX 4 Tip
33
TX 5 Ring
9
TX 5 Tip
34
RX 5 Ring
10
RX 5 Tip
35
TX 6 Ring
11
TX 6 Tip
36
RX 6 Ring
12
RX 6 Tip
37
TX 7 Ring
13
TX 7 Tip
38
RX 7 Ring
14
RX 7 Tip
39
TX 8 Ring
15
TX 8 Tip
40
1 2
3 2 4
5 3 6
7 4 8
9 5 10
11 6 12
13 7 14
15 8
MALC Hardware Installation Guide
833
T1/E1 CES
Table 102: T1/E1 CES port pinouts (Continued) Port
Pair
Signal
To
16
RX 8 Ring
16
RX 8 Tip
41
TX 9 Ring
17
TX 9 Tip
42
RX 9 Ring
18
RX 9 Tip
43
TX 10 Ring
19
TX 10 Tip
44
RX 10 Ring
20
RX 10 Tip
45
TX 11 Ring
21
TX 11 Tip
46
RX 11 Ring
22
RX 11 Tip
47
TX 12 Ring
23
TX 12 Tip
48
RX 12 Ring
24
RX 12 Tip
49
Ground
50
Ground
25
17 9 18
19 10 20
21 11 22
23 12 24
25 N/A
834
MALC Hardware Installation Guide
24 EFM T1/E1
This chapter describes the MALC-EFM-T1/E1-24 card and explains how to configure it. It includes:
•
Overview, page 836
•
Creating card profiles for T1/E1-24 cards, page 838
•
Verifying the slot card installation, page 838
•
Verifying the slot card presence, page 839
•
Displaying card-profile, page 839
•
Configuring T1/E1 interfaces, page 840
•
Bond group/physical line stats (MALC-EFM-T1/E1-24 card), page 844
•
EFM 802.3ah bonding, page 845
•
802.3ah EFM OAM, page 848
•
T1/E1 24 port TDM cable, page 851
MALC Hardware Installation Guide
835
EFM T1/E1
Overview active fault pwr fail
The MALC-EFM-T1/E1-24 card provides 24 T1/E1 bondable ports. The card provides Ethernet over T1 links to Zhone TNE devices. The T1 links can be added or removed as you configure your network. The card automatically performs load balancing over the link. The T1 links can be over dry copper four-wire pair or through a SONET fiber network that connects up to a T1 link on the far end. Both implementations transmit and receive over a DS1 connection. The MALC-EFM-T1/E1-24 bonded card supports IP bridging, VLANS, and Q-in-Q.
1-24
Ports on the card can support either N2N or EFM loop bonding, but not both. The device supports a maximum of eight ports per bonded group. Also, the device supports up to 12 bonded groups. The device requires external clock sourcing for loop bonding to work. The card is supported by GigE/RPR and DS3 uplinks. The card supports bridge and host interfaces. It does not support Cell Relay. ma0656
T1/E1 EFM
Table 103: MALC-EFM-T1/E1-24 Bonding specifications Specification
Description
Density
24 ports
Physical interface
Custom 96-pin Molex connector
Size
1 slot
Connectors
One (1) 96-pin Molex connector.
A cable is provided that breaks out to 4 non-terminated wire bundles for connecting to patch panels.
One (1) Champ 50-pin telco connector for each patch panel connection. Line characteristics
B8ZS HDB3 D4 ESF
Supported line rates
836
MALC Hardware Installation Guide
1.544 MHz, 2.048 MHz
Overview
Table 103: MALC-EFM-T1/E1-24 Bonding specifications (Continued) Specification
Description
Redundancy
None
Power consumption
27 watts
T1/E1 Network Scenario The following illustration shows a typical T1/E1 network scenario. Figure 99: T1/E1 Networkg Illustration - SONET
DS1
SONET
DS1
ma 0660
RPR
TNE
Fiber Network MALC EFM T1/E1-24 Bonded Card
Ethernet Network
Ethernet Network
Figure 100: T1/E1 Network Illustration - DS1
RPR DS1
m a 0661
TNE
Dry Copper Network
Ethernet Network
MALC EFM T1/E1-24 Bonded Card
Ethernet Network
Card profile information for T1/E1-24 cards Each card installed in the system must have a card-profile. Each type of slot card requires different settings in the card-profile.
MALC Hardware Installation Guide
837
EFM T1/E1
T1/E1 ATM 24 cards on the MALC have the following types and software images: Table 104: MALC card types Card
Type
Name of software image
MALC-EFM-T1/E1-24
5068
malct1e1bonded.bin
Creating card profiles for T1/E1-24 cards The following example creates a card-profile for a MALC-T1/E1-ATM-24 card in shelf 1, slot 5 zSH> card add 1/5/5068 shelf/slot/type linetype e1 | ds1
or zSH> new card-profile 1/5/5068 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {}: malct1e1bonded.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {0}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: e1 | ds1 card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Verifying the slot card installation After you save the card-profile record, the slot card in that slot resets and the begins downloading their software image from the flash card. This could take a few moments. When the card has finished loading, a log message similar to the following is displayed (if logging is enabled): zSH> Card in slot slot-number changed state to RUNNING zSH> slots 5 Type Card Version EEPROM Version
838
MALC Hardware Installation Guide
: MALC NTN/EFM T1E1 Bonded : 1 : 1
Verifying the slot card presence
Serial # : CLEI Code : Card-Profile ID : Shelf : Slot : ROM Version : Software Version: State : Mode : Heartbeat check : Longest hbeat : Fault reset : Uptime :
3510123 No CLEI 1/5/5068 1 5 development MALC CAN 1.13.0.102 RUNNING FUNCTIONAL enabled 8673 enabled 3 hours, 57 minutesType
Verifying the slot card presence You can also use the slots command and specify the slot number of the card to view the state of the card. For example: To view the status of all the cards, use the slots command without any arguments: zSH> slots 1: MALC RPR GIGE (RUNNING) 4: MALC NTN/EFM T1E1 Bonded (RUNNING) 5: MALC NTN/EFM T1E1 Bonded (RUNNING) 6: MALC T1E132 (LOADING)
Displaying card-profile To view the operational statistics of the card, use the get card-profile command, specifying the shelf, the slot, and the type value. In this case, specify shelf 1, slot 5, and type 5068. zSH> get card-profile 1/5/5068 sw-file-name: -----------> {malct1e1bonded.bin} admin-status: -----------> {operational} upgrade-sw-file-name: ---> {} upgrade-vers: -----------> {} admin-status-enable: ----> {enable} sw-upgrade-admin: -------> {reloadcurrrev} sw-enable: --------------> {true} sw-upgrade-enable: ------> {false} card-group-id: ----------> {0} hold-active: ------------> {false} weight: -----------------> {nopreference} card-line-type: ---------> {e1}
MALC Hardware Installation Guide
839
EFM T1/E1
Configuring T1/E1 interfaces This section explains how to configure DS1/E1 interfaces. It applies to the T1/ E1 24 port card. The following table summarizes the commands required to configure DS1 uplink interfaces on the MALC: Action
Command
Update the DS1 interfaces, which specify the basic parameters of the DS1 line, including framing, encoding, and clocking. See Configuring T1/E1 interfaces on page 840.
update ds1-profile 1-slot-port-0/ds1
Activate the DS1 interfaces in the if-translate and line-group profiles. See Activating a DS1 interface on page 844.
update if-translate 1-slot-port-0/ds1
port is 1 to 24 (for the T1/E1 Bonded card)
where port is from 1 to 24 (for the T1/E1 24 card)
Listing the profiles and running a get command The following example shows a sample list of existing DS1 profiles on a MALC: zSH> list ds1-profile ds1-profile 1-3-1-0/ds1 ds1-profile 1-3-2-0/ds1 ds1-profile 1-3-3-0/ds1 ds1-profile 1-3-4-0/ds1 ds1-profile 1-5-5-0/ds1 5 entries found.
The following example shows output to a sample get ds1-profile command. zSH> get ds1-profile 1-5-1-0/ds1 line-type: ----------------------> line-code: ----------------------> send-code: ----------------------> circuit-id: ---------------------> loopback-config: ----------------> signal-mode: --------------------> fdl: ----------------------------> dsx-line-length: ----------------> line-status_change-trap-enable: -> channelization: -----------------> ds1-mode: -----------------------> csu-line-length: ----------------> clock-source-eligible: ----------> transmit-clock-source: ----------> cell-scramble: ------------------> coset-polynomial: ---------------> protocol-emulation: -------------> signal-type: --------------------> ds1-group-number: --------------->
840
MALC Hardware Installation Guide
{e1crc} {hdb3} {sendnocode} {e1} {noloop} {none} {fdlnone} {dsx0} {enabled} {disabled} {other} {csu00} {eligible} {throughtiming} {true} {true} {network} {loopstart} {0}
Configuring T1/E1 interfaces
line-power: ---------------------> {disabled} timeslot-assignment: ------------> {0+1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+21+ 22+23+24+25+26+27+28+29+30}
The ds1-profile configures both T1 and E1 interfaces. T1 interfaces on the MALC have the following defaults:
•
ESF framing
•
B8ZS coding
•
Robbed bit signaling
•
CSU mode
•
Line build out of 0 feet
•
clock source is eligible
E1 interfaces on the MALC have the following defaults:
•
E1-CRCMF line type
•
HDB3 coding
•
Line build out of 0 feet
•
clock source is not eligible
The following table describes the supported ds1-profile parameters. Parameter
Options
line-type
The type of DS1 circuit. Values: esf Extended Super Frame. e1Mf : G.704, table 4a, with TS16 multiframing enabled for E1 circuits. e1CrcMf : G.704, table 4b, with TS16 multiframing enabled for E1 circuits. Default: esf for T1 e1 for E1
line-code
The type of Zero Code Suppression used on the interface. b8zs: a specific pattern of normal bits and bipolar violations used to replace a sequence of eight zero bits. hdb3: High Density Bipolar of order 3. A code used for E1. Default: b8zs for T1 hdb3 for E1
send-code
This parameter is used for bit error rate (BER) testing.
MALC Hardware Installation Guide
841
EFM T1/E1
Parameter
Options
circuit-id
Enter a circuit identifier for the interface, up to 36 characters.
loopback-config
This parameter is used for loopback testing.
signal mode
Specifies the signaling mode. Default: messageoriented for E1 robbedbit for T1
dsx-line-length
The length of the DSX WAN interface in feet. This parameter provides information for line build out circuitry. Values: Dsx0 0 feet for the line build out (LBO) setting. Dsx133 133 feet for the LBO. Dsx266 266 feet for the LBO. Dsx399 399 feet for the LBO. Dsx533 533 feet for the LBO. Dsx655 655 feet for the LBO. Default: 0
line-status-change-trap -enable
Specifies whether a trap is generated whenever the line state changes. Values: enabled disabled Default: enabled
ds1-mode
Type of interface. Values: dsx DS1 interface is DSX csu DS1 interface is CSU other Interface is neither CSU nor DSX Default: csu
csu-line-length
This parameter provides information for line build out circuitry. Values: csu00 0 dB line build out. csu75 -7.5 dB line build out. csu150 -15.0 dB line build out. csu225 -22.5 dB line build out. Default: csu00
842
MALC Hardware Installation Guide
Configuring T1/E1 interfaces
Parameter
Options
transmit-clock-source
Specifies the clock source for the interface. See System clocking on page 205 for information about configuring the system clock. (This reference is accurate when incorporating the section into the guide).
clock-source-eligible
Specifies whether clock source is allowed. Default: noteligible for E1 eligible for T1
cell-scramble
Indicates whether ATM cell scrambling is enabled for this interface. Both sides of the connection must agree on whether scrambling is enabled. Values: true Cell scrambling enabled. false Cell scrambling disabled. Default: true
coset-polynomial
Indicates whether the coset polynomial is used to calculate the ATM header error control (HEC) value. Both sides of the connection must agree on the method of calculating the HEC value. Values: true The coset polynomial is used to calculate the HEC value. false The coset polynomial is not used to calculate the HEC value. Default: true
Updating a DS1 interface The default values are appropriate for most applications. If you need to change them, update the ds1-profile for the interface: zSH> update ds1-profile 1-5-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}: disabled channelization: -----------------> {disabled}: ds1-mode: -----------------------> {other}: csu-line-length: ----------------> {csu00}: clock-source-eligible: ----------> {eligible}: transmit-clock-source: ----------> {throughtiming}:
MALC Hardware Installation Guide
843
EFM T1/E1
cell-scramble: ------------------> {true}: coset-polynomial: ---------------> {true}: protocol-emulation: -------------> {network} signal-type: --------------------> {loopstart} ds1-group-number: ---------------> {0} line-power: ---------------------> {disabled} Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Activating a DS1 interface Activate each DS1 interface by updating its if-translate profile: zSH> update if-translate 1-1-1-0/ds1 Please provide the following: [q]uit. ifindex: -----> {1}: . shelf: -------> {1}: slot: --------> {1}: port: --------> {1}: subport: -----> {0}: type: --------> {ds1}: adminstatus: -> {down}: up physical-flag: ----> {true}: iftype-extension: -> {0}: ifName: -----------> {1-1-1-0}: redundancy-param1: -> {0} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
After you update the profile, a log message appears indicating the line is active: 1/1: alarm_mgr: : l=167: 01:01:01 Major T1 Up Line 1:1:1:0
Continue updating each DS1 interface. When all the interfaces are active, proceed to configuring the IMA groups.
Bond group/physical line stats (MALC-EFM-T1/E1-24 card) Data in the dslstat command is provided for bond groups. The data is collected differently for N2N and EFM ports and bond groups.
Packet counts The bond stats command displays the aggregate statistics for a specified bond group interface or if-index. zSH> bond stats 93 ****************** Bond group statistics ****************** Group Info
844
MALC Hardware Installation Guide
EFM 802.3ah bonding
Slot GrpId 1 201 AdminStatus UP
Port 1 2
Interface Name IfIndex 1-1-201-0/n2nbond 93 OperStatus Bandwidth Last Change UP 11392000 0.00:01:42
Group Members Interface Name 1-1-1-0/t1e1 1-1-2-0/t1e1
IfIndex 13 15
Statistics (Received) Octets Ucast Mcast Bcast Discards Errors
4720535 2 0 0 0 379
Statistics (Transmitted) Octets Ucast Mcast Bcast Discards
0 0 0 0 0
Bond group bandwidth Table 105 shows the bond group bandwidth rates for EFM bond groups. Table 105: Bond group bandwidth
Frame Size
Downstream (pks/sec)
Upstream (pks/sec)
Total
64
40584
40584
81168
128
21478
21478
42956
256
11105
11105
22210
512
5547
5547
11094
1024
2826
2826
5652
1280
2269
2269
4538
1480
1967
1967
3934
EFM 802.3ah bonding EFM (Ethernet in the First Mile) extends Ethernet signaling between the MALC-EFM-T1/E1-24 card and EtherXtend or other EFM-enabled CPEs.
MALC Hardware Installation Guide
845
EFM T1/E1
By default, all ports are configured in N2N bond groups and can be configured for EFM bonding. The following CLI bond commands are supported to add, modify, show and delete bond groups.
Creating bond groups To add a single N2N or EFM bond group and verify bond group. zSH> bond add group 1-1-101-0/n2nbond zSH> list if-translate ..... if-translate 1-1-101-0/n2nbond if-translate 1-1-101-0-n2nbond/linegroup
zSH> bond add group 1-1-102-0/efmbond zSH> list if-translate ..... if-translate 1-1-102-0/efmbond if-translate 1-1-102-0-efmbond/linegroup
To add a new member to an existing bond group: zSH> bond add member 1-1-101-0/n2nbond 1-1-1-0/t1e1 zSH> list if-stack ..... if-stack 1-1-101-0/n2nbond/1-1-1-0-shdsl/n2nlink
To create a bond group with multiple members: zSH> bond add member 1-1-4-0/n2nbond 1-1-3-0/t1e1 1-1-4-0/t1e1 zSH> list if-translate ..... if-translate 1-1-4-0/n2nbond if-translate 1-1-4-0-n2nbond/linegroup
Displaying bond groups Bond groups can be displayed for all existing groups, a specific group, a specific slot, or link. To display all configured bond groups: zSH> bond show all Slot 1 1 1
GrpId 4 102 101
Bond Groups Name 1-1-4-0 1-1-102-0 1-1-101-0
To display a specific bond group:
846
MALC Hardware Installation Guide
Type n2nbond efmbond n2nbond
State OOS OOS OOS
EFM 802.3ah bonding
zSH> bond show group 1-1-4-0/n2nbond Bond Groups Slot GrpId Name Type 1 4 1-1-4-0 n2nbond Group Members Slot Port Name Type 1 3 1-1-3-0 t1e1 1 4 1-1-4-0 t1e1
State OOS State OOS OOS
To display bond groups by slot: zSH> bond show slot 1 Bond Groups Slot GrpId Name 1 4 1-1-4-0 1 102 1-1-102-0 1 101 1-1-101-0
Type n2nbond efmbond n2nbond
State OOS OOS OOS
Type n2nbond
State OOS
Type t1e1 t1e1
State OOS OOS
To display bond groups for a specific link: zSH> bond show link 1-1-4-0/shdsl Bond Groups Slot GrpId Name 1 4 1-1-4-0 Group Members Slot Port Name 1 3 1-1-3-0 1 4 1-1-4-0
Changing bond group type Bond group type can be changed for individual bond groups or all bond groups used in a specified slot using the bond move and bond modify commands. zSH> bond move 1-1-102-0/efmbond 1-1-101-0/n2nbond 1-1-2-0/t1e1 zSH> bond modify n2n group 1-1-101-0/efmbond zSH> bond modify efm slot 1
Deleting bond groups Bond groups can be deleted by individual member or entire group. zSH> bond delete member 1-1-101-0/n2nbond 1-1-3-0/t1e1
zSH> bond show group 1-1-101-0/n2nbond
MALC Hardware Installation Guide
847
EFM T1/E1
Displaying statistics Bond group statistics can be displayed for a bond group interface or if-index. zSH> bond stats 93 ****************** Bond group statistics ****************** Group Info Slot GrpId 1 201 AdminStatus UP
Port 1 2
Interface Name IfIndex 1-1-201-0/n2nbond 93 OperStatus Bandwidth Last Change UP 11392000 0.00:01:42
Group Members Interface Name 1-1-1-0/t1e1 1-1-2-0/t1e1
IfIndex 13 15
Statistics (Received) Octets Ucast Mcast Bcast Discards Errors
4720535 2 0 0 0 379
Statistics (Transmitted) Octets Ucast Mcast Bcast Discards
0 0 0 0 0
802.3ah EFM OAM EFM OAM uses an in-band link layer OAM packet exchange between MALC EFM interfaces and OAM-capable CPEs, such as EtherXtend and EtherXtend Lite.The OAM-capable CPE functions as a remote peer to provide event notification. The EFM and N2N bond groups are Ethernet-like interfaces and support EFM OAM. When EFM OAM is configured on a MALC EFM or Ethernet-like interface in active mode, the discovery process is started. If the interface peer also has OAM enabled, the discovery process continues until the peer is located. If the discovery process does not find a peer, the active interface continues sending the initial Information OAMPDU once a second until a peer OAM-enabled CPE device responds.
848
MALC Hardware Installation Guide
802.3ah EFM OAM
Release 1.14.1 introduces EFM OAM support on MALC-EFM-SHDSL-24, MALC-EFM-SHDSL-24NTWC, MALC-EFM-SHDSL-24NTP card interfaces connected to EtherXtend, EtherXtend Lite, other compatible CPEs.
MALC with EFM-T1/E1-24 card
Configuring OAM support The OAM interface is defined by an ether-oam profile that specifies the options for active/passive mode, loopback, and notification for events. By default, OAM is disabled on all MALC uplink and EFM interfaces. To configure OAM features: 1
Create a new OAM profile for the desired EFM interface. By default, this profile is in passive mode with loopback disabled. This example configures EFM OAM in active mode on EFM bond group 1-4-50-0/efmbond on a EFM-T1/E1-24 card in slot 4.
zSH> eth-oam add 1-4-50-0/efmbond active
2
Create a new OAM profile for the desired EtherXtend interface. By default, this profile is in passive mode with loopback disabled. This example configures EFM OAM in passive mode on EFM bond group 1-1-40-0/efmbond on the peer EtherXtend.
zSH> eth-oam add 1-1-40-0/efmbond passive
3
Enter commands to modify and display OAM parameters. The eth-oam modify command provides access to configurable settings in the ether-oam profile. The eth-oam show command displays configured OAM settings.
MALC Hardware Installation Guide
849
EFM T1/E1
The eth-oam stats command displays OAM statistics for a specified physical interface or bond group or all OAM interfaces.
eth-oam add Configures and enables OAM interface on a physical interface. Syntax eth-oam interface/type [active | passive] Options interface/type
Name and type of the physical interface or bond group. active Sets OAM to active mode on this interface. The default is passive. passive Sets OAM to passive mode on this interface. The default is passive.
eth-oam delete Deletes and disables the OAM configuration on the specified physical interface. This command does not delete any other configurations on this interface such as bond groups and bridge interfaces. Syntax eth-oam delete interface/type Options interface/type
Name and type of the physical interface or bond group.
eth-oam modify Modifies a configured eth-oam interface. Syntax eth-oam modify interface/type [active | passive] Options interface/type
Name and type of the physical interface or bond group.
eth-oam show Displays configured OAM parameters for the specified interface. If no interface is specified, configured OAM parameters are displayed for all OAM enabled interfaces. Syntax eth-oam show interface/type [peer] Options interface/type
Name and type of the physical interface or bond group. peer Displays the learned configuration information of the peer for the given interface. Includes peer MAC address, peer vendor OUI, peer vendor unique info, peer mode, peer max OAM PDU size, peer configuration revision, peer supported functions.
850
MALC Hardware Installation Guide
T1/E1 24 port TDM cable
eth-oam stats Displays OAM statistics for the specified interface. If no option is specified, statistics are displayed for all OAM interfaces. Syntax eth-oam stats interface/type Options interface/type
Name and type of the physical interface or bond group.
T1/E1 24 port TDM cable Cabling options include the MALC-CBL-T1/E1-2-45DEG and the following blunt cables:
•
MALC-CBL-ADSL-48-100FT-BLUNT
•
MALC-CBL-ADSL-48-350FT-BLUNT
•
MALC-CBL-ADSL-48-30FT-BLUNT
•
MALC-CBL-ADSL-48-15FT-BLUNT
MALC-CBL-T1/E1-2-45DEG Figure 101 shows the MALC EFM T1/E1 24-port bonding cable (MALC-CBL-T1/E1-24-45DEG). Table 109 on page 855 lists the pinouts.
P
or
ts
1-
6
Figure 101: MALC T1/E1 24 port cable
P
or
ts
7-
12
P2
P
or
ts
13
ma 0 6 6 2
-1
8
P3
25
50
48
96 P1
P
or ts
19
-2
4
P4
P5 1
26
1
49
MALC Hardware Installation Guide
851
EFM T1/E1
Table 106: Port-Pair Detail Ports 1-6 (P1 to P2) ( Port
Pair
Signal
Color
From
To
1
1
TX 1 Ring
BLU/WHT
P1-1
P2-1
TX 1 Tip
WHT/BLU
P1-2
P2-26
RX 1 Ring
ORG/WHT
P1-3
P2-27
RX 1 Tip
WHT/ORG
P1-4
P2-2
TX 2 Ring
GRN/WHT
P1-5
P2-5
TX 2 Tip
WHT/GRN
P1-6
P2-30
RX 2 Ring
BRN/WHT
P1-7
P2-31
RX 2 Tip
WHT/BRN
P1-8
P2-6
TX 3 Ring
SLT/WHT
P1-9
P2-9
TX 3 Tip
WHT/SLT
P1-10
P2-34
RX 3 Ring
BLU/RED
P1-11
P2-35
RX 3 Tip
RED/BLU
P1-12
P2-10
TX 4 Ring
ORG/RED
P1-13
P2-13
TX 4 Tip
RED/ORG
P1-14
P2-38
RX 4 Ring
GRN/RED
P1-15
P2-39
RX 4 Tip
RED/GRN
P1-16
P2-14
TX 5 Ring
BRN/RED
P1-17
P2-17
TX 5 Tip
RED/BRN
P1-18
P2-42
RX 5 Ring
SLT/RED
P1-19
P2-43
RX 5 TIP
RED/SLT
P1-20
P2-18
TX 6 Ring
BLU/BLK
P1-21
P2-21
TX 6 Tip
BLK/BLU
P1-22
P2-46
RX 6 Ring
ORG/BLK
P1-23
P2-47
RX 6 TIP
BLK/ORG
P1-24
P2-22
2
2
3
4
3
5
6
4
7
8
5
9
10
6
11
12
852
MALC Hardware Installation Guide
T1/E1 24 port TDM cable
Table 107: Port-Pair Detail Ports (P1 to P3) 7-12 Port
Pair
Signal
Color
From
To
7
13
TX 7 Ring
BLU/WHT
P1-25
P3-1
TX 7 Tip
WHT/BLU
P1-26
P3-26
RX 7 Ring
ORG/WHT
P1-27
P3-27
RX 7 Tip
WHT/ORG
P1-28
P3-2
TX 8 Ring
GRN/WHT
P1-29
P3-5
TX 8 Tip
WHT/GRN
P1-30
P3-30
RX 8 Ring
BRN/WHT
P1-31
P3-31
RX 8 Tip
WHT/BRN
P1-32
P3-6
TX 9 Ring
SLT/WHT
P1-33
P3-9
TX 9 Tip
WHT/SLT
P1-34
P3-34
RX 9 Ring
BLU/RED
P1-35
P3-35
RX 9 Tip
RED/BLU
P1-36
P3-10
TX 10 Ring
ORG/RED
P1-37
P3-13
TX 10 Tip
RED/ORG
P1-38
P3-38
RX 10 Ring
GRN/RED
P1-39
P3-39
RX 10 Tip
RED/GRN
P1-40
P3-14
TX 11 Ring
BRN/RED
P1-41
P3-17
TX 11 Tip
RED/BRN
P1-42
P3-42
RX 11 Ring
SLT/RED
P1-43
P3-43
RX 11 Tip
RED/SLT
P1-44
P3-18
TX 12 Ring
BLU/BLK
P1-45
P3-21
TX 12 Tip
BLK/BLU
P1-46
P3-46
RX 12 Ring
ORG/BLK
P1-47
P3-47
RX 12 Tip
BLK/ORG
P1-48
P3-22
14
8
15
16
9
17
18
10
19
20
11
21
22
12
23
24
MALC Hardware Installation Guide
853
EFM T1/E1
Table 108: Port-Pair Detail Ports (P1 to P4)13-18 Port
Pair
Signal
Color
From
To
13
25
TX 13 Ring
BLU/WHT
P1-49
P4-1
TX 13 Tip
WHT/BLU
P1-50
P4-26
RX 13 Ring
ORG/WHT
P1-51
P4-27
RX 13 Tip
WHT/ORG
P1-52
P4-2
TX 14 Ring
GRN/WHT
P1-53
P4-5
TX 14 Tip
WHT/GRN
P1-54
P4-30
RX 14 Ring
BRN/WHT
P1-55
P4-31
RX 14 Tip
WHT/BRN
P1-56
P4-6
TX 15 Ring
SLT/WHT
P1-57
P4-9
TX 15 Tip
WHT/SLT
P1-58
P4-34
RX 15 Ring
BLU/RED
P1-59
P4-35
RX 15 Tip
RED/BLU
P1-60
P4-10
TX 16 Ring
ORG/RED
P1-61
P4-13
TX 16 Tip
RED/ORG
P1-62
P4-38
RX 16 Ring
GRN/RED
P1-63
P4-39
RX 16 Tip
RED/GRN
P1-64
P4-14
TX 17 Ring
BRN/RED
P1-65
P4-17
TX 17 Tip
RED/BRN
P1-66
P4-42
RX 17 Ring
SLT/RED
P1-67
P4-43
RX 17 Tip
RED/SLT
P1-68
P4-18
TX 18 Ring
BLU/BLK
P1-69
P4-21
TX 18 Tip
BLK/BLU
P1-70
P4-46
RX 18 Ring
ORG/BLK
P1-71
P4-47
RX 18 Tip
BLK/ORG
P1-72
P4-22
26
14
27
28
15
29
30
16
31
32
17
33
34
18
35
36
854
MALC Hardware Installation Guide
T1/E1 24 port TDM cable
Table 109: Port-Pair Detail Ports (P1 to P5) 19-24 Port
Pair
Signal
Color
From
To
19
37
TX 19 Ring
BLU/WHT
P1-73
P5-1
TX 19 Tip
WHT/BLU
P1-74
P5-26
RX 19 Ring
ORG/WHT
P1-75
P5-27
RX 19 Tip
WHT/ORG
P1-76
P5-2
TX 20 Ring
GRN/WHT
P1-77
P5-5
TX 20 Tip
WHT/GRN
P1-78
P5-30
RX 20 Ring
BRN/WHT
P1-79
P5-31
RX 20 Tip
WHT/BRN
P1-80
P5-6
TX 21 Ring
SLT/WHT
P1-81
P5-9
TX 21 Tip
WHT/SLT
P1-82
P5-34
RX 21 Ring
BLU/RED
P1-83
P5-35
RX 21 Tip
RED/BLU
P1-84
P5-10
TX 22 Ring
ORG/RED
P1-85
P5-13
TX 22 Tip
RED/ORG
P1-86
P5-38
RX 22 Ring
GRN/RED
P1-87
P5-39
RX 22 Tip
RED/GRN
P1-88
P5-14
TX 23 Ring
BRN/RED
P1-89
P5-17
TX 23 Tip
RED/BRN
P1-90
P5-42
RX 23Ring
SLT/RED
P1-91
P5-43
RX 23 Tip
RED/SLT
P1-92
P5-18
TX 24 Ring
BLU/BLK
P1-93
P5-21
TX 24 Tip
BLK/BLU
P1-94
P5-46
RX 24 Ring
ORG/BLK
P1-95
P5-47
RX 24 Tip
BLK/ORG
P1-96
P5-22
38
20
39
40
21
41
42
22
43
44
23
45
46
24
47
48
Blunt cables Several blunt-end MALC-EFM-T1/E1-24 card cable options are supported.
•
MALC-CBL-ADSL-48-100FT-BLUNT
•
MALC-CBL-ADSL-48-350FT-BLUNT
•
MALC-CBL-ADSL-48-30FT-BLUNT
MALC Hardware Installation Guide
855
EFM T1/E1
•
MALC-CBL-ADSL-48-15FT-BLUNT
The following tables list the blunt cable pinouts. Table 110: Pinout for high density connector to blunt end cable Port
Pair
1 1
2
3 2 4
5 3 6
7 4 8
9 5 10
11 6 12
856
Signal
Color
Form
TX 1 Ring
Blue/White
P1-1
TX 1 Tip
White/Blue
P1-2
RX 1 Ring
Orange/White
P1-3
TX 1 Tip
White/Orange
P1-4
TX 2 Ring
Green/White
P1-5
TX 2 Tip
White/Green
P1-6
RX 2 Ring
Brown/White
P1-7
TX 2 Tip
White/Brow
n P1-8
TX 3 Ring
Slate/White
P1-9
TX 3 Tip
White/Slate
P1-10
RX 3 Ring
Blue/Red
P1-11
TX 3 Tip
Red/Blue
P1-12
TX 4 Ring
Orange/Red
P1-13
TX 4 Tip
Red/Orange
P1-14
RX 4 Ring
Green/Red
P1-15
TX 4 Tip
Red/Green
P1-16
TX 5 Ring
Brown/Red
P1-17
TX 5 Tip
Red/Brown
P1-18
RX 5 Ring
Slate/Red
P1-19
TX 5 Tip
Red/Slate
P1-20
TX 6 Ring
Blue/Black
P1-21
TX 6 Tip
Black/Blue
P1-22
RX 6 Ring
Orange/Black
P1-23
TX 6 Tip
Black/Orange
P1-24
MALC Hardware Installation Guide
Binder Group
1 (Blue)
T1/E1 24 port TDM cable
Table 111: Pinout for high density connector to blunt end cable (Cont’d) Port
Pair
Signal
7
13
TX 7 Ring
Blue/White
P1-25
TX 7 Tip
White/Blue
P1-26
RX 7 Ring
Orange/White
P1-27
TX 7 Tip
White/Orange
P1-28
TX 8 Ring
Green/White
P1-29
TX 8 Tip
White/Green
P1-30
RX 8 Ring
Brown/White
P1-31
TX 8 Tip
White/Brown
P1-32
TX 9 Ring
Slate/White
P1-33
TX 9 Tip
White/Slate
P1-34
RX 9 Ring
Blue/Red
P1-35
TX 9 Tip
Red/Blue
P1-36
TX 10 Ring
Orange/Red
P1-37
TX 10 Tip
Red/Orange
P1-38
RX 10 Ring
Green/Red
P1-39
TX 10 Tip
Red/Green
P1-40
TX 11 Ring
Brown/Red
P1-41
TX 11 Tip
Red/Brown
P1-42
RX 11 Ring
Slate/Red
P1-43
TX 11 Tip
Red/Slate
P1-44
TX 12 Rin
gBlue/Black
P1-45
TX 12 Tip
Black/Blue
P1-46
RX 12 Ring
Orange/Black
P1-47
TX 12 Tip
Black/Orange
P1-48
14
8
15
16
9
17
18
10
19
20
11
21
22
12
23
24
Color
Form
Binder Group
2 (Orange)
MALC Hardware Installation Guide
857
EFM T1/E1
Table 112: Pinout for high density connector to blunt end cable (Cont’d) Port
Pair
Signal
Color
Form
13
25
TX 13 Ring
Blue/White
P1-49
TX 13 Tip
White/Blue
P1-50
RX 13 Ring
Orange/White
P1-53
TX 13 Tip
White/Orange
P1-52
TX 14 Ring
Green/White
P1-55
TX 14 Tip
White/Green
P1-54
RX 14 Ring
Brown/White
P1-57
TX 14 Tip
White/Brown
P1-56
TX 15 Ring
Slate/White
P1-59
TX 15 Tip
White/Slate
P1-58
RX 15 Ring
Blue/Red
P1-61
TX 15 Tip
Red/Blue
P1-60
TX 16 Ring
Orange/Red
P1-63
TX 16 Tip
Red/Orange
P1-62
RX 16 Ring
Green/Red
P1-65
TX 16 Tip
Red/Green
P1-64
TX 17 Ring
Brown/Red
P1-67
TX 17 Tip
Red/Brown
P1-66
RX 17 Ring
Slate/Red
P1-69
TX 17 Tip
Red/Slate
P1-68
TX 18 Ring
Blue/Black
P1-71
TX 18 Tip
Black/Blue
P1-70
RX 18 Ring
Orange/Black
P1-73
TX 18 Tip
Black/Orange
P1-72
26
14
27
28
15
29
30
16
31
32
17
33
34
18
35
36
858
MALC Hardware Installation Guide
Binder Group
3 (Green)
T1/E1 24 port TDM cable
Table 113: Pinout for high density connector to blunt end cable (Cont’d) Port
Pair
Signal
Color
19
37
TX 19 Ring
Blue/White
P1-73
TX 19 Tip
White/Blue
P1-74
RX 19 Ring
Orange/White
P1-75
TX 19 Tip
White/Orange
P1-76
TX 20 Ring
Green/White
P1-77
TX 20 Tip
White/Green
P1-78
RX 20 Ring
Brown/White
P1-79
TX 20 Tip
White/Brown
P1-80
TX 21 Ring
Slate/White
P1-81
TX 21 Tip
White/Slate
P1-82
RX 21 Ring
Blue/Red
P1-83
TX 21 Tip
Red/Blue
P1-84
TX 22 Ring
Orange/Red
P1-85
TX 22 Tip
Red/Orange
P1-86
RX 22 Ring
Green/Red
P1-87
TX 22 Tip
Red/Green
P1-88
TX 23 Ring
Brown/Red
P1-89
TX 23 Tip
Red/Brown
P1-90
RX 23 Ring
Slate/Red
P1-91
TX 23 Tip
Red/Slate
P1-92
TX 24 Ring
Blue/Black
P1-93
TX 24 Tip
Black/Blue
P1-94
RX 24 Ring
Orange/Black
P1-95
TX 24 Tip
Black/Orange
P1-96
38
20
39
40
21
41
42
22
43
44
23
45
46
24
47
48
Form
Binder Group
4 (Brown
MALC Hardware Installation Guide
859
EFM T1/E1
860
MALC Hardware Installation Guide
25 DS3/E3
This chapter describes the MALC DS3/E3 Line card and explains how to configure it. It includes:
•
Overview, page 862
•
DS3 network examples, page 864
•
Creating card profiles for DS3 cards, page 865
•
Verifying the slot card installation, page 866
•
Listing profiles and running a get command, page 867
•
Configuring the DS3 interfaces, page 868
•
Activating the interface profile, page 869
•
Creating VP-VC connections, page 870
MALC Hardware Installation Guide
861
DS3/E3
Overview active fault pwr fail
The MALC-DS3/E3-4 card is a single-slot card for use in any suitably provisioned MALC chassis. It has four DS3/E3 interfaces. Note that the DS3 line card is unchannelized, meaning it does not support separate DS1 connections.
D S 3 / E 3 A T M
ma0659
DS3
862
MALC Hardware Installation Guide
Table 114: MALC-DS3/E3-4 card specifications Specification
Value
Size
1 slot
Density
4 Ports
Physical interfaces
Custom high density connector.
Redundancy
None
Overview
Table 114: MALC-DS3/E3-4 card specifications (Continued) Specification
Value
ATM support
MALC performs ATM cell relay functions between cell based line cards (such as ADSL or G.SHDSL) and the Uplink card. The Uplink card performs cell relay function for the ATM traffic on the backplane. ATM Quality of Service types supported:
• • •
CBR, rt-VBR, nrt-VBR, UBR Fair Weighted Queuing Per VC and per QoS buffering
ATM Forum specifications:
•
UNI 3.0, UNI 3.1 compliant. Note that ILMI, SVCs, point-to-multipoint are currently not supported.
•
UNI 4.0 compliant for PVC features only. Note that ABR, SVCs, SPVCs, Multicast, and Anycast are not currently supported.
•
Partial support for Traffic Management 4.0 including: –
QOS levels described above
–
Connection Admission Control
–
Traffic descriptor specification
Default VPI/VCI ranges:
• •
VPI: 0 to 3 VCI: 32 to 1023
AAL2 and AAL5 termination:
• • • Power consumption
AAL2 SAR for MALC POTS lines AAL5 SAR for in-band management VC termination RFC 1483 routed termination supported
30 W nominal 35 W maximum
MALC Hardware Installation Guide
863
DS3/E3
DS3 network examples The following two figures show sample DS3 networks. The first figure shows a DS3 connection an ATM network. Figure 102: DS3 connection to an ATM network
ATM Network
MALC 719
MALC 319
DS3 Uplink Card
DS3 Uplink Card
ma0663
ATM Cell Switched Network
The following figure shows a DS3 connection to a GigE network.
864
MALC Hardware Installation Guide
Configuring DS3 cards
Figure 103: DS3 connection to a GigE network
GigE Network
GigE Uplink Card MALC 719
DS3 Line Card
DS3 Uplink Card MALC 319
ma0664
ATM Cell Switched Network
Configuring DS3 cards Creating card profiles for DS3 cards Each card installed in the system must have a card-profile. Each type of slot card requires different settings in the card-profile. The DS3 card on the MALC have the following types and software images: Table 115: MALC card types Card
Type
Name of software image
DS3
5070
malcds3e3atm4.bin
MALC Hardware Installation Guide
865
DS3/E3
The following example creates a card-profile for a DS3 card in shelf 1, slot 6: zSH> card add 1/6/5070
or zSH> new card-profile 1/6/5070 Please provide the following: [q]uit. sw-file-name: -----------> {}: malcds3e3atm4.bin admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {true}: sw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}: hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {unknowntype}: card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created.
Verifying the slot card installation After you save the card-profile record, the slot card in that slot resets and the begins downloading their software image from the flash card. This could take a few moments. When the card has finished loading, a log message similar to the following is displayed (if logging is enabled): zSH> Card in slot slot-number changed state to RUNNING
You can also use the slots command and specify the slot number of the card to view the state of the card. For example: zSH> slots 6 Type : Card Version : EEPROM Version : Serial # : CLEI Code : Card-Profile ID : Shelf : Slot : ROM Version : Software Version: State : Mode : Heartbeat check :
866
MALC Hardware Installation Guide
MALC DS3/E3-4 1 1 210003 No CLEI 1/6/5070 1 6 MALC CAN 1.12.1.108 development RUNNING FUNCTIONAL enabled
Configuring DS3 cards
Longest hbeat Fault reset Uptime Start time
: : : :
51 enabled 2 hours, 2 minutes 1148504119
To view the status of all the cards, use the slots command without any arguments: zSH> slots 1:*MALC OC3F (RUNNING) 6: MALC DS3/E3-4 (RUNNING) 13: MALC T1E1VG/MALC T1E18VG (RUNNING) 16: MALC GSHDSL (LOADING)
To view the operational statistics of the card, use the get card command, specifying the shelf, the slot, and the type value. In this case, specify shelf 1, slot 6 and type 5070. zSH> get card-profile 1/6/5070 sw-file-name: -----------> {malcds3e3atm4.bin} admin-status: -----------> {operational} upgrade-sw-file-name: ---> {} upgrade-vers: -----------> {} admin-status-enable: ----> {enable} sw-upgrade-admin: -------> {reloadcurrrev} sw-enable: --------------> {true} sw-upgrade-enable: ------> {false} card-group-id: ----------> {0} hold-active: ------------> {false} weight: -----------------> {nopreference} card-line-type: ---------> {ds3} card-atm-configuration: -> {notapplicable} card-line-voltage: ------> {not-used}
Listing profiles and running a get command 1
Before continuing, you may want to display a list of existing DSL profiles by issuing the list command explicitly with the DS3 card. To view these profiles, issue the following command: zSH> list ds3-profile ds3-profile 1-6-1-0/ds3 ds3-profile 1-6-2-0/ds3 ds3-profile 1-6-3-0/ds3 ds3-profile 1-6-4-0/ds3
Now that you know the profile name, you can determine what settings you may want to change. 2
Run a get command explicitly on the card to determine what settings you may want to change by updating the card. To view these settings, issue the following command:
MALC Hardware Installation Guide
867
DS3/E3
zSH> get ds3-profile 1-6-4-0/ds3 line-type: ---------------> {dsx3cbitparity} line-coding: -------------> {dsx3b3zs} send-code: ---------------> {dsx3sendnocode} circuit-id: --------------> {} loopback-config: ---------> {dsx3noloop} transmit-clock-source: ---> {looptiming} line-length-meters: ------> {0} line-status-trap-enable: -> {enabled} channelization: ----------> {disabled} ds1-for-remote-loop: -----> {0} far-end-equip-code: ------> {} far-end-loc-id-code: -----> {} far-end-frame-id-code: ---> {} far-end-unit-code: -------> {} far-end-fac-id-code: -----> {} medium-scramble-config: --> {true} medium-frame-config: -----> {e3frameg832} medium-atmframe-config: --> {dsx3atmframingdirectcellmapped}
Configuring the DS3 interfaces This section explains how to configure DS3 interfaces. It applies to the DS3 card. Note: For redundant systems, configure the DS3 interfaces on both the active and standby cards. The following table summarizes the commands required to configure DS3 uplink interfaces on the MALC: Action
Command
Update the DS3 interfaces, which specify the basic parameters of the DS3 line, including framing, encoding, and clocking.
update ds3-profile 1-slot-port-0/ds3
Activate the DS3 interfaces in the if-translate and line-group profiles.
update if-translate 1-slot-port-0/ds3
where port is from 1 to 4
where port is from 1 to 4
The following section details how to configure the interface for the DS3 card. Activate the DS3 physical interface by issuing the update if-translate command: The DS3 card supports two timing modes:
868
MALC Hardware Installation Guide
–
Loop timing
–
Through timing
Configuring DS3 cards
Loop timing indicates that the timing source is coming from the line. Through timing indicates that the timing sources is from the backplane. The backplane can be set to receive its clocking signal from a port on an uplink card or ports on a line card. When through timing is used, the other side of the DS3 circuit should be set to loop timing. If loop timing is used and the card loses its received clock signal, clocking switches to the clock on the board. The clock mode is set in the DS3-profile using the transmit-clock-source parameter. To update the DS3 profile: zSH> update ds3-profile 1/6/1/0/ds3 Please provide the following: [q]uit. line-type: ---------------> {dsx3cbitparity}: line-coding: -------------> {dsx3b3zs}: send-code: ---------------> {dsx3sendnocode}: circuit-id: --------------> {}: loopback-config: ---------> {dsx3noloop}: transmit-clock-source: ---> {looptiming}: throughtiming line-length-meters: ------> {0}: line-status-trap-enable: -> {enabled}: channelization: ----------> {disabled}: ds1-for-remote-loop: -----> {0}: far-end-equip-code: ------> {}: far-end-loc-id-code: -----> {}: far-end-frame-id-code: ---> {}: far-end-unit-code: -------> {}: far-end-fac-id-code: -----> {}: medium-scramble-config: --> {true}: medium-frame-config: -----> {e3frameg832}: medium-atmframe-config: --> {dsx3atmframingdirectcellmapped}: .................... Save new record? [s]ave, [c]hange or [q]uit: s Record created.
Activating the interface profile 1
To activate the interface: zSH> update if-translate 1-6-4-0/ds3 Please provide the following: [q]uit. ifIndex: -----------------> {30}: shelf: -------------------> {1}: slot: --------------------> {6}: port: --------------------> {4}: subport: -----------------> {0}: type: --------------------> {ds3}: adminstatus: ------------> {up}: physical-flag: ----------> {true}: iftype-extension: -------> {none}: ifName: -----------------> {1-6-4-0}: redundancy-param1: ------> {0}: ................
MALC Hardware Installation Guide
869
DS3/E3
Save changes/ [s]ave, [c]hange or [q]uit:
2
The MALC automatically creates malcds3e3atm4.bin profile for each DS3 card installed. It does not matter which one you use.
3
Note that the framing and coding has to match on the local side and far side of the network. To check this, issue the following command and check the first two lines of the profile. zSH> get ds3-profile 1-6-1-0/ds3 line-type: --------------> {dsx3cbit parity} line-coding: ------------> {dsx3b3zs}
Creating VP-VC connections This procedure describes how to create VP-VC switched connections on the MALC-DS3/E3-4 card. This procedure involves the following steps:
•
Create ATM VPI profiles on the MALC-DS3/E3-4 card ports.
•
Add ATM VPI profiles and cross connections for the uplink and cellrelayproxy ports.
•
Add ATM VPL profiles and cross connections for the uplink and cellrelayproxy ports.
•
Add ATM VCL profiles and cross connections for the cellrelayproxy and DS3/E3 ports.
This procedure assumes that the MALC-DS3/E3-4 card is in slot 16 and creates cross connections between uplink VPs 20,21,22,23 and cellrelayproxy VPs 16,17,18,19. 1
Create ATM VPI profiles on the MALC-DS3/E3-4 card ports. zSH> new atm-vpi 1-6-1-0-ds3/atm/0 Please provide the following: [q]uit. zhoneAtmVpiMaxVci: ---> {0}: 64 zhoneAtmVpiSwitched: -> {vp}: vc zhoneAtmMaxVciPerVp: -> {0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved. zSH> new atm-vpi 1-6-2-0-ds3/atm/0 Please provide the following: [q]uit. zhoneAtmVpiMaxVci: ---> {0}: 64 zhoneAtmVpiSwitched: -> {vp}: vc zhoneAtmMaxVciPerVp: -> {0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved. zSH> new atm-vpi 1-6-3-0-ds3/atm/0 Please provide the following: [q]uit.
870
MALC Hardware Installation Guide
Configuring DS3 cards
zhoneAtmVpiMaxVci: ---> zhoneAtmVpiSwitched: -> zhoneAtmMaxVciPerVp: -> .................... Save new record? [s]ave, New record saved.
{0}: 64 {vp}: vc {0}: [c]hange or [q]uit: s
zSH> new atm-vpi 1-6-4-0-ds3/atm/0 Please provide the following: [q]uit. zhoneAtmVpiMaxVci: ---> {0}: 64 zhoneAtmVpiSwitched: -> {vp}: vc zhoneAtmMaxVciPerVp: -> {0}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
2
Add ATM VPI profiles and cross connections for the uplink and cellrelayproxy ports.
zSH> cc vpiadd uplink1/atm vp 20/0 1-6-4-0-cellrelayproxy/atm vp 0/0 256 maxvci is 256 create uplink atm-vpi profile Created atm-vpi uplink1/atm/20 create cellrelayproxy atm-vpi profile Created atm-vpi 1-6-4-0-cellrelayproxy/atm/16 zSH> cc vpiadd uplink1/atm vp 21/0 1-6-4-0-cellrelayproxy/atm vp 0/0 256 maxvci is 256 create uplink atm-vpi profile Created atm-vpi uplink1/atm/21 create cellrelayproxy atm-vpi profile Created atm-vpi 1-6-4-0-cellrelayproxy/atm/17 zSH> cc vpiadd uplink1/atm vp 22/0 1-6-4-0-cellrelayproxy/atm vp 0/0 128 maxvci is 128 create uplink atm-vpi profile Created atm-vpi uplink1/atm/22 create cellrelayproxy atm-vpi profile Created atm-vpi 1-6-4-0-cellrelayproxy/atm/18 zSH> cc vpiadd uplink1/atm vp 23/0 1-6-4-0-cellrelayproxy/atm vp 0/0 128 maxvci is 128 create uplink atm-vpi profile Created atm-vpi uplink1/atm/23 create cellrelayproxy atm-vpi profile Created atm-vpi 1-6-4-0-cellrelayproxy/atm/19
Perform a system reboot. 3
After, the system is rebooted, add ATM VPL profiles and cross connections for the uplink and cellrelayproxy ports.
zSH> cc vpladd uplink1/atm vp 20/0 1-6-4-0-cellrelayproxy/atm vp 16/0 td 1 Created atm-vpl uplink1/atm/20
MALC Hardware Installation Guide
871
DS3/E3
Created atm-vpl 1-6-4-0-cellrelayproxy/atm/16 Created atm-cc 1 zSH> cc Created Created Created
vpladd uplink1/atm vp 21/0 1-6-4-0-cellrelayproxy/atm vp 17/0 td 1 atm-vpl uplink1/atm/21 atm-vpl 1-6-4-0-cellrelayproxy/atm/17 atm-cc 2
zSH> cc Created Created Created
vpladd uplink1/atm vp 22/0 1-6-4-0-cellrelayproxy/atm vp 18/0 td 1 atm-vpl uplink1/atm/22 atm-vpl 1-6-4-0-cellrelayproxy/atm/18 atm-cc 3
zSH> cc Created Created Created
vpladd uplink1/atm vp 23/0 1-6-4-0-cellrelayproxy/atm vp 19/0 td 1 atm-vpl uplink1/atm/23 atm-vpl 1-6-4-0-cellrelayproxy/atm/19 atm-cc 4
Display the created VPLs. zSH> list atm-vpl atm-vpl uplink1/atm/20 atm-vpl 1-6-4-0-cellrelayproxy/atm/16 atm-vpl uplink1/atm/21 atm-vpl 1-6-4-0-cellrelayproxy/atm/17 atm-vpl uplink1/atm/22 atm-vpl 1-6-4-0-cellrelayproxy/atm/18 atm-vpl uplink1/atm/23 atm-vpl 1-6-4-0-cellrelayproxy/atm/19 8 entries found.
4
Configure the VCLs and cross connections.
zSH> cc add uplink1/atm vp 21/35 1-6-2-0-ds3/atm vc 0/37 td 1 zSH> cc add uplink1/atm vp 22/35 1-6-3-0-ds3/atm vc 0/37 td 1 zSH> cc add uplink1/atm vp 23/35 1-6-4-0-ds3/atm vc 0/37 td 1 zSH> cc add uplink1/atm vp 20/35 1-6-1-0-ds3/atm vc 0/37 td 1 zSH> list atm-vcl atm-vcl 1-6-4-0-cellrelayproxy/atm/16/35 atm-vcl 1-6-1-0-ds3/atm/0/37 atm-vcl 1-6-4-0-cellrelayproxy/atm/17/35 atm-vcl 1-6-2-0-ds3/atm/0/37 atm-vcl 1-6-4-0-cellrelayproxy/atm/18/35 atm-vcl 1-6-3-0-ds3/atm/0/37 atm-vcl 1-6-4-0-cellrelayproxy/atm/19/35 atm-vcl 1-6-4-0-ds3/atm/0/37 8 entries found. zSH> list atm-cc atm-cc 1
872
MALC Hardware Installation Guide
Configuring DS3 cards
atm-cc 2 atm-cc 3 atm-cc 4 atm-cc 5 atm-cc 6 atm-cc 7 atm-cc 8 8 entries found. zSH> get atm-cc 1 cc-index: ------> low-if-index: --> low-vpi: -------> low-vci: -------> high-if-index: -> high-vpi: ------> high-vci: ------> admin-status: --> handle-id: -----> zSH> get atm-cc 5 cc-index: ------> low-if-index: --> low-vpi: -------> low-vci: -------> high-if-index: -> high-vpi: ------> high-vci: ------> admin-status: --> handle-id: ----->
5
{1} {uplink1/atm} {20} {0} {1-6-4-0-cellrelayproxy/atm} {16} {0} {up} {handle_1} {5} {1-6-4-0-cellrelayproxy/atm} {16} {35} {1-6-1-0-ds3/atm} {0} {37} {up} {handle_5}
Use the cc show command to display the cross connects.
zSH> cc show ATM VCL CC ATM VCL HANDLE ID --------------------------------------------------------------------------uplink1/atm 20/35 Up 1 Up 1-6-1-0-ds3/atm 0/37 Up handle_1 uplink1/atm 21/35 Up 1 Up 1-6-2-0-ds3/atm 0/37 Up handle_1 uplink1/atm 22/35 Up 1 Up 1-6-3-0-ds3/atm 0/37 Up handle_1 uplink1/atm 23/35 Up 1 Up 1-6-4-0-ds3/atm 0/37 Up handle_1
MALC Hardware Installation Guide
873
DS3/E3
874
MALC Hardware Installation Guide
26
GPON CARD This chapter describes the MALC-GPON-SC1 card for GPON (Gigabit Passive Optical Networks). It includes:
•
Overview, page 875
•
Configuring a GPON interface, page 878
Overview The MALC-GPON-SC1 line card is a single-port interface that provides industry leading capabilities supporting 2.5 Gbps downstream bandwidth and 1.25 Gbps upstream bandwidth as specified in the G.984.1-4 specifications. The MALC can support up to 1280 GPON subscribers using Class B+ optics. In addition, when included in a MALC chassis with the voice gateway card, the GPON OLT line card provides a complete solution for service providers wanting to support Voice over IP. GPON technology provides one of the most cost effective ways for service providers to deploy fiber based services to the residential subscribers, businesses or other types of node. Utilizing GPON splitters that can be co-located with the MALC or remotely in the network the service provider can determine the best topology for their network. GPON OLT
Zhone's zNID GPON Residential Gateway completes Zhone's GPON solution with voice, video and data support.
MALC Hardware Installation Guide
875
GPON card
See the MALC Configuration Guide for procedures for configuration voice, video, and data connections on this card. The following features are supported:
•
Class B+ Optics with 28dB link budget
•
RF Overlay (1550nm wavelength)
•
64 subscribers per OLT line card
•
traffic management for IP QoS, traffic shaping, and dynamic bandwidth allocation
Table 116: PON OLT card specifications Specification
Value
Size
1 slot
Density
64 subscribers
Physical interfaces
SC-UPC fiber optic connector.
Line characteristics
Transmits voice and data traffic at a 1310nm wavelength Receives voice and data traffic at a 1490nm wavelength Receives video traffic at a 1550 nm wavelength
Redundancy
None
Nominal line rate
2.5 Gbps downstream and 1.25 Gbps upstream
Protocol support
Multicast IGMP v1/v3 Host-based routing Network-based routing IP host and gateway support RIP v1 (RFC 1058), RIP v2 (RFC 2453) DHCP server (RFC 2131, 2132), DHCP relay Bridging 802.1D VLAN 802.1Q/p Desense/sparse multicast
Power consumption
24 W nominal 28 W maximum
Creating card-profiles for PON OLT cards Each card installed in the system must have a card-profile. Each type of slot card requires different settings in the card-profile.
876
MALC Hardware Installation Guide
Overview
Tip: You can specify the name of the software image for a card in a card-profile or a type-module. Each card of a particular type can share a single type-module. Settings in type-modules can be overridden by settings in card-profiles. The slots cards on the MALC have the following types and software images: Card
Type
Name of software image
GPON
5076
malcgpon.bin
he following example creates a card-profile for a GPON card in shelf 1, slot 5: zSH> card add 1/5/5076
or zSH> new card-profile 1/5/5076 shelf/slot/type Please provide the following: [q]uit. sw-file-name: -----------> {malcgpon.bin}: admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {true}: sw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}: hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {unknowntype}: card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: maxvpi-maxvci: ----------> {notapplicable}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Verifying the slot card installation After you save the card-profile record, the slot card in that slot resets and the begins downloading their software image from the flash card. This could take a few moments. When the card has finished loading, a log message similar to the following is displayed (if logging is enabled): zSH> Card in slot slot-number changed state to RUNNING
You can also use the slots command and specify the slot number of the card to view the state of the card. For example:
MALC Hardware Installation Guide
877
GPON card
zSH> slots 5 Type : Card Version : EEPROM Version : Serial # : CLEI Code : Card-Profile ID : Shelf : Slot : ROM Version : Software Version: State : Mode : Heartbeat check : Longest hbeat : Fault reset : Uptime : Start time :
MALC GPON 1 1 110001 No CLEI 1/5/5076 1 5 development development RUNNING FUNCTIONAL enabled 51 enabled 44 minutes 1168985109
To view the status of all the cards, use the slots command without any arguments: zSH> slots Uplinks 1:*MALC RPR GIGE (RUNNING) Cards 3: MALC 4: MALC 5: MALC 6: MALC 9: MALC
GPON GPON GPON GPON GPON
(RUNNING) (RUNNING) (RUNNING) (RUNNING) (RUNNING)
Configuring a GPON interface This section provides an example of how to configure a GPON interface. When the MALC-GPON-SC-1 card profile is added on the MALC, the following GPON configuration profiles are created: Profile
Description
gpon-alloc-id
Specifies GPON bandwidth settings.
gpon-olt-config
Specifies the GPON settings on the MALC.
gpon-olt-onu-config
Enables communication with the zNID or ONU device based on vendor identification and password.
gpon-port-config
Used to set multicast and encryption settings and are identified by a sequential number from 501 to 564.
Use the list command to verify the available profiles.
878
MALC Hardware Installation Guide
Configuring a GPON interface
zSH> list gp gpon-alloc-id gpon-olt-config gpon-olt-onu-config gpon-port-config
Configuring GPON OLT parameters By default, the gpon-olt-config profile is configured for connections to an OLT device. To change the GPON OLT configuration, use the update command to edit the gpon-olt-config profile. zSH> update gpon-olt-config 1-8-1-1/gponolt Please provide the following: [q]uit. max-rt-propagation-delay: -> {200}: max-onu-response-time: ----> {50}: preassigned-eq-delay: -----> {0}: los-alpha: ----------------> {4}: lof-alpha: ----------------> {4}: loam-alpha: ---------------> {3}: scrambler: ----------------> {enabled}: fec-mode: -----------------> {disabled}: auto-learn: ---------------> {enabled}: power-level: --------------> {0}: guard-bit-count: ----------> {32}: dba-mode: -----------------> {predictive}: gem-block-size: -----------> {16}: us-ber-interval: ----------> {5000}: ds-ber-interval: ----------> {5000}: ber-sf-threshold: ---------> {3}: ber-sd-threshold: ---------> {5}: fec-request: --------------> {disabled}: key-exchange: -------------> {disabled}: min-rt-propagation-delay: -> {0}: min-onu-response-time: ----> {2}: eq-d-measure-cycles: ------> {2}: drift-ctrl-interval: ------> {1000}: drift-ctrl-limit: ---------> {3}: alloc-cycle-length: -------> {2}: min-us-alloc: -------------> {16}: ack-timeout: --------------> {2000}: pls-max-alloc-size: -------> {120}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Configuring GPON ONU parameters The MALC-GPON-SC-1 card supports up to 64 ONU devices and provides a gpon-olt-onu-config profile for each ONU device. This profile enables communication with the zNID or ONU device based on vendor identification and password. The available parameters include:
MALC Hardware Installation Guide
879
GPON card
•
Vendor ID
•
Vendor specific ID
•
Password authorization The MALC-GPON-SC-1 card supports 64 ONU’s, 32 active and 64 provisioned. For each ONU, the MALC assigns a logical gponport entity for provisioning. The gponports are number 501 to 564 and replace the subport number in the interface name. For example, 1-8-1-501/gponport is the first interface available on an ONU. The gponport number corresponds to the allocID used when adjusting guaranteed bandwidth. On the MALC, use the gponoun commands to display available ONUs and update the gpon-olt-onu-config profile to enable communication with the zNID or ONU device. This example updates the profile for ONU 1 with the MALC-GPON-SC-1 card in slot 8 using OLT 1.
Display line status on shelf 1, slot 8. zSH> showline 1 8 Search in progress ......... -----------------------------------------------------------------------shelf = 1, slot = 8, line type = OLT line 1-12 ACT -----------------------------------------------------------------------shelf = 1, slot = 8, port 1, line type = ONU subport 1-12ACTACTOOSOOSOOSOOSOOSOOSOOSOOSOOSOOS 13-24OOSOOSOOSOOSOOSOOSOOSOOSOOSOOSOOSOOS 25-36 OOS OOS OOS OOS OOS OOS OOS OOS OOS OOS OOS OOS 37-48 OOS OOS OOS OOS OOS OOS OOS OOS OOS OOS OOS OOS 49-60 OOS OOS OOS OOS OOS OOS OOS OOS OOS OOS OOS OOS 61-72 OOS OOS OOS OOS
Display the unassigned ONU’s for OLT 1. Note the discovered serial numbers and serial number IDs. zSH> gpononu show 8/1 Free ONUs for slot 8 olt 1: 1 2 4 5 6 7 8 9 10 11 14 15 16 17 18 19 20 21 22 23 26 27 28 29 30 31 32 33 34 35 38 39 40 41 42 43 44 45 46 47 50 51 52 53 54 55 56 57 58 59 62 63 64 Discovered serial numbers for slot 8 olt 1: sernoID Vendor Serial Number sernoID Vendor 1 ZNTS 220001 2 ZNTS 220002
880
MALC Hardware Installation Guide
12 24 36 48 60
13 25 37 49 61
Serial Number
Configuring a GPON interface
Assign the available ONU 2 with serial number ID (sernoID) 2. By not specifying a name, the default name is used. The default ONU upstream bandwidth is 512 Kbps. Bandwidth must be specified in 1/2 Mb increments (.5=512Kbps, 1= 1Mbps, 1.5=1.5 Mbps). The ONU number can also be used to specify a ONU. For example, ONU2 instead of 8/1/2. zSH> gpononu set 8/1/2 2 bw 4.5 Onu 2 successfully enabled with serial number ZNTS 220002 Bandwidth has been successfully chaged from 1 to 4.5 Mb/sec zSH> MAR 12 11:53:01: alert : 1/8/1025: alarm_mgr: 01: 8:01:02 Critical ONU Up Line 1/8/1/2/gpononu CAUSE: active
Check the ONU bandwidth setting. zSH> gpononu bw 8/1/2 Current bandwidth allocation is 4.5 Mbits/sec
Show all ONU’s on the MALC. zSH> gpononu showall Slot 8 olt 1 Onu Name Enabled Serial Number BW(Mb) GponPorts 1 1-8-1-1 Yes ZNTS 220001 1 1-8-1-501/gponport 2 1-8-1-2 Yes ZNTS 220002 4.5 1-8-1-502/gponport 3 1-8-1-3 No ZNTS 0 0 1-8-1-503/gponport 4 1-8-1-4 No ZNTS 0 0 1-8-1-504/gponport 5 1-8-1-5 No ZNTS 0 0 1-8-1-505/gponport for next page, for next line, A for all, Q to quit
Show only the ONU 2. zSH> gpononu showall 8/1/2 Slot 8 olt 1 Onu Name Enabled 1
1-8-1-2Yes
Serial Number BW(Mb)
GponPorts
ZNTS 220002 4.51-8-1-502/gponport
Show only the enabled ONU’s. zSH> gpononu showall 8/1 enabled Slot 8 olt 1 Onu Name Enabled Serial Number BW(Mb) 11-8-1-1Yes ZNTS 22000111-8-1-501/gponport 21-8-1-2Yes ZNTS 2200218.51-8-1-502/gponport Total onus = 2 bandwidth = 19.5
GponPorts
Clear or deactivate ONU 2. zSH> gpononu clear 8/1/2 Onu 2 (previously enabled with serial number ZNTS 220002) has been cleared zSH> MAR 12 14:17:13: alert : 1/8/1025: alarm_mgr: 01: 8:03:01 Critical ONU Down Line 1/8/1/2/gpononu CAUSE: inactive
MALC Hardware Installation Guide
881
GPON card
Configuring GPON port parameters By default, the gpon-port-config profile is configured for connections to an OLT device. To change the GPON port configuration, use the update command to edit the gpon-port-config profile. The gpon-port-config profiles are identified by a sequential number from 501 to 564. zSH> update gpon-port-config 1-8-1-501/gponport Please provide the following: [q]uit. multicast: -> {false}: encrypted: -> {false}: direction: -> {bidirectional}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Configuring GPON bandwidth parameters By default, the gpon-alloc-id profile contains the settings for the bandwidth for connections to an OLT device. To change the GPON bandwidth settings, use the update command to edit the gpon-alloc-id profile. The default ONU bandwidth is 1 Mbps. The guaranteed bandwidth must be set to a number divisible by 512. zSH> update gpon-alloc-id 1-8-1-0-gponolt/linegroup/501 Please provide the following: [q]uit. onu-id: --------> {1}: guaranteed-bw: -> {100}: traffic-class: -> {ubr}: compensated: ---> {true}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
GPON configuration The MALC supports configuring GPON voice, data, and video connections between the MALC-GPON-SC-1 card and the Zhone zNID CPE. By default, the following VLANs are configured on the Zhone zNID:
•
VLAN 100 for video traffic
•
VLAN 200 for data traffic
•
VLAN 300 for VoIP and management traffic
Example GPON configurations specifying the gponport 502:
882
MALC Hardware Installation Guide
GPON configuration
zSH> host add 1-8-1-502/gponport vlan 100 dynamic 43 5 video 1/5 Adding host for 1-8-1-502/gponport zSH> bridge add 1-8-1-502/gponport downlink vlan 200 tagged Adding bridge on 1-8-1-502/gponport Created bridge-interface-record 1-6-1-564-gponport-200/bridge zSH> host add 1-8-1-502/gponport vlan 300 static 172.25.44.64 Adding host for 1-8-1-502/gponport
MALC Hardware Installation Guide
883
GPON card
Multiple GEM Ports The GPON OLT line card can support one multicast GPON Encapsulation Method (GEM) port, or up to three unicast GEM ports per ONT. The three unicast GEM port IDs have fixed numbering of 501–532, 701–732, and 901 – 932. Each ONT has been assigned a set of three GEM port IDs automatically. For example, for ONT ID 1, the three GEM port IDs are 501, 701, and 901. The following example shows the GEM port IDs assignment in ONT 1 and ONT 2: zSH> Slot Onu 1
gpononu gemports 3 olt 1 Name GemPorts Admin 1-3-1-1 1-3-1-501/gponport UP 1-3-1-701/gponport UP 1-3-1-901/gponport UP 2 1-3-1-2 1-3-1-502/gponport UP 1-3-1-702/gponport UP 1-3-1-902/gponport UP for next page, for next line, A quit Q
BW(Mbits/sec) 18 0.5 0.5 18 0.5 0.5 for all, Q to
Note that the zNID-GPON-4200 ONT only requires one GEM port (5XX) because it can perform traffic shaping on a per VLAN basis inside of that single GEM port.
Activating ONTs Use gpononu set command to activate ONTs. The gpononu set command syntax is: gpononu set slot/olt/onu | interfaceName [sernoID] [bw [gemport ID/] value][omci omci filename | noomci] To active ONT 3/1/1, perform the following tasks: 1
View all the free ONTs, serial numbers under the OLT 3/1:
zSH> gpononu show 3/1 Free ONUs for slot 3 olt 1: 1 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Discovered serial numbers for slot 3 olt 1: sernoID Vendor Serial Number sernoID Vendor Serial Number 9 ZNTS 266175
2
Assign the ONT 3/1/1 with sernoID 9 (the sernoID 9 is associated with serial number 266175) to activate ONT 3/1/1.
zSH> gpononu set 3/1/1 9 Onu 1 successfully enabled with serial number ZNTS 266175
3
884
MALC Hardware Installation Guide
Verify ONT 3/1/1 is activated with serial number 266175.
Multiple GEM Ports
zSH> gpononu show 3/1/1 Slot 3 olt 1 Onu Name Enabled 1 1-3-1-1 Yes
4
Serial Number ZNTS 266175
OMCI filename (none)
If you want to disable an ONT, but still keep the serial number for this ONT, use the port down command. zSH> port down 1-3-1-1/gpononu 1-3-1-1/gpononu set to admin state DOWN
5
If you want to disable an ONT, and clear the serial number for this ONT, use the gpononu clear command.
zSH> gpononu clear 3/1/1 Onu1 (previously with serial number ZNTS 266175) has been cleared
GPON alloc-ID profile The GPON alloc-ID profile is associated with each GEM port. In the GPON alloc-ID profile, the users can specify bandwidth, traffic class, and compensation mode for the upstream traffic of the GEM port. Use get gpon-alloc-id command to show the GEM port settings in the alloc-ID profile: zSH> get gpon-alloc-id 1-4-2-0-gponolt/linegroup/501 gpon-alloc-id 1-4-2-0-gponolt/linegroup/501 onu-id: --------> {1} guaranteed-bw: -> {10240} traffic-class: -> {ubr} compensated: ---> {false}
•
guaranteed-bw: The bandwidth value is multiple of 512 kbps. By default, the value is 512 kpbs.
•
traffic-class: The traffic class value is UBR or CBR.
•
compensated: For CBR, the compensation mode can be “true” or “false”. Sometimes access can be skipped because of the ranging window. In this case CBR access can be compensated immediately after the ranging window to prevent possible jitter of the CBR channel.
Modifying upstream bandwidths for GEM ports The gpononu set command can change the upstream bandwidths for multiple GEM ports. However the traffic-class and compensation mode (compensated) can only be modified in the gpon-alloc-id profile. The following example assigns ONT 3/1/1 with serial number ID (sernoID) 9, and changes upstream bandwidths for GEM ports 501 and 901 to 12 mbps and 1 mbps respectively:
MALC Hardware Installation Guide
885
GPON card
zSH> gpononu set 3/1/1 9 bw 501/12 bw 901/1 Onu 1 successfully enabled with serial number ZNTS 266175
The following example changes upstream bandwidth for ONT 3/1/1 GEM port 501 without assigning the serial number. Specifying bw value instead of bw gemport ID / value indicates the bandwidth value is assigned to the default GEM port 5xx (i.e. GEM port 501 in this example): zSH> gpononu set 3/1/1 bw 12 Bandwidth for 501 has been changed from 18Mbps to 12 Mbps
GPON OMCI configuration The MALC supports configuring GPON data, voice, and video connections between the MALC-GPON-SC-1 card and third party ONTs. For these third party ONTs, the MALC supports three GEM ports per ONT and vendor-specific OMCI file configuration.
OMCI file The OMCI file (a standards-based ONT Management and Control Interface file) is supplied by Zhone Technologies for use with the OMCI-enabled ONTs. The OMCI file contains the commands used to configure the ONTs that are related to customer premises equipment (CPE) devices. The OMCI file must be downloaded from the server, placed in the OMCI directory, and that filename must be entered in the gpon-olt-onu-config file.
Downloading an OMCI file At first create the OMCI directory, and then download an OMCI file into this directory. 1
Create a directory at the root level. The name of the directory must be omci.
2
Download the OMCI file to the omci directory, in this example the OMCI file is cigprov_eth3_fxs.txt.
zSH> mkdir /omci
zSH> filedownload 172.16.80.201 pathname/cigprov_eth3_fxs.txt /omci/ cigprov_eth3_fxs.txt
886
MALC Hardware Installation Guide
GPON OMCI configuration
Associating the OMCI file with the ONT The following example shows how to associate the OMCI file cigprov_eth3_fxs.txt with ONT 3/1/1: 1
View all the free ONTs, serial numbers under the OLT 3/1:
zSH> gpononu show 3/1 Free ONUs for slot 3 olt 1: 1 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Discovered serial numbers for slot 3 olt 1: sernoID Vendor Serial Number sernoID Vendor Serial Number 9 ZNTS 266175
2
Assign the ONT 3/1/1 with sernoID 9 (the sernoID 9 is associated with serial number 266175) to activate ONT 3/1/1.
zSH> gpononu set 3/1/1 9 Onu 1 successfully enabled with serial number ZNTS 266175
3
Associate the ONT 3/1/1 with the OMCI file cigprov_eth3_fxs.txt.
zSH> gpononu set 3/1/1 omci cigprov_eth3_fxs.txt
4 zSH> Slot Onu 1
Verify that the ONT 3/1/1 is associated with the OMCI file cigprov_eth3_fxs.txt.
gpononu show 3/1/1 3 olt 1 Name Enabled Serial Number 1-3-1-1 Yes ZNTS 266175
5
OMCI filename cigprov_eth3_fxs.txt
Verify that the gpon-olt-onu-config file contains correct values for onu-added and the OMCI-file-name parameter. zSH> get gpon-olt-onu-config 1-3-1-1/gpononu gpon-olt-onu-config 1-3-1-1/gpononu serial-no-vendor-id: -------> {ZNTS} serial-no-vendor-specific: -> {266175} password: ------------------> {} auto-learn: ----------------> {enabled} power-level: ---------------> {0} us-ber-interval: -----------> {5000} ds-ber-interval: -----------> {5000} onu-added: -----------------> {true} omci-file-name: ------------> {cigprov_eth3_fxs.txt} zSH>
MALC Hardware Installation Guide
887
GPON card
Service configuration Example GPON configurations specifying the GEM ports 501, 701, and 901 for ONT 3/1/1. GEM port 501 is configured for data service, GEM port 701 is for voice service, and GEM port 901 is for video service. zSH> bridge add 1-3-1-501/gponport downlink vlan 100 tagged for line side Adding bridge on 1-3-1-501/gponport Created bridge-interface-record 1-3-1-501-gponport-200/bridge zSH> bridge add 1-1-1-0/ethernetsmacd uplink vlan 100
for uplink side
Refer to VLANs on page 108 for the overall VLAN bridging configuration. zSH> host add 1-3-1-701/gponport vlan 200 static 172.25.44.64 Adding host for 1-3-1-701/gponport
Voice service
zSH> host add 1-3-1-901/gponport vlan 300 dynamic 43 5 video 1/5 Video service Adding host for 1-3-1-901/gponport
Refer to Configuring the MALC for video on page 513 for the overall video configuration.
Commands for GPON configurations gpononu For GPON configurations, sets and displays ONU and serial number associations. Syntax The following command can associate a serial number with an ONU and
enable the ONU; can sets upstream bandwidth for GPON Encapsulation Method (GEM) port (s); also can associate a OMCI file with an ONU. gpononu set slot/olt/onu | interfaceName [sernoID] [bw [gemport ID/] value][omci omci filename | noomci]
sernoID Serial number ID is an ID number displayed in gpononu show command output. If sernoID is omitted in the gpononu set command, this command modifies bandwidth and / or omci filename only. [bw [gemport ID/] value]
It sets upstream bandwidth. If no GEM port ID is given, then the default GEM port (5xx) is used. In that case, use bw value to set bandwidth for the GEM port (5xx) gemport. The upstream bandwidth must be multiple of 512 kilobits/sec. e.g. 12 for 12 Megabits/sec, 1.5 for 1536 Kilobits/sec. By default, the bandwidth is 512 kbps. omci omci filename
888
MALC Hardware Installation Guide
GPON OMCI configuration
It indicates omci provisioning, using named file. noomci
It indicates omci is not used (default). Syntax The following command displays the names and bandwidth of GEM ports for
selected ONU(s). gpononu gemports [slot[/olt[/onu]] | interfaceName] Syntax The following command displays the operating status and gpon onu line
status for selected ONU(s). gpononu status [slot[/olt[/onu]] | interfaceName] Syntax The following command displays the available ONUs and the discovered
serial numbers for OLT(s). gpononu show [slot[/olt]] Syntax The following command displays ONUs with serial number data and other
information. gpononu showall [slot[/olt[/onu]] | interfaceName] [enabled] [free] [all] Syntax The following command disable an ONU and clear the serial number to
default. gpononu clear slot/olt/onu | interfaceName Example zSH> gpononu show 8/1 Free ONUs for slot 8 olt 1: 1 2 4 5 6 7 8 9 10 11 14 15 16 17 18 19 20 21 22 23 26 27 28 29 30 31 32 33 34 35 38 39 40 41 42 43 44 45 46 47 50 51 52 53 54 55 56 57 58 59 62 63 64 Discovered serial numbers for slot 8 olt 1: sernoID Vendor Serial Number sernoID Vendor 1 ZNTS 220001 2 ZNTS 220002
12 24 36 48 60
13 25 37 49 61
Serial Number
Assign the available ONU 2 with serial number ID (sernoID) 2. By not specifying a name, the default name is used. The default alloc-id bandwidth is 512Kbps. The ONU number can also be used to specify a ONU. For example, ONU2 instead of 8/1/2. And also by not specifying gemport ID, the gemport 5xx is used. zSH> gpononu set 8/1/2 2 bw 4.5 Onu 2 successfully enabled with serial number ZNTS 220002
MALC Hardware Installation Guide
889
GPON card
Bandwidth has been successfully chaged from 1 to 4.5 Mb/ sec zSH> MAR 12 11:53:01: alert : 1/8/1025: alarm_mgr: 01: 8:01:02 Critical ONU Up Line 1/8/1/2/gpononu CAUSE: active
Set bandwidth and OMCI filename to ONU 8/1/2 GEM port 512 without assigning the serial number. zSH> gpononu set 8/1/2 bw 4.5 omci cigprov_eth3_fxs.txt
Show the GPON ONU names, admin status, and bandwidth for all GEM ports associated with the ONU. zSH> Slot Onu 1
2
gpononu gemports 3 olt 1 Name GemPorts Admin 1-3-1-1 1-3-1-501/gponport UP 1-3-1-701/gponport UP 1-3-1-901/gponport UP 1-3-1-2 1-3-1-502/gponport UP 1-3-1-702/gponport UP 1-3-1-902/gponport UP
BW(Mbits/sec) 18 0.5 0.5 18 0.5 0.5
...
Check the ONU bandwidth setting. zSH> gpononu bw 8/1/2 Current bandwidth allocation is 4.5 Mbits/sec
Show all ONU’s on the MALC. zSH> gpononu showall Slot 8 olt 1 Onu Name Enabled Serial Number 1 1-8-1-1 No TXPO 754975236 2 1-8-1-2 Yes TXPO 754975233 3 1-8-1-3 No ZNTS 0 ...
OMCI filename txpces1 txpces2 (none)
Show only the ONU 2. zSH> gpononu showall 8/1/2 Slot 8 olt 1 Onu Name Enabled Serial Number 2 1-8-1-2 Yes TXPO 754975233
OMCI filename txpces2
Show only the enabled ONU’s. zSH> gpononu showall 8/1 enabled Slot 8 olt 1 Onu Name Enabled Serial Number 2 1-8-1-2 Yes TXPO 754975233 Total ONUs = 1
890
MALC Hardware Installation Guide
OMCI filename txpces2
GPON OMCI configuration
Clear or deactivate ONU 2. zSH> gpononu clear 8/1/2 Onu 2 (previously enabled with serial number ZNTS 220002) has been cleared zSH> MAR 12 14:17:13: alert : 1/8/1025: alarm_mgr: 01: 8:03:01 Critical ONU Down Line 1/8/1/2/gpononu CAUSE: inactive
Show the OMCI file name for the ONU. zSH> get gpon-olt-onu-config 1-3-1-1/gpononu gpon-olt-onu-config 1-3-1-1/gpononu serial-no-vendor-id: -------> {ZNTS} serial-no-vendor-specific: -> {266175} password: ------------------> {} auto-learn: ----------------> {enabled} power-level: ---------------> {0} us-ber-interval: -----------> {5000} ds-ber-interval: -----------> {5000} onu-added: -----------------> {true} omci-file-name: ------------> {cigprov_eth3_fxs.txt} zSH>
Change the settings on ONU. zSH> update gpon-olt-onu-config 1-9-1-6/gpononu gpon-olt-onu-config 1-9-1-6/gpononu Please provide the following: [q]uit. serial-no-vendor-id: -------> {TXPO}: serial-no-vendor-specific: -> {754975317}: password: ------------------> {}: auto-learn: ----------------> {enabled}: power-level: ---------------> {0}: us-ber-interval: -----------> {5000}: ds-ber-interval: -----------> {5000}: onu-added: -----------------> {false}: omci-file-name: ------------> {cigprov_eth3_fxs.txt}: .................... Save changes? [s]ave, [c]hange or [q]uit: Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Show the GPON alloc-ID profile for each GEM port. zSH> get gpon-alloc-id 1-4-2-0-gponolt/linegroup/501 gpon-alloc-id 1-4-2-0-gponolt/linegroup/501 onu-id: --------> {1} guaranteed-bw: -> {10240} traffic-class: -> {ubr} compensated: ---> {false}
MALC Hardware Installation Guide
891
GPON card
VLAN configuration Example GPON configurations specifying the GEM ports 502, 702, and 902 for ONU 2: zSH> host add 1-8-1-502/gponport vlan 100 dynamic 43 5 video 1/5 Adding host for 1-8-1-502/gponport zSH> bridge add 1-8-1-702/gponport downlink vlan 200 tagged Adding bridge on 1-8-1-702/gponport Created bridge-interface-record 1-6-1-702-gponport-200/bridge zSH> host add 1-8-1-902/gponport vlan 300 static 172.25.44.64 Adding host for 1-8-1-902/gponport
892
MALC Hardware Installation Guide
27
ACTIVE ETHERNET This chapter describes the MALC-ACTIVE-ETH-10 port card and explains how to configure it. It includes:
•
Active Ethernet 10 port card, page 894
•
Small form factor pluggables, page 896
•
Displaying and updating Ethernet interfaces, page 898
•
Configuring Active Ethernet ports, page 899
•
Active Ethernet with ATM and IP uplink cards, page 899
MALC Hardware Installation Guide
893
Active Ethernet
Active Ethernet 10 port card The MALC-ACTIVE-ETH-10 1 port card supports Ethernet traffic over 10 SFPs that provide 10/100/1000 Base-T, fiber 100FX or Gigabit Ethernet interfaces, supporting distances as high as 80km. The Active Ethernet card is also interoperable third party Active Ethernet devices. The Active Ethernet card runs supports Layer 2 bridging functions, Layer 2 security functions, Layer 3 routing functions and the Zhone Multimedia Traffic Management functionality (MTM). This card is commonly used with XDSL and B-PON access cards for GigE voice, data, and video solutions. This card supports non-redundant GigE connections to subtended MALC uplinks. GigE traffic can be passed to redundant linear and RPR MALC uplink connections.
Table 117: Active specifications
894
Specification
Description
Size
1 slot
Density
10 ports GigE ports
MALC Hardware Installation Guide
Active Ethernet 10 port card
Table 117: Active specifications (Continued) Specification
Description
Physical interfaces
10/100/1000 Ethernet ports with SFPs. The optical interfaces are class 1 Laser International Safety Standard IEC 825 compliant Ten Gigabit Ethernet ports with SFPs. The SFPs can be twisted pair 1000baseT or fiber (SX, LX or ZX). See Small form factor pluggables on page 896.
Standards supported
IEEE 802.3 IEEE 802.1 Q/P IEEE 802.1 AD (Q in Q)
Management interface
Management Ethernet 10/100 port routable for connecting to other Ethernet devices SNMP
Power consumption
25 W
Adding Active Ethernet cards To add an Active Ethernet card to the system: 1
Install the Active Ethernet card in the desired line card slot.
2
Create a card-profile for the card:
zSH> card add 1/1/5071
or zSH> new card-profile 1/1/5071 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {}: malcacteth10.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {enable}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {0}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s
MALC Hardware Installation Guide
895
Active Ethernet
New record saved.
3
Connect the line-side cables to the SFP connectors on the Active Ethernet card.
Verifying Active Ethernet cards To verify an Active Ethernet card has been added to a specified slot in the system: Use the slots command to display the cards configured for each slot: zSH> slots 1:*MALC RPR GIGE NT (RUNNING) 2: MALC RPR GIGE NT (RUNNING) 9: MALC ACT ETH 10 (RUNNING) zSH>
Small form factor pluggables Zhone Technologies supports a variety of small form factor pluggables (SFPs) which you select depending on the protocol, fiber type and distance requirements. These SFPs (optical transceivers) are high performance integrated duplex data links for bi-directional communication over multimode or single mode optical fiber. All Zhone Technologies SFPs are equipped with LC receptacles, which are compatible with the industry standard LC connector. These SFP transceivers measure 0.532 inches in width and provide double port densities by fitting twice the number of transceivers into the same board space as a 1x9 transceiver. All supported SFPs are hot-swappable, therefore enabling SFPs to be easily changed regardless of whether the power is on. Furthermore, this opto-electronic transceiver module is a class 1 laser product compliant with FDA Radiation Performance Standards, 21 CFR Subchapter J. This component is also class 1 laser compliant according to International Safety Standard IEC-825-1. Figure 104: Small form factor pluggable.
896
MALC Hardware Installation Guide
Active Ethernet 10 port card
Zhone Technologies supports 4 types of Gigabit Ethernet SFPs:
•
GE-SFP-SX: This is a 850 nm, multimode SFP, used in applications that are up to 5 km.
•
GE-SFP-LX: This is a 1310 nm, singlemode SFP, used in applications that are up to 10km.
•
GE-SFP-ZX: This is a 1550 nm, singlemode SFP, used in applications that are up to 80 km.
•
GE-SFP-TP: This is a twisted pair SFP for access to a twisted pair GigaBit Ethernet network. It supports data rates of up to 1.25 Gbps over distances of 100 m (per IEEE 802.3).
•
FE-SFP-LX: This is a 1310 nm, singlemode SFP used in applications that are up to 10km for 100 Mbps.
Table 118 describes the optical SFP specifications. Table 118: SFP specifications Specification
SX
LX
ZX
LX (FE)
Data rate
1.062 to 1.25 Gbps
1.062 to 1.25 Gbps
1.062 to 1.25 Gbps
100 Mbps
Fiber Interface
G.652
G.652
G.652
G.652
Operating wavelength range
830-860 nm
1274-1360 nm
1535-1565 nm
1270-1355 nm
Maximum distance supported
500 meters
10 km
80 km
10 km
Source type
multimode
singlemode
singlemode
singlemode
Power
-9.5dBm (minimum)
-9 dBm (minimum)
2 dBm (typical)
-15 dBm (minimum)
0 dBm (maximum)
-3 dBm (maximum)
Operating temperature
min 00 C, max 700 C
min 00 C, max 700 C
min 00 C, max 700 C
min 00 C, max 700 C
Spectral characteristics: max. –20 dB width
0.85 nm
4 nm
1 nm
7.7 nm
Minimum extinction ratio
9 dB
9 dB
9 dB
9 dB
Relative intensity noise (RIN) (max.)
-117 dB
-120 dB
-120 dB
—
Optical Rise/Fall Time
300 ps
260 ps
260 ps
3 ns
Deterministic jitter (max.)
85 ps
80 ps
—
0.305 UI
Transmitter
-8 dBm (maximum)
MALC Hardware Installation Guide
897
Active Ethernet
Table 118: SFP specifications (Continued) Specification
SX
LX
ZX
LX (FE)
Total Jitter Output (pk-pk) (max.)
251 ps
227 ps
200 ps
0.40 UI
-17 dBm (minimum)
-20 dBm (minimum)
-24 dBm (minimum)
-28 dBm
0 dBm (maximum)
-3 dBm (maximum)
0 dBm to -3 dBm (maximum) with damage threshold at 6 dBm
Reflectance at the receiving point
—
-14 dB
-14 dB
—
Deterministic jitter (max.)
113 ps
170 ps
—
0.305 UI
Total Jitter Output (pk-pk) (max.)
266 ps
266 ps
—
0.51 UI
Receiver Sensitivity
Displaying and updating Ethernet interfaces The list, get, and update commands support use of the interface shelf-slot-port-subport/ethernetcsmacd syntax to facilitate Ethernet port and interface monitoring and configuration. To list the currently configured Ethernet interfaces, enter the list ether command. zSH> list ether ether 1-1-1-0/ethernetcsmacd ether 1-1-2-0/ethernetcsmacd ether 1-2-1-0/ethernetcsmacd ether 1-2-2-0/ethernetcsmacd ether 1-6-1-0/ethernetcsmacd ether 1-6-2-0/ethernetcsmacd ether 1-6-3-0/ethernetcsmacd ether 1-6-4-0/ethernetcsmacd ether 1-6-5-0/ethernetcsmacd ether 1-6-6-0/ethernetcsmacd ether 1-6-7-0/ethernetcsmacd ether 1-6-8-0/ethernetcsmacd ether 1-6-9-0/ethernetcsmacd ether 1-6-10-0/ethernetcsmacd 14 entries found.
To update an Ethernet interface, enter the update command followed by the interface index.
898
MALC Hardware Installation Guide
Active Ethernet 10 port card
zSH> update ether 1-6-1-0/ethernetcsmacd Please provide the following: [q]uit. autonegstatus: -> {enabled}: disabled mauType: -------> {mau1000basetfd}: restart: -------> {norestart}: ifType: --------> {mau1000basetfd}: autonegcap: ----> {b10baseT+b10baseTFD+b100baseTX+b100baseTXFD+bFdxBPause+b1000baseT+b1000baseTF D}: remotefault: ---> {noerror}: clksrc: --------> {automatic}: .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Configuring Active Ethernet ports Configure the Active Ethernet ports for bridges or IP interfaces. See Configuring Bridging and Configuring IP chapters.
Active Ethernet with ATM and IP uplink cards All uplink cards can support the Active Ethernet card. By default, Active Ethernet cards boot up with 10 AAL5PROXY connections (one per Active Ethernet port) connected to the uplink card. On the IP-based uplink cards, the AAL5PROXY connections are the only connections used between the uplink card and the line card. On uplink cards that support ATM and IP, the default AAL5PROXY connections can be replaced by ATM-based cross connections. Only one connection per port can be active at any given time, either an ATM-based cross connection or the default AAL5PROXY connection. To configure an ATM cross connect from an ATM uplink port to an Active Ethernet port, use the cc add command. This example creates an ATM cross connection using traffic descriptor 1 between VC 0/35 on the uplink card named uplinlk1 and VC 0/45 on port 1 on the Active Ethernet card in slot 14 on shelf 1. If the ATM cross connect is configure and then deleted, the AAL5PROXY will become the active connection for that port. zSH> cc add uplink1/atm vc 0/35 1-14-1-0/ethernetcsmacd vc 0/45 td 1 Note: No VPI/VCI is actually used on the Active Ethernet port.
Flexible configurations This card supports non-redundant GigE connections to subtended MALC uplinks. GigE traffic can be passed to redundant linear and RPR MALC uplink connections.
MALC Hardware Installation Guide
899
Active Ethernet
900
MALC Hardware Installation Guide
28 ISDN
This chapter describes the MALC ISDN cards and explains how to configure them. It includes:
•
Overview, page 901
•
MALC-ISDN-4B3T-24, page 902
•
MALC-ISDN-2B1Q-24, page 908
Overview The MALC supports MALC-ISDN-4B3T-24 and MALC-ISDN-2B1Q-24 cards. The MALC-ISDN-4B3T-24 line card provides 24 ports of ISDN with 4B3T line coding. The MALC-ISDN-2B1Q-24 line card provides 24 ports of ISDS with 2B1Q line coding. These cards can support TDM voice or packet voice.
MALC Hardware Installation Guide
901
ISDN
MALC-ISDN-4B3T-24 active fault pwr fail
The MALC-ISDN-4B3T-24 line card provides 24 ports of ISDN with 4B3T line coding. This card can support TDM voice or packet voice.
1-24
ma0512
ISDN 4B3T 24
Table 119: MALC-ISDN-4B3T-24 specifications Specification
Value
Size
1 slot
Density
24 ports 1 D-channel and 2 B-channels per port
Physical interfaces
One (1) RJ-21X Champ 50-pin connector
ISDN line characteristics
144 kbps line rate 135 Ohm resistive line impedance 95V @ 45mA loop power 24 AWG 22,000 feet (maximum operational reach) 26 AWG 18,000 feet (maximum operational reach)
902
MALC Hardware Installation Guide
MALC-ISDN-4B3T-24
Table 119: MALC-ISDN-4B3T-24 specifications (Continued) Specification
Value
Redundancy
None
Line encoding
4B3T
Nominal line rate
80 kbps 5 ppm
Longitudinal balance:
500 Hz to 40 kHz: greater than 55 dB
Input return loss
greater than 20 dB, 10 kHz to 25 kHz roll-off 20 dB per decade to 1 kHz and 250 kHz
Free-run line rate (Stratum 4) if timing reference is lost
80 kbps 32 ppm
Power consumption
45 watts
40 kHz to 1 MHz: roll-off -20 dB per decade
Creating card-profiles for MALC-ISDN-4B3T-24 cards Each card installed in the system must have a card-profile. Each type of slot card requires different settings in the card-profile. MALC-ISDN-4B3T-24 cards can be configured for ISDN or packet voice support in the card profile. ISDN is used if the call is being routed out a TDM interface. Packet voice is used if ISDN calls are to be routed through a MALC voice gateway card. If configured for packet voice, ISDN signaling is only applicable if the card is connected to an NT interface. The following table describes the parameters in the card-profile for the MALC-ISDN-4B3T-24 card:
MALC Hardware Installation Guide
903
ISDN
Parameter
Description
sw-file-name
Software image for the card. The ISDN 2B1Q, MALC-ISDN-4B3T-24, and global POTS cards all use the same image. Values: malculcs.bin
card-line-type
The type of calls supported on this card. Values: pots TDM POTS. pots-pv POTS over packet voice. isdn ISDN. Used for 2B1Q and 4B3T. isdn-pv ISDN over packet voice. pots-coin TDM POTS with coin support. pots-coin-pv POTS over packet voice with coin support.
card-line-voltage
The voltage supplied to each ISDN port. Values: not-used 60-volts 68-volts 95-volts 100-volts 110-volts
1
The following example creates a card-profile for a ULCS or IMALC-ISDN-4B3T-24 card in shelf 1, slot 5:
zSH> card add 1/5/5049 linetype isdn | isdn-pv
or zSH> new card-profile 1/5/5049 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {}: malculcs.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {0}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: isdn | isdn-pv card-atm-configuration: -> {notapplicable}
904
MALC Hardware Installation Guide
MALC-ISDN-4B3T-24
card-line-voltage: ------> {not-used}: 95-volts .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
After you save the card-profile record, the slot card in that slot resets and the begins downloading their software image from the flash card. This could take a few moments. When the card has finished loading, a log message similar to the following is displayed (if logging is enabled): zSH> Card in slot slot-number changed state to RUNNING
2
Use the slots command and specify the slot number of the card to view the state of the card: zSH> slots 4 Type : Sub-Type : Card Version : EEPROM Version : Serial # : CLEI Code : Card-Profile ID : Shelf : Slot : ROM Version : Software Version: State : Mode : Heartbeat check : Longest hbeat : Fault reset : Uptime : Start time :
3
MALC ULCS ISDN 4B3T 1 1 7778848 No CLEI 1/4/5049 1 4 development release 1.12 RUNNING FUNCTIONAL enabled 53 enabled 3 minutes 1133922289
Verify the ISDN port is set to line power: zSH> show isdn-profile 1-4-4-0/isdnu Please provide the following: [q]uit. line-term-class: ---> {class1}: activation-timer2: -> {t2-50ms}: loopback: ----------> {loop-back-none}: line-power: --------> {powering}: .................... Save new record? [s]ave, [c]hange or [q]uit: q Record not updated.
ISDN to AAL2 1
To configure a ISDN to AAL2 voice connection:
zSH> voice add isdn 1-3-1-0/isdnu aal2 uplink1/atm vc 0/38 cid 127 enable Created subscriber-voice 1/5/4
MALC Hardware Installation Guide
905
ISDN
Created Created Created Created Created Created Created Created Created
subscriber-voice-isdn 65 aal2-cid-profile 38/0/38/127 subscriber-voice-aal2 66 subscriber-voice 1/5/5 subscriber-voice-isdn 67 subscriber-voice-aal2 68 subscriber-voice 1/5/6 subscriber-voice-isdn 69 subscriber-voice-aal2 70
2
View the voice connection
zSH> voice show Subscriber end-point Remote end-point ------------------------------ -----------------------------1-3-1-0/isdnu 1-1-1-0/ds1 VC 0/38 CID 127 1-3-1-0/isdnu 1-1-1-0/ds1 VC 0/38 CID 158 1-3-1-0/isdnu 1-1-1-0/ds1 VC 0/38 CID 159 Total number of voice connections : 3
Voice Prof Id -------------1/5/4 1/5/5 1/5/6
ISDN to V5.2 1
Create the connection:
zSH> voice add isdn 1-4-4-0/isdnu v52 1/22 type isdn cpath 5 Created subscriber-voice 1/21/382 Created subscriber-voice-isdn 763 Created v52-user-port 1/22/3 Created subscriber-voice-v52 764 Created subscriber-voice 1/21/383 Created subscriber-voice-isdn 765 Created subscriber-voice-v52 766 Created subscriber-voice 1/21/384 Created subscriber-voice-isdn 767 Created subscriber-voice-v52 768
2
Set the ISDN port to line power: zSH> update isdn-profile 1-4-4-0/isdnu Please provide the following: [q]uit. line-term-class: ---> {class1}: activation-timer2: -> {t2-50ms}: loopback: ----------> {loop-back-none}: line-power: --------> {off}: powering .................... Save new record? [s]ave, [c]hange or [q]uit: s Record updated.
3
View the voice connection: zSH> voice show isdn 1-4-4-0/isdnu INPUT: profile type: subscriber-voice-isdn logical address: LGId: 298 PortType: ISDNDCHANNEL ChannelId: 1
906
MALC Hardware Installation Guide
STA --ENA ENA ENA
MALC-ISDN-4B3T-24
profile address: 763 subscriber-voice INFO: voice-connection-type = ISDNTOV52 voice-endpoint1-addr-index = 763 voice-endpoint2-addr-index = 764 voice-admin-status = Enabled subscriber-voice addr: subId: 1 LGId: 21 subVoiceId: 382 MATCHING: profile type: subscriber-voice-v52 logical address: IfName: one UserId: 22 IsdnBChannelId: 0 profile address: 764 INPUT: profile type: subscriber-voice-isdn logical address: LGId: 298 PortType: ISDNBCHANNEL ChannelId: 2 profile address: 765 subscriber-voice INFO: voice-connection-type = ISDNTOV52 voice-endpoint1-addr-index = 765 voice-endpoint2-addr-index = 766 voice-admin-status = Enabled subscriber-voice addr: subId: 1 LGId: 21 subVoiceId: 383 MATCHING: profile type: subscriber-voice-v52 logical address: IfName: one UserId: 22 IsdnBChannelId: 1 profile address: 766 INPUT: profile type: subscriber-voice-isdn logical address: LGId: 298 PortType: ISDNBCHANNEL ChannelId: 3 profile address: 767 subscriber-voice INFO: voice-connection-type = ISDNTOV52 voice-endpoint1-addr-index = 767 voice-endpoint2-addr-index = 768 voice-admin-status = Enabled subscriber-voice addr: subId: 1 LGId: 21 subVoiceId: 384 MATCHING: profile type: subscriber-voice-v52 logical address: IfName: one UserId: 22 IsdnBChannelId: 2 profile address: 768
MALC Hardware Installation Guide
907
ISDN
MALC-ISDN-2B1Q-24 active fault pwr fail
The MALC-ISDN-2B1Q-24 line card provides 24 ports of ISDS with 2B1Q line coding. This card can support TDM voice or packet voice.
1-24
m a0513
ISDN 2B1Q 24
Table 120: MALC-ISDN-2B1Q-24 specifications Specification
Value
Size
1 slot
Density
24 ports 1 D-channel and 2 B-channels per port
Physical interfaces
One (1) RJ-21X Champ 50-pin connector
ISDN line characteristics
144 kbps line rate 135 Ohm resistive line impedance 95V @ 45mA loop power 24 AWG 22,000 feet (maximum operational reach) 26 AWG 18,000 feet (maximum operational reach)
908
MALC Hardware Installation Guide
MALC-ISDN-2B1Q-24
Table 120: MALC-ISDN-2B1Q-24 specifications (Continued) Specification
Value
Redundancy
None
Line encoding
2B 1Q
Nominal line rate
80 kbps 5 ppm
Longitudinal balance:
500 Hz to 40 kHz: greater than 55 dB
Input return loss
greater than 20 dB, 10 kHz to 25 kHz roll-off 20 dB per decade to 1 kHz and 250 kHz
Free-run line rate (Stratum 4) if timing reference is lost
80 kbps 32 ppm
Power consumption
45 watts
40 kHz to 1 MHz: roll-off -20 dB per decade
Creating card-profiles for MALC-ISDN-2B1Q-24 cards Each card installed in the system must have a card-profile. Each type of slot card requires different settings in the card-profile. MALC-ISDN-2B1Q-24 cards can be configured for ISDN or packet voice support in the card profile. ISDN is used if the call is being routed out a TDM interface. Packet voice is used if ISDN calls are to be routed through a MALC voice gateway card. If configured for packet voice, ISDN signaling is only applicable if the card is connected to an NT interface. The following table describes the parameters in the card-profile for the ISDN 2B1Q card:
MALC Hardware Installation Guide
909
ISDN
Parameter
Description
sw-file-name
Software image for the card. The MALCISDN-2B1Q-24, MALC-ISDN-4B3T-24, and MALC-POTS- GBL-TDM/PKT-24 cards all use the same image. Values: malculcs.bin
card-line-type
The type of calls supported on this card. Values: pots TDM POTS. pots-pv POTS over packet voice. isdn ISDN. Used for 2B1Q and 4B3T. isdn-pv ISDN over packet voice. pots-coin TDM POTS with coin support. pots-coin-pv TDM POTS with coin support over packet voice.
card-line-voltage
The voltage supplied to each ISDN port. Values: not-used 60-volts 68-volts 95-volts 100-volts 110-volts
1
The following example creates a card-profile for a ULC card or MALC-ISDN-2B1Q-24 card in shelf 1, slot 5:
zSH> card add 1/5/5049
or zSH> new card-profile 1/5/5049 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {}: malculcs.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {false}: true sw-upgrade-enable: ----> {false}: card-group-id: --------> {0}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}:
910
MALC Hardware Installation Guide
ISDN card pinouts
card-atm-configuration: -> {notapplicable} card-line-voltage: ------> {not-used}: 95-volts .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
After you save the card-profile record, the slot card in that slot resets and the begins downloading their software image from the flash card. This could take a few moments. When the card has finished loading, a log message similar to the following is displayed (if logging is enabled): zSH> Card in slot slot-number changed state to RUNNING
2
Use the slots command and specify the slot number of the card to view the state of the card: zSH> slots 5 Type : Sub-Type : Card Version : EEPROM Version : Serial # : CLEI Code : Card-Profile ID : Shelf : Slot : ROM Version : Software Version: State : Mode : Heartbeat check : Longest hbeat : Fault reset : Uptime :
MALC ULCS ISDN 2B1Q 1 1 7778852 No CLEI 1/5/5049 1 5 development release 1.12 RUNNING FUNCTIONAL enabled 5072 enabled 21 hours, 24 minutes
ISDN card pinouts The ISDN cards use standard 50-pin male Champ connectors. Table 121 lists the port pinouts for the ISDN card. Table 121: ISDN card pinouts Pin
Function
Pin
Function
1
Channel 1 ring
26
Channel 1 tip
2
Channel 2 ring
27
Channel 2 tip
3
Channel 3 ring
28
Channel 3 tip
4
Channel 4 ring
29
Channel 4 tip
5
Channel 5 ring
30
Channel 5 tip
MALC Hardware Installation Guide
911
ISDN
Table 121: ISDN card pinouts (Continued)
912
Pin
Function
Pin
Function
6
Channel 6 ring
31
Channel 6 tip
7
Channel 7 ring
32
Channel 7 tip
8
Channel 8 ring
33
Channel 8 tip
9
Channel 9 ring
34
Channel 9 tip
10
Channel 10 ring
35
Channel 10 tip
11
Channel 11 ring
36
Channel 11 tip
12
Channel 12 ring
37
Channel 12 tip
13
unused
38
unused
14
unused
39
unused
15
unused
40
unused
16
unused
41
unused
17
unused
42
unused
18
unused
43
unused
19
unused
44
unused
20
unused
45
unused
21
unused
46
unused
22
unused
47
unused
23
unused
48
unused
24
unused
49
unused
25
unused
50
unused
MALC Hardware Installation Guide
29
METALLIC TEST ACCESS This chapter describes the MALC Metallic Test Access (MTAC) cards (MALC-MTAC/RING-ENH, MALC-MTAC/RING, MALC-MTAC/ RING-FC) and explains how to configure them. The chapter includes:
•
Overview, page 914
•
Activating MTAC cards, page 919
•
Performing line test using MTAC cards with external testing set, page 924
•
Performing internal line test using MALC-MTAC/RING-ENH card, page 929
•
Configuring external alarms, page 952
•
Configuring an external clock, page 953
•
Connecting an external ring source, page 953
•
MTAC cards pinouts, page 955
MALC Hardware Installation Guide
913
Metallic Test Access
active fault pwr fail
active fault pwr fail
Overview
EXT RING
EXT RING
A L A R M
A L A R M
C L O S U R E
C L O S U R E
A C C E S S C T R L
T E S T T E S T
T E S T T E S T
The MALC MTAC cards provide metallic test access to verify the local loop conditions, perform line testing on distant regions of the physical copper cable connecting the MALC and remote devices. It can assess breakages in the cable, identifying the following data:
•Distance. Identifies the amount of distance between the MTAC card and the location of the break or open that occurred on the copper cable.
A C C E S S C T R L
•Shorts. Identifies the port to which a cable containing an electrical short is connected.
•Unbalance. Identifies if one side is longer between
C L O C K
C L O C K
MTAC
the tip and the ring, creating an unbalance in the connection.
MTAC/RGR
ENH
•Metallic noise. Identifies any impairments on the
ma0802
ma0801
cable that indicate an interruption on the ring.
The MALC MTAC card family includes:
•
MALC-MTAC-RING: This is the basic version. This card provides metallic test with external test set. It also supports external alarm inputs, external clock access, and ring generation.
•
MALC-MTAC/RING-ENH: This is the enhance version of the MTAC/ RING card. In addition to the basic features, it also supports internal line test.
•
MALC-MTAC/RING-FC: This is a special version for the MALC 319 Chassis. In addition to the basic features, it also supports fan control. Note: The MALC-MTAC/RING-FC card must be installed in slot 10 of MALC 319.
Figure 105: MTAC/RING-FC card (MALC 319 only)
The MALC MTAC cards provide these features:
•
914
MALC Hardware Installation Guide
Metallic loop testing:
Overview
–
Test equipment access to any line.
–
Loop testing for DSL and POTS interfaces with the external test set. Note that the type of tests provided will vary, depending on the type of card being tested.
–
Look-out internal testing. (MALC-MTAC/RING-ENH only)
•
External alarm inputs (12 circuits, wet or dry, normally open or normally closed)
•
T1/E1 or BITS external network clock source
•
Ring generation:
•
–
Internal ring generator
–
Access for an external ring generator
Fan control and monitoring (MALC-MTAC/RING-FC only) Note: The MALC supports only one active MTAC/RING-ENH or MTAC/RING card at a time and a total of two MTAC cards in the system. Note: The MALC 319 supports only one MTAC card in the system and it must be MTAC/RING-FC card.
MALC Hardware Installation Guide
915
Metallic Test Access
Table 122: MTAC card specifications Specification
Value
Size
1 slot
Physical interfaces
•
Metallic test access port: An RJ45 connector that connects to the external test set. It connects the external test set to metallic test bus on backplane (supports one port test simultaneously in system).
•
External test set control port: A serial control RS232D signalling port on RJ45 connector that provides a control connection to the external test set.
•
External clock input port: An RJ45 connector that accepts T1/E1 or BITS external clock reference (all versions), provisionable as system clock source.
•
External ring generator input port: A two position plug spaced at 5.08mm conforming to the IEC 60664-1 industry standard, such as the RIA Type 249 part number 312491 02. This port connects to the external ring generator.
•
External alarm connector: A 26 pin D sub connector that supports 12 alarm closures for detecting various alarm types from collocated equipment. Supports isolated closure, ground and –48VDC closure (states and names provisionable in software).
Metallic test functions
Look-out testing (toward the loop) for ADSL, ULC, and POTS interfaces (with the exception of ADSL 32 cards). Refer to Cards supporting look-out test access, page 918 Note: The type of tests provided will vary, depending on the type of card being tested.
916
Ring generation
External ring generator voltage connector.
Redundancy
1+1 card redundancy
Clocking
The clocking reference on the MTAC/Ring-2Mhz-Clk card complies with ITU-T (CTR12) G.703 standard.
Accuracy field
-10% to +10%
Power consumption
8 W nominal 38 W maximum at full ringing load The MTAC/RING-FC card is required to be installed in the MALC 319 chassis. The power consumption for the MTAC/ RING-FC card and the chassis are 31 watts maximum with no ringing, 45 watts maximum at full ringing load.
MALC Hardware Installation Guide
Internal ring voltage sine wave generator (power ranges based on load from 15 REN total @ 86VRMS, 45 REN @ 40VRMS).
Overview
Connectors on the MTAC cards MTAC/RING-ENH, MTAC/RING, and MTAC/RING-FC cards have following connectors:
•
Metallic test access port
•
External test set control port
•
External clock input port
•
External ring generator input port
•
External alarm connectors
MTAC/RING-FC card has an additional alarm output port, which is specially designed for chassis 319. Figure 106 shows the connectors on the MTAC/RING card.
active fault pwr fail
Figure 106: Connectors on MTAC/RING card
External ring generator input port
EXT RING A L A R M
External alarm connectors
C L O S U R E T E S T T E S T
A C C E S S C T R L
C L O C K
Metallic test access port External test set control port External clock input port
MTAC/RGR
Metallic loop testing The MTAC cards support metallic loop testing for T1, POTS, and DSL loops, providing preventive measures for potential line breaks. All three versions of MTAC card support external test sets. External test sets supported include Tollgrade, Harris/Fluke, and Teradyne 4-Tel components.
MALC Hardware Installation Guide
917
Metallic Test Access
The MTAC/RING-ENH card also provides internal look-out line testing.
Internal look out line test Internal line testing is supported by the MTAC/RING-ENH card. With its own integrated test set, the MTAC/RING-ENH card in each shelf can perform test out session without the external test set.
Cards supporting look-out test access The MTAC cards provide access to external test equipment through an RJ45 connector for look-out test access. All ADSL-48, POTS, ULC, and 2-wire DSL cards support look-out test access. The following table provides examples of common instances of these card types. Table 123: Examples of common cards supporting look-out test access Card Type
Example
ADSL-48
MALC-ADSL+POTS-PKT-48A/M-2S MALC-ADSL+POTS-TDM/PKT-48-2S MALC-ADSL+SPLTR-48A/M-2S MALC-ADSL-48A MALC-ADSL-BCM-48A MALC-ADSL-BCM-48B
DSL
MALC-ReachDSL-24
EFM
MALC-EFM-SHDSL-24 MALC-EFM-T1/E1-24
POTS
MALC-POTS-GBL-TDM/PKT-24
(ULC)
MALC-POTS-TDM/PKT-48 SHDSL
MALC-SHDSL-48 MALC-EFM-SHDSL-24 MALC-EFM-SHDSL-24-NT MALC-EFM-SHDSL-24-NTP
VDSL2
MALC-VDSL2-24
The test relays can be controlled by the command line interface (CLI) and Zhone Management System (ZMS). Test relays on the POTS, DSL, or ULC cards can connect any POTS pair to an RJ45 metallic test access port on the MTAC card using the back plane to allow test access to any POTS, DSL, or ULC line.
918
MALC Hardware Installation Guide
Activating MTAC cards
Ring generator The MTAC cards contain the ring generator for POTS cards installed in the MALC. Ringing voltage is supplied to all installed POTS cards via a backplane bus. Note that only one MTAC card can supply ringing voltage to the system at a time. The MTAC cards also contain a ringing voltage detector that senses the absence of ringing voltage on the card itself or on an external ringing generator (if one exists). If the ringing voltage detector detects a problem, the redundant MTAC card can supply the ringing voltage, or the MALC can be configured to use another external ringing generator. Note: The MALC ground wires must be tied to the +48V battery return at the main power Distribution Center. Absence of this connection can cause malfunctions on some cards, including generation of the MTAC/RING-ENH card error message “Internal ringer not detected”.
Activating MTAC cards Caution: Each MTAC card in a redundant pair must be configured identically; the cards do not share state or configuration information. In addition, the user must manually keep the configuration of the active and standby cards in sync. This applies to both a matched pair and a mixed pair of MTAC cards. Each MTAC card installed in the system must have a card-profile. Each type of slot card requires different settings in the card-profile. MTAC cards have the following types and software images: Table 124: MTAC card types Card
Type
Name of software image
MALC-MTAC/RING
5003
malcmtac.bin
MALC-MTAC/RING-FC
5012
malcmtacfc.bin
MALC-MTAC/RING-ENH
5072
malcmtacenh.bin
Creating card profiles for MTAC cards Creating card profiles for MTAC/RING-ENH and MTAC/RING cards The card-profile for MTAC/RING-ENH and MTAC/RING cards require that the card-line-type (which specifies the external clock source type) be specified.
MALC Hardware Installation Guide
919
Metallic Test Access
To configure a redundant MTAC/RING-ENH or MTAC/RING card, create a second card-profile for the redundant card. To enable a MTAC/RING card: zSH> card add 1/15/5003 linetype ds1 | e1
or zSH> new card-profile 1/15/5003 Please provide the following: [q]uit. sw-file-name: ---------> {}: malcmtac.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {true}: sw-upgrade-enable: ----> {false}: card-group-id: --------> {2}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: ds1 | e1 used for the external clock port card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
To enable a MTAC/RING-ENH card: zSH> card add 1/11/5072 linetype ds1 | e1
or zSH> new card-profile 1/11/5072 Please provide the following: [q]uit. sw-file-name: -----------> {malcmtacenh.bin}: admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {true}: sw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}: hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {unknowntype}: ds1 | e1 card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
920
MALC Hardware Installation Guide
Activating MTAC cards
Creating card profile for MTAC/RING-FC card The MTAC/RING-FC card only can be inserted into the slot 10 on the MALC 319. The card-profile for MTAC/RING-FC cards require that the card-line-type (which specifies the external clock source type) be specified. To enable a MTAC/RING-FC card: zSH> card add 1/15/5012 linetype ds1 | e1
or zSH> new card-profile 1/15/5012 shelf/slot/type Please provide the following: [q]uit. sw-file-name: ---------> {}: malcmtacfc.bin admin-status: ---------> {operational}: upgrade-sw-file-name: -> {}: upgrade-vers: ---------> {}: admin-status-enable: --> {operational}: sw-upgrade-admin: -----> {reloadcurrrev}: sw-enable: ------------> {false}: true sw-upgrade-enable: ----> {false}: card-group-id: --------> {2}: hold-active: ----------> {false}: weight: ---------------> {nopreference}: card-line-type: -------> {unknowntype}: ds1 | e1 used for the external clock port card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved.
Replacing an existing MTAC/RING card with a MTAC/ RING-ENH card If there is an existing MTAC/RING card in a slot in the MALC, perform the following steps to replace it with a MTAC/RING-ENH card: 1
Load the MTAC/RING-ENH card image file “malcmtacenh.bin” on the MALC.
2
Issue the slots command to determine which existing MTAC card is active and in what slot it resides. The following output assumes the existing active MTAC card is in slot 16. zSH> slots 1:*MALC RPR GIGE (RUNNING) 2: MALC RPR GIGE (RUNNING) 3: MALC XDSL 48/with Packet Voice POTS (RUNNING) 5: MALC XDSL 48/with Packet Voice POTS (RUNNING 7: MALC XDSL 48/with Packet Voice POTS (RUNNING) 9: MALC XDSL 48/with Packet Voice POTS (RUNNING) 14: MALC POTS 48/with Packet Voice (NOT_PROV) 15: MALC POTS 48/with Packet Voice (NOT_PROV) 16:*MALC MTAC (RUNNING)
MALC Hardware Installation Guide
921
Metallic Test Access
17: MALC MTAC (RUNNING)
3
Issue a get card-profile command to determine what parameter exists in the card-line-type field. The following example assumes a shelf of 1, slot of 17 and a type number of 5003 (the type number for the MTAC/RING card). zSH> get card-profile 1/17/5003 sw-file-name: -----------> {malcmtac.bin} admin-status: -----------> {operational} upgrade-sw-file-name: ---> {} upgrade-vers: -----------> {} admin-status-enable: ----> {enable} sw-upgrade-admin: -------> {reloadcurrrev} sw-enable: --------------> {true} sw-upgrade-enable: ------> {false} card-group-id: ----------> {2} hold-active: ------------> {false} weight: -----------------> {nopreference} card-line-type: ---------> {ds1} card-atm-configuration: -> {notapplicable} card-line-voltage: ------> {not-used}
4
Issue a delete card-profile to remove the profile of the existing MTAC-Ring card. The following example assumes a shelf of 1, a slot of 17, and a type number of 5003. zSH> delete card-profile 1/17/5003 card-profile 1/17/5003 1 entry found. Delete card-profile 1/17/5003? [y]es, [n]o, [q]uit : yes NOTE: Automatic deletion of residual profiles related to this card will be done concurrently; it may take several minutes.
5
Wait a couple of minutes for the card profile removal process to complete, indicated by the string Completed residual profile deletions for card. When the process completes, user will see a message that appears similar to the following: JAN 27 00:46:23: alert : 1/16/26 : cardred: R E B O O T I N G peer 1/17, cause REMOTE_CARD_PROFILE_DELETED JAN 27 00:46:23: critical: 1/16/26 : rebootserver: * * * * Slot Reboot : type = 2, shelf = 1, slot = 17 card-profile 1/17/5003 deleted. JAN 27 00:46:34: info : 1/1/1104: carddeletehdlr: Starting residual profile deletions for card 1/17/5003 JAN 27 00:46:36: info : 1/1/1104: carddeletehdlr: Completed residual profile deletions for card 1/17/ 5003 (33 records removed)
922
MALC Hardware Installation Guide
Activating MTAC cards
6
Physically remove the MTAC/RING card that exists in the slot. In this example, it is in slot 17.
7
Insert the MTAC/RING-ENH card into the slot.
8
Issue the new card-profile command for the MTAC/RING-ENH card. he following example assumes a shelf of 1, a slot of 17 (as learned from the slots command) and a type number of 5072 (the type number for the MTAC/RING-ENH card). The following example assumes the shelf is 1 and the slot is 17.
zSH> card add 1/17/5072 linetype ds1 group 2
or zSH> new card-profile 1/17/5072 Please provide the following: [q]uit. sw-file-name: -----------> {malcmtacenh.bin}: admin-status: -----------> {operational}: upgrade-sw-file-name: ---> {}: upgrade-vers: -----------> {}: admin-status-enable: ----> {enable}: sw-upgrade-admin: -------> {reloadcurrrev}: sw-enable: --------------> {true}: sw-upgrade-enable: ------> {false}: card-group-id: ----------> {0}: 2 (To match orginal card) hold-active: ------------> {false}: weight: -----------------> {nopreference}: card-line-type: ---------> {unknowntype}: ds1 (To match orginal card) card-atm-configuration: -> {notapplicable}: card-line-voltage: ------> {not-used}: .................... Save new record? [s]ave, [c]hange or [q]uit: s New record saved. zSH> JAN 27 00:51:39: notice : 1/1/12 : shelfctrl: Card in slot 17 changed state to RUNNING.
9
Issue the slots command again and make sure the MTAC/RING-ENH card is running in slot 17.
10 Repeat for the other MTAC card if it is being replaced as well.
Verifying the slot card installation After saving the card-profile record, the slot card in that slot resets and the begins downloading their software image from the flash card. This could take a few moments. When the card has finished loading, a log message similar to the following is displayed (if logging is enabled): zSH> Card in slot slot-number changed state to RUNNING
You can also use the slots command and specify the slot number of the card to view the state of the card. For example:
MALC Hardware Installation Guide
923
Metallic Test Access
zSH> slots 16 Type Card Version EEPROM Version Serial # CLEI Code Card-Profile ID Shelf Slot State Mode Heartbeat check Longest hbeat
: : : : : : : : : : : :
MALC MTAC 1 2 13740040 No CLEI 1/16/5004 1 16 LOADING indicates the card is still initializing FUNCTIONAL enabled 0
To view the status of all the cards, use the slots command without any arguments: zSH> slots 1: MALC DS3 (RUNNING) 13: MALC ADSL (RUNNING) 16: MALC MTAC (RUNNING)
Viewing active redundant cards Use the showactivecards command to view all active cards in the system that are part of a redundant card group: zSH> showactivecards Shelf/Slot Group Id Card Type __________________________________ 1: 1/16 333 MALC MTAC
Performing line test using MTAC cards with external testing set The MTAC family of cards support external line testing.
Connecting the external test set to MTAC card The external test set is connected to the MTAC card through the metallic test access port and the external test set control port. The following figure details how an external test set can be connected to the MTAC card. (external test sets are also known as external test heads, external test units, and remote test units.) The MALC enables connecting the external test set to the MTAC card to set test relays. The default baud rate is 9600 bps. (This can be changed by modifying the rs232-profile.)
924
MALC Hardware Installation Guide
Performing line test using MTAC cards with external testing set
active fault pwr fail
Figure 107: External test set connected to a MTAC card
EXT RING A L A R M C L O S U R E
Harris/Fluke Model 107A/F TB3/SPL T E S T T E S T
PS5
A C C E S S C T R L
Metallic test access port External test set control port
C L O C K
MTAC/RGR
Local PC MTAC-RGR card in the MALC
For example, to test the integrity of a line by Harris external test set, issue the test aid command, using the shelf, slot, and port, as a numeric keyword. For shelf 1/slot 5/port 1, issue the command test aid=1-5-1. Sample output is provided below. HARRIS>test aid=1-5-1 DN: PAIR: SITE: TEST CHAN: 07/18/2006 15:00 NLT: PASS LDT: N/A NPA: 910 CO: CLLI:OKLAND AID: 1-5-1 ACC:TRUNK-WB COND: OUTWARD TTYPE: LOOP SUFF: DC SIGNATURE AC SIGNATURE NOISE KOHMS VOLTS KOHMS VOLTS CPE CAP 60HzINDUCED C-MESSAGEdBrnC 9999 0.00 9999 0.00 NO 0.00 T-R 37.5 TO GROUND 9999 0.00 9999 0.00 NO 0.00 T-G .002 mA T-g 0.00 METALLIC 9999 0.00 9999 0.00 NO 0.00 R-G .002 mA R-G NOISE BAL 0.00 Mutual () NOISE UNBALANCE: 0.00% TIP LENGTH: .001 KF HIST VER: K UP, K DN +-----+-+ +-+ | DLC |M| |M| CABLE +--+ +--+ | |a|=|D|=====================|DP|====|CPE| |DSLAM|T| |F| +--+ +---+ +----------+-+ +-+ VER35: OPEN IN EQUIPMENT Dispatch: OFFICE (No CPE Seen)
Note: Refer to various external test set user guides for detail.
MALC Hardware Installation Guide
925
Metallic Test Access
Note: Only the pair of Test out tip 1 and Test out ring 1 is available to be used for loop testing.
Connecting the test measurement device to the metallic test access port If the user wants to manually measure the line integrity, the user can connect the metallic test access port on the MTAC card with a manual test measurement device, such as Ohm meter or voltage meter. Figure 108: Manual test measurement device connected to a MTAC card
C R A F T
active fault pwr fail
active fault pwr fail
Ohm meter
S E R I A L
EXT RING A L A R M C L O S U R E
D S 3 / E 3 A T M
T E S T
E T H E R N E T ATM/IP UPLINK
T E S T
A C C E S S C T R L
Metallic test access port External test set control port
C L O C K
MTAC/RGR
The MALC creates mtac-profile for each card installed in the system for manually changing test modes. After connecting the manual test measurement device, use the mtac-linetest command to set the relay options. The following table describes the supported parameters in the mtac-profile.
926
MALC Hardware Installation Guide
Performing line test using MTAC cards with external testing set
Table 125: mtac-profile command parameters description Parameter
Description
ifIndex
Specifies the ifindex of the physical line to be tested. If no line is being tested, this value is 0. Values: A physical interface on the system. In the format shelf/slot/port/subport/type Default: 0 This parameter cannot be modified while a test is in progress. The ability of a physical line to support a metallic test may vary depending on the cards installed and the external test equipment.
test_mode
Specifies metallic test mode for a given line. The test mode can be changed only if the ifIndex parameter is set to a nonzero value. Values: mtacModeLookOut The MALC service port is disconnected and the subscriber line is metallically routed to the MTAC metallic test access port. This allows the testing of line with or without a subscriber terminal. mtacModeNone No MTAC test is in progress. Default: mtacModeNone
The following example enables a manual test measurement device to access to the ADSL interface on shelf 1, slot 3, port 1: zSH> update mtac-profile 1 Please provide the following: [q]uit. ifIndex: ---> {0/0/0/0/0} 1/3/1/0/adsl test_mode: -> {mtacmodenone} mtacmodelookout .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
To stop access to the interface, set the mtac-profile back to the defaults: zSH> update mtac-profile 1 Please provide the following: [q]uit. ifIndex: ---> {1/3/1/0/adsl} 0/0/0/0/0 test_mode: -> {mtacmodelookout} mtacmodenone .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
MALC Hardware Installation Guide
927
Metallic Test Access
Note: The mtac-profile must be set back to its defaults before a line can be specified for test access.
Connecting a console to the external test set control port The user also can connect the external test set control port on the MTAC card with a console to input commands. The metallic test access port on the MTAC card would be connected with a manual test measurement device, such as Ohm meter or voltage meter to read the test results. Figure 109: Console connected to a MTAC card
active fault pwr fail
Ohm meter
EXT RING A L A R M C L O S U R E T E S T T E S T
A C C E S S C T R L
Metallic test access port Extermal test set control port
C L O C K
MTAC/RGR
Console
MTAC-RGR card in the MALC
Note: These commands are used on the MTAC card external test set control port, not on the Malc uplink card zhone shell. Use the MTAC external test set control port commands to determine what the state of the card is, either in Idle or Test mode, and to determine whether the line test has been successful. The MTAC external test set control port commands are: > mtac-status > mtac-linetest portaddr mode [linetype] [force] Note that the force parameter can only performs on voicefxs lines. > mtac-status Relay 1 in idle mode. > mtac-linetest 1/13/1 lookout Successful - In TestMode > mtac-status
928
MALC Hardware Installation Guide
Performing internal line test using MALC-MTAC/RING-ENH card
Relay 1 in lookout mode. Used by 1/13/1 iftype=102 > mtac-linetest 1/13/1 release Succssful - Returned to operational state > mtac-status Relay 1 in idle mode > mtac-linetest 1/13/1 lookout adsl Successful - In TestMode > mtac-status Relay 1 in lookout mode. Used by 1/13/1 iftype=94 > mtac-linetest 1/13/1 release Succssful - Returned to operational state
Performing internal line test using MALC-MTAC/RING-ENH card The MALC-MTAC/RING-ENH card comes with an integrated test head, thus, each shelf has its own dedicated test head. This means user can now communicate with each shelf concurrently to perform test out sessions. This section describes the following information:
•
Working with the MTAC line test command on page 929
•
Test IDs on page 931
•
Metallic loop tests on page 933
•
Troubleshooting with metallic loop tests on page 948
•
Auto-calibration on page 952
•
Lookout block diagram on page 952
Working with the MTAC line test command The MALC-MTAC-/RING-ENH card is able to perform Metallic Loop Testing (MLT) without an external test set. Use mtac-linetest commands to specify the test mode (lookout) and other test parameters for the internal line test. The mtac-linetest command syntax is: mtac-linetest portaddr mode testid [linetype] [force] The mtac-linetest command has the required components of port address, mode, and test identifier; the optional components of linetype and parameter force. zSH> mtac-linetest Usage: mtac-linetest [] [force] Description: Execute metallic test Arguments:
MALC Hardware Installation Guide
929
Metallic Test Access
- port address in shelf/slot/port - lookout, lookin, release, bridge - A builtin metallic linetest - adsl, ds1, shdsl, isdn, vdsl, and voicefxs. Default voicefxs. force - override option regardless if line is in use
Table 126 lists supported parameters in the mtac-linetest command. Table 126: mtac-linetest command parameters description Parameter
Description
portaddr
Specifies the port address of the physical line to be tested. Values: A port address on the system. In the format shelf/ slot/port
mode
Specifies metallic test mode for a given line. The test mode can be changed only if the port address parameter is set to a nonzero value. Values: Lookout The MALC service port is disconnected and the subscriber line is metallically routed to the MTAC metallic test access port. This allows the testing of line with or without a subscriber terminal. Release Terminate the MTAC test that in progress. Lookin and Bridge are not supported in current version. Default: Release
testid
Specifies the supported line tests. Values: none, all, abort, foreigndcvoltage, foreignacvoltage, dcloopresistance, 3elementresistance, 3elementcapacitance, receiveroffhook, distancetoopen, foreignaccurrents, ringerequiv, dtmfandpulsedigitmeasurement, noisemeasurement, tonegeneration, transhybridloss, drawandbreakdialtone, dcfeedselftest, onandoffhookmeasurement, ringingselftest, ringingmonitor, meteringselftest, transmissionselftest, howlertest, readloopandbatteryconditions Refer to Table 127 on page 931 for the detail description for each value.
930
MALC Hardware Installation Guide
Performing internal line test using MALC-MTAC/RING-ENH card
Table 126: mtac-linetest command parameters description Parameter
Description
linetype
Specifies the line connect type to an equipment port class. This parameter is optional. Values: adsl shdsl isdn vdsl voicefxs Default: By default, the line type is voicefxs for POTS loops, and should be changed to the correct type when testing a loop other than POTS. Note that, the line type is voicefxs for Combo lines, not adsl.
force
This option allows seizure of a line that may be in use. Using the embedded testing is invasive to the line and should not be used for a line in use. If a line is in use and must be tested, the force option will override the current usage. Values: force
Test IDs Table 127 lists the detailed description of the internal line tests that supported by MTAC/RING-ENH card. Table 127: MTAC/RING-ENH Internal Line Tests Test ID
Description
3elementcapacitance
This test measures tip-to-ground (T-G), ring-to-ground (R-G), and tip-to-ring (T-R) capacitance and impedance.
3elementresistance
This test measures tip-to-ground (T-G), ring-to-ground (R-G), and tip-to-ring (T-R) resistance.
abort
Terminate the running test.
all
Runs all standalone tests in sequence. Standalone test does not need user interaction.
dcfeedselftest
This procedure verifies that the test hardware can drive currents into a load and measure the voltage across a load.
dcloopresistance
This test measures DC loop resistance using one of the following algorithms: Forward/ Reverse Polarity or Offset Compensation.
distancetoopen
This test estimates the distance to an open-circuit by analyzing the results of a 3 elements resistance test and a 3 elements capacitance test.
MALC Hardware Installation Guide
931
Metallic Test Access
Table 127: MTAC/RING-ENH Internal Line Tests (Continued) Test ID
Description
drawandbreakdialtone
This test verifies the capability of the line circuit to detect off-hook and on-hook, the communication channel to the switching center, and the voice path from the switching center. This test is performed with the call-processing function enabled on the line under test. Note that this test will be supported in the future release.
932
dtmfandpulsedigit measurement
This test detects and measures a DTMF digit, pulse digit, or hook-switch flash. Only one digit or flash is reported for each invocation of this test. By default, a single tone is output on the line during this test.
foreignaccurrents
This test measures foreign AC currents.
foreigndcvoltage
This test examines the loop for the existence of DC voltage leaking into a line form an external source.
foreignacvoltage
The foreign AC voltage test is examining the loop for the existence of AC voltage leaking onto a line from an external source.
howlertest
This procedure generates a Howler (Receiver Off-Hook) tone until the phone goes on-hook or a timeout condition is detected.
meteringselftest
This procedure verifies that the line card can generate a metering pulse. It drives a metering signal into both a resistive load and an open-circuit using the current Metering Profile applied to the line.
none
No test. May used when changing test modes.
nosiemeasurement
This procedure performs an active or passive noise test. Various filters may be applied to the received signal during this test. The application can apply special AC transmission coefficients during this test if desired.
onandoffhook measurement
This procedure verifies that the line circuit can detect on-hook and off-hook events.
readloopandbattery conditions
This procedure measures the instantaneous loop resistance, loop currents, and loop and battery voltages. No filtering is done during the measurement, so the results may fluctuate from one reading to the next in the presence of AC induction on the line.
receiveroffhook
This test determines whether the receiver is off-hook by running the DC Loop Resistance Test twice with different test currents and analyzing the results.
ringerequiv
This test calculates the Ringer Equivalency Number (REN) for the telephone attached to the line. The test supports both the regular and electronic phone REN measurement techniques.
ringingselftest
This procedure verifies that the line circuit can generate high level differential signals such as those used during line testing or application of internally generated ringing to the loop. It generates a sinusoidal waveform with the requested amplitude and drives this signal into a test load of known resistance.
MALC Hardware Installation Guide
Performing internal line test using MALC-MTAC/RING-ENH card
Table 127: MTAC/RING-ENH Internal Line Tests (Continued) Test ID
Description
ringingmonitor
This test is useful in checking the external ringing voltage given the loop cannot be disconnected while applying ringing and the ringing signal voltage cannot be reduced. This test is expected to be called on a line that has a terminating call (thus the need for applying ringing). This test uses about 3 cycles of the ringing waveform to carry out the test and then places the line to ringing state. Thus, a test is complete and we have placed ringing on the line as well to terminate the call. Please note that no ring trip would be detected during the first three cycles of the ringing signal.
tonegeneration
This test generates up to four sinusoidal tones simultaneously.
transhybridloss
This test measures trans-hybrid loss by generating a tone and measuring the reflected signal.
transmissionselftest
This procedure verifies that the line card can pass signals in the digital to analog and analog to digital directions. It measures trans-hybrid loss with open-circuit and a load impedance applied to the line. These trans-hybrid loss results are checked against expected values to generate a pass/fail result.
Metallic loop tests This section outlines supported metallic loop tests, and provide some suggested boundary conditions as they are relevant to loop qualification:
•
3 elements capacitance test on page 934
•
3 elements resistance test on page 935
•
DC feed self-test on page 936
•
DC loop resistance test on page 937
•
Distance to open test on page 938
•
DTMF and pulse digit measurement test on page 938
•
Foreign AC currents test on page 940
•
Foreign DC voltage test on page 940
•
Foreign AC voltage test on page 941
•
Howler test on page 942
•
Metering self test on page 942
•
Noise test on page 943
•
On-Off hook transition test on page 943
•
Loop and battery condition test on page 944
•
Receiver off-hook test on page 945
•
Ringer equivalency number test on page 945
•
Ringing self test on page 946
MALC Hardware Installation Guide
933
Metallic Test Access
•
Ringing monitor test on page 947
•
Tone generation test on page 947
•
Trans-hybrid loss test on page 947
•
Transmission self test on page 948 Note: All the tests have the test time information as Time Started and Time Ended. The number listed in the Time Started and Time Ended are in hundredth of a second resolution. A typical test took about 1.5 to 2 seconds.
3 elements capacitance test The 3 elements capacitance test measures tip-to-ground (T-G), ring-to-ground (R-G), tip-to-ring (T-R) capacitance, and impedance. The following example provides the sample command and output: zSH> mtac-linetest 1/3/42 lookout 3elementcapacitance Successful - In TestMode Time Started: 334096 Time Ended: 334633 Three-Element capacitance Results (T-G)CAPACITANCE= 217.67 NFARADS (R-G)CAPACITANCE= 217.51 NFARADS (T-R)CAPACITANCE= 397.66 NFARADS (T-G)55Hz AC IMPEDANCE= 13.01 KOHMS (R-G)55Hz AC IMPEDANCE= 13.09 KOHMS (T-R)55Hz AC IMPEDANCE= 7.23 KOHMS -----------------------------------------------------Successful - Returned to operational state zSH>
3 elements capacitance test result description:
•
(T-G) CAPACITANCE, (R-G) CAPACITANCE, (T-R) CAPACITANCE: –
Reports the tip-to-ground, ring-to-ground, and tip-to-ring capacitances in NFARADS respectively. "NOT MEASURED" means the capacitance cannot be measured.
–
(T-R) CAPACITANCE value can be used to indicate whether there is a phone attached. In most the case, a capacitance less than 60nF indicates there is no load. A value greater than 60nF indicates there is a load attached, possibly a phone set. NOTE: a modern phone with electronic ringer may have less than 60nF between its Tip and Ring. A “NOT-MEASURED” value in (T-R) CAPACITANCE may indicate the phone is off-hook. In this case, run the 3 element resistance test to verify the resistance value between Tip and Ring.
934
MALC Hardware Installation Guide
Performing internal line test using MALC-MTAC/RING-ENH card
•
(T-G) 55Hz AC IMPEDANCE, (R-G) 55Hz AC IMPEDANCE, 55Hz (T-R) AC IMPEDANCE: Reports the tip-to-ground impedance at 55Hz in KOhms. "NOT MEASURED" means the impedance cannot be measured. If the result is less than 1200 KOHMS, the actual measured value is displayed as the floating-point number. Otherwise, ">1200 KOHMS (OPEN)" is displayed.
3 elements resistance test The 3 elements resistance test measures the resistance of the loop. These measurements includes resistance tip-to-ground (T-G), ring-to-ground (R-G), tip-to-ring (T-R); foreign DC voltage (T-G) and (R-G); and foreign DC current in the tip and ring leads. Note that, the foreign DC voltage results from this test are not as accurate as those returned by the individual foreign DC voltage Test, but the overall testing time may be reduced by using results of this test instead of additionally running the foreign DC voltage test. The following example provides the sample command and output: zSH> mtac-linetest 1/17/4 lookout 3elementresistance Successful - In TestMode Time Started: 1129209 Time Ended: 1129456 Three-Element Resistance Results (T-G) DC RESISTANCE= > 1200 KOHMS(OPEN DC ) (R-G) DC RESISTANCE= > 1200 KOHMS(OPEN DC ) (T-R) DC RESISTANCE= 946.68 KOHMS (T-G) FOREIGN DC VOLTAGE= NONE VOLTS (R-G) FOREIGN DC VOLTAGE= NONE VOLTS TIP FOREIGN DC CURRENT= 0.00 MILLIAMPS RING FOREIGN DC CURRENT= 0.00 MILLIAMPS -----------------------------------------------------Successful - Returned to operational state zSH>
3 elements resistance test result description:
•
(T-G) DC RESISTANCE, (R-G) DC RESISTANCE, (T-R) DC RESISTANCE: –
If the resistance is less than 150 ohms, it is considered to be very small, and interpreted as a short circuit or fault.
–
If the result could not be calculated because of some fault, NOT MEASURED is printed.
–
If the resistance is larger than 1200 KOhms, it is considered to be too high to be measured accurately, and interpreted as open-circuit.
–
Otherwise, the resistance result is considered as normal, and interpreted as a floating-point number.
MALC Hardware Installation Guide
935
Metallic Test Access
•
•
(T-G) FOREIGN DC VOLTAGE, (R-G) FOREIGN DC VOLTAGE: –
If the result is less than 5 V, it is considered to be a normal value, and the foreign DC voltage is printed as a floating-point number.
–
If the result is between 5 V to 12 V, it is considered to be marginally normal, and printed as a floating-point number.
–
If the result is greater than 12 V, it is considered as not a normal value, and should be investigated.
–
If the result is printed as NONE, it means the result is normal for loop start, data loops, and CPE.
TIP FOREIGN DC CURRENT, RING FOREIGN DC CURRENT: –
If the result is less than 1 Milliamps (MA), it is considered to be a normal value, and the tip foreign DC current is printed as a floating-point number.
–
If the result is between 1 MA to 3 MA, it is considered to be marginally normal, and printed as a floating-point number.
–
If the result is greater than 3 MA, it is considered as not a normal value, and should be investigated. If the result is greater than 8 MA, it is printed as > 80 MILLIAMPS, if the result is between 3 MA to 8 MA, the result is printed as floating-point number.
–
If the result is printed as NONE, it means the result is normal for loop start, data lines loops, and CPE.
DC feed self-test This self test puts a 0.89 KOhms test load on the line, and measures the return in order to determine if appropriate levels are available on the line. The following example provides the sample command and output: zSH> mtac-linetest 1/4/1 lookout dcfeedselftest Successful - In TestMode Time Started: 9023093 Time Ended: 9023383 DC Feed Self-Test Results TEST PASSED= MEASURED TEST LOAD= MEASURED HIGH BAT VOLTAGE= (T-R) MEASURED VOLTAGE= CURRENT IN TEST LOAD (BAT=High, POL=Normal)= CURRENT IN TEST LOAD (BAT=High, POL=Reverse)= CURRENT IN TEST LOAD (BAT=Low, POL=Normal)= ----------------------------------------------------Successful - Returned to operational state
DC feed self test result description:
936
MALC Hardware Installation Guide
Yes 892.34 -50.42 40.87 16.21 16.30 15.69
OHMS VOLTS VOLTS MILLIAMPS MILLIAMPS MILLIAMPS
Performing internal line test using MALC-MTAC/RING-ENH card
•
TEST PASSED indicates whether the test passed. It based solely on the measured test load, high battery potential and tip-ring voltage.
•
MEASURED TEST LOAD reports the measured test load resistance. If this result is not within 10% of the nominal load resistance (0.89 KOhms), then TEST PASSED is set to NO.
•
MEASURED HIGH BAT VOLTAGE reports the measured high battery voltage. It is nominal at -48 VDC. Acceptable ranges for this value are -42 to -56 VDC.
•
(T-R) MEASURED VOLTAGE reports the measured tip-ring voltage while high current is driven. If the magnitude of the tip-ring voltage plus 2.66 V SLIC head-room plus (90.4 / MEASURED TEST LOAD) × (T-R) MEASURED VOLTAGE is not within the MEASURED HIGH BAT VOLTAGE ± (1.1 V plus 10% of the magnitude of the high battery voltage), then TEST PASSED is set to NO.
DC loop resistance test The DC loop resistance test measures the resistance on a line, longitudinal imbalances, and other characteristics. This test is useful for low loop resistance, generally less than 4Kohms. For higher resistance loop the 3 elements resistance test is more accurate. The following example provides the sample command and output: zSH> mtac-linetest 1/4/1 lookout dcloopresistance Successful - In TestMode Time Started: 9025472 Time Ended: 9025648 DC loop resistance Test Results LOOP RESISTANCE= 3.95 KOHMS COMMON MODE CURRENT Phase 1= 0.00 MILLIAMPS COMMON MODE CURRENT Phase 2= 0.00 MILLIAMPS Voltage Saturation= Yes COMMON MODE CURRENT Degradation=No ----------------------------------------------------Successful - Returned to operational state
DC loop resistance test result description:
•
LOOP RESISTANCE reports the measured loop resistance in KOhms.
•
COMMON MODE CURRENT Phase 1 reports the common mode current measured during the test first phase.
•
COMMON MODE CURRENT Phase 2 reports the common mode current measured during the test second phase.
•
Voltage Saturation
MALC Hardware Installation Guide
937
Metallic Test Access
•
–
= Yes indicates that the tip-ring voltage approached the battery voltage while attempting to drive the requested test current through the loop. The users should run the 3 element resistance test to get a more accurate measurement.
–
= No is a normal measurement.
COMMON MODE CURRENT Degradation. –
= Yes indicates that the test results may be inaccurate due to excessive common-mode current. The users should run the 3 element resistance test to get a more accurate measurement.
–
= No is a normal measurement.
Distance to open test This test estimates the distance to an open-circuit by analyzing the results of a 3 elements resistance test and a 3 elements capacitance test. The following example provides the sample command and output: zSH> mtac-linetest 1/3/42 lookout distancetoopen Successful - In TestMode Time Started: 626510 Time Ended: 627395 Distance to open Results Distance to open= 4379.50 Meters Capacitence(measured)= 218.97 NFARADS -----------------------------------------------------Successful - Returned to operational state zSH>
Distance to open test result description:
•
Distance to open reports the estimated distance to an open-circuit in meters.
•
Capacitance (measured) reports the measured capacitance value in NFarads.
•
If the test fails, one or both of the following errors will be displayed: –
Test failed because the 3eleResistence failed – the Three-Element Insulation Resistance Test results show excessive current leakage.
–
Test failed because the 3eleCapcitence failed – the Three-Element Capacitance Test could not accurately measure the tip-to-ground and ring-to-ground capacitance.
DTMF and pulse digit measurement test This test detects and measures a DTMF digit, pulse digit, or hook-switch flash. Only one digit or flash is reported for each invocation of this test. By default, a single tone is output on the line during this test. The test runs for approximately 4 seconds.
938
MALC Hardware Installation Guide
Performing internal line test using MALC-MTAC/RING-ENH card
The following example provides the sample command and output: zSH> mtac-linetest 1/4/1 lookout dtmfandpulsedigitmeasurement Successful - In TestMode Time Started: 9032539 Time Ended: 9032966 DTMF/pulse Results DTMF/pulse test timed out ----------------------------------------------------Successful - Returned to operational state
DTMF and pulse digit measurement test result description:
•
If no DTMF digits detected, the test result prints “DTMF/pulse test timed out”.
•
If a DTMF digit was detected, the test result prints the real measurement as floating-point number.
•
If a DTMF digit was detected and it has time to do a fourier transform the test result prints:
•
•
–
DTMF DIGIT
–
DTMF SAMPLE SIZE=
–
DTMF FIRST TONE=
Hz
–
DTMF FIRST TONE LEVEL=
–
DTMF SECOND TONE=
–
DTMF SECOND TONE LEVEL=
dBm
Hz dBm
If a Tone was detected but no DTMF digit detected and it has time to do a fourier transform it prints: –
DTMF DIGIT
NO DIGIT DECODED
–
DTMF SAMPLE SIZE=
–
DTMF FIRST TONE=
Hz
–
DTMF FIRST TONE LEVEL=
–
DTMF SECOND TONE=
–
DTMF SECOND TONE LEVEL=
dBm
Hz dBm
If a pulse digit is detected it prints: –
PULSE DIGIT=
–
PULSE MINBRK= % OF AVG PERIOD
–
PULSE MAXBRK= % OF AVG PERIOD
–
PULSE AVGBRK= % OF AVG PERIOD
–
PULSE RATE= PER SEC
MALC Hardware Installation Guide
939
Metallic Test Access
(The MINBRK, MAXBRK, AVGBRK are a percentage of the average pulse period indicated by pulse rate.)
•
If a hook flash is detected it prints “PULSE INTERVAL= mSEC”.
•
If a disconnect is detected it prints “DISCONNECT DETECTED”.
Foreign AC currents test This test measures foreign AC currents. The following example provides the sample command and output: zSH> mtac-linetest 1/4/1 lookout foreignaccurents Successful - In TestMode Time Started: 9035116 Time Ended: 9035207 Foreign AC current Results TIP FOREIGN AC CURRENT= NONE MILLIAMPS RING FOREIGN AC CURRENT= NONE MILLIAMPS ----------------------------------------------------Successful - Returned to operational state
The foreign AC currents test result description:
•
TIP FOREIGN CURRENT reports the measured tip lead current in Milliamps.
•
RING FOREIGN CURRENT reports the measured ring lead current in Milliamps.
Foreign DC voltage test The foreign DC voltage test is examining the loop for the existence of DC voltage leaking onto a line from an external source. The following example provides the sample command and output: zSH> mtac-linetest 1/4/1 lookout foreigndcvoltage Successful - In TestMode Time Started: 9036757 Time Ended: 9036966 Foreign DC Voltage Test Results Test Passed=Yes (T-G)FOREIGN DC VOLTAGE= 0.02 VOLTS(OK) (R-G)FOREIGN DC VOLTAGE= 0.00 VOLTS(OK) (T-R)FOREIGN DC VOLTAGE= 0.02 VOLTS(OK) -----------------------------------------------------Successful - Returned to operational state
The foreign DC voltage test result description:
940
MALC Hardware Installation Guide
Performing internal line test using MALC-MTAC/RING-ENH card
•
(T-G) FOREIGN DC VOLTAGE, (R-G) FOREIGN DC VOLTAGE, (T-R) FOREIGN DC VOLTAGE: –
6 Volts indicates a fault, it need to retest and follow-up. (FAULT) is printed after the measured data.
–
= or > 100 Volts indicates the presence of hazardous levels, and should be considered a dangerous fault. (HAZARDOUS) is printed after the measured data.
–
For lines using ADSL2+, the voltage level for tip to ground should be less than 3 Volts to ensure a stable DSL connection.
Foreign AC voltage test The foreign AC voltage test is examining the loop for the existence of AC voltage leaking onto a line from an external source. The following example provides the sample command and output: zSH> mtac-linetest 1/4/1 lookout foreigndcvoltage Successful - In TestMode Time Started: 9038284 Time Ended: 9038424 Foreign AC Voltage Test Results (T-G)FOREIGN AC VOLTAGE= 0.00 VRMS(NONE) (R-G)FOREIGN AC VOLTAGE= 0.00 VRMS(NONE) (T-R)FOREIGN AC VOLTAGE= 0.00 VRMS(NONE) -----------------------------------------------------Successful - Returned to operational state
Foreign AC Voltage test result description:
•
•
(T-G) FOREIGN AC VOLTAGE, (R-G) FOREING AC VOLTAGE: –
< 3 AC Volts rms (Vrms), (NONE) will be printed out after a real measurement.
–
= or > 3 to = or < 10 AC Vrms is a normal and good measurement. It is normal for loop start, data lines loops, and CPE. (OK) will be printed out after a real measurement.
–
>10 to = or < 50 AC Vrms is a fault. It should be retested and then investigated. (FAULT) will be printed out after a real measurement.
–
>50 AC Vrms indicates the presence of hazardous levels, and should be considered a dangerous fault. (HAZARDOUS) will be printed out after a real measurement.
–
For lines using ADSL2+, the voltage levels for tip-to-ground and ring-to-ground should be less than 10 Volts to ensure a stable DSL connection.
(T-R) Foreign AC VOLTAGE:
MALC Hardware Installation Guide
941
Metallic Test Access
–
< 3 Vrms is a normal and good measurement. It is normal for loop start, data lines loops, and CPE. (NONE) will be printed out after a real measurement.
–
=or >3 to = or < 5 Vrms is a fault. It should be retested and then investigated. (FAULT) will be printed out after a real measurement.
–
>50 Vrms indicates the presence of hazardous levels, and should be considered a dangerous fault. (HAZARDOUS) will be printed out after a real measurement.
–
For lines using ADSL2+, the voltage level for tip to ring should be less than 3 Volts to ensure a stable DSL connection.
Howler test This procedure generates a Howler (Receiver Off-Hook) tone until the phone goes on-hook or a timeout condition is detected. The following example provides the sample command and output: zSH> mtac-linetest 1/4/1 lookout howlertest Successful - In TestMode Time Started: 9039942 Time Ended: 9040152 Howler Test results Running US Howler Test ----------------------------------------------------Successful - Returned to operational state
The howler test result description: Depending on the system profile, the howler test prints “Running US Howler Test”, “Running Australian Howler Test”, or “Running UK Howler Test”. If the system profile cannot be read, the test prints “Failed to access the system profile”, and stop the test.
Metering self test This procedure verifies that the line card can generate a metering pulse. It drives a metering signal into both a resistive load and an open-circuit using the current Metering Profile applied to the line. The following example provides the sample command and output: zSH> mtac-linetest 1/3/42 lookout meteringselftest Successful - In TestMode Time Started: 396242 Time Ended: 396298 Metering Self-Test Results TEST PASSED= Yes Peak metering Voltage Resistive Load= 1.22 VOLTS Peak metering Voltage Open circuit= 1.40 VOLTS -----------------------------------------------------Successful - Returned to operational state
942
MALC Hardware Installation Guide
Performing internal line test using MALC-MTAC/RING-ENH card
zSH>
The metering self test result description:
•
Peak metering Voltage Resistive Load reports the peak voltage of the metering signal with the circuit connected to a resistive load.
•
Peak metering Voltage Open Circuit reports the peak voltage of the metering signal with the circuit open.
Noise test The noise test measures the amount of noise in dBm on the line, relative to TLP 0. This provides measurements in dBm0 units. The following example provides the sample command and output: zSH> mtac-linetest 1/4/1 lookout noisemeasurement Successful - In TestMode Time Started: 9047559 Time Ended: 9047703 Noise Test results NOISE= -67.23 dBm0 ----------------------------------------------------Successful - Returned to operational state
Noise test result description:
•
Noise below -45 dBmO is an average loop (LSB switching noise approaches -45 dBmO).
•
Noise between -44 and -10 dBmO is too noisy and should be retested and investigated.
On-Off hook transition test This on-hook to off-hook test allows the MLT to determine if a loop can successfully complete a simulated hook state transition. The following example provides the sample command and output: zSH> mtac-linetest 1/4/1 lookout onandoffhookmeasurement Successful - In TestMode Time Started: 9049153 Time Ended: 9049231 ON-OFF Hook Self-Test Results PASSED ----------------------------------------------------Successful - Returned to operational state
The on-off hook transition test result description:
•
PASSED indicates that the test was passed.
MALC Hardware Installation Guide
943
Metallic Test Access
•
ABORTED indicates that the line was off-hook when the test was started.
•
HW_FAULT indicates that the test failed because the line circuit did not properly detect on-hook and off-hook state changes.
•
UNKNOWN indicates some unexpected error occurred.
Loop and battery condition test The loop and battery condition test measures the instantaneous loop resistance, loop currents, and loop and battery voltages. No filtering is done during the measurement, so the results may fluctuate from one reading to the next in the presence of AC induction on the line. The following example tests the POTS line on shelf 1, slot 4, port 1 with a forced readloopandbatteryconditions test using lookout mode, and provides the outputs: zSH> mtac-linetest 1/4/1 lookout readloopandbatteryconditions force Successful - In TestMode Time Started: 9053736 Time Ended: 9053737 Read Loop and Battery Condition TestResults Read Loop and Battery Condition Test LOOP resistance= not measured Common-mode (longitudinal)current= not measured (T-R) (metallic) current= not measured (T-R) voltage= not measured Lowest battery voltage (measured)= -50.30 VOLTS Highest battery voltage (measured)= -50.41 VOLTS Positive battery voltage= 1.40 VOLTS Metering Voltage (measured)= 0.00 VOLTS NOTE: the metering voltage is only valid if a metering pulse is currently being generated. -----------------------------------------------------Successful - Returned to operational state
Loop and battery condition test result description:
944
•
Loop resistance reports the loop resistance in KOhms. If the loop resistance can not be measured in the present line state, “not measured” is reported.
•
Common-mode (longitudinal) current reports the longitudinal (common-mode) current in Milliamps. If the longitudinal current can not be measured in the present line state, “not measured” is reported.
•
(T-R) (metallic) current reports the metallic (tip-to-ring) current in Milliamps. If the metallic current can not be measured in the present line state, “not measured” is reported.
•
(T-R) voltage reports the tip-to-ring voltage in volts. If the tip-to-ring voltage can not be measured in the present line state, "not measured" is reported.
MALC Hardware Installation Guide
Performing internal line test using MALC-MTAC/RING-ENH card
•
Lowest battery voltage (measured) reports the voltage of battery with the lowest absolute value in volts.
•
Highest battery voltage (measured) reports the voltage of the battery with the highest absolute value in volts.
•
Positive battery voltage reports the positive battery voltage in volts.
•
Metering Voltage (measured) reports the peak metering signal voltage observed across tip and ring since the start of the metering pulse.
Receiver off-hook test The receiver off-hook test allows the MLT to determine if a loop has one or more telephones that are off-hook at the far end of the circuit. The following example provides the sample command and output: zSH> mtac-linetest 1/4/1 lookout receiveroffhook Successful - In TestMode Time Started: 9057457 Time Ended: 9057635 Receiver Off-Hook Test Results OFF-HOOK= No RLOOP out of range= Yes ----------------------------------------------------Successful - Returned to operational state
Receiver off-hook test results are described in the following table: Table 128: Receiver off-hook test result description OFF-HOOK
RLOOP out of range
Test Result Description
NO
NO
The DC Loop Resistance Test returned real resistance values, but they are not characteristic of an off-hook receiver.
YES
NO
This test measured loop resistances that suggest an off-hood receiver.
NO
YES
The DC Loop Resistance Test failed to measure loop resistance or returned an unreasonable result. This is most likely due to the receiver being on-hook.
YES
YES
This test never returns this result.
Ringer equivalency number test This test calculates the Ringer Equivalency Number (REN) for the telephone attached to the line. The test supports both the regular and electronic phone REN measurement techniques.
MALC Hardware Installation Guide
945
Metallic Test Access
The following example provides the sample command and output: zSH> mtac-linetest 1/3/42 lookout ringerequiv Successful - In TestMode Time Started: 415643 Time Ended: 415740 Ringer Equivalence Number Test Results REN= 0.49 RINGEQIV Measured Zload= 14.26 KOHMS COMMON MODE CURRENT Degradation= no -----------------------------------------------------Successful - Returned to operational state zSH>
Ringer equivalency number test result description:
•
REN reports the measured Ringer Equivalency Number (REN).
•
Measured Zload reports the measured ringer impedance in KOhms and only applies to the regular phone REN test. It is set to zero if the application ran an electronic phone REN test.
•
COMMON MODE CURRENT Degradation is YES if the test results may be inaccurate due to excessive common-mode current. This flag only applies to the regular phone REN test and is set to zero if the application ran an electronic phone REN test.
Ringing self test The ringing self test is a simulation of ringing on current able to be passed on the line. As a note, no actual ringing will be audible due to low voltage used. The following example provide the sample command and output: zSH> mtac-linetest 1/4/1 lookout ringingselftest Successful - In TestMode Time Started: 9061926 Time Ended: 9062086 Ringing Self-Test Results TEST PASSED= Yes RLOOP= 2.53 KOHMS ON HOOK TO OFF HOOK TRANSITION DETECTED= Yes ----------------------------------------------------Successful - Returned to operational state
This test is informational, and is used to determine if loop conditions on the line will allow ringing current to reach the far end of the circuit. This test should pass on valid loops.
946
MALC Hardware Installation Guide
Performing internal line test using MALC-MTAC/RING-ENH card
Ringing monitor test The ringing monitor test checks the external ringing voltage given the loop cannot be disconnected while supplying ringing and the ringing signal voltage cannot be reduced. The following example provides the sample command and output: zSH> mtac-linetest 1/4/1 lookout ringingmonitor Successful - In TestMode Time Started: 9078335 Time Ended: 9078393 Ringing Monitor Results Test Aborted due to off hook=No Ring Voltage= 0.00 VRMS(NONE) ----------------------------------------------------Successful - Returned to operational state
Ring monitor test result description:
•
Test abort due to off hook indicates whether the test was aborted due to off-hook detection at the beginning of the test.
•
Ring voltage reports the measured external ringing voltage in RMS volts.
Tone generation test This test generates up to four sinusoidal tones simultaneously. The following example provides the sample command, and the output for a succeeded test: zSH> mtac-linetest 1/4/1 lookout tonegeneration Successful - In TestMode Time Started: 9079951 Time Ended: 9080179 ----------------------------------------------------Successful - Returned to operational state
The tone generation test in the example is succeed although in the output didn’t show the data.
Trans-hybrid loss test This loop test characterizes the amount of echo from a far end trans-hybrid unit. This is only found in a telephone device, and is not a valid test on a dry pair for DSL. The following example provides the sample command and output: zSH> mtac-linetest 1/4/1 lookout transhybridloss Successful - In TestMode Time Started: 9081809 Time Ended: 9081938
MALC Hardware Installation Guide
947
Metallic Test Access
Transhybrid Loss Results ECHO= -84.13 dBm0 LOSS= 74.13 dBm0 ----------------------------------------------------Successful - Returned to operational state
Trans-hybrid loss test result description:
•
ECHO returns the measured signal echo power in dBm0.
•
LOSS returns the calculated trans-hybrid loss in dB.
Transmission self test The transmission self test attempts to determine if the line’s trans-hybrid loss using a test load is greater than an allowed minimum loss. The test load value should be greater than the lower limit value. A trans-hybrid device is only found in a telephone device, and is not a valid test on a dry pair for DSL. The following example provides the sample command and sample output: zSH> mtac-linetest 1/3/42 lookout transmissionselftest Successful - In TestMode Time Started: 429667 Time Ended: 429743 Transmission Self Test Results TEST PASSED= No TEST ABORT, OFF_HOOK= No TRANS-HYBRID LOSS OPEN= 53.30 TRANS_HYBRID LOSS RLOAD= 8.98 EXPECTED TRANS-HYBRID LOSS LOWER LIMIT= 20.83 EXPECTED TRANS-HYBRID LOSS UPPER LIMIT= VERY_HIGH_THL -----------------------------------------------------Successful - Returned to operational state zSH>
dB dB dB
This test is informational, and is used to determine trans-hybrid loss on a loop. This test should pass on valid loops. The loss on open circuits should read nominally 0. The loss on the test load should read higher than the loss lower limit. If the measured level is lower than stated lower limit, then it may indicate a problem with the line.
Troubleshooting with metallic loop tests To diagnose the problem in the metallic loop, may takes several different MTAC tests. The following examples provide the sample troubleshooting cases.
Phone is off-hook To troubleshoot whether the phone is off-hook, use the 3 element capacitance test and 3 element resistance test. The (T-R) CAPACITANCE value can be
948
MALC Hardware Installation Guide
Performing internal line test using MALC-MTAC/RING-ENH card
used to indicate whether there is a phone attached. In most cases, a capacitance less than 60 NFARADS indicates the Tip to Ring is open, there is no load (e.g. no phone attached); A value greater than 60 NFARADS indicates there is a load attached, possibly a phone set; A value “NOT MEASURED” indicates the Tip to Ring is shorted, and possibly the phone is off-hook. Note: A modern phone with electronic ringer may have less than 60 NFARADS between its Tip and Ring. The following examples in this section are not using the modern phone. Here is an example of phone is off-hook (with 9600ft cable): 1
At first, look the (T-R) CAPACITANCE value in the 3 element capacitance test output. A “NOT-MEASURED” value in T-R CAPACITANCE indicate the phone is possibly off-hook.
zSH> mtac-linetest 1/7/27 lookout 3elementcapacitance force Three-Element (T-G) (R-G) (T-R) (T-G) (R-G) (T-R)
capacitance Results CAPACITANCE= CAPACITANCE= CAPACITANCE= 55Hz AC IMPEDANCE= 55Hz AC IMPEDANCE= 55Hz AC IMPEDANCE=
2
155.09 156.71 NOT MEASURED 16.10 15.97 NOT MEASURED
NFARADS NFARADS KOHMS KOHMS
Then run the 3 element resistance test to verify the resistance value between Tip and Ring. The “748.47 OHMS” value in (T-R) DC RESISTANCE indicates the Tip and Ring are closed or shorted. Based on this information, then we can diagnosed that the phone is off-hook.
zSH> mtac-linetest 1/7/27 lookout 3elementresistance force Three-Element Resistance Results (T-G) DC RESISTANCE= (R-G) DC RESISTANCE= (T-R) DC RESISTANCE= (T-G) FOREIGN DC VOLTAGE= (R-G) FOREIGN DC VOLTAGE= TIP FOREIGN DC CURRENT= RING FOREIGN DC CURRENT=
> 1200 > 1200 748.47 NONE NONE 0.00 0.00
KOHMS ( OPEN DC ) KOHMS ( OPEN DC ) OHMS VOLTS VOLTS MILLIAMPS MILLIAMPS
Phone is on-hook Here is an example of phone is on-hook (with 9600ft 24 AWG cable): Run the 3 element capacitance test. Look the (T-R) CAPACITANCE value in the 3 element capacitance test output. In this example, the value “124.67 NFARADS” is greater than 60 NFARADS, it indicates the phone is on-hook. zSH> mtac-linetest 1/7/27 lookout 3elementcapacitance force
MALC Hardware Installation Guide
949
Metallic Test Access
Three-Element (T-G) (R-G) (T-R) (T-G) (R-G) (T-R)
capacitance Results CAPACITANCE= CAPACITANCE= CAPACITANCE= 55Hz AC IMPEDANCE= 55Hz AC IMPEDANCE= 55Hz AC IMPEDANCE=
151.11 151.75 124.67 16.52 16.49 20.21
NFARADS NFARADS NFARADS KOHMS KOHMS KOHMS
Phone is not attached Here is an example of no phone is attached: Run the 3 element capacitance test. Look the (T-R) CAPACITANCE value in the 3 element capacitance test output. In this example, the value “0.79 NFARADS” is less than 60 NFARADS, it indicates the Tip to Ring is open, there is no load (e.g. no phone attached). zSH> mtac-linetest 1/7/27 lookout 3elementcapacitance force Three-Element capacitance Results (T-G) CAPACITANCE= 1.62 NFARADS (R-G) CAPACITANCE= 1.59 NFARADS (T-R) CAPACITANCE= 0.79 NFARADS (T-G) 55Hz AC IMPEDANCE= 508.99 KOHMS (R-G) 55Hz AC IMPEDANCE= 552.75 KOHMS (T-R) 55Hz AC IMPEDANCE= > 1200 KOHMS (OPEN)
Both Tip and Ring are grounded Here is an example where the loop line is grounded on both Tip and Ring. In this case, both 3 element resistance and 3 element capacitance tests would fail, indicating the line is shorted and grounded. With the DC loop resistance test, it may be possible to use the loop resistance value to determine the distance of the line. 1
At first, run the 3 element capacitance test. “NOT-MEASURED” values indicate cannot measure these values in the loop line. zSH> mtac-linetest 1/7/26 lookout 3elementcapacitance force Three-Element (T-G) (R-G) (T-R) (T-G) (R-G) (T-R)
2
capacitance Results CAPACITANCE= CAPACITANCE= CAPACITANCE= 55Hz AC IMPEDANCE= 55Hz AC IMPEDANCE= 55Hz AC IMPEDANCE=
MALC Hardware Installation Guide
MEASURED MEASURED MEASURED MEASURED MEASURED MEASURED
Then run the 3 element resistance test. Look the (T-R) DC RESISTANCE value in the 3 element resistance test output. A “< 150” value is considered to be very small, and interpreted as a short circuit or fault.
zSH> mtac-linetest 1/7/26 lookout 3elementresistance force
950
NOT NOT NOT NOT NOT NOT
Performing internal line test using MALC-MTAC/RING-ENH card
Three-Element Resistance Results (T-G) DC RESISTANCE= < 150 (R-G) DC RESISTANCE= < 150
3
OHMS(FAULT) TEST HALTED OHMS(FAULT) TEST HALTED
And then run the DC loop resistance test with an 100 feet cable.
zSH> mtac-linetest 1/7/26 lookout dcloopresistance force DC loop resistance Test Results LOOP RESISTANCE= COMMON MODE CURRENT Phase 1= COMMON MODE CURRENT Phase 2= Voltage Saturation= COMMON MODE CURRENT Degradation=
4
0.07 0.00 0.00 No Yes
KOHMS MILLIAMPS MILLIAMPS
Or run the DC loop resistance test with a 9600 feet 24 awg cable.
zSH> mtac-linetest 1/7/26 lookout dcloopresistance force DC loop resistance Test Results LOOP RESISTANCE= COMMON MODE CURRENT Phase 1= COMMON MODE CURRENT Phase 2= Voltage Saturation= COMMON MODE CURRENT Degradation=
0.56 0.00 0.00 No Yes
KOHMS MILLIAMPS MILLIAMPS
Only Ring wire is grounded The following example shows how to use metallic test command to diagnose the Ring to Ground (R-G) is shorted, yet, the Tip to Ground (T-G) is open. 1
At first, run the 3 element capacitance test. “NOT-MEASURED” values indicate cannot measure these values in the loop line. zSH> mtac-linetest 1/7/26 lookout 3elementcapacitance force Three-Element (T-G) (R-G) (T-R) (T-G) (R-G) (T-R)
2
capacitance Results CAPACITANCE= CAPACITANCE= CAPACITANCE= 55Hz AC IMPEDANCE= 55Hz AC IMPEDANCE= 55Hz AC IMPEDANCE=
NOT NOT NOT NOT NOT NOT
MEASURED MEASURED MEASURED MEASURED MEASURED MEASURED
Then run the 3 element resistance test. It only shows (R-G) DC RESISTANCE value, didn’t show the (T-G) DC RESISTANCE value, and the value is “< 150”. This indicates Ring to Ground is shorted, Tip to Ground is open.
zSH> mtac-linetest 1/7/26 lookout 3elementresistance force Three-Element Resistance Results (R-G) DC RESISTANCE= < 150
OHMS(FAULT) TEST HALTED
MALC Hardware Installation Guide
951
Metallic Test Access
Auto-calibration When the mtac-linetest command is issued, prior to running the line test, the line card performs an auto-calibration.
Lookout block diagram Figure 110: Lookout block diagram
MALC Shelf Test Attach Architecture (T.A.A.) Block Diagram
AJK 2007-05-23
Lookin 1 Lookin 2
Lookin 1
Lookout 2
Lookout 1
Lookin 2
MALC Shelf Backplane
Lookout 1 Lookout 2
Bridge 2 Bridge 1
Lookin 1
Lookout 1
Lookout 2
Lookout 1
Lookout 2
Lookout 1
Lookout 1
Lookout 2
MTAC_ENH NC BP
PNL
RJ45
TST
PNL
TST
POTS LINE
Line Card Legacy T.A.A. Type 0
Line Card Current T.A.A. Type 1
Line Card Future T.A.A. Type 2
Line I/F
Line I/F
Line I/F
Line I/F
Line I/F
Line I/F
Line I/F
Line I/F
Line I/F
Line I/F
Line I/F
Line I/F
Line 3
Line 2
Line 1
Line 3
Line 2
Line 1
Line 3
Line 2
Line 1
Line 3
MPI
Line 2
Options: NC TST-BP TST-PNL BP-PNL
Line Card U.L.C. card T.A.A. Type 3
PCM
Line 1
External Test Access
NC BP
POTS Test section CPU
All Relays shown in their default or Normally Cosed position
Configuring external alarms The MTAC cards have a 26 pin connector that provides sensing of alarm relay contacts for up to 12 external devices. When an alarm condition occurs on the external device, the MALC sends a trap. Each of the 12 pairs of pins can be assigned to a different alarm. Use the num2str-profile to assign a description to an alarm relay. The description is included in traps and log messages. The num2str-profile uses an index in the form: shelf/slot/282/alarm-contact
The following example adds a description to the first alarm contact of a MTAC/RING card in shelf 12: zSH> update num2str-profile 1/12/282/1
952
MALC Hardware Installation Guide
Configuring an external clock
Please provide the following: [q]uit. name: -> {Relay 1}: cabinet open .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Configuring an external clock The MALC supports the following external clock sources:
•
A recovered clock from a T1/E1 line.
•
Building Integrated Timing Supply (BITS) clock.
Connecting a T1/E1 recovered clock to the MTAC card The network T1/E1 clock on the MTAC card appears to the system as a T1/E1 interface. To connect the clock source: 1
Connect the T1/E1 cable to the MTAC card external clock input port which is an RJ-45 port labeled CLOCK. This is used to source the clock to the shelf using standard T1/E1 pin connections.
2
Configure the system to use the clock, as explained in System clocking on page 205.
Connecting a BITs clock to the MTAC card The external clock input port on the MTAC card uses pins 6 and 8 for ground and pin 7 for the clock reference. To connect the BITS clock (also known as 2Mhz clock) source: 1
Connect the BITS clock signal to the MTAC card external clock input port which is an RJ-45 port labeled CLOCK, pin 7.
2
Connect the clock ground line to both pins 6 and 8 together. This selects use of the 2 MHz BITS clock instead of the T1/E1 recovered clock.
3
Configure the system to use the clock, as explained in System clocking on page 205.
Connecting an external ring source The MTAC card provides support for an external ring source to provide ringing voltage for the system.
MALC Hardware Installation Guide
953
Metallic Test Access
Caution: When connecting the external ring source, observe the following: If the external ring generator is an internal -48V reference (non-isolated), connect the top pin to the ringing voltage using a minimum 22 AWG wire, and leave the bottom pin unconnected. See Figure 111 on page 954. If the external ring generator requires an external -48V reference (isolated), connect the top pin to the ringing voltage using a minimum 22 AWG wire and the bottom pin to -48V on the ring source. See Figure 112 on page 954. Figure 111: Connecting a non-isolated ring source
Figure 112: Connecting an isolated ring source
After connecting the ring source, update the system profile to specify an external ring source:
954
MALC Hardware Installation Guide
MTAC cards pinouts
zSH> update system 0 Please provide the following: [q]uit. syscontact: ----------> {Zhone Global Services and Support 7001 Oakport Road Oa kland Ca. (877) Zhone20 (946-6320) Fax (510)777-7113
[email protected]}: sysname: -------------> {Zhone Malc}: syslocation: ---------> {Oakland}: enableauthtraps: -----> {disabled}: setserialno: ---------> {0}: zmsexists: -----------> {false}: zmsconnectionstatus: -> {inactive}: zmsipaddress: --------> {0.0.0.0}: configsyncexists: ----> {false}: configsyncoverflow: --> {false}: configsyncpriority: --> {high}: configsyncaction: ----> {noaction}: configsyncfilename: --> {}: configsyncstatus: ----> {syncinitializing}: configsyncuser: ------> {}: configsyncpasswd: ----> {}: numshelves: ----------> {1}: shelvesarray: --------> {}: numcards: ------------> {3}: ipaddress: -----------> {0.0.0.0}: alternateipaddress: --> {0.0.0.0}: countryregion: -------> {us}: primaryclocksource: --> {0/0/0/0/0}: ringsource: ----------> {internalringsourcelabel}: externalringsourcelabel revertiveclocksource: -> {true} voicebandwidthcheck: --> {false} .................... Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
MTAC cards pinouts This section lists the pinouts for the following interfaces on the MTAC cards (MTAC/RING-ENH, MTAC/RING, and MTAC/RING-FC):
•
External ring generator input port pinouts
•
External alarm sense pinouts
•
Examples of alarms with specific pinouts
•
Metallic test access port pinouts
•
External test set control port pinouts
•
External clock input port pinouts
MALC Hardware Installation Guide
955
Metallic Test Access
External ring generator input port pinouts The MTAC cards provide an external ring generator input port for access to external ring generator.
active fault pwr fail
Figure 113: MTAC/RING-ENH and MTAC/RING cards external ring generator input connector pinouts
1 2
EXT RING A L A R M C L O S U R E T E S T T E S T
A C C E S S C T R L
C L O C K
MTAC/RGR
Figure 114: MTAC/RING-FC card external ring generator input connector pinouts
1 2
BAT OK
A minor major ALARM
NO C NC NO C NC
CONTROL ACCESS
1
2
B critical CRITICAL MAJ/MIN fan ALARM OUTPUTS
CLOCK
METALLIC TEST
EXTERNAL RING GEN
ALARM INPUTS
active fault pwr fail
Table 129 lists the pinouts for the external ring generator. Table 129: External ring generator pinouts
956
Pin
Function
1
Ring Power Input
2
-48V Output
MALC Hardware Installation Guide
MTAC cards pinouts
External alarm sense pinouts The MTAC cards provide a 26-pin connector for access to external alarms. The MTAC cards accept 48-volt inputs directly. All alarm inputs are metallically isolated using optocouplers. All MTAC/RING-ENH cards take 48 volts directly. Check with Zhone GSS for use of alarm sense contacts on Revision L or earlier MTAC/RING cards. Figure 115: MTAC/RING-ENH and MTAC/RING card external alarm connector pinouts
Figure 116: MTAC/RING-FC card external alarm connector pinouts
Table 130 lists the pinouts for the 26-pin connector for access to external alarms.
MALC Hardware Installation Guide
957
Metallic Test Access
Table 130: MTAC card external alarm connector pinouts External alarm
Pin
Function
N/A
1
-48V supply for external contacts (fused)
1
2
Input (+)
3
Input (-)
4
Input (+)
5
Input (-)
6
Input (+)
7
Input (-)
8
Input (+)
9
Input (-)
10
Input (+))
11
Input (-)
12
Input (+)
13
Input (-)
14
Input (+)
15
Input (-)
16
Input (+)
17
Input (-)
18
Input (+)
19
Input (-)
20
Input (+)
21
Input (-)
22
Input (+)
23
Input (-)
24
Input (+)
25
Input (-)
26
48V return (+)
2
3
4
5
6
7
8
9
10
11
12
N/A
958
MALC Hardware Installation Guide
MTAC cards pinouts
Examples of alarms with specific pinouts The following example shows alarms 10 and 12 for a single MTAC/ RING-ENH (any version) or MTAC/RING (version M or greater). See Table 130 for other alarm pin numbers. Figure 117: Single MTAC/RING-ENH or MTAC/RING Sample Connections
-48V 1
Optional Diode
10 19
Alarm_10(+) Alarm_10(-)
Con 10 Alarm Contacts
Alarm_12(+) Alarm_12(-) 48V RTN
Con 12
Optional Diode 9
18
26
MALC Hardware Installation Guide
959
Metallic Test Access
The following example shows alarms 10 and 12 for a redundant MTAC cards with any combination of a MTAC/RING or MTAC/RING-ENH, using board-supplied contact voltage. See Table 130 for other alarm pin numbers. Figure 118: Redundant MTACs: Any Combination of MTAC/RING, MTAC/ RING-ENH Example Connections
In 4002 or Equivalent (4 Places) -48V 100V 1A
1 10 19
Alarm
Con 10
Alarm_10(+) Alarm_10(-) Alarm_12(+ Alarm_12(-) 48V RTN
18 26
9
-48V 1 10 19 Alarm_10(+) Alarm_10(-) Alarm_12(+) Alarm_12(-) 48V RTN
9
960
MALC Hardware Installation Guide
18
26
Con 12
MTAC cards pinouts
The following example shows alarms 10 and 12 for a single MTAC/ RING-ENH (any version) or MTAC/RING (version M or greater). See Table 130 for other alarm pin numbers. Figure 119: Single MTAC/RING-ENH or MTAC/RING with Externally Supplied Contact Voltage
1
10 19
Alarm_10(+) Alarm_10(-)
Con 10 Alarm Contacts
Alarm_12(+) Alarm_12(-) 48V RTN
9
18
Con 12
26 -48V 48V RTN
The following example shows alarms 10 and 12 for redundant MTAC cards with combination of MTAC/RING-ENH (any version) or MTAC/RING (version M or greater) with an externally supplied contact voltage.
MALC Hardware Installation Guide
961
Metallic Test Access
Figure 120: Redundant MTACs: Any Combination of MTAC/RING, MTAC/ RING-ENH with Externally Supplied Contact Voltage
Alarm Contacts
1 10 19 Alarm_10(+) Alarm_10(-) Alarm_12(+) Alarm_12(-)
9
Con 10
Con 12
26
1
-48V -48V RTN
1
10 19 Alarm_10(+) Alarm_10(-) Alarm_12(+) Alarm_12(-)
9
18
26
Metallic test access port pinouts The MTAC cards provide a metallic test access port for access to an external test set.
962
MALC Hardware Installation Guide
MTAC cards pinouts
active fault pwr fail
Figure 121: MTAC/RING-ENH and MTAC/RING cards metallic test access port pinouts
EXT RING A L A R M C L O S U R E T E S T T E S T
1 2 3 4 5 6 7 8
A C C E S S C T R L
C L O C K
MTAC/RGR
Figure 122: MTAC/RING-FC card metallic test access port pinouts
87654321
BAT OK
NO C NC NO C NC
CONTROL ACCESS
1
2
B
A
critical CRITICAL MAJ/MIN fan
minor major ALARM
ALARM OUTPUTS
CLOCK
METALLIC TEST
EXTERNAL RING GEN
ALARM INPUTS
active fault pwr fail
Table 131 lists the pinouts for the MTAC card metallic test access port. Table 131: MTAC card metallic test access port Pin
Function
1
Test in tip 1
2
Test in ring 1
3
Test out tip 1
4
Test out ring 1
5
Test in tip 2
6
Test in ring 2
MALC Hardware Installation Guide
963
Metallic Test Access
Table 131: MTAC card metallic test access port Pin
Function
7
Test out tip 2
8
Test out ring 2
External test set control port pinouts The MTAC cards provide an external test set control port to provide a control connection to the external test set. Table 132 lists the pinouts for the MTAC card external test RS232 control port. * Factory test signals do not connect on MTAC/RING-ENH. Table 132: MTAC card external test control port pinouts
964
Pin
Function
1
*Reserved
2
*Reserved
3
*Reserved
4
Signal Ground (SGND)
5
Transmitted (TxD) (Out)
6
Received (RxD)(In)
7
NC
8
NC
MALC Hardware Installation Guide
MTAC cards pinouts
External clock input port pinouts The MTAC cards provide an external clock input port to connect T1/E1 or BITS external clock reference. Table 133 lists the pinouts for the MTAC card clock port. Pinouts follow the standard RJ45 specifications with pins 1 and 2 for receive and pins 4 and 5 for transmit. Pins 6, 7, and 8 are used for 2.048 MHz square wave signals when the line-type in the DS1 profile is set to other. * Connect BITS select to ground to use BITS clock input. Table 133: MTAC card external clock pinouts Pin
Function
1 T1/E1
Rx ring
2 T1/E1
Rx tip
3
Not used
4 T1/E1
Tx ring
5 T1/E1
Tx tip
6
BITS Select *
7
BITS clock
8
GND
MALC Hardware Installation Guide
965
Metallic Test Access
966
MALC Hardware Installation Guide
INDEX Numerics 2B1Qcard 908 48-port ADSL Cards Annex A/Annex M 636 48-port ADSL cards Annex B 636 48-port ADSL+POTS cards 632, 643 4B3Tcard 902 802.1p priority queuing 545
A accessing the flash card cd command 76 dir command 76 pwd command 76 acronyms, described 22 activating slot cards 24-port ADSL Reach DSL card 649 48-port ADSL cards 645 48-port ADSL+Splitter card 647 Active Ethernet 10 port card 899 ADSL Annex A cards 645 ADSL cards 456, 462, 465, 475, 830 ADSL+POTS 48 card 646 ADSL+POTS 48 card for TDM voice 645 description 100 POTS card 646, 647, 648, 775, 776 slot card installation 650, 715, 748, 761, 777, 810, 838, 866, 877, 905, 911, 923 ULC cards 761, 763, 767, 904, 910 Active Ethernet 10 port card 894 adding a user, description of 82 adding routes description 199 route add command 199 addresses assigned via DHCP 200 admin deleting user account of 83 administration configuring traps 114 creating SNMP access lists 113
creating SNMP community names 113 logging 136 saving and restoring configurations 80 user accounts 82 ADSL ADSL S=1/2 670 configuring tone ranges 655 downstream interface 659 low power alarm 132 upstream interface 660 ADSL 2 and ADSL 2+ configuring 676 support 676 ADSL interfaces verifying the interface 663, 678, 684, 751 ADSL+POTS-TDM/PKT-48A/2S card 632 ADSL+POTS-TDM/PKT-48A/M-2S card 632 ADSL+POTS-TDM-48A/M-2S card 632 ADSL+POTS-TDM-48A-2S card 632 ADSL-24 slot card specifications 641 alarm suppression 133 alarms 957 external on MTAC/Ring cards 957 low power ADSL 132 viewing card and shelf 88 alarms, viewing 124 A-Law setting 386 always offhook, configuring 405 APS configuration 565, 570 ARP, broadcasts and bridging 247 ata command, use of 76 ATM ATM to TDM interworking overview 35 bridging and IP support on VC 175, 242, 271 CAC 357 Circuit Emulation Service (CES) 829 cross connects 348 EPD and PPD 348 IMA groups guidelines for 586, 609, 820 IMA groups, configuring 583, 605, 816 IMA links, moving to another group 587, 610,
MALC Configuration Guide
967
Index
821 overview 346 overview of support 33 PVCs supported per card 350 SCR and PCR 353 SCR and PCR, configuring allowable values for 368 statistics 365 traffic descriptor configuration rules 354 traffic descriptor validation 360 traffic descriptors 353 general rules 356 traffic policing 360 UBR and usage-parameter-control 368 video 348 voice overview 347 VPI/VCI ranges 350 ATM cell relay connection configuration 365, 372 creating cross-connect 378, 379 creating traffic descriptor 365, 372 creating VCLs 376, 377 creating VCLs and VPLs 374 ATM cell termination connection adding IP route to remote LAN 64 configuration 67 creating IP interface 67 verifying IP interface 64 ATM data connection cell relay 365, 372 configuration 347 data communications 347 traffic descriptors 353 VCLs 352 VPLs 352 ATM management connection creating IP interface 67 ATM OC3-c interfaces configuration 565 disabling SONET interface 568 loopbacks 161 ATM on Zhone devices data communications 347 overview 347 virtual channel links 352 virtual path links 352 ATM traffic descriptor creating 67 automatic baud rate detection SDSL 717
968
MALC Configuration Guide
B BER test, described 153 binding interfaces 79 bootfile parameter 204 boot-server parameter 204 BRAs 339 bridge statistics 261 bridgeinsertpppoevendortag 342 bridging 271 adding untagged bridge 272 administrative commands 261 ARP broadcast 247 custom DHCP server 312 forbid OUI 342 intralinks 256 option 82 342 overview 241 support on VC 175, 242, 271 VLAN bridge-paths 252 VLAN configuration 271 VLAN overview 271 VLAN strip and insert 273 broadcast suppression, described 312
C cables DS3/E3 redundant 556, 560 EFM T1/E1-24 card cable 738, 851 MALC 2-GE Uplink cards 533 cables and conectors T1/E1-IMA-8 uplink card 599 cables and connectors 8-port T1/E1 to dual 50-pin 611, 614 DS3/E3 cable 560 DS3/E3 uplink 560 MALC 2-GE Uplink cards 533 non-redundant TDM uplink cable 591 redundant TDM uplink cable 588 T1/E1 IMA card 610 CAC described 357 call conferencing, SIP 413 call progress parameters 436 caller, rejecting malicious 412 caller-id-sig-protocol 437 card command 50 card profiles, adding, changing, deleting 50
cards 48-port ADSL cards 636 48-port ADSL+POTS cards 632 Active Ethernet 10 port card 894 DS3/E3 uplink 552 EFM T1/E!-24 734, 836 MALC 2-GE Uplink 530 MALC t1/E1 12 CES 829 ReachDSL-24 640 T1/E1-IMA-8 uplink card 595 types 643, 714, 736, 747, 810, 838, 865, 877, 919 Uplink types 104 VG-T1/E1-32-2S 37, 453, 789 viewing active redundant 716, 811, 924 cd command, use of 76 cdvt_btA, formula used to calculate 360 cdvt_btB, formula used to calculate 360 CES 829 structured and unstructured 829 change default passwords, how to 83 channel bank, configuring system 416 chassis viewing errors 88 viewing temperature 88 Circuit Emulation Service (CES) 829 Class of Service (COS) 274, 281 clid-mode 438 client leases, DHCP 239 clientId parameter 215 client-match-string parameter 215 clock setting system using NTP 90 clocking 91 BITS clock ds1-profile on MTAC/Ring card 90 BITS clock on MTAC/Ring card 91 configuring system in system profile 96 eligible and non-eligible sources 97 external clock on MTAC/Ring 953 for SDSL interfaces 720 manually changing system clock 96 revertive 95 specifying DS3/E3 93 specifying OC3-c/STM1 94 specifying T1/E1 93 viewing system 97 commands ata 76 cd 76 dir 76
dslstat 725 get 565 host add 190 host delete 237 host show 234 ifxlate 67 image 77 interface add 195 interface delete 237 interface show 235 log 138 log show 138 mcast 518 pwd 76 rip 199 rip show 236 route 228 route add 199 route delete 237 route show 236 showlinestatus 720 stack bind 80 configurable jitter buffer 434 configuration ATM cell relay connection 365, 372 ATM cell termination connection 67 ATM data connection 347 ATM OC3-c interfaces 565 ATM VCLs and VPLs 374 CLI disabled 61 creating DHCP server subnet options 203 creating dhcp-server-group profile 215 creating dhcp-server-host profile 215 DHCP server 200 DNS resolver 216 DS3/E3 uplink 554 Ethernet management channel 188 host-based routing 190 interface indexes 495, 504 local management channel 45 logging in 46 logging out 46 network-based routing 195 overview of profiles 28 RIP 199 saving and restoring 80 SDSL 720 SDSL/SHDSL interface 716, 721 SHDSL interface 721 specifying DSL interface 717
MALC Configuration Guide
969
Index
verifying interfaces 663, 678, 684, 720, 725, 751 configuring ATM data connection ATM cell termination connection 67 ATM on Zhone devices 347 cell relay connections 379 configuring IP DHCP server 200 displaying routing information 236 DNS resolver 216 host-based routing 190 modifying host and interface routes 232 network-based routing 195 RIP 199 static routes 199 configuring management interface accessing the serial port 45 local management channel 45 logging in and out 47 configuring physical interfaces ATM OC3-c interfaces 565 disabling SONET interface 568 loopbacks 161 SDSL 720 SDSL/SHDSL interfaces 716, 721 SHDSL interfaces 721 specifying DSL interface 717 verifying interfaces 663, 678, 684, 720, 725, 751 configuring traps, description of 114 continuing 867 COS processing 212 COS, in VLAN headers 274, 281 craft interface 47 creating IP interface adding route to remote LAN 64 description 67 ifxlate 67 specifying VPI/VCI pair 67 verifying the interface 68 creating IP management interface description 67 creating SNMP access lists, description of 113 creating SNMP community names, description of 113 cross-connect, creation of 378, 379
970
MALC Configuration Guide
D D channel status, ISDN PRI 487 Data rate delay criteria 352 throughput criteria 352 default passwords, changing 83 default-lease-time parameter 204 default-router parameter 204 deleting a user, description of 83 deleting hosts 237 deleting interfaces 237 deleting routes description 237 route delete command 237 DHCP address assignment 200 advanced applications 214 broadcast suppression 312 creating subnet options 203 custom DHCP setting in bridge records 312 enabling a DHCP server 205 external server 208 logging 237 logging messages described 238 profiles 200 relay 207 setting server options 201 DHCP client leases 239 DHCP server 177 DHCP server, enabling 205 DHCP, description of 177 dhcp-server-group profile 215 dhcp-server-host profile 201, 215 dhcp-server-subnet profile 203 dialing plan 410 dir command, use of 76 displaying host information 234 displaying interface information 235 displaying RIP information 236 displaying routing information rip show command 236 route show command 236 routing table 236 DNS resolver configuration creating a host profile 217 creating a resolver record 217 DNS, description of 177 Domain Name System, see DNS
domain parameter 204, 217 domain-name parameter 204 DS1 to POTS configuring connection 416 DS3 call admission control 356 DS3/E3 6 inch cable and 556, 560 DS3/E3 card card profiles 866 DS3/E3 line card 866, 867, 868 card profiles 866 configuring interfaces 868 description 862 listing profiles 867 verifying installation 866 DS3/E3 Uplink card cabling description 560 DS3/E3 uplink card 552 DSL ADSL S=1/2 670 fixed bit rate settings and training rates 717 DSL interfaces SDSL configuration 720 specifying interface type 717 verifying the interface 720 dual counter rotating rings, RPR 320 Dynamic Host Control Protocol, see DHCP
E E1 interface defaults 579, 600, 812, 841 E1, over ATM or IP circuit 829 EFM SHDSL-24 NTP, NTWC card overview 734 EFM T1/E1-24 card card profile 736, 838 network scenario 735, 837 overview 734, 836 profile 735, 837 encoding types supported 386 EPD, described 348 errors, viewing system 88 Ethernet Linear GigaBit configuration 334 Linear GigaBit redundancy configuration 335 Resilient Packet Ring (RPR) 31, 317
Ethernet interface configuration 62 creating a default route 63, 189 creating a route from management PVC to 68 IP interface 62 route show command 63, 189 verifying 63 verifying the route 63, 189 Ethernet management channel 188 Ethernet OAM 848
F fax service, T.38 448 FE/GigE-2 card line type 535 feature overview 29 first-nameserver parameter 217 flash cards card sizes in redundant pair 100, 792 functionality, feature overview 29 FXS adding gain and loss 690, 779
G G.SHDSL-24 slot card specifications 713 gain, adding 690, 779 GigE-2 card line type 535 Linear GigaBit Ethernet configuration 334 Linear GigaBit Ethernet redundancy 335 GPON 1-port card 875 GR-303 configuring 494 groundstart, configuring 781 groupSymmetry parameter 584, 606, 817
H H.248, configuring 399 hookflash configuring 403 configuring timers 404 host add command 190 host delete command 237 host profile 218 host show command 234
MALC Configuration Guide
971
Index
hostalias1 parameter 218 hostalias2 parameter 218 hostalias3 parameter 218 hostalias4 parameter 218 host-based routing configuration 190 description of 182 hostname parameter 218 huntgroups 406 hwaddr parameter 215
I ifindex parameter 927 if-translate profile renaming interfaces in 80 IMA group guidelines 586, 609, 820 groupSymmetry 584, 606, 817 links, moving 587, 610, 821 minNumTxLinks 584, 606, 817 parameters 584, 606, 817 IMA groups configuring 583, 599, 604, 605, 816 image command, use of 77 interface add command 195 interface delete command 237 interface groups number supported on Voice Gateway card 455 interface indexes, configuration of 495, 504 interface show command 235 commands interface show 235 interfaces DS3/E3 uplink 557 line speeds for DSL interfaces with fixed bit rates 717 renaming 80 specifying type of MTAC/Ring card 919, 921 intermediate agent, PPPoE 342 Internal ringer not detected, error message 919 internetworking, PPPoA-PPPoE 339 Intralinks configuring 256 Inverse Multiplexing over ATM, See IMA IP addresses for redundant Uplink cards 63 administrative procedures 232 advanced provisioning procedures 214
972
MALC Configuration Guide
applications 180 Circuit Emulation Service (CES) 829 DHCP external server 208 DHCP relay 207 overview 176 provisioning procedures 188 routing 180 support on VC 175, 242, 271 video, configuring 513 IP filtering description of 186 IPSLA 218 ISDN loopbacks 165 overview 39 packet voice 760, 903, 909 ISDN 2B1Q card 908 ISDN 4B3T card 902
J jitter buffer 434
L lease-time parameter 202 line testing, MTAC 926 Linear GigaBit Ethernet, configuration 334 Linear GigaBit Ethernet, redundancy configuration 335 line-type FE/GigE card 535 GigE-2 card 535 local management channel 45 log messages, description of content for 136 logging description 136 DHCP 237 DHCP messages described 238 displaying persistent logs 140 enabling/disabling 136 enabling/disabling for session 47 enabling/disabling over the serial craft port 47 log messages 136 modifying logging levels 138 syslog, configuring 141 logging in and out description 47 logout command 47
timeout command 47 logging in, restricting telnet access 97 logging levels, log command and modifying 138 logging out, described 46 loopbacks DS3 163 ISDN 165 T1 163 loopbacks, SONET and 161 loopstart, configuring 781 loss, adding 690, 779
M
N name parameter 215 netmask parameter 204 network parameter 204 network-based routing configuration 195 description of 184 non-redundant TDM uplink cable cable description 591 NTP configuring 90
O MALC 2-GE Uplink cards 530 malicious caller, rejecting 412 management configuring interface for 62 creating route from management PVC to Ethernet 68 creating VLAN for 64 for dual non-redundant Uplinks 111 ZMS 61 managment Zhone Web Config Tool 58 max-lease-time parameter 202, 204 mcast command, described 518 Megaco, configuring 399 MGCP configuring 392 MGCP, configuring 396 min-lease-time parameter 202, 204 minNumTxLinks parameter 584, 606, 817 modems DSL training rates 717 MTAC/Ring card BITS clock on 90 configuring redundancy 920 external alarm contacts 957 ifindex 927 parameters 927 specifying line type for 919, 921 test_mode 927 MTAC/Ring external contacts 957 Mu-Law setting 386 multicast creating control list 517
OAM 848 OC3-c/STM1 APS 570 attenuation 565 option 82, described 342 OUI forbin, described 342 overview 31
P packet voice configuring POTS card for 775 parameters bootfile 203 boot-server 203 clientId 215 client-match-string 215 default-lease-time 203 default-router 203 domain 203, 217 domain-name 203 first-nameserver 217 hostalias1 218 hostalias2 218 hostalias3 218 hostalias4 218 hostname 218 hwaddr 215 IMA 584, 606, 817 lease-time 202 max-lease-time 202, 203 min-lease-time 202, 203 MTAC/Ring card 927 name 215
MALC Configuration Guide
973
Index
netmask 203 network 203 primary-name-server 203 query-order 217 range1-end 203 range1-start 203 range2-end 203 range2-start 203 range3-end 203 range3-start 203 range4-end 203 range4-start 203 reserve-end 202 reserve-start 202 secondary-name-server 203 second-nameserver 217 third-nameserver 217 vendor-match-string 215 passwords, changing default 83 PCM encoding type supported 386 persistent logs, displaying 140 pinouts external alarm 957 policing, ATM 360 POTS adding gain and loss 690, 779 configuring card for packet voice 775 configuring card for TDM voice 760, 763, 774 configuring groundstate 781 configuring loopstart 781 DS1 to POTS 416 POTS card 24 port card overview 756 48 port card overview 758 POTS cards support for packetized voice 42 types 759 POTS-48 slot card specifications 758 power ADSL low power alarm 132 PPD, described 348 PPP tunnel 339 PPPoA-PPPoE internetworking 339 PPPoE intermediate agent 342 primary-name-server parameter 204 profiles dhcp-server-group 215 dhcp-server-host 201, 215
974
MALC Configuration Guide
GigE-2 uplink cards 542 host 218 overview of configuration 28 resolver 217, 218 protection switching, RPR 325 PVCs number supported per card 350 pwd command, use of 76
Q QoS and traffic descriptors QoS categories described 352 non-real-time variable bit rate 353 Quality of Service, see QoS query-order parameter 217
R RADIUS 84 range1-end parameter 204 range1-start parameter 204 range2-end parameter 204 range2-start parameter 204 range3-end parameter 204 range3-start parameter 204 range4-end parameter 204 range4-start parameter 204 ReachDSL-24 card 640 redundancy 31 configuring Uplink 100 DS3/E3 cables 556, 560 flash card sizes 100, 792 IP addresses and 63 MTAC/Ring 920 viewing active cards 716, 811, 924 viewing status information about 107 redundant TDM uplink cable cable description 588 reserve-end parameter 202 reserve-start parameter 202 resetting passwords, description of 84 Resilient Packet Ring (RPR) bridged traffic 331 configuration 324 configuration display 326 overview 31, 317 protection switching 325
ring status 329 statistics 330 topology 319 topology display 327 resolver profile 217, 218 ring cadence 436 RIP configuration 199 configuring global defaults 199 description 177 displaying information 236 rip command 199 rip show command 236 route command 228 routing description 180 routing information base 180 routing in Zhone systems route types 180 routing information base, description of 180 Routing Information Protocol, see RIP routing table, displaying 236 RPR 31, 317
S SABR 200 Saving and restoring configurations 81 saving and restoring configurations description 77 SDSL clocking from network 720 SDSL/HDSL2 cards configuration 720 SDSL/SHDSL interfaces configuration 716, 721 secondary-name-server parameter 204 second-nameserver parameter 217 security restricting telnet access 97 SELT 694 server-max-timer, voice-system profile 393 service level agreement, SLA 218 Service, quality objectives 352 SFP 545, 896 SHDSL connecting LP card to Raptor 100 731, 739 SHDSL interfaces configuration 721
verifying the interface 725 Single End Loop Tests (SELT) 694 SIP connections over different networks 392 SIP, call conferencing 413 SIP, calls not registering 393 sip-dialplan 410 SLMS Web Interface Tool 58 slot cards 48-port ADSL cards 636 48-port ADSL+POTS cards 632 activating 100 Active Ethernet 10 port card 894 ADSL-24 specifications 641 G.SHDSL-24 specifications 713 installation verifying 650, 715, 748, 761, 777, 810, 838, 866, 877, 905, 911, 923 POTS-48 specifications 758 ReachDSL-24 640 redundancy 31 Uplink-DS3/E3 specifications 552 Uplink-OC3-c/STM1 specifications 563 Uplink-T1/E1 specifications 596 Uplink-TDM/ATM specifications 574 Small Form Factor Pluggables 545, 896 SNMP statics, gathering 115 SONET disabling interface 568 loopbacks 161 source address based routing 200 stack bind 80 standards, support for IP 30 static routes adding routes 199 configuration 199 deleting routes 237 statistics ATM 365 bulk 115 statistics, bridge interfaces 261 strip and insert configuring 273 subtending, example ATM subtending 380 syslog server, configuring 141 system 91 activating slot cards 100
MALC Configuration Guide
975
Index
clocking 91 configuring ATM data connection 347 configuring management interface 45 data communications 347 Ethernet interface 62 feature overview 29 logging out 46 management interface 62 Uplink cards 62 system profile clocking and 96 voice configuration 386
T T.38 fax service 448 T.38, on voicegateway 460 T1 interface defaults 579, 600, 812, 841 T1 loopbacks activating 159, 163 T1, over ATM or IP circuit 829 T1/E1 Uplink card cable description 611, 614 T1/E1, EFM line card 734, 836 T1/E1-IMA-8 uplink card 595 DS1/E1 interfaces 599 tagged bridging described 241 TDM voice configuring POTS card for 760, 763, 774 telnet restricting access 97 temperature, viewing chassis 88 terminal interface, settings for 45 test_mode parameter 927 TFTP server 98 third-nameserver parameter 217 three-way call conferencing 413 tone ranges, on ADSL card 655 TOS processing 212 tosCOS 213 tosOption 213 traffic descriptors configuration rules 354 creation 365, 372 description 353 QoS rules for 356
976
MALC Configuration Guide
validation for 360 traps configuring 114 Type of Service (TOS) 212 types, listing of cards 643, 714, 736, 747, 810, 838, 865, 877, 919 types, listing of POTS cards 759 types, listing of Uplink cards 104
U UBR modem train rates and 368 ULC card pinouts 911 specifications 756, 902, 908 unnumbered IP interfaces description of 187 untagged bridging described 241 Uplink 2-GE card specifications 531 Uplink card redundancy and IP addresses 63 Uplink cards configuration 62 dual, non-redundant 108 dual, non-redundant and management 111 E1 defaults 579, 600, 812, 841 redundancy configuration 100 T1 defaults 579, 600, 812, 841 VOIP support and 454 uplink cards adding a redundant 535 DS3/E3 uplink 552 MALC 2-GE Uplink cards 530 T1/E1-IMA-8 595 Uplink-DS3/E3 slot card specifications 552 Uplink-OC3-c/STM1 slot card specifications 563 Uplinks types supported 27 Uplink-T1/E1 slot card specifications 596 Uplink-TDM/ATM slot card specifications 574 Upljnk cards flash card sizes in redundant pair 100, 792
user accounts adding a user 82 changing default passwords 83 deleting a user 83 deleting admin 83 resetting passwords 84 using flash cards using the ata command 76 using the image command 77
V V5.2 activating the IG 510 C-channels 506 C-paths 508 IG 503 overview 40 parameters 500 provisioning links 505 V5.2 profile, configuring 499 VCI allowed ranges 350 VCLs creation 376, 377 description 352 VCLs and VPLs creation 374 vendor-match-string 215 video ATM 348 configuring IP 513 multicast control list 517 virtual channel link, see VCL VLAN bridge-paths and 252 creating management 64 VLAN IDs supported 271 vlanCOS 213 VLANs configuring 271 IDs supported 271 overview 271 strip and insert 273 VoATM to TDM voice connections 465 voice always offhook 405 configuring MGCP 392 configuring VOIP 391
hookflash 403 hookflash timers 404 ISDN 2B1Q card 908 ISDN 4B3T card 902 packet voice on ISDN cards 760, 903, 909 packetinzed voice support on POTS cards 42 POTS 24 card 756 POTS 48 card 758 POTS to DS1 416 POTS to VOIP 402, 482 VoATM to TDM connections 465 voice gateway 37, 453, 789 VOIP to TDM connections 456 voice configuration PCM encoding supported 386 system profile 386 voice gateway adding 791 cable pinouts 794 configuration 455 overview 37, 453, 789 redundant card 792 VoATM to TDM connections 465 VOIP to TDM connections 456 Voice Gateway card number of IGs supported 455 Uplink cards supported with 454 VP- and VC-switching on 466 VOIP always offhook, configuring 405 call progress parameters 436 configuring voice gateway connections 391 hookflash, configuring 403 hookflash, configuring timers 404 malicious caller 412 POTS to VOIP 402, 482 ring cadence 436 SIP connections 392 support on POTS cards 42 Uplink cards that support 454 VOIP to TDM voice connections 456 voip, country-specific dialing features 435 VPI allowed ranges 350 VPLs description 352
MALC Configuration Guide
977
Index
W Web Configuration Tool configuraiton, Web tool 58 Web Interface Tool 58
Z ZMS CLI configuration disabled 61 managing device with 61
978
MALC Configuration Guide
