1. ADDM/CMDB Overview Ryan Kountz

2. Agenda About ICMM Project About ADDM Product Overview
Progressive PoC / Lessons Learned
Sample Data / Pattern Enhancements
Deployment Information
Production Rollout & Infrastructure
Rollout schedule /Scanning Strategy
Future Plans
About Application Signature

3. In Asset, Remedy or Atrium Interfaces
ICMM Project Goals ?
Mature CI Data
ADDM
Business App Portfolio
Other sources reviewed (SAN, network)
Control CI Data
Configuration Management Processes
Data Governance & Management
(for CMDB)
Use CI Data
In Asset, Remedy or Atrium Interfaces
Atrium Pilot
BAP PKE POC
Reporting

4. Project Goals vs. Long Team Goals
Mature Config Management
@ Progressive
Future projects
We are
here
Application CI Relationships
Liz
This picture represents our short and long term goals for the CMDB/Config Mgmt. James Gosnell previously presented the Config Mgmt Maturity Model BAM format).
To reiterate, this project is a first step in maturing our CMDB and Configuration Management at Progressive
Infrastructure Configuration Management
Data Maturity
CMDB Previously Deployed

5. ABOUT ADDM From this… Where are the best targets for virtualization?
What happens if we unplug this server?
Do we have unsupported software running in my production environment? 5

6. The “stack” of IT that supports a business application
To this…Indexed, Connected, Visible and… Automated
The “stack” of IT that supports a business application
The Business Application
Servers and Databases
Virtual
Environments
Switches

7. And this…Google Your IT (“ADDM”)”)
Dashboards
Dependency Maps
Change Intelligence
Reports
Drill-down detail
ADDM 9.x indexes the data center and returns intelligent results – in business context
Servers, software, business applications (CIs)
Dependencies
Business contextual information
Change events

8. How Does ADDM 9.x Do It? Discover Analyze Search & Report Integrate 8
IT environment is continuously discovered using low-impact agent-free discovery techniques, and third party data sources reconciled.
Analyze
Hardware, operating systems, software components, business applications and dependencies are recognized and mapped.
Search & Report
Simple search, visualizations, charts and reports on business applications and the IT environment are available on-demand
Integrate
Up-to-date, trusted configuration data and service maps are fed to key management systems such as BSM tools and CMDBs 8

9. ADDM POC Approach Approach Deployment: Install the ADDM infrastructure
Deploy ADDM to discover about 500 end points and test functionality and performance
Collect lessons to determine the optimal Production configuration for ADDM
Model the infrastructure (depicted within the scope of the POC configuration)
Model 2 applications
Deployment:
4 Virtual Appliances, 3 Windows Slaves
500 OSIs
CI details for H/W, OS, COTS and CI relationships

10. ADDM Lessons Learned
Installation (and upgrade) of appliances made simple due to packaging as VM images.
ADDM scanning load on individual server roughly equivalent to technical utilizing Remote Desktop – most performance tuning time spent on appliance sizing and CMDB sync.
Where your appliances / proxies live on the network is a critical piece of deployment, and can greatly simplify remediation efforts.
Be sure to obtain commitments for SMEs in all applicable areas – remediation of discovery issues / validation with domain experts will be a large portion of the project.
MAKE FRIENDS WITH SECURITY.
Product is extremely flexible – utilize this fact when attempting to find / model data in non-standard ways.

11. ADDM POC Results – Summary of Discovery
Instant summary of what has been discovered.
Screen shot of 'Home' tab

12. From this…

13. To this…

14. A discovered Microsoft Cluster
Within the cluster we can see two nodes. Are they configured correctly?

15. An Alternative view of a Cluster
Different cluster shown an alternate view.

16. Load Balancer VIP Pools – Progressive Enhancement

17. VMware Infrastructure

18. SAN Discovery (PGR Enhancement)

19. Progressive Application Modeling – GOPRO Functional Components

20. Progressive Application Modeling – GOPRO Functional Components

21. Application Modeling – GOPRO App Dependencies

22. Application Modeling – Remedy QA Application View

23. App Modeling – Remedy QA Application View ..Alternate Visualization

24. App Modeling – Remedy QA Application View ..Switch and VIP Dependencies

25. App Modeling – Remedy QA Application View
App Modeling – Remedy QA Application View ..Inferred Communication Details

26. ADDM Production Rollout
Infrastructure Deployment
Scanning Strategy
Rollout Timeline
Items of Interest

27. Infrastructure Deployment
Bunker East
1 Consolidator – Collects data
2 Scanners – Performs scans
5 Proxy Servers - Access domains
Bunker West
1 Scanner
3 Proxy Servers

28. Rollout Timeline Storage Design Complete
VM Appliances Installed and Storage Configured
Network Configured (first wave)
Non Production Scan starts this week
Bunker West and Western Target Scan
Bunker East DMZ & HSZ Scan
Remaining East Target Scan

29. Scanning Strategy
Scan daily, validate result of new targets in three week intervals
Avoid scanning when database backups are running
Scan when traffic is active to detect inferred cross-server communication
Potential scan times: 10PM – 1AM, 8AM – 11AM

30. Future Work
Integrate Application Portfolio with discovery and CMDB data.
Implement Application Signatures
Increased Application Modeling
Improve / Extend Discovery as needed

31. About Application Signatures
ADDM easily discovers 3rd Party Software Products, what about custom apps?
Too many custom apps to write custom patterns individually.
Most applications and components follow standard elevation process and use standard tools.
ISO/IEC provides guidelines for “tagging” software products.

32. About Application Signatures
Future work will integrate the creation and elevation of “software tags” into the software configuration management process
Integration with SCM Tools forces compliance
A simple pattern can manage the discovery and cmdb sync of most software products.
Effort saved can be spent on “true” application modeling efforts.

33. Questions?