Unicenter NSM Scalability r11

Transcript Unicenter NSM Scalability r11

Unicenter Network and Systems Management (NSM)

Preliminary Scalability Recommendations for r11 Last Updated 12/14/05

Objective

Primary objective: present sizing recommendations for the following Unicenter NSM components: MDB DSM* Agents Visualization Options (MCC, UMP, Classic 2D map, etc) * Scalability recommendations for Event and Job Management and more detailed guidelines for DSM are provided in separate presentations © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

The Architecture

Unicenter NSM r11 Architecture

Components

Common Unicenter Installation Configurations: “Enterprise Manager” – includes all management components, incl. a

local

MDB “Infrastructure Server” – includes all management components using a

remote

MDB “Managed Node” – identifies an “agent” machine that includes system, performance, event, job or other agents.

“Management Command Center” – includes the main UI client interfacing w/ Enterprise Mgr or Infrastructure Server “Gui Config” – local UI (2D Map, etc.) © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Documented Minimum Recommendations UNIX

Enterprise Manager Configuration

(all management components + local MDB): CPU P4-2 GHZ, P4-2.8 GHz RAM 2 GB - 4 GB or higher Hard drive 6 GB - 20 GB

Infrastructure Server Configuration

(all management components - remote MDB): CPU P4-2 GHZ Server Class computer or higher RAM 1GB -2 GB or higher Hard drive 4 GB - 8 GB

Managed Node Configuration:

(System, Performance and Event Agents): CPU PIII-550 MHZ, PIII-800 MHz RAM 512 MB - 1 GB or higher Hard drive500 MB1 GB -

Management Command Center Configuration

(main GUI client to Infrastructure or Enterprise Server): CPU P4-1.8 GHZ P4-2.6 GHz RAM 512 MB - 1 GB or higher -

GUI Configurations

(any local GUI configurations): Hard drive1 GB - 2 GB Recommended Video:32 MB DirectX-True Color TNT2 Monitor17” @ 1024 x 76821” @ 1600 x 1200

Swap Space:

For all of the required hardware configurations, we recommend that you configure swap space to be at least two times the size of RAM on the computer.

Documented Minimum Recommendations Windows

Enterprise Manager Configuration (

all management components + local MDB) CPU P4-2 GHZ P4-2.8 GHz RAM 2 GB - 4 GB or higher Hard drive 6 GB - 20 GB

Infrastructure Server Configuration

(all management components - remote MDB) CPU P4-2 GHZ Server Class computer or higher RAM 1GB - 2 GB or higher Hard drive 4 GB -8 GB

Managed Node Configuration

Performance and Event Agents) (System, CPU PIII-550 MHZ PIII-800 MHz RAM 512 MB - 1 GB or higher Hard drive 500 MB1 GB

Management Command Center Configuration

(main GUI client interface to an Infrastructure or Enterprise Server): CPU P4-1.8 GHZ - P4-2.6 GHz RAM 512 MB - 1 GB or higher Hard drive1 GB2 GB -

GUI Configurations

(any local GUI): Video 32 MB DirectX-True ColorTNT2 Monitor17” @ 1024 x 76821” @ 1600 x 1200 -

Note:

We recommend letting the Windows operating system manage virtual memory, rather than specifying an absolute value. If you decide to specify an absolute value, we recommend that value be at least 1.5 times the physical amount of real memory (RAM) on the computer. Virtual memory must not be less than 2 GB if installing the Ingres Server.

Note:

You may see messages stating that one or more other CA services have failed to start if the computer does not have the minimum necessary resources to support the installed components. In many cases the services may in fact be operational shortly after the error message, while in other cases they may fail due to insufficient resource availability, causing other cascading failures. The overall stability of your system may be affected if you install this product on systems with insufficient resources.

What you need to know

Number of locations Number of boxes at each location Bandwidth from each location to central/managing site Network and firewall restrictions Failover/Fault Tolerance requirements © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Other Factors

Optimization and tuning tips to enhance scalability NSM Discovery requirements ?

Dedicated or shared machines?

Planning for future growth Best practice guidelines for filtering, monitoring and policy can reduce load © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

The MDB

MDB/Enterprise Database Level

MDB – single database containing common tables and multiple product-specific tables previously contained in separate product dbs (e.g., CORe) Stores all WV data As # rows increases, table size increases as well as disk space Db does not just need db location disk space but also work location space (e.g., for sorting, temp and transient files w/in db. © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Single or Multiple?

Multiple MDBs can be used to accommodate large # managed objects (MOs), organizational requirements or network considerations Distributed MDB – component dbs on dif computers (e.g., remote or local MDB) Should always have one enterprise MDB serving as central db (provides complete view of env. Status that other prod install can use Repository Bridge can synchronize multiple MDBs © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Single, Double or More?

Multiple applications can use the same MDB – in fact the more apps using the MDB, the richer the data Solution A Solution B MDB Solution C Solution D © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

MDB Planning Guidelines

Use of Reiser file system is NOT recommended (not suitable for large dbs) Incr. computer reqs as necessary for enterprise MDB when MDB is integrating info for multiple CA prods MDB is business critical! S/b highly available Locate close to majority of users who require access Cannot be installed on Windows Domain Controller © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

MDB Sizing Implications for for WV

MDB capacity required to store WV data depends on size of your network Min. 2 rows per WV obj (w/all properties) An additional WV obj created for each net device w/ an agent Each net object can have multiple agents! For example: 10 full subnets (254 obj per subnet): 2540 * 2 = 5080 rows If each obj has average of 4 agents, need an additional 20,320 rows (2540 * 4 * 2). If each wv obj has one row per parent/child rel’ship inclusion (12700) © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

MDB Sizing Implications for Enterprise Mgt.

Calendar Mgt: 1 row per Calendar (100 calendars = 100 rows) Event Mgt: 1 row per message policy, message action and console view 100 msg policies + 200 message actions + 50 console views = 350 rows Security Mgt: 1 row per user, user group, asset type, asset group and permit rule. Approx. 200 predefined asset types and 1000 predefined permit rules created during installation. # permit rules can equal #user groups * #asset groups 6 users groups * 200 asset types = 1200 rows Once defined and loaded into the MDB, Enterprise Mgt data is primarily static and does not grow substantially over time w/o user interaction!

MDB Sizing Implications for Perf. Mgt

Content and granularity of perf data stored in MDB is configurable Primary MDB tables for Perf Mgt incl: machine, resource, day, time and data # machines * # resources * # days * # time int. = # rows For ex: 1 (machine) * 10 (resources) * 30 (days) * 1440 (minute intervals in the day) = 432K rows!

Rule of Thumb for MDB Sizing

20K objects is max for highly active MDB 25K objects is max for MDB w/o tuning 100K objects is max for any Windows MDB outside lab Use bridge to bring subset of key objects to higher level virtual MDB Use additional MDBs if objects > 2000 Of course, you can use a giant MDB with tuned DASD and extend this 100-500% but you cannot typically support a large enterprise with everything on one MDB © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Management Servers

Managers

WorldView Distributed State Machine (DSM) Continuous Discovery Event Alert Job Status © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

WorldView Manager Guidelines

Monitors MDB for changes to WV objects, propagates severity and populates Dynamic BPVs.

Best Practice – must reside on MDB server Neither WV Mgr nor MDB can be installed on Windows Domain Controller © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

DSM Manager

Manages Agents and provides 1 st level of fault correlation Mission critical – must be able to failover (i.e., minimum 2 DSMs!) > 200 hosts – use multiple DSMs # objects depends on poll interval, amt of memory, number of processes running, hard drive speed, connex speed, pollset efficiency, type of policy Max. 20K MO’s per/Windows based DSM* (Linux/UNIX DSMs max may be higher) Max. 50K MOs over a local area with tuning (e.g., adjust polling intervals) but server should have more than 1GHz CPU with 1GB RAM or more. 10K MOs max. if polling remote locations w/ slow connex (fewer would be better). If monitoring >100K mo’s w/ single DSM, that DSM s/b on dedicated server See DSM Scalability Considerations for Unicenter NSM r11 presentation for more details * based on Intel architecture w/ Pentium III (700Mhz) 512 RAM and 4 GIG or more of disk space © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Continuous Discovery Manager

Consolidates discovery information gathered by data collectors with the MDB Updates MDB when new device is discovered on network by agent © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Event Manager

Focal point for managing enterprise events Can have multiple event managers if needed Use escalation hierarchies if possible (filter and forward) and be as generic as possible with messages/actions Use color-coding to filter messages in console 80/20 rule (some msgs vital;most trivial) Use text matching rather than scan where possible in message record definitions Consider non-root event agents on Linux or UNIX for increased security Should be as close as possible to objects it communicates to Avoid lower level event mgrs and “forward all” Event Agents only require DSB -

Very scalable

– can handle large volumes of msgs; place where localized action is most effective – see Event Scalability presentation for details!

Alert Manager (AMS)

Can specify situations that create alerts, define alert policies View and manage alerts in multiple panes of MCC Can link to Unicenter Service Desk s/b as close as possible to its corresponding event mgrs Multiple AMS supported; cannot “stack” or forward alerts (use Event Mgr to filter and forward and place AMS at top of hierarchy) © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Job Manager

Controls job scheduling Multiple job managers supported; multiple platforms Remote CAICCI required for xplat scheduling 1 agent can be scheduled by multiple mgrs Place on any host that runs/schedules production work (usually coupled with Event and DSM locations) s/b mission critical computer!

See Job Management Scalability presentation for more details!

Managed Node Scalability

The Agents

Event Agent Job Agent Operating system Log files Performance Etc.

Use proxies or Remote Monitoring to monitor platforms w/o supported agents Minimal footprint!

Visualization

Visualization Components

Management Command Center (new for r11) WorldView (Maps, Class and Object Browsers, Viewers, Wizards) Unicenter Browser Interface (Remote and web-based viewers) Unicenter Management Portal Unicenter Remote Monitoring Web Reports and Dashboards Unicenter Configuration Manager Classic Enterprise Management © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

General Recommendations

For each UI, ensure adequate response and access among WV clients, and both MDB Enterprise level and associated management points © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Local UIs

Windows Workstation/Server: 128 MB RAM min. for simple delta mode used (see 2D scalability presentation) 256 MB if > 2K objects or complex maps 512 MB for > 10K objects or same as CORe box © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Classic 2D Map – Some Sizing Tips

2D map w/ 109,260 objs (w/remote Ingres MDB) 8 minutes to launch in non-delta mode 1 minute in delta mode On average – 32.5 events processed per second © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Unicenter Management Portal

Windows: 500 MHz processor, 512 MB RAM UNIX: 300 MHz processor, 512 MB RAM 800 MB disk space for installation (1GB rec.). 400 MB for DIA and 400 MB for Portal © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.