HP Brocade 8/12c HP Fabric OS 6.2.2f Release Notes (5697-1756, February 2012) - Page 27

Fabric Watch, Core Blade status reporting modification, Port Fencing

Get HP Brocade 8/12c PDF manuals and user guides View all HP Brocade 8/12c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 27 highlights

(saved on the switch with pre-Fabric OS 6.2.0 code) is merged with a switch with the same alias member WWN in lower case characters, the merge fails, because the switches do not recognize these zoning configurations as being the same. For more information and workaround solutions, see the latest Fabric OS Administrator Guide. Fabric Watch Core Blade status reporting modification Fabric Watch has been modified so that Core blade status reporting matches CP blade reporting, rather than status reported by port blades. Table 6 (page 27) shows the changes. Table 6 Fabric Watch Blade Status reporting FE Area CP Core blade Port blade Threshold Down Marginal 0 1 0 1 0 1 Original behavior if one New behavior if one blade is blade is absent or off absent or off Switch/Standby CP state No change. will be marginal. Switch/Core Blade state Switch/Core Blade state will be will be healthy. marginal. Switch/Blade state will be No change. healthy. NOTE: If any type of blade goes to a faulty state, the switch/blade state will be marginal. Port Fencing • When the Port Fencing trigger threshold is exceeded for ITW, LR, or CRC errors, the first set of errors detected on an active link that meet the custom high threshold level set by the user (or the default threshold level of approximately 6 seconds) is always ignored to account for expected link transition errors. The port is disabled only upon detection of a second set of errors; that is, the next time the user-set threshold level (or default threshold level) is reached. This prevents a port from being disabled due to normal link transition behaviors. • When using the Port Fencing feature, you must first run the fwalarmsfilterset command. This command enables the port and allows you to receive Port Fencing messages. • Port Fencing can be inadvertently disabled from Web Tools. This occurs when you first open the Fabric Watch configuration window and then select the SNMP Trap check box in the Above row. Making this change in Web Tools disables Port Fencing. If this happens, you must re-enable the Port Fencing bit from the CLI. The Port Fencing feature is not supported for Loss of Sync (LOS) and Link Failure (LF) areas of Port/F-port/E-port classes. Other important notes and recommendations 27

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
(saved on the switch with pre-Fabric OS 6.2.0 code) is merged with a switch with the same alias
member WWN in lower case characters, the merge fails, because the switches do not recognize
these zoning configurations as being the same. For more information and workaround solutions,
see the latest
Fabric OS Administrator Guide
.
Fabric Watch
Core Blade status reporting modification
Fabric Watch has been modified so that Core blade status reporting matches CP blade reporting,
rather than status reported by port blades.
Table 6 (page 27)
shows the changes.
Table 6 Fabric Watch Blade Status reporting
New behavior if one blade is
absent or off
Original behavior if one
blade is absent or off
Threshold
FE Area
Marginal
Down
No change.
Switch/Standby CP state
will be marginal.
1
0
CP
Switch/Core Blade state will be
marginal.
Switch/Core Blade state
will be healthy.
1
0
Core blade
No change.
Switch/Blade state will be
healthy.
1
0
Port blade
NOTE:
If any type of blade goes to a faulty state, the switch/blade state will be marginal.
Port Fencing
•
When the Port Fencing trigger threshold is exceeded for ITW, LR, or CRC errors, the first set
of errors detected on an active link that meet the custom high threshold level set by the user
(or the default threshold level of approximately 6 seconds) is always ignored to account for
expected link transition errors. The port is disabled only upon detection of a second set of
errors; that is, the next time the user-set threshold level (or default threshold level) is reached.
This prevents a port from being disabled due to normal link transition behaviors.
•
When using the Port Fencing feature, you must first run the
fwalarmsfilterset
command.
This command enables the port and allows you to receive Port Fencing messages.
•
Port Fencing can be inadvertently disabled from Web Tools. This occurs when you first open
the Fabric Watch configuration window and then select the
SNMP Trap
check box in the
Above row. Making this change in Web Tools disables Port Fencing. If this happens, you must
re-enable the Port Fencing bit from the CLI. The Port Fencing feature is not supported for Loss
of Sync (LOS) and Link Failure (LF) areas of Port/F-port/E-port classes.
Other important notes and recommendations
27