IBM Carrier Grade X3650 T User Manual

IBM® Carrier Grade Server X3650 T
Revision 3.0
84
17.2.3.2.4 syscon_log_sigval_recid()
The syscon_log_sigval_recid() function shall store the record ID of the event record associated with the
current notification to the location pointed to by the recid argument. If the SYSCONLOG_SEND_RECID
flag is not set in the associated notification request, the value stored to recid shall be undefined.
This function is intended to be called from the new thread that handles delivery of an event notification.
(In the associated notification request, notification->sigev_notify must be SIGEV_THREAD.) The sval
argument of syscon_log_sigval_recid() shall be the sigval argument of that thread’s start_routine. The
effect of calling syscon_log_sigval_recid() under other circumstances shall be undefined.
17.2.3.2.5 syscon_log_notify_get()
The syscon_log_notify_get() function retrieves the parameters of the notification request associated with
the nfyhandle argument. A copy of the notification request’s sigevent structure shall be stored to the
location pointed to by the notification argument.
A copy of the notification request’s flags shall be stored to the location pointed to by the flags argument.
If the notification request is currently disabled, the SYSCONLOG_NFY_DISABLED flag shall be set.
syscon_log_notify_get() shall also store a textual query expression to the buffer pointed to by the qsbuf
argument; this expression (a null-terminated string) shall be functionally equivalent to the one that was
used to create the notification request’s query object. (If the notification request’s query object is NULL, a
null character shall be stored to qsbuf[0].) The buffer pointed to by qsbuf is assumed to be at least qslen
bytes long. If qsbuf is equal to NULL, or the buffer is too small to hold the returned character string, the
syscon_log_notify_get() function shall fail. In any case, if the reqlen argument is not NULL, the length in
bytes of the query expression shall be stored in the location pointed to by reqlen.
17.2.3.2.6 Notification Requests
A process may have up to {SYSCONLOG_NOTIFY_MAX} notification requests (including disabled
requests) registered at any one time. Registration (creation), disabling, or removal of one notification
request has no effect on other notification requests. When the system log receives a new event record,
all notification requests for a particular process are processed sequentially and independently. If a
process has more than one notification request that is matched by a particular event, then the notification
associated with each such notification request will be sent to the process.
Notifications shall not be sent before the associated event record has been added to the system log, and
is available for detection by syscon_log_seek() and reading by syscon_log_read().
17.2.3.3 Returns
Upon successful completion, these functions shall return zero. Otherwise, an error number shall be
returned to indicate the error. If syscon_log_notify_add() fails, the data pointed to by nfyhandle shall
remain unchanged. If syscon_log_siginfo_recid() or syscon_log_sigval_recid() fails, the data pointed to
by the recid argument shall remain unchanged. If syscon_log_notify_get() fails, the data pointed to by the
notification and query_string arguments shall remain unchanged.

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.