In my last blog, I wrote about various OSMCONF settings that you can use to customize OSM to your specific NonStop environment. In this blog, I will discuss OSMCONF settings specific to OSM client-server communication using Secure Sockets Layer (SSL). In this context, OSM client means not only OSM Service Connection and OSM Event Viewer, but also HP Systems Insight Manager (SIM), HP Insight Remote Support Advanced, HP Insight Control Power Management, or any NonStop Essentials product.
RAS (Reliability, Availability and Serviceability) characteristics are what differentiate the mission critical systems from non-mission critical systems. With NonStop systems at the top of mission critical spectrum (L4 level availability), it is only expected of NonStop systems to excel in RAS characteristics. As NonStop Manageability and Serviceability Architect, it falls under my responsibilities to ensure that NonStop systems provide the best serviceability possible. I am happy to brag about some of the serviceability enhancements we have done recently to take the serviceability of the NonStop BladeSystems to the next level. This includes Down-system CLIM firmware update tool, DHCP DNS Configuration Wizard, DHCP and DNS server status monitoring, IPv6 support in OSM, ability for OSM to listen on specific IP addresses, alarm for non-responsive CLIM, log collection from an individual CLIM, CLIM replacement guided procedure, bad blade system board battery alarm, alarm for degraded DIMM in CLIM, suppression of service-induced BladeCluster alarms, ability for OSM to bind to a specific IP address to send indications, and suppression of creation of a specific alarm on a specific resource, to name a few.
How quickly can you service components, systems, or applications to get back up and running—before your competitors gain an edge?