Cisco ONS 15454 SDH Reference Manual, Releases 4.1.1 and 4.5
Chapter 9, Security and Timing
Downloads: This chapterpdf (PDF - 229.0KB) The complete bookPDF (PDF - 6.51MB) | Feedback

Security and Timing

Table Of Contents

Security and Timing

9.1  Users and Security

9.1.1  Security Requirements

9.2  Node Timing

9.2.1  Network Timing Example

9.2.2  Synchronization Status Messaging


Security and Timing


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

Chapter topics include:

Users and Security

Node Timing

9.1  Users and Security

The CISCO15 user ID is provided with the ONS 15454 SDH system, but this user ID is not prompted when you sign into Cisco Transport Controller (CTC). This ID can be used to set up other ONS 15454 SDH users. (To do this, complete the "Create Users and Assign Security" procedure in the Cisco ONS 15454 SDH Procedure Guide.)

You can have up to 500 user IDs on one ONS 15454 SDH. Each CTC or TL1 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 SDH maintenance options.

Provisioning—Users can access provisioning and maintenance options.

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

By default, multiple concurrent user ID sessions are permitted on the node, that is, multiple users can log into a node using the same user ID. If you provision a user ID to be active in a single occurrence, concurrent logins with that user ID are not permitted.


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


9.1.1  Security Requirements

Table 9-1 shows the actions that each user privilege level can perform in node view.

Table 9-1 ONS 15454 SDH Security Levels—Node View 

CTC Tab
Subtab(s)
Actions
Retrieve
Maintenance
Provisioning
Superuser

Alarms

Synchronize/filter/delete cleared alarms

X

X

X

X

Conditions

Retrieve/filter

X

X

X

X

History

Session

Filter

X

X

X

X

Node

Retrieve alarms and events/filter

X

X

X

X

Circuits

Create/edit/delete/filter

Partial

X

X

Search

X

X

X

X

Provisioning

General

Edit

Partial

X

EtherBridge

Spanning trees: edit

X

X

Thresholds: create/delete

X

X

Network

All

X

X

Protection

Create/delete/edit

X

X

Browse groups

X

X

X

X

MS-SPRing

All

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

DCC/GCC

DCC/GCC/OSC (R4.5)

Create/edit/delete

X

X

Timing

Edit

X

X

Alarm Behavior

Edit

X

X

Defaults

Edit

X

UCP

All

X

X

WDM-ANS (R4.5)

Provisioning: edit

X

X

Connections: Create/edit/delete/commit/ calculate

X

X

Services: launch

X

X

NE update: edit/reset/import/export

X

X

Inventory

Delete

X

X

Reset

X

X

X

Maintenance

Database

Backup

X

X

X

Restore

X

EtherBridge

MAC table retrieve

X

X

X

X

MAC table clear/clear all

X

X

X

Trunk utilization refresh

X

X

X

X

Protection

Switch/lockout operations

X

X

X

MS-SPRing

MS-SPRing maintenance

X

X

Software

Download

X

X

X

Upgrade/activate/revert

X

Cross-Connect

Protection switches

X

X

X

Overhead XConnect

Read only

Diagnostic

Retrieve diagnostics, file/lamp test

Partial

X

X

Timing

Edit

X

X

X

Audit

Retrieve

X

Routing Table

Read-only

RIP Routing Table

Refresh

X

X

X

X

Test Access

Read-only

X

X

X

X


Table 9-2 shows the actions that each user privilege level can perform in network view.

Table 9-2 ONS 15454 SDH Security Levels—Network View 

CTC Tab
Subtab
Actions
Retrieve
Maintenance
Provisioning
Superuser

Alarms

Synchronize/filter/delete cleared alarms

X

X

X

X

Conditions

Retrieve/filter

X

X

X

X

History

Filter

X

X

X

X

Circuits

Create/edit/delete/filter

Partial

X

X

Search

X

X

X

X

Provisioning

Security

Users: create/change/delete

X

Active logins: logout

X

Policy: change

X

Alarm Profiles

Load/store/delete

X

X

Compare/available/usage

X

X

X

MS-SPRing

All (MS-SPRing)

X

X

Overhead Circuits

 

Edit

X

X


9.1.1.1  Idle User Timeout

Each ONS 15454 SDH CTC or TL1 user can be idle during his or her login session for a specified amount of time before the CTC window is locked. The lockouts prevent unauthorized users from making changes. Higher-level users have shorter default idle periods and lower-level users have longer or unlimited default idle periods, as shown in Table 9-3. The idle user timeout can be modified by a superuser; refer to the Cisco ONS 15454 SDH Procedure Guide for instructions.

Table 9-3 ONS 15454 SDH Default User Idle Times 

Security Level
Idle Time

Superuser

15 minutes

Provisioning

30 minutes

Maintenance

60 minutes

Retrieve

Unlimited


9.1.1.2  Superuser Password and Login Privileges

Superuser password and login privilege criteria are as follows:

Password expiration and reuse settings—Superusers can provision password reuse periods and reuse intervals (the number of passwords that must be generated before a password can be reused).

Login visibility—Superusers can view real-time lists of users who are logged into CTC or TL1 user logins by node by retrieving the list of logins by node.

Invalid login attempts—Superusers can define the quantity of invalid login attempts a user can make before his ID is locked out.

Privilege change—Superusers can initiate privilege changes for other users while the user is logged in. The changes are propagated to all nodes within the network and they become effective the next time the user logs in.

9.1.1.3  Audit Trail

The ONS 15454 SDH maintains a 640-entry, human-readable audit trail of user actions such as login, logout, circuit creation or deletion, and so on. You can move the log to a local or network drive for later review. The ONS 15454 SDH generates an event to indicate when the when the log is 80 percent full, and another event to indicate that the oldest log entries are being overwritten.

9.2  Node Timing

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

The building integrated timing supply (BITS) pins on the ONS 15454 SDH MIC-C/T/P coaxial connectors.

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

The internal ST3 clock on the TCC2 card.

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

One node is set to external. The external node derives its timing from a BITS source wired to the BITS MIC-C/T/P coaxial connectors. 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 STM-N trunk (span) cards.

You can set three timing references for each ONS 15454 SDH. 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 SDH TCC2 card. This clock is a Stratum 3 (ST3). If an ONS 15454 SDH 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.

9.2.1  Network Timing Example

Figure 9-1 shows an ONS 15454 SDH 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 MIC-C/T/P coaxial connectors on Node 1. The third reference is set to internal clock. The BITS outputs on 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 (span) 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 an equal distance from Node 1.

Figure 9-1 ONS 15454 SDH Timing Example

9.2.2  Synchronization Status Messaging

Synchronization status messaging (SSM) is an SDH protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SDH section overhead. They enable SDH 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 SDH, consult your timing reference documentation to determine which message set to use. Table 9-4 shows the SDH message set.

Table 9-4 SDH SSM Message Set 

Message
Quality
Description

G811

1

Primary Reference Clock

STU

2

Sync traceability unknown

G812T

3

Transit Node Clock Traceable

G812L

4

Local Node Clock Traceable

SETS

5

Synchronous Equipment

DUS

6

Do not use for timing synchronization