TSR® Series II 2-Port Gigabit Ethernet Installation & Configuration

Field Replacement Procedure

TSR® Series II 2-Port Gigabit Ethernet Installation & Configuration

03482-01 Rev. DA

This procedure is for installing the 2-Port Gigabit Ethernet module in the TSR Series II (TSR II). Before beginning this procedure, carefully inspect the package to ensure no damage occurred during shipping or delivery. If you suspect any possible damage, contact Support Services immediately.

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

Support Services
Tools
Overview
Transceiver Offerings
TSR II Bay Module Population Rules
Preparing to Install Modules
Removing a Router Module
Removing Filler Modules
Installing the 2-Port Gigabit Ethernet Module
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:

Phone:
United States Support: 877-292-8424 (TSR-BY-AVICI)
International Support: 01-978-964-2350

E-mail: support@avici.com

World Wide Web: http://www.avici.com

Tools

1/2 in. flat blade screwdriver (if removing filler modules)

3/8 in. flat blade screwdriver (if installing an SAM module)

Overview

The 2-port Gigabit Ethernet module attaches to the TSR II 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.

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

NOTE A MODE-CONDITIONING CABLE IS REQUIRED FOR LX APPLICATIONS OVER MMF, as per the IEEE 802.3-2000 standard. A mode-conditioning cable should NOT be used for LX applications over single mode fiber.

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

TSR II Bay Module Population Rules

Each TSR bay has four shelves numbered from 1 (top) to 4 (bottom). Each shelf has 11 slots to house the router and server modules. All router modules must be inserted in pairs.

NOTE The module population rules for this module set MUST be followed explicitly.

TSR II Bay, Shelf, and Slot Numbering

All bays are numbered odd in the first row; for example: 1 and 3 and even in the second row; for example: 2 and 4 (refer to Figure 1).

Figure 1. Bay Numbering
The four shelves and their slots are numbered as follows:

Figure 2. TSR II 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.

Slots are labeled with red circles to help you identify the module for that slot.

The rules for populating the first TSR II Full Bay and TSR II Split Bay with module pairs are as follows:

Modules occupying a slot use the slot number as its identifier. In a multibay system, a module is identified by bay number/slot number; i.e., 1/10 would be bay 1, slot 10.

The TSR II accepts only red modules. The module color label is located on the top side of the module.

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

Router modules must be added in Family pairs. That is, you must install two Family 1 modules OR two Family 2 modules.

NOTE Do not insert router modules into a dedicated server module slot as this may damage the Very High Density Metric (VHDM) connector. If you accidentally insert a router module into a dedicated server slot, you must inspect the VHDM connector for damage prior to inserting the module into a module slot.

If installing the module in a cold bay, follow the Population Rules outlined in the Terabit Switch Router Series II Install Guide.

If installing the router module in a live bay use the show population CLI command - specifying the module family - to identify the slot(s) to populate.

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

Preparing to Install Modules

Depending on the individual configuration of the TSR II, either a router module or a filler module must be removed in order to install this module set. Refer to "Removing a Router Module" to remove a router module and refer to "Removing Filler Modules" to remove a filler module.

Use these precautions to prevent damage from static electricity:

Do not handle modules unless you are using the appropriate antistatic protection, such as an antistatic wrist or heel strap and a conductive mat.

When using an antistatic wrist strap, attach the cord to the appropriate ground jack.

Handle modules by outer enclosure only. Do not touch electrical connections, pins, or soldered surfaces.

Installing the Antistatic Wrist Strap

A grounded antistatic wrist strap must be used to protect the TSR II 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

CAUTION (1) Risk of electrostatic damage. When handling router modules, wear a grounded antistatic wrist strap or equivalent protection to avoid damaging electrostatic parts.

Removing 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.

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

router(config)#module 1/34/1

router(config-if)#shutdown

router(config-if)#end

router#

When the module is shutdown, proceed with removing the router module.

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

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.

Prior to removing a module you must shut down the module being replaced (see "Shutting Down the Module" ).

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

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, repeatStep 1 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 (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 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 connector inspection.

Figure 8. Cable Tray Pull Tab

CAUTION (5) Any contact to a VHDM connector outside a TSR II 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 (see Figure 9).

.
Figure 9. VHDM Connector

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 II. Refer to Figure 12. If this is an Return Material Authorization (RMA), repackage according to RMA directions. Ship back to Avici.

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

Removing Filler Modules

The TSR II system ships with 41 filler modules, which ensures proper cooling and elimination of electromagnetic interference during operation. Remove filler modules from slots intended for router modules (refer to 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 (refer to Figure 11).

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

Figure 11. Removing Filler Modules

Installing the 2-Port Gigabit Ethernet Module

Install the 2-Port Gigabit Ethernet module after removing the router or filler module. Gigabit Ethernet modules must be installed in an assigned slot location. See "TSR II Bay Module Population Rules"

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 Verify that the antistatic wrist strap you are wearing is properly grounded.

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

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 If the VHDM connector has any signs of damage, DO NOT insert it into a TSR II. Mark the module as damaged and call TSR-BY-AVICI to request an Request for Material Request (RMA).

Figure 12. Remove VHDM Protective Cap Before Use

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 trays (see Figure 13).

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

Step 5 Check the color indicator on the top of the module to determine if it is the right type for this slot. The TSR II only accepts red modules. If it is not the correct color and there is no other slot of that color expecting a module of this type, contact Avici Support Services.

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

Step 7 Ensure that all bay cabling is clear for module insertion.

Step 8 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 9 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 10 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).

CAUTION (6) 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 17. Router Module Insertion - 2

Figure 18. Router Module Insertion - 3

Step 11 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 12 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 8 through Step 12, 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

LEDs

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

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 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 solid 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 21. Gigabit Ethernet Module LEDs

Configuring the 2-Port Gigabit Ethernet Module

The TSR II 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:

Full duplex (clause 4)

Auto negotiation (clause 37)

Flow control (clause 31)

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:

Recognition of multiple MAC layer end points per IETF RFC 826

Ability to clear individual ARP entries from the cache

Ability to flush the cache on a per interface, module, or TSR II basis

Ability to globally define ARP cache entry timeout

Ability to display ARP entries

Ability to define a static binding

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:

The module command assigns a 2-port Gigabit Ethernet module to bay 1, slot 35.

The no shutdown command enables the module.

The show modules command displays the new configuration:

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 SX

Physical port type is multi mode

Hardware is 2x1GbE, Version 1.2, Revision AA

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

  Line Card F PGA Software Version: 0.5

  POST Software Version: 8.37.0

  Product Id: YYYYYYYYYYYYYYY (Rev. Y); S/N YYYYY

  Module CLEI Code:

Last started on Wed Dec 04 01:00:14, 24 seconds

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

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

Modify boot parameters for this module. Each module contains two flash memory locations; Location 1 and location 2. Each flash location can be loaded with a separate boot image for the module. The command without the optional file, sets the default image from which to boot. With the optional file, it burns the file into the selected flash memory location. The flags parameter is used to set the boot flags to be used when the system is restarted. To add new boot flags to the existing boot flag, perform a logical "OR" on the existing boot flag and the new setting.

exit

Exit from module mode

help

Description of the interactive help system

logging-filter system level

Specify that the hardware entity does not generate events for the specified system 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.

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 13

Fabric version is 2.0

IPriori Release Version: 5.0.3

  Operational image version: I priori Operational Image 5.0.3 Label: R5.0_CI.10

  Built on build date, build time ROM Version: IPriori Bootrom Release 6.8 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 3. 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 TSR II.

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 Starts Last Started State

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

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

.

.

.

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

  1/15     1XC192c-b    1XC192c-b   1 WED DEC 20 10:40:07 2000 Up

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

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

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

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

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

router#

The following table describes the fields in the display:

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.

Starts

The number of times this module has been started since the TSR II was started.

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 TSR II. 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:

The interface gbe command configures a Gigabit Ethernet interface for bay 1, slot 1, port 1.

The ip address command assigns the IP address 5.10.1.2 to the interface.

The show interface gbe command displays the new setting:

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 interface status is up, l

  MTU 5000 bytes

    Payload BW: 150.336 Mbit/Sec, Total BW: 155.520 Mbit/Sec

    Encapsulation ARPA

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

Autonegotiation is Enabled, Flow control is symmetric

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

Received:

132950 bytes

0 directed packets, 0 multicast packets, 0 broadcast packets

0 discards, 0 errors, 0 unknown protocols

Transmitted:

133078 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 II. 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

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

The following table describes the fields in the display:

Table 5. 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:

Uses the configure terminal command to enter configuration mode.

Uses the interface gbe command to enter interface mode for Gigabit Ethernet for the specified port.

Uses the flowcontrol asymmetric command to set flow control for this interface to asymmetric.

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.

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 TSR II 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:

Uses the configure terminal command to enter configuration mode.

Uses the interface gbe command to enter interface mode for Gigabit Ethernet for the specified port.

Uses the negotiation auto command to enable autonegotiation for the specified interface.

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 II module. Dynamic bindings are learned from the ARP protocol in the following three ways:

The TSR II sends out an ARP request for an IP address. The ARP reply provides the IP address requested by the TSR II.

The TSR II was the target of an ARP request. In this case, the new binding is the source IP and MAC address.

An already existing binding for this TSR II is updated by an ARP request or reply that the TSR II was neither the source nor the target for.

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

HHHH.HHHH.HHHH

where H is a hex character from 0 - F.

Description: Use the arp command to manually enter an IP/MAC address pair into the ARP cache.

Use the no arp command to delete the specified IP/MAC address pair from the ARP cache.

Default: None.

Command Mode: Interface configuration.

Example: The following set of commands:

Uses the configure terminal command to enter configuration mode.

Uses the interface gbe command to enter interface mode for Gigabit Ethernet for the specified port.

Uses the arp command to enter the IP/MAC address pair into the ARP cache for this host.

router#configure terminal

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

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

router(config-if)#arp 16.12.4.1 0090.b2fd.0259

router(config-if)#end

router#show interfaces gbe 1/5/2

GBE 1/5/2 is up

Internet address is 16.12.4.1/16

Broadcast address is 16.12.255.255

Ethernet address is 00:90:b2:fd:02:59

MTU 1500 bytes, Bandwidth 1000 Mbit/Sec

Encapsulation ARPA

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

Autonegotiation is Enabled, Flow control is symmetric

Received:

448 bytes

0 directed packets, 0 multicast packets, 2 broadcast packets

0 discards, 0 errors, 0 unknown protocols

Transmitted:

1020 bytes

0 directed packets, 0 multicast packets, 6 broadcast packets

0 discards, 0 errors

router#

Deleting Bindings from the ARP Cache

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

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

Command	Description
boot [flags flag {1\|2} \| file]	Modify boot parameters for this module. Each module contains two flash memory locations; Location 1 and location 2. Each flash location can be loaded with a separate boot image for the module. The command without the optional file, sets the default image from which to boot. With the optional file, it burns the file into the selected flash memory location. The flags parameter is used to set the boot flags to be used when the system is restarted. To add new boot flags to the existing boot flag, perform a logical "OR" on the existing boot flag and the new setting.
exit	Exit from module mode
help	Description of the interactive help system
logging-filter system level	Specify that the hardware entity does not generate events for the specified system 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.
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

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

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

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.
Starts	The number of times this module has been started since the TSR II was started.
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.

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 II. Valid values are integers between 1 and 40. port: Valid values are 1 - 2.

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.

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 HHHH.HHHH.HHHH where H is a hex character from 0 - F.