How to pull NonStop CLIMS logs into Prognosis.

[Jay_Horton1]

Looking to monitor the health of IPSEC on the NonStop CLIMS. I looked at all of the Records and I do not see one for CLIMLOGS. Trying to figure out a way to monitor the health of our IPSEC connections before the application sees an issue.

Any ideas?

[Scott_Clement]

Hi @Jay_Horton1,

If the CLIM's log to EMS, we should be able to pick those up (via STEMS/EMS collector). If they're logging to a log file or some other destination (maybe syslog?), then it may be a bit more difficult. I'm also assuming this is specific to Network CLIMs but, if you could clarify, that would be ideal. Unfortunately, I don't have a great deal of knowledge regarding the configuration of these devices on the NonStop so I'll either need to hit the HP manuals or track down someone who's more familiar and can provide a better answer.

Regards,

Scott

[Jay_Horton1]

Hello

Yes these are NETWORK CLIMS and the information that is needed are the SYSLOGS on the network clims. I had a case opened with HPE to see if any type of messages from the health of the IPSEC tunnel are sent to EMS on the NONSTOP. The answer was NO. So the only place is the SYSLOGS on the CLIMS. Just trying to figure out a way to monitor the health of the IPSEC tunnels and allow PROGNOSIS to Alert on this.

[Scott_Clement]

Thanks for the additional information Jay.

I did some homework, which involved reading through the ‘HPI NonStop Cluster I/O Protocols (CIP) Configuration and Management Manual’ and that did seem to indicate that messages could be logged to syslog or EMS (and the latter would certainly make things much easier), but the answer you received from HPE closes the door on that possiblity.

I ran your question by one of our Product Managers today and they suggested we might be able to achieve this in the short-term through the use of a command line extractor. The suggestion was that we might be able to use a TACL command using the format:

CLIMCMD <clim-name> <linux command>

using a linux command similar to "tail  -f <logfile>" which would keep the remote shell running (so the extractor is not constantly logging in and out of the CLIM).

I'll need to do a bit of testing to see if it's a possibility and I might be able to provide a basic example or prototype that you can build on.

You would also need to have ADI licensed in order to create your own User Defined Record and extractor, which may be another limitation. Of course, if a custom record and extractor is also not something you're comfortable building, then our Professional Services team would definitely be the best resource to engage to build a solution that meets your needs.

For a long-term solution, I can get in touch with your account manager and ask him to submit a request to incorporate this functionality into product.

Regards,

Scott Clement

[Jay_Horton1]

Thank you for researching this. We do have other extractor running for other stuff. It looks like this will not be a quick resolution any way I go. I was wanting a more real time solution other than writing a TACL MACRO to collect the SYSLOGS and search for issues or configure and extractor to do the same type of thing. Please keep me posted and I will continue to work options on my side.

[Scott_Clement]

Hi Jay,

Unfortunatley I was limited in the testing I was able to carry out, mainly because our test account has limited permissions and we aren't able to read the syslog file.

The extractor suggestion is the only short-term solution I was able to identify, but I've asked your account manager if they're able to submit an enhancement request on your behalf, which will go to our product team for consideration.

I could provide a basic 'File Info' example of an extractor instead bit, if you're already using extractors, I suspect you have a few examples if you need to something to refer to (should you decide to try building a solution yourself).

If you need anything else, please let me know

Regards,

Scott