To acknowledge a chassis, use the acknowledge chassis command.
acknowledge chassis id
id | Chassis identification number. The range of valid values is 1 to 255. |
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to verify the existence of devices in your network. For example, you can acknowledge a chassis that was recently commissioned, to ensure that it exists.
This example shows how to acknowledge a chassis:
switch-A# acknowledge chassis 10 switch-A* # commit-buffer switch-A #
Command |
Description |
show chassis |
|
show server |
|
To acknowledge a fault, use the acknowledge fault command.
acknowledge fault id
id | Fault identification number. The range of valid values is 0 to 9223372036854775807. |
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
The following example shows how to acknowledge a fault:
switch-A# acknowledge fault 1 switch-A* # commit-buffer switch-A #
Command |
Description |
show cli |
|
show fault |
|
To acknowledge a server, use the acknowledge server command.
acknowledge server { chassis-id / blade-id | slot-id }
chassis-id / blade-id | Chassis and blade identification numbers. |
slot-id | Slot identification number. The range of valid values is 1 to 8. |
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to verify the existence of devices in your network. For example, you can acknowledge a server that was recently commissioned, to ensure that it exists. slot -id is used only in /chassis mode.
The following example shows how to acknowledge a server in /chassis mode:
switch-A# scope chassis 1 switch-A /chassis # acknowledge server 2 switch-A /chassis* # commit-buffer switch-A /chassis #
Command |
Description |
show chassis |
|
show server |
|
To acknowledge a slot, use the acknowledge slot command.
acknowledge slot { chassis-id / blade-id | slot-id }
chassis-id / blade-id | Sever identification number. |
slot-id | Slot identification number. The range of valid values is 1 to 8. |
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to verify the existence of devices in your network. For example, you can acknowledge a chassis that was recently commissioned using slot -id , to ensure that it exists. slot -id is used only in /chassis mode.
The following example shows how to acknowledge a slot in /chassis mode:
switch-A# scope chassis 1 switch-A /chassis # acknowledge slot 1 switch-A /chassis* # commit-buffer switch-A /chassis #
Command |
Description |
show server |
|
show slot |
|
To activate firmware for a device, use the activate firmware command.
activate firmware version { kernel-version kernel-version [ignorecompcheck] | system-version system-version [ignorecompcheck] } +
kernel-version | Specifies switch kernel version firmware. |
kernel-version | Kernel version. |
system-version | Specifies switch system version firmware. |
system-version | System version. |
ignorecompcheck | (Optional) Specifies a compatability check. |
None
Input output module (/chassis/iom)
System (/system)
Fabric interconnect (/fabric)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use the ignorecompcheck keyword to run a compatability check when you activate the firmware.
The following example shows how to activate a specific version of software:
switch-A# scope fabric a switch-A /fabric # activate firmware kernel-version 3.0 ignorecompcheck switch-A /fabric* # commit-buffer switch-A /fabric #
Command |
Description |
show firmware |
|
show version |
|
To add more alert groups to a Call Home profile, use the add alertgroups command.
add alertgroups [ ciscotac ] [ diagnostic ] [ environmental ] [ inventory ] [ license ] [ lifecycle ] [ linecard ] [ supervisor ] [ syslogport ] [ system ] [ test ] +
ciscotac | Specifies the Cisco Technical Assistance Center (TAC) alert group. |
diagnostic | Specifies the diagnostic alert group. |
environmental | Specifies the environmental alert group. |
inventory | Specifies the inventory alert group. |
license | Specifies the license alert group. |
lifecycle | Specifies the lifecycle alert group. |
linecard | Specifies the line card alert group. |
supervisor | Specifies the supervisor alert group. |
syslogport | Specifies the syslog port alert group. |
system | Specifies the system alert group. |
test | Specifies the test alert group. |
None
Profile (/monitoring/callhome/profile)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to add more predefined Call Home alert groups to an existing alert group list within a Call Home profile.
This example shows how to add diagnostic and license alert groups to an existing Call Home profile:
switch-A# scope monitoring switch-A /monitoring # scope callhome switch-A /monitoring/callhome # scope profile profileOne switch-A /monitoring/callhome/profile # add alertgroups diagnostic license switch-A /monitoring/callhome/profile* # commit-buffer switch-A /monitoring/callhome/profile #
Command |
Description |
remove alertgroups |
|
set alertgroups |
|
To add an additional action or actions that will trigger a backup of the system event log, use the add backup actioncommand.
add backup action [log-full] [none] [on-change-of-association] [on-clear] [timer]
log-full | Specifies that the log is backed up when it is full. |
none | Specifies no action. |
on-change-of-association | Specifies that the log is backed up when the server changes associations. |
on-clear | Specifies that the log is backed up when it is cleared. |
timer | Specifies that the log is backed up at an interval. |
None
Endpoint log policy (/org/ep-log-policy)
Release | Modification |
---|---|
1.1(1) | This command was introduced. |
Use this command to add an additional action or actions that will trigger a backup of the system event log. Previously configured actions are retained.
This example shows how to add an action to trigger a backup of the system event log when the log is full:
switch-A# scope org switch-A /org # scope ep-log-policy sel switch-A /org/ep-log-policy # add backup action log-full switch-A /org/ep-log-policy* # commit-buffer switch-A /org/ep-log-policy #
Command |
Description |
remove backup action |
|
set backup action |
|
show backup |
|
To add privileges, use the add privilege command.
add privilege { aaa | admin | ext-lan-config | ext-lan-policy | ext-lan-qos | ext-lan-security | ext-san-config | ext-san-policy | ext-san-qos | ext-san-security | fault | service-profile-config | service-profile-config-policy | service-profile-network | service-profile-network-policy | service-profile-qos | service-profile-qos-policy | service-profile-security | service-profile-security-policy | service-profile-server | service-profile-server-policy | service-profile-storage | service-profile-storage-policy | operations | server-equipment | server-maintenance | server-policy | server-security | pod-config | pod-policy | pod-qos | pod-security | read-only } +
aaa | Specifies AAA privileges. |
admin | Specifies admin privileges. |
ext-lan-config | Specifies external LAN configuration priveleges. |
ext-lan-policy | Specifies external LAN policy privileges. |
ext-lan-qos | Specifies external LAN QoS privileges. |
ext-lan-security | Specifies external LAN security privileges. |
ext-san-config | Specifies external SAN configuration privileges. |
ext-san-policy | Specifies external SAN policy privileges. |
ext-san-qos | Specifies external SAN QoS privileges. |
ext-san-security | Specifies external SAN security privileges. |
fault | Specifies fault privileges. |
service-profile-config | Specifies service profile configuration privileges. |
service-profile-config-policy | Specifies service profile configuration policy privileges. |
service-profile-network | Specifies service profile network privileges. |
service-profile-network-policy | Specifies service profile network policy privileges. |
service-profile-qos | Specifies service profile QoS privileges. |
service-profile-qos-policy | Specifies service profile QoS policy privileges. |
service-profile-security | Specifies service profile security privileges. |
service-profile-security-policy | Specifies service profile security policy privileges. |
service-profile-server | Specifies service profile server privileges. |
service-profile-server-policy | Specifies service profile server policy privileges. |
service-profile-storage | Specifies service profile storage privileges. |
service-profile-storage-policy | Specifies service profile storage policy privileges. |
operations | Specifies operations privileges. |
server-equipment | Specifies server equipment privileges. |
server-maintenance | Specifies server maintenance privileges. |
server-policy | Specifies server policy privileges. |
server-security | Specifies server security privileges. |
pod-config | Specifies pod configuration privileges. |
pod-policy | Specifies pod policy privileges. |
pod-qos | Specifies pod QoS privileges. |
pod-security | Specifies pod security privileges. |
read-only | Specifies read-only privileges. |
None
Role (/security/role)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to add privileges:
switch-A # scope security switch-A /security # scope role role1 switch-A /security/role # add privilege ext-san-config ext-san-policy ext-san-qos ext-san-security switch-A /security/role* # commit-buffer switch-A /security/role #
To associate a server, use the associate server command.
associate server chassis-id/blade-id
chassis-id/blade-id | Chassis and blade identification numbers. The range of valid values is 1 to 4294967295. |
None
Service profile (/org/service-profile)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to associate a server:
switch-A# scope org 1 switch-A /org # scope service-profile 1 switch-A /org/service-profile # associate server 1 switch-A /org/service-profile* # commit-buffer switch-A /org/service-profile #
Command |
Description |
show assoc |
|
show server |
|
To associate a server pool with a service profile, use the associate server-pool command.
associate server-pool server-pool [name]
server-pool | Server pool name. The range of valid values is 1 to 16. |
name | (Optional) Qualifier. The range of valid values is 1 to 16. |
None
Service profile (/org/service-profile)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to associate a server pool:
switch-A# scope org 1 switch-A /org # scope service-profile 1 switch-A /org/service-profile # associate server-pool 1 switch-A /org/service-profile* # commit-buffer switch-A /org/service-profile #
Command |
Description |
show assoc |
|
show server |
|
To back up the system event log (SEL), use the backup sel command.
backup sel server-id
server-id | Specifies the chassis number and server number in the format A/B. |
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to back up the system event log (SEL) for a server. When entering this command in the command mode of the specific server (/chassis/server), do not enter the server-id .
This example shows how to back up the SEL for server 4 in chassis 2:
switch-A# backup sel 2/4 switch-A* # commit-buffer switch-A#
Command |
Description |
|
|
To change directories, use the cd command in local management command mode.
cd { workspace: | [path] | volatile: | [path] | | [path] }
workspace: | Specifies the workspace (flash) directory. |
volatile: | Specifies the volatile directory. |
path | Absolute or relative path. |
None
Local management (local-mgmt)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
1.1(1) | This command was modified. The bootflash: keyword is replaced by the workspace: keyword. |
This command is available on the local management port command line. Use the connect local-mgmt command to connect to that command line.
This command operates on either the workspace (FLASH) or volatile (RAM) file system. To specify the file system, include the workspace: or volatile: keyword in the path. If the file system is not specified, the current working file system is assumed.
This example shows how to change directories:
switch-A# connect local-mgmt a Cisco UCS 6100 Series Fabric Interconnect TAC support: http://www.cisco.com/tac Copyright (c) 2009, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained herein are owned by other third parties and are used and distributed under license. Some parts of this software may be covered under the GNU Public License or the GNU Lesser General Public License. A copy of each such license is available at http://www.gnu.org/licenses/gpl.html and http://www.gnu.org/licenses/lgpl.html switch-A(local-mgmt)# cd volatile:/temp Pubs-A(local-mgmt)# pwd volatile:temp switch-A(local-mgmt)#
To clear all selected alert groups in a Call Home profile, use the clear alertgroups command.
clear alertgroups
This command has no arguments or keywords.
None
Profile (/monitoring/callhome/profile)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to clear any previously configured alert group list within the Call Home profile.
This example shows how to clear alert groups in a Call Home profile:
switch-A# scope monitoring switch-A /monitoring # scope callhome switch-A /monitoring/callhome # scope profile profileOne switch-A /monitoring/callhome/profile # clear alertgroups switch-A /monitoring/callhome/profile* # commit-buffer switch-A /monitoring/callhome/profile #
Command |
Description |
set alertgroups |
|
show policy |
|
show profile |
|
To clear all selected actions that will trigger a backup of the system event log, use the clear backup actioncommand.
clear backup action
This command has no arguments or keywords.
None
Endpoint log policy (/org/ep-log-policy)
Release | Modification |
---|---|
1.1(1) | This command was introduced. |
Use this command to delete any previously configured list of actions that will trigger a backup of the system event log.
This example shows how to clear all selected actions that will trigger a backup of the system event log:
switch-A# scope org switch-A /org # scope ep-log-policy sel switch-A /org/ep-log-policy # clear backup action switch-A /org/ep-log-policy* # commit-buffer switch-A /org/ep-log-policy #
Command |
Description |
set backup action |
|
show backup |
|
To clear core files, use the clear cores command.
clear cores
This command has no arguments or keywords.
None
Sysdebug (/monitoring/sysdebug)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Core files are records of core dumps. Use the clear cores command to clear information out of core dump records.
This example shows how to clear core files:
switch-A# scope monitoring switch-A /monitoring # scope sysdebug switch-A /monitoring/sysdebug # clear cores switch-A /monitoring/sysdebug # commit-buffer switch-A /monitoring/sysdebug #
Command |
Description |
show alert-groups |
|
show cores |
|
To remove a license, use the clear license command in local management command mode.
clear license license-file-name [force]
license-file-name | The name of a license file. |
force | (Optional) |
None
Local management (local-mgmt)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to remove a license in local management command mode.
This command can be executed only on local fabric interconnect and only by the user admin.
This command is available on the local management port command line. Use the connect local-mgmt command to connect to that command line.
This example shows how to remove a license:
switch-A# connect local-mgmt a Cisco UCS 6100 Series Fabric Interconnect TAC support: http://www.cisco.com/tac Copyright (c) 2009, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained herein are owned by other third parties and are used and distributed under license. Some parts of this software may be covered under the GNU Public License or the GNU Lesser General Public License. A copy of each such license is available at http://www.gnu.org/licenses/gpl.html and http://www.gnu.org/licenses/lgpl.html switch-A(local-mgmt)# clear license FibreChannel.lic Clearing license FibreChannel.lic: SERVER this_host ANY VENDOR cisco Enter yes (yes is the default) to continue with the license update. Do you want to continue? (y/n) y Clearing license ..done switch-A(local-mgmt)#
Command |
Description |
connect local-mgmt |
|
show license brief |
|
To clear the contents of the system event log (SEL), use the clear sel command.
clear sel
This command has no arguments or keywords.
None
Server (/chassis/server)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to clear the contents of the system event log (SEL).
This example shows how to clear the contents of the SEL:
switch-A# scope server 2/4 switch-A /chassis/server # clear sel switch-A /chassis/server* # commit-buffer switch-A /chassis/server #
Command |
Description |
show sel |
|
To clear from cache the SSH public key of a remote host, use the clear sshkey command in local management mode.
clear sshkey host-name
host-name | Host name or IP address. Specify the IP address in the format A.B.C.D. |
None
Local management (local-mgmt)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to clear from cache the SSH public key of a remote host that supports SSH.
This command is available on the local management port command line. Use the connect local-mgmt command to connect to that command line.
This example shows how to clear the SSH public key of a remote host:
switch-A # connect local-mgmt a Cisco UCS 6100 Series Fabric Interconnect TAC support: http://www.cisco.com/tac Copyright (c) 2009, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained herein are owned by other third parties and are used and distributed under license. Some parts of this software may be covered under the GNU Public License or the GNU Lesser General Public License. A copy of each such license is available at http://www.gnu.org/licenses/gpl.html and http://www.gnu.org/licenses/lgpl.html switch-A(local-mgmt)# clear sshkey 192.0.2.111 switch-A(local-mgmt)#
Command |
Description |
connect local-mgmt |
|
To force a cluster to be the primary cluster, use the cluster force primary command.
cluster force primary
This command has no arguments or keywords.
None
Local management (local-mgmt)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
The cluster commands are switch-specific local management commands. You have to execute a connect local-mgmt command to connect to the management port.
This example shows how to force a cluster to be the primary cluster:
switch-A# connect local-mgmt Nexus 5000 Switch Cisco UCS 6100 Series Fabric Interconnect TAC support: http://www.cisco.com/tac Copyright (c) 2009, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained herein are owned by other third parties and are used and distributed under license. Some parts of this software may be covered under the GNU Public License or the GNU Lesser General Public License. A copy of each such license is available at http://www.gnu.org/licenses/gpl.html and http://www.gnu.org/licenses/lgpl.html switch-A# cluster force primary switch-A#
Command |
Description |
show cluster |
|
show file |
|
To designate a cluster leader, use the cluster lead command.
cluster lead [ a | b ]
a | Specifies switch A. |
b | Specifies switch B. |
None
Local management (local-mgmt)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
The cluster commands are switch-specific local management commands. You must first execute a connect local-mgmt command to connect to the management port.
This example shows how to designate a cluster leader:
switch-A# connect local-mgmt Nexus 5000 Switch Cisco UCS 6100 Series Fabric Interconnect TAC support: http://www.cisco.com/tac Copyright (c) 2009, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained herein are owned by other third parties and are used and distributed under license. Some parts of this software may be covered under the GNU Public License or the GNU Lesser General Public License. A copy of each such license is available at http://www.gnu.org/licenses/gpl.html and http://www.gnu.org/licenses/lgpl.html switch-A# cluster lead b switch-A#
Command |
Description |
show cluster |
|
show files |
|
To save or verify configuration changes, use the commit-buffer command.
commit-buffer [verify-only]
verify-only | (Optional) Specifies verification only. |
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to execute all pending configuration changes. While any configuration commands are pending, an asterisk (*) appears before the command prompt. When you enter the commit-buffer command, the pending commands are committed and the asterisk disappears.
This example shows how to save configuration changes:
switch-A# create org 3 switch-A /org* # commit-buffer switch-A /org #
Command |
Description |
discard-buffer |
|
show configuration pending |
|
To connect to an adapter, use the connect adapter command.
connect adapter chassis-id/server-id/adapter-id
chassis-id/server-id/adapter-id | Adapter identification number. |
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to connect to an adapter:
switch-A# connect adapter 1/1/1 adapter 1/1 #
To connect to the BMC (Baseboard Management Controller), use the connect bmc command.
connect bmc chassis-id/blade-id
chassis-id/blade-id | Chassis and blade identification numbers. |
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
The following example shows how to connect to the Baseboard Management Controller:
switch-A# connect bmc 1/1 Trying 127.5.1.1... Connected to 127.5.1.1. Escape character is '^]'. NUOVA-IBMC login:
To connect to DMTF CLP, use the connect clp command.
connect clp
This command has no arguments or keywords.
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to connect to DMTF CLP:
switch-A# connect clp /admin1 CLP ->
To connect to an IO module, use the connect iom command.
connect iom id
id | Chassis identification number. The valid range of values is 1 to 255. |
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to connect to a IO module:
switch-A# connect iom 1 Attaching to FEX 1 ... To exit type 'exit', to abort type '$.' fex-1#
To connect to the local management port, use the connect local-mgmt command.
connect local-mgmt [ a | b ]
a | Specifies switch A. |
b | Specifies switch B. |
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
If no switch is specified, a connection will be made to the local management port of the current active switch.
This example shows how to connect to the local management port of switch B:
switch-A# connect local-mgmt b Cisco UCS 6100 Series Fabric Interconnect TAC support: http://www.cisco.com/tac Copyright (c) 2009, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained herein are owned by other third parties and are used and distributed under license. Some parts of this software may be covered under the GNU Public License or the GNU Lesser General Public License. A copy of each such license is available at http://www.gnu.org/licenses/gpl.html and http://www.gnu.org/licenses/lgpl.html switch-B(local-mgmt)#
To connect to the NX-OS, use the connect nxos command.
connect nxos [a | b]
a | (Optional) Specifies switch A. |
b | (Optional) Specifies switch B. |
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to NXOS:
switch-A-A# connect nxos b Nexus 5000 Switch Cisco UCS 6100 Series Fabric Interconnect TAC support: http://www.cisco.com/tac Copyright (c) 2009, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained herein are owned by other third parties and are used and distributed under license. Some parts of this software may be covered under the GNU Public License or the GNU Lesser General Public License. A copy of each such license is available at http://www.gnu.org/licenses/gpl.html and http://www.gnu.org/licenses/lgpl.html switch-B#
To copy a file from one directory to another, use the copy command in local management command mode.
copy [from-filesystem:] [from-path] filename [to-filesystem:] to-path [dest-filename]
from-filesystem: | File system containing the file to be copied. See the Usage Guidelines for valid values. |
from-path | Absolute or relative path to the file to be copied. |
filename | The name of the source file to be copied. |
to-filesystem: | File system to contain the copied file. See the Usage Guidelines for valid values. |
to-path | Absolute or relative path to the copied file. |
dest-filename | (Optional) The new name for the copied file. |
None
Local management (local-mgmt)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to copy a file in local management command mode.
If a dest-filename is specified, the copied file is renamed at the destination location.
If no file system is specified, the current working file system is assumed. If no path is specified, the current working directory is assumed.
To specify the file system location, use the appropriate syntax from the following table:
ftp: [ // [ username@ ] server ]
scp: [ // [ username@ ] server ]
sftp: [ // [ username@ ] server ]
tftp: [ //server [ :port ] ]
volatile:
workspace:
Either the source or destination file system must be local; you cannot copy a file from one remote file system to another.
If a remote protocol is specified with no server name, you are prompted to enter the server name.
This command is available on the local management port command line. Use the connect local-mgmt command to connect to that command line.
This command operates on either the workspace (FLASH) or volatile (RAM) file system. To specify the file system, include the workspace: or volatile: keyword in the path. If the file system is not specified, the current working file system is assumed.
You can use the cp command as an alias for this command.
This example shows how to copy a file from the current working directory to a directory in the volatile file system:
switch-A # connect local-mgmt a Cisco UCS 6100 Series Fabric Interconnect TAC support: http://www.cisco.com/tac Copyright (c) 2009, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained herein are owned by other third parties and are used and distributed under license. Some parts of this software may be covered under the GNU Public License or the GNU Lesser General Public License. A copy of each such license is available at http://www.gnu.org/licenses/gpl.html and http://www.gnu.org/licenses/lgpl.html switch-A(local-mgmt)# copy abcdef.bin volatile:/temp switch-A(local-mgmt)#
Command |
Description |
connect local-mgmt |
|
To create an adapter, use the create adapter command.
create adapter
This command has no arguments or keywords.
None
Server qualification (/org/server-qual)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to create an adapter:
switch-A# scope org org3 switch-A /org # scope server-qual sq2 switch-A /org/server-qual # create adapter switch-A /org/server-qual/adapter* # commit-buffer switch-A /org/server-qual/adapter #
Command |
Description |
show adapter |
|
show chassis |
|
To create a backup, use the create backup command.
create backup file { all-configuration | logical-configuration | system-configuration | full-state } { disabled | enabled }
file | Managment file name. Use one of the following keywords for file type: ftp, scp, sftp, or tftp. |
all-configuration | Specifies a server, fabric, and system-related configuration backup. |
logical-configuration | Specifies a server and fabric backup. |
system-configuration | Specifies a system-related configuration backup. |
full-state | Specifies a full state backup for disaster recovery. |
disabled | Specifies disabled. |
enabled | Specifies enabled. |
None
System (/system)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
No more than one backup can be created and committed.
When you specify disabled, backup functionality is disabled. When you specify enabled, backup functionality is enabled.
This example shows how to create a backup:
switch-A# scope system switch-A /system # create backup ftp: full-state enabled Password: switch-A /system/backup* # commit-buffer switch-A /system/backup #
Command |
Description |
show backup |
|
show image |
|
To create a block, use the create block command.
IP pool configuration create block from to default-gw subnet-mask
WWN pool, UUID pool, and MAC pool configuration create block from to
from | From address, identifier, or world-wide name. Specify a MAC address in the format NN:NN:NN:NN:NN:NN. Specify a UUID in the format NNNN-NNNNNNNNNNNN. Specify a WWN in the format HH:HH:HH:HH:HH:HH:HH:HH. Specify an IP address in the format A.B.C.D. |
to | To address, identifier, or world-wide name. Specify a MAC address in the format NN:NN:NN:NN:NN:NN. Specify a UUID in the format NNNN-NNNNNNNNNNNN. Specify a WWN in the format HH:HH:HH:HH:HH:HH:HH:HH. Specify an IP address in the format A.B.C.D. |
default-gw | Default gateway. |
subnet-mask | Subnet mask. |
None
IP pool (/org/ip-pool)
WWN pool (/org/wwn-pool)
UUID suffix pool (/org/uuid-suffix-pool)
MAC pool (/org/mac-pool)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create addresses, identifiers, and world-wide names.
Use IP pool configuration mode to create IP address blocks. Use WWN pool, UUID pool, and MAC pool configuration mode to create addresses, UUIDs, and WWNs.
This example shows how to create a block:
switch-A# scope org org3 switch-A /org # scope mac-pool mp1 switch-A /org/mac-pool # create block 1a:2b:3c:4d:21:31 1b:2a:3c:4d:21:31 switch-A /org/mac-pool* # commit-buffer switch-A /org/mac-pool #
Command |
Description |
show mac-pool |
|
show pooled |
|
To create a boot definition, use the create boot-definition command.
create boot-definition
This command has no arguments or keywords.
None
Service profile (/org/service-profile)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to create a boot definition:
switch-A# scope org org3 switch-A /org # scope service-profile sp1 switch-A /org/service-profile # create boot-definition switch-A /org/service-profile/boot-definition* # commit-buffer switch-A /org/service-profile/boot-definition #
Command |
Description |
show boot-definition |
|
show lan |
|
To create a boot policy, use the create boot-policy command.
create boot-policy name purpose { operational | utility } *
name | Policy name. The range of valid values is 1 to 16. |
purpose | Specifies the purpose of the policy. |
operational | Specifies an operational policy. |
utility | Specifies a utility policy. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to create a boot policy:
switch-A# scope org org3 switch-A /org # create boot-policy boot1 switch-A /org/boot-policy* #commit-buffer switch-A /org/boot-policy #
Command |
Description |
show lan |
|
show virtual-media |
|
To create an capacity qualification, use the create cap-qual command.
create cap-qual { fcoe | non-virtualized-eth-if | non-virtualized-fc-if | path-encap-consolidated | path-encap-virtual | protected-eth-if | protected-fc-if | protected-fcoe | virtualized-eth-if | virtualized-fc-if | virtualized-scsi-if }
fcoe | Specifies Fibre Channel over Ethernet. |
non-virtualized-eth-if | Specifies non-virtualized Ethernet interface. |
non-virtualized-fc-if | Specifies non-virtualized Fibre Channel interface. |
path-encap-consolidated | Specifies path encapsulation consolidated. |
path-encap-virtual | Specifies path encapsulation virtual. |
protected-eth-if | Specifies protected Ethernet interface. |
protected-fc-if | Specifies protected Fibre Channel interface. |
protected-fcoe | Specifies protected Fibre Channel over Ethernet. |
virtualized-eth-if | Specifies virtualized Ethernet interface. |
virtualized-fc-if | Specifies virtualized Fibre Channel interface. |
virtualized-scsi-if | Specifies virtualized SCSI interface. |
None
Adapter (/org/server-qual/adapter)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Creates an adapter capacity qualification for the specified adapter type and enters organization server qualification adapter mode.
This example shows how to create a capacity qualification:
switch-A# scope org org3 switch-A /org # scope server-qual sq2 switch-A /org/server-qual # scope adapter 1/1/1 switch-A /org/server-qual/adapter # create cap-qual cq10 switch-A /org/server-qual/adapter* # commit-buffer switch-A /org/server-qual/adapter #
Command |
Description |
show adapter |
|
show server-qual |
|
To create a keyring certificate request, use the create certreq command.
create certreq { subject-name name | ip ip-address } + [ password password ]
subject-name | Specifies subject name. |
name | Subject name. The range of valid values is 1 to 16. |
ip | Specifies IP address. |
ip-address | IP address. The format is A.B.C.D. |
password | (Optional) Specifies password. |
password | Password. The range of valid values is 1 to 16. |
None
Keyring (/security/keyring)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Before you create a certreq you must set modulus.
This example shows how to create a keyring certificate request:
switch-A# scope security switch-A /security # scope keyring k1 switch-A /security/keyring # create certreq subject-name cr3 switch-A /security/keyring* # commit-buffer switch-A /security/keyring #
Command |
Description |
show certreq |
|
show keyring |
|
To create a chassis, use the create chassis command.
create chassis min-id max-id
min-id | Minimum chassis identification number. The range of valid values is 1 to 255. |
max-id | Maximum chassis identification number. The range of valid values is 1 to 255. |
None
Server qualification (/org/server-qual)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Creates a chassis with the specified name, and enters organization chassis mode.
This example shows how to create a chassis:
switch-A# scope org org3 switch-A /org # scope server-qual sq2 switch-A /org/server-qual # create chassis 2 2 switch-A /org/server-qual/chassis* # commit-buffer switch-A /org/server-qual/chassis #
Command |
Description |
show chassis |
|
show server |
|
To create a chassis statistics class, use the create class chassis-stats command.
create class chassis-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/eth-server/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to place thresholds on statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for chassis statistics.
This example shows how to create a chassis statistics class:
switch-A# scope eth-server switch-A /eth-server # scope stats-threshold-policy tp10 switch-A /eth-server/stats-threshold-policy # create class chassis-stats switch-A /eth-server/stats-threshold-policy* # commit-buffer switch-A /eth-server/stats-threshold-policy #
Command |
Description |
show chassis |
|
show class |
|
To create a CMC statistics class, use the create class cmc-stats command.
create class cmc-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/eth-server/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to place thresholds on statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for CMC statistics.
This example shows how to create a chassis statistics class:
switch-A# scope eth-server switch-A /eth-server # scope stats-threshold-policy tp10 switch-A /eth-server/stats-threshold-policy # create class cmc-stats switch-A /eth-server/stats-threshold-policy* # commit-buffer switch-A /eth-server/stats-threshold-policy #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create the CPU environment statistics class, use the create class cpu-env-stats command.
create class cpu-env-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
When you create the class, you enter organization statistics threshold policy CPU environment class mode. You can then create properties for this class with the create property command in the mode.
This example shows how to create a CPU environment statistics class:
switch-A# scope org org100 switch-A /org # scope stats-threshold-policy stp100 switch-A /org/stats-threshold-policy # create class cpu-env-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create a DIMM statistics class, use the create class dimm-stats command.
create class dimm-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for DIMMs.
This example shows how to create a DIMM statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p1 switch-A /org/stats-threshold-policy # create class dimm-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create an Ethernet error statistics class, use the create class ether-error-stats command.
create class ether-error-stats
This command has no arguments or keywords.
None
Statistics threshold policy under Ethernet uplink (/eth-uplink/stats-threshold-policy)
Statistics threshold policy under Ethernet server (/eth-server/stats-threshold-policy)
Release | Modification |
---|---|
1.0 | This command was introduced. |
Use classes to place thresholds on statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Ethernet error statistics.
This example shows how to create an Ethernet error statistics class:
switch-A# scope eth-uplink switch-A /eth-uplink # scope stats-threshold-policy p10 switch-A /eth-uplink/stats-threshold-policy # create class ether-error-stats switch-A /eth-uplink/stats-threshold-policy* # commit-buffer switch-A /eth-uplink/stats-threshold-policy #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create an Ethernet interface statistics class, use the create class ether-if-stats command.
create class ether-if-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to place a threshold on statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Ethernet interface statistics.
This example shows how to create an Ethernet interface statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p1 switch-A /org/stats-threshold-policy # create class ether-if-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create an Ethernet loss statistics class, use the create class ether-loss-stats command.
create class ether-loss-stats
This command has no arguments or keywords.
None
Statistics threshold policy under Ethernet server (/eth-server/stats-threshold-policy)
Statistics threshold policy under Ethernet uplink (/eth-uplink/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to place a threshold on statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Ethernet loss statistics.
This example shows how to create an Ethernet loss statistics class:
switch-A# scope eth-server switch-A /eth-server # scope stats-threshold-policy p10 switch-A /eth-server/stats-threshold-policy # create class ether-loss-stats switch-A /eth-server/stats-threshold-policy/class* # commit-buffer switch-A /eth-server/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create an Ethernet port error statistics class, use the create class ethernet-port-err-stats command.
create class ethernet-port-err-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to place a threshold on statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Ethernet port error statistics.
This example shows how to create an Ethernet port error statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class ethernet-port-err-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create an Ethernet port multicast statistics class, use the create class ethernet-port-multicast-stats command.
create class ethernet-port-multicast-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to place a threshold on statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Ethernet port multicast statistics.
This example shows how to create an Ethernet port multicast statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class ethernet-port-multicast-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create an Ethernet port over-under-sized statistics class, use the create class ethernet-port-over-under-sized-stats command.
create class ethernet-port-over-under-sized-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to place a threshold on statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Ethernet port over-under-sized statistics.
This example shows how to create an Ethernet port statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class ethernet-port-over-under-sized-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create an Ethernet port statistics class, use the create class ethernet-port-stats command.
create class ethernet-port-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to place a threshold on statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Ethernet port statistics.
This example shows how to create an Ethernet port statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class ethernet-port-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create an Ethernet port large packet statistics class, use the create class ethernet-port-stats-by-size-large-packets command.
create class ethernet-port-stats-by-size-large-packets
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to place thresholds on statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Ethernet port small packet statistics.
This example shows how to create an Ethernet port large packet statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class ethernet-port-stats-by-size-large-packets switch-A /org/stats-threshold-policy/class* # commit-buffer swicth-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create an Ethernet port small packet statistics class, use the create class ethernet-port-stats-by-size-small-packets command.
create class ethernet-port-stats-by-size-small-packets
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to place thresholds on statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Ethernet port small packet statistics.
This example shows how to create an Ethernet port small packet statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class ethernet-port-stats-by-size-small-packets switch-A /org/stats-threshold-policy/class* # commit-buffer swicth-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create an Ethernet recieve statistics class, use the create class ether-rx-stats command.
create class ether-rx-stats
This command has no arguments or keywords.
None
Statistics threshold policy under Ethernet server (/eth-server/stats-threshold-policy)
Statistics threshold policy under Ethernet uplink (/eth-uplink/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to place a threshold on statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Ethernet recieve statistics.
This example shows how to create an Ethernet recieve statistics class:
switch-A# scope eth-server switch-A /eth-server # scope stats-threshold-policy p10 switch-A /eth-server/stats-threshold-policy # create class eth-rx-stats switch-A /eth-server/stats-threshold-policy/class* # commit-buffer switch-A /eth-server/stats-threshold-policy/class #
Command |
Description |
show eth-uplink |
|
show stats-threshold-policy |
|
To create an Ethernet transmission statistics class, use the create class ether-tx-stats command.
create class ether-tx-stats
This command has no arguments or keywords.
None
Statistics threshold policy under Ethernet uplink (/eth-uplink/stats-threshold-policy)
Statistics threshold policy under Ethernet server (/eth-server/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to place a threshold on statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Ethernet transmission statistics.
This example shows how to create an Ethernet transmission statistics class:
switch-A# scope eth-server switch-A /eth-server # scope stats-threshold-policy p10 switch-A /eth-server/stats-threshold-policy # create class eth-tx-stats switch-A /eth-server/stats-threshold-policy/class* # commit-buffer switch-A /eth-server/stats-threshold-policy/class #
Command |
Description |
show eth-uplink |
|
show stats-threshold-policy |
|
To create a fan module statistics class, use the create class fan-module-stats command.
create class fan-module-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/eth-server/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for fan module statistics.
This example shows how to create a fan module statistics class:
switch-A# scope eth-server switch-A /eth-server # scope stats-threshold-policy p10 switch-A /eth-server/stats-threshold-policy # create class fan-module-stats switch-A /eth-server/stats-threshold-policy* # commit-buffer switch-A /eth-server/stats-threshold-policy #
Command |
Description |
show fan-module |
|
show stats-threshold-policy |
|
To create a fan statistics class, use the create class fan-stats command.
create class fan-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/eth-server/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to place thresholds on statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for fan statistics.
This example shows how to create a fan statistics class:
switch-A# scope eth-server switch-A /eth-server # scope stats-threshold-policy p10 switch-A /eth-server/stats-threshold-policy # create class fan-stats switch-A /eth-server/stats-threshold-policy* # commit-buffer switch-A /eth-server/stats-threshold-policy #
Command |
Description |
show fan-module |
|
show stats-threshold-policy |
|
To create a Fibre Channel error statistics class, use the create class fc-error-stats command.
create class fc-error-stats
This command has no arguments or keywords.
None
Statistics threshold policy /fc-uplink/stats-threshold-policy
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Fibre Channel error statistics.
This example shows how to create a Fibre Channel error statistics class:
switch-A# scope fc-uplink switch-A /org # scope stats-threshold-policy p10 Pubs-A /org/stats-threshold-policy # create class fc-error-stats Pubs-A /org/stats-threshold-policy/class* # commit-buffer Pubs-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create Fibre Channel event statistics, use the create class fc-if-event-stats command.
create class fc-if-event-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Fibre Channel event statistics.
The following example
switch-A # scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class fc-if-event-stats switch-A /org/stats-threshold-policy* # commit-buffer switch-A /org/stats-threshold-policy #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create Fibre Channel counters, use the create class fc-if-fc4-counters command.
create class fc-if-fc4-counters
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Fibre Channel counter statistics.
This example shows how to create Fibre Channel counters:
switch-A # scope org org3 switch-A /org # switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class fc-if-fc4-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create a Fibre Channel frame statistics class, use the create class fc-if-frame-stats command.
create class fc-if-frame-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Fibre Channel frame statistics.
This example shows how to create a Fibre Channel frame statistics class:
switch-A # scope org org3 switch-A /org # switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class fc-if-frame-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create Fibre Channel port statistics class, use the create class fc-port-stats command.
create class fc-port-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Fibre Channel port statistics.
This example shows how to create a Fibre Channel port statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class fc-port-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create a Fibre Channel statistics class, use the create class fc-stats command.
create class fc-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/fc-uplink/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Fibre Channel statistics.
This example shows how to create a Fibre Channel statistics class:
switch-A# scope fc-uplink switch-A /fc-uplink # scope stats-threshold-policy p10 switch-A /fc-uplink/stats-threshold-policy # create class fc-stats switch-A /fc-uplink/stats-threshold-policy/class* # commit-buffer switch-A /fc-uplink/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create a mother board power statistics class, use the create class mb-power-stats command.
create class mb-power-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for mother board power statistics.
This example shows how to create a mother board power statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class mb-power-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create a temporary mother board statistics class, use the create class mb-temp-stats command.
create class mb-temp-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Mb statistics.
This example shows how to create a temporary mother board statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class mb-temp-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show class mb-temp-stats |
|
To create a memory runtime class, use the create class memory-runtime command.
create class memory-runtime
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to create a memory runtime class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class memory-runtime switch-A /org/stats-threshold-policy* # commit-buffer switch-A /org/stats-threshold-policy #
Command |
Description |
show class |
|
show memory |
|
To create a Menlo port statistics class, use the create class menlo-dce-port-stats command.
create class menlo-dce-port-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Menlo Ethernet port statistics.
This example shows how to create a Menlo port statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class menlo-dce-port-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create a Menlo Ethernet error statistics class, use the create class menlo-eth-error-stats command.
create class menlo-eth-error-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Menlo Ethernet error statistics.
This example shows how to create a Menlo Ethernet error statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class menlo-eth-error-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create a Menlo Ethernet statistics class, use the create class menlo-eth-stats command.
create class menlo-eth-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Menlo Ethernet statistics.
This example shows how to create a Menlo Ethernet statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class menlo-eth-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create Menlo Fibre Channel error statistics, use the create class menlo-fc-error-stats command.
create class menlo-fc-error-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Menlo Fibre Channel error statistics.
This example shows how to create Menlo Fibre Channel error statistics:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class menlo-fc-error-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create Menlo Fibre Channel statistics, use the create class menlo-fc-stats command.
create class menlo-fc-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Menlo Fibre Channel statistics.
This example shows how to create Menlo Fibre Channel statistics:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class menlo-fc-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create Menlo host port statistics, use the create class menlo-host-port-stats command.
create class menlo-host-port-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Menlo host port statistics.
This example shows how to create Menlo host port statistics:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class menlo-host-port-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create a Menlo CPU error statistics class, use the create class menlo-mcpu-error-stats command.
create class menlo-mcpu-error-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Menlo CPU error statistics.
This example shows how to create a Menlo CPU error statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class menlo-mcpu-error-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create a Menlo CPU statistics class, use the create class menlo-mcpu-stats command.
create class menlo-mcpu-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Menlo CPU statistics.
This example shows how to create a Menlo CPU statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class menlo-mcpu-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create a Menlo network egress statistics class, use the create class menlo-net-eg-stats command.
create class menlo-net-eg-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Menlo network egress traffic statistics.
This example shows how to create a Menlo network egress statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class menlo-net-eg-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create a Menlo network ingress statistics class, use the create class menlo-net-in-stats command.
create class menlo-net-in-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Menlo network ingress traffic statistics.
This example shows how to create a Menlo network ingress statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class menlo-net-in-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create a Menlo Qlogic error statistics class, use the create class menlo-q-error-stats command.
create class menlo-q-error-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Menlo Qlogic error statistics.
This example shows how to create a Menlo Qlogic error statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class menlo-q-error-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create a Menlo Qlogic statistics class, use the create class menlo-q-stats command.
create class menlo-q-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Menlo Qlogic statistics.
This example shows how to create a Menlo Qlogic statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class menlo-q-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create a processor runtime statistics class, use the create class processor-runtime command.
create class processor-runtime
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to create a processor runtime statistics class:
switch-A# scope org org10 switch-A /org # scope stats-threshold-policy p10 switch-A /org/stats-threshold-policy # create class processor-runtime switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-statistics |
|
To create a power supply input statistics class, use the create class psu-input-stats command.
create class psu-input-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/eth-server/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for power supply input statistics.
This example shows how to create a power supply input statistics class:
switch-A# scope eth-server switch-A /eth-server # scope stats-threshold-policy p10 switch-A /eth-server/stats-threshold-policy # create class psu-input-stats switch-A /eth-server/stats-threshold-policy/class* # commit-buffer switch-A /eth-server/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create a power supply statistics class, use the create class psu-stats command.
create class psu-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/eth-server/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for power supply statistics.
This example shows how to create power supply statistics class:
switch-A# scope eth-server switch-A /eth-server # scope stats-threshold-policy p10 switch-A /eth-server/stats-threshold-policy # create class psu-stats switch-A /eth-server/stats-threshold-policy/class* # commit-buffer switch-A /eth-server/stats-threshold-policy/class #
Command |
Description |
show class |
|
show stats-threshold-policy |
|
To create a system statistics class, use the create class system-stats command.
create class system-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/eth-server/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for system statistics.
This example shows how to create a system statistics class:
switch-A# scope eth-server switch-A /eth-server # scope stats-threshold-policy p10 switch-A /eth-server/stats-threshold-policy # create class system-stats switch-A /eth-server/stats-threshold-policy/class* # commit-buffer switch-A /eth-server/stats-threshold-policy/class #
Command |
Description |
show class |
|
show system |
|
To create a client, use the create client command in port-profile mode.
create client client-name
client-name | The name of the client. A unique set of numbers or letters that identifies the client. The range of valid values is 1 to 16. |
None
Profile set (/system/vm-mgmt/vmware/profile-set/port-profile)
Release | Modification |
---|---|
1.1(1) | This command was introduced. |
Creates a client for a port profile. It also enters you into system VM management VMware profile set port profile mode. This command is used along with other commands to configure port profiles.
This example shows how to create a client:
switch-A# scope system switch-A /system # scope vm-mgmt switch-A /system/vm-mgmt # scope vmware switch-A /system/vm-mgmt/vmware # scope profile-set switch-A /system/vm-mgmt/vmware/profile-set # scope port-profile pp100 switch-A /system/vm-mgmt/vmware/profile-set/port-profile # create client c100 switch-A /system/vm-mgmt/vmware/profile-set/port-profile* # commit-buffer switch-A /system/vm-mgmt/vmware/profile-set/port-profile #
Command |
Description |
show port profile |
|
show profile-set |
|
To create a Virtual NIC statistics class, use the create class vnic-stats command.
create class vnic-stats
This command has no arguments or keywords.
None
Statistics threshold policy (/org/stats-threshold-policy)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use classes to threshold statistics. For example, you might want to define a threshold on a port that raises a fault if the average number of packets dropped exceeds a certain amount. For this class, you would create thresholds for Virtual NIC statistics.
This example shows how to create a Virtual NIC statistics class:
switch-A# scope org org3 switch-A /org # scope stats-threshold-policy p1 switch-A /org/stats-threshold-policy # create class vnic-stats switch-A /org/stats-threshold-policy/class* # commit-buffer switch-A /org/stats-threshold-policy/class #
Command |
Description |
show class |
|
show vnic-templ |
|
To create a data center, use the create data-center command in vcenter mode. You can also create a data center in folder mode.
create data-center datacenter-name
datacenter-name | The name of the data center. A unique set of numbers or letters that identifies the data center. The range of valid values is 1 to 16. |
None
VCenter (/system/vm-mgmt/vmware/vcenter)
Folder (/system/vm-mgmt/vmware/vcenter/folder
Release | Modification |
---|---|
1.1(1) | This command was introduced. |
Data center
This example shows how to create a data center:
switch-A# scope system switch-A /system # scope vm-mgmt switch-A /system/vm-mgmt # scope vmware switch-A /system/vm-mgmt/vmware # scope vcenter switch-A /system/vm-mgmt/vmware/vcenter # create data-center dc10 switch-A /system/vm-mgmt/vmware/vcenter* # commit-buffer switch-A /system/vm-mgmt/vmware/vcenter #
Command |
Description |
show data-center |
|
show folder |
|
To create a default behavior mode, use the create default-behavior command.
create default-behavior { vhba | | vnic }
vhba | Specifies vHBA default behavior mode. |
vnic | Specifies vNIC default behavior mode. |
None
Service profile (/org/service-profile)
Release | Modification |
---|---|
1.1(1) | This command was introduced. |
Use this command to create a default behavior, and enter organization default-behavior mode.
hw-inherit sets
This example shows how to create a vNIC default behavior mode:
switch-A# scope org org10 switch-A /org # scope service-profile sp10 switch-A /org/service-profile # create default-behavior vnic switch-A /org/service-profile/default-behavior* # commit-buffer switch-A /org/service-profile/default-behavior #
Command |
Description |
show default-behavior |
|
show vnic |
|
To create an email destination, use the create destination command.
create destination email
Email destination. |
None
Profile (/monitoring/callhome/profile)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to create an email destination:
switch-A# scope monitoring switch-A /monitoring # scope callhome switch-A /monitoring/callhome # scope profile p3 switch-A /monitoring/callhome/profile # create destination home@test.com switch-A /monitoring/callhome/profile* # commit-buffer switch-A /monitoring/callhome/profile #
Command |
Description |
show callhome |
|
show destination |
|
To create a distributed virtual switch, use the create distributed-virtual-switch command in folder mode.
create distributed-virtual-switch dvs-name
dvs-name | The name of the switch. A unique set of numbers or letters that identifies the switch. The range of valid values is 1 to 16. |
VMware (/system/vm-mgmt/vmware/vcenter/data-center/folder)
Release | Modification |
---|---|
1.1(1) | This command was introduced. |
Distributed virtual switch
This example shows how to create a distributed virtual switch:
switch-A# scope system switch-A /system # scope vm-mgmt switch-A /system/vm-mgmt # scope vmware switch-A /system/vm-mgmt/vmware # scope vcenter vc10 switch-A /system/vm-mgmt/vmware/vcenter # scope data-center dc10 switch-A /system/vm-mgmt/vmware/vcenter/data-center # scope folder f10 switch-A /system/vm-mgmt/vmware/vcenter/data-center/folder # create distributed-virtual-switch dvs10 switch-A /system/vm-mgmt/vmware/vcenter/data-center/folder* # commit-buffer switch-A /system/vm-mgmt/vmware/vcenter/data-center/folder #
Command |
Description |
show distributed-virtual-switch |
|
show folder |
|
To create a DNS host name , use the create dns command.
create dns name
name | DNS host name. The range of valid values is 1 to 16. |
None
Services (/system/services)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to create a DNS host name:
switch-A# scope system switch-A /system # scope services switch-A /system/services # create dns dns10 switch-A /system/services* # commit-buffer switch-A /system/services #
Command |
Description |
show dns |
|
show ntp |
|
To create a dynamic vNIC connection, use the create dynamic-vnic-conn command.
create dynamic-vnic-conn
This command has no arguments or keywords.
None
Service profile (/org/service-profile)
Release | Modification |
---|---|
1.1(1) | This command was introduced. |
The vNIC connection policy determines how the VN-link connectivity between VMs and dynamic vNICs is configured. This policy is required for Cisco UCS instances that include servers with Cisco M81KR VIC adapters that host VMs and dynamic vNICs.
Each Dynamic vNIC connection policy must include an adapter policy and designate the number of vNICs that can be configured for any server associated with a service profile that includes the policy.
This example shows how to create a dynamic vNIC connection:
switch-A# scope org org10 switch-A /org # scope service-profile sp10 switch-A /org/service-profile # create dynamic-vnic-conn switch-A /org/service-profile* # commit-buffer switch-A /org/service-profile #
Command |
Description |
show dynamic-vnic-con |
|
show dynamic-vnic-con-policy |
|
To create a dynamic vNIC connection policy, use the create dynamic-vnic-conn-policy command.
create dynamic-vnic-conn-policy policy-name
policy-name | The name of the vNIC connection policy. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
The vNIC connection policy determines how the VN-link connectivity between VMs and dynamic vNICs is configured. This policy is required for Cisco UCS instances that include servers with Cisco M81KR VIC adapters that host VMs and dynamic vNICs.
Each Dynamic vNIC connection policy must include an adapter policy and designate the number of vNICs that can be configured for any server associated with a service profile that includes the policy.
This example shows how to create a dynamic VNIC connection policy:
switch-A# scope org org10 switch-A /org # create dynamic-vnic-conn-policy dvcp10 switch-A /org/dynamic-vnic-conn-policy* # commit-buffer switch-A /org/dynamic-vnic-conn-policy #
Command |
Description |
show dynamic-vnic-connection-policy |
|
show vnic-templ |
|
To create an egress policy, use the create data-center command in vcenter mode. You can also create a data center in folder mode.
create egress-policy policy-name
policy-name | The name of the policy. A unique set of numbers or letters that identifies the policy. The range of valid values is 1 to 16. |
None
Egress policy (/org/qos-policy/egress-policy)
Release | Modification |
---|---|
1.1(1) | This command was introduced. |
Data center
This example shows how to create a data center:
switch-A# scope system switch-A /system # scope vm-mgmt switch-A /system/vm-mgmt # scope vmware switch-A /system/vm-mgmt/vmware # scope vcenter switch-A /system/vm-mgmt/vmware/vcenter # create data-center dc10 switch-A /system/vm-mgmt/vmware/vcenter* # commit-buffer switch-A /system/vm-mgmt/vmware/vcenter #
Command |
Description |
show data-center |
|
show folder |
|
To create an end-point user, use the create epuser command.
create epuser name
name | End-point user name. The range of valid values is 1 to 16. |
None
IPMI access profile (/org/ipmi-access-profile)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Creates the specified endpoint user and enters organization IPMI access profile endpoint user mode.
More than one endpoint user can be created within an IPMI access profile, with each endpoint user having its own password and privileges
This example shows how to create an end-point user:
switch-A# scope org org10 switch-A /org # scope ipmi-access-profile ap10 switch-A /org/ipmi-access-profile # create epuser user10 switch-A /org/ipmi-access-profile/epuser* # commit-buffer switch-A /org/ipmi-access-profile/epuser #
Command |
Description |
show epuser |
|
show ipmi-access-profile |
|
To create an Ethernet interface, use the create eth-if command.
create eth-if name
name | Interface name. The range of valid values is 1 to 16. |
None
Virtual NIC (/org/service-profile/vnic)
Virtual NIC template (/org/vnic-templ)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to create an Ethernet interface:
switch-A# scope org org10 switch-A /org # scope service-profile sp10 switch-A /org/service-profile # scope vnic vn10 switch-A /org/service-profile/vnic # create eth-if if10 switch-A /org/service-profile/vnic/eth-if* # commit-buffer switch-A /org/service-profile/vnic/eth-if #
Command |
Description |
show eth-profile |
|
show service-profile |
|
To create an Ethernet policy, use the create eth-policy command.
create eth-policy name
policy-name | The name of the Ethernet policy. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to create Ethernet policy ep100 in org100 mode:
switch-A# scope org org100 switch-A /org # create eth-policy ep100 switch-A /org/eth-policy* # commit-buffer switch-A /org/eth-policy #
Command |
Description |
show eth-policy |
|
show trans-queue |
|
To create a FCoE (Fibre Channel over Ethernet) interface, use the create fcoe-if command.
create fcoe-if
This command has no arguments or keywords.
None
Virtual NIC (/org/service-profile/vnic)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to create an FCoE interface:
switch# scope org org3 switch /org # scope service-profile sp1 switch /org/service-profile # scope vnic switch /org/service-profile/vnic # create fcoe-if switch /org/service-profile/vnic* # commit-buffer switch /org/service-profile/vnic #
Command |
Description |
show interface |
|
show vnic |
|
To create a Fibre Channel policy, use the create fc-policy command.
create fc-policy policy-name
policy-name | The name of the Fibre Channel policy. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a Fibre Channel policy, and enter organization fc-policy mode.
This example shows how to create Fibre Channel policy fcp10 in org10 mode:
switch# scope org org10 switch /org # create fc-policy fcp10 switch /org/fc-policy* # commit-buffer switch /org/fc-policy #
Command |
Description |
show fc-policy |
|
show trans-queue |
|
To create a folder, use the create folder command in vcenter mode. You can also create a folder in data-center mode.
create folder folder-name
folder-name | The name of the folder. A unique set of numbers or letters that identifies the folder. The range of valid values is 1 to 16. |
None
VCenter (/system/vm-mgmt/vmware/vcenter)
Folder (/system/vm-mgmt/vmware/vcenter/data-center
Release | Modification |
---|---|
1.1(1) | This command was introduced. |
Folder
This example shows how to create a folder:
switch-A# scope system switch-A /system # scope vm-mgmt switch-A /system/vm-mgmt # scope vmware switch-A /system/vm-mgmt/vmware # scope vcenter switch-A /system/vm-mgmt/vmware/vcenter # create folder folder10 switch-A /system/vm-mgmt/vmware/vcenter* # commit-buffer switch-A /system/vm-mgmt/vmware/vcenter #
Command |
Description |
show folder |
|
show vcenter |
|
To create a host pack, use the create fw-host-pack command.
create fw-host-pack name
name | Pack name. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
A pack is a collection of host firwmare images for devices like adapters, HBAs, NICs, and raid controllers.
Use this command to create a host firmware package and enter organization firmware host package mode.
This example shows how to create a host pack:
switch-A# scope org org3 Pubs-A /org # create fw-host-pack hp4 Pubs-A /org/fw-host-pack* # commit-buffer Pubs-A /org/fw-host-pack #
Command |
Description |
show fw- host-pack |
|
show fw-mgmt-pack |
|
To create a management pack, use the create fw-mgmt-pack command.
create fw-mgmt-pack name
name | Pack name. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
A pack is a collection of host firwmare images for devices like adapters, HBAs, NICs, and raid controllers.
Use this command to create a management firmware package and enter organization firmware management package mode.
This example shows how to create a management pack:
switch# scope org org3 switch /org # create fw-mgmt-pack mp4 switch /org/fw-host-pack* # commit-buffer switch /org/fw-host-pack #
Command |
Description |
show fw- host-pack |
|
show fw-mgmt-pack |
|
To create an HV connection, use the create hv-conn command.
create hv-conn protection { none | protected } *
protection | Specifies that the connection is protected. |
none | Specifies no protection. |
protected | Specifies protection. |
None
Service profile (/org/service-profile)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a Hypervisor connection, and enter organization HV connection mode.
This example shows how to create a HV connection:
switch# scope org org3 switch /org # scope service-profile sp1 switch /org/service-profile # create hv-conn switch /org/service-profile/hv-conn* # commit-buffer switch /org/service-profile/hv-conn #
Command |
Description |
show connectivity |
|
show hv-conn |
|
To create a import configuration, use the create import-config command.
create import-config { ftp: | scp: | sftp: | tftp: } { disabled | enabled } { merge | replace }
ftp: | Specifies File Transfer Protocol. |
scp: | Specifies Secure Copy Protocol. |
sftp: | Specifies Secure File Transfer Protocol. |
tftp: | Specifies Trivial File Transfer Protocol. |
disabled | Specifies disabled. |
enabled | Specifies enabled. |
merge | Specifies merge. |
replace | Specifies replace. |
None
System (/system)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a configuration for importing files, and enter organization import configuration mode.
This example shows how to create an import configuration:
switch# scope system switch /system # create import-config ftp: enabled replace switch /service/import-config* # commit-buffer switch /service/import-config #
Command |
Description |
show image |
|
show import-config |
|
To create an initiator, use the create initiator command.
create initiator id
id | Initiator identification number. The range of valid values is 1 to 16. |
None
WWN pool (/org/wwn-pool)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a WWN initiator, and enter organization initiator mode.
This example shows how to create an initiator:
switch-A# scope org org3 switch-A /org # scope wwn-pool wwnpool3 switch-A /org/wwn-pool # create initiator switch-A /org/wwn-pool/initiator* # commit-buffer switch-A /org/wwn-pool/initiator #
Command |
Description |
show block |
|
show initiator |
|
To create an interface, use the create interface command.
create interface slot-id port-id
slot-id | Slot identification number. The range of valid values is 2 to 5. |
port-id | Port identification number. The range of valid values is 1 to 40. |
None
Fabric interconnect under Fibre Channel uplink (/fc-uplink/fabric)
Fabric interconnect under Ethernet server (/eth-server/fabric)
Fabric interconnect under Ethernet uplink (/eth-uplink/fabric)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create an Ethernet or Fibre Channel interface, and enter organization interface mode.
This example shows how to create an interface:
switch# scope fc-uplink switch /fc-uplink # scope switch b switch /fc-uplink/switch # create interface 5 10 switch /fc-uplink/switch/interface* # commit-buffer switch /fc-uplink/switch/interface #
Command |
Description |
show interface |
|
show switch |
|
To create an IPMI (Intelligent Platform Management Interface) access profile, use the create ipmi-access-profile command.
create ipmi-access-profile name
name | IPMI access profile name. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create an IPMI access profile, and enter organization IPMI access profile mode.
This example shows how to create an IPMI access profile:
switch# scope org org3 switch /org # create ipmi-access-profile ipmiProf1 switch /org/ipmi-access-profile* # commit-buffer switch /org/ipmi-access-profile #
Command |
Description |
show epuser |
|
show ipmi-access-profile |
|
To create a keyring, use the create keyring command.
create keyring name
name | Keyring name. The range of valid values is 1 to |
None
Security (/security)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to implement RSA public-key cryptography, and enter organization keyring mode.
This example shows how to create a keyring:
switch# scope security switch /security # create keyring kr220 switch /security/keyring* # commit-buffer switch /security/keyring #
Command |
Description |
show keyring |
|
show radius |
|
To create a LAN, use the create lan command.
create lan
This command has no arguments or keywords.
None
Boot policy under organization (/org/boot-policy)
Boot definition under service-profile (/org/service-profile/boot-def)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a LAN, and enter organization lan mode.
This example shows how to create a LAN:
switch-A# scope org org3 switch-A /org # scope boot-policy bp6 switch-A /org/boot-policy # create lan switch-A /org/boot-policy/lan* # commit-buffer switch-A /org/boot-policy/lan #
Command |
Description |
show boot-policy |
|
show lan |
|
To create local storage, use the create local command.
create local
None
Storage (/org/boot-policy/storage)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to create local storage:
switch# scope org org10 switch /org # scope boot-policy bp10 switch /org/boot-policy # scope storage switch /org/boot-policy/storage # create local storage10 switch /org/boot-policy/storage* # commit-buffer switch /org/boot-policy/storage #
Command |
Description |
show local |
|
show storage |
|
To create a local disk configuration, use the create local-disk-config command.
create local-disk-config
This command has no arguments or keywords.
None
Service profile (/org/service-profile)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a local disk configuration, and enter organization local disk configuration mode.
This example shows how to create a local disk configuration:
switch# scope org org3 switch /org # scope service-profile sp1 switch /org/service-profile # create local-disk-config switch /org/service-profile/local-disk-config* # commit-buffer switch /org/service-profile/local-disk-config #
Command |
Description |
show local-disk-config |
|
show local-disk-config-policy |
|
To create a local disk configuration policy, use the create local-disk-config-policy command.
create local-disk-config-policy name
name | Local disk configuration policy name. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a local disk configuration policy, and enter organization local disk configuration policy mode.
This example shows how to create a local disk configuration policy:
switch# scope org org3 switch /org # create local-disk-config-policy ldcp1 switch /org/local-disk-config-policy* # commit-buffer Pubs-A /org/local-disk-config-policy #
Command |
Description |
show local-disk-config |
|
show local-disk-config-policy |
|
To create a locale, use the create locale command.
create locale name
name | Locale name. The range of valid values is 1 to 16. |
None
Local user (/security/local-user)
Security (/security)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a locale, and enter organization local user mode.
This example shows how to create a locale:
switch# scope security switch /security # scope local-user lu1 switch /security # create locale locale1 switch /security/local-user* # commit-buffer switch /security/local-user #
Command |
Description |
show locale |
|
show local-user |
|
To create a local user, use the create local-user command.
create local-user name
name | Local user name. The range of valid values is 1 to 74. |
None
Security (/security)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a local user, and enter organization local user mode.
This example shows how to create a local user:
switch# scope security switch /security # scope local-user lu1 switch /security # create local-user lu2 switch /security/local-user* # commit-buffer switch /security/local-user #
Command |
Description |
show locale |
|
show local-user |
|
To create a MAC pool, use the create mac-pool command.
create mac-pool name
name | MAC pool name. The range of valid values is 1 to 70. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a block of MAC addresses, and enter organization MAC pool mode.
This example shows how to create a MAC pool:
switch# scope org org3 switch /org # create mac-pool mp1 switch /org/mac-pool* # commit-buffer switch /org/mac-pool #
Command |
Description |
show block |
|
show pooled |
|
To create MAC security, use the create mac-security command.
create mac-security
This command has no arguments or keywords.
None
Port profile (/eth-uplink/port-profile)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create MAC security, and enter organization MAC security mode.
This example shows how to create MAC security:
switch# scope eth-uplink switch /eth-uplink # scope port-profile pp1 switch /eth-uplink/port-profile # create mac-security switch /eth-uplink/port-profile/mac-security* # commit-buffer switch /eth-uplink/port-profile/mac-security #
Command |
Description |
show mac-security |
|
show port-profile |
|
To create a member port, use the create member-port command.
create member-port { a | b } slot-id port-id
a | Specifies port A. |
b | Specifies port B. |
slot-id | Slot identification number. The range of valid values is 1 to 5. |
port-id | Port identification number. The range of valid values is 1 to 40. |
None
Port channel (/eth-uplink/switch/port-channel)
VSAN under Fibre Channel uplink (/fc-uplink/vsan)
VSAN under fabric interconnect (/fc-uplink/fabric/vsan)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a member port, and enter organization member port mode.
This example shows how to create a member port:
switch# scope eth-uplink switch /eth-uplink # scope switch b switch /eth-uplink/switch # scope port-channel 3 switch /eth-uplink/switch/port-channel # create member-port 2 4 switch /eth-uplink/switch/port-channel/member-port* # commit-buffer switch /eth-uplink/switch/port-channel/member-port #
Command |
Description |
show member-port |
|
show port-channel |
|
To create a memory qualifier, use the create memory command.
create memory
This command has no arguments or keywords.
None
Server qualification (/org/server-qual)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a memory qualifier, and enter organization memory mode.
This example shows how to create a memory qualifier:
Pubs-A# scope org org3 Pubs-A /org # scope server-qual sq20 Pubs-A /org/server-qual # create memory Pubs-A /org/server-qual/memory* # commit-buffer Pubs-A /org/server-qual/memory #
Command |
Description |
show memory |
|
show processor |
|
To create a Ethernet interface, use the create network command.
create network name
name | Ethernet interface name. The range of valid values is 1 to 16. |
None
Port profile (/eth-uplink/port-profile)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a network, and enter organization network mode.
This example shows how to create an Ethernet interface:
switch# scope eth-uplink switch /eth-uplink # scope port-profile pp1 switch /eth-uplink/port-profile # create network eth1 switch /eth-uplink/port-profile/network* # commit-buffer switch /eth-uplink/port-profile/network #
Command |
Description |
show fc-uplink |
|
show network |
|
To create a network, use the create network command in port-profile mode.
create network network-name
network-name | The name of the network. A unique set of numbers or letters that identifies the network. The range of valid values is 1 to 32. |
None
Profile set (/system/vm-mgmt/vmware/profile-set/port-profile)
Release | Modification |
---|---|
1.1(1) | This command was introduced. |
Network
This example shows how to create a network:
switch-A# scope system switch-A /system # scope vm-mgmt switch-A /system/vm-mgmt # scope vmware switch-A /system/vm-mgmt/vmware # scope profile-set switch-A /system/vm-mgmt/vmware/profile-set # scope port-profile switch-A /system/vm-mgmt/vmware/profile-set/port-profile # create network n100 switch-A /system/vm-mgmt/vmware/profile-set/port-profile* # commit-buffer switch-A /system/vm-mgmt/vmware/profile-set/port-profile #
Command |
Description |
show port profile |
|
show profile-set |
|
To create an NTP server, use the create ntp-server command.
create ntp-server name
name | Server name. |
None
Services (/system/services)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create an NTP server, and enter organization NTP server mode.
This example shows how to create an NTP server:
switch-A# scope system switch-A /system # scope services switch-A /system/services # create ntp-server ntps1 switch-A /system/services/ntp-server* # commit-buffer switch-A /system/services/ntp-server #
Command |
Description |
show dns |
|
show ntp |
|
To create a network control policy, use the create nwctrl-policy command.
create nwctrl-policy policy-name
policy-name | Policy name. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(2) | This command was introduced. |
When you create a network control policy, you can use the policy to perform the following tasks:
This example shows how to create a network control policy:
switch-A# scope org org10 switch-A /org # create nwctrl-policy netCtrlP10 switch-A /org/nwctrl-policy* # commit-buffer switch-A /org/nwctrl-policy #
Command |
Description |
show nwctrl-policy |
|
show service-policy |
|
To create an org, use the create org command.
create org name
name | Org name. The range of valid values is 1 to 80. |
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Organizations are logical entities that you can use to divide up large physical infrastructures into smaller infrastructures.
Use this command to create an organization, and enter organization mode.
This example shows how to create an org:
Pubs-A# scope org org3 Pubs-A /org # create org org4 Pubs-A /org* # commit-buffer Pubs-A /org #
Command |
Description |
show mac-pool |
|
show org |
|
To create a organization reference, use the create org-ref command.
create org-ref name orgdn domain-name
name | Organization name. The range of valid values is 1 to 16. |
orgdn | Specifies the organization domain name. |
domain-name | Domain name. |
None
Locale (/security/locale)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
The create org-ref command creates a an organization reference to a locale. Use this command to create a organization reference, and enter organization organization reference mode.
You can specify more than one org-ref-name and orgdn-name argument on the same command line to reference multiple organizations to the locale, or you can add organizations to the same locale using multiple create org-ref commands.
This example shows how to create an organization reference to a locale:
switch# scope security switch /security # scope locale locale1 switch /security/locale # create org-ref or3 orgdn or30 switch /security/locale/org-ref* # commit-buffer switch /security/locale/org-ref #
Command |
Description |
show locale |
|
show org |
|
To create an image pack, use the create pack-image command.
create pack-image hw-vendor hw-model { server-bios | adapter | raid-controller | host-nic | host-hba | host-hba-optionrom } version
hw-vendor | Hardware vendor. |
hw-model | Hardware model number. |
server-bios | Specifies the image for the server. |
adapter | Specifies the image for the adapter. |
raid-controller | Specifies the image for the RAID array. |
host-nic | Specifies the image for the host NIC. |
host-hba | Specifies the image for the host HBA. |
host-hba-optionrom | Specifies the image for the host HBA optional ROM. |
version | Hardware version. |
None
Firmware management package (/org/fw-mgmt-pack)
Firmware host package (/org/fw-host-pack)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
A pack is a collection of host firwmare images.
Use this command to create a pack-image, and enter organization pack image mode.
Keywords found in the create pack-image command are not supported in /org/fw-mgmt-pack mode.
This example shows how to create an image pack:
switch# scope org org3 switch /org # scope fw-mgmt-pack fmp1 switch /org/fw-mgmt-pack # create pack-image hp 1100 bmc 1.2 switch /org/fw-mgmt-pack/pack-image* # commit-buffer switch /org/fw-mgmt-pack/pack-image #
Command |
Description |
show fw-host-pack |
|
show fw-mgmt-pack |
|
To create a LAN image path, use the create path command.
create path { primary | secondary }
primary | Specifies a primary path. |
secondary | Specifies specifies a secondary path. |
None
SAN image under boot-definition/storage (/org/service-profile/boot-def/storage/san-image)
LAN under boot-policy (/org/boot-policy/lan)
LAN under boot-definition /org/service-profile/boot-def/lan
SAN image under boot-policy/storage (/org/boot-policy/storage/san-image)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
The LAN image path is the path the vNIC used when booting from an image on a LAN, such as a PXE boot. For each path you can specify the vNIC to use.
Use this command to create a LAN image path, and enter organization path mode.
This example shows how to create a LAN image path:
switch# scope org org3 switch /org # scope boot-policy boot1 switch /org/boot-policy # scope lan switch /org/boot-policy/lan # create path primary switch /org/boot-policy/lan/path* # commit-buffer switch /org/boot-policy/lan/path #
Command |
Description |
show lan |
|
show path |
|
To create a pin group, use the create pin-group command.
create pin-group name
name | Pin group name. The range of valid values is 1 to 16. |
None
Ethernet uplink (/eth-uplink)
Fibre Channel uplink (/fc-uplink)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Pinning in Cisco UCS is only relevant to uplink ports.
When you determine the optimal configuration for pin groups and pinning for an uplink port, consider the estimated bandwidth usage for the servers. If you know that some servers in the system will use a lot of bandwidth, ensure that you pin these servers to different uplink ports.
Use this command to create a pin group, and enter organization pin-group mode.
This example shows how to create a pin group:
switch# scope eth-uplink switch /eth-uplink # create pin-group pg110 switch /eth-uplink/pin-group* # commit-buffer switch /eth-uplink/pin-group #
Command |
Description |
show eth-uplink |
|
show pin-group |
|
To create a policy, use the create policy command.
callhome mode create policy event
flow-control mode create policy name
event | Select a predefined fault or system event type. See Usage Guidelines for event options. |
name | Policy name. The name can be from 1 to 16 characters. |
None
Callhome (/monitoring/callhome)
Flow control (/eth-uplink/flow-control)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
1.1(1) | This command was modified to add additional event types for Call Home. |
Use this command to create a policy, and enter either organization callhome or organization flow control mode.
In Call Home configuration, use this command to create an instance of a policy for a predefined type of fault or system event. The following list shows the available keywords for Call Home event types:
In Flow Control configuration, use this command to create a named policy.
This example shows how to create and enable a Call Home policy instance for link-down events:
switch-A# scope monitoring switch-A /monitoring # scope callhome switch-A /monitoring/callhome # create policy link-down switch-A /monitoring/callhome/policy # set admin-state enabled switch-A /monitoring/callhome/policy* # commit-buffer switch-A /monitoring/callhome/policy #
This example shows how to create a named policy for flow control:
switch-A # scope eth-uplink switch-A /eth-uplink # scope flow-control switch-A /eth-uplink/flow-control # create policy policy1 switch-A /eth-uplink/flow-control* # commit-buffer switch-A /eth-uplink/flow-control #
Command |
Description |
enter policy |
|
show policy |
|
show stats-threshold-policy |
|
To create a pooling policy, use the create pooling-policy command.
create pooling-policy name
name | Policy name. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Creates a server pooling policy, and enters organization pooling policy mode.
This example shows how to create a pooling policy:
switch# scope org org3 switch /org # create pooling-policy pp110 switch /org/pooling-policy* # commit-buffer switch /org/pooling-policy #
Command |
Description |
show policy |
|
show pooling-policy |
|
To create a port channel, use the create port-channel command.
create port-channel id
id | Port identification number. The range of valid values is 1 to 40. |
None
Fabric interconnect (/eth-uplink/fabric)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Consider using a port channel to make best use of capacity when multiple uplinks are used on a switch.
Use this command to create a port channel, and enter organization port channel mode.
This example shows how to create a port channel:
switch# scope eth-uplink switch /eth-uplink # scope switch b switch /eth-uplink/switch # create port-channel 20 switch /eth-uplink/switch/port-channel* # commit-buffer switch /eth-uplink/switch/port-channel #
Command |
Description |
show port-channel |
|
show switch |
|
To create a port profile, use the create port-profile command.
create port-profile name
name | Port profile name. The range of valid values is 1 to 16. |
None
Ethernet uplink (/eth-uplink)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a port profile, and enter organization port profile mode.
This example shows how to create a port profile:
switch# scope eth-uplink switch /eth-uplink # create port-profile pp110 switch /eth-uplink/port-profile* # commit-buffer switch /eth-uplink/port-profile #
Command |
Description |
show eth-uplink |
|
show port-profile |
|
To create a port profile, use the create port-profile command in profile-set mode.
create port-profile profile-name
profile-name | The name of the profile. A unique set of numbers or letters that identifies the profile. The range of valid values is 1 to 31. |
None
Profile set (/system/vm-mgmt/vmware/profile-set)
Release | Modification |
---|---|
1.1(1) | This command was introduced. |
The port profile client determines the DVSes to which a port profile is applied. By default, a port profile applies to all DVSes in the vCenter; however, you can use a port profile client to apply a port profile to all DVSes in a specific datacenter or datacenter folder, or to a specific DVS.
create port-profile creates the specified port profile and enters system VM management VMware profile set port profile mode.
This example shows how to create a port profile:
switch-A# scope system switch-A /system # scope vm-mgmt switch-A /system/vm-mgmt # scope vmware switch-A /system/vm-mgmt/vmware # create port-profile pp100 switch-A /system/vm-mgmt/vmware* # commit-buffer switch-A /system/vm-mgmt/vmware #
Command |
Description |
show |
|
show port profile |
|
To create a processor, use the create processor command.
create processor
This command has no arguments or keywords.
None
Server qualification (/org/server-qual)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a processor, and enter organization processor mode.
Only one processor qualifier can be created.
This example shows how to create a processor:
switch# scope org org3 switch /org # scope server-qual sq20 switch /org/server-qual # create processor switch /org/server-qual/processor* # commit-buffer switch /org/server-qual/processor #
Command |
Description |
show processor |
|
show server-qual |
|
To create a profile, use the create profile command.
create profile name
name | Profile name. The range of valid values is 1 to 16. |
None
Callhome (/monitoring/callhome)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a profile, and enter organization profile mode.
This example shows how to create a profile:
switch# scope monitoring switch /monitoring # scope callhome switch /monitoring/callhome # create profile p210 switch /monitoring/callhome/profile* # commit-buffer switch /monitoring/callhome/profile #
Command |
Description |
show callhome |
|
show profile |
|
To create a QoS policy, use the create qos-policy command in org mode.
create qos-policy policy-name
policy-name | The name of the QoS policy. A unique set of numbers or letters that identifies the policy. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to create a QoS policy:
switch-A# scope org switch-A /org # create qos-policy qp10 switch-A /org* # commit-buffer switch-A /org #
Command |
Description |
show egress-policy |
|
show qos-policy |
|
To create a role, use the create role command.
create role name
name | Role name. The range of valid values is 1 to 16. |
None
Local user (/security/local-user)
Security (/security)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a role, and enter organization role mode.
This example shows how to create a role:
switch# scope security switch /security # create role admin switch /security/role* # commit-buffer switch /security/role #
Command |
Description |
show local-user |
|
show role |
|
To create a SAN image, use the create san-image command.
create san-image { primary | secondary }
primary | Specifies primary image. |
secondary | Specifies secondary image. |
None
Storage (/org/service-profile/boot-def/storage)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Only one SAN image can be created and committed.
Use this command to create a SAN image, and enter organization SAN image mode.
This example shows how to create a SAN image:
switch#scope org org3 switch /org # scope service-profile sp1 switch /org/service-profile # scope boot-def switch /org/service-profile/boot-def # scope storage switch /org/service-profile/boot-def/storage # create san-image primary switch /org/service-profile/boot-def/storage/san-image* # commit-buffer switch /org/service-profile/boot-def/storage/san-image #
Command |
Description |
show local |
|
show san-image |
|
To create a scrub policy, use the create scrub-policy command.
create scrub-policy name
name | Scrub policy name. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a scrub policy, and enter organization scrub policy mode.
This example shows how to create a scrub policy:
switch# scope org org100 switch /org # create scrub-policy scrub100 switch /org/scrub-policy* # commit-buffer switch /org/scrub-policy #
Command |
Description |
show server-disc-policy |
|
show scrub-policy |
|
To create a server, use the create server command.
create server { server-name | | chassis-id/slot-id }
server-name | The name of the server. Valid entries for this value are a name or an IP address. The range of valid values for a name is 1 to 16. |
chassis-id/slot-id | Chassis and slot identification numbers. |
None
VMware management (/system/vm-mgmt)
LDAP (/security/ldap)
TACACS (/security/tacacs)
RADIUS (/security/radius)
Server pool (/org/server-pool)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This command takes the name argument only in the /org/server-pool mode.
Use this command to create a server, and enter organization server mode.
This example shows how to create a server:
switch#scope security switch /security # scope radius switch /security/radius # create server radius 209.165.200.226 switch /security/radius/server* # commit-buffer switch /security/radius/server #
Command |
Description |
show aaa |
|
show server |
|
To create a server automatice configuration policy, use the create server-autoconfig-policy command.
create server-autoconfig-policy name
name | Policy name. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
The server-autoconfig-policy command is definable only in org /.
Use this command to create a server automatic configuration policy with the specified policy name, and enters organization server automatic configuration policy mode.
This example shows how to create a server autoconfiguration policy:
switch#scope org org3 switch /org # create server-autoconfig-policy sap110 switch /org/server-autoconfig-policy* # commit-buffer switch /org/server-autoconfig-policy #
Command |
Description |
show server-disc-policy |
|
show server-autoconfig-policy |
|
To create a server discovery policy, use the create server-disc-policy command.
create server-disc-policy name
name | Server discovery policy name. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
The server-disc-policy command is definable only in org /.
Use this command to create a server discovery policy, and enter organization server discovery policy mode.
This example shows how to create a server discovery policy:
switch#scope org org3 switch /org # create server-disc-policy sdp110 switch /org/server-disc-policy* # commit-buffer switch /org/server-disc-policy #
Command |
Description |
show server-disc-policy |
|
show server-autoconfig-policy |
|
To create a server inherit policy, use the create server-inherit-policy command.
create server-inherit-policy name
name | Policy name. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
The server-inherit-policy command is definable only in org /.
Use this command to create a server inherit policy, and enter organization server inherit policy mode.
This example shows how to create a server inherit policy:
switch#scope org / switch /org # create server-inherit-policy sip110 switch /org/server-inherit-policy* # commit-buffer switch /org/server-inherit-policy #
Command |
Description |
show server-disc-policy |
|
show server-inherit-policy |
|
To create a server pool, use the create server-pool command.
create server-pool name
name | Server pool name. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a server pool, and enter organization server pool mode.
This example shows how to create a server pool:
switch#scope org org3 switch /org # create server-pool sPool10 switch /org/server-pool* # commit-buffer switch /org/server-pool #
Command |
Description |
show org |
|
show server-pool |
|
To create a server qualifier, use the create server-qual command.
create server-qual name
name | Server qualifier name. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a server qualifier, and enter organization server qualification mode.
This example shows how to create a server qualifier:
switch#scope org org3 switch /org # create server-qual sql10 switch /org/server-qual* # commit-buffer switch /org/server-qual #
Command |
Description |
show server-pool |
|
show server-qual |
|
To create a service profile, use the create service-profile command.
create service-profile name [ initial-template | | instance | | updating-template ]
name | The service profile name. The range of valid values is 1 to 16. |
initial-template | Specifies that instances will not automatically update if this template is updated. |
instance | Specifies the service profile instance. |
updating-template | Specifies that instances will automatically update if this template is updated. |
None.
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a service profile, and enter service profile mode.
The following example shows how to create a service profile.
switch# scope org org110 switch /org # create service-profile spEast110 switch /org/service-profile* # commit-buffer switch /org/service-profile #
Command |
Description |
show ipmi-access-profile |
|
show service-profile |
|
To create a slot, use the create slot command.
create slot min-id max-id
min-id | Minimum slot identification number. The range of valid values is 1 to 8. |
max-id | Maximum slot identification number. The range of valid values is 1 to 8. |
None
Chassis (/org/server-qual/chassis)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a slot with the specified ID, and enters organization slot mode.
This example shows how to create a slot:
switch# scope org org10 switch /org # scope server-qual sq10 switch /org/server-qual # scope chassis 1 1 switch /org/server-qual/chassis # create slot 1 1 switch /org/server-qual/chassis/slot* # commit-buffer switch /org/server-qual/chassis/slot #
Command |
Description |
show chassis |
|
show slot |
|
To create an SNMP trap, use the create snmp-trap command.
create snmp-trap ip-address
ip-address | Host IP address. Specify the IP address in the format A.B.C.D. |
None
Monitoring (/monitoring)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You must create an SNMP community before you create an SNMP trap.
This example shows how to create an SNMP trap:
switch#scope monitoring switch /monitoring # create snmp-trap 192.0.2.34 switch /monitoring/snmp-trap* # commit-buffer switch /monitoring/snmp-trap #
Command |
Description |
show snmp |
|
show snmp-trap |
|
To create an SNMPv3 user, use the create snmp-user command.
create snmp-useruser-name
user-name | User name. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(2) | This command was introduced. |
This example shows how to create an SNMPv3 user:
switch-A# scope monitoring switch-A /monitoring # create snmp-user snmpUser10 switch-A /monitoring* # commit-buffer switch-A /monitoring #
Command |
Description |
show snmp |
|
show snmp-user |
|
To create a Serial over LAN (SoL) configuration, use the create sol-config command.
create sol-config
This command has no arguments or keywords.
None
Service profile (/org/service-profile)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a SoL configuration, and enter organization SoL configuration mode.
This example shows how to create a SoL configuration:
switch-A# scope org org30 switch-A /org # scope service-profile sp30a switch-A /org/service-profile # create sol-config switch-A /org/service-profile/sol-config* # commit-buffer switch-A /org/service-profile/sol-config #
Command |
Description |
show sol-config |
|
show sol-policy |
|
To create an SoL policy, use the create sol-policy command.
create sol-policy name
name | SoL policy name. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a SoL policy with the specified name, and enters organization SoL policy mode.
This example shows how to create a SoL policy:
switch-A# scope org org3 switch-A /org # create sol-policy solpol1 switch-A /org/sol-policy* # commit-buffer switch-A /org/sol-policy #
Command |
Description |
show org |
|
show sol-policy |
|
To create a statistics threshold policy, use the create stats-threshold-policy command.
create stats-threshold-policy name
name | Policy name. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a statistics threshold policy, and enter organization statistics threshold policy mode.
This example shows how to create a statistics threshold policy:
switch# scope org org10 switch /org # create stats-threshold-policy stp10 switch /org/stats-threshold-policy* # commit-buffer switch /org/stats-threshold-policy #
Command |
Description |
show pooling-policy |
|
show stats-threshold-policy |
|
To create storage, use the create storage command.
create storage
This command has no arguments or keywords.
None
Boot definition (/org/service-profile/boot-def)
Boot policy (/org/boot-policy)
Server qualification (/org/server-qual)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to create a storage qualification, and enter organization server qualification storage mode.
This example shows how to create storage:
switch-A# scope org org3 switch-A /org # scope service-profile sp1 switch-A /org/service-profile # scope boot-def bd1 switch-A /org/service-profile/boot-def # create storage switch-A /org/service-profile/boot-def/storage* # commit-buffer switch /org/service-profile/boot-def/storage #
Command |
Description |
show boot-definition |
|
show storage |
|
To create a threshold value for a property, use the create threshold-value command.
create threshold-value { above-normal | | below-normal } { cleared | | condition | | critical | | info | | major | | minor | | warning }
above-normal | Sets the value to above normal. |
below-normal | Sets the value to below normal. |
cleared | Sets the threshold value to cleared. |
condition | Sets the threshold value to condition. |
critical | Sets the threshold value to critical. |
info | Sets the threshold value to info. |
major | Sets the threshold value to major. |
minor | Sets the threshold value to minor. |
warning | Sets the threshold value to warning. |
None
Ethernet uplink (/eth-uplink/stats-threshold-policy/class/property)
Fibre channel (/fc-uplink/stats-threshold-policy/class/property)
Ethernet server (/eth-server/stats-threshold-policy/class/property)
Organization (/org/stats-threshold-policy/class/property)
Release | Modification |
---|---|
1.0.1 |
This command was introduced. |
This command creates the specified threshold value for the class property and enters organization statistics threshold policy class property threshold value mode. You must have a class and a property created in order to execute the set threshold-value command. The command is used to set the value of the property you created.
You can configure multiple threshold values for a class property. Before you use this command, use the set normal-value command to set a baseline.
The following example shows how to set the threshold value for the bytes-rx-delta property in vnic-stats class:
switch-A#scope org org100 switch-A /org # scope stats-threshold-policy stp100 switch-A /org/stats-threshold-policy # scope class vnic-stats switch-A /org/stats-threshold-policy/class # scope property bytes-rx-delta switch-A /org/stats-threshold-policy/class/property # create threshold-value above-normal critical switch-A /org/stats-threshold-policy/class/property* # commit-buffer switch-A /org/stats-threshold-policy/class/property #
Command |
Description |
show property |
|
show threshold-value |
|
To create a trust point, use the create trustpoint command.
create trustpoint name
name | Trust point name. The range of valid values is 1 to 16. |
None
Security (/security)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to identify the trustpoints that will be used to validate a certificate during Internet Key Exchange (IKE) authentication, and enter organization trustpoint mode.
This example shows how to create a trustpoint:
switch-A# scope security switch-A /security # create trustpoint tPoint10 switch-A /security/trustpoint* # commit-buffer switch-A /security/trustpoint # create fcoe-if
Command |
Description |
show keyring |
|
show trustpoint |
|
To create a UUID suffix pool, use the create uuid-suffix-pool command.
create uuid-suffix-pool name
name | UUID suffix pool name. The range of valid values is 1 to 16. |
None
Organization (/org)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Creates a UUID suffix pool with the specified name, and enters organization UUID suffix pool mode.
This example shows how to create a UUID suffix pool:
switch-A# scope org org3 switch-A /org # create uuid-suffix-pool uuidsp1 switch-A /org/uuid-suffix-pool* # commit-buffer switch-A /org/uuid-suffix-pool #