theguard! Service Management Center (Valid for Version 6.2 and higher)

Transcription

1 theguard! Service Management Center (Valid for Version 6.2 and higher)

2 Introduction about the minimal system requirements of theguard! Service Management Center. The theguard! Service Management Center is primarily a system of interactive client applications and central communication servers. Clients are required to log in to communication servers, are registered there, and then acknowledged to the other client applications. This is the very heart of the system, with as many other processes as necessary grouped around this core in order to do justice to the respective tasks. Client applications do not necessarily have to run on only one computer, they can also be distributed throughout the network as required. All of the applications necessary to ensure basic functioning are delivered together as one package the base system. The following documentation gives you an overview of all minimum system requirements including network particulars, sizing of memory and disk space. It does not replace the standard documentation which contains far greater and fundamentally important information. System requirements: Single user systems theguard! NetworkManager Advanced Version (500/5000) Hardware Processor Intel Core2 Duo 2x2,0 GHz or compatible 2 GByte RAM (4 GByte recommended) At least 50 GByte fixed disk space free Monitor with 1280x1024 resolution (1680x1050 recommended) 100 MBit network card (1 GBit recommended) For distributed installations (e.g. dedicated embedding of an external SQL Server system) an additional network iterface card is needed Software Windows XP Professional SP 2 or Windows 2003 Server SP 1 (Windows Server 2003 R2 recommended) Internet Protocol (TCP/IP), SNMP (Simple Network Management Protocol) and Internet Information Services (IIS) Microsoft Internet Explorer 6 SP 1 (Microsoft Internet Explorer 7 recommended) Copyright REALTECH AG 2008 Page 2 of 14

3 System requirements: Multi user systems theguard! ServiceDesk Hardware Processor Intel Core2 Quad 4x2.4 GHz or compatible 4 GByte RAM (8 GByte recommended) At least 100 GByte fixed disk space free Monitor with 1280x1024 resolution (1680x1050 recommended) 100 MBit network card (1 GBit recommended) For distributed installations (e.g. dedicated embedding of an external SQL Server system) an additional network iterface card is needed Software Windows 2003 Server SP 1 (Windows Server 2003 R2 Enterprise Edition recommended) For administration of more than 4 GByte RAM, Windows Server 2003 (R2) Enterprise Edition is needed as operating system! Internet Protocol (TCP/IP), SNMP (Simple Network Management Protocol) and Internet Information Services (IIS) Microsoft Internet Explorer 6 SP 1 (Microsoft Internet Explorer 7 recommended) Microsoft SQL Server 2005 Standard Edition SP 2 theguard! NetworkManager Terminal Server Edition Hardware Processor Intel Core2 Quad 4x2.4 GHz or compatible 4 GByte RAM (8 GByte recommended) At least 100 GByte fixed disk space free Monitor with 1280x1024 resolution (1680x1050 recommended) 100 MBit network card (1 GBit recommended) For distributed installations (e.g. dedicated embedding of an external SQL Server system) an additional network iterface card is needed Copyright REALTECH AG 2008 Page 3 of 14

4 Software Windows 2003 Server SP 1 (Windows Server 2003 R2 Enterprise Edition recommended) For administration of more than 4 GByte RAM, Windows Server 2003 (R2) Enterprise Edition is needed as operating system! Internet Protocol (TCP/IP), SNMP (Simple Network Management Protocol) and Internet Information Services (IIS) Microsoft Internet Explorer 6 SP 1 (Microsoft Internet Explorer 7 recommended) Microsoft SQL Server 2005 Standard Edition SP 2 Microsoft Terminal Services For every tg! SMC-Administrator license also a Terminal Server Client license must be capable! Alternatively for Microsoft Terminal Services also CITRIX ICA can be used. For every tg! SMC-Administrator license a CITRIX Client license must be capable! theguard! NetworkManager Terminal Server Edition (clients) Hardware Monitor with 1280x1024 resolution (1680x1050 recommended) 100 MBit network card Software Microsoft Terminal Services client software (Microsoft Remote Desktop Connection recommended) Alternatively for Microsoft Terminal Services also CITRIX ICA can be used. Copyright REALTECH AG 2008 Page 4 of 14

5 System requirements: Multi Site systems theguard! Multi Site Edition (Central Site Server) Hardware Processor 2 x Intel Core2 Quad 4x2.4 GHz or compatible 8 GByte RAM (16 GByte recommended) At least 100 GByte fixed disk space free Monitor with 1280x1024 resolution (1680x1050 recommended) 100 MBit network card (1 GBit recommended) For distributed installations (e.g. dedicated embedding of an external SQL Server system) an additional network iterface card is needed Software Windows Server 2003 R2 Enterprise Edition For administration of more than 4 GByte RAM, Windows Server 2003 (R2) Enterprise Edition is needed as operating system! Internet Protocol (TCP/IP), SNMP (Simple Network Management Protocol) and Internet Information Services (IIS) Microsoft Internet Explorer 6 SP 1 (Microsoft Internet Explorer 7 recommended) Microsoft SQL Server 2005 Standard Edition SP 2 Microsoft Terminal Services For every tg! SMC-Administrator license also a Terminal Server Client license must be capable! Alternativly for Microsoft Terminal Services also CITRIX ICA can be used. For every tg! SMC-Administrator license a CITRIX Client license must be capable! theguard! Multi Site Edition (Site Server) See theguard! NetworkManager Terminal Server Edition theguard! Multi Site Edition (clients) See theguard! NetworkManager Terminal Server Edition (clients) Copyright REALTECH AG 2008 Page 5 of 14

6 System requirements for Reporting and stand-alone SQL Server installation Hardware Processor Intel Core2 Quad 4x2.4 GHz or compatible 4 GByte RAM (8 GByte recommended) At least 100 GByte fixed disk space free Monitor with 1280x1024 resolution (1680x1050 recommended) 100 MBit network card (1 GBit recommended) For distributed installations (e.g. dedicated embedding of external tg! SMC systems) up to two more network interface cards are needed! Software Windows 2003 Server SP 1 (Windows Server 2003 R2 Enterprise Edition recommended) For administration of more than 4 GByte RAM, Windows Server 2003 (R2) Enterprise Edition is needed as operating system! Internet Protocol (TCP/IP), SNMP (Simple Network Management Protocol) and Internet Information Services (IIS) Microsoft Internet Explorer 6 SP 1 (Microsoft Internet Explorer 7 recommended) Microsoft SQL Server 2005 Standard Edition SP 2 Authorizations Local Administrator status is required for installation and operation. Logging into the terminal server is done through user accounts which have local Administrator privileges with the terminal server. The connection to SQL-Server must be done with a SQL Server user account, which owns sysadmin rights. Copyright REALTECH AG 2008 Page 6 of 14

7 Scalability In very large network operations, it may become necessary to increase system performance. A first recommendation for improving system performance is to increase memory size or utilize multi-processor systems. If this does not suffice, separate applications and databases, which requires a separated database server. If this still does not suffice, distributing of functions and tasks to several servers (see Multi Site Edition) is possible Separation of Application Server and Database Server: While cluster solutions, VMware and other such similar concepts are not supported at the present time, they should not be ruled out for the future. Dimensioning The bulk of the software installation, including documentation, is on theguard! computer. This requires about 1.1 GB of disk space: NetworkManager server Type of software Software size (MB) Microsoft SQL Server ~ 180 NetworkManager main components ~ 700 Basic databases ~ 220 Since the database size is contingent upon the number of and settings made for performance monitoring, using Microsoft SQL Server 2000/2005 or Microsoft SQL Server Desktop Engine (respectively 2005 Express) may become imperative, as may the paging to additional local hard disks. The disk capacity for database backups must also be taken into account. Since the MSDE (respectively 2005 Express) is subject to certain limitations (maximum database size of 2 GB, respectively 4GB), the MS SQL Server 2005 database is recommended for larger installations. Reporting requires the usage of MS SQL Server database and Reporting Services. For further information about dimensioning see respective documentation on the current software version. Copyright REALTECH AG 2008 Page 7 of 14

8 Network and network-component requirements The following settings must be made at the network components: A fixed IP address (not DHCP) should be set at the server. This is then to be set as the trap address for the network components. A high performance connection to DNS, alternatively a local host file, is necessary for automatic name resolution. Activate SNMP protocol. Configure community strings - especially to minimize the AutoDiscovery effort, focus on uniform GET and TRAP community strings! Configure TRAP IP address (IP address of theguard! NetworkManager computer/server) Reconfigure conceivable security configurations of computers authorized for SNMP polls (IP address of theguard! NetworkManager). Detailed information relating to these settings can be found in the respective documentation on the individual products. If firewalls are used, the firewall must allow the following services: TCP/IP between all servers Specific ports must be opened (also refer to the additional documentation on theguard! Applications and Firewalls ) ICMP (ping) and SNMP between theguard! NetworkManager server and the managed nodes All software components require a transparent TCP/IP connection between the computers on which they run. Miscellaneous The Microsoft SQL Server (Version 2000) or Microsoft SQL Server Desktop Engine (MSDE) are not components which are automatically included with theguard! NetworkManager; they need to be ordered at the same time or acquired separately. Please note that the Standard Edition will no longer suffice for servers which use more than 4GB of internal memory. When using Windows 2000 servers, the Advanced version must be used and when using Windows 2003 servers, the Enterprise Edition. A web server (Microsoft IIS) is needed in order to use the WebGUIs. This component is not included in the package as delivered, although it is an included component of the Windows 2000/2003 servers. Copyright REALTECH AG 2008 Page 8 of 14

9 System specification The capability of theguard! NetworkManager depends on the system environment, on which it is installed. Although the following items influence the capability: Performance and type of CPU Number of CPUs Memory size Usage of swap file Access time to harddisks Distributed installation of single system processes (e.g. database) Windows operating system The specified requirements are considered as least requirements to the respective basic system variant. System- and network environment The theguard! NetworkManager is designed for management of usual system- and network environments. These usually consist of active network components(hubs, Core-Switches, Desktop-Switches, etc.) servers, connected at them (Windows, Unix, etc.) respectively terminals (PCs, printers, etc.) other components (e.g. monitoring system for air conditioning, UPS devices, etc.) Although the maximum number of 5000 nodes respectively 500 nodes at a Single User Advanced 500 Edition must not be overthrown. Monitoring functions (periodical polling) The monitoring of a network occurs on the one hand by active polling, and on the other hand by analysis of Event messages (Traps, Syslogs, etc.). Both methods offer advantages and disadvantages. Both, active polling and a high number of events, can lead to a high workload of the system. For this reason both methods must be carried out in practice in a mixed mode. The system environment, described above, can be monitored on status and performance parameters. Typical monitoring items are: Monitoring of active network components Node status Status of server-, respectively uplink-ports Performance of server-, respectively uplink-ports (utilization, error rate) Performance of processors (CPU-utilization) at Core-Switches, Core-Router, etc.) Monitoring of servers Node status Status von system processes (services) Performance of processors (CPU-utilization) at Core-Servers Copyright REALTECH AG 2008 Page 9 of 14

10 Monitoring of terminals Node status of important terminals like department printers, etc. Monitoring of other components Node status of important components Performance data of important components Common monitoring and statistical functions Further monitoring and statistical functions can be used on demand. These are usually: Long-term recording of performance data of Uplink- respectively server ports Long-term recording of performance data of CPUs of important components (e.g. server, core-switches respectively. router, etc.) Monitoring and long-term recording of response times of important components Never use these methods area wide! Performance data an configuration parameters This table shows some typical configuration parameters for the following system configuration: Server/Pentium IV 2,4 GHz RAM 2 GByte Windows 2003 Server (SP 1) Monitored components of a typical system- and network landscape (interval between the single polls here is 60 seconds) by the following table: Periodical monitoring functions (Polling) Component (Node) Amount of Nodes Amount of Status Polls per Node Sum of all Status Polls Core Router Router Core Switches Switches Main Servers Server PCs Printer Other Sum of all polls per minute Sum of all polls per second 167 Copyright REALTECH AG 2008 Page 10 of 14

11 Configuration parameters for the above given example Function Default Settings Example System Configuration Active monitoring (periodical polling) Max polls per second Max active SNMP requests 0 (unlimited) 0 (unlimited) Max active Ping requests 0 (unlimited) 0 (unlimited) Max active TCP requests 0 (unlimited) 0 (unlimited) Max active Http requests 0 (unlimited) 0 (unlimited) Max active Winnet requests 0 (unlimited) 0 (unlimited) Another 30% willbe added to the calculated value (167) of the above given example for means of performance, to buffer possible peaks. These configuration parameters affect the polling server. Additionally values can be stored in a long-term database (Performance data are handled by History server).of course theintervall of the polling job has a high influence. These values have to be adapted to a particular system environment, further information can be found at the product documentation. Statistical requests Long-term statistical requests with threshold control occur by History Server. Thus,single values are polled in an optimized way, e.g., following values of a port statistic result: Complete Port Statistics: Polls Byte (DB) Comment Speed 1 0 Property Duplex 0 0 Property Octets 0 8 Calculated Frames 0 8 Calculated Utilization 0 8 Calculated Errors 0 8 Calculated In Discards 0 8 Out Discards 0 8 Interval 0 8 Calculated Poll Count 1 56 To request one port statistik, only one poll is necessary. The pollcount in the table has to be extrapolated per statistic. Never use these statistic requests areawide! Threshold definitions In the following there are some threshold definitions for usual network ports/interfaces. These are values learned by experience, which can be adapted lower or higher, related to the local conditions Copyright REALTECH AG 2008 Page 11 of 14

12 Ethernet 10 Mbit Net load (upper threshold 70 %, lower threshold 40 %) Bytes / sec = 100 % Bytes / sec = 70% Bytes /sec = 40 % Bytes / sec = 10% Packets (at an average packet size of 255 Bytes) 5000 / sec = 100 % 3500 / sec = 70 % 2000 / sec = 40 % 500 / sec = 10 % Threshold values relay to an average net load of 10% Indication Threshold Reset with Collisions 100 / sec. 30 / sec. Broadcasts 500 / sec. 300 / sec. Multicasts 500 / sec 300 / sec. CRC errors 5 / sec. 3 / sec. Undersize 5 / sec. 3 / sec. Oversize 5 / sec. 3 / sec. Fragments 5 / sec. 3 / sec. Jabbers 5 / sec. 3 / sec. Drops (Indicator about current state of a RMON Probe) 5 / sec. 4 / sec. Complete error rate 5 / sec. 4 / sec. Calculation formula 10 Mbit /s = Bits/s Bits/s : 8 = Bytes (Octets) At an average packet size of 255 Bytes Bytes/ sec : 255 = = 5000 Pakete / sec. Copyright REALTECH AG 2008 Page 12 of 14

13 Ethernet 100 MBit (Fast Ethernet) Multiply all values of the threshold table by 10. Ethernet 1000 MBit (Gigabit Ethernet) Multiply all values of the threshold table by 100. External Event Handling Events, handled by theguard! NetworkManager, can commonly be separated into three groups. Generated events at status change Traps Events, generated by Event Forwarding (cascaded NM Multi Site Edition) To retrieve high performance and meaningful status information, the theguard! NetworkManager- integrated Event Manager must be configured by filter configurations, regarding to the network structure and organization of network management. Because this is individually specified, no conclusions regarding Generated events at status change will be made here. In common the processing speed depends on the hardware capability, thus, the following sample was used in this document: Measuring system The times in this document were recorded with this conditions: System configuration Server/Pentium IV 2,4 GHz 2 Gbyte RAM Windows 2003 Server (SP 1) 100 MBit network connection Microsoft Windows 2000 Advanced Server, SP3 Microsoft Data Access Pack (MDAC) 2.6 SP1 Database MS/SQL-Server 2000 (local) theguard! NetworkManager Terminal Server Edition v6.0 SP 2 For measuring such test programs were used, which generate on the one hand standardized traps (SNMP), and on the other hand theguard! NetworkManager specific events. These test programs were started on a second computer with identical configuration. Each 1000 traps, respectively events, were created and sent to the network management computer. This was repeated 10 times. The result are rounded mean values of these test series. A logfiles was created every time. Copyright REALTECH AG 2008 Page 13 of 14

14 Traps To receive external trap events, the usual Windows SNMP trap service is used. This service forwards to theguard! NetworkManager software. To interpret these traps, contents must be filled with related information from MIB database. So, the computing of a trap must be determined on the one hand at windows protocol stack, and on the other hand by theguard! NetworkManager. The part of computing was measured with 40/60 (Windows/NetworkManager) Since version 5.2 of theguard! NetworkManager an own trap server is used, so occasional system blocking are avoided. Syslogs theguard! NetworkManager can receive and compute external Syslog messages. In contrast to traps no interpretation by MIB database is necessary. Event Forwarding At larger networks several theguard! NetworkManager systems (Multi Site Edition) can be applied. In such a cascaded system environment one theguard! NetworkManager can forward events to an other theguard! NetworkManager system (Event forwarding). This events usually do not have to be interpreted, because the source system already provides all relevant data in plain text. Events are transferred to a configurable TCP- Port. By using this method, the transfer is a secure handling. Result Count per second Traps 131 Log entry Syslogs 156 Log entry Events (Event Forwarding) 177 Log entry Action Further information about REALTECH s software solutions: REALTECH AG Industriestr. 39c Walldorf Germany Tel Fax customer-services@realtech.com Copyright REALTECH AG 2008 Page 14 of 14