IBM 2109 Service Guide - Page 69

Optional features, Fabric Watch

Get IBM 2109 - SAN Fibre Channel Switch Model S16 PDF manuals and user guides
UPC - 087944519355
View all IBM 2109 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 69 highlights

| | Chapter 6. Optional features | | | | | | Fabric Watch | | This chapter contain the following optional features: v Fabric Watch. v Remote switch. See "Remote Switch" on page 62. v Extended fabrics. See "Extended Fabrics" on page 64. Fabric Watch is an optionally licensed product, and requires a valid license key to function. | Note: To verify whether the Fabric Watch license is already installed on the switch, | type licenseShow on the Telnet command line. For additional information see | step 2 on page 55. | Fabric Watch is supported for the 2109 switches using the 2109 Fabric Operating | System, version 2.2 or later. | This section describes the Fabric Watch software and how to install it, plus detailed | information for using thresholds to manage switch functions. | Fabric Watch allows the SAN manager to monitor key fabric and switch elements, | making it easy to quickly identify and escalate potential problems. It monitors each | element for out-of-boundary values or counters and provides notification when a | particular element exceeds the defined boundaries. The SAN manager can | configure which elements, such as error, status, and performance counters within a | 2109 switch, are monitored. | Fabric Watch runs on 2109 switches with Fabric OS, version 2.2 or later, and can | be accessed through the IBM StorWatch Specialist, a Telnet interface, a Simple | Management Network Protocol (SNMP)-based enterprise manager, or by modifying | and uploading the Fabric Watch configuration file to the switch. | Fabric Watch monitors the following elements: | v Fabric events (such as topology reconfigurations and zone changes) | v Switch environment (fans, power supplies, and temperature) | v Ports (state changes, errors, and performance) | v GBICs (for switches equipped with smart GBICs). | With Fabric Watch, each switch continuously monitors error and performance | counters against a set of defined ranges. This and other information specific to | each monitored element is made available by Fabric Watch for viewing and, in | some cases, modification. This set of information about each element is called a | threshold, and the upper and lower limits of the defined ranges are called | boundaries. | If conditions go beyond acceptable ranges, an event is considered to have | occurred. One or more alarms (reporting mechanisms) are generated if configured | for the relevant threshold. There are three types of alarms: | v SNMP trap | v Entry in the switch event log © Copyright IBM Corp. 1999, 2000 53

  • 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
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
Chapter 6. Optional features
This chapter contain the following optional features:
v
Fabric Watch.
v
Remote switch. See “Remote Switch” on page 62.
v
Extended fabrics. See “Extended Fabrics” on page 64.
Fabric Watch
Fabric Watch is an optionally licensed product, and requires a valid license key to
function.
Note:
To verify whether the Fabric Watch license is already installed on the switch,
type
licenseShow
on the Telnet command line. For additional information see
step 2 on page 55.
Fabric Watch is supported for the 2109 switches using the 2109 Fabric Operating
System, version 2.2 or later.
This section describes the Fabric Watch software and how to install it, plus detailed
information for using thresholds to manage switch functions.
Fabric Watch allows the SAN manager to monitor key fabric and switch elements,
making it easy to quickly identify and escalate potential problems. It monitors each
element for out-of-boundary values or counters and provides notification when a
particular element exceeds the defined boundaries. The SAN manager can
configure which elements, such as error, status, and performance counters within a
2109 switch, are monitored.
Fabric Watch runs on 2109 switches with Fabric OS, version 2.2 or later, and can
be accessed through the IBM StorWatch Specialist, a Telnet interface, a Simple
Management Network Protocol (SNMP)-based enterprise manager, or by modifying
and uploading the Fabric Watch configuration file to the switch.
Fabric Watch monitors the following elements:
v
Fabric events (such as topology reconfigurations and zone changes)
v
Switch environment (fans, power supplies, and temperature)
v
Ports (state changes, errors, and performance)
v
GBICs (for switches equipped with smart GBICs).
With Fabric Watch, each switch continuously monitors error and performance
counters against a set of defined ranges. This and other information specific to
each monitored element is made available by Fabric Watch for viewing and, in
some cases, modification. This set of information about each element is called a
threshold, and the upper and lower limits of the defined ranges are called
boundaries.
If conditions go beyond acceptable ranges, an event is considered to have
occurred. One or more alarms (reporting mechanisms) are generated if configured
for the relevant threshold. There are three types of alarms:
v
SNMP trap
v
Entry in the switch event log
© Copyright IBM Corp. 1999, 2000
53
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|