[Kea-users] Multiple Subnets on same VLAN
Kris Emsoff
kris at ucs.net
Tue Nov 8 20:03:16 UTC 2022
Nicholas,
We tried implementing this and at first it seemed to work as intended, however, within 36 hours or so we started having issues with the DHCP server failing to allocate IP's.
We tried configuring this 2 ways,
1. ALL subnets as their own shared network - we quickly found out this created a huge hit to the server load.
2. Only the VLAN with multiple subnets.
We do currently have 1 VLAN working as a shared network off of this server and it has been working fine. The issue still arises however when trying to add additional shared networks.
We will continue to troubleshoot further on this, and try to isolate why this is happening. It is the only ring we are having this issue with Kea on, multiple other instances on other rings are functioning just fine.
Not sure if we are still implementing incorrect or something else is at fault here.
Kris Emsoff
Network Analyst
Office : (817)-326-1567
Cell : (682) 970-7555
Email : kris at ucs.net<mailto:kris at ucs.net>
www.ucs.net/internet<http://www.ucs.net/internet>
[United Cooperative Services]<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.united-cs.com%2F&data=04%7C01%7Ckris%40ucs.net%7Ce2fc7b409b85401c96ca08d968c72c1a%7Cce91fdf11d35455ca72010044d2c846b%7C0%7C0%7C637656026914245951%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=aR6dGcd7GCU3HVIec%2BAJ1rZpeBtso40d1wszJqa2atA%3D&reserved=0>
From: Kea-users <kea-users-bounces at lists.isc.org> On Behalf Of Nicholas Warren
Sent: Monday, October 31, 2022 3:20 PM
To: kea-users at lists.isc.org
Subject: Re: [Kea-users] Multiple Subnets on same VLAN
CAUTION: This message originated from outside of UCS. Please do not click links or open attachments unless you recognize the source of this email and know the content is safe.
Kris,
We're just using Kea in a lab setting, but we have all our vlans that do not share subnets broken into multiple networks. We aren't seeing this problem, but again, we are just in testing. Please post results, as we will be in the same situation if we moved to production with Kea.
So for example we would break up ,
"shared-networks": [
{
"name": "SharedPop-Node1",
"relay": { "ip-addresses": ["X.X.X.1"] },
"subnet4": [
{
// VLAN 1116 - Node
"subnet": "X.X.X.0/22",
"pools": [ { "pool": "X.X.X.4 - X.X.X.254" } ],
"option-data": [ { "name": "routers", "data": "X.X.X.1" } ],
"client-class": "HA_dhcp-1"
},
{
// VLAN 1116 - Node 2nd Subnet
"subnet": "X.X.X.0/23",
"pools": [ { "pool": "X.X.X.4 - X.X.X.254" } ],
"option-data": [ { "name": "routers", "data": "X.X.X.1" } ],
"client-class": "HA_dhcp-1"
}
]
},
{
"name": "SharedPop-Node2",
"relay": { "ip-addresses": ["X.X.X.1"] },
"subnet4": [
{
// VLAN 1204 - Node
"subnet": "X.X.X.0/23",
"pools": [ { "pool": "X.X.X.4 - X.X.X.254" } ],
"option-data": [ { "name": "routers", "data": "X.X.X.1" } ],
"client-class": "HA_dhcp-1"
},
{
// VLAN 1204 - 2nd Subnet
"subnet": "X.X.X.0/23",
"pools": [ { "pool": "X.X.X.4 - X.X.X.254" } ],
"option-data": [ { "name": "routers", "data": "X.X.X.1" } ],
"client-class": "HA_dhcp-1"
}
]
}
]
Nich
From: Kea-users <kea-users-bounces at lists.isc.org<mailto:kea-users-bounces at lists.isc.org>> On Behalf Of Kris Emsoff
Sent: Monday, October 31, 2022 2:29 PM
To: kea-users at lists.isc.org<mailto:kea-users at lists.isc.org>
Subject: [Kea-users] Multiple Subnets on same VLAN
We have a lingering issue that we are trying to work through and seem to be at a standstill each time we try and resolve our issue.
The issue is solely with VLAN's that have more than 1 subnet.
We have tried adding into "Shared Networks" which solves the issue with one single VLAN, the issue is we have multiple VLAN's that use more than one subnet. When adding an additional VLAN and subnet to the "shared network" category we start getting IP issues with handouts and trying to handout from subnets that are not part of that node. I have tried using the relay function as well and have not managed to find a work around.
All of our other VLAN's with a single subnet are functioning as intended
Below is a snip of the configuration. With the other nodes commented out this performs as expected. But when I comment them back in we start seeing issues.
Should we scrap the shared networks and move them back to individual networks and just add the relay to each? Or am I missing something here?
Any help would be appreciated
"shared-networks": [
{
"name": "SharedPop",
"relay": { "ip-addresses": ["X.X.X.1"] },
"subnet4": [
// {
// // VLAN 1116 - Node
// "subnet": "X.X.X.0/22",
// "pools": [ { "pool": "X.X.X.4 - X.X.X.254" } ],
// "option-data": [ { "name": "routers", "data": "X.X.X.1" } ],
// "client-class": "HA_dhcp-1"
// },
// {
// // VLAN 1116 - Node 2nd Subnet
// "subnet": "X.X.X.0/23",
// "pools": [ { "pool": "X.X.X.4 - X.X.X.254" } ],
// "option-data": [ { "name": "routers", "data": "X.X.X.1" } ],
// "client-class": "HA_dhcp-1"
// },
// {
// // VLAN 1204 - Node
// "subnet": "X.X.X.0/23",
// "pools": [ { "pool": "X.X.X.4 - X.X.X.254" } ],
// "option-data": [ { "name": "routers", "data": "X.X.X.1" } ],
// "client-class": "HA_dhcp-1"
// },
// {
// // VLAN 1204 - 2nd Subnet
// "subnet": "X.X.X.0/23",
// "pools": [ { "pool": "X.X.X.4 - X.X.X.254" } ],
// "option-data": [ { "name": "routers", "data": "X.X.X.1" } ],
// "client-class": "HA_dhcp-1"
// },
{
// VLAN 1113 - Node
"subnet": "X.X.X.0/24",
"pools": [ { "pool": "X.X.X.4 - X.X.X.254" } ],
"option-data": [ { "name": "routers", "data": "X.X.X.1" } ],
"client-class": "HA_dhcp-1"
},
{
// VLAN 1113 - Node 2nd Subnet
"subnet": "X.X.X.0/24",
"pools": [ { "pool": "X.X.X.4 - X.X.X.254" } ],
"option-data": [ { "name": "routers", "data": "X.X.X.1" } ],
"client-class": "HA_dhcp-1"
}
]
}
],
CONFIDENTIALITY NOTICE: This electronic communication (including any attachment) contains information that (a) is or may be LEGALLY PRIVILEGED, CONFIDENTIAL, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the use of the addressee(s) named herein. If you are not an intended recipient, you are hereby notified that reading, using, copying, or distributing any part of this communication is strictly prohibited. If you have received this electronic communication in error, please notify the sender immediately by reply email, delete the communication completely from your computer system, and destroy all printed copies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20221108/38b86546/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 15732 bytes
Desc: image001.jpg
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20221108/38b86546/attachment-0001.jpg>
More information about the Kea-users
mailing list