Kerala Development And Innovation Strategic Council Tender

SERVER (Compute Nodes - High Memory) - Processor: Make: Intel/AMD, Series: Platinum/Gold/EPYC (Latest Series), Number of Processors: 4, No. of Cores/Processor: 18, No of threads/Core: 2, Base Frequency: = 2.9GHz, Turbo Frequency: = 3.50 GHz, Cache: = 24 MB, Form Factor: Rack/Blade, Size: 2U/4U, Support: AVX/AVX2; Motherboard: Chip-set Compatible: Intel/AMD, Max CPU Sockets: 4; Memory: Type: DDR4 RDIMM ECC, Single Memory module: 32GB/64GB, Speed: =3200 MT/s, Memory size: 2TB, Max memory Support: 2TB (32/64GB Module); Storage: SAS SSD: 2 No’s, SASSSD Size: 800GB, SAS SSD Req: OS Partition, SAS SSD RAID Level: RAID 1, SATA SSD usable size: 5TB, Min SATA SSD Drives: =5, SATA SSD RAID Level: RAID 5; RAID Cards: RAID level: 0,1,5,6,10,50,60, Ports/Lanes: = 8, Cache: = 8GB NV, Interface Support: SAS, SATA, NVMe; Interfaces & Ports: Total network cards: 2, Network card1 Type: Ethernet, Network card1 Speed: 1G and 10G Supported, Network card1 ports required: 4x1G and 10G supported, PXE Support, Virtual Machine Device Queues (VMDq), PCI-SIG* SR-IOV Capable, Server network ports should support DPDK and it should deliver zero packet loss as per RFC 2544 and deliver 100%-line rate for all the packet sizes over 64 Bytes, Vendor must submit latest DPDK test report for the same, Network card2 Type: SFP28, Network card2 Speed: 10G/25G, Network Transceivers: 25Gb SFP28 SR 100m Transceiver & Cables, Network card2 ports required: 2, PXE Support, Virtual Machine Device Queues (VMDq), PCI-SIG* SR-IOV Capable, Server network ports should support DPDK and it should deliver zero packet loss as per RFC 2544 and deliver 100%-line rate for all the packet sizes over 64 Bytes, Vendor must submit latest DPDK test report for the same; Operating system, Certifications/Compliance (OS): RHEL 7,8+, Ubuntu 20+, Oracle Linux 8,9+, Debian 11,12+, Windows, Certifications/Compliance (Virtualization/Cloud Platform): VM ware, PROXMOX, KVM, Citrix; Server Monitor (With Advanced License): Separate Monitoring Interface: Inbuilt Web-based secure Server hardware monitoring alerting system.

SERVER (Compute Nodes GPU Cluster) - Processor: Make: Intel/AMD, Series: Platinum/Gold/EPYC (Latest Series), Number of Processors: 2, No. of Cores/Processor: 18, No of threads/Core: 2, Base Frequency: = 2.9GHz, Turbo Frequency: = 3.50 GHz, Cache: = 24 MB, Form Factor: Rack/Blade, Size: 2U/4U, Support: AVX/AVX2; Motherboard: Chip-set Compatible: Intel/AMD, Max CPU Sockets: 2; Memory: Type: DDR4 RDIMM ECC, Single Memory module: 32GB, Speed: =3200 MT/s, Memory size: 512GB, Max memory Support: 1TB (32GB Module); GPU/FPGA/Acceleration Cards: Make: NVIDIA, Series: H100 NVL 94GB, Number of GPU: 1, Number of CUDA cores: 16,896, Number Tensor Cores: 528, Memory: =48GB; Storage, SAS SSD: 2 No’s, SASSSD Size: 800GB, SAS SSD Req: OS Partition, SAS SSD RAID Level: RAID 1, SATA SSD usable size: 5TB, Min SATA SSD Drives: =5, SATA SSD RAID Level: RAID 5; RAID Cards: RAID level: 0,1,5,6,10,50,60, Ports/Lanes: = 8, Cache: = 8GB NV, Interface Support: SAS, SATA, NVMe; Interfaces & Ports: Total network cards: 2, Network card1 Type: Ethernet, Network card1 Speed: 1G and 10G Supported, Network card1 ports required: 4x1G and 10G supported, PXE Support, Virtual Machine Device Queues (VMDq), PCI-SIG* SR-IOV Capable, Server network ports should support DPDK and it should deliver zero packet loss as per RFC 2544 and deliver 100%-line rate for all the packet sizes over 64 Bytes, Vendor must submit latest DPDK test report for the same, Network card2 Type: SFP28, Network card2 Speed: 10G/25G, Network Transceivers: 25Gb SFP28 SR 100m Transceiver & Cables, Network card2 ports required: 2, PXE Support, Virtual Machine Device Queues (VMDq), PCI-SIG* SR-IOV Capable, Server network ports should support DPDK, and it should deliver zero packet loss as per RFC 2544 and deliver 100%-line rate for all the packet sizes over 64 Bytes, Vendor must submit latest DPDK test report for the same; Operating system: Certifications/Compliance (OS): RHEL 7,8+, Ubuntu 20+, Oracle Linux 8,9+, Debian 11,12+, Windows, Certifications/Compliance (Virtualization/Cloud Platform): VM ware, PROXMOX, KVM, Citrix; Server Monitor (With Advanced License): Separate Monitoring Interface: Inbuilt Web-based secure Server hardware monitoring alerting system.

SERVER (Compute Nodes For VM) - Processor, Make: Intel/AMD, Series: Platinum/Gold/EPYC (Latest Series), Number of Processors: 2, No. of Cores/Processor: 16, No of threads/Core: 2, Base Frequency: = 2.9GHz, Turbo Frequency: = 3.50 GHz, Cache: = 24 MB, Form Factor: Rack/Blade, Size: 2U, Support: AVX/AVX2; Motherboard: Chip-set Compatible: Intel, Max CPU Sockets: 2; Memory, Type: DDR4 RDIMM ECC, Single Memory module: 32GB, Speed: =3200 MT/s, Memory size: 256GB, Max memory Support: 1TB (32GB Module); Storage: NVME SSD: 2 No’s, NVME Size: 800GB, NVME SSD Req: OS Partition, NVME SSD RAID Level: RAID 1, NVME SSD usable size: 8-10TB, Min NVME SSD Drives: =10, SATA SSD RAID Level: RAID 5; RAID Cards: RAID level: 0,1,5,6,10,50,60, Ports/Lanes: = 8, Cache: = 8GB NV, Interface Support: SAS, SATA, NVMe; Interfaces & Ports: Total network cards: 2, Network card1 Type: Ethernet, Network card1 Speed: 1G and 10G Supported, Network card1 ports required: 4x1G and 10G supported, PXE Support, Virtual Machine Device Queues (VMDq), PCI-SIG* SR-IOV Capable, Server network ports should support DPDK and it should deliver zero packet loss as per RFC 2544 and deliver 100%-line rate for all the packet sizes over 64 Bytes, Vendor must submit latest DPDK test report for the same, Network card2 Type: SFP28, Network card2 Speed: 10G/25G, Network Transceivers: 25Gb SFP28 SR 100m Transceiver & Cables, Network card2 ports required: 2, PXE Support, Virtual Machine Device Queues (VMDq), PCI-SIG* SR-IOV Capable, Server network ports should support DPDK and it should deliver zero packet loss as per RFC 2544 and deliver 100%-line rate for all the packet sizes over 64 Bytes, Vendor must submit latest DPDK test report for the same; HBA Card: FC-HBA Card; Supported FC-HBA card for Tape Library interface; Operating system: Certifications/Compliance (OS): RHEL 7,8+, Ubuntu 20+, Oracle Linux 8,9+, Debian 11,12+, Windows, Certifications/Compliance (Virtualization/Cloud Platform): VM ware, PROXMOX, KVM, Citrix; Server Monitor (With Advanced License): Separate Monitoring Interface: Inbuilt Web-based secure Server hardware monitoring alerting system.

Tier1 Storage (500TB capacity) - Storage Quality Certification: The Storage OEM should be established in the Gartner or any other equivalent global research firm for the last five years; Storage Controller: 1. The Storage system offered must be a true unified and scale-out system offering NAS (file), SAN (block) and object workloads. The Storage supplied should be an appliance with a Single Microcode offering all protocols and should not be based on server-based General Purpose File systems or Operating systems such as Linux, Windows etc., 2. Storage system must be offered in a No-Single-Point of Failure offering up to six 9s of availability with a minimum of 2 Nodes/Controllers and Scale-Out to a minimum of 12 Nodes/Controllers; Cache/Memory Support: 1. The system should be offered with a minimum 1.2 TB Distributed/Global/Federated DRAM cache across dual controllers. The cache should be scalable to 6 TB in a scale-out architecture with a minimum 12 Controllers. The system should offer the capability to protect the write cache in case of a controller failure. Also, a failure of a controller should not lead to write-through mode for cache; Drive Support: The system must support NVMe SSDs each of 100GbE interface speed to meet the capacity and performance requirements for the applications. The system must support a minimum of 240 disks for scalability purposes; Disk Drive Protection: The proposed system should offer minimum raid 6/dual drive failure protection, however for high-density drives it should also support triple drive failure protection for better resiliency and performance; Capacity: 1. The system should be configured with 500TB Usable capacity using NVMe SSD Drives with Raid 6/ Dual drive failure protection; Performance: The storage should be able to deliver a minimum of 345,000 IOPS and 10GBps (Gigabyte) with R/W 80/20, Sequential 32K block; Protocols: The storage should be configured natively with FC, NVMe-oF, NVMe/TCP, iSCSI, NFS (NFSv3, NFSv4, NFSv4.1 supporting RFC5661), CIFS/SMB protocols for use with different applications. In addition to the above, Object (S3 compatible) protocol should also be supported either natively or through any additional appliance; Front-End and Backend connectivity, The proposed storage system should have a minimum 4 x100GbE back-end ports and 8 x 10GbE iSCSI and 8 x 32 Gb FC front-end ports available across dual controllers; Investment Protection: 1. The storage offered should be a true scale-out system that allows the intermixing of controllers across generations within the same system, the system should also support the intermixing of All-flash and Hybrid arrays is the same cluster and be scalable to a minimum of 12 controllers for maximum investment protection, 2. The proposed system should offer the capability to tier the data to either On-Prem or Cloud Object Storage. The system should be configured with any software capability or license for On-Prem tiering to Object Storage from day one; Storage General Features: 1. Ability to expand LUNS/Volumes on the storage online and instantly, 2. Redundant hot-swappable components like controllers, disks, power supplies, fans etc. and allow re-usage of Disk Shelves with higher models of the same product line, 3. The proposed system should offer up to 20PBs capacity scalable within a single namespace, 4. The proposed storage should enable and integrate with server virtualization technologies such as VMware vSphere. The proposed storage must support VASA 3.0 and above, VMware VVOL feature and the feasibility of creating more than 1000 VVOLs. The proposed array should be able to present both the VVOL storage pool and traditional LUN’s, 5. The storage system should be capable of providing multi-pathing software with failover and load-balancing functionality, 6. The proposed storage should provide both in-line and post-process efficiency features such as Compression, De-Duplication and Compactation, 7. The proposed storage should be able to provide secure multi-tenancy for air gap security and isolation from other workloads; Data Protection: 1. The proposed system/solution should offer incremental replication capabilities in both fan-out and cascading topologies. The WAN replication should be secured by end-to-end encryption and bandwidth optimization supported natively. All the necessary licenses should be quoted from day 1; 2. The Storage array should be offered with Synchronous, Asynchronous replication features & Zero Data Loss protection between the DC, DR and Near DR, 3. The offered system should ensure a unified architecture flexibility for replication both on-prem & to the cloud natively without the use of any third-party hardware or software solutions. The replication should support end-to-end encryption and bandwidth optimization, 4. Proposed storage should offer capabilities to create backup copies across sites and also allow replication of data across backup targets. Any license required should be configured; Security and Encryption, 1. The proposed storage array must support data at rest encryption for file shares including both CIFS and NFS, managed by an On-board Key Manager or External Key Manager offering industry-standard certification/compliance by using a cryptographic security module supporting FIPS 140-2 level encryption. For multi-tenant configuration, individual tenant's keys should be managed by the offered storage, 2. The storage system should offer high-performance compliance solutions in accordance with various industry standards to meet regulations such as Securities and Exchange Commission (SEC) 17a-4, HIPAA, Financial Industry Regulatory Authority (FINRA), Commodity Futures Trading Commission (CFTC), and General Data Protection Regulation (GDPR), 3. Storage management software should support MFA to ensure secure access to Management Software. The Storage array should support SHA-2 level security for managing user credentials, 4. The storage should be configured to comply with SEC Rule 17a-4 for file systems. Also, the offered storage should ensure that no one including the administrator should can delete the data post WORM enabled; Management, 1. The Proposed Storage system should have native GUI to monitor & perform operations on data protection jobs, 2. The Storage Management Software should offer operational simplicity and rich data management functionalities for Unified Storage. It should provide a single dashboard to monitor the health, availability, capacity usage, performance, and data protection status of various platforms along with resource planning, 3. The management tool should display system alerts and notifications for proactive management on the dashboard for users to quickly access them and it should provide information about support cases raised on the cluster, 4. The offered system should support ransomware and insider threat detection to protect data with early detection and actionable intelligence on ransomware and other malware incursions. It should detect malicious activity and protect the data by automatically taking a snapshot; Rack Mountable: The storage should be supplied with a rack mount kit. All the necessary patch cords (Ethernet and Fiber) shall be provided and installed by the vendor; Warranty & AMC: The Hardware and software quoted should have 5 years of support along with upgrades and updates; Storage Type: NAS; Number of nodes: 4; Drive type: NVMe, QLC; End-to-end NVMe; Total usable capacity (TB): 500 TiB; Systems disk shelfs connectivity (Gbps): 100GB (Controllers to Disk Shelf); Systems backend network connectivity: 25GB (Node to Node); Scalable NAS (up to max), 9PB; System CPU proposed: =48 cores; System CPU per node, 12 cores; System memory proposed, =256 GB; System memory per node, =64 GB; NVDIMM/NVRAM, =8 GB Per Node; Total NVDIMM/NVRAM, =32 GB; Network configuration proposed, 8 x 25G SFP28 & 16 x 25G SFP28; Cloud tiering or fabric pool, ; Compression, ; Deduplication, ; Thin provisioning, ; Data access protocols, FC, iSCSI, NVMe/FC, NVMe/TCP, FCoE, NFS, SMB, Amazon S3; Dual Network Active-Active Switch for Customer Connection, 2x24Port SFP28 switch with Minimum of 4x40G/100G QSFP28 port for Uplink; Tiering support, Should support auto tiering and tiering policies. Software’s for the tiering management has to be included.

Tier 2 Storage (500 TB capacity) - Storage Quality Certification: The Storage OEM should be established in the Gartner or any other equivalent global research firm for the last five years. , 2, Storage Controller: 1. The Storage system offered must be a true unified and scale-out system offering NAS (file), SAN (block) and object workloads. The Storage supplied should be an appliance with a Single Microcode offering all protocols and should not be based on server based General Purpose Filesystems or Operating systems such as Linux, Windows etc, : 2. Storage system must be offered in a No-Single-Point of Failure offering upto six 9s of availability with minimum 2 Nodes/Controllers and Scale-Out to minimum 12 Nodes/Controllers, : 1. The system should be offered with minimum 256GB Distributed/Global/Federated DRAM cache across dual controllers. The cache should be scalable to 1536 GB in a scale-out architecture with minimum 12 Controllers. System should offer capability to protect the write cache in case of a controller failure. Also, a failure of controller should not lead to write-through mode for cache, 4, Drive Support: The system must support NVMe SSD's each of 100GbE interface speed to meet the capacity and performance requirements for the applications. The system must support a minimum of 96 disks for scalability purpose, 5, Disk Drive Protection: The proposed system should offer minimum dual drive failure protection, however for high density drives it should also support triple drive failure protection for better resiliency and performance, 6, Capacity: 1. The system should be configured with 500TB capacity using NVMe SSD Drives with Dual drive failure protection, 7, Performance: The storage should be able to deliver minimum 150,000 IOPS and 4.5 GBps (Gigabyte) with R/W 80/20, Sequential 32K block, 8, Protocols: The storage should be configured natively with FC, NVMe-oF, NVMe/TCP, iSCSI, NFS (NFSv3, NFSv4, NFSv4.1 supporting RFC5661), CIFS/SMB protocols for use with different applications. In addition to the above, Object (S3 compatible) protocol should also be supported either natively or through any additional appliance, 9, Front-End and Backend connectivity: The proposed storage system should have minimum 4 x100GbE back-end ports and 8 x 10GbE iSCSI and 8 x 32 Gb FC front end ports available across dual controllers, 10, Investment Protection: 1. The storage offered should be a true scale-out system that allows intermixing of controllers across generations within the same system and scalable to a minimum of 12 controllers for maximum investment protection. , : 2. The proposed system should offer capability to tier the data to either On-Prem or Cloud Object Storage. System should be configured with any software capability or license for On-Prem tiering to Object Storage from day-one, 11, Storage General Features: 1. Ability to expand LUNS/Volumes on the storage online and instantly, : 2. Redundant hot swappable components like controllers, disks, power supplies, fans etc. and allow re-usage of Disk Shelves with higher models of the same product line, : 3. The proposed system should offer upto 20PBs capacity scalable within a single namespace, : 4. The proposed storage should enable and integrate with server virtualization technologies such as VMware vSphere. The proposed storage must support VASA 3.0 and above, VMware VVOL feature and feasibility to create more than 1000 VVOLs. The proposed array should be able to present both VVOL storage pool and traditional LUN’s, : 5. The storage system should be capable of providing multi-pathing software with failover and load balancing functionality, : 6. The proposed storage should provide both in-line and post process efficiency features such as Compression, De-Duplication and Compression, : 7. The proposed storage should be able to provide secure multi tenancy for air gap security and isolation from other workloads, 12, Data Protection: 1.The proposed system/solution should offer incremental replication capabilities in both fan-out and cascading topologies. The WAN replication should be secured by end-to-end encryption and bandwidth optmization supported natively. All the necessary licenses should be quoted from day 1, : 2. The Storage array should be offered with Synchronous, Asynchronous replication feature & Zero Data Loss protection between the DC, DR and Near DR, : 3. The offered system should ensure a unified architecture flexibility for replication both on-prem & to the cloud natively without the use of any third-party hardware or software solutions. The replication should support end-to-end encryption and bandwidth optimization, : 4. Proposed storage should offer capabilities to create backup copies across sites and allow replication of data across backup targets. Any license required should be configured, 13, Security and Encryption: 1. The proposed storage array must support data at rest encryption for file shares including both CIFS and NFS, managed by On-board Key Manager or External Key Manager offering industry standard certification/compliance by using a cryptographic security module supporting FIPS 140-2 level encryption. For multi-tenant configuration, individual tenant's keys should be managed by the offered storage, : 2. The storage system should offer high-performance compliance solution in accordance to various industry standards to meet regulations such as Securities and Exchange Commission (SEC) 17a-4, HIPAA, Financial Industry Regulatory Authority (FINRA), Commodity Futures Trading Commission (CFTC), and General Data Protection Regulation (GDPR), : 3. Storage management software should support MFA to ensure secure access of Management Software. The Storage array should support SHA-2 level security for managing user credentials, : 4. The storage should be configured to comply with SEC Rule 17a-4 for filesystems. Also, the offered storage should ensure that no one including administrator should be able to delete the data post WORM enabled, 14, Management: 1. The Proposed Storage system should have native GUI to monitor & perform operations on data protection jobs, : 2. The Storage Management Software should offer operational simplicity and rich data management functionalities for Unified Storage. It should provide a single dashboard to monitor health, availability, capacity usage, performance, and data protection status of various platforms along with resource planning, : 3. The management tool should display system alerts and notifications for proactive management on the dashboard for users to quickly access them and it should provide information about support cases raised on the cluster, : 4. The offered system should support ransomware and insider threat detection to protect data with early detection and actionable intelligence on ransomware and other malware incursions. It should detect malicious activity and protect the data by automatically taking a snapshot, 15, Rack Mountable: The storage should be supplied with rack mount kit. All the necessary patch cords (Ethernet and Fiber) shall be provided and installed by the vendor, 16, Warranty & AMC: The Hardware and software quoted should have 5 years support along with upgrade and updates, 17, Tiering support: Should support auto tiering and tiering policies. Software’s for the tiering management must be included

Tier 3 Storage (500 TB Capacity) - 1, Storage Quality Certification: The Storage OEM should be established in the Gartner Leader Quadrant , 2, Storage Controller: 1.The Storage system should a unified system supporting all Block, File and Object protocols cluster in active-active configuration, : 2. Storage system must be offered in a No-Single-Point of Failure offering upto six 9s of availability with minimum 2 Nodes/Controllers and Scale-Out to minimum 12 Nodes/Controllers, 3, Cache required: 1. The unified system should have minimum 128 GB data cache post protection overheads across supplied controllers with an ability to protect data on cache if there is a controller failure or power outage. Cache should be protected for Writes either through a battery backup or by destaging to flash/disk, : 2. The system should be configured with minimum 2TB of SSD/Flash/NVMe in addition to the above and same should be scalable to 12TB, 4, Drive Support: The unified system must support intermixing of SSD, SAS and SATA drives to meet the capacity and performance requirements of the applications. The system must support a minimum of 140 disks in a dual controller architecture and maximum of 570 disks in a scale-out-architecture, 5, Protocols: The storage should a true unified storage configured with iSCSI, FC, FCOE, NFS (NFSv3,NFSv4, NFSv4.1) SMB(,SMB2 & SMB3) ,S3 and pNFS protocols for use with different applications and should support the maximum capacity offered by the storage system. Any hardware/software required for this functionality shall be supplied along with it in No Single Point Of Failure mode, 6, RAID configuration: Should support Raid 6/Dual Parity & Triple Parity, 7, High Availability: The unified storage system must be configured to continuously serve data in event of any controller failure. In addition to this, it must also be possible to withstand failure of any 2 or 3 disks per RAID-Group of size not more than 28 disks. In Event, architecture uses a single pool instead of multiple RAID Groups, system should be resilient against failure of three drives for every 28 drives used in the pool, 9, Storage Capacity: Storage must supply with 500 TB usable capacity NL-SAS Disk with RAID6/DP/ Triple Parity with Spare Drive at 30 drives one spare drive need to be populated, 10, Performance: The storage should be able to deliver 700 MBps (Megabyte)/22,000 IOPS with 80/20 R/W Sequential 32K block, 11, Front-End and Backend connectivity: The proposed storage system should have minimum 4x12Gb SAS ports and 4x10GbE Fiber and 4 x 32Gbps FC front end ports available across dual controllers, 12, Rack Mountable: The unified storage should be supplied with rack mount kit. All the necessary patch cords (Ethernet and Fiber) shall be provided, 13, Storage Scalability and Upgradability: 1. The unified proposed system should be field upgradeable to a higher model through data-in-place upgrades, : 2. The unified Storage should be a true scale-out architecture allowing mixing of Controller/Nodes within same product line with higher configurations, : 3. Unified Storage system should allow re-usage of Disk Shelves with higher models of the same product line, 14, Storage functionality : The unified storage shall have the ability to expand LUNS/Volumes on the storage online and instantly, : The unified storage shall have the ability to create logical volumes without physical capacity being available or in other words system should allow over-provisioning of the capacity. The license required for the same shall be supplied for the maximum supported capacity of the offered storage model, : The unified storage should be configured with Quality-of-Service feature for IOPs/Throughput for both Block and File, : The unified storage shall support logical partitioning of controllers in future such that each partition appears as a separate Virtual storage in itself for both block and file, : The storage should support data tiering with real-time movement of hot data to high performing drives. It should offer the capability to move data between one tier of drives to another tier of drives, : The proposed unified storage system should be configured to provide data protection against two simultaneous drive failures, : The required number hard disks for parity & spares, should be provided exclusively of the usable capacity mentioned. , : Unified System should have redundant hot swappable components like controllers, disks, power supplies, fans etc, 15, Point-in-times images: The unified storage should have the requisite licenses to create point-in-time snapshots. The storage should support minimum 250 snapshots per volume/LUN. The license proposed should be for the complete supported capacity of the unified system for both block and file, : The unified system should support instant creation of clones of active data, with near zero performance impact for both block and file, 16, Encryption for Data At Rest: The proposed storage array must support data at rest encryption offering industry standard certification/compliance. The storage array may implement data at rest encryption using self-encrypting drives or controller-based functionality there by not impacting performance, 17, Management: Single management, easy to use GUI based and web enabled administration interface for configuration, storage management and performance analysis tools for both block and file, 18, Remote Support & Diagnostics: Storage management should support "Call home" facility with web-based self-service portal providing an integrated, efficient monitoring and reporting capability and supporting data collection. Management software should provide features like; : 1. Automated call home feature, : 2. Nonintrusive alerting, : 3. Performance and Capacity reports, : 4. Ongoing health check analysis, OS support: Support for industry-leading Operating System platforms including: LINUX, Microsoft Windows, HP-UX, SUN Solaris, IBM-AIX, etc, : Any Multipathing software required for the solution must be supplied for unlimited host connectivity, 19, De-Duplication, Compression and Compaction: Proposed unified storage should support Iline as well As Post Process block level data de-duplication, compression and compaction for all kinds of data (structured & unstructured) on both block and file, 20, VMware Integration: The proposed storage should enable and integrate with server virtualization technologies such as VMware vSphere. The proposed storage must support VASA 3.0 and above, VMware VVOL feature and feasibility to create more than 1000 VVOLs. The proposed array should be able to present both VVOL storage pool and traditional LUN’s, 21, Multi-Pathing: The storage system should be capable of providing multi-pathing software with failover and load balancing functionality, 22, Certifications: The storage system should offer high-performance compliance solution in accordance to various industry standards to meet regulations such as Securities and Exchange Commission (SEC) 17a-4, HIPAA, Financial Industry Regulatory Authority (FINRA), Commodity Futures Trading Commission (CFTC), and General Data Protection Regulation (GDPR), 23, Warranty & SLA: The Hardware quoted should have 5 years onsite warranty and support, 24, Tiering support: Should support auto tiering and tiering policies. Software’s for the tiering management must be included

Next-generation Firewall Specifications - 1, The Firewall must be appliance based, rack mountable and it should be having internal redundant Power Supply from day one: , 2, The Proposed Firewall Vendor should be in the Leaders/ Challenger in Quadrant of Gartner Magic Quadrant for Enterprise Network Firewall.; 3, The proposed NGFW must have build in GUI and CLI to make on the go changes to Firewall policies without any dependency to management and troubleshoot any issue related to network outage.; 4, NGFW must support Secure SD - WAN feature along with advance routing protocols such as BGP ; 5, SD-WAN must be able to link and failover between various connections such as Internet, MPLS, leash line and even Routed based VPN interfaces.; 6, Build-in SDWAN must be able to do load balancing of various links based on source address, User group, protocol and/or applications ; 7, SLA for SDWAN must be defined based on packet loss or latency or jitter. Even combination of all 3 option must be possible ; 8, Central management solution for the next generation Firewall must be able to Manage all the SDWAN link centrally and should give clear dashboard showing which links are down and which are up. This helps the NOC to take action accordingly; 9, NGFW must support multicast routing as well as firewalling ; 10, The proposed solution should also support policy routing. Policy routing should work along with SD-WAN and ISP load-balancing.; 11, The proposed solution must also support identity-based routing option allowing traffic to be forced out of specific Internet/MPLS gateway based on authentication rather than IP address; 12, The proposed system should have integrated Traffic Shaping functionality this feature should have option to be configured on same firewall policy along with option to configure it separately if required.; 13, Build-in GUI on the NGFW should have option to display logical topology of the network the NGFW is protecting. The display should also be able to give security recommendation for the NGFW.; 14, Device should support Static routing, RIP, OSPF,BGP, IS-IS, RIPng, OSPFv3 and BGP4+, Performance Parameters; 1, The solution should support a minimum of at least 12 Gbps IPS throughput & Minimum 11 Gbps NGFW throughput on real-world / enterprise mix traffic test condition; 2, The solution should support minimum 10 Gbps threat protection throughput on real-world / enterprise mix traffic test condition; 3, Should support 20 Gbps IPSec VPN throughput and 1500 Tunnels; 4, The Firewall must support at least 6,000,000 concurrent connections and 500,000 new sessions per second; 5, The platform must be having minimum of 10 interfaces with auto sensing 10/100/1000 capability, 6 Gigabit SFP ports and 8 10-GbE SFP+ Interfaces from day one, Firewall Features; 1, Firewall policy should be single policy where all the features get applied such as IPS, application control, URL filtering, antivirus, SSL inspection, logging and even NAT ; 2, Firewall must support Zoning option along with User based authentication. It must have automatic option to group all the same zone policy ; 3, There must be option to configure the said Firewall policy from GUI of the NGFW appliance without requiring any Management solution. This is in the case of emergency where management solution is no available and policy needs to be changed.; 4, Firewall must support NAT46, NAT66 and NAT64 along with policy for such NAT along with option to configure DNS64.; 5, Firewall must support NAT policy for multicast traffic for both IPv4 and IPv6; 6, Firewall must support option to configure FQDN server rather then IP address in case server have dynamic IP address or site have multiple IP addresses for single domain.; 7, There must be option to even configure wildcard FQDN; 8, Firewall should allow policy based on port or service to protect attack at L3 not just application based policy which might be vulnerable to L3 attacks.; 9, Firewall must support Geo-based IP address blocking option.; 10, DNS translation option must be available in Firewall to change only the specific DNS reply from public to private IP. This is required for allowing user to access local resources using Private IP rather than there public IP address; 11, Build-in GUI/CLI must support option to configure firewall policy which allow packet capture for troubleshooting purposes; 12, The security appliance should be having configurable option to quarantine attack generating source address, Virtualization; 1, The proposed solution should support Virtualization (Virtual Firewall, Security zones and VLAN). Minimum 5 Virtual Firewall license should be provided.; 2, Virtualization must be for every feature which are IPS, Application control, Antivirus/Anti-malware, URL filtering, SSL inspection, SSL VPN, IPSec VPN, Traffic shaping and user authentication.; 3, Enabling Virtualization shouldn't require any kind of downtime or reboot. It must be done seamless even if the NGFW is live in the network.; 4, When creating virtualized NGFW it should give mode option to configure each virtualized system such as first system can work in NAT/route mode and second system can work in transparent mode.; 5, Each virtualized NGFW system must have option to configure various parameter to limit the resources utilization such as number of session, etc, VPN Features; 1, NGFW must have build in support IPSec VPN and SSL VPN. There shouldn't be any user license restriction; 2, IPSec VPN must include gateway to gateway and gateway to client vpn. In case of gateway to client the administrator must have option to assign private IP address to remote user without requiring any additional license; 3, Route based IPSec VPN must be supported along with SD-WAN in case of two or more ISP's.; 4, IPSec VPN must include gateway to gateway and gateway to client vpn. In case of gateway to client the administrator must have option to assign private IP address to remote user without requiring any additional license; 5, IPSec VPN must support SHA-1 and SHA-2 ( SHA 256, 386 and 512) along with DH group 2,5,14,15,16,17,18,19,20,21,27,28,29,30 and 31.; 6, SSL VPN must support high level algorithm along with TLS v1.2 ; 7, SSL VPN must not have any user license and should have option to integrate with local AD or RADIUS server ; 8, Both VPN must support 2-factor authentication with option to have locally imported tokens on the NFGW appliance itself, if required, Intrusion Prevention System; 1, The IPS detection methodologies shall consist of:, a) Signature based detection using real time updated database, b) Anomaly based detection that is based on thresholds; 2, The IPS system shall have at least 7,000 signatures; 3, IPS Signatures can be updated in three different ways: manually, via pull technology or push technology. Administrator can schedule to check for new updates or if the device has a public IP address, updates can be pushed to the device each time an update is available; 4, In event if IPS should cease to function, it will fail open by default and is configurable. This means that crucial network traffic will not be blocked, and the Firewall will continue to operate while the problem is resolved; 5, IPS solution should have capability to protect against Denial of Service (DOS) and DDOS attacks. Should have flexibility to configure IPv4 and IPv6 Rate based DOS protection with threshold settings against TCP Syn flood, TCP/UDP/ port scan, ICMP sweep, TCP/UDP/ SCTP/ICMP session flooding. Threshold settings must be customizable for different sources, destinations & services; 6, IPS signatures should have a configurable action like terminate a TCP session by issuing TCP Reset packets to each end of the connection, or silently drop traffic in addition to sending a alert and logging the incident; 7, Signatures should a severity level defined to it so that it helps the administrator to understand and decide which signatures to enable for what traffic (e.g. for severity level: high medium low) , Antivirus; 1, Firewall should have integrated Antivirus solution; 2, The proposed system should be able to block, allow or monitor only using AV signatures and file blocking based on per firewall policy based or based on firewall authenticated user groups with configurable selection of the following services:, a) HTTP, HTTPS, b) SMTP, SMTPS, c) POP3, POP3S, d) IMAP, IMAPS, e) FTP, FTPS; 3, The proposed system should be able to block or allow oversize file based on configurable thresholds for each protocol types and per firewall policy, Web Content Filtering; 1, The proposed system should have integrated Web Content Filtering solution without external solution, devices or hardware modules.; 2, The proposed solution should be able to enable or disable Web Filtering per firewall policy or based on firewall authenticated user groups for both HTTP and HTTPS traffic.; 3, The proposed system shall provide web content filtering features:, a) which blocks web plug-ins such as ActiveX, Java Applet, and Cookies, b) Shall include Web URL block, c) Shall include score-based web keyword block, d) Shall include Web Exempt List; 4, The proposed system shall be able to queries a real time database of over millions+ rated websites categorized into 75+ unique content categories.; 5, Update of local Database based on malicious category discovered by local Sandboxing solution from same vendor, Application Control ; 1, The proposed system shall have the ability to detect, log and take action against network traffic based on over 4000 application signatures; 2, The application signatures shall be manual or automatically updated; 3, The administrator shall be able to define application control list based on selectable application group and/or list and its corresponding actions; 4, Application control and URL filtering must work independent of each other, High Availability; 1, The proposed system shall have built-in high availability (HA) features without extra cost/license.; 2, The device shall support stateful session maintenance in the event of a fail-over to a standby unit.; 3, High Availability Configurations should support Active/Active or Active/ Passive , Warranty; 1, Warranty and support for 5 years; 2, Support includes latest patch updates, OEM should be having the following certifications/Ratings; 1, Firewall module should be EAL 4 certified, Centralized Logging & Reporting Solution; 1, The solution should deliver complete security oversight with granular graphical reporting; 2, The solution should provide centralized security event analysis, forensic research, reporting, content archiving, data mining and malicious file quarantining.; 3, The solution should provide detailed data capture for forensic purposes to comply with policies regarding privacy and disclosure of information security breaches.; 4, The solution should analyze user traffic behaviour and identify compromised users/computers; 5, The solution should provide network event correlation to allow administrators to quickly identify and react to network security threats across the network.; 6, The solution should provide streamlined graphical network-wide reporting of events, activities and trends occurring on UTM / NGFW; 7, The solution should provide centralized logging of multiple record types including traffic activity, system events, viruses, attacks, Web filtering events, and messaging activity/data; 8, The solution be able to provide real-time and historical logs with filtering and search capabilities; 9, The solution should be able to displays a map of the world that shows the top traffic destination country by colour; 10, The solution should provide predefined templates for building / generating reports; 11, The solution should be able to collect logs from multiple devices; 12, The solution should support Out-of-the-box playbook templates for enabling SOC analysts to quickly customize the use case, including playbooks for investigation of infections, compromised hosts, critical incidents, data enrichment for viewing Assets and Identity blocking of malware, C&C IPs; 13, The solution should be able to support threshold values to generate alerts.; 14, The solution should be able to send alert emails; 15, The solution should be able to manually generate the report or schedule the same; 16, The solution should be able to generate report based on user names; 17, The solution should be able to process 50 Gb logs per day; 18, The solution should be having minimum 8 TB log storage capacity after configuring RAID for data protection. ; 19, Logging & Reporting architecture shall be hardware or software-based appliance/ VM based solution and the hardware for the solution must be supplied by the bidder.

10G/25G Switch - Device should have non-blocking architecture with wire speed L2 and L3 forwarding, : , Device should have 48 x 1/10/25G SFP28 ports supporting RS-FEC and FC-FEC as per IEEE 802.3by compliance, ; Device should have 8 x 40/100G QSFP28 ports with support breakout to provide additional 16 number of 10/25/50G interfaces, ; Device should have total Throughput of 4Tbps and latency packet forwarding less than 850 nanoseconds, ; Device should support copper Base-T (1G & 10G) connectivity over CAT6 cable and 1G, Dual rate 10G/25G SFP+ fiber connectivity over MM and SM cable, ; Device should support upto 250K MAC address, ; Device should support upto 256K IPv4 Prefix routes, ; Device should support Unified Forwarding Table (UFT) feature to flexibility allocate forwarding table resources to address different type of use cases, ; Device should have Max power draw of upto 315W, ; Shall support active/active layer2/Layer3 multipathing redundancy with Multi-chassis Link Aggregation (MLAG) or equivalent technology while keeping control plane and management plane distributed, ; L2 features, ; Device should support 4K VLANs, 9216 Jumbo frames, ; Device should support MST, per-vlan, RSTP, BPDU Guard, Loop Guard, ; Device should support port ACL with l2, L3 and L4 parameters, ; Device support LLDP and LACP to bundle links and detect miscabling issues, ; Device Should support IEEE 802.1D, 802.1Q, Q-in-Q, 802.1w, 802.1s and 802.1x, , ; L3 features, ; Device should support Routing Protocols: OSPFv2 with multiple instances, OSPFv3, BGP, MP-BGP, IS-IS, and RIPv2, ; Device Should support graceful restart for BGP, OSPF v2 and v3 and ISIS, ; Device Should support BFD inclusive of BFD for Lag links, BFD for V4 and V6 VRF, Multi-hop BFD and BFD on IP unnumbered interfaces, ; Device Should support Policy Based Routing (PBR) for IPv4 and IPv6, VRRP V4 and V6, Resilient ECMP, Unicast Reverse path forwarding (urpf), and Inter-VRF route leaking, ; Device Should support Accumulated IGP Metric (AIGP), BGP Monitoring Protocol (BMP) and BGP Prefix Origin Validation with Resource Public Key Infrastructure (RPKI), ; Device should support VXLAN+EVPN leaf-spine overlay technology supporting type-1 to type-8 routes, ; Device should have support for symmetric and asymmetric IRB with EVPN with distributed gateway functionality, ; Device should support IPv4 and IPv6 clients in EVPN based overlay network, ; Device should support active-active EVPN multi-homing, ; Device should support Dynamic NAT options like Many-to-Many NAT and Many-to-One NAT (PAT) at line rate with no additional latency, ; Device should support IGMP v2/v3,PIM-SM / PIM-SSM, Anycast RP (RFC 4610), VRF Support for IP Multicast, Multicast Source Discovery Protocol (MSDP)and IP Multicast Multipath, ; High availability, ; Device should support Hitless upgrade & reloads in MLAG/Vpc setup and standalone (non-stack) setup, without adversely affecting the forwarding plane with sub second data outage during upgrade, ; Device should support maintenance mode/ Graceful insertion and removal (GIR) to isolate device from the network in order to perform debugging or an upgrade while gracefully steering traffic to peer nodes, ; Device should 1+1 redundant & hot-swappable Fans with support for both front-to-rear and rear-to-front airflow options, ; Device should support 1+1 redundant & hot-swappable power with support for both AC and DC power supply options, ; Device should support Low-Memory mode wherein during out of memory condition the device kills non-essential agents until the system recovers the necessary amount of memory, ; security, ; Should support Storm control and Control Plane protection (CoPP), ; should support port ACL with l2, L3 and L4 parameters, ; should support limiting number of mac address on a link, ; Device should support security-group based segmentation of hosts independent of the network constructs like VLAN, VRF and NVO, ; Device should protect against ARP and DHCP spoofing by ensuring that a port will only permit IP and ARP packets with IP source addresses that have been authorized, ; Device should support IEEE 802.1x Authentication framework, MAC authentication, Dynamic VLAN assignment, Dynamic ACL assignment and CoA, ; Device should support multicast accounting to AAA servers, ; Management, ; Device Should support secure Zero touch provisioning with options to provision Certificates artifacts on the device when it boots, ; should support tracking changes in MAC table, ARP, IPv6 neighbor table and IPv4, v6 route table for troubleshooting purpose, ; should support real time state streaming for advance monitoring from day 1, ; Should Support telnet, industry standard hierarchical CLI, SSHv2, HTTPS, SCP, SFTP, CLI task scheduler and configuration session, ; should support NTP and IEEE 1588 PTP (Transparent Clock and Boundary Clock), ; should support SNMP v1/2/3 and OpenConfig model over gRPC/Netconf, ; device should support Digital Optical Monitoring (DOM), ; Device should support real time data collection with sflow/netflow, ; Automation & Visibility, ; The Device should monitor output queue lengths for all Device interfaces and Log and stream events related to congestion, ; The Device should automatically mirror traffic queued in event of congestion/latency or micro burst and send mirrored traffic to CPU, directly connected server and remote server as per usecase, ; Device should support multi OEM hypervisor environment and should be able to sense movement of VM and configure network automatically, ; Device should support capturing of information around dropped packet events with associated reasons and details which can be streamed out using a open communication protocol like gRPC or equivalent, ; The Device should have OpenStack Neutron for ML2 integration with EVPN VXLAN control plane support, ; Device should support advanced mirroring features: Mirror to CPU, ACL filters and truncation on Mirror sessions, and tunneling of mirror packets to remote servers, ; Should support measure the two-way metrics such as delay, jitter, packet loss rate between two network elements using Two-Way Active Measurement Protocol (TWAMP) as per RFC 5357, ; should have programmability and automation support with on board python, bash and docker containers, ; QOS, ; should support 8 queues per port, ; should support priority queue, ; should support Weighted Fair Queue or Weighted round robin or equivalent, ; should support WRED and DSCP for CPU generated traffic, ; should support ACL based classification for QoS, ; Should support IEEE 802.1Qaz DCBX (Data Center Bridge Exchange), 802.1Qbb PFC (Priority-based Flow Control) and Explicit Congestion Notification (ECN), ; Should support rate limiting function like policing and shaping, ; Others, ; should be certified for NDcPP common criteria, ; should have IPv6 ready logo certification, ; should be 19" rack mountable with 4-post rail mount kit provided for easy installtion, ; Hardware replacement warranty and TAC support should be directly from the OEM. OEM email-id and India Contact support no. to be provided, ; Transceivers should be from Same OEM as of Device, ; Warranty, ; Warranty and support for 5 years

1/10G Switch - 1/10G 10GBASE-T/Multi-Gigabit Ports Switch, : , Port Count: 24/48, ; Uplink: min 4 x 25Gb SFP28 Uplinks, ; Efficiency: Support RoCE, ; Features; ; Speed: 100M/1000M/2.5G/5G/10GBase-T, ; 1+1 Hot-swappable Power Supplies and 2+1 Smart Fans, ; Support QoS, OSPF, DHCP, BGP, VRRP, QinQ, ; Support ACL, RADIUS, TACACS+, DHCP Snooping, etc. for Security, ; Warranty, ; Warranty and support for 5 years.

System Integration - Installation, configuration, testing and commissioning of HPC facility.