Sponsored Content
Operating Systems Linux Red Hat RHEL5 Kickstart NFS & DHCP Problem Post 302330890 by apfistler on Thursday 2nd of July 2009 04:16:59 PM
Old 07-02-2009
I figured out the problem

I actually figured out what the problem was by looking through the loging on the switch. I'm using a Cisco Catalyst 2960G switch. What was happening is that when Anaconda was requesting a DHCP lease it was taking down the eth0 interface and bringing it back up. By the way the switch is configured it takes about 60-70 seconds for the port to be renabled after the interface went down. By then Anaconda was timing out the request for the DHCP lease. So I tested this theory by using a cheap 5 port switch, and it ended up working.
 

10 More Discussions You Might Find Interesting

1. AIX

Problem with NFS & rpc.lockd-Help Needed

We have windows clients that access drawing files shared from our AIX server using NFS. The Windows clients are intermittently unable to open files or access the system. For some reason restarting the rpc.lockd temporarily resolves the problem. However, that is the only clue I have to what the... (1 Reply)
Discussion started by: theologic
1 Replies

2. UNIX for Advanced & Expert Users

Problem: Automounting Home directory for nis & nfs configuration doesn't work

Hi all, First of all, i am so sorry about my bad level in English writing. I have some problem in linux and i hope the experts of this forum to help me if they have enough time to reply to me. I have a scenario of configuring NIS and NFS in Redhat Linux environment such that user can login... (0 Replies)
Discussion started by: pioneer
0 Replies

3. Linux

NFS not mounting during kickstart

Hi, Re-building linux server from a kickstart image on cdrom. We have a kickstart server. the cdrom contacins the kickstart ks.cfg file and does a NFS mount from an IP to load the iso images and other files needed during the kickstart (re-build) Now for some reason the kickstart stops and... (2 Replies)
Discussion started by: Andrek
2 Replies

4. UNIX for Dummies Questions & Answers

Mounting an NFS share: Kickstart Postinstall

For my kickstart install I use an NFS share on another machine in order to install the packages. For the most part, all configuration required after each time I reimage is set up in the kickstart file, but this one portion is giving me issues. I'm trying to mount an NFS share in the kickstart post... (0 Replies)
Discussion started by: Colton
0 Replies

5. Linux

RHEL5 Kickstart Problem... HELP!

Folks, Im hoping you guys can help me. Here is a description of what I have going on. Fresh VM, trying to run a Kickstart Install on it for RHEL5. I am looking to access the kickstart file through nfs. I boot from a local ISO image and everything goes fine, I get to the boot prompt and enter... (3 Replies)
Discussion started by: mkono
3 Replies

6. Red Hat

nfs on RHEL5.4 in relation to the selected kernel

I have 2 RHEL5.4 systems connected by a network. I start nfs server on one (fill /etc/exports , exportfs -ra, service nfs start, portmpa is up) and the client is on the other . I can mount the exported directory on the client and work there . Now the RH54 kernel is 2.6.18 . I now installed... (2 Replies)
Discussion started by: dubi
2 Replies

7. Solaris

documents needed for dhcp and nfs tuning configuration

hi all i am learning about solaris. I am trying to configure dhcp in my sun blade 150 which is running with solaris 5.10 and i dont have any step by step guide to configure dhcp. I am requesting you all to suggest me some good document for nfs tuning too. Regards Kingston S (1 Reply)
Discussion started by: kingston
1 Replies

8. Red Hat

"ERROR : failed to mount nfs source" Red Hat Kickstart

Hi There, I have been googling for this error and try solution provided but still not avail to resolve Kickstart Issue. Any expert have encounter this problem? Thanks. Regards, Regmaster (4 Replies)
Discussion started by: regmaster
4 Replies

9. Web Development

NFS Share & Mount problem

Hi, I want to mount an NFS Shared folder on Windows XP to vxWorks. There doesnt seem to be a problem with the sharing. Now, when i try to mount the directory onto vxWorks (it runs on a Tumbleweed card), using a mount script (.sh), the following is the print i see on Tera Term: hostAdd... (0 Replies)
Discussion started by: chinmayzen
0 Replies

10. SuSE

Non Graphical AutoYast installations & Kickstart

Hi We are using Kickstart to push images out for Suse using various releases as far back as 9.0. The trouble is we often have issues with ILO, ILO2, & ILO3 so prefer to use ssh onto the ILO and use textcons to get a text console. AutoYast when using the AutoYast.xml file goes into... (0 Replies)
Discussion started by: Swaps
0 Replies
DHCP-HELPER(8)						      System Manager's Manual						    DHCP-HELPER(8)

NAME
dhcp-helper - A DHCP/BOOTP relay agent. SYNOPSIS
dhcp-helper [OPTION]... DESCRIPTION
dhcp-helper is a DHCP and BOOTP relay agent. It listens for DHCP and BOOTP broadcasts on directly connected subnets and relays them to DHCP or BOOTP servers elsewhere. It also relays replies from the remote servers back to partially configured hosts. Once hosts are fully config- ured they can communicate directly with their servers and no longer need the services of a relay. OPTIONS
The only required option is at least one DHCP server to relay to. The simplest way to configure dhcp-helper on a router is just to give the interface to the network containing the DHCP server with a -b option. All the other interfaces present on the machine will then accept DHCP requests. On a machine which does not have an interface on the network containing the DHCP server, use a -s option instead. -s <server> Specify a DHCP or BOOTP server to relay to. The server may be given as a machine name or dotted-quad IP address. More than one server may be specified. -b <interface> Relay to a DHCP or BOOTP server using broadcast via <interface>. This eliminates the need to give a server address. <interface> is automatically added to the list of interfaces which will not receive DHCP requests. -i <interface> Specify which local interfaces to listen on for DHCP/BOOTP broadcasts. If no -i flags are given all interfaces are used except those specified by -e flags and those specified by -b flags. -e <interface> Specify which local interfaces to exclude. -p Use alternative ports (1067/1068) for the DHCP client and server. -v Report the software release version and copyright information. -d Debug mode, do not change UID, write a pid-file or go into the background. -r <file> Specify an alternate path for dhcp-helper to record its process-id in. Normally /var/run/dhcp-helper.pid. -u <username> Specify the userid to which dhcp-helper will change after startup. The daemon must normally be started as root, but it will drop root priviledges after startup by changing id to another user. Normally this user is "nobody" but that can be over-ridden with this switch. NOTES
Dhcp-helper requires a 2.2 or later Linux kernel. The "Linux packet filter" and "packet socket" facilities are not required, which is the chief advantage of this software over the ISC DHCP relay daemon. AUTHOR
This manual page was written by Simon Kelley <simon@thekelleys.org.uk>. DHCP-HELPER(8)
All times are GMT -4. The time now is 03:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy