Cisco UCS Manager CLI Quick Reference Guide for Cisco UCS M-Series Modular Servers, Release 2.5
Managing Modular Servers
Managing Modular Servers

Managing Modular Servers

This part contains the following chapters:

Modular Server Management

Modular servers, which are introduced in Cisco UCS M-Series, are contained in compute cartridges.


(注)  


You cannot remove servers from their cartridges.


Booting a Modular Server

はじめる前に

Associate a service profile with a modular server or server pool.

手順の概要

    1.    UCS-A# scope org org-name

    2.    UCS-A /org # scope service-profile profile-name

    3.    UCS-A /org/service-profile # power up

    4.    UCS-A /org/service-profile # commit-buffer


手順の詳細
     コマンドまたはアクション目的
    ステップ 1UCS-A# scope org org-name  

    Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name .

     
    ステップ 2UCS-A /org # scope service-profile profile-name  

    Enters organization service profile mode for the specified service profile.

     
    ステップ 3UCS-A /org/service-profile # power up  

    Boots the modular server associated with the service profile.

     
    ステップ 4UCS-A /org/service-profile # commit-buffer  

    Commits the transaction to the system configuration.

     

    The following example boots the modular server associated with the service profile named ServProf34 and commits the transaction:

    UCS-A# scope org /
    UCS-A /org* # scope service-profile ServProf34
    UCS-A /org/service-profile* # power up
    UCS-A /org/service-profile* # commit-buffer
    UCS-A /org/service-profile #
    

    Shutting Down a Modular Server

    この手順を使用して、インストールされているオペレーティング システムによりサーバをシャットダウンする場合、Cisco UCS Manager により、この OS のグレースフル シャットダウン シーケンスがトリガーされます。

    はじめる前に

    Associate a service profile with a modular server or server pool.

    手順の概要

      1.    UCS-A# scope org org-name

      2.    UCS-A /org # scope service-profile profile-name

      3.    UCS-A /org/service-profile # power down

      4.    UCS-A /org/service-profile # commit-buffer


    手順の詳細
       コマンドまたはアクション目的
      ステップ 1UCS-A# scope org org-name  

      Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name.

       
      ステップ 2UCS-A /org # scope service-profile profile-name  

      Enters organization service profile mode for the specified service profile.

       
      ステップ 3UCS-A /org/service-profile # power down  

      Shuts down the modular server associated with the service profile.

       
      ステップ 4UCS-A /org/service-profile # commit-buffer  

      Commits the transaction to the system configuration.

       

      The following example shuts down the modular server associated with the service profile named ServProf34 and commits the transaction:

      UCS-A# scope org /
      UCS-A /org # scope service-profile ServProf34
      UCS-A /org/service-profile # power down
      UCS-A /org/service-profile* # commit-buffer
      UCS-A /org/service-profile #
      

      Power Cycling a Modular Server

      手順の概要

        1.    UCS-A# scope server chassis-num / cartridge-id / server-num

        2.    UCS-A /chassis/cartridge/server # cycle {cycle-immediate | cycle-wait}

        3.    UCS-A /chassis/cartridge/server # commit-buffer


      手順の詳細
         コマンドまたはアクション目的
        ステップ 1UCS-A# scope server chassis-num / cartridge-id / server-num  

        Enters cartridge server mode for the specified modular server in the specified chassis and cartridge.

         
        ステップ 2UCS-A /chassis/cartridge/server # cycle {cycle-immediate | cycle-wait}  

        Power cycles the modular server.

        Use the cycle-immediate keyword to immediately begin power cycling the modular server; use the cycle-wait keyword to schedule the power cycle to begin after all pending management operations have completed.

         
        ステップ 3UCS-A /chassis/cartridge/server # commit-buffer  

        Commits the transaction to the system configuration.

         

        The following example immediately power cycles modular server 2 in cartridge 2 of chassis 2 and commits the transaction:

        UCS-A#  scope server 2/2/2
        UCS-A /chassis/cartridge/server # cycle cycle-immediate
        UCS-A /chassis/cartridge/server # commit-buffer
        UCS-A /chassis/cartridge/server # 
        

        Performing a Hard Reset on a Modular Server

        サーバをリセットすると、Cisco UCS Manager により、リセット ライン上にパルスが送信されます。 オペレーティング システムのグレースフル シャットダウンを選択することができます。 オペレーティング システムでグレースフル シャットダウンがサポートされていない場合、サーバ電源の再投入が行われます。 Cisco UCS Manager に、サーバをリセットする前にすべての管理操作を完了させるオプションでは、これらの操作がサーバのリセット前に完了するかどうかは保証されていません。


        (注)  


        電源切断状態からサーバをブートする場合は、[Reset] を使用しないでください。

        この手順を使用して電源投入を続けると、サーバの望ましい電源状態が実際の電源状態と同期しなくなり、サーバが後で予期せずシャットダウンすることがあります。 選択したサーバを電源切断状態から安全にリブートするには、[Cancel] をクリックし、[Boot Server] アクションを選択します。


        手順の概要

          1.    UCS-A# scope server chassis-num / cartridge-id / server-num

          2.    UCS-A /chassis/cartridge/server # reset {hard-reset-immediate | hard-reset-wait}

          3.    UCS-A /chassis/cartridge/server # commit-buffer


        手順の詳細
           コマンドまたはアクション目的
          ステップ 1UCS-A# scope server chassis-num / cartridge-id / server-num  

          Enters cartridge server mode for the specified modular server in the specified chassis and cartridge.

           
          ステップ 2UCS-A /chassis/cartridge/server # reset {hard-reset-immediate | hard-reset-wait}  

          Performs a hard reset of the modular server.

          Use the hard-reset-immediate keyword to immediately begin hard resetting the server; use the hard-reset-wait keyword to schedule the hard reset to begin after all pending management operations have completed.

           
          ステップ 3UCS-A /chassis/cartridge/server # commit-buffer  

          Commits the transaction to the system configuration.

           

          The following example performs an immediate hard reset of modular server 2 in cartridge 2 of chassis 2 and commits the transaction:

          UCS-A#  scope server 2/2/2
          UCS-A /chassis/cartridge/server # reset hard-reset-immediate
          UCS-A /chassis/cartridge/server* # commit-buffer
          UCS-A /chassis/cartridge/server # 
          

          Acknowledging a Modular Server

          Cisco UCS Manager にサーバ、およびそのサーバのすべてのエンドポイントを再検出させる必要がある場合は、次の手順を実行します。 たとえば、サーバがディスカバリ状態など、予期していなかった状態から抜け出せなくなっている場合に、この手順を使用します。

          手順の概要

            1.    UCS-A# acknowledge server chassis-id / cartridge-id / server-id

            2.    UCS-A /chassis/cartridge/server # commit-buffer


          手順の詳細
             コマンドまたはアクション目的
            ステップ 1UCS-A# acknowledge server chassis-id / cartridge-id / server-id  

            Acknowledges the specified modular server in the specified chassis and cartridge.

             
            ステップ 2UCS-A /chassis/cartridge/server # commit-buffer  

            Commits the transaction to the system configuration.

             

            The following example acknowledges modular server 2 in cartridge 2 of chassis 2 and commits the transaction:

            UCS-A# acknowledge server 2/2/2
            UCS-A /chassis/cartridge/server* # commit-buffer
            UCS-A # 
            

            Decommissioning a Modular Server

            Decommissioning of a server is performed to temporarily remove the server from the UCSM configuration.

            手順の概要

              1.    UCS-A# decommission server chassis-num / cartridge-id / server-num

              2.    UCS-A /chassis/cartridge/server # commit-buffer


            手順の詳細
               コマンドまたはアクション目的
              ステップ 1UCS-A# decommission server chassis-num / cartridge-id / server-num  

              Decommissions the specified modular server in the specified chassis and cartridge.

               
              ステップ 2UCS-A /chassis/cartridge/server # commit-buffer  

              Commits the transaction to the system configuration.

               

              The following example decommissions modular server 2 in cartridge 2 of chassis 2 and commits the transaction:

              UCS-A# decommission server 2/2/2
              UCS-A /chassis/cartridge/server* # commit-buffer
              UCS-A # 
              

              Showing the Status of a Modular Server

              手順の概要

                1.    UCS-A# scope server chassis-num / cartridge-id / server-num

                2.    UCS-A /chassis/cartridge/server # show status


              手順の詳細
                 コマンドまたはアクション目的
                ステップ 1UCS-A# scope server chassis-num / cartridge-id / server-num  

                Enters cartridge server mode for the specified modular server in the specified chassis and cartridge.

                 
                ステップ 2UCS-A /chassis/cartridge/server # show status  

                Shows the status for the specified modular server.

                 

                The following example shows the status for modular server 1 in cartridge 3 of chassis 1:

                UCS-A# scope server 1/3/1
                UCS-A /chassis/cartridge/server # show status
                
                Server  Slot Status                       Availability Overall Status        Discovery
                ------- --------------------------------- ------------ --------------------- ---------
                1/3/1   Equipped                          Available    Unassociated          Complete
                
                
                

                Turning On the Locator LED for a Modular Server

                The locator LED is shared by all servers in a cartridge. Hence, you can turn the locator LED on from any server in a cartridge.

                手順の概要

                  1.    UCS-A# scope server chassis-num / cartridge-id / server-num

                  2.    UCS-A /chassis/cartridge/server # enable locator-led

                  3.    UCS-A /chassis/cartridge/server # commit-buffer


                手順の詳細
                   コマンドまたはアクション目的
                  ステップ 1UCS-A# scope server chassis-num / cartridge-id / server-num  

                  Enters chassis server mode for the specified modular server in the specified chassis and cartridge.

                   
                  ステップ 2UCS-A /chassis/cartridge/server # enable locator-led  

                  Turns on the modular server locator LED.

                   
                  ステップ 3UCS-A /chassis/cartridge/server # commit-buffer  

                  Commits the transaction to the system configuration.

                   

                  The following example turns on the locator LED for modular server 2 in cartridge 2 of chassis 2 and commits the transaction:

                  UCS-A# scope server 2/2/2
                  UCS-A /chassis/cartridge/server # enable  locator-led
                  UCS-A /chassis/cartridge/server* # commit-buffer
                  UCS-A /chassis/cartridge/server # 
                  
                  
                  

                  Turning Off the Locator LED for a Modular Server

                  The locator LED is shared by all servers in a cartridge. Hence, to turn off a locator LED of a cartridge, you must turn it off from all servers in the cartridge.

                  手順の概要

                    1.    UCS-A# scope server chassis-num / cartridge-id / server-num

                    2.    UCS-A /chassis/cartridge/server # disable locator-led

                    3.    UCS-A /chassis/cartridge/server # commit-buffer


                  手順の詳細
                     コマンドまたはアクション目的
                    ステップ 1UCS-A# scope server chassis-num / cartridge-id / server-num  

                    Enters chassis mode for the specified modular server in the specified chassis and cartridge.

                     
                    ステップ 2UCS-A /chassis/cartridge/server # disable locator-led  

                    Turns off the modular server locator LED.

                     
                    ステップ 3UCS-A /chassis/cartridge/server # commit-buffer  

                    Commits the transaction to the system configuration.

                     

                    The following example turns off the locator LED for modular server 2 in cartridge 2 of chassis 2 and commits the transaction:

                    UCS-A# scope chassis 2/2/2
                    UCS-A /chassis/cartridge/server # disable locator-led
                    UCS-A /chassis/cartridge/server* # commit-buffer
                    UCS-A /chassis/cartridge/server # 
                    
                    

                    Resetting the CMOS for a Modular Server

                    非常に珍しいケースですが、サーバのトラブルシューティング時に、CMOS のリセットが必要になることがあります。 この手順は、通常のサーバ メンテナンスには含まれません。

                    手順の概要

                      1.    UCS-A# scope server chassis-num / cartridge-id / server-num

                      2.    UCS-A /chassis/cartridge/server # reset-cmos

                      3.    UCS-A /chassis/cartridge/server # commit-buffer


                    手順の詳細
                       コマンドまたはアクション目的
                      ステップ 1UCS-A# scope server chassis-num / cartridge-id / server-num  

                      Enters cartridge server mode for the specified modular server in the specified chassis and cartridge.

                       
                      ステップ 2UCS-A /chassis/cartridge/server # reset-cmos  

                      Resets the CMOS for the modular server.

                       
                      ステップ 3UCS-A /chassis/cartridge/server # commit-buffer  

                      Commits the transaction to the system configuration.

                       

                      The following example resets the CMOS for modular server 2 in cartridge 2 of chassis 2 and commits the transaction:

                      UCS-A# scope server 2/2/2
                      UCS-A /chassis/cartridge/server # reset-cmos
                      UCS-A /chassis/cartridge/server* # commit-buffer
                      UCS-A /chassis/cartridge/server #  
                      

                      Resetting the CIMC for a Modular Server

                      現在実行されているファームウェアで問題が発生した場合など、非常に珍しいケースですが、サーバのトラブルシューティング時に、CIMC のリセットが必要になることがあります。 この手順は、通常のサーバ メンテナンスには含まれません。 CIMC のリセット後、サーバは、そのサーバで実行されているバージョンのファームウェアを使ってブートされます。

                      CIMC をリセットすると、CIMC がリブートするまでの間、Cisco UCS の電力モニタリング機能が短時間使用不能になります。 通常は 20 秒しかかかりませんが、その間にピーク電力制限を超える可能性があります。 非常に低い電力制限が設定された環境で、設定された電力制限を超えないようにするには、CIMC のリブートまたはアクティブ化を交互に実施することを検討してください。

                      手順の概要

                        1.    UCS-A# scope server chassis-num / cartridge-id / server-num

                        2.    UCS-A /chassis/cartridge/server # scope CIMC

                        3.    UCS-A /chassis/cartridge/server/CIMC # reset

                        4.    UCS-A /chassis/cartridge/server/CIMC # commit-buffer


                      手順の詳細
                         コマンドまたはアクション目的
                        ステップ 1UCS-A# scope server chassis-num / cartridge-id / server-num  

                        Enters cartridge server mode for the specified modular server in the specified chassis and cartridge.

                         
                        ステップ 2UCS-A /chassis/cartridge/server # scope CIMC  

                        Enters cartridge server CIMC mode

                         
                        ステップ 3UCS-A /chassis/cartridge/server/CIMC # reset  

                        Resets the CIMC for the modular server.

                         
                        ステップ 4UCS-A /chassis/cartridge/server/CIMC # commit-buffer  

                        Commits the transaction to the system configuration.

                         

                        The following example resets the CIMC for modular server 2 in cartridge 2 of chassis 2 and commits the transaction:

                        UCS-A# scope server 2/2/2
                        UCS-A /chassis/cartridge/server # scope CIMC
                        UCS-A /chassis/cartridge/server/cimc # reset
                        UCS-A /chassis/cartridge/server/cimc* # commit-buffer
                        UCS-A /chassis/cartridge/server/cimc #  
                        

                        Issuing an NMI from a Modular Server

                        システムが応答しないままになっており、Cisco UCS Manager で、CIMC から Non Maskable Interrupt(NMI)を BIOS またはオペレーティング システムに発行する必要がある場合は、次の手順を実行します。 このアクションにより、サーバにインストールされているオペレーティング システム応じて、コア ダンプまたはスタック トレースが作成されます。

                        手順の概要

                          1.    UCS-A # scope server chassis-id / cartridge-id / server-id

                          2.    UCS-A /chassis/cartridge/server # diagnostic-interrupt

                          3.    UCS-A /chassis/cartridge/server # commit-buffer


                        手順の詳細
                           コマンドまたはアクション目的
                          ステップ 1UCS-A # scope server chassis-id / cartridge-id / server-id  

                          Enters server mode for the specified server.

                           
                          ステップ 2UCS-A /chassis/cartridge/server # diagnostic-interrupt    
                          ステップ 3UCS-A /chassis/cartridge/server # commit-buffer  

                          Commits the transaction to the system configuration.

                           

                          The following example sends an NMI from server 2 in cartridge 2 of chassis 2 and commits the transaction:

                          UCS-A# scope server 2/2/2
                          UCS-A /chassis/cartridge/server # diagnostic-interrupt
                          UCS-A /chassis/cartridge/server* # commit-buffer
                          UCS-A /chassis/cartridge/server # 
                          

                          Health LED Alarms

                          The server health LED is located on the front of each Cisco UCS M-Series server. Cisco UCS Manager allows you to view the sensor faults that cause the server health LED to change color from green to amber or blinking amber.

                          The health LED alarms display the following information:

                          Name Description

                          Severity column

                          The severity of the alarm. This can be one of the following:

                          • Critical—The blade health LED is blinking amber.

                          • Minor—The blade health LED is amber.

                          Description column

                          A brief description of the alarm.

                          Sensor ID column

                          The ID of the sensor the triggered the alarm.

                          Sensor Name column

                          The name of the sensor that triggered the alarm.

                          Viewing Health LED Status

                          手順の概要

                            1.    UCS-A# scope server chassis-id / cartridge-id / server-num

                            2.    UCS-A /chassis/cartridge/server # show health-led expand


                          手順の詳細
                             コマンドまたはアクション目的
                            ステップ 1 UCS-A# scope server chassis-id / cartridge-id / server-num  

                            Enters cartridge server mode for the specified modular server in the specified chassis and cartridge.

                             
                            ステップ 2UCS-A /chassis/cartridge/server # show health-led expand  

                            Displays the health LED and sensor alarms for the selected server.

                             

                            The following example shows how to display the health LED status and sensor alarms for chassis 1 cartridge 2 server 1:

                            UCS-A# scope server 1/2/1
                            UCS-A /chassis/cartridge/server # show health-led
                            Health LED:
                                Severity: Minor
                                Reason:: P0V75_STBY:Voltage Threshold Crossed;TEMP_SENS_FRONT:Temperature Threshold Crossed;
                                Color: Amber
                                Oper State:: On
                            
                                Sensor Alarm:
                                    Severity: Minor
                                    Sensor ID: 7
                                    Sensor Name: P0V75_STBY
                                    Alarm Desc: Voltage Threshold Crossed
                            
                                    Severity: Minor
                                    Sensor ID: 76
                                    Sensor Name: TEMP_SENS_FRONT
                                    Alarm Desc: Temperature Threshold Crossed
                            
                                    Severity: Minor
                                    Sensor ID: 91
                                    Sensor Name: DDR3_P1_D2_TMP
                                    Alarm Desc: Temperature Threshold Crossed
                            
                            UCS-A /chassis/cartridge/server #