The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the Cisco Nexus 1000V commands that begin with the letter, B.
To set the inherited and received bandwidth for an interface, use the bandwidth command. To restore the default value, use the no form of this command.
Intended bandwidth, in kilobits per second. Valid values are 1 to 10000000. |
Interface configuration (config-if)
|
|
---|---|
The bandwidth command sets an informational parameter to communicate only the current bandwidth to the higher-level protocols; you cannot adjust the actual bandwidth of an interface using this command.
Note This is a routing parameter only. It does not affect the physical interface.
This example shows how to configure the bandwidth 30000 kbps:
|
|
---|---|
To set the minimum guaranteed bandwidth for a specific traffic class in a QoS policy map, use the bandwidth command. To remove this configuration, use the no form of this command.
no bandwidth percent percentage
Specify a percentage (1 - 100) of total bandwidth guaranteed. |
Policy map class queuing configuration (config-pmap-c-que).
|
|
The bandwidth command is used to control the bandwidth allocated to a class of traffic. The bandwidth command must explicitly be configured on a class, if desired. Bandwidth is configurable between 1% and 100%.
This example shows how to configure 20% minimum guaranteed bandwidth for the class_fin1 traffic class.
This example shows how to remove the configured bandwidth for the class_fin1 traffic class.
|
|
---|---|
Creates a class-based weighted fair queueing (CBWFQ) policy map. |
|
Assigns a class-based weighted fair queueing (CBWFQ) class to the specified policy map. |
|
To configure a message of the day (MOTD) banner, use the banner motd command.
banner motd [ delimiting-character message delimiting-character ]
no banner motd [ delimiting-character message delimiting-character ]
“User Access Verification” is the default message of the day.
|
|
---|---|
The MOTD banner is displayed on the terminal before the login prompt whenever you log in.
The message is restricted to 40 lines and 80 characters per line.
To create a multiple-line MOTD banner, press Enter before typing the delimiting character to start a new line. You can enter up to 40 lines of text.
Follow these guidelines when choosing your delimiting character:
This example shows how to configure and then display a banner message with the text, “Testing the MOTD.”
This example shows how to configure and then display a multiple-line MOTD banner:
This example shows how to revert to the default MOTD banner:
|
|
---|---|
To enable automatic copying of boot image files to the standby supervisor module, use the boot auto-copy command. To disable automatic copying, use the no form of this command.
|
|
---|---|
When automatic copying of image files is enabled, the Cisco NX-OS software copies the image files referred to by the boot variable to the standby supervisor module. These image files must be present in local memory on the active supervisor module. For kickstart and system boot variables, only those image files that are configured for the standby supervisor module are copied.
This example shows how to enable automatic copying of boot image files to the standby supervisor module:
|
|
---|---|
To configure the boot variable for the kickstart image, use the boot kickstart command. To clear the kickstart image boot variable, use the no form of this command.
boot kickstart [ filesystem: [ //directory ] | directory ] filename [ sup-1 ] [ sup-2 ]
Configures the kickstart boot variable for both supervisor modules.
|
|
---|---|
The kickstart boot variable is used for loading software images when booting up. You must copy the kickstart image to the device before you reload.
This example shows how to configure the kickstart boot variable for both supervisor modules:
This example shows how to configure the kickstart boot variable for the active supervisor module:
This example shows how to clear the kickstart boot variable:
|
|
---|---|
To configure the boot variable for the system image, use the boot system command. To clear the system image boot variable, use the no form of this command.
boot system [ filesystem: [ //directory ] | directory ] filename [ sup-1 ] [ sup-2 ]
Configures the system boot variable for both supervisor modules.
|
|
---|---|
The system boot variable is used for loading images when booting up. You must copy the system image to the device before you reload.
This example shows how to configure the system boot variable for both supervisor modules:
This example shows how to configure the system boot variable for the sup-1 supervisor module:
This example shows how to clear the system boot variable:
|
|
---|---|
Configures the boot variable for the kickstart software image. |
|
To create a VXLAN and associate an identifying name to it, use the bridge-domain command. To remove a VXLAN, use the no form of this command.
|
|
This example shows how to create a VXLAN:
n1000v(config)# bridge-domain tenant-red
|
|
---|---|