Network Management / (OpenView-NNM) Practitioners Forum
Showing results for 
Search instead for 
Do you mean 

is there anyinformation on nnmsetlogginglevel.ovpl beyond the ?/help

SOLVED
Go to Solution
Occasional Advisor

is there anyinformation on nnmsetlogginglevel.ovpl beyond the ?/help

I'm hoping that there are a few more options and a little information on how to set the levels.

A white paper would be nice.....:smileyhappy:

5 REPLIES
Honored Contributor [Founder]

Re: is there anyinformation on nnmsetlogginglevel.ovpl beyond the ?/help

Hi,

 

There's very little documented about nnmsetlogginglevel.ovpl. What I know is that settings via nnmsetlogginglevel.ovpl are temporarily. Once you restart NNMi the settings are lost. To make the changes permanent you should edit the logging.properties file (/var/opt/OV/shared/nnm/conf/ovjboss/) and run the nnmreadlogging.ovpl script. Make changes to the .limit, .count or .level parameters for the different processes. Regards,

 

DJ

Honored Contributor [Founder]

Re: is there anyinformation on nnmsetlogginglevel.ovpl beyond the ?/help

Agreed, this mostly used by HP Support and if misused it may crash NNM   

Trusted Contributor

Re: is there anyinformation on nnmsetlogginglevel.ovpl beyond the ?/help

Hi Drennin,

The Jboss is application server and hosting variuos applications (componentslike web interface, Discovery, Configuration or Status Pollers) if you need to troubleshoot certain component you have to increase the level of logging for that component.

 

The components are named in Java namaspace so for example if you want to troubleshoot issues related to UI the namespace for that object is com.hp.ov.nms.ui 

So you can modify logging.properties to change the logging level or you can use the command nnmreadlogginglevel.ovpl to read the current level of logging and nnmsetlogginglevel.ovpl to change it.

 

 

 

Regards,
Mahmoud Ibrahim
http://www.mahmoudthoughts.com
  • Say thanks by clicking the "Kudos! Star" which is on the left.

  • Make it easier for other people to find solutions, by marking my answer with "Accept as Solution" if it solves your issue.
  • Occasional Advisor

    Re: is there anyinformation on nnmsetlogginglevel.ovpl beyond the ?/help

    Thanks, and (I'm an HP employee)

    Highlighted
    Respected Contributor

    Re: is there anyinformation on nnmsetlogginglevel.ovpl beyond the ?/help

    SEVERE: This is the most concise logging and consumes the fewest system resources. The output describes events that relate to normal NNM behavior and are of considerable importance to NNM administrators.

     

    WARNING: This level of logging includes more details than SEVERE. The output describes events of interest to end users or system managers, or events which indicate potential problems.

     

    INFO: This level of logging includes more details than WARNING. The output includes messages written to the NNM console or its equivalent. The INFO logging level logs messages that will make sense to end users and system administrators. INFO logging messages might be the result of a user event or a significant transaction such as starting a backup, a user-initiated action, or a scheduled action. Another example of an INFO logging message is the result of an operation that failed due to incorrect user input, assuming that a corresponding message is written to the NNM console.

     

    CONFIG: This level of logging includes more details than INFO. The output includes messages intended to provide a variety of static configuration information and assist system administrators in debugging problems that may be associated with particular configurations.

     

    FINE: This level of logging includes more details than CONFIG. The last three logging levels, FINE, FINER, and FINEST, are the most detailed. When we use the FINE logging level, NNM logs the most important and fewest number of messages among these three logging levels. Examples of a FINE logging level message might include a recoverable failure or a potential performance problem.

     

    FINER: This level of logging includes more details than FINE. The output includes a higher number of messages than the FINE logging level, and includes information related to program calls for entering, returning, or throwing exceptions.

     

    FINEST: This level of logging includes more details than FINER. The output includes a higher number of messages than the FINER logging level, and includes the most verbose level of logging.

    Thanks,
    Bharath