Changes between Version 27 and Version 28 of Internal/OpenFlow/CLISetup

Timestamp:

Jan 27, 2010, 10:57:05 AM (15 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/CLISetup

@@ -534 +534 @@
 In addition to the classic VLANs, the IP8800 also allows you to assign IP addresses and subnets to VLANs as if they are IP Layer constructs. These L2/L3 conglomerates are referred to as "interface VLANs", and give the switch extra functionality that would otherwise only be found in higher-layer devices. 
 
-Interface VLANs are also important because it provides a means to interact with a Layer 2 device (the switch) using Layer 3 means (IP). This is why we have to configure an interface VLAN in order to set up telnet. 
+Interface VLANs are also important because it provides a means to interact with a Layer 2 device (the switch) using Layer 3 means (IP). For example, The IP addresses used to uniquely identify each switch on the network is assigned to the switch via an interface VLAN. 
 
 === Creating/ Using VLANs and Interface VLANs ===
@@ -584 +584 @@
 
 === Configuring Trunking ===
+With the "access mode" ports in the previous section, VLANs with the same VLAN ID that are on different but connected switches would be recognized as different VLANs despite same VLAN ID. In order to allow the two same-ID VLANs to communicate with one another, we need to 1) set up trunking between the two switches, and 2) enable "dot1q tunneling" on the ports. 
+
+1. '''Configure the trunk port.''' Say that ports 0/45-48 are trunk ports:
+{{{
+!(config-if)# interface range gi 0/45-48
+!(config-if)# switchport mode trunk
+!(config-if)# switchport trunk allowed vlan 3,27,28
+}}}
+
+ * "interface range gi 0/45-48" - configure all four ports at once with "interface range" context
+ * "switchport mode trunk" - make the ports trunk ports
+ * "switchport trunk allowed vlan 3,27,28" - allow the trunk to only carry frames from VLANs 3,27,or 28
+
+'''Some extensions of the "switchport trunk allow" context."'''
+Yes, we know that you're thinking "wait, there's more?", but without these sub-contexts you'd have to undo the whole "switchport trunk allowed vlan" bit each time you need to add or remove VLANs from the access list. 
+
+Firstly, the switch's help output:
+{{{
+sw-sb09(config-if)# switchport trunk allowed vlan ?
+  <vlan id list>  <List style>. 1 to 4094. ex. "10-20", "30,40"
+  add             add the VLANs to use this port
+  remove          remove the VLANs to use these port
+}}}
+
+Summarized:
+ * "switchport trunk...vlan add <VLAN IDs> - add VLANs to your current list. 
+ * "switchport trunk...vlan remove <VLAN IDs> - remove VLANs from your current list     
+ 
+moving on...
+
+2. '''Configure the VLAN ports.''' The steps are same as configuring the ports for regular VLANs, except instead of "switchport mode access" we specify "switchport mode dot1q-tunnel" in this case:
+{{{
+ sw-sb09(config)# int range gigabitethernet 0/1-4, gigabitethernet 0/30
+ sw-sb09(config-if-range)# 
+}}} 
+
+3. '''Associate the trunk with a Native VLAN.''' Technially speaking, native VLANs allows hosts that do not understand tagging to function on a network implementing VLAN tagging. In context of the switch, the native VLAN is much like a trunk port version of an interface VLAN.