vlans

5 More Discussions You Might Find Interesting

1. Proxy Server

Linux Networking - VLANs & Multiple IP's

In a "typical" data centre environment (telco, financial services etc), would a Linux OS typically have one IP address connected to one VLAN or would it have many IPs and/or VLANs. I say "Linux OS" as I'm referring to an instance of the OS not necessarily a Host or server. Think Linux OS = VM in a...

2. IP Networking

VLANs and their domains

Hey everyone. I work in a data center, and I'm working on getting my CCNA. Now when I read articles on the idea of VLAN's it makes sense. Especially if you have multiple switches daisy chained in multiple locations. My two main questions though are that most of these examples use PC's as examples...

3. Solaris

Oracle VMs and VLANs

I've been given an IP address to assign to an ldom that is in a different subnet than the host, and I am looking for assistance in getting it online. I believe I need "VLAN tagging" as found in this link, but I do not understand all of the terminology. My host machine is on subnet 10.25.112.x,...

4. UNIX for Dummies Questions & Answers

Help with VLANs

Hi Gurus, Can anyone explain me what is a Vlan and a Native vlan. How to check the native Vlan on my server having a solaris10 OS. Thanks in advance.:)

5. AIX

AIX / Etherchannel / VLANs

I have 1 AIX server, 4 dual ported fiber attached ethernet cards and 4 VLANS coming in. Is it possible to present those 8 ports as 1 IP address using etherchannel? Thanks.

LEARN ABOUT SUSE

ifcfg-vlan

IFCFG-VLAN(5)						       Network configuration						     IFCFG-VLAN(5)

NAME

       ifcfg-vlan - virtual LAN interface configuration

SYNOPSIS

       /etc/sysconfig/network/ifcfg-vlan*

Virtual LANs (802.1q)
       To setup a vlan interface you need a configuration file that contains at least the mandatory

       ETHERDEVICE
	      variable with the real interface used for the virtual LAN.

       Further, it may contain the optional

       VLAN_ID
	      variable that specifies the VLAN ID.

       By default and when the VLAN_ID variable is not set, the number at the end of the interface name is the VLAN ID.

       Preferably the interface name and the configuration file follow the VLAN interface name scheme (type), that is either:
	      ifcfg-vlan<VLAN-ID> (e.g. ifcfg-vlan42)

	      or

	      ifcfg-name.<VLAN-ID> (e.g. ifcfg-eth0.42)

       The VLAN-ID can be also 0-padded (e.g. ifcfg-vlan0042 or ifcfg-eth0.0042).

       Also  in case of custom names, trailing digits are interpreted as VLAN-ID by default (e.g. ifcfg-dmz42). When VLAN_ID is set in the config,
       the interface name have any name (e.g. ifcfg-foobar).

       Note: The drawback of custom interface names and VLAN_ID usage is, that a rename of the interface is required and  that	they  violate  the
       name scheme.

       The  real  interface will be set UP automatically and doesn't need a config file in case of a physical interface. But without a config file
       YaST will consider this interface as unused, if will not follow hotplug	events	and  you're  unable  to  apply	any  settings,	e.g.  ETH-
       TOOL_OPTIONS. To avoid that, provide an config file with at least STARTMODE='auto'.

       The  rest  of  the VLAN interface IP and routes configuration do not differ from ordinary interfaces. See also man ifcfg and man routes for
       details.

EXAMPLES

       Sets up vlan3 vlan interface on top of eth0:

	      ifcfg-vlan3
		 STARTMODE='auto'
		 ETHERDEVICE='eth0'
		 IPADDR='192.168.3.27/24'

       Sets up eth0.3 vlan interface on top of eth0:

	      ifcfg-eth0.3
		 STARTMODE='auto'
		 ETHERDEVICE='eth0'
		 IPADDR='192.168.3.27/24'

       Sets up lan1 vlan interface with ID 42 on top of eth0:

	      ifcfg-lan1
		 STARTMODE='auto'
		 ETHERDEVICE='eth0'
		 VLAN_ID='42'
		 IPADDR='192.168.3.27/24'

BUGS

       Please report bugs at <http://www.suse.de/feedback>

AUTHOR

       Christian Zoz <zoz@suse.de>
       Michal Svec <msvec@suse.cz>
       Bjoern Jacke
       Mads Martin Joergensen <mmj@suse.de>
       Michal Ludvig <mludvig@suse.cz>
       Marius Tomaschewski <mt@suse.de>

SEE ALSO

       routes(5), ifcfg(5), ifup(8).

sysconfig							    August 2004 						     IFCFG-VLAN(5)

IP Networking