HP Carrier-grade cc3300 Intel Server Management (ISM) Installation and User&am - Page 43

Cautions in Setting Thresholds

Page 43 highlights

Intel Server Management (ISM) Installation and User's Guide Client SSU (CSSU) Details 5. If you want to change the event actions associated with threshold state change conditions, make the changes on the Alert Actions tab. 6. Click Apply for any changes made to the alert action configuration. NOTE After applying new threshold values that may cause an event indication, the sensor status icon displayed on the Sensor Settings tab may not change. The console refreshes the display before the new threshold value takes effect on the server, making it appear as though the sensor icon does not accurately reflect the current state of the sensor. Use the menu option, View->Refresh, or the F5 keyboard shortcut, to update the Sensor Settings tab. To Configure a State-Based Threshold The state-based thresholds for processor, power supply, rotation-sensing fans, chassis door, and memory arrays have a fixed set of values, not a range. Examples of state change conditions: • Single bit memory error • Processor thermal trip • Power supply failed NOTE For systems that support rotation-sensing fans, the fan RPM threshold setting displays a 0 and is read-only in PIC. PIC generates an event whenever the state of these items changes. You can specify which actions should occur in response to changes. To configure a state-based threshold: 1. On the PIC main window, click beside a sensor name in the navigation pane to see a list of available sensors. 2. Select an entry from the list. 3. Select the Alert Actions tab. Change the event actions associated with a state change condition. 4. Click Apply to save your changes. Cautions in Setting Thresholds Rounding of Threshold Values Hardware rounding can cause thresholds to be set to a different value than the exact value you enter in ISM. Redisplay the Sensor Settings tab to find the actual value set by the software. NOTE Due to the automatic rounding of floating point values, small differences in threshold values may be interpreted as no difference at all. (PIC interpretation may be unchanged.) Avoiding a Power-On/Off Loop Improperly setting event actions can cause the server to enter a state that prevents the server from booting correctly. For example: 1. An event occurs, such as exceeding a high-temperature threshold. 2. While the condition causing the event still exists, you set a Shutdown/Power Control Action, like Immediate Power Off, to respond to this event. NOTE The Immediate Power Off action may not function during server installation.

  • 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

Intel Server Management (ISM) Installation and User's Guide
Client SSU (CSSU) Details
5.
If you want to change the event actions associated with threshold state change conditions, make the
changes on the Alert Actions tab.
6.
Click Apply for any changes made to the alert action configuration.
NOTE
After applying new threshold values that may cause an event indication, the sensor status
icon displayed on the Sensor Settings tab may not change. The console refreshes the display
before the new threshold value takes effect on the server, making it appear as though the
sensor icon does not accurately reflect the current state of the sensor. Use the menu option,
View->Refresh, or the F5 keyboard shortcut, to update the Sensor Settings tab.
To Configure a State-Based Threshold
The state-based thresholds for processor, power supply, rotation-sensing fans, chassis door, and memory
arrays have a fixed set of values, not a range. Examples of state change conditions:
Single bit memory error
Processor thermal trip
Power supply failed
NOTE
For systems that support rotation-sensing fans, the fan RPM threshold setting displays a 0
and is read-only in PIC.
PIC generates an event whenever the state of these items changes. You can specify which actions should
occur in response to changes. To configure a state-based threshold:
1.
On the PIC main window, click beside a sensor name in the navigation pane to see a list of available
sensors.
2.
Select an entry from the list.
3.
Select the
Alert Actions
tab. Change the event actions associated with a state change condition.
4.
Click Apply to save your changes.
Cautions in Setting Thresholds
Rounding of Threshold Values
Hardware rounding can cause thresholds to be set to a different value than the exact value you enter in ISM.
Redisplay the Sensor Settings tab to find the actual value set by the software.
NOTE
Due to the automatic rounding of floating point values, small differences in threshold values
may be interpreted as no difference at all. (PIC interpretation may be unchanged.)
Avoiding a Power-On/Off Loop
Improperly setting event actions can cause the server to enter a state that prevents the server from booting
correctly. For example:
1.
An event occurs, such as exceeding a high-temperature threshold.
2.
While the condition causing the event still exists, you set a Shutdown/Power Control Action, like
Immediate Power Off, to respond to this event.
NOTE
The Immediate Power Off action may not function during server installation.