IBM Carrier Grade X3650 T User Manual

IBM® Carrier Grade Server X3650 T
Revision 3.0
93
operators result in string comparisons unless otherwise specified. For example, if x and y are character-
string values, "x != y" evaluates to 1 if strcmp(x,y) would return a non-zero value, or to zero otherwise.
(Note that sometimes a string comparison is not performed even when the right operand is a string; see
Table 3 for examples.)
The "=" operator is a synonym for the "==" operator.
The "&" operator is defined only for integer operands, and has the meaning specified for that token in the
C language (bitwise OR).
As in the C language, the expression "! x" evaluates to 1 if x is zero, or to zero otherwise.
For purposes of evaluating expressions, operator precedence shall be as defined for the corresponding
operators in the C language.
An identifier token, which conforms to the rules of a C-language identifier, can be the name of an attribute
(e.g., severity) or of a symbolic constant (e.g., EMERG). An attribute name stands for the value of the
indicated attribute in the event record being examined.
A string-literal token is a character sequence, beginning and ending with double-quote characters, that
conforms to the rules for a C-language character string literal. Support for wide string literals (in which
the first double-quote is immediately preceded by the letter 'L') is not required. Support for automatic
concatenation of adjacent string literals into a single string literal is not required.
An integer-constant token is a sequence of digits and letters than conforms to the rules for a C-language
integer constant (decimal, hexadecimal, or octal), except than unsigned and long suffixes (upper or
lowercase 'U', upper or lowercase 'L') are not permitted.
The expression "x contains y" is valid only for character-string operands. It evaluates to zero if
strstr(x,y) would return NULL, or to 1 otherwise.
A test expression that consists only of an attribute name evaluates to 1 for a record that contains a value
for that attribute, or to zero for other records. In particular, the test "data" shall fail if the record contains
no variable portion.
3
A test of the form "attribute-name op val" shall fail for any event record that does not contain a value for
the named attribute.
17.2.8.2.6 Required Comparison Operations for General Queries
Table 3 lists the required members of struct syscon_log_entry and the required comparison operations
for each member. The “string representation” of a record’s attribute is the character string returned by the
syscon_log_memtostr() function for that member of that record.
4
Table 3. Required Operations on Standard Attributes
3
In strictly conforming applications, this paragraph and the next apply only to the “data” pseudo-attribute, which refers
to the variable portion of an event record. They could also apply to implementation- and/or application-defined
attributes in implementations that support such attributes.
4
The implementation is permitted to convert a string-literal operand to an equivalent value (e.g., uid=“root” to uid=0)
to obtain an equivalent (presumably more efficient) test.

IBM Carrier Grade X3650 T Specifications

General

Product Type	Server
Processor	Intel Xeon
Network Interface	Gigabit Ethernet
Operating System Support	Microsoft Windows Server, Red Hat Enterprise Linux, SUSE Linux Enterprise Server
RAID Support	Yes
Power Supply	Redundant power supply options

Summary

Revision History

Disclaimers

1. Introduction

2. SysCon Features

2.1 Automatic preservation of system settings

Preserves current BIOS and server management feature settings during system startup.

2.2 Detection of system setting changes

Compares current settings to saved ones and restores them if different, by default.

2.3 Transfer of system settings

Allows transferring system settings to a second system or using a SysCon Key.

3. Installing the SysCon Feature

3.1 Microsoft Windows*

Details the installation of the SysCon feature on Microsoft Windows* 2003 Enterprise Edition systems.

3.2 Linux

Details the installation of the SysCon feature on Linux operating systems.

3.3 Activating/Deactivating the SysCon Feature

Explains how to activate and deactivate the SysCon feature through system BIOS settings.

4. SysCon Feature Operation Overview

4.1 Configuring and booting the first time

Guides initial system configuration and boot process after SysCon installation.

4.2 Reconfiguring the system

Explains how SysCon uses policy settings to detect and act on system setting changes.

5. Booting the System

6. Controlling SysCon Behavior Using Policies

7. Interacting with the SysCon Feature

7.1 Using the SysCon Menu

Describes how to access and navigate the SysCon menu for system management.

7.2 Detecting system setting changes

Explains how SysCon detects and prompts for action when system settings change.

7.3 Applying transferred settings

Details how SysCon handles transferred settings when a device is moved to another system.

7.4 Using a SysCon Key

Covers backing up, restoring, and installing SysCon using a removable SysCon Key.

8. Creating System Settings Files

8.1 Encrypting Settings Data

Details how to encrypt sensitive component settings data using the SysconCipher.py utility.

8.2 Applying new user-specified settings

Explains how SysCon applies user-specified settings from the 'specified' folder.

8.3 Importing User-Specified Settings

Describes applying common settings to multiple servers via SysCon Keys.

9. Monitoring SysCon Activity

9.1 Logging SysCon Events

Configures logging of SysCon events, including severity filters and destinations.

9.2 Configuring Event Notification Actions

Sets up proactive user notifications for SysCon events to destinations like Telco Alarm Panel.

10. Using SysCon Operating System Services and Utilities

11. Using the SysCon Device for Application Data

12. SysCon Services

12.1 SysCon Service for Linux Features

Details SysCon install tools and utilities for Linux environments.

12.2 Events, Notification, and Actions

Explains SysCon events, logging, notification policies, and actions.

13. APPENDIX A – SysCon Environment Folder Structure

14. APPENDIX B – SysCon Policy File Format

14.1 SysCon Device Policy Defaults: policydefaults.xml

Documents default SysCon device policy settings and provides XML schema excerpts.

15. APPENDIX C – System Settings File Format

15.1 A Typical System Settings File Example

Provides an example of a system settings file in XML format for BIOS and IMM configuration.

15.2 A “Full” System Settings File Example

Presents a comprehensive example of a system settings file for detailed configuration.

15.3 System / Component Schema

Describes the XML schema files used for system and component settings.

15.4 Updating BIOS and Intel® Management Module firmware

15.4.1 Intel:BIOSVersion update example

Example XML for updating BIOS firmware versions with labels and tokens.

15.4.2 Intel:IMMVersion update example

Example XML for updating Intel Management Module firmware versions.

16. APPENDIX D – SysCon Log File Format

17. APPENDIX E – POSIX Logging API and Query Specification for SysCon

17.1 Logging Functions

Details SysCon logging functions, including writing to logs and formatted output.

17.2 Log Processing Functions

Covers functions for opening, reading, and managing log files and notifications.

18. Appendix F: Troubleshooting the SysCon Feature

18.1 Embedded USB Device “Present”

Troubleshooting table for SysCon behavior when the embedded USB device is present.

18.2 Embedded USB device “Not Present”

Troubleshooting table for SysCon behavior when the embedded USB device is not present.

18.3 Problem USB devices

Lists tested USB devices and their compatibility for use with SysCon.