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.
Cisco UCS Central supports global equipment policies defining the global power allocation policy (based on policy driven chassis group cap or manual blade level cap methods), power policy (based on grid, n+1 or non-redundant methods). Registered Cisco UCS domains choosing to define power management and power supply units globally within that client's policy resolution control will defer power management and power supply units to its registration with Cisco UCS Central.
The following example shows how to create an equipment power policy:
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group dg1 UCSC(policy-mgr) /domain-group # create psu-policy UCSC(policy-mgr) /domain-group* # commit-buffer UCSC(policy-mgr) /domain-group #
The following example shows how to delete an equipment power policy:
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group dg1 UCSC(policy-mgr) /domain-group # delete psu-policy UCSC(policy-mgr) /domain-group* # commit-buffer UCSC(policy-mgr) /domain-group #
Before configuring a power equipment policy under a domain group, this policy must first be created. Policies under the Domain Groups root were already created by the system and ready to configure.
The following example scopes the domain group dg1 and configures the equipment power policy for that domain group:
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group dg1 UCSC(policy-mgr) /domain-group/psu-policy # set descr "Power policy for sector 24" UCSC(policy-mgr) /domain-group/psu-policy* # set redundancy grid UCSC(policy-mgr) /domain-group/psu-policy* # commit-buffer UCSC(policy-mgr) /domain-group/psu-policy #
The following example shows how to create an equipment power policy:
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group dg1 UCSC(policy-mgr) /domain-group # scope psu-policy UCSC(policy-mgr) /domain-group/psu-policy # show PSU Policy: Domain Group Redundancy Description ------------ ---------- ----------- root/dg1 NPlus1 UCSC(policy-mgr) /domain-group #
The following example shows how to create a global power allocation policy for a domain group:
UCSC# connect policy-mgr UCSC(policy-mgr)# scope domain-group dg1 UCSC(policy-mgr) /domain-group # create cap-policy UCSC(policy-mgr) /domain-group/cap-policy* # commit-buffer UCSC(policy-mgr) /domain-group/cap-policy #
The following example shows how to delete a global power allocation policy for a domain group:
UCSC# connect policy-mgr UCSC(policy-mgr)# scope domain-group dg1 UCSC(policy-mgr) /domain-group # delete cap-policy UCSC(policy-mgr) /domain-group/cap-policy* # commit-buffer UCSC(policy-mgr) /domain-group/cap-policy #
The following example shows how to configure a global power allocation policy for a chassis group:
UCSC# connect policy-mgr UCSC(policy-mgr) /domain-group # scope domain-group dg1 UCSC(policy-mgr) /domain-group # scope cap-policy UCSC(policy-mgr) /domain-group/cap-policy # set cap-policy policy-driven-chassis-group-cap UCSC(policy-mgr) /domain-group/cap-policy* # commit-buffer UCSC(policy-mgr) /domain-group/cap-policy #
The following example shows how to configure manual power allocation policy for a blade server:
UCSC# connect policy-mgr UCSC(policy-mgr) /domain-group # scope domain-group dg1 UCSC(policy-mgr) /domain-group # scope cap-policy UCSC(policy-mgr) /domain-group/cap-policy # set cap-policy manual-blade-level-cap UCSC(policy-mgr) /domain-group/cap-policy* # commit-buffer UCSC(policy-mgr) /domain-group/cap-policy #
Cisco UCS Central supports global DNS policies defining the DNS server and domain name. Registered Cisco UCS domains choosing to define DNS management globally within that domain's policy resolution control will defer DNS management to its registration with Cisco UCS Central.
Before configuring a DNS policy in a domain group under the Domain Group root, this policy must first be created. Policies under the Domain Groups root were already created by the system and ready to configure.
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # create dns-config UCSC(policy-mgr) /domain-group/domain-group* # set domain-name dnsdomain UCSC(policy-mgr) /domain-group/domain-group* # commit-buffer UCSC(policy-mgr) /domain-group/domain-group #
The following example shows how to scope into the domain group domaingroup01, delete the DNS policy for that domain group, and commit the transaction:
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group/domain-group # delete dns-config UCSC(policy-mgr) /domain-group/domain-group* # commit-buffer UCSC(policy-mgr) /domain-group/domain-group #
Configure a DNS policy.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. |
Step 3 | UCSC(policy-mgr) /domain-group # scope dns-config |
Enter an existing DNS policy's configuration mode from the Domain Group root or a domain group scoped into. |
Step 4 | UCSC(policy-mgr) /domain-group/dns-config # create dns server-IP-address |
Creates a DNS server instance. |
Step 5 | UCSC(policy-mgr) /domain-group/dns-config* # commit-buffer |
Commits the transaction to the system configuration. |
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group / UCSC(policy-mgr) /domain-group # scope dns-config UCSC(policy-mgr) /domain-group/domain-group # create dns 0.0.0.0 UCSC(policy-mgr) /domain-group/domain-group* # commit-buffer UCSC(policy-mgr) /domain-group/domain-group #
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # scope dns-config UCSC(policy-mgr) /domain-group/domain-group # create dns 0.0.0.0 UCSC(policy-mgr) /domain-group/domain-group* # commit-buffer UCSC(policy-mgr) /domain-group/domain-group #
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. |
Step 3 | UCSC(policy-mgr) /domain-group # scope dns-config |
Enter an existing DNS policy's configuration mode from the Domain Group root or a domain group scoped into. |
Step 4 | UCSC(policy-mgr) /domain-group/dns-config # delete dns server-IP-address |
Deletes a DNS server instance. |
Step 5 | UCSC(policy-mgr) /domain-group/dns-config* # commit-buffer |
Commits the transaction to the system configuration. |
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group / UCSC(policy-mgr) /domain-group # scope dns-config UCSC(policy-mgr) /domain-group/domain-group # delete dns 0.0.0.0 UCSC(policy-mgr) /domain-group/domain-group* # commit-buffer UCSC(policy-mgr) /domain-group/domain-group #
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # scope dns-config UCSC(policy-mgr) /domain-group/domain-group # delete dns 0.0.0.0 UCSC(policy-mgr) /domain-group/domain-group* # commit-buffer UCSC(policy-mgr) /domain-group/domain-group #
Cisco UCS Central supports global date and time policies based on international time zones and defined NTP server. Registered Cisco UCS Manager clients choosing to define date and time globally within that client's policy resolution control will defer the configuration for date and time to its registration with Cisco UCS Central.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. |
Step 3 | UCSC(policy-mgr) /domain-group # create domain-group domain-group | (Optional)
This step is only necessary to create a new domain group under the Domain Group root (or creates a domain group under the domain group scoped into). |
Step 4 | UCSC(policy-mgr) /domain-group* # commit-buffer | (Optional)
This step is only necessary after creating a new domain group under the Domain Group root (or creating a domain group under the domain group scoped into). Commits the new domain group to the system configuration. |
Step 5 | UCSC(policy-mgr) /domain-group # create timezone-ntp-config | (Optional)
This step is only necessary the first time a date and time policy is configured for the newly created domain group under the Domain Group root that was created in the previous step, then enter the time zone NTP configuration mode. A date and time policy was created by the system for the Domain Group root, and is ready to be configured. |
Step 6 | UCSC(policy-mgr) /domain-group* # scope timezone-ntp-config | (Optional)
This step is only necessary if entering an existing date and time policy's time zone NTP configuration mode from the Domain Group root or a domain group scoped into. Skip this step if creating a date and time policy. |
Step 7 | UCSC(policy-mgr) /domain-group/timezone-ntp-config* # set timezone |
To set the time zone, press Enter after typing the set timezone command and enter the key value at the prompt. Configures the NTP server time zone. The attribute options are as follows: |
Step 8 | UCSC(policy-mgr) /domain-group/timezone-ntp-config* # commit-buffer |
Commits the transaction to the system configuration. |
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group / UCSC(policy-mgr) /domain-group # scope timezone-ntp-config UCSC(policy-mgr) /domain-group/timezone-ntp-config # set timezone Please identify a location so that time zone rules can be set correctly. Please select a continent or ocean. 1) Africa 4) Arctic Ocean 7) Australia 10) Pacific Ocean 2) Americas 5) Asia 8) Europe 3) Antarctica 6) Atlantic Ocean 9) Indian Ocean #? 9 Please select a country. 1) British Indian Ocean Territory 7) Maldives 2) Christmas Island 8) Mauritius 3) Cocos (Keeling) Islands 9) Mayotte 4) Comoros 10) Reunion 5) French Southern & Antarctic Lands 11) Seychelles 6) Madagascar #? 7 The following information has been given: Maldives Therefore timezone 'Indian/Maldives' will be set. Local time is now: Thu Oct 25 01:58:03 MVT 2012. Universal Time is now: Wed Oct 24 20:58:03 UTC 2012. Is the above information OK? 1) Yes 2) No #? 1 UCSC(policy-mgr) /domain-group/timezone-ntp-config* # commit-buffer UCSC(policy-mgr) /domain-group/timezone-ntp-config #
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group / UCSC(policy-mgr) /domain-group # create domain-group domaingroup01 UCSC(policy-mgr) /domain-group* # commit-buffer UCSC(policy-mgr) /domain-group # create timezone-ntp-config UCSC(policy-mgr) /domain-group/timezone-ntp-config # set timezone Please identify a location so that time zone rules can be set correctly. Please select a continent or ocean. 1) Africa 4) Arctic Ocean 7) Australia 10) Pacific Ocean 2) Americas 5) Asia 8) Europe 3) Antarctica 6) Atlantic Ocean 9) Indian Ocean #? 9 Please select a country. 1) British Indian Ocean Territory 7) Maldives 2) Christmas Island 8) Mauritius 3) Cocos (Keeling) Islands 9) Mayotte 4) Comoros 10) Reunion 5) French Southern & Antarctic Lands 11) Seychelles 6) Madagascar #? 7 The following information has been given: Maldives Therefore timezone 'Indian/Maldives' will be set. Local time is now: Thu Oct 25 01:58:03 MVT 2012. Universal Time is now: Wed Oct 24 20:58:03 UTC 2012. Is the above information OK? 1) Yes 2) No #? 1 UCSC(policy-mgr) /domain-group/timezone-ntp-config* # commit-buffer UCSC(policy-mgr) /domain-group/timezone-ntp-config #
UCSC # connect policy-mgr UCSC(policy-mgr) /domain-group # scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # create timezone-ntp-config UCSC(policy-mgr) /domain-group/timezone-ntp-config* # set timezone Please identify a location so that time zone rules can be set correctly. Please select a continent or ocean. 1) Africa 4) Arctic Ocean 7) Australia 10) Pacific Ocean 2) Americas 5) Asia 8) Europe 3) Antarctica 6) Atlantic Ocean 9) Indian Ocean #? 9 Please select a country. 1) British Indian Ocean Territory 7) Maldives 2) Christmas Island 8) Mauritius 3) Cocos (Keeling) Islands 9) Mayotte 4) Comoros 10) Reunion 5) French Southern & Antarctic Lands 11) Seychelles 6) Madagascar #? 7 The following information has been given: Maldives Therefore timezone 'Indian/Maldives' will be set. Local time is now: Thu Oct 25 01:58:03 MVT 2012. Universal Time is now: Wed Oct 24 20:58:03 UTC 2012. Is the above information OK? 1) Yes 2) No #? 1 UCSC(policy-mgr) /domain-group/timezone-ntp-config* # commit-buffer UCSC(policy-mgr) /domain-group/timezone-ntp-config #
Configure an NTP server for a date and time policy.
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. | ||
Step 2 | UCSC(policy-mgr)# scope domain-group domain-group |
Enters a domain group under the domain group root.
| ||
Step 3 | UCSC(policy-mgr) /domain-group # delete timezone-ntp-config |
Deletes the domain group's time zone policy. | ||
Step 4 | UCSC(policy-mgr) /domain-group* # commit-buffer |
Commits the transaction to the system configuration. |
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # delete timezone-ntp-config UCSC(policy-mgr) /domain-group* # commit-buffer UCSC(policy-mgr) /domain-group #
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group / UCSC(policy-mgr) /domain-group # delete timezone-ntp-config UCSC(policy-mgr) /domain-group* # commit-buffer Error: Update failed: [Timezone and NTP configuration under domain group root cannot be deleted] UCSC(policy-mgr) /domain-group* # exit UCSC(policy-mgr)* # exit UCSC# connect policy-mgr Cisco UCS Central UCSC(policy-mgr)#
Note | In the event you mistakenly scope to the domain group root, and enter the command delete timezone-ntp-config, the buffer will encounter an unrecoverable error, remaining in an uncommitted state and preventing subsequent commit-buffer commands from saving to the buffer. You must immediately exit and reconnect to the Policy Manager to clear the buffer. |
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. |
Step 3 | UCSC(policy-mgr) /domain-group # scope timezone-ntp-config |
Enters time zone NTP configuration mode. |
Step 4 | UCSC(policy-mgr) /domain-group/timezone-ntp-config # create ntp server-name |
Creates an NTP server instance. |
Step 5 | UCSC(policy-mgr) /domain-group/timezone-ntp-config* # commit-buffer |
Commits the transaction to the system configuration. |
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group / UCSC(policy-mgr) /domain-group # scope timezone-ntp-config UCSC(policy-mgr) /domain-group/timezone-ntp-config # create ntp domaingroupNTP01 UCSC(policy-mgr) /domain-group/timezone-ntp-config* # commit-buffer UCSC(policy-mgr) /domain-group/timezone-ntp-config #
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # scope timezone-ntp-config UCSC(policy-mgr) /domain-group/timezone-ntp-config # create ntp domaingroupNTP01 UCSC(policy-mgr) /domain-group/timezone-ntp-config* # commit-buffer UCSC(policy-mgr) /domain-group/timezone-ntp-config #
Configure a date and time policy.
The properties of an NTP server consist of its name. Changing those properties, unlike steps in the GUI involving configuring the NTP server's properties, requires deleting that NTP server and recreating it with a new name.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. |
Step 3 | UCSC(policy-mgr) /domain-group # scope timezone-ntp-config |
Enters time zone NTP configuration mode. |
Step 4 | UCSC(policy-mgr) /domain-group/timezone-ntp-config # delete ntp server-name |
Deletes an NTP server instance that requires renaming. |
Step 5 | UCSC(policy-mgr) /domain-group/timezone-ntp-config* # create ntp server-name |
Creates an NTP server instance to replace the deleted NTP server instance. |
Step 6 | UCSC(policy-mgr) /domain-group/timezone-ntp-config* # commit-buffer |
Commits the transaction to the system configuration. |
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group / UCSC(policy-mgr) /domain-group # scope timezone-ntp-config UCSC(policy-mgr) /domain-group/timezone-ntp-config # delete ntp domaingroupNTP01 UCSC(policy-mgr) /domain-group/timezone-ntp-config* # create ntp domaingroupNTP02 UCSC(policy-mgr) /domain-group/timezone-ntp-config* # commit-buffer UCSC(policy-mgr) /domain-group/timezone-ntp-config #
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. |
Step 3 | UCSC(policy-mgr) /domain-group # scope timezone-ntp-config |
Enters time zone NTP configuration mode. |
Step 4 | UCSC(policy-mgr) /domain-group/timezone-ntp-config # delete ntp server-name |
Deletes an NTP server instance. |
Step 5 | UCSC(policy-mgr) /domain-group/timezone-ntp-config* # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to delete the NTP server instance domaingroupNTP01:
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group / UCSC(policy-mgr) /domain-group # scope timezone-ntp-config UCSC(policy-mgr) /domain-group/timezone-ntp-config # delete ntp domaingroupNTP01 UCSC(policy-mgr) /domain-group/timezone-ntp-config* # commit-buffer UCSC(policy-mgr) /domain-group/timezone-ntp-config #
The following example shows how to delete the NTP server instance domaingroupNTP01:
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # scope timezone-ntp-config UCSC(policy-mgr) /domain-group/timezone-ntp-config # delete ntp domaingroupNTP01 UCSC(policy-mgr) /domain-group/timezone-ntp-config* # commit-buffer UCSC(policy-mgr) /domain-group/timezone-ntp-config #
A maintenance policy determines how Cisco UCS Central reacts when a change that requires a server reboot is made to a service profile associated with a server or to an updating service profile bound to one or more service profiles.
The maintenance policy specifies how Cisco UCS Central deploys the service profile changes. The deployment can occur in one of the following ways:
Immediately
When acknowledged by a user with admin privileges
Automatically at the time specified in a schedule
If the maintenance policy is configured to deploy the change during a scheduled maintenance window, the policy must include a valid schedule. The schedule deploys the changes in the first available maintenance window.
Note | A maintenance policy only prevents an immediate server reboot when a configuration change is made to an associated service profile. However, a maintenance policy does not prevent the following actions from taking place right away:
|
If you plan to configure this maintenance policy for deferred deployment, create a schedule.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. |
Step 3 | UCSC(policy-mgr) /domain-group # create maint-policy policy-name |
Creates the specified maintenance policy and enters maintenance policy mode. |
Step 4 | UCSC(policy-mgr) /domain-group/maint-policy # set reboot-policy {immediate | timer-automatic | user-ack} |
|
Step 5 | UCSC(policy-mgr) /domain-group/maint-policy # enable on-next-boot | (Optional)
Choose whether to apply the changes on the next reboot, and ignore the selection in the reboot-policy. |
Step 6 | UCSC(policy-mgr) /domain-group/maint-policy # disable on-next-boot | (Optional)
Disables the on-next-boot option. |
Step 7 | UCSC(policy-mgr) /domain-group/maint-policy # set scheduler scheduler-name | (Optional)
If the reboot-policy property is set to timer-automatic, you must select the schedule that specifies when maintenance operations can be applied to the server. Cisco UCS reboots the server and completes the service profile changes at the scheduled time. |
Step 8 | UCSC(policy-mgr) /domain-group/maint-policy # set scheduler scheduler-name | (Optional)
If the reboot-policy property is set to timer-automatic, you must select the schedule that specifies when maintenance operations can be applied to the server. Cisco UCS reboots the server and completes the service profile changes at the scheduled time. |
Step 9 | UCSC(policy-mgr) /domain-group/maint-policy # commit-buffer |
Commits the transaction to the system configuration. |
Scope into the Domain group root
Create a maintenance policy called MaintPol1
Set the system to reboot immediately when a service profile is associated with a server
Commit the transaction
UCSC# connect policy-mgr UCSC(Policy-mgr)# scope domain-group UCSC(policy-mgr) /domain-group# create maint-policy MaintPol1 UCSC(policy-mgr) /domain-group/maint-policy* # set reboot-policy immediate UCSC(policy-mgr) /domain-group/maint-policy* # commit-buffer UCSC(policy-mgr) /domain-group/maint-policy #
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name. |
Step 3 | UCSC(policy-mgr) /org # delete maint-policy policy-name |
Deletes the specified maintenance policy. |
Step 4 | UCSC(policy-mgr) /org # |
Commits the transaction to the system configuration. |
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCSC(policy-mgr)/org # delete maint-policy maintenance UCSC(policy-mgr)/org* # commit-buffer UCSC(policy-mgr)/org #
Cisco UCS Central supports a global system event log (SEL) policy.
The system event log (SEL) records most server-related events, such as over and under voltage, temperature events, fan events, and events from BIOS. The SEL is mainly used for troubleshooting purposes. The SEL file is approximately 40KB in size, and no further events can be recorded when it is full. It must be cleared before additional events can be recorded. You can use the SEL policy to backup the SEL to a remote server, and optionally clear the SEL after a backup operation occurs. Backup operations can be triggered based on specific actions, or they can occur at regular intervals. You can also manually backup or clear the SEL.
The system event log (SEL) resides on the CIMC in NVRAM. It records most server-related events, such as over and under voltage, temperature events, fan events, and events from BIOS. The SEL is mainly used for troubleshooting purposes.
The SEL file is approximately 40KB in size, and no further events can be recorded when it is full. It must be cleared before additional events can be recorded.
You can use the SEL policy to backup the SEL to a remote server, and optionally clear the SEL after a backup operation occurs. Backup operations can be triggered based on specific actions, or they can occur at regular intervals. You can also manually backup or clear the SEL.
The backup file is automatically generated. The filename format is sel-SystemName-ChassisID-ServerID-ServerSerialNumber-Timestamp; for example, sel-UCS-A-ch01-serv01-QCI12522939-20091121160736.
Tip | For more information about the SEL, including how to view the SEL for each server and configure the SEL policy, see the Cisco UCS Manager configuration guides, which are accessible through the Cisco UCS B-Series Servers Documentation Roadmap. |
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. | ||
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. | ||
Step 3 | UCSC(policy-mgr) /domain-group # scope ep-log-policy sel |
Enters organization endpoint log policy mode and scopes the SEL policy. | ||
Step 4 | UCSC(policy-mgr) /domain-group/ep-log-policy # set description description | (Optional)
Provides a description for the policy.
| ||
Step 5 | UCSC(policy-mgr) /domain-group/ep-log-policy # set backup action [log-full] [on-change-of-association] [on-clear] [timer] [none] |
Specifies an action or actions that will trigger a backup operation. | ||
Step 6 | UCSC(policy-mgr) /domain-group/ep-log-policy # set backup clear-on-backup {no | yes} |
Specifies whether to clear the system event log after a backup operation occurs. | ||
Step 7 | UCSC(policy-mgr) /domain-group/ep-log-policy # set backup destination URL |
Specifies the protocol, user, password, remote hostname, and remote path for the backup operation. Depending on the protocol used, specify the URL using one of the following syntax:
| ||
Step 8 | UCSC(policy-mgr) /domain-group/ep-log-policy # set backup format {ascii | binary} |
Specifies the format for the backup file. | ||
Step 9 | UCSC(policy-mgr) /domain-group/ep-log-policy # set backup hostname {hostname | ip-addr} |
Specifies the hostname or IP address of the remote server. | ||
Step 10 | UCSC(policy-mgr) /domain-group/ep-log-policy # set backup interval {1-hour | 2-hours | 4-hours | 8-hours | 24-hours | never} |
Specifies the time interval for the automatic backup operation. Specifying the never keyword means that automatic backups will not be made. | ||
Step 11 | UCSC(policy-mgr) /domain-group/ep-log-policy # set backup password password |
Specifies the password for the username. This step does not apply if the TFTP protocol is used. | ||
Step 12 | UCSC(policy-mgr) /domain-group/ep-log-policy # set backup protocol {ftp | scp | sftp | tftp} |
Specifies the protocol to use when communicating with the remote server. | ||
Step 13 | UCSC(policy-mgr) /domain-group/ep-log-policy # set backup remote-path path |
Specifies the path on the remote server where the backup file is to be saved. | ||
Step 14 | UCSC(policy-mgr) /domain-group/ep-log-policy # set backup user username |
Specifies the username the system should use to log in to the remote server. This step does not apply if the TFTP protocol is used. | ||
Step 15 | UCSC(policy-mgr) /domain-group/ep-log-policy # commit-buffer |
Commits the transaction. |
UCSC# connect policy-mgr UCSC(policy-mgr)# scope domain-group UCSC(policy-mgr) /domain-group #scope ep-log-policy sel UCSC(policy-mgr) /domain-group/ep-log-policy # set backup destination scp://user@192.168.1.10/logs Password: UCSC(policy-mgr) /domain-group/ep-log-policy* # set backup action log-full UCSC(policy-mgr) /domain-group/ep-log-policy* # set backup clear-on-backup yes UCSC(policy-mgr) /domain-group/ep-log-policy* # set backup format ascii UCSC(policy-mgr) /domain-group/ep-log-policy* # set backup interval 24-hours UCSC(policy-mgr) /domain-group/ep-log-policy* # commit-buffer UCSC(policy-mgr) /domain-group/ep-log-policy #
Before configuring a TFTP core export debug policy under a domain group, this policy must first be created. Policies under the Domain Groups root were already created by the system and ready to configure.
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. | ||
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. | ||
Step 3 | UCSC(policy-mgr) /domain-group # create tftp-core-export-config | (Optional)
Creates a TFTP Core Export Debug policy if it does not exist, then scopes into the policy. | ||
Step 4 | UCSC(policy-mgr) /domain-group # scope tftp-core-export-config | (Optional)
Scopes an existing TFTP Core Export Debug policy's configuration mode. | ||
Step 5 | UCSC(policy-mgr) /domain-group/tftp-core-export-config* # enable core-export-target |
Enables the TFTP core export target. | ||
Step 6 | UCSC(policy-mgr) /domain-group/tftp-core-export-config* # set core-export-target path name-of-path |
Sets the TFTP core export policy target path. | ||
Step 7 | UCSC(policy-mgr) /domain-group/tftp-core-export-config* # set core-export-target port port-number |
Sets the TFTP core export policy port number (1-65535). | ||
Step 8 | UCSC(policy-mgr) /domain-group/tftp-core-export-config* # set core-export-target server-description port-number |
Sets the TFTP core export target policy server description.
| ||
Step 9 | UCSC(policy-mgr) /domain-group/tftp-core-export-config* # set core-export-target server-name server-name |
Sets the TFTP core export target policy server name. | ||
Step 10 | UCSC(policy-mgr) /domain-group/tftp-core-export-config* # commit-buffer |
Commits the transaction to the system configuration. |
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # create tftp-core-export-config UCSC(policy-mgr) /domain-group/tftp-core-export-config* # enable core-export-target UCSC(policy-mgr) /domain-group/tftp-core-export-config* # set core-export-target path /target UCSC(policy-mgr) /domain-group/tftp-core-export-config* # set core-export-target port 65535 UCSC(policy-mgr) /domain-group/tftp-core-export-config* # set core-export-target server-description "TFTP core export server 2" UCSC(policy-mgr) /domain-group/tftp-core-export-config* # set core-export-target server-name TFTPcoreserver01 UCSC(policy-mgr) /domain-group/tftp-core-export-config* # commit-buffer UCSC(policy-mgr) /domain-group/tftp-core-export-config #
Cisco UCS uses the Core File Exporter to export core files as soon as they occur to a specified location on the network through TFTP. This functionality allows you to export the tar file with the contents of the core file. The Core File Exporter provides system monitoring and automatic export of core files to be included in TAC cases.
A TFTP core export debug policy is deleted from a domain group under the domain group root. TFTP core export debug policies under the domain groups root cannot be deleted.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. |
Step 3 | UCSC(policy-mgr) /domain-group # delete tftp-core-export-config |
Deletes the TFTP Core Export Debug policy. |
Step 4 | UCSC(policy-mgr) /domain-group/tftp-core-export-config* # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to delete the TFTP core export debug policy:
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # delete tftp-core-export-config UCSC(policy-mgr) /domain-group* # commit-buffer UCSC(policy-mgr) /domain-group #
Before configuring a syslog debug policy under a domain group, this policy must first be created.
Syslog Debug Policies under the Domain Group root were created by the system.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr)# scope domain-group domain-group |
Enters a domain group under the Domain Group root. |
Step 3 | UCSC(policy-mgr) /domain-group # create syslog |
Creates a Syslog Debug policy if it does not exist, then scopes into the policy. |
Step 4 | UCSC(policy-mgr) /domain-group/syslog* # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to create the Syslog Console debug policy:
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # create syslog UCSC(policy-mgr) /domain-group/syslog/remote-destination* # commit-buffer UCSC(policy-mgr) /domain-group/syslog/remote-destination #
The Syslog Debug Policy is now ready to be configured.
A syslog debug policy is deleted from a domain group under the domain group root. Syslog debug policies under the domain groups root cannot be deleted.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. |
Step 3 | UCSC(policy-mgr) /domain-group # delete syslog |
Deletes the Syslog Debug policy. |
Step 4 | UCSC(policy-mgr) /domain-group* # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to delete the Syslog debug policy:
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # delete syslog UCSC(policy-mgr) /domain-group* # commit-buffer UCSC(policy-mgr) /domain-group #
Before configuring a syslog console debug policy under a domain group, this policy must first be created. Policies under the Domain Groups root that were already created by the system are ready to configure.
Create a Syslog Debug Policy.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. |
Step 3 | UCSC(policy-mgr) /domain-group # scope syslog |
Creates or scopes a Syslog Debug policy's configuration mode. |
Step 4 | UCSC(policy-mgr) /domain-group/syslog* # create | scope console |
Creates or scopes the Syslog Console Debug policy. |
Step 5 | UCSC(policy-mgr) /domain-group/syslog/console* # enable |
Enables the Syslog Console Debug policy. |
Step 6 | UCSC(policy-mgr) /domain-group/syslog/console* # set level 1 | 2 | 0 |
Sets the syslog console to one of the following conditions: Alerts (1), Critical (2), or Emergencies (0). |
Step 7 | UCSC(policy-mgr) /domain-group/syslog/console* # exit |
Moves back a level for the next create or scope command. |
Step 8 | UCSC(policy-mgr) /domain-group/syslog/console* # commit-buffer |
Commits the transaction to the system configuration. |
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # scope syslog UCSC(policy-mgr) /domain-group/syslog # scope console UCSC(policy-mgr) /domain-group/syslog/console # enable UCSC(policy-mgr) /domain-group/syslog/console* # set level 2 UCSC(policy-mgr) /domain-group/syslog/console* # commit-buffer UCSC(policy-mgr) /domain-group/syslog/console #
Disable a syslog console debug policy from a sub-domain group. You cannot disable syslog console debug policies under the Domain Group root.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. |
Step 3 | UCSC(policy-mgr) /domain-group # scope syslog |
Scopes an existing Syslog Console Debug policy's configuration mode. |
Step 4 | UCSC(policy-mgr) /domain-group/syslog* # scope console |
Scopes the Syslog Console Debug policy. |
Step 5 | UCSC(policy-mgr) /domain-group/syslog/console* # disable |
Disables the Syslog Console Debug policy. |
Step 6 | UCSC(policy-mgr) /domain-group/syslog/console* # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to disable the Syslog Console debug policy:
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # scope syslog UCSC(policy-mgr) /domain-group/syslog* # scope console UCSC(policy-mgr) /domain-group/syslog/console* # disable UCSC(policy-mgr) /domain-group/syslog/console* # commit-buffer UCSC(policy-mgr) /domain-group/syslog/console #
Before configuring a syslog monitor debug policy under a domain group, this policy must first be created. Policies under the Domain Groups root that were already created by the system are ready to configure.
Create a Syslog Debug Policy.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. |
Step 3 | UCSC(policy-mgr) /domain-group # scope syslog |
Creates or scopes a Syslog Debug policy's configuration mode. |
Step 4 | UCSC(policy-mgr) /domain-group/syslog* # create | scope monitor |
Creates or scopes the Syslog Monitor Debug policy. |
Step 5 | UCSC(policy-mgr) /domain-group/syslog/monitor* # enable |
Enables the syslog monitor. |
Step 6 | UCSC(policy-mgr) /domain-group/syslog/monitor* # set level 1 | 2 | 3 | 4 | 5 | 6 | 7 |
Sets the syslog monitor to one of the following conditions: Alerts (1), Cisco UCS domains Critical (2), Cisco UCS domains Major Error (3), Cisco UCS domains Minor Warnings (4), Cisco UCS domains Warning (5), Information (6), Debugging (7). |
Step 7 | UCSC(policy-mgr) /domain-group/syslog/monitor* # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to configure the Syslog Monitor debug policy:
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # scope syslog UCSC(policy-mgr) /domain-group/syslog* # scope monitor UCSC(policy-mgr) /domain-group/syslog/monitor # enable UCSC(policy-mgr) /domain-group/syslog/monitor* # set level 3 UCSC(policy-mgr) /domain-group/syslog/monitor* # commit-buffer UCSC(policy-mgr) /domain-group/syslog/monitor #
Disable a syslog monitor debug policy from a domain group under the Domain Group root. You cannot disable a syslog monitor debug policies under the Domain Group root.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. |
Step 3 | UCSC(policy-mgr) /domain-group # scope syslog |
Scopes an existing Syslog Debug policy's configuration mode. |
Step 4 | UCSC(policy-mgr) /domain-group/syslog* # scope monitor |
Scopes the syslog Monitor Debug policy. |
Step 5 | UCSC(policy-mgr) /domain-group/syslog/monitor* # disable |
Disables the syslog monitor. |
Step 6 | UCSC(policy-mgr) /domain-group/syslog/monitor* # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to disable the policy:
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # scope syslog UCSC(policy-mgr) /domain-group/syslog* # scope monitor UCSC(policy-mgr) /domain-group/syslog/monitor* # disable UCSC(policy-mgr) /domain-group/syslog/monitor* # commit-buffer UCSC(policy-mgr) /domain-group/syslog/monitor #
Before configuring a syslog remote destination debug policy under a domain group, this policy must first be created. Policies under the Domain Groups root that were already created by the system are ready to configure.
Create a Syslog Debug Policy.
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. | ||
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. | ||
Step 3 | UCSC(policy-mgr) /domain-group # scope syslog |
Creates or scopes a Syslog Debug policy's configuration mode. | ||
Step 4 | UCSC(policy-mgr) /domain-group/syslog* # create | scope remote-destination | server-1 | server-2 | server-3 |
Creates or scopes the Syslog Remote Destination Debug policy to server-1, server-2, or server-3. | ||
Step 5 | UCSC(policy-mgr) /domain-group/syslog/remote-destination* # enable |
Enables the syslog remote destination. | ||
Step 6 | UCSC(policy-mgr) /domain-group/syslog/remote-destination* # set facility auth hostname or level | authpriv hostname or level | cron hostname or level | daemon hostname or level | ftp hostname or level | kernel hostname or level | local[0-7] hostname or level | lpr hostname or level | mail hostname or level | news hostname or level | syslog hostname or level | user hostname or level | uucp hostname or level |
Sets the syslog remote destination facility to the following hostname or level configuration:
| ||
Step 7 | UCSC(policy-mgr) /domain-group/syslog/remote-destination* # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to configure the Syslog Remote Destination Debug policy:
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # scope syslog UCSC(policy-mgr) /domain-group/syslog* # scope remote-destination server-3 UCSC(policy-mgr) /domain-group/syslog/remote-destination* # enable UCSC(policy-mgr) /domain-group/syslog/remote-destination* # set facility auth 4 UCSC(policy-mgr) /domain-group/syslog/remote-destination* # set facility auth hostname 02 UCSC(policy-mgr) /domain-group/syslog/remote-destination* # set facility authpriv 3 UCSC(policy-mgr) /domain-group/syslog/remote-destination* # set facility authpriv hostname 02 *** Continue configuring all facility settings as required *** UCSC(policy-mgr) /domain-group/syslog/remote-destination* # commit-buffer UCSC(policy-mgr) /domain-group/syslog/remote-destination #
A syslog remote destination debug policy is disabled in a domain group under the domain group root. Syslog remote destination debug policies under the domain groups root cannot be disabled.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. |
Step 3 | UCSC(policy-mgr) /domain-group # scope syslog |
Scopes an existing Syslog Debug policy's configuration mode. |
Step 4 | UCSC(policy-mgr) /domain-group/syslog* # scope remote-destination | server-1 | server-2 | server-3 |
Creates or scopes the Syslog Remote Destination Debug policy to server-1, server-2, or server-3. |
Step 5 | UCSC(policy-mgr) /domain-group/syslog/remote-destination* # disable |
Disables the syslog remote destination. |
The following example shows how to disable the Syslog Remote Destination debug policy:
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # scope syslog UCSC(policy-mgr) /domain-group/syslog* # scope remote-destination server-3 UCSC(policy-mgr) /domain-group/syslog/remote-destination* # disable UCSC(policy-mgr) /domain-group/syslog/remote-destination* # commit-buffer UCSC(policy-mgr) /domain-group/syslog/remote-destination #
Before configuring a syslog source debug policy under a domain group, this policy must first be created. Policies under the Domain Groups root that were already created by the system are ready to configure.
Create a Syslog Debug Policy.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. |
Step 3 | UCSC(policy-mgr) /domain-group # scope syslog |
Creates or scopes a Syslog Debug policy's configuration mode. |
Step 4 | UCSC(policy-mgr) /domain-group/syslog* # create | scope source |
Creates or scopes the Syslog Source Debug policy. |
Step 5 | UCSC(policy-mgr) /domain-group/syslog/source* # enable |
Enables the syslog source. |
Step 6 | UCSC(policy-mgr) /domain-group/syslog/remote-destination* # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to configure the Syslog Source Debug policy:
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # scope syslog UCSC(policy-mgr) /domain-group/syslog* # scope source UCSC(policy-mgr) /domain-group/syslog/source* # enable UCSC(policy-mgr) /domain-group/syslog/source* # commit-buffer UCSC(policy-mgr) /domain-group/syslog/source #
Delete a syslog source debug policy from a sub-domain group of domain group root. You cannot delete syslog source debug policies under the domain groups root.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. |
Step 3 | UCSC(policy-mgr) /domain-group/syslog* # scope source |
Scopes the Syslog Source Debug policy. |
Step 4 | UCSC(policy-mgr) /domain-group/syslog/source* # disable |
Disables the Syslog Source Debug policy. |
Step 5 | UCSC(policy-mgr) /domain-group/syslog/source* # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to disable the Syslog Source Debug policy
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # create syslog UCSC(policy-mgr) /domain-group/syslog* # scope source UCSC(policy-mgr) /domain-group/syslog/source* # disable UCSC(policy-mgr) /domain-group/syslog/source* # commit-buffer UCSC(policy-mgr) /domain-group/syslog/source #
Before configuring a syslog logfile debug policy under a domain group, this policy must first be created. Policies under the Domain Groups root that were already created by the system are ready to configure.
Create a Syslog Debug Policy.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. |
Step 3 | UCSC(policy-mgr) /domain-group # scope syslog |
Creates or scopes a Syslog Debug policy's configuration mode. |
Step 4 | UCSC(policy-mgr) /domain-group/syslog* # create | scope file |
Creates or scopes the Syslog Logfile Debug policy. |
Step 5 | UCSC(policy-mgr) /domain-group/syslog/file* # enable |
Enables the syslog logfile. |
Step 6 | UCSC(policy-mgr) /domain-group/syslog/file* # set level 1 | 2 | 3 | 4 | 5 | 6 | 7 |
Sets the syslog file to one of the following conditions: Alerts (1), Cisco UCS domains Critical (2), Cisco UCS domains Major Error (3), Cisco UCS domains Minor Warnings (4), Cisco UCS domains Warning (5), Information (6), Debugging (7). |
Step 7 | UCSC(policy-mgr) /domain-group/syslog/file* # set name syslog-file-name |
Sets the syslog file name. |
Step 8 | UCSC(policy-mgr) /domain-group/syslog/file* # set size syslog-file-size |
Sets the syslog file size (4096-4194304 bytes). |
Step 9 | UCSC(policy-mgr) /domain-group/syslog/file* # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to configure the Syslog Logfile debug policy:
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # scope syslog UCSC(policy-mgr) /domain-group/syslog* # scope file UCSC(policy-mgr) /domain-group/syslog/file* # enable UCSC(policy-mgr) /domain-group/syslog/file* # set level 4 UCSC(policy-mgr) /domain-group/syslog/file* # set name syslogfilename01 UCSC(policy-mgr) /domain-group/syslog/file* # set size 4194304 UCSC(policy-mgr) /domain-group/syslog/file* # commit-buffer UCSC(policy-mgr) /domain-group/syslog/file #
Disable a syslog logfile debug policy from a domain group under the domain group root. You cannot diable syslog logfile debug policies under the domain groups root.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope domain-group domain-group |
Enters domain group root mode and (optionally) enters a sub-domain group under the domain group root. To enter the domain group root mode, type / as the domain-group. |
Step 3 | UCSC(policy-mgr) /domain-group # scope syslog |
Creates or scopes a Syslog Debug policy's configuration mode. |
Step 4 | UCSC(policy-mgr) /domain-group/syslog* # scope file |
Scopes the Syslog Logfile Debug policy. |
Step 5 | UCSC(policy-mgr) /domain-group/syslog/file* # disable |
Disables or enables the syslog logfile. |
Step 6 | UCSC(policy-mgr) /domain-group/syslog/file* # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to disable the Syslog LogFile debug policy:
UCSC # connect policy-mgr UCSC(policy-mgr)# scope domain-group domaingroup01 UCSC(policy-mgr) /domain-group # scope syslog UCSC(policy-mgr) /domain-group/syslog* # scope file UCSC(policy-mgr) /domain-group/syslog/file* # disable UCSC(policy-mgr) /domain-group/syslog/file* # commit-buffer UCSC(policy-mgr) /domain-group/syslog/file #
Use a terminal emulator to access the CLI.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC # scope monitoring |
Enters monitoring mode. |
Step 2 | UCSC /monitoring # scope sysdebug |
Enters sysdebug mode. |
Step 3 | UCSC /monitoring/sysdebug # scope mgmt-logging |
Enters management logging mode. |
Step 4 | UCSC /monitoring/sysdebug/mgmt-logging # set module tomcat_config [crit | debug0 | debug1 | debug2 | debug3 | debug4 | info | major | minor | warn] |
Sets the logging level. |
Step 5 | UCSC /monitoring/sysdebug/mgmt-logging # commit-buffer | Commits the change. |
UCSC # scope monitoring UCSC /monitoring # scope sysdebug UCSC /monitoring/sysdebug # scope mgmt-logging UCSC /monitoring/sysdebug/mgmt-logging # set module tomcat_config debug4 UCSC /monitoring/sysdebug/mgmt-logging # commit-buffer
Cisco UCS Central provides high availability in a cluster setup when you deploy Cisco UCS Central in two virtual nodes. High availability provides stability and redundancy directly to your Cisco UCS Central and indirectly to your Cisco UCS Domains management. The high availability in Cisco UCS Central provides you the following:
Simplified large scale Cisco UCS deployments with an increased number of servers, chassis, fabric interconnects, and data centers.
UCS Central VM redundancy in a Hypervisor independent environment.
A shared storage device to house database and image repositories.
Built-in failure detection (DME, VM, host, or network failures) and automatic failover to ensure continuous operation.
You will deploy Cisco UCS Central in two VMs on separate hosts to enable high availability. High availability:
Requires at least one Cisco UCS Manager be registered with Cisco UCS Central for a cluster to support high availability
Uses the same subnet for individual VMs and VIP addresses
Allows you to configure a mirrored, multi-path shared storage disk on each VM that is accessible from both hosts
Uses UCS Manager to store quorum data and determine primary node.
Exchanges information such as heartbeat and election protocols in the same way as Cisco UCS Manager. This results in a simpler design, more code reusability, and easy to define failover conditions
The following are the guidelines to setup Cisco UCS Central in high availability:
Make sure both VMs in the cluster should never be on the same server. Otherwise, a single host failure would end up bringing down the cluster.
Each node in the cluster must have the following:
Separate network path for management and storage network.
Make sure the management network used communications between the two Cisco UCS Central nodes are not on the same network as the network that the nodes use to access the shared disk array. The primary heartbeat mechanism relies on exchanging datagrams across the management network. The secondary heartbeat mechanism uses quorum data on Cisco UCS Manager. When you use separate network paths for management and shared disk access, that provides redundant paths between the two nodes making it easier to distinguish node failures from link failures.
Note | High availability is supported only in IPv4 addressing without the DHCP. You must configure the node IPs and cluster VIPs statically during the installation. These IP addresses are allocated from the production network over which the Cisco UCS Central cluster communicates with Cisco UCS Manager. |
Both VMs must be configured on IP addresses that belongs to the same subnet.
For NFS, you should configure an NTP server on the NFS server to ensure that the time of both VMs is always synced to Cisco UCS Central.
Make sure the cluster node infrastructure does not have a single point of failure. You can connect the cluster nodes my multiple, distinct networks. You can also construct the network with redundant switches and routers or similar hardware that removes single points of failure.
For high availability Cisco UCS Central supports the most commonly used bus types, such as SAS , Fiber Channel (FC), and iSCSI. SCSI compatibility with Persistent Reservations (PRs) is recommended. LUN masking or zoning should be used to isolate the storage volumes accessed by the cluster from other hosts on the network.
Command or Action | Purpose |
---|
UCSC# show cluster state A: UP, PRIMARY B: UP, SUBORDINATE HA NOT READY No device connected to this VM.
Command or Action | Purpose |
---|
UCSC# show cluster extended-state Cluster Id: 0x2e95deacbd0f11e2-0x8ff35147e84f3de2 Start time: Thu May 16 06:54:22 2013 Last election time: Thu May 16 16:29:28 2013 A: UP, PRIMARY B: UP, SUBORDINATE A: memb state UP, lead state PRIMARY, mgmt services state: UP B: memb state UP, lead state SUBORDINATE, mgmt services state: UP heartbeat state PRIMARY_OK HA READY Detailed state of the device selected for HA quorum data: Device 1007, serial: a66b4c20-8692-11df-bd63-1b72ef3ac801, state: active Device 1010, serial: 00e3e6d0-8693-11df-9e10-0f4428357744, state: active Device 1012, serial: 1d8922c8-8693-11df-9133-89fa154e3fa1, state: active
Use this command to designate a cluster leader.
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | UCSC # connect local-mgmt |
Enters local management mode. | ||
Step 2 | UCSC(local-mgmt)# cluster lead {a | b} |
Change the cluster lead to the specified fabric interconnect.
|
The following example shows how to view the primary, change the cluster lead to fabric interconnect B, and verify the result:
UCSC-A# show cluster state Cluster Id: 0x1efd4e4ea47511e5-0x94961118a1af3b76 A: UP, PRIMARY B: UP, SUBORDINATE HA NOT READY No device connected to this VM UCSC-A# connect local-mgmt UCSC-A(local-mgmt)# cluster lead b Cluster Id:0x1efd4e4ea47511e5-0x94961118a1af3b76 UCSC-A(local-mgmt)#
After the VIP disconnects, log back in to verify the primary is now fabric interconnect B.
UCSC-B# show cluster state Cluster Id: 0x1efd4e4ea47511e5-0x94961118a1af3b76 B: UP, PRIMARY A: UP, SUBORDINATE HA NOT READY No device connected to this VM UCSC-B#
This command forces the secondary FI to be primary. This can be used when the primary FI has failed or remains in Election in Progress state.
Command or Action | Purpose |
---|
The following example shows how to use the cluster force primary command:
UCSC-A# connect local-mgmt UCSC-A(local-mgmt)# cluster force primary Cluster Id:0x1efd4e4ea47511e5-0x94961118a1af3b76 UCSC-A(local-mgmt)#
Command or Action | Purpose |
---|
UCSC# show network-interface ID OOB IP Addr OOB Gateway OOB Netmask ---- --------------- --------------- ----------- A 10.106.189.54 10.106.189.1 255.255.255.0 B 10.106.189.55 10.106.189.1 255.255.255.0
Command or Action | Purpose |
---|
ucsc# show network-interface detail VM IP interface: ID: A OOB IP Addr: 10.106.189.54 OOB Gateway: OOB Netmask: 255.255.255.0 Current Task: ID: B OOB IP Addr: 10.106.189.55 OOB Gateway: OOB Netmask: 255.255.255.0 Current Task:
Command or Action | Purpose |
---|
UCSC# show network-interfaceserver [ a | b] ID OOB IP Addr OOB Gateway OOB Netmask ---- --------------- --------------- ----------- A 10.106.189.54 10.106.189.1 255.255.255.0
Command or Action | Purpose |
---|
UCSC# show system Systems: Hostname Installation Type System IP Address ---------------- ------------------------ ---------------------------- central-vk2 Cluster 10.106.189.56 central-lun-A#
Command or Action | Purpose |
---|
UCSC# show system detail System: Hostname: central-lun Installation Type: Cluster System IP Address: Current Task: central-lun-A#