
JITC Memo, JTE, Special Interoperability Test Certification of the Avaya Ethernet Routing
Switch (ERS)5500 Series with Release 6.2.100.073
4
Table 3. SUT CRs and FRs Status (continued)
CR/FR
ID
Capability/ Function Applicability
1
UCR
Reference
Status Remarks
3
NM Requirements
Configuration Control
Required 5.3.1.6.1 Met
Operational Changes
Required 5.3.1.6.2 Met
Performance Monitoring
Required 5.3.1.6.3 Met
Alarms
Required 5.3.1.6.4 Met
Reporting
Required 5.3.1.6.5 Met
4
Engineering Requirements
Physical Media
Required 5.3.1.7.1 Met
Traffic Engineering
Required 5.3.1.7.3 Met
5
Configured with four
queues, each set to
25% of total
bandwidth.
Availability
Required 5.3.1.7.6 Met
100% availability
during test. Met by
vendor LoC
Redundancy
Conditional 5.3.1.7.7 Met
5
MPLS
MPLS Requirements
Conditional 5.3.1.8.4.1 Not Tested
6
MPLS VPN Augmentation to VLANs
Conditional 5.3.1.8.4.2 Not Tested
6
6
IPv6 Requirements
Product Requirements
Required 5.3.5.4
Partially
Met
7
NOTES:
1. The annotation of ‘required’ refers to a high-level requirement category. The applicability of each sub-requirement is provided in
Enclosure 3. The system under test does not need to provide conditional requirements. However, if a capability is provided, it must
function according to the specified requirements.
2. The ERS5520 and ERS5510 were unable to remark IPv6 DSCP values. This discrepancy was adjudicated by DISA on 4 October
2011 as having a minor operational impact based on DISA change in requirements for remarking of DSCP values on the access layer is
no longer required. The test equipment recorded that the higher prioritized traffic was properly queued above lower prioritized best effort
traffic.
3. Refers to IA requirements described in reference (c) Section 5.4. Detailed IA requirements are included in Reference (e).
4. This requirement was verified and met using simulated voice, video, and data traffic in an operational emulated environment to meet
E2E requirements. The SUT must be deployed in accordance with deployment guide and engineering guidelines provided in UCR
5.3.1.4.
5. This requirement was met with the following stipulations: It is the site’s responsibility to configure the SUT in a manner which meets
the engineering requirements listed in Section 11.2 d. of Enclosure 2 and that does not create a single point of failure which could impact
more than 96 C2 users. The SUT did not meet the stack failover requirement with Brocade when the LACP links connected to Unit 1 and
Unit 2 and a failover occurred. This discrepancy was adjudicated by DISA on 4 October 2011 as having a minor impact based on vendor
including this discrepancy in the deployment guide.
6. MPLS was not tested and is not certified for joint use. MPLS is conditional and; therefore, not required for a Core, Distribution, or
Access switch.
7. The SUT does not support scope address architecture zones in accordance with RFC 4007. This discrepancy was adjudicated by DISA
as having a minor impact with vendor POA&M of 1 April 2012.
LEGEND:
C2 Command And Control
CR Capability Requirement
DISA Defense Information Systems Agency
E2E End-to-End
FR Functional Requirement
IA Information Assurance
ID Identification
IPv6 Internet Protocol version 6
LACP Link Aggregate Control Protocol
LoC Letter of Compliance
MPLS Multiprotocol Label Switching
NM Network Management
POA&M Plan of Action and Milestones
QoS Quality of Service
RFC Request for Comment
SUT System Under Test
UCR Unified Capabilities Requirements
VLAN Virtual Local Area Network
VPN Virtual Private Network
Kommentare zu diesen Handbüchern