Changes between Version 8 and Version 9 of Internal/OpenFlow/CLISetup


Ignore:
Timestamp:
Jul 9, 2009, 5:09:40 AM (15 years ago)
Author:
akoshibe
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Internal/OpenFlow/CLISetup

    v8 v9  
    1 [wiki:Documentation/OpenFlow/  Go back to OpenFlow index]
    2 
    3 = Initial setup through the command line interface (CLI) =
    4 
    5 The IP8800/S3640-48T2XW and IP8800/S3640-24T2XW are the two models of NEC switch that support !OpenFlow. This page explains how to initially configure the IP8800/S3640-48T2XW NEC switch through the CLI so you would be able to telnet to it. 
    6 
    7 
    8 == Connecting to the switch ==
    9 The switch must be configured through the console port before telnet can be used.[[BR]] The settings for the serial connection are the following:
     1= Configuring the switch through command line interface (CLI) =
     2
     3The 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. 
     4
     5== References ==
     6
     7For people literate in Japanese, a complete set of configuration guides may be found in the [http://www.nec.co.jp/ip88n/02.html#manual03 documents section of the NEC website.]
     8
     9== console connection to the switch (6/11) ==
     10The switch uses regular RS-232 for the serial connection. The settings for the serial connection are the following:
    1011
    1112 * speed: 9600
    … …  
    1516 * Parity: none
    1617 
    17 Kermit was used to connect to the switch because default settings can be used directly and no changes need to be made. !HyperTerminal should work, minicom doesn't seem to despite using the right settings. After installation (The Debian package is ckermit), use the following commands:
     18Minicom didn't seem to work too well no matter what settings were changed. Kermit was used to connect to the switch because default settings can be used directly and no changes need to be made. After installation (The Debian package is ckermit), use the following commands as root:
    1819
    1920{{{
    … …  
    2627
    2728== Making configuration changes through CLI ==
    28 Changes to the configurations can only be done in privileged mode. to do this, type `enable` in the prompt. The '>' should become a '#'.
     29A lot of it looks like Cisco IOS. Type `enable` in the prompt to get to privileged mode. The '>' should become a '#'.
    2930
    3031{{{   
    … …  
    3334}}}
    3435
    35 ''Note that the shorthand of a command may be used''. The switch also does command completions when you hit tab. A full list of commands can be seen by typing `?` at the prompt - this will produce a sizeable list and will not be shown here. Commands are often used in compound; a `?` can be used at any time to see what options are available:
     36The shorthand of a command can be used. The switch also does command completions when you hit tab. A full list of commands can be seen by typing `?` at the prompt. Commands are often used in compound, so a `?` can be used at any time to see what options are available:
    3637
    3738{{{
    … …  
    4849(config)#
    4950}}}
    50 
    5151
    5252If, at any time, you get confused as to which interface or '' what '' you are even configuring, command `show` will output the name of the interface and the configuration changes made to it so far:
    … …  
    6161
    6262 
    63 == Telnet access to the switch ==
    64 To telnet to a switch, you need to set up an IP address for the interface on the switch that a remote host may connect to. To do this, you need to not only set up a vlan interface to which the IP address belongs, but also permit telnet access. 
    65 
    66  1. After entering configuration mode, create a vlan (arbitrarily 4 in this case). Give it a name if you feel like it. [[BR]] The '!' before the prompt indicates that a change has been made, and you must use the command 'save' before exiting out of config mode to have the configuration changes apply.
     63== Telnet access to the switch (6/12) ==
     64To telnet to a switch, you need to set up an IP address for the switch. To do this, you need to not only set up a vlan interface to which the IP address belongs, but also permit telnet access. 
     65
     66 1. After entering configuration mode, create a vlan. Give it a name if you feel like it. The '!' before the prompt indicates that a change has been made, and you must use the command 'save' before exiting out of config mode to have the configuration changes apply.
    6767{{{
    6868(config)# vlan 4
    … …  
    8383{{{
    8484!(config)# interface vlan 4
    85 !(config-if)# ip address 192.168.1.1 255.255.255.0
     85!(config-if)# ip address 192.168.10.1 255.255.255.0
    8686!(config-if)# exit
    8787!(config)#
    … …  
    102102}}}
    103103
    104 
    105 == Refrences ==
    106 
    107 For people literate in Japanese, a complete set of configuration guides may be found in the [http://www.nec.co.jp/ip88n/02.html#manual03 documents section of the NEC website.]
    108 
     104The telnet VLAN (4) was later changed to VLAN 1.
     105
     106== switch as DHCP server ==
     107The switch can be a DHCP server, so it was made so the laptop that'll be used to test telnet would get an address from the switch. The commands make it so there is DHCP for group "Test1" on VLAN 1, and an address pool whose lease length is 10 minutes.   
     108{{{
     109!(config)# service dhcp vlan 1
     110!(config)# ip dhcp excluded-address 192.168.10.1
     111!(config)# ip dhcp pool Test1
     112!(dhcp-config)# network 192.168.11.0 255.255.255.0
     113!(dhcp-config)# lease 0 0 10
     114}}}
     115
     116== Command `ppupdate`, not actually needed (6/15) ==
     117The manual specified the command `ppupdate` for updating the firmware. This command copies new firmware (i.e. downloaded with ftp) on to the switch's flash memory. parameters usable:
     118
     119`ppupdate [test][no-display][-f][no-reload]<file name>`   
     120
     121 * `test` - only tests firmware, but doesn't update the firmware
     122 * `no-display` - does not show status messages while firmware is being updated
     123 * `-f` - update without confirmation
     124 * `no-reload` - does not reboot switch after update, so changes take place after next restart
     125 * `file-name` - the firmware, usually named k.img
     126
     127== The right way to flash the switch (6/16) ==
     128The specific how-to's are on [wiki:Documentation/OpenFlow/Firmware another article], but the general gist is to copy the firmware, license, and configuration files onto a SD card provided by NEC, and cold booting the switch off of it.   
     129
     130== VLAN Configuration, based on convention (6/23) ==
     131The switch should follow the conventions used in other switches for which port corresponds to which VLAN, where the trunk is, ect. After week 2, the switch was booted back into normal mode (no SD card), and the VLANs statically set according to the following convention for networking SB9:
     132
     133 ||Usage||ports||VLAN||
     134 ||CM||1-4||3||
     135 ||Control||5-8||27||
     136 ||Data||9-12||28||
     137
     138== Static VLAN Configuration ==
     139Configuration of the CM VLAN (VLAN 3) is shown here.
     140 
     141 1. Create and name VLAN
     142{{{
     143(config)# vlan 3
     144!(config-vlan)# name "CM"
     145!(config-vlan)# exit
     146}}}
     147
     148 2. Assign CM VLAN 3 to the desired ports. Unfortunately, you have to configure one port at a time. Luckily, you can use the up arrow key to go through previous commands to make things faster. 
     149{{{
     150!(config)# interface gi 0/1
     151!(config-if)# switchport mode access
     152!(config-if)# switchport acc vlan 3
     153!(config)# interface gi 0/2
     154!(config-if)# switchport mode access
     155!(config-if)# switchport acc vlan 3
     156!(config)# interface gi 0/3
     157!(config-if)# switchport mode access
     158!(config-if)# switchport acc vlan 3
     159!(config)# interface gi 0/4
     160!(config-if)# switchport mode access
     161!(config-if)# switchport acc vlan 3
     162}}}
     163 
     164 3. After repeating steps 1 and 2 for the Control and Data VLANs (with correct port numbers and VLAN number, of course), configure the trunk ports:
     165{{{
     166!(config-if)# interface gi 0/45
     167!(config-if)# switchport mode trunk
     168!(config-if)# switchport trunk allowed vlan 3,27,28
     169!(config-if)# interface gi 0/46
     170!(config-if)# switchport mode trunk
     171!(config-if)# switchport trunk allowed vlan 3,27,28
     172!(config-if)# interface gi 0/47
     173!(config-if)# switchport mode trunk
     174!(config-if)# switchport trunk allowed vlan 3,27,28
     175!(config-if)# interface gi 0/48
     176!(config-if)# switchport mode trunk
     177!(config-if)# switchport trunk allowed vlan 3,27,28
     178!(config-if)# exit
     179!(config)# save
     180(config)# exit
     181}}}
     182
     183== DHCP/BootP relay agent (6/24) ==
     184attempt was made but not knowing the DHCP server's address didn't help. Nevertheless, translations on how to set up a relay agent/ IP helper are [wiki:Documentation/OpenFlow/SwitchConfiguration here].
     185
     186== Native VLAN configuration (6/25) ==
     187A native VLAN was set up on the trunk ports so the switch will have an interface that can be assigned an IP address.   
     188
     189 1. Make a VLAN. Name the native VLAN. 
     190{{{
     191(config)# vlan 1
     192(config-vlan)# name "Network"
     193!(config-vlan)# exit
     194}}}
     195 2. Assign static IP address to the interface. we needed to find the switch's IP address with nslookup. This was actually done 7/2, after its MAC address was registered.   
     196{{{
     197!(config-vlan)# interface vlan 1
     198!(config-if)# ip address 172.16.19.253 255.255.0.0
     199}}}
     200 3. Configure ports to be trunk ports, then specify the native VLAN
     201{{{
     202!(config)# interface gi 0/48
     203!(config-if)# switchport mode trunk
     204!(config-if)# switchport trunk native vlan 1
     205}}}
     206 4. Specify which VLANs are allowed on the trunk. This includes all VLANs that converge to this trunk, as well as the native VLAN for this trunk. If the port is already made to allow other VLANs, instead of using command `switchport trunk allowed vlan 1,3,27,28` you can just add VLAN 1 by using the `vlan add <vlan ID>` context:
     207{{{
     208!(config-if)# swi trunk allowed vlan add 1
     209}}}
     210so now the configurations for port 0/48 look like this:
     211{{{
     212!(config-if)# sh
     213interface gigabitethernet 0/48
     214  switchport mode trunk
     215  switchport trunk allowed vlan 1,3,27-28
     216  switchport trunk native vlan 1
     217}}}
     218
     219 
     220
     221   
    109222
    110223[wiki:Documentation/OpenFlow/  Go back to OpenFlow index]