Contents

• Configuring LAN Interfaces
• Finding Feature Information
• Configuring Ethernet Fast Ethernet or Gigabit Ethernet Interfaces
• Ethernet Fast Ethernet and Gigabit Ethernet Interface Configuration Task List
• Specifying an Ethernet Fast Ethernet or Gigabit Ethernet Interface
• Specifying an Ethernet Encapsulation Method
• Specifying Full-Duplex Operation
• Specifying the Media and Connector Type
• Extending the 10BASE-T Capability
• Configuring Fast Ethernet 100BASE-T
• Configuring PA-12E 2FE Port Adapters
• Configuring the PA-12E 2FE Port Adapter
• Configuring the PA-12E 2FE Port Adapter
• Monitoring and Maintaining the PA-12E 2FE Port Adapter
• Configuring Bridge Groups Using the 12E 2FE VLAN Configuration WebTool
• Configuring the 100VG-AnyLAN Port Adapter
• Configuring the Cisco 7200-I O-GE+E and Cisco 7200-I O-2FE E Input Output Controllers
• Cisco 7200-I O-GE+E and Cisco 7200-I O-2FE E Configuration Task List
• Configuring the Interface Transmission Mode
• Configuring Interface Speed
• Configuring the Ethernet Fast Ethernet and Gigabit Ethernet Interfaces
• Verifying the Configuration
• Monitoring and Maintaining the Cisco 7200-I O GE+E and Cisco 7200-I O-2FE E
• Configuring an FDDI Interface
• Source-Route Bridging over FDDI on Cisco 4000-M Cisco 4500-M and Cisco 4700-M Routers
• Particle-Based Switching of Source-Route Bridge Packets on Cisco 7200 Series Routers
• Using Connection Management Information
• FDDI Configuration Task List
• Specifying a FDDI Interface
• Enabling FDDI Bridging Encapsulation
• Enabling Full-Duplex Mode on the FDDI Interface
• Setting the Token Rotation Time
• Setting the Transmission Valid Timer
• Controlling the Transmission Timer
• Modifying the C-Min Timer
• Modifying the TB-Min Timer
• Modifying the FDDI Timeout Timer
• Controlling SMT Frame Processing
• Enabling Duplicate Address Checking
• Setting the Bit Control
• Controlling the CMT Microcode
• Starting and Stopping FDDI
• Setting FDDI Frames per Token Limit
• Controlling the FDDI SMT Message Queue Size
• Preallocating Buffers for Bursty FDDI Traffic
• Configuring a Hub Interface
• Enabling a Hub Port
• Disabling or Enabling Automatic Receiver Polarity Reversal
• Disabling or Enabling the Link Test Function
• Enabling Source Address Control
• Enabling SNMP Illegal Address Trap
• Configuring a Token Ring Interface
• Particle-Based Switching of Source-Route Bridge Packets on Cisco 7200 Series Routers
• Dedicated Token Ring Port Adapter
• Token Ring Interface Configuration Task List
• Specifying a Token Ring Interface
• Enabling Early Token Release
• Configuring PCbus Token Ring Interface Management
• Enabling a Token Ring Concentrator Port
• Monitoring and Maintaining the Port
• LAN Interface Configuration Examples
• Ethernet Encapsulation Enablement Example
• Full-Duplex Enablement Operation Example
• PA-12E 2FE Port Configuration Examples
• PA-VG100 Port Adapter Configuration Example
• Cisco 7200-I O-GE+E and Cisco 7200-I O-2FE E Configuration Examples
• Configuring the Gigabit Ethernet Interface on the Cisco 7200-I O-GE+E
• Configuring Autonegotiation on the Cisco 7200-I O-2FE E
• Fast EtherChannel Configuration Examples
• FDDI Frames Configuration Example
• Hub Configuration Examples
• Hub Port Startup Examples
• Source Address for an Ethernet Hub Port Configuration Examples
• Hub Port Shutdown Examples
• SNMP Illegal Address Trap Enablement for Hub Port Example

Configuring LAN Interfaces

---

• Finding Feature Information
• Configuring Ethernet Fast Ethernet or Gigabit Ethernet Interfaces
• Configuring the Cisco 7200-I O-GE+E and Cisco 7200-I O-2FE E Input Output Controllers
• Configuring an FDDI Interface
• Configuring a Hub Interface
• Configuring a Token Ring Interface
• LAN Interface Configuration Examples

Configuring Ethernet Fast Ethernet or Gigabit Ethernet Interfaces

Cisco supports 10-Mbps Ethernet, 100-Mbps Fast Ethernet, and 1000-Mbps Gigabit Ethernet. Support for the 10-Mbps, 100-Mbps, and 1000-Mbps Ethernet interface is supplied on various Ethernet network interface cards or systems.

Fast Ethernet NP-1FE Module Benefits

• VLAN routing--VLAN support enables network managers to group users logically rather than by physical location. The high performance of the underlying Cisco 4700, combined with the feature-rich NP-1FE, makes it an ideal combination for a low-density, higher-performance application such as inter-VLAN routing.

• High-speed interconnections--The Fast Ethernet interface enables network managers to implement Fast-Ethernet routing solutions for optimal cost and performance across a wide range of applications, including campus or enterprise backbones and data centers. It is also a low-cost way to provide Fast-Ethernet access to traditional low-speed WAN services.

• Local area network aggregation--The Cisco 4500 or the Cisco 4700 series routers can support as many as 12 Ethernet, 4 Token Ring, or 1 FDDI segment. ISDN interfaces are also supported.

With the Catalyst 3000 or Catalyst 5000 system, the Fast Ethernet processor can be used to aggregate up to twelve 10-Mbps LANs and give them high-speed access to such Layer 3 routing services as providing firewalls and maintaining access lists.

Cisco 7200 Series Routers with Fast Ethernet and Gigabit Ethernet

Cisco 7200 series routers support an I/O controller with an RJ-45 interface for Fast Ethernet support and an I/O controller with both RJ-45 and GBIC interfaces for Gigabit Ethernet support.

The Cisco 7200-I/O-GE+E is an Input/Output controller that provides one Gigabit Ethernet and one Ethernet port. It is equipped with a GBIC receptacle for 1000 Mbps operation and an RJ-45 receptacle for 10-Mbps operation.

The Cisco 7200-I/O-2FE/E is an I/O controller that provides two autosensing Fast Ethernet ports and is equipped with two RJ-45 receptacles for 10/100 Mbps operation.

You can configure the Fast Ethernet port for use at 100-Mbps full-duplex or half-duplex operation (half duplex is the default). The Fast Ethernet port is equipped with either a single MII receptacle or an MII receptacle and an RJ-45 receptacle. To support this new feature, the media-type interface command has been modified. The media-type command now supports two options:

• 100BASE-X --Specifies an RJ-45 100BASE-X physical connection.

• mii --Specifies a media-independent interface.

The Gigabit Ethernet interface on the Cisco 7200-I/O-GE+E operates at full duplex and cannot be configured for half-duplex mode.

Second-generation Fast Ethernet Interface Processors (FEIP2-DSW-2TX and FEIP2-DSW-2FX) are available on Cisco 7500 series routers and on Cisco 7000 series routers with the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI). The FEIP2-DSW is a dual-port, fixed-configuration interface processor that provides two 100-Mbps Fast Ethernet (FE) interfaces. Each interface on the FEIP2-DSW supports both half-duplex and full-duplex.

Refer to the Cisco Product Catalog for specific platform and hardware compatibility information.

Use the show interfaces, show controllers mci, and show controllers cbusEXEC commands to display the Ethernet port numbers. These commands provide a report for each interface supported by the router or access server.

Use the show interfaces fastethernetcommand to display interface statistics, and use the show controllers fastethernet to display information about the Fast Ethernet controller chip. The output shows statistics, including information about initialization block information, transmit ring, receive ring, and errors.

Use the show interfaces gigabitethernetcommand to display interface statistics, and use the show controllers gigabitethernet to display the information about the Gigabit Ethernet controller chip. The output shows statistics, including information about initialization block information, transmit ring, receive ring, and errors.

• Ethernet Fast Ethernet and Gigabit Ethernet Interface Configuration Task List

Ethernet Fast Ethernet and Gigabit Ethernet Interface Configuration Task List

To configure features on an Ethernet, Fast Ethernet, or Gigabit Ethernet interface, perform the tasks in the following sections:

• Specifying an Ethernet Fast Ethernet or Gigabit Ethernet Interface
• Specifying an Ethernet Encapsulation Method
• Specifying Full-Duplex Operation
• Specifying the Media and Connector Type
• Extending the 10BASE-T Capability
• Configuring Fast Ethernet 100BASE-T
• Configuring PA-12E 2FE Port Adapters
• Configuring the 100VG-AnyLAN Port Adapter

Specifying an Ethernet Fast Ethernet or Gigabit Ethernet Interface

To specify an Ethernet interface and enter interface configuration mode, use one of the following commands in global configuration mode.

Command or Action	Purpose
Router(config)# interface ethernet number	Enters interface configuration mode.
Router(config)# interface ethernet slot / port	Enters interface configuration mode for the Cisco 7200 and Cisco 7500 series routers.
Router(config)# interface ethernet slot / port-adapter / port	Enters interface configuration mode for Cisco 7500 series routers.
Router(config)# interface fastethernet number	Enters interface configuration mode for the Cisco 4000 series with a Fast Ethernet NIM installed.
Router(config)# interface fastethernet slot / port	Specifies a Fast Ethernet interface and enters interface configuration mode on the Cisco 7200 series routers.
Router(config)# interface fastethernet slot / port-adapter / port	Specifies a Fast Ethernet interface and enters interface configuration mode on the Cisco 7500 series routers.
Router(config)# interface gigabitethernet slot / port	Specifies a Gigabit Ethernet interface and enters interface configuration mode on the Cisco 7200 series routers.

To display the Fast Ethernet slots and ports, use the show interfaces fastethernetcommand. The Fast Ethernet network interface module (NIM) and the Fast Ethernet Interface Processor (FEIP) default to half-duplex mode.

Specifying an Ethernet Encapsulation Method

Currently, there are three common Ethernet encapsulation methods:

• The standard Advanced Research Projects Agency (ARPA) Ethernet Version 2.0 encapsulation, which uses a 16-bit protocol type code (the default encapsulation method).

• Service access point (SAP) IEEE 802.3 encapsulation, in which the type code becomes the frame length for the IEEE 802.2 LLC encapsulation (destination and source Service Access Points, and a control byte).

• The SNAP method, as specified in RFC 1042, >Standard for the Transmission of IP Datagrams Over IEEE 802 Networks , which allows Ethernet protocols to run on IEEE 802.2 media.

The encapsulation method that you use depends upon the routing protocol that you are using, the type of Ethernet media connected to the router or access server, and the routing or bridging application that you configure.

To establish Ethernet encapsulation of IP packets, use one of the following commands in interface configuration mode.

Command or Action	Purpose
Router(config-if)# encapsulation arpa	Selects ARPA Ethernet encapsulation.
Router(config-if)# encapsulation sap	Selects SAP Ethernet encapsulation.
Router(config-if)# encapsulation snap	Selects SNAP Ethernet encapsulation.

For an example of selecting Ethernet encapsulation for IP, see the Ethernet Encapsulation Enablement Example.

Specifying Full-Duplex Operation

The default is half-duplex mode on the FEIP2-DSW-2FX. To enable full-duplex mode on the FEIP2-DSW-2FX (for a maximum aggregate bandwidth of 200 Mbps), use either of the following commands in interface configuration mode.

Command or Action	Purpose
Router(config-if)# full-duplex or Router(config-if)# no half-duplex	Enables full-duplex on the Fast Ethernet interface of the FEIP2-DSW-2FX.

For an example of enabling full-duplex mode on Fast Ethernet, see the Full-Duplex Enablement Operation Example.

Caution

To prevent system problems, do not configure both FEIP2-DSW-2FX interfaces for full-duplex operation at the same time. The FEIP2-DSW-2TX supports half-duplex only and should not be configured for full-duplex.

Specifying the Media and Connector Type

You can specify that the Ethernet network interface module (NIM) on the Cisco 4000 series routers use either the default of an attachment unit interface (AUI) and a 15-pin connector, or 10BASE-T and an RJ-45 connector. To do so, use one of the following commands in interface configuration mode.

Command or Action	Purpose
Router(config-if)# media-type aui	Selects a 15-pin Ethernet connector.
Router(config-if)# media-type 10baset	Selects an RJ-45 Ethernet connector.

The default media connector type is an RJ-45 or SC (fiber-optic) connector. You can specify that the interface uses either an MII connector, or an RJ-45 or SC (fiber-optic) connector (this is the default). To do so, use one of the following commands in interface configuration mode.

Command or Action	Purpose
Router(config-if)# media-type mii	Selects an MII Ethernet connector.
Router(config-if)# media-type 100basex	Selects an RJ-45 Ethernet connector for the FEIP2-DSW-2TX or an SC connector for the FEIP2-DSW-2FX.

Note	When using the I/O controller that is equipped with an MII receptacle and an RJ-45 receptacle, only one receptacle can be configured for use at a time.

Extending the 10BASE-T Capability

On a Cisco 4000 series or Cisco 4500 series routers, you can extend the twisted-pair 10BASE-T capability beyond the standard 100 meters by reducing the squelch (signal cutoff time). This feature applies only to the LANCE controller 10BASE-T interfaces. LANCE is the AMD controller chip for the Cisco 4000 and Cisco 4500 Ethernet interface and does not apply to the Fast Ethernet interface.

To reduce squelch, use the first command in the following table in interface configuration mode. You can later restore the squelch by using the second command.

Command or Action	Purpose
Router(config-if)# squelch reduced	Reduces the squelch.
Router(config-if)# squelch normal	Returns squelch to normal.

Configuring Fast Ethernet 100BASE-T

You must configure the Fast Ethernet 100BASE-T interface on a Cisco AS5300 so that it can be recognized as a device on the Ethernet LAN. The Fast Ethernet interface supports 10- and 100-Mbps speeds with the 10BASE-T and 100BASE-T routers, hubs, and switches.

To configure the interface, use the following commands beginning in privileged EXEC mode.

SUMMARY STEPS

1.    Router# configure terminal

2.    Router(config)# interface fastethernet number

3.    Router(config-if)# ip address address subnet-mask

4.    Router(config-if)# speed {10 | 100 | auto}

5.    Router(config-if)# duplex {full | half | auto}

DETAILED STEPS

	Command or Action	Purpose
Step 1	Router# configure terminal	Enters global configuration mode.
Step 2	Router(config)# interface fastethernet number	Enters Fast Ethernet interface configuration mode.
Step 3	Router(config-if)# ip address address subnet-mask	Assigns an IP address and subnet mask to the interface.
Step 4	Router(config-if)# speed {10 | 100 | auto}	Assigns a speed to the interface. The default is 100 Mbps.1 For relationship between duplex and speed command options, see the table below.
Step 5	Router(config-if)# duplex {full | half | auto}	Sets up the duplex configuration on the Fast Ethernet interface. The default is half duplex.Configuring Fast Ethernet 100BASE-T For relationship between duplex and speed command options, see the table below.

¹ The auto option automatically negotiates the speed on the basis of the speed and the peer router, hub, or switch media.

What to Do Next

To use the autonegotiation capability (that is, to detect speed and duplex modes automatically), you must set both speed and duplex command to auto. Setting the speed command to auto negotiates speed only, and setting duplex command to auto negotiates duplex only. The table below describes the performance of the access server for different combinations of the duplex and speed command options. The specified duplex command option plus the specified speed command option produces the resulting system action.

Table 1 Relationship Between duplex and speed Command Options

duplex Command	speed Command	Resulting System Actions
Router(config-if)# duplex auto	speed auto	Autonegotiates both speed and duplex modes.
Router(config-if)# duplex auto	speed 10 or speed 100	Autonegotiates both speed and duplex modes.
Router(config-if)# duplex half or Router(config-if)# duplex full	speed auto	Autonegotiates both speed and duplex modes.
Router(config-if)# duplex half	speed 10	Forces 10 Mbps and half duplex.
Router(config-if)# duplex full	speed 10	Forces 10 Mbps and full duplex.
Router(config-if)# duplex half	speed 100	Forces 100 Mbps and half duplex.
Router(config-if)# duplex full	speed 100	Forces 100 Mbps and full duplex.

Configuring PA-12E 2FE Port Adapters

The PA-12E/2FE Ethernet switch port adapter provides Cisco 7200 series routers with up to twelve 10-Mbps and two 10/100-Mbps switched Ethernet (10BASE-T) and Fast Ethernet (100BASE-TX) interfaces for an aggregate bandwidth of 435 Mbps, full-duplex. The PA-12E/2FE port adapter supports the Ethernet, IEEE 802.3, and IEEE 802.3u specifications for 10-Mbps and 100-Mbps transmission over unshielded twisted pair (UTP) cables.

The PA-12E/2FE port adapter offloads Layer 2 switching from the host CPU by using store-and-forward or cut-through switching technology between interfaces within the same virtual LAN (VLAN) on the PA-12E/2FE port adapter. The PA-12E/2FE port adapter supports up to four VLANs (bridge groups).

Note	The PA-12E/2FE port adapter is a dual-width port adapter, which means it occupies two horizontally aligned port adapter slots when installed in a Cisco 7200 series router. (Single-width port adapters occupy individual port adapter slots in a Cisco 7200 series router.)

All interfaces on the PA-12E/2FE port adapter support autosensing and autonegotiation of the proper transmission mode (half-duplex or full-duplex) with an attached device. The first two PA-12E/2FE interfaces (port 0 and port 1) also support autosensing and autonegotiation of the proper connection speed (10 Mbps or 100 Mbps) with an attached device. If an attached device does not support autosensing and autonegotiation of the proper transmission mode, the PA-12E/2FE interfaces attached to the device automatically enter half-duplex mode. Use the show system:running-configcommand to determine if a PA-12E/2FE interface is autosensing and autonegotiating the proper transmission mode with an attached device. Use the full-duplexand the half-duplex commands to change the transmission mode of a PA-12E/2FE interface. After changing the transmission mode, use the show interfacescommand to verify the transmission mode of the interface.

Note

If you use the full-duplexand the half-duplex commands to change the transmission mode of the first two PA-12E/2FE interfaces (port 0 and port 1), the transmission speed of the two PA-12E/2FE interfaces automatically defaults to 100-Mbps. The first two PA-12E/2FE interfaces operate only at 10 Mbps when the interfaces are autosensing and autonegotiating the proper connection speed (10 Mbps or 100 Mbps) with an attached device.

To configure the PA-12E/2FE port adapter, perform the tasks in the following sections. Each task in the list is identified as either required or optional.

Note

If you plan to use a PA-12E/2FE interface to boot from a network (using TFTP), ensure that the interface is configured for a loop-free environment, that an IP address is configured for the interface’s bridge-group virtual interface, and that system boot image 11.2(10)P is installed on your router (use the show version command to view the system boot image of your router). Then, before booting from the network server, use the bridge-group bridge-group number spanning-disabled command to disable the Spanning Tree Protocol configured on the interface to keep the TFTP server from timing out and closing the session. For detailed information about booting from a network using TFTP, loading a system image from a network server, and configuring the Spanning Tree Protocol on your Cisco 7200 series router, refer to the PA-12E/2FE Ethernet Switch Port Adapter book that accompanies the hardware and to the Cisco IOS Bridging and IBM Networking Configuration Guide.

For information on other commands that can be used to configure a PA-12E/2FE port adapter, refer to the CiscoIOS Interface and Hardware Component Command Reference . For information on bridging, refer to the "Configuring Transparent Bridging" chapter in the CiscoIOS Bridging and IBM Networking Configuration Guide .

For PA-12E/2FE port adapter configuration examples, see the PA-12E 2FE Port Configuration Examples.

• Configuring the PA-12E 2FE Port Adapter
• Configuring the PA-12E 2FE Port Adapter
• Monitoring and Maintaining the PA-12E 2FE Port Adapter
• Configuring Bridge Groups Using the 12E 2FE VLAN Configuration WebTool

Configuring the PA-12E 2FE Port Adapter

This section provides instructions for a basic configuration. You might also need to enter other configuration commands depending on the requirements for your system configuration and the protocols that you plan to route on the interface. For complete descriptions of configuration commands and the configuration options available, refer to the other configuration guides and command references in the Cisco IOS documentation set.

To configure the interfaces on the PA-12E/2FE port adapter, use the following commands beginning in global configuration mode.

SUMMARY STEPS

1.    Router(config)# bridge bridge-group protocol ieee

2.    Router(config)# interface fastethernet slot / port

3.    Router(config-if)# bridge-group bridge-group

4.    Router(config-if)# cut-through [receive | transmit]

5.    Router(config-if)# full-duplex

6.    Router(config-if)# no shutdown

7.    Router(config-if)# exit

8.    Repeat Steps 1 through 7 for each interface.

9.    Router# copy system:running-config nvram:startup-config

DETAILED STEPS

	Command or Action	Purpose
Step 1	Router(config)# bridge bridge-group protocol ieee	Specifies the type of Spanning Tree Protocol. The PA-12E/2FE port adapter supports DEC and IEEE Spanning Tree Protocols; however, we recommend using the IEEE protocol when configuring bridge groups.
Step 2	Router(config)# interface fastethernet slot / port Example: (ports 0 and 1) Example: Router(config)# interface ethernet slot / port Example: (ports 2 through 13)	Enters interface configuration mode for the interface that you want to configure.
Step 3	Router(config-if)# bridge-group bridge-group	Assigns a bridge group to the interface.
Step 4	Router(config-if)# cut-through [receive | transmit]	(Optional) Configures the interface for cut-through switching technology. The default is store-and-forward (that is, no cut-through).
Step 5	Router(config-if)# full-duplex	(Optional) Configures the transmission mode for full-duplex, if an attached device does not support autosensing or autonegotiation. The default is half-duplex.
Step 6	Router(config-if)# no shutdown	Restarts the interface.
Step 7	Router(config-if)# exit	Returns to global configuration mode.
Step 8	Repeat Steps 1 through 7 for each interface.	--
Step 9	Router# copy system:running-config nvram:startup-config	Saves the new configuration to memory.

Configuring the PA-12E 2FE Port Adapter

To enable integrated routing and bridging on the bridge groups, use the following commands beginning in global configuration mode.

SUMMARY STEPS

1.    Router(config)# bridge irb

2.    Router(config)# interface bvi bridge-group

3.    Router(config-if)# ip address ip-address mask

4.    Router(config-if)# no shutdown

5.    Router(config-if)# exit

6.    Repeat Steps 1 through 5 for each bridge group.

7.    Router(config)# bridge bridge-group route protocol

8.    Router(config)# exit

9.    Router# copy system:running-config nvram:startup-config

DETAILED STEPS

	Command or Action	Purpose
Step 1	Router(config)# bridge irb	Enables integrated routing and bridging.
Step 2	Router(config)# interface bvi bridge-group	Enables a virtual interface on a bridge group.
Step 3	Router(config-if)# ip address ip-address mask	Assigns an IP address and subnet mask to the bridge-group virtual interface.
Step 4	Router(config-if)# no shutdown	Restarts the interface.
Step 5	Router(config-if)# exit	Returns to global configuration mode.
Step 6	Repeat Steps 1 through 5 for each bridge group.	--
Step 7	Router(config)# bridge bridge-group route protocol	Specifies the protocol for each bridge group.
Step 8	Router(config)# exit	Exits global configuration mode.
Step 9	Router# copy system:running-config nvram:startup-config	Saves the new configuration to memory.

Monitoring and Maintaining the PA-12E 2FE Port Adapter

After configuring the new interface, you can display its status and verify other information. To display information about the PA-12E/2FE port adapter, use the following commands in EXEC mode.

Command or Action	Purpose
Router# show version	Displays the configuration of the system hardware, the software version, the names and sources of configuration files, and the boot image.
Router# show controllers	Displays all current port adapters and their interfaces
Router# show interfaces fastethernet slot / port (ports 0 and 1) or Router# show interfaces ethernet slot / port (ports 2 through 13)	Displays the interfaces so that you can verify that they have the correct slot number and that the interface and line protocol are in the correct state.
Router# show bridge group	Displays all bridge groups and their interfaces.
Router# show interfaces fastethernet slot / port irb (ports 0 and 1) or Router# show interfaces ethernet slot / port irb (ports 2 through 13)	Displays the routed protocol so you can verify that it is configured correctly for each interface.
Router# show protocols	Displays the protocols configured for the entire system and specific interfaces.
Router# show pas eswitch addresses fastethernet slot / port (ports 0 and 1) or Router# show pas eswitch addresses ethernet slot / port (ports 2 through 13)	Displays the Layer 2 learned addresses for each interface.
Router# more system:running-config	Displays the running configuration file.
Router# more nvram:startup-config	Displays the configuration stored in NVRAM.

Configuring Bridge Groups Using the 12E 2FE VLAN Configuration WebTool

The 12E/2FE VLAN Configuration WebTool, shown in the figure below, is a web browser-based Java applet that displays configured interfaces and bridge groups for PA-12E/2FE port adapters installed in Cisco routers. With the WebTool you can perform the following tasks:

• Create and delete bridge groups (also referred to as VLANs)

• Add and remove PA-12E/2FE interfaces from bridge groups

• Assign colors to bridge groups and PA-12E/2FE interfaces

• Administratively shut down (disable) and bring up (enable) PA-12E/2FE interfaces

• View the bridge-group status of each PA-12E/2FE interface

You can access the 12E/2FE VLAN Configuration WebTool from the home page of your router. For complete procedures on how to use the VLAN Configuration WebTool, refer to the PA-12E/2FE Ethernet Switch Port Adapter book that accompanies the hardware.

All Cisco routers that run Cisco IOS Release 11.0 or later have a home page. All Cisco router home pages are password protected. Contact your network administrator if you do not have the name or password for your Cisco 7200 series router.

If your router has an installed PA-12E/2FE port adapter, the 12E/2FE VLAN Configuration WebTool shown in the figure above can be accessed from the home page of the router using a Java-enabled web browser.

Configuring the 100VG-AnyLAN Port Adapter

The 100VG-AnyLAN port adapter (PA-100VG) is available on Cisco 7200 series routers and on Cisco 7500 series routers.

The PA-100VG provides a single interface compatible with and specified by IEEE 802.12 to support 100 Mbps over Category 3 or Category 5 UTP cable with RJ-45 terminators. The PA-100VG supports 802.3 Ethernet packets and can be monitored with the IEEE 802.12 Interface MIB.

To configure the PA-100VG port adapter, use the following commands beginning in global configuration mode.

SUMMARY STEPS

1.    Do one of the following:

• Router(config)# interface vg-anylan slot / port
• (Cisco 7200)

2.    Router(config-if)# ip address ip-address mask

3.    Router(config-if)# frame-type ethernet

DETAILED STEPS

	Command or Action	Purpose
Step 1	Do one of the following: Router(config)# interface vg-anylan slot / port (Cisco 7200) Example: Router(config)# interface vg-anylan slot / port-adapter / port Example: (Cisco 7500)	Specifies a 100VG-AnyLAN interface and enters interface configuration.
Step 2	Router(config-if)# ip address ip-address mask	Specifies the IP address and subnet mask to the interface.
Step 3	Router(config-if)# frame-type ethernet	Configures the frame type. Currently, only Ethernet frames are supported. The frame type defaults to Ethernet.

What to Do Next

Note	The port number for the 100VG-AnyLAN port adapter is always 0.

Configuring the PA-100VG interface is similar to configuring an Ethernet or Fast Ethernet interface. To display information about the 100VG-AnyLAN port adapter, use the show interfaces vg-anylan EXEC command.

Configuring the Cisco 7200-I O-GE+E and Cisco 7200-I O-2FE E Input Output Controllers

The Cisco 7200-I/O-GE+E is an Input/Output controller that provides one Gigabit Ethernet and one Ethernet port. It is equipped with a GBIC receptacle for 1000-Mbps operation and an RJ-45 receptacle for 10-Mbps operation.

The Cisco 7200-I/O-2FE/E is an Input/Output controller that provides two autosensing Fast Ethernet ports and is equipped with two RJ-45 receptacles for 10/100-Mbps operation.

I/O controllers support the following features:

• Dual EIA/TIA-232 channels for local console and auxiliary ports

• NVRAM for storing the system configuration and environmental monitoring logs

• Two PC Card slots that hold Flash disks or Flash memory cards for storing the default Cisco IOS software image

• Flash memory for storing the boot helper image

• Two environmental sensors for monitoring the cooling air as it enters and leaves the chassis

• Cisco 7200-I O-GE+E and Cisco 7200-I O-2FE E Configuration Task List

Cisco 7200-I O-GE+E and Cisco 7200-I O-2FE E Configuration Task List

See the following sections for configuration tasks for the Cisco 7200-I/O-GE+E and the Cisco 7200-I/O-2FE/E feature. Each task in the list is identified as required or optional.

Note	For Cisco 7200 VXR routers used as router shelves in AS5800 Universal Access Servers, use the router-shelf / slot / port command format for all interface commands.

• Configuring the Interface Transmission Mode
• Configuring Interface Speed
• Configuring the Ethernet Fast Ethernet and Gigabit Ethernet Interfaces
• Verifying the Configuration
• Monitoring and Maintaining the Cisco 7200-I O GE+E and Cisco 7200-I O-2FE E

Configuring the Interface Transmission Mode

To configure the interface transmission mode, use the following commands beginning in privileged EXEC mode. The Fast Ethernet and Ethernet interfaces on the Cisco 7200-I/O-2FE/E are duplex auto by default.

SUMMARY STEPS

1.    Router# configure terminal

2.    Router(config)# interface fastethernet slot / port²

3.    Router(config)# duplex full

DETAILED STEPS

	Command or Action	Purpose
Step 1	Router# configure terminal	Enters global configuration mode and specifies that the console terminal is the source of the configuration subcommands.
Step 2	Router(config)# interface fastethernet slot / port2	Selects the Fast Ethernet interface to configure.
Step 3	Router(config)# duplex full	Changes the Fast Ethernet interface port transmission mode to full duplex from autonegotiation.

² Use the interface fastethernet router-shelf / slot / port command for a Cisco 7200 VXR used as a router shelf in an AS5800 Universal Access Server.

Configuring Interface Speed

To configure the two autosensing Ethernet/Fast Ethernet interfaces on the C7200-I/O-2FE/E, use the speed command. The the default interface speed is auto.The following procedure configures the C7200-I/O-2FE/E for a speed of 10 Mbps.

SUMMARY STEPS

1.    Router# configure terminal

2.    Router(Config)# interface ethernet slot / port³

3.    Router(Config-if)# interface fastethernet slot / port⁴

4.    Router(Config-if)# speed 10

DETAILED STEPS

	Command or Action	Purpose
Step 1	Router# configure terminal	Enters global configuration mode and specifies that the console terminal is the source of the configuration subcommands.
Step 2	Router(Config)# interface ethernet slot / port3	Selects the Ethernet interface to configure.
Step 3	Router(Config-if)# interface fastethernet slot / port4	Selects the Fast Ethernet interface to configure.
Step 4	Router(Config-if)# speed 10	Sets the Ethernet or Fast Ethernet interface speed to 10 Mbps.

³ Use the interface ethernet router-shelf / slot / port command for a Cisco 7200 VXR used as a router shelf in an AS5800 Universal Access Server.

⁴ Use the interface fastethernet router-shelf / slot / port command for a Cisco 7200 VXR used as a router shelf in an AS5800 Universal Access Server.

Configuring the Ethernet Fast Ethernet and Gigabit Ethernet Interfaces

The following procedure explains a basic configuration for an Ethernet, Fast Ethernet, or Gigabit Ethernet interface on a C7200-I/O-GE+E or a C7200-I/O-2FE/E.

SUMMARY STEPS

1.    Router# configure terminal

2.    Router(config)# interface ethernet slot / port⁵

3.    Router(config)# interface fastethernet slot / port⁶

4.    Router(config)# interface gigabitethernet slot / port⁷

5.    Router(config-if) # ip address ip-address mask

6.    Router(config-if)# duplex auto

7.    Router#(config-if)# Exit

DETAILED STEPS

	Command or Action	Purpose
Step 1	Router# configure terminal Example:	Enters global configuration mode and specifies that the console terminal is the source of the configuration subcommands.
Step 2	Router(config)# interface ethernet slot / port5 Example:	Selects the Ethernet interface on the I/O controller in slot 0 in port adapter slot 1 to configure.
Step 3	Router(config)# interface fastethernet slot / port6 Example:	Selects the Fast Ethernet interface on the I/O controller in slot 0 in port adapter slot 2 to configure.
Step 4	Router(config)# interface gigabitethernet slot / port7	Selects the Gigabit Ethernet interface on the I/O controller in slot 0 in port adapter slot 0 to configure.
Step 5	Router(config-if) # ip address ip-address mask	Assigns an IP address and subnet mask to the interface (if IP routing is enabled on the system).
Step 6	Router(config-if)# duplex auto	Changes the Fast Ethernet interface port transmission mode to autonegotiation.
Step 7	Router#(config-if)# Exit	Exits configuration mode.

⁵ Use the interface ethernet router-shelf / slot / port command for a Cisco 7200 VXR used as a router shelf in an AS5800 Universal Access Server.

⁶ Use the interface fastethernet router-shelf / slot / port command for a Cisco 7200 VXR used as a router shelf in an AS5800 Universal Access Server.

⁷ Use the interface gigabitethernet router-shelf / slot / port command for a Cisco 7200 VXR used as a router shelf in an AS5800 Universal Access Server.

Verifying the Configuration

Use the show interfaces {ethernet | fastethernet | gigabitethernet} command to verify that the interface and line protocol are in the correct state (up) and that the transmission mode is configured on the interface. You can configure full, half, or auto transmission mode for Ethernet and Fast Ethernet interfaces. You can configure forced transmission mode for Gigabit Ethernet interfaces. The following is sample output from the show interfaces gigabitethernet command.

Router# show interfaces gigabitethernet 0/0
GigabitEthernet0/0 is up, line protocol is up 
   Hardware is 82543 (Livengood), address is 00d0.ffb6.4c00 (bia 00d0.ffb6.4c00)
   Internet address is 10.1.1.0/0
   MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec, 
      reliability 255/255, txload 1/255, rxload 1/255
   Encapsulation ARPA, loopback not set
   Keepalive set (10 sec)
   Full-duplex mode, link type is autonegotiation, media type is SX
   output flow-control is on, input flow-control is on
   ARP type:ARPA, ARP Timeout 04:00:00
   Last input 00:00:04, output 00:00:03, output hang never
   Last clearing of "show interface" counters never
   Queueing strategy:fifo
   Output queue 0/40, 0 drops; input queue 0/75, 0 drops
   5 minute input rate 0 bits/sec, 0 packets/sec
   5 minute output rate 0 bits/sec, 0 packets/sec
      2252 packets input, 135120 bytes, 0 no buffer
      Received 2252 broadcasts, 0 runts, 0 giants, 0 throttles
      0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
      0 watchdog, 0 multicast, 0 pause input
      0 input packets with dribble condition detected
      2631 packets output, 268395 bytes, 0 underruns
      0 output errors, 0 collisions, 2 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

Monitoring and Maintaining the Cisco 7200-I O GE+E and Cisco 7200-I O-2FE E

To monitor and maintain the Gigabit Ethernet or Ethernet interfaces on the Cisco 7200-I/O-GE+E, use the following commands in privileged EXEC mode.

Command or Action	Purpose
Router# show controllers ethernet	Displays hardware and software information about the Ethernet interface.
Router# show interfaces ethernet slot/port8	Displays information about the Ethernet interface on the router.
Router# show controllers gigabitethernet	Displays hardware and software information about the Gigabit Ethernet interface.
Router# show interfaces gigabitethernet slot/port9	Displays information about a Gigabit Ethernet interface on the router.

⁸ Use the show interfaces ethernet router-shelf/slot/port command for a Cisco 7200 VXR used as a router shelf in an AS5800 Universal Access Server

⁹ Use the interface gigabitethernet router-shelf/slot/port command for a Cisco 7200 VXR used as a router shelf in an AS5800 Universal Access Server.

To monitor and maintain the Fast Ethernet or Ethernet interfaces on the Cisco 7200-I/O-2FE/E, use the following commands in privileged EXEC mode.

Command or Action	Purpose
Router# show controllers ethernet	Displays hardware and software information about the Ethernet interface.
Router# show interfaces ethernet slot/port10	Displays information about an Ethernet interface on the router.
Router# show controllers fastethernet	Displays hardware and software information about the Fast Ethernet interfaces.
Router# show interfaces fastethernet	Displays information about a Fast Ethernet interface on the router.

¹⁰ Use the show interfaces ethernet router-shelf/slot/port command for a Cisco 7200 VXR used as a router shelf in an AS5800 Universal Access Server.

Configuring an FDDI Interface

The FDDI is an ANSI-defined standard for a timed 100-Mbps token passing over a fiber-optic cable. FDDI is not supported on access servers.

A FDDI network consists of two counter-rotating, token-passing fiber-optic rings. On most networks, the primary ring is used for data communication and the secondary ring is used as a hot standby. The FDDI standard sets a total fiber length of 200 kilometers. (The maximum circumference of the FDDI network is only half the specified kilometers because of the wrapping or looping back of the signal that occurs during fault isolation.)

The FDDI standard allows a maximum of 500 stations with a maximum distance of 2 kilometers between active stations, when interconnecting them with multimode fiber, or a maximum distance of 10 kilometers between them when interconnected via single mode fiber, both of which are supported by FDDI interface controllers. The FDDI frame can contain a minimum of 17 bytes and a maximum of 4500 bytes. Cisco FDDI implementation supports Station Management (SMT) Version 7.3 of the X3T9.5 FDDI specification, offering a single MAC dual-attach interface that supports fault-recovery methods of dual attachment stations (DASs). The mid-range platforms also support single attachment stations (SASs).

Refer to the Cisco Product Catalog for specific information on platform and interface compatibility. For installation and configuration information, refer to the installation and configuration publication for the appropriate interface card or port adapter.

• Source-Route Bridging over FDDI on Cisco 4000-M Cisco 4500-M and Cisco 4700-M Routers
• Particle-Based Switching of Source-Route Bridge Packets on Cisco 7200 Series Routers
• Using Connection Management Information
• FDDI Configuration Task List

Source-Route Bridging over FDDI on Cisco 4000-M Cisco 4500-M and Cisco 4700-M Routers

Source-route bridging (SRB) is supported on the FDDI interface to the Cisco 4000-M, Cisco 4500-M, and Cisco 4700-M routers. For instructions on configuring autonomous FDDI SRB or fast-switching SRB over FDDI, refer to the "Configuring Source-Route Bridging" chapter of the CiscoIOS Bridging and IBM Networking Configuration Guide .

Particle-Based Switching of Source-Route Bridge Packets on Cisco 7200 Series Routers

SRB is supported over FDDI. Particle-based switching is supported for SRB packets (over FDDI and Token Ring) by default.

Particle-based switching adds scatter-gather capability to SRB to improve performance. Particles represent a communications data packet as a collection of noncontiguous buffers. The traditional Cisco IOS packet has a packet type control structure and a single contiguous data buffer. A particle packet has the same packet type control structure, but also maintains a queue of particle type structures, each of which manages its own block.

The scatter-gather architecture used by particle-based switching provides the following advantages:

• Allows drivers to use memory more efficiently (especially when using media that has a large maximum transmission unit [MTU]). For example, Token Ring buffers could be 512 bytes rather than 16 KB.

• Allows concurrent use of the same region of memory. For example, on IP multicast a single packet is received and sent out on multiple interfaces simultaneously.

• Allows insertion or deletion of memory at any location in a packet (not just at the beginning or end).

For information about configuring SRB over FDDI, refer to the "Configuring Source-Route Bridging" chapter of the CiscoIOS Bridging and IBM Networking Configuration Guide .

Using Connection Management Information

Connection management (CMT) is a FDDI process that handles the transition of the ring through its various states (off, on, active, connect, and so on) as defined by the X3T9.5 specification. The FIP (FDDI Interface Processor) provides CMT functions in microcode.

A partial sample output of the show interfaces fddi command follows, along with an explanation of how to interpret the CMT information in the output.

Phy-A state is active, neighbor is B, cmt signal bits 08/20C, status ALS
Phy-B state is active, neighbor is A, cmt signal bits 20C/08, status ILS
CFM is thru A, token rotation 5000 usec, ring operational 0:01:42
Upstream neighbor 0800.2008.C52E, downstream neighbor 0800.2008.C52E

The show interfaces fddi example shows that Physical A (Phy-A) completed CMT with its neighbor. The state is active, and the display indicates a Physical B-type neighbor.

The sample output indicates CMT signal bits 08/20C for Phy-A. The transmit signal bits are 08. Looking at the pulse code modulation (PCM) state machine, 08 indicates that the port type is A, that the port compatibility is set, and that the LCT duration requested is short. The receive signal bits are 20C, that indicate that the neighbor type is B, that port compatibility is set, that there is a MAC on the port output, and so on.

The neighbor is determined from the received signal bits, as follows:

Bit Positions	9 8 7 6 5 4 3 2 1 0
Value Received	1 0 0 0 0 0 1 1 0 0

Interpreting the bits in the diagram above, the received value equals 0x20C. Bit positions 1 and 2 (0 1) indicate a Physical B-type connection.

The transition states displayed indicate that the CMT process is running and actively trying to establish a connection to the remote physical connection. The CMT process requires state transition with different signals being transmitted and received before moving on to the state ahead as indicated in the PCM state machine. The 10 bits of CMT information are transmitted and received in the Signal State. The NEXT state is used to separate the signaling performed in the Signal State. Therefore, in the preceding sample output, the NEXT state was entered 11 times.

Note	The display line showing transition states is not generated if the FDDI interface has been shut down, or if the cmt disconnect command has been issued, or if the fddi if-cmt command has been issued. (The fddi if-cmt command applies to the Cisco 7500 series routers only.)

The CFM state is through A in the sample output, which means the Phy-A of this interface has successfully completed CMT with the Phy-B of the neighbor and Phy-B of this interface has successfully completed CMT with the Phy-A of the neighbor.

The display (or nondisplay) of the upstream and downstream neighbor does not affect the ability to route data. Because the upstream neighbor is also its downstream neighbor in the sample, there are only two stations in the ring: the network server and the router at address 0800.2008.C52E.

FDDI Configuration Task List

To configure a FDDI interface, perform the tasks in the following sections. Each task in the list is identified as either required or optional.

• Specifying a FDDI Interface
• Enabling FDDI Bridging Encapsulation
• Enabling Full-Duplex Mode on the FDDI Interface
• Setting the Token Rotation Time
• Setting the Transmission Valid Timer
• Controlling the Transmission Timer
• Modifying the C-Min Timer
• Modifying the TB-Min Timer
• Modifying the FDDI Timeout Timer
• Controlling SMT Frame Processing
• Enabling Duplicate Address Checking
• Setting the Bit Control
• Controlling the CMT Microcode
• Starting and Stopping FDDI
• Setting FDDI Frames per Token Limit
• Controlling the FDDI SMT Message Queue Size
• Preallocating Buffers for Bursty FDDI Traffic

Specifying a FDDI Interface

To specify a FDDI interface and enter interface configuration mode, use one of the following commands in global configuration mode.

Command or Action	Purpose
Router(config)# interface fddi number	Enters interface configuration.
Router(config)# interface fddi slot / port	Enters interface configuration for the Cisco 7200 or Cisco 7500 series routers.

Enabling FDDI Bridging Encapsulation

By default, Cisco FDDI uses the SNAP encapsulation format defined in RFC 1042. It is not necessary to define an encapsulation method for this interface when using the FIP.

FIP fully supports transparent and translational bridging for the following configurations:

• FDDI-to-FDDI

• FDDI-to-Ethernet

• FDDI-to-Token Ring

Enabling FDDI bridging encapsulation places the FIP into encapsulation mode when doing bridging. In transparent mode, the FIP interoperates with earlier versions of encapsulating interfaces when performing bridging functions on the same ring. When using the FIP, you can specify the encapsulation method by using the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi encapsulate	Specifies the encapsulation method for the FIP.

When you are doing translational bridging, use routing for routable protocols and use translational bridging for the rest, such as local-area transport (LAT).

Note

Bridging between dissimilar media presents several problems that can prevent communications. These problems include bit-order translation (using MAC addresses as data), maximum transfer unit (MTU) differences, frame status differences, and multicast address usage. Some or all of these problems might be present in a multimedia-bridged LAN and might prevent communication. These problems are most prevalent in networks that bridge between Token Ring and Ethernet networks or between Token Ring and FDDI because of the different ways that Token Ring is implemented by the end nodes.

We are currently aware of problems with the following protocols when bridged between Token Ring and other media: AppleTalk, DECnet, IP, Novell IPX, Phase IV, VINES, and XNS. Further, the following protocols might have problems when bridged between FDDI and other media: Novell IPX and XNS. We recommend that these protocols be routed whenever possible.

Enabling Full-Duplex Mode on the FDDI Interface

To enable full-duplex mode on the PA-F/FD-SM and PA-F/FD-MM port adapters, use one of the following commands in interface configuration mode.

Command or Action	Purpose
Router(config-if)# full-duplex or Router(config-if)# no half-duplex	Enables full-duplex on the FDDI interface of the PA-F/FD-SM and PA-F/FD-MM port adapter.

Setting the Token Rotation Time

You can set the FDDI token rotation time to control ring scheduling during normal operation and to detect and recover from serious ring error situations. To do so, use the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi token-rotation-time microseconds	Sets the FDDI token rotation time.

The FDDI standard restricts the allowed time to greater than 4000 microseconds and less than 165,000 microseconds. As defined in the X3T9.5 specification, the value remaining in the token rotation timer (TRT) is loaded into the token holding timer (THT). Combining the values of these two timers provides the means to determine the amount of bandwidth available for subsequent transmissions.

Setting the Transmission Valid Timer

You can set the transmission timer to recover from a transient ring error by using the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi valid-transmission-time microseconds	Sets the FDDI valid transmission timer.

Controlling the Transmission Timer

You can set the FDDI control transmission timer to control the FDDI TL-Min time, which is the minimum time to transmit a Physical Sublayer or PHY line state before advancing to the next Physical Connection Management or PCM state as defined by the X3T9.5 specification. To do so, use the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi tl-min-time microseconds	Sets the FDDI control transmission timer.

Modifying the C-Min Timer

You can modify the C-Min timer on the PCM from its default value of 1600 microseconds by using the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi c-min microseconds	Sets the C-Min timer on the PCM.

Modifying the TB-Min Timer

You can change the TB-Min timer in the PCM from its default value of 100 milliseconds. To do so, use the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi tb-min milliseconds	Sets TB-Min timer in the PCM.

Modifying the FDDI Timeout Timer

You can change the FDDI timeout timer in the PCM from its default value of 100 ms. To do so, use the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi t-out milliseconds	Sets the timeout timer in the PCM.

Controlling SMT Frame Processing

You can disable and enable SMT frame processing for diagnostic purposes. To do so, use one of the following commands in interface configuration mode.

Command or Action	Purpose
Router(config-if)# no fddi smt-frames	Disables SMT frame processing.
Router(config-if)# fddi smt-frames	Enables SMT frame processing.

Enabling Duplicate Address Checking

You can enable the duplicate address detection capability on the FDDI. If the FDDI finds a duplicate address, it displays an error message and shuts down the interface. To enable duplicate address checking, use the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi duplicate-address-check	Enables duplicate address checking capability.

Setting the Bit Control

You can set the FDDI bit control to control the information transmitted during the Connection Management (CMT) signaling phase. To do so, use the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi cmt-signal-bits signal-bits [phy-a | phy-b]	Sets the FDDI bit control.

Controlling the CMT Microcode

You can control whether the CMT onboard functions are on or off. The FIP provides CMT functions in microcode. These functions are separate from those provided on the processor card and are accessed through EXEC commands.

The default is for the FIP CMT functions to be on. A typical reason to disable these functions is when you work with new FDDI equipment and have problems bringing up the ring. If you disable the CMT microcode, the following actions occur:

• The FIP CMT microcode is disabled.

• The main system code performs the CMT function while debugging output is generated.

To disable the CMT microcode, use the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# no fddi if-cmt	Disables the FCIT CMT functions.

Starting and Stopping FDDI

In normal operation, the FDDI interface is operational once the interface is connected and configured. You can start and stop the processes that perform the CMT function and allow the ring on one fiber to be stopped. To do so, use either of the following commands in EXEC mode.

Command or Action	Purpose
Router# cmt connect [interface-name [phy-a | phy-b]]	Starts CMT processes on a FDDI ring.
Router# cmt disconnect [interface-name [phy-a | phy-b]]	Stops CMT processes on a FDDI ring.

Do not use either of the preceding commands during normal operation of FDDI; they are used during interoperability tests.

Setting FDDI Frames per Token Limit

The FDDI interface is able to transmit multiple frames per token on a Cisco 4000, a Cisco 4500, and a Cisco 4700 series router, instead of transmitting only a single frame at a time. You can specify the maximum number of frames to be transmitted with each token capture. This significantly improves your throughput when you have heavy or very bursty traffic.

To configure the FDDI interface to transmit a maximum number of frames per token capture, use the following commands beginning in privileged EXEC mode.

SUMMARY STEPS

1.    Router# configure terminal

2.    Router(config)# interface fddi number

3.    Router(config-if)# fddi number

4.    Router(config-if)# fddi frames-per-token number

5.    Router(config-if)# fddi frames-per-token number

DETAILED STEPS

	Command or Action	Purpose
Step 1	Router# configure terminal	Enters global configuration mode.
Step 2	Router(config)# interface fddi number	Enters interface configuration mode.
Step 3	Router(config-if)# fddi number	Shows fddi command options.
Step 4	Router(config-if)# fddi frames-per-token number	Shows fddi frames-per-token command options.
Step 5	Router(config-if)# fddi frames-per-token number	Specifies the maximum number of frames to be transmitted per token capture.

Controlling the FDDI SMT Message Queue Size

You can set the maximum number of unprocessed FDDI Station Management (SMT) frames that will be held for processing. Setting this number is useful if the router that you are configuring gets bursts of messages that arrive faster than the router can process. To set the number of frames, use the following command in global configuration mode.

Command or Action	Purpose
Router(config)# smt-queue-threshold number	Sets SMT message queue size.

Preallocating Buffers for Bursty FDDI Traffic

The FCI card preallocates three buffers to handle bursty FDDI traffic (for example, Network File System (NFS) bursty traffic). You can change the number of preallocated buffers use the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi burst-count	Preallocates buffers to handle bursty FDDI traffic.

Router(config-hub)# no auto-polarity 

Router(config-hub)# auto-polarity

Router(config-hub)# no link-test 

Router(config-hub)# link-test

Router(config-hub)# source-address [mac-address]

Configuring a Token Ring Interface

Cisco supports various Token Ring interfaces. Refer to the Cisco Product Catalog for information about platform and hardware compatibility.

The Token Ring interface supports both routing (Layer 3 switching) and source-route bridging (Layer 2 switching) on a per-protocol basis. For example, IP traffic could be routed, while SNA traffic is bridged. Routing features enhance source-route bridges

The Token Ring MIB variables support the specification in RFC 1231, IEEE 802.5 Token Ring MIB . The mandatory Interface Table and Statistics Table are implemented, but the optional Timer Table of the Token Ring MIB is not. The Token Ring MIB has been implemented for the Token Ring Interface Processor (TRIP).

Use the show interfaces, show controllers token, and show controllers cbusEXEC commands to display the Token Ring numbers. These commands provide a report for each ring that Cisco IOS software supports.

Note

If the system receives an indication of a cabling problem from a Token Ring interface, it puts that interface into a reset state and does not attempt to restart it. It functions this way because periodic attempts to restart the Token Ring interface drastically affect the stability of routing tables. Once you have plugged the cable into the MAU (media attachment unit) again, restart the interface by using the clear interface tokenring numbercommand, where the number argument is the interface number.

By default, the Token Ring interface uses the SNAP encapsulation format defined in RFC 1042. It is not necessary to define an encapsulation method for this interface.

• Particle-Based Switching of Source-Route Bridge Packets on Cisco 7200 Series Routers
• Dedicated Token Ring Port Adapter
• Token Ring Interface Configuration Task List

Particle-Based Switching of Source-Route Bridge Packets on Cisco 7200 Series Routers

Particle-based switching is supported for SRB packets (over FDDI and Token Ring) by default.

Particle-based switching adds scatter-gather capability to SRB to improve performance. Particles represent a communications data packet as a collection of noncontiguous buffers. The traditional Cisco IOS packet has a packet type control structure and a single contiguous data buffer. A particle packet has the same packet type control structure, but it also maintains a queue of particle type structures, each of which manages its own block.

The scatter-gather architecture used by particle-based switching provides the following advantages:

• Allows drivers to use memory more efficiently (especially when using media that has a large maximum transmission unit [MTU]). For example, Token Ring buffers could be 512 bytes rather than 16 KB.

• Allows concurrent use of the same region of memory. For example, on IP multicast a single packet is received and sent out on multiple interfaces simultaneously.

• Allows insertion or deletion of memory at any location in a packet (not just at the beginning or end).

For information about configuring SRB over FDDI, refer to the "Configuring Source-Route Bridging" chapter of the CiscoIOS Bridging and IBM Networking Configuration Guide .

Dedicated Token Ring Port Adapter

The Dedicated Token Ring port adapter (PA-4R-DTR) is available on Cisco 7500 series routers, Cisco 7200 series routers, and Cisco 7000 series routers with the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI).

The PA-4R-DTR provides up to four IBM Token Ring or IEEE 802.5 Token Ring interfaces. Each Token Ring interface can be set for 4-Mbps or 16-Mbps half-duplex or full-duplex operation and can operate as a standard Token Ring station or as a concentrator port. The default for all interfaces is Token Ring station mode with half-duplex 16-Mbps operation. The PA-4R-DTR connects over Type 1 lobe or Type 3 lobe cables, with each interface providing an RJ-45 receptacle.

Token Ring Interface Configuration Task List

To configure a Token Ring interface, perform the tasks in the following sections. Each task is identified as either required or optional.

• Specifying a Token Ring Interface
• Enabling Early Token Release
• Configuring PCbus Token Ring Interface Management
• Enabling a Token Ring Concentrator Port
• Monitoring and Maintaining the Port

Specifying a Token Ring Interface

To specify a Token Ring interface and enter interface configuration mode, use one of the following commands in global configuration mode.

Command	Purpose
Router(config)# interface tokenring number	Enters interface configuration mode.
Router(config)# interface tokenring slot / port	Enters interface configuration mode for the Cisco 7200 or Cisco 7500 series routers.
Router(config)# interface tokenring slot / port-adapter / port	Enters interface configuration mode for the Cisco 7500 series routers.

Enabling Early Token Release

Cisco Token Ring interfaces support early token release, a method whereby the interface releases the token back onto the ring immediately after transmitting rather than waiting for the frame to return. This feature can help to increase the total bandwidth of the Token Ring. To configure the interface for early token release, use the following command in interface configuration mode.

Command	Purpose
Router(config-if)# early-token-release	Enables early token release.

Configuring PCbus Token Ring Interface Management

The Token Ring interface on the AccessPro PC card can be managed by a remote LAN manager over the PCbus interface. Currently, the LanOptics Hub Networking Management software running on an IBM-compatible PC is supported.

To enable LanOptics Hub Networking Management of a PCbus Token Ring interface, use the following command in interface configuration mode.

Command	Purpose
Router(config-if)# local-lnm	Enables PCbus LAN management.

Enabling a Token Ring Concentrator Port

To enable an interface to operate as a concentrator port, use the following command in interface configuration mode.

Command	Purpose
Router(config-if)# port	Specifies concentrator port operation.

Monitoring and Maintaining the Port

To monitor the Token Ring concentrator port, use one or more of the following commands in EXEC mode.

Command	Purpose
Router# show controllers token	Displays internal state information about the Token Ring interfaces in the system.
Router# show interfaces token	Displays high-level statistics for a particular interface.

LAN Interface Configuration Examples

This section provides the following examples to illustrate configuration tasks described in this chapter.

• Ethernet Encapsulation Enablement Example
• Full-Duplex Enablement Operation Example
• PA-12E 2FE Port Configuration Examples
• PA-VG100 Port Adapter Configuration Example
• Cisco 7200-I O-GE+E and Cisco 7200-I O-2FE E Configuration Examples
• Fast EtherChannel Configuration Examples
• FDDI Frames Configuration Example
• Hub Configuration Examples

Ethernet Encapsulation Enablement Example

These commands enable standard Ethernet Version 2.0 encapsulation on the Ethernet interface processor in slot 4 on port 2 of a Cisco 7500 series router:

interface ethernet 4/2
 encapsulation arpa

Full-Duplex Enablement Operation Example

The following example assigns an IP address and subnet mask, specifies an MII Ethernet connector, and enables full-duplex mode on Fast Ethernet interface port 0 in slot 1 port adapter 0:

Router(config)# interface fastethernet 1/0/0
Router(config-if)# 
ip address 10.1.1.10 255.255.255.0 
Router(config-if)# 
full-duplex
Router(config-if)# 
media-type mii
Router(config-if)# exit
Router(config)# exit

PA-12E 2FE Port Configuration Examples

The following is an example of a configuration for the PA-12E/2FE port adapter interface. Bridge groups 10, 20, and 30 use IEEE Spanning Tree Protocol. The first four interfaces of a PA-12E/2EF port adapter in port adapter slot 3 use bridge groups 10 and 20. Each interface is assigned to a bridge group, and the shutdown state is set to up. The PA-12E/2FE port adapter supports store-and-forward or cut-through switching technology between interfaces within the same bridge group; store-and-forward is the default. In the following example, the cut-throughcommand is used to configure each interface for cut-through switching of received and transmitted data:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL-Z.
Router(config)# 
bridge 10 protocol ieee
Router(config)# 
bridge 20 protocol ieee
Router(config)# 
bridge 30 protocol ieee
Router(config)#
 
interface fastethernet 3/0
Router(config-if)#
 
bridge-group 10
Router(config-if)#
 
cut-through
Router(config-if)#
 no shutdown
Router(config-if)# 
exit
Router(config)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface Fast Ethernet3/0, changed
state to up
%LINK-3-UPDOWN: Interface Fast Ethernet3/0, changed state to up
Router(config)#
 interface fastethernet 3/1
Router(config-if)#
 bridge-group 10
Router(config-if)#
 
cut-through
Router(config-if)#
 
no shutdown
Router(config-if)# 
exit
Router(config)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface Fast Ethernet3/1, changed
state to up
%LINK-3-UPDOWN: Interface Fast Ethernet3/1, changed state to up
Router(config)#
 interface ethernet 3/2
Router(config-if)#
 bridge-group 20
Router(config-if)#
 cut-through
Router(config-if)#
 
no shutdown
Router(config-if)# 
exit
Router(config)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet3/2, changed state to up
%LINK-3-UPDOWN: Interface Ethernet3/2, changed state to up
Router(config)#
 interface ethernet 3/3
Router(config-if)#
 bridge-group 20
Router(config-if)#
 cut-through
Router(config-if)#
 
no shutdown
Router(config-if)# 
exit
Router(config)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet3/3, changed state to up
%LINK-3-UPDOWN: Interface Ethernet3/3, changed state to up

The following example shows integrated routing and bridging enabled on the bridge groups. Bridge group 10 is assigned an IP address and subnet mask, and the shutdown state is changed to up. Bridge group 10 is configured to route IP.

Router(config)# 
bridge irb
Router(config)# 
interface bvi 10
Router(config-if)# 
ip address 10.1.15.1 255.255.255.0
Router(config-if)# 
no shutdown
Router(config-if)# 
exit
Router(config)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface BVI10, changed state to up
Router(config)# 
bridge 10 route ip
Router(config)# exit
Router#

PA-VG100 Port Adapter Configuration Example

The following is an example of a basic configuration for the PA-VG100 port adapter interface in slot 1 on a Cisco 7500 series router. In this example, IP routing is enabled on the router, so an IP address and subnet mask are assigned to the interface.

configure terminal
interface vg-anylan 1/0/0 
 ip address 10.1.1.10 255.255.255.0 
 no shutdown 
 exit
exit

Cisco 7200-I O-GE+E and Cisco 7200-I O-2FE E Configuration Examples

This section provides the following configuration examples:

• Configuring the Gigabit Ethernet Interface on the Cisco 7200-I O-GE+E
• Configuring Autonegotiation on the Cisco 7200-I O-2FE E

Configuring the Gigabit Ethernet Interface on the Cisco 7200-I O-GE+E

The following example configures the Gigabit Ethernet interface on the Cisco 7200-I/O-GE+E. The following commands are configured on slot 0, port 0.

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# interface gigabitethernet 0/0
Router(config-if)# ip address 10.1.1.10 255.255.255.252
Router(config-if)# negotiation auto
Router(config-if)# end

Configuring Autonegotiation on the Cisco 7200-I O-2FE E

The following example configures the Fast Ethernet interface on the Cisco 7200-I/O-2FE/E for fully enabled autonegotiation:

Router# 
configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# interface fastethernet 0/0
Router(config-if)# 
duplex auto
Router(config-if)# speed auto

Fast EtherChannel Configuration Examples

The figure below shows four point-to-point Fast Ethernet interfaces that are aggregated into a single Fast EtherChannel interface.

The configuration file that illustrates this topology follows.

The following is an example of how to create a Fast EtherChannel (port-channel interface) with four Fast Ethernet interfaces. In this example, ISL is enabled on the Fast EtherChannel, and an IP address is assigned to the subinterface.

Router# configure terminal
Router(config)# interface port-channel 1 
Router(config-if)# no shutdown 
Router(config-if)# exit
Router(config)# interface port-channel 1.1
Router(config-if)# ip address 10.1.1.10 255.255.255.0 
Router(config-if)# encapsulation isl 100
Router(config-if)# exit
Router(config)# interface fastethernet 0/0/0
Router(config-if)# no ip address
Router(config-if)# channel-group 1
Fast Ethernet 0/0 added as member-1 to port-channel1.
Router(config-if)# exit
Router(config)# interface fastethernet 0/1/0
Router(config-if)# no ip address
Router(config-if)# channel-group 1
Fast Ethernet 0/1 added as member-2 to port-channel1.
Router(config-if)# exit
Router(config)# interface fastethernet 1/0/0
Router(config-if)# no ip address
Router(config-if)# channel-group 1
Fast Ethernet 1/0 added as member-3 to port-channel1.
Router(config-if)# exit
Router(config)# interface fastethernet 1/1/0
Router(config-if)# no ip address
Router(config-if)# channel-group 1
Fast Ethernet 1/1 added as member-4 to port-channel1.
Router(config-if)# exit
Router(config)# exit
Router#

The following is a partial example of a configuration file. The MAC address is automatically added to the Fast Ethernet interface when the interfaces are added to the Fast EtherChannel.

Note	If you do not assign a static MAC address on the port-channel interface, the Cisco IOS software automatically assigns a MAC address. If you assign a static MAC address and then later remove it, the Cisco IOS software automatically assigns a MAC address.

interface Port-channel1
 ip address 10.1.1.10 255.255.255.0
!
interface Port-channel1.1
 encapsulation isl 100
!
interface Fast Ethernet0/0/0
 mac-address 00e0.1476.7600
 no ip address
 channel-group 1
!
interface Fast Ethernet0/1/0
 mac-address 00e0.1476.7600
 no ip address
 channel-group 1
!
interface Fast Ethernet1/0/0
 mac-address 00e0.1476.7600
 no ip address
 channel-group 1
!
interface Fast Ethernet1/1/0
 mac-address 00e0.1476.7600
 no ip address
 channel-group 1

FDDI Frames Configuration Example

The following example shows how to configure the FDDI interface to transmit four frames per token capture:

! Enter global configuration mode.
  4700# 
configure terminal
! Enter interface configuration mode.
  4700(config)#
 interface fddi 0
! Show the fddi command options.
  4700(config-if)# 
fddi ?
  encapsulate              Enable FDDI Encapsulation bridging
  frames-per-token         Maximum frames to transmit per service opportunity
  tl-min-time              Line state transmission time
  token-rotation-time      Set the token rotation timer
  valid-transmission-time  Set transmission valid timer
! Show fddi frames-per-token command options.
  4700(config-if)# 
fddi frames-per-token ?
  <1-10> Number of frames per token, default = 3
! Specify 4 as the maximum number of frames to be transmitted per token.
  4700(config-if)# 
fddi frames-per-token 4

Hub Configuration Examples

This section provides the following hub configuration examples:

• Hub Port Startup Examples
• Source Address for an Ethernet Hub Port Configuration Examples
• Hub Port Shutdown Examples
• SNMP Illegal Address Trap Enablement for Hub Port Example

Hub Port Startup Examples

The following example configures port 1 on hub 0 of Ethernet interface 0:

hub ethernet 0 1
 no shutdown

The following example configures ports 1 through 8 on hub 0 of Ethernet interface 0:

hub ethernet 0 1 8
 no shutdown

Source Address for an Ethernet Hub Port Configuration Examples

The following example configures the hub to allow only packets from MAC address 1111.2222.3333 on port 2 of hub 0:

hub ethernet 0 2
 source-address 1111.2222.3333

The following example configures the hub to remember the first MAC address received on port 2 and allow only packets from that learned MAC address:

hub ethernet 0 2
 source-address

Hub Port Shutdown Examples

The following example shuts down ports 3 through 5 on hub 0:

hub ethernet 0 3 5
 shutdown

The following example shuts down port 3 on hub 0:

hub ethernet 0 3
 shutdown

SNMP Illegal Address Trap Enablement for Hub Port Example

The following example specifies the gateway IP address and enables an SNMP trap to be issued to the host 172.16.40.51 when a MAC address violation is detected on hub ports 2, 3, or 4. It specifies that Ethernet interface 0 is the source for all traps on the router. The community string is defined as the string public and the read/write parameter is set.

ip route 0.0.0.0 0.0.0.0 172.22.10.1
snmp-server community public rw
snmp-server trap-source ethernet 0
snmp-server host 172.16.40.51 public
hub ethernet 0 2 4
snmp trap illegal-address

Contents

• Configuring LAN Interfaces
• Finding Feature Information
• Configuring Ethernet Fast Ethernet or Gigabit Ethernet Interfaces
• Ethernet Fast Ethernet and Gigabit Ethernet Interface Configuration Task List
• Specifying an Ethernet Fast Ethernet or Gigabit Ethernet Interface
• Specifying an Ethernet Encapsulation Method
• Specifying Full-Duplex Operation
• Specifying the Media and Connector Type
• Extending the 10BASE-T Capability
• Configuring Fast Ethernet 100BASE-T
• Configuring PA-12E 2FE Port Adapters
• Configuring the PA-12E 2FE Port Adapter
• Configuring the PA-12E 2FE Port Adapter
• Monitoring and Maintaining the PA-12E 2FE Port Adapter
• Configuring Bridge Groups Using the 12E 2FE VLAN Configuration WebTool
• Configuring the 100VG-AnyLAN Port Adapter
• Configuring the Cisco 7200-I O-GE+E and Cisco 7200-I O-2FE E Input Output Controllers
• Cisco 7200-I O-GE+E and Cisco 7200-I O-2FE E Configuration Task List
• Configuring the Interface Transmission Mode
• Configuring Interface Speed
• Configuring the Ethernet Fast Ethernet and Gigabit Ethernet Interfaces
• Verifying the Configuration
• Monitoring and Maintaining the Cisco 7200-I O GE+E and Cisco 7200-I O-2FE E
• Configuring an FDDI Interface
• Source-Route Bridging over FDDI on Cisco 4000-M Cisco 4500-M and Cisco 4700-M Routers
• Particle-Based Switching of Source-Route Bridge Packets on Cisco 7200 Series Routers
• Using Connection Management Information
• FDDI Configuration Task List
• Specifying a FDDI Interface
• Enabling FDDI Bridging Encapsulation
• Enabling Full-Duplex Mode on the FDDI Interface
• Setting the Token Rotation Time
• Setting the Transmission Valid Timer
• Controlling the Transmission Timer
• Modifying the C-Min Timer
• Modifying the TB-Min Timer
• Modifying the FDDI Timeout Timer
• Controlling SMT Frame Processing
• Enabling Duplicate Address Checking
• Setting the Bit Control
• Controlling the CMT Microcode
• Starting and Stopping FDDI
• Setting FDDI Frames per Token Limit
• Controlling the FDDI SMT Message Queue Size
• Preallocating Buffers for Bursty FDDI Traffic
• Configuring a Hub Interface
• Enabling a Hub Port
• Disabling or Enabling Automatic Receiver Polarity Reversal
• Disabling or Enabling the Link Test Function
• Enabling Source Address Control
• Enabling SNMP Illegal Address Trap
• Configuring a Token Ring Interface
• Particle-Based Switching of Source-Route Bridge Packets on Cisco 7200 Series Routers
• Dedicated Token Ring Port Adapter
• Token Ring Interface Configuration Task List
• Specifying a Token Ring Interface
• Enabling Early Token Release
• Configuring PCbus Token Ring Interface Management
• Enabling a Token Ring Concentrator Port
• Monitoring and Maintaining the Port
• LAN Interface Configuration Examples
• Ethernet Encapsulation Enablement Example
• Full-Duplex Enablement Operation Example
• PA-12E 2FE Port Configuration Examples
• PA-VG100 Port Adapter Configuration Example
• Cisco 7200-I O-GE+E and Cisco 7200-I O-2FE E Configuration Examples
• Configuring the Gigabit Ethernet Interface on the Cisco 7200-I O-GE+E
• Configuring Autonegotiation on the Cisco 7200-I O-2FE E
• Fast EtherChannel Configuration Examples
• FDDI Frames Configuration Example
• Hub Configuration Examples
• Hub Port Startup Examples
• Source Address for an Ethernet Hub Port Configuration Examples
• Hub Port Shutdown Examples
• SNMP Illegal Address Trap Enablement for Hub Port Example

Configuring LAN Interfaces

---

Use the information in this chapter to configure LAN interfaces supported on Cisco routers and access servers.

To identify the hardware platform or software image information associated with a feature, use Cisco Feature Navigator on Cisco.com to search for information about the feature.

This chapter describes the processes for configuring LAN interfaces and includes the following sections:

For examples of configuration tasks, see the LAN Interface Configuration Examples.

For hardware technical descriptions and information about installing interfaces, refer to the hardware installation and configuration publication for your product. For a complete description of the LAN interface commands used in this chapter, refer to the Cisco IOS Interface and Hardware Component Command Reference . To locate documentation of other commands that appear in this chapter, use the master commands list or search online.

• Finding Feature Information
• Configuring Ethernet Fast Ethernet or Gigabit Ethernet Interfaces
• Configuring the Cisco 7200-I O-GE+E and Cisco 7200-I O-2FE E Input Output Controllers
• Configuring an FDDI Interface
• Configuring a Hub Interface
• Configuring a Token Ring Interface
• LAN Interface Configuration Examples

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

Configuring Ethernet Fast Ethernet or Gigabit Ethernet Interfaces

Cisco supports 10-Mbps Ethernet, 100-Mbps Fast Ethernet, and 1000-Mbps Gigabit Ethernet. Support for the 10-Mbps, 100-Mbps, and 1000-Mbps Ethernet interface is supplied on various Ethernet network interface cards or systems.

Fast Ethernet NP-1FE Module Benefits

• VLAN routing--VLAN support enables network managers to group users logically rather than by physical location. The high performance of the underlying Cisco 4700, combined with the feature-rich NP-1FE, makes it an ideal combination for a low-density, higher-performance application such as inter-VLAN routing.

• High-speed interconnections--The Fast Ethernet interface enables network managers to implement Fast-Ethernet routing solutions for optimal cost and performance across a wide range of applications, including campus or enterprise backbones and data centers. It is also a low-cost way to provide Fast-Ethernet access to traditional low-speed WAN services.

• Local area network aggregation--The Cisco 4500 or the Cisco 4700 series routers can support as many as 12 Ethernet, 4 Token Ring, or 1 FDDI segment. ISDN interfaces are also supported.

With the Catalyst 3000 or Catalyst 5000 system, the Fast Ethernet processor can be used to aggregate up to twelve 10-Mbps LANs and give them high-speed access to such Layer 3 routing services as providing firewalls and maintaining access lists.

Cisco 7200 Series Routers with Fast Ethernet and Gigabit Ethernet

Cisco 7200 series routers support an I/O controller with an RJ-45 interface for Fast Ethernet support and an I/O controller with both RJ-45 and GBIC interfaces for Gigabit Ethernet support.

The Cisco 7200-I/O-GE+E is an Input/Output controller that provides one Gigabit Ethernet and one Ethernet port. It is equipped with a GBIC receptacle for 1000 Mbps operation and an RJ-45 receptacle for 10-Mbps operation.

The Cisco 7200-I/O-2FE/E is an I/O controller that provides two autosensing Fast Ethernet ports and is equipped with two RJ-45 receptacles for 10/100 Mbps operation.

You can configure the Fast Ethernet port for use at 100-Mbps full-duplex or half-duplex operation (half duplex is the default). The Fast Ethernet port is equipped with either a single MII receptacle or an MII receptacle and an RJ-45 receptacle. To support this new feature, the media-type interface command has been modified. The media-type command now supports two options:

• 100BASE-X --Specifies an RJ-45 100BASE-X physical connection.

• mii --Specifies a media-independent interface.

The Gigabit Ethernet interface on the Cisco 7200-I/O-GE+E operates at full duplex and cannot be configured for half-duplex mode.

Second-generation Fast Ethernet Interface Processors (FEIP2-DSW-2TX and FEIP2-DSW-2FX) are available on Cisco 7500 series routers and on Cisco 7000 series routers with the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI). The FEIP2-DSW is a dual-port, fixed-configuration interface processor that provides two 100-Mbps Fast Ethernet (FE) interfaces. Each interface on the FEIP2-DSW supports both half-duplex and full-duplex.

Refer to the Cisco Product Catalog for specific platform and hardware compatibility information.

Use the show interfaces, show controllers mci, and show controllers cbusEXEC commands to display the Ethernet port numbers. These commands provide a report for each interface supported by the router or access server.

Use the show interfaces fastethernetcommand to display interface statistics, and use the show controllers fastethernet to display information about the Fast Ethernet controller chip. The output shows statistics, including information about initialization block information, transmit ring, receive ring, and errors.

Use the show interfaces gigabitethernetcommand to display interface statistics, and use the show controllers gigabitethernet to display the information about the Gigabit Ethernet controller chip. The output shows statistics, including information about initialization block information, transmit ring, receive ring, and errors.

• Ethernet Fast Ethernet and Gigabit Ethernet Interface Configuration Task List

Ethernet Fast Ethernet and Gigabit Ethernet Interface Configuration Task List

To configure features on an Ethernet, Fast Ethernet, or Gigabit Ethernet interface, perform the tasks in the following sections:

• Specifying an Ethernet Fast Ethernet or Gigabit Ethernet Interface
• Specifying an Ethernet Encapsulation Method
• Specifying Full-Duplex Operation
• Specifying the Media and Connector Type
• Extending the 10BASE-T Capability
• Configuring Fast Ethernet 100BASE-T
• Configuring PA-12E 2FE Port Adapters
• Configuring the 100VG-AnyLAN Port Adapter

Specifying an Ethernet Fast Ethernet or Gigabit Ethernet Interface

To specify an Ethernet interface and enter interface configuration mode, use one of the following commands in global configuration mode.

Command or Action	Purpose
Router(config)# interface ethernet number	Enters interface configuration mode.
Router(config)# interface ethernet slot / port	Enters interface configuration mode for the Cisco 7200 and Cisco 7500 series routers.
Router(config)# interface ethernet slot / port-adapter / port	Enters interface configuration mode for Cisco 7500 series routers.
Router(config)# interface fastethernet number	Enters interface configuration mode for the Cisco 4000 series with a Fast Ethernet NIM installed.
Router(config)# interface fastethernet slot / port	Specifies a Fast Ethernet interface and enters interface configuration mode on the Cisco 7200 series routers.
Router(config)# interface fastethernet slot / port-adapter / port	Specifies a Fast Ethernet interface and enters interface configuration mode on the Cisco 7500 series routers.
Router(config)# interface gigabitethernet slot / port	Specifies a Gigabit Ethernet interface and enters interface configuration mode on the Cisco 7200 series routers.

To display the Fast Ethernet slots and ports, use the show interfaces fastethernetcommand. The Fast Ethernet network interface module (NIM) and the Fast Ethernet Interface Processor (FEIP) default to half-duplex mode.

Specifying an Ethernet Encapsulation Method

Currently, there are three common Ethernet encapsulation methods:

• The standard Advanced Research Projects Agency (ARPA) Ethernet Version 2.0 encapsulation, which uses a 16-bit protocol type code (the default encapsulation method).

• Service access point (SAP) IEEE 802.3 encapsulation, in which the type code becomes the frame length for the IEEE 802.2 LLC encapsulation (destination and source Service Access Points, and a control byte).

• The SNAP method, as specified in RFC 1042, >Standard for the Transmission of IP Datagrams Over IEEE 802 Networks , which allows Ethernet protocols to run on IEEE 802.2 media.

The encapsulation method that you use depends upon the routing protocol that you are using, the type of Ethernet media connected to the router or access server, and the routing or bridging application that you configure.

To establish Ethernet encapsulation of IP packets, use one of the following commands in interface configuration mode.

Command or Action	Purpose
Router(config-if)# encapsulation arpa	Selects ARPA Ethernet encapsulation.
Router(config-if)# encapsulation sap	Selects SAP Ethernet encapsulation.
Router(config-if)# encapsulation snap	Selects SNAP Ethernet encapsulation.

For an example of selecting Ethernet encapsulation for IP, see the Ethernet Encapsulation Enablement Example.

Specifying Full-Duplex Operation

The default is half-duplex mode on the FEIP2-DSW-2FX. To enable full-duplex mode on the FEIP2-DSW-2FX (for a maximum aggregate bandwidth of 200 Mbps), use either of the following commands in interface configuration mode.

Command or Action	Purpose
Router(config-if)# full-duplex or Router(config-if)# no half-duplex	Enables full-duplex on the Fast Ethernet interface of the FEIP2-DSW-2FX.

For an example of enabling full-duplex mode on Fast Ethernet, see the Full-Duplex Enablement Operation Example.

Caution

To prevent system problems, do not configure both FEIP2-DSW-2FX interfaces for full-duplex operation at the same time. The FEIP2-DSW-2TX supports half-duplex only and should not be configured for full-duplex.

Specifying the Media and Connector Type

You can specify that the Ethernet network interface module (NIM) on the Cisco 4000 series routers use either the default of an attachment unit interface (AUI) and a 15-pin connector, or 10BASE-T and an RJ-45 connector. To do so, use one of the following commands in interface configuration mode.

Command or Action	Purpose
Router(config-if)# media-type aui	Selects a 15-pin Ethernet connector.
Router(config-if)# media-type 10baset	Selects an RJ-45 Ethernet connector.

The default media connector type is an RJ-45 or SC (fiber-optic) connector. You can specify that the interface uses either an MII connector, or an RJ-45 or SC (fiber-optic) connector (this is the default). To do so, use one of the following commands in interface configuration mode.

Command or Action	Purpose
Router(config-if)# media-type mii	Selects an MII Ethernet connector.
Router(config-if)# media-type 100basex	Selects an RJ-45 Ethernet connector for the FEIP2-DSW-2TX or an SC connector for the FEIP2-DSW-2FX.

Note	When using the I/O controller that is equipped with an MII receptacle and an RJ-45 receptacle, only one receptacle can be configured for use at a time.

Extending the 10BASE-T Capability

On a Cisco 4000 series or Cisco 4500 series routers, you can extend the twisted-pair 10BASE-T capability beyond the standard 100 meters by reducing the squelch (signal cutoff time). This feature applies only to the LANCE controller 10BASE-T interfaces. LANCE is the AMD controller chip for the Cisco 4000 and Cisco 4500 Ethernet interface and does not apply to the Fast Ethernet interface.

To reduce squelch, use the first command in the following table in interface configuration mode. You can later restore the squelch by using the second command.

Command or Action	Purpose
Router(config-if)# squelch reduced	Reduces the squelch.
Router(config-if)# squelch normal	Returns squelch to normal.

Configuring Fast Ethernet 100BASE-T

You must configure the Fast Ethernet 100BASE-T interface on a Cisco AS5300 so that it can be recognized as a device on the Ethernet LAN. The Fast Ethernet interface supports 10- and 100-Mbps speeds with the 10BASE-T and 100BASE-T routers, hubs, and switches.

To configure the interface, use the following commands beginning in privileged EXEC mode.

SUMMARY STEPS

1.    Router# configure terminal

2.    Router(config)# interface fastethernet number

3.    Router(config-if)# ip address address subnet-mask

4.    Router(config-if)# speed {10 | 100 | auto}

5.    Router(config-if)# duplex {full | half | auto}

DETAILED STEPS

	Command or Action	Purpose
Step 1	Router# configure terminal	Enters global configuration mode.
Step 2	Router(config)# interface fastethernet number	Enters Fast Ethernet interface configuration mode.
Step 3	Router(config-if)# ip address address subnet-mask	Assigns an IP address and subnet mask to the interface.
Step 4	Router(config-if)# speed {10 | 100 | auto}	Assigns a speed to the interface. The default is 100 Mbps.1 For relationship between duplex and speed command options, see the table below.
Step 5	Router(config-if)# duplex {full | half | auto}	Sets up the duplex configuration on the Fast Ethernet interface. The default is half duplex.Configuring Fast Ethernet 100BASE-T For relationship between duplex and speed command options, see the table below.

¹ The auto option automatically negotiates the speed on the basis of the speed and the peer router, hub, or switch media.

What to Do Next

To use the autonegotiation capability (that is, to detect speed and duplex modes automatically), you must set both speed and duplex command to auto. Setting the speed command to auto negotiates speed only, and setting duplex command to auto negotiates duplex only. The table below describes the performance of the access server for different combinations of the duplex and speed command options. The specified duplex command option plus the specified speed command option produces the resulting system action.

Table 1 Relationship Between duplex and speed Command Options

duplex Command	speed Command	Resulting System Actions
Router(config-if)# duplex auto	speed auto	Autonegotiates both speed and duplex modes.
Router(config-if)# duplex auto	speed 10 or speed 100	Autonegotiates both speed and duplex modes.
Router(config-if)# duplex half or Router(config-if)# duplex full	speed auto	Autonegotiates both speed and duplex modes.
Router(config-if)# duplex half	speed 10	Forces 10 Mbps and half duplex.
Router(config-if)# duplex full	speed 10	Forces 10 Mbps and full duplex.
Router(config-if)# duplex half	speed 100	Forces 100 Mbps and half duplex.
Router(config-if)# duplex full	speed 100	Forces 100 Mbps and full duplex.

Configuring PA-12E 2FE Port Adapters

The PA-12E/2FE Ethernet switch port adapter provides Cisco 7200 series routers with up to twelve 10-Mbps and two 10/100-Mbps switched Ethernet (10BASE-T) and Fast Ethernet (100BASE-TX) interfaces for an aggregate bandwidth of 435 Mbps, full-duplex. The PA-12E/2FE port adapter supports the Ethernet, IEEE 802.3, and IEEE 802.3u specifications for 10-Mbps and 100-Mbps transmission over unshielded twisted pair (UTP) cables.

The PA-12E/2FE port adapter offloads Layer 2 switching from the host CPU by using store-and-forward or cut-through switching technology between interfaces within the same virtual LAN (VLAN) on the PA-12E/2FE port adapter. The PA-12E/2FE port adapter supports up to four VLANs (bridge groups).

Note	The PA-12E/2FE port adapter is a dual-width port adapter, which means it occupies two horizontally aligned port adapter slots when installed in a Cisco 7200 series router. (Single-width port adapters occupy individual port adapter slots in a Cisco 7200 series router.)

All interfaces on the PA-12E/2FE port adapter support autosensing and autonegotiation of the proper transmission mode (half-duplex or full-duplex) with an attached device. The first two PA-12E/2FE interfaces (port 0 and port 1) also support autosensing and autonegotiation of the proper connection speed (10 Mbps or 100 Mbps) with an attached device. If an attached device does not support autosensing and autonegotiation of the proper transmission mode, the PA-12E/2FE interfaces attached to the device automatically enter half-duplex mode. Use the show system:running-configcommand to determine if a PA-12E/2FE interface is autosensing and autonegotiating the proper transmission mode with an attached device. Use the full-duplexand the half-duplex commands to change the transmission mode of a PA-12E/2FE interface. After changing the transmission mode, use the show interfacescommand to verify the transmission mode of the interface.

Note

If you use the full-duplexand the half-duplex commands to change the transmission mode of the first two PA-12E/2FE interfaces (port 0 and port 1), the transmission speed of the two PA-12E/2FE interfaces automatically defaults to 100-Mbps. The first two PA-12E/2FE interfaces operate only at 10 Mbps when the interfaces are autosensing and autonegotiating the proper connection speed (10 Mbps or 100 Mbps) with an attached device.

To configure the PA-12E/2FE port adapter, perform the tasks in the following sections. Each task in the list is identified as either required or optional.

Note

If you plan to use a PA-12E/2FE interface to boot from a network (using TFTP), ensure that the interface is configured for a loop-free environment, that an IP address is configured for the interface’s bridge-group virtual interface, and that system boot image 11.2(10)P is installed on your router (use the show version command to view the system boot image of your router). Then, before booting from the network server, use the bridge-group bridge-group number spanning-disabled command to disable the Spanning Tree Protocol configured on the interface to keep the TFTP server from timing out and closing the session. For detailed information about booting from a network using TFTP, loading a system image from a network server, and configuring the Spanning Tree Protocol on your Cisco 7200 series router, refer to the PA-12E/2FE Ethernet Switch Port Adapter book that accompanies the hardware and to the Cisco IOS Bridging and IBM Networking Configuration Guide.

For information on other commands that can be used to configure a PA-12E/2FE port adapter, refer to the CiscoIOS Interface and Hardware Component Command Reference . For information on bridging, refer to the "Configuring Transparent Bridging" chapter in the CiscoIOS Bridging and IBM Networking Configuration Guide .

For PA-12E/2FE port adapter configuration examples, see the PA-12E 2FE Port Configuration Examples.

• Configuring the PA-12E 2FE Port Adapter
• Configuring the PA-12E 2FE Port Adapter
• Monitoring and Maintaining the PA-12E 2FE Port Adapter
• Configuring Bridge Groups Using the 12E 2FE VLAN Configuration WebTool

Configuring the PA-12E 2FE Port Adapter

This section provides instructions for a basic configuration. You might also need to enter other configuration commands depending on the requirements for your system configuration and the protocols that you plan to route on the interface. For complete descriptions of configuration commands and the configuration options available, refer to the other configuration guides and command references in the Cisco IOS documentation set.

To configure the interfaces on the PA-12E/2FE port adapter, use the following commands beginning in global configuration mode.

SUMMARY STEPS

1.    Router(config)# bridge bridge-group protocol ieee

2.    Router(config)# interface fastethernet slot / port

3.    Router(config-if)# bridge-group bridge-group

4.    Router(config-if)# cut-through [receive | transmit]

5.    Router(config-if)# full-duplex

6.    Router(config-if)# no shutdown

7.    Router(config-if)# exit

8.    Repeat Steps 1 through 7 for each interface.

9.    Router# copy system:running-config nvram:startup-config

DETAILED STEPS

	Command or Action	Purpose
Step 1	Router(config)# bridge bridge-group protocol ieee	Specifies the type of Spanning Tree Protocol. The PA-12E/2FE port adapter supports DEC and IEEE Spanning Tree Protocols; however, we recommend using the IEEE protocol when configuring bridge groups.
Step 2	Router(config)# interface fastethernet slot / port Example: (ports 0 and 1) Example: Router(config)# interface ethernet slot / port Example: (ports 2 through 13)	Enters interface configuration mode for the interface that you want to configure.
Step 3	Router(config-if)# bridge-group bridge-group	Assigns a bridge group to the interface.
Step 4	Router(config-if)# cut-through [receive | transmit]	(Optional) Configures the interface for cut-through switching technology. The default is store-and-forward (that is, no cut-through).
Step 5	Router(config-if)# full-duplex	(Optional) Configures the transmission mode for full-duplex, if an attached device does not support autosensing or autonegotiation. The default is half-duplex.
Step 6	Router(config-if)# no shutdown	Restarts the interface.
Step 7	Router(config-if)# exit	Returns to global configuration mode.
Step 8	Repeat Steps 1 through 7 for each interface.	--
Step 9	Router# copy system:running-config nvram:startup-config	Saves the new configuration to memory.

Configuring the PA-12E 2FE Port Adapter

To enable integrated routing and bridging on the bridge groups, use the following commands beginning in global configuration mode.

SUMMARY STEPS

1.    Router(config)# bridge irb

2.    Router(config)# interface bvi bridge-group

3.    Router(config-if)# ip address ip-address mask

4.    Router(config-if)# no shutdown

5.    Router(config-if)# exit

6.    Repeat Steps 1 through 5 for each bridge group.

7.    Router(config)# bridge bridge-group route protocol

8.    Router(config)# exit

9.    Router# copy system:running-config nvram:startup-config

DETAILED STEPS

	Command or Action	Purpose
Step 1	Router(config)# bridge irb	Enables integrated routing and bridging.
Step 2	Router(config)# interface bvi bridge-group	Enables a virtual interface on a bridge group.
Step 3	Router(config-if)# ip address ip-address mask	Assigns an IP address and subnet mask to the bridge-group virtual interface.
Step 4	Router(config-if)# no shutdown	Restarts the interface.
Step 5	Router(config-if)# exit	Returns to global configuration mode.
Step 6	Repeat Steps 1 through 5 for each bridge group.	--
Step 7	Router(config)# bridge bridge-group route protocol	Specifies the protocol for each bridge group.
Step 8	Router(config)# exit	Exits global configuration mode.
Step 9	Router# copy system:running-config nvram:startup-config	Saves the new configuration to memory.

Monitoring and Maintaining the PA-12E 2FE Port Adapter

After configuring the new interface, you can display its status and verify other information. To display information about the PA-12E/2FE port adapter, use the following commands in EXEC mode.

Command or Action	Purpose
Router# show version	Displays the configuration of the system hardware, the software version, the names and sources of configuration files, and the boot image.
Router# show controllers	Displays all current port adapters and their interfaces
Router# show interfaces fastethernet slot / port (ports 0 and 1) or Router# show interfaces ethernet slot / port (ports 2 through 13)	Displays the interfaces so that you can verify that they have the correct slot number and that the interface and line protocol are in the correct state.
Router# show bridge group	Displays all bridge groups and their interfaces.
Router# show interfaces fastethernet slot / port irb (ports 0 and 1) or Router# show interfaces ethernet slot / port irb (ports 2 through 13)	Displays the routed protocol so you can verify that it is configured correctly for each interface.
Router# show protocols	Displays the protocols configured for the entire system and specific interfaces.
Router# show pas eswitch addresses fastethernet slot / port (ports 0 and 1) or Router# show pas eswitch addresses ethernet slot / port (ports 2 through 13)	Displays the Layer 2 learned addresses for each interface.
Router# more system:running-config	Displays the running configuration file.
Router# more nvram:startup-config	Displays the configuration stored in NVRAM.

Configuring Bridge Groups Using the 12E 2FE VLAN Configuration WebTool

The 12E/2FE VLAN Configuration WebTool, shown in the figure below, is a web browser-based Java applet that displays configured interfaces and bridge groups for PA-12E/2FE port adapters installed in Cisco routers. With the WebTool you can perform the following tasks:

• Create and delete bridge groups (also referred to as VLANs)

• Add and remove PA-12E/2FE interfaces from bridge groups

• Assign colors to bridge groups and PA-12E/2FE interfaces

• Administratively shut down (disable) and bring up (enable) PA-12E/2FE interfaces

• View the bridge-group status of each PA-12E/2FE interface

You can access the 12E/2FE VLAN Configuration WebTool from the home page of your router. For complete procedures on how to use the VLAN Configuration WebTool, refer to the PA-12E/2FE Ethernet Switch Port Adapter book that accompanies the hardware.

All Cisco routers that run Cisco IOS Release 11.0 or later have a home page. All Cisco router home pages are password protected. Contact your network administrator if you do not have the name or password for your Cisco 7200 series router.

If your router has an installed PA-12E/2FE port adapter, the 12E/2FE VLAN Configuration WebTool shown in the figure above can be accessed from the home page of the router using a Java-enabled web browser.

Configuring the 100VG-AnyLAN Port Adapter

The 100VG-AnyLAN port adapter (PA-100VG) is available on Cisco 7200 series routers and on Cisco 7500 series routers.

The PA-100VG provides a single interface compatible with and specified by IEEE 802.12 to support 100 Mbps over Category 3 or Category 5 UTP cable with RJ-45 terminators. The PA-100VG supports 802.3 Ethernet packets and can be monitored with the IEEE 802.12 Interface MIB.

To configure the PA-100VG port adapter, use the following commands beginning in global configuration mode.

SUMMARY STEPS

1.    Do one of the following:

• Router(config)# interface vg-anylan slot / port
• (Cisco 7200)

2.    Router(config-if)# ip address ip-address mask

3.    Router(config-if)# frame-type ethernet

DETAILED STEPS

	Command or Action	Purpose
Step 1	Do one of the following: Router(config)# interface vg-anylan slot / port (Cisco 7200) Example: Router(config)# interface vg-anylan slot / port-adapter / port Example: (Cisco 7500)	Specifies a 100VG-AnyLAN interface and enters interface configuration.
Step 2	Router(config-if)# ip address ip-address mask	Specifies the IP address and subnet mask to the interface.
Step 3	Router(config-if)# frame-type ethernet	Configures the frame type. Currently, only Ethernet frames are supported. The frame type defaults to Ethernet.

What to Do Next

Note	The port number for the 100VG-AnyLAN port adapter is always 0.

Configuring the PA-100VG interface is similar to configuring an Ethernet or Fast Ethernet interface. To display information about the 100VG-AnyLAN port adapter, use the show interfaces vg-anylan EXEC command.

Configuring the Cisco 7200-I O-GE+E and Cisco 7200-I O-2FE E Input Output Controllers

The Cisco 7200-I/O-GE+E is an Input/Output controller that provides one Gigabit Ethernet and one Ethernet port. It is equipped with a GBIC receptacle for 1000-Mbps operation and an RJ-45 receptacle for 10-Mbps operation.

The Cisco 7200-I/O-2FE/E is an Input/Output controller that provides two autosensing Fast Ethernet ports and is equipped with two RJ-45 receptacles for 10/100-Mbps operation.

I/O controllers support the following features:

• Dual EIA/TIA-232 channels for local console and auxiliary ports

• NVRAM for storing the system configuration and environmental monitoring logs

• Two PC Card slots that hold Flash disks or Flash memory cards for storing the default Cisco IOS software image

• Flash memory for storing the boot helper image

• Two environmental sensors for monitoring the cooling air as it enters and leaves the chassis

• Cisco 7200-I O-GE+E and Cisco 7200-I O-2FE E Configuration Task List

Cisco 7200-I O-GE+E and Cisco 7200-I O-2FE E Configuration Task List

See the following sections for configuration tasks for the Cisco 7200-I/O-GE+E and the Cisco 7200-I/O-2FE/E feature. Each task in the list is identified as required or optional.

Note	For Cisco 7200 VXR routers used as router shelves in AS5800 Universal Access Servers, use the router-shelf / slot / port command format for all interface commands.

• Configuring the Interface Transmission Mode
• Configuring Interface Speed
• Configuring the Ethernet Fast Ethernet and Gigabit Ethernet Interfaces
• Verifying the Configuration
• Monitoring and Maintaining the Cisco 7200-I O GE+E and Cisco 7200-I O-2FE E

Configuring the Interface Transmission Mode

To configure the interface transmission mode, use the following commands beginning in privileged EXEC mode. The Fast Ethernet and Ethernet interfaces on the Cisco 7200-I/O-2FE/E are duplex auto by default.

SUMMARY STEPS

1.    Router# configure terminal

2.    Router(config)# interface fastethernet slot / port²

3.    Router(config)# duplex full

DETAILED STEPS

	Command or Action	Purpose
Step 1	Router# configure terminal	Enters global configuration mode and specifies that the console terminal is the source of the configuration subcommands.
Step 2	Router(config)# interface fastethernet slot / port2	Selects the Fast Ethernet interface to configure.
Step 3	Router(config)# duplex full	Changes the Fast Ethernet interface port transmission mode to full duplex from autonegotiation.

² Use the interface fastethernet router-shelf / slot / port command for a Cisco 7200 VXR used as a router shelf in an AS5800 Universal Access Server.

Configuring Interface Speed

To configure the two autosensing Ethernet/Fast Ethernet interfaces on the C7200-I/O-2FE/E, use the speed command. The the default interface speed is auto.The following procedure configures the C7200-I/O-2FE/E for a speed of 10 Mbps.

SUMMARY STEPS

1.    Router# configure terminal

2.    Router(Config)# interface ethernet slot / port³

3.    Router(Config-if)# interface fastethernet slot / port⁴

4.    Router(Config-if)# speed 10

DETAILED STEPS

	Command or Action	Purpose
Step 1	Router# configure terminal	Enters global configuration mode and specifies that the console terminal is the source of the configuration subcommands.
Step 2	Router(Config)# interface ethernet slot / port3	Selects the Ethernet interface to configure.
Step 3	Router(Config-if)# interface fastethernet slot / port4	Selects the Fast Ethernet interface to configure.
Step 4	Router(Config-if)# speed 10	Sets the Ethernet or Fast Ethernet interface speed to 10 Mbps.

³ Use the interface ethernet router-shelf / slot / port command for a Cisco 7200 VXR used as a router shelf in an AS5800 Universal Access Server.

⁴ Use the interface fastethernet router-shelf / slot / port command for a Cisco 7200 VXR used as a router shelf in an AS5800 Universal Access Server.

Configuring the Ethernet Fast Ethernet and Gigabit Ethernet Interfaces

The following procedure explains a basic configuration for an Ethernet, Fast Ethernet, or Gigabit Ethernet interface on a C7200-I/O-GE+E or a C7200-I/O-2FE/E.

SUMMARY STEPS

1.    Router# configure terminal

2.    Router(config)# interface ethernet slot / port⁵

3.    Router(config)# interface fastethernet slot / port⁶

4.    Router(config)# interface gigabitethernet slot / port⁷

5.    Router(config-if) # ip address ip-address mask

6.    Router(config-if)# duplex auto

7.    Router#(config-if)# Exit

DETAILED STEPS

	Command or Action	Purpose
Step 1	Router# configure terminal Example:	Enters global configuration mode and specifies that the console terminal is the source of the configuration subcommands.
Step 2	Router(config)# interface ethernet slot / port5 Example:	Selects the Ethernet interface on the I/O controller in slot 0 in port adapter slot 1 to configure.
Step 3	Router(config)# interface fastethernet slot / port6 Example:	Selects the Fast Ethernet interface on the I/O controller in slot 0 in port adapter slot 2 to configure.
Step 4	Router(config)# interface gigabitethernet slot / port7	Selects the Gigabit Ethernet interface on the I/O controller in slot 0 in port adapter slot 0 to configure.
Step 5	Router(config-if) # ip address ip-address mask	Assigns an IP address and subnet mask to the interface (if IP routing is enabled on the system).
Step 6	Router(config-if)# duplex auto	Changes the Fast Ethernet interface port transmission mode to autonegotiation.
Step 7	Router#(config-if)# Exit	Exits configuration mode.

⁵ Use the interface ethernet router-shelf / slot / port command for a Cisco 7200 VXR used as a router shelf in an AS5800 Universal Access Server.

⁶ Use the interface fastethernet router-shelf / slot / port command for a Cisco 7200 VXR used as a router shelf in an AS5800 Universal Access Server.

⁷ Use the interface gigabitethernet router-shelf / slot / port command for a Cisco 7200 VXR used as a router shelf in an AS5800 Universal Access Server.

Verifying the Configuration

Use the show interfaces {ethernet | fastethernet | gigabitethernet} command to verify that the interface and line protocol are in the correct state (up) and that the transmission mode is configured on the interface. You can configure full, half, or auto transmission mode for Ethernet and Fast Ethernet interfaces. You can configure forced transmission mode for Gigabit Ethernet interfaces. The following is sample output from the show interfaces gigabitethernet command.

Router# show interfaces gigabitethernet 0/0
GigabitEthernet0/0 is up, line protocol is up 
   Hardware is 82543 (Livengood), address is 00d0.ffb6.4c00 (bia 00d0.ffb6.4c00)
   Internet address is 10.1.1.0/0
   MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec, 
      reliability 255/255, txload 1/255, rxload 1/255
   Encapsulation ARPA, loopback not set
   Keepalive set (10 sec)
   Full-duplex mode, link type is autonegotiation, media type is SX
   output flow-control is on, input flow-control is on
   ARP type:ARPA, ARP Timeout 04:00:00
   Last input 00:00:04, output 00:00:03, output hang never
   Last clearing of "show interface" counters never
   Queueing strategy:fifo
   Output queue 0/40, 0 drops; input queue 0/75, 0 drops
   5 minute input rate 0 bits/sec, 0 packets/sec
   5 minute output rate 0 bits/sec, 0 packets/sec
      2252 packets input, 135120 bytes, 0 no buffer
      Received 2252 broadcasts, 0 runts, 0 giants, 0 throttles
      0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
      0 watchdog, 0 multicast, 0 pause input
      0 input packets with dribble condition detected
      2631 packets output, 268395 bytes, 0 underruns
      0 output errors, 0 collisions, 2 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

Monitoring and Maintaining the Cisco 7200-I O GE+E and Cisco 7200-I O-2FE E

To monitor and maintain the Gigabit Ethernet or Ethernet interfaces on the Cisco 7200-I/O-GE+E, use the following commands in privileged EXEC mode.

Command or Action	Purpose
Router# show controllers ethernet	Displays hardware and software information about the Ethernet interface.
Router# show interfaces ethernet slot/port8	Displays information about the Ethernet interface on the router.
Router# show controllers gigabitethernet	Displays hardware and software information about the Gigabit Ethernet interface.
Router# show interfaces gigabitethernet slot/port9	Displays information about a Gigabit Ethernet interface on the router.

⁸ Use the show interfaces ethernet router-shelf/slot/port command for a Cisco 7200 VXR used as a router shelf in an AS5800 Universal Access Server

⁹ Use the interface gigabitethernet router-shelf/slot/port command for a Cisco 7200 VXR used as a router shelf in an AS5800 Universal Access Server.

To monitor and maintain the Fast Ethernet or Ethernet interfaces on the Cisco 7200-I/O-2FE/E, use the following commands in privileged EXEC mode.

Command or Action	Purpose
Router# show controllers ethernet	Displays hardware and software information about the Ethernet interface.
Router# show interfaces ethernet slot/port10	Displays information about an Ethernet interface on the router.
Router# show controllers fastethernet	Displays hardware and software information about the Fast Ethernet interfaces.
Router# show interfaces fastethernet	Displays information about a Fast Ethernet interface on the router.

¹⁰ Use the show interfaces ethernet router-shelf/slot/port command for a Cisco 7200 VXR used as a router shelf in an AS5800 Universal Access Server.

Configuring an FDDI Interface

The FDDI is an ANSI-defined standard for a timed 100-Mbps token passing over a fiber-optic cable. FDDI is not supported on access servers.

A FDDI network consists of two counter-rotating, token-passing fiber-optic rings. On most networks, the primary ring is used for data communication and the secondary ring is used as a hot standby. The FDDI standard sets a total fiber length of 200 kilometers. (The maximum circumference of the FDDI network is only half the specified kilometers because of the wrapping or looping back of the signal that occurs during fault isolation.)

The FDDI standard allows a maximum of 500 stations with a maximum distance of 2 kilometers between active stations, when interconnecting them with multimode fiber, or a maximum distance of 10 kilometers between them when interconnected via single mode fiber, both of which are supported by FDDI interface controllers. The FDDI frame can contain a minimum of 17 bytes and a maximum of 4500 bytes. Cisco FDDI implementation supports Station Management (SMT) Version 7.3 of the X3T9.5 FDDI specification, offering a single MAC dual-attach interface that supports fault-recovery methods of dual attachment stations (DASs). The mid-range platforms also support single attachment stations (SASs).

Refer to the Cisco Product Catalog for specific information on platform and interface compatibility. For installation and configuration information, refer to the installation and configuration publication for the appropriate interface card or port adapter.

• Source-Route Bridging over FDDI on Cisco 4000-M Cisco 4500-M and Cisco 4700-M Routers
• Particle-Based Switching of Source-Route Bridge Packets on Cisco 7200 Series Routers
• Using Connection Management Information
• FDDI Configuration Task List

Source-Route Bridging over FDDI on Cisco 4000-M Cisco 4500-M and Cisco 4700-M Routers

Source-route bridging (SRB) is supported on the FDDI interface to the Cisco 4000-M, Cisco 4500-M, and Cisco 4700-M routers. For instructions on configuring autonomous FDDI SRB or fast-switching SRB over FDDI, refer to the "Configuring Source-Route Bridging" chapter of the CiscoIOS Bridging and IBM Networking Configuration Guide .

Particle-Based Switching of Source-Route Bridge Packets on Cisco 7200 Series Routers

SRB is supported over FDDI. Particle-based switching is supported for SRB packets (over FDDI and Token Ring) by default.

Particle-based switching adds scatter-gather capability to SRB to improve performance. Particles represent a communications data packet as a collection of noncontiguous buffers. The traditional Cisco IOS packet has a packet type control structure and a single contiguous data buffer. A particle packet has the same packet type control structure, but also maintains a queue of particle type structures, each of which manages its own block.

The scatter-gather architecture used by particle-based switching provides the following advantages:

• Allows drivers to use memory more efficiently (especially when using media that has a large maximum transmission unit [MTU]). For example, Token Ring buffers could be 512 bytes rather than 16 KB.

• Allows concurrent use of the same region of memory. For example, on IP multicast a single packet is received and sent out on multiple interfaces simultaneously.

• Allows insertion or deletion of memory at any location in a packet (not just at the beginning or end).

For information about configuring SRB over FDDI, refer to the "Configuring Source-Route Bridging" chapter of the CiscoIOS Bridging and IBM Networking Configuration Guide .

Using Connection Management Information

Connection management (CMT) is a FDDI process that handles the transition of the ring through its various states (off, on, active, connect, and so on) as defined by the X3T9.5 specification. The FIP (FDDI Interface Processor) provides CMT functions in microcode.

A partial sample output of the show interfaces fddi command follows, along with an explanation of how to interpret the CMT information in the output.

Phy-A state is active, neighbor is B, cmt signal bits 08/20C, status ALS
Phy-B state is active, neighbor is A, cmt signal bits 20C/08, status ILS
CFM is thru A, token rotation 5000 usec, ring operational 0:01:42
Upstream neighbor 0800.2008.C52E, downstream neighbor 0800.2008.C52E

The show interfaces fddi example shows that Physical A (Phy-A) completed CMT with its neighbor. The state is active, and the display indicates a Physical B-type neighbor.

The sample output indicates CMT signal bits 08/20C for Phy-A. The transmit signal bits are 08. Looking at the pulse code modulation (PCM) state machine, 08 indicates that the port type is A, that the port compatibility is set, and that the LCT duration requested is short. The receive signal bits are 20C, that indicate that the neighbor type is B, that port compatibility is set, that there is a MAC on the port output, and so on.

The neighbor is determined from the received signal bits, as follows:

Bit Positions	9 8 7 6 5 4 3 2 1 0
Value Received	1 0 0 0 0 0 1 1 0 0

Interpreting the bits in the diagram above, the received value equals 0x20C. Bit positions 1 and 2 (0 1) indicate a Physical B-type connection.

The transition states displayed indicate that the CMT process is running and actively trying to establish a connection to the remote physical connection. The CMT process requires state transition with different signals being transmitted and received before moving on to the state ahead as indicated in the PCM state machine. The 10 bits of CMT information are transmitted and received in the Signal State. The NEXT state is used to separate the signaling performed in the Signal State. Therefore, in the preceding sample output, the NEXT state was entered 11 times.

Note	The display line showing transition states is not generated if the FDDI interface has been shut down, or if the cmt disconnect command has been issued, or if the fddi if-cmt command has been issued. (The fddi if-cmt command applies to the Cisco 7500 series routers only.)

The CFM state is through A in the sample output, which means the Phy-A of this interface has successfully completed CMT with the Phy-B of the neighbor and Phy-B of this interface has successfully completed CMT with the Phy-A of the neighbor.

The display (or nondisplay) of the upstream and downstream neighbor does not affect the ability to route data. Because the upstream neighbor is also its downstream neighbor in the sample, there are only two stations in the ring: the network server and the router at address 0800.2008.C52E.

FDDI Configuration Task List

To configure a FDDI interface, perform the tasks in the following sections. Each task in the list is identified as either required or optional.

• Specifying a FDDI Interface
• Enabling FDDI Bridging Encapsulation
• Enabling Full-Duplex Mode on the FDDI Interface
• Setting the Token Rotation Time
• Setting the Transmission Valid Timer
• Controlling the Transmission Timer
• Modifying the C-Min Timer
• Modifying the TB-Min Timer
• Modifying the FDDI Timeout Timer
• Controlling SMT Frame Processing
• Enabling Duplicate Address Checking
• Setting the Bit Control
• Controlling the CMT Microcode
• Starting and Stopping FDDI
• Setting FDDI Frames per Token Limit
• Controlling the FDDI SMT Message Queue Size
• Preallocating Buffers for Bursty FDDI Traffic

Specifying a FDDI Interface

To specify a FDDI interface and enter interface configuration mode, use one of the following commands in global configuration mode.

Command or Action	Purpose
Router(config)# interface fddi number	Enters interface configuration.
Router(config)# interface fddi slot / port	Enters interface configuration for the Cisco 7200 or Cisco 7500 series routers.

Enabling FDDI Bridging Encapsulation

By default, Cisco FDDI uses the SNAP encapsulation format defined in RFC 1042. It is not necessary to define an encapsulation method for this interface when using the FIP.

FIP fully supports transparent and translational bridging for the following configurations:

• FDDI-to-FDDI

• FDDI-to-Ethernet

• FDDI-to-Token Ring

Enabling FDDI bridging encapsulation places the FIP into encapsulation mode when doing bridging. In transparent mode, the FIP interoperates with earlier versions of encapsulating interfaces when performing bridging functions on the same ring. When using the FIP, you can specify the encapsulation method by using the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi encapsulate	Specifies the encapsulation method for the FIP.

When you are doing translational bridging, use routing for routable protocols and use translational bridging for the rest, such as local-area transport (LAT).

Note

Bridging between dissimilar media presents several problems that can prevent communications. These problems include bit-order translation (using MAC addresses as data), maximum transfer unit (MTU) differences, frame status differences, and multicast address usage. Some or all of these problems might be present in a multimedia-bridged LAN and might prevent communication. These problems are most prevalent in networks that bridge between Token Ring and Ethernet networks or between Token Ring and FDDI because of the different ways that Token Ring is implemented by the end nodes.

We are currently aware of problems with the following protocols when bridged between Token Ring and other media: AppleTalk, DECnet, IP, Novell IPX, Phase IV, VINES, and XNS. Further, the following protocols might have problems when bridged between FDDI and other media: Novell IPX and XNS. We recommend that these protocols be routed whenever possible.

Enabling Full-Duplex Mode on the FDDI Interface

To enable full-duplex mode on the PA-F/FD-SM and PA-F/FD-MM port adapters, use one of the following commands in interface configuration mode.

Command or Action	Purpose
Router(config-if)# full-duplex or Router(config-if)# no half-duplex	Enables full-duplex on the FDDI interface of the PA-F/FD-SM and PA-F/FD-MM port adapter.

Setting the Token Rotation Time

You can set the FDDI token rotation time to control ring scheduling during normal operation and to detect and recover from serious ring error situations. To do so, use the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi token-rotation-time microseconds	Sets the FDDI token rotation time.

The FDDI standard restricts the allowed time to greater than 4000 microseconds and less than 165,000 microseconds. As defined in the X3T9.5 specification, the value remaining in the token rotation timer (TRT) is loaded into the token holding timer (THT). Combining the values of these two timers provides the means to determine the amount of bandwidth available for subsequent transmissions.

Setting the Transmission Valid Timer

You can set the transmission timer to recover from a transient ring error by using the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi valid-transmission-time microseconds	Sets the FDDI valid transmission timer.

Controlling the Transmission Timer

You can set the FDDI control transmission timer to control the FDDI TL-Min time, which is the minimum time to transmit a Physical Sublayer or PHY line state before advancing to the next Physical Connection Management or PCM state as defined by the X3T9.5 specification. To do so, use the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi tl-min-time microseconds	Sets the FDDI control transmission timer.

Modifying the C-Min Timer

You can modify the C-Min timer on the PCM from its default value of 1600 microseconds by using the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi c-min microseconds	Sets the C-Min timer on the PCM.

Modifying the TB-Min Timer

You can change the TB-Min timer in the PCM from its default value of 100 milliseconds. To do so, use the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi tb-min milliseconds	Sets TB-Min timer in the PCM.

Modifying the FDDI Timeout Timer

You can change the FDDI timeout timer in the PCM from its default value of 100 ms. To do so, use the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi t-out milliseconds	Sets the timeout timer in the PCM.

Controlling SMT Frame Processing

You can disable and enable SMT frame processing for diagnostic purposes. To do so, use one of the following commands in interface configuration mode.

Command or Action	Purpose
Router(config-if)# no fddi smt-frames	Disables SMT frame processing.
Router(config-if)# fddi smt-frames	Enables SMT frame processing.

Enabling Duplicate Address Checking

You can enable the duplicate address detection capability on the FDDI. If the FDDI finds a duplicate address, it displays an error message and shuts down the interface. To enable duplicate address checking, use the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi duplicate-address-check	Enables duplicate address checking capability.

Setting the Bit Control

You can set the FDDI bit control to control the information transmitted during the Connection Management (CMT) signaling phase. To do so, use the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi cmt-signal-bits signal-bits [phy-a | phy-b]	Sets the FDDI bit control.

Controlling the CMT Microcode

You can control whether the CMT onboard functions are on or off. The FIP provides CMT functions in microcode. These functions are separate from those provided on the processor card and are accessed through EXEC commands.

The default is for the FIP CMT functions to be on. A typical reason to disable these functions is when you work with new FDDI equipment and have problems bringing up the ring. If you disable the CMT microcode, the following actions occur:

• The FIP CMT microcode is disabled.

• The main system code performs the CMT function while debugging output is generated.

To disable the CMT microcode, use the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# no fddi if-cmt	Disables the FCIT CMT functions.

Starting and Stopping FDDI

In normal operation, the FDDI interface is operational once the interface is connected and configured. You can start and stop the processes that perform the CMT function and allow the ring on one fiber to be stopped. To do so, use either of the following commands in EXEC mode.

Command or Action	Purpose
Router# cmt connect [interface-name [phy-a | phy-b]]	Starts CMT processes on a FDDI ring.
Router# cmt disconnect [interface-name [phy-a | phy-b]]	Stops CMT processes on a FDDI ring.

Do not use either of the preceding commands during normal operation of FDDI; they are used during interoperability tests.

Setting FDDI Frames per Token Limit

The FDDI interface is able to transmit multiple frames per token on a Cisco 4000, a Cisco 4500, and a Cisco 4700 series router, instead of transmitting only a single frame at a time. You can specify the maximum number of frames to be transmitted with each token capture. This significantly improves your throughput when you have heavy or very bursty traffic.

To configure the FDDI interface to transmit a maximum number of frames per token capture, use the following commands beginning in privileged EXEC mode.

SUMMARY STEPS

1.    Router# configure terminal

2.    Router(config)# interface fddi number

3.    Router(config-if)# fddi number

4.    Router(config-if)# fddi frames-per-token number

5.    Router(config-if)# fddi frames-per-token number

DETAILED STEPS

	Command or Action	Purpose
Step 1	Router# configure terminal	Enters global configuration mode.
Step 2	Router(config)# interface fddi number	Enters interface configuration mode.
Step 3	Router(config-if)# fddi number	Shows fddi command options.
Step 4	Router(config-if)# fddi frames-per-token number	Shows fddi frames-per-token command options.
Step 5	Router(config-if)# fddi frames-per-token number	Specifies the maximum number of frames to be transmitted per token capture.

Controlling the FDDI SMT Message Queue Size

You can set the maximum number of unprocessed FDDI Station Management (SMT) frames that will be held for processing. Setting this number is useful if the router that you are configuring gets bursts of messages that arrive faster than the router can process. To set the number of frames, use the following command in global configuration mode.

Command or Action	Purpose
Router(config)# smt-queue-threshold number	Sets SMT message queue size.

Preallocating Buffers for Bursty FDDI Traffic

The FCI card preallocates three buffers to handle bursty FDDI traffic (for example, Network File System (NFS) bursty traffic). You can change the number of preallocated buffers use the following command in interface configuration mode.

Command or Action	Purpose
Router(config-if)# fddi burst-count	Preallocates buffers to handle bursty FDDI traffic.

Configuring a Hub Interface

Cisco 2500 series includes routers that have hub functionality for an Ethernet interface. The hub is a multiport repeater. The advantage of an Ethernet interface over a hub is that the hub provides a star-wiring physical network configuration while the Ethernet interface provides 10BASE-T physical network configuration. The router models with hub ports and their configurations are as follows:

• Cisco 2505--1 Ethernet (8 ports) and 2 serial

• Cisco 2507--1 Ethernet (16 ports) and 2 serial

• Cisco 2516--1 Ethernet (14 ports), 2 serial, and 1 ISDN BRI

Cisco provides Simple Network Management Protocol (SNMP) management of the Ethernet hub as specified in RFC 1516, Definitions of Managed Objects for IEEE 802.3 Repeater Devices .

To configure hub functionality on an Ethernet interface, perform the tasks in the following sections Each task in the list is identified as either required or optional.

For configuration examples, see the Hub Configuration Examples.

• Enabling a Hub Port
• Disabling or Enabling Automatic Receiver Polarity Reversal
• Disabling or Enabling the Link Test Function
• Enabling Source Address Control
• Enabling SNMP Illegal Address Trap

Enabling a Hub Port

To enable a hub port, use the following commands in global configuration mode.

SUMMARY STEPS

1.    Router(config)# hub ethernet numberport [end-port]

2.    Router(config)# no shutdown

DETAILED STEPS

	Command or Action	Purpose
Step 1	Router(config)# hub ethernet numberport [end-port]	Specifies the hub number and the hub port (or range of hub ports) and enters hub configuration mode.
Step 2	Router(config)# no shutdown	Enables the hub ports.

Disabling or Enabling Automatic Receiver Polarity Reversal

On Ethernet hub ports only, the hub ports can invert, or correct, the polarity of the received data if the port detects that the received data packet waveform polarity is reversed because of a wiring error. This receive circuitry polarity correction allows the hub to repeat subsequent packets with correct polarity. When enabled, this function is executed once after reset of a link fail state.

Automatic receiver polarity reversal is enabled by default. To disable this feature on a per-port basis, use the following command in hub configuration mode.

Command or Action	Purpose
Router(config-hub)# no auto-polarity	Disables automatic receiver polarity reversal.

To enable automatic receiver polarity reversal on a per-port basis, use the following command in hub configuration mode.

Command or Action	Purpose
Router(config-hub)# auto-polarity	Enables automatic receiver polarity reversal.

Disabling or Enabling the Link Test Function

The link test function applies to Ethernet hub ports only. The Ethernet ports implement the link test function as specified in the 802.3 10BASE-T standard. The hub ports will transmit link test pulses to any attached twisted pair device if the port has been inactive for more than 8 to 17 milliseconds.

If a hub port does not receive any data packets or link test pulses for more than 65 to 132 milliseconds and the link test function is enabled for that port, that port enters link fail state and cannot transmit or receive. The hub port is enabled again when it receives four consecutive link test pulses or a data packet.

The link test function is enabled by default. To allow the hub to interoperate with 10BASE-T twisted-pair networks that do not implement the link test function, the link test receive function of the hub can be disabled on a per-port basis. To do so, use the following command in hub configuration mode.

Command	Purpose
Router(config-hub)# no link-test	Disables the link test function.

To enable the link test function on a hub port connected to an Ethernet interface, use the following command in hub configuration mode.

Command	Purpose
Router(config-hub)# link-test	Enables the link test function.

Enabling Source Address Control

On an Ethernet hub port only, you can configure a security measure such that the port accepts packets only from a specific MAC address. For example, suppose your workstation is connected to port 3 on a hub, and source address control is enabled on port 3. Your workstation has access to the network because the hub accepts any packet from port 3 with the MAC address of the workstation. Any packets that arrive with a different MAC address cause the port to be disabled. The port is enabled again after 1 minute, and the MAC address of incoming packets is checked again.

To enable source address control on a per-port basis, use the following command in hub configuration mode.

Command	Purpose
Router(config-hub)# source-address [mac-address]	Enables source address control.

If you omit the optional MAC address, the hub remembers the first MAC address that it receives on the selected port and allows only packets from the learned MAC address.

See the examples of establishing source address control in the Hub Configuration Examples.

Enabling SNMP Illegal Address Trap

To enable the router to issue an SNMP trap when an illegal MAC address is detected on an Ethernet hub port, use the following commands in hub configuration mode.

SUMMARY STEPS

1.    Router(config-hub)# hub ethernet number port [end-port]

2.    Router(config-hub)# snmp trap illegal-address

DETAILED STEPS

	Command or Action	Purpose
Step 1	Router(config-hub)# hub ethernet number port [end-port]	Specifies the hub number and the hub port (or range of hub ports) and enters hub configuration mode.
Step 2	Router(config-hub)# snmp trap illegal-address	Enables the router to issue an SNMP trap when an illegal MAC address is detected on the hub port.

What to Do Next

You may need to set up a host receiver for this trap type (snmp-server host) for a Network Management System (NMS) to receive this trap type. The default is no trap. For an example of configuring a SNMP trap for an Ethernet hub port, see the Hub Configuration Examples.

Configuring a Token Ring Interface

Cisco supports various Token Ring interfaces. Refer to the Cisco Product Catalog for information about platform and hardware compatibility.

The Token Ring interface supports both routing (Layer 3 switching) and source-route bridging (Layer 2 switching) on a per-protocol basis. For example, IP traffic could be routed, while SNA traffic is bridged. Routing features enhance source-route bridges

The Token Ring MIB variables support the specification in RFC 1231, IEEE 802.5 Token Ring MIB . The mandatory Interface Table and Statistics Table are implemented, but the optional Timer Table of the Token Ring MIB is not. The Token Ring MIB has been implemented for the Token Ring Interface Processor (TRIP).

Use the show interfaces, show controllers token, and show controllers cbusEXEC commands to display the Token Ring numbers. These commands provide a report for each ring that Cisco IOS software supports.

Note

If the system receives an indication of a cabling problem from a Token Ring interface, it puts that interface into a reset state and does not attempt to restart it. It functions this way because periodic attempts to restart the Token Ring interface drastically affect the stability of routing tables. Once you have plugged the cable into the MAU (media attachment unit) again, restart the interface by using the clear interface tokenring numbercommand, where the number argument is the interface number.

By default, the Token Ring interface uses the SNAP encapsulation format defined in RFC 1042. It is not necessary to define an encapsulation method for this interface.

• Particle-Based Switching of Source-Route Bridge Packets on Cisco 7200 Series Routers
• Dedicated Token Ring Port Adapter
• Token Ring Interface Configuration Task List

Particle-Based Switching of Source-Route Bridge Packets on Cisco 7200 Series Routers

Particle-based switching is supported for SRB packets (over FDDI and Token Ring) by default.

Particle-based switching adds scatter-gather capability to SRB to improve performance. Particles represent a communications data packet as a collection of noncontiguous buffers. The traditional Cisco IOS packet has a packet type control structure and a single contiguous data buffer. A particle packet has the same packet type control structure, but it also maintains a queue of particle type structures, each of which manages its own block.

The scatter-gather architecture used by particle-based switching provides the following advantages:

• Allows drivers to use memory more efficiently (especially when using media that has a large maximum transmission unit [MTU]). For example, Token Ring buffers could be 512 bytes rather than 16 KB.

• Allows concurrent use of the same region of memory. For example, on IP multicast a single packet is received and sent out on multiple interfaces simultaneously.

• Allows insertion or deletion of memory at any location in a packet (not just at the beginning or end).

For information about configuring SRB over FDDI, refer to the "Configuring Source-Route Bridging" chapter of the CiscoIOS Bridging and IBM Networking Configuration Guide .

Dedicated Token Ring Port Adapter

The Dedicated Token Ring port adapter (PA-4R-DTR) is available on Cisco 7500 series routers, Cisco 7200 series routers, and Cisco 7000 series routers with the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI).

The PA-4R-DTR provides up to four IBM Token Ring or IEEE 802.5 Token Ring interfaces. Each Token Ring interface can be set for 4-Mbps or 16-Mbps half-duplex or full-duplex operation and can operate as a standard Token Ring station or as a concentrator port. The default for all interfaces is Token Ring station mode with half-duplex 16-Mbps operation. The PA-4R-DTR connects over Type 1 lobe or Type 3 lobe cables, with each interface providing an RJ-45 receptacle.

Token Ring Interface Configuration Task List

To configure a Token Ring interface, perform the tasks in the following sections. Each task is identified as either required or optional.

• Specifying a Token Ring Interface
• Enabling Early Token Release
• Configuring PCbus Token Ring Interface Management
• Enabling a Token Ring Concentrator Port
• Monitoring and Maintaining the Port

Specifying a Token Ring Interface

To specify a Token Ring interface and enter interface configuration mode, use one of the following commands in global configuration mode.

Command	Purpose
Router(config)# interface tokenring number	Enters interface configuration mode.
Router(config)# interface tokenring slot / port	Enters interface configuration mode for the Cisco 7200 or Cisco 7500 series routers.
Router(config)# interface tokenring slot / port-adapter / port	Enters interface configuration mode for the Cisco 7500 series routers.

Enabling Early Token Release

Cisco Token Ring interfaces support early token release, a method whereby the interface releases the token back onto the ring immediately after transmitting rather than waiting for the frame to return. This feature can help to increase the total bandwidth of the Token Ring. To configure the interface for early token release, use the following command in interface configuration mode.

Command	Purpose
Router(config-if)# early-token-release	Enables early token release.

Configuring PCbus Token Ring Interface Management

The Token Ring interface on the AccessPro PC card can be managed by a remote LAN manager over the PCbus interface. Currently, the LanOptics Hub Networking Management software running on an IBM-compatible PC is supported.

To enable LanOptics Hub Networking Management of a PCbus Token Ring interface, use the following command in interface configuration mode.

Command	Purpose
Router(config-if)# local-lnm	Enables PCbus LAN management.

Enabling a Token Ring Concentrator Port

To enable an interface to operate as a concentrator port, use the following command in interface configuration mode.

Command	Purpose
Router(config-if)# port	Specifies concentrator port operation.

Monitoring and Maintaining the Port

To monitor the Token Ring concentrator port, use one or more of the following commands in EXEC mode.

Command	Purpose
Router# show controllers token	Displays internal state information about the Token Ring interfaces in the system.
Router# show interfaces token	Displays high-level statistics for a particular interface.

LAN Interface Configuration Examples

This section provides the following examples to illustrate configuration tasks described in this chapter.

• Ethernet Encapsulation Enablement Example
• Full-Duplex Enablement Operation Example
• PA-12E 2FE Port Configuration Examples
• PA-VG100 Port Adapter Configuration Example
• Cisco 7200-I O-GE+E and Cisco 7200-I O-2FE E Configuration Examples
• Fast EtherChannel Configuration Examples
• FDDI Frames Configuration Example
• Hub Configuration Examples

Ethernet Encapsulation Enablement Example

These commands enable standard Ethernet Version 2.0 encapsulation on the Ethernet interface processor in slot 4 on port 2 of a Cisco 7500 series router:

interface ethernet 4/2
 encapsulation arpa

Full-Duplex Enablement Operation Example

The following example assigns an IP address and subnet mask, specifies an MII Ethernet connector, and enables full-duplex mode on Fast Ethernet interface port 0 in slot 1 port adapter 0:

Router(config)# interface fastethernet 1/0/0
Router(config-if)# 
ip address 10.1.1.10 255.255.255.0 
Router(config-if)# 
full-duplex
Router(config-if)# 
media-type mii
Router(config-if)# exit
Router(config)# exit

PA-12E 2FE Port Configuration Examples

The following is an example of a configuration for the PA-12E/2FE port adapter interface. Bridge groups 10, 20, and 30 use IEEE Spanning Tree Protocol. The first four interfaces of a PA-12E/2EF port adapter in port adapter slot 3 use bridge groups 10 and 20. Each interface is assigned to a bridge group, and the shutdown state is set to up. The PA-12E/2FE port adapter supports store-and-forward or cut-through switching technology between interfaces within the same bridge group; store-and-forward is the default. In the following example, the cut-throughcommand is used to configure each interface for cut-through switching of received and transmitted data:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL-Z.
Router(config)# 
bridge 10 protocol ieee
Router(config)# 
bridge 20 protocol ieee
Router(config)# 
bridge 30 protocol ieee
Router(config)#
 
interface fastethernet 3/0
Router(config-if)#
 
bridge-group 10
Router(config-if)#
 
cut-through
Router(config-if)#
 no shutdown
Router(config-if)# 
exit
Router(config)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface Fast Ethernet3/0, changed
state to up
%LINK-3-UPDOWN: Interface Fast Ethernet3/0, changed state to up
Router(config)#
 interface fastethernet 3/1
Router(config-if)#
 bridge-group 10
Router(config-if)#
 
cut-through
Router(config-if)#
 
no shutdown
Router(config-if)# 
exit
Router(config)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface Fast Ethernet3/1, changed
state to up
%LINK-3-UPDOWN: Interface Fast Ethernet3/1, changed state to up
Router(config)#
 interface ethernet 3/2
Router(config-if)#
 bridge-group 20
Router(config-if)#
 cut-through
Router(config-if)#
 
no shutdown
Router(config-if)# 
exit
Router(config)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet3/2, changed state to up
%LINK-3-UPDOWN: Interface Ethernet3/2, changed state to up
Router(config)#
 interface ethernet 3/3
Router(config-if)#
 bridge-group 20
Router(config-if)#
 cut-through
Router(config-if)#
 
no shutdown
Router(config-if)# 
exit
Router(config)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet3/3, changed state to up
%LINK-3-UPDOWN: Interface Ethernet3/3, changed state to up

The following example shows integrated routing and bridging enabled on the bridge groups. Bridge group 10 is assigned an IP address and subnet mask, and the shutdown state is changed to up. Bridge group 10 is configured to route IP.

Router(config)# 
bridge irb
Router(config)# 
interface bvi 10
Router(config-if)# 
ip address 10.1.15.1 255.255.255.0
Router(config-if)# 
no shutdown
Router(config-if)# 
exit
Router(config)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface BVI10, changed state to up
Router(config)# 
bridge 10 route ip
Router(config)# exit
Router#

PA-VG100 Port Adapter Configuration Example

The following is an example of a basic configuration for the PA-VG100 port adapter interface in slot 1 on a Cisco 7500 series router. In this example, IP routing is enabled on the router, so an IP address and subnet mask are assigned to the interface.

configure terminal
interface vg-anylan 1/0/0 
 ip address 10.1.1.10 255.255.255.0 
 no shutdown 
 exit
exit

Cisco 7200-I O-GE+E and Cisco 7200-I O-2FE E Configuration Examples

This section provides the following configuration examples:

• Configuring the Gigabit Ethernet Interface on the Cisco 7200-I O-GE+E
• Configuring Autonegotiation on the Cisco 7200-I O-2FE E

Configuring the Gigabit Ethernet Interface on the Cisco 7200-I O-GE+E

The following example configures the Gigabit Ethernet interface on the Cisco 7200-I/O-GE+E. The following commands are configured on slot 0, port 0.

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# interface gigabitethernet 0/0
Router(config-if)# ip address 10.1.1.10 255.255.255.252
Router(config-if)# negotiation auto
Router(config-if)# end

Configuring Autonegotiation on the Cisco 7200-I O-2FE E

The following example configures the Fast Ethernet interface on the Cisco 7200-I/O-2FE/E for fully enabled autonegotiation:

Router# 
configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# interface fastethernet 0/0
Router(config-if)# 
duplex auto
Router(config-if)# speed auto

Fast EtherChannel Configuration Examples

The figure below shows four point-to-point Fast Ethernet interfaces that are aggregated into a single Fast EtherChannel interface.

The configuration file that illustrates this topology follows.

The following is an example of how to create a Fast EtherChannel (port-channel interface) with four Fast Ethernet interfaces. In this example, ISL is enabled on the Fast EtherChannel, and an IP address is assigned to the subinterface.

Router# configure terminal
Router(config)# interface port-channel 1 
Router(config-if)# no shutdown 
Router(config-if)# exit
Router(config)# interface port-channel 1.1
Router(config-if)# ip address 10.1.1.10 255.255.255.0 
Router(config-if)# encapsulation isl 100
Router(config-if)# exit
Router(config)# interface fastethernet 0/0/0
Router(config-if)# no ip address
Router(config-if)# channel-group 1
Fast Ethernet 0/0 added as member-1 to port-channel1.
Router(config-if)# exit
Router(config)# interface fastethernet 0/1/0
Router(config-if)# no ip address
Router(config-if)# channel-group 1
Fast Ethernet 0/1 added as member-2 to port-channel1.
Router(config-if)# exit
Router(config)# interface fastethernet 1/0/0
Router(config-if)# no ip address
Router(config-if)# channel-group 1
Fast Ethernet 1/0 added as member-3 to port-channel1.
Router(config-if)# exit
Router(config)# interface fastethernet 1/1/0
Router(config-if)# no ip address
Router(config-if)# channel-group 1
Fast Ethernet 1/1 added as member-4 to port-channel1.
Router(config-if)# exit
Router(config)# exit
Router#

The following is a partial example of a configuration file. The MAC address is automatically added to the Fast Ethernet interface when the interfaces are added to the Fast EtherChannel.

Note	If you do not assign a static MAC address on the port-channel interface, the Cisco IOS software automatically assigns a MAC address. If you assign a static MAC address and then later remove it, the Cisco IOS software automatically assigns a MAC address.

interface Port-channel1
 ip address 10.1.1.10 255.255.255.0
!
interface Port-channel1.1
 encapsulation isl 100
!
interface Fast Ethernet0/0/0
 mac-address 00e0.1476.7600
 no ip address
 channel-group 1
!
interface Fast Ethernet0/1/0
 mac-address 00e0.1476.7600
 no ip address
 channel-group 1
!
interface Fast Ethernet1/0/0
 mac-address 00e0.1476.7600
 no ip address
 channel-group 1
!
interface Fast Ethernet1/1/0
 mac-address 00e0.1476.7600
 no ip address
 channel-group 1

FDDI Frames Configuration Example

The following example shows how to configure the FDDI interface to transmit four frames per token capture:

! Enter global configuration mode.
  4700# 
configure terminal
! Enter interface configuration mode.
  4700(config)#
 interface fddi 0
! Show the fddi command options.
  4700(config-if)# 
fddi ?
  encapsulate              Enable FDDI Encapsulation bridging
  frames-per-token         Maximum frames to transmit per service opportunity
  tl-min-time              Line state transmission time
  token-rotation-time      Set the token rotation timer
  valid-transmission-time  Set transmission valid timer
! Show fddi frames-per-token command options.
  4700(config-if)# 
fddi frames-per-token ?
  <1-10> Number of frames per token, default = 3
! Specify 4 as the maximum number of frames to be transmitted per token.
  4700(config-if)# 
fddi frames-per-token 4

Hub Configuration Examples

This section provides the following hub configuration examples:

• Hub Port Startup Examples
• Source Address for an Ethernet Hub Port Configuration Examples
• Hub Port Shutdown Examples
• SNMP Illegal Address Trap Enablement for Hub Port Example

Hub Port Startup Examples

The following example configures port 1 on hub 0 of Ethernet interface 0:

hub ethernet 0 1
 no shutdown

The following example configures ports 1 through 8 on hub 0 of Ethernet interface 0:

hub ethernet 0 1 8
 no shutdown

Source Address for an Ethernet Hub Port Configuration Examples

The following example configures the hub to allow only packets from MAC address 1111.2222.3333 on port 2 of hub 0:

hub ethernet 0 2
 source-address 1111.2222.3333

The following example configures the hub to remember the first MAC address received on port 2 and allow only packets from that learned MAC address:

hub ethernet 0 2
 source-address

Hub Port Shutdown Examples

The following example shuts down ports 3 through 5 on hub 0:

hub ethernet 0 3 5
 shutdown

The following example shuts down port 3 on hub 0:

hub ethernet 0 3
 shutdown

SNMP Illegal Address Trap Enablement for Hub Port Example

The following example specifies the gateway IP address and enables an SNMP trap to be issued to the host 172.16.40.51 when a MAC address violation is detected on hub ports 2, 3, or 4. It specifies that Ethernet interface 0 is the source for all traps on the router. The community string is defined as the string public and the read/write parameter is set.

ip route 0.0.0.0 0.0.0.0 172.22.10.1
snmp-server community public rw
snmp-server trap-source ethernet 0
snmp-server host 172.16.40.51 public
hub ethernet 0 2 4
snmp trap illegal-address