RE: [Vacm-general] Slow EMP handling

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Hey Ard,

As I suspected, it looks like you're having a serial protocol issue..
The reason that only the cisco boxes are qualified as a *network* based
connectivity method for EMP are that they have below 1 ms round trip
latency on single byte transactions on their raw ports... The EMP
protocol requires a MAXIMUM latency of 2ms per byte.. otherwise it will
timeout the byte (and sometimes the fame). It is VERY difficult to
recover a frame when this occurs, so we end up having to do nasty
re-synchronizing which doesn't always work...

I would advise going to a rocketport connectivity solution since its
much cheaper than the cisco method...
-san

-----Original Message-----
From: Ard van Breemen [mailto:ar...@te...] 
Sent: Tuesday, July 24, 2001 10:32 AM
To: San Mehat
Cc: vac...@li...
Subject: Re: [Vacm-general] Slow EMP handling

On Tue, Jul 24, 2001 at 09:59:56AM -0700, San Mehat wrote:
> This is not normal.. please run nexxus with -l and send me the
output..
Thanks, I needed to here it is not normal :)
> you may have a serial concentrator problem (probably latency), causing
> protocol errors...
I've seen those errors, when I used telnet as the protocol....
But now:
ard@c24574:/net/home/ard$ time vash -c localhost -u blum -p frub -x 'ipc
localhost emp:chassis_status:rs0'
EMP:3:JOB_STARTED
vash: Nexxus 127.0.0.1 timed out waiting for IPC response

real    0m50.113s
user    0m0.000s
sys     0m0.000s
You have mail in /home/ard/Mail/.inbox
ard@c24574:/net/home/ard$ time vash -c localhost -u blum -p frub -x 'ipc
localhost emp:chassis_status:rs0'
EMP:6:JOB_STARTED
EMP:3:CSTATUS:YES:NO:NO:NO:NO:YES:NO:NO:NO:NO:NO:YES:NO:NO:NO
EMP:3:JOB_COMPLETED

real    0m38.015s
user    0m0.000s
sys     0m0.000s
ard@c24574:/net/home/ard$ 

And in the log (used /var/log/vacm.log, since that is timestamped):
[18:52:08][VACM] 2.0.5 Nexxus daemon (Build Jun 24 2001 23:21:50)
[18:52:08][Nexxus] Standard Out Logging Enabled
[18:52:08][Nexxus] Identified 11 modules
[18:52:08][Nexxus] [Vasenet][0.5][VASENET][Zac Sprackett
(za...@va...)]
[18:52:08][Nexxus] [VA1000][1.1][VA1000][Jerry Katzung
(ka...@va...)]
[18:52:08][VA1000] Failed to open /dev/va1000_smbus: device does not
exist!
[18:52:08][Nexxus] [Sysstat][0.1][SYSSTAT][San Mehat
(net...@va...)]
[18:52:08][Nexxus] [BayTech][2.0][BAYTECH][Zac Sprackett
(zsp...@va...)]
[18:52:08][Nexxus] [EMP][2.0][EMP][San Mehat (net...@va...)]
[18:52:08][Nexxus] [ICMP ECHO][1.0][ICMP_ECHO][San Mehat
(net...@va...)]
[18:52:08][Nexxus] [QUANTA][0.1][QUANTA][Zac Sprackett
(za...@va...)]
[18:52:08][Nexxus] [rsh][2.0][RSH][Dean Johnson (dt...@sg...) & Zac
Sprackett (zsp...@va...)]
[18:52:08][Nexxus] [SBT2][0.1][SBT2][Zac Sprackett (za...@va...)]
[18:52:08][Nexxus] [SERCON][2.0][SERCON][San Mehat
(net...@va...)]
[18:52:08][Nexxus] [msc][2.0][MSC][Dean Johnson (dt...@sg...)]
[18:52:08][SERCON] Unable to lookup 'c24574.telegraafnet.nl'.
Connections unavailable (Unknown host)
<snipped 17 more of these SERCON>
[18:52:09][EMP] Thread rs0 protocol detected
[18:52:13][EMP] Thread office protocol unavailable (Connection timed
out)
[18:53:04][Nexxus] Logging user blum in on client 17 from 127.0.0.1
[18:53:54][Nexxus] Logging user blum out on client 17 from 127.0.0.1
[18:54:01][Nexxus] Logging user blum in on client 17 from 127.0.0.1
[18:54:39][Nexxus] Logging user blum out on client 17 from 127.0.0.1

I've seen errors:
[11:25:29][EMP] Thread rs0 received corrupt EMP data field (us 0x49,
them 0x48)
[11:25:29][EMP] Thread rs0 data c4 2c 10 20 78 11 00 10 00 ff ff 00 00
00 00 00 00 00 00 00 00 00 00 00 00 48 a5 
[11:25:30][EMP] Thread rs0 received corrupt EMP data field (us 0x45,
them 0x44)
[11:25:30][EMP] Thread rs0 data c4 2c 10 20 7c 11 00 10 00 ff ff 00 00
00 00 00 00 00 00 00 00 00 00 00 00 44 a5 
[11:25:30][EMP] Thread rs0 received corrupt EMP data field (us 0x45,
them 0x44)
[11:25:30][EMP] Thread rs0 data c4 2c 10 20 7c 11 00 10 00 ff ff 00 00
00 00 00 00 00 00 00 00 00 00 00 00 44 a5 
But these were the typical telnet instead of raw errors.

And the following:
ard@c24574:/net/home/ard$ sudo lsof -c emp.loose|grep pm2-0|wc -l
     56

Is there a way to (runtime) limit the number of threads started, so that
I can strace, and see what exactly is going on?
The build I use is the wakkerma build:
http://people.debian.org/~wakkerma/vacm

> The only serial concentrator qualified to work with VACM is a Cisco
36xx
> with 32 port async cards
> -san
Hmmm, the cyclades ts2000 sounds interesting. If we are able to strip
software that is not needed (like radius and stuff like that), and
implement some emp daemon, it could nicely handle all those emp ports,
and serial consoles...
(http://www.cyclades.com/products/stdalone/ts1_2000.htm)
But then again, it might all be cyclades proprietery software that runs
on linux...

-- 
<ar...@te...> Telegraaf Elektronische Media  http://wwwijzer.nl
http://leerquoten.monster.org/ http://www.faqs.org/rfcs/rfc1855.html 
Let your government know you value your freedom. Sign the petition:
http://petition.eurolinux.org/