To acknowledge a chassis, use the
acknowledgechassis command.
acknowledge
chassisid
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.
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:
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:
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:
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:
To back up the system event log (SEL), use the
backupsel command.
backupselserver-id
Syntax Description
server-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.
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.
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.
Examples
This example shows how to clear alert groups in a Call Home profile:
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.
clearsel
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
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:
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:
switch-A# connect bmc 1/1Trying 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
connectiom command.
connectiomid
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 1Attaching to FEX 1 ...To exit type 'exit', to abort type '$.'fex-1#
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.
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
createadapter 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.
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.
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:
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:
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 createproperty command in the mode.
Examples
This example shows how to create a CPU environment statistics class:
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:
To create an Ethernet error statistics class, use the
createclassether-error-stats command.
createclassether-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:
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:
To create an Ethernet loss statistics class, use the
createclassether-loss-stats command.
createclassether-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:
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:
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:
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:
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:
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:
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:
To create an Ethernet recieve statistics class, use the
createclassether-rx-stats command.
createclassether-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:
To create an Ethernet transmission statistics class, use the
createclassether-tx-stats command.
createclassether-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:
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:
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:
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:
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.
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:
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:
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:
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:
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:
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:
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:
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:
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:
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:
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:
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:
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:
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:
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:
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:
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:
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:
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:
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:
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:
To create a client, use the createclient command in port-profile mode.
createclientclient-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.
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:
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.
Examples
This example shows how to create a dynamic vNIC connection:
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.
Examples
This example shows how to create a dynamic VNIC connection policy:
To create a organization reference, use the
createorg-ref command.
createorg-refnameorgdndomain-name
Syntax Description
name
Organization name. The range of valid values is 1 to 16.
orgdn
Specifies the organization domain name.
domain-name
Domain name.
Command Default
None
Command Modes
Locale (/security/locale)
Command History
Release
Modification
1.0(1)
This command was introduced.
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:
To create a pin group, use the
createpin-group command.
createpin-groupname
Syntax Description
name
Pin group name. The range of valid values is 1 to 16.
Command Default
None
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.
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:
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.
create port-profile creates the specified port profile and enters system VM management VMware profile set port profile mode.
To create a server automatice configuration policy, use the
createserver-autoconfig-policy command.
createserver-autoconfig-policyname
Syntax Description
name
Policy 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
The
server-autoconfig-policy command is definable only in org /.
Use this command to create a server automatic configuration policy
with the specified policy name, and enters organization server automatic
configuration policy mode.
Examples
This example shows how to create a server autoconfiguration policy:
This command creates the specified threshold value for the class property and enters organization statistics threshold policy class property threshold value mode. You must have a class and a property created in order to execute the setthreshold-value command. The command is used to set the value of the property you created.
You can configure multiple threshold values for a class property. Before you use this command, use the set normal-value command to set a baseline.
Examples
The following example
shows how to set the threshold value for the bytes-rx-delta property in vnic-stats class:
To create a trustpoint, use the
createtrustpoint command.
createtrustpointname
Syntax Description
name
Trustpoint 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 identify the trustpoints that will be used to
validate a certificate during Internet Key Exchange (IKE) authentication, and
enter organization trustpoint mode.
To create a vCon policy (vNIC/vHBA placement profile), use the createvcon-policy command.
createvcon-policypolicy-name
Syntax Description
policy-name
The name of the policy.
Command Default
None
Command Modes
Organization (/org)
Command History
Release
Modification
1.1(1)
This command was introduced.
Usage Guidelines
Creates the specified vCon policy and enters organization vcon-policy mode. vCon policies determine the placement and distribution of vNICs and vHBAs between the adapters for a server that has more than one adapter.
policy-name should be a unique set of numbers or letters that identifies the policy. The range of valid values is 1 to 16.
To create a vHBA template, use the
createvhba-templ command.
createvhba-templname
{
fabric
{
a | b
}
|
fc-iffci-name
}
*
Syntax Description
name
vHBA template name. The range of valid values is 1 to 16.
fabric
Specifies fabric.
a
Specifies fabric A.
b
Specifies fabric B.
fc-if
Specifies a Fibre Channel interface.
fci-name
Fibre Channel interface 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 vHBA is a virtualized host bus adapter that is configured on a
physical network adapter and appears to be a physical HBA to the operating
system of the server. The type of adapter in the system determines how many
vHBAs you can create.
Use this command to create a vHBA template, and enter organization
virtual HBA template mode.