HP Brocade 8/12c Fabric Watch Administrator's Guide v6.4.0 (53-1001770-01, Jun - Page 62

Fabric monitoring setting guidelines, Loss of E_Port

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 62 highlights

6 Fabric monitoring guidelines and default settings TABLE 3 Area Fabric class areas (Continued) Description Segmentation changes Tracks the cumulative number of segmentation changes. Segmentation changes occur because of one of the following: • Zone conflicts. • Incompatible link parameters. During E_Port and VE_Port initialization, ports exchange link parameters, and incompatible parameters result in segmentation. This is a rare event. • Domain conflicts. • Segmentation of the principal link between two switches. Zone changes Tracks the number of zone changes. Because zoning is a security provision, frequent zone changes might indicate a security breach or weakness. Zone change messages occur whenever there is a change in zone configurations. Fabric monitoring setting guidelines It is recommended that you leave the entire Fabric class in its default state (no alerts) for the following reasons. • Domain ID changes Plan and use strict change control practices to avoid Domain ID changes. • State changes SFP class areas and Port class (including E_Port and FOP_Port) areas are used to gather SFP state changes; therefore, don't change the default settings for the Fabric class. • Loss of E_Port Detect if an E_Port is down using the E_Port class areas. • Fabric logins In a large environment of numerous devices, this area is of no interest. • Fabric reconfiguration Fabric reconfigurations typically occur when new switches are added to a fabric, which is a planned activity, or when an upstream or downstream ISL fails, which is detected through the E_Port class areas. Since fabric reconfigurations are monitored elsewhere, don't change the default settings for the Fabric class. • Segmentation changes Segmentations only occur in the event of an entire switch failure. In this rare case, you can gather multiple reports from all the attached E_Ports of the link failures. • Zoning changes Zone changes are captured through the Audit facility in Fabric OS. All zone changes can be configured to be recorded in the RASlog, which is the recommended practice. 42 Fabric Watch Administrator's Guide 53-1001770-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
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
42
Fabric Watch Administrator’s Guide
53-1001770-01
Fabric monitoring guidelines and default settings
6
Fabric monitoring setting guidelines
It is recommended that you leave the entire Fabric class in its default state (no alerts) for the
following reasons.
•
Domain ID changes
Plan and use strict change control practices to avoid Domain ID changes.
•
State changes
SFP class areas and Port class (including E_Port and FOP_Port) areas are used to gather SFP
state changes; therefore, don’t change the default settings for the Fabric class.
•
Loss of E_Port
Detect if an E_Port is down using the E_Port class areas.
•
Fabric logins
In a large environment of numerous devices, this area is of no interest.
•
Fabric reconfiguration
Fabric reconfigurations typically occur when new switches are added to a fabric, which is a
planned activity, or when an upstream or downstream ISL fails, which is detected through the
E_Port class areas. Since fabric reconfigurations are monitored elsewhere, don’t change the
default settings for the Fabric class.
•
Segmentation changes
Segmentations only occur in the event of an entire switch failure. In this rare case, you can
gather multiple reports from all the attached E_Ports of the link failures.
•
Zoning changes
Zone changes are captured through the Audit facility in Fabric OS. All zone changes can be
configured to be recorded in the RASlog, which is the recommended practice.
Segmentation changes
Tracks the cumulative number of segmentation changes. Segmentation changes occur
because of one of the following:
•
Zone conflicts.
•
Incompatible link parameters. During E_Port and VE_Port initialization, ports
exchange link parameters, and incompatible parameters result in segmentation.
This is a rare event.
•
Domain conflicts.
•
Segmentation of the principal link between two switches.
Zone changes
Tracks the number of zone changes. Because zoning is a security provision, frequent
zone changes might indicate a security breach or weakness. Zone change messages
occur whenever there is a change in zone configurations.
TABLE 3
Fabric class areas (Continued)
Area
Description