The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter includes the following sections:
You can use the following communication services to interface third-party applications with Cisco UCS:
Note |
Cisco recommends that you enable only the communication services that are required to interface with other network applications. |
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# scope system | Enters system mode. |
Step 2 | UCS-A /system # scope services | Enters system services mode. |
Step 3 | UCS-A /system/services # enable cimxml | Enables the CIM XLM service. |
Step 4 | UCS-A /system/services # set cimxml port port-num | Specifies the port to be used for the CIM XML connection. |
Step 5 | UCS-A /system/services # commit-buffer | Commits the transaction to the system configuration. |
The following example enables CIM XML, sets the port number to 5988, and commits the transaction:
UCS-A# scope system UCS-A /system # scope services UCS-A /system/services # enable cimxml UCS-A /system/services* # set cimxml port 5988 UCS-A /system/services* # commit-buffer UCS-A /system/services #
Note |
Cisco recommends that you enable only the communication services that are required to interface with other network applications. |
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# scope system | Enters system mode. |
Step 2 | UCS-A /system # scope services | Enters system services mode. |
Step 3 | UCS-A /system/services # enable http | Enables the HTTP service. |
Step 4 | UCS-A /system/services # set http port port-num | Specifies the port to be used for the HTTP connection. |
Step 5 | UCS-A /system/services # commit-buffer | Commits the transaction to the system configuration. |
The following example enables HTTP, sets the port number to 80, and commits the transaction:
UCS-A# scope system UCS-A /system # scope services UCS-A /system/services # enable http UCS-A /system/services* # set http port 80 UCS-A /system/services* # commit-buffer UCS-A /system/services #
Note |
Cisco recommends that you enable only the communication services that are required to interface with other network applications. |
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | UCS-A# scope system | Enters system mode. |
||
Step 2 | UCS-A /system # scope services | Enters system services mode. |
||
Step 3 | UCS-A /system/services # enable https | Enables the HTTPS service. |
||
Step 4 | UCS-A /system/services # set https port port-num | Specifies the port to be used for the HTTPS connection. |
||
Step 5 | UCS-A /system/services # set https keyring keyring-name | Specifies the name for the HTTPS keyring.
|
||
Step 6 | UCS-A /system/services # commit-buffer | Commits the transaction to the system configuration. |
The following example enables HTTPS, sets the port number to 443, sets the key ring name to kring7984, and commits the transaction:
UCS-A# scope system UCS-A /system # scope services UCS-A /system/services # enable https UCS-A /system/services* # set https port 443 UCS-A /system/services* # set https keyring kring7984 UCS-A /system/services* # commit-buffer UCS-A /system/services #
Configuring SNMP
Note |
Cisco recommends that you enable only the communication services that are required to interface with other network applications. |
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# scope monitoring | Enters monitoring mode. |
Step 2 | UCS-A /monitoring # enable snmp | Enables SNMP. |
Step 3 | UCS-A /monitoring # set snmp community community-name | Specifies SNMP community. The community name can be any alphanumeric string up to 32 characters. |
Step 4 | UCS-A /monitoring # commit-buffer | Commits the transaction to the system configuration. |
The following example enables SNMP, configures an SNMP community named SnmpCommSystem2, and commits the transaction:
UCS-A# scope monitoring UCS-A /monitoring # enable snmp UCS-A /monitoring* # set snmp community SnmpCommSystem2 UCS-A /monitoring* # commit-buffer UCS-A /monitoring #
Note |
Cisco recommends that you enable only the communication services that are required to interface with other network applications. |
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# scope monitoring | Enters monitoring mode. |
Step 2 | UCS-A /monitoring # enable snmp | Enables SNMP. |
Step 3 | UCS-A /monitoring # create snmp-user user-name | Creates the specified SNMPv3 user. |
Step 4 | UCS-A /monitoring/snmp-user # set aes-128 {no | yes} | Enables or disables the use of AES-128 encryption. |
Step 5 | UCS-A /monitoring/snmp-user # set auth {md5 | sha} | Specifies the use of MD5 or DHA authentication. |
Step 6 | UCS-A /monitoring/snmp-user # set password | Specifies the user password. After you enter the set password command, you are prompted to enter and confirm the password. |
Step 7 | UCS-A /monitoring/snmp-user # set priv-password | Specifies the user privacy password. After you enter the set priv-password command, you are prompted to enter and confirm the privacy password. |
Step 8 | UCS-A /monitoring/snmp-user # commit-buffer | Commits the transaction to the system configuration. |
The following example enables SNMP, creates an SNMPv3 user named snmp-user14, disables AES-128 encryption, specifies the use of MD5 authentication, sets the password and privacy password, and commits the transaction:
UCS-A# scope monitoring UCS-A /monitoring # enable snmp UCS-A /monitoring* # create snmp-user snmp-user14 UCS-A /monitoring/snmp-user* # set aes-128 no UCS-A /monitoring/snmp-user* # set auth md5 UCS-A /monitoring/snmp-user* # set password Enter a password: Confirm the password: UCS-A /monitoring/snmp-user* # set priv-password Enter a password: Confirm the password: UCS-A /monitoring/snmp-user* # commit-buffer UCS-A /monitoring/snmp-user #
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# scope monitoring | Enters monitoring mode. |
Step 2 | UCS-A /monitoring # delete snmp-user user-name | Deletes the specified SNMPv3 user. |
Step 3 | UCS-A /monitoring # commit-buffer | Commits the transaction to the system configuration. |
The following example deletes the SNMPv3 user named snmp-user14 and commits the transaction:
UCS-A# scope monitoring UCS-A /monitoring # delete snmp-user snmp-user14 UCS-A /monitoring* # commit-buffer UCS-A /monitoring #
Note |
Cisco recommends that you enable only the communication services that are required to interface with other network applications. |
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# scope monitoring | Enters monitoring mode. |
Step 2 | UCS-A /monitoring # enable snmp | Enables SNMP. |
Step 3 | UCS-A /monitoring # create snmp-trap trap-name | Creates the specified SNMP trap. |
Step 4 | UCS-A /monitoring/snmp-trap # set community community-name | Specifies the SNMP community name to be used for the SNMP trap. |
Step 5 | UCS-A /monitoring/snmp-trap # set port port-num | Specifies the port to be used for the SNMP trap. |
Step 6 | UCS-A /monitoring/snmp-trap # commit-buffer | Commits the transaction to the system configuration. |
The following example enables SNMP, creates an SNMP trap named sys-trap2, specifies that the trap will use the SnmpCommSystem2 community on port 2, and commits the transaction:
UCS-A# scope monitoring UCS-A /monitoring # enable snmp UCS-A /monitoring* # create snmp-trap sys-trap2 UCS-A /monitoring/snmp-trap* # set community SnmpCommSystem2 UCS-A /monitoring/snmp-trap* # set port 2 UCS-A /monitoring/snmp-trap* # commit-buffer UCS-A /monitoring/snmp-trap #
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# scope monitoring | Enters monitoring mode. |
Step 2 | UCS-A /monitoring # delete snmp-trap trap-name | Deletes the specified SNMP trap. |
Step 3 | UCS-A /monitoring # commit-buffer | Commits the transaction to the system configuration. |
The following example deletes the SNMP trap named sys-trap2 and commits the transaction:
UCS-A# scope monitoring UCS-A /monitoring # delete snmp-trap sys-trap2 UCS-A /monitoring* # commit-buffer UCS-A /monitoring #
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# scope monitoring | Enters monitoring mode. |
Step 2 | UCS-A /monitoring # disable snmp | Disables the SNMP service. |
Step 3 | UCS-A //monitoring # commit-buffer | Commits the transaction to the system configuration. |
The following example disables SNMP:
UCS-A# scope monitoring UCS-A /monitoring # disable snmp UCS-A /monitoring* # commit-buffer UCS-A /monitoring #
Note |
Cisco recommends that you enable only the communication services that are required to interface with other network applications. |
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# scope system | Enters system mode. |
Step 2 | UCS-A /system # scope services | Enters system services mode. |
Step 3 | UCS-A /services # enable telnet-server | Enables the Telnet service. |
Step 4 | UCS-A /services # commit-buffer | Commits the transaction to the system configuration. |
The following example enables Telnet and commits the transaction:
UCS-A# scope system UCS-A /system # scope services UCS-A /services # enable telnet-server UCS-A /services* # commit-buffer UCS-A /services #
Note |
Cisco recommends that you disable all communication services that are not required to interface with other network applications. |
The following example disables CIM XML and commits the transaction:
UCS-A# scope system UCS-A# scope services UCS-A /system/services # disable cimxml UCS-A /system/services* # commit-buffer UCS-A /system/services #