Hi,
It seems that I cannot modify the node selection for reporting at the report level. It would appear that I have to modify the individual policies to filter out specific nodes? Surely this cannot be the case?
Jonathan
One more thing. If my boss comes down the hall and wants a report of all Cisco routers within the Americas Region, but sub netted to five particular ranges, and I have 9 different policies applied to a report, I have to go into each individual policy and modify the node selection to achieve my desired report results. How could a development team actually release a product with this type limitation and expect it to be used in the real world?
Can you give an example of what it is that you are trying to do?
For example, I have a policy titled "AAA Policy" that is a global policy to be applied to every single Cisco device. Within that policy I have 9 rules. When there is a configuration violation, its a lot easier having your rules very granular so that someone reading the report knows exactly why that device is out of compliance. But that is a different feature request....
If I want to report on only Cisco AP's within the Asia Pac region, then I have to modify that individual policy, instead of creating a new report based on Cisco AP's within the Asia Pac region. The issue is that AAA policy is already assigned to other reports running as a scheduled task. I do not want to modify a policy that could interfere with automatic reporting.
It seems that if I want to report on specific regions, or devices, that the selection criteria should be at the report creation level and not at the policy level. Maybe I am doing something wrong. But if this is the case, then I need to create new policies just to generate a granular report.
