Anyone gotten X4100 SP to work with static IP?
IN <a href="http://www.sun.com/products-n-solutions/hardware/ docs/html/8" target="_blank"> http://www.sun.com/products-n-solutions/hardware/docs/html/8</a> 19-1160-11/cli_tasks.html
7.6.2.3 Examples
To change the IP address for the service processor, type:
set /SP/network ipaddress=192.168.77.21 commitpending=true
should be
set /SP/network pendingipaddress=192.168.77.21 commitpending=true
None of these commands work:
-> set pendingipaddress=10.10.12.87 pendingipgateway=10.10.12.1
pendingipnetmask=255.255.255.0 commitpending=true
Set 'pendingipaddress' to '10.10.12.87'
Set 'pendingipgateway' to '10.10.12.1'
Set 'pendingipnetmask' to '255.255.255.0'
/sbin/ifdown: interface eth0 not configured
route: SIOC[ADD|DEL]RT: Invalid argument
Failed to bring up eth0.
10 10 12 87
/sbin/ifdown: interface eth0 not configured
route: SIOC[ADD|DEL]RT: Invalid argument
Failed to bring up eth0.
10 10 12 1
/sbin/ifdown: interface eth0 not configured
255 255 255 0
Set 'commitpending' to 'true'
Plus the settings do not survive across resets.
Do I have a dead BIOS battery or something? The preposterous badness of the hardware and documentation is baffling. We are on the verge of sending the boxes back for a refund.
[1741 byte] By [
wsanders1] at [2007-11-25 22:40:58]
# 1
Did you try using the web GUI?
These were our experiences with a X4200:
after unpacking the server, the BIOS was unable to read out the SP IP .. if there was any configured by factory
setting static IP from BIOS is not possible
we had no serial console available
thus, only option was DHCP
we ended up connecting the new box to a DHCP server to assign it a static DHCP IP
after that, we used the Web GUI to configure a static IP, which worked fine
also, the BIOS shows the IP and the IP survives resets and full shutdowns.
afterwards, we twice reconfigured the static IP over the Web gui
first time worked fine
second time, the SP was rendered unreachable (first) .. it reappeared _hours_ later with the _correct_ IP.
maybe this was because we were installing solaris while we were reconfiguring the IP of the SP. don't know. it was quit a shock since the server already was in the datacenter many many miles away. thus: configure it and leave it.
besides these initial wrinkles, the ILOM is really great .. redirection works .. even local CD/DVD redirection ..
whats left are issues with keyboard map (local PC has german keys).
# 3
I issue the command:
set /SP/network pendingipdiscovery=dhcp pendingipaddress=10.10.12.87
pendingipnetmask=255.255.255.0 pendingipgateway=10.10.12.1 commitpending=true
I get a bunch of junk:
Set 'pendingipdiscovery' to 'dhcp'
Set 'pendingipaddress' to '10.10.12.87'
Set 'pendingipnetmask' to '255.255.255.0'
Set 'pendingipgateway' to '10.10.12.1'
/sbin/ifdown: interface eth0 not configured
SIOCSIFNETMASK: Cannot assign requested address
SIOCSIFBRDADDR: Cannot assign requested address
Failed to bring up eth0.
10 10 12 87
/sbin/ifdown: interface eth0 not configured
SIOCSIFNETMASK: Invalid argument
Failed to bring up eth0.
/sbin/ifdown: interface eth0 not configured
# 4
My understanding of the matter is this:
The SP is a Linux/Motorola CPU based "2nd Computer" on-board, which runs a DHCP client to request a dynamic IP.
The AMI BIOS is run by the "main computer" and is only able to _read_ the IP assigned to the "SP computer".
# 5
May sound trivial, but have you connected the right ethernet port?
The X4200 has 5 ethernet ports at the back: 4 x GBit Ethernet port - those are arranged 2x2 closely together, and a somewhat separated from those 4 is a 5th one - the 10/100MBit managment port which is the one connected to the SP. Obviously, you must connect that last one to your DHCP server.
If your SP comes up with an IP <A> you don't like, but you still at least know which IP (from snooping, from the serial console or from checking via AMI BIOS) .. why not try pointing your browser at http://<A> and try setting the IP via the Web GUI?
Also: it might be that the SP configuration got somehow scrambled while trying again and again to configure it. According to the server manual, there is a jumper on the mainboard to reset the SP config to the factory default. WARNING: I haven't used this jumper and I suspect setting it is not riskless ... really: don't blame me if you choose to reset the SP config via the jumper and this screws up your box completely. I'm not a Sun engineer ..
just my 2cts
cheers
poiuz23
# 6
Whaddya know - a fifth ethernet interface wedged in there. OK, I'm going to take the rest of the day off at the beach and give Sun a break from my ranting. Static address assignment works (it still throws an invalid argument error but succeeds) The interface cannot be configured until it has a link, that threw me off.
The messages about "eth0" from the ILOM SP - of course that is the ILOM's eth0 and not the mainboard's eth0.
# 7
>>>> second time, the SP was rendered unreachable (first) .. it reappeared _hours_ later with the _correct_ IP.
Looks like the ILOM SP crashes a lot. I disconnected the network interface for a little bit and reconnected. I was presented with the HTTPS login page, but the ILOM SP crashed when I typed my username & password. It's pingable, but it's not accessible via the serial port now either.
