1 Dec
2003
1 Dec
'03
10:20 p.m.
On Mon, 1 Dec 2003, Antonio Carlini wrote:
Yes, a KFQSA controller creates up to three MSCP controllers;
one for each device connected (in my VAX 4705A, which only HAS
three drives.. it may support the full 7 drives..)
So, if you have a KDA50 as well, that could create up to 4
of em. Make sure the one you want to *boot* from is the one
at the MSCP default (17772150 comes to mind?) address.
Thanks for your answers !
I'm also convinced sure that the KDA is masked by the KFQSA.
The adress on the KDA has been changed by myself to the adress given by the
"config" - command,
1ut unfortunately, the KDA hasn't been detected by "show device".
Tonight, i'll remove the KFQSA and the KLESI and make a new try with the default
addess (172150).
Pierre
______________________________________________________________________________
WEB.DE FreeMail wird 5 Jahre jung! Feiern Sie mit uns und
nutzen Sie die neuen Funktionen http://f.web.de/features/?mc=021130
gives out
the adress fopr the SDI-Controller, if I type in
KLESI, KFQSA and KDA50. I installed the controller directly
behind the KFQSA-Board with the address given by config.
It's been a while now but I'm pretty sure that the KFQSA
pretends to be an MSCP device for each disk it has been
configured to recognise. So if you have configured your
KFQSA for two disks, it behaves as two KDA50s. The
exact addresses of these depend on how the KFQSA was
configured. Yes, definitely. With the post-MicroVAX II
systems, it's
one of the quick ways to see if the KDA50 works at all.
It's probably being masked by the KFQSA.
The KDA probably sits at the default
address, with the KFQSA
also using that address, indeed. Most KFQSA's are configured
to allocate as many controllers as needed, with the first one
sitting at the MSCP-default address, soo..