This discussion is archived
13 Replies Latest reply: Feb 18, 2011 12:55 PM by 836014 RSS

T1000 - Solaris 10 - Jumpstart problem

836014 Journeyer
Currently Being Moderated
I am trying jumpstart installation on T1000.

My jumpstart server is Sun Fire V210, running Solaris 9. Jumpstart configuration is done for Solaris 10.

When run boot net - install from T1000, I am getting the following error and the installation stops

{0} ok boot net - install
Boot device: /pci@7c0/pci@0/network@4 File and args: - install
Timed out waiting for Autonegotiation to complete
Check cable and try again
Link Down
Retrying network initialization
Timed out waiting for Autonegotiation to complete
Check cable and try again
Link Down
Retrying network initialization
Timed out waiting for Autonegotiation to complete
Check cable and try again
Link Down
Retrying network initialization

Can't open boot device

I am able to ping my T1000 console address from my install server. What "Link Down" it reports about? What is the problem with this installation?

Please help
  • 1. Re: T1000 - Solaris 10 - Jumpstart problem
    abrante Pro
    Currently Being Moderated
    "Link down" reports that the system itself is not connected to the network on the interface its trying to boot on.

    The network connection used for the console is only used for the console and not for the system itself. When you try to jumpstart a SPARC system it will typically try to boot from the interface labeled 'net 0'.

    If your system is installed correctly you should have one network cable to the console port, and one network cable to one of the 'normal' ethernet ports.

    .7/M.
  • 2. Re: T1000 - Solaris 10 - Jumpstart problem
    836014 Journeyer
    Currently Being Moderated
    So, I should give the host IP, not the console IP, while add install client and the default network port (bge0?) should also be in the network to complete the installation.

    Is that correct?

    Edited by: user11284483 on Feb 16, 2011 8:40 AM
  • 3. Re: T1000 - Solaris 10 - Jumpstart problem
    836014 Journeyer
    Currently Being Moderated
    I have overcome that Link down error and now it says

    1000 Mbps FDX Link up

    Requesting Internet address for 0:14:4f:2:a1:85
    panic - boot: Could not mount filesystem.
    Program terminated

    I changed following parameters in /etc/default/nfs

    #NFS_SERVER_VERSMAX=4

    I changed this value to 2 and 3 and restarted nfs, still the above error is not getting away.

    Is there any other problem?

    Please help

    - Soorya
  • 4. Re: T1000 - Solaris 10 - Jumpstart problem
    Nik Expert
    Currently Being Moderated
    Hi. Please show result command
    share
    On jumpstart server.
    Regards.
  • 5. Re: T1000 - Solaris 10 - Jumpstart problem
    abrante Pro
    Currently Being Moderated
    As Nik suggested, this indicates that you haven't shared the jumpstart filesystem properly. Check your NFS configuration.

    .7/M.
  • 6. Re: T1000 - Solaris 10 - Jumpstart problem
    836014 Journeyer
    Currently Being Moderated
    Here are the share detail

    # share
    - /opt/SUNWjet ro,anon=0 "JET Framework"
    - /export/jumpstart ro,anon=0 ""
    - /cdrom/sol_10_910_sparc/Solaris_10/Tools/Boot ro,anon=0 ""
    - /export/install/5.10/Solaris_10/Tools/Boot ro,anon=0 ""
  • 7. Re: T1000 - Solaris 10 - Jumpstart problem
    Nik Expert
    Currently Being Moderated
    Hi

    You have two shared boot environment:
    /cdrom/sol_10_910_sparc/Solaris_10/Tools/Boot
    /export/install/5.10/Solaris_10/Tools/Boot

    What used for install T1000 ?
    Please, show /etc/bootparams record for T1000.

    Are you shure that no other install servers present in network ?

    If problem not resolved.
    On Jumpstart server run
    snoop 0:14:4f:2:a1:85

    If this server have more one active network interface:
    snoop -d <interface LAN to T1000> 0:14:4f:2:a1:85

    You can see what filesystem T1000 try mount.

    Regards.
  • 8. Re: T1000 - Solaris 10 - Jumpstart problem
    836014 Journeyer
    Currently Being Moderated
    I am starting fresh.

    Will get back soon, if any problem persists.

    Regards
    Soorya
  • 9. Re: T1000 - Solaris 10 - Jumpstart problem
    836014 Journeyer
    Currently Being Moderated
    I reconfigured from the start, still the status is same.

    share
    - /export/install/Solaris_10/Tools/Boot ro,anon=0 ""

    */etc/bootparams*
    scdsoltst root=scdkla01a:/export/install/Solaris_10/Tools/Boot install=scdkla01:/export/install boottype=:in sysid_config=scdkla01:
    /export/jumpstart install_config=scdkla01:/export/jumpstart rootopts=:rsize=8192

    # snoop 0:14:4f:2:a1:85Using device bge0 (promiscuous mode)
    xx.x.x.3 -> * ARP C Who is 10.1.5.35, scdsoltst ?
    xx.x.x.2 -> * ARP C Who is 10.1.5.35, scdsoltst ?
    xx.x.x.3 -> * ARP C Who is 10.1.5.35, scdsoltst ?
    xx.x.x.2 -> * ARP C Who is 10.1.5.35, scdsoltst ?

    OLD-BROADCAST -> (broadcast) RARP C Who is 0:14:4f:2:a1:85 ?
    jumpstart srvr.my.domain -> scdsoltst RARP R 0:14:4f:2:a1:85 is 10.1.5.35, scdsoltst
    scdsoltst -> BROADCAST TFTP Read "0A010523" (octet)
    scdkla01.cree.com -> scdsoltst TFTP Data block 1 (512 bytes)
    scdsoltst -> jumpstart srvr.my.domain TFTP Ack block 1
    jumpstart srvr.my.domain -> scdsoltst TFTP Data block 2 (512 bytes)
    scdsoltst -> jumpstart srvr.my.domain TFTP Ack block 2
    jumpstart srvr.my.domain -> scdsoltst TFTP Data block 3 (512 bytes)
    scdsoltst -> jumpstart srvr.my.domain TFTP Ack block 3
    ....
    .....
    jumpstart srvr.my.domain -> scdsoltst TFTP Data block 432 (112 bytes) (last block)
    scdsoltst -> jumpstart srvr.my.domain TFTP Ack block 432
    OLD-BROADCAST -> (broadcast) RARP C Who is 0:14:4f:2:a1:85 ?
    jumpstart srvr.my.domain -> scdsoltst RARP R 0:14:4f:2:a1:85 is xx.x.x.35, scdsoltst
    scdsoltst -> BROADCAST BIFF R port=111
    scdsoltst -> (broadcast) ARP C Who is xx.x.x.22, server1.my.domain ?
    scdsoltst -> (broadcast) ARP C Who is xx.x.x.25, server2.my.domain ?
    ^C

    snoop output ends here, as the following error generated at the client, no NFS mount requests found in snoop output.

    Rebooting with command: boot net - install
    Boot device: /pci@7c0/pci@0/network@4,1 File and args: - install
    1000 Mbps FDX Link up
    Requesting Internet Address for 0:14:4f:2:a1:85
    Requesting Internet Address for 0:14:4f:2:a1:85
    Requesting Internet Address for 0:14:4f:2:a1:85
    Requesting Internet Address for 0:14:4f:2:a1:85
    Requesting Internet Address for 0:14:4f:2:a1:85
    Requesting Internet Address for 0:14:4f:2:a1:85
    1000 Mbps FDX Link up

    Requesting Internet address for 0:14:4f:2:a1:85
    panic - boot: Could not mount filesystem.
    Program terminated

    I have the following NICs in the client, out which only one is usable currently

    {0} ok show-nets
    a) /pci@7c0/pci@0/network@4,1 (0:14:4f:2:a1:85 - this is active)
    b) /pci@7c0/pci@0/network@4
    c) /pci@7c0/pci@0/pci@8/network@1,1
    d) /pci@7c0/pci@0/pci@8/network@1

    the banner output shows

    Sun Fire(TM) T1000, No Keyboard
    Copyright 2006 Sun Microsystems, Inc. All rights reserved.
    OpenBoot 4.23.4, 8184 MB memory available, Serial #67281284.
    Ethernet address 0:14:4f:2:a1:84, Host ID: 8402a184.

    0:14:4f:2:a1:84 is unusable due to problem in it, inactive.

    My latest jumpstart server is M4000 with Solaris 10. I donot have any other jumpstart servers in my network.

    Please help.

    Regards
    Soorya

    Edited by: Soorya on Feb 17, 2011 11:54 AM

    Edited by: Soorya on Feb 17, 2011 12:30 PM
  • 10. Re: T1000 - Solaris 10 - Jumpstart problem
    abrante Pro
    Currently Being Moderated
    If you don't see any NFS requests in your snoop perhaps you should change the servername in bootparams from:

    scdkla01
    to

    scdkla01.cree.com

    Also, your bootparams states that you uses the following three filesystems:
    sdckla01:/export/install/Solaris_10/Tools/Boot
    sdckla01:/export/install
    scdkla01:/export/jumpstart

    ..so rather than sharing /export/install/Solaris_10/Tools/Boot you have to share the top-level directory used by jumpstart, i.e. /export/install and then also /export/jumpstart .
  • 11. Re: T1000 - Solaris 10 - Jumpstart problem
    Nik Expert
    Currently Being Moderated
    Hi again.

    Some problem what i can see:

    1) bootparams: ... install=scdkla01:/export/install ....
    But, share say:
    /export/install/Solaris_10/Tools/Boot
    So, Install directory, realy, not shared.

    At my test envoronment, addinstallclient share with options : anon=0,sec=sys,ro
    You should share whol /export/install


    2) Look snoop result:
    We find ARP request and TFTP traffic.
    It's fine. RARPD give address to scdsoltst and bootloader was transfered.

    ( Please - show: ls -la /tftpboot/0A010523 )

    After Start work bootloader. It again ask IP address and get it. It's correct.
    After send request for bootparams ( BIFF )

    But not recived answer from your server and start found servers
    scdsoltst -> (broadcast) ARP C Who is xx.x.x.22, server1.my.domain ?
    scdsoltst -> (broadcast) ARP C Who is xx.x.x.25, server2.my.domain ?

    What this server? Is it possible that this servers was configured as jumpstart (bootparams) servers ?

    jumpstart srvr.my.domain and scdkla01a is same system?

    Check state of service bootparams
    bash-3.00# svcs -a | grep bootparams
    online 14:25:57 svc:/network/rpc/bootparams:default
    bash-3.00#



    For Information.
    How look normal network boot: vserv1 - client. i-host -server.
    1 0.00000 OLD-BROADCAST -> (broadcast) RARP C Who is 0:21:28:a6:5e:6c ?
    2 0.00143 i-host -> vserv1 RARP R 0:21:28:a6:5e:6c is XXX.XXX.XXX.151, vserv1
    3 0.00038 vserv1 -> BROADCAST TFTP Read "XXXXXXXXXXX" (octet)
    4 0.03008 i-host -> vserv1 TFTP Data block 1 (512 bytes)
    ..........
    866 0.00006 i-host -> vserv1 TFTP Data block 432 (112 bytes) (last
    block)
    867 0.00042 vserv1 -> i-host TFTP Ack block 432
    868 18.41304 OLD-BROADCAST -> (broadcast) RARP C Who is 0:21:28:a6:5e:6c ?
    869 0.00136 i-host -> vserv1 RARP R 0:21:28:a6:5e:6c is XXX.XXX.XXX.151, vserv1
    870 0.00049 vserv1 -> BROADCAST BIFF R port=111 ( 512 port UDP)
    871 0.00513 i-host -> vserv1 BIFF C port=32771
    872 0.00103 vserv1 -> (broadcast) ARP C Who is XXX.XXX.XXX.197, i-host ?
    873 0.00039 vserv1 -> i-host WHO R port=37864
    874 0.00064 i-host -> vserv1 WHO C port=37864
    875 0.00100 vserv1 -> i-host SYSLOG R port=37864
    876 0.00038 i-host -> vserv1 SYSLOG C port=37864 BAD.FMT:
    877 0.00106 vserv1 -> i-host PRINTER R port=2049
    878 0.00011 i-host -> vserv1 PRINTER C port=2049
    879 0.00092 vserv1 -> i-host PRINTER R port=2049
    ............
  • 12. Re: T1000 - Solaris 10 - Jumpstart problem
    836014 Journeyer
    Currently Being Moderated
    Now, I only have the following share, this has all sysidcfg, rules and etc in /export/install dir.

    share
    - /export/install anon=0,sec=sys,ro ""

    I changed the bootparams servername to servername.domain.com.

    But, the result is same

    Requesting Internet address for 0:14:4f:2:a1:85
    panic - boot: Could not mount filesystem.
    Program terminated
  • 13. Re: T1000 - Solaris 10 - Jumpstart problem
    836014 Journeyer
    Currently Being Moderated
    I have reconfigured the jumpstart in V240 and successfully installed T1000.

    For some reason M4000 is not supporting jumpstart for T1000.

    Thanks a ton for Nik and ABrante.

    Regards
    Soorya

    Edited by: Soorya on Feb 18, 2011 12:54 PM

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points