Avici Systems Inc.


Field Replacement Procedure

TSR® 2-Port Gigabit Ethernet Installation & Configuration

03482-00 Rev. EA

This procedure is for installing the 2-Port Gigabit Ethernet module in the Terabit Switch Router (TSR®).

Before beginning this procedure, carefully inspect the package to ensure no damage occurred during shipping or delivery. If you suspect any possible damage, contact Customer Service immediately. For easy and quick reference, this FRP is organized as follows:

Support Services
Tools
Overview
TSR Bay, Shelf, and Module Numbering
Populating the Bay
Transceiver Offerings
Preparing to Install Modules
Removing a Router Module
Removing Filler Modules
LEDs
Configuring the 2-Port Gigabit Ethernet Module
Configuring the Interfaces

Support Services

There are three ways to obtain information on customer service and training:

Tools

Overview

The 2-port Gigabit Ethernet module attaches to the TSR® via optical multi-mode short reach (1GigE 2P-SX) Printed Circuit Board (PCB) or multi-mode/single-mode long reach (1GigE 2P-LX) PCB. '

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

To visually identify this module, please refer to the faceplate label. The 2-Port Gigabit Ethernet module can be identified by either 1GigE 2P-SX for the short reach version or 1GigE 2P-LX for the long reach version.

TSR Bay, Shelf, and Module Numbering

Each TSR bay has four shelves numbered from 1 (top) to 4 (bottom). Each shelf has 10 slots to house the router and server modules.

Bay Numbering

Bay numbering for the TSR is as follows: all bays will be numbered odd in the first row; for example: 1, 3, 5, and even in the second row; for example: 2, 4, 6. This numbering system is more logical for a larger scale system typically found in a POP (with odd first row and even second row.) Refer to Figure 1.

Figure 1. TSR Bay Numbering

The four shelves and the router module numbering is as follows:

Figure 2. TSR Bay Shelf and Slot Numbering

Populating the Bay

The location of the routing modules within the bay creates the TSR system's "toroidal mesh." It is critical to install routing modules and server modules in predefined positions. All router modules must be inserted in pairs.

The rules for populating the first TSR Full Bay and TSR Split Bay with router module pairs follow.

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.

Transceiver Offerings

The 2-Port Gigabit Ethernet module includes two transceiver offerings: SX and LX. See Table 1. The SX transceiver supports only Multi-mode Fiber (MMF) including both 62.5/125 µm and 50/125 µm diameters. The LX transceiver supports both MMF and single-mode fiber (9/125 µm) and requires an external mode conditioning cable for Gigabit Ethernet applications.

Table 1. Transceiver Offerings 
Requirements SX Transceiver Requirements LX Transceiver Requirements

Center Wavelength

850 nm

1300 nm

Launch Power

-9.5 dBm

-11 dBm (SMF)

-11.5 dBm (MMF)

Rx Sensitivity

-17 dBm

-19 dBm

Distance:
   62.5/125µm

   50/125µm
   9/125µm

200 meters

500 meters

NA

550 meters

550 meters

5000 meters

Preparing to Install Modules

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

Use these precautions to prevent damage from static electricity:

CAUTION Risk of electrostatic damage. When handling circuit cards, wear a grounded antistatic wrist strap or equivalent protection to avoid damaging electrostatic parts.

Installing the Antistatic Wrist Strap

A grounded antistatic wrist strap must be used to protect the TSR system modules and components from damage caused by static.

PROCEDURE: Use the following procedure to install the antistatic wrist strap:

Step 1 Remove the alligator clip from the grounding pin on the antistatic wrist strap.

Step 2 Insert the grounding pin into the electrostatic discharge (ESD) jack on the front of the TSR bay shelf. Refer to Figure 3.

Step 3 Use the ESD jack while handling modules.

Figure 3. ESD Jack Location

Removing a Router Module

If you are removing a router module, use the following instructions. If you are removing a filler module, refer to "Removing Filler Modules" .

Before removing a module you must shut down the module being replaced. Use the shutdown command to disable all functions on the module. The module appears as administratively down when executing the show mod brief command.

Shutting Down the Module

To notify the system to shutdown a module, use the CLI command line to turn off the respective slot. Using the shutdown command allows the removal of the module without service interruption.

Example: Use the shutdown command to disable all functions on the module. The module appears as administratively down when executing the show mod brief command.

router(config)#module 1/5/1

router(config-if)#shutdown

router(config-if)#end

router#

router#show module brief



Module Discovered Configured      Last Started            State



  1/1     1xOC192c    1xOC192c       MON DEC 17  10:40:07 2003           Up

  1/2     2x1GBE      2x1GbE         MON SEP 2  10:40:07  2002           Up

.

.

  1/5     1xOC48c     1xOC48c        MON SEP 2   10:40:08 2002           Down

  1/6      1xOC12c    1xOC12c        MON SEP 2   10:39:57 2002           Up

  1/3      4xOC12c    4xOC12c        MON SEP 2   10:40:07 2002           Up

 router#



When the module is shutdown, proceed with 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 (1) When handling router modules, wear a grounded wrist strap or equivalent antistatic protection to prevent damage to electronic parts.

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

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

Step 2 Open the pull tab on the center cable tray and gently pull the center cable tray out of the router (refer to Figure 4 and Figure 5).

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.

Figure 4. Router Module Faceplate

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

Figure 5. Router Module Cable Connections

Step 4 Gently push the center cable tray back into the router module and close the cable tray pull tab. If necessary, repeat Step 2 through Step 3 for fiber optic cable connections in the right cable tray.

If the module is a SAM, proceed to Step 5, if not then 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 (refer to Figure 6).

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 6 Open the pull tab on the center cable tray and gently pull the cable tray out of the router until detent clicks (refer to Figure 6).

Figure 6. Ethernet Cable Connection

Step 7 Disconnect and undress the RJ-45 Ethernet cable from the Ethernet port on the tray marked "AUX" (refer Figure 6).

Step 8 Hang the Ethernet cable down and out of the way, or tuck the cable into the horizontal cable tray under the module shelf.

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

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

Figure 7. Router Module Removal

Step 11 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 7).

CAUTION (2) 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 12 Hold 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.

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 (refer to Figure 8).

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

NOTE 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 inspection.

Figure 8. Cable Tray Pull Tab

CAUTION (3) Any contact to a VHDM connector outside a TSR could damage the connector.

Step 14 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.

.

Figure 9. VHDM Connector

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

Step 15 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 TSR. Refer to Figure 13. Repackage according to RMA directions. Ship back to Avici.

CAUTION (4) 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 Filler Modules

The TSR system ships with 36 filler modules, which ensures proper cooling and elimination of electromagnetic interference during operation. Remove filler modules from slots intended for router modules (see Figure 10).

Figure 10. Filler Module

PROCEDURE: Use the following procedure 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).

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

Figure 11. Removing Filler Modules

Figure 12. Filler Module

Installing the 2-Port Gigabit Ethernet Module

Install the 2-Port Gigabit Ethernet module after removing the filler module. Gigabit Ethernet modules must be installed in an assigned slot location. See "TSR Bay, Shelf, and Module Numbering"

NOTE When the ejector latch release lever is in the open position, do not use the lever to lift or adjust the module in the card guide.

PROCEDURE: Use the following procedure to install 2-Port Gigabit Ethernet modules:

Step 1 Remove the 2-Port Gigabit Ethernet from its static protection packaging.

Step 2 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 13).

Figure 13. 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.

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. Refer to Figure 14.

Figure 14. Cable Tray Pull Tabs

Step 3 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

Figure 15. VHDM Connector

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

Step 4 Check the color indicator on the top of the module to determine if it is the right type for this slot (red circle or blue square). If it is not the correct color and there is no other slot of that color expecting a module of this type, contact Avici Customer Service.

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 bay cabling is clear for module insertion.

Step 7 Close the ejectors latches completely by sliding the release levers in the direction of the arrows and locking into place (see Figure 16).

Figure 16. 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 17 and Figure 18).

Figure 17. Router Module Insertion -1

CAUTION (5) 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.

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

Figure 18. Router Module Insertion - 2

Figure 19. 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 20).

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 20. 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 20 and Figure 21). 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 21. Router Module Insertion - 5

NOTE The 2-Port Gigabit Ethernet module uses existing I/O RJ-45 and fiber optic cables. Unlike the OC-48, the 2-Port Gigabit Ethernet module only uses the right most (3-4) tray for cabling, instead of the center tray.

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 22).

Figure 22. Connecting the Ethernet Cable

Step 13 Open the pull tab on the right most cable tray (3-4) and gently pull the cable tray out of the router until detent clicks (see Figure 23).

Step 14 Connect 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 Connect the fiber optic cables to the fiber cable adapters (SC) on the right most cable tray. Refer to Figure 23.

Figure 23. Installing Fiber Optics

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

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

LEDs

The 2-Port Gigabit Ethernet module supports six LEDs.

Board Status

The two top (existing) 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 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 (green/orange) LEDs, indicate port status. These bottom LEDs consist of two pairs of LEDs, the left most LED indicates port status and the right most LED indicates activity status, one set per port.

When the port is up, the left most LED will be solid green. If no light is present, the port is down.

When the port is receiving data, the right most activity LED will be blinking orange, indicating activity. If there is no light, then it is not active (see Figure 24).

Figure 24. Gigabit Ethernet Module LEDs

Configuring the 2-Port Gigabit Ethernet Module

Introduction

The TSR Gigabit Ethernet interface interconnects to other Gigabit Ethernet compliant devices. Support for the following IEEE 802 standards is available:

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 with the 2x1gbe keyword to identify the 2-port Gigabit Ethernet module installed in the slot.

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 2x1gbe

router(config-module)#boot 2

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 fiber

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. Default = 1

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 2. 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 3.0

  Ipriori release version: 5.0.10

  Operational image version: Platform: cm-d;Label: R5.0_DEV.89,  Built on Mo., Day, Year, Time

   ROM Version: Ipriori Bootrom Release 6.8 built Mo., Day, Year, Time



  Line Card FPGA Software Version: 0.6

  Switch CArd FPGA Software Version: 0.8

  POST Software Version: 10.6.0

  Product Id: (Rev.); S/N

  Module CLEI Code:

  Last started on Day, Month, Year Time

Module uptime is 31 minutes, 27 seconds

Administratively Up; Current state is Up



Max number of historical logging files: 5

The following table describes the fields in the display:

Table 3. Fields Displayed by show modules    
Field Description

MODULE

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.

IPriori release version:

Version of IPriori software loaded on the module.

Operational image version

Platform, label and date operational image was built.

ROM version:

Version of the Boot ROM on the module.

Line Card FPGA Software Version

Version of the FPGA software on the line card portion of the module.

Switch Card FPGA Software Version

Version of the FPGA software on the line card portion of the module. Displayed only if the switch card has an FPGA.

POST Software Version

Version of the POST image on the module.

Product Id:

Specifies the product identifier for the module.

Module CLEI Code:

Common Language Equipment Identification (CLEI) Code assigned by Telcordia for this 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 operational 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.

  • misconfigured - Module has been booted but is not properly configured.

  • unknown - The bay controller has not yet discovered the module.

  • IncompatibleSW - The module is running a software image that is not compatible with the server(s), bay controllers, and other modules.

Max number of historical logging files:

A value from 1 to 199, indicating the maximum number of log files created. Set using the logging-max-history command.

Non-default logging filters:

Input filtering to the logging system as defined using the logging-filter command.

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        WED DEC  4 10:40:07 2002             Up

  1/2     2x1GbE      2x1GbE         WED DEC  4 10:40:07 2002             Up

.

.

.

  1/14     2x1GbE     2x1GbE         WED DEC 4 10:40:08 2002              Up

router#

The following table describes the fields in the display:h


Table 4. 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.

Status

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 TSR. 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 4470 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

Received:

474 bytes

0  directed packets, 0  multicast packets, 0  broadcast packets

0 discards, 0 errors, 0 unknown protocols

Transmitted:

2882 bytes

0  directed packets, 1  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 TSR. 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 4470 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

    Received: c

723431054176 bytes

7279943161 directed packets, 0 broadcast packets

0 discards, 0 errors, 0 unknown protocols

    Transmitted:

284446377380 bytes

2273151325 directed packets, 0 broadcast packets

0 discards, 0 errors

The following table describes the fields in the display:

Table 5. Fields Displayed by show interfaces gbe  
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#

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.

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

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

Default: None.

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 TSR 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 t