Specifications for Converged Interconnect for Blade System
Sl. No Feature
Description
Shall be capable of simplifying server connections by
separating the server in the Blade enclosure from LAN, thus
reducing cables without adding switches to manage
1
Standard Features
Shall be capable of tailoring network connections and
speeds based on application needs
Shall be capable of tailoring FC HBA/iSCSI HBA
connections and speeds based on application needs
Shall be capable of increasing the number of NICs per
connection and configuring FC HBA or iSCSI HBA without
adding extra HBA cards, Blade I/O modules, and reducing
cabling uplinks to the data center network
Shall be capable of slicing the physical port up to 3
FlexNICs and 1 FlexHBA or 4 FlexNICs to reduce overall
components
Should support SR-IOV management to allow assigning
Virtual Functions to any Physical Functions
Shall be capable of providing 16 x 20Gbps downlinks to
Blade servers
Shall be capable of providing redundant 20Gbps cross
connects between Blade I/O Modules for redundancy and
stacking
Shall be capable of providing flexibility in choosing between
40Gbps, 10Gbps SR, LR, or LRM fiber and copper SFP+
uplinks
Shall be capable of providing flexibility in choosing between
4Gbps and 8Gbps Fibre SFP transceivers to connect to
external storage switches
Shall be capable of providing up to 4 X 40Gbps or 16 x
10Gbps uplinks to connect to other Standard Data Center
Ethernet switches and at least 8 x 8Gbps uplinks to FC
Storage switches for Ethernet and Fibre Storage network.
Should support atleast 4* 1Gbps Ethernet uplinks if required
Each of the tailoring NIC shall be capable of tailoring the
network bandwidth with their own dedicated, customized
bandwidth per 20Gb downlink connection, with
customizable speeds from 100Mbps to 20Gbps
Shall be capable of configuring in IGMP groups
Shall be capable of supporting VLAN Tagging, Pass-Thru
and Link Aggregation on all uplinks
Shall support MTU up to 9216 Bytes - Jumbo Frames
Should be capable of providing an embedded Management
Console which is Simple and should contain an intuitive
Graphical User Interface (GUI) for defining, configuring, and
managing network connections for ease of Management
Shall be capable of supporting secure HTTP and scriptable
CLI interface
Shall be capable of supporting standards such as SNMP
v.1 and v.2, SMI-S for providing ease of administration and
maintenance
Shall be capable of providing Role-based security for
network and server administration with LDAP compatibility
Shall be capable of providing Port Mirroring on any uplink
for network troubleshooting support with Network Analyzers
2
Management
Shall be capable of providing support for IGMP Snooping
for optimizing network traffic and reducing bandwidth for
multicast applications such as streaming applications
Shall be capable of recognizing and directing Server-Side
VLAN tags
APPENDIX-17
Complied? YES / NO Remarks
2
Management
Specifications for Converged Interconnect for Blade System
Sl. No Feature
Description
Should support network access groups to prevent enabling
specific network combinations in the same server profile
Shall support QoS configurable based on DOT1P and
DSCP
Shall be capable of providing a robust, scriptable and
secure Command Line Interface for simplified management,
enabling macros to control common tasks of the Ethernet
Module
Shall support sFlow monitoring
Shall be capable of supporting HTTPS (HTTP exchanged
over an SSL-encrypted session) for access to the
embedded GUI Management module.
Shall be capable of providing User verification by account
name and password
Role based customization to assign various privileges to
Server Admin, Network Admin and Storage Admin
3
Security
TACACS+ authentication, authorization and accounting
RADIUS authentication and authorization
Private VLANs for secure connectivity between servers
within a domain
Shall be capable of providing LDAP Authentication services
for role based security via an LDAP SSL Directory Server
connection
Should support Shared Uplink Sets using Link Aggregation
Control Protocol (LACP) allows the creation of Ethernet
channeling with upstream switches that conform to IEEE
802.3ad
Shall be able to support the configuration of the uplink Ports
for failover.
4
Trunking and Failover
Should support sensing a failed upstream switch connection
and faioling over teamed NICs
Should support Fast MAC Cache failover
Shall be capable of supporting active connections on uplink
connections or aggregated uplinks in the event of an uplink
failure to a data center switch
Shall be capable of Configuring uplink speeds to Auto,
1Gb,or10Gb on the associated uplinks
Shall be capable of support 802.1Q VLAN on uplinks
The Uplink ports shall be capable of configuring for VLAN
5
VLAN Features
tagging at egress or pass-thru of tagged VLAN packets
from Server ports.
Shall be capable of supporting Native VLAN for untagged
packets on a shared uplink and Packets can be targeted to
a specific server ports
Should support HBA aggregation on FC configured uplink
Storage
6
network connectivity features
ports using ANSI T11 standards-based N_Port ID
Virtualization (NPIV) technology
Shall be capable of supporting various standards such as:
INCITS FC-BB-5 Rev 2.00 (on all downlinks), 802.1Qbb,
802.1Qaz, 802.1AB LLDP, 802.1Q (VLAN includes Native
VLAN support and server side VLAN tag mapping), 802.2
LLC, 802.3ad Link Aggregation, 802.3ae 10Gb Fiber
Ethernet, 802.3aq 10Gb LRM Ethernet, SNMP v.1, v.2,
7
Management & Standards Support
IGMP v1, v2, v3, IPv6, SR-IOV, ANCI T11 N_Port ID
Virtualization, FC-PH Rev. 4.3, FC-PH-2, FC-PH-3, FC-FLA,
FC-GS, FC-GS-2, FC-GS-3, FC-FG, FC-VI, FC Element
MIB RFC 2837, Fibre Alliance MIB Version 4.0, FC-BB5
and sFlow v5
APPENDIX-17
Complied? YES / NO Remarks