Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.3
Configuring Communication Services
Downloads: This chapterpdf (PDF - 466.0KB) The complete bookPDF (PDF - 2.03MB) | Feedback

Configuring Communication Services

Configuring Communication Services

This chapter includes the following sections:

Configuring HTTP

Before You Begin

You must log in as a user with admin privileges to configure HTTP.

Procedure
      Command or Action Purpose
    Step 1 Server# scope http  

    Enters the HTTP command mode.

     
    Step 2 Server /http # set enabled {yes | no}  

    Enables or disables HTTP and HTTPS service on the CIMC.

     
    Step 3 Server /http # set http-port number  

    Sets the port to use for HTTP communication. The default is 80.

     
    Step 4 Server /http # set https-port number  

    Sets the port to use for HTTPS communication. The default is 443.

     
    Step 5 Server /http # set timeout seconds  

    Sets the number of seconds to wait between HTTP requests before the CIMC times out and terminates the session.

    Enter an integer between 60 and 10,800. The default is 1,800 seconds.

     
    Step 6 Server /http # commit  

    Commits the transaction to the system configuration.

     

    This example configures HTTP for the CIMC:

    Server# scope http
    Server /http # set enabled yes
    Server /http *# set http-port 80
    Server /http *# set https-port 443
    Server /http *# set timeout 1800
    Server /http *# commit
    Server /http # show
    HTTP Port  HTTPS Port Timeout  Active Sessions Enabled 
    ---------- ---------- -------- --------------- ------- 
    80         443        1800     0               yes 
        
    Server /http #         
    

    Configuring SSH

    Before You Begin

    You must log in as a user with admin privileges to configure SSH.

    Procedure
        Command or Action Purpose
      Step 1 Server# scope ssh  

      Enters the SSH command mode.

       
      Step 2 Server /ssh # set enabled {yes | no}  

      Enables or disables SSH on the CIMC.

       
      Step 3 Server /ssh # set ssh-port number  

      Sets the port to use for secure shell access. The default is 22.

       
      Step 4 Server /ssh # set timeout seconds  

      Sets the number of seconds to wait before the system considers an SSH request to have timed out.

      Enter an integer between 60 and 10,800. The default is 300 seconds.

       
      Step 5 Server /ssh # commit  

      Commits the transaction to the system configuration.

       
      Step 6 Server /ssh # show [detail]  

      (Optional) Displays the SSH configuration.

       

      This example configures SSH for the CIMC:

      Server# scope ssh
      Server /ssh # set enabled yes
      Server /ssh *# set ssh-port 22
      Server /ssh *# set timeout 600
      Server /ssh *# commit
      Server /ssh # show
      SSH Port   Timeout  Active Sessions Enabled 
      ---------- -------- --------------- ------- 
      22         600      1               yes     
      
      Server /ssh #         
      

      Configuring IPMI

      IPMI Over LAN

      IPMI defines the protocols for interfacing with a service processor embedded in a server platform. This service processor is called a Baseboard Management Controller (BMC) and resides on the server motherboard. The BMC links to a main processor and other on-board elements using a simple serial bus.

      During normal operations, IPMI lets a server operating system obtain information about system health and control system hardware. For example, IPMI enables the monitoring of sensors, such as temperature, fan speeds and voltages, for proactive problem detection. If server temperature rises above specified levels, the server operating system can direct the BMC to increase fan speed or reduce processor speed to address the problem.

      Configuring IPMI over LAN

      Configure IPMI over LAN when you want to manage the CIMC with IPMI messages.

      Before You Begin

      You must log in with admin privileges to perform this task.

      Procedure
          Command or Action Purpose
        Step 1 Server# scope ipmi  

        Enters the IPMI command mode.

         
        Step 2 Server /ipmi # set enabled {yes | no}  

        Enables or disables IPMI access on this server.

         
        Step 3 Server /ipmi # set privilege-level {readonly | user | admin}  
        Specifies the highest privilege level that can be assigned to an IPMI session on this server. This can be:
        • readonly — IPMI users can view information but cannot make any changes. If you select this option, IPMI users with the "Administrator", "Operator", or "User" user roles can only create read-only IPMI sessions, regardless of their other IPMI privileges.
        • user — IPMI users can perform some functions but cannot perform administrative tasks. If you select this option, IPMI users with the "Administrator" or "Operator" user role can create user and read-only sessions on this server.
        • admin — IPMI users can perform all available actions. If you select this option, IPMI users with the "Administrator" user role can create admin, user, and read-only sessions on this server.
         
        Step 4 Server /ipmi # set encryption-key key  

        Sets the IPMI encryption key to use for IPMI communications. The key value must be 40 hexadecimal numbers.

         
        Step 5 Server /ipmi # commit  

        Commits the transaction to the system configuration.

         

        This example configures IPMI over LAN for the CIMC:

        Server# scope ipmi
        Server /ipmi # set enabled yes
        Server /ipmi *# set privilege-level admin
        Server /ipmi *# set encryption-key abcdef01234567890abcdef01234567890abcdef
        Server /ipmi *# commit
        Server /ipmi # show
        Enabled Encryption Key                           Privilege Level Limit 
        ------- ---------------------------------------- --------------------- 
        yes     abcdef01234567890abcdef01234567890abcdef admin              
        
        Server /ipmi #         
        

        Configuring SNMP Properties

        Before You Begin

        You must log in as a user with admin privileges to perform this task.

        Procedure
            Command or Action Purpose
          Step 1 Server# scope snmp  

          Enters SNMP command mode.

           
          Step 2 Server /snmp # set enabled {yes | no}  

          Enables or disables SNMP.

          Note   

          SNMP must be enabled and saved before additional SNMP configuration commands are accepted.

           
          Step 3 Server /snmp # commit  

          Commits the transaction to the system configuration.

           
          Step 4 Server /snmp # set community-str community  

          Specifies the default SNMP v1 or v2c community name that CIMC includes on any trap messages it sends to the SNMP host. The name can be up to 18 characters.

           
          Step 5 Server /snmp # set sys-contact contact  

          Specifies the system contact person responsible for the SNMP implementation. The contact information can be up to 254 characters, such as an email address or a name and telephone number. To enter a value that contains spaces, you must enclose the entry with quotation marks.

           
          Step 6 Server /snmp # set sys-location location  

          Specifies the location of the host on which the SNMP agent (server) runs. The location information can be up to 254 characters. To enter a value that contains spaces, you must enclose the entry with quotation marks.

           
          Step 7 Server /snmp # commit  

          Commits the transaction to the system configuration.

           

          This example configures the SNMP properties and commits the transaction:

          Server# scope snmp
          Server /snmp # set enabled yes
          Server /snmp *# commit
          Server /snmp # set community-str cimcpublic
          Server /snmp *# set sys-contact "User Name <username@example.com> +1-408-555-1212"
          Server /snmp *# set sys-location "San Jose, California"
          Server /snmp *# commit
          Server /snmp #  show detail
          SNMP Settings:
              SNMP Port: 161
              System Contact: User Name <username@example.com> +1-408-555-1212
              System Location: San Jose, California
              SNMP Community: cimcpublic
              SNMP Trap community: 0
              Enabled: yes
              SNMP Trap Version: 1
              SNMP Inform Type: inform
          
          Server /snmp #  
          
          What to Do Next

          Configure SNMP trap settings as described in Configuring SNMP Trap Settings.