Changes between Version 20 and Version 21 of Internal/OpenFlow/CLISetup


Ignore:
Timestamp:
Jan 5, 2010, 11:44:25 PM (14 years ago)
Author:
akoshibe
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Internal/OpenFlow/CLISetup

    v20 v21  
    278278 * You are using the NEC IP8800/S3640-48T2XW switch.   
    279279
    280 === Logging in for the first time. ===
     280=== Logging into the switch for the first time. ===
    281281
    282282Out 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.   
     
    302302{{{
    303303
    304 Connecting to /dev/ttyS0, speed 0
    305  Escape character: Ctrl-\ (ASCII 28, FS): enabled
    306 Type the escape character followed by C to get back,
    307 or followed by ? to see other options.
    308 ----------------------------------------------------
    309 
    310 
    311 login:
    312 
    313 }}}
    314 If the login prompt doesn't come up, hitting enter should bring it up. The default username is `operator`, and the password is blank.   
     304 Connecting to /dev/ttyS0, speed 0
     305  Escape character: Ctrl-\ (ASCII 28, FS): enabled
     306 Type the escape character followed by C to get back,
     307 or followed by ? to see other options.
     308 ----------------------------------------------------
     309
     310
     311 login:
     312
     313}}}
     314If the login prompt doesn't come up, hitting the enter key should bring it up. The default username is "operator", and the password is blank. Once logged in, you will be brought to the CLI (Command line interface). Commands are entered at the caret.
     315
     316{{{
     317login: operator
     318
     319Copyright (c) 2005-2008 ALAXALA Networks Corporation. All rights reserved.
     320
     321
     322>
     323}}}     
    315324
    316325`Ctrl-\ q` ends the kermit session.
     
    318327
    319328== Configuration ==
    320 For configuration, you need to be in privileged mode. The magic word is "enable". "configure" brings you to the configuration prompt, which looks like this :
    321 {{{
    322 sw-sb09(config)#
    323 }}}
    324 
    325 From here, you can enter different contexts according to what you are trying to configure:
    326 
    327  * `interface vlan n` - create/ configure VLAN n, n being the VLAN ID (some number)
     329
     330=== The Basics: Admin modes, contexts ===
     331As 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:
     332
     333{{{
     334> ena   
     335#
     336}}}
     337
     338
     339"configure" brings you to the configuration prompt, which looks like this :
     340{{{
     341# config
     342(config)#
     343}}}
     344
     345All configurations, from port speed to the MoTD banner, are done from here.
     346
     347Here, 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." Some contexts we want to focus on throughout these pages are:
     348
     349 * `vlan n` - create/configure standard VLANs, n being the VLAN ID (some number)
     350 * `interface vlan n` - create/ configure a virtual interface with both Layer 2 and 3 characteristics
    328351 * `interface gigabitethernet 0/n` - configure specific port, n being number between 1 and 48
    329352 * `line <vty|console>` - configure telnet or console parameters, respectively
    330353
    331 when in a different context, you can tell from how the prompt becomes "(config-if)." [[BR]]
    332 Ranges of ports and VLANs can be specified. For example, to config ports 1-4 and 30 at once:
     354Don't worry even if they don't make sense now - The meanings of the contexts will be explained later in detail. 
     355
     356{{{
     357(config)# interface vlan 8                           
     358(config-if)#
     359(config-if)# interface gi 0/3           <<---switch to interface gigabitethernet context
     360(config-if)#                            <<---note how prompt still shows up as "config-if"
     361}}}
     362As 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. The command `exit` lets you exit from contexts and enabled mode, or log out of the switch.
     363
     364There are also contexts that support ranges of interfaces/ports/VLANs. For example, to configure ports 1-4 and 30 at once:
    333365{{{
    334366 sw-sb09(config)# int range gigabitethernet 0/1-4, gigabitethernet 0/30
    335367 sw-sb09(config-if-range)#
    336368}}}
    337 
    338369Note how the prompt becomes "(config-if-range)" in this case.
    339370