Comply
|
5,101
|
If a circuit is not fully utilizing the CIR bandwidth, then the unused portion must be available as burst bandwidth to other circuits.
|
Comply
|
5,102
|
System must be capable of wire speed Traffic Management implementation.
|
Comply
|
5,103
|
System must be capable of providing COS treatment for up to 1,000 logical interfaces on 10 G ports. This includes Policers and Shapers.
|
Comply
|
5,104
|
System must be capable of providing COS treatment for up to 2,000 logical interfaces on 40 G ports. This includes Policers and Shapers
|
Comply
|
5,105
|
System must be capable of providing COS treatment for up to 4,000 logical interfaces on 100 G ports. This includes Policers and Shapers
|
Comply
|
5,106
|
Please provide information on your available buffer size and buffer allocation to both physical and logical interfaces.
|
Comply
|
5,107
|
Please indicate the number of policy maps on both ingress and egress supported should be provided
|
Comply
|
5,108
|
Queues : Support the capability to assign traffic to any of the possible 8 queues per physical port. Explain the capability to assign traffic to any of the possible 8 queues per physical port. What criteria is the assignment based on? Is it user definable? What are the possible definitions?
|
Comply
|
5,109
|
Support for WRED, Class-Based WFQ, and LLQ mechanisms.
|
Comply
|
5,110
|
User configurable to Support assignment of traffic of more than one class per queue.
|
Comply
|
5,111
|
Support for One alternate priority based low delay/jitter queue. The algorithm is intended to produce a structure by where the data held within the non priority queue is not completely starved for bandwidth, thus allowing the TCP based streams to survive during times of congestion while introducing as little delay variation upon the priority queue as possible also the ability to limit any and all transmission queues.
|
Comply
|
5,112
|
Support to serve all classes without bandwidth reservations [or below EF classes] with WFQ.
|
Comply
|
5,113
|
Support at least 1 EF and 7 AF classes. How many EF and AF classes are supported?
|
Comply
|
5,114
|
Platform shall supported a class based drop mechanism that uses configurable relative class weights within each queue, number of queues ranging from one to eight when using EXP and PREC values. The drop mechanism must be based on average queue depth with the ability to tune that relative average in order to accommodate bursty customer traffic patterns.
|
Comply
|
5,115
|
Support for the class-full shaping, policing, and queuing mechanism should not be an absolute value instead a function of the line capacity etc.
|
Comply
|
5,116
|
Support QoS packet coloring: default 0, ToS bit setting on all packets, EXP setting on labels on both inbound and outbound interfaces
|
Comply
|
5,117
|
Support Queuing per logical interface. 8 queues per Logical Interface. How many logical interfaces can be supported for each interface type?
|
Comply
|
5,118
|
Support Queuing per Physical interface. 8 queues per Physical Interface.
|
Comply
|
5,119
|
The platform shall support “Marking per logical interface”.
|
Comply
|
5,120
|
The platform shall support Full line rate forwarding at 64 byte packet sizes with QoS mechanism enabled
|
Comply
|
5,121
|
The platform shall support RFC 2597 (AF PHB Group) and 3246 (An Expedited PHB). In the case of partial support of the RFCs, please indicate what is supported and what is not supported.
|
Comply
|
5,122
|
Support ability to Classify Frames by EXP and TOS QoS as well as DSCP per logical interface. [Ability to assign EXP, TOS and DSCP to any queue].
|
Comply
|
5,123
|
Describe support for multiple classes of traffic from separate physical and logical sources bound for the same logical/ and or physical interface that traverse the systems fabric as well as hair pinning on the same card. Describe the support for class-full scheduling across the fabric and the flexibility to fine tune available to the network designer.
|
Comply
|
5,124
|
The platform must support the capability to support Hashing over Links in a LAG bundle based on: S/D IP address (if IP payload), S/D MAC Address (If non IP payload), MPLS Label- 5 lables labels deep. Describe any additional capabilities to load balance traffic flows over links in a LAG bundle.
|
Comply
|
5,125
|
The platformm must support a Preference/Precedence/COS indicator that is used internally (e.g., across the switch fabric) that provides intelligent discard if congestion results between interface COS Application points.
|
Comply
|
5,126
|
Describe the capability to assign frames to TE-Tunnels based on EXP bit settings.
|
Comply
|
5,127
|
When your equipment performs a P-Router function it must be able to optionally support the use .1p bits of the Ethernet Frame, in addition to the MPLS EXP bits, for COS treatment.
|
Comply
|
