(DP) Support Tip: Set omnirc values remotely

There are cases where you would like to set an omnirc variable to a remote host.

This can be achived by using: util_cmd -setomnirc <hostname> <variable> <value>

For example:

C:\Users\Administrator.DPLAB>util_cmd -setomnirc mail1.dplab.local OB2IPCKEEPALIVE 1
*RETVAL*0

C:\Users\Administrator.DPLAB>util_cmd -getomnirc mail1.dplab.local OB2IPCKEEPALIVE
1

Tags:

Parents
  • Very nice addition to the Admin-Commands.

    Is it planned to add a Option to list all set Variables of a Client?

    Also an Option to list all available Variables with their Defaults and/or modified Value would be nice, like it can be found for Global-Variables in Debug-Logs.

  • I'm not aware of any plans to add this functionality. The original request was to allow omnirc distribution from GUI which might come in the future. In the meantime you could use my script that uses util_cmd to push omnirc templates to clients in the cell.

    https://www.data-protector.org/wordpress/2016/05/script-distribute-omnirc-file/

    Regards,
    Sebastian Koehler

  • Hi Sebastian

    That Script seems to be a nice hack to distribute the same Variables to many Clients, have something similar (although more basic) in place. Thanks for sharing it, will give it a go.

    But looks like this is only a one-way push kind of thing. What I often need is an Overview on what a client or a group of them have set up so far. For known Variables you can manage with -getomnirc. But usually the unknown or undocumented Variables are more interesting, especially when Application-Guys tend to modfiy variables set by us or add new ones they consider helpful.

    Some kind of option to get a summary like in Debugs would be nice:

    Logging
    --------------
    [ 20]   LogCrsEvents              = 0
    [ 20]   EventLogMessages          = 0
    [ 20] * SmLogStartStop            = 0
    [ 20]   EventLogAudit             = 0
    [ 20] * AuditLogEnable            = 1
    [ 20] * AuditLogRetention         = 60
    [ 20]   LogChangedProtection      = 0
    [ 20]   LogChangedProtectionRetention = 1
    [ 20]
    Limits
    --------------
    [ 20]   MaxSessions               = 1000
    [ 20]   MaxBSessions              = 500
    [ 20]   MaxMaPerSm                = 100
    [ 20]   MaxDaPerMa                = 32
    [ 20]   MaxNumberOfMirrors        = 5
    [ 20]   MaxSessionsPerDay         = 100000
    [ 20]
    Cell Server
    --------------
    [ 20]   CrsPort                   = -1
    [ 20]   CheckVersions             = 1
    [ 20]   MaxWaitForSm              = 120
    [ 20] * SchedulerGranularity      = 15
    [ 20] * DailyMaintenanceTime      = "13:00"
    [ 20] * DailyCheckTime            = "13:30"

Reply
  • Hi Sebastian

    That Script seems to be a nice hack to distribute the same Variables to many Clients, have something similar (although more basic) in place. Thanks for sharing it, will give it a go.

    But looks like this is only a one-way push kind of thing. What I often need is an Overview on what a client or a group of them have set up so far. For known Variables you can manage with -getomnirc. But usually the unknown or undocumented Variables are more interesting, especially when Application-Guys tend to modfiy variables set by us or add new ones they consider helpful.

    Some kind of option to get a summary like in Debugs would be nice:

    Logging
    --------------
    [ 20]   LogCrsEvents              = 0
    [ 20]   EventLogMessages          = 0
    [ 20] * SmLogStartStop            = 0
    [ 20]   EventLogAudit             = 0
    [ 20] * AuditLogEnable            = 1
    [ 20] * AuditLogRetention         = 60
    [ 20]   LogChangedProtection      = 0
    [ 20]   LogChangedProtectionRetention = 1
    [ 20]
    Limits
    --------------
    [ 20]   MaxSessions               = 1000
    [ 20]   MaxBSessions              = 500
    [ 20]   MaxMaPerSm                = 100
    [ 20]   MaxDaPerMa                = 32
    [ 20]   MaxNumberOfMirrors        = 5
    [ 20]   MaxSessionsPerDay         = 100000
    [ 20]
    Cell Server
    --------------
    [ 20]   CrsPort                   = -1
    [ 20]   CheckVersions             = 1
    [ 20]   MaxWaitForSm              = 120
    [ 20] * SchedulerGranularity      = 15
    [ 20] * DailyMaintenanceTime      = "13:00"
    [ 20] * DailyCheckTime            = "13:30"

Children
  • You can use the script to set and reset omnirc parameters only. Removal is not possible, since I'm not able to query the remote system unless I can name the parameter. It is not possible to query undefined omnirc parameters (default value compiled in).

    The -debug 20 output will only list global options. omnirc parameters are not global, they are module specific. This means generating an overview is a major problem since a parameter in VBDA does not have to exist in VEPA and vice versa.

    Regards,
    Sebastian Koehler