The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter includes the following sections:
Each server in a Cisco UCS instance must have a management IP address assigned to its Cisco Integrated Management Controller (CIMC) or to the service profile associated with the server. Cisco UCS Manager uses this IP address for external access that terminates in the CIMC. This external access can be through one of the following:
The management IP address used to access the CIMC on a server can be one of the following:
You can assign a management IP address to each CIMC on the server and to the service profile associated with the server. If you do so, you must use different IP addresses for each of them.
Note |
You cannot assign a static IP address to a server or service profile if that IP address has already been assigned to a server or service profile in the Cisco UCS instance. If you attempt to do so, Cisco UCS Manager warns you that the IP address is already in use and rejects the configuration. |
A management IP address that is assigned to a service profile moves with the service profile. If a KVM or SoL session is active when you migrate the service profile to another server, Cisco UCS Manager terminates that session and does not restart it after the migration is completed. You configure this IP address when you create or modify a service profile.
Configuring the Management IP Address on a Blade Server
The following example configures a static management IP address for chassis 1 server 1, sets the static IPv4 address, sets the default gateway, sets the subnet mask, and commits the transaction:
UCS-A# scope server 1/1 UCS-A /chassis/server # scope cimc UCS-A /chassis/server/cimc # create ext-static-ip UCS-A /chassis/server/cimc/ext-static-ip* # set addr 192.168.10.10 UCS-A /chassis/server/cimc/ext-static-ip* # set default-gw 192.168.10.1 UCS-A /chassis/server/cimc/ext-static-ip* # set subnet 255.255.255.0 UCS-A /chassis/server/cimc/ext-static-ip* # commit-buffer UCS-A /chassis/server/cimc/ext-static-ip #
Deleting the static management IP address returns the specified server to the management IP pool.
The following example deletes the static management IP address for chassis 1 server 1 and commits the transaction:
UCS-A# scope server 1/1 UCS-A /chassis/server # scope cimc UCS-A /chassis/server/cimc # delete ext-static-ip UCS-A /chassis/server/cimc* # commit-buffer UCS-A /chassis/server/cimc/ #
Configuring the Management IP Address on a Rack Server
The following example configures a static management IP address for rack server 1, sets the static IPv4 address, sets the default gateway, sets the subnet mask, and commits the transaction:
UCS-A# scope server 1 UCS-A /server # scope cimc UCS-A /server/cimc # create ext-static-ip UCS-A /server/cimc/ext-static-ip* # set addr 192.168.10.10 UCS-A /server/cimc/ext-static-ip* # set default-gw 192.168.10.1 UCS-A /server/cimc/ext-static-ip* # set subnet 255.255.255.0 UCS-A /server/cimc/ext-static-ip* # commit-buffer UCS-A /server/cimc/ext-static-ip #
Deleting the static management IP address returns the specified server to the management IP pool.
The following example deletes the static management IP address for rack server 1 and commits the transaction:
UCS-A# scope server 1 UCS-A /server # scope cimc UCS-A /server/cimc # delete ext-static-ip UCS-A /server/cimc* # commit-buffer UCS-A /server/cimc/ #
The following example sets the management IP address policy for a service profile called accounting to static and then commits the transaction:
UCS-A# scope org / UCS-A /org # scope service-profile accounting UCS-A /org/service-profile # set ext-mgmt-ip-state static UCS-A /org/service-profile* # commit-buffer UCS-A /org/service-profile #
If you have set the management IP address to static, configure a server to use a static IP address.
Configuring the Management IP Pool
The management IP pool is a collection of external IP addresses. Cisco UCS Manager reserves each block of IP addresses in the management IP pool for external access that terminates in the CIMC on a server.
You can configure service profiles and service profile templates to use IP addresses from the management IP pool. You cannot configure servers to use the management IP pool.
All IP addresses in the management IP pool must be in the same subnet as the IP address of the fabric interconnect.
Note |
The management IP pool must not contain any IP addresses that have been assigned as static IP addresses for a server or service profile. |
The management IP pool must not contain any IP addresses that have been assigned as static IP addresses for a server or service profile.
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | UCS-A# scope org / | Enters root organization mode. |
||
Step 2 | UCS-A /org # scope ip-pool ext-mgmt | Enters organization IP pool mode.
|
||
Step 3 | UCS-A /org/ip-pool # set descr description | (Optional) Provides a description for the management IP pool. This description applies to all address blocks in the management IP pool.
|
||
Step 4 | UCS-A /org/ip-pool # create block first-ip-addr last-ip-addr gateway-ip-addr subnet-mask | Creates a block (range) of IP addresses, and enters organization IP pool block mode. You must specify the first and last IP addresses in the address range, the gateway IP address, and subnet mask.
|
||
Step 5 | UCS-A /org/ip-pool/block # commit-buffer | Commits the transaction to the system configuration. |
The following example configures an IP address block for the management IP pool and commits the transaction:
UCS-A# scope org / UCS-A /org # scope ip-pool ext-mgmt UCS-A /org/ip-pool* # set descr "This is a management IP pool example." UCS-A /org/ip-pool* # create block 192.168.100.1 192.168.100.200 192.168.100.10 255.255.255.0 UCS-A /org/ip-pool/block* # commit-buffer UCS-A /org/ip-pool/block #
Configure one or more service profiles or service profile templates to obtain the CIMC IP address from the management IP pool.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# scope org org-name | Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name . |
Step 2 | UCS-A /org # scope ip-pool ext-mgmt | Enters the management IP pool. |
Step 3 | UCS-A /org/ip-pool # delete block first-ip-addr last-ip-addr | Deletes the specified block (range) of IP addresses. |
Step 4 | UCS-A /org/ip-pool # commit-buffer | Commits the transaction to the system configuration. |
The following example configures an IP address block for the management IP pool and commits the transaction:
UCS-A# scope org / UCS-A /org # scope ip-pool ext-mgmt UCS-A /org/ip-pool # delete block 192.168.100.1 192.168.100.200 UCS-A /org/ip-pool* # commit-buffer UCS-A /org/ip-pool #