![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| IP Networking Learn TCP/IP, Internet Protocol, Routing, Routers, Network protocols in this UNIX and Linux forum. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Timeout waiting for arp/rarp error | solar10 | UNIX for Advanced & Expert Users | 7 | 01-16-2009 08:16 PM |
| Alternate way for echo. | senthil_is | Shell Programming and Scripting | 5 | 03-05-2008 09:12 AM |
| Help with waiting for ARP/RARP packet | chezmargm | UNIX for Dummies Questions & Answers | 1 | 05-29-2007 09:03 PM |
| Jumpstart: Rarp protocol specifics | mhm4 | SUN Solaris | 3 | 01-21-2007 11:22 AM |
| Alternate command for cut | Mohammed | Shell Programming and Scripting | 2 | 10-20-2006 07:42 AM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
||||
|
Alternate to RARP Solaris 5.6 & 5.8
I am a Cisco Engineer and have run into a problem with the boot process for UNIX servers running Solaris 5.6 & 5.8 OS. Currently the servers boot using RARP to discover IP configuration.
This works and is OK as long as everything is on the same network where the broadcasts are free to roam. The network is being put into VLAN's with much smaller subnets where the RARP broadcast will not reach the RARP server. What alternatives are there for this version of Solaris. I've been told that the BIOS on these boxes cannot accomodate BootP. BootP would solve the problem easily, is it possible that it can be run on this version? Sorry for the lack of OS details, but I'm responsible for the network piece and am trying to present options to the server engineers. Thanks! |
|
||||
|
I don't think there is a solution to that. You need to have a boot server on each vlan. Where I work now our jumpstart server has an interface on every subnet which works fine. Or you can designate one machine on each vlan as the boot server for that vlan, then just that one will need to be able to talk to the rarp server.
I would probably look at the first option if I were you. See if you can create virtual interfaces for your rarp server so it is on every vlan. That is by far the easiest if you can do it that way. |
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|