v1 Anymedia Access System

AnyMedia® Access System
Commands and Procedures for IP-based

Services
Releases upto 1.38.1 and R3.6
363-211-555
CC109562736
Issue 10
September 2008
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their
respective owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright © 2008 Alcatel-Lucent. All Rights Reserved.
Notice
Every effort has been made to ensure that the information contained in this information product was accurate at the time of printing. However,
information is subject to change.
Ordering information
See “How to order” (p. xx).
Technical support
Technical support is available for AnyMedia Access System indoor/outdoor applications, for AnyMedia Access System 800, for AnyMedia LAG
System, and for AnyMedia Element Manager (Navis AnyMedia Element Manager).
AnyMedia service is complemented by a full range of services available to support planning, maintaining and operating your system.
Applications testing, network integration, and upgrade conversion support is available.
Alcatel-Lucent service personnel will troubleshoot field problems 24 h a day over the phone and on site (if necessary) based on Alcatel-Lucent
service contracts by Local/Regional Customer Support (LCS/RCS) and by Remote Technical Support (RTS).
Contacting your Alcatel-Lucent support: For Europe call the International Customer Management Center (ICMC): +353 1692 4579 or call the
toll free number: 00 800 00 58 2368. For Asia Pacific, Caribbean and Latin America Region, Saudi Arabia, Middle East and Africa call the
local Alcatel-Lucent Customer Technical Support Team. For north and south America (NAR and CALA) call the Customer Technical
Assistance Management (CTAM): +1 866 Lucent8 (prompt#1) or +1 630 224 4672 from outside the United States.
Contents
About this information product

Purpose ........................................................................................................................................................................................... xv
Reason for reissue .................................................................................................................................................................... xvi
History ........................................................................................................................................................................................... xvi
Safety information ................................................................................................................................................................... xvii
Intended audience .................................................................................................................................................................... xvii
Conventions used ................................................................................................................................................................... xvii
Related documentation for the international regions ............................................................................................... xviii
Related documentation for the North America regions ............................................................................................. xix
How to order ................................................................................................................................................................................ xx
How to comment ........................................................................................................................................................................ xx
1 Safety
Overview ...................................................................................................................................................................................... 1-1
Structure of hazard statements ............................................................................................................................................ 1-2
General safety information ................................................................................................................................................... 1-4
Appearance of the safety instructions .............................................................................................................................. 1-7
Relevant safety instructions .................................................................................................................................................. 1-9
Electrostatic discharge considerations ............................................................................................................................ 1-11
Laser safety guidelines ......................................................................................................................................................... 1-14
2 Initial system turn-up and service activation
Overview ...................................................................................................................................................................................... 2-1
...................................................................................................................................................................................................................................
363-211-555 iii
Issue 10, September 2008
Contents
Before you begin
Important notes .......................................................................................................................................................................... 2-3
Configuration considerations for the different AnyMedia ® shelf types ............................................................. 2-5
OAM&P Connectivity .......................................................................................................................................................... 2-13
Links to commonly used procedures ............................................................................................................................. 2-19
Initial system turn-up for configurations in controlled mode
Overview .................................................................................................................................................................................... 2-20
Flowchart of system turn-up with IPFM(s) ................................................................................................................. 2-21
Links to initial system turn-up procedures with IPFM(s) ..................................................................................... 2-23
Flowchart of system turn-up for ESIM used as controller in the LAG 200 Shelf ................................... 2-24
Links to initial system turn-up of the ESIM used as controller in the LAG 200 Shelf ......................... 2-26
Service activation
Overview .................................................................................................................................................................................... 2-27
Activate service for VoIP .................................................................................................................................................... 2-28
Activate service over ICAPs ............................................................................................................................................. 2-29
Activate VDSL service ........................................................................................................................................................ 2-34
Activate ADSL2 service ...................................................................................................................................................... 2-35
Activate Ethernet downlinks on ESIM ........................................................................................................................ 2-36
Initial system turn-up for configurations in stand-alone mode
Overview .................................................................................................................................................................................... 2-37
Flowchart of system turn-up for ICAP and VoIP APs in stand-alone mode ................................................. 2-38
Links to initial system turn-up procedures for ICAP and VoIP APs in stand-alone mode .................... 2-40
Flowchart of system turn-up for IPADSL APs in stand-alone mode .............................................................. 2-42
Links to initial system turn-up procedures for IPADSL APs in stand-alone mode .................................... 2-44
3 Support L2 and L3 functionality
Related procedures ................................................................................................................................................................... 3-1
4 Quality of service
Overview ...................................................................................................................................................................................... 4-1
...................................................................................................................................................................................................................................
iv 363-211-555
Contents
QoS provisioning recommendations ................................................................................................................................. 4-2
VoIP AP provisiong for QoS ................................................................................................................................................ 4-5
VLAN provisioning on VoIP APs ...................................................................................................................................... 4-7
TOS provisioning on VoIP APs .......................................................................................................................................... 4-8
Subscriber priority provisioning on VoIP APs ........................................................................................................... 4-10
5 Operations, administration and maintenance functions
6 Alarms and trouble clearing
Overview ...................................................................................................................................................................................... 6-1
Software alarms
Overview ...................................................................................................................................................................................... 6-5
IPFM software mismatch alarm ......................................................................................................................................... 6-6
IPFM/ESIM software mismatch between AP and IPFM/ESIM alarm ............................................................... 6-7
Software program corrupt alarm ........................................................................................................................................ 6-8
Generic system fault alarms
Overview ...................................................................................................................................................................................... 6-9
IPFM uplink failure alarm .................................................................................................................................................. 6-10
Slot-xx unequipped alarm ................................................................................................................................................... 6-11
Pack type mismatch alarm ................................................................................................................................................. 6-12
NTP Synchronization failed alarm .................................................................................................................................. 6-13
CPU utilization reaches its threshold alarm ................................................................................................................ 6-14
Specific ICAP alarms
Overview .................................................................................................................................................................................... 6-15
V5 faults – Overview ........................................................................................................................................................... 6-17
V5 interface failed alarm .................................................................................................................................................... 6-18
V5 data link failed alarm - Common Control ............................................................................................................ 6-19
V5 data link failed alarm - PSTN ................................................................................................................................... 6-20
...................................................................................................................................................................................................................................
363-211-555 v
Contents
V5 data link failed alarm - Protection ........................................................................................................................... 6-21
V5 data link failed alarm - Bearer Channel Control ............................................................................................... 6-22
V5 data link failed alarm - Link Control ..................................................................................................................... 6-23
V5 data link failed alarm - timeslot cessation of flags .......................................................................................... 6-24
V5 PSTN restart failed alarm ........................................................................................................................................... 6-25
V5 interface service degraded alarm .............................................................................................................................. 6-26
V5 interface identification failed alarm ........................................................................................................................ 6-27
V5 interface out of service alarm .................................................................................................................................... 6-28
V5 link failed alarm .............................................................................................................................................................. 6-29
V5 link identification failed alarm .................................................................................................................................. 6-30
V5 link disabled alarm ......................................................................................................................................................... 6-31
GR-303 faults – Overview ................................................................................................................................................. 6-32
GR-303 data link failed alarms - TMC/EOC ............................................................................................................. 6-33
GR-303 far end major or critical alarm ........................................................................................................................ 6-34
GR-303 far end minor alarm ............................................................................................................................................. 6-35
RT faults – Overview ........................................................................................................................................................... 6-36
RT link identification failed alarm .................................................................................................................................. 6-37
RT link interface identification failed alarm ............................................................................................................... 6-38
RT link layer 2 failed alarm .............................................................................................................................................. 6-39
RT link layer 3 failed alarm .............................................................................................................................................. 6-40
ROC provisioning mismatch detected alarm .............................................................................................................. 6-41
RT interface failed alarm .................................................................................................................................................... 6-42
RT interface service degraded alarm .............................................................................................................................. 6-43
RT interface control data link failed .............................................................................................................................. 6-44
ICAP specific sync faults – Overview .......................................................................................................................... 6-45
Synchronization input failed alarm ................................................................................................................................. 6-46
System free running synchronization failed alarm ................................................................................................... 6-47
ICAP specific system faults – Overview ...................................................................................................................... 6-48
Software program version mismatch alarm (ICAPs) .............................................................................................. 6-49

...................................................................................................................................................................................................................................
vi 363-211-555
Contents
Database corrupt alarm (ICAP) ........................................................................................................................................ 6-50
Database synchronization failed alarm (ICAP) ......................................................................................................... 6-51
Required pack missing alarm (ICAPs) .......................................................................................................................... 6-52
Required pack mismatch alarm ........................................................................................................................................ 6-53
Duplex cable misconfigured alarm ................................................................................................................................. 6-54
Media gateway controller not reachable alarm (ICAP) .......................................................................................... 6-55
E1 faults – Overview ............................................................................................................................................................ 6-56
AIS detected alarm ................................................................................................................................................................ 6-57
Incoming E1 signal FE degraded alarm ....................................................................................................................... 6-58
Incoming E1 signal near end degraded alarm ............................................................................................................ 6-59
Incoming E1 signal failed alarm ...................................................................................................................................... 6-60
Incoming E1 signal LOF alarm ........................................................................................................................................ 6-61
Incoming E1 signal LOS alarm ........................................................................................................................................ 6-62
Remote alarm indication received alarm ...................................................................................................................... 6-63
DS1 faults – Overview ........................................................................................................................................................ 6-64
AIS detected alarm ................................................................................................................................................................ 6-65
Incoming DS1 signal degraded alarm ........................................................................................................................... 6-66
Incoming DS1 signal failed alarm .................................................................................................................................. 6-67
Yellow alarm received .......................................................................................................................................................... 6-68
Incoming DS1 signal LOF alarm .................................................................................................................................... 6-69
Incoming DS1 signal LOS alarm .................................................................................................................................... 6-70
Specific VoIP AP alarms
Overview .................................................................................................................................................................................... 6-71
Tip/ring cable disconnect alarm ....................................................................................................................................... 6-72
Ringing source failed alarm ............................................................................................................................................... 6-73
MGC <IP address> connection failure alarm (VoIP AP) ....................................................................................... 6-74
VoIP port protection alarm (LPZ600) ............................................................................................................................ 6-75
1:N port protection failed (LPZ602) .............................................................................................................................. 6-76
VoIP CPU overload alarm .................................................................................................................................................. 6-77

...................................................................................................................................................................................................................................
363-211-555 vii
Contents
Trouble clearing procedures
Overview .................................................................................................................................................................................... 6-78
To clear “IPFM software mismatch” alarm ................................................................................................................ 6-80
To clear “software mismatch alarm between AP and controller flash” ........................................................... 6-82
To clear “Database corrupt” alarm (ICAP) ................................................................................................................. 6-85
To clear “Uplink failure” alarm ....................................................................................................................................... 6-87
To clear “Slot-xx unequipped” alarm ............................................................................................................................ 6-91
To clear “Pack type mismatch” alarm ........................................................................................................................... 6-93
To clear “NTP Synchronization failed” alarm ........................................................................................................... 6-95
To clear V5 protocol data link faults ............................................................................................................................. 6-96
To clear V5 interface fault alarm .................................................................................................................................... 6-99
To clear GR-303 data link fault alarms ...................................................................................................................... 6-101
To clear RT alarms caused by wrong cabling ......................................................................................................... 6-103
To clear “RT link interface identification failed” alarm ...................................................................................... 6-105
To clear “ROC provisioning mismatch detected” alarm ..................................................................................... 6-107
To clear “RT interface failed” alarm ........................................................................................................................... 6-109
To clear “RT interface service degraded” alarm ..................................................................................................... 6-110
To clear “RT interface control data link failed” alarm ......................................................................................... 6-111
To clear synchronization input failed alarm ............................................................................................................. 6-113
To clear “Software program version mismatch” alarm on ICAP .................................................................... 6-115
To reset IP pack .................................................................................................................................................................... 6-117
To clear “Required pack missing” alarm ................................................................................................................... 6-118
To clear “Required pack mismatch” alarm ............................................................................................................... 6-120
To clear incoming E1 signal fault alarms .................................................................................................................. 6-122
To clear DS1 input signal fault alarms ....................................................................................................................... 6-126
To clear “Tip/Ring cable (cable <x>) disconnect” alarm ................................................................................... 6-130
To clear “Ringing source failed” alarm ...................................................................................................................... 6-133
To clear “Media gateway controller not reachable” or Proxyhost alarm .................................................... 6-135
To clear VoIP port protection alarm ............................................................................................................................. 6-137

...................................................................................................................................................................................................................................
viii 363-211-555
Contents
7 Detailed procedure descriptions
Overview ...................................................................................................................................................................................... 7-1
Commonly used basic procedures
Overview ...................................................................................................................................................................................... 7-5
Installing the GSI ...................................................................................................................................................................... 7-6
Remove a Circuit Pack ....................................................................................................................................................... 7-11
System Access via GSI ...................................................................................................................................................... 7-14
Create/Edit or run a Script ................................................................................................................................................. 7-18
Procedures used for initial system turn-up
Overview .................................................................................................................................................................................... 7-22
AP Installation ......................................................................................................................................................................... 7-24
Change password .................................................................................................................................................................. 7-26
Change password on ICAP ................................................................................................................................................ 7-28
Configure or retrieve stand-alone mode for ICAP or VoIP AP via terminal ................................................. 7-31
Configure stand-alone mode for ICAP or VoIP APs via IP controller and GSI .......................................... 7-36
Configure stand-alone/controlled mode via GSI ....................................................................................................... 7-38
ESIM Installation in a LAG 200 Shelf (controller mode) .................................................................................. 7-39
Insert a pack ........................................................................................................................................................................... 7-41
IPFM Installation .................................................................................................................................................................... 7-44
Provision duplex IPFM mode (optional) ...................................................................................................................... 7-46
Provision IP AP slots ............................................................................................................................................................ 7-48
Provision link aggregation (optional) ........................................................................................................................... 7-49
Provision the IPFM uplink transmission parameters ............................................................................................... 7-52
Provision spanning tree protocol group (optional) ................................................................................................. 7-54
Provision uplink transmission parameters on the ESIM used as controller in the LAG 200 Shelf .. 7-57
Set inband management channel (optional) ............................................................................................................... 7-59
Set/Retrieve Date and Time ............................................................................................................................................. 7-61
Set/Retrieve Date and Time for APs in stand-alone mode ................................................................................... 7-64
Set/Retrieve IP address ....................................................................................................................................................... 7-66

...................................................................................................................................................................................................................................
363-211-555 ix
Contents
Set System Management IP address via serial port on IPADSL AP ................................................................ 7-68
Set up inband management channel for IPADSL in stand-alone mode (optional) .................................... 7-71
Verify/Update software load ............................................................................................................................................. 7-73
Wiring for ESIM used as controller ............................................................................................................................. 7-75
Wiring for IPFM ..................................................................................................................................................................... 7-78
Procedures used for VoIP service activation
Overview .................................................................................................................................................................................... 7-85
Provision port parameters on a VoIP AP ...................................................................................................................... 7-86
Provision VoIP AP parameters .......................................................................................................................................... 7-89
Provision/Retrieve SIP network protocol parameters ............................................................................................ 7-94
Provision/Retrieve H.248 network protocol parameters ...................................................................................... 7-100
Provision/Retrieve MGCP network protocol parameters .................................................................................... 7-103
Wiring for VoIP APs ........................................................................................................................................................... 7-106
Procedures used for ICAP service activation
Overview ................................................................................................................................................................................. 7-112
Provision ICAP parameters ............................................................................................................................................ 7-113
Provision/retrieve feeder parameters on an ICAP ................................................................................................ 7-118
Provision/retrieve ICAP profiles .................................................................................................................................. 7-125
Provision/retrieve network protocol parameters .................................................................................................... 7-130
Provision/retrieve H.248 port parameters on an ICAP ....................................................................................... 7-138
Provision/retrieve MGCP port parameters on an ICAP ..................................................................................... 7-143
Provision/retrieve SIP port parameters on an ICAP ............................................................................................ 7-148
Provision duplex ICAPs in controlled mode or stand-alone mode (optional) ........................................... 7-155
Provision VLANs, IP addresses and Routing on ICAP ....................................................................................... 7-157
Provision parameters for V5.2 aggregation on an ICAP ................................................................................... 7-165
Wiring for ICAPs ................................................................................................................................................................. 7-174
Procedures used for VDSL service activation
Overview ................................................................................................................................................................................. 7-184
Provision port parameters on a VSIM AP ............................................................................................................... 7-185

...................................................................................................................................................................................................................................
x 363-211-555
Contents
Provision/Retrieve VSIM PM profile .......................................................................................................................... 7-188
Provision/Retrieve VSIM transmission profile ........................................................................................................ 7-191
Retrieve VSIM transmission status .............................................................................................................................. 7-195
Wiring for VDSL APs ....................................................................................................................................................... 7-196
Procedures used for activating Ethernet downlinks on ESIM
Overview ................................................................................................................................................................................. 7-199
Provision port parameters on ESIM ........................................................................................................................... 7-200
Wiring for ESIMs used as APs ...................................................................................................................................... 7-202
Procedures used for ADSL2 service activation
Overview ................................................................................................................................................................................. 7-206
Provision/Edit/Delete DMT Profile ............................................................................................................................ 7-207
Provision port parameters on an IPADSL2 AP ...................................................................................................... 7-211
Provision/Retrieve bridge port PM profile .............................................................................................................. 7-214
Provision/Retrieve bridge port traffic profile ........................................................................................................... 7-217
Provision/Retrieve IPADSL transmission profile ................................................................................................... 7-220
Provision/Retrieve IPADSL PM profile ..................................................................................................................... 7-225
Provision/Retrieve IPADSL bridge port profile ...................................................................................................... 7-228
Wiring for IPADSL2_32p APs ..................................................................................................................................... 7-232
Procedures used for support of L2 and L3 functionality
Overview ................................................................................................................................................................................. 7-238
Create/modify a VLAN ................................................................................................................................................... 7-239
Provision/Delete addresses in DHCP relay ............................................................................................................. 7-247
Provision/Delete MAC address learning .................................................................................................................. 7-248
Provision/Delete static route ........................................................................................................................................... 7-251
Provision/Disable broadcast storm control .............................................................................................................. 7-252
Provision/Disable IGMP snooping .............................................................................................................................. 7-254
Trace route .............................................................................................................................................................................. 7-257
Procedures used for QoS support
Overview ................................................................................................................................................................................. 7-258

...................................................................................................................................................................................................................................
363-211-555 xi
Contents
Provision/Modify L2/L3 group priorities for QoS ................................................................................................. 7-259
Provision/Modify L4 group priorities for QoS ........................................................................................................ 7-262
Provision/Modify classifiers on VSIM APs .............................................................................................................. 7-265
Provision/Modify packet type priorities for QoS ................................................................................................... 7-269
Provision/Modify policies on VSIM APs .................................................................................................................. 7-272
Provision/Modify policy attributes on VSIM APs ................................................................................................. 7-274
Provision/Modify policy instances on VSIM APs ................................................................................................. 7-277
Provision the IPFM/ESIM for QoS ............................................................................................................................ 7-279
Provision VSIM APs for QoS ....................................................................................................................................... 7-287
Procedures used for operations, administration and maintenance functions
Overview ................................................................................................................................................................................. 7-292
Activate VoIP AP 1:N port protection ......................................................................................................................... 7-294
AP Software download and activation in controlled mode ................................................................................ 7-297
Activate system log facility ............................................................................................................................................. 7-304
Database backup ................................................................................................................................................................... 7-306
Database restore .................................................................................................................................................................. 7-308
Deactivate VoIP AP 1:N port protection .................................................................................................................... 7-310
Delete an IP application pack ......................................................................................................................................... 7-312
Force IPFM side switch .................................................................................................................................................... 7-313
ICAP Media monitoring .................................................................................................................................................... 7-315
IP AP Growth ........................................................................................................................................................................ 7-317
IP AP Degrowth ................................................................................................................................................................... 7-318
ICAP Migration from duplex to simplex mode ...................................................................................................... 7-321
IPFM Migration from duplex to simplex mode ...................................................................................................... 7-323
Provision/Delete trap receiving ...................................................................................................................................... 7-325
Provision/deprovision CPU utilization alarm ........................................................................................................... 7-326
Retrieve active alarms ........................................................................................................................................................ 7-327
Retrieve IP Equipment ....................................................................................................................................................... 7-328
Retrieve RMON statistics ................................................................................................................................................. 7-330

...................................................................................................................................................................................................................................
xii 363-211-555
Contents
Retrieve call statistics on ICAP ..................................................................................................................................... 7-332
IPFM/ESIM Software download and activation ..................................................................................................... 7-335
Software download/activation and database backup/restore for stand-alone AP(s) ................................. 7-340
System initialization ........................................................................................................................................................... 7-347
VoIP Voice stream monitoring ........................................................................................................................................ 7-350
8 Configuration Examples
Remote Management solutions for ICAP and RT-ROC (COMDAC)
Overview ...................................................................................................................................................................................... 8-1
A Product conformance
Overview ..................................................................................................................................................................................... A-1
European conformity (CE) statements ............................................................................................................................ A-2
Additional international conformity statements .......................................................................................................... A-5
Eco-environmental statements ............................................................................................................................................ A-6
Glossary
Index
...................................................................................................................................................................................................................................
363-211-555 xiii
Purpose
These Commands and Procedures for IP-based Services apply to the international
version and to the NAR version of the AnyMedia ® Access System. It enhances the
traditional Commands and Procedures with information about IP-based services.
Note that not all features described here, are supported by both system versions.
The Commands and Procedures for the international version of the AnyMedia ® Access
System consist of three parts which are closely related to each other. They are not
considered to be independent information products. For the titles of the three C&Ps,
see table below:
C&P titles for international regions CIC Ordering

Number
Commands and Procedures for Narrowband Services with TDM COMDAC 363-211-119
Commands and Procedures for ATM xDSL services 363-211-133
Commands and Procedures for IP-based services 363-211-555
The Commands and Procedures for the NAR version of the AnyMedia ® Access System
consists of two parts which are closely related to each other. They are not considered
to be independent information products. The conventional Commands and Procedures
(363-211-100) has now been enhanced with a second part, “Commands and Procedures
for IP-based services”.. For the titles of the two C&Ps, see table below:
C&P titles for North America regions (NAR) CIC Ordering

Number
Commands and Procedures 363-211-100
Commands and Procedures for IP-based services 363-211-555
The Commands and Procedures part for IP-based services focuses totally on the
IP-based services in the AnyMedia ® Access System. The following information is
provided in this information product:
• Initial system turn-up and service activation
• Support L2 and L3 functionality
...................................................................................................................................................................................................................................
363-211-555 xv
,
• Quality of service
• Operations, administration and maintenance functions.
• Alarms and maintenance
• Detailed procedure descriptions
Reason for reissue

This is the first issue of this document. Information that is added, deleted, or changed
in future releases will be summarized in this notice.
History
Issue Date Future
8 July 07 • Improve description alarms and trouble clearing, see chapter 6:

– Make additions and modifications related to ICAP (aggregation)
and LPZ602 alarm messages
– New trouble clearing procedures
• New “enable” password configuration on the ICAP (two level password
feature).
• Provisioning change of initial default for OAM access on IPFM, via any
provisioned L3 VLAN.
7 March 07 • Multiple IP addresses on ICAP and VLAN provisioning

• V5 Aggregation on ICAP
• Call statistics and megaco message statistics
• Activate system log facility on ICAP and VoIP APs
• Provisionable Receive and Transmit Gain in ICAP
• Support multiple H.248 Backup Media Gateway Controllers
• Support of Direct Dial In for MGCP
• Support of ICAP faceplate Fast-Ethernet uplink in controlled mode
• Source IP Policy Routing
• PayPhone support
• Provisionable Metering Mode for R2 Interface
6 November 06 • LPA633 in LAG200
• Support of additional features on ICAP and VoIP APs:
– Media monitoring
– Voice activity detection per port
– Echo cancelation per port
– Loopbacks per feeder
• New VoIP AP LPZ602_64p (at the issue date of this document only
supported for NAR markets)
• ICAP in stand-alone mode
• LPZ600 in stand-alone mode (not yet supported at the issue date of this
document)
5 August 06 • New IP ADSL2+ 32 port AP, Annex A application pack IPADSL2_32p AP
LPA633 in controlled and stand-alone mode
...................................................................................................................................................................................................................................
xvi 363-211-555
,
4 April 06 • Support of new IP pack IP COMDAC AP (ICAP)

• Support of new IP packs IP-AFM
• Migrating existing AnyMedia® Access Systems towards IP networks by
aggregation of remote terminals via ICAPs
• Support of several IP APs in stand-alone mode
3 January 06 • Support of IPFMs with extended memory
• Support of LAG 200 Shelf (used in international regions)
• Support of LAG 2300 Shelf (used in NAR)
• Support of ESIM as controller in a LAG 200 Shelf
• Support of new IP packs (IP-AFM, ICAP, IPADSL2_32p AP)
2 June 05 • Support of VDSL service
• Quality of service
• IP loopbacks
• DHCP relay
• Manual call restriction control
• Improved software download capabilities for VoIP
1 February 05 first edition
Safety information
This information product contains hazard statements for your safety. Hazard statements
are given at points where safety consequences to personnel, equipment, and operation
may exist. Failure to follow these statements may result in serious consequences.
Intended audience
The intended audience of this Commands and Procedures for IP-based Services
primarily consists of people who are responsible for the turn-up, and maintenance of
network elements and for the supervision of transmission operation.
Conventions used
The following conventions are used throughout the Commands and Procedures for
IP-based Services.
Acronyms and abbreviations
In the text acronyms are expanded the first time they are used in the main text of a
chapter (for example Fast Ethernet (FE)). If the acronym is a trademark, it will not be
spelled out. A list of acronyms is provided at the end of this document.
...................................................................................................................................................................................................................................
363-211-555 xvii
,
Terms used (alphabetically ordered)

The following are terms used in this information product (IP) that may have a different
meaning than the general or common use of the term.
• a/b-cable refer generically to the tip/ring pair cables that attach to the faceplate of
application packs (APs).
• In the AnyMedia ® Access System, the term access means that the system provides
the primary service interface for the subscriber to enter the network.
• The term AnyMedia LAG Shelf is generally used for an AnyMedia shelf with IP
spokes on the backplane, independently of the physical design of the shelf.
In contrast to an AnyMedia ® ETSI V5 Shelf or FAST Shelf the AnyMedia LAG
Shelves are capable to support IP-based services also in controlled mode.
• The term AnyMedia shelves is used whenever the text does not need to distinguish
between the shelf types. It is mostly used where services and service packs are
described.
• The term controlled mode is generally used for a mode, in which the inter-worked
traffic is handled by IP spokes on the shelf backplane which connect the pack to
the IP controller. Therefore this mode requires the usage of a LAG Shelf equipped
with an IP controller. The uplinks on the faceplates of the APs are not usable in
this mode.
Note that the IPFM controlled mode is supported in the LAG Shelves only.
• The term stand-alone mode is generally used for a mode, in which the inter-worked
traffic is handled by the uplinks on the faceplate of the individual AP without using
neither IP spokes on the backplane nor an IP controller. This mode is supported in
all shelf types, but it is not supported by each IP AP type.
A combination of APs in stand-alone mode and of APs in controlled mode is also
allowed within one shelf. But note that every stand-alone pack is a separate NE
from the management perspective, that means it reduces the NAM capacity in
terms of managed shelves correspondingly.
• The term IP controller is a general term for an IP forwarding module (IPFM) or an
ESIM that is used not as an AP but as an IP controller in a LAG 200 Shelf.
Trademarks
Trademarks of Alcatel-Lucent and other companies are in italics. They are identified
with the registered mark ( ®) or trademark (™) symbol the first time the trademarks are
used in the text (for example Alcatel-Lucent AnyMedia ® Access System).
Related documentation for the international regions

The following is orderable documentation related to the AnyMedia ® Access System
and for additional components, especially for international regions. For the ordering
address see “How to order” (p. xx). Additionally, these information products are
accessible from the Alcatel-Lucent’ internal web page:
http://access.de.lucent.com/ACCESS/cdoc/index.html
...................................................................................................................................................................................................................................
xviii 363-211-555
,
Manual Type Comcode CIC Ordering

Number (1)
Applications and Planning Guide (APOG), Overview 109 562 744 363-211-585
Applications and Planning Guide (APOG), Narrowband and 109 562 751 363-211-586
ATM xDSL services
Applications and Planning Guide (APOG), IP-based services 109 562 769 363-211-587
Data Sheet Book 109 218 651 363-211-251
Ordering Guide 109 097 782 363-211-144
Commands and Procedures for Narrowband Services with 109 105 635 363-211-119
TDM COMDAC
Commands and Procedures for ATM xDSL Services 109 024 737 363-211-133
Commands and Procedures for IP-based Services 109 562 736 363-211-555
Installation Manual for DC-Powered Racks for ETSI V5 and 109 576 140 363-211-603 (2)
LAG 1900 Shelves
Installation Manual for the Mainshelf and DC-powered racks 109 024 752 363-211-207 ( 3)
Installation Manual for AC-powered racks 109 024 745 363-211-206
ONU Installation Manual for Indoor Applications 108 626 367 363-211-150
AnyMedia ® LAG 4300 System, Installation Manual (IM) 109 461 939 363-211-256
Customer Documentation on CD-ROM 108 298 787 363-211-114
Notes:
1. For the ordering address see “How to order” (p. xx).
2. Applicable for the new DC-powered racks based on CABI600 mechanics (J1C293B-1 L1 and
J1C301B-1 L1)
3. Applicable for the established DC-powered racks J1C283B-1 L2 and J1C293A-1 L2.
Print copy (hard copy)

All listed documents are available in print and on CD-ROM.
Related documentation for the North America regions

The following is orderable documentation related to the AnyMedia ® Access System
and for additional components, especially for NAR. For the ordering address see “How
to order” (p. xx). Additionally, these information products are accessible from the
Alcatel-Lucent’ internal web page:
http://access.de.lucent.com/ACCESS/cdoc/index.html
Manual Type Comcode CIC Ordering Number (1)

Applications and Planning Guide (APOG) 108 298 639 363-211-101
...................................................................................................................................................................................................................................
363-211-555 xix
,
Manual Type Comcode CIC Ordering Number (1)

Applications and Planning Guide (APOG), IP-based 109 562 769 363-211-587
services
AnyMedia ® Access System Feature Supplement, N/A 363-211-127
Integrated Access Terminal (IAT)
AnyMedia ® Access System Feature Supplement, 108 864 521 363-211-106
MDS2 Shelf Configuration
AnyMedia ® Access System Feature Supplement, N/A 363-211-128
Central Office Terminal
Ordering Guide N/A 363-211-125
2
Commands and Procedures ( ) N/A 363-211-100
Commands and Procedures for IP-based Services 109 562 736 363-211-555
Installation Manual 108 298 654 363-211-102
Engineering Guidelines N/A 363-211-178
Data Sheet Book N/A 363-211-254
AnyMedia ® Access System Floor Plan Data Sheets N/A FPD 801-450-111-1
Customer Documentation on CD-ROM 108 361 155 363-211-104
Notes:
1. For the ordering address see “How to order” (p. xx).
2. Available on CD-ROM only.
Print copy (hard copy)

If nor market otherwise, all listed documents are available in print and on CD-ROM.
How to order
These documents and drawings can be ordered at or downloaded from the
Alcatel-Lucent Online Customer Support Site (OLCS) (https://support.lucent.com) or
through your Local Customer Support.
How to comment
To comment on this information product, go to the Online Comment Form
(http://www.lucent-info.com/comments/enus/) or e-mail your comments to the
Comments Hotline ([email protected]).
Because customer satisfaction is extremely important to Alcatel-Lucent, every attempt
is made to encourage feedback from customers about our information products.
...................................................................................................................................................................................................................................
xx 363-211-555
,
1 S afety
1
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter contains safety instructions, shows the appearance of safety instructions
and provides information on electrostatic discharge.
Contents
Structure of hazard statements 1-2

General safety information 1-4
Appearance of the safety instructions 1-7
Relevant safety instructions 1-9
Electrostatic discharge considerations 1-11
Laser safety guidelines 1-14
...................................................................................................................................................................................................................................
363-211-555 1-1
Safety
Structure of hazard statements

...................................................................................................................................................................................................................................
Overview
Hazard statements describe the safety risks relevant while performing tasks on
Alcatel-Lucent products during deployment and/or use. Failure to avoid the hazards
may have serious consequences.
General structure
Hazard statements include the following structural elements:
Item Structure element Purpose

1 Personal-injury symbol Indicates the potential for personal injury
(optional)
2 Hazard-type symbol Indicates hazard type (optional)
3 Signal word Indicates the severity of the hazard
4 Hazard type Describes the source of the risk of damage or
injury
5 Damage statement Consequences if protective measures fail
6 Avoidance message Protective measures to take to avoid the hazard
7 Identifier The reference ID of the hazard statement
(optional)
...................................................................................................................................................................................................................................
1-2 363-211-555
Safety Structure of hazard statements
Signal words
The signal words identify the hazard severity levels as follows:
Signal word Meaning

DANGER Indicates an imminently hazardous situation (high risk) which, if
not avoided, will result in death or serious injury.
WARNING Indicates a potentially hazardous situation (medium risk) which,
if not avoided, could result in death or serious injury.
CAUTION When used with the personal injury symbol:
Indicates a potentially hazardous situation (low risk) which, if
not avoided, may result in personal injury.
When used without the personal injury symbol:
Indicates a potentially hazardous situation (low risk) which, if
not avoided, may result in property damage, such as service
interruption or damage to equipment or other materials.
...................................................................................................................................................................................................................................
363-211-555 1-3
Safety
General safety information

...................................................................................................................................................................................................................................
Overview
This section lists the safety information needed for the AnyMedia ® Access System for
system turn-up after installation has been completed, operating, provisioning and
maintaining the system.
Make sure that you read this section carefully and that you understand all the safety
information in this section. The safety information in this section includes:
• Important general safety instructions
• Appearance and classification of safety instructions
• Understanding electrostatic discharge (ESD) and avoiding damage from ESD
• Lightwave safety
• Special safety instructions for handling batteries.
NOTE: If you do not understand any of the safety information in this section, please
see your manager immediately. You should also talk with your manager if you feel you
do not understand any procedures in this manual, or if you feel you need additional
training before performing any of these procedures.
Not only the general instructions in this chapter on safety must be observed, but also
the specific safety instructions in the individual chapters.
Only trained service personnel should perform the procedures in this document. These
procedures allow exposure to high electrical energy and/or current that may result in
electric shock and/or injury to untrained personnel during servicing, maintenance, and
installation of this system.
All safety instructions have a uniform appearance. This appearance is described in
detail in “Appearance of the safety instructions” (p. 1-7).
NOTE: The AnyMedia ® Access System must be supplied with Safety Extra-Low
Voltage (SELV) of –48 V and the positive terminal of this source must be correctly
connected to the protective earth. Never connect to supply voltage of –60 V, which will
destroy the equipment.
General notes on safety

This system has been developed in line with the present state-of-the-art and fulfils the
current national and international safety requirements. It is provided with a high degree
of operational safety resulting from many years of development experience and
continuous stringent quality checks in our company.
...................................................................................................................................................................................................................................
1-4 363-211-555
Safety General safety information
The system is safe in normal operation. There are, however, some potential sources of
danger that cannot be completely eliminated. In particular, these arise during the
• Opening of housings or equipment covers
• Manipulation of any kind within the equipment, even if it has been disconnected
from the power supply
• Disconnection of optical or electrical connections
through possible contact with
• Live parts
• Laser light
• Hot surfaces
• Sharp edges, or
• Devices sensitive to electrostatic discharge.
General safety requirements

In order to keep the technically unavoidable residual risk to a minimum, it is
imperative to observe the following rules:
• Installation, configuration and disassembly must be carried out only by expert
personnel and with reference to the respective documentation.
Due to the complexity of the unit/system, the personnel requires special training.
• The unit/system must be operated by expert and authorized users only.
The user must operate the unit/system only after having read and understood the
chapter on safety and the parts of the documentation relevant to operation. For
complex systems, additional training is recommended. Any obligatory training for
operating and service personnel must be carried out and documented.
• Any conversions or changes to the system or parts of the system (including the
software) must be carried out by qualified Alcatel-Lucent personnel or by expert
personnel authorized by Alcatel-Lucent.
All changes carried out by other persons lead to a complete exemption from
liability.
No components/spare parts must be used other than those recommended by the
manufacturer and those listed in the procurement documents.
• The unit/system must not be operated unless it is in perfect working order.
Any faults and errors that might affect safety must be reported immediately by the
user to a person in responsibility.
• The equipment must be supplied with Safety Extra-Low Voltage (SELV) of -48 V
and the positive terminal of this source must be correctly connected to the
protective earth.
Never connect to –60 V.
• The unit/system must be operated only with the connections and under the
environmental conditions as described in the documentation.
...................................................................................................................................................................................................................................
363-211-555 1-5
Safety General safety information
• The removal or disabling of safety facilities, the clearing of faults and errors, and
the maintenance of the equipment must be carried out by specially qualified
personnel only.
The respective parts of the documentation must be strictly observed.
The documentation must also be consulted during the selection of measuring and
test equipment.
• Transport, storage and operation of the unit/system must be under the permissible
conditions only.
See accompanying documentation and information on the unit/system.
• Calibrations, special tests after repairs and regular safety checks must be carried
out, documented and archived.
• Only use tested and virus-free diskettes.
• Do not place the shelves on an unstable cart, stand, or table.
The product may fall causing serious damage to the equipment.
• Never push objects of any kind into this product through cabinet slots as they may
touch dangerous voltage points or short out parts that could result in a risk of fire
or electrical shock. Never spill liquid of any kind on the product.
...................................................................................................................................................................................................................................
1-6 363-211-555
Safety
Appearance of the safety instructions

...................................................................................................................................................................................................................................
Overview
All safety instructions have a uniform appearance. They include a signal word that
classifies the danger and a text block that contains descriptions of the type and cause
of the danger, the consequences of ignoring the safety instruction and the measures that
can be taken to minimize the danger. In some safety instructions, a warning symbol is
placed underneath the signal word.
Example:
DANGER
Arcing on removing or inserting a live power supply plug.
Arcing can cause serious burns to the hands and damage to the eyes.
Ensure that the line circuit-breaker on the fuse panel is in the “OFF” position before
removing or inserting the power supply plug
Warning symbols
The following warning symbols are used:
Symbol Common application

General warning about a danger
Warning about a dangerous electrical voltage
Warning about laser radiation
Warning about explosion
Warning about battery acid
Warning about devices sensitive to electrostatic dis-

charge (ESD)
...................................................................................................................................................................................................................................
363-211-555 1-7
Safety Appearance of the safety instructions
The safety instructions for the classes “Danger”, “Warning” and “Caution” always have
a warning symbol, the “Important” and “Notice” safety instructions can, but do not
always have a warning symbol.
This document may contain safety labels such as WARNING, CAUTION,
IMPORTANT, and NOTICE.
Special safety instructions

The aspects of “handling of components sensitive to electrostatic discharge (ESD)” and
“laser safety” are of vital importance for equipment in the AnyMedia ® Access System.
The key safety instructions for these subjects are summarized in “Electrostatic
discharge considerations” (p. 1-11).
...................................................................................................................................................................................................................................
1-8 363-211-555
Safety
Relevant safety instructions

...................................................................................................................................................................................................................................
WARNING: Risk of injury due to untrained personnel

Only trained service personnel should perform the procedures in this document.
These procedures allow exposure to high electrical energy and/ or current that
may result in electric shock and/or injury to untrained personnel during servicing,
maintenance, and installation of this system. Do not allow non-service person-
nel to access electrical wiring.
Read and understand all instructions and warning labels.
Follow all warnings and instructions marked on the product and in the manu-
als.
DANGER: Injury to eyes caused by invisible laser radiation.

AnyMedia Access System systems operate with invisible laser radiation. Laser
radiation can cause considerable injuries to the eyes.
Never look into the end of an exposed fibre or pack optical connectors as long as
the optical source is switched on. This applies particularly to the connections of
the optical packs of the WaveStar ADM 4/1, to the OAP in the AnyMedia Main-
shelf, to the OCP in the ONU Subshelf and to the optical link between them.
Always observe the laser warning instructions.
DANGER: Arcing on removing or inserting a live power supply plug or the power
filter unit (PFU).
Arcing can cause burns to the hands and damage to the eyes.
Ensure that the DC circuit-breaker on the fuse panel is in the "OFF" position be-
fore removing or inserting the power supply plug or power filter unit.
CAUTION: Risk of injury, if only one −48 V DC power feeder is disconnected.

The AnyMedia shelf maybe equipped with two −48 V DC input power feeders.
Disconnecting one power feeder will not de-energize the AnyMedia shelf.
Disconnect both power supply cables when removing power from the AnyMedia
shelf.
IMPORTANT: Destruction of packs in the event of a short-circuit.

A short-circuit in the AnyMedia Access System can cause destruction of elec-
tronic components and thus malfunctioning of the complete system.
You must therefore not handle objects such as a screwdriver in the pack area.
Never push objects of any kind into this product through slots as they may touch
dangerous voltage points or cause a short-circuit.
...................................................................................................................................................................................................................................
363-211-555 1-9
Safety Relevant safety instructions
IMPORTANT: Destruction of components by incorrect handling.

Before replacing a pack, check the identification code to ensure that the proper
pack is being used.
CAUTION: Destruction of LEDs by improper handling of packs

Take care to avoid damaging the LED(s) that protrude through the openings in the
faceplate of the packs during handling and pack installation.
When installing a pack, place your thumbs on the rounded indentations of the
latch to lock the pack in position. Do not use your palm because your hand may
slip and break LEDs that protrude through the openings of the faceplate
...................................................................................................................................................................................................................................
1-10 363-211-555
Safety
Electrostatic discharge considerations

...................................................................................................................................................................................................................................
General notes on ESD

Electrostatic discharge (ESD), for example caused by touching with the hand, can
destroy semiconductor components. The correct operation of the complete system is
then no longer assured.
All semiconductor components are basically sensitive to electrostatic discharge (ESD).
The electrostatic discharge can also affect the components indirectly via contacts or
conductor tracks.
Plug-in units containing components that are especially sensitive to electrostatic
discharge are identified by warning labels bearing the barred-hand symbol.
Warning symbol:
CAUTION
ESD hazard
Warning about devices sensitive to electrostatic discharge (ESD).
Electronic components can be destroyed by electrostatic discharge.
To avoid electrostatic discharge conductively connected wrist straps connect to the
cabinet ESP bonding point should be used.
The safety instructions for the classes “Danger”, “Warning” and “Caution” always have
a warning symbol, the “Important” and “Notice” safety instructions can, but do not
always have a warning symbol.
This document may contain safety labels such as WARNING, CAUTION,
IMPORTANT, and NOTICE.
Important! Destruction of components by electrostatic discharge.
Electronic components can be destroyed by electrostatic discharge. An electrostatic
discharge wrist strap, with a resistance between 250 kΩ and 1.5 MΩ, should be
worn when handling AnyMedia ® Access System plug-ins to prevent possible
damage to the plug-ins. Before using the wrist strap, check the wrist strap for
shorts, opens, and proper resistance value. Do not use a wrist strap that does not
pass these checks.
Hold plug-in units only at the edges or on the insertion and removal facilities.
Always observe the ESD instructions.
...................................................................................................................................................................................................................................
363-211-555 1-11
Safety Electrostatic discharge considerations
Precautions
The following list of precautions should be observed when handling circuit packs to
prevent damage by electrostatic discharge (ESD):
• Assume all circuit packs contain solid state electronic components that can be
damaged by ESD.
• Work in an area which is protected against electrostatic discharge. Use conducting
floor and bench mats which are conductively connected to the rack ESD bonding
point.
• Wear conductively connected wrist straps and connect them to the rack ESD
bonding point.
• Handle all circuit packs by the faceplate or latch and by the top and bottom
outermost edges. Never touch the components, conductors, or connector pins.
• Observe warning labels on bags and cartons. Whenever possible, do not remove
circuit packs from antistatic packaging until ready to insert them into slots.
• If possible, open all circuit packs at a static-safe work position, using properly
grounded wrist straps and static-dissipating table mats. If a static-dissipating table
mat is used, be sure that it is clean to ensure a good discharge path.
• Always store and transport circuit packs in static-safe packaging. Shielding is not
required unless specified.
• Ensure that the rack is grounded.
• Keep all static-generating materials such as food wrappers, plastics, and foam
packaging away from all circuit packs. On removal from the shelf, immediately put
circuit packs into static-safe packages.
• Whenever possible, maintain relative humidity above 20 percent.
ESD wrist strap

To reduce the possibility of ESD damage, the shelves and the racks are equipped with
a grounding jack to enable personnel to ground themselves using wrist straps with a
minimum resistance of 250 kΩ while handling circuit packs or working on a
shelf/shelves. The jacks are located on the left and right of the rack and are accessible
from the front. When grounding jacks are not provided, an alligator clip adapter
enables connection to rack’s frame ground (FRMGND).
...................................................................................................................................................................................................................................
1-12 363-211-555
Safety Electrostatic discharge considerations
To
Ground
Connection
e12:/7W-21610.dia/fig_20.cdr
Conductively connect all test equipment and trolleys to the rack ESD bonding point.
...................................................................................................................................................................................................................................
363-211-555 1-13
Safety
Laser safety guidelines

...................................................................................................................................................................................................................................
Laser safety
In its normal operating mode, a lightwave system is totally enclosed and presents no
risk of eye injury. It is a Laser Class 1/I product under the IEC schemes.
The Lightguide cables that interconnect various components of a lightwave system can
be disconnected or break, and may expose people to lightwave emission. Also, certain
measures and service procedures may expose the technician to emission from the laser
circuit pack during installation and servicing.
Observe the following instructions to avoid exposing yourself and others to risk:
• Don’t look into the end of an exposed fiber or an open connector as long as the
optical source is still switched on. Even for Class 1 lasers viewing with the unaided
eye at distances greater than 250 mm (≈10 inches) will normally not cause eye
injury.
• Under no circumstances lightwave/lightguide operations shall be performed by a
technician before satisfactorily completing an approved training course. Only
authorized, trained personnel shall be permitted to carry out service, maintenance
and restoration activities.
• Read the relevant descriptions in the manuals before taking equipment into
operation or carrying out any installation and maintenance work on the optical
packs, and follow the instructions. Ignoring the instructions can result in exposure
to dangerous radiation.
• If you are not sure that the fiber is connected to a Laser Class I product ensure that
the optical source is switched off before disconnecting optical fiber connectors.
• Under no circumstances shall any personnel scan a fiber with an optical test set
without verifying that all lightwave sources on the fiber are turned off or that the
test set is specially approved for this test.
• In the event of doubt, check that the optical source is switched off by measuring
with an optical power meter.
Warning symbol:
CAUTION
Components with lasers and fibers
Although, at present, the transmitting power levels for Laser Class 1 are below those
known to cause injury to the eye at distances greater than 250 mm ( ~10 inches) direct
exposure should always be avoided.
Always observe the laser warning instructions (see instructions below)
...................................................................................................................................................................................................................................
1-14 363-211-555
Safety Laser safety guidelines
Classification of lasers
The laser classes are defined in standards such as EC 60825 (or EN 60825) and its
supplements. A maximum laser radiation is defined for each laser class according to
the wavelength. The maximum laser radiation depends on the type of laser diode used.
This results in different laser classes for the various optical plug-in units.
These standards require manufacturers to classify their laser products as belonging to
one of the major classes, classes 1, 2, 3A, and 3B. Manufacturers of lasers and laser
products in the U.S. are regulated by the Food and Drug Administration’s Center for
Devices and Radiological Health FDA/CDRH) under 21 CFR 1040. Classification
schemes are similar to the IEC with categories such as class I, II, lla, IlIa or lllb. In
both cases, laser products are classified according to the accessible emission levels and
their potential for causing injury.
Laser classes to IEC 60825 and DIN/EN 60825
Laser class Wavelength Max. laser radiation

Class 1 1300 nm 8.85 mW
Class 1 1550 nm 10 mW
Class 3A 1300 nm 31 mW
Class 3A 1550 nm 50 mW
Class k x 3A 1300 nm 81 mW
Class k x 3A 1550 nm 50 mW
Class 3B 1300 nm 0.5 mW
Class 3B 1550 nm 0.5 mW
Optical transmission systems are identified by yellow laser warning labels on which
only the laser class (see the labels below ) is indicated.
Lightwave systems are generally classified as class 1/I, because, under normal
operating conditions, all energized laser transmitting circuit packs are terminated on
optical fibers which enclose the laser energy with the fiber sheath forming a protective
housing. Also, covers are typically in place over the circuit pack shelves.
The label shown below is used to identify systems belonging to laser class 1 in normal
operation.
Laser warning labels for Class 1 lasers
LASER PRODUCT
CLASS 1
...................................................................................................................................................................................................................................
363-211-555 1-15
CLASS 1
LASER PRODUCT
Appropriate labels are also available for the remaining laser classes (k x 3A, 3B); each
label indicates the laser class, wavelength and maximum laser radiation. These labels
are affixed in a clearly visible position on the equipment.
The following laser warning symbols can be affixed to the optical packs. The optical
connectors from which laser radiation can be emitted can be identified by a laser
warning symbol near the connector:
Due to lack of space, laser warning labels cannot be affixed to the potential source of
laser radiation, that is, directly to the optical connectors.
Handling fibers
Never look into the end of an exposed fiber or optical connector of a pack as long as
the optical source is switched on. Always observe the laser warning instructions.
Splicing
Cutting and splicing fibers must be followed and performed by trained personnel only.
Read and understand all instructions of the manual of the splicing and cutting
equipment.
After cutting/splicing, every splice has to be checked. Follow the instructions of the
manual of the splicing and cutting equipment.
Routing and connecting

During installation of fibers the optical connectors of fibers must be equipped with a
protective cap until the connectors are coupled.
The fibers should by guided to the optical packs using the special protective spiral
wrap of the pigtail.
If the fiber is routed from bottom to an optical connector take care if the fiber has to
be disconnected so that the fiber will not hang out of the ONU Subshelf and can be
bent or broken.
...................................................................................................................................................................................................................................
1-16 363-211-555
Optical cable break

There is a risk to cause micro defects in the fiber or a risk of a cable break if the
bending radius of optical fiber cables is less than about 30 mm. Microdefects can
increase the fiber attenuation and reduce the long term stability. Ensure that the
bending radius is not less than 30 mm.
Cleaning optical connectors and couplings

Cleaning optical connectors is required only if problems have occurred which indicate
that these connectors have an impurity (for example deviation of attenuation values
beyond the permitted maximum).
Checking fiber connectors

Before starting to clean the optical connectors, ensure that the optical source is
switched off. Never look into the end of an exposed fiber or optical connector of a
pack as long as the optical source is switched on. Always observe the laser warning
instructions.
To check for impurities (for example fluff, dust particles, ...), use a microscope with an
enlargement factor of 40, so that the connector face can be inspected.
Checking optical couplers

Visually check the coupling for residual impurities by holding it to the light (the
geometry of the coupling does not allow the coupling to be checked under the
microscope). After cleaning with a pipe cleaner do not connect the optical
connectors/couplings without checking them for impurities.
Use isopropanol for cleaning. Let the connector/coupling face air-dry or use purified
compressed air (the isopropanol must evaporate completely!).
...................................................................................................................................................................................................................................
363-211-555 1-17
2 I2nitial system turn-up and
service activation
Overview
...................................................................................................................................................................................................................................
Purpose
Firstly, this chapter provides general information about the system. That includes:
• Important general notes about the system
• Configuration considerations for the different AnyMedia shelf types
• Information about OAM&P connectivity.
Then this chapter provides information about procedures for system turn-up and service
activation.
The procedures that have to be performed for initial system turn-up, depend on the
configuration mode of the IP subsystem (controlled or stand-alone) and on the
controller type (IPFM or ESIM in LAG 200 Shelf). You will find for each of these
turn-up types a flowchart followed by a set of links that points to the applicable
detailed procedure descriptions in the correct sequence.
Contents
Before you begin 2-3

Important notes 2-3
Configuration considerations for the different AnyMedia ® shelf types 2-5
OAM&P Connectivity 2-13
Links to commonly used procedures 2-19
Initial system turn-up for configurations in controlled mode 2-20
Flowchart of system turn-up with IPFM(s) 2-21
Links to initial system turn-up procedures with IPFM(s) 2-23
Flowchart of system turn-up for ESIM used as controller in the 2-24
LAG 200 Shelf
Links to initial system turn-up of the ESIM used as controller in the 2-26
LAG 200 Shelf
Service activation 2-27
...................................................................................................................................................................................................................................
363-211-555 2-1
Initial system turn-up and service activation Overview
Activate service for VoIP 2-28

Activate service over ICAPs 2-29
Activate VDSL service 2-34
Activate ADSL2 service 2-35
Activate Ethernet downlinks on ESIM 2-36
Initial system turn-up for configurations in stand-alone mode 2-37
Flowchart of system turn-up for ICAP and VoIP APs in stand-alone 2-38
mode
Links to initial system turn-up procedures for ICAP and VoIP APs in 2-40
stand-alone mode
Flowchart of system turn-up for IPADSL APs in stand-alone mode 2-42
Links to initial system turn-up procedures for IPADSL APs in 2-44
stand-alone mode
....................................................................................................................................................................................................................................
2-2 363-211-555
Initial system turn-up and service activation
Before you begin
Important notes
...................................................................................................................................................................................................................................
Overview
This section contains information that is important to know before you begin the
system turn-up. It also includes commonly used procedures that are performed in
different context, for example how to insert or remove a pack. When procedures are
required during other activities, you will automatically be pointed to the procedure
descriptions.
Controlled mode — stand-alone mode

IP-based services are supported in two modes in the AnyMedia ® Access System:
• Controlled mode
• Stand-alone mode
By default, all APs are shipped configured in controlled mode. When required they
have to be provisioned for stand-alone mode during system turn-up.
Controlled mode
In this mode, the inter-worked traffic is handled by IP spokes on the shelf backplane
which connect the pack to the IP controller. The AP configuration is stored on the IP
controller.
Therefore this mode requires the usage of a LAG Shelf equipped with an IP controller
and for some functions (LED test, pack polling or inventory data) a COMDAC as
system controller. The uplinks on the faceplates are not usable in this mode.
Note that the IPFM controlled mode is supported in the LAG Shelves only.
Stand-alone mode
In stand-alone mode the inter-worked traffic is handled by the uplinks on the faceplate
without using neither IP spokes on the backplane nor an IP controller. The SW image
and the database is stored on the AP. For some functions (LED test, pack polling,
inventory data and summary alarm) a COMDAC is required in the shelf.
This mode is supported in all shelf types, but it is not supported by each IP AP type.
Any combination of stand-alone packs is possible in the shelf and any number of
stand-alone packs is allowed. But note that every stand-alone pack is a separate NE
from the management perspective, that means it reduces the NAM capacity in terms of
managed shelves correspondingly.
...................................................................................................................................................................................................................................
363-211-555 2-3
Initial system turn-up and service activation Important notes
ESIM as controller in LAG 200 Shelf

In LAG 200 applications, the ESIM has two 100Base-T spokes to slots 2-3, and one
100Base-T spoke for ATP. The ESIM supports L3/L4 packet classification, QoS,
congestion management and access control functions.
It is used for small configurations, providing 3 slots for IP application packs
supporting:
• Fast Ethernet via the ESIM LPE408
• Voice over IP (VoIP) via the LPZ600/LPZ602
• VDSL via the LPV417
• ADSL2+ via the LPA633.
In contrast to other AnyMedia shelves it does not support TDM-based narrowband
applications or ATM xDSL applications.
Only in this shelf type the ESIM can be used as controller with the same IP-DSLAM
features as the IPFM. An IP forwarding module (IPFM) cannot be used as controller in
this shelf. In this configuration the ESIM resides in slot 1 only.
Turn-up procedures
The initial system turn-up introduces each section with a flowchart that graphically
displays the order of the turn-up procedures. Then follows an ordered sequence of links
to the applicable turn-up procedures.
Save to NVDS
Important! After each set of provisioning operations, the provisioning data must be
written to NVDS. If it is not written to NVDS, the provisioning data will be lost
when the IPFM or AP pack is reset or removed and reinserted.
Assumption
For some functions (LED test, pack polling or inventory data) a COMDAC and for
metallic line testing additionally a CIU/CTU are required in the LAG shelf. The IP
packs have to be provisioned on the COMDAC too. It is assumed that COMDAC and
CIU/CTU have been inserted and that COMDAC and CIU/CTU and the IP packs have
been provisioned on the COMDAC as described in the Commands and Procedures for
narrowband services.
....................................................................................................................................................................................................................................
2-4 363-211-555
Configuration considerations for the different AnyMedia ® shelf

types
...................................................................................................................................................................................................................................
Overview
The Commands and Procedures for IP-based Services apply to all IP-based services in
the AnyMedia Access System, independent of the shelf type used:
• AnyMedia ® LAG 1900 Shelf
• AnyMedia ® ETSI V5 Shelf (consider limitations on support of IP-based services)
• AnyMedia FAST Shelf (consider limitations on support of IP-based services).
Although the principle of turn-up and operations and maintenance is the same for the
different LAG Shelf types, there are some differences to consider regarding:
• Physical design and IPFM/ESIM type used
• Slot numbering
• Access Identifiers.
LAG 1900 Shelf physical design

Each AnyMedia LAG 1900 Shelf includes one row for circuit packs and application
packs. If one IPFM is inserted, it provides up to 13 slots for application packs. IPFMs
(LPI904/906) reside in slot 1 (preferred IPFM slot) and optionally in slot 2 (IPFM
protection slot).
...................................................................................................................................................................................................................................
363-211-555 2-5
Initial system turn-up and service activation Configuration considerations for the different AnyMedia ®
shelf types
Important! Do not insert ICAPs into slots 1-2!

In controlled and stand-alone mode, ICAPs are only supported in slots 3-14.

Each AnyMedia LAG 4300 Shelf includes two rows for circuit packs and application
packs. If one IPFM is inserted, both rows together provide up to 42 slots for
application packs. IPFMs (LPI903) reside in slot 25 (preferred IPFM slot) and optional
in slot 26 (IPFM protection slot).
....................................................................................................................................................................................................................................
2-6 363-211-555
shelf types
Connector field
IO_E1
spare
IPFM or AFM or AP
IPFM or AFM or AP
AP or RGP
AP or RGP
4 5
COMDAC
COMDAC
IO_E1
IO_E1
CIU
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
Upper Row
2 3
IO_E1
IO_E1
P 1 1 2 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43
Fans and Cables

AFM or AP
AFM or AP
Lower Row
OAP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
AP
1 2 3 4 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
Cables

In controlled and stand-alone mode, ICAPs are only supported in slots 1-24, 27-43.

The AnyMedia ® LAG 200 Shelf provides three AP slots for supporting the following
IP-based services:
• One ESIM (LPE408, 8 ports) for Ethernet access and for controlling, which resides
in slot AP-1 only and
• one VoIP AP (LPZ600, 32 ports) for VoIP services and one VSIM AP (LPV417, 16
ports) for VDSL services, which reside in the slots AP-2, AP-3 or
• up to two VoIP AP (LPZ602, 64 ports) for VoIP services, which reside in the slots
AP-2, AP-3 or
• up to two IPADSL2 AP (LPA633, 32 ADSL2/2+ ports) for xDSL services, which
reside in the slots AP-2, AP-3.
TDM-based narrowband services and ATM xDSL services are not supported.
....................................................................................................................................................................................................................................
363-211-555 2-7
shelf types
Air outlet
For future
use
Connection panel
PFU
PFU
ESIM AP
IP AP
IP AP
RGU
RGU
01 02 03
AP-1 AP-2 AP-3
Cable trough
Fan unit
Air filter
Air inlet
ETSI V5 Shelf physical design

Each AnyMedia ETSI V5 Shelf includes one row for circuit packs and application
packs. For IP-based services IP COMDAC APs (ICAPs) in stand-alone mode and
LPZ600 can be inserted, other IP AP types are not supported by the shelf backplane. In
this mode, the ICAP uses one FE port on the faceplate to directly connect to the IP
network without using an IPFM controller. An ICAP may reside in any AP slot. The
COMDAC(s) and CIU are required for certain functionality such as inventory
management, LED test or metallic line testing.
....................................................................................................................................................................................................................................
2-8 363-211-555
shelf types
Fan unit and air outlet FAULT F1 F2 F3 T315 mA J1

A B C D E F G H J K
HDLC-1 HDLC-2 IO_E1P IO_E1-1IO_E1-2 IO_E1-3IO_E1-4 PFU A1 B1 C1 D1 E1 F1 G1 H1 J1 K1
IO_HDLC
IO_HDLC
IO_E1P
RING0
RING1
E1 DOWN
E1 DOWN
- 48A
- 48B
IO_E1
IO_E1
IO_E1
IO_E1
E1 UP
E1 UP
GPC
TAP
PFU
LAN
J2
ALTPWR SC ALARM OUT RTU ALARM IN

1 2 1 1 2 3 4 A2 D2 F2 H2 J3
AFM or Application pack

AFM or Application pack
Application pack
Application pack
Application pack
Application pack
Application pack
Application pack
Application pack
Application pack
Application pack
Application pack
Application pack
Application pack
Application pack
Application pack
COMDAC
COMDAC
CIU
1 2 1 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16
COM-1 COM-2 CIU AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8 AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15 AP-16
Cable trough and air inlet (baffle)

The AnyMedia LAG 2300 shelf arranged as RT accommodates 6 small and 19 large
circuit packs, all with 25 mm horizontal spacing.
Important! The AFM packs, ATM xDSL APs or IPFMs are used only with RT
applications.
If one IPFM is inserted, it provides up to 15 slots for application packs. IPFMs
(LPI904/906) reside in slot 1 (preferred IPFM slot) and optionally in slot 2 (IPFM
protection slot).
Sample AnyMedia LAG 2300 Shelf Arrangement
....................................................................................................................................................................................................................................
363-211-555 2-9
shelf types
AnyMedia LAG 2300 Shelf

-48V(F1)15A -48V(M1)10A
! WARNING:
AnyMedia Access System FCM REMOVAL OF FUSES
WILL CAUSE LOSS -20Hz / 1A F1 F2 -20Hz -48V -20Hz ALM A B PWR
OF SERVICE A B -48V RTN RTN -48V
-48V
-48V(F2)15A -48V(M2)10A FAIL LAN
I I A A
O O P P
D D
S S or or
1 1
IO-4 IO-5
C C A A A A A A A A A A A A A A A A
F F P P P P P P P P P P P P P P 43.5 cm
I I O O M M
O O M M C 17 in
D D
S S D D T or or or or or or or or or or or or or or or or
1 1 A A U 33.8 cm
C C I I S S S S S S S S S S S S S S
IO-2 IO-3
P P e e e e e e e e e e e e e e 13.2 in
I I F F r r r r r r r r r r r r r r
O O M M v v v v v v v v v v v v v v
D D e e e e e e e e e e e e e e
S S r r r r r r r r r r r r r r
1 1
AP-1/ AP-2/ AP-3 AP-4 AP-5 AP-6 AP-7 AP-8 AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15 AP-16
IO-P IO-1 COM-1 COM-2 CTU
AFM AFM
Cable Trough
21610_fig_008n_6
54.9W x 43.5H x 33.3D cm
21.4W x 17H x 13D in
Important! The AnyMedia LAG 2300 Shelf does not yet support IP-based services
via IPFM(s) and simultaneous xDSL-based services via AFM(s) at the same time.
In controlled and stand-alone mode, ICAPs are only supported in slots 3-16.
FAST Shelf physical design

Each AnyMedia FAST Shelf includes one row for circuit packs and application packs.
For IP-based services only IP COMDAC APs (ICAPs) in stand-alone mode can be
inserted, other IP AP types are not supported by the shelf backplane. In this mode, the
ICAP uses one FE port on the faceplate to directly connect to the IP network without
using an IPFM controller. An ICAP may reside in any AP slot. The COMDAC(s) and
CTU are required for certain functionality such as inventory management or LED test.
....................................................................................................................................................................................................................................
2-10 363-211-555
shelf types
FAST Shelf
-48V(F1)15A -48V(M1)10A
! WARNING:
REMOVAL OF FUSES
WILL CAUSE LOSS -20Hz / 1A F1 F2 -20Hz -48V -20Hz ALM A B PWR
OF SERVICE A B -48V RTN RTN -48V
-48V
-48V(F2)15A -48V(M2)10A FAIL LAN
I I
A A
O O P P
D D
S S
1 1 A A A A A A A A A A A A A A or or
P P P P P P P P P P P P P P
C C S S
or or or or or or or or or or or or or or e e 43.5 cm
O O
I I C r r 17 in
O O M M v
D D T S S S S S S S S S S S S S S v
S S D D e
1 1 U e e e e e e e e e e e e e e er r 33.8 cm
A A r r r r r r r r r r r r r r
v v v v v v v v v v v v v v 13.2 in
C C or
I I e e e e e e e e e e e e e e or
O
D
O
D
r r r r r r r r r r r r r r A A
S S
1 1 F F
M M
Cable Trough
21610_fig_008n_5a
54.9W x 43.5H x 33.3D cm
21.4W x 17H x 13D in
Important! The AFM packs or ATM xDSL APs are used only with RT
applications.
Pack placement in the different LAG Shelf types

Descriptions of the IP-based subsystem may include the terms ″preferred IPFM slot″
and ″IPFM protection slot″. These terms are generic because the preferred IPFM slot
and the IPFM protection slot have a different slot number in the different LAG shelf
types. The table below lists the slot numbers for the preferred IPFM slots and the
IPFM protection slots for the different AnyMedia LAG Shelf types.
Shelf/row Supported Preferred IPFM slot IPFM protection Additional AP slots (1)
regions slot
AnyMedia LAG 1900 For AP-1 AP-2 AP-2 to AP-14 in simplex mode
Shelf international AP-3 to AP-14 in duplex mode
regions only
( 2)
AnyMedia LAG 4300 AP-25 AP-26 AP-1 to AP-24
Shelf AP-26 to AP-43 in simplex mode
AP-27 to AP-43 in duplex mode
( 3)
AnyMedia LAG 200 Not applicable (4) Not applicable AP-2 to AP-3
Shelf
AnyMedia LAG 2300 For North AP-1 AP-2 AP-2 to AP-16 in simplex mode
Shelf America AP-3 to AP-16 in duplex mode
regions (NAR)
only (5)
....................................................................................................................................................................................................................................
363-211-555 2-11
shelf types
Notes:
1. The number of the AP slot assumes that IP-based services only are supported.
2. Controlled and stand-alone mode, ICAPs are only supported in slots 3-14. Do not insert ICAPs into slots
1-2!
3. Controlled and stand-alone mode, ICAPs are only supported in slots 1-24, 27-43. Do not insert ICAPs
into slots 25-26!
4. The IPFM and the AFM/IP-AFM cannot be used in the LAG 200 Shelf, but an ESIM is used in
controller mode in slot 1 instead.
5. Controlled and stand-alone mode, ICAPs are only supported in slots 3-16. Do not insert ICAPs into slots
1-2!
Access identifiers for LAG Shelf types

The access identifiers used for the user-interfaces are different for the different LAG
Shelf types.
Entity AIDs on LAG 1900 Shelf AIDs on LAG 4300 AIDs on LAG 200 AIDs on LAG 2300 Shelf
Application ap-{1}-{2-14} ap-{1}-{1-24} ap-{1}-{2-3} ap-{1}-{2-16}

pack ap-{1}-{26-43}
Port on an ap-{1}-{2-14}-{1-64} ap-{1}-{1-24}-{1-64} ap-{1}-{2-3}-{1-32} ap-{1}-{2-16}-{1-64}
AP ap-{1}-{26-43}-{1-64}
IPFM ap-{1}-{1-2} ap-1-{25-26} N/A ap-{1}-{1-2}
ESIM (used N/A N/A ap-{1}-{1} N/A

as
controller)
....................................................................................................................................................................................................................................
2-12 363-211-555
OAM&P Connectivity
...................................................................................................................................................................................................................................
Overview
This section describes the maintenance interfaces for operations, administration,
maintenance, and provisioning (OAM&P) of the AnyMedia ® Access System related to
IP-based services.
Where to access the system for OAM&P activities, depends on whether the packs
operate in controlled mode or in stand-alone mode.
In controlled mode the interfaces used are located on the IPFM (or on the ESIM if the
ESIM is used in controller mode in a LAG 200 Shelf). The following OAM&P
interfaces are provided:
• 100Base-T port (outband)
• Inband management channel
• CONSOLE port (for initial system turn-up)
For stand-alone mode the OAM&P interfaces used are located on the individual APs.
The following table shows as an overview the subscriber interfaces, the network
interfaces (for stand-alone mode and for controlled mode) and the OAM&P interfaces
used in each mode.
Note that not all IP APs support stand-alone mode and that not all IP APs provide the
same management ports.
Interface Pack Type
IPFM ICAP VoIP AP VSIM AP ESIM IP-AFM IPADSL2_32 AP
Subscriber - 8 E1/DS1 32 Z or 16 VDSL 8 Fast Broadband The connector

interfaces 64 Z interfaces Ethernet distribution on the AP side
with interfaces with downlinks bus to ATM includes two
36-pin with 64-pin with SFPs xDSL APs connectors:
AMP 64-pin AMP a/b (up to 736 POTS connector
champ AMP a/b connector xDSL with 32 pin
ribbon connector subscribers
style on and
connectors controlled POTS-ADSL
APs) connector with
32 pin
...................................................................................................................................................................................................................................
363-211-555 2-13
Initial system turn-up and service activation OAM&P Connectivity
Interface Pack Type
IPFM ICAP VoIP AP VSIM AP ESIM IP-AFM IPADSL2_32 AP
Network In IPFM 2 GbE IP spoke to IPFM N/A IP spoke to

controlled uplinks IPFM
mode with
GBICs
2 FE
uplinks
100Base-T
port with
RJ-45
connectors
In - 1 10/100 1 10/100 - 1 GbE 4 GbE with Two
stand- Base-T Base-T uplink SFP 100/1000Base-T
alone uplink uplink with SFP 2 FE uplinks 2 with
mode with RJ-45 with uplinks RJ-45 connectors
connector RJ-45 100Base-T
(FE1) connector1 ports with
RJ-45
connectors
In ESIM - - - - 1 GbE - -
controller uplink
mode with SFP3
4
OAM&P In 100Base-T - - - N/A -
controlled port with
mode RJ-45
connector
Inband
management
channel
CONSOLE
port with
9-pin
D-sub
connector 5
In - RS232 RS232 N/A6 RS232 RS232 local RS232 port with

stand- port with local port with console port USB-A physical
alone USB-A console USB-A with RJ-45 connector 5
mode physical port with physical connector 10/100Base-T
connector5 RJ-45 connector 5 10Base-T port with RJ-45
Inband connector1 10/100Base-T port or connector
5
management , port with remote link Inband
channel Inband RJ-45 with RJ-45 management
management connector connector channel
channel Inband
management
channel
Notes:
1. Only the VoIP AP LPZ600 supports stand-alone mode.
2. One for future use.
3. Applicable in LAG 200 Shelves only.
....................................................................................................................................................................................................................................
2-14 363-211-555
4. If the ESIM is used in controller mode in a LAG 200 Shelf, then it provides the same management
interfaces as in stand-alone mode.
5. For initial system turn-up.
6. Pack is not yet used in stand-alone mode.
This section contains information on:

• PC/GSI interface cabling to OAM&P ports in a simplex configuration of the IP
controller which is done in the same way as the OAM&P cabling to the
10/100Base-T management port of APs in stand-alone mode
– “Simplex direct 10/100BASE-T port connection ” (p. 2-15)
– “Simplex 10/100BASE-T port connection via hub” (p. 2-16)
• PC/GSI interface cabling to OAM&P ports in a duplex configuration of the IP
controller (not applicable to an ESIM controller),
– “Duplex direct 10/100BASE-T port connection ” (p. 2-17)
– “Duplex 10/100BASE-T port connection via hub” (p. 2-18)
• For OAM&P connection via an inband management channel refer to “Set inband
management channel (optional) ” (p. 7-59).
• “Serial connection to USB-A ports” (p. 2-18)
Simplex direct 10/100BASE-T port connection

For connecting directly (without going through a network or a hub) to the
10/100Base-T port in simplex mode use the following commercially available cable:
• Commonly called a “10BaseT cable”
• Wired “cross over” as described in the table below:
• RJ-45 connector on both ends
• Length suitable for location of the IPFM circuit pack relative to the location of the
PC
End A End B
RJ-45 Pin Signal RJ-45 Pin Signal
1 Transmit Data + 3 Receive Data +
2 Transmit Data - 6 Receive Data -
3 Receive Data + 1 Transmit Data +
6 Receive Data - 2 Transmit Data -
The figure below shows the signal flow for simplex 10BaseT port connection
....................................................................................................................................................................................................................................
363-211-555 2-15
1 TD+ TD+ 1
2 TD- TD- 2
3 RD+ RD+ 3
6 RD- RD- 6
PC IPFM
Simplex 10/100BASE-T port connection via hub

For connecting not directly to the 10BaseT port in simplex mode (but going through a
network or a hub) use the following commercially available cable:
• RJ-45 connector on both ends
• Wired “straight-through” as described in the table below:
End A (GSI/EMS) End B (IPFM)

1 Transmit Data + 1 Transmit Data +
2 Transmit Data - 2 Transmit Data -
3 Receive Data + 3 Receive Data +
6 Receive Data - 6 Receive Data -
The figure below shows the signal flow for simplex LAN connection
1 TD+ TD+ 1
2 TD- TD- 2
3 RD+ RD+ 3
6 RD- RD- 6
HUB IPFM
....................................................................................................................................................................................................................................
2-16 363-211-555
Duplex direct 10/100BASE-T port connection

For connecting directly to the 10/100BASE-T port in duplex mode (without going
through a network or a hub) there are two possibilities:
• Connect the PC/GSI directly to the active IP controller using a cable as described
in “Simplex direct 10/100BASE-T port connection ” (p. 2-15)above. If the IP
controller executes a side switch, the PC/GSI cable has to be moved to the newly
active IP controller.
• Construct a special Y-assembly as described below and use it to connect both IP
controllers directly to the PC/GSI.
– Obtain a commercially available “straight-through” wired RJ45 modular splitter.
– Connect commercially available straight through wired 10BaseT cables as
described in “Simplex 10/100BASE-T port connection via hub” (p. 2-16) to two
of the split-out jacks of the RJ45 modular splitter and the IP controllers.
– Connect commercially available cross over wired 10BaseT cables as described
in “Simplex direct 10/100BASE-T port connection ” (p. 2-15) to the common
jack of the RJ45 modular splitter and the PC.
The figure below shows how to construct this special Y-assembly.
RJ 45 Modular Splitter
Jack 1
Common Jack
IPFM 1 10BaseT
10/100BASE-Tx
A “straight-through”
10BaseT 10BaseT
IPFM 2 PC
10/100BASE-Tx “straight-through” “cross-over” C
B
Jack 2
The signals and pins of this complete Y-assembly with RJ-45 plug connectors on all
three ends and wired “cross over” is shown in the table below.
End A (IP controller 1) End B (IP controller 2) End C (GSI/EMS)

RJ-45 Signal RJ-45 Pin Signal RJ-45 Pin Signal
Pin
1 Transmit Data + 1 Transmit Data + 3 ReceiveData +
....................................................................................................................................................................................................................................
363-211-555 2-17
End A (IP controller 1) End B (IP controller 2) End C (GSI/EMS)

RJ-45 Signal RJ-45 Pin Signal RJ-45 Pin Signal
Pin
2 Transmit Data - 2 Transmit Data - 6 Receive Data -
3 Receive Data + 3 Receive Data + 1 Transmit Data +
6 Receive Data - 6 Receive Data - 2 Transmit Data -
Duplex 10/100BASE-T port connection via hub

For connecting not directly to the 10BaseT port in duplex mode (but going through a
network or a hub) connect both IP controllers to a hub and then connect the PC/GSI to
the hub using a cable as described in “Simplex 10/100BASE-T port connection via
hub” (p. 2-16)above.
Serial connection to USB-A ports

The serial connection to the USB-A port on IP APs is used for initial system turnup in
stand-alone mode. For this serial connection Alcatel-Lucent provides an adapter cable
with USB-A connector (DB9-to-USB RS232) ED7C873-31 G8.
Important! Although the CONSOLE connector below the FAULT LED looks like
a USB connector, it is not a USB connector. It will not work if a laptop is
connected, but attaching a true USB host or peripheral to this port may damage the
USB drivers of this device or the pack.
Note that not all IP APs provide a serial USB-A port.
....................................................................................................................................................................................................................................
2-18 363-211-555
Links to commonly used procedures

...................................................................................................................................................................................................................................
Overview
In this context commonly used procedure means procedures that may be used for
different reasons and in different states of turn-up and maintenance activities, (e.g. how
to insert or remove a pack).
Commonly used procedures:
• “Installing the GSI” (p. 7-6)
• “System Access via GSI ” (p. 7-14)
• “Insert a pack ” (p. 7-41)
• “Remove a Circuit Pack ” (p. 7-11)
• “Wiring for ESIMs used as APs” (p. 7-202)
• “Wiring for ICAPs” (p. 7-174)
• “Wiring for VoIP APs” (p. 7-106)
• “Wiring for VDSL APs” (p. 7-196)
• “Wiring for IPADSL2_32p APs ” (p. 7-232)
...................................................................................................................................................................................................................................
363-211-555 2-19
Initial system turn-up for configurations in

controlled mode
Overview
...................................................................................................................................................................................................................................
Purpose
This section provides information about the activities that are required for initial
system turn-up in controlled mode, either with IPFM controller or with ESIM used as
controller in a LAG 200 Shelf.
The section includes for both types flowcharts which guide on a high level through the
required activities. The flowcharts are followed by a set of links which point to the
applicable detailed procedure descriptions in the correct sequence.
This section includes
• A flowchart and links to all procedures used for initial system turn-up with
IPFM(s)
• A flowchart and links to all procedures used for initial system turn-up of the ESIM
used as controller in the LAG 200 Shelf.
Contents
Flowchart of system turn-up with IPFM(s) 2-21

Links to initial system turn-up procedures with IPFM(s) 2-23
Flowchart of system turn-up for ESIM used as controller in the 2-24
LAG 200 Shelf
Links to initial system turn-up of the ESIM used as controller in the 2-26
LAG 200 Shelf
...................................................................................................................................................................................................................................
2-20 363-211-555
Flowchart of system turn-up with IPFM(s)

...................................................................................................................................................................................................................................
Flowchart
The flowchart graphically displays the sequence of the required turn-up procedures.
After the flowchart the links to the applicable detailed turn-up procedure descriptions
are provided in the correct order.
...................................................................................................................................................................................................................................
363-211-555 2-21
Initial system turn-up and service activation Flowchart of system turn-up with IPFM(s)
Begin of Turn-Up Procedures with IPFM
IPFM Installation
Set/Retrieve IP address
Duplex mode
Simplex mode Provision

duplex IPFM mode
Verify/Update
software load
Change password
IPFM Cabling
Set Date and Time required
no Set date and time
Set inband management channel required
no Set inband
Management channel
Provision the IPFM uplink

transmission parameters
Spanning tree protocol group Link aggregation
Provision Spanning Provision

Tree protocol group Link aggregation
Provision
the IPFM for QoS
AP Installation
Provision IP AP slots
End of Turn-Up
In the HTML file click on image to enlarge
....................................................................................................................................................................................................................................
2-22 363-211-555
Links to initial system turn-up procedures with IPFM(s)

...................................................................................................................................................................................................................................
Overview
This section contains links to the detailed procedure descriptions of all procedures
mostly required for initial system turn-up. It is strongly recommended to perform the
procedures in the correct order as shown in the Flowchart or as given below. Note that
not all of these procedures are required for each system turn-up. Some of them are
optional.
Links to procedures:
1. “IPFM Installation” (p. 7-44)
2. “Set/Retrieve IP address ” (p. 7-66)
3. “Provision duplex IPFM mode (optional)” (p. 7-46)
4. “Verify/Update software load ” (p. 7-73)
5. “Change password ” (p. 7-26)
6. “Wiring for IPFM” (p. 7-78)
7. “Set/Retrieve Date and Time ” (p. 7-61)
8. “Set inband management channel (optional) ” (p. 7-59)
9. “Provision the IPFM uplink transmission parameters” (p. 7-52)
10. If link aggregation is required “Provision link aggregation (optional) ” (p. 7-49)
11. If spanning tree protocol group is required “Provision spanning tree protocol group
(optional) ” (p. 7-54)
12. “Provision the IPFM/ESIM for QoS ” (p. 7-279)
13. “AP Installation” (p. 7-24)
14. “Provision IP AP slots” (p. 7-48).
If the provisioning of L2 and L3 functionality is required (e.g. creation of VLANs)
refer also to Chapter 3, “Support L2 and L3 functionality”.
...................................................................................................................................................................................................................................
363-211-555 2-23
Flowchart of system turn-up for ESIM used as controller in the

LAG 200 Shelf
...................................................................................................................................................................................................................................
Flowchart
...................................................................................................................................................................................................................................
2-24 363-211-555
Initial system turn-up and service activation Flowchart of system turn-up for ESIM used as controller
in the LAG 200 Shelf
Begin of Turn-Up Procedures with ESIM
ESIM Installation
Verify/Update
software load
Change password
Wiring for ESIM

used as controller
no
Set date and time
no Set inband
Management channel
Provision the ESIM uplink

transmission parameters
Spanning tree protocol group Link aggregation
Provision Spanning Provision

Tree protocol group Link aggregation
Provision
the ESIM for QoS
AP Installation
End of Turn-Up
....................................................................................................................................................................................................................................
363-211-555 2-25
Links to initial system turn-up of the ESIM used as controller

...................................................................................................................................................................................................................................
Overview
This section contains links to the detailed procedure descriptions of the procedures
required for initial system turn-up of the ESIM used as controller in the LAG 200
Shelf. It is strongly recommended to perform the procedures in the correct order as
shown in the flowchart above or as given below. Note that not all of these procedures
are required for each system turn-up. Some of them are optional.
1. “ESIM Installation in a LAG 200 Shelf (controller mode) ” (p. 7-39)
2. “Set/Retrieve IP address ” (p. 7-66)
3. “Verify/Update software load ” (p. 7-73)
5. “Wiring for ESIM used as controller ” (p. 7-75)
6. If Set/Retrieve Date and Time is required “Set/Retrieve Date and Time ” (p. 7-61)
7. If set inband management channel is required “Set inband management channel
8. “Provision uplink transmission parameters on the ESIM used as controller in the
LAG 200 Shelf ” (p. 7-57)
9. If link aggregation is required “Provision link aggregation (optional) ” (p. 7-49)
10. If spanning tree protocol group is required “Provision spanning tree protocol group
12. “AP Installation” (p. 7-24)
13. “Provision IP AP slots” (p. 7-48).
...................................................................................................................................................................................................................................
2-26 363-211-555
Service activation
Overview
...................................................................................................................................................................................................................................
Purpose
This section provides for each service type a set of links which point to the applicable
detailed procedure descriptions in the correct sequence.
Contents
Activate service for VoIP 2-28

Activate service over ICAPs 2-29
Activate VDSL service 2-34
Activate ADSL2 service 2-35
Activate Ethernet downlinks on ESIM 2-36
...................................................................................................................................................................................................................................
363-211-555 2-27
Activate service for VoIP

...................................................................................................................................................................................................................................
Overview
This section contains links to all procedures for provisioning a VoIP AP and the
associated subscriber ports in order to activate VoIP subscriber services. Note that the
procedures have to be performed in the correct order.
Assumptions
Make sure that the following assumptions are fulfilled:
• The a/b cabling is already installed in the rack.
• The shelf is powered and equipped with one or two IPFMs.
• The IPFMs are provisioned.
• The VoIP APs are equipped and cabled. For the wiring refer to “Wiring for VoIP
APs” (p. 7-106).
• The AP slot in the LAG Shelf has been provisioned for a VoIP AP.
Procedures
For service activation follow these procedures:
1. “Provision VoIP AP parameters” (p. 7-89)
2. If the system is configured for SIP protocol follow “Provision/Retrieve SIP network
protocol parameters ” (p. 7-94)
3. If the system is configured for H.248 protocol follow “Provision/Retrieve H.248
network protocol parameters” (p. 7-100)
4. “Provision/Retrieve MGCP network protocol parameters” (p. 7-103)
5. “Provision port parameters on a VoIP AP” (p. 7-86).
If the provisioning of L2 functionality is required (e.g. creation of VLANs) refer also
to Chapter 3, “Support L2 and L3 functionality”.
...................................................................................................................................................................................................................................
2-28 363-211-555
Activate service over ICAPs

...................................................................................................................................................................................................................................
Overview
This section contains links to all procedures for provisioning IP COMDAC APs
(ICAPs) in order to transport TDM traffic across an IP network. Note that the
The ICAP provides the same VoIP capabilities as the VoIP AP.
For background information and most useful references to provision service activation
over ICAP see “Background – ICAP table interrelations” (p. 2-30).
Procedures
Assumptions
• The E1/DS1 cabling is already installed in the rack.
• The shelf is powered and, if the pack will operate in controlled mode, the shelf is
equipped with an IP controller that is provisioned already.
• The AP slot in the Shelf has been provisioned for an ICAP.
1. “Provision ICAP parameters ” (p. 7-113) and “Provision VLANs, IP addresses and
Routing on ICAP” (p. 7-157) this also includes the provisioning of multiple IP
addresses within the ICAP.
2. “Provision/retrieve ICAP profiles ” (p. 7-125)
3. “Provision/retrieve network protocol parameters ” (p. 7-130)
4. “Provision/retrieve SIP port parameters on an ICAP ” (p. 7-148).
5. “Provision/retrieve H.248 port parameters on an ICAP ” (p. 7-138)
6. “Provision/retrieve MGCP port parameters on an ICAP ” (p. 7-143)
7. “Provision/retrieve feeder parameters on an ICAP ” (p. 7-118)
8. “Provision duplex ICAPs in controlled mode or stand-alone mode (optional)”
(p. 7-155) Note that in a duplex configuration do not connect E1/DS1 cables to the
ICAP before the ICAP has been set to “duplex”.
9. “Provision parameters for V5.2 aggregation on an ICAP ” (p. 7-165)
10. Follow the “Wiring for ICAPs” (p. 7-174) procedure to connect E1/DS1 cables to
the ICAP(s).
...................................................................................................................................................................................................................................
363-211-555 2-29
Initial system turn-up and service activation Activate service over ICAPs
Background – ICAP table interrelations
Provisioning Model Overview VoIP to TDM
SIP/H248/MGCP Interface RTP Profile Emergency#Profil
DigitMapProfile
only SIP only SIP

SIP/H248/MGCP Port NumberTranslation SipSwitchProfile
only SIP and MGCP only SIP

PortProfile Emergency#Exclude EmergencyCall
MediaMonitoring
TDM CrsConnect
optional for OAM ROC
only in auto-
RT TDM Port created
RT Interface IP Interface
E1 mode
RT Link RTL CrsConnect
E1 Feeder
only in
V5 TDM UserPort V5U CrsConnect
E1 mode
V5CommChannel
V5 Interface V5ProtGroup
V5CommPath
V5 Link V5L CrsConnect
E1 Feeder
only in auto-
R2 TDM Port created
R2 Interface
E1 mode
E1 Feeder
only in auto-
Gr303 TDM Port created
GR303 Interface
Ds1 mode
Gr303 Link GR303 CrsConnect
DS1 Feeder
....................................................................................................................................................................................................................................
2-30 363-211-555
Provisioning Model IP Connectivity
(auto-created)
IP Interface
(used for downstream RT + OAM ROCs)
Routing Policy Route2 Tables
VLAN Table + (used for upstream IP interfaces)

IP Interface
Provisioning Model Overview V5 CommChannels, CommPaths and ProtectionGroups
CCTS CrsConnect V5CommChannel CPCC CrsConnect
auto
V5 Link V5 Link Timeslot PGCC CrsConnect V5CommPath
created
PGTS CrsConnect V5ProtectionGroup
Provisioning examples of multiple IP addresses on ICAP

The next figure shows L2/L3 VLANs, where RTP, Signaling and OAM&P data streams
of the ICAP in controlled mode can be sent to the next network node (IPFM, L2/L3
switch) via one line. To separate these data over two or three different ways each data
stream can have a dedicated VLAN ID, which can be assigned to a dedicated IP
address.
Layer 3 VLAN provisioning via ICAP for multiple IP addresses
....................................................................................................................................................................................................................................
363-211-555 2-31
RTP
streams OAM&P
GSI/NMS
AnyMedia LAG shelf
VLAN table (IPFM) VLAN table
VLAN IP Addr. Mask FE1 FE2 7 VLAN IP Addr. Mask BP FP VPT
10 T T 10 10.0.0.1 255.0.0.0 T 1
20 T T 20 20.0.0.1 255.0.0.0 T 3
router 40 40.0.0.1 255.0.0.0 T 5
40 40.0.0.2 255.0.0.0 T T
10.0.0.10 tagged FE1 tagged AnyMedia RT1
40.0.0.40 IP spoke 7
VLAN 10 + 40 VLAN
IP Interface
10,20,40 ROC1
IPIF# IP Addr. Mask Remote IP 30.0.1.2
1 30.0.1.1 255.255.255.0 30.0.1.2
8 30.0.8.1 255.255.255.0 30.0.8.2
untagged
E1/DS1 I/F
OAM&P for AnyMedia RTs:
VLAN 40, 40.0.0.1 as Gateway 30.0.1.1
RTP: 10.0.0.1
Signaling: 20.0.0.1 untagged
VoIP 30.0.8.1
signaling Routing Policy table
Pol Idx Src IP Source Mask RT Idx#
1 30.0.0.0 255.0.0.0 3 AnyMedia RT8
2 10.0.0.1 255.255.255.255 2
4 20.0.0.1 255.255.255.255 4 ROC8
router
Static Route table 30.0.8.2
tagged FE2
20.0.0.20
Table 3 Dest IP Dest Mask Gatway
VLAN 20
3 0.0.0.0 0.0.0.0 40.0.0.40
3 2 Dest
Table 0.0.0.0 0.0.0.0
IP Dest 40.0.0.40
Mask Gatway
2 4 0.0.0.0 0.0.0.0
0.0.0.0 0.0.0.0 20.0.0.20
10.0.0.10
3 0.0.0.0 0.0.0.0 40.0.0.40
Table 4 Dest IP Dest Mask Gatway
44 0.0.0.00.0.0.0
0.0.0.0 0.0.0.0 20.0.0.20
20.0.0.20
OAM&P for IPFM: 40.0.0.2
the IPFM operate in layer 2 mode
IPFM ICAP (slot 7)
Dest IP Destination IP address BP Backplane

Src IP Source IP address FP Faceplate Port
IPIF IP Interface
VPT VLAN Priority Tag
Rules and relationships between parameter used to provision multiple IP addresses on ICAP
Parameter used
• Management IP address (for ICAP in stand-alone mode only)
• Control IP address
• RTP IP address
• VLAN
• Static Route Table
• Routing Policy.
ICAP in controlled mode
for 1-IP: Call Control and RTP IP addresses must be the same
for 2-IP: Call Control and RTP IP addresses are different (IP addresses must be different on
subnets / VLANs)
ICAP in stand-alone mode
....................................................................................................................................................................................................................................
2-32 363-211-555
Standalone ICAP CLI turn-up script will default the ICAP to use 1-IP address
For 1-IP: Management, Call Control and RTP IP addresses are the same
For 2-IP: Management (ip #1), Call Control and RTP IP addresses must be the same (ip #2)
(IP addresses must be different on subnets / VLANs)
For 3-IP: Management, Call Control and RTP IP addresses are different (IP addresses must be
different on subnets / VLANs)
Management parameters The management IP address and VLAN cannot be changed from the initial turn-up values.
The management default gateway may be changed but care must be taken as not to loose
remote access to the pack.
VLAN tab There must by 1 VLAN for each unique ICAP IP address (Management, Call Control and/or
RTP)
The VLAN IP addresses must match the ICAP’s IP addresses (Management, Call Control and
RTP) exactly.
Each VLAN must be on a different subnet.
Only one Untagged VLAN is allowed.

Static Route Table Tab Default Gateway Routes
• A default gateway should be provisioned for each VLAN entry.
• Default gateways are defined as: dest_ip_addr = 0.0.0.0 / mask = 0.0.0.0
Static Routes
• Route_Index = 1 is the ICAP’s main default route.
• All static (non-default-gateway) routes must be added to Route_Index = 1
Route Policy Tab A route policy should be provisioned for each default gateway defined in the static route
table. (Note: A route policy is optional for static route index 1 since it is the ICAP’s main
default route.)
The Source_IP_Addr must match the ICAP’s IP addresses (Management, Call Control and
RTP) exactly.
....................................................................................................................................................................................................................................
363-211-555 2-33
Activate VDSL service

...................................................................................................................................................................................................................................
Overview
This section contains links to all procedures for provisioning a VSIM AP and the
associated subscriber ports in order to activate VDSL subscriber service. Note that the
Predefined profiles
The IP subsystem contains a library of predefined profiles, applicable for supporting
VDSL service:
• VSIM transmission profiles
• VSIM performance management profiles.
These profiles cannot be deleted or edited. But they can be used to build new profiles.
Assumptions
• The shelf is powered and equipped with one or two IPFMs.
• The IPFMs are provisioned.
• The VSIM APs are equipped and cabled. For the wiring refer to “Wiring for VDSL
APs” (p. 7-196).
• The AP slot in the LAG Shelf has been provisioned for a VSIM AP.
Procedures
1. “Provision port parameters on a VSIM AP ” (p. 7-185)
2. “Provision/Retrieve VSIM transmission profile” (p. 7-191)
3. “Provision/Retrieve VSIM PM profile” (p. 7-188)
4. “Provision VSIM APs for QoS ” (p. 7-287)
5. “Retrieve VSIM transmission status” (p. 7-195)
...................................................................................................................................................................................................................................
2-34 363-211-555
Activate ADSL2 service

...................................................................................................................................................................................................................................
Overview
In this context, ″ADSL2 service″ also covers ADSL2+ service.
This section contains links to all procedures for provisioning an IPADSL2 AP and the
associated subscriber ports in order to activate ADSL2 subscriber service. Note that the
Predefined profiles
The IP subsystem contains a library of predefined profiles, applicable for supporting
ADSL2 service:
• IPADSL line configuration profiles
• IPADSL performance management profiles
• Bridge port profiles
• Bridge port traffic profiles
• Bridge port performance management profiles.
These profiles cannot be deleted or edited. But they can be used to build new profiles.
Assumptions
• The shelf is powered and, if the pack will operate in IPFM controlled mode, the
shelf is equipped with one or two IPFMs that are provisioned already.
• The APs are equipped and cabled. For the wiring refer to “Wiring for
IPADSL2_32p APs ” (p. 7-232).
• The AP slot in the LAG Shelf has been provisioned for the correct AP type.
Procedures
1. “Provision port parameters on an IPADSL2 AP ” (p. 7-211)
2. “Provision/Retrieve IPADSL transmission profile” (p. 7-220)
3. “Provision/Retrieve IPADSL PM profile” (p. 7-225)
4. “Provision/Retrieve IPADSL bridge port profile” (p. 7-228)
5. “Provision/Retrieve bridge port traffic profile” (p. 7-217)
6. “Provision/Retrieve bridge port PM profile ” (p. 7-214)
7. “IPADSL2 AP provisioning for QoS ” (p. 4-4)
For OAM&P purposes also the following procedures may apply:
• “Retrieve VSIM transmission status” (p. 7-195)
...................................................................................................................................................................................................................................
363-211-555 2-35
Activate Ethernet downlinks on ESIM

...................................................................................................................................................................................................................................
Overview
This section contains links to all procedures for provisioning an ESIM and the
associated subscriber ports in order to activate the Ethernet downlinks.
Note that the procedures have to be performed in the correct order.
Assumptions
• The shelf is powered.
• If the pack will work in IPFM controlled mode, the LAG Shelf is equipped with
one or two IPFMs and the IPFMs are provisioned.
• The ESIMs are equipped and cabled. For the wiring refer to “Wiring for ESIMs
used as APs” (p. 7-202).
• The AP slot in the shelf has been provisioned for an ESIM.
Procedures
1. “Provision port parameters on ESIM ” (p. 7-200)
2. “Provision link aggregation (optional) ” (p. 7-49)
3. “Provision spanning tree protocol group (optional) ” (p. 7-54)
...................................................................................................................................................................................................................................
2-36 363-211-555
Initial system turn-up for configurations in

stand-alone mode
Overview
...................................................................................................................................................................................................................................
Purpose
This section provides information about the activities that are required for initial
system turn-up of IP APs in stand-alone mode. Note that stand-alone mode is not
supported for each IP AP type.
The section includes flowcharts (for the IP AP types which support stand-alone mode),
which guide on a high level through the required activities. The flowcharts are
followed by a set of links which point to the applicable detailed procedure descriptions
in the correct sequence.
Contents
Flowchart of system turn-up for ICAP and VoIP APs in stand-alone 2-38
mode
Links to initial system turn-up procedures for ICAP and VoIP APs in 2-40
stand-alone mode
Flowchart of system turn-up for IPADSL APs in stand-alone mode 2-42
Links to initial system turn-up procedures for IPADSL APs in 2-44
stand-alone mode
...................................................................................................................................................................................................................................
363-211-555 2-37
Flowchart of system turn-up for ICAP and VoIP APs in

stand-alone mode
...................................................................................................................................................................................................................................
Flowchart
...................................................................................................................................................................................................................................
2-38 363-211-555
Initial system turn-up and service activation Flowchart of system turn-up for ICAP and VoIP APs in
stand-alone mode
Begin of Turn-Up Procedures with ICAP and VoIP APs in stand-alone mode
AP Insertion
IPFM present in shelf No IPFM present in shelf
Configure parameters Configure stand-alone

for stand-alone via GSI mode via terminal
Set AP to stand-alone
via GSI
Faceplate connections
for APs used
in stand-alone mode
Connect GSI via uplink

IP address
no Set Date and Time
Change password
(if required)
ICAP in Duplex mode
no Provision to duplex
(only applicable for ICAP(s))
E1/DS1 Wiring
AP Software download
and activation
End of Turn-Up
....................................................................................................................................................................................................................................
363-211-555 2-39
Links to initial system turn-up procedures for ICAP and VoIP

APs in stand-alone mode
...................................................................................................................................................................................................................................
Overview
By default, the ICAP and the VoIP APs are configured in controlled mode. When
required, the controlled mode has to be changed to stand-alone mode during system
turn-up.
In stand-alone mode several functions which are usually performed by the IP controller
have to be done by the APs. In this mode the APs are self-managed packs which can
be housed in any AnyMedia shelf. Faceplate connections are used for all IP traffic and
OAM&P data.
The ICAP supports simplex or duplex operation. For duplex operation in stand-alone
mode the FE2 ports of both ICAPs have to be connected via a LAN crossover cable.
From the management point of view, each AP in stand-alone mode (or each pair of
ICAPs in duplex mode) is a separate NE and needs to be accessible via the GSI
individually. For the description of how to access the AP via the GSI see the “System
Access via GSI ” (p. 7-14) procedure.
Assumptions
• The shelf is powered.
• If the ICAPs operate in duplex mode, the preferred one resides in an odd numbered
slot and the non-preferred ICAP resides in the even numbered slot to the right.
• If the ICAP operates in simplex mode, it is recommended to install the first ICAP
in the odd numbered slot (preferred slot) and leave the even numbered slot to the
right empty, to be prepared for the future use of the ICAP duplex future.
Links to procedures
This section contains links to the detailed procedure descriptions of the individual
procedures for initial system turn-up of ICAP and VoIP APs (LPZ600 only) in
stand-alone mode. It is strongly recommended to perform the procedures in the correct
...................................................................................................................................................................................................................................
2-40 363-211-555
Initial system turn-up and service activation Links to initial system turn-up procedures for ICAP and
VoIP APs in stand-alone mode
order as shown in the previous flowchart or in the following ordered list. Note that not
all of these procedures are required for each system turn-up. Some of them are
optional.
1. Insert the pack into the shelf as described in “Insert a pack ” (p. 7-41)
2. As next steps in the turn-up flow set the IP address and change the pack
configuration mode to stand-alone mode.
If there is an IP controller present in the shelf, follow “Configure stand-alone mode
for ICAP or VoIP APs via IP controller and GSI” (p. 7-36) and then “Configure
stand-alone/controlled mode via GSI” (p. 7-38).
If there is no IP controller present in the shelf, follow “Configure or retrieve
stand-alone mode for ICAP or VoIP AP via terminal” (p. 7-31)
3. For the cabling follow either “Wiring for ICAPs” (p. 7-174) or “Wiring for VoIP
APs” (p. 7-106) respectively, depending on the pack type inserted.
4. Follow the “System Access via GSI ” (p. 7-14) procedure to connect the GSI via
uplink
5. If Set/Retrieve Date and Time is required “Set/Retrieve Date and Time for APs in
stand-alone mode” (p. 7-64)
6. “Change password on ICAP” (p. 7-28)
7. Provision the ICAP for duplex mode if required “Provision duplex ICAPs in
controlled mode or stand-alone mode (optional)” (p. 7-155)
8. Follow the “Wiring for ICAPs” (p. 7-174) procedure to connect the E1/DS1 cables
to the ICAP(s).
9. “Software download/activation and database backup/restore for stand-alone AP(s)”
(p. 7-340)
....................................................................................................................................................................................................................................
363-211-555 2-41
Flowchart of system turn-up for IPADSL APs in stand-alone

mode
...................................................................................................................................................................................................................................
Flowchart
...................................................................................................................................................................................................................................
2-42 363-211-555
Initial system turn-up and service activation Flowchart of system turn-up for IPADSL APs in
stand-alone mode
Begin of Turn-Up Procedures with ASIM APs in stand-alone mode
AP Installation
AP Software download
and activation
Wiring for APs used

in stand-alone mode
Change password
no
Set date and time
no Set inband
Management channel
Provision the uplink for

APs in stand-alone mode
End of Turn-Up
....................................................................................................................................................................................................................................
363-211-555 2-43
Links to initial system turn-up procedures for IPADSL APs in

stand-alone mode
...................................................................................................................................................................................................................................
Overview
By default, all AP APs come configured in IPFM controlled mode. When required, the
IPFM controlled mode has to be changed to stand-alone mode during system turn-up.
Moreover several functions which are usually performed by the IPFM have to be done
by the IP AP.
From the management point of view, each IP AP in stand-alone mode is a separate NE
and needs to be access via the GSI individually follow the “System Access via GSI ”
(p. 7-14) procedure.
This section contains links to the detailed procedure descriptions of the procedures
required for initial system turn-up of stand-alone APs. Currently it applies to the
IPADSL2_32p AP only. It is strongly recommended to perform the procedures in the
correct order as shown in the flowchart above or as given below. Note that not all of
these procedures are required for each system turn-up. Some of them are optional.
1. Insert the pack into the shelf as described in “Insert a pack ” (p. 7-41)
2. “Set System Management IP address via serial port on IPADSL AP” (p. 7-68)
3. “AP Software download and activation in controlled mode” (p. 7-297)
4. Wiring for APs used in stand-alone mode (“Wiring for IPADSL2_32p APs ”
(p. 7-232))
6. “Provision IP AP slots” (p. 7-48)
7. “Set/Retrieve Date and Time for APs in stand-alone mode” (p. 7-64)
8. “Set up inband management channel for IPADSL in stand-alone mode (optional) ”
(p. 7-71)
9. Provision the uplink transmission parameters for APs in stand-alone
...................................................................................................................................................................................................................................
2-44 363-211-555
3 S upport L2 and L3 functionality
3
Related procedures
...................................................................................................................................................................................................................................
Overview
The IP subsystem supports several Layer 3 and Layer 2 functionalities.
The following Layer 2 functionality is supported:
• VLAN configuration
• MAC Learning
• Spanning tree.
The following Layer 3 functionality is supported:
• Static route
• IGMP snooping
• Trace route.
Each of the following blocks includes the links to the detailed procedure descriptions
that apply to this functionality.
VLAN configuration
Procedures that are related to VLAN creation include:
• “Create/modify a VLAN ” (p. 7-239)
• “Provision/Disable broadcast storm control ” (p. 7-252).
Note that VLAN provisioning on VoIP APs and on ICAPs is handled differently. It is
already included in the procedures used for activating VoIP service or service over
ICAPs and does not require further activities.
MAC learning
The IP packs (except the VoIP APs) internally maintain a table with the MAC
addresses that are learned from the network (dynamic MAC addresses).
It is also possible to provision secure MAC addresses in the table directly by the
operator (static MAC addresses).
MAC Learning is described in:
• “Provision/Delete MAC address learning ” (p. 7-248)
....................................................................................................................................................................................................................................
363-211-555 3-1
Support L2 and L3 functionality Related procedures
Spanning tree
When uplinks are configured using spanning tree, one of the links is considered to be a
redundant connection and is placed in the blocked state by one node in the spanning
tree, that means, no traffic is forwarded to it.
A spanning tree protocol group may be provisioned during initial system turn-up.
The procedure is described in:
• “Provision spanning tree protocol group (optional) ” (p. 7-54)
Static route
Routers forward packets to the destination addresses based on information from static
routes or dynamic routing protocols. The IPFM supports up to 256 static route entries.
The procedure how to set up a static route is described in:
• “Provision/Delete static route” (p. 7-251)
IGMP snooping
The purpose of IGMP snooping is to restrain multicast traffic in a switched network.
With IGMP snooping enabled, the switch intercepts IGMP messages from the host
itself and updates its MAC table accordingly.
Provisioning of IGMP snooping is described in:
• “Provision/Disable IGMP snooping ” (p. 7-254)
DHCP relay
If DHCP services are used to distribute dynamic IP addresses to the APs and they are
not located in the same subnet as the APs, the IPFM can act as a DHCP relay between
the DHCP requests of the APs and the DHCP servers.
The procedure how to provision/delete the IP addresses is described in:
• “Provision/Delete addresses in DHCP relay ” (p. 7-247)
Trace route
The procedure how to trace the route through a network is described in:
• “Trace route” (p. 7-257)
...................................................................................................................................................................................................................................
3-2 363-211-555
4 Q uality of service
4
Overview
...................................................................................................................................................................................................................................
Purpose
The following chapter provides some general recommendations for quality of service
(QoS) provisioning on the IP subsystem and points to the related procedures.
The QoS provisioning is different for different pack types. Therefore links are provided
to detailed procedure descriptions. The procedure descriptions include information
about how to provision the classifier tables, the classification rules and the scheduler
on the IPFM and how to set up classification rules and provision the scheduler on
VSIM APs.
For VoIP APs and ICAPs all settings that have to be done for QoS provisioning are
already included in the procedures used for activating VoIP service or service over
ICAPs and do not require further activities.
Nevertheless, for completeness reasons these settings are summarized additionally here,
within the QoS considerations.
...................................................................................................................................................................................................................................
363-211-555 4-1
Quality of service
QoS provisioning recommendations

...................................................................................................................................................................................................................................
Strategy
For QoS provisioning on the IP subsystem the following is recommended:
1. Assign VoIP traffic to a dedicated VLAN.
This isolates the traffic from subscriber data traffic and it permits to provision a
concise classifier to match VoIP traffic. Otherwise, it is difficult to provision a
classifier, because signaling (SIP/H.248) uses a deterministic port #, but RTP
packets can be assigned to thousands of port values.
2. The VLAN assignment can be made
• on the IPFM with untagged uplinks from the VoIP APs, or
• on the IPFM and on the APs using tagged uplinks.
Both VLAN assignment options are supported. Tagged uplinks permit 802.1p
priority to be set on the APs, but this provides no clear advantage.
3. Construct a classifier to match the VoIP VLAN number.
If SIP signaling is used and it is desired to provide differentiated QoS for
emergency services, then provision multiple classifiers to match all combinations of
the VoIP VLAN and TOS octet. Also, provision the TOS values on the APs.
4. Assign the classified VoIP traffic to high-priority queues.
If WRR scheduling is used, then allocate bandwidth for the VoIP service class.
5. Assure that default classifiers are defined for subscriber data packets.
The subscriber data traffic must be assigned to lower-priority queues than VoIP
traffic. Optionally re-mark the subscriber data packets.
...................................................................................................................................................................................................................................
4-2 363-211-555
Quality of service
Related procedures
...................................................................................................................................................................................................................................
Overview
The following blocks include the links to the detailed procedure descriptions that apply
to the different pack types.
IPFM provisioning for QoS

Procedures that are related to IPFM provisioning for QoS include:
• “Provision the IPFM/ESIM for QoS ” (p. 7-279)
• “Provision/Modify packet type priorities for QoS” (p. 7-269).
• “Provision/Modify L2/L3 group priorities for QoS” (p. 7-259)
• “Provision/Modify L4 group priorities for QoS” (p. 7-262)
VSIM AP provisioning for QoS

Procedures that are related to VSIM AP provisioning for QoS include:
• “Provision VSIM APs for QoS ” (p. 7-287)
• “Provision/Modify classifiers on VSIM APs” (p. 7-265)
• “Provision/Modify policies on VSIM APs” (p. 7-272)
• “Provision/Modify policy instances on VSIM APs” (p. 7-277)
• “Provision/Modify policy attributes on VSIM APs” (p. 7-274)
VoIP AP provisioning for QoS

For VoIP APs all settings that have to be done for QoS provisioning are already
included in the procedures used for activating VoIP service.
Procedures that are related to VoIP AP provisioning for QoS include:
• “VoIP AP provisiong for QoS” (p. 4-5)
• “VLAN provisioning on VoIP APs” (p. 4-7)
• “TOS provisioning on VoIP APs” (p. 4-8)
• “Subscriber priority provisioning on VoIP APs” (p. 4-10)
ESIM provisioning for QoS

Procedures that are related to ESIM provisioning for QoS include:
• “Provision the IPFM/ESIM for QoS ” (p. 7-279)
• “Provision/Modify packet type priorities for QoS” (p. 7-269)
• “Provision/Modify L2/L3 group priorities for QoS” (p. 7-259)
• “Provision/Modify L4 group priorities for QoS” (p. 7-262)
...................................................................................................................................................................................................................................
363-211-555 4-3
Quality of service Related procedures
IPADSL2 AP provisioning for QoS

There are 8 possible values for 802.1p priority bits, 0 through 7 in the upstream
direction to establish a priority on the packets that go towards the controller pack or
towards the network (when the LPA633 is in standalone). And in the downstream
direction, ATM Service Categories can be used to establish for priorities of traffic
(CBR, rtVBR, nrtVBR, and UBR from highest to lowest).
Procedures that are related to IPADSL2 AP provisioning for QoS include:
• “Provision/Retrieve IPADSL bridge port profile” (p. 7-228)
• “Provision/Retrieve bridge port traffic profile” (p. 7-217).
...................................................................................................................................................................................................................................
4-4 363-211-555
Quality of service
VoIP AP provisiong for QoS

...................................................................................................................................................................................................................................
Overview
As mentioned, all settings that have to be done for QoS provisioning for VoIP APs are
already included in the procedures used for VoIP service activation.
The VoIP pack offers QoS on three levels:
• VLAN tagging and 802.1q priority
• IP TOS settings
• Subscriber priority.
The three levels are provisioned independently from each other.
VLAN support
QoS based on VLAN tagging only affects data transmission in the network. VoIP pack
operation is only affected as frames might not be accepted.
If VLAN administration is enabled:
• All frames will be sent VLAN tagged.
• Only tagged frames with the correct VLAN ID are accepted, other frames are
dropped.
• Only 1 VLAN ID is supported using a single 802.1q priority for all ports on the
pack.
• IPFM QoS settings must match VoIP configuration.
If VLAN administration is disabled:
• All frames will be sent untagged.
• Only untagged frames are accepted.
IP TOS support
TOS settings will only affect data transmission in the IP network as the VoIP pack is
no possible point of congestion for downstream data.
Four different data types with individual TOS settings exist:
• Normal call control data (for call setup)
• Normal call RTP data (for voice)
• Emergency call control data (for call setup)
• Emergency call RTP data (for voice)
All ports on a pack use the same TOS configuration. As a rule, the TOS for emergency
calls should be higher than those for normal calls The TOS settings for the classes
define the complete TOS byte. Therefore the provisionable range is 0{255.
...................................................................................................................................................................................................................................
363-211-555 4-5
Quality of service VoIP AP provisiong for QoS
Subscriber priority
Subscriber priority defines a possible limitation of system resources for subscribers of
different classes. This may affect data transmission and is therefore regarded as part of
QoS.
• Four classes are defined:
– Emergency
– Urgent
– Normal
– Non-urgent.
• For each class, the maximum percentage of system performance allowed can be
provisioned (threshold).
• 100% equals 36 RTP streams.
• The sum of all settings can exceed 100%
• There is a strict priority among the four classes. If high-priority users consume all
RTP streams, then lower-priority users are denied service.
• Existing calls are not disrupted.
• If a new RTP stream would exceed the provisioned threshold, the call setup is
rejected. The originating subscriber will receive an announcement or tones to
indicate that the call attempt is denied.
...................................................................................................................................................................................................................................
4-6 363-211-555
Quality of service
VLAN provisioning on VoIP APs

...................................................................................................................................................................................................................................
Purpose
As already mentioned, the VLAN provisioning on VoIP APs is already covered in
“Provision VoIP AP parameters” (p. 7-89). The following steps especially repeat and
summarize what has to be done for VLAN provisioning on VoIP APs as part of QoS
considerations.
Procedure
...................................................................................................................................................................................................
1 From the menu bar select IP Subsystem -> VoIP -> Network...
Result: The VoIP System Turnup window opens, displaying the tab Network.
...................................................................................................................................................................................................
2 In the VLAN Administration field enter the VLAN ID which is used to tag transmitted
frames.
...................................................................................................................................................................................................
3 In the Priority Tag text line enter the 802.1p priority (range: 0...7).
...................................................................................................................................................................................................
4 From the Admin Status pull-down menu select Enabled.

Result:
VLAN tagging is turned on.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
363-211-555 4-7
Quality of service
TOS provisioning on VoIP APs

...................................................................................................................................................................................................................................
Purpose
The TOS provisioning on VoIP APs is also already covered in “Provision VoIP AP
parameters” (p. 7-89). The following steps repeat and summarize what has to be done
especially for TOS provisioning on VoIP APs as part of QoS considerations.
TOS provisioning consists of:
• TOS provisioning for the normal call RTP (voice data)
• TOS provisioning for normal call setup (SIP or H.248)
• TOS provisioning for the emergency call RTP (voice data)
• TOS provisioning for emergency call setup (SIP).
Procedure
...................................................................................................................................................................................................
1 From the menu bar select IP Subsystem -> VoIP -> Network...
Result: The VoIP System Turnup window opens, displaying the tab Network.
...................................................................................................................................................................................................
2 In the Configuration Parameters field enter the TOS Control which is used for
normal call setup (SIP or H.248).
...................................................................................................................................................................................................
3 Select the tab Media.

...................................................................................................................................................................................................
4 In the text line TOS enter the TOS value for the normal call RTP.
...................................................................................................................................................................................................
5 IF... THEN...
the control protocol is H.248 END OF STEPS
the control protocol is SIP go to Step 6.
...................................................................................................................................................................................................
6 Select the tab SIP and then the subtab Control.

...................................................................................................................................................................................................
7 In the Emergency Rtp TOS text line enter the TOS value for the emergency call RTP
(voice data).
...................................................................................................................................................................................................................................
4-8 363-211-555
Quality of service TOS provisioning on VoIP APs
...................................................................................................................................................................................................
8 In the Emergency Ctr TOS text line enter the TOS value for the emergency call setup
(SIP).
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
363-211-555 4-9
Quality of service
Subscriber priority provisioning on VoIP APs

...................................................................................................................................................................................................................................
Purpose
The subscriber priority provisioning on VoIP APs is already covered in
“Provision/Retrieve SIP network protocol parameters ” (p. 7-94). The following steps
repeat and summarize what has to be done especially for subscriber priority
provisioning on VoIP APs as part of QoS considerations. Note that subscriber priority
provisioning is supported only when the SIP protocol is used.
The following subscriber priorities are supported:
• Emergency
• Urgent
• Normal
• Non-Urgent.
Procedure
...................................................................................................................................................................................................
1 From the menu bar select IP Subsystem -> VoIP -> SIP...
Result: The VoIP System Turnup window opens, displaying the tab SIP.
...................................................................................................................................................................................................
2 Select the subtab Control.

...................................................................................................................................................................................................
3 In the field Call Priority Thresholds enter the maximum percentage of system
performance per subscriber priority class and click Apply.
...................................................................................................................................................................................................
4 Select the subtab Transport.

...................................................................................................................................................................................................
5 From the Port pull-down menu select an individual subscriber port.

...................................................................................................................................................................................................
6 From the Subscriber Priority pull-down menu select the required subscriber priority
and click Apply.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
4-10 363-211-555
5 5 perations, administration and
O
maintenance functions
Related procedures
...................................................................................................................................................................................................................................
Overview
In this information product operations, administration and maintenance functions mean
functionality that is related to:
• Configuration management
• Inventory management
• Performance management
• Fault management
• Reconfiguration/Migration.
Each of the following blocks includes the links to the detailed descriptions of the
procedures that apply to this functionality.
Assumption
For these procedures it is assumed that the IP subsystem is up and running. Procedures
that are based on more specific assumptions, will provide more detail.
Configuration management
Software and configuration data management refers to the management of program
images of the IPFM and the APs and to the handling of provisioning data. It also
means methods to backup and restore the database.
The following procedures are applicable:
• “Database backup” (p. 7-306)
• “Database restore ” (p. 7-308)
• “IPFM/ESIM Software download and activation” (p. 7-335)
• “AP Software download and activation in controlled mode” (p. 7-297)
• “System initialization” (p. 7-347)
....................................................................................................................................................................................................................................
363-211-555 5-1
Operations, administration and maintenance functions Related procedures
Inventory management
Inventory management information for the IPFM and the IP APs can be retrieved via
the IPFM as soon as the packs have been inserted. A technician sees a graphical
representation of the AnyMedia ® LAG Shelves populated with IPFM pack(s) and IP
APs on the GSI .
In mixed configurations, inventory management information for IP packs, as well as
TDM narrowband APs, can also be retrieved via the COMDAC. A technician, logged
into the COMDAC, sees a graphical representation of the AnyMedia ® LAG Shelves
populated with both TDM narrowband and IP APs on the GSI. A technician in a mixed
configuration, when connected to the IPFM, sees a graphical representation of the
AnyMedia ® LAG Shelves populated with IP APs only on the GSI.
Inventory management in the IP subsystem is supported by the following procedure:
• “Retrieve IP Equipment” (p. 7-328)
Performance management
Performance management is the system activity for collecting and reporting data on the
quality of transmission. The IP subsystem supports remote monitoring (RMON)
according to RFC1757.
It contains statistics measured by the probe for each monitored Ethernet interface on
the device.
Currently, performance management in the IP subsystem is supported by the following
procedures:
• “Retrieve RMON statistics” (p. 7-330)
The following procedure applies to the system performance of the IP subsystem:
• “Provision/deprovision CPU utilization alarm” (p. 7-326).
Fault management
Fault management is the system activity for operations that cover the following:
• Maintenance — automatic and manual activities to ensure continued operation and
minimize service degradation.
• Alarms — equipment and facility monitoring that results in alarms.
• Protection switching
– IPFM protection
Automatic switch from a failing IPFM to a standby IPFM when a fault is
detected on the active IPFM
– Uplink protection
Automatic switch from the active IPFM to a standby IPFM when a fault is
detected on any uplink of the active IPFM. The uplinks that shall be used after
the side switch are provisionable.
– 1:N POTS circuit protection
• Testing — turn-up tests and on-demand circuit testing.
...................................................................................................................................................................................................................................
5-2 363-211-555
Operations, administration and maintenance functions Related procedures

• “VoIP Voice stream monitoring” (p. 7-350)
• “Activate system log facility” (p. 7-304)
• “Retrieve active alarms” (p. 7-327)
• “IPFM Migration from duplex to simplex mode” (p. 7-323)
• “Provision duplex IPFM mode (optional)” (p. 7-46)
• “Activate VoIP AP 1:N port protection” (p. 7-294)
• “Deactivate VoIP AP 1:N port protection” (p. 7-310)
• Metallic line test.
For the description of how to perform a metallic line test refer to the Commands
and Procedures for Narrowband Services.
Reconfiguration/Migration
Reconfiguration/migration refers to procedures required for growth or degrowth of the
system and for migration from simplex mode to duplex mode and vice versa.
• “IP AP Growth” (p. 7-317)
• “IP AP Degrowth” (p. 7-318)
• “Provision duplex IPFM mode (optional)” (p. 7-46)
• “IPFM Migration from duplex to simplex mode” (p. 7-323)
• “Force IPFM side switch” (p. 7-313).
• “Provision duplex ICAPs in controlled mode or stand-alone mode (optional)”
(p. 7-155)
• “ICAP Migration from duplex to simplex mode” (p. 7-321)
...................................................................................................................................................................................................................................
363-211-555 5-3
6 A larms and trouble clearing
6
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter contains an alarm description for each alarm that may be raised in the IP
subsystem and leads to the applicable trouble clearing procedures. The alarm
descriptions show which alarm strings may be provided by the IP subsystem, inform
about the possible causes, the impact on service and the default severity of these
alarms.
The alarm descriptions are grouped into several categories. The last paragraph of each
alarm description directly leads to the corresponding trouble clearing procedure which
is included later in this chapter.
Reporting and retrieving IP related alarms

The alarms for IP APs and the IPFM are reported/retrieved via the IP-related OAM&P
interfaces as described in “Overview” (p. 2-13). The system also supports query for
alarms and status conditions over these interfaces.
Active alarms can be retrieved via “Retrieve active alarms” (p. 7-327).
Note: Environmental alarms, the IP subsystem summary alarm as well as pack failure
alarms for the AnyMedia® LAG Shelves are reported via the OAM&P interfaces for
narrowband services.
Contents
Software alarms 6-5

IPFM software mismatch alarm 6-6
IPFM/ESIM software mismatch between AP and IPFM/ESIM alarm 6-7
Software program corrupt alarm 6-8
Generic system fault alarms 6-9
IPFM uplink failure alarm 6-10
Slot-xx unequipped alarm 6-11
...................................................................................................................................................................................................................................
363-211-555 6-1
Alarms and trouble clearing Overview
Pack type mismatch alarm 6-12

NTP Synchronization failed alarm 6-13
CPU utilization reaches its threshold alarm 6-14
Specific ICAP alarms 6-15
V5 faults – Overview 6-17
V5 interface failed alarm 6-18
V5 data link failed alarm - Common Control 6-19
V5 data link failed alarm - PSTN 6-20
V5 data link failed alarm - Protection 6-21
V5 data link failed alarm - Bearer Channel Control 6-22
V5 data link failed alarm - Link Control 6-23
V5 data link failed alarm - timeslot cessation of flags 6-24
V5 PSTN restart failed alarm 6-25
V5 interface service degraded alarm 6-26
V5 interface identification failed alarm 6-27
V5 interface out of service alarm 6-28
V5 link failed alarm 6-29
V5 link identification failed alarm 6-30
V5 link disabled alarm 6-31
GR-303 faults – Overview 6-32
GR-303 data link failed alarms - TMC/EOC 6-33
GR-303 far end major or critical alarm 6-34
GR-303 far end minor alarm 6-35
RT faults – Overview 6-36
RT link identification failed alarm 6-37
RT link interface identification failed alarm 6-38
RT link layer 2 failed alarm 6-39
ROC provisioning mismatch detected alarm 6-41
RT interface failed alarm 6-42
RT interface service degraded alarm 6-43
RT interface control data link failed 6-44
ICAP specific sync faults – Overview 6-45
Synchronization input failed alarm 6-46
System free running synchronization failed alarm 6-47
...................................................................................................................................................................................................................................
6-2 363-211-555
ICAP specific system faults – Overview 6-48

Software program version mismatch alarm (ICAPs) 6-49
Database corrupt alarm (ICAP) 6-50
Database synchronization failed alarm (ICAP) 6-51
Required pack missing alarm (ICAPs) 6-52
Required pack mismatch alarm 6-53
Duplex cable misconfigured alarm 6-54
Media gateway controller not reachable alarm (ICAP) 6-55
E1 faults – Overview 6-56
AIS detected alarm 6-57
Incoming E1 signal FE degraded alarm 6-58
Incoming E1 signal near end degraded alarm 6-59
Incoming E1 signal failed alarm 6-60
Incoming E1 signal LOF alarm 6-61
Incoming E1 signal LOS alarm 6-62
Remote alarm indication received alarm 6-63
DS1 faults – Overview 6-64
Incoming DS1 signal degraded alarm 6-66
Incoming DS1 signal failed alarm 6-67
Yellow alarm received 6-68
Incoming DS1 signal LOF alarm 6-69
Incoming DS1 signal LOS alarm 6-70
Specific VoIP AP alarms 6-71
Tip/ring cable disconnect alarm 6-72
Ringing source failed alarm 6-73
MGC <IP address> connection failure alarm (VoIP AP) 6-74
VoIP port protection alarm (LPZ600) 6-75
1:N port protection failed (LPZ602) 6-76
VoIP CPU overload alarm 6-77
Trouble clearing procedures 6-78
To clear IPFM software mismatch alarm 6-80
To clear “software mismatch alarm between AP and controller flash” 6-82
To clear Database corrupt alarm (ICAP) 6-85
To clear “Uplink failure” alarm 6-87
...................................................................................................................................................................................................................................
363-211-555 6-3
To clear Slot-xx unequipped alarm 6-91

To clear Pack type mismatch alarm 6-93
To clear NTP Synchronization failed alarm 6-95
To clear V5 protocol data link faults 6-96
To clear V5 interface fault alarm 6-99
To clear GR-303 data link fault alarms 6-101
To clear RT alarms caused by wrong cabling 6-103
To clear RT link interface identification failed alarm 6-105
To clear ROC provisioning mismatch detected alarm 6-107
To clear RT interface failed alarm 6-109
To clear RT interface service degraded alarm 6-110
To clear RT interface control data link failed alarm 6-111
To clear synchronization input failed alarm 6-113
To clear Software program version mismatch alarm on ICAP 6-115
To reset IP pack 6-117
To clear Required pack missing alarm 6-118
To clear Required pack mismatch alarm 6-120
To clear incoming E1 signal fault alarms 6-122
To clear DS1 input signal fault alarms 6-126
To clear Tip/Ring cable (cable <x>) disconnect alarm 6-130
To clear Ringing source failed alarm 6-133
To clear Media gateway controller not reachable or Proxyhost alarm 6-135
To clear VoIP port protection alarm 6-137
....................................................................................................................................................................................................................................
6-4 363-211-555
Alarms and trouble clearing
Software alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes general software alarms. Software alarms that are related to
specific packs, are described in other sections (for example, software program version
mismatch alarm which is raised on the ICAP only is described in the section “Specific
ICAP alarms”). Each alarm description points at its end to the recommended trouble
clearing.
Contents
IPFM software mismatch alarm 6-6

IPFM/ESIM software mismatch between AP and IPFM/ESIM alarm 6-7
Software program corrupt alarm 6-8
...................................................................................................................................................................................................................................
363-211-555 6-5
IPFM software mismatch alarm

...................................................................................................................................................................................................................................
Alarm description
Parameter Description
Alarm message IPFM software mismatch between
active and standby
Alarm description This alarm is generated only for circuit
packs in duplex mode.
It is raised for the IPFM.
Local indication The red LED FAULT on the IPFMs is on.
Possible cause The alarm indicates that the software on
the standby pack is different from the
software on the active pack.
It may be raised due to one of the
following reasons:
• Two IPFMs with different software
versions are inserted during system
turn-up.
• When upgrading a running system
from simplex to duplex mode.
• When software has been swapped from
Alternate version to Current version.
• After software download.
Entity AP-1-Slot#
Severity Minor
Service impact Non service affecting (NSA)
SNMP object identity ipfmSoftwareMismatchAlarm
Trouble clearing
For the trouble clearing procedure refer to “To clear IPFM software mismatch alarm”
(p. 6-80).
...................................................................................................................................................................................................................................
6-6 363-211-555
IPFM/ESIM software mismatch between AP and IPFM/ESIM

alarm
...................................................................................................................................................................................................................................
Alarm description
Alarm message IPFM software mismatch between ap
and ipfm flash
esim software mismatch between ap
and esim flash
Alarm description This alarm is generated when a mismatch
is detected between the software of a
certain AP type on the IPFM/ESIM flash
and on the flash of this AP.
It is raised for the IPFM and for the ESIM
in controller mode.
Local indication None
Possible cause The alarm may be raised in the following
scenarios:
• During system turn-up
• When software on the AP has been
swapped from Alternate version to
Current version.
• After AP SW download to IPFM
without further download to APs.
Entity AP-1-Slot#
Severity Minor
The procedure is service affecting if the
flash on the AP must be upgraded.
SNMP object identity ipApSoftwareMismatchAlarm
For the trouble clearing procedure refer to “To clear “software mismatch alarm
between AP and controller flash”” (p. 6-82).
...................................................................................................................................................................................................................................
363-211-555 6-7
Software program corrupt alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message Software program corrupt
Alarm description This alarm is generated for circuit packs.
It is raised for all pack types except the
IPFM.
Local indication Depending on the pack type the following
LED lits red:
• on the ICAP the F/A LED
• on other APs the FAULT LED.
Possible cause It indicates that the software program is
corrupted on the specified pack.
Entity AP-1-Slot#
Severity Minor
SNMP object identity genSoftwareProgramCorruptAlarm
Trouble clearing
For trouble clearing download software again to the pack. Depending on the pack type
refer to one of these procedures:
If the pack is... Then follow...

an ICAP “Software download/activation and
database backup/restore for stand-alone
AP(s)” (p. 7-340)
another application pack “Software download/activation and
database backup/restore for stand-alone
AP(s)” (p. 7-340)
...................................................................................................................................................................................................................................
6-8 363-211-555
Generic system fault alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes generic system fault alarms, that means alarms which are raised
by the system but are not associated with a specific pack/slot/port/service. Each alarm
description points at its end to the recommended trouble clearing.
Contents
IPFM uplink failure alarm 6-10

Slot-xx unequipped alarm 6-11
Pack type mismatch alarm 6-12
NTP Synchronization failed alarm 6-13
CPU utilization reaches its threshold alarm 6-14
...................................................................................................................................................................................................................................
363-211-555 6-9
IPFM uplink failure alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message ipfm uplink failure
Alarm description This alarm is generated on pack level
when one or more uplinks fail.
It is raised on the IPFM.
Possible cause It indicates that one of the IPFM uplinks
(g1, g2, f1, f2) detects a failure while
carrying service.
Entity AP-1-Slot#
Severity Critical
Service impact Service affecting (SA)
SNMP object identity ipfmUplinkFailureAlarm
Troubleclearing
For the trouble clearing procedure refer to “To clear “Uplink failure” alarm” (p. 6-87).
...................................................................................................................................................................................................................................
6-10 363-211-555
Slot-xx unequipped alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message Slot-xx unequipped, provisioned
as ...
Possible cause It indicates that a pack is removed from
one of the slots while carrying service or
that the operator performs a pack reset.
Entity AP-1-Slot#
Severity Major for APs
Minor for IPFMs
Service impact Service affecting (SA) for APs
Non service affecting (NSA) for IPFMs as
standby APs.
SNMP object identity ipfmAPPackRemovedAlarm
Trouble clearing
For the trouble clearing procedure refer to “To clear Slot-xx unequipped alarm”
(p. 6-91)
...................................................................................................................................................................................................................................
363-211-555 6-11
Pack type mismatch alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message Pack mismatch, provisioned [%],
inserted [%]
Local indication The red LED FAULT on the AP is on.
Possible cause It indicates that there is a mismatch
between an installed pack and its
provisioned pack type.
Entity AP-1-Slot#
Severity Major
SNMP object identity ipfmModuleEquipmentProvision-
ingMismatch
Trouble clearing
For the trouble clearing procedure refer to “To clear Pack type mismatch alarm”
(p. 6-93)
...................................................................................................................................................................................................................................
6-12 363-211-555
NTP Synchronization failed alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message NTP Synchronization failed
Alarm description This alarm is generated on a pack when at
least one NTP server is defined and the
NTP synchronization results in a failure.
The alarm is raised for the IPFM and for
application packs in stand-alone mode.
Possible cause • There is no route to the NTP servers.
• NTP servers specified are not working
properly for any reason.
Entity AP-1-Slot#
Severity Minor
SNMP object identity ipfmNtpSyncFailureAlarm
Trouble clearing
For the trouble clearing procedure refer to “To clear NTP Synchronization failed
alarm” (p. 6-95).
...................................................................................................................................................................................................................................
363-211-555 6-13
CPU utilization reaches its threshold alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message CPU utilization (%) reaches its
threshold
Alarm description This alarm is generated on a pack when
CPU utilization reaches its threshold.
The alarm is raised on any pack except
ICAP and VoIP AP.
Possible cause Too many processor capacity consuming
processes are running on the pack.
Entity AP-1-Slot#
Severity Minor
SNMP object identity ipfmCpuOverloadAlarm
Trouble clearing
For trouble clearing it is recommended to decrease the number of L3 VLANs, that
means to delete L3 VLANs which are not really needed.
...................................................................................................................................................................................................................................
6-14 363-211-555
Specific ICAP alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes specific ICAP alarms, that means alarms which are raised
exclusively on the ICAP. Each alarm description points at its end to the recommended
trouble clearing.
Contents
V5 faults – Overview 6-17

V5 interface failed alarm 6-18
V5 data link failed alarm - Common Control 6-19
V5 data link failed alarm - PSTN 6-20
V5 data link failed alarm - Protection 6-21
V5 data link failed alarm - Bearer Channel Control 6-22
V5 data link failed alarm - Link Control 6-23
V5 data link failed alarm - timeslot cessation of flags 6-24
V5 PSTN restart failed alarm 6-25
V5 interface service degraded alarm 6-26
V5 interface identification failed alarm 6-27
V5 interface out of service alarm 6-28
V5 link failed alarm 6-29
V5 link identification failed alarm 6-30
V5 link disabled alarm 6-31
GR-303 faults – Overview 6-32
GR-303 data link failed alarms - TMC/EOC 6-33
GR-303 far end major or critical alarm 6-34
GR-303 far end minor alarm 6-35
RT faults – Overview 6-36
RT link identification failed alarm 6-37
RT link interface identification failed alarm 6-38
ROC provisioning mismatch detected alarm 6-41
...................................................................................................................................................................................................................................
363-211-555 6-15
RT interface failed alarm 6-42

RT interface service degraded alarm 6-43
RT interface control data link failed 6-44
ICAP specific sync faults – Overview 6-45
Synchronization input failed alarm 6-46
System free running synchronization failed alarm 6-47
ICAP specific system faults – Overview 6-48
Software program version mismatch alarm (ICAPs) 6-49
Database corrupt alarm (ICAP) 6-50
Database synchronization failed alarm (ICAP) 6-51
Required pack missing alarm (ICAPs) 6-52
Required pack mismatch alarm 6-53
Duplex cable misconfigured alarm 6-54
Media gateway controller not reachable alarm (ICAP) 6-55
E1 faults – Overview 6-56
Incoming E1 signal FE degraded alarm 6-58
Incoming E1 signal near end degraded alarm 6-59
Incoming E1 signal failed alarm 6-60
Incoming E1 signal LOF alarm 6-61
Incoming E1 signal LOS alarm 6-62
Remote alarm indication received alarm 6-63
DS1 faults – Overview 6-64
Incoming DS1 signal degraded alarm 6-66
Incoming DS1 signal failed alarm 6-67
Yellow alarm received 6-68
Incoming DS1 signal LOF alarm 6-69
Incoming DS1 signal LOS alarm 6-70
....................................................................................................................................................................................................................................
6-16 363-211-555
V5 faults – Overview
...................................................................................................................................................................................................................................
Introduction
This section describes alarms on the ICAP, which refer to faults for
• protocol data links
• V5 link timeslots
• V5 interfaces
• V5 links.
These faults are related to standard V5 interfaces, which are used for connecting V5
access nodes (ANs) from any vendor to the ICAP acting as V5.2LE.
...................................................................................................................................................................................................................................
363-211-555 6-17
V5 interface failed alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message V5 interface failed
Alarm description This alarm is generated for V5 interface.
It is raised on the ICAP.
Local indication The yellow LED NE and the red LED CR
on the impacted ICAP are on.
Possible cause This alarm indicates a general failure.
Entity AP-1-slot#-interface#-V5I
Severity Critical
SNMP object identity genFailedAlarm
For the trouble clearing procedure refer to “To clear V5 interface fault alarm” (p. 6-99)
...................................................................................................................................................................................................................................
6-18 363-211-555
V5 data link failed alarm - Common Control

...................................................................................................................................................................................................................................
Alarm description
Alarm message V5 datalink failed - Common
Control
Alarm description This alarm is generated for V5 interface
data link failed - Common Control
Possible cause It indicates that a control data link to a
remote entity has failed.
Entity AP-1-slot#-interface#-V5I-CC
Severity Critical
SNMP object identity genDatalinkFailedAlarm
For the trouble clearing procedure refer to “To clear V5 protocol data link faults”
(p. 6-96)
...................................................................................................................................................................................................................................
363-211-555 6-19
V5 data link failed alarm - PSTN

...................................................................................................................................................................................................................................
Alarm description
Alarm message V5 datalink failed - PSTN
data link failed - PSTN
Local indication The yellow LED NE and the red LED MJ
Entity AP-1-slot#-interface#-V5I-PSTN
Severity Major
(p. 6-96)
...................................................................................................................................................................................................................................
6-20 363-211-555
V5 data link failed alarm - Protection

...................................................................................................................................................................................................................................
Alarm description
Alarm message V5 datalink failed - Protection
data link failed - Protection
Entity AP-1-slot#-interface#-V5I-Prot
Severity Major
(p. 6-96)
...................................................................................................................................................................................................................................
363-211-555 6-21
V5 data link failed alarm - Bearer Channel Control

...................................................................................................................................................................................................................................
Alarm description
Alarm message V5 datalink failed - Bearer
Channel Control
data link failed - Bearer Channel Control
Entity AP-1-slot#-interface#-V5I-BCC
Severity Critical
(p. 6-96)
...................................................................................................................................................................................................................................
6-22 363-211-555
V5 data link failed alarm - Link Control

...................................................................................................................................................................................................................................
Alarm description
Alarm message V5 datalink failed - Link Control
data link failed - Link Control
Entity AP-1-slot#-interface#-V5I-LC
Severity Critical
(p. 6-96)
...................................................................................................................................................................................................................................
363-211-555 6-23
V5 data link failed alarm - timeslot cessation of flags

...................................................................................................................................................................................................................................
Alarm description
Alarm messages The following alarm messages can occur:
• V5 link timeslot 15 Cessation
of Flags error
of Flags error
of Flags error
Alarm description This alarm is generated for V5 link
timeslot as follows:
• V5 link timeslot 15
Possible causes It indicates that a control data link to a
remote entity has failed due to HDLC flag
failures at a certain timeslot.
Entity Appropriate entity as follows:
• AP-1-slot#-Link#-15V5TS
Severity Major
For the trouble clearing procedure refer to procedure “To clear V5 protocol data link
faults” (p. 6-96).
...................................................................................................................................................................................................................................
6-24 363-211-555
V5 PSTN restart failed alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message V5 PSTN restart failed
Alarm description This alarm is generated for an V5
interface.
Possible cause It indicates that the restart of the PSTN
protocol on a V5 interface has failed.
Severity Major
SNMP object identity icapV5PstnRestartFailedAlarm
...................................................................................................................................................................................................................................
363-211-555 6-25
V5 interface service degraded alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message V5 interface service degraded
and is raised on the ICAP.
It indicates that the service is degraded on
the logical interface.
Possible cause The provisioned service degrade threshold
is exceeded for this interface, that is too
many links are not operational.
The V5 links may be not operational due
to accidental physical misconfigurations
between ICAP and AN.
Entity AP-1-Slot#-interface#-V5I
Severity Critical
SNMP object identity icapRtInterfaceServiceDegradeAlarm
...................................................................................................................................................................................................................................
6-26 363-211-555
V5 interface identification failed alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message V5 prov. variant or interface
identification failed
Alarm description This alarm is generated for the V5
interface or for the V5 link.
Possible causes It indicates that an identification
procedure failed due to a physical
misconfiguration or a provisioning
mismatch to the far end.
Severity Critical
SNMP object identity genIdentificationFailedAlarm
...................................................................................................................................................................................................................................
363-211-555 6-27
V5 interface out of service alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message V5 interface administratively out
of service
Alarm description This alarm is generated for V5 interface.
Note that this alarm is a customer-specific
option (CKC-dependent).
Possible cause This alarm indicates that an entity is
administratively set to disabled, that is
intentionally set to an out of service state.
Severity Critical
SNMP object identity genDisabledAlarm
...................................................................................................................................................................................................................................
6-28 363-211-555
V5 link failed alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message V5 link failed
Alarm description This alarm is generated for V5 link.
It is raised for the ICAP.
Possible cause This alarm indicates a failure of a V5
link. This alarm may be raised together
with an alarm (for example LOS, LOF,...)
of the corresponding E1 feeder.
Entity AP-1-slot#-Link#-V5L
Severity Major
SNMP object identity genFailedAlarm
...................................................................................................................................................................................................................................
363-211-555 6-29
V5 link identification failed alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message V5 link identification failed
Alarm description This alarm is generated for the V5
interface or for the V5 link.
Possible causes It indicates that an identification
procedure failed due to a physical
misconfiguration or a provisioning
mismatch of a V5 link to the far end.
Entity AP-1-slot#-Link#-V5L
Severity Major
SNMP object identity genIdentificationFailedAlarm
...................................................................................................................................................................................................................................
6-30 363-211-555
V5 link disabled alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message V5 link administratively disabled
Alarm description This alarm is generated for V5 link.
Note that this alarm is a customer-specific
option (CKC-dependent).
Possible cause This alarm indicates that an entity is
administratively set to disabled, that is
intention set into an out of service state.
Entity AP-1-slot#-interface#-V5L
Severity Major
SNMP object identity genDisabledAlarm
...................................................................................................................................................................................................................................
363-211-555 6-31
GR-303 faults – Overview

...................................................................................................................................................................................................................................
Introduction
This section describes alarms on the ICAP, which refer to data link faults for logical
GR-303 interfaces. These faults are related to standard GR-303 interfaces, which are
used for connecting access nodes (ANs) from any vendor to the ICAP as host.
...................................................................................................................................................................................................................................
6-32 363-211-555
GR-303 data link failed alarms - TMC/EOC

...................................................................................................................................................................................................................................
Alarm description
• Datalink 1 failed - TMC
• Datalink 2 failed - TMC
• Datalink 1 failed - EOC
• Datalink 2 failed - EOC
Alarm description This alarm is generated for data links for
a logical GR-303 interface as follows:
• TMC data links (1 or 2)
• EOC data links (1 or 2)
It is raised on the ICAP
Local indication For visual indication, see Step 2 in
procedure “To clear GR-303 data link
fault alarms” (p. 6-101)
Possible causes It indicates that a control data link to a
• AP-1-slot#-interface#-TMC1
or
• AP-1-slot#-interface#-TMC2
or
• AP-1-slot#-interface#-EOC1
or
• AP-1-slot#-interface#-EOC2
Severity Minor/Critical
Service impact Non service affecting (NSA) for alarm
severity “Minor”
Service affecting (SA) for alarm severity
“Critical”
For the trouble clearing procedure refer to “To clear GR-303 data link fault alarms”
(p. 6-101)
...................................................................................................................................................................................................................................
363-211-555 6-33
GR-303 far end major or critical alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message Far End major or critical alarm
received
Alarm description This alarm is generated for a logical
GR-303 interface.
Local indication The yellow LED FE and the red LED MJ
or CR on the impacted ICAP are on.
Possible causes It indicates that a major or critical alarm
is raised at the far end.
Entity AP-1-slot#-interface#
Severity Major
SNMP object identity genFarEndMajorAlarm
(p. 6-101).
...................................................................................................................................................................................................................................
6-34 363-211-555
GR-303 far end minor alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message Far End minor alarm received
Alarm description This alarm is generated for a logical
GR-303 interface.
Local indication The yellow LED FE and the yellow LED
MN on the impacted ICAP are on.
Possible causes It indicates that a minor alarm is raised at
the far end.
Entity AP-1-slot#-interface#
Severity Minor
SNMP object identity genFarEndMinorAlarm
(p. 6-101).
...................................................................................................................................................................................................................................
363-211-555 6-35
RT faults – Overview
...................................................................................................................................................................................................................................
Introduction
This section describes alarms on the ICAP which refer to RT faults. RT faults are
faults related to the remote terminals that are connected to the ICAP as host.
...................................................................................................................................................................................................................................
6-36 363-211-555
RT link identification failed alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message RT link identification failed
Alarm description This alarm is generated for a logical RT
link. It is raised on the ICAP.
Local indication The yellow LED NE on the impacted
ICAP is on.
Possible causes The remote terminal link identification
procedure may have failed due to one of
the following reasons:
• A physical misconfiguration of E1
cabling
• No SA-7 bit was received from remote
terminal
• The E1 link is connected at the far
end to an E1 feeder which is not
configured for RT service.
Entity AP-1-Slot#-link#-RTL
Severity Major
SNMP object identity icapRtLinkIdentFailedAlarm
Trouble clearing
For the trouble clearing procedure refer to “To clear RT alarms caused by wrong
cabling” (p. 6-103)
...................................................................................................................................................................................................................................
363-211-555 6-37
RT link interface identification failed alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message RT link interface identification
failed
link.
It indicates that the Remote Terminal Link
identification procedure failed due to an
interface identification mismatch.
The alarm is raised on the ICAP
Local indication The yellow LED NE on the ICAP is on.
Possible causes Accidental physical misconfiguration of
the E1 link to wrong RT link E1 port at
the far end.
Remote terminal link identification
procedure failed due to a mismatch of the
interface identification string of the
related HTI/RTI.
Severity Major
SNMP object identity icapRtLinkInterfaceIdentFailedAlarm
Trouble clearing
For the trouble clearing procedure refer to “To clear RT link interface identification
failed alarm” (p. 6-105)
...................................................................................................................................................................................................................................
6-38 363-211-555
RT link layer 2 failed alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message RT link layer 2 failed
link.
identification procedure failed due to no
layer 2 establishment.
The alarm is raised on the ICAP.
ICAP is on.
Possible causes Physical misconfiguration of remote
terminal links.
Severity Major
SNMP object identity icapRtLinkLayer2FailedAlarm
Trouble clearing
...................................................................................................................................................................................................................................
363-211-555 6-39
RT link layer 3 failed alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message RT link layer 3 failed
link.
identification procedure failed due to no
layer 3 establishment.
ICAP is on.
Possible causes Physical misconfiguration of remote
terminal links.
Severity Major
SNMP object identity icapRtLinkLayer3FailedAlarm
Trouble clearing
...................................................................................................................................................................................................................................
6-40 363-211-555
ROC provisioning mismatch detected alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message ROC provisioning mismatch detected
interface.
ICAP is on.
Possible cause Provisioning mismatch of the ROC via
nailed-up timeslot usage on the remote
terminal interface between the ICAP and
the RT.
Entity AP-1-Slot#-interface#-RTI
Severity Critical
SNMP object identity icapRtROCProvisioningMismatchAlarm
Trouble clearing
For the trouble clearing procedure refer to “To clear ROC provisioning mismatch
detected alarm” (p. 6-107)
...................................................................................................................................................................................................................................
363-211-555 6-41
RT interface failed alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message RT interface failed
interface.
ICAP is on.
Possible cause Complete remote terminal interface is not
operational. All E1 links are not connected
or broken. Identifier mismatch of all E1
links.
Severity Critical
SNMP object identity icapRtInterfaceFaultAlarm
Trouble clearing
For the trouble clearing procedure refer to “To clear RT interface failed alarm”
(p. 6-109)
...................................................................................................................................................................................................................................
6-42 363-211-555
RT interface service degraded alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message RT interface service degraded
Alarm description This alarm is generated for RT interface
It indicates that the service is degraded on
the logical interface.
ICAP is on.
Possible cause The provisioned service degrade threshold
is exceeded for this interface, that is too
many links are not operational.
The RT links may be not operational due
to accidental physical misconfigurations
between ICAP and RT or physical link
failures.
Severity Major
SNMP object identity icapRtInterfaceServiceDegradeAlarm
Trouble clearing
For the trouble clearing procedure refer to “To clear RT interface service degraded
alarm” (p. 6-110).
...................................................................................................................................................................................................................................
363-211-555 6-43
RT interface control data link failed

...................................................................................................................................................................................................................................
Alarm description
Alarm message RT interface control data link
failed
interface.
It indicates that the Layer 2 of the
signaling control channel is lost on a once
operational remote terminal interface.
ICAP is on.
Possible cause The far end interface was administratively
set to out of service.
Severity Critical
SNMP object identity icapRtInterfaceControlDatalinkAlarm
Trouble clearing
For the trouble clearing procedure refer to “To clear RT interface control data link
failed alarm” (p. 6-111)
...................................................................................................................................................................................................................................
6-44 363-211-555
ICAP specific sync faults – Overview

...................................................................................................................................................................................................................................
Introduction
This section describes alarms on the ICAP which refer to failed synchronization input
or that the network timing synchronization is lost on a specified pack in a LAG shelf
configuration.
The synchronization input faults are related to the following ICAP synchronization
sources: Physical ports, backplane, COMDAC and AFM.
...................................................................................................................................................................................................................................
363-211-555 6-45
Synchronization input failed alarm

...................................................................................................................................................................................................................................
Alarm description
• Synchronization input failed -
Feeder
Backplane 1
Backplane 2
COMDAC
AFM
Alarm description This alarm is currently used for the
following ICAP synchronization sources:
Physical ports, backplane, COMDAC and
AFM.
The alarms are raised on the ICAP.
Local indication The yellow LED NE and the yellow LED
MN on the impacted ICAP are on.
Possible cause It indicates that no valid synchronization
signal is applied to the specified input.
• AP-1-slot#-port#
• AP-1-slot#-BPSYNC1
• AP-1-slot#-BPSYNC2
• AP-1-slot#-CORE
• AP-1-slot#-AFM
Severity Minor
SNMP object identity genSynchronizationFailedInputAlarm
For the trouble clearing procedure refer to procedure “To clear synchronization input
failed alarm” (p. 6-113).
...................................................................................................................................................................................................................................
6-46 363-211-555
System free running synchronization failed alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message System free running,
synchronization failed
It is raised on the ICAP
Possible cause It indicates that the network timing
synchronization is lost on the specified
pack.
Entity AP-1-slot#
Severity Major
SNMP object identity genSynchronizationFailedSystemAlarm
For the trouble clearing verify the following alarm messages for:
• “Generic system fault alarms” (p. 6-9)
• “Specific VoIP AP alarms” (p. 6-71)
Check the signal (both clock signals have failed) and repair if necessary the clock
source.
...................................................................................................................................................................................................................................
363-211-555 6-47
ICAP specific system faults – Overview

...................................................................................................................................................................................................................................
Introduction
This section describes ICAP specific system fault alarms, that means generic system
fault alarms which are raised exclusively on the ICAP. but are not associated with a
specific pack/slot/port/service.
...................................................................................................................................................................................................................................
6-48 363-211-555
Software program version mismatch alarm (ICAPs)

...................................................................................................................................................................................................................................
Alarm description
Alarm message Software program version mismatch
Alarm description This alarm is generated only for circuit
packs in duplex mode.
Local indication The F/A LED on the active ICAP lits
green and the LEDs NE and MJ/MN lit
yellow.
Possible cause The alarm indicates that the software on
the standby pack is different from the
software on the active pack.
It may be raised due to one of the
following reasons:
• Two ICAPs with different software
versions are inserted during system
turn-up.
• When upgrading a running system
from simplex to duplex mode.
Entity AP-1-Slot#
Severity Minor
SNMP object identity ipfmSoftwareMismatchAlarm
Trouble clearing
For the trouble clearing procedure refer to “To clear Software program version
mismatch alarm on ICAP” (p. 6-115).
...................................................................................................................................................................................................................................
363-211-555 6-49
Database corrupt alarm (ICAP)

...................................................................................................................................................................................................................................
Alarm description
Alarm message Database corrupt
Currently it is raised for the ICAP
exclusively.
Possible cause It indicates that the non-volatile data
storage (NVDS) database is corrupted on
the specified pack.
Entity AP-1-Slot#
Severity Minor
SNMP object identity genDatabaseCorruptAlarm
Trouble clearing
For the trouble clearing procedure refer to “To clear Database corrupt alarm (ICAP)”
(p. 6-85)
...................................................................................................................................................................................................................................
6-50 363-211-555
Database synchronization failed alarm (ICAP)

...................................................................................................................................................................................................................................
Alarm description
Alarm message Database synchronization failed
Possible cause It indicates that the non-volatile data
storage (NVDS) database synchronization
to its duplex mate has failed.
Entity AP-1-Slot#
Severity Minor
SNMP object identity genDatabaseSyncAbortAlarm
Trouble clearing
For trouble clearing initiate a reset of the standby ICAP as described in “To reset IP
pack” (p. 6-117)
...................................................................................................................................................................................................................................
363-211-555 6-51
Required pack missing alarm (ICAPs)

...................................................................................................................................................................................................................................
Alarm description
Alarm message Required pack missing
It is raised on the ICAP in duplex mode
only.
green and the yellow LEDs NE and CR
are on.
Possible cause It indicates that the standby ICAP is
removed or that the operator performs a
pack reset.
Entity AP-1-Slot#
Severity Critical
SNMP object identity ipfmAPPackRemovedALarm
Trouble clearing
For the trouble clearing procedure refer to “To clear Required pack missing alarm”
(p. 6-118).
...................................................................................................................................................................................................................................
6-52 363-211-555
Required pack mismatch alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message Required pack mismatch
green and the yellow LEDs NE and CR
are on.
Possible cause It indicates that the hardware of the
standby ICAP is not compatible to the
hardware of the active ICAP.
Entity AP-1-Slot#
Severity Critical
SNMP object identity ipfmModuleEquipementProvisio-
ningMismatch
Trouble clearing
For the trouble clearing procedure refer to “To clear Required pack mismatch alarm”
(p. 6-120).
...................................................................................................................................................................................................................................
363-211-555 6-53
Duplex cable misconfigured alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message Duplex cable misconfigured
Alarm description This alarm is generated for circuit packs
in duplex mode.
A misconfiguration of the cabling between
duplex packs is detected.
Applicable for ICAPs in a duplex configuration in
stand-alone mode.
ICAPs is on.
Possible cause It indicates that the FE2 duplex cabling is
not established between slot n and n+1
(where n is an odd slot number).
Entity AP-1-slot#
Severity Critical
SNMP object identity genDuplexCableMisconfiguredAlarm
Trouble clearing
For trouble clearing attach the LAN crossover cable for 1:1 protection between the
FE2 ports on active and standby ICAP as described in “Wiring for ICAPs” (p. 7-174).
...................................................................................................................................................................................................................................
6-54 363-211-555
Media gateway controller not reachable alarm (ICAP)

...................................................................................................................................................................................................................................
Alarm description
Alarm message The following alarm messages can occur:
• For H.248 or MGCP protocol:
Media gateway controller not
reachable
• For SIP protocol:
Proxyhost <FQDN> OP:
yyy.yyy.yyy.yyy or
Registrar <FQN> OP:
yyy.yyy.yyy.yyy
FQDN = Fully Qualified Domain Name
OP = Outbound Proxy
yyy...yyy = IP Address of Outband Proxy.
Alarm description This alarm is generated for a logical VoIP
interface. The service of all subscribers of
this VoIP interface is affected.
This alarm is raised for VoIP interfaces on
ICAP.
Local indication The LED FE on the ICAP is on.
Possible cause It indicates that the keep-alive mechanism
to the media gateway controller
respectively softswitch of this VoIP
interface has detected a fault.
Entity AP-1-slot#-interface#-VOIP
Severity Critical
Service impact
Service affecting (SA)
SNMP object identity genMgcConnectionFailedAlarm
Trouble clearing
For the trouble clearing procedure refer to “To clear Media gateway controller not
reachable or Proxyhost alarm ” (p. 6-135).
...................................................................................................................................................................................................................................
363-211-555 6-55
E1 faults – Overview
...................................................................................................................................................................................................................................
Introduction
This section describes alarms on the ICAP which refer to incoming E1 signal faults.
The E1 signal faults are generated for physical ports of a proprietary RT E1 interface
(feeder) that is used to provide the AnyMedia RT connection.
...................................................................................................................................................................................................................................
6-56 363-211-555
AIS detected alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message AIS detected
Alarm description This alarm is generated for physical ports.
on the impacted ICAP is on.
The yellow LED CLF flashes when an AIS
alarm occurs on the E1 line.
Possible cause It indicates that a AIS (Alarm indication
signal) condition persists on the specified
port.
Entity AP-1-slot#-port#
Severity Major
SNMP object identity genAlarmIndicationSignalAlarm
For the trouble clearing procedure refer to “To clear incoming E1 signal fault alarms”
(p. 6-122)
...................................................................................................................................................................................................................................
363-211-555 6-57
Incoming E1 signal FE degraded alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message incoming E1 signal FE degraded
Local indication The yellow LEDs FE and MN on the
impacted ICAP are on.
Possible cause It indicates that the far end low BER (Bit
Error Rate) threshold is exceeded on the
specified port, i.e. the service is degraded
but still operational.
Severity Minor
SNMP object identity genLowBitErrorRateFeExceededAlarm
(p. 6-122)
...................................................................................................................................................................................................................................
6-58 363-211-555
Incoming E1 signal near end degraded alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message incoming E1 signal near end
degraded
Local indication The yellow LEDs NE and MN on the
Possible cause It indicates that the near end low BER
(Bit Error Rate) threshold is exceeded on
the specified port, i.e. the service is
degraded but still operational.
Severity Minor
SNMP object identity genLowBitErrorRateNeExceededAlarm
(p. 6-122)
...................................................................................................................................................................................................................................
363-211-555 6-59
Incoming E1 signal failed alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message incoming E1 signal failed
Local indication The yellow LED NE, the red LED MJ, and
the yellow LED CLF on the impacted
ICAP are on.
Possible cause It indicates that the high BER (Bit Error
Rate) threshold is exceeded on the
specified port, that is the port is not
operational.
Severity Major
SNMP object identity genHighBitErrorRateExceededAlarm
(p. 6-122)
...................................................................................................................................................................................................................................
6-60 363-211-555
Incoming E1 signal LOF alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message incoming E1 signal LOF
ICAP are on.
Possible cause It indicates that a LOF (Loss Of Frame)
condition persists on the specified port.
Severity Major
SNMP object identity genLossOfFrameAlarm
(p. 6-122)
...................................................................................................................................................................................................................................
363-211-555 6-61
Incoming E1 signal LOS alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message incoming E1 signal LOS
ICAP are on.
Possible cause It indicates that a LOS (Loss Of Signal)
Severity Major
SNMP object identity genLossOfSignalAlarm
(p. 6-122)
...................................................................................................................................................................................................................................
6-62 363-211-555
Remote alarm indication received alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message remote alarm indication received
ICAP are on.
Possible cause It indicates that a RAI (Remote Alarm
Indication, condition persists on the
specified port.
Severity Major
SNMP object identity genRemoteAlarmIndicationAlarm
(p. 6-122)
...................................................................................................................................................................................................................................
363-211-555 6-63
DS1 faults – Overview

...................................................................................................................................................................................................................................
Introduction
This section describes alarms on the ICAP which refer to DS1 input signal faults. The
DS1 input signal faults are generated for physical ports of a GR-303 interface (feeder)
that is used to provide the GR-303 connection.
...................................................................................................................................................................................................................................
6-64 363-211-555
AIS detected alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message AIS detected
The yellow LED CLF flashes when an AIS
alarm occurs on the DS1 line.
Possible cause It indicates that a AIS (Alarm indication
signal) condition persists on the specified
port.
Severity Major
SNMP object identity genAlarmIndicationSignalAlarm
For the trouble clearing procedure refer to “To clear DS1 input signal fault alarms”
(p. 6-126)
...................................................................................................................................................................................................................................
363-211-555 6-65
Incoming DS1 signal degraded alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message incoming DS1 signal degraded
Local indication The yellow LEDs NE and MN on the
Possible cause It indicates that the near end low BER
(Bit Error Rate) threshold is exceeded on
the specified port, i.e. the service is
degraded but still operational.
Severity Minor
SNMP object identity genLowBitErrorRateNeExceededAlarm
(p. 6-126)
...................................................................................................................................................................................................................................
6-66 363-211-555
Incoming DS1 signal failed alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message incoming DS1 signal failed
ICAP are on.
Possible cause It indicates that the high BER (Bit Error
Rate) threshold is exceeded on the
specified port, that is the port is not
operational.
Severity Major
SNMP object identity genHighBitErrorRateExceededAlarm
(p. 6-126)
...................................................................................................................................................................................................................................
363-211-555 6-67
Yellow alarm received

...................................................................................................................................................................................................................................
Alarm description
Alarm message Yellow alarm received
ICAP are on.
Possible cause It indicates that a yellow alarm condition
persists on the specified port.
Severity Major
SNMP object identity genRemoteAlarmIndicationAlarm
(p. 6-126)
...................................................................................................................................................................................................................................
6-68 363-211-555
Incoming DS1 signal LOF alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message incoming DS1 signal LOF
ICAP are on.
Possible cause It indicates that a LOF (Loss Of Frame)
Severity Major
SNMP object identity genLossOfFrameAlarm
(p. 6-126)
...................................................................................................................................................................................................................................
363-211-555 6-69
Incoming DS1 signal LOS alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message incoming DS1 signal LOS
ICAP are on.
Possible cause It indicates that a LOS (Loss Of Signal)
Severity Major
SNMP object identity genLossOfSignalAlarm
(p. 6-126)
...................................................................................................................................................................................................................................
6-70 363-211-555
Specific VoIP AP alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes specific VoIP AP alarms, that means alarms which are raised
exclusively on VoIP APs. Each alarm description points at its end to the recommended
trouble clearing.
Contents
Tip/ring cable disconnect alarm 6-72

Ringing source failed alarm 6-73
MGC <IP address> connection failure alarm (VoIP AP) 6-74
VoIP port protection alarm (LPZ600) 6-75
1:N port protection failed (LPZ602) 6-76
VoIP CPU overload alarm 6-77
...................................................................................................................................................................................................................................
363-211-555 6-71
Tip/ring cable disconnect alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm type possible tip/ring cable (cable <x>
) disconnect
Alarm description The alarm is generated when one of the
a/b (tip/ring) cable on the LPZ602 is
disconnected.
Local indication The red LED FAULT on the concerned AP
is on.
Possible cause The a/b (tip/ring) cable is disconnected or
missing (on-line).
Entity AP-1-Slot#-cable#-CABLE
Severity Minor/Major
Service impact Service affecting (SA) for major alarm or
non service affecting (NSA) for minor
alarm (that means no service is
provisioned for the pack.
SNMP object identity ipfmTipRingCableAlarm
For the trouble clearing procedure refer to “To clear Tip/Ring cable (cable <x>)
disconnect alarm” (p. 6-130).
...................................................................................................................................................................................................................................
6-72 363-211-555
Ringing source failed alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm type Ringing source failed
Alarm description The alarm is generated when ringing
voltage is not present.
Local indication The red LED FAULT on the concerned AP
is on.
Possible cause Indicates the status of the faceplate
tip-ring cable(s).
Entity AP-1-Slot#
Severity Major
SNMP object identity voipRingpackFailed
For the trouble clearing procedure refer to “To clear Ringing source failed alarm”
(p. 6-133).
...................................................................................................................................................................................................................................
363-211-555 6-73
MGC <IP address> connection failure alarm (VoIP AP)

...................................................................................................................................................................................................................................
Alarm description
Alarm message The following alarm messages can occur:
• For H.248 or MGCP protocol:
MGC <IP address> connection
failure
• For SIP protocol:
Proxyhost <FQDN> OP:
yyy.yyy.yyy.yyy or
Registrar <FQN> OP:
yyy.yyy.yyy.yyy
FQDN = Fully Qualified Domain Name
OP = Outbound Proxy
yyy...yyy = IP Address of Outband Proxy.
Alarm description This alarm is generated for a logical VoIP
interface.
It is raised for the LPZ60x.
Possible cause It indicates that the keep-alive mechanism
to the media gateway controller (MGC)
respectively softswitch of this VoIP
interface has detected a fault.
Entity AP-1-slot#-internal#-VOIP
Severity Major
SNMP object identity genMgcConnectionFailedAlarm
Trouble clearing
For the trouble clearing procedure refer to “To clear Media gateway controller not
reachable or Proxyhost alarm ” (p. 6-135).
...................................................................................................................................................................................................................................
6-74 363-211-555
VoIP port protection alarm (LPZ600)

...................................................................................................................................................................................................................................
Alarm description
Alarm message VOIP port protection alarm [%p]
Alarm description This alarm is generated when a protection
has been provisioned for a VoIP port but
the protection path cannot be established.
It is raised for the LPZ600.
Possible cause Failures of the involved equipment, that
means COMDAC, CIU and the other
LPZ600 which should provide the
protection port.
Entity AP-1-Slot#
Severity Minor
SNMP object identity voipPortProtectionAlarm
Trouble clearing
For the trouble clearing procedure refer to “To clear VoIP port protection alarm”
(p. 6-137).
...................................................................................................................................................................................................................................
363-211-555 6-75
1:N port protection failed (LPZ602)

...................................................................................................................................................................................................................................
Alarm description
Alarm message 1:N port protection failed
Alarm description This alarm is generated when 1:N port
protection failed.
It is raised for the LPZ602.
Possible cause The alarm is raised due to one of the
following reasons:
• Failure of the pack of the port to be
protected
• Failure of the pack of protection port
• Failure of the CIU.
Entity AP-1-Slot#
Severity Minor
SNMP object identity voipPortProtectionAlarm
Trouble clearing
For the trouble clearing procedure refer to “To clear VoIP port protection alarm”
(p. 6-137).
...................................................................................................................................................................................................................................
6-76 363-211-555
VoIP CPU overload alarm

...................................................................................................................................................................................................................................
Alarm description
Alarm message VoIP CPU overload
Alarm description This alarm is generated when CPU
utilization reaches its threshold.
The alarm is raised on an LPZ600.
Possible cause Too many processor capacity consuming
processes are running on the pack.
Entity AP-1-Slot#
Severity Minor
SNMP object identity ipfmCpuOverloadAlarm
Trouble clearing
Nothing specific can be recommended for trouble clearing. The alarm will be cleared
without operator interference when some of the running processes have been
completed.
...................................................................................................................................................................................................................................
363-211-555 6-77
Trouble clearing procedures
Overview
...................................................................................................................................................................................................................................
Purpose
This section contains trouble clearing procedures for the IP subsystem. These trouble
clearing procedures are cross-referenced from the alarm descriptions in the proceeding
sections.
Contents
To clear IPFM software mismatch alarm 6-80

To clear “software mismatch alarm between AP and controller flash” 6-82
To clear Database corrupt alarm (ICAP) 6-85
To clear “Uplink failure” alarm 6-87
To clear Slot-xx unequipped alarm 6-91
To clear Pack type mismatch alarm 6-93
To clear NTP Synchronization failed alarm 6-95
To clear V5 protocol data link faults 6-96
To clear V5 interface fault alarm 6-99
To clear GR-303 data link fault alarms 6-101
To clear RT alarms caused by wrong cabling 6-103
To clear RT link interface identification failed alarm 6-105
To clear ROC provisioning mismatch detected alarm 6-107
To clear RT interface failed alarm 6-109
To clear RT interface service degraded alarm 6-110
To clear RT interface control data link failed alarm 6-111
To clear synchronization input failed alarm 6-113
To clear Software program version mismatch alarm on ICAP 6-115
To reset IP pack 6-117
To clear Required pack missing alarm 6-118
To clear Required pack mismatch alarm 6-120
To clear incoming E1 signal fault alarms 6-122
To clear DS1 input signal fault alarms 6-126
To clear Tip/Ring cable (cable <x>) disconnect alarm 6-130
To clear Ringing source failed alarm 6-133
...................................................................................................................................................................................................................................
6-78 363-211-555
To clear Media gateway controller not reachable or Proxyhost alarm 6-135

To clear VoIP port protection alarm 6-137
....................................................................................................................................................................................................................................
363-211-555 6-79
To clear “IPFM software mismatch” alarm

...................................................................................................................................................................................................................................
Purpose
This procedure is used to clear an alarm that is raised in duplex IPFM mode due to
different software on the standby IPFM and the active IPFM. It must be cleared
because the system is not protected in this condition.
After completion of this procedure the correct software version is running in the IP
subsystem and the same IPFM is the active one as at the beginning.
The alarm may be raised in the following scenarios:
• During system turn-up when two IPFMs with different software versions are
inserted
• When upgrading a running system from simplex to duplex IPFM mode
• When software has been swapped from Alternate version to Current version.
The procedure is not service-affecting.
Assumption
Make sure that in a running system the following assumptions are fulfilled:
• The system configuration has been stored to NVDS.
• Duplex operation mode is required.
• The software version on the active IPFM is the required one.
Procedure
...................................................................................................................................................................................................
1 From the menu bar select IP SubSystem -> IP Data -> System -> Software ->
Administration.
Result: The Software Administration window opens. It displays the Current
software versions on both IPFMs and the Alternate software version that is also
available.
...................................................................................................................................................................................................
2 Copy software from the active IPFM to the standby IPFM. Therefore, in the SW
Download subtab select from the SW Type pull-down menu IPFM.
...................................................................................................................................................................................................
3 In the Download Direction field select the IPFM Stby checkbox and click Apply.
...................................................................................................................................................................................................................................
6-80 363-211-555
Alarms and trouble clearing To clear “IPFM software mismatch” alarm
Result: At the bottom of the Software Administration window the progress of the
file transfer and writing to flash is displayed. After completion and a refresh of the
window the new software version is displayed in the Alternate column of the
standby IPFM.
...................................................................................................................................................................................................
4 Select the SW Activation subtab on the Software Administration window.

...................................................................................................................................................................................................
5 In the SW Activation subtab select the Slot number of the standby IPFM. and click
Apply.
Result: The standby IPFM reboots. When initialization completes, the standby
IPFM is running the same software as the active IPFM.
...................................................................................................................................................................................................
6 Follow the “Retrieve active alarms” (p. 7-327) GSI operation in order to verify that
there is no longer an IPFM software mismatch alarm.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 6-81
To clear “software mismatch alarm between AP and controller

flash”
...................................................................................................................................................................................................................................
Purpose
This procedure is used to clear an alarm that is raised due to different software image
of a certain AP type on the controller flash (IPFM/ESIM) and on the flash of this AP.
After completion of this procedure the same software version is kept on the controller
flash and on the flash of the AP running in the IP subsystem.
Note that the term controller is used whenever the IPFM or ESIM is used as
controller in an IP subsystem.
• During system turn-up
• When software on the AP has been swapped from Alternate version to Current
version.
The procedure is service affecting if the flash on the AP must be upgraded.
The procedure is not service-affecting if only the flash on the controller needs to be
upgraded.
Assumption
Procedure
...................................................................................................................................................................................................
1 From the menu bar select IP SubSystem -> IP Data -> System -> Software ->
Administration.
Result: The Software Administration window opens. The software versions
running in the IP subsystem are listed in the column labeled Current.
...................................................................................................................................................................................................
2 Determine the correct software version
IF... AND... THEN...

the required software the current and the Go to Step 3 to perform a
version is available on the alternate SW versions on software download from
controller flash the AP flash are not the the controller flash to AP
correct ones flash.
...................................................................................................................................................................................................................................
6-82 363-211-555
Alarms and trouble clearing To clear “software mismatch alarm between AP and
controller flash”
the required software the alternate SW version on Go to Step 6 to activate

version is available on the AP flash is correct but the the alternate SW on the AP.
controller flash SW version in the current
column is not the correct
one
the required software the current SW versions on perform a software
version is not available on the AP flash is correct download from server to
the controller flash the controller by following
the “Verify/Update
software load ” (p. 7-73)
procedure.
...................................................................................................................................................................................................
3 In the SW Download subtab select from the SW Type pull-down menu the applicable
AP type.
...................................................................................................................................................................................................
4 IF... THEN...
you want to download the new software to in the Download Direction field select the
all APs of that type AP type expanded with All. Then go to
Step 5.
you want to download the new software to in the Download Direction field select the
single APs only applicable AP(s). Then go to Step 5.
...................................................................................................................................................................................................
5 Click Apply.
file transfer and writing to flash is displayed. After completion the new software
version is displayed in the Alternate column for the APs selected.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
7 In the SW Activation subtab the current and alternate software versions are displayed.
Select the Slot number of the AP type to be activated or click Select All.
...................................................................................................................................................................................................
8 Click Apply.
Result: The AP reboots. After the reboot has completed, the AP(s) will run the new
software version.
...................................................................................................................................................................................................
9 Refresh the Software Administration window.

....................................................................................................................................................................................................................................
363-211-555 6-83
Alarms and trouble clearing To clear “software mismatch alarm between AP and
controller flash”
Result: The new version is displayed in the Current column.

...................................................................................................................................................................................................
10 Repeat Step 6 through Step 9 for other APs as required.

END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
6-84 363-211-555
To clear “Database corrupt” alarm (ICAP)

...................................................................................................................................................................................................................................
Purpose
The “Database corrupt” alarm indicates that the non-volatile data storage database
(NVDS) is corrupted on the specified pack.
It must be cleared because the specific pack does not provide any service in this case.
Fault Clearance Procedure

...................................................................................................................................................................................................
1 Reset the pack as described in “To reset IP pack” (p. 6-117).

Result: If the alarm is not cleared, proceed with next step.
If the alarm is cleared,
End of Steps
...................................................................................................................................................................................................
2
IF... THEN..
a backup file of the NVDS exists restore the NVDS as described in
“Database restore ” (p. 7-308)
End of Steps
no backup file exists and the pack is an proceed with next step.
AP in controlled mode
no backup file exists and the pack is an proceed with step Step 5 to initialize the
ICAP in stand-alone mode pack.
...................................................................................................................................................................................................
3 Click on any slot in the GSI to open the Pack Provisioning window and delete the
provisioning for the applicable slot.
...................................................................................................................................................................................................
4 Reprovision the slot for this pack type as described in “Provision IP AP slots” (p. 7-48)
.
Reprovision the pack as described in the “Service Activation” section for the different
AP types.
End of Steps
...................................................................................................................................................................................................
5 From the GSI menu select IP SubSystem -> IP Data -> System -> Initialize System...
...................................................................................................................................................................................................................................
363-211-555 6-85
Alarms and trouble clearing To clear “Database corrupt” alarm (ICAP)
Result: The System Initialization window opens.

...................................................................................................................................................................................................
6 Select the applicable stand-alone pack and check the Clear All Pack Configuration
radio button. Then click Apply.
Result: After confirmation the pack will be initialized. All previous provisioning is
lost.
E...................................................................................................................................................................................................
ND OF STEPS
Expected results
In the Active Alarms and Conditions window, the Database corrupt alarm is
cleared. The LED NE is off or is indicating a different alarm.
....................................................................................................................................................................................................................................
6-86 363-211-555
To clear “Uplink failure” alarm

...................................................................................................................................................................................................................................
Purpose
This procedure is used to clear alarms that are raised when a failure is detected at least
at one uplink (on IPFM/ICAP/ESIM) while carrying service. This alarm is a summary
alarm and may be caused by one or by several IPFM/ESIM uplink failures.
The alarm must be cleared because this failure may result in congestion and traffic
loss.
Note that the IPFM and the ESIM (in a LAG 200 Shelf) can be used as central
controller of the IP subsystem.
Assumption
The technician has access to information about which uplinks are required.
Flowchart
The example below shows the principle how to clear uplink failure alarm on an IPFM
controller pack.
...................................................................................................................................................................................................................................
363-211-555 6-87
Alarms and trouble clearing To clear “Uplink failure” alarm
IPFM uplink failure
Identify fault uplink
uplink no Disable the

required?
uplink
yes
Connect the uplink

no
corresponding properly connect. at
the IPFM
uplink (cable/fiber)
yes
yes
Alarm still present?
no
uplink Connect the
no
END properly connect. at corresponding
the far end
yes
yes
no
Enable the uplink
no END
corresponding enabled at the
far end?
yes
yes
no
cable/fiber
END OK?
Replace the
cable or fiber
End of Steps
....................................................................................................................................................................................................................................
6-88 363-211-555
Procedure
...................................................................................................................................................................................................
1 Identify which of the uplinks raised the alarm.
IF... THEN...
the pack is an IPFM or an ESIM from the menu bar select IP SubSystem ->
IP Data -> Equipment -> Port
Provisioning.
the pack is an ICAP from the menu bar select IP SubSystem ->
ICAP -> Ports.
...................................................................................................................................................................................................
2 From the Port pull-down menu select one port after the other and search for a port
whose Service State is In Service while the Operational State field displays Link
down. This uplink may have raised the alarm.
...................................................................................................................................................................................................
3 Check whether this uplink is a required uplink.
IF... THEN...
this uplink is not required change the Service State of this port to Out
of Service. Then go to Step 4.
this uplink is required the corresponding uplink may not be
physically (fiber or cable) properly
connected to the far end. Verify proper
connection. Then go to Step 4.
...................................................................................................................................................................................................
4 Follow the “Retrieve active alarms” (p. 7-327) GSI operation to verify if there is still
an IPFM/ICAP/ESIM uplink failure alarm present.
IF... THEN...
there is no IPFM/ICAP/ESIM uplink END OF STEPS
failure alarm anymore
there is still an IPFM/ICAP/ESIM uplink the corresponding uplink may not be
failure alarm enabled at the far end. Verify that the
uplink is enabled at the far end. Then go
to Step 5.
....................................................................................................................................................................................................................................
363-211-555 6-89
...................................................................................................................................................................................................

there is no IPFM/ICAP/ESIM uplink failure alarm END OF STEPS
anymore
there is still an the transport medium is the Rx and Tx fibers may
IPFM/ICAP/ESIM uplink fiber be interchanged. Exchange
failure alarm the Rx and Tx fibers. Then
go to Step 6.
the transport medium is The transport medium may
either fiber or cable be faulty. Replace the
cable. Then go to Step 6.
...................................................................................................................................................................................................
IF... THEN...
there is no IPFM/ICAP/ESIM uplink END OF STEPS
failure alarm anymore
there is still an IPFM/ICAP/ESIM uplink go to Step 1 and repeat this procedure for
failure alarm all other ports until no IPFM uplink
failure is raised anymore.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
6-90 363-211-555
To clear “Slot-xx unequipped” alarm

...................................................................................................................................................................................................................................
Purpose
This procedure is used to clear an alarm that indicates that a pack was removed or is
not recognized while carrying service.
The alarm must be cleared because this slot cannot provide any service.
Assumption
The technician has access to information about which pack types are required in the
individual slots.
Flowchart
Slot-xx unequipped
Pack in slot-xx no
required
yes
no Pack equipped
in slot-xx
yes
Insert requested Pack possibly Delete pack from

pack in slot xx defect. provisioning
Replace pack
Procedure
...................................................................................................................................................................................................
1 Check if a pack is required in this slot.

no pack is required in no pack is equipped follow the “Delete an IP application
this slot pack” (p. 7-312) GSI operation.
END OF STEPS
a pack is required in a pack is equipped the pack may be faulty. Replace the
this slot pack by following “Remove a
Circuit Pack ” (p. 7-11) and “Insert
a pack ” (p. 7-41).
END OF STEPS
...................................................................................................................................................................................................................................
363-211-555 6-91
Alarms and trouble clearing To clear “Slot-xx unequipped” alarm

a pack is required in no pack is equipped Insert the required pack by
this slot following “Insert a pack ” (p. 7-41)
to
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
6-92 363-211-555
To clear “Pack type mismatch” alarm

...................................................................................................................................................................................................................................
Purpose
This procedure is used to clear alarms for mismatches between installed APs and the
provisioned pack type.
The alarm must be cleared because otherwise this slot cannot provide any service.
Assumption
The technician has access to information about which pack types are required in the
individual slots.
Flowchart
Pack type mismatch, provisioned [typeA],

inserted [typeB]
no yes
Pack required
in slot xx
Pack yes
matches the required
pack type
no
Delete pack from Replace pack Delete pack type

provisioning and with the correct provisioning and
remove pack pack type provision correct
AP type
Procedure
...................................................................................................................................................................................................
1 Check if a pack is required in this slot.

no pack is required in this Remove and deprovision the
slot AP by following “IP AP
Degrowth” (p. 7-318).
END OF STEPS
...................................................................................................................................................................................................................................
363-211-555 6-93
Alarms and trouble clearing To clear “Pack type mismatch” alarm

a pack is required in this the pack does not match Replace the pack with the
slot the required pack type correct pack type by
following “Remove a Circuit
Pack ” (p. 7-11) and “Insert
a pack ” (p. 7-41) .
END OF STEPS
a pack is required in this the pack matches the the pack provisioning may
slot required pack type be wrong. Go to Step 2.
...................................................................................................................................................................................................
2 From the GSI menu bar select IP Subsystem -> IP Data -> Equipment.
Result: The Pack Provisioning window pops up.
...................................................................................................................................................................................................
3 Select the Slot Number which shall be provisioned with the correct pack type.
...................................................................................................................................................................................................
4 Click Delete.
...................................................................................................................................................................................................
5 Again select the Slot Number for the affected slot and select from the Prov. Pack
Type pull-down menu the correct pack.
...................................................................................................................................................................................................
6 Click Apply.
...................................................................................................................................................................................................
7 Follow the “Retrieve active alarms” (p. 7-327) GSI operation in order to verify that
there is no longer a mismatch alarm.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
6-94 363-211-555
To clear “NTP Synchronization failed” alarm

...................................................................................................................................................................................................................................
Purpose
This alarm indicates that the system cannot be synchronized with the signal from the
provisioned NTP server.
The alarm must be cleared because all alarming and event logging will use incorrect
time stamps.

...................................................................................................................................................................................................
1 Check the provisioning entry for the route, whether the specified IP address is correct
and complete. There might be a typo.
From the GSI menu select IP SubSystem -> System ->NTP synchronization..
Result: The NTP Synchronization window opens. The Server Info tab displays
the provisioned IP address of the NTP server.
...................................................................................................................................................................................................
2 If the routing entry related to the NTP server is wrong, modify it as required:
From the GSI menu select IP Subsystem -> System -> IP Routing.... In the panels
Static Route Table and Routing Policy verify and enter the appropriate parameters.
Result: If the routing entry has been modified, the alarm should be cleared.
Otherwise the NTP server might not be working properly. Continue with next step.
End of Steps
...................................................................................................................................................................................................
3 IF... THEN...
there is a chance to do trouble clearing on initiate it.
the NTP server
there is another NTP server that can be enter the IP address of this new NTP
used instead server instead.
there is no chance to use an NTP server manually set date and time and
de-provision the NTP server usage.
E...................................................................................................................................................................................................
ND OF STEPS
Expected results
In the Active Alarms and Conditions window, the alarm which provoked this trouble
clearing procedure is cleared. The green L/A LED on the IPFM or the green Link up
LED on the ICAP/LPZ600 lits. The appropriate FE link is established.
...................................................................................................................................................................................................................................
363-211-555 6-95
To clear V5 protocol data link faults

...................................................................................................................................................................................................................................
Purpose
This trouble clearing procedure applies to the following alarms:
• “V5 data link failed alarm - Common Control” (p. 6-19)
• “V5 data link failed alarm - PSTN” (p. 6-20)
• “V5 data link failed alarm - Protection” (p. 6-21)
• “V5 data link failed alarm - Bearer Channel Control” (p. 6-22)
• “V5 data link failed alarm - Link Control” (p. 6-23)
“V5 data link failed alarm - timeslot cessation of flags” (p. 6-24)
These alarms may be raised in an AnyMedia host terminal equipped with ICAP(s) and
indicate that no layer 2 frames for protocol data link are received for a certain time
frame.
These alarms must be cleared because
• they may impact on call processing or
• no protection switching for V5 CCs is possible or
• no link control handling is possible.

...................................................................................................................................................................................................
1 Verify the following autonomous alarm messages in the Active Alarms and
Conditions window.
IF ALARM MESSAGE OCCURS.... THEN...

V5 datalink failed - Common In V5 edition 2: No call processing for
Control ISDN calls; existing ISDN calls are
dropped.
Note that if this alarm is not cleared after
approximately one minute, a V5 interface
failed alarm will be raised.
V5 datalink failed - PSTN PSTN call processing stopped; existing
POTS calls are dropped.
V5 datalink failed - Protection no protection switching for V5 CCs is
possible, but no impact on call processing.
V5 datalink failed - Bearer no effects on existing (stable) calls, but no
Channel Control setup of new calls possible.
...................................................................................................................................................................................................................................
6-96 363-211-555
Alarms and trouble clearing To clear V5 protocol data link faults
IF ALARM MESSAGE OCCURS.... THEN...

V5 datalink failed - Link Control no link control handling is possible, but
no impact on call processing.
V5 link timeslot xy Cessation of no HDLC flags received in V5 active or
Flags error standby CCs (V5 link between ICAP
xy stands for timeslot 15, 16 or 31. (V5.2LE) and V5AN is disturbed).
...................................................................................................................................................................................................
2 Check in the Active Alarms and Conditions window for other previous active
equipment and/or facility alarms that could cause the faulty V5 protocol data link.
Result: There should be one or more alarms against the implicated V5 interface.
...................................................................................................................................................................................................
3 Verify the alarm messages.
IF... THEN...
there are one or more protocol data link go to the procedure “To clear V5 interface
error alarm messages and finally a V5 fault alarm” (p. 6-99).
interface failed alarm check if provisioning of V5 data links and
their cross connection to the appropriate
CCs and timeslot at ICAP (V5.2LE) and
V5AN side is identical.
several protocol data link error alarm go to Step 4
messages are present but no V5 interface
failed alarm
a V5 interface service degraded alarm the service degrade threshold shows a
message is present value (percentage) for service degrading
concerning the ratio of the number of
failed V5 data links and the number of
provisioned V5 data links.
End of Steps
no protocol data link error alarm messages End of Steps
are present
....................................................................................................................................................................................................................................
363-211-555 6-97
Alarms and trouble clearing To clear V5 protocol data link faults
...................................................................................................................................................................................................
4 Control the correctness of the system synchronization input reference signal by

selecting the subtab Timing Source Control in the ICAP System Turnup window
(verify the control mode, the synchronization reference sources, the state of the
synchronization reference sources and the currently active synchronization reference
source).
IF... THEN...
the active synchronization reference go to Step 5
source is okay and the protocol data link
alarm messages are not cleared
the system synchronization input reference go to the procedure “To clear
signal is not okay synchronization input failed alarm”
(p. 6-113).
...................................................................................................................................................................................................
5 Check the transmission path between ICAP (V5.2LE) and V5 access node - including
MDF and connectors - for crosstalk/noise.
...................................................................................................................................................................................................
6 Check the transportation network for degraded quality of service (for example Bit
Error Ratio).
...................................................................................................................................................................................................
7 After the check verify that the protocol data link alarm messages have been cleared,
see “Expected results” (p. 6-98)
E...................................................................................................................................................................................................
ND OF STEPS
Expected results
In the Active Alarms and Conditions window the alarm messages, which provoked
this trouble clearing procedure are cleared. The LED NE is off or is indicating a
different alarm.
System Fault
If alarm messages persist, call your local customer support.
....................................................................................................................................................................................................................................
6-98 363-211-555
To clear V5 interface fault alarm

...................................................................................................................................................................................................................................
Purpose
• “V5 interface failed alarm” (p. 6-18)
• “V5 interface identification failed alarm” (p. 6-27)
“V5 interface service degraded alarm” (p. 6-26)
• “V5 interface out of service alarm” (p. 6-28) (Customer-specific)
• “V5 link failed alarm” (p. 6-29)
• “V5 link identification failed alarm” (p. 6-30)
• “V5 link disabled alarm” (p. 6-31) (Customer-specific)
• “V5 PSTN restart failed alarm” (p. 6-25)
The “V5 interface fault” alarms may be raised in an AnyMedia system equipped with
ICAP(s). It indicates that the V5 interface/link has failed due to following causes:
• V5 interface startup has failed
• V5 links mixed up
• V5 interface/link configuration data are different between the host terminal side and
the V5 access node side
• Persistent protocol data link alarm messages were present beforehand
• V5 interface/link is administratively out of service or disabled (customer-specific).
It must be cleared because all links on this interface are lost and this will result to
traffic loss.

...................................................................................................................................................................................................
1 Verify the V5 interface/link alarm messages in the Active Alarms and Conditions
window.
IF... THEN...
persistent protocol data link alarm go to the procedure “To clear V5 protocol data
messages are present beforehand, link faults” (p. 6-96).
V5 interface failed alarm messages go to Step 2
are present,
the alarm message V5 link failed go to the procedure “To clear incoming E1
is present, signal fault alarms” (p. 6-122).
V5 interface service degraded too many V5 links have failed.
...................................................................................................................................................................................................................................
363-211-555 6-99
Alarms and trouble clearing To clear V5 interface fault alarm
IF... THEN...
the alarm message V5 interface failed alarm is raised and an
V5 PSTN restart failed is autonomous PSTN restart within the V5
present, interface startup is attempted.
Note that if POTS call processing is possible
within 5 minutes, ignore the alarm message.
...................................................................................................................................................................................................
2 Check the V5 interface/link configuration data and provisioning especially for:

• Interface ID
• Link IDs
• CC IDs
• Provisioning variant ID (currently only value 0 supported)
• CP assignments to CCs
• CC assignments to timeslots of a V5 data link
• Correlation between E1 link cabling, E1 feeder and provisioning of the
corresponding V5 data links and their cross connection to certain V5 interfaces,
especially the V5 primary link carrying the CC in timeslot 16.
...................................................................................................................................................................................................
3 CAUTION
ESD hazard
Check the E1 cabling and transportation network between the AnyMedia host system
and the V5 access node by following the complete E1 cabling path to check whether
the cabling is disconnected or the cable is broken.
Reconnect the cable or replace a broken cable.
Result: If the cabling has been reconnected or the cable has been replaced the
alarm should be cleared.
End of Steps
E...................................................................................................................................................................................................
ND OF STEPS
Expected results
In the Active Alarms and Conditions window, the V5 interface and/or V5 link failed
alarm messages are cleared. The LED NE is off or is indicating a different alarm.
....................................................................................................................................................................................................................................
6-100 363-211-555
To clear GR-303 data link fault alarms

...................................................................................................................................................................................................................................
Purpose
This trouble clearing procedure is used for trouble analysis and clearing and applies to
the following alarms:
• “GR-303 data link failed alarms - TMC/EOC” (p. 6-33)
• “GR-303 far end major or critical alarm” (p. 6-34)
• “GR-303 far end minor alarm” (p. 6-35)
The TMC data link handles dynamic call setup and disconnect information. The EOC
data link handles OAM&P information for the GR-303 interface.
These alarms may be raised in an AnyMedia host terminal equipped with ICAP(s) due
to faulty DS1s associated with TMC/EOC data links or unprotected IODS1 fault in an
RT.
They alarms must be cleared because the dynamic call set-up handling and disconnect
information for the RT may interrupted or the OAM&P information for the GR-303
interface is lost.

...................................................................................................................................................................................................
1 Verify the alarm messages in the Active Alarms and Conditions window. Check for
other active equipment and/or facility alarms that could cause the faulty TMC and/or
EOC data link.
...................................................................................................................................................................................................
2 Verify that the visual indications agree with the active equipment and/or facility alarm
messages:
Possible causes Visual Indication Action

DS1 signal faults The CLF LED Go to “To clear DS1 input signal fault
(LOS, LOF, AIS, lights on one of alarms” (p. 6-126). Then go to Step 3.
YEL or BERL) the IODS1s.
Unprotected The FAULT LED Remove and then (re)insert the suspected
IODS1 missing, light on one of IODS1 pack. For replacement go to Step 7 in
failed, or the IODS1. the procedure “To clear DS1 input signal fault
incompatible or alarms” (p. 6-126).
The IODS1 is Then go to Step 3.
absent.
...................................................................................................................................................................................................................................
363-211-555 6-101
Alarms and trouble clearing To clear GR-303 data link fault alarms
Possible causes Visual Indication Action

Protected ICAP The F/A LED Go to “To clear Required pack missing alarm”
missing, failed, or lights red on (p. 6-118). Then go to Step 3.
incompatible standby ICAP.
or
The standby ICAP
is absent.
Aggregated TMC, Data link Check DS1 feeder provisioning or
EOC data link protected: The mis-connection between AnyMedia host and
failed yellow LEDs RT.
MJ/MN and NE on Go to “To clear DS1 input signal fault
the impacted alarms” (p. 6-126). Then go to Step 3.
ICAP are on.
Data link
unprotected: The
red LED CR and
the yellow LED
NE on the
impacted ICAP
are on.
...................................................................................................................................................................................................
3 Verify the TMC and/or EOC data link alarm(s) as follows:

Standard system response Any alarm indications of data link faults are cleared,
see Step 2.
Standard system fault If the alarm is not cleared, the problem may be outside the
AnyMedia host and RT. Call your organization for assistance.
E...................................................................................................................................................................................................
ND OF STEPS
Expected results
clearing procedure is cleared. The impacted LED F/A, MJ/MN, CR, or NE on the ICAP
is off or is indicating a different alarm.
....................................................................................................................................................................................................................................
6-102 363-211-555
To clear RT alarms caused by wrong cabling

...................................................................................................................................................................................................................................
Purpose
• “RT link identification failed alarm” (p. 6-37)
• “RT link layer 2 failed alarm” (p. 6-39)
• “RT link layer 3 failed alarm” (p. 6-40)
These alarms may be raised in ICAPs, primarily after installation or other cabling
activities.
The alarms must be cleared because they may lead to congestion on the other links up
to a complete loss of the RT interface.

...................................................................................................................................................................................................
1 CAUTION
ESD hazard
Follow the complete E1 cabling path to check whether there is a mismatch in E1

cabling. Interface cabling may be interchanged or the E1 cable may be wired to a
wrong interface.
Change the cabling as required.
Result: If the cabling has been changed the alarm should be cleared. Otherwise
continue with next step.
End of Steps
...................................................................................................................................................................................................
2 Set the remote terminal link to out of service to provoke a “Loss of Signal” alarm at
the far end. If this alarm at the far end will be raised for another feeder than the
expected one, then there is a E1 cabling mismatch at this E1 feeder.
Correct the cabling and enable the remote terminal link again by setting it to in
service.
E...................................................................................................................................................................................................
ND OF STEPS
...................................................................................................................................................................................................................................
363-211-555 6-103
Alarms and trouble clearing To clear RT alarms caused by wrong cabling
Expected results
clearing procedure is cleared. The LED NE is off or is indicating a different alarm.
....................................................................................................................................................................................................................................
6-104 363-211-555
To clear “RT link interface identification failed” alarm

...................................................................................................................................................................................................................................
Purpose
The “RT link interface identification failed” alarm may be raised in an AnyMedia host
terminal equipped with ICAP(s).
It must be cleared because the remote terminal identification procedure failed due to a
mismatch of the interface identification string.
Assumptions
A PC that is installed with the GSI/EMS software.
The Commands and Procedures for narrowband services with TDM COMDAC
(363-211-119).

...................................................................................................................................................................................................
1 Check the consistency of the interface identification strings as follows:

• On the RT-side with the RTRV-HTI command.
• On the ICAP-side from the menu bar select IP SubSystem -> ICAP -> Feeders &
TDM Network....
Result: The ICAP System Turnup window opens.
...................................................................................................................................................................................................
2 Select RT-TDM subtab for checking the ID strings.

...................................................................................................................................................................................................
3 Especially take care of the capitalization of the ID string. The string is case-sensitive!
If strings seem to match, re-provisioning the strings at both sides with taking especially
care of upper and lower case characters.
IF... THEN...
the interface identification strings don’t verify the ID string
match • for the ICAP-side via the subtab
Identification String
or
• for the RT-side, see chapter 5, section
“Remote subscriber services” and the
procedure “SA-6220 Host terminal
interface in a remote terminal” in the
Commands and Procedures for
narrowband services with TDM
COMDAC.
the interface identification strings match END OF STEPS
...................................................................................................................................................................................................................................
363-211-555 6-105
Alarms and trouble clearing To clear “RT link interface identification failed” alarm
E...................................................................................................................................................................................................
ND OF STEPS
Expected results
In the Active Alarms and Conditions window, the
RT link interface identification failed alarm is cleared. The LED NE is off or
is indicating a different alarm.
....................................................................................................................................................................................................................................
6-106 363-211-555
To clear “ROC provisioning mismatch detected” alarm

...................................................................................................................................................................................................................................
Purpose
The “ROC provisioning mismatch detected” alarm may be raised in an AnyMedia host
terminal equipped with ICAP(s), primarily after system turn up.
It must be cleared because it leads to a complete RT interface failure.
Assumptions
(363-211-119).

...................................................................................................................................................................................................
1 In the engineering work order check whether a ROC is required on the applicable
interface.
...................................................................................................................................................................................................
2 Check the provisioning on the ICAP side:

If the ICAP System Turnup window is not yet open, from the menu bar select IP
Subsystem -> ICAP -> System -> General
...................................................................................................................................................................................................
3 Select the Feeder tab.

...................................................................................................................................................................................................
4 Go to tab RT-TDM, check via subtab Interface whether the field IP Interface Addr:
is correctly set (either to none or to a roc) according to the work order.
...................................................................................................................................................................................................
5 Check the provisioning on the RT side:

Connect to the RT and perform the RTRV-HTI operation to retrieve the logical host
interfaces. Check whether the IP interface (IPIF): is set to none or to a roc.
Result: There might be a provisioning mismatch between the ICAP and the RT.
...................................................................................................................................................................................................
6 Correct the provisioning mismatch on the RT or on the ICAP, depending on where it is

wrong.
Be aware that this will require additional provisioning steps as described for the ICAP
in “Activate service over ICAPs” or for the RT in “SA-6187 ROC via nailed-up
remote link timeslot and leased line link transport in host terminal” and “SA-6188
...................................................................................................................................................................................................................................
363-211-555 6-107
Alarms and trouble clearing To clear “ROC provisioning mismatch detected” alarm
ROC via nailed-up remote link timeslot and IP-routed transport in host terminal”
in the Commands and Procedures for Narrowband Services.
E...................................................................................................................................................................................................
ND OF STEPS
Expected results
ROC provisioning mismatch detected alarm is cleared. The LED NE is off or is
indicating a different alarm.
....................................................................................................................................................................................................................................
6-108 363-211-555
To clear “RT interface failed” alarm

...................................................................................................................................................................................................................................
Purpose
The “RT interface fault” alarm may be raised in an AnyMedia host terminal equipped
with ICAP(s). It indicates that the complete remote interface is not operational.
It must be cleared because all links on this interface are lost and this will result in
traffic loss.

...................................................................................................................................................................................................
1 CAUTION
ESD hazard
Follow the complete E1 cabling path to check whether the cabling is disconnected or
the cable is broken.
Reconnect the appropriate cable or replace all cables.
...................................................................................................................................................................................................
2 If the alarm still exists connect to the RT and check whether the administrative state of
the HT interface and of the RT links is in service or whether an identifier mismatch
has occur.
Result: If the cabling is correct and the administrative state of HT interface and RT
links is set to in service, the alarm should be cleared.
E...................................................................................................................................................................................................
ND OF STEPS
Expected results
In the Active Alarms and Conditions window, the RT interface fault alarm is
cleared. The LED NE is off or is indicating a different alarm.
...................................................................................................................................................................................................................................
363-211-555 6-109
To clear “RT interface service degraded” alarm

...................................................................................................................................................................................................................................
Purpose
This alarm may be raised in an AnyMedia host terminal equipped with ICAP(s). It will
be raised together with other E1 failures.
The alarm must be cleared because the service may be further degraded on the RT
interface up to a complete loss of the RT interface.

...................................................................................................................................................................................................
1 In the Active Alarms and Conditions window, check for RT link or E1 failures that
are related to this RT interface.
...................................................................................................................................................................................................
2 Follow the related trouble clearing procedures for these RT link or E1 failures.
E...................................................................................................................................................................................................
ND OF STEPS
Expected results
When the related E1 failures are cleared, the “RT interface service degraded” alarm
which provoked this trouble clearing procedure is cleared. The LED NE is off or is
...................................................................................................................................................................................................................................
6-110 363-211-555
To clear “RT interface control data link failed” alarm

...................................................................................................................................................................................................................................
Purpose
The “RT interface control data link failed” alarm may be raised in an AnyMedia host
terminal equipped with ICAP(s).
It must be cleared because the signaling control channel to the RT is lost on a once
operational RT interface.
Assumptions
(363-211-119).

This alarm should never persist permanently as internal counter measures take place to
re-establish the data link again. If it persists permanently, then proceed as follows:
...................................................................................................................................................................................................
1 On the ICAP connect to the applicable RT interface, set it administratively out of

service and then set it back to in service again.
IF... THEN...
the alarm has cleared END OF STEPS
the alarm has not cleared go to next step.
...................................................................................................................................................................................................
2 On the applicable RT connect to the HT interface, use the ED-RTI command to set it
administratively out of service and then set it back to in service again.
IF... THEN...
the alarm has cleared END OF STEPS
the alarm has not cleared Hardware may be corrupt. First replace
the impacted ICAP and if that does not
help, replace the COMDAC.
NOTE: For COMDAC replacement in
simplex and duplex mode, see software
upgrade procedures SWM-6010.....SWM-
6030 in the Commands and Procedures for
narrowband services with TDM COMDAC.
E...................................................................................................................................................................................................
ND OF STEPS
...................................................................................................................................................................................................................................
363-211-555 6-111
Alarms and trouble clearing To clear “RT interface control data link failed” alarm
Expected results
RT interface control data link failed alarm is cleared. The LED NE is off or is
....................................................................................................................................................................................................................................
6-112 363-211-555
To clear synchronization input failed alarm

...................................................................................................................................................................................................................................
Purpose
This alarm is currently used for the following ICAP synchronization sources:
• Physical ports (feeder)
• Backplane (1 or 2)
• COMDAC
• AFM
The synchronization input failed alarm must be cleared immediately because one (or
both) synchronization input(s) has (have) failed and the telephony functions (calls) are
disturbed.
Assumptions
• The system is in normal operation mode (that is Sync Control Mode = External)
when the fault condition is detected.
• The system is not in free-running mode.
Procedure
...................................................................................................................................................................................................
1 Verify the currently active synchronization reference source from which the ICAP
timing is derived by selecting the subtab Timing source Control in the ICAP System
Turnup window.
IF... THEN...
active synchronization source is check the feeder E1/DS1 signal alarms.
primary/secondary with appropriate If one (or both) synchronization input(s) has
range fdr-1... fdr-8, (have) failed, which is a result of the
implicated E1/DS1 LOS, LOF, BER or AIS,
then go to the procedure “To clear incoming
E1 signal fault alarms” (p. 6-122) or “To
clear DS1 input signal fault alarms”
(p. 6-126).
Then go to Step 2
...................................................................................................................................................................................................................................
363-211-555 6-113
Alarms and trouble clearing To clear synchronization input failed alarm
IF... THEN...
active synchronization source is verify the pack which should output a clock
primary/secondary with appropriate signal to the bpsync1, bpsync2 lines on the
range bpsnc-1 or bpsnc-2, backplane.
If one (or both) clock signal(s) has (have)
failed, check the signal and repair if
necessary the clock source. Note that the
system switches temporarily to free-running,
see “System free running synchronization
failed alarm” (p. 6-47).
Then go to Step 2
active external synchronization source is check the AFM or COMDAC.
primary/secondary with appropriate If the afm-1 alarm is present, verify the
afm-1 or core-1, AFM alarms, see procedure “TCP-510d
IP-AFM Faults” in the Commands and
Procedures for ATM xDSL services
If the core-1 alarm is present, verify the
COMDAC alarms, see procedure “TCP-6710
COMDAC faults” in the Commands and
Procedures for narrowband services with
TDM COMDAC.
Then go to Step 2
...................................................................................................................................................................................................
2 Verify that the appropriate alarm messages are cleared, see “Expected results”
(p. 6-114) .
...................................................................................................................................................................................................
3 Control the correctness of the system synchronization by checking the Control Mode in
the subtab Timing source Control window. The active synchronization must not be
free-running.
E...................................................................................................................................................................................................
ND OF STEPS
Expected results
In the Active Alarms and Conditions window, the appropriate
Synchronization input failed alarms are cleared. The LED NE is off or is
....................................................................................................................................................................................................................................
6-114 363-211-555
To clear “Software program version mismatch” alarm on ICAP

...................................................................................................................................................................................................................................
Purpose
This procedure is used to clear an alarm that is raised for ICAPs in duplex mode due
to different software on the standby ICAP and the active ICAP.
• During system turn-up when two ICAPs with different software versions are
inserted.
• When upgrading a running system from simplex to duplex ICAP mode.
In stand-alone mode this alarm will only be raised, when the Autocopy function which
is activated by default has been deactivated for some reason.
The alarm must be cleared because the ICAP and the subtending systems are not
protected in this condition.
The procedure is not service-affecting.
Assumption
• Duplex operation mode is provisioned.
Procedure
...................................................................................................................................................................................................
1 IF... THEN...
the ICAPs run in stand-alone mode proceed with next step
the ICAPs run in controlled mode download and activate the required
software version as described in “Software
download/activation and database
backup/restore for stand-alone AP(s)”
(p. 7-340).
END OF STEPS
...................................................................................................................................................................................................
2 On the GSI click on one of the ICAPs in the protection group.

...................................................................................................................................................................................................
3 Select the Duplex tab.

...................................................................................................................................................................................................
4 In the Auto Copy Mode pull-down menu select Enabled then click Apply.
...................................................................................................................................................................................................................................
363-211-555 6-115
Alarms and trouble clearing To clear “Software program version mismatch” alarm on
ICAP
Result: The software version of the active ICAP is copied to the standby ICAP.
The ICAP reboots. After the reboot has completed, the standby ICAP will run the
new software version.
The operational state of the standby ICAP is now displayed in the ICAP System
Turnup window as ReadyToProtect.
E...................................................................................................................................................................................................
ND OF STEPS
Expected results
Software program version mismatch alarm is cleared. The LEDs F/A are off or are
....................................................................................................................................................................................................................................
6-116 363-211-555
To reset IP pack
...................................................................................................................................................................................................................................
Purpose
This procedure is used for trouble clearing on a pack when other recommended
procedures did not solve the problem.
Apart of trouble clearing, a reset of an ICAP is always required and requested by the
system when IP address, VLAN, H.248 or MGCP provisioning data have been changed
in the Network tab.
Important! Do not unintentionally reset an IPFM in simplex mode or an AP in
stand-alone mode because you will temporarily loose connection and service.
A reset of the active IPFM in duplex mode results in a side switch before the reset.
Procedure
...................................................................................................................................................................................................
1 On the GSI click on any slot.

Result: The Pack Provisioning window opens.
...................................................................................................................................................................................................
2 In the table select the pack to reboot and click Reset.

Result: Pack software is reinitialized using configuration data saved on the IPFM
(in controlled mode). The pack disappears from the GSI and is displayed again
when the reset has been completed.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
363-211-555 6-117
To clear “Required pack missing” alarm

...................................................................................................................................................................................................................................
Purpose
This procedure is used to clear the “Required pack missing” alarm on an ICAP in
duplex mode. The alarm indicates that the standby ICAP is faulty or was removed or it
is in a pack reset.
The alarm must be cleared because protection is not effective anymore.
Assumption
It is assumed that protection is required and therefore a migration to simplex mode is
not an acceptable option.
Procedure
...................................................................................................................................................................................................
1 Check whether the standby ICAP is in a reset.

From the GSI menu select IP SubSystem -> IP Data -> Fault -> Event Log.
Result: The Event Log window opens. If there is no entry that indicates that the
ICAP is in a reset, proceed with next step.
If the ICAP is in a reset the alarm will disappear as soon as the reset has
completed.
End of Steps
...................................................................................................................................................................................................
2 CAUTION
ESD hazard
IF... THEN...
an ICAP is equipped in the slot the pack may be faulty. Replace the ICAP by
following “Remove a Circuit Pack ” (p. 7-11) and
“Insert a pack ” (p. 7-41) .
END OF STEPS
no ICAP is equipped in the slot Insert an ICAP by following “Insert a pack ”
(p. 7-41)
...................................................................................................................................................................................................................................
6-118 363-211-555
Alarms and trouble clearing To clear “Required pack missing” alarm
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 6-119
To clear “Required pack mismatch” alarm

...................................................................................................................................................................................................................................
Purpose
This procedure is used for trouble clearing when the “Required pack mismatch alarm”
is raised for ICAPs in duplex mode. The alarm indicates that the hardware of the two
ICAPs is not compatible.
The alarm must be cleared because traffic cannot be switched from the active ICAP to
the standby ICAP, that means, no protection is effective.
Important! Do not replace the active ICAP because this will interrupt service on
all connected E1/DS1 lines.
Background
Two packs are compatible when the interchangeability code (ICC) is compatible.
The ICC is printed on the top of the faceplate (for example S1:1). Only packs whose
ICCs are the same on the first position are compatible (for example S1:1 is compatible
to S1:2 but not to S2:1).
Procedure
The standby ICAP has to be replaced by an ICAP which is compatible to the active
ICAP.
...................................................................................................................................................................................................
1 Check the ICC of the active ICAP and look for another ICAP with a compatible ICC
which can be used to replace the standby ICAP.
...................................................................................................................................................................................................
2 If the ICAPs run in stand-alone mode, disconnect the LAN crossover cable from the
FE2 ports of both ICAPs.
...................................................................................................................................................................................................
3 Remove the standby ICAP.

...................................................................................................................................................................................................
4 Insert the new standby ICAP.

...................................................................................................................................................................................................
5 If the ICAPs run in stand-alone mode, reconnect the LAN crossover cable to the FE2
ports of both ICAPs.
E...................................................................................................................................................................................................
ND OF STEPS
...................................................................................................................................................................................................................................
6-120 363-211-555
Alarms and trouble clearing To clear “Required pack mismatch” alarm
Expected results
clearing procedure is cleared. The LED FAULT is off or is indicating a different alarm.
....................................................................................................................................................................................................................................
363-211-555 6-121
To clear incoming E1 signal fault alarms

...................................................................................................................................................................................................................................
Purpose
• “AIS detected alarm” (p. 6-57)
• “Incoming E1 signal FE degraded alarm” (p. 6-58)
• “Incoming E1 signal near end degraded alarm” (p. 6-59)
• “Incoming E1 signal failed alarm” (p. 6-60)
• “Incoming E1 signal LOF alarm” (p. 6-61)
• “Incoming E1 signal LOS alarm” (p. 6-62)
• “Remote alarm indication received alarm” (p. 6-63)
Note that the feeder protocol RT_TDM is predefined by the customer key code (CKC).
These alarms may be raised in an AnyMedia system equipped with ICAP(s) due to
faulty E1 link connection(s). The E1 physical feeder ports are E1 circuits that are used
to provide the E1 link connections. The circuitry for each E1 port is located at the
ICAP. The E1 feeder numbers AP-1-{slot #}-{feeder port #} are used to identify these
E1 physical ports for reporting E1 signal faults.
They alarms must be cleared because they may lead to crosstalk or excessive noise on
the E1 links, up to a complete loss of the E1 link connections.

...................................................................................................................................................................................................
1 Check the operational status of the individual E1 links:

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

...................................................................................................................................................................................................
3 In the Feeder Config subtab, conduct a Loopback Action on the appropriate TDM
feeder towards to the access node (AN) or RT.
Note that the E1 loopbacks are executed by using the values operate and release.
...................................................................................................................................................................................................................................
6-122 363-211-555
Alarms and trouble clearing To clear incoming E1 signal fault alarms
...................................................................................................................................................................................................
4 Verify the E1 loopback test results.
IF... THEN...
the E1 line loopback test result is good the problem is most likely to be at the
ICAP system.
the E1 line loopback test fails the problem could be at the far end
[IO_E1(P)], the ICAP system, or at the
interface between the far end [IO_E1(P)]
and the ICAP system.
Check the following items if the loopback
test fails:
• If all of the faulted E1s are carried by
the same IO_E1(P) pack, the problem
could be at the input to the pack;
indicated by its FAULT LED lighting.
• Otherwise, the problem could be at the
interface between the far end
[IO_E1(P)] and the ICAP system.
...................................................................................................................................................................................................
5 Visual check of the E1 link connections.
IF... THEN...
the 120Ω / 75Ω termination on the E1 go to Step 6.
feeder port is as specified, the CRC4 is
active at both sides, and the faulty E1 link
connection problem is still present
the problem is not at the E1 link the feeder port may be suspect. Go to
connection Step 7
...................................................................................................................................................................................................
6 Verify the prior record of faults with the appropriate alarm messages.
IF... THEN...
there is a prior record of faults reported go to Step 8
on this pack
there is no prior record of faults reported go to Step 7
on this pack
....................................................................................................................................................................................................................................
363-211-555 6-123
...................................................................................................................................................................................................
7 CAUTION
ESD hazard
Remove and then reinsert the ICAP: With the latch in the open position, slide the pack
in until the top portion of the upper latch is behind the upper lip of the shelf. Lock the
pack in position by pressing firmly on the rounded indentation on the top latch until it
clicks into place.
Result: Upon power-up, all LEDs on the ICAP light for a short interval, followed
by a F/A (Fail/Active) LED flashing at a rate of 1 Hz during self-initialization.
After the self-initialization the green LED F/A (Active) is on. Go to “Expected
results” (p. 6-125).
At a System Fault: Go to Step 8
...................................................................................................................................................................................................
8 Remove the faulty ICAP and insert a new ICAP (see Step 7).
Result: Upon power-up, all LEDs on the ICAP light for a short interval, followed
by a F/A (Fail/Active) LED flashing at a rate of 1 Hz during self-initialization.
After the self-initialization the green LED F/A (Active) is on.
At a System Fault: Repeat Step 8.
...................................................................................................................................................................................................
9 Select
• in the tab RT-TDM, subtab Interface and verify that the Operational Status of the
appropriate RT-TDM interface is Up.
or
• in the tab V5 Network, subtab Interface and verify that the Operational Status of
the appropriate V5 interface is Up.
...................................................................................................................................................................................................
10 Select
• in the tab RT-TDM, subtab Links and verify that the Operational Status of the
appropriate RT-TDM links are Up.
or
• select in the tab V5 Network, subtab Links and verify that the Operational Status
of the appropriate V5 links are Up.
....................................................................................................................................................................................................................................
6-124 363-211-555
...................................................................................................................................................................................................
11 Make sure that all parameters of an interface/link are properly provisioned before
Administration Status is set on Enabled.
E...................................................................................................................................................................................................
ND OF STEPS
Expected results
clearing procedure is cleared. The LED NE on the ICAP is off or is indicating a
different alarm.
....................................................................................................................................................................................................................................
363-211-555 6-125
To clear DS1 input signal fault alarms

...................................................................................................................................................................................................................................
Purpose
• “AIS detected alarm” (p. 6-65)
• “Incoming DS1 signal degraded alarm” (p. 6-66)
• “Incoming DS1 signal failed alarm” (p. 6-67)
• “Yellow alarm received” (p. 6-68)
• “Incoming DS1 signal LOF alarm” (p. 6-69)
• “Incoming DS1 signal LOS alarm” (p. 6-70)
Note that the feeder protocol GR303 is predefined by the customer key code (CKC).
These alarms may be raised in an AnyMedia host terminal equipped with ICAP(s) due
to faulty DS1 link connection(s) to the RT.
They alarms must be cleared because they may lead to crosstalk or excessive noise on
the DS1 links, up to a complete loss of the DS1 link connections to the RT.

...................................................................................................................................................................................................
1 Check the operational status of the individual E1 links:

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

...................................................................................................................................................................................................
3 In the Feeder Config subtab, conduct a Loopback Action on the appropriate DS1
feeder towards to the RT.
Note that the DS1 loopbacks are executed by using the values operate and release.
...................................................................................................................................................................................................
4 Verify the DS1 loopback test results.
IF... THEN...
the DS1 loopback test result is good, the problem is most likely to be at the
ICAP system, provided that
DS1-provisioned parameters agree with
required service.
...................................................................................................................................................................................................................................
6-126 363-211-555
Alarms and trouble clearing To clear DS1 input signal fault alarms
IF... THEN...
the DS1 loopback test fails, the problem could be at the far end
(IODS1 pack), the ICAP system, or at the
interface between the far end (IODS1) and
the ICAP system.
Check the following items if the loopback
test fails:
• If the AIS detected alarm is received
from the far end, the problem is at the
far end.
• If all of the faulted DS1s are carried
by the same IODS1 pack, the problem
could be at the input to the pack;
indicated by its FAULT LED lighting.
• Otherwise, the problem could be at the
interface between the far end (IODS1)
and the ICAP system.
...................................................................................................................................................................................................
5 Visual check of the DS1 feeder connections. If any connector is loose, secure the
connector.
IF... THEN...
the faulty DS1 feeder connection problem go to Step 6.
is still present
the problem is not at the DS1 feeder the IODS1 pack may be suspect. Go to
connection Step 7
...................................................................................................................................................................................................
6 Verify the prior record of faults with the appropriate alarm messages in the Active
Alarms and Conditions window.
IF... THEN...
there is a prior record of faults reported go to Step 8
on this pack,
there is no prior record of faults reported go to Step 7
on this pack,
....................................................................................................................................................................................................................................
363-211-555 6-127
...................................................................................................................................................................................................
7 CAUTION
ESD hazard
Dispatch to the RT site immediately. Remove and then reinsert the suspected IODS1
pack: With the latch in the open position, slide the pack in until the top portion of the
upper latch is behind the upper lip of the shelf. Lock the pack in position by pressing
firmly on the rounded indentation on the top latch until it clicks into place.
Result: Upon power-up, all LEDs on the IODS1 pack light for a short interval,
followed by a FAULT LED flashing at a rate of 1 Hz during self-initialization.
After the self-initialization the ACTIVE LED (green) is on and the FAULT LED
extinguishes. Self-initialization lasts no more than three minutes. Go to “Expected
results” (p. 6-125).
System Fault: Go to Step 8
...................................................................................................................................................................................................
8 Remove the faulty IODS1 pack and insert a new IODS1 pack (replacement procedure,
see Step 7).
Result: Upon power-up, all LEDs on the IODS1 pack light for a short interval,
followed by a FAULT LED flashing at a rate of 1 Hz during self-initialization.
After the self-initialization the ACTIVE LED (green) is on and the FAULT LED
extinguishes. Self-initialization lasts no more than three minutes.
System Fault: Repeat Step 8.
...................................................................................................................................................................................................
9 Select in the tab GR303, subtab Interface and verify that the Operational Status of the
appropriate GR303 interface is restored Up.
...................................................................................................................................................................................................
10 Make sure that all parameters of an interface/link are properly provisioned before
Primary State is set on Enabled.
...................................................................................................................................................................................................
11 Select in the tab GR303, subtab Links and verify that the Secondary State of the
appropriate GR303 link is set on None.
E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
6-128 363-211-555
Expected results
clearing procedure is cleared. The LED FE on the ICAP is off or is indicating a
different alarm.
....................................................................................................................................................................................................................................
363-211-555 6-129
To clear “Tip/Ring cable (cable <x>) disconnect” alarm

...................................................................................................................................................................................................................................
Purpose
The following procedure describes steps that are recommended for trouble clearing of
a/b (tip/ring) cable disconnects on the VoIP AP LPZ602.
The alarm must be cleared because the call traffic to half of the subscribers is
disturbed.
Assumptions
A flashlight (torch) for checking connector pin(s).
A screwdriver.
Note that the connector pin(s) may be field repairable. If not, the AP with the specified
connector(s) must be replaced, and the defective AP must be returned to the factory for
repair.
(363-211-119)
Background
The VoIP AP LPZ602 provides the capability to monitor the cable connection interface.
The connectors on the LPZ602 faceplate are arranged as follows:
• POTS connector P1 for subscriber lines 1 to 32 (lower connector)
The related alarm message is possible tip/ring cable (cable 1) disconnect.
• POTS connector P2 for subscriber lines 33 to 64 (upper connector)
The related alarm message is possible tip/ring cable (cable 2) disconnect.

...................................................................................................................................................................................................
1 CAUTION
ESD hazard
Dispatch to the site and verify that the tip/ring cable is disconnected, missing,
suspected or loosely connected to the faceplate of the implicated AP.
...................................................................................................................................................................................................
2 From the GSI menu bar select IP SubSystem -> VoIP ->System... or left-click the
front of the AP that you want to check.
...................................................................................................................................................................................................................................
6-130 363-211-555
Alarms and trouble clearing To clear “Tip/Ring cable (cable <x>) disconnect” alarm
Result: The VoIP System Turnup window opens.

...................................................................................................................................................................................................
3 In the General tab check the following options of the specified AP:
• Tip&Ring Cable
The following values of the cable status can reported:
– present indicates that the cable (at the LPZ602 both cables) is/are properly
connected.
– missing indicates that the cable (at the LPZ602 the cable for ports 1-32) is not
properly connected.
The following values are only applicable for the LPZ602:
– missing-2nd indicates that the cable for the ports 33-64 is not properly
connected while the cable for ports 1-32 is properly connected.
– missing-both indicates that both cables for the ports 1-32 and 33-64 are not
properly connected.
Then go to Step 4.
...................................................................................................................................................................................................
4 Check and repair as follows:

• Reconnect the tip/ring cable securely
or
• fix the AP connector screws tightly
or
• install a new tip/ring cable per the installation instructions, for the wiring refer to
the procedure “Wiring for VoIP APs” (p. 7-106).
Continue with next step.
...................................................................................................................................................................................................
5 Verify the alarm message(s).

IF... THEN...
the alarm message is not cleared, go to Step 4.
the alarm message persists after step 4 is the VoIP AP LPZ602 may be suspect. Go
repeated, to step 3 of the procedure “TCP-6735
Application pack faults” in the Commands
and Procedures for narrowband services
with TDM COMDAC.
E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
363-211-555 6-131
Alarms and trouble clearing To clear “Tip/Ring cable (cable <x>) disconnect” alarm
Expected results
clearing procedure is cleared. The LED FAULT on the LPZ602 is off or is indicating a
different alarm.
....................................................................................................................................................................................................................................
6-132 363-211-555
To clear “Ringing source failed” alarm

...................................................................................................................................................................................................................................
Purpose
This procedure provides instructions to check the internal or external ringing sources if
the ringing voltages are not present on the ringing busses.
The alarm must be cleared because no dial-up to the subscriber possible.
Assumptions
A digital multimeter (DMM), for example Tek DM 254.
The appropriate ringing generator packs (RGPs) or ringing generator units (RGUs)
related to the shelf types (e.g. LAG 1900, LAG 4300).
(363-211-119).
The appropriate Installation Manual.
Background
The ringing voltage of the AnyMedia System includes engineering for the following
principles:
• Internal ringing source
• External ringing source.
The COMDAC monitors the internal and external ringing source input.

...................................................................................................................................................................................................
1 CAUTION
ESD hazard
Determine the shelf type and verify which kind of ringing source is connected.
...................................................................................................................................................................................................................................
363-211-555 6-133
Alarms and trouble clearing To clear “Ringing source failed” alarm
...................................................................................................................................................................................................
2 Allocate the alarm message Ringing source failed to the pack and the shelf type.
IF... THEN...
the alarm message applies to the LPZ60x go to one of the following procedures in
located in a LAG 4300 shelf, LAG 1900 the Commands and Procedures for
shelf or ETSI V5 shelf narrowband services with TDM
COMDAC:
• “TCP-6821 AnyMedia LAG 4300
System ringing source failed”
• “TCP-6822 AnyMedia LAG 1900
System ringing source failed”
• “TCP-6823 AnyMedia ETSI V5 Shelf
ringing source failed”
E...................................................................................................................................................................................................
ND OF STEPS
Expected results
clearing procedure is cleared. The LED FAULT on the LPZ60x is off or is indicating a
different alarm.
....................................................................................................................................................................................................................................
6-134 363-211-555
To clear “Media gateway controller not reachable” or

Proxyhost alarm
...................................................................................................................................................................................................................................
Purpose
This alarm indicates that the provisioned media gateway controller which applies to
H.248 and to MGC protocol or the proxy host which applies to SIP control protocol
cannot be reached.
The alarm must be cleared because no service is provided in this case.
Background
The control protocol is fixed with setting the customer key code.

Check the provisioning entries for the media gateway controller (for H.248 and MGCP
or the proxy host (for SIP).
...................................................................................................................................................................................................
1
IF... THEN...
the connection was never established follow Step 2 to double-check the ICAP
before, provisioning regarding
• MGC/SIP switch provisioning
• Routing entries.
the connection could be established go to Step 5.
before, but failed now
...................................................................................................................................................................................................
2
IF... THEN...
the VoIP interface is on an ICAP, on the GSI screen click on the ICAP to
open the ICAP System Turnup window. Go
to next step.
the VoIP interface is on an LPZ602, select IP SubSystem -> VoIP ->System... to
open the VoIP System Turnup window. Go
to next step.
...................................................................................................................................................................................................
3 Select the Network tab and then the subtab for the control protocol.
...................................................................................................................................................................................................................................
363-211-555 6-135
Alarms and trouble clearing To clear “Media gateway controller not reachable” or
Proxyhost alarm
...................................................................................................................................................................................................
4 Verify the correct settings for

• MGC/SIP switch provisioning
• Routing entries.
Result: If the entries have been modified, the alarm should be cleared. Otherwise
the failure cause is outside the AnyMedia Access System. Continue with next step.
...................................................................................................................................................................................................
5 Double-check the following in the network:

• The next hop router (default gateway)
• MGC/SIP switch host
• Outbound proxy host
• Network routing.
E...................................................................................................................................................................................................
ND OF STEPS
Expected results
clearing procedure is cleared. The LED FAULT (or F/A on a stand-alone ICAP) is off
or is indicating a different alarm.
....................................................................................................................................................................................................................................
6-136 363-211-555
To clear VoIP port protection alarm

...................................................................................................................................................................................................................................
Purpose
This procedure is used to clear an alarm that is raised when a VoIP port protection is
set up, but the protection path cannot be established due to failures of the involved
equipment.
The alarm must be cleared because the protection for this port will not be effective
anymore.
Assumption
The technician has access to information about which port is to be protected and which
is used as protecting port.
Procedure
...................................................................................................................................................................................................
1 Look for an VoIP port protection event message in the Active Alarms and Conditions
window. The address identifier of this notification indicates the module and port id of
the protecting port. Maybe there is already a 1:N port protection provisioned on a
different port.
...................................................................................................................................................................................................
2 Check if the provisioned 1:N port protection is the correct one.
IF... THEN...
the provisioned 1:N port protection is the • check in configuration equipped with
correct one and the only one LPZ600 whether COMDAC and CIU
are equipped
• check the protecting LPZ600 or
LPZ602 for pack faults.
the provisioned 1:N port protection is not the specified protecting port is not located
the correct one but the only one on the LPZ60x. Follow “Deactivate VoIP
AP 1:N port protection” (p. 7-310) to stop
the current port protection. Then follow
“Activate VoIP AP 1:N port protection”
(p. 7-294) in order to provision the correct
protecting and the correct protected port.
more than one 1:N port protections have follow “Deactivate VoIP AP 1:N port
been provisioned protection” (p. 7-310) to stop the port
protections that will not be used.
...................................................................................................................................................................................................................................
363-211-555 6-137
Alarms and trouble clearing To clear VoIP port protection alarm
...................................................................................................................................................................................................
3 Verify that there is no longer a VoIP protection alarm raised in the Active Alarms and
Conditions window.
E...................................................................................................................................................................................................
ND OF STEPS
Expected results
clearing procedure is cleared.
....................................................................................................................................................................................................................................
6-138 363-211-555
7 D etailed procedure descriptions
7
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter contains GSI operations.
Contents
Commonly used basic procedures 7-5

Installing the GSI 7-6
Remove a Circuit Pack 7-11
System Access via GSI 7-14
Create/Edit or run a Script 7-18
Procedures used for initial system turn-up 7-22
AP Installation 7-24
Change password 7-26
Change password on ICAP 7-28
Configure or retrieve stand-alone mode for ICAP or VoIP AP via 7-31
terminal
Configure stand-alone mode for ICAP or VoIP APs via IP controller and 7-36
GSI
Configure stand-alone/controlled mode via GSI 7-38
ESIM Installation in a LAG 200 Shelf (controller mode) 7-39
Insert a pack 7-41
IPFM Installation 7-44
Provision duplex IPFM mode (optional) 7-46
Provision IP AP slots 7-48
Provision link aggregation (optional) 7-49
Provision the IPFM uplink transmission parameters 7-52
Provision spanning tree protocol group (optional) 7-54
...................................................................................................................................................................................................................................
363-211-555 7-1
Detailed procedure descriptions Overview
Provision uplink transmission parameters on the ESIM used as controller 7-57

Set inband management channel (optional) 7-59
Set/Retrieve Date and Time 7-61
Set/Retrieve Date and Time for APs in stand-alone mode 7-64
Set/Retrieve IP address 7-66
Set System Management IP address via serial port on IPADSL AP 7-68
Set up inband management channel for IPADSL in stand-alone mode 7-71
(optional)
Verify/Update software load 7-73
Wiring for ESIM used as controller 7-75
Wiring for IPFM 7-78
Procedures used for VoIP service activation 7-85
Provision port parameters on a VoIP AP 7-86
Provision VoIP AP parameters 7-89
Provision/Retrieve SIP network protocol parameters 7-94
Provision/Retrieve H.248 network protocol parameters 7-100
Provision/Retrieve MGCP network protocol parameters 7-103
Wiring for VoIP APs 7-106
Procedures used for ICAP service activation 7-112
Provision ICAP parameters 7-113
Provision/retrieve feeder parameters on an ICAP 7-118
Provision/retrieve ICAP profiles 7-125
Provision/retrieve network protocol parameters 7-130
Provision/retrieve H.248 port parameters on an ICAP 7-138
Provision/retrieve MGCP port parameters on an ICAP 7-143
Provision/retrieve SIP port parameters on an ICAP 7-148
Provision duplex ICAPs in controlled mode or stand-alone mode 7-155
(optional)
Provision VLANs, IP addresses and Routing on ICAP 7-157
Provision parameters for V5.2 aggregation on an ICAP 7-165
Wiring for ICAPs 7-174
Procedures used for VDSL service activation 7-184
Provision port parameters on a VSIM AP 7-185
Provision/Retrieve VSIM PM profile 7-188
Provision/Retrieve VSIM transmission profile 7-191
...................................................................................................................................................................................................................................
7-2 363-211-555
Retrieve VSIM transmission status 7-195

Wiring for VDSL APs 7-196
Procedures used for activating Ethernet downlinks on ESIM 7-199
Provision port parameters on ESIM 7-200
Wiring for ESIMs used as APs 7-202
Procedures used for ADSL2 service activation 7-206
Provision/Edit/Delete DMT Profile 7-207
Provision port parameters on an IPADSL2 AP 7-211
Provision/Retrieve bridge port PM profile 7-214
Provision/Retrieve bridge port traffic profile 7-217
Provision/Retrieve IPADSL transmission profile 7-220
Provision/Retrieve IPADSL PM profile 7-225
Provision/Retrieve IPADSL bridge port profile 7-228
Wiring for IPADSL2_32p APs 7-232
Procedures used for support of L2 and L3 functionality 7-238
Create/modify a VLAN 7-239
Provision/Delete addresses in DHCP relay 7-247
Provision/Delete MAC address learning 7-248
Provision/Delete static route 7-251
Provision/Disable broadcast storm control 7-252
Provision/Disable IGMP snooping 7-254
Trace route 7-257
Procedures used for QoS support 7-258
Provision/Modify L2/L3 group priorities for QoS 7-259
Provision/Modify L4 group priorities for QoS 7-262
Provision/Modify classifiers on VSIM APs 7-265
Provision/Modify packet type priorities for QoS 7-269
Provision/Modify policies on VSIM APs 7-272
Provision/Modify policy attributes on VSIM APs 7-274
Provision/Modify policy instances on VSIM APs 7-277
Provision the IPFM/ESIM for QoS 7-279
Provision VSIM APs for QoS 7-287
Procedures used for operations, administration and maintenance 7-292
functions
Activate VoIP AP 1:N port protection 7-294
...................................................................................................................................................................................................................................
363-211-555 7-3
AP Software download and activation in controlled mode 7-297

Activate system log facility 7-304
Database backup 7-306
Database restore 7-308
Deactivate VoIP AP 1:N port protection 7-310
Delete an IP application pack 7-312
Force IPFM side switch 7-313
ICAP Media monitoring 7-315
IP AP Growth 7-317
IP AP Degrowth 7-318
ICAP Migration from duplex to simplex mode 7-321
IPFM Migration from duplex to simplex mode 7-323
Provision/Delete trap receiving 7-325
Provision/deprovision CPU utilization alarm 7-326
Retrieve active alarms 7-327
Retrieve IP Equipment 7-328
Retrieve RMON statistics 7-330
Retrieve call statistics on ICAP 7-332
IPFM/ESIM Software download and activation 7-335
Software download/activation and database backup/restore for 7-340
stand-alone AP(s)
System initialization 7-347
VoIP Voice stream monitoring 7-350
....................................................................................................................................................................................................................................
7-4 363-211-555
Detailed procedure descriptions
Commonly used basic procedures
Overview
...................................................................................................................................................................................................................................
Purpose
The following section provides commonly used basic procedures. In this context
commonly used procedure means procedures that may be used for different reasons and
in different states of turn-up and maintenance activities. The procedure descriptions
include detailed information about how to perform the procedures and specify if certain
assumptions have been made.
Contents
Installing the GSI 7-6

Remove a Circuit Pack 7-11
System Access via GSI 7-14
Create/Edit or run a Script 7-18
...................................................................................................................................................................................................................................
363-211-555 7-5
Installing the GSI

...................................................................................................................................................................................................................................
Overview
This section contains information on the AnyMedia Management Interface software
platform requirements and installation instructions. The AnyMedia Management
Interface package is composed of the GSI and the Network Maintenance Manager.
PC requirements
The AnyMedia Management Interface is supported on PCs with the following
minimum functionality:
Hardware requirements
• Computer/processor: a Pentium (586) system (a Pentium III or better is
recommended)
• Display: SVGA video board (SVGA) or higher resolution display 1024 x 768-pixel
resolution for 17″ color monitor; 800 x 600-pixel resolution for laptop
• Peripheral/miscellaneous: mouse or compatible pointing device
• Local access connection through the following:
– COMDAC: a cable connects from the PC serial port(s) to the system’s CIT port
EIA-232E/574 9-pin connector, which is located on the front of the CIU/CTU
circuit pack (local access is optional, but required for local CIT port access).
– AFM: a cable connects from the PC Ethernet port to the 10BaseT RJ-45 jack
on the faceplate of the AFM.
– IPFM: a cable connects from the PC Ethernet port to the 10/100BASE-T RJ-45
jack on the faceplate of the IPFM.
• Remote access: Ethernet LAN card (optional, but required for LAN connection).
Software requirements
• Operating system: Windows 2000, or Windows XP
Windows is a registered trademark of Microsoft Corporation
In Windows XP the following setting is required in order to get a proper display of
the GSI: Click on the desktop to open the ″Display Properties″ window. In the
″Themes″ tab select ″Windows Classic″ from the ″Theme″ scroll list. Click ″OK″
to confirm the setting and close the window.
• Memory: 128 MB minimum of RAM for the application software
• Hard disk space: 500 MB of available hard disk space
• Microsoft Excel and Microsoft Access
Some procedures (ADSL line monitoring, retrieval of NB traffic statistics,
collection of AFM processor load) require these software packages to be installed
on the PC.
• Communications packages: TCP/IP (for LAN connection only)
...................................................................................................................................................................................................................................
7-6 363-211-555
Detailed procedure descriptions Installing the GSI
• Web browsers (for viewing online documentation): Internet Explorer© 5.0 or

Netscape Navigator[tm] 4.0 or later
• PDF Viewer: The current version of Adobe® Acrobat ® Reader comes on the
CD-ROM with the online documentation (for viewing the PDF documentation).
Adobe Systems distributes this software for free; the user does not need a license.
Settings
The following settings are recommended:
• For laptops, minimum setting recommended: 800 × 600 with small fonts.
• For PC, minimum setting recommended: 800 × 600 with small fonts: highly
recommended: 1024 × 768 or higher with small fonts.
Installing the AnyMedia Maintenance Manager application (including NMM and GSI)
These instructions are also available as hard copy with your software.
The AnyMedia Maintenance Manager software is available on CD-ROM and is
equipped with an install wizard that steps you through the process. To get started,
perform the following:
1. Insert the CD-ROM in the CD-ROM drive (probably D: or E:).
2. Select Start from the Windows Task Bar
3. Select Run... from the Menu Box
4. Type or select the drive:\setup.exe (where drive is A, B, C, or D)
5. Select OK.
6. Follow the instructions that appear in the dialog boxes. The installation program
guides you through the setup.
Install online documents

To have access to the online documents after you install the NMM/GSI software,
choose one or both of the following:
• View documentation on CD-ROM
• Copy documentation folders into your PC
View documentation on CD-ROM
NOTE: You may not have enough disk space to install all the documents; therefore,
you may choose to leave the CD-ROM in its drive and view the document(s) from
there.
Please perform the following steps:
1. Insert the AnyMedia Documentation CD-ROM into the CD-ROM drive.
2. Click Start on the Taskbar and select Run...
3. Open field: click the down arrow until you see a path with the letter of your
CD-ROM drive and Setup.exe (e.g., D:\Setup.exe). Click this path and click OK.
or
Click Browse to navigate to your CD-ROM drive. Click Setup.exe.
....................................................................................................................................................................................................................................
363-211-555 7-7
4. The Lucent Electronic Documentation program group is created automatically.

5. Click OK.
6. A pop-up window asks: Do you wish to install Adobe Acrobat Reader X.X?
If you click Yes, Reader is installed.
If you click No, you receive the following notification: Installation Complete!
7. Click OK.
8. In the Lucent Electronic Documentation window, double-click on the AnyMedia
Documentation icon or select Start -> Programs -> Lucent Electronic
Documentation -> AnyMedia. Your default Web browser opens to the AnyMedia
Access System Commands and Procedures home page.
9. You can view Acrobat versions of other AnyMedia documents by scrolling in the
navigation window and clicking on Other AnyMedia Documents. The documents
appear in the Acrobat Reader window.
Copy documentation folders into your PC
If you have enough disk space, you may want to load the documents into your PC.
Please perform the following steps:
1. Insert the AnyMedia Documentation CD-ROM into the CD-ROM drive.
2. Click the Start button on the Taskbar and select Programs, then Windows Explorer.
3. Find the CD-ROM drive and click on it.
4. The documents are included in folders on the CD-ROM see following tables.
5. To load the folders, click and hold with the left mouse button on the folder you
want to copy, then drag the file(s) into the location on your PC where your GSI is
installed (a folder named Documents has been created for you if you already
installed the GSI software [see “Installing the AnyMedia Maintenance Manager
application (including NMM and GSI)” (p. 7-7)]). In this example, the disk drive is
the C drive:
C:\Program Files\Lucent Technologies\Anymedia\Gsi\Documents
Tip: If you set your Web browser’s home page to the Commands and Procedures
index.html file, it will always appear when you open your Web browser (see “Set
browser home page ” (p. 7-9)).
Documents on the CD-ROM for International regions
Folder name Documents on the CD-ROM (363-211-114) for international regions

363-211-555 Commands and Procedures for IP-based services (HTML format 4.00 MB)
363-211-119 Commands and Procedures for Narrowband Services (HTML format 8.75 MB)
363-211-133 Commands and Procedures for ATM xDSL services (HTML format 7.5 MB)
pdf All documents in PDF format for example:
• Applications and Planning Guide (APOG) Overview
• Applications and Planning Guide (APOG) IP-based Services
• Applications and Planning Guide (APOG) Narrowband and ATM xDSL
Services.
....................................................................................................................................................................................................................................
7-8 363-211-555
Documents on the CD-ROM for North America regions (NAR)
Folder name Documents on the CD-ROM (363-211-104) for North America regions (NAR)
363-211-555 Commands and Procedures for IP-based services (HTML format 4.00 MB)
363-211-100 Commands and Procedures (HTML format 8.75 MB)
pdf All documents in PDF format for example:
• Applications and Planning Guide (APOG) Overview
• Applications and Planning Guide (APOG) IP-based Services
• Applications and Planning Guide (APOG) Narrowband and ATM xDSL
Services
• AnyMedia Access System Feature Supplements.
Navigating to a file
This is general guidance on navigating to the Commands and Procedures file in your
PC from a Web browser. Your Web browser version may have different steps.
For example Internet Explorer© users have to perform the following steps:
1. From the Internet Explorer menu, select File, then select Open.
2. Locate the file on the PC; use the Browse button.
3. Click on the folder named 363-211-555.
4. Click on the file named index.html.
To set the browser home page, highlight this path, copy and paste the path to the Start
Page or Home Page field in the home page area (see “Set browser home page ”
(p. 7-9)).
Set browser home page

If you do not copy the documents on the CD-ROM to your PC, your Web browser will
open when you click on the AnyMedia Documentation icon if the CD-ROM is in the
CD-ROM drive. You do not need to set a browser home page.
If you load the documents into your PC, you will want to set your Web browser home
page to the following location (in this instance, the drive is C drive:)
C:/Program Files/Lucent Technologies/Anymedia/Gsi/Documents/363-211-
555/index.html
If you choose to do this, the browser will always start with the Commands and
Procedures first page. Otherwise, bookmark this location so that you can find it easily.
Internet Explorer© Users have to perform the following steps:
1. Double-click on the Internet Explorer icon.
2. Select Tools, then Options, then General.
....................................................................................................................................................................................................................................
363-211-555 7-9
3. From the menu, select Start Page or Home Page.

4. Type or paste in the path to the online documentation from the URL obtained when
you navigated to the file (see “Navigating to a file ” (p. 7-9)). In this example, the
drive is C drive:
(C:/Program Files/Lucent Technologies/AnyMedia/Gsi/Documents/363-211-
555/index.html)
Netscape Navigator[tm] 4.0 Users have to perform the following steps:
1. Double-click on the Netscape Navigator icon.
2. Select Edit, then Preferences.
3. Select Navigator.
4. Select Home Page button.
5. Select the Browse button.
The Browse for Home Page window appears. Browse for the file called index.html.
In this example, the drive is C drive:
C:/Program Files/Lucent Technologies/AnyMedia/Gsi/Documents/363-211-
555/index.html
6. Click Open. The path name is populated in the Home Page field.
7. Click OK to save the home page location.
Getting Help on GSI

The GSI has online Help that will guide you through the GSI application. While in the
GSI do the following steps:
1. From the menu bar, click Help then Contents. This launches the Help table of
contents.
2. Click Overview if you need information on the GSI environment.
3. Click Getting Started for a quick start on how to use the GSI to connect to the
COMDAC, AFM or IPFM and perform the operations.
....................................................................................................................................................................................................................................
7-10 363-211-555
Remove a Circuit Pack

...................................................................................................................................................................................................................................
Purpose
Use this procedure to remove a pack from theAnyMedia ® Access System shelf safely
and without damaging the pack.
Assumption
Make sure that there is no service unintentionally interrupted! Before removing a pack
from the AnyMedia ® Access System make sure that there is no cross connection
established and no service is running. If the IPFM shall be removed ensure that this
does not lead to an undesired service interruption. The connected cables have been
already removed.
CAUTION
ESD hazard
cabinet ESD bonding point should be used.
Important! When removing or inserting a pack always wait 15 seconds before

removing or inserting the same or another pack.
Procedure
...................................................................................................................................................................................................
1 Attach the ESD wrist strap that is grounded on the shelf.

...................................................................................................................................................................................................
2 Remove the pack physically from the shelf as described in the next step.
...................................................................................................................................................................................................
3 CAUTION
Destruction of components by incorrect handling.
Handle the pack by the faceplate only to prevent pack or personal injury.
Simultaneously press up on the upper latching lever and press down on the lower
latching lever. Pull the latching levers gently outward to disengage the pack from the
assembly.
Upper and lower latch of a pack
...................................................................................................................................................................................................................................
363-211-555 7-11
Detailed procedure descriptions Remove a Circuit Pack
(Click on image to enlarge)

...................................................................................................................................................................................................
4 If the pack will not be reinserted as part of the procedure being executed, remove the
pack from the slot and place the pack gently in an ESD-compliant bag.
....................................................................................................................................................................................................................................
7-12 363-211-555
Detailed procedure descriptions Remove a Circuit Pack
...................................................................................................................................................................................................
5 If the pack is to be removed permanently, replace the circuit pack with a blank
faceplate and fasten the cables somewhere or remove them.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-13
System Access via GSI

...................................................................................................................................................................................................................................
Purpose
Use this procedure to access the IP subsystem via the GSI on a PC. The IP subsystem
can be either
• a controlled system or
• a stand-alone IP application pack or
• an IP system in a LAG 200 Shelf with an ESIM in controller mode.
Assumptions
• Verify that IP connectivity between PC and circuit pack is provided via LAN or
directly.
Required equipment
The following equipment is required:
• A PC that is equipped with the GSI software and properly configured. Instructions
for installing the GSI can be found in “Installing the GSI” (p. 7-6).
Procedure
...................................................................................................................................................................................................
1 Determine from the work order how the PC is to be connected to the shelf.
...................................................................................................................................................................................................
2 If you don`t know the IP address of the network element you want to connect to,
follow the procedure “Set/Retrieve IP address ” (p. 7-66) or in case of an ICAP or a
VoIP configured in stand-alone mode follow the procedure “Configure or retrieve
stand-alone mode for ICAP or VoIP AP via terminal” (p. 7-31).
...................................................................................................................................................................................................
3 Verify that the IP address of the PC is compatible for direct connection to the circuit
pack.
If PC IP address and IP address of the network element do not have the same Network
ID the communication between both systems will not work. In this case ask your
network administrator for the appropriate IP address of your PC.
...................................................................................................................................................................................................
4 From the Start button on the taskbar select Programs-> Anymedia click on
AnyMedia GSI Rx.x.x (x.x.x stands for the GSI version number).
Result: A No Records found... window pops up.
...................................................................................................................................................................................................
5 Click Ok.
...................................................................................................................................................................................................................................
7-14 363-211-555
Detailed procedure descriptions System Access via GSI
Result: The AnyMedia Access System Network Maintenance Manager window

pops up.
NOTE: For information on how to use the Network Maintenance Manager go to
“Installing the GSI” (p. 7-6).
...................................................................................................................................................................................................
6 Click Run GSI.

Result:

This is the first time you have connected to the the Ask User window opens and
system presents the startup options. Go to
Step 7.
This is not the first you previously the Communications window opens.
time you have selected Connect to Go to Step 10.
connected to the the System as a default
system you previously the Ask User window opens and
selected Ask User as a presents the startup options. Go to
default Step 7.
you want to change from the menu bar select View ->
the default startup Options. Click the Startup tab. Note
option that this menu bar option is only
available when the user is not
connected to the system. Go to Step
7.
...................................................................................................................................................................................................
7 To change, set, or execute a startup option, click one of the following in the GSI
section of the window:
• Offline (Learn Mode)
• Connect to the System
• Ask User
To use your choice as the default mark the Set As Default checkbox. Click OK
...................................................................................................................................................................................................
8 IF... THEN...
you want the GSI as the startup in the GSI or NMM Startup section of the window
option verify the Always Ask User checkbox is empty. Go
to Step 9.
you want the choice to select the in the GSI or NMM Startup section of the window,
GSI or NMM at startup click in the Always Ask User checkbox so that a
checkmark appears. Go to Step 9.
....................................................................................................................................................................................................................................
363-211-555 7-15
...................................................................................................................................................................................................
9 IF... THEN...
you want to access an IP subsystem in go to Step 10.
controlled mode via GSI
you want to access to a stand-alone AP go to Step 12.
via GSI
...................................................................................................................................................................................................
10 Select the IPFM/ESIM tab and enter the appropriate IP address in the Host Add drop
list box.
IF... THEN...
You want to add an IP address select the tab New IP Address, enter the IP Address,
to the list in the Host field, NE Name, and Location in the entry fields. Click OK.
click Address book The new IP address appears in the List of IP
Addresses. Click OK to close the Address Book
window. Go to Step 11.
You want to edit an IP address select the IP address, click Edit and make the
already in the list in the Host change. Click OK to close the Address Book
field, click Address book window. Go to Step 11.
You want to delete an IP select the IP address you want to delete and press the
address from the list in the Del button of your keyboard.
Host field, click Address book
...................................................................................................................................................................................................
11 In the Login section, enter the Security ID given in the work order, or enter the default
setting private.
Security ID: private
Select the option Remember my Password, if desired.

Verify that the Learn Mode (No Connection) is not selected. Click Connect.
....................................................................................................................................................................................................................................
7-16 363-211-555
Result: Example, for connecting to IPFM: The Login block is replaced with a
Status block and shows the activity of the connection with a green bar and the
words Connecting to IPFM.... The Connect button text changes to Disconnect.
The IPFM:LED in the bottom status bar of the GSI changes from red to green and
the text Offline changes to the IP address. The Shelf View window displays only
the IP circuit packs. The Communications window disappears. If alarms are
present, the Alarms and Conditions Reporting window opens and if new events
occur, the Event window opens.
...................................................................................................................................................................................................
12 Select the STANDALONE tab and enter the appropriate Slot number, Pack type, Shelf
type, IPAddress in the table.
Enter the Security ID given in the work order, or enter the default setting private then
click in the Action column the Connect tab.
Result: In the Status column the Not Connected entry changes to Connected and
the field becomes green.
The Shelf:LED in the bottom status bar of the GSI changes from red to green and the
text Not Connected changes to for example LAG1900 SA: Connected. The Shelf
View window displays only the IP circuit pack you are connected. The
Communications window disappears. If alarms are present, the Alarms and
Conditions Reporting window opens and if new events occur, the Event window
opens.
...................................................................................................................................................................................................
13 In case of a system fault the Status bar remains blue. A connect fail message appears.
• Check the cabling between AnyMedia ® and PC
• Check the pinout of the AnyMedia ® - PC cable
• Check the remote LAN connection
• Confirm the IP address being used for the GSI connection is the same as specified
in the work order
• Check IP connectivity
• Confirm the Security ID is the same as specified in the work order
• Contact your local organization if necessary.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-17
Create/Edit or run a Script

...................................................................................................................................................................................................................................
Purpose
To facilitate the entry of a large number of SNMP provisioning commands, such as
provisioning of ports.
Follow the applicable procedure
• “Create a text script with script mode” (p. 7-18)
• “Edit a text script with script mode” (p. 7-19)
• “Edit a text file with WordPad” (p. 7-20)
• “Run a Script” (p. 7-21)
Background
You can create/edit a script or run a script in the following ways:
• Create a text script with the Script Mode button on a command window
• Edit a text file directly with a text editor, such as WordPad
• Run a script from the script mode in the GSI window (e.g. port provisioning)
• Run a script from the menu bar in the GSI.
Create a text script with script mode

...................................................................................................................................................................................................
1 Navigate to the screen that contains the provisioning you would like to save into a
script, (e.g. port provisioning).
...................................................................................................................................................................................................
2 Click on the Script Mode box if not already checked.

Result: The GSI Script Facility window opens.
...................................................................................................................................................................................................
3 In the provisioning window, select the shelf, pack, and other provisioning entities and
parameters.
...................................................................................................................................................................................................
4 When all the entities and parameters have been selected, click, Delete, or Apply.
Result: As you click on the, Delete, or Apply buttons, the provisioning commands
will appear in the GSI Script Facility window.
In case of a system fault: If you want to change the resulting commands, click
Clear in the GSI Script Facility window. Go to Step 3.
...................................................................................................................................................................................................
5 Repeat Step 1 through Step 4 for any additional provisioning you would like to add in
the script from the pack and port screens.
...................................................................................................................................................................................................................................
7-18 363-211-555
Detailed procedure descriptions Create/Edit or run a Script
...................................................................................................................................................................................................
6 To save the script, click Save As...

Result: The Save Script As dialog window opens.
...................................................................................................................................................................................................
7 Enter a file name and navigate to the directory in which you want to store the file.
Click Save.
...................................................................................................................................................................................................
8 Click the X in the upper right-hand corner of the window and uncheck the Script Mode
box in the provisioning screen.
E...................................................................................................................................................................................................
ND OF STEPS
Edit a text script with script mode

...................................................................................................................................................................................................
1 From the menu bar, select File -> Scripting -> Run.
Result: The Open window opens.
...................................................................................................................................................................................................
2 Navigate to the appropriate directory and select the script file that you want to edit.
Click Open.
Result: The selected file opens in the GSI Script Facility window.
...................................................................................................................................................................................................
3 IF... THEN...
you want remove all lines in the in the GSI Script Facility window, click Clear.
file
you want to add to the lines in select the command.
the file Click Apply in the provisioning window.
...................................................................................................................................................................................................
4 In the provisioning window, select the shelf, pack, and other provisioning entities and
parameters.
...................................................................................................................................................................................................
5 When all the entities and parameters have been selected, click, Delete, or Apply.
Result: As you click, Delete, or Apply, the provisioning commands will appear in
the GSI Script Facility window.
In case of a system fault: If you want to change the resulting commands, click
Clear in the GSI Script Facility window. Go to Step 3.
....................................................................................................................................................................................................................................
363-211-555 7-19
...................................................................................................................................................................................................
6 Repeat Step 4 through Step 5 for any additional provisioning you would like to add in
the script from the pack and port screens.
...................................................................................................................................................................................................
7 To save the script, click Save As ...

Result: The Script Save as dialog window opens.
...................................................................................................................................................................................................
8 Enter a file name and navigate to the directory in which you want to store the file.
Click Save.
...................................................................................................................................................................................................
9 Click the X in the upper right-hand corner of the window and uncheck the Script Mode
box in the provisioning screen.
E...................................................................................................................................................................................................
ND OF STEPS
Edit a text file with WordPad

...................................................................................................................................................................................................
1 Start the WordPad text editor.

...................................................................................................................................................................................................
2 From the WordPad menu bar, select File -> Open.

Result: The Open window appears.
...................................................................................................................................................................................................
3 Navigate to the appropriate directory and select the file that you want to edit.
...................................................................................................................................................................................................
4 Click Open.
...................................................................................................................................................................................................
5 Edit or add to the commands, one per line, using the appropriate syntax.
NOTE: For similar commands, use the Copy and the Paste edit commands to create
identical commands and then edit in the differences (e.g, to keep the command the
same but to change the Configured State parameter).
...................................................................................................................................................................................................
6 When you have completed entering commands, save the file: from the WordPad menu
bar, select File -> Save.
...................................................................................................................................................................................................
7 Exit the WordPad text editor: from the WordPad menu bar, select File -> Exit.
....................................................................................................................................................................................................................................
7-20 363-211-555
Result: The WordPad window closes.

E...................................................................................................................................................................................................
ND OF STEPS
Run a Script
...................................................................................................................................................................................................
1 Navigate to any screen that has a Script Mode button (e.g., port screens).
...................................................................................................................................................................................................
2 Navigate to the appropriate directory and select the script that you want to run. Click
Open.
Result: The GSI Script Facility window opens.
The text of the script appears in the GSI Script Facility window.
...................................................................................................................................................................................................
3 In the GSI Script Facility window, click Run.

NOTE: You can make the script pause with the Pause button and resume with the
Run button. You can stop the script with the Stop button; if you want to run the script
again, it starts over from the beginning.
...................................................................................................................................................................................................
4 Verify that each command executes as desired.

In case of a system fault: If any individual TL1 command fails to execute, determine
the reason for the failure and resubmit the command manually.
...................................................................................................................................................................................................
5 To exit the GSI Script Facility window, click the X in the upper right-hand corner of
the window. To exit Script Mode, uncheck the Script Mode box in the provisioning
screen.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-21
Procedures used for initial system turn-up
Overview
...................................................................................................................................................................................................................................
Purpose
The following section provides the procedures mainly used for initial system turn-up.
Note that it is strongly recommended to follow the procedure order that is provided in
Chapter 2, “Initial system turn-up and service activation”.
The procedure descriptions include detailed information about how to perform the
procedures and specify if certain assumptions have been made.
Contents
AP Installation 7-24
Change password 7-26
Change password on ICAP 7-28
Configure or retrieve stand-alone mode for ICAP or VoIP AP via 7-31
terminal
Configure stand-alone mode for ICAP or VoIP APs via IP controller and 7-36
GSI
Configure stand-alone/controlled mode via GSI 7-38
ESIM Installation in a LAG 200 Shelf (controller mode) 7-39
Insert a pack 7-41
IPFM Installation 7-44
Provision duplex IPFM mode (optional) 7-46
Provision IP AP slots 7-48
Provision link aggregation (optional) 7-49
Provision the IPFM uplink transmission parameters 7-52
Provision spanning tree protocol group (optional) 7-54
Provision uplink transmission parameters on the ESIM used as controller 7-57
Set inband management channel (optional) 7-59
Set/Retrieve Date and Time 7-61
Set/Retrieve Date and Time for APs in stand-alone mode 7-64
Set/Retrieve IP address 7-66
Set System Management IP address via serial port on IPADSL AP 7-68
...................................................................................................................................................................................................................................
7-22 363-211-555
Set up inband management channel for IPADSL in stand-alone mode 7-71

(optional)
Verify/Update software load 7-73
Wiring for ESIM used as controller 7-75
Wiring for IPFM 7-78
....................................................................................................................................................................................................................................
363-211-555 7-23
AP Installation
...................................................................................................................................................................................................................................
Purpose
Use this procedure to insert IP APs into an AnyMedia ® shelf.
Wiring
The wiring information for the different AP types is provided in the individual wiring
procedures.
Procedure
CAUTION
CAUTION
ESD hazard

...................................................................................................................................................................................................
1 Locate the AP slot specified in the work order. For more information on where which
pack type may be installed, see “Configuration considerations for the different
AnyMedia ® shelf types” (p. 2-5).
...................................................................................................................................................................................................

...................................................................................................................................................................................................
3 If the slot is equipped with a blank cover, remove the cover from the slot by releasing
the latches at the top and bottom.
...................................................................................................................................................................................................
4 Insert the AP into the identified slot. For details about how to insert a pack properly,
see “Insert a pack ” (p. 7-41)
...................................................................................................................................................................................................................................
7-24 363-211-555
Detailed procedure descriptions AP Installation
Result: When the AP is inserted, all LEDs on the AP light for a short interval,
followed by a flashing of the FAULT LED during AP self-initialization. The
FAULT LED will remain lit red until the cable connectors have been attached. (The
LEDs on the ICAP do not behave this way).
Failure conditions: If the FAULT LED remains dark, check the following possible
causes:
• Is the shelf powered?
Verify that the LEDs POW1 and POW2 on the CIU/CTU are lit.
• Are the shelf fuses faulty?
Refer to the Installation Manuals and check the fuses.
• Is the AP faulty?
Insert another AP and check the LED behavior.
System behavior: If the ICAP (in controlled mode configuration) is not seen by
the IPFM within 5 minutes verify that the ICAP is not provisioned for standalone
mode.
...................................................................................................................................................................................................
5 Repeat the steps above until all APs specified in the work order are plugged in.
...................................................................................................................................................................................................
6 IF YOU WANT TO RETURN TO THE THEN...

LINKS FOR INITIAL SYSTEM
TURN-UP FOR...
an IPFM go to “Links to initial system turn-up
procedures with IPFM(s)” (p. 2-23)
an ESIM as controller in a LAG 200 go to “Links to initial system turn-up of
Shelf the ESIM used as controller in the
LAG 200 Shelf ” (p. 2-26)
an ICAP and VoIP APs in stand-alone go to “Links to initial system turn-up
mode procedures for ICAP and VoIP APs in
stand-alone mode ” (p. 2-40)
APs in stand-alone mode go to “Links to initial system turn-up
procedures for IPADSL APs in stand-alone
mode” (p. 2-44)
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-25
Change password
...................................................................................................................................................................................................................................
Purpose
Use this procedure to set a new CLI login password or to set/configure a password for
the different user roles (admin, privileged user) on the controller pack.
Assumptions
directly.
Procedure
...................................................................................................................................................................................................
1 Follow the “System Access via GSI ” (p. 7-14) for connecting the GSI.
...................................................................................................................................................................................................
2 From the menu bar select IP Subsystem -> IP Data -> Communication -> Open
CLI{ to open a Telnet session at the GSI into the controller pack.
Result: A telnet window with CLI opens.
...................................................................................................................................................................................................
3 IF... THEN...
you want to set a new CLI login password go to Step 4.
you want to set a new password for go to Step 5.
privileged user
...................................................................................................................................................................................................
4 In the Login section, enter the user id and the default password:
• Firebird login: admin
• password: changeme
• Firebird(xxx)> enable
Then set a new password:
• Firebird(xxx)# config terminal
• Firebird(xxx) (config)#
username admin privilege 15 password <new password>
• exit
• write
To disconnect the telnet session go to Step 6.
...................................................................................................................................................................................................................................
7-26 363-211-555
Detailed procedure descriptions Change password
...................................................................................................................................................................................................
• password: changemetoo
• Firebird(xxx)# config terminal
Then set a new password for level 15 and/or level 8:
• Firebird(xxx) (config)# enable password level 15 <new password>
• Firebird(xxx) (config)# enable password level 8 <new password>
• exit
• write
Result: The CLI window is closed automatically.

...................................................................................................................................................................................................
6 Disconnect the telnet session:

Firebird(xxx)# exit
...................................................................................................................................................................................................
7 Disconnect the Ethernet cable from the circuit pack MGMT interface.
...................................................................................................................................................................................................
8 IF YOU CAME FROM... THEN RETURN TO...

initial system turn-up for an IPFM “Links to initial system turn-up
initial system turn-up for an ESIM as “Links to initial system turn-up of the
controller in a LAG 200 Shelf ESIM used as controller in the LAG 200
Shelf ” (p. 2-26)
initial system turn-up for ICAP and VoIP “Links to initial system turn-up
APs in stand-alone mode procedures for ICAP and VoIP APs in
stand-alone mode ” (p. 2-40) for
continuing with the next steps in the
system turn-up flow
initial system turn-up for an IPADSL APs “Links to initial system turn-up
in stand-alone mode procedures for IPADSL APs in stand-alone
mode” (p. 2-44)for continuing with the
next steps in the system turn-up flow
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-27
Change password on ICAP

...................................................................................................................................................................................................................................
Purpose
Use this procedure to set a new CLI login password or to set/configure a password for
the different user roles (admin, privileged user) on the ICAP in controlled mode or
stand-alone mode.
Assumptions
directly.
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 From the menu bar select IP Subsystem -> IP Data -> Communication -> Open
CLI{ to open a Telnet session at the GSI into the controller pack.
Result: A telnet window with CLI opens.
...................................................................................................................................................................................................
3 IF... THEN...
and the ICAP is in controlled mode
and the ICAP is in stand-alone mode
...................................................................................................................................................................................................
• Firebird(xxx)# slot 7 <slot number for the ICAP>
...................................................................................................................................................................................................
5 Enter the default login parameters:

• Login: admin
• Password: changeme
...................................................................................................................................................................................................................................
7-28 363-211-555
Detailed procedure descriptions Change password on ICAP
Result: The Alcatel-Lucent AnyMedia Access System Configuration Program opens

and prompts you to enter one of the following options:
1. Display Flash Version
2. Display Existing Configuration
3. Configure System
4. Restricted shell interpreter
5. Change Administrator Password
6. Change Standalone IP Management port Parameters
7. Log off
Select Option>
Additional information: You may enter ″help″ or ″?″ for help, ″quit″ or ″q″ to exit.
...................................................................................................................................................................................................
6 At the prompt enter 5 for Change Administrator Password.

Result: The following dialog will be initiated:
• Old password: changeme
Enter the new password (minimum of 8, maximum of 10 characters) It must be
a case-sensitive string containing 8 to 10 alphabetic, numeric and symbolic
characters, where at least two characters have to be numeric and one is
symbolic (~, @, #, $, %, ^, &, *, +, -, _, /, <, and >).
• Enter new password:
• Re-enter new password:
• passwd: The password for admin is changed.
...................................................................................................................................................................................................
7 At the prompt enter 7 for Log Off and then disconnect the telnet session twice via
″exit″.
Firebird(xxx)# exit
...................................................................................................................................................................................................
8 Disconnect the Ethernet cable from the circuit pack MGMT interface.
...................................................................................................................................................................................................
9 IF YOU CAME FROM... THEN RETURN TO...

initial system turn-up for ICAP and VoIP “Links to initial system turn-up
APs in stand-alone mode procedures for ICAP and VoIP APs in
stand-alone mode ” (p. 2-40) for
continuing with the next steps in the
system turn-up flow
....................................................................................................................................................................................................................................
363-211-555 7-29
Detailed procedure descriptions Change password on ICAP
initial system turn-up for an IPADSL APs “Links to initial system turn-up
in stand-alone mode procedures for IPADSL APs in stand-alone
mode” (p. 2-44)for continuing with the
next steps in the system turn-up flow
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-30 363-211-555
Configure or retrieve stand-alone mode for ICAP or VoIP AP

via terminal
...................................................................................................................................................................................................................................
Purpose
This procedure applies to the turn-up of an ICAP or a VoIP AP in stand-alone mode,
that is in configurations where no IP controller is present in the shelf.
This procedure is based on running a script that supports you to change the
configuration mode of the AP to stand-alone mode and to set the management IP
address, the mask and routes on the pack via its serial port.
Note that this procedure does not apply to the LPZ602, because this pack does not
support stand-alone mode.
Required equipment
• PC with a terminal program installed (for example Microsoft Windows Hyper
Terminal)
• A cable to connect the PC to the serial port of the pack
– For an ICAP (LPI600) use the special adapter cable (ED7C873-31 G8) with a
DB9 connector on one side and an RJ45 connector on the pack side.
– For a VoIP AP (LPZ600) use the special adapter cable (ED7C873-31 G13) with
a DB9 connector on one side and an RJ45 connector on the pack side.
Assumption
The IP address, subnet mask and default gateway are known and appropriate to allow
the connection to the PC via the LAN port of the AP after the completion of this
procedure. If this is not the case and you have a Windows® based system, reconfigure
the IP address on the PC accordingly by changing the network settings.
If the pack is an ICAP running in duplex mode, the FE2 ports of both ICAPs are
connected via a LAN crossover cable assembly (ED7C873-31 G7).
Procedure
...................................................................................................................................................................................................
1 Connect the serial port of the PC to the serial port on the faceplate of the pack.
If the pack is an ICAP, then use the special adapter cable and connect the USB like
connector to the CONSOLE port of the pack. Do not use a common USB connector
cable!
If the pack is a VoIP AP, then use the special adapter cable and connect the RJ45
connector to the CONSOLE port of the pack. Do not use a common LAN connector
cable!
...................................................................................................................................................................................................................................
363-211-555 7-31
Detailed procedure descriptions Configure or retrieve stand-alone mode for ICAP or VoIP
AP via terminal
...................................................................................................................................................................................................
2 Turn on the PC.

...................................................................................................................................................................................................
3 Open a terminal program on the PC.

Use the following settings for the connection:
• Data rate: 115200 bps
• Data bits: 8
• Parity: None
• Stop bits: 1
• Flow control: None
...................................................................................................................................................................................................

• Login: admin
• Password: changeme
Result: The Alcatel-Lucent AnyMedia Access System Configuration Program opens
and prompts you to enter one of the following options:
1. Display Flash Version
2. Display Existing Configuration
3. Configure System
4. Restricted shell interpreter
5. Change Administrator Password
6. Change Standalone IP Management port Parameters
7. Log off
Select Option>
Additional information: You may enter ″help″ or ″?″ for help, ″quit″ or ″q″ to exit.
The password can be changed in the hyperterminal with the command passwd or
later, via the GSI.
...................................................................................................................................................................................................
5 IF... THEN...
you want to retrieve the existing Go to Step 6.
configuration
you want to configure the system for Go to Step 7.
stand-alone mode
...................................................................................................................................................................................................
6 At the prompt enter 2 for Display Existing Configuration.
....................................................................................................................................................................................................................................
7-32 363-211-555
AP via terminal
Result: The actual Provisioned Configuration will be displayed:

• Configuration Mode (Standalone or Controlled)
• Customer key code
• Shelf type
• Slot ID
• IP Address
• Network Mask
• Default Gateway
• VLAN ID
• VLAN Priority
• VLAN Admin Status.
Configuration example:
Configuration Mode = Standalone

Provisioned Configuration:
CKC = 64
ShelfType = lag1900
RealSlotId = 5
IpAddress = 135.246.51.248
NetworkMask = 255.255.254.0
DefaultGateway = 135.246.50.1
VlanAdminStatus = disabled
VlanID = 1
VlanPriority = 0
Active Network Configuration:
IpAddress = 135.246.51.248
NetworkMask = 255.255.254.0
VlanID = <N/A>
DefaultGateway = 135.246.50.1
...................................................................................................................................................................................................
7 At the prompt enter 3 for Configure System.

Result: The following configuration methods will be offered:
1. IPFM Controlled Mode: pack configured by local IPFM controller
host.
2. Standalone Mode: pack configured to run as independent host.
3. Return to main Menu.
....................................................................................................................................................................................................................................
363-211-555 7-33
AP via terminal
...................................................................................................................................................................................................
8 WARNING
Service interruption
Changing the configuration is service affecting!
Do not change configuration on an operational system.
At the prompt enter 2 for Standalone Mode.

Result: The Configuring system in Standalone Mode script is started.
...................................................................................................................................................................................................
9 At the prompt enter for each data type a value from the displayed options, or accept
the default value. Data are required for
• Customer key code
• Shelf type
• Slot ID
• IP Address
• Network Mask
• Default Gateway
• VLAN ID
• VLAN Priority
• VLAN Admin Status.
Configuration example: Enter Customer Key Code [0..256, default=28] >
31
Enter Chassis Shelf Type [fastv5dlc, lag1900, lag200, lag2300,

lag4300, other, default=lag2300]> lag1900
Enter Slot ID [3..14, default=3] > 9
Enter IP Address [default=0.0.0.0]> 135.246.51.249
Enter Network Mask [default=255.255.255.0]> 255.255.254.0
Enter Default Gateway [default=0.0.0.0]> 135.246.50.1
Enter VLAN ID [1..4092, default=1] >
Enter VLAN Priority [0..7, default=0] >
Enter VLAN Admin Status [enabled/disabled, default=disabled]>
....................................................................................................................................................................................................................................
7-34 363-211-555
AP via terminal
Result: The configured values are displayed but the system must reboot in order to
activate the new configuration. Therefore you will be prompted to reboot.
...................................................................................................................................................................................................
10 WARNING
Loss of provisioning data
Previous provisioning data will get lost!
Do not start the system reboot if you are not sure about the changed configuration
data.
At the prompt enter yes to start the system reboot.

...................................................................................................................................................................................................
11 Return to “Links to initial system turn-up procedures for ICAP and VoIP APs in
stand-alone mode ” (p. 2-40) for continuing with the next steps in the system turn-up
flow.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-35
Configure stand-alone mode for ICAP or VoIP APs via IP

controller and GSI
...................................................................................................................................................................................................................................
Purpose
This procedure applies to the turn-up of an ICAP or a VoIP AP in stand-alone mode in
configurations where an IP controller is present in the shelf although the IP controller
will not be used for stand-alone mode. But the IP controller in the shelf with its
connection to the GSI allows to easily provision the service parameters and to set the
communications parameters, for example IP address, subnet mask, default gateways
and routes.
Note that this procedure does not apply to the LPZ602, because this pack does not
support stand-alone mode.
Assumption
The pack is running in controlled mode and the IP controller is managed via GSI.
Procedure
...................................................................................................................................................................................................
1 Follow the procedure “Provision IP AP slots” (p. 7-48) to assign the appropriate slot
number.
...................................................................................................................................................................................................
2 IF... THEN...
you want to configure an ICAP AP for go to Step 3
stand-alone mode
you want to provision a VoIP AP for go to Step 6
stand-alone mode
...................................................................................................................................................................................................
3 Follow the procedure “Provision ICAP parameters ” (p. 7-113) to provision in the
System Configuration subtab the appropriate customer key code.
...................................................................................................................................................................................................
4 Follow the procedure “Provision/retrieve ICAP profiles ” (p. 7-125) to provision in the
RTP subtab a new profile with the appropriate values, therefor click first the New
button.
...................................................................................................................................................................................................
5 Follow the “Provision/retrieve network protocol parameters ” (p. 7-130) procedure to

provision the Network Protocol Parameters.
Note: It is important to set the Administrative Status to Enable before you click
Apply.
...................................................................................................................................................................................................................................
7-36 363-211-555
Detailed procedure descriptions Configure stand-alone mode for ICAP or VoIP APs via IP
controller and GSI
...................................................................................................................................................................................................
6 Follow the “Provision VoIP AP parameters” (p. 7-89) procedure to provision in the
General tab the appropriate customer key code and in the Network tab the pack IP
address, subnet mask, and the default gateway. If required enter the appropriate Vlan
ID.
...................................................................................................................................................................................................
7 Go to next procedure “Configure stand-alone/controlled mode via GSI” (p. 7-38) to

configure the AP in stand-alone mode and to restart the pack.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-37
Configure stand-alone/controlled mode via GSI

...................................................................................................................................................................................................................................
Purpose
Use this GSI operation to set an application pack from controlled mode to stand-alone
mode and vice versa via the GSI.
Assumption
You are connected to the pack for which you want to change the operation mode.
If you want to change the operation mode from controlled mode to stand-alone mode,
the service parameters and communications parameters must be provisioned on the
pack already as described in “Configure stand-alone mode for ICAP or VoIP APs via
IP controller and GSI” (p. 7-36).
Procedure
...................................................................................................................................................................................................
1 To change the operational mode of an AP (from controlled to stand-alone or

stand-alone to controlled mode), right-click the front of the AP that you want to
configure and select Set as Standalone Pack or Set as Controlled Pack respectively.
System Response:
Pack will reset! Do you really want to change the Pack-Mode? Yes / No.
...................................................................................................................................................................................................
2 Click Yes to change the pack mode.

Result: The AP reboots. The initialization process takes several minutes. During this
time, connection to the AP is not possible and the fault LED is on. After the AP has
finished initialization, the fault LED extinguishes. After the reboot the pack is in
stand-alone mode or controlled mode respectively, and is ready to connect to the GSI.
...................................................................................................................................................................................................
3
If you want to return to the links for initial system turn-up for stand-alone APs
click on back to initial system turn-up for stand-alone APs.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
7-38 363-211-555
ESIM Installation in a LAG 200 Shelf (controller mode)

...................................................................................................................................................................................................................................
Purpose
Use this procedure to install one ESIM as controller in the LAG 200. In this
configuration the ESIM resides in slot AP-1 only.
For the slot numbers and possible configurations in LAG 200 Shelf see “Configuration
considerations for the different AnyMedia ® shelf types” (p. 2-5).
Assumptions
The LAG 200 Shelf is installed and powered. No IP packs are installed yet.
Procedure
...................................................................................................................................................................................................

...................................................................................................................................................................................................
2 Open the shelf door by turning the latches.

...................................................................................................................................................................................................
3 If applicable, remove the blank faceplate from slot AP-1 by releasing the latches at the
top and bottom of the faceplate and set it aside.
...................................................................................................................................................................................................
4 In this step you will insert the ESIM in slot AP-1. Study the Result before proceeding.
Insert the ESIM into the slot AP-1 (see “Insert a pack ” (p. 7-41)).
Result: Behavior of the ESIM after inserting it into the slot:
• Upon insertion, the FAULT and STANDBY LEDs on the ESIM light for a short
period of time.
• The FAULT LED then flashes for about 15 seconds and the STANDBY LED
remains on.
• The FAULT LED stops flashing and the STANDBY LED extinguishes.
• The ACTIVE LED comes on.
• The ESIM continues to initialize for another minute after the ACTIVE LED
lights. During this time, connection to the ESIM cannot be completed.
• Do not proceed to the next turn-up procedure until self-initialization is
complete.
...................................................................................................................................................................................................................................
363-211-555 7-39
Detailed procedure descriptions ESIM Installation in a LAG 200 Shelf (controller mode)
...................................................................................................................................................................................................
5 In case of a system fault, or if the LEDs behavior is not as described, follow the table
below. Otherwise go to Step 6.
IF THEN
no LEDs light on any installed packs lack of power to the shelf indicates a
faulty fuse or disconnected power. See the
trouble clearing procedures “Power Feed
Failed” in the Commands and Procedures
for additional information.
Then go to Step 6.
...................................................................................................................................................................................................
6 Go to the next turn-up procedure “Set/Retrieve IP address ” (p. 7-66).

If you want to return to the links for initial system turn-up click on back to initial
system turn-up.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-40 363-211-555
Insert a pack
...................................................................................................................................................................................................................................
Purpose
Use this procedure to insert or reinsert a pack into the AnyMedia shelf safely and
without damaging the pack.
Procedure
CAUTION
CAUTION
ESD hazard

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

...................................................................................................................................................................................................
2 If you are inserting a new pack, unwrap the pack.

...................................................................................................................................................................................................
3 With the latches in the open position, slide the pack in until the top portion of the
upper latch is behind the upper lip of the shelf and the bottom portion of the lower
latch is behind the lower lip of the shelf, see figure below.
Upper and lower latch of a pack
...................................................................................................................................................................................................................................
363-211-555 7-41
Detailed procedure descriptions Insert a pack
....................................................................................................................................................................................................................................
7-42 363-211-555
Detailed procedure descriptions Insert a pack
...................................................................................................................................................................................................
4 Lock the pack in position by pressing firmly on the rounded indentation on both top
and bottom latches simultaneously until they click into place.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-43
IPFM Installation
...................................................................................................................................................................................................................................
Purpose
Use this procedure to install one IPFM in the preferred IPFM slot for simplex mode
and additionally one in the IPFM protection slot for duplex mode if applicable.
The type of IPFM depends on the LAG Shelf type:
• In the LAG 1900 Shelf and LAG 2300 is used the IPFM LPI904 or LPI906
• In the LAG 4300 Shelf is used the IPFM LPI903 or LPI905
For the slot numbers of the preferred IPFM slot and the IPFM protection slot in the
different LAG Shelf types refer to “Configuration considerations for the different
AnyMedia ® shelf types” (p. 2-5).
Assumptions
The LAG Shelf is installed and powered. No IP packs are installed yet.
Procedure
...................................................................................................................................................................................................

...................................................................................................................................................................................................
2 Open the shelf doors by turning the latches.

...................................................................................................................................................................................................
3 If applicable, remove the blank faceplate from the preferred IPFM slot by releasing
the latches at the top and bottom of the faceplate and set it aside.
...................................................................................................................................................................................................
4 In this step you will insert the IPFM. Study the Result before proceeding. Insert the
IPFM into the preferred IPFM slot (see “Insert a pack ” (p. 7-41)).
Result: Behavior of the active IPFM after inserting it into the preferred slot:
• Upon insertion, the FAULT and STANDBY LEDs on the IPFM light for a short
period of time.
remains on.
• The FAULT LED stops flashing and the STANDBY LED extinguishes.
• The ACTIVE LED comes on.
• The IPFM continues to initialize for another minute after the ACTIVE LED
lights. During this time, connection to the IPFM cannot be completed.
complete.
System Fault: The system will not work properly if the IPFM is inserted in
another slot than the preferred slot.
...................................................................................................................................................................................................................................
7-44 363-211-555
Detailed procedure descriptions IPFM Installation
Behavior of the standby IPFM after inserting it, while the IPFM in the preferred
slot is active:
• Upon insertion, the FAULT and STANDBY LEDs on the IPFM light for a short
period of time.
remains on.
complete.
...................................................................................................................................................................................................
5 In case of a system fault, or if the LEDs behavior is not as described, follow the table
below. Otherwise go to Step 6.
IF THEN
no LEDs light on any installed packs lack of power to the shelf indicates a
faulty fuse or disconnected power. See the
trouble clearing procedures “Power Feed
Failed” in the Commands and Procedures
for additional information.
Then go to Step 6.
...................................................................................................................................................................................................
6 IF THEN
the system is to run in simplex mode END OF STEPS.
Go to the next turn-up procedure
“Set/Retrieve IP address ” (p. 7-66)
the system is to run in duplex mode repeat Step 3 through Step 5 with the
IPFM protection slot.
Then go to the next turn-up procedure
“Set/Retrieve IP address ” (p. 7-66).
system turn-up.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-45
Provision duplex IPFM mode (optional)

...................................................................................................................................................................................................................................
Purpose
If the subsystem is to run in duplex IPFM mode, use this procedure to provision
duplex mode and to enable IPFM uplink protection if required.
Assumptions
Two IPFMs are inserted in the LAG Shelf.
Requirements
For duplex mode a Y-cable assembly as described in “OAM&P Connectivity” (p. 2-13)
or a hub is required to connect to the LAN OAM&P port of both IPFMs.
Procedure
...................................................................................................................................................................................................
1 Follow “System Access via GSI ” (p. 7-14) for connecting the GSI.
...................................................................................................................................................................................................
2 From the menu bar, select IP Subsystem -> IP Data -> System -> Duplex
Maintenance.
Result: The Duplex Maintenance IPFM window opens.
...................................................................................................................................................................................................
3 From the Protection Mode pull-down menu select Duplex.

...................................................................................................................................................................................................
4 IF... THEN...
IPFM uplink protection is required in the Side Switch on Uplink Failure check
box panel, select the uplinks to be
protected in the event of an uplink failure.
Then go to Step 5.
IPFM uplink protection is not required go to Step 5.
...................................................................................................................................................................................................
5 Click Apply.
...................................................................................................................................................................................................................................
7-46 363-211-555
Detailed procedure descriptions Provision duplex IPFM mode (optional)
Result: The operational state of the standby IPFM changes from the OOS to
Standby.
System Fault: Duplex provisioning is denied if the protection slot is provisioned
for any type of AP. Such provisioning must be removed by the operator before
duplex provisioning can proceed.
...................................................................................................................................................................................................
6 Save this change to the NVDS:

From the menu bar select IP Data -> System -> Save Changes to NVDS.
Result: The duplex IPFM configuration is saved.
...................................................................................................................................................................................................
7 Go to the next procedure “Verify/Update software load ” (p. 7-73).

system turn-up.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-47
...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision the IP AP slots with the applicable AP type for APs in
controlled mode or stand-alone mode.
Assumptions
Make sure that the AP(s) you want to provision is/are properly installed. How to insert
APs refer to “AP Installation” (p. 7-24).
Procedure
...................................................................................................................................................................................................
1 In order to connect to the GSI follow the “System Access via GSI ” (p. 7-14)
procedure.
...................................................................................................................................................................................................
2 From the menu bar select IP Subsystem -> IP Data -> Equipment -> Pack
Provisioning
...................................................................................................................................................................................................
3 Select the desired Slot Number and the Prov. Pack Type (e.g. LPZ600) and press the
Apply button.
...................................................................................................................................................................................................
4 Repeat Step 3 for each AP slot.

...................................................................................................................................................................................................
5 Save these changes to the NVDS:

From the menu bar select IP SubSystem → IP Data → System → Save Changes to
NVDS.
Result: A confirmation window appears. Click YES.
If you want to return to the links for initial system turn-up for an IPFM click on
back to initial system turn-up IPFM or if you want to return to the links for
initial system turn-up for an ESIM as controller in a LAG 200 Shelf click on back
to initial system turn-up ESIM.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
7-48 363-211-555
Provision link aggregation (optional)

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision link aggregation as defined in IEEE 802.3ad which
provides link protection and increased bandwidth. The IPFM supports link aggregation
on the uplinks, the ESIM supports link aggregation on the downlinks to the
subscribers.
Link aggregation builds up a group of physical ports that act as one single logical link.
It is limited to links of the same type and that terminate on the same pack.
Background
Possible link aggregation groups on the IPFM are:
• the two FE uplinks
• the two GbE uplinks.
Possible link aggregation groups on the ESIM are up to four groups of aggregated
physical ports.
Procedure
...................................................................................................................................................................................................
1 From the menu bar, select IP Subsystem -> IP Data -> Transmission -> Link
Aggregation.
Result: The Link Aggregation window opens.
...................................................................................................................................................................................................
2 In the System Configuration field select the Slot of the pack that will be provisioned
for link aggregation. Only slots with IPFMs or ESIMs inserted are displayed.
...................................................................................................................................................................................................
3 In the Distribute Traffic by pull-down menu select how to distribute traffic.

Options are:
• IP Address
• MAC Address
• TCP/UDP L4 Port Nr.
• MAC/IP Address
• IP L4 Port Nr.
• MAC/IP L4 Port Nr.
...................................................................................................................................................................................................................................
363-211-555 7-49
Detailed procedure descriptions Provision link aggregation (optional)
...................................................................................................................................................................................................
4 In the Address Mode pull-down menu select one of the options:

• Source Addr.
• Destination Addr.
• Source & Dest. Addr.
...................................................................................................................................................................................................
5 Click Apply.
...................................................................................................................................................................................................
6 At the bottom of the Aggregation Information field set the administrative state of link
aggregation in the Admin Status pull-down menu to Enabled.
...................................................................................................................................................................................................
7 In the Enable Aggregation Ports field select the ports that will be aggregated:
IF... THEN...
the selected slot houses an IPFM the options for the aggregated ports are:
• FE1 and FE2 or
• GbE1 and GbE2
the selected slot houses an ESIM the options for the aggregated ports are
Port 1 ... Port 8.
...................................................................................................................................................................................................
8 In the Group Identifier pull-down menu select the unique identifier for a particular
aggregator of a pack.
IF... THEN...
the selected slot houses an IPFM select the group identifier:
• 1 for GbE1 and GbE2
• 2 for FE1 and FE2
the selected slot houses an ESIM select one of the group identifiers 1, 2, 3
or 4
...................................................................................................................................................................................................
9 In the Control Protocol pull-down menu select the control protocol.

Options are:
• LACP
• none.
....................................................................................................................................................................................................................................
7-50 363-211-555
Detailed procedure descriptions Provision link aggregation (optional)
...................................................................................................................................................................................................
10 Click Apply.
Result: The link aggregation group becomes active. The text field at the button of
the window displays the parameters of the link aggregation group.
...................................................................................................................................................................................................

From the menu bar select IP SubSystem -> IP Data -> System -> Save Changes to
NVDS.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-51
Provision the IPFM uplink transmission parameters

...................................................................................................................................................................................................................................
Purpose
This procedure is used to set up to 4 uplinks on the IPFM into service and to provision
some port-specific parameters.
Recommendation
For duplex mode the usage of two Y-cable assemblies as described in “OAM&P
Connectivity” (p. 2-13) or two hubs are recommended, one for connecting to both FE1
ports (on active and standby IPFM) in parallel and one for connecting to both FE2
ports in parallel.
Procedure
...................................................................................................................................................................................................
1 From the menu bar, select IP Subsystem -> IP Data -> Equipment -> Port
Provisioning.
Result: The IPFM Port Provisioning window opens.
...................................................................................................................................................................................................
2 In the Port pull-down menu select one of the 4 uplinks.

Options are:
• FE1, FE2 for 100 Mb
• GbE1, GbE2 for 1000 Mb.
Result: The text field Physical Interface Type displays the physical interface type
of the selected port.
...................................................................................................................................................................................................
3 In the Service State pull-down menu set the port to In Service.

...................................................................................................................................................................................................
4 Enable or disable Auto-Negotiation.

...................................................................................................................................................................................................
5 IF... THEN...
Auto-Negotiation is disabled select the Transmission Rate (10, 100, or
1000 Mbps)
and the Transmission Mode (Full or Half)
Go to Step 6.
Auto-Negotiation is enabled Go to Step 6.
...................................................................................................................................................................................................................................
7-52 363-211-555
Detailed procedure descriptions Provision the IPFM uplink transmission parameters
...................................................................................................................................................................................................
6 In the Flow Control pull-down menu enable or disable flow control according to IEEE
802.3x as required.
...................................................................................................................................................................................................
7 IF... THEN...
the provisioned port is a GbE type select the required Pause Announcement.
Options are:
• No pause
• Symmetric
• Asymmetric
• Symmetric and Asymmetric
Then go to Step 8.
the provisioned port is an FE type go to Step 8.
...................................................................................................................................................................................................
8 Only if required, enable the Send Link up/down Traps function.

...................................................................................................................................................................................................
9 Click Apply.
A confirmation message is displayed at the bottom of the window.
...................................................................................................................................................................................................
10 Repeat Step 2 through Step 9 for all IPFM ports to be provisioned.

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

NVDS.
system turn-up.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-53
Provision spanning tree protocol group (optional)

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision a spanning tree protocol (STP) group according to
IEEE 802.1d standard or a rapid spanning tree protocol (RSTP) group according to
IEEE 802.1w standard. STP and RSTP provide loop prevention and link protection.
The IPFM supports the provisioning of an STP group or an RSTP group on the
uplinks, the ESIM supports STP and RSTP on the downlinks to the subscribers.
The procedure consists of the subprocedures:
• “Provision port mapping” (p. 7-54)
• “Provision the group settings” (p. 7-55)
• “Provision the port settings” (p. 7-55).
Background
STP is provisionable on links that terminate on the same pack. All links can be
provisioned to the same STP group.
Provision port mapping

...................................................................................................................................................................................................
1 From the menu bar, select IP Subsystem -> IP Data -> L2 Functions -> Spanning
Tree.
Result: The Spanning Tree window opens.
...................................................................................................................................................................................................
2 Select the Port Mapping tab.

...................................................................................................................................................................................................
3 In the Slot pull-down menu select the slot number of the pack.
...................................................................................................................................................................................................
4 Select the required STP Protocol:

• Standard - 802.1D or
• Rapid - 802.1W
...................................................................................................................................................................................................
5 In the Port Membership field check the ports to be grouped.

...................................................................................................................................................................................................
6 Click Apply.
E...................................................................................................................................................................................................
ND OF STEPS
...................................................................................................................................................................................................................................
7-54 363-211-555
Detailed procedure descriptions Provision spanning tree protocol group (optional)
Go to next subprocedure: “Provision the group settings” (p. 7-55).
Provision the group settings

...................................................................................................................................................................................................
1 Select the Group/Port Setting tab.

...................................................................................................................................................................................................
2 In the Group Setting field set the Group Status of the STP group to Enabled.
...................................................................................................................................................................................................
3 Change the following parameters if required:
Parameter Range Default Value

Bridge Priority 1...65535 32768 (recommended)
Hello Interval 1...10 sec 2 sec
Max. Age 6...40 sec 20 sec
Forward Delay 4...30 sec 15 sec
...................................................................................................................................................................................................
4 Click Apply.
Result: Uneditable text fields provide the following information:
Label Information
Root Bridge Indicates the bridge priority and bridge
MAC address of the root bridge
Cost to Root Indicates the cost of the path to the root
bridge
Root Port Indicates the port identifier of the active
path to the root bridge
E...................................................................................................................................................................................................
ND OF STEPS
Go to next subprocedure: “Provision the port settings” (p. 7-55).
Provision the port settings

...................................................................................................................................................................................................
1 Select the Group/Port Setting tab.
....................................................................................................................................................................................................................................
363-211-555 7-55
Detailed procedure descriptions Provision spanning tree protocol group (optional)
...................................................................................................................................................................................................
2 In the Port Setting field select one port of the group (e.g. FE1).
...................................................................................................................................................................................................
3 Change the following parameters if required:
Parameter Range Default Value

Port Priority (part of the 0...255 128 (recommended)
Port Identifier)
Port Path Cost ( 1) 0...65535 0
Notes:
1. Contribution of the path through this port to the total cost of the path to the root for this
bridge
Result: The Port Status text field displays the current state of the port
The options are:
• Disabled
• Down
• Listening
• Learning
• Forwarding
• Blocking.
...................................................................................................................................................................................................
4 Click Apply.
...................................................................................................................................................................................................
5 Repeat Step 1 through Step 4 for all ports in spanning tree.

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

NVDS.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-56 363-211-555
Provision uplink transmission parameters on the ESIM used as

controller in the LAG 200 Shelf
...................................................................................................................................................................................................................................
Purpose
This procedure is used to set up the uplink transmission parameters on the ESIM into
service and to provision some port specific parameters. In this case the ESIM is the
controller of the other application packs (APs) in the LAG 200 Shelf.
Procedure
...................................................................................................................................................................................................
1 From the menu bar, select IP Subsystem -> IP Data -> Equipment -> Port
Provisioning.
Result: The ESIM Port Provisioning window opens.
...................................................................................................................................................................................................
2 In the Port pull-down menu select the GbE (1000 MB) uplink.
Result: The text field Physical Interface Type displays the physical interface type
of the selected port.
...................................................................................................................................................................................................
3 In the Service State pull-down menu set the port to In Service.

...................................................................................................................................................................................................
4 Enable or disable Auto-Negotiation.

...................................................................................................................................................................................................
5 IF... THEN...
Auto-Negotiation is disabled select the Transmission Rate (1000 Mbps)
and the Transmission Mode (Full)
Go to Step 6.
Auto-Negotiation is enabled Go to Step 6.
...................................................................................................................................................................................................
802.3x as required.
...................................................................................................................................................................................................
7 In the Pause Announcement pull-down menu select the required option.

Options are:
• No pause
• Symmetric
...................................................................................................................................................................................................................................
363-211-555 7-57
Detailed procedure descriptions Provision uplink transmission parameters on the ESIM
used as controller in the LAG 200 Shelf
• Asymmetric
• Symmetric and Asymmetric.
...................................................................................................................................................................................................
8 Click Apply.
A confirmation message is displayed at the bottom of the window.
...................................................................................................................................................................................................

NVDS.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-58 363-211-555
Set inband management channel (optional)

...................................................................................................................................................................................................................................
Purpose
Use this procedure to set up management access to the IPFM via IPFM uplinks
(inband management) or to ESIM via ESIM uplink (if the ESIM is used as controller
pack in a LAG 200 Shelf) and reserve sufficient bandwidth to it if it has to be
guaranteed that the management channel will not be ruled out by user traffic.
Note that OAM access via any provisioned L3 VLAN is not provided per default. If
L3 VLAN OAM is desired, then this L3 VLAN has to be provisioned at initial turn-up
and L3 VLAN OAM access can be provisioned with this procedure.
Assumptions
When setting up the inband management channel, the following conditions are
assumed:
• The AnyMedia ® LAG Shelf is initially configured and managed by GSI or NAM.
• The outband management is performed via its local MGMT Ethernet port.
• The uplink is connected to a network device and is operational.
• The required bandwidth has been calculated according to the QoS provisioning
recommendation for the management channel in the Applications and Planning
Guide for IP-based services.
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 From the menu bar select IP Subsystem -> IP Data -> L2 Functions -> VLAN
Configuration{
Result: The VLAN Configuration window opens.
...................................................................................................................................................................................................
3 Determine an existing VLAN on the controller pack (IPFM or ESIM) to be used for
the inband management channel or define a new one, following the “Create/modify a
VLAN ” (p. 7-239) GSI operation.
...................................................................................................................................................................................................
4 Assign an IP address / subnet mask for that VLAN:

• IP address (inband management IP address)
• Subnet mask
IP address and subnet must be different from the IP address and subnet which have
been provisioned as management IP address at initial system turnup.
...................................................................................................................................................................................................................................
363-211-555 7-59
Detailed procedure descriptions Set inband management channel (optional)
Note: This assignment enables IP connectivity to the controller management services

(Telnet, SNMP).
Note: That host IP address can only be reached across the related VLAN.
...................................................................................................................................................................................................
5 In the Port List field select any of the uplink ports and provision it/them as egress tag
members. Then click Apply.
Result: The table displays a new row with the entered information.
...................................................................................................................................................................................................
6 Set the OAM capable VLAN parameter as used in Step 3.

...................................................................................................................................................................................................
7 Close the window.

...................................................................................................................................................................................................
8 Follow “Provision/Delete static route” (p. 7-251) in order to retrieve the existing
default route and delete it.
...................................................................................................................................................................................................
9 As described in “Provision/Delete static route” (p. 7-251) provision a new default

route.
• For Destination IP Address enter 0.0.0.0
• For Subnet Mask enter 0.0.0.0
• For Gateway enter the IP address of the default gateway.
A VLAN relation is automatically added to a static route when the IP gateway
address is within the IP subnet defined for that VLAN.
...................................................................................................................................................................................................
10 Disconnect and close the GSI.

...................................................................................................................................................................................................
11 Disconnect the Ethernet cable from the MGMT interface.

END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-60 363-211-555
Set/Retrieve Date and Time

...................................................................................................................................................................................................................................
Purpose
Use this GSI operation to set the date and/or the time-of-day either for the COMDAC,
or for the AFM or for the IPFM or for the ESIM or for all of them.
Optionally, for all pack types, the time of day can be synchronized to an NTP server.
Assumption
You are connected to the pack for which you want to set/retrieve date and/or time).
Procedure
...................................................................................................................................................................................................
1 IF... THEN...
you want to use PC date and go to Step 2.
time or set an individual date and
time
you want to synchronize to an go to Step 8.
NTP server
...................................................................................................................................................................................................
2 From the menu bar, select IP Subsystem -> IP Data -> System -> Date and Time
Result: The Set IPFM Date and Time window opens.
The Date and Time fields in the Current Date /Time frame display the date and
time obtained from the controller pack at the time the Set IPFM Date and Time
window was opened.
The Set to PC date and time checkbox in the Set New Date /Time frame is
selected.
...................................................................................................................................................................................................
3 IF... THEN...
you are connected to the IPFM the IPFM is selected in the Select to Set frame. Go
only to Step 5.
you are connected to the ESIM the ESIM is selected in the Select to Set frame. Go
used as controller in the to Step 5.
LAG 200 Shelf only
you are connected to the AFM the AFM is selected in the Select to Set frame. Go
only to Step 5.
you are connected to the the COMDAC is selected in the Select to Set
COMDAC only frame. Go to Step 5.
...................................................................................................................................................................................................................................
363-211-555 7-61
Detailed procedure descriptions Set/Retrieve Date and Time
IF... THEN...
you are connected to the IPFM, the radio button with All is selected in the Select to
AFM and COMDAC Set frame.
Go to Step 4.
...................................................................................................................................................................................................
4 In the Select to Set frame select the radio button of the controller pack for which you
want to set/retrieve date and time.
...................................................................................................................................................................................................
5
IF... THEN...
you are using this procedure to provision go to Step 6.
the date and/or time kept in the controller
pack
you are using this procedure to retrieve Click Refresh to retrieve the actual time
the date and/or time of the IP sub-system
the Current Date /Time frame displays the
date and time obtained from the controller
pack.
Click Cancel after you have finished
examining the values.
END OF STEPS
...................................................................................................................................................................................................
6
IF... THEN...
you want the controller to use the PC date select the Set to PC date and time
and time checkbox. Then go to Step 7.
you want to enter an individual date and uncheck the Set to PC date and time check
time box. Change the date and/or time by
clicking on the date or time field and
typing over the existing numbers or using
the up/down arrows. Use the calendar
format Month:Day:Year and the 24-hour
clock format Hour:Minutes:Seconds (for
example, 16:45:00).
...................................................................................................................................................................................................
7 Click Apply, then click Cancel to close the window. END OF STEPS.
....................................................................................................................................................................................................................................
7-62 363-211-555
Detailed procedure descriptions Set/Retrieve Date and Time
system turn-up.
...................................................................................................................................................................................................
8 From the menu bar, select IP Subsystem -> IP Data -> System -> NTP
Synchronization.
Result: The NTP Server window opens.
...................................................................................................................................................................................................
9 In the tab General select the applicable NTP Protocol Version, enable Synch.
Periodically and enter a value for the Synch. Interval.
...................................................................................................................................................................................................
10 In the Time Offset to Local [min] text field enter the time difference between your
local time and UTC time.
...................................................................................................................................................................................................
11 In the tab Server Info select an IP server from the list or enter the IP address of a new
one and click Apply.
...................................................................................................................................................................................................
12 In the tab Daylight Saving Time select the dates for start and end of the daylight
saving period in your local time zone and click Apply.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-63
Set/Retrieve Date and Time for APs in stand-alone mode

...................................................................................................................................................................................................................................
Purpose
Use this GSI operation to set the date and/or the time-of-day for APs in stand-alone
mode.
Optionally, for all pack types, the time of day can be synchronized to an NTP server.
Assumption
You are connected to the pack for which you want to set/retrieve date and/or time).
Procedure
...................................................................................................................................................................................................
1 IF... THEN...
you want to use PC date and go to Step 2.
time or set an individual date and
time
you want to synchronize to an go to Step 5.
NTP server
...................................................................................................................................................................................................
2 From the menu bar, select IP Subsystem -> IP Data -> System -> Date and Time
Result: The Set Standalones Date and Time window opens.
The Date and Time fields in the Current Date/Time frame display the date and
time obtained from the pack in stand-alone mode. The current date and time from
the controller pack is not available.
The Set to PC date and time checkbox in the Set New Date /Time frame is
selected.
...................................................................................................................................................................................................
3
IF... THEN...
you want to use the PC date and time select the Set to PC date and time
checkbox. Then go to Step 4.
you want to enter an individual date and uncheck the Set to PC date and time check
time box. Change the date and/or time by
clicking on the date or time field and
typing over the existing numbers or using
the up/down arrows. Use the calendar
format Month:Day:Year and the 24-hour
clock format Hour:Minutes:Seconds (for
example, 16:45:00). Then go to Step 4.
...................................................................................................................................................................................................................................
7-64 363-211-555
Detailed procedure descriptions Set/Retrieve Date and Time for APs in stand-alone mode
IF... THEN...
you are using this procedure to retrieve Click Refresh to retrieve the actual time
the date and/or time of the IP sub-system
the Current Date/Time frame displays the
current date and time obtained from the
stand-alone pack.
Click Cancel after you have finished
examining the values.
END OF STEPS
...................................................................................................................................................................................................
4 Click Apply, then click Cancel to close the window. END OF STEPS.
system turn-up.
...................................................................................................................................................................................................
5 From the menu bar, select IP Subsystem -> IP Data -> System -> NTP
Synchronization.
Result: The NTP Synchronization window opens.
...................................................................................................................................................................................................
6 In the tab General select the applicable NTP Protocol Version, enable Synch.
Periodically and enter a value for the Synch. Interval.
...................................................................................................................................................................................................
7 In the Time Offset UTC [min] and Time Offset to Local [min] text field enter the
time difference between your local time and UTC time.
...................................................................................................................................................................................................
8 In the tab Server Info select an IP server from the list or enter the IP address of a new
one and click Apply.
...................................................................................................................................................................................................
9 If you want to return to the links for initial system turn-up click on back to initial
system turn-up.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-65
...................................................................................................................................................................................................................................
Purpose
Use this procedure to set / retrieve the management IP address via the serial port of a
controller in an IP subsystem.
The term Controller is used for an IPFM or for an ESIM used as controller in a LAG
200 Shelf.
Required equipment
• PC with a terminal program (e.g. Windows Hyperterminal) installed
• Null modem cable with male - female connectors or female - female connectors
with gender changer (for IPFM).
• Adapter cable to CONSOLE port with USB-A connector for ESIM controller
(DB9-to-USB RS232).
Procedure
...................................................................................................................................................................................................
1 Turn on the PC
...................................................................................................................................................................................................
2 Connect the null modem cable with the COM port of the PC and the CONSOLE port
of the pack.
...................................................................................................................................................................................................
3 Launch the terminal program with the following settings:

• Data bits: 8
• Parity: None
• Stop bits: 1
...................................................................................................................................................................................................

• login: admin
...................................................................................................................................................................................................
5 IF... THEN...
you want to set IP addresses go to Step 6
you want to retrieve IP address go to Step 7
...................................................................................................................................................................................................................................
7-66 363-211-555
Detailed procedure descriptions Set/Retrieve IP address
...................................................................................................................................................................................................
6 Enter following command sequence to configure the management address (example

192.168.100.100, subnet mask 255.255.255.0) and default router (example
192.168.100.101).
• enable <CR>
• configure terminal <CR>
• interface mgmt <CR>
• ip address 192.168.100.100 255.255.255.0 <CR>
• exit <CR>
• ip route 0.0.0.0/0 168.100.001 <CR> (optional)
• exit <CR>
• write <CR>
...................................................................................................................................................................................................
7 Enter following command sequence to retrieve the IP address of the pack:

• enable <CR>
• show int eth0 (in order to verify interface)
• exit <CR>
...................................................................................................................................................................................................
8 Disconnect terminal program.

...................................................................................................................................................................................................
9 IF YOU WANT TO RETURN TO THE THEN...

LINKS FOR INITIAL SYSTEM
TURN-UP FOR...
an IPFM go to “Links to initial system turn-up
an ESIM as controller in a LAG 200 go to “Links to initial system turn-up of
Shelf the ESIM used as controller in the
LAG 200 Shelf ” (p. 2-26)
APs in stand-alone mode go to “Links to initial system turn-up
procedures for IPADSL APs in stand-alone
mode” (p. 2-44)
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-67
Set System Management IP address via serial port on IPADSL

AP
...................................................................................................................................................................................................................................
Purpose
Use this procedure to set the management IP address on the IPADSL AP via serial port
for using the AP in stand-alone mode.
Required equipment
• PC with a terminal program (e.g. Windows Hyperterminal) installed
• Adapter cable to CONSOLE port with USB-A connector for IPADSL AP
(DB9-to-USB RS232).
Assumption
The IP address, subnet mask and default gateway are appropriate to allow the
connection to the PC via LAN port of the AP after the completion of this procedure if
not, use the CLI to configure the PC accordingly.
Procedure
...................................................................................................................................................................................................
1 Turn on the PC
...................................................................................................................................................................................................
2 Connect the serial cable between the PC serial port COM 1 and the CONSOLE port on
the faceplate of the pack.
...................................................................................................................................................................................................
3 Open Hyperterminal on the PC.

Use the following settings for the connection:
• Data bits: 8
• Parity: None
• Stop bits: 1
...................................................................................................................................................................................................

• LPA633 login: root
...................................................................................................................................................................................................................................
7-68 363-211-555
Detailed procedure descriptions Set System Management IP address via serial port on
IPADSL AP
...................................................................................................................................................................................................
5 Enter following command sequence to configure the management IP address (example

192.168.100.100, subnet mask 255.255.255.0) and default router (example
192.168.100.101).
Provision Management IP address.
At the # prompt type:
# mount -n -o remount,rw /
At the # prompt type:

# cd /opt
Set System Management IP address:

# echo “xxx.xxx.xxx.xxx” > standalone
where xxx.xxx.xxx.xxx is the IP address
Set NETMASK IP address:

# echo “yyy.yyy.yyy.yyy” >> standalone
where yyy.yyy.yyy.yyy is the NETMASK
Set Default Route:

# echo “zzz.zzz.zzz.zzz” >> standalone
where zzz.zzz.zzz.zzz is the Default Gateway IP address
Verify the file has the correct IP address, NETMASK and Default Gateway:
# cat standalone
xx.xxx.xxx.xxx
yyy.yyy.yyy.yyy
zzz.zzz.zzz.zzz
Reboot the LPA633 IP ADSL AP:

# reboot
Result: The IPADSL continues initializing for several minutes. During this time,
connection to the IPADSL is not possible and the fault LED is on. After the AP has
finished initialization, the fault LED will extinguish and the terminal program
window will display the LPA633 login prompt. Disconnect terminal program.
After reboot the pack come up in stand-alone mode and is ready to connect the
GSI in stand-alone mode.
....................................................................................................................................................................................................................................
363-211-555 7-69
Detailed procedure descriptions Set System Management IP address via serial port on
IPADSL AP
...................................................................................................................................................................................................
6 Return to the links for initial system turn-up for APs in stand-alone mode go to “Links
to initial system turn-up procedures for IPADSL APs in stand-alone mode” (p. 2-44)
for continuing the system turn-up.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-70 363-211-555
Set up inband management channel for IPADSL in stand-alone

mode (optional)
...................................................................................................................................................................................................................................
Purpose
Use this procedure to set up management access to the IPADSL via IPADSL uplink
(inband management) and reserve sufficient bandwidth to it if it has to be guaranteed
that the management channel will not be ruled out by user traffic.
Assumptions
When setting up the inband management channel, the following conditions are
assumed:
• The AnyMedia ® LAG Shelf is initially configured and managed by GSI or NAM.
• The outband management is performed via its local MGMT Ethernet port.
• The uplink is connected to a network device and is operational.
• The required bandwidth has been calculated according to the QoS provisioning
recommendation for the management channel in the Applications and Planning
Guide for IP-based services.
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 From the menu bar select IP Subsystem -> IP Data -> Communication ->
Communication Mgmt{
Result: The Communication Mgmt-Standalone window opens.
...................................................................................................................................................................................................
3 Select the Management Interface tab. The Current section already displays the
current management IP address, subnet mask, default router and VLAN ID.
...................................................................................................................................................................................................
4 To set up the management interface with a new IP address, subnet mask, default router
and VLAN ID determine first, in the Requested section of the window, an existing or
a new VLAN on the IPADSL pack to be used for the inband management channel.
Then enter the new IP address, subnet mask, and default router.
Click Apply.
The IP address and subnet mask must be different from the IP address and subnet mask
which have been provisioned as management IP address at initial system turnup.
Note: This assignment enables IP connectivity to the AP management services (Telnet,
SNMP).
...................................................................................................................................................................................................................................
363-211-555 7-71
Detailed procedure descriptions Set up inband management channel for IPADSL in
stand-alone mode (optional)
...................................................................................................................................................................................................
5 To activate the new management interface click on the Activate button.

...................................................................................................................................................................................................
6 If you want to return to the links for initial system turn-up for APs in stand-alone
mode go to “Links to initial system turn-up procedures for IPADSL APs in stand-alone
mode” (p. 2-44).
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-72 363-211-555
Verify/Update software load

...................................................................................................................................................................................................................................
Purpose
Use this procedure to verify and update, if necessary, the software load during initial
system turn-up.
Assumptions
The operator has information about which software version should run on the
controller.
Requirements
For IPFM duplex mode a Y-cable assembly as described in “OAM&P Connectivity”
(p. 2-13) or a hub is required to connect to the LAN OAM&P port of both IPFMs.
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Verify software load and update if necessary:

From the menu bar select IP SubSystem -> IP Data -> System -> SW
Administration...
Result:
The Software Administration window opens. The program version running is listed in
the column labeled Current.

the version on the (if duplex) END OF STEPS.
preferred IPFM the version on the
matches the required protection IPFM
version matches the required
version
neither the version on (if duplex) go to Step 3.
the preferred IPFM nor the version on the
does not matches the protection IPFM
required version matches the required
version
...................................................................................................................................................................................................................................
363-211-555 7-73
Detailed procedure descriptions Verify/Update software load

the version on the (if duplex) follow the “IPFM/ESIM Software
active IPFM matches the version on the download and activation”
the required version protection IPFM does (p. 7-335) procedure to copy the
not match the required required SW version from active
version IPFM to the protection IPFM then
activate the SW on the protection
IPFM.
If the version on the (if duplex) follow the “Force IPFM side
active IPFM does not the version the switch” (p. 7-313) procedure to
match the required protection IPFM does perform a side switch from active
version match the required to the protection IPFM then follow
version the “IPFM/ESIM Software
download and activation”
(p. 7-335) to copy the required SW
version from active IPFM to the
protection IPFM and activate the
SW on the protection IPFM.
ESIM is used as a new software version go to Step 3.
controller in the is required
LAG 200 Shelf in slot
AP-1
...................................................................................................................................................................................................
3 Follow the “IPFM/ESIM Software download and activation” (p. 7-335) procedure.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-74 363-211-555
Wiring for ESIM used as controller

...................................................................................................................................................................................................................................
Purpose
This procedure applies to the ESIM as controller (in LAG 200 Shelf). For wiring the
ESIM used as application pack, refer to “Wiring for ESIMs used as APs” (p. 7-202).
Use this procedure to provide a connection from the ESIM in a LAG 200 Shelf to the
Ethernet transport network.
The ESIM supports one GbE connection (optical or electrical dependent on inserted
SFP module) and/or up to 8 Fast Ethernet connections via SFP modules.
In this manual, the expression connection to the Ethernet transport network is used as
a general term for a connection to the Edge Switch.
NOTE: If the ESIM is used as controller pack in a LAG 200 Shelf, the ESIM is
always inserted in to slot AP-1.
For a reference list refer to “Configuration considerations for the different AnyMedia ®
shelf types” (p. 2-5).
Assumptions
• The optical fiber cables to the Edge Switch are installed in the rack.
• The appropriate SFP module is inserted (ports on the ESIM faceplate).
NOTE: The optical fiber cable must not be connected to the RX ports unless the
optical power is checked.
Required equipment
The cables for connecting the PC are described in “OAM&P Connectivity” (p. 2-13).
Required equipment for GbE:
• A power meter for measuring the output power at the optical cable.
• A set of optical fiber cable between ESIM and Ethernet transport network.
• Appropriate twisted pair cable (100/1000Base-Tx).
For GbE connection via optical cables refer to “Procedure of Gigabit Ethernet fiber
cabling” (p. 7-75) , for GbE and FE connection via electrical cables refer to
“Procedure of 100/1000Base-Tx cabling” (p. 7-76).
Procedure of Gigabit Ethernet fiber cabling
CAUTION
Laser hazard
Injury to eyes caused by invisible laser radiation.
Review the Optical Safety section of this document before proceeding with the
following steps, see “Laser safety” (p. 1-14).
...................................................................................................................................................................................................................................
363-211-555 7-75
Detailed procedure descriptions Wiring for ESIM used as controller
...................................................................................................................................................................................................

...................................................................................................................................................................................................
2 Locate the optical fiber cables coming from the Ethernet transport network and verify,
that all cable ends are labeled. For labeling see figure below.
Edge Switch
(Slot AP-1)
Rx Tx
SFP
Tx Rx
...................................................................................................................................................................................................
3 Route the optical fiber cables from the Ethernet transport network in the cable trough
to the SFP connector 9(GE) on the ESIM faceplate.
...................................................................................................................................................................................................
4 Verify that the port at the Edge Switch side (Tx and Rx) of the fiber cable is active.
...................................................................................................................................................................................................
5 Take the optical fiber cable labeled SFP RX and connect it to the SFP TX port of the
ESIM. Connect the optical fiber cable labeled SFP TX to the SFP RX port of the
ESIM.
...................................................................................................................................................................................................
6 NOTE: Ensure that the bending radius for a single fiber cable is not less than 30 mm
to avoid fiber micro banding and/or the breaking of the optical fiber cable.
Carefully wind and move the excess optical fiber cable from the ESIM into the cable
duct of the rack.
Use the tie wraps as needed to secure the optical fiber cables to the grounding fingers
on the shelf.
NOTE: Do not overtighten the tie wrap or other means used to secure the fiber cable
slack as the fibers may be damaged.
E...................................................................................................................................................................................................
ND OF STEPS
Procedure of 100/1000Base-Tx cabling

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-76 363-211-555
Detailed procedure descriptions Wiring for ESIM used as controller
...................................................................................................................................................................................................
2 Label the ends of the twisted pair cable.

...................................................................................................................................................................................................
3 Connect the ESIM controller pack to the Ethernet transport network for a Gigabit
Ethernet or Fast Ethernet connection. See the “Required equipment” (p. 7-75) section
of this procedure and the “OAM&P Connectivity” (p. 2-13) for details on using the
100/1000Base-Tx-cable assembly.
IF... THEN...
the 100/1000Base-Tx-cable assembly has connect the RJ-45 connector of the twisted
been installed pair cable to the Gigabit Ethernet SFP
module 9(GE) or to the Fast Ethernet SFP
module, ports on the faceplate of the ESIM.
Then connect the other end to the LAN
used for remote operations as specified in
the work order (example the Ethernet
transport network).
Verify that the cable is fixed with cable tie
to the grounding finger of the shelf.
END OF STEPS
the 100/1000Base-Tx cable assembly has route the twisted pair cable in the cable
not been installed trough close to the ESIM faceplate.
Then connect the RJ-45 connector of the
twisted pair cable to the Gigabit Ethernet
SFP module 9(GE) or to the Fast Ethernet
SFP module, ports on the faceplate of the
ESIM. Connect the other end to the
system turn-up.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-77
Wiring for IPFM

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provide a connection from the IPFM to the Ethernet transport
network. The IPFM supports two GbE uplinks via GBIC modules and two Fast
Ethernet FE uplinks.
The type of the optical fiber cables depends on the type of GBIC module used.
In this manual, the expression connection to the Ethernet transport network is used as
a general term for a connection to the Edge Switch.
NOTE: The slot numbering is different for AnyMedia LAG Shelf types. For a reference
list refer to “Configuration considerations for the different AnyMedia ® shelf types”
(p. 2-5).
NOTE: This procedure does not apply to the case of using electrical GBICs in the
LAG 2300 Shelf.
Assumptions
• The optical fiber cables to the Edge Switch are installed in the rack.
Note that the optical fiber cable must not be connected to the RX ports unless the
• The LBOs (Lightguide Buildout) are installed according to the work order.
• The appropriate optical and electrical GBIC modules are available and the IPFM is
inserted.
Note that the electrical GBIC uses a standard RJ-45 connector.
• When using electrical GBICs in the LAG 1900 Shelf, a LAG 1900 Shelf with a
specific front door must be available on site.
If the specific front door is not available, order the appropriate LAG 1900 shelf
type with the specific front panel assembly or just the specific front panel assembly
if you only want to replace the left door (for ordering identification numbers, see
the Ordering Guide).
Required equipment
The cables for connecting the PC are described in “OAM&P Connectivity” (p. 2-13).
Required equipment for FEs:
• Appropriate twisted pair cables (10/100Base-T) for cabling the IPFMs FE1 and
FE2 uplink port.
Required equipment for the optical GbEs:
• A power meter for measuring the output power at the optical cable.
• A set of optical fiber cable between IPFM and Ethernet transport network.
• Two lightguide buildouts (LBO) as specified in the work order.
...................................................................................................................................................................................................................................
7-78 363-211-555
Detailed procedure descriptions Wiring for IPFM
Required equipment for the electrical GbEs:

• Straight-through or crossover, four twisted-pair, Category 5 cable.
• Specific front door at LAG 1900 Shelf.
For FE uplink cabling refer to “100B-T uplink port FE1 and FE2 cabling” (p. 7-79)
For GbE uplink cabling refer to “Procedure of Gigabit Ethernet fiber cabling” (p. 7-80)
or “Procedure of Gigabit Ethernet electrical cabling” (p. 7-83).
100B-T uplink port FE1 and FE2 cabling

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

...................................................................................................................................................................................................
2 Label the ends of the twisted pair cable.

...................................................................................................................................................................................................
3 Connect the IPFM circuit pack to the LAN for a Fast Ethernet connection. See the
“Required equipment” (p. 7-78) section of this procedure and the “OAM&P
Connectivity” (p. 2-13) for details on using the 10/100Base-T-cable assembly.
IF... THEN...
the 10/100Base-T-cable assembly has connect the RJ-45 connector of the twisted
been installed pair cable to the FE(x) port on the faceplate
of the IPFM and connect the other end to
the LAN used for remote operations as
specified in the work order.
NOTE: The ″x″ in the expression FE(x)
stands for 1 or 2 of the IPFM in the
preferred or protection slot.
END OF STEPS
the 10/100Base-T cable assembly has route the twisted pair cable in the cable
not been installed trough to the FE(x) port on the IPFM circuit
pack faceplate. Terminate the other cable
end to the appropriate terminals or
connector on the LAN equipment.
Connect the RJ-45 connector of the twisted
pair cable to the FE(x) port on the faceplate
of the IPFM and connect the other end to
the Ethernet transport network.
....................................................................................................................................................................................................................................
363-211-555 7-79
system turn-up.
E...................................................................................................................................................................................................
ND OF STEPS
Procedure of Gigabit Ethernet fiber cabling
CAUTION
Laser hazard
Injury to eyes caused by invisible laser radiation.
Review the Optical Safety section of this document before proceeding with the
following steps, see “Laser safety” (p. 1-14).
...................................................................................................................................................................................................

...................................................................................................................................................................................................
2 Insert the appropriate optical GBIC module on the GBIC(x) connector of the IPFM
circuit pack.
Note that the yellow LED is turned on when a GBIC module is removed.
...................................................................................................................................................................................................
3 Locate the optical fiber cables coming from the Ethernet transport network and verify,
that all cable ends are labeled. For labeling see figure below.
Rx Tx
GBIC 1
GBIC 1
(preferred slot)
Edge Switch
Tx Rx
Rx Tx
GBIC 2
GBIC 2
Tx Rx
Rx Tx
GBIC 1
GBIC 1
(protection slot)
Edge Switch
Tx Rx
Rx Tx
GBIC 2
GBIC 2
Tx Rx
...................................................................................................................................................................................................
4 Route the optical fiber cables from the Ethernet transport network in the cable trough
to the GBIC1 connectors on the IPFM circuit pack faceplate.
....................................................................................................................................................................................................................................
7-80 363-211-555
...................................................................................................................................................................................................
5 Verify that the port at the Edge Switch side (Tx) of the fiber cable is active.
...................................................................................................................................................................................................
6 Take the optical fiber cable labeled GBIC1 RX and measure the optical power of the
optical fiber receive cables using an optical power meter.
...................................................................................................................................................................................................
7
IF... THEN...
the power is within the IPFM go to Step 9.
circuit pack Receive Max and
Receive Min values
the power is greater than the replace the Lightguide buildout at the far-end
IPFM circuit pack Receive Max circuit pack with an appropriate attenuation value.
The figure in Step 8 shows the correct method for
removing a Cap already installed in a Base.
the power is less than the IPFM replace the Lightguide buildout at the far-end
circuit pack Receive Min circuit pack with an appropriate attenuation value.
The figure in Step 8 shows the correct method for
removing a Cap already installed in a Base.
...................................................................................................................................................................................................
8 Lightguide buildout replacement

NOTE: To avoid permanently damaging the Cap, the small tab on the Cap shown in
the figure must be depressed prior to removing the Cap. Do not lift the tab. While
depressing the tab, slightly rotate the Cap counterclockwise to remove it.
A3003 Base
(Blue)
1 Press
2 Twist counter-clockwise SLIGHTLY
A3060 Cap
(Yellow)
21610_fig_206a
3
Pull to separate
....................................................................................................................................................................................................................................
363-211-555 7-81

...................................................................................................................................................................................................
9 Connect the tested optical fiber cable to the GBIC1 RX port of the IPFM circuit pack.
...................................................................................................................................................................................................
10 Measure the optical power at the fiber to be connected to the RX port of the Edge
switch by using an optical power meter.
...................................................................................................................................................................................................
11
IF... THEN...
the power is within the circuit go to Step 12.
pack’s Edge switch Receive Max
and Receive Min values specified
in the work order
the power is greater than the replace the Lightguide buildout connected to the
circuit pack’s Edge switch IPFM’s GBIC1 TX connector with one with an
Receive Max specified in the appropriate attenuation value. The figure in Step 8
work order shows the correct method for removing a Cap
already installed in a Base.
the power is less than the circuit replace the Lightguide buildout connected to the
pack’s Edge Switch Receive Min IPFM’s GBIC1 TX connector with one with an
specified in the work order appropriate attenuation value. The figure in Step 8
shows the correct method for removing a Cap
already installed in a Base.
...................................................................................................................................................................................................
12 Connect the tested optical fiber cable to the GBIC1 RX port of the Edge switch.
...................................................................................................................................................................................................
13 NOTE: Ensure that the bending radius for a single fiber cable is not less than 30 mm
to avoid fiber micro banding and/or the breaking of the optical fiber cable.
Carefully wind and move the excess optical fiber cable from the IPFM circuit pack
into the cable duct of the rack.
Use the tie wraps as needed to secure the optical fiber cables to the grounding fingers
on the shelf.
NOTE: Do not overtighten the tie wrap or other means used to secure the fiber cable
slack as the fibers may be damaged.
...................................................................................................................................................................................................
system turn-up.
E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
7-82 363-211-555
Procedure of Gigabit Ethernet electrical cabling

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

...................................................................................................................................................................................................
2 Insert the electrical GBIC module on the GBIC(x) connector of the IPFM circuit pack.
Note that the yellow LED is turned on when a GBIC module is removed.
...................................................................................................................................................................................................
3 Connect the IPFM circuit pack via its electrical GBIC to a 1000Base-T-compatible
router or Edge switch for a Fast Ethernet connection. See the “Required equipment”
(p. 7-78) section of this procedure.
IF... THEN...
the 1000Base-T-cable assembly has been connect the RJ-45 connector of the twisted
installed pair cable to the GBIC(x) port on the
faceplate of the IPFM. Insert the other cable
connector in an RJ-45 connector on the
target router or Edge switch located in the
NOTE: The ″x″ in the expression GBIC(x)
stands for 1 or 2 of the IPFM in the
preferred or protection slot.
END OF STEPS
the 1000Base-T cable assembly has not route the twisted pair cable in the cable
been installed trough to the GBIC(x) port on the IPFM
circuit pack faceplate.
Connect the RJ-45 connector of the twisted
pair cable to the GBIC(x) port on the
faceplate of the IPFM. Insert the other cable
connector in an RJ-45 connector on the
target router or Edge switch located in the
....................................................................................................................................................................................................................................
363-211-555 7-83
...................................................................................................................................................................................................
system turn-up.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-84 363-211-555
Procedures used for VoIP service activation
Overview
...................................................................................................................................................................................................................................
Purpose
The following section provides the procedures used for VoIP service activation. Note
that it is strongly recommended to follow the procedure order that is provided in
Contents
Provision port parameters on a VoIP AP 7-86

Provision VoIP AP parameters 7-89
Provision/Retrieve SIP network protocol parameters 7-94
Provision/Retrieve H.248 network protocol parameters 7-100
Provision/Retrieve MGCP network protocol parameters 7-103
Wiring for VoIP APs 7-106
...................................................................................................................................................................................................................................
363-211-555 7-85
Provision port parameters on a VoIP AP

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision the individual port parameters on a VoIP AP. It can be
determined whether the provisioning should apply to an individual port only or to all
ports on the pack.
Procedure
...................................................................................................................................................................................................
1 If the VoIP System Turnup window is not yet open, from the menu bar select IP
Subsystem -> VoIP -> System...
Result The VoIP System Turnup window opens.
...................................................................................................................................................................................................
2 Select the tab Ports

...................................................................................................................................................................................................
3 Depending on whether you want to provision an individual port or all ports on the AP
select from the Port pull-down menu a dedicated port or select the Select All Ports
check box (for LPZ600 1-32 and for PLZ602 1-64 ports).
...................................................................................................................................................................................................
4 In the Control Parameters field enter the following parameters:

Options Default value Possible values Comments
Control Parameters
Operational State: In service In service Indicate the operational state of port.
Out of Service Read only.
Administrative Enabled Enabled When disabled no service is provided for the port.
State: Disabled
Hook Status: Off Hook Off Hook The hook status of the port.
On Hook Read only.
Admin Send Trap: Disabled Enabled When disabled no traps will be send to the OAM&P
Disabled interfaces.
Port Info: blank ASCII text Indicates a port location info or similar. Used for
provisional purpose only, not for call control.
Call Status: Not Active Not Active Indicate whether there is any call active on port.
Active Read only.
Active Codec: PCMU If there is a call active on the port, then this indicates the
codec being used for outgoing packets. Empty string means
no codec when there is no active call.
Read only.
...................................................................................................................................................................................................................................
7-86 363-211-555
Detailed procedure descriptions Provision port parameters on a VoIP AP
Port Dialing: Auto Dial-pulse Indicates the signaling type from this port.
Push button
Auto
Audio Codec AB, T38 A-PCMA Preferred audio codec in receiving direction.
Preference: B-PCMU G711 a-law (PCMA)
C-G726-32 (*) G711 u-law (PCMU)
D-G729 (*) G729AB
F-telephone-event G726-40 (40 kbit/s)
G-CN (*) G726-32 (32 kbit/s)
H-G726-16 (*) G726-24 (24 kbit/s)
I-G726-24 (*) G726-16 (16 kbit/s)
J-G726-40 (*) G723-5 (5.3 kbit/s)
K-G723-5 (*) G723-6 (6.3 kbit/s)
L-G723-6 (*) CN (comfort noise from far end subscriber)
M-T38 (*) telephone-event (DTMF digits according to RFC 2833
(*) Not supported by (only add-on, not valid without any other real codec))
LPZ600 T.38 Fax (only add-on, not valid without any other real
codec)
Voice Activity Disable Disable Indicate whether voice activity detection is performed on
Detection: EnConfortNoise the incoming voice of the locally connected subscriber.
Applicable only for LPZ602.
In the Statistics field the text line Percent Of Packet Loss displays the
percentage of lost packets.
...................................................................................................................................................................................................
5 In the Physical Parameters field enter the following parameters:
Options Default Possible values Comments

value
Transmit Gain (dB): 0.0 -40 - 80 in steps of 5. The exact range Transmit gain relative to the digital
depends on the VoIP customer key reference point, multiplied by 10.
code.
Receive Gain (dB): -7.0 -120 - 30in steps of 5. The exact range Receive gain relative to the digital
depends on the VoIP customer key reference point, multiplied by 10.
code.
Balance Network ID: 1 1 - 5 if VoIP customer key code is not Defines the balance network type of the
0. Otherwise the range depends on the port
VoIP customer key code.
CID Sig Performance: Default Default The preferred signaling method to be

Modem used for Calling Line Id Presentation
(CLIP).
Push-Button
Echo Canceller: 16 0..128 The tail length in milliseconds for the

echo canceler.
....................................................................................................................................................................................................................................
363-211-555 7-87
Detailed procedure descriptions Provision port parameters on a VoIP AP
...................................................................................................................................................................................................
6 Click Apply.
...................................................................................................................................................................................................

NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
If you want to return to the links for activating service for VoIP click on back to
activate service for VoIP.
....................................................................................................................................................................................................................................
7-88 363-211-555
Provision VoIP AP parameters

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision all parameters valid for a VoIP AP that apply to the
pack and/or to all ports on this AP.
Assumptions
Make sure that the AP(s) you want to provision is/are properly installed as described in
“AP Installation” (p. 7-24).
Check that the pack type is correctly provisioned as described in “Provision IP AP
slots” (p. 7-48)
Procedure
...................................................................................................................................................................................................
1 From the menu bar select IP Subsystem -> VoIP -> System...
or left-click the front of the AP that you want to configure.
...................................................................................................................................................................................................
2 In the section Module ID select the Shelf type and the Pack number you want to
provision.
...................................................................................................................................................................................................
3 In the General tab enter the following options for the system configuration:
Options Default Range Comments

value
Customer Key Code 0 0 - 255 Includes customer specific parameters like Control
(CKC): Protocol, soft switch type, country specific settings,
special services, etc.
Hook Duration Min 250 10 - 2000 Range for detecting a hook flash signal. If this field is
(msecs): empty the default value, defined by CKC, is used.
Hook Duration Max 1325 10 - 2000

(msecs):
Control Protocol: SIP SIP Control protocol between gateway and soft switch.
H.248 Depends on customer key code.
MGCP Read only.
Ring Pack Status: Up Operational status of the ring pack.

Down Read only.
...................................................................................................................................................................................................................................
363-211-555 7-89
Detailed procedure descriptions Provision VoIP AP parameters

value
Tip&Ring Cable: Present Indicates the status of the faceplate Tip&Ring cable(s).
Missing Present - indicates that the cable (at the LPZ602 both
Missing-2nd cables) is/are properly connected.
Missing-Both Missing - indicates that the cable (at the LPZ602 the
cable for ports 1-32) is not properly connected.
Only applicable for LPZ602:
Missing-2nd - indicates that the cable for the ports 33-64
is not properly connected while the cable for ports 1-32
is properly connected.
Missing-Both - indicates that both cables for the ports
1-32 and 33-64 are not properly connected.
Read only.
Administrative Status: Enabled Enabled Enable/disable the availability for call processing
Disabled Enable/disable the availability of an audible
Disabled Gracefully indication/announcement that the system is unavailable
Disable gracefully depends on subscriber’s hook state,
there are two cases:
1. If all subscribers are on-hook, the system will act
just as if the value is set to “disabled”.
2. If any subscriber is off-hook, then the VoIP
operational status will be set to “out-of-service-pending”,
the system will allow the subscriber to complete the
existing call.
Operation Status: In Service Indicates the operational status of the system.
Out-of-Service-
Pending
...................................................................................................................................................................................................
4 Set the Administrative Status to Enable.

...................................................................................................................................................................................................
5 Click Apply
...................................................................................................................................................................................................
6 Select the Network tab and enter the following options:
Options Default value Range Comments
Configuration Parameters
Public Network Status: up, down Read only.
Pack IP Address: Depends on the 0.0.0.0 - IP address of the VoIP AP. This address is used for
network 255.255.255.255 call control protocol and RTP streams
configuration
Network Mask: Depends on the 0.255.255.255 - Network mask of the public network interface for the
network 255.255.255.0 VoIP card
configuration
....................................................................................................................................................................................................................................
7-90 363-211-555
Default Gateway: Depends on the 0.0.0.0 - IP address of the default gateway

network 255.255.255.255
configuration
Domain Name Server Depends on the - May contain the IP addresses of the various domain
1: network name server.
configuration
Domain Name Server
2:
Domain Name Server

3:
TOS Control: 0 0 - 255 Defines the decimal value for the IPv4 TOS octet in
outgoing call control protocol packets. Used to
modify the Differentiated Services (DiffServ) code
point for call control packets, containing call control
protocol information.
Vlan ID: 1 1 - 4092 When tagging is enabled, all outgoing packets which
are not already tagged will be tagged with the VLAN
ID.
The VlanID must match the settings in the L2 VLAN
Configuration settings (IPFM provisioning).
For the LPZ600 this is the VLAN ID for all
originating traffic for the LPZ602 the VLAN ID for
the signaling traffic only.
Priority Tag: 0 0-7 Defines the 802.1p priority to be used to sign RTP.
For the LPZ600 this is the VLAN ID for all
originating traffic for the LPZ602 the VLAN ID for
the signaling traffic only.
Admin Status: Disabled Enabled If the VLAN Admin Status is enabled all outgoing
Disabled packets get the VLAN tag given by the VLAN ID
If the VLAN Admin Status is disabled no outgoing
packet will have a VLAN tag. For the LPZ600 this is
the VLAN ID for all originating traffic for the
LPZ602 the VLAN ID for the signaling traffic only.
RTP Configuration(only applicable for the LPZ602 starting with R3.3)
IP Address: 0.0.0.0 0.0.0.0 - The IP address specified here is used for RTP traffic.
255.255.255.255 Using a different IP address for RTP is optional.
Network Mask: 0.0.0.0 0.255.255.255 - The network mask of the IP address specified at
255.255.255.0 ’voipRtpIpAddress’.
Default Gateway: 0.0.0.0 0.0.0.0 - The default gateway for traffic originating from the
255.255.255.255 IP address specified at ’voipRtpIpAddress’, i.e. the
default gateway for the RTP traffic.
Vlan ID: 1 1..4092 The VLAN ID for traffic originating from the IP
address specified at ’voipRtpIpAddress’, i.e. the
VLAN ID for the RTP traffic.
Priority Tag: 0 0..7 The VPT (Vlan Priority Tag) field in 802.1Q header
for traffic originating from the IP address specified at
’voipRtpIpAddress’, i.e. the VLAN ID for the RTP
traffic.
Admin Status: Disabled Enabled Specifies whether the VLAN is enabled or disabled
Disabled for traffic originating from the IP address specified at
’rtpIpAddress’, i.e. the RTP traffic.
....................................................................................................................................................................................................................................
363-211-555 7-91
...................................................................................................................................................................................................
7 Click Apply.
...................................................................................................................................................................................................
8 Select the Media tab and enter the following options:

value
Media RTP Parameters
Audio Codec Preference: AB, T38 A-PCMA Preferred audio codec in receiving direction.
B-PCMU G711 a-law (PCMA)
C-G726-32 (*) G711 u-law (PCMU)
D-G729 (*) G729AB
F-telephone-event G726-40 (40 kbit/s)
G-CN (*) G726-32 (32 kbit/s)
H-G726-16 (*) G726-24 (24 kbit/s)
I-G726-24 (*) G726-16 (16 kbit/s)
J-G726-40 (*) G723-5 (5.3 kbit/s)
K-G723-5 (*) G723-6 (6.3 kbit/s)
L-G723-6 (*) CN (comfort noise from far end subscriber)
M-T38 (*) telephone-event (DTMF digits according to RFC
(*) Not supported by 2833 (only add-on, not valid without any other real
LPZ600 codec))
T.38 Fax (only add-on, not valid without any other
real codec)
Minimum Port #: 8000 1000 - 65436 Is used for receiving the RTP stream. The difference
between min and max must be at least 100. Each
Maximum Port #: 8999 1101 - 65534 new call uses the next port.
Jitter Buffer Size 20 10 -200 This parameter defines also the downstream delay of
(msecs): the VoIP AP
Jitter Buffer Type: Dynamic Dynamic Defines whether the jitter buffer size is fixed and
Fix non-adapative or whether the jitter buffer size
dynamically adapts to the jitter of the received
packets.
TOS: 0 0 - 255 The TOS bits of RTP packets the VoIP pack sends
RTCP Admin State: Disabled Enabled Real Time Control Protocol can be enabled/disabled.
Disabled Enabled causes an overhead RTP traffic
G711 Packet Interval 20 10 - 100 The RTP packet interval in milliseconds for the
(msecs): G.711 (PCMA/PCMU) codec.
Valid values for LPZ600: 20,30,40,50,60,70,80,90,
100 (Default: 20)
for LPZ602: 10,20,30,40,50,60 (Default: 10)
G726 Packet Interval 10 10 - 60 Not applicable for LPZ600
(msecs): Valid values for LPZ602: G726-16/24/40: 10,20,30
G726-32: 10,20,30,40,50,60
....................................................................................................................................................................................................................................
7-92 363-211-555

value
G729 Packet Interval 10 10 - 80 Not applicable for LPZ600

(msecs): Valid values for LPZ602: 10,20,30,40,50,60,70,80
(Default: 10)
G723 Packet Interval 30 30 - 60 The RTP packet interval in milliseconds for the
(msecs): G723.1 codec.
Not applicable for LPZ600, any value is ignored
Valid values for LPZ602: 30,60 (Default: 30)
Monitor RTP Stream parameters

Media Monitor Host: The media monitor host for both inbound and
outbound directions.
Inbound Port: 1 1 - 65535 Inbound voice monitor port.
Outbound Port: 1 1 - .65535 Outbound voice monitor port.

Media Monitor Control: Off Off Voice monitor control.
Inbound
Outbound
Both-Direction
Media Monitor Port: 1 1 - 64 The port to be monitored.
...................................................................................................................................................................................................
9 Click Apply.
...................................................................................................................................................................................................

NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
363-211-555 7-93
Provision/Retrieve SIP network protocol parameters

...................................................................................................................................................................................................................................
Purpose
In a system that is configured via the customer key code to support SIP protocol, use
this procedure to provision the SIP protocol parameters for all ports on the VoIP AP.
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Select the tab SIP

Result: Four subtabs appear on the VoIP System Turnup window
• Digit Map
• Control
• Transport
• Service
The Port pull-down menu is active.
...................................................................................................................................................................................................
3 Select the Digit Map subtab and enter the appropriate digit map configuration
parameters. Then click Apply.

value
Start Timer (secs): 45 0 - 3600 Specifies the time in secs to wait for the first digit after off-hook.
Short Timer (secs) 4 0 - 3600 Is used when ambiguous digit pattern must be distinguished (e.g. 0 |
00)
Long Timer (secs): 12 0 - 3600 Defines the max. interdigit time. If this timer expires, the dialed
number was incomplete and the VoIP AP will generate an error tone
towards the subscriber
Default Digitmap Alpha numeric string without blank space. This field is not used by SIP.
Name:
Default Digitmap: [0 - 9], [A - Digit Map symbols are “0” - “9”, “*” and “#”.
F], [*], [.] Up to 256 characters are supported.
The Digitmap can de edited using the key board or click Digit Map
Generator to open a support window.
Digit Map Generator Clicking on this button opens a support window which allows the user
to define a digitmap in a comfortable manner.
Option buttons:
...................................................................................................................................................................................................................................
7-94 363-211-555
Detailed procedure descriptions Provision/Retrieve SIP network protocol parameters

value
Default Map - Port Default Default Map Select if the Default Map (valid per pack) or the Port Map (valid per
Map Map Port Map port) should be displayed.
If a Port Map is defined, the Default Map is not used for the
corresponding port. If no Port Map is defined, the corresponding port
uses the Default Map.
NOTE: The Apply button has immediate effect for future calls, but will not affect
current active calls!
...................................................................................................................................................................................................
4 Select the subtab Control and enter the appropriate SIP control configuration
parameters:
Local Port: 5060 1000 - 65535 The local UDP port to receive call control
protocol messages from softswitch
Outbound Proxy Host: Depends on the Optional information. IP address of the
network proxy via which all messages are sent to the
configuration IP network (Route header information).
Outbound Proxy Port: 5060 1..65535 Optional information. Port number of the
proxy via which all messages are sent to the
IP network (Route header information).
Emergency Rtp TOS: 0 TOS field of the RTP stream for emergency
calls.
Emergency Ctrl TOS: 0 TOS field of the control messages for
emergency calls.
Emergency Numbers: 110, 118, 119 List of emergency numbers, separated by
comma, without white space and unique
numbers.
Allowed symbols are “0” - “9” and “A” -
“F”:
Desired Session Interval (secs): 1800 0 - 65535 Used to negotiate the Session Interval time
Within this Interval time, keep alive
Min Session Interval (secs): 90 90 - 65535 messages (re-invite) must be received, or
the connection is disrupted
Call Priority Thresholds
Emergency: 100 0 - 100 The resource threshold for calls of this

priority. At most this percentage of system
Urgent: 100 0 - 100 resources will be used for a call of this
Normal: 100 0 - 100 priority
Non Urgent: 100 0 - 100
...................................................................................................................................................................................................
5 Select the subtab Transport and enter the appropriate SIP transport configuration
parameters:
....................................................................................................................................................................................................................................
363-211-555 7-95
Control status: Read only

Indicate whether VoIP application is ready to
communicate with SIP proxy
Proxy Host: Depends on the In case a Proxy Server is available enter IP address
network and port of this server
configuration
Proxy Port: 5060 1 - 65535
Registrar Host: Depends on the The registrar host is responsible for converting
network registration ID to telephone number
configuration
Registrar Port: 5060 1 - 65535
Registration ID: Subscriber’s SIP URL in the format of

user@host:port, where user part is alphanumeric
character not relating to the phone number, host part
is alphanumeric character not relating to SIP IP
address.
If portion ‘@host:port’ is omitted, Proxy Host or
Registrar Host values are used as domain name.
Contact User Name: line 1 The username portion of the contact address. It is
line 2 case sensitive. (INVITE method information, Contact
header information)
etc.
Contact Parameter: This field adds a parameter-value pair to the
registration contact.
Use of this field causes non-standard INVITE
messages. The form of the string is param=value. If
the value portion is omitted, the Contact User Name
value is used.
Auth User Name: auth3 The user name for authorization.
If omitted, the username portion of the Registration
ID is used. This is case sensitive.
Auth Password: The SIP password for the port.
Register On Startup: Enable Enable When set to enable SIP shall register on start up.
Disable
Expiration Interval 32,000 1 -65535 This is the expiry time for a registration message
(mins):
Preferred Identity: None none, Indicates which value should be used in
Parent Hunt P-Preferred-Identity message.
Group,
Per-Line,
Preferred
number
Preferred Number: Arbitrary notification number used in
P-Preferred-Identity header.
Multi Hunt URL: Multiple hunt group parent (or pilot) URL.
DNS Address Caching Checkbox

Enabled:
....................................................................................................................................................................................................................................
7-96 363-211-555
Subscriber Priority: Normal Emergency The priority level from non-emergency calls for this
Urgent subscriber
Normal
Non Urgent
Table View Button Clicking this button pops up a Table View of all ports
transport configuration parameters listed by port
number in a separate screen as overview
...................................................................................................................................................................................................
6 Select the subtab Service and enter the appropriate configuration parameters to control
the services for each port:
Inbound Caller ID: Disable-All Enable-All (caller Controls whether the caller ID info (number
number and name is and name) should be displayed for inbound
displayed) calls to this port. (CLIP function)
Enable-Number-Only
(caller number is
displayed)
Disable-All (no caller
number/name is
displayed)
Outbound Caller ID UnBlock Block (restriction to Controls whether the caller ID info (number
Blocking: show the caller number and name) should be blocked for all
at the terminating side) outbound calls from this port. (CLIR
UnBlock (caller function)
number/name may be
displayed at the
terminating side
Call Waiting: Disable Enable Controls whether the call waiting service
Disable should be enabled for normal calls.
Anonymous Call Rejection: Disable Enable Controls whether this port should reject
Disable anonymous calls. ’Disable’ means no call
will be rejected.
Extension Ringing: None None Controls the extension ringing signal.
Ir
Sir
Emergency Call Hold: Enable Enable If enabled, the call is kept on-hold even if a
Disable disconnect signal on the subscriber port is
detected.
....................................................................................................................................................................................................................................
363-211-555 7-97
Emergency CID Block: Block Block (permits the user Display of caller/number can be
to block caller ID blocked/unblocked
display for emergency
calls by dialing “184”
prefix)
UnBlock (the users
caller ID information is
always displayed for
emergency calls. The
“184” prefix is ignored
Exclude Emcy Numbers: Depends on the Empty Disables the use of these emergency
Emergency numbers per port.
number list
provisioned in the
Control tab
Emergency RingStart: 0 0 - 60 Time after which a subscriber phone starts

ringing again after dialing an emergency
number and an accident hang-up of the
phone.
Emergency RingStop: 0, this indicates 0 - 600 Maximum time for which ringing signal
no stop of ringing shall be send to the subscriber in case of an
signal on-hook during emergency call
Number Translation: [0 - 9], [A - F] This parameter supports the omitted (or
abbreviated) dialing feature. The format is:
abbrevString=assignedString separated by
“;”
Direct Dial In Signaling: None None Signaling method for direct dial in service
Modem towards the subscriber port for terminating
calls
Push-Button
Extension Signaling: None None Signaling method for extension connection
Modem service towards the subscriber port for
terminating calls
Push-Button
Subscriber Class ID: 1 1 - 100 used for ease of provisioning by NAM
Subscriber Class Version: 1 1 - 60000 used for ease of provisioning by NAM
Inbound Call Waiting Caller Disable-All Enable-All (caller Controls whether the caller ID info (both
ID: number and name are number and name) should displayed for
displayed) inbound calls during call waiting
Enable-Number-Only
(caller number is
displayed)
number/name is
displayed)
Originator Ring T out: 485 10 - 600 Timer value for abandoning outbound
(originating) call requests
Term Ring T out: 485 1 - 600 timer value for abandoning inward
(terminating) call requests
....................................................................................................................................................................................................................................
7-98 363-211-555
PB Signaling Digits Len: 0 1 For DID signaling, a phone number is sent

2 in the did= field. For PB mode DID
signaling (Push Button, or DTMF), these
3 phone numbers are trimmed downed to the
4 last N digits.
3 Way Calling: Disable Enable enable/disable the feature for SIP

Disable
Music on hold: Disable Enable enable/disable the feature
Disable
Msg Waiting Indicator: none none This parameter is used to activate and
audible configure the type of message waiting
indication (MWI) feature for a VoIP port.
visual
none: deactivates the MWI feature.
both
audible: activates an audible indication
towards the subscriber, e.g. a customer key
code dependent special dial tone is used
instead of the normal dial tone at
originating call attempts.
visual: activates a customer key code
dependent line signaling to trigger a visual
indication on the subscriber equipment, e.g.
the activation of a light or info text in an
display.
Note: The subscribers equipment must
support the special line signaling which
transfers the info of waiting message(s) to
it.
both: activates both the audible and visual
indication.
Not supported by LPZ600.
...................................................................................................................................................................................................
7 Click Apply.
...................................................................................................................................................................................................

NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
363-211-555 7-99
Provision/Retrieve H.248 network protocol parameters

...................................................................................................................................................................................................................................
Purpose
In a system that is configured via the customer key code to support H.248 protocol,
use this procedure to provision the H.248 protocol parameters for all ports on the VoIP
AP.
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Select the tab H.248

Result: Two subtabs appear on the VoIP System Turnup window.
• Digit Map
• Transport
The Port pull-down menu is active.
...................................................................................................................................................................................................
3 Select the Digit Map subtab and select either an individual port or click on the check
box Select All Ports. Enter the following options. Then click Apply.
Start Timer (secs): 45 0 - 3600 Specifies the time in seconds to wait for
the first digit after off-hook. Value
0-means infinity
Short Timer (secs): 8 0 - 3600 Is used when ambiguous digit pattern
must be distinguished (e.g. 0|00) on
expiry, the already matching pattern is
used
Long Timer (secs): 12 0 - 3600 Defines the maximum inter-digit time. If

this timer expires, the dialed number was
incomplete (too short) and the VoIP pack
will generate an error tone towards the
subscriber
Default Digitmap Name: defaultDM Alpha-numeric string without blank space
Default Digitmap: (0|00|[2-9]xxxxxx|*[1- Up to 256 Digit Map symbols are ″0″ - ″9“, “*″ and
7]x|1xxxxxxxxxx|*[8- characters are “#″.
9]xxxxxxxxxx) supported Up to 256 characters are supported.
The Digitmap can de edited using the key
board or click Digit Map Generator to
open a support window.
...................................................................................................................................................................................................................................
7-100 363-211-555
Detailed procedure descriptions Provision/Retrieve H.248 network protocol parameters
Digit Map Generator Clicking on this button opens a support

window which allows the user to define a
digitmap in a comfortable manner.
Option buttons:
Default Map - Port Map Default Map Default Map Select if the Default Map (valid per pack)
Port Map or the Port Map (valid per port) should be
displayed.
If a Port Map is defined, the Default Map
is not used for the corresponding port. If
no Port Map is defined, the corresponding
port uses the Default Map.
...................................................................................................................................................................................................
4 Select the subtab Transport and enter the appropriate H.248 transport configuration
parameters:.
The Port pull-down menu is now inactive. That is, these parameters are valid for the
entire AP.
Application Status: Ready Ready Indication whether the VoIP application is ready
Not Ready to communicate with the Media Gateway.
Read only.
Local Port: 2944 This is the local UDP or TCP port in the gateway
to receive H.248 call control protocol messages
from softswitch. The transport protocol (UDP or
TCP) is controlled by the customer key code
(CKC).
Primary Host: 10.10.36.252 This parameter defines the IP address of the
H.248 primary media gateway controllers.
Primary port: 2944 1 ... 65535 This parameter defines the port number of the
primary media gateway controller.
Connection Timeout: 0 Number of seconds the AnyMedia times out the
connection to the H.248 MG controller. A value
of “0” indicates no timeout
Register On Startup: Enable Enable
Disable
Encoding: h248text h248text H.248 message coding
h248binary
Version h248v1 h248v1 H.248 version number
h248v2
Security Parameter Idx: 6600 Security Parameter Index (SPI) field
Authentication Algorithm: hmac-md5-96 hmac-md5-96 The algorithm used for H.248 authentication
hmac-sha1-96 header
....................................................................................................................................................................................................................................
363-211-555 7-101
Detailed procedure descriptions Provision/Retrieve H.248 network protocol parameters
Authentication Key: lucent_amas_voip The key string for H.248 authentication header
Authentication Admin State: Disable Enable Enable or disable H.248 authentication header
Disable
DNS Address Caching off on Turns on / off control protocol tracing (checkbox)
Enabled off
...................................................................................................................................................................................................
5 Click Apply.
...................................................................................................................................................................................................

NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
7-102 363-211-555
Provision/Retrieve MGCP network protocol parameters

...................................................................................................................................................................................................................................
Purpose
In a system that is configured via the customer key code to support MGCP protocol,
use this procedure to provision the MGCP protocol parameters for all ports on the VoIP
AP.
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Select the tab MGCP.

Result: Three subtabs appear on the VoIP System Turnup window
• Digit Map
• Transport
• Service.
...................................................................................................................................................................................................
3 Select the Digit Map sub, and define following parameters:
Start Timer (secs): 16 0..3600 Specifies the time in secs before the first digit is expected. The
value 0 means infinity, i.e., the gateway wait for the first digit
forever.
Short Timer (secs): 10 0..3600 If the digit string collected has matched one of the patterns in a
digit map, but it is possible that more digits could be received
which would cause a match with a different pattern, then instead
of reporting the match immediately, the MG must apply the
short timer (number of seconds) and wait for more digits.
Long Timer (secs): 12 0..3600 If the gateway can determine that at least one more digit is
needed for a digit string to match any of the allowed patterns in
the digit map, then the interdigit timer value is set to this
number of seconds.
Default Digitmap Alpha numeric string without blank space.
Name:
Default Digitmap: The default digitmap for the port.

The Digitmap can de edited using the key board or click Digit Map Generator to open a support
window.
...................................................................................................................................................................................................
4 Click Apply.
...................................................................................................................................................................................................................................
363-211-555 7-103
Detailed procedure descriptions Provision/Retrieve MGCP network protocol parameters
...................................................................................................................................................................................................
5 Select the subtab Transport and enter the appropriate MGCP transport configuration
parameters:
Control Status: Ready Ready Indicate whether VOIP application is ready to communicate
Not-Ready with call agent.
Read-only.
Local Port: 2427 1000..4000 This is the local UDP or TCP port in the gateway to receive
call control messages from call agent. The transport
protocol (UDP or TCP) is controlled by the customer key
code (CKC).
Agent Host: 255.255.255.255 Primary media gateway controller’s IP address.
Agent Port: 2427 1..65535 The port number of the call agent.
Register on Disable Enable Indicate whether gateway should send registration message
Startup: Disable to call agent at start up.
...................................................................................................................................................................................................
6 Click Apply.
...................................................................................................................................................................................................
7 Select the subtab Service and enter the appropriate configuration parameters to control
the services for each port:
Direct Dial In Modem Modem Signaling method for Direct Dial-In service if requested by
Signaling: Push-Button the Media Gateway Controller.
PB Signaling 0 0..4 Specifies how many digits, from the end of the complete
Digits Len: digit string, shall be signaled towards the PBX at
’push-button’ Dial-In Signaling mode. In ’modem’ Dial-In
Signaling mode all digits are signaled to the PBX in any
case. The value 0 means that all digits are to be signalled.
...................................................................................................................................................................................................
8 Click Apply.
...................................................................................................................................................................................................

NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
7-104 363-211-555
Detailed procedure descriptions Provision/Retrieve MGCP network protocol parameters
....................................................................................................................................................................................................................................
363-211-555 7-105
Wiring for VoIP APs

...................................................................................................................................................................................................................................
Purpose
This procedure provides information on how to wire the VoIP AP LPZ600 with 32
subscriber ports and the 64 port VoIP AP LPZ602, that is wiring information for the
packs when they operate in controlled mode and for the LPZ600 in stand-alone mode.
The LPZ602 does not support stand-alone mode.
This procedure describes:
• How to connect the a/b cables (tip/ring cables) on the subscriber side to the
faceplate of the VoIP APs
• The cabling for the uplink to the IP network. The uplink cabling is required for
stand-alone mode (LPZ600 only).
The connection to the serial port is determined for initial system turn-up in stand-alone
mode only and is therefore described in the procedures for stand-alone mode. The
connection to the serial port does not apply to the LPZ602.
The OAM&P management is done via an inband management channel and does not
require any wiring.
Cables
Cable assemblies for VoIP APs (LPZ600 and LPZ602):
Connector on Interface for Cable description Cable

faceplate
Subscriber cabling on LPZ600:

POTS a/b cabling Shielded a/b cables connectorized on one ED7C873-31 G2x
(Select one of these end with a special AP connector;
options) No external ferrite kits required (except
for LAG 200 shelves)
Shielded a/b cables connectorized on both ED7C873-31 G4x

ends with special AP connectors;
No external ferrite kits required
Subscriber cabling on LPZ602:
...................................................................................................................................................................................................................................
7-106 363-211-555
Detailed procedure descriptions Wiring for VoIP APs

faceplate
POTS P1 and a/b cabling Shielded a/b cables (2×32 pairs on ED7C873-31 G1x
POTS P2 (Select one of these connectors P1 and P2 for 64 port APs)
options) Connectorized on one end with two
special AP connectors;
Unshielded a/b cables for use in LAG ED7C873-31 G39x

4300 (2×32 pairs for 64 port AP)
Connectorized on one end with two
special AP connectors;
Shielded a/b cables (2×32 pairs for 64 ED7C873-31 G3x
port APs
Connectorized on both ends with special
AP connectors;
Additional cabling for stand-alone mode (not applicable for LPZ602):
10/100Base-Tx 10/100Base-T uplink Wired straight-through, Commercially

(for stand-alone mode RJ-45 connectors available 100Base-T
only) cable
Pin assignment of subscriber interface on LPZ600

The a/b connector on the VoIP AP LPZ600 is different from the a/b connector used for
POTS APs. The figure below shows the pin assignment for the a/b connector of the
VoIP AP LPZ600. Shown is the wiring / soldering side of the a/b cable connector
which is identical to the contact side of the AP.
....................................................................................................................................................................................................................................
363-211-555 7-107
Shown is the wiring/soldering side of the

AP cable connector of the a/b-cable
(identical to the contact side of the AP)
Short
Tip32 Y/BL 64 32 BL/Y Ring32

Tip31 BK/S 63 31 S/BK Ring31
Tip30 BK/BR BR/BK Ring30
Tip29 BK/G G/BK Ring29
Tip28 BK/O O/BK Ring28
Tip27 BK/BL BL/BK Ring27
Tip26 R/S S/R Ring26

Tip25 R/BR BR/R Ring25
Tip24 R/G G/R Ring24

Tip23 R/O O/R Ring23
Tip22 R/BL BL/R Ring22
Tip21 W/S S/W Ring21
Tip20 W/BR BR/W Ring20

Tip19 W/G G/W Ring19
Tip18 W/O O/W Ring18
Tip17 W/BL BL/W Ring17
Tip16 Y/BL BL/Y Ring16
Tip15 BK/S S/BK Ring15
Tip14 BK/BR BR/BK Ring14
Tip13 BK/G G/BK Ring13
Tip12 BK/O O/BK Ring12
Tip11 BK/BL BL/BK Ring11
Tip10 R/S S/R Ring10

Tip9 R/BR BR/R Ring9
Tip8 R/G G/R Ring8

Tip7 R/O O/R Ring7
Tip6 R/BL BL/R Ring6
Tip5 W/S S/W Ring5
Tip4 W/BR BR/W Ring4

Tip3 W/G G/W Ring3
Tip
Tip2 W/O O/W Ring2
34 2
Tip1 W/BL BL/W Ring1
36
33 12
Short
Wiring side
Pin assignment of subscriber interface on LPZ602

The a/b connectors on the VoIP AP LPZ602 are different from the a/b connectors used
for POTS APs. The figure below shows the pin assignment for the a/b connectors of
the VoIP AP LPZ602. Shown is the wiring / soldering side of the a/b cable connectors
which are identical to the contact side of the AP.
....................................................................................................................................................................................................................................
7-108 363-211-555
Shown is the wiring/soldering side of the Shown is the wiring/soldering side of the
AP cable connector of the a/b-cable AP cable connector of the a/b-cable
(identical to the contact side of the AP) (identical to the contact side of the AP)
Tip32 Y/BL BL/Y Ring32 Tip64 Y/BL BL/Y Ring64

64 32 64 32
Tip31 BK/S S/BK Ring31 Tip63 BK/S S/BK Ring63
63 31 63 31
Tip30 BK/BR BR/BK Ring30 Tip62 BK/BR BR/BK Ring62
Tip29 BK/G G/BK Ring29 Tip61 BK/G G/BK Ring61
Tip28 BK/O O/BK Ring28 Tip60 BK/O O/BK Ring60
Tip27 BK/BL BL/BK Ring27 Tip59 BK/BL BL/BK Ring59
Tip26 R/S S/R Ring26 Tip58 R/S S/R Ring58
Tip25 R/BR BR/R Ring25 Tip57 R/BR BR/R Ring57
Orange Orange Brown Brown
binder Tip24 R/G G/R Ring24 binder binder Tip56 R/G G/R Ring56 binder
Tip23 R/O O/R Ring23 Tip55 R/O O/R Ring55

Tip22 R/BL BL/R Ring22 Tip54 R/BL BL/R Ring54
Tip21 W/S S/W Ring21 Tip53 W/S S/W Ring53
Tip20 W/BR BR/W Ring20 Tip52 W/BR BR/W Ring52
Tip19 W/G G/W Ring19 Tip51 W/G G/W Ring51
Tip18 W/O O/W Ring18 Tip50 W/O O/W Ring50
Tip17 W/BL BL/W Ring17 Tip49 W/BL BL/W Ring49
Tip16 Y/BL BL/Y Ring16 Tip48 Y/BL BL/Y Ring48
Tip15 BK/S S/BK Ring15 Tip47 BK/S S/BK Ring47
Tip14 BK/BR BR/BK Ring14 Tip46 BK/BR BR/BK Ring46
Tip13 BK/G G/BK Ring13 Tip45 BK/G G/BK Ring45
Tip12 BK/O O/BK Ring12 Tip44 BK/O O/BK Ring44
Tip11 BK/BL BL/BK Ring11 Tip43 BK/BL BL/BK Ring43
Tip10 R/S S/R Ring10 Tip42 R/S S/R Ring42
Tip9 R/BR BR/R Ring9 Tip41 R/BR BR/R Ring41
Blue Blue Green Green
binder Tip8 R/G G/R Ring8 binder binder Tip40 Ring40 binder
R/G G/R
Tip7 R/O O/R Ring7 Tip39 R/O O/R Ring39
Tip6 R/BL BL/R Ring6 Tip38 R/BL BL/R Ring38
Tip5 W/S S/W Ring5 Tip37 W/S S/W Ring37
Tip4 W/BR BR/W Ring4 Tip36 W/BR BR/W Ring36
Tip3 W/G G/W Ring3 Tip35 W/G G/W Ring35
Tip2 W/O O/W Ring2 Tip34 W/O O/W Ring34
34 2 34 2
Tip1 W/BL BL/W Ring1 Tip33 W/BL BL/W Ring33
33 1 33 1
LPZ602 POTS connector P1 (Wiring side) LPZ602 POTS connector P2 (Wiring side)
Color coding
Pin assignment for 10/100Base-T uplink cabling (for stand-alone mode only)
The following table shows the pin assignment for a 10/100Base-T uplink connection to
the LPZ600 in stand-alone mode. A straight-through cable connection is used for this
purpose.
RJ45 connector on the Signal RJ45 connector on Signal

pack connection point in the
IP/Ethernet network

4 Frameground 4 Frameground
....................................................................................................................................................................................................................................
363-211-555 7-109

IP/Ethernet network

Assumptions
The following is assumed:
• The VoIP APs are inserted in the correct slots.
• The a/b cables are installed in the rack.
• If the pack has to operate in stand-alone mode, the uplink cable is installed in the
rack.
Procedure
...................................................................................................................................................................................................
1
IF... THEN...
the VoIP AP is an LPZ600 Push the cable connector to the POTS
connector on the faceplate.
the VoIP AP is an LPZ602 Push the cable connector which is labeled
″P2″ to the upper POTS connector on the
faceplate so that the cable exits the
connector downwards.
Then push the cable connector which is
labeled ″P1″ to the lower POTS connector
so that the cable also exits the connector
downwards.
...................................................................................................................................................................................................
2 Tighten the connector (s) with two screws, one at the top and one at the bottom of
each connector.
....................................................................................................................................................................................................................................
7-110 363-211-555
Result: The FAULT LED on the AP extinguishes.

Failure conditions: If the FAULT LED lights permanently, check the following
possible causes:
• Is the faceplate connector properly fixed?
If the screws are not tight, an alarm tip/ring cable disconnect will raise.
• Is the cable faulty?
Try another cable.
• Is the AP or the connector on the faceplate of the AP faulty?
Replace the AP.
...................................................................................................................................................................................................
3 IF... THEN...
the AP will operate in controlled mode End of Steps
the AP will operate in stand-alone mode connect a 100Base-T cable for the uplink
to the 10/100Base-Tx port.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-111
Procedures used for ICAP service activation
Overview
...................................................................................................................................................................................................................................
Purpose
The following section provides the procedures used for ICAP service activation. Note
Contents
Provision ICAP parameters 7-113

Provision/retrieve feeder parameters on an ICAP 7-118
Provision/retrieve ICAP profiles 7-125
Provision/retrieve network protocol parameters 7-130
Provision/retrieve H.248 port parameters on an ICAP 7-138
Provision/retrieve MGCP port parameters on an ICAP 7-143
Provision/retrieve SIP port parameters on an ICAP 7-148
Provision duplex ICAPs in controlled mode or stand-alone mode 7-155
(optional)
Provision VLANs, IP addresses and Routing on ICAP 7-157
Provision parameters for V5.2 aggregation on an ICAP 7-165
Wiring for ICAPs 7-174
...................................................................................................................................................................................................................................
7-112 363-211-555
Provision ICAP parameters

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision all parameters valid for an ICAP that apply to the pack
and/or to all ports on this AP.
Assumptions
slots” (p. 7-48)
Before you begin

The following procedure shows you how to provision ICAP parameters using the
following tabs of the GSI System Turnup window:
• System Configuration
• Timing Source Control
• IP Interface
• IP Routing
• VLAN
Procedure
...................................................................................................................................................................................................
1 From the menu bar select IP Subsystem -> ICAP -> System -> General...
...................................................................................................................................................................................................
2 In the section Module ID select the Shelf type the Pack, Group and the Port number
you want to provision.
...................................................................................................................................................................................................
3 In the subtab System Configuration set the appropriate options for the system
configuration parameters:

value
Operational Status: Up Up Indicates the operational status of the ICAP. Read only.
Down
...................................................................................................................................................................................................................................
363-211-555 7-113
Detailed procedure descriptions Provision ICAP parameters

value
Customer Key Code (CKC): 28 0 - 255 Includes customer specific parameters like Control
Protocol, soft switch type, country specific settings, etc.
define also the network protocol and the feeder
protocol.
Changing the CKC results in a reset of the system.
Control Protocol: SIP SIP Control protocol between gateway and softswitch.
H.248 Depends on customer key code.
MGCP Read only.

To configure the control protocol, follow the
“Provision/retrieve network protocol parameters ”
DNS Address Caching off on Turns on / off control protocol tracing (checkbox)
Enabed: off
Protection Mode: Simplex Simplex Indicates the operational mode simplex or duplex.
Duplex Note: Do not connect the E1/DS1 Y-cable to the ICAPs
before setting the ICAP to duplex mode.
Read only.
Mgmnt IP Address (N/A in 0.0.0.0 The management IP address for a system operating in
Controlled Mode): stand-alone mode.
Note that the IP address specified here is only a
reference and not a real IP interface definition. The IP
address must exist in the icapVlanTable, otherwise it
will not be usable and no management will be possible.
A pre-provisioning, while in controlled mode, of the
management IP address is possible as at the switch to
stand-alone operation this data will be retained and then
the management IP interface is activated.
...................................................................................................................................................................................................
4 Click Apply.
Note: The ICAP will reset automatically when the CKC is applied. Wait until the ICAP
recovers before continuing.
...................................................................................................................................................................................................
5 Select the subtab Timing Source Control and define the following parameters:
Control Mode: free-running free-running Indicates the synchronization source from which
external the ICAP timing is be derived
Primary source: fdr-1 fdr-1...fdr-8 The address of the primary physical

bpsync-1 synchronization source to be used
bpsync-2
afm-1
core-1
....................................................................................................................................................................................................................................
7-114 363-211-555
Secondary source: fdr-1 fdr-1...fdr-8 The address of the secondary physical

bpsync-1 synchronization source to be used
bpsync-2
afm-1
core-1
Sync Control Master: no no Specifies, if the pack should output a clock
pri-to-bp-pri signal to the bpsynch1, bpsynch2 lines on the
backplane
sec-tobpsec
active-to-bppri
Active Source: free-running free-running This parameter shows the currently active
primary synchronization source.
secondary Read only.
Sync Switch Action: other other Allows manual switch of the active clock input
sw-to-primary from primary to secondary or from secondary to
primary, given a valid clock to which to. If the
sw-to-secondary active clock source fails, the switch to the other
is done automatically
...................................................................................................................................................................................................
6 Select the subtab IP Interface and set the appropriate parameters for the IP Interface:
IP Interface Index: roc-1 roc-1 to roc-8 The index for logical IP Interfaces and the logical
ROC ports.
Admin State: Enable Enable Enable/disable the availability for call processing
Disable Enable/disable the availability of an audible
indication/announcement that the system is
unavailable
IP Address: Depends on the 0.0.0.0 - IP address of the ICAP AP. This address is used
network 255.255.255.255 for call control protocol and RTP streams
configuration
Network Mask: Depends on the 0.255.255.255 - Network mask of the public network interface for
network 255.255.255.0 the ICAP card
configuration
Remote IP Address: 0.0.0.0 IP address of the remote end of the point-to-point
link
...................................................................................................................................................................................................
7 Select the subtab IP Routing, in the Routing Policy panel enter the appropriate
parameters:
Routing Policy Index: 1 1..10 The index for the routing policy rules.
Source IP Address: 0.0.0.0 0.255.255.255 - The source IP address or subnet address

255.255.255.0 respectively of the packet to match this rule.
....................................................................................................................................................................................................................................
363-211-555 7-115
Source Net Mask: 255.255.255.255 0.0.0.0 - This network mask defines which bits of the
255.255.255.255 source IP address of the packet have to match
the ICAP Routing Policy Src. IP Address.
Examples: To exactly match the source IP
addresses used for Signaling, RTP or
Management, provision the exact IP address in
ICAP Routing Policy Src. IP Address table and
specify a host mask of ’255.255.255.255’ here.
To match the source IP addresses used, e.g. on
the downstream remote operation channels,
provision only the aggregate net address in ICAP
Routing Policy Src. IP Address and specify a net
mask of e.g. ’255.255.255.0’ here.
Route Table Index: 1 1..4 Specifies the table index to be used in the Static
Route Table if the packet matches this rule.
...................................................................................................................................................................................................
8 Select the Static Route Table panel and enter the appropriate parameters:
Route Table Index: 1 1..4 The IP static routing table for the system.
Destination IP Address: 0.0.0.0 The destination address is the network or host
IP address reached via this route.
Use a 0.0.0.0 destination with a 0.0.0.0
network mask to indicate a default route. Use
an IP address with a 255.255.255.255
submask to indicate a host route.
Network Mask: Depends on the 0.255.255.255 - Network mask of the destination.

network 255.255.255.0
configuration
Gateway: none 0.0.0.0 - 255.255.255.255 The default gateway for the IP route. The
gateway address is the IP address of the
gateway through which packets are sent to the
destination address. The gateway must be on
a directly connected network or subnetwork,
that means the gateway’s network portion of
an IP address and the corresponding
interface’s network portion of an IP address
must match.
TOS bit policy: Fixed to 0 The TOS bits routing policy is not
implemented yet.
...................................................................................................................................................................................................
9 Click Apply.
...................................................................................................................................................................................................
10 Select the VLAN subtab, and enter the appropriate parameters:
....................................................................................................................................................................................................................................
7-116 363-211-555
Options Default Possible Comments

value values
Vlan ID: 1 1...4091 The 12-bit VLAN ID used in the VLAN Tag header.
VLAN ID 4092 to 4095 are reserved for system-internal use and
therefore excluded here.
Vlan Name: The name of this VLAN must be unique across all VLANs.
IP Address: The IP address of the logical IP interface on this VLAN. The IP
address must be unique across all interfaces (including the Remote
Operations Channel interfaces specified in the IP Interface table).
Subnet Mask: The network mask for the logical IP interface. The resulting IP
subnet must be unique across all interfaces (including the Remote
Operations Channel interfaces specified in the IP Interface table).
Priority Tag [VPT]: 0 0-7 The default 3-bit VLAN Priority used in the VLAN Tag header on
tagged port(s).
Backplane Port [BP]: Tagged Tagged The set of untagged ports in this VLAN. Any packet sent via an
UnTagged untagged port will be transmitted without VLAN header tag. A
specific port can only be configured for untagged traffic for
UnJoin exactly one VLAN.
Faceplate Port [FE1]: Tagged
The set of tagged ports in this VLAN. Any packet sent via a
tagged port will be transmitted with a VLAN header tag.
...................................................................................................................................................................................................
11 Click Apply.
...................................................................................................................................................................................................

From the menu bar, select IP SubSystem → IP Data → System → Save Changes to
NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
If you want to return to the links for activating service for VoIP, click back to activate
service for ICAP.
....................................................................................................................................................................................................................................
363-211-555 7-117
Provision/retrieve feeder parameters on an ICAP

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision or retrieve the feeder interface parameters (e.g. the
appropriate impedance) on the pack. The provisioned settings must match the settings
of the connected device.
Note that the feeder protocol (R2_TDM, RT_TDM, GR303) is predefined by the
customer key code (CKC).
Procedure
...................................................................................................................................................................................................
1 If the ICAP System Turnup window is not yet open, from the menu bar select IP
Subsystem -> ICAP -> System -> General...
Result The ICAP System Turnup window opens.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
3 In the Feeder Config subtab, enter the appropriate parameters for the Feeder Config:

value values
ICAP Feeder: 1 1..8 The index of the TDM feeder towards to the remote terminal
Operational Status: up up, down, lpbk Indicates the operational status of the feeder.
External Status: None none, mon, rai Indicates the external status of the feeder.
TDM Interface: 1 0..8 The index of the logical TDM interface if the feeder is allocated.
TDM Link: 1 0..8 The index of the logical TDM link which has allocated this feeder.
TDM Type: rt none, rt, The type of the TDM interface if the feeder is allocated. If the
gr303, r2, v5 feeder is not allocated the value ’none’ is returned.
Loopback Action: none none Parameters to loopbacks on TDM feeders.

operate
release
Impedance: ohm75 ohm75 Indicates the impedance used for feeder. Only applicable if the
ohm120 system is running in E1 mode.
...................................................................................................................................................................................................
4 Click Apply.
...................................................................................................................................................................................................................................
7-118 363-211-555
Detailed procedure descriptions Provision/retrieve feeder parameters on an ICAP
...................................................................................................................................................................................................
5 IF... THEN...
the feeder protocol is defined as R2_TDM Go to Step Step 6.
protocol
the feeder protocol is defined as RT_TDM Go to Step Step 7.
protocol
the feeder protocol is defined as GR303 Go to Step Step 12.
protocol
...................................................................................................................................................................................................
6 In the tab R2-TDM subtab enter the appropriate parameters:

value
R2-TDM Link: 1 1 to 8
Operational Status: Up The operational status of the selected interface is shown
here.
Administrative Status: Enabled Enabled The administrative status enables or disables an
Disabled interface. Make sure all parameters of an interface are
properly provisioned before enabling it.
ICAP Feeder: 1 1...8 The index of the TDM feeder to be used towards the R2
PBX.
Identification String: MyR2Tdm The identification string is used to check connection to

the correct remote terminal device. If the identification
strings do not match, an error will be reported and the
link will not become In Service.
NE Signal Degrade: -6 -4,-5,-6,-7 Near end E1 or Far end E1 signal degrade (in 10E) to
be regarded as low bit error threshold. If the actual
signal bit error rate exceeds the specified threshold an
FE Signal Degrade: -6 -4,-5,-6,-7 alarm is raised by the system while still keeping the
feeder operational.
Metering Mode: Pulsed- Pulsed-answer Defines the metering mode to be used for this R2
answer Pulsed-clearback interface.
...................................................................................................................................................................................................
7 In the RT-TDM, subtab Interface window enter the appropriate parameters:
RT-TDM Interface: 1 1 to 8 The index of the logical Remote Terminal interface.
Operational Status: Up Up The operational status of the selected interface is

Down shown here.
Administrative Status: Disabled Enabled The administrative status enables or disables an

Disabled interface. Make sure all parameters of an interface are
properly provisioned before enabling it.
....................................................................................................................................................................................................................................
363-211-555 7-119
Identification String: MyRTTdm The identification string is used to check connection to

the correct remote terminal device. If the identification
strings do not match, an error will be reported and the
link will not become In Service.
IP Interface Addr: none none, roc-1 to The IP interface address is used for ROC support.
roc-8 Select a ROC interface from the list. The provisioning
of the interface is done under the General tap in the
IP-Interface subtab.
Service Degrade: 50 5 to 95 The service degrade threshold defines the percentage

of failed links of this interface at which an alarm shall
be sent by the system.
...................................................................................................................................................................................................
8 Click Apply.
...................................................................................................................................................................................................
9 In the RT-TDM, subtab Links enter the appropriate parameters:

value values
RT-TDM Link: 1 1 to 8 Select the RT-TDM interface to create, edit or delete.

Operational Status: Unknown Unknown The operational status of the selected interface is shown here.
Administrative Status: Enabled The Administrative Status enables or disables a link. Make
Disabled sure all parameters of a link are properly provisioned before
enabling it.
ICAP Feeder: fdr-1 fdr-1 to fdr-8 The ICAP feeder defines the physical port used for this
logical link.
NE Signal Degrade: -6 -4, -5, -6, -7 The NE Signal Degrade and FE Signal Degrade define a bit
error rate thresholds in 10E for the E1 signal. If the threshold
FE Signal Degrade: -6 -4, -5, -6, -7 is exceeded, an alarm is raised.
...................................................................................................................................................................................................
10 Click Apply.
...................................................................................................................................................................................................
11 Select the subtab Xcons. To create a cross connection, select the appropriate RT-TDM
Interface and the appropriate RT-TDM Link, and click Apply. Repeat this until all
required links are assigned to an interface.
System Response: If the group or port settings are incorrect, an error massage is
reported.
Enter the following parameters:
....................................................................................................................................................................................................................................
7-120 363-211-555

value
RT-TDM Interface: 1 1-8 Index of the logical remote terminal
interface
RT-TDM Link: 1 1-8 Index of the logical remote terminal
link
The created cross connections between RT-TDM Interface and RT-TDM Link are
sorted by Module IDs, and displayed in a table on the Xcons window. To delete a
created cross connection in the Module Id column in the table select the cross
connection to be deleted, and click Delete.
...................................................................................................................................................................................................
12 IF the feeder protocol is defined as used the GR303 interface protocol, enter the
appropriate parameters:

value values
ICAP Feeder: 1 1..8 The index of the TDM feeder towards the GR303 terminal.
Operational Status: Down Up Indicates the operational status of the feeder. A status of ’lpbk’ is
Down returned when a loopback is active on the physical feeder.
Lpbk Read-only.
External Status: Mon None If the Feeder Operational Status denotes ’down’ this External Status
Mon indicates the failure location, otherwise ’none’ is returned.
MON(itoring) indicates that a faulty signal is received while RAI
RAI indicates that ’Remote Alarm Indication’ (aka ’Yellow Alarm’) is
received. In both failure conditions an additional alarm is raised
against the feeder which indicates the specific failure condition like
LOS, LOF, AIS or RAI.
Read-only.
TDM Interface: 1 1..4 The index for logical GR303 TDM network interfaces.
TDM Link: 1 1..8 The index for logical GR303 TDM network links.
Read-only.
TDM Type: GR303 None The type of the TDM interface if the feeder is allocated. If the
RT feeder is not allocated the value ’none’ is returned.
GR303 Read-only.
R2
V5
Loopback Action: none none Setting this action to ’operate-line-loopback’ starts a loopback on a
operate TDM feeder. A line loopback causes the received signal to be
loopback into the sending direction.
release
...................................................................................................................................................................................................
13 In the GR303, subtab Interface window, enter the appropriate parameters:
....................................................................................................................................................................................................................................
363-211-555 7-121

value
GR303-TDM Interface: 1 1 to 4 The index of the logical GR303 interface.
Operational Status: Up Up Indicates the operational status of the logical GR303 interface.
Down Read-only.
EOC/TMC Datalink Control

Active EOC: None Normal Initiates a protection switch from the active EOC/TMC to the
Forced standby datalink. Execution of this command initiates the dialog
with the far end to effect this path switch. If the protection
switch times out after 30 seconds, an SNMP SET error be
returned.
Active TMC: None Normal
Parameters to switch EOC’s (Embedded Operations Channel) or
Forced
TMC’s (Timeslot Management Channel) within a logical GR303
interface.
ROC Nail-Up Control
Control: None None

Setup
Remove
Status: Unknown not-nailed-up The nailed-up status of the ROC at the far-end remote terminal
nailed-up connected to a logical GR303 interface.
Traffic Statistics
TS Type: BCO BCO This parameter defines the traffic parameter to be retrieved.
BCT BCO and BCT are peg counts, PHTL is the usage (30 second
scan) in CCS for the peak hour, and TCB is the peg count in
PHLT seconds that all channels were busy (i.e. the next call may be
TCB blocked) during the peak hour. Note that the peak hour is
defined by the hour (as measured by the time of day clock) with
the highest PHTL; the TCB value is always associated with this
same hour. CCS stands for Centum Call Second, i.e. 100 call
seconds. A call second is defined as one channel (a DS0 here)
being occupied for 1 second. Thus, each channel can carry a
theoretical maximum load of 36 CCS. The PHTL number is the
sum of a VRT’s DS0s CCS counts and depends only on the DS0
usage. For instance, a DS0 carrying two 100 second calls would
register the same CCS as one carrying one 200 second call.
DS0s used for data links (including the ROC) are not included
in the CCS calculation.
TS Value: 1 1..8 The measured value of the traffic parameter.

Read-only
Reset Time & Date: 0..65536 This value represents the date and time where the traffic statistic
data was last reset.
Peak Time & Date: 0..65536 This value represents the date and time of the Peak Traffic hour
and is only applicable for the traffic types PHTL and PCB.
Init Traffic Data: check box Setting this action to ’initialize’ requests to reset the traffic
statistic data. When read this parameter always delivers ’none’.
...................................................................................................................................................................................................
14 In the GR303, subtab Links enter the appropriate parameters:
....................................................................................................................................................................................................................................
7-122 363-211-555

value values
GR303-TDM Link 1 1 to 8 Select the RT-TDM interface to create, edit or delete.

IF-Fdr:
Equalization (0-655): 0 0..655 Equalization of a DS1 port adjusts the gain vs. frequency of the port’s
transmission circuitry to compensate for added frequency-dependent loss
of cable connecting the port to a DSX-1 interface with standard levels.
The DSX-1 is allowed to be up to 655 feet distant from the feeder.
DS1 Signal Degrade: 6 4..7 The signal degrade threshold parameter determines how degraded a
received DS1 signal can become before an event is reported with an
alarm. The parameter is specified in terms of bit error rate (BER) in
powers of 10, i.e. in 10E-<value>.
Primary State: Enabled Enabled Specifies whether the Gr303 link is enabled or disabled. This value can
Disabled only be set to ’disabled’ (in combination with a secondary status of
’auto’) as the system automatically sets a Gr303 link to ’enabled’ once it
is cross-connected to a physical feeder and the physical feeder gets
operational.
Secondary State: None none Indicates the secondary status of the GR303 link. The secondary port
auto service state shows the failure reason when the primary port service state
is ’disabled’. Failures of the related physical feeder are shown with the
mon ’MON’ (i.e., monitoring) secondary service state accompanied with an
yel alarm specifying the failure reason. The secondary service state ’AUTO’
indicates either a failure of the related physical feeder or the absence of
lpbk
a cross-connect to a physical feeder. The ’LPBK’ (i.e., loopback)
secondary service state indicates an active loopback. If a remote alarm
indication signal is received a ’YEL’ (i.e., yellow alarm) secondary
service state will be returned.
The state ’None’ is used if the Gr303 is operational without any failure
condition.
...................................................................................................................................................................................................
15 Select the subtab Xcons. To create a cross connection select the appropriate
GR303-TDM Interface the appropriateGR303-TDM Feeder then the appropriateICAP
Feeder and click Apply. Repeat this until all required links are assigned to an
interface.
System Response: If the group or port settings are incorrect, an error massage is
reported.
GR303-TDM Interface: 1 1..4 Index of the logical remote terminal interface
GR303-TDM Feeder: 1 1..8 Index of the logical remote terminal link

ICAP Feeder: 1 1..8 The index of the TDM feeder towards the
remote terminal.
....................................................................................................................................................................................................................................
363-211-555 7-123
The created cross connections between GR303-TDM Interface and GR303-TDM Link
and the ICAP Feeder are sorted by Module IDs, and displayed in a table on the Xcons
window. To delete a created cross connection select in the Module Id column the cross
connection to be deleted, and click Delete.
...................................................................................................................................................................................................

NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
activate service for ICAP.
....................................................................................................................................................................................................................................
7-124 363-211-555
Provision/retrieve ICAP profiles

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision all parameters valid for an ICAP that apply to the pack
and/or to all ports on this AP.
Assumptions
slots” (p. 7-48)
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Select the Profiles tab.

...................................................................................................................................................................................................
3 In the section Profile ID select the Pack and the Profile Name you want to provision,
retrieve, edit, delete or create a new profile.
If you want to create New profile, click New then enter a new profile name and set the
appropriate values for the new profile, click Apply.
To edit an existing profile, select the profile and click Edit, set the appropriate values
and click Apply.
If you want to delete an existing profile, select the profile to be deleted and click
Delete. Note that the list of existing profiles always includes the predefined profiles.
Predefined profiles (default profiles) cannot be deleted.
...................................................................................................................................................................................................
4 Select the DigitMap subtab and enter the following options. Then click Apply.
Start Timer (secs): 45 0 - 3600 Specifies the time in secs to wait for the first digit after
off-hook.
Short Timer (secs): 4 0 - 3600 Is used when ambiguous digit pattern must be distinguished
(e.g. 0 | 00)
Long Timer (secs): 12 0 - 3600 Defines the max. interdigit time. If this timer expires, the
dialed number was incomplete and the VoIP AP will generate an
error tone towards the subscriber
Digitmap Name: Alpha numeric string without blank space. This field is not used by SIP.
...................................................................................................................................................................................................................................
363-211-555 7-125
Detailed procedure descriptions Provision/retrieve ICAP profiles
Digitmap: [0 - 9], [A - Digit Map symbols are “0” - “9”, “*” and “#”.
F], [*], [.] Up to 256 characters are supported.
The Digitmap can de edited using the key board or click Digit
Map Generator to open a support window.
Digit Map Generator Clicking on this button opens a support window which allows
the user to define a digitmap in a comfortable manner.
...................................................................................................................................................................................................
5 Click Apply
...................................................................................................................................................................................................
6 Select the RTP subtab and enter the following options:

value
Minimum Port #: 8000 1000 - 65436 Is used for receiving the RTP stream.
G711 Packet Interval (msecs): 10 10 - 100 The RTP packet interval in milliseconds to be used if the
far end does not explicitly requests a specific packet
interval.
G726 Packet Interval (msecs): 10 10, 11, 20, 22, The provisioned value is used in the following way:
30 • in SDP receive offers containing only one codec the
specific GxxxPacketInterval as provisioned for this
codec is used to request this receiving ’ptime’
G729 Packet Interval (msecs): 10 10 - 80 • in SDP receive offers containing multiple codecs the
provisioned GxxxPacketInterval of the first codec is
used to request this receiving ’ptime’
G723 Packet Interval (msecs): 30 30 - 60 • the GxxxPacketInterval defines also the packet size
of sent RTP packets if the far end has not requested
to receive a specific ’ptime’.
Clear Channel Packet Interval 10 5, 10, 20, 30 The RTP packet interval in milliseconds for the Clear
(msecs): Channel ’codec’ to be used if the far end does not
explicitly requests a specific packet interval.
Jitter Buffer Type: dynamic dynamic Defines whether the jitter buffer size is fixed and
fix non-adapative or whether the jitter buffer size
dynamically adapts to the jitter of the received packets.
In any case the parameter ’icapRtpJitBufferSize’ defines
the maximum used jitter buffer size.
Jitter Buffer Size (msecs): 60 10 -200 This parameter defines also the downstream delay of the
VoIP AP
Rtp TOS: 0 0 - 255 The TOS bits of RTP packets the VoIP pack sends
Ctrl TOS: 0 0 - 255 The TOS bits of control packets the VoIP pack sends
Emergency Rtp TOS: 0 0 - 255 TOS field of the RTP stream for emergency calls.
....................................................................................................................................................................................................................................
7-126 363-211-555

value
NonPort Codec Usage: AB 1 - 15 The audio codecs resp. RTP data types to be used if
non-port related audio has to be generated or negotiated
to be received. Please note the slight difference to the
’icapxxxPortCodecUsage’ parameters which only defines
the receiving direction. This parameter is applicable e.g.
for announcements towards to network.
...................................................................................................................................................................................................
7 Click Apply.
...................................................................................................................................................................................................
8 Select the Switch subtab and enter the following options:
Proxy Host: Depends on the In case a Proxy Server is available enter IP address
network and port of this server
configuration
Proxy Port: 5060 1..65535
Outbound Proxy Host: Depends on the Optional information. IP address of the proxy via
network which all messages are sent to the IP network (Route
configuration header information).
Outbound Proxy Port: 5060 1..65535 Optional information. Port number of the proxy via
which all messages are sent to the IP network (Route
header information).
Registrar Host: Depends on the The registrar host is responsible for converting
network registration ID to telephone number
configuration
Registrar Port: 5060 1..65535
Register On Startup: Enable Enable When set to enable SIP shall register on start up.
Disable
Expiration Interval (mins): 4320 1..65535 This is the expiry time for a registration message
Desired Session Interval (secs): 1800 0..65535 Used to negotiate the Session Interval time
Within this Interval time, keep alive messages
Min Session Interval (secs): 90 90..65535 (re-invite) must be received, or the connection is
disrupted
Originator Ring T out: 485 10..600 Timer value for abandoning outbound (originating)
call requests
Terminator Ring T out: 485 1..600 timer value for abandoning inward (terminating) call
requests
...................................................................................................................................................................................................
9 Click Apply.
...................................................................................................................................................................................................
10 Select the subtab Numbers and enter the following options:
....................................................................................................................................................................................................................................
363-211-555 7-127
Emergency
Emergency #´s: 110, 118, 119 List of emergency numbers, separated by comma,
without white space and unique numbers. Allowed
symbols are “0” - “9” and “A” - “F”:
Emergency Exclude
Emergency Exclude #´s: Depends on the Empty Disables the use of these emergency numbers per
Emergency number port.
list provisioned in
the Control tab
Translation (this field is not used by MGCP protocol)
Number Translation: [0 - 9], [A - F] This parameter supports the omitted (or abbreviated)
dialing feature. The format is:
abbrevString=assignedString separated by “;”
...................................................................................................................................................................................................
11 Click Apply.
...................................................................................................................................................................................................
12 Select the subtab Emergency Call and enter the following options:
Emergency Call Hold: Enable Enable If enabled, the call is kept on-hold even if
Disable a disconnect signal on the subscriber port
is detected.
Emergency CID Block: Block Block (permits the user to Display of caller/number can be
block caller ID display blocked/unblocked
for emergency calls by
dialing “184” prefix)
UnBlock (the users caller
ID information is always
displayed for emergency
calls. The “184” prefix is
ignored
Emergency RingStart: 2 0 - 60 Time after which a subscriber phone starts

ringing again after dialing an emergency
number and an accident hang-up of the
phone.
Emergency RingStop: 0 0 - 600 Maximum time for which ringing signal

0, this value indicates no shall be send to the subscriber in case of
stop of ringing signal an on-hook during emergency call
...................................................................................................................................................................................................
13 Click Apply.
...................................................................................................................................................................................................
14 Select the subtab Port and enter the following options:
....................................................................................................................................................................................................................................
7-128 363-211-555

value
Voice Activity Detection: Disable Enable Defines whether voice activity detection shall be performed on
Disable the incoming voice of the locally connected subscriber.
Echo Canceller: 32 0..128 The tail length in milliseconds for the echo canceler. A setting of
’0’ disables the echo canceler.
CID Sig Preference: Default default, The preferred signaling method to be used for Calling Line Id
modem, Presentation (CLIP). Value ’default’ means that the customer key
code dependent default is used.
push-button
Transmit Gain (db): 0 -40..70 The transmit gain is the amplification/attenuation performed on
the signal received from the remote terminal and then sent up to
the IP network.
Decibel relative to the digital reference point, multiplied by 10.
Receive Gain (db): 0 -120..30 The receive gain is the amplification/attenuation performed on
the signal received from the IP network and then sent down to
the remote terminal.
Decibel relative to the digital reference point, multiplied by 10.
...................................................................................................................................................................................................
15 Click Apply.
...................................................................................................................................................................................................

NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
363-211-555 7-129
Provision/retrieve network protocol parameters

...................................................................................................................................................................................................................................
Purpose
In a system that is configured via the customer key code to support SIP protocol,
H.248 protocol or MGCP protocol use this procedure to provision the network protocol
parameters for all ports on the ICAP.
Note that the network protocol (SIP, H.248 or MGCP) is predefined by the customer
key code (CKC).
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Select the tab Network

Result: Depending on customer key code, one of the following subtabs appear on
the ICAP System Turnup window:
• SIP Interface Config
• H.248 Interface Config
• H.248 Switch Interface
• MGCP Interface Config.
...................................................................................................................................................................................................
3 IF... THEN...
the network protocol is defined as SIP Go to Step 4.
the network protocol is defined as H.248 Go to Step 6.
the network protocol is defined as MGCP Go to Step 10.
...................................................................................................................................................................................................
4 Select the SIP Interface Config subtab and enter the following options. Then click
Apply.

value
Operational Status: Up Up Indicates the operational status of the ICAP

Down
...................................................................................................................................................................................................................................
7-130 363-211-555
Detailed procedure descriptions Provision/retrieve network protocol parameters

value
Administrative Enable Enable Enables the SIP operation of the pack. It might be advisable
Status: Disable to enable the pack after all other provisioning has been done.
Local Port: 5060 1000..65535 The local UDP port to receive call control protocol messages
from Softswitch
CTRL IP Address: Depends on 0.0.0.0.. The IP address to be used for call control messages of this
the network 255.255.255.255 logical VoIP interface. The IP address referenced here is
configuration either a different one than used for RTP voice streams and/or
Management or can be the same.
Note that the IP address specified here is only a reference
and not a real IP interface definition. The IP address must
exist in the ICAP VLAN Table, otherwise it will not be usable
and the VoIP interface will remain non-operational.
DNS 1: 0.0.0.0 Domain name server 1.


RTP IP Address: The IP address to be used for the RTP voice streams of this
logical VoIP interface. The IP address set here is either a
different one than used for call control and/or Management
or can be the same. Note that the IP address specified here is
only a reference and not a real IP interface definition. The IP
address must exist in the icapVlanTable, otherwise it will not
be usable and the VoIP interface will remain non-operational.
DigitMap Profile: 0 Clicking on the Configure button opens a support window
which allows the user to define a digitmap in a comfortable
manner.
As defined in “Provision/retrieve ICAP profiles ” (p. 7-125)
procedure.
RTP Profile: 1 Clicking on the Configure button opens a support window

which allows the user to define a digitmap in a comfortable
manner.
procedure.
Emergency #´s 0 Clicking on the Configure button opens a support window

Profile: which allows the user to define a digitmap in a comfortable
manner.
procedure.
Call Priority Thresholds

Emergency 100 0..100 The resource threshold for calls of this priority. At most this
percentage of system resources will be used for a call of this
Urgent 100 0..100 priority
Normal 100 0..100
Non Urgent 100 0..100
....................................................................................................................................................................................................................................
363-211-555 7-131
...................................................................................................................................................................................................
5 Click Apply then go to Step 12 to save these changes.

...................................................................................................................................................................................................
6 Select the H.248 Interface Config subtab and enter the following options. Then click
Apply.
Operational Status: Up Indicates the operational status of the ICAP
Administrative Status: Enable Enable Indicates the administrative status of the ICAP
Disable
Local Port: 2944 1000 - 65535 This is the local UDP or TCP port in the gateway to
receive H.248 call control protocol messages from
softswitch. The transport protocol (UDP or TCP) is
controlled by the customer key code (CKC).
CTRL IP Address: Depends on 0.0.0.0 - The IP address to be used for call control messages of
the network 255.255.255.255 this logical VoIP interface. The IP address referenced here
configuration is either a different one than used for RTP voice streams
and/or Management or can be the same.
Note that the IP address specified here is only a reference
and not a real IP interface definition. The IP address must
exist in the ICAP VLAN table, otherwise it will not be
usable and the VoIP interface will remain non-operational.

RTP IP Address: 0.0.0.0 The IP address to be used for the RTP voice streams of
this logical VoIP interface. The IP address set here is
either a different one than used for call control and/or
Management or can be the same. Note that the IP address
specified here is only a reference and not a real IP
interface definition. The IP address must exist in the
icapVlanTable, otherwise it will not be usable and the
VoIP interface will remain non-operational.
DigitMap Profile: 0 Clicking on the Configure button opens a support window

which allows the user to define a digitmap in a
comfortable manner.
As defined in “Provision/retrieve ICAP profiles ”
RTP Profile: 1 Clicking on the Configure button opens a support window

which allows the user to define a digitmap in a
comfortable manner.
As defined in “Provision/retrieve ICAP profiles ”
...................................................................................................................................................................................................
7 Click Apply then go to Step 12 to save these changes.
....................................................................................................................................................................................................................................
7-132 363-211-555
...................................................................................................................................................................................................
8 Select the H.248 Switch Interface subtab and enter the following options. Then click
Apply.

value
Primary Host: 10.10.36.252 This parameter defines the IP address of the H.248 primary media
gateway controllers.
Primary port: 2944 1..65535 This parameter defines the port number of the primary media gateway
controller.
Register On Startup: Enable Enable Indicate whether gateway should send registration message to
Disable softswitch at start up.
Connection Timeout: 0 Number of seconds the AnyMedia times out the connection to the
H.248 MG controller. A value of “0” indicates no timeout
Encoding: h248text h248text H.248 message coding

h248binary
Version: h248v1 h248v1 H.248 version number

h248v2
Security Parameter 256 256.. The Security Parameters Index (SPI) field in the H248 authentication
Idx: 4294967295 header.
Authentication hmac- hmac- The algorithm used for H.248 authentication header
Algorithm: md5-96 md5-96
hmac-
sha1-96
Authentication Key: 1..32 The key string for H.248 authentication header. The string can be
ASCII or hexadecimal.
Authentication Admin Disable Enable Enable or disable H.248 authentication header.
State: Disable
Compact Output: Disable Enable Indicates if H.248 output messages need to be in compact format, that
Disable uses the shorter tokens and excludes white-spaces, linefeed,
carriage-return characters in text encoding.
Mgc Backup Retry 45 0..1800 This timer defines the amount of seconds for which a ’Media
Timer: Gateway Controller not reachable’ failure condition must persist to
trigger a switch-over to one of the provisioned Media Gateway
Controllers. The provisioned primary/backup MGCs are prioritized in
the sense that first a switch-over is tried to the primary MGC (unless
it was the one that failed), then to backup host 1, then to backup host
2 and so on. i.e. this means that, if a currently used backup host fails,
then the switch-over procedure starts again with the primary MGC
before trying to contact the other backup MGCs.A value of ’0’
disables a self-initiated switch-over between provisioned MGCs due
to this timer .Note that this does not prevent to follow any
’Hand-Off’ procedure initiated by the network or a self-initiated
switch-over triggered by exceeding the maximum number of retries as
defined in the parameter icapH248ParamReTransMaxCount in the
icapH248ParamTable.
....................................................................................................................................................................................................................................
363-211-555 7-133

value
Mgc Backup Host 1: 0.0.0.0 The IP address/FQDN of the first backup Media Gateway Controller.
If this IP address is set to ’0.0.0.0’ then no backup MGC is defined.
If this backup host is currently in use then a switch-over procedure
starts again with the primary MGC before trying to contact the other
backup MGCs.
To unset this parameter set it to ’0.0.0.0’. The usage of ’’, i.e an
empty string, for this purpose is not recommended to use.
Port 1: 2944 1..65535 The UDP port number for signaling of the first backup Media
Gateway Controller.
backup MGCs.
backup MGCs.
Gateway Controller.
backup MGCs.
backup MGCs.
Gateway Controller.
backup MGCs.
Mgc Current Host: 0.0.0.0 The IP address/FQDN of the currently connected Media Gateway
Read only Controller. This reflects either the primary MGC, one of the backup
MGCs or, in case of a successful network-initiated ’Hand-Off’
procedure, the MGC which the system was told to use. Note that a
network-initiated ’Hand-Off’ procedure does not change any
provisioned MGC host and port settings. If no connection exists to
any MGC then this parameter shows ’0.0.0.0’.
Port: Read only 0..65535 The UDP port number for signaling of the currently connected Media
Gateway Controller. If no connection exists to any MGC then this
parameter shows ’0’.
....................................................................................................................................................................................................................................
7-134 363-211-555
...................................................................................................................................................................................................
9 Select the Miscellaneous Parameters subtab and enter the following options. Then
click Apply.

value
Re-Trans Interval: 10 1..30 The interval (in seconds) to wait for a reply to a (initial)
signaling message request and any subsequent
retransmission of this request.
Re-Trans max Count: 3 infinite The maximum number of retransmissions to be performed

no re-transmission in case no reply is received to a signaling message within
the time period. To ensure that the number of retries
1..20 defined here are actually performed, the
icapH248IfMgcBackupRetryTimer must be set to either ’0’
or at least (icapH248ParamReTransMaxCount + 1) *
icapH248ParamReTransInterval seconds.
Example: With 3 retransmissions and a 10 second
re-transmission interval the
icapH248IfMgcBackupRetryTimer should be set to at least
40 seconds.
On the other hand, if infinite number of retransmissions
are set here, then the icapH248IfMgcBackupRetryTimer
parameter ’overrules’ and ultimately defines the time
period after which a self-initiated switchover is triggered.
Thus, to define infinite retransmissions without any
self-initiated switchover, the
icapH248IfMgcBackupRetryTimer is to be set to ’0’ and
this parameter is to be set to ’-1’.
...................................................................................................................................................................................................
10 Select the MGCP Interface Config subtab and enter the following options. Then click
Apply.

value
Operational Status: Up Up Indicates the operational status of the ICAP

Down
Administrative Disable Enable Specifies whether the VoIP interface is enabled or disabled. If
Status: Disable disabled the system will not react on any incoming traffic destined
to the IP address and port specified here nor will it sent out any
traffic.
Local Port: 2944 1000 - 65535 This is the local UDP or TCP port in the gateway to receive call
control messages from call agent. The transport protocol (UDP or
TCP) is controlled by the customer key code (CKC).
IP Address: Depends on 0.0.0.0 - The IP address to be used for call control messages of this logical
the network 255.255.255.255 VoIP interface. The IP address referenced here is either a different
configuration one than used for RTP voice streams and/or Management or can be
the same.
Note that the IP address specified here is only a reference and not a
real IP interface definition. The IP address must exist in the ICAP
VLAN table, otherwise it will not be usable and the VoIP interface
will remain non-operational.
....................................................................................................................................................................................................................................
363-211-555 7-135

value

RTP IP Address: The IP address to be used for the RTP voice streams of this logical
VoIP interface. The IP address set here is either a different one than
used for call control and/or management or can be the same. Note
that the IP address specified here is only a reference and not a real
IP interface definition. The IP address must exist in the
icapVlanTable, otherwise it will not be usable and the VoIP
interface will remain non-operational.
DigitMap Profile: 0 Clicking on the Configure button opens a support window which
allows the user to define a digitmap in a comfortable manner.
RTP Profile: 1 Clicking on the Configure button opens a support window which
allows the user to define a RTP profile in a comfortable manner.
The profile index of the RTP profile to be used for all subscribers
of this logical VoIP interface.
Emergency #´s 0 Clicking on the Configure button opens a support window which
Profile: allows the user to define a emergency profile in a comfortable
manner.
SdtDigitmap 0 The profile index of the digit map profile to be used to identify
Profile prefix digits after which a Second Dial Tone is autonomously
applied towards the subscriber.
DmRepDigitmap- 0 The profile index of the digit map profile to be used to identify
Profile prefix digits after which the digit map parsing is to be reset. If such
a prefix is recognized the digit map parsing is reset and any follow
up dialed digits are parsed again against the default digit map or to
the one supplied and superseded by the media gateway controller.
Select the MGCP Switch Interface subtab enter the following options. Then click
Apply.
Primary Host: Depends on the The Media Gateway Controller host.

network
configuration
Primary Port: 2727 1..65535 The port number of the Media Gateway Controller.
Register On Startup: Enable Enable Indicate whether gateway should send registration
Disable message to softwitch at start up.
...................................................................................................................................................................................................
11 Click Apply then go to Step 12.

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

....................................................................................................................................................................................................................................
7-136 363-211-555
NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
363-211-555 7-137
Provision/retrieve H.248 port parameters on an ICAP

...................................................................................................................................................................................................................................
Purpose
In a system that is configured via the customer key code to support H.248 protocol use
this procedure to provision or retrieve the individual port parameters on an ICAP. It
can be determined whether the provisioning should apply to an individual port only or
to all ports on the pack.
Procedure
...................................................................................................................................................................................................
Note that the ports provisioning window supports also the ports provisioning via
Script Mode see “Create/Edit or run a Script” (p. 7-18).
...................................................................................................................................................................................................
2 Select the Ports tab.

...................................................................................................................................................................................................
select from the Port pull-down menu a dedicated port (the choices are or Port 1 to
2048 or All).
...................................................................................................................................................................................................
4 In the Configuration subtab, H.248 Port Control window enter the following
parameters:
Operational State: Out of In service Indicate the operational state of port.

Service Out of Service Read only.
Administrative State: Disabled Enabled When disabled no service is provided for the port.
Disabled
Active Read only.
Active Codec: PCMU If there is a call active on the port, then this indicates the
codec being used for outgoing packets. Empty string
means no codec when there is no active call.
Read only.
...................................................................................................................................................................................................................................
7-138 363-211-555
Detailed procedure descriptions Provision/retrieve H.248 port parameters on an ICAP
Audio Codec Usage: AB PCMA, PCMU, Preferred audio codec in receiving direction.
(PCMA G726, G729AB, Note that telephone-event and comfort noise from far end
PCMU) clear-channel, subscriber are only add-ons, and are not valid without any
telephone-event, other codecs.
comfort noise from
far end subscriber, Note that the actual list of supported codecs may be
G726-16, G726-24, limited depending on the actual customer key code.
G726-40, G723-5,
G723-6.T.38
Real-time Facsimile
Service Type: pots pots, r2 Indicate the signaling type from this port.
Port Info: Port-1 ASCII text Indicates a port location info or similar. Used for
Push-button
Auto
Metering Signaling: default default The preferred metering signaling method to be used for
reversed-polarity pay phones or home meters. Value “default” means that
the customer key code dependent default is used.
meter-pulse
This parameter is not applicable in DS1 mode.
Termination ID Card: -1 -1..350 The card part of the Termination ID as used in the H.248
protocol. Combined with the Interface and Port part this
triple must be unique across all H.248 VoIP ports. The
number given here should reflect the real physical slot
number used in the remote terminal. Anyhow it must be
noted that the value here is purely logical and does not
necessarily need to be the real physical slot number.
Termination ID Port: 0 0...2048 The port part of the Termination ID as used in the H.248
protocol. Combined with the Interface and Card part this
triple must be unique across all H.248 VoIP ports. The
number given here should reflect the real physical port
number used in the remote terminal. Anyhow it must be
noted that the value here is purely logical and does not
necessarily need to be the real physical port number.
Remote Phys Card: 0 0...43 This ’Remote Physical Card’ parameter is only applicable
for customer key codes which support the wildcard
mechanism in the H.248 Termination ID to indicate in the
H.248 protocol any pack and/or interface level failures
towards the Media Gateway Controller. Otherwise this
parameter may be used for informational purposes only.
Remote Phys Port: 0 0...64 This ’Remote Physical Port’ parameter is only applicable
for customer key codes which support the wildcard
mechanism in the H.248 Termination ID to indicate in the
H.248 protocol any pack and/or interface level failures
towards the Media Gateway Controller. Otherwise this
parameter may be used for informational purposes only.
...................................................................................................................................................................................................
5 Click Apply.
....................................................................................................................................................................................................................................
363-211-555 7-139
...................................................................................................................................................................................................
6 Select the Profiles subtab and select the profiles from the list of existing profiles.
Click Configure to check or change the content of a profile or create a new profile.
These profiles work on port level.
Options Profiles Possible Comments

values
Port DigitMap Profile: 0 0..200 The profile index of the digit map profile to
be used as port specific digit map.
As defined in “Provision/retrieve ICAP
profiles ” (p. 7-125) procedure.
Port Profile: 1 1..36 The profile index of the ’Port’ profile to be
used for this port.
As defined in “Provision/retrieve ICAP
profiles ” (p. 7-125) procedure.
...................................................................................................................................................................................................
7 Click Apply.
...................................................................................................................................................................................................
8 Select the XConnects subtab. To create a cross connection select the Network Group
and Port then select the TDM Group and Port and then click Apply.
System Response: If the group or port settings are incorrect a system error massage
will be reported.
Network
Interface: 1 1 Indicate the index of the logical VoIP interface.
Group: 1 fixed to 1 Indicate the index of the logical VoIP group.
Port: 1 1 to 2048 Indicate the index for H.248 VoIP ports within a
H.248 logical group.
TDM
Interface Type: RT(1) RT(1) Type of the logical TDM interface

GR303
R2
V5
Interface: 1 1 to 8 Indicate the index of the logical TDM interface.
Port: 1 1 to 2047 Indicate the index for TDM ports within a TDM
logical interface.
....................................................................................................................................................................................................................................
7-140 363-211-555
The created cross connections is displayed in a table on the Xconnects window. To

delete a created cross connection select in the Module Id column the cross connection
to be deleted, and click Delete.
...................................................................................................................................................................................................
9 Select the Media Mon subtab and enter the appropriate parameters:
Note that this provisioning is only used for ″legal intercept″ of calls, i.e. to listen to the
speech of an ongoing call without notice to the a- and b-party subscribers.
Media Monitor Host: 0.0.0.0 any IP address The IP address or FQDN of the media monitoring host
to which the media monitoring RTP streams are sent.
Depending on the icapVoipPortMediaMonitorControl
parameter either inbound only, outbound only or both
RTP streams are sent to the media monitoring host
specified here.
Inbound Port: 18000 1..65535 The TCP port on the media monitor host to which the
monitored inbound RTP stream (network -> VoIP port)
is to be sent.
Outbound Port: 18002 1..65535 The TCP port on the media monitor host to which the
monitored outbound RTP stream (VoIP port -> network)
is to be sent.
Media Monitor Control Off Off, Controls whether media monitoring is to be activated
Inbound, for either
Outbound, - only the inbound RTP stream (network -> VoIP port)
Both-Directions or
- only the outbound RTP stream (VoIP port -> network)
or
- both RTP streams of the VoIP port as specified within
this entry. If the control is set to ’off’ the media
monitoring is stopped.
Media Monitor Interface: 1 1 The index of the logical VoIP interface of the VoIP port
to be monitored.
Media Monitor Group: 1 fixed to 1 The index of the logical VoIP group of the VoIP port to
be monitored.
Media Monitor Port: 1 1..2048 The index of the logical VoIP port of the VoIP port to
be monitored.
...................................................................................................................................................................................................
10 Click the Apply button.

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

NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
363-211-555 7-141
....................................................................................................................................................................................................................................
7-142 363-211-555
Provision/retrieve MGCP port parameters on an ICAP

...................................................................................................................................................................................................................................
Purpose
In a system that is configured via the customer key code to support MGCP protocol
use this procedure to provision or retrieve the individual port parameters on an ICAP.
It can be determined whether the provisioning should apply to an individual port only
or to all ports on the pack.
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
select from the Port pull-down menu a dedicated port (the choices are Port 1 to 2048
or All).
...................................................................................................................................................................................................
4 In the Config subtab, MGCP Port Control window enter the following parameters:
Operational State: Out of Service In service Indicate the operational state of port.
Disabled
Active Read only.
Active Codec: PCMU If there is a call active on the port, then this indicates
the codec being used for outgoing packets. Empty
string means no codec when there is no active call.
Read only.
...................................................................................................................................................................................................................................
363-211-555 7-143
Detailed procedure descriptions Provision/retrieve MGCP port parameters on an ICAP
Audio Codec Usage: AB PCMA The audio codecs resp. RTP data types to be used by
(PCMA PCMU this port in receiving direction.
PCMU) G726-32 A - G711 a-law (PCMA)
G729AB B - G711 u-law (PCMU)
clear-channel C - G726-32 (32 kbit/s)
telephone-event D - G729AB
comfort noise E - clear-channel (RFC 4040, Mimetype:

clearmode/clear-channel)
G726-16
F - telephone-event (only add-on, not valid without
G726-24 any other codec)
G726-40 G - comfort noise from far end subscriber (only
G723-5 add-on, not valid without any other codec)
G723-6 H - G726-16 (16 kbit/s)
T.38 Real-time I - G726-24 (24 kbit/s)
Facsimile J - G726-40 (40 kbit/s)
K - G723-5 (5.3 kbit/s)
L - G723-6 (6.3 kbit/s)
M - T.38 Real-time Facsimile - RFC 3362 (only
add-on, not valid without any other codec)
Service Type: pots pots, r2 Indicates the service type of the port. Supported
service types for MGCP are - pots.
Port Info: Port-1 ASCII text Any arbitrary information for this port. Useful e.g. for
location info. Not used by the system.
Port Dialing: Auto Dial-pulse Specifies the allowed dialing mechanism for this port.
Push button The mode ’auto’ accepts dial pulses as well as DTMF
tone dialing. The mode ’dial-pulse’ accepts only dial
Auto pulses. The mode ’push-button’ accepts only DTMF
notapplicable tone dialing. The value ’not applicable’ is used for
virtual ports like e.g. the Automatic Answering Trunk.
Direct Dial in Signaling: Modem None Signaling method for Direct Dial-In service.
Modem
Push button
Metering Signaling: Default Default The preferred metering signaling method to be used for
Reversed-polarity pay phones or home meters. Value ’default’ means that
Meter-pulse
Note that this parameter is not applicable in DS1
mode.
Push Button Signaling 0 0..4 Specifies how many digits, from the end of the
Digits Length: complete digit string, shall be signaled towards the
PBX at ’push-button’ Dial-In Signaling mode. In
’modem’ Dial-In Signaling mode all digits are signaled
to the PBX in any case. The value 0 means that all
digits are to be signaled.
Note that this parameter is not applicable in DS1
mode.
...................................................................................................................................................................................................

....................................................................................................................................................................................................................................
7-144 363-211-555
...................................................................................................................................................................................................
Options Profiles Possible values Comments
Port DigitMap Profile: 0 0..200 The profile index of the digit map profile to be used as
port specific digit map. If specified it overrules any
default digit of the related logical VoIP interface. If set
to ’0’ no profile, i.e. no port specific digit map, is
applied for this port and the default digit map of the
related logical VoIP interface is used.
Port Profile: 1 1..36 The profile index of the “Port” profile to be used for
this port.
Em. Num. Excl. Profile: 0 0..50 The profile index of the “Emergency Number Exclude”
profile to be used for this port.
...................................................................................................................................................................................................
7 Click Apply.
...................................................................................................................................................................................................
8 Select the XConnects subtab. To create a cross connection between logical VoIP/ROC
ports and logical TDM ports select the Network Group and Port then select the TDM
Group and Port and then click Apply.
will be reported.
Network
Interface: 1 1 The index for logical VoIP network interfaces.
Group: 1 1 to 32 The index for logical groups within an MGCP VoIP network
interface.
Port: 1 1 to 64 The index for MGCP VoIP ports within an MGCP logical
group.
TDM
Interface Type: RT RT Type of the logical TDM interface

GR303
R2
V5
Interface: 1 1 to 8 The index for TDM logical interfaces.
Port: 1 1 to 2047 The index for TDM ports within a TDM logical interface.
....................................................................................................................................................................................................................................
363-211-555 7-145
The created cross connections is displayed in a table on the Xcons window. To delete
a created cross connection select in the Module Id column the cross connection to be
deleted, and click Delete. Note that to delete a cross-connection the related VoIP/ROC
Port must be administratively set to “disabled”.
...................................................................................................................................................................................................
9 Select the Media Mon subtab and enter the following parameters:
Media Monitor Host: 0.0.0.0 any IP address or The IP address or FQDN of the media monitoring host
FQDN to which the media monitoring RTP streams are sent.
Depending on the icapVoipPortMediaMonitorControl
specified here.
Inbound Port: 1..65535 The TCP port on the media monitor host to which the
is to be sent.
Outbound Port: 1..65535 The TCP port on the media monitor host to which the
is to be sent.
Media Monitor Control: Off Off Controls whether media monitoring is to be activated
Inbound for either
Outbound - only the inbound RTP stream (network -> VoIP port)
or
Both-Directions
or
to be monitored.
Media Monitor Group: 1 1...32 The index of the logical VoIP group of the VoIP port to
be monitored.
Media Monitor Port: 1 1...64 The index of the logical VoIP port of the VoIP port to
be monitored.
...................................................................................................................................................................................................

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

NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
7-146 363-211-555
....................................................................................................................................................................................................................................
363-211-555 7-147
Provision/retrieve SIP port parameters on an ICAP

...................................................................................................................................................................................................................................
Purpose
In a system that is configured via the customer key code to support SIP protocol use
this procedure to provision or retrieve the individual port parameters on an ICAP. It
can be determined whether the provisioning should apply to an individual port only or
to all ports on the pack.
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
select from the Port pull-down menu a dedicated port (the choices are or Port 1 to
2048 or All).
...................................................................................................................................................................................................
4 In the Config subtab, SIP Port Control window enter the appropriate parameters:
Operational State: Out of Service In service Indicate the operational state of port.
Disabled
Active Read only.
Active Codec: PCMU If there is a call active on the port, then this indicates
the codec being used for outgoing packets. Empty string
means no codec when there is no active call.
Read only.
...................................................................................................................................................................................................................................
7-148 363-211-555
Detailed procedure descriptions Provision/retrieve SIP port parameters on an ICAP
Audio Codec Usage: AB PCMA Preferred audio codec in receiving direction.

PCMU The possible codecs specified here defines the (priority
G726-32 ordered) receiving codecs which are offered in the
Session Description Protocol towards the far end. The
G729AB far end decides which codec(s) are actually used to sent
clear-channel RTP towards this port.
telephone-event Following codec types are defined:
comfort noise A - G711 a-law (PCMA)
G726-16 B - G711 u-law (PCMU)
G726-24 C - G726-32 (32 kbit/s)
G726-40 D - G729AB
G723-5 E - clear-channel (RFC 4040, Mimetype:
clearmode/clear-channel)
G723-6
F - telephone-event (only add-on, not valid without any
T.38 Real-time
other codec)
Facsimile
G - comfort noise from far end subscriber (only add-on,
not valid without any other codec) See also at
icapPortVoiceActivityDetection for details! (Mimetype:
cn)
H - G726-16 (16 kbit/s)
I - G726-24 (24 kbit/s)
J - G726-40 (40 kbit/s)
K - G723-5 (5.3 kbit/s)
L - G723-6 (6.3 kbit/s) Enabling at least one of the
G723 codes automatically enables both rates for the
receiving direction. Additionally this allows to specify a
preferred _sending_ rate if the far end requests G723 to
be sent to it.
M - T.38 Real-time Facsimile - RFC 3362 (only add-on,
not valid without any other codec)
Note that the actual list of supported codecs may be
limited depending on the actual customer key code.
Service Type: pots pots Indicate the signaling type from this port.
r2
Port Info: Port-1 ASCII text Indicates a port location info or similar. Used for
Push button
Auto
Registration ID: 5550001 Subscriber’s SIP URL in the format of “user@host:port”,
where user part is alphanumeric character not relating to
the phone number, host part is alphanumeric character
not relating to SIP IP address. If portion ‘@host:port’ is
omitted, ‘Proxy Host’ or ‘Registrar Host’ values are used
as domain name. The registration ID is the “who” of a
SIP user, the ‘Name’.
....................................................................................................................................................................................................................................
363-211-555 7-149
Contact User Name: line.1.1.1 The username portion of the contact address. Case
sensitive. It will default to line1.1.1, line1.1.2, etc.
(INVITE method information,Contact header
information). The Contact User Name is the “where” of
a SIP user, the ‘mail address’.
Contact Parameter: param=Port1 This field adds a parameter-value pair to the registration
contact. Use of this field causes non-standard INVITE
messages. The form of the string is param=value’. If the
value portion is omitted, the ‘Contact User Name’ value
is used.
Auth User Name: abc The user name for authorization. If omitted, the
username portion of the ‘Registration ID’ is used. Case
sensitive.
Auth Password: xxxxxx The SIP password for the port
Metering Signaling: default default The preferred metering signaling method to be used for
reserved-polarity pay phones or home meters. Value ’default’ means that
meter-pulse
Note: This parameter is not applicable in DS1 mode.
Msg Waiting Indicator: none none This parameter is used to activate and configure the type
audible of message waiting indication (MWI) feature for a VoIP
port.
visual
none: deactivates the MWI feature.
both
audible: activates an audible indication towards the
subscriber, e.g. a customer key code dependent special
dial tone is used instead of the normal dial tone at
originating call attempts.
visual: activates a customer key code dependent line
signaling to trigger a visual indication on the subscriber
equipment, e.g. the activation of a light or info text in
an display.
Note: The subscribers equipment must support the
special line signaling which transfers the info of waiting
message(s) to it.
both: activates both the audible and visual indication.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
6 In the Config subtab, SIP Port Service window enter the appropriate parameters:
Options Default value Possible Comments

values
Call Waiting: Disabled Enabled Controls whether the call waiting service should be enabled
Disabled for normal calls.
3 Way Calling: Disabled Enabled enable/disable the feature for SIP

Disabled
....................................................................................................................................................................................................................................
7-150 363-211-555
Options Default value Possible Comments

values
Music On Hold: Disabled Enabled enable/disable the feature

Disabled
Anonymous Call Disabled Enabled If enabled, a call with notification “anonymous” will be
Rejection: Disabled rejected.
Extension Ringing: None None Controls the extension ringing signal according to japanese
Ir specification.
Sir
Extension Signaling: None None Indicate the signaling type for extension service.
Modem
Push-Button
PB Signaling Digits Len: 0 0..4 When we’re in DID PB signaling mode, an INVITE will
contain the substring we have to signal to the DID
terminal. This parameter indicates how many digits should
be used here. Value 0 means using all digits received. This
parameter is not applicable in DS1 mode.
Direct Dial In Signaling: None None Signaling method for direct dial in service towards the
Modem subscriber port for terminating calls
Push-Button
Subscriber Priority: Normal Emergency The priority level from non-emergency calls for this
Urgent subscriber
Normal
Non-Urgent
...................................................................................................................................................................................................

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

values
Port DigitMap Profile: 0 0..200 The profile index of the digit map profile to be used as port specific
digit map. If specified it overrules any default digit of the related
logical VoIP interface. If set to ’0’ no profile, i.e. no port specific
digit map, is applied for this port and the default digit map of the
related logical VoIP interface is used.
Port Profile: 1 1..36 The profile index of the ’Port’ profile to be used for this port.
Em. Num. Excl. Profile: 0 0..50 The profile index of the ’Emergency Number Exclude’ profile to be
used for this port.
Switch Profile: 1 1..32 The profile index of the ’Sip Switch’ profile to be used for this port.
....................................................................................................................................................................................................................................
363-211-555 7-151

values
Em. Call Profile: 0 0..50 The profile index of the Emergency Call profile to be used. If set to
’0’ no profile is applied and emergency calls are handled as normal
calls for this logical VoIP port.
Num. Xlate Profile: 0 0..50 The profile index of the Number Translation profile to be used. If set
to ’0’ no profile is applied and no number translation is performed for
this logical VoIP port.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
10 Select the ID`s subtab and enter the following parameters:.
Preferred Identity Select: None None Indicate which value should be

Parent-Hunt-Group used in P-Preferred-Identity
message.
Pre-line
Preferred-Number
Preferred Identity: None none, Parent Hunt Group, Indicates which value should be
Per-Line, Preferred number used in P-Preferred-Identity
message.
Inbound Caller ID: Disable-All Enable-All (caller number Controls whether the caller ID info
and name is displayed) (number and name) should be
Enable-Number- Only (caller displayed for inbound calls to this
number is displayed) port. (CLIP function)
number/name is displayed)
Outbound Caller ID Blocking: Block Block (restriction to show Controls whether the caller ID info
the caller number at the (number and name) should be
terminating side) UnBlock blocked for all outbound calls from
(caller number/name may be this port. (CLIR function)
displayed at the terminating
side
Inbound Call Waiting Caller ID: Disable-All Enable-All, Disable-All, Same as CLIP but for waiting
Enable-Number- Only callers
...................................................................................................................................................................................................

...................................................................................................................................................................................................
12 Select the XConnects subtab. To create a cross connection select the Network Group
and Port then select the TDM Group and Port and then click Apply.
will be reported.
....................................................................................................................................................................................................................................
7-152 363-211-555
Network
Interface: 1 1 The index for logical VoIP network interfaces.

Group: 1 1 The index for logical groups within a SIP VoIP
network interface.
Port: 1 1 to 2048 The index for SIP VoIP ports within a SIP logical
group.
TDM
Interface Type: RT (1) RT (1) Type of the logical TDM interface

GR303
R2 (3)
V5 (4)
Interface: 1 1 to 8 The index for TDM logical interfaces.
Port: 1 1 to 2047 The index for TDM ports within a TDM logical
interface.
The created cross connections is displayed in a table on the Xconnects window. To

delete a created cross connection select in the Module Id column the cross connection
to be deleted, and click Delete.
...................................................................................................................................................................................................
13 Select the Media Mon subtab and enter the following parameters:
Media Monitor Host: 0.0.0.0 any IP address or The IP address or FQDN of the media monitoring host
FQDN to which the media monitoring RTP streams are sent.
Depending on the Voip Port Media Monitor Control
specified here.
Inbound Port: 18000 1..65535 The TCP port on the media monitor host to which the
is to be sent.
Outbound Port: 18002 1..65535 The TCP port on the media monitor host to which the
is to be sent.
Media Monitor Control: Off Off, Controls whether media monitoring is to be activated
Inbound, for either
Outbound, - only the inbound RTP stream (network -> VoIP port)
Both-Directions or
or
....................................................................................................................................................................................................................................
363-211-555 7-153
to be monitored. Read only.
Media Monitor Group: 1 fixed to 1 The index of the logical VoIP group of the VoIP port to
be monitored.
Media Monitor Port: 1 1...2048 The index of the logical VoIP port of the VoIP port to
be monitored.
...................................................................................................................................................................................................

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

NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
If you want to return to the links for activating service for VoIP click back to activate
service for ICAP.
....................................................................................................................................................................................................................................
7-154 363-211-555
Provision duplex ICAPs in controlled mode or stand-alone

mode (optional)
...................................................................................................................................................................................................................................
Purpose
Use this procedure to set ICAPs provisioned in controlled mode or ICAPs provisioned
in stand-alone mode into duplex mode and to enable ICAP uplink protection if
required.
Assumptions
Two ICAPs are inserted in the AnyMedia Shelf.
Two ICAPs in adjacent slots where the left ICAP is inserted in the odd-numbered slot.
The FE2 ports of both ICAPs have to be connected via a LAN crossover cable (for
stand-alone mode only).
Requirements
For duplex mode a Y-cable assembly as described in “OAM&P Connectivity” (p. 2-13)
or a hub is required to connect to the LAN OAM&P port (FE1 port) of both ICAPs.
Procedure
Important! Do not connect E1/DS1 cables to the ICAP before the ICAP has been
set to “duplex”.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Select the Duplex tab.

...................................................................................................................................................................................................
4 From the Protection Mode pull-down menu select Duplex.

...................................................................................................................................................................................................
5 In the Auto Copy Mode pull-down menu select Enabled (stand-alone mode only).
Click Apply.
...................................................................................................................................................................................................
6 Verify that the packs, active and standby reside in the correct slots for duplex
configuration and have the same software version.
System displays:
...................................................................................................................................................................................................................................
363-211-555 7-155
Detailed procedure descriptions Provision duplex ICAPs in controlled mode or stand-alone
mode (optional)
Active Pack: the ICAP in preferred slot

Standby Pack: the ICAP in protection slot
Operational State: ReadyToProtect
Note that if the Operational State: GettingReadyToProtect is displayed, wait until
the Operational State becomes ReadyToProtect before continuing.
System Fault: Duplex provisioning is denied if the protection slot is provisioned
for any type of AP. Such provisioning must be removed by the operator before
duplex provisioning can proceed.
For ICAP in stand-alone mode only. When the standby ICAP contains a different
software version the active ICAP will copy its software to the standby ICAP
because Duplex Auto Copy is enabled. After completion of copy, the standby
ICAP will reset.
...................................................................................................................................................................................................
7 Go to the next procedure “Wiring for ICAPs” (p. 7-174).

system turn-up.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-156 363-211-555
Provision VLANs, IP addresses and Routing on ICAP

...................................................................................................................................................................................................................................
Purpose
Use this procedure to assign a dedicated IP address for each traffic type, i.e. RTP,
signaling and, in stand-alone mode, the inband management (OAM&P). That is, each
traffic type can have one dedicated IP address, which can be assigned to a dedicated
VLAN ID.
Configuration examples see “Examples of multiple IP addresses configuration on
ICAP” (p. 7-161).
Background
The operator defines via tables in the ICAP the assignment of the traffic types to IP
addresses and to VLAN IDs. Each traffic type belongs to a separate IP address or
VLAN ID respectively, and is forwarded to the IPFM via the backplane (in controlled
mode) and/or the FE1 uplink. In stand-alone mode the separated data traffic is
forwarded directly to the FE1 uplink on the ICAP.
Configuration example:
Routing Policy table Static Route table VLAN table
Pol Idx Src IP Source Mask RT Idx# RT Idx Dest IP Dest Mask Gatway VLAN IP Addr. Mask BP FP VPT
1 30.0.0.0 255.0.0.0 3 2 0.0.0.0 0.0.0.0 10.0.0.10 10 10.0.0.1 255.0.0.0 T 1
2 10.0.0.1 255.255.255.255 2 3 0.0.0.0 0.0.0.0 40.0.0.40 20 20.0.0.1 255.0.0.0 T 3
4 20.0.0.1 255.255.255.255 4 4 0.0.0.0 0.0.0.0 20.0.0.20 40 40.0.0.1 255.0.0.0 T 5
OAM&P for subtending AnyMedia RTs Dest IP Destination IP address BP Backplane

uses the 30.x.x.x subnet for its ROCs and Src IP Source IP address FP Faceplate Port
routes them via the 40.x.x.x subnet, i.e. VPT VLAN Priority Tag
the 40.0.0.40 gateway, upstream.
RTP: 10.0.0.1
Signaling: 20.0.0.1
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Select the IP Interface subtab, and define the logical IP interfaces to be used as inband
ROC (Remote Operational Channel) toward remote terminals:

value values
IP Interface Index: roc-1 roc-1 to The index for logical IP interfaces and the logical ROC
roc-8 ports.
...................................................................................................................................................................................................................................
363-211-555 7-157
Detailed procedure descriptions Provision VLANs, IP addresses and Routing on ICAP

value values
Admin State: disabled enabled Specifies whether the logical IP interface is enabled or
disabled disabled. Initial default is ’disabled’. The interface can be
enabled only when a valid IP address is assigned.
IP Address: The local IP address of the logical IP interface. The
initial IP address is 0.0.0.0. An interface IP address
cannot be changed to a new one if there are routing
entries in the static routing table associated with the old
IP address. To remove an IP address from a logical IP
interface, enter 0.0.0.0 again. The IP address must be
unique across all interfaces (including the VLAN IP
interfaces specified in the VLAN table).
Network Mask: The network mask for the logical IP interface. The initial
value with no IP address entered is 0.0.0.0. After the IP
address has been entered, the default submask value
corresponds to the network class of the IP address, if not
especially specified.
Remote IP The remote IP address parameter identifies the address of
Address: the remote end of the point-to-point link and must be
within the same subnet as specified for the local IP
address and netmask.
...................................................................................................................................................................................................
3 Click Apply.
...................................................................................................................................................................................................
4 Select the IP Routing tab.

...................................................................................................................................................................................................
5 In the Static Route Table subtab, define the parameters to enable policy-based routing:
Note: A routing entry can only be added if the specified gateway is in a subnet of a
local IP interface (Remote Operation Channel or Layer 3 VLAN IP interface).

value values
Route Table 1 1..4 The actual routing table to be used for each packet
Index: depends on the matching rule in the Routing Policy table.
If no matching rule is found in the Routing Policy table,
the default routing table with index 1 is used.
Destination IP 0.0.0.0 The destination address is the host IP address reached via
Address: this route. Use a 0.0.0.0 destination with a 0.0.0.0
network mask to indicate a default route. Use an IP
address with a 255.255.255.255 submask to indicate a
host route.
....................................................................................................................................................................................................................................
7-158 363-211-555

value values
Network Mask: 0.0.0.0 The destination mask is the network address reached via
this route. Use a 0.0.0.0 destination with a 0.0.0.0
network mask to indicate a default route. Use an IP
address with a 255.255.255.255 submask to indicate a
host route.
Gateway: 0.0.0.0 The gateway address is the IP address of the gateway
through which packets are sent to the destination address.
The gateway must be on a directly connected network or
subnetwork, that means the gateway’s network portion of
an IP address and the corresponding interface’s network
portion of an IP address must match.
TOS bit policy: 0 The TOS bits of the packet to match this rule.
The TOS bit value is set to 0 for now.
...................................................................................................................................................................................................
6 Click Apply.
...................................................................................................................................................................................................
7 In the Routing Policy subtab, define the policy rules:

value values
Routing Policy 1 1..10 The index for the routing policy rules.
Index:
Source IP 0.0.0.0 The source IP address or subnet address respectively
Address: of the packet to match this rule.
Source Net Mask: 255.255.255. This network mask defines which bits of the source
255 IP address of the packet have to match the Routing
Policy Source IP Address.
Examples: To exactly match the source IP addresses
used for Signaling, RTP or Management, provision
the exact IP address (Routing Policy Source IP
Address) and specify a host mask of
’255.255.255.255’ here. To match the source IP
addresses used, e.g. on the downstream remote
operation channels, provision only the aggregate net
address (Routing Policy Source IP Address) and
specify a net mask of e.g. ’255.255.255.0’ here.
Route Table 1 1-4 Specifies the table index to be used in the Static
Index: Route Table if the packet matches this rule
Not supported yet.
....................................................................................................................................................................................................................................
363-211-555 7-159
...................................................................................................................................................................................................
8 Click Apply.
...................................................................................................................................................................................................
9 Select the VLAN subtab, define layer 3 VLANs with the associated logical IP interface
for the network uplink(s):

value values
Vlan ID: 1 1..4091 The 12-bit VLAN ID used in the VLAN Tag header.
VLAN ID 4092 to 4095 are reserved for system-internal
use and therefore excluded here.
Vlan Name: The name of this VLAN must be unique across all
VLANs.
IP Address: The IP address of the logical IP interface on this VLAN.
The IP address must be unique across all interfaces
(including the Remote Operations Channel interfaces
specified in the IP Interface table).
Subnet Mask: The network mask for the logical IP interface. The
resulting IP subnet must be unique across all interfaces
(including the Remote Operations Channel interfaces
specified in the IP Interface table).
Priority Tag 0 0-7 The default 3-bit VLAN Priority used in the VLAN Tag
[VPT]: header on tagged port(s).
Backplane Port Tagged Tagged Specifies whether the BP/FP port is member of the
[BP]: UnTagged VLAN as either tagged or untagged port or not at all. A
specific port can only be an untagged member for exactly
UnJoin
Faceplate Port Tagged one VLAN. This setting defines whether the outgoing
[FP]: traffic for a specific VLAN is sent with or without a
VLAN tag on this port.
...................................................................................................................................................................................................
10 Click Apply.
...................................................................................................................................................................................................

From the menu bar, select IP SubSystem -> IP Data -> System -> Save Changes to
NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
7-160 363-211-555
If you want to return to the links for activating service for VoIP click back to activate
service for ICAP.
Examples of multiple IP addresses configuration on ICAP
Configuration with 1 IP address - ICAP in controlled mode (untagget VLAN)
Control and RTP IP address 10. 10.20.100
Mask 255.255.255.0
Default gateway 10.10.20.1
VLAN_ID 120
VLAN_Priority 2
Interface Backplane Port (BP) / UnTagged

VLAN ID = 120/ Name = cntl_rtp / IP_Addr = 10.10.20.100 / Mask = 255.255.255.0 /
Priority = 2 / BP = UnTagged / FE1 = Unjoin
Static Route Table R_Idx = 1 / Dest_ IP_Addr = 0.0.0.0 / Mask = 0.0.0.0 / Gateway = 10.10.20.1
Route Policy P_Idx = 1 / Source_IP_Addr = 10.10.20.100 / Mask = 255.255.255.255 / R_Idx = 1

(optional)
Configuration with 1 IP address - ICAP in controlled mode (tagget VLAN)
Control and RTP IP address 10.10.20.100

Mask 255.255.255.0

VLAN_ID 120
VLAN_Priority 2
Interface Backplane Port (BP) / Tagged

VLAN ID = 120/ Name = cntl_rtp / IP_Addr = 10.10.20.100 / Mask = 255.255.255.0 /
Priority = 2 / BP = Tagged / FE1 = Unjoin

(optional)
Configuration with 2 IP address - ICAP in controlled mode (tagget VLANs)
Control IP address 10.10.20.100
Mask 255.255.255.0

VLAN_ID 120
VLAN_Priority 2
RTP IP address 10.10.30.100
Mask 255.255.255.0

VLAN_ID 130
....................................................................................................................................................................................................................................
363-211-555 7-161
VLAN_Priority 3

VLAN ID = 120/ Name = Cntl / IP_Addr = 10.10.20.100 / Mask = 255.255.255.0 / Priority
= 2 / BP = Tagged / FE1 = Unjoin
ID = 130/ Name = RTP / IP_Addr = 10.10.30.100 / Mask = 255.255.255.0 / Priority

= 3 / BP = Tagged / FE1 = Unjoin
R_Idx = 2 / Dest_ IP_Addr = 0.0.0.0 / Mask = 0.0.0.0 / Gateway = 10.10.30.1

(optional)
P_Idx = 2 / Source_IP_Addr = 10.10.30.100 / Mask = 255.255.255.255 / R_Idx = 2
Configuration with 1 IP address - ICAP in stand-alone mode (tagget VLAN)
Management, Control and RTP IP 10.10.20.100

address
Mask. 255.255.255.0
VLAN_ID 120
VLAN_Priority 2
Interface FE1 / Tagged
VLAN ID = 120/ Name = vtf001/ IP_Addr = 10.10.20.100 / Mask = 255.255.255.0 /

Priority = 2 / FE1 = Tagged

(optional)
Configuration with 2 IP addresses - ICAP in stand-alone mode (Mgmt: untagged VLANs / Control and RTP: tagged VLAN)
Management IP address 10.10.20.100
Mask 255.255.255.0
VLAN_ID 120
VLAN_Priority 1
Interface FE1 / UnTagged

Control and RTP IP address 10.10.30.100
Mask 255.255.255.0
VLAN_ID 130
VLAN_Priority 2
....................................................................................................................................................................................................................................
7-162 363-211-555

Priority = 1/ FE1 = UnTagged
ID = 130/ Name = Cntl_RTP / IP_Addr = 10.10.30.100 / Mask = 255.255.255.0 /
Priority = 2 / FE1 = Tagged

(optional)
Configuration with 3 IP addresses - ICAP in stand-alone mode (Tagged VLANs with a static route entry for a DNS server)
Management IP address 10.10.20.100
Mask 255.255.255.0
VLAN_ID 120
VLAN_Priority 1
Control IP address 10.10.30.100
Mask 255.255.255.0
VLAN_ID 130
VLAN_Priority 2
RTP IP address 10.10.40.100
Mask 255.255.255.0
VLAN_ID 140
VLAN_Priority 3
DNS server 10.10.30.123
Gateway 10.10.30.1

Priority = 1/ FE1 = Tagged
ID = 130/ Name = Cntl / IP_Addr = 10.10.30.100 / Mask = 255.255.255.0 / Priority

= 2 / FE1 = Tagged
ID = 140/ Name = RTP / IP_Addr = 10.10.40.100 / Mask = 255.255.255.0 / Priority
= 3/ FE1 = Tagged
....................................................................................................................................................................................................................................
363-211-555 7-163
R_Idx = 1 / Dest_ IP_Addr = 10.10.30.123 / Mask = 255.255.255.255 / Gateway =

10.10.30.1

(optional)
....................................................................................................................................................................................................................................
7-164 363-211-555
Provision parameters for V5.2 aggregation on an ICAP

...................................................................................................................................................................................................................................
Purpose
Use this procedure to create a V5 Interface entity to concentrate subscribers connected
to one or more subtending V5 systems into one VoIP interface of this ICAP.
Two subprocedures must be completed to provision the V5 aggregation on an ICAP:
• “V5 Interface provisioning in ICAP” (p. 7-165)
• “V5 User port provisioning” (p. 7-172).
To create a POTS subscriber entity, see the procedure GR-5610 POTS subscriber
growth in the chapter System Reconfiguration of the Commands and Procedures for
Narrowband Services with TDM COMDAC (363–211–119).
Assumptions
The system is configured via customer key and operates in E1 mode.
All required provisioning is complete.
V5 Interface provisioning in ICAP

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Select the V5 Network tab.

...................................................................................................................................................................................................
3 In the Interface subtab, enter the appropriate parameters to define a V5 network

interface:

value values
Interface ID 1 1..8
Oper Status In service In Service Indicates the operational status of the V5
Out of Service interface.
Read only.
Admin Status Disabled Enabled Specifies whether the V5 interface is enabled
Disabled or disabled.
Protocol Type V5.2 Defines the protocol used for this V5 interface.
Currently only the V5.2 protocol is supported.
Read only.
...................................................................................................................................................................................................................................
363-211-555 7-165
Detailed procedure descriptions Provision parameters for V5.2 aggregation on an ICAP

value values
Unique Identifier 0 0..16777215 Defines the unique identifier for this V5
interface. This identifier is used within the V5
protocol to ensure that the correct systems are
interconnected or that a mismatch can be
detected.
The Unique Identifier must be provisioned at
both ends to the same value. It is checked
during interface startup to prevent accidental
misconfigurations of the interconnection.
This identifier must be unique across all V5
interfaces provisioned in this ICAP, otherwise
the V5 interface creation is denied.
Provisioning 0 0..127 Defines the active provisioning variant number
Variant for this V5 interface. This variant number is
used within the V5 protocol to ensure that the
correct provisioning data set is used on both
interconnected systems.
Note that currently only one variant (variant 0)
is supported.
Service Degrade 50 5..95 The service degrade threshold defines the
percentage of failed links of this interface at
which an alarm shall be sent by the system.
Flag Monitoring Disabled Enabled Defines whether the communication channels
Disabled contained in this interface shall be monitored
for HDLC flags or not.
Read only.
Protocol Edition Edition 2 Edition 2 Defines which edition of the V5 protocol
standard is to be used on this interface.
Read only.
Note that currently only V5.2 edition 2 is
supported.
Identification The interface identification is not used by the
system, and serves only as easy identification
for the operator.
...................................................................................................................................................................................................
4 Click Apply.
...................................................................................................................................................................................................
5 In the Links subtab Logical Links window, enter the appropriate parameters to
provision a logical V5 link:
....................................................................................................................................................................................................................................
7-166 363-211-555

value values
Link ID 1 1..8 The index of the logical V5 link.
Oper Status Out of In Service Indicates the operational status of the V5 link.
Service Out of Service Read only
Admin Status Disabled Enabled Specifies whether the V5 link is enabled or
Disabled disabled.
Feeder Address Fdr-1 Fdr-1 to Fdr-8 The index of the TDM feeder to be used as
V5 link.
Note that this feeder index can only be set
during creation of the table row. A later
change is not supported, and will be rejected.
Unique Identifier 0 0..255 The unique identifier for this V5 link. This
identifier is used within the V5 protocol to
ensure that the correct links are
interconnected or that a mismatch can be
detected.
both ends to the same value. It is checked
during the link identification procedure to
prevent accidental misconfigurations of the
interconnection.
This identifier must be unique within each V5
interface of this ICAP.
NE Signal Degrade -6 -7 Near-end E1 signal degrade (in 10E<value>)
-6 to be regarded as low bit error threshold. If
the actual signal bit error rate exceeds the
-5
specified threshold, an alarm is raised by the
-4 system while still keeping the feeder
operational.
FE Signal Degrade -6 -7 Far-end E1 signal degrade (in 10E<value>) to
-6 be regarded as low bit error threshold. If the
actual signal bit error rate exceeds the
-5
specified threshold, an alarm is raised by the
-4 system while still keeping the feeder
operational.
...................................................................................................................................................................................................
6 Click Apply.
...................................................................................................................................................................................................
7 Once a V5 link is cross-connected to a V5 Interface, the read-only table in the Links

subtab Timeslots window shows the V5 link time slot usage.
....................................................................................................................................................................................................................................
363-211-555 7-167
Lnk Time Slot Time Slot Type
Note that this table especially shows the usage of the V5 link time slots 15, 16 and 31.
Those can either be used as bearer channels, or to serve V5 communication channels.
...................................................................................................................................................................................................
8 Define the cross-connection between logical V5 interfaces and the logical V5 links in
the Links subtab XCons window:

value values
V5 Link 1..8 Parameters defining a logical V5 link.
V5 Interface 1..8 Parameters defining a logical V5 TDM
network interface.
Note that this cross-connection is of type 1 to n, which means that you can connect
one interface to many links.
...................................................................................................................................................................................................
9 Click Apply.
...................................................................................................................................................................................................
10 In the Communication subtab Channel window, create a V5 communication channel:

value values
Interface ID 1 1..8 Defines a V5 interface ID.
Comm. Channel ID 1..2 Defines a logical V5 communication channel.
Unique Identifier 0 0..65503 The unique identifier for this V5
communication channel. This identifier is used
within the V5 protocol to uniquely address a
V5 communication channel within a V5
interface.
both ends to the same value, and must be
unique within each V5 interface of this ICAP.
A modification of this value is denied if the
related V5 Interface is not administratively set
to ’disabled’
Current Link This parameter displays the V5 link number
which is currently used for this
communication channel (read-only).
....................................................................................................................................................................................................................................
7-168 363-211-555

value values
Current Timeslot 0 This parameter displays the V5 link timeslot
number which is currently used for this
communication channel (read-only).
Current Oper Indicates the operational status of the V5
Status communication channel (read-only).
...................................................................................................................................................................................................
11 Click Apply.
...................................................................................................................................................................................................
12 In the Communication subtab Path window, define the V5 communication paths:

value values
Interface ID 1 1..8 The index of the logical V5 interface.
Comm. Path ID 1 1..4 The index for logical V5 communication paths.
Comm. Path BCC BCC (Bearer Channel Connection) represents the
Type Common Ctrl signaling used for the dynamic allocation of
bearer channels on V5 links.
Link Ctrl
Common-Ctrl (Common and Port Control)
PSTN
represents the signaling used for the overall V5
interface and port control, e.g. interface startup,
port blocking, checking V5 interface ID and
variant, PSTN Restart, unblock all relevant Ports
etc.
Link-Ctrl (Link Control) represents the signaling
used for the V5 link control.
PSTN (Public Switched Telephone Network)
represents the signaling used to transfer telephony
events, e.g. on-/off-hook events, pulsed digit
information, hook flashes, ringing cadences etc.
...................................................................................................................................................................................................
13 Click Apply.
...................................................................................................................................................................................................
14 In the Communication subtab CP-CCXCons window, define the logical

cross-connections between a logical V5 Communication Path and a logical V5
Communication Channel.
....................................................................................................................................................................................................................................
363-211-555 7-169

value values
Comm. Path
Comm. Path ID 1 1..4 The index of the logical V5 communication
paths.
Comm. Channel
Comm. Channel ID 1 1..2 The index of the logical V5 communication
channel.
Note that this cross-connection is of type n to 1, which means that you can connect
many Communication Paths to one Communication Channel.
...................................................................................................................................................................................................
15 Click Apply.
...................................................................................................................................................................................................
16 In the Communication subtab CC-TSXCons window, define the parameters of

cross-connections between logical V5 Communication Channels and V5 Link time
slots.
Note that this cross-connection is of type 1 to 1, which means that you can connect
one V5 communication channel to exactly one V5 link timeslot.

value values
Comm. Channel
Comm. Channel 1 1..2 The index of the logical V5 communication
ID channel.
Timeslot
Link ID 1 1..8 The index of the logical V5 interface.
Timeslot ID 1 15, 16, 31 The index of the V5 link timeslot.
...................................................................................................................................................................................................
17 Click Apply.
...................................................................................................................................................................................................
18 In the Protection subtab Protection Group window, define the parameters for a
logical V5 Protection Group:
....................................................................................................................................................................................................................................
7-170 363-211-555

value values
Protection ID 1 1..2 The index of the logical V5 protection group.
Note:
Protection Group 1 is dedicated to protecting the V5 communication channel which
carries the signaling types ’bcc’, ’common-ctrl’ and ’link-ctrl’, i.e. the communication
channel also cross-connected to Protection Group 1. By cross-connecting a V5 link
time slot to Protection Group 1, this time slot is defined to be used as protection in
case the V5 link, originally carrying this communication channel, fails.
Note that the Protection Group 1 may also carry the PSTN protocol, in this case no
Protection Group 2 is used.
Protection Group 2 is dedicated to protecting the other communication channels, i.e.
the ones which carry the signaling type ’pstn’. By cross-connecting V5 link time slots
to Protection Group 2, these time slots are defined to be used as protection for those
communication channels also cross-connected to Protection Group 2.
...................................................................................................................................................................................................
19 Click Apply.
...................................................................................................................................................................................................
20 In the Protection subtab PG-CCXCons window, define the cross-connections between

logical V5 Protection Groups and Communication Channels:

value values
Protection Group
Interface ID 1..8 The index of the logical V5 interface.
Protection ID 1..2 The index of the logical V5 protection group.
Comm. Channel
Interface ID 1..8 The index of the logical V5 interface.
Comm. Channel 1..2 The index of the V5 communication channel.
ID
...................................................................................................................................................................................................
21 Click Apply.
...................................................................................................................................................................................................
22 In the Protection subtab PG-TSXCons window, define the cross-connections between

logical V5 Protection Groups and V5 Link time slots:
....................................................................................................................................................................................................................................
363-211-555 7-171

value values
Protection Group
Interface ID 1...8 The index of the logical V5 interface.
Protection ID 1...2 The index of the logical V5 protection group.
Timeslot
Link ID 1...8 The index of the logical V5 link, which is
used as target link for protection switching in
case that the normal link fails.
Timeslot ID 15, 16, 31 The index of the V5 link timeslot.
...................................................................................................................................................................................................
23 Click Apply.
...................................................................................................................................................................................................

NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
V5 User port provisioning

Make sure that the V5 interface provisioning in ICAP is successfully completed and a
V5 interface is available.
...................................................................................................................................................................................................
1 In the User Ports subtab User Prot window, define the parameters for a V5 user port:

value values
User Port ID Multi IDs, The index of the logical V5 user port.
1..2047
User Port Type POTS POTS Specifies the V5 User Port type.
POTS (Plain Old Telephone Service)
Layer 3 Address 0 0..32767 This V5 layer 3 address is used within the V5
protocol to uniquely address a POTS port
within a V5 interface. The V5 layer 3 address
must be provisioned at both ends to the same
value, and must be unique within each V5
interface of this ICAP.
....................................................................................................................................................................................................................................
7-172 363-211-555
...................................................................................................................................................................................................
2 Click Apply.
...................................................................................................................................................................................................
3 In the User Ports subtab XCons window, define the cross-connections between logical
V5 User Ports and V5 Interfaces.

value values
V5 Interface
V5 Interface 1...8 The index of the logical V5 interface.
V5 User Port
V5 User Port 1...2047 Parameters defining a logical V5 User Port.
...................................................................................................................................................................................................
4 Click Apply.
...................................................................................................................................................................................................

NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
If you want to return to the links for activating service for ICAP, click the text back to
....................................................................................................................................................................................................................................
363-211-555 7-173
Wiring for ICAPs

...................................................................................................................................................................................................................................
Purpose
This procedure provides information on how to wire the ICAP, that is wiring
information for the pack when it operates in controlled mode and for stand-alone
mode, for simplex and for duplex operation mode. It covers E1/DS1 cabling as well as
the uplink cabling to the IP network.
This procedure contains four subprocedures which describe - dependent on the
configuration - the following:
• The cabling for a simplex configuration in controlled mode.
• The cabling for a simplex configuration in stand-alone mode.
• The cabling for a duplex configuration in controlled mode.
• The cabling for a duplex configuration in stand-alone mode.
Note, that in some cases it is important to do the cabling in the right order. In a duplex
configuration do not connect the E1/DS1 cables before the ICAP is set to duplex.
Additionally to the four subprocedures the procedure provides information about the
required cables and it shows several wiring examples.
The OAM&P management is done via an inband management channel and does not
require any wiring.
Important! Do not use a common USB connector! Always use the special adapter
cable (ED7C873-31 G8) to connect to the CONSOLE connector on this pack.
Although the CONSOLE connector below the FAULT LED looks like a USB
connector, it is not a USB connector. It will not work if a laptop is connected, but
attaching a true USB host or peripheral to this port may damage the USB drivers
of this device or the pack.
The connection to the serial port is determined for initial system turn-up in
stand-alone mode only.
Cables
Depending on the configuration (simplex or duplex) and the operation mode the
following cables are required to connect to the ICAP(s):
Mode Connector on Interface for Cable description Cable

faceplate
Simplex mode:
Simplex (in M DS1/E11, 2

E1/DS1 downlink ED7C873-31 G6
controlled mode) feeders
...................................................................................................................................................................................................................................
7-174 363-211-555
Detailed procedure descriptions Wiring for ICAPs
Mode Connector on Interface for Cable description Cable

faceplate
Simplex (in M DS1/E11, 2

E1/DS1 downlink ED7C873-31 G6
stand-alone mode) feeders
FE1 10/100Base-T Wired Commercially

uplink (for straight-through, available
stand-alone mode RJ-45 connectors 100Base-T cable
only)
CONSOLE RS232 port with Adapter cable ED7C873-31 G8

USB-A physical with USB-A
connector for connector
initial system (DB9-to-USB
turn-up in RS232)
stand-alone mode
Duplex mode:
Duplex in M DS1/E1 (on E1/DS1 downlink Y-cable ED7C873-31 G5

controlled mode active pack) 1, 2 feeders to both
M DS1/E1 (on ICAPs
standby pack) 1, 2
Duplex in M DS1/E1 (on E1/DS1 downlink Y-cable ED7C873-31 G5

stand-alone mode active pack) 1, 2 feeders to both
M DS1/E1 (on ICAPs
standby pack) 1, 2
FE2 (on active Interconnection of LAN crossover ED7C873-31 G7

pack) the LAN ports on cable for 1:1
FE2 (on standby both ICAPs protection
pack)
FE1 (on active 10/100Base-T Wired Commercially
pack) uplinks (for straight-through, available
FE1 (on standby stand-alone mode RJ-45 connectors 100Base-T cable;
pack) only) Two cables
required, one for
each uplink
CONSOLE RS232 port with Adapter cable ED7C873-31 G8
USB-A physical with USB-A
connector for connector
initial system (DB9-to-USB
turn-up in RS232)
stand-alone mode
Notes:
1. The “Buddy” connector (B DS1/E1) is for future use.
2. The connector M DS1/E1 on the faceplate supports 8 Tx/Rx feeders each.
Note that for special applications additional cables may be required. For more
information about these cables refer to the following individual examples.
Example: Wiring for stand-alone mode

The next figure shows an example with two ICAPs in duplex configuration in
stand-alone mode. In this example the ICAP E1/DS1 downlink feeders connect to the
E1/DS1 feeders in the same shelf.
....................................................................................................................................................................................................................................
363-211-555 7-175
Note that in stand-alone mode for duplex the FE2 ports of both ICAPs have to be
connected via a LAN crossover cable and that the E1/DS1 feeder cables that are
directly connecting to the ICAPs are different for duplex mode from those for simplex
mode.
IP Network
Commercially available
100Base-T cables ED7C818-36 G2x if the hosting shelf is ETSI V5
ED7C874-31 G1x if the hosting shelf is LAG 1900
FAN UNIT
STATUS
Lucent GREEN - ACTIVE RED - FAULT
BLINKING GREEN -
INITIALIZING
IO_E1-P IO_E1 IO_E1 RGU RGU PFU PFU

IO_E1P
-48 VB
-48 VA
IO_E1
IO_E1
RGU
RGU
PFU
PFU
0 1 2 0 1 0 1
LPI600 LPI600
S1:1 S1:1
ED7C873-31 G7
Lucent Lucent
AFM or Application Pack
F/A CR MJ/MN F/A CR MJ/MN
NE FE CLF NE FE CLF
required for
CONSOLE
CONSOLE
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
FE1
FE1
stand-alone configurations
FE2
FE2
COMDAC
COMDAC
B DS1/E1 B DS1/E1
in duplex mode
CIU
M DS1/E1 M DS1/E1
1 2 1 01 02 03 04 05 06 07 08 09 10 11 12 13 14
COM-1 COM-2 CIU AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8 AP-9 AP-10 AP-11 AP-12 AP-13 AP-14
ED7C873-31 G6
for simplex
ED7C873-31 G5
for duplex
ED7C874-31 G1x
DDF
Note that Tx always connects to Rx and vice versa
Example: Wiring to remote terminal

The next figure shows as an example the wiring for ICAPs (in duplex mode) in an
application where the ICAP aggregates the E1/DS1 feeders from a remote terminal.
Note that in stand-alone mode for duplex the FE2 ports of both ICAPs have to be
connected via a LAN crossover cable and that the E1/DS1 feeder cables that are
directly connecting to the ICAPs are different for duplex mode from those for simplex
mode.
....................................................................................................................................................................................................................................
7-176 363-211-555
IP Network
Commercially available
100Base-T cables
Host Terminal
FAN UNIT
STATUS
BLINKING GREEN -
INITIALIZING
IO_E1P
-48 VB
-48 VA
IO_E1
IO_E1
RGU
RGU
PFU
PFU
0 1 2 0 1 0 1
LPI600 LPI600
S1:1 S1:1
Lucent Lucent
IPFM or Application Pack

NE FE CLF NE FE CLF
CONSOLE
CONSOLE
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
FE1
FE1
FE2
FE2
COMDAC
COMDAC
IPFM
B DS1/E1 B DS1/E1
CIU
M DS1/E1 M DS1/E1
1 2 1 01 02 03 04 05 06 07 08 09 10 11 12 13 14
ED7C818-36 G2x if Remote Terminal is ETSI V5

ED7C874-31 G1x if Remote Terminal is LAG 1900 ED7C873-31 G6
for simplex
ED7C873-31 G5
Lucent ACTIVE FAULT
for duplex
A B C D E F G H J
HDLC-1 HDLC-2 IO_E1-P IO_E1-1 IO_E1-2 IO_E1-3 IO_E1-4 PFU A1 B1 C1 D1 E1 F1 G1 H1 J1
IO_HDLC
IO_HDLC
-48 VB
-48 VA
E1 DOWN
E1 DOWN
Ringing
E1 UP
E1 UP
IO_E1
IO_E1
IO_E1
IO_E1
IO_E1
TAP
PFU
LAN
J2
ALARM OUT RTU ALARM IN

1 2 1 1 2 3 4
ED7C874-31 G1x
D2 F2 H2 J3
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
AFM or NB-AP
DDF
COMDAC
COMDAC
OAP
CIU
1 2 1 01 02 03 04 05 06 08 09 10 11 12 13 14 15 16
COM-1 COM-2 CIU AP-1 AP-2 AP-3 AP-4 AP-5 AP-6 AP-7 AP-8 AP-9 AP-10 AP-11 AP-12 AP-13 AP-14 AP-15 AP-16
Remote Terminal Note that Tx always connects to Rx and vice versa
Example: Wiring ICAP(s) using IP-AFM(s) as uplink connection

The next figure shows as examples the wiring for ICAPs in simplex and duplex mode
in an application where the IP traffic from the ICAP(s) is aggregated and via the GbE
or FE uplink(s) on the IP-AFM(s) transported to an IP/Ethernet network. For the
interconnection ICAP(s) to IP-AFM(s) commercially available 100Base-T cables can be
used.
....................................................................................................................................................................................................................................
363-211-555 7-177
Commercially
IP/Ethernet available
Network 1000Base-SX/LX/TX cable
Simplex Configuration
FAN UNIT
STATUS
BLINKING GREEN -
INITIALIZING
IO_E1P
-48 VB
-48 VA
IO_E1
IO_E1
RGU
RGU
PFU
PFU
0 1 2 0 1 0 1
LPI600
S1:1
LPI960
Lucent Lucent
CONSOLE
F/A CR MJ/MN
10 BASE-T
NE FE CLF
CONSOLE
100BASE-T0
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
FE1
100BASE-T1
FE2
SFP1 SFP2
Commercially
COMDAC
COMDAC
SFP1
B DS1/E1
available
SFP2
CIU
SFP3 SFP4
100Base-T cable
SFP3
M DS1/E1
1 2 1 01 02 03 04 05 06 07 08 09 10 11 12 13 14
SFP4
IP-AFM ICAP
Duplex Configuration
FAN UNIT
STATUS
BLINKING GREEN -
INITIALIZING

IO_E1P
-48 VB
-48 VA
IO_E1
IO_E1
RGU
RGU
PFU
PFU
0 1 2 0 1 0 1
LPI600 LPI600
S1:1 S1:1
LPI960 LPI960
Lucent Lucent
Lucent Lucent
CONSOLE
CONSOLE

10 BASE-T
10 BASE-T
NE FE CLF NE FE CLF
CONSOLE
CONSOLE
100BASE-T0
100BASE-T0
Commercially
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
Application Pack
FE1
FE1
Commercially
100BASE-T1
100BASE-T1
FE2
FE2
available
SFP1 SFP2 SFP1 SFP2
COMDAC
COMDAC
available
SFP1
SFP1
1000Base-SX/LX/TX cable
B DS1/E1 B DS1/E1
SFP2
SFP2
CIU
SFP3 SFP4 SFP3 SFP4

100Base-T cable
SFP3
SFP3
M DS1/E1 M DS1/E1
1 2 1 01 02 03 03 05 06 07 08 09 10 11 12 13 14
SFP4
SFP4
IP-AFMs ED7C873-31 G7
required for ICAPs
in duplex mode
Note that Tx always connects to Rx and vice versa
Pin assignment of connectors on DS1/E1 cables

The next figures show the pin assignment for the 36-pin AMP champ ribbon style
connectors on the DS1/E1 cables,. Shown is the wiring / soldering side (male) of the
36-pin AMP champ ribbon style connector(s) which is identical to the contact side
(female) of the AP faceplate on the ICAP.
....................................................................................................................................................................................................................................
7-178 363-211-555
E1/DS1 cable for simplex mode
Blue binder Blue binder

W/BL 1 19 BL/W
TXTIP 1 TXRING 1
TXTIP 2 W/O O/W TXRING 2
TXTIP 3 W/G G/W TXRING 3
Transmit (output) W/BR BR/W Transmit (output)
TXTIP 4 TXRING 4
signal from ICAP, W/SL SL/W signal from ICAP,
TXTIP 5 TXRING 5
tip lead R/BL BL/R ring lead
TXTIP 6 TXRING 6
TXTIP 7 R/O O/R TXRING 7
TXTIP 8 R/G G/R TXRING 8
9 27 JUMPER
Orange binder Orange binder
RXTIP 1 R/BR BR/R RXRING 1
RXTIP 2 R/SL SL/R RXRING 2
RXTIP 3 BLK/BL BL/BLK RXRING 3
Receive (input) BLK/O O/BLK Receive (input)
RXTIP 4 RXRING 4
signal towards ICAP, BLK/G G/BLK signal towards ICAP,
RXTIP 5 RXRING 5
tip lead BLK/BR BR/BLK ring lead
RXTIP 6 RXRING 6
RXTIP 7 BLK/SL SL/BLK RXRING 7
RXTIP 8 Y/BL BL/Y RXRING 8
18 36
E1/DS1 Y-cable for duplex mode
W/BL 1 19 BL/W R/BR 1 19 BR/R

TXTIP 1 TXRING 1 Transmit (output) TXTIP 1 TXRING 1
TXTIP 2 W/O O/W TXRING 2 TXTIP 2 R/SL SL/R TXRING 2
signal from ICAP,
TXTIP 3 W/G G/W TXRING 3 TXTIP 3 BLK/BL BL/BLK TXRING 3
ring lead
Blue binder
Transmit (output)
Blue binder
Transmit (output) W/BR BR/W BLK/O O/BLK
Blue binder
Blue binder
TXTIP 4 TXRING 4 Transmit (output) TXTIP 4 TXRING 4

signal from ICAP, W/SL SL/W BLK/G G/BLK signal from ICAP,
TXTIP 5 TXRING 5 signal from ICAP, TXTIP 5 TXRING 5
tip lead R/BL BL/R BLK/BR BR/BLK ring lead
TXTIP 6 TXRING 6 tip lead TXTIP 6 TXRING 6
TXTIP 7 R/O O/R TXRING 7 TXTIP 7 BLK/SL SL/BLK TXRING 7
TXTIP 8 R/G G/R TXRING 8 TXTIP 8 Y/BL BL/Y TXRING 8
9 27 JUMPER CROSS WIRE 9 27 JUMPER
W/BL BL/W R/BR BR/R

RXTIP 1 RXRING 1 RXTIP 1 RXRING 1
W/O O/W R/SL SL/R
W/G G/W Receive (input) BLK/BL BL/BLK
Orange binder
Orange binder
Orange binder
signal towards ICAP,

Orange binder
Receive (input) W/BR BR/W RXTIP 4 BLK/O O/BLK RXRING 4 Receive (input)
RXTIP 4 RXRING 4 tip lead
signal towards ICAP, W/SL SL/W BLK/G G/BLK signal towards ICAP,
tip lead R/BL BL/R BLK/BR BR/BLK ring lead
RXTIP 6 RXRING 6 Receive (input) RXTIP 6 RXRING 6
RXTIP 7 R/O O/R RXRING 7 signal towards ICAP, RXTIP 7 BLK/SL SL/BLK RXRING 7
RXTIP 8 R/G G/R RXRING 8 ring lead RXTIP 8 Y/BL BL/Y RXRING 8
18 36 18 36
....................................................................................................................................................................................................................................
363-211-555 7-179
Pin assignment for 10/100Base-T uplink cabling (for stand-alone mode only)
The following table shows the pin assignment for a 10/100Base-T uplink connection to
the ICAP in stand-alone mode. A straight-through cable connection is used for this
purpose.

IP/Ethernet network

Assumptions
• The ICAPs are inserted in the correct slot(s).
• The external E1/DS1 cables are already installed in the rack.
Follow the applicable procedure

Depending on the configuration, follow one of these procedures:
• “Cabling for a simplex configuration in controlled mode” (p. 7-180)
• “Cabling for a simplex configuration in stand-alone mode” (p. 7-181)
• “Cabling for a duplex configuration in controlled mode” (p. 7-182)
• “Cabling for a duplex configuration in stand-alone mode” (p. 7-182)
Cabling for a simplex configuration in controlled mode

For an ICAP in a simplex configuration in controlled mode, the cabling is constrained
to the E1/DS1 cabling.
...................................................................................................................................................................................................
1 Obtain the required E1/DS1 cable for a simplex configuration (see “Cables” (p. 7-174)
).
...................................................................................................................................................................................................
2 Connect the E1/DS1 cable connector to the lower DS1/E1 connector on the faceplate
of the ICAP. This connector is labeled M DS1/E1.
....................................................................................................................................................................................................................................
7-180 363-211-555
...................................................................................................................................................................................................
3 Tighten the connector with two screws, one at the top and one at the bottom of the
connector.
...................................................................................................................................................................................................
4 Ensure that all DS1/E1 cable shields are grounded at both ends of the connections.
On the ICAP side all cable shields are grounded at the shelf through their cable
connector hoods and no further action is required. The other cable end must be
connected to the DDF according to local grounding conditions or requirements of the
network provider.
IF you want to return to the links for provisioning the ICAP click on back to
E...................................................................................................................................................................................................
ND OF STEPS
Cabling for a simplex configuration in stand-alone mode

For an ICAP in a simplex configuration in stand-alone mode, in addition to the
E1/DS1 cabling, the uplink cabling is required.
...................................................................................................................................................................................................
1 Obtain the required E1/DS1 cable for a simplex configuration (see “Cables” (p. 7-174)
).
...................................................................................................................................................................................................
2 Connect the E1/DS1 cable connector to the lower DS1/E1 connector on the faceplate
of the ICAP. This connector is labeled M DS1/E1.
...................................................................................................................................................................................................
3 Tighten the connector with two screws, one at the top and one at the bottom of the
connector.
...................................................................................................................................................................................................
network provider.
...................................................................................................................................................................................................
5 Connect a 100Base-T cable for the uplink to connector FE1.

E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
363-211-555 7-181
Cabling for a duplex configuration in controlled mode

For an ICAP in a duplex configuration it is important, that the E1/DS1 cabling is done
in the correct order. Do not connect the E1/DS1 cables before the ICAP has been set to
duplex.
...................................................................................................................................................................................................
1 Obtain the required E1/DS1 cable (Y-cable) for a duplex configuration (see “Cables”
(p. 7-174)).
...................................................................................................................................................................................................
2 Connect one E1/DS1 cable connector to the lower DS1/E1 connector on the faceplate
of the ICAP in the preferred slot. This connector is labeled M DS1/E1.
Connect the other leg of the Y-cable to the ICAP in the non-preferred slot in the same
way.
...................................................................................................................................................................................................
3 Tighten each connector with two screws, one at the top and one at the bottom of each
connector.
...................................................................................................................................................................................................
network provider.
E...................................................................................................................................................................................................
ND OF STEPS
Cabling for a duplex configuration in stand-alone mode

For an ICAP in a duplex configuration it is important, that the E1/DS1 cabling is done
in the correct order. Do not connect the E1/DS1 cables before the ICAP has been set to
duplex. ICAPs in duplex mode in a stand-alone configuration require in addition to the
E1/DS1 cabling a cross-connection between the FE2 ports of both ICAPs and the
uplink cabling on both ICAPs.
...................................................................................................................................................................................................
1 Connect a 100Base-T cable for the uplink to connector FE1 on the ICAP in the
preferred slot.
...................................................................................................................................................................................................
2 Repeat the same for the ICAP in the non-preferred slot.
....................................................................................................................................................................................................................................
7-182 363-211-555
...................................................................................................................................................................................................
3 Connect the FE2 ports on both packs with the specified LAN crossover cable.
...................................................................................................................................................................................................
4 Return to the links for provisioning the ICAP click on back to activate service for
ICAP and continue the provisioning until the ICAP is set to duplex.
Then follow the next steps for the E1/DS1 cabling.
...................................................................................................................................................................................................
5 Obtain the required E1/DS1 cable (Y-cable) for a duplex configuration (see “Cables”
(p. 7-174)).
...................................................................................................................................................................................................
6 Connect one E1/DS1 cable connector to the lower DS1/E1 connector on the faceplate
of the ICAP in the preferred slot. This connector is labeled M DS1/E1.
Connect the other leg of the Y-cable to the ICAP in the non-preferred slot in the same
way.
...................................................................................................................................................................................................
connector.
...................................................................................................................................................................................................
network provider.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-183
Procedures used for VDSL service activation
Overview
...................................................................................................................................................................................................................................
Purpose
The following section provides the procedures used for VDSL service activation. Note
Contents
Provision port parameters on a VSIM AP 7-185

Provision/Retrieve VSIM PM profile 7-188
Provision/Retrieve VSIM transmission profile 7-191
Retrieve VSIM transmission status 7-195
Wiring for VDSL APs 7-196
...................................................................................................................................................................................................................................
7-184 363-211-555
Provision port parameters on a VSIM AP

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision the individual port parameters on a VSIM AP including
the service state. Provisioning of a VSIM transmission profile or a VSIM PM profile is
described in separate procedures.
Procedure
...................................................................................................................................................................................................
1 From the menu bar select IP Subsystem ->IP Data -> Equipment -> Port
Provisioning.
...................................................................................................................................................................................................
2 From the option menus select the Slot number and the Port number.
...................................................................................................................................................................................................
3 Change the Service State to In Service.

...................................................................................................................................................................................................
4 Enable or disable Auto-Negotiation and Link Aggregation Ctrl Protocol, as required.

...................................................................................................................................................................................................
5 Select“Predefined transmission profiles” (p. 7-186) or provision a new one by

following “Provision/Retrieve VSIM transmission profile” (p. 7-191).
...................................................................................................................................................................................................
6 Select the “Predefined PM Profile” (p. 7-187) or provision a new one by following
“Provision/Retrieve VSIM PM profile” (p. 7-188).
...................................................................................................................................................................................................
7 Click Apply.
...................................................................................................................................................................................................
8 Repeat Step 2 through Step 6 for all required ports on the pack.
...................................................................................................................................................................................................

NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
...................................................................................................................................................................................................................................
363-211-555 7-185
Detailed procedure descriptions Provision port parameters on a VSIM AP
If you want to return to the links for activating VDSL service click on back to
activate service for VDSL.
Predefined transmission profiles

The parameters for the predefined VDSL transmission profiles are shown in the table
below.
Parameter Predefined transmission profiles

1-DEFVAL 2-PLAN998 3-PLAN998_ADSL
Deployment location Street Cabinet Street Cabinet Street Cabinet
VDSL Standard ANSI ETSI ETSI
VDSL Band Plan ANSI 997 ANSI 998 ANSI 998
ADSL Band Plan Use No ADSL Service No ADSL Service ADSL over POTS
US BW used [25-138] kHz Used upstream Used upstream Used upstream
Latency No Channel Interleaved only Interleaved only
HAM 160 m Disable Disable Disable
Type of Rate Adaptation US Flexible US Flexible US Flexible
DS Flexible DS Flexible DS Flexible
Max Power Level [dBm] US 0 13 13
DS 0 38 38
Power Back Off (upstream) Disable Auto Auto
Max SNR Margin [0.25 dB] US 0 48 48
DS 0 48 48
Min SNR Margin [0.25 dB] US 0 0 0
DS 0 0 0
Target SNR Margin [0.25 US 0 24 24
dB] DS 0 24 24
Slow Channel Max Rate US 0 40000 40000
[kbps] DS 0 70000 70000
Slow Channel Min Rate US 0 0 0
[kbps] DS 0 0 0
Max Interleave Delay US 0 3 3
[0..25] ms DS 0 5 5
....................................................................................................................................................................................................................................
7-186 363-211-555
Detailed procedure descriptions Provision port parameters on a VSIM AP
Predefined PM Profile
The parameters for the predefined VDSL PM profiles are shown in the table below.
Parameters Predefined PM profile

1-DEFVAL
15 Min ES (Sec) 0
15 Min LOF (Sec) 0
15 Min LOL (Sec) 0
15 Min SES (Sec) 0
15 Min UAS (Sec) 0
Send Init Failure Trap Disabled
....................................................................................................................................................................................................................................
363-211-555 7-187
Provision/Retrieve VSIM PM profile

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision a new VDSL performance management profile or to
edit or delete an existent one.
A given VDSL performance management profile can be used by any number of
subscriber lines. This capability avoids the need to provision every VDSL performance
management parameter separately for each subscriber line.
Procedure
...................................................................................................................................................................................................
1 From the menu bar, select IP SubSystem -> IP Data -> Transmission -> VSIM PM
Profile
or
click Configure Profile below PM Thresholds Profile in the VSIM Port Provisioning
window.
Result: The VSIM PM Profile window opens.
...................................................................................................................................................................................................
2 In the Slot field select a desired slot number. (Only slots with provisioned VSIM packs
are visible).
...................................................................................................................................................................................................
3 IF... THEN...
you want to provision a new VSIM PM go to Step 5.
profile
you want to edit a VSIM PM profile in the Profile Name field, select the
applicable profile and click Edit.
Result:
The Modify VSIM PM Profile window
opens. Go to Step 4.
you want to delete a VSIM PM profile in the Profile Name field, select the
applicable profile and click Delete.
Note that predefined profiles and profiles
which are in use (applied to a port) cannot
be deleted.
END OF STEPS.
...................................................................................................................................................................................................
4 Change the values of the VDSL PM parameters as required and click Apply.
...................................................................................................................................................................................................................................
7-188 363-211-555
Detailed procedure descriptions Provision/Retrieve VSIM PM profile
Result: A message confirms the successful modification.

System Fault: If the modified Performance Monitoring profile contains invalid
parameters, the modification request will be denied and an error message appears
on the GSI.
END OF STEPS.
...................................................................................................................................................................................................
5 In the Profile Name field, select an existing VSIM Performance Monitoring profile as
a pattern.
Note that the list of existing profiles always includes the predefined profiles.
...................................................................................................................................................................................................
6 Click New.
Result: The Create New VSIM PM Profile window opens.
...................................................................................................................................................................................................
7 Enter the values of the VDSL PM parameters as given in the work order. If the value
of a particular parameter is already correct, continue with the next parameter.
...................................................................................................................................................................................................
8 Type a profile name in the Profile Name field and click Apply.
Result: The new VDSL PM profile appears in the Profile Name field.
System Fault: If the new PM profile contains invalid parameters, the create request
will be denied and an error message appears on the GSI.
...................................................................................................................................................................................................

NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
VDSL PM parameters
Parameters Default Ranges

15 Min ES (Sec) 0 0-900
15 Min LOF (Sec) 0 0-900
15 Min LOL (Sec) 0 0-900
....................................................................................................................................................................................................................................
363-211-555 7-189
Detailed procedure descriptions Provision/Retrieve VSIM PM profile

15 Min SES (Sec) 0 0-900
15 Min UAS (Sec) 0 0-900
Send Init Failure Trap Disable
....................................................................................................................................................................................................................................
7-190 363-211-555
Provision/Retrieve VSIM transmission profile

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision a new VSIM transmission profile or to edit or delete
an existing one.
A VSIM transmission profile can be used by any number of subscriber lines. This
capability avoids the need to provision every VSIM transmission parameter separately
for each subscriber line.
Procedure
...................................................................................................................................................................................................
1 From the menu bar, select IP SubSystem -> IP Data -> Transmission -> VSIM
Transmission Profile.....
or
click Configure Profile below Transmission Profile in the VSIM Port Provisioning
window.
Result: The VSIM Transmission Profile window opens.
...................................................................................................................................................................................................
2 In the Slot field select a desired slot number. (Only slots with provisioned VSIM packs
are visible).
...................................................................................................................................................................................................
3 IF... THEN...
you want to provision a new VSIM go to Step 5.
transmission profile
you want to edit a VSIM transmission in the Profile Name field, select the
profile applicable profile and click Edit.
Result:
The Modify VSIM Transmission Profile
window opens. Go to Step 4.
you want to delete a VSIM transmission in the Profile Name field, select the
profile applicable profile and click Delete.
Note that predefined profiles and profiles
which are in use (applied to a port) cannot
be deleted.
END OF STEPS.
...................................................................................................................................................................................................
4 Change the values of the VDSL transmission parameters as required and click Apply.
...................................................................................................................................................................................................................................
363-211-555 7-191
Detailed procedure descriptions Provision/Retrieve VSIM transmission profile

System Fault: If the modified transmission profile contains invalid parameters, the
modification request will be denied and an error message appears on the GSI.
END OF STEPS.
...................................................................................................................................................................................................
5 In the Profile Name field, select an existing VSIM transmission profile as a pattern.
...................................................................................................................................................................................................
6 Click New.
Result: The Create New VSIM Transmission Profile window opens.
...................................................................................................................................................................................................
7 Enter the values of the VDSL transmission parameters as given in the work order. If
the value of a particular parameter is already correct, continue with the next parameter.
...................................................................................................................................................................................................
Result: The new VDSL transmission profile appears in the Profile Name field
System Fault: If the new transmission profile contains invalid parameters, the
create request will be denied and an error message appears on the GSI.
...................................................................................................................................................................................................

NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
VDSL transmission parameters
Parameter Options Description

Deployment location Street Cabinet It defines the physical location of the VTU-C
Central Office transceiver. This value is just informational
and has no effect on the transceiver behavior.
Other
....................................................................................................................................................................................................................................
7-192 363-211-555

VDSL Standard ANSI The VDSL standard to be used for the line
ETSI
ITU
Other
VDSL Band Plan Currently only Band Plan 998 is supported
ADSL Band Plan Use No ADSL Service Indicates presence of ADSL service in the
ADSL over POTS associated cable. When ADSL usage is
configured, band-pass filters are applied to
ADSL over ISDN
avoid frequency interference between VDSL
and ADSL services
US BW used [25-138] kHz Currently fixed to “Used upstream”
Latency Currently only interleaved mode is supported
HAM 160 m Enable The notch filters are used to avoid
Disable interference with HAM (Handheld Amateur
Radio) radio bands by introducing power
HAM 80 m Enable control (notching) in one or more of these
Disable bands.
HAM 40 m Enable
Disable
HAM 30 m Enable
Disable
Type of Rate Adaptation Currently fixed to “Flexible” for US and DS.
Max Power Level [dBm] US 0, 13 Maximum transmit power on the VDSL link.
DS 0, 38
Power Back Off Disable
Auto
Manual
Max SNR Margin [0.25 dB] US 0, 48 Min and max SNR margin define the interval
within which the link will stay stable. If the
DS 0, 48
SNR exceeds the max margin, the transmit
Min SNR Margin [0.25 dB] US 0 power should be reduced. If the SNR falls
below the max margin, the date rate should
DS 0 be reduced.
Target SNR Margin [0.25 dB] US 0, 24 Target SNR margin defines the minimum
DS 0, 24 SNR value needed to train the link.
....................................................................................................................................................................................................................................
363-211-555 7-193

Slow Channel Max Rate US 0, 4000 Min and max rate define the interval within
[kbps] which the link should train. If the attainable
DS 0, 7000
bit rate is higher, the SNR should be higher
Slow Channel Min Rate [kbps] US 0 and/or transmit power reduced. If the
attainable bit rate is lower than the min rate,
DS 0 link will be disrupted or will not come up.
Max Interleave Delay [0..25] US 0, 3 Defines the maximum delay caused by using
ms DS 0, 5 interleaved mode.
....................................................................................................................................................................................................................................
7-194 363-211-555
Retrieve VSIM transmission status

...................................................................................................................................................................................................................................
Purpose
Use this procedure to retrieve the VSIM transmission status.
Procedure
...................................................................................................................................................................................................
1 From the menu bar, select IP SubSystem -> IP Data -> Transmission -> VSIM
Transmission Status.....
...................................................................................................................................................................................................
2 In the Slot field select a desired slot number (Only slots with provisioned VSIM cards
are visible).
...................................................................................................................................................................................................
3 In the Port field select the desired port.

Result: If the selected Slot and Port is provisioned the tables below display all
necessary transmission values.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
363-211-555 7-195
Wiring for VDSL APs

...................................................................................................................................................................................................................................
Purpose
This procedure provides information on how to connect the a/b subscriber cables
(tip/ring cables) to the faceplate of the VDSL AP (VSIM).
As the VDSL AP is used in controlled mode only, no other cables than subscriber
cables have to be connected.
Important! Although the CONSOLE connector above the FAULT LED looks like
Cables
The cable assemblies used for VDSL APs are the commonly used a/b cables for most
APs (if nothing else is specified for them):

faceplate
a/b cable connector Subscriber lines Shielded a/b cables (1×32 pairs) ED7C818-30 G1
Connectorized on one end with a
special AP connector; No external
ferrite kits required
Pin assignment
The following figure shows the pin assignment for the a/b connector. Shown is the
wiring / soldering side of the a/b cable connector which is identical to the contact side
of the AP.
...................................................................................................................................................................................................................................
7-196 363-211-555
Detailed procedure descriptions Wiring for VDSL APs
Shown is the wiring/soldering side of the

AP cable connector of the a/b-cable
(identical to the contact side of the AP)
Orange binder Blue binder

68 34
Ring BL/Y BL/Y Ring
R32 67 33 R16
Z port 32* Tip Y/BL Y/BL Tip Z port 16
T32 T16
S/BK S/BK
R31 R15
Z port 31* BK/S BK/S Z port 15
T31 T15
BR/BK BR/BK
R30 R14
Z port 30* BK/BR BK/BR Z port 14
T30 T14
G/BK G/BK
R29 R13
Z port 29* BK/G BK/G Z port 13
T29 T13
O/BK O/BK
R28 R12
Z port 28* BK/O BK/O Z port 12
T28 T12
BL/BK BL/BK
R27 R11
Z port 27* BK/BL BK/BL Z port 11
T27 T11
S/R S/R
R26 R10
Z port 26* R/S R/S Z port 10
T26 T10
BR/R BR/R
R25 R9
Z port 25* R/BR R/BR Z port 9
T25 T9
G/R G/R
R24 R8
Z port 24 R/G R/G Z port 8
T24 T8
O/R O/R
R23 R7
Z port 23 R/O R/O Z port 7
T23 T7
BL/R BL/R
R22 R6
Z port 22 R/BL R/BL Z port 6
T22 T6
S/W S/W
R21 R5
Z port 21 W/S W/S Z port 5
T21 T5
BR/W BR/W
R20 R4
Z port 20 W/BR W/BR Z port 4
T20 T4
G/W G/W
R19 R3
Z port 19 W/G W/G Z port 3
T19 T3
O/W O/W
R18 R2
Z port 18 W/O W/O Z port 2
T18 T2
Ring BL/W BL/W Ring
R17 R1
Z port 17 Tip W/BL W/BL Tip Z port 1
T17 36 2 T1
35 1
The top pair (34 & 68)
and bottom pair (1 & 35)
are each shorted to alert the
Wiring side circuit pack that the connector
is attached.
Assumptions
• The VDSL APs are inserted in the correct slots.
• The a/b cables are installed in the rack.
....................................................................................................................................................................................................................................
363-211-555 7-197
Detailed procedure descriptions Wiring for VDSL APs
Procedure
...................................................................................................................................................................................................
1 Raise the ejector on the front side of the AP until the entire slot is visible and align the
cable connector with the top of the faceplate connector.
...................................................................................................................................................................................................
2 Attach the cable connector to the faceplate connector, then press the cable firmly until
it clicks into place.
possible causes:
• Is the faceplate connector properly fixed?
If the connector is not fixed properly, an alarm tip/ring cable disconnect
will raise.
Try another cable.
• Is the AP or the connector on the faceplate of the AP faulty?
Replace the AP.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-198 363-211-555
Procedures used for activating Ethernet downlinks

on ESIM
Overview
...................................................................................................................................................................................................................................
Purpose
The following section provides the procedures used for ESIM service activation. Note
Contents
Provision port parameters on ESIM 7-200

Wiring for ESIMs used as APs 7-202
...................................................................................................................................................................................................................................
363-211-555 7-199
Provision port parameters on ESIM

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision the individual port parameters on ESIM including the
service state.
Procedure
...................................................................................................................................................................................................
Provisioning.
...................................................................................................................................................................................................
2 From the option menus select the Slot number and the Port number.
Result: The title of the window changes to ESIM Port Provisioning.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
4 Enable or disable Auto-Negotiation as required.

Note that auto-negotiation can be enabled only for the 100Base-T modules.
...................................................................................................................................................................................................
802.3x as required.
...................................................................................................................................................................................................
6 Only if required, enable the Send Link up/down Traps function.

...................................................................................................................................................................................................
7 Click Apply.
...................................................................................................................................................................................................
8 Repeat Step 2 through Step 5 for all required ports on the pack.
...................................................................................................................................................................................................

NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
...................................................................................................................................................................................................................................
7-200 363-211-555
Detailed procedure descriptions Provision port parameters on ESIM
If you want to return to the links for activating Ethernet service click on back to
activate Ethernet service.
....................................................................................................................................................................................................................................
363-211-555 7-201
Wiring for ESIMs used as APs

...................................................................................................................................................................................................................................
Purpose
This procedure applies to the ESIM used as application pack. For cabling the ESIM as
controller (in LAG 200 Shelf), refer to “Wiring for ESIM used as controller ” (p. 7-75)
.
This procedure provides information on how to connect optical fibers (up to eight Fast
Ethernet downlinks to subscribers) to the small form factor pluggable (SFPs) modules
attached to the connectors F1 to F8 on the ESIM faceplate.
SFP modules and cables

For installing fiber cables as Fast Ethernet downlinks to the subscribers, the following
equipment is required:
• One SFP module per Fast Ethernet downlink
Depending on the wavelength, the following SFP modules are available:
– 100Base-FX (LC connector for optical connection)
– 100Base-BX (LC connector for optical connection)
– 100Base-T (RJ45 connector for electrical connection).
• One metal radius clip for each fiber cable
The clip has to be installed to protect the fiber if the shelf doors will be closed.
• The fiber cables are commercially available and depend on the reach.
For the electrical cables to the Fast Ethernet 1 to 8 downlink ports use the following
cables:
• Commercially available 100Base-T cable (also known as CAT 5 cable), wired
“straight-through” as described in the table below
• Length suitable for the distance between the End A and End B.
End A (ESIM) End B (connection point in the IP network)

Assumptions
The ESIMs are inserted in the correct slots according to the work order.
...................................................................................................................................................................................................................................
7-202 363-211-555
Detailed procedure descriptions Wiring for ESIMs used as APs
The cables for the downlinks are installed in the rack or cabinet and fiber cables are
preferably routed through a separate optical cable duct, if possible.
Install fiber cables to the Ethernet downlink and uplink ports

...................................................................................................................................................................................................
1 CAUTION
Laser hazard
Lightwave digital transmission systems and associated optical test sets operate with
invisible laser radiation. Laser radiation can cause damage to the skin and
considerable injuries to the eyes. This applies particularly to the connections of the
optical packs. Although, at present, the transmitting power levels for Class 1 lasers
are below those known to cause injury to the eye at distances greater than 250 mm
(≈ 10 inches) direct exposure should always be avoided.
Don’t look into the end of an exposed fiber or optical connector of a pack as long as
the optical source is switched on. Never view any unterminated optical connector with
optical microscope or magnifying glasses as long as the laser source is switched on.
Always test with an optical power meter or infrared detectors that the fiber is
de-energized and ensure that the laser source can not be activated during inspection
with the microscope.
...................................................................................................................................................................................................
2 Insert the correct SFP modules (see labeling on the SFP module) in the appropriate
Fast Ethernet ports (1 to 8) on the ESIM faceplate.
Note that the cables have to be inserted from the bottom up – the downlink port 8 first,
then 7, 6, { 1.
...................................................................................................................................................................................................
3 Obtain one radius clip per fiber to connect to a Fast Ethernet downlink port (1 to 8).
The following figure shows metal radius clip
....................................................................................................................................................................................................................................
363-211-555 7-203
...................................................................................................................................................................................................
4 Slip the metal radius clip carefully under the rubber boot of the customer provided
fiber.
The following figure shows metal radius clip and fiber
The following figure shows mounted radius clip on fiber
...................................................................................................................................................................................................
5 Insert the fiber into the clamp on the other end of the radius clip so that the fiber is
attached closely to the clip.
...................................................................................................................................................................................................
6 Remove the dust plug of the SFP and connect the fiber to the SFP module.
...................................................................................................................................................................................................
7 If applicable, repeat this procedure for all FE ports on the ESIM, if applicable.
E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
7-204 363-211-555
Install electrical cables to the uplink and downlink ports

...................................................................................................................................................................................................
1 If required, connect the customer provided 100Base-T cables to the appropriate Fast
Ethernet downlink ports on the ESIM faceplate.
Note that the cables have to be inserted from the bottom up – the downlink port 8 first,
then 7, 6, { 1.
...................................................................................................................................................................................................
2 Route the cable through the left cable duct of the rack to the top.
...................................................................................................................................................................................................
3 If applicable, repeat this sub-procedure for each port 2 to 8.

If you want to return to the links for provisioning the ESIM click on back to
activate Ethernet service.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-205
Procedures used for ADSL2 service activation
Overview
...................................................................................................................................................................................................................................
Purpose
The following section provides the procedures used for ADSL2 service activation. Note
Contents
Provision/Edit/Delete DMT Profile 7-207

Provision port parameters on an IPADSL2 AP 7-211
Provision/Retrieve bridge port PM profile 7-214
Provision/Retrieve bridge port traffic profile 7-217
Provision/Retrieve IPADSL transmission profile 7-220
Provision/Retrieve IPADSL PM profile 7-225
Provision/Retrieve IPADSL bridge port profile 7-228
Wiring for IPADSL2_32p APs 7-232
...................................................................................................................................................................................................................................
7-206 363-211-555
Provision/Edit/Delete DMT Profile

...................................................................................................................................................................................................................................
Purpose
Use this GSI operation to provision a new DMT profile, to edit or to delete an existing
DMT profile. DMT profiles apply to ADSL2/ADSL2+ only.
Background
ADSL2/ADSL2+ provides the opportunity to define the range of upstream bins and
downstream bins in a flexible way via a new DMT bin profile. Furthermore the user
can enable or disable dedicated bins with the GSI.
NOTE: currently only the non-overlapped mode is supported, i.e. the upstream range is
restricted to 6-31 and the downstream range is restricted to 32-511.
Procedure
...................................................................................................................................................................................................
1 From the menu bar, select IP Subsystem -> IP Data -> Profiles -> DMT...
Result: The DTM Profile window opens.
...................................................................................................................................................................................................
2 IF... THEN...
you want to provision new DTM profile go to Step 3.
you want to edit DTM profile go to Step 9.
you want to delete DTM profile go to Step 15.
...................................................................................................................................................................................................
3 Click New.
Result: The Create new DTM Profile window opens.
...................................................................................................................................................................................................
4 In the Profile Name field enter a name for the new profile.
...................................................................................................................................................................................................
5 Select the following ADSL2/ADSL2+ DTM parameters as given in the work order. For
the allowed values refer to “DTM parameters” (p. 7-210).
Parameters:
• DTM Start Bin upstream and downstream
• DTM End Bin upstream and downstream
...................................................................................................................................................................................................................................
363-211-555 7-207
Detailed procedure descriptions Provision/Edit/Delete DMT Profile
...................................................................................................................................................................................................
6 For fine tuning you can additionally enable or disable dedicated bins in upstream and
downstream direction. For enable or disable dedicated bins in upstream or downstream
direction select the desired bins and click the Enable or Disable button.
...................................................................................................................................................................................................
7 Click Apply.
Result: The new DTM profile name appears in the DTM Profile Name field (e.g.
2 - test)
System Fault: If the new transmission profile contains invalid parameters, the
...................................................................................................................................................................................................
8
IF... THEN...
you want to build another new DTM go to Step 3
profile
you do not want to build another new go to Step 20
DTM profile
...................................................................................................................................................................................................
9 From the Profile Name pull-down menu select the DMT profile which you want to
edit.
...................................................................................................................................................................................................
10 Click Edit.
Result: The Edit DTM Profile window opens.
...................................................................................................................................................................................................
11 For fine tuning you can additionally enable or disable dedicated bins in upstream and
downstream direction. Select the dedicated bins in upstream or downstream direction as
required and click the Enable or Disable button.
...................................................................................................................................................................................................
12 Select the following ADSL2/ADSL2+ DTM parameters as given in the work order. For
allowed values refer to “DTM parameters” (p. 7-210).
Parameters:
• DTM Start Bin upstream and downstream
• DTM End Bin upstream and downstream
...................................................................................................................................................................................................
13 Click Apply.
....................................................................................................................................................................................................................................
7-208 363-211-555
System Fault: If the new profile contains invalid parameters, the create request
...................................................................................................................................................................................................
14
IF... THEN...
you want to edit another DTM profile go to Step 10
you do not want to edit another DTM go to Step 20
profile
...................................................................................................................................................................................................
15 In the Profile Name field, click on the down arrow to see the DMT profile types that
are available. Select from the Profile Name pull-down menu the profile which you
want to delete.
...................................................................................................................................................................................................
16 Click Delete.
Result: The Delete DMT Profile window opens for confirmation.
...................................................................................................................................................................................................
17 IF... THEN...
you want to delete the selected click Yes.
DMT profile Result: The DMT profile is deleted. Go to Step 18.
you do not want to delete the click No.
selected DMT profile Result: The window displays the same profile as
before. Go to Step 19.
...................................................................................................................................................................................................
18 In the Profile Name field, click on the down arrow to verify that the deleted profile
does no longer appear in the list.
...................................................................................................................................................................................................
19 IF... THEN...
you want to delete another DMT go to Step 15
profile
you do not want to delete another go to Step 20
DMT profile
....................................................................................................................................................................................................................................
363-211-555 7-209
...................................................................................................................................................................................................
20 Click Cancel to close the DMT Profile window.

E...................................................................................................................................................................................................
ND OF STEPS
DTM parameters
The table below shows the parameter range for DTM profiles.
Parameter Allowed and default values

Upstream Default Downstream Default
DMT Start Bin 0 - 63 6 32 - 511 32
DMT End Bin 0 - 63 31 32 - 511 255
DMT Configured Bins 0 - 63 all bin 32 - 511 all bin
enabled enabled
Note that the upstream range is restricted to 6-31 and the downstream range is
restricted to 32-511 as only non-overlapped operation mode is supported. The allowed
value for ADSL2 is 32-511, the supported value for ADSL2 is 32-255.
....................................................................................................................................................................................................................................
7-210 363-211-555
Provision port parameters on an IPADSL2 AP

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision the individual port parameters on an IPADSL2 AP
including the service state. Provisioning of the applicable profiles is described in
separate procedures.
Procedure
...................................................................................................................................................................................................
Provisioning.
Result: The IPAFM Port Provisioning window opens.
...................................................................................................................................................................................................
2 From the option menus select the Slot number with an IPADSL and the Port number
to be provisioned.
Result: The GSI switch to the IPADSL Port Provisioning window.
...................................................................................................................................................................................................
3 IF... THEN...
you want to provision the ports parameters go to Step 4.
you want to provision the bridge ports go to Step 13.
parameters
...................................................................................................................................................................................................

...................................................................................................................................................................................................
5 From the Line Coding pull-down menu select whether DMT or other code will be
used.
...................................................................................................................................................................................................
6 The Start-up Mode depends on the CPE used. From the pull-down menu select the
appropriate type.
...................................................................................................................................................................................................
7 Enable or disable the Send Link up/down Traps.

...................................................................................................................................................................................................
8 Select a predefined IPADSL transmission profile or provision a new one by following

“Provision/Retrieve IPADSL transmission profile” (p. 7-220).
...................................................................................................................................................................................................................................
363-211-555 7-211
Detailed procedure descriptions Provision port parameters on an IPADSL2 AP
...................................................................................................................................................................................................
9 Select a predefined ADSL performance management profile or provision a new one by

following “Provision/Retrieve IPADSL PM profile” (p. 7-225).
...................................................................................................................................................................................................
10 Select a predefined DMT profile or provision a new one by following

“Provision/Edit/Delete DMT Profile ” (p. 7-207).
...................................................................................................................................................................................................
11 Click Apply.
...................................................................................................................................................................................................
12 Repeat these steps for all required ports on the pack. To provision the uplink ports
GbE1 or GbE2 see “IPADSL Port provisioning parameters (uplink ports)” (p. 7-212).
...................................................................................................................................................................................................
13 Select the Bridge Port subtab to retrieve the provisioned bridge port parameters or
provision a new one by following “IPADSL Bridge port provisioning parameters”
(p. 7-213).
...................................................................................................................................................................................................

NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
If you want to return to the links for activating IPADSL service click on back to
activate service for IPADSL.
IPADSL Port provisioning parameters (uplink ports)
Parameter Possible values Default Comment
Service State In Service In Service Indicates the Port Operational State.

Out of service
Operational State In Service Out of service Indicates the Port Operational State, that provides
Out of service info about the port ability to provide service
depending on hardware state, etc. (read-only).
Auto-Negotiation Enabled Enabled This object identifies the port’s auto-negotiation
Disabled capability.
Restart Auto-Negot. restart Disabled This parameter forces the restart of the
Disable auto-negotiation capability for the port.
Flow Control Enabled Enabled This entry controls whether the port will generate
Disabled 802.3x Pause frames.
....................................................................................................................................................................................................................................
7-212 363-211-555
Detailed procedure descriptions Provision port parameters on an IPADSL2 AP
Pause Announcement Symmetric Both This entry determines the 802.3x flow control
Asymmetric capability announcement mode during
auto-negotiation.
Both
Transmission Mode Simplex Duplex Sets the simplex/duplex mode for the port. This
Duplex setting is ignored if auto-negotiation is enabled.
Not applicable for stand-alone mode .
Transmission Rate [Mbps] 1000 1000 This entry defines the port interface speed.
100 Fastethernet is a 100 Mbit interface speed and
gigabitethernet is a 1000 Mbit interface speed.
IPADSL Bridge port provisioning parameters
VPI (0...10) 0...10 A type for ADSL2+ AP Bridge Port Virtual Path
Indexes.
VCI (0...127) 0...127 A type for ADSL2+ AP Bridge Port Virtual Circuit
Indexes.
VLAN ID 1..4092 1 A type for ADSL2+ AP VLAN IDs. Vlans 4093

and 4094 are used internally for communication.
VLANs 4095 and 4092 are reserved
VLAN Name Default VLAN

Port Profile
Traffic Profile
PM Statistic Profile
Static MAC Limit 1...20 1 This is the number of static Vlan/MAC addresses
which may be provisioned on this bridge port
....................................................................................................................................................................................................................................
363-211-555 7-213
Provision/Retrieve bridge port PM profile

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision a new bridge port PM profile or to edit or delete an
existing one.
A bridge port PM profile can be used by any number of subscriber lines. This
capability avoids the need to provision every bridge port PM parameter separately for
each subscriber line.
Procedure
...................................................................................................................................................................................................
1 From the menu bar, select IP SubSystem -> IP Data -> Profiles -> Bridge Port PM...
Result: The Bridge Port PM Profiles window opens.
...................................................................................................................................................................................................
2 In the Slot field select a desired slot number. (Only slots with provisioned IPADSL
packs are visible).
...................................................................................................................................................................................................
3 IF... THEN...
you want to provision a new bridge port go to Step 5.
PM profile
you want to edit a bridge port PM profile in the Profile Name field, select the
Result:
The Modify Bridge Port PM Profile
you want to delete a bridge port PM in the Profile Name field, select the
Note that predefined profiles cannot be
deleted.
END OF STEPS.
...................................................................................................................................................................................................
4 Change the values of the bridge port PM parameters as required and click Apply.
System Fault: If the modified bridge port PM profile contains invalid parameters,
the modification request will be denied and an error message appears on the GSI.
END OF STEPS.
...................................................................................................................................................................................................................................
7-214 363-211-555
Detailed procedure descriptions Provision/Retrieve bridge port PM profile
...................................................................................................................................................................................................
5 In the Profile Name field, select an existing bridge port PM profile as a pattern.
...................................................................................................................................................................................................
6 Click New.
Result: The Create New Bridge Port PM Profile window opens.
...................................................................................................................................................................................................
7 Enter the values of the bridge port PM parameters as given in the work order. If the
value of a particular parameter is already correct, continue with the next parameter.
...................................................................................................................................................................................................
Result: The new bridge port PM profile appears in the Profile Name field
System Fault: If the new bridge port PM profile contains invalid parameters, the
...................................................................................................................................................................................................

NVDS.
activate service for IPADSL2.
E...................................................................................................................................................................................................
ND OF STEPS
Bridge port PM parameters

The parameters for the IPADSL Bridge Port PM profiles and the predefined values are
shown in the table below.
Parameter Possible values 1-IPADSL Bridge Port Comment

Status Default Profile
15 Min Packets Dropped 0..4294967295 0 This is alarm
threshold for
packets dropped by
this bridge port in a
15 minute interval.
....................................................................................................................................................................................................................................
363-211-555 7-215
Detailed procedure descriptions Provision/Retrieve bridge port PM profile
Parameter Possible values 1-IPADSL Bridge Port Comment

Status Default Profile
24 Hours Packets Dropped 0..4294967295 0 This is alarm
threshold for
packets dropped by
this bridge port in a
24 hour interval.
....................................................................................................................................................................................................................................
7-216 363-211-555
Provision/Retrieve bridge port traffic profile

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision a new bridge port traffic profile or to edit or delete an
existing one.
A bridge port traffic profile can be used by any number of subscriber lines. This
capability avoids the need to provision every bridge port traffic parameter separately
for each subscriber line.
Procedure
...................................................................................................................................................................................................
1 From the menu bar, select IP SubSystem -> IP Data -> Profiles -> Bridge Port
Traffic...
Result: The Bridge Port Traffic Profile window opens.
...................................................................................................................................................................................................
2 In the Slot field select a desired slot number. (Only slots with provisioned IPADSL2
packs are visible).
...................................................................................................................................................................................................
3 IF... THEN...
you want to provision a new bridge port go to Step 5.
traffic profile
you want to edit a bridge port traffic in the Profile Name field, select the
profile applicable profile and click Edit.
Result:
The Modify Bridge Port Traffic Profile
you want to delete a bridge port traffic in the Profile Name field, select the
deleted.
END OF STEPS.
...................................................................................................................................................................................................
4 Change the values of the bridge port traffic profile parameters as required and click
Apply.
...................................................................................................................................................................................................................................
363-211-555 7-217
Detailed procedure descriptions Provision/Retrieve bridge port traffic profile

System Fault: If the modified bridge port traffic profile contains invalid
on the GSI.
END OF STEPS.
...................................................................................................................................................................................................
5 In the Profile Name field, select an existing bridge port profile as a pattern.
...................................................................................................................................................................................................
6 Click New.
Result: The Create New Bridge Port Traffic Profile window opens.
...................................................................................................................................................................................................
7 Enter the values of the bridge port traffic parameters as given in the work order. If the
...................................................................................................................................................................................................
Result: The new bridge port traffic profile appears in the Profile Name field
System Fault: If the new bridge port traffic profile contains invalid parameters, the
...................................................................................................................................................................................................

NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
Bridge port traffic profile parameters

The parameters for the IPADSL Bridge Port Traffic profiles and the predefined values
are shown in the table below.
....................................................................................................................................................................................................................................
7-218 363-211-555
Detailed procedure descriptions Provision/Retrieve bridge port traffic profile
Parameter Possible values 1-IPADSL Comment

Bridge Port
Traffic
Default
Profile
ATM Service ubr, cbr, rt-vbr, ubr specifies the ATM service category for
Category nrt-vbr the profile.
....................................................................................................................................................................................................................................
363-211-555 7-219
Provision/Retrieve IPADSL transmission profile

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision a new IPADSL transmission profile or to edit or delete
an existing one.
An IPADSL transmission profile can be used by any number of subscriber lines. This
capability avoids the need to provision every IPADSL transmission parameter
separately for each subscriber line.
Procedure
...................................................................................................................................................................................................
1 From the menu bar, select IP SubSystem -> IP Data ->Profiles -> Transmission...
Result: The Transmission Profile window opens.
...................................................................................................................................................................................................
2 In the Slot field select a desired slot number with the IPADSL pack.
Result: The GSI switch to the IPADSL Transmission Profile window.
...................................................................................................................................................................................................
3 IF... THEN...
you want to provision a new IPADSL go to Step 5.
transmission profile
you want to edit an IPADSL transmission in the Profile Name field, select the
profile applicable profile and click Edit. Note that
predefined profiles cannot be edited.
Result:
The Modify IPADSL transmission profile
you want to delete an IPADSL in the Profile Name field, select the
transmission profile applicable profile and click Delete.
deleted.
END OF STEPS.
...................................................................................................................................................................................................
4 Change the values of the IPADSL transmission parameters as required and click Apply.
System Fault: If the modified profile contains invalid parameters, the modification
request will be denied and an error message appears on the GSI.
END OF STEPS.
...................................................................................................................................................................................................................................
7-220 363-211-555
Detailed procedure descriptions Provision/Retrieve IPADSL transmission profile
...................................................................................................................................................................................................
5 In the Profile Name field, select an existing IPADSL transmission profile as a pattern.
...................................................................................................................................................................................................
6 Click New.
Result: The Create New transmission profile window opens.
...................................................................................................................................................................................................
7 Enter the values of the transmission parameters as given in the work order. If the value
of a particular parameter is already correct, continue with the next parameter.
...................................................................................................................................................................................................
Result: The new IPADSL transmission profile appears in the Profile Name field
...................................................................................................................................................................................................

NVDS.
activate service for IPADSL.
E...................................................................................................................................................................................................
ND OF STEPS
Predefined IPADSL Transmission profile

The parameters for the IPADSL Line configuration profiles and the predefined values
are shown in the table below.
Parameter Possible values ADSL Default Comment

Configuration
Profile
US DS
Line Type No Channel Interleave This field defines the type
Fast of ADSL physical line by
specifying whether and
Interleave
how the line is
Fast or Interleave channelized
Fast and
Interleave
....................................................................................................................................................................................................................................
363-211-555 7-221

Configuration
Profile
US DS
Rate Adaptation Fixed Runtime Runtime Indicates what type of rate
Startup adaptation is configured on
this ATU-C.
Runtime
Fast channel Usage [%] 0...100 Configured allocation ratio
of excess transmit
bandwidth between fast
and interleaved channels.
(Fast + Interleaved = 100)
Min SNR Margin [0.1dB] 0...31 Configured Minimum
acceptable Signal/Noise
Margin. If the noise
margin falls below this
level, the modem should
attempt to increase its
power output. If that is not
possible the modem will
attempt to re-initialize or
shut down.
Max SNR Margin [0.1dB] 0...31 Configured Maximum
acceptable Signal/Noise
Margin. If the Noise
Margin is above this the
modem should attempt to
reduce its power output to
optimize its operation.
Target SNR Margin 0.1dB] 0...31 6 6 Indicates the Target
Signal/Noise Margin. This
is the Noise Margin the
modem must achieve with
a BER of 10-7 or better to
successfully complete
initialization.
Decrease Transmit Bandwidth
SNR Margin Threshold [0.1dB]
Thres. Crossing min Time [sec]
Increase Transmit Bandwidth
SNR Margin Threshold [0.1dB]
Thres. Crossing min Time [sec]
Fast Ch. Min Rate [kbit/s]
....................................................................................................................................................................................................................................
7-222 363-211-555

Configuration
Profile
US DS
Fast Ch. Max Rate [kbit/s]
Interl. Ch. Min Rate [kbit/s]
Interl. Ch. Max Rate [kbit/s]
Max. Interleave delay 1 Defines the Maximum
Interleave Delay for the
port.
PSD [dBm/Hz]
PSD Mask Mask 1 n.a. Mask
Mask 2 1
Reach ADSL2 Mode Disable Disable n.a. The value of this object is
NB Spectrum used to enable/disable
Reach ADSL2. Reach
WB Spectrum
ADSL2 is supported in
non-overlapped mode with
submode
- wide band spectrum (bins
6-24) in upstream direction
- narrowband spectrum
(bins 6-14) in upstream
direction.
Auto Power Management Enable n.a. Disable The value of this object is
Disable used to enable/disable
automatic power
management of this line. If
disabled, the low power
state L2 is not used.
Min L0 State [sec] 0..255 30 The value of this object is
used to set the minimum
time between an exit from
L2 (into L0 state) and the
next entry into the L2
state.
Min L2 State [sec] 0..255 30 The value of this object is
used to set the minimum
time between an entry into
the L2 state and the first
power trim in the L2 state
and between 2 consecutive
power trims in the L2
state.
....................................................................................................................................................................................................................................
363-211-555 7-223

Configuration
Profile
US DS
Max L2 Power Reduction 0..32 The value of this object is
[0.1dB] used to set the maximum
aggregate can be
performed through a single
power trim in the L2 state.
L2 Entery Criteria 50..100 This value specifies the
criteria for entering the L2
Power Management state.
The entry condition is
expressed as a percentage
of transmitted user cells to
total transmitted cells
(downstream). (user
cells/(user cells + Idle
Cells) * 100)
Min Impulse 0, 0.5, 1, 2 0 0 This value specifies the
downstream/upstream
Minimum Impulse Noise
Protection threshold. This
values specifies the
duration of an impulse
noise event that can be
tolerated introducing
minimal downstream or
upstream errors.
....................................................................................................................................................................................................................................
7-224 363-211-555
Provision/Retrieve IPADSL PM profile

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision a new IPADSL performance management profile or to
edit or delete an existent one.
A given IPADSL performance management profile can be used by any number of
subscriber lines. This capability avoids the need to provision every IPADSL
performance management parameter separately for each subscriber line.
Procedure
...................................................................................................................................................................................................
1 From the menu bar, select IP SubSystem -> IP Data -> Profiles -> PM...
Result: The PM Profile window opens.
...................................................................................................................................................................................................
2 In the Slot field select a desired slot number with an IPADSL pack.
Result: The GSI switch to the IPADSL subtab with the PM profile.
...................................................................................................................................................................................................
3 IF... THEN...
you want to provision a new IPADSL PM go to Step 5.
profile
you want to edit an IPADSL PM profile in the Profile Name field, select the
Result:
The Modify PM Profile window opens. Go
to Step 4.
you want to delete an IPADSL PM profile in the Profile Name field, select the
applicable profile and click Delete.
deleted.
END OF STEPS.
...................................................................................................................................................................................................
4 Change the values of the IPADSL PM parameters as required and click Apply.
System Fault: If the modified Performance Monitoring profile contains invalid
on the GSI.
END OF STEPS.
...................................................................................................................................................................................................................................
363-211-555 7-225
Detailed procedure descriptions Provision/Retrieve IPADSL PM profile
...................................................................................................................................................................................................
5 In the Profile Name field, select an existing IPADSL Performance Monitoring profile
as a pattern.
...................................................................................................................................................................................................
6 Click New.
Result: The Create new PM Profile window opens.
...................................................................................................................................................................................................
7 Enter the values of the “IPADSL PM parameters” (p. 7-226) as given in the work
order. If the value of a particular parameter is already correct, continue with the next
parameter.
...................................................................................................................................................................................................
Result: The new IPADSL PM profile appears in the Profile Name field.
System Fault: If the new PM profile contains invalid parameters, the create request
...................................................................................................................................................................................................

NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
IPADSL PM parameters

15 Min ES (Sec) 20 0-900
15 Min LOF (Sec) 20 0-900
15 Min LOL (Sec) 20 0-900
15 Min SES (Sec) 20 0-900
15 Min UAS (Sec) 20 0-900
15 Min LOS (Sec) 20 0-900
15 Min LPRS (Sec) 20 0-900
....................................................................................................................................................................................................................................
7-226 363-211-555
Detailed procedure descriptions Provision/Retrieve IPADSL PM profile

Send Init Failure Trap 20 0-900
....................................................................................................................................................................................................................................
363-211-555 7-227
Provision/Retrieve IPADSL bridge port profile

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision a new IPADSL bridge port profile or to edit or delete
an existing one.
An IPADSL bridge port profile can be used by any number of subscriber lines. This
capability avoids the need to provision every IPADSL bridge port profile parameter
separately for each subscriber line.
Background
IPADSL bridge ports represent the subscriber’s ingress/egress points of the layer
2-interworking system implemented on the IPADSL2 pack.
Procedure
...................................................................................................................................................................................................
1 From the menu bar, select IP SubSystem -> IP Data -> Profiles -> Bridge Port...
Result: The Bridge Port Profile window opens.
...................................................................................................................................................................................................
2 In the Slot field, select a desired slot number. (Only slots with provisioned IPADSL
packs are visible).
...................................................................................................................................................................................................
3 IF... THEN...
you want to provision a new go to Step 5.
IPADSL bridge port profile
you want to edit an IPADSL bridge in the Profile Name field, select the applicable
port profile profile and click Edit.
Result:
The Modify IPADSL bridge port Profile window
opens. Go to Step 4.
you want to delete an IPADSL in the Profile Name field, select the applicable
bridge port profile profile and click Delete.
Note that predefined profiles cannot be deleted.
END OF STEPS.
...................................................................................................................................................................................................
4 Change the values of the IPADSL bridge port parameters as required and click Apply.
...................................................................................................................................................................................................................................
7-228 363-211-555
Detailed procedure descriptions Provision/Retrieve IPADSL bridge port profile

System Fault: If the modified profile contains invalid parameters, the modification
request will be denied and an error message appears on the GSI.
END OF STEPS.
...................................................................................................................................................................................................
5 In the Profile Name field, select an existing IPADSL bridge port profile as a pattern.
...................................................................................................................................................................................................
6 Click New.
Result: The Create New IPADSL bridge port Profile window opens.
...................................................................................................................................................................................................
7 Enter the values of the IPADSL bridge port profile as given in the work order. If the
...................................................................................................................................................................................................
Result: The new IPADSL bridge port profile appears in the Profile Name field
...................................................................................................................................................................................................

NVDS.
activate service for IPADSL2. .
E...................................................................................................................................................................................................
ND OF STEPS
IPADSL bridge port profile parameters

The parameters for the IPADSL Bridge Port profiles and the predefined values are
shown in the table below.
....................................................................................................................................................................................................................................
363-211-555 7-229
Parameter Possible values 1-ATM Bridge Comment

Port Default
Profile
1
Frame Tagged Both This specifies the type of ingress
Acceptance Both frames which will be accepted by the
Mode: bridge port. Acceptable frames may
be 802.1q tagged or both, where both
indicates both tagged and untagged
frames are acceptable. Untagged is
not used at present.
802.1 Priority: 0-7 0 Used for forming the 802.1 tag
together with the port’s VLAN id.
This tag is used for marking the
ingressing frame with the layer 2
information associated to this port
1
Layer 2 Insert Transparent In the upstream direction the tag
inter-working formed by the VLAN id and priority
behavior fields will be inserted into the frame
to be processed by the ATM bridge
port .In the downstream direction the
802.1 tag of the frame will be
removed before being forwarded
through the ATM bridge port. This
option can be specified independently
of the Acceptable Frame field.
VLAN stacking is achieved by
specifying this option and allowing
tagged frames to ingress the
interworking system via the ATM
bridge port.
2
Replace The tag formed by the VLAN
id/priority fields will replace the
802.1 tag of the ingressing frame.
This option can be specified only
when the Acceptable Frames field
specifies tagged frames only.
Transparent No tag modification is done in the
frame.
This option can be specified
independently of the Acceptable
Frames field.
Dynamic MAC 1-35 35 This parameter specifies the
Limit maximum number of devices that can
be attached to a provisioned ATM
Bridge Port.
....................................................................................................................................................................................................................................
7-230 363-211-555
Parameter Possible values 1-ATM Bridge Comment

Port Default
Profile
DHCP filtering Disable Enable If enabled, no
Enable DHCP/NetBEUI/NetBIOS/NBT
responses frames originating at the
NetBEUI Disable Enable subscriber side will be processed by
filtering Enable the Layer 2-inter-working system.
NetBIOS filtering Disable Enable Each of these filters can be
Enable enabled/disabled independently from
the others.
NBT filtering Disable Enable
Enable
Notes:
1. Only VLAN 1 (the default) will be allowed to carry the combination of Both and Transparent tagging.
When creating a new profile if this combination is selected with another VLAN an error will be returned
to the GSI when the LPA633 is in standalone mode.
2. Not yet supported at the issue date of this document
....................................................................................................................................................................................................................................
363-211-555 7-231
Wiring for IPADSL2_32p APs

...................................................................................................................................................................................................................................
Purpose
This procedure provides information on how to wire the IPADSL2_32p APs, that is
wiring information for the pack when it operates in controlled mode and for
stand-alone mode.
This procedure describes:
• How to connect the ADSL2+ subscriber cable to the faceplate of the IPADSL2_32p
AP
• The cabling for the uplink to the IP network. An uplink is required for stand-alone
mode only.
The OAM&P connection to the LAN port LAN1 of the AP and the serial connection to
the CONSOLE port for initial system turn-up also apply to stand-alone mode only. The
LAN connection is done via a commercially available standard 100Base-T cable as
described in “OAM&P Connectivity” (p. 2-13). It is not subject of this procedure.
Important! Although the CONSOLE connector below the FAULT LED looks like
Cables
The following cables are required to connect an IPADSL2_32p AP:
Connector on faceplate Interface for Cable description Cable
POTS-ADSL Subscriber lines Shielded special cable ED7C873-31 G9x

with two connectors on
POTS the AP side
Additional cabling for stand-alone mode
LAN1 10/100Base-T Straight through or Commercially available

management port (for crossover cable - 100Base-T cable
stand-alone mode only) depending on the
connected equipment,
RJ-45 connectors
LAN2 100/1000Base-T uplink Wired straight-through, Commercially available

(for stand-alone mode RJ-45 connectors 100Base-T cable or
only) 1000Base-T cable
LAN3 for future use
CONSOLE RS232 port with USB-A Adapter cable with ED7C873-31 G8

physical connector for USB-A connector
initial system turn-up in (DB9-to-USB RS232)
stand-alone mode
...................................................................................................................................................................................................................................
7-232 363-211-555
Detailed procedure descriptions Wiring for IPADSL2_32p APs
Pin assignment of subscriber interface

The POTS connector and the POTS-ADSL connector on the IPADSL2_32p AP support
32 subscriber ports and are used for ADSL2/2+ and POTS services. The following
figure shows the pin assignment for the POTS splitter connector and the POTS-ADSL
connector of the IPADSL2_32p AP. Shown is the frontview of the connectors on the
faceplate of the pack.
POTS connector/
POTS-ADSL connector
GRD GRD
Ring31 Tip31 Ring32 Tip32

Color coding on ADSL2+ cables

The following table shows the color coding on the ADSL2+ cables.
....................................................................................................................................................................................................................................
363-211-555 7-233
Cable Connector Binder Color in Binder Color in

Color Code
Pin-outs POTS Cable POTS-ADSL Cable
Tip1 (B1) BLU 1WHT
Ring1 (A1) BLU 2WHT
Tip2 (D1) ORG 1WHT
Ring2 (C1) ORG 2WHT
Tip3 (B2) GRN 1WHT
Ring3 (A2) GRN 2WHT
Tip4 (D2) BRN 1WHT
Ring4 (C2) BRN 2WHT
Tip5 (B3) SLT 1WHT
Ring5 (A3) SLT 2WHT
Tip6 (D3) BLU 1RED
Ring6 (C3) BLU 2RED
Tip7 (B4 ORG 1RED
Ring7 (A4) ORG 2RED
Tip8 (D4) GRN 1RED
Ring8 (C4) GRN 2RED
BLU GRN
Tip9 (B5) BRN 1RED
Ring9 (A5) BRN 2RED
Tip10 (D5) SLT 1RED
Ring10 (C5) SLT 2RED
Tip11 (B6) BLU 1BLK
Ring11 (A6) BLU 2BLK
Tip12 (D6) ORG 1BLK
Ring12 (C6) ORG 2BLK
Tip13 (B7) GRN 1BLK
Ring13 (A7) GRN 2BLK
Tip14 (D7) BRN 1BLK
Ring14 (C7) BRN 2BLK
Tip15 (B8) SLT 1BLK
Ring15 (A8) SLT 2BLK
Tip16 (D8) BLU 1YEL
Ring16 (C8) BLU 2YEL
Tip17 (B9) BLU 1WHT
Ring17 (A9) BLU 2WHT
Tip18 (D9) ORG 1WHT
Ring18 (C9) ORG 2WHT
Tip19 (B10) GRN 1WHT
Ring19 (A10) GRN 2WHT
Tip20 (D10) BRN 1WHT
Ring20 C10) BRN 2WHT
Tip21 (B11) SLT 1WHT
Ring21 (A11) SLT 2WHT
Tip22 (D11) BLU 1RED
Ring22 (C11) BLU 2RED
Tip23 (B12) ORG 1RED
Ring23 (A12) ORG 2RED
Tip24 (D12) GRN 1RED
Ring24 (C12) GRN 2RED
ORG BRN
Tip25 (B13) BRN 1RED
Ring25 (A13) BRN 2RED
Tip26 (D13) SLT 1RED
Ring26 (C13) SLT 2RED
Tip27 (B14) BLU 1BLK
Ring27 (A14) BLU 2BLK
Tip28 (D14) ORG 1BLK
Ring28 (C14) ORG 2BLK
Tip29 (B15) GRN 1BLK
Ring29 (A15) GRN 2BLK
Tip30 (D15) BRN 1BLK
Ring30 (C15) BRN 2BLK
Tip31 (B16) SLT 1BLK
Ring31 (A16) SLT 2BLK
Tip32 (D16) BLU 1YEL
Ring32 (C16) BLU 2YEL
BLU = Blue WHT = White ORG = Orange GRN = Green BRN = Brown SLT = Slate BLK = Black YEL = Yellow
1 and 2 stand for the number of colored dots on each wire.
....................................................................................................................................................................................................................................
7-234 363-211-555
Pin assignment for 100Base-T uplink cabling (for stand-alone mode only)
The following table shows the pin assignment for an 100Base-T uplink connection. A
straight-through cable connection is used for this purpose.

IP/Ethernet network


Pin assignment for 1000Base-T uplink cabling (for stand-alone mode only)
The following table shows the pin assignment for an 1000Base-T uplink connection. A
straight-through cable connection is used for this purpose.

IP/Ethernet network
1 Bi-directional pait +A 1 Bi-directional pait +A

2 Bi-directional pait -A 2 Bi-directional pait -A
3 Bi-directional pait +B 3 Bi-directional pait +B

4 Bi-directional pait -B 4 Bi-directional pait -B
5 Bi-directional pait +C 5 Bi-directional pait +C
6 Bi-directional pait -C 6 Bi-directional pait -C

7 Bi-directional pait +D 7 Bi-directional pait +D
8 Bi-directional pait -D 8 Bi-directional pait -D
Assumptions
• The IPADSL2_32p APs are inserted in the correct slots.
• The ADSL2+ subscriber cables are installed in the rack.
• If the pack has to operate in stand-alone mode, the uplink cable is installed in the
rack.
....................................................................................................................................................................................................................................
363-211-555 7-235
Procedure
...................................................................................................................................................................................................
1 Connect the cable connector which is labeled ″POTS″ to the POTS connector on the
faceplate of the AP so that the cable exits the connector downwards. The keyed profile
of the connector will prevent you from attaching the connector in the wrong direction.
...................................................................................................................................................................................................
2 Connect the other cable connector which is labeled ″POTS-ADSL″ to the POTS-ADSL
connector on the faceplate of the AP in the same way.
...................................................................................................................................................................................................
connector.
possible causes:
• Are the faceplate connector properly fixed?
If a connector is not fixed properly, an alarm tip/ring cable disconnect
will raise.
Try another cable.
• Is the AP or a connector on the faceplate of the AP faulty?
Replace the AP.
...................................................................................................................................................................................................
4 IF... THEN...
the AP will operate in controlled mode End of Steps
the AP will operate in stand-alone mode connect a 100Base-T cable or a
1000Base-T cable for the uplink to port
LAN2.
...................................................................................................................................................................................................
5 IF... AND.... THEN...

the AP will operate in a serial connection to the connect the CONSOLE
stand-alone mode RS232 port CONSOLE is port of the AP and a PC
required for initial system terminal via the adapter
turn-up, cable.
the initial settings for the connect a 100Base-T cable
OAM&P have already been to the LAN port LAN1
done, (see “OAM&P
Connectivity” (p. 2-13)).
....................................................................................................................................................................................................................................
7-236 363-211-555
IF you want to return to the links for activating service for IPADSL2_32 APs click
on back to activate ADSL2 service.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-237
Procedures used for support of L2 and L3

functionality
Overview
...................................................................................................................................................................................................................................
Purpose
The following section provides the applicable procedures for support of L2 and L3
functionality. The procedure descriptions include detailed information about how to
perform the procedures and specify if certain assumptions have been made.
Contents
Create/modify a VLAN 7-239

Provision/Delete addresses in DHCP relay 7-247
Provision/Delete MAC address learning 7-248
Provision/Delete static route 7-251
Provision/Disable broadcast storm control 7-252
Provision/Disable IGMP snooping 7-254
Trace route 7-257
...................................................................................................................................................................................................................................
7-238 363-211-555
Create/modify a VLAN
...................................................................................................................................................................................................................................
Purpose
Use this procedure to:
• Create a VLAN on an IPFM, ESIM, ICAP, LPZ600, LPZ602, VSIM or on an
IPADSL AP.
• Enable or disable a filter for the incoming packets on an IPFM port, ESIM port,
VSIM port or on an IPADSL port.
• Provision the acceptable frame types on an IPFM port, ESIM port, VSIM port or
on an IPADSL port.
• Provision the PVID for individual ports on a VSIM AP.
For the VSIM AP, the PVID is also provisionable. It is not automatically set to the
VLAN ID of the untagged VLAN. Ports on the VSIM AP can be provisioned as
untagged in multiple VLANs. It is recommended that the PVID is set to the VLAN
ID of one of the Untagged VLANs.
When creating a VLAN, the following provisionable items are required:
• VLAN Type
• VLAN ID
• VLAN Name
• Broadcast Storm Control (optional)
• IP Address (only applicable for Layer 3 VLANs; not applicable for VSIM APs)
• Subnetmask (only applicable for Layer 3 VLANs; not applicable for VSIM APs)
• Associated ports and egress rule per port
• Port VLAN ID (PVID) including Ingress Filter and type of Acceptable Frame.
Background on VLANs
The AnyMedia ® Access System system supports three types of VLANs:
•
– ″Normal″, port-based VLANs, including shared VLANs
– Layer 3 VLANs
– Tunnel VLANs (also known as QinQ or stacked VLANs).
• Each VLAN is linked with an ingress and an egress rule.
• Additionally to the ingress rules, classifying and policing is supported (see Chapter
4, “Quality of service”)
• VLANs must be provisioned separately on every single pack.
• VLAN configuration must be carefully planned through the whole network, or data
loss might occur.
...................................................................................................................................................................................................................................
363-211-555 7-239
Detailed procedure descriptions Create/modify a VLAN
• VLANs support MAC learning and broadcast storm control (note that VSIM APs
support broadcast storm control on a per pack basis only)
• There is no distinction between upstream or downstream except for tunnel VLANS
(for tunnel VLANs, downstream ports can be provisioned as QinQ access ports or
QinQ ports. Upstream ports can only be provisioned as QinQ ports). All ports are
treated identically. Only the physical connection makes a difference.
Not all packs support all VLAN types. The table below shows which VLAN types are
supported by the individual pack types.
Pack type VLAN types

Port-based VLANs L3 VLAN Tunnel-VLAN
Normal Shared
VLANs VLANs
IPFM × × × ×
VoIP AP ×
VSIM AP × ×
ESIM × × × ×
IPADSL2_32 × ×
AP
• The number of supported VLANs depends on the pack type:

– The IPFM supports 257 VLANs.
– The ESIM supports 257 VLANs.
– The VSIM AP supports 253 VLANs.
– The IPADSL2 AP supports 32 VLANs.
– The LPZ600 supports 1 VLAN.
– The LPZ602 supports up to 2 VLANs.
– The ICAP supports up to 3 VLANs.
Port-based VLANs
• Port-based VLANs form broadcast domains:
– Broadcast messages are forwarded to all members of a VLAN, but not to other
ports.
– Unicast messages with a known MAC address are only sent to the
corresponding port.
– Unicast messages with unknown MAC address are broadcasted.
– Multicast messages are only sent to all ports which have members of this
multicast group. Membership is learned by IGMP.
• The VLANs are identified by their VLAN ID
....................................................................................................................................................................................................................................
7-240 363-211-555
• The AnyMedia ® Access System supports VLAN 1 to 4092. VLAN 4093 and 4094
are reserved for internal use.
• Ports are assigned to a VLAN with egress rules:
– Untagged
– Tagged
– Shared.
Note that egress rules are not provisionable for the LPA633 in stand-alone mode,
therefore the procedure below is not applicable in this case.
• Each port can be member of many VLANs, but only one can be untagged (except
VSIM).
• Each port has a PVID (port VLAN ID). This VLAN ID is used to tag untagged
packets for internal use. Default PVID for all ports is ″1″.
• Each port has ingress rules. A filter, which is enabled or disabled can be defined.
Ingress filter Accepted frames Result

Disabled All All received packets are
accepted at the port.
However they might be
Tagged only dropped later by
subsequent policies
Enabled All Untagged and/or tagged
packets with a valid VLAN
ID are accepted1
Tagged only Only tagged packets with a
valid VLAN ID are
accepted1
Notes:
1. A VLAN ID is valid, when the port is a member of this VLAN.
Shared VLANs
There are applications (e.g. video broadcast), where it might be helpful to split
protocols in different VLANs (e.g. control data and video stream).
• VLAN unaware subscribers connected to a port can only be member of one
untagged VLAN. To allow splitting traffic into different VLANs, a shared VLAN
must be used (or better: the port must be a shared member of a VLAN).
• A shared VLAN is unidirectional (not unicast), but is expected to transport
broadcast or multicast traffic.
• Broadcast traffic (e.g. video) from the ISP can be sent tagged (preferred) or
untagged, but it will be untagged at the subscriber ports.
....................................................................................................................................................................................................................................
363-211-555 7-241
• Control traffic is expected always to be tagged at network side.

• Untagged traffic from the subscribers will be sent tagged with the corresponding
VLAN ID (via a normal port-based VLAN) to the ISP.
Layer 3 VLANs
Layer 3 VLANs (L3 VLANs) allow routing in the packs of the AnyMedia ® Access
System.
• For L3 VLANs the packs support routing on VLAN base, not on port base.
Therefore the IP address is not assigned to a port, but to the VLAN.
• When an IP address (and subnet mask) is assigned to a VLAN, this VLAN
becomes a L3 VLAN and is internally connected to the router.
• Routing is only supported between L3 VLANs
• If routing is done between tagged VLANs, the VLAN ID of a routed packet is
changed.
• Subscribers on a L3 VLAN should have their default gateway set to the IP address
of this VLAN.
• L3 VLANs may support inband management. If L3 VLAN OAM access is desired,
then the L3 VLAN has to be provisioned at initial system turn-up.
• L3 VLANs are (optionally) used on VoIP APs to segregate different traffic types
like RTP, Signaling and OAM (in stand-alone operation or for ROCs of subtending
remote terminals).
Tunnel-VLANs
Tunnel-VLANs (also called QinQ or stacked VLANs) support an additional (outer)
VLAN tag on a packet.
• The additional tag is the VLAN ID of the tunnel-VLAN.
• A port can be member of a tunnel-VLAN being a QinQ -port or QinQ -access
-port.
• Packets at QinQ-ports have the additional outer VLAN tag, QinQ -access -port do
not.
• Packets received at a QinQ-access-port are forwarded to a QinQ-port by adding the
additional tag.
• Packets received at a QinQ-port are forwarded to an access port by deleting the
additional tag.
• Packets received at a QinQ-port are forwarded unchanged to QinQ-ports.
• If a port is member of a tunnel-VLAN, it cannot be member of normal port-based
or L3 VLAN.
• It is strongly recommended to only send tagged frames to a port, which is member
of a tunnel-VLAN, because there is no way to distinguish between a tunneled
untagged packet and a tagged not tunneled packet.
....................................................................................................................................................................................................................................
7-242 363-211-555
Provisioning scenarios
Provisioning scenarios for the different VLAN types are provided in the Applications
and Planning Guide for IP-based services (363-211-587).
Procedure
...................................................................................................................................................................................................
1 IF... THEN...
you want to create or provision a VLAN go to Step 2
on an IPFM
you want to create or provision a VLAN go to “Provision ICAP parameters ”
on an ICAP (p. 7-113)
you want to create or provision a VLAN go to “Provision VoIP AP parameters”
on a VoIP (p. 7-89)
...................................................................................................................................................................................................
2 From the menu bar select IP Subsystem -> IP Data -> L2 Functions -> VLAN
Configuration{
...................................................................................................................................................................................................
3 Select the applicable Slot.

...................................................................................................................................................................................................
4 IF... THEN...
you want to create a VLAN go to Step 5
you want to enable or disable a filter for click PVID.
the incoming packets on an IPFM port or In the PORT VLAN ID window select the
on a VSIM port correct slot, then move the cursor to the
line with the applicable port and
right-click in the column Ingress Filter.
From the pop-up menu entry Ingress Filter
select Disable or Enable and click Apply.
END OF STEPS
....................................................................................................................................................................................................................................
363-211-555 7-243
IF... THEN...
you want to provision the acceptable click PVID.
frame types on an IPFM port or on a In the PORT VLAN ID window select the
VSIM port correct slot, then move the cursor to the
right-click in the column Acceptable
Frame. From the pop-up menu entry
Acceptable Frame select All or Tagged
only and click Apply.
END OF STEPS
you want to provision the PVID for click PVID.
individual ports on a VSIM AP In the PORT VLAN ID window select the
correct slot, then move the cursor to the
right-click in the column PVID. From the
pop-up menu entry PVID select Modify
PVID and enter a new PVID for the
selected VLAN. Click Apply.
END OF STEPS
...................................................................................................................................................................................................
5 From the VLAN Type pull-down menu select either VLAN or Tunnel.
...................................................................................................................................................................................................
6 Set the OAM Capable VLAN (optional). The configuration options are: 0 means no
OAM capable VLAN is defined, 5000 means no inband OAM is permitted, and the
range of 2..4091 if VLAN is provisioned as L3, then inband OAM via this interface is
possible.
...................................................................................................................................................................................................
7 IF... THEN...
you want to create a standard VLAN go to Step 8
you want to create a tunnel-VLAN go to Step 10
...................................................................................................................................................................................................
8 Enter the following VLAN information:

• VLAN ID (in the range of 1...4092)
• VLAN Name
• IP Address (not applicable for Layer 2 VLANs)
• Subnetmask (not applicable for Layer 2 VLANs).
....................................................................................................................................................................................................................................
7-244 363-211-555
...................................................................................................................................................................................................
9 Select the associated VLAN ports and determine the egress rule for each port:
In the Port List field right click in the Egress Rule field of the selected port and
select the applicable egress rule for this port. The ports 1 to n are the links to the AP
slots. Then go to Step 12.
Additional Info - The following VLAN egress can be selected:
• Egress Tagged (standard VLAN)
To frames that are transmitted from these ports, a 4-byte tag including the VLAN
ID will be added (or kept if already contained) to the MAC frame header.
• Egress Untagged (standard VLAN)
Originally tagged frames that are transmitted from these ports, become untagged
(the tag field will be removed). An untagged frame remains untagged.
• Egress Shared (standard VLAN)
Egress shared refers to overlapping VLAN domains.
The ingress VLAN assignment (PVID setting) is derived from the provisioned egress
untagged VLAN membership of that particular port.
System Failure:
The creation of a new VLAN will be refused in the following cases:
• A given port is defined in a new standard VLAN and that port was already
defined as QinQ-access-port in an existing tunnel-VLAN.
...................................................................................................................................................................................................
10 Enter the following VLAN information:

• VLAN ID (in the range of 1...4092)
• VLAN Name
...................................................................................................................................................................................................
11 Select the associated VLAN ports and determine the egress rule for each port:
In the Port List field right click in the Egress Rule field of the selected port and
select the applicable egress rule for this port. The ports 1 to n are the links to the AP
slots. Go to Step 12.
Additional Info - The following VLAN egress can be selected:
• QinQ-port (for tunnel-VLANS only)
Any packet received on the port should be a double tagged packet with a second
802.1Q tag which VLAN ID should be the same as the VLAN ID of the
tunnel-VLAN.
If an untagged packet is received on the port, the packet will belong to the other
VLAN associated with the PVID of the port. If a tagged packet is received on the
....................................................................................................................................................................................................................................
363-211-555 7-245
port and the VLAN ID in the outer tag is different to the VLAN ID of the
tunnel-VLAN, then the packet will be discarded. Any packet to be forwarded from
the tunnel-VLAN to the tagged port will be transmitted as double tagged packet
and the VLAN ID in the outer tag will be defined by the VLAN ID of the
tunnel-VLAN.(for tunnel-VLANs only)
• QinQ-access-port (for tunnel-VLANS only)
Any packet received on the port will be tagged with a second 802.1q tag regardless
of the tagged/untagged type of the original packets. The VLAN ID in the outer tag
will be defined by the VLAN ID of the tunnel-VLAN. Any packet to be forwarded
from the tunnel-VLAN to the port will be transmitted with the second IEEE
802.1Q tag removed.
A given port can only be defined as QinQ-access-port in one tunnel-VLAN. A port
can only be provisioned as a QinQ-access-port if it is not in any non-default
standard VLAN or any tunnel-VLAN.
The ingress VLAN assignment (PVID setting) is derived from the provisioned egress
untagged VLAN membership of that particular port.
System Failure:
The creation of a new VLAN will be refused in the following cases:
• A given port is defined as QinQ-access-port in a new tunnel-VLAN and that
port was already defined in an existing non-default standard VLAN.
...................................................................................................................................................................................................
12 Click Apply.
Result: The VLAN is created and is displayed in the table.
...................................................................................................................................................................................................
13 IF... THEN...
you want to modify the VLAN regarding return to Step 4
ingress filter or acceptable frames or if
you want to modify PVIDs for VSIM
ports
you do not want to modify the VLAN go to Step 14
...................................................................................................................................................................................................

NVDS.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-246 363-211-555
Provision/Delete addresses in DHCP relay

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision IP addresses of one or several DHCP servers in the
IPFM or in the ESIM or to delete addresses.
Background
DHCP servers can be used to distribute dynamic IP addresses to the APs. But the
DHCP servers may not be located within the same subnet as the APs. Therefore the
IPFM or the ESIM may act as a DHCP relay between the DHCP requests of the APs
and the DHCP servers and their responses.
Procedure
...................................................................................................................................................................................................
1 From the GSI menu bar select IP SubSystem -> IP Data -> L3 Functions -> DHCP
Relay...
Result: The DHCP Relay window opens. It may display a list of already
provisioned IP addresses of DHCP servers.
...................................................................................................................................................................................................
2 IF... THEN...
you want to add an additional DHCP in the Server field enter the IP address
server and click Add. Go to Step 3.
you want to delete a DHCP server select the IP address in the table and click
Delete selected Server. Go to Step 3.
...................................................................................................................................................................................................
3 Click Refresh.
Result: The table reflects the modification.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
363-211-555 7-247
Provision/Delete MAC address learning

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision MAC learning for static MAC addresses or to delete
MAC addresses.
Background
MAC addresses can be:
• Dynamic MAC addresses which are automatically learned by the system and
automatically deleted when for a provisionable time frame no packets are sent from
it or
• Static MAC addresses.
The IPFM and the ESIM support the following MAC address learning features:
• Up to 64 static MAC addresses provisionable per VLAN ID (downlinks only)
• Max 4096 static MAC addresses per pack
• MAC addresses can be learned per port (uplinks and downlinks)
• Learned MAC addresses can be deleted
• Max. 250 dynamic MAC addresses per VLAN on pack
• Max 512 dynamic MAC addresses per port
• Max 4096 dynamic MAC addresses per pack.
The VSIM AP and the IPADSL2_32p AP support the following MAC address learning
features:
• MAC addresses can be learned per VDSL/ADSL port
• MAC addresses can be provisioned per VDSL/ADSL port
• A limit of 1...35 is provisionable per port for dynamic MAC addresses
• A limit of 1...20 is provisionable per port for static MAC addresses
• Dynamic entries can be declared static.
Procedure
...................................................................................................................................................................................................
1 From the GSI menu bar select IP SubSystem -> IP Data -> L2 Functions -> MAC
Learning...
Result: The MAC Learning window opens.
...................................................................................................................................................................................................
2 From the Slot pull-down menu select the applicable slot.

...................................................................................................................................................................................................
3 From the Port pull-down menu select the applicable port.
...................................................................................................................................................................................................................................
7-248 363-211-555
Detailed procedure descriptions Provision/Delete MAC address learning
...................................................................................................................................................................................................
4 IF... THEN...
you want to provision a static MAC Go to Step 5.
address
you want to delete a static MAC address in the Static MAC addresses field in the
table select the applicable rows. Then
click Delete or Delete selected MAC’s.
Result:
A confirmation window opens. After
confirmation the entries are removed from
the table.
END OF STEPS
you want to delete static MAC addresses in the Static MAC addresses field select
with a specific VLAN ID (on IPFM or this VLAN ID from the pull-down menu.
ESIM) Then click Delete MAC’s with VLAN ID.
Result:
the table.
END OF STEPS.
you want to provision the time after that a in the Pack Parameter field enter a value
dynamic MAC address is deleted when no in the Aging Time [sec] text field and
packages were sent from it click Apply.
Note, that in the VSIM AP the actual time
interval for deleting a MAC entry when
no packets have been received may range
from 1 to 2 times the provisioned interval.
For example, if the MAC ageing timer on
a VSIM AP is set to 5 minutes, MACs
will be deleted after 5 to 10 minutes of
inactivity.
END OF STEPS.
you want to delete all dynamic MAC in the Dynamic MAC addresses field
addresses for a port (on IPFM or ESIM) select the Port from the pull-down menu .
Then click Delete All MAC’s.
Result:
the table.
END OF STEPS.
....................................................................................................................................................................................................................................
363-211-555 7-249
Detailed procedure descriptions Provision/Delete MAC address learning
IF... THEN...
you want to delete dynamic MAC in the Static MAC Addresses field select
addresses with a specific VLAN ID (on the Port and this VLAN ID from the
IPFM or ESIM) pull-down menu. Then click Delete MAC’s
with VLAN ID.
Result:
the table.
END OF STEPS.
you want to declare a dynamic MAC in the Dynamic MAC Addresses field
address to become static (on VSIM AP or select the row in the table and click Move
IPADSL2_32p AP) to Static MAC Table>>.
Result:
After a refresh the MAC address is
displayed in the table holding the static
MAC addresses.
END OF STEPS.
...................................................................................................................................................................................................
5 In the Static MAC Addresses field select the VLAN ID and the Port (applicable for
IPFM and ESIM) from the pull-down menus.
...................................................................................................................................................................................................
6 Then enter the MAC address and click Add.

Result: This MAC address is now a static MAC address and will not be deleted
automatically.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-250 363-211-555
Provision/Delete static route

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision on the IPFM or ESIM up to 256 static routes through
the network or to delete them.
For the static route provisioning for ICAPs follow the “Provision ICAP parameters ”
Procedure
...................................................................................................................................................................................................
1 From the GSI menu bar select IP SubSystem -> IP Data -> L3 Functions -> Static
Route...
Result: The Static Route window opens.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
3 IF... THEN...
you want to provision a static route Go to Step 4.
you want to delete a static route select the applicable entry in the table and
click Delete.
Result: The entry is removed from the
table.
END OF STEPS.
...................................................................................................................................................................................................
4 In the text fields enter the values for

• Destination IP Address
• Subnet Mask
• Gateway.
...................................................................................................................................................................................................
5 Click Apply.
Result: The new static route is displayed in the table.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
363-211-555 7-251
Provision/Disable broadcast storm control

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision broadcast storm control or to disable it.
Important! Broadcast storm control the following provisioning is required:
• First enable broadcast storm control on the pack
• Then set the threshold in the VLAN configuration window.
Broadcast storm control on pack level is supported on all IP packs (except the VoIP
AP), broadcast storm control per VLAN is supported by the IPFM and the ESIM.
Broadcast storm control provisioning on pack

...................................................................................................................................................................................................
1 From the GSI menu bar select IP SubSystem -> IP Data -> Equipment -> Pack
Provisioning...
Result: The Pack Provisioning window opens.
...................................................................................................................................................................................................
2 Select the Global Pack Parameter tab.

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

...................................................................................................................................................................................................
4 IF... THEN...
you want to provision broadcast storm from the pull-down menu select Enable.
control Click Apply.
Result:
All per VLAN configured broadcast storm
control thresholds are activated. Go to
Broadcast storm control provisioning on
VLAN.
you want to disable broadcast storm from the pull-down menu select Disable.
control Result:
All per VLAN configured broadcast storm
control thresholds can be set, but will be
ignored.
...................................................................................................................................................................................................
5 Click Apply.
E...................................................................................................................................................................................................
ND OF STEPS
...................................................................................................................................................................................................................................
7-252 363-211-555
Detailed procedure descriptions Provision/Disable broadcast storm control
Broadcast storm control provisioning on VLAN

...................................................................................................................................................................................................
1 From the GSI menu bar select IP SubSystem -> IP Data -> L2 Functions -> VLAN
Configuration...
...................................................................................................................................................................................................
2 IF... THEN...
you want to provision broadcast storm go to Step 3.
control on an existing VLAN
you want to provision broadcast storm follow “Create/modify a VLAN ”
control on a new VLAN (p. 7-239). Then go to Step 3.
...................................................................................................................................................................................................
3 In the left field of the window enter the applicable VLAN ID and the VLAN Name.
...................................................................................................................................................................................................
4 In the BC Storm Control [pps] field enter a value (the value needs to be a multiple of
16 pps) for the number of broadcast packets per second that are allowed to access this
VLAN at a maximum.
...................................................................................................................................................................................................
5 Click Apply.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-253
Provision/Disable IGMP snooping

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision the system for Internet group management protocol
(IGMP) snooping in order to restraining multicast traffic. On VSIM APs and
IPADSL2_32p APs the subscriber ports can individually be enabled for IGMP
snooping. The Multicast Forwarding Table can be retrieved on IPFM, VSIM, ESIM
and IPADSL2_32p APs.
Procedure
...................................................................................................................................................................................................
1 From the GSI menu bar select IP SubSystem -> IP Data -> L3 Functions -> IGMP
Snooping...
Result: The IGMP Snooping window opens.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
3 IF... THEN...
you want to provision IGMP snooping from the IGMP Snooping pull-down menu
select Enabled. Go to Step 4.
you want to disable IGMP snooping from the IGMP Snooping pull-down menu
select Disabled. Go to Step 5.
you want to enable forced ageing (on from the Forced Ageing pull-down menu
IPFM and ESIM) select Enabled and enter a value for the
ageing timeout. Go to Step 5.
you want to retrieve the multicast click Display Multicast Forwarding
forwarding table (on IPFM, VSIM, ESIM Table>>.
and IPADSL2_32p APs) Result:
A window with the Multicast Forwarding
Table opens, displaying details about the
destinations.
you want to enable or disable fast leave from the Fast Leave Mode pull-down
mode on VSIM AP or IPADSL2_32p AP menu select either Enable or Disable. Go
to Step 5.
you want to enable or disable fast leave fast leave is always enabled on a per
mode on IPFM and/or ESIM VLAN ID/port basis.
After selecting the correct pack, select the
VID from the pull-down menu. Then click
on the port(s) for which you would like to
apply Fast Leave. Go to Step 5.
...................................................................................................................................................................................................................................
7-254 363-211-555
Detailed procedure descriptions Provision/Disable IGMP snooping
IF... THEN...
you want to enable individual subscriber select the applicable ports.
ports for IGMP snooping (on VSIM AP Go to Step 5.
and IPADSL2_32p AP)
...................................................................................................................................................................................................
4 IF... THEN...
the pack is an IPFM or an ESIM go to Step 5.
the pack is a VSIM AP or an enter values for
IPADSL2_32p AP • IGMP Query Timeout
• IGMP Query Interval
• Max. Response Time.
Then go to Step 5.
...................................................................................................................................................................................................
5 Click Apply.
Result: Blue text at the bottom of the window provides status information.
E...................................................................................................................................................................................................
ND OF STEPS
IPADSL IGMP snooping parameters
Parameters Default Ranges Comment

Per Pack
Admin State Disable Enable IGMP Global Administrative State
Disable (Enabled/Disabled) – specifies if IGMP
Snooping is Enabled or Disabled in the
IPADSL2+ Inter-Working system. If enabled,
the multi-cast frames associated to the
VLANs enabled for IGMP Snooping will be
handled by the IGMP Snooping algorithm
running on the layer 2 inter-working system.
Router Discovery Disable Enable This parameter enables/disables router port
Disable discovery in the switch. If disabled, only the
Ethernet uplinks will be treated as router
forwarding ports. If this entry is enabled,
ADSL bridge ports may be added to the
forwarding port list of router ports.
Fast Leave Disable Enable This parameter specifies whether IGMP fast
Disable leave is enabled for this switch.
....................................................................................................................................................................................................................................
363-211-555 7-255
Detailed procedure descriptions Provision/Disable IGMP snooping
Parameters Default Ranges Comment

Query Timeout 125 sec 60-600 Router Port Purge Interval - This parameter
specifies how long the IGMP snooping
algorithm will wait before removing learned
multicast router ports from the forwarding
port list if no protocol control packets have
been received.
Query Interval 260 sec 130-1225 ATM Bridge Port Purge Interval – this
parameter
specifies how long the IGMP snooping
algorithm will wait before removing ATM
Bridge Ports from a multicast flow once no
response to multicast queries are received
through the port.
Max. Resp. Time 1 sec 0-25 specifies the minimum interval in seconds
IGS will wait after having sent a
group-specific query message on a Vlan port.
If no response is received from the port
during this interval, the port is removed from
the registered multicast group. Allowed range
is [0-25] seconds. Setting this parameter to 0
causes the pack to apply Fast Leave mode for
all the configured ATM Bridge Ports.
Report Fwd Interv. 5 sec 0-25 specifies the minimum interval in seconds
between IGMP membership report messages
sent by the switch.
Query Src IP 0.0.0.0 specifies the source IP address in IGMP
query messages sent by the switch.
Per VLAN
VLAN Id 1 1-4092 VLANs 0 and 4093-4095 are reserved for
internal use of the system.
IGMP Snooping Disable Enable specifies if IGMP Snooping is Enabled or
Disable Disabled for this VLAN.
....................................................................................................................................................................................................................................
7-256 363-211-555
Trace route
...................................................................................................................................................................................................................................
Purpose
Use this procedure to trace route through the network to an IP address that can be
routed to.
This feature is supported by the IPFM and by all stand-alone IP APs including the
ICAP.
Procedure
...................................................................................................................................................................................................
1 From the GSI menu bar select IP SubSystem -> IP Data -> L3 Functions -> Trace
Route.
Result: The Trace Route window opens.
...................................................................................................................................................................................................
2 In the Destination IP Address field enter the IP address to be routed to.

...................................................................................................................................................................................................
3 Click Apply.
Result: Blue text at the bottom of the window provides status information. The
table displays the number of hops to the IP address, and response times.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
363-211-555 7-257
Procedures used for QoS support
Overview
...................................................................................................................................................................................................................................
Purpose
The following section provides procedures related to QoS provisioning. The QoS
provisioning is different for the different pack types.
The procedure descriptions include information about how to provision the classifier
tables, the classification rules and the scheduler on the IPFM and the ESIM, how to set
up classification rules and provision the scheduler on VSIM APs.
Contents
Provision/Modify L2/L3 group priorities for QoS 7-259

Provision/Modify L4 group priorities for QoS 7-262
Provision/Modify classifiers on VSIM APs 7-265
Provision/Modify packet type priorities for QoS 7-269
Provision/Modify policies on VSIM APs 7-272
Provision/Modify policy attributes on VSIM APs 7-274
Provision/Modify policy instances on VSIM APs 7-277
Provision the IPFM/ESIM for QoS 7-279
Provision VSIM APs for QoS 7-287
...................................................................................................................................................................................................................................
7-258 363-211-555
Provision/Modify L2/L3 group priorities for QoS

...................................................................................................................................................................................................................................
Purpose
This procedure is used to retrieve, delete, provision, or modify L2/L3 group priorities
on different packs in order to support quality of service (QoS). The provisioning of
L2/L3 group priorities is currently supported by the IPFM and by the ESIM.
Procedure
...................................................................................................................................................................................................
1 From the menu bar, select IP Subsystem -> IP Data -> QoS -> L2/L3 Groups...
Result:
The L2/L3 Group Provisioning window opens.
...................................................................................................................................................................................................
2 Select the Slot number for the applicable pack.

...................................................................................................................................................................................................
3 IF... THEN...
you want to retrieve the provisioned go to Step 4.
L2/L3 group priorities for a pack
you want to delete a provisioned L2/L3 go to Step 4 to identify the L2/L3 group
group priority for this group. Then follow Step 6
.
you want to provision a new L2/L3 group go to Step 7.
you want to edit an existing the L2/L3 go to Step 4 to identify the priority for
group this L2/L3 group. Then follow Step 17.
...................................................................................................................................................................................................
4 Click List All L2/L3 Groups>>.

Result:
The List All Classifier L2/L3 Group window for this pack opens, showing all table
entries (up to 128). L2/L3 group priority 124 through 127 are default entries. The
L2/L3 priority is selected automatically according to the order of the entries (first entry
gets #0, then #1,{). The table entries are validated from top to bottom. A match ends
the table search.
...................................................................................................................................................................................................
5 Click Cancel to close the window.

END OF STEPS
...................................................................................................................................................................................................................................
363-211-555 7-259
Detailed procedure descriptions Provision/Modify L2/L3 group priorities for QoS
...................................................................................................................................................................................................
6 In the L2/L3 Group Priority pull-down menu select the L2/L3 priority that shall be
deleted and click Delete.
Result:
After confirmation, the applicable entry is deleted and disappears from the List All
Classifier L2/L3 Group window.
System Failure: The deletion will be denied if the selected priority is a default entry.
END OF STEPS
...................................................................................................................................................................................................
7 Click New.
Result:
The lines in the L2/L3 Group Provisioning window become editable.
...................................................................................................................................................................................................
8 In the L2/L3 Group Name text line enter a name to identify the table entry.
The name can consist of any ASCII text. No space is allowed.
...................................................................................................................................................................................................
9 Enter any number between 1{63 in the L2/L3 Group ID field. This number will be
used in the classifier rules table.
...................................................................................................................................................................................................
10 From the Packet Type pull-down menu select the applicable packet type.
Choices are:
• IP or
• IPX.
...................................................................................................................................................................................................
11 From the Classify Packet based on pull-down menu select:

• Source or
• Destination or
• Both.
...................................................................................................................................................................................................
12 If applicable, check the IP/Network Address checkbox and enter the IP address and
the net mask.
...................................................................................................................................................................................................
13 If applicable, check the VLAN ID checkbox and enter the VLAN ID.
...................................................................................................................................................................................................
14 If applicable, check the Physical Port No. checkbox and select the appropriate port
from the pull-down menu.
....................................................................................................................................................................................................................................
7-260 363-211-555
Detailed procedure descriptions Provision/Modify L2/L3 group priorities for QoS
Choices on the IPFM are:

• FE1 or FE2 or GbE1 or GbE2
• AP1{AP14 for LAG 1900 Shelf or
• AP1{AP16 for LAG 2300 Shelf
• CPU or
• Broadcast/Multicast.
Choices on the ESIM are:
• 1 .... 8 or
• CPU or
• Broad-/Multicast
...................................................................................................................................................................................................
15 If applicable, check the DSCP Bits checkbox and enter the 802.1p/DSCP bits as
requested. DSCP or 802.1p has been selected during global pack provisioning.
...................................................................................................................................................................................................
16 Click Apply.
Result:
A new line is added to the List All Classifier L2/L3 Group.
END OF STEPS
...................................................................................................................................................................................................
17 In the L2/L3 Group Priority pull-down menu select the L2/L3 priority that shall be
edited and click Edit.
Result:
The lines in the L2/L3 Group Provisioning window become editable.
...................................................................................................................................................................................................
18 Edit the applicable lines and click Apply.

Result:
The applicable entry is changed in the List All Classifier L2/L3 Group window.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-261
Provision/Modify L4 group priorities for QoS

...................................................................................................................................................................................................................................
Purpose
This procedure is used to retrieve, delete, provision, or modify L4 group priorities on
different packs in order to support quality of service (QoS). The provisioning of L4
group priorities is currently supported by the IPFM or if an ESIM is used as controller
in a LAG 200 Shelf.
Procedure
...................................................................................................................................................................................................
1 From the menu bar, select IP Subsystem -> IP Data -> QoS -> L4 Groups...
Result:
The L4 Group Provisioning window opens.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
3 IF... THEN...
you want to retrieve the provisioned L4 go to Step 4.
group priorities for a pack
you want to delete a provisioned L4 group go to Step 4 to identify the L4 group
priority for this group. Then follow Step 6
.
you want to provision a new L4 group go to Step 7.
you want to edit an existing the L4 group go to Step 4 to identify the priority for
this L4 group. Then follow Step 18.
...................................................................................................................................................................................................
4 Click List All L4 Groups>>.

Result:
The List All Classifier L4 Group window for this pack opens, showing all table
entries (up to 128). L4 group priority 124 through 127 are default entries. The L4
priority is selected automatically according to the order of the entries (first entry gets
#0, then #1,{). The table entries are validated from top to bottom. A match ends the
table search.
...................................................................................................................................................................................................

END OF STEPS
...................................................................................................................................................................................................................................
7-262 363-211-555
Detailed procedure descriptions Provision/Modify L4 group priorities for QoS
...................................................................................................................................................................................................
6 In the L4 Group Priority pull-down menu select the L4 priority that shall be deleted
and click Delete.
Result:
Classifier L4 Group.
System Failure: The deletion will be denied if the selected priority is a default entry.
END OF STEPS
...................................................................................................................................................................................................
7 Click New.
Result:
The lines in the L4 Group Provisioning window become editable.
...................................................................................................................................................................................................
8 In the L4 Group Name text line enter a name to identify the table entry.
...................................................................................................................................................................................................
9 Enter any number between 1{63 in the L4 Group ID field. This number will be used in
the classifier rules table.
...................................................................................................................................................................................................
10 From the Packet Type pull-down menu select the applicable packet type.
Choices are:
• IP or
• IPX.
...................................................................................................................................................................................................
11 From the Classify Packet based on pull-down menu select:

• Source or
• Destination or
• Both.
...................................................................................................................................................................................................
12 If applicable, check the L4 Prot/IPX Pack Type check box and enter the L4
Protocol/IPX packet type as requested (17 = UDP, 6 = TCP).
...................................................................................................................................................................................................
13 If applicable, check the L4 Prot./Port No./IPX Socket/Data check box and enter the
L4 protocol port # / IPX socket # as requested.
...................................................................................................................................................................................................
14 If applicable, check the TCP Flags check box.

....................................................................................................................................................................................................................................
363-211-555 7-263
Detailed procedure descriptions Provision/Modify L4 group priorities for QoS
Result:
The following check boxes appear:
• Urgent
• Ack
• Reset
• Synch
• Finish.
...................................................................................................................................................................................................
15 Select the TCP flags as requested.

...................................................................................................................................................................................................
16 Click Apply.
Result:
A new line with the provisioned L4 group is added to the List All Classifier L4 Group
window.
END OF STEPS
...................................................................................................................................................................................................
17 In the L4 Group Priority pull-down menu select the L4 group priority that shall be
edited and click Edit.
Result:
...................................................................................................................................................................................................

Result:
The applicable entry is changed in the List All Classifier L4 Group window.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-264 363-211-555
Provision/Modify classifiers on VSIM APs

...................................................................................................................................................................................................................................
Purpose
This procedure is used to provision or delete classifiers on VSIM APs in order to
support quality of service (QoS). It includes the provisioning of the classifiers and the
classifier rules for them.
Up to 8 classifiers with up to 6-classifier rules for each classifier can be provisioned
for VSIM APs.
Provision classifiers
...................................................................................................................................................................................................
1 From the menu bar, select IP Subsystem -> IP Data -> QoS -> Classifier Rules...
Result:
The Classifier Rules Provisioning window opens.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
3 IF... THEN...
you want to delete a classifier with all its Select the appropriate classifier number
rules from the pull-down menu and click
Delete.
Result: After confirmation, the applicable
classifier with all its rules is deleted.
END OF STEPS
you want to provision a new classifier go to Step 4.
you want to edit an existing classifier Go to Step 6.
...................................................................................................................................................................................................
4 Click New.
Result:
The lines in the Classifier Rules Provisioning window become editable.
...................................................................................................................................................................................................
5 In the Classifier Name text line enter a name to identify the classifier and click
Apply.
Result:
...................................................................................................................................................................................................................................
363-211-555 7-265
Detailed procedure descriptions Provision/Modify classifiers on VSIM APs
A classifier has been provisioned. A classifier number will be automatically assigned to

it. Go to the next subprocedure “Provision classifier rules within classifiers” (p. 7-266).
...................................................................................................................................................................................................
6 Select the appropriate classifier number from the pull-down menu and click Edit.
Result:
...................................................................................................................................................................................................
7 In the Classifier Name text line enter a new name to identify the classifier and click
Apply.
Result:
A classifier has been provisioned. A classifier number will be automatically assigned to
it.
Go to the next subprocedure “Provision classifier rules within classifiers” (p. 7-266)
.
E...................................................................................................................................................................................................
ND OF STEPS
Provision classifier rules within classifiers

...................................................................................................................................................................................................
1 From the Classifier Number pull-down menu select the appropriate classifier number.
...................................................................................................................................................................................................
2 IF... THEN...
you want to delete a classifier rule Select the appropriate classifier rule
number from the pull-down menu and
click Delete.
classifier with all its rules is deleted.
END OF STEPS
rule
...................................................................................................................................................................................................
3 Click New.
Result:
The lines in the lower part of the Classifier Rules Provisioning window become
editable. A classifier rule number will automatically be assigned to it.
....................................................................................................................................................................................................................................
7-266 363-211-555
...................................................................................................................................................................................................
4 From the Match Type pull-down menu select the classifier rule type that should match.
Options are shown in “VSIM classifier provisioning - match types” (p. 7-267).
Result:
Depending on the type selected, the window expands in order to enter further
parameters.
...................................................................................................................................................................................................
5 Enter further parameters as required.

...................................................................................................................................................................................................
6 Select either Match or Exclude depending on how the rule should be applied to the
selected type
...................................................................................................................................................................................................
7 Click Apply.
...................................................................................................................................................................................................
8 IF... THEN...
No more classifiers or classifier rules have END OF STEPS
to be provisioned
More classifier rules have to be Repeat “Provision classifier rules within
provisioned within the selected classifier classifiers” (p. 7-266).
END OF STEPS
More classifiers have to be provisioned Repeat the complete procedure for each
additional classifier.
END OF STEPS
E...................................................................................................................................................................................................
ND OF STEPS
VSIM classifier provisioning - match types
Match type Options Parameter

802.1p - 802.1p bits
Dest. IP address - IP address
network mask
Dest. L4 port - Port #
Dest. MAC - MAC address
MAC address mask
....................................................................................................................................................................................................................................
363-211-555 7-267
Match type Options Parameter

Ethernet type custom Type
Apple Talk -
ARP -
IBMSNA -
IP v4 -
IP v6 -
IPX -
MPLS MCAST -
MPLS UCAST -
NETBIOS -
NOVELL -
PPPOE -
RARP -
Every - -
IP DSCP - DSCP bits
IP Precedence - IP Precedence
IP TOS - TOS bits
- TOS match mask
Protocol - L4 protocol #
Ref. Class - Inherited rules from class
number
Src. IP address - IP address
network mask
Src. L4 port - Port #
Src. MAC - MAC address
MAC address mask
VLAN - VLAN ID
....................................................................................................................................................................................................................................
7-268 363-211-555
Provision/Modify packet type priorities for QoS

...................................................................................................................................................................................................................................
Purpose
This procedure is used to retrieve, delete, provision, or modify packet type priorities on
different packs in order to support quality of service (QoS). The provisioning of packet
type priorities is currently supported by the IPFM and by the ESIM (if the ESIM is
used as controller in a LAG 200 Shelf).
Procedure
...................................................................................................................................................................................................
1 From the menu bar, select IP Subsystem -> IP Data -> QoS -> Packet Types...
Result:
The Packet Type Provisioning window opens.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
3 IF... THEN...
you want to retrieve the provisioned go to Step 4.
packet type priorities for a pack
you want to delete a provisioned packet go to Step 4 to identify the priority for
type this packet type. Then follow Step 6.
you want to provision a new packet type go to Step 7.
you want to edit an existing packet type go to Step 4 to identify the priority for
this packet type. Then follow Step 13.
...................................................................................................................................................................................................
4 Click List All Packet Types>>.

Result:
The List of All Packet Types window for this pack opens, showing all table entries
(up to 64). Packet type priority 62 and 63 are default packet types. The packet type
priority is selected automatically according to the order of the entries (first entry gets
#0, then #1,{). The table entries are validated from top to bottom. A match ends the
table search.
...................................................................................................................................................................................................

END OF STEPS
...................................................................................................................................................................................................................................
363-211-555 7-269
Detailed procedure descriptions Provision/Modify packet type priorities for QoS
...................................................................................................................................................................................................
6 In the Packet Type Priority pull-down menu select the packet type priority that shall
be deleted and click Delete.
Result:
Packet Types window.
System Failure: The deletion will be denied if the selected packet type priority is a
default entry.
END OF STEPS
...................................................................................................................................................................................................
7 Click New.
Result:
The lines in the Packet Type Provisioning window become editable.
...................................................................................................................................................................................................
8 In the Packet Type Name text line enter a name to identify the table entry.
...................................................................................................................................................................................................
9 Enter any number between 1{63 in the Packet Type ID field. This number will be
used in the classifier rules table.
...................................................................................................................................................................................................
10 If applicable check the Ethernet Type checkbox and enter the Ethernet type according
to RFC894.
...................................................................................................................................................................................................
11 If applicable check the Packet Type checkbox and select the packet type from the
pull-down menu.
Choices are:
• Unicast
• Multicast
• Broadcast.
...................................................................................................................................................................................................
12 Click Apply.
Result:
A new line with the provisioned packet type is added to the List All Packet Types
window.
END OF STEPS
....................................................................................................................................................................................................................................
7-270 363-211-555
Detailed procedure descriptions Provision/Modify packet type priorities for QoS
...................................................................................................................................................................................................
13 In the Packet Type Priority pull-down menu select the packet type priority that shall
be edited and click Edit.
Result:
The lines (except Packet Type Name) in the Packet Type Provisioning window
become editable.
...................................................................................................................................................................................................

Result:
The applicable entry is changed in the List All Packet Types window.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-271
Provision/Modify policies on VSIM APs

...................................................................................................................................................................................................................................
Purpose
This procedure is used to delete, provision, or modify policies on VSIM APs in order
to support quality of service (QoS) and to assign the policies to an ingress port.
Up to 12 policies can be provisioned on VSIM APs.
Procedure
...................................................................................................................................................................................................
1 From the menu bar, select IP Subsystem -> IP Data -> QoS -> Policy...
Result:
The Policy Provisioning window opens.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
3 IF... THEN...
you want to delete a policy Select the appropriate policy number from
the pull-down menu and click Delete.
policy is deleted with all its instances.
END OF STEPS
you want to provision a new policy go to Step 4.
you want to edit an existing policy go to Step 8.
...................................................................................................................................................................................................
4 Click New.
Result:
The lines in the Policy Provisioning window become editable.
...................................................................................................................................................................................................
5 In the Policy Name text line enter a name to identify the policy.
...................................................................................................................................................................................................
6 From the Port pull-down menu select the ingress ports to which the policy will be
assigned. Then click Assign to Port and Apply. Note that a port can only be assigned
to one policy, while a policy can have several ports assigned to it.
Result:
...................................................................................................................................................................................................................................
7-272 363-211-555
Detailed procedure descriptions Provision/Modify policies on VSIM APs
A new policy has been provisioned. A policy number will be automatically assigned to
it. The selected port is now included in the List of used ports window.
...................................................................................................................................................................................................
7 Repeat this procedure for all required policies.

END OF STEPS
...................................................................................................................................................................................................
8 Select the appropriate policy number from the pull-down menu and click Edit.
Result:
The line Policy Name in the Policy Provisioning window becomes editable.
...................................................................................................................................................................................................
9 Enter a new policy name and click Apply.

Result:
The name of the policy has changed. Port assignment has not been modified.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-273
Provision/Modify policy attributes on VSIM APs

...................................................................................................................................................................................................................................
Purpose
This procedure is used to delete, provision, or modify policy attributes within policy
instances on VSIM APs in order to support quality of service (QoS).
Procedure
...................................................................................................................................................................................................
1 From the menu bar, select IP Subsystem -> IP Data -> QoS -> Policy Attribute...
Result:
The Policy Attribute Provisioning window opens.
...................................................................................................................................................................................................
2 Select the Slot number for the applicable pack. Only slots with VSIM APs are offered.
...................................................................................................................................................................................................
3 Select the appropriate Policy Number from the list of all existing policies on the
selected port.
...................................................................................................................................................................................................
4 Select the appropriate Policy Instance Number from the list of all existing policy
instances for the selected policy.
...................................................................................................................................................................................................
5 IF... THEN...
you want to delete a policy attribute Select the appropriate Policy Attribute
Number from the pull-down menu and
click Delete.
policy attribute is deleted.
END OF STEPS
attribute
you want to edit the parameters of a go to Step 10.
policy attribute Note that the type cannot be edited. In
this case use Delete and New.
...................................................................................................................................................................................................
6 Click New.
Result:
The Type pull-down menu becomes active.
...................................................................................................................................................................................................................................
7-274 363-211-555
Detailed procedure descriptions Provision/Modify policy attributes on VSIM APs
...................................................................................................................................................................................................
7 From the Type pull-down menu select the action how the packet will be handled.
Options are shown in “VSIM policy attribute provisioning” (p. 7-275)
Result:
Depending on the type selected, the window expands in order to enter further
parameters.
...................................................................................................................................................................................................
8 Enter further parameters as required and click Apply.

Result:
A new policy attribute has been provisioned for one policy instance. A policy attribute
number will be automatically assigned to it.
...................................................................................................................................................................................................
9 Repeat this procedure for all required policy attributes in one policy instance.
END OF STEPS
...................................................................................................................................................................................................
10 Select the appropriate Policy Instance Number from the pull-down menu and click
Edit.
Result:
The parameters for the provisioned action type become editable.
...................................................................................................................................................................................................
11 Edit the parameters for this action type as required and click Apply.
E...................................................................................................................................................................................................
ND OF STEPS
VSIM policy attribute provisioning
Type Parameter Explanation Comment

802.1p 802.1p bits Set the 802.1p bits of the Only 1 attribute of these
packet to the selected value types can be contained
IP DSCP DSCP bits Set the DiffServ priority to the in a policy instance
selected value
IP TOS bits Set the IP TOS priority to the
Precedence selected value
....................................................................................................................................................................................................................................
363-211-555 7-275
Detailed procedure descriptions Provision/Modify policy attributes on VSIM APs
Queue Queue Select SC (SC = queue priority The VSIM uses the
priority + 1) highest priority queue
(which is queue 3) to
transport internal
management packets.
See provisioning
recommendation below.
Drop yes/no drop the packet; do not an attribute of this type
forward cannot be combined
with other attributes
Note, that the selection of 802.1p or IP DSCP or IP Precedence will change the data in
the packets.
Provisioning recommendation
If user data is given the same priority by placing it into queue 3, it is possible that
internal management packets will be discarded due to possible congestion of this
queue.
In strict priority scheduling mode it is suggested that queue 3 is either not used for
any user data to avoid this potential loss of internal management packets.
If this queue is used for user data, you must make sure there is no ability to congest
the backplane interface (100 Mb) with user data and that at least 5 Mb (without
overhead) is reserved for the management traffic. Thus, the combined upstream traffic
rate from all VSDL ports must not exceed 95 Mb with overhead included.
If WRR scheduling mode is used, the bandwidth reserved for the highest priority
queue must be sufficient for internal management traffic which is bursty in nature. A
weight of no less than 5 should be used for queue 3. Again it is still recommended to
avoid using queue 3 for user data. If it is used, user data cannot exceed the Queue
Weight - 5. Thus, if the Queue 3’s Weight = 20, user traffic must not exceed 15 Mb.
....................................................................................................................................................................................................................................
7-276 363-211-555
Provision/Modify policy instances on VSIM APs

...................................................................................................................................................................................................................................
Purpose
This procedure is used to delete, provision, or modify policy instances within policies
on VSIM APs and to assign them to classifiers in order to support quality of service
(QoS). Note that if identical policy instances are required in several policies, they have
to be provisioned for each policy separately.
Up to 8 policy instances per policy can be provisioned on VSIM APs.
Procedure
...................................................................................................................................................................................................
1 From the menu bar, select IP Subsystem -> IP Data -> QoS -> Policy Instance...
Result:
The Policy Instance Provisioning window opens.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
3 Select the Policy Number for which the policy instance will be provisioned.
...................................................................................................................................................................................................
4 IF... THEN...
you want to delete a policy instance Select the appropriate Policy Instance
Number from the pull-down menu and
click Delete.
policy instance is deleted with all its
attributes from the selected policy.
END OF STEPS
instance with the classifier link
you want to edit an existing policy go to Step 8.
instance
...................................................................................................................................................................................................
5 Click New.
Result:
The Assign to Classifier Number pull-down menu becomes active.
...................................................................................................................................................................................................................................
363-211-555 7-277
Detailed procedure descriptions Provision/Modify policy instances on VSIM APs
...................................................................................................................................................................................................
6 From the Assign to Classifier Number pull-down menu select the appropriate
classifier to be linked to this policy instance. Only already created classifiers are
offered. Note that one classifier can be linked via a single instance. will be assigned.
Click Apply.
Result:
A new policy instance has been provisioned for the selected policy and assigned to a
classifier. A policy instance number will be automatically assigned to it.
...................................................................................................................................................................................................
7 Repeat this procedure for all required policy instances.

END OF STEPS
...................................................................................................................................................................................................
8 Select the appropriate Policy Instance Number from the pull-down menu and click
Edit.
Result:
The Assign to Classifier Number pull-down menu becomes active.
...................................................................................................................................................................................................
9 From the Assign to Classifier Number pull-down menu select the classifier number
to which the policy instance will be assigned and click Apply.
Result:
A new policy instance has been provisioned and assigned to a classifier. A policy
instance number will be automatically assigned to it.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-278 363-211-555
Provision the IPFM/ESIM for QoS

...................................................................................................................................................................................................................................
Purpose
This procedure is used to provision the IPFM or the ESIM (the ESIM is used as
controller pack in a LAG 200 Shelf) for quality of service (QoS). QoS is supported on
each port, no matter, whether upstream or downstream. Default settings exist for each
table type for the different levels, so that if nothing specific has been provisioned by
the operator, each packet is sent to its destination.
This procedure is subdivided in the following subprocedures:
• Provision/modify the classifier rules
• Provision the scheduler.
Note that it is the operator’s responsibility to create consistent entries in the classifier
tables. When inconsistent table entries are combined in a classifier rule, that rule will
not be hit.
Simplified packet flow
Scheduler
prioritizer
Bandwidth Scheduler
provisioning
Classifier table
provisioning
Prioritizer
Classifier/
policy
Forwarding block
Queue engine
L2 switching
Port queues
Incoming packet L3 routing Outgoing packet
Packet decoder Port
Broadcast storm control queue
Spanning tree protocol mux
Link aggregation
Address learning
dropped packets
VLAN support
Packet flow Label forwarding
Control informaton input
Operation control
...................................................................................................................................................................................................................................
363-211-555 7-279
Detailed procedure descriptions Provision the IPFM/ESIM for QoS
The packet flow through the pack is impacted by the following components
• The packet decoder extracts data from all Ethernet-packets received.
This information is used by the classifier/policy to perform the table comparisons
and to fill the address tables of the forwarding block.
• The forwarding block uses tables (MAC address tables, routing tables,{) to
distribute the incoming packet to the right ports.
Parts of these tables are filled automatically (MAC learning), other parts are
provisioned (static routes,{).
The functions performed by this block are:
– L2 switching
– L3 routing
– Multicasting, broadcasting (including broadcast storm control)
– Spanning Tree Protocol
– Link aggregation
– Address learning
– VLAN support
– Label forwarding (including MPLS, double VLAN, priority tag forwarding)
• The classifier/policy block compares the parameters of the incoming packet with
compare tables and generates output rules how this packet has to be handled.
The compare lists are provisioned. There is only 1-classifier/policy block for all
ports. The compare lists allow checks on dedicated port numbers.
• The scheduler/prioritizer block controls the output queues for each port.
There is one dedicated scheduler per port. The scheduler controls the packet flow
from the queues to the port.
• The prioritizer controls the distribution into the queues. It also can set/change the
802.1p priority of a transmitted packet.
• The queue engine consists of a queue multiplexer (controlled by the prioritizer) and
the queues.
There are 8 queues per port, represented by the queue priorities in the classifier
rules. These rules also map service classes to the queues.
....................................................................................................................................................................................................................................
7-280 363-211-555
Classifier/policy block
Packet types table Classifier rules table
match/ result/ match/ result/

compare ID compare ID
Ethernet type
Packet type Packet type Id
IP address Drop packet

Net mask L2/L3 group table Service class
VLAN Id. match/ result/ Queue priority
Phy. Port # compare ID
L2/L3 group source Id New TOS setting
802.1p priority
DSCP bits source info Packet
policy
destination info L2/L3 group destination Id
L4 group table
L4 protocol / IPX Type
L4 protocol port # / match/ result/
IPX socket / compare ID
L4 group source Id
L4 Data type
TCP flags source info
destination info L4 group destination Id
The classification is done in 2 steps:

• The first step performs comparisons against 5 tables in parallel:
– Packet table
– L2/L3 group table using source addresses
– L2/L3 group table using destination addresses
– L4 group table using source addresses
– L4 group table using destination addresses
Each table comparison delivers an ID, if a match is found. The ID is the table entry
number.
Default entries are available at the end of each table. Comparison is done starting
with the first table entry and ends with the first match. So there is only 1 ID per
pack and table (5 are possible in summary per packet),
• These IDs are used as input for the second step, the comparison in the classifier
rules table. The result from this second comparison defines the action to be
performed on the corresponding packet.
....................................................................................................................................................................................................................................
363-211-555 7-281
Prioritizer rules
• There are 8 queues per output port
• Strict mapping between output queue and queue priority (queue 0 has priority 0,{)
• The outgoing 802.1p bits are equal to the incoming 802.1p bits
• Prioritizer only uses queue priority
Therefore it is recommended to mapping high SC priority to high queue priority.
Do not assign different SCs to the same queue priority.
• Queue priority is determined by:
– Classifier rules table entry (if defined)
– 802.1p bits (if no queue priority is defined)
– TOS/DSCP bits (if no 802.1p bits are available)
– 0 (else).
Provisioning rules
• User table entries are sorted by their input; first entry gets Nr. 0.
• Table entries cannot be manually re-ordered.
• Default table entries are always last in the tables.
• Table entries are checked from start (0) to end (63, 127, 511 respectively).
• The first match in each table ends the look-up process.
• L2/L3 group table entries should be entered with the longest sub-net mask first.
This ensures longest prefix match.
• Packet queue priority and service class in the classifier rules table should carefully
be matched. Do not assign different service classes to the same queue priority.
• It is strongly recommended, not to use more than 4 queue priorities.
• Do not map different service classes to the same queue.
Provision/modify the classifier rules

...................................................................................................................................................................................................
Result:
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-282 363-211-555
...................................................................................................................................................................................................
3 IF... THEN...
you want to retrieve all provisioned Click List All Class. Rules>>.
classifier rules Result: The List All Classifier Rules
window opens, displaying all provisioned
packet types for this pack.
you want to retrieve the provisioned Click List All Packet Types>>.
packet types Result: The List All Packet Types window
opens, displaying all provisioned packet
types for this pack.
you want to retrieve the provisioned Click List All L2/L3 Groups>>.
L2/L3 group priorities for a pack Result: The List All L2/L3 Groups window
opens, displaying all provisioned L2/L3
groups for this pack.
you want to retrieve the provisioned L4 Click List All L4 Groups>>.
group priorities for a pack Result: The List All L4 Groups window
opens, displaying all provisioned L4
groups for this pack.
you want to delete a provisioned classifier identify the rule number and select it from
rule the Class. Rule Number pull-down menu.
Then click Delete.
entry is deleted and disappears from List
All Classifier Rules.
System Failure: The deletion will be
denied if the selected rule is a default
entry.
END OF STEPS
rule
you want to edit an existing classifier rule identify the rule number and select it from
the Class. Rule Number pull-down menu.
Then go to Step 12.
...................................................................................................................................................................................................
4 Click New.
Result:
...................................................................................................................................................................................................
5 In the Class Rule Name text line enter a name to identify the table entry.
....................................................................................................................................................................................................................................
363-211-555 7-283

...................................................................................................................................................................................................
6 If applicable, check the VLAN ID checkbox and enter a VLAN ID as requested.

...................................................................................................................................................................................................
7 If applicable, check the Packet Type ID checkbox and select a valid ID from the
packet type table or follow “Provision/Modify packet type priorities for QoS”
(p. 7-269) in order to provision a new packet type.
...................................................................................................................................................................................................
8 If applicable, in the L2/L3 Group Identifier field, check the Source ID checkbox or
the Destination ID (only Source ID or Destination ID can be tagged, but not both) and
select a valid ID from the L2/L3 group table or follow “Provision/Modify L2/L3 group
priorities for QoS” (p. 7-259) in order to provision a new L2/L3 group.
...................................................................................................................................................................................................
9 If applicable, in the L4 Group Identifier field, check the Source ID checkbox or the
Destination ID (only Source ID or Destination ID can be tagged, but not both) and
select a valid ID from the L4 group table or follow “Provision/Modify L4 group
priorities for QoS” (p. 7-262) in order to provision a new L4 group.
...................................................................................................................................................................................................
10 Determine the Packet Policy for this classifier rule:

• From the Service Class pull-down menu select either No or 1, 2, 3, or 4; this
choice specifies if and which service class is assigned to a packet.
• From the Drop Packet pull-down menu select Yes or No; this choice specifies
whether a packet may be dropped or not.
• From the Queue Priority pull-down menu select a queue priority for a packet;
choices are 0{7
• From the TOS Byte pull-down menu select either No or 1{63;
This selection specifies if and which TOS byte will be added to the packet.
...................................................................................................................................................................................................
11 Click Apply.
Result:
A classifier rule is added to the List All Classifier Rules window.
END OF STEPS
Go to the next subprocedure: “Provision the scheduler” (p. 7-285)
...................................................................................................................................................................................................
12 Click Edit.
Result:
....................................................................................................................................................................................................................................
7-284 363-211-555
END OF STEPS
...................................................................................................................................................................................................

Result:
...................................................................................................................................................................................................

Result:
The applicable entry is changed in List All Classifier Rules.
Go to the next subprocedure: “Provision the scheduler” (p. 7-285)
E...................................................................................................................................................................................................
ND OF STEPS
Provision the scheduler

...................................................................................................................................................................................................
1 From the menu bar, select IP Subsystem -> IP Data -> QoS -> Scheduler...
Result:
The Scheduler window opens.
...................................................................................................................................................................................................
2 From the Slot pull-down menu select the applicable slot number.
...................................................................................................................................................................................................
3 From the Port pull-down menu select the appropriate port.

Choices are:
• On the IPFM
– FE1 or
– FE2 or
– GbE1 or
– GbE2 or
– Any of the AP slots.
• On the ESIM Controller (in slot AP-1, in LAG 200 Shelf)
– GbE (uplink)
– or any of the F1 to F8 (Fast Ethernet downlink ports).
....................................................................................................................................................................................................................................
363-211-555 7-285
...................................................................................................................................................................................................
4 From the Scheduling Mode pull-down menu select either Strict or WRR. Note that
the bandwidth provisioning that is described in the next steps, only applies to WRR
mode.
IF... THEN...
WRR mode has been provisioned go to Step 5.
Strict mode has been provisioned Go to Step 8.
...................................................................................................................................................................................................
5 In the Max BW text line enter the maximum bandwidth to distribute on the selected
port (1{2000 Mbit/s).
...................................................................................................................................................................................................
6 In the Nominal BW text line enter for each of the four service classes the nominal
bandwidth (0{2000 Mbit/s).
The nominal bandwidth defines the threshold, after which traffic will be rated as unfair.
In case of congestion, unfair traffic will be dropped first.
...................................................................................................................................................................................................
7 In the Guaranteed BW text line enter for each of the four service classes the
guaranteed bandwidth (0{2000 Mbit/s).
...................................................................................................................................................................................................
8 Click Apply.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-286 363-211-555
Provision VSIM APs for QoS

...................................................................................................................................................................................................................................
Purpose
This procedure is used to provision the VSIM APs for quality of service (QoS). QoS is
supported on each port, no matter, whether upstream or downstream.
The procedure is subdivided into two subprocedures:
• Provision/modify the classifiers including classifier rules, and policies including
policy instancies and policy attributes.
• Provision the scheduler.
Classifier/policy block on VSIM APs (internal logical links)
port port port port port port port port
policy policy policy policy

instance instance instance instance
attribute attribute attribute attribute
Classifier Classifier Classifier Classifier Classifier Classifier Classifier Classifier

rule rule rule rule rule rule rule rule
(Logical) link port <--> Policy (Logical) link policy instance <--> Classifier
The classifier/policy block is built of dedicated classifiers and policies.

• There are up to 12 policies
Each policy:
– Is identified by a number (automatically assigned) and a user-defined name.
– Is linked to one or more ports.
– Contains up to 8 policy instances.
Each instance:
– Is identified by a number (automatically assigned)
– Is linked to a classifier.
...................................................................................................................................................................................................................................
363-211-555 7-287
Detailed procedure descriptions Provision VSIM APs for QoS
Each policy-attribute:
– Defines a single action, that will be performed with a packet. Actions could be:
output queue to use, discard, redirect, change 802.1Q priority, change IP
priority, IP precedence
– Several actions can be performed with the same packet, but not all combination
are allowed.
Policies cannot share policy instances. If policies should contain identical policy
instances, these policy instances must be created in each policy.
• There are up to 8 classifiers.
Each classifier:
– Is identified by a number (automatically assigned) and a user-defined name
– Can be linked to several policy instances.
– Contains up to 6 classifier rules.
Each classifier rule contains a comparison type (and value).
Dependent on this, packets that match the comparison will then be handled by
the policy attributes of the linked policy instance.
Packet handling on VSIM APs
Weight
provisioning Scheduler
Classifier &
policy
provisioning Prioritizer
Classifier /
policy block
Forwarding Queue engine

block Port queues
Incoming packet Port Outgoing packet
Packet decoder queue
mux
dropped packets
Packet flow
Control informaton input
Operation control
• A packet that enters the VSIM pack passes the packet decoder, which extracts
information from each packet.
• This information will be handled by the policy to which this port is linked. A port
can only be linked to 1 policy.
• The packet is then checked by each classifier linked to the policy via the policy
attributes.
....................................................................................................................................................................................................................................
7-288 363-211-555
• If a classifier result indicates, that the packet must be processed, the policy marks
the packet with the policy attributes.
• Only the policy attributes of the policy instance, to which the classifier is linked
are valid (a policy attribute links only 1 classifier).
• The corresponding actions indicated by the policy attributes are not performed by
the policy function block, but by subtending function blocks (e.g. forwarding
block).
Provision/modify the classifier rules

...................................................................................................................................................................................................
Result:
...................................................................................................................................................................................................
2 Select the Slot number for the applicable VSIM pack.

...................................................................................................................................................................................................
3 Select an existing classifier or provision a new one by following “Provision/Modify

classifiers on VSIM APs” (p. 7-265). The provisioning of the classifier includes the
provisioning of the classifier rules.
Up to 8 classifiers can be provisioned.
...................................................................................................................................................................................................
4 From the menu bar, select IP Subsystem -> IP Data -> QoS -> Policy...
Result:
The Policy Provisioning window opens.
...................................................................................................................................................................................................
5 Select an existing policy or provision new ones by following “Provision/Modify

policies on VSIM APs” (p. 7-272).
Up to 12 policies can be provisioned.
...................................................................................................................................................................................................
6 From the menu bar, select IP Subsystem -> IP Data -> QoS -> Policy Instance...
Result:
The Policy Instances Provisioning window opens.
...................................................................................................................................................................................................
7 Select existing policy instances or provision new ones by following “Provision/Modify

policy instances on VSIM APs” (p. 7-277).
Up to 8 policy instances can be provisioned per policy.
....................................................................................................................................................................................................................................
363-211-555 7-289
...................................................................................................................................................................................................
8 From the menu bar, select IP Subsystem -> IP Data -> QoS -> Policy Attribute...
Result:
The Policy Attributes Provisioning window opens.
...................................................................................................................................................................................................
9 Select existing policy attributes or provision new ones by following “Provision/Modify

policy attributes on VSIM APs” (p. 7-274).
Go to the next subprocedure: “Provision the scheduler” (p. 7-290).
E...................................................................................................................................................................................................
ND OF STEPS
Provision the scheduler

...................................................................................................................................................................................................
1 From the menu bar, select IP Subsystem -> IP Data -> QoS -> Scheduler...
Result:
The Scheduler window opens.
...................................................................................................................................................................................................
2 From the Slot pull-down menu select the applicable slot number.
...................................................................................................................................................................................................
3 From the Port pull-down menu select the appropriate port. Choices on the VSIM AP
are Uplink or 1{16.
...................................................................................................................................................................................................
4 Enter the Priority for this port.

...................................................................................................................................................................................................
5 From the Scheduling Mode pull-down menu select either Strict or WRR. Note that
the WRR priority provisioning and provisioning of weights that is described in the next
step, only applies to WRR mode.
IF... THEN...
WRR mode has been provisioned go to Step 6.
Strict mode has been provisioned Go to Step 7.
In case of Strict mode

...................................................................................................................................................................................................
6 In the Weights text lines enter the weights for the four service classes. The range is
from 0...100 in steps of 5.
....................................................................................................................................................................................................................................
7-290 363-211-555
Assigned bandwidth per SC:

BWSCx = (BWport×WeightSCx)/(WeightSC1+...+WeightSC4)
Queues are emptied until the bandwidth limit is reached or the queue is empty.
This results in:
• No overbooking
• All service classes are served even in case of congestion.
...................................................................................................................................................................................................
7 In the 802.1p Priority text lines enter for each of the four service classes the priorities.
...................................................................................................................................................................................................
8 Click Apply.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-291
Procedures used for operations, administration and

maintenance functions
Overview
...................................................................................................................................................................................................................................
Purpose
The following section provides procedures related to OAM&P activities such as
software administration, inventory management, performance management, fault
management, migration and reconfiguration. The procedure descriptions include
detailed information about how to perform the procedures and specify if certain
assumptions have been made.
Contents
Activate VoIP AP 1:N port protection 7-294

AP Software download and activation in controlled mode 7-297
Activate system log facility 7-304
Database backup 7-306
Database restore 7-308
Deactivate VoIP AP 1:N port protection 7-310
Delete an IP application pack 7-312
Force IPFM side switch 7-313
ICAP Media monitoring 7-315
IP AP Growth 7-317
IP AP Degrowth 7-318
ICAP Migration from duplex to simplex mode 7-321
IPFM Migration from duplex to simplex mode 7-323
Provision/Delete trap receiving 7-325
Provision/deprovision CPU utilization alarm 7-326
Retrieve active alarms 7-327
Retrieve IP Equipment 7-328
Retrieve RMON statistics 7-330
Retrieve call statistics on ICAP 7-332
IPFM/ESIM Software download and activation 7-335
Software download/activation and database backup/restore for 7-340
stand-alone AP(s)
...................................................................................................................................................................................................................................
7-292 363-211-555
System initialization 7-347

VoIP Voice stream monitoring 7-350
....................................................................................................................................................................................................................................
363-211-555 7-293
Activate VoIP AP 1:N port protection

...................................................................................................................................................................................................................................
Purpose
Use this procedure to protect one port on a VoIP AP running SIP control protocol. With
this procedure it is possible to delay an AP replacement in case of an AP circuit.
Note: The system supports one 1:N protection in the IP subsystem at a time.
Required equipment
A PC that is installed with the GSI software.
A COMDAC and a CIU/CTU is required for 1:N port protection.
Assumptions
TheAnyMedia ® Access System is in normal operation mode.
Important note
When 1:N port protection is active, the tip/ring of the protecting line is bridged to the
tip/ring of the protected line. Phones attached to both ports will ring when the
protected line receives a call. Therefore the a/b cabling of the protection port should
terminate at the MDF, that means no subscriber connects to it.
Procedure
...................................................................................................................................................................................................
1 For connecting the PC with the AnyMedia ® Access System follow the
procedure“System Access via GSI ” (p. 7-14). Log in to COMDAC and IPFM
...................................................................................................................................................................................................
2 Optionally provision the IPFM on the COMDAC by performing the following steps:
• From the menu bar select TL1 Commands -> Configuration Mgmt -> Ent -> AP
• Set PST to IS
• Select the slot number of the IPFM in the frame AID
• Select the APTYPE to IPP
• Click Execute
• If the shelf has duplex IPFMs, repeat with the second IPFM
...................................................................................................................................................................................................
3 If not already done, provision the VoIP AP(s) on COMDAC by performing the
following steps:
• From the menu bar select TL1 Commands -> Configuration Mgmt -> Ent -> AP
• Set PST to IS
• Select the slot number of the VoIP AP in the frame AID
• Select the APTYPE to VoIPP
...................................................................................................................................................................................................................................
7-294 363-211-555
Detailed procedure descriptions Activate VoIP AP 1:N port protection
• Click Execute
• Repeat these steps for all VoIP APs in the shelf
...................................................................................................................................................................................................
4 Activate the port protection circuit by performing the following steps:

From the GSI menu bar select IP Subsystem -> VoIP -> Test & Maintenance...
Result: The Line Maintenance window opens.
• At the top of the window, select the following information:
– Slot number of the protecting pack
– Port number of the protecting port
• In the N+1 Protection tab select the following:
– Protected Pack (pack number of protected pack)
– Protected Port (port number of protected port).
• Click Start.
Result:
A protection switch status condition is raised.
The Start button will change to Starting and begin to blink. This will change to
Active when the port protection circuit is up.
System Failure:
If the 1:N port protection switch cannot be established an alarm Protection switch
failure is raised. Then verify:
• AP provisioning in COMDAC
• CIU/CTU installation
• Correct port provisioning.
...................................................................................................................................................................................................
5 Provision Registration ID and Contact User Name on protecting port for service:
From the GSI menu bar select IP Subsystem -> VoIP -> Control
Select the tab SIP and then the subtab Transport.
•
– In the Registration Id field, type: phone number of protected port
– In the Contact User Name field, type: phone number of protected port.
• Click Apply.
....................................................................................................................................................................................................................................
363-211-555 7-295
Detailed procedure descriptions Activate VoIP AP 1:N port protection
...................................................................................................................................................................................................
6 Modify Registration ID and Contact User Name on protected port to avoid

duplication:
– Slot number of the protected pack
– Port number of the protected port
•
– In the Registration Id field, type: Disabled
– In the Contact User Name field, type: Disabled.
• Click Apply.
...................................................................................................................................................................................................

NVDS.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-296 363-211-555
AP Software download and activation in controlled mode

...................................................................................................................................................................................................................................
Purpose
• Download AP software from an FTP server to the controller flash
• Download it from the controller flash to the AP
• Activate it.
controller in an IP subsystem. The ESIM is always used in simplex mode and inserted
in slot 1 from LAG 200 Shelf.
Important! The reboot after software activation will cause a service interruption.
Important! Prior to starting the download, make sure that your current
provisioning has been written to NVDS.
AP software download and activation

The example below shows the principle how to download and activate the AP
software.
...................................................................................................................................................................................................................................
363-211-555 7-297
Detailed procedure descriptions AP Software download and activation in controlled mode
1. AP SW download to IPFM flash

IPFM
current
SW
alternate
SW
Flash
new
AP SW
2. SW download to AP(s)
IPFM
AP
current
current
SW
old SW
alternate
SW alternate
SW
Flash
new
AP SW
3. Activate SW
AP
current
old SW
alternate
new SW
Assumptions
Make sure that the following conditions are fulfilled:
• The required software version is available on an FTP server or on the active
controller (in the latter case the software download to controller flash as described
below can be skipped).
• If applicable, an FTP server is available and a connection to the controller is
working.
Software upgrade capabilities for AP

Software upgrades for AP may consist of
• Application patches only or
• Full software upgrades.
....................................................................................................................................................................................................................................
7-298 363-211-555
If the software upgrade is an application patch only, the service outage will be
approximately 10 seconds. If the software upgrade is a full software upgrade then the
service outage is at least 30 seconds.
In order to determine which type of software upgrade is relevant, compare the old SW
version number and the new SW version number. The example below shows how to
distinguish between a patch and an upgrade.
Initial SW version 03.00.01.00 -001_001
Patch 03.00.01.00 -002_001 If there is any difference after the ″-″.
then the SW upgrade is an application
patch and the service impact will be
brief.
Upgrade 03.00.01.01-001_001 If there is any difference before the ″-″,
then the SW upgrade is an application
upgrade and the service impact will be
greater than for a patch.
SW Download to controller flash

...................................................................................................................................................................................................
1 If the Software Administration window is not yet open, from the menu bar select IP
SubSystem -> IP Data -> System -> Software Administration.
...................................................................................................................................................................................................
2 In the SW Download subtab select from the SW Type pull-down menu the AP type.
...................................................................................................................................................................................................
3 In the Download Direction field select the controller (IPFM or ESIM) checkbox.
...................................................................................................................................................................................................
4
IF... THEN...
you want to use the GSI local installed go to Step 5
FTP server on your PC
you want to use external FTP server go to Step 6
...................................................................................................................................................................................................
5 Select the checkbox for Use GSI local FTP Server. Use the Browse... button to enter
the file name and locate the file on the PC. Continue with Step 7.
....................................................................................................................................................................................................................................
363-211-555 7-299
...................................................................................................................................................................................................
6 In the FTP Server Information field enter the required data for starting the connection
to the FTP server:
• Server IP Address
• User ID
• Password
• Filename
...................................................................................................................................................................................................
7 Click Apply.
version is displayed in the On Controller Flash column.
...................................................................................................................................................................................................
8 IF... THEN...
a duplex IPFM configuration is installed copy the AP load (for example ICAP load)
from the active to standby IPFM by
selecting in the Download Direction field
the IPFM Standby. Then click Apply
Result: At the bottom of the Software
Administration window the progress of the
file transfer and writing to flash is
displayed.
a simplex IPFM configuration is installed go to “SW Download to AP(s)” (p. 7-300)
.
E...................................................................................................................................................................................................
ND OF STEPS
SW Download to AP(s)
...................................................................................................................................................................................................
1 In the SW Type pull-down menu select the AP type (for example ICAP).
...................................................................................................................................................................................................
2 IF... THEN...
you want to download the new software in the Download Direction field select the
from the controller flash to all APs of that AP type expanded with All. Then go to
type Step 3.
you want to download the new software in the Download Direction field select the
from the controller flash to single APs applicable AP(s). Then go to Step 3.
only
....................................................................................................................................................................................................................................
7-300 363-211-555
IF... THEN...
you want to download the new software in the Download Direction field select
from the controller flash to APs (for both APs and determine which is the
example ICAPs) in duplex configuration active and standby AP. Then go to “SW
Activation duplex mode” (p. 7-301).
...................................................................................................................................................................................................
3 Click Apply.
version is displayed in the Alternate column of the software versions for the APs
selected.
Go to next procedure: “SW Activation simplex mode” (p. 7-301)
E...................................................................................................................................................................................................
ND OF STEPS
SW Activation simplex mode

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

...................................................................................................................................................................................................
Select the Slot number of the AP type to be activated or click Select All.
...................................................................................................................................................................................................
3 Click Apply.
Result: The AP reboots. After the reboot has completed, the AP(s) will run the new
software version.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
5 Repeat Step 1 through Step 4 for other APs as required.
E...................................................................................................................................................................................................
ND OF STEPS
SW Activation duplex mode

...................................................................................................................................................................................................
1 Select IP Subsystem -> ICAP -> System -> Generic -> Duplex Maintenance.
....................................................................................................................................................................................................................................
363-211-555 7-301
...................................................................................................................................................................................................
2 First activate the software on the standby ICAP by selecting the SW Activation subtab
on the Software Administration window.
...................................................................................................................................................................................................
3 Select the Slot number of the standby AP type (for example ICAP).
Result: The ICAP will appear in the Type window.
In the SW Activation subtab the current and alternate software versions are
displayed.
...................................................................................................................................................................................................
4 Click Apply.
Result: The ICAP reboots. After the reboot has completed, the ICAP will run the
...................................................................................................................................................................................................

...................................................................................................................................................................................................
6 Go to the Duplex subtab and wait until the standby ICAP is ReadyToProtect before
continuing.
...................................................................................................................................................................................................
7 After that, activate the software on the active ICAP by selecting the SW Activation
subtab on the Software Administration window.
...................................................................................................................................................................................................
8 Select the Slot number of the active ICAP.

displayed.
...................................................................................................................................................................................................
9 Click Apply.
Result: The active ICAP reboots. This will cause an ICAP switch and the standby
ICAP will become the active ICAP. After the reboot has completed, the standby
ICAP will become the active ICAP and running the new software version.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-302 363-211-555

...................................................................................................................................................................................................
11 Wait until the formerly standby ICAP is ReadyToProtect before continuing.

END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-303
Activate system log facility

...................................................................................................................................................................................................................................
Purpose
Use this procedure to activate the system log facility on individual AnyMedia IP packs.
That includes the installation of the Kiwi Syslog Daemon, which is part of the GSI
software delivery, on the local PC and to start logging.
Optionally these logs can also be logged by some other RFC3164 compliant syslog
server on a different host than the GSI.
Important! The various options of system logging should be used for diagnostic
purposes only. Setting tracing options during normal operation will decrease the
overall traffic capacity of the individual pack(s).
Background
Some packs provide the possibility to send RFC3164 compliant syslog notifications.
• The ICAP allows logs of
– Megaco control protocol
– Protocol errors
– Control events.
• The VoIP APs LPZ60x allow
– RTP tracing
– SLIC Log.
In any case the Kiwi Syslog Daemon which is part of the GSI software delivery or a
separate syslog daemon has to be installed before.
Assumption
The syslogd.exe file is available. In a standard GSI installation it is located in the
path C:\ProgramFiles\AnyMedia\GSI\Syslogd.exe.
Procedure
...................................................................................................................................................................................................
1 Execute once the syslogd.exe file to install the Kiwi Syslog Daemon.
...................................................................................................................................................................................................
2 Start the GSI.

Additional information For more details refer to “System Access via GSI ”
(p. 7-14).
...................................................................................................................................................................................................
3 For a system in controlled mode connect to the IPFM, or directly connect to the ICAP
or the VoIP AP if the pack runs in standalone mode.
...................................................................................................................................................................................................................................
7-304 363-211-555
Detailed procedure descriptions Activate system log facility
...................................................................................................................................................................................................
4
If... then...
the pack is an ICAP from the menu bar select IP SubSystem ->
ICAP -> SysLog...
the pack is a VoIP AP from the menu bar select IP SubSystem ->
VoIP -> SysLog...
Result: The SysLog Facility window opens.

...................................................................................................................................................................................................
5 In the Module ID frame use the Pack scrollbar to select the applicable pack.
...................................................................................................................................................................................................
6 Activate once the Use GSI’s SysLog Server checkbox to start the syslog facility on
the local PC.
Result: The IP address of your local PC appears in the Host IP Address text field.
The Kiwi Syslog Daemon window opens and displays a table which logs the
notifications sent by the AnyMedia pack.
If you are using the syslog facility for the first time, a welcome window opens too.
Additional information: Alternatively the syslog notifications can be directed to a
different host. In that case do not check the Use GSI’s SysLog Server checkbox
and enter the applicable Host IP Address instead, where the syslog server is
running, instead.
...................................................................................................................................................................................................
7 Activate the checkbox beside the desired tracing option. Note that only those
checkboxes will be active that apply to the pack type.
...................................................................................................................................................................................................
8 Activate the Enabled checkbox and click Apply.

Result: All upcoming messages of the selected type will be logged in the Kiwi
Syslog Daemon window or on the external host that you might have provisioned
above.
...................................................................................................................................................................................................
9 For stopping the system log, open the SysLog Facility window as described above and
deactivate the Enabled Checkbox.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-305
Database backup
...................................................................................................................................................................................................................................
Purpose
Use this GSI operation to backup the database of the IP subsystem.
Important! Prior to starting upload of configuration, make sure that your current
provisioning has been saved to NVDS.
Assumptions
• The current provisioning has been saved to NVDS.
• The required information for starting an FTP session is available.
• An FTP server is available and a connection to the IPFM is working.
Procedure
...................................................................................................................................................................................................
1 From the menu bar select IP Subsystem -> IP Data -> System -> SW
Administration.
Result: The Sofware Administration window opens.
...................................................................................................................................................................................................
2 Select the Backup/Restore tab.

...................................................................................................................................................................................................
3 Select Backup Configuration.

Select NVDS or MOH.
...................................................................................................................................................................................................
4
IF... THEN...
...................................................................................................................................................................................................
the file name and locate the file on the PC.
If you want to obtain the extracted MOH files select the Auto Extract MOH File
checkbox.
Continue with Step 7.
...................................................................................................................................................................................................................................
7-306 363-211-555
Detailed procedure descriptions Database backup
...................................................................................................................................................................................................
6 Enter the following FTP server information:

• User ID
• Password
• Filename.
...................................................................................................................................................................................................
7 Click Apply.
Result: At the bottom of the SW Administration window the progress of the
backup is displayed.
...................................................................................................................................................................................................
8 When complete, click Cancel to close the window.

END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-307
Database restore
...................................................................................................................................................................................................................................
Purpose
Use this procedure to restore a database from the management system to the active
IPFM. In a duplex system, the protection IPFM is automatically updated after the
changes have been saved to NVDS.
If a simplex database is restored onto the IPFM in the non-preferred slot, the system
will remain in duplex mode.
Assumptions
• The required information for starting an FTP session is available.
• An FTP server is available and a connection to the IPFM is working.
Procedure
...................................................................................................................................................................................................
1 From the menu bar select IP Subsystem -> IP Data -> System -> SW
Administration.
Result: The Sofware Administration window opens.
...................................................................................................................................................................................................
2 Select the Backup/Restore tab.

...................................................................................................................................................................................................
3 Select the Restore Configuration.

...................................................................................................................................................................................................
4
IF... THEN...
...................................................................................................................................................................................................
the file name and locate the file on the PC.
Continue with Step 7.
...................................................................................................................................................................................................................................
7-308 363-211-555
Detailed procedure descriptions Database restore
...................................................................................................................................................................................................
6 Enter the following FTP server information:

• User ID
• Password
• Filename.
...................................................................................................................................................................................................
7 Click Apply.
Result: At the bottom of the SW Administration window the progress of the
restore is displayed. When the restore is complete, the active IPFM and the standby
IPFM (if duplex mode is provisioned) and all APs will reboot. The IPFM in the
preferred slot will become the active IPFM.
Note: If a simplex database is restored onto the IPFM in the non-preferred slot, the
system will reset and come up with the IPFM active in the preferred slot in
simplex mode.
...................................................................................................................................................................................................
8 After the reboot has completed, login to the IPFM.

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

NVDS.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-309
Deactivate VoIP AP 1:N port protection

...................................................................................................................................................................................................................................
Purpose
Use this procedure to deactivate a 1:N port protection of a VoIP AP.
Required equipment
A COMDAC and a CIU/CTU is required for 1:N port protection.
Assumptions
The AnyMedia ® Access System is in normal operation mode.
A 1:N port protection is active.
Procedure
...................................................................................................................................................................................................
procedure“System Access via GSI ” (p. 7-14). Log in to IPFM.
...................................................................................................................................................................................................
2 Deactivate the port protection circuit by performing the following steps:

From the GSI menu bar select IP Subsystem -> VoIP -> Test & Maintenance...
Result: The Line Maintenance window opens.
• In the N+1 Protection tab select the following:
– Protected Pack (pack number of protected pack)
– Protected Port (port number of protected port).
• Click Stop.
The Stop button will change to Stopping and begin to blink. The status changes to
Not Active and the blue text will state Not Established.
...................................................................................................................................................................................................
3 Provision original Registration ID and Contact User Name on protected port for
service:
...................................................................................................................................................................................................................................
7-310 363-211-555
Detailed procedure descriptions Deactivate VoIP AP 1:N port protection

•
– In the Registration Id field, type: phone number of protected port
– In the Contact User Name field, type: phone number of protected port.
• Click Apply.
...................................................................................................................................................................................................
4 Modify Registration ID and Contact User Name on protecting port to avoid

duplication:
•
– In the Registration Id field, type: Disabled
– In the Contact User Name field, type: Disabled.
• Click Apply.
...................................................................................................................................................................................................

NVDS.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-311
Delete an IP application pack

...................................................................................................................................................................................................................................
Purpose
Use this procedure to delete the pack provisioning data for an IP application pack.
Procedure
...................................................................................................................................................................................................
1 Follow the “System Access via GSI ” (p. 7-14) procedure.

...................................................................................................................................................................................................
2 For setting the desired pack Out of service from the menu bar select IP Subsystem
-> IP Data -> Equipment -> Pack Provisioning.
...................................................................................................................................................................................................
3 Select the application pack you want to delete by clicking on the desired Slot Number
and press the Delete button.
Result: A warning window pops up which informs you that performing this
procedure will delete all subscriber data.
...................................................................................................................................................................................................
4 Click the Ok button

Result: The relevant application pack will be deleted. The IP pack will reset.
...................................................................................................................................................................................................

NVDS.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
7-312 363-211-555
Force IPFM side switch

...................................................................................................................................................................................................................................
Purpose
Use this GSI operation in a duplex system to force a side switch from the active IPFM
to the protection IPFM. After this procedure has been performed the Operational State
of the previous standby IPFM has changed to IS and the previously active IPFM has
become the new standby IPFM.
Background
The active IPFM does not automatically update the protection IPFM with provisioning
changes. The provisioning information of the protection IPFM is synchronized only
when an Save to NVDS operation is performed manually by the operator. As a result,
if a side switch occurs prior to an Save to NVDS operation, the system will revert to
the last saved configuration.
Assumptions
• The system is provisioned for duplex operation.
• The protection pack is in the OOS (Out of service) or STBY (Standby) operational
state.
• The two IPFMs are of the same type.
• A software download, database back-up, database restore, or software activation
process is not in progress.
Procedure
...................................................................................................................................................................................................
1 Update the protection IPFM with the last provisioning data. For this purpose from the
menu bar select IP SubSystem -> IP Data -> System -> Save Changes to NVDS.
...................................................................................................................................................................................................
2 From the menu bar select IP SubSystem -> IP Data -> System -> Duplex
Maintenance.
Result: The Duplex Pack Maintenance IPFM window opens.
...................................................................................................................................................................................................
3 Click the Forced Switch to Protection button.

Result: A confirmation window appears.
...................................................................................................................................................................................................
4 Confirm the side switch.
...................................................................................................................................................................................................................................
363-211-555 7-313
Detailed procedure descriptions Force IPFM side switch
Result: The previous standby IPFM is in the operational state IS (in service) and
the previously active IPFM is in the operational state STBY (standby). The
transmission configuration and the OAM&P paths have been restored automatically.
System Fault: If the protection IPFM was not in operational state STBY (standby)
or MEA (Mismatch of Equipment) the side switch will be rejected.
...................................................................................................................................................................................................
5 Click Cancel to close the Duplex Pack Maintenance IPFM window.

END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-314 363-211-555
ICAP Media monitoring

...................................................................................................................................................................................................................................
Purpose
Use this procedure to monitor a subscriber line on an ICAP AP.
Required equipment
Assumptions
The AnyMedia ® Access System is in normal operation mode when the test is to be run.
Procedure
...................................................................................................................................................................................................
procedure“System Access via GSI ” (p. 7-14).
...................................................................................................................................................................................................
2 For opening the Media Monitoring screen from the GSI menu bar select IP
Subsystem -> ICAP -> Ports....
Result: The ICAP System Turnup window pops up.
...................................................................................................................................................................................................
3 In the Module ID field select ICAP Pack and Port, then select the Media Mon tab.
...................................................................................................................................................................................................
4 In the frame Media Mon select the following settings:

• IP address or the FQDN of the Media Monitor Host (MMH). The device must be
capable to receive and decode the RTP streams which are sent to the TCP/IP ports
specified below.
• Inbound Port
• Outbound Port
• Media Monitor Control as desired
• Media Monitor Interface read only
• Media Monitor Group
• Media Monitor Port (possible value 1...2048 for SIP)
...................................................................................................................................................................................................
5 Click Apply.
...................................................................................................................................................................................................................................
363-211-555 7-315
Detailed procedure descriptions ICAP Media monitoring
...................................................................................................................................................................................................
6 Setup Call on the selected port and verify that the RTP stream is received by the
MMH.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-316 363-211-555
IP AP Growth
...................................................................................................................................................................................................................................
Purpose
Use this procedure to grow an IP AP to an existing IP subsystem.
Assumptions
Make sure that the IPFM(s) is/are properly installed.
Procedure
...................................................................................................................................................................................................
1 For inserting the AP in the appropriate slot refer to “AP Installation” (p. 7-24).
...................................................................................................................................................................................................
2 For correct provisioning of the AP(s) refer to “Provision IP AP slots” (p. 7-48).
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
363-211-555 7-317
IP AP Degrowth
...................................................................................................................................................................................................................................
Purpose
Use this procedure to remove an IP AP from an in-service IP subsystem.
Required equipment
A PC equipped with the GSI software
Assumptions
This procedure assumes the following conditions:
• The AnyMedia ® Access System shelf is powered and equipped for service
• An IPFM is present
• Customer service is no longer required on any of the ports of the IP AP that is to
be removed.
Background
This procedure is intended to avoid having an alarm issued via the AnyMedia ® Access
System OAM&P interfaces.
Procedure
...................................................................................................................................................................................................
1 Follow “System Access via GSI ” (p. 7-14) for connecting the PC to the IP subsystem.
...................................................................................................................................................................................................
2 CAUTION
Service-disruption hazard
Pressing down on the rounded indentation on the top of the ejector (or removing the
screws on VoIP packs) causes the cable connector to disconnect. This action affects
customer service.
Make sure that the AP you want to degrow is the correct AP.
Follow “Delete an IP application pack” (p. 7-312) to delete the complete provisioning
for this pack.
...................................................................................................................................................................................................
3 If... ...then...
you want to degrow an AP with the go to step 4
connector screwed to the faceplate (e.g. a
VoIP AP)
you want to degrow an AP with an ejector go to step 5
mechanism
...................................................................................................................................................................................................................................
7-318 363-211-555
Detailed procedure descriptions IP AP Degrowth
...................................................................................................................................................................................................
4 Remove the connector from the AP by screwing out the two screws. See the picture
below.
Got to step 6
...................................................................................................................................................................................................
5 Remove the connector from the AP by pushing down the ejector. See the picture
below.
....................................................................................................................................................................................................................................
363-211-555 7-319
Detailed procedure descriptions IP AP Degrowth
...................................................................................................................................................................................................
6 Remove (see “Remove a Circuit Pack ” (p. 7-11)) the IP AP and put it into an
antistatic bag or carton.
...................................................................................................................................................................................................
7 Install a blank faceplate that was originally delivered with the shelf in the empty slot
and secure the cable in the retainer.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-320 363-211-555
ICAP Migration from duplex to simplex mode

...................................................................................................................................................................................................................................
Purpose
Use this procedure to migrate an ICAP system from duplex mode to simplex mode.
Assumptions
• Two ICAPs running in duplex mode, that is, one ICAP is installed in the preferred
slot, and a second one in the ICAP protection slot.
• Duplex E1/DS1 cabling
• LAN crossover cable for 1:1 protection (stand-alone mode only)
• For the wiring refer to the procedure “Wiring for ICAPs” (p. 7-174)
• There are no outstanding alarms against the ICAPs.
Controlled mode
...................................................................................................................................................................................................
1 Delete one of the two ICAPs, the standby or the active ICAP.
From the menu bar, select IP Subsystem -> IP Data -> Equipment -> Pack
Provisioning...
Select the Slot Number to be deleted and click Delete.
Note: If the current active ICAP is to be deleted, the system automatically performs an
NSA ICAP protection switch before the pack is deleted.
...................................................................................................................................................................................................
2 Remove the E1/DS1 cable from the deleted ICAP.

...................................................................................................................................................................................................
3 From the menu bar select IP SubSystem -> ICAP -> Duplex Maintenance...
In the Protection Mode pull-down menu select Simplex and click Apply.
Result: A pop-up window opens:
The pack provisioning for the current stand-by ICAP, must be deleted
first before setting the mode to simplex. Otherwise a setting of
simplex will denied. If the pack is already deleted hit `Yeś to
proceed or `Nó to cancel the action.
...................................................................................................................................................................................................

Result: The remaining ICAP is active and running in simplex mode.
...................................................................................................................................................................................................
5 Save these changes to the NVDS.
...................................................................................................................................................................................................................................
363-211-555 7-321
Detailed procedure descriptions ICAP Migration from duplex to simplex mode
NVDS.
E...................................................................................................................................................................................................
ND OF STEPS
Stand-alone mode
...................................................................................................................................................................................................
1 From the menu bar select IP SubSystem -> ICAP -> Duplex Maintenance...
In the Protection Mode pull-down menu select Simplex and click Apply.
Result: A pop-up window opens:
The stand-by pack (if available) will be reset and initialized to
factory default settings, i.e. into simplex mode without any
provisioning data. Yes / No
...................................................................................................................................................................................................

Result: The remaining ICAP is active and running in simplex mode.
Note that if the active ICAP reside in the protection slot the GSI connection gets
lost and you have to connect again to the ICAP in protection slot.
...................................................................................................................................................................................................
3 Remove the LAN crossover cable from the deleted ICAP (FE2 port).
...................................................................................................................................................................................................
4 Remove the E1/DS1 cable from the deleted ICAP.

END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-322 363-211-555
IPFM Migration from duplex to simplex mode

...................................................................................................................................................................................................................................
Purpose
Use this procedure to migrate an IP subsystem with two IPFMs inserted from duplex
mode to simplex mode.
Assumptions
• The IP subsystem is running in duplex mode, that is, one IPFM is installed in the
preferred slot, and a second one in the IPFM protection slot.
• There are no outstanding alarms against the IPFMs.
• The GSI is connected to both IPFMs via a Y-cable assembly or a hub.
Procedure
...................................................................................................................................................................................................
1 Determine whether the IPFM in the preferred slot is the active one (the ACTIVE LED
should lit in this case):
From the menu bar select IP SubSystem ->IP Data -> System -> Duplex
Maintenance.
Result: The Duplex Pack Maintenance IPFM window opens.
...................................................................................................................................................................................................
2 Check the operational state of the IPFM in the preferred slot.
IF... THEN...
the operational state of the IPFM in the go to Step 4.
preferred slot is IS
the operational state of the IPFM in the go to Step 3.
preferred slot is STBY
...................................................................................................................................................................................................
3 Perform an IPFM side switch by following the “Force IPFM side switch” (p. 7-313)
GSI operation. Note that when performing this GSI operation you will be prompted to
do a “Save to NVDS” operation in advance.
Result: The IPFM in the IPFM preferred slot becomes the active IPFM. The
operational state of the IPFM in the preferred IPFM slot is IS.
...................................................................................................................................................................................................
4 In the Duplex Pack Maintenance IPFM window from the Protection Mode pull-down
menu select Simplex and click Apply.
...................................................................................................................................................................................................................................
363-211-555 7-323
Detailed procedure descriptions IPFM Migration from duplex to simplex mode
Result: The operational state of the standby IPFM changes from Standby to OOS.
System Fault: Simplex provisioning will be denied if the IPFM in the preferred
slot is the standby IPFM.
...................................................................................................................................................................................................

NVDS.
Result: A confirmation window appears. Click YES. The IP subsystem is running
in simplex mode.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
7 Disconnect any cabling from the faceplate of the protection IPFM.

...................................................................................................................................................................................................
8 Remove the IPFM from the IPFM protection slot and put it into an antistatic bag or
carton.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-324 363-211-555
Provision/Delete trap receiving

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision IP addresses and SNMP ports where traps are to be
sent to or to delete them.
Procedure
...................................................................................................................................................................................................
1 From the GSI menu bar select IP SubSystem -> IP Data -> Communication -> Trap
Receiver Table...
Result: The Trap Receiver Table window opens. It displays the IP address/SNMP
port of the IPFM and, if already provisioned, an IP address/SNMP port for sending
traps to.
...................................................................................................................................................................................................
2 Check the operational state of the IPFM in the preferred slot.
IF... THEN...
you want to add an additional address Enter the new IP Address and the SNMP
port and click Add.
Result: The new address is displayed in the
table.
you want to delete an address Select the applicable entry in the table and
click Delete.
Result: The selected entry removes from the
table.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
363-211-555 7-325
Provision/deprovision CPU utilization alarm

...................................................................................................................................................................................................................................
Purpose
Use this procedure to provision the system to raise an alarm when CPU utilization
exceeds a provisioned threshold or to deprovision it. Or use the procedure to retrieve
CPU utilization. The threshold is provisionable per pack.
Procedure
...................................................................................................................................................................................................
1 From the GSI menu bar select IP SubSystem -> IP Data -> System -> CPU
Utilization...
Result: The CPU Utilization window opens. It displays the current CPU utilization
in ″%″ (for all packs that have thresholds Enabled), the provisioning status
(Enabled) and their provisioned thresholds.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
3
IF... THEN...
you want to provision a CPU utilization In the Threshold field enter the CPU
alarm utilization limit.
From the Status pull-down menu select
Enabled. Then go to Step 4.
you want to deprovision a CPU From the Status pull-down menu select
utilization alarm Disabled. Then go to Step 4.
...................................................................................................................................................................................................
4 Click Apply.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
7-326 363-211-555
Retrieve active alarms

...................................................................................................................................................................................................................................
Purpose
Use this GSI operation to retrieve active alarms on the AnyMedia ® Access System.
Procedure
...................................................................................................................................................................................................
1 From the menu bar, select Fault -> Alarms.

Result:
The Alarms window opens. The following descriptors are displayed for current
alarms:
Descriptor Values
Severity CR, MJ, MN
Raised mm-dd/hh:mm:ss
Entity ap-{shelf#}-{slot#}
Message English language description
Extra Info IP Alarm (IPFM)
...................................................................................................................................................................................................
2 Per default the Alarms window will be refreshed automatically. If you want to
deactivate this function click on the check box Auto Refresh. As a result a message
window pops up which warns you that turning off the auto refresh function prevents
any updates to the Alarm Log. Click Ok.
...................................................................................................................................................................................................
3 IF... THEN...
you want to save the values of the Alarms Click Save...; then go to Step 4.
table in a report format
you do not want to save the alarms and END OF STEPS.
conditions table in a report format
...................................................................................................................................................................................................
4 As a result an Alarms Save window pops up. Select the desired path and file name
and click Save.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
363-211-555 7-327
Retrieve IP Equipment
...................................................................................................................................................................................................................................
Purpose
Use this GSI operation to retrieve equipment information for all inserted IP packs (for
example, IPFM, IP APs). Inventory information includes the physical identifier and
state information.
Inventory information for the narrowband packs or ATM xDSL packs is not retrievable
from the IPFM.
Procedure
...................................................................................................................................................................................................
1 Inventory information can be retrieved in two ways:

• From the Shelf View window, right click on the apparatus code on the front plate
of the pack, then click Inventory Data or
• From menu bar select IP Subsystem -> IP Data -> Equipment -> Inventory.
Result: The Inventory Data window opens, displaying the Inventory Data for all
packs in the shelf.
...................................................................................................................................................................................................
2
IF... THEN...
you want to save the inventory data in a report click the Save button to save a log
format file. Then go to Step 3.
you do not want to save the inventory data go to Step 3.
...................................................................................................................................................................................................
3 Click the X box in the Inventory Data window title bar to close the window.
E...................................................................................................................................................................................................
ND OF STEPS
Inventory Data
Heading Meaning Explanation
Entity Physical identifier This field shows the shelf number (1) and the slot number
of the pack
PST Primary Service State This field shows the status of the pack, e.g. IS for in
service.
Type Circuit Pack This is the mnemonic name that identifies the general type
of function provided. For example, the pack type is VoIP.
...................................................................................................................................................................................................................................
7-328 363-211-555
Detailed procedure descriptions Retrieve IP Equipment
Heading Meaning Explanation

APP Apparatus The apparatus code uniquely identifies the specific
function provided by the pack. Packs with different
apparatus codes are not interchangeable (e.g. LPZ600).
ICC Interchangeability The interchangeability code is used to specify the forward
or backward compatibility of two packs with the same
pack type and apparatus code but different manufacturing
versions. It is of the form S m - n, where m is the issue
number and n is the series number of the product. In
general, a pack can be replaced by another pack that has
the same apparatus code and the same issue number
regardless of their Series Numbers
ECI Equipment Catalog The equipment catalog item is a 6-character code
identifying each pack. The code corresponds to the
bar-code label on the face-plate of the pack, and is
uniquely equivalent to the CLEI.
CLEI Common Language The Common Language Equipment Identifier is a
Equipment Identifier 10-character code identifying each pack type.
SLN Serial Number The serial number is a 12-character code uniquely
identifying each pack and indicating the date and place of
manufacture.
PVRSN Program Version
PCDE Program Equipment Only defined for IO-E1 packs and subshelves
Code
....................................................................................................................................................................................................................................
363-211-555 7-329
Retrieve RMON statistics

...................................................................................................................................................................................................................................
Purpose
Use this procedure for remote network monitoring (RMON). It allows to retrieve
RMON statistics for the individual ports of a pack. Currently RMON statistics are
supported for the IPFM.
Procedure
...................................................................................................................................................................................................
1 From the GSI menu bar select IP SubSystem -> IP Data -> Performance Monitoring
-> RMON Statistics.
Result: The RMON Statistics window opens.
...................................................................................................................................................................................................
2 From the Slot pull-down menu select the slot with the applicable pack inserted.
...................................................................................................................................................................................................
3 From the Port pull-down menu select the applicable port.

Result: The table is populated with the RMON Statistics Parameters for the
selected port.
• Drop Events
• Received Packets
• Received Broadcast Packets
• Received Multicast Packets
• Received Packets with CRC Error
• Received Undersized Packets (<64 Bytes)
• Received Oversized Packets (>1516 Bytes)
• Received Fragments
• Received Jabbers
• Collisions
• Received Frames with Size 64 Bytes
• Received Frames with Size 65-127 Bytes
• Received Octets
...................................................................................................................................................................................................................................
7-330 363-211-555
Detailed procedure descriptions Retrieve RMON statistics
...................................................................................................................................................................................................

END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-331
Retrieve call statistics on ICAP

...................................................................................................................................................................................................................................
Purpose
Use this procedure to retrieve call statistics. The ICAP provides call statistics on
demand. It allows to retrieve call statistics for the individual slot of a VoIP pack.
Currently call statistics are supported for the ICAP operating in H.248 mode only.
Background
The ICAP collects counts of events for the entire call traffic at a monitoring interval of
5 minutes. There are 288 × 5-minutes register to store the data and one current 5-min
register. In total, registers cover a period of 24 hours. The registers are numbered from
3 to 289, and ″Current″ and ″Previous″ for the most recent complete register and the
second most recent complete register respectively.
The following measurement entities are defined:
• H.284 (Megaco) command counters
– Add
– Subtract
– Modify
– Move
– Audit
– ServiceChange
– Connection loss to the MGC (MgcConnLoss)
– Invalid termination ID/package (InvTermID)
– ProtoError
– Notify
– TransPendMG2MGC
• Call processing success rate-statistics
– Successful calls (CollSucc..)
– Call failures (FailColl..)
– Premature releases (StableCollFail..)
• Protocol failure counters
• Signaling transport event counters.
Assumptions
Make sure that the VoIP interface is In Service (for obtain a call statistics for all 288
registers, the VoIP interface must have been in service for at least 24 hours.
Procedure
...................................................................................................................................................................................................
1 From the GSI menu bar select IP SubSystem -> ICAP -> Call Statistics...
...................................................................................................................................................................................................................................
7-332 363-211-555
Detailed procedure descriptions Retrieve call statistics on ICAP
Result: The Call Statistics window opens.

...................................................................................................................................................................................................
2 From the Slot pull-down menu select the slot with the applicable pack inserted.
Result: In number of the VoIP interface is displayed at the Interface Nr. field.
...................................................................................................................................................................................................
3 In the Intervals [5 Min] selection field define start and end time for periodic statistics.
Then click Refresh, the GSI retrieves data every 5 minutes as soon as the data
collection is started (parameter for statistics data, see table below).
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
ND OF STEPS
Parameter for the statistics data

All counters of one interval are (in the order as delivered):
01 - AddOrigReq The number of H.248 ’Add Request’ events for originating calls.
02 - AddOrigRepl The number of H.248 ’Add Reply’ events for originating calls.
03 - AddTermReq The number of H.248 ’Add Request’ events for terminating calls.
04 - AddTermRepl The number of H.248 ’Add Reply’ events for terminating calls.
05 - AddOtherReq The number of H.248 ’Add Request’ events unrelated to originating or terminating
calls, e.g. call waiting or conferencing.
06 - AddOtherRepl The number of H.248 ’Add Reply’ events unrelated to originating or terminating
calls, e.g. call waiting or conferencing.
07 - SubOrigReq The number of H.248 ’Subtract Request’ events for originating calls.
08 - SubOrigRepl The number of H.248 ’Subtract Reply’ events for originating calls.
09 - SubTermReq The number of H.248 ’Subtract Request’ events for terminating calls.
10 - SubTermRepl The number of H.248 ’Subtract Reply’ events for terminating calls.
11 - SubOtherReq The number of H.248 ’Subtract Request’ events unrelated to originating or

terminating calls, e.g. call waiting or conferencing.
12 - SubOtherRepl The number of H.248 ’Subtract Reply’ events unrelated to originating
13 - ModOtherReq The number of H.248 ’Modify Request’ events.
14 - ModOtherRepl The number of H.248 ’Modify Reply’ events.

15 - MovOtherReq The number of H.248 ’Move Request’ events.
16 - MovOtherRepl The number of H.248 ’Move Reply’ events.
7 - AuditLineReq The number of H.248 ’Audit Request per line’ events.
18 - AuditLineRepl The number of H.248 ’Audit Reply per line’ events.
19 - AuditCapLineReq The number of H.248 ’Audit Capabilities Request per line’ events.
20 - AuditCapLineRepl The number of H.248 ’Audit Capabilities Reply per line’ events.
....................................................................................................................................................................................................................................
363-211-555 7-333
Detailed procedure descriptions Retrieve call statistics on ICAP
21 - AuditPackReq The number of H.248 ’Audit Request per pack’ events.
22 - AuditPackRepl The number of H.248 ’Audit Reply per pack’ events.

23 - AuditCapPackReq The number of H.248 ’Audit Capabilities Request per pack’ events.
24 - AuditCapPackRepl The number of H.248 ’Audit Capabilities Reply per pack’ events.
25 - AuditRootReq The number of H.248 ’Audit Request per root’ events.

26 - AuditRootRepl The number of H.248 ’Audit Reply per root’ events.
27 - AuditCapRootReq The number of H.248 ’Audit Capabilities Request per root’ events.
28 - AuditCapRootRepl The number of H.248 ’Audit Capabilities Reply per root’ events.
29 - SvcMgcLineReq The number of H.248 ’Service Change Request per line from MGC’ events.
30 - SvcMgcLineRepl The number of H.248 ’Service Change Reply per line from MGC’ events.
31 - SvcMgLineReq The number of H.248 ’Service Change Request per line from MG’ events.
32 - SvcMgLineRepl The number of H.248 ’Service Change Reply per line from MG’ events.
33 - SvcMgcPackReq The number of H.248 ’Service Change Request per pack from MGC’ events.
34 - SvcMgcPackRepl The number of H.248 ’Service Change Reply per pack from MGC’ events.
35 - SvcMgPackReq The number of H.248 ’Service Change Request per pack from MG’ events.
36 - SvcMgPackRepl The number of H.248 ’Service Change Reply per pack from MG’ events.
37 - SvcMgcRootReq The number of H.248 ’Service Change Request per root from MGC’ events.
38 - SvcMgcRootRepl The number of H.248 ’Service Change Reply per root from MGC’ events.
39 - SvcMgRootReq The number of H.248 ’Service Change Request per root from MG’ events.
40 - SvcMgRootRepl The number of H.248 ’Service Change Reply per root from MG’ events.
41 - MgcConnLoss The number of ’connection loss to the MGC’ events.

42 - InvTermId The number of ’invalid termination id received’ events.
43 - InvPkgeElem The number of ’invalid package element received’ events.
44 - ProtoError The number of ’protocol errors received’ events.

45 - CallSuccOrig The number of ’successful originating calls’.
46 - SuccCallTerm The number of ’successful terminating calls’.
47 - FailCallOrig The number of ’failed originating calls’.
48 - FailCallTerm The number of ’failed terminating calls’.

49 - StableCallFailOrig The number of ’prematurely aborted stable originating calls’
50 - StableCallFailTerm The number of ’prematurely aborted stable terminating calls’
51 - TransPendMG2MGC The number of pending H.248 transactions sent from MG to MGC’

52 - TransRetransMG2MGC The number of H.248 transaction retransmissions from MG to MGC’
53 - TransRetransMGC2MG The number of H.248 transaction retransmissions from MGC to MG’
54 - NotifyReq The number of notifications for all lines from MG to MGC

55 - NotifyRepl The number of replies from MGC for all MG notifications
....................................................................................................................................................................................................................................
7-334 363-211-555
IPFM/ESIM Software download and activation

...................................................................................................................................................................................................................................
Purpose
This procedure is used to download and activate new software. It applies to the IPFM
in simplex and duplex mode and to the ESIM in controller mode (in the LAG 200
Shelf only). It may be used either during initial system turn up or in a running system.
Important! The reboot after software activation will cause a service interruption in
simplex mode.
Important! Prior to starting the download, make sure that your current
provisioning has been written to NVDS.
Software download for a duplex IPFM system
...................................................................................................................................................................................................................................
363-211-555 7-335
Detailed procedure descriptions IPFM/ESIM Software download and activation
Assumptions
Make sure that the following conditions are fulfilled:
• The required software version is available on an FTP server (or, if the procedure is
used to download SW to the protection IPFM, it is available on the active IPFM).
• If applicable, an FTP server is available and a connection to the pack is working.
SW download to the controller pack flash

...................................................................................................................................................................................................
SubSystem -> IP Data -> System -> SW Administration.
Result: The Software Administration window opens. The program version
running is listed in the column labeled Current.
...................................................................................................................................................................................................
2 In the SW Download subtab, from the SW Type pull-down menu select the software
type (IPFM or ESIM).
...................................................................................................................................................................................................
3 In the Download Direction field checkbox, select the download direction to the
controller pack (IPFM, ESIM as controller in a LAG 200 Shelf...).
...................................................................................................................................................................................................
4
IF... THEN...
...................................................................................................................................................................................................
...................................................................................................................................................................................................
to the FTP server:
• User ID
• Password
• Filename
...................................................................................................................................................................................................
7 Click Apply.
....................................................................................................................................................................................................................................
7-336 363-211-555
window the new software version is displayed in the Alternate column of the
active IPFM.
System Fault: When the software is mismatched between the active and standby
IPFMs, the standby IPFM is MEA (Mismatch of Equipment). In this case it is not
possible to force a protection switch from the active to the standby IPFM.
...................................................................................................................................................................................................
8 IF... THEN...
the IP subsystem is running in simplex select the SW Activation subtab on the
IPFM mode Software Activation window. Then go to
“Activate SW on active controller pack”
(p. 7-338).
the IP subsystem is running in duplex go to next procedure “Copy software to
IPFM mode standby IPFM” (p. 7-337).
the IP subsystem is running with an ESIM go to next procedure “Activate SW on
as controller in a LAG 200 Shelf active controller pack” (p. 7-338).
E...................................................................................................................................................................................................
ND OF STEPS
Copy software to standby IPFM

...................................................................................................................................................................................................
1 Copy the software from active IPFM to standby IPFM. In the SW Download subtab
select IPFM from the SW Type pull-down menu.
...................................................................................................................................................................................................
2 In the Download Direction field select the IPFM Stby checkbox and click Apply.
window the new software version is displayed in the Alternate column of the both
IPFMs, while the old software is in the Current location on both IPFMs.
E...................................................................................................................................................................................................
ND OF STEPS
Activate SW on standby IPFM

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

...................................................................................................................................................................................................
2 Activate software on the standby IPFM: In the SW Activation subtab select the Slot
number of the standby IPFM.
....................................................................................................................................................................................................................................
363-211-555 7-337
Result: The IPFM appears in the Type window. The Current and Alternate
software versions is displayed.
...................................................................................................................................................................................................
3 Click Apply.
Result: The standby IPFM reboots. When initialization completes, the standby
IPFM is running the new software (Current). The old software is in the Alternate
location.
E...................................................................................................................................................................................................
ND OF STEPS
Activate SW on active controller pack

...................................................................................................................................................................................................
1 Activate software on the active controller pack:

In the SW Activation subtab select the Slot number of the active controller pack.
Result: The controller pack appears in the Type column. The Current and
Alternate software is displayed.
...................................................................................................................................................................................................
2 Click Apply.
Result: The active application pack reboots and in duplex mode a protection switch
occurs. When initialization completes, the controller pack is running with the new
software. The old software is in the Alternate location.
In duplex mode the system ends up running the new software on both, the active
and the standby IPFM. The original standby IPFM (at the beginning of this
procedure) is now the active IPFM.
Note that the service will be interrupted in simplex IPFM mode or when ESIM is
used as controller in LAG 200 Shelf.
...................................................................................................................................................................................................
3 IF... THEN...
the GSI has disconnected reconnect and open the Software
Administration window again.
Result:
The new version is displayed in the
Current column.
Go to Step 4.
....................................................................................................................................................................................................................................
7-338 363-211-555
IF... THEN...
the GSI has not disconnected click Refresh.
Result:
The new software version is displayed in
the Current column.
Go to Step 4.
...................................................................................................................................................................................................
4 Click Cancel to close the Software Administration window.

END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-339
Software download/activation and database backup/restore for

stand-alone AP(s)
...................................................................................................................................................................................................................................
Purpose
• Download the software from an FTP server to the AP flash and activate it,
• or to backup or restore the AP database.
Important! The reload after software download will cause a service interruption.
AP software download and activation

The example below shows the principle how to download and activate the ICAP
software.
1. AP SW download to ICAP flash

ICAP
current
SW
alternate
SW
2. Activate SW
ICAP
current
old SW
alternate
new SW
...................................................................................................................................................................................................................................
7-340 363-211-555
Detailed procedure descriptions Software download/activation and database
backup/restore for stand-alone AP(s)
Assumptions
Make sure that the required software version is available on an FTP server.
SW Download to AP flash
...................................................................................................................................................................................................
1 In the SW Type pull-down menu select the AP type (for example ICAP) and determine
whether the ICAP is a:
• Stand-alone ICAP in simplex mode
• Stand-alone ICAP in duplex mode and the Active Pack
• Stand-alone ICAP in duplex mode and the Standby Pack.
Repeat the following steps for each stand-alone ICAP in simplex or duplex mode.
...................................................................................................................................................................................................
SubSystem -> IP Data -> System -> Software Administration.
...................................................................................................................................................................................................
3 In the SW Download subtab select from the SW Type pull-down menu the appropriate
AP (for example ICAP).
Note: In case of an ICAP in duplex mode (duplex ICAP pair) select always the active
ICAP and set the Auto Copy Mode to enabled.
...................................................................................................................................................................................................
4 In the Download Direction field select the slot number of the AP (for example ICAP)
to be upgraded.
...................................................................................................................................................................................................
5
IF... THEN...
you want to use the external SFTP server go to Step 8
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-341
...................................................................................................................................................................................................
to the external FTP server:
• User ID
• Password
• Filename
To use your choice as the default click the Store as Default button. Continue with
Step 9
...................................................................................................................................................................................................
8 Select the checkbox “SFTP (not selected = FTP)”

In the SFTP Server Information field enter the required data for starting the
connection to the external SFTP server:
• User ID
• Password
• Filename
Step 9
...................................................................................................................................................................................................
9 Click Apply.
version is displayed in the Alternate column.
...................................................................................................................................................................................................
10 IF... THEN...
you want to activate the new software on verify after approximately 5 minutes, that
stand-alone ICAP in simplex mode the software download has completed.
Then go to “SW Activation in simplex
mode” (p. 7-343).
you want to activate the new software on wait until both the active and standby
stand-alone ICAP in duplex mode ICAP downloads are completed. Then go
to “SW Activation in duplex mode”
(p. 7-343).
E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
7-342 363-211-555
SW Activation in simplex mode

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

...................................................................................................................................................................................................
Select the Slot number with the AP (for example ICAP) to be activated or click Select
All.
...................................................................................................................................................................................................
3 Click Apply.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
5 Repeat Step 1 through Step 4 for other ICAPs in simplex mode as required.
E...................................................................................................................................................................................................
ND OF STEPS
SW Activation in duplex mode

...................................................................................................................................................................................................
1 Select IP Subsystem -> ICAP -> System -> Generic -> Duplex Maintenance.
...................................................................................................................................................................................................
2 Go to Duplex subtab and change the Auto Copy Mode to Disabled.

...................................................................................................................................................................................................
3 First activate the software on the standby ICAP by selecting the SW Activation subtab
on the Software Administration window.
...................................................................................................................................................................................................
4 Select the Slot number of the standby AP type (for example ICAP).
displayed.
...................................................................................................................................................................................................
5 Click Apply.
....................................................................................................................................................................................................................................
363-211-555 7-343
...................................................................................................................................................................................................

...................................................................................................................................................................................................
7 Go to the Duplex subtab and wait until the standby ICAP is ReadyToProtect before
continuing.
...................................................................................................................................................................................................
8 After that, activate the software on the active ICAP by selecting the SW Activation
subtab on the Software Administration window.
...................................................................................................................................................................................................
9 Select the Slot number of the active ICAP.

displayed.
...................................................................................................................................................................................................
10 Click Apply.
Result: The active ICAP reboots. This will cause an ICAP switch and the standby
ICAP will become the active ICAP. After the reboot has completed, the standby
ICAP will become the active ICAP and running the new software version.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
12 Go to the Duplex subtab and change the Auto Copy Mode to Enabled.
...................................................................................................................................................................................................
13 Wait until the formerly standby ICAP is ReadyToProtect before continuing.

E...................................................................................................................................................................................................
ND OF STEPS
Database backup/restore
...................................................................................................................................................................................................
1 Select the Backup/Restore tab on the Software Administration window.

...................................................................................................................................................................................................
2 Select Backup Configuration or the Restore Configuration radio button.
....................................................................................................................................................................................................................................
7-344 363-211-555
...................................................................................................................................................................................................
3
IF... THEN...
you want to use the external SFTP server go to Step 6
...................................................................................................................................................................................................
the file name and locate the file on the PC. Continue with Step 7
...................................................................................................................................................................................................
5 In the FTP server information field enter the following data for starting the connection
to the external FTP server:
• User ID
• Password
• Filename
Step 7
...................................................................................................................................................................................................
6 Select the checkbox “SFTP (not selected = FTP)”

In the SFTP server information field enter the following data for starting the
connection to the external SFTP server:
• User ID
• Password
• Filename
Step 7
...................................................................................................................................................................................................
7 Click Apply.
....................................................................................................................................................................................................................................
363-211-555 7-345
Result At the bottom of the SW Administration window, depending on selected

configuration, the progress of the backup or restore is displayed.
...................................................................................................................................................................................................
8 When complete, click Cancel to close the window.

END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-346 363-211-555
System initialization
...................................................................................................................................................................................................................................
Purpose
This procedure uses the GSI to initialize the IP subsystem. The operator has three
options for the level of system initialization. These options and their impact on the IP
subsystem are described in “Background” (p. 7-347).
controller in an IP subsystem. The ESIM is always inserted in to slot 1 from LAG 200
Shelf and in simplex mode configuration.
Background
When initializing the system the operator has the following options
• Clear All Pack Configuration
This partial system initialization results in:
– All AP configuration data is cleared. The APs will reset.
– The configuration file for APs on the controller is deleted.
– All other provisioning on the controller will remain intact.
• Clear System Configuration except Management IP Address and Routing
Information
This partial system initialization results in
– All controller configuration data is cleared with the exception of the
management IP address, subnet mask and routing information.
– Both controller (if in duplex mode) will reset. The system ends up in simplex
mode with the active controller in the preferred slot.
– Except for the management IP and route information, the controller return to a
default (unprovisioned) state.
• Clear all System Configuration.
This full system initialization results in
– All controller configuration data including the Management IP address and the
Routing table is cleared.
– Both controller (if in duplex mode) will reset. The system ends up in simplex
mode with the active controller in the preferred slot.
– The controller return to a default (unprovisioned) state.
...................................................................................................................................................................................................................................
363-211-555 7-347
Detailed procedure descriptions System initialization
CAUTION
Service-disruption hazard
Initializing the system database in a given shelf interrupts IP service to all end users in
the shelf and, depending on the level of system initialization, clears all provisioning on
the controller.
Execution of a full system initialization also drops the operations communications links
to remote GSIs or NAM.
Do not use this procedure on an in-service system. It should normally be used only as
a part of initial system installation and system turn-up procedure.
Procedure
...................................................................................................................................................................................................
1 Follow the “System Access via GSI ” (p. 7-14) procedure.

...................................................................................................................................................................................................
2 For starting the initialization select from the menu bar IP Subsystem -> IP Data ->
System -> Initialize System...
Result: A selection window with the following options opens:
• Clear All Pack Configuration
• Clear System Configuration except Management IP Address and Routing
Information
• Clear all System Configuration
...................................................................................................................................................................................................
3 Select the appropriate system initialization type and click Apply.

Result: A warning window pops up.
...................................................................................................................................................................................................
4 If you are sure that you have selected the correct system initialization type, click Yes.
Result: The system initializes. The GSI will disconnect.
...................................................................................................................................................................................................
5
IF... THEN...
you selected Clear All Pack Configuration The system ends up in a status as
described in “Background” (p. 7-347) for
this option. Go to Step 6.
you selected Clear System Configuration The system ends up in a status as
except Management IP Address and described in “Background” (p. 7-347) for
Routing Information this option.
END OF STEPS.
....................................................................................................................................................................................................................................
7-348 363-211-555
Detailed procedure descriptions System initialization
IF... THEN...
you selected Clear all System The system ends up in a status as
Configuration described in “Background” (p. 7-347) for
this option.
END OF STEPS.
...................................................................................................................................................................................................

NVDS.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
363-211-555 7-349
VoIP Voice stream monitoring

...................................................................................................................................................................................................................................
Purpose
Use this procedure to monitor a subscriber line on a VoIP AP.
Required equipment
Assumptions
The AnyMedia ® Access System is in normal operation mode when the test is to be run.
Procedure
...................................................................................................................................................................................................
procedure“System Access via GSI ” (p. 7-14).
...................................................................................................................................................................................................
2 For opening the line test screen from the GSI menu bar select IP Subsystem -> VoIP
-> Ports....
Result: The VoIP System Turnup window pops up.
...................................................................................................................................................................................................
3 In the Module ID field select VoIP Pack and Port

...................................................................................................................................................................................................
4 In the frame Monitor Call Status Parameters select the following settings:
• IP address of the Media Monitor Host (MMH). The device is capable to receive
and decode the RTP stream.
• Inbound Port value (e.g. 9000) of the MMH if used
• Outbound Port value (e.g. 9000) of the MMH if used.
• Media Monitor Control as desired.
• Media Monitor Port (Phone line 1-32/64)
...................................................................................................................................................................................................
5 Click Apply.
...................................................................................................................................................................................................
6 Setup Call on the selected port and verify that the RTP stream is received by the
MMH.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
7-350 363-211-555
8 C onfiguration Examples
8
Remote Management solutions for ICAP and

RT-ROC (COMDAC)
Overview
...................................................................................................................................................................................................................................
Purpose
This section shows three different remote management scenarios for the ICAP and, via
the AnyMedia RT-ROC (COMDAC), for the connected RTs:
• In controlled mode management via the management port on the IPFM
• In controlled mode inband management via an IPFM uplink port
• In stand-alone mode management via the uplink port on the ICAP.
Management via IPFM management port

The following scenario shows an ICAP in controlled mode can be managed via the
management port of the IPFM. For management a separate Layer 3 VLAN has to be
provisioned on the IPFM and on the ICAP in this case.
...................................................................................................................................................................................................................................
363-211-555 8-1
Configuration Examples Overview
IPFM ICAP COMDAC

GSI
OAM&P config
Management Port IP Addr.: IP-icap_oam
Netmask: NM-oam
VLAN: ID-oam
Management port config
GSI config IP Addr.: IP-mgnt
IP Addr.: IP-gsi Netmask: NM-mgnt IP
Default Route:
Netmask: NM-mgnt Spoke ROC config
IP-icap_oam OAM&P
Default GW: IP-mgnt default GW config roc-n (n=2...8)
L3-VLAN Dest IP: 0.0.0.0 IP Addr.: IP-roc_b
Management config Dest Mask: 0.0.0.0 Netmask: NM-roc
IP Addr.: IP-ipfm_L3_oam Gateway: Remote IP: IP-roc_a
Netmask: NM-oam IP-ipfm_L3_oam
VLAN: ID-oam RT-ROC Default GW config
RT-ROC config Dest IP: 0.0.0.0
roc-m (m=1...8) Dest Mask: 0.0.0.0
Faceplate Port IP Addr.: IP-roc_a Gateway: IP-roc_a
FE1/FE2/GbE1/GbE2 Netmask: NM-roc
Remote IP: IP-roc_b
GSI: IP-gsi IPFM: IP-mgnt
Mgmnt-subnet; Net mask: NM-gsi
L3-VLAN-mgnt: IP-ipfm_L3_oam ICAP: IP-icap_oam
Management-VLAN (ID-oam);
Network mask: NM-oam
ICAP: IP-roc_a COMDAC: IP-roc_b
ROC-subnet; Network mask: NM-roc
Note: The transport network is intentionally not shown here
Inband Management via IPFM uplink port

In the next example the ICAP again is operating in controlled mode. But in this
scenario the management information is transported in an inband management channel
via an uplink port of the IPFM. A Layer 3 VLAN has to be provisioned on the router,
the IPFM and the ICAP.
....................................................................................................................................................................................................................................
8-2 363-211-555
Router IPFM ICAP COMDAC

OAM&P config
Management Port IP Addr.: IP-icap_oam
Static route config
Netmask: NM-oam
Dest IP: IP-roc_b
VLAN: ID-oam
Dest Mask: NM-roc
Gateway:
IP_icap_oam
IP
GSI config Spoke
IP Addr.: IP-gsi OAM&P ROC config
Netmask: NM-mgnt default GW config roc-n (n=2...8)
L3-VLAN
Netmask: NM-gsi
IP:
Netmask: NM-oam
VLAN-IP: IP-rout_vlan
VLAN:
Default GW: IP-mgnt Dest IP: 0.0.0.0 IP Addr.: IP-roc_b
Management config Dest Mask: 0.0.0.0 Netmask: NM-roc
GSI IP Addr.: IP-ipfm_L3_oam Gateway: IP-rout_vlan Remote IP: IP-roc_a
Netmask: NM-oam
VLAN: ID-oam RT-ROC
ID-oam
IP-rout_sub
RT-ROC config Default GW config

roc-m (m=1...8) Dest IP: 0.0.0.0
IP Addr.: IP-roc_a Dest Mask: 0.0.0.0
Faceplate Port Netmask: NM-roc Gateway: IP-roc_a
FE1/FE2/GbE1/GbE2 Remote IP: IP-roc_b
GSI: IP-gsi Router: IP-rout_sub
Mgmnt-subnet;
Net mask: NM-gsi
L3-VLAN-mgnt: IP-ipfm_L3_oam
Router: IP-rout_vlan ICAP OAM&P: IP-icap_oam
Management-VLAN (ID-oam);Network mask: NM-oam
Management via ICAP uplink port

The following scenario shows an ICAP in stand-alone mode. In this case the uplink
port on the ICAP is used for management traffic. A management VLAN has to be
provisioned on the Router and on the ICAP.
....................................................................................................................................................................................................................................
363-211-555 8-3
Router ICAP COMDAC

Faceplate port FE1
Static route config
Dest IP: IP-roc_b
Dest Mask: NM-roc OAM&P config
Gateway: IP Addr.: IP-icap_oam
IP_icap_oam Netmask: NM-oam
VLAN: ID-oam
GSI config
IP Addr.: IP-gsi OAM&P ROC config
Netmask: NM-mgnt default GW config roc-n (n=2...8)
Netmask: NM-gsi
IP:
Netmask: NM-oam
VLAN-IP: IP-rout_vlan
VLAN:
Default GW: IP-mgnt Dest IP: 0.0.0.0 IP Addr.: IP-roc_b
Dest Mask: 0.0.0.0 Netmask: NM-roc
GSI Gateway: IP-rout_vlan Remote IP: IP-roc_a
RT-ROC
ID-oam
IP-rout_sub
RT-ROC config Default GW config

roc-m (m=1...8) Dest IP: 0.0.0.0
IP Addr.: IP-roc_a Dest Mask: 0.0.0.0
Netmask: NM-roc Gateway: IP-roc_a
Remote IP: IP-roc_b
GSI: IP-gsi Router: IP-rout_sub
Mgmnt-subnet;
Net mask: NM-gsi
Router: IP-rout_vlan ICAP : IP-icap_oam
Management-VLAN (ID-oam);
Network mask: NM-oam
....................................................................................................................................................................................................................................
8-4 363-211-555
Appendix A: Product conformance
Overview
...................................................................................................................................................................................................................................
Purpose
This section provides the European conformity (CE) statements, additional international
conformity statements, and the eco-environmental statements that apply to the
AnyMedia ® Access System.
Note that in regions such as the European Union, the statements that are required are
determined primarily by national or multi-national regulations. However, in some
regions, contact terms determine which statements are required.
The presence of the statement indicates that the product does comply with that
statement wherever it is required to do so.
Contents
European conformity (CE) statements A-2

Additional international conformity statements A-5
Eco-environmental statements A-6
...................................................................................................................................................................................................................................
363-211-555 A-1
Product conformance
European conformity (CE) statements

...................................................................................................................................................................................................................................
Overview
The statements that follow are the European conformity (CE) statements that apply to
the AnyMedia ® Access System.
Informal compliance statement
Language Statement
English Hereby, Alcatel-Lucent declares that this
equipment is in compliance with the
essential requirements and other relevant
provisions of Directive 89/336/EEC and
73/23/EEC.
Suomi Alcatel-Lucent vakuuttaa täten, että laite,
jonka dokumentaatio on tässä julkaisussa,
on direktiivin 89/336/ETY, 73/23/ETY
oleellisten vaatimusten ja tämän
direktiivin muiden ehtojen mukainen.
Nederlands Hierbij verklaart Alcatel-Lucent dat de in
deze publicatie beschreven apparatuur in
overeenstemming is met de essentiële
eisen en de andere relevante bepalingen
van Richtlijn 89/336/EEG, 73/23/EEG.
Français Par la présente, Alcatel-Lucent déclare que
l’appareil décrit dans cette publication est
conforme aux exigences essentielles et aux
autres dispositions pertinentes de la
directive 89/336/CEE, 73/23/CEE.
Svenska Härmed intygar Alcatel-Lucent att den
utrustning som behandlas i denna
dokumentation står i överensstämmelse
med de väsentliga egenskapskraven och
övriga relevanta bestämmelser i direktiv
89/336/EEG, 73/23/EEG.
Dansk Alcatel-Lucent erklærer herved, at det
udstyr, der er dokumenteret i denne
publikation, overholder de grundlæggende
krav og øvrige relevante forskrifter i
Europa-Parlamentets og Rådets direktiv
89/336/EOEF, 73/23/EOEF.
...................................................................................................................................................................................................................................
A-2 363-211-555
Product conformance European conformity (CE) statements
Language Statement
Deutsch Hiermit erklärt Alcatel-Lucent die
Übereinstimmung des in dieser
Publikation dokumentierten Gerätes mit
den grundlegenden Anforderungen und
den anderen relevanten Festlegungen der
Richtlinie 89/336/EWG und 73/23/EWG.
Ελληνικα ΜΕ ΤΗΝ ΠΑΡΟΥΣΑ Alcatel-Lucent
∆ΗΛΩΝΕΙ ΟΤΙ ΣΥΜΜΟΡΦΩΝΕΤΑΙ
ΠΡΟΣ ΤΙΣ ΟΥΣΙΩ∆ΕΙΣ ΑΠΑΙΤΗΣΕΙΣ
ΚΑΙ ΤΙΣ ΛΟΙΠΕΣ ΣΧΕΤΙΚΕΣ
∆ΙΑΤΑΞΕΙΣ ΤΗΣ Ο∆ΗΓΙΑΣ 89/336/EOK,
73/23/EOK.
Italiano La Alcatel-Lucent dichiara che le
apparecchiature descritte nella presente
pubblicazione sono conformi ai requisiti e
alle indicazioni contenute nella direttiva
89/336/CEE, 73/23/CEE.
Español Por la presente, Alcatel-Lucent declara
que el equipo descrito en esta publicación
cumple los requisitos básicos y demás
disposiciones pertinentes de la Directiva
89/336/CEE, 73/23/CEE.
Português A Alcatel-Lucent declara por este meio
que todo o equipamento documentado
nesta publicação se encontra em
conformidade com os requisitos essenciais
e outras condições relevantes da Directiva
89/336/CEE, 73/23/CEE.
Declaration of conformity
Hereby, Alcatel-Lucent declares that this equipment is in compliance with the essential
requirements and other relevant provisions of the following Directive:
• Council Directive 89/336/EEC and 73/23/EEC, as amended by Directive
93/68/EEC, on the approximation of the laws of the Member States relating to
electromagnetic compatibility and electrical equipment designed for use within
certain voltage limits.
This equipment is tested and conforms with the essential requirements for protection of
health and the safety of the user and any other person and electromagnetic
compatibility.
Conformity is indicated by the CE marking affixed to the product. For more
information regarding CE marking and Declaration of Conformity (DoC), please
contact your local Alcatel-Lucent customer service organization.
...................................................................................................................................................................................................................................
363-211-555 A-3
Product conformance European conformity (CE) statements
Intended use
This equipment shall be used only in accordance with its intended use, according to the
installation and maintenance instructions contained in this documentation. Any other
use or modification is prohibited.
For further restrictions that apply in some regions and/or countries, please contact your
local Alcatel-Lucent representative.
Technical documentation
The technical documentation required by the Conformity Assessment procedure is kept
at the Alcatel-Lucent location which is responsible for this product. For more
information, please contact your local Alcatel-Lucent representative.
...................................................................................................................................................................................................................................
A-4 363-211-555
Product conformance
Additional international conformity statements

...................................................................................................................................................................................................................................
Overview
The AnyMedia ® LAG 200 Shelf complies with the following additional international
conformity statements.
VCCI Class A Statement

The AnyMedia ® LAG 200 Shelf complies with Class A ITE.
Translation:
This is a Class A product.
In a domestic environment this product may cause radio interference, in which case the
user may be required to take corrective actions. VCCI-A
ENSS022/CISPR22 Class A Warning Statement

This is a Class A product. In a domestic environment this product may cause radio
interference, in which case the user may be required to take adequate measures.
...................................................................................................................................................................................................................................
363-211-555 A-5
Product conformance
Eco-environmental statements
...................................................................................................................................................................................................................................
Overview
The statements that follow are the eco-environmental statements that apply to the
Packaging collection and recovery requirements

Countries, states, localities, or other jurisdictions may require that systems be
established for the return and/or collection of packaging waste from the consumer, or
other end user, or from the waste stream. Additionally, reuse, recovery, and/or recycling
targets for the return and/or collection of the packaging waste may be established.
For more information regarding collection and recovery of packaging and packaging
waste within specific jurisdictions, please contact the Alcatel-Lucent Services -
Environmental Health and Safety organization.
For installations not performed by Alcatel-Lucent, please contact the Alcatel-Lucent
Customer Support Center at:
Technical Support Services
Alcatel-Lucent
Within the United States: 1 866 LUCENT8 (866 582 3688), prompt 1
From all other countries: +1 630 224 4672, prompt 2
Recycling / take-back / disposal of products and batteries

Electronic products and batteries bearing or referencing the symbols shown below shall
be collected and treated at the end of their useful life, in compliance with applicable
European Union and other local legislation. They shall not be disposed of as part of
unsorted municipal waste. Due to materials that may be contained in the product and
batteries, such as heavy metals, the environment and human health may be negatively
impacted as a result of inappropriate disposal.
Note 1: For electronic products put on the market in the European Union, a solid bar
under the crossed-out wheeled bin indicates that the product was put on the market
after 13 August 2005.
Note: If a solid bar appears under the crossed

out wheelie bin, it signifies the product was put
on the EU market on or after 13 August 2005.
...................................................................................................................................................................................................................................
A-6 363-211-555
Product conformance Eco-environmental statements
Note 2: For batteries put on the market in the European Union, a chemical symbol Hg
(mercury), Cd (cadmium), or Pb (lead), or a combination of those symbols, beneath the
cross-out wheeled bin indicates that the battery contains the corresponding heavy
metals.
Moreover, in compliance with legal requirements and contractual agreements, where

applicable, Alcatel-Lucent will offer to provide for the collection and treatment of
Alcatel-Lucent products bearing the logo at the end of their useful life, or products
displaced by Alcatel-Lucent equipment offers.
For information regarding take-back, recycling, or disposal of equipment by
Alcatel-Lucent or for equipment take-back requests, visit the Alcatel-Lucent Take-Back
web page (http://www.alcatel-lucent.com/product_takeback) or contact Alcatel-Lucent
Takeback Support at [email protected]. For technical information on
product treatment, consult the Alcatel-Lucent Recycling Information web page
http://www.alcatel-lucent.com/product_recycling.
Material content compliance

European Union (EU) Directive 2002/95/EC, ″Restriction of the use of certain
Hazardous Substances″ (RoHS), restricts the use of lead, mercury, cadmium,
hexavalent chromium, and certain flame retardants in electrical and electronic
equipment.
This Directive applies to electrical and electronic products placed on the EU market
from 1 July 2006, with various exemptions, including an exemption for lead solder in
network infrastructure equipment.
Alcatel-Lucent products shipped to the EU from 1 July 2006 will comply with the
RoHS Directive.
...................................................................................................................................................................................................................................
363-211-555 A-7
Glossary
....................................................................................................................................................................................................................................
Numerics
1N / 3N
Formats of packs which define the height according to the One GPN standard hardware
requirement.
10Base-T
IEEE 802.3 standard for Ethernet transmission over unshielded twisted pair.
100Base-T
IEEE 802.3 standard for Ethernet transmission over unshielded twisted pair. 100Base-T
or Fast Ethernet, supports data transfer rates of 100 Mbps.
100Base-FX
Version of Fast Ethernet (100 Mbps) over optical fiber.
....................................................................................................................................................................................................................................
A a-wire
One of the two wires of a twisted a/b copper pair. The a/b copper pairs are used for
subscriber lines connected for example with Z interfaces. The a-wire is sometimes called
tip-wire.
AC
Alternating Current
Active pack
The IPFM performing the operational work. The active pack can reside in the preferred
slot or the protected slot.
Active status condition message

Each status condition message contains access identifier, condition type, condition effect,
and condition description. Currently active status conditions are listed chronologically
(see also status condition).
ADM
Add/Drop Multiplexer
....................................................................................................................................................................................................................................
363-211-555 GL-1
Glossary
Administrative State
A nominal service state typically set by the operator. The administrative state is
non-volatile data. It survives system crashes when saved to NVDS.
ADSL
Asymmetric Digital Subscriber Line
ADSL (Full-rate ADSL)

Asymmetric digital subscriber line - A method of data transmission over unloaded copper
loops. The data rate transmitted toward the end user is typically much higher (e.g.
6.144 Mbps) than the data rate transmitted by the end user (e.g. 640 kbps).
ADSL subscriber
Asymmetric digital subscriber line - The subscriber lines that terminate on ADSL APs.
ADSL-lite (Universal)
A version of asymmetric digital subscriber line (ADSL) that is less expensive than
full-rate ADSL and that operates at a lower bit rate than full-rate ADSL. This version of
ADSL is specified in ITU-T G.992.2.
ADSL2/ADSL2+
ADSL2 and ADSL2+ are two new standards for asymmetric digital subscriber line
(ADSL) technology specified in ITU-T G.992.3 to ITU-T G.992.5. These standards are
specifically designed to improve the rate and reach of ADSL largely by achieving better
performance on long lines in the presence of narrowband interference. ADSL2 achieves
downstream and upstream data rates of about 12 Mbps and 1 Mbps respectively,
depending on loop length and other factors. ADSL2 accomplishes this by improving
modulation efficiency, reducing framing overhead, achieving higher coding gain,
improving the initialization state machine, and providing enhanced signal processing
algorithms. As a result, ADSL2 mandates higher performance for all standard-compliant
devices.
ADSLAP
Asymmetric Digital Subscriber Lineapplication pack (ATU-C) that transmits and receives
a broadband signal to/from ATU-R customer premises equipment (CPE), and if so
connected, diplexes a voice frequency signal on to the same tip and ring pair carrying
the broadband signal.
AID
Access identifier - AID is the address that is used to identify the physical or logical
entity (or entities) within a network element to which the command applies. It has the
format of a unique component identifier followed by hierarchical addresses of
components. For example, subap-{2}-{4} is an object representing the application pack
in slot #4 of the AnyMedia Subshelf #2.
AN
Access Network
ANSI
American National Standards Institute
...................................................................................................................................................................................................................................
GL-2 363-211-555
Glossary
AnyMedia ® Access System

The AnyMedia ® Access System is an access network element which supports various
narrowband, ATM xDSL and IP services, digital as well as analog.
AnyMedia ® ETSI V5 Shelf

The AnyMedia Mainshelf consists of a metal mechanical structure that serves to guide
and fasten packs, locate and mount a multi-layer backplane. It allows mounting into
supporting structures such as racks and provides an interface for internal and external
connections. One AnyMedia Mainshelf houses up to 16 physical E1 links and up to 16
subscriber distribution application packs.
AnyMedia ® LAG 1900 Shelf

The AnyMedia ® LAG 1900 Shelf is a specific LAG Shelf. It contains seven 1N high
slots for 1N-sized common packs and 17 3N high slots for common packs (COMDAC,
CIU, IPFM, AFM) and application packs with subscriber interfaces. The AnyMedia ®
LAG 1900 Shelf can house narrowband services, ATM xDSL services and/or IP-based
services.

The AnyMedia LAG 200 Shelf consists of a high speed IP spoke architecture that serves
up to three IP-based application packs for supporting Ethernet, VDSL and VoIP services.
The shelf provides three 3N high slots (one controller and 2 APs) and three 1N double
wide slots. The LAG 200 Shelf with door could be deployed in LAG 200 cabinet as well
as in the customer supplied cabinet with 19”, ETSI or 23” racks. It provides interfaces
for internal and external connections and operates in controlled mode with combined
uplink.

The AnyMedia ® LAG 4300 Shelf is a double row shelf. The upper row contains six 1N
high slots and 22 3N high slots. The lower row contains 24 3N high slots. The 1N high
slots are designated for circuit packs with network interfaces, while certain of the 3N
high slots are designated for control (COMDAC, CIU, ..) and the other 3N high slots are
designated for circuit packs with subscriber interfaces.
AnyMedia LAG 4300 System

The AnyMedia LAG 4300 System is housed in an EMI protected indoor cabinet and can
be delivered in three configurations equipped with
• one AnyMedia ® LAG 4300 Shelf
• two AnyMedia ® LAG 4300 Shelves
• two AnyMedia ® LAG 4300 Shelves and two AnyMedia ® ETSI V5 Shelves.
The Power Filter Units, Passive Clock Distributions, Ringing Filter Units, Alarm
Connection Panels and fan units are also housed in the indoor cabinet.
AnyMedia LAG Shelf

The term AnyMedia LAG Shelf is generally used for an AnyMedia shelf with a high
capacity backplane, independently of the physical design of the shelf. It houses
COMDAC(s), CIU/CTU, AFM(s) IPFM(s) and application packs.
For information about the number of available slots refer to “Configuration
considerations for the different AnyMedia ® shelf types” (p. 2-5).
...................................................................................................................................................................................................................................
363-211-555 GL-3
Glossary
AP
Application pack - A 3N-sized pack which is located in any of the AP slots of the
APOG
Applications, Planning, and Ordering Guide
Apparatus code (APP)

The apparatus code is an 8-byte item of ASCII information stored in the nonvolatile data
storage (NVDS) of a pack (for example LPZ600, LPA633,...). It is a unique identifier
which specifies the function of the pack.
Application pack (AP)

A circuit pack which is located in any of the AP slots and supports subscriber interfaces
for certain services. Some examples for application packs are LPZ600, LPA633,
LPV417.
Authentication
Process used to verify the integrity of transmitted data, especially that of a message.
Availability
The probability that a system is in operable state at a given instant in time.
....................................................................................................................................................................................................................................
B b-wire
One of the two wires of a twisted a/b copper pair. The a/b copper pairs are used for
subscriber lines. The b-wire is sometimes called ring-wire.
BORSCHT
BORSCHT is an abbreviation for interface functions provided by Z ports for POTS.
• Battery (Subscriber loop feeding)
• Overvoltage/Overcurrent protection
• Ringing (Ringing signal provided for subscriber’s terminal)
• Supervision (Loop signaling)
• Coding/Decoding (PCM)
• Hybrid (2- to 4-wire conversion)
• Test (provide a test access to subscriber’s line and line circuit).
Bridge
A network layer device that passes packets between two or more network segments that
use the same data link communications protocol (OSI layer 2). The network segments
appear as one segment to protocol levels higher than the data link layer.
Bridging
Port and subscriber line are connected during a test session.
...................................................................................................................................................................................................................................
GL-4 363-211-555
Glossary
....................................................................................................................................................................................................................................
C CE
Communauté Européenne
Circuit pack
A general term for any plug-in unit that is determined > to be inserted into the slot of a
shelf, regardless of the slot size (1N-sized or 3N-sized) and the functionality. Common
packs and application packs are subsets of circuit packs.
Circuit testing
Verifies the ability of an AP port to provide proper transmission and signaling.
CIT
Craft Interface Terminal - The Craft Interface Terminal is used to enter and receive
messages. A CIT emulation is running on the GSI.
CIT interface
Interface for the Craft Interface Terminal - A serial EIA-232C interface (9-pin Dsub) on
the faceplate of the communication interface unit (CIU/CTU) where a craft interface
terminal (CIT) or a graphical system interface (GSI) is connected to the AnyMedia ®
Access System.
CIU
Communication interface unit - This is a pack used to provide several OAM&P interface
terminations to the AnyMedia ® Access System.
CKC
Customer key code
CL channel
Used to transfer information concerning operation, maintenance and
activation/deactivation of the access transmission system (ATS) in both directions
between the LT and the NT.
CLEI
Common language equipment ID code - The CLEI is a 10-character code assigned by
Bellcore identifying each pack. The CLEI information relates to the function of the pack,
the condition of use, the source document used in creating the CLEI code etc. If two
packs have the same first seven characters in the CLEI code, then the packs are
electrically and mechanically interchangeable. Knowledge of CLEI is useful in planning,
engineering and provisioning.
CLI
Command line interpreter
CLIP
Calling line identification presentation - A supplementary service which provides the
called party with the possibility of receiving identification of the calling party.
CLIR
Caller ID restriction
...................................................................................................................................................................................................................................
363-211-555 GL-5
Glossary
CN
Change Notification
CO
Central Office
Collocation
Grouping entities in the same physical location.
Comcode
The comcode is a unique nine-digit code with the ECI being represented by the digits 2
through 7. The comcode is used by various Alcatel-Lucent organizations for the ordering
of components.
COMDAC
Common data and control - Pack which provides the central control and transmission
fabric for the AnyMedia ® Access System. The COMDAC supports multiple system
applications, including V5.x switched services and analog and digital leased lines (ALL
and DLL) and a variety of application packs.
Common pack
A circuit pack providing system functionality that is not limited to a specific application
like POTS or ADSL. All circuit packs that are not defined as application packs, are
common packs. Some examples for common packs are COMDAC, CIU, AFM, RGUs.
Configuration management
Consists of a set of functions to exercise control over elements in the network, including
initialization, parameter setting, starting and stopping, and collection of information
about the configuration.
Controlling entity
A controlling entity has a control relationship to another entity where the operational
condition of the other (controlled) entity depends on the operational condition of the
entity concerned.
CPE
Customer premises equipment - CPE covers the subscriber’s installation and the
subscriber’s terminal.
CR
Critical
CRC-4 procedure
Cyclic redundancy check-4 procedure - A multiplication/division process, specified in
ITU-T G.704, to provide additional protection against simulation of the frame alignment
signal and capability for enhanced error monitoring.
Cross-connection
A term for a logical association between two objects, for example between a subscriber
port and a network interface. A physical cross-connection may additionally be
established in the case of a network interface where bandwidth allocation is done on a
...................................................................................................................................................................................................................................
GL-6 363-211-555
Glossary
provisioning basis.
CTU
Craft test unit
Customer key code

The provisionable customer key code defines which customer specific settings are used
by the AnyMedia ® Access System.
....................................................................................................................................................................................................................................
D DC
Direct Current
DDI
Direct dialing in
Degrowth
The removal of circuit packs or traffic from a system via a provisioning operation (may
be accompanied by the physical removal of associated equipment, but this is not
required).
Device
Any electrical part (IC, diode, capacitor, resistor, etc.) with distinct electrical
characteristics. This term is used interchangeably with component.
DHCP
Dynamic Host Control Protocol (Defined in RFC 1541)
DHCP allows IP addresses to be assigned in three ways:
1) Manual Allocation: The network administrator keeps complete control over addresses
by specifically assigning them to clients.
2) Automatic Allocation: The DHCP server permanently assigns an address from a pool
of addresses.
3) Dynamic Allocation: The DHCP server assigns an address to a DHCP client for a
limited period of time.
Distance-to-open
For deciding whether a line is broken (open), a distance-to-open measurement is to be
implemented. Such a measurement could be based upon several techniques: capacitance
or impedance measurement, or even pulse-reflection. TAP10x may produce parameters,
with which the operator can decide on the location of the cable-fault (based on the
operator’s knowledge of the applied cable type).
DoS
Denial of service.
Downlink, uplink
In the AnyMedia ® IP subsystem, any interfaces carrying IP traffic which are oriented
towards the network are termed uplinks. Those interfaces which are oriented towards the
subscriber (end-user) are termed downlinks. Typical uplinks are the GbE and FE
interfaces of the IPFM. Typical downlinks are the VDSL lines. Whether a link is a
downlink or uplink may depend on the relative viewpoint: From an AP point of view the
...................................................................................................................................................................................................................................
363-211-555 GL-7
Glossary
baclplane spokes are uplinks. From an IPFM point of view the same spokes are
downlinks.
Download
A binary data transfer from the GSI to the AnyMedia ® Access System.
Downstream, upstream
Those terms denote a direction relative to the network or the subscriber. Upstream is
towards the network, downstream is towards the subscriber.
Downtime
Used to describe the time during which a system is not available for service. In
engineering applications downtime is associated with unavailability.
Downtime per port

Downtime, in minutes per year, for a single bidirectional path terminating on an
interface port on an add/drop multiplexer or a digital cross connect system. Any service
interruption longer than 50 milliseconds contributes to this measure.
Drop
See subscriber loop.
Drop testing
Checks for opens, shorts, leakages to ground, foreign voltages, or other faults on the
subscriber loop.
DS1
DS1 is a GR-303-like format
DSCP
Differentiated Services Code Point
DSP
Digital signal processor
DTE
Data Terminal Equipment
DTP500
Communication interface unit (CIU)
Duplex mode
A facility protection scheme in which two identical facilities (packs or feeders) are
installed on a shelf; one is running in the active mode, the other is in the standby mode.
The standby facility takes over when the active one fails or on an external command.
Such a take-over (″protection switch″) guarantees that a facility failure does not disrupt
the services. In the duplex IPFM context ‘Duplex Mode’ means, that the Protection Slot
is provisioned in the IPFM data base to contain an IPFM.
...................................................................................................................................................................................................................................
GL-8 363-211-555
Glossary
....................................................................................................................................................................................................................................
E E1
E1 is the standard acronym for the 2.048-Mbps interface defined in the ITU standards
G.703/G.704.
ECI
Equipment catalog item - Equipment catalog item code is a 6-character code assigned by
Bellcore identifying each pack. This code corresponds to the bar-coded label on the
faceplate of the pack, and is uniquely equivalent to the CLEI code - for a given CLEI
there is a unique ECI. It is used internally in the databases of external inventory systems
for cataloging of equipment and is useful in accounting and inventory control.
Edge switch
A switch that is located at the meeting point between the access and the core network.
EIA-232C
American Standard for Serial Interface (the same as EIA-RS-232C; similar to V.24)
EIDR
Enhanced inventory data record - Enhanced inventory data record is a set of parameters
that are stored in the non-volatile memory of packs. The parameters relate to the
function performed by the pack, the manufacturing information, ordering information etc.
that is of importance in provisioning a new service, maintaining the service, and in
restoring the service quickly in event of a failure.
EMC
Electromagnetic Compatibility
End of life
The instant when a device parameter reaches a specified failure threshold. The failure
threshold is device-dependent. For instance, an aluminum electrolytic capacitor reaches
its end of life when its equivalent series resistance (ESR) exceeds twice its initial value.
EOC
Embedded Operations Channel
Equipment pair
The equipment pair of the TAP-B interface consists of the 2 wires towards the customer
premises equipment (outward direction).
ES
Errored Seconds
ESIM
Ethernet subscriber interface module (LPE408)
ETS
European Telecommunication Standard
ETSI
European Telecommunication Standards Institute
...................................................................................................................................................................................................................................
363-211-555 GL-9
Glossary
External interface
Any operations or user interface system connected locally or remotely to the AnyMedia ®
Access System. For example: CIT, GSI, EMS.
....................................................................................................................................................................................................................................
F Facility pair
The facility pair of the TAP-B interface consists of the 2 wires towards the application
pack circuitry (inward direction).
Facility protection
The capability for a system to choose which signal from two facilities to pass along to
the internal, unprotected transmission paths. A system switches from one facility to the
other, for example, when the facility being used fails or when an administrator issues an
OAM&P command.
Far end
The transmission termination or network element terminating the remote end of a feeder
connected to the system. Examples include the edge switch and another AnyMedia shelf
within a daisy chain. The far end is also referred to as remote end.
Fault management
Consists of a set of functions, such as testing, that enable the detection, isolation, and
correction of abnormal operation of the telecommunications network and its
environment.
FDI
Feeder Distribution Interface
FE
Fast Ethernet
FFU
Fan Filter Unit
FITL
Fiber In The Loop
Forced mode
Refers to the mode of changing to administrative primary service state OOS. In forced
mode the resources are freed immediately and the administrative primary service state
OOS is entered.
Forward direction
The direction followed by monitored user cells. Unlike the definition of upstream and
downstream direction, the forward and backward directions are relative to a reference
point (e.g., the point where a failure occurs).
FQDN
Fully Qualified Domain Name
...................................................................................................................................................................................................................................
GL-10 363-211-555
Glossary
FTP
File Transfer Protocol
Full duplex
Refers to the transmission of data in two directions simultaneously.
Full split
With full-split test access, transmission is interrupted in both the transmit and receive
directions at the test access point and the tester is allowed to inject and look at the
transmitted and received signals both in the equipment (towards the end-customer) and
in the facility (towards the network) directions simultaneously.
....................................................................................................................................................................................................................................
G GbE
Gigabit Ethernet
GBIC
Gigabit Interface Converter
GND
Ground - Synonym for electrical potential of 0V.
GSI
Graphical System Interface - A user friendly front-end for communicating with a system.
In the AnyMedia ® Access System the GSI is installed on a Windows based Personal
Computer and used for entering and receiving TL1 (Transaction Language 1) messages
for narrowband applications and SNMP messages for ATM xDSL and IPFM applications.
The GSI provides support for managing the AnyMedia ® Access System in the following
functional areas:
• Configuration management
• Fault management
• Performance management
• Security management
• Inventory management.
....................................................................................................................................................................................................................................
H Half simplex
Refers to the transmission of data in just one direction at a time.
Half split
With half-split test access, transmission is interrupted in both the transmit and receive
directions at the test access point, exactly as in full-split access. However, the tester is
allowed to inject and look at the transmitted and received signals either in the equipment
(towards the end-customer) direction or in the facility (towards the network) direction,
but not in both directions simultaneously.
High-impedance state
This state refers to the Z interface and implies that the physical Z port circuit is
disabled. Consequently no feeding current can flow from the Z interface to the
...................................................................................................................................................................................................................................
363-211-555 GL-11
Glossary
subscriber’s terminal, no loop scanning will be performed and no AC signal transmission

is possible.
Hold-up time
The time during which a power supplies output voltage remains within specification
following the loss of input power.
Hook flash
Hook flash is a signal of POTS. A hook flash signal is a short interruption of
subscriber’s loop, which is generated at subscriber’s terminal. Hook flash signals are
used to request additional service features (for example establishing a three party
telephone conference).
HST
Hold service tone
....................................................................................................................................................................................................................................
I ICAP
IP COMDAC application pack
ICC
Interchangeability code - The ICC is of the form Sm:n, where ″m″ is the issue number
and ″n″ is the series number. This is used to accurately indicate the interchangeability
among packs with the same pack name and apparatus code, but different manufacturing
versions. In general, a pack can be replaced by another pack that has the same apparatus
code and the same issue number regardless of the series number.
ICV
Integrity check value.
ID
Identification
IEEE
Institute of Electrical and Electronic Engineers
IGMP
Internet group management protocol
IIT
Incoming identification tone
IM
Installation Manual
Inbound, outbound
From a VoIP AP perspective outbound signaling messages are messages sent towards the
network. In traditional telephony those messages are termed outgoing messages. Inbound
messages are messages received from the network. In traditional telephony those
messages are termed incoming messages.
...................................................................................................................................................................................................................................
GL-12 363-211-555
Glossary
Incoming, outgoing
In the traditional call context of a local exchange (LE), incoming calls are calls coming
in from the network and being destined for a subscriber connected to this LE directly or
via an access node (AN). Correspondingly, outgoing calls are calls initiated by
subscribers being connected to the LE directly or via an AN and being forwarded
towards the trunk network.
Inrush current
Inrush current is the current flowing at the moment when the power is switched on.
Installation time
The period of time beginning when the transfer of software to the peripheral pack starts.
The interval ends at the point when the transfer of the peripheral image to the pack is
completed for both peripheral processors and field programmable gate array (FPGAs).
Peripheral SW version switch over is not included.
Inventory
Inventory is the summary of data stored on a pack in the NVDS during manufacturing
which is used to identify the pack and its functionality.
Inventory management
Consists of a set of functions to track, report, and ensure adequate supplies of
equipment.
Inward direction
See facility pair.
IP
Internet Protocol
IP Subsystem
IP subsystem is the part of the system to provide IP services. It consists of the IPFM,
which is the controller of the IP subsystem, hosting the IP feeder interfaces also, the IP
application packs and the associated parts of the backplane.
IP-AFM
IP ATM feeder multiplexer
IPFM
IP forwarding module
IS
In Service
ISP
Internet Service Provider
IT
IT is the synonym for a power distribution system having no direct connection to earth,
the exposed conductive parts of the electrical installation are connected to a local earth.
...................................................................................................................................................................................................................................
363-211-555 GL-13
Glossary
ITU
International Telecommunication Union
....................................................................................................................................................................................................................................
J Jabber
In this document Jabber is defined as condition where any packet exceeds 20 ms. The
allowed range to detect jabber is between 20 ms and 150 ms.
Jitter
Short-term noncumulative variations of the significant instants of a digital signal from
their ideal positions in time.The most significant form of jitter arises from imperfections
in the circuitry, for example quantizing distortions in phase locked loops (PLL).
....................................................................................................................................................................................................................................
L LACP
Link aggregation control protocol.
LAG
Line Access Gateway
LAN
Local Area Network
Latency
The minimum amount of time it takes for a token to circulate around the LAN token
ring or FDDI ring in the absence of a data transmission. Latency is selected when
provisioning data service in the AnyMedia ® Access System.
LBO
Lightguide Buildout; the LBO is an optical attenuator used between ATM circuit packs
in an ATM switch or multiplexer and the AFMOs in an AnyMedia shelf, or between
separate AFMOs in multiple AnyMedia shelves in a daisy chain. LBO guarantees the
proper signal level.
LCS
Local Customer Support
LE
Local Exchange
LED
Light Emitting Diode
Load
The total number of call attempts offered to a telecommunication system during a given
interval of time.
Load set
The load image plus the site-dependent configuration data.
...................................................................................................................................................................................................................................
GL-14 363-211-555
Glossary
Local login
Login into the AnyMedia ® Access System via the CIT or External System LAN 10BaseT
interface from the collocated GSI or dumb terminal.
LOF
Loss of frame - A LOF condition is declared when an out of frame (OOF) condition
persists for t seconds.
LOP
Loss of pointer - A LOP is declared when a valid pointer can not be obtained using the
pointer interpretation rules for SONET/SDH.
LOS
Loss of signal
....................................................................................................................................................................................................................................
M MAC
Media Access Control
Mainshelf
See AnyMedia Mainshelf.
MDF
Main Distribution Frame
MEA
Mismatch of Equipment
Megaco
Media gateway control protocol
MGCP
Media gateway control protocol according to RFC3435
MIB
Management information base - Declaration of a collection of objects that defines the
network or network element for a given interface protocol. For example, there is a MIB
defined for access using the simple network management protocol (SNMP) and a
different MIB defined for access using the protocol of the GR-303 Embedded Operations
Channel (EOC).
MJ
Major
MMH
Media monitor host
MN
Minor
...................................................................................................................................................................................................................................
363-211-555 GL-15
Glossary
Monitoring
The operator can hear to the subscriber while the circuit is still operational and in
bridged state. Additionally a speech connection can be established to allow to talk to the
customer.
MSG
Message
....................................................................................................................................................................................................................................
N NAM
Navis AnyMedia Element Management System - Represents computing facilities,
specialized software and data storage facilities used to administer and maintain multiple
network elements (NEs) distributed over a wide geographical area from a centralized
location. Communication in both directions is accomplished via TL1 messages.
NCP
Network connection point - NCP is the point at subscriber site on which subscriber’s
installation and subscriber’s line are connected.
NE
Network Element
NE name
The network element (NE) name is a unique provisioned name given to an AnyMedia
shelf. This name is identified by the GSI as the site ID.
Non-revertive mode
Means, that a certain protected working system resource which has become faulty and
thus caused a switch to or replacement by another resource is NOT reused automatically
as working resource if the (temporarily) faulty resource returns back to operation.
Instead of this the (former) protection resource is used further on as working resource. A
switch back may take place later on, but is independent from the recovery of the
(temporarily) faulty resource.
Non-service-affecting
Refers to a condition not affecting the service at the time it is detected.
NSA
Non-Service Affecting
NT
Network termination - The equipment that terminates the access transmission system on
the customer side. The most known network termination device is the NT1, that provides
only physical layer functionality. Other network termination devices with more
functionality are NT-N or NT-a/b.
NTP
Network Time Protocol
...................................................................................................................................................................................................................................
GL-16 363-211-555
Glossary
NVDS
Nonvolatile data storage - NVDS refers to that part of the database which is retained
even after a power failure, for example provision parameters.
NVPS
Nonvolatile program storage - NVPS refers to nonvolatile memory used to store the load
image.
....................................................................................................................................................................................................................................
O OAM&P
Operations, Administration, Maintenance, and Provisioning
Off-hook
In the off-hook state the telephone is picked up. The off-hook state indicates the busy
state.
On-demand tests
On-demand tests will be executed only by an operator TL1 command.
On-hook
In the on-hook state the telephone is not picked up. The on-hook state indicates the idle
state.
OOS
Out Of Service
Operational condition
Reflects whether the entity concerned is able to take over operation or not. It depends on
the service state.
Operational State
The operational state is determined autonomously by the system, often but not
exclusively relative to an administrative state. It is volatile and is re-determined in case
of recoveries.
Originating call
Originating call is the type of call initiated at the subscriber side.
OSPF
Open Shortest Path First
Outgoing
See Incoming.
Overload
Any load which is greater than the nominal load for which the system is required to
work without any performance degradation.
....................................................................................................................................................................................................................................
P Pack
See circuit pack
...................................................................................................................................................................................................................................
363-211-555 GL-17
Glossary
PCM
Pulse Code Modulation
Performance management
Consists of a set of functions to evaluate and report on the behavior of telecommunica-
tion equipment and the effectiveness of the network and/or network elements (NEs).
Planned Side Switch

Planned side switches are side switches that are jointly and carefully prepared by both
the active and protection IPFMs. I.e., there is some time to prepare the side switch in
order to accomplish it with a minimum impact on service. Events that cause planned
side switches include administrator command and software upgrade.
Platform
Items and functions in SW, HW and FW which are independent of the application.
PLC
Packet loss concealment
Port
Refers to the devices and functions built on or provided by a pack for one subscriber or
line interface; sometimes referenced as circuit.
POTS
Plain old telephone service - Analog telephony service via a copper pair.
PP
Point-to-Point
ppm
parts per million
PPPoE
Point-to-Point Protocol over Ethernet
Preferred slot
In the IPFM context, the Preferred Slot is the slot to be used for simplex mode. For
more details see “Pack placement in the different LAG Shelf types” (p. 2-11)
Profiles
Profiles are a common feature of systems that are managed using SNMP. A profile is a
fixed set of parameters with specific values that needs to be provisioned only once but
that can be used by any number of system entities of the same type.
Protected configuration
The protection pack is provisioned but may be faulty or moved to OOS by the operator.
Protection pack
The mate of the active pack. The protection pack can reside in the preferred slot or the
protection slot.
...................................................................................................................................................................................................................................
GL-18 363-211-555
Glossary
Protection slot
In the duplex IPFM context, the Protection Slot is the slot to be used by the second
IPFM in duplex mode. For more details see “Pack placement in the different LAG Shelf
types” (p. 2-11)
Protection status
An indication which reflects the actual state of the pack protection.
Protection switch
A switch of the service from the service pack to the protection pack. A protection switch
can be requested manually or driven by pack fault.
Protection switching
A reliability feature that causes service to switch to the backup equipment during faults
or testing.
Provisioning
The process of providing the system with parameters needed to realize a specific
customer and site specific behavior.
PSTN
Public Switched Telephone Network
....................................................................................................................................................................................................................................
Q QMS
Quality Management System
Quality of service (QoS)

An indicator of the performance of a transmission system on the Internet and other
networks. QoS is measured in transmission rate, error rates, latency, and other
characteristics.
....................................................................................................................................................................................................................................
R RAM
Random Access Memory
Regenerator
A transmission device between LT and NT. It enhances the transmission distance
between LT and the NT. The regenerator is remote powered from the LT and is powering
the NT. In ETR080 the number of regenerator between LT and NT is due to reasons of
powering limited to one.
Relationship
A dependence between two entities concerning the operational condition where the
operational condition of one entity depends on the operational condition of another
...................................................................................................................................................................................................................................
363-211-555 GL-19
Glossary
entity. The relationship may be of two types:

• hierarchical relationship according to the provisioning and resource view where upperlying
entities depend on underlying entities; that is underlying entities have to be provisioned
first. This also implies that the operational condition of an upperlying entity depends on the
operational condition of an underlying entity. If a pack is in a protected configuration, the
EQUIPMENT-layer entity has more than one relationship to underlying PACKS-layer
entities. The operational condition of the upperlying EQIPMENT layer entity is
″operational″, if at least one underlying entity is also ″operational″ and available for a
protection switch.
• control relationship not necessarily a relationship between entities of different layers as the
hierarchical relationship. It is a relationship of two entities where the operational condition
of one of the entities (controlled entity) depends on the operational condition of the other
(controlling) entity in such a way that the operational condition of the controlled entity is
only ″operational″ if the operational condition of the controlling entity is also
″operational″.
Remote login
Login into the AnyMedia ® Access System via LAN or External System LAN (over
TCP/IP DCN) from NAM or GSI.
RGP
Ringing Generator Pack - The RGP is a dual slot ringing generator pack, which may be
plugged in slot 40/41 and slot 42/43 of the AnyMedia LAG Shelf. The RGP in slot
40/41 drives ringing bus 0, while the RGP in slot 42/43 drives ringing bus 1.
Ringing protection mode

Two ringing sources (external or internal) on the AnyMedia LAG System are working in
active/active protection mode. Each one provides a ringing voltage to a separate ringing
bus. The power ringing is taken by the POTS APs from the ringing bus according to the
load sharing scheme. If one ringing voltage on one ringing bus fails, all POTS AP take
the ringing voltage from the remaining operational ringing bus.
Router
A LAN/WAN device that operates at OSI layers 1 (physical), 2 (data link), and 3
(network). Distinguished from a bridge by its capability to switch and route data based
upon network protocols such as IP.
RSTP
Rapid spanning tree protocol.
RTP
Real time protocol
RTU
Remote Test Unit - An RTU is a testing equipment for subscriber lines. An RTU-2 is
collocated to the system and performs test functions (application of test signals and
measurements) under the control of a test system controller. An RTU-1 is collocated to
the central office and not used in the 30 channel market.
...................................................................................................................................................................................................................................
GL-20 363-211-555
Glossary
....................................................................................................................................................................................................................................
S SA
Service Affecting
SC
Station clock - An external 2048 kHz synchronization signal, according to ITU-T G.703.
SCC
Serial communication controller - Part of the communication processor module of the
micro-controller MPC860. The SCC can be configured to implement different protocols.
For most protocols, this corresponds to portions of the link layer (OSI layer 2). For a
ROC (64-kbps timeslot of an E1 link), the SCC is configured to implement HDLC
protocol in QMC-mode (QUICC multichannel controller mode).
SDP
Session description protocol
Seamless Rate Adaptation

A distinguished V5.2 link with some special characteristics: timeslot 16 serves as
protection physical channel for the communication channel related to timeslot 16 of the
primary link. Both timeslots form protection group 1. The protection protocol is also
associated to timeslot 16 of the secondary link.
Security management
Consists of a set of functions that protect telecommunications networks and systems
from unauthorized access by persons, acts, or influences, and to track and report access
attempts.
Serial number
The serial number is a 12-character code uniquely identifying each pack and indicating
the date and place of manufacture.
Service pack
Identifies the pack(s) which are responsible for handling the service. In 1:N protection
configuration there are dedicated pack(s) which are protected by a protection pack. In
1:1 protection configuration it is the pack currently carrying the service.
Service state
Each unit in the system at any time has a defined service state. This service state is
system driven and shows the usability of the unit. The normal service state is a read
only value and can not be changed by the operator. Each service state consists of two
parts: a primary service state displaying the general usability [in service (IS) or out of
service (OOS)] and a secondary service state displaying in case of a failure the failure
reason [for example not operational (NOP)]. The secondary service state is not used in
all cases. For some objects there is an administrative service state, whose primary
service state is changeable via TL1 commands. The operator can set the desired mode
for operation: IS or OOS. In this case the current availability is expressed in the
secondary state which is controlled and changed automatically by the system.
Service-affecting
Refers to a condition affecting the service at the time it is detected.
...................................................................................................................................................................................................................................
363-211-555 GL-21
Glossary
SID
System Identification
Side switch
The operation of deactivating an active pack and activating the stand-by pack.
Simplex mode
In the duplex IPFM context ‘Simplex Mode’ means, that the Protection Slot is not
provisioned in the IPFM data base to contain an IPFM. In normal simplex operation, per
convention the IPFM resides in the Preferred Slot. For more details see “Pack placement
in the different LAG Shelf types” (p. 2-11)
SIP
Session initiation protocol
SN
Serial Number
SNMP
Simple network management protocol - Used by the GSI/NAM for the AnyMedia ®
Access System subsystem for accessing the MIB objects.
SNMP TRAP
See TRAP.
Soft switch
In this information product used as a generic term to denote H.248 media gateway
controllers as well as SIP Proxies.
Software package
At the architectural level, software packages are the primary vehicle for functional
partitioning of the system. Software packages are configuration units of the system.
Software upgrade
Installing newer system software.
SPI
Security parameters index.
SRA
Seamless Rate Adaptation
Standby pack
The protection pack is up-to-date with the provisioning information of the active pack
and ready to take over operation with minimum service interruption. Its operational state
is STBY. As long as this state is not left the protection pack will be kept up-to-date with
the provisioning information.
Status condition
Report of a type of standing condition that reflects abnormal conditions or other
anomalies that are not assigned a severity. Status conditions are necessary to indicate to
the EMS or the operator that the system is in an unusual state, or is performing an
...................................................................................................................................................................................................................................
GL-22 363-211-555
Glossary
action that may interfere with system operations, such as loop-back, software
installation, or a forced or inhibited protection switch. A status condition is reported via
a report-event TL1 message or an SNMP trap. Two kinds of status conditions are
supported: Set/clear status conditions, which are active as long as the abnormal condition
persists, and transient status conditions, which indicate a single abnormal event which is
already cleared again.
STP
Spanning tree protocol.
Subscriber
Represents one customer entity on the LINES-layer.
Subscriber line
The a/b copper pair between a local exchange (LE) or access network system (AN) and
the network connection point (NCP) (see ITU G.101).
Subscriber loop
Contains subscriber’s line, subscriber’s installation and subscriber’s terminal; sometimes
referenced as drop.
Subscriber loop feeding

Subscriber loop feeding will be provided for POTS to supply subscriber’s terminal with
power and for supervisioning of subscriber’s loop.
SVGA
Super Video Graphics Adapter
SW
Software - Software is program data which is downloadable into the system.
....................................................................................................................................................................................................................................
T TA
Terminal Adapter
TAP
Test access path - Two metallic test access paths, one consisting of two pairs (TAP-B)
and the other of six pairs (TAP-A), provide both internal and external metallic test
access to the ports and drops of the application packs.
TAP-B
Test Access Path B
TAP10x
Test Application Pack - TAP10x (that is TAP100, TAP100B, or TAP101) is the internal
test head executing the measurements required for the drop.
TC
TAP Connected
...................................................................................................................................................................................................................................
363-211-555 GL-23
Glossary
TCA
Threshold Crossing Alert
TCP/IP
Transmission control protocol/Internet protocol - The combination of a network and
transport protocol developed by ARPANET for internetworking IP-based networks.
TDM
Time Division Multiplexing
TE
Terminal Equipment
TELNET
A remote terminal interface protocol which allows remote login capability into a system
on a network from any other node on that network that is also running TELNET.
TELNET is a TCP/IP application.
Terminating call
Terminating call is the type of call initiated at the network side of the network user
interface. It comprises the build-up, speech and the tear-down phase. For a POTS call
for example it starts with a message from the LE to the AnyMedia ® Access System to
seize a given subscriber and to supply ringing current.
Test session
A test session is the procedure including all necessary functions to test a subscriber. This
includes the setup of the test path as well as the release of the test equipment. The test
session runs in the AnyMedia ® Access System.
Threshold crossing alert

A threshold is a value assigned by the system user to a certain desired level (for
example errored seconds); when the level is exceeded, a threshold crossing alert is
issued.
TID
Target Identifier
Tier 2 NMS
A generic term for a network management system (NMS) that can manage multiple kinds
of network elements as a connected network. Tier 3 refers to element managers and Tier
1 refers to customer service support systems.
Timeslot number
A timeslot number identifies a timeslot of 64 kbps within the 2048-kbps V5.x link. The
range shall be 1 to 31. It may be used as a bearer channel, communication channel or
protection physical channel. Timeslot 0 is reserved and not used for the purposes
described above.
TRAP
An autonomous report in the simple network management protocol (SNMP), sent out by
a network element towards an SNMP network manager, indicating an exceptional event.
...................................................................................................................................................................................................................................
GL-24 363-211-555
Glossary
TS
Timeslot - Any cyclic time interval that can be recognized and defined uniquely. For
example a 64-kbps channel of a V5 interface that can be used either as bearer channel
(carrying subscriber payload information) or as communication channel (carrying both
subscriber and network element signaling information).
Turn-up
The process of bringing the system or a system component to an operational state (it
includes HW and SW installation as well as self diagnostics). After that the system can
be provisioned for service and other operational functionality.
....................................................................................................................................................................................................................................
U UART
Universal Asynchronous Receiver/Transmitter
UAS
Unavailable Second
UDP
User datagram protocol
Unavailability
In general, steady-state unavailability is defined as the fraction of time that the system is
not available, or equivalently as the average downtime per year. Unavailability is often
expressed in minutes per year of downtime. In engineering applications, unavailability is
frequently expressed in terms of its complement, that is the availability. For a digital
channel, unavailability or downtime begins when the first 10 consecutive severely error
seconds (SESs) occur, and it ends when the first of 10 consecutive non-SESs occur.
Unplanned side switch

Unplanned side switches are side switches that occur autonomously without any special
preparation by the active and protection IPFMs. Events that cause unplanned side
switches include software failure, hardware failure, pack removal.
Unprotected configuration
No protection pack is provisioned.
Uplink, downlink
See Downlink.
Upload
A binary data transfer from the AnyMedia ® Access System to the GSI.
Upstream
The bitstream direction from the NT towards the network.
Upstream direction
Transmission direction from customer to ATM network or telephony switch.
...................................................................................................................................................................................................................................
363-211-555 GL-25
Glossary
URI
Uniform resource identifier
Uniform resource identifiers are defined in RFC 2396. This RFC replaces the older
definitions of the uniform resource locators URL per RFCs 1738 and 1808.
URL
See URI.
User identifier (login)

A unique character string consisting of up to 20 alphanumeric characters (ASCII) used
by the system to identify a particular person or user.
....................................................................................................................................................................................................................................
V VBD
Voice band data
VDSL
Very High Speed Digital Subscriber Line.
VID
VLAN Identifier
VLANs
Virtual local area networks
VoIP
Voice over IP
VSIM
VDSL subscriber interface module.
....................................................................................................................................................................................................................................
W WAN
Wide area network - A network that operates over a large region and commonly uses
carrier facilities and services.
WFHBD
Weighted fair hashed bandwidth distributor.
WRR
Weighted round robin scheduling
....................................................................................................................................................................................................................................
Z Z interface
A 2-wire analog subscriber interface. It is used for connection of analog subscriber lines
and will carry signals such as speech, voice-band analog data and multi-frequency push
button signals, etc. In addition the Z interface must provide the DC feeding of
subscriber’s terminal and ordinary functions such as DC signaling, ringing, metering,
etc., where appropriate (see ITU Q.551 2.1.1).
...................................................................................................................................................................................................................................
GL-26 363-211-555
Index
Numerics Incoming DS1 signal LOS, ROC provisioning mismatch

1:N port protection failed, 6-76 6-70 detected, 6-41
............................................................. Incoming E1 signal failed, RT interface control data

6-60 link failed, 6-44
A Activate system log facility,
Incoming E1 signal FE RT interface failed, 6-42
7-304
degraded, 6-58
RT interface service
Activate VoIP AP 1:N port
Incoming E1 signal LOF, degraded, 6-43
protection, 7-294
6-61
RT link identification failed,
ADSL2+ Line configuration
Incoming E1 signal LOS, 6-37
parameters, 7-221
6-62
RT link interface
AIS detected, 6-57, 6-65
Incoming E1 signal near end identification failed, 6-38
Alarms degraded, 6-59
RT link layer 2 failed, 6-39
1:N port protection failed, IPFM software mismatch,
RT link layer 3 failed, 6-40
6-76 6-6
Slot-xx unequipped, 6-11
AIS detected, 6-57, 6-65 IPFM uplink failure, 6-10
Software program corrupt,
CPU utilization reaches its IPFM/ESIM software
6-8
threshold, 6-14 mismatch between AP and
IPFM/ESIM, 6-7 Software program version
Database corrupt, 6-50
mismatch, 6-49
Media gateway controller
Database synchronization
not reachable, 6-55 Synchronization input failed,
failed, 6-51
6-46
MGC connection failure,
Duplex cable misconfigured,
6-74 System free running -
6-54
synchronization failed,
NTP Synchronization failed,
GR-303 data link failed - 6-47
6-13
TMC/EOC, 6-33
Tip/ring cable disconnect,
Pack type mismatch, 6-12
GR-303 far end 6-72
major/critical, 6-34 Remote alarm indication
V5 data link failed - Bearer
received, 6-63
GR-303 far end minor, 6-35 Channel Control, 6-22
Incoming DS1 signal Required pack mismatch,
V5 data link failed -
6-53
degraded, 6-66 Common Control, 6-19
Required pack missing, 6-52
Incoming DS1 signal failed, V5 data link failed - Link
6-67 Retrieve active alarms, Control, 6-23
Incoming DS1 signal LOF, 7-327
6-69 Protection, 6-21
....................................................................................................................................................................................................................................
363-211-555 IN-1
Index
V5 data link failed - PSTN, ............................................................. Configure stand-alone mode for

6-20 ICAP or VoIP AP via terminal,
C Cabling
7-31
timeslot cessation of flags, 10BaseT port, 7-14, 7-66, Conformance statements
6-24 7-68
Additional international
V5 data link failed - V5 Between LAN connector conformity statements, A-5
PSTN restart failed, 6-25 (NB) and duplex IPFMs,
2-13 CE, A-2
V5 interface
Console port, 7-14, 7-66, Controlled mode, 2-3
administratively out of
service, 6-28 7-68 Controller
V5 interface failed, 6-18 ESIM APs, 7-202 Software load, 7-73
V5 interface identification ICAPs, 7-174 CPU utilization reaches its

failed, 6-27 IPADSL2_32 APs, 7-232 threshold, 6-14
V5 interface service Lightguide buildout Create/edit a script

degraded, 6-26 replacement, 7-81 Scripting, 7-18
V5 link administratively VDSL APs, 7-196 Create/modify a VLAN, 7-239
disabled, 6-31
VoIP APs, 7-106 Customer documentation, xviii,
V5 link failed, 6-29 xix
Cabling to OAM&P ports, 2-13
V5 link identification failed, How to order, xx
Clear required pack mismatch
6-30
alarm, 6-120 .............................................................
VoIP CPU overload alarm,
Clear software mismatch alarm
6-77 D Database backup, 7-306
between AP and IPFM flash,
VoIP port protection alarm, 6-82 Database corrupt, 6-50
6-75
Clear uplink failure alarm, 6-87 Database restore, 7-308
Yellow alarm received, 6-68
CLEI, 7-328 Database synchronization
AP installation, 7-24 failed, 6-51
Communications interfaces
AP installation/growth, 7-317 Date
Change password, 7-26
Apparatus code, 7-328 Set/retrieve date and time,
Change password on ICAP,
............................................................. 7-61
7-28
Set/retrieve date and time
B Backup Set inband management
for APs in stand-alone
channel, 7-59, 7-71
Database, 7-306 mode, 7-64
Set system management IP
Bridge port PM Deactivate VoIP AP 1:N port
address, 7-68
protection, 7-310
Provision/retrieve bridge
Set/Retrieve IP address,
port PM profile, 7-214 Delete a pack, 7-347
7-66
bridge port PM parameters, Delete an IP application pack,
System access via GSI, 7-14
7-215 7-312
Configuration considerations
bridge port PM profile DMT profile
for the different AnyMedia
Provision/retrieve, 7-214 shelf types, 2-5 Provision, 7-207
bridge port traffic profile Configure stand-alone mode for DS1 alarms
ICAP or VoIP AP via GSI, AIS detected, 6-65
Provision/retrieve, 7-217
7-36
...................................................................................................................................................................................................................................
IN-2 363-211-555
Index
Incoming DS1 signal ESIM Database corrupt, 6-50

degraded, 6-66
Ethernet cable connections, Database synchronization
Incoming DS1 signal failed, 7-75 failed, 6-51
6-67
Installation, 7-39 Duplex cable
Incoming DS1 signal LOF, misconfigured, 6-54
ESIM AP
6-69
IPFM software mismatch,
Wiring, 7-202
Incoming DS1 signal LOS, 6-6
6-70 ESIM fiber connector
IPFM uplink failure, 6-10
Incoming E1 signal failed, SFP module, 7-202
6-60 ETSI V5 Shelf not reachable, 6-55
Yellow alarm received, 6-68 Physical design, 2-8 NTP Synchronization
DTM parameters, 7-210 ............................................................. failed, 6-13
Duplex cable misconfigured, Pack type mismatch, 6-12
F FAST Shelf
6-54
Required pack mismatch,
Physical design, 2-10
Duplex ICAP 6-53
Fault management
Migration to simplex, 7-321 Required pack missing,
Activate VoIP AP 1:N port 6-52
Duplex IPFM
protection, 7-294 Ringing source failed, 6-73
Migration to simplex, 7-323
Deactivate VoIP AP 1:N port Slot-xx unequipped, 6-11
............................................................. protection, 7-310
Software program version
E E1 alarms ICAP Media monitoring, mismatch, 6-49
7-315
AIS detected, 6-57 GR-303 alarms
VoIP Voice stream
Incoming E1 signal FE GR-303 data link failed -
monitoring, 7-350
degraded, 6-58 TMC/EOC, 6-33
Flowcharts
Incoming E1 signal LOF, GR-303 far end major or
6-61 Turn-up for stand-alone APs, critical, 6-34
2-42
Incoming E1 signal LOS, GR-303 far end minor, 6-35
6-62 Turn-up for stand-alone
ICAP and VoIP APs, 2-38 GR-303 data link failed -
Incoming E1 signal near end TMC/EOC, 6-33
degraded, 6-59 Turn-up with an ESIM, 2-24
GR-303 far end major/critical,
Remote alarm indication Turn-up with an IPFM, 2-21 6-34
received, 6-63 .............................................................
GR-303 far end minor, 6-35
Eco-environmental statements,
G Generic synchronization alarms GSI
A-6
Synchronization input failed, Set system management IP
Electrostatic discharge
6-46 address, 7-68
considerations, 1-11
System free running - Set/Retrieve IP address,
Equipment
synchronization failed, 7-66
Retrieve IP equipment, 6-47
7-328 System access, 7-14
Generic system alarms
Equipment catalog item, 7-328 GSI operations
CPU utilization reaches its
ESD, 1-11 Activate system log facility,
threshold, 6-14
7-304
...................................................................................................................................................................................................................................
363-211-555 IN-3
Index
AP Software download and Provision/delete MAC .............................................................

activation in controlled address learning, 7-248
H Hardware
mode, 7-297
Provision/delete static route,
Configure stand-alone mode 7-251 Cabling and hardware, 2-13
via GSI, 7-38 .............................................................
Provision/delete trap
Create/modify a VLAN, receiving, 7-325 I ICAP
7-239
Provision/deprovision CPU
Activate system log facility,
Database backup, 7-306 utilization alarm, 7-326
7-304
Database restore, 7-308 Provision/disable broadcast
Configure stand-alone mode
storm control, 7-252
Delete a pack, 7-347 for ICAP or VoIP AP via
Provision/disable IGMP GSI, 7-36
Delete an IP application
snooping, 7-254
pack, 7-312 Configure stand-alone mode
Provision/retrieve feeder for ICAP or VoIP AP via
Force IPFM side switch,
parameters on an ICAP, terminal, 7-31
7-313
7-118
Migration duplex to
ICAP Software download
Provision/retrieve H.248 simplex, 7-321
and activation, 7-340
port parameters on an
Pin assignment E1/DS1
IPFM/ESIM Software ICAP, 7-138
cables, 7-178
download and activation,
Provision/retrieve H.248
7-335 Wiring, 7-174
protocol parameters, 7-100
Provision a VoIP AP, 7-89 Wiring example, 7-175,
Provision/retrieve ICAP
7-176, 7-177
Provision an ICAP, 7-113 profiles, 7-125
ICAP Media monitoring, 7-315
Provision IP AP slots, 7-48 Provision/retrieve MGCP
port parameters on an Incoming DS1 signal degraded,
Provision link aggregation,
ICAP, 7-143 6-66
7-49
Provision/retrieve MGCP Incoming DS1 signal failed,
Provision parameters for
protocol parameters, 7-103 6-67
V5.2 aggregation on an
ICAP, 7-165 Provision/retrieve network Incoming DS1 signal LOF, 6-69
protocol parameters, 7-130 Incoming DS1 signal LOS,
Provision port parameters on
a VoIP AP, 7-86 Provision/retrieve SIP 6-70
network protocol Incoming E1 signal failed, 6-60
a VSIM AP, 7-185 parameters, 7-94
Incoming E1 signal FE
Reset IP pack, 6-117 degraded, 6-58
an ESIM, 7-200 Retrieve active alarms, Incoming E1 signal LOF, 6-61
7-327
Incoming E1 signal LOS, 6-62
an ICAP, 7-148 Retrieve call statistics on
ICAP, 7-332 Incoming E1 signal near end
degraded, 6-59
an IPADSL2 AP, 7-211 Retrieve RMON statistics,
7-330 Insert packs, 7-41
Provision VLANs, IP
addresses and routing on Set/retrieve date and time, Installing the GSI, 7-6
ICAP, 7-157 7-61, 7-64 Interchangeability code, 7-328
Provision/delete addresses in Trace route, 7-257
DHCP relay, 7-247
...................................................................................................................................................................................................................................
IN-4 363-211-555
Index
Inventory IPFM/ESIM Software download Duplex to simplex for

and activation, 7-335 IPFM, 7-323
Retrieve IP equipment,
7-328 IPFM/ESIM software mismatch ............................................................
between AP and IPFM/ESIM,
IP pack N NTP server, 7-61, 7-64
6-7
Reset, 6-117 NTP Synchronization failed,
.............................................................
IP-AFM 6-13
L LAG 1900 Shelf
Wiring example with ICAP, ............................................................
7-177 Physical design, 2-5
O OAM&P Connectivity, 2-13
IPADSL bridge port profile LAG 200 Shelf
Ordering
Provision/retrieve, 7-228 Physical design, 2-7
Ordering Guide for the
IPADSL IGMP snooping LAG 2300 Shelf AnyMedia Access System,
parameters, 7-255 Physical design, 2-9 xix
IPADSL PM parameters, 7-226 LAG 4300 Shelf ............................................................
IPADSL PM profile Physical design, 2-6 P Pack type mismatch, 6-12

Provision/retrieve, 7-225 Laser safety guidelines, 1-14 PC requirements, 7-6
IPADSL2 transmission profile Layer 3 VLANs, 7-242 Pin assignment
Provision/retrieve, 7-220 Lightguide buildout a/b connector on VDSL AP,
IPADSL2_32 AP replacement, 7-81 7-196
Pin assignment 1000Base-T LPZ600 E1/DS1 cables for ICAP,

uplink interface, 7-235 7-178
Activate system log facility,
Pin assignment 100Base-T 7-304 Subscriber interface on
uplink interface, 7-234 IPADSL2_32 AP, 7-232
Pin assignment
Pin assignment subscriber 10/100Base-T uplink Subscriber interface on
interface, 7-232 interface, 7-109, 7-179 LPZ600, 7-107
Wiring, 7-232 Pin assignment subscriber Subscriber interface on

interface, 7-107 LPZ602, 7-108
IPFM
LPZ602 Uplink interface on
Classifier/policy block, IPADSL2_32 AP, 7-234,
7-281 Activate system log facility,
7-235
7-304
Ethernet cable connections, Uplink interface on
7-78 Pin assignment subscriber
LPZ600, 7-109, 7-179
interface, 7-108
Installation, 7-44 Pin assignment on ADSL2+
.............................................................
Migration duplex to cable connector, 7-233
simplex, 7-323 M Media gateway controller not
Port-based VLANs, 7-240
reachable, 6-55
Packet flow on IPFM, 7-279 Procedures
Metal radius clip, 7-203
Prioritizer rules, 7-282 Provision/Retrieve ADSL2
MGC connection failure, 6-74 transmission profile, 7-220
Provisioning rules for
Quality of service, 7-282 Migration Provision/retrieve bridge
IPFM software mismatch, 6-6 Duplex to simplex for ICAP, port PM profile, 7-214
7-321 Provision/Retrieve bridge
IPFM uplink failure, 6-10
port traffic profile, 7-217
...................................................................................................................................................................................................................................
363-211-555 IN-5
Index
Provision/retrieve IPADSL VSIM APs for Quality of VSIM transmission profile,

bridge port profile, 7-228 service, 7-287 7-191
Provision/retrieve IPADSL VSIM transmission status, Provision/Retrieve bridge port
PM profile, 7-225 7-195 traffic profile, 7-217
Provision/retrieve VSIM Provision a VoIP AP, 7-89 Provision/retrieve feeder
transmission profile, 7-191 parameters on an ICAP, 7-118
Provision an ICAP, 7-113,
VSIM PM profile, 7-188 7-125 Provision/retrieve H.248 port
parameters on an ICAP, 7-138
VSIM transmission status, Provision duplex ICAP mode,
7-195 7-155 Provision/retrieve H.248
Profiles Provision duplex IPFM mode,
7-46 Provision/retrieve MGCP port
Provision/edit/delete DMT
parameters on an ICAP, 7-143
profile, 7-207 Provision IP AP slots, 7-48
Provision/retrieve MGCP
Provision Provision parameters for V5.2
aggregation on an ICAP,
classifiers on VSIM APs,
7-165 Provision/retrieve network
7-265
Provision port parameters on a
GbE uplink transmission
VoIP AP, 7-86 Provision/retrieve SIP network
parameters, 7-57
Provision port parameters on a
Gigabit ethernet/100 B-T
VSIM AP, 7-185 Provisioning recommendations
uplink transmission
parameters, 7-52 Provision port parameters on an Quality of service, 4-2
ESIM, 7-200
IPFM/ESIMfor Quality of Provisioning scenarios
service, 7-279 Provision port parameters on an
VLANs, 7-243
ICAP, 7-148
L2/L3 group priorities for
.............................................................
Quality of service, 7-259 Provision port parameters on an
IPADSL2 AP, 7-211 Q Quality of service
L4 group priorities for
Quality of service, 7-262 Provision the gigabit ethernet Classifier/policy block on
uplink transmission the IPFM, 7-281
Link aggregation, 7-49
parameters, 7-57
New DMT profile, 7-207 Classifier/policy block on
Provision the gigabit VSIM APs, 7-287
packet type priorities for ethernet/100 B-T uplink
Quality of service, 7-269 Packet flow on IPFM, 7-279
transmission parameters, 7-52
policies on VSIM APs, Packet handling on VSIM
Provision VLANs, IP addresses
7-272 APs, 7-288
and routing on ICAP, 7-157
policy attributes on VSIM Provision/retrieve Prioritizer rules, 7-282
APs, 7-274 Provisioning
Bridge port PM profile,
policy instances on VSIM 7-214 recommendations, 4-2
APs, 7-277 Provisioning rules, 7-282
IPADSL bridge port profile,
Provision duplex ICAP 7-228 VoIP AP provisioning, 4-5
mode, 7-155
IPADSL PM profile, 7-225 Quality of service Support
Provision duplex IPFM
Provision/Retrieve ADSL2 Provision the IPFM/ESIM
mode, 7-46
transmission profile, 7-220 for Quality of service,
Spanning tree protocol 7-279
VSIM PM profile, 7-188
group, 7-54
...................................................................................................................................................................................................................................
IN-6 363-211-555
Index
Provision VSIM APs for Retrieve Electrostatic discharge

Quality of service, 7-287 considerations, 1-11
Active alarms, 7-327
Provision/modify classifiers General safety information,
Date and time, 7-61, 7-64
on VSIM APs, 7-265 1-4
IP equipment, 7-328
Provision/modify L2/L3 Laser safety guidelines,
group priorities for Quality Retrieve call statistics on ICAP, 1-14
of service, 7-259 7-332
Serial number, 7-328
Provision/modify L4 group Ringing source failed, 6-73
Service-activation
priorities for Quality of ROC provisioning mismatch
service, 7-262 Wiring for ESIM APs,
detected, 6-41
7-202
Provision/modify packet RT alarms
type priorities for Quality Wiring for ICAPs, 7-174
of service, 7-269 ROC provisioning mismatch
Wiring for IPADSL2_32
detected, 6-41
Provision/modify policies on APs, 7-232
VSIM APs, 7-272 RT interface control data
Wiring for VDSL APs,
link failed, 6-44
Provision/modify policy 7-196
attributes on VSIM APs, RT interface failed, 6-42
Wiring for VoIP APs, 7-106
7-274 RT interface service
Set
Provision/modify policy degraded, 6-43
instances on VSIM APs, Date and time, 7-61, 7-64
RT link identification failed,
7-277 6-37 SFP module on ESIM
............................................................. connector, 7-202
RT link interface
R Reconfiguration identification failed, 6-38 Shared VLANs, 7-241
RT link layer 2 failed, 6-39 Shelf types
IP AP degrowth, 7-318
Related documentation RT link layer 3 failed, 6-40 Configuration
considerations, 2-5, 2-5,
international regions, xviii RT interface control data link
2-5
Related documentation NAR, failed, 6-44
Slot-xx unequipped, 6-11
xix RT interface failed, 6-42
Software
Remote alarm indication RT interface service degraded,
received, 6-63 6-43 AP Software download and
activation in controlled
Remote Management solutions RT link identification failed,
mode, 7-297
for ICAP and RT-ROC 6-37
(COMDAC), 8-1 ICAP Software download
RT link interface identification
and activation, 7-340
Remote terminal failed, 6-38
IPFM/ESIM Software
ICAP wiring example, 7-176 RT link layer 2 failed, 6-39
download and activation,
Remove packs, 7-11 RT link layer 3 failed, 6-40 7-335
Required pack mismatch, 6-53 Run a script Software alarms
Required pack missing, 6-52 Create/edit a script, 7-18 IPFM/ESIM software
Reset ............................................................. mismatch between AP and
IPFM/ESIM, 6-7
IP pack, 6-117 S Safety, 1-1
Software download and
Restore Appearance of the safety activation, 7-297, 7-340
Database, 7-308 instructions, 1-7 Software program corrupt, 6-8
...................................................................................................................................................................................................................................
363-211-555 IN-7
Index
Software program version Transmission profile Software program version

mismatch, 6-49 mismatch alarm, 6-115
IPADSL bridge port profile,
Software related alarms 7-228 Synchronization input failed,
6-113
Software program corrupt, IPADSL PM profile, 7-225
6-8 Tip/ring cable disconnect,
Provision new DMT profile,
6-130
Specific VoIP AP alarms 7-207
V5 interface fault, 6-99
1:N port protection failed, Provision/Retrieve ADSL2
6-76 transmission profilee, V5 protocol data link faults,
7-220 6-96
MGC connection failure,
6-74 Provision/retrieve VSIM VoIP port protection alarm,
transmission profile, 7-191 6-137
Ringing source failed, 6-73
Trouble clearing, 6-82, 6-87 Trouble clearing procedures
Tip/ring cable disconnect,
6-72 Clear required pack Clear software mismatch
mismatch alarm, 6-120 alarm between AP and
IPFM flash, 6-82
6-77 Database corrupt, 6-85
Clear uplink failure alarm,
VoIP port protection alarm, DS1 signal faults, 6-126
6-87
6-75
E1 signal faults, 6-122
Tunnel-VLANs, 7-242
Stand-alone mode, 2-3
GR-303 data link faults,
Turn-up
Configure stand-alone mode 6-101
for ICAP or VoIP AP via AP installation, 7-24
IPFM software mismatch
GSI and IPFM, 7-36
alarm, 6-80 AP installation/growth,
Configure stand-alone mode 7-317
for ICAP or VoIP AP via
not reachable alarm, 6-135 ESIM, 2-24
terminal, 7-31
NTP Synchronization failed, ESIM installation in LAG
Subscriber priority provisioning
6-95 200 Shelf, 7-39
on VoIP APs, 4-10
Pack type mismatch alarm, for stand-alone APs, 2-42
Synchronization input failed,
6-93
6-46 for stand-alone ICAP and
Required pack missing VoIP APs, 2-38
System free running -
alarm, 6-118
synchronization failed, 6-47 Important notes, 2-3
Ringing source failed, 6-133
............................................................. IPFM, 2-21
ROC provisioning mismatch
T Time IPFM installation, 7-44
detected, 6-107
Set/retrieve date and time, IPFM Wiring, 7-78
RT cabling wrong, 6-103,
7-61 6-110 Provision spanning tree
Set/retrieve date and time protocol group, 7-54
RT interface control data
for APs in stand-alone link failed, 6-111 Verify/Update software load,
mode, 7-64 7-73
RT interface failed, 6-109
Tip/ring cable disconnect, 6-72 Wiring for ESIM as
RT link interface
TOS provisioning on VoIP APs, controller, 7-75
identification failed, 6-105
4-8
Slot-xx unequipped alarm,
6-91
...................................................................................................................................................................................................................................
IN-8 363-211-555
Index
............................................................. V5 data link failed - timeslot Quality of service

cessation of flags, 6-24 provisioning, 4-5
V V5 alarms
V5 data link failed - V5 PSTN Subscriber priority
V5 data link failed - Bearer restart failed, 6-25 provisioning, 4-10
Channel Control, 6-22
V5 interface administratively TOS provisioning, 4-8
V5 data link failed - out of service, 6-28
Common Control, 6-19 VLAN provisioning, 4-7
V5 interface failed, 6-18
V5 data link failed - Link Wiring, 7-106
Control, 6-23 V5 interface identification
failed, 6-27
V5 data link failed - 6-77
Protection, 6-21 V5 interface service degraded,
VoIP port protection alarm,
6-26
V5 data link failed - PSTN, 6-75
6-20 V5 link administratively
VoIP Voice stream monitoring,
disabled, 6-31
V5 data link failed - 7-350
timeslot cessation of flags, V5 link failed, 6-29
VSIM
6-24 V5 link identification failed,
Wiring, 7-196
V5 interface 6-30
administratively out of VSIM AP
VDSL AP
service, 6-28 Classifier/policy block,
Pin assignment, 7-196
V5 interface failed, 6-18 7-287
Wiring, 7-196
V5 interface identification Packet handling for Quality
failed, 6-27 VDSL PM parameters, 7-189 of service, 7-288
V5 interface service VDSL transmission parameters, VSIM PM profile

degraded, 6-26 7-186, 7-192, 7-218, 7-229
V5 link administratively VLANs, 7-239
VSIM PM profile, 7-188
disabled, 6-31 Layer 3 VLANs, 7-242
VSIM transmission profile
V5 link failed, 6-29 Port-based VLANs, 7-240
V5 link identification failed, Provisioning scenarios,
6-30 VSIM transmission status
7-243
Provision, 7-195
V5 data link alarms Shared VLANs, 7-241
V5 data link failed - V5 VSIM transmission status,
Tunnel-VLANs, 7-242
7-195
PSTN restart failed, 6-25
VLAN provisioning on VoIP
............................................................
V5 data link failed - Bearer APs, 4-7
Channel Control, 6-22 W Wiring
VoIP AP
V5 data link failed - Common ESIM APs, 7-202
Control, 6-19 Activate system log facility,
7-304 ESIM uplink cabling, 7-75
V5 data link failed - Link
Configure stand-alone mode ICAPs, 7-174
Control, 6-23
for ICAP or VoIP AP via
V5 data link failed - Protection, IPADSL2_32 APs, 7-232
GSI, 7-36
6-21 IPFM, 7-78
Configure stand-alone mode
V5 data link failed - PSTN, for ICAP or VoIP AP via VDSL APs, 7-196
6-20 terminal, 7-31
VoIP APs, 7-106
...................................................................................................................................................................................................................................
363-211-555 IN-9
Index
Wiring ADSL2+ cable

connector
Pin assignment, 7-233
.............................................................
Y Yellow alarm received, 6-68
...................................................................................................................................................................................................................................
IN-10 363-211-555

v1 Anymedia Access System

Uploaded by

Copyright:

Available Formats

v1 Anymedia Access System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

v1 Anymedia Access System

Uploaded by

Copyright:

Available Formats

AnyMedia® Access System

Commands and Procedures for IP-based

See “How to order” (p. xx).

About this information product

Reason for reissue .................................................................................................................................................................... xvi

History ........................................................................................................................................................................................... xvi

Safety information ................................................................................................................................................................... xvii

Intended audience .................................................................................................................................................................... xvii

Conventions used ................................................................................................................................................................... xvii

Related documentation for the international regions ............................................................................................... xviii

Related documentation for the North America regions ............................................................................................. xix

How to order ................................................................................................................................................................................ xx

How to comment ........................................................................................................................................................................ xx

Overview ...................................................................................................................................................................................... 1-1

Structure of hazard statements ............................................................................................................................................ 1-2

General safety information ................................................................................................................................................... 1-4

Appearance of the safety instructions .............................................................................................................................. 1-7

Relevant safety instructions .................................................................................................................................................. 1-9

Electrostatic discharge considerations ............................................................................................................................ 1-11

Laser safety guidelines ......................................................................................................................................................... 1-14

2 Initial system turn-up and service activation

Overview ...................................................................................................................................................................................... 2-1

Before you begin

Important notes .......................................................................................................................................................................... 2-3

OAM&P Connectivity .......................................................................................................................................................... 2-13

Links to commonly used procedures ............................................................................................................................. 2-19

Initial system turn-up for configurations in controlled mode

Overview .................................................................................................................................................................................... 2-20

Flowchart of system turn-up with IPFM(s) ................................................................................................................. 2-21

Links to initial system turn-up procedures with IPFM(s) ..................................................................................... 2-23

Overview .................................................................................................................................................................................... 2-27

Activate service for VoIP .................................................................................................................................................... 2-28

Activate service over ICAPs ............................................................................................................................................. 2-29

Activate VDSL service ........................................................................................................................................................ 2-34

Activate ADSL2 service ...................................................................................................................................................... 2-35

Activate Ethernet downlinks on ESIM ........................................................................................................................ 2-36

Initial system turn-up for configurations in stand-alone mode

Overview .................................................................................................................................................................................... 2-37

3 Support L2 and L3 functionality

Related procedures ................................................................................................................................................................... 3-1

Overview ...................................................................................................................................................................................... 4-1

QoS provisioning recommendations ................................................................................................................................. 4-2

Related procedures ................................................................................................................................................................... 4-3

VoIP AP provisiong for QoS ................................................................................................................................................ 4-5

VLAN provisioning on VoIP APs ...................................................................................................................................... 4-7

TOS provisioning on VoIP APs .......................................................................................................................................... 4-8

Subscriber priority provisioning on VoIP APs ........................................................................................................... 4-10

5 Operations, administration and maintenance functions

Related procedures ................................................................................................................................................................... 5-1

6 Alarms and trouble clearing

Overview ...................................................................................................................................................................................... 6-1

Overview ...................................................................................................................................................................................... 6-5

IPFM software mismatch alarm ......................................................................................................................................... 6-6

IPFM/ESIM software mismatch between AP and IPFM/ESIM alarm ............................................................... 6-7

Software program corrupt alarm ........................................................................................................................................ 6-8

Generic system fault alarms

Overview ...................................................................................................................................................................................... 6-9

IPFM uplink failure alarm .................................................................................................................................................. 6-10

Slot-xx unequipped alarm ................................................................................................................................................... 6-11