Skip to main content
Network Engineering

Return to Answer

Post Timeline

added 82 characters in body
Source Link
Zac67 ♦
Zac67 ♦
  • 92.2k
  • 4
  • 76
  • 144

Your actual configs are missing from your question, so we can only provide general advice:

  • Tag VLANs between switches and routers (trunking) and use a single untagged VLAN on access port towards end nodes.
  • Configure tagged VLANs in exactly the same way on both sides of a link - switch ports use VLAN membership, routed ports most often subinterfaces.
  • Check VLAN connectivity by inspecting the MAC table on a switch, or ARP/NDP caches on routed interfaces.
  • Each node needs to be able to ping (or at least ARP) its default gateway.
  • Don't forget DHCP on extra VLANs for end nodes expecting automatic configuration - either a directly attached DHCP server or a DHCP relay.
  • VLANs need to be routed in between, either by an L3 switch or a router.
  • Don't forget to propagate new VLAN subnets to routers that are not directly attached. You can use static routes or a routing protocol like OSPF. Without proper routing, packets end up taking the default route.

Your actual configs are missing from your question, so we can only provide general advice:

  • Tag VLANs between switches and routers (trunking) and use a single untagged VLAN on access port towards end nodes.
  • Configure tagged VLANs in exactly the same way on both sides of a link - switch ports use VLAN membership, routed ports most often subinterfaces.
  • Check VLAN connectivity by inspecting the MAC table on a switch, or ARP/NDP caches on routed interfaces.
  • Don't forget DHCP on extra VLANs for end nodes expecting automatic configuration - either a directly attached DHCP server or a DHCP relay.
  • VLANs need to be routed in between, either by an L3 switch or a router.
  • Don't forget to propagate new VLAN subnets to routers that are not directly attached. You can use static routes or a routing protocol like OSPF. Without proper routing, packets end up taking the default route.

Your actual configs are missing from your question, so we can only provide general advice:

  • Tag VLANs between switches and routers (trunking) and use a single untagged VLAN on access port towards end nodes.
  • Configure tagged VLANs in exactly the same way on both sides of a link - switch ports use VLAN membership, routed ports most often subinterfaces.
  • Check VLAN connectivity by inspecting the MAC table on a switch, or ARP/NDP caches on routed interfaces.
  • Each node needs to be able to ping (or at least ARP) its default gateway.
  • Don't forget DHCP on extra VLANs for end nodes expecting automatic configuration - either a directly attached DHCP server or a DHCP relay.
  • VLANs need to be routed in between, either by an L3 switch or a router.
  • Don't forget to propagate new VLAN subnets to routers that are not directly attached. You can use static routes or a routing protocol like OSPF. Without proper routing, packets end up taking the default route.
added 117 characters in body
Source Link
Zac67 ♦
Zac67 ♦
  • 92.2k
  • 4
  • 76
  • 144

Your actual configs are missing from your question, so we can only provide general advice:

  • ConfigureTag VLANs between switches and routers (taggedtrunking) and use a single untagged VLAN on access port towards end nodes.
  • Configure tagged VLANs in exactly the same way on both sides of a link - switch ports use VLAN membership, routed ports most often subinterfaces.
  • Check VLAN connectivity by inspecting the MAC table on a switch, or ARP/NDP caches on routed interfaces.
  • Don't forget DHCP on extra VLANs for end nodes expecting automatic configuration - either a directly attached DHCP server or a DHCP relay.
  • VLANs need to be routed in between, either by an L3 switch or a router.
  • Don't forget to propagate new VLAN subnets to routers that are not directly attached. You can use static routes or a routing protocol like OSPF. Without proper routing, packets end up taking the default route.

Your actual configs are missing from your question, so we can only provide general advice:

  • Configure (tagged) VLANs in exactly the same way on both sides of a link - switch ports use VLAN membership, routed ports most often subinterfaces.
  • Check VLAN connectivity by inspecting the MAC table on a switch, or ARP/NDP caches on routed interfaces.
  • Don't forget DHCP on extra VLANs for end nodes expecting automatic configuration - either a directly attached DHCP server or a DHCP relay.
  • VLANs need to be routed in between, either by an L3 switch or a router.
  • Don't forget to propagate new VLAN subnets to routers that are not directly attached. You can use static routes or a routing protocol like OSPF. Without proper routing, packets end up taking the default route.

Your actual configs are missing from your question, so we can only provide general advice:

  • Tag VLANs between switches and routers (trunking) and use a single untagged VLAN on access port towards end nodes.
  • Configure tagged VLANs in exactly the same way on both sides of a link - switch ports use VLAN membership, routed ports most often subinterfaces.
  • Check VLAN connectivity by inspecting the MAC table on a switch, or ARP/NDP caches on routed interfaces.
  • Don't forget DHCP on extra VLANs for end nodes expecting automatic configuration - either a directly attached DHCP server or a DHCP relay.
  • VLANs need to be routed in between, either by an L3 switch or a router.
  • Don't forget to propagate new VLAN subnets to routers that are not directly attached. You can use static routes or a routing protocol like OSPF. Without proper routing, packets end up taking the default route.
Source Link
Zac67 ♦
Zac67 ♦
  • 92.2k
  • 4
  • 76
  • 144

Your actual configs are missing from your question, so we can only provide general advice:

  • Configure (tagged) VLANs in exactly the same way on both sides of a link - switch ports use VLAN membership, routed ports most often subinterfaces.
  • Check VLAN connectivity by inspecting the MAC table on a switch, or ARP/NDP caches on routed interfaces.
  • Don't forget DHCP on extra VLANs for end nodes expecting automatic configuration - either a directly attached DHCP server or a DHCP relay.
  • VLANs need to be routed in between, either by an L3 switch or a router.
  • Don't forget to propagate new VLAN subnets to routers that are not directly attached. You can use static routes or a routing protocol like OSPF. Without proper routing, packets end up taking the default route.