Cisco UCS Manager CLI Command Reference, Release 1.4
Commands
Downloads: This chapterpdf (PDF - 7.8MB) The complete bookPDF (PDF - 9.57MB) | Feedback

Commands

Contents

Commands

acknowledge chassis

To acknowledge a chassis, use the acknowledge chassis command.

acknowledge chassis id

Syntax Description

id

Chassis identification number. The range of valid values is 1 to 255.

Command Default

None

Command Modes

Any command mode

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

This example shows how to acknowledge a chassis:

switch-A# acknowledge chassis 10

switch-A* # commit-buffer

switch-A #                                           

Related Commands

Command

Description

show chassis

 

show server

 

acknowledge fex

To acknowledge the fabric extender module (fex), use the acknowledge fex command.

acknowledge fex id

Syntax Description

id

The ID of the fabric extender module.

Command Default

None

Command Modes

Any command mode

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

Active links between the chassis and the Fabric interconnect must exist to use this command.

Examples

This example shows how to acknowledge the fabric extender module.

Switch-A # acknowledge fex 2
Switch-A * # commit-buffer
Switch-A # 

Related Commands

Command

Description

acknowledge fault

 

acknowledge server

 

acknowledge fault

To acknowledge a fault, use the acknowledge fault command.

acknowledge fault id

Syntax Description

id

Fault identification number. The range of valid values is 0 to 9223372036854775807.

Command Default

None

Command Modes

Any command mode

Command History

Release Modification
1.0(1)

This command was introduced.

Examples

The following example shows how to acknowledge a fault:

switch-A# acknowledge fault 1

switch-A* # commit-buffer

switch-A #                                           
                                          

Related Commands

Command

Description

show cli

 

show fault

 

acknowledge server

To acknowledge a server, use the acknowledge server command.

acknowledge server { chassis-id / blade-id | slot-id }

Syntax Description

chassis-id / blade-id

Chassis and blade identification numbers.

slot-id

Slot identification number. The range of valid values is 1 to 8.

Command Default

None

Command Modes

Any command mode

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                          

Related Commands

Command

Description

show chassis

 

show server

 

acknowledge slot

To acknowledge a slot, use the acknowledge slot command.

acknowledge slot { chassis-id / blade-id | slot-id }

Syntax Description

chassis-id / blade-id

Sever identification number.

slot-id

Slot identification number. The range of valid values is 1 to 8.

Command Default

None

Command Modes

Any command mode

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                           

Related Commands

Command

Description

show server

 

show slot

 

activate firmware

To activate firmware for a device, use the activate firmware command.

activate firmwareversion [ignorecompcheck] [set-startup-only] +

Syntax Description

version

Firmware version.

ignorecompcheck

(Optional) Ignores the results of the compatibility check.

set-startup-only

(Optional) Activates the firmware only on next startup.

Command Default

None

Command Modes

Board controller (/chassis/server/boardcontroller)

Input output module (/chassis/iom)

System (/system)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

Use the ignorecompcheck keyword to ignore the results of the automatic compatibility check when you activate the firmware.

Use the set-startup-only keyword to activate the specified Input output module (IOM) firmware version only on the next startup of the IOM. The system will not restart at this time. This keyword is available only in the IOM command mode.

Examples

The following example shows how to activate a specific version of system software, ignoring the compatibility check:

switch-A# scope system
switch-A /system # activate firmware 3.0 ignorecompcheck
switch-A /system* # commit-buffer
switch-A /system # 

Related Commands

Command

Description

show firmware

 

show version

 

activate firmware (fabric)

To activate kernal or system firmware on a fabric interconnect, use the activate firmware command.

activate firmware { kernel-version kernel-version | system-version system-version } [ignorecompcheck] [force] +

Syntax Description

kernel-version

Specifies switch kernel firmware.

kernel-version

Kernel firmware version.

system-version

Specifies switch system firmware.

system-version

System firmware version.

ignorecompcheck

(Optional) Ignores the results of the compatability check.

force

(Optional) Forces the upgrade.

Command Default

None

Command Modes

Fabric interconnect (/fabric-interconnect)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

Use the ignorecompcheck keyword to ignore the results of the automatic compatability check when you activate the firmware.

Examples

The following example shows how to activate a specific version of kernal software on fabric interconnect A, ignoring the compatibility check:

switch-A# scope fabric-interconnect a
switch-A /fabric-interconnect # activate firmware kernel-version 3.0 ignorecompcheck
switch-A /fabric-interconnect* # commit-buffer
switch-A /fabric-interconnect # 

Related Commands

Command

Description

show firmware

 

show version

 

activate internal firmware

To activate a new internal firmware version, use the activate internal firmware command.

activate internal firmware version [ignorecompcheck]

Syntax Description

version

The version number of the internal firmware version that you want to upgrade the system to. The maximum length of the version string is 512 characters.

ignorecompcheck

(Optional) Use this option to ignore the compatibility check between the versions.

Command Default

None

Command Modes

System (/system)

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

None

Examples

This example shows how to activate the internal firmware version.

Switch-A # scope system
Switch-A /system # activate internal firmware 1.4(1) ignorecompcheck
Switch-A /system # 

Related Commands

Command

Description

activate firmware

 

add alertgroups

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 ] +

Syntax Description

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.

Command Default

None

Command Modes

Profile (/monitoring/callhome/profile)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

Use this command to add more predefined Call Home alert groups to an existing alert group list within a Call Home profile.

Examples

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 #                                                                       

Related Commands

Command

Description

remove alertgroups

 

set alertgroups

 

add backup action

To add an additional action or actions that will trigger a backup of the system event log, use the add backup action command.

add backup action [log-full] [none] [on-change-of-association] [on-clear] [timer]

Syntax Description

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.

Command Default

None

Command Modes

Endpoint log policy (/org/ep-log-policy)

Command History

Release Modification
1.1(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 # 

Related Commands

Command

Description

remove backup action

 

set backup action

 

show backup

 

add privilege

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 } +

Syntax Description

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.

Command Default

None

Command Modes

Role (/security/role)

Command History

Release Modification
1.0(1)

This command was introduced.

Examples

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 # 

apply pending-changes immediate

To immediately apply pending changes to a service profile, use the apply pending-changes immediate command.

apply pending-changes immediate

Command Default

None

Command Modes

Service profile (/org/service-profile)

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

A service profile must be created to use this command.

Examples

This example shows how to immediately apply pending changes to a service profile.

Switch-A # scope org
Switch-A /org # scope service-profile example
Switch-A /org/service-profile # apply pending-changes immediate
Switch-A /org/service-profile* # commit-buffer
Switch-A /org/server-profile # 

Related Commands

Command

Description

create service-profile

 

create org

 

associate server

To associate a server, use the associate server command.

associate server { ID | chassis-id/blade-id | restrict-migration }

Syntax Description

ID

Slot identification number. The range of valid values is 1 to 255.

chassis-id/blade-id

Chassis and blade identification numbers. The range of valid values is 1 to 4294967295.

restrict-migration

(Optional). Use this option to ensure that the operating system boots appropriately when the service profile is moved to a new server.

Command Default

None

Command Modes

Service profile (/org/service-profile)

Command History

Release Modification
1.0(1)

This command was introduced with chassis-id/blade-id option.

1.4(1)

The option ID has been introduced to associate a server to the service profile using the slot ID.

The option restrict-migration has been introduced.

Examples

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 restrict-migration
 
switch-A /org/service-profile* # commit-buffer

switch-A /org/service-profile #                                          

Related Commands

Command

Description

associate server-pool

 

show assoc

 

show server

 

associate server-pool

To associate a server pool with a service profile, use the associate server-pool command.

associate server-pool server-pool [name] restrict-migration

Syntax Description

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.

restrict-migration

(Optional) Qualifier. Use this option to ensure that the operating system boots appropriately when the service profile is moved to a new server.

Command Default

None

Command Modes

Service profile (/org/service-profile)

Command History

Release Modification
1.0(1)

This command was introduced.

1.4(1)

The option restrict-migration was introduced.

Examples

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 restrict-migration
 
switch-A /org/service-profile* # commit-buffer

switch-A /org/service-profile #                                             

Related Commands

Command

Description

show assoc

 

show server

 

backup sel

To back up the system event log (SEL), use the backup sel command.

backup sel ID chassis-d / blade-id

Syntax Description

ID

Specifies the server ID. It must be a value between 1 and 255.

chassis-id / blade-id

Specifies the chassis number and server number in the format A/B.

Command Default

None

Command Modes

Any command mode

Command History

Release Modification
1.0(1)

This command was introduced.

1.4(1)

This command was modified to include the ID chassis-id / blade-id options.

Usage Guidelines

Use this command to back up the system event log (SEL) for a server.

In the command mode of a specific server (/chassis/server), you can run this command without any options.

Examples

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# 

Related Commands

Command

Description

 

cd

To change directories, use the cd command in local management command mode.

cd { workspace: | [path] | volatile: | [path] | | [path] }

Syntax Description

workspace:

Specifies the workspace (flash) directory.

volatile:

Specifies the volatile directory.

path

Absolute or relative path.

Command Default

None

Command Modes

Local management (local-mgmt)

Command History

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.

Usage Guidelines

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.

Examples

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

clear alertgroups

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.

Command Default

None

Command Modes

Profile (/monitoring/callhome/profile)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

Use this command to clear any previously configured alert group list within the Call Home profile.

Examples

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 #

Related Commands

Command

Description

set alertgroups

 

show policy

 

show profile

 

clear backup action

To clear all selected actions that will trigger a backup of the system event log, use the clear backup action command.

clear backup action

This command has no arguments or keywords.

Command Default

None

Command Modes

Endpoint log policy (/org/ep-log-policy)

Command History

Release Modification
1.1(1)

This command was introduced.

Usage Guidelines

Use this command to delete any previously configured list of actions that will trigger a backup of the system event log.

Examples

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 # 

Related Commands

Command

Description

set backup action

 

show backup

 

clear cores

To clear core files, use the clear cores command.

clear cores

This command has no arguments or keywords.

Command Default

None

Command Modes

Sysdebug (/monitoring/sysdebug)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

Core files are records of core dumps. Use the clear cores command to clear information out of core dump records.

Examples

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 #

Related Commands

Command

Description

show alert-groups

 

show cores

 

clear file

To clear a license file, use the clear file command.

clear file name

Syntax Description

name

The name of the license file.

Command Default

None

Command Modes

License (/license)

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

A license file must exist to use this command.

Examples

This example shows how to clear a license file.

Switch-A # scope license
Switch-A /license # clear file Sample
Switch-A /license* # commit-buffer
Switch-A /license #  

Related Commands

Command

Description

install file

 

clear license

To remove a license, use the clear license command in local management command mode.

clear license license-file-name [force]

Syntax Description

license-file-name

The name of a license file.

force

(Optional)

Command Default

None

Command Modes

Local management (local-mgmt)

Command History

Release Modification
1.0(1)

This command was introduced.

1.4(1)

This command was deprecated.

Usage Guidelines

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 command has been deprecated. Use the clear file command in the License mode (/license).

Examples

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

Related Commands

Command

Description

connect local-mgmt

 

show license brief

 

clear sel (/chassis/server)

To clear the contents of the system event log (SEL), use the clear sel command.

clear sel

This command has no arguments or keywords.

Command Default

None

Command Modes

Server (/chassis/server)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

Use this command to clear the contents of the system event log (SEL).

Examples

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 #

Related Commands

Command

Description

show sel

 

clear sel (/chassis/server)

To clear the contents of the system event log (SEL), use the clear sel command.

clear sel

This command has no arguments or keywords.

Command Default

None

Command Modes

Server (/chassis/server)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

Use this command to clear the contents of the system event log (SEL).

Examples

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 #

Related Commands

Command

Description

show sel

 

clear sshkey

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

Syntax Description

host-name

Host name or IP address. Specify the IP address in the format A.B.C.D.

Command Default

None

Command Modes

Local management (local-mgmt)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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

Related Commands

Command

Description

connect local-mgmt

 

cluster force primary

To force a cluster to be the primary cluster, use the cluster force primary command.

cluster force primary

Command Default

This command has no arguments or keywords.

None

Command Modes

Local management (local-mgmt)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

The cluster commands are switch-specific local management commands. You have to execute a connect local-mgmt command to connect to the management port.

Examples

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#                                    

Related Commands

Command

Description

show cluster

 

show file

 

cluster lead

To designate a cluster leader, use the cluster lead command.

cluster lead [ a | b ]

Syntax Description

a

Specifies switch A.

b

Specifies switch B.

Command Default

None

Command Modes

Local management (local-mgmt)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

The cluster commands are switch-specific local management commands. You must first execute a connect local-mgmt command to connect to the management port.

Examples

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#                                    

Related Commands

Command

Description

show cluster

 

show files

 

commit-buffer

To save or verify configuration changes, use the commit-buffer command.

commit-buffer [verify-only]

Syntax Description

verify-only

(Optional) Specifies verification only.

Command Default

None

Command Modes

Any command mode

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

This example shows how to save configuration changes:

switch-A# create org 3

switch-A /org* # commit-buffer

switch-A /org #                                          
                                          

Related Commands

Command

Description

discard-buffer

 

show configuration pending

 

connect adapter

To connect to an adapter, use the connect adapter command.

connect adapter chassis-id/server-id/adapter-id

Syntax Description

chassis-id/server-id/adapter-id

Adapter identification number.

Command Default

None

Command Modes

Any command mode

Command History

Release Modification
1.0(1)

This command was introduced.

Examples

This example shows how to connect to an adapter:

switch-A# connect adapter 1/1/1

adapter 1/1 #                                          
                                          

connect bmc

To connect to the BMC (Baseboard Management Controller), use the connect bmc command.

connect bmc chassis-id/blade-id

Syntax Description

chassis-id/blade-id

Chassis and blade identification numbers.

Command Default

None

Command Modes

Any command mode

Command History

Release Modification
1.0(1)

This command was introduced.

Examples

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:

                                      

connect clp

To connect to DMTF CLP, use the connect clp command.

connect clp

This command has no arguments or keywords.

Command Default

None

Command Modes

Any command mode

Command History

Release Modification
1.0(1)

This command was introduced.

Examples

This example shows how to connect to DMTF CLP:

switch-A# connect clp

/admin1 CLP ->

connect iom

To connect to an IO module, use the connect iom command.

connect iom id

Syntax Description

id

Chassis identification number. The valid range of values is 1 to 255.

Command Default

None

Command Modes

Any command mode

Command History

Release Modification
1.0(1)

This command was introduced.

Examples

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#                                        

connect local-mgmt

To connect to the local management port, use the connect local-mgmt command.

connect local-mgmt [ a | b ]

Syntax Description

a

Specifies switch A.

b

Specifies switch B.

Command Default

None

Command Modes

Any command mode

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

If no switch is specified, a connection will be made to the local management port of the current active switch.

Examples

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

connect nxos

To connect to the NX-OS, use the connect nxos command.

connect nxos [a | b]

Syntax Description

a

(Optional) Specifies switch A.

b

(Optional) Specifies switch B.

Command Default

None

Command Modes

Any command mode

Command History

Release Modification
1.0(1)

This command was introduced.

Examples

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#                                   

copy

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]

Syntax Description

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.

Command Default

None

Command Modes

Local management (local-mgmt)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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

Related Commands

Command

Description

connect local-mgmt

 

create adapter

To create an adapter, use the create adapter command.

create adapter

This command has no arguments or keywords.

Command Default

None

Command Modes

Server qualification (/org/server-qual)

Command History

Release Modification
1.0(1)

This command was introduced.

Examples

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 #                                      

Related Commands

Command

Description

show adapter

 

show chassis

 

create auth-domain

To create an authentication domain, use the create auth-domain command.

create auth-domain name

Syntax Description

name

The name of the authentication domain. This name can include a maximum of 16 characters.

Command Default

None

Command Modes

Security (/security)

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

The name of the authentication domain can include alphanumeric characters, but cannot include special characters.

Examples

This example shows how to create an authentication domain for the system:

Switch-A # scope security
Switch-A /security # create auth-domain Default
Switch-A /security/auth-domain* # commit-buffer
Switch-A /security/auth-domain # 

Related Commands

Command

Description

delete auth-domain

 

scope auth-domain

 

create auth-server-group

To create an authentication server group, use the create auth-server-group command.

create auth-server-group Authentication server group

Syntax Description

Authentication server group

The name of the authentication server group. This name can include a maximum of 127 characters.

Command Default

None

Command Modes

LDAP (/security/ldap)

RADIUS (/security/radius)

TACACS (/security/tacacs)

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

The name of the authentication server group can be alphanumeric, but special characters cannot be used.

Examples

This example shows to create an authentication server group:

Switch-A # scope security
Switch-A /security # scope ldap
Switch-A /security/ldap # create auth-server-group Default
Switch-A /security/ldap/auth-server-group* # commit-buffer
Switch-A /security/ldap/auth-server-group #

Related Commands

Command

Description

scope auth-server-group

 

delete auth-server-group

 

create backup

To create a backup, use the create backup command.

create backup file { all-configuration | logical-configuration | system-configuration | full-state } { disabled | enabled }

Syntax Description

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.

Command Default

None

Command Modes

System (/system)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                                            

Related Commands

Command

Description

show backup

 

show image

 

create bios-policy

To create a BIOS policy, use the create bios-policy command.

create bios-policy policy-name

Syntax Description

policy-name

Policy name. The name can contain up to 16 characters.

Command Default

None

Command Modes

Organization (/org)

Command History

Release Modification

1.3(1)

This command was introduced.

Usage Guidelines

Use this command to create a BIOS policy and enter org BIOS policy mode.

Examples

The following example shows how to create a BIOS policy and enter org BIOS policy mode:

switch-A# scope org org3
switch-A /org # create bios-policy bios1
switch-A /org/bios-policy* # commit-buffer
switch-A /org/bios-policy #

Related Commands

Command

Description

show bios-policy

 

create bladeserver-disc-policy

To create a compute blade discovery policy, use the create bladeserver-disc-policy command.

create bladeserver-disc-policy name

Syntax Description

name

Name of the compute blade discovery policy. This name can include a maximum of 16 characters.

Command Default

None

Command Modes

Organization (/org)

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

The name of the policy can include alphanumeric characters, but cannot include special characters.

Examples

This example shows how to create a computer blade discovery policy.

Switch-A # scope org
Switch-A /org # create bladeserver-disc-policy Sample
Switch-A /org/bladeserver-disc-policy* # commit buffer
Switch-A /org/bladeserver-disc-policy # 

Related Commands

Command

Description

scope bladeserver-disc-policy

 

enter bladeserver-disc-policy

 

show bladeserver-disc-policy

 

delete bladeserver-disc-policy

 

create block

To create a block, use the create block command.

IP pool configurationcreate block from to default-gw subnet-mask

WWN pool, UUID pool, and MAC pool configuration create block from to

Syntax Description

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.

Command Default

None

Command Modes

IP pool (/org/ip-pool)

WWN pool (/org/wwn-pool)

UUID suffix pool (/org/uuid-suffix-pool)

MAC pool (/org/mac-pool)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

This example shows how to create a block:

UCS-A# scope org org3
UCS-A /org # scope mac-pool mp1
UCS-A /org/mac-pool # create block 1a:2b:3c:4d:21:31 1b:2a:3c:4d:21:31
UCS-A /org/mac-pool* # commit-buffer
UCS-A /org/mac-pool # 

Related Commands

Command

Description

show mac-pool

 

show pooled

 

create boot-definition

To create a boot definition, use the create boot-definition command.

create boot-definition

This command has no arguments or keywords.

Command Default

None

Command Modes

Service profile (/org/service-profile)

Command History

Release Modification
1.0(1)

This command was introduced.

Examples

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 #                                     

Related Commands

Command

Description

show boot-definition

 

show lan

 

create boot-policy

To create a boot policy, use the create boot-policy command.

create boot-policy name purpose { operational | utility } *

Syntax Description

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.

Command Default

None

Command Modes

Organization (/org)

Command History

Release Modification
1.0(1)

This command was introduced.

Examples

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 #                                                  

Related Commands

Command

Description

show lan

 

show virtual-media

 

create boot-target

To create a boot-target object, use the create boot-target command.

create boot-target { primary | secondary }

Syntax Description

primary

Specifies the primary boot target.

secondary

Specifies the secondary boot target.

Command Default

None.

Command Modes

WWN initiator(/org/wwn-pool/initiator)

Command History

Release Modification
1.1(1)

This command was introduced.

Usage Guidelines

Use this command to specify a boot target for a WWN initiator.

Examples

The following example shows how to create a secondary boot target:

server# scope org
server /org # scope wwn-pool default
server /org/wwn-pool # scope initiator 20:00:00:25:B5:00:00:00
server /org/wwn-pool/initiator # create boot-target secondary
server /org/wwn-pool/initiator/boot-target* # commit-buffer
server /org/wwn-pool/initiator/boot-target #

Related Commands

Command

Description

delete boot-target

 

enter boot-target

 

scope boot-target

 

set lun

 

set wwn

 

show boot-target

 

show initiator

 

create cap-qual

To create a 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 }

Syntax Description

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.

Command Default

None

Command Modes

Adapter (/org/server-qual/adapter)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

Creates an adapter capacity qualification for the specified adapter type and enters organization server qualification adapter mode.

Examples

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 # 

Related Commands

Command

Description

show adapter

 

show server-qual

 

create certreq

To create a keyring certificate request, use the create certreq command.

create certreq { subject-name name | ip ip-address } + [ password password ]

Syntax Description

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.

Command Default

None

Command Modes

Keyring (/security/keyring)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

Before you create a certreq you must set modulus.

Examples

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 #                                                

Related Commands

Command

Description

show certreq

 

show keyring

 

create chassis

To create a chassis, use the create chassis command.

create chassis min-id max-id

Syntax Description

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.

Command Default

None

Command Modes

Server qualification (/org/server-qual)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

Creates a chassis with the specified name, and enters organization chassis mode.

Examples

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 #                                             

Related Commands

Command

Description

show chassis

 

show server

 

create class chassis-stats

To create a chassis statistics class, use the create class chassis-stats command.

create class chassis-stats

This command has no arguments or keywords.

Command Default

None

Command Modes

Statistics threshold policy (/eth-server/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                       

Related Commands

Command

Description

show chassis

 

show class

 

create class cmc-stats

To create a CMC statistics class, use the create class cmc-stats command.

create class cmc-stats

This command has no arguments or keywords.

Command Default

None

Command Modes

Statistics threshold policy (/eth-server/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                       

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class cpu-env-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                       

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class dimm-env-stats

To create a dual in-line memory module (DIMM) environment statistics class, use the create class dimm-env-stats command.

create class dimm-env-stats

This command has no arguments or keywords.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.3.1

This command was introduced.

Usage Guidelines

Examples

This example shows how to create a DIMM environment statistics class:

server# scope org
server /org # scope stats-threshold-policy default
server /org/stats-threshold-policy # create class dimm-env-stats
server /org/stats-threshold-policy/class* # commit-buffer
server /org/stats-threshold-policy/class #

Related Commands

Command

Description

delete class dimm-env-stats

 

enter class dimm-env-stats

 

scope class dimm-env-stats

 

show class dimm-env-stats

 

create class dimm-stats

To create a DIMM statistics class, use the create class dimm-stats command.

create class dimm-stats

This command has no arguments or keywords.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                       

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class env-stats

To create an environment statistics class, use the create class env-stats command.

create class env-stats

This command has no arguments or keywords.

Command Default

None

Command Modes

Ethernet server statistcics threshold policy (/eth-server/stats-threshold-policy)

Command History

Release Modification
1.3.1

This command was introduced.

Usage Guidelines

Examples

This example shows how to create an environment statistics class:

server# scope eth-server
server /eth-server # scope stats-threshold-policy default
server /eth-server/stats-threshold-policy # create class env-stats
server /eth-server/stats-threshold-policy/class* # commit-buffer
server /eth-server/stats-threshold-policy/class #

Related Commands

Command

Description

delete class env-stats

 

enter class env-stats

 

scope class env-stats

 

show class env-stats

 

create class ether-error-stats

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.

Command Default

None

Command Modes

Statistics threshold policy under Ethernet uplink (/eth-uplink/stats-threshold-policy)

Statistics threshold policy under Ethernet server (/eth-server/stats-threshold-policy)

Command History

Release Modification
1.0

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                      

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class ether-if-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                        

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class ether-loss-stats

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.

Command Default

None

Command Modes

Statistics threshold policy under Ethernet server (/eth-server/stats-threshold-policy)

Statistics threshold policy under Ethernet uplink (/eth-uplink/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                       

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class ether-pause-stats

To create an Ethernet pause statistics class, use the create class ether-pause-stats command.

create class ether-pause-stats

This command has no arguments or keywords.

Command Default

None

Command Modes

Ethernet statistics threshold policy (/eth-server/stats-threshold-policy)

Command History

Release Modification
1.31.

This command was introduced.

Usage Guidelines

Examples

This example shows how to create a class for Ethernet pause statistics:

server# scope eth-server
server /eth-server # scope stats-threshold-policy default
server /eth-server/stats-threshold-policy # create class ether-pause-stats
server /eth-server/stats-threshold-policy/class* # commit-buffer
server /eth-server/stats-threshold-policy/class #

Related Commands

Command

Description

delete class ether-pause-stats

 

enter class ether-pause-stats

 

scope class ether-pause-stats

 

show class ether-pause-stats

 

create class ethernet-port-err-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                       

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class ethernet-port-multicast-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                       

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class ethernet-port-over-under-sized-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                       

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class ethernet-port-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                       

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class ethernet-port-stats-by-size-large-packets

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                     

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class ethernet-port-stats-by-size-small-packets

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                     

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class ether-rx-stats

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.

Command Default

None

Command Modes

Statistics threshold policy under Ethernet server (/eth-server/stats-threshold-policy)

Statistics threshold policy under Ethernet uplink (/eth-uplink/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                        

Related Commands

Command

Description

show eth-uplink

 

show stats-threshold-policy

 

create class ether-tx-stats

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.

Command Default

None

Command Modes

Statistics threshold policy under Ethernet uplink (/eth-uplink/stats-threshold-policy)

Statistics threshold policy under Ethernet server (/eth-server/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                        

Related Commands

Command

Description

show eth-uplink

 

show stats-threshold-policy

 

create class fan-module-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/eth-server/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                      

Related Commands

Command

Description

show fan-module

 

show stats-threshold-policy

 

create class fan-stats

To create a fan statistics class, use the create class fan-stats command.

create class fan-stats

This command has no arguments or keywords.

Command Default

None

Command Modes

Statistics threshold policy (/eth-server/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                      

Related Commands

Command

Description

show fan-module

 

show stats-threshold-policy

 

create class fc-error-stats

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.

Command Default

None

Command Modes

Statistics threshold policy /fc-uplink/stats-threshold-policy

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                       

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class fc-if-event-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                       

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class fc-if-fc4-counters

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                      

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class fc-if-frame-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                      

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class fc-port-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                        

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class fc-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/fc-uplink/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                        

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class fex-env-stats

To create an Fex environment statistics class, use the create class fex-env-stats command.

create class fex-env-stats

This command has no arguments or keywords.

Command Default

None

Command Modes

Statistics Threshold Policy (/eth-server/stats-threshold-policy)

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

A statistics threshold policy must be created to use this command.

Examples

This example shows how to create an Fex environment statistics class:

Switch-A # scope eth-server
Switch-A /eth-server # scope stats-threshold-policy default
Switch-A /eth-server/stats-threshold-policy # create class fex-env-stats
Switch-A /eth-server/stats-threshold-policy/class* # commit-buffer
Switch-A /eth-server/stats-threshold-policy/class # 

Related Commands

Command

Description

scope class fex-env-stats

 

delete class fex-env-stats

 

create class fex-power-summary

To create an Fex power summary statistics class, use the create class fex-power-summary command.

create class fex-power-summary

This command has no arguments or keywords.

Command Default

None

Command Modes

Statistics threshold policy (/eth-server/stats-threshold-policy)

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

A statistics threshold policy must be created to use this command.

Examples

This example shows how to create an Fex power summary statistics class.

Switch-A # scope eth-server
Switch-A /eth-server # scope stats-threshold-policy default
Switch-A /eth-server/stats-threshold-policy # create class fex-power-summary
Switch-A /eth-server/stats-threshold-policy/class* # commit-buffer
Switch-A /eth-server/stats-threshold-policy/class # 

Related Commands

Command

Description

scope class fex-power-summary

 

delete class fex-power-summary

 

create class fex-psu-input-stats

To create an Fex power supply input statistics class, use the create class fex-psu-input-stats command.

create class fex-psu-input-stats

This command has no arguments or keywords.

Command Default

None

Command Modes

Statistics threshold policy (/eth-server/stats-threshold-policy)

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

A statistics threshold policy must be created to use this command.

Examples

This example shows how to create an Fex power supply input statistics class:

Switch-A # scope eth-server
Switch-A /eth-server # scope stats-threshold-policy default
Switch-A /eth-server/stats-threshold-policy # create class fex-psu-input-stats
Switch-A /eth-server/stats-threshold-policy/class* # commit-buffer
Switch-A /eth-server/stats-threshold-policy/class # 

Related Commands

Command

Description

scope class fex-psu-input-stats

 

delete class fex-psu-input-stats

 

create class io-card-stats

To create an Ethernet IO card statistics class, use the create class io-card-stats command.

create class io-card-stats

This command has no arguments or keywords.

Command Default

None

Command Modes

Ethernet statistics threshold policy (/eth-server/stats-threshold-policy)

Command History

Release Modification
1.3.1

This command was introduced.

Usage Guidelines

Examples

This example shows how to create an IO card statistics class:

server# scope eth-server
server /eth-server # scope stats-threshold-policy default
server /eth-server/stats-threshold-policy # create class io-card-stats
server /eth-server/stats-threshold-policy/class* # commit-buffer
server /eth-server/stats-threshold-policy/class #

Related Commands

Command

Description

delete class io-card-stats

 

enter class io-card-stats

 

scope class io-card-stats

 

show class io-card-stats

 

create class mb-power-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                        

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class mb-temp-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                      

Related Commands

Command

Description

show class

 

show class mb-temp-stats

 

create class memory-array-env-stats

To create a class for memory array environment statistics, use the create class memory-array-env-stats command.

create class memory-array-env-stats

This command has no arguments or keywords.

Command Default

None

Command Modes

Statistcis threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.3.1

This command was introduced.

Usage Guidelines

Examples

This example shows how to create a class to store the memory array environment statistics:

server# scope org
server /org # scope stats-threshold-policy default
server /org/stats-threshold-policy # create class memory-array-env-stats
server /org/stats-threshold-policy/class* # commit-buffer
server /org/stats-threshold-policy/class #

Related Commands

Command

Description

delete class memory-array-env-stats

 

enter class memory-array-env-stats

 

scope class memory-array-env-stats

 

show class memory-array-env-stats

 

create class memory-runtime

To create a memory runtime class, use the create class memory-runtime command.

create class memory-runtime

This command has no arguments or keywords.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Examples

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 #                                      

Related Commands

Command

Description

show class

 

show memory

 

create class menlo-dce-port-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                      

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class menlo-eth-error-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                      

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class menlo-eth-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                      

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class menlo-fc-error-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                     

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class menlo-fc-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                     

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class menlo-host-port-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                     

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class menlo-mcpu-error-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                     

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class menlo-mcpu-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                     

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class menlo-net-eg-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                       

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class menlo-net-in-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                       

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class menlo-q-error-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                       

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class menlo-q-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                       

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class pcie-fatal-completion-error-stats

To create a Peripheral Component Interconnect (PCI) Express (PCIe) fatal completion error statistics class, use the create class pcie-fatal-completion-error-stats command.

create class pcie-fatal-completion-error-stats

This command has no arguments or keywords.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.3.1

This command was introduced.

Usage Guidelines

Examples

This example shows how to create a PCIe fatal completion error statistics class:

server# scope org
server /org # scope stats-threshold-policy default
server /org/stats-threshold-policy # create class pcie-fatal-completion-error-stats
server /org/stats-threshold-policy/class* # commit-buffer
server /org/stats-threshold-policy/class #

Related Commands

Command

Description

delete class pcie-fatal-completion-error-stats

 

enter class pcie-fatal-completion-error-stats

 

scope class pcie-fatal-completion-error-stats

 

show class pcie-fatal-completion-error-stats

 

create class pcie-fatal-error-stats

To create a Peripheral Component Interconnect (PCI) Express (PCIe) fatal errors statistics class, use the create class pcie-fatal-error-stats command.

create class pcie-fatal-error-stats

This command has no arguments or keywords.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.3.1

This command was introduced.

Usage Guidelines

Examples

This example shows how to create a PCIe fatal error statistics class:

server# scope org
server /org # scope stats-threshold-policy default
server /org/stats-threshold-policy # create class pcie-fatal-error-stats
server /org/stats-threshold-policy/class* # commit-buffer
server /org/stats-threshold-policy/class #

Related Commands

Command

Description

delete class pcie-fatal-error-stats

 

enter class pcie-fatal-error-stats

 

scope class pcie-fatal-error-stats

 

show class pcie-fatal-error-stats

 

create class pcie-fatal-protocol-error-stats

To create a Peripheral Component Interconnect (PCI) Express (PCIe) fatal protocol error statistics class, use the create class pcie-fatal-protocol-error-stats command.

create class pcie-fatal-protocol-error-stats

This command has no arguments or keywords.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.3.1

This command was introduced.

Usage Guidelines

Examples

This example shows how to create a PCIe fatal protocol error statistics class:

server# scope org
server /org # scope stats-threshold-policy default
server /org/stats-threshold-policy # create class pcie-fatal-protocol-error-stats
server /org/stats-threshold-policy/class* # commit-buffer
server /org/stats-threshold-policy/class #

Related Commands

Command

Description

delete class pcie-fatal-protocol-error-stats

 

enter class pcie-fatal-protocol-error-stats

 

scope class pcie-fatal-protocol-error-stats

 

show class pcie-fatal-protocol-error-stats

 

create class pcie-fatal-receiving-error-stats

To create a Peripheral Component Interconnect (PCI) Express (PCIe) fatal receive errors statistics class, use the create class pcie-fatal-receiving-error-stats command.

create class pcie-fatal-receiving-error-stats

This command has no arguments or keywords.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.3.1

This command was introduced.

Usage Guidelines

Examples

This example shows how to create a PCIe fatal receive errors statistics class:

server# scope org
server /org # scope stats-threshold-policy default
server /org/stats-threshold-policy # create class pcie-fatal-receiving-error-stats
server /org/stats-threshold-policy/class* # commit-buffer
server /org/stats-threshold-policy/class #

Related Commands

Command

Description

delete class pcie-fatal-receiving-error-stats

 

enter class pcie-fatal-receiving-error-stats

 

scope class pcie-fatal-receiving-error-stats

 

show class pcie-fatal-receiving-error-statss

 

create class processor-runtime

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Examples

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 #                                       

Related Commands

Command

Description

show class

 

show stats-threshold-statistics

 

create class psu-input-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/eth-server/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                    

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class psu-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/eth-server/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                    

Related Commands

Command

Description

show class

 

show stats-threshold-policy

 

create class rack-unit-fan-stats

To create a rack unit fan statistics class, use the create class rack-unit-fan-stats command.

create class rack-unit-fan-stats

This command has no arguments or keywords.

Command Default

None

Command Modes

Statistics threshold policy (/eth-server/stats-threshold-policy)

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

A statistics threshold policy must be created to use this command.

Examples

This example shows how to create a rack unit fan statistics class:

Switch-A # scope eth-server
Switch-A /eth-server # scope stats-threshold-policy default
Switch-A /eth-server/stats-threshold-policy # create class rack-unit-fan-stats
Switch-A /eth-server/stats-threshold-policy/class* # commit-buffer
Switch-A /eth-server/stats-threshold-policy/class #

Related Commands

Command

Description

scope class rack-unit-fan-stats

 

delete class rack-unit-fan-stats

 

create class rack-unit-psu-stats

To create a rack unit power supply statistics class, use the create class rack-unit-psu-stats command.

create class rack-unit-psu-stats

This command has no arguments or keywords.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

A statistics threshold policy must be created to use this command.

Examples

This example shows how to create a rack unit power supply statistics class:

Switch-A # scope org
Switch-A /org # scope stats-threshold-policy Default
Switch-A /org/stats-threshold-policy # create class rack-unit-psu-stats
Switch-A /org/stats-threshold-policy/class* # commit-buffer
Switch-A /org/stats-threshold-policy/class # 

Related Commands

Command

Description

scope class rack-unit-psu-stats

 

delete class rack-unit-psu-stats

 

create class system-stats

To create a system statistics class, use the create class system-stats command.

create class system-stats

This command has no arguments or keywords.

Command Default

None

Command Modes

Statistics threshold policy (/eth-server/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                    

Related Commands

Command

Description

show class

 

show system

 

create class vnic-stats

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.

Command Default

None

Command Modes

Statistics threshold policy (/org/stats-threshold-policy)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                    

Related Commands

Command

Description

show class

 

show vnic-templ

 

create client

To create a client, use the create client command in port-profile mode.

create client client-name

Syntax Description

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.

Command Default

None

Command Modes

Profile set (/system/vm-mgmt/vmware/profile-set/port-profile)

Command History

Release Modification
1.1(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                      

Related Commands

Command

Description

show port profile

 

show profile-set

 

create cpu

To create a CPU qualifier for a server pool policy, use the create cpu command.

create cpu

This command has no arguments or keywords.

Command Default

None

Command Modes

Server qualification (/org/server-qual)

Command History

Release Modification
1.3(1)

This command was introduced.

Usage Guidelines

Use this command create a CPU qualifier for a server pool policy, and to enter organization CPU mode.

Only one CPU qualifier can be created.

Examples

This example shows how to create a CPU qualifier:

switch# scope org org3
switch /org # scope server-qual sq20
switch /org/server-qual # create cpu
switch /org/server-qual/cpu* # commit-buffer 
switch /org/server-qual/cpu #

Related Commands

Command

Description

show cpu

 

show server-qual

 

create data-center

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

Syntax Description

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.

Command Default

None

Command Modes

VCenter (/system/vm-mgmt/vmware/vcenter)

Folder (/system/vm-mgmt/vmware/vcenter/folder

Command History

Release Modification
1.1(1)

This command was introduced.

Usage Guidelines

Data center

Examples

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 #                                      

Related Commands

Command

Description

show data-center

 

show folder

 

create default-auth

To create a default authentication method for an authentication domain, use the create default-auth command.

create default-auth

This command has no arguments or keywords.

Command Default

None

Command Modes

Authentication Domain (/security/auth-domain)

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

An authentication domain must be created to use this command.

Examples

This example shows how to create a default authentication method for an authentication domain:

Switch-A # scope security
Switch-A /security # scope auth-domain Default
Switch-A /security/auth-domain # create default-auth
Switch-A /security/auth-domain/default-auth* # commit-buffer
Switch-A /security/auth-domain/default-auth #

Related Commands

Command

Description

scope default-auth

 

delete default-auth

 

create default-behavior

To create a default behavior mode, use the create default-behavior command.

create default-behavior { vhba | | vnic }

Syntax Description

vhba

Specifies vHBA default behavior mode.

vnic

Specifies vNIC default behavior mode.

Command Default

None

Command Modes

Service profile (/org/service-profile)

Command History

Release Modification
1.1(1)

This command was introduced.

Usage Guidelines

Use this command to create a default behavior, and enter organization default-behavior mode.

hw-inherit sets

Examples

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 #                                          

Related Commands

Command

Description

show default-behavior

 

show vnic

 

create destination

To create an email destination, use the create destination command.

create destination email

Syntax Description

email

Email destination.

Command Default

None

Command Modes

Profile (/monitoring/callhome/profile)

Command History

Release Modification
1.0(1)

This command was introduced.

Examples

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 #                                          

Related Commands

Command

Description

show callhome

 

show destination

 

create dest-interface

To create a destination interface for the Fibre Channel traffic monitoring session or the Ethernet traffic monitoring session, use the create dest-interface command.

create dest-interface slotid portid

Syntax Description

slotid

The slot ID of the interface. It must be a value between 1-5

portid

The port ID of the interface. It must be a value between 1-40.

Command Default

None

Command Modes

Fibre Channel traffic monitoring session (/fc-traffic-mon/fabric/fc-mon-session)

Ethernet traffic monitoring session (/eth-traffic-mon/fabric/eth-mon-session)

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

A Fibre Channel traffic monitoring session or an Ethernet traffic monitoring session must be created prior to using this command.

Examples

This example shows how to create a destination interface for the Ethernet traffic monitoring session.

To create a destination interface for the Fibre Channel traffic monitoring session, replace eth-traffic-mon with fc-traffic-mon , and eth-mon-session with fc-mon-session .

Switch-A # scope eth-traffic-mon
Switch-A /eth-traffic-mon # scope fabric a
Switch-A /eth-traffic-mon/fabric # scope eth-mon-session Default
Switch-A /eth-traffic-mon/fabric/eth-mon-session # create dest-interface 2 33 
Switch-A /eth-traffic-mon/fabric/eth-mon-session/dest-interface* # commit buffer
Switch-A /eth-traffic-mon/fabric/eth-mon-session/dest-interface #  

Related Commands

Command

Description

delete dest-interface

 

create distributed-virtual-switch

To create a distributed virtual switch, use the create distributed-virtual-switch command in folder mode.

create distributed-virtual-switch dvs-name

Syntax Description

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.

Command Default


  • Admin State is disabled

  • UUID is 00000000-0000-0000-0000-000000000000

  • Extension key is blank

Command Modes

VMware (/system/vm-mgmt/vmware/vcenter/data-center/folder)

Command History

Release Modification
1.1(1)

This command was introduced.

Usage Guidelines

Distributed virtual switch

Examples

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 #                                      

Related Commands

Command

Description

show distributed-virtual-switch

 

show folder

 

create dns

To create a DNS host name , use the create dns command.

create dns name

Syntax Description

name

DNS host name. The range of valid values is 1 to 16.

Command Default

None

Command Modes

Services (/system/services)

Command History

Release Modification
1.0(1)

This command was introduced.

Examples

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 #                                        

Related Commands

Command

Description

show dns

 

show ntp

 

create dynamic-vnic-conn

To create a dynamic vNIC connection, use the create dynamic-vnic-conn command.

create dynamic-vnic-conn

This command has no arguments or keywords.

Command Default

None

Command Modes

Service profile (/org/service-profile)

Command History

Release Modification
1.1(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                                  

Related Commands

Command

Description

show dynamic-vnic-con

 

show dynamic-vnic-con-policy

 

create dynamic-vnic-conn-policy

To create a dynamic vNIC connection policy, use the create dynamic-vnic-conn-policy command.

create dynamic-vnic-conn-policy policy-name

Syntax Description

policy-name

The name of the vNIC connection policy. The range of valid values is 1 to 16.

Command Default

None

Command Modes

Organization (/org)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                                  

Related Commands

Command

Description

show dynamic-vnic-connection-policy

 

show vnic-templ

 

create egress-policy

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

Syntax Description

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.

Command Default

None

Command Modes

Egress policy (/org/qos-policy/egress-policy)

Command History

Release Modification
1.1(1)

This command was introduced.

Usage Guidelines

Data center

Examples

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 #                                      

Related Commands

Command

Description

show data-center

 

show folder

 

create eth-if

To create an Ethernet interface, use the create eth-if command.

create eth-if name

Syntax Description

name

Interface name. The range of valid values is 1 to 16.

Command Default

None

Command Modes

Virtual NIC (/org/service-profile/vnic)

Virtual NIC template (/org/vnic-templ)

Command History

Release Modification
1.0(1)

This command was introduced.

Examples

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 #                                         

Related Commands

Command

Description

show eth-profile

 

show service-profile

 

create eth-mon-session

To create an Ethernet traffic monitoring session mode, use the create eth-mon-session command.

create eth-mon-session name

Syntax Description

name

The name of the Ethernet traffic monitoring session. The name can include a maximum of 16 characters.

Command Default

None

Command Modes

Fabric (/eth-traffic-mon/fabric)

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

The name of the session can include alphanumeric characters. You cannot include special characters.

Examples

This example shows how to create an Ethernet traffic monitoring session:

Switch-A # scope eth-traffic-mon
Switch-A /eth-traffic-mon # scope fabric a
Switch-A /eth-traffic-mon/fabric # create eth-mon-session Default
Switch-A /eth-traffic-mon/fabric/eth-mon-session* # commit-buffer
Switch-A /eth-traffic-mon/fabric/eth-mon-session #

Related Commands

Command

Description

scope eth-mon-session

 

delete eth-mon-session

 

create eth-policy

To create an Ethernet policy, use the create eth-policy command.

create eth-policy name

Syntax Description

policy-name

The name of the Ethernet policy. The range of valid values is 1 to 16.

Command Default

None

Command Modes

Organization (/org)

Command History

Release Modification
1.0(1)

This command was introduced.

Examples

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 #                                         

Related Commands

Command

Description

show eth-policy

 

show trans-queue

 

create eth-target

To create an Ethernet target endpoint for a fabric interface, use the create eth-target command.

create eth-target name

Syntax Description

name

The name of the Ethernet target endpoint. The name can include a maximum of 16 characters.

Command Default

None

Command Modes

Interface (/eth-storage/fabric/interface)

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

An interface for a fabric must be created to use this command.

The name of the Ethernet target endpoint can be alphanumeric, but cannot include special characters.

Examples

This example shows how to create an Ethernet target endpoint for a fabric interface.

Switch-A # scope eth-storage
Switch-A /eth-storage # scope fabric a
Switch-A /eth-storage/fabric # scope interface 2 33
Switch-A /eth-storage/fabric/interface # create eth-target Testing
Switch-A /eth-storage/fabric/interface/eth-target* # commit-buffer
Switch-A /eth-storage/fabric/interface/eth-target # 

Related Commands

Command

Description

set macaddress

 

scope eth-target

 

enter eth-target

 

show eth-target

 

delete eth-target

 

create ext-static-ip

To create an external static management IP, use the create ext-static-ip command.

create ext-static-ip

This command has no arguments or keywords.

Command Default

None

Command Modes

CIMC (/chassis/server/cimc)

Service profile (/org/service-profile)

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

A service profile must be created to use this command.

You cannot use this command to set an external static management IP for a service profile that uses an initial template.

Examples

This example shows how to set an external static management IP address for the CIMC.

Switch-A # scope server 1/7
Switch-A /chassis/server # scope cimc
Switch-A /chassis/server/cimc # create ext-static-ip
Switch-A /chassis/server/cimc/ext-static-ip* # commit-buffer
Switch-A /chassis/server/cimc/ext-static-ip # 

Related Commands

Command

Description

scope ext-static-ip

 

enter ext-static-ip

 

show ext-static-ip

 

delete ext-static-ip

 

create fc-mon-session

To create a Fibre Channel traffic monitoring session, use the create fc-mon-session command.

create fc-mon-session Name

Syntax Description

Name

Name of the monitoring session. The name can include a maximum of 16 characters, and can include alphanumeric characters.

Command Default

None

Command Modes

Fabric (/fc-traffic-mon/fabric)

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

The Fibre Channel traffic monitoring session must be created prior to using this command.

The name of the Fibre Channel monitoring session cannot include special characters.

Examples

This example shows how to create a Fibre Channel monitoring session:

Switch-A # scope fc-traffic-mon
Switch-A /fc-traffic-mon # scope fabric a
Switch-A /fc-traffic-mon/fabric # create fc-mon-session Default
Switch-A /fc-traffic-mon/fabric/fc-mon-session* # commit-buffer

Related Commands

Command

Description

scope fc-mon-session

 

delete fc-mon-session

 

create fcoe-if

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.

Command Default

None

Command Modes

Virtual NIC (/org/service-profile/vnic)

Command History

Release Modification
1.0(1)

This command was introduced.

Examples

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 #                                   

Related Commands

Command

Description

show interface

 

show vnic

 

create fc-policy

To create a Fibre Channel policy, use the create fc-policy command.

create fc-policy policy-name

Syntax Description

policy-name

The name of the Fibre Channel policy. The range of valid values is 1 to 16.

Command Default

None

Command Modes

Organization (/org)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

Use this command to create a Fibre Channel policy, and enter organization fc-policy mode.

Examples

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 #                                          

Related Commands

Command

Description

show fc-policy

 

show trans-queue

 

create folder

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

Syntax Description

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.

Command Default

None

Command Modes

VCenter (/system/vm-mgmt/vmware/vcenter)

Folder (/system/vm-mgmt/vmware/vcenter/data-center

Command History

Release Modification
1.1(1)

This command was introduced.

Usage Guidelines

Folder

Examples

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 #                                      

Related Commands

Command

Description

show folder

 

show vcenter

 

create fw-host-pack

To create a host pack, use the create fw-host-pack command.

create fw-host-pack name

Syntax Description

name

Pack name. The range of valid values is 1 to 16.

Command Default

None

Command Modes

Organization (/org)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                        

Related Commands

Command

Description

show fw- host-pack

 

show fw-mgmt-pack

 

create fw-mgmt-pack

To create a management pack, use the create fw-mgmt-pack command.

create fw-mgmt-pack name

Syntax Description

name

Pack name. The range of valid values is 1 to 16.

Command Default

None

Command Modes

Organization (/org)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

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.

Examples

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 #                                        

Related Commands

Command

Description

show fw- host-pack

 

show fw-mgmt-pack

 

create hv-conn

To create an HV connection, use the create hv-conn command.

create hv-conn protection { none | protected } *

Syntax Description

protection

Specifies that the connection is protected.

none

Specifies no protection.

protected

Specifies protection.

Command Default

None

Command Modes

Service profile (/org/service-profile)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

Use this command to create a Hypervisor connection, and enter organization HV connection mode.

Examples

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 #                                                

Related Commands

Command

Description

show connectivity

 

show hv-conn

 

create import-config

To create a import configuration, use the create import-config command.

create import-config { ftp: | scp: | sftp: | tftp: } { disabled | enabled } { merge | replace }

Syntax Description

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.

Command Default

None

Command Modes

System (/system)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

Use this command to create a configuration for importing files, and enter organization import configuration mode.

Examples

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 #                                   

Related Commands

Command

Description

show image

 

show import-config

 

create initiator

To create an initiator, use the create initiator command.

create initiator id

Syntax Description

id

Initiator identification number. The range of valid values is 1 to 16.

Command Default

None

Command Modes

WWN pool (/org/wwn-pool)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

Use this command to create a WWN initiator, and enter organization initiator mode.

Examples

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 #                                           

Related Commands

Command

Description

show block

 

show initiator

 

create interface

To create an interface, use the create interface command.

create interface slot-id port-id

Syntax Description

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.

Command Default

None

Command Modes

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)

Fabric interconnect under Ethernet storage (/eth-storage/fabric)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

Use this command to create an Ethernet or Fibre Channel interface, and enter organization interface mode.

Examples

This example shows how to create an interface:

switch-A# scope fc-uplink
switch-A /fc-uplink # scope fabric b
switch-A /fc-uplink/fabric # create interface 5 10
switch-A /fc-uplink/fabric/interface* # commit-buffer
switch-A /fc-uplink/fabric/interface #

Related Commands

Command

Description

show interface

 

show switch

 

create interface fc

To create a Fibre Channel interface for a fabric, use the create interface fc command.

create interface fc slot id port id

Syntax Description

slot id

The slot identification number. The range of valid values is 2 to 5.

port id

The port identification of the interface. The range of valid values is 1 to 40.

Command Default

None

Command Modes

Fabric (/fc-storage/fabric)

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

None

Examples

This example shows how to create a fibre channel interface for a fabric.

Switch-A # scope fc-storage
Switch-A /fc-storage # scope fabric a
Switch-A /fc-storage/fabric # create interface fc 2 33
Switch-A /fc-storage/fabric/fc* # commit-buffer
Switch-A /fc-storage/fabric/fc # 

Related Commands

Command

Description

scope interface fc

 

enter interface fc

 

show interface fc

 

delete interface fc

 

create interface fcoe

To create a Fibre Channel over Ethernet interface for a fabric, use the create interface fcoe command.

create interface fcoe slot id port id

Syntax Description

slot id

The slot identification number. The range of valid values is 2 to 5.

port id

The port identification number. The range of valid values is 1 to 40.

Command Default

None

Command Modes

Fabric (/fc-storage/fabric)

Command History

Release Modification
1.4(1)

This command was introduced.

Usage Guidelines

None

Examples

This example shows how to create a Fibre Channel over Ethernet interface for a fabric.

Switch-A # scope fc-storage
Switch-A /fc-storage # scope fabric a
Switch-A /fc-storage/fabric # create interface fcoe 3 40
Switch-A /fc-storage/fabric/fcoe* # commit-buffer
Switch-A /fc-storage/fabric/fcoe # 

Related Commands

Command

Description

scope interface fcoe

 

enter interface fcoe

 

show interface fcoe

 

delete interface fcoe

 

create ipmi-access-profile

To create an IPMI (Intelligent Platform Management Interface) access profile, use the create ipmi-access-profile command.

create ipmi-access-profile name

Syntax Description

name

IPMI access profile name. The range of valid values is 1 to 16.

Command Default

None

Command Modes

Organization (/org)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

Use this command to create an IPMI access profile, and enter organization IPMI access profile mode.

Examples

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 #                                           

Related Commands

Command

Description

show epuser

 

show ipmi-access-profile

 

create ipmi-user

To create an end-point user, use the create ipmi-user command.

create ipmi-user name

Syntax Description

name

End-point user name. The range of valid values is 1 to 16.

Command Default

None

Command Modes

IPMI access profile (/org/ipmi-access-profile)

Command History

Release Modification
1.0(1)

This command was introduced as create epuser.

1.4(1)

This command was renamed as create ipmi-user.

Usage Guidelines

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

Examples

This example shows how to create an IPMI user:

switch-A# scope org org10

switch-A /org # scope ipmi-access-profile ap10
                                          
switch-A /org/ipmi-access-profile # create ipmi-user user10
 
switch-A /org/ipmi-access-profile/ipmi-user* # commit-buffer

switch-A /org/ipmi-access-profile/ipmi-user #                                         

Related Commands

Command

Description

show ipmi-user

 

show ipmi-access-profile

 

create keyring

To create a keyring, use the create keyring command.

create keyring name

Syntax Description

name

Keyring name. The name can be up to 16 alphanumeric characters.

Command Default

None

Command Modes

Security (/security)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

Use this command to create a keyring to store RSA keys, and enter organization keyring mode.

Examples

This example shows how to create a keyring:

switch# scope security
switch /security # create keyring kr220
switch /security/keyring* # commit-buffer
switch /security/keyring #

Related Commands

Command

Description

show keyring

 

create lan

To create a LAN, use the create lan command.

create lan

This command has no arguments or keywords.

Command Default

None

Command Modes

Boot policy under organization (/org/boot-policy)

Boot definition under service-profile (/org/service-profile/boot-def)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

Use this command to create a LAN, and enter organization lan mode.

Examples

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 #                                       

Related Commands

Command

Description

show boot-policy

 

show lan

 

create ldap-group

To create an LDAP group, use the create ldap-group command.

create ldap-group Group DN

Syntax Description

Group DN

The group description. The name of the LDAP group can contain a maximum of 127 characters.