Basically there’s two options that i like to use when connecting to Cisco’s Integrated Management Console (CIMC).  Via the router connected to an address within the allocated subnet.  Although using this method you must add the host specific route to the ucse4/0 interface to provide access to the UCS-E module.

interface ucse4/0
description UCS-E Series CIMC Link
no ip unnumbered GigabitEthernet0/0
imc ip address 172.22.39.70 255.255.255.248 default-gateway 172.22.39.65
imc access-port shared-lom
!
ip route 172.22.39.70 255.255.255.255 ucse4/0

Alternatively, to manage the CIMC from your Data-vLAN add the below device configuration and use the dedicated console mode to provide access to the CIMC alone.  Ensure you put the console into the correct vLAN for management, in this case I’ll be using vLAN-901.

interface ucse4/0
description UCS-E Series CIMC Link
no ip unnumbered GigabitEthernet0/0
imc ip address 172.22.36.2 255.255.255.0 default-gateway 172.22.36.1
imc access-port dedicated console
end
!
Supporting a vMware configuration you will need to use x2 GigabitEthernet ports for redundancy / fail-over. These are GE2 & G3 (GE1 is used for the Console) The x2 ports should be added to the Data-vLAN, and NIC teamed using VMware.

Summary of ports:

GigabitEthernet1/0/11 >> GE2
GigabitEthernet1/0/12 >> GE3
GigabitEthernet1/0/13 >> GE1 (Console Port)

I recently ran into “The maximum number of user sessions has been reached” error when working on a new Cisco UCS-E160D.

To fix things you can SSH to the CIMC address and run:

show user-session

To change to a particular session from the resulting list, note the session index numbers from the user-session list and run:

scope user-session sessionindex

To end the session you just switched to, run:

terminate

To exit the scope of that session, run:

exit