HP 5500 Ei 5500 Si Switch Series Configuration Guide
Have a look at the manual HP 5500 Ei 5500 Si Switch Series Configuration Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1114 HP manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
129 The main boot app is: flash:/soft-version2.bin The backup boot app is: flash:/ Slot 3 The current boot app is: flash:/soft-version2.bin The main boot app is: flash:/soft-version2.bin The backup boot app is: flash:/
130 Managing the device Device management includes monitoring the operating status of devices and configuring their running parameters. The configuration tasks in this document are order independent. You can perform these tasks in any order. Configuring the device name A device name identifies a device in a network an d works as the user view prompt at the CLI. For example, if the device name is Sysname, the user view prompt is . To configure the device name: Step Command Remarks 1. Enter system view. system-view N/A 2. Configure the device name. sysname sysname Optional. The default device name is HP. Changing the system time You must synchronize your device with a trusted time source by using NTP or changing the system time before you run it on the network. Network management depends on an accurate system time setting, because the timestamps of system mess ages and logs use the system time. In a small-sized network, you can manually set the system time of each device. Configuration guidelines You can change the system time by configuring the relative time, time zone, and daylight saving time. The configuration result depends on their configuration order (see Tabl e 20) . In the first column of this table, 1 represents the clock datetime command, 2 represents the clock timezone command, and 3 represents the clock summer-time c ommand. To veri f y the system ti me set ti ng, use the display clock command. This table assumes that the original system time is 2005/1/1 1:00:00. Table 20 System time configuration results Command Effective s ystem time Configuration example System time 1 date-time clock datetime 1:00 2007/1/1 01:00:00 UTC Mon 01/01/2007. 2 Original system time ± zone-offset clock timezone zone-time add 1 02:00:00 zone-time Sat 01/01/2005. 1, 2 date-time ± zone-offset clock datetime 2:00 2007/2/2 clock timezone zone-time add 1 03:00:00 zone-time Fri 02/02/2007.
131 Command Effective system time Configuration example System time 2, 1 date-time clock timezone zone-time add 1 clock datetime 3:00 2007/3/3 03:00:00 zone-time Sat 03/03/2007. 3 The original system time outside the daylight saving time range: The system time does not change until it falls into the daylight saving time range. clock summer-time ss one-off 1:00 2006/1/1 1:00 2006/8/8 2 01:00:00 UTC Sat 01/01/2005. The original system time in the daylight saving time range: The system time increases by summer-offset . clock summer-time ss one-off 00:30 2005/1/1 1:00 2005/8/8 2 03:00:00 ss Sat 01/01/2005. NOTE: If the original system time plus summer-offset is beyond the daylight saving time range, the original system time does not change. After you disable the daylight saving setting, the system time automatically decreases by summer-offset . 1, 3 date-time outside the daylight saving time range: date-time clock datetime 1:00 2007/1/1 clock summer-time ss one-off 1:00 2006/1/1 1:00 2006/8/8 2 01:00:00 UTC Mon 01/01/2007. date-time in the daylight saving time range: date-time + summer-offset clock datetime 8:00 2007/1/1 clock summer-time ss one-off 1:00 2007/1/1 1:00 2007/8/8 2 10:00:00 ss Mon 01/01/2007. NOTE: If the date-time plus summer-offset is outside the daylight saving time range, the system time equals date-time . After you disable the daylight saving setting, the system time automatically decreases by summer-offset . 3, 1 (date-time outside the daylight saving time range) date-time clock summer-time ss one-off 1:00 2007/1/1 1:00 2007/8/8 2 clock datetime 1:00 2008/1/1 01:00:00 UTC Tue 01/01/2008.
132 Command Effective system time Configuration example System time 3, 1 (date-time in the daylight saving time range) date-time – summer-offset outside the daylight saving time range: date-time – summer-offset clock summer-time ss one-off 1:00 2007/1/1 1:00 2007/8/8 2 clock datetime 1:30 2007/1/1 23:30:00 UTC Sun 12/31/2006. date-time – summer-offset in the daylight saving time range: date-time clock summer-time ss one-off 1:00 2007/1/1 1:00 2007/8/8 2 clock datetime 3:00 2007/1/1 03:00:00 ss Mon 01/01/2007. 2, 3 or 3, 2 Original system clock ± zone-offset outside the daylight saving time range: Original system clock ± zone-offset clock timezone zone-time add 1 clock summer-time ss one-off 1:00 2007/1/1 1:00 2007/8/8 2 02:00:00 zone-time Sat 01/01/2005. Original system clock ± zone-offset outside the daylight saving time range: Original system clock ± zone-offset + summer-offset clock timezone zone-time add 1 clock summer-time ss one-off 1:00 2005/1/1 1:00 2005/8/8 2 System clock configured: 04:00:00 ss Sat 01/01/2005. 1, 2 , 3 or 1, 3, 2 date-time ± zone-offset outside the daylight saving time range: date-time ± zone-offset clock datetime 1:00 2007/1/1 clock timezone zone-time add 1 clock summer-time ss one-off 1:00 2008/1/1 1:00 2008/8/8 2 02:00:00 zone-time Mon 01/01/2007. date-time ± zone-offset outside the daylight saving time range: date-time ± zone-offset + summer-offset clock datetime 1:00 2007/1/1 clock timezone zone-time add 1 clock summer-time ss one-off 1:00 2007/1/1 1:00 2007/8/8 2 04:00:00 ss Mon 01/01/2007. 2, 3, 1 or 3, 2, 1 date-time outside the daylight saving time range: date-time clock timezone zone-time add 1 clock summer-time ss one-off 1:00 2008/1/1 1:00 2008/8/8 2 clock datetime 1:00 2007/1/1 01:00:00 zone-time Mon 01/01/2007.
133 Command Effective system time Configuration example System time date-time in the daylight saving time range, but date-time – summer-offset outside the summer-time range: date-time – summer-offset clock timezone zone-time add 1 clock summer-time ss one-off 1:00 2008/1/1 1:00 2008/8/8 2 clock datetime 1:30 2008/1/1 23:30:00 zone-time Mon 12/31/2007. Both date-time and date-time – summer-offset in the daylight saving time range: date-time clock timezone zone-time add 1 clock summer-time ss one-off 1:00 2008/1/1 1:00 2008/8/8 2 clock datetime 3:00 2008/1/1 03:00:00 ss Tue 01/01/2008. Configuration procedure To change the system time: Step Command Remarks 1. Set the system time and date. clock datetime time date Optional. Available in user view. 2. Enter system view. system-view N/A 3. Set the time zone. clock timezone zone-name { add | minus } zone-offset Optional. Universal time coordinated (UTC) time zone by default. 4. Set a daylight saving time scheme. • Set a non-recurring scheme: clock summer-time zone -name one-off start-time start-date end-time end-date add-time • Set a recurring scheme: clock summer-time zone -name repeating start-time start-date end-time end-date add-time Optional. Use either command. By default, daylight saving time is disabled, and the UTC time zone applies. Enabling displaying the copyright statement The device by default displays the copyright statemen t when a Telnet or SSH user logs in, or when a console user quits user view. You can disable or enable the function as needed. The following is a sample copyright statement: ************************************************************************\ ****** * Copyright (c) 2010-2011 Hewlett-Packard Development Company, L.P. \ * * Without the owners prior written consent, \ * * no decompiling or reverse-engineering shall be allowed. \ * ************************************************************************\ ******
134 To enable displaying the copyright statement: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable displaying the copyright statement. copyright-info enable Optional Enabled by default. Changing the brand name An IRF fabric using HP, H3C, and 3Com member switches together might cause network management problems. For example, if an IRF fabric uses an HP swi t c h a s t h e m a s t e r m e m b e r swi t c h a n d u s e s a n H 3 C s w i t c h a s a s u b o r d i n a t e m e m b e r s w i t c h , t h e n e t w o r k m a n a g e m e n t s o f t w a r e i d e n t i f i e s t h e s w i t c h a s a n H P IRF fabric. Then, if the IRF fabric is rebooted and the H3C switch is elected as the master, the network management software identifies the IRF fabric as a new IRF fabric. To avoid this problem, perform this task to change the brand names of all member switches to the same. Table 21 lists the model matrix for HP, H3C, and 3C om switches. You can change brand names among them, except the models marked N/A. Before you change the brand name, you must get clear of the matrix for proper operation of the switches. Table 21 Brand matrix HP switch model H3C switch model 3COM switch model HP 5500-24G EI Switch with 2 Interface Slots S5500-28C-EI Switch 4800G 24-Port HP 5500-48G EI Switch with 2 Interface Slots S5500-52C-EI Switch 4800G 48-Port H P 5 5 0 0 - 2 4 G - S F P E I S w i t c h w i t h 2 Interface Slots S5500-28F-EI Switch 4800G 24-Port SFP HP 5500-24G-PoE+ EI Switch with 2 Interface Slots S5500-28C-PWR-EI Switch 4800G PWR 24-Port HP 5500-48G-PoE+ EI Switch with 2 Interface Slots S5500-52C-PWR-EI Switch 4800G PWR 48-Port HP 5500-24G SI Switch with 2 Interface Slots S5500-28C-SI N/A HP 5500-48G SI Switch with 2 Interface Slots S5500-52C-SI N/A HP 5500-24G-PoE+ SI Switch with 2 Interface Slots S5500-28C-PWR-SI N/A HP 5500-48G-PoE+ SI Switch with 2 Interface Slots S5500-52C-PWR-SI N/A Configuration preparation Before you change the brand name for an HP, H3C, or 3Com switch, prepare the proper Boot ROM and system software image file according to the model matrix as listed in Table 21. The following describes
135 the procedure for changing the brand name of an H3C or 3Com switch to HP. The procedure is the same for changing the brand names among HP, H3C, and 3Com switches. 1. Load the proper HP Boot ROM to the flash memory of the H3C or 3Com switch and use the HP Boot ROM to upgrade the Boot ROM of the switch. 2. Load the proper HP system software image file to the flash memory of the H3C or 3Com switch, specify the file as the main system software image file, and reboot the switch. 3. Execute the brand command and reboot the switch. NOTE: For HP 5500 EI and HP 5500SI use the bootrom update command to upgrade the Boot ROM. Configuration guidelines • After you change the brand name of a 3Com switch to HP or H3C, the default baudrate of the console port changes from 19200 to 9600. • T h e p o r t n u m b e r i n g r u l e f o r 3 C o m s w i t c h e s i s d i f f e r e n t f r o m t h a t f o r H P a n d H 3 C s w i t c h e s . A f t e r y o u change the brand name for a 3Com switch, the port numbers become inconsistent with the silkscreen marks. Configure the port (if necessary) according to the numbering rules for the models in the model matrix in Tabl e 21. • T he default settings for some features on 3Com switches are different from those on HP and H3C switches. After you change the brand name for a switch, the default settings for those features become the default settings of the target brand. Configuration procedure You can use the display brand command to display the brand names of the member switches. If any consistent brand names exist in the IRF fabric, change them to the same. To change brand name for a member switch: Step Command 1. Change the brand name for a member switch. brand { hp | h3c | 3com } [ slot slot-number ] 2. Reboot the member switch. reboot slot slot-number After you change the brand name for a member switch, the switch can use the later software versions for the new brand. NOTE: The default settings vary with different brands. Changing the brand name might affect the running configuration. After you change the brand name of a member switch, verify the configuration and re-configure the switch if necessary. Configuring banners Banners are messages that the system displays during user login.
136 The system supports the following banners: • Legal banner —Appears after the copyright or license statem ent. To continue login, the user must enter Y or press Enter. To quit the process, the user must enter N . Y and N are case-insensitive. • Message of the Day (MOTD) banner —Appears after the legal banner and before the login banner. • Login banner—Appears only when password or scheme authentication has been configured. • Incoming banner —Appears for Modem users. • Shell banner —Appears for non-Modem users. Banner message input modes You can configure a banner in one of the following ways: • Single-line input Input the entire banner in the same line as th e command. The start and end delimiters for the banner must be the same but can be any visible character. The input text, including the command keywords and the delimiters cannot exceed 510 characters. In this mode, do not press Enter before you input the end delimiter. For example, you can configure the shell banner “Have a nice day.” as follows: system-view [System] header shell %Have a nice day.% • Multiple-line input Input message text in multiple lines. In th is approach, the message text can be up to 2000 characters. Use one of the following meth ods to implement multi-line input mode: { Method 1 —Press Enter after the last command keyword. At the system prompt, enter the banner message and end with the delimiter char acter %. For example, you can configure the banner “Have a nice day. Please in put the password.” as follows: system-view [System] header shell Please input banner content, and quit with the character %. ――System prompt Have a nice day. Please input the password.% { Method 2 — A f t e r yo u t yp e t h e l a s t c o m m a n d key wo rd, type any character as the start delimiter for the banner message and press Enter. At the system prompt, type the banner message and end the last line with a delimiter that is the sa me as the start delimiter. For example, you can configure the banner “Have a nice day. Pl ease input the password.” as follows: system-view [System] header shell A Please input banner content, and quit with the character A. ――System prompt Have a nice day. Please input the password.A { Method 3 —After you type the last keyword, type the start delimiter and part of the banner message and press Enter. At the system prompt, enter the rest of the banner and end the last line with a delimiter that is th e same as the start delimiter. In this approach, you can use any character as the start and end delimiters but must make sure that it is not the same as the end character of the message text in the first line. For example, you can configure the banner “Have a nice day. Please input the password.” as follows: system-view [System] header shell AHave a nice day.
137 Please input banner content, and quit with the character A. ――System prompt Please input the password.A Configuration procedure To configure a banner: Step Command Remarks 1. Enter system view. system-view N/A 2. Configure the incoming banner. header incoming text Optional 3. Configure the login banner. header login text Optional 4. Configure the legal banner. header legal text Optional 5. Configure the shell banner. header shell text Optional 6. Configure the MOTD banner. header motd text Optional Configuring the exception handling method You can configure the device to handle system exceptions in one of the following methods: • reboot —The device automatically reboots to recover from the error condition. • maintain—The device stays in the error condition so you can collect complete data, including error messages, for diagnosis. In this approach , you must manually reboot the device. To configure the exception handling method: Step Command Remarks 1. Enter system view. system-view N/A 2. Configure the exception handling method. system-failure { maintain | reboot } Optional. By default, the system reboots when an exception occurs. NOTE: In an IRF fabric, the exception handling method appl ies to all member switches, but the member switches handle system exceptions independen tly without affecting one another. Rebooting the device
138 CAUTION: • A reboot can interrupt network services. • To avoid data loss, use the save command to save the current configuration before a reboot. • Use the display startup and display boot-loader commands to verify that you have correctly set the startup configuration file and the main system software image file. If the main system software image file has been corrupted or does not exist, the device cannot reboot. You must re-specify a main system software image file, or power off the device and then power it on so the system can reboot with the backup system software image file. You can reboot the device in one of the following ways to recover from an error condition: • Reboot the device immediately at the CLI. • At the CLI, schedule a reboot to occur at a specific time and date or after a delay. • Power off and then power on the device. This me thod might cause data loss and hardware damage, and is the least preferred method. • Reboot at the CLI enables easy remote device maintenance. Rebooting devices immediately at the CLI To reboot a device, perform the following task in user view: Task Command Remarks Reboot a switch or all IRF member switches immediately. reboot [ slot slot-number ] If you do not specify any IRF member ID for the slot-number argument, all IRF member switches reboot. Scheduling a device reboot The switch supports only one device reboot schedule. If you configure the schedule reboot delay command multiple times, the last configuration takes effect. The schedule reboot at command and the schedule reboot delay command overwrite each other, and whichever is configured last takes effect. For data security, if you are performing file operatio ns at the reboot time, the system does not reboot. To schedule a device reboot, perform the following task in user view: Task Command Remarks Schedule a reboot. • Schedule a reboot to occur at a specific time and date: schedule reboot at hh:mm [ date ] • Schedule a reboot to occur after a delay: schedule reboot delay { hh:mm | mm } Use either command. The scheduled reboot function is disabled by default. Changing any clock setting can cancel the reboot schedule.