From: San M. <net...@va...> - 2001-04-10 16:10:02
|
if you're not seeing any data through minicom then the bios on the remote machines is not setup correctly. Please have a look at the documentation screenshots which show the proper settings -san dr...@va... wrote: > -- > Tony Kubinski 1.877.VALINUX x76776 (work) > Systems Engineer 1.781.823.6029 (fax) > VA Linux Systems 1.630.248.5293 (cell) > Chicago dr...@va... (email) > 630...@mo... (text page) > > ------------------------------------------------------------------------ > > Subject: Re: [se] VACM Question > Date: Tue, 10 Apr 2001 08:15:57 -0500 > From: dr...@va... > CC: se...@li..., vac...@va... > References: <3AD...@va...> <200...@va...> <3AD...@va...> <200...@va...> <3AD...@va...> <200...@va...> <200...@va...> > > I'm not getting anything thru minicom from the client's EMP > port at any port settings. > > Ari Jort wrote: > > > > Tony, > > > > Also, use minicom to check out the port on which EMP data > > should be coming. Run it on the mayor, set to 19200, > > but try other speeds also. > > > > If you see garbage data pulsing every 2 seconds or so, > > then you might actually have EMP going across. > > > > The garbage looks kinda like this: > > > > .$,%.,$.#,*,#.,$%{,@> > > > > basically, lots of punctuation :) > > > > If you see that in minicom, then you know for sure > > that the monitored machine is in fact sending EMP data out. > > If vash can't see it, then you know it's a nexxus problem. > > > > Have you configured the nodes correctly in nexxus? > > > > Send us you /usr/lib/vacm/vacm_configuration file. > > > > Stay in touch so we can get this. Pratt experience > > from yesterday has me a little nervous. > > > > Plus, Trey and I are going onsite today to Bear Stearns > > to do precisely what Pratt was doing the other day. > > Expectations are reasonable and I feel prepared, so I'm > > not worried. At least not yet. > > > > Do we have that emergency hotline to San set up yet? > > > > ari > > > > On Tue, Apr 10, 2001 at 05:59:33AM -0700, Greg Pryzby wrote: > > > On Tue, Apr 10, 2001 at 06:52:13AM -0500, dr...@va... wrote: > > > > > > > > Thanks...vacm_sys_statd now runs and client system data > > > > can be retrieved by the mayor. No, I wasn't using either > > > > flim or hoover, just vash. There seems to be some basic EMP > > > > communication issue that is escaping me. > > > > > > What is working/isn't for emp? What can yo do? > > > /var/log/vacm.log > > > /var/log/vacm*nodename*log > > > > > > should help debug the problem. > > > > > > Send exact commands and responses and we can fix /answer Qs. > > > > -- > > -------------------------------------------------------------- > > Ari Jort * ar...@va... * 212 858 7686 > > VA Linux Systems * 140 Broadway Suite 4616 * New York NY 10005 > > http://valinux.com * http://nylug.org > > -- > Tony Kubinski 1.877.VALINUX x76776 (work) > Systems Engineer 1.781.823.6029 (fax) > VA Linux Systems 1.630.248.5293 (cell) > Chicago dr...@va... (email) > 630...@mo... (text page) > > ********************** > se mailing list > |