Tsp Load Sharing - HP ProCurve 9304M Installation And Configuration Manual

Management redundancy is described in "Using Redundant Management Modules" on page 3-1. Management
redundancy using a pair of T-Flow modules works as described in the chapter, with the following important
differences:
• The TSP CPUs on both modules actively process traffic. Only the MP CPU on the standby module is in
backup mode. The TSP CPUs on the standby module actively process traffic.
• The TSP CPU flash code is not automatically synchronized. To synchronize the flash code on the TSP
CPUs, use the vm copy tftp flash command, described in "File Synchronization Between the Active and
Standby Redundant Management Modules" on page 3-10. The flash code on the CPU is automatically
synchronized.
• If you use a pair of T-Flow management modules in a chassis for redundancy, the device does not reassign
the forwarding modules assigned to the TSP CPUs on the active module to the other module following a hot
swap. See the next section.
Management Redundancy and Hot Swap
If you use a pair of T-Flow management modules in a chassis for redundancy, the device does not reassign the
forwarding modules assigned to the TSP CPUs on the active module to the other module following a hot swap.
This is true in the following cases:
• If you insert a standby T-Flow into an active device, the device does not replicate the assignments of the
forwarding modules to the TSP CPUs on the standby module. To work around this issue, use the vm-map
command to assign the forwarding modules to the TSP CPUs on the standby module after you insert the
module.
• If you remove a standby T-Flow module that has taken over forwarding on an active device, the forwarding
modules assigned to the TSP CPUs on the standby module are not reassigned to the TSP CPUs on the
default active module. To avoid traffic interruption, use the vm-map command to assign the forwarding
modules to the TSP CPUs on the default active T-Flow module before removing the standby module .
To list the TSP CPU assignments, enter the following command: show vm-map
To assign forwarding modules to TSP CPUs, enter the following command:
vm vm-map <from-slotnum> vm-slot <to-slotnum> vm-cpu <cpunum>
The <from-slotnum> parameter specifies the slot that contains the forwarding module.
The <to-slotnum> parameter specifies the slot that contains the T-Flow.
The <cpunum> parameter specifies the VSM CPU on <to-slotnum> that will perform the processing. The VSM
CPUs are numbered from 1 – 3.

TSP Load Sharing

The T-Flow optimizes performance by distributing responsibility for the forwarding modules across the TSPs, so
that each TSP has sole responsibility for a given forwarding module and the modules are as evenly distributed
across the TSPs in terms of bandwidth.
When you power on or reset the T-Flow, the module assigns each of the forwarding modules to a TSP according
to each module's weight. A forwarding module's weight is a number that represents its total forwarding capacity.
The weight is measured in units of 1 for each 100 Mbps. For example, Table 4.1 shows the weights for some
common forwarding module types. Notice that the weight for 10/100 modules is based on the higher bandwidth
(100 Mbps instead of 10 Mbps) for all ports.
Using the T-Flow Redundant Management Module
4 - 3