|
I finally got back to poking at my 170's Operations Console connections today, after being out of town the past few days. My LAN isn't 192.168.0.x, so Vern Hamberg's suggestion isn't the problem; I installed the latest service pack, per Andy Nolen-Park's suggestion; the 11111111 signon I'm, using is out fo the book at the Operations COnsole startup on the PC, not the DST signon (which I've used QSECOFR for when I've gotten into it from the twinax console); and I ran the conneciton test Steven Segars suggested, and it shows that the connection is present and running. Mark Waterbury suggested privately that I run a prerequisite checking program found on the V5R1 setup CD; I couldn't find it, however. That leaves this: On Tue, Mar 04, 2003 at 08:18:04AM -0800, Chris Bipes wrote: > Check your card configuration. I seem to remember that on the 170 the card > you are attaching the operations console to has to be in a particular slot. > Also you need the 2 port WAN, cannot remember the card number, not the 4 > port twinax /w 1 port WAN, which it sounds like you have. The operations console neds to be connected to the left-hand port (as you look at the back of the machine) in slot C08. As it turns out, I shoulda read the requirements in the setup guide more closely. They list, for a 170, a requirement of a 2745 dual-port WAN card or a 2771 (I guess it's another dual-port WAN card). My system does indeed have a 9720 1-port WAN/4-port twinax card. I need to keep the twinax connections, so I need to get one of the other cards and stick it in slot C09 (the only open PCI slot in my system). I guess that means I need a 2771, since it will be found and used wherever it's placed. My copy of the System Builder is old enough that it doesn't list the 2771 at all, so I don't know its ocnfiguration rules; I believe that if I want to keep the 9720, though, it must live in slot C08 to be used as a console device. Am I correct? If I can find a 2745 card, would it have to go in C08? If it does, do I then lose the twinax console possibility? What's been throwing me is that the low-level connectivity is there, as shown by the tests and the fact that the Operations Console screen shows a status of connected; it just won't do anything after that. It seems strange that it would get that far and then not work.
As an Amazon Associate we earn from qualifying purchases.
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.