Standard Specifications For Network Devices

Corporate Infocom Services
ONGC
Standard Specifications for

Network Devices
Contents
1. Router with POE capability built-in ........................................................................................................ 2
2. Router without POE capability ................................................................................................................ 4
3. L-3 switch ................................................................................................................................................. 6
4. L2 switch – 24 Ports................................................................................................................................. 8
5. L-2 switch - 48 ports ............................................................................................................................... 10
6. Accessories for the ports of switches ...................................................................................................... 10
Rev 1.1 28 Jan. 21
1. Router with POE capability built-in

Router with POE
S No Minimum Technical Specifications
1. General (Features/Hardware should be provided from day 1)
Should be provided with internal redundant power supply. Main Power Supply unit(s) should be able
1.1.
to handle the load of fully loaded chassis.
Router be rack mounted with all accessories for rack mounting provided and should have fans/fan
1.2.
tray(s) for cooling
1.3. Router should have space for minimum 4 I/O modules
Each router should have capability to accommodate up to minimum 16 X 100/1000 Mbps Ethernet
1.4.
ports with POE enabled on each port. WorkCentre may go for more Ethernet/fibre ports if required.
2. Router Architecture and Memory (Features/Hardware should be provided from day 1)
2.1. Router should have control and data planes.
2.2. Should have preferably 4GB of DRAM and built in storage
2.3. Should have support for external USB memory/flash memory
2.4. Router should have latest supported OS of Enterprise Class.
3. Ports
3.1. Requirement (to be supplied with each router)
Each router is to be supplied with 8 X 100/1000 Mbps Base Ethernet ports with POE enabled on each
3.1.1.
port
3.2. Additional Ports
The number of ports indicated schedule is minimum. The bidder is free to offer compatible module
3.2.1.
with higher number of ports provided other specifications are met
4. Router Performance (should be provided from Day 1)
4.1. Should have at least 1 Gbps/1.4 Mpps of Throughput
5. Network Protocols (All protocols/features/licenses should be provided from day 1)
5.1. IPv4 Routing Protocols (All protocols/features/licenses should be provided from day 1)
5.1.1. Should support Static Routing, Default Routing, RIPv2, OSPFv2, BGP, IS-IS
Should support BGP4 routing protocol with CIDR and should have all necessary licenses to enable full
5.1.2.
features of BGP protocol
5.1.3. Should support IPv4 NAT feature/service
5.2.1. Should support Static Routing, Default Routing, RIP for IPv6, OSPFv3, BGP for IPv6, IS-IS for IPv6
5.2.2. Should have all necessary licenses for to enable full features of BGP protocol for IPv6
5.2.3. Router should have full support for dual stack IPv6 on all interfaces and IPv6 over IPv4 tunnelling
5.2.4. Should support NAT64 feature/service.
5.3. Multicast (All protocols/features/licenses should be provided from day 1)
5.3.1. Should have PIM-SM, PIM-DM, PIM-Sparse-Dense mode, Bidirectional PIM, PIM-SSM for IPv4
6. QoS Support (All protocols/features/licenses should be provided from day 1)
The router should support Access Control List to filter traffic based on Source & Destination IP Subnet,
6.1.
Source & Destination Port, VLAN, Protocol Type (IP, UDP, TCP, ICMP, etc.) and Port Range etc.
The Router shall support QoS for Traffic Management, class-based policing, shaping, CBWFQ, WRED,
6.2.
802.1p and HQOS (All Ethernet ports)
6.3. Should support IPv6 QoS, ACL, SSH over IPv6
2| Standard Specs for Network Devices © ONGC

Rev 1.1 28 Jan. 21
Router with POE

7. WAN Protocols (All protocols/features/licenses should be provided from day 1)
7.1. The Router should have WAN protocols like PPP,ML PPP etc.
The router should have at the minimum MPLS features like Layer 2 VPN, Traffic engineering with RSVP-
7.2.
TE, Fast Reroute and Virtual Route Forwarding (VRF) and Layer-3 MPLS-VPN
The Router shall be MPLS Aware and shall work with Service provider provided MPLS services. However
7.3. In case of ONGC wants to build their own MPLS services, Router should have all necessary license and
hardware to act as Customer edge, Provider core and Provider Edge device
8. Encryption (All protocols/features/licenses should be provided from day 1)
Router should support advance generation security protocols (IKEV1/V2) to ensure data confidentiality
8.1.
and integrity. Router should support IPsec Encryption
8.2. Router should provide at least 200 IPSec tunnels (internally)
Other features
9.
(All protocols/features/licenses should be provided from day 1)
Router must have Stateful and VRF aware Firewall and support IPS features natively. The State full
9.1.
firewall should support IPSEC pass through. Firewall and all routing features should run simultaneously.
The router shall provide MD5 hash authentication mechanism for RIPv2, OSPF, IS-IS, BGP and MPLS
9.2.
routing protocols.
9.3. The router shall support AAA features through Active Directory and/or RADIUS or TACACS+
The router shall have Network Address Translation (NAT). Router should be able to use NAT feature on
9.4.
all the interfaces. All software licenses should be included from day 1
Router Should have all the standard enterprise features such as MPLS Layer 2 and Layer 3, Encryption,
9.5. NAT, ACL, IPv6, BGP router reflector, IPSEC and all these features should work together concurrently .
The entire hardware and software license, to enable these features, should be provided from day 1.
10. Regulatory Compliance from day 1
Router shall conform IEC Standards for Safety requirements of Information Technology Equipment.
10.1.
(documentary proof shall be submitted with the bid)
10.2. Command line interface of the router must be in English Language
10.3. Medium of communication shall be in English language for all documents and certificates
10.4. Operating Voltage : AC 220V + 5%, 50 Hz
The specifications given are minimum. Any specification/parameter which is better than that
11.
specified above is acceptable.

Rev 1.1 28 Jan. 21
2. Router without POE capability

Router without POE
Should be provided with internal power supply. Main Power Supply unit(s) should be able to handle the load
1.1.
of fully loaded chassis.
Router be rack mounted with all accessories for rack mounting provided and should have fans/fan tray(s) for
1.2.
cooling
1.3. Router should have space for minimum 2 I/O modules
Each router should have capability to accommodate up to minimum 16 X 100/1000 Base-T WAN Ethernet
1.4.
ports. WorkCentre may go for more Ethernet/fibre ports if required.
2. Router Architecture and Memory (Features/Hardware should be provided from day 1)
2.1. Router should have control and data planes.
2.2. Should have 4GB of DRAM and built-in storage/flash
2.4. Router should have latest supported OS of Enterprise Class.
3. Ports
3.1. Requirement (to be supplied with every router at each location)
3.1.1. Each router is to be supplied with 8 X 100/1000 Base-T WAN Ethernet ports
3.2. Additional Ports
3.2.1. The number of ports indicated schedule is minimum. The bidder is free to offer compatible module with higher
number of ports provided other specifications are met
4. Router Performance (should be provided from Day 1)
4.1. Should have at least 1000 Mbps/1.4 Mpps of Throughput
5. Network Protocols (All protocols/features/licenses should be provided from day 1)
5.1.1. Should support Static Routing, Default Routing, RIPv2, OSPFv2, BGP, IS-IS
5.1.2. Should support BGP4 routing protocol with CIDR and should have all necessary licenses to enable full features
of BGP protocol
5.1.3. Should support IPv4 NAT feature/service
5.2.1. Should support Static Routing, Default Routing, RIP for IPv6, OSPFv3, BGP for IPv6, IS-IS for IPv6
5.2.3. Router should have full support for dual stack IPv6 on all interfaces and IPv6 over IPv4 tunnelling
5.2.4. Should support NAT64 feature/service.
5.3. Multicast (All protocols/features/licenses should be provided from day 1)
6. QoS Support (All protocols/features/licenses should be provided from day 1)
The router should support Access Control List to filter traffic based on Source & Destination IP Subnet, Source
6.1.
& Destination Port, VLAN, Protocol Type (IP, UDP, TCP, ICMP, etc.) and Port Range etc.
The Router shall support QoS for Traffic Management, class based policing, shaping, CBWFQ, WRED, 802.1p
6.2.
and HQOS (All Ethernet ports)
6.3. Should support IPv6 QoS, ACL, SSH over IPv6

Rev 1.1 28 Jan. 21
Router without POE

7. WAN Protocols (All protocols/features/licenses should be provided from day 1)
7.1. The Router should have WAN protocols like PPP,ML PPP etc.
The router should have at the minimum MPLS features like Layer 2 VPN, Traffic engineering with RSVP-TE,
7.2.
Fast Reroute and Virtual Route Forwarding (VRF) and Layer-3 MPLS-VPN
The Router shall be MPLS Aware and shall work with Service provider provided MPLS services. However In
7.3. case of ONGC wants to build their own MPLS services, Router should have all necessary license and hardware
to act as Customer edge, Provider core and Provider Edge device
8. Encryption (All protocols/features/licenses should be provided from day 1)
Router should support advance generation security protocols (IKEV1/V2) to ensure data confidentiality and
8.1.
integrity. Router should support IPsec Encryption
8.2. Router should provide at least 200 IPSec tunnels (internally)
Other features
9.
(All protocols/features/licenses should be provided from day 1)
Router must have Stateful and VRF aware Firewall and support IPS features natively. The State full firewall
9.1.
should support IPSEC pass through. Firewall and all routing feature should run simultaneously.
The router shall provide MD5 hash authentication mechanism for RIPv2, OSPF, IS-IS, BGP and MPLS routing
9.2.
protocols.
9.3. The router shall support AAA features through Active Directory and/or RADIUS or TACACS+
The router shall have Network Address Translation (NAT). Router should be able to use NAT feature on all the
9.4.
interfaces. All software licenses should be included from day 1
10. Regulatory Compliance
Router shall conform IEC Standards for Safety requirements of Information Technology Equipment.
10.1.
10.2. Command line interface of the router must be in English Language
10.4. Operating Voltage: AC 220V + 5%, 50 Hz
The specifications given are minimum. Any specification/parameter which is better than that specified
11.
above is acceptable.

Rev 1.1 28 Jan. 21
3. L-3 switch
L-3 Switch
1.1. Should be provided with 1+1 or N+1 internal redundant power supply.
L3 Switch should be rack mounted and should have hot swappable fan modules and power supply. All rack
1.2.
mounting accessories to be supplied.
2. L3 Architecture and Memory (Features/Hardware should be provided from day 1)
2.1. Should have preferably 2GB of DRAM
2.3. Switch should have latest supported OS of Enterprise Class.
2.4. Each Switch should have capability to accommodate at least 24 x1/10GE (SFP/SFP+) port in single switch
3. Ports
3.1. Requirement
Equipped with 16 X 1/10 GE (SFP/SFP+) ports. Should support 1GE on BASE-T and 10GE on OFC. (Should
3.1.1.
perform in non-blocking mode). WorkCentre may go for more Ethernet/fibre ports if required.
3.2. Add-on Requirements
The number of ports indicated is minimum. The bidder is free to offer compatible module with higher
3.2.1.
number of ports provided other specifications are met.
4. L3 Performance (should be provided from day 1)
4.1.
Switch should have at least 480 Gbps throughput capacity such as all the ports should operate at non-
blocking mode
5. Layer 2 Protocols and Support (All Protocols/License/Features should be provided from day 1)
5.1. Jumbo Frames support up to 9K Bytes on Gigabit / 10G Ports
Support for broadcast/ multicast/ unicast storm control and ARP storm protection to prevent degradation
5.2.
of switch performance from faulty end stations
The Switch should be able to discover the neighbouring device giving the details about the platform, IP
5.3.
Address, Link connected through etc, thus helping in troubleshooting connectivity problems
Should support port, subnet based 802.1Q VLANs. The switch should support at least 4000 active VLANs.
5.4.
Should support subnet based VLANs.
5.5. The switch should support IEEE 802.1w RSTP and IEEE 802.1s MSTP
5.6. Local Proxy Address Resolution Protocol (ARP)
6. Network Protocols (All Protocols/License/Features should be provided from day 1)
6.1. IPv4 Routing Protocols (All Protocols/License/Features should be provided from day 1)
6.1.1. Should support Static Routing, Default Routing, RIPv2, OSPFv2, BGP
Should support BGP4 routing protocol with CIDR and should have all necessary licenses to enable full
6.1.2.
features of BGP protocol
6.1.3. Support for VRF-Lite or equivalent
6.1.4. Should support DNS, TFTP and NTP protocols
6.2. IPv6 Routing Protocols (All Protocols/License/Features should be provided from day 1)
6.2.1. Should support Static Routing, Default Routing, RIP for IPv6, OSPFv3, BGP for IPv6
6.2.3. Should support both IPv4 and IPv6 routing concurrently; Should have dual stack functionality
6.2.4. Should support DNS, TFTP and NTP protocols
6.2.5. Supported IPv6 features should include: DHCPv6, ICMPv6

Rev 1.1 28 Jan. 21
L-3 Switch
6.3. Multicast (All Protocols/License/Features should be provided from day 1)
6.3.1. Should support IPv4 and IPv6 Multicasting
6.3.2. Should have PIM-SM, PIM-Sparse-Dense mode, Bidirectional PIM, PIM-SSM for IPv4
6.3.3. Should have PIM-SM, PIM-Sparse-Dense mode, Bidirectional PIM, PIM-SSM for IPv6
6.3.4. Should Support IGMP v1, v2 , v3, IGMP Snooping
7. QoS Support (All Protocols/License/Features should be provided from day 1)
7.1. Should support Ingress/Egress Queuing or QoS per port or user
Should be able to collect and limit traffic flows based on MAC Source/ Destination address, IP Source/
7.2.
Destinations address, TCP/UDP port nos etc.
Should support policy based traffic classification based on Type of Service (ToS), IP Precedence mapping,
7.3.
Layer 2/3/4 defined traffic flows, MAC address, VLANs
7.4. The Switch shall support QoS for Traffic Management, class based policing, WRED and 802.1p.
8. Management (All Protocols/License/Features should be provided from day 1)
Switch should be manageable through NMS on per port/switch basis with common interface for
8.1. all manageable devices on the network. Should Support SNMP, RMON/RMON-II, or equivalent SSH V2,
telnet, web management through network management software
Should support port mirroring feature for monitoring network traffic of a particular port/VLAN/group of
8.2.
ports/entire switch
8.3. The switch should support role-based access control to limit access to switch operations
8.4. The switch should support SNMP v1, v2 and V3.
Trivial File Transfer Protocol (TFTP) / SFTP to reduce the cost of administering software upgrades by
8.5.
downloading from a centralized location.
8.6. Version of software for supplied switch should be of latest release, and to support all required features
9. Other features (All Protocols/License/Features should be provided from day 1)
Must have the ability to complete hitless software upgrades with zero interruption to services or data
9.1.
forwarding
The switch should support Access Control List to filter traffic based on Source & Destination IP Subnet, Source
9.2.
& Destination Port, VLAN, Protocol Type (IP, UDP, TCP, ICMP etc) and Port Range etc
Should support integrated security features like DHCP snooping, Dynamic ARP Inspection, IP Source guard
9.3.
etc.
9.4. The switch should support control plane policing to filter the unwanted traffic to fill up the CPU queues
9.5. The Switch Should support SFTP for remote file transfer
9.6. Should Support VRRP Protocol or equivalent
10. Regulatory Compliance from day 1
Switch shall conform to IEC Standards for Safety requirements of Information Technology Equipment.
10.1.
10.2. Command line interface of the Switch must be in English Language
10.4. Operating Voltage : AC 220V + 5%, 50 Hz
11.

Rev 1.1 28 Jan. 21
4. L2 switch – 24 Ports
24 port L2 Switch
1. General Features
Min 24 Port Ethernet 10/100/1000 Mbps (autosensing RJ-45) with all POE ports and 2X10 Gig
1.1. uplinks/Modules. Switch should also support POE+ technology. (Optics for uplink modules are specified
separately). Uplink (SFP+) ports should work simultaneously along with 24 Nos of 1G Base T ports.
1.2. Switch should have Internal Redundant Power supply installed with hot – swappable facility.
1.3. Same switch should also support 1G by replacing 10G uplinks or by adding new modules.
Should have dedicated stacking port. Any of the ports mentioned at Clause 1.1 should not be used for
1.4.
stacking.
1.5. Min DRAM 256 MB and External USB support for uploading OS images and configuration files
1.6. Should be 19'' rack mountable and all accessories for mounting should be provided
2. Performance
2.1. At least 88 Gbps switch fabric with non-blocking mode at full duplex
2.2. Stacking bandwidth of minimum 80Gbps
2.3. Should support at least 4 Switches in one stack
Forwarding rate – at least 90 Mpps. Forwarding rate must be in such a way that all the ports should be in
2.4.
non-blocking mode while operating at full duplex
2.5. Configurable at least 16000 MAC addresses
2.6. Jumbo frames minimum size 9200 – byte
3. Layer-2 Features
3.1. IEEE 802.1Q VLAN encapsulation, at least 1000 VLans should be active. Support for at least 4000 VLAN IDs.
Support for Voice VLAN which will simplify telephony installations by keeping voice traffic on a separate
3.2.
VLAN for easier administration and troubleshooting from day 1
Should have centralized VLAN Management. Switch should support VLAN propagation automatically created
3.3.
on the Core Switches
3.4. Should have spanning-tree enhancements for fast convergence
3.5. Should have all features as per IEEE 802.1d, 802.1s, 802.1w, 802.3ad, 802.3af, 802.3at
3.6. Should have spanning-tree feature to prevent other edge switches becoming the root bridge
3.7. Switch should have features like IGMP snooping v3, IGMP filtering and should have min 500 IGMP Groups
3.8. Should have Link Aggregation Protocol (LACP)
Should support for Detection of Unidirectional Links (in case of fiber cut) and to disable them to avoid
3.9.
problems such as spanning-tree loops.
Switch should be able to discover the neighbouring device giving the details about the platform, IP Address,
3.10.
Link connected through it etc, thus helping in troubleshooting connectivity problems.
Should have feature for storm control to prevent faulty end stations from degrading overall systems
3.11.
performance.
Local Proxy Address Resolution Protocol (ARP) to work in conjunction with Private VLAN Edge to minimize
3.12.
broadcasts and maximize available bandwidth.
Should have Multicast VLAN registration (MVR) to continuously send multicast streams in a multicast VLAN
3.13.
while isolating the streams from subscriber VLANs for bandwidth and security reasons.
4. Network security features
4.1. Should have IEEE 802.1x to allow dynamic, port-based security, providing user authentication
4.2. Port-based ACLs for Layer 2 interfaces to allow application of security policies on individual switch ports.
SSHv2 and SNMPv3 to provide network security by encrypting administrator traffic during Telnet and SNMP
4.3.
sessions.

Rev 1.1 28 Jan. 21
24 port L2 Switch
Bidirectional data support on the Mirrored port to allow the intrusion detection system (IDS) to take action
4.4. when an intruder is detected. Also support for remote mirroring capability which helps administrators to
remotely monitor ports in a Layer 2 switch network from any other switch in the same network.
RADIUS authentication to enable centralized control of the switch and restrict unauthorized users from
4.5.
altering the configuration.
Dynamic ARP Inspection or equivalent which can ensure user integrity by preventing malicious users from
4.6.
exploiting the insecure nature of the ARP protocol.
DHCP snooping to allow administrators to ensure consistent mapping of IP to MAC addresses. This can be
4.7. used to prevent attacks that attempt to poison the DHCP binding database, and to rate-limit the amount of
DHCP traffic that enters a switch port.
4.8. Port security to secure the access to an access or trunk port based on MAC address.
Multilevel security on console access to prevent unauthorized users from altering the switch configuration
4.9.
using local database or through an external AAA Server.
Spanning tree feature to shut down Spanning Tree Protocol enabled interfaces when BPDU’s are received
4.10.
to avoid accidental topology loops.
4.11. Security ACL entries – At least 1000.
IEEE 802.1AE which can provide MAC layer encryption over wired networks using out-of-band methods for
4.12.
encryption keying.
5. Quality of Service (QoS) & Control
5.1. Standard 802.1p CoS and DSCP
5.2. 8 egress queues per port to enable differentiated management of up to 8 traffic types across the stack.
5.3. Weighted tail drop (WTD) or equivalent to provide congestion avoidance
5.4. Strict priority queuing mechanisms
Future support for feature which will provide rate limiting based on source and destination IP address,
5.5. source and destination MAC address, Layer 4 TCP and UDP information, or any combination of these fields,
using QoS ACLs (IP ACLs or MAC ACLs), class maps, and policy maps.
6. Management
6.1. Command Line Interface (CLI) support for configuration & troubleshooting purposes.
For enhanced traffic management, monitoring, and analysis, upto four RMON groups (history, statistics,
6.2.
alarms, and events) must be supported.
6.3. Domain Name System (DNS) support to provide IP address resolution with user-defined device names.
FTP/ Trivial File Transfer Protocol (TFTP) to reduce the cost of administering software upgrades by
6.4.
downloading from a centralized location.
Network Timing Protocol (NTP) based on RFC 1305 to provide an accurate and consistent timestamp to all
6.5.
intranet switches.
SNMP v1, v2c, and v3 and Telnet interface support to deliver comprehensive in-band management, and a
6.6.
CLI-based management console to provide detailed out-of-band management.
6.7. RMON I and II standards
6.8. SNMPv1, SNMPv2c, and SNMPv3
7. Other
Should have IPv4 and IPv6 Layer 3 support which includes static routing, Default Routing, Layer-3
7.1.
redundancy (VRRP) or similar. The switch shall have Dual stack mode to run both IPv4 & IPv6 simultaneously.
7.2. Should have latest OS supported on the device.
All the specified features/parameters/certifications must be available on the Technical Bid opening date.
7.3. Features /parameters /certifications proposed to be available in near future / on roadmap shall not be
considered.
8.

Rev 1.1 28 Jan. 21
5. L-2 switch - 48 ports

48 port L2 Switch
S
Minimum Technical Specifications
No
1. General Features
Min 48 Port Ethernet 10/100/1000 Mbps (autosensing RJ-45) with all POE ports and 2X10 Gig
1.1. uplinks/Modules. Switch should also support POE+ technology. (Optics for uplink modules are specified
separately). Uplink (SFP+) ports should work simultaneously along with 48 Nos of 1G Base T ports.
1.2. Switch should have Internal Redundant Power supply installed with hot – swappable facility.
1.3. Same switch should also support 1G by replacing 10G uplinks or by adding new modules.
1.4. Should have dedicated stacking port. Any of the ports mentioned at Clause 1.1 should not be used for stacking.
1.5. Min DRAM 256 MB and External USB support for uploading OS images and configuration files
1.6. Should be 19'' rack mountable and all accessories for mounting should be provided
2. Performance
2.1. At least 136 Gbps switch fabric with non-blocking mode at full duplex
2.2. Stacking bandwidth of minimum 80Gbps
2.3. Should support at least 4 Switches in one stack
2.4.
Forwarding rate – at least 130 Mpps. Forwarding rate must be in such a way that all the ports should be in
non-blocking mode while operating at full duplex
2.5. Configurable at least 16000 MAC addresses
2.6. Jumbo frames minimum size 9200 – byte
3. Other Specifications are same as that for 24 port L-2 switch
6. Accessories for the ports of switches

S
Minimum Technical Specifications
No
1. SFP+ Long Range Modules
1.1. Should be LC Connector type
1.2. Module with one LC-LC Single mode 50/125 micron, OM3, Duplex Patch Cord 3 Metre
1.3. Distance supported must be greater than or equal to 5 Kilometres on OM3 Cable standard
2. SFP+ Short Range Modules
2.1. Should be LC Connector type
2.2. Module with one LC-LC multi-mode 50/125 micron, OM3, Duplex Patch Cord 3 Metre
2.3. Distance supported must be greater than or equal to 300 meters on OM3 Cable standard
3. Stacking Module
3.1.
Module should reside inside the dedicated slot provided in the switch; Stacking Cable of length 1 metre. OEM
for stacking module should be the same as that of switches.
10 | Standard Specs for Network Devices © ONGC

Standard Specifications For Network Devices

Uploaded by

Copyright:

Available Formats

You might also like

Standard Specifications For Network Devices

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Standard Specifications For Network Devices

Uploaded by

Copyright:

Available Formats

Corporate Infocom Services

Standard Specifications for

1. Router with POE capability built-in

2| Standard Specs for Network Devices © ONGC

Router with POE

3| Standard Specs for Network Devices © ONGC

2. Router without POE capability

4| Standard Specs for Network Devices © ONGC

Router without POE

5| Standard Specs for Network Devices © ONGC

6| Standard Specs for Network Devices © ONGC

7| Standard Specs for Network Devices © ONGC

8| Standard Specs for Network Devices © ONGC

9| Standard Specs for Network Devices © ONGC

5. L-2 switch - 48 ports

3. Other Specifications are same as that for 24 port L-2 switch

6. Accessories for the ports of switches

10 | Standard Specs for Network Devices © ONGC

You might also like