One of Enterprise Manager Ops Center's core functionalities is to be able to provision the OS to bare metal servers. If the network you are provisioning across is connected to one of the onboard ports (on the first onboard network chip), all is well and provisioning will work as expected. This would be the case for 95% plus of all customers, but if you are trying to provision across a network that is connected to a port on a card in an expansion slot (or a second onboard network chip), your provisioning job will fail due to the incorrect MAC address being set in the JET/AI/Kickstart server. If you are one of the people who has hit this issue, please read on. If you are provisioning over an onboard NIC port, stop reading now and happy OS provisioning.
When Ops Center discovers the ILOM (ALOM/XSCF and all the other various LOMs) of a server, there are only certain pieces of information that can be collected from the LOM while the OS is running. We maintain a policy of creating as little impact as possible during discovery, so we do not force you to shutdown the OS during discovery.
Information we can collect:
- the number of network interfaces
- the MAC address of the first network interface (port)
Information we can NOT collect:
- the MAC address of all the other network interfaces (ports)
Since the LOM only provides the first MAC address, Ops Center must calculate the MAC addresses of the remaining network interfaces. Ops Center will get the MAC addresses for the onboard NICs correct but its calculated MAC addresses will be wrong for any NICs not on the first onboard network chip.
If we have an example system that has 4 onboard network ports (on the motherboard) and an expansion network card in the PCI-E/X slot with an additional 4 network ports, Ops Center's view of that server, based on the information from the LOM, would not match the physical server.
||Ops Center's Mac Address - Calculated ( from LOM)
||Actual Mac Adress
|Number of Network interfaces
|Mac Address for interface 0 (onboard)
|Mac Address for interface 1 (onboard)
|Mac Address for interface 2 (onboard
|Mac Address for interface 3 (onboard
|Mac Address for interface 4 (PCI-E/X card)
|Mac Address for interface 5 (PCI-E/X card)
|Mac Address for interface 6 (PCI-E/X card)
|Mac Address for interface 7 (PCI-E/X card)
You can confirm that the Mac addresses for an expansion network card has been calculated, by looking at the Network tab in the BUI for the LOM object.
You can see the displayed MAC addresses for GB_4 and GB_5 are just a simple increment of 1 from that of GB_3 which should not be the case as GB_4 and GB_5 are on a PCI-E/X expansion card. While most Oracle(Sun) servers have 4 on-board network interfaces of the same type, some servers may have 2 x 1GBit interfaces and 2 x 10Gbit interfaces. In this case, only the first on-board network interfaces will display the correct MAC addresses.
It should be noted that if you have discovered the LOM and discovered the running operation system, Ops Center will have been able to identify the correct MAC addresses for all the network interfaces as it combines the information gathered from the LOM and the Operating System to display the full picture (correct values). Unfortunately, you can not rely on these when re-provisioning, as part of the OSP job will delete the OS object (we are re-provisioning it after all) and the cached values for the MAC address may expire before the JET/AI/Kickstart server is configured.
If you were to provision across net0, net1, net2, or net3 all would work well, but if you selected net4 or above for provisioning, the job would fail due to a timeout in the "Monitor OS Installation" task as the Jet/AI/Kickstart server would have been configured with the wrong MAC address and so it would have not responded to the OSP request. Please note that a misidentified MAC address is not the only possible cause of a timeout in the "Monitor OS Installation" task. This error only indicates that some step of the OS provisioning has failed and can be caused by a number of different issues.
There are 2 ways of provisioning to secondary network interfaces
1) Use the MAC address method (simplest method - only available in 12.2.0+)
In Ops Center 12.2.0, we introduced an option to specify the MAC address to provision across directly in the BUI. When running the "Install Server" Action/Wizard, the "Boot Interface Resource Assignments" page has a check-box [Identify Network Interface by MAC Address]. Selecting this check-box will change the wizard from using netX interface names that rely on the discovered MAC address, to letting you manually enter the MAC address. This entered MAC address is used to setup the JET/AI/Kickstart server and is used to interrogate the OBP of the server to workout the netX interface that is required for wanboot.
It is as easy as that and your provisioning job will progress as normal.
2) Overload the MAC address before provisioning (the way we did it before we had method #1)
Assuming you have already discovered and managed the systems LOM, you can overload (update) the discovered/calulated network interface MAC addresses.
In the BUI, select "Assets" ==> "All Assets" ==> "Add Assets"
then choose "Manually declared server to be a target of OS provisioning"
While this could declare multiple servers using an XML file, in this example, we will just be doing a single server. This wizard normally lets us declare a server network interfaces but as some of the MAC addresses we will be declaring are already part of an existing discovered server LOM, Ops Center will identify the overlaping MAC address and merge this data with the existing server. The matching interfaces will stay the same but the new MAC addresses will overload (replace) the incorrect addresses.
Select Declare a single server, then click the [Green Plus] icon
Enter the port name [GB_X] and the actual MAC address.
Repeat this for all the interfaces, up to and including the one you want to provision across.
Do not skip any interfaces as the interface numbering is based on the order the entries are stored in the database.
When you have entered all required interfaces, you then have to fill in the server details.
Once completed, click the [Declare Asset] button and wait for the job to complete. Normally, this will just take a few seconds.
You can check in the BUI that the updated MAC addresses have been applied.
Now, just run your provisioning job as per normal and the correct MAC address will be configured in the JET/AI/Kickstart server.
As you can see, if you have updated your Enterprise Controller to Ops Center 12.2.0 or higher, option #1 is the simpler method.
All the best with your OS provisioning,