![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||
Solution Type Problem Resolution Sure Solution 1539729.1 : Error "set: Unable to configure network" when trying to configure/change ILOM network parameters
In this Document
Created from <SR 3-6965823781> Applies to:SPARC T4-4 - Version Not Applicable to Not Applicable [Release N/A]SPARC T4-1 - Version Not Applicable to Not Applicable [Release N/A] SPARC T4-2 - Version Not Applicable to Not Applicable [Release N/A] SPARC T3-1 - Version Not Applicable to Not Applicable [Release N/A] SPARC T3-2 - Version Not Applicable to Not Applicable [Release N/A] Information in this document applies to any platform. SymptomsWhen configuring or changing ILOM network interface configuration, one may get the following error:
set: Unable to configure network
CauseThe IP address parameters informed may be invalid or incorrect. For example, selecting IP addresses from different subnets for the parameters ipaddress and ipgateway will produce such error: -> set /SP/network pendingipaddress=10.10.13.93
set 'pendingipaddress' to '10.10.13.93' -> set /SP/network pendingipnetmask=255.255.255.0 set 'pendingipnetmask' to '255.255.255.0' -> set /SP/network pendingipgateway=10.10.12.7 set 'pendingipgateway' to '10.10.12.7' -> set /SP/network commitpending=true set: Unable to configure network -> show /SP/network Targets: interconnect ipv6 test Properties: commitpending = (Cannot show property) dhcp_server_ip = none ipaddress = 172.16.2.26 ipdiscovery = static ipgateway = 172.16.2.254 ipnetmask = 255.255.255.0 macaddress = 00:21:28:FA:C5:EB managementport = /SYS/MB/SP/NETMGMT outofbandmacaddress = 00:21:28:FA:C5:EB pendingipaddress = 10.10.13.93 pendingipdiscovery = static pendingipgateway = 10.10.12.7 pendingipnetmask = 255.255.255.0 pendingmanagementport = /SYS/MB/SP/NETMGMT sidebandmacaddress = 00:21:28:FA:C5:EA state = enabled Notice from example above that the netmask used (255.255.255.0) causes ipaddress and ipgateway belong to different subnets, hence the configuration fails. SolutionIn order to have network changes applied, select valid, consistent values for ipaddress and ipgateway within the same subnet address range. You can find additional information from Oracle documentation: Attachments This solution has no attachment |
||||||||||||||||
|