Cisco ONS 15454 Reference Manual, Release 3.4
Chapter 8, Security and Timing

Table Of Contents

Security and Timing

8.1 Users and Security

8.2 Node Timing

8.2.1 Network Timing Example

8.2.2 Synchronization Status Messaging


Security and Timing


This chapter provides information about Cisco ONS 15454 users and SONET timing. To provision security and timing, refer to the Cisco ONS 15454 Procedure Guide.

Chapter topics include:

Users and Security

Node Timing

8.1 Users and Security

The CISCO15 user provided with each ONS 15454 can be used to set up other ONS 15454 users. You can have up to 500 users to one ONS 15454. Each ONS 15454 user can be assigned one of the following security levels:

Retrieve users can retrieve and view CTC information but cannot set or modify parameters.

Maintenance users can access only the ONS 15454 maintenance options.

Provisioning users can access provisioning and maintenance options.

Superusers can perform all of the functions of the other security levels as well as set names, passwords, and security levels for other users.

Table 8-1 shows the actions that each user can perform in node view.

Table 8-1 ONS 15454 Security Levels—Node View 

CTC Tab
Subtab
Actions
Retrieve
Maintenance
Provisioning
Superuser

Alarms

n/a

Synchronize alarms

X

X

X

X

Conditions

n/a

Retrieve

X

X

X

X

History

Session

Read only

       
 

Node

Retrieve Alarms/Events

X

X

X

X

Circuits

n/a

Create/Edit/Delete/Filter

   

X

X

   

Search

X

X

X

X

Provisioning

General

Edit

   

X

X

 

EtherBridge

Spanning Trees: Edit

   

X

X

   

Thresholds: Create/Delete

   

X

X

 

Network

All

     

X

 

Protection

Create/Delete/Edit

   

X

X

   

Browse groups

X

X

X

X

 

Ring

All (BLSR)

   

X

X

 

Security

Create/Delete

     

X

   

Change password

same user

same user

same user

all users

 

SNMP

Create/Delete/Edit

   

X

X

   

Browse trap destinations

X

X

X

X

 

Sonet DCC

Create/Delete

   

X

X

 

Timing

Edit

   

X

X

 

Alarm Behavior

Edit

   

X

X

 

Defaults Editor

Edit

     

X

 

UCP

All

   

X

X

Inventory

n/a

Delete

     

X

   

Reset

     

X

Maintenance

Database

Backup/Restore

     

X

 

EtherBridge

Spanning Tree (read only)

       
   

MAC Table Retrieve

X

X

X

X

   

MAC Table Clear/Clear all

 

X

X

X

   

Trunk Utilization Refresh

X

X

X

X

 

Protection

Switch/lock out operations

 

X

X

X

 

BLSR

BLSR maintenance

 

X

X

X

 

Software

Download/Upgrade/ Activate/Revert

     

X

 

XC Cards

Protection switches

 

X

X

X

 

Overhead XConnect

Read only

       
 

Diagnostic

Retrieve

     

X

   

Lamp test

 

X

X

X

 

Timing

Edit

 

X

X

X

 

Audit

Retrieve

X

X

X

X

 

Routing Table

Read only

       
 

RIP Routing Table

Refresh

X

X

X

X


Each ONS 15454 user has a specified amount of time that he or she can leave the system idle before the CTC window is locked. The lockouts prevent unauthorized users from making changes. Higher-level users have shorter idle times, as shown in Table 8-2.

Table 8-2 ONS 15454 User Idle Times 

Security Level
Idle Time

Superuser

15 minutes

Provisioning

30 minutes

Maintenance

60 minutes

Retrieve

Unlimited


You can perform ONS 15454 user management tasks from network or node view. In network view, you can add, edit, or delete users from multiple nodes at one time. If you perform user management tasks in node view, you can only add, edit, or delete users from that node.


Note You must add the same user name and password to each node the user will access.


8.2 Node Timing

SONET timing parameters must be set for each ONS 15454. Each ONS 15454 independently accepts its timing reference from one of three sources:

The BITS (Building Integrated Timing Supply) pins on the ONS 15454 backplane

An OC-N card installed in the ONS 15454. The card is connected to a node that receives timing through a BITS source.

The internal ST3 clock on the TCC+ card

You can set ONS 15454 timing to one of three modes: external, line, or mixed. If timing is coming from the BITS pins, set ONS 15454 timing to external. If the timing comes from an OC-N card, set the timing to line. In typical ONS 15454 networks:

One node is set to external. The external node derives its timing from a BITS source wired to the BITS backplane pins. The BITS source, in turn, derives its timing from a Primary Reference Source (PRS) such as a Stratum 1 clock or GPS signal.

The other nodes are set to line. The line nodes derive timing from the externally-timed node through the OC-N trunk cards.

You can set three timing references for each ONS 15454. The first two references are typically two BITS-level sources, or two line-level sources optically connected to a node with a BITS source. The third reference is the internal clock provided on every ONS 15454 TCC+ card. This clock is a Stratum 3 (ST3). If an ONS 15454 becomes isolated, timing is maintained at the ST3 level.


Caution Mixed timing allows you to select both external and line timing sources. However, Cisco does not recommend its use because it can create timing loops. Use this mode with caution.

8.2.1 Network Timing Example

Figure 8-1 shows an ONS 15454 network timing setup example. Node 1 is set to external timing. Two timing references are set to BITS. These are Stratum 1 timing sources wired to the BITS input pins on the Node 1 backplane. The third reference is set to internal clock. The BITS output pins on the backplane of Node 3 are used to provide timing to outside equipment, such as a Digital Access Line Access Multiplexer.

In the example, Slots 5 and 6 contain the trunk cards. Timing at Nodes 2, 3, and 4 is set to line, and the timing references are set to the trunk cards based on distance from the BITS source. Reference 1 is set to the trunk card closest to the BITS source. At Node 2, Reference 1 is Slot 5 because it is connected to Node 1. At Node 4, Reference 1 is set to Slot 6 because it is connected to Node 1. At Node 3, Reference 1 could be either trunk card because they are equal distance from Node 1.

Figure 8-1 An ONS 15454 timing example

8.2.2 Synchronization Status Messaging

Synchronization Status Messaging (SSM) is a SONET protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SONET Line layer. They enable SONET devices to automatically select the highest quality timing reference and to avoid timing loops.

SSM messages are either Generation 1 or Generation 2. Generation 1 is the first and most widely deployed SSM message set. Generation 2 is a newer version. If you enable SSM for the ONS 15454, consult your timing reference documentation to determine which message set to use. Table 8-3 and Table 8-4 show the Generation 1 and Generation 2 message sets.

Table 8-3 SSM Generation 1 Message Set 

Message
Quality
Description

PRS

1

Primary reference source - Stratum 1

STU

2

Sync traceability unknown

ST2

3

Stratum 2

ST3

4

Stratum 3

SMC

5

SONET minimum clock

ST4

6

Stratum 4

DUS

7

Do not use for timing synchronization

RES

 

Reserved; quality level set by user


Table 8-4 SSM Generation 2 Message Set

Message
Quality
Description

PRS

1

Primary reference source - Stratum 1

STU

2

Sync traceability unknown

ST2

3

Stratum 2

TNC

4

Transit node clock

ST3E

5

Stratum 3E

ST3

6

Stratum 3

SMC

7

SONET minimum clock

ST4

8

Stratum 4

DUS

9

Do not use for timing synchronization

RES

 

Reserved; quality level set by user