VLAN Interfaces
When it is necessary to provide a system access to one of the defined VLANs without having an available network interface, create the virtual interface on the primary ethernet interface. The VLANs defined for WilliamsNet are:
| VLAN number | VLAN name | IP subnet | VLAN purpose |
|---|---|---|---|
| 1 | HomeNet | 10.0.0.0/24 | Primary VLAN |
| 10 | StorageNet | 10.1.0.0/24 | Private network for Development Cluster |
| 15 | SCSIVLAN | 10.2.0.0/24 | isolated VLAN for iSCSI Storage Traffic |
| 20 | MgmtVLAN | unused | |
| 21 | NodeBackbone | unused | |
| 22 | StorageVLAN | unused |
Note that all these are defined in the HP Procurve Switches (http://10.0.0.1 -- interface requires java plugins, and only accessible using IE 11)
When creating the virtual interface, ensure that the port used by the system is included in the 'tagged' definition for the appropriate VLAN in the ProCurve VLAN configuration.
Debian/Ubuntu
The following is excerpted from https://wiki.debian.org/NetworkConfiguration#Bridges_and_VLANs
The interface can be set up manually using the following commands:
modprobe 8021q apt install vlan vconfig add eth0 222 # 222 is vlan number ifconfig eth0.222 up ifconfig eth0.222 10.10.10.1 netmask 255.255.255.0
As this will disappear with the next reboot, it is recommended to put the definition in the /etc/network/interfaces file:
auto eth0.222
iface eth0.222 inet static
address 10.10.10.1/24
vlan-raw-device eth0