Installadm - network in unreachable

Seems to wanboot ok but then fails to connect to server. What do I need to check?

{0} ok boot net - install

Boot device: /pci@300/pci@1/pci@0/pci@1/network@0  File and args: - install

1G link up

<time unavailable> wanboot info: WAN boot messages->console

<time unavailable> wanboot info: configuring /pci@300/pci@1/pci@0/pci@1/network@0



1G link up
<time unavailable> wanboot progress: wanbootfs: Read 368 of 368 kB (100%)

<time unavailable> wanboot info: wanbootfs: Download complete
Fri Feb 23 09:34:13 wanboot progress: miniroot: Read 249357 of 249357 kB (100%)

Fri Feb 23 09:34:13 wanboot info: miniroot: Download complete

SunOS Release 5.11 Version 11.2 64-bit

Copyright (c) 1983, 2014, Oracle and/or its affiliates. All rights reserved.

strplumb: unable to hold root device: /pci@300/pci@1/pci@0/pci@1/network@0

Remounting root read/write

Probing for device nodes ...

Preparing network image for use

Downloading solaris.zlib

curl arguments --insecure for http://xyz:5555//export/auto_install/solaris11_2-sparc/solaris.zlib



curl: (7) Failed to connect to 172.24.4.146: Network is unreachable

Download resuming in 10 seconds...

Resuming download of http://xyz:5555//export/auto_install/solaris11_2-sparc/solaris.zlib

I am by no means a Solaris expert, but it seems that the system 172.24.4.146 cannot be reached.

Why this is so is open for speculation, a few possible reasons would be:

  • your system has no default route
  • your routing is otherwise wrong/broken.
  • your system has the wrong netmask and thinks it is in the same network as the target system but in fact isn't
  • firewall in between source and target that blocks traffic
  • a simple reason: interface not connected (just because your interface goes up dodesn't mean the NIC is connected to anything)

and probably several dozen more which didn't come to me off te top of my head.

I hope this helps.

bakunin

Turns out not to be a network problem at all.

S7-2 servers only support a certain SRU version and above it seems. Once I upgraded to correct version on AI it worked ok.

Still bit of a dodgy error message though.