T1000 jumpstart

I am trying to jumpstart a t1000 to U3. From what I have seen everything appears to be configured properly. When booting the t1000, it get the IP, and then only posts "Timed out waiting for TFTP reply"

Running a snoop -v on the boot server shows this:

ETHER: -- Ether Header --

ETHER:

ETHER: Packet 443 arrived at 11:00:26.67024

ETHER: Packet size = 64 bytes

ETHER: Destination = 0:14:4f:6e:b7:ce,

ETHER: Source= 0:3:ba:e:67:9,

ETHER: Ethertype = 0800 (IP)

ETHER:

IP:-- IP Header --

IP:

IP:Version = 4

IP:Header length = 20 bytes

IP:Type of service = 0x00

IP: xxx. .... = 0 (precedence)

IP: ...0 .... = normal delay

IP: .... 0... = normal throughput

IP: .... .0.. = normal reliability

IP: .... ..0. = not ECN capable transport

IP: .... ...0 = no ECN congestion experienced

IP:Total length = 50 bytes

IP:Identification = 102

IP:Flags = 0x4

IP: .1.. .... = do not fragment

IP: ..0. .... = last fragment

IP:Fragment offset = 0 bytes

IP:Time to live = 60 seconds/hops

IP:Protocol = 17 (UDP)

IP:Header checksum = b764

IP:Source address = xxxxxxxxxxxx, xxxxxx

IP:Destination address = xxxxxxxxxxxx, xxxxxx

IP:No options

IP:

UDP: -- UDP Header --

UDP:

UDP: Source port = 63058

UDP: Destination port = 32768

UDP: Length = 30

UDP: Checksum = 100C

UDP:

TFTP: -- Trivial File Transfer Protocol --

TFTP:

TFTP: Opcode = 5 (error)

TFTP: Error = 2 (access violation)

TFTP: Error string = "Access violation"

ETHER: -- Ether Header --

ETHER:

ETHER: Packet 444 arrived at 11:00:55.64773

ETHER: Packet size = 64 bytes

ETHER: Destination = ff:ff:ff:ff:ff:ff, (broadcast)

ETHER: Source= 0:14:4f:6e:b7:ce,

ETHER: Ethertype = 0800 (IP)

ETHER:

IP:-- IP Header --

IP:

IP:Version = 4

IP:Header length = 20 bytes

IP:Type of service = 0x00

IP: xxx. .... = 0 (precedence)

IP: ...0 .... = normal delay

IP: .... 0... = normal throughput

IP: .... .0.. = normal reliability

IP: .... ..0. = not ECN capable transport

IP: .... ...0 = no ECN congestion experienced

IP:Total length = 45 bytes

IP:Identification = 35

IP:Flags = 0x0

IP: .0.. .... = may fragment

IP: ..0. .... = last fragment

IP:Fragment offset = 0 bytes

IP:Time to live = 64 seconds/hops

IP:Protocol = 17 (UDP)

IP:Header checksum = b73c

IP:Source address = xxxxxxxxxxxx, xxxxx

IP:Destination address = 255.255.255.255, BROADCAST

IP:No options

IP:

UDP: -- UDP Header --

UDP:

UDP: Source port = 32768

UDP: Destination port = 69 (TFTP)

UDP: Length = 25

UDP: Checksum = F8E0

UDP:

TFTP: -- Trivial File Transfer Protocol --

TFTP:

TFTP: Opcode = 1 (read request)

TFTP: File name = "C0A802EA"

TFTP: Transfer mode = octet

On the boot server, the files created by add_install_client are named: C0A802B9

I tried renaming these, but that didn't effect it. All the information is correct when running the script. Is there some other way of calculating this ID so I can try and find where the problem is?

[3374 byte] By [joshspeera] at [2007-11-26 19:43:07]
# 1

As a follow up, I renamed the boot file to the proper name that the client was searching for. Here is a snoop now:

ETHER: -- Ether Header --

ETHER:

ETHER: Packet 616 arrived at 12:27:36.60037

ETHER: Packet size = 558 bytes

ETHER: Destination = 0:14:4f:6e:b7:ce,

ETHER: Source= 0:3:ba:e:67:9,

ETHER: Ethertype = 0800 (IP)

ETHER:

IP:-- IP Header --

IP:

IP:Version = 4

IP:Header length = 20 bytes

IP:Type of service = 0x00

IP: xxx. .... = 0 (precedence)

IP: ...0 .... = normal delay

IP: .... 0... = normal throughput

IP: .... .0.. = normal reliability

IP: .... ..0. = not ECN capable transport

IP: .... ...0 = no ECN congestion experienced

IP:Total length = 544 bytes

IP:Identification = 8441

IP:Flags = 0x4

IP: .1.. .... = do not fragment

IP: ..0. .... = last fragment

IP:Fragment offset = 0 bytes

IP:Time to live = 60 seconds/hops

IP:Protocol = 17 (UDP)

IP:Header checksum = 94e3

IP:Source address = 192.168.2.231, slashtra

IP:Destination address = 192.168.2.185, nxdev6

IP:No options

IP:

UDP: -- UDP Header --

UDP:

UDP: Source port = 63339

UDP: Destination port = 32768

UDP: Length = 524

UDP: Checksum = 076C

UDP:

TFTP: -- Trivial File Transfer Protocol --

TFTP:

TFTP: Opcode = 3 (data packet)

TFTP: Data block = 1

TFTP: [ 512 bytes of data ]

However the client is repeating:

Timed out waiting for TFTP reply

Could it take a few hours to copy the small boot image?

joshspeera at 2007-7-9 22:25:57 > top of Java-index,Sun Hardware,Servers - General Discussion...
# 2
Have you booted off that image before? if it's a new image, perhaps the directory structure isn't shared properly? or the permissions to the image are not set properly?Don
ddratliffa at 2007-7-9 22:25:57 > top of Java-index,Sun Hardware,Servers - General Discussion...
# 3

This would be the first time, I just setup the boot server. Here are the permissions, and the shares...

# dfshares

RESOURCE SERVER ACCESSTRANSPORT

ultra:/mnt/dvdultra - -

ultra:/backupultra - -

ultra:/tftpbootultra - -

# ls -al /backup/config

total 132

drwxr-xr-x2 rootroot 512 Feb 26 10:48 .

drwxr-xr-x5 rootroot 512 Feb 23 12:54 ..

-rwxr-xr-x1 rootroot59701 Feb 23 13:27 check

-rwxr-xr-x1 rootroot 34 Feb 26 10:48 finish_script

-rwxr-xr-x1 rootroot 245 Feb 23 13:27 profile1

-rwxr-xr-x1 rootroot 41 Feb 26 10:48 rules

-rwxr-xr-x1 rootroot 55 Feb 26 10:40 rules.ok

-rwxr-xr-x1 rootroot 297 Feb 23 13:12 sysidcfg

# ls -al /tftpboot

total 1354

drwxr-xr-x2 rootroot 512 Feb 26 11:41 .

drwxr-xr-x 37 rootroot1024 Feb 21 12:34 ..

lrwxrwxrwx1 rootroot 27 Feb 26 10:58 C0A802B9 -> inetboot.SUN4V.Solaris_10-1

lrwxrwxrwx1 rootroot 27 Feb 26 10:58 C0A802B9.SUN4V -> inetboot.SUN4V.Solaris_10-1

-rwxr-xr-x1 rootroot215936 Feb 26 11:29 C0A802EA

-rwxr-xr-x1 rootroot215936 Feb 26 11:41 C0A802EA.SUN4V

-rwxr-xr-x1 rootroot215936 Feb 26 10:58 inetboot.SUN4V.Solaris_10-1

-rw-r--r--1 rootroot 319 Feb 26 10:58 rm.192.168.2.185

joshspeera at 2007-7-9 22:25:57 > top of Java-index,Sun Hardware,Servers - General Discussion...
# 4

@joshspeer

is your problem solved? If not, I stumpled about this little important fact when jumpstarting a T1000 - because the server has a new architecture sun4v!

(jumpstart server)

# ./add_install_client -e <MAC address> -p 192.168.0.1:/jumpstart -c 192.168.0.1:/jumpstart mantis sun4v

-- Nick

der_nikia at 2007-7-9 22:25:57 > top of Java-index,Sun Hardware,Servers - General Discussion...
# 5
Once I added the MAC address is worked. Thanks alot!
joshspeera at 2007-7-9 22:25:57 > top of Java-index,Sun Hardware,Servers - General Discussion...