| Asset ID: |
1-72-1592805.1 |
| Update Date: | 2013-10-23 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1592805.1
:
Exadata: Cannot Ping or Connect ILOM Network Interface With Http Protocol
| Related Categories |
- PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Exadata>DB: Exadata_EST
|
Created from <SR 3-7923495911>
Applies to:
Exadata X3-2 Hardware - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Symptoms
Customer cannot connect to ILOM web interface.
Cause
The IP and gateway of the ILOM was wrongly set.
Cause can be justified by reviewing the command output.
The IP address and the Gateway is different for both the nodes.
The setup is correct on node 1.
[root@exadb01 ~]# ipmitool lan print
Set in Progress : Set Complete
Auth Type Support : NONE MD2 MD5 PASSWORD
Auth Type Enable : Callback : MD2 MD5 PASSWORD
: User : MD2 MD5 PASSWORD
: Operator : MD2 MD5 PASSWORD
: Admin : MD2 MD5 PASSWORD
: OEM :
IP Address Source : Static Address
IP Address : 192.168.50.70
Subnet Mask : 255.255.255.192
MAC Address : 00:10:e0:29:fa:f8
SNMP Community String : public
IP Header : TTL=0x00 Flags=0x00 Precedence=0x00 TOS=0x00
BMC ARP Control : ARP Responses Disabled, Gratuitous ARP Disabled
Gratituous ARP Intrvl : 5.0 seconds
Default Gateway IP : 192.168.50.65
Default Gateway MAC : 00:00:00:00:00:00
Backup Gateway IP : 0.0.0.0
Backup Gateway MAC : 00:00:00:00:00:00
802.1q VLAN ID : Disabled
802.1q VLAN Priority : 0
RMCP+ Cipher Suites : 2,3,0
Cipher Suite Priv Max : XXXXXXXXXXXXXXX
: X=Cipher Suite Unused
: c=CALLBACK
: u=USER
: o=OPERATOR
: a=ADMIN
: O=OEM
[root@exadb01 ~]#
The incorrect setup on node 2.
[root@exadb02 ~]# ipmitool lan print
Set in Progress : Set Complete
Auth Type Support : NONE MD2 MD5 PASSWORD
Auth Type Enable : Callback : MD2 MD5 PASSWORD
: User : MD2 MD5 PASSWORD
: Operator : MD2 MD5 PASSWORD
: Admin : MD2 MD5 PASSWORD
: OEM :
IP Address Source : Static Address
IP Address : 192.168.1.109
Subnet Mask : 255.255.255.0
MAC Address : 00:10:e0:29:a0:a4
SNMP Community String : public
IP Header : TTL=0x00 Flags=0x00 Precedence=0x00 TOS=0x00
BMC ARP Control : ARP Responses Disabled, Gratuitous ARP Disabled
Gratituous ARP Intrvl : 5.0 seconds
Default Gateway IP : 192.168.1.8
Default Gateway MAC : 00:00:00:00:00:00
Backup Gateway IP : 0.0.0.0
Backup Gateway MAC : 00:00:00:00:00:00
802.1q VLAN ID : Disabled
802.1q VLAN Priority : 0
RMCP+ Cipher Suites : 2,3,0
Cipher Suite Priv Max : XXXXXXXXXXXXXXX
: X=Cipher Suite Unused
: c=CALLBACK
: u=USER
: o=OPERATOR
: a=ADMIN
: O=OEM
[root@exadb02 ~]#
Solution
Correct the IP address and Gateway matching with the working configuration.
Login into the DB node using ssh and then connect to ILOM using ipmitool:
[root@exadb02 ~]# ipmitool sunoem cli
Connected. Use ^D to exit.
->
Once logged in, execute the following commands to set the correct values.
-> cd /SP/network
-> set pendingipaddress=192.168.50.71
-> set pendingipnetmask=255.255.255.192
-> set pendingipgateway=192.168.50.65
-> set commitpending=true
Note - the command will return an error if the gateway is not in the same subnet as the IP address being set.
Use the following command to verify the corect values reported as "ipaddress" "ipdiscovery=static" "ipgateway" "ipnetmask":
-> show /SP/network
...
-> exit
Disconnected.
[root@exadb02 ~]#
Refer to ILOM documentation for additional methods of troubleshooting.
Attachments
This solution has no attachment
