Home > HP > Printer > HP 5500 Ei 5500 Si Switch Series Configuration Guide

HP 5500 Ei 5500 Si Switch Series Configuration Guide

Add to Favourites
    Download as PDF Print this page Share this page

    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+.

    View all the pages
    Page
    of 2513
    Add page 151 to Favourites
    image text
    Enable zoom 
    							 139 
Scheduling jobs 
You can schedule a job to automatically run a command or a set of commands without administrative 
interference. The commands in a job are polled every minute. When the scheduled time for a command 
is reached, the job automatically executes the command. If a confirmation is required while the 
command is running, the system automatically inputs Y or Ye s . If characters are required, the system 
automatically inputs a default character string, or in puts an empty character string when there is no 
default character string. 
Job configuration approaches 
You can configure jobs in a non-modular or modular approach. Use the non-modular approach for a 
one-time command execution and use non-modular approach for complex maintenance work.  
Table 22  A comparison of non-modular and modular approaches 
Comparison item  Scheduling a job in the non-modular 
a
pproach 
Scheduling a job in the modular 
a
pproach 
Configuration method  Configure all elements in one command Separate job, view, and time settings. 
Can multiple jobs be 
configured?  No Yes 
Can a job have multiple 
commands? No 
If you use the 
schedule job command 
repeatedly, only the last configuration 
takes effect.   Yes 
You can use the time 
command in job 
view to configure commands to be 
executed at different time points.  
Supported views  User view and system view. In the 
schedule job 
command, shell represents 
user view, and system represents system 
view.  All views. In the 
time command, 
monitor represents user view. 
Supported  commands  Commands in user view and system view Commands in all views. 
Can a job be repeatedly 
executed?   No 
Yes 
Can a job be saved to the 
configuration file? No 
Yes 
 
Configuration guidelines 
•
  To have a job successfully run a command, check that the specified view and command are valid. 
The system does not verify their validity.  
•   The configuration interface, view, and user status that you have before job execution restores even 
if the job has run a command that changes the user interface (for example,  telnet, ftp, and  ssh2), 
the view (for example,  system-view and quit), or the user status (for example,  super).  
•   The jobs run in the background without displaying any messages except log, trap and debugging 
messages. 
•   In the modular approach:  
{ Every job can have only one view and up to 10 commands. If you specify multiple views, the 
one specified the last takes effect.
    Add page 152 to Favourites
    image text
    Enable zoom 
    							 140 
{ Input a view name in its complete form. Most commonly used view names include  monitor for 
user view,  system for system view, GigabitEthernet x/x/x, and Ten-GigabitEthernet x/x/x for 
Ethernet interface view, and  Vlan-interfacex for VLAN interface view.  
{ The time ID ( time-id) must be unique in a job. If two time and command bindings have the same 
time ID, the one configured last takes effect.  
Scheduling a job in the non-modular approach 
Perform one of the following commands in user view to schedule a job:  
Step Command Remarks 
Schedule a job.  •
 
Schedule a job to run a 
command at a specific time: 
schedule job at  time [ date ] 
view  view command  
• Schedule a job to run a 
command after a delay: 
schedule job delay  time view 
view  command   Use either command. 
NOTE:
 
• If you execute the  schedule job 
command repeatedly, the last 
configuration takes effect. 
•  Changing any clock setting can 
cancel the job set by using the 
schedule job  command. 
 
Scheduling a job in the modular approach 
To configure a scheduled job:  
Step Command Remarks 
1.  Enter system view.  system-view  N/A 
2.  Create a job and enter job 
view.   job 
job-name  N/A 
3.  Specify the view in which 
the commands in the job 
run.   view
 view-name   You can specify only one view for 
a job. The job executes all 
commands in the specified view.
 
4.
  Add commands to the job.  
• Configure a command to run at a 
specific time and date: 
time  time-id  at time date  command  
command  
• Configure a command to run at a 
specific time: 
time  time-id  { one-off  | repeating } 
at  time  [  month-date  month-day | 
week-day  week-daylist  ] command 
command  
• Configure a command to run after a 
delay:  
time  time-id  { one-off  | repeating  } 
delay  time command  command  Use any of the commands. 
NOTE: 
Changing a clock setting does not 
affect the schedule set by using the 
time
 at  or  time delay  command.
    Add page 153 to Favourites
    image text
    Enable zoom 
    							 141 
Disabling Boot ROM access 
By default, anyone can press Ctrl+B during startup to enter the Boot menu and configure the Boot ROM. 
To protect the system, you can disable Boot ROM ac cess so the users can access only the CLI.  
You can also set a Boot ROM password the first time you access the Boot menu to protect the Boot ROM. 
To view Boot ROM accessibility status, use the  display startup command. For more information about the 
display startup  command, see Fundamentals Command Reference . 
Follow the step below to disable Boot ROM access: 
 
Task Command Remarks 
Disable Boot ROM access.  undo startup bootrom-access 
enable  By default, Boot ROM access is 
enabled. 
Available in user view. 
 
Configuring the port status detection timer 
Some protocols might shut down ports under specific
 circumstances. For example, MSTP shuts down a 
BPDU guard enabled port when the port receives a BPDU. Then, the device starts the detection timer. If 
the port is still down when the detection timer expires, the port quits the shutdown status and resumes its 
actual physical status.  
To configure the port status detection timer: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Configure the port status 
detection timer.  shutdown-interval
 time  Optional. 
The detection timer is 30 seconds 
by default. 
 
Configuring temperature thresholds for a device 
You can set the temperature thresholds to
 monitor the temperature of a device. 
The temperature thresholds include lowe r threshold and warning threshold.  
When the device temperature drops below the lower  threshold or reaches the warning threshold, the 
device logs the event and outputs a log message and a trap. 
When the device temperature reaches the alarming thre shold, the device logs the event and outputs a log 
message and a trap repeatedly. 
When the device temperature reaches the shut-down threshold, the device logs the event, outputs a log 
message and a trap, and automatically shuts down. 
To configure temperature thresholds for an IRF member device:
    Add page 154 to Favourites
    image text
    Enable zoom 
    							 142 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Configure temperature 
thresholds for an IRF 
member device.  temperature-limit 
slot 
slot-number  hotspot  
sensor-number  lowerlimit 
warninglimit    Optional. 
By default, the lower threshold is –5°C 
(23°F), and the warning threshold is 55°C 
(131°F). 
The warning threshold must be higher than 
the lower threshold. 
 
Clearing unused 16-bit interface indexes 
The device must maintain persistent 16-bit interf
ace indexes and keep one interface index match one 
interface name for network management. After deleting  a logical interface, the device retains its 16-bit 
interface index so the same index can be assigned  to the interface at interface re-creation.  
To avoid index depletion causing interface creation fa ilures, you can clear all 16-bit indexes that have 
been assigned but not in use. The operation does not  affect the interface indexes of the interfaces that 
have been created but the indexes assigned  to re-recreated interfaces might change.  
 
 IMPORTANT: 
A confirmation is required when you execute this command. The command will not run if you fail to make 
a confirmation within 30 seconds or enter 
N to cancel the operation.  
To clear unused 16-bit interface indexes, perform the following task in user view:  
Task Command Remarks 
Clear unused 16-bit interface 
indexes.  reset unused porttag In an IRF fabric, the command 
applies to all member switches.  
 
Verifying and diagnosing transceiver modules 
You can verify the genuineness of a transceiver module in the following ways:  
•
  Display the key parameters of a transceiver module , including its transceiver type, connector type, 
central wavelength of the transmit laser, transfer distance and vendor name. 
•   Display its electronic label. The el ectronic label is a profile of the transceiver module and contains 
the permanent configuration including the serial  number, manufacturing date, and vendor name. 
The data is written to the storage comp onent during debugging or testing.  
To verify transceiver modules, perform the following tasks in any view: 
 
Task Command 
Display key parameters of transceiver 
modules.  display transceiver 
interface [ interface-type 
interface-number  ] [ | { begin |  exclude | include  } 
regular-expression  ]
    Add page 155 to Favourites
    image text
    Enable zoom 
    							 143 
Task Command 
Display electronic label data for transceiver 
modules. display transceiver manuinfo
 interface  [ interface-type 
interface-number  ] [ | { begin |  exclude | include  } 
regular-expression  ] 
 
Diagnosing transceiver modules 
The device provides the alarm function and digital diagnosis function for transceiver modules. When a 
transceiver module fails or inappropriately operates, you can check for alarms present on the transceiver 
module to identify the fault source or examine the key parameters monitored by the digital diagnosis 
function, including the temperature, voltage, laser bias current, TX power, and RX power.  
To diagnose transceiver modules, perform the following tasks in any view: 
 
Task Command 
Display alarms present on transceiver modules.  display transceiver alarm 
interface [ interface-type 
interface-number  ] [ | { begin |  exclude | include  } 
regular-expression  ] 
Display the present measured  values of the digital 
diagnosis parameters for pluggable transceivers.  display transceiver diagnosis interface
 [ interface-type 
interface-number  ] [ | { begin |  exclude | include  } 
regular-expression  ] 
 
Displaying and maintaining device management 
For diagnosis or troubleshooting, you can use separate  display commands to collect running status data 
module by module, or use the  display diagnostic-information command to bulk collect running data for 
multiple modules. The  display diagnostic-information  command equals this set of commands:  display 
clock , display version , display device , and display current-configuration .  
 
Task Command Remarks 
Display system version 
information.  display version
 [ | { begin |  exclude | 
include  } regular-expression  ]  Available in any view 
Display the system time and date.  display clock [ 
| { begin |  exclude | 
include  } regular-expression  ]  Available in any view 
Display or save operating statistics 
for multiple feature modules.  display diagnostic-information
 [ | 
{  begin |  exclude  | include  } 
regular-expression  ]  Available in any view 
Display alarm information.  display alarm 
[ slot  slot-number  ] [ | 
{  begin |  exclude | include  } 
regular-expression  ]  Available in any view
    Add page 156 to Favourites
    image text
    Enable zoom 
    							 144 
Task Command Remarks 
Display CPU usage statistics. display cpu-usage [ slot 
slot-number 
[  cpu  cpu-number  ] ] [ | { begin |  exclude 
|  include  } regular-expression  ] 
display cpu-usage  entry-number [ offset ] 
[ verbose  ] [ slot slot-number  ] [  cpu  
cpu-number  ] [ | { begin |  exclude | 
include  } regular-expression  ] Available in any view 
Display historical CPU usage 
statistics in a chart. 
display cpu-usage history 
[ task  task-id  ] 
[  slot slot-number  [ cpu cpu-number ] ] [ |  
{  begin |  exclude | include  } 
regular-expression  ]  Available in any view 
Display hardware information. 
display device [[ slot 
slot-number ] | 
verbose  ] [ | { begin |  exclude | 
include  } regular-expression ]  Available in any view 
Display the electronic label data 
for the device.  display device manuinfo
 [ slot 
slot-number  ] [ | { begin |  exclude | 
include  } regular-expression  ] Available in any view 
Display device temperature 
statistics.  display environment
 [ slot slot-number  ] 
[ |  { begin |  exclude | include } 
regular-expression  ]  Available in any view 
Display the operating states of fan 
trays.  display fan [ slot 
slot-number [ fan-id ] ] 
[ |  { begin |  exclude | include } 
regular-expression  ]  Available in any view 
Display memory usage statistics.  display memory
 [ slot slot-number [ cpu  
cpu-number  ] ] [ | { begin |  exclude | 
include  } regular-expression ]  Available in any view 
Display power supply information.  display power [ slot 
slot-number 
[ power-id  ] ] [ | { begin |  exclude | 
include  } regular-expression ]  Available in any view 
Display the mode of the last reboot.  display reboot-type 
[ slot slot-number  ] 
[ |  { begin |  exclude | include } 
regular-expression  ]  Available in any view 
Display RPS status information.  display rps
 [ slot slot-number  [ rps-id ] ] 
[ |  { begin |  exclude | include  } 
regular-expression  ]  Available in any view 
Display the configuration of the job 
configured by using the 
schedule 
job  command.  display schedule job
 [ | { begin  | 
exclude  | include  } regular-expression  ]
 Available in any view 
Display the device reboot setting.  display schedule reboot
 [ | { begin  | 
exclude  | include  } regular-expression ] Available in any view 
Display the configuration of jobs 
configured by using the  job 
command.  display job
 [ job-name  ] [ | { begin  | 
exclude  | include  } regular-expression ]
 Available in any view 
Display the exception handling 
method.  display system-failure [ |
 { begin | 
exclude  | include  } regular-expression ]
 Available in any view
    Add page 157 to Favourites
    image text
    Enable zoom 
    							 145 
Automatic configuration introduction 
Automatic configuration enables a device without any configuration file to automatically obtain and 
execute a configuration file during startup. Automatic configuration simplifies network configuration, 
facilitates centralized management, and reduces maintenance workload.  
To implement automatic configuration, the network administrator saves configuration files on a server 
and a device automatically obtains and executes a specific configuration file. 
Typical application scenario 
Figure 53 Network diagram 
 
 
As shown in Figure 53, the de vice implements automatic configuration with the cooperation of the 
following servers: 
•   DHCP server —Assigns an IP address and other configuration parameters such as the configuration 
file name, TFTP server IP address, and DNS server IP address to the device. 
•   TFTP server —Saves files needed in automatic configuration. The device gets the files needed from 
t h e  T F T P  s e r ve r,  s u ch  a s  t h e  h o s t  n a m e  fi l e  t h a t   saves mappings between host IP addresses and host 
names, and the configuration file. 
•   DNS server —Resolves between IP addresses and host names. In some cases, the device resolves its 
IP address to the corresponding host name through the DNS server, and then uses the host name to 
request the configuration file with the same name (hostname.cfg)  from the TFTP server. If the device 
gets the domain name of the TFTP server from the DHCP response, the device can also resolve the 
domain name of the TFTP server to the IP address of the TFTP server through the DNS server. 
If the DHCP server, TFTP server, DNS server, and the device are not in the same network segment, you 
need to configure the DHCP relay agent on the gateway, and configure routing protocols to enable each 
server and the device to reach one another.
    Add page 158 to Favourites
    image text
    Enable zoom 
    							 146 
How automatic configuration works 
Automatic configuration works in the following manner: 
1. During startup, the device sets the first up interface (if up Layer 2 Ethernet ports exist, the VLAN 
interface of the default VLAN of the Ethernet ports is selected as the first up interface. Otherwise, 
the up Layer 3 Ethernet interface with the smallest  interface number is selected as the first up 
interface) as the DHCP client to request parameters from the DHCP server, such as an IP address 
and name of a TFTP server, IP address of a  DNS server, and the configuration file name. 
2. After getting related parameters, the device sends a TFTP request to  obtain the configuration file 
from the specified TFTP server and executes the configuration file. If the client cannot get such 
parameters, it uses the factory defaults. 
To implement automatic configuration, you must configure the DHCP server, DNS server, and TFTP server, 
but you do not need to perform any configuration on  the device that performs automatic configuration. 
Before starting the device, connect only the interface needed in automatic configuration to the network. 
Automatic configuration work flow 
Figure 54  shows the work flow of automatic configuration. 
Figure 54  Automatic configuration work flow
    Add page 159 to Favourites
    image text
    Enable zoom 
    							 147 
Using DHCP to obtain an IP address and other configuration 
information 
Address acquisition process 
As previously mentioned, a device sets the first up interface as the DHCP client during startup. The DHCP 
client broadcasts a DHCP request, where the Option 55 field specifies the information that the client 
wants to obtain from the DHCP server such as the configuration file name, domain name and IP address 
of the TFTP server, and DNS server IP address. 
After receiving the DHCP response from the DHCP server, the device obtains the IP address and resolves 
the following fields in the DHCP response: 
•   Option 67 or the file field —Obtains the configuration file name. The device resolves Option 67 first. 
If Option 67 contains the configuration file name, the device does not resolve the file field. If not, the 
device resolves the file field.   
•   Option 66 —Obtains the TFTP server domain name 
•   Option 150 —Obtains the TFTP server IP address 
•   Option 6 —Obtains the DNS server IP address.  
If no response is received from the DHCP server, the device removes the temporary configuration and 
starts up with the factory defaults. 
The temporary configuration contains two parts: the  configuration made on the interface through which 
automatic configuration is performed, and the  ip host command in the host name file (For more 
information about the  ip host command, see  Layer 3—IP Services Command Reference. ). The temporary 
configuration is removed by executing the corresponding  undo commands. 
For more information about DHCP, see  Layer 3—IP Services Configuration Guide.  
Principles for selecting an address pool on the DHCP server 
The DHCP server selects IP addresses and other network configuration parameters from an address pool 
for clients. DHCP supports the fo llowing types of address pools: 
•   Dynamic address pool —A dynamic address pool contains a range of IP addresses and other 
parameters that the DHCP server dynamically assigns to clients. 
•   Static address pool —A static address pool contains the binding of an IP address and a MAC 
address (or a client ID). The DHCP server assi gns the IP address of the binding and specific 
configuration parameters to a requesting client whose MAC address or ID is contained in the 
binding. In this way, the client can get a fixed IP address. 
Select address pools by using one of the following methods: 
•   If devices use the same configuration file, you can configure a dynamic address pool on the DHCP 
server to assign IP addresses and the same configuration parameters (for example, configuration 
f i l e  n a m e )  t o  t h e  d e v i c e s .  I n  t h i s  c a s e ,  t h e  c o n f i g uration file can only contain common configurations 
of the devices, and the specific configurations of each device need to be performed in other ways. 
For example, the configuration file can enable Telnet  and create a local user on devices so that the 
administrator can Telnet to each device to perfor m specific configurations (for example, configure 
the IP address of each interface). 
•   If devices use different configuration files, you n eed to configure static address pools to make sure 
each device can get a fixed IP address and a specific configuration file. With this method, no more 
configuration is required for the devices.
    Add page 160 to Favourites
    image text
    Enable zoom 
    							 148 
To configure static address pools, you must obtain corresponding client IDs. To obtain a device’s client ID, 
use the display dhcp server ip-in-use command to display address binding information on the DHCP 
server after the device obtains its IP address through DHCP. 
Obtaining the configuration file from the TFTP server 
A device can obtain the following files from the TFTP server during automatic configuration: 
•   The configuration file specified by the Option 67 or file field in the DHCP response. 
•   The host name file named network.cfg that stores  mappings between IP addresses and host names. 
For example, the host name file can include the following: 
 ip host host1 101.101.101.101 
 ip host host2 101.101.101.102 
 ip host client1 101.101.101.103 
 ip host client2 101.101.101.104 
 
  IMPORTANT: 
•
  There must be a space before the keyword  ip host. 
•   The host name of a device saved in the host name file must be the same as the confi
guration file name
of the device, and can be identical with or different from that saved in the DNS server. 
 
•   The configuration file for the device, which is named  hostname.cfg (hostname  is the host name of 
the device). For example, if the host name of a device is  aaa, the configuration file for the device is 
named aaa.cfg. 
•   The default configuration file named  device.cfg.
    All HP manuals Comments (0)

    Related Manuals for HP 5500 Ei 5500 Si Switch Series Configuration Guide