primeaccess.att.com€¦ · web viewit uses color-coded alarm levels to reveal the condition of...

CNM for SONET/MON User Guide

Customer Network Management (CNM) for SONET/MON

User Guide

Version 1.0

This is a confidential, unpublished property of AT&T Operations, Inc. Receipt or possession of this document does not convey any rights to divulge, reproduce, use, or allow others to use it without the specific written authorization of AT&T Knowledge Ventures, L.P. Use must conform strictly to the license agreement between the user and AT&T Operations, Inc.

2003 AT&T Knowledge Ventures, L.P.All Rights Reserved.

This copyright notice should not be construed as evidence of publication.


CNM for SONET/MONUser Guide

TABLE OF CONTENTS1 ABOUT CUSTOMER NETWORK MANAGEMENT (CNM) FOR SONET/MON.....................1

1.1 WHAT IS CNM FOR SONET/MON?...........................................................................11.2 WHAT IS SONET AND MON....................................................................................21.3 UNDERSTANDING ON-SCREEN COLORS.......................................................................21.4 WHAT IS “PULL TECHNOLOGY”?................................................................................3

2 LOGGING ON TO CNM FOR SONET/MON AND SECURITY MANAGEMENT......42.1 HOME PAGE..........................................................................................................42.2 EXISTING USER LOGIN TO THE CNM FOR SONET/MON................................................52.3 NEW USER LOGIN TO CNM FOR SONET/MON WEB APPLICATION...................................62.4 SECURITY MANAGEMENT..........................................................................................7

2.4.1 PASSWORD PROTECTION AND SECURITY...............................................................7


2.4.2 ACCESSING SECURITY MANAGEMENT....................................................................72.4.3 PASSWORD AND SESSION CONTROL FEATURES IN THE CNM FOR SONET/MON WEB

APPLICATION...................................................................................................72.4.4 PASSWORD CHANGE.........................................................................................8

3 CONFIGURATION MANAGEMENT..............................................................93.1 HOW CONFIGURATION MANAGEMENT IS USED..............................................................93.2 ACCESSING CONFIGURATION MANAGEMENT..................................................................93.3 NETWORK MAP......................................................................................................9

3.3.1 ACCESSING THE NETWORK MAP..........................................................................93.3.2 USING THE NETWORK MAP................................................................................9

3.4 MON DETAILS........................................................................................................93.4.1 ACCESSING THE MON DETAILS...........................................................................93.4.2 USING THE MON DETAILS.................................................................................9

3.5 RING MAP.............................................................................................................93.5.1 ACCESSING THE RING MAP................................................................................93.5.1 USING THE RING MAP.......................................................................................9

3.6 CIRCUIT MAP.........................................................................................................93.6.1 ACCESSING THE CIRCUIT MAP.............................................................................93.6.2 USING THE CIRCUIT MAP...................................................................................9

3.7 CIRCUIT FILTER......................................................................................................93.7.1 ACCESSING THE CIRCUIT FILTER..........................................................................93.7.2 USING THE CIRCUIT FILTER................................................................................9

3.8 SINGLE CIRCUIT INFORMATION MAINTENANCE...............................................................93.8.1 ACCESSING THE SINGLE CIRCUIT INFORMATION MAINTENANCE..................................93.8.2 USING THE SINGLE CIRCUIT INFORMATION MAINTENANCE.........................................9

3.9 MULTIPLE CIRCUIT INFORMATION MAINTENANCE............................................................93.9.1 ACCESSING THE MULTIPLE CIRCUIT INFORMATION MAINTENANCE...............................93.9.2 USING THE MULTIPLE CIRCUIT INFORMATION MAINTENANCE......................................9

3.10 UPDATE RING ALIAS..............................................................................................93.10.1 ACCESSING THE UPDATE RING ALIAS.................................................................93.10.2 USING THE UPDATE RING ALIAS........................................................................9

3.11 SONET NODE DETAILS REPORT..............................................................................93.11.1 SONET NODE DETAILS REPORT.......................................................................93.11.2 USING THE SONET NODE DETAILS REPORT........................................................9

3.12 MON NODE DETAILS REPORT.................................................................................93.12.1 ACCESSING THE MON NODE DETAILS REPORT....................................................93.12.2 USING THE MON NODE DETAILS REPORT...........................................................9

3.13 SONET CIRCUIT DETAILS REPORT...........................................................................93.13.1 ACCESSING THE SONET CIRCUIT DETAILS REPORT..............................................93.13.2 USING THE SONET CIRCUIT DETAILS REPORT.....................................................9

3.14 SONET OVER MON CIRCUIT DETAILS REPORT...........................................................93.14.1 ACCESSING THE SONET OVER MON CIRCUIT DETAILS REPORT..............................93.14.2 USING THE SONET OVER MON CIRCUIT DETAILS REPORT....................................9

3.15 LAMBDA DETAILS REPORT......................................................................................93.15.1 ACCESSING THE LAMBDA DETAILS REPORT..........................................................93.15.2 USING THE LAMBDA DETAILS REPORT................................................................9

4 FAULT MANAGEMENT.............................................................................94.1 ACCESSING FAULT MANAGEMENT...............................................................................94.2 NETWORK OUTAGES................................................................................................9

4.2.1 ACCESSING NETWORK OUTAGES.........................................................................94.2.2 USING NETWORK OUTAGES...............................................................................9

4.3 MON OUTAGES......................................................................................................9


4.3.1 ACCESSING MON OUTAGES...............................................................................94.3.2 USING MON OUTAGES.....................................................................................9

4.4 RING OUTAGES......................................................................................................94.4.1 ACCESSING RING OUTAGES................................................................................94.4.2 USING RING OUTAGES......................................................................................9

4.5 CIRCUIT OUTAGES...................................................................................................94.5.1 ACCESSING CIRCUIT OUTAGES............................................................................94.5.2 USING CIRCUIT OUTAGES..................................................................................9

4.6 ALARM AND EVENT HISTORY.....................................................................................94.6.1 ACCESSING ALARM AND EVENT HISTORY.............................................................94.6.2 USING ALARM AND EVENT HISTORY.....................................................................9

4.7 DETECTION SETTINGS..............................................................................................94.7.1 ACCESSING DETECTION SETTINGS.......................................................................94.7.2 USING DETECTION SETTINGS..............................................................................9

4.8 DETECTION STATUS.................................................................................................94.8.1 ACCESSING DETECTION STATUS..........................................................................94.8.2 USING DETECTION STATUS................................................................................94.8.3 ALARM WINDOW..............................................................................................9

4.9 NOTIFICATION SETTINGS...........................................................................................94.9.1 ACCESSING NOTIFICATION SETTINGS....................................................................94.9.2 USING NOTIFICATION SETTINGS..........................................................................9

5 PERFORMANCE MANAGEMENT................................................................95.1 ACCESSING PERFORMANCE MANAGEMENT....................................................................95.2 HOW PERFORMANCE MANAGEMENT IS USED................................................................9

5.2.1 TERMINOLOGY USED IN CNM PERFORMANCE MANAGEMENT.....................................95.3 CIRCUIT PERFORMANCE TABLE – NETWORK LEVEL.........................................................9

5.3.1 ACCESSING THE CIRCUIT PERFORMANCE TABLE – NETWORK LEVEL:...........................95.3.2 USING THE CIRCUIT PERFORMANCE TABLE – NETWORK LEVEL:.................................9

5.4 CIRCUIT PERFORMANCE TABLE – SONET OVER MON LEVEL...........................................95.4.1 ACCESSING THE CIRCUIT PERFORMANCE TABLE – SONET OVER MON LEVEL :............95.4.2 USING THE CIRCUIT PERFORMANCE TABLE – SONET OVER MON LEVEL :...................9

5.5 CIRCUIT PERFORMANCE TABLE – SONET RING LEVEL....................................................95.5.1 ACCESSING THE CIRCUIT PERFORMANCE TABLE – SONET RING LEVEL:......................95.5.2 USING THE CIRCUIT PERFORMANCE TABLE – SONET RING LEVEL:............................9

5.6 CIRCUIT PERFORMANCE TABLE – CIRCUIT LEVEL...........................................................95.6.1 ACCESSING THE CIRCUIT PERFORMANCE TABLE – CIRCUIT LEVEL:..............................95.6.2 USING THE CIRCUIT PERFORMANCE TABLE– CIRCUIT LEVEL:.....................................9

5.7 LINE / PATH - NEAR END AND FAR END CURRENT PERFORMANCE STATS...........................95.7.1 ACCESSING THE LINE / PATH - NEAR END AND FAR END CURRENT PERFORMANCE

STATS:..........................................................................................................95.7.2 USING THE LINE / PATH - NEAR END AND FAR END CURRENT PERFORMANCE STATS:....9

5.8 LINE / PATH - NEAR END AND FAR END INTERVAL PERFORMANCE STATS...........................95.8.1 ACCESSING THE LINE / PATH - NEAR END AND FAR END INTERVAL PERFORMANCE

STATS:..........................................................................................................95.8.2 LINE / PATH - NEAR END AND FAR END INTERVAL PERFORMANCE STATS:...................9

5.9 SECTION INTERVAL REPORT......................................................................................95.9.1 ACCESSING THE SECTION INTERVAL REPORT:.........................................................95.9.2 USING THE SECTION INTERVAL REPORT:...............................................................9

5.10 SECTION CURRENT GRAPH......................................................................................95.10.1 ACCESSING THE SECTION CURRENT GRAPH:........................................................95.10.2 USING THE SECTION CURRENT GRAPH:..............................................................9

5.11 CIRCUIT HOURLY LINE GRAPH.................................................................................95.11.1 ACCESSING THE CIRCUIT HOURLY LINE GRAPH:....................................................9


5.11.2 USING CIRCUIT HOURLY LINE GRAPH:................................................................95.12 CIRCUIT DAILY GRAPH...........................................................................................9

5.12.1 ACCESSING THE CIRCUIT DAILY GRAPH:.............................................................95.12.2 USING THE CIRCUIT DAILY GRAPH:....................................................................9

5.13 LINE / PATH - WEEKLY TREND GRAPH......................................................................95.13.1 ACCESSING THE CIRCUIT WEEKLY TREND GRAPH:................................................95.13.2 USING THE CIRCUIT WEEKLY TREND GRAPH:.......................................................9

5.14 DOWNLOADING DATA IN PERFORMANCE MANAGEMENT................................................95.15 CIRCUIT REPORTS.................................................................................................9

5.15.1 ACCESSING CIRCUIT REPORTS..........................................................................95.15.2 USING CIRCUIT REPORTS.................................................................................9

6 THE TOOLBAR........................................................................................96.1 CNM HOME PAGE TOOLBAR FUNCTIONS.....................................................................96.2 CNM FOR SONET/MON APPLICATION TOOLBAR FUNCTIONS..........................................9

7 IF YOU HAVE MORE QUESTIONS..............................................................98 SONET/MON DEFINITIONS AND ACRONYMS.............................................9

8.1 SONET/MON DEFINITIONS......................................................................................98.2 SONET DEFINITIONS...............................................................................................98.3 MON DEFINITIONS..................................................................................................98.4 PERFORMANCE PARAMETERS DEFINITIONS....................................................................98.5 ACRONYMS COMMON TO TECHNOLOGY AND EQUIPMENT FOR AT&T SONET/MON..............9

9 SONET/MON References............................................................................................9



LIST OF FIGURES

FIGURE 2-1: HOME PAGE..................................................................................................4FIGURE 2-2: EXISTING USERS’ LOGIN...................................................................................5FIGURE 2-3: VALIDATING USER ID AND PASSWORD................................................................6FIGURE 2-4: CHANGE PASSWORD SCREEN............................................................................9FIGURE 3-1: CONFIGURATION MANAGEMENT ACCESS VIA THE TOOLBAR......................................9FIGURE 3-2: NETWORK MAP..............................................................................................9FIGURE 3-3: MON DETAILS...............................................................................................9FIGURE 3-4: RING MAP.....................................................................................................9FIGURE 3-5: CIRCUIT MAP.................................................................................................9FIGURE 3-6: CIRCUIT FILTER FROM CIRCUIT MAP....................................................................9FIGURE 3-7: CIRCUIT FILTER FROM CIRCUIT OUTAGES.............................................................9FIGURE 3-8: CIRCUIT MAP FILTERS......................................................................................9FIGURE 3-9: SINGLE CIRCUIT INFORMATION MAINTENANCE.......................................................9FIGURE 3-10: MULTIPLE CIRCUIT INFORMATION MAINTENANCE..................................................9FIGURE 3-11: UPDATE RING ALIAS......................................................................................9FIGURE 3-12: NODE DETAILS REPORT.................................................................................9FIGURE 3-13: MON NODE DETAILS REPORT.........................................................................9FIGURE 3-14: SONET CIRCUIT DETAILS REPORT...................................................................9FIGURE 3-15: MON CIRCUIT DETAILS REPORT......................................................................9FIGURE 3-16: LAMBDA DETAILS REPORT..............................................................................9FIGURE 4-1: ACCESSING FAULT MANAGEMENT.......................................................................9FIGURE 4-2: NETWORK OUTAGES........................................................................................9FIGURE 4-3: NETWORK OUTAGES – HEALTHY NETWORK.........................................................9FIGURE 4-4: MON OUTAGES.............................................................................................9FIGURE 4-5: MON OUTAGES – HEALTHY MON.....................................................................9FIGURE 4-6: RING OUTAGES..............................................................................................9FIGURE 4-7: RING OUTAGES – HEALTHY RING.......................................................................9FIGURE 4-8: CIRCUIT OUTAGES..........................................................................................9FIGURE 4-9: CIRCUIT OUTAGES – HEALTHY CIRCUITS..............................................................9FIGURE 4-10: CIRCUIT OUTAGES – FILTERED WITH NO CIRCUITS...............................................9FIGURE 4-11: ALARM AND EVENT HISTORY...........................................................................9FIGURE 4-12: DETECTION SETTINGS....................................................................................9FIGURE 4-13: DETECTION STATUS.......................................................................................9FIGURE 4-14: ALARM WINDOW – NO ACKNOWLEDGEMENT......................................................9FIGURE 4-15: ALARM WINDOW – ACKNOWLEDGED.................................................................9FIGURE 4-16: NOTIFICATION SETTINGS.................................................................................9FIGURE 5-1: PERFORMANCE MANAGEMENT ACCESS VIA THE TOOLBAR........................................9FIGURE 5-2: CIRCUIT PERFORMANCE TABLE – NETWORK LEVEL.................................................9FIGURE 5-3: CIRCUIT PERFORMANCE TABLE – SONET OVER MON............................................9FIGURE 5-4: CIRCUIT PERFORMANCE TABLE – SONET RING LEVEL...........................................9FIGURE 5-5: CIRCUIT PERFORMANCE TABLE – CIRCUIT LEVEL...................................................9FIGURE 5-6: PATH CURRENT GRAPH....................................................................................9FIGURE 5-7: PATH NEAR END INTERVAL REPORT....................................................................9FIGURE 5-8: SECTION INTERVAL REPORT..............................................................................9FIGURE 5-9: SECTION CURRENT GRAPH...............................................................................9FIGURE 5-10: CIRCUIT HOURLY LINE GRAPH.........................................................................9


FIGURE 5-11: CIRCUIT DAILY GRAPH...................................................................................9FIGURE 5-12: CIRCUIT WEEKLY TREND GRAPH......................................................................9FIGURE 5-13: DOWNLOAD OPTION......................................................................................9FIGURE 5-14: RAW DATA FROM A HOURLY LINE GRAPH..........................................................9FIGURE 5-15: CIRCUIT REPORTS.........................................................................................9FIGURE 6-1: CNM APPLICATION HOME PAGE TOOLBAR...........................................................9FIGURE 6-2: BROWSER SETTINGS........................................................................................9FIGURE 6-3: CONTACT US (UNSECURED)..............................................................................9FIGURE 6-4: TOOLBAR FOR CNM SONET/MON APPLICATION..................................................9FIGURE 6-5: SITE MAP SCREEN..........................................................................................9FIGURE 6-6: CONTACT US (SECURED).................................................................................9Figure 6-7: User Guide.................................................................................................9



LIST OF TABLESTABLE 1-1: UNDERSTANDING ON-SCREEN COLORS.................................................................3TABLE 2-1: ELEMENTS OF CHANGE PASSWORD SCREEN..........................................................9TABLE 3-1: ELEMENTS OF NETWORK MAP.............................................................................9TABLE 3-2: ELEMENTS OF MON DETAILS.............................................................................9TABLE 3-3: ELEMENTS OF RING MAP...................................................................................9TABLE 3-4: ELEMENTS OF CIRCUIT MAP...............................................................................9TABLE 3-5: ELEMENTS OF CIRCUIT FILTER.............................................................................9TABLE 3-6: ELEMENTS OF SINGLE CIRCUIT INFORMATION MAINTENANCE.....................................9TABLE 3-7: ELEMENTS OF MULTIPLE CIRCUIT INFORMATION MAINTENANCE..................................9TABLE 3-8: ELEMENTS OF UPDATE RING ALIAS......................................................................9TABLE 4-1: FAULT MANAGEMENT OPTIONS DESCRIPTION.........................................................9TABLE 4-2: ELEMENTS OF NETWORK OUTAGES......................................................................9TABLE 4-3: ELEMENTS OF MON OUTAGES............................................................................9TABLE 4-4: ELEMENTS OF RING OUTAGES.............................................................................9TABLE 4-5: ELEMENTS OF CIRCUIT OUTAGES.........................................................................9TABLE 4-6: ELEMENTS OF ALARM AND EVENT HISTORY...........................................................9TABLE 4-7: ELEMENTS OF DETECTION SETTINGS....................................................................9TABLE 4-8: ELEMENTS OF DETECTION STATUS.......................................................................9TABLE 4-9: ELEMENTS OF ALARM WINDOW...........................................................................9TABLE 4-10: ELEMENTS OF NOTIFICATION SETTING................................................................9TABLE 5-1: PERFORMANCE TERMS.......................................................................................9TABLE 5-2: ELEMENTS OF CIRCUIT PERFORMANCE TABLE – NETWORK LEVEL...............................9TABLE 5-3: CIRCUIT PERFORMANCE REPORTS........................................................................9TABLE 5-4: CIRCUIT PERFORMANCE GRAPHS.........................................................................9TABLE 5-5: ELEMENTS OF CIRCUIT PERFORMANCE TABLE – SONET OVER MON..........................9TABLE 5-6: ELEMENTS OF CIRCUIT PERFORMANCE TABLE – SONET RING LEVEL..........................9TABLE 5-7: ELEMENTS OF CIRCUIT PERFORMANCE TABLE – CIRCUIT LEVEL..................................9TABLE 5-8: ELEMENTS OF PATH CURRENT GRAPH..................................................................9TABLE 5-9: ELEMENTS OF LINE / PATH - NEAR END AND FAR END INTERVAL PERFORMANCE REPORT

.............................................................................................................................9TABLE 5-10: ELEMENTS OF SECTION INTERVAL REPORT..........................................................9TABLE 5-11: ELEMENTS OF SECTION CURRENT GRAPH............................................................9TABLE 5-12: ELEMENTS OF CIRCUIT HOURLY LINE GRAPH.......................................................9TABLE 5-13: ELEMENTS OF CIRCUIT DAILY GRAPH.................................................................9TABLE 5-14: ELEMENTS OF WEEKLY TREND GRAPH................................................................9TABLE 5-15: ELEMENTS OF CIRCUIT REPORTS.......................................................................9TABLE 6-1: ELEMENTS OF CNM APPLICATION TOOLBAR..........................................................9TABLE 6-2: ELEMENTS OF TOOLBAR FOR CNM SONET/MON APPLICATION................................9TABLE 8-1: SONET/MON DEFINITIONS...............................................................................9TABLE 8-2: SONET DEFINITIONS........................................................................................9TABLE 8-3: MON DEFINITIONS...........................................................................................9TABLE 8-4: MON DEFINITIONS...........................................................................................9Table 8-5: Acronyms for SONET/MON...........................................................................9


1 About Customer Network Management (CNM) for SONET/MON

1.1 What is CNM for SONET/MON?The Customer Network Management (CNM) Application – enables SONET/MON customers to proactively monitor their SONET and MON services in order to maximize their Network operational efficiency. CNM for SONET/MON provides four ways to manage the customer’s network.

Performance Management – helps customers better understand the performance of traffic on the network by displaying trend analysis and performance data in a meaningful graphical depiction.

Fault Management – helps customers to monitor the network by providing them with notification of alarms that may occur in their network.

Configuration Management – helps customers track the various elements of the network, such as ring, node, lambda, and circuits.

Security Management – provides customers with their own network view and authentication functionality to restrict access to authorized individuals with password and session controls.

CNM for SONET/MON as well as the underlying SONET and MON service is provided by the AT&T Local Exchange Companies: AT&T California, AT&T Nevada, AT&T Arkansas, AT&T Kansas, AT&T Missouri, AT&T Oklahoma, AT&T Texas, AT&T Illinois, AT&T Indiana, AT&T Michigan, AT&T Ohio, AT&T Wisconsin, and AT&T Connecticut.


1.2 What is SONET and MON

SONET (Synchronous Optical Network) is a standard for fiber-based optical transport. SONET defines optical carrier levels (OCn) and electrically equivalent synchronous transport signals (STS) within an industry standard. A SONET network can be configured in a ring or linear point-to-point topology. SONET/MON CNM is available to AT&T customers with the following SONET-based services:

Dedicated SONET Ring Service (DSRS) SONET Ring and Access Service (SRAS) Self-Healing Transport Service (STN)

Dense Wavelength Division Multiplexing (DWDM) is a technology that transmits multiple data signals over the same fiber-optic cable simultaneously using different wavelengths of light in order to increase the amount of information that can be transferred. DWDM can be configured in a ring or linear point-to-point topology. SONET/MON CNM is available to AT&T customers with the following MON-based services:

Multi-Service Optical Network (MON) Ring Service

1.3 Understanding On-Screen Colors

The on-screen colors will display the customer’s network information using an informative range of colors to indicate the statuses. Table 1-1 explains the color codes used in CNM for SONET/MON Web Application and their meaning. No colors will be used for customers that subscribe only to the Data Feed service.

Service Color State Of Network ElementWeb Green The Network is healthy. There are no

fault events. Red Critical - An anomaly that affects traffic

and requires immediate attentionAmber Major - An anomaly that may affect

traffic if it does not receive immediate attention.

22- 2 -


Service Color State Of Network ElementYellow Minor – A secondary indicator of another

alarm or a condition that may not affect traffic. (May not be reported to the customer.)

Table 1-1: Understanding On-Screen Colors

1.4 What Is “Pull Technology”?

The functions and features of the CNM for SONET/MON Web Application are based on what is called “pull” technology. When an event/alarm occurs on a customer’s network, they will not be aware of it until they pull the data to their desktop. Customers will be aware of it only by fault notification. Fault notification is done by email and/or pager as well as on the customer’s web page. To determine the current state of the network, customers will need to click on their browser’s “Reload” button – or click on “Refresh” for Internet Explorer – to collect the most recent data and present it on the web page. Therefore, customers are “pulling” the data to their screen from the network via their browsers – which gives them maximum control over the events that occur on their screens.

33- 3 -


2 Logging On To CNM for SONET/MON and Security Management

2.1 Home PageThis User Guide will provide customers an easy “road map” to navigate the CNM for SONET/MON Web Application.

To logon to CNM for SONET/MON, enter the URL address – www.fastrakview.com – this will invoke the Home Page. Then click on the “SONET/MON” link, below “User Login”, as shown in Figure 2-1. The next step is to log in and authenticate.

Figure 2-1: Home Page

Note: Below the toolbar (blue field on left hand side) on the Home page, and most subsequent pages, there will be a link (not shown above) that will connect the user to a corporate page that discusses copyright and privacy policy information. Also, at the top left of each web page, except pop-up windows, there will be a company logo. The web pages that are secure (after successful login) will also show the AT&T Local Exchange Companies. These items have been omitted from this document because they add almost nothing toward

44- 4 -

SONET/MON customers sign on

Bulletin Message will appear here


understanding the CNM service, and because they are subject to periodic change.

2.2 Existing User Login to the CNM for SONET/MON

Once “SONET/MON” has been selected, customers will invoke the “Authentication” screen as shown in Figure 2-2.

Figure 2-2: Existing Users’ Login

Enter “User ID” and “Password” and click on the “LOGIN” button. As the password is entered, it will appear as a series of asterisks (******) for security purposes (i.e., to prevent others from seeing it while entering).

After a successful authentication, the user will be presented with the “Network Map” screen as shown in Figure 3-6.

If the entered “User ID” and “Password” combination is invalid, it will result in a failed authentication and invoke the “Authentication” screen as shown in Figure 2-3. The user will be prompted to re-enter “User ID” and “Password” again.

If an invalid “User ID” and “Password” combination is entered 6 times in succession, the “User ID” will be disabled for 3 minutes. No special

55- 5 -

Enter your “User ID” and “Password”

Click on the “LOGIN” button


message will be displayed. This feature is intended to prevent unauthorized users from guessing the valid password.

Figure 2-3: Validating User ID and Password

If the password has expired (more than 90 days old), the user will see the “Change Password” screen, which is described in Security Management under section 2.4.4

2.3 New User Login to CNM for SONET/MON Web Application

New users of CNM for SONET/MON Web Application will also see the “Authentication” screen with “User ID” and “Password” prompts as shown in Figure 2-2.

The user should enter the “User ID” and the initial “Password”, which has been provided, and should click on the “LOGIN” button. If the entered “User ID” and “Password” combination is valid, then the “Change Password” screen is presented, which is described in Security Management under section 2.4.4.

If the entered “User ID” and “Password” combination is invalid, it will result in a failed authentication and invoke the “Authentication” screen as shown in Figure 2-3 The user will be prompted to re-enter the “User ID” and “Password” again.

66- 6 -

Re-enter your “User ID” and “Password” and click on the “LOGIN” button.


2.4 Security Management 2.4.1 Password Protection and Security

Security Management provides customers with authentication, password, and session control features. New and existing users can update and maintain their password in the CNM for SONET/MON Web Application.

AT&T Operations, Inc. is taking all reasonable and appropriate measures, including encryption, to ensure that customer’s corporate information is disclosed only to them.

In order for the Internet communications to remain confidential, customers must use a Web browser, which supports the Secure Sockets Layer (SSL) security protocol. Many popular Web browsers already support SSL.

2.4.2 Accessing Security Management

Customers can access Security Management by:

Click on the “Security Management” link on the toolbar Click on the “Change Password” link from the “Site Map” screen.

2.4.3 Password and Session Control Features in the CNM for SONET/MON Web Application

To ensure effective access control and data security, CNM for SONET/MON provides customers with password and session control functionality. Password Control

Password control includes stringent password specifications, password aging, password expiration and password inactivity.

05/18/23 77- 7 -


05/18/23 88- 8 -


The password chosen must meet the following specifications:

Must be 6 to 10 characters long. Must not start or end with a digit. Must not use User ID, or reverse of User ID Must contain at least one digit. Must not be the same as previous six passwords.

With the password-aging and expiration feature, a password expires after 90 days. When users log in and authenticate, if the password is older than 90 days, users will be prompted to change the password. Users do not need to wait until 90 days has elapsed before changing the password. For example, if an unauthorized person has gained use of the password, it should be changed immediately.

With the password inactivity feature, a user will be blocked from logging in if the User ID and password have not been used for 90 days. A message will be displayed instructing the user to contact the Helpdesk to have the password reset.

Session Control

With the session control feature, when a user’s session has been idle for the last 60 minutes, the user will automatically be logged out of the application.

2.4.4 Password Change

Users are presented with the “Change Password” screen, and prompted to change their password during any of the following conditions:

If the user has logged into the CNM for SONET/MON Web Application for the first time after initializing the password in the “Authentication” screen.

If the current password has expired (password is older than 90 days). If the user has clicked on the “Security Management” link in the toolbar or

the “Change Password” link in Site Map.

99- 9 -


Figure 2-4: Change Password Screen

Item Description1 In the “Current Password” field, enter your initial (current) password.2 In the “New Password” field, enter a password of your own choosing

based on the password specifications provided on the screen.

In the “Re-enter new password for confirmation” field, re-enter the “New Password”. This new password remains valid for a total of 90 days.

3 Click on the “SUBMIT CHANGES” button to apply the change.Table 2-2: Elements of Change Password Screen

If the new password entered does not conform to the password guidelines provided on the screen, the user will receive an error message. Verify and re-enter the password that conforms to the password specifications provided on the screen to change the password.

10- 10 -10-

10 -- 10 -

1

2

3


3 Configuration Management3.1 How Configuration Management Is Used

The purpose of Configuration Management is to assist AT&T Customers in managing and tracking the various elements of the network, Customers can manage the Inventory of their Network, Ring, Node and Circuit information. It enables users to have a top down view of their network starting from a Network Map all the way to the Circuit Map.

Specifically, using Configuration Management, customers can:

Track network resources: Determine circuit origination and termination endpoints (locations)

Determine the provisioned parameters of the network: View the subscribed Ring. Obtain Network, Lambda, Node and Circuit information to aid in

communicating with the Customer Support Center. Current release of CNM does not offer SDS or VT Layer statistics.

Maintain the Circuit(s) Information: Provides features for maintaining and updating the contact person,

circuit alias, contact address, contact telephone number, and/or contact e-mail address for a circuit(s)

Note: The circuit IDs shown throughout this User Guide are meant for illustrative purposes only. The actual format for a circuit that a user would see would follow the naming conventions of the circuit provider. For example: 12/HFQS/123456-001/PT, 34/LUXX/000012-001/SW, etc. Additionally, each figure shown in this guide is meant as a stand alone item, often created to illustrate the functionality of the CNM service. No attempt has been made to correlate the contents of one figure to another.

11- 11 -11-

11 -- 11 -


3.2 Accessing Configuration ManagementUsers can access Configuration Management by clicking on the “Configuration Management” link on the toolbar (as shown in Figure 3-5), or from the Home Page after a successful login.

Figure 3-5: Configuration Management Access via the Toolbar

The explanation of data elements of each field (illustrated figures and screen shots) is given in associated Tables. Further details of each field and SONET/MON terminology is given at the end of the document.

12- 12 -12-

12 -- 12 -

Click on “Configuration Management”.


3.3 Network Map

3.3.1 Accessing the Network Map Click on “SONET/MON“ under “User Login” in the toolbar. It is the default

page after login. Click on “Configuration Management” from the toolbar, which is accessible

from most pages.

3.3.2 Using the Network MapThe network map displays all the SONET and MON rings belonging to the CNM user.

Figure 3-6: Network Map

13- 13 -13-

13 -- 13 -

21

34

6 7

8

9

10

11 12 13 14 15


Item

Description

1 SONET/MON subscriber’s userid.2 Customer’s business name and location. Location consists of street

number and name, city, and state.3 Clicking on the "Up Arrow" or the "Down Arrow" links retrieves and

provides views for additional networks. The default presentation is 30 networks per page. Clicking on the "Up Arrow" link will display the previous set of networks; Clicking on the "Down Arrow" link will display the next set of networks. These links are also available at the bottom of this page if there is more than one page. If the user is viewing the first set of networks, the "Up Arrow" link will be disabled; If the user is viewing the last set of networks, then the "Down Arrow" link will be disabled. And if all the networks can be shown in one page, both links will be disabled

4 Start and end count of networks displayed in the page and the total number of networks.

5 If there are more than 60 networks to be displayed, a dropdown box is displayed which allows the user to select the range of networks to view (in 30 network increments). This dropdown box will also be available at the bottom of this page.

Select next range of circuits to view

6 Clicking on the "Up Arrow" sorts the list of networks by ascending Network ID. This is the default sorting order.

7 Clicking on the "Down Arrow" sorts the list of networks by descending Network ID.

8 Network ID = a unique identifier for a group of Rings. 9 Ring ID.

SCID signifies SONET Ring (system generated SONET Ring ID) DWID identifies MON Ring (system generated MON Ring ID) All Ring IDs are clickable If the service type for this ring is SONET, clicking on this link will

14- 14 -14-

14 -- 14 -


invoke Figure 3-8 pertaining to Ring Map. If the service type for this ring is MON, clicking on this link will

invoke Figure 3-7 pertaining to MON Details.

15- 15 -15-

15 -- 15 -


10 Ring Alias. Clicking on this link will invoke Figure 3-15 pertaining to Update Ring Alias

11 Service Type for this ring. Value is either SONET or MON.12 OC Level of this ring. Value is either OC-3, OC-12, OC-48, or OC-192. This

is not applicable for MON rings.13 Ring Type.

Value for SONET rings is either “CHAIN UNPROT'D”, “CHAIN PROT'D”, “BLSR 2B”, “UPSR”, or “BLSR 4B”. Value for MON rings is either “B-OCHDPRING”, “U-OCHDPRING”, “P-P OMS”, or “P-P OCH”.

14 Number of nodes in this ring.15 If the ring has no alarms, this will display “Normal” in green.

If the ring has a corresponding ring-level alarm, this will display “Alarm”. The text will be color-coded based on the severity level of the event.

Critical – Red Major – Amber Minor – Yellow

If this is a SONET ring and the ring does not have a corresponding ring-level alarm but it contains nodes that have alarms, this will display “Alarm”. The text will be color-coded based on the node alarms’ highest severity level (e.g. If the ring has a node with a Critical level alarm and another node with a Major level alarm, “Alarm” will be displayed in red.). If this is a MON ring and the ring does not have a corresponding ring-level alarm but it contains lambdas that have alarms, this will display “Alarm”. The text will be color-coded based on the lambda alarms’ highest severity levels.

Table 3-3: Elements of Network Map

16- 16 -16-

16 -- 16 -


3.4 MON Details

3.4.1 Accessing the MON Details Click on MON Ring ID in the Network Map page or Circuit Map (SONET over

MON) page or Multiple Circuit Info. Maintenance page or Single Circuit Info. Maintenance page

Click on Configuration Management on the toolbar when the current page is MON Outages or SONET over MON level circuit performance table.

3.4.2 Using the MON Details The MON Details displays DWIDs, Bands and Lambda DWDM (Wavelength) attributes of a MON network. Each MON Ring ID has 2 DWIDs corresponding to the C-Band and the L-Band, respectively, each DWID has 4 bands and each band has 4 Lambdas. If the service for the Lambda is SONET, the Lambda has an associated SCID.

17- 17 -17-

17 -- 17 -


18- 18 -18-

18 -- 18 -

21

47

3

658


Figure 3-7: MON Details

19- 19 -19-

19 -- 19 -


Item Description 1 MON subscriber’s userid.2 Network ID, MON Ring ID and Ring Alias.3 DWID and Band Type.

The MON Details displays DWIDs, Bands and Lambda wavelength attributes of a MON network. Each MON Ring ID has 2 DWIDs corresponding to the C-Band and the L-Band, respectively, each DWID has 4 bands and each band has 4 Lambdas. If the service for the Lambda is SONET, the Lambda has an associated SCID.

4 Band - Band Type is either C-Band or L-Band.5 Lambda.- single wavelength6 Service ID (link). Clicking on this link will invoke Figure 3-8 pertaining to

Ring Map.7 If the lambda has no alarms, this will display “Normal” in green.

If the lambda has a corresponding lambda-level alarm, this will display “Alarm”. The text will be color-coded based on the severity level of the event. Critical – Red Major – Amber Minor – YellowIf the lambda does not have a corresponding lambda-level alarm but it contains nodes that have alarms, this will display “Alarm”. The text will be color-coded based on the node alarms’ highest severity level (e.g. If the ring has a node with a Critical level alarm and another node with a Major level alarm, “Alarm” will be displayed in red.).

8 Dropdown list of options available for this Lambda. Lambda Details will invoke Figure 3-20 pertaining to Lambda Details Report

Table 3-4: Elements of MON Details

20- 20 -20-

20 -- 20 -


3.5 Ring Map

3.5.1 Accessing the Ring Map Click on a Ring ID in the Network Map page Click on Service ID in the MON Details page Click on a Ring ID link in the Circuit Map, Circuit Information Maintenance,

or the Single Circuit Information Maintenance page Click on Configuration Management on the toolbar when the current page

is Ring Outages or the ring level circuit performance table.

3.5.1 Using the Ring MapThe ring map displays the topology of a SONET or MON ring and associated nodes that transport the data across the ring. The following illustration is a Ring Map for SONET networks.

21- 21 -21-

21 -- 21 -


Figure 3-8: Ring Map

22- 22 -22-

22 -- 22 -

2 1

3

7 8

9

10

11

12

5

4

6


Item

Description

1 SONET/MON subscriber’s userid.2 Network ID, Ring ID, Ring Alias and total number of nodes in the ring.

If this is a MON ring, the Service ID will also be displayed and the Ring ID will be clickable. Clicking on the Ring ID will invoke Figure 3-7 pertaining to MON Details.

3 Target ID (TID) of the node.4 Node Location. Location consists of the city.5 Graphical representation of the ring and its nodes. The nodes are color-

coded based on the severity level of the event affecting the nodes Critical – Red Major – Amber Minor – Yellow

If a node currently has no alarms, it will be green. If a node has a corresponding node-level alarm, its color will be based on that alarm’s severity level. Clicking on a TID link will invoke Figure 3-9 pertaining to Circuit Map.If the node does not have a corresponding node-level alarm but it contains circuits that have alarms, its color will be based on the circuit alarm’s highest severity level. (E.g. If the node has a circuit with a Critical level alarm and another circuit with a Major level alarm, the node will be red.)

6 OC-Level of the ring, Interface Speed, and Ring Type. OC-Level value is either OC-3, OC-12, OC-48, or OC-192. This is not applicable for MON rings.The interface speed is not applicable for MON rings.Ring Type. Value for SONET rings is either “CHAIN UNPROT'D”, “CHAIN PROT'D”, “BLSR 2B”, “UPSR”, or “BLSR 4B”. Value for MON rings is either “B-OCHDPRING”, “U-OCHDPRING”, “P-P OMS”, or “P-P OCH”.

7 Clicking on the "Up Arrow" sorts the list of circuits in ascending order.The sorting parameters provided are “TID”, "Node Location" (City), and “Status”. If no sorting parameter is specified, the Ring Map is sorted by ascending "TID".

8 Clicking on the "Down Arrow" sorts the list of circuits in descending order.

23- 23 -23-

23 -- 23 -


The sorting parameters provided are “TID”, "Node Location" (City), and “Status”.

24- 24 -24-

24 -- 24 -


9 Target ID (TID) of the node. For SONET rings or MON rings with SONET service, the TID will be a clickable link. Clicking on a TID link will invoke Figure 3-9 pertaining to Circuit Map.

10 Node Location. Location consists of street number and name, city, and state.

11 If the node has no alarms, this will display “Normal” in green.If the node has a corresponding node-level alarm, this will display “Alarm”. The text will be color-coded based on the severity level of the event. Critical – Red Major – Amber Minor – YellowIf the node does not have a corresponding node-level alarm but it contains circuits that have alarms, this will display “Alarm”. The text will be color-coded based on the circuit alarms’ highest severity level (e.g. If the node has a circuit with a Critical level alarm and another circuit with a Major level alarm, “Alarm” will be displayed in red).

12 Dropdown list of options available for this node. Values are: Node Details will invoke Figure 3-16 pertaining to Node Details

Report Circuit Info. Maintenance will invoke Figure 3-14 pertaining to

Multiple Circuit Information MaintenanceTable 3-5: Elements of Ring Map

25- 25 -25-

25 -- 25 -


3.6 Circuit Map

3.6.1 Accessing the Circuit MapClick on a TID or a Node in the Ring Map OR the Single Circuit Information Maintenance Page

3.6.2 Using the Circuit MapThe circuit map displays all the circuits passing through a particular node. There is a circuit filter feature. If filtering is on, only circuits matching the filter criteria are displayed. If filtering is off, all circuits for the selected node are displayed.

26- 26 -26-

26 -- 26 -


Figure 3-9: Circuit Map

27- 27 -27-

27 -- 27 -

21

45

7 8

9 10

1211

13

3


Item

Description

1 SONET/MON subscriber’s userid.2 Network ID, Ring ID (link), Ring Alias, and TID. If this is a MON ring, the

Service ID will also be displayed as a link.For SONET, clicking on the Ring ID will invoke Figure 3-8 pertaining to Ring Map.For SONET over MON, clicking on the Ring ID will invoke Figure 3-7 pertaining to MON Details and clicking on the Service ID will invoke Figure3-8 pertaining to Ring Map.

3 Clicking on the "Filter” button will invoke Figure 3-10 pertaining to Circuit Filter.

4 Clicking on the "Up Arrow" or the "Down Arrow" retrieves and provides views for additional circuits. The default presentation of a set of circuits is 30 circuits per page. Clicking on the "Up Arrow" will display the previous set of circuits; Clicking on the "Down Arrow" will display the next set of circuits. These arrows are also available at the bottom of this page if there is more than one page. If the user is viewing the first set of circuits, the "Up Arrow" will be disabled. If the user is viewing the last set of circuits, then the "Down Arrow" will be disabled. If all the circuits can be shown in one page, both arrows will be disabled.

5 Start and end count of circuits displayed on this page, followed by the closing bracket and the literal “of” followed by the total number of circuits to be displayed, followed by the literal “Circuit(s)”. For example, if this user has a total of 100 circuits and the second page is being displayed, this text would read, “[31 – 60] of 100 Circuit(s)”. If filtering were in effect, this text would read “[31 – 60] of 80 Filtered Circuit(s)” (if filtering criteria results into 80 circuits).

28- 28 -28-

28 -- 28 -


6 If there are more than 60 circuits to be displayed, a dropdown box is displayed which allows the user to select the range of circuits to view (in 30 circuit increments). This dropdown box will also be available at the bottom of this page.


7 Clicking on the "Up Arrow" sorts the list of circuits in ascending order.The sorting parameters provided are "Circuit ID", "Circuit Alias", “SONET Rate”, “Speed”, and “Status”. If no sorting parameter is specified, the Circuit Map is sorted by ascending "Circuit ID".

29- 29 -29-

29 -- 29 -


8 Clicking on the "Down Arrow" sorts the list of circuits in descending order.The sorting parameters provided are "Circuit ID", "Circuit Alias", “SONET Rate”, “Speed”, and “Status”.

9 Circuit ID.10 Circuit Alias.11 SONET Rate and Speed.12 If the circuit has no alarms, this will display “Normal” in green.

If the circuit has an alarm, this will display “Alarm”. The text will be color-coded based on the severity level of the event.


13 Dropdown list of reports available for this circuit. Values are: Circuit Details will invoke Figure 3-14 pertaining to Circuit Details

Report Circuit Info. Maint. will invoke Figure 3-13 pertaining to Single Circuit

Information MaintenanceTable 3-6: Elements of Circuit Map

30- 30 -30-

30 -- 30 -


3.7 Circuit Filter

3.7.1 Accessing the Circuit Filter Click the “FILTER" button/link in the Circuit Map page Click on the " FILTER" button/link in the Fault Management - Circuit Outages

page

3.7.2 Using the Circuit FilterThis feature allows the CNM user to specify filtering criteria so that only a subset of the circuits belonging to a specific node will be displayed in the Circuit Map or Circuit Outages page.

Figure 3-10: Circuit Filter from Circuit Map

31- 31 -31-

31 -- 31 -

2

1

45 6

3


Figure 3-11: Circuit Filter from Circuit Outages

32- 32 -32-

32 -- 32 -


Item

Description

1 If this page is invoked from the "Filter" link in the "Circuit Map" page, the title displayed is "Circuit Map" If it is invoked from the “Filter” link in the “Circuit Outages” page, the title is “Circuit Outages”

2 Target dropdown box contains circuit attributes that can be used as filter criteria. Values are: “Street Number/Name“ “City“ “State“ “Circuit ID“ “Circuit Alias“Default value is “Circuit ID”.

3 Criteria dropdown box contains the list of operators that specify the relationship between the target attribute and the value entered by the user. Values are: “Contains“ “Equals“Default Value is “Contains”.

4 Input text box where the user can specify a specific criteria value (ex. SONET.111111).

5 Clicking the "START FILTER" button validates the information entered by the user. The following validation rules are checked: Value is a required field (ex. SONET.111111). Value cannot contain the following characters: “%”, “&”If no error is detected, either the Circuit Map or Circuit Outages page is regenerated with circuits matching the specified filter criteria.

6 Clicking the "STOP FILTER" button regenerates the Circuit Map or Circuit Outages page with all the circuits within a selected node.

Table 3-7: Elements of Circuit Filter

33- 33 -33-

33 -- 33 -


If the user has no circuit(s) matching the filter criteria, following screen is displayed.

Figure 3-12: Circuit Map Filters

34- 34 -34-

34 -- 34 -


3.8 Single Circuit Information Maintenance

3.8.1 Accessing the Single Circuit Information MaintenanceClick the “Single Circuit Info. Maint” option in the Circuit Map drop down box.

3.8.2 Using the Single Circuit Information MaintenanceThis feature allows the CNM user to specify a different circuit alias, contact person, location, phone number and/or email address for the origination and destination end points of a specific circuit.

35- 35 -35-

35 -- 35 -

21

6

8 9

7

5

3

4


Figure 3-13: Single Circuit Information Maintenance

36- 36 -36-

36 -- 36 -


Item

Description

1 SONET/MON subscriber’s userid.2 Network ID, Ring ID (link), Ring Alias, and TID (link). If this is a MON ring,

the Service ID will also be displayed as a link.For SONET, clicking on the Ring ID will invoke Figure 3-8 pertaining to Ring Map.For SONET over MON, clicking on the Ring ID will invoke Figure 3-7 pertaining to MON Details and clicking on the Service ID will invoke Figure3-8 pertaining to Ring Map.For both SONET and SONET over MON, clicking on the TID will invoke Figure 3-9 pertaining to Circuit Map.

3 Circuit ID. 4 Circuit’s SONET Rate.5 Circuit Alias.6 Input Box for origination contact name / street address / city / telephone /

e-mail / state / zip code. Pre-populated with the current value in the database.

7 Input Box for destination contact name / street address / city / telephone / e-mail / state / zip code. Pre-populated with the current value in the database.

8 Clicking the "SUBMIT" button validates all the information entered by the user. The following validation rules are checked origination/destination contact name, origination/destination contact

street address, origination/destination contact city, and origination/destination contact state are required fields

origination/destination zip code should be a 5-digit number origination/destination email address should have at least 1 “@”

character and can contain only the following characters: alphabetic, numeric, period, hyphen, “_”, “@”

origination/destination telephone number should be in the format nnn-nnn-nnnn

origination/destination contact name, origination/destination contact street address, and circuit alias should contain only the following characters: alphabetic, numeric, space, apostrophe, period, comma,

37- 37 -37-

37 -- 37 -


hyphen, “@”, “#” origination/destination contact city should contain only the following

characters: alphabetic, space, apostrophe, period, comma, hyphen, “@”, “#”

If no error is detected, a confirmation pop-up window will be displayed. 9 Clicking the "RESET" button reloads the Single Circuit Information

Maintenance page with all input fields reset to their current values in the database.

Table 3-8: Elements of Single Circuit Information Maintenance

38- 38 -38-

38 -- 38 -


3.9 Multiple Circuit Information Maintenance

3.9.1 Accessing the Multiple Circuit Information Maintenance

Click the “Circuit Info. Maint” option in the Ring Map drop down box.

3.9.2 Using the Multiple Circuit Information MaintenanceThe feature allows the CNM user to specify a different contact details for the origination and destination end points of multiple circuits within a node.

39- 39 -39-

39 -- 39 -


Figure 3-14: Multiple Circuit Information Maintenance

40- 40 -40-

40 -- 40 -

14

2

1

4

5

6 9

3

810

1311 12

15

16

7

17


Item

Description

1 SONET/MON subscriber’s userid.2 Network ID, Ring ID (link), Ring Alias, and TID. If this is a SONET over MON

ring, the Service ID will also be displayed as a link.For SONET, clicking on the Ring ID will invoke Figure 3-8 pertaining to Ring Map.For SONET over MON, clicking on the Ring ID will invoke Figure 3-7 pertaining to MON Details and clicking on the Service ID will invoke Figure3-8 pertaining to Ring Map.

3 Input Box for origination contact name, street address, city, telephone, e-mail, state, and zip code.

4 Input Box for destination contact name, street address, city, telephone, e-mail, state, and zip code.

5 Circuit ID. 6 Circuit Alias.7 Circuit’s SONET Rate.8 Current Origination Contact Name.9 Current Origination Contact Address. Address consists of street number

and name, city, and state.10 Current Origination Contact telephone number and Current Origination

Contact Email Address.11 Current Destination Contact Name.12 Current Destination Contact Address. Address consists of street number

and name, city, and state.13 Current Destination Contact telephone number and Current Destination

Contact Email Address.14 When the "UPDATE ALL" button is clicked, all the checkboxes will be

checked.15 Clicking the "SUBMIT" button validates all the information entered by the

user. The following validation rules are checked: at least 1 checkbox must be selected

41- 41 -41-

41 -- 41 -


contact name, contact street address, contact city, and contact state are required fields

zip code should be a 5-digit number email address should have at least 1 “@” character and can contain

only the following characters: alphabetic, numeric, period, hyphen, “_”, “@”

telephone number should be in the format nnn-nnn-nnnn contact name and contact street address should contain only the

following characters: alphabetic, numeric, space, apostrophe, period, comma, hyphen, “@”, “#”

contact city should contain only the following characters: alphabetic, space, apostrophe, period, comma, hyphen, “@”, “#”

If no error is detected, a confirmation pop-up window will be displayed. 16 Clicking the "CLEAR" button reloads the Multiple Circuit Information

Maintenance page with all input fields and checkboxes cleared. 17 This column could be sorted in ascending / descending order for Circuit ID,

Circuit Alias and SONET RateTable 3-9: Elements of Multiple Circuit Information Maintenance

42- 42 -42-

42 -- 42 -


3.10 Update Ring Alias

3.10.1 Accessing the Update Ring Alias Click the “Ring Alias” from the Network Map. Click the “Circuit Info. Maint” option in the Ring Map drop down box.

3.10.2 Using the Update Ring AliasThis feature opens a new window that will allow the SONET/MON user to specify an alias for the ring ID.

Figure 3-15: Update Ring Alias

Item

Description

1 Ring ID 2 Current ring alias.3 Clicking the "SUBMIT" button displays a confirmation pop-up window.4 Clicking the "RESET" button reloads this page with the current ring alias in

the database.5 Clicking the "CLOSE" button closes the Update Ring Alias pop-up window.

43- 43 -43-

43 -- 43 -

3

42

1

5


Table 3-10: Elements of Update Ring Alias

05/18/23 PROPRIETARY INFORMATIONNot for use or disclosure outside AT&T Communications, Inc. Except under written

agreement44- 44 -44-

44 -- 44 -


3.11 SONET Node Details Report

3.11.1 SONET Node Details ReportClick the “Node Details” option in the Ring Map drop down box.

3.11.2 Using the SONET Node Details ReportThis report provides all the relevant details of SONET Network Node including hardware and software details

Figure 3-16: Node Details Report

45- 45 -45-

45 -- 45 -


3.12 MON Node Details Report

3.12.1 Accessing the MON Node Details ReportClick the “Node Details” option in the Ring Map drop down box.

3.12.2 Using the MON Node Details ReportThis report provides all the relevant details of MON Network Node including hardware and software details

Figure 3-17: MON Node Details Report

46- 46 -46-

46 -- 46 -


3.13 SONET Circuit Details Report

3.13.1 Accessing the SONET Circuit Details ReportClick the “Circuit Details” option in the Circuit Map drop down box.

3.13.2 Using the SONET Circuit Details ReportThis report provides full details of selected SONET circuit including origination and destination locations and Identifiers.

47- 47 -47-

47 -- 47 -


Figure 3-18: SONET Circuit Details Report

48- 48 -48-

48 -- 48 -


3.14 SONET over MON Circuit Details Report

3.14.1 Accessing the SONET over MON Circuit Details Report

Click the “Circuit Details” option in the Circuit Map drop down box.

3.14.2 Using the SONET over MON Circuit Details ReportThis report provides full details of selected MON circuit including origination and destination locations and Identifiers.

49- 49 -49-

49 -- 49 -


Figure 3-19: MON Circuit Details Report

50- 50 -50-

50 -- 50 -


3.15 Lambda Details Report

3.15.1 Accessing the Lambda Details ReportClick the “Lambda Details” option in the MON Details drop down box.

3.15.2 Using the Lambda Details ReportThis report provides details of Lambda Dense Wavelength Identifier (DWID) including Band Type, direction and other bandwidth details.

Figure 3-20: Lambda Details Report

51- 51 -51-

51 -- 51 -


4 Fault ManagementFault Management helps CNM for SONET/MON customers to manage their network by monitoring, and providing them with notification of alarms that may occur in their network. For example, if a Link Down alarm occurs on the SONET network, CNM Fault Management can help identify the specific source of that Link Down alarm. This service provides customers with the capability to specify the conditions that trigger a system notification and to choose other preferences, as well.

All SONET/MON alarms and events are reported by the ring, using Transaction Language 1 (TL1) protocol. This information gets matched to a table of alarms and events that CNM supports. (The SONET equipment manufactures, used by AT&T, each provide hundreds of alarms and events, many of which are either repetitious, or otherwise of little value to a Network Manager.) Those which CNM supports, are then filtered to match the CNM customer base. The remaining alarms and events are loaded into a database to be available for pulling by CNM. Detection Settings on CNM can be set to pull this information, in 1-15 minute range.

4.1 Accessing Fault Management

To access Fault Management, click on “Fault Management” on the navigation toolbar. The user will be presented either with the “Healthy Network Message” screen as shown in Figure 4-23 or with the “Network Outages” screen (Figure 4-22). Clicking on “Fault Management” will expand the toolbar, and the user will be presented with the “Network Outages”, “Alarm and Event History”, “Detection Status”, “Detection Settings”, and ”Notification Settings” options, as shown in Figure 4-21.

52- 52 -52-

52 -- 52 -


Figure 4-21: Accessing Fault Management

Option DescriptionNetwork Outages The “Network Outages” screen displays all the

SONET (see Figure 4-22) and MON (see Figure 4-24) networks belonging to a customer that currently have rings with events and alarms.

Alarm and Event History

The “Alarm and Event History” screen displays all of the events and alarms within the past 30 days.

Detection Status “Detection Status” allows the user to activate online detection. Based on the detection settings, it will periodically check the database for incoming events.

Detection Settings This feature allows the user to view and/or specify fault detection settings. Detection settings include duration, frequency, and audible alarm setting.

Notification Settings The feature allows the user to specify fault notification settings such as trigger counters (count at which an alphanumeric pager/email/online notification will be sent out), email, and alphanumeric pager settings.

53- 53 -53-

53 -- 53 -

Click on the “Fault Management” link to access Fault Management.


Table 4-11: Fault Management Options Description

4.2 Network Outages

4.2.1 Accessing Network Outages

Click on the “Fault Management” link in the Toolbar when the current page is not the “MON Details”, “Ring Map”, “Circuit Map”, or the “Circuit Performance Table” at the MON, ring, or circuit level.

Click on the “Network Outages” link in the Toolbar. Click on the “Network Outages” link in the Site Map.

4.2.2 Using Network Outages

“Network Outages” provides a complete list of all networks that contain rings which have alarms. It uses color-coded Alarm Levels to reveal the condition of each ring. If there are no active alarms, the “Network Outages” screen appears, with the message “There are no active alarms to report. Your network(s) is in good condition!” (Figure 4-23). This means that the network is healthy and traffic is flowing smoothly. An active alarm is one in which the condition that caused the alarm in the network, ring, or node is still present.

When there are current fault alarms, the “Network Outages” screen will resemble Figure 4-22.

54- 54 -54-

54 -- 54 -


Figure 4-22: Network Outages

Item Description1 Displays your User ID.2 Displays your Business Name and Address.3 Clicking on the “Up Arrow” or the

“Down Arrow” displays additional networks. The default presentation is a set of 30 networks per page. When viewing the first set of circuits, the “Up Arrow” is disabled. The “Down Arrow” will be disabled when viewing the last set. If all the networks are shown on one page, both arrows will be disabled. A Network Range Selector window with dropdown (shown at right) will be available if there are more than 60 networks. The arrows, and the dropdown box are also available at the bottom of the page if there is more than one page.

Select next range of networks to view

55- 55 -55-

55 -- 55 -

1

3

2

5

4

6

78

9

10 11


Item Description4 Displays the start and end count of networks displayed on the page and

the total number of networks.5 Clicking on the “Up Arrow” in the Sort Bar sorts the networks in

ascending order by Network ID. This is the default sorting order.6 Clicking on the “Down Arrow” in the Sort Bar sorts the networks in

ascending order by Network ID. 7 Displays the Network ID associated with the outage.8 Ring ID.

If the service type for this ring is SONET, this will display the SCID as a clickable link. Clicking on this link will invoke Figure 4-26 Ring Outages.

If the service type for this ring is MON, this will display the MON Ring ID as a clickable link. Clicking on this link will invoke Figure 4-24MON Outages.

9 Ring Alias. Clicking on this link will invoke “Update Ring Alias” which is explained in Configuration Management (Section 3.8.2).

10 Event Description. If the ring has a corresponding ring-level alarm, the Event Type and Event Timestamp will be displayed.

11 Alarm’s severity level.If the ring has a corresponding ring-level alarm, this will display that alarm’s severity level. If this is a SONET ring and the ring does not have a corresponding ring-level alarm but it contains nodes that have alarms, this will display the node alarms’ highest severity level. (E.g. If the ring has a node with a Critical level alarm and another node with a Major level alarm, “Critical” will be displayed.)If this is a MON ring and the ring does not have a corresponding ring-level alarm but it contains lambdas that have alarms, this will display the lambda alarms’ highest severity level. (E.g. If the ring has a lambda with a Critical level alarm and another lambda with a Major level alarm, “Critical” will be displayed.)The text is color-coded based on the severity level of the alarm. Alarms and Severity Levels for the possible values of the alarm types and their corresponding severity levels):


Table 4-12: Elements of Network Outages

56- 56 -56-

56 -- 56 -


Figure 4-23: Network Outages – Healthy Network

57- 57 -57-

57 -- 57 -


4.3 MON Outages

4.3.1 Accessing MON Outages

To access the “MON Outages” screen, if the service type for this ring is MON: Click on the Ring ID from the “Network Outages” page (see Figure 4-22,

item 8). Click on the Ring ID from the “Circuit Outages” page (see Figure 4-28,

item 2). Click on the “Fault Management” link in the Toolbar when the current

page is the “MON Details” (Figure 3-7) or the “Circuit Performance Table” (Figure 5-39) at the MON level.

4.3.2 Using MON Outages

The MON Outages page displays the alarms specific to MON Network.

Figure 4-24: MON Outages

58- 58 -58-

58 -- 58 -

43

12

5

6

7

8


Item

Description

1 Displays your User ID.2 Displays your Network ID, Ring ID and the Ring Alias.3 Clicking on the “Up Arrow” in the Sort Bar sorts the lambdas in

ascending order based on that sorting parameter. The sorting parameters provided are “Service ID” and “Alarm Level”. The default sort provided is by ascending “Service ID”.

4 Clicking on the “Down Arrow” in the Sort Bar sorts the lambdas in ascending order based on that sorting parameter. The sorting parameters provided are “Service ID” and “Alarm Level”.

5 DWID and its Band Type, Band, and Lambda. Band Type is either C-Band or L-Band.

6 Service ID (link). Clicking on this link will invoke Figure 4-26 Ring Outages.

7 Event Description. If the lambda has a corresponding lambda-level alarm, the Event Type and Event Timestamp will be displayed.

8 Alarm’s severity level.If the lambda has a corresponding lambda-level alarm, this will display that alarm’s severity level. If the lambda does not have a corresponding lambda-level alarm but it contains nodes that have alarms, this will display the node alarms’ highest severity level. (E.g. If the lambda has a node with a Critical level alarm and another node with a Major level alarm, “Critical” will be displayed.)The text is color-coded based on the severity level of the alarm.


Table 4-13: Elements of MON Outages

59- 59 -59-

59 -- 59 -


Figure 4-25: MON Outages – Healthy MON

60- 60 -60-

60 -- 60 -


4.4 Ring Outages

4.4.1 Accessing Ring OutagesTo access the “Ring Outages” screen, if the service type for this ring is SONET:

Click on the “Fault Management” link in the Toolbar when the current page is the “Ring Map” (Figure 3-8) or the “Circuit Performance Table” (Figure 5-40) at the ring level.

Click on the specific Ring ID from the “Network Outages” page (Figure 4-22).

Click on the specific Ring ID from the “MON Outages” page (Figure 4-24).

Click on the Ring ID from the “Circuit Outages” page (Figure 4-28).

4.4.2 Using Ring OutagesThe Ring Outage page displays the nodes in the ring that currently have alarms. It also displays a graphical topology of the ring.

61- 61 -61-

61 -- 61 -


Figure 4-26: Ring Outages

Item

Description

1 Displays your User ID.2 Network ID, Ring ID, Ring Alias, and total number of nodes in the ring.

If this is a MON ring, the Service ID will also be displayed and the Ring ID will be clickable. Clicking on the Ring ID invokes Figure 4-24, “MON Outages”.

3 Target ID (TID) of the node.4 Node Location (City).

62- 62 -62-

62 -- 62 -

1

2

3 4

56

7 89

10 11


Item

Description

5 Graphical representation of the ring and its nodes. The nodes are color-coded based on the severity level of the alarm affecting the nodes.


If a node currently has no alarms, it will be green and non-clickable. If a node has a corresponding node-level alarm, it will be clickable and its color will be based on that alarm’s severity level.If the node does not have a corresponding node-level alarm but it contains circuits that have alarms, it will be clickable and its color will be based on the circuit alarms’ highest severity level. (e.g. If the node has a circuit with a Critical level alarm and another circuit with a Major level alarm, the node will be red.)For SONET rings or MON rings with SONET service, the node will be clickable. Clicking on a node will invoke Figure 4-28, “Circuit Outages”.

6 OC-Level of the ring, Circuit Speed, and SONET Ring Type.OC-Level value is either OC-3, OC-12, OC-48, or OC-192. This is not applicable for MON rings.The Circuit Speed is not applicable for MON rings.Ring Type. Value for SONET rings is either “CHAIN UNPROT'D”, “CHAIN PROT'D”, “BLSR 2B”, “UPSR”, or “BLSR 4B”. Value for MON rings is either “B-OCHDPRING”, “U-OCHDPRING”, “P-P OMS”, or “P-P OCH”.

7 Clicking on the "Up Arrow" sorts the list of nodes in ascending order based on that sorting parameter.The sorting parameters provided are “TID” and “Alarm Level”. The default sort provided is by ascending "TID".

8 Clicking on the "Up Arrow" sorts the list of nodes in ascending order based on that sorting parameter. The sorting parameters provided are “TID” and “Alarm Level”.

9 Target ID (TID) of the node. For SONET rings or MON rings with SONET service, the TID will be a clickable link. Clicking on a TID link will invoke Figure 4-28 Circuit Outages.

10 Event Description. If the node has a corresponding node-level alarm, the Event Type and Event Timestamp will be displayed.

63- 63 -63-

63 -- 63 -


Item

Description

11 Alarm’s severity level.If the node has a corresponding node-level alarm, this will display that alarm’s severity level. If the node does not have a corresponding node-level alarm but it contains circuits that have alarms, this will display the circuit alarms’ highest severity level. (e.g. If the node has a circuit with a Critical level alarm and another circuit with a Major level alarm, “Critical” will be displayed.)The text is color-coded based on the severity level of the alarm.


Table 4-14: Elements of Ring Outages

Figure 4-27: Ring Outages – Healthy Ring

64- 64 -64-

64 -- 64 -


4.5 Circuit Outages

4.5.1 Accessing Circuit OutagesTo access the “Circuit Outages” screen, if the service type for the selected ring is SONET: Click on the “Fault Management” link in the Toolbar and the current page

is the “Circuit Map” Figure 3-9 or the “Circuit Performance Table” Figure 5-41 at the circuit level.

Click on a specific node with outages in a “Ring Outages” page Figure 4-26.

4.5.2 Using Circuit OutagesThe Circuit Outages page, which only applies to SONET service, displays all the circuits passing through a particular node that currently have alarms. The page provides a circuit filter feature to assist in locating specific circuits. When filtering is on, only circuits matching the filter criteria are displayed.

Figure 4-28: Circuit Outages

65- 65 -65-

65 -- 65 -

1

2 3

4 5

6 7

8

9

10

11


Item Description1 Displays your User ID.2 Network ID, SCID (link), Ring Alias, and TID. If this is a MON ring, the MON Ring ID

will also be displayed as a link.Clicking on the MON Ring ID invokes Figure 4-24 MON Outages.Clicking on the SCID invokes Figure 4-26 Ring Outages.

3 Clicking on the "Filter” button invokes the Circuit Filter, Figure 3-11. 4 Clicking on the “Up Arrow” or the

“Down Arrow” displays additional circuits. The default presentation is a set of 30 circuits per page. When viewing the first set of circuits, the “Up Arrow” is disabled. The “Down Arrow” will be disabled when viewing the last set. If all the circuits are shown on one page, both arrows will be disabled. A Circuit Range Selector window with dropdown (shown at right) will be available if there are more than 60 networks. The arrows, and the dropdown box are also available at the bottom of the page if there is more than one page.


5 Start and end count of circuits displayed on this page, followed by the total number of circuits to be displayed. For example, if this user has a total of 100 circuits and the second page is being displayed, this text would read, “[31 – 60] of 100 Circuit(s)”. If filtering were in effect, this text would read “[31 – 60] of 80 Filtered Circuit(s)” (if filtering criteria results into 80 circuits).

6 Clicking on the "Up Arrow" sorts the list of circuits in ascending order based on that sorting parameter. The sorting parameters provided are "Circuit ID", "Circuit Alias", “Sonet Rate”, “Speed”, and “Alarm Level”. If no sorting parameter is specified, the Circuit Outages page is sorted by ascending "Circuit ID".

7 Clicking on the "Down Arrow" sorts the list of circuits in descending order based on that sorting parameter. The sorting parameters provided are "Circuit ID", "Circuit Alias", “Sonet Rate”, “Speed”, and “Alarm Level”.

8 Circuit ID and Circuit Alias.9 Circuit SONET Rate and Circuit Speed.10 Event Type and Timestamp. 11 Circuit Alarm’s severity level. The text is color-coded based on the severity level

of the alarm type.

66- 66 -66-

66 -- 66 -


Critical – Red Major – Amber Minor - Yellow

Table 4-15: Elements of Circuit Outages

67- 67 -67-

67 -- 67 -


Figure 4-29: Circuit Outages – Healthy Circuits

Figure 4-30: Circuit Outages – Filtered with No Circuits

68- 68 -68-

68 -- 68 -


4.6 Alarm and Event History

4.6.1 Accessing Alarm and Event HistoryTo access the “Alarm and Event History” screen:

Click on the “Alarm and Event History” link in the Toolbar. Click on the “Alarm and Event History” link in the Site Map. Click on “View History” from the Alarm Window (Figure 4-34).

4.6.2 Using Alarm and Event HistoryThe “Alarm and Event History” screen displays all of the events and alarms within the past 30 days for a CNM SONET/MON user. For each alarm/event, the “Alarm and Event History” screen tells what type of alarm/event it was, the date and time of the alarm/event occurrence, and the message, which provides additional detail about that alarm/event.

Figure 4-31: Alarm and Event History

69- 69 -69-

69 -- 69 -

12

34 5

6 7

8 9

10


Item

Description

1 Displays your User ID.2 Displays your Business Name and Address.3 Dropdown box containing all the dates within the past 30 days when

alarms/events have occurred.4 Clicking on the “Up Arrow” or the

“Down Arrow” displays additional alarms/events. The default presentation is a set of 30 alarms/events per page. When viewing the first set of alarms/events, the “Up Arrow” is disabled. The “Down Arrow” will be disabled when viewing the last set. If all the alarms/events are shown on one page, both arrows will be disabled. An alarm/event Range Selector window with dropdown (shown at right) will be available if there are more than 60 alarms/events. The arrows, and the dropdown box are also available at the bottom of the page if there is more than one page.

Select next range of alarms/events to view

5 Start and end count of alarms/events displayed on this page, followed by the total number of alarms/events to be displayed.

6 Clicking on the "Up Arrow" sorts the list of alarms/events in ascending order based on that sorting parameter. The sorting parameters provided are "Alarm/Event Type", and “Date-Time”. If no sorting parameter is specified, the “Alarm and Event History” page is sorted by "Date-Time" with the most recent at the top.

7 Clicking on the “Down Arrow" sorts the list of alarms/events in descending order based on that sorting parameter. The sorting parameters provided are "Alarm/Event Type", and “Date-Time”.

8 Alarm/Event Type. Types are color-coded based on their severity level. Critical – Red Major – Amber Minor – Yellow Informational – Green

9 Alarm/Event Timestamp with time zone.10 Alarm/Event Description.

70- 70 -70-

70 -- 70 -


Table 4-16: Elements of Alarm and Event History

71- 71 -71-

71 -- 71 -


4.7 Detection Settings

4.7.1 Accessing Detection SettingsTo access the “Detection Settings” screen:

Click on the “Detection Settings” link in the Toolbar. Click on the “Detection Settings” link in the Site Map.

Click on “Settings” from the Detection Status window ().

4.7.2 Using Detection SettingsThe Detection Settings feature allows the CNM customer to specify online fault detection settings such as duration, frequency, and audible alarm settings.

Figure 4-32: Detection Settings

72- 72 -72-

72 -- 72 -

1

2

3

4

5 6


Item

Description

1 Displays your User ID.2 “Enable Audible Alarm” Setting: If you select this check box, when the

“Alarm” window appears, a siren will sound.3 “Check for alarms every” (Frequency) setting: This will determine how

often the database will be checked for incoming alarms. Values are from 1 to 15 minutes. The default value is 5 minutes.

4 “Continue checking for” (Duration) setting: This will determine how long online detection will run. Values are from 1 to 18 hours. The default value is 3 hours.

5 Clicking on the “SUBMIT” button displays a confirmation pop-up window for your acknowledgement to proceed with the database update of the new values.

6 Clicking on the “RESET” button reloads the current detection setting values from the database.

Table 4-17: Elements of Detection Settings

73- 73 -73-

73 -- 73 -


4.8 Detection Status

4.8.1 Accessing Detection StatusTo access the “Detection Status” screen:

Click on the “Detection Status” link in the Toolbar. Click on the “Detection Status” link in the Site Map. Click on “Settings” from the Detection Status window (Figure 4-33).

4.8.2 Using Detection StatusThe feature allows the user to activate online detection. Based on the detection settings, it will periodically check the database for incoming events.

The Detection window must be active for online fault detection to occur. However, the window can be minimized so it does not obscure other windows.

Detection can occur offline, without an active Detection window, as well. System can be configured to notify a user by pager or by e-mail when an alarm occurs (discussed in section 4.9, Notification Settings)

74- 74 -74-

74 -- 74 -

2

3

1

4

5 6 7 8


Figure 4-33: Detection Status

The circular radar-scan image rotates on the screen as seconds tick by on the digital timer. This timer tracks the duration of each query cycle, also known as frequency. If an alarm is detected, the word “Yes” appears in red. Clicking on “Yes”, or when a fault occurs with detection on, a new window as shown in Figure 4-34 is presented for acknowledging the alarm and viewing a history of alarms and events.

Item

Description

1 This indicates the type of technology to which you have subscribed. Value is either:SONET (if the user only has SONET service)MON (if the user only has MON service)SONET/MON (if the user has both SONET and MON services)

2 Time when online detection was activated.3 Time when the last duration period started.4 If an alarm has been detected as of the duration time, “Yes” appears

here as a link. Clicking this link presents you with the “Alarm Window” page as shown in Figure 4-34. If no alarm has been detected, “No” appears here as plain text.

5 Remaining time in the current duration period.6 Clicking on the “RESTART” button restarts the duration period. Item

#5 is reset to the duration setting. 7 Clicking on the “STOP” button stops the online fault detection

altogether. A confirmation pop-up window is displayed to close the online detection window.

8 Clicking on the “SETTINGS” button invokes the “Detection Settings” screen as shown in Figure 4-32.

Table 4-18: Elements of Detection Status

4.8.3 Alarm Window

The Alarm window is automatically displayed when online detection is activated (Online Detection window is up) and when either one of the

75- 75 -75-

75 -- 75 -


following occurs: 1) a new fault event is detected or 2) when the “Yes” link in the Online “Detection Status” window is clicked ( Item 4).

Figure 4-34: Alarm Window – No Acknowledgement

Item

Description

1 This indicates the type of technology to which you have subscribed. Value is either:SONET (if the user only has SONET service)MON (if the user only has MON service)SONET/MON (if the user has both SONET and MON services)

2 Clicking on the “Acknowledge Alarm” link, turns off the sound (if on) and imposes an “OK” message on top of the blue alarm as shown in Figure 4-35.

3 Clicking on the “View History” link invokes the “Alarm and Event History” screen.

4 If the audible alarm setting is set to on, the siren will sound off, and this check box will be available. If this check box is selected, the siren will be turned off. If the audible alarm setting is set to off, this check box will be disabled.

5 The siren icon will spin until the alarm has been acknowledged.Table 4-19: Elements of Alarm Window

76- 76 -76-

76 -- 76 -

2

3

15

4


Figure 4-35: Alarm Window – Acknowledged

77- 77 -77-

77 -- 77 -


4.9 Notification Settings4.9.1 Accessing Notification SettingsTo access the “Notification Settings” screen:

Click on the “Notification Settings” link in the Toolbar. Click on the “Notification Settings” link in the Site Map

4.9.2 Using Notification SettingsThe Notification Settings feature allows the user to specify fault notification settings for an alphanumeric pager and email, such as trigger counters (count at which an alphanumeric pager/email will be sent out). Numeric only pagers are not supported.

Figure 4-36: Notification SettingsItem Description1 User Login ID.

78- 78 -78-

78 -- 78 -

1

4

8

5

11 12

7

13

14

1618

19

20

17

15

6

2 3 9 10


2 Clicking on the "Up Arrow" sorts the list of alarm types in ascending order based on that sorting parameter.The sorting parameters provided are "Alarm Type" and “Network Level”. If no sorting parameter is specified, the page is sorted by ascending “Network Level” and then by ascending "Alarm Type".

3 Clicking on the "Down Arrow" sorts the list of alarm types in descending order based on that sorting parameter.The sorting parameters provided are "Alarm Type" and “Network Level”.

4 Alarm Description. This is color-coded based on the severity level of the alarm. Critical – Red Major – Amber Minor – Yellow

5 Alarm Network Level.6 Alarm type notification trigger counter. Pre-populated with the current

setting in the database. Valid values are from 0-99.7 Click on a “+” button to increment the notification trigger counter by

one.8 Click on a “-” button to decrement the notification trigger counter by

one.9 Checking this checkbox will automatically check all the email

checkboxes. Un-checking this checkbox will automatically un-check all the email checkboxes. This checkbox is initially unchecked.

10 Checking this checkbox will automatically check all the pager checkboxes. Un-checking this checkbox will automatically un-check all the pager checkboxes. This checkbox is initially unchecked.

11 When an email checkbox is clicked, an email notification will be sent to the specified email address in Item #8 whenever that particular alarm type has reached the trigger counter.

12 When a pager checkbox is clicked, a pager notification will be sent to the specified alpha pager address in Item #9 whenever that particular alarm type has reached the trigger counter.

13 Email address to send a notification to.14 Alpha pager address to send a notification to.15 Dropdown box containing the 24 hours of the day. The user can select

the time of day when pager notifications should start to be sent. 16 Dropdown box containing the 24 hours of the day. The user can select

up the time of day when pager notifications should stop being sent. 17 This is a dropdown box containing the following time zones: CT,

ET, MT, and PT. The user can select the time zone when pager

79- 79 -79-

79 -- 79 -


notifications should start to be sent. 18 Clicking the “SUBMIT” button displays a confirmation pop-up window

for your acknowledgement to proceed with the database update of the new values.

19 Clicking the “TEST PAGER” button sends a sample pager notification to the alpha pager address specified in Item #9.

20 Clicking the "RESET" button reloads this page with the current notification settings in the database.

Table 4-20: Elements of Notification Setting

80- 80 -80-

80 -- 80 -


5 Performance ManagementThe purpose of Performance Management is to assist AT&T customers in monitoring and measuring performance of their circuits. In the initial phase CNM will ONLY include Dedicated SONET and SONET over MON services. The next release will encompass both dedicated and non-dedicated services. Therefore all the screen shots displayed in this guide are ONLY for dedicated services.

While AT&T monitors performance of the SONET/MON network at various levels, CNM for SONET/MON measures performance at Network, Ring and Circuit level.

Network level performance measurements provides information on the network conditions and performance history.

SONET (or SONET over MON) Ring level provides Node attributes, Topology. and other Ring level SONET performance services (including SONET services riding over MON).

Circuit level measurements include circuit speed, Circuit ID, Alias etc. The measurements are only at the optical level from the highest carrier (for example OC-192) down to riding services (for example DS3 and DS1)

Details of above performance metrics are explained further in the following sections, where appropriate. The acronyms and terminology used by CNM is explained in Section 8 SONET/MON Definitions and Acronyms

5.1 Accessing Performance Management Users can access Performance Management by clicking on the

“Performance Management” link on the toolbar Users can access Performance Management by clicking on the “Circuit

Performance Table” link on the toolbar or “site map”.

81- 81 -81-

81 -- 81 -


5.2 How Performance Management Is UsedThe purpose of Performance Management is to assist AT&T Customers in managing and tracking the various elements of the network. Customers can oversee the performance of Network.

Figure 5-37: Performance Management Access via the Toolbar

The explanation of the data elements of each illustration is given in the associated table

.

82- 82 -82-

82 -- 82 -

Click on “Performance Management”.


5.2.1 Terminology used in CNM Performance Management

0 Term 0 SONET/MON Definition Line A transmission medium, together with the associated Line

Terminating Equipment (LTE), required to provide the means of transporting information between two consecutive line terminating network elements, one of which originates the line signal and the other terminates the line signal.

Path A path at a given bit rate is a logical connection between the point at which a standard frame format for the signal at the given bit rate is assembled, and the point at which the standard frame format for the signal is disassembled

Section The portion of a transmission facility, including terminating points, between (i) a terminal network element and a regenerator or (ii) two regenerators. A terminating point is the point after signal regeneration at which performance monitoring is (or may be) done.

0 Circuit Identifier

0 This is a character string specified by the circuit vendor, and is useful when communicating with the vendor during the troubleshooting process.

1 SCID 1 SONET Carrier IDentifier, or SCID provides a unique identification of all equipment and facility network elements associated with a particular SONET network.

0 TID 2 For interoperability with other vendors’ network elements, all TL1 commands must include the target identifier (TID) as a mandatory parameter.

Table 5-21: Performance Terms

83- 83 -83-

83 -- 83 -


5.3 Circuit Performance Table – Network Level

5.3.1 Accessing the Circuit Performance Table – Network Level:

Click on “Performance Management“ in the toolbar if it is Network Level Click on “Circuit Performance Table” in the toolbar or Site Map

5.3.2 Using the Circuit Performance Table – Network Level:The Circuit Performance Table displays the performance details of a CNM SONET/MON subscriber’s circuits for dedicated services.

84- 84 -84-

84 -- 84 -

8

12

3 4

65

7

9

12

11

10

13


Figure 5-38: Circuit Performance Table – Network Level

85- 85 -85-

85 -- 85 -


Item Description1 SONET/MON user’s ID.2 User’s business name and location. Location consists of street

number and name, city, and state.3 Clicking on the "Up Arrow" or the "Down Arrow" links retrieves

and views additional Circuits. The default presentation is 30 circuits per page. Clicking on the "Up Arrow" link will display the previous set of circuits under the network. Clicking on the "Down Arrow" link will display the next set of circuits under the network. These links are also available at the bottom of this page if there is more than one page.If the user is viewing the first set of circuits, the "Up Arrow" link will be disabled. If the user is viewing the last set of circuits, then the "Down Arrow" link will be disabled. If all the circuits can be shown in one page, both links will be disabled

4 Start and end count of circuits displayed in the page and the total number of circuits.

5 Origination Target ID (TID) - where the circuit originates from Network Element or Node.

6 Clicking on the "Up Arrow" sorts the list of circuits in ascending order.The sorting parameters provided are “Origination TID”, "Circuit ID", "Circuit Alias", “SONET Rate”, “Destination TID” and “Alarm Level”. If no sorting parameter is specified, the table is sorted in descending order of Alarm Level and then Circuit ID.

7 Circuit ID, Circuit Alias and SONET Rate of the circuit.Displays all the circuits belonging to this user.

8 Clicking on the "Down Arrow" sorts the list of circuits by descending order.The sorting parameters provided are “Origination TID”, "Circuit ID", "Circuit Alias", “SONET Rate”, “Destination TID” and “Alarm Level”.

9 Destination Target ID (TID) where the circuit got terminated from Network Element or Node.

10 Drop down with list of Networks available for the user. User can choose a Network ID to retrieve the circuits under that particular Network. Default report criteria will be “All” Networks.

86- 86 -86-

86 -- 86 -


11 Drop down with list of available reporting options. See Table 5-23: for detailed description

12 Drop down with list of available graph options. See Table 5-24: for detailed description

13 Alarm’s severity level for the particular circuit will be displayed. The text is color-coded based on the severity level of the event type.

Critical – Red Major – Amber Minor – Yellow Normal - Green

14 If there are more than 60 circuits to be displayed, a dropdown box is displayed which allows the user to select the range of circuits to view (in 30 circuit Increments). This dropdown box will also be available at the bottom of this page.


Table 5-22: Elements of Circuit Performance Table – Network Level

87- 87 -87-

87 -- 87 -


Report Name DescriptionSelecting Path- Near End Interval Report

Display Near End Interval Stats for a Path layer starting from midnight to the last 15 min for a selected circuit. Please see Figure 5-43

Selecting Path- Far End Interval Report

Display Far End Interval Stats for a Path layer starting from midnight to the last 15 Min for a selected circuit. Please see Figure 5-43

Selecting Line- Near End Interval Report

Display Near End Interval Stats for a Line layer starting from midnight to the last 15 Min for a selected circuit. Please see Figure 5-43

Selecting Line- Far End Interval Report

Display Far End Interval Stats for a Line layer starting from midnight to the last 15 Min for a selected circuit. Please see Figure 5-43

Selecting Section- Interval Report

Display Interval Stats for a Section layer starting from midnight to the last 15 Min for a selected circuit. Please see Figure 5-44

Table 5-23: Circuit Performance Reports

88- 88 -88-

88 -- 88 -


Graph Name DescriptionSelecting Path -Current Graph

Display the graph and stats for a Path for Near end and Far end for the last 15 Min . Please see Figure 5-42

Selecting Path -Hourly Line Graph

Display the Hourly Line Graph for Path for Near end and Far end. Default date is for previous day. Please see Figure 5-46

Selecting Path- Daily Graph

Display the Daily Graph for Path for Near end and Far end. Default date is the previous week ending date. Please see Figure 5-47.

Selecting Path-Weekly Trend Graph

Display the Weekly Trend Graph for Path for Near end and Far end for previous 26 weeks. Please see Figure 5-48

Selecting Line -Current Graph

Display the graph and stats for Line for Near end and Far end for the last 15 Min. Please see Figure 5-42

Selecting Line -Hourly Line Graph

Display the Hourly Line Graph for Line for Near end and Far end. Default date is for previous day. Please see Figure 5-46

Selecting Line- Daily Graph

Display the Daily Graph for Line for Near end and Far end. Default date is the previous week ending date. Please see Figure 5-47

Selecting Line-Weekly Trend Graph

Display the Weekly Trend Graph for Line for Near end and Far end for previous 26 weeks. Please see Figure 5-48

Selecting Section -Current Graph

Display the graph and stats for Section for last 15 Min. Please see Figure 5-45

Selecting Section -Hourly Line Graph

Display the Hourly Line Graph for Section. Default date is for previous day. Please see Figure 5-46

Selecting Section - Daily Graph

Display the Daily Graph for Section. Default date is the previous week ending date. Please see Figure 5-47

Selecting Section -Weekly Trend Graph

Display the Weekly Trend Graph for Section for previous 26 weeks. Please see Figure 5-48

Table 5-24: Circuit Performance Graphs

89- 89 -89-

89 -- 89 -


5.4 Circuit Performance Table – SONET over MON Level

5.4.1 Accessing the Circuit Performance Table – SONET over MON Level :

Click on “Performance Management“ in the toolbar if SONET over MON level

5.4.2 Using the Circuit Performance Table – SONET over MON Level :

Through this feature, The MON user will be able to choose and display SONET over MON statistics for their dedicated circuits.

Figure 5-39: Circuit Performance Table – SONET over MON

90- 90 -90-

90 -- 90 -

1

2

3 46 8

5 7

9

10

11

12


91- 91 -91-

91 -- 91 -


Item Description1 SONET/ MON user’s user ID2 Network ID, MON Ring ID and Ring Alias. Clicking the Network ID

link invokes Circuit performance table for that particular network as shown in Figure 5-39.

3 Clicking on the "Up Arrow" or the "Down Arrow" links retrieves and views additional Circuits. The default presentation is 30 circuits per page. Clicking on the "Up Arrow" link will display the previous set of circuits for the Ring. Clicking on the "Down Arrow" link will display the next set of circuits for the Ring. These links are also available at the bottom of this page if there is more than one page.If the user is viewing the first set of circuits, the "Up Arrow" link will be disabled. If the user is viewing the last set of circuits, then the "Down Arrow" link will be disabled. If all the circuits can be shown in one page, both links will be disabled


5 Origination Target ID (TID) where the circuit Originates from Network Element or Node

6 Clicking on the "Up Arrow" sorts the list of circuits in ascending order.The sorting parameters provided are “Origination TID”, "Circuit ID", "Circuit Alias", “SONET Rate”, “Destination TID” and “Alarm Level”. If no sorting parameter is specified the table is sorted in descending order of Alarm Level and then Circuit ID.

7 Circuit ID, Circuit Alias and SONET Rate of the circuit.Displays all the circuits under the MON Ring.


9 Destination Target ID (TID) where the circuit got terminated Network Element or Node.

92- 92 -92-

92 -- 92 -


10 Drop down with list of available reporting options. See Table 5-23 for detailed description

11 Drop down with list of available graph options. See Table 5-24 for detailed description


Critical – Red Major – Amber Minor – Yellow Normal - Green



Table 5-25: Elements of Circuit Performance Table – SONET over MON

93- 93 -93-

93 -- 93 -


5.5 Circuit Performance Table – SONET Ring Level

5.5.1 Accessing the Circuit Performance Table – SONET Ring Level:

Click on “Performance Management“ in the toolbar if it is at SONET Ring level.

5.5.2 Using the Circuit Performance Table – SONET Ring Level:

Through this feature, SONET user will be able to choose and display SONET Ring statistics for their circuits.

Figure 5-40: Circuit Performance Table – SONET Ring Level

05/18/23 PROPRIETARY INFORMATIONNot for use or disclosure outside AT&T Operations, Inc. Except under written


94 -- 94 -

12

3 4

7

6 8 9

10

5 11

12


05/18/23 PROPRIETARY INFORMATIONNot for use or disclosure outside AT&T Communications, Inc. Except under written


95 -- 95 -


Item Description1 SONET/ MON user’s user ID.2 Network ID, Ring ID and Ring Alias. Clicking the Network ID link

invokes Circuit performance table for that particular network as shown in Figure 5-40.

3 Clicking on the "Up Arrow" or the "Down Arrow" links retrieves and views additional Circuits. The default presentation is 30 circuits per page. Clicking on the "Up Arrow" link will display the previous set of circuits for the Ring. Clicking on the "Down Arrow" link will display the next set of circuits for the Ring. These links are also available at the bottom of this page if there is more than one page.If the user is viewing the first set of circuits, the "Up Arrow" link will be disabled. If the user is viewing the last set of circuits, then the "Down Arrow" link will be disabled. If all the circuits can be shown in one page, both links will be disabled


5 Origination Target ID (TID) where the circuit originates from Network Element or Node

6 Clicking on the "Up Arrow" sorts the list of circuits in ascending order.The sorting parameters provided are “Origination TID”, "Circuit ID", "Circuit Alias", “SONET Rate”, “Destination TID” and “Alarm Level”. If no sorting parameter is specified the table is sorted in descending order of Alarm Level and then Circuit ID.

7 Circuit ID, Circuit Alias and SONET Rate of the circuit.Displays all the circuits under the SONET Ring.


9 Destination Target ID (TID) where the circuit got terminated Network Element or Node.

96- 96 -96-

96 -- 96 -


10 Drop down with list of available reporting options. See Table 5-23 for detailed description

11 Drop down with list of available graph options. See Table 5-24 for detailed description


Critical – Red Major – Amber Minor – Yellow Normal – Green



Table 5-26: Elements of Circuit Performance Table – SONET Ring Level

97- 97 -97-

97 -- 97 -


5.6 Circuit Performance Table – Circuit Level

5.6.1 Accessing the Circuit Performance Table – Circuit Level:

Click on “Performance Management“ in the toolbar if it is at circuit level.

5.6.2 Using the Circuit Performance Table– Circuit Level:Through this feature, SONET user will be able to choose and display performance statistics for their circuits.

Figure 5-41: Circuit Performance Table – Circuit Level

98- 98 -98-

98 -- 98 -

1

3 4

2

6

75

8

9

10


Item Description1 SONET/MON user’s user ID.2 Network ID, Ring ID, Ring Alias and TID . Clicking the Network ID link

invokes Circuit performance table for that particular network as shown in Figure 5-39 or Figure 5-40. Clicking on the Ring ID link invokes Circuit Performance Table for that particular Ring as shown in Figure 5-41.

3 Clicking on the "Up Arrow" or the "Down Arrow" links retrieves and views additional Circuits. The default presentation is 30 circuits per page. Clicking on the "Up Arrow" link will display the previous set of circuits for the Node. Clicking on the "Down Arrow" link will display the next set of circuits for the Node. These links are also available at the bottom of this page if there is more than one page.If the user is viewing the first set of circuits, the "Up Arrow" link will be disabled. If the user is viewing the last set of circuits, then the "Down Arrow" link will be disabled. If all the circuits can be shown in one page, both links will be disabled


5 Clicking on the "Up Arrow" sorts the list of circuits in ascending order.The sorting parameters provided are "Circuit ID", "Circuit Alias", “SONET Rate” and “Alarm Level”. If no sorting parameter is specified the table is sorted by Alarm level starting from Critical to Normal and Circuit ID.

6 Circuit ID, Circuit Alias and SONET Rate of the circuit.Displays all the circuits under a Node.

7 Clicking on the "Down Arrow" sorts the list of circuits by descending order. The sorting parameters provided are "Circuit ID", "Circuit Alias", “SONET Rate” and “Alarm Level”.

99- 99 -99-

99 -- 99 -


8 Drop down with list of available reporting options. Refer to Table5-23 for a list of options.

9 Drop down with list of available graph options. Refer to Table 5-24 for a list of options .

10 Alarm’s severity level for the particular circuit will be displayed. The text is color-coded based on the severity level of the event type. Critical – Red Major – Amber Minor - Yellow Normal - Green



Table 5-27: Elements of Circuit Performance Table – Circuit Level

100- 100 -100- 100 -

-


5.7 Line / Path - Near End and Far End Current Performance Stats

5.7.1 Accessing the Line / Path - Near End and Far End Current Performance Stats: User selects Path- Current Graph from the Graphs dropdown under

“Reports and Graphs” for a particular circuit on Circuit Performance Table User selects Line - Current Graph from the Graphs dropdown under

“Reports and Graphs” for a particular circuit on Circuit Performance Table

5.7.2 Using the Line / Path - Near End and Far End Current Performance Stats:

Through this feature CNM User can view the Near End and Far End Line / Path Current Stats for the last 15 minutes in both graphical (histogram) and tabular format.

101- 101 -101- 101 -

-


Figure 5-42: Path Current Graph

102- 102 -102- 102 -

-

2

4

1

3

12

5 6 7 8 9 10 11


Item Description1 Graph title “Path Current Graph”. “Line Current Graph” title will be

displayed for Line Current Graph.2 Header Information:

Report Date Circuit ID Circuit Alias SONET Rate Near End Ring Far End Ring Near End TID Far End TID Near End Circuit Address Far End Circuit Address

3 Graph Plotting the Near End and Far End for all the stats.4 Stats for Near End and Far End5 Time in hours and minutes6 CV- Coding Violation 7 ES- Errored Seconds8 FC- Failure Counts9 SES- Severely Errored Seconds10 SEFS- Severely Errored Framing Seconds11 UAS- Unavailable Seconds12 Clicking the “REFRESH” button will generate the graph for the last

15 minutes if it is available.Table 5-28: Elements of Path Current Graph

103- 103 -103- 103 -

-


5.8 Line / Path - Near End and Far End Interval Performance Stats

5.8.1 Accessing the Line / Path - Near End and Far End Interval Performance Stats:

User selects Near end or Far end path Interval reports from Reports dropdown under “Reports and Graphs” column for a particular circuit on Circuit Performance Table.

User selects Near end or Far end Line Interval reports from Reports dropdown under “Reports and Graphs” column for a particular circuit on Circuit Performance Table.

5.8.2 Line / Path - Near End and Far End Interval Performance Stats:

CNM User can view the Near End and Far End Path Interval Stats starting at midnight to the last 15 minutes.

104- 104 -104- 104 -

-


105- 105 -105- 105 -

-

3

1

2

4 5 6 7 8 9


Figure 5-43: Path Near End Interval Report

106- 106 -106- 106 -

-


Item Description1. Graph title “Path Near End Interval Report”.

“Path Far End Interval Report” title will be displayed for Path Far End Interval Stats.“Line Near End Interval Report” title will be displayed for Line Near End Interval Stats.“Line Far End Interval Report” title will be displayed for Line Far End Interval Stats.

2. Header Information. Report Date Circuit ID Circuit Alias SONET Rate Near End Ring Far End Ring Near End TID Far End TID Near End Circuit Address Far End Circuit Address

3. Time in hours and minutes

4. CV- Coding Violation

5. ES- Errored Seconds

6. FC- Failure Counts

7. SES- Severely Errored Seconds

8. SEFS- Severely Errored Framing Seconds

9. UAS- Unavailable Seconds

Table 5-29: Elements of Line / Path - Near End and Far End Interval Performance Report

107- 107 -107- 107 -

-


5.9 Section Interval Report

5.9.1 Accessing the Section Interval Report:User selects Section Interval Report from Reports dropdown under Reports and Graphs column for a particular circuit on Circuit Performance Table.

5.9.2 Using the Section Interval Report:CNM User can view the Section Interval Stats for a particular circuit.

108- 108 -108- 108 -

-


109- 109 -109- 109 -

-

3

1

2

4 5 6 7 8 9


Figure 5-44: Section Interval Report

110- 110 -110- 110 -

-


Item Description1. Graph title “Section Interval Report”. 2. Header Information:-

Report Date Circuit ID Circuit Alias SONET Rate Near End Ring Far End Ring Near End TID Far End TID Near End Circuit Address Far End Circuit Address








Table 5-30: Elements of Section Interval Report

111- 111 -111- 111 -

-


5.10 Section Current Graph

5.10.1 Accessing the Section Current Graph:User selects “Section Current Graph” from “Graphs” dropdown under “Reports and Graphs” column for a particular circuit on Circuit Performance Table

5.10.2 Using the Section Current Graph:CNM User can view the Section Current Stats for the last 15 minutes.

112- 112 -112- 112 -

-


Figure 5-45: Section Current Graph

113- 113 -113- 113 -

-

2

4

1

3

11

5 6 7 8 9 10


Item Description1. Graph title “Section Current Graph”.

2. Header Information:- Report Date Circuit ID Circuit Alias SONET Rate Near End Ring Far End Ring Near End TID Far End TID Near End Circuit Address Far End Circuit Address

3. Graph Plotting the stats.








11. Clicking the “REFRESH” button will generate the graph for the last 15 minutes if available.

Table 5-31: Elements of Section Current Graph

114- 114 -114- 114 -

-


5.11 Circuit Hourly Line Graph

5.11.1 Accessing the Circuit Hourly Line Graph: Click on “Generate Report” link on the Circuit Hourly Line Graph. CNM user accesses the graph from the Circuit Performance Table. CNM User has selected to generate the “Circuit Hourly Line” report in the

Circuit Reports page

5.11.2 Using Circuit Hourly Line Graph:Display the circuit reports page with parameters for Circuit Hourly Line Graph.

115- 115 -115- 115 -

-


Figure 5-46: Circuit Hourly Line Graph

116- 116 -116- 116 -

-

3

2

9

5

4

6

78

1


Item Description1 Graph title “Circuit Hourly Line Graph”.

2 Header Information. Report Date Circuit ID Circuit Alias SONET Rate Near End Ring Far End Ring Near End TID Far End TID Near End Circuit Address Far End Circuit Address

3 Hourly Graph for the date, Circuit Layer and statistic specified by the user. Default date to generate the graph is yesterday’s date. Default Circuit Layer to generate the graph is Path, and default statistics to generate the graph is Coding Violation. For Section layer and BER stat, Graph will be plotted for a circuit, not for end points.

4 When the “Download” link is clicked, a new window appears with the raw data used to generate the graph. See Figure 5-49

5 Clicking on the "Back Arrow" or the "Forward Arrow" retrieves the Hourly Line graph for the previous or next day. The graph can only be generated for the last 14 days. If the user is viewing the graph for yesterday, the "Forward Arrow" is disabled. If the user is viewing the graph for the earliest date, then the "Back Arrow" link is disabled.

6 Dropdown list of the last 14 days. Users can select a new report date.

7 Dropdown list with the Circuit Layer types. Values are: Path Line Section Physical

117- 117 -117- 117 -

-


The default value is Path. CV, ES, SES, etc. exists at Section, Line and Path layers. BER (Bit error ratio – the ratio of the bits in error to the total number of bits received) is measured on the physical layer level.

8 Dropdown list of the statistic types that can be used to re generate the graph. Coding Violation Errored Seconds Failure Count Severely Errored Seconds Severely Errored Framing Seconds Unavailable Seconds Bit Error RatioThe default value is Coding Violation.

9 Click “GENERATE REPORT” button to re-generate the report based on the new report date, Circuit Layer and statistics specified in Items #6 - #8.

Table 5-32: Elements of Circuit Hourly Line Graph

118- 118 -118- 118 -

-


5.12 Circuit Daily Graph

5.12.1 Accessing the Circuit Daily Graph: Click on the “Generate Report” link on the Circuit Daily Graph. CNM user accesses the graph from the Circuit Performance

Table. CNM User has selected to generate the “Circuit Daily Graph”

report in the Circuit Reports page.

5.12.2 Using the Circuit Daily Graph:Display the circuit reports page with parameters for Circuit Daily Graph:

119- 119 -119- 119 -

-


120- 120 -120- 120 -

-

6

9

8

7

5

2

3

4

1


Figure 5-47: Circuit Daily Graph

121- 121 -121- 121 -

-


Item Description1 Graph title “Circuit Daily Graph”.


3 Daily Graph for the week ending date, Circuit Layer and statistic specified by the user. Default date to generate the graph is previous week’s week ending date. Default Circuit Layer to generate the graph is Path and Default Statistic to generate the graph is Coding Violation. For Section layer and BER stat Graph will be plotted for a circuit, not end points.

4 When the “Download” link is clicked, a new window appears with the raw data used to generate the graph. See Section Figure 5-49.

5 Clicking on the "Back Arrow" or the "Forward Arrow" retrieves the Daily graph for the previous or next week. The graph can only be generated for the last 2 completed weeks. If the user is viewing the graph for the previous week the "Forward Arrow" is disabled. If the user is viewing the graph for the week before that then the "Back Arrow" link is disabled.

6 Dropdown list of the last 2 week ending dates. 7 Dropdown list with the Circuit Layer types. Values are:

Path, Line, Section and PhysicalThe default value is Path. CV, ES, SES, etc. exists at Section, Line and Path layers. BER (Bit error ratio – the ratio of the bits in error to the total number of bits received) is measured on the physical layer level.

8 Dropdown list of the statistic types can be used to re-generate the

122- 122 -122- 122 -

-


graph : Coding Violation Errored Seconds Failure Count Severely Errored Seconds Severely Errored Framing Seconds Unavailable Seconds Bit Error Ratio

The default value is Coding Violation.9 Clicking “GENERATE REPORT” button to re-generate the report

based on the new report date, Circuit Layer, and statistic specified.Table 5-33: Elements of Circuit Daily Graph

5.13 Line / Path - Weekly Trend Graph

5.13.1 Accessing the Circuit Weekly Trend Graph: Click on the “Generate Report” link on the Circuit Weekly Trend CNM user accesses the graph from the Circuit Performance Table CNM User has selected to generate the “Circuit Weekly Trend”

report in the Circuit Reports page

5.13.2 Using the Circuit Weekly Trend Graph:Display the circuit reports page for Circuit Weekly Trend. The graph shows the minimum, maximum, and median values. It also shows the value at the 1st (25%) and 3rd (75%) quartile.

123- 123 -123- 123 -

-


124- 124 -124- 124 -

-

2

3

6

7

4

8

5

9

1


Figure 5-48: Circuit Weekly Trend Graph

125- 125 -125- 125 -

-


Item Description1 Graph title “Circuit Weekly Trend Graph”.


3 Weekly Graph generated for Line / Path Near End for the Circuit Layer and statistic specified by the user. The past 26 weeks data is displayed. The Default Circuit Layer to generate the graph is Path Default Statistic to generate the graph is Coding Violation. The graph shows the minimum, maximum, and median values. It also shows the value at the 1st (25%) and 3rd (75%) quartile.

4 When the “Download” link is clicked, a new window appears with the raw data used to generate the graph for the Near End Stats. See Section Figure 5-49.

5 Weekly Graph generated for Line / Path Far End for the Circuit Layer and statistic specified by the user. The past 26 weeks data is displayed. The default Circuit Layer to generate the graph is Path and default statistics to generate the graph is Coding Violation The graph shows the minimum, maximum, and median values. It also shows the value at the 1st (25%) and 3rd (75%) quartile.

6 When the “Download” link is clicked, a new window appears with the raw data used to generate the graph for the Far End Stats.

7 Dropdown list with the Circuit Layer types Values are: Path, Line, Section and Physical

The default value is Path. CV, ES, SES, etc. exists at Section, Line and Path layers. BER (Bit error ratio – the ratio of the bits in error to the total number of bits received) is measured on the physical layer level.

126- 126 -126- 126 -

-


8 Dropdown list of the statistic types can be used to re-generate the graph

Coding Violation Errored Seconds Failure Count Severely Errored Seconds Severely Errored Framing Seconds Unavailable Seconds Bit Error Ratio

The default value is Coding Violation.9 Clicking “GENERATE REPORT” button to re-generate the report

based on the new statistic specified.Table 5-34: Elements of Weekly Trend Graph

127- 127 -127- 127 -

-


5.14 Downloading Data In Performance Management

The user can capture and download raw performance data using the “Download” feature (Figure 5-49). This feature presents raw data in a simple frame of rows and columns of data, as shown in Figure 5-50.

Figure 5-49: Download Option

To capture downloaded data in a spreadsheet program, follow these steps:

Click on the “Download” link on the original graph. Highlight all of the data that is needed, then right-click the data and

select “copy”. Paste the contents into the desired file.

128- 128 -128- 128 -

-


Figure 5-50: Raw Data from a Hourly Line Graph

5.15 Circuit Reports

5.15.1 Accessing Circuit Reports

Click on the “Circuit Reports” link under “Performance Management “in the SONET/MON toolbar to invoke the “Circuit Reports” screen.

5.15.2 Using Circuit Reports

Detailed analysis on circuits can be performed by using the graphs (“Circuit Hourly Line Graph”, “Circuit Daily Graph”, and “Circuit Weekly Trend Graph”) available for individual circuits. The navigation to these

129- 129 -129- 129 -

-


graphs for any circuit can be easily done from the “Circuit Reports” screen as shown in Figure 5-51.

To generate a report, first select a Report Type , then select the Circuit ID and other Report Parameters associated with the Report Type (as shown in Step 1 and 2 below). When all parameters have been selected, click the “Generate Report” button.

Figure 5-51: Circuit Reports

Item

Description

1 User ID for SONET/MON.2 Report Type Selection.

If Circuit Hourly Line is selected, Figure 5-46 will be displayed.

If Circuit Daily Graph is selected, Figure 5-47 will be displayed.

If Circuit Weekly Trend is selected, Figure 5-48 will be

130- 130 -130- 130 -

-

Step 2. Establish necessary report parameters.

.Step 1. Select the report type.

.

1

4

5

3

2


Item

Description

displayed.3 Provides a dropdown list of all the circuits associated with your

User ID. Circuit ID’s will be populated in the order of the severity levels of the Alarms pertaining to the circuit.

4 Dropdown lists of parameters required by the “Report Type” selected.

5 Clicking on the generate button executes the selected report (example, “Circuit Summary”) based on the selected parameters.

Table 5-35: Elements of Circuit Reports

131- 131 -131- 131 -

-


6 The Toolbar6.1 CNM Home Page Toolbar Functions

When the user enters URL address – www.fastrakview.com, the user will be presented with the CNM Home Page screen with the toolbar as shown in Figure 6-52.

Figure 6-52: CNM Application Home Page Toolbar

132- 132 -132- 132 -

-

http://www.fastrakview/


Link DescriptionAn existing or new CNM for SONET/MON customer, will launch the application by clicking on the “SONET/MON” link below “User Login”. The user will be presented with the application “Authentication” screen as shown in Figure 2-2.An existing or new CNM for SLA Tracking customer, will launch the application by clicking on the “ATM/Frame Relay” link below “SLA Tracking”. The user will be presented with the application “Authentication” screen as shown in Figure 2-2.Customers who have not subscribed to CNM can view a demonstration of the ATM or Frame Relay application by clicking on the “ATM” or “Frame Relay” link below “Demo Login”. The user will be presented with the application “Authentication” screen as shown in Figure2-2.Clicking on the “Take the Tour” link will invoke the CNM for ATM/Frame Relay Online Web Tour.Clicking on the “Browser Settings” link will invoke the “Browser Settings” screen as shown in Figure 6-53. The “Browser Settings” screen displays the required browser settings for accessing the CNM application.Clicking on the “Contact Us” link will invoke the “Contact Us” screen as shown in Figure 6-54. The “Contact Us” screen provides customers with information about contacting the CNM website customer support.

Table 6-36: Elements of CNM Application Toolbar

133- 133 -133- 133 -

-


Figure 6-53: Browser Settings

134- 134 -134- 134 -

-


Figure 6-54: Contact Us (Unsecured)

135- 135 -135- 135 -

-


6.2 CNM for SONET/MON Application Toolbar Functions

After successful authentication, the user will be presented with the “Network Map” screen as shown in Figure 3-6 with the SONET/MON application toolbar. From the toolbar the user can click on any link to easily navigate to the appropriate screen.

Figure 6-55: Toolbar for CNM SONET/MON Application

Link DescriptionClicking the “Home” link will take the user to the CNM Home Page.

This is static text showing which application the user is logged into.

136- 136 -136- 136 -

-


Link Description

Clicking the “Configuration Management” link will invoke the “Network Map” screen as shown in Figure 3-6.

Clicking the “Fault Management” link will invoke the “Network Outages” screen. The user will be presented with one of the following options: Network Outages Alarm and Event History Detection Status Detection Settings Notification Settings

137- 137 -137- 137 -

-


Link Description

Clicking the “Performance Management” link will invoke the “Circuit Perf. Table” screen as shown in Figure 5-38. The user will be presented with the following options:

Circuit Perf. Table Circuit Reports

Clicking on the “Security Management” link will invoke the “Change Password” screen and the user will be presented with the “Change Password” link in the expanded toolbar.Clicking on “Logout” terminates the user session.

Clicking on “Site Map” will invoke the “Site Map” screen as shown in Figure 6-56. To navigate within the website, click on the “Site Map” link. On this single page, user’s will find links which enable them to go directly to the section or function that they need. (Usability tip: Some users like to use the Site Map as their Home Page so that they can move around the site more quickly).Clicking on the “User Guide” link will display a window containing instructions for downloading the User Guide. For convenience the User Guide is provided in PDF and Word Document formats.

138- 138 -138- 138 -

-


Link DescriptionClicking on the “Contact Us” link will invoke the “Contact Us” Screen as shown in Figure 6-57. The “Contact Us” screen provides customers with information about contacting the CNM for SONET/MON website customer support.

Table 6-37: Elements of Toolbar for CNM SONET/MON Application

Figure 6-56: Site Map Screen

139- 139 -139- 139 -

-


Figure 6-57: Contact Us (Secured)

Figure 6-58: User Guide

140- 140 -140- 140 -

-


7 If You Have More QuestionsYour comments and/or questions about CNM for SONET/MON application are always welcome! We invite you to contact us by sending an e-mail message to:

opticalCNM@AT&T.com

141- 141 -141- 141 -

-

mailto:[email protected]


8 SONET/MON Definitions and Acronyms

This document provides definitions for conditions that trigger alarms and events that occur in Nortel and Fujitsu SONET and MON equipment. The network vendors (Fujitsu and Nortel) may have more specific alarm and event names that differ somewhat from the values listed in the “Term” column below. This difference is due to the fact the Fujitsu and Nortel alarm and event names have been made generic in this document to capture the appropriate term that addresses the condition causing the alarm or event independent of the equipment manufacturer (Nortel or Fujitsu). Also, one alarm/event description in the table below may represent multiple vendor-specific alarm/event conditions where the vendor-specific alarm/events are very similar in nature.

The definitions provided in the table below are based on RFC standards and Nortel and Fujitsu equipment documentation. Changes and new versions to the Nortel and Fujitsu equipment supported by CNM will likely require upgrades to this document to ensure that it is synchronized with the alarms and events generated from the changed/modified equipment.

One of the criteria utilized in developing this list is whether or not an alarm/event condition has impacts at the circuit network level. However, it should be understood that many of the alarm/event conditions described below can occur at more than on network level (i.e. circuit, node, and ring level). Additionally, the level at which an alarm or event occurs has significance to the scope of network impact of the alarm or event.

142- 142 -142- 142 -

-


8.1 SONET/MON DefinitionsTerm SONET/MON (Both) Definitions Access Fail Communications between the shelf processor and at

least three circuit packs on the shelf over the maintenance bus (MBus) have been interrupted. Theinterruption can occur for any of the following reasons:• a defective shelf processor• a defective circuit pack on the MBus• a failed MBus on the backplane• a low voltage condition• a transient high voltage conditionThis alarm masks all circuit pack missing alarms, regardless of the type of circuit pack. It becomes active when the network element detects the condition. It clears when there are fewer than three circuit packs that have interrupted communications with shelf processor.

Circuit Pack Failed

The alarm results from one of the following:• The most likely cause is that the DS3 mapper or STS-1 interface circuit pack identified in the alarm failed.• You inserted a number of circuit packs at the same time into unprovisioned slots. In this case, the alarm should clear momentarily.• An OC-48 receiver, OC-48 demultiplexer, or OC-48 transmit interface is faulty.• Any one of DS3 or STS-1 input signals on the shelf is unterminated or marginal.

Specific to MONThe shelf processor has an internal failure that affects the synchronization messaging capability of the external synchronization interface (ESI) feature. This alarm applies only to the NT7E20GD, KA, and

143- 143 -143- 143 -

-


LA versions of the shelf processor. This alarm becomes active when the network element detects the condition. It clears when you replace the shelf processor.

144- 144 -144- 144 -

-


Circuit Pack Missing

This alarm becomes active for one of the following reasons:• The shelf slot is provisioned for a DS3 mapper or STS-1 interface circuit pack as indicated by the alarm, but the slot is empty. • The circuit pack is not properly engaged with the backplane connector.• There is an appropriate type of circuit pack in the slot, but the circuit packis defective.• There is a shelf processor failure.

This alarm masks the “Circuit pack mismatch” alarm. It is masked by the “SP MBus access fail” alarm.

Specific to MONThis alarm becomes active when the provisioned slot (20) does not contain an OSC circuit pack or the circuit pack is not seated in the slot.

Cooling Unit Failed/Missing

This alarm becomes active when the cooling unit is missing or has failed.

Download in progress

The OPC is currently downloading firmware or software to the flash code server. The alarm becomes active when the download begins. It clears automatically when the download is complete.

145- 145 -145- 145 -

-


Failure to lock The external synchronization interface (ESI) failed to lock on to a valid reference after 140 seconds in acquire mode. The possible causes are as follows:

• An ESI subunit circuit pack has failed.• The currently active timing reference has failed (excess wander).• The currently active timing reference is less than Stratum 3 in quality.• There is a forced switch to a failed reference.If the fault is active on one ESI subunit, the fault is most likely a failure of the subunit. If the fault is active on both ESI subunits, the fault is most probably a problem with the timing reference. This alarm is masked by the ESI “Subunit mismatch” alarm. The “Failure to lock” alarm clears when the subunit leaves acquire mode (whether into fast or freerun modes) or there is an automatic equipment or timing reference switch.In the case of a timing reference switch, the subunit remains in acquire mode, but the 140-second period starts again.

LOPPath - Loss of Pointer

A STS-Path LOP failure is declared when the STS-Path LOP defect persists for a period of 2.5 +/- 0.5 seconds. A STS-Path LOP failure is cleared when the STS-Path LOP defect is absent for 10 +/- 0.5 seconds.

LOPVT Loss of Pointer

A VT LOP defect is declared when either a valid pointer is not detected in eight consecutive VT superframes, or when eight consecutive VT superframes are detected with the NDF set to "1001" without a valid concatenation indicator. A VT LOP failure is declared when the VT LOP defect persists for 2.5 +/- 0.5 seconds. A VT LOP failure is cleared when the VT LOP defect is absent for 10 +/- 0.5 seconds.

146- 146 -146- 146 -

-


LOF Section Loss of Frame

The A1 and A2 bytes in the section overhead provide frame alignment by using a particular bit pattern. A receiving interface declares LOF after detecting errors in the framing pattern for three milliseconds. LOF is cleared when two consecutive valid A1/A2 framing patterns are received

147- 147 -147- 147 -

-


LOSLoss of Signal

A SONET link must see a certain number of digital bit transitions (from 1 to 0 and 0 to 1) to ensure proper synchronization. LOS is declared when no bit transitions are detected on the incoming signal (before descrambling) for 2.3 to 100 microseconds. The LOS defect is cleared after a 125 microsecond interval (one frame) during which no LOS defect is detected.

OPE Cold Restart This alarm becomes active when a cold restart of an 2x1000SX circuit pack occurs. It clears when a 15-minute timeout period elapses after the most recentcold restart or when another cold or warm restart occurs during the timeout period.

SP firmware update fail

The shelf processor was unable to back up the active firmware load to its redundant flash memory. Such a failure can occur when the flash memory isnearing its end of life. This alarm becomes active when the network element detects the condition. It clears when you replace the shelf processor.

Table 8-38: SONET/MON Definitions

148- 148 -148- 148 -

-


8.2 SONET Definitions Term SONET DefinitionsAIS Alarm Indicate Signal - Line

LAIS is sent by the section terminating equipment (STE) to alert the downstream line terminating equipment (LTE) that a LOS or LOF defect has been detected on the incoming SONET section. Upstream STE generates line AIS to downstream LTE by setting bits 6, 7, and 8 of the K2 byte to 111.

AISLine Alarm Indication Signal

Line Alarm Indication Signal (L-AIS) defect is detected as a "111" pattern in bits 6, 7, and 8 of the K2 byte in five consecutive frames. Line AIS defect is terminated when bits 6, 7, and 8 of the K2 byte do not contain the code "111" for five consecutive frames. A Line AIS failure is declared when the Line AIS defect persists for a period of 20.5 +/- 0.5 seconds. A Line AIS failure is cleared when the Line AIS defect is absent for 10 +/- 0.5 seconds.

AISVT Alarm Indication Status

VT-Path Alarm Indication Signal (AIS) is only applicable for VTs in the floating mode of operation. VT-Path AIS is used to alert the downstream VT Path Terminating Entity (PTE) of an upstream failure. A VT-Path AIS failure is declared when the VT-Path AIS defect persists for 2.5 +/- 0.5 seconds. A VT-Path AIS failure is cleared when the VT-Path AIS defect is absent for 10 +/- 0.5 seconds

Circuit pack mismatch

This alarm becomes active in the following circumstances:• A type of circuit pack other than a DS3 mapper or STS-1 interface occupies the slot provisioned for a DS3 mapper or STS-1 interface. For example, you removed the DS3 mapper or STS-1 interface and installedanother type of circuit pack in its place.• You removed and reseated the DS3 mapper or STS-1 interface circuit pack during a network element restart.

149- 149 -149- 149 -

-


• An STS-1 interface circuit pack occupies the protection slot (slot 16) of theprotection shelf of a multishelf 1:N systemThis alarm is masked by the “Circuit pack missing” alarm. It masks the “Circuit pack fail” and “Interface subunit 1/2/3 missing” alarms. It becomes active when the network element detects the condition. It clears when you install the correct circuit pack in the slot.

150- 150 -150- 150 -

-


Equipment protection switch complete

A switch from the working external synchronization interface (ESI) to the protection ESI successfully completed. The alarm becomes active when the protection switch completes. For automatic protection switches, it clears when the cause of the automatic protection switch clears. For forced switches and lockouts, it clears when you release the forced switch or lockout. For manual switches, it clears immediately after the manual switch completes.

Equipment protection switch fail

A protection switch from the active external synchronization interface (ESI) to the standby ESI failed.This alarm becomes active when the requested protection switch fails. It clears when the protection request drops or when a successful protection switchcompletes.

Interface carrier missing

An interface carrier circuit pack supporting DS3 or STS-1 tributary equipment is missing. For example, you removed an in-service circuit pack. The alarm might also become active because of a shelf processor failure.The interface carrier contains up to six interface port circuit packs (six DS3 or STS-1 tributary facilities). This alarm masks the “Interface subunit 1/2/3 missing” alarms for the interface port subunit circuit packs. It is masked by the “SP MBus access fail” alarm.The alarm becomes active when the network element detects the condition.

Interface subunit 1/2/3 missing

An interface port subunit circuit pack is not present in the carrier position associated with a provisioned DS3 mapper or STS-1 interface. These alarms might also become active because of a shelf processor failure.

151- 151 -151- 151 -

-


PDIPayload Defect Indication

A Payload Defect Indication Path alarm indicates a signal label mismatch failure SLMF. An invalid C2 byte in the SONET path overhead causes an SLMF. The C2 byte is the signal label byte. This byte tells the equipment what the SONET payload envelope contains and how it is constructed. It enables a SONET device to transport multiple types of services.

152- 152 -152- 152 -

-


Protection path fail

The protection-switching exerciser was unable to bridge traffic to the protection DS3 mapper or STS-1 interface circuit pack. This alarm can also become active after a completed protection switch or bridge if a problem existson the protection DS3 mapper or STS-1 interface, but not on the working DS3 mapper or STS-1 interface.The cause can be any of the following:

• a failed protection DS3 mapper or STS-1 interface circuit pack• a missing or out-of-service protection DS3 mapper or STS-1 interface circuit pack• any one of DS3 or STS-1 input signals on the shelf is marginal or faulty• a failed switcher circuit pack (suspect switcher 1 before switcher 2)• a failed switch controller circuit pack• a faulty OC-48 receive interface, OC-48 demultiplexer, or OC-48 transmit interface

Protection switch fail

A working DS3 mapper or STS-1 interface circuit pack attempted a protection switch, but failed. The working traffic could not access the protection bus.The cause can be any of the following:

• a failed protection DS3 mapper or STS-1 interface circuit pack• a missing or out-of-service protection DS3 mapper or STS-1 interfacecircuit pack• any one of DS3 or STS-1 input signals on the shelf is marginal or faulty• a failed switcher circuit pack (suspect switcher 1 before switcher 2)• a failed switch controller circuit pack

153- 153 -153- 153 -

-


• a failed working DS3 mapper or STS-1 interface circuit pack• a faulty OC-48 receive interface, OC-48 demultiplexer, or OC-48 transmitinterface

The alarm becomes active when the network element detects the condition.

RFILine Remote Failure IndicationPath Remote Failure IndicationVT Remote Failure Indication

The VT-Path RFI signal is only required for the case of byte synch mapped DS1s where the DS1 frame bit is not mapped. The VT-Path RFI is specified in ANSI T1.105, where it is currently called VT path yellow. When provided, the VT-Path RFI signal is used to indicate the occurrence of far-end failures. When the VT-Path RFI is not provided, far-end failures are derived from local timing of the VT-Path RDI defect. The VT-Path RFI failure is declared within 5 ms of detecting the incoming VT-Path RFI Signal. The VT-Path Remote Failure Indication (RFI) failure is cleared within 50 ms of detecting the removal of the incoming VT-Path RFI signal

STS1 protection unavailable, equipment OOS

The protection STS-1 interface is provisioned to be out of service. This alarm remains active during system operation to indicate that there is one or moreworking STS-1 interfaces in service, but there is no protection STS-1 interface provisioned. Therefore, STS-1 tributary protection is unavailable.

Subunit fail This alarm can become active for the following reasons:

• The external synchronization interface (ESI) circuit pack has failed.• The ESI carrier is faulty.• There is a failure on the active OC-48 transmit interface.

154- 154 -154- 154 -

-


This alarm is masked by the ESI “Subunit mismatch” alarm. It masks the “Timing generation entry to freerun”, “Timing generation entry to acquire”, “Timing generation entry to fast”, and “Timing generation entry to holdover”alarms. The alarm becomes active 1 0seconds after the network element detects the condition. It clears 20 seconds after you replace the failed subunit or the failurecondition clears. If the alarm results from a fault on an OC-48 transmit interface, the alarm clears if there is a protection switch to the counterpart transmit interface.

Switch controller fail

The circuit pack failed. This alarm is masked by the “Switch controller mismatch” alarm. The alarm becomes active when the network element detects the condition. It clears when you replace the circuit pack or correct the fault.

155- 155 -155- 155 -

-


Switch controller mismatch

A different type of circuit pack occupies the switch controller shelf slot. This condition can also occur if you remove or reseat the switch controller circuitpack during a restart.This alarm is masked by the “Switch controller circuit pack missing” alarm and masks the “Switch controller circuit pack fail” alarm.

The alarm becomes active when the network element detects the condition. It clears when the correct circuit pack is installed in the slot.

Switch controller missing

The switch controller is missing from slot 30 in the network element shelf. For example, you might have removed it while it was in service. The alarm might also become active because of a shelf processor failure.

This alarm masks the “Switch controller mismatch” alarm. It is masked by the “SP MBus access fail” alarm.The alarm becomes active when the network element detects the condition. It clears when you:• install a switch controller in the slot• deprovision both the protection DS3 mapper and STS-1 interface circuit packs• replace the shelf processor in the case of a shelf processor fault

Note: The switch controller, used to control protection switching for DS3 and STS-1 tributaries, also monitors battery feeds A and B on the lower half of the OC-48 shelf for alarm monitoring. Therefore, if the networkelement requires alarm monitoring for the lower half of the shelf, the switch controller must be present in slot 30, even if the network element does not

156- 156 -156- 156 -

-


require DS3 or STS-1 protection switching.

157- 157 -157- 157 -

-


Traffic recovery in progress

A service interruption has occurred on the network element and the automatic traffic recovery feature is in progress. This feature tries to recover traffic by performing the following actions:• It resets the OC-48 receive interface circuit packs.• It resets the OC-48 demultiplexer circuit packs.• It performs an equipment protection switch for the externalsynchronization interface (ESI).• It performs a timing reference protection switch.• It tries to reinitialize the affected OC-48 transport interface circuit packs.These circuit packs include both transmit interfaces, receive interfaces, and demultiplexers. The traffic recovery feature is available only on rings for the OC-48 transport interfaces. It does not operate for the tributaries. It can recover traffic only for outages resulting from equipment failures. It cannot recover traffic resulting from double failures affecting both the OC-48 G1 and G2 facilities.The feature detects the outage condition within 1minute and automatically initiates the traffic recovery sequence. The sequence completes within 10 minutes. After 10 minutes, it can begin again if the traffic has not yetrecovered.Table 8-39: SONET Definitions

158- 158 -158- 158 -

-


8.3 MON DefinitionsTerm MON Definitions Band Input Failure

This alarm becomes active when all provisioned OCLD circuit packsassociated with a given OMX have experienced optical input failure.

OPE LAN Port Down

This alarm becomes active when a link on a local area network (LAN) port on the 2x1000SX circuit pack fails. It clears when the link becomes active again.

OPE WAN Port Down

This alarm becomes active when a link on a wide area network (WAN) port on the 2x1000SX circuit pack fails. It clears when the link becomes active again.

RDI Path Remote Defect Indication

Path Remote Defect Indicator (PRDI) is used only at the path level. A problem at the path layer prompts PAIS to be sent downstream and PRDI to be sent back upstream to let the traffic provider know that there is a problem with their circuit down stream.

RDIVT Remote Defect Indication

VT Path RDI (aka VT Path FERF) signal shall be generated within 100 milliseconds by the VT PTE upon detection of a VT-Path AIS or LOP defect. Transmission of the VT-Path RDI signal shall cease within 100 milliseconds when the VT PTE no longer detects VT-Path AIS or VT-Path LOP defect. The VT-Path RDI shall accurately report the presence or absence of VT-Path AIS or VT-Path LOP defects.

Temperature Out of Range

This alarm becomes active when the temperature is too high. One of thefollowing conditions exist:• the shelf cooling unit has failed• the central office temperature is too high• the OFA circuit pack is defectiveTable 8-40: MON Definitions

159- 159 -159- 159 -

-


8.4 Performance Parameters DefinitionsTerm Performance Parameters Definitions Coding Violation Coding Violations (CV) are Bit Interleaved Parity

(BIP) errors that are detected in the incoming signal. CV counters are incremented for each BIP error detected. That is, each BIP-8 can detect up to eight errors per STS-N frame, with each error incrementing the CV counter. Section CVs shall be collected using the BIP-8 in the B1 byte located in the Section Overhead of STS-1 #1. Line CVs shall be collected using the BIP-8s in B2 bytes located in the Line Overhead of each STS-1 (since all CVs on an STS-N line are counted together, this is equivalent to counting each error in the BIP-8*N contained in the B2 bytes of the STS-N Line Overhead). Thus, on an STS-N signal, up to 8 x N CVs may occur in each frame. Path CVs shall be collected using the BIP-8 in the B3 byte of the STS-Path Overhead of the STS SPE. VT CVs shall becollected using the BIP-2 in the V5 overhead byte of the floating VT.

Errored Seconds At each layer, an Errored Second (ES) is a second with one or more Coding Violations at that layer OR one or more incoming defects (e.g., SEF, LOS, AIS, LOP) at that layer has occurred.

Severely Errored Seconds

At each layer, a Severely Errored Second (SES) is a second with x or more CVs at that layer, or a second during which at least one or more incoming defects at that layer has occurred. Values of x vary depending on the line rate and the Bit Error Rate.

Severely Errored Framing Seconds

A Severely Errored Framing Second (SEFS) is a seconds with containing one or more SEF events. This counter is only counted at the Section Layer.

160- 160 -160- 160 -

-


Unavailable Seconds

At the Line, Path, and VT layers, an unavailable second is calculated by counting the number of seconds that the interface is unavailable. At each layer, the SONET/SDH interface is said to be unavailable at the onset of 10 contiguous SESs. The 10 SESs are included in unavailable time. Once unavailable, the SONET/SDH interface becomes available at the onset of 10 contiguous seconds with no SESs. The 10 seconds with no SESs are excluded from unavailable time. With respect to the SONET/SDH error counts at each layer, all counters at that layer are incremented while the SONET/SDH interface is deemed available at that layer. While the interface is deemed unavailable at that layer, the only count that is incremented is UASs at that layer. A special case exists when the 10 or more second period crosses the 900 second statistics window boundary, as the foregoing description implies that the SES and UAS counters must be adjusted when the Unavailable Signal State is entered. Clearly, successive GETs of the affected sonetPathIntervalSES and sonetPathIntervalUAS (for the Line and VT also) objects will return differing values if the first GET occurs during the first few seconds of the window. Table 8-41: MON Definitions

161- 161 -161- 161 -

-


8.5 Acronyms common to technology and equipment for AT&T SONET/MON

ADMAIDATAGBIFBLSRCkt IDCLLICNMCOCOMXCONDTYPEDSRSDWDIDWIDDWDMDSXECTEHGFDFGigEGNEHECIGIFSLTEMONMONTYPENENMAOADMOC-3OC-12OC-48OC-192

Add-Drop MultiplexerAccess IdentifierAutomatic message tagBand Input FailureBidirectional Line Switched RingCircuit Identifier (DS-1, DS-3, OC-3, OC-12, OC-48 and OC-192) COMMON LANGUAGE® Location IdentificationCustomer Network ManagementCentral OfficeCoarse Optical MultiplexerCondition TypeDedicated Sonet Ring Access ServiceDense Wave Division Identifier Dense Wave IDDense Wavelength Division MultiplexingDigital Cross-Connect PanelEqualizer Coupler TrayEquipment Hierarchy GeneratorFiber Distribution FrameGigabit EthernetGateway Network ElementHuman Equipment Catalog Item GroupIntrasite Fault SectionalizationLine Terminating EquipmentMulti-Service Optical NetworkMonitored Parameter TypeNetwork ElementNetwork Monitoring and AnalysisOptical Add/Drop MultiplexerOptical carrier Level 3Optical carrier Level 12Optical carrier Level 48Optical carrier Level 192

162- 162 -162- 162 -

-


OCIOCLDOCMPOPSCIDSRASTIDTBMUPSR

Optical channel interfaceOptical Channel Laser and DetectorOptical Channel ManagerPoint of Presence (Customer-Service Provider Network Access)Sonet Ring IdentifierSonet Ring Access ServiceTarget IdentifierNortel Terminal Bandwidth MultiplexerUnidirectional Path Switched Ring

Table 8-42: Acronyms for SONET/MON

163- 163 -163- 163 -

-


9 SONET/MON References

References for this document include RFC 1595 Telecordia Standards for all vendors for SONET technology.

Other references include the following source material: FLM 6 General Description FJTU-320-410-100, Issue 4, Rev 1,

June 1997 FLM 6 TL1 Messages, Task Oriented Practice (TOP) FJTU-320-410-

274, Issue 4 Rev 1, June 1997. CNM/MON Dedicated Ring Service Architecture, Arvind R. Mallya

Phase 1, Draft 4, 6/10/03. OPTera Metro 5200-series Multiservice Platform Software and

User Interface Standard Release 5.0 Issue 2 December 2002. OPTera Metro 5000-series Multiservice Platform TL1 Interface,

Part 1 of 2 Standard Release 5.0 Issue 2 December 2002.

164- 164 -164- 164 -

-

primeaccess.att.com€¦ · web viewit uses color-coded alarm levels to reveal the condition of...

Documents