If you plan to connect to the SP through its NET MGT port (through the dongle's RJ-45 connector), the SP must have a valid IP address.
By default, the server module is configured to obtain an IP address from DHCP services in your network. If the network your server module is connected to does not support DHCP for IP addressing, perform this procedure.
To configure the server module to support DHCP, refer to the Oracle ILOM documentation.
->set /SP/network pendingipdiscovery=static Set 'pendingipdiscovery' to 'static'
->set /SP/network pendingipaddress=service-processor-IPaddr Set 'pendingipaddress' to 'service-processor-IPaddr'
-> set /SP/network pendingipgateway=gateway-IPaddr Set 'pendingipgateway' to 'gateway-IPaddr'
-> set /SP/network pendingipnetmask=255.255.255.0 Set 'pendingipnetmask' to '255.255.255.0'
This example uses 255.255.255.0 to set the netmask. Your network environment subnet might require a different netmask. Use a netmask number most appropriate to your environment.
-> show /SP/network /SP/network Targets: Properties: commitpending = (Cannot show property) dhcp_server_ip = xxx.xxx.xxx.xxx ipaddress = xxx.xxx.xxx.xxx ipdiscovery = dhcp ipgateway = xxx.xxx.xxx.xxx ipnetmask = 255.255.255.0 macaddress = 00:21:28:C1:6E:C5 managementport = /System/MB/SP/NETMGMT outofbandmacaddress = 00:21:28:C1:6E:C5 pendingipaddress = service-processor-IPaddr pendingipdiscovery = static pendingipgateway = gateway-IPaddr pendingipnetmask = 255.255.255.0 pendingmanagementport = /System/MB/SP/NETMGMT sidebandmacaddress = 00:21:28:C1:6E:C4 state = enabled
-> set /SP/network commitpending=true Set 'commitpending' to 'true'