Changes between Version 21 and Version 22 of Internal/OpenFlow/CLISetup
- Timestamp:
- Jan 19, 2010, 10:11:57 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Internal/OpenFlow/CLISetup
v21 v22 271 271 }}} 272 272 273 == Elucidation (Or, Frequently asked questions) ==273 == Elucidation (Or, How-TO's) == 274 274 275 275 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: … … 277 277 * You are running Linux (We are, for the most part, using Ubuntu unless specified) 278 278 * You are using the NEC IP8800/S3640-48T2XW switch. 279 280 == Section 1: The Basics == 281 282 "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: 283 284 * Logging in for the first time (through serial) 285 * Admin modes and intro to contexts 286 * VLANs and ports 287 279 288 280 289 === Logging into the switch for the first time. === … … 326 335 327 336 328 == Configuration == 329 330 === The Basics: Admin modes, contexts === 337 === Admin modes, contexts === 331 338 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: 332 339 333 340 {{{ 334 > ena 341 > ena <<---whole command is 'enable' 335 342 # 336 343 }}} … … 339 346 "configure" brings you to the configuration prompt, which looks like this : 340 347 {{{ 341 # config 348 # config 342 349 (config)# 343 350 }}} … … 345 352 All configurations, from port speed to the MoTD banner, are done from here. 346 353 347 Here, 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:354 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: 348 355 349 356 * `vlan n` - create/configure standard VLANs, n being the VLAN ID (some number) … … 352 359 * `line <vty|console>` - configure telnet or console parameters, respectively 353 360 354 Don'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 361 Don't worry even if these don't make sense now - The meanings of the contexts will be explained as they are introduced. 362 363 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. 364 {{{ 365 (config)# interface vlan 8 <<---start by entering the 'interface vlan' context 358 366 (config-if)# 359 (config-if)# interface gi 0/3 <<---switch to interface gigabitethernetcontext367 (config-if)# interface gi 0/3 <<---switch to 'interface gigabitethernet' context 360 368 (config-if)# <<---note how prompt still shows up as "config-if" 361 }}} 362 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. The command `exit` lets you exit from contexts and enabled mode, or log out of the switch. 363 364 There are also contexts that support ranges of interfaces/ports/VLANs. For example, to configure ports 1-4 and 30 at once: 369 }}} 370 371 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: 365 372 {{{ 366 373 sw-sb09(config)# int range gigabitethernet 0/1-4, gigabitethernet 0/30 … … 369 376 Note how the prompt becomes "(config-if-range)" in this case. 370 377 371 ==== VLAN creation and port configuration. ==== 372 In order to do anything with the switch, you need to configure the following two: 378 === VLANs and ports. === 379 ==== ports ==== 380 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: 381 {{{ 382 sw-sb09> sh po st 383 Date 2010/01/18 05:44:23 UTC 384 Port Counts: 50 385 Port Name Status T/R All packets Multicast Broadcast Discard 386 0/ 1 geth0/1 up Tx 950638 581 437112 0 387 Rx 83404 0 2376 0 388 0/ 2 geth0/2 up Tx 948981 581 437196 0 389 Rx 81580 0 2292 0 390 0/ 3 geth0/3 up Tx 948982 581 437194 0 391 Rx 81584 0 2294 2 392 0/ 4 geth0/4 down Tx 0 0 0 0 393 Rx 0 0 0 0 394 0/ 5 geth0/5 down Tx 0 0 0 0 395 Rx 0 0 0 0 396 ... 397 398 0/49 tengeth0/49 down Tx 0 0 0 0 399 Rx 0 0 0 0 400 0/50 tengeth0/50 down Tx 0 0 0 0 401 Rx 0 0 0 0 402 }}} 403 '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). 404 405 ==== VLANs ==== 406 These can become confusing quickly because based on different contexts, the switch handles them differently. 373 407 374 408 * 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).
