Page 37 of 83 Confidential & Proprietary The Supplier is responsible for all unpacking and installation of Products. The Supplier will test all system operations and accomplish all adjustments necessary for successful and continuous operation of the software at all installation sites.
4.33 Technical Documentation
The Technical Documentation involving detailed instruction for operation and maintenance of the hardware (if any) and software is to be delivered. The language of the documentation should be English.
4.34 Right to use defective product
If after delivery, acceptance and installation and within the guarantee and AMC period, the operation or use of the product is found to be unsatisfactory, the Bank shall have the right to continue to operate or use such product until rectification of defects, errors or omissions by partial or complete replacement is made without interfering with the Bank’s operation.
4.35 Repeat Orders
4.35.1 Bank reserves the right to place repeat order/s on the bidder under the same terms and conditions within a period of 6 months from the date of acceptance of purchase order by the bidder.
4.35.3 The bank reserves the right to re-negotiate the price with the bidder for downward revision of the prices.
************
Page 38 of 83 Confidential & Proprietary PART 5: FUNCTIONAL SPECIFICATIONS
Functionalities to be implemented in Hardware and Software as per the details mentioned.
Specifications for buying High Performance Blade Chassis/Enclosure
Sl. No Features Specifications Required
1 Form Factor Chassis to house at least 8 Compute Nodes.
2 IO Modules
• The chassis must have Server side FCoE connectivity in case vendor is quoting Converged Network Adapter on to the blade server.
• The chassis must have Server side 10 Gig Ethernet connectivity and 8 Gig Fiber Channel connectivity in
redundancy in case vendor is quoting separate 10 G Ethernet NIC and 8 Gig FC HBA on to the blade server.
•The vendor needs to provide additional / external Network (10 Gig )and FC Fabric switches (8 Gig), in case they are
proposing Pass-Thru modules in the solution.
In case direct FC connectivity is not supported on the Chassis or enclosure, 24 port SAN switches should be provided separately.
3 Midplane
Chassis should have a highly reliable passive mid plane for providing connectivity of the shared resources to the compute nodes in a highly reliable manner.
4 Power Modules
The enclosure should be populated fully with power supplies of the highest capacity available with the vendor.
Power supplies should support N+N as well as N+1 redundancy configuration, where N is greater than 1.
5 and compute node power management and diagnostics for elements including Chassis, I/O options and compute nodes.
6 Support for Multiple Platform
Should provide support for multiple platforms in x86 servers within the same enclosure.
7
Cooling
Each blade enclosure should have a cooling subsystem consisting of redundant hot pluggable fans or blowers enabled with technologies for improved power
consumption and acoustics
Page 39 of 83 Confidential & Proprietary 8 Warranty 3 years comprehensive warranty with 24x7 6-Hour Call to
Repair (No 6 HR CTR) Support.
9.
Alerts
The server should be able to alert impending failures on maximum number of components. The components covered under alerting mechanism should at least include Server components, Storage components, Switch components and Chassis components. It should also be able to provide "Call Home" type of alert.
10.
Integrated Management User Interface
The proposed solution should have an Integrated management where integration of Servers, Storage, Networking and other available hardware resources in the solution are managed using a common GUI
Blade Specifications
1 CPU 2 x Intel Xeon Eight Core E5-2670 CPU @ 2.6 GHz
or better
2 Cache L3 20 MB of L3 Cache
3 Chipset Intel Chipset C600
4 Memory 16GB RDIMMS Memory to provide 256GB memory
per node scalable up to 512 GB (min 16 Slots) 5 Memory protection support ECC and Memory Sparing
6 SCSI Controllers Integrated Hardware Raid Controller to supports Hardware Raid RAID 0, 1.
7 Disk Drives 2 x 300GB 6Gbps10K SAS Hard Disk Drive
8 Graphics Controller 16MB SDRAM
9 Ethernet Adapter
Server should be configured with 2 Number of 10G Ethernet ports, also support FCOE and ISCSI functionality on demand
10 Fiber Channel HBA
Connectivity Dual Port 8Gbps Fiber Channel / FCoE adapter
11 Warranty 3 years comprehensive warranty with 24x7
6-Hour Call to Repair (No 6 HR CTR) Support.
12 Failure Alerting Mechanism
The server should be able to alert impending failures on maximum number of components. The
components covered under alerting mechanism should at least include Processor, memory and HDDs
13 OS Support
Microsoft Windows Server 2008 R2, Red Hat Enterprise Linux 5.7 and above, SUSE Linux VMware ESX 4.1 and above, Xen Server
Page 40 of 83 Confidential & Proprietary
Compliance sheet for Specifications of Unified Storage System (standard)
i) The array should have support for 2 nos. of SAN controllers for better performance and redundancy. The storage system should also support 2 nos. of dedicated NAS controller for file workload.
Total 4 nos. of storage controllers.
iii) The back-end architecture should be based on SAS II (@6Gbps) technology.
2 Host/Back-end Interface
The Dual SAN Controllers should support FC for Front-end host connectivity. Each SAN controller should have 2x8 Gbps FC ports, min. 2 nos of SAS 6Gbps backend physical ports for disk
connectivity. The storage should also provide with 4x1 Gbps IP ports for NAS connectivity.
3. Disk drive support
The array should support inter-mixing of dual-ported SSD, FC/SAS (both with 15K RPM) and SATA/Mid/NL SAS. The drive interface should be 6Gbps. The array must be capable of supporting 240 drives with the proposed pair of controllers and support 480 HDD by simple controller upgrade.
4 Storage cache
i) The array should have min. 16 GB cache per SAN controllers, i.e. 32GB Cache across dual controller.
iv) The array must have complete cache protection mechanism either by de-staging data or providing complete cache data protection with battery backup for up to 72 hours or more.
5 Protocol support
The array should support Block level/NAS protocols (FC/ FCoE/
iSCSI/CIFS/NFS) on dedicated pair of SAN controllers.
6 Storage Capacity
OS Data - 5TB RAID 1 with 5000 IOPS (minimum 36 x 15K SAS Drives)
User Data - 10TB RAID 5 (max 7D+1P) with 1000 IOPS (minimum 10 x 15K SAS Drives)
User Data - 5TB RAID 5/6 (max 7D+1P) with 500 IOPS (minimum 5 SATA Disks)
The enclosure should able to accommodate 25 TB over and above to the above mentioned storage.
7 Redundancy The storage array should be configured in a No Single Point of failure including Storage Controller card, Cache memory, Power supply and cooling fans with power cords, etc.
Page 41 of 83 Confidential & Proprietary 8 OS support The storage array should support industry-leading Operating
System platforms & clustering including: Windows Server 2008, 2012, VMWare, Linux, Sun Solaris, HP-UX, IBM-AIX, OS, etc.
9 Global Hot Spare Disks
The storage array should support Global Hot Spare (HS) Disks. A minimum of one global hot spare per 30 disks should be supplied and configured. These should be of the same type as used for the capacity requirements.
10 Automated Storage Tiering
The storage array systems must natively provide automated Sub-LUN tiering of data within the Storage to achieve improved
performance and lower Total cost of Ownership. The Storage should have auto tiering between available three tiers.If additional software is required, the same needs to be provided for full SAN capacity. It should also support policy based movement of Data between different tier for NAS volume.
13 On-line RAID Group
Expansion
The storage array must support RAID 0,1,5,6,10 levels with online expansion of RAID Group/Disk Group.
15 Snapshot and Full
Copy/Clone Functionality
The array should support controller-based functionality for pointer based snap copies as well as full physical copies.
16 Mirroring / Replication
i) The storage array should support both Sync and Async mode data replication at the storage controller level.
ii) The storage array must have the capability to do array based remote replication using FCIP or IP technology
17 Virtual /Thin provisioning
The storage array should be provided with virtual/Thin provisioning for proposed storage capacity.
18 Data in Place upgrade
The proposed storage must support seamless data-in-place upgrade of existing storage controllers without having to change the disk subsystem.
19 Storage Management
Storage Management Software should be provided with simple to use Browser based interface and CLI
20 Data
Compression
Storage array should support both File & block level compression for NAS and SAN Data.
21 Software / Firmware
Should Support online firmware upgrade of firmware, etc. without a need for downtime.
22 Warranty 3 years comprehensive warranty with 24x7 6-Hour Call to Repair (No 6 HR CTR) Support.
23 Virtualisation Integration
i) The Storage should be fully certified for all supported protocols to virtualized application environments.
Page 42 of 83 Confidential & Proprietary v) The storage solution should be capable of providing
multi-pathing software with failover and load-balancing functionality for the virtualised OS, various OS platforms such as Windows and UNIX platforms
2
User Interface
The proposed backup solution shall have same GUI across heterogeneous platform to ensure easy administration.
3 The proposed backup solution software has inbuilt consistent GUI for centralized management of backup domain.
4 High Availability Features
The proposed backup solution should support tape to tape copy.
5 Licensing
The proposed backup solution should support both LAN and LAN Free backups and should offer CPU independent Licensing policy.
6 Multi Streaming The proposed backup solution supports the capability to write up to 32 data streams.
7 Media
Management
The proposed backup solution has in-built media management and supports cross platform device and media sharing in SAN environment. It provides a centralized scratched pool thus ensuring backups never fail for media.
The proposed backup solution has in-built frequency and
The proposed backup solution has certified “hot-online”
backup solution for different type of databases such as Oracle, MS SQL, Sybase , Vmware , Exchange , SAP etc.
The proposed backup solution shall also support granular recovery for Vmware , Exchange server, Share point Portal
The proposed backup solution shall provide granularity of single file restore.
Page 43 of 83 Confidential & Proprietary The backup software should support object level restore.
18 Search and Compliance
The proposed backup should support searching data using either structured and unstructured Information
The proposed backup software should support contextual search based on meaning.
22 Other Features
The proposed backup solution must support full automated transfer of disk backup images to tape on a scheduled basis.
The proposed backup solution shall support synthetic full backup / Virtual full backups.
The proposed backup solution shall also support disk based virtual full backup approach.
The proposed backup solution shall be able to copy data across firewall.
The proposed backup solution shall support automatic skipping of backup during holidays.
The proposed backup solution must support at least AES 256-bit encryption capabilities.
The internal backup catalogue database should not have a big foot print.
The backup software should support object based restore option which is one of the most granular option available with any backup software vendor.
The backup software should support scheduled recovery of Exchange , SQL and Oracle databases to perform restore drills.
Sr
No Specification for virtualization Software Virtualization Platform and Management
1
Virtualization software shall provide a Virtualization layer that sits directly on the bare metal server hardware with no dependence on a general purpose OS for greater reliability and security.
2
Virtualization software should be able to boot from iSCSI, FCoE, and Fibre Channel SAN
3
Virtualization software shall have the capability to create Virtual Machines with upto 4 processors for all the desktop guest operating system in virtual machines and with upto 8 processors for all the server guest operating system in virtual machines supported by the hypervisor.
4
Virtualization software shall integrate with NAS, FC, FCoE,and iSCSI SAN and infrastructure from leading vendors Leverage high performance shared storage to centralize virtual machine file storage for greater manageability, flexibility and availability.
Page 44 of 83 Confidential & Proprietary 5
Virtualization software shall have the capability for creating virtual machine templates to provision new servers
6
Virtualization software shall allow taking snapshots of the virtual machines to be able to revert back to an older state if required.
7
Virtualization software should have the ability to thin provisions disks to avoid allocating all storage space upfront. Full monitoring capabilities and alerts to prevent from accidentally running out of physical storage space.
8
Virtualization software should Support live Virtual Machine migration with enhanced CPU compatibility
9 Virtualization software should support of storage vm's on clustered file share 10
Virtualization Software to support unlimited live migration of VM's over 1G& 10G networks
11
Virtualization software should have the ability to live migrate VM files from one storage array to another without no VM downtime. Support this migration from one storage protocol to another (ex. FC, iSCSI, NFS, DAS)
12
Virtualization Software should support migrations of VM's even if they are not stored on a common storage.
13
Virtualization software shall be able to dynamically allocate and balance
computing capacity across collections of hardware resources of one physical box aggregated into one unified resource pool
14
Virtualization software should provide dynamic power management such that incase during off peak hours not all servers are required to be powered on due to less load it should shut down few servers to save power.
15
Virtualization software shall have High Availability capabilities for the virtual machines in the sense if in case one server fails all the Virtual machines running on that server shall be able to migrate automatically to another physical server running same virtualization software.
16
Virtualization software should have the ability to provide no-downtime protection for any VM, not just for applications that are cluster aware, in the event of a hardware failure.
17
Virtualization software should provide patch management capabilities such that it should be able to update patches on it's own hypervisor as well as the Windows based guest operating systems
18
Virtualization software should have the ability to manage virtual switches at a cluster level by creating a distributed switch that can span an entire cluster and is VM mobility aware.
19
Virtualization software should provides an integrated network firewall for virtual network with centralized mgmt, suitable for all virtualized applications
20 Virtualization software must support built-in storage multi-pathing
22
Virtualization software should allow configuring each virtual machine with one or more virtual NICs. Each of those network interfaces can have its own IP address and even its own MAC address
23
Virtualization software must support NIC teaming for load sharing and redundancy.
24 Virtualization software shall allow creating virtual switches that connect virtual
Page 45 of 83 Confidential & Proprietary machines
25
Virtualization software shall support configurations of 802.1q VLANs which are compatible with standard VLAN implementations from other vendors
26
Virtualization software should allow dynamic adjustment of the teaming algorithm so that the load is always balanced across a team of physical network adapters
27
Virtualization software should provide network traffic-management controls to allow flexible partitioning of physical NIC bandwidth between different network-traffic types
28
Virtualization Software to support multitenancy with network virtualization. Eg:
should support hosting VM's with similar IP address on the same host without a network clash
30
Virtualization software shall continuously monitor utilization across virtual machines and should intelligently allocate available resources among virtual machines
31
Virtualization software shall allow usage of Remote devices which allow Installation of software in a virtual machine running on a server from the CD-ROM of a desktop
32
Virtualization software should provide support for Microsoft Cluster Services between virtual machines
33
Virtualization software should provides an integrated back-up solution in addition to support for a centralized backup proxy to offload backup from virtualization host.
35
Virtualization management software should have intergrated Physical Host and Virtual Machine performance monitoring
36
Virtualization management software console shall provide reports for
performance and utilization of Virtual Machines. It shall co-exist and integrate with leading systems management vendors
37
Virtualization management software console shall provide capability to monitor and analyze virtual machines, and server utilization and availability with detailed performance graphs.
38
Virtualization management software console shall allow to Move a powered off virtual machine from one physical server to another by dragging and dropping the virtual machine icon.
39
Virtualization management software console shall provide Interactive topology maps to visualize the relationships between physical servers, virtual machines, networks and storage.
40
Virtualization management software console shall maintain a record of significant configuration changes and the administrator who initiated them.
41
Virtualization management software console shall provide the Manageability of the complete inventory of virtual machines, and physical servers with greater visibility into object relationships.
42
Virtualization management software should support user role and permission assignment (RBAC)
43
Virtualization management software should include provision for automated and integrated online/offline VM patch management and automated host patch mgmt
Page 46 of 83 Confidential & Proprietary with no VM downtime
44
Virtualization software should have a built in hypervisor replication solution for Disaster recovery scenarios
Sr no Specification for Tape Library
1 Proposed Fibre Channel Tape Library Must be Rack Mountable Chassis 2
Tape Library Should support atleast 2 Ultrium Generation 5 drives with 48 cartridge slots
3
Tape Library Should be based on open technology ( Supporting heterogeneous hosts) with multi-hosting sharing,robotic mechanism for auto loading of Tape Cartridges
4
Backup Tape Library should support SAN based backup (LAN Free) as well as LAN based backups.
5 Tape Library should have removable magazines for easy off-site backup storage 6
3 years comprehensive warranty with 24x7 6-Hour Call to Repair (No 6 HR CTR) Support
7
The proposed Tape Library Must have GUI based remote management functionality for ease of hardware management.
Page 47 of 83 Confidential & Proprietary PART 6: BID FORM, PRICE SCHEDULES
AND OTHER FORMATS (BF)