Configuring the Cisco 1GE-CU-SFP and 2GE-CU-SFP Network Interface Modules in Cisco 4000 Series Integrated Services Routers

Required Configuration Tasks

This section lists the required configuration steps to configure the Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs. Some of the required configuration commands implement 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 “(As Required)” in the Purpose column.

To configure the Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs, complete the following steps:

Specifying the Interface Address on a NIM

NIM interface ports begin numbering with “0” from left to right. Single-port NIMs use only the port number 0. To configure or monitor NIM interfaces, you need to specify the physical location of the NIM, and interface in the CLI. The interface address format is slot/subslot/port, where:

• slot—Specifies the chassis slot number in the Cisco 4000 Series ISR Routers where the SM-X-NIM-ADPTR is installed.
• subslot—Specifies the slot of the SM-X-NIM-ADPTR where the NIM is installed.
• port—Specifies the number of the individual interface port on a NIM.

The following example shows how to specify the first interface (0) on a NIM installed in the first subslot of a SM-X-NIM-ADPTR (0) installed in chassis slot 1:

Modifying the MAC Address on an Interface

The Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs 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 4000 series ISR.

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

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

Verifying a 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 is” field.

The following example shows that the MAC address is a44c.119e.0884 (bia a44c.119e.0884) for interface 0 on the NIM installed in subslot 0 of the SM-X-NIM-ADPTR installed in slot 1 of the Cisco ISR 4451-X:

Configuring the Hot Standby Router Protocol

The Hot Standby Router Protocol (HSRP) provides high network availability because it routes IP traffic from hosts without relying on the availability of any single router. HSRP is used in a group of routers for selecting an active router and a standby router. (An active router is the router of choice for routing packets; a standby router is a router that takes over the routing duties when an active router fails, or when preset conditions are met).

HSRP is enabled on an interface by entering the standby [ group-number ] ip [ ip-address [ secondary ]] command. The standby command is also used to configure various HSRP elements. This document does not discuss more complex HSRP configurations. For additional information on configuring HSRP, refer to the HSRP section of the Cisco IP Configuration Guide publication that corresponds to your Cisco IOS XE software release. In the following HSRP configuration, standby group 2 on Gigabit Ethernet port 2/0/0 is configured at a priority of 110 and is also configured to have a preemptive delay should a switchover to this port occur:

Verifying HSRP

To verify the HSRP information, use the show standby command in EXEC mode:

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 NIM 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 subinterface. 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 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.

Different encapsulation methods and the number of MPLS MTU labels add additional overhead to a packet. For example, Subnetwork Access Protocol (SNAP) encapsulation adds an 8-byte header, dot1q encapsulation adds a 2-byte header, and each MPLS label adds a 4-byte header ( n labels x 4 bytes).

For Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs on the Cisco 4000 series ISR, the default MTU size is 1500 bytes. The maximum configurable MTU is 9216 bytes. The NIM automatically adds an additional 22 bytes to the configured MTU size to accommodate some of the additional overhead.

Note In the Cisco 4000 series ISR, 2RU and 2RU-Fixed chassis, the MTU size for the Management Ethernet interface (Interface GigabitEthernet 0) is limited to 4470 bytes.

Interface MTU Configuration Guidelines

When configuring the interface MTU size on a Gigabit Ethernet NIM on a Cisco 4000 series ISR, 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

• 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:

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

Verifying the MTU Size

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

The following example shows an MTU size of 1500 bytes for interface port 0 on the Gigabit Ethernet NIM installed in the top subslot (0) of the SM-X-NIM-ADPTR that is located in slot 2 of the Cisco ISR 4451-X:

Configuring the Encapsulation Type

By default, the interfaces on the Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs support Advanced Research Projects Agency (ARPA) encapsulation. They do not support configuration of service access point or SNAP encapsulation for transmission of frames.

The only other encapsulation supported by the NIM interfaces is IEEE 802.1Q encapsulation for virtual LANs (VLANs).

Configuring Autonegotiation on an Interface

The Gigabit Ethernet interfaces use a connection-setup algorithm called autonegotiation. Autonegotiation allows the local and remote devices to configure compatible settings for communication over the link. Using autonegotiation, each device advertises its transmission capabilities and then agrees upon the settings to be used for the link.

For the Gigabit Ethernet interfaces on Cisco 4000 series ISR, flow control is autonegotiated when autonegotiation is enabled. Autonegotiation is enabled by default.

The following guidelines should be followed regarding autonegotiation:

• 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 will not come up properly on both ends.
• Flow control is enabled by default.
• Flow control will be on if autonegotiation is disabled on both ends of the link.

Enabling Autonegotiation

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

Disabling Autonegotiation

Autonegotiation is automatically enabled and can be disabled on the Gigabit Ethernet interfaces on the Cisco 4000 series ISR. During autonegotiation, advertisement for flow control, speed, and duplex occurs, depending on the media (fiber or copper) in use. If the interface is connected to a link that has autonegotiation disabled, autonegotiation should either be re-enabled on the other end of the link or disabled on the Gigabit Ethernet NIM, if possible. Both ends of the link will not come up properly if only one end of the link has disabled autonegotiation.

Speed and duplex configurations can be advertised using autonegotiation. However, the only values that are negotiated are:

• For Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs using RJ-45 copper interfaces—1000 Mbps for speed and full-duplex mode. Link speed is not negotiated when using fiber interfaces.

From a user's perspective, these settings are not really negotiated, but rather are enabled using autonegotiation. The SFPs for Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs support 1000Base-X, and the IEEE 1000Base-X standard for fiber does not support negotiation of link speed.

To disable autonegotiation, use the following command in interface configuration mode:

Configuring Speed and Duplex

Note When using the SFP-GE-T, you must configure both the speed and duplex modes.

To configure the speed for a Gigabit Ethernet interface, use the speed command in interface configuration mode. To return to the default setting, use the no form of this command:

To configure duplex operation on an interface, use the duplex command in interface configuration mode. Use the no form of this command to return to the default value.

Configuring the Media Type

The Gigabit Ethernet NIMs support two media types: RJ-45 and SFP. Use the media-type configuration command to select either the RJ-45 or SFP for a given port.

NIM Port and FPGE Difference

The Cisco 1GE-CU-SFP and 2GE-CU-SFP NIM support media auto-select. However, it uses VSC8584/8552 as its PHY. Due to this PHy limitation, the media auto-select behaves different with the behavior of FPGE and Cisco 6-port GE SFP Service Module and Cisco 4-port GE SFP and 1-port 10 GE SFP Service Module. This table provides the difference between NIM port and FPGE:

Configuring Auto-Media-Detection and Auto-Failover

The Gigabit Ethernet NIMs supports the auto-detection and auto-failover feature. You can configure the media for failover redundancy when the network goes down.

Enabling Auto-Media-Detection

When the media-type is not configured, the auto-select feature is enabled by default. The auto-select feature automatically detects the media that is connected and links it up. If both the media are connected, RJ-45 is preferred as the primary media.

Enabling Auto-Failover

The primary media is explicitly indicated as SFP or RJ-45. When the router receives an indication that the primary media is down, the secondary failover media is enabled. After the switchover, when the primary media is restored, the media switch backs to the primary media depending on the module and SFP type.

To enable auto-detect or auto-failover, use the following commands beginning in global configuration mode:

Configuring a Subinterface on a VLAN

You can configure subinterfaces on the Gigabit Ethernet NIM interfaces on a VLAN using IEEE 802.1Q encapsulation. Cisco Discovery Protocol (CDP) is disabled by default on the Gigabit Ethernet NIM interfaces and subinterfaces on the Cisco 4000 series ISR.

To configure a NIM interface on a VLAN, use the following commands beginning in global configuration mode:

Verifying Subinterface Configuration on a VLAN

To verify the configuration of a subinterface and its status on the VLAN, use the show vlans privileged EXEC command.

The following example shows the status of subinterface number 1 on port 0 on the NIM in VLAN number 200:

Saving the Configuration

To save your running configuration to nonvolatile random-access memory (NVRAM), use the following command in privileged EXEC configuration mode:

For information about managing your system image and configuration files, refer to the Cisco IOS Configuration Fundamentals Configuration Guide and Cisco IOS Configuration Fundamentals Command Reference publications that correspond to your Cisco IOS software release.

Shutting Down and Restarting an Interface on a Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs

You can shut down and restart any of the interface ports on Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs independently of each other. Shutting down an interface stops traffic and enters the interface into an “administratively down” state.

There are no restrictions for online insertion and removal (OIR) on Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs. Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs can be removed from a SM-X-NIM-ADPTR at any time. SM-X-NIM-ADPTRs populated with any type of Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs can be removed from the router at any time.

If you are preparing for an OIR of a Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs, it is not necessary to independently shut down each of the interfaces prior to deactivation of the NIM. The hw-module subslot stop command automatically stops traffic on the interfaces and deactivates them along with the Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs in preparation for OIR.

In similar fashion, you do not need to independently restart any interfaces on a Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs after OIR of a Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs or SM-X-NIM-ADPTR.

To shut down an interface on Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs, use the following command in interface configuration mode:

To restart an interface on Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs, use the following command in interface configuration mode:

Configuring Ethernet Flow Control

To configure Ethernet flow control per queue per port, use the following commands in the interface configuration mode:

Verifying Per-Port Interface Status

To find detailed interface information on a per-port basis for the Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs, use the show interfaces gigabitethernet command.

The following example provides sample output for interface port 0 on the NIM located in the top subslot (0) of the SM-X-NIM-ADPTR that is installed in slot 2 of the Cisco ISR 4451-X:

Basic Interface Configuration

The following example shows how to enter the global configuration mode 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 Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs that is located in subslot 0 of the SM-X-NIM-ADPTR that is installed in slot 2 of the Cisco ISR 4451-X:

MAC Address Configuration

The following example shows how to change the default MAC address on the interface to 1111.2222.3333:

MTU Configuration

The following example shows how to set the MTU interface to 9216 bytes.

Note Note: The Cisco 1GE-CU-SFP and 2GE-CU-SFP NIMs automatically adds an additional 22 bytes to the configured MTU interface size.

VLAN Configuration

The following example shows how to create the subinterface number 268 on NIM interface port 2 (the third port), and configure the subinterface on the VLAN with the ID number 268, using IEEE 802.1Q encapsulation:

Additional References

Related Documents

MIBs

Technical Assistance

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

© 2015 Cisco Systems, Inc. All rights reserved.