Because:
- Remote capability is #1.
- Twinax is unreliable. Baluns, someone removing a terminal midstream,
someone leaving a stack of papers on the space bar when turning it on and
then resetting the address, IBM having to come in and upgrade the firmware
on several 3196's, switches breaking like crazy on those 3196's, replacing
a twinax with a different model and it not autoconfiguring thus you have
no console and a host of other failures.
- How do you copy/paste from a twinax terminal into word or email
something that appears on it? ESPECIALLY the oddball stuff most likely to
be seen when you are in restricted state on your system console?
- The fact that power7's drop twinax as an option.
- 10 lpars would require 10 twinax cards - that's a lot of wasted real
estate, and expense.
- Multiple consoles spread out all over our computer room for system
consoles all replaced by one built into the rack HMC. Thus freeing up a
LOT of desk space.
- Having to drag my butt into the machine room to access the system
console would be a big pain in the butt.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: Migrate twinax console to LAN console V5R2, (continued)
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.