Context Navigation

CLISetup

Timestamp:: Jan 27, 2010, 8:07:50 AM (15 years ago)
Author:: akoshibe
Comment:: —

Legend:

: Unmodified
: Added
: Removed
: Modified

Internal/OpenFlow/CLISetup

-              v26
+              v27
 == User modes and contexts ==
+'''Super user mode.'''
 As with Cisco switches, you must be in privileged mode to make any configuration changes on the switch (or see the full list of commands). The magic word is "enable".
 {{{
 > ena     <<---whole command is 'enable'
+> ena     <<---whole command is 'enable' -- the switch autocompletes commands.
+#
 }}}
+Note how the switch autocompletes commands; you don't need to type the whole command. "configure" brings you to the configuration prompt, which looks like this :
+'''Configuration mode and Contexts.'''
+All configurations, from port speed to the MoTD banner, are done from the configuration prompt. The command "configure" brings you to the prompt, which looks like this :
 {{{
 # config
 …
 }}}
-All configurations, from port speed to the MoTD banner, are done from here.
 Here, typing different sets of commands bring you to different configuration modes specific to the feature you are trying to modify. the commands that bring you to the specialized modes are called "contexts," and typing them are called "entering a context." Some contexts we want to focus on are:
+{{{
  - `vlan n` - create/configure standard VLANs, n being the VLAN ID (some number)
  - `interface vlan n` - create/ configure a virtual interface with both Layer 2 and 3 characteristics
  - `interface gigabitethernet 0/n` - configure specific port, n being number between 1 and 48
  - `line <vty|console> vtyrange<0-b>` - configure telnet or console parameters, respectively
+}}}
+ * `vlan n` - create/configure standard VLANs, n being the VLAN ID (some number)
+ * `interface vlan n` - create/ configure a virtual interface with both Layer 2 and 3 characteristics
+ * `interface gigabitethernet 0/n` - configure specific port, n being number between 1 and 48
+ * `line <vty|console> vtyrange<0-b>` - configure telnet or console parameters, respectively
 Don't worry even if these don't make sense now - The meanings of the contexts will be explained as we introduce each context.
+As you can see, when you enter a context, the prompt becomes "(config-if)#." However, this prompt doesn't indicate what context you are using; you just have to remember what you are doing. If you forget where you were, typing "show" will display all of the configurations saved for that specific context (hopefully giving you enough information to let you recall what you were trying to do).
+As you can see, when you enter a context, the prompt becomes "(config-if)#." Note, however, this prompt doesn't indicate what context you are using (i.e. which port you are setting up, what VLAN, ect); you just have to keep track of what you are doing.
 {{{
 (config)# interface vlan 8              <<---start by entering the 'interface vlan' context
 …
 }}}
+As you can see above, when you make changes to the configurations (e.g. create vlan interfaces as in this example), you will see a "!" before the prompt. This is there to remind you that you've made changes that must be saved if you want them to survie a reboot. The command "save" intuitively saves the settings.
+If you forget where you were in a context (i.e. which vlan you were configuring, ect.), typing "show" will display all of the configurations saved for that specific context (hopefully giving you enough information to let you recall what you were trying to configure).
+{{{
+(config-if)# show
+interface gigabitethernet 0/27
+  switchport mode access
+  switchport access vlan 4
+!
+}}}
+When you make changes to the configurations (e.g. create vlan interfaces as in this example), you will see a "!" before the prompt. This is there to remind you that you've made changes that must be saved if you want them to survie a reboot. The command "save" intuitively saves the settings.
+'''exiting/ logging off.'''
 The command `exit` lets you exit from contexts and enabled mode, or lets you log out of the switch if you were just in user mode.
 {{{
 …
 }}}
+=== Available commands / help pages ===
+=== Finding help/ Some tips. ===
+'''Using the built-in help functionalities.'''
 Like with Cisco switches, typing `?` at the prompt will list the available commands along with a brief summary. If you are in a certain context, typing `?` will show you configuration options available for that context.
+=== switching contexts and autocompletion ===
+==== switching contexts and autocompletion ====
 From the initial configuration prompt, you can let the switch autocomplete contexts. For example:
 {{{
 …
 !(config)#
 }}}
 . Assign an IP address to the VLAN. By entering the "interface vlan" context you automatically turn VLAN 4 into a VLAN interface.
+. Assign an IP address to the VLAN.
 {{{
 !(config)# interface vlan 4
 …
  * classic VLANs - http://en.wikipedia.org/wiki/Virtual_LAN
  * tagging/trunking - http://en.wikipedia.org/wiki/IEEE_802.1Q
+ * native VLANs -
 ==== VLANs ====
 …
 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.
 === Creating/ Configuring VLANs and Interface VLANs ===
+=== Creating/ Using VLANs and Interface VLANs ===
 The following steps outline the general configuration of VLANs and interface VLANs through the CLI.
 …
 }}}
+This cannot be done with interface VLANs (although you can configure multiple interface VLANs at once, if they exist, using context "interface range vlan <range>"). Hence when we need to generate many VLANs, we'd first create them with "vlan 1-n", then configure the VLANs as interface VLANs later.
+. '''Asssociate Ports.'''
+ There are also contexts that support ranges of interfaces/ports/VLANs. For example, to configure ports 1-4 and 30 at once:
+This cannot be done with interface VLANs (see step 3 for details and caveats)
+. '''Associate Ports.''' A VLAN is fairly useless without hosts. Hosts become part of a VLAN if they are connected to a port associated with it. By default, all ports on the IP8800 are associated to VLAN 1,so you must specify which ports are associated with which VLAN manually. Here we associate port 0/25 with the VLAN we just created.
+{{{
+(config)# int gi 0/25
+(config-if)# switchport mode access
+(config-if)# swi acc vlan 3           <<-- full command is "switchport access vlan 3"
+(config-if)# exit
+}}}
+ * "switchport mode access" means that the port only has access to the VLAN 3 that exists on the local switch (no trunking - see next section )
+ * "switchport access vlan 3" means that this port has access to VLAN 3
+As with the VLANs, we can configure more than one port at a time using the "interface range" context. For example, to configure ports 1-4 and 30 at once:
 {{{
  sw-sb09(config)# int range gigabitethernet 0/1-4, gigabitethernet 0/30
  sw-sb09(config-if-range)#
 }}}
+Note how the prompt becomes "(config-if-range)" in this case.
+Note how the prompt becomes "(config-if-range)" in this case. The exact same sets of commands apply to this context as for the single-port context.
+. '''Configure the interface VLAN.''' If we need an IP address or some other higher-layer characteristic associated with our VLAN, we create an interface VLAN of the same VLAN ID (number) as the VLAN, and configure it. So, to assign an IP address to VLAN 3:
+{{{
+(config)# interface vlan 3
+!(config-if)# ip address 172.16.100.10 255.255.255.0
+!(config-if)# exit
+!(config)#
+}}}
+When the "interface vlan" context is entered for a VLAN ID that the switch doesn't know about, a new interface VLAN and VLAN of that ID are created automatically. But, as stated before, the "interface range vlan" context cannot be used to create multiple interface VLANs at once. This range context is used when configuring multiple interface VLANs at once, ''given'' that the range of VLAN IDs exist on the switch. Hence, if we want to configure multiple interface VLANs at once, we must first create the VLANs using the "VLAN <range>" context.
+=== Configuring Trunking ===