| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||
Solution Type Technical Instruction Sure Solution 1008481.1 : Ensure that Jumpstart / Boot Server can be contacted from the current network port.
PreviouslyPublishedAs 211593 Description This document is intended to help to ensure the Jumpstart / Boot Server can be reached by the Jumpstart Client from switch port that it is attached to. This document is part of resolution path <Document: 1012870.1> Troubleshooting Common Jumpstart Problems: " Timeout waiting for ARP/RARP packet. Steps to Follow The test can be conducted by connecting a test client such as a known working system or a laptop to the switch port in question, giving that system the same IP address you desire the actual Jumpstart client to have when net-booted, and pinging the boot server. It is preferable to use the same cable that is to be used by the jumpstart client, so that all connections from the cable through to the switch are being verified. In order to perform the steps outlined here, you will need a test client system which has been installed with an operating environment; The steps here are based on a Solaris system with an e1000g interface, however, any system that can use TCP/IP would be appropriate. For example, if the boot server had an IP address of 192.168.1.1 and your Jumpstart client desired the address 192.168.1.10, you could attach a Solaris test client system (a laptop is the simplest alternative) to the cable, configuring the IP address and pinging the server. Note that if your Switch administrators have automatic Ethernet Address / VLAN association setup, it is likely that the client ethernet address will also need to be set. On the test client connected to the new client's cable for testing: Make sure the interface is unplumbed to start with. # ifconfig e1000g0 unplumb Set the ethernet address of the e1000g card to the ethernet address of the client to be net-booted # ifconfig e1000g0 plumb ether 01:02:03:04:05:06 Add the new interface and IP address # ifconfig e1000g0 192.168.1.10 up Ping the boot server # ping 192.168.1.1 If the boot server responds # ping 192.168.1.1 192.168.1.1 is alive the connection is good. If not, there may still have connectivity or network issues. You should consider requesting the network administration group review the switch port settings, VLAN settings and cable connectivity. Product Sun SPARC Enterprise T2000 Server Internal Comments Place Sun Internal-Use Only content here. This content will be published to internal SunSolve only. normalized, ethernet, network switch, jumpstart, boot, netboot Previously Published As 90534 Change History Date: 2007-09-28 User Name: 95826 Action: Approved Comment: - made hyperlinks - verified metadata - changed review date to 2008-09-27 - checked normalized data - checked for TM - none added - checked audience : contract Publishing Version: 3 Date: 2007-09-26 User Name: 95826 Action: Add Comment Comment: referenced document 90313 is not published yet Delaying publication Version: 0 Date: 2007-09-25 User Name: 95826 Action: Accept Comment: Version: 0 Date: 2007-09-25 User Name: 125045 Action: Approved Comment: Document part of new resolution path for timeout waiting for arp/rarp. Please review Product_uuid 0e37d2ca-ce95-11db-9135-080020a9ed93|Sun SPARC Enterprise T2000 Server Attachments This solution has no attachment |
||||||||||||
|
||||||||||||