IMM UCSX - IPMI BMC MAC?

[KRIS PATE]

I am trying to setup IPMI so that the blade is automatically powered down when utilization is low. 

In the past this was easy to do via UCSM, but I can't figure out where the BMC MAC address is for the Blade in Intersight. 

I am looking at the server and it shows me the Management IP, the Serial Number and the MAC Address field is blank. 

I tried grabbing the MAC address via another device on the same subnet (ARP table), but when I enter that in vCenter it says that the IP and MAC don't match.   I logged into the CIMC of the blade via the FI (connect cimc 1/1) but when I run the "network" command I get a lot of interfaces, but none of them match the IP address of the blade (OOB). 

Is this not supported on IMM UCSX?  Do I need to go back to UCSM? 

The more I dive into IMM the more I realize it isn't a fully baked product yet. 

[Derek Szolucha]

Hi @KRIS PATE 

I am not using OOB IP pool for blades vKVM interfaces, I am using IB IP Pool. I am not sure if steps listed below will be helpful in your case.
Steps:

SSH to OOB mgmt IP of FI  and run CLI listed below:
connect cimc 1/1                                   (chassis/blade)
network

You will find HWaddr under second bond ending with VLAN ID of you IB vKVM pool i.e. bond0.10

example:

[ help ]# network
bond0 Link encap:Ethernet HWaddr AA:BB:CC:00:11:22
inet6 addr: XXXXXX/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1496 Metric:1
RX packets:1446456 errors:0 dropped:0 overruns:0 frame:0
TX packets:487922 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:107343626 (102.3 MiB) TX bytes:47912066 (45.6 MiB)

bond0.10 Link encap:Ethernet HWaddr AA:BB:CC:00:11:22
inet addr:X.X.X.X Bcast:0.0.0.0 Mask:255.255.254.0
inet6 addr: XXXXXXX/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1496 Metric:1
RX packets:462385 errors:0 dropped:0 overruns:0 frame:0
TX packets:223918 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:29842169 (28.4 MiB) TX bytes:22085094 (21.0 MiB)

[KRIS PATE]

I don't see a bond interface.  Also I don't seen an interface with the OOB IP address of my blade -  10.34.18.206

There isn't a VLAN attached to the mgmt interface, because I am using OOB and not In-band. 

eth0 Link encap:Ethernet HWaddr 4A:74:10:F5:BA:01
inet6 addr: fe80::4874:10ff:fef5:ba01/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21570963 errors:0 dropped:0 overruns:0 frame:0
TX packets:18938233 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1030019027 (982.3 MiB) TX bytes:18446744073093318127 (167772 15.9 TiB)
Interrupt:50

eth0.1 Link encap:Ethernet HWaddr 4A:74:10:F5:BA:01
inet addr:127.3.0.1 Bcast:127.3.0.255 Mask:255.255.255.0
inet6 addr: fe80::4874:10ff:fef5:ba01/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14378013 errors:0 dropped:1 overruns:0 frame:0
TX packets:16035066 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1560198049 (1.4 GiB) TX bytes:15366194987 (14.3 GiB)

eth0.4043 Link encap:Ethernet HWaddr 4A:74:10:F5:BA:01
inet6 addr: fe80::4874:10ff:fef5:ba01/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:670961 errors:0 dropped:161520 overruns:0 frame:0
TX packets:508891 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:216714262 (206.6 MiB) TX bytes:77740863 (74.1 MiB)

eth0.4044 Link encap:Ethernet HWaddr 4A:74:10:F5:BA:01
inet6 addr: fe80::4874:10ff:fef5:ba01/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6521974 errors:0 dropped:0 overruns:0 frame:0
TX packets:2319405 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7541046686 (7.0 GiB) TX bytes:1109015272 (1.0 GiB)

eth1 Link encap:Ethernet HWaddr 4A:74:10:F5:BA:00
inet6 addr: fe80::4874:10ff:fef5:ba00/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:32094110 errors:0 dropped:0 overruns:0 frame:0
TX packets:28203620 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1996414019 (1.8 GiB) TX bytes:1148926409 (1.0 GiB)
Interrupt:49

eth1.1 Link encap:Ethernet HWaddr 4A:74:10:F5:BA:00
inet addr:127.4.0.1 Bcast:127.4.0.255 Mask:255.255.255.0
inet6 addr: fe80::4874:10ff:fef5:ba00/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29714154 errors:0 dropped:1 overruns:0 frame:0
TX packets:26986661 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3639488487 (3.3 GiB) TX bytes:18109825935 (16.8 GiB)

eth1.4043 Link encap:Ethernet HWaddr 4A:74:10:F5:BA:00
inet6 addr: fe80::4874:10ff:fef5:ba00/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:609 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:42766 (41.7 KiB)

eth1.4044 Link encap:Ethernet HWaddr 4A:74:10:F5:BA:00
inet addr:127.5.1.1 Bcast:0.0.0.0 Mask:255.255.0.0
inet6 addr: fe80::4874:10ff:fef5:ba00/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2379935 errors:0 dropped:0 overruns:0 frame:0
TX packets:1215740 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2202573692 (2.0 GiB) TX bytes:217286762 (207.2 MiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.255.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:74728426 errors:0 dropped:0 overruns:0 frame:0
TX packets:74728426 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:35749578095 (33.2 GiB) TX bytes:35749578095 (33.2 GiB)

[Derek Szolucha · Accepted solution]

Hi Kris

I have tested blade OOB IPs in my LAB. 
Short answer. Your blade MAC address is listed under CIMC eth0 (FIA) OR eth1 (FIB)
You can check it with FI CLI:
connect cimc 1/1
network
Search for:
eth0 Link encap:Ethernet HWaddr 4A:74:10:F5:BA:01
eth1 Link encap:Ethernet HWaddr 4A:74:10:F5:BA:00

To identify which OOB CIMC MAC  is active (eth0 or eth1) you can check it at FI level - FI CLI - show mgmt-ip-tables.
Search for FI OOB MGMT IP in pre-routing table - chain pre-routing.

In my case FI-B was hosting pre-routing table w/ FI mgmt OOB IP, hence eth1 MAC is active, eth1 post routing IP 127.40.1.2 (screenshot)

CIMC eth to FI mapping:
FI-A -> CIMC eth0
FI-B -> CIMC eth1

It is not super simple, but at least you can get CIM OOB IP MAC.

Derek

[KRIS PATE]

Hi Derek,

     That worked.   Thanks for testing that out.  Originally we tried the MAC address associated with eth0 and when it didn't work didn't think to try the MAC associated with eth1. 

I was on a call with TAC yesterday and we tried to find a way to get the same info via the API, but it doesn't look like that is currently possible.  Which is probably why the GUI doesn't show it already. 

There will need to be a new feature implemented. 

Kris

[Derek Szolucha]

Hi Chris, I have requested for it. Please ping your account team to request this feature as well, we can join the forces