Context Navigation

CLISetup

Timestamp:: Jan 26, 2010, 1:55:29 AM (14 years ago)
Author:: yasaswiv
Comment:: —

Legend:

: Unmodified
: Added
: Removed
: Modified

Internal/OpenFlow/CLISetup

-              v25
+              v26
  * Using the serial connection to log in
+  * step-by-step
   * troubleshooting
  * User modes and contexts
 …
 ----
 == Logging into the switch for the first time. ==
+== Using serial to log in (Logging into the switch for the first time.) ==
 Out of the box, the switches are not configured for Telnet. In this case, you need to log into the switch using the serial port, which uses a standard RS-232 cable. You'll also need to have software installed on your PC to be able to establish a serial connection. Kermit is the recommended choice - it's default settings allow you to connect without changing anything.
+=== The Steps. ===
 . '''Name your switch.''' People names are easier to remember than IP addresses or machine-like names i.e. as01-hh-alex, and are easier to use in discussion if everyone agrees on names. Note, the names Bob, Nancy, and Andy are already taken.
 …
 . '''exiting.''' `Ctrl-\ q` ends the kermit session. The command `exit` or  `logout` will just log you out of the switch, but will not end the session.
 ==== Troubleshooting serial connections ====
+=== Troubleshooting serial connections ===
  * Make sure you are root when you start up kermit.
 …
 === switching contexts and autocompletion ===
 From the intitial configuration prompt, you can let the switch autocomplete contexts. For example:
+From the initial configuration prompt, you can let the switch autocomplete contexts. For example:
 {{{
 sw-sb09(config)# int gi 0/34     <<-- instead of "interface gigabitethernet 0/34"
 …
 }}}
 However, if you are already in a context, and you want to switch to another context, you must type the first word in full, else the switch will throw an error:
+However, if you are already in a context, and you want to switch to another context, you must type the first word in full, or else the switch will throw an error:
 {{{
 sw-sb09(config-if)# int gi 0/35
 …
 !(config)#
 }}}
 . Enable telnet logins to the switch. The "line vty" context allows you to do this. The numbers following the context denote which virtual terminals users can use to access the switch via telnet. Here, vty 0-2 can be used, meaning 3 users can simultaneously telnet into the switch.
+. Enable telnet logins to the switch. The "line vty" context allows you to do this. The numbers following the context denote the range of virtual terminals that the users have access to for telnet. Here, vty 0-2 can be used, meaning 3 users can simultaneously telnet into the switch.
 {{{
 !(config)# line vty 0 2
 !(config-line)# exit
 !(config)#
-!(config)# save
-(config)# exit
+#
 }}}
 …
 === Troubleshooting ===
  ...coming soon, if ever
+ ...coming soon, if ever.
 ----
+== Creating and configuring VLANs and VLAN interfaces ==
+ There are also contexts that support ranges of interfaces/ports/VLANs. 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.
+=== Ports, VLANs, VLAN interfaces ===
+Before we get to configuring things, we cover a few basics about ports and VLANs in terms of these switches. You should be familiar with the following before going through this section or on to configuration:
+== Creating and configuring VLANs and interface VLANs ==
+Here we cover the VLAN and interface VLAN in greater detail. You should be familiar with the following before going through this section or on to configuration:
  * classic VLANs - http://en.wikipedia.org/wiki/Virtual_LAN
  * tagging/trunking - http://en.wikipedia.org/wiki/IEEE_802.1Q
-==== ports ====
-By configuring the ports, you can control physical layer properties of the switch e.g. port speed, whether it is full or half duplex, and whether the port is up or down.
-There are 48 RJ-45 (Ethernet) 1GBps ports and two sockets for GBICs (10GBps fiber links) on the switch. The switch identifies the ports by giving them unique names based on their speed and location. RJ45 ports are geth0/1 through geth0/48, and the GBICs, tengeth0/49 and 0/50.
-The command "show port status" can be used to see this:
-{{{
-sw-sb09> sh po st
-Date 2010/01/18 05:44:23 UTC
-Port Counts: 50
-Port  Name           Status T/R  All packets   Multicast   Broadcast     Discard
-/ 1 geth0/1        up     Tx        950638         581      437112           0
-                            Rx         83404           0        2376           0
-/ 2 geth0/2        up     Tx        948981         581      437196           0
-                            Rx         81580           0        2292           0
-/ 3 geth0/3        up     Tx        948982         581      437194           0
-                            Rx         81584           0        2294           2
- ...
-/47 geth0/47       down   Tx             0           0           0           0
-                            Rx             0           0           0           0
-/48 geth0/48       up     Tx        281248          10        6975           0
-                            Rx       4358554     3135424      481238           0
-/49 tengeth0/49    down   Tx             0           0           0           0
-                            Rx             0           0           0           0
-/50 tengeth0/50    down   Tx             0           0           0           0
-                            Rx             0           0           0           0
-}}}
-The ports are counted beginning the top left RJ-45 at 0/1 and end at the lower right port at 0/48. If you look at the front of the switch you can see that they are labeled above the link lights of each of the pairs of ports.
 ==== VLANs ====
 In the context of switching, VLANs tie Layer 1 with Layer 2 by assigning each port a VLAN. A host connected to a port assigned to VLAN n will become a member of that VLAN. The VLANs on a switch can be seen with the command `show vlan` under enabled (super user) mode:
+In the context of switching, VLANs tie Layer 1 with Layer 2 by assigning each port a VLAN. A host connected to a port assigned to VLAN n will become a member of that VLAN. The VLANs on a switch can be seen with the command "show vlan" under enabled (super user) mode:
 {{{
 sw-sb09# sh vlan
 …
   Untagged(10)  :0/39-48
 VLAN ID:3     Type:Port based      Status:Up
+  Learning:On            Tag-Translation:
+  BPDU Forwarding:       EAPOL Forwarding:
+  Router Interface Name:VLAN0003
+  IP Address:
+  Source MAC address: 0012.e2c8.1f9c(System)
+  Description:CM
+  Spanning Tree:
+  AXRP RING ID:      AXRP VLAN group:
 ...
+}}}
+Rest assured, there are many details in this output that you don't have to worry about.
+}}}
+==== VLAN interfaces ====
+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 "VLAN interfaces", and give the switch extra functionality that would otherwise only be found in higher-layer devices.
+VLAN interfaces are also important because it provides a means to interact with a Layer 2 device (the switch) using Layer 3 means (IP). Hence, you will need to deal with VLAN interfaces if you want to, say, use telnet to communicate with the switch.
+Otherwise, VLAN interfaces are handled like any other VLAN.
+==== Interface VLANs ====
+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.
+=== Creating/ Configuring VLANs and Interface VLANs ===
+The following steps outline the general configuration of VLANs and interface VLANs through the CLI.
+. '''Creating VLANs.''' Entering the "vlan n" context creates a new VLAN when VLAN n doesn't exist already. Here we create VLAN 3, and name it "CM".
+{{{
+(config)# vlan 3
+!(config-vlan)# name "CM"
+!(config-vlan)# exit
+}}}
+Many VLANs can be created at once by denoting a range of VLANs when entering a context:
+{{{
+(config)# vlan 1-8          <<--create 8 VLANs numbered 1 through 8
+!(config-vlan)#
+}}}
+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:
+{{{
+ 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.
+==== ports ====
+By configuring the ports, you can control physical layer properties of the switch e.g. port speed, whether it is full or half duplex, and whether the port is up or down.
+There are 48 RJ-45 (Ethernet) 1GBps ports and two sockets for GBICs (10GBps fiber links) on the switch. The switch identifies the ports by giving them unique names based on their speed and location. RJ45 ports are geth0/1 through geth0/48, and the GBICs, tengeth0/49 and 0/50.
+The command "show port status" can be used to see this:
+{{{
+sw-sb09> sh po st
+Date 2010/01/18 05:44:23 UTC
+Port Counts: 50
+Port  Name           Status T/R  All packets   Multicast   Broadcast     Discard
+/ 1 geth0/1        up     Tx        950638         581      437112           0
+                            Rx         83404           0        2376           0
+/ 2 geth0/2        up     Tx        948981         581      437196           0
+                            Rx         81580           0        2292           0
+/ 3 geth0/3        up     Tx        948982         581      437194           0
+                            Rx         81584           0        2294           2
+ ...
+/47 geth0/47       down   Tx             0           0           0           0
+                            Rx             0           0           0           0
+/48 geth0/48       up     Tx        281248          10        6975           0
+                            Rx       4358554     3135424      481238           0
+/49 tengeth0/49    down   Tx             0           0           0           0
+                            Rx             0           0           0           0
+/50 tengeth0/50    down   Tx             0           0           0           0
+                            Rx             0           0           0           0
+}}}
+The ports are counted beginning the top left RJ-45 at 0/1 and end at the lower right port at 0/48. If you look at the front of the switch you can see that they are labeled above the link lights of each of the pairs of ports.
  * Virtual interfaces - Also called "VLANs" by the switch. They do function as VLANs in the traditional sense, but in this case, are also associated with IP addresses used by the switch (i.e. the IP address used when telnetting).