Before You Begin:
Sideband management is supported on most Oracle servers. However, to verify whether a server supports sideband management, refer to the server administration guide or the product release notes.
To maintain the most reliable and secure environment for Oracle ILOM, the sideband management port on the server must always be connected to an internal trusted network or dedicated secure management or private network.
The SP Management Port property for Oracle ILOM is configurable from the Oracle ILOM CLI and web interface. It is also configurable for x86 servers from the BIOS Setup Utility
If you modify the Management Port property through Oracle ILOM, the following requirements apply:
A management connection to Oracle ILOM should already be established. For instructions, see either:
You should have logged in to Oracle ILOM. For instructions, see Logging In to Oracle ILOM Server SP or CMM.
The default root account or a user account with Admin (a) role privileges is required in Oracle ILOM to modify the Management Port property.
To configure a sideband management connection to Oracle ILOM, follow these steps:
For instructions, refer to the cabling section in the server or blade system installation guide.
In the Management Port list box, select the active physical data port name (NET0, NET1, NET2, or NET3), then click Save.
set /SP/network pendingmanagementport=/SYS/MB/NETn commitpending=true
n is the physical active data port number (0, 1, 2, or 3) on the server.
In the LAN Configuration menu, set the Management Port setting to the physical active data port name (NET0, NET1, NET2, or NET3), then click Commit for the change to take effect.
This section provides general network connectivity issues for you to consider when using a sideband management connection to Oracle ILOM:
In-chip connectivity between the server SP and the host operating system might not be supported by the on-board host Gigabit Ethernet controller. If this condition occurs, use a different port or route to transmit the traffic between the source and destination targets instead of using L2 bridging/switching.
Server host power cycles might cause a brief interruption of network connectivity for server Gigabit Ethernet ports (NET 0, 1, 2, 3) that are configured for sideband management. If this condition occurs, configure the adjacent switch/bridge ports as host ports.
If the Ethernet data ports on the server are configured as switch ports and participate in the Spanning Tree Protocol (STP), you might experience longer outages due to spanning tree recalculations.