HP Intelligent Management Center

Transcription

1 HP Intelligent Management Center Deployment and Hardware Configuration Schemes Document version: V5.10

2 Legal and notice information Copyright 2011 Hewlett-Packard Development Company, L.P. No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HEWLETT-PACARD COMPANY MAES NO WARRANTY OF ANY IND WITH REARD TO THIS MATERIAL, INCLUDIN, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein Page 2 of 28

3 Content Legal and notice information 2 Hardware requirements 4 Overall deployment requirements 4 imc platform deployment scheme 6 NTA/UBA deployment scheme 10 NTA deployment scheme (for processing NetStreamV5 or NetFlowV5 logs) 10 NTA deployment scheme (for processing sflow logs) 10 UBA deployment scheme (for processing NetStreamV5, NetFlowV5, NAT, or flow logs) 11 Deploying the NTA and UBA on one server (for processing NetStreamV5 or NetFlowV5 logs) 11 DI collectors deployment scheme 12 NTA deployment scheme (in cooperation with DI collectors) 12 UBA deployment scheme (in cooperation with DI collectors) 12 Deploying the NTA and UBA on one server (working with DI collectors) 13 SHM deployment scheme 13 APM deployment scheme (for Windows only) 13 SOM deployment scheme 14 UAM/CAMS/EAD/DAM deployment scheme 14 TAM deployment scheme 14 MVM deployment scheme 15 WSM deployment scheme 17 EPM deployment scheme 20 EoCM deployment scheme 21 VSM deployment scheme 22 IVM deployment scheme 22 BIMS deployment scheme 24 Software requirements 26 Operating system (x86-64-bit operating systems preferred) 26 Windows 26 Linux 26 Databases 26 Databases embedded in the imc 26 Oracle 11g release 1 and release 2 (on Linux only) 27 SQL server 2005 SP3 27 SQL server 2008 SP2 27 SQL server 2008 R2 27 Web browser Page 3 of 28

4 imc Deployment and Hardware Configuration Schemes Hardware requirements Overall deployment requirements Intelligent Management Center (imc) provides such services as the intelligent management platform, which includes resource management, alarm management, performance management, ACLM, icc, Syslog management, and VLAN management, and such components as user access management, EAD security policy, CAMS, TAM, MPLS VPN management, and WSM wireless service management. According to service requirements, a user can deploy the desired service components based on the imc. The i intelligent client includes the i management center software and the i intelligent client software. They are installed independently of the imc platform. For normal imc system operation and service processing that meets basic running environment requirements, imc distributed deployment and convergence management have the following server requirements: imc component imc Platform imc SHM Server requirements Standalone server (prima server) Standalone server is recommended, or the same server as the imc platform if the SHM dule manages less than 5000 NQA instances. An NQA instance is a test instance between the NQA client and NQA server. Standalone server is recommended: imc UAM imc EAD imc DAM imc CAMS imc TAM imc MVM If the imc Platform manages less than 100 devices, the UAM can be deployed on the same server as the imc platform, and the UAM can manage the same number of users as that when it is deployed on a standalone server. You can deploy the user self-service component on the same server as the UAM when the UAM manages no re than users. If the UAM manages re, deploy the user self-service component on another computer. HP recommends installing EAD and UAM on the same server. HP recommends installing DAM and EAD on the same server. HP recommends installing CAMS and UAM on the same server. Standalone server is recommended (If TAM manages less than 5000 devices, TAM can be deployed on the same server as the imc platform or UAM/EAD.) Standalone server is recommended, or the same server as the imc platform if the number of MVM audit link instances to be managed is less than Page 4 of 28

5 imc component imc NTA imc UBA imc WSM imc EPM imc EoCM imc VSM imc IVM imc BIMS imc QoSM imc APM imc SOM i Management Center i Intelligent Client Server requirements Standalone server is recommended. If the NTA processes re than 200 Mbps traffic, deploy the NTA on a separate server. Multiple NTA components can be deployed on separate servers respectively. Standalone server is recommended. If the UBA processes re than 200 Mbps traffic, deploy the UBA on a separate server. Multiple UBA components can be deployed on separate servers respectively. Standalone server is recommended, or the same server as the imc platform if the WSM manages less than 100 APs. This component can be installed on the same server as the imc platform. When the imc platform manages re than 200 devices, use a higher-level server configuration than the recommended server configuration. Standalone server is recommended, or the same server as the imc platform if the EoCM manages less than 2000 CNUs. Standalone server is recommended, or the same server as the imc platform if the VSM manages less than 5000 devices. Standalone server is recommended, or the same server as the imc platform if the IVM manages less than 1000 devices. Standalone server is recommended. When BIMS manages less than 100 CPEs, BIMS can be deployed on the same server as the imc platform. This component can be installed on the same server as the imc platform. Standalone server is recommended. When APM manages less than 100 nitors, APM can be deployed on the same server as the imc platform. Standalone server is recommended, or the same server as the imc platform if the number of SOM users is less than 50 and the number of equivalent CI nodes, which can be calculated based on the number of devices, is less than 500. Standalone server Authentication client installed on the desktop terminal If the user does not need the imc platform to provide network management but only needs service management through the UAM/EAD, NTA, and UBA, any of these components can be installed on the same server as the imc platform. For a system in which the UAM/EAD manages re than users, HP recommends you to install the user self-service component and Portal Web component on another server in distributed de, reducing the burden on the prima server. The following sections detail the server configuration requirements of the imc platform and each component. Caution: Some 32-bit operating systems support me of less than 4 B. Therefore, select me s based on operating system requirements. The following table lists the maximum me supported by some comn Windows operating systems. The data provided in the following table is for reference only. For the me s supported by different Windows operating systems, see the latest Microsoft documentation Page 5 of 28

6 Operating systems Standard Edition s 4 B 32-bit Enterprise Edition 32 B Windows Server 2003 SP2 / Windows Server 2003 R2 SP2 Datacenter Edition Standard Edition 64 B 32 B 64-bit Enterprise Edition 1 TB Datacenter Edition 1 TB Standard Edition 4 B 32-bit Enterprise Edition 64 B Windows Server 2008 SP2 / Windows Server 2008 R2 SP1 64-bit Datacenter Edition Standard Edition Enterprise Edition 64 B 32 B 2 TB Datacenter Edition 2 TB imc platform deployment scheme Before selecting the deployment schemes described in this section, understand the following: 1. In imc resource components, device states are polled eve one minute by default and device configurations are polled eve two hours by default. If the system needs to manage re than 3000 devices, the device state polling interval and device configuration polling interval need to be increased. An interval increase rule can be as follows: for eve 3000 devices, device states are polled eve one minute and device configurations are polled eve two hours. If the system needs to manage 6000 devices, the device state polling interval should be increased to two minutes and the device configuration polling interval to four hours. Alternatively, a user can configure different polling intervals depending on the importance of the devices managed. The imc provides the interface for configuring state polling and configuration polling intervals in batches. To configure state polling interval and configuration polling interval, log on to the imc, click Batch Operation under the Resource tab, and set the device polling parameters. 2. Collection unit: A collection unit is an instance collected eve five minutes and is calculated by using the formula 5 minutes/collection interval of a collection instance in minutes. A collection unit is an instance of performance collection indexes. For example, the collection of the CPU utilization ratio of a device is a collection unit, so is the collection of the input rate of an interface. Suppose a device has one CPU and one me dule and needs to nitor the output rates and input rates of ten interfaces. anwhile, device unreachability ratio and response time need to be nitored. The nitoring of one CPU occupies a collection unit, so does the nitoring of one me dule. The nitoring of the input rates of ten interfaces occupies ten collection units, so does the nitoring of the output rates of the ten interfaces. Device unreachability ratio nitoring occupies one collection unit, so does device response time nitoring. Therefore, this device occupies 24 collection instances. If eve collection interval of the instances is 5 minutes, this device occupies 24 collection units. If eve collection interval of the instances is 10 minutes, this device occupies 12 collection units. 3. To improve the input/output (I/O) performance, follow these guidelines: Page 6 of 28

7 imc Deployment and Hardware Configuration Schemes Restricted If the number of collection units is from 100 to 200, install two or re disks and a RAID card with a cache of 256 MB or re. If the number of collection units is from 200 to 300, install two or re disks and a RAID card with a cache of 512 MB or re. If the number of collection units is from 300 to 400, install four or re disks and a RAID card with a cache of 1 B or re. HP recommends you to set the RAID level to 5, which needs three or re disks. When you use re than four disks, HP recommends you to set the RAID level to imcinstalldir: Installation directo of the imc. 5. imcdatadir: Directo that stores data when the imc is deployed. 6. : Maximum me to be used by processes on the imc web server. It can be set to 1 B at st in 32-bit operating systems. If the is re than 1 B, use 64-bit operating systems. Versions before imc PLAT 3.20R2606P09 supports only 32-bit operating systems. For imc PLAT 3.20R2606P09 or a later version, the default is 2 B on a Windows 64-bit operating system and 512 MB on other operating systems. Follow these steps to change the : a. Stop the imc through the intelligent deployment nitoring agent. b. Run script directo\client\bin\setmem.bat 1024 in the windows environment or run script directo/client/bin/setmem.sh 1024 in the Linux environment to set the maximum to 1024 MB (the value ranges 256 to 1024). Make sure that the set ranges from 1/4 to 1/3 of the physical server me. c. Restart the imc on the Monitor tab of the intelligent deployment nitoring agent. 7. Modify the me option of the SQL server, so that the maximum SQL server me is half of the physical server me. 8. When multiple components are deployed in distributed de, the CPU/me configuration of the prima server should meet the highest requirement of these components. 9. The resource management and alarm management dule of the imc platform are the foundation of imc, and many components work depending on the two dules. HP recommends deploying the two dules on the prima server. 10. The number of cores mentioned below refers to the number of physical cores, and does not mean the number of virtual cores created by hyper treading. 32-bit Windows environment Collection units(1) frequency r y for data storage B 2-core CPU 4 B 3 B 5 to MB 60 B B 4-core CPU 6 B 1 B 3 B 10 to B Page 7 of 28

8 (1) A value in the range 5 means not starting performance nitoring or starting minor performance nitoring. This explanation to Collection units applies to all of the following environments. 64-bit Windows environment (recommended) 200 Collection units m o 30 B 2-core CPU 4 B 2 B 3 B 5 to B 200 to 1 1 to 2 2 to 5 5 to 10 10~ B 4-core CPU 8 B 2 B 3 B 10 to B B 6-core CPU 4 B 4 B 20 to B 200 B B 8-core CPU 8 B 5 B 30 to B 250 B B 16-core CPU 7 B 40 to B B 300 B 0~ B 24-core CPU B 40~ B CAUTION: To improve the I/O performance, follow these guidelines: If the number of collection units is from 100 to 200, install two or re disks and a RAID card with a cache of 256 MB or re. If the number of collection units is from 200 to 300, install two or re disks and a RAID card with a cache of 512 MB or re. If the number of collection units is from 300 to 400, install four or re disks and a RAID card with a cache of 1 B or re. HP recommends you to set the RAID level to 5, which needs three or re disks. If you use re than four disks, HP recommends you to set the RAID level to bit Linux environment 200 Collection units m o B 2-core CPU 6 B 3 B 5 to MB 60 B Page 8 of 28

9 B 4-core CPU 8 B 1 B 3 B 10 to B 64-bit Linux environment (recommended) Collection units frequency m o to 1 1 to 2 2 to 5 5 to 10 10~ 15 2-core 30 B 6 B 2 B 3 B CPU 5 to B core 50 B 12 B 4 B 3 B 10 to CPU 100 B core 60 B 16 B 6 B 4 B 20 to CPU 200 B core 80 B 24 B 8 B 5 B 30 to CPU 250 B core 100 B 32 B 12 B 7 B 40 to CPU 300 B 0~ B 24-core CPU B 40~ B CAUTION: To improve the I/O performance, follow these guidelines: If the number of collection units is from 100 to 200, install two or re disks and a RAID card with a cache of 256 MB or re. If the number of collection units is from 200 to 300, install two or re disks and a RAID card with a cache of 512 MB or re. If the number of collection units is from 300 to 400, install four or re disks and a RAID card with a cache of 1 B or re. HP recommends you to set the RAID level to 5, which needs three or re disks. If you use re than four disks, HP recommends you to set the RAID level to 0+1. SM dem (optional) The following dels are tested and verified that they can operate with imc. For re specifications about the SM dem, see the related product manuals: WaveCom M2306B WaveCom TS-WC1 (Q2403A) Wanxiang serial port SM dem (D-C1A) Wanxiang USB SM dem (D-U1A) Page 9 of 28

10 Wanxing USB min SM dem (D-MINI) WaveCom M1206B SM dem (chip: 24PL) WaveCom USB M1206B SM dem (chip: Q24PL, Q2403A) NTA/UBA deployment scheme The specifications and system requirements provided in this section is for deploying the NTA or UBA on a server. To improve performance especially in a network where the aunt of data is large, a user can deploy the NTA or UBA on multiple servers for data analysis. The NTAs or UBAs will work in distributed de. The NTA can process NetStream, NetFlow, and sflow data, and log data generated by DI collectors. The UBA can process logs in NetStream, NetFlow, NAT, or Flow formats and logs generated by DI collectors. The aunt of data processed by the NTA/UBA is great and disk input/output operations affect the writing of data into databases. If the required disk space is re than 200 B, install two or re disks and a RAID card with a cache of 256 MB or re. If the required disk space is re than 500 B, install four or re disks and a RAID card with a cache of 512 MB or re. If the required disk space is re than one TB, install four or re disks and a RAID card with a cache of one B or re. HP recommends you to set the RAID level to 5, which needs three or re disks. When you use re than four disks, HP recommends you to set the RAID level to 0+1. NTA deployment scheme (for processing NetStreamV5 or NetFlowV5 logs) Number of managed interfaces 1 E port or 10 FE ports Operating system frequency 2-core CPU 4 B 50 B 3 E ports or 30 FE ports 4-core CPU 6 B 100 B Windows 6 E ports or 60 FE ports 6-core CPU 8 B 200 B 10 E ports or 100 FE ports 8-core CPU 12 B 300 B 1 E ports or 10 FE ports 2-core CPU 6 B 50 B 3 E ports or 30 FE ports 4-core CPU 8 B 100 B Linux 6 E ports or 60 FE ports 6-core CPU 12 B 200 B 10 E ports or 100 FE ports 8-core CPU 16 B 300 B NTA deployment scheme (for processing sflow logs) Data in the following table is created at a sampling ratio of 20000:1 or above. The management scale should decrease in proportion with the sampling ratio Page 10 of 28

11 Number of managed interfaces 100 Operating system 2-core CPU 4 B 100 B Windows core CPUs 6 B 200 B core CPU 6 B 100 B Linux core CPUs 8 B 200 B UBA deployment scheme (for processing NetStreamV5, NetFlowV5, NAT, or flow logs) Number of managed interfaces 2 FE ports Operating system 2-core CPU 4 B 700 B 5 FE ports 4-core CPU 6 B 1.5 TB Windows 1 E port or 10 FE ports 6-core CPU 8 B 3 TB 2 E ports or 20 FE ports 8-core CPU 12 B 6 TB 2 FE ports 2-core CPU 6 B 700 B 5 FE ports 4-core CPU 8 B 1.5 TB Linux 1 E port or 10 FE ports 6-core CPU 12 B 3 TB 2 E ports or 20 FE ports 8-core CPU 16 B 6 TB Deploying the NTA and UBA on one server (for processing NetStreamV5 or NetFlowV5 logs) Number of managed interfaces 2 FE ports Operating system 2-core CPU 4 B 700 B 5 FE ports 4-core CPU 6 B 1.5 TB Windows 1 E ports or 10 FE ports 6-core CPU 8 B 3 TB 2 E ports or 20 FE ports 8-core CPU 12 B 6 TB 2 FE ports 2-core CPU 6 B 700 B 5 FE ports 4-core CPU 8 B 1.5 TB Linux 1 E ports or 10 FE ports 6-core CPU 12 B 3 TB 2 E ports or 20 FE ports 8-core CPU 16 B 6 TB Page 11 of 28

12 DI collectors deployment scheme Collected traffic CPU (In a Linux Redhat ES3/AS5 environment, the main frequency is greater than or equal to 2.5 Hz.) Disk Space 0 MB to 300 MB 1-core CPU 2 B 100 B 300 MB to 1 B 2-core CPU 4 B 100 B Capable of sampling statistics, DI collectors can perform dynamic sampling according to system load. Alternatively, a fixed sampling ratio can be set. When the aunt of traffic sent to the probe exceeds one B, DI collectors sample the traffic. NTA deployment scheme (in cooperation with DI collectors) Corresponding DI collected traffic 0 MB to 500 MB Operating system 1-core CPU 4 B 50 B 500 MB to 1 B Windows 2-core CPU 6 B 100 B 1 B to 3 B 4-core CPU 8 B 200 B 0 MB to 500 MB 1-core CPU 6 B 50 B 500 MB to 1 B Linux 2-core CPU 8 B 100 B 1 B to 3 B 4-core CPU 8 B 200 B UBA deployment scheme (in cooperation with DI collectors) Corresponding DI collected traffic 0 MB to 300 MB Operating system 1-core CPU 4 B 700 B 300 MB to 500 MB Windows 2-core CPU 6 B 1.5 TB 500 MB to 1 B 4-core CPU 8 B 3 TB 0 MB to 300 MB 1=core CPU 6 B 700 B 300 MB to 500 MB Linux 2-core CPU 8 B 1.5 TB 500 MB to 1 B 4-core CPU 8 B 3 TB Page 12 of 28

13 Deploying the NTA and UBA on one server (working with DI collectors) Corresponding DI collected traffic 0 MB to 300 MB Operating system 1-core CPU 4 B 700 B 300 MB to 500 MB Windows 2-core CPU 6 B 1.5 TB 500 MB to 1 B 4-core CPU 8 B 3 TB 0 MB to 300 MB 1-core CPU 6 B 700 B 300 MB to 500 MB Linux 2-core CPU 8 B 1.5 TB 500 MB to 1 B 4-core CPU 8 B 3 TB SHM deployment scheme The following table shows different management scales based on the number of NQA instances. Number of NQA 2.5 Operating system instances Hz) core CPU 2 B 100 B Windows/Linux core CPU 4 B 200 B APM deployment scheme (for Windows only) The default collection interval is 5 minutes for APM. The following APM deployment scheme is based on the default collection interval. If you change the collection, you must adjust the management scale accordingly. For example, when you change the collection interval to 10 minutes, you can double the management scale. System requirements Operating system Disk space 100 nitors 2-core CPU 4 B 10 B Windows/Linux nitors 4-core CPU 6 B 30 B Page 13 of 28

14 SOM deployment scheme 32-bit Windows/Linux environment SOM users frequency 3 Hz) 50 1-core CPU 4 B 512 MB 1 B 4 B core CPU 6 B 1 B 1 B 6 B 64-bit Windows/Linux environment SOM users 3 Hz) core CPU 4 B 1 B 1 B 4 B core CPU 4 B 1.5 B 1 B 6 B core CPU 6 B 2 B 1 B 8 B UAM/CAMS/EAD/DAM deployment scheme To get an appropriate UAM/CAMS/EAD/DAM deployment scheme for your network, use the tool "imc UAM and EAD Deployment Scheme Recommender." TAM deployment scheme 64-bit operating system (recommended) Number of managed devices 2.6 Hz) core CPU B 160 B core CPU B 320 B core CPU B 500 B Page 14 of 28

15 CAUTION: To improve the input/output (I/O) performance, use a dual channel Ultra 320 SCSI controller or higher with 256 MB cache or higher, and set the RAID level to 0, 1, 1+0, or 5. MVM deployment scheme Follow these guidelines when deploying MVM: 1. Make sure that the number of VPN devices does not exceed the imc platform license. When the number of VPN devices is larger than the license, manage the CEs as virtual CEs. 2. The MVM performance depends on the number of VPNs, in addition to the number of VPN devices and the number of CE-CE connections. It is a good practice to manage no re than 10 VPNs in one MVM. If you need to manage re VPNs, upgrade the hardware configuration to a higher level. 3. Deploy the MVM component on a different server from the imc platform in distributed de. 32-bit Windows environment 500 CE-CE connections per VPN Online m o B 2-core CPU B B 64-bit Windows environment (recommended) 500 CE-CE connections per VPN Online frequency r y B 2-core CPU B B to 2 2 to 5 5 to B 4-core CPU B B B 6-core CPU 6 4 B B B 8-core CPU 8 5 B B core B 12 7 B CPU B Page 15 of 28

16 CAUTION: To improve the I/O performance, follow these guidelines: If the number of CE-CE connections per VPN is from 1 to 2, install two or re disks and a RAID card with a cache of 256 MB or re. If the number of CE-CE connections per VPN is from 2 to 5, install two or re disks and a RAID card with a cache of 512 MB or re. If the number of CE-CE connections per VPN is from 5 to 10, install four or re disks and a RAID card with a cache of 1 B or re. HP recommends you to set the RAID level to 5, which needs three or re disks. When you use re than four disks, HP recommends you to set the RAID level to bit Linux environment 500 CE-CE connections per VPN Online frequency r y B 2-core CPU M 3 B B 64-bit Linux environment (recommended) 500 CE-CE connections per VPN B 2-core CPU 1 3 B B 500 to 1 1 to 2 2 to 5 5 to B 4-core CPU 4 3 B B core B 6 3 B CPUs 200 B B 8-core CPU 8 5 B B B 12-core CPU 12 7 B B Page 16 of 28

17 CAUTION: To improve the I/O performance, follow these guidelines: If the number of CE-CE connections per VPN is from 1 to 2, install two or re disks and a RAID card with a cache of 256 MB or re. If the number of CE-CE connections per VPN is from 2 to 5, install two or re disks and a RAID card with a cache of 512 MB or re. If the number of CE-CE connections per VPN is from 5 to 10, install four or re disks and a RAID card with a cache of 1 B or re. HP recommends you to set the RAID level to 5, which needs three or re disks. When you use re than four disks, HP recommends you to set the RAID level to 0+1. WSM deployment scheme Follow these guidelines when deploying WSM: 1. If an AP supports switching between fit and fat AP de, the AP as a fat AP and choose the hardware configuration according to the number of fat APs. 2. In a network configured with AC backup (1+1 backup or N+1 backup), choose the hardware configuration by twice the number of fit APs. 3. When the number of managed APs exceeds 100, deploy the WSM component in distributed de. When re than 8000 fit APs or 5000 fat APs exist in the service provider network, or when re than fit APs or 5000 fat APs exist in the enterprise network, you must deploy multiple WSM components. 4. It is a good practice to allow no re than 10. To allow re, select a hardware configuration of a higher level. 32-bit Windows environment Fit AP: 500 or Fat AP: 300 Collec tion units 50 Online 10 2-core CPU B 60 B 64-bit Windows environment (recommended) Fit AP: 500 Or Fat AP: 300 Colle ction units 50 Online 10 2-core CPU 4 for for data storage 1 3 B 60 B Page 17 of 28

18 Fit AP: Or Fat AP: Colle ction units 16 to 90 Online 10 4-core CPU 8 for for data storage 4 3 B 100 B Fit AP: Or Fat AP: to core CPU B 200 B Fit AP: Or Fat AP: 2000 to to core CPU B 250 B Fit AP: Or Fat AP: 3000 to 5000 in an enterprise network Fit AP: to core CPU B 300 B Or Fat AP: 3000 to 5000 in a service provider network CAUTION: To improve the I/O performance, follow these guidelines: If the number of collection units is from , install two or re disks and a RAID card with a cache of 256 MB or re. If the number of collection units is from , install two or re disks and a RAID card with a cache of 512 MB or re. If the number of collection units is from , install four or re disks and a RAID card with a cache of 1 B or re. HP recommends you to set the RAID level to 5, which needs three or re disks. When you use re than four disks, HP recommends you to set the RAID level to Page 18 of 28

19 32-bit Linux environment imc Deployment and Hardware Configuration Schemes Restricted Fit AP: 500 or Fat AP: 300 Collec tion units 50 Online 10 2-core CPU B 60 B 64-bit Linux environment (recommended) Fit AP: 500 Or Fat AP: 300 Colle ction units 50 Online 10 2-core CPU 4 for 1 3 B 60 B for data storage Fit AP: Or Fat AP: to core CPU B 100 B Fit AP: Or Fat AP: to core CPU B 200 B Fit AP: Or Fat AP: 2000 to to core CPU B 250 B Fit AP: Or Fat AP: 3000 to 5000 in an enterprise network Fit AP: to core CPU B 300 B Or Fat AP: 3000 to 5000 in a service provider network Page 19 of 28

20 CAUTION: To improve the I/O performance, follow these guidelines: If the number of collection units is from , install two or re disks and a RAID card with a cache of 256 MB or re. If the number of collection units is from , install two or re disks and a RAID card with a cache of 512 MB or re. If the number of collection units is from , install four or re disks and a RAID card with a cache of 1 B or re. HP recommends you to set the RAID level to 5, which needs three or re disks. When you use re than four disks, HP recommends you to set the RAID level to 0+1. EPM deployment scheme 32-bit Windows environment (ONU) ONUs per OLT Plat node operat ors frequency 2.5 Hz) for for data storage B 2-core CPU B B 64-bit Windows environment (recommended) (ONU) 1000 ONUs per OLT Plat node operat ors frequency 2.5 Hz) for data storage B 2-core CPU B B 1 to 2 2 to 5 5 to B 50 4-core CPU B B B core CPU 4 4 B B B core CPU 8 5 B B Page 20 of 28

21 CAUTION: If re than 2000 optical network units (ONUs) are connecting to an optical line terminal (OLT), the MIB interface performance of the OLT is poor. In this case, enhancing server performance does not solve the problem. EoCM deployment scheme Before you deploy EoCM, HP recommends you to configure the coaxial-cable line terminals (CLTs) and coaxial-cable network units (CNUs) at the ratio of 1:20. If the ratio is smaller, choose a server of a higher level. If the imc platform manages less than 50 devices, you can install EoCM on the same server as the imc platform. Otherwise, you must deploy EoCM on a seconda server. 32-bit Windows environment (CNU) Collection units(1) operat ors 5 30 B 2-core CPU B 5 to B (1) A value in the range 5 means not starting performance nitoring or starting minor performance nitoring. 64-bit Windows environment (recommended) (CNU) Collection units(1) frequency r y for for data storage 5 5 to to B 2-core CPU B 5 to B 50 B 4-core CPU B 5 to B B 6-core CPU 4 4 B 5 to B B 8-core CPU 8 5 B 5 to B (1) A value in the range 5 means not starting performance nitoring or starting minor performance nitoring Page 21 of 28

22 VSM deployment scheme Follow these guidelines when deploying VSM: 1. MSR voice gateways consume the imc platform license. For how to deploy the VSM server in a network where only MSR voice gateways exist, see the imc platform configuration requirements. 2. When no IP phones are in the network but software terminal applications exist, see the IP phone configuration requirements for traffic statistics. 32-bit Windows environment (IP Phone) 500 Call numbe r 100 to core CPU B 60 B 64-bit Windows environment (recommended) (IP Phone) 500 Call numbe r 100 to 200 opera tors 10 2-core CPU B 60 B to core CPU B 100 B 2 to to core CPU B 200 B 5 to 10 1 M to 2 M 10 8-core CPU B 250 B IVM deployment scheme The IPsec VPN uses the hub spoke de, so the number of spoke devices determines the number of nodes, and one hub device uses one device node from the license. See the imc platform configuration requirements for the IVM server deployment Page 22 of 28

23 32-bit Windows environment (Spoke device) 200 imc Deployment and Hardware Configuration Schemes Restricted Collection units (1) 4 30 B 2-core CPU 1 3 B 5 to B (1) A value in the range 5 means not starting performance nitoring or starting minor performance nitoring. 64-bit Windows environment (recommended) (Spoke device) 200 Collection units (1) operat ors 4 30 B 2-core CPU 1 3 B 5 to B to 5 5 to B 4-core CPU 4 3 B 5 to B B 6-core CPU 6 4 B 5 to B B 8-core CPU 8 5 B 5 to B B 12-core CPU 12 7 B 5 to B (1) A value in the range 5 means not starting performance nitoring or starting minor performance nitoring. 32-bit Linux environment (Spoke device) 200 Collection units (1) 4 30 B 2-core CPU 1 3 B 5 to B Page 23 of 28

24 (1) A value in the range 5 means not starting performance nitoring or starting minor performance nitoring. 64-bit Linux environment (recommended) (Spoke device) 200 Collection units (1) operat ors 4 30 B 2-core CPU 1 3 B 5 to B to 5 5 to B 4-core CPU 4 3 B 5 to B B 6-core CPU 6 4 B 5 to B B 8-core CPU 8 5 B 5 to B B 12-core CPU 12 7 B 5 to B (1) A value in the range 5 means not starting performance nitoring or starting minor performance nitoring. BIMS deployment scheme Follow these guidelines when deploying BIMS: 1. When the number of managed CPEs is re than 100, you must deploy BIMS and imc on different servers. 2. When the number of managed CPEs is re than 5000, HP recommends you to deploy multiple ACSs separately. 32-bit Windows environment data storage core CPU B 60 B Page 24 of 28

25 64-bit Windows environment (recommended) 200 imc Deployment and Hardware Configuration Schemes Restricted 10 2-core CPU B 60 B to 2 2 to 5 5 to core CPU B 100 B 10 6-core CPU B 200 B 10 8-core CPU B 250 B core CPU B 300 B 32-bit Linux environment data storage core CPU B 60 B 64-bit Linux environment (recommended) Hz) r y 10 2-core CPU B 60 B to 2 2 to core CPU B 100 B 10 6-core CPU B 200 B 10 8-core CPU B 250 B 5 to core CPU B 300 B Page 25 of 28

26 Software requirements Operating system (x86-64-bit operating systems preferred) Windows Windows Server 2003 with Service Pack 2 (32-bit) Windows Server 2003 with Service Pack 2 (64-bit) and patch B Windows Server 2003 R2 with Service Pack 2 (32-bit) Windows Server 2003 R2 with Service Pack 2 (64-bit) and patch B Windows Server 2008 with Service Pack 2 (32-bit) Windows Server 2008 with Service Pack 2 (64-bit) Windows Server 2008 R2 with Service Pack 1 (64-bit) Linux Red Hat Enterprise Linux Server 5 (32-bit) Red Hat Enterprise Linux Server 5 (64-bit) Red Hat Enterprise Linux Server 5.5 (32-bit) Red Hat Enterprise Linux Server 5.5 (64-bit) Red Hat Enterprise Linux Server 6.1 (64bit) Databases Databases embedded in the imc The maximum capacity of an SQL Server 2008 R2 Express database embedded in the imc is 10 B. If the total number of collection units of the platform components is less than 20, the total number of alarms saved in the database is less than , and the number of managed device nodes is less than 1000, you can use SQL Server Express databases. Otherwise, use external databases. For the NTA/UBA component, the volume of collected data is generally ve large and therefore embedded databases are not recommended. For the UAM, EAD, and CAMS components, the volume of data increases rapidly. Many factors contribute to the increase in database s, which often exceed the 4 B embedded database limit. Therefore, embedded databases are not recommended Page 26 of 28

27 For the MVM, which runs on the core network, stability is of vital importance and therefore embedded databases are not recommended. The WSM needs to summarize and analyze the large volumes of report data at the operator's office. The volume of data processed is large and embedded databases have a performance bottleneck. Therefore, embedded databases are not recommended. If the number of APs on an enterprise network exceeds 200, embedded databases are not recommended. For the EoCM component, if the number of CNUs exceeds 1000, embedded databases are not recommended. For the EPM component, if the number of ONUs exceeds 1000, embedded databases are not recommended. Oracle 11g release 1 and release 2 (on Linux only) For Oracle database versions, the numbers of CPUs supported are limited. When choosing a deployment scheme, see the following table (The data listed in the following table is for reference only. For the actual CPU support of different Oracle 11g Release 1 versions, see Oracle documentation). Oracle 11g Release 1 applies to Linux systems only. Number of supported CPUs Standard edition one Standard edition Enterprise edition 2 4 No limit Remarks Multi-core processors are supported. SQL server 2005 SP3 SQL server 2008 SP2 SQL server 2008 R2 For SQL Server versions, the number of supported CPUs and RAM s are limited. When choosing a deployment scheme, see the following table (This table takes for example the CPU and me support for SQL Server 2008 database versions. This is similar to the CPU and me support for SQL Server 2005 database versions. The data in this table is for reference only. For the actual CPU and RAM support for SQL Server 2008 database versions, see Microsoft documentation.) Number of supported CPUs Express Workgroup Standard Enterprise Remarks No limit Multi-core processors are supported. Supported me 1 B 4 B OS Max OS Max The me cannot exceed the maximum value supported by the operating system Page 27 of 28

28 Web browser imc Deployment and Hardware Configuration Schemes Restricted Turn off all the window blocking settings of the browser. Enable cookies on the browser. The client screen resolution should be at least IE 8 or later. Firefox 3.6 or later Page 28 of 28