Command Default

Command Modes

Command History

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 10switch-A* # commit-bufferswitch-A #

Related Commands

Command

Description

show chassis

show server

acknowledge fault

To acknowledge a fault, use the acknowledgefault command.

acknowledgefaultid

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 1switch-A* # commit-bufferswitch-A #

Related Commands

Command

Description

show cli

show fault

acknowledge server

To acknowledge a server, use the acknowledgeserver command.

acknowledgeserver
{ 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:

Syntax Description

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:

Command Default

Command Modes

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.

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:

Command Default

Command Modes

Command History

Usage Guidelines

Use this command to back up the system event log (SEL) for a server. When entering this command in the command mode of the specific server (/chassis/server), do not enter the server-id.

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 clearalertgroups command.

clearalertgroups

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.

Related Commands

clear license

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

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

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.

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

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

Related Commands

clear sshkey

To clear from cache the SSH public key of a remote host, use the clearsshkey command in local management mode.

clearsshkeyhost-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 clusterforceprimary command.

clusterforceprimary

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-mgmtNexus 5000 SwitchCisco UCS 6100 Series Fabric InterconnectTAC support: http://www.cisco.com/tacCopyright (c) 2009, Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained herein are owned byother third parties and are used and distributed under license.Some parts of this software may be covered under the GNU PublicLicense or the GNU Lesser General Public License. A copy ofeach such license is available athttp://www.gnu.org/licenses/gpl.html andhttp://www.gnu.org/licenses/lgpl.htmlswitch-A# cluster force primaryswitch-A#

Related Commands

Command

Description

show cluster

show file

cluster lead

To designate a cluster leader, use the clusterlead command.

clusterlead
[ 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-mgmtNexus 5000 SwitchCisco UCS 6100 Series Fabric InterconnectTAC support: http://www.cisco.com/tacCopyright (c) 2009, Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained herein are owned byother third parties and are used and distributed under license.Some parts of this software may be covered under the GNU PublicLicense or the GNU Lesser General Public License. A copy ofeach such license is available athttp://www.gnu.org/licenses/gpl.html andhttp://www.gnu.org/licenses/lgpl.htmlswitch-A# cluster lead bswitch-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 3switch-A /org* # commit-bufferswitch-A /org #

Related Commands

Command

Description

discard-buffer

show configuration pending

connect adapter

To connect to an adapter, use the connectadapter command.

connectadapterchassis-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/1adapter 1/1 #

connect bmc

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

connectbmcchassis-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:

Examples

connect local-mgmt

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

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

connectnxos [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 bNexus 5000 SwitchCisco UCS 6100 Series Fabric InterconnectTAC support: http://www.cisco.com/tacCopyright (c) 2009, Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained herein are owned byother third parties and are used and distributed under license.Some parts of this software may be covered under the GNU PublicLicense or the GNU Lesser General Public License. A copy ofeach such license is available athttp://www.gnu.org/licenses/gpl.html andhttp://www.gnu.org/licenses/lgpl.htmlswitch-B#

copy

To copy a file from one directory to another, use the copy command in local management command mode.

Syntax Description

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

create block

To create a block, use the createblock command.

IP pool configuration createblockfromtodefault-gwsubnet-mask

WWN pool, UUID pool, and MAC pool configuration createblockfromto

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.

Related Commands

create class chassis-stats

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

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

Related Commands

create class cmc-stats

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

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

Related Commands

create class dimm-stats

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

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

Command Default

Command Modes

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.

Related Commands

create class ether-if-stats

To create an Ethernet interface statistics class, use the createclassether-if-stats command.

createclassether-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:

Command Default

Command Modes

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.

Related Commands

create class ethernet-port-err-stats

To create an Ethernet port error statistics class, use the createclassethernet-port-err-stats command.

createclassethernet-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:

Related Commands

create class ethernet-port-multicast-stats

To create an Ethernet port multicast statistics class, use the createclassethernet-port-multicast-stats command.

createclassethernet-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:

Related Commands

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

To create an Ethernet port over-under-sized statistics class, use the createclassethernet-port-over-under-sized-stats command.

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

Related Commands

create class ethernet-port-stats

To create an Ethernet port statistics class, use the createclassethernet-port-stats command.

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

Related Commands

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

To create an Ethernet port large packet statistics class, use the createclassethernet-port-stats-by-size-large-packets command.

createclassethernet-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:

Related Commands

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

To create an Ethernet port small packet statistics class, use the createclassethernet-port-stats-by-size-small-packets command.

createclassethernet-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:

Command Default

Command Modes

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:

Command Default

Command Modes

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:

Related Commands

create class fan-module-stats

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

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

Related Commands

create class fan-stats

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

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

Related Commands

create class fc-error-stats

To create a Fibre Channel error statistics class, use the createclassfc-error-stats command.

createclassfc-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:

Related Commands

create class fc-if-event-stats

To create Fibre Channel event statistics, use the createclassfc-if-event-stats command.

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

Related Commands

create class fc-if-fc4-counters

To create Fibre Channel counters, use the createclassfc-if-fc4-counters command.

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

Related Commands

create class fc-if-frame-stats

To create a Fibre Channel frame statistics class, use the createclassfc-if-frame-stats command.

createclassfc-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:

create class fc-port-stats

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:

Related Commands

create class fc-stats

To create a Fibre Channel statistics class, use the createclassfc-stats command.

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

Related Commands

create class mb-power-stats

To create a mother board power statistics class, use the createclassmb-power-stats command.

createclassmb-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:

Related Commands

create class mb-temp-stats

To create a temporary mother board statistics class, use the createclassmb-temp-stats command.

createclassmb-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:

Related Commands

create class menlo-dce-port-stats

To create a Menlo port statistics class, use the createclassmenlo-dce-port-stats command.

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

Related Commands

create class menlo-eth-error-stats

To create a Menlo Ethernet error statistics class, use the createclassmenlo-eth-error-stats command.

createclassmenlo-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:

Related Commands

create class menlo-eth-stats

To create a Menlo Ethernet statistics class, use the createclassmenlo-eth-stats command.

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

create class menlo-fc-error-stats

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.

Related Commands

create class menlo-fc-stats

To create Menlo Fibre Channel statistics, use the createclassmenlo-fc-stats command.

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

Related Commands

create class menlo-host-port-stats

To create Menlo host port statistics, use the createclassmenlo-host-port-stats command.

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

Related Commands

create class menlo-mcpu-error-stats

To create a Menlo CPU error statistics class, use the createclassmenlo-mcpu-error-stats command.

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

Related Commands

create class menlo-mcpu-stats

To create a Menlo CPU statistics class, use the createclassmenlo-mcpu-stats command.

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

Related Commands

create class menlo-net-eg-stats

To create a Menlo network egress statistics class, use the createclassmenlo-net-eg-stats command.

createclassmenlo-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:

Related Commands

create class menlo-net-in-stats

To create a Menlo network ingress statistics class, use the createclassmenlo-net-in-stats command.

createclassmenlo-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:

Related Commands

create class menlo-q-error-stats

To create a Menlo Qlogic error statistics class, use the createclassmenlo-q-error-stats command.

createclassmenlo-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:

Related Commands

create class menlo-q-stats

To create a Menlo Qlogic statistics class, use the createclassmenlo-q-stats command.

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

Related Commands

create class psu-input-stats

To create a power supply input statistics class, use the createclasspsu-input-stats command.

createclasspsu-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:

Related Commands

create class psu-stats

To create a power supply statistics class, use the createclasspsu-stats command.

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

Related Commands

create class system-stats

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

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

Related Commands

create class vnic-stats

To create a Virtual NIC statistics class, use the createclassvnic-stats command.

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

Related Commands

create dynamic-vnic-conn

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

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

Related Commands

create dynamic-vnic-conn-policy

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

createdynamic-vnic-conn-policypolicy-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.

Command Default

Command Modes

Command History

Usage Guidelines

The create org-ref command creates a an organization reference to a locale. Use this command to create a organization reference, and enter organization organization reference mode.

You can specify more than one org-ref-name and orgdn-name argument on the same command line to reference multiple organizations to the locale, or you can add organizations to the same locale using multiple create org-ref commands.

Examples

This example shows how to create an organization reference to a locale:

create pin-group

Syntax Description

Command Default

Command Modes

Ethernet uplink (/eth-uplink)

Fibre Channel uplink (/fc-uplink)

Command History

Release

Modification

1.0(1)

This command was introduced.

Usage Guidelines

Pinning in Cisco UCS is only relevant to uplink ports.

When you determine the optimal configuration for pin groups and pinning for an uplink port, consider the estimated bandwidth usage for the servers. If you know that some servers in the system will use a lot of bandwidth, ensure that you pin these servers to different uplink ports.

Use this command to create a pin group, and enter organization pin-group mode.

Related Commands

create policy

Syntax Description

Select a predefined fault or system event type. See Usage Guidelines for event options.

name

Policy name. The name can be from 1 to 16 characters.

Command Default

None

Command Modes

Callhome (/monitoring/callhome)

Flow control (/eth-uplink/flow-control)

Command History

Release

Modification

1.0(1)

This command was introduced.

1.1(1)

This command was modified to add additional event types for Call Home.

Usage Guidelines

Use this command to create a policy, and enter either organization callhome or organization flow control mode.

In Call Home configuration, use this command to create an instance of a policy for a predefined type of fault or system event. The following list shows the available keywords for Call Home event types:

association-failed

chassis-seeprom-error

configuration-failure

connectivity-problem

election-failure

equipment-inaccessible

equipment-inoperable

equipment-problem

fru-problem

identity-unestablishable

link-down

management-services-failure

management-services-unresponsive

power-problem

thermal-problem

unspecified

version-incompatible

voltage-problem

In Flow Control configuration, use this command to create a named policy.

Examples

This example shows how to create and enable a Call Home policy instance for link-down events:

Related Commands

create port-profile (profile-set)

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

createport-profileprofile-name

Syntax Description

profile-name

The name of the profile. A unique set of numbers or letters that identifies the profile. The range of valid values is 1 to 31.

Command Default

None

Command Modes

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

Command History

Release

Modification

1.1(1)

This command was introduced.

Usage Guidelines

The port profile client determines the DVSes to which a port profile is applied. By default, a port profile applies to all DVSes in the vCenter; however, you can use a port profile client to apply a port profile to all DVSes in a specific datacenter or datacenter folder, or to a specific DVS.