Technical data

...
#pop ancestor programfile
Refer to the Guardian Programmer’s Guide for more information about CMON.
Optional OSM Configuration
It is not necessary to create a configuration file to use OSM with the default settings. However, if
you want to alter any default settings or take advantage of the following OSM features, you must
create and use an OSMCONF file:
• “Creating and Using an OSMCONF File” (page 15)
• “Disabling Alarm Remote Notification (Dial-out) ”
• “Suppressing Specific Alarms” (page 17)
• “Specifying Alternate Collector for OSM Event Viewer” (page 16)
• “Binding to an IP Address and Stack for OSM when Sending Indications” (page 17)
• “Configuring Additional TCP/IP Processes for OSM Connectivity” (page 18)
• “Configuring OSM to Monitor Devices Not on the Dedicated Service LAN” (page 19)
• “Enabling Enhanced Redundant Power Scrub” (page 20)
• “Disabling Creation of System Inventory Files ” (page 20)
• “Configuring Automatic Data Collection” (page 21)
• “Disabling Alarm and Attribute Suppression Persistence” (page 21)
• “Suppressing Redundant IRs from ServerNet Cluster Nodes” (page 22)
• “Configuring Secure Sockets Layer (SSL) Support” (page 22)
• “Configuring the Cipher Suites Used by SSL” (page 22)
• “Configuring Event Viewer Security Timeout” (page 27)
• “Configuring OSM in a Network Address Translation (NAT) Environment” (page 28)
• “Configuring Insight Remote Support Advanced” (page 29)
• “Configuring OSM Power Fail Support ” (page 29)
• “Configuring OSM Process File Security Levels” (page 30)
• “Flagging Up-rev CLIM and SAS Disk Enclosure Firmware as a Problem Attribute” (page 32)
• “Disabling Access Control List Functionality” (page 32)
• “Enabling IPv6 Support” (page 32)
For information on how an administrator for a maintenance switch or UPS changes the default
SNMP access configurations for those devices, see Appendix E, Configuring SNMP Access for
Monitored Service LAN Devices.
Creating and Using an OSMCONF File
OSMINI is a template file delivered as part of T0682, to assist you in creating your own (optional)
customized OSMCONF file. Because the OSMCONF file is user-created and not installed by OSM,
when you upgrade to a new T0682 SPR, your customized settings are not overwritten.
To create an OSMCONF file from an OSMINI template file and to put your configuration changes
into effect:
1. Go to $SYSTEM.ZSERVICE and copy OSMINI to create a new file named OSMCONF.
2. Edit the OSMCONF file to customize the default settings as desired. To avoid possible problems,
delete blank lines from the OSMCONF file.
Optional OSM Configuration 15