Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 23 Dec 1999 16:26:35 -0600 (CST)
From:      Mike Spengler <mks@networkcs.com>
To:        bxgu@seu.edu.cn (bxgu)
Cc:        atm@freebsd.org
Subject:   Re: nicstar/signalling problems
Message-ID:  <199912232226.QAA88767@us.networkcs.com>
In-Reply-To: <001a01bf4c1f$537f1dc0$5e3afea9@mars_atm.seu.edu.cn> from "bxgu" at Dec 22, 1999 09:53:10 AM

next in thread | previous in thread | raw e-mail | index | archive | help
There are some odd things here and I believe some missing information...

> port:
>   Port  VPI Interface      SigVersion State ILMI Side    RemoteAddress
>  1A4     0 privateUNI     uni31      down  down network
> when I enter "stat vcc 1a4",the system appear the following:
>  Port VPI  VCI Port VPI  VCI  Uptime       Received   Rejected
> 1A4    0    5 1CTL   0   49  0d:20:40          366                 0
> 1A4    0   14 1CTL   0   48  0d:20:40            0                   0
> 1A4    0   15 1CTL   0   47  0d:20:40            0                   0
> 1CTL   0   49 1A4    0    5  0d:20:40         7148                0
> 1CTL   0   48 1A4    0   15  0d:20:40       152530            0
> in my freebsd3.0 system,before I enter "atm set prefix ..."the status of my
> atmadapter is as following:
> Interface  Sigmgr   State
> idt0       UNI 3.1  ADR_WAIT
> ATM address = -
> Network interfaces: it0 - it2
> after I enter "atm set prefix ...",the status of my atm adapter is as
> following:
>  Interface  Sigmgr   State
> idt0       UNI 3.1  ACTIVE
> ATM address = 0x47.0005.80.ffe100.0000.f21a.60c0.0020485b0bf1.00

This is the state that it's supposed to be!  Did you do something different
or change anything for this test??


> Network interfaces: it0 - it2
>                         Input    Input  Input  Output   Output Output
> Interface  VPI   VCI     PDUs    Bytes   Errs    PDUs    Bytes   Errs
> idt0         0     5        0        0      0       0        0      0
> idt0         0    16        0        0      0       0        0      0
It seems that the NICStar driver is not counting VCC statistics..


>  but,In this time,the system appear the following errors:
>  Dec 22 17:00:00 mars /kernel: sscop_maa_error: intf=idt0 vpi=0 vci=5 code=U
> state=2
> Dec 22 17:00:00 mars /kernel: sscop badpdu received: vcc=(0,5)
> Dec 22 17:00:00 mars /kernel: : bfr=0xf56cb380 data=0xf5556710 len=48:
See below...

> meantime.the status of corresponding port on my awitch is the following:
> Input         Output                         Cells      Cells
> Port VPI  VCI Port VPI  VCI  Uptime       Received   Rejected
> 1A4    0    5 1CTL   0   49  0d:21:12         1078                0
> 1A4    0   14 1CTL   0   48  0d:21:12            0                  0
> 1A4    0   15 1CTL   0   47  0d:21:12            0                   0
> 1CTL   0   49 1A4    0    5  0d:21:12         9481                0
> 1CTL   0   48 1A4    0   15  0d:21:12       156515              0

This shows that the switch is sending and receiving cells on the signalling
VCC (vpi=0,vci=5).

> when I return my freebsd system,I enter "atm sh stats int idt0 aal5",the
> freebsd system tell me that
> atm:unknown adapter vender.

The ATM utility commands don't know about the NICStar type...

> the attached please find my atmdump and message files that you need.thank
> you!

The /var/log/messages file seems wrong and/or incomplete.  The atmdump
trace shows activity from about 16:40 through 17:00.  The message file starts
with a reboot at 17:09 but ends with the "badpdu" messages from 17:00.  I'm
guessing that the reboot messages are from a reboot AFTER the tests you ran.
I need to see the /var/log/messages file from the period when you actually
ran the tests above.  In particular, you should see a line like the following:

uni: set address 0x47....... on interface idt0

in this area of the messages file when you issue the 'atm set prefix' command.

> Dec 22 17:00:00 mars /kernel: sscop badpdu received: vcc=(0,5)
> Dec 22 17:00:00 mars /kernel: : bfr=0xf56cb380 data=0xf5556710 len=48:

The badpdu errors indicate that the driver is delivering the SSCOP PDUs with
an incorrect length.  It appears that the length includes the entire AAL5 
length (48), not the SSCOP PDU length (8 for these PDUs) - SSCOP is rejecting 
these during its PDU validation process.  The missing messages may help with
this, plus maybe Mark can comment on this.

-- 
Mike Spengler				Network Computing Services, Inc.
Email: mks@networkcs.com		1200 Washington Ave. So.
Phone: +1 612 337 3557			Minneapolis MN 55415
FAX:   +1 612 337 3400			(aka Minnesota Supercomputer Center)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-atm" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912232226.QAA88767>