Collecting the BMC MAC Addresses

This guide will detail how to collect BMC MAC addresses from an HPE Cray EX system with configured switches. The BMC MAC address is the exclusive, dedicated LAN for the onboard BMC.

Prerequisites

  • There is a configured switch with SSH access or unconfigured with COM access (Serial Over LAN/DB-9).
  • A file is available to record the collected BMC information.

Procedure

  1. (pit#) Start a session on the leaf-bmc switch, either using SSH or a USB serial cable.

    See Connect to Switch over USB-Serial Cable, if wanting to use that option.

    NOTE These IP addresses are examples; 10.X.0.4 may not match the setup.

    • For bare-metal switches, log in over the MTL network:

      ssh admin@10.1.0.4
      
    • For configured switches, log in to the leaf switch:

      ssh admin@10.254.0.4
      
  2. (sw-leaf-001) Display the MAC addresses for the BMC ports (if known).

    If they exist on the same VLAN, then dump the VLAN to get the MAC addresses. In order to find the ports of the BMCs, cross-reference the HMN tab of the SHCD file.

    NOTE Reference the CLI for more information (press ? or tab).

    • DellOS 10

      show mac address-table vlan 4
      

      The output should look similar to:

      VlanId Mac Address  Type        Interface
      4 00:1e:67:98:fe:2c dynamic     ethernet1/1/11
      4 a4:bf:01:38:f0:b1 dynamic     ethernet1/1/27
      4 a4:bf:01:38:f1:44 dynamic     ethernet1/1/25
      4 a4:bf:01:48:1e:ac dynamic     ethernet1/1/28
      4 a4:bf:01:48:1f:70 dynamic     ethernet1/1/31
      4 a4:bf:01:48:1f:e0 dynamic     ethernet1/1/26
      4 a4:bf:01:48:20:03 dynamic     ethernet1/1/30
      4 a4:bf:01:48:20:57 dynamic     ethernet1/1/29
      4 a4:bf:01:4d:d9:9a dynamic     ethernet1/1/32
      
    • Aruba AOS-CX

      show mac-address-table vlan 4
      

      The output should look similar to:

      MAC age-time            : 300 seconds
      Number of MAC addresses : 21
      
      MAC Address          VLAN     Type                      Port
      --------------------------------------------------------------
      b4:2e:99:df:f3:61    4        dynamic                   1/1/36
      b4:2e:99:df:ec:f1    4        dynamic                   1/1/35
      b4:2e:99:df:ec:49    4        dynamic                   1/1/33
      94:40:c9:37:04:84    4        dynamic                   1/1/26
      94:40:c9:35:03:06    4        dynamic                   1/1/27
      94:40:c9:37:0a:2a    4        dynamic                   1/1/29
      94:40:c9:37:67:60    4        dynamic                   1/1/43
      94:40:c9:37:67:80    4        dynamic                   1/1/37
      94:40:c9:37:77:26    4        dynamic                   1/1/31
      94:40:c9:37:77:b8    4        dynamic                   1/1/28
      94:40:c9:37:87:5a    4        dynamic                   1/1/30
      94:40:c9:37:f9:b4    4        dynamic                   1/1/25
      b4:2e:99:df:eb:c1    4        dynamic                   1/1/34
      
  3. Ensure that the management NCNs are present in the ncn_metadata.csv file.

    The output from the previous show mac address-table command will display information for all management NCNs that do not have an external connection for their BMC, such as ncn-m001. The BMC MAC address for ncn-m001 will be collected in the next step, as this BMC is not connected to the system’s management network like the other management nodes.

    Fill in the Bootstrap MAC, Bond0 MAC0, and Bond0 MAC1 columns with a placeholder value, such as de:ad:be:ef:00:00, as a marker that the correct value is not in this file yet.

    IMPORTANT NCNs of each type (master, storage, and worker) are grouped together in the file and are listed in descending numerical order within their group (for example, ncn-s003 is listed directly before ncn-s002).

    Xname,Role,Subrole,BMC MAC,Bootstrap MAC,Bond0 MAC0,Bond0 MAC1
    x3000c0s9b0n0,Management,Storage,a4:bf:01:38:f1:44,de:ad:be:ef:00:00,de:ad:be:ef:00:00,de:ad:be:ef:00:00
    x3000c0s8b0n0,Management,Storage,a4:bf:01:48:1f:e0,de:ad:be:ef:00:00,de:ad:be:ef:00:00,de:ad:be:ef:00:00
    x3000c0s7b0n0,Management,Storage,a4:bf:01:38:f0:b1,de:ad:be:ef:00:00,de:ad:be:ef:00:00,de:ad:be:ef:00:00
    
                                     ^^^^^^^^^^^^^^^^^
                                     BMC MAC address
    

    NOTE The column heading line must match that shown above in order for csi to parse it correctly.

  4. (pit#) Collect the BMC MAC address information for the PIT node.

    The PIT node BMC is not connected to the switch like the other management nodes.

    ipmitool lan print | grep "MAC Address"
    

    Example output:

    MAC Address             : a4:bf:01:37:87:32
    

    NOTE An Intel node needs to use ipmitool lan print 3 instead of the above command.

  5. Add this information for ncn-m001 to the ncn_metadata.csv file.

    There should be ncn-m003, then ncn-m002, and this new entry for ncn-m001 as the last line in the file.

    x3000c0s1b0n0,Management,Master,a4:bf:01:37:87:32,de:ad:be:ef:00:00,de:ad:be:ef:00:00,de:ad:be:ef:00:00
                                    ^^^^^^^^^^^^^^^^^
                                    BMC MAC address
    
  6. Verify that the ncn_metadata.csv file has a row for every management node in the SHCD.

    NOTE There may be placeholder entries for some MAC addresses.

    Below is a sample file showing storage nodes 3, 2, and 1, then worker nodes 3, 2, and 1, and finally master nodes 3, 2, and 1, with valid BMC MAC addresses, but placeholder value de:ad:be:ef:00:00 for the Bootstrap MAC, Bond0 MAC0, and Bond0 MAC1.

    Xname,Role,Subrole,BMC MAC,Bootstrap MAC,Bond0 MAC0,Bond0 MAC1
    x3000c0s9b0n0,Management,Storage,a4:bf:01:38:f1:44,de:ad:be:ef:00:00,de:ad:be:ef:00:00,de:ad:be:ef:00:00
    x3000c0s8b0n0,Management,Storage,a4:bf:01:48:1f:e0,de:ad:be:ef:00:00,de:ad:be:ef:00:00,de:ad:be:ef:00:00
    x3000c0s7b0n0,Management,Storage,a4:bf:01:38:f0:b1,de:ad:be:ef:00:00,de:ad:be:ef:00:00,de:ad:be:ef:00:00
    x3000c0s6b0n0,Management,Worker,a4:bf:01:48:1e:ac,de:ad:be:ef:00:00,de:ad:be:ef:00:00,de:ad:be:ef:00:00
    x3000c0s5b0n0,Management,Worker,a4:bf:01:48:20:57,de:ad:be:ef:00:00,de:ad:be:ef:00:00,de:ad:be:ef:00:00
    x3000c0s4b0n0,Management,Worker,a4:bf:01:48:20:03,de:ad:be:ef:00:00,de:ad:be:ef:00:00,de:ad:be:ef:00:00
    x3000c0s3b0n0,Management,Master,a4:bf:01:48:1f:70,de:ad:be:ef:00:00,de:ad:be:ef:00:00,de:ad:be:ef:00:00
    x3000c0s2b0n0,Management,Master,a4:bf:01:4d:d9:9a,de:ad:be:ef:00:00,de:ad:be:ef:00:00,de:ad:be:ef:00:00
    x3000c0s1b0n0,Management,Master,a4:bf:01:37:87:32,de:ad:be:ef:00:00,de:ad:be:ef:00:00,de:ad:be:ef:00:00
    
  7. (pit#) Run pit-init to setup the PIT (at least part way).

    Ignore errors regarding site-init (because it may not exist at this time).

    NOTE This assumes all other topology files are present in $PITDATA/prep from Generate Topology Files.

    /root/bin/pit-init.sh
    
  8. Proceed to Collecting NCN MAC Addresses.