Avici Systems Inc.


Field Replacement Procedure

QSR 2-Port Gigabit Ethernet Module Installation & Configuration

03482-03 Rev. BA

This procedure is for replacing a Quarter-rack Scalable Router (QSR) 2-Port Gigabit Ethernet module.

Before beginning this procedure, carefully inspect the package to ensure no damage occurred during shipping or delivery. If you suspect any possible damage to any field replacement unit, contact Customer Support.

For easy and quick reference, this Field Replacement Procedure (FRP) is organized as follows:

Support Services
Tools
Antistatic Precautions
QSR Module Population Rules
Preparing to Remove a Router Module
Removing Fabric Filler or Filler Modules
Installing Router Modules
Configuring the 2-Port Gigabit Ethernet Module
Configuring the Interfaces
LEDs

Support Services

Avici offers three ways to obtain information on customer service and training:

Tools

Antistatic Precautions

This section describes the procedure to prevent damage to the QSR system from static electricity.

CAUTION (1) When handling router modules, wear a grounded wrist strap or equivalent antistatic protection to prevent damage to electronic parts.

Use these precautions to prevent damage from static electricity:

Figure 1. QSR ESD Jack Location (Front)

QSR Module Population Rules

Each QSR chassis provides a single chassis with 10 slots to house route controller and router modules. The chassis accepts one or two route controller modules and up to nine router modules in a one chassis system. Additional chassis may be populated with up to ten router modules. Route controller modules can reside only in slots 10 and 1 (10 and 1). In a QSR chassis with only one route controller module, install the route controller module in slot 10. Figure 2 shows QSR chassis slot numbering when viewed from the front of the QSR.

NOTE The 2-Port Gigabit Ethernet module is a Family 1 module.

Figure 2. QSR Chassis Slot Numbering

Rules for populating a single QSR chassis are as follows:

Refer to IPriori CLI Reference and Configuration Guides (Vol. 1) for further information on this command. Online versions of the manuals are available at http://www.avici.com/documentation.

CAUTION (2) When handling router modules, wear a grounded wrist strap or equivalent antistatic protection to prevent damage to electronic parts.

Populating Multiple Chassis

Population rules for a second chassis that you plan to connect to the first chassis are similar to the rules for the first chassis. However, you must install a minimum of two router modules in the second and subsequent chassis. After installing the first two modules, you can continue to populate the chassis one module at a time, following the population rules in the preceding section.

A secondary chassis does not require a route controller module and can house up to 10 router modules. Place the last router module in slot 10.

Completely fill the first QSR chassis with router modules before starting to populate a second QSR that you plan to connect to the first.

In a multiple-chassis system, a module is identified by the chassis number and slot number; for example, 1/10 is chassis 1, slot 10.

Preparing to Remove a Router Module

Router module replacement requires shutting down the module via the CLI command line, disconnecting the cable connections, and removing the router module.

Routine router module removal requires the disconnecting of existing fiber optic cable connections. Router modules serving as Server Attached Modules (SAMs) require disconnecting fiber optic and Ethernet cable connections to the server module.

CAUTION (3) Within five minutes of removal of a module, a replacement module or filler module must be installed in the empty slot to ensure proper air flow within the system.

Removing a Router Module

Prior to removing a module you must shut down the module being replaced.

WARNING (1) This is a Class 1 laser product. Invisible laser radiation can be emitted from the aperture of the port when the fiber cable is disconnected. Avoid exposure to laser radiation and do not look directly into open apertures.

PROCEDURE: Use the following steps to remove the Gigabit Ethernet module(s):

Step 1 Verify that the wrist strap you are wearing is properly grounded.

Step 2 Open the pull tab on the right cable tray and gently pull the right cable tray out of the router (see Figure 3).

Figure 3. Router Module Faceplate

Step 3 Disconnect the lower fiber optic cables from the fiber cable adapters (SC) on the right cable tray. Move the cables to one side to ensure that they do not interfere with removal of the router module (see Figure 4).

Figure 4. Router Module Cable Connections

Step 4 Gently push the right cable tray back into the module and close the cable tray pull tab.

If the module is a SAM, proceed to Step 5, if not, skip to Step 6.

Step 5 Open the cable tray pull tab on the faceplate of the router module tray marked "AUX." Gently pull the cable tray partially out of the module until detent clicks (see Figure 5).

Step 6 Open the pull tab on the center cable tray and gently pull the cable tray out of the router until detent clicks (see Figure 5).

Figure 5. Ethernet Cable Connection

Step 7 Disconnect and undress the RJ-45 Ethernet cable from the Ethernet port on the tray marked "AUX" (see Figure 5). Hang the Ethernet cable down and out of the way, or tuck the cable into the horizontal cable tray under the module shelf.

Step 8 Gently push all cable trays to the closed position and close the cable tray pull tabs.

WARNING (2) This is a Class 1 laser product. Invisible laser radiation can be emitted from the port aperture when the fiber cable is disconnected. Avoid exposure to laser radiation and do not look directly into open apertures

Step 9 To unlock the ejector latches, simultaneously slide the release levers in the direction of the arrows (see Figure 6).

CAUTION (4) When the ejector latch release lever is in the open position, do not use the latch lever to remove the module or adjust the module in the card guides. Failure to adhere to these guidelines may result in equipment damage.

Step 10 To release the module from the backplane, simultaneously rotate the ejector latches to a fully open position and carefully pull the router out a few inches out of the shelf (see Figure 6).

Figure 6. Router Module Ejector Release Levers

Step 11 Hold the module in place with one hand at the bottom of case, then close the ejector latches by rotating them to the closed position and sliding the release levers in the direction of the arrows to lock the levers back into place.

Step 12 To remove the module, grasp it on the top and bottom and pull it carefully out of the shelf.

NOTE Do not rest the module on the cable trays during inspection. This could result in the breaking of the pull tabs on the cable tray drawers (see Figure 3).

Step 13 Carefully inspect the Very High Density Metric (VHDM) connector for damage such as deformed sockets, holes between socket columns, and deformed guide fins on top and bottom of the socket columns.

CAUTION (5) Any contact to a VHDM connector outside a QSR could damage the connector. A detailed inspection of the VHDM connector is required each time a module is removed or inserted. Lay the module gently on its side to perform a VHDM connector inspection.

.

Figure 7. VHDM Connector

NOTE If the VHDM connector has any signs of damage, DO NOT insert it into a QSR. Mark the module and slot as damaged and call TSR-BY-AVICI to request an Return Material Authorization (RMA).

Step 14 Before placing the module in a static-proof bag, replace the VHDM protective cap over the VHDM connector at the rear of the module. This will protect the pins while the module is not in the QSR (see Figure 12). Repackage according to RMA directions. Ship back to Avici.

Step 15 If the slot is not populated with a module, it must be filled with a filler module within five minutes.

Removing Fabric Filler or Filler Modules

The QSR systems ships with five (5) filler modules that ensure proper cooling and elimination of electromagnetic interference during operation and two (2) fabric filler modules that ensure a robust and reliable topology between modules. Remove filler modules or fabric filler modules from slots intended for router modules.

Removing Fabric Filler Modules

If the slot intended for the route controller is filled with a filler or fabric filler module, remove it using the procedure below.

To avoid damage to the backplane, perform a detailed inspection of the fabric filler module VHDM connector each time you remove or insert a module.

PROCEDURE: Use the following procedure to remove a fabric filler module:

Step 1 Verify that the wrist strap you are wearing is properly grounded or that other antistatic measures are in place.

Step 2 To unlock the ejector latches on the module, simultaneously do the following to both latches (see Figure 9):

Figure 8. Opening Fabric Filler Module Latches

Step 3 Pull the module out of the chassis to unseat the backplane connectors.

Step 4 Carefully inspect the VHDM connector for damage such as deformed sockets, holes between socket columns, or distorted guide fins on the top and bottom of the socket columns (see Figure 9).

.

Figure 9. Fabric Filler Module VHDM Connector

CAUTION (6) If the VHDM connector shows any signs of damage, DO NOT insert it into a chassis. Mark the module as damaged and call TSR-BY-AVICI to request an RMA.

Step 5 Close the ejector latch levers on the fabric filler module.

Removing Filler Modules

If the slot intended for the route controller is filled with a fabric filler module, remove it using the procedure below. Figure 10 shows a filler module.

Figure 10. Filler Module

PROCEDURE: Use the following steps to remove a filler module:

Step 1 Use a 1/2-in. flat-blade screw driver to loosen the lock latch on the filler module.

Step 2 Pull the filler module out of the slot (see Figure 11).

Figure 11. Removing Filler Modules

Step 3 Store the filler module in a dry, cool area.

Installing Router Modules

When replacing a router module or a filler module, installation must adhere to module population rules for your type of installation. Refer to the "QSR Module Population Rules" .

CAUTION (7) Fiber optic cables must be thoroughly cleaned each time a cable is connected or reconnected. Failure to do so may impact performance or damage to the fiber optic cable.

Installation of the Server Attached Module (SAM) requires the re-connection of fiber optic and Ethernet cables.

CAUTION (8) When handling modules, wear a grounded wrist strap or equivalent antistatic protection to prevent damage to electronic parts.

PROCEDURE: Use the following procedure when installing a router module or a router module acting as a Server Attached Module (SAM):

Step 1 Verify that your antistatic wrist strap is properly grounded.

Step 2 Remove the router module from its packaging and static protection bag.

Step 3 Before inserting the module, remove the VHDM protective cap from the end of the module before use. Set the protective cap aside in a safe place (see Figure 12).

NOTE Do not rest the module on the cable trays during inspection. This could result in the breaking of the pull tabs on the cable tray drawers (see Figure 13).

Figure 12. Remove VHDM Protective Cap Before Use

NOTE A detailed inspection of the VHDM connector is required prior to insertion. Lay the module gently on its side so you can perform a VHDM connector inspection.

Figure 13. Cable Tray Pull Tabs

Step 4 Carefully inspect the VHDM connector for damage such as deformed sockets, holes between socket columns, and deformed guide fins on top and bottom of the socket columns (see Figure 14).

.

Figure 14. VHDM Connector

NOTE If the VHDM connector has any signs of damage, DO NOT insert it into a QSR. Mark the module as damaged and call TSR-BY-AVICI to request an RMA.

Step 5 Ensure that the cable trays on the router module being inserted and on the adjacent router modules are fully closed.

Step 6 Ensure that all chassis cabling is clear for module insertion.

Step 7 If not already done, close the ejectors latches completely by sliding the release levers in the direction of the arrows and locking into place (see Figure 15).

Figure 15. Router Module Installation

Step 8 Align the module with the card guides and slide the module into the slot until the ejector latch's release lever tab hits the outer lip of the shelf (see Figure 16 and Figure 17).

Figure 16. Router Module Insertion -1

Step 9 Simultaneously slide the release levers in the direction of the arrows and rotate the ejector latches to the open position (see Figure 17 and Figure 18).

Figure 17. Router Module Insertion - 2

CAUTION (9) When the ejector latch is in the open position, do not use the lever to lift or adjust the module in the card guide. Failure to adhere to these guidelines may result in equipment damage.

Figure 18. Router Module Insertion - 3

Step 10 Slide the module in until the ejector latch tab slides into position behind the outer lip of the shelf (see Figure 19).

NOTE Do not push the module too far into the slot. The ejector latch tabs must not extend beyond the groove that forms the outer lip of the shelf.

Figure 19. Router Module Insertion - 4

Step 11 Simultaneously depress the release levers on the top and bottom ejector latches and rotate the ejector latch to the closed position (see Figure 19 and Figure 20). Release the release levers once the ejector latches are closed.

NOTE If the ejector latches will not close, reseat the module by pulling it six inches out of the slot and then repeating Step 7 through Step 11, making sure the module is not inserted too far into the slot. If the ejector latches still do not close after reseating the module, contact Avici Customer Support.

Figure 20. Router Module Insertion - 5

WARNING (3) This is a Class 1 laser product. Invisible laser radiation can be emitted from the aperture of the port when the fiber cable is disconnected. Avoid exposure to laser radiation and do not look directly into open apertures.

If the module is a SAM, then perform Step 12 through Step 15.If the module is not a SAM perform Step 13, then skip to Step 16.

Step 12 Open the cable tray pull tab on the faceplate of the router module tray marked "AUX." Gently pull the cable tray partially out of the module until the detent clicks (see Figure 21).

Step 13 Open the pull tab on the center cable tray and gently pull the cable tray out of the router until detent clicks (see Figure 21).

Figure 21. Reconnecting the Ethernet Cable Connection

Step 14 Reconnect and route the RJ-45 Ethernet cable from the Ethernet port on the tray marked "AUX." using the cable management system.

Step 15 Gently push the cable tray marked "AUX" to the closed position and close the cable tray pull tabs.

NOTE Take care to route the cables using the cable management system to avoid damaging the cables when closing the drawers.

Step 16 Reconnect the fiber optic cables to the fiber cable adapters (SC) on the center cable tray (see Figure 22).

WARNING (4) This is a Class 1 laser product. Invisible laser radiation can be emitted from the port aperture when the fiber cable is disconnected. Avoid exposure to laser radiation and do not look directly into open apertures

Figure 22. Reconnecting of Fiber Optic Cables

Step 17 Gently push the center cable tray back into the router module and close the cable tray pull tabs.

Step 18 Open right cable tray door and repeat Step 16 and Step 17 for fiber optic cable connections in the right cable tray.

Configuring the 2-Port Gigabit Ethernet Module

The QSR Gigabit Ethernet interface interconnects to other Gigabit Ethernet compliant devices. Support for the following optional clauses of IEEE 802.3-2000 standards are currently supported:

Address Resolution Protocol (ARP) processing is available for the conversion of internetwork addresses to physical addresses hard coded in the network interface hardware. ARP support includes:

To configure a 2-port Gigabit Ethernet module, activate the installed module and configure the interface as described in the following sections.

Activating a 2-Port Gigabit Ethernet Module

PROCEDURE: Use the following steps to configure and activate a module.

Step 1 Use the module command to identify the module to be activated. Module type is auto detected.

Step 2 Use the boot command to specify which image the module loads.

Step 3 Use the no shutdown command to activate the module.

Example: In the following example:

router#configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

router(config)#module 1/35

router(config-module)#no shutdown

router(config-module)#end

router#show modules

MODULE 1/35:

Discovered (2x1GbE) 2 Port Gigabit Ethernet MPLS-Capable

Configured (2x1GbE) 2 Port Gigabit Ethernet

Physical port type is multi mode



Hardware is 2x1GbE, Version 1.0, Revision 11

Fabric version is 2.0

Software version: Platform: cm-d; Label: R4_2

                    Built on May 29 2001, 12:37:44

ROM Version: IPriori Bootrom Release 5.3 built Aug 28 2000, 20:19:21



Product Id: S16/O48-POS-1-SR-R (Rev. 04); S/N CELROM000011

Started 1 time

Last started on TUE MAY 29 12:27:11 2001

Module uptime is 19 hours, 15 minutes, 49 seconds

Administratively Up; Current state is Up



Max number of historical logging files: 5

The module Command

The module command is used to enter module mode.

Syntax: [no] module bay#/slot# type

bay#

Defines the bay number in which this module is located.

slot#

Defines the slot number to configure. Slots are numbered from 1 to 40 beginning at the top left of the machine. Each physical slot is numbered on the hardware for reference.

type

The type of module to configure in this slot. When configuring a 2-Port Gigabit Ethernet module:

  • 2x1gbe - Assign a 2-Port Gigabit Ethernet module to the slot

Description: Within module mode, the following commands are available:

Table 1. Module Mode Commands

Command Description

auto-upgrade

Enable Auto Upgrade of images for the module.

boot[flags flag {1|2} | file | package-file]

Modify boot parameters for this module.

default

Set default values.

exit

Exit from module mode

fabric

Fabric functions.

fpga

Configure FPGAs on the module(s).

help

Description of the interactive help system

ip

Module specific IP configuration commands.

logging-filter system level

Specify that the hardware entity does not generate events for the specified system at or below the specified level. Note that critical errors are always generated regardless of filtering. Multiple logging filter statements can be given. Default is to log all levels including and above warning for all systems.

logging-max-history max_files

Change the maximum number of log files that are created on the permanent storage for the current system. A number will form the extension to the stored file name and be numbered from 0 to max_file -1. Default is 5. Allowed range is 1 to 100.

no

Negate a command or set its defaults.

post-burn filename

Burn POST on individual or all module(s).

reboot filename [1 | 2]

Specify the image or configuration file to be used when the system starts and restarts the system.

rom-burn filename

Burn ROM on individual or all module(s).

[no] shutdown

Startup or shutdown the module

The primary function available in module mode is the ability to configure or delete the module that resides in the slot. This is done with the [no] shutdown command. The shutdown command disables and shuts down the module residing in the slot. The no shutdown command enables or configures the module residing in the slot.

Use the no module command to delete a module.

Related Commands: show modules

Display the Modules

Use the show modules command to display the current configuration and state for a module.

Syntax: show modules [bay/slot] [brief]

bay/slot

Show only information for the module residing in bay/slot where bay is the bay number and slot is the slot number.

brief

Display summarized information about the specified module(s).

Description: This command displays configuration information for one or all modules residing in this bay.

The show modules brief command will specify which module is the SAM module by starting the information line with an S in the case of the primary SAM and a B in the case of a backup SAM.

Default: None.

Command Mode: Privileged.

Example 1: In the following example, the show modules command displays information about all the configured modules:

MODULE 1/16:

Discovered (2x1GbE) 2 Port Gigabit Ethernet MPLS-Capable

Configured (2x1GbE) 2 Port Gigabit Ethernet

Physical port type is multi mode fiber

Hardware is 2x1GbE, Version 1.0, Revision 11

Fabric version is 2.0

IPriori Release Version:

  Operational image version: Platform: platform; Label: release label Built on build date, build time ROM Version: IPriori Bootrom Release release # built build date, build time



Product Id: YYYYYYYYYYYYYYY (Rev. YY); S/N YYYYYYYYYYYY

Started 1 time

Last started on TUE MAY 29 12:27:11 2001

Module uptime is 19 hours, 15 minutes, 49 seconds

Administratively Up; Current state is Up



Max number of historical logging files: 5

MODULE 1/17:

Discovered (1xOC12c) 1 Port Packet Over SONET OC-12c/STM-4c

Configured (1xOC12c) 1 Port Packet Over SONET OC-12c/STM-4c

Physical port type is short range single mode fiber

  Hardware is CHE, Version 0.0, Revisions 0

  Fabric version is 2.0

Software version:

Product Id: (Rev. ); S/N

Started 1 times

Last started on THU AUG 12 12:39:06 1999

Administratively Up; Current state is Unknown



Max number of historical logging files:5

Non-default logging filters:

transport information

The following table describes the fields in the display:

Table 2. Fields Displayed by show modules    
Field Description

MODULE n/n

Specifies the bay number and slot number where the module is configured.

Discovered

Specifies the type of module "discovered" by the Bay Controller in the specified slot.

Configured

Specifies they type of module configured for the specified slot.

Physical port type

Specifies the type of fiber installed in the specified slot.

Hardware

Specifies hardware type, version, and Revision.

Fabric version

Specifies the fabric version configured for this QSR.

Software version:

Specifies the version of software loaded on the module.

Product Id:

Specifies the product identifier for the module.

Started

The number of times the module has been restarted since the bay came up.

Last started on

The time at which the module was last started.

Module Uptime

The amount of time the module has been up.

Administrative status

Indicates the administrative state of the module.

  • Administratively Up - Module has been discovered and configured and is operational.

  • Administratively Down - module is discovered and configured but has been shut down

Current state is

Indicates the operation state of the module.

  • up - Module has been discovered and configured and is operational.

  • down - module is discovered and configured but is not operating. Indicates problem.

  • unconfigured - Module has been booted but has not yet been fully configured.

  • unknown - The Bay Controller has not yet discovered the module.

Example 2: In the following example, the show modules brief command displays summarized information about the modules:

router#show module brief

Module Discovered Configured                Last Started            State

  1/1     4xOC12c     4xOC12c       1 WED SEP 20 10:40:07 2000             Up

  1/2     2x1GbE      2x1GbE        1 WED SEP 20 10:40:07 2000             Up

.

.

.

  1/14     1xOC48c     1xOC48c      1 WED SEP 20 10:40:08 2000 Up

  1/15      4xOC3c     4xOC3c       1 WED SEP 20 10:40:07 2000 Up

S 1/16      1xOC12c    1xOC12c      1 WED SEP 20 10:39:57 2000 Up

  1/17      4xOC12c    4xOC12c      1 WED SEP 20 10:40:07 2000 Up

  1/18      4xOC12c    4xOC12c      1 WED SEP 20 10:40:08 2000 Up

  1/19      4xOC12c    4xOC12c      1 WED SEP 20 10:40:07 2000 Up

B 1/20      4xOC12c    4xOC12c      1 WED SEP 20 10:40:07 2000 Up

router#

The following table describes the fields in the display:


Table 3. Fields Displayed by show modules brief 
Field Description

Module

Bay and slot number where the module is installed.

Discovered

Indicates the type of module and the number of ports on the module as discovered by the bay controller.

Configured

Indicates the type of module IPriori has configured for the specified bay/slot.

Last Started

Date and time of last start.

State

Admin Up - Module has been discovered and configured and is operational.

Admin Down - module is discovered and configured but has been shut down

Up - Module has been discovered and configured and is operational.

Down - module is discovered and configured but is not operating. Indicates problem.

Unconfigured - Module has been booted but has not yet been fully configured.

Misconfigured - Module has been booted but is not properly configured.

Unknown - The Bay Controller has not yet discovered the module.

Configuring the Interfaces

Activating a Gigabit Ethernet Interface

PROCEDURE: Use the following steps to configure a Gigabit Ethernet interface:

Step 1 Use the show module command to display configured modules. If the 2-port Gigabit Ethernet module is shut down, use the no shutdown command in module configuration mode to activate the module.

Step 2 Use the configure terminal command to enter configuration command mode.

Step 3 Use the interface command with the gbe key word and bay/slot/port location to enter interface configuration command mode.

Step 4 Optionally, modify the default settings.

Step 5 Optionally, configure a description for the interface using the description command.

Step 6 Configure the local address using the ip address command.

Step 7 Use the no shutdown command to activate the interface.

Step 8 Use the show interface command to display and verify the new interface configuration.

The interface Command

The interface command defines/deletes an interface.

Syntax: [no] interface gbe bay/slot/port

gbe

Configures the interface to support gigabit Ethernet connections.

bay/slot/port

Identifies a specific interface on the TSR. Valid values are as follows:

bay: Bay number. Valid values 1 - 2. Default 1.
slot: Slot number where the module is installed in the QSR. Valid values are integers between 1 and 40.

port: Valid values are 1 - 2.

Description: The interface gbe command defines a Gigabit Ethernet interface and enters the interface configuration mode. The interface is not usable as a routing interface until you use the ip address and no shutdown commands.

To configure a gbe interface:

Use the interface gbe bay/slot/port syntax to configure a Gigabit Ethernet interface.

Default: No interfaces configured.

Command Mode: Configuration.

Example: In the following example:

router#configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

router(config)#interface gbe 1/1/1

router(config-if)#ip address 5.10.1.2 255.255.0.0

router(config-if)#no shutdown

router(config-if)#end



router#show interface gbe 1/1/1



GBE 1/1/1 is up

Internet address is 5.10.1.2/16

Broadcast address is 5.10.255.255

Ethernet address is 00:90:b2:fd:00:06

MTU 10240 bytes, Bandwidth 1000.000 Mbit/Sec

Encapsulation ARPA

Frame type for ARP is ARPA, Frame type for IP is ARPA

Autonegotiation is Disabled, Flow control is symmetric

    Vlan is Disabled, Number of vlans on this port are 0

Received:

132950 bytes

0  directed packets, 1621  multicast packets, 1  broadcast packets

0 discards, 0 errors, 0 unknown protocols

Transmitted:

133078 bytes

0  directed packets,1623  multicast packets, 1  broadcast packets

0 discards, 0 errors

Related Commands: show interface gbe
show running-config
show startup-config
ip address

Display the Gigabit Ethernet Interface

Use the show interfaces gbe command to display information about Gigabit Ethernet interfaces.

Syntax: show interfaces gbe bay/slot/port

bay/slot/port

Identifies a specific interface on the TSR. Valid values are as follows:

bay: numeric identifier for the bay.
slot: Slot number where the module is installed in the QSR. Valid values are integers between 1 and 40.

port: The 2x1gbe has 2 ports.

Description: Use the show interfaces gbe command with no arguments to display information about all the gigabit Ethernet interfaces.

Use the show interfaces gbe bay/slot/port command to display information about a specific gigabit Ethernet interface.

Default: None.

Command Mode: Executive and privileged.

Example: In the following example, show interfaces gbe bay/slot/port command displays information about the specified Gigabit Ethernet interface:

router#show interface gbe 1/1/1



GBE 1/1/1 is up

    Internet address is 5.10.1.2/16

Broadcast address is 5.10.255.255

    Ethernet address is 00:90:b2:fd:00:06

MTU 1500 bytes, Bandwidth 1000 Mbit/Sec

Encapsulation ARPA

Frame type for ARP is ARPA, Frame type for IP is ARPA

Autonegotiation is Disabled, Flow control is symmetric

    Vlan is Disabled, Number of vlans on this port are 0

Received:

132950 bytes

0  directed packets, 1621  multicast packets, 1  broadcast packets

0 discards, 0 errors, 0 unknown protocols

Transmitted:

133078 bytes

0  directed packets,1623  multicast packets, 1  broadcast packets

0 discards, 0 errors

router#

The following table describes the fields in the display:

Table 4. Fields Displayed by show interfaces gbe Command 
Field Description

line protocol up/down

Indicates the operational status of the interface.

Internet address is

IP address and netmask of the interface.

Broadcast address is

The address for all hosts on a network.

Ethernet address is

The Ethernet address for this interface.

MTU bytes

The Maximum Transfer Unit (MTU) size for this interface.

Bandwidth

Available bandwidth of this interface.

Encapsulation

The protocol enabled on this interface.

Frame type for ARP is

The frame type used for the Address Resolution Protocol.

Frame type for IP is

The frame type used for the Internet Protocol.

Autonegotiation is

If enabled, attempts to discover the highest mode of interoperability on the link.

Flow control is

Indicates how the interface will control traffic during periods of congestion. There are two types configurable:

  • asymmetric allows the local port to determine on its own whether to perform flow control of the remote port.

  • symmetric allows for the local port to perform flow control only if the remote port can also perform flow control of the local port.

Received:

  • bytes -

The total number of packets received over this interface.

  • directed packets -

The number of unicast packets received on this interface.

  • multicast packets -

The number of multicast packets received on this interface.

  • broadcast packets -

The number of broadcast packets received on this interface.

  • discards -

The number of received packets purposely dropped during reception on this interface.

  • errors -

The number of packets in error received on this interface.

  • unknown protocols -

The number of packets received with an unknown protocol.

Transmitted:

  • bytes -

The total number of bytes sent over member links of this interface.

  • directed packets -

The number of unicast packets sent on this interface.

  • multicast packets -

The number of multicast packets sent on this interface.

  • broadcast packets -

The number of broadcast packets sent on this interface.

  • discards -

The number of packets purposely dropped during transmission on this interface.

  • errors -

The number of packets sent in error on this interface.

Configuring Flow Control

The flowcontrol command provides for configuring the circumstances under which flowcontrol will be used.

Syntax: flowcontrol {asymmetric | symmetric}

no flowcontrol

Description: Flow control controls traffic rates during periods of congestion. Use the flowcontrol asymmetric command to allow the local port to determine whether flow control will be performed on the remote port. During periods of local port congestion, the local port will send a request for the remote port to stop transmitting.

Use the flowcontrol symmetric command to allow for the local port to only perform flow control if the remote port can also perform flow control. If the remote port is not able to perform flow control locally, the local port will also not perform flowcontrol.

Use the no flowcontrol to disable flow control on this interface.

Default: Symmetric.

Command Mode: Gigabit Ethernet interface configuration.

Example: The following set of commands:

router#configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

router(config)#interface gbe 1/34/1

router(config-if)#flowcontrol asymmetric

router(config-if)#end

router#

LEDs

The 2-Port Gigabit Ethernet module supports six LEDs, see Figure 23.

Board Status

The two top LEDs indicate "up" status of the board. During routing module POST, the red LED on the faceplate lights and remains lit until POST is completed. After completion of POST, the green LED lights and remains solid and the red LED is extinguished.

The solid green LED indicates that the module has passed POST.

If the red LED remains lit, POST has detected a nonrecoverable error or fault. If the red LED remains lit, remove and reseat the module to run POST again.

Port Status

The four bottom bi-color LEDs, indicate port status. These bottom LEDs consist of two pairs of LEDs: the left most LED (green, red, or not lit) indicates port status and the right most LED (amber) indicates activity status, one set per port.

When the Gigabit Ethernet link is up, the left most LED will be steady green. If no light is present, the port is down. If the same leftmost LED is steady red, there is either a Remote Fault or Autonegotiation Error. A Remote Fault is usually caused by the transmit (TX) fiber of the link being broken or not connected. An Autonegotiation Error is caused by a mismatch or failure to resolve 802.3 Autonegotiation. This can be fixed by disabling Autonegotiation on both devices on the link.

Figure 23. LEDs on the 2-Gigabit Module

Configuring Autonegotiation

The negotiation auto command enables autonegotiation on an interface.

Syntax: [no] negotiation auto

Description: By detecting the capabilities of the device at the other end of the link autonegotiation attempts to configure the highest performance mode of interoperability between the two devices.

As per IEEE 802.3 standard, autonegotiation should be configured identically on both devices of a link; if the remote device is enabled for autonegotiation, the local QSR should be enabled as well. Otherwise, one device may indicate a link is up when the other end does not.

Use the negotiation auto command to enable autonegotiation for this interface.

Use the no negotiation auto command to disable autonegotiation for this interface.

Default: Enabled.

Command Mode: Interface configuration.

Example: The following set of commands:

router#configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

router(config)#interface gbe 1/34/1

router(config-if)#negotiation auto

router(config-if)#end

router#

Configuring ARP

Because the IP network layer is a four-byte address and the Ethernet link layer is a six-byte MAC address, a method of binding these two address types together is required to allow the transmission of data between the layers. Two types of IP to MAC address bindings or entries are supported: static and dynamic.

Static is a manual entry from the CLI using the arp command in interface mode.

Dynamic binding requires a protocol to bind addresses between the two layers. Address Resolution Protocol (ARP) is a low-level protocol that fulfills this function by dynamically binding the configured IP network layer address with the Ethernet link layer hardware address. A dynamic database of address pairings is kept in the ARP cache on each QSR module. Dynamic bindings are learned from the ARP protocol in the following three ways:

Dynamic bindings are placed in an ARP Cache and are subject to a uniform timeout or aging policy that takes into account both transmit inactivity as well as failure to periodically refresh those bindings through any one of the above three mechanisms. A timer is started when a new binding is entered for the first time in the ARP Cache, and subsequently reset whenever that binding is updated, or whenever a packet is sent to the entry's IP/MAC address. If the timer expires, the binding is removed from the ARP Cache.

In addition to deletion from inactivity or refresh failures, dynamic bindings can also be deleted manually on an individual, or per interface or module basis through the CLI at any time. Static bindings are also placed in the ARP Cache; however, they're not considered for deletion on the flush command. These bindings are also not subject to any timeouts.

Static bindings have an absolute precedence over those learned via ARP: if a dynamic mapping for a given IP address already exists when a static binding for that address is specified, the MAC address on the static binding takes precedence; furthermore, all subsequent updates coming over the wire for that IP address are discarded.

Configuring a Static Binding

The arp command is used to manually enter or delete a static binding.

Syntax: [no] arp ipaddress mac-address

ip-address

The IP address to be matched with the MAC address for the ARP cache entry.

mac-address

The Ethernet hardware MAC address to be matched with the IP address for the ARP cache entry. Valid formats are:

  • HH:HH:HH:HH:HH:HH