I have two DHCP servers ... dhcp configured on sub-interface bundle1.1 work fine but dhcp on bundle1.2 not work....
when stopped bundle1.1 when interface 1.2 work... 2 sub interface not work the same time
this is my configuration bundle
interface Bundle1
no ip address
cable arp filter request-send 3 2
cable arp filter reply-accept 3 2
cable dhcp-giaddr policy
!
interface Bundle1.1
ip address 10.16.0.1 255.255.0.0 secondary
ip address 10.2.0.1 255.255.192.0
cable dhcp-giaddr policy
cable helper-address 172.33.55.10 cable-modem
cable helper-address 172.33.55.10 host
!
interface Bundle1.2
ip address 10.40.0.1 255.255.0.0 secondary
ip address 10.2.128.1 255.255.192.0
cable dhcp-giaddr policy
cable helper-address 10.181.15.252 cable-modem
cable helper-address 10.181.15.252 host
interface Bundle1
no ip address
cable arp filter request-send 3 2
cable arp filter reply-accept 3 2
cable dhcp-giaddr policy
!
interface Bundle1.1
ip address 10.16.0.1 255.255.0.0 secondary
ip address 10.2.0.1 255.255.192.0
cable dhcp-giaddr policy
cable helper-address 172.33.55.10 cable-modem
cable helper-address 10.181.15.252 host
!
interface Bundle1.2
ip address 10.40.0.1 255.255.0.0 secondary
ip address 10.2.128.1 255.255.192.0
cable dhcp-giaddr policy
cable helper-address 172.33.55.10 cable-modem
cable helper-address 10.181.15.252 host
is what you want, the way you have it, the modem sends dhcp request to first server it sees. (on the first bundle)
What you want to do is to setup your modem DHCP server so that the modems that need to be on bundle 1.1 get CM ips from 10.2.0.1 255.25.192.0 and modems that need to be on bundle 1.2 get ips on from 10.2.128.1 255.255.192.0
then in your host dhcp server you create a two shared networks
one with
10.2.0.1 255.255.192.0
and 10.16.0.1 255.255.0.0
and one with
10.2.128.1 255.255.192.0
and 10.40.0.1 255.255.0.0
I want when Dhcp on server 1. With CM ip 10.2.0.1. and cpe 10.16.0.1 expired to get DHCP. from server 2 and modem to connect on server 2
The cisco architecture does not work that way, The way it works is: the modem always sends its dhcp to the first subinterface cable helper address no matter what you specify.
the first dhcp server (the modem one) controls which bundle sub interface a modem/cpe comes up on. on the dhcp server you would create a shared network with both modem subnets and use some external criteria to determine which subnet to put modems in. What works well is known and unknown modems.
then on the second dhcp server you have two shared networks one with cm subnet from bundle 1.1 but no pool and the cpe subnet associated with bundle 1.1 and a second shared network with the cm subnet from bundle 1.2 with no pool and the cpe subnet associated with bundle 1.2. Depending on what subnet the modem is in will determine from what shared network it pulls the cpe address.
any example please how to do this!!
interface Bundle1
no ip address
cable arp filter request-send 3 2
cable arp filter reply-accept 3 2
!
interface Bundle1.1
ip address 10.16.0.1 255.255.0.0 secondary
ip address 10.2.0.1 255.255.192.0
cable helper-address 10.181.15.252 cable-modem
cable helper-address 172.33.55.10 host
!
interface Bundle1.2
ip address 10.40.0.1 255.255.0.0 secondary
ip address 10.2.128.1 255.255.192.0
cable helper-address 10.181.15.252 cable-modem
cable helper-address 172.33.55.10 host
#MODEM DHCPD SERVER CONFIG SNIPPET
# Cable Modem Class
class "CM" {
# only match if first 6 chars of option 61 are docsis
match if (substring(option vendor-class-identifier,0,6) = "docsis");
spawn with hardware;
}
# Match anything Else Only modems should be hitting this server so log any other devices that aren't CM or MTA
class "Unknown" {
match if ((substring(option vendor-class-identifier,0,6) != "docsis") and (substring(option vendor-class-identifier,0,4) != "pktc"));
spawn with hardware;
}
shared-network ModemPool {
option tftp-server-name "192.168.0.14";
option time-servers 24.137.168.1;
option log-servers 192.168.0.13;
next-server 192.168.0.14;
# Subnet for Authorized Modems
subnet 10.2.0.0 netmask 255.255.192.0 {
option subnet-mask 255.255.192.0;
option routers 10.2.0.1;
pool {
deny unknown-clients;
range 10.2.0.10 10.2.63.254;
allow members of "CM";
deny members of "Unknown";
}
}
# Subnet for UnAuthorized Modems
subnet 10.2.128.0 netmask 255.255.192.0 {
option subnet-mask 255.255.192.0;
option routers 10.2.128.1;
pool {
deny known-clients;
allow unknown-clients;
range 10.2.128.2 10.2.191.254;
allow members of "CM";
deny members of "Unknown";
}
}
}
#CLIENT DHCPD SERVER CONFIG SNIPPET
# Cable Modem Class Should not ever get to this DHCP server if it does Log it
class "CM" {
# only match if first 6 chars of option 61 are docsis
match if (substring(option vendor-class-identifier,0,6) = "docsis");
spawn with hardware;
log (info, concat("Modem with mac Address :", hardware, " hit the Clients DHCP Server"));
}
# Match Clients as determined by option 61
class "Client" {
match if ((substring(option vendor-class-identifier,0,6) != "docsis") and (substring(option vendor-class-identifier,0,4) != "pktc"));
spawn with hardware;
}
# Match MTAs that Identify themselves as pktc
class "MTA" {
match if (substring(option vendor-class-identifier,0,4) = "pktc");
spawn with hardware;
}
# Shared network for Un Authorized Modems
shared-network ClientsBehindUnAuthedModems {
# Subnet for Un Authed modems Defined in Modem DHCP server
subnet 10.2.128.0 netmask 255.255.192.0 {
}
# Subnet for Any Client behind an UnAuthorized Modem
subnet 10.40.0.0 netmask 255.255.192.0 {
# Unknown clients
option subnet-mask 255.255.0.0;
option routers 10.40.0.1;
pool {
range 10.40.0.3 10.40.32.254;
allow unknown-clients;
allow known-clients;
allow members of "Client";
deny members of "CM";
deny members of "MTA";
default-lease-time 30;
max-lease-time 60;
min-lease-time 30;
option domain-name-servers 192.168.0.14;
}
}
}
# Shared network for Authorized Modems
shared-network ClientsBehindAuthedModems {
# Subnet for Authed modems Defined in Modem DHCP server
subnet 10.2.0.0 netmask 255.255.192.0 {
}
# Subnet for Any Client behind an Authorized Modem
subnet 10.16.0.0 netmask 255.255.192.0 {
# known clients
option subnet-mask 255.255.0.0;
option routers 10.16.0.1;
pool {
range 10.16.0.3 10.16.32.254;
allow unknown-clients;
allow known-clients;
allow members of "Client";
deny members of "CM";
deny members of "MTA";
default-lease-time 30;
max-lease-time 60;
min-lease-time 30;
option domain-name-servers 192.168.0.14;
}
}
}
Hi,
I'm doing this this way:
1. create shared network docsis where both primary networks are included. You need to know which modem goes to which subbundle otherwise it is unacceptable.
2. create shared network for each of secondary interface (shared network sec-bundle 1.1, shared network sec-bundle 1.2)
This works like a charm.
BR,
Janko