Context Navigation

CLISetup

Timestamp:: Jan 21, 2010, 7:45:42 AM (14 years ago)
Author:: akoshibe
Comment:: —

Legend:

: Unmodified
: Added
: Removed
: Modified

Internal/OpenFlow/CLISetup

-              v22
+              v23
 == Elucidation (Or, How-TO's) ==
+As of now, this is just a conglomeration of facts and hints on how to configure the IP8800. Before we begin, here are the assumptions that are made throughout these pages:
+ * You are running Linux (We are, for the most part, using Ubuntu unless specified)
+The IP8800/S3640-48T2XW and IP8800/S3640-24T2XW are the two models of NEC switch that support !OpenFlow. "Smart" switches like the IP8800 must be configured via a command line before they can be used.
+As of now, this is just a conglomeration of facts and hints on how to configure the 48-port IP8800/S3640-48T2XW. Before we begin, here are the assumptions that are made throughout these pages:
+ * You are running/know how to get around Linux (We are, for the most part, using Ubuntu unless specified)
  * You are using the NEC IP8800/S3640-48T2XW switch.
+ * You know network models (e.g. TCP/IP, OSI)
 == Section 1: The Basics ==
 "Smart" switches like the IP8800 must be configured via a command line before they can be used. If you are unfamiliar with "smart" switches and how to configure them, this is the place to start. This section coveres the following:
+If you are unfamiliar with "smart" switches or how to configure them, this is the place to start. This section covers the following:
  * Logging in for the first time (through serial)
  * Admin modes and intro to contexts
  * VLANs and ports
+ * VLANs, VLAN interfaces, and ports
+ * User modes and contexts
 === 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 make configuration changes by logging into the switch via the console 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. If not already installed on your box, the Debian package for kermit is ckermit.
+. 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.
+. Connect via serial using the following commands at the console (Make sure you are root):
+Out of the box, the switches are not configured for Telnet. In this case, you need to make configuration changes by logging into the switch via the console 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.
+. '''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.
+. '''Install kermit.''' If not already installed on your box, the Debian package for kermit is ckermit, and can be easily installed with the command:
+ sudo apt-get install ckermit
+. '''Establish a connection.''' Connect your PC to the port labeled "console" on the switch using the RS-232 cable, and issue the following commands as root:
 {{{
  /$ kermit
 …
 `Ctrl-\ q` ends the kermit session.
+=== Admin modes, contexts ===
+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". Note how the switch does autocompletion; you don't need to type the whole command:
+{{{
+> ena     <<---whole command is 'enable'
+#
+}}}
+"configure" brings you to the configuration prompt, which looks like this :
+{{{
+# config
+(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 throughout these pages 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>` - 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 they are introduced.
+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.
+{{{
+(config)# interface vlan 8              <<---start by entering the 'interface vlan' context
+(config-if)#
+(config-if)# interface gi 0/3           <<---switch to 'interface gigabitethernet' context
+(config-if)#                            <<---note how prompt still shows up as "config-if"
+}}}
+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. 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.
+=== VLANs and ports. ===
+==== Troubleshooting ====
+Make sure you are root when you start up kermit.
+Kermit will balk if you try to log in while there is a session going on. Make sure that no one else is logged in via serial, and that you haven't forgotten to log out during a previous session.
+If, for some reason, you can't use kermit or have to configure the settings for your serial connection, use the following settings:
+ * speed: 9600
+ * data bits: 8
+ * stop bits: 1
+ * Flow control: none
+ * Parity: none
+Note, we have found that minicom doesn't seem to work too well with the switches. If you get it to work, please note it!
+=== 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:
+ * classic VLANs - http://en.wikipedia.org/wiki/Virtual_LAN
+ * tagging/trunking - http://en.wikipedia.org/wiki/IEEE_802.1Q
 ==== ports ====
+There are 48 RJ-45 1 GBps 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. The command "show port status" can be used to look at this:
+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
 …
 / 3 geth0/3        up     Tx        948982         581      437194           0
                             Rx         81584           0        2294           2
+/ 4 geth0/4        down   Tx             0           0           0           0
+ ...
+/47 geth0/47       down   Tx             0           0           0           0
                             Rx             0           0           0           0
+/ 5 geth0/5        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
 …
                             Rx             0           0           0           0
 }}}
+'geth' refers to the 1GBps RJ-45 ports, and 'tengeth' refers to the GBIC sockets. The numbers following the 'geth' or 'tengeth' denote which blade and where on the blade the port is located using the convention <blade/location>. The port locations are counted beginning the top left RJ-45 port, and end at the GBICs (ports 0/49 and 0/50).
+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:
+{{{
+sw-sb09# sh vlan
+Date 2010/01/20 03:12:01 UTC
+VLAN counts:6   VLAN tunneling enabled
+VLAN ID:1     Type:Port based      Status:Up
+  Learning:On            Tag-Translation:
+  BPDU Forwarding:       EAPOL Forwarding:
+  Router Interface Name:VLAN0001
+  IP Address:172.16.19.253/16                         <<---IP address of VLAN interface
+  Source MAC address: 0012.e2c8.1f9c(System)
+  Description:Network
+  Spanning Tree:
+  AXRP RING ID:      AXRP VLAN group:
+  GSRP ID:      GSRP VLAN group:    L3:
+  IGMP snooping:     MLD snooping:
+  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.
+==== VLANs ====
+These can become confusing quickly because based on different contexts, the switch handles them differently.
+==== 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.
+=== User modes and contexts ===
+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". Note how the switch autocompletes; you don't need to type the whole command:
+{{{
+> ena     <<---whole command is 'enable'
+#
+}}}
+"configure" brings you to the configuration prompt, which looks like this :
+{{{
+# config
+(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>` - 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 they are introduced.
+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.
+{{{
+(config)# interface vlan 8              <<---start by entering the 'interface vlan' context
+(config-if)#
+(config-if)# interface gi 0/3           <<---switch to 'interface gigabitethernet' context
+(config-if)#                            <<---note how prompt still shows up as "config-if"
+}}}
+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. 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.
  * 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).