From: rob.de.langhe@belgacom.be
Date: Wed Apr 06 2005 - 07:12:32 EDT
Hi,
we have an urgent problem that I can't get resolved:
a V440 on a new network segment needs to be Jumpstarted with Solaris-9,
it gets (using TFTP) correctly the very initial boot image from a
boot-server (RARP, BOOTP) on the same segment, does some BOOTP requests
to that same boot-server which returns properly the gateway's IP-address
and the NFS-server's IP-address plus directory path on it where the
initial Solaris must be retrieved from.
Then it hangs, sending out ARP requests to 255.255.255.255 to find out
the MAC-address for the NFS-server's IP-address :
This machine's subnet is 45.217.2.0/23, so the range is from 45.217.2.0
till 45.217.3.255
The boot-server in this subnet is 45.217.2.49
This server gets IP-address 45.217.2.110
The gateway for this subnet is 45.217.2.33
The NFS-server has IP-address 45.216.114.42
{1} ok boot /pci@1c,600000/network@2:speed=100,duplex=full - install
Boot device: /pci@1c,600000/network@2:speed=100,duplex=full File and
args: - install
/pci@1c,600000/network@2: 100 Mbps full duplex link up
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
4000 /pci@1c,600000/network@2: 100 Mbps full duplex link up
Requesting Ethernet address for: 45.216.114.42
panic - boot: Could not mount filesystem.
Program terminated
{1} ok boot /pci@1c,600000/network@2:speed=100,duplex=full - install
A network sniffer has captured the packets that are sent out during
"Requesting Ethernet address for: 45.216.114.42", and they are not
directed to the gateway, but generic ARP requests.
This indicates to me that the boot-image is not using the netmask (which
it receives from the local boot server, i.e. 255.255.254.0) to determine
if that NFS-server is on a remote subnet or if it belongs to this same
subnet. It is maybe not using any netmask, and defaulting to the
RFC-category for the 45.*.*.* ranges, being a class-A subnet (mask
255.0.0.0)
There is a separate discussion that happened (including by myself a few
weeks ago) about the initial Solaris O/S which incorrectly gets the
netmask of the NFS-server.
This server is not yet in that stage. Here it is the boot-image itself
that fails to use a proper netmask.
On another subnet, we have exactly the same boot-image sitting on a
boot-server, and there a 280R uses correctly the local gateway to
contact this same NFS-server accross it subnet boundaries.
Is there something different in behaviour of 280R compared to V440 ?
The bootimage is "inetboot.SUN4U.Solaris_9-1", 152376 bytes, "sum" on
this file returns 3662 and 298.
Searched the web for 2 days, found nothing about this particular
problem...
Rob
**** DISCLAIMER ****
http://www.belgacom.be/maildisclaimer
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:30:29 EDT