cwood1009

How I did the vrf seperation is create groups for the different vrfs and have the subnets of each of the vrfs in different groups. We dont have any overlapping subnets, but IPAM allows duplicate subnets however I dont see how automatic scanning would work with this since you just have one IPAM scanner.

also include Cisco ACE

Yes this is all about MPLS. In the network tab it pulls in the “global” routing table, but none of the routing tables in the VRFs are displayed.

This I would think would be very easy to implement and much needed. Today you cannot search anything subnet related. We have custom properties we assign to subnets and you cannot search for them.

Orion does not currently pull in ip addresses from all vdc's in Nexus environments. just the global ip addresses. It does pull in the routing table for the VRF's in the Nexus 7k environment.

Would like it to remember filters, or be able to define filter templates, so when you import from discovery scans you dont have to re-massage the filters to select what you want.

Main things that I find annoying as my Orion system has grown. 1. Web sluggishness - when going into a node details it can be rather sluggish. 2. Compliance Report Updating - would like to be able to update a single report 3. Executing Scripts/Downloading Configs. Would like an option to download configs on a set of nodes…