Tellabs® 8600 Managed Edge System Network Time Protocol Configuration Guide75

rate or flag this pageTweet this

By Dian Hendratmo

Tellabs® 8600 Managed Edge System Network Time Protocol Configuration Guide

A. Overview

The figure below shows the fault management processing in a network element (NE).

The network element management model can be presented as Managed Object Classes (MOC),
Instances and their attribute values with related operations. Logically the fault and event information is
able to map to the management model.

Fault Source Grouping

Faults are mapped to the card slot (only in Tellabs 8630 access switch and Tellabs 8660 edge

switch), fault groups and inside groups to specific sources.

Here are some examples of the CLI fault groups/sources:

NODE

• Node

HW-INVENTORY

• Unit

• IF Module <slot>/<module>/*

• Timing Module Primary

• Timing Module Backup

• Cooling Fan <FAN number>

• IF Conn. Module <slot>/<module>/<interface>

• IF Module <slot>/<module>/*

• Unit Inventory

• Unit Inventory <slot>

INTERFACE

• Physical fe <slot>/<module>/<interface>

• Logical fe <slot>/<module>/<interface>

• Logical fe <slot>/<module>/<interface>.<vlanId>

• fe <slot>/<module>/<interface>

• L1 fe <slot>/<module>/<interface>.<vlanId>

• L2 fe <slot>/<module>/<interface>.<vlanId>

• PPP so <slot>/<module>/<interface>

• PPP LCP <slot>/<module>/<interface>

• PPP IP CP so <slot>/<module>/<interface>

• PPP MPLS CP so <slot>/<module>/<interface>

• Physical so <slot>/<module>/<interface>

• RS so <slot>/<module>/<interface>

• MS so <slot>/<module>/<interface>

• AU4 so <slot>/<module>/<interface>

• VC4 so <slot>/<module>/<interface>

• ATMso<if id>

• ATMVPso<if id>
• ATMVCso<if id>

• ATM AAL5 so <if id>

• P12 so<if id>

• TSGroup so<if id>

<if id> refers to a normal interface identification number sequence as specified in the interface

CLI command.

FAULT

• Current faults

• History faults

• Ext Input <Input line number>

• <user given source if user definable fault>

TCP

• Tcp

ICMP

• Icmp

ARP

• fe <slot>/<module>/<interface>.<vlanId>

BGP

• Bgp <AS number>

• Neighbor <neighbor address>

• Neighbor <neighbor address> Vrf <vrf name>

• Neighbor <neighbor address> ipv4 unicast

• Neighbor <neighbor address> ipv4 multicast

• Neighbor <neighbor address> vpnv4 unicast

OSPF

• fe <slot>/<module>/<interface>.<vlanId>

• Ospf <processid>

RSVP-TE

• Primary <tunnel name>

• Secondary <tunnel name>

LDP

• Session <peer address>

MPLS

• Oam <OAM name>

MANAGEMENT-IF

• BMPAgent

• BMP Testing

• CLIAgent

• SNMP Agent

PROTECTION

• Unit Prot. <group name>

• Unit Prot. <group name> Primary <slot>

• Unit Prot. <group name> Backup <slot>

• IF Prot <group name>

• IF Prot <group name> Primary

• IF Prot <group name> Backup

• MSProt.

• MS Prot.<group name>
• MS Prot.<group name> Primary

• MS Prot.<group name>Backup

• MSP so <slot>/<module>/<interface>

• LSPProt.

• LSP Prot.<group name>

• LSP Prot. <group name> Primary

• LSP Prot. <group name> Backup

NTP

• Ntp

SW-MANAGEMENT

• Node

• Manager

• BootSW

• Mini Appl. SW

• <file name> SW

NODE-TIMING

• Node

• Clock Selector

• Fallback List <slot>/<module>/<interface>

• Sync. Input <slot>/<module>/<interface>

• Sync. Output <slot>/<module>/<interface>

MEASURE

• Voltage <voltage> V

• CPU Temperature
• Unit Temperature

• Cooling Fan <FAN number>

HW

• Unit

• Unit<slot>

• IF Module <slot>/<module>/*

• Timing Module

B. Fault Severity

Each fault (or event) has a predefined severity:

• Critical

• Major

• Minor

• Warning

• Informational

• (Debug)

In Tellabs 8630 access switch and Tellabs 8660 edge switch the NE state LEDs in CDC reflect the

severity of the currently active faults in the NE.

C. Service Affected Flag

Some faults are “service affected”, that is they break traffic or have major impact on service quality.

Alarm Type

Each fault has a predefined alarm type in one of the following categories:

• com = communication alarm type

• qos = quality of service alarm type

• pro = processing error alarm type

• equ = equipment alarm

• env = environmental alarm

• int = integrity violation

• ope = operational violation

• phy = physical violation

• sec = security service or mechanism violation

D. LED

A fault might light a card state and/or interface state LED. The possible consequents are:

• No led

• Yellow led (error detected but fault cause not in this card or NE)

• Red led (error detected in this card)

In Tellabs 8630 access switch and Tellabs 8660 edge switch, also the NE state LEDs in CDC might

be lit, see chapter 1.1.2 Fault Severity.

F. Fault Status

The fault status (or fault state) is one of the following:

• On (fault is active)

• Off (fault is not active)

• Delta; for some faults, no specific on and off time can be defined. This describes some event.

After a delta event, the fault state is off.

1. External Alarm Relays

Tellabs 8630 access switch and Tellabs 8660 edge switch have 4 fixed and 2 programmable external

output relays and 8 (per CDC) external input relays. Tellabs 8605 access switch has one fixed and

one programmable external output relays and 4 external input relays.

The external line status can be:

• Open - not connected to GND (ground)

• Closed - connected to GND (ground)

The fixed external outputs are:

• If Critical output is closed, the Critical NE alarm is ON.

• If Major output is closed, the Major NE alarm is ON.

• If Minor/Warning output is closed, the Minor/Warning NE alarm is ON

• If power voltage output is on, power voltage (+48 V battery in CDC) is OK.

The first three outputs act like NE state alarm LEDs.

The programmable output line status and non-volatile behavior can be set by the user.

Each of the external input lines can be associated to the user-defined fault or pre-defined faults.

1.1.8 System Message Logging

Faults and other events cause corresponding human readable system messages. The messages can

be stored into:

• CLI console (optional)

• Logging server using syslog protocol [RFC3164] (optional)

Tellabs® 8600 Managed Edge System FP1.0 and FP2.8 Network Time Protocol Configuration Guide

1. Network Time Protocol

General

In the Tellabs 8600 system Network Time Protocol (NTP) synchronizes the clock of the hosts

and routers in the Internet. The synchronized time is needed in routers for various reasons suchas
network monitoring, measurement and control, intrusion detection, isolation and logging. The
supported versions are NTPv3 according to [RFC1305] except for Authentication and Broadcastm mode
and NTPv4 according to [draft-ietf-ntp-ntpv4-proto-04.txt].

Primary servers synchronize to national standards whereas secondary servers and clients synchronize to
primary servers via a hierarchical subnet. Clients and servers operate in Master/Slave, Symmetric or
Multicast modes with or without cryptographic authentication.

Fig. 1

As can be seen in the figure above, the routers are acting as NTP clients and as a time server. They
communicate via the network and their connection is a subject to changes in the communication path.
The system clock is disciplined in time and frequency using an adaptive algorithm responsive to network
time jitter and clock oscillator frequency wander.

This means, in practice, that the algorithms used in NTP communication can compensate the delay and
the differences in delay caused by the network between the NTP server and clients. Hence, the times of
the servers 1 and 2 are comparable even if the network between them and the server is not similar. NTP
algorithms are designed to compensate such differences. The nominal accuracy of the protocol is in the
low milliseconds. In practice, the accuracy is at the 10 millisecond level in wide area networks and at the
millisecond level in local area networks.

If NTP is configured, clients can have a peer relationship. In this case either the client 1 or 2 can provide
the time synchronization services to the other clients if they are configured to do so.The router 1 acts as
an NTP server to routers 3 and 4. These routers have a client-server relationship; routers 3 and 4 are NTP
clients and router 1 is the NTP server.

Stratum index in the figure above refers to the distance to the authoritative time source in the clock
synchronization network. Stratum 1 level clock source cannot be implemented with the Tellabs 8600
equipment due to the lack of direct connection to the Global Positioning System (GPS) and atom clock.
Stratum in the context of NTP does not refer to the NE transport layer synchronization “Stratum X” clock.
The security threats imposed by enabling NTP in the network element are similar to those of other
distributed protocols used for network routing and management. The access control mechanisms
offered via the NTP commands respond to these threats by limiting access to trusted peers. The NTP
functionality in the network element recognizes the trusted peers by using authentication keys. It is
possible to configure more than one peer and multiple synchronization peers provide redundancy and
diversity. For further information on NTP, see NTP home page at http://www.ntp.org.

NTP References

Network Time Protocol Configuration

Examples
This chapter presents the currently supported configuration examples for the network time protocol.

Synchronizing Network Time

Configuration Examples

Setting the Clock

The user can set the network element clock. If the NTP functionality is configured and the NTP

server is reachable, the time will be adjusted by NTP. For NTP to be operational, the clock is initially set
manually close enough to the correct time (within 1000 s).

NTP Master

This command configures the system as the authoritative NTP server. This allows the network

elements to act as the time distribution root server. Note that if the network has several NTP masters
enabled, instability in keeping the time may occur.