NN10600 550
NN10600 550
NN10600 550
Configuration
NN10600-550
Document status: Standard
Document issue: 02.01
Document date: June 2007
Product release: PCR 8.2
Job function: Installation and Commissioning
Type: NTP
Language type: U.S. English
Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks.
Contents
New in this release 10
Features 10
Hitless CP Software Removal 10
Other changes 10
nodes 320
Fabric card configuration 321
Configuring the fabric card component 322
Understanding the Multiservice Switch 7400 bus 322
Single- and dual-bus mode 323
Bus taps 323
Clock source 323
Understanding the Multiservice Switch file system 324
File system information 325
Disk synchronization 325
Different-sized disks 326
File system restrictions 326
Disk full conditions 327
Understanding Y-protection for dual FPs 327
The operation of Y-protection 328
Equipment protection for dual FPs with Y-protection 329
Software migration between dual FPs with Y-protection 329
Card configuration for Y-protection 330
Hardware specifications of the Y-splitter cables 330
Understanding hitless services 330
Types of services 330
Critical components and attributes 334
Hitless activation of critical attributes 338
Failure modes for hitless activation of critical attributes 339
Supported critical attributes for hitless activation 339
Attention: To ensure that you are using the most current version of an NTP,
check the current NTP list in Nortel Multiservice Switch 7400/15000/20000
New in this Release (NN10600-000).
Features
See the following section for information about feature changes:
Hitless CP Software Removal (page 10)
Other changes
See the following section for information about changes that are not feature-
related:
Updated Interpreting bus clock source status (page 176) to show a
change in the definition for unknown.
Yes
Task navigation
Run the StartUp utility. See Nortel Multiservice Switch 7400/15000/20000
Administration Network Management Connectivity (NN10600-271).
Setting up node security (page 13)
Configuring node identification (page 14)
Configuring general service parameters (page 17)
Configuring node basics (page 18)
Set up data collection. See Nortel Multiservice Switch 7400/15000/20000
Administration Data Management (NN10600-561).
Performing node maintenance (page 19)
CAUTION
Configure user IDs immediately
The first configuring task must be to configure at least one user ID
with system administration impact. If you do not configure a user
ID, your node has no security. Anyone can access the node
without a user ID and password.
Prerequisites
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
The nodeId, nodeName, and namsId can be set using the Multiservice
Switch StartUp software. Before performing this procedure, verify that the
node has not already been identified. For more information, see Nortel
Multiservice Switch 7400/15000/20000 Administration Network
Management Connectivity (NN10600-271).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<name> A 12-character ASCII string that is unique to every Multiservice Switch
node in a network. The default is noname.
Only the following set of characters is permitted in the node name:
uppercase and lowercase alphanumeric characters
period (.)
underscore (_)
For example, LA_12 is valid and LA$%12 is invalid.
The nodeName attribute is a unique name given to each node in order
to distinguish it from other nodes in the network. The nodeName
attribute is used by the Nortel Multiservice Data Manager.
<nodeid> Any number between 1 and 4095. The node identifier must be unique
for each Multiservice Switch node.
The nodeId attribute is a number that uniquely identifies the node
component instance in the Multiservice Switch network. The system
uses the node identifier for routing control and in some data packets
sent to other nodes in the network. Routing protocol packets indicate
the node identifiers for all other nodes in the network.
<regionId> Any number between 0 and 126.
The regionId attribute identifies the nodes that belong to a topology
region within a network. Neighbor nodes exchange region identifier
values to determine whether or not they belong to the same topology
region.
<namsId> Any number between 256 and 49151. It must be unique across the
entire network of Multiservice Switch nodes supporting the transport of
DPN traffic as well as all DPN resource modules (RMs) and access
modules (AMs) in the network.
The namsId attribute holds the network administration (Nams)
identifier, which identifies nodes that support DPN traffic.
EM
ModuleData (Mod)
nodeld
nodeName
namsld
regionld
VirtualCircuitSystem (Vcs)
FrameRelaySystem (Frs)
Time
moduleTime
offset
syncStatus
mainServer
syncSources
xntpVersion
Server
ipAddress(ipAddr)
ipStack
xntpVersion
stratum
status
pktSent
pktRecv
pktValid
PPT 2930 005 AA
Nortel Multiservice Switch StartUp utility sets the attributes existing under
these components with default values. You have the option to customize the
attributes to suit the requirements of the network. Many of the attributes must
have the same values across a Multiservice Switch subnet so that the
Multiservice Switch nodes can communicate with each other. If you do decide
to change values, do so with extreme caution. Call Nortel Networks for
assistance if necessary.
CAUTION
Risk of data loss
Changing the node-wide attributes of the VirtualCircuitSystem and
FrameRelaySystem components can cause the node to become
isolated from other nodes in the network. This node isolation can
cause data loss.
Step Action
1 Configure the cards and ports. See Common processor card procedures
(page 57).
2 Configure the Multiservice Switch trunks. See Nortel Multiservice Switch
7400/15000/20000 Configuration Trunking (NN10600-420) for details.
3 Configure the IP interface over virtual circuit (IPIVC) or the IP interface over
frame relay (IPIFR) for network management connections.
See Nortel Multiservice Switch 7400/15000/20000 Administration
Network Management Connectivity (NN10600-271) for details.
--End--
Network and
node time
configuration
Configuring a
network time server
No
Synchronizing
Multiservice Switch
to a Preside MDM
No
End
MSS 3418 002 AA
Task navigation
Configuring a network time server (page 23)
Synchronizing automatically with a network time server (page 24)
Synchronizing manually with a network time server (page 26)
Configuring the time zone offset (page 28)
Verifying the time configuration on the node (page 30)
Prerequisites
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<n> The instance of the Server component. You can configure up to 10
Server components (110) on a Multiservice Switch node.
In case a network time server is not specified, the Multiservice Switch system
automatically attempts to synchronize with any Multiservice Data Manager
workstation it can reach using its IP interface over frame relay (IPIFR) or its IP
interface over virtual circuit (IPIVC). If time servers are deleted when the
Multiservice Switch node is up and running, the system does not synchronize
with a Multiservice Data Manager workstation. For example, automatic
synchronization works at startup if no time servers are specified.
The node gets the network time from the network management interface
system (NMIS) notification of a new fast management information protocol
(FMIP) session. In this case, the system decides with which, and how many
management devices (maximum 10), the node will synchronize. Multiservice
Data Manager connectivity, IPIFR, and IPIVC are explained in detail in Nortel
Multiservice Switch 7400/15000/20000 Administration Network
Management Connectivity (NN10600-271).
Prerequisites
See RFC 1305, Network Time Protocol (Version 3) for more information
on public NTP.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<address> The IP address of the management device that you want to use as a
time server to the node.
<type> Either ipiFrIpiVc (for frame relay/X.25 connectivity to a time server
management device) or VrIp (for IP virtual router connectivity to a time
server management device). The time servers must connect to the
node via the same connection type (for example, all using vrIP or all
using ipiFrIpiVc). Mixed connections are not supported.
Prerequisites
CAUTION
Risk of confusion in the interpretation of accounting
records and alarm time stamps
Nortel Networks recommends that you synchronize all nodes in a
network from a reliable time reference.
When set manually, the node time is not initially precisely the
same on all network nodes and also eventually drifts out of
synchronization due to the different precision of the local clocks on
each node.
This eventually results in alarms and accounting records not
reporting an accurate time stamp.
Procedure steps
Step Action
1 Stop the time synchronization on the node. Lock all the provisioned time
server components for each provisioned server:
lock Time Server/<n>
2 Verify that the node time has changed to unsynchronized:
d Time syncStatus
3 On the node, make sure that the time offset is set to 0. Configure the node
time so that it is set to UTC and as close as possible to the Multiservice Data
Manager workstation UTC time: (less than 1000 seconds of UTC):
display time moduletime
set time offset 0
set time moduleTime <yyyy-mm-dd> <hh:mm:ss>
4 On the node, restart synchronization by unlocking the time server
components:
unlock Time Server/<n>
5 Monitor the progress by checking the syncStatus attribute:
d Time syncStatus
--End--
Variable definitions
Variable Value
<hh>:<mm>:<ss> The hour, minute, and second.
<n> The instance value of the time server.
<yyyy>-<mm>-<dd> The year, month, and day.
The time zone offset value ranges from 720 to 900 minutes, which
represents a range from 12 hours to +15 hours. A time offset between 0 and
900 minutes (+15 hours) represents a time ahead of UTC (or east of the prime
meridian). A time offset value between 0 and 720 minutes (12 hours)
represents a time behind UTC (or west of the prime meridian).
Prerequisites
CAUTION
Risk of confusion in the interpretation of accounting
records and alarm time stamps
Nortel Networks recommends that you set the time zone offset to
the same value for every node in the same network.
If nodes in the same network have different time zone offsets and
two alarms on different nodes are generated at the exact same
time, they have different time stamps. This can result in difficulties
when correlating time between the two Multiservice Switch nodes.
Procedure steps
Step Action
1 Set the offset attribute of the Time component to the number of minutes
difference (before or after) between the local node time and the network
time. The node must be synchronized before setting the time offset.
set Time offset <offset value>
--End--
Variable definitions
Variable Value
<offset value> is the value of the offset attribute.
Prerequisites
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<n> The instance value of the Server component.
NCS configuration
Are you
configuring or
removing NCS?
Removing
Configur ing
Removing an NCS
refer ence or
Removing SSM
setting a node to
NCS
free- run
End
MSS_4002_029_AA
Is the node
connected to an
external timing
Yes source?
No
Configuri ng an
external timing Configuri ng NS
source
Internal
No
Yes
No Configuri ng NS
Configuri ng SETS SSM for SETS
ports
Yes
Are you
Configuri ng NS
confi guring SSM
for SETS
for SETS?
MSS_4002_030_AA
Task navigation
Configuring an external timing source (page 35)
Configuring NS (page 37)
Configuring SSM NCS (page 40)
Configuring the clocking source for the ports (page 39)
Removing a NCS reference or setting a node to free-run (page 42)
Removing SSM NCS (page 43)
Configuring SETS ports (page 44)
Configuring NS for SETS (page 45)
Configuring NS SSM for SETS (page 47)
Prerequisites
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
For information about the Nortel Multiservice Switch 7400 node BITS
termination panel, see Nortel Multiservice Switch 7400 Fundamentals
Hardware (NN10600-170). FOR information about the Multiservice
Switch 15000 or Multiservice Switch 20000 node Alarm/BITS module, see
Nortel Multiservice Switch 15000/20000 Fundamentals Hardware
(NN10600-120).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<linetype> d4 or esf
<x> The instance of the Lp.
Configuring NS
Configure NS to add network synchronization and set clocking references.
Prerequisites
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
If there are no references where the node can receive a timing signal, do
not configure any references. This forces the node clocking to run in free-
run mode.
The individual ports of an optical interface card configured for automatic
protection switching (APS) can each serve independently as a reference
source. However, the pair of them as defined by the Aps component
instance cannot be used as a single reference source.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<path> The logical port to be used as a timing reference.
<reference_type> The type of network synchronization reference. Up to three sources
can be defined using the components primaryReference,
secondaryReference, and tertiaryReference.
<revDel_value> The value of the reversionDelay attribute. Can have the value manual
or the number of minutes, between 0 and 120, can be set. The default
is 0 minutes.
<useRef_value> The value of the useableReferences attribute. Can have the value
enabled, default value, or notDegraded.
Em
NetworkSynchronization (NS)
primaryReference (priRef)
secondaryReference (secRef)
tertiaryReference (tertRef)
useableReferences (useRef)
reversionDelay (revDel)
ssmProtocol (ssm)
PPT 3104 001 AB
Prerequisites
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
If you are using an external timing source, Nortel Networks recommends
that the clockingSource for all ports be set to module.
If you are using a V.11 or V.35 FP, see Clocking for V.11 and V.35 FPs
(page 291) for additional information.
See Nortel Multiservice Switch 7400/15000/20000 Components
Reference (NN10600-060) for LP port types and clockingSource values.
Procedure steps
Step Action
1 Set all ports of the LP to synchronize with the necessary timing source:
set Lp/<x> <port_type>/<y> clockingSource
<clockingSource_type>
2 Repeat step 1 for all ports on the LP.
3 For ports on a V.11 or V.35 FP set the linkMode attribute.
set lp/<x> x21/<y> linkMode <linkMode_value>
set lp/<x> V35/<y> linkMode <linkMode_value>
--End--
Variable definitions
Variable Value
<clockingSource_type> The value for the type of clocking source used for synchronizing
the transmit clock.
<linkMode_value> The value of the x21 or V35 port linkMode. It can be set to either
dte or dce.
<port_type> The type of port.
<x> The instance of the Lp.
<y> The instance of the port.
Prerequisites
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
Attention: This attribute needs to be configured only if the equipment at the remote
end of the port does not support SSM transmission
6 For E1 ports, set the ssmE1SaNumber attribute to specify the San used by
the network for SSM signalling.
set lp/<x> e1/<e1_value> ssmE1SaNumber <san_value>
7 Optionally, if using E1BITS timing on a node, you can set the quality level
normally assigned with the BITS timing reference as follows:
set lp/<x> ee1/<ee1_value> ssmRxDefault <quality_value>
8 Optionally, if using DS1BITS timing on a node, you can set the quality level
normally assigned with the BITS timing reference as follows:
set lp/<x> eds1/<eds1_value> ssmRxDefault
<quality_value>
--End--
Variable definitions
Variable Value
<default> The provisioned value of the s1RxDefault attribute. It can be set to any
value from 0 to 15, or it can be set to none.
<e1_value> The instance value of the e1 component.
<eds1_value> The instance value of the eds1 component.
<ee1_value> The instance value of the ee1 component.
<quality_value> The provisioned value of the ssmRxDefault attribute. For a summary
of acceptable quality level values, refer to SONET/SDH quality level
(QL) mapping table (page 291).
<san_value> The provisioned value of the ssmE1SaNumber attribute. The default
value of none disables SSM signalling on the specified E1 port.
<value> The provisioned value of the ssmProtocol attribute. It can be set to one
of four possible values: disabled, enabledRevertive,
enabledNonRevertive, enabledMigration.
<x> The instance of the Lp.
<y> The instance of the SONET port.
Prerequisites
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<reference_type> One of the primaryReference, secondaryReference, or
tertiaryReference attribute.
Prerequisites
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<x> The instance value of the LP.
<y> The instance of the port.
Prerequisites
Add the externalTiming feature to the CPfeatureList attribute.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<m> The SETS port, which can be 0 or 1.
<transmit_mode> The transmit mode, which can be e1Signal or squareWave.
<ssm_bits> The value of the SSM transmission encoding bits, which can be 4, 5, 6,
7, 8, or none.
Em
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<path> is the logical port to be used as a timing reference. The possible values
for SETS sources are nsSelect, bitsA, bitsB, nsProcessed, and none.
When you choose the nsSelect option, the SETS reference is the same
as the clock reference selected by the NS component. The following
SETS configurations are not recommended because they may result in
excessive phase transients during SETS reference switching due to
LOS/LOF/AIS on the SETS active reference:
setsPrimaryReference = nsSelect,
setsSecondaryReference = bitsA, primaryReference = lp/0 EE1/0
setsPrimaryReference = nsSelect,
setsSecondaryReference = bitsB, primaryReference = lp/01 EE1/1
The excessive transient occurs only if nsSelect is the active reference,
bitsA (or bitsB) is the standby reference, and lp/0 EE1/0 (or lp/0 EE1/1)
is the NS active reference.
<reference_type> is the type of network synchronization reference. Up to three sources
can be defined using the components setsprimaryReference,
setssecondaryReference, and setstertiaryReference.
<termPanel> specifies if the termination panel is used in the configuration. Use yes
if it is used and no if it is not used.
<timer> specifies how long after a node becomes enabled (due to a reset or CP
switchover) before starting the SETS source selection. This is to
ensure a stable SETS output source. The value range from 0 to 12 (in
minutes).
Em
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<value> The provisioned value of the ssmProtocol attribute, which can be set to
disabled, enabledRevertive, or enabledNonRevertive.
Em
NetworkSynchronization (NS)
setsSSMProtocol
Navigation
Adding and configuring applications (page 49)
Removing and replacing specific applications and patches (page 50)
Removing and replacing all applications and patches (page 52)
Activating the AVL configuration changes (page 54)
Changing the patch list (page 56)
You can add certain applications only after the associated feature has been
included in the feature list of a logical processor type (LPT). See Configuring
the software features of an LPT (page 164).
Prerequisites
Before you can add and configure applications, you must have previously
installed Multiservice Switch software by running StartUp. As part of the
software installation, StartUp will add default applications and the software
installer will download the release software to the node. You can then add
and configure applications. For instructions on running StartUp, see Nortel
Multiservice Switch 7400/15000/20000 Administration Network
Management Connectivity (NN10600-271).
Perform the following steps in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<application> The application that you want to add.
Prerequisites
Keep a copy of the committed provisioning file that was running before you
updated the AVL until you confirm that the new software functions
properly. To revert to the old version of the software, you need this file.
See Nortel Multiservice Switch 7400/15000/20000 Installation Software
(NN10600-270).
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<avName> The application version that you want to delete.
<patch> The name of the unwanted patch. To remove multiple patches,
precede each patch name with a tilde (~) and separate each of them
with a space.
To replace all the application versions and patches with new versions in a
single command, use an exclamation mark. The exclamation mark tells the
system to delete all the applications or patches in the AVL or patch list.
Prerequisites
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<avName> The application version that you want to add.
<patch> The patch that you want to add.
If you are only applying a patch to an application version, you do not have to
modify the AVL, only the patch list. For more information, see Changing the
patch list (page 56).
Prerequisites
When you update the AVL to perform a software upgrade, you have to
verify the configuration twice using the check Prov command. First, you
must verify the configuration before you can activate it using the old
software version, then after activation using the new software version. You
need a second check Prov to ensure that the node configuration is based
on the software and component model that you want to run as
configuration might have changed since the first check Prov was done, or
a view migration might have introduced new components. See Nortel
Multiservice Switch 7400/15000/20000 Installation Software
(NN10600-270) for more information.
When you update the AVL you also must ensure that the patch list is still
valid. In general, a new application version incorporates the changes in
the preceding patches, making them obsolete. For more information on
specific application versions and patches, see Nortel Multiservice Switch
Release Notes.
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
Attention: If the standby CP resets during the software activation, continue the
standard software activation sequence on the active CP. Allow both CPs to load the
new software and perform the remaining steps on the active CP.
--End--
Variable definitions
Variable Value
<name> The name you want to give the committed view.
Prerequisites
You cannot put a patch on the patch list unless its associated application
version is on the AVL. See Application versions (page 313). Some patches
can require other patches to also be on the patch list. Certain
combinations of patches do not work together. For more information on
patches, see Patches (page 314). See Nortel Multiservice Switch Release
Notes for the restrictions on particular patches.
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<list> A list of patches. The patch names in the list must be separated by a
space. To remove a particular patch from the patch list, precede it with
a tilde (~) character. To replace all of the patches on the list with new
patches, begin the list with an exclamation mark (!) followed by a
space.
Navigation
Comparing the card type of a mounted card and its configured slot
(page 59)
Configuring a new processor card (page 60)
Configuring a port to use an SFP optical module (page 62)
Configuring the fan alarm to recur (page 65)
Decommissioning an FP (page 66)
Displaying information about daughter cards on a Multiservice
Switch 7400 processor card (page 67)
Displaying the memory capacity of a processor card (page 68)
Displaying the status of a processor card (page 78)
Displaying the status of an installed SFP optical module (page 69)
Locking a function processor (page 72)
Locking a port (page 74)
Preparing an active FP for being replaced (page 76)
Re-enabling an LP (page 79)
Removing from service a failed FP (page 82)
Removing from service a standby electrical FP (page 84)
Comparing the card type of a mounted card and its configured slot
Make sure the card mounted in a slot matches the type of card configured for
that slot in the system software.
Prerequisites
Perform the following procedure in operational mode. For more
information, see Operational mode (page 342).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<m> The slot number of the processor card.
Prerequisites
Install all required hardware. See Nortel Multiservice Switch 7400
Installation, Maintenance, and Upgrade Hardware (NN10600-175) or
Nortel Multiservice Switch 15000/20000 Installation, Maintenance, and
Upgrade Hardware (NN10600-130). FPs do not have to be physically
mounted; however, you must know the slot number where the FP is
installed before you can configure it.
Configure the required LP and logical processor types (LPT). See Logical
processor, port, and channel configuration (page 146).
Perform the following procedure in provisioning mode. For more
information, see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<cardtype> is the type of the processor card. For information on the type associated
with a particular processor card, see Processor card instances (page 301)
or Nortel Multiservice Switch 7400/15000/20000 Fundamentals FP
Reference (NN10600-551).
<connector> is the connector on the sparing panel. The default value is notApplicable.
If the processor card is the spare card, use the value spare. If the
processor card is the main card on a Multiservice Switch 7400 series
node, use one of these values: mainA, mainB, mainC, or mainD. If the
processor card is the main card on a Multiservice Switch 15000 or
Multiservice Switch 20000 node, or an MSA32 FP or MSA8 FP of a
Multiservice Switch 7400 node, use one of these values: mainA, mainB,
mainC, mainD, mainE, or mainF.
If the processor card is to be part of a one-for-one (1:1) sparing
configuration using a one-for-one sparing panel, leave the attribute
sparingConnection set to the default value notApplicable.
<m> is the slot number of the processor card. Multiservice Switch nodes
number their slots starting at zero.
Prerequisites
When configuring the card, component OpticalModule is automatically
added. The default is none. You must match the software port
configuration to the type of inserted SFP module so that the port can
operate.
The port must be locked. For information on locking a port, see Nortel
Multiservice Switch 7400/15000/20000 Commands Reference
(NN10600-050).
When re-configuring the SFP module type for a port, change only the
OpticalModule type.
The description of what an SFP module is, the listed types of available
SFPs, and the specific FPs that use them are identified in the chapter on
processor cards in Nortel Multiservice Switch 15000/20000 Fundamentals
Hardware (NN10600-120).
When configuring an FP with cardtype 16pOC3PosAtm (NTHW44) to use
Y-protection on a port, the only supported type of SFP module is
OC3SmIr. The SFP modules with PEC NTTP02CD must be connected
when this configuration is being entered. Since the NTHW44 supports
more than one version of SFP module, you must ensure the appropriate
ones are plugged into the ports that are to use Y-protection. The custom
Y-splitter cables should already be made but not connected while the
configuration occurs.
You can display the operational status of a port by doing the procedure
Displaying the status of an installed SFP optical module (page 69).
Other FP configuration information is included in Nortel Multiservice
Switch 7400/15000/20000 Fundamentals FP Reference
(NN10600-551).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<m> The instance value for the logical processor (LP).
<n> The instance value for the port.
<p> The instance value for the Ethernet port.
<type> One of the following types of optical module:
OC3MmSr, OC3SmIr, or OC3SmLr for an NTHW44 port
OC3SmIr for an NTHW44 port with an NTTP02CD when
configuring the port for Y-protection
OC12SmIr, OC12SmLr, OC48SmLr, OC48SmLr2, or OC48SmIr
for an NTHW46 port
LX or SX for an NTHW49 port
none for an FP that does not have SFP module sockets (ports) on
its faceplate
Em
LogicalProcessor (Lp)
Ethernet
OpticalModule
type
typeCheck
Sdh
OpticalModule
type
typeCheck
Sonet
OpticalModule
type
typeCheck
MSS 3305 001 AA
Prerequisites
Perform the following procedure in provisioning mode. For more
information, see Provisioning mode (page 343).
The attribute repeatFanAlarm is set to on or off by default depending on
your software package.
The 8-hour interval is fixed.
Procedure steps
Step Action
1 Determine what the attribute for repeating the fan failure alarm is set at.
query Shelf repeatFanAlarm
2 Set the attribute repeatFanAlarm to enable the fan alarm to recur.
set Shelf repeatFanAlarm ON
If you are using the CAS interface, use the command
display Shelf repeatFanAlarm ON
--End--
Decommissioning an FP
Decommission an FP by removing it from a shelf slot and nullifying or
changing that slots configuration (provisioning) in preparation to install a
blank processor card.
Prerequisites
Perform the following procedure in provisioning mode. For more
information, see Provisioning mode (page 343).
Whether or not another card type is being deployed in the slot, nullify the
existing software configuration by setting its attributes back to the defaults.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<m> The slot number of the processor card you want to decommission. Nortel
Multiservice Switch nodes number their slots starting at zero.
<n> The number of the LP.
Prerequisites
Perform the following procedure in operational mode. For more
information, see Operational mode (page 342).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<m> The slot number of the processor card.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<m> The slot number of the processor card.
Prerequisites
You need an optical FP that is configured to use an SFP optical module.
The 4-port MR POS and ATM (NTHW46) and 16-port OC-3/STM-1
POS and ATM (NTHW44) cards must have the component sonet or
sdh configured.
The 4-port Gigabit Ethernet card (NTHW49) must have the component
ethernet configured.
Identify the PEC versions of all SFP modules that are available for the
specific FP in Nortel Multiservice Switch 15000/20000 Fundamentals
Hardware (NN10600-120).
Whenever an FP that uses SFP modules is inserted into a slot, the ports
(sockets) of its SFP module must be matched to the socket by following
the procedure Configuring a port to use an SFP optical module (page 62).
To get any status about an SFP module, it must be plugged into the socket
on the FP faceplate. When an SFP is plugged into a powered FP, it is
automatically tested for its ability to operate.
Alarm 7011 5480 is generated to indicate the installed SFP module is not
operating because:
it fails diagnostics after insertion
it mismatches the software configuration of the SFP module for the
port
it is not an approved type or vendor
When removing an SFP module, its port must be locked in software, as
described in Nortel Multiservice Switch 7400/15000/20000 Configuration
(NN10600-550). The status of the SFP is still provided when the port is
locked.
For information about the commands used in the following procedure, see
Nortel Multiservice Switch 7400/15000/20000 Commands Reference
(NN10600-050).
Perform the procedure steps in operational mode.
Procedure steps
Step Action
1 Display the status of the installed version of the SFP module for a port by
entering one of the following:
display lp/<lp> ethernet/<e> OpticalModule
display lp/<lp> sdh/<s> OpticalModule
display lp/<lp> sonet/<s> OpticalModule
2 Ensure that the insertedType matches the capability of the PEC version that
is labelled on the SFP module.
OC3MmSr, OC3SmIr, or OC3SmLr for an NTHW44
OC12SmIr, OC12SmLr, OC48SmLr, OC48SmLr2, or OC48SmIr for an
NTHW46
LX or SX for an NTHW49
none for an FP that does not have SFP module sockets (ports) on its
faceplate
When insertedType indicates none (the default), it means the card has not
been configured, or the card does not have SFP module sockets.
3 When the insertedType indicates typeMismatch, either change the software
configuration to match the installed module or use an appropriate module.
You can query what type of SFP module is configured for the port by
entering one of the following:
display -provisioned lp/<lp> ethernet/<e> OpticalModule
display -provisioned lp/<lp> sdh/<s> OpticalModule
display -provisioned lp/<lp> sonet/<s> OpticalModule
The configured type is one of the SFP modules in step 2.
4 When failureCause indicates internalError, check for alarm 7011 5480. Do
the remedial action of the alarm or replace the SFP module to restore signal
throughput.
5 When failureCause indicates absentOm, install the SFP module so that an
operational state can be indicated.
6 When failureCause indicates unsupportedOm, install an SFP module that is
approved by Nortel Networks.
7 Confirm normal operation of the SFP module by observing these in the
response:
adminstate = unlocked, which applies to the component OpticalModule;
an SFP module can be enabled but not sending signals through
because the port itself is locked
operationalState = enabled
usageState = active or idle
insertedType = one of the following:
none for the default for an FP without SFP module sockets
--End--
Variable definitions
Variable Value
<lp> The number of the logical processor for the card.
<s> The number of the SONET or SDH port on the card. Use an asterisk (*)
to display all the ports on a card.
<e> The number of the Ethernet port on the card. Use an asterisk (*) to
display all the ports on a card.
Prerequisites
CAUTION
Risk of service interruption for a LAPS configuration
Other than up to 50 milliseconds of lost traffic due to a switchover in
a line automatic protection switching (LAPS) dual-FP configuration,
a service outage is possible if the command switch laps is not used
to switch activity while the spare card is locked. For example, you
might enter the command lock on a port on the active card while the
spare card or port is locked. A service outage will occur because both
the active and spare ports are locked. The command switch laps
checks whether the spare is in-service and available before
attempting the switchover. When the port or card is not available, this
command prevents the switchover.
Procedure steps
Step Action
CAUTION
Risk of service loss
Forcing an active (in-service) FP into the locked state causes the FP
to drop the traffic on the FP, depending on how equipment protection
is configured for that FP. If the FP is unspared, all traffic is dropped.
If the FP is a spared optical card, up to 50 milliseconds of traffic can
be lost. If the FP is a spared electrical card, up to 100 milliseconds of
traffic can be lost.
CAUTION
Risk of shelf reset
If you are locking an FP to remove it from the shelf, you must use the
following command:
lock -force Shelf Card/<m>
If you do not use this command, the Multiservice Switch 7400/15000/
20000 can reset when you remove the FP from the shelf.
--End--
Variable definitions
Variable Value
<m> The slot number of the processor card.
Locking a port
Lock a port during maintenance procedures to remove it from service. Locking
a port prevents the port from running the software defined in its logical
processor.
Prerequisites
CAUTION
Risk of service interruption for a LAPS configuration
Other than up to 50 milliseconds of lost traffic due to a switchover in
a line automatic protection switching (LAPS) dual-FP configuration,
a service outage is possible if the command switch laps is not used
to switch activity while the spare card is locked. For example, you
might enter the command lock on a port on the active card while the
spare card or port is locked. A service outage will occur because both
the active and spare ports are locked. The command switch laps
checks whether the spare is in-service and available before
attempting the switchover. When the port or card is not available, this
command prevents the switchover.
If you are unfamiliar with lock command concepts, see Nortel Multiservice
Switch 7400/15000/20000 Commands Reference (NN10600-050).
Perform the following procedure in operational mode. For more
information, see Operational mode (page 342).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<n> The instance number of the logical processor linked to the port.
(1 of 2)
Variable Value
<p> The port number.
<port> The port type.
(2 of 2)
Prerequisites
If you are unfamiliar with removing and replacing FPs, see Considerations
for replacing function processors (page 305).
For more information on the commands that are used in the following
procedure, see Nortel Multiservice Switch 7400/15000/20000 Commands
Reference (NN10600-050).
Perform the following procedure in operational mode. For more
information, see Operational mode (page 342).
Procedure steps
Step Action
1 If the card was configured for LAPS, ensure that LAPS is not degraded. (For
an electrical FP, skip this step.)
display laps/* osiState
Under osiAvail, determine if any LAPS has a status of degraded. If so, you
must determine the cause of the degradation. For example, if the mate port
is out of service, an active port can be degraded because it cannot be
switched over to an out-of-service port. You must fix any degraded laps on
either card before proceeding with this procedure.
2 Check all software alarms that are active on the node housing the FP being
replaced. All alarms are described in Nortel Multiservice Switch 6400/7400/
15000/20000 Alarms Reference (NN10600-500).
For a spared FP, address the remedial action of any alarm indicating that
the standby or mate FP is not available to take over the traffic of the active
FP.
For an unspared FP, consider the status of the far end and address the
worst problem first.
3 If your site records indicate that the network was configured to back up the
traffic of an unspared FP, removing the FP from service may cause the
network to reroute far-end traffic away from the FP. For example, the
configuration can have an intra-network card as opposed to an access card
or have a node connected to two nodes to split services. PNNI links may
have been set up to do this. If your site records indicate that one or more
PNNI links pass through the FP, busy or lock each of those links at the far
end.
4 Verify that the former standby card is now carrying traffic (is in service).
display Shelf Card/* sps
--End--
Variable definitions
Variable Value
<m> The slot number of the active card. For information about the command
lock, see Nortel Multiservice Switch 7400/15000/20000 Commands
Reference (NN10600-050).
Prerequisites
Perform the following procedure in operational mode. For more
information, see Operational mode (page 342).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<m> The slot number of the processor card.
Re-enabling an LP
Re-enable an LP by using the unlock command if you have disabled an LP
using the lock command.
Prerequisites
Perform the following procedure in operational mode. For more
information, see Operational mode (page 342).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<n> The number of the LP.
Prerequisites
CAUTION
Risk of data loss
When you reset or restart a processor card, it is temporarily unable
to provide service. During the time that the processor card is
restarting, data can be lost.
CAUTION
Risk of losing stable SVC connections
When you reset or restart a processor card, a loss of switched virtual
circuit (SVC) connections may occur. Although stable SVC calls
should remain active in a redundant processor configuration,
exercise caution when issuing this command.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<m> The slot number of the processor card.
Prerequisites
If you are unfamiliar with removing FPs from service, see Considerations
for replacing function processors (page 305).
Perform the following procedure in operational mode. For more
information, see Operational mode (page 342).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<m> The slot number of the standby card determined in this procedure. For
information about the command lock, see Nortel Multiservice Switch
7400/15000/20000 Commands Reference (NN10600-050).
Whenever a card is locked, the alarm 7012 0100 is generated.
Whenever a standby card is locked, the alarm 7054 0105 is generated.
The alarms are described in Nortel Multiservice Switch 6400/7400/
15000/20000 Alarms Reference (NN10600-500).
Prerequisites
If you are unfamiliar with removing FPs from service, see Considerations
for replacing function processors (page 305).
Perform the following procedure in operational mode. For more
information, see Operational mode (page 342).
Procedure steps
Step Action
1 Identify and record the software level or PCR that is running in the node
containing the standby FP. You will need it to label the PCR onto the
faceplate of the card.
display software avl
2 Block the standby card and ports from being put into service.
lock -force Shelf Card/<m>
3 If you are doing this procedure to replace an FP, return immediately to Nortel
Multiservice Switch 15000/20000 Installation, Maintenance, and Upgrade
Hardware (NN10600-130).
--End--
Variable definitions
Variable Value
<m> The slot number of the standby card determined in this procedure. For
information about the command lock, see Nortel Multiservice Switch
7400/15000/20000 Commands Reference (NN10600-050).
Whenever a card is locked, the alarm 7012 0100 is generated.
Whenever a standby card is locked, the alarm 7054 0105 is generated.
The alarms are described in Nortel Multiservice Switch 6400/7400/
15000/20000 Alarms Reference (NN10600-500).
Prerequisites
If you are unfamiliar with removing FPs from service, see Considerations
for replacing function processors (page 305).
Identify from your site records whether any private network-to-network
(PNNI) links pass through either of the FP pair. The procedure will indicate
when to remove the PNNI links from service.
An FP that supports only intra-card LAPS (single-FP LAPS) has port-to-
port sparing on the same card. For this configuration, follow the procedure
Removing from service an unspared FP (page 90).
Perform the following procedure in operational mode. For more
information, see Operational mode (page 342).
Procedure steps
Step Action
1 Identify and record the software level or PCR that is running in the node
containing the FP. You will need it to label the PCR onto the faceplate of the
card.
display software avl
4 Identify which SONET lines are providing service (as opposed to being on
hot standby).
display laps/* nearendrxactiveline
The lines with status working are providing service while the lines with
protec are on hot standby. When nearEndRequest indicates
signalFailure it usually means a cable has been cut
signalDegrade it usually means a bit error
forcedSwitch it means a manual switchover was invoked and the mate
port is not available
CAUTION
Risk of service interruption from a degraded LAPS
You must determine the cause of each degraded LAPS port because
a switchover to one means it can remain out of service longer than
50 milliseconds.
6 When removing the card from service for an upgrade or a redeployment (as
opposed to a failure), ensure that traffic is running on the mate FP, using
step 7 through step 8. If traffic is not running on the mate before the removal,
it is unlikely traffic will run on the replacement FP after the return to service.
7 Verify that the services are unlocked and enabled and that there are no
unexpected alarms.
d <service>/*
8 Verify that all connections are up and passing traffic and that there are no
signalling alarms.
d -o -c <service>/* <connection>/*
For example:
d -o -c atmif/* vcc/*
d -o -c fruni/* dlci/*
9 Check all software alarms that are active on the node housing the FP being
replaced. Address the remedial action of any alarm involving equipment or
software for the FP being replaced.
10 Prepare the far-end ports for the near-end ports being removed from
service. This step applies to any FP.
11 If your site records indicate that you have at least one PNNI link passing
through the FP to be removed from service, you must first busy or lock the
PNNI link at the far end to remove it from service. At the facility level of
operation, as opposed to the service level, move the PNNI traffic off the
target FP to its mate by following the procedure Switching SONET line
protection to the mate FP (page 96).
CAUTION
Risk of service interruption for a LAPS configuration
Other than up to 50 milliseconds of lost traffic due to a switchover in
a line automatic protection switching (LAPS) dual-FP configuration,
a service outage is possible if the command switch laps is not used
to switch activity while the spare card is locked. For example, you
might enter the command lock on a port on the active card while the
spare card or port is locked. A service outage will occur because
both the active and spare ports are locked. The command switch
laps checks whether the spare is in-service and available before
attempting the switchover. When the port or card is not available, this
command prevents the switchover.
12 Remove any traffic from the ports on the near-end target card to the mate
card and block the target card and ports from being put into service.
lock -force Shelf Card/<m>
When the dual-FP LAPS configuration involves 16-port OC-3/STM-1 cards,
you must use the command lock -force on the card instead of the command
switch laps. Otherwise the completion of the switchover can take days or be
indefinite.
Whether the card ports are configured as unidirectional or bidirectional, or
as a revertive or non-revertive mode, the command lock handles all
associated connections. For information about these attributes, refer to
Configuring line and equipment protection for Multiservice Switch 15000
and Multiservice Switch 20000 optical interfaces (page 207).
13 Observe the traffic on the active card to ensure it is flowing. Use appropriate
test equipment to monitor the cell counts.
14 If the switchover did not occur, abort this procedure and refer to Nortel
Multiservice Switch 7400/15000/20000 Troubleshooting (NN10600-520) for
diagnosing FPs. For FP fiber optic cards with LAPS, if the active (target) and
standby (mate) LEDs on the faceplates do not swap within 50 milliseconds,
the switchover may not occur.
--End--
Variable definitions
Variable Value
<connection> The type of connection for a particular service. For example, vcc for atm
or dlci for FrUni.
<m> The slot number of the standby card configured in this procedure. For
information about the command lock, see Nortel Multiservice Switch
7400/15000/20000 Commands Reference (NN10600-050).
Whenever a card is locked, the alarm 7012 0100 is generated.
Whenever a standby card is locked, the alarm 7054 0105 is generated.
The alarms are described in Nortel Multiservice Switch 6400/7400/
15000/20000 Alarms Reference (NN10600-500).
<service> The service running on a particular card. For example, atmif or FrUni.
Prerequisites
If you are unfamiliar with removing FPs from service, see Considerations
for replacing function processors (page 305).
Identify from your site records whether any private network-to-network
(PNNI) links pass through the FP. The procedure will indicate when to
remove the PNNI links from service.
Perform the following procedure in operational mode. For more
information, see Operational mode (page 342).
Procedure steps
Step Action
1 Identify and record the software level or PCR that is running in the node that
has the standby FP.
display software avl
The response indicates the configured (provisioned) software that is running
through the node, not the software that might be loaded on the inactive CP.
When removing a card for re-deployment or repair, it is important to know
what version of software was running on it. Label the PCR onto the
faceplate.
2 Typically, when an unspared FP is removed from service, all traffic to that FP
is dropped.
CAUTION
Risk of service interruption
When an unspared card is removed from service either manually or
automatically by the system (for example, by the command lock), all
traffic to the card is dropped. If you must remove an in-service card
from service, ensure that you do it during a period of lowest traffic for
that card, and you do not delay inserting the replacement card.
3 Check all software alarms that are active on the node housing the FP being
replaced. Address the remedial action of any alarm indicating that the
standby or mate FP is not available to take over the traffic of the active FP.
If your site records indicate that the network was configured to back-up the
traffic of an unspared FP, removing the FP from service may cause the
network to reroute far-end traffic away from the FP. For example, the
configuration can have an intra-network card as opposed to an access card
or have a node connected to two nodes to split services. PNNI links may
have been set up to do this. If your site records indicate that one or more
PNNI links pass through the FP, busy or lock each of those links at the far
end.
4 Prevent a node reset by entering the command:
lock -force Shelf Card/<m>
Whenever a card is locked, the alarm 7012 0100 is generated. Whenever a
standby card is locked, the alarm 7054 0105 is generated. The alarms are
described in Nortel Multiservice Switch 6400/7400/15000/20000 Alarms
Reference (NN10600-500).
For a VSP3 card, do not lock the gigabit Ethernet ports.
5 If you are doing this procedure to replace an FP, return immediately to Nortel
Multiservice Switch 15000/20000 Installation, Maintenance, and Upgrade
Hardware (NN10600-130) to replace the out-of-service FP.
If you are doing this procedure to test an FP, return immediately to Nortel
Multiservice Switch 7400/15000/20000 Troubleshooting (NN10600-520).
--End--
Variable definitions
Variable Value
<m> The slot number of the card. For information about the command lock,
see Nortel Multiservice Switch 7400/15000/20000 Commands
Reference (NN10600-050).
Returning an FP to service
After inserting the replacement FP into its slot, return the FP to service.
Prerequisites
If you are unfamiliar with removing FPs from service, see Considerations
for replacing function processors (page 305).
Monitor for alarms generated against the equipment that the FP connects
to. While the replaced FP is returning to service, alarms generated for
linked equipment can help indicate the progressive operation of the
replaced FP, and the status of connected equipment. All alarms are
described in Nortel Multiservice Switch 6400/7400/15000/20000 Alarms
Reference (NN10600-500).
Perform the following procedure in operational mode. For more
information, see Operational mode (page 342).
Procedure steps
Step Action
2 While the replacement FP is inserted and out of service, test each port
according to the type of FP as described in Nortel Multiservice Switch 7400/
15000/20000 Troubleshooting (NN10600-520). This is optional.
If the replacement card is a 4-port DS3, see also Nortel Multiservice Switch
15000/20000 Installation, Maintenance, and Upgrade Hardware
(NN10600-130) about changing the FP configuration for a replacement
card.
3 As required, return to service any equipment that is involved in the port
connection up to the far-end termination. If the equipment is other than
Nortel Multiservice Switch equipment, it will also have to be unlocked. Since
the FP is still locked, Multiservice Switch system and far-end alarms will still
be generated.
4 After port testing passes, unlock the FP so that it can return to service.
unlock Shelf Card/<m>
Whenever a card is unlocked, the alarm 7012 0100 is generated. Whenever
a standby card is unlocked, the alarm 7054 0105 is generated.
Wait until the cycling of the LEDs ends at fast flashing green. If the LED
stays solid red after loading is attempted, the card is an incompatible vintage
or was previously loaded with software that is incompatible with the current
software running on the node. Use a compatible card. If the LED is other
--End--
Variable definitions
Variable Value
<m> The slot number of the processor card.
<n> The number of the LP. Note the LP number of the in-service card.
Prerequisites
CAUTION
Risk of service loss
A CP switchover can result in loss of service. See Understanding CP
equipment sparing (page 248) for more information.
If the FP is a spared optical card, up to 50 milliseconds of hot spared
services can be lost. If the FP is a hot spared electrical card, up to
100 milliseconds of hot spared services can be lost. Hot sparing
applies only to the Multiservice Switch 15000 and the Multiservice
Switch 20000.
You can also schedule a switchover for a later time and cancel a
scheduled switchover. You cannot schedule a switchover for the CP,
that is, Lp/0.
Perform the following procedure in operational mode. For more
information, see Operational mode (page 342).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<n> The number of the LP.
Prerequisites
This procedure applies only to the Nortel Multiservice Switch 15000 or a
Multiservice Switch 20000. You cannot do optical card switchovers on a
Multiservice Switch 7400.
The sparing arrangement must provide an FP card which is the mate for
the FP to be replaced. These are pairs of cards in adjacent slots (that is,
slots 2 and 3, slots 4 and 5, slots 6 and 7) up to and including slots 14 and
15.
Refer to the Network Specification Book to determine which SONET ports
are configured on the FP to be replaced.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<m> The number of the LAPS instance on the FP to be replaced.
<n> The number of the LP associated with the FP to be replaced.
<o> The number of the SONET ports configured on the LP to be replaced.
<p> The number of the SONET ports configured on the LP located on the
far-end Nortel Multiservice Switch node.
Temporarily disabling an LP
Disable an LP using the lock command to prevent it from running the software
configuration defined in its LPT. Since a locked LP cannot run its software, it
is disabled.
Prerequisites
If you are unfamiliar with the concepts relating to locking LPs, see Locking
and disabling LPs (page 276) for information.
Perform the following procedure in operational mode. For more
information, see Operational mode (page 342).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<n> The number of the LP. You cannot lock Lp/0 (the CP).
After you unlock an FP in a Nortel Multiservice Switch 7400 node, it loads and
starts running its logical processor (if defined). After you unlock an FP in a
Multiservice Switch 15000 or Multiservice Switch 20000 node, it restarts its
logical processor (if defined).
Prerequisites
Perform the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<m> The slot number of the processor card.
Unlocking a port
Unlock a port after you have completed maintenance procedures to return it
to service. Unlocking a port allows the port to run the software defined in its
logical processor.
Prerequisites
If you are unfamiliar with lock command concepts, see Nortel Multiservice
Switch 7400/15000/20000 Commands Reference (NN10600-050).
Perform the following procedure in operational mode. For more
information, see Operational mode (page 342).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<n> The instance number of the logical processor linked to the port.
<p> The port number.
<port> The port type.
EM
LogicalProcessor (Lp)
<port>
Test
Setup
purpose
type
frmSize (size)
frmPatternType (fpt)
customizedPattern (cp)
dataStartDelay (dsd)
displayInterval (di)
duration
Results
elapsedTime
timeRemaining
causeOfTermination
bitsTx
bytesTx
frmTx
bitsRx
bytesRx
frmRx
erroredFrmRx
bitErrorRate
PPT 2930 022 AA
Navigation
Disabling and enabling hot standby for CP switchover (page 104)
Locking external timing ports (page 105)
Unlocking external timing ports (page 106)
Configuring CP equipment sparing (page 107)
Changing the CP equipment protection mode (page 109)
Adding a spare CP to a single-CP node (page 111)
Removing a spare CP (page 113)
Replacing a CP in a single-CP node (page 115)
Replacing a CP using a donor node and backup (page 117)
Reconfiguring a donor CP (page 119)
Replacing a CP using a donor node only (page 121)
Replacing a CP using a backup only (page 123)
Replacing a CP without a donor node or backup (page 125)
Replacing a CP in a two-CP node (page 126)
Upgrading a CP2 to a CP3 in a single-CP node (page 128)
Upgrading a CP2 to a CP3 in a two-CP node (page 129)
The standards from the Open Standards Interface (OSI) group use different
terminology when referring to standby modes. When you display the
standbyStatus attribute for the CP LP (Lp/0), it reports notSet for both standby
modes.
Prerequisites
Hot standby for CP switchover does not support the removal of the active
CP. Removing the active CP causes unexpected behavior on the bus of a
Nortel Multiservice Switch 7400 node, or the fabric of Multiservice
Switch 15000 and Multiservice Switch 20000 nodes. It can cause all
processor cards to reset.
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Prerequisites
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<external_port> EDS1 (for DS1 lines) or EE1 (for E1 lines).
Prerequisites
Replacing a BITS termination panel does not require a shelf reset.
Network synchronization will return to the BITS source automatically, if it
is provisioned as the reference source.
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<external_port> EDS1 (for DS1 lines) or EE1 (for E1 lines).
Prerequisites
In you are unfamiliar with CP sparing concepts, see Understanding CP
equipment sparing (page 248).
For Nortel Multiservice Switch 15000 and Multiservice Switch 20000
nodes, the main CP is in slot 0, while the spare CP is in slot 1. Ensure the
main CP and the spare CP are of the same type by verifying that the first
6 characters of their product engineering codes (PECs) are identical. As
well, the amount of memory and disk space must be the same.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<m> The slot number of the main card. Multiservice Switch nodes numbers its
slots starting at 0. The main CP is in slot 0.
<n> The slot number of the spare card. Multiservice Switch nodes number
their slots starting at 0. The main CP is always in slot 0. In Multiservice
Switch 15000 and Multiservice Switch 20000 nodes, the spare CP is in
slot 1. In a Multiservice Switch 7400 node, the spare CP is in the last slot
of the shelf.
Prerequisites
If you are unfamiliar with CP sparing concepts, see Understanding CP
equipment sparing (page 248).
If hot CP standby is enabled (hot), then the maxNumberJournalFiles
attribute in ProvisioningSystem must be enabled by setting it to a value
other than none. See the following note for additional information on
support of CPSO and hitless software migration (HSM) by the
maxNumberJournalFiles attribute of the Prov component.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<cpEquipmentProtection> Hot (CP equipment protection is enabled) or cold (CP equipment
protection is disabled).
If you no longer want to use a spare CP, you must physically remove the spare
CP, then delete its configuration. See Removing a spare CP (page 113) for
more information.
Prerequisites
If you are unfamiliar with CP sparing in a single-CP node, see
Considerations for adding a spare CP to a single-CP node (page 252).
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
Two instances of the Disk component appear, one for each CP.
8 Synchronize the new standby disk with the active disk.
synchronize Fs
When the synchronization is complete, an alarm indicates that the file
system is now synchronized.
--End--
Variable definitions
Variable Value
<c> The card type (CP, CPeD, or CPeE).
<m> The slot number of the spare CP. Multiservice Switch 15000 and
Multiservice Switch 20000 nodes designate slot 1 for the spare CP. In
Multiservice Switch 7400 nodes, the spare CP is located in the last slot
of the shelf.
Removing a spare CP
Remove a spare CP to disable CP redundancy. When you remove a spare CP
to disable CP redundancy, you must also delete its configuration.
Prerequisites
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<m> The slot number of the spare CP. Multiservice Switch 15000 and
Multiservice Switch 20000 nodes designate slot 1 for the spare CP. In
Multiservice Switch 7400 nodes, the spare CP is located in the last slot
of the shelf.
Procedure steps
Step Action
--End--
Prerequisites
For information on physically replacing a CP, see either Nortel Multiservice
Switch 7400 Installation, Maintenance, and Upgrade Hardware
(NN10600-175) or Nortel Multiservice Switch 15000/20000 Installation,
Maintenance, and Upgrade Hardware (NN10600-130).
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
1 If necessary, force the main CP on the donor node to become the active CP.
switchover Lp/0
2 Remove the spare CP from the shelf of the donor node. You will install this
CP on the failed node after you have configured a new spare CP on the
donor node.
3 Insert a new CP into the spare slot of the donor node.
For Nortel Multiservice Switch 15000 and Multiservice Switch 20000 nodes
use slot 1 for the spare CP. In Multiservice Switch 7400 nodes, the spare CP
is located in the last slot of the shelf.
Nortel Networks recommends that the new spare CP have the same size
disk as the main CP.
4 Synchronize the new standby disk with the active disk on the donor node.
synchronize Fs
This step can take several hours, depending on the amount of data stored
on the active disk and the difference between the two disks.
5 Remove the failed CP from the shelf of the failed node.
6 Install the CP you removed from the donor node into the main slot (slot 0) of
the failed node.
7 When the CP comes up (LED is lit solid green), clean up the disk. Remove
any unnecessary files including unused software, unused provisioning files,
and the spooling files stored in the /spooled/closed directory. For
information on removing files, see the following:
tidy Prov, tidy Sw, remove Sw Av, and remove Fs commands in Nortel
Multiservice Switch 7400/15000/20000 Commands Reference
(NN10600-050)
Nortel Multiservice Switch 7400/15000/20000 Installation Software
(NN10600-270)
8 Change the node name, node ID, and the addresses of the IPIVC interface,
the IPIFR interface, or the OAM Ethernet port to the values of the failed
node. This step allows you to restore your connection to the network and
Multiservice Data Manager.
For information on changing the node name and ID, see Configuring node
identification (page 14). For information on changing the address of IPIVC
or IPIFR, see Nortel Multiservice Switch 7400/15000/20000 Administration
Network Management Connectivity (NN10600-271).
9 Restore the files from the last Multiservice Data Manager backup. See
Nortel Multiservice Data Manager ConfigurationTools (241-6001-023) for
procedures on file restore.
10 Activate the provisioning view that was running when the last backup to
Multiservice Data Manager was made:
reloadCp -file(<view>) Lp/0
If the provisioning view changed since the last Multiservice Data Manager
backup, you must manually reconfigure the changes.
--End--
Variable definitions
Variable Value
<view> The name of the provisioning view.
Reconfiguring a donor CP
Reconfigure a donor CP to establish network management connectivity and
identify the node as a unique node in the network.
Prerequisites
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
1 Synchronize the new standby disk with the active disk on the donor node.
synchronize Fs
This step can take several hours, depending on the amount of data stored
on the active disk and the difference between the two disks.
2 Remove the failed CP from slot in the failed node.
3 Install the CP you removed from the donor node into the main slot (slot 0) of
the failed node.
4 When the CP comes up (LED is lit solid green), clean up the disk. Remove
any unnecessary files including unused software, unused provisioning files,
and the spooling files stored in the /spooled/closed directory. For
information on removing files, see the following:
tidy Prov, tidy Sw, remove Sw Av, and remove Fs commands in Nortel
Multiservice Switch 7400/15000/20000 Commands Reference
(NN10600-050)
Nortel Multiservice Switch 7400/15000/20000 Installation Software
(NN10600-270)
5 Change the node name, node ID, and the addresses of the IPIVC interface,
the IPIFR interface, or the OAM Ethernet port to the values of the failed
node. This step allows you to restore your connection to the network and
Nortel Multiservice Data Manager workstation.
For information on changing the node name and ID, see Configuring node
identification (page 14). For information on changing the address of IPIVC
or IPIFR, see Nortel Multiservice Switch 7400/15000/20000 Administration
Network Management Connectivity (NN10600-271).
6 Restore the files from the last Multiservice Data Manager backup. See
Nortel Multiservice Data Manager ConfigurationTools (241-6001-023) for
procedures on file restore.
7 Activate the provisioning view that was running when the last backup to
Multiservice Data Manager was made.
reloadCp -file(<view>) Lp/0
If the provisioning view changed since the last Multiservice Data Manager
backup, you must manually reconfigure the changes.
--End--
Variable definitions
Variable Value
<view> The name of the provisioning view.
Prerequisites
For information on physically replacing a CP, see either Nortel Multiservice
Switch 7400 Installation, Maintenance, and Upgrade Hardware
(NN10600-175) or Nortel Multiservice Switch 15000/20000 Installation,
Maintenance, and Upgrade Hardware (NN10600-130).
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
1 If necessary, force the main CP on the donor node to become the active CP.
switchover Lp/0
2 Remove the spare CP from the shelf of the donor node. You will install this
CP on the failed node after you have configured a new spare CP on the
donor node.
3 Insert a new CP into the spare slot of the donor node. For Multiservice
Switch 15000 and Multiservice Switch 20000 nodes the spare CP resides in
slot 1. For Multiservice Switch 7400 nodes, the spare CP resides in the last
slot of the shelf.
Nortel Networks recommends that the new spare CP have the same size
disk as the main CP.
4 Synchronize the new standby disk with the active disk on the donor node.
synchronize Fs
This step can take several hours, depending on the amount of data stored
on the active disk and the difference between the two disks.
5 Remove the failed CP from the slot in the failed node.
6 Install the CP you removed from the donor node into the main slot (slot 0) of
the failed node.
7 When the CP comes up (LED is lit solid green), clean up the disk. Remove
any unnecessary files including unused software, unused provisioning files,
and the spooling files stored in the /spooled/closed directory. For
information on removing files, see the following:
tidy Prov, tidy Sw, remove Sw Av, and remove Fs commands in Nortel
Multiservice Switch 7400/15000/20000 Commands Reference
(NN10600-050)
Nortel Multiservice Switch 7400/15000/20000 Installation Software
(NN10600-270)
8 Change the node name, node ID, and the addresses of the IPIVC interface,
the IPIFR interface or the OAM Ethernet port to the values of the failed node.
This step allows you to restore your connection to the network and
Multiservice Data Manager.
For information on changing the node name and ID, see Configuring node
identification (page 14). For information on changing the address of IPIVC
or IPIFR, see Nortel Multiservice Switch 7400/15000/20000 Administration
Network Management Connectivity (NN10600-271).
9 Install the application versions (AVs) for the node using the procedures
described in Nortel Multiservice Switch 7400/15000/20000 Installation
Software (NN10600-270).
10 Manually reconfigure the node.
--End--
Prerequisites
For information on physically replacing a CP, see either Nortel Multiservice
Switch 7400 Installation, Maintenance, and Upgrade Hardware
(NN10600-175) or Nortel Multiservice Switch 15000/20000 Installation,
Maintenance, and Upgrade Hardware (NN10600-130).
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
6 Restore the files from the last Multiservice Data Manager backup. See
Nortel Multiservice Data Manager ConfigurationTools (241-6001-023) for
procedures on file restore.
7 Activate the provisioning view that was running when the last backup to
Multiservice Data Manager was made.
reloadCp -file(<view>) Lp/0
If the provisioning view changed since the last Multiservice Data Manager
backup, you must manually reconfigure the changes.
--End--
Variable definitions
Variable Value
<view> The name of the provisioning view.
Prerequisites
For information on physically replacing a CP, see either Nortel Multiservice
Switch 7400 Installation, Maintenance, and Upgrade Hardware
(NN10600-175) or Nortel Multiservice Switch 15000/20000 Installation,
Maintenance, and Upgrade Hardware (NN10600-130).
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
6 Reinstall the application versions (AVs) for the node using the procedures
described in Nortel Multiservice Switch 7400/15000/20000 Installation
Software (NN10600-270).
7 Manually reconfigure the node.
--End--
Prerequisites
In the unlikely event that both CPs fail simultaneously or the standby CP
is unavailable to take over the traffic of the active CP, follow the
procedures in Replacing a CP in a single-CP node (page 115).
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
1 If necessary, force the CP you want to remove to become the standby CP.
switchover Lp/0
2 Lock the standby CP in order to remove it without losing traffic.
lock -force Shelf Card/<m>
3 Have someone be ready at the CP to continue with the physical removal and
insertion procedures. The CP can be removed when the availabilityStatus is
offLine and the CP LED indicates solid red. See Nortel Multiservice Switch
15000/20000 Installation, Maintenance, and Upgrade Hardware
(NN10600-130) or Nortel Multiservice Switch 7400 Installation,
Maintenance, and Upgrade Hardware (NN10600-175), for information on
removing a CP.
4 When the replacement CP is inserted into the slot, you can unlock the CP.
As a result, the new CP starts loading the software.
unlock Shelf Card/<m>
5 After the new CP starts loading software (its status LED is fast flashing
green), verify that the disks on both CPs are available.
list Fs Disk/*
Two instances of the Disk component appear, one for each CP.
Attention: If the new CP has the same volume name as the active CP, the new
standby disk is automatically synchronized with the active disk. Disk synchronization
can take a long time (up to an hour or more). When synchronization is complete, an
alarm indicates that the file system is now synchronized.
6 If the new standby disk did not automatically synchronize with the active
disk, manually synchronize the two disks:
synchronize Fs
This command can take a long time to execute (up to an hour or more).
When synchronization is complete, an alarm indicates that the file system is
now synchronized.
7 Leave the standby CP as available (not active). It is not necessary to restore
it to active status because the system functions normally regardless which
one is currently active.
--End--
Variable definitions
Variable Value
<m> The slot number of the new processor card.
Before upgrading a CP2 to a CP3, ensure that the node is operating with
software that supports the CP3. Refer to the table on minimum CP software
requirements in Nortel Multiservice Switch 15000/20000 Fundamentals
Hardware (NN10600-120).
See Nortel Multiservice Switch Release Notes to see which software vintage
supports the CP3, or the table of minimum CP software vintages in Nortel
Multiservice Switch 15000/20000 Fundamentals Hardware
(NN10600-120). See Nortel Multiservice Switch 7400/15000/20000
Installation Software (NN10600-270) to verify the following:
the vintage of the software that the node is currently using
whether the application version list (AVL) of the node contains application
versions that support PowerPC (ppc) applications
Also, you can reduce the time required to upgrade to a CP3 by doing the
following:
turn off data collection, to minimize file system activity
minimize the accounting data on the disk
keep only the minimum number of software versions on the disk
CAUTION
Upgrading a CP2 to a CP3 has the same service impact as replacing
a CP2. Some new call connections may not be set up during CP
switchover.
CP3 control processors are used only in Multiservice Switch 15000 and
Multiservice Switch 20000 nodes.
Attention: A two-CP node should operate with a CP3 and a CP2 only during
the upgrade procedure. Normal operation requires that a two-CP node
operates with two identical CPs, either two CP3s or two CP2s.
CAUTION
Upgrading a CP2 to a CP3 has the same service impact as replacing
a CP2. Some new call connections may not be set up during CP
switchover.
Prerequisites
Before upgrading a CP2 to a CP3, ensure that the node is operating with
software that supports the CP3.
The CP3 requires PowerPC applications. Before downloading the
software to run on the CP3, ensure that the processorTargets attribute of
the Software Download component is set to i960 ppc.
You can reduce the time required to upgrade to a CP3 by turning off data
collection, minimizing the accounting data on the disk, and keeping only
the minimum number of software versions on the disk.
Before migrating a Multiservice Switch 15000 platform from a CP2
processor to a CP3, ensure there is enough available space on the CP2,
see Determining file system capacity (page 187). If there is not enough
available space, the CP2 may not be able to synchronize its disk with the
CP3 when trying to revert to CP2 after a CP3 switchover.
See Timeout for a subsequent CP switchover (page 255) for information
about performing CP switchover and disconnecting the Ethernet cable on
the CP.
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
See the Nortel Multiservice Switch Release Notes to see which software
vintage supports the CP3.
See Nortel Multiservice Switch 7400/15000/20000 Installation Software
(NN10600-270) to verify the following:
Procedure steps
Step Action
list Fs Disk/*
If the new CP3 has the same volume name as the active CP, the new
standby disk is automatically synchronized with the active disk. Disk
synchronization can take up to an hour or more. When synchronization is
complete, an alarm indicates that the file is now synchronized.
8 If the new standby disk did not automatically synchronize with the active
disk, manually synchronize the two disks.
synchronize Fs
You can check on the progress of the synchronization by entering.
d Fs synchstatus
d Fs synchprogres
9 Once the file system is synchronized and the new CP3 is available, force the
remaining CP2 to become the standby CP.
switchover Lp/0
11 Once the file system is synchronized, change the control back to the starting
configuration, making CP0 the active processor.
switchover Lp/0
--End--
Variable definitions
Variable Value
<x> The slot number of the inactive processor card, either 0 or 1.
Prerequisites
There should be no BITS or SETS features configured.
Active and standby CPs are CP NTNQ01AA.
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
For PEC code description of the termination panels and cables see Nortel
Multiservice Switch 7400 Fundamentals Hardware (NN10600-170).
Procedure steps
Step Action
--End--
Prerequisites
There should be no BITS or SETS features configured.
Active and standby CPs are CP NTNQ03AA.
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
For PEC code description of the termination panels and cables see Nortel
Multiservice Switch 7400 Fundamentals Hardware (NN10600-170).
Procedure steps
Step Action
--End--
Navigation
Configuring the CP OAM Ethernet port (page 136)
Enabling CP switchover for a CP OAM Ethernet port failure (page 141)
Disabling CP switchover for a CP OAM Ethernet port failure (page 142)
Changing the statistics gathered from the CP OAM Ethernet port
(page 143)
Configuring the line speed of the OAM Ethernet port on a CP3 control
processor (page 144)
Changing the mode of the OAM Ethernet port on a CP3 control processor
(page 145)
For information on configuring IP security (IPSec) for OAM traffic, see
Nortel Multiservice Switch 7400/15000/20000 Administration Network
Management Connectivity (NN10600-271) and Nortel Multiservice Switch
7400/15000/20000 Security (NN10600-601).
Attention: The CP OAM Ethernet port supports static routes and open
shortest path first (OSPF) passive interface. The CP OAM Ethernet port
does not support any other routing protocols or any other shortest path first
(OPSF) configurations. Configure the CP OAM Ethernet port with static
routes or as an open shortest path first (OSPF) passive interface.
Prerequisites
If you are unfamiliar with CP OAM Ethernet port configuration, see
Understanding the control processor OAM Ethernet port (page 314).
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
1 Add the oamEnet and ip features to the feature list of the CP.
set Software Lpt/CP featureList oamEnet ip
Attention: The oamEnet and ip features must be part of the software application
version list (AVL). For more information on adding features to the AVL, see Software,
applications, and features additions and updates (page 48).
2 Add the OamEthernet component to the logical processor for the CP.
add LogicalProcessor/0 oamEnet/0
--End--
Variable definitions
Variable Value
<broadcastaddress> The broadcast address.
<cost> A relative metric value (ranges from 1 to +65535) assigned to the
static routethe assigned cost judges route preference.
(1 of 2)
Variable Value
<destmask> The subnetwork mask used with the IP address.
If <ipAddress> specifies a host, provision <destmask> as
255.255.255.255. Also, provision locally attached hosts as Arp
HostEntry components instead of a Static component entry.
For more information on the IP Static RouteEntry component, see
Nortel Multiservice Switch 7400/15000/20000 IP Fundamentals
(NN10600-800).
<IPaddress> The IP address of the OAM Ethernet port.
<ipAddress2> The IP address of the remote management workstation (can refer
either to a specific node or to a network).
<netmaskaddress> The netmask address.
<nextHop_ipAddress> The IP address of the next router in the path to the destination. Since
this is a specific node and cannot be a network, there is no
subnetwork mask.
<tos> The type of service (currently, only the default value of 0 is
supported).
(2 of 2)
EM
LogicalProcessor/0 (Lp/0)
OamEthernet/0 (OamEnet/0)
Provisioned (Prov)
applicationFramerName (framer)
switchoverOnFailure (switch)
extendedStatistics (extStats)
Operational (Oper)
macAddress
activeStatus
standbyStatus
Test
type
causeOfTermination
testResult
PPT 2930 014 AA
Prerequisites
If you are unfamiliar with CP OAM Ethernet port concepts, see
Understanding the control processor OAM Ethernet port (page 314).
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Prerequisites
If you are unfamiliar with CP OAM Ethernet port concepts, see
Understanding the control processor OAM Ethernet port (page 314).
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Prerequisites
If you are unfamiliar with CP OAM Ethernet port, see Understanding the
control processor OAM Ethernet port (page 314).
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<value> Enabled or disabled. The default is disabled.
Configuring the line speed of the OAM Ethernet port on a CP3 control
processor
Configure the line speed of the OAM Ethernet port on a CP3 control processor
to match the requirements of the far end.
Prerequisites
If you are unfamiliar with CP OAM Ethernet port concepts, see
Understanding the control processor OAM Ethernet port (page 314).
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<value> AutoConfig, tenMeg, or hundredMeg. The default is autoConfig.
Attention: When set to autoConfig, the CP3 automatically sets the line
speed to match the requirements of the far-end hub. The actual line
speed can be obtained from the actualLineSpeed attribute.
Prerequisites
If you are unfamiliar with CP OAM Ethernet port concepts, see
Understanding the control processor OAM Ethernet port (page 314).
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<value> AutoConfig, half, or full. The default is autoConfig.
Attention: When set to autoConfig, the CP3 automatically sets the
duplex mode to match the requirements of the far end hub. The actual
duplex mode can be obtained from the actualDuplexMode attribute.
Navigation
Adding a channel to a port (page 148)
Adding an LP and linking it to an LPT (page 150)
Adding an LPT (page 153)
Adding an Sts component to a port with the FP is operating with a single
path (page 155)
Adding an Sts component to a port when the FP is operating with multiple
paths (page 156)
Changing the LPT used by an LP (page 159)
Configuring ports on an LP (page 160)
Adding the NPU service bundle (page 162)
Configuring the software features of an LPT (page 164)
Attention: This procedure does not apply to the OC-48/STM-16 ATM with
APS FP. See instead the procedure Adding an Sts component to a port with
the FP is operating with a single path (page 155) or Adding an Sts
component to a port when the FP is operating with multiple paths (page 156).
Prerequisites
To determine whether an FP supports channelization, see appropriate list
of configuration parameters in Nortel Multiservice Switch 7400/15000/
20000 Fundamentals FP Reference (NN10600-551).
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<c> The channel type for the port.
<n> The LP number.
<p> The port number.
<port> The port type.
<r> The channel number. See Nortel Multiservice Switch 7400/15000/
20000 Fundamentals FP Reference (NN10600-551) for valid values
for <r>.
<rate> The timeslot data rate.
<t> The list of timeslots.
Prerequisites
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
1 Display existing LPTs and their features to determine if any are suitable.
display Sw Lpt/* featureList
If a suitable LPT does not exist, create one using the procedure Adding an
LPT (page 153).
2 Add a LogicalProcessor (Lp) component.
add Lp/<n>
3 Link the LP to an LPT:
set Lp/<n> logicalProcessorType Sw Lpt/<lpt_name>
4 Set the main card for the LP.
set Lp/<n> mainCard Shelf Card/<m>
5 If necessary, set the spare card for the LP.
set Lp/<n> spareCard Shelf Card/<m>
6 If you are configuring a one-for-n sparing configuration, repeat step 2 to
step 5 for each FP in the sparing configuration.
--End--
Variable definitions
Variable Value
<lpt_name> The name of the LPT you want to use.
<m> The slot number of the main card. Multiservice Switch nodes number
their slots starting at 0.
<n> The number of the LP, from 1 through 15. The system reserves 0 for
the CP.
match. For FPs, the first six digits (four letters and two numbers) must
match.
For the sparing of MSA32 DS1 FPs, there are 1-slot and 2-slot cards with
different PECs that can spare each other. For the sparing of MSA32 E1
FPs, there are 1-slot and 2-slot cards with different PECs that can spare
each other. For example, the same sparing configuration can contain
1-slot and 2-slot FPs with or without the optical ports. The combinations of
cards are identified in the FP descriptions in Nortel Multiservice Switch
7400 Fundamentals Hardware (NN10600-170).
For MSA32 FP sparing, electrical interfaces are protected inter-card
(electrical sparing protection) while optical interfaces are protected intra-
card (APS line protection). Regardless of either PEC or card type:
DS1 FPs can only spare other DS1 FPs and only for electrical
interfaces
E1 FPs can only spare other E1 FPs and only for electrical interfaces
DS1 and E1 MSA8 FPs can only spare other DS1 and E1 MSA8 FPs of
the same kind. Sparing MSA8 FPs with MSA32 FPs is not supported.
For information on creating an LPT, see Adding an LPT (page 153). For more
information on sparing, see Understanding equipment protection for
Multiservice Switch electrical interfaces (page 258).
Once you have the software and sparing configured, you can configure the
ports on the processor card by adding port subcomponents to the
LogicalProcessor component. For information on configuring ports, see
Configuring ports on an LP (page 160).
Adding an LPT
Add an LPT to define a group of software features you can assign to an LP.
You can only use features that are part of a software application version (AV)
currently available on the node. You can assign more than one feature to an
LPT.
Prerequisites
CAUTION
Risk of processor memory fragmentation
Processor memory can become fragmented as software features
are added and deleted through configuration and activation
cycles. To ensure optimal use of FP memory, always specify the
features in order of priority, with the first feature being the feature
that you want the best performance. Otherwise, once a certain
level of fragmentation has occurred, it might not be possible to
load new software. In the worst case, FPs may reset.
Exactly which combinations of features you can use depends on the type
of the processor card you intend to associate with the LPT (through the
LP). For a list of supported feature combinations, see Nortel Multiservice
Switch Release Notes.
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<lpt_name> A name for the LPT. The name can contain up to 25 alphanumeric
characters. The system converts the name to all uppercase letters.
<features> A list of the features of the LPT, separated by spaces.
Make sure you specify the features in order of priority. Make the first
feature on the list the one for which you want the best performance.
Prerequisites
See Nortel Multiservice Switch 7400/15000/20000 Fundamentals FP
Reference (NN10600-551) for the appropriate values for the Sts
component and the concatenation level.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<c> The concatenation level.
<n> The LP number.
<p> The port number.
<path> The path type.
<port> The port type.
For example, for the OC-48/STM-16 ATM FP with APS, you need to add the
first Sts component with a value 0 and set its concatenation level. Then you
add the second Sts component with a value of 12 and set its concatenation
level.
Prerequisites
See Nortel Multiservice Switch 7400/15000/20000 Fundamentals FP
Reference (NN10600-551) for the maximum number of Sts components
you can define.You do not need to define all the available Sts components
on a port if they are not all needed.
See Nortel Multiservice Switch 7400/15000/20000 Fundamentals FP
Reference (NN10600-551) for the appropriate values for the Sts
component and for the concatenation level.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<c> The concatenation level.
<n> The LP number.
<r> The Sts component instance.
<p> The port number.
<path> The path type.
<port> The port type.
Prerequisites
Do the following procedure in operational mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<n> The number of the LP.
Prerequisites
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
1 Display existing LPTs and their features to determine if any are suitable.
display Sw Lpt/* featureList
If a suitable LPT does not exist, create one using the procedure Adding an
LPT (page 153).
2 Set the LPT for the LP.
set Lp/<n> logicalProcessorType Sw Lpt/<lpt_name>
--End--
Variable definitions
Variable Value
<lpt_name> The name of the LPT you want to use.
<n> The number of the LP.
Configuring ports on an LP
For each LP, you must configure the ports that exist on the processor card.
See Nortel Multiservice Switch 7400/15000/20000 Fundamentals FP
Reference (NN10600-551) for specific types and the number of ports,
including tributary ports, that can be configured.
You can spare a maximum of four ports on an 8-port DS1/E1 IMA card using
a single termination panel. The configured ports must be in the range of 0 to
3 or 4 to 7. If you do not connect a sparing panel when a port has been
configured, the FP poll for the missing connection and causes a click in the
panel serving the other bank of ports.
Sts andVc4 components are not automatically created when you add a port,
so you need to add them separately. See the procedure Adding an Sts
component to a port with the FP is operating with a single path (page 155) or
Adding an Sts component to a port when the FP is operating with multiple
paths (page 156).
If this is a channelized FP that supports more than one channel, add additional
channels using the procedure Adding a channel to a port (page 148).
Prerequisites
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
See Nortel Multiservice Switch 7400/15000/20000 Fundamentals FP
Reference (NN10600-551) for valid values for the procedure variables.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<n> The LP number.
<p> The port number.
<port> The port type.
<q> The tributary port number.
<trib_port> The tributary port type.
Prerequisites
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Ensure that the shelf card cardType attribute is 16pOC3PosAtm. For more
information, see Configuring a new processor card (page 60)
Add a logical processor (LP). For more information, see Adding an LP and
linking it to an LPT (page 150).
The features you specify in the sw lpt featureList attribute must be
supported by the service bundle that you choose in step 3. See NPU
service bundles available for the 16-port OC-3/STM-1 POS ATM FP
(page 163) for a list of features.
For conceptual information regarding NPU service bundle, see Nortel
Multiservice Switch 7400/15000/20000 Fundamentals FP Reference
(NN10600-551).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<n> The LP number.
<bundle_name> The service bundle name. For MPLS, set it to mplsAtmIp. For
PorsTrunk, set it to PorsAtmIp.
<list_of_features> List of names of features required to support the MPLS service or the
PorsTrunk service. For more information about configuring MPLS, see
Nortel Multiservice Switch 7400/15000/20000 Configuration MPLS
(NN10600-445). For more information about configuring PORS, see
Nortel Multiservice Switch 7400/15000/20000 Configuration PORS
(NN10600-435).
Prerequisites
CAUTION
Deleting a feature from an in-use LPT
If you delete a feature from an in-use LPT (referenced by an LP),
the active processor card and the standby processor card reset. If
no other in-use LPT contains the feature, the whole node can
reset.
Procedure steps
Step Action
To clear the feature list and replace it with a new list, use an exclamation
point (!) as the first element in the list. For example, to clear the current
feature list and replace it with the atmTrunks feature, use the following list
of changes:
! atmTrunks
2 Verify that the changes are successful.
display Sw Lpt/<lpt_name> featureList
--End--
Variable definitions
Variable Value
<featurechanges> A list of feature changes separated by spaces.
<lpt_name> The name of the LPT for which you are changing the features.
Prerequisites
For more information on attribute values, use the help command for the
port type or refer to Nortel Multiservice Switch 7400/15000/20000
Components Reference (NN10600-060).
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<attribute> The name of the attribute.
<attributevalue> The value for the attribute.
<n> The LP number.
<p> The port number.
<port> The port type.
<subcomponents> Represents any subcomponents (such as tributary ports or channels)
that have provisionable attributes. This is an optional parameter.
Deleting an LP
Delete an LP by deleting its LogicalProcessor (Lp) component. When you
delete an Lp component, you also delete all its subcomponents.
This procedure can trigger a system reset or service outage. By using hitless
software removal (HSR), either Removal of a last LP or Removal of one or
more features provisioned on the CP, a system reset or service outage can
be prevented. See Nortel Multiservice Switch 7400/15000/20000 Upgrades
Software (NN10600-272).
Prerequisites
You must also delete services that were associated with the deleted Lp
component. To delete all associated services simultaneously, use the
clear -rf prov command. Alternatively, you can delete every associated
service individually using the delete command.
If you delete an LP and are left with a processor card with no LP assigned
to it, that processor card does not load when you activate your
configuration changes.
If you delete the last LP running a particular software feature, the CP
resets when you activate your configuration changes. This situation
occurs when the deleted LP uses an LPT that is not used by any other LP
and contains a feature not contained by any other currently used LP:
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
If you have deleted the LP of an active card, the semantic check indicates
that the card will reset when you activate the configuration changes. If you
have deleted the last LP running a particular software feature, the
semantic check also indicates that the CP will reset when you activate the
configuration.
Procedure steps
Step Action
Attention: To avoid a system reset or service outage, use an HSR procedure. See
Nortel Multiservice Switch 7400/15000/20000 Upgrades Software
(NN10600-272).
--End--
Variable definitions
Variable Value
<n> The number of the LP you want to delete.
Prerequisites
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<BITS_port> EDS1 (for DS1 lines) or EE1 (for E1 lines).
<port> 0 or 1.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<port> 0 or 1.
Prerequisites
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<dd> The two-digit day.
<hh> The two-digit hour.
<mm> The two-digit month.
<mn> The two-digit minute.
<n> The number of the LP.
<yyyy> The four-digit year.
Navigation
Locking and unlocking a bus (page 173)
Enabling and disabling automatic bus clock testing (page 174)
Interpreting the bus clock source status (page 175)
Verifying which buses are in service (page 177)
Prerequisites
For information on testing a bus, see Nortel Multiservice Switch 7400/
15000/20000 Troubleshooting (NN10600-520).
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Ensure the other bus is unlocked and enabled. You can lock a bus only if
the other bus is unlocked and enabled.
Procedure steps
Step Action
CAUTION
Risk of data loss
To reduce the risk of data loss, do not lock a bus during peak
periods of traffic. Bus system capacity is reduced by half when a
bus is locked, potentially causing minimal data loss due to
congestion. If problems occur on the enabled bus, card crashes
can also occur.
--End--
Variable definitions
Variable Value
<n> x or y.
Prerequisites
If you disable automatic testing, you should manually test the bus clock
source at least once a month. See Nortel Multiservice Switch 7400/15000/
20000 Troubleshooting (NN10600-520).
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Prerequisites
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
--End--
Navigation
Locking a fabric card (page 179)
Unlocking a fabric card (page 180)
Displaying the operating mode of fabrics (page 181)
Displaying the status of a fabric card (page 182)
Displaying the configuration or capacity of a fabric card (page 183)
Prerequisites
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
1 Check the status of the fabric cards to ensure that the mate can
accommodate taking over all traffic on the node. You cannot lock a fabric
card unless its mates is unlocked and enabled with LED status solid green.
display Shelf fabricCard/*
2 Lock the fabric card.
lock Shelf fabricCard/<n>
When the fabric card is locked, alarm 0000 1000 is generated. Record
whether the upper or the lower fabric card was locked.
When locking the fabric card fails, alarm 7002 0013 is generated with a
reason for the failure.
--End--
Variable definitions
Variable Value
<n> x (for the fabric card in the upper position of the node) or y (for the fabric
card in the lower position of the same node).
The unlock command works on the card mounted in the fabric slot, even if you
replace the locked card with a new one.
Prerequisites
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<n> x or y.
Prerequisites
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
The reasons for a fabric card or fabric port being out of service are indicated
in the 7002 series of alarms.
Attention: If the reset button under the handle of a Multiservice Switch 20000 fabric
card is not fully engaged, the fabric card remains out of service and shows a solid
red LED.
--End--
Prerequisites
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<n> x or y.
Attention: For the initial release of Multiservice Switch 20000, the fabric
card is the 70 G version with PEC NTPN02, but the node backplane is
designed to accommodate other capacities.
Prerequisites
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
--End--
Navigation
Synchronizing disks (page 185)
Displaying information about the file system (page 186)
Determining file system capacity (page 187)
Changing the volume name of a disk (page 188)
Formatting a disk (page 190)
Synchronizing disks
Synchronize disks so that both the active and standby CPs in a node have
identical content.
Depending on the amount of stored data on the active disk and the difference
between the two disks, the synchronization can take several hours.
Prerequisites
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
--End--
Displayed information about the file system includes the volume name,
synchronization status, capacity, free space, and usage percentage.
Displayed information about the disks of the file system includes the volume
name, capacity, and free space on the disk. The instance number of the Disk
component corresponds to the slot number of the CP that holds the disk.
Attention: If there are different numbers of bad blocks on the disks in a dual-
disk system, the reported free space can differ on the two disks.
Prerequisites
Do the following procedure in operational mode. For information on
working in operational mode, see Operational mode (page 342).
Procedure steps
Step Action
--End--
Prerequisites
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
1 Display information about the file system on the CP2 and CP3 using the
procedure Displaying information about the file system (page 186).
2 Subtract the amount of free space from the capacity to determine the
amount of space available on the CP3 disk:
freeSpace - capacity = <amount_of_data>
If the <amount_of_data> exceeds the value of the capacity attribute for the
CP2, the synchronization from CP3 to CP2 will fail.
--End--
Variable definitions
Variable Value
<amount_of_data> The amount of space available on a CP.
Prerequisites
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
CAUTION
Locking the file system
Minimize the time you spend in lock Fs. Locking the file system
results in a condition where configuration activity can fail,
downloading can fail, and spooling can stop if the disk remains in
this state too long.
3 If you are changing the volume name of the active CP disk, lock the file
system.
lock Fs
4 Lock the disk whose volume name you want to change.
lock Fs Disk/<n>
5 Set the volume names on the disk.
set Fs Disk/<n> volumeName <volumename>
6 Unlock the disk.
unlock Fs Disk/<n>
7 If you previously locked the file system, unlock it.
unlock Fs
--End--
Variable definitions
Variable Value
<n> The number of the disk. The disk number corresponds to the slot
number of the CP that holds the disk.
<volumename> The new volume name of the disk (up to 11 characters).
Formatting a disk
Format a disk to erase all files and directories and reset the volume name of
the disk. To support synchronization between different-sized disks, Nortel
Multiservice Switch systems can format a disk to a size smaller than its
physical capacity.
Prerequisites
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
CAUTION
Never format the disk on the active CP. Loss of
important files can result from using the format
command.
If your node has only one CP, do not format its disk. Only format
a disk if you have two CPs and one of them is in standby mode.
If you need to format the disk on the active CP and you have a
two-CP node, first use the switchover command to make the
active CP the standby. Once it has become the standby CP, you
can format its disk.
7 Fix the file system due to the possible bad media found.
set Fs disk/<n> test type filesystemCheck
start fs disk/<n> test
8 Wait for its completion.
9 Unlock the disk.
unlock Fs Disk/<n>
10 Synchronize the file system.
synchronize Fs
The synchronization can take several hours depending on the amount of
data on the active disk.
--End--
Variable definitions
Variable Value
<n> The slot number of the standby CP.
<volumename> The volume name of the disk. If you do not specify a volume name, the
system uses the first 11 characters of the node name.
Procedure steps
Step Action
Attention: This step is optional. The default setting for the attribute is
delayedSwitchOver.
--End--
Variable definitions
Variable Value
<connector> is the connector on the sparing panel. The default value is
notApplicable. If the processor card is the spare card, use the value
spare. If the processor card is the main card on a Multiservice
Switch 7400 series nodes, use one of these values: mainA, mainB,
mainC, or mainD. If the processor card is the main card on a
Multiservice Switch 15000 or Multiservice Switch 20000 node, or an
MSA32 FP or MSA8 FP of a Multiservice Switch 7400, use one of these
values: mainA, mainB, mainC, mainD, mainE, or mainF.
Attention: If the processor card is to be part of a one-for-one (1:1)
sparing configuration, using a one-for-one sparing panel, leave the
attribute sparingConnection set to the default value notApplicable.
<m> is the slot number of the main card, or a new processor card that you
intend to use as a main card.
<n> is the slot number of the spare card.
<x> is the instance value of the LP.
P0 P0
P1 P1
P2 P2
P0
control ports P0
P1 P1
P2 spare P2
FP1 FP2 FP3 FP4 FP5 FP6 FP
P0 P0
P1 P1
P2 P2
P0 P1 P2
Set up 1+1 inter-card line protection and equipment protection for an STM-1
optical channelized CES/ATM/IMA (2pSTM1Ch) FP on a Nortel Multiservice
Switch 7400. With 1+1 protection, one line is used to receive the incoming
traffic and both working and standby lines are used to transmit the outgoing
traffic. With the introduction of the 2pSTM1Ch FP, the Multiservice
Switch 7400 now supports the Laps component, along with Aps.
Navigation
Configuring line protection for Multiservice Switch 7400 optical interfaces
(page 198)
Configuring line and equipment protection for Multiservice Switch 7400
optical interfaces (page 200)
Locking the protection line on Multiservice Switch 7400 nodes (page 202)
Prerequisites
The logical processor type (LPT) associated with these ports must have
Line APS in its feature list.
See Nortel Multiservice Switch 7400/15000/20000 Fundamentals FP
Reference (NN10600-551) for information on port numbers for APS
protection pairs.
Procedure steps
Step Action
The default setting is non-revertive. This means that after a failure has
cleared, the protection line stays active until the operator issues a
switchover command.
7 Verify your configuration of the AutomaticProtectionSwitching component.
display aps/<a>
8 Check, activate and confirm the provisioning changes, see Activating
configuration changes (page 343).
--End--
Variable definitions
Variable Value
<laps> is the LAPS identifying number.
<n> is the instance of the LP linked to the line APS application. At this point,
lp/<n> is configured as the main card.
<p> is the LP number of the main card.
<port> is the port type, either Sonet or Sdh.
<q> is the LP number of the standby card.
Prerequisites
The logical processor type (LPT) associated with the SDH ports must
have the Laps component in its feature list.
When you add Aps in the feature list, you have to first activate prov then
add Laps.
Procedure steps
Step Action
1 Add an SDH port to the protected LogicalProcessor (Lp) components for the
main and standby 2pSTM1Ch FPs.
add lp/<p> sdh/<sdh>
add lp/<q> sdh/<sdh>
The OpticalModule component is added automatically under the Sdh
component if cardType has been specified as 2pSTM1Ch.
2 Set the type of SFP optical module (om) for each port on both cards.
set lp/<p> sdh/<sdh> om type <m>
set lp/<q> sdh/<sdh> om type <m>
3 Add the Laps component.
add laps/<laps>
The CrossConnect (Xc) component is created automatically when the
Laps component is added.
4 Set the working and protection lines.
set laps/<laps> workingLine lp/<p> sdh/<sdh>
set laps/<laps> protectionLine lp/<q> sdh/<sdh>
5 Add the high order path component (Vc4).
add laps/<laps> vc4/<vc4>
6 Add the low order path component (Vc12) and tributaries.
add laps/<laps> vc4/<vc4> vc12/<k,l,m>
When the Vc12 component is added, the E1 component and the Chan
component with all timeslots, except timeslot 16, are automatically
added. On the 2pSTM1Ch, the timeslots are put under Chan/0 for all
supported services.
7 Add the AtmCell component if the Chan/0 on the 2pSTM1Ch is used for
ATM or IMA services
add Laps/<laps> vc4/<vc4> vc12/<k,l,m> E1 Chan/0 AtmCell
8 Check, activate, and confirm the provisioning.
check Prov
activate Prov
confirm Prov
--End--
Variable definitions
Variable Value
<k,l,m> is the Vc12 component path value
where k=1-3, l=1-7, m=1-3,
ATMIF cannot be used on E1 57 to 62 or k=3, l=2 to 7 and m=3 in Vc12/
k,l,m
<laps> is the Laps identifying number.
<m> is type of optical module used for this port.
The possible values are:
OC3SmLr (Long Haul: SDH STM1 L-1.1 compliant)
OC3SmIr (Short Haul: SDH STM1 S-1.1 compliant)
<n> is the instance of the LP linked to the line APS application. At this point,
lp/<n> is configured as the main card.
<p> is the LP number of the main card.
<port> is the port type, either Sonet or Sdh.
<q> is the LP number of the standby card.
<sdh> is the SDH identifying number.
<vc4> is the number of the Vc4 component. There is only one Vc4 per STM-1
There are several commands the operator can use to set the active line. The
protectionLockout verb prevents the protection line from being used as the
active channel. If the protection line is active when protectionLockout is
issued, the working line becomes active.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<n> is the instance of the Aps or Laps component.
You can issue the switch command when the Aps or Laps component is
locked or unlocked.
Prerequisites
The switch verb is used to effect a change on the active line. The -force
option is used to invoke the changeover with the higher priority
nearEndRequest value of forcedSwitch. When -force is not used as an
option, the nearEndRequest value is the lower priority manualSwitch.
The working and protection lines should be synchronized with the same
timing source to make sure there is no service impact during equipment or
line switchovers.
Procedure steps
Step Action
1 Enter one of the following commands to change the working and protection
lines for APS.
switch [-force] -protectionToWorking Aps/<n>
switch [-force] -workingToProtection Aps/<n>
2 Enter one of the following commands to change the working and protection
lines for MSP.
switch [-force] -protectionToWorking Laps/<n>
switch [-force] -workingToProtection Laps/<n>
--End--
Variable definitions
Variable Value
<n> is the instance of the Aps or Laps component.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<n> is the instance of the Aps or Laps component.
Navigation
Configuring line and equipment protection for Multiservice Switch 15000
and Multiservice Switch 20000 optical interfaces (page 207)
Configuring line protection for optical interfaces on Multiservice
Switch 15000 and Multiservice Switch 20000 nodes (page 211)
Converting from a non-protected FP to a protected FP with LAPS on
Multiservice Switch 15000 and Multiservice Switch 20000 nodes
(page 213)
Converting from single-FP to dual-FP protection (page 215)
Configuring Y-protection for dual FPs in a Multiservice Switch 15000 and
Multiservice Switch 20000 nodes (page 217)
Prerequisites
The node must meet the requirements listed in Requirements for
configuring line and equipment protection for Multiservice Switch 15000
and Multiservice Switch 20000 optical interfaces (page 264)
You cannot connect an optical interface on a Multiservice Switch 15000 or
Multiservice Switch 20000 node that uses the Laps component, to an
optical interface on another Multiservice Switch 15000 or Multiservice
Switch 20000 node that does not use the Laps component, or to any third
party optical interface that does not support line APS.
When the dual-FP configuration involves the 16-port OC-3/STM-1 POS
and ATM cards (16pOC3PosAtm or NTHW44), the Y-protection capability
supports LAPS for dual FPs at the near end while LAPS is unsupported at
the far end interface (Multiservice Switch node or non-Multiservice Switch
node). Refer to the procedure Configuring Y-protection for dual FPs in a
Multiservice Switch 15000 and Multiservice Switch 20000 nodes
(page 217).
You can use the LineAutomaticProtectionSwitching component in an
equipment sparing configuration to provide both line and equipment
protection at the same time.
See Nortel Multiservice Switch 7400/15000/20000 Fundamentals FP
Reference (NN10600-551) at each description of a card type for limitations
about choosing slots and port numbers for LAPS protection pairs.
The logical processor type (LPT) associated with these ports must have
APS in its feature list.
The software logical processor type (SW LPT) of the logical processor
(LP) must be the same for the working line and the protection line
attributes.
The attributes for the working and the protection lines:
cannot be empty
must have the same card types
for FPs that use small-form pluggable (SFP) optical modules, must
have the same type and vintage of optical module
Procedure steps
Step Action
CAUTION
Risk of loss of service by interface attribute mismatch
Special care should be taken when connecting an optical interface
on one Multiservice Switch 15000 or Multiservice Switch 20000
node using the Laps component for equipment protection, to another
optical interface on another Multiservice Switch 15000 or
Multiservice Switch 20000 node that does not. You can make such
a connection when both Multiservice Switch nodes are connected
through an optical transport device, such as a Nortel OC-48
TransportNode or a third party device.
A mismatch can occur between the interface attributes set through
the Laps component of the first Multiservice Switch node and the
equivalent interface attribute set through the port components of the
LP of the second Multiservice Switch node. In particular, the default
value of the alarmActDelay attribute is 2000 when set through a
Laps component, but only 500 when set through a port component.
This can cause loss of service between both nodes when an
equipment protection switchover occurs on the node using the Laps
component.
To avoid loss of service, ensure the interface attributes set through
the port component match the equivalent interface attributes set
through the Laps component. For example, the alarmActDelay
attribute of each node should be set to 2000.
Add AtmIf/<c>
4 Link the Laps component to the ports on the LP.
set AtmIf/<c> interfacename Laps/<a> <path>/<o>
set Laps/<a> workingLine Lp/<m> <port>/<p>
set Laps/<a> protectionLine Lp/<n> <port>/<p>
5 If the near and far end line terminating equipment must negotiate to
determine the line to receive the payload from, change the mode attribute to
bidirectional.
set Laps/<a> mode bidirectional
Bidirectional mode must be configured at both ends. The default setting is
unidirectional. This means that the line terminating equipment at each end
determines independently where to receive the payload.
When configuring G.841 Annex B on either the 16-port OC-3/STM-1 ATM
or 16-port OC-3/STM-1 POS and ATM FP, mode must be set to
bidirectional.
6 If you want line APS to revert automatically from the protection to the
working line once a failure has cleared, set revertive to yes.
set Laps/<a> revertive yes
The default setting is nonrevertive. This means that after a failure has
cleared, the protection line stays active until the operator issues a
switchover command.
When configuring G.841 Annex B on either the 16-port OC-3/STM-1 ATM
or 16-port OC-3/STM-1 POS and ATM FP, revertive must be set to no. For
these FPs, the only time traffic is reverted back to the working line is if the
protection line experiences a failure.
7 If you want to configure G.841 Annex B on either the 16-port OC-3/STM-1
ATM or 16-port OC-3/STM-1 POS and ATM FP, set the protocol attribute
accordingly.
set Laps/<a> protocol g841AnnexB
display Laps/<a>
8 Complete the configuration changes. See Activating configuration changes
(page 343).
--End--
Variable definitions
Variable Value
<a> The instance number of the Laps component. The Laps instance must be
between 0 and 15999.
<c> The instance number of the AtmIf component. The AtmIf instance must
be between 1 and 4095.
<m> The LP number of the working line.*
<n> The LP number of the protection line.*
<o> The path number.
<p> The port number on the LP. It must be the same on both the working line
and the protection line.
<path> Sts or Vc4.
<port> Sonet or Sdh.
* For the 16-port OC-3/STM-1 ATM and 16-port OC-3/STM-1 POS and ATM FPs, only inter-
card LAPS is supported and therefore two identical cardtypes must be positioned in adjacent
slots in order for LAPS to function properly.
Prerequisites
The node must meet the requirements listed in Requirements for
configuring line and equipment protection for Multiservice Switch 15000
and Multiservice Switch 20000 optical interfaces (page 264).
When you are configuring the LineAutomaticProtectionSwitching
component, ensure that the FPs use module timing to synchronize with
the CP. If the clocking source is not set to module timing, cell loss and
corruption could result in some configurations. Refer to Network clock
synchronization configuration (page 31) for more information on clock
configuration.
You can use the LineAutomaticProtectionSwitching component in an
equipment sparing configuration to provide both line and equipment
protection at the same time. For more information on equipment sparing
and line sparing, see Understanding line and equipment protection for
Multiservice Switch 15000 and Multiservice Switch 20000 optical
interfaces (page 262).
The logical processor type (LPT) associated with these ports must have
LAPS in its feature list.
Y-protection provides equipment protection (EP) and hitless software
migration (HSM) that can co-exist with standard LAPS on the same port
pairs. Refer to Configuring Y-protection for dual FPs in a Multiservice
Switch 15000 and Multiservice Switch 20000 nodes (page 217).
See Nortel Multiservice Switch 7400/15000/20000 Fundamentals FP
Reference (NN10600-551) at each description of a card type for limitations
about choosing slots and port numbers for LAPS protection pairs.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<a> The instance number of the LineAutomaticProtectionSwitching
component.
For Multiservice Switch 15000 and Multiservice Switch 20000 FPs, the
LineAutomaticProtectionSwitching instance can be any value between 0
and 15999.
<n> The logical processor number. It must be the same for both the working
line and the protection line.
<p> The working port number on the logical processor.
<path> Sts or Vc4.
<port> Sonet or Sdh.
<q> The protecting port number on the logical processor.
<o> The path number.
Prerequisites
CAUTION
Risk of loss of service by installing line APS protection
Converting from a non-protected single-FP to a protected dual-FP
with line APS causes a traffic outage.
Procedure steps
Step Action
1 Configure the spare FP. See Configuring a new processor card (page 60).
2 Add the ports to the LP. See Configuring ports on an LP (page 160).
3 Add the Laps component.
add Laps/<a>
4 Add the path component, either Sts for Sonet or Vc4 for Sdh.
add Laps/<a> <path>/<o>
5 Add the atmcell component.
add Laps/<a> <path>/<o> atmcell
6 Link the Laps component to the ports on the LP.
set atmif/<c> interfacename Laps/<a> <path>/<o>
7 Delete the path from the port.
Delete Lp/<n> <port>/<p> <path>/0
Attention: The working line and protection line ports are configured in pairs (for
example, port 0 and port 1) and are located on different LPs.
--End--
Variable definitions
Variable Value
<a> The instance number of the Laps component.
<c> The atminterface instance. The atmif instance must be between 1 and
4095.
<n> The LP number. It must be the same for the working and protection lines.
<o> The path number
<p> The port number on the working LP; the working line and protection line
ports are configured in pairs (for example, port 0 and port 1).
<path> Sts or Vc4
<port> Sonet or Sdh.
<q> The port number on the protection LP.
Prerequisites
The configuration of your node must match the requirements listed in
Nodal requirements for converting line and equipment protection
(page 265)
Converting from single-FP line APS to dual-FP line APS causes both FPs
to reset.
See Nortel Multiservice Switch 7400/15000/20000 Fundamentals FP
Reference (NN10600-551) for information on port numbers for line APS
protection pairs.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<a> The instance number of the Laps component.
<m> The LP number of the working line.
<n> The LP number of the protection line.
<p> The port number on the working LP; the working line and protection line
ports are configured in pairs (for example, port 0 and port 1).
<path> Sts or Vc4
(1 of 2)
Variable Value
<port> Sonet or Sdh
<q> The port number on the protection LP; the working line and protection line
ports are configured in pairs (for example, port 0 and port 1).
(2 of 2)
Prerequisites
The cards that are to be configured for Y-protection must be 16-port OC-3/
STM-1 POS and ATM FPs with PEC NTHW44 and software name
16pOC3PosAtm. The cards must be installed in adjacent slots with the left
one in an even-numbered slot in the range 2 to 14.
You must configure LAPS for the dual FPs as the start of configuring
Y-protection. The SFP modules with PEC NTTP02CD must be installed
and the Y-splitter cables must be disconnected before you begin the
configuration.
Decide the port pairs to be configured for LAPS with Y-protection. You
must first configure the port pair for LAPS, then alter the configuration to
include Y-protection. The procedure includes the steps for the NTHW44
FPs.
The table The changes to a LAPS configuration when configuring
Y-protection (page 219) indicates how components of LAPS are the same
or different when Y-protection is configured.
Ensure that you are familiar with the interactions and operational behavior
described in Understanding Y-protection for dual FPs (page 327).
Procedure steps
Step Action
1 Start provisioning.
start prov
2 Add a logical processor type (LPT) and add the aps feature to the LPT.
add sw lpt/laps fl aps
3 Set the card type of the two NTHW44 FPs.
set shelf card/<n> cardtype 16pOC3PosAtm
set shelf card/<n+1> cardtype 16pOC3PosAtm
4 Add a logical processor (LP) for each card, and set the main card and LPT.
add -s lp/<p> main shelf card/<n>, lpt sw lpt/aps
add -s lp/<q> main shelf card/<n+1>, lpt sw lpt/aps
--End--
Variable definitions
Variable Value
<a> The LAPS identifying number.
<fileName> The user-defined file name to capture the provisioning entries.
<n> The slot number of the left FP of the dual FP configuration.
<n+1> The slot number of the right FP of the dual FP configuration.
<p> The LP number of the main card.
<q> The LP number of the standby card.
<s> The SDH identifying number.
<v> The number of the vc4 component.
Prerequisites
The verb protectionLockout is not supported for Y-protection.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<n> The instance of the Laps component.
Prerequisites
You can issue the command switch when the Laps component is locked
or unlocked.
You must use the option -force when the provisioned protocol is
g841AnnexB. The ITU-T G.841 Annex B standard does not support the
manual command. This protocol is currently supported only on FPs
16pOC3SmIrAtm (with PEC NTHW24) and 16pOC3PosAtm (with PEC
NTHW44).
The verb switch is not supported for Y-protection.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<n> The instance of the Laps component.
Prerequisites
The verb clear is not supported for Y-protection.
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<n> The instance of the Laps component.
Enabling the
Hitless activation of critical
hitless activatio n
attributes configuratio n
mod e
Mon itoring a
Is a non-disruptive hitless critical
Software migration
activation attribute activatio n
possible? (optional)
Yes
Invoking a non-
Feature upgrades
disruptive
and patch activation
activation
Do you wa nt to
disable the hitless
activation mode?
No
Yes
Disabling the
End hitless activatio n
mod e
No MSS 4001 0 14 AA
Prerequisites
You must perform this procedure in provisioning mode. For more
information, see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Em
ProvisioningSystem (Prov)
ActivationMode (Am)
hitlessActivation
MSS 4001 024 AA
Prerequisites
You must perform this procedure in provisioning mode. For more
information, see Provisioning mode (page 343).
You must ensure that all the conditions for a hitless critical attribute
activation are met. For more information on those conditions, see
Conditions for hitless activation of critical attributes (page 338).
You must ensure that the operational state of the Multiservice Switch is
ideal for hitless critical attribute activation. You must complete the following
procedures:
Verifying the provisioned card status (page 232)
Verifying the logical processor status (page 233)
Verifying the electrical functional processor status in a 1:1 sparing
configuration (page 235)
Verifying the logical processor status in a 1+1 FP sparing configuration
(page 236)
Procedure steps
Step Action
Attention: You can use the copy prov command to make the edit view equal to the
current view. However, the provisioning changes in the edit view will be lost when
you use the copy prov command.
CAUTION
Risk of service outage
If the value of the hitlessActivation attribute is set to disabled,
operators can make provisioning changes to critical attributes that
can result in service outages when the critical attribute is activated.
--End--
Em
ProvisioningSystem (Prov)
editViewAddedComponents (evAdded)
editViewDeletedComponents (evDeleted)
editViewChangedComponents (evChanged)
MSS 4001 008 AA
Prerequisites
You must perform this procedure in provisioning mode. For more
information, see Provisioning mode (page 343).
Procedure steps
Step Action
CAUTION
Risk of service outage
If the value of the hitlessActivation attribute is set to disabled,
operators can make provisioning changes to critical attributes that
can result in service outages when the critical attribute is activated.
--End--
Prerequisites
You must perform this procedure in operational mode. For more
information, see Operational mode (page 342).
Procedure steps
Step Action
1 Verify that all provisioned cards involved in the hitless critical attribute
activation are operational. If the value of the operationalState attribute is
disabled, the card is not operational.
display Shelf Card/<shelf_card> osiState
If the response indicates that any card is disabled and this card is configured
as a 1:1 or 1+1 FP sparing, then the services associated with this card will
incur a complete service outage for hitless critical attribute activation.
--End--
Em
Shelf
Card
adminState (osiAdmin)
operationalState (osiOper)
usageState (osiUsage)
availabilityStatus (osiAvail)
proceduralStatul (osiProc)
controlStatus (osiCntrl)
alarmStatus (osiAlarm)
standbyStatus (osiStby)
unknownStatus (osiUnknw)
MSS 4001 009 AA
Prerequisites
You must perform this procedure in operational mode. For more
information, see Operational mode (page 342).
You must configure the active alarm list. For more information on how to
configure the active alarm list, see Nortel Multiservice Switch 7400/15000/
20000 Administration Data Management (NN10600-561).
Procedure steps
Step Action
1 Verify that LPs involved in the hitless critical attribute activation are
operational. If the value of the operationalState attribute is disabled, the
card is not operational.
display Lp/* osiState
If the response indicates that any card is disabled and this card is configured
as a 1:1 or 1+1 FP sparing, then the services associated with this card will
incur a complete service outage for hitless critical attribute activation.
2 Ensure that there are no active alarms.
display Lp/* Eng ActiveAlarmList
--End--
Em
LogicalProcessor (Lp)
adminState (osiAdmin)
operationalState (osiOper)
usageState (osiUsage)
availabilityStatus (osiAvail)
proceduralStatul (osiProc)
controlStatus (osiCntrl)
alarmStatus (osiAlarm)
standbyStatus (osiStby)
unknownStatus (osiUnknw)
Engineering (Eng)
ActiveAlarmList (AAList)
Prerequisites
You must perform this procedure in operational mode. For more
information, see Operational mode (page 342).
Procedure steps
Step Action
--End--
Em
LogicalProcessor (Lp)
mainCardStatus
spareCardStatus
MSS 4001 011 AA
Prerequisites
You must perform this procedure in operational mode. For more
information, see Operational mode (page 342).
Procedure steps
Step Action
--End--
Em
Shelf
Card
sparedServices (SpServ)
operationalState (osiOper)
availabilityStatus (osiAvail)
MSS 4001 012 AA
Prerequisites
You must perform this procedure in operational mode. For more
information, see Operational mode (page 342).
Procedure steps
Step Action
--End--
Em
ProvisioningSystem (Prov)
CriticalAttributeActivation (Caa)
cardsBeingActivated
cardsToActivate
ActivityProgress
MSS 4001 013 AA
Prerequisites
You must perform this procedure in provisioning mode. For more
information, see Provisioning mode (page 343).
Procedure steps
Step Action
CAUTION
Risk of service outage
If the value of the hitlessActivation attribute is set to disabled,
operators can make provisioning changes to critical attributes that
can result in service outages when the critical attribute is activated.
Attention: When the value of the hitlessActivation attribute is set to disabled, the
Multiservice Switch issues a SET alarm. For more information on the alarm, see
Nortel Multiservice Switch 6400/7400/15000/20000 Alarms Reference
(NN10600-500).
--End--
Em
ProvisioningSystem (Prov)
ActivationMode (Am)
hitlessActivation
MSS 4001 024 AA
Maintenance
monitoring
Loading maintenance
monitor software
Configuring maintenance
monitor
Starting maintenance
monitor
Stopping maintenance
monitor
End
MSS 3613 002 AA
Task navigation
Loading maintenance monitor software (page 241)
Configuring maintenance monitor (page 242)
Starting maintenance monitor (page 244)
Stopping maintenance monitor (page 245)
Prerequisites
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<lpt_name> The name of the logical processor type.
<version> The version number of the software being loaded.
Prerequisites
Ensure that the channel you want to monitor is provisioned and operating
with either an ATM, AAL1 CES, or frame relay service.
Set up an ATM virtual channel connection with a nailed-up end point on
the port where the remote receiver is connected.
Do the following procedure in provisioning mode. For more information,
see Provisioning mode (page 343).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<dir> ingress or egress. With ingress, the traffic going into the channel is
monitored. With egress, the traffic going out of the channel is
monitored.
<lp> The LP containing the channel you want to monitor.
<m> The ATM interface with the port where the remote receiver is
connected.
<n> The instance number of the MaintenanceMonitorTX component.
<vpi.vci> Identifies the virtual channel connection to the port where the remote
receiver is connected.
Root
MaintenanceMonitorTX (MmTx)
Provisioned (Prov) group
linkToLogicalProcessor (IpName)
monitoredDirection (direction )
serviceType (serType)*
partialFill (partFill)*
idleSuppression (idleSup)*
Operational (Oper) group
connectionStatus (connStatus)*
chanToMonitor (chan)
NailedUpAdaptionPoint (Nap)
Provisioned (Prov) group
atmConnection (ac)
*read-only attribute
PPT 2920 035 AA
Prerequisites
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<lp> The LP containing the channel you want to monitor. The value must be
the same as the one specified in Configuring maintenance monitor
(page 242). The specified channel must be linked by provisioning to an
ATM interface, a frame relay interface, or a structured AAL1 CES
interface.
<n> The instance number of the MaintenanceMonitorTX component.
<x> The instance number of the port containing the channel you want to
monitor.
<y> The instance number of the channel you want to monitor.
Prerequisites
Do the following procedure in operational mode. For more information,
see Operational mode (page 342).
Procedure steps
Step Action
--End--
Variable definitions
Variable Value
<n> The instance number of the MaintenanceMonitorTX component.
The maintenance monitor software directs the data flow as a basic structured
ATM adaptation layer 1 (AAL1) circuit emulation service (CES) by means of
an ATM PVC. The output AAL1 CES data stream can be directed to a local
port, or to a remote port. The remote port can be located anywhere in the
network that supports CES.
The figure Maintenance monitor component hierarchy (page 243) shows the
maintenance monitor components and attributes that you can provision.
Navigation
Multiservice Switch system overview (page 248)
Understanding CP equipment sparing (page 248)
Understanding equipment protection for Multiservice Switch electrical
interfaces (page 258)
Understanding line and equipment protection for Multiservice
Switch 15000 and Multiservice Switch 20000 optical interfaces
(page 262)
Understanding line protection for Multiservice Switch 7400 optical
interfaces (page 267)
Understanding Multiservice Switch 15000 and Multiservice Switch 20000
support of G.841 Annex B (page 269)
Understanding logical processors, ports, and channels (page 270)
Understanding NCS (page 277)
Understanding network time and date configuration (page 297)
Understanding Multiservice Switch control processors and function
processors (page 299)
Understanding Multiservice Switch software (page 310)
Understanding the control processor OAM Ethernet port (page 314)
Understanding the fabric card (page 318)
Understanding the Multiservice Switch 7400 bus (page 322)
Understanding the Multiservice Switch file system (page 324)
Understanding Y-protection for dual FPs (page 327)
Understanding hitless services (page 330)
Every Multiservice Switch node has a shelf, a fabric card or a bus, and multiple
processor cards (Shelf, FabricCard or Bus, and Card components). The shelf
contains slots that hold the processor cards and the fabric card or bus. The
bus or fabric card allows the processor cards to communicate with the other
processor cards installed in the node.
Software and configuration files are stored on the node file system
(FileSystem component). The file system consists of up to two disks (Disk
component): one on the main CP and another on the spare CP.
The data collection system (Collector component) collects the data generated
for troubleshooting, performance tuning, and billing. In most cases, this data
is transferred to an external network management system for analysis.
The StartUp utility configures the main CP when you initially set up the node.
You can also configure a spare CP using the StartUp utility. For more
information, see Nortel Multiservice Switch 7400/15000/20000 Administration
Network Management Connectivity (NN10600-271). You can also manually
configure CP equipment sparing by configuring a spare CP.
Attention: When you connect both of the Ethernet ports on a two-CP node
through a hub or IP router, the Multiservice Data Manager workstation
connectivity is also spared. In order to quickly resume the OAM Ethernet
connectivity after the spare CP becomes active, direct hub or IP router
sparing is required for both the active and standby CP OAM Ethernet ports.
The CP currently running the node is the active CP. The other CP is the
standby CP. At any given time, either the main or the spare CP can be the
active CP.
A CP switchover occurs when the active CP gives control of the node to the
standby CP and the standby CP becomes the newly active CP.
There are two modes of CP equipment sparing: cold standby and hot standby.
In cold standby, all function processors (FP) must restart when the CP
switchover occurs. In hot standby, FPs that support this mode of operation
continue running uninterrupted when the CP switchover occurs.
CAUTION
Risk of damage to the CP
Do not remove the active CP from the node as a way of simulating
active CP failure.
To test the behavior of hot standby CP redundancy under CP failure
conditions, use the restart lp/0 command or the reset lp/0 command.
CP standby states
There are three CP standby states when CP equipment protection is enabled
(hot): steady-state, synchronizing, and manual synchronization.
In steady state, all standby applications have been created, have had their
provisioning data delivered, and are ready to take over should a control
processor switchover (CPSO) occur. If a CPSO occurs, then the following
events will occur:
Standby applications on this CP will become active.
CP applications that are cold will have their provisioning data delivered
after all standby applications have been notified of the switchover.
Attention: Note that the above windows can overlap, but will typically be
quite small, since only the delta configuration needs to be activated,
journaled, and loaded.
Attention: With journaling enabled and the autoConfirm attribute set to on,
the current view is automatically confirmed after the switchover.
If the active CP fails after the activation has finished but before the user has
confirmed the activation, then the standby CP changes to the just activated
view, with the following steps:
Hot and warm standby CP applications are told to become active.
The delta configuration (of the last activation) is loaded on the standby CP.
Cold standby applications are activated.
The confirm timer is restarted (20 minutes). If the operator does not issue
confirm prov within 20 minutes, then the node resets to the committed
view.
The table Applications and features that support hot standby for CP
switchover (page 253) identifies the features that support hot standby. If an
application or feature is not listed in this table, then it does not support hot
standby mode.
Application Feature
base aps
atmCore
(1 of 3)
Application Feature
atmNetworking atmAini
atmEbr
atmIisp
atmPnni
atmUni
aal1Ces aal1Ces
atmBearerService atmBearerService
frameRelay frameRelayNni
frameRelayUni
frameRelayUniPvcSvc
mpaNetworkLink
ip ip 1
mpls mplsCrldp 2
networking dpnRouting
pvg vgsAtm
vgsIp
vgsIpG729
trunks atmTrunks
dpnTrunks 3
frDpnTrunks
porsTrunks
unackTrunks
vtds bitTransparent
echoCancellor
hdlcTransparent
silenceSuppressor
vtds
voice
voiceCompressor
(2 of 3)
Application Feature
wanDte atmMpe 1
frameRelayDte 1
1
During a CP switchover, ILS FPs configured with these features reset. The WAN
FPs do not reset. However, ILS services on the WAN FPs do reset.
2
MPLS service on the FP are interrupted during a CP switchover, but other services
on the FP that support hot standby mode are not interrupted.
3
The dpnTrunks feature on an FP does not cause that FP to restart on CP
switchover, but all DPN trunks restage if a CP switchover occurs. The network
routes traffic destined for DPN nodes around this node while DPN trunks restage.
(3 of 3)
Attention: Multiservice Switch nodes do not allow you to remove the active
CP without first preparing the system. Removing the active CP without due
preparation causes unexpected behavior on the bus or fabric and can cause
a full node reset.
switchover occurs in cold standby mode (all FPs on the node restart).
Refer to CP switchover operator commands (page 258).
The file system is synchronized.
If one or more of these requirements are not met, the CP switchover occurs
in cold standby mode; that is, all FPs restart.
Even if all the above requirements are satisfied, individual FPs may not
continue providing service during a CP switchover in hot standby node. An FP
continues to provide service if all the following requirements are met:
All features configured on the FP support hot standby mode for CP
switchover.
The configured data loaded on the FP matches that of the newly active
CP. For example, if the FP is running uncommitted data and you issue a
switchover -force lp/0 command, an FP restart occurs.
The newly active CP resynchronizes with the FP within approximately
60 seconds. This is required to ensure routing tables are updated correctly
and that routing loops do not occur for more than 60 seconds. If the newly
active CP cannot resynchronize with the FP within approximately
60 seconds, the FP resets.
If one or more of these requirements are not met, the FP may restart during a
CP switchover in hot standby mode.
Effects of a CP switchover
For all CP switchovers (in either cold or hot standby mode), the following
common effects occur:
Network management sessions terminate (such as Telnet, ssh, FTP, and
FMIP), that is, drop all connections to the active CP. A local network
management session on the standby CP does not terminate. However, it
is suspended until the CP becomes active.
Information stored in the edit view is lost unless it was saved on disk.
Some components that were in the locked state move to the unlocked
state. The fabric card or bus component remains locked if it was locked
prior to the switchover.
The operational attributes of CP-resident components revert to default
values.
All Multiservice Data Manager activities such as provisioning, backup/
restore, software download, the FTP connection between Multiservice
Data Manager and Nortel Multiservice Switch nodes, and performance
viewer sessions terminate.
The card currently providing service is the active card. The other card is the
standby card. At any given time, either the main or the spare card can be the
active card. If the active card fails, the standby automatically takes over. The
change from the active to standby card is called a switchover. The activity of
detecting the failure and performing the switchover temporarily disrupts traffic
through the node. The degree of disruption depends on the level of standby
support provided by the services running on the cards, for example hot, warm,
and cold. See Understanding hitless services (page 330).
sparing. For information about the sparing capabilities of a specific FP, see
Nortel Multiservice Switch 7400/15000/20000 Fundamentals FP Reference
(NN10600-551).
For DS1 and E1 MSA8 FP sparing, MSA8 FPs can only spare other MSA8
FPs of the same type. Sparing between MSA8 FPs and MSA32 FPs is not
supported.
If the main FP restarts before the sparing timer expires, traffic does not
change to the spare. However, if the FP fails again within a specified stability
period, traffic immediately moves to the spare FP. The CP then instructs the
main FP to come up in standby mode.
If the main FP fails to come up in standby mode after three restarts, the CP
places the failed FP into a rejected state. You need to replace the FPs that are
in a rejected state.
When the spare FP is in use, all the other main FPs are not protected. If a
spare FP fails and recovers while there are many main FP failures, the spare
always carries the traffic of the FP with the lowest LP number.
Manual FP switchover
Entering any of the following commands causes a manual switchover:
switchover Lp/<activeFP>
reset Shelf Card/<activeFP>
reset Lp/<activeFP>
restart Shelf Card/<activeFP>
restart Lp/<activeFP>
lock -force Lp/<activeFP>
lock -force Shelf Card/<activeFP>
CAUTION
Data loss may occur
When you reset or restart a processor it is temporarily unable to
provide service. During the time the processor is restarting, data can
be lost.
CAUTION
Loss of stable SVC connections may occur
When you reset or restart a processor card, a loss of SVC
connections may occur. Although stable SVC calls should remain
active in a redundant processor configuration, exercise caution when
issuing this command.
Both single-FP APS and dual-FP APS on Multiservice Switch 15000 and
Multiservice Switch 20000 nodes offer:
revertive and non-revertive switching schemes
unidirectional and bidirectional operating modes
The defaults are the same as for Multiservice Switch 7400 series nodes. See
Understanding line protection for Multiservice Switch 7400 optical interfaces
(page 267).
Line APS on Multiservice Switch 15000 and Multiservice Switch 20000 nodes
use:
a logical processor (LP) to define the main port where a service runs
a second LP to define a spare port where the service runs if the FP
containing the main port fails.
SONET line automatic protection switching (line APS) to link the ports
from both LPs
For Multiservice Switch 15000 and Multiservice Switch 20000 nodes, line
APS:
is implemented using the LineAutomaticProtectionSwitching (Laps)
component
applies to predetermined pairs of ports on a single FP to provide the same
level of functionality as with Multiservice Switch 7400 series nodes. This
is called single-FP APS
can also apply to predetermined pairs of ports on a pair of FPs. This is
called dual-FP APS. This configuration specifies both line and equipment
protection
The figure LAPS components and attributes (page 263) illustrates the
components and attributes of the Laps component.
EM
LineAutomaticProtectionSwitching (Laps)
workingLine (working)
protectionLine (protection)
mode
revertive
mimicAps
holdOffTimer (hoTime)
waitToRestorePeriod (wtrPeriod)
signalDegradeRatio (sdRatio)
protocol
primarySectionMismatchTime
Sts
applicationFramerName (framer)
PPT 2930 013 AA2
The following sections contain information about line APS for Multiservice
Switch 15000 and Multiservice Switch 20000 optical interfaces:
Requirements for configuring line and equipment protection for
Multiservice Switch 15000 and Multiservice Switch 20000 optical
interfaces (page 264)
Nodal requirements for converting line and equipment protection
(page 265)
Working line on Multiservice Switch 15000 and Multiservice Switch 20000
optical interfaces (page 266)
Attention: Some services are no longer hitless when combined with other
services on the same FP. See Understanding hitless services (page 330) for
details.
CAUTION
Risk of loss of service by improper timing source
Ports configured for equipment protection/dual FP APS should use
the same timing source to make sure there is no service impact
during equipment or line switchovers. This can be accomplished by
using the module clock as the ports clocking source.
For more information about choosing the location of FPs in Nortel Multiservice
Switch 15000 and Multiservice Switch 20000 nodes, see Nortel Multiservice
Switch 15000/20000 Installation, Maintenance, and Upgrade Hardware
(NN10600-130).
When the working line is active, the protection line operates as a backup. Line
failure, signal degradation or an operator command can cause the active line
to change from working to protection.
Line APS standards define two switching schemes: revertive and non-
revertive. Revertive switching causes the active channel to change back to
the designated working line when the condition causing the switchover is
cleared. Non-revertive switching allows the protection line to remain active
until the criteria for a switchover are met and an operator issues a manual
switchover. The non-revertive scheme is the default for optical FPs.
The figure APS components and attributes (page 268) illustrates the
components and attributes of the Aps component.
EM
AutomaticProtectionSwitching (Aps)
applicationFramerName (framer)
workingLine (working)
protectionLine (protection)
mode
revertive
holdOffTime (hoTime)
waitToRestorePeriod (wtrPeriod)
signalDegradeRatio (sdRatio)
PPT 2930 012 AA2
See the following sections for a description of Line APS for Multiservice
Switch 7400 optical interfaces:
Working line on Multiservice Switch 7400 optical interfaces (page 268)
Protection line on Multiservice Switch 7400 optical interfaces (page 268)
Revertive and non-revertive switching on Multiservice Switch 7400 optical
interfaces (page 269)
Unidirectional and bidirectional mode on Multiservice Switch 7400 optical
interfaces (page 269)
For information on how to configure the working line, see Nortel Multiservice
Switch 7400/15000/20000 Fundamentals FP Reference (NN10600-551).
For information on how to configure the protection line, see Nortel Multiservice
Switch 7400/15000/20000 Fundamentals FP Reference (NN10600-551).
unspared ports can co-exist on the same FP with either or both APS
protocols
provides same level of protection for a single line failure
makes use of two lines: working line and protection line
existing semantic checks are supported
EM
LogicalProcessor (Lp)
mainCard (main)
spareCard (spare)
logicalProcessorType (lpt)
<port>
applicationFramerName (framer)
Channel (Chan)
applicationFramerName (framer)
Software (Sw)
avList (avl)
patchList (patl)
LogicalProcessorType (Lpt)
featureList (fl)
logicalProcessors
ApplicationVersion (Av)
Feature (Feat)
Patch (Patch)
PPT 2930 011 AA
Function processor and control processor sparing uses LPs to define the
processor software and configuration regardless of whether the main or spare
processor is currently active.
For example, if you create an LP for a V.35 processor card, you add eight V35
subcomponents (numbered 0 to 7) to the Lp component to represent each of
the eight ports on the processor card.
Some processor cards can also have channels on their ports. If you are
configuring an LP for a channelized port, you have to add Channel
subcomponents to the port component. For example, on a DS1C card you can
add between 1 and 24 Channel components (numbered 0 to 23) under each
of its four DS1 port components (numbered 0 to 4).
After you define the ports and channels of an LP, you can link them to the
service that you want to run on that port or channel. You create the link by
setting the applicationFramerName (framer) attribute of the port or channel to
the Framer component for the service.
Each application has a version number appended to its name. For example,
if the trunks application is version AA01, its application version is
trunks_AA001. The ApplicationVersion (Av) component, which is a
subcomponent of Software (Sw), indicates each application version that is
currently available on the node.
Applications are further divided into features. Features contain the software
necessary to provide a particular service. For example, the trunks application
has a number of features, one for each type of Multiservice Switch trunk:
dpnTrunks
unackTrunks
porsTrunks
frDpnTrunks
atmTrunks
In the preceding example, the four SONET ports are used by three different
application instances. One application instance uses the first SONET port
(and a second port defined through another LP). A second application
instance uses the second SONET port. A third application instance uses the
third and fourth SONET ports. Of the three application instances, two are
spared and one is unspared.
Attention: Do not define LPTs that mix cold standby applications or features
with hot standby or a warm standby applications or features. A single cold
standby application or feature in an LPT changes all other applications and
features into cold standby. See Understanding hitless services (page 330)
for details. Warm standby applications and features can co-exist with hot
standby applications and instances in an LPT.
Relationship between LPTs, LPs, and processor cards in Multiservice Switch 15000 or
Multiservice Switch 20000 nodes
Card/5
LP/8
Card/15
Primary mapping (main)
Spare mapping
PPT 0032 001 AA
In the example, Lpt/FRS contains the software features required to run the
frame relay service. Since this LPT maps to both Lp/5 and Lp/8, these two LPs
can provide frame relay services. Processor cards 4 and 15 are main cards
for LPs 5 and 8, respectively. Processor card 5 is a spare card for Lp/5 and
runs the software and services defined for Lp/5 if processor card 4 fails.
When you associate an LP with more than one processor card, you have
processor card sparing. In a sparing configuration, one processor card is the
main and the other is the spare. Typically, the main processor card is active
and provides the services and capabilities of the LP. The spare card is in
standby mode, waiting to take over in case the main card fails.
If the main card fails, the Multiservice Switch node performs an automatic
switchover. During a switchover, the standby processor card becomes active
and the active processor card comes up as standby. You can manually
change from the active and standby processor cards using the switchover
command.
The figure Sample relationship between LPTs, LPs, and processor cards
(page 276) illustrates a one-for-n sparing configuration of LPTs, LPs, and
processor cards.
Card/2
Lp/2 Card/3
Software
Main
Spare
PPT 2706 001 AA
The LPs 1 and 2 both share the same LPT. LP 1 has processor card 1 as its
main card and processor card 2 as its spare card. LP 2 has processor card 3
as its main card and processor card 2 as it spare card. If either card 1 or 3
fails, card 2 takes over. For this configuration to work, you must correctly
connect the processor cards to a sparing panel and configure the sparing
connection. For information on configuring the sparing connection, see
Configuring a new processor card (page 60).
You can immediately disable (skipping the shutting down state) an LP using
the force option of the lock command. When you use the force option, the LP
immediately restarts and the LP moves into the locked state. If you are
unfamiliar with lock command concepts, see Nortel Multiservice Switch 7400/
15000/20000 Commands Reference (NN10600-050).
When an LP is locked, the LED status display on its main processor card is
slow-pulsing red.
Understanding NCS
Network clock synchronization (NCS) provides the clock rates for connected
ports so that they operate in synchronization. NCS prevents data loss or data
retransmission for synchronous services.
The physical ports can be made to synchronize with a clocking source (using
the port attribute clockingSource). For example, the clockingSource can be
set to module, local, or line. The value module means that the stratum-3 clock
of the CP generates the ports transmit clock. The value local means the FP
uses its own crystal oscillator as a reference. The value line means the clock
signal received from the port generates the transmit clock. For more
information on clocking, see Understanding basic clocking (page 278).
The figure Components and attributes used for NCS (page 278) shows the
configurable software and logical hardware components and attributes for
NCS. The term reference indicates a reference for the CP. The reference
receives the network clock signal from another node and passes it to the CP
(to use as a reference).
Root Root
LP NetworkSynchronization (NS)
primaryReference
DS1 (E1, etc.) secondaryReference
clockingSource TertiaryReference
Root
LP
Similarly, if the transmit clock at node A is slower than the one at node B, the
buffer at node B underruns. This is because the transmission rate of node B
is greater than the rate it receives data.
Buffer overflow and underrun result in either data loss or data retransmission.
In the case of overflow, data is lost. In the case of underrun, the last
transmitted data is usually repeated. Therefore, providing a synchronized
network is critical for synchronous services.
Attention: NCS errors are not the only cause of underruns and overflows.
Traffic congestion can cause the same result.
Understanding synchronization
The figure Hierarchical clock synchronization network (page 280) shows an
example of a hierarchical clock synchronization network. In the hierarchical
synchronization method, a frequency reference is transmitted from one node
to another node. Nodal clocks supply a synchronization reference to specific
nodes, each of which can in turn supply a reference to other nodes.
Reference
Frequency Stratum 1 Node
Stratum 2 Nodes
Stratum 3 Nodes
Stratum 4 Nodes
Synchronization minimizes frame slips and data loss for bit-transparent data
applications. The figures Network synchronization component and
provisionable attribute (page 282) and Network synchronization component
and operational attributes (page 282) show the provisionable and operational
attributes for the network synchronization component.
Em
NetworkSynchronization (NS)
primaryReference (priRef)
secondaryReference (secRef)
tertiaryReference (tertRef)
useableReferences (useRef)
reversionDelay (revDel)
ssmProtocol (ssm)
PPT 3104 001 AB
Em
NetworkSynchronization (NS)
adminState (osiAdmin)
operationalState (osiOper)
usageState (osiUsage)
clockSyncState (clkSyncState)
activeReference (actRef)
standbyReference (standbyRef)
activeRefSSMValue (actSsm)
standbyRefSSMValue (stdSsm)
PPT 3104 001 AA
Clock distribution
The figure Multiservice Switch module 8 kHz clock distribution (page 284)
represents a simplified view of the distribution of clocks on a Nortel
Multiservice Switch node. Each FP provides a means of extracting an 8 kHz
reference clock from its connected external link. The control processors (CP)
can choose an extracted clock from a port to be used as a reference for this
node. The chosen reference clock signal is relayed across the backplane to
the CP.
If the clocking source for networking synchronization comes from line timing,
set the clocking source for all ports, including the port used as the reference,
to module. As the figure Multiservice Switch module 8 kHz clock distribution
(page 284) shows, the clockingSource attribute selects an outgoing clock
source unrelated to the incoming clock.
CP FP
8K crystal
module
local
line
NS
External
This is selected Link
based on the
clocking Source attribute This is the selected port
on the FP. for use as Reference
by NS on the CP.
For networks not carrying time-sensitive traffic, it is possible to have one core
Multiservice Switch node running in free-run with all other network nodes
synchronized with it. In this situation, the Stratum-3 clock is the
synchronization source, but the same clock is used everywhere in the
networks. In this configuration, the core nodes acting as the master clock
source.
The figure Network using NCS (page 286) shows a network using NCS. The
master signal is taken from a BaseOne port. Each successive node
synchronizes with the signal of the last, from BaseSix node in turn back to the
master. For example, BaseSix synchronizes with BaseFive, which in turn
synchronizes with BaseThree, which synchronizes with the master, BaseOne.
BaseFive
BaseThree Signal synchronizes with:
Signal synchronizes with: BaseThree (Primary)
Master (Primary) BaseTwo (Secondary)
BaseOne
BaseSix
Master
Signal synchronizes
with:
BaseFive (Primary)
BaseFour (Secondary)
BaseTwo BaseFour
Signal synchronizes with: Signal synchronizes with:
Master (Primary) BaseTwo (Primary)
BaseThree (Secondary) BaseFive (Secondary)
The clocking signal source is altered under any of the following conditions:
the activeReference port (supplying the reference clock to the module)
determines that its connection to the network or external source is bad.
For example, there can be a loss of signal or loss of frame.
the activeReference port goes to the locked state as a result of operator
commands
a DS1 or E1 activeReference port on the FP is configured to have a local
clock source
the configured primaryReference becomes enabled or a new
primaryReference is configured
the logical processor (LP) that the activeReference port is on becomes
disabled
The BITS concept stipulates that all digital equipment in a physical structure
must receive timing from the same master clock. This master clock produces
a stratum-3 or better reference signal.
The figure BITS components and attributes (page 290) illustrates the
components and attributes of external timing ports. Even though the ports are
physically located on the alarm/BITS card (for Multiservice Switch 15000 and
Multiservice Switch 20000 nodes) and on the CP (optional for Multiservice
Switch 7400 series nodes), the ports are logically configured as a
subcomponent of the LP.
Em
LogicalProcessor (Lp)
EDS1
lineType
ssmRxDefault
EE1
rxSynchClk
ssmRxDefault
PPT 3329 001 AA
Since the SONET and SDH S1 byte definitions have different values for the
equivalent clock quality level, a mapping table assists in determining the best
clocking source available. The NS component makes switching decisions
based on the Quality Level (QL), as seen in the table SONET/SDH quality
level (QL) mapping table (page 291). In cases where the quality level on a port
is not provided, a value of Quality Unknown is used.
Rx S1 Mapping to QL QL Mapping to Tx S1
SONET/ S1 Byte SDH/E1 S1 Byte QL SONET/ S1 Byte SDH/E1 S1 Byte
DS1 (binary / acronym (binary / DS1 (binary / acronym (binary /
acronym decimal) decimal) acronym decimal) decimal)
STU 0000 0 0 STU 0000 0 STU 0000 0
PRS or 0001 1 PRC 0010 2 1 PRS or 0001 1 PRC 0010 2
ST1 ST1
STU 0000 0 2 STU 0000 0 STU 0000 0
ST2 0111 7 SSUT 0100 4 3 ST2 0111 7 SSUT 0100 4
TNC 0100 4 4 TNC 0100 4 SSUL 1000 8
ST3E 1101 13 5 ST3E 1101 13 SSUL 1000 8
ST3 1010 10 SSUL 1000 8 6 ST3 1010 10 SSUL 1000 8
SMC 1100 12 SEC 1011 11 7 SMC 1100 12 SEC 1011 11
ST4 N/A 8 ST4/ 1100 12 SEC 1011 11
SMC
Refer to Configuring SSM NCS (page 40) for details on configuring SSM
functionality.
Node B; Synchronized
to Node As Stratum-3
Node A: Master DCE DTE clock
PP PP
Attention: When setting the linkmode attribute, you must be aware of the
physical termination of the individual V11/V35 FP on the node. If there is a
mismatch between the type of hardware connection and the linkmode
setting, the hardware connection overrides the linkmode setting. As a result,
the configured setting for the linkmode attribute is not recognized. To avoid
this problem, ensure that the configured setting for the linkmode attribute
matches the physical termination of the FP.
The output ports of an individual V11/V35 FP are grouped into two separate
connections. Ports 0 through 3 represent one connection and ports 4 through
7 represent another connection. Each of these connections can be set to
either dte or dce depending on its physical connection. For connections that
are physically connected as dce and have ports with linkmode set as dce, you
must set the clockingsource attribute to the same value for all ports of that
connection. This can be module, local, or line. For example, if the first
connection (ports 0 through 3) is connected as dce and the linkmode
attributes for these ports are set to dce, the value set for the clockingsource
attribute for ports 0 through 3 must all be the same. This is not applicable if
the connection is set to dte.
Set the linkMode attribute to dte. The link mode is set when you configure your
hardware. The hardware setup is shown by the operational attribute,
actualLinkMode. Setting the linkmode attribute does not override the
hardware configuration.
The linkMode attribute must be set to dce. The actual link mode is set when
you configure your hardware. The hardware setup is shown by the
actualLinkMode attribute (operational attribute).
Configure Node A:
Attention: If there is not an external reference for the node to slave from,
do not configure any references. This forces the nodes clocking to free run.
4 Select the source for the reference clock for the module. Typically the
secondaryReference and the tertiaryReference attributes are also set at
this point:
set NetworkSync primaryReference lp/2 ds1/0
5 Set the transmit clock port lp/2 ds1/0 (logical processor instance 2, ds1
port instance 0) to synchronize with the Node A stratum-3 clock. To do
this, use the module value for the clockingSource attribute:
The clocking source for this module and the rest of the Multiservice Switch
network slaving from this module are now synchronized to the external
equipment.
6 Set port lp/1 ds1/0 (this is the Multiservice Switch trunk to Node B) to
synchronize with the Node A stratum-3 clock:
set lp/1 ds1/0 clockingSource module
The clocking used by this port is now synchronized with the Node A
stratum-3 clock. See the figure Example: results of Node A commands
(page 295).
check Prov
activate Prov
confirm Prov
commit Prov
Configure Node B:
Node B;
Node A: Synchronized
Master to Node A
External
Clock PP PP
Source
Node A:
DS1
CP
Ip/2
Stratum-3 Ip/1
clock
DS1
PPT 0532 001 AA
NodeB
CP DS1
Stratum-3
clock
LP NetworkSynchronization (NS)
setsPrimaryReference
SETS
setsSecondaryReference
TxSynchClk
setsTertiaryReference
ssmE1SaNumber
setsSSMProtocol
setsSquelchTimer
There are three types of time to consider when configuring the time on a
Multiservice Switch node:
reference time
network time
module time
The reference time is the date and time that is the official reference around the
world. The universally accepted reference time is Coordinated Universal Time
(UTC) which, in general, is equivalent to Greenwich Mean Time (GMT).
The network time is the date and time that is common across the whole
network. This is the date and time to which all nodes in the network
synchronize internally. Nortel Networks recommends that you use UTC for the
network time. The network time is controlled by one or more time servers.
The module time is the time on a particular Multiservice Switch node. In most
cases, you synchronize the module time on a node to the network time on a
time server. You then adjust for time zone differences using a time zone
offset. The system uses the module time for time stamps in alarms,
accounting records, and other time-stamped data.
CAUTION
Risk of confusion in the interpretation of alarm and
accounting record time stamps
Nortel Networks recommends that your network be synchronized
to a reliable time server running reference time. Failure to do so
can result in difficulties when correlating time between multiple
Multiservice Switch nodes.
With this approach, a time offset of zero is configured on each node in the
Nortel Multiservice Switch network. As well, the whole network is
synchronized to a common time reference. When the whole network is on
reference time, the reference time is used as network time as well as module
time.
With this approach, a non-zero time offset representing a specific time zone
is selected to be used for the whole network. The selected time offset is
configured on each node in the Nortel Multiservice Switch network.
Although the reference time (UTC) is used to synchronize all nodes in the
network, each node displays time using the selected, common time offset. In
this manner, the date and time reported by all nodes in the network is the
same.
With this approach, a different time offset is configured on each node in the
Nortel Multiservice Switch network. However, the whole network is still
synchronized to a common time reference.
Although the reference time (UTC) is used to synchronize all nodes in the
network, each node displays time using its own time offset, based on the time
zone where the node resides. In this manner, the date and time reported by
all nodes in the network can be different.
CAUTION
Risk of confusion in the interpretation of alarm and
accounting record time stamps
Nortel Networks recommends that nodes not be operated each
with its own time offset as there is a risk of confusion in the time
stamp of alarms and accounting records.
For example, two nodes in different time zones generate a
different time stamp for accounting records produced on both
nodes at the exact same time.
Multiservice Switch 15000 and Multiservice Switch 20000 nodes have two
types of CPs: CP2 and CP3. CP2 offers a lower-cost option, while CP3 offers
increased processing power and connection space.
Multiservice Switch 7400 nodes support two types of CPs: the base model CP
and CP with building integrated timing supply (BITS). The CP with BITS has
a port on the faceplate for direct input of two external timing sources.
Because a CP is critical to the whole node, you often use two CPs to provide
redundancy. If the active CP fails, the node automatically moves traffic to the
standby CP. If you enable this feature, FPs with applications that support hot
standby for CP switchover continue running uninterrupted during the
switchover from active to standby CP. For more information see
Understanding CP equipment sparing (page 248).
Multiservice Switch nodes support a number of FPs that can run a variety of
different communication services, including frame relay, Asynchronous
Transfer Mode (ATM), Ethernet, and voice services, depending on the type of
node you have.
The figure Processor card components and attributes (page 301) shows the
components and attributes for a processor card. For more information on the
types of processor cards, see Processor card instances (page 301).
cardType
sparingConnection
configuredLPs
insertedCardType
type
memorySize
productCode
MSS 2930 010 AA
You must configure the type of the card you are inserting in the slot by setting
the cardType attribute. The CP on Multiservice Switch 7400 series nodes
have a card type of CP. The CP on Multiservice Switch 15000 and
Multiservice Switch 20000 nodes have a card type of CPeD or CPeE,
depending on whether it supports DS1 or E1 Building-Integrated Timing
Supply (BITS) timing. FPs can be of various types depending on the function
of the card. If the card that is actually inserted in the slot (as indicated by the
insertedCardType attribute) does not match the configured card type, the
processor card does not start and its status LED turns solid amber.
Some FPs on the Multiservice Switch 7400 series nodes contain daughter
cards, which are specialized cards attached to the FP. If an FP has daughter
cards, DaughterCard subcomponents appear under the Card component for
the FP. The instance number, that is automatically set by the node, indicates
the location of the daughter card. The attributes of the component give
information about the type, memory size, and product equipment code (PEC)
of the daughter card.
nodes reserve slot 0 for the main CP. Multiservice Switch 15000 and
Multiservice Switch 20000 nodes designate slot 1 for the spare CP. The
Multiservice Switch 7400 series nodes designate the last slot of the for the
spare CP.
Attention: Some Multiservice Switch 7400 processor cards are dual slot.
The procedure for configuring a dual-slot processor is the same as
configuring a single-slot processor.
If the FP is currently running an LP, locking the FP puts the card into the
shutting down state. The FP stays in the shutting down state until the LP stops
running. An LP stops running when you lock it or when some condition causes
it to restart (an operator command or an error). After the LP stops running, the
FP moves to the locked state.
If you are running certain configured services on the FP, the LP will never stop
running, in which case you need to use the -force option to lock the card. The
-force option bypasses intermediate states and immediately moves the FP to
the locked state. For spared optical FPs, the -force option can cause up to
50 ms of traffic to be dropped. For spared electrical FPs, the -force option can
cause up to 100 ms or more of traffic to be dropped depending on the type of
sparing panel. The amount of dropped traffic also depends on what the card
is, what it is configured for, and how much traffic is in progress.
The person who will replace the card and the software operator who locks the
card must coordinate their efforts to ensure that the FP is locked in software
before physically removing the card. If you remove a standby FP before it is
locked, the active FP can try to move its traffic over to it, but will not be able
to. All traffic on the active FP can be lost.
You can move an FP immediately into the locked state (skipping the shutting
down state) using the force option of the lock command.
For Multiservice Switch 7400 series nodes, when you lock an FP using the
force option, the LP immediately restarts and the card moves into the locked
state. For Multiservice Switch 15000 and Multiservice Switch 20000 nodes,
when you lock an FP using the force option, the card moves immediately into
the locked state. The LP restarts only when you restart the card.
If you lock an FP that has a defined spare card (is configured for equipment
protection), the LP changes to the standby card. For Multiservice Switch 7400
series nodes, when an FP is locked, its LED status light is slow-pulsing green.
For Multiservice Switch 15000 and Multiservice Switch 20000 nodes, when
an FP is locked, its LED status light is solid red.
Attention: With line automatic protection switching (LAPS), the status LEDs
on the faceplates of paired FPs do not indicate which one is active or
standby. For example, both can have solid green LEDs. Before replacing a
card that has been configured for LAPS, the standby card must be identified
by software commands. The software query must occur very close to the
actual time of card removal to minimize the systems opportunity to
automatically change cards.
When you restart a processor card, its hardware resets but it does not clear
the loaded software out of memory. The processor card reinitializes the
software in memory, but it does not reload the software from the file system.
This behavior generally makes restarting a processor card faster than
resetting the card.
the FP has already been removed from service by the system, minimize
the risk of not having a backup by doing the procedure during the period
of lowest traffic for that FP. An out-of-service FP shows a solid red LED.
During the removal from service, monitor alarms generated for equipment
that is involved in the connection paths of the FP being replaced. Address
the remedial action when the system allows it. All alarms are described in
Nortel Multiservice Switch 6400/7400/15000/20000 Alarms Reference
(NN10600-500).
For the sparing of MSA32 DS1 FPs, there are 1-slot and 2-slot cards with
different PECs that can spare each other. For the sparing of MSA32 E1 FPs,
there are 1-slot and 2-slot cards with different PECs that can spare each
other. For example, the same sparing configuration can contain 1-slot and
2-slot FPs with or without the optical ports. The combinations of cards are
identified in the FP descriptions in Nortel Multiservice Switch 7400
Fundamentals Hardware (NN10600-170).
For FPs, protection switching is available in case the card or signal fails. For
more information, see the following sections:
Multiservice Switch electrical interface equipment protection configuration
(page 192)
Multiservice Switch 7400 optical interface line and equipment protection
configuration (page 196)
Multiservice Switch 15000 and 20000 optical interface line and equipment
protection configuration (page 205)
The same load supports each of these nodes to provide functionality and
services. Each node uses the portion of software that applies to it, and
supports most of the available functionality and services. The new or changed
functionality or services is directly associated with a version of the PCR, 4.1
for example.
EM
Software (Sw)
avList (avl)
patchList (patl)
ApplicationVersion (Av)
compatibleAvList
processorTargets
Feature (Feat)
Patch
description (descr)
Download (Dld)
avBeingDownloaded
status
filesToTransfer
processorTargets
avListToDownload (dldList)
downloadedAvList
PPT 2930 002 AA
Software structure
Nortel Multiservice Switch software has four major classes:
base
trunking
networking
access services
The figure Multiservice Switch software structure (page 313) illustrates these
four software classes and their relationship to one another.
The base system provides the functions that support the access services. Its
functions include software management, command processing, provisioning,
node management, port management, file storage, data collection, and
network management interfaces.
The access services run on the base system and provide the
telecommunication capabilities of Multiservice Switch nodes. In general,
Multiservice Switch network access services include frame relay,
asynchronous transfer mode (ATM), Internet protocol (IP), and voice.
Networking software
Trunking software
Base software
Components
The main interface to Multiservice Switch nodes is by way of components.
Components represent the hardware, software, and services on a node. If you
want to modify the configuration of the node, you change the attribute values
of its components. You can do this directly by typing commands in the text
interface, or indirectly using a graphical network management tool. In either
case, you are manipulating node components.
Application versions
A particular version of an application is called an application version (AV). An
application version number identifies each AV. The version number consists
of two letters followed by two numbers. The most recent version of an
application has the highest letter pair (with AA being the lowest) and the
highest number pair (with 00 being the lowest). For example, AV numbers for
a specific application can be: AA01, AA02, and AB01, where AA01 is the
oldest version and AB01 is the newest.
The application version list (AVL) specifies the selected version for each
application to run on a node. You set the AVL using the avList attribute of the
Software component.
A processor card can have one of two types of processors: i960 or PowerPC.
A particular AV can support one or both of these processor types. When you
define your AVL, make sure that your AV supports the processor types on
your node. The processorTarget attribute of the ApplicationVersion
Patches
A patch is a temporary enhancement or correction to the functionality of an
application version. Patches allow for a number of small changes to be made
to an application until the next version of the application is available. In
general, a new application version incorporates all the changes in functionality
made in the preceding patches.
Each patch has a unique name. The patch name starts with the application
name, followed by a four-digit patch number (that starts at 0000). The patch
name ends with a single letter (starting at A) that indicates the version of the
patch. A patch is always associated with an application version. The number
and version of a patch start at 0000 and A for each application version.
For example, you have a patch named base0000B, that is associated with
application version base_AQ0123A. The patch modifies the behavior of the
base application provided by the base_AQ0123A application version. It is the
first patch (0000) released for that application version, but is the second
version (B) of that patch.
The patch list allows you to specify which patches you want to run on the
Multiservice Switch node. You specify the patches using the patchList attribute
of the Software component.
When nodes are directly connected to the management network, they use
local network management connectivity. Local connectivity can be achieved
by connecting the Ethernet port on the management device as follows:
directly to the physical Ethernet port on the CP
In remote connectivity, the management traffic can be routed over any WAN
or LAN media that connect the nodes, including the following:
Ethernet
Asynchronous Transfer Mode multi-protocol encapsulation (ATM-MPE)
frame relay data terminal equipment (DTE)
For more information on the CP OAM Ethernet port, see the following
sections:
OAM Ethernet port sparing (page 315)
OAM Ethernet port tests (page 317)
OAM Ethernet port statistics (page 317)
For procedures on configuring and maintaining the OAM Ethernet port, see
Control processor OAM Ethernet port configuration (page 135).
For information on IP security (IPSec) for OAM traffic, see Nortel Multiservice
Switch 7400/15000/20000 Administration Network Management
Connectivity (NN10600-271) and Nortel Multiservice Switch 7400/15000/
20000 Security (NN10600-601).
The Ethernet ports on the main and spare CPs are spared at the media
access control (MAC) and IP addressing level. When both these Ethernet
ports are connected to a hub or an IP router, only the Ethernet port of the main
CP is visible to the hub. The connection to the port on the spare CP appears
to have nothing at the end of it.
When the main CP fails or a CP switchover is initiated, the OAM port of the
main CP is disabled. This results in a loss of connectivity until the spare CP
becomes active. Once the spare becomes active, its OAM port becomes
enabled. All connection-oriented management applications must re-establish
their connections.
There are two conditions related to the failure of the OAM Ethernet port that
cause a CP switchover:
a port test fails during the initialization of the hardware device when the
CP first starts up
a time domain reflectometry test fails following an absence of traffic on the
link for a period of at least 25 seconds
As soon as the exception scenario clears and if the oamEnet port failure still
exists, then the CP switchover occurs.
The port device tests are initiated automatically prior to enabling the OAM port
functionality. You can also initiate them manually through the Test
subcomponent. The tests report a pass or fail.
Attention: The OAM Ethernet port tests are not supported on CP3 on
Multiservice Switch 15000 and Multiservice Switch 20000 nodes.
For more information on the fabric cards, see the following sections:
Single- and dual-fabric mode (page 319)
Fabric ports (page 319)
Fabric card firmware (page 320)
Fabric card operation on Multiservice Switch 15000 and Multiservice
Switch 20000 nodes (page 320)
Fabric card configuration (page 321)
Configuring the fabric card component (page 322)
For procedures on controlling the fabric cards and determining their status,
see Fabric card configuration (page 321).
EM
Shelf
FabricCard
adminState
operationalState
usageState
utilization
fixedBankVersion
writableBankVersion
activeBank
bankOnShelfRestart
PPT 2930 008 AA
Attention: In cases when both fabric cards may be operational, but at least
one fabric port on an FP is disabled, the backplaneOperatingMode attribute
is dualFabricDegraded rather than dualFabric.
When one fabric card is handling the traffic of the entire node, the node is in
single-fabric mode (backplaneOperatingMode attribute is singleFabricX or
singleFabricY) and all processor card cells run on that enabled fabric card.
The single fabric card still provides a node bandwidth of 40 Gbit/s for a
Multiservice Switch 15000 node and 70 Gbit/s for a Multiservice
Switch 20000 node. These nodes automatically alternate between single- and
dual-fabric mode depending on the state of the individual fabric cards.
Attention: If both fabric cards are out of service, the node enters fabric-less
mode. In this mode, all cards in the node are disabled. The node
automatically resets.
Fabric ports
Each fabric card has 16 ports that interface with the processor cards. Each
processor card has two fabric ports that interface with the fabric cards. Each
card component has two fabricPort subcomponents, one for each fabric port.
The OsiState attribute of the fabricPort component indicates the status of the
user-specified fabric port on a processor card.
Attention: Do not include the fabric card firmware AV in the software AV list.
Fabric card firmware upgrades are not normally needed when the CP and
FPs software is upgraded. All Multiservice Switch software is compatible with
all fabric card firmware. However, some versions of fabric card firmware
contain enhancements and new functionality to increase node efficiency.
For the commands to handle fabric firmware, see Nortel Multiservice Switch
7400/15000/20000 Upgrades Software (NN10600-272), the chapter on
installing new firmware on a fabric card.
These components are added and automatically configured when the fabric
cards and processor cards are physically installed and booted up.
The fabric card enables the processor cards on Multiservice Switch 15000
and Multiservice Switch 20000 nodes to communicate with each other. There
are two fabric cards, each represented by an instance of the FabricCard
component (x and y). The x denotes the fabric card in the upper physical
position in a node, while the y denotes the lower mate. When both fabric cards
are operational, the node is in dual-fabric mode. When in dual-mode with at
least one fabric port disabled, the node is in dual-fabric degraded mode. When
one fabric card is disabled, the node is in single-fabric mode.
You can manually remove a fabric card from service using the lock
command.You can lock a fabric card if both fabric cards are unlocked and
enabled, or when the card has been removed from its slot. The fabric card
remains locked until you unlock it using the unlock command. For example,
when a fabric is replaced or upgraded by another card, the new card is still
locked until unlocked.
There are two buses, each represented by an instance of the Bus component
(x and y). The figure Bus components and attributes (page 322) illustrates the
components and attributes of the buses.When both buses are operational, the
node is in dual-bus mode. When one bus is disabled, the node is in single-bus
mode.
You prevent a bus from carrying data using the lock command. The bus
remains locked until you unlock it using the unlock command. You can only
lock a bus if both buses are unlocked and enabled. If a control processor (CP)
switchover occurs, a locked bus remains locked. However if the node restarts,
a locked bus becomes unlocked.
Multiservice Switch 7400 nodes provide automatic testing of the bus clock
source. Since the bus clock source test can cause minor data loss, you can
disable the automatic testing. If you have disabled the automatic testing, it is
a good idea to manually test the bus clock source at least once a month.
EM
Shelf
busOperatingMode
Test
Bus
adminState
operationalState
usageState
utilization
busTapStatus
PPT 2930 009 AA
Bus taps
Each processor card has two bus taps, that provide an interface to the buses.
Each card component has two BusTap subcomponents, one for each bus tap.
The busTapStatus attribute of the Bus component indicates the status of each
bus tap.
Clock source
To properly function, the bus needs a clock signal. In most cases, the active
CP provides the clock signal for the bus. The alternate clock source is the
processor card (either an FP or a CP) in a slot at the opposite end from the
active CP. If that slot is empty, no alternate clock source is available. If
present, the standby CP is always the alternate clock source.
The alternate clock source only provides the clock signal for the bus if a
hardware failure makes it impossible for the active CP to do so. The
clockSource attribute indicates the current clock source. The
busClockSourceStatus attribute indicates the status of both the active and
alternate clock sources. If the busClockSourceStatus attribute has a value of
unknown, you should run a manual bus clock source test.
The manual bus clock source test is controlled by the Test subcomponent of
the Shelf component. You perform the test using the run Shelf Test command.
For a procedure on running the test, see Nortel Multiservice Switch 7400/
15000/20000 Troubleshooting (NN10600-520). For information on the run
Shelf Test command, see Nortel Multiservice Switch 7400/15000/20000
Commands Reference (NN10600-050).
When the two disks are synchronized, the system dynamically copies the
information on the active CPs disk to the standby CPs disk. If the active CP
fails and an automatic switchover to the standby CP occurs, information
stored on the file system is preserved.
For more information on the file system, see the following sections:
File system information (page 325)
Disk synchronization (page 325)
Different-sized disks (page 326)
File system restrictions (page 326)
Disk full conditions (page 327)
For procedures on maintaining the file system, see Navigation (page 184).
EM
FileSystem (Fs)
volumeName
activeDisk
syncStatus
syncProgress
capacity
freeSpace
usage
Disk
volumeName
capacity
freeSpace
PPT 2930 015 AA
Along with a component instance, each disk also has a name. The
volumeName attribute of the Disk component indicates the name of the
individual disk. The volumeName attribute of the FileSystem component
indicates the name of the active disk.
Disk synchronization
Before the Nortel Multiservice Switch system begins copying modifications
made on the active disk to the standby disk, the two disks must be
synchronized. The disks are synchronized when they have identical content.
If the disks do not have the same volume name, you can manually
synchronize the disks. During the synchronization, the system copies the
contents of the active disk to the standby disk. If the two disks are completely
different and the active disk contains a lot of information, the synchronization
process can take several hours. When the synchronization is complete, both
disks have the same volume name. The system takes the volume name from
the disk on the active CP.
The syncStatus attribute indicates whether the disks are synchronized, not
synchronized, or in the process of synchronizing. If they are in the process of
synchronizing, the syncProgress attribute indicates the percent completed.
You can manually initiate the synchronization process using the synchronize
Fs command. For information on performing a manual synchronization, see
Synchronizing disks (page 185). For information on the synchronize Fs
command, see Nortel Multiservice Switch 7400/15000/20000 Commands
Reference (NN10600-050).
Different-sized disks
The disks on the main and spare CP can be of different sizes. The file system
operates as if the two disks are the size of the smaller disk until the smaller
disk is full.
If the smaller disk is full and it is the standby disk, the system cannot copy
changes from the active disk to the standby disk. In this case, the file system
redundancy is disabled and the system treats the active disk as the only
available disk. If the smaller disk is the active disk, then the system cannot
write information to the file system because the active disk is full. You must
take immediate action to prevent loss of information.
Although you can operate your node with differently sized disks on the main
and spare CP, Nortel Networks recommends that the two disks be of the same
size whenever possible. If you must operate with different-sized disks, ensure
the active disk is always the smaller disk to avoid losing file system
redundancy.
The following restrictions apply when working with directories and files:
The only characters that can appear in a file name are letters, numbers,
the dot (.) character, and the underscore (_) character.
File names and directory names are case-sensitive.
If a file or directory name contains a slash (/), it must be enclosed in
quotation marks (" ").
File and directory names cannot be longer than 40 characters.
File names with their full path cannot be longer than 128 characters.
Attention: Slashes (/) count as characters, but quotation marks (" ") do not.
Directory names with their full path cannot exceed 125 characters.
You can have a maximum of 10 directory levels.
The root directory can have a maximum of 110 items (directories and
files).
When you copy a protected file, the new file is not protected.
CAUTION
Risk of damaging configuration data
Nortel Multiservice Switch provisioning system looks for saved
views according to specific file name formats and file relationships.
If you move or rename directories and files using the Multiservice
Switch file system commands (or using a non-Multiservice Switch
utility or application), you can destroy the integrity of the saved-
view database. Affected saved views cannot be recovered unless
you have backed them up. Only use the tidy prov command to
remove saved views.
To fix a full disk problem, you must remove any unused software and
provisioning files. For information on removing software files, see Nortel
Multiservice Switch 7400/15000/20000 Installation Software
(NN10600-270). For information on removing provisioning files, see the tidy
Prov command in Nortel Multiservice Switch 7400/15000/20000 Commands
Reference (NN10600-050). After removing unused files, you must manually
synchronize the disks on a two-CP node using the synchronize command. For
more information, see Synchronizing disks (page 185). Spooling of data
records restarts automatically when disk goes below 90% full.
Tx
Y-Splitter cable Rx
Service Active FP
Rx Tx
Tx Rx
To far-end
interface
Rx Tx
Tx Rx
Hot Standby FP
Tx
Rx
The FP software controls the lasers of each transmit and receive port such
that only the laser of an active port is on. This control ensures that the far end
does not get confused by receiving signals from two different sources on the
same line. This control also ensures that the laser is not turned on too soon
for a reset card that is still waiting for software to be loaded.
When a port with Y-protection fails or is locked on the service active FP, the
traffic is lost because there is no line switchover. Otherwise, locking or
unlocking a card, laps, logical processor (lp), or port is not affected by
Y-protection being configured on it. The impact of locking or unlocking is
determined by whatever else is configured.
Types of services
Nortel Multiservice Switch applications and features fall into three categories
with respect to equipment protection:
hot standby
warm standby
cold standby
Hot standby applications operate with the standby instance synchronized with
the active instance of the software. Hot standby applications and features use
equipment protection for electrical function processors (FP) and line and
equipment protection for optical FPs to offer hitless services. During an
equipment switchover, hot standby applications incur a minimal traffic
interruption and established connections stay up. For electrical FPs, a service
is considered hitless if the traffic interruption is less than 100 milliseconds. For
optical FPs, a service is considered hitless if the traffic interruption is less than
50 milliseconds.
Warm standby applications operate with the standby instance provisioned but
not synchronized with the active instance of the software. During an
equipment switchover, warm standby applications incur a longer outage of
service than hot standby applications, but not as long as cold standby
applications. As well, all connections must be re-established.
Warm standby applications can co-exist with hot standby applications and
instances on a logical processor (LP). Although you can create a logical
processor type (LPT) that mixes cold standby features with hot standby or
warm standby features, Nortel Networks does not recommend this action. A
single cold standby application or feature in an LP changes all other
applications and features to cold standby.
See the tables Hot standby applications and features (page 331) and Warm
standby applications and features (page 332) for a list of hot and warm
standby applications and features as they apply to hitless services.
Application Feature
atmBearerService atmBearerService
base aal1Ces
for the 4-port OC-3/STM-1Ch TDM/ CES FP (NTHW70)
aps
atmCore
atmNetworking atmIisp
atmPnni
atmUni
aal1Ces aal1Ces
(1 of 2)
Application Feature
pvg vgsAtm
vgsAtmDc
vgsAtmG729
vgsIp
vgsIpG729
Attention: Applications aal1Ces and pvg support hot equipment protection (HEP) and hitless software
migration (HSM) for a 1 + 1 sparing configuration on the Multiservice Switch 15000 Media Gateway
node. The HEP and HSM are only supported for voice services processor 2 (VSP2) (NTHW87), voice
services processor 3 (VSP3) (NTHW84), voice services processor 3 with optical TDM interface
(VSP3-o) (NTHW77), or 2-port voice services processor 4 with optical TDM interface (2pVSP4e)
(NTHW26) FP cards, and 4-port OC-3/STM-1Ch TDM/CES FP cards. The 1 + 1 sparing configuration
of VSP3-o and 2pVSP4e FP cards requires the VSP3-o and 2pSP4e FP cards to be in adjacent slots
where the lower slot number is an even number. Application pvg is only hitless when used in conjunction
with application aal1Ces (but not vice versa).
(2 of 2)
Application Feature
base aal1Ces
for the 4-port DS3Ch AAL1 CES FP (NTHR91), the 2-port STM-
1e channelized CES/ATM/IMA FP (NTNQ91), and the 2-port
STM-1 optical channelized CES/ATM/IMA FP (NTNQ96AA),
imaAtmForum
for the 2-port STM-1e channelized CES/ATM/IMA FP (NTNQ91)
and the 2-port STM-1 optical channelized CES/ATM/IMA FP
(NTNQ96AA).
atmNetworking atmApi
dprsMcsEp
dprsMcsEpIntercept
porsApi
routingGateway
callRedirection callRedirection
(1 of 3)
Application Feature
frameRelay frameRelayAtm
frameRelayAtmNiwf
frameRelayAtmIsdn
frameRelayNni
frameRelayUni
frameRelayUniPvcSvc
frf5EndPoint
frsVirtualFramer
frUniIpOptimized
huntGroupSystem huntGroupSystem
ip ip
rfc2547bis
networking callServer
dpnRouting
ipiFr
ServiceTrace frameRelayNniTrace
frameRelayUniTrace
atmUniTrace
atmIispTrace
atmPnniTrace
atmAiniTrace
frTraceRcvr
x25TraceRcvr
frAtmTraceRcvr
atmTraceRcvr
trunks atmTrunks
porsTrunks
WanDte AtmMpe
frameRelayDte
(2 of 3)
Application Feature
LocalMedia
ppp
Attention: LAN applications are considered warm standby.
(3 of 3)
As well, hitless services do not guarantee that there are no service outages.
See Critical components and attributes (page 334) for details.
See the following tables for a list of critical components and attributes:
Shelf critical components and attributes (page 334)
FP pair critical components and attributes (page 335)
ATM interface critical components and attributes (page 335)
ATM PVC critical components and attributes (page 337)
Non-stable call critical components and attributes (page 337)
Component Attribute
Software (Sw) avList (see Note)
LogicalProcessorType (Lpt) featureList (see Note)
Card cardType (see Note)
(1 of 2)
Component Attribute
Module (Mod) all attributes except for regionID
Routing DpnAddressPlan (Rtg Dpn) logicalNetworkNumber
routingId
moduleId
porsTrunks
unackTrunks
Attention: These attributes cause a service outage for the entire shelf if the software configuration of
the control processor is changed such that the system cannot incrementally load new software.
(2 of 2)
Component Attribute
Software (Sw) avList (see Note)
LogicalProcessorType (Lpt) featureList (see Note)
Card cardType (see Note)
Lp Eng Arc Ov all attributes
Lp Eng Arc Cqc Ov all attributes
Lp Eng Arc Apc Ov all attributes
Lp Eng Arc Aqm Ov all attributes
Lp Eng Arc Fcrc Ov all attributes
Lp Eng Arc Fcrc Pqc Ov all attributes
Lp Eng Fcrc Pqc Ov ipRoutesPoolCapacity
Attention: These attributes cause a service outage for the entire shelf if the LP software configuration
is changed such that the system cannot incrementally load new software.
Component Attribute
Lp Sonet ifIndex
Lp Sonet Sts concatNumber
ifIndex
(1 of 2)
Component Attribute
Laps workingLine
protectionLine
mimicAps
Laps Sts concatNumber
ifIndex
AtmInterface (AtmIf) interfaceName
oamSegmentBoundary
maxVpiBits
minimumBandwidthGuarantee
txCellMemory
AtmIf Ca all attributes except for bandwidthPool
AtmIf Ca Ubr all attributes except for maxVpcs, maxVpts, maxVccs, maxCtd,
and cdv
AtmIf Ca Cbr all attributes except maxCtd and cdv
AtmIf Ca RtVbr all attributes except maxCtd and cdv
AtmIf Ca NrtVbr all attributes except maxCtd and cdv
AtmIf ConnMap Ov all attributes
AtmIf Uni version
side
interfaceType
AtmIf Uni Ilmi vci
operatingMode
AtmIf Uni Sig vci
AtmIf Uni Sig Vcd all attributes
AtmIf Pnni Sig vci
AtmIf Pnni Rcc vci
helloHoldDown
helloInterval
helloInactivityFactor
AtmIf Ep minimumBandwidthGuarentee
AtmIf Vpt Ca Ubr all attributes except for maxVccs
(2 of 2)
Component Attribute
AtmIf Vcc Nrp all attributes
AtmIf Vcc Vcd mCastConnectionType
AtmIf Vcc Vcd Tm all attributes
Component Attribute
Artg Pnni nodeAddressPrefix
domain
Artg Pnni CfgNode nodeId
peerGroupId
restrictTransit
Component Attribute
AtmMpe ifIndex
encaptype
linkToProtocolPort
AtmMpe Ac AtmConnection
ipCos
La ifIndex
linkToProtocolPort
enetConnection
La Framer interfaceName
Vr virtualRouterProcessor
Vr Ip Static RouteEntry staticRemoteRtePrefer
Vr Pp linkToMedia
Vr Pp IpPort linkModel
mcastDomain
Component Attribute
Nsta linkToServer
idlePattern
Nsta Vgs gatewayAtmAddress
hostName
Nsta Vgs BragS tdmLogLaw
bufferSize
packetDelayVariationTolerance
signalingType
Nsta Vgs BragS Q921 dChanTimeslot
side
Nsta Vgs h248 mgMid
Nsta Vgs IpMConn ipAddress
udpPortBase
Nsta Vgs Iua asStatus
Nsta Vgs PktProf bufferSize
packetDelayVariationTolerance
For more information on how to configure this capability, see Hitless activation
of critical attributes configuration (page 224).
the attributes being changed support the hitless critical attribute activation.
See the table, Critical attributes for hitless activation (page 340).
the provisioning changes are not causing a control processor (CP) reset.
The provisioning changes impact the functional processors (FPs) only.
all the FPs that have changed critical attributes are either in a 1:1 or 1+1
sparing configuration and support equipment protection.
there are no LPs added or deleted.
there are no LP-card mapping changes.
there are no shelf card types changes.
there are no software LPT changes.
You can change any number of critical attributes within a single provisioning
session. There is no limit to the number of critical attributes changed, as long
as all the conditions for hitless activation of critical attributes are met.
pause. The operation pauses when the standby FP cannot synchronize all
connections. You can either continue or abort the pause failure mode. If
you decide to continue the operation (cont -force pr), you can cause loss
of traffic. If you decide to abort (stop pr) the operation, the FP reverts back
to the provisioning view before you started the hitless activation of critical
attributes.
Operational mode
Procedures contained within this document can either be performed in
operational mode or provisioning mode. When you initially log into a node, you
are in operational mode. Nortel Multiservice Switch systems use the following
command prompt when you are in operational mode:
#>
where:
# is the current command number
Provisioning mode
To change from operational mode to provisioning mode, type the following
command at the operator prompt:
start Prov
PROV #>
where:
CAUTION
Activating a provisioning view can affect service
Activating a provisioning view can result in a CP reload or restart,
causing all services on the node to fail. See Nortel Multiservice
Switch 7400/15000/20000 Commands Reference
(NN10600-050), for more information.
CAUTION
Risk of service failure
When you activate the provisioning changes (see
step 3), you have 20 minutes to confirm these
changes. If you do not confirm these changes within
20 minutes, the shelf resets and all services on the
node fail.
1 Verify that the provisioning changes you have made are acceptable.
check Prov
Correct any errors and then verify the provisioning changes again.
2 If you want to store the provisioning changes in a file, save the provisioning
view.
save -f(<filename>) Prov
3 If you want these changes as well as other changes made in the edit view
to take effect immediately, activate and confirm the provisioning changes.
activate Prov
confirm Prov
Publication: NN10600-550
Document status: Standard
Document issue: 02.01
Document date: June 2007
Product release: PCR 8.2
Job function: Installation and Commissioning
Type: NTP
Language type: U.S. English
Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks.