Procurement Of Routers Switches Sfps And Other Items Through Gem - Outer Type-I As Per Technical Specifications Of Sor‐ - Router Should Support Minimum 1G / 10G Sfp+ Ports ( Including 8X10g Sfp+ Module ) And 4 Number Of 100G Interface ( Excluding Xfp / Sfp / Qsfp ) From Day One. 2 Total Throughput ( Full Duplex ) : Minimum 280 Gbps 3 Mac Table Size : 64K 4 Ipv4 Rib / Fib : Minimum 1M / 128K 5 Ipv6 Rib / Fib : Minimum 512K / 32K 6 Mpls Labels : Minimum 32K 7 Label Stack : 5 8 L2 / L3 Vpn Vrf : Minimum L2 1000, Minimum L3 256 9 Support Of Number Of Queues Per System : Minimum 4K 10 Number Of Vlan Support : 1000 11 Operating Temperature : ( 0 To 40 Degree C Or Better ) 12 Storage Temperature : ( -10 To 60 Degree C Or Better ) 13 Router Can Be Of Either Modular / Fixed Type And Shall Have Modular Operating System Where It Shall Support Individual Restart Of Critical Processes Without Affecting Other Processes Or Rebooting The Entire Operating System. 14 All 10G Interfaces Should Support Lr, Er And Zr. 15 Router Shall Have Option Checking Configuration Before Committing And Option Of Rolling Back To At Least Five Configurations. 16 Router Should Have Redundant Dc ( With The Operating Range Of -40 To -72 Vdc ) Power Supplies 17 Digital Optical Monitoring ( Dom ) Should Be Supported, Optics Information Retrievable Including Rx / Tx-Power, Threshold-Monitoring / Alarming, Inventory. 18 It Shall Support Role Based Privileges For The System Access And Radius Authentication For The System Admin. 19 The Router Should Have A Console Or Out-Of-Band Management. 20 Alerts For Environmental Or Other Hardware Based Alarms Should Be Visibly Implemented On The Chassis. 21 All Interfaces Shall Support Services Like L2vpn, L3vpn, Vpls And Multicast Vpn For Both Ipv4 And Ipv6 22 The Router Should Have Mechanism To Protect Itself From Ddos Attack. 23 The Router Should Be Ipv6 Ready From Day One. 24 The Router Should Support Filtering Based On Different Parameters Like: Src Ip, Dst Ip, Src Port, Dst Port, Protocol Etc 25 The Router Should Support Netflow, Jflow Or Equivalent 26 The Router Should Support Ip Sla Or Rpm ( Or Equivalent ) For Performance Measurements, It Should Also Support Monitoring Of Ip Sla / Rpm ( Or Equivalent ) Probes Using Snmp Polling ( Oem Has To Provide Snmp Mib Information ) 27 Shall Support Qos, Option Of Traffic Shaping Per Interface Based. 28 Shall Support Following Class Of Service Features: A ) Classification, Policing, Marking, Shaping, Filtering B ) Manage Congestion Using A Weighted Random Early Detection ( Wred ) Algorithm C ) Rfc 2474, Definition Of The Differentiated Services Field In The Ipv4 And Ipv6 Headers D ) Single Rate Three Color Policer Rfc 2697 E ) Rfc 2698, A Two Rate Three Color Policer F ) Congestion Management Through Cbwfq, Round-Robin Or Equivalent, Wfq Or Equivalent G ) Rfc 2597, Assured Forwarding Phb Group H ) Rfc 2598, An Expedited Forwarding Phb I ) Router Should Be Able To Classify Based On 802.1 Ad, 802.1 P, Exp And Dscp Bits J ) The Router Shall Support Traffic Interface Mirroring In Both Ingress & Egress Directions For Both Ipv4 & Ipv6 29 The Router Shall Support Provision For Event Based Scripts That Shall Be Capable Of Performing Actions Based On Certain Triggers 30 The Router Shall Support Aggregated Ethernet And It Shall Be Possible To Bundle Upto 16 Links. 31 Shall Support Following Mpls Features A ) Ldp And Rsvp Signalling B ) Rfc 5036, Ldp Specification C ) Rfc 3212 Or Constraint-Based Lsp Setup Using Ldp D ) Rfc 3215, Ldp State Machine E ) Rfc 3478, Graceful Restart Mechanism For Ldp F ) Rfc 2858, Multiprotocol Extensions For Bgp-4 G ) Rfc 3063, Mpls Loop Prevention Mechanism H ) Rfc 3031, Multiprotocol Label Switching Architecture I ) Rfc 3032, Mpls Label Stack Encoding J ) The Router Should Be Able To Do Load-Balancing Over Multiple Equal Cost Mpls Lsp 32 The Router Shall Support Mpls Fast Reroute Both Link Protection And Node Protection. 33 Mpls Ping, Mpls Trace Route 34 Fast Reroute Extensions To Rsvp-Te For Lsp Tunnels 35 The Router Shall Support Of Sync-E & Ptp Technology ( License Price To Be Quoted Separately ) 36 Shall Support Mpls Based Vpn Services A ) L3vpn, L2vpn ( Kompella Bgp / Martini Ldp ) , B ) Internet Draft, Draft-Ietf-L2vpn-Vpls-Bgp-08.Txt, Virtual Private Lan Service ( Vpls ) Using Bgp For Auto-Discovery And Signaling C ) Rfc 4762 Virtual Private Lan Service ( Vpls ) Using Label Distribution Protocol ( Ldp ) Signaling D ) Next Generation Mvpn ( P2mp ) Based On ( Draft-Ietf-13Vpn-2547Bis-Mcast-01.Txt ) & Mvpn ( Draft-Rosen-Vpn-Mcast ) . 37 The Router Shall Support The Following Routing Features A ) Bgpv4, Bgp Confederations And Route Reflector B ) Dynamic Host Configuration Protocol ( Dhcp ) C ) Rfc 3101, The Ospf Nssa Option D ) Rfc 2328, Ospf Version 2 E ) Rfc 3623, Ospf Graceful Restart F ) Rfc 3630, Traffic Engineering ( Te ) Extensions To Ospf Version 2 G ) Rfc 1195, Use Of Osi Is-Is For Routing In Tcp / Ip And Dual Environments H ) Rfc 2104, Hmac: Keyed-Hashing For Message Authentication I ) Rfc 2973, Is-Is Mesh Groups J ) Rfc 3358, Optional Checksums In Is-Is K ) Rfc 3359, Reserved Type, Length And Value ( Tlv ) Code Points In Is-Is L ) Rfc 3373, Three-Way Handshake For Is-Is Point-To-Point Adjacencies M ) Rfc 5305, Is-Is Extensions For Traffic Engineering N ) Rfc 3847, Restart Signalling For Is-Is O ) Rfc 3590, Source Address Selection For Multicast Listener Discovery Protocol P ) Igmp V2 And V3 As Described In Rfc 2236 And Rfc 3376 With Igmp Routing Policies To Filter Igmp Requests. 38 The Router Shall Support Virtual Router Redundancy Protocol ( Vrrp ) As Per Ietf Rfc 3768 39 Router Shall Support Snmp V2 / V3 And Ntp 40 Shall Support Bfd For Both Single Hop And Multihop Sessions 41 Shall Support The Following Oam Features And Actions Such As Syslog / Link Down Should Be Configurable On Oam Event Trigger: A ) 802.3Ah B ) 802.1Ag C ) Y.1731 42 Shall Support Multi-Chassis Lag 43 Ipv6 Features A ) Ipv6 Ping B ) Ipv6 Trace Route C ) Ospf V3 D ) Is-Is E ) Vrrpv3 F ) Ipv6 Cos ( Classification & Rewrite, Scheduling Based On Tc ) G ) Ipv6 Acl H ) 6Pe And 6Vpe 44 Multicast Feature: It Shall Support Following: A ) It Shall Support Igmp Snooping V2 / V3 B ) The Router Shall Support Pim Sparse Mode, Rfc 4601 ( Optional ) C ) Rendezvous Point ( Rp ) - Ability To Be Configured As An Rp D ) Rfc 3569, Source Specific Multicast ( Ssm ) E ) Rfc 2365, Administratively Scoped Ip Multicast F ) Rfc 3446, Anycast Rendezvous Point ( Rp ) Mechanism Using Protocol Independent Multicast ( Pim ) And Multicast Source Discovery Protocol ( Msdp ) . G ) Rfc 3618, Multicast Source Discovery Protocol ( Msdp ) . 45 The Proposed Router Should Be Nebs Level 3 Compliant. Nebs Certification Is Not Required For Pma. However, Oem Has To Produce Certificate From Standard Lab Approved Or Authorized By Govt. Of India That The Supplied Products Are Equivalent To Nebs And Meet All Standard And Specification Of Nebs. 46 The Device Should Comply To The Following Safety Standards A ) En 55022 Class A Emissions ( Europe ) B ) Fcc Class A ( Usa ) Radiated Emissions C ) Ul 60950-1 Information Technology Equipment – Safety D ) En 60825-1 Safety Of Laser Products E ) En-61000-4-11 Voltage Dips And Sags F ) Ets-300386 Electromagnetic Compatibility Requirements G ) The Device Will Conform To The Following En / Iec Standard: I. 61000-4-2 – Esd Ii. 61000-4-3 Radiated Immunity Iii. 61000-4-4 – Eft Iv. 61000-4-5 – Surge V. 61000-4-6 – Low Frequency Common Immunity Devices Shall Support Following For Provisioning ( A ) Use Netconf ( Rfc 6241, Rfc 6242, Rfc 5277 ) ( B ) Rest Based Crud Operations For Configuration And Management. ( C ) Web Services Based Operations For Configuration And Management 49 The Offered Devices Must Support Api / Nbis For Auto Discovery Of Services And Physical & Logical Topology 50 Telemetry Function: It Shall Support Following: A ) The Router Should Support Telemetry Based On Push Model For Monitoring Network Devices B ) The Router Should Support Various Software Models / Sensors For Capturing Different Health Parameters From The Devices C ) The Router Should Support Sending Telemetry Data To Multiple Consumers Simultaneously D ) The Router Shall Support Gpb / Grpc / Kafka Encoding For Telemetry Data E ) The Software Model / Sensors Should Be Based On Either Yang, Xml Or Open Config F ) The Solution Shall Use Either Udp Or Grpc For Transport Of Telemetry Data G ) The System Should Support Streaming Granularity Of Atleast 10 Sec H ) The Router Shall Have The Ability To Interact With Open Standard Based Tools I ) The System Should Support Rest Api For Communication With Third Party Tools And Applications J ) Enabling Telemetry Should Not Have Any Adverse Impact On The Performance Of The Device / Router K ) Some Of The Streaming Models / Sensors The Router Should Support Are: System Chassis Environment Line Card Utilization ( Memory , Processor, Qos, Temp, Port Utilization ) , Errors Counters Controller Card Sensors ( Memory, Cpu, Temp Etc ) Fabric Statistics Arp Table State Routing Prefix Information Interface Interface Statistics ( Physical And Logical Interfaces ) Interface Optical Diagnostic Congestion And Latency Filter Statistics Protocol Bgp Peer Information Isis State, Interface, Adjacency Statistics, Lsdb Isis Spring / Segment Routing Statistics Rsvp Interface Statistics Lsp Statistics Lsp Event Export, Experimental Ip Sla / Rpm ( Or Equivalent ) Reporting Page 15 Of 62 Segment Routing Statistics Dhcp Statistics 51 Router Should Support Dual Image / Partition With Usb Flash Drive Booting Option For Os Recovery 52 Router Should Support Jumbo Frame. 53 Router Should Support Port Mirroring 54 Router Should Support Security Features Of Broadcast / Mulitcast / Unicast Storm Control. 55 Router Should Comply To Following Temperature Performance Parameters: I. Operating Temperature: 0 To 40 Degree C Or Better Ii. Storage Temperature: -10 To 60 Degree C Or Better 56 Routers Should Support Following Metro Ethernet Features: I. Itu-T G.8032 Ethernet Ring Protection Designed For Loop Protection Or Alternate Mechanism To Achieve Ring Protection In Less Than 50 Ms. Ii. Should Support Multiple Ring Up To 8 Ring ( Main And Sub Ring ) Protection Failover With In 50 Ms Or Itu-T G.8032 V2. 57 The Operating System Of The Routers Category / Series / Family Should Be Mef-9 / 14 Or Ce ( Carrier Ethernet ) Certified. 58 The Router Shall Be Designed For Continuous Operations With Dual Fan System. 59 Router Should Support Cfm And Lfm Alarms. 60 Shall Support Hqos, Option Of Traffic Shaping Per Vlan Based. I. Shall Support At Least 4K Queues. Ii. Per-Vlan Policing. Iii. Per-Vlan Rewrite Iv. Per-Vlan Two-Rate Tri-Color Marking. V. Per-Vlan Classification Vi. Per-Vlan Filtering 61 Support For P And Pe Router Functionality For Mpls On The Same Router Simultaneously And On All The Interfaces. 62 Router Shall Support E-Line Or E-Lan Mef Standards. 63 Routers Should Be Rack Mountable To Fit Into A Standard 19-Inch Rack 64 Oem Shall Ensure That Use Of Third Party Optics Shall Not Be Explicitly Blocked On The Router. Router Must Support All Msa Complied Optics Available In Market. 65 Segment Routing I Router Should Be Able To Support Sr Standards On Ipv6 Whenever It Is Firmed Upt Without Any Cost To Rcil. Ii The Router Should Support Sr-Mpls Dataplane And Protocols Ospf, Is-Is And Bgp Segment Routing Extensions Iii Traffic Steering Of Sr Policies With Autoroute Include And Segment Routing Ti-Lfa Srlg Protection Iv Lsp Ping, Trace-Route, Pseudo Wire Ping Over Segment Routing, Trace Route For Binding-Sid V Mpls-Ldp Interworking With Sr-Isis And Sr-Ospf Vi Ti-Lfa With Igp ( Link, Node, Local Srlg, Remote Srlg Protection ) Vii Controller Instantiated Sr Policy ( Pcep, Bgp ) And Sr Policy Based On On Demand Next Hop Viii Router Should Have Capability To Calculate Bandwidth Based Path Using Centralized Controller. Ix Shall Support Sr And Mpls ( Ldp ) Interworking Mapping Server X The Router Shall Support Dynamic Point-To-Point Interface Latency Performance Measurement. The Measurement Must Be Integrated In The Igp And Bgp Ls For Sdn Controller Analysis. Xi Label Distribution Protocol And Segment Routing Should Coexist And There Should Support Option To Prefer Ldp Over Segment Routing. Page 16 Of 62 66 Evpn Features I Router Should Have Support Of Ethernet Vpn ( Evpn With Single Homing, Multi Homing Ii Router Should Have Support Of Following Features On Evpn: Evpn-Irb, Evpn Vpws, Evpn Vpws Preferred Path Over Sr-Te Policy 67 I ) Specification Router To Support Gre Tunnels ( Rfc 2784 ) .
