cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
630
Views
0
Helpful
5
Replies

Enable CIMC Management from Catalyst Centre using Enterprise Interface

Toy Thompson
Level 1
Level 1

I have a Catalyst Centre (2.3.7.x) with the following configuration:

1 Node Cluster
Enterprise Interface: 10.10.10.146/29 VIP:10.10.10.150 static route 10.0.0.0/255.0.0.0/10.10.10.145 (Used for bulk communication of Catalysts Centre) where 10.10.10.145 is the default gateway

Internet Interface: 10.10.10.138/29 DG:10.10.10.137 VIP:10.10.10.140 (Used mainly for internet communication with cisco.com)

Management Interface: 10.10.10.131/29 VIP:10.10.10.130 static route 172.10.10.0/255.255.255.0/10.10.10.145 (Used by 3rd party management and API platforms) where 10.10.10.129 is the default gateway

 

During the deployment the client requested the management interface to change as follows:
Management Interface: 192.168.10.21/24 VIP:192.168.10.20 static route 172.10.10.0/255.255.255.0/192.168.10.1 (Used by 3rd party management and API platforms) where 192.168.10.1 is the default gateway (Changed using maglev-configuration wizard)

We now want to enable management of the CIMC interface through the Catalyst Centre. 

  • Can we manage the CIMC interface through the Catalyst Centre using the Enterprise Interface (10.10.10.146 or 10.10.10.150) and not the Management Interface (192.168.10.21)
  • I tried to enable the CIMC interface management through System->Setting->System Health but it by default use the previous Management IP 10.10.10.131 as the Catalyst Centre Address, the "trashcan" is greyed out so I cannot delete it and I cannot add another interface to use for communication with the CIMC interface
  • Is there maybe a way in the CLI to configure the System Health to use the Enterprise Interface (10.10.10.146 or 10.10.10.150) and not the Management Interface(192.168.10.21) if editing in the GUI is not possible?
5 Replies 5

Torbjørn
VIP
VIP

Interface selection is based on the routing table for the Cat-C appliance. If you wish to route that traffic through the management interface you simply add a route for the CIMC address through the gateway in the management network, the same goes if you want it to go out the enterprise interface. If the CIMC is in the same network as the management interface yout Cat-C will always use the management interface for connectivity. 

Happy to help! Please mark as helpful/solution if applicable.
Get in touch: https://torbjorn.dev

Thanks for the response....the routing is working, if I do a traceroute in the CLI to the CIMC interface IP, traffic is forwarded to the Enterprise Interface default gateway, which is correct.
When I try to enable manage the CIMC using the Catalyst Centre (go System->Settings->System Health) the Catalyst Centre by default add the previous Management as the Catalyst Center Address. I cannot delete the entry and I cannot add an entry to use the Enterprise Interface instead

 

maflesch
Cisco Employee
Cisco Employee

That's because that's the route that the API has defined as the port that communicates to the Cisco IMC address. You can also test this by going to the CLI of the Catalyst Center and issuing this command:

ip route get <CIMC address>

Thank you for the clarification. Can I change it to use the Enterprise Interface instead
I ran the command and the route sends traffic for the CIMC interface to the Enterprise Interface default gateway.
The problem is adding the CIMC in the Catalyst Center (System->Settings->System Health) to manage the Catalyst Center hardware from the Catalyst Center. I cannot delete the current entry and I cannot change the Catalyst Center Address. which is still the old Management IP Address (10.10.10.131)

Unfortunately, this is not something that we can change. If the internal routing in Catalyst Center shows the enterprise port, then when we run through the config wizard, it should change this value automatically. If it is not, then that would seem like a defect to me. This info is going to be auto generated based on the route Catalyst Center sees to accessing the Cisco IMC based on the IP it is getting from the communication internally with the UCS hardware.