- New and Changed Information
- Preface
- A Commands
- Advanced Services Modules Commands
- B Commands
- C Commands
- Caching Services Module Commands
- CLI Overview
- D Commands
- Debug Commands
- E Commands
- F Commands
- G Commands
- H Commands
- I Commands
- J Commands
- K Commands
- L Commands
- M Commands
- N Commands
- O Commands
- P Commands
- Q Commands
- R Commands
- S Commands
- Show Commands
- T Commands
- U Commands
- V Commands
- W Commands
- Z Commands
B Commands
The commands in this chapter apply to the Cisco MDS 9000 Family of multilayer directors and fabric switches. All commands are shown here in alphabetical order regardless of command mode. See the “About the CLI Command Modes” section to determine the appropriate mode for each command.
banner motd
To configure a message of the day (MOTD) banner, use the banner motd command in configuration mode.
banner motd [ delimiting-character message delimiting-character ]
no banner motd [ delimiting-character message delimiting-character ]
Syntax Description
(Optional) Specifies the banner message that is restricted to 40 lines with a maximum of 80 characters in each line. |
Defaults
Command Modes
Command History
|
|
---|---|
Usage Guidelines
The configured MOTD banner is displayed before the login prompt on the terminal whenever a user logs in to a Cisco MDS 9000 Family switch.
Follow these guidelines when choosing your delimiting character:
You can include tokens in the form $(token) in the message text. Tokens will be replaced with the corresponding configuration variable. For example:
Examples
The following example configures a banner message with the following text “Testing the MOTD Feature:
The following example spans multiple lines and uses tokens to configure the banner message:
Enter TEXT message. End with the character '#'.
Welcome to switch $(hostname).
You tty line is $(line).
#
Related Commands
|
|
---|---|
boot
To perform operations on the system, use the boot command in configuration mode. To negate this feature or return to factory defaults, use the no form of the command.
boot { asm-sfn { bootflash: | slot0: | tftp: } [ image ] [ module [ slot-number ]] | auto-copy | kickstart { bootflash: | slot0: | tftp: } [ image ] [sup-1 [sup-2] | sup-2] | lasilc { bootflash: | slot0: | tftp: } [ image ] [ module [ slot-number ]] | ssi { bootflash: | slot0: } | system { bootflash: | slot0: | tftp: } [ image ] [sup-1 [sup-2] | sup-2] }
no boot { asm-sfn { bootflash: | slot0: | tftp: } [ image ] [ module [ slot-number ]] | auto-copy | kickstart { bootflash: | slot0: | tftp: } [ image ] [sup-1 [sup-2] | sup-2] | lasilc { bootflash: | slot0: | tftp: } [ image ] [ module [ slot-number ]] | ssi { bootflash: | slot0: } | system { bootflash: | slot0: | tftp: } [ image ] [sup-1 [sup-2] | sup-2] }
Syntax Description
Command Modes
Command History
|
|
---|---|
Usage Guidelines
The boot kickstart slot0: image command is currently not allowed. For kickstart, only bootflash: is allowed.
You enter the boot auto-copy command, the system copies the boot variable images that are local (present) in the active supervisor module (but not in the standby supervisor module) to the standby supervisor module. For kickstart and system boot variables, only those images that are set for the standby supervisor module are copied. For modules (line card) images, all modules present in standby's corresponding locations (bootflash: or slot0:) are copied.
Examples
The following example adds the new system image file to the SYSTEM environment variable:
The following example boots from the CompactFlash device (slot0:). The switch updates the SYSTEM environment variable to reflect the new image file in the specified flash device:
The following example overwrites the old Kickstart environment variable in the configuration file:
The following example specifies the SSM image to be used:
The following example enables automatic copying of boot variables from the active supervisor module to the standby supervisor module:
The following example disables the automatic copy feature (default):
Related Commands
|
|
---|---|
bport
To configure a B port mode on a FCIP interface, use the bport option. To disable a B port mode on a FCIP interface, use the no form of the command.
Syntax Description
Defaults
Command Modes
Interface configuration submode
Command History
|
|
---|---|
Usage Guidelines
Examples
The following example shows how to configure a B port mode on an FCIP interface:
Related Commands
|
|
---|---|
Displays an interface configuration for a specified FCIP interface. |
bport-keepalive
To configure keepalive responses for B port FCIP interfaces, use the bport-keepalive option. To disable keepalive responses for B port FCIP interfaces, use the no form of the command.
Syntax Description
Defaults
Command Modes
Interface configuration submode
Command History
|
|
---|---|
Usage Guidelines
Examples
The following example shows how to configure keepalive responses for B port FCIP interfaces:
Related Commands
|
|
---|---|
Displays an interface configuration for a specified FCIP interface. |
broadcast
To enable the broadcast frames attribute in a zone attribute group, use the broadcast command. To revert to the default, use the no form of the command.
Syntax Description
Defaults
Command Modes
Zone attribute configuration submode
Command History
|
|
Usage Guidelines
Broadcast frames are sent to all Nx ports.
If any NL port attached to an FL port shares a broadcast zone with the source of the broadcast frame,
then the frames are broadcast to all devices in the loop.
This command only configures the broadcast attribute for enhanced zoning. To enable broadcast zoning for basic mode, use the attribute broadcast subcommand after entering zone configuration mode using the zone name command.
Examples
The following example shows how to set the broadcast attribute for a zone attribute group:
Related Commands
|
|
---|---|