Table Of Contents
Manage Alarms
Before You Begin
NTP-80 Document Existing Provisioning
DLP-138 Print CTC Data
DLP-139 Export CTC Data
NTP-67 View Alarms, History, Events, and Conditions
DLP-110 View Alarm History
DLP-111 Changing the Maximum Number of Session Entries for Alarm History
DLP-112 Display Alarms and Events Using Each Node's Timezone
DLP-113 View Events and Synchronize Alarms
DLP-114 View Conditions
NTP-68 Delete Cleared Alarms from Display
NTP-69 View Alarm-Affected Circuits
NTP-70 View Alarm Counts on the LCD for a Slot or Port
NTP-71 Create, Download, and Assign Alarm Severity Profiles
DLP-115 Create Alarm Severity Profiles
DLP-223 Download an Alarm Severity Profile
DLP-116 Apply Alarm Profiles to Ports
DLP-117 Apply Alarm Profiles to Cards and Nodes
DLP-118 Delete Alarm Severity Profiles
NTP-168 Enable, Modify, or Disable Alarm Severity Filtering
DLP-225 Enable Alarm Filtering
DLP-226 Modify Alarm and Condition Filtering Parameters
DLP-227 Disable Alarm Filtering
NTP-72 Suppress and Unsuppress Alarm Reporting
DLP-119 Suppress Alarm Reporting
DLP-120 Unsuppress Alarm Reporting
Manage Alarms
This chapter explains how to view and manage the alarms and conditions on a Cisco ONS 15454.
CTC detects and reports SONET alarms generated by the Cisco ONS 15454 and the larger SONET network. You can use Cisco Transport Controller (CTC) to monitor and manage alarms at a card, node, or network level and view alarm counts on the LCD front panel.
Before You Begin
This section lists the chapter procedures (NTPs). Turn to a procedure for applicable tasks (DLPs).
1. 
NTP-80 Document Existing Provisioning—Complete this procedure as needed to record node information for troubleshooting rings and spans.
2. NTP-67 View Alarms, History, Events, and Conditions—Complete this procedure as needed to see alarms and conditions occurring on the node and a complete history of alarm and condition messages to determine trouble occurrence patterns when troubleshooting.
3. NTP-68 Delete Cleared Alarms from Display—Complete this procedure as needed to delete cleared alarm information that is no longer needed.
4. NTP-69 View Alarm-Affected Circuits—Complete this procedure as needed to find circuits that are affected by a particular alarm or condition.
5. NTP-70 View Alarm Counts on the LCD for a Slot or Port—Complete this procedure as needed to see a statistical count of alarms that have occurred for a slot or port.
6. NTP-71 Create, Download, and Assign Alarm Severity Profiles—Complete this procedure as needed to change the default severity for certain alarms, assign the new severities to a port, card, or node, and delete alarm profiles.
7. NTP-168 Enable, Modify, or Disable Alarm Severity Filtering—Complete this procedure as needed to enable, disable, or modify alarm severity filtering in the Conditions, Alarms, or History screens; you can enable, modify, and disable alarm severity filtering at the node or network level.
8. NTP-72 Suppress and Unsuppress Alarm Reporting—As needed, use these tasks to suppress reported alarms at the port, card, or node level and disable the suppress command to resume normal alarm reporting.
NTP-80 Document Existing Provisioning
Purpose
|
Use this procedure to record node information for troubleshooting rings and spans.
|
Tools/Equipment
|
A printer must be connected to the CTC computer
|
Prerequisite Procedures
|
"Turn Up Node"
|
Required/As needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 Log into the ONS 15454 that has the information you want to record or save. See the "DLP-60 Log into CTC" task for instructions. If you are already logged in, go to Step 2.
Step 2 If you need to document information that you cannot write down, or need to preserve, you can do so by
•Copying and pasting CTC text into other applications using the Windows Copy (Ctrl+C), Cut (Ctrl+X), and Paste (Ctrl+V) commands.
•Printing information with the "DLP-138 Print CTC Data" task.
•Saving information to a word processing application such as a spreadsheet; complete the "DLP-139 Export CTC Data" task.
DLP-138 Print CTC Data
Purpose
|
Use this task to print CTC windows and CTC table data such as alarms and inventory.
|
Tools/Equipment
|
A printer must be connected to the CTC computer
|
Prerequisite procedures
|
DLP-60 Log into CTC
|
Required/As needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 Click the CTC tab containing the information you want to print (for example, the Alarms tab or the Circuits tab).
Step 2 From the CTC File menu, click Print.
Step 3 In the Print dialog box choose an option ( Figure 7-1):
•Entire Frame—Prints the entire CTC window
•Tabbed View—Prints the lower half of the CTC window
•Table Contents—Prints CTC data in table format; this option is only available for CTC table data (see the "Table Display Options" section).
Figure 7-1 Selecting CTC data for print
Step 4 Click OK.
Step 5 In the Windows Print dialog box, choose a printer and click Print.
Step 6 Repeat this task for each tab that you want to print.
Step 7 Return to your originating procedure (NTP).
DLP-139 Export CTC Data
Purpose
|
Use this task to export CTC table data for use by other applications such as spreadsheets, word processors, and database management applications.
|
Tools/Equipment
|
None
|
Prerequisite procedures
|
DLP-60 Log into CTC
|
Required/As needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 Click the CTC tab containing the information you want to export (for example, the Alarms tab or the Circuits tab).
Step 2 From the CTC File menu, click Export.
Step 3 In the Export dialog box ( Figure 7-2) choose a format for the data:
•As HTML—Saves the data as an HTML file. The file can be viewed with a web browser (such as Netscape Navigator or Microsoft Internet Explorer) without running CTC. Use the browser's File/Open command to open the CTC data file.
•As CSV—Saves the CTC table values as text, separated by commas. You can import CSV data into spreadsheets and database management programs.
•As TSV—Saves the CTC table values as text, separated by tabs. You can import TSV data into spreadsheets and database management programs.
Figure 7-2 Selecting CTC data for export
Step 4 Click OK.
Step 5 In the Save dialog box, enter a file name in one of the following formats:
•[filename].htm—for HTML files
•[filename].csv—for CSV files
•[filename].tsv—for TSV files
Step 6 Navigate to a directory where you want to store the file.
Step 7 Click OK.
Step 8 Repeat the task for each tab that you want to export.
Note CTC data exported as comma separated values (CSV) or tab separated values (TSV) can be viewed in text editors, word processors, spreadsheets, and database management applications. Although procedures depend on the application, you typically can use File/Open to display the CTC data. Text editors and word processors display the data exactly as it is exported. Spreadsheet and database management applications display the data in cells. You can then format and manage the data using the spreadsheet or database management application tools.
Step 9 Return to your originating procedure (NTP).
NTP-67 View Alarms, History, Events, and Conditions
Purpose
|
Use this procedure to view alarms and conditions occurring on the node and to retrieve a complete history of event messages.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
None
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 Log into the node that contains the alarms you want to view. See the "DLP-60 Log into CTC" task for instructions. If you are already logged in, go to Step 2.
Step 2 At the card, node, or network-level CTC view, click the Alarms tab to display the alarms for that card, node, or network ( Figure 7-3).
Step 3 Troubleshoot the alarms using the Cisco ONS 15454 Troubleshooting Guide.
Step 4 Complete the "DLP-110 View Alarm History" task, the "DLP-113 View Events and Synchronize Alarms" task, or the "DLP-114 View Conditions" task as needed.
Figure 7-3 Viewing alarms in the CTC network view
DLP-110 View Alarm History
Purpose
|
Use this task to view past cleared and uncleared ONS 15454 alarm messages at the card, node, or network level.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
None
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve
|
Step 1 Decide whether you want to view the alarm message history at the node, network or card level.
For the node-level alarm history, go to Step 2. For the network-level alarm message history, go to Step 3. For the card-level alarm message history, go to Step 5.
Step 2 The node-level view is the default view after you log into CTC ( Figure 7-4). To display the node-level alarm message history:
a. Click the History > Session tabs if you want to see only the alarm messages and event messages that have occurred since you logged into the CTC.
b. Click the History > Node tabs if you want to retrieve all available alarm messages for the node. Go to Step 6.
Step 3 From the node (default login) view ( Figure 7-4), display the network view.
Step 4 Click the History tab. Alarm messages and event messages that have occurred on the network since you logged into CTC are displayed. Go to Step 9.
Step 5 Double-click a card on the shelf graphic of any card besides the TCC+ or cross-connect card to display the card-level view for the card.
a. Click the History > Session tabs if you want to see only the alarm messages and event messages that have occurred since you logged into CTC.
b. Click the History > Card tabs if you want to retrieve all available alarm messages for the card. Go to Step 6.
Note The ONS 15454 can store up to 640 critical alarm raise/clear messages, 640 major alarm raise/clear messages, 640 minor alarm raise/clear messages, and 640 event-level raise/clear/transient messages. When any of these limits is reached, the ONS 15454 discards the oldest alarms and events in that category.
Step 6 Verify that the Alarms checkbox is selected in the History > Node tabs and/or History > Card tabs to ensure that alarm messages and event messages with a severity of minor (MN), major (MJ), or critical (CR) - are reported.
Step 7 If you want to retrieve event messages, click the Events checkbox in the History > Node and/or History > Card tabs. Event messages include transient messages and also raise/clear messages for Not Alarmed (NA) standing conditions.
Step 8 In the History > Node and/or History > Card tabs, click the Retrieve button. Alarm messages are automatically shown in the network view.
Tip Double-click an alarm in the alarm table or an event message in the history table to display the view that corresponds to the alarm message. For example, double-clicking a card alarm takes you to card view. In network view, double-clicking a node alarm takes you to node (default login) view.
Figure 7-4 Viewing alarm history for the current session
Step 9 Return to your originating procedure (NTP).
DLP-111 Changing the Maximum Number of Session Entries for Alarm History
Purpose
|
Use this task to change the maximum number of session entries displayed by the alarm history from the default of 5000.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
None
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 At the card, node, or network view, from the CTC menu bar click Edit > Preferences.
The CTC Preferences Dialog appears ( Figure 7-5).
Figure 7-5 CTC Preferences Dialog featuring Maximum History Entries
Step 2 Click the up or down arrow buttons next to the Maximum History Entries field to change the entry to the desired number. The permitted range of maximum history entries is from 500 to 100,000. When the value is changed, the Apply button is enabled.
Step 3 Click Apply and OK.
Note Setting the maximum history entries entry to the high end of the range uses more CTC memory and could impair CTC performance.
Note This task changes the maximum history entries recorded for CTC sessions. It does not affect the maximum number of history entries viewable for a network, node or card.
Step 4 Return to your originating procedure (NTP).
DLP-112 Display Alarms and Events Using Each Node's Timezone
Purpose
|
Use this task to change the timestamp for events to the timezone of the ONS node reporting the alarm. By default, the events timestamp is set to the timezone for the CTC workstation.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
DLP-60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 At the card, node, or network view, from the CTC menu bar click Edit > Preferences.
The CTC Preferences Dialog appears ( Figure 7-6).
Figure 7-6 CTC Preferences Dialog featuring Maximum History Entries
Step 2 Click the Display Events Using Each Node's Timezone checkbox. The Apply button is enabled.
Step 3 Click Apply and OK.
Step 4 Return to your originating procedure (NTP).
DLP-113 View Events and Synchronize Alarms
Purpose
|
Use this task to view ONS 15454 events at the card, node, or network level and synchronize the alarm listing while troubleshooting to check for cleared alarms or conditions.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
DLP-60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve
|
Step 1 At the card, node, or network view, click the Alarms tab.
Step 2 Click the Synchronize button.
This button causes CTC to retrieve a current alarm summary for the node. This step is optional, since CTC updates the Alarms tab automatically as raise/clear messages arrive from the node.
Step 3 Return to your originating procedure (NTP).
DLP-114 View Conditions
Purpose
|
Use this task to view conditions at the card, node, or network level.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
DLP-60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve
|
Step 1 From the card, node, or network view, click the Conditions tab.
Step 2 Click the Retrieve button ( Figure 7-7).
Conditions include all fault conditions raised on the node, whether or not they are reported (i.e. messages sent) to CTC and other clients. Conditions that are reported at Major, Minor, or Critical severities are alarms. Conditions that are reported at Not Alarmed are events. Conditions that are not reported at all are marked as Not Reported in the Conditions tab severity column.
Clicking Retrieve requests the current set of fault conditions from the node. The tab is not updated when things change on the node. The operator must click Retrieve to see any changes.
Conditions have a default severity of CR, MJ, MN, or NA but are not reported at this time due to exclusion or suppression (by CTC command or port or circuit state other than IS) are shown as NR on the Conditions tab. Conditions that are currently reported are shown at the chosen reporting severity.
Note When ONS 15454 ports are placed in the out-of-service (OOS) state, OOS maintenance (OOS-MT) state, or OOS auto-in-service (OOS-AINS) state for loopback testing operations, traffic passes and performance-monitoring information is collected, but alarming is suppressed. The alarms are not reported autonomously, but can be retrieved.
When ports are placed in OOS state, the Alarms Suppressed for Maintenance (AS-MT) condition is raised on them. For more information about placing the ONS 15454 in OOS state for performing loopback tests, or for information about alarm troubleshooting, refer to the Cisco ONS 15454 Troubleshooting Guide.
Figure 7-7 Viewing fault conditions retrieved under the Conditions tabs
Step 3 If you want to apply exclusion rules, click the Exclude Same Root Cause checkbox at the node or network view.
According to Telcordia, exclusion rules apply to a query of "all conditions from a node" (the rules that apply in a "RTRV-ALM-ALL" TL1 command, but not in more specific TL1 RTRV-ALM commands). To match TL1 retrieval results, click the Exclude Same Root Cause checkbox on node view and network view, and leave it unchecked on card view.
Step 4 Return to your originating procedure (NTP).
NTP-68 Delete Cleared Alarms from Display
Purpose
|
Use this procedure to delete cleared alarms and transient messages from the CTC display when they are not needed for long-term information or later troubleshooting.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
None
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve
|
Step 1 Log into a node where you want to delete alarms. See the "DLP-60 Log into CTC" task for instructions. If you are already logged in, go to Step 2.
To delete node-level alarms, go to Step 2. To delete card-level alarms, go to Step 3. To delete network-level alarms, go to Step 4.
Step 2 To delete node-level alarms:
a. On the node (default) view click the Alarms tab.
b. Click Delete Cleared Alarms, referring to the rules in c..
This action will remove any cleared ONS 15454 alarms from the Alarms display. The rows of cleared alarms are colored white and have a C in their status (ST) column ( Figure 7-7).
Step 3 To delete card-level alarms:
a. On the node (default login) view, double-click the card graphic for the card you want to open.
b. Click the Alarms tab and then click the Delete Cleared Alarms button, referring to the rules in
Step 5.
Step 4 To delete network-level alarms:
a. On the node (default login) view, click the blue up arrow tool on the toolbar at the top of the CTC window to display the network view.
b. Click the Alarms tab and then click the Delete Cleared Alarms button, referring to the rules in
Step 5.
Step 5 Consult the following rules when deleting cleared alarms from the display:
a. If the Autodelete Cleared Alarms checkbox is checked, an alarm will disappear from the tab when it is cleared.
b. If the Autodelete Cleared Alarms checkbox is not checked, an alarm will remain on the tab when it is cleared as an item that displays white on the tab with the severity Clear (CL). The item can be removed by clicking Delete Cleared Alarms.
c. Transient messages are single message, not raise/clear pairs (i.e. they do not have a companion message). Click Delete Cleared Alarms to remove the transients from the tab.
NTP-69 View Alarm-Affected Circuits
Purpose
|
Use this procedure to view all circuits affected by a past or present alarm or condition.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
None
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve
|
Step 1 Log into the ONS 15454. See the "DLP-60 Log into CTC" task for instructions. If you are already logged in, go to Step 2.
Step 2 In the network, node, or card view, click the Alarms tab and then right-click anywhere on the row of an active alarm.
Note The node view is the default, but you can also navigate to the Alarms tab in the network view and card view to perform Step 2.
Note The card view is not available for the TCC+ or cross-connect cards.
The Select Affected Circuit option appears on the shortcut menu ( Figure 7-8).
Figure 7-8 Selecting the Affected Circuits option
Step 3 Left-click or right-click Select Affected Circuits.
The Circuits pane appears with affected circuits highlighted ( Figure 7-9).
Figure 7-9 Highlighted circuit appears
Step 4 If you want to search for particular circuits, refer to the "DLP-131 Search for Circuits" procedure.
NTP-70 View Alarm Counts on the LCD for a Slot or Port
Purpose
|
Use this procedure to view a statistical count of alarms that have occurred for a slot or port to help in problem identification or elimination.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
None
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve
|
Step 1 Press the Slot button on the LCD panel to toggle to the desired slot number on the ONS 15454.
Step 2 If you want a card-level alarm count, press the Status button.
Step 3 Press the Port button to toggle to a specific port.
Step 4 If you want a port-level alarm count, press the Status button on the LCD panel.
Figure 7-10 shows the LCD panel.
Figure 7-10 The LCD panel
Note A blank LCD results when the fuse on the AIP board is blown. If this occurs, call Cisco TAC at 1-877-323-7368.
Note Use the Slot button to toggle to Node to see a summary of alarms for the entire node.
NTP-71 Create, Download, and Assign Alarm Severity Profiles
Purpose
|
Use this procedure to change the default severity for certain alarms; assign the new severities to a port, card, or node; and delete alarm profiles.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
None
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 Log into a node where you want to create an alarm profile. See the "DLP-60 Log into CTC" task for instructions. If you are already logged in, go to Step 2. Go to Step 2 to clone or modify an alarm profile, or Step 3 to download an alarm profile.
Step 2 Complete the "DLP-115 Create Alarm Severity Profiles" task. This task clones a current alarm profile, renames the profile, and customizes the new profile. Go to Step 4.
Step 3 Complete the "DLP-223 Download an Alarm Severity Profile" procedure. This task downloads an alarm severity profile from a CD or a node.
Step 4 As necessary, complete the "DLP-116 Apply Alarm Profiles to Ports" task or the "DLP-117 Apply Alarm Profiles to Cards and Nodes" task.
DLP-115 Create Alarm Severity Profiles
Purpose
|
Use this task to create custom severity profiles for alarms that differ from the default severity profile.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
DLP-60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 On the node (default login) view, click the blue up arrow tool to display the network view.
Figure 7-11 shows the blue up arrow tool on the node (default login) view.
Figure 7-11 Blue up arrow tool on node (default login) view
Step 2 Click the Provisioning > Alarm Profiles tabs ( Figure 7-12).
Step 3 Click the Load button.
Step 4 In the Select Profile(s) or Filename to Load window, click the From Node radio button.
Step 5 Highlight the node name you are logged into in the Node Names list.
Step 6 Highlight Default in the Profile Names list.
Step 7 Click OK.
The Default alarm severity profile appears in the Alarm Profiles tab pane.
Step 8 Right-click anywhere in the Default profile column to display the profile editing shortcut menu.
Step 9 Choose Clone from the menu.
You can also clone any other profiles that appear under the Available button, except Inherited.
Figure 7-12 Alarm profiles window showing the default profiles of the listed alarms
Step 10 In the Clone Profile dialog box, enter a name in the New Profile Name field.
Profile names must be unique. If you try to import or name a profile that has the same name as another profile, CTC adds a suffix to create a new name. Long file names are supported.
Tip You can also clone alarm profiles shown when you click the Available button in the Provisioning > Alarm Profiles tabs.
Step 11 Click OK.
A new alarm profile (named in Step 10) is created. This profile duplicates the severities of the default profile and is added as a new column on the right side of the Alarm Profiles tab.
Step 12 Modify (customize) the alarm profile:
a. In the new alarm profile column, left-click in a row that contains the alarm severity you want to change.
b. From the pull-down menu, choose the desired severity.
c. Repeat Steps a and b for each alarm that needs to be changed.
Step 13 After you have assigned the properties to the new alarm profile, right-click anywhere in the column of the new alarm profile to highlight it.
Step 14 On the profile editing shortcut menu, choose Store.
Step 15 In the Store Profile(s) dialog box, click the To Node(s) radio button or the To File radio button ( Figure 7-13).
Figure 7-13 Store Profile(s) dialog window
Step 16 If you selected To Node(s), go to Step a. If you selected To File, go to Step b.
a. Choose the login node from the Node Names list, and click one of the following buttons:
–Select All—Selects all node names in the Node Names list. (This will also select all nodes if none are highlighted in the list.)
–Select None—Selects none of the node names in the Node Names list. (This will also select none of the nodes in the list even if they have been highlighted.)
–(Synchronize)—Updates the alarm profile information.
Go to Step c.
b. Click the Browse button to choose a file destination on the workstation.
c. Enter a filename in the name field.
Long file names are supported. CTC supplies a suffix of *.pfl.
d. Click OK.
Step 17 Return to your originating procedure (NTP).
Note Checking the Hide identical rows checkbox configures the Alarm Profiles tab pane to display only the rows of the profile severities that do not match, along with the row's specific alarm type and condition.
Note Checking the Hide values matching profile Default checkbox configures the Alarm Profiles tab pane to display only the severities that do not match the severities of the Default profile.
DLP-223 Download an Alarm Severity Profile
Purpose
|
Use this task to download a custom alarm severity profile from a CD or another node.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
DLP-60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 On the node (default login) view, click the blue up arrow tool to display the network view.
Figure 7-14 shows the blue up arrow tool on the node (default login) view.
Figure 7-14 Blue up arrow tool on node (default login) view
Step 2 Click the Provisioning > Alarm Profiles tabs ( Figure 7-15).
Figure 7-15 Alarm window showing the default profiles of the listed alarms
Step 3 Click Load.
If you want to download a file from the local PC, a CD, or a network drive (if connected), go to Step 4. If you want to download a file from another connected node, go to Step 5.
Step 4 In the Select Profile(s) from Node or Filename to Load window, click the From File radio button.
a. Click the Browse button.
The Open dialog box appears.
b. In the Look in pull-down menu, navigate to the folder on the local PC hard drive, CD, or network (if connected) where the profile file is located.
c. Click the name in the window to highlight it.
The file must have the *.pfl extension.
d. Click the Open button.
e. Go to Step 6.
Step 5 In the Select Profile(s) from Node or Filename to Load window, click the From Node radio button if it is not already selected.
a. Under the Node Names list, click the node you want to download the existing profile from.
b. Under the Profile Names list, click the profile you want to download.
Step 6 In the Select Profile(s) from Node or Filename to Load window, click OK.
The downloaded profile appears on the right side of the Alarm Profiles tab.
Step 7 Right-click anywhere in the downloaded profile column to display the profile editing shortcut menu.
Step 8 Choose Store from the menu.
Step 9 In the Store Profile(s) dialog box, click the To Node(s) radio button ( Figure 7-16).
Figure 7-16 Store Profile(s) dialog window
Step 10 Choose the node where you are logged on from the Node Names list, and click one of the following buttons:
•Select All—Selects all node names in the Node Names list. (This will also select all nodes if none are highlighted in the list.)
•Select None—Selects none of the node names in the Node Names list. (This will also select none of the nodes in the list even if they have been highlighted.)
•(Synchronize)—Synchronizes the stored alarm profile on the selected nodes.
•Click OK.
Step 11 Return to your originating procedure (NTP).
DLP-116 Apply Alarm Profiles to Ports
Purpose
|
Use this task to apply a custom or default alarm severity profile to a port or ports.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
DLP-115 Create Alarm Severity Profiles
DLP-60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 On the node (default login) view, double-click a card to display the card view.
Note You can also apply alarm profiles to cards using the "DLP-117 Apply Alarm Profiles to Cards and Nodes" task.
Note The card view is not available for the TCC+ or cross-connect cards.
Step 2 Click the Provisioning > Alarm Behavior tabs.
Figure 7-17 shows the profile of the affected DS-3 card. CTC shows Parent Card Profile: Inherited.
Go to Step 3 to apply profiles on a port-by-port basis. Go to Step 4 to apply profiles to all ports on a card.
Figure 7-17 Card view of a DS3 alarm profile
Step 3 To apply profiles on a port basis:
a. Click the appropriate row under the Profile column for the port desired.
b. Choose the appropriate profile from the pull-down menu.
c. Click the Apply button.
Step 4 To apply profiles to all ports on a card:
a. Click the Force all ports to profile menu arrow at the bottom of the window.
b. Choose the appropriate profile from the pull-down menu.
c. Click the Force (still need to "Apply") button.
d. Click the Apply button
Step 5 Return to your originating procedure (NTP).
Tip If you choose the wrong profile, click Reset to return to the previous profile setting.
DLP-117 Apply Alarm Profiles to Cards and Nodes
Step 1 On the node (default login) view, click the Provisioning > Alarm Behavior tabs ( Figure 7-18).
To apply profiles on a card basis, go to Step 2. To apply the profile to the entire node, go to Step 3.
Figure 7-18 Node (default login) view of a DS3 alarm profile
Step 2 To apply profiles on a card-by-card basis:
a. Click the Profile row for the card desired.
b. Choose the appropriate profile.
c. Click Apply.
d. Go to Step 4.
Step 3 To apply the profile to an entire node:
a. Click the Node Profile menu arrow.
b. Choose the appropriate Profile.
c. Click Apply.
d. Go to Step 4.
Step 4 Return to your originating procedure (NTP).
Tip If you choose the wrong profile, click Reset to return to the previous profile.
DLP-118 Delete Alarm Severity Profiles
Purpose
|
Use this task to delete a custom or default alarm severity profile.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
DLP-60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provision
|
Step 1 From the node (default login) view, click the blue up arrow tool to display the network view.
Figure 7-19 shows the blue up arrow tool on the node (default login) view.
Figure 7-19 Blue up arrow tool on node (default login) view
Step 2 Click the Provisioning > Alarm Profiles tabs.
Step 3 Click the heading of the profile column you want to delete to highlight the profile column.
Figure 7-20 shows the highlighted profile column.
Figure 7-20 Highlighted Alarm Profile column
Step 4 Click the Delete button.
The Select Node/Profile Combination for Delete dialog window appears ( Figure 7-21).
Figure 7-21 Select Node/Profile Combination for Delete Window
Step 5 Click the node name(s) in the Node Names list to highlight the nodes you want to delete profiles from. Hold down the Shift key to select multiple node names.
Step 6 Click the profile name(s) in the Profile Names list to highlight the profiles you want to delete from the highlighted node names.
Step 7 Click OK.
The Delete Alarm Profile confirmation dialog(s) appear.
Step 8 Click Yes for each Delete Alarm Profile confirmation dialog.
The profiles are now deleted from the nodes selected.
Step 9 If you want to also remove the profile from appearing on the Provisioning > Alarm Profiles tab, right-click the column of the profile you deleted, and choose Remove on the shortcut menu.
Step 10 Return to your originating procedure (NTP).
Note If a combination of node and profile are selected that do not exist a warning appears "One or more of the profile(s) selected do not exist on one or more of the node(s) selected." For example, if node A has only profile 1 and the user tries to delete from node A both profile 1 and profile 2, which exists only on nodes other than node A, this warning will appear. However, the operation still removes profile 1 from node A.
Note Deleting profiles currently in use prompts the user for a confirmation.
Note The special profiles called Default and Inherited may not be deleted and do not appear in the Select Node/Profile Combination for Delete Window.
NTP-168 Enable, Modify, or Disable Alarm Severity Filtering
Purpose
|
Use this procedure to enable, disable, or modify alarm severity filtering for alarms, conditions, or events in all network nodes.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
None
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve
|
Step 1 Log into a node where you want to create an enable alarm severity filtering. See the "DLP-60 Log into CTC" task for instructions. If you are already logged in, go to Step 2.
Step 2 As necessary, complete the "DLP-225 Enable Alarm Filtering" task. This task enables alarm filtering at the card, node, and network views for all nodes in the network. Alarm filtering can be enabled for alarms, conditions, or events.
Step 3 As necessary, complete the "DLP-226 Modify Alarm and Condition Filtering Parameters" procedure. This task modifies the alarm filtering for network nodes to show or hide particular alarms or conditions.
Step 4 As necessary, complete the "DLP-227 Disable Alarm Filtering" task. this task disables alarm profile filtering for all network nodes.
DLP-225 Enable Alarm Filtering
Purpose
|
Use this task to enable alarm filtering for alarms, conditions, or events in all network nodes.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
None
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve
|
Step 1 At the node, network, or card-level view, click the Alarms tab ( Figure 7-22).
Figure 7-22 Node-level view of Alarms tab
.
Step 2 Click the Alarm Filter tool at the lower-right side of the window bottom toolbar.
Alarm filtering is enabled if the tool is selected and disabled if the tool is not selected.
Alarm filtering will be enabled in the card, node, and network views of the Alarms tab at the node and for all other nodes in the network. If, for example, the Alarm Filter tool is enabled in the Alarms tab of the node view at one node, the Alarms tab in the network view and card view of that node will also show the tool enabled. All other nodes in the network will also have the tool enabled.
If you filter an alarm in card view, the alarm will still be displayed in node view. In this view, the card will display the color of the highest-level alarm. The alarm is also shown for the node in the network view.
Step 3 If you want alarm filtering enabled when you view conditions, repeat Steps 1 and 2 using the Conditions tab.
Step 4 If you want alarm filtering enabled when you view alarm history, repeat Steps 1 and 2 using the History tab.
Step 5 Return to your originating procedure (NTP).
DLP-226 Modify Alarm and Condition Filtering Parameters
Purpose
|
Use this task to modify alarm filtering for alarms, conditions, or events in all network nodes.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
DLP-225 Enable Alarm Filtering
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve
|
Step 1 At the node, network, or card-level view, click the Alarms tab ( Figure 7-23).
Figure 7-23 Node-level view of Alarms tab
.
Step 2 Click the Alarm Filter tool at the lower-left side of the window bottom toolbar.
The Alarm Filter Dialog window appears, showing the General tab ( Figure 7-24).
Figure 7-24 Alarm Filter Dialog window, General tab
In the General tab Show Severity area, you can modify which alarm severities show through the alarm filter or the period of time to apply to the alarms. If you want to change the alarm severities shown in the filter, go to Step a. In the Time area, you can choose a time period that alarms are displayed for. If you want to change the time period that the alarms show for, go to Step b.
a. In the Show Severity area, click the checkboxes for critical (CR), major (MJ), minor (MN), or not alarmed (NA) to determine which alarms will bypass the alarm filter when it is enabled. Leave severity checkboxes empty to filter the alarms.
When alarm filtering is disabled, all alarms show.
b. In the Time area, click the Show alarms between time limits checkbox to enable it. Then click the up and down arrows in the From Date, To Date, and Time fields to modify what period of alarms will be shown.
Step 3 To modify filter parameters for conditions, proceed to Step 4. If not, proceed to Step 5.
Step 4 Click the Conditions tab ( Figure 7-25).
Figure 7-25 Alarm Filter Dialog window, Conditions tab
Conditions in the Show list are visible when alarm filtering is enabled. Conditions in the Hide list are invisible when alarm filtering is enabled. To move conditions individually from the Show list to the Hide list, click the > button. To move conditions individually from the Hide list to the Show list, click the
< button. To move conditions collectively from the Show list to the Hide list, click the >> button. To move conditions collectively from the Hide list to the Show list, click the << button.
Note Conditions include alarms.
Step 5 Click Apply and OK.
Filter parameters for alarms and conditions are enforced when alarm filtering is enabled, and not enforced when alarm filtering is disabled.
Step 6 Return to your originating procedure (NTP).
DLP-227 Disable Alarm Filtering
Purpose
|
Use this task to disable alarm filtering for alarms, conditions, or events in all network nodes.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
DLP-225 Enable Alarm Filtering
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Retrieve
|
Step 1 At the node, network, or card-level view, click the Alarms tab ( Figure 7-26).
Figure 7-26 Node-level view of Alarms tab
.
Step 2 Click the Alarm Filter tool at the lower-right side of the window bottom toolbar.
Alarm filtering is enabled if the tool is selected, and disabled if the tool is not selected.
Step 3 If you want alarm filtering disabled when you view conditions, repeat Steps 1 and 2 using the Conditions tab.
Step 4 If you want alarm filtering disabled when you view alarm history, repeat Steps 1 and 2 using the History tab.
Step 5 Return to your originating procedure (NTP).
NTP-72 Suppress and Unsuppress Alarm Reporting
Purpose
|
Use this procedure to suppress reported alarms at the port, card, or node level and disable the suppress command to resume normal alarm reporting.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
None
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning
|
Step 1 Log into the ONS 15454. See the "DLP-60 Log into CTC" task for instructions. If you are already logged in, go to Step 2.
Step 2 Complete the "DLP-119 Suppress Alarm Reporting" task to provision the node to send out autonomous messages to clear any raised alarms.
Note Suppressing alarms prevents alarms from appearing on Alarm or History tabs or in any other clients. The suppressed alarms behave like events, which have their own NA severities, and appear on the Conditions tab. The suppressed alarms appear with their alarm severity, color code, and service-affecting status.
Step 3 Complete the "DLP-120 Unsuppress Alarm Reporting" task to remove the suppress-alarms command and provision the node to send out autonomous messages to raise any actively suppressed alarms.
DLP-119 Suppress Alarm Reporting
Purpose
|
Use this task to suppress the reporting of ONS 15454 alarms at the port, card, or node level.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
DLP-60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning
|
Step 1 At either the node (default) or card view, click the Provisioning > Alarm Behavior tabs.
At the card level, you can suppress alarms on a port-by-port basis. At the node level, you can suppress alarms on a card basis or on the entire node.
Step 2 Click the Suppress Alarms checkbox for the card (at the default login node view) or ports (at the card view) you want to suppress ( Figure 7-27).
On the node (default login) view, row numbers correspond to slot numbers.
Figure 7-27 The Suppress Alarms checkbox
Step 3 Click the Apply button.
The node sends out autonomous messages to clear any raised alarms.
Step 4 Return to your originating procedure (NTP).
Caution If multiple CTC/TL1 sessions are open, suppressing alarms in one session will suppress the alarms in all other open sessions.
DLP-120 Unsuppress Alarm Reporting
Purpose
|
Use this task to discontinue alarm suppression and reenable alarm reporting on a port, card, or node.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
DLP-119 Suppress Alarm Reporting
DLP-60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning
|
Step 1 At either the node (default) or card view, depending on where the alarms were suppressed, click the Provisioning > Alarm Behavior tabs.
Step 2 In card view, deselect the Suppress Alarms checkbox for the cards or ports you no longer want to suppress. In node (default login) view, deselect the Suppress Alarms checkbox next to the Node Profile field.
Step 3 Click the Apply button. The node sends out autonomous messages to raise any actively suppressed alarms.
Step 4 Return to your originating procedure (NTP).
