EMC
®
Smarts
®
Network Configuration Manager
Version 9.3
Support Matrix
P/N 302-001-039
Copyright © 2009 - 2014 EMC Corporation. All rights reserved. Published in the USA. Published July, 2014
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.
The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries.
All other trademarks used herein are the property of their respective owners.
EMC Smarts Network Configuration Manager Support Matrix 3
CONTENTS
Preface
Chapter 1
System Requirements
Prerequisites... 10
Clients ... 10
Bandwidth ... 11
Combination, Application, Device, and Database server requirements... 11
Supported virtual hardware... 12
RSA Token server hardware requirements for Windows... 12
Network Configuration Manager environment sizing ... 12
Basic disk partitioning (Linux)... 13
Advanced disk partitioning... 13
Compatibility ... 14
Interoperability ... 14
Chapter 2
Software requirements for Windows
Software prerequisites ... 18Configuration requirements... 18
Software installed with Network Configuration Manager ... 19
Chapter 3
Software requirements for Linux
Software prerequisites for Red Hat Enterprise Linux... 22Configuration Requirements... 23
Software installed with Network Configuration Manager ... 23
Chapter 4
Software requirements for Integrated Adapters
Software Prerequisites ... 26System and platform requirements ... 26
Preface 5
PREFACE
As part of an effort to improve its product lines, EMC periodically releases revisions of its software and hardware. Therefore, some functions described in this document might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information on product features.
Contact your EMC technical support professional if a product does not function properly or does not function as described in this document.
This document was accurate at publication time. Go to EMC Online Support (https://support.emc.com) to ensure that you are using the latest version of this document.
Revision history
Purpose
This document describes the prerequisites for Network Configuration Manager on Windows and Linux platforms.
Audience
This document is part of the EMC Smarts Network Configuration Manager documentation set, and the information and procedures contained within this document are intended for individuals responsible for installing and deploying EMC Smarts Network Configuration Manager.
Readers of this document should be familiar with:
◆ Red Hat Enterprise Linux and CentOS Linux operating systems ◆ Database architecture and concepts
◆ Security management
◆ Internet protocols, including https, TCP/IP, File Transfer Protocol (FTP), and Telnet ◆ Lightweight Directory Access Protocol (LDAP) and directory services
◆ Authentication and authorization
Related documentation
Related documents include:
Date Revision Description
June, 2014 01 GA release
July, 2014 02 Added interoperability
information and removed references to RedHat 6.1 - not supported
Preface
◆ EMC Smarts Network Configuration Manager Release Notes ◆ EMC Smarts Network Configuration Manager Installation Guide
◆ Smarts Network Configuration Manager EMC Data Access API (EDAA) Programmer
Guide
◆ EMC Smarts Network Configuration Manager Applicaton Program Interface (API)
Javadoc Reference Guide
◆ EMC Smarts Network Configuration Manager Device Access Scripting Language (DASL)
Specifications Guide
◆ EMC Smarts Network Configuration Manager Documentation Portfolio ◆ EMC Smarts Open Source License and Copyright Information
◆ EMC Smarts Network Configuration Manager Online User Guide
◆ EMC Smarts Network Configuration Manager System Management Console Guide ◆ EMC Smarts Network Configuration Manager Security Configuration Guide ◆ EMC Smarts Network Configuration Manager User Guide
◆ EMC Smarts Network Configuration Manager Troubleshooting Guide
Conventions used in this document
EMC uses the following conventions for special notices:
NOTICE is used to address practices not related to personal injury.
Note: A note presents information that is important, but not hazard-related.
Typographical conventions
EMC uses the following type style conventions in this document:
Bold Use for names of interface elements, such as names of windows, dialog boxes, buttons, fields, tab names, key names, and menu paths (what the user specifically selects or clicks)
Italic Use for full titles of publications referenced in text
Monospace Use for:
• System output, such as an error message or script • System code
• Pathnames, filenames, prompts, and syntax • Commands and options
Monospace italic Use for variables. Monospace bold Use for user input.
[ ] Square brackets enclose optional values
| Vertical bar indicates alternate selections — the bar means “or” { } Braces enclose content that the user must specify, such as x or y or z ... Ellipses indicate nonessential information omitted from the example
7
Preface
Where to get help
EMC support, product, and licensing information can be obtained as follows: Product information — For documentation, release notes, software updates, or information about EMC products, go to EMC Online Support at:
https://support.emc.com
Technical support — Go to EMC Online Support and click Service Center. You will see several options for contacting EMC Technical Support. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account.
Your comments
Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to:
System Requirements 9
CHAPTER 1
System Requirements
This chapter includes:
◆ Prerequisites... 10
◆ Clients ... 10
◆ Bandwidth ... 11
◆ Combination, Application, Device, and Database server requirements... 11
◆ Supported virtual hardware... 12
◆ RSA Token server hardware requirements for Windows... 12
◆ Network Configuration Manager environment sizing ... 12
◆ Basic disk partitioning (Linux)... 13
◆ Compatibility ... 14
System Requirements
Prerequisites
The prerequisites for Network Configuration Manager:
◆ Email address where the job notifications will be sent from ◆ License keys for Network Configuration Manager
◆ Any Root CA Certificates to be used
◆ Fully Qualified Domain Name (FQDN) or IP Address for the outbound SMTP mail server ◆ Directory where Report advisor was installed (for upgrade only).
◆ Application server IP Address. ◆ Database server IP Address.
◆ EMC M&R (Watch4net) server IP Address.
◆ Report Server FQDN or IP Address (for upgrade only).
Clients
The client requirements:
If an error appears when bringing up the GUI with NFS mounted, the NFS parameter file in /etc/default/nfs has to be modified by changing the maximum number of concurrent NFS requests to the last numeric argument on nfsd command line.
For example: NFSD_SERVERS=512.
The maximum number of concurrent lockd requests should be set to 128. For example: LOCKD_SERVERS=128.
Component Linux Windows
OS Version
• RHEL 5.8 or later, RHEL 6.2, and 6.3
• CentOS 6.4 or 6.5
Windows 7 and 8
Processor 2 GHz 2 GHz +
Memory 2 GB 2 GB
Storage 200 MB on disk 200 MB on disk
Client Download Size 30 MB on disk 30 MB on disk
Browser Versions
Firefox 9.0.1 or later Microsoft Internet Explorer 9.0 Firefox 9.0.1 or later
Chrome 18.0.1025.168 or later
SSH Client SSH version 2 SSH version 2
Bandwidth 11
System Requirements
Bandwidth
Combination, Application, Device, and Database server
requirements
The hardware requirements for Network Configuration Manager.
Linux Windows Device pull 150 KB 150 KB DevicepPush 300 KB 300 KB Platform CPU Speed / CPU Model / No. of CPUs RAM
Disk technology/
size Disk configuration
Minimum DB spindles Combination
server Microsoft Windows 2008 R2, Microsoft Windows Server 2012,
Linux 5.8 or later, 6.2, and 6.3
2.67 GHz / x86_64 dual core / 4
16 GB SAS/
1.5TB Minimum 300 GB. Maximize spindles. Use small, fast drives whenever possible. Dedicate RAID5 partition for [Product Directory]
3
Application
server (small) Microsoft Windows 2008 R2, Microsoft Windows Server 2012,
Linux 5.8 or later, 6.2, and 6.3
2.67 GHz / x86_64 dual core / 4
16 GB SAS/
1.5TB Minimum 300 GB (Linux) and 500GB (Windows). Maximize spindles. Use small, fast drives whenever possible. Dedicate RAID5 partition for [Product Directory]
6
Application
server (large) Microsoft Windows 2008 R2, Microsoft Windows Server 2012,
Linux 5.8 or later, 6.2, and 6.3
2.67 GHz / x86_64 dual core / 4
16 GB SAS/
1.5TB Minimum 300 GB (Linux) and 500GB (Windows). Maximize spindles. Use small, fast drives whenever possible. Dedicate RAID5 partition for [Product Directory]
6
Database
server (small) Linux 5.8 or later, 6.2, and 6.3 2.67 GHz / x86_64 dual core / 4
8 GB SAS/
1.5TB Minimum 300 GB. Maximize spindles. Use small, fast drives whenever possible. Dedicate RAID1 partition for [Product Directory]
6
Database
server (large) Linux 5.8 or later, 6.2, and 6.3 2.67 GHz / x86_64 dual core / 4
8 GB SAS/
1.5TB Minimum 300 GB. Maximize spindles. Use small, fast drives whenever possible. Dedicate RAID1 partition for [Product Directory]
6
Device server Microsoft Windows 2008 R2, Microsoft Windows Server 2012,
Linux 5.8 or later, 6.2, and 6.3
2.67 GHz / x86_64 dual core / 4
8 GB SAS/
1.5TB Minimum 140 GB. Maximize spindles. Use small, fast drives whenever possible. Dedicate RAID1 partition for [Product Directory]
System Requirements
Disk technology or size is the total disk size required (DAS), including Operating System, Network Configuration Manager application and database install requirements such as, swap and temp space.
Disk configuration is the disk capacity required for the Network Configuration Manager database (not the application) formatted capacity
Supported virtual hardware
The supported virtual hardware for Network Configuration Manager.
RSA Token server hardware requirements for Windows
The RSA Token Server hardware requirements for Network Configuration Manager:
Network Configuration Manager environment sizing
The type and number of servers needed to run Network Configuration Manager based on the number of devices.
The maximum number of Device servers per Application server is 50. Network Configuration Manager 9.3 can support up to 50,000 devices in a single deployment.
Vendor Version
Microsoft Hyper-V on Server 2008 R2 and Server 2012
VMware VMware ESX 5.1.x
CPU Model RAM
Disk Technology /
Size Disk configuration
Token server 2.67 GHz, x86_64 dual
core 2 GB SAS / 1.5TB Minimum 100 GB. Maximize spindles. Use small, fast drives whenever possible. Dedicate RAID5 partition for [Product Directory].
Combination
server Application server Database server
Report server
(optional) Device server
Up to 500 devices 1 N/A N/A N/A N/A
Up to 5K devices N/A 1 Small N/A 1 1+
Up to 10K devices N/A 1 Large 1 Small 1 2+
Up to 25K devices N/A 1 Large 1 Large 1 5+
Basic disk partitioning (Linux) 13
System Requirements
To increase performance of Network Configuration Manager environments with a high number of device changes, it is advisable to setup Network Configuration Manager using a larger sizing setup than is required. For example, if a large number of device changes will occur on a 500 device environment, use the 5K device sizing requirements when you setup your Network Configuration Manager environment.
Basic disk partitioning (Linux)
The following information is provided as a recommendation for your Network
Configuration Manager server disk partitioning scheme. This example assumes that you are installing the product on the /opt partition. If you are installing on a different partition, refer to the /opt partition size requirements when sizing that partition.
Advanced disk partitioning
In large Network Configuration Manager configurations, you may receive performance benefits from placing the database on its own dedicated disks. The database is located under [Product directory]/db. For example, if you have 6 disks in the system, you could allocate 2 disks in RAID1 for the OS and application and allocate 4 disks in RAID5 for the database.
If you have 10 disks or more, you may also separate the database and the database transaction log so that they reside on their own dedicated disks. The database transaction log is located under [Product directory]/db/controldb/data/pg_xlog.
For example, if you have 10 disks in the system, you could allocate 2 disks in RAID1 for the OS and application, 6 disks in RAID5 for the database, and 2 disks in RAID1 for the database transaction log.
Mount point File system Size
Linux Linux Linux
/boot ext3 100 MB - <swap> 1 /var ext3 16000 MB / ext3 10000 MB /tmp ext3 4000 MB /opt ext3 40000 - 200000 MB 2 /usr ext3 4000 MB
1. The swap value should equal two times the physical RAM for up to 2 gigabytes (GB) of physical RAM, and then one times the physical RAM for any amount above 2GB. For example, a system with 2GB of physical RAM would have 4GB of swap, while a system with 3GB of physical RAM would have 5GB of swap.
2. The /opt partition is used to store the Network Configuration Manager application data as well as 8 data backups. Large installations may need as much as 200 GB of disk space depending on the amount of historic information retained in the database.
System Requirements
Compatibility
Upgrading to Network Configuration Manager 9.3 will make previous versions of Advisors and Adapters inoperable until a compatible release is installed. The compatible versions for Network Configuration Manager 9.3:
◆ Integration Adapters 9.3
Report Advisor (RA), Network Advisor (NA), and Compliance Advisor (CA) has been replaced with EMC M&R (Watch4net) in Network Configuration Manager version 9.3. If you perform a fresh or a new installation of NCM 9.3, the advisor pages and tabs will not be visible.
If you migrate or upgrade from Network Configuration Manager 4.1.1.x or NCM 9.x.x and want to use the RA, NA or CA, you have to first migrate or upgrade to NCM 9.2.2a, and then while upgrading to NCM 9.3 choose the Retain RA option. You can also install NCM 9.2.2a Advisors over a new installation of NCM 9.3.
Detailed procedures are available in the EMC Smarts Network Configuration Manager Installation and Configuration Guide.
Network Configuration Manager Integration Modules
After upgrading to Network Configuration Manager 9.3, you do not have to uninstall SNMP, Mail, and/or Flatfile Integration modules. You can use the existing customizations of the SNMP, Mail, and/or Flatfile Integration modules with Network Configuration Manager 9.3.
Interoperability
Service Assurance Suite 9.3.0.0 components interoperate as described here: Table 1 Interoperability among Service Assurnace Suite components
Product Version
ACM 2.3, 2.4
ASAM 3.2.x
EMC M&R (Watch4net) 6.4.x (If EMC M&R and SolutionPack for EMC Smarts are used to manage notifications, you must use SAM 9.3.x with Notification Cache.
6.4.x provides the latest version of the SolutionPack for Network Configuration Manager.
ESM 9.1, 9.2.x
IP 8.1.4, 9.1, 9.2.x
MCAST 8.1.4
Interoperability 15
System Requirements
NCM 9.1, 9.2.x (NCM 9.3.x does not include Report Advisor. Instead, use EMC M&R (Watch4net) and the SolutionPack for Network
Configuration Manager to generate NCM reports. For customers with legacy NCM deployments, you may upgrade to 9.2.2a and use the Report Advisor with a 9.3.x NCM deployment. The EMC Smarts Network Configuration Manager Installation Guide provides details.)
NPM 8.1.4, 9.2.x
OTM XD 5.1
SAM 8.1.4, 9.1, 9.2.x
SAM Adapters 8.1.4
VoIP Availability Manager 8.1.4, 9.2.x
Table 1 Interoperability among Service Assurnace Suite components
Software requirements for Windows 17
CHAPTER 2
Software requirements for Windows
This chapter includes:
◆ Software prerequisites ... 18 ◆ Software installed with Network Configuration Manager ... 19
Software requirements for Windows
Software prerequisites
Do not install Network Configuration Manager on a Windows Domain Controller. The following softwares must be installed prior to installing Network Configuration Manager for all Combination, Application, and Device Servers.
◆ Microsoft Windows Server 2008 R2 Standard Edition 64-bit or Microsoft Windows
Server 2008 R2 Enterprise Edition 64-bit or Windows Server 2008 R2 Datacenter Edition 64-bit
or
Microsoft Windows Server 2012 installed.
◆ Strawberry-perl-5.12.3.0 32-bit:
• Visit the Strawberry Perl website to download a copy of Strawberry-perl-5.12.3.0 32-bit.
After installing Strawberry perl for the first time, you must logout and then re-login so that the system PATH variable modification can take effect.
◆ Microsoft Visual C++ 2005 SP1 Redistributable Package MFC Security Update ◆ Microsoft Visual C++ 2008 SP1 Redistributable Package (x64)
Configuration requirements
Page File Size
Network Configuration Manager requires a minimum page file size of 2000 MB for all server types.
Ensure that when you use ping -a <IP address> command in the console, it returns the FQDN. This is essential for Network Configuration Manager Application communication with remote servers.
Software installed with Network Configuration Manager 19
Software requirements for Windows
Software installed with Network Configuration Manager
The following software is installed automatically with Network Configuration Manager for all Combination and Application servers.
◆ JBoss 5.2
The following software is installed automatically with Network Configuration Manager for all Combination, Application and Remote Database servers.
◆ PostgreSQL 9.0.7 64 bit
The following softwares are installed automatically with Network Configuration Manager for all Combination, Application, Device, and Report Servers.
◆ Apache HTTP Server 2.2
• Apache HTTP Server 2.2 is included with the Network Configuration Manager distribution.
• Network Configuration Manager will automatically install httpd-2.2.22-win32-x86-openssl-0.9.8t.msi.
– It is recommended to setup Apache as a service on Port 80, and select the Typical setup type when installing Apache HTTP Server 2.2.
◆ Apache Tomcat 6.0.37
• Network Configuration Manager will automatically install apache-tomcat-6.0.37.exe.
– It is recommended to set the Connector Port to 8080, and select either the Minimal or Normal setup type when installing Tomcat 6.0.37. Username and password fields are optional.
– It is recommended to use a directory path that does not contain spaces (for example, C:\Tomcat6) when installing Tomcat 6.0.37 on Windows.
Do not manually install Tomcat 6.0.37 prior to installing Advisors. This causes errors during installation.
The following software is installed automatically with Network Configuration Manager for all Combination, Application, Device, Report, and Remote Database servers.
◆ Java SE Development Kit 7, 64-bit
• Network Configuration Manager will automatically install
jdk-7u45-windows-x64.exe if it is not already present in the system.
Enable the Java plugins in your browser before you launch the user interface. The following softwares are part of Network Configuration Manager distribution and installed automatically with Network Configuration Manager for all Combination, Application, Device, Report, and Remote Database servers.
Software requirements for Windows
◆ OpenSSL v0.9.8r—Win32OpenSSL-0_9_8r.exe
• It is recommended to accept the default directory (C:\OpenSSL) when installing OpenSSL on Windows. If a directory whose path contains spaces is used, the creation of the certificates will fail.
When the install.pl script is run to install OpenSSL for Windows, the following warning message appears: The Win32 OpenSSL Installation Project setup has detected that a Command Prompt is currently running. Win32 OpenSSL will not work properly from already opened Command Prompts. It is highly recommended that you close all open Command Prompts before clicking “Ok” to continue.
It is safe to click Ok when this message is displayed. Do not close the Network Configuration Manager installation window.
For details about upgrading OpenSSL on Windows, see the EMC Smarts Network Configuration Manager Security Configuration Guide.
Software requirements for Linux 21
CHAPTER 3
Software requirements for Linux
This chapter includes:
◆ Software prerequisites for Red Hat Enterprise Linux... 22 ◆ Software installed with Network Configuration Manager ... 23
Software requirements for Linux
Software prerequisites for Red Hat Enterprise Linux
Accept the default configuration when installing each prerequisite.
One of the following operating system must be installed prior to installing Network Configuration Manager for all Combination, Application, Device, and remote Database servers:
◆ Red Hat Enterprise Linux 5.8 or later
◆ Red Hat Enterprise Linux 6.2, 6.3, 6.4, and 6.5
Red Hat Enterprise Linux maintains bug fixes and distributes them continuously through their subscription service. Knowledge of current Redhat updates is essential.
Software
Version Architecture Package Group (if applicable)
RHEL 5 RHEL 6 RHEL 5 RHEL 6 RHEL 5 RHEL 6
httpd 2.2 2.2 x86_64 x86_64 Web Server Web Server
mod_ssl 2.2 2.2 x86_64 x86_64 Web Server Web Server
tftp-server x86_64 x86_64 Legacy Network Server Legacy Network Server
perl 5.8.8 5.10.1 x86_64 x86_64
sendmail x86_64 x86_64 Mail Server Mail Server
wget 1.10.2 1.12-1 x86_64 x86_64 Base Base
compat-libstdc++-33 x86_64 x86_64
libtermcap 2.0.8 2.0.8 x86_64 x86_64
glibc 2.5 2.12 x86_64 and
i686 x86_64 and i686
audit-libs x86_64 x86_64 krb5-libs 1.6 1.9 x86_64 x86_64 e2fsprogs 1.39 1.41 x86_64 x86_64 pam x86_64 x86_64 perl-DBD-Pg x86_64 x86_64 perl-DBI x86_64 x86_64 postgresql-libs x86_64 x86_64 xinetd x86_64 x86_64 telnet client x86_64 x86_64 sysklogd 1.4.1 x86_64
Software installed with Network Configuration Manager 23
Software requirements for Linux
To list the architecture of an .rpm file, use the following command, where [RPM] is the name of the rpm, and is optional.
rpm -q -a --queryformat='%{N}-%{V}-%{R}.%{arch}\n' [RPM]
Configuration Requirements
/etc/hosts
The Network Configuration Manager requires a valid FQDN entry in the /etc/hosts and /etc/sysconfig/network files for all server types. For example:
◆ 127.0.0.1 localhost
◆ 192.168.1.100 myserver.mydomain.com myserver
/etc/resolv.conf
The Network Configuration Manager requires a valid DNS server entry in the /etc/resolv.conf file. For example:
◆ domain (your own domain name)
◆ nameserver (your own DNS server IP Address) ◆ search (your own domain name)
Ensure that when you use hostname command in the console, it returns the FQDN. This is essential for communication of the Network Configuration Manager application
communication with other remote servers.
Software installed with Network Configuration Manager
The following software is installed automatically with Network Configuration Manager for all Combination and Application servers.
◆ JBoss 5.2
The following software is installed automatically with Network Configuration Manager for all Combination, Application and Remote Database servers.
◆ PostgreSQL 9.0.7 64 bit
The following softwares are installed automatically with Network Configuration Manager for all Combination, Application, Device, and Report Servers.
◆ Apache HTTP Server 2.2
rsyslog 4.6.2 x86_64
openssl 0.9.8 1.0.0 x86_64, x86_64
distcache x86_64
Software
Version Architecture Package Group (if applicable)
Software requirements for Linux
• Apache HTTP Server 2.2 is included with the Network Configuration Manager distribution.
◆ Apache Tomcat 6.0.37
• Network Configuration Manager will automatically install apache-tomcat-6.0.37.zip.
The following software is installed automatically with Network Configuration Manager for all Combination, Application, Device, Report, and Remote Database servers.
◆ Java SE Development Kit 7, 64-bit
• Network Configuration Manager will automatically install jdk-7u45-linux-x64.rpm.
Enable the Java plugins in your browser before you launch the user interface.
Software requirements for Integrated Adapters 25
CHAPTER 4
Software requirements for Integrated Adapters
This chapter includes:
◆ Software Prerequisites ... 26 ◆ System and platform requirements ... 26 ◆ Supported web browsers ... 26
Software requirements for Integrated Adapters
Software Prerequisites
The EMC Smarts Network Configuration Manager Integration Adapter for Smarts Manager requires the following prerequisites:
◆ Perl 5.10.1 for RHEL6 ◆ Perl 5.8.8 for RHEL5
◆ Strawberry Perl version 5.12.3 for Windows Server 2008 R2 and Server 2012 ◆ Java 1.7.0_60 or later
System and platform requirements
The Network Configuration Manager Integration Adapter for Smarts Manager requires the following software:
◆ EMC Smarts Network Configuration Manager 9.3
You must have EMC Smarts Network Configuration Manager Report Advisor, or later installed before installing the EMC Smarts Network Configuration Manager Integration Adapter for Smarts Manager.
◆ Supported Operating Systems:
• Red Hat Enterprise Linux 6.2, 6.3, 6.4, or 6.5 • Red Hat Enterprise Linux 5.8 or later
• Windows Server 2008 R2 • Windows Server 2012
◆ EMC Smarts IP Availability Manager 8.x, 8.1.3, 8.1.4, or 9.x ◆ EMC Smarts IP Topology Split Manager (TSM) 9.0. 9.1, 9.2 or 9.3 ◆ EMC Smarts Service Assurance Manager 8.x, 9.0, 9.1, 9.2 or 9.3
Supported web browsers
The EMC Smarts Network Configuration Manager Integration Adapter for Smarts Manager requires a web browser for successful client installation.
RHEL 5.8 or later, 6.2, and 6.3
CentOS 6.4 and 6.5 Windows Server 2008 R2 and Server 2012
• Mozilla Firefox 9.0.1 or later • Microsoft Internet Explorer 9.0 • Mozilla Firefox 9.0.1 or later
