NEA, e-GIF and MSDP Reportbnda.gov.bd/uploads/hardware_specification_standards.pdf · 2021. 2....

NEA, e-GIF and MSDP Report

Specifications Checklist

LICT-36-SBCC-CF-SIO: Establishing Enterprise Architecture and

Interoperability Framework

Bangladesh Computer Council

January 2016

Establishing National Enterprise Architecture and Interoperability Framework

January 2016

Page 2 | Specifications checklist

Document control

Project name Establishing Enterprise Architecture and Interoperability Framework

Client representatives Mr. Tarique Barkatullah

Contract package S10

Credit 5025#BD

Report No 2015-Delhi-0288

Start date 30 November 2014

End date 30 January 2016

Key project team members

Designation Name Function

EY

Team Leader Mr. Ashish Verma Team leader

Engagement Manager Mr. Ramesh Mishra Engagement Management

Engagement Partner Mr. Rahul Rishi Engagement Leadership

BC

C

Director (In-charge) Mr. Tarique Barkatullah Project Coordinator

Project Director, LICT Mr. Md. Rezaul Karim Project Management

Approval

Designation Name Approval Date

EY

Team Leader Mr. Ashish Verma

Engagement Manager Mr. Ramesh Mishra

Engagement Partner Mr. Rahul Rishi

BC

C

Director (In-charge) Mr. Tarique M Barkatullah

Project Director, LICT Mr. Md. Rezaul Karim


January 2016


Disclaimer

This report is intended solely for the information and use of the management of Bangladesh Computer Council and is not intended to be

and should not be used by anyone other than these specified parties. EY therefore assumes no responsibility to any user of the report

other than Bangladesh Computer Council. Any other persons who choose to rely on our report do so entirely at their own risk.

As it is practically not possible to study all aspects of a process in its entirety thoroughly during the limited time period of an assessment,

based on our methodology for conducting assessments, we conducted a review of the process and held discussions with the process

owners and other key people in the process during the planning stage of assessment which helped us in identifying specific areas where

architectural & process gaps may exist, opportunities for process and technology improvement. Our subsequent test work, study of issues

in detail and developing action plans are directed towards the issues identified. Consequently this report may not necessarily comment on

all the function / process related matters perceived as important by the management.

The issues identified and proposed action plans in this report are based on our discussions with the people engaged in the process, review

of relevant documents/records and our physical observation of the activities in the process. We made specific efforts to verify the

accuracy and authenticity of the information gathered only in those cases where it was felt necessary. The work carried out and the

analysis thereof is based on the interviews with the personnel and the records provided by them.

The identification of the issues in the report is mainly based on the review of records, sample verification of documents / transactions and

physical observation of the events. As the basis of sample selection is purely judgmental in view of the time available, the outcome of the

analysis may not be exhaustive and representing all possibilities, though we have taken reasonable care to cover the major eventualities.

Errors and Omissions:

When reading this document if you identify any errors or omissions please advise the author in writing, in 15 calendar days, giving a brief

description of the problem, its location within the document and your contact details.

Confidentiality:

This do u e t o tai s privileged a d o fide tial i for atio pertai i g to Establishing Enterprise Architecture and Interoperability

Framework . The a ess level for the do u e t is spe ified a ove. The addressee should honour this access rights by preventing

intentional or accidental access outside the access scope.


January 2016


Table of Contents

1. SERVERS ................................................................................................................................................... 8

1.1 BLADE SERVER – DATABASE ............................................................................................................................ 8 1.2 BLADE SERVER – APPLICATION ........................................................................................................................ 9 1.3 DATABASE SERVER – RACK MOUNT ................................................................................................................ 10 1.4 WEB AND DIRECTORY SERVER ....................................................................................................................... 11

1.5 BLADE CHASIS ........................................................................................................................................... 12

1.6 RACKS ..................................................................................................................................................... 14

2. STORAGE ................................................................................................................................................ 16

2.1 UNIFIED STORAGE SYSTEM ........................................................................................................................... 16

2.2 SAN STORAGE ........................................................................................................................................... 18

2.3 VIRTUAL TAPE LIBRARY ............................................................................................................................... 19

3. SWITCHES............................................................................................................................................... 21

3.1 CORE SWITCH ............................................................................................................................................ 21

3.2 MANAGED ACCESS SWITCH .......................................................................................................................... 23

3.3 SAN SWITCH ............................................................................................................................................ 27

3.4 AGGREGATION SWITCH ............................................................................................................................... 27

4. LOAD BALANCER .................................................................................................................................... 29

5. CLOUD MANAGEMENT SYSTEM ............................................................................................................. 30

6. VIRTUALIZATION .................................................................................................................................... 39

7. ENTERPRISE MANAGEMENT SYSTEM ..................................................................................................... 42

8. SECURITY OPERATIONS CENTER ............................................................................................................. 47

9. ANTI VIRUS ............................................................................................................................................ 52

10. ROUTER .............................................................................................................................................. 54

10.1 CORE ROUTER ........................................................................................................................................... 54

11. FIREWALL ........................................................................................................................................... 57

11.1 INTERNET ROUTER – FIREWALL ..................................................................................................................... 57 11.2 WEB APPLICATION FIREWALL ........................................................................................................................ 57

11.3 NEXT GENERATION FIREWALL ...................................................................................................................... 61

12. INTRUSION PREVENTION SYSTEM ...................................................................................................... 64

12.1 NETWORK INTRUSION PREVENTION SYSTEM ................................................................................................... 64

12.2 HOST BASED INTRUSION PREVENTION SYSTEM ................................................................................................ 67

13. SECURITY INCIDENT AND EVENT MANAGEMENT ................................................................................ 69

14. VULNERABILITY MANAGEMENT AND PENETRATION TESTING ............................................................ 75

15. ANTI-ADVANCED PERSISTENT THREAT ............................................................................................... 82

16. DATA LEAKAGE PREVENTION SYSTEM ................................................................................................ 84

17. NETWORK ACCESS CONTROL .............................................................................................................. 87

18. DATABASE ACTIVITY MONITORING SYSTEM ....................................................................................... 89


January 2016


19. CONFERENCE ROOM – LED DISPLAY ................................................................................................... 91

20. VIDEO WALL PROJECTION SYSTEM ..................................................................................................... 92

21. END-USER SYSTEMS............................................................................................................................ 96

21.1 DESKTOP .................................................................................................................................................. 96

21.2 LAPTOPS .................................................................................................................................................. 97

21.3 TABLETS ................................................................................................................................................... 98

21.4 UPS ........................................................................................................................................................ 99

21.5 MULTI-FUNCTION PRINTERS ....................................................................................................................... 100

21.6 COLOR PRINTERS ..................................................................................................................................... 101

21.7 BARCODE PRINTER ................................................................................................................................... 101

21.8 BARCODE SCANNER .................................................................................................................................. 102

21.9 WEB CAMERA ......................................................................................................................................... 102


January 2016


A reviatio

Abbreviation Description

a2i Access to Information

ADM Architecture Development Method

ARM Application Reference Model

BCC Bangladesh Computer Council

BRM Business Reference Model

BPEL Business Process Execution Language

BPMN Business Process Modelling Notation

CR Change Request

DC Data Centre

DR Disaster Recovery

DRM Data Reference Model

e-GIF Electronic Government Interoperability Framework

EA Enterprise Architecture

EY Ernst & Young LLP

FOSS Free and Open Source Software

GoB Government of Bangladesh

ICT Information and Communication Technology

ICTD Information and Communication Technology Division

ISO International Organization for Standardization

KPI Key Performance Indicators

LICT Leveraging Information and Communications Technologies

MoP&ME Ministry of Primary & Mass Education

MPT&IT Ministry of Post, Telecommunications & Information Technology

MSDP Mobile Service Delivery Platform

NEA National Enterprise Architecture

NeSS National e-Services System

NID National Identity

NP National Portal

PMO Project Management Office

PoC Proof of Concept

SID Statistics and Informatics Division

SLA Service Level Agreements

TA Technical Architecture

TOGAF ® The Open Group Architecture Framework

TRM Technical Reference Model

UML Unified Modelling Language


January 2016



January 2016


1. Servers

1.1 Blade server – database

Sr. No. Item Minimum Requirement Description

DBS.REQ.001 Processor Latest Generation x86-64 Bit Minimum XX GHz with XX Core and XXMB

Cache or more

DBS.REQ.002 Number of Processors Server should be X socket and populated with X physical processors

DBS.REQ.003 Memory XX GB DDR3 or higher memory Per Server

(To begin with minimum 128GB can be scaled upto 512GB or more

depending upon the application requirement )

DBS.REQ.004 Interface Port Blade server should support Ethernet and fiber channel connectivity

OR

Converged Network Adapters in lieu of the same.

The Converged Network Adapters should aggregate both the Ethernet

and FC connectivity on a single fabric

DBS.REQ.005 Network The server should provide a minimum of XXGb aggregate bandwidth

per blade server

(To begin with 36GB is fine can be scaled up to 128 GB or more depending

no of blades that you populate in a single blade chassis)

DBS.REQ.006 RAID RAID Controller should be able to do RAID 1, 0

DBS.REQ.007 Internal HDD Minimum 2 * XXX GB Internal SAS / SATA Hot Swap HDD (10k rpm or

higher)

(To start with 600GB is fine else can be scaled up to 1TB each or more

depending the availablity of capacity in Blade servers)

DBS.REQ.008 Warranty Critical Components like CPU, Memory, SSD / HDD should be covered

DBS.REQ.009 Power Supply Redundancy The supporting chassis should have redundant power supply

Configured in N+N Mode.

DBS.REQ.010 Fans Redundant Hot Swappable Fans

DBS.REQ.011 Form Factor Blade/ Rack

(Servers for Database can either be Blade or Rack form factor)

DBS.REQ.012 Application Support Any Database application support like MySQL/SQL Server/Oracle/DB

2/Postgre Sql etc.

DBS.REQ.013 Operating System Support Support for proposed operating system

(This co-relates with the application and OS that the solution is built on)


January 2016


1.2 Blade server – application

Sr.No. Item Minimum Requirement Description

AS.REQ.001 Processor Latest Generation x86-64 Bit with Minimum XX Ghz Clock Speed or above

with minimum XX of processors, each processor having X cores and XXMB

Cache or more

AS.REQ.002 Memory Minimum XX GB DDR3 or higher RAM of highest frequency as applicable

in the quoted model to be offered per processor. Memory should support

ECC and memory mirroring upgradable up to XXGB

(To begin with minimum 128GB can be scaled upto 512GB or more depending

upon the application requirement )

AS.REQ.003 PCI-Express Slots Server Should Have Minimum 2 * PCI Express Slots or more

AS.REQ.004 Network Interface Ports Minimum 2 * 10 Gbps Ethernet Ports Per Server or more

AS.REQ.005 FC-HBA Ports Minimum 2 * 8Gb/s FC HBA Ports / Server or more

AS.REQ.006 Internal RAID Internal RAID Controller with minimum 256MB battery Backed Write

Cache or better

AS.REQ.007 Internal HDD Minimum 2* XXXGB Internal SAS / SATA Hot Plug HDD

(To start with 600GB is fine else can be scaled up to 1TB each or more

depending the availablity of capacity of hard drives for blade servers)

AS.REQ.009 Power Redundant Hot-Swappable Power Supplies Configured in N+N Mode

AS.REQ.010 Fans Redundant Hot Swappable Fans

AS.REQ.011 Pre-Failure Warranty Critical Components like CPU, Memory, HDD and PCI Slots should be

covered under Pre-Failure Warranty

AS.REQ.012 OS & Virtualization

Infrastructure Support

MS Windows, UNIX, Linux, Solaris, VMWare VSphere & Microsoft HyperV

etc.

AS.REQ.013 I/O & Power Supply

Redundancy

The supporting chassis should have redundant power supply. The server

should have redundant I/O

AS.REQ.014 From Factor Half Blade

(With the increase in CPUs the form factor changes half blade supports 2 CPU

where as full blade supports 4 physical CPUs. At any given point in time blade

Chassis support 8 full blade or 16 half blade servers )


January 2016


1.3 Database server – rack mount

Sr no Minimum Requirement Specifications

1 Servers offered should be highest end enterprise class and should be with the

latest generation processors at the time of supply. However the proposed servers

with 64 bit processor of RISC/EPIC cores processor should not be less than 3.30 Ghz

(RISC), 2.53 GHz for "Ultra SPARC64-VII" or 1.6 GHz for EPIC Processor. It should be

supplied with minimum 24 cores which can be upgraded to 128 cores in the same

server.

The server proposed should be compatible with the Database Solution proposed by

the Bidder for the period of contract.

2 Should support 64bit enterprise class Linux / UNIX, with HA & cluster functionalities.

3 Minimum 24 MB cache (L3) per processor or higher

4 Minimum of 8 GB RAM DDR-3 1066 per core.

5 Min 5 x 300 GB(or higher) latest generation SAS (15 K rpm) for each partition within

the server

6 Minimum 2 Ethernet Ports of 10 Gigabit speed each for each partition

7 Fiber Channel Adapters Minimum 4 x 8Gbps for each partition.

8 1 DVD RW Drive

9 Dual Redundant hot pluggable Power Supply and Fan

10 Logical or Physical Partitioning should be supported

11 Server must have capability for minimum 4 Partitions to run Independent

Enterprise OS Server must have capability for minimum 4 Partitions to run

Independent Enterprise OS

12 Capable of dynamic movement of resources (CPU/ memory/ adapters) across

partitions

13 Should be provided with a GUI / browser based management console to take care

of the partition management & configuration

14 Necessary software and scripts for automatic cluster failover to be supplied for

cluster based solutions to maintain high availability & Fault tolerance in the

proposed solution. It should have seamless failover without manual intervention

15 19 rack mountable with rack mounting accessories

16 Must ensure no single point of failure for production environment and necessary

components must be added to the solution accordingly to ensure that.

17 The proposed server should have ability to use spare processors which would

dynamically kick in when any active processors fail.


January 2016


18 Should support a shared architecture wherein CPU, Memory and I/O can be shared

between the different partitions, be it virtual partitions or logical partitions.

19 If partitioning is used then servers should have similar number of partitions and

every partition on one server should be clustered with respective partition (with

equal amount of Processor Cores, Memory & I/O per partition) on the other server.

20 The proposed partitioning mechanism should have flexibility of assigning resources

like CPU, and Memory to a unit level granularity

to each individual partition. The server should have the configured capability to

assign dedicated resources to partitions.

21 At any given point, CPU utilization should not exceed 65 percentage (during peak &

nonpeak hours)

22 Critical component like CPU, Memory, HDD in server should be hot pluggable to

ensure availability even during hardware failure

23 The database should have the capability to be deployed in an active-active clustered

environment. The database should be available even when one of the servers /

instances fails. The users should be able to work without interruptions.

24 The database software should be available in UNIX, Linux and Windows

environments with identical functionalities and user interfaces

25 Should have the capability to open the standby database for reporting and backup

purpose.

26 Capability to offload all backup activities from the primary database to the physical

standby database.

27 MS Windows, RHEL, SLES, OEL, Oracle Solaris, VMWare VSphere & Microsoft HyperV

28 Critical Components like CPU, Memory, HDD and PCI Slots should be covered under

Pre-Failure Warranty

29 Support granularity in database security, such as restricted row level access etc

30 The database has to be in the Gardner quadrant

31 The system should not be an end of life / end of service product.

32 Updates and upgrades for minimum three years should be factored

1.4 Web and directory server


1 19" rack server with rack mounting accessories


January 2016


2 Minimum Intel / AMD series

Processor 6 Core, 15MB Cache, 2.0 GHz.

Populated with 1 Nos. of CPU, scalable to 2.

3 Intel® C600 Chipset / Equivalent or higher

4 Minimum 24 GB RAM DDR-3 1066 scalable to 512 GB.

5 Minimum 3 X 300 GB SAS hard drive

6 RAID Controller with minimum 512 MB Cache & should support RAID levels

minimum 0, 1, 10, 5 & 6

7 Minimum 2 x 10G Ethernet ports with dual controllers & minimum 2 x 8G FC ports with dual

controllers

8 Minimum four PCI-Express slots

9 DVD ± R/W Drive

10 Hot Swappable Redundant power supply & fan

11 Operating System: 64 bit Windows/Linux OEM Server Management Suite, Integrated

remote management controller with dedicated 10/100 Mbps port, should

support graphical console and remote media control

12 The quoted system must conform to FCC Class A



1.5 Blade chasis


1 Single blade Chassis/enclosure should accommodate minimum 14 blade servers

2 Support support heterogeneous environment: AMD, Intel CPU blades, RISC/EPIC

blades must be in same chassis with scope to run Windows Server, Red Hat Linux,

Suse Linux / 64 Bit UNIX or other standard open source OS.

3 Chassis should have a highly reliable mid plane for providing connectivity of the

shared resources to the compute nodes in a highly reliable manner

4 Each enclosure should be configured with redundant Ethernet modules with 10Gbps

downlink ports and 4 no. 10 Gbps and 2 no. 1 Gbps uplink ports per module, up-

linkable to the data centre switch. Shall be capable of supporting up to 4 physical

slices per 10Gbps server communication port, within the server Blade. Each of the

tailoring slices shall be capable of tailoring the network with their own dedicated,

customized bandwidth per 10Gbps downlink connection, with customizable speeds

from 100Mbps to 10Gbps


January 2016


5 The Blade enclosure should be configured with redundant fiber channel module

which should support downlink ports to all the blades and 6 No of 8 Gbps uplink

ports to consolidate the FC uplinks to upstream SAN switches. This module should

also provide virtual WWN to the servers in order to assign the servers rapidly.

6 Hot swap and redundant cooling unit and all fans should be fully populated.

7 The blade chassis should have at least 8 I/O Modules

8 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

9 Power Management Features like ;

• To cap the power of individual server or a group.

• Intelligently assign power to the appropriate server in the pool basedon policy

settings.

• To generate comprehensive power reports.

• To show the actual power usage and thermal measurements data of servers.

10 The blade chassis should be configured with cables, connectors and accessories

required to connect the Power distribution units to the power supplies

11 Should support Hot Pluggable & fully Redundant Management Modules

12 The blade chassis should be configured with Hot swap IP based KVM Switch for

Management or KVM Management should be integrated in Remote Management

Controller

13 Should support combination housing of Ethernet, FC, IB interconnect fabrics offering

Hot Pluggable & Redundancy as feature

14 Warranty 5 years 24x7 support directly from the OEM.

15 Must have the ability to map the remote media to the server. Also must have the

ability to transfer files from the user’s desktop/laptop folders to the remote server

with only the network connectivity. Must have the capability of capturing and

deploying OS images.

16 Must have the ability to automatically trigger events and alerts based on performance

issues or thresholds set.




January 2016


1.6 Racks

Sr.

No.

Parameter Minimum specification

Floor Mounted Rack- Size 42U (For Rack mounted Servers & Telecom equipment)

1 Acceptable makes

2 Product Certification Agency to specify the name of the certification and the agency certifying it.

Agency should attach a copy of the certificate.

2 Product Certification ISO 9001 or CE Certified

3 Width x Depth 800 mm(W) x 1200 mm(D)

3 Side panels Perforated & Open able with slam latches

4 Cable entry provision From Top of rack with knock-off, pre-punched marked openings

4 Cable management Vertical Cable Managers to be provided with suitable accessories on each

side of the rack with covers to improve aesthetics and conceal wiring within

the rack

5 Doors Front & Rear Metallic Perforated Doors with Air Filters to block entry of fine

dust particles.

5 Locking arrangement Spring loaded locks for front and rear door with uniform pattern of key

levers with 3 keys to be provided. It should also have provisions for

biometric or proximity card access control mechanism

6 Equipment Mounting Frame Adjustable frame (preset to 19 inch) with notches at regular intervals for

mounting of equipment such as High end Servers, Telecom equipment, etc

as per Industry standards to be provided

6 Horizontal shelves 4 Nos. of Horizontal perforated shelves for equipment placement

7 Construction of Rack Powder coated steel cabinet, Black coloured

7 Ventilation Ventilation Louvers or uniform perforations to be provided on side panel

and rear door

8 Equipment cooling Equipment cooling to be provided with Brushless Fans (4 Nos.) housed in

Fan tray


January 2016


8 AC Power Outlets Two strips each with 16 Nos. of 5A/ 15 A, 230 VAC Power outlets (ISI

approved) with Miniature Circuit Breaker, inbuilt Surge suppressor and

power line filter for conditioned power output. Strips to be fitted at rear on

either side with provision for tension reliever. Dual Power supply and

modular power strips should be provided

9 Earthing Earthing continuity kit to be provided with braided Earth strip.

9 Temperature Control Two sensors per rack for temperature and humidity control

10 Floor Mounting kit Floor mounting accessories (such as Adjustable screw legs, Sturdy Castor

wheels, nuts, bolts, washers, clip-on nuts for equipment mounting, etc) and

assembly hardware to be provided.

10 Other accessories All rack accessories required for equipment mounting to be supplied.

Compact Fluorescent Lamp fitted in the Rack to provide adequate light in

the rack. Filters to be provided to block entry of fine dust particles. As part

of access control the access to racks should also be controlled by a

proximity card system wherever required along with the standard lock and

key mechanism


January 2016


2. Storage

2.1 Unified storage system

Sr no Specifications

1 The Storage system should have unified capability i.e. should support block and file

access with host connectivity for FC, iSCSI, CIFS and NFS.

2 The NAS/Gateway/File serving node should be purpose built appliance and should

not be windows based or running on General purpose simple OS or a simple SMB /

NFS configured file server.

3 The system must be dedicated appliance with specifically optimized OS to provide

both SAN and NAS functionalities. The architecture should allow modular upgrades

of hardware and software for investment protection. The system should be suitably

configured for achieving enhanced performance and throughput.

4 The storage system must have dual controllers & file system heads with automatic

failover capabilities in case of one controller or head failure. The storage should be

installed in the OEM Rack to be supplied.

5 High available internal configuration with redundancy features and no single point

of failure. The system should have memory / cache of 16 GB or more across the

controllers for block level

6 The storage system must have auto-negotiating 2 / 4 / 8 Gbps FC, 1 GbE and 10 GbE

interfaces and licenses for NFS, CIFS, FC and iSCSI protocols. The Storage System

should support Raid Levels 0,5,6,10 or equivalent data protections. Multiple raid

configurations to be configured in the proposed solution.

7 The proposed System must be populated with the following ports.

For file-based (NAS) functionality, the solution should be configured with minimum

of 4 (or more) x10GigE (Optical 10G Base SR).

For Block-based (SAN) functionality, the solution should be configured with 4 (or

more) X 8Gbps FC and 2 (or more) X 10G iSCSI.

8 The Storage System should have support for SSD, SAS Drives, NL SAS Drives. The

storage system should have support for 6Gbps SAS 2.0 drives. There should not be

any legacy 3Gbps technologies used in the entire storage architecture. Proposed

system must be able to support all on-line data storage tiers in order to maximize

both system performance and capacity scalability. Proposed system should support

flash, 10K RPM SAS2.0, 15K RPM SAS 2.0as well as 7.2K RPM drives.

9 The storage system is to be supplied with at least 100 TB of usable disk space

(binary) scalable upto 150 TB after RAID6 (in 6+2 configuration) and other over

heads like formatting, raid configuration, one hot spare disk for every 25 disks and

configured with SATA / NL SAS drives for file level access using 4 Tb disks and

necessary disk enclosures.


January 2016


10 The storage system is to be supplied with 800 GB SSD storage with not less than 4

Drives. The storage system is also to be supplied with 60 TB of usable disk space

(binary) after RAID 6 (in 6+2) and other over heads like formatting, raid

configuration, one hot spare disk for every 15 disks and configured with 300GB and

15K RPM SAS 2.0 drives and necessary disk enclosures. All the drives must be in

addition to the drives used to hold the system’s OS

11 The Storage System should have the capability to support Non-Disruptive Data

migration across Volumes. The Storage System Should be configured with host

multi-pathing drivers.

12 The storage array must support at least 1000 disk drives. No replacement or

upgrade of controllers should be required for supporting the 200 disks. It must be a

single or tightly clustered singly managed system rather than aggregate of multiple

separate smaller boxes.

13 The storage must have the ability to create logical volumes without physical capacity

being available (Thin Provisioned) or in other words system should allow

overprovisioning of the capacity. The feature should be made available for the

maximum supported capacity.

14 For file access It must be possible to set quotas at a user, group or file set level and

should have Microsoft active directory and LDAP integration. Support for

heterogeneous client Operating System platforms (on both block and file level) like

LINUX , Microsoft Windows, HP-UX, SUN Solaris, IBM-AIX, ESXi, etc

15 The Storage System must have the Capability to support creation of instantaneous

or Point In Time Snapshot copies of volumes. The snapshot feature should support

incremental and thin provisioned volumes. The snapshot feature needs to have at

least 90 snapshot copies

16 The solution should support virtual infrastructure (like VMware / Hyper-V etc).

Should have capabilities for booting VMs from the SAN. Should be supplied with

virtualization aware APIs for provisioning and managing the storage array from the

virtual infrastructure.

17 The solution must support movement of data between different disk tiers based on

predefined policies (ie storage tiring). Licensing should be provided. The Storage

System shall support Synchronous & Asynchronous Replication for DR Strategy.

18 Easy to use GUI based and web enabled administration interface for configuration,

managing and administration of file & block storage and associated functionalities

including deployment, automation, provisioning, and protection and monitoring

management. Solution Should offer real time performance monitoring tools giving

information on CPU utilization, volume throughput, I/O rate and latency

19 The Storage box should be connected to the servers through SAN switches in High

Available Configuration. (Specifications of the SAN switch enclosed). All necessary

cables for connecting the storage with switches are to be supplied.


January 2016


20 Solution Must be provided with full NDMP functionality and license or equivalent.

Solution Must be fully compatible with all standard backup software’s. There must

be redundant 1 Gbps LAN ports / equivalent mechanism for management. The

storage shall support all standard SAN & NAS security features.



2.2 San storage


SAN.REQ.001 Net Storage Capacity Duration XX Days

SAN.REQ.002 Throughput 8 Gbps or higher (To begin with 8Gbps can be

increased uptill 32Gbps or more)

SAN.REQ.003 Form Factor Rack mountable

SAN.REQ.004 Disk Speed 10 Krpm

SAN.REQ.005 Minimum Capacity per disk 900GB or higher

SAN.REQ.006 Hot swap disks Yes

SAN.REQ.007 On-line capacity Expansion Yes

SAN.REQ.008 H/W based RAID controller Yes

SAN.REQ.009 Hot swappable controller Yes

SAN.REQ.010 RAID protection against double failure in RAID

Group

Yes

SAN.REQ.011 Data and control cache swappable Yes

SAN.REQ.012 Non diruptive on-line firmware upgrade Yes

SAN.REQ.013 Hot swappable power supply Yes

SAN.REQ.014 (N+1) redundant power supply Yes

SAN.REQ.015 Hot swappable cooling fans Yes

SAN.REQ.016 (N+1) hot swappable cooling fans Yes

SAN.REQ.017 FC protocol Yes

SAN.REQ.018 Fabric Management Software Shall be provided

SAN.REQ.019 Minimum connection from a server to a SAN

Switch

2

SAN.REQ.020 RAID level that will be implemented RAID 6


January 2016


SAN.REQ.021 Will the proposed product/service reach End-of-

support during the currency of contract?

Shouldn't

SAN.REQ.022 The system should not be an end of life / end of

service product.

Yes

2.3 Virtual Tape Library


1 Offered Virtual tape Library shall be of modular design to allow configuration,

addition of capacity to increase performance. Offered virtual tape Library

shall be scalable to at-least four numbers of Front-end heads / Nodes. Tape library

shall be configured with minimum 50 number of data cartridges,1 bar code label pack,

cleaning cartridge etc.

2 Offered Virtual Disk library shall be offered with minimum of 60 TB of usable space

scalable to more than 500 TB of usable space in Raid 5/6 if required by adding

additional heads/nodes.

3 Each front-end head / Node of Virtual Tape Library shall have the ability to configure

atleast 16 tape Libraries, at least 100 or more tape drives & at-least 2000 Cartridge

slots. The Virtual Tape Library should be scalable to minimum of 64 Tape Libraries,

minimum 400 Tape drives and minimum 8000 cartridge slots.

4 Offered Virtual Tape library Solution shall have capability to deliver selective restore

from disk Library itself.

5 The Virtual Tape Library should be compatible with the proposed Storage

Solution infrastructure including the SAN Storage, SAN Switch etc.

6 The Virtual Tape Library should be compatible with all the leading backup

software products.

7 The Virtual Tape Library should have the ability to flexibly emulate the most

commonly used tape drive/ tape formats like LTO-Gen3, LTO-Gen4, LTO-Gen5 etc.

8 Each Offered Virtual tape Library head / node shall have minimum of 2 x 4Gbps fiber

Channel connections to SAN switches.

9 Fault tolerance in the offered Virtual tape library shall be achieved by redundancy

technology like RAID 5/6.

10 Offered Virtual Tape Library shall offer inbuilt Hardware Data compression, without

performance degradation,

11 Offered Virtual tape library shall support throughput of minimum 1TB/hr and shall be

scalable to 10TB per hour by adding more capacity and front-end heads / Nodes.


January 2016





January 2016


3. Switches

3.1 Core switch


CSW.REQ.001 Hardware features Proposed network device must be 19’’ rack mountable

CSW.REQ.002 Hardware features Network Infrastructure equipment must use 240V AC power.

CSW.REQ.003 Hardware features Must have Redundancy Power Supply Units (PSUs).

CSW.REQ.004 Hardware features Must have redundant of other components such as fans within network

equipment.

CSW.REQ.005 Hardware features Must have redundant CPU/processor cards.

CSW.REQ.006 Hardware features Support Redundancy for CPU cards in switching over, to allow the standby

CPU to immediately take over

CSW.REQ.007 Hardware features All components (including elements such as I/O cards, CPUs, power

supplies and fans) must be hot swappable with zero disruption to traffic

forwarding (Unicast or multicast).

CSW.REQ.008 Hardware features Must have modular slots and dedicated for I/O modules as per

requirement

CSW.REQ.009 Hardware features For high availability & performance must have approximate supervisory

engine

CSW.REQ.010 Hardware features Chassis Switching Fabric Must be capable of delivering required bandwidth

per I/O slot.

CSW.REQ.011 Scalability Must support port channelling or equivalent across multiple chassis.

CSW.REQ.012 Scalability Physical standards for Network Device

Should support Ethernet (IEEE 802.3, 10BASE-T), Fast Ethernet (IEEE 802.3u,

100BASE-TX), Gigabit Ethernet (IEEE 802.3z, 802.3ab), Ten Gigabit Ethernet

(IEEE 802.3ae)

CSW.REQ.013 Scalability Software based standards for Network Device

Must support IEEE 802.1d - Spanning-Tree Protocol,

IEEE 802.1w - Rapid Spanning Tree,

IEEE 802.1s - Multiple Spanning Tree Protocol,

IEEE 802.1q - VLAN encapsulation,

IEEE 802.3ad - Link Aggregation Control Protocol (LACP),

IEEE 802.1ab - Link Layer Discovery Protocol (LLDP),

IEEE 802.3x Flow Control

CSW.REQ.014 Scalability Must support auto-sensing and auto-negotiation like Link Speed/Duplex

CSW.REQ.015 Scalability Should support Bidirectional Forwarding Detection (BFD) for OSPF, IS-IS

and BGP

CSW.REQ.016 Scalability Routing protocol support; Static IP routing, OSPF, BGPv4, MP-BGP, BGP

Route


January 2016


CSW.REQ.017 Scalability The network infrastructure must allow for multiple equal metric/cost

routes to be utilized at the same time

CSW.REQ.018 Scalability Hardware must support FCOE ports with all FCOE standards support like

FCF & DCB

CSW.REQ.019 Scalability Must have the ability to complete hitless software upgrades with zero

interruption to services or data forwarding

CSW.REQ.020 Scalability Should support 802.1 Q-in-Q

CSW.REQ.021 Scalability IEEE 802.3ad Link Aggregation or equivalent capabilities

CSW.REQ.022 Scalability IPv6 functionality and capable. If IPv6 compliance/support is not available,

please identify if compliance is defined in device roadmap along with a

timeframe

CSW.REQ.023 Scalability Must support Static IPv6 routing, OSPFv3 and Should support both IPv4

and IPv6 routing concurrently. There should be the ability to tunnel IPv6

within IPv4.

CSW.REQ.024 Scalability Supported IPv6 features should include: DHCPv6, ICMPv6, IPv6 QoS, IPv6

Multicast support, IPv6 PIMv2 Sparse Mode, IPv6 PIMv2 Source-Specific

Multicast, Multicast VPN

CSW.REQ.025 Scalability Device must support multicast in hardware

CSW.REQ.026 Scalability The switch mush support IEEE 802.1 QBR/ 802.1 BR standard to support

scalability and extension of switching fabric to additional ports if required

outside chassis.

CSW.REQ.027 Scalability The system must allow extending Layer 2 applications across distributed

data centers

CSW.REQ.028 Security features Must support multiple privilege levels for remote access (e.g. console or

telnet access)

CSW.REQ.029 Security features Must support Remote Authentication Dial-In User Service (RADIUS) and/or

Terminal Access Controller Access Control System Plus (TACACS+)

CSW.REQ.030 QoS features Must support IEEE 802.1p class-of-service (CoS) prioritization

CSW.REQ.031 QoS features Must support rate limiting (to configurable levels) based on

source/destination IP/MAC, L4 TCP/UDP

CSW.REQ.032 QoS features Must have the ability to complete traffic shaping to configurable levels

based on source/destination IP/MAC and Layer 4 (TCP/UDP) protocols

CSW.REQ.033 QoS features There should not be any impact to performance or data forwarding when

QoS features

CSW.REQ.034 QoS features Must support a "Priority" queuing mechanism to guarantee delivery of

highest-priority (broadcast critical/delay-sensitive traffic) packets ahead of

all other traffic

CSW.REQ.035 QoS features Must support ability to trust the QoS markings received on an ingress port


January 2016


CSW.REQ.036 Virtualisation The switch must support data center virtualization, giving department the

ability to virtualize a physical switch into multiple logical devices. With each

logical switch having its own processes, configuration, and administration

CSW.REQ.037 Management

features

Must support SNMP V1,V2, V3 and be MIB-II compliant


features

Must support SNMP traps (alarms/alerts) for a minimum of four

destinations


features

Network switch should support Remote Monitoring on every port covering

the following four groups (Statistics, Alarm, Event, History).


features

Must be able to integrate with all standard Network Management Systems,

including HP Open View Suite, Netcool and Infovista


features

Should support flow based traffic analysis features and the ability to

export of network IP flow information.


features

Must support Network Timing Protocol (NTPv3) and should support the

following:

• Configuration of more than one NTP server

• Speciation of a local time zone

• NTP authentication

CSW.REQ.043 Port Should support upto 48-Port 10G SFP+ Ports loaded with MM modules and

48 nos. 10/100/1000 Mbps ports from Day 1.

(This can be modified as per the solution requirements)

CSW.REQ.044 Complaince The switch should be IPV6 complaint.

3.2 Managed access switch


MAS.REQ.001 Switch Architecture and

Performance

Switch should have 24 Nos. 10/100/1000Base-TX auto-sensing plus

4x1G SFP uplinks. (The one highlighted in blue can be updated as

per the port requirements in line with the solution architecture)


Performance

Should support stacking using dedicated stacking ports with up to

80Gbps throughput

(The one highlighted in blue can be updated as per the port

requirements in line with the solution architecture)


Performance

Switch should support link aggregation across multiple switches in a

stack.


Performance

Should support stacking of minimum of eight switches


Performance

Switch should have non-blocking wire-speed architecture.


Performance

Switch should support IPv4 and IPv6 from day One


January 2016



Performance

Switch should have non-blocking switching fabric of minimum 56

Gbps or more (The one highlighted in blue can be updated as per

the port requirements in line with the solution architecture)


Performance

Switch should have Forwarding rate of minimum 41 Mpps.

MAS.REQ.009 Layer 2 Features IEEE 802.1Q VLAN tagging.

MAS.REQ.010 Layer 2 Features 802. 1Q VLAN on all ports with support for minimum 255 active

VLANs and 4k VLAN ids

MAS.REQ.011 Layer 2 Features Support for minimum 8k MAC addresses

MAS.REQ.012 Layer 2 Features Spanning Tree Protocol as per IEEE 802.1d

MAS.REQ.013 Layer 2 Features Multiple Spanning-Tree Protocol as per IEEE 802.1s

MAS.REQ.014 Layer 2 Features Rapid Spanning-Tree Protocol as per IEEE 802.1w

MAS.REQ.015 Layer 2 Features Self-learning of unicast & multicast MAC addresses and associated

VLANs

MAS.REQ.016 Layer 2 Features Jumbo frames up to 9000 bytes

MAS.REQ.017 Layer 2 Features Link Aggregation Control Protocol (LACP) as per IEEE 802.3ad.

MAS.REQ.018 Layer 2 Features Port mirroring functionality for measurements using a network

analyzer.

MAS.REQ.019 Layer 2 Features Switch should support IGMP v1/v2/v3 as well as IGMP v1/v2/v3

snooping.

MAS.REQ.020 Quality of Service (QoS)

Features

Switch should support classification and scheduling as per IEEE

802.1P on all ports.


Features

Switch should support DiffServ as per RFC 2474/RFC 2475.


Features

Switch should support four queues per port.


Features

Switch should support QoS configuration on per switch port basis.


Features

Switch should support classification and marking based on IP Type

of Service (TOS) and DSCP.


Features

Switch should provide traffic shaping and rate limiting features (for

egress as well as ingress traffic) for specified Host, network,

Applications etc.


Features

Strict priority queuing guarantees that the highest-priority packets

are serviced ahead of all other traffic.

MAS.REQ.027 Security Features Switch should support MAC address based filters / access control

lists (ACLs) on all switch ports.

MAS.REQ.028 Security Features Switch should support Port as well as VLAN based Filters / ACLs.


January 2016


MAS.REQ.029 Security Features Switch should support RADIUS and TACACS+ for access restriction

and authentication.

MAS.REQ.030 Security Features Secure Shell (SSH) Protocol, HTTP and DoS protection

MAS.REQ.031 Security Features IP Route Filtering, ARP spoofing, DHCP snooping etc.

MAS.REQ.032 Security Features Should support DHCP snooping, DHCP Option 82, Dynamic ARP

Inspection (DAI)

MAS.REQ.033 Security Features Should support a mechanism to shut down Spanning Tree Protocol

Port Fast-enabled interfaces when BPDUs are received to avoid

accidental topology loops.

MAS.REQ.034 Security Features Should support a mechanism to prevent edge devices not in the

network administrator's control from becoming Spanning Tree

Protocol root nodes.

MAS.REQ.035 Security Features Switch should support static ARP, Proxy ARP, UDP forwarding and IP

source guard.

MAS.REQ.036 Security Features Switch should Support Ipv6 First hop Security with the following

functions: IPv6 snooping, IPv6 FHS binding, neighbor discovery

protocol (NDP) address gleaning, IPv6 data address gleaning, IPv6

dynamic host configuration protocol (DHCP) address gleaning, IPv6

device tracking, neighbor discovery (ND) Inspection, IPv6 DHCP

guard, IPv6 router advertisement (RA) guard

MAS.REQ.037 Management, Easy-to-Use

Deployment and Control

Features

Switch should have a console port with RS-232 Interface for

configuration and diagnostic purposes.



Features

Switch should be SNMP manageable with support for SNMP Version

1, 2 and 3.



Features

Switch should support all the standard MIBs (MIB-I & II).



Features

Switch should support TELNET and SSH Version-2 for Command Line

Management.



Features

Switch should support 4 groups of embedded RMON (history,

statistics, alarm and events).



Features

Switch should support system and event logging functions as well as

forwarding of these logs to multiple syslog servers.



Features

Switch should support on-line software reconfiguration to

implement changes without rebooting. Any changes in the

configuration of switches related to Layer-2 & 3 functions, VLAN, STP,

Security, QoS should not require rebooting of the switch.


January 2016




Features

Support for Automatic Quality of Service for easy configuration of

QoS features for critical applications.



Features

Support for Unidirectional Link Detection Protocol (UDLD) to detect

unidirectional links caused by incorrect fiber-optic wiring or port

faults and disable on fiber-optic interfaces



Features

Switch should have comprehensive debugging features required for

software & hardware fault diagnosis.



Features

Layer 2/Layer 3 trace route eases troubleshooting or equivalent

feature supporting IEEE 802.1 AG, IEEE 802.3 AH identifying the

physical path that a packet takes from source to destination.



Features

Should support DHCP Server feature to enable a convenient

deployment option for the assignment of IP addresses in networks

that do



Features

not have without a dedicated DHCP server.



Features

Switch should support Multiple privilege levels to provide different

levels of access.



Features

Switch should support NTP (Network Time Protocol)



Features

Switch should support FTP/ TFTP

MAS.REQ.053 Standards RoHS Compliant.

MAS.REQ.054 Standards IEEE 802.1x support.

MAS.REQ.055 Standards IEEE 802.3x full duplex on 10BASE-T and 100BASE-TX ports.

MAS.REQ.056 Standards IEEE 802.1D Spanning-Tree Protocol.

MAS.REQ.057 Standards IEEE 802.1p class-of-service (CoS) prioritization.

MAS.REQ.058 Standards IEEE 802.1Q VLAN.

MAS.REQ.059 Standards IEEE 802.3u 10 BaseT / 100 Base Tx /1000 Base Tx.

MAS.REQ.060 Compliance The switch should be IPV6 complaint


January 2016


3.3 SAN switch


SAN.REQ.001 Performance Minimum Dual SAN switches shall be configured where each SAN switch shall

be configured with minimum of 48 Ports scalable to 192 ports. Switch should

support 240 no of 2/4/8 -Gbps FC ports. Switch should also support 16Gbps

ports, 10G ports as well. (The one highlighted in blue can be updated as per the

port requirements in line with the solution architecture)

SAN.REQ.002 Standard The switch to support different port types such as FL_Port, F_Port, M_Port

(Mirror Port), arid E_Port; self-discovery based on switch type (U_Port); optional

port type control in Access Gateway mode: F_Port and NPIV-enabled N_Port

SAN.REQ.003 Standard The switch should be rack mountable with minimum 2 slots for CPU & 3 slots

for line cards. Switch should be loaded with dual CPU from day one.

SAN.REQ.004 Standard Switch should support advanced features like zoning, hardware based VSAN &

Inter-VSAN routing

SAN.REQ.005 Performance Should protect existing device investments with auto-sensing 1, 2, 4, and 8

Gbit/sec capabilities.

SAN.REQ.006 Performance The switch shall provide Aggregate bandwidth of 8000 Gbit/sec Performance of

the switch should not degrade incase one CPU or Fabric fails.

SAN.REQ.007 General Switch shall have support for web based management and should also support

CLI.

SAN.REQ.008 General The switch should have facility for firmware download, support save, and

configuration upload/download.

SAN.REQ.009 Reliability Offered SAN switches shall be highly efficient in power consumption. Bidder

shall ensure that each offered SAN switch shall provide dual redundant power.

3.4 Aggregation switch


AS.REQ.001 Architecture Switch fabric capacity - 800 Gbps

(The one highlighted in blue can be modified as per the requirements in line with the

solution architecture)

AS.REQ.002 Architecture Switch forwarding rates – 600 Mpps for IPv4 and IPv6

(The one highlighted in blue can be modified as per the requirements in line with the

solution architecture)

AS.REQ.003 Architecture Should have at least 48 unified fixed ports configurable as 1 and 10 Gigabit

Ethernet, FCoE or 8/4/2/1-Gbps native Fibre Channel. Out of 48, at least 40 port

should be configured from day one with 10G SR optics.

AS.REQ.004 Architecture Non-blocking switch architecture

AS.REQ.005 Connectivity 802.3ad based standard port/link aggregation, Jumbo frames, storm control


January 2016


AS.REQ.006 Switching

features

Support at least 2500 VLAN and 24,000 MAC Address

AS.REQ.007 Switching

features

Datacenter bridging exchange, IEEE 802.1Qbb

AS.REQ.008 Security 802.1X Network Security and Radius/TACACS AAA authentication

AS.REQ.009 Security MAC Address filtering based on source and destination address

AS.REQ.010 Security Support for various ACLs like port based, vlan based and L2- L4 ACL's

AS.REQ.011 Network

Protocols

Layer3 routing protocols like Static, Inter VLAN routing, OSPF from day 1 for the

solution.

AS.REQ.012 Quality Of Service Minimum 8 number of hardware queues per port

AS.REQ.013 Quality Of Service DSCP, 802.1p

AS.REQ.014 Multicast IGMP v1,v2,v3, IGMP snooping, PIM SM/DM, MLD

AS.REQ.015 Management SNMP v1, v2, v3, RMON/RMON-II enabled, SSH,telnet,GUI, Web management and

should have out of Band Management port

AS.REQ.016 Management Switch should support port mirroring feature for monitoring network traffic of a

particular port/VLAN.

AS.REQ.017 Management Switch should support Link Aggregation on two different switches

AS.REQ.018 Management Built-in real-time performance monitoring capabilities

AS.REQ.019 Management Power Supply: Switch should have internal Hot Swappable redundant Power

supply

AS.REQ.020 Management Cooling Fans: Should have redundant cooling FANS

AS.REQ.021 Management Support consolidating IP, Storage, FC and traditional Ethernet protocols into

single media

AS.REQ.022 Management The switch should also deliver Fibre Channel over Ethernet (FCoE), which allows

storage traffic to be reliably carried over an Ethernet infrastructure.

AS.REQ.023 Compliance The switch should be IPV6 complaint


January 2016


4. Load balancer


LB.REQ.001 Load Balancer The proposed load balancer should have the capability to be configured

as the SSL/TLS termination point for HTTPS requests.


to cache the static content that it receives from origin or backend servers

in its process memory.


to compress data received from servers in the back end and forward the

compressed content to the requesting clients.


to limit the number of concurrent connections to a server in the back end.

LB.REQ.005 Load Balancer The proposed load balancer should support Reverse proxy, SSL 3.0 and

TLS 1.0

LB.REQ.006 Load Balancer The proposed load balancer should have the capability to limit the

number of concurrent connections to clients and the maximum speed at

which data can be transferred to clients.

LB.REQ.007 Load Balancer The proposed load balancer should have the capability to limit the rate of

requests from specific clients and request types.


January 2016


5. Cloud management system


1 Solution should support cloud services to be delivered on both X86 (Intel, AMD) and

RISC/ EPIC based servers as and when required.

2 The Solution should be capable of allowing applications to self-service compute, network

and storage infrastructures automatically based on workload demand.

3 The Solution should be capable of decoupling applications and application infrastructure

configurations in portable containers called images

4 The tool should provide image library, where Software and server images can be

maintained. Facilities should be there to import new server templates to the library and

registering, so as to use the same for provisioning the new virtual and physical servers

5 Unified infrastructure management software should provide unified physical and virtual

machine management from single console.

6 The Solution should be able to isolate and allow secure authenticated access to

infrastructure services

7 The Solution should be capable of orchestrating compute and storage resource

placements based on flexible policies to maximize hardware utilization.

8 Infrastructure as a service solution to be offered. It should deliver services using multiple

hypervisors including Unix based hypervisors and physical servers.

9 The Solution should be able to abstract compute, network, and storage resources for the

application and user self-service regardless of hypervisor, server, network and storage

hardware.

10 The Solution should be capable of supporting multi-tenancy to run cloud services

(compute, network, and storage) for multiple consumers on a single platform while

dynamically and automatically managing the isolation of virtual and physical machines

into secure pools. This functionality should be exposed via API

11 The solution must provide API reference, So as to aid in integrating with third party

system.

12 The Solution should be able to provide workload migration, orchestration,

interoperability between private and public clouds (like auto-scaling, cloud-bursting)

13 The Solution must support standards-based REST/SOAP/Equivalent interfaces

14 The Solutions should be deployable on a wide variety of open source and proprietary

host Operating Systems


January 2016


15 The Solution should support open format

16 The solution should also be able to restrict usage of each tenant to defined values, else it

would lead to control over-consumption and under consumption of resources

17 Software console shall provide a single view of all virtual machines, allow Monitoring of

system availability and performance and automated notifications with email alerts.

Software console shall provide reports for performance and utilization of physical

servers, Virtual Machines & hypervisors. It shall co-exist and integrate with leading

systems management vendors

18 Management software should provide real-time utilization & trend analysis for CPU,

Memory, Network, disk and power (for physical servers only) for physical server and

virtual machine. It should able to integrate 3 blade enclosures.

19 Software should provide forecast analysis for future workloads based on previous server

(physical or virtual) utilization history

20 Infrastructure management software console shall provide the Manageability of the

complete inventory of virtual machines, and physical servers with greater visibility into

object relationships.

21 It should provide seamless migration from physical to virtual, virtual to physical and

virtual to virtual servers.

22 Software should provide ability to create solution templates (solution may includes

physical servers, virtual machine, storage, network, OS etc ) which can be automatically

deployed multiple times based on subscription. A Single template should support

multiple virtualization technologies & physical servers.

23 It should provide self service portal through which users can subscribe for their suitable

virtual machine / solution template. Users should be able to define for the period for

which they would like to subscribe for the virtual machine / solution

24 Management software should also include necessary workflow for subscription,

approval and provisioning of solution

25 Management solution should enable to deliver Infrastructure as a service with complete

lifecycle management.

26 Proposed hardware platform should offer state-less compute nodes & ability to move

workloads among the farm of servers across enclosures offered. Virtual Server profiles

should move across enclosures offered in the blade server section

27 To ensure future-proofing infrastructure & considering future bandwidth requirements,

proposed server blades and enclosures must have a cost effective upgrade path.

28 Solution should be capable to allocate bandwidth based on application requirement &

to avoid over provisioning of network resources.


January 2016


29 Solution should have capability to integrate with the network slices/ports mentioned in

the enclosure specification and should able to integrate with variable configurable

speeds

30 The software should have the capability to create virtual machines with required

number of vCPUs

31 The cloud solution should tightly integrate with FC and iSCSI SAN Solution provided in

the storage section to leverage high performance shared storage for greater

manageability, flexibility and availability of cloud services

32 The Virtualization software should be based on hypervisor technology which sits directly

on top of Hardware (Bare Metal). The vendor should offer suitable management

software.

33 The Solution should be able to run various operating systems like windows client,

windows server, Linux (at least RedHat, SUSE, Ubuntu, Debian, FreeBSD, Oracle

Enterprise Linux & CentOS), solarisx86, Novell NetWare and any other open source.

34 The Solution should have the capability for creating Virtual Machines templates to

provision new servers

35 The Solution should continuously monitor utilization across Virtual Machines and

should intelligently allocate available resources among the Virtual Machines

36 The Virtualized Machines should be able to boot from iSCSI, FCoE and fiber channel SAN

37 The Virtualized Infrastructure should be able to consume Storage across various

protocols like DAS, NAS , SAN. It should support thin provisioning

38 The Solution should allow for taking snapshots of the Virtual Machines to be able to

revert back to an older state, if required

39 The Solution should be able to dynamically allocate and balance computing capacity

across collections of hardware resources of one physical box aggregated into one

unified resource pool

40 The Solution should cater for the fact that if one server fails all the resources running on

that server shall be able to migrate to another set of virtual servers as available

41 The Solution should provide support for cluster services between Virtual Machines

42 The Solution should provide patch management capabilities such that it should be able

to update patches on its own hypervisor and update guest operating system through

the existing EMS

43 The Solution should provide the monitoring, prioritizing and reserving capabilities for

storage, processor, network, memory so as to ensure that the most important Virtual

Machines get adequate resources even in the times of congestion


January 2016


44 The Solution should support Live Migration of Virtual Machine from one host (Physical

Server) to another

45 The Solution should deliver above listed Hypervisor capabilities using standard server

infrastructure

46 The Solution should provide security on the hypervisor, as well as guest VMs. It should

provide the ability to apply security to virtual machines and security policies that can

follow the machines as they move in the cloud.

47 The Solution should provide policy-based configuration management to ensure

compliance across all aspects of the datacenter infrastructure, including virtual

and physical resources.

48 The solution 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).

49 The solution should provide an integrated back-up solution in addition to support for a

centralized backup proxy to offload backup from virtualization host.

50 The Management software should have integrated Physical Host and Virtual Machine

performance monitoring including CPU, Memory, Disk, Network, Power, Storage

Adapter, Storage Path, Cluster services, Virtual machine data stores

51 The management software console shall provide reports for performance and

utilization of Virtual Machines.

52 The management software console shall provide Interactive topology maps to visualize

the relationships between physical servers, virtual machines, networks and storage.

53 The management software should allow reliable and non disruptive migrations for

Physical/ Virtual machines running Windows and Linux operating systems to virtual

environment.

54 The management software should generate automated notifications and alerts, and can

trigger automated workflows to remedy and pre-empt problems.

55 The management software should have provision to capture the blueprint of a known,

validated configuration - including networking, storage and security settings – and

deploy it to many hosts, simplifying setup for automated host

configuration and compliance monitoring

56 The solution should include DR functionality management that must be integrated with

the rest of the virtualization management, with functionality to automate testing and

executing of DR plans (to reduce RTOs) without disrupting production environment

57 The Solution should also provide solution to address replication between

heterogeneous storage arrays across sites.


January 2016


58 The Solution should be able to discover and display virtual machines protected by

storage replication using integration adapters certified by storage vendors.

Support for iSCSI, FibreChannel, and NFS-based store replication.

59 The Solution should be able to discover and display virtual machines protected by

storage replication using integration adapters certified by storage vendors.

Support for iSCSI, FibreChannel, and NFS-based store replication.

60 The Solution should have the ability to extend recovery plans with custom scripts like it

should be able to reconfigure virtual machines’ IP addresses to match network

configuration at failover site.

Compute

1 The Software should have the capability to create Virtual Machines with

required number of vCPUs

2 The Solution should allow Virtual Machines consume RAM dynamically in such

a way that if some of the VMs in Physical machine are not utilizing the RAM,

this RAM can be utilized by some other VM in the same physical machine which has a

requirement

3 The Solution should be able to use power features like in case off peak hours if not all

servers are required to be powered on the solution should shut down to save power

Service Portal Capabilities

1 The Solution should provide a simple to use intuitive Web portal for Data Center Cloud

Administrator and User Departments.

2 The Solution should have self-service capabilities to allow Users Departments to log

service requests

3 The Solution should be able to offer choice of various Service offering on multiple

hypervisors (such as XEN/KVM , Hyper-V, VMware) with an option to select multi

operating systems such as Windows 2003, 2008, RHEL / SUSE Linux, etc., VLAN , Storage

and quickly compute associated price for the same as well as shows the deduction for

overall Tenant approved infrastructure Quota.

4 The Solution should offer Service catalog listing availability of Cloud infrastructure like

Virtual Machines, Physical Machines, Applications , Common Services offered by Private

cloud. Software console shall provide a single view of all type of virtual and physical

machines for monitoring of system availability performance and automated

notifications with email alerts.

5 The Solution should provide comprehensive service catalog with capabilities for service

design and lifecycle management, a web-based self-service portal for users to order and

manage services


January 2016


6 The solution should provide an on-boarding mechanism for the new tenants (

Department) on the cloud infrastructure that automatically creates the tenant, the

tenant administrators, allocates specific resources for the tenant like

storage pools, server pools, S/W packages, network pools (including VLANs, DNS, IP

address spaces, etc...)

7 The Solution should offer Registration, Signup , Forgot Password and other standard

pages (Profile, Billing or Contact information)

8 The Solution should enforce password policies and allow to personalize the look & feel

and logo on the user-interface panels

9 The Solution should be able to offer choice of various hardware profiles, custom

hardware profile, Selection of operating systems, VLAN, Storage. Solution should have

capability to integrate with the network slices/ports mentioned in the enclosure

specification and should able to integrate with variable configurable speeds and

resources available in the enclosure

10 The Solution should automate provisioning of new and changes to existing

infrastructure (Virtual, Physical, Application or Common Services) with approvals

11 The Solution should allow creation of library hosting various Operating System that can

be selected while creating new virtual and physical servers

12 The Solution should track ownership and utilization of virtual machines, Physical

machines, and common services. Solution should have capability to allocate bandwidth

based on application requirement & to avoid over provisioning of network resources. .

13 The Solution must provide the capability to support the following Service Request Types

or reasons for contact: Provisioning of Commuting Infrastructure - Virtual, Physical or

OS

14 The Solution should allow for implementing workflows for provisioning, deployment,

decommissioning all virtual and physical assets in the cloud

datacenter

15 The Solution should allow easy inventory tracking all the physical & virtual assets in the

Private Cloud. The software solution should provide life-cycle management for physical

and virtual servers

16 The Solution should employ Role Level Access Control with the ability to central manage

Roles and Identities in an LDAP based Identity Store

17 The Solution should have the ability to manage Virtual Assets across the major multiple

virtualization platforms (Microsoft, VMware, Xen/KVM, UNIX VM)

18 The Solution should be able to dynamically allocate and balance computing capacity

across collections of hardware resources aggregated into one unified resource pool

with optional control over movement of virtual machines like restricting VMs to run on

selected physical hosts


January 2016


19 The Solution should have Show-Back (to check the usage patterns and reporting for the

user department) and the same solution should have the capability of Charge-Back

20 The Solution should offer usage report by tenant, by region, or by virtual and by

physical server machine reporting usage of memory consumption, CPU consumption,

disk consumption

21 The solution should allow the users to schedule a service creation request in a future

date/time; the solution should check if a request scheduled for a future time can be

fulfilled and reject the request in case of projected resources shortage or accept the

request and reserve the resources for that request,

The solution should allow the users to schedule a service creation request in a future

date/time; the solution should check if a request scheduled for a future time can be

fulfilled and reject the request in case of projected resources shortage or accept the

request and reserve the resources for that request,

22 The Solution should have web based interface for administration

23 The Solution should have the ability generate customize report as well as the native

ability to export to common formats

24 Whenever the Charge Back mechanism is enabled, the Solution must satisfy the

following requirements: • The Solution should support different cost models like

allocated or reserved cost per virtual machine. It should also allow tracking usage of

resources • The Solution should have the ability to charge differently for different level of

services • The Solution should support cost calculation of shared/ multi-tenant

application

25 The Solution should provide service catalog with capabilities for service offering design

and lifecycle management, a self-service portal for users to order and manage services

Capacity Management

1 The Solution should be able to determine how many more physical and virtual

machines can fit the environment

2 The Solution should identify idle, underutilized capacity to provide inputs to the capacity

management function such that informed decisions can be taken

3 The Solution should support to identify and determine optimum sizing and placement

of virtual and physical machines

4 The Solution should provide forecast reports demonstrating forecasted utilization of the

entire solution

5 The Solution should support all of the following modeling scenarios: Physical

to Virtual, Virtual to Virtual, Virtual to Physical,


January 2016


6 The Solution should provide a mechanism to automatically assess high volumes of

workloads and determines optimal placement on virtual machines across the

enterprise’s shared resource pools. The cloud solution should tightly integrate with FC

SAN Solution provided in the storage section to leverage high performance shared

storage for greater manageability, flexibility and availability of cloud services. Also it

should able to integrate with the offered storage and virtualization solution offered.

7 The Solution should be able to utilize existing investment in tools/

Functionality and extend these to physical and virtual environment as well, which are

available from leading vendors

Automation, Orchestration and Monitoring

Process Automation

1 The Solution should demonstrate a way to comprehensively model cloud datacenter

process end to end across multiple Vendors software and hardware thus enforcing

Operational Best Practices and Procedures

Integration Capabilities

1 The Orchestration Solution should be open and interoperable and has rich integration

capabilities that support interfaces from command line interface and web services

2 The Solution should provide resource-level operations across compute resources (IBM,

Cisco, HP, Dell, Oracle and/or other hardware), hypervisors (VMware, Xen/KVM, Hyper-

V), storage resources (EMC, Netapp, IBM,HP,Oracle), and network resources (3Com,

Cisco, Juniper). It should support provisioning for

multiple platforms including Windows, Linux, & ESX, HyperV on x86 (32 and 64 bit) and

UNIX on RISC/EPIC environment

3 The Solution should provide capability for orchestrating tasks across systems for

consistent, documented, compliant activity

4 The Solution should possess capabilities to extent resource & cloud fabric management

onto other Private Clouds or public cloud

5 The Solution should be able to move identified workloads to another private cloud or

public cloud

6 The Solution should be able to audit and monitor execution of processes and report on

violations against the same

7 The various participating HW & SW components in

NEA, e-GIF and MSDP Reportbnda.gov.bd/uploads/hardware_specification_standards.pdf · 2021. 2....

Documents

Transcript of NEA, e-GIF and MSDP Reportbnda.gov.bd/uploads/hardware_specification_standards.pdf · 2021. 2....