module

module

Enters module configuration command 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. Module type is automatically sensed by the bay controller and entered into the running configuration file. If for any reason you wish to pre-configure a module slot prior to the physical installation of that module, you must provide the type field in the command line. Available types include:

1xoc48c - Assign a 1 port OC-48c module to the slot.

4xoc48c - Assign a 4 port OC-48c module to the slot.

2xoc48c - Assign a 2 port OC-48c module to the slot.

2x1gbe - Assign a 2 port Gigabit Ethernet module to the slot.

8x1gbe - Assign an 8 port Gigabit Ethernet module to the slot.

1x10gbe -Assign a 1 port 10 Gigabit Ethernet module to the slot.

4xoc3c - Assign a 4 port OC-3c module to the slot.

16xoc3c - Assign a 16 port OC-3c module to the slot

4xoc12c - Assign a 4 port OC-12c module to the slot.

1xoc192c - Assign a 1 port single-slot OC-192c module to the slot.

1xoc192c-a - Assign a 1 port dual-slot OC-192c module (1 of 2 module set) to the slot.

1xoc192c-b - Assign a 1 port dual-slot OC-192c module (2 of 2 module set) to the slot.

8xoc3-4xoc12msc - Assign an 8 port OC-3c, 4 port OC-12c Multi-service module to the slot.

16xoc3msc - Assign a 16 port OC-3c Multiservice Module to the slot.

8xoc12msc - Assign an 8 port OC-12c Multiservice module to the slot.

Description: The Avici router supports a variety of routing modules in each bay. Modules support Packet Over SONET/SDH traffic (OC-nnc modules), frame relay over SONET, or Gigabit Ethernet traffic (gbe modules).

Each module contains two flash banks: 1 and 2. Each flash bank can be loaded with a separate boot image.

The primary function available in Module configuration mode is the ability to configure or delete the module that resides in the slot.

Use the module bay/slot type command configure the specified module type in the specified slot, change the command mode to Module configuration for the specified module, and access the various commands to configure the module.

Use the no module bay/slot command to delete the module configuration information for the specified slot.

Once you are in Module configuration command mode, you can access the following commands:

Use the auto-upgrade command to enable/disable automatic upgrade for the module.

Use the boot [1 | 2] command to set the flash bank from which to boot the module at the next startup.

Use the boot file [1 | 2] command to burn the specified file into the specified flash memory location.

Package files are a convenient method of bundling image files for module ROM, FPGAs, operational, and POST images. Package files can be used to upgrade all the images on a module using a single command. Package files have the file name extension of ".PKG".

Use the boot package-file [1 | 2] command to burn the contents of the specified package file into the specified flash bank.

You can configure the boot flags for the module to control the module's behavior during startup.

Use the flags command to set the boot flags to be used when the module 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.

You can configure the type of messages regarding the modules that are forwarded to the logging system.

Use the logging-max-history max_files and the logging-filter system level commands to configure logging for the specified module.

Use the shutdown command to disable the module. The configuration information associated with the module in the running configuration file is not removed.

Use the no shutdown command to enable the module.

The following table summarizes the commands available in Module configuration command mode:

Table 3-4. Commands in Module Configuration Command Mode
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.

exit

Exit from module mode

fabric

Fabric functions.

help

Description of the interactive help system

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.

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

shutdown

Disable/enable a module (or module subsystem).

To remove a primary SAM with a backup SAM present, the CLI for warns the user that the module they are removing is a primary SAM:

router(config)#no module 1/37

This command will remove ALL configuration for module 1/37.

WARNING: ACTIVE SAM MODULE.

MODULE REMOVAL WILL TRANSITION TSR TO THE SECONDARY SAM MODULE 1/34.

Are you sure [yes|no]? yes

Removing module from configuration...

Successfully removed module from configuration.

To remove a primary SAM with no backup SAM present, the CLI warns the user that the module they are removing is a primary SAM with no backup SAM present:

router(config)#no module 1/37

This command will remove ALL configuration for module 1/37.

WARNING: ACTIVE SAM MODULE.

MODULE REMOVAL WILL CAUSE ALL MODULES TO REBOOT.

Proceed with the active SAM module removal [yes|no]? yes

Are you sure [yes|no]? yes

Removing module from configuration...

Successfully removed module from configuration.

To remove a backup SAM, the CLI warns the user that the module they are removing is a backup SAM:

router(config)#no module 1/34

This command will remove ALL configuration for module 1/34.

WARNING: SECONDARY SAM MODULE.

MODULE REMOVAL WILL TRANSITION TSR TO A SINGLE SAM MODULE CONFIGURATION.

Are you sure [yes|no]? yes

Removing module from configuration...

Successfully removed module from configuration.

To shut down a primary SAM with a backup SAM present, the CLI warns the user that the module they are deactivating is a primary SAM with a backup SAM present:

router(config-module)#shutdown

This command will disable module 1/34.

WARNING: ACTIVE SAM MODULE.

SHUTDOWN WILL TRANSITION TSR TO THE SECONDARY SAM MODULE 1/37.

Are you sure [yes|no]? yes

Disabling module...

To shut down a primary SAM with no backup SAM present, the CLI warns the user that the module they are deactivating is a primary SAM with no backup SAM present:

router(config)#module 1/37

router(config-module)#shutdown

This command will disable module 1/37.

WARNING: ACTIVE SAM MODULE.

SHUTDOWN WILL CAUSE ALL MODULES TO REBOOT.

Proceed with the active SAM module shutdown [yes|no]? yes

Are you sure [yes|no]? yes

Disabling module...

To shut down a backup SAM, the CLI warns the user that the module they are deactivating is a backup SAM:

router(config)#module 1/37

router(config-module)#shutdown

This command will disable module 1/37.

WARNING: SECONDARY SAM MODULE.

SHUTDOWN WILL TRANSITION TSR TO A SINGLE SAM MODULE CONFIGURATION.

Are you sure [yes|no]? yes

Disabling module...

Example 1: In the following example:

The module bay/slot type configures an 4xOC-12c module in slot 1/35, and changes the command mode to Module configuration.

The boot 2 command configures the module to boot from flash bank 2 at the next startup.

The no shutdown command enables the module.

The show module 1/35 command displays the new configuration:

router(config)#module 1/35 4xoc12c

router(config-module)#boot 2

router(config-module)#no shutdown

router(config-module)#exit

router#show module 1/35

MODULE 1/35:

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

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

Physical port type is multi mode fiber

Last started on WED AUG 11 16:15:59 1999

Administratively Up; Current state is Up

Max number of historical logging files: 5

Non-default logging filters:

transport information

Example 2: In the following example:

The dir command displays the name of a package file R0401020.PKG.

The module bay/slot type specifies a 16 port OC-3c module in slot 1 of bay 1, and changes the command mode to Module configuration.

The boot package-file 1 command extracts the image from the specified package file and burns it into position 1 of the module's flash bank.

router#dir

size date time name

-------- ------ ------ --------

512 DEC-09-1908 22:59:24 TRASH <DIR>

.

.

.

8653312 AUG-24-2001 11:29:32 R0401020.PKG

.

.

.

router#configure terminal

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

router(config)#module 1/1 16xoc3c

router(config-module)#boot R0401020.PKG 1

Burning operational image B:\TMP\rt412.cmp into location 1 for modules:

Reading image............Done

Sending image............Done

Waiting for responses:

Burn Results: 1 succeeded 0 failed

Example 3: In the following example:

The no module bay/slot command deletes the configuration for a module.

The prompt queries for confirmation.

NOTE You MUST enter the entire word "yes" to delete the configuration. If you enter a "y", the deletion is aborted.

router#con t

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

router(config)#no module 1/1

This command will remove ALL configuration for module 1/1.

Are you sure [yes|no]? yes

Removing module from configuration...

Successfully removed module from configuration.

Related Commands: dir
fpga activebank
fpga download
module all
show fpga module
show module

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. Module type is automatically sensed by the bay controller and entered into the running configuration file. If for any reason you wish to pre-configure a module slot prior to the physical installation of that module, you must provide the type field in the command line. Available types include: 1xoc48c - Assign a 1 port OC-48c module to the slot. 4xoc48c - Assign a 4 port OC-48c module to the slot. 2xoc48c - Assign a 2 port OC-48c module to the slot. 2x1gbe - Assign a 2 port Gigabit Ethernet module to the slot. 8x1gbe - Assign an 8 port Gigabit Ethernet module to the slot. 1x10gbe -Assign a 1 port 10 Gigabit Ethernet module to the slot. 4xoc3c - Assign a 4 port OC-3c module to the slot. 16xoc3c - Assign a 16 port OC-3c module to the slot 4xoc12c - Assign a 4 port OC-12c module to the slot. 1xoc192c - Assign a 1 port single-slot OC-192c module to the slot. 1xoc192c-a - Assign a 1 port dual-slot OC-192c module (1 of 2 module set) to the slot. 1xoc192c-b - Assign a 1 port dual-slot OC-192c module (2 of 2 module set) to the slot. 8xoc3-4xoc12msc - Assign an 8 port OC-3c, 4 port OC-12c Multi-service module to the slot. 16xoc3msc - Assign a 16 port OC-3c Multiservice Module to the slot. 8xoc12msc - Assign an 8 port OC-12c Multiservice module to the slot.

**Table 3-4.** Commands in Module Configuration Command Mode
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.
exit	Exit from module mode
fabric	Fabric functions.
help	Description of the interactive help system
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.
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).
shutdown	Disable/enable a module (or module subsystem).

router(config)#no module 1/37 This command will remove ALL configuration for module 1/37. WARNING: ACTIVE SAM MODULE. MODULE REMOVAL WILL TRANSITION TSR TO THE SECONDARY SAM MODULE 1/34. Are you sure [yes\|no]? yes Removing module from configuration... Successfully removed module from configuration.

router(config)#no module 1/37 This command will remove ALL configuration for module 1/37. WARNING: ACTIVE SAM MODULE. MODULE REMOVAL WILL CAUSE ALL MODULES TO REBOOT. Proceed with the active SAM module removal [yes\|no]? yes Are you sure [yes\|no]? yes Removing module from configuration... Successfully removed module from configuration.

router(config)#no module 1/34 This command will remove ALL configuration for module 1/34. WARNING: SECONDARY SAM MODULE. MODULE REMOVAL WILL TRANSITION TSR TO A SINGLE SAM MODULE CONFIGURATION. Are you sure [yes\|no]? yes Removing module from configuration... Successfully removed module from configuration.

router(config-module)#shutdown This command will disable module 1/34. WARNING: ACTIVE SAM MODULE. SHUTDOWN WILL TRANSITION TSR TO THE SECONDARY SAM MODULE 1/37. Are you sure [yes\|no]? yes Disabling module...

router(config)#module 1/37 router(config-module)#shutdown This command will disable module 1/37. WARNING: ACTIVE SAM MODULE. SHUTDOWN WILL CAUSE ALL MODULES TO REBOOT. Proceed with the active SAM module shutdown [yes\|no]? yes Are you sure [yes\|no]? yes Disabling module...

router(config)#module 1/37 router(config-module)#shutdown This command will disable module 1/37. WARNING: SECONDARY SAM MODULE. SHUTDOWN WILL TRANSITION TSR TO A SINGLE SAM MODULE CONFIGURATION. Are you sure [yes\|no]? yes Disabling module...

router(config)#module 1/35 4xoc12c router(config-module)#boot 2 router(config-module)#no shutdown router(config-module)#exit router#show module 1/35 MODULE 1/35: Discovered (4xOC12c) 4 Port Packet Over SONET OC-12c/STM-4c Configured (4xOC12c) 4 Port Packet Over SONET OC-12c/STM-4c Physical port type is multi mode fiber Last started on WED AUG 11 16:15:59 1999 Administratively Up; Current state is Up Max number of historical logging files: 5 Non-default logging filters: transport information

router#dir size date time name -------- ------ ------ -------- 512 DEC-09-1908 22:59:24 TRASH <DIR> . . . 8653312 AUG-24-2001 11:29:32 R0401020.PKG . . .
router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)#module 1/1 16xoc3c router(config-module)#boot R0401020.PKG 1 Burning operational image B:\TMP\rt412.cmp into location 1 for modules: Reading image............Done Sending image............Done Waiting for responses: Burn Results: 1 succeeded 0 failed

router#con t Enter configuration commands, one per line. End with CNTL/Z.
router(config)#no module 1/1 This command will remove ALL configuration for module 1/1. Are you sure [yes\|no]? yes Removing module from configuration... Successfully removed module from configuration.

   Source File Name: sys_mgmt.fm
    HTML File Name: sys_mgmt26.html
    Last Updated: 02/25/05 at 14:26:49

module

Please email suggestions and comments to: doc@avici.com