TECHNICAL SPECIFICATION
FOR
DATA CENTRE AND IT INFRASTRUCTURE
SETTING-UP
DATA CENTRE AND IT INFRASTRUCTURE
AT
INFRASTRUCTURE AT DELHI OFFICE & PALATANA PLANT
TABLE OF CONTENT
Clause No. Description Page No.
1.0 Background 3
2.0 Scope of Supply 4
3.0 Hardware Sizing for SAP 10
4.0 Design Considerations & Critical Factors – Hardware for IT
Infrastructure 12
5.0 Design Considerations & Critical Factors – Hardware for Data
Centre 16
6.0 Technical Specification for Blade Chassis 19 7.0 Technical Specification for Servers, Database – Central
Instance (DB-CI) Design Considerations & RAS features 23
8.0 Technical Specification for Storage 50
9.0 Technical Specification for Tape Library and Tape Drive 57 10.0 Technical Specification for Tape Cartridges 60 11.0 Technical Specification for Network and Security Setup 62 12.0 Technical Specification for Load Balancers 110
13.0 Technical Specification for Racks 118
14.0 Technical Specification for Passive Work 121 15.0 Technical Specification for Scanner 133 16.0 Technical Specification for LINUX Operating System 135 17.0 Technical Specification for Backup Software 138 18.0 Technical Specification for Enterprise Management System 143 19.0 Technical Specification for Virtualization Software 166 20.0 Technical Specification for E-Mail Gateway spam &
Anti-virus Software 173
21.0 Technical Specification for Data Centre Infrastructure (DELHI) 176 22.0 Technical Specification for Server Room Infrastructure
(PALATANA) 190
23.0 Technical Specification for Static / Source Transfer Switch 201 24.0 Technical Specification for Fire Proof Media Enclosure 203
SECTION - 1.0
SCOPE OF SUPPLY & DESIGN REQUIREMENTS
1.0 BACKGROUND
1.1 ONGC Tripura Power Company Limited (hereinafter referred as "OTPC" or "Owner"), a joint venture company promoted by Oil and Natural Gas Corporation Limited ("ONGC"), Infrastructure Leasing and Financial Services Limited ("IL&FS") and Government of Tripura, is a public limited company incorporated under the Indian Companies Act, 1956 and having its registered office at ONGC Tripura Assets, Badarghat Complex, Agartala, Tripura-799014 (India), and one of its office at 6th Floor, IFCI Tower, 61, Nehru Place, New Delhi-110019 (India).
1.2 OTPC is setting up Data Centre and IT Infrastructure at Delhi office and Palatana plant, which is about 60 (sixty) km from the capital city of Agartala in the State of Tripura. The setup shall cater to the ERP implementation and other IT infrastructure requirement.
1.3 The SAP ERP project is an end-to-end implementation of an IT Solution at OTPC. SAP ECC 6.0 with latest enhancement package shall be implemented with following modules:
1.3.1 SAP ERP - Finance & Costing Module 1.3.2 SAP ERP – Management Accounting Module 1.3.3 SAP ERP – Material Management Module
1.3.4 SAP ERP – Human Resource Management Module & Payroll 1.3.5 SAP ERP – Public Sector management – Funds Management
1.4 Delhi and Palatana locations are currently not connected through any kind of network. The internet access for both the locations is independent. The email system is running at Delhi and Palatana users access e-mail remotely through Internet. 1.5 Existing LAN setup at Palatana is spread across different buildings in the campus.
These buildings are interconnected using Wi-Fi (Building to Building). The ISP’s STM link is terminated at BHEL office in administrative building. Fibre is laid from administrative block to Control and Facility Building. The outdoor access point at Control and Facility Block connects Switch Yard Control Block and Administrative Block. One Access Point is provided at Switch Yard Control Block and one at Administrative Block.
Diagram Below gives a high-level representation of the present LAN setup at Palatana
.
1.6 Existing Network Setup (At Delhi Office):
The existing LAN at OTPC HO (Delhi) is spread across on 6th floor of IFCI Tower, Nehru place, New Delhi. CAT 6 cabling is used for networking. The entire setup is housed in 2 racks (1 for server and 1 for Voice and Data).
2.0 SCOPE OF SUPPLY
The Scope of supply specified inter-alia below includes items necessary for the successful implementation of IT and Data Centre infrastructure for SAP ERP Implementation at Delhi and Palatana, Tripura. All the items offered shall be with 5 years warranty and 24 x 7 on-site support. The quantities mentioned for IT and Data Centre infrastructure are indicative and the minimum required for the implementation, contractor shall supply necessary material of all the items required
for setting-up IT and Data Centre infrastructure at Delhi office and Palatana Plant as per the good design and industry practices.
The basic Scope of supply covers the following in general: 2.1 IT Hardware
Decription Minimum
Quantity Location
2.2 Blade Chassis As Required Delhi
2.3 Servers
2.3.1 Blade Servers for SAP ERP
2.3.1.1 IDES Server As Required Delhi
2.3.1.2 Development Server
2.3.1.2.1 ERP Development Server As Required Delhi 2.3.1.2.2 SAP Net weaver Portal Server As Required Delhi 2.3.1.3 Quality and Training Server
2.3.1.3.1 ERP Quality Server As Required Delhi
2.3.1.3.2 SAP Net weaver Portal Server As Required Delhi 2.3.1.4 Production Servers
2.3.1.4.1 DB / CI (Database / Central
Instance) Server As Required Delhi
2.3.1.4.2 Application Server As Required Delhi
2.3.1.5 Enterprise Portal Production Server 2.3.1.5.1 DB / CI (Database / Central
Instance) Server As Required Delhi
2.3.1.5.2 Application Server As Required Delhi
2.3.1.6 SAP Solution Manager As Required Delhi
2.3.1.7 SAP Router As Required Delhi
2.3.3 Blade Servers for Enterprise
Management System (EMS) As Required Delhi 2.3.4 Blade Servers for Infrastructure
Setup
Delhi
2.3.4.1 Domain Controller and DNS 2 No. Delhi
2.3.4.2 DHCP Server Primary & Windows
Update Service 1 No. Delhi
2.3.4.3 DHCP Server Secondary & NTP
Server 1 No. Delhi
2.3.4.4 Antivirus Server 1 No. Delhi
2.3.5 Blade Servers for Anti-spam & E-Mail
Gateway Antivirus 2 No. Delhi
2.3.6 Blade Servers for existing production upgrade (E-Mail Migration and Setup)
4 No. Delhi
2.3.7 Rack Servers for Domain Controller, DNS, DHCP, Windows Update Service and Antivirus (Minimum 2
Physical Servers)
Palatana
2.3.7.1 Domain Controller + DHCP +
Windows Update Service 2 No. Palatana
2.3.7.2 Antivirus Server 1 No. Palatana
2.4 Storage
2.4.1 Storage Area Network (SAN) 1 No. Delhi
2.4.2 Network Attached Storage (NAS) 1 No. Palatana 2.5 Tape Library / Drive
2.5.1 LTO-6 (Liner Tape Open Generation
6) Tape Library 1 No. Delhi
2.5.2 LTO-6 (Liner Tape Open Generation
6) Tape Drive 1 No. Palatana
2.6 Tape Cartridges
2.6.1 LTO-6 tape cartridges (with bar
2.6.2 LTO-6 tape cartridges (with bar
codes) 30 No. Palatana
2.6.3 LTO-6 cleaning cartridges (with bar
codes) 20 No. Delhi
2.6.4 LTO-6 cleaning cartridges (with bar
codes) 5 No. Palatana
2.7 Network
2.7.1 SAN Switch 2 No. Delhi
2.7.2 Core Switch 2 No. Delhi
2.7.3 DMZ (De-Militarized) Zone 2 No. Delhi
2.7.4 Aggregation Switch 2 No. Delhi
2.7.5 WAN (Wide Area Network) Switch 2 No. Delhi
2.7.6 48 Port LAN (Local Area Network)
Switch 2 No. Delhi
2.7.7 Core Switch 2 No. Palatana
2.7.8 48 Port LAN (Local Area Network)
Switch 6 No. Palatana
2.7.9 24 Port LAN (Local Area Network)
Switch 14 No. Palatana
2.7.10 MPLS (Multi-Protocol Label
Switching) VPN Router 2 No. Delhi
2.7.11 Internet Routers 2 No. Delhi
2.7.12 MPLS (Multi-Protocol Label
Switching) VPN Router 2 No. Palatana
2.7.13 WAN (Wide Area Network) Links 1 Lot Delhi & Palatana
2.7.14 Internet Links 1 Lot Delhi &
Palatana 2.8 Security
2.8.1 External (Perimeter) Firewall 2 No. Delhi
2.8.2 Internal Firewall 2 No. Delhi
2.8.3 DLP (Data Loss Prevention) & Information security enforcement solution
1 No. Delhi
2.9 Load Balancers 2 No. Delhi 2.10 Racks
2.10.1 42U Rack (Network & Server) 1 No. Palatana 2.10.2 12U Wall Mount Network Racks 19 No. Palatana 2.11 Passive Work
2.11.1 Wall Mount Patch Panels As Required Delhi
2.11.2 Patch Panels for Server & Network
Rack As Required Palatana
2.11.3 Patch Panels for Wall Mount
Network Racks As Required Palatana
2.12 Scanner 1 No. Delhi
2.13 Software
2.13.1 LINUX Operating System (Media &
Licenses) As Required Delhi
2.13.2 Microsoft Windows Server Operating
System (Media & Licenses) As Required Delhi 2.13.3 Microsoft Windows Server Operating
System (Media & Licenses) As Required Palatana 2.13.4 Microsoft Exchange 2013 (Media &
Licenses)
2.13.4.1 Microsoft Exchange Server 2013
Enterprise 2013 2 No. Delhi
2.13.4.2 Microsoft Exchange Server 2013
Standard 2013 2 No. Delhi
2.13.4.3 Microsoft Exchange Standard CAL
2.13.4.4 Microsoft Exchange Enterprise CAL
2013 (User CAL) 100 No. Delhi
2.13.4.5 SAN (Subject Alternative Name) SSL
Digital Certificates 4 No. Delhi
2.13.5 Backup Software (Media & Licenses)
& Backup Agents As Required Delhi
2.13.6 Backup Software (Media & Licenses)
& Agents As Required Palatana
2.13.7 Enterprise Management Software
(Media & Licenses) As Required Delhi
2.13.8 Virtualization Software (Media &
Licenses) As Required Delhi
2.13.9 Virtualization Software (Media &
Licenses) As Required Palatana
2.13.10 2.13.11
E-Mail Gateway Anti-spam & Antivirus Software
Client Access Licenses (User) for Windows Servers For 100 Users As Required 100 Users Delhi Delhi & Palatana
2.14 Data Centre Infrastructure
2.14.1 UPS for Server Area 2 No. Delhi
2.14.2 Air Conditioning System for Server
Room 2 No. Delhi
2.14.3 Access Control System 1 No. Delhi
2.14.4 Fire Detection and Alarm System 1 No. Delhi
2.14.5 Fire Suppression System 1 No. Delhi
2.14.6 CCTV Surveillance System 1 Set Delhi
2.14.7 Monitoring System 1 Set Delhi
2.14.8 Water Leakage System 1 No. Delhi
2.14.10 Civil Work As Required Delhi
2.14.11 Electrical Work As Required Delhi
2.15 Server Room Infrastructure Palatana
2.15.1 UPS for Server Area 2 No. Palatana
2.15.2 Precision Air Conditioning System for
Server Room 2 No. Palatana
2.15.3 Civil Work As Required Palatana
2.15.4 Access Control System 1 No. Palatana
2.15.5 Electrical Work As Required Palatana
2.15.6 Fire Detection & Alarm System 1 No. Palatana 2.15.7 2.15.8 2.15.9 2.16 2.17 CCTV System
Water Leakage Detection System Rodent Repellent System
Static/Source Transfer Switch Fire Proof Media Enclosure
1 Set 1 No. 1 No. 1 No. 1 No. Palatana Palatana Palatana Delhi Delhi 2.18 Passive (Cabling) Material As Required Delhi &
Palatana
2.18.1 CAT 6A Cabling As Required Delhi &
Palatana
2.18.2 Fibre Cabling As Required Delhi &
Palatana
2.18.3 Other Accessories As Required Delhi &
Palatana 3.0 Hardware Sizing for SAP ERP
Following table shows the minimum required configuration for SAP ERP environment. This is the minimum configuration as given by M/s SAP India, however supplier may provide higher configuration if required.
Required / recommended Configuration Users Base SAPS at 65% CPU Additional Loading on Base
SAPS RecommendedSAPS (GB)RAM
Disk (GB) -SAP & Oracle Software Disk (GB) – Database Remarks
Core Team Training Systems
IDES Server 10 2500 0% 2500 16 150 800 Development Systems ECC Development System 20 1500 0% 1500 16 150 400 SAP Netweaver Portal + NDWI 20 1500 0% 2500 16 150 300
Quality Servers + Training Servers
ECC Quality System 20 2000 0% 2000 16 150 800 SAP Netweaver Portal 20 2000 0% 2000 16 150 300 Production Servers ECC Production
System 5200 around 35 ERPusers
Database Server 30% 1560 75% 2730 24 150 800 HA Cluster Central Instance 30% 1560 75% 2730 24 150 Application Server 70% 3640 75% 6370 24 150 Enterprise Portal Production 2000 Database/CI Server 100% 2000 100% 4000 24 150 300 HA Cluster Application Server 100% 2000 100% 4000 24 150 SAP Solution Manager 150 2000 3000 16 150 300 Windows/Linux SAP SAP Router 8 150 High End Desktop Machine
Reverse Proxy 8 150
In case of Internet scenario
Total SAPS 33330 224 3300
3.1 The table provides the RAM required for application. Additional memory for overload due to Operating System and virtualization shall be provided. Also these memories are indicative only and memory shall be supplied as per the configuration guidelines provided in above table at clause 3.0.
3.2 For Development, Quality Assurance & End User Training Systems: As these systems are not business critical systems, no high availability (HA) feature is required for these. Accordingly the Database and Central Instance for each of the system in this environment shall be configured in central mode (No DB-CI Cluster).
3.3 All critical components (for production setup) shall be in HA (Highly-Available) mode to ensure business continuity.
3.4 All application servers requirement (for production setup) shall be fulfilled by providing multiple servers with minimum 13500 SAPS each to provide scalability and redundancy
3.5 For ERP, additional load shall be considered for printing, batch jobs, interfaces, extractions, custom development
3.6 All production systems SAPS rating requirement are indicated for 65% CPU Utilization.
4.0 Design Considerations and Critical Factors – Hardware for IT Infrastructure
4.1 Critical Factors
Following critical factors should be considered while selecting the configuration of Hardware, Software and Data Centre Components:
4.1.1 Scalable
4.1.1.1 The architecture offered must support scaling to provide continuous growth to meet changing business requirements with respect to the changing IT computing equipments.
4.1.1.2 All the power consuming components of IT Infrastructure must have scalability options to avoid over sizing & reduce the incredible wastage of power.
4.1.2 Availability
4.1.2.1 There shall be multiple level redundancies in the critical components used in Data Centre to reduce the MTTR (Mean time to repair) to the minimum & to provide the maximum up-time to the Data Centre as a whole.
4.1.3 Modularity
4.1.3.1 To the extent possible, all the Components used in the Data Centre physical architecture shall be modular & hot swappable in nature, so as to minimize the human error as well as down time due to critical faults.
4.1.4 Redundancy
4.1.4.1 While designing physical infrastructure, Supplier must consider minimum N + 1 redundancy for all the critical active components.
4.1.4.2 Since OTPC is hosting business critical applications, N + 2 or N + N redundancies are to be appropriately used to achieve above 99.5 % uptime on services to business users.
4.1.5 Manageability
4.1.5.1 Ease of configuration, on-going health monitoring, and failure detection are vital to the goals of scalability, availability, and security and must be able to match the growth of the environment.
4.1.5.2 In this respect it is required to consolidate applications on minimum servers. 4.2 Design Consideration
4.2.1 Latest and proven technologies in the market shall be offered.
4.2.2 Shall not supply products which will be End of Sale (EOS) in next 24 (Twenty Four) months from the date of supply and End of Life (EOL) in next 5 (five) years from the date of taking over of the facility. Supplier shall guarantee availability of spares for a minimum period of 7 (seven) years from date of supply.
4.2.3 All the servers shall have facility to access the Internal/External DVD ROM Drive for OS, software and patch installations. In case of external DVD ROM, at least 4 DVD ROM shall be supplied per Blade Chassis.
4.2.4 Shall design the IP addressing schema for OTPC. 4.2.5 Hardware shall be supplied for 24x7 environments.
4.2.6 Supply and install all necessary cables (fibre and cooper networking cable, power cables from UPS, control etc.), adaptors, power cords and any other interconnects as per the technical specification.
4.2.7 Documentation of the complete system including the following shall be submitted: 4.2.7.1 Factory / site test certificates of various equipments supplied
4.2.7.2 Original Manufacturers manuals and warranty cards
4.2.7.3 Installation certificates of all equipments, description of configuration profile as executed for different equipment
4.2.7.4 Standard OEM checklist for installation, maintenance etc, if any 4.2.7.5 Training documents
4.2.8 The supplied material shall be complete in all respect to meet the RFP requirements and infrastructure objective of SAP-ERP project.
4.2.8.1 Any item (Hardware and / or Software/Licenses) not specifically mentioned in contract and not supplied by supplier but are required for successful completion of facility as per technical specifications and performance requirement shall be supplied free of cost at the earliest, so that committed implementation schedule shall not get affected. In case the implementation schedule is affected, Liquidity charges will be applied.
4.2.8.2 In case this situation of any hardware / software/Licenses found short or not quoted but required to meet the tender conditions, arises during warranty and AMC period, the supplies, installation and commissioning of the relevant hardware/ software/ License shall have to be made free of cost and completed within 8 weeks from the date of detection of such shortfall / inadequacy.
4.2.9 Shall ensure that all the devices, servers and hardware appliance supplied are rack mountable and provided with required rack mounting accessories / kit.
4.2.10 Data Centre space is limited and at premium. So supplier shall optimize on the rack-space requirement and take all other measures to fit in the IT infrastructure in available space.
4.2.11 Shall provide the technology which minimizes total power and cooling requirement for the Data Centre without compromising the performance.
4.2.12 The power supplies, cables, connectors etc. for all equipment shall be suitable for Indian power specifications of voltage, frequency and phasing and matching the requirements completely.
4.2.13 Supplied material should be such that all the specified features and specifications mentioned in detailed technical specifications are complied with.
4.2.14 Material should include all other supporting material as required to ensure smooth implementation.
4.2.15 Remote Management
4.2.15.1 Facility shall have a remote management functionality to operate the server in both in in-band and out-of-band. This feature must be part of the server without need to install any additional hardware or software and any additional licensing requirements. 4.2.15.2 It shall have facility to manage the servers and get access to critical information about the health of the server from any remote location with just the help of a standard web browser.
4.2.15.3 It shall support hardware based and OS independent remote management like remote power on/off the server. It should support SSL encryption.
4.2.16 Server, Storage and Tape library shall be supplied from the same OEM. 4.3 Design Consideration specific to LAN Switches and Network Cabling
4.3.1 LAN Switches
4.3.1.1 Ethernet ports, SFPs, SFP+ and switch interconnecting cables required for connectivity on the switch shall satisfy the LAN point’s requirements.
4.3.1.2 For interconnecting 2 or more floor switches, proper interconnecting cables shall be used to provide the maximum available bandwidth (minimum 1Gbps required) between switches using a single port. Link aggregation shall not be used to achieve higher bandwidth.
4.3.2 Network Cabling
4.3.2.1 UTP CAT6 cabling shall support 1Gbps connectivity.
4.3.2.2 LAN / fiber cabling shall support all types of traffic (data, voice or video). 4.3.2.3 UTP CAT6 LAN Cabling shall be able to carry power for PoE devices.
4.3.2.5 Fiber termination on LIUs shall be of SC type with proper interfaces.
4.3.2.6 A minimum of 20 years cabling (LAN / fiber) product warranty by OEM shall be ensured.
4.3.2.7 The network racks power supplies cables shall be suitable for Indian power specifications of voltage, frequency, and phasing, and match the power requirements.
4.3.2.8 All the cable interfaces, connectors, etc. are included in scope of supply. This shall include fixing of LIU, connecters, cables, and components to make the circuit operational.
4.3.2.9 Each building shall have redundant fiber connectivity to the Server room (Admin) building at plant site (Palatana, Tripura)
4.3.2.10 Uplink ports from each building shall be on fiber and shall terminate on Core Switch at Admin building at Palatana Plant Site.
4.3.2.11 To save the space on network rack at Data Centre (Delhi), external wall mount patch panel shall be supplied. It shall support minimum 250 ports including the current requirement of data and voice ports.
4.4 Virtualization:
Virtualization shall be considered without compromising on performance and availability of service to OTPC’s business users. Hence applications shall be consolidated on minimum physical servers using virtualization.
5.0 Design Considerations and Critical Factors – Hardware for Data Centre Infrastructure
5.1 OTPC Data Centre shall be designed considering the following critical factors and requirements:
5.1.1 Minimize the capital investment as well as the operating & maintenance cost of the Data Centre.
5.1.2 Data Centre physical infrastructure must be designed with highly efficient & reliable components available in the market.
5.1.3 Power: All the components of the Data Centre must be designed to have the
5.1.4 Scalability: Components of the Data Centre physical architecture must support
scaling to provide future growth to meet future IT requirements. All the components in the Data Centre must have scalability to meet the future requirement and optimum solution at present.
5.1.5 Availability and Redundancy: While designing the Data Centre physical
infrastructure Redundancy must be considered for all the active components. All the critical components used must provide redundancy level like N+N, N+1 to provide the maximum uptime to the Data Centre.
5.1.6 Security: The System Integrator must provide an end-to-end security model that
protects data and the infrastructure from malicious attacks, theft, natural disasters etc.
5.1.7 Manageability: Easy of configuration, ongoing health monitoring, and failure
detection are vital to the goals of scalability, availability, and security and must be able to match the growth of the environment.
5.1.8 Indoor Conditions: As per ASHARE (American Society of Heating, Refrigeration &
Air-conditioning Engineers) Guidelines.
5.1.9 Blanking Panels: Supplier shall supply blanking panels to cover the vacant rack
SECTION 2.0
DETAILED TECHNICAL SPECIFICATION AND COMPLIANCE MATRICES (I.T. AND DATA CENTRE INFRASTRUCTURE)
CONTENTS
SECTION - 2.1 TECHNICAL SPECIFICATION FOR BLADE CHASSIS SECTION - 2.2 TECHNICAL SPECIFICATION FOR SERVERS
SECTION - 2.3 TECHNICAL SPECIFICATION FOR STORAGE
SECTION - 2.4 TECHNICAL SPECIFICATION FOR TAPE LIBRARY / DRIVE SECTION - 2.5 TECHNICAL SPECIFICATION FOR TAPE CARTRIDGES
SECTION - 2.6 TECHNICAL SPECIFICATION FOR NETWORK & SECURITY SETUP SECTION - 2.7 TECHNICAL SPECIFICATION FOR LOAD BALANCERS
SECTION - 2.8 TECHNICAL SPECIFICATION FOR RACKS
SECTION - 2.9 TECHNICAL SPECIFICATION FOR PASSIVE WORK SECTION - 2.10 TECHNICAL SPECIFICATION FOR SCANNER SECTION - 2.11 TECHNICAL SPECIFICATION FOR LINUX OS
SECTION - 2.12 TECHNICAL SPECIFICATION FOR BACKUP SOFTWARE
SECTION - 2.13 TECHNICAL SPECIFICATION FOR ENTERPRISE MANAGEMENT SYSTEM SOFTWARE
SECTION - 2.14 TECHNICAL SPECIFICATION FOR VIRTUALIZATION SOFTWARE SECTION - 2.15 TECHNICAL SPECIFICATION FOR E-MAIL GATEWAY ANTI-SPAM
& ANTIVIRUS SOFTWARE
SECTION - 2.16 TECHNICAL SPECIFICATION FOR DATA CENTRE INFRASTRUCTURE (DELHI)
SECTION - 2.17 TECHNICAL SPECIFICATION FOR SERVER ROOM (PALATANA) SECTION - 2.18 TECHNICAL SPECIFICATION FOR STATIC/SOURCE TRANSFER
SWITCH (DELHI)
SECTION - 2.19 TECHNICAL SPECIFICATION FOR FIRE PROOF MEDIA ENCLOSURE (DELHI)
SECTION 2.1
TECHNICAL SPECIFICATION FOR BLADE CHASSIS
1.0 Blade Chassis Specification * Feature /
Specifications MinimumSpecification Required Compliance Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks (Y / N) for minimum specifications 1.1 Form Factor
Max 10U Rack mounted Chassis to house at least 14 Compute Nodes. Blade chassis shall be 19” Electronic
Industries Alliance standard width rack mountable and provide appropriate rack mount kit
1.2 IO Modules
Min Four high-speed switch bays capable of supporting I/O
architectures in Ethernet, Fiber Channel, FCoE and Infiniband 1.3 Ethernet IOModule 2 x 10gbps Ethernet switch with L2 capabilities, Vmready standards
1.4 Fibre ChannelIO Module
Should provide FC connectivity to all blade slots in chassis. 2 x 8 gbps FC switch and 8 Gbps SFP should be supplied along with the switch.
The chassis should have redundant module for all fabric connectivity
1.5 EthernetModule
Chassis should have 2 hot-plug, redundant Ethernet modules with SFP ports.
Should have minimum 4 numbers of active fibre uplink ports of 10Gbps and 4 numbers of active 1Gbps (copper) port each module Should have 10GB uplink from the
Ethernet module which is connected to the blade chassis All Ethernet module should be VM aware.
1.6 Midplane
Chassis should have a highly reliable mid plane for providing connectivity of the shared resources to the compute nodes in a highly reliable manner. 1.7 PowerModules Redundant Platinum power modules to provide N+N or N+1 redundancy. 1.8 ChassisManagement Module Integrated two redundant chassis Management Modules providing IP based management of the compute nodes and vital elements like FC and Ethernet Switches. Should also provide for controlling Power, Fan management, Chassis and compute node initialization, Switch management, Resource discovery and inventory management, Resource alerts and
monitoring
management, Chassis and compute node power management and diagnostics for elements including Chassis, I/O options and compute nodes.
1.9 Security
Should provide Secure Socket Layer (SSL) 128 bit encryption and Secure Shell (SSH) Version 2 and support VPN for secure access over internet
Chassis supports both legacy-SNMP and SNMPv3 interfaces.
1.10 Drivers andLicenses
Appropriate number of licenses and drivers required for servers, networking and blade chassis
1.11 System Panel
LEDs on the front information panel that can be used to obtain the status of the chassis Identify, Check log and the Fault LED
1.12 Virtual DVDSupport
Should be able to support the feature of virtual DVD to
individual servers from remote systems 1.13 KVMFunctionality It should support remote KVM capability from an external keyboard, video monitor and mouse to all blades installed in the chassis through the management controllers. Simultaneous KVM access to a single blade KVM by multiple users but the admin user can take Read Write ownership while the other user in in read only mode
1.14 OperatingTemperature Range
Chassis should support the operating temperature range between 5 C to 40 C 1.15 Should provide 5 years onsite comprehensive warranty & Hardware maintenance support. Required
* The blade chassis should be quoted based on optimum number of chassis requirement for the supplied number of blades.
SECTION 2.2
TECHNICAL SPECIFICATION FOR SERVERS
1.0 Blade Servers for SAP ERP
1.1 IDES, Development, Quality, Solution Manager, SAP Router, Portal Servers Feature /
Specifications MinimumSpecification Required Compliance Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks (Y / N) for minimum specifications 1.1.1
Make and Model
of the server Required 1.1.2 Form Factor Blade
1.1.3
Processor Type The Server should be based on x86-64-bit architecture that is latest in respective product line & server should have the capability of supporting 32-bit applications as well. 1.1.4
Processors Should have minimum 2.6 GHz, 15MB L3 cache and should provide 9000. Should be 100% scalable
1.1.5
Server RAM The server must be with the Minimum of 8 GB RAM per core, DDR3 RDIMM memory modules having same DIMM for all slots. If Vms are installed, the same can be increased
as per the solution requirement. Blade should have minimum 24 DIMM slots.
1.1.6
Memory
Protection Advanced ECC(Chipkill/ Extended ECC/ Chipspare) with multi-bit error protection support 1.1.7 HDD 2 x 600GB 6G hot plugSFF SAS Internal HDD
in RAID-1 1.1.8 HDD Speed 15/10K RPM 1.1.9 RAID Support forinternal HDDs With Hardware orSoftware RAID-1
support 1.1.10
Ethernet 2 (Two) nos 10G Ethernet Ports with 4 nos vNIC support per port.
1.1.11 Ethernet feature Should support andprovide the NIC teaming / bonding 1.1.12 IO adapters All adapters should bePCI/X or PCI/E
1.1.13
FC ports All FC ports for storage connectivity should be 8Gbps and should be provided in redundant config with multi pathing enabled. They should be provided with appropriate drivers and licenses 1.1.14 OS Support and
Virtualization The OS should belatest available version. The Operating systems (OS) should be 64-bit industry compliant LINUX (LINUX or Windows for Solution Manager and SAP Router) and should support both 32-bit and 64-bit applications. 1.1.15 DVD ROM Should supportInternal or External
and O.S. installation and patch
management. 1.1.16
Manageability Should support unified management suite that can monitor and manage all the servers 1.1.17 VirtualizationSupport Required
1.1.18
Should provide the facility and interfaces / cables for connecting Monitor, USB keyboard and USB mouse to the server Required 1.1.19 No single point of failure for Fan Assembly
Required
1.1.20 Power Supplywith redundancy Required
1.1.21
Should provide LINUX OS (64-Bit Windows OS for SAP Router), licenses along with media Required 1.1.22 Hardware should be compatible with SAP applications Required
1.1.23 USB Ports Server should have 1front and 2 internal USB 2.0 ports
1.1.24
Predictive Failure
Analysis Server should havefeature of Predictive Failure Analysis on Processors, memory, drives, in servers fans and power supplies in the chassis 1.1.25 Should provide 5 years onsite comprehensive warranty & Hardware maintenance Required
support.
1.1.26 Number ofServers or partitions
As per solution requirement
1.2 DB & CI and Application Instance Design Considerations and Servers
1.2.1 DB & CI Instance Specific Design Considerations
Design Considerations Compliance (Y / N)for Design Considerations
Details / Remarks / Deviations
1.2.1.1
The DB & CI systems for each SAPS Production application module will run in a High Availability cluster on two different physical systems with adequate redundancy and with equal performance and configuration, and will have access to the same database and storage.
1.2.1.2
The cluster solution must be able to provide fail-over to the other system for any failure arising due to: Hardware,
Operating system, Database
SAP processes in any of the two systems.
The solution must be able to recover automatically (by restarting any stopped process automatically). In case of unrecoverable errors, the process on the failed system must be automatically restarted on the other system. This switch over should remain transparent to all the
Application Servers and end-users and they should be able to continue working without re-logging into SAP.
1.2.1.3
The fail over scenario mentioned in Serial number 2 item no 4, no
committed transactions in SAP should be lost. Once the failed system comes up, there should be a scope of reverting back to the original configuration manually and
automatically (both options) without disrupting the applications.
Design Considerations Compliance (Y / N)for Design Considerations
Details / Remarks / Deviations
1.2.1.4 An uptime of 99.5% is required forthe entire solution for DB and CI.
1.2.1.5
The database and CI servers should be configured such that there should be CPU and Memory headroom of minimum 50% allocable to any of the SAP application module (DB/CI) running on that server.
1.2.1.6 System Integrator should propose thesolution, with DB and CI consolidation for relevant applicable SAP modules. 1.2.2 Application Instance Specific
1.2.2.1
The total required SAPS for application servers have to be divided in to multiple servers or partitions to provide load balancing and redundancy. Each such server or partition should provide SAPS not less than 13500
1.2.2.2
If the System Integrator proposes a large server partitioned to provide the required number of Application servers, the following points are mandatory:
Each partition should be able to run same or different versions of OS independently
Any configuration change in one partition should not affect any other partition unless desired
An error in one partition should not bring the entire system or other partitions down
Each partition should be upgradeable separately and independently without affecting other partitions.
1.2.3 Other Considerations
1.2.3.1
The SAPS mentioned in hardware sizing are purely required for the SAP applications. System Integrator need propose the system considering
Design Considerations Compliance (Y / N)for Design Considerations
Details / Remarks / Deviations
additional SAPS due to OS and Virtualization overheads.
1.2.3.2
The RAM mentioned in hardware sizing is purely minimum required for the SAP applications. System
Integrator need propose the system considering additional RAM for performance, OS and Virtualization overheads.
1.2.3.3 The offered machine must be certifiedfor SAP Usage for 64-bit OS kernel. 1.2.3.4 OS should include Kerberos
1.2.3.5
System Integrator needs to provide the published benchmark or OEM letter mentioning the SAPS rating supported by the Server. The offer without competency center certificate shall not be accepted.
1.3 Reliability, Availability and Serviceability (RAS) features required for SAP DB, CI and Application Servers
RAS features described here shall be supported both by Hardware and Operating System
Reliability, Availability and Serviceability (RAS) Compliance(Y / N) for RAS
Specifications
Details / Remarks
1.3.1 RAS Type Advanced RASrequired
Processor RAS
1.3.2 ECC Cache Required
1.3.3 Memory Address Parity Required 1.3.4 Resilient QPI Links Required 1.3.5 Redundant processor to I/O hub links Required 1.3.6 Machine Check Architecture (MCA) Required
QPI RAS
1.3.7 QPI protocol CRC protection Required
1.3.8 QPI self-healing Required
1.3.9 QPI clock failover Required 1.3.10 QPI packet retry Required
Memory RAS
1.3.11 Chipkill /Extended ECC/ Chipspare Required 1.3.12 Redundant Bit Steering Required 1.3.13 Memory Scrubbing Required
Reliability, Availability and Serviceability (RAS) Compliance(Y / N) for RAS
Specifications
Details / Remarks
1.3.14 Memory mirroring Required 1.3.15 Memory DIMM sparing Required 1.3.16 Memory Rank Sparing Required
SMI RAS
1.3.17 SMI Protocol CRC Protection Required 1.3.18 SMI Lane failover Required 1.3.19 SMI Clock failover Required 1.3.20 SMI Packet retry Required
System-wide RAS features
1.3.21 Hot-swap components (HDDs, Power
supplies, fans etc.) Required 1.3.22 Integrated Management Module Required 1.3.23 Predictive Failure Analysis Required 1.3.24 Light Path Diagnostics Required 1.3.25 Dynamic System Analysis Required 1.4 Blade Servers for SAP Application Instance
Feature /
Specifications MinimumSpecification Required Compliance Proposed Capacity / Hardware ( Bidder can propose technically superior components ) Details / Remarks (Y / N) for minimum specification s 1.4.1
Make and Model of
Server Required 1.4.2 Form Factor Blade
1.4.3
Processor Type The Server should be based on Intel E7 based x86-64-bit architecture that is latest in respective product line & server should have the capability of supporting 32-bit applications as well.
1.4.4
Processors Should have minimum 2.0 GHz, 16 MB L3 cache and should provide minimum 13500 SAPS to application instance. Should be 100% scalable 1.4.5
Server RAM The server must be with the Minimum of 8 GB RAM per core, DDR3 RDIMM memory modules having same DIMM for all slots. If Vms are installed, the same can be increased as per the solution requirement. Blade should have minimum 24 DIMM slots.
1.4.6
Memory Protection Advanced ECC (Chipkill/ Extended ECC/ Chipspare), with multi-bit error
protection support 1.4.7 HDD 2 x 600GB 6G hot plugSFF SAS Internal HDD 1.4.8 HDD Speed 15/10 K RPM
1.4.9 RAID Support forinternal HDDs With Hardware orSoftware RAID-1
1.4.10
Ethernet 2 (Two) Ethernet Controllers each with 2 X 10G Ethernet ports with 4 Nos vNIC support per port. 1.4.11 Ethernet feature Should support andprovide the NIC
teaming / bonding
1.4.12
OS Support and
Clustering Support RHEL, SLES, VMware,Citrix XenServer, RHEV, MS-Hyper-V. The OS should be latest available
version. The Operating systems (OS) should be 64-bit industry compliant LINUX and should support both 32-bit and 64-bit
applications.
1.4.13
DVD ROM Should support Internal or External DVD-ROM for software and O.S. installation and patch
management. 1.4.14
Manageability Should support unified management suite that can monitor and manage all the servers
1.4.15
Should provide the facility and
interfaces / cables for connecting Monitor, USB keyboard and USB mouse to the server
Required
1.4.16
No single point of failure for Fan Assembly
Required on chassis level
1.4.17 Power Supply withredundancy Required on chassislevel
1.4.18
Should provide LINUX OS,
licenses along with media
Required
1.4.19 Hardware shouldbe compatible with SAP applications Required 1.4.20 Application instances should be running on separate physical servers to avoid single point of failure Required
1.4.21 USB Ports Offered server shouldhave 1 front and 2 internal USB 2.0 ports
1.4.22
Predictive Failure
Analysis Offered Server shouldhave feature of Predictive Failure Analysis on
Processors, memory, drives, in servers fans
and power supplies in the chassis 1.4.23 Should provide 5 years onsite comprehensive warranty & Hardware maintenance support. Required
1.4.24 Number of Serversor partitions As per solutionrequirement
1.5 Blade Servers for DB – CI Instance
Feature /
Specifications MinimumSpecification Required Compliance Proposed Capacity / Hardware ( Bidder can propose technically superior component s) Details / Remarks (Y / N) for minimum specification s 1.5.1
Make and Model of
the servers Required 1.5.2 Form Factor Blade
1.5.3 The nodes of the cluster should be of same make and model Required 1.5.4 With reference to SAP Hardware Sizing System Integrator must ensure that required SAPS are allocated to SAP application module. At any point in time resource partitions should not run
with less resources. 1.5.5 The failover partition should be capable of providing same SAPS in the event of failover
Required
1.5.6 Each SAP instance in production system should be running in independent partitions Required 1.5.7 The partitions should have their own operating systems. Required 1.5.8 The DB and CI systems should be clustered with HA clustering technology and there should be no single point of failure in the system Required
1.5.9 All servers should have same x86-64 processors Required 1.5.10 Systems should have redundant fans Required at chassis level 1.5.11 The systems should be provided with redundant power supplies Required at chassis level
1.5.12 All the components including disks, power supplies, fans should be hot pluggable
Required
1.5.13 Processor Type The Server should be based Intel E7 on x86-64-bit architecture to support minimum 2 processors that is latest in respective product line & server should have the
capability of supporting 32-bit applications as well. 1.5.14 Processors Should have minimum
2.0 GHz, 16 MB L3 cache and should provide minimum 12500 SAPS to application instance. 1.5.15 Number of
Processors As per SAPSrequirement of the SAP application modules 1.5.16 Processor
Scalability Processor should bescalable to provide 100% scalability 1.5.17 Minimum SAPS
allocated for each SAP application module must be offered as per mandatory requirement in the hardware sizing, Integrator need to put appropriate buffer considering OS and other overheads. Required 1.5.18 Minimum Memory in each SAP application module must be offered as per mandatory requirement in the hardware sizing, Integrator need to put appropriate buffer considering OS and other overheads. Required
1.5.19 Server RAM The server must be with the Minimum of 8 GB RAM per core, DDR3 RDIMM memory modules having same DIMM for all slots. If Vms are installed, the same can be increased as per the solution requirement. Blade
should have minimum 24 DIMM slots
1.5.20 Memory Protection Advanced ECC (Chipkill/ Extended ECC/ Chipspare) with multi-bit error protection support 1.5.21 Partitions Each SAP instance
should run in independent virtual partitions with dedicated resources CPU/memory/IO and independent operating system
1.5.22 Any software error in one partition should not affect the other partition
Required 1.5.23 OS in each partition should be upgradeable, without impacting the other Required 1.5.24 Each partition should have capability to start and shutdown independently of the other Required 1.5.25 Any configuration change in one partition should not impact other partition.
Required
1.5.26 IO adapters All adapters should be PCI/X or PCI/E
1.5.27 FC ports All FC ports for storage connectivity should be 8Gbps and should be provided in redundant config with multi pathing enabled. They should be provided with appropriate drivers and licenses 1.5.28 Ethernet Adapter 2 (two) Ethernet
Controller with 2 x 10G ports,
The controllers should support 4 nos vNIC
per port. 1.5.29 All Ethernet adapters should be redundant, 10/100/1000 autosensing, should be provided with automatic failover or with link aggregation for each partition. Relevant software and licenses should be also provided
Required
1.5.30 Internal Disks 2 x 600GB 6G hot plug SFF SAS Internal HDD in RAID-1
1.5.31 HDD Speed 15/10 K RPM 1.5.32 The OS should be
mirrored for all partitions
Required
1.5.33 Operating system Latest OS version of 64 bit Linux operating system with latest patch level. 1.5.34 OS should be
capable of running 64bit SAP and 64bit Oracle database.
Required
1.5.35 All software licenses should be provided that are offered for the solution
Required
1.5.36 Cluster and high
availability The systems should bemade highly available using OS clustering solutions 1.5.37 Redundant heart beat paths to be provided. Paths should be physically isolated Required 1.5.38 Cluster solution should be OEM or SAP certified solution Required
1.5.39 DVD ROM Each partition should be capable to have online access to internal/External DVD. 1.5.40 USB Ports Server should have 1
front and 2 internal USB 2.0 ports 1.5.41 Predictive Failure
Analysis Server should havefeature of Predictive Failure Analysis on Processors, memory, drives, in servers fans and power supplies in the chassis 1.5.42 Should provide 5 years onsite comprehensive warranty & Hardware maintenance support. Required
1.5.43 Number of Servers As per solution requirement
2.0 Blade Servers for Backup Software
Feature / Specifications Minimum Specification Required Compliance Proposed Capacity / Hardware ( Bidder can propose technically superior component s) Details /Remarks (Y / N) for minimum specifications
2.1 Make and Model Required 2.2 Form Factor Blade 2.3
Processor System Integrator topropose 2.4 Number ofProcessor System Integrator topropose 2.5
Processor Upgrade
Upgradeable to provide 50% scalability for future expansion in storage 2.6 Server RAM System Integrator topropose
2.7 Server RAM expansion capacity Upgradeable to provide 50% scalability 2.8
Internal HDDs 2 x 600GB 6G hot plugSFF SAS Internal HDD or SAN boot in RAID-1 (additional storage capacity needs to be factored for the same) 2.9 HDD Speed 15/10 K RPM 2.10 Internal Storage Controller With Hardware / software RAID-0,1 support 2.11 Ethernet 2 (Two) nos. 10G Ethernet Ports with 4 nos vNIC support per port.
2.12
Ethernet feature
Should support and provide the NIC teaming / bonding. 2.13 IO Adaptors All adapters should bePCI/X or PCI/E
2.14
FC Ports
All FC ports for storage connectivity should be 8Gbps and should be provided in redundant config with multi pathing enabled. They should be provided with appropriate drivers and licenses 2.15 Support for DVD-ROM
(Internal/External) Required 2.16 Redundant PowerSupply Required 2.17 No single point of
failure for Fan
Assembly Required 2.18 Operating System System Integrator needs to provide details 2.19 System Integrator needs to supply the operating system media and requisite license
environment.
2.20 USB Ports Server should have 1front and 2 internal USB 2.0 ports
2.21
Predictive Failure
Analysis Server should havefeature of Predictive Failure Analysis on Processors, memory, drives, in servers fans and power supplies in the chassis 2.22 Should provide 5 years onsite comprehensive warranty and hardware maintenance support Required 2.23 Number of Servers/ Partitions As per solutionrequirement
3.0 Blade Servers for EMS (Enterprise Management System)
Feature / Specifications Minimum Specification Required Compliance Proposed Capacity / Hardware ( Bidder can propose technically superior component s) Details /Remarks (Y / N) for minimum specifications 3.1
Make and Model Required 3.2 Form Factor Blade
3.3
Processor Type
The Server should be based on x86-64-bit architecture that is latest in respective product line & server should have the capability of supporting 32-bit applications as well.
3.4 Processor As per solutionrequirement 3.5 Number OfProcessor As per solution
requirement 3.6 Processor Upgrade
Upgradeable to provide 50% scalability for future expansion
3.7
Server RAM As per solutionrequirement 3.8
Memory protection
Advanced ECC with multi-bit error protection support 3.9 Server RAM expansion capacity Upgradeable to provide 100% scalability for future expansion
3.10 Internal HDDs 2 x 600GB 6G hot plug SFF SAS with RAID-1 3.11 HDD Speed 10K RPM
3.12 Internal StorageController WithHardware/Software RAID-0,1 support
3.13
For any additional hard-disk
requirement as per the solution, System Integrator needs to propose the additional storage space on SAN. Required 3.14 Ethernet 2(Two) nos. 10GB Ethernet ports, with 4 nos vNIC support per port
3.15
Ethernet feature
Should support and provide the NIC teaming / bonding. 3.16 Support for DVD-ROM
3.17 Redundant PowerSupply Required 3.18 No single point of
failure for Fan
Assembly Required 3.19
Redundant Power
Supply Required
3.20 Operating System As per the solution 3.21 VirtualizationSupport Required
3.22
System Integrator needs to supply the operating system media and license including virtualization
licenses. Required
3.23 USB Ports Server should have 1front and 2 internal USB 2.0 ports
3.24
Predictive Failure
Analysis Server should havefeature of Predictive Failure Analysis on Processors, memory, drives, in servers fans and power supplies in the chassis 3.25 Should provide 5 years onsite comprehensive warranty and maintenance support Required
4.0 Blade Servers for Infrastructure Setup (Domain Controller, DNS, DHCP, NTP, Windows Update Service, Antivirus) - Delhi
Feature / Specifications Minimum Specification Required Compliance Proposed Capacity / Hardware ( Bidder can propose technically superior
components) Details /Remarks (Y / N) for
minimum specifications
4.1 Make and Model Required 4.2 Form Factor Blade
4.3
Processor Type
The Server should be based on x86-64-bit architecture that is latest in respective product line & server should have the capability of supporting 32-bit applications as well. 4.4 Processor 2 * 12 Core, Should have minimum 2.7 GHz, 30MB L3 Cache 4.5 Number ofProcessor Two
4.6
Server RAM
16GB with Advanced Error checking and correcting (ECC) 4.7 Server RAMexpansion
capacity
Upgradeable to provide 100% scalability for future expansion 4.8 Internal HDDs 2 x 600GB 6G hot plug SFF Internal HDD in RAID-1 4.9 HDD Speed 15/10 K RPM
4.10 Internal StorageController With Hardware RAID-0,1 support 4.11
Ethernet
2 (Two) nos. 10G Ethernet ports, with 4 nos vNIC support per port
4.12
Ethernet feature
Should support and provide the NIC teaming / bonding. 4.13 DVD-ROM(Internal /
External) Required
4.14 Redundant PowerSupply Required on chassislevel 4.15 No single point of
failure for Fan
Assembly Required on chassislevel 4.16 Operating System – windows 2012 System Integrator needs to propose standard /enterprise edition and 32/64 bits as per requirement. 4.17
Virtualization Support
The virtualization should be offered with management component to manage virtual machines 4.18 System Integrator need to supply windows 2012 OS with downgrade rights. Required 4.19 System Integrator needs to supply the operating system media and license including virtualization
licenses. Required
4.20 USB Ports Server should have 1front and 2 internal USB 2.0 ports
4.21
Predictive Failure
Analysis Server should havefeature of Predictive Failure Analysis on Processors, memory, drives, in servers fans and power supplies in the chassis 4.22 Should provide 5 years onsite comprehensive warranty and maintenance support Required
4.23 Domain Controller role should be running on separate physical servers in virtualized environment to avoid single point
of failure Required 4.24 Number of Servers/ Virtual partitions 5 Nos
5.0 Blade Servers for Anti-Spam & E-Mail Gateway Antivirus
Feature / Specifications Minimum Specification Required Compliance Proposed Capacity / Hardware ( System Integrator can propose technically superior
components) Details /Remarks (Y / N) for
minimum specifications
5.1 Make and Model Required 5.2 Form Factor Blade
5.3
Processor Type
The Server should be based on x86-64-bit architecture that is latest in respective product line & server should have the capability of supporting 32-bit applications as well. 5.4 Processor 2 * 12 Core, Shouldhave minimum 2.7
GHz, 30MB L3 Cache 5.5 Number ofProcessor Two
5.6 Server RAM 16GB with AdvancedError checking and correcting (ECC) 5.7 Server RAM
expansion capacity
Upgradeable to provide 100% scalability for future expansion
5.8
Internal HDDs
2 x 600GB 6G hot plug SFF Internal HDD or SAN boot in RAID-1
5.9 HDD Speed 15/10 K RPM
5.10 Internal StorageController With Hardware RAID-0,1 support 5.11
Ethernet
2(Two) nos. 10G Ethernet ports, with 4 nos vNIC support per port
5.12
Ethernet feature
Should support and provide the NIC teaming / bonding. 5.13 DVD-ROM(Internal /
External) Required 5.14 Redundant Power
Supply Required at chassislevel 5.15 No single point offailure for Fan
Assembly Required at chassislevel 5.16
Operating System
System Integrator to propose the OS as per solution requirements. 5.17 Virtualization Support Required 5.18 System Integrator needs to supply the operating system media and license including virtualization
licenses. Required
5.19 USB Ports Server should have 1front and 2 internal USB 2.0 ports
5.20
Predictive Failure
Analysis Server should havefeature of Predictive Failure Analysis on Processors, memory, drives, in servers fans and power supplies in the chassis 5.21 Should provide 5 years onsite comprehensive warranty and maintenance support Required 5.22 Email anti-spam and antivirus serer should be running on separate physical servers in
virtualized as well as non-virtualized environment to avoid single point of failure
5.23 Number of Servers/ Virtual partitions 2 Nos
6.0 Blade Servers for E-Mail Upgrade (Microsoft Exchange, E-Mail Migration and Setup)
Feature / Specifications Minimum Specification Required Compliance Proposed Capacity / Hardware ( System Integrator can propose technically superior
components) Details /Remarks (Y / N) for
minimum specifications
6.1
Make and Model Required 6.2 Form Factor Blade
6.3
Processor Type
The processor should be based on x86-64-bit architecture that is latest in respective product line and Shall support 32-bit applications 6.4 Processor 2 * 12 Core, Should have minimum 2.7 GHz, 30MB L3 Cache 6.5 Number ofProcessor Two
6.6
Server RAM
16 GB with Error checking and correcting (ECC) 6.7 Server RAMexpansion
capacity
Upgradeable to provide 100% scalability for future expansion
6.8
Internal HDDs 2 x 600GB 6G hot plugSAS in RAID-1 6.9 HDD Speed 15/10 K RPM
6.10 Internal StorageController With Hardware RAID-0,1 support 6.11 Ethernet 2 (two) x 10 Gigabit
Ethernet Ports with 4 nos. vNIC support per port
6.12
Ethernet feature
Should support and provide the NIC teaming / bonding. 6.13 I/O Sots Minimum two I/O slots 6.14
HBA Port
2 port HBA for
connecting to the SAN Switch
6.15 DVD-ROM(Internal /
External) Required 6.16 Redundant PowerSupply Required 6.17 No single point offailure for Fan
Assembly Required
6.18 USB Ports Server should have 1front and 2 internal USB 2.0 ports
6.19
Predictive Failure
Analysis Server should havefeature of Predictive Failure Analysis on Processors, memory, drives, in servers fans and power supplies in the chassis 6.20 Operating System – Windows Server 2012 Required 6.21 System Integrator needs to supply the operating system media and license. Required 6.22 System Integrator to supply Exchange 2013 Media, User CALs, SSL Digital Certificates (Four
SAN names) Required
6.23 Should provide 5 years onsite comprehensive warranty and maintenance support Required
6.24 Number ofServers / Virtual
Partition 4 Nos
7.0 Rack Servers for Domain Controller, DNS, DHCP, Windows Update Service and Antivirus – Palatana, Tripura
Feature / Specifications Minimum Specification Required Compliance Proposed Capacity / Hardware ( System Integrator can propose technically superior
components) Details /Remarks (Y / N) for
minimum specifications
7.1
Make and Model Required 7.2 Form Factor Rack
7.3
Processor Type
The Server should be based on x86-64-bit architecture that is latest in respective product line & server should have the capability of supporting 32-bit applications as well. 7.4 Processor 2 * 6 Core, Should have minimum 2.0 GHz, 15MB L3 Cache 7.5 Number ofProcessor Two
7.6 Processor Upgrade
Upgradeable to provide 100% scalability for future expansion
7.7
Server RAM
48GB with Advanced Error checking and correcting (ECC) 7.8 Server RAMexpansion
capacity
Upgradeable to provide 100% scalability for future expansion
7.9 Internal HDDs 6 x 600GB 6G hot plugSFF Internal HDD 7.10 HDD Speed 15/10 K RPM
RAID-Controller 0,1,5 support 7.12
Ethernet Four Gigabit EthernetPorts 7.13
Ethernet feature
Should support and provide the NIC teaming / bonding. 7.14 DVD-ROM(Internal /
External) Required 7.15 Redundant PowerSupply Required 7.16 No single point offailure for Fan
Assembly Required 7.17 Operating System – windows 2012 System Integrator needs to propose standard /enterprise edition and 32/64 bits as per requirement. 7.18 VirtualizationSupport Required
7.19 System Integrator need to supply windows 2012 OS with downgrade rights. Required 7.20 System Integrator needs to supply the operating system media and license including virtualization licenses. Required 7.21 Should provide 5 years onsite comprehensive warranty and maintenance support Required 7.22 Number ofServers / Virtual
SECTION 2.3
TECHNICAL SPECIFICATION FOR STORAGE
1.0 STORAGE AREA NETWORK (SAN) – DELHI Feature /
Specifications MinimumSpecification Required Compliance Proposed Capacity / Hardware ( Bidder can propose technically superior component s) Details / Remarks (Y / N) for minimum specifications 1.1
Make and Model Required
1.2
System Integrator need to propose the number of disks for total no of IOPS as per SAPS (minimum 50% of the total SAPS excluding HA)
Required System Integrator need to provide the number of disks for production storage 1.3
For SAP production servers System Integrator need to provide 600 GB, 15/10 K RPM, 6Gbps SAS HDD Required 1.4
The usable capacity for the production storage should not be less than 5 TB with RAID 1+0 and 1 TB raw SSD in RAID 5
Required
1.5
Storage for IDES, Development & Quality Systems, Solution Manager, SAP Router Staging / disk cloning, SAP DVDs & reserve
8 TB usable disk space With RAID-5 , SAS Disks
space 1.6
Usable Storage for Desktop Users should not be less than 2 TB (NL-SAS Disks) in RAID 6
Required
1.7
Highly available NAS Gateways based on Windows storage server 2012 platform for use with
different applications and users roaming profiles
Required
1.8 NAS gatewaysshould be integrated with AD
Required
1.9
Disk Speed for IDES, development & Quality, Staging/Disk Cloning & reserve, Desktop Users
10K RPM
1.10 Disk Speed for SAPproduction and E-Mail Servers
15 / 10 K RPM
1.11
Disk Drive Support 300/450/900 GB hot-pluggable enterprise SAS HDD, 100/200/400 GB SSD and 1/2/3 TB NL- SAS HDD 1.12
Cache (Memory) System Integrator need to provide minimum 16GB cache memory to meet the performance.
1.13
Storage array shall have either Cache Duplexing, Disk de-staging or battery backup support to avoid any kind of data loss.
Required
1.14 Storage Expansion 50% scalability forfuture expansion 1.15 Hot Spare Disks Minimum 1 hot spareper 10 disks are
required of each type 1.16 RAID support forstorage controllers Storage Array shallsupport standard
and Raid 6 other various RAID concepts 1.17 Storage shall beoffered with
required licenses.
As per requirement of RFP with 10% buffer. Irrespective of OS.
1.18
Storage should have a facility of create snapshots/ pointing copies/ flash copies/ Automatic Tiering of Data.
Required
1.19
The storage array should be based on FC front-end and SAS backend with dual redundant controllers Required 1.20 There shall be no single point of failure into the array system including Power Supplies, Cache, Cache boards, Front-end Boards, Backend Boards Required
1.21 Host Ports 4 Nos. per controller 1.22 Back-end Ports 4 Nos. per controller 1.23 Ports Bandwidth 8Gbps or higher onhost port
1.24
Load Balancing &
Multi-path Should support Multi-path and load balancing. System Integrator need to provide required software 1.25 Operating System
Support The storage arrayshould support industry-leading Operating System platforms including: various versions of Microsoft Windows, Sun Solaris, HP-UX, IBM-AIX, and Linux.
1.26
Storage Shall support all above operating systems in Clustering.
Required
1.27
The Storage system should support online replacement of failed disks without interruption or rebooting the array Required
1.28 Power Supply Should provide hotplug redundant power supplies 1.29
FAN Hot-plug redundant FAN
1.30
Offered storage shall support online non-disruptive firmware upgrade for both Controller
Required
1.31
The storage system should support automatic detection of errors, error logging and notification. Required 1.32
The storage system should support hardware based data replication to a remote sites in two geographical locations
Required
1.33
Storage
Management System Integrator toprovide the storage management software and appropriate licenses. It should have the flexibility to allow the users to set up, enable and delete volumes
1.34
System Integrator should provide dual-controller arrays to avoid a single point
of failure. Controller should be active-active 1.35 Should provide 5 years onsite comprehensive warranty and maintenance support Required
1.36 No of SAN Storagerequired 1 No.
2.0 NETWORK ATTACHED STORAGE (NAS) – PALATANA, TRIPURA Feature /
Specifications MinimumSpecification Required Compliance Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks (Y / N) for minimum specifications 2.1
Make and Model Required
2.2 LDAP (Active Directory Services) Integration
Functionality
Required
2.3 The usable capacity for the storage should not be less than 3 TB with RAID - 6
Required
2.4 Cache (Memory) System Integrator needs to provide appropriate cache memory to meet the performance
2.5 Storage Expansion 100% scalability for future expansion 2.6 Hot Spare Disks Appropriate number
of disks to be provided.
2.7 RAID support for
storage controllers Storage Array shallsupport standard Raid 0,1, 0+1/1+0, 5 and Raid 6 other various RAID concepts 2.8 There shall be no
single point of failure into the system including Power Supplies, Cache, Cache boards, Front-end Boards, Backend Boards Required
2.9 Ports As per solution requirement 2.10 Disk Types Support SAS, NL SAS 2.11 Protocols Supported CIFS, NFS 2.12 Operating System
Support The storage arrayshould support Microsoft Windows Platform. The storage shall be based on Windows Storage Server. (Primarily the storage will be used for storing OTPC users official data) 2.13 The Storage system
should support online replacement of failed disks without interruption or rebooting Required
2.14 Power Supply Should provide hot plug redundant power supplies 2.15 FAN Hot-plug redundant
FAN 2.16 The storage system
should support automatic detection of errors, error logging and notification. Required 2.17 Storage
Management System Integrator toprovide the storage management
software and appropriate licenses. It should have the flexibility to allow the users to set up, enable and delete volumes 2.18 Should provide 5 years onsite comprehensive warranty and maintenance support Required 2.19 No of Storage – 1 No Required
SECTION 2.4
TECHNICAL SPECIFICATION FOR TAPE LIBRARY / DRIVE 1.0 LTO-6 TAPE LIBRARY – DELHI
Feature /
Specifications MinimumSpecification Required Compliance Proposed Capacity / Hardware ( Bidder can propose technically superior components) Details / Remarks (Y / N) for minimum specifications 1.1
Make and Model Required
1.2
Modular Architecture to allow
configuration, add capacity and increase performance as per requirement.
Required
1.3
Should have feature for accurate
identification of bar-coded cartridges which is important for unattended and automated backup application
Required
1.4
Calibration Should be able to do automatic calibration and therefore shall not require downtime for periodic alignment 1.5 Capacity Minimum 2 (two)LTO6 FC Half