Situation
When a request is sent to the iSeries agent for a time window, the time out counter is expecting the request to return within 60 mins. In the case of the customer, the request returned in a bit more than than (it was 1 min late).
When a request is being timed out, one of the information that get removed is "ScheduleId", so even when the agent returns the data a bit late, that schedule id is no longer valid and thus SM reject the data.
To map this to the customer case:
Request sent at 9/17/2007 @ 7:49 AM
Request timed out at 9/17/2007 @ 8:49 AM, SM raised windows event 31077 Agent returned data at 9/17/2007 @ 8:50 AM SM rejected the data at 9/17/2007 @ 8:50 AM because of no longer valid scheduleID and raised event 31026
Here is how we can solve this problem (do this on every SM Central Computer)
- There is a file called mk.options under Program Files\NetIQ Security Manager\OnePoint
- Backup the mk.options (just a pre caution)
- Edit the mk.options using notepad
- Change the value of the property: RequestTimeOutm=60 to RequestTimeOutm=1440
That will a 24 hours time out.
- Save the file
- Restart SM service
you might need to reset the schedule since the schedule window might be too large.
Resolution
The problem is because of the time out setting of 1 hour.
When a request is sent to the iSeries agent for a time window, the time out counter is expecting the request to return within 60 mins. In the case of the customer, the request returned in a bit more than than (it was 1 min late).
When a request is being timed out, one of the information that get removed is "ScheduleId", so even when the agent returns the data a bit late, that schedule id is no longer valid and thus SM reject the data.
To map this to the customer case:
Request sent at 9/17/2007 @ 7:49 AM
Request timed out at 9/17/2007 @ 8:49 AM, SM raised windows event 31077 Agent returned data at 9/17/2007 @ 8:50 AM SM rejected the data at 9/17/2007 @ 8:50 AM because of no longer valid scheduleID and raised event 31026
Here is how we can solve this problem (do this on every SM Central Computer)
- There is a file called mk.options under Program Files\NetIQ Security Manager\OnePoint
- Backup the mk.options (just a pre caution)
- Edit the mk.options using notepad
- Change the value of the property: RequestTimeOutm=60 to RequestTimeOutm=1440
That will a 24 hours time out.
- Save the file
- Restart SM service
you might need to reset the schedule since the schedule window might be too large.