Home > Managed Servers

Managed Servers

Managed Sysadmin Support – Windows 2003 Servers

The information provided below is for Windows 2003 Servers

Introduction

The managed server product is based around standalone Windows 2003 Servers (Standard edition or Web edition – no domains / active directories).

Features

Base Operating System:

  • 20 users created initially and 5 per month
  • Backups to either tape or backup+ (schedule can be daily, weekly or monthly) of up to 10 separate paths
  • Standard partitioning is 8Gb C: drive for Operating System, with the remainder of the drive set a separate disk used for data, logs and application storage

Virtual web hosting

  • 20 virtual hosts created initially and 5 per month
  • 1 Virtual Application per Virtual Host
  • IIS functionality supported:
  • SSL
  • ActivePerl
  • ASP
  • ASP.net (Note: Virtual hosts will be configured with ASP.NET 1.1 by default. Customer should advise if they require virtual hosts to be configured with ASP.NET 2.0)
  • PHP
  • Authentication (up to 5 authenticated directories per virtual host, with 1 user directory per month)
  • CDOSYS
  • Anonymous and user ftp (1 of each)
  • Terminal Services access


MS SQL Server 2005, MS SQL Server Express or MySQL 5

  • 20 database users created initially and 5 per month
  • 20 databases created initially and 5 per month

(NB: MS SQL Desktop Engine 2000 is limited to 5 concurrent database connections and so is only suitable for test or very, very low traffic web applications. Once the MS SQL Desktop Engine 2000 reaches 5 concurrent connections it will queue subsequent database connections which may cause web applications to time out.)

Pulsant recommend only one Database server is run concurrently. MySQL can be installed alongside MS SQL Server 2005 or SQL 2005 Express Edition for migration purposes.

Specifications

Base Windows 2003 Server with all latest service packs and hotfixes installed plus:

  • Indexing Service (with a limit of 5 catalogues initial setup, and 5 new catalogues per month)
  • IIS (with frontpage, ftp and smtp components)
  • Script Debugger
  • Terminal Services (remote administration or application mode)
  • ActiveState Perl 5.6.1 + Standard PPMs
  • PHP 4.4 (default, vanilla configuration)

If the customer requires any service or configuration not listed above then they should contact the sales team ([email protected]) to obtain a quote for Pulsant to provide these services.

Management

  • Pulsant will automatically apply critical level and all security hotfixes available from Microsoft informing the customer as this happens. In the case of a critical or security hotfix breaking site/server functionality, Pulsant will rollback. Prior notice may not be given due to the nature of the fixes and potential threat.
  • Other hotfixes or service packs will be applied only after the customer has been given 7 days notice.
  • Critical faults on the server will be dealt with 24×7, but customer-change requests will normally only be actioned within normal working hours (Monday – Friday, 9am – 5pm).
  • Customer-requested configuration changes can be arranged to happen outside of working hours, but these will be charged at the out-of-hours pro rata rate. All customer-requested configuration changes will be actioned within 1 working day of receipt in writing from the customer. The customer will be notified of any changes made to their managed server.

End user access

  • The end user shall be provided access to the server via one or more user accounts. Administrator access will not be permitted.
  • Users may access the system by Terminal Services, FTP or SMB from trusted static IP addresses. Up to 10 such addresses may be nominated.
  • Terminal Services are limited to 2 concurrent connections with a 10 minute idle timeout and customers must ensure 1 connection is available to Pulsant to carry out server management tasks on demand.
  • Changes to administrator level configurations shall be made by the web admin interface, or by request to the Pulsant support system.

System Monitoring

Hardware needs to be one of the following Dell Poweredge models:

  • 350
  • 650
  • 750
  • 850
  • 1850
  • 2550
  • 2650
  • 2850
  • 2950

The following checks will be monitored via Dell OpenManage Server Administrator’s (OMSA) SNMP interface:

Check Warning Critical Platforms supported
Fans N/A Any fan less than minimum failure threshold 350, 650, 750, 850, 1850, 2550, 2650, 2850, 2950 PV220
Memory Status “non-critical” as reported by OMSA Status other than “OK” as reported by OMSA 350, 650, 750, 850, 1850, 2550, 2650, 2850, 2950
Temp Greater than maximum warning thresholds or less than minimum warning thresholds in OMSA Greater than maximum failure thresholds or less than minimum failure thresholds in OMSA 350, 650, 750, 850, 1850, 2550, 2650, 2850, 2950, PV220
Voltage N/A Status other than “good” as reported by OMSA 350, 650, 750, 850, 1850, 2550, 2650, 2850, 2950
PSUs N/A Status other than “good” as reported by OMSA 1850, 2550, 2650, 2850, 2950, PV220
RAID array Status other than “ready” or “failed” as reported by OMSA Status “failed” as reported by OMSA 1850, 2550, 2650, 2850, 2950, PV220*
Disks Status other than “disk online” as reported by OMSA Status “disk failed” or “redundancy lost” as reported by OMSA 1850, 2550, 2650, 2850, 2950, PV220*
Disk utilisation 80% full 90% full 350, 650, 750, 850, 1850, 2550, 2650, 2850, 2950
CPU utilisation Linux: Load of 3
Windows: 95% utilisation
Linux: Load of 5
Windows: 97% utilisation
350, 650, 750, 850, 1850, 2550, 2650, 2850, 2950
IP Network Connectivity 25% packet loss or 500ms latency 75% packet loss or 1000ms latency All
HTTP availability Anything other than a 2xx or 3xx code returned 4xx or 5xx error codes or port 80 not available All
HTTP delay If request takes 10% and 100ms longer than last request If request takes 12% or 120ms longer than last request. Or if request takes longer than 1000ms in total. All
FTP availability N/A Anything returned other than FTP code 220 (server OK) All
SMTP availability N/A Anything returned other than SMTP code 220 (server OK) All
MySQL availability N/A Cannot get connected or logged in as specified user All
PostgreSQL availability N/A Cannot get connected or logged in as specified user Linux hosts only

 

 

*PV220 itself does not have OMSA capability and requires a Dell controlling head unit (e.g. 2850) in order to be monitored.

In order not to generate false positives, the monitoring system has to have 3 consecutive failure states to generate an alert.

Monitoring is only currently available under Sysadmin Support.

Managed Red Hat Enterprise Linux 5 Server – Sysadmin Support

Introduction

The managed server product is closely based on the Red Hat Enterprise Linux, version 5

Features

Base Operating System:

  • 20 users created initially and 5 per month
  • Backups to either tape or backup+ (schedule can be daily, weekly or monthly) of up to 10 separate paths. (Subject to purchase of a backup product)
  • All core system logging (syslog) is logged both locally and to a secure centralised system for audit purposes.
  • System disk partitioning:
  • 4 gig allocated to /
  • 2 gig allocated to /swap
  • 5 gig allocated to /var
  • 250 meg allocated to /boot
  • Remaining space on disk allocated to /data(which includes /home and /var/lib/pgsql)

Virtual web hosting (CGI, PHP, Perl, SSL)

  • 20 virtual hosts created initially and 5 per month
  • Apache modules/functionality supported:
  • mod_ssl.c, sapi_apache2.c, mod_cgi.c, mod_mem_cache.c, mod_file_cache.c, mod_disk_cache.c, mod_suexec.c, mod_cache.c, mod_rewrite.c, mod_alias.c, mod_userdir.c, mod_speling.c, mod_actions.c, mod_imap.c, mod_dir.c, mod_negotiation.c, mod_vhost_alias.c, mod_dav_fs.c, mod_info.c, mod_asis.c, mod_autoindex.c, mod_status.c, mod_dav.c, mod_mime.c, mod_setenvif.c, mod_unique_id.c, mod_usertrack.c, mod_headers.c, mod_deflate.c, mod_expires.c, mod_cern_meta.c, mod_mime_magic.c, mod_env.c, mod_log_config.c, mod_include.c, mod_auth_digest.c, mod_auth_dbm.c, mod_auth_anon.c, mod_auth.c, mod_access.c, mod_so.c, http_core.c, prefork.c, core.c
  • cgi-wrapper
  • Anonymous and user ftp server (1 of each)
  • Shell access and development environment

PostgreSQL and MySQL databases

  • 20 database users created initially and 5 per month
  • 20 databases created initially and 5 per month

Specifications (no Control Panels)

  • RedHat Enterprise Linux Release 5
  • Kernel 2.6.10 (RHEL Build)
  • Apache2 (2.2.3) *
  • OpenSSH Server 4.3 *
  • OpenSSH Client 5.3
  • Emacs 2.1
  • GCC 4.1.2
  • SNMP (net-snmp-5.1.2)
  • S.M.A.R.T. Tools for IDE based systems *
  • OpenManage system – Dell equipment only *
  • Perl 5.8.8
  • VIM 7.0

Optional Supported Packages Available

  • PHP 5.1.6
  • Tomcat 5.5.23 Red Hat Package with Sun Java 1.5.0, using proxy_ajp connectors.
  • VSftpd 2.0.5 *
  • Python 2.4.3
  • PostgreSQL Server 8.1.9 *
  • PostgreSQL Client 8.1.9
  • MySQL Server 5.0.22 *
  • MySQL Client 5.0.22
  • Postfix 2.3.3 (mail relay only) *
  • Sendmail 8.13.8 *
  • BIND DNS Caching server 9.3.3 *
  • SAMBA Server 3.0.25 *
  • SAMBA Client 3.0.25
  • External Download tools – wget and/or curl.
  • ImageMagick (C/C++/Perl libraries as appropriate)
  • NFS Server * (access only provided to other dedicated Pulsant hosted servers)

* means that the service is monitored

If the customer requires any service or configuration not listed above then they should contact the sales team ([email protected]) to obtain a quote for Pulsant to provide these services.

Management

  • Pulsant will automatically apply updated RedHat packages on a periodic basis (currently every 4 hours, except kernels which will be applied manually at a time agreed with the customer), or in response to a published security advisory where necessary.
  • In the case of a faulty upgrade, the updates will be rolled back.
  • Critical faults on the server will be dealt with 24×7, but customer-change requests will normally only be actioned within normal working hours (Monday – Friday, 9am – 5pm).
  • Customer-requested configuration changes can be arranged to happen outside of working hours, but these will be charged at the out-of-hours pro rata rate. All customer-requested configuration changes will be actioned within 1 working day of receipt in writing from the customer. The customer will be notified of any changes made to their managed server.
  • SELinux is not supported by Pulsant.

End-user access

  • The end user shall be provided access to the server via one or more user accounts. Root access will not be permitted.
  • Users may access the system by SSH or FTP from trusted static IP addresses. Up to 10 such addresses may be nominated.
  • Changes to root-level configurations shall be made by the web admin interface, or by request to the Pulsant support system.
  • Users may run their own software within a user account, but must accept that this will not be supported. Daemons may be run on high port numbers, and Pulsant will provide the facility to start such services at boot up.
  • Process limits may be applied to maintain the stability of the server.