cc/td/doc/product/core/cis12000/xr12000/xr12hw/linecard/lc_spa/spa_sw
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Configuring Ethernet SPAs on Cisco IOS XR Software

Configuration Tasks

Required Configuration Steps

Specifying the Interface Address

Configuring a Basic Ethernet Interface

Verifying the Interface Configuration

Configuration Examples

Configuring an Ethernet Interface Example

Configuring MAC Accounting Example


Configuring Ethernet SPAs on Cisco IOS XR Software


This chapter provides information about configuring Ethernet SPAs on the Cisco XR 12000 Series Router running Cisco IOS XR software. It includes the following sections:

Configuration Tasks

Verifying the Interface Configuration

Configuration Examples

For information about managing your system images and configuration files, refer to the Cisco IOS XR Getting Started Guide, Release 3.2 and the Cisco IOS XR Commands Master List, Release 3.2 publications.

For more information about the commands used in this chapter, see Chapter 10, "Command Reference" which documents new and modified commands and the Cisco IOS XR Interface and Hardware Component Command Reference, Release 3.0. For more information about accessing these publications, see the "Related Documentation" section in the "Preface".

Configuration Tasks

This section describes how to configure the Gigabit Ethernet SPAs. It includes the following topics:

Required Configuration Steps

Specifying the Interface Address

Configuring a Basic Ethernet Interface

Required Configuration Steps

This section lists the required configuration steps to configure the Gigabit Ethernet SPAs. Some of the required configuration commands have default values that might be appropriate for your network. If the default value is correct for your network, then you do not need to configure the command. These commands are indicated by "(Optional)" in the purpose column.


Note See the "Configuring a Basic Ethernet Interface" section for detailed information regarding the parameters that can be configured.


SUMMARY STEPS

1. show version

2. show interface

3. configure

4. interface type number

5. ipv4 address ip-address mask
or
ipv6 address ipv6-prefix/prefix-length

6. flow-control {bidirectional | egress | ingress}

7. negotiation auto

8. mac-accounting {egress | ingress}

9. mtu value

10. mac-address value1.value2.value3

11. no shutdown

12. end
or
commit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

show version

Example:

RP/0/0/CPU0:Router> show version

(Optional) Displays the current software version, and can also be used to confirm that the router recognizes the line card.

Step 2 

show interfaces

Example:

RP/0/0/CPU0:Router> show interface

(Optional) Displays the configured interface and checks the status of each interface port.

Step 3 

configure

Example:

RP/0/0/CPU0:Router> configure terminal

Enters global configuration mode.

Step 4 

interface type number

Example:

RP/0/0/CPU0:Router(config)# interface gigabitethernet 0/2/0/1

Enters interface configuration mode, where:

type—Specifies gigabitethernet for the Gigabit Ethernet SPAs.

number—Specifies the Ethernet interface in the notation rack/slot/module/port.

The example indicates Gigabit Ethernet interface 1, on a SPA in subslot 0, in line card slot 2.

Step 5 

ipv4 address ip-address mask

or

ipv6 address ipv6-prefix/prefix-length

Example:

RP/0/0/CPU0:Router(config-if)# ipv4 address 172.18.189.38 255.255.255.224

or

RP/0/0/CPU0:Router(config-if)# ipv6 address 3000:1116::1:3:300:1/112

Assigns an IP address to the interface, where:

ip-address mask—Specifies an IPv4 IP address and subnet mask.

ipv6-prefix/prefix-length—Specifies an IPv6 network address and prefix length.

Step 6 

flow-control {bidirectional | egress | ingress}

Example:

RP/0/0/CPU0:Router(config-if)# flow control ingress

(Optional) Enables the sending of flow control pause frames.

Step 7 

negotiation auto

Example:

RP/0/0/CPU0:Router(config-if)# negotiation auto

(Optional) Enables autonegotiation of the interface with the connected interface.

Step 8 

mac-accounting {egress | ingress}

Example:

RP/0/0/CPU0:Router(config-if)# mac-accounting egress

(Optional) Generates accounting information for IP traffic based on the source and destination MAC addresses on LAN interfaces.

To disable MAC accounting, use the no form of this command.

Step 9 

mtu value

Example:

RP/0/0/CPU0:Router(config-if# mtu 1448

(Optional) Sets the MTU value for the interface.

The default is 1514 for normal frames and 1518 for 802.1Q tagged frames.

Step 10 

mac-address value1.value2.value3

Example:

RP/0/0/CPU0:Router(config-if)# mac address 0001.2468.ABCD

(Optional) Sets the MAC layer address of the management Ethernet interface.

The values are the high, middle, and low 2 bytes, respectively, of the MAC address in hexadecimal. The range of each 2-byte value is 0 to ffff.

Step 11 

no shutdown

Example:

RP/0/0/CPU0:Router(config-if)# no shutdown

Removes the shutdown configuration, which forces an interface administratively down.

The no shutdown command passes an enable command to the SPA, which then returns to an up or a down state depending on the configuration and state of the link.

Step 12 

end

or

commit

Example:

RP/0/0/CPU0:Router(config-if)# end

or

RP/0/0/CPU0:Router(config-if)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found. Commit them before exiting (yes/no/cancel)? [cancel]:

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Specifying the Interface Address

SPAs on Cisco XR 12000 Series Routers running Cisco IOS XR software use an addressing format that specifies the physical location of the SIP, SPA, and interface. The interface address format is rack/slot/subslot/port:

rack—Specifies the rack number, 0 for the Cisco XR 12000 Series Router.

slot—Specifies the slot number in the Cisco XR 12000 Series Router in which the MSC that contains the SPA is installed.

subslotSpecifies the secondary slot on the MSC where the SPA that you want to select is installed.

port—Specifies the interface number that you want to select on the SPA:

For the 1-Port 10-Gigabit Ethernet SPA—0 is the only option.

For the 10-Port Gigabit Ethernet SPA—0 through 9

For the 5-Port Gigabit Ethernet SPA—0 through 4

Figure 4-1 shows the slot, subslot, and interface port locations of the 1-Port 10-Gigabit Ethernet SPA and 10-Port Gigabit Ethernet SPA installed in the SIP located in slot 3.

Figure 4-1 Slot, Subslot, and Port Locations on the Cisco 12000 SIP-600

1

Router slot number 3

3

SPA subslot 1 with ports 0/3/1/0 to 0/3/1/9

2

SPA subslot number 0 with port 0/3/0/0

   

For more information about the installation of cards on the Cisco XR 12000 Series Router, refer to the Cisco 12000 Series Router SIP and SPA Hardware Installation Guide.

Configuring a Basic Ethernet Interface

To configure Gigabit Ethernet interfaces you need to understand the following concepts:

Ethernet Technology Overview

Default Configuration Values

Gigabit Ethernet Protocol Standards Overview

MAC Accounting

Ethernet MTU

Flow Control on Ethernet Interfaces

MAC Address

802.1Q VLAN

VRRP

HSRP

Ethernet Technology Overview

Ethernet was developed in the mid-1970s as a 10-Mbps networking protocol operating over a heavy coax cable.

Today, although many networks have migrated to Fast Ethernet (100 Mbps), Gigabit Ethernet (1000 Mbps), and 10-Gigabit Ethernet (10 Gbps), 10-Mbps Ethernet is still in widespread use and forms the basis of most networks.

Ethernet is defined by the IEEE 802.3 international standard. It enables the connection of up to 1024 nodes over coax, twisted-pair, or fiber-optic cable.

Default Configuration Values

When an interface is enabled on an Ethernet SPA and associated SIP, the following default interface configuration parameters are present. See Table 4-1.


Note You must specifically configure the shutdown command to bring an interface administratively down. The interface default is no shutdown. When a SPA and SIP are first inserted into the router, if there is no established preconfiguration for it, the configuration manager adds a shutdown item to its configuration. This shutdown can be removed only by entering the no shutdown command.


Table 4-1 Ethernet SPA Default Configuration Values 

Parameter
Configuration File Entry
Default Value

MAC Accounting

mac-accounting

off

Flow Control

 

off

MTU

mtu

1514 for normal interfaces, 1518 for 802.1Q VLAN

MAC Address

mac address

Hardware burned in address (BIA)


Gigabit Ethernet Protocol Standards Overview

IEEE 802.3ab 1000BASE-T Gigabit Ethernet

The IEEE 802.3ab protocol standards, or Gigabit Ethernet over copper (also known as 1000BaseT) is an extension of the existing Fast Ethernet standard. It specifies Gigabit Ethernet operation over the Category 5e/6 cabling systems already installed, making it a highly cost-effective solution. As a result, most copper-based environments that run Fast Ethernet can also run Gigabit Ethernet over the existing network infrastructure in order to dramatically boost network performance for demanding applications.

IEEE 802.3z 1000 Mbps Gigabit Ethernet

Gigabit Ethernet builds on top of the Ethernet protocol, but increases speed tenfold over Fast Ethernet to 1000 Mbps, or 1 Gbps. Gigabit Ethernet allows Ethernet to scale from 10 or 100 Mbps at the desktop to 100 Mbps up to 1000 Mbps in the data center. Gigabit Ethernet conforms to the IEEE 802.3z protocol standard.

By leveraging the current Ethernet standard and the installed base of Ethernet and Fast Ethernet switches and routers, network managers do not need to retrain and relearn a new technology in order to provide support for Gigabit Ethernet.

IEEE 802.3ae 10 Gbps Ethernet

Under the International Standards Organization's Open Systems Interconnection (OSI) model, Ethernet is fundamentally a Layer 2 protocol. 10-Gigabit Ethernet uses the IEEE 802.3 Ethernet MAC protocol, the IEEE 802.3 Ethernet frame format, and the minimum and maximum IEEE 802.3 frame size. 10 Gbps Ethernet conforms to the IEEE 802.3ae protocol standards.

Just as 1000BASE-X and 1000BASE-T (Gigabit Ethernet) remained true to the Ethernet model, 10-Gigabit Ethernet continues the natural evolution of Ethernet in speed and distance. Because it is a full-duplex only and fiber-only technology, it does not need the carrier-sensing multiple-access with collision detection (CSMA/CD) protocol that defines slower, half-duplex Ethernet technologies. In every other respect, 10-Gigabit Ethernet remains true to the original Ethernet model.

MAC Accounting

The MAC address accounting feature provides accounting information for IP traffic based on the source and destination MAC addresses on LAN interfaces. This feature calculates the total packet and byte counts for a LAN interface that receives or sends IP packets to or from a unique MAC address. It also records a time stamp for the last packet received or sent.

Ethernet MTU

A maximum transmission unit (MTU) is the largest size packet or frame, specified in octets (eight-bit bytes), that can be sent in a packet- or frame-based network such as the Internet. The Internet's TCP uses the MTU to determine the maximum size of each packet in any transmission. Too large an MTU size may mean retransmissions if the packet encounters a router that can't handle the large packet. Too small an MTU size means relatively more header overhead and more acknowledgements that have to be sent and handled. Most computer operating systems provide a default MTU value that is suitable for most users. The default value is 1514 for standard frames and 1518 for 802.1Q tagged frames. These numbers exclude the 4 byte frame check sequence (FCS).

Flow Control on Ethernet Interfaces

The flow control used on Gigabit Ethernet interfaces consists of periodically sending flow control pause frames. It is fundamentally different from the usual full- and half-duplex flow control used on standard management interfaces. Flow control can be activated for either ingress traffic, egress traffic or bi-directional traffic. Flow control by default is not activated on SPA Gigabit Ethernet interfaces.

Some hardware has restrictions on how flow-control can be configured. If you attempt to configure a method of flow-control that is not supported, an error is returned at configuration verification. The current operational flow control settings can be displayed using the show interfaces command.

MAC Address

A MAC address is a 6-byte-long hardware address that uniquely identifies each node of a network.

802.1Q VLAN

A VLAN is a group of devices on one or more LANs that are configured so that they can communicate as if they were attached to the same wire, when in fact they are located on a number of different LAN segments. Because VLANs are based on logical instead of physical connections, it is very flexible for user and host management, bandwidth allocation, and resource optimization.

The IEEE's 802.1Q protocol standard addresses the problem of breaking large networks into smaller parts so broadcast and multicast traffic does not consume more bandwidth than necessary. The standard also helps provide a higher level of security between segments of internal networks.

The 802.1Q specification establishes a standard method for inserting VLAN membership information into Ethernet frames.

VRRP

The Virtual Router Redundancy Protocol (VRRP) eliminates the single point of failure inherent in the static default routed environment. VRRP specifies an election protocol that dynamically assigns responsibility for a virtual router to one of the VPN concentrators on a LAN. The VRRP VPN concentrator controlling the IP addresses associated with a virtual router is called the Master, and forwards packets sent to those IP addresses. When the master becomes unavailable, a backup VPN concentrator takes the place of the master.

For more information on VRRP, refer to the "Implementing VRRP on Cisco IOS XR Software" module of the Cisco IOS XR IP Addresses and Services Configuration Guide.

HSRP

Hot Standby Routing Protocol (HSRP) is a proprietary protocol from Cisco. HSRP is a routing protocol that provides backup to a router in the event of failure. Several routers are connected to the same segment of an Ethernet, FDDI, or token-ring network and work together to present the appearance of a single virtual router on the LAN. The routers share the same IP and MAC addresses and therefore, in the event of failure of one router, the hosts on the LAN are able to continue forwarding packets to a consistent IP and MAC address. The transfer of routing responsibilities from one device to another is transparent to the user.

HSRP is designed to support non disruptive failover of IP traffic in certain circumstances and to allow hosts to appear to use a single router and to maintain connectivity even if the actual first hop router they are using fails. In other words, HSRP protects against the failure of the first hop router when the source host cannot learn the IP address of the first hop router dynamically. Multiple routers participate in HSRP and in concert create the illusion of a single virtual router. HSRP ensures that one and only one of the routers is forwarding packets on behalf of the virtual router. End hosts forward their packets to the virtual router.

The router forwarding packets is known as the active router. A standby router is selected to replace the active router should it fail. HSRP provides a mechanism for determining active and standby routers, using the IP addresses on the participating routers. If an active router fails a standby router can take over without a major interruption in the host's connectivity.

HSRP runs on top of User Datagram Protocol (UDP), and uses port number 1985. Routers use their actual IP address as the source address for protocol packets, not the virtual IP address, so that the HSRP routers can identify each other.

For more information on HSRP, refer to the "Implementing HSRP on Cisco IOS XR Software" module of the Cisco IOS XR IP Addresses and Services Configuration Guide.

Verifying the Interface Configuration

Use the following task to display your router configuration settings.

SUMMARY STEPS

1. show interfaces type number

2. show mac-accounting type number [location node-id]

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

show interfaces type number

Example:

RP/0/0/CPU0:Router# show interfaces gigabitethernet 0/2/0/0

(Optional) Displays statistics for an interface, where:

type—Specifies gigabitethernet for the Gigabit Ethernet SPAs.

number—Specifies the Ethernet interface in the notation rack/slot/module/port.

Step 2 

show mac-accounting type number [location node-id]

Example:

RP/0/0/CPU0:Router# show mac-accounting gigabitethernet 0/2/0/0

Displays MAC accounting statistics for an interface, where:

type—Specifies gigabitethernet for the Gigabit Ethernet SPA.

number—Specifies the Ethernet interface in the notation rack/slot/module/port.

Configuration Examples

This section contains the following examples:

Configuring an Ethernet Interface Example

Configuring MAC Accounting Example

Configuring an Ethernet Interface Example

The following example indicates how to configure an interface for the Gigabit Ethernet SPA:

RP/0/0/CPU0:Router# configure
RP/0/0/CPU0:Router(config)# interface gigabitethernet 0/2/0/0
RP/0/0/CPU0:Router(config-if)# ipv4 address 172.18.189.38 255.255.255.224
RP/0/0/CPU0:router(config-if)# flow-control ingress
RP/0/0/CPU0:Router(config-if)# mtu 1448
RP/0/0/CPU0:Router(config-if)# mac-address 0000.0c00.e8bb
RP/0/0/CPU0:Router(config-if)# no shutdown
RP/0/0/CPU0:Router(config-if)# end
Uncommitted changes found, commit them before exiting(yes/no/cancel)? [cancel]:yes
LC/0/2/CPU0:Feb 13 03:47:44.622 : ifmgr[137]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/2/0/0, changed state to Up
RP/0/0/CPU0:Feb 13 03:47:45.010 : config[65730]: %MGBL-LIBTARCFG-6-COMMIT : Configuration committed by user 'xxx'. Use 'show commit changes 1000012264' to view the changes.
RP/0/0/CPU0:Feb 13 03:47:45.091 : config[65730]: %MGBL-SYS-5-CONFIG_I : Configured from console by xxx
RP/0/0/CPU0:Router# show interfaces gigabitethernet 0/2/0/0

GigabitEthernet0/2/0/0 is up, line protocol is up

Hardware is GigabitEthernet, address is 0000.0c00.e8bb (bia 0000.0c00.e8bb)
Internet address is 172.18.189.38/27
MTU 1448 bytes, BW 1000000 Kbit
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA,
Full-duplex, 1000Mb/s, SX, link type is force-up
output flow control is off, input flow control is on
loopback not set
Last clearing of "show interface" counters never
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 total input drops
0 drops for unrecognized upper-level protocol
Received 0 broadcast packets, 0 multicast packets
0 runts, 0 giants, 0 throttles, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
1 packets output, 46 bytes, 0 total output drops
Output 0 broadcast packets, 0 multicast packets
0 output errors, 0 underruns, 0 applique, 0 resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions

Configuring MAC Accounting Example

The following example indicates how to configure MAC-accounting on an Ethernet interface:

RP/0/0/CPU0:Router# config
RP/0/0/CPU0:Router(config)# gigabitethernet 0/0/0/2
RP/0/0/CPU0:Router(config-if)# ipv4 address 172.18.189.38 255.255.255.224
RP/0/0/CPU0:Router(config-if)# mac-accounting egress
RP/0/0/CPU0:Router(config-if)# commit
RP/0/0/CPU0Sep 19 20:21:11.330 : config[65726]: %LIBTARCFG-6-COMMIT : Configuration committed by user 'unknown'. Use 'show commit changes 1000003461' to view the changes.
RP/0/0/CPU0:Router(config-if)# exit
RP/0/0/CPU0:Router(config)# exit


hometocprevnextglossaryfeedbacksearchhelp

Posted: Mon Jan 9 21:05:28 PST 2006
All contents are Copyright © 1992--2006 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.