HP StorageWorks Fabric OS 6.2 administrator guide (5697-0016, May 2009)

Fabric OS 6.2 administrator guide 439
Adding a monitor to an F_Port master port
1. Connect to the switch and log in using an account assigned to the admin role.
2. Enter the perfAddEEMonitor command.
switch:admin> perfaddeemonitor 4 0x010400 0x020800
Adding monitor to the master port <port no.> of the F-Port Trunk.
where 4 is a slave port of the F_Port Trunk.
If you attempt to install a monitor on a slave port of an F_Port trunk and the same monitor is already
installed on the corresponding master, the following message is displayed.
switch:admin> perfaddeemonitor 4 0x010400 0x020800
Similar monitor already exists on the master port <port no.> of the F-Port
Trunk
where 4 is a slave port of the F_Port Trunk.
Fabric Watch allows you to monitor traffic flow through specified ports on the switch and send alerts when
the traffic exceeds or drops below configured thresholds. Fabric Watch monitors only the trunk masters and
not the slave ports.
Fabric OS CLI allows you to display throughput information for all ports on the switch. Data is displayed in
8 or 16 columns, one column per port plus one column that displays the total for these ports. Results
display every second or over the specified interval, until Enter, Ctrl-C, or Ctrl-D is pressed. See the Fabric
OS Command Reference for additional information.
Displaying port throughput performance information for all ports on the switch
1. Connect to the switch and log in using an account assigned to the admin role.
2. Enter the portPerfShow command.
portperfshow [interval]
where the interval is the number of seconds between each data-gathering sample (the default is
one sample every second).
3. Record the traffic flow for each port participating in an ISL.
4. Repeat step 1 through step 3 for each switch in the fabric until all ISL traffic flow is captured.
In a large fabric, it may be necessary only to identify and capture the key ISLs. However, you may want
to continue this process throughout the day (or an entire work cycle) to capture varying traffic patterns
under different conditions.
The following example shows a switch without trunking, and indicates that ports 0 through 2 are
underutilized and ports 4 and 5 are congested:
switch:admin> portperfshow
01234567 Total
--------------------------------------------------------------------
0 0 0 145m204m202m0168m 719
0 0 0 145m206m208m0186m 745