Specifications

©
2002, David K. Z. Harris
27
Pg. 27
© 2002
David K. Z. Harris
Evaluating the Hardware
Ø Cost per port is just one metric
Ø Security features may be needed
² Do you need SSL or SSH access?
• What version(s)? Interoperability…
² How often, how many, how long?
Ø Size and port density
² Rack space may be valuable
² How many ports do you need?
² Wiring, adapters, patch panels
While many Console Servers now have SSH access capability, SSH V.2
capability has been slow in coming.
Most vendors blanch when you tell them you want to make 32 simultaneous
SSH connections to their Console Server, and they’ll ask “For how long?”,
indicating that their SSH may have memory leaks, or SSH sessions may
severely tax the performance of the device. (I haven’t done a large-scale test,
with 32 busy async devices connected to a console server, using SSH to
connect to all of the ports, but I also haven’t found a vendor who wants me to
put their gear up to that test, either.)
SSL access is also starting to be offered by vendors, but then you need to
manage certificates.
None of my vendors wanted to discuss where their SSH and SSL core code
have come from. But, few Console Server devices have been listed on the
SANS vulnerability alerts…
Interoperability between your Console Server hardware and your standard
Operating Systems should be investigated, and tested. What will you do if an
SSH upgrade or patch breaks the interoperability with your Console Server
hardware? How soon can your vendor(s) restore communication?
You may want to consider buying more console servers, and deploying them in
your racks, instead of using patch panels and infrastructure wiring to keep the
console servers centrally located. Investigate your infrastructure costs, both
parts and labor!