RHEL 802.1q / VLAN Tagging - Revision history

Hutch: /* Current boot environment */

Hutch — Wed, 02 Apr 2008 19:47:13 GMT

Current boot environment

←Older revision		Revision as of 19:47, 2 April 2008
Line 20:		Line 20:

	* Configure the VLAN device.		* Configure the VLAN device.
-	# '''ifconfig bond0.1100 10.216.225.1 255.255.240.0 up'''	+	# '''ifconfig bond0.1100 10.216.225.1 netmask 255.255.240.0 up'''

	=== Preserving the changes across system boots ===		=== Preserving the changes across system boots ===

Hutch: /* If you don't use a native VLAN */

Hutch — Fri, 21 Mar 2008 15:40:11 GMT

If you don't use a native VLAN

←Older revision		Revision as of 15:40, 21 March 2008
Line 42:		Line 42:
	* Use ''GATEWAYDEV=bond0.825'' in ''/etc/sysconfig/network'' so that the default route uses a tagged interface. I believe the default route would otherwise have used the untagged ''bond0'' interface, which would cause problems communicating with other networks.		* Use ''GATEWAYDEV=bond0.825'' in ''/etc/sysconfig/network'' so that the default route uses a tagged interface. I believe the default route would otherwise have used the untagged ''bond0'' interface, which would cause problems communicating with other networks.
	* Potentially remove the network route 10.216.16.0/20 through interface ''bond0''. When bringing up ''bond0'', which is a prerequisite to bringing up ''bond0.1100'', the network route 10.216.16.0/20 through device ''bond0'' is created. When bringing up ''bond0.825'', the network route 10.216.16.0/20 through device ''bond0.825'' is created. Having the same route with different devices appears to cause problems; I had to manually delete route 10.216.16.0/20 through device ''bond0'' to make this work.		* Potentially remove the network route 10.216.16.0/20 through interface ''bond0''. When bringing up ''bond0'', which is a prerequisite to bringing up ''bond0.1100'', the network route 10.216.16.0/20 through device ''bond0'' is created. When bringing up ''bond0.825'', the network route 10.216.16.0/20 through device ''bond0.825'' is created. Having the same route with different devices appears to cause problems; I had to manually delete route 10.216.16.0/20 through device ''bond0'' to make this work.
-
-	Manually remove the network route 10.216.
-
-	* I'd have to configure a ''bond0.825'' interface.
-	* I'd have to use '''GATEWAYDEV=bond0

Hutch at 15:39, 21 March 2008

Hutch — Fri, 21 Mar 2008 15:39:57 GMT

←Older revision		Revision as of 15:39, 21 March 2008
Line 34:		Line 34:
	USERCTL=no		USERCTL=no
	'''VLAN=yes'''		'''VLAN=yes'''
		+
		+	== If you don't use a native VLAN ==
		+
		+	If you do not use a native VLAN, the configuration is a bit more complex. In this example, I'd have to:
		+
		+	* Configure a ''bond0.825'' interface.
		+	* Use ''GATEWAYDEV=bond0.825'' in ''/etc/sysconfig/network'' so that the default route uses a tagged interface. I believe the default route would otherwise have used the untagged ''bond0'' interface, which would cause problems communicating with other networks.
		+	* Potentially remove the network route 10.216.16.0/20 through interface ''bond0''. When bringing up ''bond0'', which is a prerequisite to bringing up ''bond0.1100'', the network route 10.216.16.0/20 through device ''bond0'' is created. When bringing up ''bond0.825'', the network route 10.216.16.0/20 through device ''bond0.825'' is created. Having the same route with different devices appears to cause problems; I had to manually delete route 10.216.16.0/20 through device ''bond0'' to make this work.
		+
		+	Manually remove the network route 10.216.
		+
		+	* I'd have to configure a ''bond0.825'' interface.
		+	* I'd have to use '''GATEWAYDEV=bond0

Hutch: /* Preserving the changes across system boots */

Hutch — Fri, 21 Mar 2008 15:21:46 GMT

Preserving the changes across system boots

←Older revision		Revision as of 15:21, 21 March 2008
Line 25:		Line 25:

	To preserve the 802.1 configuration changes across reboots, create appropriate ''/etc/sysconfig/network-scripts'' files.		To preserve the 802.1 configuration changes across reboots, create appropriate ''/etc/sysconfig/network-scripts'' files.
-
-	e.g., ''/etc/sysconfig/network-scripts/ifcfg-bond0.825''
-	DEVICE=bond0.825
-	IPADDR=10.216.16.49
-	NETMASK=255.255.240.0
-	GATEWAY=10.216.16.1
-	ONBOOT=yes
-	BOOTPROTO=static
-	USERCTL=no
-	'''VLAN=yes'''

	e.g., ''/etc/sysconfig/network-scripts/ifcfg-bond0.1100''		e.g., ''/etc/sysconfig/network-scripts/ifcfg-bond0.1100''

Hutch: /* Current boot environment */

Hutch — Fri, 21 Mar 2008 15:21:09 GMT

Current boot environment

←Older revision		Revision as of 15:21, 21 March 2008
Line 16:		Line 16:
	# '''modprobe 8021q'''		# '''modprobe 8021q'''

-	* Create a VLAN device on the ''bond0'' interface for ~~both VLANs~~.	+	* Create a VLAN device on the ''bond0'' interface for VLAN 1100.
-	~~# '''vconfig add bond0 825'''~~	+
	# '''vconfig add bond0 1100'''		# '''vconfig add bond0 1100'''

-	* Configure the VLAN ~~devices~~.	+	* Configure the VLAN device.
-	~~# '''ifconfig bond0.825 10.216.16.48 255.255.240.0 up'''~~	+
	# '''ifconfig bond0.1100 10.216.225.1 255.255.240.0 up'''		# '''ifconfig bond0.1100 10.216.225.1 255.255.240.0 up'''

Hutch: /* Procedure */

Hutch — Fri, 21 Mar 2008 15:20:11 GMT

Procedure

←Older revision		Revision as of 15:20, 21 March 2008
Line 7:		Line 7:
	== Procedure ==		== Procedure ==

-	Note: Once your network administrator enables 802.1q on the switch, your system ~~will appear to~~ "fall off" the network~~. It~~ won't know how to handle VLAN ~~tagged~~-frames until you perform the below steps.	+	Note: Once your network administrator enables 802.1q on the switch, your system may "fall off" the network if its network interface is not on the native VLAN (if applicable), as the host won't know how to handle VLAN-tagged frames until you perform the below steps.

	=== Current boot environment ===		=== Current boot environment ===

Hutch: /* Overview */

Hutch — Fri, 21 Mar 2008 15:18:38 GMT

Overview

←Older revision		Revision as of 15:18, 21 March 2008
Line 2:		Line 2:

	In this example on a RHEL 5 system, I take a bonded (mode 6, balance-alb) network interface and enable 802.1q, or "VLAN tagging." The bonded interface will be a member of two VLANs:		In this example on a RHEL 5 system, I take a bonded (mode 6, balance-alb) network interface and enable 802.1q, or "VLAN tagging." The bonded interface will be a member of two VLANs:
-	* The "native VLAN" (825). Frames for the native VLAN are not tagged, so no special configuration has to be performed for this VLAN. The ''bond0'' interface is on the native VLAN with IP address 10.216.16.48 and netmask 255.255.240.0.	+	* The "native VLAN" (in this example, VLAN 825). Frames for the native VLAN are not tagged, so no special configuration has to be performed for this VLAN. The ''bond0'' interface is on the native VLAN with IP address 10.216.16.48 and netmask 255.255.240.0.
	* VLAN 1100 with IP address 10.216.225.1 and netmask 255.255.240.0		* VLAN 1100 with IP address 10.216.225.1 and netmask 255.255.240.0

Hutch: /* Overview */

Hutch — Fri, 21 Mar 2008 15:18:15 GMT

Overview

←Older revision		Revision as of 15:18, 21 March 2008
Line 1:		Line 1:
	== Overview ==		== Overview ==

-	In this example on a RHEL 5 system, I take ~~an interface that is~~ bonded ~~with~~ mode 6 (balance-alb) and enable 802.1q, or "VLAN tagging." The bonded interface will be a member of two VLANs:	+	In this example on a RHEL 5 system, I take a bonded (mode 6, balance-alb) network interface and enable 802.1q, or "VLAN tagging." The bonded interface will be a member of two VLANs:
-	* VLAN 825 with IP address 10.216.16.48 and netmask 255.255.240.0	+	* The "native VLAN" (825). Frames for the native VLAN are not tagged, so no special configuration has to be performed for this VLAN. The ''bond0'' interface is on the native VLAN with IP address 10.216.16.48 and netmask 255.255.240.0.
	* VLAN 1100 with IP address 10.216.225.1 and netmask 255.255.240.0		* VLAN 1100 with IP address 10.216.225.1 and netmask 255.255.240.0
-
-	The current interface is ''bond0'' with an IP address of 10.216.16.48 and netmask of 255.255.240.0.

	== Procedure ==		== Procedure ==

Hutch: New page: == Overview == In this example on a RHEL 5 system, I take an interface that is bonded with mode 6 (balance-alb) and enable 802.1q, or "VLAN tagging." The bonded interface will be a member...

Hutch — Thu, 20 Mar 2008 19:40:43 GMT

New page: == Overview == In this example on a RHEL 5 system, I take an interface that is bonded with mode 6 (balance-alb) and enable 802.1q, or "VLAN tagging." The bonded interface will be a member...

New page

== Overview ==

In this example on a RHEL 5 system, I take an interface that is bonded with mode 6 (balance-alb) and enable 802.1q, or "VLAN tagging." The bonded interface will be a member of two VLANs:
* VLAN 825 with IP address 10.216.16.48 and netmask 255.255.240.0
* VLAN 1100 with IP address 10.216.225.1 and netmask 255.255.240.0

The current interface is ''bond0'' with an IP address of 10.216.16.48 and netmask of 255.255.240.0.

== Procedure ==

Note: Once your network administrator enables 802.1q on the switch, your system will appear to "fall off" the network. It won't know how to handle VLAN tagged-frames until you perform the below steps.

=== Current boot environment ===

The following steps will enable 802.1q for your current session. The configuration will not be preserved across reboots.

* Enable the ''8021q'' kernel module.
# '''modprobe 8021q'''

* Create a VLAN device on the ''bond0'' interface for both VLANs.
# '''vconfig add bond0 825'''
# '''vconfig add bond0 1100'''

* Configure the VLAN devices.
# '''ifconfig bond0.825 10.216.16.48 255.255.240.0 up'''
# '''ifconfig bond0.1100 10.216.225.1 255.255.240.0 up'''

=== Preserving the changes across system boots ===

To preserve the 802.1 configuration changes across reboots, create appropriate ''/etc/sysconfig/network-scripts'' files.

e.g., ''/etc/sysconfig/network-scripts/ifcfg-bond0.825''
DEVICE=bond0.825
IPADDR=10.216.16.49
NETMASK=255.255.240.0
GATEWAY=10.216.16.1
ONBOOT=yes
BOOTPROTO=static
USERCTL=no
'''VLAN=yes'''

e.g., ''/etc/sysconfig/network-scripts/ifcfg-bond0.1100''
DEVICE=bond0.1100
IPADDR=10.216.225.1
NETMASK=255.255.240.0
ONBOOT=yes
BOOTPROTO=static
USERCTL=no
'''VLAN=yes'''