Environment
NetIQ Security Solutions for iSeries 8.0
Remote Request Management 8.0
Situation
I've changed my alerting parameters for FTP in RRM, but I'm not seeing all my rejected transactions now.
RRM Jobs Generate alerts inconsistently.
Resolution
When changing RRM default values, you must cycle your remote servers for changes to take effect immediately. If you do not cycle your remote servers, jobs started before you change default values continue to use the original settings. Any jobs started after you change the default values use the updated settings, causing jobs to run with inconsistent configuration settings.
To cycle your remote servers:
- From the NetIQ Product Access Menu, type 2 (PSSecure) and press Enter.
- Type 3 (Remote Request Management) and press Enter.
- Type 30 (Manage RRM) and press Enter.
- Type 3 (Cycle Remote Servers) and press Enter.
- Ensure the value for each parameter is correct.
- Press Enter.
Cause
In order for changes to RRM configuration to take effect, host servers must be recycled because the RRM defaults are retrieved only once by the exit program when the server job starts.
Additional Information
Values for servers can be:
*ALL
*CENTRAL
*DATABASE
*DDM
*DTAQ
*FILE
*FTP
*NETPRT
*REXEC
*RMTCMD
*SIGNON
*TELNET
*TFTP
*WSG
See NETIQKB46681 for additional information about the RRM Cycle step. An IPL or going to Restricted State will accomplish the steps in the RRM cycle if you have either event planned.
Exit Points must be in "Secure Mode" -- *YES before alerts will be sent.
See NETIQKB30986 for additional information regarding alerts.