7210 SAS D, E, K OS Router Configuration
Guide
Release 9.0.R1
3HE11494AAAATQZZA
Issue: 01
November 2016
Nokia — Proprietary and confidential.
Use pursuant to applicable agreements.
7210 SAS D, E, K OS Router Configuration
Guide
Nokia is a registered trademark of Nokia Corporation. Other products and company
names mentioned herein may be trademarks or tradenames of their respective
owners.
The information presented is subject to change without notice. No responsibility is
assumed for inaccuracies contained herein.
Contains proprietary/trade secret information which is the property of Nokia and must
not be made available to, or copied or used by anyone outside Nokia without its
written authorization. Not to be used or disclosed except in accordance with
applicable agreements.
7210 SAS D, E, K OS Router Configuration GuidePage 7
7210 SAS D, E, K OS Router Configuration GuidePage 8
About This Guide
This guide describes logical IP routing interfaces, IP and MAC-based filtering support provided by
the 7210 SAS D, E, K OS and presents configuration and implementation examples.
On 7210 SAS devices, not all the CLI commands are supported on all the platforms and in all the
modes. In many cases, the CLI commands are mentioned explicitly in this document. In other
cases, it is implied and easy to know the CLIs that are not supported on a particular platform.
NOTE: 7210 SAS-E and 7210 SAS-D operate in access-uplink mode by default. No explicit user
configuration is needed for this.
Preface
Audience
This document is organized into functional chapters and provides concepts and descriptions of the
implementation flow, as well as Command Line Interface (CLI) syntax and command usage.
This manual is intended for network administrators who are responsible for configuring the 7210
SAS-Series routers. It is assumed that the network administrators have an understanding of
networking principles and configurations. Protocols, standards, and services described in this
manual include the following:
•IP router configuration
•Virtual routers
•IP and MAC-based filters
7210 SAS D, E, K OS Router Configuration GuidePage 9
Preface
List of Technical Publications
The 7210-SAS D, E, K OS documentation set is composed of the following books:
•7210-SAS D, E, K OS Basic System Configuration Guide
This guide describes basic system configurations and operations.
•7210-SAS D, E, K OS System Management Guide
This guide describes system security and access configurations as well as event
logging and accounting logs.
•7210-SAS D, E, K OS Interface Configuration Guide
This guide describes card, Media Dependent Adapter (MDA), link aggregation group
(LAG) and port provisioning.
•7210-SAS D, E, K OS Router Configuration Guide
This guide describes logical IP routing interfaces and associated attributes such as an
IP address, port, as well as IP and MAC-based filtering.
•7210-SAS D, E, K OS Routing Protocols Guide
This guide provides an overview of routing concepts and provides configuration
examples for routing protocols and route policies.
•7210-SAS D, E, K OS Services Guide
This guide describes how to configure service parameters such as customer
information, and user services.
•7210-SAS D, E, K OS OAM and Diagnostic Guide
This guide describes how to configure features such as service mirroring and
Operations, Administration and Management (OAM) tools.
•7210-SAS D, E, K OS Quality of Service Guide
This guide describes how to configure Quality of Service (QoS) policy management.
Page 107210 SAS D, E, K OS Router Configuration Guide
Technical Support
If you purchased a service agreement for your 7210 SAS router and related products from a
distributor or authorized reseller, contact the technical support staff for that distributor or reseller
for assistance. If you purchased an Alcatel-Lucent service agreement, contact your welcome center
at:
Table 1 lists the tasks necessary to configure logical IP routing interfaces, virtual routers, IP and
MAC-based filtering.
This guide is presented in an overall logical configuration flow. Each section describes a software
area and provides CLI syntax and command usage to configure parameters for a functional area.
Table 1: Configuration Process
AreaTaskChapter
Router configurationConfigure router parameters,
including router interfaces and
addresses and router IDs.
IP and MAC filtersFilter Policies on page 81
ReferenceList of IEEE, IETF, and other
proprietary entities.
IP Router Configuration on page 15
Standards and Protocol Support on page 339
7210 SAS D, E, K OS Router Configuration GuidePage 13
Getting Started
Page 147210 SAS D, E, K OS Router Configuration
Guide
In This Chapter
IP Router Configuration
This chapter provides information about commands required to configure basic router
parameters.
Topics in this chapter include:
•Configuring IP Router Parameters on page 16
→ Interfaces on page 16
•Configuration Notes on page 21
Page 157210 SAS D, E, K OS Router Configuration Guide
Configuring IP Router Parameters
Configuring IP Router Parameters
In order to provision services on a 7210 SAS device, logical IP routing interfaces must be
configured to associate attributes such as an IP address or the system with the IP interface.
A special type of IP interface is the system interface. A system interface must have an IP address
with a 32-bit subnet mask.
The following router features can be configured:
•Interfaces on page 16
Interfaces
7210 SAS routers use different types of interfaces for various functions. Interfaces must be
configured with parameters such as the interface type (system) and address. A port is not
associated with a system interface. An interface can be associated with the system (loopback
address).
System Interface
The system interface is associated with the network entity (such as a specific router or switch), not
a specific interface. The system interface is also referred to as the loopback address.
The system interface is used to preserve connectivity (when routing reconvergence is possible)
when an interface fails or is removed. The system interface is also referred to as the loopback
address and is used as the router identifier.
Page 167210 SAS D, E, K OS Router Configuration Guide
Internet Protocol Versions
The TiMOS implements IP routing functionality, providing support for IP version 4 (IPv4) and IP
version 6 (IPv6). IP version 6 (RFC 1883, Internet Protocol, Version 6 (IPv6)) is a newer version
of the Internet Protocol designed as a successor to IP version 4 (IPv4) (RFC-791, Internet
Protocol). The changes from IPv4 to IPv6 effects the following categories:
•Expanded addressing capabilities — IPv6 increases the IP address size from 32 bits (IPv4)
to 128 bits, to support more levels of addressing hierarchy, a much greater number of
addressable nodes, and simpler auto-configuration of addresses. The scalability of
multicast routing is improved by adding a scope field to multicast addresses. Also, a new
type of address called an anycast address is defined that is used to send a packet to any one
of a group of nodes.
•Header format simplification — Some IPv4 header fields have been dropped or made
optional to reduce the common-case processing cost of packet handling and to limit the
bandwidth cost of the IPv6 header.
•Improved support for extensions and options — Changes in the way IP header options are
encoded allows for more efficient forwarding, less stringent limits on the length of
options, and greater flexibility for introducing new options in the future.
IP Router Configuration
•Flow labeling capability — The capability to enable the labeling of packets belonging to
particular traffic flows for which the sender requests special handling, such as non-default
quality of service or “real-time” service was added in IPv6.
•Authentication and privacy capabilities — Extensions to support authentication, data
integrity, and (optional) data confidentiality are specified for IPv6.
7210 SAS D, E, K OS Router Configuration Guide Page 17
Configuring IP Router Parameters
Figure 1: IPv6 Header Format
Table 2: IPv6 Header Field Descriptions
FieldDescription
Version 4-bit Internet Protocol version number = 6.
Prio. 4-bit priority value.
Flow Label 24-bit flow label.
Payload Length6-bit unsigned integer. The length of payload, for example, the rest of the
packet following the IPv6 header, in octets. If the value is zero, the payload
length iscarried in a jumbo payload hop-by-hop option.
Next Header 8-bit selector. Identifies the type of header immediately following the IPv6
header.
This field uses the same values as the IPv4 protocol field.
Hop Limit8-bit unsigned integer. Decremented by 1 by each node that forwards the
packet.
The packet is discarded if the hop limit is decremented to zero.
Source Addres128-bit address of the originator of the packet.
Destination Address 128-bit address of the intended recipient of the packet (possibly not the ulti-
mate recipient if a routing header is present).
Page 187210 SAS D, E, K OS Router Configuration Guide
IPv6 Applications for 7210 SAS-D
The IPv6 applications for 7210 SAS-D are:
•IPv6 inband management of the node using access-uplink port IPv6 IP interface
•IPv6 transit management traffic (using access-uplink port port IPv6 IP interfaces)
DNS
The DNS client is extended to use IPv6 as transport and to handle the IPv6 address in the DNS
AAAA resource record from an IPv4 or IPv6 DNS server. An assigned name can be used instead
of an IPv6 address as IPv6 addresses are more difficult to remember than IPv4 addresses.
IP Router Configuration
7210 SAS D, E, K OS Router Configuration Guide Page 19
Process Overview
Process Overview
The following items are components to configure basic router parameters.
•System interface — This creates an association between the logical IP interface and the
system (loopback) address. The system interface address is the circuitless address
(loopback)
Page 207210 SAS D, E, K OS Router Configuration Guide
Configuration Notes
The following information describes router configuration guidelines.
•A system interface and associated IP address should be specified.
•Boot options file (BOF) parameters must be configured prior to configuring router
parameters.
•IPv4 and IPv6 route table lookup entries are shared. Before adding routes for IPv6
destinations, route entries in the routed lookup table needs to be allocated for IPv6
addresses. This can be done using the CLI command config> system> resource-profile> max-ipv6-routes. This command allocates route entries for /64 IPv6 prefix route lookups.
The system does not allocate any IPv6 route entries by default and user needs to allocate
some resources before using IPv6. For the command to take effect the node must be
rebooted after making the change. Please see the example below and the Systems Basic
guide for more information.
•A separate route table (or a block in the route table) is used for IPv6 /128-bit prefix route
lookup. A limited amount of IPv6 /128 prefixes route lookup entries is supported. The
software enables lookups in this table by default (in other words no user configuration is
required to enable IPv6 /128-bit route lookup).
IP Router Configuration
•IPv6 interfaces are allowed to be created without allocating IPv6 route entries. With this
only IPv6 hosts on the same subnet will be reachable.
7210 SAS D, E, K OS Router Configuration Guide Page 21
Configuration Notes
Page 227210 SAS D, E, K OS Router Configuration Guide
Configuring an IP Router with CLI
This section provides information to configure an IP router.
Topics in this section include:
•Router Configuration Overview on page 24
•Basic Configuration on page 25
•Common Configuration Tasks on page 26
→ Configuring a System Name on page 26
→ Configuring Interfaces on page 27
•Configuring a System Interface on page 27
→ Service Management Tasks on page 31
•Service Management Tasks on page 31
→ Changing the System Name on page 31
→ Modifying Interface Parameters on page 54
→ Deleting a Logical IP Interface on page 32
IP Router Configuration
7210 SAS D, E, K OS Router Configuration GuidePage 23
Router Configuration Overview
Router Configuration Overview
In a 7210 SAS, an interface is a logical named entity. An interface is created by specifying an
interface name under the
context where objects like static routes are defined. An IP interface name can be up to 32
alphanumeric characters long, must start with a letter, and is case-sensitive; for example, the
interface name “1.1.1.1” is not allowed, but “int-1.1.1.1” is allowed.
To create an interface on an Alcatel-Lucent 7210 SAS router, the basic configuration tasks that
must be performed are:
•Assign a name to the interface.
•Associate an IP address with the interface.
•Associate the interface with a system or a loopback interface.
A system interface should be configured.
configure>router context. This is the global router configuration
System Interface
The system interface is associated with the network entity , not a specific interface.
The system interface is used to preserve connectivity (when routing reconvergence is possible)
when an interface fails or is removed. The system interface is used as the router identifier. A
system interface must have an IP address with a 32-bit subnet mask.
Page 247210 SAS D, E, K OS Router Configuration Guide
Basic Configuration
The most basic router configuration must have the following:
•System name
•System address
The following example displays a router configuration:
7210 SAS D, E, K OS Router Configuration GuidePage 25
Common Configuration Tasks
Common Configuration Tasks
The following sections describe basic system tasks.
•Configuring a System Name on page 26
•Configuring Interfaces on page 27
→ Configuring a System Interface on page 27
Configuring a System Name
Use the system command to configure a name for the device. The name is used in the prompt
string. Only one system name can be configured. If multiple system names are configured, the last
one configured will overwrite the previous entry.
If special characters are included in the system name string, such as spaces, #, or ?, the entire string
must be enclosed in double quotes. Use the following CLI syntax to configure the system name:
CLI Syntax: config# system
name system-name
Example
:config# system
config>system# name ALA-A
ALA-A>config>system# exit all
ALA-A#
The following example displays the system name output.
A:ALA-A>config>system# info
#-----------------------------------------# System Configuration
#----------------------------------------- name "ALA-A"
location "Mt.View, CA, NE corner of FERG 1 Building"
coordinates "37.390, -122.05500 degrees lat."
snmp
exit
. . .
exit
----------------------------------------------
Page 267210 SAS D, E, K OS Router Configuration Guide
Configuring Interfaces
The following command sequences create a system IP interface. The system interface assigns an
IP address to the interface in the IES context and create logical IP interfaces for inband
management.
7210 SAS D, E, K OS Router Configuration GuidePage 29
Common Configuration Tasks
Router Advertisement
To configure the router to originate router advertisement messages on an interface, the interface
must be configured under the router-advertisement context and be enabled (no shutdown). All
other router advertisement configuration parameters are optional.
Use the following CLI syntax to enable router advertisement and configure router advertisement
parameters: