|
Table Of Contents
7.1 Performance Monitoring Thresholds
7.2 Provisioning Electrical Cards
7.3 Provisioning Optical Cards
7.3.1 Modifying Transmission Quality
7.3.2 Provisioning OC-N Cards for SDH
7.5 Provisioning the Alarm Interface Controller
7.5.2 Provisioning AIC Orderwire
7.6 Converting DS-1 and DS-3 Cards From 1:1 to 1:N Protection
Card Provisioning
This chapter provides Cisco ONS 15454 procedures for:
•Changing the default transmission parameters for electrical (EC-1, DS-N) and optical (OC-N) cards, including provisioning OC-N cards for SDH
•Setting performance monitoring (PM) thresholds, including intermediate path performance monitoring
•Provisioning the Alarm Interface Controller card
•Converting the DS1-14 and DS3-12 cards from 1:1 to 1:N protection
Note Ethernet card provisioning is described in Chapter 9, "Ethernet Operation."
Because much of the electrical and optical card provisioning involves PM thresholds, see Chapter 8, "Performance Monitoring," for definitions and general information about ONS 15454 performance monitoring parameters. In addition, refer to the Telcordia GR-1230-CORE, GR-820-CORE, and GR-253-CORE documents. The default thresholds delivered with ONS 15454 cards are based on specifications contained in those documents.
Note For information about creating protection groups, see the "Creating Protection Groups" section on page 3-9. For circuit creation procedures, see Chapter 6, "Circuits and Tunnels."
7.1 Performance Monitoring Thresholds
ONS 15454 card default thresholds are based on GR-253-CORE and GR-820-CORE. If you change their settings, the following rules apply:
•The minimum threshold that you can set is 1.
•If you set a threshold to 0, no threshold crossing alert (TCA) is issued.
•You can set thresholds to any DS-N or OC-N maximum. However, CTC does not perform range checking. Setting a threshold to a value greater than what is logically possible is the same as setting the threshold to zero. No TCA will be issued.
7.2 Provisioning Electrical Cards
The ONS 15454 electrical cards (DS1-14, DS1N-14, DS3-12, DS3N-12, DS3E1-12, DS3EN-12, DS3XM-6, and EC1-12) are pre-provisioned with settings that you can modify to manage transmission quality. When you open a card in CTC and select the Provisioning tab, the following subtabs are commonly displayed:
•Line—Sets line setup parameters, such as line coding and line length. This is also where you put ports in and out of service.
•Line Threshold—Sets the line-level PM thresholds.
•Elect Path Threshold—Sets the path-level PM thresholds for electrical (DS-3/DS-1) traffic.
•SONET Threshold—Sets the path-level PM thresholds for (STS/VT1.5) traffic.
•Alarming—Sets alarm profiles for individual ports and suppresses alarms. See Chapter 10, "Alarm Monitoring and Management," for information about alarm profiles and alarm suppression.
Table 7-1 provides an overview of DS-1, DS-3, DS3E, and DS3XM parameters (an X means the item is available for the card). EC1-12 card parameters are shown in Table 7-6.
7.2.1 DS-1 Card Parameters
The ONS 15454 DS-1 cards (DS1-14 and DS1N-14) provide 14 DS-1 ports. Each port operates at 1.544 Mbps. Default thresholds are based on recommendations in GR-820-CORE, Sections 4.0.
Procedure: Modify Line and Threshold Settings for the DS-1 Card
Step 1 Display the DS1-14 or DS1N-14 in CTC card view.
Step 2 Click the Provisioning tab ( Figure 7-1).
Figure 7-1 Provisioning line parameters on the DS1-14 card
Step 3 Depending on the setting you need to modify, click the Line, Line Thrshld, Elect Path, or Sonet Thrshld subtab.
Note See Chapter 10, "Alarm Monitoring and Management" for information about the Alarm Behavior tab.
Step 4 Modify the settings shown in Table 7-2. For drop-down lists, select an item from the list. For numerics, double-click the field and type the new number.
Step 5 Click Apply.
Step 6 Repeat Steps 4 - 5 for each subtab that has parameters you want to provision.
7.2.2 DS-3 Card Parameters
The ONS 15454 DS-3 cards (DS3-12 and DS3N-12) provide 12 DS-1 ports. Each port operates at 44.736 Mbps. Default thresholds are based on recommendations in GR-820-CORE, Section 5.0.
Procedure: Modify Line and Threshold Settings for the DS-3 Card
Step 1 Display the DS3-12 or DS3N-12 in CTC card view.
Step 2 Click the Provisioning tab.
Step 3 Depending on the setting you need to modify, click the Line, Line Thrshld, or Sonet Thrshld subtab.
Note See Chapter 10, "Alarm Monitoring and Management" for information about the Alarm Behavior tab.
Step 4 Modify the settings shown in Table 7-3. For drop-down lists, select an item from the list. For numerics, double-click the field and type the new number.
Step 5 Click Apply.
Step 6 Repeat Steps 4 - 5 for each subtab that has parameters you want to provision.
7.2.3 DS3E Card Parameters
The DS3E-12 and DS3EN-12 cards provide 12 DS-3 ports. Each port operates at 44.736 Mbps. The DS3E uses B3ZS error monitoring and enhanced performance monitoring, including P-Bit and CP-Bit monitoring. Default thresholds are based on recommendations in GR-820-CORE, Section 5.0.
Note If the DS3E is installed in an ONS 15454 slot that is provisioned for a DS-3 card, the DS3E enhanced performance monitoring parameters are not available. If this occurs, remove the DS3E from the ONS 15454, delete the DS-3 card in CTC, and provision the slot for the DS3E.
Procedure: Modify Line and Threshold Settings for the DS3E Card
Step 1 Display the DS3E-12 or DS3EN-12 in CTC card view.
Step 2 Click the Provisioning tab.
Step 3 Depending on the setting you need to modify, click the Line, Line Thrshld, Elect Path, or Sonet Thrshld subtab.
Note See Chapter 10, "Alarm Monitoring and Management" for information about the Alarm Behavior tab.
Step 4 Modify the settings shown in Table 7-4. For drop-down lists, select an item from the list. For numerics, double-click the field and type the new number.
Step 5 Click Apply.
Step 6 Repeat Steps 4 - 5 for each subtab that has parameters you want to provision.
7.2.4 DS3XM-6 Card Parameters
The DS3XM-6 transmux card can accept up to six DS-3 signals and convert each signal to 28 VT1.5s. Conversely, the card can take 28 T-1s and multiplex them into a channeled C-bit or M23 framed DS-3. Unlike the DS3-12 and DS3N-12 cards, the DS3XM-6 allows circuit mapping at the VT level. Table 7-5 shows parameters that you can provision for each port.
Procedure: Modify Line and Threshold Settings for the DS3XM-6 Card
Step 1 Display the DS3XM-6 in CTC card view.
Step 2 Click the Provisioning tab.
Step 3 Depending on the setting you need to modify, click the Line, Line Thrshld, Elect Path, or Sonet Thrshld subtab.
Note See Chapter 10, "Alarm Monitoring and Management" for information about the Alarm Behavior tab.
Step 4 Modify the settings shown in Table 7-5. For drop-down lists, select an item from the list. For numerics, double-click the field and type the new number.
Step 5 Click Apply.
Step 6 Repeat Steps 4 - 5 for each subtab that has parameters you want to provision.
7.2.5 EC1-12 Card Parameters
The EC1-12 provides 12 STS-1 electrical ports. Each port operates at 51.840 Mbps. Table 7-6 shows the parameters for the EC1-12 card.
Procedure: Modify Line and Threshold Settings for the EC-1 Card
Step 1 Display the EC1-12 in CTC card view.
Step 2 Click the Provisioning tab.
Step 3 Depending on the setting you need to modify, click the Line, Thresholds, or STS subtab.
Note See Chapter 10, "Alarm Monitoring and Management" for information about the Alarm Behavior tab.
Step 4 Modify the settings shown in Table 7-6. For drop-down lists, select an item from the list. For numerics, double-click the field and type the new number.
Table 7-6 EC1-12 Card Parameters
Subtab Parameter Description Options LinePort #
EC-1 card port #
1 - 12
Port Name
Name assigned to the port (optional)
To enter a name for the port, click the cell and type the name. To change a name, double-click the cell, then edit the text.
PJStsMon#
Sets the STS that will be used for pointer justification. If set to zero, no STS is used. See the "Pointer Justification Count Parameters" section on page 8-12 for more information.
•0 (default)
•1
Line Buildout
Defines the distance (in feet) from backplane to next termination point
•0 - 225 (default)
•226 - 450
Rx Equalization
For early EC1-12 card versions, equalization can be turned off if the line length is short or the environment is extremely cold; Rx Equalization should normally be set to On
•On (checked, default)
•Off (unchecked)
Status
Places the port in or out of service
•Out of Service (default)
•In Service
Thresholds - LineCV
Coding violations
Numeric. Defaults:
•1312 (15 minutes)
•13120 (1 day)
ES
Errored seconds
Numeric. Defaults:
•87 (15 minutes)
•864 (1 day)
SES
Severely errored seconds
Numeric. Defaults:
•1 (15 minutes)
•4 (1 day)
FC
Failure count
Numeric. Defaults:
•10 (15 minutes)
•0 (1 day)
UAS
Unavailable seconds
Numeric. Defaults:
•3 (15 minutes)
•10 (1 day)
PPJC-Pdet
Positive Pointer Justification Count, STS Path Detected. See the "Pointer Justification Count Parameters" section on page 8-12 for more information.
Numeric. Defaults (near end):
•60 (15 minutes)
•5760 (1 day)
NPJC-Pdet
Negative Pointer Justification Count, STS Path Detected. See the "Pointer Justification Count Parameters" section on page 8-12 for more information.
Numeric. Defaults
•0 (15 minutes)
•0 (1 day)
PPJC-Pgen
Positive Pointer Justification Count, STS Path Generated. See the "Pointer Justification Count Parameters" section on page 8-12 for more information.
Numeric. Defaults:
•0 (15 minutes)
•0 (1 day)
NPJC-Pgen
Negative Pointer Justification Count, STS Path Generated. See the "Pointer Justification Count Parameters" section on page 8-12 for more information.
Numeric. Defaults:
•0 (15 minutes)
•0 (1 day)
Thresholds - SectionCV
Coding violations
Numeric. Defaults (Near End only):
10000 (15 minutes)
100000 (1 day)
ES
Errored seconds
500 (15 minutes)
5000 (1 day)
SES
Severely errored seconds
500 (15 minutes)
5000 (1 day)
SEFS
Severely errored framing seconds
500 (15 minutes)
5000 (1 day)
Thresholds - PathCV
Coding violations
Numeric. Defaults (Near and Far End):
15 (15 minutes)
125 (1 day)
ES
Errored seconds
12 (15 minutes)
100 (1 day)
FC
Failure count
10 (15 minutes)
10 (1 day)
SES
Severely errored seconds
3 (15 minutes)
7 (1 day)
UAS
Unavailable seconds
10 (15 minutes)
10 (1 day)
STSSTS #
EC-1 port (Line #) and STS # available for Intermediate Path Performance Monitoring.
Enable IPPM
Enables IPPM for the EC-1 port and STS #
Unchecked (default); IPPM not enabled
Checked; IPPM is enabled
AlarmingPort
Port number
1 - 12
Profile
Sets the alarm profile for the port.
Default
Inherited
Custom profiles (if any)
Suppress Alarms
Suppresses alarm display for the port.
Unselected (default)
Selected
Step 5 Click Apply.
Step 6 Repeat Steps 4 - 5 for each subtab that has parameters you want to provision.
7.3 Provisioning Optical Cards
This section explains how to modify transmission quality by provisioning line and threshold settings for OC-N cards and how to provision OC-N cards for SDH.
7.3.1 Modifying Transmission Quality
The OC-3, OC-12, OC-48, and OC-192 cards are pre-provisioned with settings that you can modify to manage transmission quality. Depending on the optical card, you can specify thresholds for near and far end nodes at the Line, Section, and Path levels for 15-minute and one day intervals.
Procedure: Provision Line Transmission Settings for OC-N Cards
Step 1 Display the OC-N card in CTC card view.
Step 2 Click the Provisioning > Line tabs.
Step 3 Modify the settings shown in Table 7-7.
Table 7-7 OC-N Card Line Settings on the Provisioning > Line Tab
Heading Description Options#
Port number
•1 (OC-12, OC-48, OC-192)
•1-4 (OC-3)
SF BER Level
Sets the signal fail bit error rate
•1E-3
•1E-4 (default)
•1E-5
SD BER Level
Sets the signal degrade bit error rate
•1E-5
•1E-6
•1E-7 (default)
•1E-8
•1E-9
Provides Synch
If checked, the card is provisioned as a network element timing reference on the Provisioning > Timing tabs
Read-only
•Yes (checked)
•No (unchecked)
Enable Synch Messages
Enables synchronization status messages (S1 byte), which allow the node to choose the best timing source
•Yes (checked, default)
•No (unchecked)
Send Do Not Use
When checked, sends a DUS (do not use) message on the S1 byte
•Yes (checked)
•No (unchecked; default)
PJ Sts Mon #
Sets the STS that will be used for pointer justification. If set to 0, no STS is monitored. Only one STS can be monitored on each OC-N port. See the "Pointer Justification Count Parameters" section on page 8-12 for more information.
•0 (default) - 3 (OC-3, per port)
•0 (default) - 12 (OC-12)
•0 (default) - 48 (OC-48)
•0 (default) - 192 (OC-192)
Status
Places port in or out of service
•Out of Service (default
•In Service
Type
Defines the port as SONET or SDH. See the "Provisioning OC-N Cards for SDH" section.
•Sonet
•SDH
Step 4 Click Apply.
Procedure: Provision Threshold Settings for OC-N Cards
Step 1 Display the OC-N card in CTC card view ( Figure 7-2).
Step 2 Click the Provisioning > Thresholds tabs.
Figure 7-2 Provisioning thresholds for the OC48 IR 1310 card
Step 3 Modify the settings shown in Table 7-8.
Default thresholds apply to all optical cards unless otherwise specified.
Table 7-8 OC-N Card Threshold Settings on the Provisioning > Thresholds Tab
Heading Description Options PortPort number
•1, 2, 3, or 4 (OC-3)
•1 (OC-12, OC-48, OC-192)
CVCoding violations
Numeric. Defaults (15 min/1 day):
Line
•1312/13,120 (OC-3 Near & Far End)
•5315/53150 (OC-12 Near & Far End)
•21260/212600 (OC-48 Near & Far End)
•85040/850400 (OC-192 Near & Far End)
Section
•10000/100000 (Near End) 0/0 (Far End)
•10000/500 (OC-192 Near & Far End)
Path
•15/125 (OC-12, OC-48, OC-192 Near & Far End)
ESErrored seconds
Numeric. Default (15 min/1 day):
Line
•87/864 (Near & Far End)
Section
•500/5000 (Near End); 0/0 (Far End)
Path
•12/100 (OC-48 & OC-192 Near & Far End)
SESSeverely errored seconds
Numeric. Defaults (15 min/1 day):
Line
•1/4 (Near and Far End)
Section
•500/5000 (Near End); 0/0 (Far End)
Path
•3/7 (OC-48 & OC-192 Near & Far End)
SEFSSeverely errored framing seconds
Numeric. Defaults (15 min/1 day):
Section
•500/5000 (Near End); 0/0 (Far End)
FCFailure count
Numeric. Defaults (15 min/1 day):
Line
•10/0 (OC-3, Near and Far End)
•10/40 (OC-12, OC-48, OC-192 Near and Far End)
Path
•10/10 (OC-12, OC-48, OC-192 Near and Far End)
UASUnavailable seconds
Numeric. Defaults (15 min/1 day):
Line
•3/3 (OC-3, Near & Far End
•3/10 (OC-12, OC-48, OC-192 Near and Far End)
Path
•10/10 (Near and Far End)
PPJC-PdetPositive Pointer Justification Count, STS Path detected. See the "Pointer Justification Count Parameters" section on page 8-12 for more information.
Numeric. Defaults (15 min/1 day):
Line
•60/5760 Near End
•0/0 Far End
NPJC-PdetNegative Pointer Justification Count, STS Path detected. See the "Pointer Justification Count Parameters" section on page 8-12 for more information.
Numeric. Defaults (Near and Far End):
Line
•0 (15 minutes)
•0 (1 day)
PPJC-PgenPositive Pointer Justification Count, STS Path generated. See the "Pointer Justification Count Parameters" section on page 8-12 for more information.
Numeric. Defaults (15 min/1 day):
Line
•0/0 (Near and Far End)
NPJC-PgenNegative Pointer Justification Count, STS Path generated. See the "Pointer Justification Count Parameters" section on page 8-12 for more information.
Numeric. Defaults (15 min/1 day):
Line
•0/0 (Near and Far End)
PSCProtection Switching Count (Line)
Numeric. Defaults (15 min/1 day):
Line
•1/5 (Near End)
•0/0 (Far End)
PSDProtection Switch Duration (Line)
Numeric. Defaults (15 min/1 day):
Line
•300/600 (Near End)
•0/0 (all OC-N cards, Far End)
PSC-WProtection Switching Count - Working line
BLSR is not supported on the OC-3 card; therefore, the PSC-W, PSC-S, and PSC-R PMs do not increment.
Numeric. Defaults (15 min/1 day):
Line
•0/0 (all OC-N cards except OC-3, Near and Far End)
PSD-WProtection Switching Duration - Working line
BLSR is not supported on the OC-3 card; therefore, the PSD-W, PSD-S, and PSD-R PMs do not increment.
Numeric. Defaults (15 min/1 day):
Line
•0/0 (all OC-N cards except OC-3, Near and Far End)
PSC-SProtection Switching Duration - Span
BLSR is not supported on the OC-3 card; therefore, the PSC-W, PSC-S, and PSC-R PMs do not increment.
Numeric. Defaults (15 min/1 day):
Line
•0/0 (all OC-N cards except OC-3, Near and Far End)
PSD-SProtection Switching Duration - Span
BLSR is not supported on the OC-3 card; therefore, the PSD-W, PSD-S, and PSD-R PMs do not increment.
Numeric. Defaults (15 min/1 day):
Line
•0/0 (all OC-N cards except OC-3, Near and Far End)
PSC-RProtection Switching Duration - Ring
BLSR is not supported on the OC-3 card; therefore, the PSC-W, PSC-S, and PSC-R PMs do not increment.
Numeric. Defaults (15 min/1 day):
Line
•0/0 (all OC-N cards except OC-3, Near and Far End)
PSD-RProtection Switching Duration - Ring
BLSR is not supported on the OC-3 card; therefore, the PSD-W, PSD-S, and PSD-R PMs do not increment.
Numeric. Defaults (15 min/1 day):
Line
•0/0 (all OC-N cards except OC-3, Near and Far End)
Click Apply.
7.3.2 Provisioning OC-N Cards for SDH
You can provision the ONS 15454 OC-3, OC-12, and OC-48 cards to support either SONET or SDH over SONET signals. When provisioned for SDH, each OC-N port drops and inserts STM traffic in unprotected or 1+1 protection mode. Each STM-1 signal is mapped as a 155 Mbps concatenated signal (STS-3c) for transparent transport over a SONET network. The original STM-1 traffic may be handed off as an STM-1 or OC-3.
Because SDH and SONET frame format and size are nearly identical, their line speeds meet, starting at 155 Mbps. For example, at the STM-1/OC-3 level, the ONS 15454 performs section and line overhead conversions and maps the 261x9 byte VC-4 into an STS-3c for transparent transport across the SONET domain. At the far end, the STS-3c carrying the original VC-4 is remapped into an STM-1 for handoff to an SDH network element (node). Table 7-9 shows the SDH over SONET mapping for the ONS 15454 OC-N cards.
Table 7-9 OC-N - SDH Over SONET Mapping
Card SDH SDH over SONETOC-3
STM-1
STS-3c
OC-12
STM-4
STS-12c
OC-48
STM-16
STS-48c
OC-192
STM-64
STS-192c
The ONS 15454 performs section, line overhead, and pointer conversions between SDH and SONET. However, to ensure operability, the following requirements must be met:
•The embedded payload must be compatible on both sides and require no conversion of any kind. Examples of such payloads include concatenated ATM or Packet over SONET/SDH signals.
•The path overhead (POH) must be compatible on both sides and require no conversion of any kind. Each overhead byte must be processed identically or simultaneously ignored. Key POH bytes to consider are the J1 (path indicator) and C2 (payload format).
•You cannot enable intermediate path protection monitoring (IPPM) on OC-12 and OC-48 ports that are enabled for SDH.
Most SONET and SDH routers and ATM switches can be configured to meet these requirements.
Procedure: Provision an OC-N Card for SDH
Step 1 Log into the node and double-click the OC-N card.
Step 2 Click the Provisioning > Line tabs.
Step 3 Under Type, choose SDH.
Step 4 Click Apply.
7.4 Provisioning IPPM
Intermediate-Path Performance Monitoring (IPPM) allows you to transparently monitor traffic originating on DS-1, DS-3, DS3E and DS3XM cards (Path Terminating Equipment) as it passes through EC-1, OC-3, OC-12, OC-48, and OC-192 cards (Line Terminating Equipment). To use IPPM, you create the STS circuit on the DS-N cards, then enable IPPM on the EC-1 or OC-N cards that carry the circuit.
Note For Release 3.0 and later, IPPM is enabled for near-end (originating) traffic only. Far-end (terminating) IPPM will be enabled in a future release.
For example, suppose you have an STS circuit that originates and terminates on DS-N cards at Nodes 1 and 4. You want to monitor the circuit as it passes through OC-N cards at Nodes 2 and 3. To do this, you enable IPPM on the OC-N card by selecting the appropriate STS, in this example, STS 1 ( Figure 7-3).
Figure 7-3 IPPM provisioned for STS 1 on an OC-12 card
After enabling IPPM, performance is displayed on the Performance tab for the OC-48 card. IPPM enables per-path statistics for STS CV-P (coding violations), STS ES-P (errored seconds), STS FC-P (failure count), STS SES-P (severely errored seconds), and STS UAS-P (unavailable seconds). Only one STS per port can be monitored at one time. See Chapter 8, "Performance Monitoring" for a definition of every parameter.
Procedure: Enable Intermediate-Path Performance Monitoring
Step 1 If the STS circuit does not exist, create the circuit. (The circuit must pass through the EC-1 or OC-N card before you can enable IPPM on the circuit.)
Step 2 In CTC, open the card view of an EC-1 or OC-N card that carries the circuit.
Step 3 Select the Provisioning > STS tabs.
Step 4 Click Enable IPPM for the STS you want to monitor.
Step 5 Click Apply.
7.5 Provisioning the Alarm Interface Controller
The Alarm Interface Controller (AIC) card can be provisioned to receive input from, or send output to, external devices wired to the ONS 15454 backplane. (For detailed specifications about the AIC, refer to the Cisco ONS 15454 Troubleshooting and Maintenance Guide.) You can provision the AIC to:
•Generate CTC alarms based on events such as heating or cooling equipment failure, fire alarms, smoke detection, and other environmental changes that can damage ONS 15454 equipment. These are called external alarms.
•Turn external devices on or off based on a CTC alarm. For example, you can provision the AIC to turn on an audio or visual device, such as a bell or light, when a critical ONS 15454 alarm occurs. These triggers are called external controls.
Figure 7-4 shows the flow to and from external devices provisioned through the AIC.
Figure 7-4 AIC alarm input and output
7.5.1 Using Virtual Wires
Provisioning the AIC card provides a "virtual wires" option used to route external alarms and controls from different nodes to one or more alarm collection centers. In Figure 7-5, smoke detectors at Nodes 1, 2, 3, and 4 are assigned to Virtual Wire #1, and Virtual Wire #1 is provisioned as the trigger for an external bell at Node 1.
Figure 7-5 External alarms and controls using a virtual wire
When using AIC virtual wires, you can:
•Assign different external devices to the same virtual wire.
•Assign virtual wires as the trigger type for different external controls.
Procedure: Provision External Alarms
Step 1 Wire the external-device relays to the ENVIR ALARMS IN backplane pins. See the "Alarm, Timing, LAN, and Craft Pin Connections" section on page 1-32 for more information.
Step 2 Log into the node in CTC and display the AIC in card view.
Step 3 Click the Provisioning > External Alarms tabs ( Figure 7-6).
Step 4 Complete the following fields for each external device wired to the ONS 15454 backplane:
•Enabled—Click to activate the fields for the alarm input number.
•Alarm Type—Select an alarm type from the provided list.
•Severity—Select a severity. The severity determines how the alarm is displayed in the CTC Alarms and History tabs and whether the LEDs are activated. Critical, Major, and Minor activate the appropriate LEDs. Not Alarmed and Not Reported do not activate LEDs, but do report the information in CTC.
•Virtual Wire—To assign the external device to a virtual wire, select the virtual wire. Otherwise, do not change the None default.
•Raised When—Select the contact condition (open or closed) that will trigger the alarm in CTC.
•Description—Default descriptions are provided for each alarm type; change the description as necessary.
Figure 7-6 Provisioning external alarms on the AIC card
Step 5 To provision additional devices, complete Step 4 for each additional device.
Step 6 Click Apply.
Procedure: Provision External Controls
Step 1 Wire the external control relays to the ENVIR ALARMS OUT backplane pins. See the "Alarm, Timing, LAN, and Craft Pin Connections" section on page 1-32 for more information.
Step 2 In CTC, log into the node and display the AIC in card view.
Step 3 On the External Controls subtab, complete the following fields for each external control wired to the ONS 15454 backplane:
•Enabled—Click to activate the fields for the alarm input number.
•Trigger Type—Select a trigger type: a local minor, major, or critical alarm; a remote minor, major, or critical alarm; or a virtual wire activation.
•Description—Enter a description.
Step 4 To provision additional controls, complete Step 3 for each additional device.
Step 5 Click Apply.
7.5.2 Provisioning AIC Orderwire
The AIC provides RJ-11 jacks to allow onsite personnel to communicate with one another using standard phone sets. The AIC Local and Express orderwire channels are carried on the SONET Orderwire overhead:
•Local orderwire is carried on the SONET Section layer E1 byte. Regenerators between ONS 15454 nodes terminate the channel.
•Express orderwire is carried on the E2 byte of the SONET Line layer.
If regenerators are not used between ONS 15454 nodes, local or express AIC orderwire channels can be used. If regenerators exist, use the Express orderwire channel. You can provision up to four ONS 15454 OC-N ports for each orderwire path.
Caution When provisioning orderwire for ONS 15454s residing in a ring, do not provision a complete orderwire loop. For example, a four-node ring typically has east and west ports provisioned at all four nodes. However, to prevent orderwire loops, provision two orderwire ports (east and west) at all but one of the ring nodes.
Procedure: Provision AIC Orderwire
Tip Before you begin, make a list of the ONS 15454 slots and ports that require orderwire communication.
Step 1 In CTC, open the AIC card view.
Step 2 Select the orderwire subtab, Local Orderwire or Express Orderwire, appropriate to the orderwire path that you want to create.
The Local Orderwire subtab is shown in Figure 7-7. Provisioning procedures are the same for both types of orderwire.
Figure 7-7 Provisioning local orderwire
Step 3 In the Available Ports list, select each port that you want to use for the orderwire channel and click Add to move them to the Selected Ports column.
Step 4 If needed, adjust the Tx and Rx dBm by moving the slider to the right or left for the headset type (four-wire or two-wire) that you will use. In general, you should not need to adjust the dBm.
Step 5 Click Apply.
7.5.3 Using the AIC Orderwire
The AIC orderwire channels function as a party line. Anyone plugging a phone set into an AIC orderwire channel can communicate with all participants on the connected orderwire. The AIC does not provide private, point-to-point connections. To alert participants, press the AIC Call button to activate a buzzer and illuminate the RING LED on AICs at all connected nodes.
7.6 Converting DS-1 and DS-3 Cards From 1:1 to 1:N Protection
The ONS 15454 provides three protection options for DS1-14 and DS3-12 cards: unprotected, 1:1, and 1:N (N=5 or less). Changing protection from 1:1 to 1:N increases the available bandwidth because two of the three cards used for protection in the 1:1 protection group become working cards in the 1:N group.
When setting up 1:N protection, install the DS1N-14 or DS3N-12 card in Slot 3 or 15 on the same side of the ONS 15454 as the cards it protects. Slot 3 protects cards in Slots 1 - 2 and 4 - 6. Slot 15 protects Slots 12 - 14 and 16 - 17. A DS1N-14 or DS3N-12 card installed in Slot 3 or 15 can protect up to five DS1-14 or DS3-12 cards. If you install a DS3N-12 or DS1N-14 card in another slot, it behaves like a normal DS-1 or DS-3 card.
To create 1:1 protection for DS-1 and DS-3 cards, see the "Creating Protection Groups" section on page 3-9.
Procedure: Convert DS1-14 Cards From 1:1 to 1:N Protection
Note This procedure assumes DS1-14 cards are installed in Slots 1 through 6 and/or Slots 12 through 17. The DS1-14 cards in Slots 3 and 15, which are the protection slots, will be replaced with DS1N-14 cards. The ONS 15454 must run CTC Release 2.0 or later. The procedure also requires at least one DS1N-14 card and a protection group with DS1-14 cards.
Step 1 In node view, click the Maintenance > Protection tabs.
Step 2 Click the protection group that contains Slot 3 or Slot 15 (where you will install the DS1N-14 card).
Step 3 Make sure the slot you are upgrading is not carrying working traffic. In the Selected Group list, the protect slot must say Protect/Standby (shown in Figure 7-8) and not Protect/Active. If the protect slot status is Protect/Active, use the following steps to switch traffic to the working card:
a. Under Selected Group, click the protect card.
b. Next to Switch Commands, click Switch.
The working slot should change to Working/Active and the protect slot should change to Protect/Standby. If they do not change, do not continue. Troubleshoot the working card and slot to determine why the card cannot carry working traffic.
c. Next to Switch Commands, select Clear.
Figure 7-8 Viewing slot protection status
Step 4 Repeat Steps 1 - 3 for each protection group that you need to convert.
Step 5 Verify that no standing alarms exist for any of the DS1-14 cards that you are converting. If alarms exist and you have difficulty clearing them, contact your next level of support.
Step 6 Click the Provisioning > Protection tabs.
Step 7 Click the 1:1 protection group that contains the cards that you will move into the new protection group.
Step 8 Click Delete.
Step 9 When the confirmation dialog displays, click Yes.
Note Deleting the 1:1 protection groups does not disrupt service. However, no protection bandwidth exists for the working circuits until you complete the 1:N protection procedure. Therefore, complete this procedure as quickly as possible.
Step 10 If needed, repeat Steps 7- 9 for other protection groups.
Step 11 On the node view, right-click the DS1-14 card in Slot 3 or Slot 15 and select Delete from the shortcut menu.
Step 12 Physically remove the DS1-14 card from Slot 3 or Slot 15. This raises an improper removal alarm.
Step 13 In node view, right-click the slot that held the removed card and select delete from the pull-down menu. Wait for the card to disappear from the node view.
Step 14 Physically insert a DS1N-14 card into the same slot.
Step 15 Verify that the card boots up properly.
Step 16 Click the Inventory tab and verify that the new card appears as a DS1N-14.
Step 17 Click the Provisioning > Protection tabs.
Step 18 Click Create. The Create Protection Group dialog opens with the protect card in the Protect Card field and the available cards in the Available Cards field.
Step 19 Type a name for the protection group in the Name field (optional).
Step 20 Click Type and choose 1:N (card) from the pull-down menu.
Step 21 Verify that the DS1N-14 card appears in the Protect Card field.
Step 22 Under Available Cards, highlight the cards that you want in the protection group. Click the arrow (>>) tab to move the cards to the Working Cards list.
Step 23 Click OK. The protection group appears in the Protection Groups list on the Protection subtab.
Procedure: Convert DS3-12 Cards From 1:1 to 1:N Protection
Note This procedure assumes that DS3-12 cards are installed in Slots 1 - 6 and/or Slots 12 - 17. The DS3-12 cards in Slots 3 and 15, which are the protection slots, will be replaced with DS3N-12 cards. The ONS 15454 must run CTC Release 2.0 or later. The procedure also requires at least one DS3N-12 card and a protection group with DS3-12 cards.
Step 1 In node view, click the Maintenance > Protection tabs.
Step 2 Click the protection group containing Slot 13 or Slot 15 (where you will install the DS3N-12 card).
Step 3 Make sure the slot you are upgrading is not carrying working traffic. In the Selected Group list, the protect slot must say Protect/Standby as shown in Figure 7-8, and not Protect/Active. If the protect slot status is Protect/Active, use the following steps to switch traffic to the working card:
a. Under Selected Group, click the protect card.
b. Next to Switch Commands, click Switch.
The working slot should change to Working/Active and the protect slot should change to Protect/Standby. If they fail to change, do not continue. Troubleshoot the working card and slot to determine why the card cannot carry working traffic.
c. Next to Switch Commands, click Clear.
Step 4 Repeat Steps 2 and 3 for each protection group that you need to convert.
Step 5 Verify that no standing alarms exist for any of the DS3-12 cards you are converting. If alarms exist and you have difficulty clearing them, contact your next level of support.
Step 6 Click the Provisioning > Protection tabs.
Step 7 Click the 1:1 protection group that contains the cards that you will move into the new protection group.
Step 8 Click Delete.
Step 9 When the confirmation dialog displays, click Yes.
Note Deleting the 1:1 protection groups will not disrupt service. However, no protection bandwidth exists for the working circuits until the 1:N protection procedure is completed. Do not delay when completing this procedure.
Step 10 If you are deleting more than one protection group, repeat Steps 7-9 for each group.
Step 11 On the node view, right-click the DS3-12 card in Slot 3 or Slot 15 and choose Delete from the shortcut menu.
Step 12 Physically remove the DS3-12 card from Slot 3 or Slot 15. This raises an improper removal alarm.
Step 13 In node view, right-click the slot that held the removed card and choose Delete from the pull-down menu. Wait for the card to disappear from the node view.
Step 14 Physically insert a DS3N-12 card into the same slot.
Step 15 Verify that the card boots up properly.
Step 16 Click the Inventory tab and verify that the new card appears as a DS3N-12.
Step 17 Click the Provisioning > Protection tabs.
Step 18 Click Create.
The Create Protection Group dialog shows the protect card in the Protect Card field and the available cards in the Available Cards field.
Step 19 Type a name for the protection group in the Name field (optional).
Step 20 Click Type and choose 1:N (card) from the pull-down menu.
Step 21 Verify that the DS3N-12 card appears in the Protect Card field.
Step 22 In the Available Cards list, highlight the cards that you want in the protection group. Click the arrow (>>) tab to move the cards to the Working Cards list.
Step 23 Click OK.
The protection group should appear in the Protection Groups list on the Protection subtab.
Posted: Fri Feb 22 16:15:42 PST 2008
All contents are Copyright © 1992--2008 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.