Contents

Registering Cisco UCS Domains with Cisco UCS Central

This chapter includes the following sections:

Registration of Cisco UCS Domains

You can have Cisco UCS Central manage some or all of the Cisco UCS domains in your data center.

If you want to have Cisco UCS Central manage a Cisco UCS domain, you need to register that domain. When you register, you need to choose which types of policies and other configurations, such as backups and firmware, will be managed by Cisco UCS Central and which by Cisco UCS Manager. You can have Cisco UCS Central manage the same types of policies and configurations for all registered Cisco UCS domains or you can choose to have different settings for each registered Cisco UCS domain.

Before you register a Cisco UCS domain with Cisco UCS Central, do the following:

  • Configure an NTP server and the correct time zone in both Cisco UCS Manager and Cisco UCS Central to ensure that they are in sync. If the time and date in the Cisco UCS domain and Cisco UCS Central are out of sync, the registration might fail.

  • Obtain the hostname or IP address of Cisco UCS Central

  • Obtain the shared secret that you configured when you deployed Cisco UCS Central


Note

You cannot change or swap the IP addresses used by Cisco UCS Manager in a domain that is registered with Cisco UCS Central. If you need to change or swap that IP address, you must first unregister the domain from Cisco UCS Central. You can reregister the Cisco UCS domain after you have changed or swapped the IP address.

Policy Resolution between Cisco UCS Manager and Cisco UCS Central

For each Cisco UCS domain that you register with Cisco UCS Central, you can choose which application will manage certain policies and configuration settings. This policy resolution does not have to be the same for every Cisco UCS domain that you register with the same Cisco UCS Central.

You have the following options for resolving these policies and configuration settings:

  • Local—The policy or configuration is determined and managed by Cisco UCS Manager.

  • Global—The policy or configuration is determined and managed by Cisco UCS Central.

The following table contains a list of the policies and configuration settings that you can choose to have managed by either Cisco UCS Manager or Cisco UCS Central:

Name Description

Infrastructure & Catalog Firmware

Determines whether the Capability Catalog and infrastructure firmware policy are defined locally or come from Cisco UCS Central.

Date & Time

Determines whether the date and time is defined locally or comes from Cisco UCS Central.

Communication

Determines whether HTTP, CIM XML, Telnet, SNMP, web session limits, and Management Interfaces Monitoring Policy settings are defined locally or in Cisco UCS Central.

Faults

Determines whether the Global Fault Policy is defined locally or in Cisco UCS Central.

Security

Determines whether authentication and native domains, LDAP, RADIUS, TACACS+, trusted points, locales, and user roles are defined locally or in Cisco UCS Central.

DNS Management

Determines whether DNS servers are defined locally or in Cisco UCS Central.

Config Backup

Determines whether the Full State Backup Policy and All Configuration Export Policy are defined locally or in Cisco UCS Central.

Monitoring

Determines whether Call Home, Syslog, and TFTP Core Exporter settings are defined locally or in Cisco UCS Central.

Managed Endpoint

Determines whether managed endpoints are defined locally or in Cisco UCS Central.

Power Management

Determines whether the power management is defined locally or in Cisco UCS Central.

Power Supply Unit

Determines whether power supply units are defined locally or in Cisco UCS Central.

Registering a Cisco UCS Domain with Cisco UCS Central


Note

You cannot change or swap the IP addresses used by Cisco UCS Manager in a domain that is registered with Cisco UCS Central. If you need to change or swap that IP address, you must first unregister the domain from Cisco UCS Central. You can reregister the Cisco UCS domain after you have changed or swapped the IP address.

Before You Begin

Configure an NTP server and the correct time zone in both Cisco UCS Manager and Cisco UCS Central to ensure that they are in sync. If the time and date in the Cisco UCS domain and Cisco UCS Central are out of sync, the registration might fail.

Procedure
     Command or ActionPurpose
    Step 1UCS-A# scope system 

    Enters system mode.

     
    Step 2UCS-A/system # create control-ep policy ucs-central  

    Creates the policy required to register the Cisco UCS Domain with Cisco UCS Central.

    ucs-central can be the hostname or IP address of the virtual machine where Cisco UCS Central is deployed.

    Note   

    If you use a hostname rather than an IPv4 or IPv6 address, you must configure a DNS server. If the Cisco UCS domain is not registered with Cisco UCS Central or DNS management is set to local, configure a DNS server in Cisco UCS Manager. If the Cisco UCS domain is registered with Cisco UCS Central and DNS management is set to global, configure a DNS server in Cisco UCS Central.

     
    Step 3Shared Secret for Registration: shared-secret  

    Enter the shared secret (or password) that was configured when Cisco UCS Central was deployed.

     
    Step 4UCS-A/system/control-ep # commit-buffer 

    Commits the transaction to the system configuration.

     

    The following example registers a Cisco UCS Domain with a Cisco UCS Central system at IP address 209.165.200.233, and commits the transaction: 

    UCS-A# scope system
UCS-A /system # create control-ep policy 209.165.200.233
Shared Secret for Registration: S3cretW0rd!
UCS-A /system/control-ep* # commit-buffer
UCS-A /system/control-ep #
    What to Do Next

    Configure policy resolution between Cisco UCS Manager and Cisco UCS Central.

    Configuring Policy Resolution between Cisco UCS Manager and Cisco UCS Central

    Before You Begin

    You must register the Cisco UCS Domain with Cisco UCS Central before you can configure policy resolution.

    Procedure
       Command or ActionPurpose
      Step 1UCS-A# scope system 

      Enters system mode.

       
      Step 2UCS-A/system # scope control-ep policy  

      Enters control-ep policy mode.

       
      Step 3 UCS-A/system/control-ep # set backup-policy-ctrl source {local | global} 

      Determines whether the Full State Backup Policy and All Configuration Export Policy are defined locally or in Cisco UCS Central.

       
      Step 4 UCS-A/system/control-ep # set communication-policy-ctrl source {local | global} 

      Determines whether HTTP, CIM XML, Telnet, SNMP, web session limits, and Management Interfaces Monitoring Policy settings are defined locally or in Cisco UCS Central.

       
      Step 5 UCS-A/system/control-ep # set datetime-policy-ctrl source {local | global} 

      Determines whether the date and time is defined locally or comes from Cisco UCS Central.

       
      Step 6 UCS-A/system/control-ep # set dns-policy-ctrl source {local | global} 

      Determines whether DNS servers are defined locally or in Cisco UCS Central.

       
      Step 7 UCS-A/system/control-ep # set fault-policy-ctrl source {local | global} 

      Determines whether the Global Fault Policy is defined locally or in Cisco UCS Central.

       
      Step 8 UCS-A/system/control-ep # set infra-pack-ctrl source {local | global} 

      Determines whether the Capability Catalog and infrastructure firmware policy are defined locally or come from Cisco UCS Central.

       
      Step 9 UCS-A/system/control-ep # set mep-policy-ctrl source {local | global} 

      Determines whether managed endpoints are defined locally or in Cisco UCS Central.

       
      Step 10 UCS-A/system/control-ep # set monitoring-policy-ctrl source {local | global} 

      Determines whether Call Home, Syslog, and TFTP Core Exporter settings are defined locally or in Cisco UCS Central.

       
      Step 11 UCS-A/system/control-ep # set powermgmt-policy-ctrl source {local | global} 

      Determines whether the power management is defined locally or in Cisco UCS Central.

       
      Step 12 UCS-A/system/control-ep # set psu-policy-ctrl source {local | global} 

      Determines whether power supply units are defined locally or in Cisco UCS Central.

       
      Step 13 UCS-A/system/control-ep # set security-policy-ctrl source {local | global} 

      Determines whether authentication and native domains, LDAP, RADIUS, TACACS+, trusted points, locales, and user roles are defined locally or in Cisco UCS Central.

       
      Step 14UCS-A/system/control-ep # commit-buffer 

      Commits the transaction to the system configuration.

       

      The following example configures policy resolution for a Cisco UCS Domain that is registered with Cisco UCS Central and commits the transaction: 

      UCS-A# scope system
UCS-A /system # scope control-ep policy
UCS-A /system/control-ep* # set backup-policy-ctrl source global
UCS-A /system/control-ep* # set communication-policy-ctrl source local
UCS-A /system/control-ep* # set datetime-policy-ctrl source global
UCS-A /system/control-ep* # set dns-policy-ctrl source global
UCS-A /system/control-ep* # set fault-policy-ctrl source global
UCS-A /system/control-ep* # set infra-pack-ctrl source global
UCS-A /system/control-ep* # set mep-policy-ctrl source global
UCS-A /system/control-ep* # set monitoring-policy-ctrl source global
UCS-A /system/control-ep* # set powermgmt-policy-ctrl source global
UCS-A /system/control-ep* # set psu-policy-ctrl source local
UCS-A /system/control-ep* # set security-policy-ctrl source global
UCS-A /system/control-ep* # commit-buffer
UCS-A /system/control-ep #

      Unregistering a Cisco UCS Domain from Cisco UCS Central

      When you unregister a Cisco UCS domain from Cisco UCS Central, Cisco UCS Manager no longer receives updates to global policies.

      Procedure
         Command or ActionPurpose
        Step 1UCS-A# scope system 

        Enters system mode.

         
        Step 2UCS-A/system # delete control-ep policy  

        Deletes the policy and unregisters the Cisco UCS Domain from Cisco UCS Central.

         
        Step 3UCS-A/system # commit-buffer 

        Commits the transaction to the system configuration.

         

        The following example unregisters a Cisco UCS Domain from Cisco UCS Central and commits the transaction: 

        UCS-A# scope system
UCS-A /system # delete control-ep policy
UCS-A /system* # commit-buffer
UCS-A /system #
        Registering Cisco UCS Domains with Cisco UCS Central

        Registering Cisco UCS Domains with Cisco UCS Central

        This chapter includes the following sections:

        Registration of Cisco UCS Domains

        You can have Cisco UCS Central manage some or all of the Cisco UCS domains in your data center.

        If you want to have Cisco UCS Central manage a Cisco UCS domain, you need to register that domain. When you register, you need to choose which types of policies and other configurations, such as backups and firmware, will be managed by Cisco UCS Central and which by Cisco UCS Manager. You can have Cisco UCS Central manage the same types of policies and configurations for all registered Cisco UCS domains or you can choose to have different settings for each registered Cisco UCS domain.

        Before you register a Cisco UCS domain with Cisco UCS Central, do the following:

        • Configure an NTP server and the correct time zone in both Cisco UCS Manager and Cisco UCS Central to ensure that they are in sync. If the time and date in the Cisco UCS domain and Cisco UCS Central are out of sync, the registration might fail.

        • Obtain the hostname or IP address of Cisco UCS Central

        • Obtain the shared secret that you configured when you deployed Cisco UCS Central


        Note

        You cannot change or swap the IP addresses used by Cisco UCS Manager in a domain that is registered with Cisco UCS Central. If you need to change or swap that IP address, you must first unregister the domain from Cisco UCS Central. You can reregister the Cisco UCS domain after you have changed or swapped the IP address.

        Policy Resolution between Cisco UCS Manager and Cisco UCS Central

        For each Cisco UCS domain that you register with Cisco UCS Central, you can choose which application will manage certain policies and configuration settings. This policy resolution does not have to be the same for every Cisco UCS domain that you register with the same Cisco UCS Central.

        You have the following options for resolving these policies and configuration settings:

        • Local—The policy or configuration is determined and managed by Cisco UCS Manager.

        • Global—The policy or configuration is determined and managed by Cisco UCS Central.

        The following table contains a list of the policies and configuration settings that you can choose to have managed by either Cisco UCS Manager or Cisco UCS Central:

        Name Description

        Infrastructure & Catalog Firmware

        Determines whether the Capability Catalog and infrastructure firmware policy are defined locally or come from Cisco UCS Central.

        Date & Time

        Determines whether the date and time is defined locally or comes from Cisco UCS Central.

        Communication

        Determines whether HTTP, CIM XML, Telnet, SNMP, web session limits, and Management Interfaces Monitoring Policy settings are defined locally or in Cisco UCS Central.

        Faults

        Determines whether the Global Fault Policy is defined locally or in Cisco UCS Central.

        Security

        Determines whether authentication and native domains, LDAP, RADIUS, TACACS+, trusted points, locales, and user roles are defined locally or in Cisco UCS Central.

        DNS Management

        Determines whether DNS servers are defined locally or in Cisco UCS Central.

        Config Backup

        Determines whether the Full State Backup Policy and All Configuration Export Policy are defined locally or in Cisco UCS Central.

        Monitoring

        Determines whether Call Home, Syslog, and TFTP Core Exporter settings are defined locally or in Cisco UCS Central.

        Managed Endpoint

        Determines whether managed endpoints are defined locally or in Cisco UCS Central.

        Power Management

        Determines whether the power management is defined locally or in Cisco UCS Central.

        Power Supply Unit

        Determines whether power supply units are defined locally or in Cisco UCS Central.

        Registering a Cisco UCS Domain with Cisco UCS Central


        Note

        You cannot change or swap the IP addresses used by Cisco UCS Manager in a domain that is registered with Cisco UCS Central. If you need to change or swap that IP address, you must first unregister the domain from Cisco UCS Central. You can reregister the Cisco UCS domain after you have changed or swapped the IP address.

        Before You Begin

        Configure an NTP server and the correct time zone in both Cisco UCS Manager and Cisco UCS Central to ensure that they are in sync. If the time and date in the Cisco UCS domain and Cisco UCS Central are out of sync, the registration might fail.

        Procedure
           Command or ActionPurpose
          Step 1UCS-A# scope system 

          Enters system mode.

           
          Step 2UCS-A/system # create control-ep policy ucs-central  

          Creates the policy required to register the Cisco UCS Domain with Cisco UCS Central.

          ucs-central can be the hostname or IP address of the virtual machine where Cisco UCS Central is deployed.

          Note   

          If you use a hostname rather than an IPv4 or IPv6 address, you must configure a DNS server. If the Cisco UCS domain is not registered with Cisco UCS Central or DNS management is set to local, configure a DNS server in Cisco UCS Manager. If the Cisco UCS domain is registered with Cisco UCS Central and DNS management is set to global, configure a DNS server in Cisco UCS Central.

           
          Step 3Shared Secret for Registration: shared-secret  

          Enter the shared secret (or password) that was configured when Cisco UCS Central was deployed.

           
          Step 4UCS-A/system/control-ep # commit-buffer 

          Commits the transaction to the system configuration.

           

          The following example registers a Cisco UCS Domain with a Cisco UCS Central system at IP address 209.165.200.233, and commits the transaction: 

          UCS-A# scope system
UCS-A /system # create control-ep policy 209.165.200.233
Shared Secret for Registration: S3cretW0rd!
UCS-A /system/control-ep* # commit-buffer
UCS-A /system/control-ep #
          What to Do Next

          Configure policy resolution between Cisco UCS Manager and Cisco UCS Central.

          Configuring Policy Resolution between Cisco UCS Manager and Cisco UCS Central

          Before You Begin

          You must register the Cisco UCS Domain with Cisco UCS Central before you can configure policy resolution.

          Procedure
             Command or ActionPurpose
            Step 1UCS-A# scope system 

            Enters system mode.

             
            Step 2UCS-A/system # scope control-ep policy  

            Enters control-ep policy mode.

             
            Step 3 UCS-A/system/control-ep # set backup-policy-ctrl source {local | global} 

            Determines whether the Full State Backup Policy and All Configuration Export Policy are defined locally or in Cisco UCS Central.

             
            Step 4 UCS-A/system/control-ep # set communication-policy-ctrl source {local | global} 

            Determines whether HTTP, CIM XML, Telnet, SNMP, web session limits, and Management Interfaces Monitoring Policy settings are defined locally or in Cisco UCS Central.

             
            Step 5 UCS-A/system/control-ep # set datetime-policy-ctrl source {local | global} 

            Determines whether the date and time is defined locally or comes from Cisco UCS Central.

             
            Step 6 UCS-A/system/control-ep # set dns-policy-ctrl source {local | global} 

            Determines whether DNS servers are defined locally or in Cisco UCS Central.

             
            Step 7 UCS-A/system/control-ep # set fault-policy-ctrl source {local | global} 

            Determines whether the Global Fault Policy is defined locally or in Cisco UCS Central.

             
            Step 8 UCS-A/system/control-ep # set infra-pack-ctrl source {local | global} 

            Determines whether the Capability Catalog and infrastructure firmware policy are defined locally or come from Cisco UCS Central.

             
            Step 9 UCS-A/system/control-ep # set mep-policy-ctrl source {local | global} 

            Determines whether managed endpoints are defined locally or in Cisco UCS Central.

             
            Step 10 UCS-A/system/control-ep # set monitoring-policy-ctrl source {local | global} 

            Determines whether Call Home, Syslog, and TFTP Core Exporter settings are defined locally or in Cisco UCS Central.

             
            Step 11 UCS-A/system/control-ep # set powermgmt-policy-ctrl source {local | global} 

            Determines whether the power management is defined locally or in Cisco UCS Central.

             
            Step 12 UCS-A/system/control-ep # set psu-policy-ctrl source {local | global} 

            Determines whether power supply units are defined locally or in Cisco UCS Central.

             
            Step 13 UCS-A/system/control-ep # set security-policy-ctrl source {local | global} 

            Determines whether authentication and native domains, LDAP, RADIUS, TACACS+, trusted points, locales, and user roles are defined locally or in Cisco UCS Central.

             
            Step 14UCS-A/system/control-ep # commit-buffer 

            Commits the transaction to the system configuration.

             

            The following example configures policy resolution for a Cisco UCS Domain that is registered with Cisco UCS Central and commits the transaction: 

            UCS-A# scope system
UCS-A /system # scope control-ep policy
UCS-A /system/control-ep* # set backup-policy-ctrl source global
UCS-A /system/control-ep* # set communication-policy-ctrl source local
UCS-A /system/control-ep* # set datetime-policy-ctrl source global
UCS-A /system/control-ep* # set dns-policy-ctrl source global
UCS-A /system/control-ep* # set fault-policy-ctrl source global
UCS-A /system/control-ep* # set infra-pack-ctrl source global
UCS-A /system/control-ep* # set mep-policy-ctrl source global
UCS-A /system/control-ep* # set monitoring-policy-ctrl source global
UCS-A /system/control-ep* # set powermgmt-policy-ctrl source global
UCS-A /system/control-ep* # set psu-policy-ctrl source local
UCS-A /system/control-ep* # set security-policy-ctrl source global
UCS-A /system/control-ep* # commit-buffer
UCS-A /system/control-ep #

            Unregistering a Cisco UCS Domain from Cisco UCS Central

            When you unregister a Cisco UCS domain from Cisco UCS Central, Cisco UCS Manager no longer receives updates to global policies.

            Procedure
               Command or ActionPurpose
              Step 1UCS-A# scope system 

              Enters system mode.

               
              Step 2UCS-A/system # delete control-ep policy  

              Deletes the policy and unregisters the Cisco UCS Domain from Cisco UCS Central.

               
              Step 3UCS-A/system # commit-buffer 

              Commits the transaction to the system configuration.

               

              The following example unregisters a Cisco UCS Domain from Cisco UCS Central and commits the transaction: 

              UCS-A# scope system
UCS-A /system # delete control-ep policy
UCS-A /system* # commit-buffer
UCS-A /system #