Cisco uBR10012 Universal Broadband Router SIP and SPA Software Configuration Guide - Configuring Gigabit Ethernet SPAs [Cisco uBR10000 Series Universal Broadband Routers]

Table Of Contents

Configuring Gigabit Ethernet SPAs

Configuration Tasks

Default Configuration Values

Specifying the Interface Address on a SPA

Configuring Gigabit Ethernet SPAs

Modifying the MAC Address on the Interface

Verifying the MAC Address

Gathering MAC Address Accounting Statistics

Configuring Autonegotiation on an Interface

Disabling Autonegotiation

Enabling Autonegotiation

Ethernet Flow Control

Disabling Flow Control

Enabling Flow Control

Modifying the Interface MTU Size

Interface MTU Configuration Guidelines

Interface MTU Configuration Task

Verifying MTU Size

Configuring the Encapsulation Type and VLANs

Configuring the Hold Queue

Configuring EtherChannels

Configuring a Priority Queue on Gigabit Ethernet SPAs

Preprovisioning the SIPs and Gigabit Ethernet SPAs

Removing Preprovisioning on a SIP and SPA

Verifying the Configuration

Verifying Per-Port Interface Status

Configuration Examples

Basic Interface Configuration Example

MAC Address Configuration Example

MAC Address Accounting Configuration Example

MTU Configuration Example

VLAN Configuration Example

Priority Queue Classification Configuration Example

Configuring any Keyword on Subinterfaces for PPPoE-QinQ Support

Configuring Gigabit Ethernet SPAs

This chapter provides information about configuring Gigabit Ethernet SPAs on the Cisco uBR10012 router. It includes the following sections:

•Configuration Tasks

•Verifying the Configuration

•Configuration Examples

Configuration Tasks

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

•Default Configuration Values

•Specifying the Interface Address on a SPA

•Configuring Gigabit Ethernet SPAs

•Modifying the MAC Address on the Interface

•Gathering MAC Address Accounting Statistics

•Configuring Autonegotiation on an Interface

•Ethernet Flow Control

•Modifying the Interface MTU Size

•Configuring the Encapsulation Type and VLANs

•Configuring the Hold Queue

•Configuring EtherChannels

•Configuring EtherChannels

•Configuring a Priority Queue on Gigabit Ethernet SPAs

•Preprovisioning the SIPs and Gigabit Ethernet SPAs

Default Configuration Values

Table 12-1 lists the default configuration parameters when an interface is enabled on a Gigabit Ethernet SPA.

Table 12-1 Gigabit Ethernet SPA Default Configuration Values

Parameter

Default Value

Autonegotiation

Enabled (supported only on Cisco 5-Port Gigabit Ethernet SPA)

Flow control

Enabled

Hold queue

Disabled

IEEE 802.1Q encapsulation

Disabled

MAC accounting

Disabled

MAC address

Hardware burned in address (BIA)

MTU

1514 for normal interfaces, 1518 for 802.1Q VLAN

Specifying the Interface Address on a SPA

Gigabit Ethernet SPAs on the Cisco uBR10012 router use an addressing format that specifies the physical location of the SIP, SPA, and interface. The interface address format is slot/subslot/port, where:

•slot—Specifies the slot number in the Cisco uBR10012 router where the SIP is installed.

•subslot—Specifies the secondary slot of the SIP where the SPA is installed.

•port—Specifies the number of the individual interface port on a SPA.

The following example shows how to specify the second interface (1) on a Gigabit Ethernet SPA installed in the first subslot of a SIP (0) installed in chassis slot 3:
Router(config)# interface gigabitethernet 3/0/1
Note The interface address format for the Cisco Wideband SPA is changed in Cisco IOS Release 12.2(33)SCB. For details, see "SIP and SPA Addressing Format" section on page 4-2.

Configuring Gigabit Ethernet SPAs

To configure a Gigabit Ethernet SPA, follow this procedure:
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode. If prompted, enter your password.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.
Step 3
Router(config)# interface gigabitethernet slot/subslot/port [.subinterface-number]
or

Router(config)# interface tengigabitethernet slot/subslot/port [.subinterface-number]
Example:

Router(config)# interface gigabitethernet 5/0/0
Specifies the Gigabit Ethernet or the 10-Gigabit Ethernet interface to enter interface configuration mode.

•slot/subslot/port—Specifies the location of the interface.

•subinterface-number—(Optional) Specifies a secondary interface (subinterface) number.
Step 4
Router(config-if)# ip address ip-address mask
or

Router(config-if)#ipv6 address ipv6-prefix/prefix-length
Example:

Router(config-if)# ip address 172.18.189.38 255.255.255.224
or

Router(config-if)# ipv6 address 3000:1116::1:3:300:1/112
Assigns an IP address to the interface.

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

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

Router(config-if)# no shutdown
Example:

Router(config-if)# no shutdown

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

Step 6

Router(config-if)# end
Example:

Router(config-if)# end

Saves configuration changes.
Modifying the MAC Address on the Interface

The Gigabit Ethernet SPAs use a default MAC address for each port that is derived from the base address that is stored in the electrically erasable programmable read-only memory (EEPROM) on the backplane of the Cisco uBR10012 router.

To modify the default MAC address of an interface to some user-defined address, use the following command in interface configuration mode:

Command

Purpose

Router(config-if)# mac-address ieee-address

Modifies the default MAC address of an interface to a user-defined address.

•ieee-address—Specifies the 48-bit Institute of Electrical and Electronics Engineers (IEEE) MAC address written as a dotted triple of four-digit hexadecimal numbers (xxxx.yyyy.zzzz).

To return to the default MAC address on the interface, use the no form of the command.

Verifying the MAC Address

To verify the MAC address of an interface, use the show interfaces gigabitethernet privileged EXEC command and observe the value shown in the address field.

The following example shows output from the show interfaces tengigabitethernet command on a 1-Port 10-Gigabit Ethernet SPA in slot 1, SPA subslot 3. The second line of the output identifies the type of SPA and its MAC address.
Router# show interfaces tengigabitethernet 1/3/0
GigabitEthernet1/3/0 is up, line protocol is up 
  Hardware is TenGigEther SPA, address is 0005.00e7.2548 (bia 0005.00e7.2548)
  MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive not set
  Full Duplex, 1000Mbps, link type is auto, media type is SX
  output flow-control is unsupported, input flow-control is XON
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output 00:00:00, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Interface GigabitEthernet1/3/0 queueing strategy: PXF Class-based
  5 minute input rate 19000 bits/sec, 23 packets/sec
  5 minute output rate 17000 bits/sec, 23 packets/sec
     61860 packets input, 9470324 bytes, 0 no buffer
     Received 3151 broadcasts (0 IP multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 3151 multicast, 0 pause input
     62413 packets output, 5726961 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 pause output
     0 output buffer failures, 0 output buffers swapped out
Gathering MAC Address Accounting Statistics

MAC address accounting provides accounting information for IP traffic based on the source and destination MAC addresses of the LAN interfaces. MAC address accounting 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. With MAC address accounting, you can determine how much traffic is being sent to or received from various peers.

To enable MAC address accounting on an interface, use the following command in interface configuration mode:

Command

Purpose

Router(config-if)# ip accounting mac-address [input | output]

Enables MAC address accounting on an interface.

•input—Performs accounting based on the source MAC address on received packets.

•output—Performs accounting based on the destination MAC address on transmitted packets.

Configuring Autonegotiation on an Interface

Autonegotiation is enabled by default and can be disabled on the 5-Port Gigabit Ethernet SPA. During autonegotiation, advertisement for flow control, speed, and duplex occurs. If autonegotiation is disabled on one end of a link, it must be disabled on the other end of the link. If one end of a link has autonegotiation disabled while the other end of the link does not, the link does not come up properly on both ends. Flow control is always negotiated when autonegotiation is enabled.

Note Autonegotiation is not supported on the 1-Port 10-Gigabit Ethernet SPA.

Disabling Autonegotiation

To disable autonegotiation on the 5-Port Gigabit Ethernet SPA, use the following command in interface configuration mode:

Command

Purpose

Router(config-if)# no negotiation auto

Disables autonegotiation on the 5-Port Gigabit Ethernet SPA interface on the SIP-600. No advertisement of flow control occurs.

Enabling Autonegotiation

To re-enable autonegotiation on a Gigabit Ethernet interface, use the following command in interface configuration mode:

Command

Purpose

Router(config-if)# negotiation auto

Enables autonegotiation on the 5-Port Gigabit Ethernet SPA interface on the SIP-600. Advertisement of flow control occurs.

Ethernet Flow Control

The Ethernet flow control feature is a mechanism for temporarily stopping the transmission of data between two peers to prevent packet drops in the event of data overflow. The overwhelmed network element will send a PAUSE frame, which halts transmission from the sending node for a specified period of time. Flow control is enabled by default on the 1-Port 10-Gigabit Ethernet SPA.

Note Flow control is always negotiated when autonegotiation is enabled.

Disabling Flow Control

To disable flow control on the 1-Port 10-Gigabit Ethernet SPA, use the following command in interface configuration mode:

Command

Purpose

Router(config-if)# flowcontrol receive off

Disables flow control on the 1-Port 10-Gigabit Ethernet SPA. When the flow control is disabled, the PAUSE frames received from its peer are ignored and transmission continues.

Enabling Flow Control

To re-enable flow control on a Gigabit Ethernet interface, use the following command in interface configuration mode:

Command

Purpose

Router(config-if)# no flowcontrol receive off

Enables flow control on a Gigabit Ethernet SPA interface.

Modifying the Interface MTU Size

The Cisco IOS software supports three different types of configurable maximum transmission unit (MTU) options at different levels of the protocol stack:

•Interface MTU—Checked by the SPA on traffic coming in from the network. Different interface types support different interface MTU sizes and defaults. The interface MTU defines the maximum packet size allowable (in bytes) for an interface before drops occur. If the frame is smaller than the interface MTU size, but is not smaller than the minimum frame size for the interface type (such as 64 bytes for Ethernet), then the frame continues to process.

•IP MTU—Can be configured on an interface or a subinterface and is used by the Cisco IOS software to determine whether fragmentation of a packet takes place. If an IP packet exceeds the IP MTU size, then the packet is fragmented.

•Tag or Multiprotocol Label Switching (MPLS) MTU—Can be configured on an interface or a subinterface and allows up to six different labels, or tag headers, to be attached to a packet. The maximum number of labels is dependent on your Cisco IOS software release.

Note For the Gigabit Ethernet SPAs on the Cisco uBR10012 router, the default MTU size is 1500 bytes. When the interface is being used as a Layer 2 port, the maximum configurable MTU is 9000 bytes. The SPA automatically adds an additional 22 bytes to the configured MTU size to accommodate some of the additional overhead.

Interface MTU Configuration Guidelines

When configuring the interface MTU size on a Gigabit Ethernet SPA on a Cisco uBR10012 router, consider the following guidelines:

•The default interface MTU size accommodates a 1500-byte packet, plus 22 additional bytes to cover the following additional overhead:

–Layer 2 header—14 bytes

–Dot1Q header—4 bytes

–CRC—4 bytes

Note Depending on your Cisco IOS software release, a certain maximum number of MPLS labels are supported. If you need to support more than two MPLS labels, then you must increase the default interface MTU size.

•If you are using MPLS, be sure that the mpls mtu command is configured for a value less than or equal to the interface MTU.

•If you are using MPLS labels, then you should increase the default interface MTU size to accommodate the number of MPLS labels. Each MPLS label adds 4 bytes of overhead to a packet.

Interface MTU Configuration Task

To modify the MTU size on an interface, use the following command in interface configuration mode:

Command

Purpose

Router(config-if)# mtu bytes

Configures the maximum packet size for an interface. The default is 1500 bytes. The maximum configurable MTU is 9129 bytes.

•bytes—Specifies the maximum number of bytes for a packet.

To return to the default MTU size, use the no form of the command.

Verifying MTU Size

To verify the MTU size for an interface, use the show interfaces command in privileged EXEC command and observe the value shown in the MTU field.

The following example shows an MTU size of 1500 bytes for the Gigabit Ethernet SPA installed in the SIP that is located in slot 1 of the Cisco uBR10012 router:
Router# show interfaces GigabitEthernet 1/3/0
GigabitEthernet1/3/0 is up, line protocol is up 
  Hardware is GigEther SPA, address is 0005.00e7.2548 (bia 0005.00e7.2548)
  MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive not set
Configuring the Encapsulation Type and VLANs

By default, the interfaces on the Gigabit Ethernet SPAs support Advanced Research Projects Agency (ARPA) encapsulation. They do not support configuration of service access point or SNAP encapsulation for transmission of frames; however, the interfaces will properly receive frames that use service access point and SNAP encapsulation.

The Cisco uBR10012 router supports virtual local area networks (VLANs) to separate a service provider's subscriber traffic. Each Gigabit Ethernet SPA supports up to 8000 VLANs

The other encapsulation supported by the SPA interfaces is IEEE 802.1Q encapsulation for virtual LANs (VLANs). To create a subinterface on a SPA interface port and configure the subinterface on a VLAN using IEEE 802.1Q encapsulation, use the following command in subinterface configuration mode:

Command

Purpose

Router(config-subif)# encapsulation dot1q vlan-id

Enables IEEE 802.1Q encapsulation on a subinterface on a VLAN

•vlan-id— Specifies the VLAN identifier. The valid range is from 1 to 4095.

Configuring the Hold Queue

You can limit the size of the input queue on a Gigabit Ethernet SPA in units of packets. The input hold queue prevents a single interface from flooding the network server with too many input packets. Further input packets are discarded if the interface has too many input packets outstanding in the system. The default input hold queue limit is 75 packets.

To modify the input hold queue on a Gigabit Ethernet SPA, use the following command in interface configuration mode:

Command

Purpose

Router(config-if)# hold-queue length in

Configures the input hold queue in units of packets.

•length— Specifies the maximum number of packets in the queue. The valid values are from 0 to 4096.

Configuring EtherChannels

An EtherChannel bundles individual Gigabit Ethernet links into a single logical link that provides the aggregate bandwidth of up to four physical links. This feature helps improve the cost effectiveness of a device by increasing cumulative bandwidth without requiring hardware upgrades. In addition, IEEE 802.3ad link bundling provides a capability to dynamically provision, manage, and monitor various aggregated links and enables interoperability between various Cisco devices and the devices of third-party vendors.

Configuring a Priority Queue on Gigabit Ethernet SPAs

The Gigabit Ethernet SPAs provide the ability to separate high-priority traffic from low-priority traffic and places the traffic in the appropriate interface queue. Priority and nonpriority traffic are separated at the SIP to prevent the dropping of high-priority traffic in an oversubscription case.

Note Each SPA supports one priority queue.

The following classification types are available to prioritize ingress traffic on the Gigabit Ethernet SPAs:

•VLAN 802.1Q priority bits

•IP DSCP bits

•IP precedence bits

•IPv6 traffic-class bits

•MPLS EXP bits

Classifying Ingress VLAN Traffic

To classify ingress VLAN traffic based on the 802.1Q priority bits, use the following commands in interface and subinterface configuration mode:

Command

Purpose

Router(config-if)# plim qos input map cos enable

Enables classification of ingress VLAN traffic according to the 802.1Q priority bits.

Note This command can only be applied to VLAN interfaces.

Router(config-subif)# plim qos input map cos cos-value queue low-latency

(Optional) Classifies incoming VLAN traffic on a subinterface according to the 802.1Q priority bits and places the traffic into the appropriate queue.

•cos-value—Specifies an IEEE 802.1Q/ISL CoS value from 0 to 7.

Note When you configure a class of service (CoS) value on a QinQ subinterface, the CoS value applies to all QinQ subinterfaces with the same outer VLAN ID.

•low-latency—Specifies the high-priority queue.

Classifying Ingress IP Traffic According to DSCP Bits

To classify ingress IP traffic based on the value of the DSCP bits, use the following commands in interface configuration mode:

Command

Purpose

Router(config-if)# plim qos input map ip dscp-based

Enables the classification of incoming IP traffic according to the value of the DSCP bits.

Note This command only applies to physical interfaces.

Router(config-if)# plim qos input map ip dscp dscp-value queue low-latency

Classifies incoming IP traffic according to the value of the DSCP bits and places the traffic into the appropriate queue. By default, IP traffic with the DSCP bits will use the low-latency queue, and traffic with any other DSCP value will use the low-priority queue.

•dscp-value—Value of the DSCP bits. Values can be one of the following:

0 to 63—Differentiated services code point value

af11—001010

af12—001100

af13—001110

af21—010010

af22—010100

af23—010110

af31—011010

af32—011100

af33—011110

af41—100010

af42—100100

af43—100110

cs1—Precedence 1 (001000)

cs2—Precedence 2 (010000)

cs3—Precedence 3 (011000)

cs4—Precedence 4 (100000)

cs5—Precedence 5 (101000)

cs6—Precedence 6 (110000)

cs7—Precedence 7 (111000)

default—000000

ef—101110

A range of values can be specified separated by a dash (-), or a list of values can be specified.

•low-latency—Specifies the high-priority queue.

Classifying Ingress IP Traffic According to IP Precedence Bits

To classify ingress IP traffic based on the value of the IP precedence bits, use the following commands in interface configuration mode:

Command

Purpose

Router(config-if)# plim qos input map ip precedence-based

Enables the classification of incoming IP traffic according to the IP precedence value.

Note This command only applies to physical interfaces.

Router(config-if)# plim qos input map ip precedence precedence-value queue low-latency

Classifies incoming IP traffic according to the value of the IP precedence bits and places the traffic into the appropriate queue.

•precedence-value—Value of the IP precedence bits (0 to 7). A range of values can be specified separated by a dash (-), or a list of values can be specified.

•queue low-latency—Specifies the high-priority queue.

Classifying Ingress IPv6 Traffic According to Traffic-Class Bits

To classify ingress IPv6 traffic based on the value of the traffic-class bits, use the following command in interface configuration mode:

Command

Purpose

Router(config-if)# plim qos input map ipv6 tc tc-value queue low-latency

Classifies ingress IPv6 traffic based on the value of the traffic-class bits and places the traffic into the appropriate queue. By default, IPv6 traffic with a traffic-class value uses the high-priority queue, and all other traffic will use the low-priority queue. Only the most significant six bits of the traffic-class octet is used for the classification.

Note This command only applies to physical interfaces.

•tc-value—Value of the traffic-class bits. Values can be one of the following:

0 to 63—Differentiated services code point value

af11—001010

af12—001100

af13—001110

af21—010010

af22—010100

af23—010110

af31—011010

af32—011100

af33—011110

af41—100010

af42—100100

af43—100110

cs1—Precedence 1 (001000)

cs2—Precedence 2 (010000)

cs3—Precedence 3 (011000)

cs4—Precedence 4 (100000)

cs5—Precedence 5 (101000)

cs6—Precedence 6 (110000)

cs7—Precedence 7 (111000)

default—000000

ef—101110

A range of values can be specified separated by a dash (-), or a list of values can be specified.

•queue low-latency—Specifies the high-priority queue.

Classifying Ingress MPLS Traffic According to EXP Bits

To classify ingress MPLS traffic based on the value of the EXP bits, use the following commands in interface configuration mode:

Command

Purpose

Router(config-if)# plim qos input map mpls exp exp-value queue low-latency

Classifies incoming MPLS traffic according to the value of the EXP bits and places the traffic into the appropriate queue.

Note This command only applies to physical interfaces.

•exp-value—Value of the EXP bits (0 to 7). A range of values can be specified separated by a dash (-), or a list of values can be specified.

•queue low-latency—Specifies the high-priority queue.

Preprovisioning the SIPs and Gigabit Ethernet SPAs

Preprovisioning is an optional configuration task for the SIP-600 and the Gigabit Ethernet SPAs. It allows you to preprovision a line card slot in the Cisco uBR10012 router to accept a particular SIP, and to preconfigure the SPA interfaces without the SIP being physically present in the chassis. This feature allows planning for future configurations.

For preprovisioning a SPA, the subslot must be physically empty or gracefully deactivated. For information on gracefully deactivating a SPA, refer to the "Preparing for Online Insertion and Removal of SIPs and SPAs" section on page 5-2.

Tip To display the slots, if any, that are preprovisioned for a card type, use the show running-config | include card command.

To preprovision a SIP, use the following command in global configuration mode:
Command

Purpose
Router(config)# card slot card type
Example:
Router(config)#card 1 4jacket-1
Specifies preprovisioning of a Cisco SIP-600 in a particular line card slot.

•slot—Specifies the slot number for the SIP.

•card type—Specifies the type of card for which to preprovision the slot. 4jacket-1 is the card type for the Cisco SIP-600.
To preprovision a Gigabit Ethernet SPA, use the following command in global configuration mode:
Command

Purpose
Router(config)#card slot/bay card type

Example:
Router(config)#card 1/3 SPA-1XTENGE-XFP-V2
•slot—Identifies the chassis slot for a SIP. Valid values are 1 to 3.

•bay—Identifies the bay number in the SIP where a SPA is located. Valid values are 0 (upper bay) or 1 (lower bay).

•card type—Specifies the type of card for which to preprovision the slot. Following are the card types for the Gigabit Ethernet SPAs:

–SPA-1XTENGE-XFP-V2 for the 1-Port 10-Gigabit Ethernet SPA

–SPA-5X1GE-V2 for the 5-Port Gigabit Ethernet SPA
Removing Preprovisioning on a SIP and SPA

To remove a preprovisioning configuration from a line card slot, use the no card command. This removes all configuration information for that subslot, as well as any information in the SNMP MIB database about the card and its card slot.

To remove preprovisioning configuration information, the SIP slot or SPA subslot must be physically empty or gracefully deactivated. For information on deactivating SIPs and SPAs, refer to the "Preparing for Online Insertion and Removal of SIPs and SPAs" section on page 5-2.

Verifying the Configuration

Besides using the show running-configuration command to display your router configuration settings, you can use the show interfaces gigabitethernet command to get detailed information on a per-port basis for your Gigabit Ethernet SPAs.

Verifying Per-Port Interface Status

To find detailed interface information on a per-port basis for the Gigabit Ethernet SPAs, use the show interfaces gigabitethernet command.

The following example provides sample output on a 1-Port 10-Gigabit Ethernet SPA in slot 1, subslot 3, port 0:
Router# show interfaces tenGigabitEthernet 1/3/0
GigabitEthernet1/3/0 is up, line protocol is up 
  Hardware is GigEther SPA, address is 0005.00e7.2548 (bia 0005.00e7.2548)
  MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive not set
  Full Duplex, 1000Mbps, link type is auto, media type is SX
  output flow-control is unsupported, input flow-control is XON
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output 00:00:00, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Interface GigabitEthernet1/3/0 queueing strategy: PXF Class-based
  5 minute input rate 19000 bits/sec, 23 packets/sec
  5 minute output rate 17000 bits/sec, 23 packets/sec
     61860 packets input, 9470324 bytes, 0 no buffer
     Received 3151 broadcasts (0 IP multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 3151 multicast, 0 pause input
     62413 packets output, 5726961 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 pause output
     0 output buffer failures, 0 output buffers swapped out
Configuration Examples

This section includes the following configuration examples:

•Basic Interface Configuration Example

•MAC Address Configuration Example

•MAC Address Accounting Configuration Example

•MTU Configuration Example

•VLAN Configuration Example

•Priority Queue Classification Configuration Example

•Configuring any Keyword on Subinterfaces for PPPoE-QinQ Support

Basic Interface Configuration Example

The following example shows how to specify the interface that you want to configure, configure an IP address for the interface, and save the configuration. This example configures interface port 0 on the SPA that is located in subslot 3 of the SIP, which is installed in slot 1 of the Cisco uBR10012 router.

! Enter global configuration mode.
!
Router# configure terminal
! Enter configuration commands, one per line. End with CNTL/Z.
!
! Specify the interface address.
!
Router(config)# interface gigabitethernet 1/3/0
!
! Configure an IP address.
!
Router(config-if)# ip address 192.168.50.1 255.255.255.0
!
! Start the interface.
!
Router(config-if)# no shut
!
! Save the configuration to NVRAM.
!
Router(config-if)# exit
Router# copy running-config startup-config

MAC Address Configuration Example

The following example changes the default MAC address on the interface to 1111.2222.3333:

! Enter global configuration mode.
!
Router# configure terminal
! Enter configuration commands, one per line. End with CNTL/Z.
!
! Specify the interface address
!
Router(config)# interface gigabitethernet 1/3/0
!
! Modify the MAC address.
!
Router(config-if)# mac-address 1111.2222.3333

MAC Address Accounting Configuration Example

The following example enables MAC Address Accounting:

! Enter global configuration mode.
!
Router# configure terminal
! Enter configuration commands, one per line. End with CNTL/Z.
!
! Enable MAC address accounting
Router(config)# ip accounting mac-address {input | output}
Router(config-if)# ip accounting ?
access-violations Account for IP packets violating access lists on this interface
mac-address Account for MAC addresses seen on this interface
output-packets Account for IP packets output on this interface
precedence Count packets by IP precedence on this interface
Router(config-if)# ip accounting mac
Router(config-if)# ip accounting mac-address ?
input Source MAC address on received packets
output Destination MAC address on transmitted packets
Router(config-if)# ip accounting mac-address ip
Router(config-if)# ip accounting mac-address input ?
! Specify MAC address accounting for traffic entering the interface.
!
Router(config-if)# ip accounting mac-address input
! Specify MAC address accounting for traffic leaving the interface.
!
Router(config-if)# ip accounting mac-address output
Router(config-if)# end
! Verify the MAC Address on the interface.
!
Router# show interfaces GigabitEthernet 1/3/0 mac-accounting
GigabitEthernet1/3/0
Input (511 free)
000f.f7b0.5200(26 ): 124174 packets, 7450440 bytes, last: 1884ms ago
Total: 124174 packets, 7450440 bytes
Output (511 free)
000f.f7b0.5200(26 ): 135157 packets, 8109420 bytes, last: 1884ms ago
Total: 135157 packets, 8109420 bytes

MTU Configuration Example

The following example sets the interface MTU to 9180 bytes:

! Enter global configuration mode.
!
Router# configure terminal
! Enter configuration commands, one per line. End with CNTL/Z.
!
! Specify the interface address
!
Router(config)# interface gigabitethernet 1/3/0
!
! Configure the interface MTU.
!
Router(config-if)# mtu 9180

VLAN Configuration Example

The following example creates subinterface number 268 on the SPA interface port, and configures the subinterface on the VLAN with ID number 268 using IEEE 802.1Q encapsulation:

! Enter global configuration mode.
!
Router# configure terminal
! Enter configuration commands, one per line. End with CNTL/Z.
!
! Specify the interface address
!
Router(config)# interface gigabitethernet 1/3/0.268
!
! Configure dot1q encapsulation and specify the VLAN ID.
!
Router(config-subif)# encapsulation dot1q 268

Priority Queue Classification Configuration Example

The following example enables DSCP-based classification on the SPA that is located in subslot 3 of the SIP in slot 1of the Cisco uBR10012 router:

! Enter global configuration mode.
!
Router# configure terminal
! Enter configuration commands, one per line. End with CNTL/Z.
!
! Specify the interface address
!
Router(config)# interface gigabitethernet 1/3/0
!
! Configure the priority queue classification type.
Router(config-if)# plim qos input map ip dscp-based
Configuring any Keyword on Subinterfaces for PPPoE-QinQ Support

The following example configures seven subinterfaces with various outer and inner VLAN IDs:

! Enter global configuration mode.
!
Router# configure terminal
! Enter configuration commands, one per line. End with CNTL/Z.
Router# interface GigabitEthernet3/0/0.1
Router(config-if)#  encapsulation dot1q 100 second-dot1q 100
Router(config-if)# exit 
Router# interface GigabitEthernet3/0/0.2
Router(config-if)# encapsulation dot1q 100 second-dot1q 200
Router(config-if)# exit 
Router# interface GigabitEthernet3/0/0.3
Router(config-if)# encapsulation dot1q 100 second-dot1q 300-400,500-600
Router(config-if)# exit 
Router# interface GigabitEthernet3/0/0.4
Router(config-if)# encapsulation dot1q 100 second-dot1q any
Router(config-if)# exit 
Router# interface GigabitEthernet3/0/0.5
Router(config-if)# encapsulation dot1q 200 second-dot1q 50
Router(config-if)# exit 
Router# interface GigabitEthernet3/0/0.6
Router(config-if)# encapsulation dot1q 200 second-dot1q 1000-2000,3000-4000
Router(config-if)# exit 
Router# interface GigabitEthernet3/0/0.7
Router(config-if)# encapsulation dot1q 200 second-dot1q any