1. Manuals
  2. Brands
  3. ProCurve Manuals
  4. Switch
  5. 6400cl
  6. Management and configuration manual

ProCurve 6400cl Management And Configuration Manual

Procurve switches e.10.02 (series 5300xl) l.10.xx (series 4200vl) m.08.73 (series 3400/6400cl)
Hide thumbs
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
Table of Contents

Advertisement

Quick Links

Download this manual
6400cl
5300xl
4200vl
3400cl
ProCurve Switches
E.10.02 (Series 5300xl)
L.10.XX (Series 4200vl)
M.08.73 (Series 3400/6400cl)
www.procurve.com
Management and
Configuration Guide

Advertisement

Table of Contents
loading

Related Manuals for ProCurve 6400cl

Summary of Contents for ProCurve 6400cl

  • Page 1 Management and 6400cl 5300xl Configuration Guide 4200vl 3400cl ProCurve Switches E.10.02 (Series 5300xl) L.10.XX (Series 4200vl) M.08.73 (Series 3400/6400cl) www.procurve.com...

  • Page 3: Management And Configuration Guide

    ProCurve Series 6400cl Switches Series 5300xl Switches Series 4200vl Switches Series 3400cl Switches October 2005 E.10.02 or Greater (5300xl) L.10.01 or Greater (4200vl) M.08.73 or Greater (3400/6400cl) Management and Configuration Guide...
  • Page 4 (J8772A) See the Customer Support/Warranty booklet included with ProCurve Switch 4202vl-48G (J8771A) the product. ProCurve Switch 10G CX4 6400cl-6XG (J8433A) ProCurve Switch 10G X2 6400cl-6XG (J8474A) A copy of the specific warranty terms applicable to your Hewlett-Packard products and replacement parts can be...

  • Page 5: Table Of Contents

    Contents Product Documentation About Your Switch Manual Set ....... . . xix Feature Index .

  • Page 6: Advantages Of Using Procurve Manager

    ProCurve Manager Plus ........

  • Page 7: Using The Web Browser Interface

    Using ProCurve Manager (PCM) or ProCurve Manager Plus (PCM+) ....... 5-5 Tasks for Your First Web Browser Interface Session .

  • Page 8: Switch Memory And Configuration

    Sorting the Alert Log Entries ......5-20 Alert Types and Detailed Views ......5-21 The Status Bar .

  • Page 9: Interface Access And System Information

    Using the Clear + Reset Button Combination To Reset the Switch to Its Default Configuration ......6-34 Transferring Startup-Config Files To or From a Remote Server .

  • Page 10: Time Protocols

    DHCP/Bootp Operation ........8-12 Network Preparations for Configuring DHCP/Bootp ..8-14 IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads .

  • Page 11: Port Status And Basic Configuration

    10 Port Status and Basic Configuration Contents ........... . . 10-1 Overview .
  • Page 12 Viewing PoE Configuration and Status ..... . . 11-15 Displaying the Switch’s Global PoE Power Status ....11-15 Displaying an Overview of PoE Status on All Ports .

  • Page 13: Port Trunking

    Changing the VLAN-Base ....... 12-18 Configuring Client VLANs ........12-18 Configuring Uplink Network Ports .
  • Page 14 All-Traffic Rate-Limiting for the 5300xl, 3400cl and 6400cl Switches ......14-4 Introduction ..........14-4 Rate-Limiting Operation .
  • Page 15 LLDP Operating Rules ........15-31 LLDP Data Management on the Series 3400cl and 6400cl Switches 15-32 LLDP Neighbor Data .
  • Page 16 Viewing the Current Configuration ..... . . 15-34 Configuring Global LLDP Packet Controls ....15-36 Configuring SNMP Notification Support .
  • Page 17 Disable TFTP and Auto-TFTP for Enhanced Security ..A-10 Command Options ........A-12 Authentication .
  • Page 18 Menu Access ......... . . B-5 CLI Access .
  • Page 19 Browser or Telnet Access Problems ......C-5 Unusual Network Activity ........C-7 General Problems .
  • Page 20 CLI: Viewing the Port and VLAN MAC Addresses ....D-5 Viewing the MAC Addresses of Connected Devices ... . . D-8 E Daylight Savings Time on ProCurve Switches Index...

  • Page 21: Product Documentation

    N o t e For the latest version of all ProCurve switch documentation, including Release Notes covering recently added features, visit the ProCurve Network­ ing web sit at http://www.procurve.com, click on Technical support, and then click on Product manuals (all).
  • Page 22 Supported Supported Traffic Security on 5300xl on 4200vl on 3400cl/ Configuration Management Guide 6400cl 802.1Q VLAN Tagging 802.1X Port-Based Priority 802.1X Multiple Authenticated Clients per port ACLs AAA Authentication Authorized IP Managers Authorized Manager List (web, telnet, TFTP) Auto MDIX Configuration...
  • Page 23 Access Supported Supported Supported Traffic Security on 5300xl on 4200vl on 3400cl/ Configuration Management Guide 6400cl Eavesdrop Protection Event Log Factory Default Settings Flow Control (802.3x) File Management File Transfers Friendly Port Names Guaranteed Minimum Bandwidth (GMB) GVRP IGMP Delayed Group Flush...
  • Page 24 Management Advanced Access Supported Supported Supported Traffic Security on 5300xl on 4200vl on 3400cl/ Configuration Management Guide 6400cl Meshing Monitoring and Analysis Multicast Filtering Multiple Configuration Files Network Management SNMP SNMP Applications only only OpenView Device Management OSPF Passwords Password Clear Protection...
  • Page 25 Access Supported Supported Supported Traffic Security on 5300xl on 4200vl on 3400cl/ Configuration Management Guide 6400cl RMON 1,2,3,9 Routing Routing - IP Static Secure Copy SFLOW SFTP SNMPv3 Software Downloads (SCP/SFTP, TFTP, Xmodem) Source-Port Filters Spanning Tree (STP, RSTP, MSTP)
  • Page 26 Product Documentation Feature Index Feature Management Advanced Access Supported Supported Supported Traffic Security on 5300xl on 4200vl on 3400cl/ Configuration Management Guide 6400cl VLAN Mirroring (1 static VLAN) Voice VLAN Web Authentication RADIUS Support Web-based Authentication Web UI Xmodem XRRP xxiv...

  • Page 27: Contents

    Getting Started Contents Introduction ..........1-2 Conventions .

  • Page 28: Introduction

    For an overview of other product documentation for the above switches, refer to “Product Documentation” on page xix. The Product Documentation CD-ROM shipped with the switch includes a copy of this guide. You can also download a copy from the ProCurve Network­ ing web site, http://www.procurve.com. Conventions This guide uses the following conventions for command syntax and displayed information.

  • Page 29: Command Syntax Statements

    ProCurve 5308xl# ProCurve 4204vl# ProCurve 4208vl# ProCurve 3400-24cl# ProCurve 3400-48cl# To simplify recognition, this guide uses ProCurve to represent command prompts for all models. For example: ProCurve# (You can use the hostname command to change the text in the CLI prompt.)

  • Page 30: Screen Simulations

    Port Identity Examples This guide describes software applicable to both chassis-based and stackable ProCurve switches. Where port identities are needed in an example, this guide uses the chassis-based port identity system, such as “A1, “B3-B5”, “C7”, etc. However, unless otherwise noted, such examples apply equally to the stack- able switches, which typically use only numbers, such as “1”, “3-5”, “15”, etc.
  • Page 31 Getting Started Sources for More Information N o t e For the latest version of all ProCurve switch documentation, including Release Notes covering recently added features, visit the ProCurve Network­ ing web site at http://www.procurve.com, click on Technical support, and then click on Product Manuals (all).

  • Page 32: Getting Documentation From The Web

    2. Click on Technical support. 3. Click on Product manuals (all). 4. Click on the product for which you want to view or download a manual. Figure 1-2. Example of How to Locate Product Manuals on the ProCurve Networking Web Site...

  • Page 33: Online Help

    Getting Started Sources for More Information Figure 1-3. Listing of ProCurve Manuals on the ProCurve Networking Web Site Online Help If you need information on specific parameters in the menu interface, refer to the online help provided in the interface. For example:...

  • Page 34: Need Only A Quick Start

    For more information on web browser Help options, refer to “Online Help for the Web Browser Interface” on page 5-11. If you need further information on ProCurve switch technology, visit the ProCurve Networking web site at: http://www.procurve.com...

  • Page 35: To Set Up And Install The Switch In Your Network

    To Set Up and Install the Switch in Your Network To Set Up and Install the Switch in Your Network Use the ProCurve Installation and Getting Started Guide (shipped with the switch) for the following: ■ Notes, cautions, and warnings related to installing and using the switch and its related modules ■...
  • Page 36 Getting Started To Set Up and Install the Switch in Your Network — This page unused intentionally— 1-10...

  • Page 37: Contents

    ProCurve Manager Plus ........

  • Page 38: Overview

    VLAN management. (ProCurve includes a copy of PCM+ in-box for a free 30-day trial.) This manual describes how to use the menu interface (chapter 2), the CLI (chapter 3), the web browser interface (chapter 4), and how to use these interfaces to configure and monitor the switch.

  • Page 39: Advantages Of Using The Menu Interface

    Selecting a Management Interface Advantages of Using the Menu Interface To use ProCurve Manager or ProCurve Manager Plus, refer to the Getting Started Guide and the Administrator’s Guide, which are available electron­ ically with the software for these applications. For more information, visit the ProCurve Networking web site at http://www.procurve.com.

  • Page 40: Advantages Of Using The Cli

    Provides more security; configuration information and passwords are ■ not seen on the network. Advantages of Using the CLI Prompt for Operator Level ProCurve> Prompt for Manager Level ProCurve# Prompt for Global Configuration ProCurve(config)# Level Prompt for Context ProCurve(<context>)#...

  • Page 41: Information On Using The Cli

    Selecting a Management Interface Advantages of Using the Web Browser Interface Information on Using the CLI For information on how to use the CLI, refer to chapter 3. “Using the ■ Command Line Interface (CLI)”. ■ To perform specific procedures (such as configuring IP addressing or VLANs), use the Contents listing at the front of the manual to locate the information you need.
  • Page 42 Selecting a Management Interface Advantages of Using the Web Browser Interface Familiar browser interface--locations of window objects consistent ■ with commonly used browsers, uses mouse clicking for navigation, no terminal setup ■ Many features have all their fields in one screen so you can view all values at once More visual cues, using colors, status bars, device icons, and other ■...

  • Page 43: Or Procurve Manager Plus

    Advantages of Using ProCurve Manager or ProCurve Manager Plus You can operate ProCurve Manager and ProCurve Manager Plus (PCM and PCM+) from a PC on the network to monitor traffic, manage your hubs and switches, and proactively recommend network changes to increase network uptime and optimize performance.
  • Page 44 Features and benefits of ProCurve Manager Plus: ■ • All of the Features of ProCurve Manager: Refer to the above listing. • In-Depth Traffic Analysis: An integrated, low-overhead traffic monitor interface shows detailed information on traffic throughout the network.
  • Page 45 Updates can be scheduled easily across large groups of devices, all at user-specified times. • Investment Protection: The modular software architecture of ProCurve Manager Plus will allow HP to offer network administrators add-on software solutions that complement their needs.

  • Page 46: Web Browser Interfaces

    Selecting a Management Interface Advantages of Using ProCurve Manager or ProCurve Manager Plus Custom Login Banners for the Console and Web Browser Interfaces You can now configure the switch to display a login banner of up to 320 characters when an operator initiates a management session with the switch through any of the following methods: ■...

  • Page 47: Banner Operation With Telnet, Serial, Or Sshv2 Access

    Selecting a Management Interface Advantages of Using ProCurve Manager or ProCurve Manager Plus Banner Operation with Telnet, Serial, or SSHv2 Access When a system operator begins a login session, the switch displays the banner above the local password prompt or, if no password is configured, above the Press any key to continue prompt.

  • Page 48: Example Of Configuring And Displaying A Banner

    Selecting a Management Interface Advantages of Using ProCurve Manager or ProCurve Manager Plus The switch allows up to 320 banner characters, including blank spaces and “ and the delimiter defined by banner motd CR-LF ( ). (The tilde “ [Enter] <delimiter>...
  • Page 49 Selecting a Management Interface Advantages of Using ProCurve Manager or ProCurve Manager Plus ProCurve(config)# show banner motd Banner Information Banner status: Enabled Configured Banner: This is a private system maintained by the Allied Widget Corporation. Unauthorized use of this system can result in civil and criminal penalties! Figure 3.
  • Page 50 Selecting a Management Interface Advantages of Using ProCurve Manager or ProCurve Manager Plus The next time someone logs onto the switch’s management CLI, the following appears: The login screen displays the configured banner. Entering a correct password clears the banner and displays the CLI prompt.

  • Page 51: Operating Notes

    Selecting a Management Interface Advantages of Using ProCurve Manager or ProCurve Manager Plus If someone uses a Web browser to log in to the switch interface, the following message appears: Figure 6. Example of Web Browser Interface Result of the Login Banner...
  • Page 52 Selecting a Management Interface Advantages of Using ProCurve Manager or ProCurve Manager Plus — This page is intentionally unused. — 2-16...

  • Page 53: Contents

    Using the Menu Interface Contents Overview ........... . . 3-2 Starting and Ending a Menu Session .

  • Page 54: Overview

    Configure these features: • M anager and Operator • A network monitoring port passwords • Stack Management (3400cl and • System parameters 6400cl switches only) • IP addressing • Spanning Tree operation • Time protocol • SNMP community names • Ports •...

  • Page 55: Starting And Ending A Menu Session

    Using the Menu Interface Starting and Ending a Menu Session N o t e If the switch has neither a Manager nor an Operator password, anyone having access to the console interface can operate the console with full manager privileges. Also, if you configure only an Operator password, entering the Operator password enables full manager privileges.

  • Page 56: How To Start A Menu Interface Session

    If no password has been configured, the CLI prompt appears. Go to the next step. 4. When the CLI prompt appears, display the Menu interface by entering the menu command. For example: ProCurve# menu [Enter] results in the following display:...

  • Page 57: How To End A Menu Session And Exit From The Console

    Using the Menu Interface Starting and Ending a Menu Session Stacking is available on Series 3400cl and Series 6400cl switches. Figure 3-1. Example of the Main Menu with Manager Privileges For a description of Main Menu features, see “Main Menu Features” on page 3-7.
  • Page 58 Stacking is available on Series 3400/6400cl switches and Series 4200vlswitches. Figure 3-2. Example Indication of a Configuration Change Requiring a Reboot 1. In the current session, if you have not made configuration changes that require a switch reboot to activate, return to the Main Menu and press (zero) to log out.

  • Page 59: Main Menu Features

    Using the Menu Interface Main Menu Features Main Menu Features Figure 3-3. The Main Menu View with Manager Privileges The Main Menu gives you access to these Menu interface features: ■ Status and Counters: Provides access to display screens showing switch information, port status and counters, port and VLAN address tables, and spanning tree information.
  • Page 60 Using the Menu Interface Main Menu Features Command Line (CLI): Selects the Command Line Interface at the same ■ level (Manager or Operator) that you are accessing in the Menu interface. (Refer to chapter 3, “Using the Command Line Interface (CLI)”.) ■...

  • Page 61: Screen Structure And Navigation

    Using the Menu Interface Screen Structure and Navigation Screen Structure and Navigation Menu interface screens include these three elements: ■ Parameter fields and/or read-only information such as statistics Navigation and configuration actions, such as Save, Edit, and Cancel ■ ■ Help line to describe navigation options, individual parameters, and read- only data For example, in the following System Information screen:...
  • Page 62 Using the Menu Interface Screen Structure and Navigation Table 3-1. How To Navigate in the Menu Interface Task: Actions: Execute an action Use either of the following methods: from the “Actions –>” • Use the arrow keys ( [<] ,or [>] ) to highlight the action you want list at the bottom of to execute, then press [Enter].
  • Page 63 Using the Menu Interface Screen Structure and Navigation To get Help on individual parameter descriptions. In most screens there is a Help option in the Actions line. Whenever any of the items in the Actions line is highlighted, press , and a separate help screen is displayed. For example: Pressing [H] or highlighting Help and pressing [Enter] displays Help for the...

  • Page 64: Rebooting The Switch

    Reboot Switch is not available if you log on in Operator mode; that is, if you enter an Operator password instead of a manager password at the password prompt.) Reboot Switch option Stacking is available on Series 4200vl switches and Series 3400/6400cl switches. Figure 3-6. The Reboot Switch Option in the Main Menu 3-12...
  • Page 65 Using the Menu Interface Rebooting the Switch Rebooting To Activate Configuration Changes. Configuration changes for most parameters in the menu interface become effective as soon as you save them. However, you must reboot the switch in order to implement a change in the .

  • Page 66: Menu Features List

    VLAN Menu Console Passwords Event Log Command Line (CLI) Reboot Switch Download OS (Download Switch Software) Run Setup Stacking (Series 3400cl, Series 6400cl and Series 4200vl switches) • Stacking Status (This Switch) • Stacking Status (All) • Stack Configuration •...

  • Page 67: Where To Go From Here

    Using the Menu Interface Where To Go From Here Where To Go From Here This chapter provides an overview of the menu interface and how to use it. The following table indicates where to turn for detailed information on how to use the individual features available through the menu interface.
  • Page 68 Using the Menu Interface Where To Go From Here — This page is intentionally unused. — 3-16...

  • Page 69: Contents

    Using the Command Line Interface (CLI) Contents Overview ........... . . 4-2 Accessing the CLI .

  • Page 70: Overview

    Using the Command Line Interface (CLI) Overview Overview The CLI is a text-based command interface for configuring and monitoring the switch. The CLI gives you access to the switch’s full set of commands while providing the same password protection that is used in the web browser interface and the menu interface.

  • Page 71: Privilege Levels At Logon

    In the above case, you will enter the CLI at the level corresponding to the password you provide (operator or manager). If no passwords are set when you log onto the CLI, you will enter at the Manager level. For example: ProCurve# _...

  • Page 72: Privilege Level Operation

    A “>” character delimits the Operator-level prompt. For example: (Example of the Operator prompt.) ProCurve> _ When using enable to move to the Manager level, the switch prompts you for the Manager password if one has already been configured.

  • Page 73: Manager Privileges

    To select this level, enter the specific context at the Global Configuration level prompt. For example, to select the context level for an existing VLAN with the VLAN ID of 10, you would enter the following command and see the indicated result: ProCurve(config)# vlan 10 ProCurve(vlan-10)#...
  • Page 74 Using the CLI Table 4-1. Privilege Level Hierarchy Privilege Example of Prompt and Permitted Operations Level Operator Privilege Operator Level ProCurve> show < command > View status and configuration information. setup ping < argument > Perform connectivity tests. link-test < argument >...

  • Page 75: How To Move Between Levels

    Using the Command Line Interface (CLI) Using the CLI How To Move Between Levels Change in Levels Example of Prompt, Command, and Result Operator level > enable ProCurve Password:_ Manager level enable After you enter , the Password prompt appears. After you enter the...

  • Page 76: Listing Commands And Command Options

    Using the Command Line Interface (CLI) Using the CLI For example, if you use the menu interface to configure an IP address of “X” for VLAN 1 and later use the CLI to configure a different IP address of “Y” for VLAN 1, then “Y”...
  • Page 77 [Tab] (with no spaces allowed). For example, at the Global Configuration level, if you press [Tab] immediately after typing “t”, the CLI displays the available command options that begin with “t”. For example: ProCurve(config)# t [Tab] tacacs-server telnet-server time timesync...

  • Page 78: Listing Command Options

    CLI completes the current word (if you have typed enough of the word for the CLI to distinguish it from other possibilities), including hyphenated exten­ sions. For example: ProCurve(config)# port- [Tab] ProCurve(config)# port-security _ Pressing after a completed command word lists the further options for [Tab] that command.

  • Page 79: Displaying Cli "Help

    Using the Command Line Interface (CLI) Using the CLI Displaying CLI “Help” CLI Help provides two types of context-sensitive information: ■ Command list with a brief summary of each command’s purpose Detailed information on how to use individual commands ■ Displaying Command-List Help.
  • Page 80 Note that trying to list the help for an individual command from a privilege level that does not include that command results in an error message. For example, trying to list the help for the interface command while at the global configuration level produces this result: ProCurve# speed-duplex help Invalid input: speed-duplex 4-12...

  • Page 81: Configuration Commands And The Context Configuration Modes

    Port or Trunk-Group Context . Includes port- or trunk-specific com­ mands that apply only to the selected port(s) or trunk group, plus the global configuration, Manager, and Operator commands. The prompt for this mode includes the identity of the selected port(s): ProCurve(config)# interface c3-c6 ProCurve(eth-C5-C8)# ProCurve(config)# interface trk1 ProCurve(eth-Trk1)#...
  • Page 82 Using the Command Line Interface (CLI) Using the CLI In the port context, the first block of commands in the “?” listing show the context-specific commands that will affect only ports C3-C6. The remaining commands in the listing are Manager, Operator, and context commands.
  • Page 83 VLAN ID of the selected VLAN. For example, if you had already configured a VLAN with an ID of 100 in the switch: ProCurve(config)# vlan 100 Command executed at configuration level to enter VLAN 100 context. ProCurve(vlan-100)# Resulting prompt showing VLAN 100 context.

  • Page 84: Cli Control And Editing

    Using the Command Line Interface (CLI) CLI Control and Editing CLI Control and Editing Keystrokes Function [Ctrl] [A] Jumps to the first character of the command line. or [<] Moves the cursor back one character. [Ctrl] [B] [Ctrl] [C] Terminates a task and displays the command prompt. [Ctrl] [D] Deletes the character at the cursor.

  • Page 85: Contents

    Using ProCurve Manager (PCM) or ProCurve Manager Plus (PCM+) ....... 5-5 Tasks for Your First Web Browser Interface Session .

  • Page 86: Overview

    Command Prompt or changing the Web Agent Enabled parameter setting to No (page 7-4). For information on operating system, browser, and Java versions for the switches covered by this guide, go to the ProCurve Networking web site at http://www.procurve.com and: Click on: Technical support...

  • Page 87: General Features

    System information • IP configuration • Support and management server URLs • Device features (Spanning Tree On/Off, VLAN selection, and IGMP) • Stacking (3400cl, 6400cl and 4200vl switches) Switch Security: • User names and passwords • Authorized Addresses • Intrusion Log •...

  • Page 88: Starting An Web Browser Interface Session With The Switch

    Location or Address field instead of the IP address. Using DNS names typically improves browser performance. Contact your network adminis­ trator to enquire about DNS names associated with your ProCurve switch. Type the IP address (or DNS name) of the switch in the browser Location or Address (URL) field and press .

  • Page 89: Procurve Manager Plus (Pcm+)

    Using ProCurve Manager (PCM) or ProCurve Manager Plus (PCM+) ProCurve Manager and ProCurve Manager Plus are designed for installation on a network management workstation. For this reason, the system require­ ments are different from the system requirements for accessing the switch’s web browser interface from a non-management PC or workstation.
  • Page 90 Using the Web Browser Interface Starting an Web Browser Interface Session with the Switch First-Time Alert Install Alert Figure 5-1. Example of Status Overview Screen...

  • Page 91: Tasks For Your First Web Browser Interface Session

    Using the Web Browser Interface Tasks for Your First Web Browser Interface Session Tasks for Your First Web Browser Interface Session The first time you access the web browser interface, there are three tasks you should perform: ■ Review the “First Time Install” window Set Manager and Operator passwords ■...

  • Page 92: In The Browser Interface

    Using the Web Browser Interface Tasks for Your First Web Browser Interface Session This window is the launching point for the basic configuration you need to perform to set web browser interface passwords for maintaining security and a fault detection policy, which determines the types of messages that the Alert Log displays.
  • Page 93 Using the Web Browser Interface Tasks for Your First Web Browser Interface Session Figure 5-3. The Device Passwords Window To set the passwords: 1. Access the Device Passwords screen by one of the following methods: • If the Alert Log includes a “First Time Install” event entry, double click on this event, then, in the resulting display, click on the secure access to the device link.

  • Page 94: Entering A User Name And Password

    Using the Web Browser Interface Tasks for Your First Web Browser Interface Session Entering a User Name and Password Figure 5-4. Example of the Password Prompt in the Web Browser Interface The manager and operator passwords are used to control access to all switch interfaces.

  • Page 95: Online Help For The Web Browser Interface

    N o t e To access the online Help for the web browser interface, you need either ProCurve Manager (version 1.5 or greater) installed on your network or an active connection to the World Wide Web. Otherwise, Online help for the web browser interface will not be available.

  • Page 96: Support/Mgmt Urls Feature

    Support tab. The default is the URL for the ProCurve Networking home page. – The URL of a PCM (ProCurve Network Manager) workstation or other server for the online Help files for this web browser interface. (The default setting accesses the switch’s browser-based Help on the ProCurve World Wide...

  • Page 97: Support Url

    As an alternative, you can replace the ProCurve URL with the URL for a local site used for logging reports on network performance or other support activ­...

  • Page 98: Using The Pcm Server For Switch Web Helpweb Help

    Figure 5-7. How To Access Web Browser Interface Online Help Using the PCM Server for Switch Web HelpWeb Help For ProCurve devices that support the "Web Help" feature, you can use the PCM server to host the switch help files for devices that do not have HTTP access to the HP Support Web site.
  • Page 99 Using the Web Browser Interface Support/Mgmt URLs Feature You will enter the IP address for your PCM server. 8040 is the standard port number to use. Restart the Discovery process for the change to be applied. N o t e Changing the Discovery’s Global properties file will redirect the Device Help URL for all devices.

  • Page 100: Status Reporting Features

    Using the Web Browser Interface Status Reporting Features Status Reporting Features Browser elements covered in this section include: The Overview window (below) ■ ■ Port utilization and status (page 5-17) ■ The Alert log (page 5-20) The Status bar (page 5-22) ■...

  • Page 101: The Port Utilization And Status Displays

    Using the Web Browser Interface Status Reporting Features The Port Utilization and Status Displays The Port Utilization and Status displays show an overview of the status of the switch and the amount of network activity on each port. The following figure shows a sample reading of the Port Utilization and Port Status.
  • Page 102 Using the Web Browser Interface Status Reporting Features Maximum Activity Indicator: As the bars in the graph area change ■ height to reflect the level of network activity on the corresponding port, they leave an outline to identify the maximum activity level that has been observed on the port.

  • Page 103: Port Status

    Using the Web Browser Interface Status Reporting Features Port Status Port Status Indicators Legend Figure 5-12. The Port Status Indicators and Legend The Port Status indicators show a symbol for each port that indicates the general status of the port. There are four possible statuses: Port Connected –...

  • Page 104: The Alert Log

    Using the Web Browser Interface Status Reporting Features The Alert Log The web browser interface Alert Log, shown in the lower half of the screen, shows a list of network occurrences, or alerts, that were detected by the switch. Typical alerts are Broadcast Storm, indicating an excessive number of broadcasts received on a port, and Problem Cable, indicating a faulty cable.

  • Page 105: Alert Types And Detailed Views

    Using the Web Browser Interface Status Reporting Features Alert Types and Detailed Views As of April, 2004, the web browser interface generates the following alert types: • Auto Partition • High collision or drop rate • Backup Transition • Loss of Link •...

  • Page 106: The Status Bar

    Using the Web Browser Interface Status Reporting Features Figure 5-14. Example of Alert Log Detail View The Status Bar The Status Bar appears in the upper left corner of the web browser interface window. Figure 5-15 shows an expanded view of the status bar. Most Critical Alert Description Status Indicator System Name...
  • Page 107 Using the Web Browser Interface Status Reporting Features The Status bar includes four objects: ■ Status Indicator. Indicates, by icon, the severity of the most critical alert in the current display of the Alert Log. This indicator can be one of four shapes and colors, as shown below.

  • Page 108: Setting Fault Detection Policy

    Using the Web Browser Interface Status Reporting Features Setting Fault Detection Policy One of the powerful features in the web browser interface is the Fault Detection facility. For your switch, this feature controls the types of alerts reported to the Alert Log based on their level of severity. Set this policy in the Fault Detection window (figure 5-16).
  • Page 109 Never. Disables the Alert Log and transmission of alerts (traps) to the ■ management server (in cases where a network management tool such as ProCurve Manager is in use). Use this option when you don’t want to use the Alert Log. The Fault Detection Window also contains three Change Control Buttons: Apply Changes.
  • Page 110 Using the Web Browser Interface Status Reporting Features —This page left blank intentionally— 5-26...

  • Page 111: Contents

    Switch Memory and Configuration Contents Overview ........... . . 6-3 Overview of Configuration File Management .

  • Page 112: Overview

    Switch Memory and Configuration Overview Overview This chapter describes: ■ How switch memory manages configuration changes How the CLI implements configuration changes ■ ■ How the menu interface and web browser interface implement configu­ ration changes ■ How the switch provides software options through primary/secondary flash images How to use the switch’s primary and secondary flash options, including ■...
  • Page 113 Switch Memory and Configuration Overview of Configuration File Management Running Config File: Exists in volatile memory and controls switch ■ operation. If no configuration changes have been made in the CLI since the switch was last booted, the running-config file is identical to the startup-config file.
  • Page 114 5: ProCurve(config)# interface ethernet 5 disable The above command disables port 5 in the running-config file, but not in the startup-config file. Port 5 remains disabled only until the switch reboots. If...

  • Page 115: Using The Cli To Implement Configuration Changes

    Switch Memory and Configuration Using the CLI To Implement Configuration Changes Using the CLI To Implement Configuration Changes The CLI offers these capabilities: Access to the full set of switch configuration features ■ ■ The option of testing configuration changes before making them perma­ nent How To Use the CLI To View the Current Configuration Files.
  • Page 116 ProCurve(config)# interface e a5 speed-duplex auto-10 After you are satisfied that the link is operating properly, you can save the change to the switch’s permanent configuration (the startup-config file) by...
  • Page 117 Using the CLI To Implement Configuration Changes Disables port 1 in the running configuration, which causes port 1 to block all traffic. ProCurve(config)# interface e 1 disable ProCurve(config)# boot Device will be rebooted, do you want to continue [y/n]? y Press [Y] to continue the rebooting process.

  • Page 118: Configuration Changes

    Syntax: erase startup-config For example: ProCurve(config)# erase startup-config Configuration will be deleted and device rebooted, continue [y/n]? Press to replace the current configuration with the factory default config­ uration and reboot the switch. Press to retain the current configuration and prevent a reboot.
  • Page 119 Switch Memory and Configuration Using the Menu and Web Browser Interfaces To Implement Configuration Changes N o t e The only exception to this operation are two VLAN-related parameter changes that require a reboot—described under “Rebooting To Activate Configuration Changes” on page 6-10. Using in the Menu Interface Save...

  • Page 120: Rebooting From The Menu Interface

    Optional Reboot Switch Command Note: The Stacking feature is available on the Series 3400/6400cl and Series 4200vl switches. Figure 6-4. The Reboot Switch Option in the Main Menu Rebooting To Activate Configuration Changes. Configuration changes for most parameters become effective as soon as you save them. However,...

  • Page 121: Web: Implementing Configuration Changes

    Switch Memory and Configuration Using the Menu and Web Browser Interfaces To Implement Configuration Changes If configuration changes requiring a reboot have been made, the switch displays an asterisk (*) next to the menu item in which the change has been made.

  • Page 122: Using Primary And Secondary Flash Image Options

    Switch Memory and Configuration Using Primary and Secondary Flash Image Options Using Primary and Secondary Flash Image Options The Series switches covered by this guide feature two flash memory locations for storing switch software image files: ■ Primary Flash: The default storage for a switch software image. ■...
  • Page 123 Switch Memory and Configuration Using Primary and Secondary Flash Image Options For example, if the switch is using a software version of E.08.22 stored in Primary flash, show version produces the following: Figure 6-6. Example Showing the Identity of the Current Flash Image (5300xl) Determining Whether the Flash Images Are Different Versions.

  • Page 124: Switch Software Downloads

    Switch Memory and Configuration Using Primary and Secondary Flash Image Options 1. In this example show version indicates the switch has version E.08.30 in primary flash. 2. After the boot system command, show version indicates that version E.08.20 is in secondary flash.

  • Page 125: Local Switch Software Replacement And Removal

    Switch Memory and Configuration Using Primary and Secondary Flash Image Options Local Switch Software Replacement and Removal This section describes commands for erasing a software version and copying an existing software version between primary and secondary flash. N o t e It is not necessary to erase the content of a flash location before downloading another software file.
  • Page 126 Figure 6-9. Example Indicating Two Different Software Versions in Primary and Secondary Flash Execute the copy command as follows: ProCurve(config)# copy flash flash primary Erasing the Contents of Primary or Secondary Flash. This command deletes the software image file from the specified flash location.

  • Page 127: Rebooting The Switch

    Switch Memory and Configuration Using Primary and Secondary Flash Image Options The prompt shows which flash location will be erased. Figure 6-10. Example of Erase Flash Prompt Type y at the prompt to complete the flash erase. Use show flash to verify erasure of the selected software flash image The “...
  • Page 128 Switch Memory and Configuration Using Primary and Secondary Flash Image Options Booting from Primary Flash. This command always boots the switch from primary flash, executes the complete set of subsystem self-tests, and gives you the option of saving or discarding any configuration changes in the running­ config file.
  • Page 129 Shows the status of the fastboot feature, either enabled or disabled. The fastboot command is shown below. ProCurve(config)# fastboot Figure 6-14. Example of the Fastboot Command Rebooting from the Current Software Version. Reload reboots the switch from the flash image and startup-config file on which the switch is currently running, and provides the option for saving to the startup-config file any configuration changes currently in the running-config file.

  • Page 130: Operating Notes

    Switch Memory and Configuration Using Primary and Secondary Flash Image Options Operating Notes Default Boot Source. The switch reboots from primary flash by default unless you specify the secondary flash. Boot Attempts from an Empty Flash Location. In this case, the switch aborts the attempt and displays Image does not exist Operation aborted.

  • Page 131: Multiple Configuration Files On 5300Xl And 4200Vl Switches

    Switch Memory and Configuration Multiple Configuration Files on 5300xl and 4200vl Switches Multiple Configuration Files on 5300xl and 4200vl Switches This section applies only to 5300xl switches running software release E.09.xx or greater, and 4200vl switches. Action Page Listing and Displaying Startup-Config Files 6-26 Changing or Overriding the Reboot Configuration Policy 6-28...
  • Page 132 Switch Memory and Configuration Multiple Configuration Files on 5300xl and 4200vl Switches Beginning with software release E.09.xx, the switch allows up to three startup­ config files with options for selecting which startup-config file to use for: ■ A fixed reboot policy using a specific startup-config file for a specific boot path (primary or secondary flash) Overriding the current reboot policy on a per-instance basis ■...

  • Page 133: General Operation

    Switch Memory and Configuration Multiple Configuration Files on 5300xl and 4200vl Switches General Operation Multiple Configuration Storage in the Switch. The switch uses three memory “slots”, with identity (id) numbers of 1, 2, and 3. Memory Slots for Different Startup-Config Files A startup-config file stored in a memory slot has a unique, changeable file name.
  • Page 134 Switch Memory and Configuration Multiple Configuration Files on 5300xl and 4200vl Switches The result is that the startup-config file used to reboot the switch is modified by the actions in step 2. Boot Command Primary Boot Path Active Startup-Config File: Idle Startup-Config File: backupConfig workingConfig...

  • Page 135: Transitioning To Multiple Configuration Files

    Switch Memory and Configuration Multiple Configuration Files on 5300xl and 4200vl Switches Transitioning to Multiple Configuration Files If your 5300xl switch was shipped from the factory with software release E.08.xx or earlier installed, you must download software release E.09.xx or greater to use the multiple configuration feature.

  • Page 136: Listing And Displaying Startup-Config Files

    Switch Memory and Configuration Multiple Configuration Files on 5300xl and 4200vl Switches Listing and Displaying Startup-Config Files Command Page show config files Below show config < filename > 6-28 Viewing the Startup-Config File Status with Multiple Configuration Enabled Rebooting the switch with software release E.09.xx or later automatically enables the multiple configuration feature.
  • Page 137 Switch Memory and Configuration Multiple Configuration Files on 5300xl and 4200vl Switches — Continued from the previous page. — In the default configuration : • If the switch was shipped from the factory with software release E.09.xx installed in both the primary and secondary boot paths, then one startup-config file named config1 is used for both paths and is stored in memory slot 1.

  • Page 138: Displaying The Content Of A Specific Startup-Config File

    Switch Memory and Configuration Multiple Configuration Files on 5300xl and 4200vl Switches Displaying the Content of A Specific Startup-Config File With Multiple Configuration enabled, the switch can have up to three startup­ config files. Because the show config command always displays the content of the currently active startup-config file, the command extension shown below is needed to allow viewing the contents of any other startup-config files stored in the switch.
  • Page 139 1). Also, whenever the switch boots from secondary flash, the operator also wants the startup-config named newconfig to be used. The following two commands configure the desired behavior. ProCurve(config)# startup-default pri config minconfig ProCurve(config) # startup-default sec config newconfig. 6-29...

  • Page 140: Managing Startup-Config Files In The Switch

    Switch Memory and Configuration Multiple Configuration Files on 5300xl and 4200vl Switches Overriding the Default Reboot Configuration Policy. This command provides a method for manually rebooting with a specific startup-config file other than the file specified in the default reboot configuration policy. Syntax: boot system flash <...

  • Page 141: Renaming An Existing Startup-Config File

    Switch Memory and Configuration Multiple Configuration Files on 5300xl and 4200vl Switches Renaming an Existing Startup-Config File Syntax: rename config < current-filename > < newname-str > This command changes the name of an existing startup­ config file. A file name can include up to 63, alphanumeric characters.
  • Page 142 Switch Memory and Configuration Multiple Configuration Files on 5300xl and 4200vl Switches Figure 6-21. Example of Using One Startup-Config File for Both Primary and Secondary Flash If you wanted to experiment with configuration changes to the software version in secondary flash, you could create and assign a separate startup­ config file for this purpose.

  • Page 143: Erasing A Startup-Config File

    Switch Memory and Configuration Multiple Configuration Files on 5300xl and 4200vl Switches Erasing a Startup-Config File You can erase any of the startup-config files in the switch’s memory slots. In some cases, erasing a file causes the switch to generate a new, default- configuration file for the affected memory slot.

  • Page 144: Switch To Its Default Configuration

    Switch Memory and Configuration Multiple Configuration Files on 5300xl and 4200vl Switches Figure 6-23 illustrates using erase config < filename > to remove a startup-config file. Figure 6-23. Example of Erasing a Non-Active Startup-Config File With the same memory configuration as is shown in the bottom portion of figure 6-23, executing erase startup-config boots the switch from primary flash, resulting in a new file named minconfig in the same memory slot.
  • Page 145 Switch Memory and Configuration Multiple Configuration Files on 5300xl and 4200vl Switches • Boots the switch from primary flash using the new (default) configu­ ration in the startup-config file in memory slot 1. Since the primary flash in this instance does not support multiple configuration files, the multiple configuration feature does not operate until the switch is booted again using software release E.09.xx or greater.

  • Page 146: Transferring Startup-Config Files To Or From A Remote Server

    For example, the following command copies a startup-config file named test­ 01 from the switch to a (UNIX) TFTP server at IP address 10.10.28.14: ProCurve(config)# copy config test-01 tftp 10.10.28.14 test-01.txt unix TFTP: Copying a Configuration File from a Remote Host Syntax: copy tftp config <...

  • Page 147: Serially Connected Host

    For example, the following command copies a startup-config file named test­ 01.txt from a (UNIX) TFTP server at IP address 10.10.28.14 to the first empty memory slot in the switch: ProCurve(config)# copy tftp config test-01 10.10.28.14 test-01.txt unix Xmodem: Copying a Configuration File to a...

  • Page 148: Operating Notes For Multiple Configuration Files

    Switch Memory and Configuration Multiple Configuration Files on 5300xl and 4200vl Switches Operating Notes for Multiple Configuration Files SFTP/SCP: The configuration files are available for sftp/scp transfer as ■ /cfg/< filename >. ■ If you retain a software version earlier than E.09.xx on the switch, always reserve the first config memory slot (id = 1) for a configuration compatible with the earlier version.

  • Page 149: Contents

    Interface Access and System Information Contents Overview ........... . . 7-2 Interface Access: Console/Serial Link, Web, and Inbound Telnet .

  • Page 150: Overview

    Interface Access and System Information Overview Overview This chapter describes how to: ■ View and modify the configuration for switch interface access Use the CLI kill command to terminate a remote session ■ ■ View and modify switch system information For help on how to actually use the interfaces built into the switch, refer to: ■...

  • Page 151: Interface Access: Console/Serial Link, Web, And Inbound Telnet

    Interface Access and System Information Interface Access: Console/Serial Link, Web, and Inbound Telnet Interface Access: Console/Serial Link, Web, and Inbound Telnet Interface Access Features Feature Default Menu Inactivity Time 0 Minutes page 7-4 page 7-6 — (disabled) Inbound Telnet Access Enabled page 7-4 page 7-5...

  • Page 152: Menu: Modifying The Interface Access

    Interface Access and System Information Interface Access: Console/Serial Link, Web, and Inbound Telnet Menu: Modifying the Interface Access The menu interface enables you to modify these parameters: ■ Inactivity Timeout Inbound Telnet Enabled ■ Web Agent Enabled ■ To Access the Interface Access Parameters: From the Main Menu, Select...

  • Page 153: Cli: Modifying The Interface Access

    Console Control Options Figure 7-2. Listing of Show Console Command Reconfigure Inbound Telnet Access. In the default configuration, inbound Telnet access is enabled. Syntax: [no] telnet-server To disable inbound Telnet access: ProCurve(config)# no telnet-server To re-enable inbound Telnet access: ProCurve(config)# telnet-server...
  • Page 154 Telnet to another device that has an IP address. Syntax: telnet < ip-address > For example: ProCurve # telnet 10.28.27.204 Reconfigure Web Browser Access. In the default configuration, web browser access is enabled. Syntax: [no] web-management...
  • Page 155 Interface Access and System Information Interface Access: Console/Serial Link, Web, and Inbound Telnet All console parameter changes except events require that you save the config­ uration with write memory and then execute boot before the new console configuration will take effect. For example, to use one command to configure the switch with the following: ■...

  • Page 156: Sessions

    Interface Access and System Information Denying Interface Access by Terminating Remote Management Sessions Denying Interface Access by Terminating Remote Management Sessions The switch supports up to four management sessions. You can use show ip ssh to list the current management sessions, and kill to terminate a currently running remote session.

  • Page 157: System Information

    Configuring system information is optional, but recommended. System Name: Using a unique name helps you to identify individual devices where you are using an SNMP network management tool such as ProCurve Manager. System Contact and Location: This information is helpful for identifying the person administratively responsible for the switch and for identifying the locations of individual switches.

  • Page 158: Menu: Viewing And Configuring System Information

    Daylight Time Rule: Specifies the daylight savings time rule to apply for your location. The default is None. (For more on this topic, see appendix D, “Daylight Savings Time on ProCurve Switches.) Time: Used in the CLI to specify the time of day, the date, and other system parameters.

  • Page 159: Cli: Viewing And Configuring System Information

    Interface Access and System Information System Information 2. Press (for Edit). The cursor moves to the System Name field. 3. Refer to the online help provided with this screen for further information on configuration options for these features. 4. When you have finished making changes to the above parameters, press (for Save) and return to the Main Menu.
  • Page 160 Interface Access and System Information System Information Configure a System Name, Contact, and Location for the Switch. To help distinguish one switch from another, configure a plain-language identity for the switch. Syntax: hostname < name-string > snmp-server [contact <system-contact>] [location <system-location>] Both fields allow up to 48 characters.
  • Page 161 Syntax: time [ hh:mm [ :ss ]] [ mm/dd/ [ yy ] yy ] For example, to set the switch to 9:45 a.m. on November 17, 2002: ProCurve(config)# time 9:45 11/17/02 N o t e Executing reload or boot resets the time and date to their default startup values.

  • Page 162: Web: Configuring System Parameters

    Interface Access and System Information System Information Web: Configuring System Parameters In the web browser interface, you can enter the following system information: ■ System Name System Location ■ System Contact ■ For access to the MAC Age Interval and the Time parameters, use the menu interface or the CLI.

  • Page 163: Contents

    Configuring IP Addressing Contents Overview ........... . . 8-2 IP Configuration .

  • Page 164: Overview

    Configuring IP Addressing Overview Overview You can configure IP addressing through all of the switch’s interfaces. You can also: ■ Easily edit a switch configuration file to allow downloading the file to multiple switches without overwriting each switch’s unique gateway and VLAN 1 IP addressing.

  • Page 165: Just Want A Quick Start With Ip Addressing

    Switch Setup screen to quickly configure IP addressing. To do so, do one of the following: Enter setup at the CLI Manager level prompt. ■ ProCurve# setup Select 8. Run Setup in the Main Menu of the menu interface. ■...

  • Page 166: Ip Addressing With Multiple Vlans

    Configuring IP Addressing IP Configuration For more on using the Switch Setup screen, see the Installation and Getting Started Guide you received with the switch. IP Addressing with Multiple VLANs In the factory-default configuration, the switch has one, permanent default VLAN (named DEFAULT_VLAN) that includes all ports on the switch.

  • Page 167: Menu: Configuring Ip Address, Gateway, And Time-To-Live (Ttl)

    Configuring IP Addressing IP Configuration Menu: Configuring IP Address, Gateway, and Time-To- Live (TTL) Do one of the following: To manually enter an IP address, subnet mask, set the IP Config parameter ■ to Manual and then manually enter the IP address and subnet mask values you want for the switch.

  • Page 168: Cli: Configuring Ip Address, Gateway, And Time-To-Live (Ttl)

    Configuring IP Addressing IP Configuration 3. If the switch needs to access a router, for example, to reach off-subnet destinations, select the Default Gateway field and enter the IP address of the gateway router. 4. If you need to change the packet Time-To-Live (TTL) setting, select Default TTL and type in a value between 2 and 255.
  • Page 169 Configuring IP Addressing IP Configuration (You can also use the show management command to display the IP addressing and time server IP addressing configured on the switch. Refer to figure 9-6 on page 9-10.) For example, in the factory-default configuration (no IP addressing assigned), the switch’s IP addressing appears as: The Default IP Configuration...
  • Page 170 ProCurve(config)# vlan 1 ip address 10.28.227.103/24 This example deletes an IP address configured in VLAN 1. ProCurve (config) no vlan 1 ip address 10.28.227.103/24 Configure Multiple IP Addresses on a VLAN (Multinetting). You can configure up to eight IP addresses for the same VLAN. That is, the switch enables you to assign up to eight networks to a VLAN.
  • Page 171 Configuring IP Addressing IP Configuration 1. Go to VLAN 20. 2. Configure two additional IP addresses on VLAN 3. Display IP addressing. Figure 8-4. Example of Configuring and Displaying a Multinetted VLAN If you then wanted to multinet the default VLAN, you would do the following: Figure 8-5.

  • Page 172: Web: Configuring Ip Addressing

    Syntax: ip default-gateway < ip-address > For example: ProCurve(config)# ip default-gateway 10.28.227.115 Note The switch uses the IP default gateway only while operating as a Layer 2 device. While routing is enabled on the switch, the IP default gateway is not used.

  • Page 173: How Ip Addressing Affects Switch Operation

    • Stacking Candidate or Stack Member (Series 3400cl with suggested solutions and Series 6400cl switches only) • SNMP network management access such as • DHCP or Bootp support for automatic IP address ProCurve Manager for network configuration,...

  • Page 174: Dhcp/Bootp Operation

    Configuring IP Addressing IP Configuration DHCP/Bootp Operation Overview. DHCP/Bootp is used to provide configuration data from a DHCP or Bootp server to the switch. This data can be the IP address, subnet mask, default gateway, Timep Server address, and TFTP server address. If a TFTP server address is provided, this allows the switch to TFTP a previously saved configuration file from the TFTP server to the switch.
  • Page 175 Configuring IP Addressing IP Configuration DHCP Operation. A significant difference between a DHCP configuration and a Bootp configuration is that an IP address assignment from a DHCP server is automatic. Depending on how the DHCP server is configured, the switch may receive an IP address that is temporarily leased. Periodically the switch may be required to renew its lease of the IP configuration.

  • Page 176: Network Preparations For Configuring Dhcp/Bootp

    Configuring IP Addressing IP Configuration gw=10.66.77.1:\ lg=10.22.33.44:\ T144=”switch.cfg”:\ vm=rfc1048 where: 5300switch is a user-defined symbolic name to help you find the correct section of the bootptab file. If you have multiple switches that will be using Bootp to get their IP configuration, you should use a unique symbolic name for each switch.

  • Page 177: Configuration File Downloads

    Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads N o t e Designating a primary VLAN other than the default VLAN affects the switch’s use of information received via DHCP/Bootp. For more on this topic, refer to the chapter describing VLANs in the Advanced Traffic Management Guide for your switch.

  • Page 178: Enabling Ip Preserve

    Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads If the switch’s current IP addressing for VLAN 1 is from a DHCP server, ■ IP Preserve is suspended. In this case, whatever IP addressing the config­ uration file specifies is implemented when the switch downloads the file and reboots.
  • Page 179 Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads For example, consider Figure 8-7: DHCP TFTP Server Server Management config. Station Address Switch 1 Switch 2 Switch 4 Switch 3 VLAN 1: DHCP VLAN 1: VLAN 1: VLAN 1: 10.31.22.101 10.31.22.102...
  • Page 180 Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads If you apply this configuration file to figure 8-7, switches 1 - 3 will still retain their manually assigned IP addressing. However, switch 4 will be configured with the IP addressing included in the file.

  • Page 181: Contents

    Time Protocols Contents Overview ........... . . 9-2 TimeP Time Synchronization .

  • Page 182: Overview

    Time Protocols Overview Overview This chapter describes: ■ SNTP Time Protocol Operation Timep Time Protocol Operation ■ Using time synchronization ensures a uniform time among interoperating devices. This helps you to manage and troubleshoot switch operation by attaching meaningful time data to event and error messages. The switch offers TimeP and SNTP (Simple Network Time Protocol) and a timesync command for changing the time protocol selection (or turning off time protocol operation).

  • Page 183: Protocol Operation

    Time Protocols Selecting a Time Synchronization Protocol or Turning Off Time Protocol Operation ular server, it ignores time broadcasts from other SNTP servers unless the configurable expires three consecutive times without Poll Interval an update received from the first-detected server. Note To use Broadcast mode, the switch and the SNTP server must be in the same subnet.

  • Page 184: Disabling Time Synchronization

    Time Protocols SNTP: Viewing, Selecting, and Configuring Note that simply selecting a time synchronization protocol does not enable that protocol on the switch unless you also enable the protocol itself (step 2, above). For example, in the factory-default configuration, TimeP is the selected time synchronization method.

  • Page 185: Menu: Viewing And Configuring Sntp

    Time Protocols SNTP: Viewing, Selecting, and Configuring Table 9-1. SNTP Parameters SNTP Parameter Operation Time Sync Used to select either SNTP, TIMEP, or None as the time synchronization method. Method SNTP Mode Disabled The Default. SNTP does not operate, even if specified by the Menu interface Time Sync Method parameter or the CLI timesync command.
  • Page 186 Time Protocols SNTP: Viewing, Selecting, and Configuring Time Protocol Selection Parameter – TIMEP – SNTP – None Figure 9-1. The System Information Screen (Default Values) 2. Press (for ). The cursor moves to the field. Edit System Name 3. Use [v] to move the cursor to the Time Sync Method field.
  • Page 187 Time Protocols SNTP: Viewing, Selecting, and Configuring [>] i. Press to move the cursor to the field. Server Address ii. Enter the IP address of the SNTP server you want the switch to use for time synchronization. Note: This step replaces any previously configured server IP address.

  • Page 188: Cli: Viewing And Configuring Sntp

    Time Protocols SNTP: Viewing, Selecting, and Configuring CLI: Viewing and Configuring SNTP CLI Commands Described in this Section SNTP Command Page show sntp [no] timesync 9-10 and ff., 9-13 sntp broadcast 9-10 sntp unicast 9-11 sntp server 9-11 and ff. Protocol Version 9-13 poll-interval...
  • Page 189 Time Protocols SNTP: Viewing, Selecting, and Configuring Figure 9-4. Example of SNTP Configuration When SNTP Is the Selected Time Synchronization Method In the factory-default configuration (where TimeP is the selected time synchronization method), still lists the SNTP configuration even show sntp though it is not currently in use.

  • Page 190: Configuring (Enabling Or Disabling) The Sntp Mode

    Time Protocols SNTP: Viewing, Selecting, and Configuring Figure 9-6. Example of Display Showing IP Addressing for All Configured Time Servers and VLANs Configuring (Enabling or Disabling) the SNTP Mode Enabling the SNTP mode means to configure it for either broadcast or unicast mode.
  • Page 191 Time Protocols SNTP: Viewing, Selecting, and Configuring Syntax: sntp broadcast Configures as the SNTP mode. broadcast For example, suppose: ■ Time synchronization is in the factory-default configuration (TimeP is the currently selected time synchronization method). You want to: ■ 1. View the current time synchronization. 2.
  • Page 192 ProCurve(config)# timesync sntp Selects SNTP. ProCurve(config)# sntp unicast Activates SNTP in Unicast mode. ProCurve(config)# sntp server 10.28.227.141 Specifies the SNTP server and accepts the current SNTP server version (default: 3). In this example, the Poll Interval and the Protocol Version appear at their default settings.
  • Page 193 720 seconds. (This parameter is separate from the poll inter­ val parameter used for Timep operation.) For example, to change the poll interval to 300 seconds: ProCurve(config)# sntp poll-interval 300 Disabling Time Synchronization Without Changing the SNTP Configuration. The recommended method for disabling time synchroniza­...
  • Page 194 Time Protocols SNTP: Viewing, Selecting, and Configuring Figure 9-10. Example of SNTP with Time Sychronization Disabled Disabling the SNTP Mode. If you want to prevent SNTP from being used even if selected by (or the Menu interface’s param­ timesync Time Sync Method eter), configure the SNTP mode as disabled.

  • Page 195: Timep: Viewing, Selecting, And Configuring

    Time Protocols TimeP: Viewing, Selecting, and Configuring TimeP: Viewing, Selecting, and Configuring TimeP Feature Default Menu view the Timep time synchronization configuration page 9-16 page 9-18 — select Timep as the time synchronization method TIMEP page 9-14 pages 9-20 ff. —...

  • Page 196: Menu: Viewing And Configuring Timep

    Time Protocols TimeP: Viewing, Selecting, and Configuring Menu: Viewing and Configuring TimeP To View, Enable, and Modify the TimeP Protocol: 1. From the Main Menu, select: 2. Switch Configuration... 1. System Information Time Protocol Selection Parameter – TIMEP (the default) –...
  • Page 197 Time Protocols TimeP: Viewing, Selecting, and Configuring • Use the Space bar to select the mode. Manual [>] i. Press to move the cursor to the field. Server Address ii. Enter the IP address of the TimeP server you want the switch to use for time synchronization.

  • Page 198: Cli: Viewing And Configuring Timep

    Time Protocols TimeP: Viewing, Selecting, and Configuring CLI: Viewing and Configuring TimeP CLI Commands Described in this Section Command Page show timep 9-18 [no] timesync 9-20 ff., 9-23 ip timep dhcp 9-20 manual 9-21 server <ip-addr> 9-21 interval 9-22 no ip timep 9-23 This section describes how to use the CLI to view, enable, and configure TimeP parameters.
  • Page 199 Time Protocols TimeP: Viewing, Selecting, and Configuring If SNTP is the selected time synchronization method, still lists the show timep TimeP configuration even though it is not currently in use: Even though, in this example, SNTP is the current time synchronization method, the switch maintains the TimeP configuration.

  • Page 200: Configuring (Enabling Or Disabling) The Timep Mode

    Time Protocols TimeP: Viewing, Selecting, and Configuring Configuring (Enabling or Disabling) the TimeP Mode Enabling the TimeP mode means to configure it for either broadcast or unicast mode. Remember that to run TimeP as the switch’s time synchronization protocol, you must also select TimeP as the time synchronization method by using the CLI timesync command (or the Menu interface Time Sync Method parameter).
  • Page 201 For example, to select TimeP and configure it for manual operation using a TimeP server address of 10.28.227.141 and the default poll interval (720 minutes, assuming the TimeP poll interval is already set to the default): ProCurve(config)# timesync timep Selects TimeP. ProCurve(config)# ip timep manual 10.28.227.141 Activates TimeP in Manual mode. 9-21...
  • Page 202 1 to 9999 minutes. (This parameter is separate from the poll interval parameter used for SNTP operation.) Syntax: ip timep < dhcp | manual > interval < 1 - 9999 > For example, to change the poll interval to 60 minutes: ProCurve(config)# ip timep interval 60 9-22...
  • Page 203 Time Protocols TimeP: Viewing, Selecting, and Configuring Disabling Time Synchronization Without Changing the TimeP Configuration. The recommended method for disabling time synchroniza­ tion is to use the command. This halts time synchronization without timesync changing your TimeP configuration. Syntax: no timesync Disables time synchronization by changing the Time Synch Mode configuration to Disabled...

  • Page 204: Sntp Unicast Time Polling With Multiple Sntp Servers

    Time Protocols SNTP Unicast Time Polling with Multiple SNTP Servers SNTP Unicast Time Polling with Multiple SNTP Servers When running SNTP unicast time polling as the time synchronization method, the switch requests a time update from the server you configured with either the Server Address parameter in the menu interface, or the primary server in a list of up to three SNTP servers configured using the CLI.

  • Page 205: Displaying All Sntp Server Addresses Configured On The Switch

    Time Protocols SNTP Unicast Time Polling with Multiple SNTP Servers Displaying All SNTP Server Addresses Configured on the Switch The System Information screen in the menu interface displays only one SNTP server address, even if the switch is configured for two or three servers. The CLI show management command displays all configured SNTP servers on the switch.
  • Page 206 (See “Address Prioritization” on page 24.) Syntax: no sntp server < ip-addr > For example, to delete the primary address in the above example (and automatically convert the secondary address to primary): ProCurve(config)# no sntp server 10.28.227.141 9-26...

  • Page 207: Menu: Operation With Multiple Sntp Server Addresses Configured

    Time Protocols SNTP Messages in the Event Log Menu: Operation with Multiple SNTP Server Addresses Configured When you use the Menu interface to configure an SNTP server IP address, the new address writes over the current primary address, if one is configured. If there are multiple addresses configured, the switch re-orders the addresses according to the criteria described under “Address Prioritization”...
  • Page 208 Time Protocols SNTP Messages in the Event Log — This page is intentionally unused. — 9-28...

  • Page 209: Contents

    Port Status and Basic Configuration Contents Overview ........... . 10-2 Viewing Port Status and Configuring Port Parameters .

  • Page 210: Overview

    Port Status and Basic Configuration Overview Overview This chapter describes how to view the current port configuration and how to configure ports to non-default settings, including ■ Enable/Disable Mode (speed and duplex) ■ ■ Flow Control ■ Broadcast Limit Viewing Port Status and Configuring Port Parameters Port Status and Configuration Features Feature...
  • Page 211 Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Table 10-1. Status and Parameters for Each Port Type Status or Description Parameter Enabled Yes (default): The port is ready for a network connection. No: The port will not operate, even if properly connected in a network. Use this setting, for example, if the port needs to be shut down for diagnostic purposes or while you are making topology changes.
  • Page 212 Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Status or Description Parameter — Continued From Previous Page — 100/1000Base-T Ports: • auto-mdix (default): Senses speed and negotiates with the port at the other end of the link for port operation (MDI-X or MDI).
  • Page 213 Series 5300xl and Series 4200vl Switches: The broadcast-limit command operates at the global configuration context level to set the broadcast limit for all ports on the switch. Series 3400cl and Series 6400cl Switches: The broadcast-limit command operates at the port context level to set the broadcast limit on a per-port basis.

  • Page 214: Menu: Port Configuration

    (if configured) any trunk groups. From the Main Menu, select: 1. Status and Counters … 3. Port Status (3400cl and 6400cl switches) — or — 4. Port Status (5300cl and 4200vl switches) In this example,...
  • Page 215 Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Using the Menu To Configure Ports. N o t e The menu interface uses the same screen for configuring both individual ports and port trunk groups. For information on port trunk groups, refer to chapter 13, “Port Trunking”...

  • Page 216: Cli: Viewing Port Status And Configuring Port Parameters

    < port-list >: Shows a summary of network traffic handled by the specified ports. Series 3400cl and Series 6400cl switches include per-port broadcast limit settings in the show interfaces and show interfaces brief display outputs. The next two figures list examples of the output of the above two command options for the same port configuration.

  • Page 217: Configure Port Mode

    Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters This screen shows current port operating status. Note: The (per-port) Bcast Limit column appears only on the 3400cl and 6400cl switches. (The 5300xl switches apply a global broadcast limit. 3400cl/ 6400cl Switches Only Figure 10-4.
  • Page 218 For example, to configure ports C1 through C3 and port C6 for 100Mbps full- duplex, you would enter these commands: ProCurve(config)# int c1-c3,c6 speed-duplex 100-full Similarly, to configure a single port with the above command settings, you could either enter the same command with only the one port identified, or go to the context level for that port and then enter the command.

  • Page 219: Enabling Or Disabling Flow Control

    Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Enabling or Disabling Flow Control 3400cl/6400cl Switches: Flow-Control on these switches is enabled and ■ disabled on a per-port basis. ■ 5300xl and 4200vl Switches: You must first enable flow-control glo­...
  • Page 220 Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters For example, suppose that: You want to enable flow control on ports A1-A6. Later, you decide to disable flow control on ports A5 and A6. As a final step, you want to disable flow control on all ports. Assuming that flow control is currently disabled on the switch, you would use these commands: Enables global flow control.
  • Page 221 Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Disables per-port flow control on ports A5 and A6. Figure 10-8. Example Continued from Figure 10-7 Disables per-port flow control on ports A1 through A4 and global flow control. Flow control is now disabled on the switch.

  • Page 222: Configuring A Broadcast Limit On The Switch

    (on all ports) as a fixed limit. Broadcast-Limit on the 3400cl/6400cl Switches. Syntax: interface < port-list > broadcast-limit < 0 - 99 > (3400cl/6400cl Switches) Configures the theoretical maximum bandwidth percentage that the specified switch ports use to limit broadcasts and multicasts.

  • Page 223: Configuring Auto-Mdix

    100/1000-T xl module ports 10/100/1000-T xl module ports (MDI/MDI-X does not apply to the optional 10-gigabit ports on the Series 3400cl switches or the 10-gigabit ports on the Series 6400cl switches.) Using the above ports: ■ If you connect a copper port using a straight-through cable on a Series...
  • Page 224 Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters For more information on MDI-X, refer to the appendix titled “Switch Ports and Network Cables” in the Installation and Getting Started Guide for your switch. Manual Override. If you require control over the MDI/MDI-X feature you can set the switch to either of two non-default modes: ■...
  • Page 225 Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Syntax: show interfaces config Lists the current per-port Auto/MDI/MDI-X configuration. Syntax: show interfaces brief Where a port is linked to another device, this command lists the MDI mode the port is currently using. In the case of ports configured for Auto (auto-mdix), the MDI mode appears as either MDI or MDIX, depending upon which option the port has negotiated with the device on the other end of the link.

  • Page 226: Web: Viewing Port Status And Configuring Port Parameters

    Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Per-Port MDI Operating Mode Figure 10-11. Example of Displaying the Current MDI Operating Mode N o t e Upgrading the Switch Series 5300xl Operating System from E_07.XX or earlier: Copper ports in auto-negotiation still default to auto-mdix mode.

  • Page 227: Using Friendly (Optional) Port Names

    Port Status and Basic Configuration Using Friendly (Optional) Port Names Using Friendly (Optional) Port Names Feature Default Menu Configure Friendly Port Names Standard Port page 20 Numbering Display Friendly Port Names page 21 This feature enables you to assign alphanumeric port names of your choosing to augment automatically assigned numeric port names.

  • Page 228: Configuring Friendly Port Names

    Port Status and Basic Configuration Using Friendly (Optional) Port Names Configuring Friendly Port Names Syntax: interface < port-list > name < port-name-string > Assigns a port name to port-list. Syntax: no interface < port-list > name Deletes the port name from port-list. Configuring a Single Port Name.

  • Page 229: Displaying Friendly Port Names With Other Port Data

    Port Status and Basic Configuration Using Friendly (Optional) Port Names Displaying Friendly Port Names with Other Port Data You can display friendly port name data in the following combinations: show name: Displays a listing of port numbers with their corresponding ■...
  • Page 230 Port Status and Basic Configuration Using Friendly (Optional) Port Names Port Without a “Friendly” Name Friendly port names assigned in previous examples. Figure 10-15. Example of Friendly Port Name Data for Specific Ports on the Switch Including Friendly Port Names in Per-Port Statistics Listings. A friendly port name configured to a port is automatically included when you display the port’s statistics output.
  • Page 231 Port Status and Basic Configuration Using Friendly (Optional) Port Names For a given port, if a friendly port name does not exist in the running-config file, the Name line in the above command output appears as: Name not assigned To Search the Configuration for Ports with Friendly Port Names. This option tells you which friendly port names have been saved to the startup­...
  • Page 232 Port Status and Basic Configuration Using Friendly (Optional) Port Names — This page is intentionally unused. — 10-24...

  • Page 233: Contents

    Power Over Ethernet (PoE) Operation for the Series 5300xl Switches Contents PoE Operation on the Series 5300xl Switches ....11-3 Introduction ..........11-3 PoE Terminology .

  • Page 234: Poe Operation On The Series 5300Xl Switches

    PoE technology allows IP telephones, wireless LAN access points, and other appliances to receive power and transfer data over existing LAN cabling. (For more on this topic, refer to edition 2 or later of the ProCurve xl Modules Installation Guide shipped with your optional J8161A Switch xl PoE Module (beginning in April, 2004).

  • Page 235: Poe Terminology

    External Power Supply; for example, an HP 600 ProCurve RPS/EPS or a ProCurve 610 EPS. An EPS device provides power to provision PoE ports on a module. See also "RPS", below. Maintenance Power Signature; the signal a PD sends to the switch to indicate that the PD is connected and requires power.

  • Page 236: Overview Of Operation

    5300xl device supplies PoE power over the data pin/wire pairs. For more on this topic, refer to the PoE Planning and Imple­ mentation Guide (p/n 5990-6045, Nov. 2003 or later) available on the ProCurve Networking web site. (See “Getting Documentation From the Web” on page 1­...

  • Page 237: General Poe Operation

    The ProCurve Networking web site at http://www.procurve.com. (Click on technical support, then Product manuals (all).) The latest version of any ProCurve product guide is always on the ProCurve Networking web site. See to “Getting Documentation From the Web” on page 1-6.

  • Page 238: Pd Support

    Power Over Ethernet (PoE) Operation for the Series 5300xl Switches General PoE Operation Note The ports on a PoE module support standard networking links and PoE links. Thus, you can connect either a non-PoE device or a PD to a PoE-enabled port without reconfiguring the port.
  • Page 239 PoE Module” on page 11-21. If a ProCurve EPS device is supplying PoE power to two PSE devices, then both PSE devices receive 204 watts. If a ProCurve EPS device is delivering PoE power to only one PSE device, then that device receives 408 watts.

  • Page 240: Power Priority Operation

    Power Over Ethernet (PoE) Operation for the Series 5300xl Switches General PoE Operation Power Priority Operation When Does an xl PoE Module Prioritize Power Allocations? If an xl PoE module can provide power for all connected PD demand, it does not use its power priority settings to allocate power.
  • Page 241 Critical In this example, the following CLI command sets ports C3-C17 to Critical: ProCurve(config)# interface c3-c17 power critical The Critical priority class always receives power. If there is not enough power to provision PDs on all of the ports configured for this class, then no power goes to ports configured for High and Low priority.

  • Page 242: Configuring Poe Operation

    You can use one command to set the same priority level on PoE ports in multiple modules. For example, to configure the priority to High for ports c5-c10, C23-C24, D1-D10, and D12, you could use this command: ProCurve(config)# interface c5-c10,c23-c24,d1­ d10,d12 11-10...

  • Page 243: Disabling Or Re-Enabling Poe Port Operation

    In this case, executing the following command sets the global notification threshold to 70% of available PoE power. ProCurve(config)# power threshold 70 With this setting, if an increasing PoE power demand crosses this threshold on the module in slot B, the switch sends an SNMP trap and generates this Event Log message: Slot B POE usage has exceeded threshold of 70 %.

  • Page 244: Configuring Optional Poe Port Identifiers

    PoE module in slot “A” to 75% and the threshold for the module in slot “B” to 68% by executing the following two commands: ProCurve(config)# power slot a threshold 75 ProCurve(config)# power slot b threshold 68 Note that the last threshold command affecting a given slot supersedes the previous threshold command affecting the same slot.
  • Page 245 Power Over Ethernet (PoE) Operation for the Series 5300xl Switches Configuring PoE Operation 1. Use the walkmib pethPsePortType.< slot-# > command to determine the MIB-based port number for the port to which you want to assign a Configured Type identifier. On the 5300xl switches the slot numbering is as follows: Slot Slot Number...
  • Page 246 For example, to return port B2 in the above figure to a null setting, use this command: ProCurve(config)# setmib pethPsePortType.2.27 -D " " For more on displaying PoE configuration and status, refer to “Viewing PoE Configuration and Status” on page 11-15.

  • Page 247: Viewing Poe Configuration And Status

    Power Over Ethernet (PoE) Operation for the Series 5300xl Switches Viewing PoE Configuration and Status Viewing PoE Configuration and Status Displaying the Switch’s Global PoE Power Status Syntax: show power-management Displays the switch’s global PoE power status, including: • Maximum Power: Lists the maximum PoE wattage available to provision active PoE ports on the switch.

  • Page 248: Displaying An Overview Of Poe Status On All Ports

    Power Over Ethernet (PoE) Operation for the Series 5300xl Switches Viewing PoE Configuration and Status Displaying an Overview of PoE Status on All Ports Syntax: show power-management brief Displays the following port power status: • Port: Lists all PoE-capable ports on the switch. • Power Enable: Shows Yes for ports enabled to support PoE (the default) and No for ports on which PoE is disabled.

  • Page 249: Displaying The Poe Status On Specific Ports

    Power Over Ethernet (PoE) Operation for the Series 5300xl Switches Viewing PoE Configuration and Status Ports C1 through C4 are delivering power. The remaining ports are available to supply power, but currently do not detect a connected PD. Figure 11-3. Example of Show Power-Management Brief Output Displaying the PoE Status on Specific Ports Syntax: show power-management <...
  • Page 250 Power Over Ethernet (PoE) Operation for the Series 5300xl Switches Viewing PoE Configuration and Status Syntax: show power-management < port-list > (Continued) Power Denied Cnt: Shows the number of times PDs requesting • power on the port have been denied due to insufficient power available.

  • Page 251: Planning And Implementing A Poe Configuration

    Configuration This section provides an overview of some considerations for planning a PoE application. For additional information on this topic, refer to the ProCurve PoE Planning and Implementation Guide. Some of the elements you may want to consider for a PoE installation include: ■...

  • Page 252: Assigning Priority Policies To Poe Traffic

    For more information on security options, refer to the latest edition of the Access Security Guide for your switch. (The ProCurve Networking web site offers the latest version of all ProCurve product publications. Refer to “Getting Documentation from the Web” in chapter 1, “Getting Started”.)

  • Page 253: Calculating The Maximum Load For An Xl Poe Module

    Power Over Ethernet (PoE) Operation for the Series 5300xl Switches Planning and Implementing a PoE Configuration Calculating the Maximum Load for an xl PoE Module Since the full PoE load on an xl PoE module receiving 408 watts (from an EPS supporting only that module) cannot exceed 369.6 watts (24 ports with a maximum of 15.4 watts per port), there is no concern for overloading the module’s PoE capacity.

  • Page 254: Poe Operating Notes

    For example, to cycle the power on a PoE device connected to port 1 on an xl PoE module installed in slot D: ProCurve(config)# no interface d1 power ProCurve(config)# interface d1 power 11-22...

  • Page 255: Poe Event Log Messages

    Power Over Ethernet (PoE) Operation for the Series 5300xl Switches PoE Operating Notes PoE Event Log Messages PoE operation generates these Event Log messages. You can also configure the switch to send these messages to a configured debug destination (terminal device or SyslogD server).

  • Page 256: Warning" Poe Event-Log Messages

    < fault-type > is one of the following: • Over Current fault: The external power supply reported a fault condition. Contact your ProCurve support representative. • Fan fault: A fan in an external power supply has failed.
  • Page 257 Power Over Ethernet (PoE) Operation for the Series 5300xl Switches PoE Operating Notes Port < port-id > PD Invalid Signature indication. The switch has detected a non-802.3af-compliant device on the indicated port. This message appears for all non-802.3af devices connected to the port, such as other switches, PC-NICs, etc. Port <...
  • Page 258 Power Over Ethernet (PoE) Operation for the Series 5300xl Switches PoE Operating Notes —This page is intentionally unused— 11-26...

  • Page 259: Contents

    for the Series 5300xl Access Controller xl Module Switches Contents Introduction ..........12-3 General Operation .
  • Page 260 Access Controller xl Module for the Series 5300xl Switches Contents Managing the ACM ......... . 12-27 Using the ACM’s Extended CLI .

  • Page 261: Introduction

    Access Controller xl Module for the Series 5300xl Switches Introduction Introduction The ProCurve Access Controller xl Module (ACM) enables secure, mobile user access to appropriate network services on any ProCurve Series 5300xl switch. This modular addition to the 5300xl switch offers a unique approach to integrating identity-based user access control, wireless data privacy and secure roaming with the flexibility of a full-featured intelligent edge switch.

  • Page 262: Terminology

    The Access Control Server is deployed as a dedicated control function and does not sit in the user data path. The Secure Access 700wl Series has two products that provide this capability: the ProCurve Access Control Server 740wl and the Integrated Access Manager 760wl.

  • Page 263: Access Controller Xl Module Overview

    VPN services, and application persistence across subnet boundaries at the edge of the network, where users connect. Centrally managed from the ProCurve Secure Access Control Server 740wl or Integrated Access Manager 760wl, the Access Controller xl Module provides hassle-free access while maintaining a high level of security.
  • Page 264 VLAN that can communicate with the 740wl or 760wl. The ACM establishes communication with the 740wl/760wl, using the IP address and the shared secret from step 2 above. See the ProCurve xl Modules Installation Guide for details.

  • Page 265: Using 5300Xl Features With The Access Controller Xl Module

    Access Controller xl Module for the Series 5300xl Switches Using 5300xl Features with the Access Controller xl Module 4. Configure downlink client ports, client VLANs, uplink network ports, and the uplink VLAN on the 5300xl switch. Configure access and user/group policy rights on the 740wl/760wl to support and manage clients and client traffic through the ACM.
  • Page 266 Access Controller xl Module for the Series 5300xl Switches Using 5300xl Features with the Access Controller xl Module Note 5300xl switch ports that are not used by the Access Controller xl Module (that is, they are not downlink client ports, or members of client VLANs) continue to operate as regular 5300xl ports.
  • Page 267 Access Controller xl Module for the Series 5300xl Switches Using 5300xl Features with the Access Controller xl Module Table 12-1. 5300xl Switch Features Not Supported on an ACM (Continued) Feature Explanation IP Routing/ No routing is done. Not allowed. Multicast Routing IP Stacking Not supported across an ACM.

  • Page 268: Routing Infrastructure Support

    Access Controller xl Module for the Series 5300xl Switches Using 5300xl Features with the Access Controller xl Module Routing Infrastructure Support The ACM uses IP to communicate with Access Control Server 740wls, Inte­ grated Access Managers 760wls and Access Controller 720wls. The default gateway must be set up correctly if there is a router in the communications path.

  • Page 269: Using 5300Xl Switch Network Address Translation With The Acm

    Access Controller xl Module for the Series 5300xl Switches Using 5300xl Features with the Access Controller xl Module Figure 12-3. A Downlink Client Port with a Non-Routed Network Structure Using 5300xl Switch Network Address Translation with the ACM The Secure Access 700wl series products and the ACM provide network address translation for client traffic.

  • Page 270: The Role Of Vlans

    Access Controller xl Module for the Series 5300xl Switches Using 5300xl Features with the Access Controller xl Module The Role of VLANs VLANs are used by the Access Controller xl Module to manage client traffic through the switch. Downlink client ports, connecting to access points, either directly or through an intermediate network, are assigned as untagged mem­...

  • Page 271: Static Vlan Features Supported On Client Vlans

    Access Controller xl Module for the Series 5300xl Switches Using 5300xl Features with the Access Controller xl Module Downlink client ports must be members of some other VLAN before they can be removed from a client VLAN. If you use the no access-controller <slot-id> client-ports [e] <port-list>...

  • Page 272: General Operating Rules

    Access Controller xl Module for the Series 5300xl Switches General Operating Rules General Operating Rules ■ Uplink and downlink ports cannot be members of the same VLAN. Switch 5300xl features used to manage ports that are connected to ■ bridges don’t apply, as the ACM is not a bridge. A client VLAN containing the downlink port, <slot-id>DP, is automat­...
  • Page 273 Access Controller xl Module for the Series 5300xl Switches Configuring the ACM on the Network Note ‘ProCurve’ is used as a generic prompt for all 5300xl switches. The term ‘id’ is used below for ‘slot-id’ to shorten the command prompt. ProCurve (config)# access-controller <slot-id>...

  • Page 274: Configuring The Access Controller Xl Module

    VID. Switch ports become untagged members of the client VLAN. The downlink port also becomes a tagged member of the client VLAN. From the CLI command prompt at the global configuration level, enter ProCurve (config) #access-controller <slot-id> client-ports <port list> 12-16...
  • Page 275 VLANs (see Figure 12­ 5). BDP, the downlink port for the module in slot B, is a tagged member of both client VLANs. ProCurve Switch 5308xl(config)# access-controller b client-ports a2,a6 ProCurve Switch 5308xl(config)# access-controller b ProCurve Switch 5308xl(access-controller-B)# show vlans...

  • Page 276: Changing The Vlan-Base

    Use the following command to configure a client VLAN: ProCurve (Config)# access-controller <slot-id> client-ports vlan <vlan-list> where <slot-id> is the slot letter where the module is installed. <vlan-list> is the VID for the desired client VLAN.

  • Page 277: Configuring Uplink Network Ports

    VLAN. Be sure that the new VLAN allows communication with the 740wl/760wl, or communications is lost. ProCurve (Config)# vlan 25 untagged <slot-id>up where slot-id is the 5300xl switch slot where the ACM module is installed. This command configures a new uplink VLAN, VID 25, for the ACM module installed in slot n.

  • Page 278: Acm Configuration Commands Summary And Syntax

    Access Controller xl Module for the Series 5300xl Switches Configuring the Access Controller xl Module ACM Configuration Commands Summary and Syntax Command Page Configuration Context access-controller <slot-id> 1220 [no] access-controller <slot-id> client-ports [e] < port-list > 1221 [no] access-controller <slot-id> client-ports vlan < vlan-list > 1222 access-controller <slot-id>...
  • Page 279 Access Controller xl Module for the Series 5300xl Switches Configuring the Access Controller xl Module Syntax: [no] access-controller <slot-id> client-ports [ethernet] < port-list > Assigns switch ports (port-list) to separate client VLANs for the access controller in slot-id (a - h). The ports are removed from all other VLANs.

  • Page 280: Access Controller Context Command Syntax

    Access Controller xl Module for the Series 5300xl Switches Configuring the Access Controller xl Module Syntax: [no] access-controller <slot-id> client-ports vlan < vlan-list > Configures client VLANs with the VIDs given, contain­ ing only the downlink port, (<slot-id>DP), as a tagged member.
  • Page 281 Access Controller xl Module for the Series 5300xl Switches Configuring the Access Controller xl Module Syntax: enable extended-commands Changes the CLI to the access controller extended com­ mands context. A limited set of commands from the 720wl CLI is provided here. See “Using the ACM’s Extended CLI”...

  • Page 282: Displaying Access Controller Xl Status From The 5300Xl Cli

    Access Controller xl Module for the Series 5300xl Switches Displaying Access Controller xl Status from the 5300xl CLI Displaying Access Controller xl Status from the 5300xl CLI Show commands are available in both the configuration context and the access controller context of the 5300xl CLI. These commands display ACM status and configuration.

  • Page 283: Configuration Context Command Syntax

    Access Controller xl Module for the Series 5300xl Switches Displaying Access Controller xl Status from the 5300xl CLI Configuration Context Command Syntax Syntax: show access-controller <slot-id> Displays the following for the access controller in slot-id (a - h). Versions ACM version information for support staff.

  • Page 284: Access Controller Context Command Syntax

    Access Controller xl Module for the Series 5300xl Switches Displaying Access Controller xl Status from the 5300xl CLI Syntax: show access-controller vlan-base Displays the starting VLAN ID (VID) for client VLANs configured by the access-controller <slot-id> client-ports < port-list > or the access-controller <slot-id> client-ports vlan <...

  • Page 285: Managing The Acm

    720wl CLI commands. They are documented in the ProCurve Secure Access 700wl Series Management and Configuration Guide, avail­ able on the CD shipped with the ACM, or from the ProCurve Networking Web site at http://www.procurve.com. (Click on Technical support, then Product man­...
  • Page 286 Access Controller xl Module for the Series 5300xl Switches Managing the ACM ProCurve(access-controller-id-ext)# The available commands are listed below. Detailed descriptions are found in Appendix A, “Command Line Interface” in the ProCurve Secure Access 700wl Series Management and Configuration Guide. Command [no] ip address <<ip-addr>/<1-32> | <ip-addr> <mask>>...
  • Page 287 Access Controller xl Module for the Series 5300xl Switches Managing the ACM Command set dhcp <on | off> set dhcpserver <ip-addr> set dns <primary-ip-addr> [<secondary-ip-addr>] set domainname <domain> set forwardipbroadcasts <all | none | on <port> | off <port> | <port>> set gateway <ip-addr>...

  • Page 288: Downloading New Software To The Module

    Access Controller xl Module for the Series 5300xl Switches Managing the ACM Command show natdhcp show product show serial show sharedsecret show status show syslogserver show temperature show time show upgrade show upgradeproxy show version show vlans show vpn terminal length <2..1000> terminal width <61…...

  • Page 289: Operating Notes

    Management VLAN. Client-to-client communications is not possible through an ACM. ■ ProCurve Manager does not support the ACM at this time. Support is ■ expected later in 2005. BIOS POST Event Log Messages...
  • Page 290 Access Controller xl Module for the Series 5300xl Switches BIOS POST Event Log Messages System memory failure. 0x0002 Shadow memory failure. 0x0004 Protected memory failure. 0x0020 CMOS not ready error. 0x0040 Periodic timer failure. 0x0100 Device configuration error. 0x0800 Memory configuration error. 0x1000 Non-volatile RAM failure.

  • Page 291: Contents

    Port Trunking Contents Overview ........... . 13-2 Port Trunk Features and Operation .

  • Page 292: Overview

    Port Trunking Overview Overview This chapter describes creating and modifying port trunk groups. This includes non-protocol trunks and LACP (802.3ad) trunks. Port Status and Configuration Features Feature Default Menu viewing port trunks page 13-9 page 13-11 page 13-17 configuring a static trunk none page 13-9 page 13-15...
  • Page 293 Port Trunking Overview Port Connections and Configuration: All port trunk links must be point- to-point connections between a switch covered by this guide and another switch, router, server, or workstation configured for port trunking. No inter­ vening, non-trunking devices are allowed. It is important to note that ports on both ends of a port trunk group must have the same mode (speed and duplex) and flow control settings.

  • Page 294: Port Trunk Features And Operation

    Series 4200vl Switches Series 3400cl Switches Up to 25 Trunk Groups* Series 6400cl Switches *Actual maximum depends on the number of ports available on the switch and the number of links in each trunk. (Using the Link Aggregation Control Protocol—LACP—option, you can include standby trunked ports in addition to the maximum of eight actively trunking ports.)

  • Page 295: Trunk Configuration Methods

    (the default) LACP-passive: ProCurve(config)# no int c1-c4 lacp Removes the ports from the trunk. ProCurve(config)# int c1-c4 lacp passive Configures LACP passive. Static Trunk: The switch uses the links you configure with the Port/Trunk Settings screen in the menu interface or the trunk command in the CLI to create a static port trunk.
  • Page 296 For more information, refer to “Trunk Group Operation Using LACP” on page 13-18. Trunk Provides manually configured, static-only trunking to: (non- • Most ProCurve switches and routing switches not running the 802.3ad LACP protocol. protocol) • Windows NT and HP-UX workstations and servers Use the Trunk option when: – The device to which you want to create a trunk link is using a non-802.3ad trunking protocol...
  • Page 297 Port Trunking Trunk Configuration Methods Table 13-3. General Operating Rules for Port Trunks Media: For proper trunk operation, all ports on both ends of a trunk group must have the same media type and mode Auto (speed and duplex). (For the switches covered by this guide, HP recommends leaving the port Mode setting at Auto-10 in networks using Cat 3 cabling, Port Configuration: The default port configuration is Auto, which enables a port to sense speed and negotiate duplex with...
  • Page 298 Port Trunking Trunk Configuration Methods Spanning Tree: 802.1D (STP) and 802.1w (RSTP) Spanning Tree operate as a global setting on the switch (with one instance of Spanning Tree per switch). 802.1s (MSTP) Spanning Tree operates on a per-instance basis (with multiple instances allowed per switch).

  • Page 299: Menu: Viewing And Configuring A Static Trunk Group

    Port Trunking Menu: Viewing and Configuring a Static Trunk Group Menu: Viewing and Configuring a Static Trunk Group Important Configure port trunking before you connect the trunked links to another switch, routing switch, or server. Otherwise, a broadcast storm could occur. (If you need to connect the ports before configuring them for trunking, you can temporarily disable the ports until the trunk is configured.
  • Page 300 Port Trunking Menu: Viewing and Configuring a Static Trunk Group • For proper trunk operation, all ports in a trunk must have the same media type and mode (such as 10/100TX set to 100FDx, or 100FX set to 100FDx). The flow control settings must also be the same for all ports in a given trunk.

  • Page 301: Cli: Viewing And Configuring Port Trunk Groups

    Port Trunking CLI: Viewing and Configuring Port Trunk Groups 8. Connect the trunked ports on the switch to the corresponding ports on the opposite device. If you previously disabled any of the trunked ports on the switch, enable them now. (See “Viewing Port Status and Configur­ ing Port Parameters”...
  • Page 302 Port Trunking CLI: Viewing and Configuring Port Trunk Groups Using a port list specifies, for switch ports in a static trunk group, only the ports you want to view. In this case, the command specifies ports A5 through A7. However, because port A6 is not in a static trunk group, it does not appear in the resulting listing: Port A5 appears with an example of a name that you can optionally assign using the Friendly Port Names feature.
  • Page 303 Port Trunking CLI: Viewing and Configuring Port Trunk Groups Listing Static LACP and Dynamic LACP Trunk Data. Syntax: show lacp Lists data for only the LACP-configured ports.. In the following example, ports A1 and A2 have been previously configured for a static LACP trunk. (For more on “Active”, see table 11-13-5 on page 13-21.) Figure 13-8.

  • Page 304: Using The Cli To Configure A Static Or Dynamic Trunk Group

    Trunks configured as FEC (Fast Ethernet Channel) are not supported. To configure port trunk groups, use static or LACP trunks. For release notes describing the latest software updates, visit the ProCurve Networking web site at http://www.procureve.com. Click on Technical support, and then click on Product manuals (all).
  • Page 305 This example uses ports C4 - C6 to create a non-protocol static trunk group with the group name of Trk2. ProCurve(config)# trunk c4-c6 trk2 trunk Removing Ports from a Static Trunk Group. This command removes one or more ports from an existing Trkx trunk group.
  • Page 306 < port-list >. This example uses ports C4 and C5 to enable a dynamic LACP trunk group. ProCurve(config)# interface c4-c5 lacp active Removing Ports from an Dynamic LACP Trunk Group. To remove a port from dynamic LACP trunk operation, you must turn off LACP on the port.

  • Page 307: Web: Viewing Existing Port Trunk Groups

    C6 from the dynamic trunk and return it to passive LACP, you would do the following: ProCurve(config)# no interface c6 lacp ProCurve(config)# interface c6 lacp passive Note that in the above example, if the port on the other end of the link is configured for active LACP or static LACP, the trunked link will be re­...

  • Page 308: Trunk Group Operation Using Lacp

    Port Trunking Trunk Group Operation Using LACP Trunk Group Operation Using LACP The switch can automatically configure a dynamic LACP trunk group or you can manually configure a static LACP trunk group. N o t e LACP requires full-duplex (FDx) links of the same media type (10/100Base-T, 100FX, etc.) and the same speed, and enforces speed and duplex conformance across a trunk group.
  • Page 309 Port Trunking Trunk Group Operation Using LACP Table 13-4. LACP Trunk Types LACP Port Trunk Operation Configuration 802.3ad-compliant Dynamic LACP This option automatically establishes an trunk group, with LACP for the port Type parameter and DynX for the port Group name, where X is an automatically assigned value from 1 to 36, depending on how many dynamic and static trunks are currently on the switch.
  • Page 310 Port Trunking Trunk Group Operation Using LACP LACP Port Trunk Operation Configuration Static LACP Provides a manually configured, static LACP trunk to accommodate these conditions: • The port on the other end of the trunk link is configured for a static LACP trunk. • You want to configure non-default spanning tree or IGMP parameters on an LACP trunk group.

  • Page 311: Default Port Operation

    LACP trunking. A link having two passive LACP ports will not perform LACP trunking because both ports are waiting for an LACP protocol packet from the opposite device. Note: For the Series 4200vl switches, LACP is turned off by default. For the 5300xl, 3400cl, and 6400cl switches, all ports are configured for passive LACP by default.

  • Page 312: Lacp Notes And Restrictions

    LACP (active or passive) is configured, the switch removes the LACP configuration, displays a notice that LACP is disabled on the port(s), and enables port security on that port. For example: ProCurve(config)# port-security a17 learn-mode static address-limit 2 LACP has been disabled on secured port(s).
  • Page 313 Port Trunking Trunk Group Operation Using LACP ProCurve(config)# int a17 lacp passive Error configuring port A17: LACP and port security cannot be run together. ProCurve(config)# To restore LACP to the port, you must remove port security and re-enable LACP active or passive.
  • Page 314 Port Trunking Trunk Group Operation Using LACP If there are ports that you do not want on the default VLAN, ensure that ■ they cannot become dynamic LACP trunk members. Otherwise a traffic loop can unexpectedly occur. For example: VLAN-1 VLAN-1 VLAN-1 VLAN-1...

  • Page 315: Trunk Group Operation Using The "Trunk" Option

    Use the Trunk option to establish a trunk group between a 5300xl, 3400cl, or 6400cl switch and another device, where the other device’s trunking operation fails to operate properly with LACP trunking configured on the 5300xl or LACP trunking configured on the 3400/6400cl switches or 4200vl switches.

  • Page 316: How The Switch Lists Trunk Data

    In actual networking environments, this is rarely a problem. However, if it becomes a problem, you can use the ProCurve 13-26...
  • Page 317 Port Trunking Outbound Traffic Distribution Across Trunked Links Manager Plus network management software to quickly and easily identify the sources of heavy traffic (top talkers) and make adjustments to improve performance. Broadcasts, multicasts, and floods from different source addresses are dis­ tributed evenly across the links.
  • Page 318 Port Trunking Outbound Traffic Distribution Across Trunked Links 13-28...

  • Page 319: Contents

    Jumbo Packets on the Series 3400cl and Series 6400cl Switches ......14-27 Terminology ..........14-27 Operating Rules .
  • Page 320 Port Traffic Controls Contents Viewing the Current Jumbo Configuration ....14-30 Enabling or Disabling Jumbo Traffic on a VLAN ... . 14-32 Operating Notes for Jumbo Traffic-Handling .

  • Page 321: Overview

    Jumbo Packets (3400cl and 6400cl Only): Enables ports operating at ■ 1 Gbs or 10 Gbps speeds to accept inbound packets of up to 9220 bytes when configured for jumbo traffic.

  • Page 322: Xl, 3400Cl And 6400Cl Switches

    [ port-list ] page 14-6 N o t e This feature applies to the 5300xl, 3400cl, and 6400cl switches. Introduction Rate-Limiting for all traffic provides a method for limiting the amount of bandwidth a user or device may utilize inbound on a switch port. This effectively sets an inbound usage level on a given port, and is a tool for enforcing maximum service level commitments granted to network users.

  • Page 323: Rate-Limiting Operation

    QoS mask. This affects the resources available for configuring QoS and ACLs. If you plan to configure QoS and/or ACLs on a 3400cl and 6400cl 3400cl or 6400cl switch, refer to the chapters on these topics in the Advanced Switches Traffic Management Guide for your switch.

  • Page 324: Displaying The Current Rate-Limit Configuration

    Port Traffic Controls All-Traffic Rate-Limiting for the 5300xl, 3400cl and 6400cl Switches For example, either of the following commands configures an inbound rate limit of 60% on ports A3 - A5: ProCurve (config)# int a3-a5 rate-limit all 60 ProCurve (eth-A3-A5)# rate-limit all 60 Displaying the Current Rate-Limit Configuration This command displays the per-port rate-limit configuration in the running­...

  • Page 325: Operating Notes For Rate-Limiting

    Port Traffic Controls All-Traffic Rate-Limiting for the 5300xl, 3400cl and 6400cl Switches The outbound port priority queues 1 - 4 for ports A1-A2 are configured with the indicated Guaranteed Minimum Bandwidth percentages. Ports A3-A5 are configured with a rate limit of 60 %. (Ports A1 and A2 are not configured for rate-limiting.)
  • Page 326 Port Traffic Controls All-Traffic Rate-Limiting for the 5300xl, 3400cl and 6400cl Switches rate limit. In this case, the inbound traffic flow does not reach the configured rate and lower priority traffic is not forwarded into the switch fabric from the rate-limited port. (This behavior is termed “head-of-line blocking”...
  • Page 327 Port Traffic Controls All-Traffic Rate-Limiting for the 5300xl, 3400cl and 6400cl Switches Network Stress Conditions: Under normal network operating condi­ ■ tions, rate-limiting limits inbound traffic on a port to no more than the configured level. However, under network stress conditions, the port may allow occasional bursts of inbound traffic forwarding that exceed the configured rate.

  • Page 328: Icmp Rate-Limiting

    Port Traffic Controls All-Traffic Rate-Limiting for the 5300xl, 3400cl and 6400cl Switches ICMP Rate-Limiting In IP networks, ICMP messages are generated in response to either inquiries or requests from routing and diagnostic functions. These messages are directed to the applications originating the inquiries. In unusual situations, if the messages are generated rapidly with the intent of overloading network circuits, they can threaten network availability.
  • Page 329 Port Traffic Controls All-Traffic Rate-Limiting for the 5300xl, 3400cl and 6400cl Switches C a u t i o n The ICMP protocol is necessary for routing, diagnostic, and error responses in an IP network. ICMP rate-limiting is primarily used for throttling worm or virus-like behavior, and should normally be configured to allow one to five per cent of available inbound bandwidth to be used for ICMP traffic.
  • Page 330 Port Traffic Controls All-Traffic Rate-Limiting for the 5300xl, 3400cl and 6400cl Switches ICMP Rate-Limit at 5% ICMP Rate-Limit at 1% Dormitory 1 5300xl Switch 5300xl Switch Router Dormitory 2 Dormitory 3 5300xl Switch Dormitory 4 Classroom Backup Server Administration Building...
  • Page 331 Port Traffic Controls All-Traffic Rate-Limiting for the 5300xl, 3400cl and 6400cl Switches All ports belonging to a trunk configured for ICMP rate-limiting operate ■ according to the trunk configuration, regardless of the ICMP rate-limiting state that existed on the port prior to its being added to the trunk. (While a port is in a trunk, any ICMP rate-limiting previously configured for that port is suspended, but remains in the switch configuration.)
  • Page 332 Port Traffic Controls All-Traffic Rate-Limiting for the 5300xl, 3400cl and 6400cl Switches Configuring Inbound Rate-Limiting. This command controls inbound usage of a port by setting a limit on the bandwidth available for inbound traffic. Syntax: [no] int < port- list | trunk-list > rate-limit icmp < 0..100 >...
  • Page 333 Port Traffic Controls All-Traffic Rate-Limiting for the 5300xl, 3400cl and 6400cl Switches For example, if you wanted to view the rate-limiting configuration on the first six ports in the module in slot “B”: Ports B2-B5 are configured with an ICMP rate limit of 1%.
  • Page 334 Port Traffic Controls All-Traffic Rate-Limiting for the 5300xl, 3400cl and 6400cl Switches The show config status command compares the content of the startup-config and running-config files and prints a report. Ports B2-B5 are configured with an ICMP rate limit of 1%.

  • Page 335: Operating Notes For Icmp Rate-Limiting

    Port Traffic Controls All-Traffic Rate-Limiting for the 5300xl, 3400cl and 6400cl Switches The switch does not send more traps or Event Log messages for excess ICMP traffic on the affected port until the system operator resets the port’s ICMP trap function. The reset can be done through SNMP from a network manage­...
  • Page 336 Port Traffic Controls All-Traffic Rate-Limiting for the 5300xl, 3400cl and 6400cl Switches Interface Support: ICMP rate-limiting is available on all types of ports ■ and trunks on the switches covered by this guide, and at all port speeds configurable for these devices.
  • Page 337 Port Traffic Controls All-Traffic Rate-Limiting for the 5300xl, 3400cl and 6400cl Switches tion, an outbound interface can become oversubscribed by traffic received from multiple ICMP rate-limited interfaces. In this case, the actual rate for traffic on the rate-limited interfaces may be lower than configured because the total traffic load requested to the outbound inter­...
  • Page 338 Port Traffic Controls All-Traffic Rate-Limiting for the 5300xl, 3400cl and 6400cl Switches ProCurve# walkmib ifDescr ifDescr.1 = A1 ifDescr.2 = A2 ifDescr.3 = A3 Beginning and Ending of Port Number Listing for Slot A ifDescr.23 = A23 ifDescr.24 = A24 ifDescr.27 = B1...

  • Page 339: Switches

    Port Traffic Controls Guaranteed Minimum Bandwidth (GMB) on the Series 5300xl Switches Guaranteed Minimum Bandwidth (GMB) on the Series 5300xl Switches This section applies only to the Series 5300xl switches. Feature Default Menu bandwidth-min output Per-Queue: page 14-23 8%-16%-30%-45% show bandwidth output [ port-list ] page 14-21 Introduction Guaranteed Minimum Bandwidth (GMB) provides a method for ensuring that...
  • Page 340 Port Traffic Controls Guaranteed Minimum Bandwidth (GMB) on the Series 5300xl Switches Table 14-1. Per-Port Outbound Priority Queues 802.1p Priority Settings in Tagged VLAN Outbound Priority Queue for a Given Port Packets* 1 (low) 2 (low) 0 (normal) 3 (normal) 4 (medium) 5 (medium) 6 (high)

  • Page 341: Outbound Traffic

    Port Traffic Controls Guaranteed Minimum Bandwidth (GMB) on the Series 5300xl Switches N o t e For a given port, when the demand on one or more outbound queues exceeds the minimum bandwidth configured for those queues, the switch apportions unallocated bandwidth to these queues on a priority basis.
  • Page 342 Port Traffic Controls Guaranteed Minimum Bandwidth (GMB) on the Series 5300xl Switches Syntax: [ no ] int < port-list > bandwidth-min output (Continued) [ < queue1% > < queue2% > < queue3% > < queue4% >] For ports in < port-list >, specifies the minimum outbound bandwidth as a percent of the total bandwidth for each outbound queue.

  • Page 343: Configuration

    Either of the following commands configures ports A1 and A2 with the bandwidth settings shown in the preceding table: ProCurve(config)#int a1-a2 bandwidth-min output 10 20 20 50 ProCurve(eth-A1-A2)#bandwidth-min output 10 20 20 50 Displaying the Current Guaranteed Minimum Bandwidth...

  • Page 344: Gmb Operating Notes

    Port Traffic Controls Guaranteed Minimum Bandwidth (GMB) on the Series 5300xl Switches For example, to display the GMB configuration resulting from either of the above commands: User-Configured Minimum Bandwidth Settings Default Minimum Bandwidth Settings Figure 14-6. Example of Listing the Guaranteed Minimum Bandwidth Configuration For an example listing the GMB configuration in the startup-config file, refer to figure 14-2 on page 14-7.

  • Page 345: Cl And Series 6400Cl Switches

    Layer 2 packets inbound on a port. The switch allows jumbo packets of up to 9220 bytes. Standard MTU: On the 3400cl/6400cl switches, an IP packet of 1522 bytes in size. (This size includes 4 bytes for the VLAN tag.)

  • Page 346: Operating Rules

    Switch Meshing: If you enable jumbo traffic on a VLAN in a 3400cl or ■ 6400cl switch, then all meshed ports on the switch will be enabled to support jumbo traffic. (On a given meshed switch, every meshed port operating at 1 Gbps or higher becomes a member of every VLAN config­...

  • Page 347: Configuring Jumbo Packet Operation

    Port Traffic Controls Jumbo Packets on the Series 3400cl and Series 6400cl Switches Configuring Jumbo Packet Operation Command Page show vlans 14-30 show vlans ports < port-list > 14-31 show vlans < vid > 14-32 jumbo 14-32 Overview 1. Determine the VLAN membership of the ports or trunks through which you want the switch to accept inbound jumbo traffic.

  • Page 348: Viewing The Current Jumbo Configuration

    Port Traffic Controls Jumbo Packets on the Series 3400cl and Series 6400cl Switches Viewing the Current Jumbo Configuration Syntax: show vlans Lists the static VLANs configured on the switch and includes a Jumbo column to indicate which VLANs are configured to support inbound jumbo traffic.
  • Page 349 Port Traffic Controls Jumbo Packets on the Series 3400cl and Series 6400cl Switches Indicates which static VLANs are configured to enable jumbo packets. Figure 14-8. Example of Listing the VLAN Memberships for a Range of Ports Syntax: show vlans < vid >...

  • Page 350: Enabling Or Disabling Jumbo Traffic On A Vlan

    CLI and sends a similar message to the Event Log. ■ The default MTU on the 3400cl/6400cl switches is 1522 bytes (including 4 bytes for the VLAN tag). The jumbo MTU is 9220 bytes (including 4 bytes for the VLAN tag).
  • Page 351 Port Traffic Controls Jumbo Packets on the Series 3400cl and Series 6400cl Switches When a port is not a member of any jumbo-enabled VLAN, it drops all ■ jumbo traffic. If the port is receiving “excessive” inbound jumbo traffic, the port generates an Event Log message to notify you of this condition.
  • Page 352 2400M/2424M/4000M/8000M switches along with Series 3400cl and Series 6400cl switches configured to support jumbo traffic, only the 3400cl/ 6400cl switches will receive jumbo packets. The other switch models in the mesh will drop such packets. For more information on switch mesh­...

  • Page 353: Troubleshooting

    < port-list > A non-jumbo port is generating “Excessive undersize/giant packets” messages in the Event Log. The 3400cl/6400cl switches can transmit out­ bound jumbo traffic on any port, regardless of whether the port belongs to a jumbo VLAN. In this case, another port in the same VLAN on the switch may...
  • Page 354 Port Traffic Controls Jumbo Packets on the Series 3400cl and Series 6400cl Switches — This page is intentionally unused. — 14-36...

  • Page 355: Contents

    Configuring for Network Management Applications Contents Using SNMP Tools To Manage the Switch ..... . 15-3 Overview ..........15-3 SNMP Management Features .
  • Page 356 LLDP Operating Rules ........15-31 LLDP Data Management on the Series 3400cl and 6400cl Switches 15-32 LLDP Neighbor Data .

  • Page 357: Using Snmp Tools To Manage The Switch

    Overview You can manage the switch via SNMP from a network management station running an application such as ProCurve Manager (PCM) or ProCurve Manager Plus (PCM+). For more on PCM and PCM+, visit the ProCurve Networking web site at: http://www.procurve.com Click on products index in the sidebar, then click on the appropriate link appearing under the Network Management heading.

  • Page 358: Snmp Management Features

    HP OpenView, you can ensure that it is using the latest version of the MIB file by downloading the file to the OpenView database. To do so, go to the ProCurve Networking web site at: http://www.procurve.com Click on software updates, then MIBs.

  • Page 359: Configuring For Snmp Version 3 Access To The Switch

    C a u t i o n For ProCurve Manager (PCM) version 1.5 or earlier (or any TopTools version), deleting the “public” community disables some network management functions (such as traffic monitoring, SNMP trap generation, and threshold setting).

  • Page 360: Snmp Version 3 Commands

    Configuring for Network Management Applications Using SNMP Tools To Manage the Switch SNMP Version 3 Commands SNMP version 3 (SNMPv3) adds a new command to the CLI for configuring SNMPv3 functions. To enable SMNPv3 operation on the switch you must: Enable SNMPv3 with the snmpv3 enable command.

  • Page 361: Enabling Snmpv3

    Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Enabling SNMPv3 The snmpv3 enable command starts a dialog that performs three functions: enabling the switch to receive SNMPv3 messages, configuring the initial users, and, optionally, to restrict non-version 3 messages to “read only”. Figure 15-1 shows an example of this dialog.
  • Page 362 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch 2. Assign users to Security Groups based on their security model. This is done with the snmpv3 group command. See“Assigning Users to Groups” on page 15-9. C a u t i o n Adding a user without authentication and/or privacy to a group that requires it, will cause the user to not be able to access the switch.
  • Page 363 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch [priv <priv_pass>] With privacy, the switch only supports DES (56-bit) encryption. The privacy password priv_pass must be 6-32 characters in length and must be included when using the priv parameter. (Default: None) Assigning Users to Groups.

  • Page 364: Group Access Levels

    Configuring for Network Management Applications Using SNMP Tools To Manage the Switch This parameter identifies the user to be added to the access group. This must match the user name added with the snmpv3 user command. sec-model <ver1 | ver2c | ver3> This defines which security model to use for the added user.

  • Page 365: Snmpv3 Communities

    Configuring for Network Management Applications Using SNMP Tools To Manage the Switch SNMPv3 Communities SNMP commuities are supported by the switch to allow management application that use version 2c or version 1 to access the switch. The communities are mapped to Group Access Levels that are used for version 2c or version 1 support.
  • Page 366 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Figure 15-4 shows the assigning of Operator community on MgrStation1 to the CommunityOperatorReadWrite group. Any other Operator only has an access level of CommunityOperatorReadOnly Add mapping to allow write access for Operator community on MgrStation1 Two Operator Access Levels Figure 15-4.

  • Page 367: Version 3 Communities

    Using SNMP Tools To Manage the Switch C a u t i o n For ProCurve Manager (PCM) version 1.5 or earlier (or any TopTools version), deleting the “public” community disables some network management functions (such as traffic monitoring, SNMP trap generation, and threshold setting).

  • Page 368: Cli: Viewing And Configuring Snmp Community Names

    Configuring for Network Management Applications Using SNMP Tools To Manage the Switch If you are adding a community, the fields in this screen are blank. If you are editing an existing community, Type the value for this field. the values for the currently selected Use the Space bar to select Community appear...
  • Page 369 To list the data for only one community, such as the "public" community, use the above command with the community name included. For example: ProCurve# show snmp-server public Configuring Community Names and Values. The snmp-server command enables you to add SNMP communities with either default or specific access attributes, and to delete specific communities.

  • Page 370: Snmpv3 Notification And Traps

    ProCurve(config)# snmp-server community blue-team operator restricted To eliminate a previously configured community named "gold-team": ProCurve(config) # no snmp-server community gold-team SNMPv3 Notification and Traps The switches covered by this manual support the SNMPv3 notification process. They also support version 1 or version 2c traps. For more information on version 1 or version2c traps, see “SNMPv1 and SNMPv2c Trap Features”...
  • Page 371 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch [no] snmpv3 targetaddress < name > taglist < tag > params < parms_name > < ip-addr > Add or delete an address where notification messages are sent. The < tag > value must match the tag value of a notify entry.

  • Page 372: Snmpv1 And Snmpv2C Trap Features

    Configuring for Network Management Applications Using SNMP Tools To Manage the Switch This established the security model to use for messages passed to the targetaddress. If you use ver3 then msg-processing must also be ver3. < msg-processing < ver1 | ver2c | ver3 > [noaut | auth | priv] Establishes the msg-processing algorithm for messages passed to the target address.

  • Page 373: Cli: Configuring And Displaying Trap Receivers

    Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Thresholds: The switch automatically sends all messages resulting from thresholds to the network management station(s) that set the thresholds, regardless of the trap receiver configuration. In the default configuration, there are no trap receivers configured, and the authentication trap feature is disabled.
  • Page 374 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Example of Community Name Data (See page 15-11.) Authentication Trap Setting Example of Trap Receiver Data Figure 15-9. Example of Show SNMP-Server Listing Configuring Trap Receivers. This command specifies trap receivers by community membership, management station IP address, and the type of Event Log messages to send to the trap receiver.
  • Page 375 Send critical-level log messages. Debug Reserved for HP-internal use. For example, to configure a trap receiver in a community named "red-team" with an IP address of 10.28.227.130 to receive only "critical" log messages: ProCurve(config)# snmp-server trap-receiver red-team 10.28.227.130 critical 15-21...

  • Page 376: Using The Cli To Enable Authentication Traps

    For example: ProCurve(config)# snmp-server enable traps authentication Check the Event Log in the console interface to help determine why the authentication trap was sent. (Refer to “Using the Event Log To Identify Problem Sources”...
  • Page 377 Note that you can access the Ethernet statistics, Alarm, and Event groups from the ProCurve Manager network management software. For more on ProCurve Manager, visit the ProCurve Networking web site at http://www.procurve.com Click on products index, then look for the ProCurve Manager topic under the Network Manager bar. 15-23...

  • Page 378: Lldp (Link-Layer Discovery Protocol)

    CDP as documented in this manual. For current information on your switch model, consult the Release Notes (available on the ProCurve Networking web site). If LLDP has not yet been implemented (or if you are running an older version of software), consult a previous version of the Management and Configuration Guide for device discovery details.

  • Page 379: Terminology

    LLDP-MED operation. As of October, 2005, LLDP­ MED operates on 5300xl and 4200vl switches. This feature is not currently offered on the 3400cl and 6400cl switches. An SNMP utility can progressively discover LLDP devices in a network by: 1. Reading a given device’s Neighbors table (in the Management Information...
  • Page 380 PD (Powered Device): This is an IEEE 802.3af-compliant device that receives its power through a direct connection to a 10/100Base-TX PoE RJ-45 port in a ProCurve fixed-port or chassis-based switch. Examples of PDs include Voice-over-IP (VoIP) telephones, wireless access points, and remote video cameras.

  • Page 381: General Lldp Operation

    Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) PSAP (Public Safety Answering Point): PSAPs are typically emergency telephone facilities established as a first point to receive emergency (911) calls and to dispatch emergency response services such as police, fire and emergency medical services.

  • Page 382: Configuration Options

    Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) An intervening hub or repeater forwards the LLDP packets it receives in ■ the same manner as any other multicast packets it receives. Thus, two LLDP switches joined by a hub or repeater handle LLDP traffic in the same way that they would if directly connected.
  • Page 383 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Receive only (rxonly): This setting enables a port to receive and read LLDP ■ packets from LLDP neighbors, and to store the packet data in the switch’s MIB. However, the port does not transmit outbound LLDP packets. This prevents LLDP neighbors from learning about the switch through that port.

  • Page 384: Options For Reading Lldp Information Collected By The Switch

    LLDP devices (page 15-33). Using an SNMP application that is designed to query the Neighbors ■ MIB for LLDP data to use in device discovery and topology mapping. (In the 3400cl and 6400cl switches only.) 15-30...

  • Page 385: Lldp And Lldp-Med Standards Compatibility

    The operation covered by this section is compatible with these standards: IEEE P802.1AB/D9 (Series 3400cl switches) ■ ■ IEEE P802.1AB (Series 5300xl, Series 4200vl, and Series 6400cl switches) ■ RFC 2922 (PTOPO, or Physical Topology MIB) RFC 2737 (Entity MIB) ■...

  • Page 386: Lldp Data Management On The Series 3400Cl And 6400Cl Switches

    LLDP (Link-Layer Discovery Protocol) operation on the 3400cl and 6400cl switches includes transmitting LLDP packets to neighbor devices and reading LLDP packets received from neighbor devices.) This section describes points to note regarding LLDP data received by a 3400cl or 6400cl switch from other devices. LLDP Neighbor Data With LLDP enabled on a switch port, the port can read LLDP advertisements, and stores the data from the advertisements in its neighbor database.

  • Page 387: Configuring Lldp Operation

    LLDP packets. LLDP transmit/receive are enabled in the default configuration of 3400cl and 6400cl switches. Configuring LLDP Operation In the default configuration, LLDP is enabled and in both transmit and receive mode on all active ports. The LLDP configuration includes global settings that apply to all active ports on the switch, and per-port settings that affect only the operation of the specified ports.

  • Page 388: Viewing The Current Configuration

    Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Command Page lldp config < port-list > IpAddrEnable 15-41 lldp config < port-list > basicTlvEnable 15-42 lldp config < port-list > dot3TlvEnable < macphy_config > 15-44 Viewing the Current Configuration Displaying the Global LLDP, Port Admin, and SNMP Notification Status.
  • Page 389 Transmit and Receive Modes” on page 15-41. The blank IpAddress field indicates that the default IP address will be advertised from this port. (Refer to page 15-41: “Configuring a Remote Management Address for Outbound LLDP Advertisements” Figure 15-11. Example of Per-Port Configuration Display (3400cl/6400cl Switches) 15-35...

  • Page 390: Configuring Global Lldp Packet Controls

    Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) These fields appear when medtlvenable is enabled on the switch, which is the default setting. This field appears when dot3tlvenable is enabled on the switch, which is the default setting. The blank IpAddress field indicates that the default IP address will be advertised from this port.
  • Page 391 (Default: Enabled) For example, to disable LLDP on the switch: ProCurve(config)# no lldp run Changing the Packet Transmission Interval. This interval controls how often active ports retransmit advertisements to their neighbors. Syntax lldp refresh-interval < 5 - 32768 >...
  • Page 392 2, which would result in a Time-to- Live of 30 seconds. ProCurve(config)# lldp holdtime-multiplier 2 Changing the Delay Interval Between Advertisements Generated by Value or Status Changes to the LLDP MIB. The switch uses a delay- interval setting to delay transmitting successive advertisements resulting from these LLDP MIB changes.
  • Page 393 The delay interval commences with execution of the lldp admin-status < port-list > disable command. (Default: 2 seconds; Range: 1 - 10 seconds) For example, the following command changes the reinitialization delay interval to five seconds: ProCurve(config)# setmib lldpreinitdelay.0 -i 5 15-39...

  • Page 394: Configuring Snmp Notification Support

    Applications” in the Management and Configuration Guide for your switch. For example, this command enables SNMP notification on ports 1 - 5: ProCurve(config)# lldp enable-notification 1-5 Changing the Minimum Interval for Successive Data Change Notifications for the Same Neighbor LLDP trap notification is enabled on a port, a rapid succession of changes in LLDP information received in advertisements from one or more neighbors can generate a high number of traps.

  • Page 395: Configuring Per-Port Transmit And Receive Modes

    Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) ProCurve(config)# setmib lldpnotificationinterval.0 -i 60 lldpNotificationInterval.0 = 60 Configuring Per-Port Transmit and Receive Modes These commands control advertisement traffic inbound and outbound on active ports. Syntax lldp admin-status < port-list > < txonly | rxonly | tx_rx | disable >...
  • Page 396 10.10.10.100 and you wanted port 3 to use this secondary address in LLDP advertisements, you would need to execute the following command: ProCurve(config)# lldp config 3 ipAddrEnable 10.10.10.100 Optional Data. You can configure an individual port or group of ports to exclude one or more of these data types from outbound LLDP advertisements.

  • Page 397: Configuring Support For Port Speed And Duplex Advertisements On The 5300Xl And 4200Vl Switches

    For example, if you wanted to exclude the system name TLV from the outbound LLDP advertisements for all ports on a 3400cl-24G switch, you would use this command: ProCurve(config)# no lldp config 1-24 basicTlvEnable system_name If you later decided to reinstate the system name TLV on ports 1-5, you would...

  • Page 398: Xl And 4200Vl Switches

    Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Port speed and duplex advertisements are supported on 5300xl switches and 4200vl switches to inform an LLDP endpoint and the switch port of each other’s port speed and duplex configuration and capabilities. Configuration mismatches between a switch port and an LLDP endpoint can result in excessive collisions and voice quality degradation.
  • Page 399 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) described earlier in this section, with some extensions, and also introduces new commands unique to LLDP-MED operation. The show commands described elsewhere in this section are applicable to both LLDP and LLDP­ MED operation.
  • Page 400 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) 5300xl Switches Providing Network LLDP-MED Class 1 Generic Endpoints Access to LLDP-MED Endpoints Such As IP Call Control Devices IP Network Infrastructure LLDP-MED Class 2 Media Endpoints Such As (IEEE 802 LAN) Media Gateways, Conference Bridges, and other Devices Supporting IP Media Streams LLDP-MED Class 3 End-User IP Communication...

  • Page 401: Lldp-Med Topology Change Notification

    Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) N o t e LLDP-MED is intended for use with VoIP endpoints, and is not designed to support links between network infrastructure devices, such as switch-to­ switch or switch-to-router links. LLDP-MED Endpoint Device Classes. LLDP-MED endpoint devices are, by definition, located at the network edge and communicate using the LLDP­...
  • Page 402 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Syntax: lldp top-change-notify < port-list > Topology change notification, when enabled on an LLDP port, causes the switch to send an SNMP trap if it detects LLDP­ MED endpoint connection or disconnection activity on the port, or an age-out of the LLDP-MED neighbor on the port.

  • Page 403: Lldp-Med Fast Start Control

    Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) LLDP-MED Fast Start Control Syntax: lldp fast-start-count < 1 - 10 > An LLDP-MED device connecting to a switch port may use the data contained in the MED TLVs from the switch to configure itself.
  • Page 404 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) physical location data — page 54 ■ N o t e LLDP-MED operation requires the macphy_config TLV subelement—enabled by default—that is optional for IEEE 802.1AB LLDP operation. Refer to the dot3TlvEnable macphy_config command on page 15-44. Network Policy Advertisements.
  • Page 405 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) vlan < vid > qos dscp < codepoint > N o t e s A codepoint must have an 802.1p priority before you can configure it for use in prioritizing packets by VLAN-ID. If a codepoint you want to use shows No Override in the Priority column of the DSCP policy table (display with show qos­...
  • Page 406 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Syntax: [ no ] lldp config < port-list > medTlvEnable < medTlv > ■ Enables or disables advertisement of the following TLVs on the specified ports: • device capability TLV • configured network policy TLV • configured location data TLV (Refer to “Configuring Location Data for LLDP-MED Devices”...
  • Page 407 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) This TLV enables the switch port to advertise its configured network policies (voice VLAN, Layer 2 QoS, Layer 3 QoS), and allows LLDP-MED endpoint devices to auto-configure the voice network policy advertised by the switch.

  • Page 408: Configuring Location Data For Lldp-Med Devices

    Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Power-over-Ethernet TLVs include the following power data: ■ power type: indicates whether the device is a power-sourcing entity (PSE) or a powered device (PD). Ports on the J8161A PoE xl module are PSE devices.
  • Page 409 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Syntax: [ no ] lldp config < port-list > medPortLocation < Address-Type > Configures location or emergency call data the switch advertises per port in the location_id TLV. This TLV is for use by LLDP-MED endpoints employing location-based applications.
  • Page 410 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) — Continued from Preceding Page— When an emergency call is placed from a properly configured class 3 endpoint device to an appropriate PSAP, the country code, device type, and type/value pairs configured on the switch port are included in the transmission.
  • Page 411 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) This feature is intended for use in Emergency Call Service (ECS) applications to support class 3 LLDP-MED VoIP telephones connected to a 5300xl switch in a multiline telephone system (MLTS) infrastructure. An ELIN (Emergency Location Identification Number) is a valid North American Numbering Plan (NANP) format telephone number assigned to MLTS operators in North...
  • Page 412 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Example of a Location Configuration on a 5300xl Switch Port. Suppose a system operator wanted to configure the following information as the civic address for a telephone connected to her company’s network through port A2 of a 5300xl switch at the following location: Description CA-Type...

  • Page 413: Displaying Advertisement Data

    Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Figure 15-15 shows the commands for configuring and displaying the above data. Figure 15-15. Example of a Civic Address Configuration Displaying Advertisement Data Command Page show lldp info local-device below walkmib lldpXdot3LocPortOperMauType show lldp info remote-device 15-62 walkmib lldpXdot3RemPortAutoNegAdvertisedCap...

  • Page 414: Advertisements

    Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Displaying Switch Information Available for Outbound Advertisements These commands display the current switch information that will be used to populate outbound LLDP advertisements. Syntax show lldp info local-device [ port-list ] Without the [ port-list ] option, this command displays the global switch information and the per-port information currently available for populating outbound LLDP advertisements.
  • Page 415 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) The Management Address field displays only the LLDP-configurable IP addresses on the switch. (Only manually-configured IP addresses are LLDP-configurable.) If the switch has only an IP address from a DHCP or Bootp server, then the Management Address field is empty (because there are no LLDP­...
  • Page 416 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) information on displaying the currently configured port speed and duplex on an LLDP-MED endpoint, refer to “Displaying the Current Port Speed and Duplex Configuration on a Switch Port” on page 15-61. Syntax: show interfaces brief <...
  • Page 417 • 5300xl and 4200vl Switches: Multiple devices listed for the same port indicates that such devices are connected to the switch through a hub. • 3400cl/6400cl Switches: Multiple devices listed for the same port indicate that multiple devices are connected to the switch through a hub.
  • Page 418 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Note: In software releases earlier than M_08_06x (for the 3400cl switches only), a Port Type column appears with this command instead of the PortId, PortName columns shown in this figure. Note: In software release E.10.x and greater for the 5300xl switches, and for 4200vl switches, the PortName column heading appears as PortDescr.

  • Page 419: Displaying Lldp Statistics

    Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Displaying LLDP Statistics LLDP statistics are available on both a global and a per-port levels. Rebooting the switch resets the LLDP statistics counters to zero. Disabling the transmit and/or receive capability on a port “freezes” the related port counters at their current values.
  • Page 420 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) — Continued from the preceding page. — Per-Port LLDP Counters: NumFramesRecvd: Shows the total number of valid, inbound LLDP advertisements received from any neighbor(s) on < port- list >. Where multiple neighbors are connected to a port through a hub, this value is the total number of LLDP advertisements received from all sources.

  • Page 421: Lldp Operating Notes

    Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Counters showing frames sent on a port but no frames received on that port indicates an active link with a device that either has LLDP disabled on the link or is not LLDP- aware.
  • Page 422 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) LLDP Packet Forwarding: An 802.1D-compliant switch does not forward LLDP packets, regardless of whether LLDP is globally enabled or disabled on the switch. One IP Address Advertisement Per-Port: LLDP advertises only one IP address per-port, even if multiple IP addresses are configured by lldp config <...

  • Page 423: Lldp And Cdp Data Management

    LLDP packets received from neighbor devices. CDP operation is limited to reading incoming CDP packets from neighbor devices. (ProCurve switches do not generate CDP packets.) LLDP and CDP Neighbor Data With both LLDP and (read-only) CDP enabled on a switch port, the port can read both LLDP and CDP advertisements, and stores the data from both types of advertisements in its neighbor database.
  • Page 424 Neighbors database. N o t e Because ProCurve switches do not generate CDP packets, they are not represented in the CDP data collected by any neighbor devices running CDP. A switch with CDP disabled forwards the CDP packets it receives from other devices, but does not store the CDP information from these packets in its own MIB.

  • Page 425: Cdp Operation And Commands

    Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Protocol State Packet Inbound Data Management Inbound Packet Forwarding Generation CDP Enabled Store inbound CDP data. No forwarding of inbound CDP packets. CDP Disabled No storage of CDP data from Floods inbound CDP packets neighbor devices.
  • Page 426 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Command Page [no] cdp run 15-73 [no] cdp enable < port-list > 15-74 N o t e For details on how to use an SNMP utility to retrieve information from the switch’s CDP Neighbors table maintained in the switch’s MIB (Management Information Base), refer to the documentation provided with the particular SNMP utility.
  • Page 427 Syntax: [no] cdp run Enables or disables CDP read-only operation on the switch. (Default: Enabled) For example, to disable read-only CDP on the switch: ProCurve(config)# no cdp run When CDP is disabled: ■ show cdp neighbors displays an empty CDP Neighbors table...
  • Page 428 Disabling CDP on a port causes it to drop inbound CDP packets without recording their data in the CDP Neighbors table. Syntax: [no] cdp enable < [e] port-list > For example, to disable CDP on port A1: ProCurve(config)# no cdp enable a1 15-74...
  • Page 429 File Transfers Contents Overview ........... . A-3 Downloading Switch Software .
  • Page 430 File Transfers Contents Xmodem: Copying a Configuration File from a Serially Connected PC or UNIX Workstation ....A-26 Copying Diagnostic Data to a Remote Host, PC, or UNIX Workstation A-27 Copying Command Output to a Destination Device .

  • Page 431: Downloading Switch Software

    HP periodically provides switch software updates through the ProCurve Networking web site. For more information, refer to the support and warranty booklet shipped with the switch, or visit http://www.procurve.com and click on software updates. After you acquire a new switch software version, you can...

  • Page 432: General Software Download Rules

    A software version for the switch has been stored on a TFTP server accessible to the switch. (The software file is typically available from the ProCurve Networking web site at http://www.procurve.com.) The switch is properly connected to your network and has already been ■...
  • Page 433 File Transfers Downloading Switch Software Menu: TFTP Download from a Server to Primary Flash Note that the menu interface accesses only the primary flash. 1. In the console Main Menu, select Download OS to display the screen in figure A-1. (The term “OS”, or “operating system” refers to the switch software): Figure A-1.
  • Page 434 File Transfers Downloading Switch Software A “progress” bar indicates the progress of the download. When the entire software file has been received, all activity on the switch halts and you will see Validating and writing system software to FLASH... 7. After the primary flash memory has been updated with the new software, you must reboot the switch to implement the newly downloaded software.
  • Page 435 File Transfers Downloading Switch Software Execute copy as shown below: This message means that the image you Dynamic counter continually displays the want to upload will replace the image number of bytes transferred. currently in primary flash. Figure A-3. Example of the Command to Download an OS (Switch Software) 2. When the switch finishes downloading the software file from the server, it displays this progress message: Validating and Writing System Software to FLASH …...

  • Page 436: Using Secure Copy And Sftp

    As described earlier in this chapter you can use a TFTP client on the admin­ istrator workstation to update software images. This is a plain text mechanism and it connects to a standalone TFTP server or another ProCurve switch acting as a TFTP server to obtain the software image file(s). Using SCP and SFTP allows you to maintain your switches with greater security.
  • Page 437 File Transfers Downloading Switch Software Note SFTP over SSH version 1 (SSH v1) is not supported. A request from either the client or the switch (or both) using SSH v1 generates an error message. The actual text of the error message differs, depending on the client software in use.
  • Page 438 2. To enable secure file transfer on the switch (once you have an SSH session established between the switch and your computer), open a terminal window and type in the following command: ProCurve(config)# ip ssh filetransfer Disable TFTP and Auto-TFTP for Enhanced Security Beginning with software release E.10.02, using the ip ssh filetransfer command to enable Secure FTP (SFTP) automatically disables TFTP and auto-TFTP (if either or both are enabled).
  • Page 439 File Transfers Downloading Switch Software Enables/Disables TFTP. Note: If SFTP is enabled, this field will be set to No. You cannot use this field to enable TFTP if SFTP is enabled. Attempting to do so produces an Inconsistent value message in the banner below the Actions line. Figure A-5.
  • Page 440 As a matter of policy, administrators should not enable the SSHv1-only or the SSHv1-or-v2 advertisement modes. SSHv1 is supported on only some legacy switches (such as the ProCurve Series 2500 switches). To confirm that SSH is enabled type in the command ProCurve(config)# show ip ssh 3. Once you have confirmed that you have enabled an SSH session (with the...
  • Page 441 File Transfers Downloading Switch Software Authentication Switch memory allows up to ten public keys. This means the authentication and encryption keys you use for your third-party client SCP/SFTP software can differ from the keys you use for the SSH session, even though both SCP and SFTP use a secure SSH tunnel.
  • Page 442 File Transfers Downloading Switch Software All files have read-write permission. Several SFTP commands, such as ■ create or remove, are not allowed and return an error message. The switch displays the following files: +---cfg running-config startup-config +---log crash-data (5304xl Only) crash-data-a “...
  • Page 443 File Transfers Downloading Switch Software Using Xmodem to Download Switch Software From a PC or UNIX Workstation This procedure assumes that: The switch is connected via the Console RS-232 port to a PC operating as ■ a terminal. (Refer to the Installation and Getting Started Guide you received with the switch for information on connecting a PC as a terminal and running the switch console interface.) ■...
  • Page 444 File Transfers Downloading Switch Software Continue reboot of system? Press the space bar once to change No to Yes, then press [Enter] to begin the reboot. 7. To confirm that the software downloaded correctly: From the Main Menu, select 1. Status and Counters 1.
  • Page 445 (For example, all of the Series 5300xl switches use software with the “E” identifier, such as E.08.40.swi, all of the Series 3400cl and Series 6400cl switches use software with the “M” identifier, such as M.08.01, and all of the Series 4200vl switches use the “L”...
  • Page 446 “E” identifier, such as E.08.40.swi, all of the Series 3400cl and Series 6400cl switches use software with the “M” identifier, such as M.08.01 and all of the Series 4200vl switches use the “L” identifier, such as L.10.xx.) The options for this CLI feature include:...
  • Page 447 File Transfers Downloading Switch Software Downloading from Primary Only. Syntax: copy tftp flash < ip-addr > flash [ primary | secondary ] This command (executed in the destination switch) downloads the software flash in the source switch’s primary flash to either the primary or secondary flash in the destination switch.

  • Page 448: Troubleshooting Tftp Downloads

    Using PCM+ to Update Switch Software ProCurve Manager Plus includes a software update utility for updating on ProCurve switch products such as the 5300xl and 4200vl. (PCM+ version 1.6 and greater will offer this feature for the 3400cl switches and 6400 switches beginning in December, 2004.
  • Page 449 To find more information on the cause of a download failure, examine the messages in the switch’s Event Log by executing this CLI command: ProCurve# show log tftp (For more on the Event Log, see “Using the Event Log To Identify Problem Sources”...
  • Page 450 Options” on page 6-12 for more on flash image use.) For example, to download a configuration file named sw5300 in the configs directory on drive “d” in a remote host having an IP address of 10.28.227.105: ProCurve# copy tftp startup-config 10.28.227.105 d:\configs\sw2512 A-22...
  • Page 451 File Transfers Transferring Switch Configurations and ACL Command Files TFTP: Copying a Configuration File to a Remote Host Syntax: copy < startup-config | running-config > tftp < ip-addr > < remote-file > [ pc | unix ] copy config < filename > tftp < ip-addr > < remote-file > [ pc | unix ] All Switches: This command copies the switch’s startup configuration (startup-config file) or running configuration (running-config file) to a TFTP server.
  • Page 452 2. Copied the file to a TFTP server at 18.38.124.16. Using a PC workstation, you then execute the following from the CLI to upload the file to the switch and implement the ACL commands it contains: ProCurve(config)# copy tftp command-file 18.38.124.16 vlan10_in.txt pc The switch displays this message:...
  • Page 453 File Transfers Transferring Switch Configurations and ACL Command Files This message indicates that “show running” command just above it is not an ACL command and will be ignored by the switch. Manually executing show running from the CLI indicates that the file was implemented, creating ACL 155 in the switch’s running...
  • Page 454 File Transfers Transferring Switch Configurations and ACL Command Files All Switches: Uses Xmodem to copy a startup-config or running-config file from the switch to a PC or Unix workstation. 5300xl and 4200vl: A 5300xl switch running software release E.09.xx or greater, or a 4200vl switch, uses Xmodem to copy a designated configuration file from the switch to a PC or Unix workstation.
  • Page 455 File Transfers Copying Diagnostic Data to a Remote Host, PC, or UNIX Workstation For example, to copy a configuration file from a PC serially connected to the switch: 1. Execute the following command: 2. After you see the above prompt, press [Enter] 3. Execute the terminal emulator commands to begin the file transfer.

  • Page 456: Copying Command Output To A Destination Device

    File Transfers Copying Diagnostic Data to a Remote Host, PC, or UNIX Workstation Event Log: Copies the switch’s Event Log into a file on the destination ■ device. ■ Crash Data: software-specific data useful for determining the reason for a system crash. Crash Log: Processor-Specific operating data useful for determining the ■...

  • Page 457: Copying Crash Data Content To A Destination Device

    File Transfers Copying Diagnostic Data to a Remote Host, PC, or UNIX Workstation At this point, press [Enter] and start the Xmodem command sequence in your terminal emulator. Figure A-11. Example of Sending Event Log Content to a File on an Attached PC Copying Crash Data Content to a Destination Device This command uses TFTP or Xmodem to copy the Crash Data content to a PC or UNIX workstation on the network.

  • Page 458: Copying Crash Log Data Content To A Destination Device

    File Transfers Copying Diagnostic Data to a Remote Host, PC, or UNIX Workstation Copying Crash Log Data Content to a Destination Device Syntax: copy crash-log [<slot-id | master>] tftp <ip-address> <filepath and filename> copy crash-log [<slot-id | master>] xmodem where: slot-id = a - h, and retrieves the crash log or crash data from the processor on the module in the specified slot.
  • Page 459 Monitoring and Analyzing Switch Operation Contents Overview ........... . B-3 Status and Counters Data .
  • Page 460 Monitoring and Analyzing Switch Operation Contents VLAN Information ......... B-20 Web Browser Interface Status Information .
  • Page 461 Monitoring and Analyzing Switch Operation Overview Overview The switches covered by this guide have several built-in tools for monitoring, analyzing, and troubleshooting switch and network operation: ■ Status: Includes options for displaying general switch information, man­ agement address data, port status, port and trunk group statistics, MAC addresses detected on each port or VLAN, and STP, IGMP, and VLAN data (page B-4).

  • Page 462: Status And Counters Data

    Monitoring and Analyzing Switch Operation Status and Counters Data Status and Counters Data This section describes the status and counters screens available through the switch console interface and/or the web browser interface. N o t e You can access all console screens from the web browser interface via Telnet to the console.

  • Page 463: Menu Access To Status And Counters

    Monitoring and Analyzing Switch Operation Status and Counters Data Menu Access To Status and Counters Beginning at the Main Menu, display the Status and Counters menu by select­ ing: 1. Status and Counters Figure B-1. The Status and Counters Menu Each of the above menu items accesses the read-only screens described on the following pages.

  • Page 464: Switch Management Address Information

    Monitoring and Analyzing Switch Operation Status and Counters Data Figure B-2. Example of General Switch Information This screen dynamically indicates how individual switch resources are being used. See the online Help for details. CLI Access Syntax: show system-information Switch Management Address Information Menu Access From the Main Menu, select: 1 Status and Counters …...
  • Page 465 Monitoring and Analyzing Switch Operation Status and Counters Data Figure B-3. Example of Management Address Information with VLANs Configured This screen displays addresses that are important for management of the switch. If multiple VLANs are not configured, this screen displays a single IP address for the entire switch.

  • Page 466: Module Information

    Monitoring and Analyzing Switch Operation Status and Counters Data Module Information Use this feature to determine which slots have modules installed and which type(s) of modules are installed. Menu: Displaying Port Status From the Main Menu, select: 1. Status and Counters … 3.
  • Page 467 Monitoring and Analyzing Switch Operation Status and Counters Data Port Status The web browser interface and the console interface show the same port status data. Menu: Displaying Port Status From the Main Menu, select: 1. Status and Counters … 4. Port Status Figure B-5.

  • Page 468: Viewing Port And Trunk Group Statistics And Flow Control Status

    Monitoring and Analyzing Switch Operation Status and Counters Data Viewing Port and Trunk Group Statistics and Flow Control Status Feature Default Menu viewing port and trunk statistics for all page B-11 page B-12 page B-12 ports, and flow control status viewing a detailed summary for a page B-11 page B-12...

  • Page 469: Menu Access To Port And Trunk Statistics

    Monitoring and Analyzing Switch Operation Status and Counters Data Menu Access to Port and Trunk Statistics To access this screen from the Main Menu, select: 1. Status and Counters … 4. Port Counters Figure B-6. Example of Port Counters on the Menu Interface To view details about the traffic on a particular port, use the [v] key to highlight that port number, then select Show Details.
  • Page 470 Monitoring and Analyzing Switch Operation Status and Counters Data CLI Access To Port and Trunk Group Statistics To Display the Port Counter Summary Report. Syntax: show interfaces This command provides an overview of port activity for all ports on the switch. To Display a Detailed Traffic Summary for Specific Ports.
  • Page 471 Monitoring and Analyzing Switch Operation Status and Counters Data Viewing the Switch’s MAC Address Tables Feature Default Menu viewing MAC addresses on all page B-13 page B-16 — ports on a specific VLAN viewing MAC addresses on a page B-15 page B-16 —...
  • Page 472 Monitoring and Analyzing Switch Operation Status and Counters Data Figure B-8. Example of the Address Table To page through the listing, use Next page and Prev page. Finding the Port Connection for a Specific Device on a VLAN. This feature uses a device’s MAC address that you enter to identify the port used by that device.
  • Page 473 Monitoring and Analyzing Switch Operation Status and Counters Data Port-Level MAC Address Viewing and Searching. This feature displays and searches for MAC addresses on the specified port instead of for all ports on the switch. 1. From the Main Menu, select: 1.
  • Page 474 To List All Learned MAC Addresses on a VLAN, with Their Port Numbers. This command lists the MAC addresses associated with the ports for a given VLAN. For example: ProCurve> show mac-address vlan 100 N o t e The switches covered by this guide operate with a multiple forwarding data­...
  • Page 475 Monitoring and Analyzing Switch Operation Status and Counters Data Spanning Tree Protocol (STP) Information Menu Access to STP Data From the Main Menu, select: 1. Status and Counters … 8. Spanning Tree Information STP must be enabled on the switch to display the following data: Figure B-11.

  • Page 476: Cli Access To Stp Data

    Status and Counters Data Figure B-12. Example of STP Port Information CLI Access to STP Data This option lists the STP configuration, root data, and per-port data (cost, priority, state, and designated bridge). Syntax: show spanning-tree ProCurve> show spanning-tree B-18...
  • Page 477 Monitoring and Analyzing Switch Operation Status and Counters Data Internet Group Management Protocol (IGMP) Status The switch uses the CLI to display the following IGMP status on a per-VLAN basis: Show Command Output show ip igmp Global command listing IGMP status for all VLANs configured in the switch: •...

  • Page 478: Vlan Information

    Monitoring and Analyzing Switch Operation Status and Counters Data VLAN Information The switch uses the CLI to display the following VLAN status: Show Command Output show vlan Lists: • Maximum number of VLANs to support • Existing VLANs • Status (static or dynamic) •...
  • Page 479 Monitoring and Analyzing Switch Operation Status and Counters Data Listing the VLAN ID (VID) and Status for Specific Ports. Because ports A1 and A2 are not members of VLAN­ 44, it does not appear in this listing. Figure B-15. Example of VLAN Listing for Specific Ports Listing Individual VLAN Status.

  • Page 480: Web Browser Interface Status Information

    Monitoring and Analyzing Switch Operation Status and Counters Data Web Browser Interface Status Information The “home” screen for the web browser interface is the Status Overview screen, as shown below. As the title implies, it provides an overview of the status of the switch, including summary graphs indicating the network utili­...

  • Page 481: Interface Monitoring Features

    Monitoring and Analyzing Switch Operation Interface Monitoring Features Interface Monitoring Features Port Monitoring Features Feature Default Menu display monitoring disabled page B-24 page B-26 page B-29 configuration configure the monitor port(s) ports: none page B-24 page B-27 page B-29 selecting or removing ports none selected page B-24 page B-28 page B-29 You can designate monitoring of inbound and outbound traffic on: Ports and static trunks: Allows monitoring of individual ports, groups...
  • Page 482 Monitoring and Analyzing Switch Operation Interface Monitoring Features Menu: Configuring Port and Static Trunk Monitoring This procedure describes configuring the switch for monitoring when moni­ toring is disabled. (If monitoring has already been enabled, the screens will appear differently than shown in this procedure.) 1. From the Console Main Menu, Select: 2.
  • Page 483 Monitoring and Analyzing Switch Operation Interface Monitoring Features Move the cursor to the Monitoring Port parameter. Inbound Port and Trunk Monitoring (Only) on the Switch 4108 Figure B-19. How To Select a Monitoring Port 5. Use the Space bar to select the port to use for monitoring. 6. Highlight the Monitor field and use the Space bar to select the interfaces to monitor: Ports: Use for monitoring ports, static trunks, or the mesh.
  • Page 484 Monitoring and Analyzing Switch Operation Interface Monitoring Features ii. Use the Space bar to select the VLAN you want to monitor. iii. Go to step 10. 8. Use the down arrow key to move the cursor to the Action column for the individual ports and position the cursor at a port you want to monitor.
  • Page 485 Removing the monitor port disables port monitoring and resets the monitoring parameters to their factory-default settings. For example, to assign port A6 as the monitoring port: ProCurve(config)# mirror-port a6 To turn off monitoring: ProCurve(config)# no mirror-port B-27...
  • Page 486 Monitoring and Analyzing Switch Operation Interface Monitoring Features Selecting or Removing Monitoring Source Interfaces. After you con­ figure a monitor port you can use either the global configuration level or the interface context level to select ports, static trunks, meshed ports, or (for the 5300xl switches or 4200vl switches) VLANs as monitoring sources.
  • Page 487 Monitoring and Analyzing Switch Operation Interface Monitoring Features To monitor a VLAN: Configure monitoring of VLAN 20. Display current monitoring configuration: – Monitor port – Interface Being Monitored Figure B-22. Example of Configuring VLAN Monitoring These two commands show how to disable monitoring at the interface context level for a single port or all ports in an...
  • Page 488 Monitoring and Analyzing Switch Operation Interface Monitoring Features — This page is intentionally unused. — B-30...
  • Page 489 Troubleshooting Contents Overview ........... . C-3 Troubleshooting Approaches .
  • Page 490 Troubleshooting Contents Debug Types ......... . C-35 Debug Destinations .
  • Page 491 N o t e HP periodically places switch software updates on the ProCurve Networking web site. HP recommends that you check this web site for software updates that may have fixed a problem you are experiencing.

  • Page 492: Troubleshooting Approaches

    Troubleshooting Approaches Troubleshooting Approaches Use these approaches to diagnose switch problems: ■ Check the ProCurve Networking web site for software updates that may have solved your problem: http://www.procurve.com ■ Check the switch LEDs for indications of proper switch operation: •...

  • Page 493: Browser Or Telnet Access Problems

    Troubleshooting Browser or Telnet Access Problems Browser or Telnet Access Problems Cannot access the web browser interface: Access may be disabled by the Web Agent Enabled parameter in the switch ■ console. Check the setting on this parameter by selecting: 2.
  • Page 494 Troubleshooting Browser or Telnet Access Problems Cannot Telnet into the switch console from a station on the network: ■ Off subnet management stations can lose Telnet access if you enable routing without first configuring a static (default) route. That is, the switch uses the IP default gateway only while operating as a Layer 2 device.

  • Page 495: Unusual Network Activity

    Unusual network activity is usually indicated by the LEDs on the front of the switch or measured with the switch console interface or with a network management tool such as ProCurve Manager. Refer to the Installation Guide you received with the switch for information on using LEDs to identify unusual network activity.

  • Page 496: Q Prioritization Problems

    Troubleshooting Unusual Network Activity This can also happen, for example, if the server is first configured to issue IP addresses with an unlimited duration, then is subsequently configured to issue IP addresses that will expire after a limited duration. One solution is to configure “reservations”...
  • Page 497 Troubleshooting Unusual Network Activity Indicates that routing is enabled; a require­ ment for ACL operation. (There is an exception. See the Note, below.) Figure C-1. Indication that Routing Is Enabled Note If an ACL assigned to a VLAN includes an ACE referencing an IP address on the switch itself as a packet source or destination, the ACE screens traffic to or from this switch address regardless of whether IP routing is enabled.
  • Page 498 Troubleshooting Unusual Network Activity Error (Invalid input) when entering an IP address. When using the “host” option in the command syntax, ensure that you are not including a mask in either dotted decimal or CIDR format. Using the “host” option implies a specific host device and therefore does not permit any mask entry.
  • Page 499 10 Net’s 10.0.8.1 router gateway needed by the 20 Net. (Subnet mask is 255.255.255.0.) Figure C-3. Example of ACE Blocking an Entire Subnet 5300xl, 3400cl, or 6400cl Switch Switch 2 10 Net -- VLAN 1 10 Net -- VLAN 1 IP: 10.08.15 IP: 10.0.8.16...
  • Page 500 Troubleshooting Unusual Network Activity To avoid inadvertently blocking the remote gateway for authorized traffic from another network (such as the 20 Net in this example): 1. Configure an ACE that specifically permits authorized traffic from the remote network. 2. Configure narrowly defined ACEs to block unwanted IP traffic that would otherwise use the gateway.
  • Page 501 GVRP. Thus, if there are any of these switches in the mesh, GVRP must be disabled for any switch in the mesh.) The Switch Mesh Does Not Allow A ProCurve Switch 1600M/2400M/ 2424M/4000M/8000M Port To Join the Mesh . One of the switches in the mesh domain has detected a duplicate MAC address on multiple switches.
  • Page 502 4000M/8000M switches do not recognize multiple instances of a particular MAC address on different VLANs.) Refer to “The Switch Mesh Does Not Allow A ProCurve Switch 1600M/2400M/2424M/4000M/8000M Port To Join the Mesh” on page C-13. Port-Based Access Control (802.1x)-Related Problems Note To list the 802.1x port-access Event Log messages stored on the switch, use...
  • Page 503 Troubleshooting Unusual Network Activity authentication request. If the RADIUS server configuration for authenti­ cating the client includes a VLAN assignment, ensure that the VLAN exists as a static VLAN on the switch. Refer to “How 802.1x Authentication Affects VLAN Operation” in the Access Security Guide for your switch. During RADIUS-authenticated client sessions, access to a VLAN on the port used for the client sessions is lost.
  • Page 504 Troubleshooting Unusual Network Activity Port A9 shows an “Open” status even though Access Control is set to Unauthorized (Force Auth). This is because the port-access authenticator has not yet been activated. Figure C-6. Authenticator Ports Remain “Open” Until Activated RADIUS server fails to respond to a request for service, even though the server’s IP address is correctly configured in the switch.
  • Page 505 Troubleshooting Unusual Network Activity Also, ensure that the switch port used to access the RADIUS server is not blocked by an 802.1x configuration on that port. For example, show port- access authenticator < port-list > gives you the status for the specified ports. Also, ensure that other factors, such as port security or any 802.1x configura­...
  • Page 506 Troubleshooting Unusual Network Activity Ensure that the radius-server timeout period is long enough for network ■ conditions. ■ Verify that the switch is using the same UDP port number as the server. RADIUS server fails to respond to a request for service, even though the server’s IP address is correctly configured in the switch.
  • Page 507 Troubleshooting Unusual Network Activity Broadcast Storms Appearing in the Network. This can occur when there are physical loops (redundant links) in the topology.Where this exists, you should enable STP on all bridging devices in the topology in order for the loop to be detected.
  • Page 508 Troubleshooting Unusual Network Activity Executing IP SSH does not enable SSH on the switch. The switch does not have a host key. Verify by executing show ip host-public-key. If you see the message ssh cannot be enabled until a host key is configured (use 'crypto' command).
  • Page 509 Troubleshooting Unusual Network Activity TACACS-Related Problems Event Log. When troubleshooting TACACS+ operation, check the switch’s Event Log for indications of problem areas. All Users Are Locked Out of Access to the Switch. If the switch is func­ tioning properly, but no username/password pairs result in console or Telnet access to the switch, the problem may be due to how the TACACS+ server and/or the switch are configured.
  • Page 510 Troubleshooting Unusual Network Activity The encryption key configured in the server does not match the ■ encryption key configured in the switch (by using the tacacs-server key command). Verify the key in the server and compare it to the key configured in the switch.
  • Page 511 Troubleshooting Unusual Network Activity TimeP, SNTP, or Gateway Problems The Switch Cannot Find the Time Server or the Configured Gateway . TimeP, SNTP, and Gateway access are through the primary VLAN, which in the default configuration is the DEFAULT_VLAN. If the primary VLAN has been moved to another VLAN, it may be disabled or does not have ports assigned to it.
  • Page 512 Troubleshooting Unusual Network Activity Link supporting VLAN_1 and VLAN_2 Switch “Y” Switch “X” Port Y- 7 Port X-3 VLAN Port Assignment VLAN Port Assignment Port VLAN_1 VLAN_2 Port VLAN_1 VLAN_2 Untagged Tagged Untagged Tagged Figure C-9. Example of Correct VLAN Port Assignments on a Link 1. If VLAN_1 (VID=1) is configured as “Untagged”...
  • Page 513 Troubleshooting Unusual Network Activity MAC Address “A”; VLAN 1 Server VLAN 1 Switch with 5300xl, 4200vl, Single 3400cl, or 6400cl MAC Address “A”; VLAN 2 Forwarding Switch Database VLAN 2 (Multiple Forwarding Database) Problem: This switch detects continual moves of MAC address “A”...

  • Page 514: Using The Event Log To Identify Problem Sources

    Troubleshooting Using the Event Log To Identify Problem Sources Using the Event Log To Identify Problem Sources The Event Log records operating events as single-line entries listed in chrono­ logical order, and serves as a tool for isolating problems. Each Event Log entry is composed of five fields: Severity Date...
  • Page 515 Troubleshooting Using the Event Log To Identify Problem Sources Table C-1. Event Log System Modules Module Event Description Module Event Description addrMgr Address table timep Time protocol chassis switch hardware udpf UDP broadcast forwarder bootp bootp addressing vlan VLAN operations connfilt Connection-Rate filtering RateLim...
  • Page 516 Troubleshooting Using the Event Log To Identify Problem Sources Menu: Entering and Navigating in the Event Log From the Main Menu, select Event Log. Range of Events in the Log Range of Log Events Displayed Log Status Line Figure C-11. Example of an Event Log Display The log status line at the bottom of the display identifies where in the sequence of event messages the display is currently positioned.
  • Page 517 Troubleshooting Using the Event Log To Identify Problem Sources CLI: Listing Events Syntax: show logging [-a] [<search-text>] Uses the CLI to list: ■ Events recorded since the last boot of the switch All events recorded ■ ■ Event entries containing a specific keyword, either since the last boot or all events recorded show logging Lists recorded log messages since last reboot.

  • Page 518: Reducing Duplicate Event Log And Snmp Trap Messages

    Messages N o t e This feature is available with all software releases for the Series 3400/6400cl switches, Series 4200vl switches and with software release E.08.xx and greater on the Series 5300xl switches. Initially it applies only to Event Log messages and SNMP traps generated by the PIM software module.
  • Page 519 Troubleshooting Using the Event Log To Identify Problem Sources W 10/01/04 09:00:33 PIM:No IP address configured on VID 100 (1) The counter indicates that this is the first instance of this event since the switch last rebooted. Figure C-12. Example of the First Instance of an Event Message and Counter If PIM operation caused the same event to occur six more times during the initial log throttle period, there would be no further entries in the Event Log.
  • Page 520 Troubleshooting Using the Event Log To Identify Problem Sources Example of Event Counter Operation. Suppose the switch detects the following after a reboot: ■ Three duplicate instances of the PIM “Send error” during the first log throttle period for this event Five more instances of the same Send error during the second log throttle ■...

  • Page 521: Debug And Syslog Messaging Operation

    Troubleshooting Debug and Syslog Messaging Operation Debug and Syslog Messaging Operation The switch’s Event Log records switch-level progress, status, and warning messages. The Debug/System-Logging (Syslog) feature provides a method for recording messages you can use to help in debugging network-level problems, such as routing misconfigurations and other network protocol details.

  • Page 522: Debug Command Operation

    Series 2600 switches and the Switch 6108 (software release H.07.30 or ■ greater) For the latest feature information on ProCurve switches, visit the ProCurve Networking web site and check the latest release notes for the switch products you use. ■...

  • Page 523: Debug Types

    Troubleshooting Debug and Syslog Messaging Operation N o t e Using the logging < dest-ip-addr > command to configure a Syslog server address creates an exception to the above general operation. Refer to “Syslog Operation” on page C-38. Debug Types This section describes the types of debug messages the switch can send to configured debug destinations.
  • Page 524 Troubleshooting Debug and Syslog Messaging Operation Syntax: [no] debug < debug-type > (Continued) ip [ ospf < adj | event | flood | lsa-generation | packet | retransmission | spf > ] For the configured debug destination(s): ospf < adj | event | flood | lsa-generation | packet | retransmission | spf >...

  • Page 525: Debug Destinations

    The session can be on any one terminal emula­ tion device with serial, Telnet, or SSH access to the CLI at the Manager level prompt (ProCurve#_ ). If more than one terminal device has a console session with the CLI, you can redirect the destination from the current device to another device.

  • Page 526: Syslog Operation

    Troubleshooting Debug and Syslog Messaging Operation Syslog Operation Syslog is a client-server logging tool that allows a client switch to send event notification messages to a networked device operating with Syslog server software. Messages sent to a Syslog server can be stored to a file for later debugging analysis.

  • Page 527: Viewing The Debug Configuration

    — cron/at subsystem sys10 - sys14 — Reserved for system use local10 - local17 — Reserved for system use For a listing of applicable ProCurve switches, refer to the Note on page C-34. Viewing the Debug Configuration Syntax: show debug This command displays the currently configured debug log­...
  • Page 528 3. Enable the debug types for which you want messages sent to the Syslog server(s) and/or the current session device: ProCurve# debug < acl | all | event | ip [ospf-opt]> Repeat this step if necessary to enable multiple debug types.
  • Page 529 Troubleshooting Debug and Syslog Messaging Operation Example: Suppose that there are no Syslog servers configured on the switch (the default). Configuring one Syslog server enables debug logging to that server and also enables Event Log messages to be sent to the server. Displays the default debug configuration.
  • Page 530 Troubleshooting Debug and Syslog Messaging Operation Example. Suppose that you want to: ■ Configure Syslog logging of ACL and IP-OSPF packet messages on a Syslog server at 18.38.64.164 (with user as the default logging facility). Also display these messages in the CLI session of your terminal device’s ■...

  • Page 531: Operating Notes For Debug And Syslog

    Troubleshooting Debug and Syslog Messaging Operation Operating Notes for Debug and Syslog Rebooting the Switch or pressing the Reset button resets the ■ Debug Configuration. Debug Option Effect of a Reboot or Reset logging (destination) If any Syslog server IP addresses are in the startup-config file, they are saved across a reboot and the logging destination option remains enabled.

  • Page 532: Diagnostic Tools

    Troubleshooting Diagnostic Tools Diagnostic Tools Diagnostic Features Feature Default Menu Port Auto negotiation Ping Test — page C-47 page C-46 Link Test — page C-47 page C-46 Display Config File — page C-49 page C-49 Admin. and Troubleshooting — page C-51 —...
  • Page 533 Troubleshooting Diagnostic Tools N o t e To respond to a Ping test or a Link test, the device you are trying to reach must be IEEE 802.3-compliant. Ping Test. This is a test of the path between the switch and another device on the same or another IP network that can respond to IP packets (ICMP Echo Requests).
  • Page 534 Troubleshooting Diagnostic Tools Web: Executing Ping or Link Tests 1. Click here. 2. Click here. 3. Select Ping Test (the default) or Link Test 4. For a Ping test, enter the IP address of the target device. For a Link test, enter the MAC address of the target device.
  • Page 535 Troubleshooting Diagnostic Tools Number of Packets to Send is the number of times you want the switch to attempt to test a connection. Timeout in Seconds is the number of seconds to allow per attempt to test a connection before determining that the current attempt has failed. To halt a Link or Ping test before it concludes, click on the Stop button.
  • Page 536 Troubleshooting Diagnostic Tools Link Tests. You can issue single or multiple link tests with varying repeti­ tions and timeout periods. The defaults are: ■ Repetitions: 1 (1 - 999) Timeout: 5 seconds (1 - 256 seconds) ■ Syntax: link < mac-address > [repetitions < 1 - 999 >] [timeout < 1 - 256 >] [vlan <...

  • Page 537: Displaying The Configuration File

    Troubleshooting Diagnostic Tools Displaying the Configuration File The complete switch configuration is contained in a file that you can browse from either the web browser interface or the CLI. It may be useful in some troubleshooting scenarios to view the switch configuration. CLI: Viewing the Configuration File Using the CLI, you can display either the running configuration or the startup configuration.
  • Page 538 Troubleshooting Diagnostic Tools IP routes ■ ■ Status and counters — VLAN information ■ GVRP support Load balancing (trunk and LACP) ■ Syntax: show tech Executing show tech outputs a data listing to your terminal emulator. However, using your terminal emulator’s text capture features, you can also save show data to a text file for viewing, printing, or sending to an associate.

  • Page 539: Cli Administrative And Troubleshooting Commands

    Diagnostic Tools 4. Execute show tech ProCurve# show tech a. Each time the resulting listing halts and displays -- MORE --, press the Space bar to resume the listing. b. When the CLI prompt appears, the show tech listing is complete. At...

  • Page 540: Traceroute Command

    Troubleshooting Diagnostic Tools setup Displays the Switch Setup screen from the menu interface. repeat Repeatedly executes the previous command until a key is pressed. kill Terminates all other active sessions. Traceroute Command The traceroute command enables you to trace the route from the switch to a host address.
  • Page 541 Troubleshooting Diagnostic Tools [maxttl < 1-255 >] For the current instance of traceroute, changes the maximum number of hops allowed for each probe packet sent along the route. If the destination address is further from the switch than maxttl allows, then traceroute lists the IP addresses for all hops it detects up to the maxttl limit.
  • Page 542 Troubleshooting Diagnostic Tools Traceroute does not reach destination IP address because of low maxttl setting. The asterisk indicates there was a timeout on the second probe to the third hop. Figure C-24. Example of Incomplete Traceroute Due to Low Maxttl Setting If A Network Condition Prevents Traceroute from Reaching the Destination.

  • Page 543: Restoring The Factory-Default Configuration

    Troubleshooting Restoring the Factory-Default Configuration Restoring the Factory-Default Configuration As part of your troubleshooting process, it may become necessary to return the switch configuration to the factory default settings. This process momen­ tarily interrupts the switch operation, clears any passwords, clears the console Event Log, resets the network counters to zero, performs a complete self test, and reboots the switch into its factory default configuration including deleting an IP address.

  • Page 544: Restoring A Flash Image

    Troubleshooting Restoring a Flash Image When the Self Test LED begins to flash, release the Clear button. The switch will then complete its self test and begin operating with the configuration restored to the factory default settings. Restoring a Flash Image The switch can lose its operating system if either the primary or secondary flash image location is empty or contains a corrupted OS file and an operator uses the erase flash command to erase a good OS image file from the opposite...
  • Page 545 Troubleshooting Restoring a Flash Image 4. Since the OS file is large, you can increase the speed of the download by changing the switch console and terminal emulator baud rates to a high speed. For example: a. Change the switch baud rate to 115,200 Bps. =>...
  • Page 546 Troubleshooting Restoring a Flash Image Figure C-26. Example of Xmodem Download in Progress 8. When the download completes, the switch reboots from primary flash using the OS image you downloaded in the preceding steps, plus the most recent startup-config file. C-58...

  • Page 547: Mac Address Management

    MAC Address Management Contents Overview ........... . D-2 Determining MAC Addresses .

  • Page 548: Overview

    MAC Address Management Overview Overview The switch assigns MAC addresses in these areas: ■ For management functions, one Base MAC address is assigned to the default VLAN (VID = 1). (All VLANs on the switches covered in this guide use the same MAC address.) For internal switch operations: One MAC address per port (See “CLI: ■...

  • Page 549: Determining Mac Addresses

    MAC Address Management Determining MAC Addresses Determining MAC Addresses MAC Address Viewing Methods Feature Default Menu view switch’s base (default vlan) MAC address — and the addressing for any added VLANs view port MAC addresses (hexadecimal format) n/a — — ■...

  • Page 550: Menu: Viewing The Switch's Mac Addresses

    MAC Address Management Determining MAC Addresses Menu: Viewing the Switch’s MAC Addresses The Management Address Information screen lists the MAC addresses for: ■ Base switch (default VLAN; VID = 1) Any additional VLANs configured on the switch. ■ Also, the Base MAC address appears on a label on the back of the switch. N o t e The Base MAC address is used by the first (default) VLAN in the switch.

  • Page 551: Cli: Viewing The Port And Vlan Mac Addresses

    1. If the switch is at the CLI Operator level, use the enable command to enter the Manager level of the CLI. 2. Type the following command to display the MAC address for each port on the switch: ProCurve# walkmib ifPhysAddress...
  • Page 552 MAC Address Management Determining MAC Addresses (The above command is not case-sensitive.) For example, with a 4-port module in slot A of a 5304xl switch, a 24-port module in slot B, and four nondefault VLANs configured: ifPhysAddress.1 - 4: Ports A1 - A4 in Slot A (Addresses 5 - 24 in slot A are unused, and addresses 25 and 26 are reserved.) ifPhysAddress.27 - 50:...
  • Page 553 MAC Address Management Determining MAC Addresses ifPhysAddress.1 - 24: Ports 1 - 24 (A 3400cl-48G switch includes addresses 1 - 48 for the fixed ports.) ifPhysAddress.25 - 26: Ports 25 - 26 (Addresses 25 - 26 appear only if a 10-gigabit expansion module is installed in the switch.

  • Page 554: Viewing The Mac Addresses Of Connected Devices

    MAC Address Management Viewing the MAC Addresses of Connected Devices Viewing the MAC Addresses of Connected Devices Syntax: show mac-address [ | mac-addr | Lists the MAC addresses of the devices the switch has detected, along with the number of the specific port on which each MAC address was detected.
  • Page 555 • Series 5300xl • Series 6400cl ProCurve switches provide a way to automatically adjust the system clock for Daylight Savings Time (DST) changes. To use this feature you define the month and date to begin and to end the change from standard time. In addition to the value “none”...
  • Page 556 Daylight Savings Time on ProCurve Switches Middle Europe and Portugal: • Begin DST at 2am the first Sunday on or after March 25th. • End DST at 2am the first Sunday on or after September 24th. Southern Hemisphere: • Begin DST at 2am the first Sunday on or after October 25th.
  • Page 557 Daylight Savings Time on ProCurve Switches Before configuring a “User defined” Daylight Time Rule, it is important to understand how the switch treats the entries. The switch knows which dates are Sundays, and uses an algorithm to determine on which date to change the system clock, given the configured “Beginning day”...
  • Page 558 Daylight Savings Time on ProCurve Switches — This page is intentionally unused. —...
  • Page 559 Index Symbols address table, port … B-13 address, network manager … 15-4, 15-5 => prompt … C-56 advertise location … 15-46 alert log … 5-20 Numerics alert types … 5-21 disabling … 5-25 802.1x setting the sensitivity level … 5-24 LLDP blocked …...
  • Page 560 broadcast traffic, IPX … 10-5, 10-14 restoring factory defaults … C-55 browser interface saving from menu interface … 3-10 See web browser interface. serial link … 7-3 SNMP … 15-4, 15-5, 15-11 SNMP communities … 15-13, 15-14 startup … 3-10 system …...
  • Page 561 running-config file … 6-24 show debug … C-39 running-config file operation … 6-23 structure … C-33 secondary boot path … 6-26 syntax … C-35 sftp/scp transfer … 6-38 debug logging, LLDP … 15-30 show config file content … 6-28 default gateway … 8-3 show multiple files …...
  • Page 562 excessive packets … 14-35 operation … 14-21 outbound queue priority … 14-22 starving queues … 14-23 factory default configuration restoring … 6-8, C-55 failure, switch software download … A-21 Help … 3-11, 5-13 fault detection … 5-8 Help line, about … 3-9 fault detection policy …...
  • Page 563 for SNMP management … 15-3 dynamic … 13-19 multiple in a VLAN … 8-8 enabling dynamic trunk … 13-15 removing or replacing … 8-10 full-duplex required … 13-4, 13-18 IP preserve IGMP … 13-23 DHCP server … 8-15 monitoring static trunk … B-23 overview …...
  • Page 564 … 15-40 neighbor statistics … 15-65 trap receiver, data change notice … 15-40 neighbor, maximum … 15-67 TTL … 15-28, 15-30 on 3400/6400cl switches … 15-32 txonly … 15-41 operating rules … 15-31 VLAN, untagged … 15-68 operation … 15-27 walkmib …...
  • Page 565 See port trunk. MLTS … 15-26 logging, command … C-35 monitoring logical port … 13-8 See port monitoring. loop, network … 13-3 monitoring meshed ports … B-23 lost password … 5-10 monitoring traffic … B-23 monitoring, port … B-23 Multiline Telephone system … 15-26 multinetting …...
  • Page 566 delete … 3-7, 5-10 threshold, power … 11-5, 11-11 if you lose the password … 5-10 unneeded power … 11-6 lost … 5-10 viewing status … 11-15 manager … 5-8 VLAN assignments … 11-19 operator … 5-8 wire pairs, cable … 11-4 set …...
  • Page 567 … 3-12, 6-10 See PoE. Reset button … 6-3 Power-Sourcing Equipment … 15-27 restoring factory default configuration … C-55 Procurve reset port counters … B-10 support URL … 5-13 resetting the switch prompt, => … C-56 factory default reset … C-55 PSAP …...
  • Page 568 RFC2863 … 15-31 IP … 15-3 RIP notification, LLDP debug command … C-36 SNMP notification … 15-29 RIP broadcast traffic, broadcast traffic, RIP … 10-5, public community … 15-5, 15-13 10-14 setmib … 11-12 RMON … 15-4 thresholds … 15-19 RMON groups supported …...
  • Page 569 viewing … 9-4, 9-8 download, troubleshooting … A-20 software download, using TFTP … A-4 See switch software. software image … A-3 software image version … A-6, A-16 See switch software. Syslog software version … B-6 configure server IP … C-35 sorting alert log entries …...
  • Page 570 … 15-22 management … 5-13 CLI access … 15-19 management server … 5-12, 5-13 event levels … 15-21 Procurve … 5-13, 15-4 limit … 15-19 support … 5-12, 5-13 receiver … 15-18 user name, using for browser or console SNMP …...
  • Page 571 URL, support … 5-14 VoIP … 15-44 web site, HP … 15-4 VT-100 terminal … 7-3 world wide web site, ProCurve See Procurve. write access … 15-12 write memory, effect on menu interface … 3-13 walkmib … 15-31, D-5, D-6 warranty …...
  • Page 572 —This page is unused intentionally— 14 – Index...
  • Page 574 Technical information in this document is subject to change without notice. © Copyright 2000, 2005. Hewlett-Packard Development Company, L.P. Reproduction, adaptation, or translation without prior written permission is prohibited except as allowed under the copyright laws. October 2005 Manual Part Number 5990-6050...

This manual is also suitable for:

4200vl3400cl5300xl

Table of Contents