Alcatel-Lucent Scalable IP Networks Student Guide v1-1

Alcatel-Lucent Scalable IP Networks

Module 0 Introduction

Alcatel-Lucent C

onfidential for internal use only -- Do N

ot Distribute

Module 0 - 2Scalable IP Networks v1.00

Alcatel-Lucent Scalable IP Networks v1.1 Module 0 | 2 All rights reserved 20062007 Alcatel-Lucent

Module Objectives

Course timelineCourse objectivesCourse prerequisitesCourse introduction


This course is part of the Alcatel-Lucent Service Routing Certification (SRC) Program. For more information on the the SRC program, see www.alcatel-lucent.com/src

To locate additional information relating to the topics presented in this manual, refer to the following:

Technical Practices for the specific product Internet Standards documentation such as protocol standards bodies, RFCs, and IETF drafts Technical support pages of the Alcatel website located at: http://www.alcatel-lucent.com/support

Alcatel-Lucent C


ot Distribute



Alcatel-Lucent Scalable IP Networks Timeline

Day 1 Module 0 Introduction Module 1 Internet Overview Module 2 7x50 SR/ESS Components and CLI

Day 2 Module 3 Ethernet Overview Module 4 IP Overview & Addressing

Alcatel-Lucent C


ot Distribute



Alcatel-Lucent Scalable IP Networks Timeline

Day 3 Module 5 Transport Layer Overview Module 6 IP Routing Module 7 Link State Routing Protocols

Day 4 Module 8 BGP Overview Module 9 7750 SR Services Overview

Alcatel-Lucent C


ot Distribute



Alcatel-Lucent Scalable IP Networks Objectives

After successful completion of this course, you should be familiar with: The OSI protocol suite Key functions of the Ethernet protocol Key functions of an IP network The IP address classes, IP subnet masking, and IP super-

netting Configuration of IP addresses and subnet masks on router

interfaces The concepts of static and dynamic routing The differences between IGP and EGP routing protocols

Alcatel-Lucent C


ot Distribute



Alcatel-Lucent Scalable IP Networks Objectives (continued)

Understand the differences between a distance vector protocol and a link state protocol Understand the basic operation of RIP Understand the basic operation of OSPF Successfully configure the various IGP protocols Understand the basic operation of BGPv4 Successfully configure BGPv4 Understand TCP and UDP as transport protocols Understand the various services offered by the 7750 SR

Alcatel-Lucent C


ot Distribute



Prerequisites and Follow-On

Suggested prerequisites There is no prerequisite for this course, however familiarity

with binary arithmetic is an asset.

Suggested follow-on courses Based on the material covered in this course, it is

recommended that this course be followed with the Alcatel-Lucent IGP course.

ASIN exam To ensure full comprehension of the material covered in

this course, it is recommended that the student register for and take the Alcatel-Lucent Scalable IP Networks exam following successful completion of this course.

Alcatel-Lucent C


ot Distribute



Alcatel-Lucent Scalable IP Networks Introduction

IP technology has exploded over the last decade. The technology has now infiltrated every facet of our lives. This 4-day course introduces the layer 2 and layer 3 technology that is used in the networking world.

Alcatel-Lucent C


ot Distribute



Alcatel-Lucent Scalable IP Networks Course Goal

Provide the participants with foundation knowledge of IP networking, its applications, and its implementation in an Alcatel-Lucent environment.

Alcatel-Lucent C


ot Distribute



Graphical Symbols and Icons

DA SA Type IP Data

10.1.1.1

Generic router

Table

Flow or lookup

Packet (showing detail)

Network Cloud System or loopbackInterface

Data plane

(dotted blue)

Control plane

(dashed red)

Physical link

(solid black)

PE

Customer site 1

Switch

Customer site 2Server

Workstation

User

1

These typical graphical symbols are used in this course.

Alcatel-Lucent C


ot Distribute



Administration

RegistrationFacility informationRestroomsCommunicationsMaterialsScheduleIntroductions Name and company Experience

Questions

Alcatel-Lucent C


ot Distribute

www.alcatel-lucent.com

3HE-02767-AAAA-WBZZA Edition 01

Alcatel-Lucent C


ot Distribute


Module 1 Internet Overview

Alcatel-Lucent C


ot Distribute

Module 1 page 2Scalable IP Networks v1.01


Module Objectives

After successful completion of this module, you should be able to: Understand the layering concepts of network protocols Discuss the functions of the different layers of the TCP/IP

protocol suite Identify some of the different protocols that operate at the

different layers Understand the encapsulation process as data travels across

the Internet Compare and contrast the OSI and TCP/IP layering models

Alcatel-Lucent C


ot Distribute

OSI Overview

Section 1 Reference Model

Alcatel-Lucent C


ot Distribute



TCP/IP Protocols

Developed in the 1970s by pioneering network engineers Vinton Cerf and Bob Kahn Intended to provide a common framework to allow the

interworking of diverse network hardware and computer systems Included in early releases of the UNIX operating system During the 1980s, primarily used by U.S. universities and

research institutions During the 1990s, increasingly adopted by commercial

enterprises Provides the underlying technological framework of the

Internet today

Developed in the 1970s by pioneering network engineers Vinton Cerf and Bob Kahn.

Intended to provide a common framework to allow the interworking of diverse network hardware and computer systems.

TCP/IP was included in early releases of the UNIX operating system. This led to extensive use of TCP/IP at universities and other enterprises that used UNIX.

During the 1980s, primarily used by U.S. universities and research institutions. From 1986, the backbone of the Internet was primarily provided by the NSFnet, a government-sponsored network, and was not intended for commercial use.

Increasingly adopted by commercial enterprises during the 1990s. On April 30, 1995, the architecture was transitioned from the NSFnet backbone to the use of distributed interconnection or peering points.

Provides the underlying technological framework of the Internet today. As of June 30, 2006, it was estimated that there are 1.04 billion Internet users worldwide (http://www.internetworldstats.com/stats.htm).

Alcatel-Lucent C


ot Distribute



TCP/IP Layering

ApplicationServices

Transport

InternetProtocol

NetworkInterfaces

TCP/IP Layers

The purpose of a network protocol suite is to define the protocols and technologies that support the interconnection of a diverse array of hardware and systems to support the operation of a wide range of applications over the network. Anyone who has used an Internet application such as a web browser or e-mail can appreciate the complexity of the systems required to support these applications.

The layering of protocols provides a way to simplify this complex problem by segregating it into a number of smaller functions. Each layer performs a specific function that contributes to the overall functioning of the network. Protocol layers have the following benefits:

Simplify complex procedures into a structure that is easier to understand Allow vendors to interoperate Isolate problems from one layer that may be passed to other areas Allow modular plug-and-play functionality

The TCP/IP protocol suite (or Internet protocol suite) is constructed around four layers of technology. The application layer provides all the services (for example, web browsing and e-mail) available to users of the Internet. The network interfaces layer includes all the hardware that comprises the physical infrastructure of the Internet. The two intermediate layers provide a common set of services that are available to all Internet applications and that operate on all the hardware infrastructure of the Internet.

Alcatel-Lucent C


ot Distribute



TCP/IP Layering Application Layer

ApplicationServices

Transport

InternetProtocol

NetworkInterfaces

TCP/IP Layers

ApplicationUser interface to the network

User Applications E-mail Telnet FTP WWW

The application layer is the layer for the user. It is important to understand at this point that this layer only describes Network applications. Applications such as word processors and database programs are not considered network applications as they do not require network connectivity and are not part of this layer.

The figure above shows examples of network applications. Without network connectivity, these applications would be useless.

Alcatel-Lucent C


ot Distribute



TCP/IP Layering Transport Layer

ApplicationServices

Transport

InternetProtocol

NetworkInterfaces

TCP/IP Layers

TransportCommunication between applications

Reliable data transfer Flow control Sequencing of data

Transport protocols are the applications interface to the network. The transport protocol provides a mechanism for an application to communicate with an application residing on another device in the network.

In the TCP/IP protocol suite there are two transport protocols: TCP and UDP. TCP is a connection-oriented protocol that provides an ordered and reliable transfer of data over the network. UDP is a connectionless protocol that supports the transfer of a single datagram across the network with no delivery guarantee. UDP is simpler and operates with less overhead than TCP.

Most Internet applications use TCP for data transfer because it provides a reliable transfer service. This includes HTTP (web browsing), e-mail, Telnet, and FTP. Some applications, such as DNS and SNMP, use UDP because they only require a simple datagram transfer, while RTP uses UDP to avoid the overhead of TCP and because there is no benefit in retransmitting lost packets for applications that use RTP.

Alcatel-Lucent C


ot Distribute



TCP/IP Layering Internet Protocol Layer

ApplicationServices

Transport

InternetProtocol

NetworkInterfaces

TCP/IP Layers

Internet ProtocolCommon services and addressing

Unique network addressing scheme to identify hosts Routing protocols for path determination End-to-end forwarding of datagrams

The Internet protocol layer provides a common addressing plan for all hosts on the Internet as well as a simple, unreliable datagram transfer service between these hosts. IP is the common glue that defines the Internet.

IP also defines the way a datagram (or packet) is routed to its final destination. In an IP network, the forwarding of packets across the network is handled by routers. IP routers examine the destination address of a datagram and determine which router is the next hop that will provide the best route to the destination (known as hop-by-hop routing). Routers communicate with each other using dynamic routing protocols to exchange information about the networks they are connected to. This allows routers to make forwarding decisions for the datagrams they receive.

Alcatel-Lucent C


ot Distribute



TCP/IP Layering Network Interfaces

ApplicationServices

Transport

InternetProtocol

NetworkInterfaces

TCP/IP Layers

Network InterfacesPhysical transfer of data

Ethernet ATM Frame Relay PPP

The network interfaces layer comprises the hardware that supports the physical interconnection of all network devices. The technologies of this layer are often defined as multiple layers themselves. The common attribute of all technologies of this layer is that they are able to forward IP datagrams.

There are many different technologies that operate at this layer, some of which are very complex. Some of the protocols commonly used at this layer include ATM, frame relay, PPP, and Ethernet. However, there are many other protocols used; some are open standards and some are proprietary. The diversity of the network interfaces layer demonstrates one of the benefits of protocol layering. As new transmission technologies are developed, it is not necessary to make changes to the upper layers to incorporate these technologies in the network. The only requirement is that the new technology be able to support the forwarding of IP datagrams.

This layer is often referred to as Layer 2 in reference to the data link layer of the OSI reference model (presented later).

Alcatel-Lucent C


ot Distribute



Application Encapsulation

ApplicationServices

Transport

InternetProtocol

NetworkInterfaces

TCP/IP Layers

From: [email protected]: [email protected]

Message Body

When a network application wants to communicate with another application across the network, it must first prepare its data in the specific format defined by the protocol to be used by the receiving application. A specific protocol is used so that the receiving application will know how to interpret the data it receives.

In the case of a mail message, the message consists of two parts, the message header and the body. The message header contains the senders and receivers addresses as well as other information such as the urgency of the message and the nature of the message body. The format of the header and the nature of the addresses is defined by the application protocol. In the case of a mail message, the protocol is SMTP.

In addition to defining the format of the message, the protocol also specifies how the applications are expected to interact with each other, including the exchange of commands and the expected responses.

To accomplish the transfer of the applications data, the application uses the services of the transport layer.

Alcatel-Lucent C


ot Distribute



Transport Encapsulation

ApplicationServices

Transport

InternetProtocol

NetworkInterfaces

TCP/IP Layers


Message Body

Source: 1223Destination: 25

Message BodyHeader Body

The transport layer provides a service to transfer data between applications across a network. There are two transport protocols used on the Internet: TCP and UDP. For exchanging e-mail across the Internet, an e-mail application uses SMTP. SMTP uses TCP to accomplish the transfer. TCP provides a reliable transfer service so that the application does not have to be concerned about whether all data is properly transferred. UDP provides a simple, unreliable datagram delivery service (much like IP).

TCP treats all application data as a simple byte stream, including both the message header and the message body. TCP accepts the applications data and breaks it into segments for transmission across the network as required. To accomplish this reliable transfer, TCP packages the application data with a TCP header. On the receiving end of the connection, TCP removes the TCP header and reconstructs the application data stream exactly as it was received from the application on the senders side of the network.

The TCP and UDP headers carry source and destination addresses that identify the sending and recipient applications because a single host system may support multiple applications. These addresses are known as port numbers. The TCP units of data are known as segments; UDP data is called a datagram.

To transmit its segments of data across the network, TCP uses the services of the IP layer.

Alcatel-Lucent C


ot Distribute



IP Encapsulation

ApplicationServices

Transport

InternetProtocol

NetworkInterfaces

TCP/IP Layers


Message Body



Source:138.120.191.122Dest.: 197.199.45.12

Header Header Body

The IP layer provides a common addressing scheme across the network as well as a simple, unreliable datagram forwarding service between nodes in the network.

Data from the transport layer is packaged in IP datagrams for transfer over the network. Each datagram travels independently across the network. The intermediate routers forward the datagram on a hop-by-hop basis based on the destination address.

Each datagram contains source and destination addresses that identify the end nodes in the network. Every node in an IP network is expected to have a unique IP address.

IP uses the services of the underlying network interfaces to accomplish the physical transfer of data.

Alcatel-Lucent C


ot Distribute



Data Link Encapsulation

ApplicationServices

Transport

InternetProtocol

NetworkInterfaces

TCP/IP Layers


Message Body



Source:138.120.191.122Dest.: 197.199.45.12

Header Header Body

DA: 00-D0-F6-A4-26-5CSA: 00-20-60-37-BB-5F

Hdr FCS

Hdr Hdr Body

The data link layer is the term used to describe the network interfaces used by IP for physically transmitting the data across the network. The units of data transmitted at the data link layer are usually known as frames. IP datagrams must always be encapsulated in some type of data link frame for transmission.

A typical data link frame contains a header, usually containing some type of address. The frame also often carries a trailer that contains some type of checksum to verify the integrity of the transmitted data. There are many types of technology used as network interfaces by IP, and they each have their own specific format and rules of operation. The common characteristic is that the technologies are all capable of carrying IP datagrams.

Most protocols at this layer also use some type of addressing. The address identifies the two endpoints of a data exchange to the data link protocol. For example, the figure above shows the addressing of an Ethernet frame. Some point-to-point protocols such as PPP may not use addresses if there is only one possible destination for the data.

Alcatel-Lucent C


ot Distribute



OSI A History Lesson

Early 1970s Canepa and Bachman at Honeywell Information Systems worked to develop a mechanism to distribute databases. Late 1970s ISO and CCITT each developed a standard. 1983 The ISO and CCITT documents merged into the Basic

Reference Model for Open Systems Interconnection. 1984 The merged document was published by both ISO

and CCITT, with CCITT being renamed ITU-T (ISO 7498 and ITU-T X.200). Some OSI protocols (e.g., X.21 and ATM) competed with

TCP/IP, but growth of the Internet caused IP to be adapted.

The OSI reference model was developed at the end of the 1970s, but the development of actual protocols to support the reference model was slow. By the early 1990s a number of OSI protocols (TP0-4, CLNS, CONS, X.400, and X.500) had been specified and commercial implementations attempted, but the success of TCP/IP and the weaknesses of OSI led to the complete adoption of TCP/IP for internetworking.

Alcatel-Lucent C


ot Distribute



OSI Interesting Facts

Formed the basis of the OSI protocol suite, to create a widely adopted suite of protocols to be used by international networks The 7-layer model created by Bachman and Canepa was the

only model submitted to the ISO subcommittee in March 1978 Introduced to compete with IBMs SNA, due to the

companys closed architecture

OSI was designed as an open standard to replace the strictly proprietary networking technologies that were in use in the 1970s (SNA was dominant, but many others were also in use). However, TCP/IP applications and implementations grew much more rapidly than OSI and by 2000, OSI was essentially replaced by TCP/IP.

The OSI reference model is widely used to describe the layering of network protocols, and much networking terminology derives from the OSI protocol suite. A few remnants of OSI are still in use; for example, LDAP, which is a derivation and simplification of X.500, and IS-IS, which was designed as an OSI routing protocol and was adapted to TCP/IP networks.

Alcatel-Lucent C


ot Distribute



OSI Model

OSI

Upper Layers

Lower Layers

Application

Presentation

Session

Transport

Network

Data Link

Physical

The OSI reference model represents a logical way of organizing how networks talk to each other so that all hardware and software vendors have an agreed-upon framework to develop networking technologies. By providing and using this model, the ISO has accomplished the following:

Simplifies complex procedures into an easy-to-understand structure Allows vendors to interoperate Provides the ability to isolate problems from one layer that may be passed to other areas Allows a modular plug-and-play functionality Provides an independent layer design

The OSI model is represented by the seven layers depicted in the figure above. These layers may be grouped into two main areas, defined simply as the upper and lower layers.

Although a single device (for example, a UNIX workstation) can execute all seven layers, this is not practical in real networks. The amount of traffic that needs to be moved through modern networks requires purpose-built devices that handle various layer functions. Two such examples are bridges, which are purpose-built for layer 2 operation, and routers, which are purpose-built for layer 3 operation.

Alcatel-Lucent C


ot Distribute



TCP/IP Suite vs. OSI

ApplicationServices

Transport

InternetProtocol

NetworkInterfaces

TCP/IP Suite

Application

Presentation

Transport

Data Link

OSI

Session

Network

Physical

The TCP/IP suite differs from the OSI model in that the TCP/IP suite uses four protocol layers and the OSI model uses seven layers. The figure above roughly shows the protocol layer relationship between the two models.

Network Interfaces This layer is used to define the interface between hosts and contains the functionality of both the physical and data link layers of the OSI model. Protocols such as Ethernet describe both the framing of data (layer 2) and the physical transmission of the frame over the media (layer 1). This layer is often referred to as layer 2 or L2 because it provides OSI layer 2-type services to the IP layer.

Internet Protocol The IP layer provides a universal and consistent forwarding service across a TCP/IP network. IP provides services comparable to the OSI network layer and is sometimes referred to as a layer 3 (or L3) protocol. The OSI protocol CLNP corresponds most closely to IP.

Transport The transport layer comprises two main protocols, TCP and UDP. These transport protocols provide similar services to the OSI transport protocols. TCP is very similar to the OSI transport protocol, TP4. TCP and UDP may be referred to as layer 4 protocols.

Application Services The application services provide end-user access to the Internet. Any of the services of the upper three OSI protocols that are required are incorporated into the application protocols. There are a number of Internet protocols that provide services similar to these OSI layers, although they do not follow the layering or service definitions of OSI. For example, TLS provides session-like services to Internet applications and MIME provides presentation-like services to SMTP and HTTP. Application layer protocols are sometimes referred to as layer 7 protocols.

Alcatel-Lucent C


ot Distribute

OSI Overview

Section 2 Network Devices

Alcatel-Lucent C


ot Distribute



Network Devices Examples

Switch Router

Hub

Repeater

The figure above shows some different network devices. The major difference between them is the OSI layer that each of the devices operates at.

L1 Physical Layer With regard to the figure above, the repeater and the hub are considered to be layer 1 devices. These devices normally have no intelligence. The devices simply take whatever traffic comes in and send it out with no decision-making.

L2 Data Link Layer In the figure above, the switch is the layer 2 device. The switch makes intelligent forwarding decisions based on the data link address, whether it be a MAC address, VPI/VCI, or DLCI. An Ethernet switch also dynamically learns the MAC addresses of the hosts in its LAN. Data on a switch is divided into collision domains (a port on a switch represents a single collision domain). However, the switch and all its ports reside in one broadcast domain.

L3 Network Layer The most common layer 3 device is a router. The router makes intelligent forwarding decisions based on the network layer address. As in a switch, each port on a router is a single collision domain. However, each port on a router is also a single broadcast domain. Therefore, traffic crossing from one broadcast domain to another broadcast domain must go through a router.

Alcatel-Lucent C


ot Distribute



Layer 1 Devices

A repeater retransmits the Ethernet signal down a wire and amplifies it to be used again. The repeater extends the reach ofEthernet in a LAN. A hub works exactly like a repeater, with the exception that it

functions less as a distance extender and more like a port concentrator of several hosts in one physical area.

HubRepeater

Alcatel-Lucent C


ot Distribute



Layer 1 Devices Repeater

Connects network segments Retimes and regenerates signals to proper amplitudes Disadvantage propagation delay due to broadcasting Disadvantage physical limit to the number of repeaters used

Repeater

Alcatel-Lucent C


ot Distribute



Layer 1 Devices Hub

A single Ethernet segment device that can operate at 10/100/1000 Mb Can act as a repeater Disadvantage Same as repeater Used in small home networks or isolated segments in larger

networks

Hub

Alcatel-Lucent C


ot Distribute



Bridging and Bridges

Bridging is a layer 2 (L2) concept. Bridging is primarily associated with Ethernet. A bridge (or switch) operates at L2 of the OSI model. A bridge is an intelligent device that does an L2 address lookup.

OSI Model

Bridge

Application

Presentation

Session

Transport

Network

Data Link

Physical

L2 Network Device

Bridge

Alcatel-Lucent C


ot Distribute



Switches

A switch is a multiple Ethernet segment device that can have dedicated 10/100/1000 Mb ports. Traffic in isolated segments is switched via a high-speed,

bandwidth-dedicated backplane called a fabric. The majority of modern switches function in store/forward.

Switch

L2 Network Device

A store/forward switch requires the whole Ethernet frame (packet) to be received before it can be forwarded. Although this may suggest higher network latencies due to larger frame sizes, high-speed switching hardware and interfaces mean that this is usually not a problem.

Alcatel-Lucent C


ot Distribute



A router, unlike a bridge, operates up to L3 of the OSI model.A router connects two different network segments.

Routing

OSI Model

Router

L3 Network Device

Router

Application

Presentation

Session

Transport

Network

Data Link

Physical

Basic router functions: Examine the IP header of the incoming packet for

the destination IP address Look up this address in its routing table Determine the best path to the destination IP

address Determine the egress interface for the above path Forward the data out of this egress interface

L3 Devices Routers

Alcatel-Lucent C


ot Distribute



ETHERNET

IP

TCP/UDP

DATA

ATM

IP

TCP/UDP

DATA

Ethernet

Ethernet/ ATM

ETHERNET

IP

TCP/UDP

DATA

ETHERNET

IP

TCP/UDP

DATA

DATA

POS

IP

TCP/UDP

DATA

ETHERNET

IP

TCP/UDP

PPP

IP

TCP/UDP

DATA PPP

1

10 9

6

43

2

8

5

7

L2 Encapsulations

Encapsulated data enters the ingress Ethernet switch on the top left via Ethernet interface 1 and leaves the switch via interface 2. Because both the ingress and egress interfaces for the Ethernet switch are Ethernet line cards, the Ethernet switch simply transmits the Ethernet frame, unchanged, out the egress interface. The data frame is still referred to as an Ethernet frame or layer 2 frame.

When the L2 frame reaches the router at interface 3, the router strips off the Ethernet header, looks into the next encapsulation, which is the IP header, and forwards the frame based on the IP header only via interface 4.

Basic router functions:

1. Examine the IP header of the incoming packet for the destination IP address.

2. Look up this address in its routing tables.

3. Determine the best path described in the routing table for the destination IP address.

4. Determine the egress interface for the above path.

5. Forward the data out of this egress interface.

Assuming that the next router decides to forward this data packet out of interface 6 because this interface is connected to a PPP-based L2 switch, egress interface 6 of the router encapsulates the IP frame with a PPP header and sends the data to the PPP device.

If the router decides to forward the data packet via interface 7, to the next router and then out to interface 8, the egress interface at 8 would add an ATM header to the IP frame because it is connected to ATM interface 9 on the Ethernet/ATM switch.

Note: Although only the IP header is relevant during the routing of the data packet, the data packet is encapsulated at router interfaces 4, 5, and 7 by the appropriate L2 headers.

Alcatel-Lucent C


ot Distribute



Module Summary

TCP/IP and OSI protocol suites provides a common framework to allow the interworking of diverse network hardware and computer systems TCP/IP protocol suite has 4 layers:y Application Servicesy Transporty Internet Protocoly Network Interfaces

Alcatel-Lucent C


ot Distribute



Module Summary (contd)

OSI protocol suite has 7 layers:y Applicationy Presentationy Sessiony Transporty Networky Data Linky Physical

Routers are layer 3 devices, switches are layer 2 devices and hubs & repeaters are layer 1 devices At each layer of the TCP/IP or OSI suite data is

encapsulated in the appropriate format

Alcatel-Lucent C


ot Distribute



Learning Assessment

1. Which of the following applications fall under the application layer of the OSI model? (Select all that apply)A. MS WordB. TelnetC. NotepadD. FTP

2. Which layer is responsible for providing reliable communications?A. SessionB. ApplicationC. Physical D. TransportE. NetworkF. Data linkG. Presentation

Alcatel-Lucent C


ot Distribute



Learning Assessment (continued)

3. Which of the following devices operate at the physical layer? (Select all that apply)A. RouterB. RepeaterC. HubD. Switch

4. Which of the following are layer 2 encapsulations?(select all that apply)

A. ATMB. PPPC. IPD. Ethernet

Alcatel-Lucent C


ot Distribute

www.alcatel-lucent.com

3HE-02767-AAAA-WBZZA Edition 01

Alcatel-Lucent C


ot Distribute


Module 2 7x50 SR/ESS Components and CLI

Alcatel-Lucent C


ot Distribute



Module Objectives

After successful completion of this module, you should be able to: Understand the hierarchical structure of the 7x50 CLI Understand basic CLI commands Understand the concepts of configuring the hardware of the

7x50 product line Understand the physical access options of the 7x50 Understand basic system configuration Understand the purpose of the BOF

Alcatel-Lucent C


ot Distribute

7x50 SR/ESS Components and CLI

Section 1 Hardware Configuration

Alcatel-Lucent C


ot Distribute



Alcatel 7450 Ethernet Service Switch Group

Integrated switch fabric/control, IOM, and power

20 Gb/s full duplexsystem capacity

Two 10 Gb/s MDAsOver-subscription of

some MDAs availablePower redundancy

7 Slots (5 IOM, 2 SF/CPM)100 Gb/s full duplex system capacity 200 Gb/s switch fabric/ controlFabric/control redundancyFive 20 Gb/s IOMsTen 10 Gb/s MDAsOver-subscription of some MDAs availablePower redundancy

Slot

MDA

1 2

12345AB

ESS-7ESS-1

Alcatel-Lucent C


ot Distribute



Alcatel 7450 Ethernet Service Switch Group

10 Slots (10 IOM, 2 SF/CPM)400 Gb/s full duplex system capacity 400 Gb/s switch fabric/ controlFabric/control redundancyTen 20/40 Gb/s IOMsOver-subscription of some MDAs availablePower redundancy

6 Slots (4 IOM, 2 SF/CPM)80 Gb/s full duplex system capacity 80 Gb/s switch fabric/ controlFabric/control redundancy4 10/20 Gb/s IOMsOver-subscription of some MDAs availablePower redundancy

ESS 6

ESS 12

Alcatel-Lucent C


ot Distribute



Alcatel 7750 Service Router Family

Three chassis options 1, 7, and 12 slots Carrier-class reliability combined with high

density in a small footprint System capacities scalable from 20 Gb/s to

200 Gb/s Modular design for the SR-7 and SR-12removable IOM, SF/CPM,

and MDAs Common operating system

12345AB

Slot

MDA

1 2

SR-7

MDA

1 2

A1 SR-1

Slot

1 2 3 4 5 A B 6 7 8 9 10

1

MDA

2

SR-12

Alcatel-Lucent C


ot Distribute



Alcatel 7750 SR SF/CPM Cards

Redundant SF/CPMs supported on

SR7 and SR12

Alcatel-Lucent C


ot Distribute



Alcatel 7750 SR IOM, MDAs, and SFPs

Small Form-Factor Pluggable (SFP) optics

2 MDAs per IOM

10 IOMs per SR-125 IOMs per SR-7

IOMs and MDAs are hot-swappable

IOM - Input/Output Module

IOMs are hot-swappable modules responsible for connecting to standard physical interfaces. It contains two 10Gbps traffic-processing programmable fast path complexes. Each complex supports a pluggable Media Dependent Adapter (MDA) that allows a common programmable fast path to support all of the possible interface types. The IOM also contains a CPU section for managing the forwarding hardware in each flexible fast path.

MDA - Media Dependent Adapters

MDAs provide one or more physical interfaces, such as Ethernet, ATM or SONET/SDH. MDAs pass incoming packets to the IOM for processing, and transmits outgoing packets out the appropriate physical interface in the correct format.

SFP Small Form Factor Pluggable interfaces

SFPs transceivers are small optical modules available in a variety of formats.

Alcatel-Lucent C


ot Distribute



Alcatel 7x50 Service Router System Components

Switch Fabric

Control Plane

Media Dependent

Adapter(MDA)

Flexible Fast Path Complex

CPU

Media Dependent

Adapter(MDA)


CPU

CPU

FFPC

Media Dependent

Adapter(MDA)


I/O Module

CPU

Media Dependent

Adapter(MDA)


Control Plane

SF/CPM Module

Data plane operationData coming in from the remote network/customer site, ingresses through the Media dependent adapters, where the data is formatted (internal format). The data is then processed in the I/O module where the decision to switch happens (L2/L3 Forwarding information lookup) and the data packets are sent to the switch fabric. The switch fabric then forwards the data to the appropriate IOM from where its sent to the appropriate MDA.

The data plane operation happens after the control plane has built the forwarding information and stored them in the IOM.

Control plane operationControl messages ingress the 7x50 in a manner similar to the data packets, except they are processed further by the control plane.

Alcatel-Lucent C


ot Distribute



Comparisons between the 7450 ESS and 7750 SR

MDA

RedundancyPwr/Control

Platforms

Purpose

Type

All Ethernet, ATM, POS, DS3/OC3 channelized

Ethernet, POS

SR-7 and SR-12ESS-6,7 and ESS-12

SR-1, SR-7, SR-12ESS-1, ESS-6, ESS-7 and ESS-12

Support Ethernet, ATM, Frame relay and VPRN services

Primarily designed to support Ethernet aggregation services

7750 Service Router7450 Ethernet Service Switch

Alcatel-Lucent C


ot Distribute


Section 2 CLI Commands

Alcatel-Lucent C


ot Distribute



Command Line Interface

Alcatels 7750 SR CLI is a command-driven interface accessible through the console, Telnet and SSH. The CLI is used for configuration and management of 7750

SR routers. The CLI command structure is a hierarchical inverted tree. The highest level is root. Navigation down the hierarchy tree is performed by typing

the names of submenus. Global commands can be used anywhere in the hierarchy.

The Alcatel 7750 SR CLI is a command-driven interface accessible through the console, Telnet and SSH. The CLI can be used for the configuration and management of 7750 SR routers.

The 7750 SR CLI command tree is a hierarchical inverted tree. At the highest level is root. Below root are other levels with the major command groups; for example,

configuration commands and show commands are levels below root.To move up in the hierarchy, enter the command node name (sometimes a parameter must be provided).

Navigate down the tree by typing the name of the successively lower contexts. For example, typing configure or show at the root level navigates down to the configure or show context, respectively. Global commands, such as back, exit, info, and tree, can be entered at any level in the CLI hierarchy.

Sometimes the context can be specified in a specific context with a single keyword, such as:

SR>config# router

SR>config>router#

Sometimes a keyword and a user-supplied identifier are required:

SR>config>router# interface system

SR>config>router>if#

Viewing the CLI Tree StructureYou can view the hierarchical CLI command structure below your current position with the tree and tree detailcommands.

Displaying Configuration ContextsUse the info and info detail commands to display information about the current context level.

info displays non-default information

info detail displays all configuration information, including defaults

Alcatel-Lucent C


ot Distribute



CLI Command Prompt

Example of configuring OSPF:

SR1>config>router>ospf#

Example of creating a new router interface:

SR1>config# router interface Toronto SR1>config>router>if$ address 131.131.131.1/30

Host name SR1 Context separator

At the end of the prompt, there is either a pound symbol (#) or a dollar symbol ($). A # symbol at the end of the prompt indicates that the context is an existing context. A $ symbol at the end of the prompt indicates that the context has been newly created.

Alcatel-Lucent C


ot Distribute



Command Completion

Command completion can be achieved by:

1. Abbreviation, if the keystrokes entered are unique.SR1>config>router>os [ENTER]SR1>config>router>ospf#

2. Tab Key or Space Key to automatically complete the command.SR1>config>router>os [TAB]SR1>config>router>ospfSR1>config>router>os [SPACEBAR]SR1>config>router>ospf

If a match is not unique, the CLI displays possible matches:SR1>config# ro [TAB]

router router-ipv6SR1>config# router

The system maintains a history of previously entered commands. The history command displays the previous 30 commands entered.

Alcatel-Lucent C


ot Distribute



CLI Navigation

Console Control Commands Console control commands are used for navigating a CLI

session and displaying information about a console session. The following is a list of some of the more commonly used global commands (see next page for additional commands): Aborts the pending command Terminates the pending command line and

returns to the root context echo Echoes the text that is typed (primary use is to

display messages in an exec file)

When you enter a CLI command, you move from one command level to another. When you start a CLI session, you begin in the root context. Navigate to another level by entering the name of successively lower contexts. For example, enter either the configure or show commands at the root level to navigate to the config or show context, respectively.

Other navigation methods include:

Move down the hierarchy by entering the level; for example, config. Move up one level in the hierarchy by entering the keyword back. Move several levels down in the hierarchy by entering multiple contexts separated by spaces. For example: #config router

ospf

See Console Control Commands below for explanations of exit, exit all and .

Some contexts are specified with a single keyword, such as router, and others require a keyword and a user-supplied identifier such as interface interface-name.

Console Control Commands

Console control commands are used for navigating in a CLI session and for displaying information about a console session. Many of these commands are global commands, which means they can be executed at any level of the CLI hierarchy.

The following are some of the more commonly used global commands (see the next page for additional commands):

Aborts the pending command

Terminates the pending command line and returns to the root context

This is a special keyboard sequence that acts like pressing the key and entering exit all to return the user to the root context.

back Navigates the user to the parent context

echo Echoes the text that is typed (primary use is to display messages within an exec file)

exec Executes the contents of a text file as if they were CLI commands entered at the console

exit Returns the user to the previous higher context

exit all Returns (moves up) the user to the root context

help Displays a brief description of the help system

? Lists all commands in the current context

history Displays a list of the most recently entered commands (like history in UNIX shell environments)

info Displays the running configuration for a configuration context

Alcatel-Lucent C


ot Distribute



CLI Navigation (continued)

back Brings you back one contextexit all Brings you back to the root levelup/down arrow Lists previous command(s) to be repeated tree Shows available commands from context

SR1>config>router>ospf# tree ospf|+---area| || +---area-range| || +---blackhole-aggregate| || +---interface| | || | +---advertise-subnet| | |

Alcatel-Lucent C


ot Distribute



CLI Navigation (continued)

The shutdown command can be used to disable protocols and interfaces. The no form of any command may have one of two results: The removal from the configuration (i.e., no ospf). Reset to default settings (i.e.,

config>ospf>area>interface>no hello-interval)

The shutdown command does not change, reset, or remove any configuration settings or statistics. Many objects must be shut down before they can be deleted. A shutdown is saved in the configuration file. All ports are shut down by default when the system is first powered on.

To restore the settings after issuing a no command, you must reconfigure the router, reboot from a configuration file that has the correct configuration, or do an exec command on a configuration file that contains the correct settings. You can use an exec command to process a configuration file and restore the configuration stored in the file.

Alcatel-Lucent C


ot Distribute



Info provides info on the configurationlogout Terminates the CLI sessionoam OAM test suite (see the Service OAM section of the 7750 SR OS

Services Guide)password Changes the user CLI login password

Note: Not a global command; must be entered at the root level.ping Verifies the reachability of a remote hostpwc Displays the present or previous working context of the CLI

sessionsleep Causes the console session to pause operation (sleep) for 1

second or for the specified number of seconds (primary use is tointroduce a pause during the execution of an exec file)

ssh Opens a secure shell connection to a hosttelnet Telnet to a hosttraceroute Determines the route to a destination addresstree Displays a list of all commands at the current level and all

sublevelswrite Sends a console message to a specific user or to all users with

active console sessions

CLI Global Commands

Refer to the 7750 SR OS System Guide for detailed information about CLI commands and navigation.

Alcatel-Lucent C


ot Distribute



alias Enables the substitution of a command line by an alias

create Enables the create parameter check

more Configures whether CLI output should be displayed 1screen at a time, awaiting user input to continue

reduced-prompt Configures the number of higher-level CLI contextlevels to display in the CLI prompt

terminal Configures the terminal screen length for the current CLIsession

time-display Specifies whether time should be displayed in local or UTC format

CLI Environment Commands

CLI environment commands are used to customize session preferences for a single CLI session.


Alcatel-Lucent C


ot Distribute



Help Displays a brief description of the help system

? Lists all commands in the current context

string ? Lists all commands available in the current context that start with string

command ? Displays the commands syntax and associated keywords

command keyword ? Lists the associated arguments for keyword in command

string Completes a partial command name (auto-completion) or listsstring available commands that match string

Help Edit Displays help on editing (editing keystrokes)Lists the available editing keystrokes

Help Globals Displays help on global commandsLists the available global commands

Finding Help

The tree and tree detail system commands are help commands that are useful when you search for a command in a lower-level context.


Alcatel-Lucent C


ot Distribute



File System CLI Context

File system is DOS based and is used to store software image, configuration files and event logsFile commands can be used to create, copy, move, remove files and directories

RootFile Attrib

CdCopyDeleteDirMdMoveRdScpTypeVersion

Displays the version of a 7750 SR OS cpm.tim or iom.tim file.version

Display the contents of a text file.type

Copies a file from the local files system to a remote host on the network. scp uses ssh for the data transfer, and uses the same authentication and provides the same security as ssh.

scp

Moves a local file, system file, or a directory. If the target already exists, the command fails and an error message displays.

move

Deletes the specified file. The optional wildcard (*) can be used to delete multiple files that share a common (partial) prefix and/or (partial) suffix.

Delete

Alcatel-Lucent C


ot Distribute


Section 3 Boot Process

Alcatel-Lucent C


ot Distribute



Basic Boot Up components

Uses a Boot Option File (BOF) to start the systemStored in the compact flash CF3Other components required for startup Boot loader BOF configuration file TiMOS-m.n.Y.Z software image file Default config file

Basic Operating SystemThe 7750 SR does not use a BOOT PROM to start the system; instead, it uses a Boot Option File (BOF).

Each new system is shipped with a Compact Flash (CF) card that contains the files required to start a 7750 SR system. The system files are stored on CF3 and that is where the system looks for the files when initializing.

The CF3 card contains the following directories and files located off of the root directory:

Boot.ldrThis file contains the system bootstrap image.

Bof.cfgThe Bof.cfg file is user configurable and contains information such as:

Management port IP address

Location of the image files (primary, secondary, and tertiary)

Location of the configuration files (primary, secondary, and tertiary)

TiMOS-m.n.Y.zThis is a directory this is named according to the major and minor software release, type of release and version.

For example, if the software release is Version 1.2 of a released software version the name would be:

TiMOS 1.2.R.0

On an SR7, and SR12 this directory contains two files, cpm.tim and iom.tim, for the SF/CPM and IOM cards respectively. Since the SR-1 has an integrated fabric/control and I/O, there is only one file, named both.tim.

Config.cfgThis file contains the default configuration file. The default configuration file is very basic and provides just enough information to make the system operational.

You can create other configuration files and point the system to them using the bof.cfg file.

Alcatel-Lucent C


ot Distribute



Software Release Media

Root

config.cfg TiMOS-m.n.Y.z

cpm.tim iom.tim

boot.ldr

Bootstrap Image

Default Configuration

File

CPMImage

File

bof.cfg

Boot Option

File

IOMImage

File

m Major release number n Minor release numberY A Alpha Release

B Beta ReleaseM Maintenance Release R Released SoftwareI Internal Engineering and Test Release

z Version number.

Alcatel-Lucent C


ot Distribute



System Initialization

START

Load & Execute boot strap loader

(cf3:\boot.ldr)

Processboot option file(cf3:\bof.cfg)

InitializeHardware

Waitrequired

Get runtime image(3 possible locations)

YN

Get config(3 possible locations)

Image OK ?

StartupFailed

N

Y

Config found ?

Boot with DefaultsSNMP shutdown

Issue TrapIssue Log entry

Issue Console msg

N

NeedPersistence

?

Y

Config FileProcessed OK

Log InPrompt

N

Y

Y

NPersistenceFile Processed

OK

Y

NUser intervention point:

1

User activity detected

SNMP shutdownIssue Trap (if possible)

Issue Log entryIssue Console msg

Processpersistence

andConfiguration

files

1

ProcessConfig File

The configuration file includes chassis, IOM, MDA, and port configurations, as well as system, routing and service configurations.

PersistenceYou can configure the BOF to turn persistence On or Off (default is Off). Persistence is required if the 7450 is managed by the 5620 SAM network manager. When persistence is turned on the 7450 SR creates an index file with the same file prefix name as the current configuration file. The index file contains variable index information (i.e. interface indexes, LSP ids, path ids, etc.). The index file is built dynamically by the 7450 operating system and does not contain configuration information entered by users. The index file is saved whenever the system configuration file is saved.

The index file ensures that the 5620 SAM has the same index data as the 7450 ESS node after a system reboot. If a 7450 reboots and the indexes stored on the SAM do not match the node indexes, a complete re-synchronization between the node and the SAM takes place automatically. This can be a very time consuming and processor intensive operation.

If a node reboots with persistence turned on, it must locate the persistence index file and successfully process it before processing the system configuration file.

If the index file cannot be processed for some reason, the system performs an SNMP shutdown (Get and Set functionality is disabled), however traps will continue to be issued. The system issues traps, log messages, and console messages to advise the user. It requires a no shutdown SNMP to reactivate full SNMP functionality.

Alcatel-Lucent C


ot Distribute



Boot Options File

Stores parameters that specify the location of the image filename that the router will try to boot from and the configuration file that the router uses to configure the applications and interfacesThe most basic BOF configuration should have the following: Primary address Primary image location Primary configuration location

Alcatel-Lucent C


ot Distribute



BOF Parameters

BootOptionFile

Alcatel 7750 SR uses the BOF file to perform the following tasks:

1) Set up the CPM Ethernet port (speed, duplex, auto)2) Create an IP address for the CPM Ethernet port3) Create a Static route for the CPM Ethernet port4) Set the console port speed.5) Configure the DNS Domain name6) Configure Primary, Secondary, Tertiary configuration source7) Configure Primary, Secondary, Tertiary image source8) Configure persistence requirements

Always be sure to save the BOF!

Parameters that are configured in the BOF are shown in the chart above. Configuration of the BOF is done in the BOF CLI context.

Sample BOF file commands:

SR-1# buff cf3 # Change or create a buff file on media cf3

SR-1>buff# address 10.10.10.2/24 primary # Change or create the CPM Ethernet Port IP address (must be entered from console)

SR-1>buff# speed 100 # Set the CPM Ethernet Port speed to 100 Mbps.

SR-1>bof# primary-image cf3:/TIMOS.1.0.R0 # Set the primary image directory

SR-1>bof# primary-config cf3:/test.cfg # Set the primary configuration file to be test.cfg

SR-1>bof# save # Saves the bof

Show Commands:

SR-1>show bof Displays the in-memory bof file (last used)

Alcatel-Lucent C


ot Distribute



Show BOF

A:sr1a# show bof===============================================================================BOF (Memory)===============================================================================

primary-image cf3:\4.0.R9primary-config cf3:\test\test_sr1a.cfgaddress 138.120.199.60/24 activeautonegotiateduplex fullspeed 100wait 3persist onconsole-speed 115200

===============================================================================

The slide above shows the information that is contained in the boot options file. The primary image location is one of the most important items in the BOF. If the router cannot find an image, it will remain in the boot cycle forever.

In this example, the primary configuration is located in CF1. Therefore, when the router reboots, it goes to CF1, gets the configuration that is specified in the BOF, and loads the router with that configuration. In addition, after the primary configuration location has been defined, every time the operator inputs the command admin save, the current configuration is saved to the primary configuration file.

The address that is referred to in the slide above is the address of the management port on the CPM. Notice the console speed; this is the default speed of the RS-232 port on the CPM. This speed can be changed here in the BOF.

Setting the CPM Ethernet Port AddressUse the following command to assign an IP address to the active CPM in the running configuration and the BOF or the standby CPM for systems that use redundant CPMs.

SR1# bof

SR1>bof# address (or e.g.,SR7>bof# address )SR1# show bof

Alcatel-Lucent C


ot Distribute



Compact Flash

Each Control/Switch processor on a 7x50 product can have 3 compact flashes, cf1:, cf2:, cf3: Flash size can be 256M, 512M, 1G and 2G By default the system startup looks for the boot.ldr file in

cf3 cf3 can store the runtime image, the running configuration Requires a shutdown of the compact flash before removing

it Compact flash 1 and 2 can be used to store

debug/accounting logs

Alcatel-Lucent C


ot Distribute


Section 4 Basic Router Configuration

Alcatel-Lucent C


ot Distribute



Physical Access

OOB-CPMManagement

EthernetPort

In-band

Customer-Facing

Access Ports&

Network Portsare located on

MDAs

CPM Console Port

SF/CPM (Switch Fabric/Control Processor Module) Card Common to the SR-7 and 12

SR-1

The 7750 SR can be accessed in three ways:

In-band ports These are access ports and network ports on MDAs.

Console port A DB-9 serial port; this port is enabled by default. The default settings are:

Baud Rate: 115,200

Data Bits: 8

Parity: None

Stop Bits: 1

Flow Control: None

CPM Ethernet port A 10/100 Ethernet management port.

Alcatel-Lucent C


ot Distribute



Initial System SETUP

The following steps are typically used to configure a system from start up Login to the SR/ESS using console input Configure System name and changing admin user password Configure CPM Ethernet management IP address Configure additional BOF parameters Configure IOM cards Configure MDA cards View Alarms Configure system address Configure Logs if required View entire running config

Alcatel-Lucent C


ot Distribute



Initial System SETUP (contd)

Set the system name >config>system# name SR-1

Configure the CPM Ethernet port IP address

SR-1# bofSR-1>bof># address 10.1.1.1/32SR-1>bof# saveSR-1>bof# exit

Change admin user password

SR-1# passwordEnter current password: Enter new password: Re-enter new password:

Basic System Management ConfigurationSome basic configuration on the 7750 SR is required before putting it into service: System name Change admin password CPM Ethernet management port IP address Configure IOMs, MDAs, and ports

System NameThe system name can be any ASCII printable string of up to 32 characters. The system name is configured in the config CLI context. If the name contains spaces, it must be enclosed in double quotes to delimit the start and end of the name. The system name becomes part of the CLI prompt.

PasswordsThe default login and password is admin. This password should be changed before your router is put into service.The system automatically creates at least one admin user (the default) and must retain at least one admin user unless you are using an external protocol such as RADIUS or TACACS+ to provide authentication.

You can configure the following password parameters:

Aging The maximum number of days (1 to 500) that a password remains valid before the user must change it. The default is no aging enforced.

Attempts The number of unsuccessful login attempts allowed in a specified time period. If the configured threshold is exceeded, the user is locked out for a specified time.

Count: 4Time (minutes): 10Lockout (minutes): 10

In the example above, a user is locked out for 10 minutes if 4 unsuccessful login attempts in occur in a 10-minuteperiod.

Authentication Order You can configure the order in which password authentication is attempted among RADIUS, TACACS +, and local methods.

Complexity You can use this parameter to specify if passwords must contain upper- and lowercase characters, numeric, and special characters.

Minimum Length You can specify the minimum number of characters (1 to 8) required for a password.

Alcatel-Lucent C


ot Distribute



Show Card

A:sr1a# show card 1

===============================================================================Card 1===============================================================================Slot Provisioned Equipped Admin Operational

Card-type Card-type State State -------------------------------------------------------------------------------1 iom-20g-b iom-20g-b up up ===============================================================================

Show CardThe slide above shows the output of a show card command. The output shows that the card slot is configured to support all IOMs. The next columns show which card the slot is configured to accept and then which card is actually installed in the slot. These two entries must match. Finally, the administrative and operational states should both be up.

Alcatel-Lucent C


ot Distribute



Show MDA

A:sr1a# show mda

===============================================================================MDA Summary===============================================================================Slot Mda Provisioned Equipped Admin Operational

Mda-type Mda-type State State -------------------------------------------------------------------------------1 1 m5-1gb-sfp-b m5-1gb-sfp-b up up

2 m16-oc3-sfp m16-oc3-sfp up up ===============================================================================

Show MDAThe slide above shows the output of a show mda command. The output shows the card slot that is being referenced, in this case card 1, and then the MDAs that are supported by the IOM in card slot 1. In this case, all MDAs are supported.

Next is which MDA is the IOM slot configured to accept, the actual MDA that is installed in the IOM MDA slot, and the status of the MDA.

Alcatel-Lucent C


ot Distribute



Admin display-config

A:acie_sr1a# admin display-config # TiMOS-B-4.0.R9 both/hops ALCATEL SR 7750 Copyright (c) 2000-2007 Alcatel-Lucent.# All rights reserved. All use subject to applicable license agreements.# Built on Tue Dec 19 15:56:05 PST 2006 by builder in /rel4.0/b1/R9/panos/main

# Generated FRI DEC 22 16:00:41 2006 UTC

exit allconfigure#--------------------------------------------------echo "System Configuration"#--------------------------------------------------

systemname "acie_sr1a"snmp

shutdownexitlogin-control

Press any key to continue (Q o quit)

Admin display-configThe slide above shows a partial output of the admin display-config command. The first portion of the output shows the current version of the operating system that is running on the router. The router then outputs the entire configuration of the router, down to the port level. This command can output a large number of pages on a fully configured router.

Alcatel-Lucent C


ot Distribute



Info Command

The info command provides informational display during configuration without the need to use the show configcommand.

A:Training1>config>router# interface TorontoA:Training1>config>router>if# info----------------------------------------------

address 131.131.131.1/30port 1/1/1

----------------------------------------------

You can view more details by using the detailed version of the info command: info detail

Alcatel-Lucent C


ot Distribute



Logs

Record Events, Alarms, Faults that result from actions performed on the 7X50Can be used to record debug messages for trouble shootingLog Sources Main - most normal logs Security - any attempt to breach system security Debug - events as a result of turning debug tracing on Change - any events that change configuration of the node

Log Destinations Console, Session Memory, File SYSLOG Server SNMP Trap Group

7x50 Logs

The 7x50 ESS keeps very extensive logs of events, alarms, traps, and debug/trace messages. The logs are used to monitor events and troubleshoot faults in the 7450. You can configure what type of logging information is captured and where you want to send the captured logging information.

Log Sources

Applications and processes within the 7450 generate event logs. The logs are divided into four streams:

Main most normal logs not specifically directed to any other event stream.

Security any attempts to breach system security, such as failed login attempts.

Change any events that affect the configuration or operation of the node.

Debug/Trace all output generated as a result of turning on debug/trace.

Forwarded events are placed into an event log. Each event log has a log identification (log-id) number and can contain events from more than one event stream.

Log Destinations

You can configure the destination for the contents of a log-id. A log-id can be directed to one of the following destinations:

Console the physical 9-pin console port of the 7450.

Session a console or Telnet session. Sessions are temporary log destinations that are valid only as long as the session lasts.

Memory a circular buffer where the oldest entry is overwritten when the buffer is full.

File event logs and accounting policy information can be directed to a file.

Syslog event log information can be sent to a syslog server.

SMNP Trap Group event log information can be sent to an SNMP trap group. All events and traps are time-stamped and numbered per destination. Traps are sequence-numbered per destination and stored in memory. If the 7450 NMS should go offline for some reason it may not receive some trap notifications. When the NMS comes back online it will automatically recognize that it has missed some trap notifications because the last sequence number it has will be different from the sequence number in the 7450. The NMS will then update its records with the missing traps. If the in-memory notification log become full and some records are overwritten the NMS will resynchronize itself with

the 7450.

Alcatel-Lucent C


ot Distribute



Configuring Logs

Main

Event ControllerLog event?

Security Change Debug

Optional Filter Policy

YesNo

Garbage

Sources

Session File Memory SNMP

Log Id 10 Log Id 13Log Id 11 Log Id 12

Configuring Logs

Steps1. Configure a log id with a number from 1-98

2. Identify the source

3. Specify an optional filter to filter events if desired

4. Identify the destination

5. Examine the logs to view the events

Alcatel-Lucent C


ot Distribute



CLI for Configuring Logs

A:PE1>config# log filter - filter - no filter

: [1..1001]

[no] default-action - Specify the default action for the event filter[no] description - Description string for the event filter[no] entry + Configure an event filter entry

A:PE1>config# log filter 14

A:PE1>config>log>filter$ description "default filter"A:PE1>config>log>filter$ default-action forward A:PE1>config>log>filter$ back

A:PE1>config>log>filter# info detail ----------------------------------------------

default-action forwarddescription "default filter"

----------------------------------------------

Alcatel-Lucent C


ot Distribute



CLI for Configuring Logs (contd)

A:PE1>config>log# log-id 14A:PE1>config>log>log-id# from debug-trace A:PE1>config>log>log-id# to session A:PE1>config>log>log-id# filter 14

A:PE1>config>log>log-id# info detail ----------------------------------------------

no descriptionfilter 14 time-format utcfrom debug-traceto sessionno shutdown

----------------------------------------------A:PE1>config>log>log-id#

General Log Commands

Show log applications

Show log event-control

Show log file-id

Show log filter-id

Show log log-collector

Show log log-id

Show log snmp-trap-group

Show log syslog

Alcatel-Lucent C


ot Distribute



Default Alarm Logs

There are two default logs Log 99 All severity levels of alarms Log 100 Only serious errors

To view the logs use the following commands: Show log log-id 99 Show log log-id 100

More granular data mining of the two log files can be accomplished: Show log log-id 99 subject 1/1/1 port specific Show log log-id 99 application chassis chassis related alarms Others exist.

Only store about 500 entries. If more entries are required then specific alarm logs need to be created

How to show Layer 1 & Layer 2 alarms7X50 has two default memory logs (Log-id 99 & 100) containing all the events from the main application. All severity levels of alarms are recorded in log-id 99, where log-id 100 only contains serious errors.

There are several ways to view the alarms of a specific subject, such as alarms related to a particular port. One method is to create a new log that only monitors the specific subject.

Alcatel-Lucent C


ot Distribute



Default Logs Alarm Monitoring Example

The show log commandA:PE1>config>log>log-id# show log log-id 99===================================================================Event Log 99===================================================================Description : Default System LogMemory Log contents [size=500 next event=25 (not wrapped)]

24 2006/08/17 15:30:55.29 UTC WARNING: SYSTEM #2006 - CHASSIS"tmnxMDATable: Slot 1, MDA 2 configuration modified"

23 2006/08/17 15:30:55.29 UTC WARNING: SYSTEM #2007 - PORT"Pool on Port 1/2/b.net-sap Modified managed object created.5 2006/08/17 15:30:55.29 UTC MINOR: CHASSIS #2004 - Mda 1/2"Class MDA Module : wrong type inserted"

The show log log-id 99 application chassis command details any and all alarms that have been logged within the router. In the above case the detailed information only shows minor alarms from the individual modules being inserted into the chassis. Noting the time, these entries were from when the router first booted.

Alcatel-Lucent C


ot Distribute



Module Summary

7x50 product CLI commands and navigation Useful commands System startup and boot files Boot Options File (BOF) and default configuration files Basic system and hardware configuration Logs and alarms

Alcatel-Lucent C


ot Distribute



Learning Assessment

1. What information does the BOF contain?2. What is the CLI context in which interfaces are configured?3. What command can be used to view the status of the MDAs?4. List the possible log sources.5. How many default logs are there, and what info do they

provide?

Alcatel-Lucent C


ot Distribute


Alcatel-Lucen

Documents

Alcatel-Lucent Scalable IP Networks Student Guide v1-1