Router Solution RFP - Attachment 6.1.3.2 Hardware Attributes and

advertisement
Router Solution RFP - Attachment 6.1.3.2 Hardware Attributes and Performance
If additional space is required to answer the questions below, use a Word document and list the section
number of the question.
SECTION
QUESTION
6.1.3.2.1
Are you NEBS compliant?
6.1.3.2.2
If your answer to the above question is yes, at
what NEBS level are you compliant?
6.1.3.2.3
What is the latency through your product?
6.1.3.2.4
Does your platform support DC power?
6.1.3.2.5
Does your platform support AC power?
6.1.3.2.6
What is the maximum throughput of your
system at 64 byte frames?
6.1.3.2.7
Does your platform support pluggable fiber /
fixed copper software selectable ports?
6.1.3.2.8
What is the receive sensitivity of your supplied
optics?
6.1.3.2.9
What is the transmit power of your supplied
optics?
6.1.3.2.10
What is the maximum distance your design
supports?
6.1.3.2.11
Using the Interface support spreadsheet,
document all interface cards your platform
supports. (See “Integrated Support Matrix”
attachment.)
6.1.3.2.12
Do you currently ship 40G products? If not what
is your roadmap?
6.1.3.2.13
Do you currently ship 100G products? If not
what is your roadmap?
6.1.3.2.14
Does this solution provide fault tolerance for the
OS?
VENDOR RESPONSE
Page | 1
Router Solution RFP - Attachment 6.1.3.2 Hardware Attributes and Performance
6.1.3.2.15
Does this solution provide fault tolerance for the
management?
6.1.3.2.16
Are power supplies hot swappable?
6.1.3.2.17
Are interface modules hot swappable?
6.1.3.2.18
Are the processor boards hot swappable?
6.1.3.2.19
Can your product be configured with a
command line interface?
6.1.3.2.20
Can your product be configured with a GUI
interface?
6.1.3.2.21
Can your product be configured using telnet?
6.1.3.2.22
Can your product be configured using SSH?
6.1.3.2.23
If your answer to the above question is yes,
which versions of SSH do you support?
6.1.3.2.24
Can your product be configured using HTTP?
6.1.3.2.25
Can your product be configured using HTTPS?
6.1.3.2.26
Is there a console port on your device that can
be accessed to configure the device?
6.1.3.2.27
Is there proprietary client software required to
configure your product?
6.1.3.2.28
Are invalid access attempts logged?
6.1.3.2.29
How are security logs accessed?
6.1.3.2.30
Can your product be configured to force user
authentication?
6.1.3.2.31
Can authentication be integrated with native MS
Active Directory?
6.1.3.2.32
Can authentication be integrated via LDAP?
6.1.3.2.33
Can authentication be integrated with TACACS?
Page | 2
Router Solution RFP - Attachment 6.1.3.2 Hardware Attributes and Performance
6.1.3.2.34
Can authentication be integrated with RADIUS?
6.1.3.2.35
How is access gained if authentication servers
are unavailable?
6.1.3.2.36
Can your product be configured for
configuration authorization?
6.1.3.2.37
If your answer to the above question is yes, can
authorization be integrated with active
directory?
6.1.3.2.38
What is the maximum number of IPv4 Routes in
FIB?
6.1.3.2.39
What is the maximum number of IPv4 Routes in
RIB?
6.1.3.2.40
What is the maximum number of IPv6 Routes in
FIB?
6.1.3.2.41
What is the maximum number of IPv4 Routes in
RIB?
SECTION QUESTION AND VENDOR RESPONSE
6.1.3.2.42 If your answer to 6.1.3.2.36 is ‘YES’, how is access gained if authentication
servers are unavailable?
Page | 3
Router Solution RFP - Attachment 6.1.3.2 Hardware Attributes and Performance
SECTION QUESTION AND VENDOR RESPONSE
6.1.3.2.43 Explain out-of-band management options.
SECTION QUESTION AND VENDOR RESPONSE
6.1.3.2.44 Explain in-band management options.
Page | 4
Router Solution RFP - Attachment 6.1.3.2 Hardware Attributes and Performance
SECTION QUESTION AND VENDOR RESPONSE
6.1.3.2.45 Explain how your product can provide path protection.
SECTION QUESTION AND VENDOR RESPONSE
6.1.3.2.46 Provide MTBF for all components in the proposed solution.
Page | 5
Router Solution RFP - Attachment 6.1.3.2 Hardware Attributes and Performance
SECTION QUESTION AND VENDOR RESPONSE
6.1.3.2.47 Please provide power consumption requirements for all proposed
hardware. The response must include nominal and maximum AMPS.
SECTION QUESTION AND VENDOR RESPONSE
6.1.3.2.48 Please provide heat dissipation qualities for all proposed hardware
(BTU/Hr).
Page | 6
Router Solution RFP - Attachment 6.1.3.2 Hardware Attributes and Performance
SECTION QUESTION AND VENDOR RESPONSE
6.1.3.2.49 Please provide the operating temperature and humidity ranges for all
proposed hardware.
SECTION QUESTION AND VENDOR RESPONSE
6.1.3.2.50 Please provide device dimensions for all proposed hardware.
Page | 7
Router Solution RFP - Attachment 6.1.3.2 Hardware Attributes and Performance
SECTION QUESTION AND VENDOR RESPONSE
6.1.3.2.51 Does your product use G.709? If no, please explain.
SECTION QUESTION AND VENDOR RESPONSE
6.1.3.2.52 Explain the power supply fault tolerance options.
Page | 8
Router Solution RFP - Attachment 6.1.3.2 Hardware Attributes and Performance
SECTION QUESTION AND VENDOR RESPONSE
6.1.3.2.53 Explain the fault tolerance options for processor boards.
SECTION QUESTION AND VENDOR RESPONSE
6.1.3.2.54 Explain interface fault tolerance options.
Page | 9
Router Solution RFP - Attachment 6.1.3.2 Hardware Attributes and Performance
SECTION QUESTION AND VENDOR RESPONSE
6.1.3.2.55 Are there any modules that are not hot swappable? If yes, explain.
SECTION QUESTION AND VENDOR RESPONSE
6.1.3.2.56 Explain design limitations of your interfaces. Example: NNI interfaces vs.
UNI interfaces.
Page | 10
Router Solution RFP - Attachment 6.1.3.2 Hardware Attributes and Performance
SECTION QUESTION AND VENDOR RESPONSE
6.1.3.2.57 What is the per-slot capacity of you platform?
SECTION QUESTION AND VENDOR RESPONSE
6.1.3.2.58 Please list and describe all available cards for your platform.
Page | 11
Download