|
 |
Agent Configuration |
 |
|
|
This configuration allows you to do some adjustments about the ASWM agent especially for those hardware-dependant options. Be careful before making any adjustment, you have to actually understand the results that they will affect to your system.
- ASR Control: ASR (Automatic Server Restart) is a function that can reboot the computer system automatically when a computer system hangs (or locked). You can enable or disable it here.
- ASR Time Interval: If the system has no response for a period of time that goes beyond this interval, ASR function activates.
- Chassis Intrusion Control: Chassis intrusion detector warns when the system's chassis is opened. This can provide somewhat security for the system's integrity. You can enable or disable it here. Not every model of system supports detection of chassis intrusion.
- Chassis Intrusion Counter: A counter will be increased every time the system's chassis is opened. It will be reset to zero if you disable the chassis intrusion alarm. This counter will be shown on the menu's region that is below the computer name and OS brand in the banner of ASWM.
- Reset Chassis Intrusion Counter: Literally, reset the chassis intrusion counter to zero. Note that if the counter is a non-zero value, a small and animated symbol will appear on the menu's area and this reminds you to check the system's integrity.
- Rescan Sensors: If the number of sensors is inconsistent, such as a certain fan was plugged out, you can rescan sensors here to make the number of sensors up to date. Note that a removed sensor will not disappear without doubt unless you rescan it here.
- Locator LED Control: You can turn on or off the locator LED on the system here. With this feature, you can find out the desired system among a pile of machines in a computer room easily. Not every model of system supports locator LED.
- System Rebootable: This property works with Reboot property. The system will be rebooted If this property was enabled and Reboot command has been issued.
- Reboot: Reboot system immediately. Nothing happens if System Rebootable property isn't also enabled.
- Send Repeated Event: If it is enabled, In each time (of interval duration), ASWM will always generate event repeatedly until the sensor values is back to normal.
- Sensor Update Interval: This indicates how many times that underlying of ASWM will refresh the up-to-date values for each sensor periodically.
- Reset To Default: Reset the underlying of ASWM to be default settings.
 Fig. Agent Configuration |
|
|
|
 |
|
|
|
 |
 |
HTTP Configuration |
 |
|
|
This configuration permits you to customize the items that will be explained shortly. Each HTTP browser on a single machine can have its own HTTP configuration, thus you can adjust a suitable configuration depending on the character of each client. To permanently keep your settings, the HTTP browser has to be cookie-ready and the cookie support should not be turned off. Otherwise, ASWM still cannot store any local information by your browser. However, even your configuration cannot be stored locally on your client machine, the settings that you adjusted here are still effective during the browsing time until it is closed.
- Enable Auto Update: You can decide if the HTTP browser can continuously update the contents of web pages during each of time interval.
- Browser Refresh Interval: This is the time in seconds that the HTTP browser updates the contents of web page. Minimum is five seconds.
- Desire VNC Display: To understand what VNC Display it is, you have to read the manual of VNC. When you ask ASWM web page to connect the VNC server on the remote system, the display number that shows here will be referred to. If you have a VNC server installed on a Linux platform, you probably could start up as many as VNC servers and each of them has a unique display number. You could connect any VNC server by specifying an existed display number here.
- VNC HTTP Port & VNC Main Port: In addition to ASWM, you still can use the pure VNC client application; it connects to the VNC main port on your system. However, when ASWM connects to VNC by its Java Applet, this Java Applet uses VNC HTTP port and then redirects the sockets to VNC main port. Hence when you connect to VNC by the Java Applet and if there is firewall installed before your system, two TCP ports have to be opened.
- HTTP Access Policy: This information will be stored on the system side permanently instead of the client side by cookie. Choose "Grant all without checking accessibility" will tell ASWM not to restrict any clients from accessing web pages; otherwise, only "Granted Clients" can access ASWM's web page.
- Granted Clients: This information will be stored on the system side permanently instead of the client side by cookie. It records about what IP classes or IP addresses that can access the ASWM's web page when the access policy is set to be "Grant only clients in <Granted Clients>". Before any HTTP browser connects to the ASWM, its IP address will be checked. Those blocked addresses will be led to a warning page and it tells that you are denied to access ASWM. 127.0.0.1 always is allowable connections from the system itself.
- Display Language: You are allowed to view the contents of ASWM web page in any supported language. Currently, only English is supported and soon some Asian languages (e.g., Traditional Chinese, Simplified Chinese and Japanese) will be supported as well. Note that if your remote system has different language of OS installed rather than the language you want to browse, then there may be some contents possibly will show incorrectly on your HTTP browser. In that case, we suggest you to use English as your primary displaying language.
 Fig. HTTP Configuration |
|
|
|
 |
|
|
|
 |
 |
Firmware Flash |
 |
|
|
This configuration allows you to flash your system's BIOS (plus BMC firmware in the future). The flashing program on the system will strictly check the uploaded file, so that you do not have to concern that if somebody wants to ruin your system by uploading and flashing a garbage file. Besides, even if you close the HTTP browser before the flashing progress is finished, the flashing program will continue until the job is well done. There is no chance that two of flashing actions will occur because the flashing program will lock itself when a flashing action is on-going.
Currently, it only supports on Windows platform.
 Fig. Firmware Flash |
|
|
|
 |
|
|
|
 |
|