03-17-2006
Enabling dhcp relaying for the three VLANs on your switch should in fact solve the problem.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I need to setup a DHCP server in our office for Macs, Windows (98/ME/NT/2000) Linux and Unix servers and workstations. We want it on a Unix server, but I'm unsure what is out there. The Unix world is new to me, so any suggestions would be appreciated.
Thanks!
Corey (2 Replies)
Discussion started by: coreyhead
2 Replies
2. UNIX for Advanced & Expert Users
hi all,
In dhcp client , how to specify no of retiral attempts for getting IP ?
man dhclient.conf - has rery timeout but i m looking for attempts
Also option nwip.autoretries uint8; - i guess this is for dhcpd server
I basically want to expire after the first attempt.
Any... (1 Reply)
Discussion started by: ramchan10
1 Replies
3. IP Networking
Hi.
I want to use the DHCP server that comes with vxWorks 6.4.
The DHCP server implementation has a table that contains addresses of DHCP servers that will receive a copy of all the client requests that the local server gets, thus the server acts as a dhcp relay at the same time.
Can anyone... (4 Replies)
Discussion started by: tomwolf
4 Replies
4. Debian
Hi ,
when i configure my server with a fixed ip address in dhcpd.conf as below
subnet 172.21.151.0 netmask 255.255.255.0 {
range 172.21.151.66 172.21.151.66;
}
host switch {
hardware ethernet 00:05:30:02:DB:31;
fixed-address 172.21.151.66;
}
when i start dhcpd server , it... (2 Replies)
Discussion started by: Gopi Krishna P
2 Replies
5. Solaris
Dears,
my question
is that possible to configure any server to work in solaris zone
i mean any server
cos i read that DHCP can't be work on solaris zone
is that real or not
Best Regards
Alexander Corvinus (4 Replies)
Discussion started by: corvinusbsd
4 Replies
6. IP Networking
Hi,
We currently operate a DHCP Server on Vxworks system.
It seems that the server is functioning only over the boot interface.
While trying to use it on a different interface the DHCP client messages seems to reach the interface but stay without response.
From a... (1 Reply)
Discussion started by: zohara
1 Replies
7. Red Hat
Where can you find your DHCP Server address? I checked all of the files that this mentioned with no luck.
Quick HOWTO : Ch08 : Configuring the DHCP Server - Linux Home Networking (6 Replies)
Discussion started by: cokedude
6 Replies
8. IP Networking
I need a script to scan the surrounding DHCP servers. I want to know how many dhcp servers are there on my connected etnernet. (2 Replies)
Discussion started by: getrue
2 Replies
9. Solaris
I need to find out the MAC address of an IP leased from DHCP server .
For Eg:-i need to know the MAC of the below mentioned IP at the below mentioned time .
IP : 172.16.28.90
Date :Sunday July 2nd 2011
Time : 14.07.2011
OS -Solaris 10
Vital QIP IP management software using to... (0 Replies)
Discussion started by: sandeep.tk
0 Replies
10. Ubuntu
Hello.
Doing my first steps in Linux and while trying to configure a DHCP server in Linux i encountered some problems:
TOPOLOGY:
- Laptop with Windows 8.1
- VM Player 12 with Linux installed (Ubuntu Server 14.04)
- ICS-DHCP-SERVER installed and running
- Another LAPTOP conected to a... (1 Reply)
Discussion started by: Portuguevos
1 Replies
LEARN ABOUT DEBIAN
fipvlan
FIPVLAN(8) Open-FCoE Tools FIPVLAN(8)
NAME
fipvlan - Fibre Channel over Ethernet VLAN Discovery
SYNOPSIS
fipvlan [-c|--create] [-s|--start] interfaces
fipvlan -a|--auto [-c|--create] [-d|--debug] [-s|--start] [-l|--link-retry <num>]
fipvlan -h|--help
fipvlan -v|--version
DESCRIPTION
The fipvlan command performs Fibre Channel over Ethernet (FCoE) Initialization Protocol (FIP) VLAN Discovery over Ethernet interfaces.
fipvlan can be used as a diagnostic tool to determine which VLANs have FCoE services available on a network, prior to configuring VLAN
interfaces and the Open-FCoE initiator. fipvlan can also be used to create VLAN interfaces as they are discovered, and to start the
Open-FCoE initiator. The --create and --start options are primarily intended to be used as part of an Open-FCoE boot solution. FCoE
instances started in this way cannot be destroyed or reset by fcoeadm.
fipvlan takes a list of network interface names to run the VLAN discovery protocol over, or the --auto option to use all available Ethernet
interfaces.
fipvlan will enable any interface which is found to be not enabled by the time the program runs. If no response is received on that
interface it will be shutdown again when fipvlan terminates.
OPTIONS
-a, --auto
Use all Ethernet interfaces currently available
-c, --create
Create network interfaces for discovered FCoE VLANs. If a VLAN device already exists for a discovered VLAN, a new VLAN device will not
be created.
-d, --debug
Enable debugging output
-s, --start
Start the Open-FCoE initiator on discovered FCoE VLANs
-f, --suffix <suffix string>
Append the specified string <suffix string> to VLAN interface names.
-l, --link-retry <number of retries>
Retry check for link up up to <number of retries> times. The link state is retried every 500 ms. The default is 20.
-h, --help
Display a help message with basic usage instructions
-v, --version
Display the fipvlan version string
VLAN NAMING CONVENTIONS
The default VLAN device name is dev.vlan; where dev is the name of the Ethernet parent device and vlan is the discovered VLAN ID number. An
optional suffix can be appended to this with -f commandline option.
EXAMPLES
Display all discoverable VLANs with FCoE services
fipvlan --auto
Discover FCoE VLANs on interface eth2, create VLAN devices and start the Open-FCoE initiator
fipvlan --create --start eth2
In this example if FCoE services were available on VLAN 101 of network interface eth2, then a VLAN interface eth2.101-fcoe would be created
and used as the parent device for the initiator.
SEE ALSO
fcoeadm(8) fcoemon(8)
SUPPORT
fipvlan is part of the fcoe-utils package, maintained through the Open-FCoE project. Resources for both developers and users can be found
at the Open-FCoE website http://open-fcoe.org/
Open-FCoE 10/06/2011 FIPVLAN(8)