|
|
Use the information in this chapter to configure LAN interfaces supported on Cisco routers and access servers.
This chapter describes the processes for configuring LAN interfaces. It contains these sections:
For examples of configuration tasks, see "LAN Interface Configuration Examples" at the end of this chapter.
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 "Interface Commands" chapter of the Cisco IOS Interface Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.
Cisco supports both 10-Mbps Ethernet and 100-Mbps Fast Ethernet.
Support for the 10-Mbps and 100-Mbps Ethernet interface is supplied on various Ethernet network interface cards or systems.
The Fast Ethernet NP-1FE module, for example, provides the following benefits:
Cisco 7200 series routers support a new I/O controller with an RJ-45 interface. The optional Fast Ethernet port is configurable 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 interface command now supports two options:
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 half-duplex only for a maximum aggregate bandwidth of 200 Mbps.
Refer to the Cisco Product Catalog for specific platform and hardware compatibility information.
Use the show interfaces, show controllers mci, and show controllers cbus EXEC 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 interface fastethernet command to display interface statistics, and use the show controller fastethernet to display the information about the Fast Ethernet controller chip. The output shows statistics, including information about initialization block information, transmit ring, receive ring and errors.
For information on how to configure Fast EtherChannel, refer to the tasks listed in the "Configure Fast EtherChannel" section of this chapter.
Perform the tasks in the following sections to configure features on an Ethernet or Fast Ethernet interface. The first task is required; the remaining tasks are optional.
To specify an Ethernet interface and enter interface configuration mode, use one of the following commands in global configuration mode:
| Command | Purpose |
|---|---|
interface ethernet number | Begin interface configuration. |
interface ethernet slot/port | Begin interface configuration for the Cisco 7200 and 7500 series routers. |
interface ethernet slot/port-adapter/port | Begin interface configuration for Cisco 7500 series routers. |
Begin interface configuration for the Cisco 4000 series with a Fast Ethernet NIM installed. | |
interface fastethernet slot/port | Specify a Fast Ethernet interface and enter interface configuration mode on the Cisco 7200 series routers. |
interface fastethernet slot/port-adapter/port | Specify a Fast Ethernet interface and enter interface configuration mode on the Cisco 7500 series routers. |
Use the show interfaces fastethernet command to display the Fast Ethernet slots and ports. The Fast Ethernet NIM and the FEIP default to half-duplex mode.
Currently, there are three common Ethernet encapsulation methods:
The encapsulation method you use depends upon the routing protocol you are using, the type of Ethernet media connected to the router or access server and the routing or bridging application you configure.
Establish Ethernet encapsulation of IP packets by using one of the following commands in interface configuration mode:
| Command | Purpose |
|---|---|
Select ARPA Ethernet encapsulation. | |
Select SAP Ethernet encapsulation. | |
Select SNAP Ethernet encapsulation. |
For an example of selecting Ethernet encapsulation for IP, see the section "Enable Ethernet Encapsulation Example" at the end of this chapter. See also the chapters describing specific protocols or applications.
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 | Purpose |
|---|---|
|
or no half-duplex | Enable full-duplex on the Fast Ethernet interface of the FEIP2-DSW-2FX. |
For an example to enable full-duplex mode on Fast Ethernet, see the section "Enable Full Duplex Operation Example" at the end of this chapter.
 | Caution To prevent system problems, do not configure both FEIP2-DSW-2FX interfaces for full-duplex operation at the same time. |
You can specify that the Ethernet network interface module (NIM) on the Cisco 4000 series routers use either the default of an AUI and a 15-pin connector, or 10BaseT and an RJ-45 connector. To do so, use one of the following commands in interface configuration mode:
| Command | Purpose |
|---|---|
media-type aui | Select a 15-pin Ethernet connector. |
Select an RJ-45 Ethernet connector. |
| Command | Purpose |
|---|---|
media-type mii | Select an MII Ethernet connector. |
Select an RJ-45 Ethernet connector for the FEIP2-DSW-2TX or an SC connector for the FEIP2-DSW-2FX. |
On a Cisco 4000 series or Cisco 4500 series routers, you can extend the twisted-pair 10BaseT capability beyond the standard 100 meters by reducing the squelch (signal cutoff time). This feature applies only to the LANCE controller 10BaseT interfaces. LANCE is the AMD controller chip for the Cisco 4000 and Cisco 4500 Ethernet interface.
To reduce squelch, use the first command that follows in interface configuration mode. You can later restore the squelch by using the second command.
| Command | Purpose |
|---|---|
Reduce the squelch. | |
Return squelch to normal. |
You must configure the Fast Ethernet 100BaseT 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 100BaseT and 10BaseT routers, hubs, and switches.
To configure the interface, use the following commands beginning in privileged EXEC mode:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| configure terminal | Enter global configuration mode. | ||
| interface fastethernet number
| Enter Fast Ethernet interface configuration mode. | ||
| ip address address subnet-mask | Assign an IP address and subnet mask to the interface. | ||
| speed {10 | 100 | auto} | Assign a speed to the interface. The default is 100 Mbps.1 For relationship between duplex and speed command options, see Table 3. | ||
| duplex {full | half | auto} | Set up the duplex configuration on the Fast Ethernet interface. The default is half duplex.1 For relationship between duplex and speed command options, see Table 3. |
| 1The auto option automatically negotiates the speed based on the speed and the peer router, hub, or switch media. |
To use the auto-negotiation capability (that is, to detect speed and duplex modes automatically), you must set both speed and duplex to auto. Setting the speed to auto negotiates speed only, and setting duplex to auto negotiates duplex only. Table 3 describes the access server's performance 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.
| Duplex Command | Speed Command | Resulting System Actions |
|---|---|---|
duplex auto | speed auto | Auto negotiates both speed and duplex modes. |
duplex auto | speed 100 or speed 10 | Auto negotiates both speed and duplex modes. |
duplex half or duplex full | speed auto | Auto negotiates both speed and duplex modes. |
duplex half | speed 10 | Forces 10 Mbps and half duplex. |
duplex full | speed 10 | Forces 10 Mbps and full duplex. |
duplex half | speed 100 | Forces 100 Mbps and half duplex. |
duplex full | speed 100 | Forces 100 Mbps and full duplex. |
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 (10BaseT) and Fast Ethernet (100BaseTX) 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 UTP cables.
The PA-12E/2FE port adapter off-loads 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).
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-config command to determine if a PA-12E/2FE interface is autosensing and autonegotiating the proper transmission mode with an attached device. Use the full-duplex and the half-duplex commands to change the transmission mode of a PA-12E/2FE interface. After changing the transmission mode, use the show interfaces command to verify the interface's transmission mode.
To configure the PA-12E/2FE port adapter, perform the tasks in the following sections (the first task is required, all other tasks are optional):
For information on other commands that can be used to configure a PA-12E/2FE port adapter, refer to the "Interfaces Commands" chapter in the Cisco IOS Interface Command Reference. For information on bridging, refer to the "Configuring Transparent Bridging" chapter in the Bridging and IBM Networking Configuration Guide.
For PA-12E/2FE port adapter configuration examples, see "PA-12E/2FE Port Configuration Examples" section later in this chapter.
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 you plan to route on the interface. For complete descriptions of configuration commands and the configuration options available, refer to the Cisco IOS Release 12.0 configuration guides.
To configure the interfaces on the PA-12E/2FE port adapter, use the following commands in global configuration mode:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| bridge bridge-group protocol ieee | Specify 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. | ||
| interface fastethernet slot/port (ports 0 and 1) interface ethernet slot/port (ports 2 through 13) | |||
| bridge-group bridge-group | Assign a bridge group to the interface. | ||
| cut-through [receive | transmit] | Optionally, configure the interface for cut-through switching technology. The default is store-and-forward. | ||
| full-duplex | Optionally, if an attached device does not support autosensing or autonegotiation, configure the transmission mode for full-duplex. The default is half-duplex. | ||
| no shutdown | Change the shutdown state to up. | ||
| exit | |||
|
| |||
| copy system:running-config nvram:startup-config | Save the new configuration to memory. |
To enable integrated routing and bridging on the bridge groups, use the following commands beginning in global configuration mode:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| bridge irb | Enable integrated routing and bridging. | ||
| interface bvi bridge-group | |||
| ip address address mask | Assign an IP address and subnet mask to the bridge-group virtual interface. | ||
| no shutdown | Change the shutdown state to up. | ||
| exit | |||
|
| |||
| bridge bridge-group route protocol | Specify the protocol for each bridge group. | ||
| exit | Exit configuration mode. | ||
| copy system:running-config nvram:startup-config | Save the new configuration to memory. |
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 | Purpose |
|---|---|
show version | Display the configuration of the system hardware, the software version, the names and sources of configuration files, and the boot image. |
show controllers | Display all current port adapters and their interfaces |
show interface fastethernet slot/port or show interface ethernet slot/port | Verify the interfaces have the correct slot number and that the interface and line protocol are in the correct state. |
show bridge group | Verify all bridge groups and their interfaces. |
show interface ethernet slot/port irb or show interface fastethernet slot/port irb | Verify the correct routed protocol is configured for each interface. |
show protocols | Display the protocols configured for the entire system and specific interfaces. |
show pas eswitch addresses fastethernet slot/port or show pas eswitch addresses ethernet slot/port | Display the Layer 2 learned addresses for each interface. |
more system:running-config | Display the running configuration file. |
more nvram:startup-config | Display the configuration stored in NVRAM. |
The 12E/2FE VLAN Configuration WebTool, shown in Figure 3, 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:
You can access the 12E/2FE VLAN Configuration WebTool from your router's home page. For complete procedures on how to use the VLAN Configuration WebTool, refer to the PA-12E/2FE Ethernet Switch 10BASE-T and 100BASE-TX Port Adapter Installation and Configuration that accompanies the hardware.
All Cisco routers running Cisco IOS Release 11.0 or later have a home page. If your router has an installed PA- 12E/2FE port adapter, you can access the 12E/2FE VLAN Configuration WebTool from the router's home page.
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 unshielded twisted-pair (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.
| Step | Command | Purpose | ||
|---|---|---|---|---|
| interface vg-anylan slot/port-adapter/port (Cisco 7500) or interface vg-anylan slot/port (Cisco 7200) | Specify a 100VG-AnyLAN interface and enter interface configuration. | ||
| ip address ip-address mask | Specify the IP address and subnet mask to the interface. | ||
| frame-type ethernet | Configure the frame type. Currently, only Ethernet frames are supported. The frame type defaults to Ethernet. |
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.
The Fast EtherChannel feature allows multiple Fast Ethernet point-to-point links to be bundled into one logical link to provide bidirectional bandwidth of up to 800 Mbps. Fast EtherChannel builds on standards-based 802.3 full-duplex Fast Ethernet to provide fault-tolerant, high-speed links between switches, routers, and servers. This feature can be configured between Cisco 7500 series routers and Cisco 7000 series routers with the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI) or between a Cisco 7500 series router or a Cisco 7000 series router with the RSP7000 and RSP700CI and a Catalyst 5000 switch.
Fast EtherChannel provides higher bidirectional bandwidth, redundancy, and load sharing. Up to four Fast Ethernet interfaces can be bundled in a port-channel, and the router or switch can support up to four port-channels. The Fast EtherChannel feature is capable of load balancing traffic across the Fast Ethernet links. Unicast, broadcast, and multicast traffic is distributed across the links providing higher performance and redundant parallel paths. In the event of a link failure, traffic is redirected to remaining links within the Fast EtherChannel without user intervention.
In this release of the Fast EtherChannel feature, IP traffic is distributed over the port-channel interface while traffic from other routing protocols is sent over a single link. Bridged traffic is distributed based on the Layer 3 information in the packet. If the Layer 3 information does not exist in the packet, the traffic is sent over the first link.
Fast EtherChannel supports all features currently supported on the Fast Ethernet interface. You must configure these features on the port-channel interface rather than on the individual Fast Ethernet interfaces. Fast EtherChannel connections are fully compatible with Cisco IOS virtual LAN (VLAN) and routing technologies. The Inter-Switch Link (ISL) VLAN trunking protocol can carry multiple VLANs across a Fast EtherChannel, and routers attached to Fast EtherChannel links can provide full multiprotocol routing with support for host standby using Host Standby Router Protocol (HSRP).
The port-channel (consisting of up to four Fast Ethernet interfaces) is treated as a single interface. Port-channel is used in the Cisco IOS software to maintain compatibility with existing commands on the Catalyst 5000 switch. You create the Fast EtherChannel by using the interface port-channel interface configuration command. You can assign up to four Fast Ethernet interfaces to a port-channel by using the channel-group interface configuration command.
Fast Etherchannel also supports the following two features:
Support for host standby using Host Standby Router Protocol (HSRP)
For more information about configuring HSRP, refer to the "Configuring IP Services" chapter in the Network Protocols Configuration Guide, Part 1.
Support for Cisco Express Forwarding (CEF) and distributed CEF (dCEF)
For more information about configuring CEF, refer to the "Cisco Express Forwarding" chapter in the Cisco IOS Switching Services Configuration Guide.
For information on how to configure Ethernet or Fast Ethernet, refer to the tasks listed in the "Configure an Ethernet or Fast Ethernet Interface" section of this chapter.
Perform the tasks in the following sections to configure Fast EtherChannel. To configure Fast EtherChannel, perform the following required steps:
1. Create a port-channel interface and assign an IP address.
2. Assign the Fast Ethernet interfaces (up to four) to the port-channel interface.
For information on other configuration tasks for the Fast EtherChannel, refer to the "Configure an Ethernet or Fast Ethernet Interface" section in this chapter.
For information on other commands that can be used by the Fast EtherChannel, refer to the Cisco IOS Release 11.1 configuration guides.
| Step | Command | Purpose | ||
|---|---|---|---|---|
| interface port-channel channel-number | Create the port-channel interface and enter interface configuration mode. The channel-number can be 1 to 4. | ||
| ip address ip-address mask | Assign an IP address and subnet mask to the Fast EtherChannel. | ||
| mac-address ieee-address | Optionally, assign a static MAC address to the Fast EtherChannel. | ||
| end | Optionally, enable other supported interface commands to meet your needs and exit when you have finished. | ||
| show interface port-channel | Verify the configuration. |
| Caution With Release 11.1(20)CC, Fast EtherChannel supports CEF/dCEF. We recommend that you clear all explicit ip route-cache distributed commands from the Fast Ethernet interfaces before enabling dCEF on the port-channel interface. Doing this gives the port-channel interface proper control of its physical Fast Ethernet links. When you enable CEF/dCEF globally, all interfaces that support CEF/dCEF are enabled. When CEF/dCEF is enabled on the port-channel interface, it is automatically enabled on each of the Fast Ethernet interfaces in the channel group. However, if you have previously disabled CEF/dCEF on the Fast Ethernet interface, CEF/dCEF is not automatically enabled. In this case, you must enable CEF/dCEF on the Fast Ethernet interface. |
| Step | Command | Purpose | ||
|---|---|---|---|---|
| interface fastethernet slot/port-adapter/port | Create or modify an existing Fast Ethernet interface and enter interface configuration mode. | ||
| no ip address | If the Fast Ethernet interface already exists and has an IP address assigned, disable the IP address before performing the next step. | ||
| channel-group channel-number | Assign the Fast Ethernet interfaces to the Fast EtherChannel. The channel number is the same as the channel number you specified when you created the port-channel interface. | ||
| exit | Exit interface configuration mode and repeat through to add up to four Fast Ethernet interfaces to the Fast EtherChannel. | ||
| end | Exit when you have finished. | ||
| show interface port-channel | Verify the configuration. |
| Caution The port-channel interface is the routed interface. Do not enable Layer 3 addresses on the physical Fast Ethernet interfaces. Do not assign bridge groups on the physical Fast Ethernet interfaces because it creates loops. Also, you must disable spanning tree. |
| Step | Command | Purpose | ||
|---|---|---|---|---|
| interface fastethernet slot/port-adapter/port | Specify the Fast Ethernet interface and enter interface configuration mode. | ||
| Remove the Fast Ethernet interface from the channel group. | |||
| end | Exit when you have finished. |
The Cisco IOS software automatically removes a Fast Ethernet interface from the Fast EtherChannel if the interface goes down, and the software automatically adds the Fast Ethernet interface to the Fast EtherChannel when the interface is back up.
Currently, Fast EtherChannel relies on keepalives to detect whether the line protocol is up or down. Keepalives are enabled by default on the Fast Ethernet interfaces. If the line protocol on the interface goes down because it did not receive a keepalive signal, the Fast EtherChannel detects that the line protocol is down and removes the interface from the Fast EtherChannel. However, if the line protocol remains up because keepalives are disabled on the Fast Ethernet interface, the Fast EtherChannel cannot detect this link failure (other than a cable disconnect) and does not remove the interface from the Fast EtherChannel even if the line protocol goes down. This can result in unpredictable behavior. The implementation of the Port Aggregation Protocol (PAgP) in a subsequent release of this feature will remove the dependency on keepalives.
See the "LAN Interface Configuration Examples" section, later in this document, for configuration examples.
You can monitor the status of the Fast EtherChannel interface by using the show interfaces port-channel EXEC command.
The Fiber Distributed Data Interface (FDDI) is an ANSI-defined standard for timed 100-Mbps token passing over fiber-optic cable. FDDI is not supported on access servers.
An FDDI network consists of two counter 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 between active stations of two kilometers when interconnecting them with multimode fiber or ten kilometers when interconnected via single mode fiber, both of which are supported by our FDDI interface controllers. The FDDI frame can contain a minimum of 17 bytes and a maximum of 4500 bytes. Our implementation of FDDI supports Station Management (SMT) Version 7.3 of the X3T9.5 FDDI specification, offering a single MAC dual-attach interface that supports the fault-recovery methods of the 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 (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 Bridging and IBM Networking Configuration Guide.
Source-route bridging (SRB) is supported over Fiber Distributed Data Interface (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:
For information about configuring SRB over FDDI, refer to the "Configure Source-Route Bridging" chapter of the Cisco IOS Bridging and IBM Networking Configuration Guide.
Connection management (CMT) is an 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 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 PCM state machine, 08 indicates that the port type is A, the port compatibility is set, and the LCT duration requested is short. The receive signal bits are 20C, which indicate the neighbor type is B, port compatibility is set, 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 ten 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.
The CFM state is through A in the sample output, which means this interface's Phy-A 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. Since 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.
Perform the tasks in the following sections to configure an FDDI interface. The first task is required; the remaining tasks are optional.
To specify an FDDI interface and enter interface configuration mode, use one of the following commands in global configuration mode:
| Command | Purpose |
|---|---|
interface fddi number | Begin interface configuration |
interface fddi slot/port | Begin interface configuration for the Cisco 7200 or Cisco 7500 series routers. |
Cisco FDDI by default 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:
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 | Purpose |
|---|---|
Specify the encapsulation method for the FIP. |
When you are doing translational bridging, you have to route routable protocols and use translational bridging for the rest (such as LAT).
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.
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 | Purpose |
|---|---|
|
or no half-duplex | Enable full-duplex on the FDDI interface of the PA-F/FD-SM and PA-F/FD-MM port adapter. |
| Command | Purpose |
|---|---|
Set the FDDI token rotation time. |
The FDDI standard restricts the allowed time to be 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.
You can set the transmission timer to recover from a transient ring error by using the following command in interface configuration mode:
| Command | Purpose |
|---|---|
Set the FDDI valid 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 | Purpose |
|---|---|
Set the FDDI control transmission 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 | Purpose |
|---|---|
fddi c-min microseconds | Set the C-Min timer on the PCM. |
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 | Purpose |
|---|---|
fddi tb-min milliseconds | Set TB-Min timer in the PCM. |
You can change the FDDI timeout timer in the PCM from its default value of 100 milliseconds. To do so, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
fddi t-out milliseconds | Set the timeout timer in the PCM. |
You can disable and reenable SMT frame processing for diagnostic purposes. To do so, use one of the following commands in interface configuration mode:
| Command | Purpose |
|---|---|
no fddi smt-frames | Disable SMT frame processing. |
Enable SMT frame processing. |
| Command | Purpose |
|---|---|
Enable duplicate address checking capability. |
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 | Purpose |
|---|---|
Set the FDDI bit control. |
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 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:
To disable the CMT microcode, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
no fddi if-cmt | Disable the FCIT CMT functions. |
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 | Purpose |
|---|---|
Start CMT processes on FDDI ring. | |
Stop CMT processes on FDDI ring. |
Do not use either of the preceding commands during normal operation of FDDI; they are used during interoperability tests.
The FDDI interface is able to transmit multiple frames per token on a Cisco 4000, Cisco 4500, and a Cisco 4700 series routers, instead of 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.
| Step | Command | Purpose | ||
|---|---|---|---|---|
| configure terminal | Enter global configuration mode. | ||
| interface fddi0 | Enter interface configuration mode. | ||
| fddi ? | Show fddi command options. | ||
| fddi frames-per-token ? | Show fddi frames-per-token command options. | ||
| fddi frames-per-token number | Specify the maximum number of frames to be transmitted per token capture. |
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 you are configuring gets bursts of messages arriving faster than the router can process them. To set the number of frames, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
Set SMT message queue size. |
The FCI card preallocates three buffers to handle bursty FDDI traffic (for example, NFS bursty traffic). You can change the number of preallocated buffers by using the following command in interface configuration mode:
| Command | Purpose |
|---|---|
Preallocate buffers to handle bursty FDDI traffic. |
The Cisco 2500 series routers 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 10BaseT physical network configuration. The router models with hub ports and their configurations are as follows:
We provide SNMP management of the Ethernet hub as specified in RFC 1516.
To configure hub functionality on an Ethernet interface, perform the tasks in the following sections. The first task is required; the remaining are optional.
For configuration examples, see the "Hub Configuration Examples" section at the end of this chapter.
To enable a hub port, use the following commands in global configuration mode:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| hub ethernet number port [end-port] | Specify the hub number and the hub port (or range of hub ports) and enter hub configuration mode. | ||
| Enable the hub ports. |
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 | Purpose |
|---|---|
Disable automatic receiver polarity reversal. |
To reenable automatic receiver polarity reversal on a per-port basis, use the following command in hub configuration mode:
| Command | Purpose |
|---|---|
auto-polarity | Reenable automatic receiver polarity reversal. |
The link test function applies to Ethernet hub ports only. The Ethernet ports implement the link test function as specified in the 802.3 10BaseT 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 will enter link fail state and be disabled from transmit and receive functions. The hub port will be reenabled 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 10BaseT twisted-pair networks that do not implement the link test function, the hub's link test receive function can be disabled on a per-port basis. To do so, use the following command in hub configuration mode:
| Command | Purpose |
|---|---|
Disable the link test function. |
To reenable the link test function on a hub port connected to an Ethernet interface, use the following command in hub configuration mode:
| Command | Purpose |
|---|---|
link-test | Enable the link test function. |
To enable source address control on a per-port basis, use the following command in hub configuration mode:
| Command | Purpose |
|---|---|
source-address [mac-address] | Enable source address control. |
If you omit the optional MAC address, the hub remembers the first MAC address it receives on the selected port, and allows only packets from the learned MAC address.
See the examples of establishing source address control at the end of this chapter in "Hub Configuration Examples."
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:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| hub ethernet number port [end-port] | Specify the hub number and the hub port (or range of hub ports) and enter hub configuration mode. | ||
| snmp trap illegal-address | Enable the router to issue an SNMP trap when an illegal MAC address is detected on the hub port. |
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 section "Hub Configuration Examples" at the end of this chapter.
The Cisco 1001 and Cisco 1002 LAN Extenders are two-port chassis that connect a remote Ethernet LAN to a core router at a central site (see Figure 4). The LAN Extender is intended for small networks at remote sites. Overview information for LAN extender interfaces is provided in these sections:
The remote site can have one Ethernet network. The core router can be a Cisco 2500 series, Cisco 4000 series, Cisco 4500 series, Cisco 4700 series, Cisco 7500 series, or AGS+ router running Cisco IOS Release 10.2(2) or later, which support the LAN Extender host software.
Figure 4 shows the connection between the LAN Extender and the core router via a short leased serial line, typically a 56-kbps or 64-kbps line. However, the connection can also be via T1 or E1 lines.
Figure 5 is an expanded view of Figure 4 that shows all the components of the LAN Extender connection to a core router. On the left is the core router, which is connected to the LAN Extender as well as to other networks. In the core router, you configure a LAN Extender interface, which is a logical interface that connects the core router to the LAN Extender chassis. In the core router, you also configure a serial interface, which is the physical interface that connects the core router to the LAN Extender. You then bind, or associate, the LAN Extender interface to the physical serial interface.
Figure 5 shows the actual physical connection between the core router and the LAN Extender. The serial interface on the core router is connected by a leased serial line to a serial port on the LAN Extender. This creates a virtual Ethernet connection, which is analogous to having inserted an Ethernet interface processor into the core router.
Although there is a physical connection between the core router and the LAN Extender, what you actually manage is a remote Ethernet LAN. Figure 6 shows the connection you are managing, which is a LAN Extender interface connected to an Ethernet network. The virtual Ethernet connection (the serial interface and LAN Extender) has been removed from the figure, and points A and B, which in Figure 5 were separated by the virtual Ethernet connection, are now adjacent. All LAN Extender interface configuration tasks described in this chapter apply to the interface configuration shown in Figure 6.
To install a LAN Extender at a remote site, refer to the Cisco 1000 Series Hardware Installation publication.
After the LAN Extender has been installed at the remote site, you need to obtain its MAC address. Each LAN Extender is preconfigured with a permanent (burned-in) MAC address. The address is assigned at the factory; you cannot change it. The MAC address is printed on the LAN Extender's packing box. (If necessary, you can also display the MAC address with the debug ppp negotiation command.) The first three octets of the MAC address (the vendor code) are always the hexadecimal digits 00.00.0C.
You can upgrade software for the LAN Extender on the host router with a TFTP server that is local to the host router.
The LAN Extender and core router communicate using the Point-to-Point Protocol (PPP). Before you can configure the LAN Extender from the core router, you must first enable PPP encapsulation on the serial interface to which the LAN Extender is connected.
You configure the LAN Extender from the core router--either a Cisco 4000 series or Cisco 7000 series router--as if it were simply a network interface board. The LAN Extender cannot be managed or configured from the remote Ethernet LAN or via a Telnet session.
To configure the LAN Extender, you configure a logical LAN Extender interface on the core router and assign the MAC address from your LAN Extender to that interface. Subsequently, during the PPP negotiation on the serial line, the LAN Extender sends its preconfigured MAC address to the core router. The core router then searches for an available (preconfigured) LAN Extender interface, seeking one to which you have already assigned that MAC address. If the core router finds a match, it binds, or associates, that LAN Extender interface to the serial line on which that MAC address was negotiated. At this point, the LAN Extender interface is created and is operational. If the MAC address does not match one that is configured, the connection request is rejected. Figure 7 illustrates this binding process.
To configure a LAN Extender interface, perform the tasks described in the following sections. The first task is required; the remainder are optional.
To monitor the LAN Extender interface, see the section "Monitor and Maintain the Interface" in the "Interface Configuration" chapter. For configuration examples, see the "Enable a LAN Extender Interface Example" and the "LAN Extender Interface Access List Examples" sections at the end of this chapter.
To configure and create a LAN Extender interface, you configure the LAN Extender interface itself and the serial interface to which the LAN Extender is physically connected. The order in which you configure these two interface interfaces does not matter. However, you must first configure both interfaces in order for the LAN Extender interface to bind (associate) to the serial interface.
To create and configure a LAN Extender interface, use the following commands starting in interface configuration mode:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| interface lex number | Configure a LAN Extender interface in global configuration mode and enter interface configuration mode. | ||
| Assign the burned-in MAC address from your LAN Extender to the LAN Extender interface. | |||
| Assign a protocol address to the LAN Extender interface. | |||
| exit | Return to global configuration mode. | ||
| Configure a serial interface in global configuration mode and enter interface configuration mode. | |||
| Enable PPP encapsulation on the serial interface in interface configuration mode. | |||
| Ctrl-Z | Exit interface configuration mode. | ||
| Save the configuration to memory. |
Note that there is no correlation between the number of the serial interface and the number of the LAN Extender interface. These interfaces can have the same or different numbers.
You can configure specific administrative filters that filter frames based on their source MAC address. The LAN Extender forwards packets between a remote LAN and a core router. It examines frames and transmits them through the internetwork according to the destination address, and it does not forward a frame back to its originating network segment.
You define filters on the LAN Extender interface in order to control which packets from the remote Ethernet LAN are permitted to pass to the core router. (See Figure 8.) These filters are applied only on traffic passing from the remote LAN to the core router. Filtering on the LAN Extender interface is actually performed in the LAN Extender, not on the core router. This means that the filtering is done using the LAN Extender CPU, thus off-loading the function from the core router. This process also saves bandwidth on the WAN, because only the desired packets are forwarded from the LAN Extender to the core router. Whenever possible, you should perform packet filtering on the LAN Extender.
You can also define filters on the core router to control which packets from the LAN Extender interface are permitted to pass to other interfaces on the core router. (See Figure 9.) You do this using the standard filters available on the router. This means that all packets are sent across the WAN before being filtered and that the filtering is done using the core router's CPU.
The major reason to create access lists on a LAN Extender interface is to prevent traffic that is local to the remote Ethernet LAN from traversing the WAN and reaching the core router. You can filter packets by MAC address, including vendor code, and by Ethernet type code. To define filters on the LAN Extender interface, perform the tasks described in one or both of the following sections:
When defining access lists, keep the following points in mind:
You can create access lists to administratively filter MAC addresses. These access lists can filter groups of MAC addresses, including those with particular vendor codes. There is no noticeable performance loss in using these access lists, and the lists can be of indefinite length.
You can filter groups of MAC addresses with particular vendor codes by creating a vendor code access list and then by applying an access list to an interface.
To create a vendor code access list, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
access-list access-list-number {permit | deny} address mask | Create an access list to filter frames by canonical (Ethernet-ordered) MAC address. |
Once you have defined an access list to filter by a particular vendor code, you can assign this list to a particular LAN Extender interface so that the interface will then filter based on the MAC source addresses of packets received on that LAN Extender interface. To apply the access list to an interface, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
Assign an access list to an interface for filtering by MAC source addresses. |
For an example of creating an access list and applying it to a LAN Extender interface, see the section "LAN Extender Interface Access List Examples" in the section "LAN Interface Configuration Examples" at the end of this chapter.
You can filter by creating a type-code access list and applying it to a LAN Extender interface.
The LAN Extender interface can filter only on bytes 13 and 14 of the Ethernet frame. In Ethernet packets, these two bytes are the type field. For a list of Ethernet type codes, refer to the "Ethernet Type Codes" appendix in the Bridging and IBM Networking Command Reference. In 802.3 packets, these two bytes are the length field.
You can filter by protocol type by creating a protocol-type access list and then applying the access list to an interface.
To create a protocol-type access list, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
access-list access-list-number {permit | deny} type-code wild-mask | Create an access list to filter frames by protocol type. |
To apply an access list to an interface, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
Add a filter for Ethernet- and SNAP-encapsulated packets on input. |
For an example of creating an access list and applying it to a LAN Extender interface, see the section "LAN Extender Interface Access List Examples" in the section "LAN Interface Configuration Examples" at the end of this chapter.
Priority output queuing is an optimization mechanism that allows you to set priorities on the type of traffic passing through the network. Packets are classified according to various criteria, including protocol and subprotocol type. Packets are then queued on one of four output queues. For more information about priority queuing, refer to the "Managing System Performance" chapter.
To control priority queuing on a LAN Extender interface, perform the following tasks:
To establish queuing priorities based on the protocol type, use one of the following commands in global configuration mode:
| Command | Purpose |
|---|---|
priority-list list protocol protocol {high | medium | normal | low} |
You then assign a priority list to an interface. You can assign only one list per interface. To assign a priority list to a LAN Extender interface, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
Each time the core router sends a command to the LAN Extender, the LAN Extender responds with an acknowledgment. The core router waits for the acknowledgment for a predetermined amount of time. If it does not receive an acknowledgment in this time period, the core router resends the command.
By default, the core router waits 2 seconds for an acknowledgment from the LAN Extender. You might want to change this interval if your connection to the LAN Extender requires a different amount time. To determine whether commands to the LAN Extender are timing out, use the debug lex rcmd privileged EXEC command. To change this interval, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
Set the amount of time that the core router waits to receive an acknowledgment from the LAN Extender. |
By default, the core router sends each command ten times before giving up. The core router displays an error message when it gives up sending commands to the LAN Extender. To change this default, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
Set the number of times the core router sends a command to the LAN Extender before giving up. |
From the core router, you can shut down the LAN Extender's Ethernet interface. This stops traffic on the remote Ethernet LAN from reaching the core router, but leaves the LAN Extender interface that you created intact.
| Command | Purpose |
|---|---|
Shut down the LAN Extender's Ethernet interface. |
To restart the LAN Extender's Ethernet interface, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
no shutdown |
| Command | Purpose |
|---|---|
Halt operation of the LAN Extender and have it perform a cold restart. | |
clear controller lex slot/port [prom] | Halt operation of the LAN Extender on a Cisco 7000 series routers. |
When the LAN Extender is powered on, it runs the software image that is shipped with the unit. You can download a new software image from Flash memory on the core router or from a TFTP server or from Flash memory on the core router to the LAN Extender.
| Command | Purpose |
|---|---|
copy tftp lex number | Download a software image from a TFTP server. |
copy flash lex number | Download a software image from Flash memory. |
The primary means of troubleshooting the LAN Extender is by using the light emitting diodes (LEDs) that are present on the chassis. This section will help you assist the remote user at the LAN Extender site who can observe the LEDs.
The Cisco 1000 series LAN Extender uses multiple LEDs to indicate its current operating condition. By observing the LEDs, any fault conditions that the unit is encountering can be observed. The system LEDs are located on the front panel of your LAN Extender (see Figure 10).
When there is a problem with the LAN Extender, a user at the remote site should contact you and report the condition of the LEDs located on the front panel of the LAN Extender. You can then use this information to diagnose or verify the operation of the system. Table 4 explains the LEDs.
| LED | Condition | Meaning |
POWER | On Steady | The POWER LED indicates that 12 V DC is being supplied to the LAN Extender. |
| Off | If the POWER LED is off, power is not reaching the unit. Verify that the power supply is plugged into the wall receptacle, and that the cable from the power supply to the unit is connected. |
SYSTEM | On Steady | The SYSTEM OK LED is lit when the unit passes the power on diagnostics. This indicates proper operation. |
| Blinking | The system will blink while running its startup diagnostics and then will go to a steady on position. Blinking after the start-up diagnostics indicates that a system error has been encountered. Contact your system administrator who will have you disconnect and then reconnect the power to recycle your LAN Extender. If the blinking continues, check your WAN connection and the RX and TX LEDs. |
| Off | An error condition has occurred. Contact your system administrator who will ask you to disconnect the power cord and then reconnect it to re-establish power to your LAN Extender. |
SERIAL TX and SERIAL RX | Flicker | The serial line is transmitting and receiving packets normally. |
| Blinking | A line fault has been detected. The LEDs will go on for several seconds and then they will blink a certain number of times to indicate a particular error. The LEDs will blink at a rate of one to two blinks per second. The following are the errors that can be encountered: 1 blink = The serial line is down. 2 blinks = No clock signal was received. 3 blinks = An excessive number of cyclic redundancy check (CRC) errors has been received. 4 blinks = The line is noisy. 5 blinks = A loopback condition has occurred. 6 blinks = The PPP link has failed. Contact your system administrator. |
LAN TX and LAN RX | Flicker | The Ethernet LAN connection is transmitting and receiving data normally. |
COLLISION |
| Data collisions are being detected. |
LINK | Steady | This indicates the serial link is up and functioning. |
For more complete network troubleshooting information, refer to the Troubleshooting Internetworking Systems publication.
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," by K. McCloghrie, R. Fox, and E. Decker, May 1991. 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 TRIP.
Use the show interfaces, show controllers token, and show controllers cbus EXEC commands to display the Token Ring numbers. These commands provide a report for each ring that Cisco IOS software supports.
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 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:
For information about configuring SRB over FDDI, refer to the "Configure Source-Route Bridging" chapter of the Bridging and IBM Networking Configuration Guide.
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).
Perform the tasks in the following sections to configure a Token Ring interface. The first task is required; the remaining tasks are optional.
To specify a Token Ring interface and enter interface configuration mode, use one of the following commands in global configuration mode:
| Command | Purpose |
|---|---|
interface tokenring number | Begin interface configuration. |
interface tokenring slot/port | Begin interface configuration for the Cisco 7200 or Cisco 7500 series routers. |
interface tokenring slot/port-adapter/port | Begin interface configuration for the Cisco 7500 series routers. |
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 |
|---|---|
early-token-release | Enable early token release. |
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 |
|---|---|
Enable PCbus LAN management. |
To enable an interface to operate as a concentrator port, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
port | Specify concentrator port operation. |
To monitor the Token Ring Concentrator Port, use one or more of the following commands in EXEC mode:
| Command | Purpose |
|---|---|
show controllers token | Display internal state information about the Token Ring interfaces in the system. |
show interface token | Provide high-level statistics for a particular interface. |
This section provides examples to illustrate configuration tasks described in this chapter. These examples are included:
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 routers:
interface ethernet 4/2 encapsulation arpa
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 1.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
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 ieeeRouter(config)#int fastethernet 3/0Router(config-if)#bridge-group 10Router(config-if)#cut-throughRouter(config-if)#no shutdown Router(config-if)# exit Router(config)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet3/0, changed
state to up %LINK-3-UPDOWN: Interface FastEthernet3/0, changed state to upRouter(config)#int fastethernet 3/1Router(config-if)#bridge-group 10Router(config-if)#cut-throughRouter(config-if)#no shutdown Router(config-if)# exit Router(config)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet3/1, changed
state to up %LINK-3-UPDOWN: Interface FastEthernet3/1, changed state to upRouter(config)#int ethernet 3/2Router(config-if)#bridge-group 20Router(config-if)#cut-throughRouter(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 upRouter(config)#int ethernet 3/3Router(config-if)#bridge-group 20Router(config-if)#cut-throughRouter(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 1.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#
configure terminal interface vg-anylan 1/0/0 ip address 1.1.1.10 255.255.255.0 no shutdown exit exit
Figure 11 shows four point-to-point Fast Ethernet interfaces that are aggregated into a single Fast EtherChannel interface.
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 1.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.
interface Port-channel1 ip address 1.1.1.10 255.255.255.0 ! interface Port-channel1.1 encapsulation isl 100 ! interface FastEthernet0/0/0 mac-address 00e0.1476.7600 no ip address channel-group 1 ! interface FastEthernet0/1/0 mac-address 00e0.1476.7600 no ip address channel-group 1 ! interface FastEthernet1/0/0 mac-address 00e0.1476.7600 no ip address channel-group 1 ! interface FastEthernet1/1/0 mac-address 00e0.1476.7600 no ip address channel-group 1
The following example shows how to configure the FDDI interface to transmit four frames per token capture:
! Enter global configuration mode4700#configure terminal ! Enter interface configuration mode4700(config)#interface fddi0 ! Show the fddi command options4700(config-if)#fddi ?encapsulate Enable FDDI Encapsulation bridgingframes-per-token Maximum frames to transmit per service opportunitytl-min-time Line state transmission timetoken-rotation-time Set the token rotation timervalid-transmission-time Set transmission valid timer! Show fddi frames-per-token command options4700(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 token4700(config-if)#fddi frames-per-token 4
The following sections provide examples of hub configuration:
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
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
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
The following example specifies the gateway IP address and enables an SNMP trap to be issued to the host 172.69.40.51 when a MAC address violation is detected on hub ports 2, 3, or 4. It specifies that interface Ethernet 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.69.40.51 public hub ethernet 0 2 4 snmp trap illegal-address
The following simple example configures and creates a LAN Extender interface. In this example, the MAC address of the LAN Extender is 0000.0c00.0001.
interface serial 4 encapsulation ppp interface lex 0 lex burned-in-address 0000.0c00.0001 ip address 131.108.172.21 255.255.255.0
This section provides these examples of LAN extender interface configuration:
The following is an example that controls which traffic from Macintosh computers on the remote Ethernet LAN reaches the core router:
access-list 710 permit 0800.0298.0000 0000.0000.FFFF access-list 710 deny 0800.0276.2917 0000.0000.0000 access-list 710 permit 0800.0000.0000 0000.FFFF.FFFF interface lex 0 lex input-address-list 710
The first line of this access list permits traffic from any Macintosh whose MAC address starts with 0800.0298. The remaining two octets in the MAC address can be any value because the mask for these octets is FFFF ("don't care" bits).
The second line specifically rejects all traffic originating from a Macintosh with the MAC address of 0800.0276.2917. Note that none of the mask bits are "don't care" bits.
The third line specifically permits all traffic from other Macintoshes whose MAC addresses start with 0800. Note that in the mask, the "don't care" bits are the rest of the address.
At the end of the list is an implicit "deny everything" entry, meaning that any address that does not match an address or address group on the list is rejected.
Using the same configuration as in the previous section, you could allow only the Macintosh traffic by Ethernet type code with the following access list:
access-list 220 permit 0x809B 0x0000 interface lex 0 lex input-type-list 220
This access list permits only those messages whose protocol number matches the masked protocol number in the first line. The implicit last entry in the list is a "deny everything" entry.
Posted: Wed Aug 16 20:18:45 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.