Bug 1380645

Summary: [RHEL Networking Guide] VLANs: please document how to set the interface's "switchport" mode
Product: Red Hat Enterprise Linux 7 Reporter: Răzvan Sandu <rsandu2004>
Component: doc-Networking_GuideAssignee: Ioanna Gkioka <igkioka>
Status: CLOSED CURRENTRELEASE QA Contact: Hannes Frederic Sowa <hsowa>
Severity: unspecified Docs Contact:
Priority: high    
Version: 7.4CC: alexandru.tote, hsowa, igkioka, mjahoda, mnavrati, rhel-docs, sukulkar
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-23 07:15:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1425467    

Description Răzvan Sandu 2016-09-30 08:58:14 UTC
Document URL: 

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7-Beta/html/Networking_Guide/ch-Configure_802_1Q_VLAN_Tagging.html

Section Number and Name: 

Chapter 7. Configure 802.1Q VLAN tagging

Describe the issue: 

The guide contains no information about setting a RHEL interface's "switchport mode", when the (Ethernet) interface is connected to a switch and there are VLANs running over that physical interface.

Usually, a RHEL server or workstation would be connected to only one VLAN: that probably means that "switchport mode access" would be suitable (and the default).

However, there are scenarios when multiple tagged VLANs would use the same physical link (Ethernet between the switch and RHEL machine), requiring "switchport mode trunk" to be configure at both ends.

One such scenario is that of the RHEL machine being used as a router: it will need to forward tagged packets from the various VLANs "behind" it to the switch, over the same physical Ethernet, still maintaining separation between those VLANs.


Suggestions for improvement: 

Please completely document:

- all the necessary parameters in /etc/sysconfig/network-scripts/ifcfg-interface files

- various commands (in CLI, text-inteface or GUI)

for unambiguosly setting the "switchport mode" of the inteface on the RHEL machine.


Additional information: 

http://www.ciscopress.com/articles/article.asp?p=29803&seqNum=2

http://www.developingthefuture.net/vlan-tutorial/

http://bradhedlund.com/2007/11/27/switchport-configurations-explained/

Comment 2 Răzvan Sandu 2017-03-03 08:55:21 UTC
Hello,

Summarizing this:

Red Hat Enterprise Linux machines (and other GNU/Linuxes) are often used as routers, so a more advanced VLAN configuration should be possible on their network interfaces.

Please document how to obtain, on a Red Hat Enterprise Linux Ethernet interface, the equivalent of the following Cisco commands (which are "common language" among network engineers and widely described in technical network literature):


vlan
vlan database

switchport mode access
switchport access vlan ID

switchport encapsulation (dot1q or isl)
switchport mode trunk
switchport trunk native vlan ID
switchport trunk allowed vlan IDs

switchport mode private-vlan

switchport voice


and their "no" counterparts.


Please see, as reference from other major providers:


https://supportforums.cisco.com/discussion/12476171/switch-port-modes

https://www.alliedtelesis.com/sites/default/files/gs900mx_command_ref_5.4.6-2.x_reva.pdf

https://www.alliedtelesis.com/sites/default/files/x510_command_ref_5.4.5-0.1_reva_0.pdf


Thank you,
Răzvan

Comment 3 Milan Navratil 2017-03-20 11:48:57 UTC
Hi Răzvan,

Thank you for reporting this docs BZ. I'll create a new section with an introduction based on the info you provided, and I'll set a needinfo on a Red Hat Subject Matter expert to determine the extent of the new section and then work on the content.

Please note that we are not trying to document absolutely all features with all options in Red Hat documentation. Instead, we are trying to prioritize appropriately by identifying user stories to enhance our documentation in order to provide guidance for situation and problems the users encounter.

I'll discuss with a Subject Matter Expert how to best handle this docs update, and we'll let you know in a public comment.

Thanks again for taking the time to file this BZ and helping us make Red Hat documentation awesome.

Comment 5 Hannes Frederic Sowa 2017-03-24 20:12:10 UTC
(In reply to Răzvan Sandu from comment #2)
> vlan
> vlan database

We don't have any equivalent commands and basically refer on how to list vlans on a local system. We might be able to talk a bit about GVRP a bit in here, depending on its status in NetworkManager?

> switchport mode access
> switchport access vlan ID
>
> switchport encapsulation (dot1q or isl)
> switchport mode trunk
> switchport trunk native vlan ID
> switchport trunk allowed vlan IDs

We can refer to: https://access.redhat.com/solutions/39674

> switchport mode private-vlan

For Layer two, we basically just need to enable routing instead of switching, weak end host model does the rest (in contrast to Cisco). On top of that either proxy_arp or simple routing with /32 addresses (if supported by the end operating system, otherwise /31).

> switchport voice

As far as I see, we miss support for cisco discovery protocol. We provide LLDP instead, but AFAIK there is no integration with LLDP and Cisco's voice capabilities.

Voice VLANs also have a lot to do with 802.1P and we don't support QoS and vlan priorities out of the box. We might be able to come up with special tc/qdisc setups upon providing more details. But there is no single-click feature we can offer right now.

Comment 6 Răzvan Sandu 2017-04-05 14:11:54 UTC
Hello,

@Milan Navratil

Thank you for your kind response!

In today's high density networks, using VLANs is not uncommon; in fact, these are basic networking tasks, such as assigning IP addreses.

So a user must know how to:

- connect his RedHat workstation to a given VLAN (the "switchport access" case)

- send (or forward, if the system is used as a router) packets for *multiple* VLANs on a single interface (the "switchport trunk" case).


This is pretty common, should be well-known and easily feasible.


Thanks again,
Răzvan

Comment 8 Hannes Frederic Sowa 2017-06-26 11:53:50 UTC
Hello Răzvan Sandu,

please also have a look at comment #5, which I just made public.

(In reply to Răzvan Sandu from comment #6)
> In today's high density networks, using VLANs is not uncommon; in fact,
> these are basic networking tasks, such as assigning IP addreses.
> 
> So a user must know how to:
> 
> - connect his RedHat workstation to a given VLAN (the "switchport access"
> case)
> 
> - send (or forward, if the system is used as a router) packets for
> *multiple* VLANs on a single interface (the "switchport trunk" case).

Both of these should be pretty easy to configure with either iproute or in NetworkManager. Basically it is about just adding interfaces and enabling forwarding. I hope the comment in #5 helped you. If not, please let us know.

Bye,
Hannes