The HBAnyware Utility User Manual Page 59
TraceBufSiz=n TraceBufSiz sets the size in bytes for the internal driver trace buffer.
The internal driver trace buffer acts as an internal log of the driver's
activity.
Value: 250,000 - 2,000,000 or 0x3D090 - 0x1E8480 (hex).
Default = 250,000 (0x3D090)
Reboot
Table 2: Storport Miniport Topology Reference
Topology Description Value
Private Loop
Operation Only FC-AL topology is used. After successful loop initialization, the driver
attempts login with FL_PORT.
• If FL_PORT login is successful, public loop operation is employed.
• If FL_PORT login is unsuccessful, private loop mode is entered. If a fabric
is not discovered and the topology is arbitrated loop, the driver operates in
private loop mode using the following rules:
• If an FC-AL device map is present, each node described in the map is
logged and verified as a target.
• If an FC-AL device map is not present, logins are attempted with all 126
possible FC-AL addresses. LPGO/PRLO are also handled by the driver.
Reception of either causes a new discovery or login to take place.
0
Switched Fabric
Operation Only switched F_PORT(point-to-point [pt.-to-pt.]) login is successful, fabric
mode is used.
• If F_PORT login is unsuccessful, N_PORT-to-N_PORT direct connection
topology will be used.
• If a switch is discovered, the driver performs the following tasks:
• FL_PORT login (Topology = 0;).
• F_PORT login (Topology =1;).
• Simple Name Server login.
• State Change Registration.
• Symbolic Name Registration.
• FCP Type Registration if RegFcpType is set to 1.
• The driver logs out and re-logs in. The name server indicates that
registration is complete.
• Simple Name Server Query for devices (the registry parameter SnsAll
determines whether all N_Ports are requested (SnsALL=1;) or only SCSI
FCP N_Ports (SnsAll=0; default)
• Discovery/device creation occurs for each target device described by the
Name Server.
• The driver handles RSCN and LOGO/PRLO. Reception of either causes
new discovery/logins to take place.
1
*FC-AL attempt
first, then attempt
pt.-to-pt.
• Topology fail-over requires v3.20 firmware or higher. If firmware does not
support topology fail-over, options 0 and 2 are analogous. Options 1 and 3
are analogous.
2
*pt.-to-pt. fabric
attempt first, then
attempt FC-AL.
• Topology fail-over requires v3.20 firmware or higher. If firmware does not
support topology, fail-over options 0 and 2 are analogous. Options 1 and 3
are analogous.
3
Table 1: Storport Miniport Driver Parameters (Continued)
Parameter Definitions Activation
Requirement