Displaying Port Throughput Performance - HP A7533A - Brocade 4Gb SAN Switch Base Administrator's Manual

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
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. Use the fwConfigure command to display and modify the Fabric
Watch configuration. Because the index is the same for all ports in the trunk, Fabric Watch shows the
master trunk port counter values for all slaves when you issue the fwConfigure command. You can
issue the fwPortDetailShow command to display the overall status of specific ports. See the Fabric
Watch Administrator's Guide for additional information.
• The Fabric OS CLI portPerfShow command allows you to display throughput information for all
ports on the switch. Data displays 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. This command displays the number of bytes received plus the number of
bytes transmitted per interval. Throughput values are displayed as either bytes, kilobytes (k), megabytes
(m), or gigabytes (g). Values are always rounded down.

Displaying port throughput performance

1. Connect to the switch and log in as admin.
2. Enter the following command:
portperfshow [interval]
where 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
In a large fabric, it may be necessary to only 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 under
utilized and ports 4 and 5 are congested:
switch:admin> portperfshow
0
--------------------------------------------------------------------
0
0
The following example shows traffic flowing through a trunking group (ports 5, 6, and 7). After port 6 fails,
traffic is redistributed over the remaining two links in the group, ports 5 and 7:
switch:admin> portperfshow
0
--------------------------------------------------------------------
0
0 0
0 0
360 Administering ISL Trunking
through step 3 for each switch in the fabric until all ISL traffic flow is captured.
1 2 3 4
0 0 145m 204m
0 0 145m 206m
1 2 3 4
0 0 0 0
0 0 0
0 0 0
0x010400 0x020800
5 6 7
202m 0 168m
208m 0 186m
5 6 7
145m 144m 145m
144m 143m 144m
162m 0 162m
Total
719
745
Total
434
431
324