Start a Conversation

Unsolved

CD

1 Rookie

 • 

8 Posts

144

October 21st, 2024 08:17

IP Helper and Routing with PVLAN (OS10)

Hi,

We have a VLAN which has multiple access switches for a client type. The VLAN is configured with private-vlan mode isolated.

interface vlan116

 private-vlan mode isolated

no shutdown

 

To hand this network off to another router, we have another VLAN as follows:

interface vlan1116

 private-vlan mode primary

 private-vlan mapping secondary-vlans 116

no shutdown

 

This all works as intended. However, we are now considering using a DHCP relay on the switch rather than the upstream router.

We need the primary VLAN to be in L3 mode for this to work. I.e. something like:

interface vlan1116

 mode L3

 private-vlan mode primary

 private-vlan mapping secondary-vlans 116

 no shutdown

 ip helper-address xxx.xxx.xxx.xxx

 ip helper-address  yyy.yyy.yyy.yyy

 ip address zzz.zzz.zzz.zzz/24

 ip local-proxy-arp

Local proxy ARP is required according to the documentation at https://www.dell.com/support/manuals/da-dk/smartfabric-os10-emp-partner/smartfabric-os-user-guide-10-5-4/configure-an-ipv4-address-and-local-proxy-arp-on-a-pvlan-interface?guid=guid-d03b70e1-f671-41c6-8bcf-529042956638&lang=en-us

This configuration works too. However, we do not want clients to be able to use the IP address of the switch (zzz.zzz.zzz.zzz) for routing. The address is there only for the purpose of the DHCP relay.

One way to solve this would be to put the interface into a separate VRF and blackhole all traffic. However, OS10 does not allow a private VLAN to be in a VRF. Do you have any ideas on how I might solve this problem?

An obscure solution that I can see would be to create a separate L3 VLAN with the IP helper. To bridge this into the VLAN 1116, I would need to use a physical cable between two ports on the switch. I do not want actually to do it this way.

Moderator

 • 

9.4K Posts

October 21st, 2024 12:41

Christopher-deHaas,
 
 
There are a few things you can try to help you achieve your goal:
 
  1. Secondary IP address on the VLAN interface : Assign a secondary IP address to the VLAN 1116 interface (vlan1116) that's not routable and not used by the clients. This way, the switch will have a secondary IP address that can be used for the DHCP relay, but clients won't be able to use it for routing.

For example

interface vlan1116
  ip address zzz.zzz.zzz.zzz/24 secondary
  private-vlan mode primary
  private-vlan mapping secondary-vlans 116
  no shutdown
  ip helper-address xxx.xxx.xxx.xxx
  ip helper-address yyy.yyy.yyy.yyy

 

 

  1. Sub-interface on the VLAN interface : Create a sub-interface on the VLAN 1116 interface and configure the IP helper address on that sub-interface. This way, the clients won't be able to use the main IP address of the VLAN interface for routing.

For example

interface vlan1116.1
  ip address zzz.zzz.zzz.zzz/24
  ip helper-address xxx.xxx.xxx.xxx
  ip helper-address yyy.yyy.yyy.yyy
  no shutdown

 

 

  1. Routed port : Configure a routed port on the switch, which will allow you to assign a separate IP address to the port that's not routable. Then, you can use this IP address as the IP helper address for the DHCP relay.

for example

interface EthernetX
  no switchport
  ip address zzz.zzz.zzz.zzz/24
  ip helper-address xxx.xxx.xxx.xxx
  ip helper-address yyy.yyy.yyy.yyy
  no shutdown

 

 

 

Let me know if any of these ideas work to you, or if you'd like me to explore other options, or if this helps.

 

 

(edited)

1 Rookie

 • 

8 Posts

October 21st, 2024 14:23

Hi @DELL-Chris H ​ ,

 

Thank you very much for your ideas.

 

  1. Secondary IP. I have not yet tried to test this option, but I cannot find much on secondary addresses in the OS10 documentation. I can see that up to 255 secondary addresses should be supported (https://www.dell.com/support/manuals/da-dk/smartfabric-os10-emp-partner/smartfabric-os-user-guide-10-5-6/l3-mode-configuration?guid=guid-1d24ba07-ca00-426f-a282-badc584f034c&lang=en-us), but why would a secondary address not support routing for the client?

  2. Sub-interface. This option sounds very promising. However, I can't find any documentation on sub-interfaces. I have tried in the lab, but the command interface vlan 1116.1 throws an Illegal Parameter error.

  3. This sounds like the cable option; it still occupies a physical port but without the cable. Is it possible to keep the link up without a cable attached? While I can see the idea behind this, it does not scale. We would need to occupy a physical port for every PVLAN on which we need an IP Helper. Unfortunately, we are unable to do that.

 

Best regards,

Christopher de Haas

(edited)

No Events found!

Top