Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!PAN.SSEC.HONEYWELL.COM!thompson From: thompson@PAN.SSEC.HONEYWELL.COM (John Thompson) Newsgroups: comp.sys.apollo Subject: re: ADUS SysAdmin summary? (700 series & ATR) Message-ID: <9106061932.AA04142@pan.ssec.honeywell.com> Date: 6 Jun 91 19:32:57 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 62 Carl -- > > Ok folks, rumor control time. ATR is not an option on the 700 series > > ... > > However ATR -IS- an option for the 700 series under OSF. HP/Apollo > > Everything David says here is absolutely correct. No "ifs", "ands", > or "buts".... > THE ONLY PROTOCOL WE WILL SUPPORT OVER ATR is IP. I hope that the rumours didn't start w/ the USENET letter. I tried to be clear in the fact that AT FIRST we wouldn't be able to have the Snakes in the same network. If we wait until Q?, we can of course run OSF, and that is of course true (unless HP decides to change their mind again). > In order to facilitate interoperation with Domain nodes on ATR (why else > would you want ATR on a Snake, right?).... Oh, I don't know. Maybe the large investment in building wiring; maybe the fact that ATR is faster than ethernet; maybe the fact that token-ring doesn't break down at high load levels; maybe because ATR is superior! > In order to maintain the integrity of the ring, HP/OSF1 ATR will respond to > "lcnode" (asknode_$who) packets and regenerate the request in order to > allow the Domain/OS node performing the lcnode to wee the entire ring. > If HP/OSF1 didn't do this, the lcnode output would stop at the node > immediately "upstream" from the first Snake in the ring. Good. Thank you. > We will also respond to the "bldt" command to the extent that a > "bldt Net.Node_ID" done to an HP/OSF1 node from a Domain/OS node will > return the string elicited by the OSF command "uname -a". We are doing this > to allow people to figure out why a node shows up on an "lcnode", but > can't be catalogued or otherwise accessed with Domain services. Better. Thank you even more. > I suppose this would be the place to say that even though I have permission > from HP Marketing to post this I am not an official spokesman for HP and > therefore if what I have written conflicts with some official policy or > announcement either now or in the future, then, of course, the official > policy or announcement is the one to believe. On the other hand, you can > have a fairly high degree of confidence that the above is correct, since > I'm the one writing the code and I currently have it running on my Snake > here in Chelmsford. I realize that it's necessary, but I hope that, after you re-read the above paragraph, you understand some of our concerns. HP has promised longer support for Domain/OS and yanked it; HP has promised a PRISM-II and yanked it (I know many of the details, and can't (quite) blame mgmt for the problem); HP has promised Domain/OS on the first merged RISC box and yanked it; HP has promised OSF support on all DN3000+ boxes and yanked it. I know that you are writing only what is true and correct, but HP management seems to revel in changing the truth to suit their whims. IBIWISI!!! (I'llBelieveItWhenISeeIt). Regards -- jt -- John Thompson Honeywell, SSEC Plymouth, MN 55441 thompson@pan.ssec.honeywell.com When in danger, when in doubt -- run in circles, scream and shout.