HP StorageWorks 1606 Brocade Fabric Watch Administrator's Guide v6.3.0 (53-100 - Page 29

Switch policies, Virtual Fabric support, Port persistence

Get HP StorageWorks 1606 - Extension SAN Switch PDF manuals and user guides View all HP StorageWorks 1606 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 29 highlights

Switch policies 1 Switch policies Switch policies are a series of rules that define specific health states for the overall switch. Fabric OS interacts with Fabric Watch using these policies. Each rule defines the number of types of errors that transitions the overall switch state into a state that is not healthy. For example, you can specify a switch policy so that if a switch has two port failures, it is considered to be in a marginal state; if it has four failures, it is in a down state. You can define these rules for a number of classes and field replaceable units, including ports, power supplies, and flash memory. See Chapter 10, "Switch and FRU configuration" for information on configuring switch policies. See Chapter 9, "Fabric Watch Reports" for information on viewing the current switch policies using the switch policy report. Virtual Fabric support Fabric Watch can monitor the switch health on eight logical switches. You can configure thresholds and alarms for ports that belong to a particular logical switch. Each logical switch has its own Fabric Watch configuration and triggers alarms based on its local configuration. Fabric Watch supports port movement from one logical switch to another. Whenever a port is moved, thresholds associated with the port are deleted from the logical switch the port was moved from, and created for the logical switch to where the port is moved. A logical interswitch link (LISL) is the logical portion of the physical connection that joins base switches. You can enable or disable port thresholds and create thresholds for state changes on LISLs, but Fabric Watch does not support other threshold areas such as link loss or signal loss for LISLs as it does for normal E_Ports. See "Port class areas" on page 15, for a complete list of state changes that are allowed on an LISL. NOTE Only state changes are supported on LISL ports. Port persistence The data collected in port monitoring can vary a great deal over short time periods. Therefore, the port can become a source of frequent event messages (the data can exceed the threshold range and return to a value within the threshold range). Fabric Watch uses port persistence for a port event that requires the transition of the port into a marginal status. Fabric Watch does not record any event until the event persists for a length of time equal to the port persistence time. If the port returns to normal boundaries before the port persistence time elapses, Fabric Watch does not record any event. To set the port persistence time, refer to "Setting the port persistence time" on page 35. Fabric Watch Administrator's Guide 5 53-1001342-01

  • 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
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
Fabric Watch Administrator’s Guide
5
53-1001342-01
Switch policies
1
Switch policies
Switch policies are a series of rules that define specific health states for the overall switch. Fabric
OS interacts with Fabric Watch using these policies. Each rule defines the number of types of errors
that transitions the overall switch state into a state that is not healthy. For example, you can specify
a switch policy so that if a switch has two port failures, it is considered to be in a marginal state; if it
has four failures, it is in a
down
state.
You can define these rules for a number of classes and field replaceable units, including ports,
power supplies, and flash memory.
See
Chapter 10, “Switch and FRU configuration”
for information on configuring switch policies.
See
Chapter 9, “Fabric Watch Reports”
for information on viewing the current switch policies using
the switch policy report.
Virtual Fabric support
Fabric Watch can monitor the switch health on eight logical switches. You can configure thresholds
and alarms for ports that belong to a particular logical switch. Each logical switch has its own
Fabric Watch configuration and triggers alarms based on its local configuration.
Fabric Watch supports port movement from one logical switch to another. Whenever a port is
moved, thresholds associated with the port are deleted from the logical switch the port was moved
from, and created for the logical switch to where the port is moved.
A logical interswitch link (LISL) is the logical portion of the physical connection that joins base
switches. You can enable or disable port thresholds and create thresholds for state changes on
LISLs, but Fabric Watch does not support other threshold areas such as link loss or signal loss for
LISLs as it does for normal E_Ports. See
“Port class areas”
on page 15, for a complete list of state
changes that are allowed on an LISL.
NOTE
Only state changes are supported on LISL ports.
Port persistence
The data collected in port monitoring can vary a great deal over short time periods. Therefore, the
port can become a source of frequent event messages (the data can exceed the threshold range
and return to a value within the threshold range).
Fabric Watch uses port persistence for a port event that requires the transition of the port into a
marginal status. Fabric Watch does not record any event until the event persists for a length of time
equal to the port persistence time. If the port returns to normal boundaries before the port
persistence time elapses, Fabric Watch does not record any event.
To set the port persistence time, refer to
“Setting the port persistence time”
on page 35.