1. Manuals
  2. Brands
  3. HP Manuals
  4. Switch
  5. ProCurve 2510
  6. Management and configuration manual

HP ProCurve 2510 Management And Configuration Manual

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
Table of Contents

Advertisement

Quick Links

2510
ProCurve Switches
XX
Q.11.
(2510-24)
XX
U.11.
(2510-48)
www.procurve.com
Management and
Configuration Guide

Advertisement

Table of Contents
loading

Related Manuals for HP ProCurve 2510

Summary of Contents for HP ProCurve 2510

  • Page 1 Management and Configuration Guide 2510 ProCurve Switches Q.11. (2510-24) U.11. (2510-48) www.procurve.com...
  • Page 3 ProCurve Series 2510 Switches January 2008 Management and Configuration Guide...
  • Page 4 January 2008 consequential damages in connection with the furnishing, performance, or use of this material. Applicable Products The only warranties for HP products and services are set forth in the express warranty statements accompanying ProCurve Switch 2510-24 (J9019B) such products and services. Nothing herein should be...
  • Page 5 Contents Product Documentation About Your Switch Manual Set ........xv Feature Index .
  • Page 6 3 Using the Menu Interface Contents ............3-1 Overview .
  • Page 7 5 Using the Web Browser Interface Contents ............5-1 Overview .
  • Page 8 Using the Menu and Web Browser Interfaces To Implement Configuration Changes ......... . 6-8 Configuration Changes Using the Menu Interface .
  • Page 9 Menu: Configuring IP Address, Gateway, and Time-To-Live (TTL) . . 8-5 CLI: Configuring IP Address, Gateway, and Time-To-Live (TTL) ..8-7 Web: Configuring IP Addressing ......8-11 How IP Addressing Affects Switch Operation .
  • Page 10 Using the CLI To Configure a Broadcast Limit ....10-11 Configuring HP Auto-MDIX ......10-12 Manual Auto-MDIX Override .
  • Page 11 11 Port Trunking Contents ............11-1 Overview .
  • Page 12 SNMP Notification and Traps ....... 12-18 Trap Features ......... 12-20 Using the CLI To Enable Authentication Traps .
  • Page 13 A File Transfers Contents ............A-1 Overview .
  • Page 14 B Monitoring and Analyzing Switch Operation Contents ............B-1 Overview .
  • Page 15 C Troubleshooting Contents ............C-1 Overview .
  • Page 16 Restoring the Factory-Default Configuration ..... . C-43 Using the CLI ......... C-43 Using the Clear/Reset Buttons .
  • Page 17 Product Documentation About Your Switch Manual Set The switch manual set includes the following: Read Me First - a printed guide shipped with your switch. Provides ■ software update information, product notes, and other information. ■ Installation and Getting Started Guide - a printed guide shipped with your switch.
  • Page 18 Product Documentation Feature Index For the manual set supporting your switch model, the following feature index indicates which manual to consult for information on a given software feature. (Note that some software features are not supported on all switch models.) Feature Management and Advanced Traffic...
  • Page 19 Product Documentation Feature Management and Advanced Traffic Access Security Configuration Management Guide Link LLDP MAC Address Management Monitoring and Analysis Multicast Filtering Network Management Applications (LLDP, SNMP) Passwords Ping Port Configuration Port Security Port Status Port Trunking (LACP) Port-Based Access Control Port-Based Priority (802.1Q) Quality of Service (QoS) RADIUS Authentication and Accounting...
  • Page 20 Product Documentation Feature Management and Advanced Traffic Access Security Configuration Management Guide TACACS+ Authentication Telnet Access TFTP Time Protocols (TimeP, SNTP) Troubleshooting VLANs Xmodem xviii...
  • Page 21 Getting Started Contents Introduction ........... 1-2 Conventions .
  • Page 22 Getting Started Introduction Introduction This Management and Configuration Guide is intended to support the following switches: ProCurve Series 2510-24 ■ ■ ProCurve Series 2510-48 This guide describes how to use the command line interface (CLI), menu interface, and web browser interface to configure, manage, and monitor switch operation.
  • Page 23 Getting Started Conventions Command Syntax Statements Syntax: aaa port-access authenticator < port-list > [ control < authorized | auto | unauthorized >] Vertical bars ( | ) separate alternative, mutually exclusive elements. ■ ■ Square brackets ( [ ] ) indicate optional elements. ■...
  • Page 24 Getting Started Sources for More Information Screen Simulations Figures containing simulated screen text and command output look similar to this: ProCurve(config)# show version Image stamp: /sw/code/build/dosx(ndx) Dec 11 2007 11:44:02 U.11.03 1340 Boot Image: Primary Figure 1-1. Example of a Figure Showing a Simulated Screen In some cases, brief command-output sequences appear outside of a numbered figure.
  • Page 25 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 Networking website at www.procurve.com. Click on Technical support, and then click on Product manuals (all). For information on specific parameters in the Menu interface, refer ■...
  • Page 26 Getting Started Need Only a Quick Start? For further information on ProCurve Networking switch technology, ■ visit the ProCurve website at: www.procurve.com Need Only a Quick Start? IP Addressing If you just want to give the switch an IP address so that it can communicate on your network, or if you are not using multiple VLANs, ProCurve recommends that you use the Switch Setup screen to quickly configure IP addressing.
  • Page 27 Selecting a Management Interface Contents Overview ............2-2 Advantages of Using the Menu Interface .
  • Page 28 Selecting a Management Interface Overview Overview Management interfaces enable you to reconfigure the switch and to monitor switch status and performance. Interface types include: ■ Menu interface—a menu-driven interface offering a subset of switch commands through the built-in VT-100/ANSI console—page 2-3 CLI—a command line interface offering the full set of switch commands ■...
  • Page 29 Selecting a Management Interface Advantages of Using the Menu Interface Advantages of Using the Menu Interface Figure 2-1. Example of the Console Interface Display Provides quick, easy management access to a menu-driven subset of ■ switch configuration and performance features: •...
  • Page 30 Selecting a Management Interface Advantages of Using the CLI Allows faster navigation, avoiding delays that occur with slower ■ display of graphical objects over a web browser interface. ■ Provides more security; configuration information and passwords are not seen on the network. Advantages of Using the CLI Operator Level ProCurve>...
  • Page 31 Selecting a Management Interface Advantages of Using the Web Browser Interface Advantages of Using the Web Browser Interface Figure 2-3. Example of the Web Browser Interface Easy access to the switch from anywhere on the network ■ ■ 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...
  • Page 32 Selecting a Management Interface Advantages of Using ProCurve Manager 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 33 Selecting a Management Interface Advantages of Using ProCurve Manager or ProCurve Manager Plus PCM and PCM+ enable greater control, uptime, and performance in your network: ■ Features and benefits of ProCurve Manager: • Network Status Summary: Upon boot-up, a network status screen displays high-level information on network devices, end nodes, events, and traffic levels.
  • Page 34 Selecting a Management Interface Advantages of Using ProCurve Manager or ProCurve Manager Plus • Device Software Updates: This feature automatically obtains new device software images from ProCurve and updates devices, allowing users to download the latest version or choose the desired version. Updates can be scheduled easily across large groups of devices, all at user-specified times.
  • Page 35 Using the Menu Interface Contents Overview ............3-2 Starting and Ending a Menu Session .
  • Page 36 Using the Menu Interface Overview Overview This chapter describes the following: Overview of the Menu Interface ■ ■ Starting and ending a Menu session (page 3-3) ■ The Main Menu (page 3-7) ■ Screen structure and navigation (page 3-8) Rebooting the switch (page 3-11) ■...
  • Page 37 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 38 Using the Menu Interface Starting and Ending a Menu Session How To Start a Menu Interface Session In its factory default configuration, the switch console starts with the CLI prompt. To use the menu interface with Manager privileges, go to the Manager level prompt and enter the command.
  • Page 39 Using the Menu Interface Starting and Ending a Menu Session Figure 3-1. The Main Menu with Manager Privileges For a description of Main Menu features, see “Main Menu Features” on page 3-7. N o t e To configure the switch to start with the menu interface instead of the CLI, go to the Manager level prompt in the CLI, enter the setup command, and in the resulting display, change the Logon Default parameter to Menu.
  • Page 40 Using the Menu Interface Starting and Ending a Menu Session Asterisk indicates a configuration change that requires a reboot to activate. Figure 3-2. An Asterisk Indicates a Configuration Change Requiring a Reboot 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 41 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 42 Using the Menu Interface Screen Structure and Navigation Command Line (CLI): Selects the Command Line Interface at the same ■ level (Manager or Operator) that you are accessing in the Menu interface. (See chapter 4, “Using the Command Line Interface (CLI)”.) ■...
  • Page 43 Using the Menu Interface Screen Structure and Navigation Screen title – identifies the location within the menu structure Parameter fields Help describing each of the items in the parameter fields Actions line Help line describing the selected action or selected Navigation instructions parameter field Figure 3-4.
  • Page 44 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: • Use the arrow keys ([<] or [>]) to highlight the action you want to from the “Actions –>”...
  • Page 45 Using the Menu Interface Rebooting the Switch 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 46 Using the Menu Interface Rebooting the Switch (Note that statistical counters can be reset to zero without rebooting the switch.) To Reboot the switch, use the Reboot Switch option in the Main Menu. (Note that the Reboot Switch option 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...
  • Page 47 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 48 Using the Menu Interface Menu Features List Menu Features List Status and Counters • General System Information • Switch Management Address Information • Port Status • Port Counters • Address Table • Port Address Table • Spanning Tree Information Switch Configuration •...
  • Page 49 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 50 Using the Menu Interface Where To Go From Here 3-16...
  • Page 51 Using the Command Line Interface (CLI) Contents Overview ............4-2 Accessing the CLI .
  • Page 52 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 53 Using the Command Line Interface (CLI) Using the CLI When you use the CLI to make a configuration change, the switch writes the change to the Running-Config file in volatile memory. This allows you to test your configuration changes before making them permanent. To make changes permanent, you must use the write memory command to save them to the Startup Config file in non-volatile memory.
  • Page 54 Using the Command Line Interface (CLI) Using the CLI C a u t i o n ProCurve strongly recommends that you configure a Manager password. If a Manager password is not configured, then the Manager level is not password- protected, and anyone having in-band or out-of-band access to the switch may be able to reach the Manager level and compromise switch and network security.
  • Page 55 Using the Command Line Interface (CLI) Using the CLI Manager Privileges Manager privileges give you three additional levels of access: Manager, Global Configuration, and Context Configuration. (See figure 4-2.) A “#” character delimits any Manager prompt. For example: ProCurve#_ Example of the Manager prompt. ■...
  • Page 56 Using the Command Line Interface (CLI) Using the CLI Changing Interfaces. If you change from the CLI to the menu interface, or the reverse, you will remain at the same privilege level. For example, entering the menu command from the Operator level of the CLI takes you to the Operator privilege level in the menu interface.
  • Page 57 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 ProCurve> enable Password:_ Manager level After you enter enable, the Password prompt appears. After you enter the Manager password, the system prompt appears with the # symbol: ProCurve#_...
  • Page 58 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 59 Using the Command Line Interface (CLI) Using the CLI Typing ? at the Manager level produces this listing: When - - MORE - - appears, use the Space bar or [Return] to list additional commands. Figure 4-4. Example of the Manager-Level Command Listing When - - MORE - - appears, there are more commands in the listing.
  • Page 60 Using the Command Line Interface (CLI) Using the CLI telnet terminal ProCurve(config)# t As mentioned above, if you type part of a command word and press , the [Tab] 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.
  • Page 61 Using the Command Line Interface (CLI) Using the CLI Listing Command Options. You can use the CLI to remind you of the options available for a command by entering command keywords followed . For example, suppose you want to see the command options for config- uring console settings: This example displays the command options for configuring the switch’s console settings.
  • Page 62 Using the Command Line Interface (CLI) Using the CLI Figure 4-6. Example of Context-Sensitive Command-List Help Displaying Help for an Individual Command. You can display Help for any command that is available at the current context level by entering enough of the command string to identify the command, along with help.
  • Page 63 Using the Command Line Interface (CLI) Using the CLI Figure 4-8. Example of Help for a Specific Instance of a Command 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# interface help...
  • Page 64 Using the Command Line Interface (CLI) Using the CLI Port or Trunk-Group Context . Includes port- or trunk-specific commands 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): Command executed at ProCurve(config)# interface e 3-6...
  • Page 65 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 3-6. The remaining commands in the listing are Manager, Operator, and context commands.
  • Page 66 Using the Command Line Interface (CLI) Using the CLI VLAN Context . Includes VLAN-specific commands that apply only to the selected VLAN, plus Manager and Operator commands. The prompt for this mode includes the VLAN ID of the selected VLAN. For example, if you had already configured a VLAN with an ID of 100 in the switch: Command executed at configura- ProCurve(config)# vlan 100...
  • Page 67 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 68 Using the Command Line Interface (CLI) CLI Control and Editing 4-18...
  • Page 69 Using the Web Browser Interface Contents Overview ............5-2 General Features .
  • Page 70 Using the Web Browser Interface Overview Overview The Web browser interface built into the switch lets you easily access the switch from a browser-based PC on your network. This lets you do the following: Optimize your network uptime by using the Alert Log and other diagnostic ■...
  • Page 71 Using the Web Browser Interface General Features General Features The switch includes these web browser interface features: Switch Configuration: • Ports • VLANs and Primary VLAN • Fault detection • Port monitoring (mirroring) • System information • Enable/Disable Multicast Filtering (IGMP) and Spanning Tree •...
  • Page 72 Using the Web Browser Interface Starting a Web Browser Interface Session with the Switch Starting a Web Browser Interface Session with the Switch You can start a web browser session in the following ways: ■ Using a standalone web browser on a network connection from a PC or UNIX workstation: •...
  • Page 73 Using the Web Browser Interface Starting a Web Browser Interface Session with the Switch 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 74 Using the Web Browser Interface Starting a Web Browser Interface Session with the Switch First-Time Alert Install Alert Figure 5-1. Example of Status Overview Screen N o t e The above screen appears somewhat different if the switch is configured as a stack Commander.
  • Page 75 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 that you should perform: ■ Review the “First Time Install” window Set Manager and Operator passwords ■...
  • Page 76 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 to maintain security and Fault Detection policy, which determines the types of messages that will be displayed in the Alert Log.
  • Page 77 Using the Web Browser Interface Tasks for Your First Web Browser Interface Session Figure 5-3. The Device Passwords Window To set the passwords: 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 78 Using the Web Browser Interface Tasks for Your First Web Browser Interface Session Using the Passwords Figure 5-4. Example of the Password Window in the Web Browser Interface The manager and operator passwords are used to control access to all switch interfaces.
  • Page 79 Using the Web Browser Interface Tasks for Your First Web Browser Interface Session Online Help for the Web Browser Interface Online Help is available for the web browser interface. You can use it by clicking on the question mark button in the upper right corner of any of the web browser interface screens.
  • Page 80 Using the Web Browser Interface Support/Mgmt URLs Feature Support/Mgmt URLs Feature The Support/Mgmt URLs window enables you to change the World Wide Web Universal Resource Locator (URL) for two functions: ■ Support URL – a support information site for your switch Management Server URL –...
  • Page 81 Using the Web Browser Interface Support/Mgmt URLs Feature Support URL This is the site that the switch accesses when you click on the Support tab on the web browser interface. The default URL is: www.procurve.com which is the web site for ProCurve’s networking products. Click on the [Support] button on that page and you can get to support informa- tion regarding your switch, including white papers, operating system (OS) updates, and more.
  • Page 82 PCM server to host the switch help files for devices that do not have HTTP access to the ProCurve Support Web site. Go to the ProCurve Support web site to get the Device Help files: www.hp.com//rnd/device_help/ Copy the Web help files to the PCM server, under: C:\\program files\hewlett-packard\pnm\server\webroot\...
  • Page 83 Using the Web Browser Interface Support/Mgmt URLs Feature Add an entry, or edit the existing entry in the Discovery portion of the global properties (globalprops.prp) in PCM to redirect the switches to the help files on the PCM server. For example: Global { TempDir=data/temp Discovery{...
  • Page 84 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-23) ■...
  • Page 85 Using the Web Browser Interface Status Reporting Features Policy Management and Configuration. ProCurve PCM can perform network-wide policy management and configuration of your switch. The Management Server URL field (page 5-13) shows the URL for the management station performing that function. For more information, refer to the documen- tation provided with the PCM software.
  • Page 86 Using the Web Browser Interface Status Reporting Features % Error Pkts Rx: All error packets received by the port. (This indicator ■ is a reddish color on many systems.) Although errors received on a port are not propagated to the rest of the network, a consistently high number of errors on a specific port may indicate a problem on the device or network segment connected to the indicated port.
  • Page 87 Using the Web Browser Interface Status Reporting Features Figure 5-11. Display of Numerical Values for the Bar 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.
  • Page 88 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 89 Using the Web Browser Interface Status Reporting Features Alert Types and Detailed Views As of August, 2006, the web browser interface generates the following alert types: • Auto Partition • High collision or drop rate • Backup Transition • Loss of Link •...
  • Page 90 Using the Web Browser Interface Status Reporting Features Figure 5-14.Example of Alert Log Detail View 5-22...
  • Page 91 Using the Web Browser Interface Status Reporting Features The Status Bar The Status Bar is displayed in the upper left corner of the web browser interface screen. Figure 5-15 shows an expanded view of the status bar. Status Indicator Most Critical Alert Description Product Name Figure 5-15.
  • Page 92 Using the Web Browser Interface Status Reporting Features Most Critical Alert Description. A brief description of the earliest, ■ unacknowledged alert with the current highest severity in the Alert Log, appearing in the right portion of the Status Bar. In instances where multiple critical alerts have the same severity level, only the earliest unacknowledged alert is deployed in the Status bar.
  • Page 93 Using the Web Browser Interface Status Reporting Features To provide the most information on network problems in the Alert Log, the recommended sensitivity level for Log Network Problems is High Sensitivity. The Fault Detection settings are: ■ High Sensitivity. This policy directs the switch to send all alerts to the Alert Log.
  • Page 94 Using the Web Browser Interface Status Reporting Features 5-26...
  • Page 95 Switch Memory and Configuration Contents Overview ............6-2 Overview of Configuration File Management .
  • Page 96 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 image options How to use the switch’s primary and secondary flash options, including ■...
  • Page 97 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 98 Switch Memory and Configuration Overview of Configuration File Management “permanent”. When you are satisfied that the change is satisfactory, you can make it permanent by executing the write memory command. For example, suppose you use the following command to disable port 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.
  • Page 99 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 100 Switch Memory and Configuration Using the CLI To Implement Configuration Changes Observe the switch’s performance with the new parameter settings to verify the effect of your changes. When you are satisfied that you have the correct parameter settings, use the write memory command to copy the changes to the startup-config file. Syntax: write memory For example, the default port mode setting is auto.
  • Page 101 Switch Memory and Configuration 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 to continue the rebooting process.
  • Page 102 Switch Memory and Configuration Using the Menu and Web Browser Interfaces To Implement Configuration Changes How To Reset the startup-config and running-config Files to the Factory-Default Configuration. This command reboots the switch, replacing the contents of the current startup-config and running-config files with the factory-default startup configuration.
  • Page 103 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-11. Using in the Menu Interface Save...
  • Page 104 Switch Memory and Configuration Using the Menu and Web Browser Interfaces To Implement Configuration Changes N o t e If you reconfigure a parameter in the CLI and then go to the menu interface without executing a write memory command, those changes are stored only in the running configuration.
  • Page 105 Switch Memory and Configuration Using the Menu and Web Browser Interfaces To Implement Configuration Changes Rebooting To Activate Configuration Changes. Configuration changes for most parameters become effective as soon as you save them. However, you must reboot the switch in order to implement a change in the Maximum VLANs to support parameter (To access these parameters, go to the Main menu and select 2.
  • Page 106 Switch Memory and Configuration Using Primary and Secondary Flash Image Options Using Primary and Secondary Flash Image Options The switch features two flash memory locations for storing switch software image files: ■ Primary Flash: The default storage for a switch software image. ■...
  • Page 107 Switch Memory and Configuration Using Primary and Secondary Flash Image Options For example, if a 2510-24 switch is using a software version of Q.11.XX stored in Primary flash, show version produces the following: ProCurve(config)# show version Image stamp: /sw/code/build/bass(ppne_swt) Nov 21 2007 11:44:02 Q.11.XX 1189 Boot Image:...
  • Page 108 Switch Memory and Configuration Using Primary and Secondary Flash Image Options ProCurve(config)# show version Image stamp: /sw/code/build/bass(ppne_swt) 1. In this example show Dec 17 2007 11:44:02 version indicates the Q.11.XX switch has version 2624 Q.11.XX in primary flash. Boot Image: Primary ProCurve(config)# boot system flash secondary Device will be rebooted, do you want to continue [y/n]?
  • Page 109 Switch Memory and Configuration Using Primary and Secondary Flash Image Options flash and you can either copy the secondary image into primary or download another image to primary from an external source. See Appendix A, “File Transfers”. 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.
  • Page 110 Switch Memory and Configuration Using Primary and Secondary Flash Image Options Syntax: copy flash flash <destination flash> where: destination flash = primary or secondary: For example, to copy the image in secondary flash to primary flash: Verify that there is a valid flash image in the secondary flash location. The following figure indicates that a software image is present in secondary flash.
  • Page 111 Switch Memory and Configuration Using Primary and Secondary Flash Image Options For example, to erase the software image in primary flash, do the following: First verify that a usable flash image exists in secondary flash. The most reliable way to ensure this is to reboot the switch from the flash image you want to retain.
  • Page 112 Switch Memory and Configuration Using Primary and Secondary Flash Image Options Table 6-2. Comparing the Boot and Reload Commands Actions Included In Included In Note Boot? Reload Save all configuration Optional, Yes, Config changes saved to the changes since the last boot with prompt automatic startup-config file...
  • Page 113 Switch Memory and Configuration Using Primary and Secondary Flash Image Options For example, to reboot the switch from secondary flash when there are no pending configuration changes in the running-config file: Figure 6-14. Example of Boot Command with Primary/Secondary Flash Option In the above example, typing either a at the second prompt initiates the reboot operation.
  • Page 114 Switch Memory and Configuration Using Primary and Secondary Flash Image Options Scheduled Reload. Additional parameters have been added to the reload command to allow for a scheduled reboot of the switch via the CLI. Syntax: [no] reload [after <[dd:]hh:]mm> | at <hh:mm[:ss]> [<mm/dd[/[yy]yy]>]] Enables a scheduled warm reboot of the switch.
  • Page 115 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 116 Switch Memory and Configuration Using Primary and Secondary Flash Image Options 6-22...
  • Page 117 Interface Access and System Information Contents Overview ............7-2 Interface Access: Console/Serial Link, Web, and Telnet .
  • Page 118 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 119 Interface Access and System Information Interface Access: Console/Serial Link, Web, and Telnet Interface Access: Console/Serial Link, Web, and 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 120 Interface Access and System Information Interface Access: Console/Serial Link, Web, and Telnet Menu: Modifying the Interface Access The menu interface enables you to modify these parameters: ■ Inactivity Time-out Inbound Telnet Enabled ■ ■ Web Agent Enabled To Access the Interface Access Parameters: From the Main Menu, Select...
  • Page 121 Interface Access and System Information Interface Access: Console/Serial Link, Web, and Telnet CLI: Modifying the Interface Access Interface Access Commands Used in This Section show console below [no] telnet-server below [no] web-management page 7-6 console page 7-6 local terminal mode page 7-8 Listing the Current Console/Serial Link Configuration.
  • Page 122 Interface Access and System Information Interface Access: Console/Serial Link, Web, and Telnet To re-enable inbound Telnet access: ProCurve(config)# telnet-server Outbound Telnet to Another Device. This feature operates indepen- dently of the telnet-server status and enables you to Telnet to another device that has an IP address.
  • Page 123 Interface Access and System Information Interface Access: Console/Serial Link, Web, and Telnet N o t e If you change the Baud Rate or Flow Control settings for the switch, you should make the corresponding changes in your console access device. Oth- erwise, you may lose connectivity between the switch and your terminal emulator due to differences between the terminal and switch settings for these two parameters.
  • Page 124 Interface Access and System Information Interface Access: Console/Serial Link, Web, and Telnet Configure individual parameters. Save the changes. Boot the switch. Figure 7-4. Example of Executing a Series of Console Commands CLI Local Terminal Mode. To enable temporary and non-disruptive changes to the terminal mode without forcing a change in the switch’s terminal mode configuration, use the console local-terminal command.
  • Page 125 Interface Access and System Information Interface Access: Console/Serial Link, Web, and Telnet none When invoked in a console session, changes the terminal mode to “raw” (scripting mode) for that console session. (Scripting mode eliminates unwanted control characters that may appear in some scripting languages.) Use this option when the configured terminal mode is either vt100 or ansi, and you want to temporarily use the scripting mode.
  • Page 126 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 127 Interface Access and System Information System Information System Information System Information Features Feature Default Menu System Name switch product page page page name 7-12 7-14 7-16 System Contact page page page 7-12 7-14 7-16 System Location page page page 7-12 7-14 7-16 MAC Age Time...
  • Page 128 Interface Access and System Information System Information Time Zone: The number of minutes your time zone location is to the West (-) or East (+) of Coordinated Universal Time (formerly GMT). The default 0 means no time zone is configured. For example, Berlin, Germany is in the +1 zone, while Vancouver, Canada is in the -8 zone.
  • Page 129 Interface Access and System Information System Information Refer to the online help provided with this screen for further information on configuration options for these features. When you have finished making changes to the above parameters, press [Enter], then press (for Save) and return to the Main Menu. CLI: Viewing and Configuring System Information System Information Commands Used in This Section show system-information...
  • Page 130 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 131 Interface Access and System Information System Information Reconfigure the Age Time for Learned MAC Addresses. This com- mand corresponds to the MAC Age Interval in the menu interface, and is expressed in seconds. Syntax: mac-age-time <10 . . 1000000> (seconds) For example, to configure the age time to seven minutes: ProCurve(config)# mac-age-time 420 Configure the Time Zone and Daylight Time Rule.
  • Page 132 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 133 Configuring IP Addressing Contents Overview ............8-2 IP Configuration .
  • Page 134 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 135 Configuring IP Addressing IP Configuration IP Configuration IP Configuration Features Feature Default Menu IP Address and Subnet Mask DHCP/Bootp page 8-5 page 8-7 page 8-11 Multiple IP Addresses on a VLAN page 8-9 Default Gateway Address none page 8-5 page 8-7 page 8-11 Packet Time-To-Live (TTL) 64 seconds...
  • Page 136 Configuring IP Addressing IP Configuration then the switch uses this gateway, even if a different gateway is received via DHCP or Bootp on the primary VLAN. (This is also true for TimeP and a non- default Time-To-Live.) See “Notes” on page 8-4 and refer to the chapter on Virtual LANs in the Advanced Traffic Management Guide.
  • Page 137 Configuring IP Addressing IP Configuration The IP addressing used in the switch should be compatible with your ■ network. That is, the IP address must be unique and the subnet mask must be appropriate for your IP network. ■ If you change the IP address through either Telnet access or the web browser interface, the connection to the switch will be lost.
  • Page 138 Configuring IP Addressing IP Configuration For descriptions of these parameters, see the online Help for this screen. Before using the DHCP/ Bootp option, refer to “DHCP/Bootp Operation” on page 8-12. Figure 8-1. Example of the IP Service Configuration Screen without Multiple VLANs Configured Press (for Edit).
  • Page 139 Configuring IP Addressing IP Configuration CLI: Configuring IP Address, Gateway, and Time-To- Live (TTL) IP Commands Used in This Section show ip page 8-7 vlan <vlan-id> ip page 8-8 address ip default-gateway page 8-11 ip ttl page 8-11 Viewing the Current IP Configuration. The following command displays the IP addressing for each VLAN configured in the switch.
  • Page 140 Configuring IP Addressing IP Configuration Figure 8-3. Example of Show IP Listing with Non-Default IP Addressing Configured Configure an IP Address and Subnet Mask. The following command includes both the IP address and the subnet mask. You must either include the ID of the VLAN for which you are configuring IP addressing or go to the context configuration level for that VLAN.
  • Page 141 Configuring IP Addressing IP Configuration Configure Multiple IP Addresses on a VLAN (Multinetting). You can configure one primary IP address per VLAN and up to seven secondary IP addresses for the same VLAN. That is, the switch enables you to assign up to eight networks to a VLAN.
  • Page 142 Configuring IP Addressing IP Configuration If you then wanted to multinet the default VLAN, you would do the following: The secondary IP addresses in a VLAN are listed immediately after the primary IP address for the VLAN. Figure 8-5. Example of Multinetting on the Default VLAN N o t e The Internet (IP) Service screen in the Menu interface (figure 8-1 on page 8-6) displays only the primary IP address for each VLAN.
  • Page 143 Configuring IP Addressing IP Configuration Configure the Optional Default Gateway. Using the Global configura- tion level, you can assign one default gateway to the switch. Syntax: ip default-gateway <ip-address> For example: ProCurve(config)# ip default-gateway 10.28.227.115 Configure Time-To-Live (TTL). Use this command at the Global config prompt to set the time that a packet outbound from the switch can exist on the network.
  • Page 144 Configuring IP Addressing IP Configuration Table 8-1. Features Available With and Without IP Addressing on the Switch Features Available Without an IP Address Additional Features Available with an IP Address and Subnet Mask • Direct-connect access to the CLI and the menu interface. •...
  • Page 145 Configuring IP Addressing IP Configuration When a DHCP or Bootp server receives the request, it replies with a previously configured IP address and subnet mask for the switch. The switch also receives an IP Gateway address if the server has been config- ured to provide one.
  • Page 146 Configuring IP Addressing IP Configuration operation, Bootp configurations are always the same for a specific receiving device. That is, the Bootp server replies to a request with a configuration previously stored in the server and designated for the requesting device. Bootp Database Record Entries.
  • Page 147 Configuring IP Addressing IP Configuration N o t e The above Bootp table entry is a sample that will work for the switch when the appropriate addresses and file names are used. Network Preparations for Configuring DHCP/Bootp In its default configuration, the switch is configured for DHCP/Bootp opera- tion.
  • Page 148 Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads IP Preserve enables you to copy a configuration file to multiple switches that use the same operating-system software while retaining the individual IP address and subnet mask on VLAN 1 in each switch, and the Gateway IP address assigned to the switch.
  • Page 149 Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads ; J9019B Configuration Editor; Created on release #Q.11.XX hostname "ProCurve Switch" time daylight-time-rule None Entering "ip preserve" in the last line of a configuration password manager file implements IP Preserve when the file is Password operator downloaded to the switch and the switch reboots.
  • Page 150 Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads ; J9019B Configuration Editor; Created on release #Q.11.XX hostname "ProCurve Switch" time daylight-time-rule None interface 11 no lacp interface 12 no lacp exit trunk 11-12 Trk1 Trunk Using figure 8-7, above, switches 1 - 3 ignore these ip default-gateway 10.22.32.1 entries because the file implements IP Preserve and...
  • Page 151 Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads To summarize the IP Preserve effect on IP addressing: ■ If the switch received its most recent VLAN 1 IP addressing from a DHCP/ Bootp server, it ignores the IP Preserve command when it downloads the configuration file, and implements whatever IP addressing instructions are in the configuration file.
  • Page 152 Configuring IP Addressing IP Preserve: Retaining VLAN-1 IP Addressing Across Configuration File Downloads 8-20...
  • Page 153 Time Protocols Contents Overview ............9-2 TimeP Time Synchronization .
  • Page 154 Time Protocols Overview Overview This chapter describes: ■ SNTP Time Protocol Operation Timep Time Protocol Operation ■ Using time synchronization ensures a uniform time among inter operating 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 155 Time Protocols Overview: Selecting a Time Synchronization Protocol or Turning Off Time Protocol Operation N o t e To use Broadcast mode, the switch and the SNTP server must be in the same subnet. Unicast Mode: The switch requests a time update from the config- ■...
  • Page 156 Time Protocols SNTP: Viewing, Selecting, and Configuring Disabling Time Synchronization You can use either of the following methods to disable time synchronization without changing the Timep or SNTP configuration: In the System Information screen of the Menu interface, set the Time ■...
  • Page 157 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 158 Time Protocols SNTP: Viewing, Selecting, and Configuring Time Protocol Selection Parameter – TIMEP – SNTP – None Figure 9-1. The System Information Screen (Default Values) Press (for ). The cursor moves to the System Name field. Edit Use [v] to move the cursor to the Time Sync Method field. Use the Space bar to select SNTP, then press [v] once to display and move to the SNTP Mode field.
  • Page 159 Time Protocols SNTP: Viewing, Selecting, and Configuring 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. If you will be using backup SNTP servers (requires use of the CLI), then see “SNTP Unicast Time Polling with Multiple SNTP Servers”...
  • Page 160 Time Protocols SNTP: Viewing, Selecting, and Configuring CLI: Viewing and Configuring SNTP CLI Commands Described in this Section show sntp page 9-8 [no] timesync pages 9-9 and ff., 9-12 sntp broadcast page 9-9 sntp unicast page 9-10 sntp server pages 9-10 and ff. Protocol Version page 9-12 poll-interval...
  • Page 161 Time Protocols SNTP: Viewing, Selecting, and Configuring Even though, in this example, TimeP is the current time synchronous method, the switch maintains the SNTP configuration. Figure 9-3. Example of SNTP Configuration When SNTP Is Not the Selected Time Synchronization Method Configuring (Enabling or Disabling) the SNTP Mode Enabling the SNTP mode means to configure it for either broadcast or unicast mode.
  • Page 162 Time Protocols SNTP: Viewing, Selecting, and Configuring 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. Select SNTP as the time synchronization mode. 3.
  • Page 163 Time Protocols SNTP: Viewing, Selecting, and Configuring Syntax: timesync sntp Selects SNTP as the time synchronization method. sntp unicast Configures the SNTP mode for Unicast operation. sntp server <ip-addr> [version] Specifies the SNTP server. The default server version is no sntp server < ip-addr > Deletes the specified SNTP server.
  • Page 164 Time Protocols SNTP: Viewing, Selecting, and Configuring If the SNTP server you specify uses SNTP version 4 or later, use the sntp server command to specify the correct version number. For example, suppose you learned that SNTP version 4 was in use on the server you specified above (IP address 10.28.227.141).
  • Page 165 Time Protocols SNTP: Viewing, Selecting, and Configuring If you then viewed the SNTP configuration, you would see the following: Figure 9-7. Example of SNTP with Time Sychronization Disabled Disabling the SNTP Mode. If you want to prevent SNTP from being used even if selected by timesync (or the Menu interface’s Time Sync Method param- eter), configure the SNTP mode as disabled.
  • Page 166 Time Protocols TimeP: Viewing, Selecting, and Configuring TimeP: Viewing, Selecting, and Configuring TimeP Feature Default Menu view the Timep time synchronization page 9-15 page 9-17 — configuration select Timep as the time synchronization TIMEP page 9-13 pages 9-18 — method disable time synchronization timep page 9-15...
  • Page 167 Time Protocols TimeP: Viewing, Selecting, and Configuring Menu: Viewing and Configuring TimeP To View, Enable, and Modify the TimeP Protocol: From the Main Menu, select: 2. Switch Configuration... 1. System Information Time Protocol Selection Parameter – TIMEP (the default) – SNTP –...
  • Page 168 Time Protocols TimeP: Viewing, Selecting, and Configuring Use the Space bar to select the Manual mode. • Press [>] to move the cursor to the Server field. Address ii. Enter the IP address of the TimeP server you want the switch to use for time synchronization.
  • Page 169 Time Protocols TimeP: Viewing, Selecting, and Configuring This section describes how to use the CLI to view, enable, and configure TimeP parameters. Viewing the Current TimeP Configuration This command lists both the time synchronization method (TimeP, SNTP, or None) and the TimeP configuration, even if SNTP is not the selected time protocol.
  • Page 170 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 171 Time Protocols TimeP: Viewing, Selecting, and Configuring The commands and output would appear as follows: show timep displays the TimeP configuration and also shows that SNTP is the currently active time synchronization mode. show timep again displays the TimeP configuration and shows that TimeP is now the currently active time synchronization mode.
  • Page 172 Time Protocols TimeP: Viewing, Selecting, and Configuring Figure 9-13. Example of Configuring Timep for Manual Operation Changing the TimeP Poll Interval. This command lets you specify how long the switch waits between time polling intervals. The default is 720 minutes and the range is 1 to 9999 minutes. (This parameter is separate from the poll interval parameter used for SNTP operation.) Syntax: ip timep dhcp interval <...
  • Page 173 Time Protocols SNTP Unicast Time Polling with Multiple SNTP Servers Disabling the TimeP Mode. Disabling the TimeP mode means to configure it as disabled. (Disabling TimeP prevents the switch from using it as the time synchronization protocol, even if it is the selected option.) Time Sync Method Syntax:...
  • Page 174 Time Protocols SNTP Unicast Time Polling with Multiple SNTP Servers Address Prioritization If you use the CLI to configure multiple SNTP servers, the switch prioritizes them according to the decimal values of their IP addresses. That is, the switch compares the decimal value of the octets in the addresses and orders them accordingly, with the lowest decimal value assigned as the primary address, the second-lowest decimal value assigned as the next address, and the third- lowest decimal value as the last address.
  • Page 175 Time Protocols SNTP Unicast Time Polling with Multiple SNTP Servers N o t e If there are already three SNTP server addresses configured on the switch, and you want to use the CLI to replace one of the existing addresses with a new one, you must delete the unwanted address before you configure the new one.
  • Page 176 Time Protocols SNTP Messages in the Event Log SNTP Messages in the Event Log If an SNTP time change of more than three seconds occurs, the switch’s event log records the change. SNTP time changes of less than three seconds do not appear in the Event Log.
  • Page 177 Using the CLI To Configure a Broadcast Limit ....10-11 Configuring HP Auto-MDIX ......10-12 Manual Auto-MDIX Override .
  • Page 178 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 Auto-MDIX ■...
  • Page 179 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 180 Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Status or Description Parameter Flow Control • Disabled (default): The port does not generate flow control packets, and drops any flow control packets it receives. • Enabled: The port uses 802.3x Link Layer Flow Control, generates flow control packets, and processes received flow control packets.
  • Page 181 Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters In this example, ports A7 and A8 have previously been configured as a trunk group. Figure 10-1. Example of the Port Status Screen 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.
  • Page 182 Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters (for Edit). The cursor moves to the Enabled field for the first port. Press Refer to the online help provided with this screen for further information on configuration options for these features. When you have finished making changes to the above parameters, press [Enter], then press (for Save).
  • Page 183 Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters Feature Show Interfaces Brief Show Interfaces Config Intrusion Alert Mode (Configured) MDIX Mode Operating Configured * There is also the show interfaces [< port-number >] option, which displays port statistics.
  • Page 184 Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters ProCurve# show interface brief Current Operating Mode Status and Counters - Port Status | Intrusion Flow Bcast Port Type | Alert Enabled Status Mode Mode Ctrl Limit ----- --------- + --------- ------- ------ ---------- ----- ----- ------ 100/1000T | No Down 1000FDx...
  • Page 185 ■ The following error messages may be displayed for a non-operational transceiver: • Unsupported Transceiver. (SelfTest Err#060) Check: www.hp.com/rnd/device_help/2_inform for more info. • This switch only supports revision B and above transceivers. Check: www.hp.com/rnd/device_help/ 2_inform for more info. •...
  • Page 186 Transceiver type not supported in this software version. • Not a ProCurve Transceiver. Please go to: www.hp.com/rnd/device_help/2_inform for more info. Displaying Spanning Tree Configuration Details To view detailed statistics on spanning tree operation for different ports, use the show spanning-tree command.
  • Page 187 Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters ProCurve(config)# int e 6 ProCurve(eth-6)# speed-duplex 100-full If port 8 was disabled, and you wanted to enable it and configure it for 100FDx with flow-control active, you could do so with either of the following com- mand sets.
  • Page 188 MDI-X port. HP Auto-MDIX was developed for auto-negotiating devices, and was shared with the IEEE for the development of the IEEE 802.3ab standard. HP Auto- MDIX and the IEEE 802.3ab Auto MDI/MID-X feature are completely compat- ible.
  • Page 189 Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters If you want more information on this subject please refer to the IEEE 802.3ab Standard Reference. For more information on MDI-X, refer to the appendix titled “Switch Ports and Network Cables”...
  • Page 190 Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters 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 191 Port Status and Basic Configuration Viewing Port Status and Configuring Port Parameters N o t e Port Response to Switch Software Updates ■ Switch software updated from xx.xx.xx or earlier Copper ports in auto-negotiation still default to auto-mdix mode. Copper ports in forced speed/duplex default to mdix mode. The default is auto-mdix.
  • Page 192 Port Status and Basic Configuration QoS Pass-Through Mode QoS Pass-Through Mode QoS Pass-Through mode is designed to enhance the performance of line-rate traffic transfers through the switches covered in this guide. This feature should only be used in environments where Quality of Service (QoS) is not of major importance, but where lossless data transfers are key.
  • Page 193 Port Status and Basic Configuration QoS Pass-Through Mode High priority packets sourced by the switch itself, such as Spanning ■ Tree packets, will be serviced in the "high" priority queue. Any 802.1p tagging on a received packet, or any tag added to a ■...
  • Page 194 Port Status and Basic Configuration QoS Pass-Through Mode How to enable/disable QoS Pass-Through Mode 2510-48: QoS Pass-Through Mode is enabled by default (Optimized). 2510-24: QoS Pass-Through Mode is disabled by default (Typical). To enable or disable QoS Pass-Through Mode: Syntax: [no] qos-passthrough-mode write memory reload The above command sequence enables QoS pass-through...
  • Page 195 Port Status and Basic Configuration QoS Pass-Through Mode Configuring Port-Based Priority for Incoming Packets Feature Default Menu Assigning a priority level to traffic on the basis Disabled page 10-22 of incoming port When network congestion occurs, it is important to move traffic on the basis of relative importance.
  • Page 196 Port Status and Basic Configuration QoS Pass-Through Mode Outbound Port Queues and Packet Priority Settings Ports on the ProCurve switches have the following outbound port queue structure: Switch Model Outbound Port Queues Switch 6108 Series 5300xl Switch Series 4100gl Switch Series 3400cl Switch Series 2600, 2600-PWR Switch Series 2800 Switch...
  • Page 197 Port Status and Basic Configuration QoS Pass-Through Mode For example, suppose you have configured port 10 to assign a priority level of 1 (low): ■ An untagged packet coming into the switch on port 10 and leaving the switch through any other port configured as a tagged VLAN member would leave the switch as a tagged packet with a priority level of 1.
  • Page 198 Port Status and Basic Configuration QoS Pass-Through Mode Configuring and Viewing Port-Based Priority This command enables or disables port-based priority on a per-port basis. You can either enter the command on the interface context level or include the interface in the command. Syntax: interface <port #>...
  • Page 199 Port Status and Basic Configuration QoS Pass-Through Mode For example, suppose you wanted to configure ports 1-3 on the switch to prioritize all untagged, inbound VLAN traffic as “Low” (priority level = 1; refer to table 10-3 on page 10-20). ProCurve(config)# int 1-3 qos priority 1 Ports 1-3 are now ProCurve(config)# write mem...
  • Page 200 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 25 Numbering Display Friendly Port Names page 27 This feature enables you to assign alphanumeric port names of your choosing to augment automatically assigned numeric port names.
  • Page 201 Port Status and Basic Configuration Using Friendly (Optional) Port Names In a port listing, not assigned indicates that the port does not have a name ■ assignment other than its fixed port number. To retain friendly port names across reboots, you must save the current ■...
  • Page 202 Port Status and Basic Configuration Using Friendly (Optional) Port Names Configuring the Same Name for Multiple Ports. Suppose that you want to use ports 5 through 8 as a trunked link to a server used by a drafting group. In this case you might configure ports 5 through 8 with the name “Draft- Server:Trunk”.
  • Page 203 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 204 Port Status and Basic Configuration Using Friendly (Optional) Port Names Port Without a "Friendly" Name Friendly port names assigned in previous examples. Figure 10-16. 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 205 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- config file.
  • Page 206 Port Status and Basic Configuration Using Friendly (Optional) Port Names 10-30...
  • Page 207 Port Trunking Contents Overview ........... . . 11-2 Port Status and Configuration .
  • Page 208 This capability applies to connections between backbone devices as well as to connections in other network areas where traffic bottlenecks exist. Port Trunking Support ProCurve 2510-24 Switch ProCurve 2510-48 Switch Ports per trunk (maximum) Trunks per switch (maximum) (2-10/100 trunks of 4 ports,...
  • Page 209 Port Trunking Port Status and Configuration The multiple physical links in a trunk behave as one logical link Switch 2: port a1 Switch 1: port c1 port a2 port c2 Ports a2 and Ports c1 - c4 port a3 port c3 a4 - a6 are configured port a4...
  • Page 210 Port Trunking Port Status and Configuration Fault Tolerance: If a link in a port trunk fails, the switch redistributes traffic originally destined for that link to the remaining links in the trunk. The trunk remains operable as long as there is at least one link in operation. If a link is restored, that link is automatically included in the traffic distribution again.
  • Page 211 • 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 212 Port Trunking Port Status and Configuration Table 11-3. General Operating Rules for Port Trunks Media: All ports on both ends of a trunk group must have the same media type and mode (speed and duplex). The switch blocks any trunked links that do not conform to this rule. (For the switches covered in this guide, ProCurve recommends Auto Auto-10 leaving the port Mode setting at...
  • Page 213 Port Trunking Port Status and Configuration Spanning Tree: Spanning Tree operates as a global setting on the switch (one instance of Spanning Tree per switch). However, you can adjust Spanning Tree parameters on a per-port basis. A static trunk of any type appears in the Spanning Tree configuration display, and you can configure Spanning Tree parameters for a static trunk in the same way that you would configure Spanning Tree parameters on a non-trunked port.
  • Page 214 Port Trunking Port Status and Configuration 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 215 Port Trunking Port Status and Configuration • 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. To verify these settings, see “Viewing Port Status and Configuring Port Param- eters”...
  • Page 216 Port Trunking Port Status and Configuration 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 217 Port Trunking Port Status and Configuration 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 218 Port Trunking Port Status and Configuration Listing Static LACP and Dynamic LACP Trunk Data. This command lists data for only the LACP-configured ports. Syntax: show lacp In the following example, ports A1 and A2 have been previously configured for a static LACP trunk. (For more on “Active”, see table 11-5 on page 11-20.) Figure 11-6.
  • Page 219 Port Trunking Port Status and Configuration “Up” Links Standby Link Figure 11-7. Example of a Dynamic LACP Trunk with One Standby Link Using the CLI To Configure a Static or Dynamic Trunk Group I m p o r t a n t Configure port trunking before you connect the trunked links between switches.
  • Page 220 Port Trunking Port Status and Configuration The following examples show how to create different types of trunk groups. Configuring a Static Trunk or Static LACP Trunk Group. For switches covered in this guide: Syntax: trunk <port-list> < trk1 ... trk24 > < trunk | lacp > The following example uses ports 4 - 6 to create a non-protocol static trunk group with the group name of Trk2.
  • Page 221 Port Trunking Port Status and Configuration Switch “A” Switch “B” with ports set with ports set to LACP to LACP passive (the passive (the default). default). Dynamic LACP trunk cannot automatically form because both ends of the links are LACP passive. (In this case STP blocking is needed to prevent a loop.
  • Page 222 Port Trunking Port Status and Configuration Syntax: no interface <port-list> lacp In this example, port 6 belongs to an operating, dynamic LACP trunk. To remove port 6 from the dynamic trunk and return it to passive LACP, you would do the following: ProCurve>(config)# no interface 6 lacp ProCurve>(config)# interface 6 lacp passive Note that in the above example, if the port on the other end of the link is...
  • Page 223 Port Trunking Port Status and Configuration N o t e Dynamic LACP trunks operate only in the default VLAN (unless GVRP is enabled and Forbid is used to prevent the trunked ports from joining the default VLAN). Thus, if an LACP dynamic trunk forms using ports that are not in the default VLAN, the trunk will automatically move to the default VLAN unless GVRP operation is configured to prevent this from occurring.
  • Page 224 Port Trunking Port Status and Configuration Table 11-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 1 to 24 depending on how many dynamic and static trunks are currently on the switch.
  • Page 225 Port Trunking Port Status and Configuration Default Port Operation In the default configuration, LACP is off. The port will not try to detect a trunk configuration and will operate as a standard, untrunked port. N o t e Passive and active LACP ports will pause and listen for LACP packets once a link is established.
  • Page 226 Port Trunking Port Status and Configuration Table 11-5. LACP Port Status Data Status Name Meaning Port Numb Shows the physical port number for each port configured for LACP operation (1, 2, 3 . . .). Unlisted port numbers indicate that the missing ports are assigned to a static Trunk group or are not configured for any trunking.
  • Page 227 Port Trunking Port Status and Configuration LACP Notes and Restrictions 802.1X (Port-Based Access Control) Configured on a Port. To main- tain security, LACP is not allowed on ports configured for 802.1X authenticator operation. If you configure port security on a port on which 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 802.1X on that port.
  • Page 228 Port Trunking Port Status and Configuration Static LACP Trunks. Where a port is configured for LACP (Active or Passive), but does not belong to an existing trunk group, you can add that port to a static trunk. Doing so disables dynamic LACP on that port, which means you must manually configure both ends of the trunk.
  • Page 229 Port Trunking Port Status and Configuration Half-Duplex and/or Different Port Speeds Not Allowed in LACP Trunks. The ports on both sides of an LACP trunk must be configured for the same speed and for full-duplex (FDx). The 802.3ad LACP standard speci- fies a full-duplex (FDx) requirement for LACP trunking.
  • Page 230 Port Trunking Port Status and Configuration Interface Option Dynamic LACP Static LACP Static Non-Protocol Trunk Group Trunk Group Trunk Group Menu Interface CLI: show trunks show interfaces show lacp show spanning-tree show igmp show config Outbound Traffic Distribution Across Trunked Links Both trunk group options (LACP and Trunk) use source-destination address pairs (SA/DA) for distributing outbound traffic over trunked links.
  • Page 231 Port Trunking Port Status and Configuration Switch Switch Figure 11-10. Example of Port-Trunked Network Table 11-6. Example of Link Assignments in a Trunk Group (SA/DA Distribution) Source: Destination: Link: Node A Node W Node B Node X Node C Node Y Node D Node Z Node A...
  • Page 232 Port Trunking Port Status and Configuration 11-26...
  • Page 233 Configuring for Network Management Applications Contents Using SNMP Tools To Manage the Switch ......12-3 Overview ..........12-3 SNMP Management Features .
  • Page 234 Configuring for Network Management Applications Contents Configuring LLDP Operation ....... . 12-32 Viewing the Current Configuration .
  • Page 235 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch 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+).
  • Page 236 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Security via configuration of SNMP communities (page 12-4) ■ ■ Security via authentication and privacy for SNMP Version 3 access Event reporting via SNMP ■ • Version 1 traps •...
  • Page 237 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch C a u t i o n The “public” community exists by default and is used by ProCurve’s network management applications. Deleting the “public” community disables many network management functions (such as auto-discovery, traffic monitoring, SNMP trap generation, and threshold setting).
  • Page 238 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch SNMP Version 3 Commands SNMP version 3 (SNMPv3) adds new commands to the CLI for configuring SNMPv3 functions. You can: Enable SNMPv3 with the snmpv3 enable command. An initial user entry ■...
  • Page 239 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch SNMPv3 Enable 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 12-1 shows and example of this dialog.
  • Page 240 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch SNMP Version 3 Users The second step to using SNMPv3 on the switch is to configure the users that you assign to different groups. To establish users on the switch: Add the users to the User table.
  • Page 241 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch [no] snmpv3 group group_name user user_name sec-model <ver1| ver2c | ver3> user user_name This is 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>...
  • Page 242 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Then you must set the group access level to the user. This is done with the snmpv3 group command. For more details on the MIBs access for a give group see “Group Access Levels”...
  • Page 243 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Group Access Levels The switch supports eight predefined group access levels. There are four levels for use with version 3 users and four are used for access by version 2c or version 1 management applications.
  • Page 244 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch SNMP 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 245 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Figure 12-4 shows the assigning of the 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 12-4.
  • Page 246 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch C a u t i o n Deleting or changing the community named “public” prevents network management applications (such as auto-discovery, traffic monitoring, SNMP trap generation, and threshold setting) from operating in the switch. (Changing or deleting the “public”...
  • Page 247 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 248 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch CLI: Viewing and Configuring SNMP Community Names Community Name Commands Page show snmp-server [<community-string>] 12-16 [no] snmp-server 12-17 [community <community-str>] 12-17 [host <community-str> <ip-addr>] 12-22 [<none | debug | all | not-info | critical>] [enable traps <authentication>...
  • Page 249 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch 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. Syntax: [no] snmp-server community < community-name > Configures a new community name.
  • Page 250 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch SNMP Notification and Traps The switches covered in this guide support the SNMPv3 notification process. They also support version 1or version 2c traps. For more information on version 1 or version 2c traps, see “Trap Features” on page 12-20. The SNMPv3 notification process allows for the messages passed to be authenticated and encrypted if you choose.
  • Page 251 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch [no] snmpv3 targetaddress <addr-name> params < params-name> < IP-Addr > max-msg-size<size> The maximum number of bytes of length a message to this target can be. ( Default:1472) taglist < tag-params> Set list of values used to select this entry from snmpNotifyTable.
  • Page 252 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Trap Features Feature Default Menu snmp-server host (trap receiver) public — page — 12-22 snmp-server enable (authentication trap) none — page — 12-23 A trap receiver is a management station designated by the switch to receive SNMP traps sent from the switch.
  • Page 253 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Using the CLI To List Current SNMP Trap Receivers. This command lists the currently configured trap receivers and the setting for authentication traps (along with the current SNMP community name data — see “SNMP Communities”...
  • Page 254 Table 12-2. Options for Sending Event Log Messages as Traps Event Level Description None (default) Send no log messages. Send all log messages. Not INFO Send the log messages that are not information-only. Critical Send critical-level log messages. Debug Reserved for HP-internal use. 12-22...
  • Page 255 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch 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 N o t e s To replace one community name with another for the same IP address, you...
  • Page 256 Configuring for Network Management Applications Using SNMP Tools To Manage the Switch Advanced Management: RMON The switches covered in this guide support RMON (Remote Monitoring) on all connected network segments. This allows for troubleshooting and optimizing your network. The following RMON groups are supported: ■...
  • Page 257 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) LLDP (Link-Layer Discovery Protocol) To standardize device discovery on all ProCurve switches, LLDP has been implemented while offering limited read-only support for CDP as documented in this manual. For current information on your switch model, consult the latest Release Notes (available on the ProCurve Networking web site).
  • Page 258 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Also, by using show commands to access the switch’s neighbor database for information collected by an individual switch, system administrators can learn about other devices connected to the switch, including device type (capability) and some configuration information.
  • Page 259 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) NANP (North American Numbering Plan): A ten-digit telephone number format where the first three digits are an area code and the last seven-digits are a local telephone number. Neighbor: See “LLDP Neighbor”. Non-LLDP Device: A device that is not capable of LLDP operation.
  • Page 260 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Packet Boundaries in a Network Topology ■ Where multiple LLDP devices are directly connected, an outbound LLDP packet travels only to the next LLDP device. An LLDP-capable device does not forward LLDP packets to any other devices, regardless of whether they are LLDP-enabled.
  • Page 261 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 262 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Data Type Configuration Default Description Options System Description Enable/Disable Enabled Includes switch model name and running software version, and ROM version. Port Description Enable/Disable Enabled Uses the physical port identifier. System capabilities Enable/Disable Enabled Identifies the switch’s primary capabilities (bridge, router).
  • Page 263 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) LLDP Standards Compatibility The operation covered by this section is compatible with these standards: ■ IEEE P802.1AB RFC 2922 (PTOPO, or Physical Topology MIB) ■ ■ RFC 2737 (Entity MIB) ■ RFC 2863 (Interfaces MIB) LLDP Operating Rules Port Trunking.
  • Page 264 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Spanning-Tree Blocking. Spanning tree does not prevent LLDP packet transmission or receipt on STP-blocked links. 802.1X Blocking. Ports blocked by 802.1X operation do not allow transmission or receipt of LLDP packets. Configuring LLDP Operation In the default configuration, LLDP is enabled and in both transmit and receive mode on all active ports.
  • Page 265 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) For example, show lldp config produces the following display when the switch is in the default LLDP configuration: Note: This value corresponds to the lldp refresh-interval command (page 12-35). Med Topology Trap Enabled ------------------------- False True...
  • Page 266 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Displaying Port Configuration Details. This command displays the port- specific configuration, including. Syntax show lldp config < port-list > Displays the LLDP port-specific configuration for all ports in < port-list >, including which optional TLVs and any non-default IP address that are included in the port’s outbound advertisements.
  • Page 267 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Configuring Global LLDP Packet Controls The commands in this section configure the aspects of LLDP operation that apply the same to all ports in the switch. Enabling or Disabling LLDP Operation on the Switch. Enabling LLDP operation (the default) causes the switch to: ■...
  • Page 268 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Changing the Time-to-Live for Transmitted Advertisements. The Time-to-Live value (in seconds) for all LLDP advertisements transmitted from a switch is controlled by the switch that generates the advertisement, and determines how long an LLDP neighbor retains the advertised data before discarding it.
  • Page 269 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Syntax setmib lldpTxDelay.0 -i < 1 - 8192 > Uses setmib to change the minimum time (delay-interval) any LLDP port will delay advertising successive LLDP advertisements due to a change in LLDP MIB content. (Default: 2;...
  • Page 270 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) delay interval delays the port’s ability to reinitialize and generate LLDP traffic following an LLDP disable/enable cycle. Syntax setmib lldpReinitDelay.0 -i < 1 - 10 > Uses setmib to change the minimum time (reinitialization delay interval) an LLDP port will wait before reinitializing after receiving an LLDP disable command followed closely by a txonly or tx_rx command.
  • Page 271 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Changing the Minimum Interval for Successive Data Change Notifications for the Same Neighbor. If 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 272 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Configuring Basic LLDP Per-Port Advertisement Content In the default LLDP configuration, outbound advertisements from each port on the switch include both mandatory and optional data. Mandatory Data. An active LLDP port on the switch always includes the mandatory data in its outbound advertisements.
  • Page 273 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) For example, if port 3 belongs to a subnetted VLAN that includes an IP address of 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.
  • Page 274 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) system_descr For outbound LLDP advertisements, this TLV includes an alphanumeric string describing the full name and version identification for the system’s hardware type, software version, and networking application. (Default: Enabled) system_cap For outbound advertisements, this TLV includes a bitmask of supported system capabilities (device functions).
  • Page 275 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Syntax: [ no ] lldp config < port-list > dot3TlvEnable macphy_config For outbound advertisements, this TLV includes the (local) switch port’s current speed and duplex settings, the range of speed and duplex settings the port supports, and the method required for reconfiguring the speed and duplex settings on the device (auto-negotiation during link initialization, or manual configuration).
  • Page 276 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 277 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- configurable IP addresses available).
  • Page 278 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Syntax: show interfaces brief < port-list > Includes port speed and duplex configuration in the Mode column of the resulting display. Displaying Advertisements Currently in the Neighbors MIB. These commands display the content of the inbound LLDP advertisements received from other LLDP devices.
  • Page 279 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Figure 12-15. Example of a Global Listing of Discovered Devices 12-47...
  • Page 280 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 281 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) — Continued — 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 282 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 283 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) LLDP Operating Notes Neighbor Maximum. The neighbors table in the switch supports as many neighbors as there are ports on the switch. The switch can support multiple neighbors connected through a hub on a given port, but if the switch neighbor maximum is reached, advertisements from additional neighbors on the same or other ports will not be stored in the neighbors table unless some existing neighbors time-out or are removed.
  • Page 284 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) LLDP and CDP Data Management This section describes points to note regarding LLDP (Link-Layer Discovery Protocol) and CDP (Cisco Discovery Protocol) data received by the switch from other devices. LLDP operation includes both transmitting LLDP packets to neighbor devices and reading LLDP packets received from neighbor devices.
  • Page 285 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) 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 286 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) CDP Operation and Commands By default the switches covered by this guide have CDP enabled on each port. This is a read-only capability, meaning that the switch can receive and store information about adjacent CDP devices but does not generate CDP packets.
  • Page 287 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) The following example shows the default CDP configuration. CDP Enable/Disable on the Switch Per-Port CDP Enable/Disable Figure 12-18. Example of Show CDP with the Default CDP Configuration Viewing the Switch’s Current CDP Neighbors Table. Devices are listed by the port on which they were detected.
  • Page 288 Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Enabling CDP Operation. Enabling CDP operation (the default) on the switch causes the switch to add entries to its CDP Neighbors table for any CDP packets it receives from other neighboring CDP devices. Disabling CDP Operation.
  • Page 289 File Transfers Contents Overview ........... . . A-2 Downloading Switch Software .
  • Page 290 File Transfers Overview Overview You can download new switch software and upload or download switch configuration files. These features are useful for acquiring periodic switch software upgrades and for storing or retrieving a switch configuration. This appendix includes the following information: ■...
  • Page 291 File Transfers Downloading Switch Software General Switch Software Download Rules ■ A switch software image downloaded through the menu interface always goes to primary flash. ■ After a switch software download, you must reboot the switch to imple- ment the newly downloaded code. Until a reboot occurs, the switch continues to run on the software it was using before the download started.
  • Page 292 File Transfers Downloading Switch Software N o t e If your TFTP server is a Unix workstation, ensure that the case (upper or lower) that you specify for the filename is the same case as the characters in the switch software filenames on the server. Menu: TFTP Download from a Server to Primary Flash Note that the menu interface accesses only the primary flash.
  • Page 293 File Transfers Downloading Switch Software Progress Bar Figure A-2. Example of the Download OS Screen During a Download A “progress” bar indicates the progress of the download. When the entire switch software file has been received, all activity on the switch halts and you will see Validating and writing system software to FLASH...
  • Page 294 File Transfers Downloading Switch Software CLI: TFTP Download from a Server to Primary or Secondary Flash This command automatically downloads a switch software image to primary or secondary flash. Syntax: copy tftp flash < ip-address > < remote-os-file > [< primary | secondary >] Note that if you do not specify the flash destination, the Xmodem download defaults to primary flash.
  • Page 295 File Transfers Downloading Switch Software If you need information on primary/secondary flash memory and the boot commands, refer to “Using Primary and Secondary Flash Image Options” on page 6-12. Using Secure Copy and SFTP For some situations you may want to use a secure method to issue commands or copy files to the switch.
  • Page 296 File Transfers Downloading Switch Software N o t e 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 297 File Transfers Downloading Switch Software The SCP/SFTP Process To use SCP and SFTP: Open an SSH session as you normally would to establish a secure encrypted tunnel between your computer and the switch. For more detailed directions on how to open an SSH session see the chapter titled “Configuring Secure Shell (SSH)”...
  • Page 298 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 299 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 crash-log event log +---os primary secondary...
  • Page 300 File Transfers Downloading Switch Software Menu: Xmodem Download to Primary Flash Note that the menu interface accesses only the primary flash. From the console Main Menu, select 7. Download OS (for Edit). Press Use the Space bar to select XMODEM in the Method field. Press [Enter], then (for eXecute) to begin the switch software download.
  • Page 301 File Transfers Downloading Switch Software CLI: Xmodem Download from a PC or Unix Workstation to Primary or Secondary Flash Using Xmodem and a terminal emulator, you can download a switch software file to either primary or secondary flash. Syntax: copy xmodem flash [< primary | secondary >] Note that if you do not specify the flash destination, the Xmodem download defaults to primary flash.
  • Page 302 File Transfers Downloading Switch Software To confirm that the operating system downloaded correctly, use the show system, show version, or show flash CLI commands. Check the Firmware revision line. It should show the switch software version that you downloaded in the preceding steps. If you need information on primary/secondary flash memory and the boot commands, refer to “Using Primary and Secondary Flash Image Options”...
  • Page 303 File Transfers Downloading Switch Software After the primary flash memory has been updated with the new operating system, you must reboot the switch to implement the newly downloaded (for Reboot Switch). You will then software. From the Main Menu, press see this prompt: Continue reboot of system? Press the space bar once to change No to Yes, then press...
  • Page 304 File Transfers Downloading Switch Software Running Total of Bytes Downloaded Figure A-5. Switch-To-Switch, from Primary in Source to Either Flash in Destination Downloading from Either Flash in the Source Switch to Either Flash in the Destination Switch. This command (executed in the destination switch) gives you the most options for downloading between switches.
  • Page 305 File Transfers Troubleshooting TFTP Downloads Troubleshooting TFTP Downloads When using the menu interface, if a TFTP download fails, the Download OS screen indicates the failure. Message Indicating cause of TFTP Download Failure Figure A-7. Example of Message for Download Failure 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...
  • Page 306 File Transfers Transferring Switch Configurations For a Unix TFTP server, the file permissions for the switch software file ■ do not allow the file to be copied. ■ Another console session (through either a direct connection to a terminal device or through Telnet) was already running when you started the session in which the download was attempted.
  • Page 307 File Transfers Transferring Switch Configurations TFTP: Copying a Configuration File to a Remote Host. Syntax: copy < startup-config | running-config > tftp < ip-addr > < remote-file > This command copies the switch’s startup configuration (startup-config file) to a remote TFTP host. For example, to upload the current startup configuration to a file named sw2510 in the configs directory on drive “d”...
  • Page 308 File Transfers Transferring Switch Configurations Xmodem: Copying a Configuration File from a Serially Connected PC or Unix Workstation. To use this method, the switch must be connected via the serial port to a PC or Unix workstation on which is stored the configuration file you want to copy.
  • Page 309 File Transfers Copying Diagnostic Data to a Remote Host, PC, or Unix Workstation Copying Diagnostic Data to a Remote Host, PC, or Unix Workstation You can use the CLI to copy the following types of switch data to a text file in a management device: ■...
  • Page 310 File Transfers Copying Diagnostic Data to a Remote Host, PC, or Unix Workstation Copying Event Log Output to a Destination Device This command uses TFTP or Xmodem to copy the Event Log content to a PC or UNIX workstation on the network. Syntax: copy event-log tftp <...
  • Page 311 File Transfers Copying Diagnostic Data to a Remote Host, PC, or Unix Workstation Copying Crash Log Data Content to a Destination Device This command uses TFTP or Xmodem to copy the Crash Log content to a PC or UNIX workstation on the network. You can copy individual slot information or the master switch information.
  • Page 312 File Transfers Copying Diagnostic Data to a Remote Host, PC, or Unix Workstation A-24...
  • Page 313 Monitoring and Analyzing Switch Operation Contents Overview ........... . . B-3 Status and Counters Data .

  • Page 314: Table Of Contents

    Monitoring and Analyzing Switch Operation Contents Port and Static Trunk Monitoring Features ..... . . B-23 Menu: Configuring Port and Static Trunk Monitoring ... B-24 CLI: Configuring Port and Static Trunk Monitoring .
  • Page 315 Monitoring and Analyzing Switch Operation Overview Overview The switch has several built-in tools for monitoring, analyzing, and trouble- shooting 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 316 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 317 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 318 Monitoring and Analyzing Switch Operation Status and Counters Data General System Information Menu Access From the console Main Menu, select: 1. Status and Counters 1. General System Information Figure B-2. Example of General Switch Information This screen dynamically indicates how individual switch resources are being used.
  • Page 319 Monitoring and Analyzing Switch Operation Status and Counters Data Switch Management Address Information Menu Access From the Main Menu, select: 1. Status and Counters . . . 2. Switch Management Address Information Figure B-3. Example of Management Address Information with VLANs Configured This screen displays addresses that are important for management of the switch.
  • Page 320 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 321 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.
  • Page 322 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 323 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 324 Monitoring and Analyzing Switch Operation Status and Counters Data CLI Access To Port and Trunk Group Statistics To Display the Port Counter Summary Report. This command provides an overview of port activity for all ports on the switch. Syntax: show interfaces To Display a Detailed Traffic Summary for Specific Ports.
  • Page 325 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 326 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 327 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. From the Main Menu, select: 1.
  • Page 328 Monitoring and Analyzing Switch Operation Status and Counters Data CLI Access for MAC Address Views and Searches Syntax: show mac-address [vlan < vlan-id >] [ethernet]< port-list >] [< mac-addr >] To List All Learned MAC Addresses on the Switch, with The Port Number on Which Each MAC Address Was Learned.
  • Page 329 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-12.
  • Page 330 Monitoring and Analyzing Switch Operation Status and Counters Data Figure B-13. 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>...
  • Page 331 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 332 Monitoring and Analyzing Switch Operation Status and Counters Data VLAN Information The switch uses the CLI to display the following VLAN status: Syntax: show vlan Lists: • Maximum number of VLANs to support • Existing VLANs • Status (static or dynamic) •...
  • Page 333 Monitoring and Analyzing Switch Operation Status and Counters Data Listing the VLAN ID (VID) and Status for ALL VLANs in the Switch. Figure B-15. Example of VLAN Listing for the Entire Switch Listing the VLAN ID (VID) and Status for Specific Ports. Because ports A1 and A2 are not members of VLAN-...
  • Page 334 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- zation on each of the switch ports, symbolic port status indicators, and the Alert Log, which informs you of any problems that may have occurred on the...

  • Page 335: Port And Static Trunk Monitoring Features

    Monitoring and Analyzing Switch Operation Port and Static Trunk Monitoring Features Port and Static Trunk Monitoring Features Port Monitoring Features Feature Default Menu display monitoring disabled page B-24 page B-26 page B-28 configuration configure the monitor port(s) ports: none page B-24 page B-27 page B-28 selecting or removing ports none selected page B-24 page B-27 page B-28 You can designate a port for monitoring inbound (ingress) and outbound...

  • Page 336: Menu: Configuring Port And Static Trunk Monitoring

    Monitoring and Analyzing Switch Operation Port and Static Trunk 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.) From the Console Main Menu, select: 2.
  • Page 337 Monitoring and Analyzing Switch Operation Port and Static Trunk Monitoring Features Move the cursor to the Monitoring Port parameter. Port where monitored traffic exits the switch. Figure B-20. How To Select a Monitoring Port Use the Space bar to select the port to use for monitoring. 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 338: Cli: Configuring Port And Static Trunk Monitoring

    Monitoring and Analyzing Switch Operation Port and Static Trunk Monitoring Features CLI: Configuring Port and Static Trunk Monitoring Port and Static Trunk Monitoring Commands Used in This Section show monitor below mirror-port page B-27 monitor page B-27 You must use the following configuration sequence to configure port and static trunk monitoring in the CLI: Assign a monitoring (mirror) port.
  • Page 339 Monitoring and Analyzing Switch Operation Port and Static Trunk Monitoring Features Configuring the Monitor Port. This command assigns or removes a mon- itoring port, and must be executed from the global configuration level. Remov- ing the monitor port disables port monitoring and resets the monitoring parameters to their factory-default settings.

  • Page 340: Web: Configuring Port Monitoring

    Monitoring and Analyzing Switch Operation Port and Static Trunk Monitoring Features These two commands show how to disable monitoring at the interface context level for a single port or all ports in an interface context level. These two commands show how to disable monitoring at the global config level for a single port or a group of ports .

  • Page 341: Locating A Device

    Monitoring and Analyzing Switch Operation Locating a Device Locating a Device If you are trying to locate a particular switch you can enter the chassislocate command. The blue Locator LED will light up on that switch. Syntax: chassislocate [ blink | on | off ] Locate a device by using the blue Locate LED on the front panel.
  • Page 342 Monitoring and Analyzing Switch Operation Locating a Device Locator LED Figure B-25. Location of the Locator LED B-30...
  • Page 343 Troubleshooting Contents Overview ........... . . C-3 Troubleshooting Approaches .
  • Page 344 Troubleshooting Contents Displaying the Configuration File ......C-39 CLI: Viewing the Configuration File ..... . C-39 Web: Viewing the Configuration File .

  • Page 345: Overview

    Troubleshooting Overview Overview This chapter addresses performance-related network problems that can be caused by topology, switch configuration, and the effects of other devices or their configurations on switch operation. (For switch-specific information on hardware problems indicated by LED behavior, cabling requirements, and other potential hardware-related problems, refer to the Installation and Getting Started Guide you received with the switch.) N o t e...
  • Page 346 Troubleshooting Troubleshooting Approaches Check the network cables – Cabling problems are a frequent cause of ■ network faults. Check the cables for damage, correct type, and proper connections. You should also use a cable tester to check your cables for compliance to the relevant IEEE 802.3 specification.

  • Page 347: Chassis Over-Temperature Detection

    Troubleshooting Chassis Over-Temperature Detection Chassis Over-Temperature Detection If a switch reaches an over-temperature condition, it generates a chassis-module Warning message in the Event Log and in any optionally configured debug destinations (console session and SyslogD servers). If the switch later returns to its acceptable temperature range, it signals this event with a chassis module Information message to the same destinations.
  • Page 348 Troubleshooting Chassis Over-Temperature Detection If there are no fan failures, ensure that the ambient temperature in the ■ switch’s operating area is not causing the over-temperature condition. If the condition persists, remove power from the switch until you can find the cause and apply an effective remedy.

  • Page 349: 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 350 Troubleshooting Browser or Telnet Access Problems Cannot Telnet into the switch console from a station on the network: Telnet access may be disabled by the Inbound Telnet Enabled parameter in ■ the System Information screen of the menu interface: 2. Switch Configuration 1.

  • Page 351: Unusual Network Activity

    Troubleshooting Unusual Network Activity Unusual Network Activity Network activity that fails to meet accepted norms may indicate a hardware problem with one or more of the network components, possibly including the switch. Such problems can also be caused by a network loop or simply too much traffic for the network as it is currently designed and implemented.

  • Page 352: 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 353: Lacp-Related Problems

    Troubleshooting Unusual Network Activity IP Multicast Traffic Floods Out All Ports; IGMP Does Not Appear To Filter Traffic. The IGMP feature does not operate if the switch or VLAN does not have an IP address configured manually or obtained through DHCP/ Bootp.

  • Page 354: Port-Based Access Control (802.1X)-Related Problems

    Troubleshooting Unusual Network Activity Port-Based Access Control (802.1X)-Related Problems N o t e To list the 802.1X port-access Event Log messages stored on the switch, use show log 802. See also “Radius-Related Problems” on page C-15. The switch does not receive a response to RADIUS authentication requests.
  • Page 355 Troubleshooting Unusual Network Activity The switch appears to be properly configured as a supplicant, but cannot gain access to the intended authenticator port on the switch to which it is connected. If aaa authentication port-access is configured for Local, ensure that you have entered the local login (operator-level) username and password of the authenticator switch into the identity and secret parame- ters of the supplicant configuration.
  • Page 356 Troubleshooting Unusual Network Activity a server-specific key. If the switch already has a server-specific key assigned to the server’s IP address, then it overrides the global key and must match the server key. Global RADIUS Encryption Key Unique RADIUS Encryption Key for the RADIUS server at 10.33.18.119 Figure C-3.

  • Page 357: Radius-Related Problems

    Troubleshooting Unusual Network Activity Radius-Related Problems The switch does not receive a response to RADIUS authentication requests. In this case, the switch will attempt authentication using the secondary method configured for the type of access you are using (console, Telnet, or SSH). There can be several reasons for not receiving a response to an authentication request.

  • Page 358: Spanning-Tree Protocol (Stp) And Fast-Uplink Problems

    Troubleshooting Unusual Network Activity Spanning-Tree Protocol (STP) and Fast-Uplink Problems C a u t i o n If you enable STP, it is recommended that you leave the remainder of the STP parameter settings at their default values until you have had an opportunity to evaluate STP performance in your network.

  • Page 359: Ssh-Related Problems

    Troubleshooting Unusual Network Activity SSH-Related Problems Switch access refused to a client. Even though you have placed the cli- ent’s public key in a text file and copied the file (using the copy tftp pub-key- file command) into the switch, the switch refuses to allow the client to have access.

  • Page 360: Stacking-Related Problems

    Troubleshooting Unusual Network Activity The public key file you are trying to download has one of the following problems: ■ A key in the file is too long. The maximum key length is 1024 characters, including spaces. This could also mean that two or more keys are merged together instead of being separated by a <CR><LF>.
  • Page 361 Troubleshooting Unusual Network Activity memory to save the authentication configuration to flash, then pressing the Reset button or cycling the power reboots the switch with the boot-up configuration. Disconnect the switch from network access to any TACACS+ servers ■ and then log in to the switch using either Telnet or direct console port access.

  • Page 362: Timep, Sntp, Or Gateway Problems

    Troubleshooting Unusual Network Activity The access attempt is outside of the time frame allowed for the ■ account. The allowed number of concurrent logins for the account has been ■ exceeded For more help, refer to the documentation provided with your TACACS+ server application.
  • Page 363 Troubleshooting Unusual Network Activity None of the devices assigned to one or more VLANs on an 802.1Q- compliant switch are being recognized. If multiple VLANs are being used on ports connecting 802.1Q-compliant devices, inconsistent VLAN IDs may have been assigned to one or more VLANs. For a given VLAN, the same VLAN ID must be used on all connected 802.1Q-compliant devices.
  • Page 364 Troubleshooting Unusual Network Activity Note that attempting to create redundant paths through the use of VLANs will cause problems with some switches. One symptom is that a duplicate MAC address appears in the Port Address Table of one port, and then later appears on another port.

  • Page 365: Using Logging To Identify Problem Sources

    Troubleshooting Using Logging To Identify Problem Sources Using Logging To Identify Problem Sources Event Log Operation 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 366 Troubleshooting Using Logging To Identify Problem Sources (The event log is not erased by using the Reboot Switch command in the Main Menu.) Table C-1.Event Log System Modules Module Event Description Module Event Description addrMgr Address table Console management chassis switch hardware ports Change in port status;...

  • Page 367: Menu: Entering And Navigating In The Event Log

    Troubleshooting Using Logging 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-8. 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 368: Cli

    Troubleshooting Using Logging To Identify Problem Sources CLI: Using the CLI, you can 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 ■...

  • Page 369: Debug And Syslog Operation

    Troubleshooting Using Logging To Identify Problem Sources Debug and Syslog Operation You can direct switch debug (Event log) messages to these destinations: ■ Up to six SyslogD servers One management-access session through: ■ • A direct-connect RS-232 console CLI session •...
  • Page 370 Troubleshooting Using Logging To Identify Problem Sources Debug Types. This section describes the types of debug messages the switch can send to configured debug destinations. Syntax: [no] debug < debug-type > Configures the switch to send all debug types to the config- ured debug destination(s).
  • Page 371 Troubleshooting Using Logging To Identify Problem Sources Configuring the Switch To Send Debug Messages to One or More SyslogD Servers. Use the logging command to configure the switch to send Syslog messages to a SyslogD server, or to remove a SyslogD server from the switch configuration.
  • Page 372 Troubleshooting Using Logging To Identify Problem Sources For example, on a switch where there are no SyslogD servers configured, you would do the following to configure SyslogD servers 18.120.38.155 and 18.120.43.125 and automatically enable Syslog logging (with user as the default logging facility): logging <...
  • Page 373 Troubleshooting Using Logging To Identify Problem Sources Enabling or Disabling Logging to Management Sessions and SyslogD Servers. Use this command when you want to do any of the following: ■ Disable Syslog logging on all currently configured SyslogD servers with- out removing the servers from the switch configuration.
  • Page 374 Troubleshooting Using Logging To Identify Problem Sources Shows that Syslog (Destination) logging is enabled and transmitting log messages to IP address 18.120.38.155. Also shows that the logging facility is set to user (the default), and that session logging is enabled.) Disables Syslog logging (but retains the Syslog IP address in the switch configuration).
  • Page 375 Troubleshooting Using Logging To Identify Problem Sources Syntax: show debug List the current debug status for both Syslog logging and Session logging. Shows that Syslog logging is enabled and sending event messages to the user facility on the SyslogD server at IP address 18.120.38.155.

  • Page 376: Diagnostic Tools

    Troubleshooting Diagnostic Tools Ensure that your Syslog server(s) will accept Debug messages. All ■ Syslog messages the switch generates carry the configured facility. All Syslog messages resulting from debug operation carry a “debug” severity. If you configure the switch to transmit debug messages to a SyslogD server, ensure that the server’s Syslog application is configured to accept the “debug”...

  • Page 377: Ping And Link Tests

    Troubleshooting Diagnostic Tools If the attached end-node does not have an Auto mode setting, then you must manually configure the switch port to the same setting as the end- node port. See Chapter 10, “Port Status and Basic Configuration”. Ping and Link Tests The Ping test and the Link test are point-to-point tests between your switch and another IEEE 802.3-compliant device on your network.

  • Page 378: Web: Executing Ping Or Link Tests

    Troubleshooting Diagnostic Tools Web: Executing Ping or Link Tests 1. Click here. 2. Click here. 4. For a Ping test, enter the IP address of the 3. Select Ping Test (the target device. For a default) or Link Test. Link test, enter the MAC address of the target device.

  • Page 379: Cli: Ping Or Link Tests

    Troubleshooting Diagnostic Tools To halt a Link or Ping test before it concludes, click on the Stop button. To reset the screen to its default settings, click on the Defaults button. CLI: Ping or Link Tests Ping Tests. You can issue single or multiple ping tests with varying repeti- tions and timeout periods.
  • Page 380 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 381: 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 382: Listing Switch Configuration And Operation Details For Help In Troubleshooting

    Troubleshooting Diagnostic Tools Listing Switch Configuration and Operation Details for Help in Troubleshooting The show tech command outputs, in a single listing, switch operating and running configuration details from several internal switch sources, including: ■ Image stamp (software version data) Running configuration ■...
  • Page 383 Troubleshooting Diagnostic Tools In Hyperterminal, click on Transfer | Capture Text... Figure C-17. The Capture Text window of the Hypertext Application Used with Microsoft Windows Software In the File field, enter the path and file name under which you want to store the show tech output.

  • Page 384: Cli Administrative And Troubleshooting Commands

    Troubleshooting Diagnostic Tools CLI Administrative and Troubleshooting Commands These commands provide information or perform actions that you may find helpful in troubleshooting operating problems with the switch. N o t e For more on the CLI, refer to “Using the Command Line Interface (CLI)” on page 4-1.

  • Page 385: 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 386: Restoring A Flash Image

    Troubleshooting Restoring a Flash Image 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 flash location.
  • Page 387 Troubleshooting Restoring a Flash Image 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: Change the switch baud rate to 115,200 Bps. =>...
  • Page 388 Troubleshooting Restoring a Flash Image Figure C-19. Example of Xmodem Download in Progress 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-46...
  • Page 389 MAC Address Management Contents Overview ........... . . D-2 Determining MAC Addresses in the Switch .

  • Page 390: Overview

    MAC Address Management Overview Overview The switch assigns MAC addresses in these areas: ■ For management functions: • One Base MAC address assigned to the default VLAN (VID = 1) • Additional MAC address(es) corresponding to additional VLANs you configure in the switch ■...

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

    MAC Address Management Determining MAC Addresses in the Switch Use the CLI to view the switch’s port MAC addresses in hexadecimal ■ format. Menu: Viewing the Switch’s MAC Addresses The Management Address Information screen lists the MAC addresses for: Base switch (default VLAN; VID = 1) ■...

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

    MAC Address Management Determining MAC Addresses in the Switch CLI: Viewing the Port and VLAN MAC Addresses The MAC address assigned to each switch port is used internally by such features as Flow Control and the Spanning Tree Protocol. Using the walkmib command to determine the MAC address assignments for individual ports can sometimes be useful when diagnosing switch operation.
  • Page 393 MAC Address Management Determining MAC Addresses in the Switch ifPhysAddress.1 - 6:Ports A1 - A6 in Slot 1 (Addresses 7 - 24 in slot 1 and 25 - 48 in slot 2 are unused.) ifPhysAddress.49 - 51:Ports C1 - C3 in Slot 3 (Addresses 52 - 72 in slot 3 are unused.) ifPhysAddress.205Base MAC Address (MAC Address for default VLAN;...

  • Page 394: 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 395 MAC Address Management Viewing the MAC Addresses of Connected Devices To list the MAC addresses of devices the switch has detected, use the show mac-address command. For example, ProCurve(config)# show mac-address Status and Counters - Port Address Table MAC Address Located on Port ------------- --------------- 001e6-09620c...
  • Page 396 MAC Address Management Viewing the MAC Addresses of Connected Devices...
  • Page 397 Daylight Savings Time on ProCurve Switches Configuring Daylight Savings Time This information applies to the following ProCurve switches: • 2510 • 3400cl • 1600M • ProCurve AdvanceStack • 2512 • 4108gl • 2400M Switches • 2524 • 4104gl • 2424M •...
  • Page 398 Daylight Savings Time on ProCurve Switches Configuring Daylight Savings Time Canada and Continental US: • Begin DST at 2am on the second Sunday in March. • End DST at 2am on the first Sunday in November. Middle Europe and Portugal: •...
  • Page 399 Daylight Savings Time on ProCurve Switches Configuring Daylight Savings Time 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 400 Daylight Savings Time on ProCurve Switches Configuring Daylight Savings Time...
  • Page 401 Index Symbols boot ROM console … A-3 boot ROM mode … C-44 => prompt … C-44 Bootp Bootp table file … 8-14 Numerics Bootptab file … 8-14 effect of no reply … C-9 802.1X operation … 8-13 LLDP blocked … 12-32 using with Unix systems …...
  • Page 402 configuration … 3-7 debug command Bootp … 8-14 "debug" severity and Syslog servers … C-34 comparing startup to running … 6-5 event … C-28 console … 7-3 event log … C-33 copying … A-18 syntax … C-28 download … A-3 debug logging factory default …...
  • Page 403 Emergency Location Identification Number … 12-26 IEEE 802.1d … C-16 ending a console session … 3-5 IEEE 802.3ab … 10-3 event log … 3-7, C-23 IEEE P802.1AB/D9 … 12-31 navigation … C-25 IGMP See also debug logging. host not receiving … C-10 severity level …...
  • Page 404 CDP neighbor data kill command … 7-10 LLDP neighbor data … 12-52 chassis ID … 12-40 chassis type … 12-40 clear statistics counters … 12-48 LACP comparison with CDP data fields … 12-52 802.1x, not allowed … 11-21 configuration options … 12-28 active …...
  • Page 405 … 12-41 MIB … 12-4 terminology … 12-26 MIB listing … 12-4 time-to-live … 12-28, 12-36 MIB, HP proprietary … 12-4 TLV … 12-27 MIB, standard … 12-4 transmission frequency … 12-28 mirroring transmission interval, change … 12-35 See port monitoring.
  • Page 406 network management functions … 12-5 CLI access … 10-6 network manager address … 12-4, 12-5 context level … 10-10 network monitoring control configuration … 10-1, 11-1 traffic overload … B-23 counters … B-10 Network Monitoring Port screen … B-23 counters, reset … B-10 network slow …...
  • Page 407 STP … 11-7 reconfigure … 3-10 STP operation … 11-6 reload … 6-17, 6-19 traffic distribution … 11-6 at/after … 6-20, 6-21 Trk1 … 11-6 scheduled … 6-20, 6-21 trunk (non-protocol) option … 11-5 remote session, terminate … 7-10 trunk option described … 11-23 reset …...
  • Page 408 show tech … C-40 unicast, address priority … 9-22 slow network … C-9 unicast, deleting addresses … 9-23 SNMP … 12-3 unicast, replacing servers … 9-23 CLI commands … 12-13 viewing … 9-4, 9-8 communities … 12-4, 12-5, 12-12, 12-13, 12-14 software version …...
  • Page 409 Syslog traffic, port … B-10 facility, user … C-34 transceiver See debug logging. error messages … 10-9 severity, "debug" … C-34 view status … 10-8 system configuration screen … 7-11 transceiver, fiber-optic … 10-3 System Name parameter … 7-12 trap … 5-25 authentication …...
  • Page 410 enabled … 5-2 browser interface online help location … 5-13 web browser access configuration … 7-3 management … 5-13 web browser enable/disable … 7-4 management server … 5-12, 5-13 web browser interface ProCurve Networking … 5-13 access parameters … 5-8 support …...
  • Page 412 Technical information in this document is subject to change without notice. © Copyright 2008 Hewlett-Packard Development Company, L.P. All rights reserved. Reproduction, adaptation, or translation without prior written permission is prohibited except as allowed under the copyright laws. January 2008 Manual Part Number 5991-4761...

This manual is also suitable for:

Procurve 2510-24Procurve 2510-48

Table of Contents