Context Navigation

CLISetup

Timestamp:: Jan 24, 2010, 4:39:41 PM (14 years ago)
Author:: akoshibe
Comment:: —

Legend:

: Unmodified
: Added
: Removed
: Modified

Internal/OpenFlow/CLISetup

-              v23
+              v24
 = Configuring the switch through command line interface (CLI) =
+= Configuring the switch through command line interface (CLI) =
 The IP8800/S3640-48T2XW and IP8800/S3640-24T2XW are the two models of NEC switch that support !OpenFlow. This page is a how-to/log on configuring the IP8800/S3640-48T2XW NEC switch through the CLI.
 …
  * You know network models (e.g. TCP/IP, OSI)
+----
 == Section 1: The Basics ==
 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)
  * VLANs, VLAN interfaces, and ports
+ * Logging in for the first time (serial connection)
+  * troubleshooting the connection
  * User modes and contexts
+=== Logging into the switch for the first time. ===
+ * Creating and configuring VLANs and VLAN interfaces
+ * Setting up Telnet
+----
+== 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.
 …
 . '''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
+. '''Install kermit.''' If not already installed on your box, the Debian package for kermit is ckermit, and can be easily installed with apt-get.
 . '''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:
 …
 }}}
 Or, you can use the shorthand for the above:
+Or, you can use the shorthand one-liner:
 {{{
  kermit -l /dev/ttyS0
 …
 }}}
+`Ctrl-\ q` ends the kermit session.
+==== 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!
+. '''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 ====
+ * 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 you get a message like this with the one-liner of `kermit -l /dev/ttyS0`. :
+{{{
+?Carrier required but not detected.
+***********************************
+ Hint: To CONNECT to a serial device that
+ is not presenting the Carrier Detect signal,
+ first tell C-Kermit to:
+   SET CARRIER-WATCH OFF
+***********************************
+}}}
+ type the commands given above in lowercase.
+ * 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!
+----
+== 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".
+{{{
+> ena     <<---whole command is 'enable'
+#
+}}}
+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 :
+{{{
+# 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 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.
+{{{
+(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.
+[[BR]]
+----
+== Creating and configuring VLANs and VLAN interfaces ==
+[[BR]]
+----
+== Setting up Telnet ==
+Setting up telnet on the switch requires several steps that involve a few contexts. The steps can be outlined as the following:
+. Create a VLAN for telnet via the "vlan" context. For clarity (and good practice), we name our VLAN "telnet" so we know what it's used for.
+{{{
+(config)# vlan 4
+!(config-vlan)# name "telnet"
+!(config-vlan)# exit
+!(config)#
+}}}
+. Assign an IP address to the VLAN. By entering the "interface vlan" context you automatically turn VLAN 4 into a VLAN interface.
+{{{
+!(config)# interface vlan 4
+!(config-if)# ip address 192.168.10.1 255.255.255.0
+!(config-if)# exit
+!(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.
+{{{
+!(config)# line vty 0 2
+!(config-line)# exit
+!(config)#
+!(config)# save
+(config)# exit
+#
+}}}
+ 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.
 …
 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).