5200 Mica modems problem: users get disconnected intermittently and busy signal GOT A LEAD!!!!

5200 Mica modems problem: users get disconnected intermittently and busy signal GOT A LEAD!!!!

Post by gfaer.. » Tue, 04 Aug 1998 04:00:00



Ok, if you have read my previous post you are familiar with the RBS issue.
That was related to AS5200 disconnecting the users.
Well, now I got a snapshot of what's going on when a user tries to dialin
and just get busy signal over the phone, and NOBODY is actually conencted
(all 30 timeslots are free).

the sh isdn stat shows this (in fact this are not ISDN call, we use E1 and
internal MICA modem to receive up to V.90 analog calls). But someone told
me to look at it.

ISDN Serial1:15 interface
        dsl 0, interface ISDN Switchtype = primary-net5
    Layer 1 Status:
        DEACTIVATED
    Layer 2 Status:
        TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
    Layer 3 Status:
        0 Active Layer 3 Call(s)
    Activated dsl 0 CCBs = 0
    Total Allocated ISDN CCBs = 0

Then let see to the sh line command output (just showing the last lines to
shorten this)
I 24 TTY               - inout     -    -    -    14        0        0/0
I 25 TTY               - inout     -    -    -    18        0        0/0
I 26 TTY               - inout     -    -    -    19        0        0/0
I 27 TTY               - inout     -    -    -    20        0        0/0
I 28 TTY               - inout     -    -    -    12        0        0/0
I 29 TTY               - inout     -    -    -    13        0        0/0
I 30 TTY               - inout     -    -    -    12        0        0/0
and show modem reports
* 0/23    5%      19     12      0      0       6        0       6     61%
* 0/24    9%      20     13      0      0       7        0       6     60%
* 0/25    8%      19     14      0      0       7        0       6     57%
* 0/26    6%      19     14      0      0       7        0       5     57%
* 0/27    5%      14     17      0      0       7        0       9     45%
* 0/28    9%      17     12      0      0       7        0       6     58%
* 0/29    2%      13     19      0      0       7        0      11     40%

as if they are being in use!

sh controller shows
5200_01#sh controller e1 0
E1 0 is up.
  Applique type is Channelized E1 - unbalanced
  No alarms detected.
  Version info of Slot 1:  HW: 4, Firmware: 8, NEAT PLD: 18
  Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line Primary.
  Data in current interval (670 seconds elapsed):
     0 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

When fingering the AS5200 it shows no users!

Well, at Mon Aug  3 20:51:47 1998    user    Pwaisgold was dropped out as
you can see here at the tac_plus acct record

Mon Aug  3 20:51:47 1998  200.26.98.198   Pwaisgold       tty14
async/0279      stop    task_id=858     timezone=UTC    service=ppp
protocol=ipaddr=200.26.98.149      disc-cause=2    disc-cause-ext=1011
pre-bytes-in=134
        pre-bytes-out=107       pre-paks-in=5   pre-paks-out=5
bytes_in=27752 bytes_out=140396        paks_in=1359    paks_out=1315
pre-session-time=7 elapsed_time=1389       data-rate=33600 xmit-rate=33600

Since then, it is Mon Aug  3 21:34:44 ART 1998 at the machine running the
syslog and tacacs 2.1 daemon, nobody was able to dialin because the busy
signal issue.

This is an extract from the debug output collected since that time

Aug  3 20:51:43 200.26.98.198 12565: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 29 is down
Aug  3 20:51:43 200.26.98.198 12566: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 30 is down
Aug  3 20:51:43 200.26.98.198 12567: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 12 is down
Aug  3 20:51:43 200.26.98.198 12568: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 16 is down
Aug  3 20:51:43 200.26.98.198 12569: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 22 is down
Aug  3 20:51:43 200.26.98.198 12570: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 31 is down
Aug  3 20:51:47 200.26.98.198 12571: %LINEPROTO-5-UPDOWN: Line protocol on
Interface Async14, changed state to down
Aug  3 20:51:48 200.26.98.198 12572: %LINK-5-CHANGED: Interface Async14,
changed state to reset
Aug  3 20:51:53 200.26.98.198 12573: %LINK-3-UPDOWN: Interface Async14,
changedstate to down
Aug  3 20:52:21 200.26.98.198 12574: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 15 is down
Aug  3 20:52:36 200.26.98.198 12575: %MICA-5-MODEM_RECOVERY: Modem (0/8) is
 being recovered by redownload
Aug  3 20:52:48 200.26.98.198 12576: %DSX0-5-RBSLINEUP: RBS of controller 0
 timeslot 16 is up
Aug  3 20:52:48 200.26.98.198 12577: %DSX0-5-RBSLINEUP: RBS of controller 0
 timeslot 22 is up
Aug  3 20:52:48 200.26.98.198 12578: %DSX0-5-RBSLINEUP: RBS of controller 0
 timeslot 31 is up
Aug  3 20:52:48 200.26.98.198 12579: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 16 is down
Aug  3 20:52:48 200.26.98.198 12580: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 22 is down
Aug  3 20:52:48 200.26.98.198 12581: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 31 is down
Aug  3 20:52:54 200.26.98.198 12582: %DSX0-5-RBSLINEUP: RBS of controller 0
 timeslot 16 is up
Aug  3 20:52:54 200.26.98.198 12583: %DSX0-5-RBSLINEUP: RBS of controller 0
 timeslot 22 is up
Aug  3 20:52:54 200.26.98.198 12584: %DSX0-5-RBSLINEUP: RBS of controller 0
 timeslot 31 is up
Aug  3 20:52:54 200.26.98.198 12585: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 16 is down
Aug  3 20:52:54 200.26.98.198 12586: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 22 is down
Aug  3 20:52:54 200.26.98.198 12587: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 31 is down
Aug  3 20:53:19 200.26.98.198 12588: %DSX0-5-RBSLINEUP: RBS of controller 0
 timeslot 16 is up
Aug  3 20:53:19 200.26.98.198 12589: %DSX0-5-RBSLINEUP: RBS of controller 0
 timeslot 22 is up
Aug  3 20:53:19 200.26.98.198 12590: %DSX0-5-RBSLINEUP: RBS of controller 0
 timeslot 31 is up
Aug  3 20:53:19 200.26.98.198 12591: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 16 is down
Aug  3 20:53:19 200.26.98.198 12592: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 22 is down
Aug  3 20:53:19 200.26.98.198 12593: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 31 is down
Aug  3 20:53:25 200.26.98.198 12594: %DSX0-5-RBSLINEUP: RBS of controller 0
 timeslot 16 is up

Yyou can see there is a loop here with the RBS of controller 0 (the E1) and
 timeslots 16, 22 and  31. Funny thing that timeslot is reserved for
signaling (I do not know nothing about E1 trunks, just repeating what I
read somewhere)

Now, please see this

Aug  3 21:42:08 200.26.98.198 14452: %DSX0-5-RBSLINEUP: RBS of controller 0
 timeslot 16 is up
Aug  3 21:42:08 200.26.98.198 14453: %DSX0-5-RBSLINEUP: RBS of controller 0
 timeslot 22 is up
Aug  3 21:42:08 200.26.98.198 14454: %DSX0-5-RBSLINEUP: RBS of controller 0
 timeslot 31 is up
Aug  3 21:42:08 200.26.98.198 14455: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 16 is down
Aug  3 21:42:08 200.26.98.198 14456: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 22 is down
Aug  3 21:42:08 200.26.98.198 14457: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 31 is down

As you can see almost 50 minutes later the loop is still there, noone can
dialin into the AS5200.
Reload will reset this to normal (after the reload AS5200 will still  drop
calls every 2-12 minutes anyway) and 48 hours from now we are going into
the loop again.

If you are at this part of this message, thank you for your attention. Hope
 we can solve this.

Gustavo Faerman
Faerman & Solari consultores
Buenos Aires, Argentina.

 
 
 

5200 Mica modems problem: users get disconnected intermittently and busy signal GOT A LEAD!!!!

Post by Aaron Leona » Thu, 13 Aug 1998 04:00:00


Well, this definitely shows that you've got an ISDN-layer
problem.  Since you look OK at the E1 layer, then there is
presumably some protocol disagreement between the 5200 and
your switch.  DEBUG ISDN Q921, DEBUG ISDN Q931 gathered at the
time when the problem occurs will be helpful,
although if you want an impartial opinion, you'd need an ISDN
protocol analyzer on your E1 line.

Aaron

---

On 3 Aug 1998 21:52:46 -0600, gfaer...@fys.com.ar wrote:

~ Ok, if you have read my previous post you are familiar with the RBS issue.
~ That was related to AS5200 disconnecting the users.
~ Well, now I got a snapshot of what's going on when a user tries to dialin
~ and just get busy signal over the phone, and NOBODY is actually conencted
~ (all 30 timeslots are free).
~
~ the sh isdn stat shows this (in fact this are not ISDN call, we use E1 and
~ internal MICA modem to receive up to V.90 analog calls). But someone told
~ me to look at it.
~
~ ISDN Serial1:15 interface
~         dsl 0, interface ISDN Switchtype = primary-net5
~     Layer 1 Status:
~         DEACTIVATED
~     Layer 2 Status:
~         TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
~     Layer 3 Status:
~         0 Active Layer 3 Call(s)
~     Activated dsl 0 CCBs = 0
~     Total Allocated ISDN CCBs = 0
~
~ Then let see to the sh line command output (just showing the last lines to
~ shorten this)
~ I 24 TTY               - inout     -    -    -    14        0        0/0
~ I 25 TTY               - inout     -    -    -    18        0        0/0
~ I 26 TTY               - inout     -    -    -    19        0        0/0
~ I 27 TTY               - inout     -    -    -    20        0        0/0
~ I 28 TTY               - inout     -    -    -    12        0        0/0
~ I 29 TTY               - inout     -    -    -    13        0        0/0
~ I 30 TTY               - inout     -    -    -    12        0        0/0
~ and show modem reports
~ * 0/23    5%      19     12      0      0       6        0       6     61%
~ * 0/24    9%      20     13      0      0       7        0       6     60%
~ * 0/25    8%      19     14      0      0       7        0       6     57%
~ * 0/26    6%      19     14      0      0       7        0       5     57%
~ * 0/27    5%      14     17      0      0       7        0       9     45%
~ * 0/28    9%      17     12      0      0       7        0       6     58%
~ * 0/29    2%      13     19      0      0       7        0      11     40%
~
~ as if they are being in use!
~
~ sh controller shows
~ 5200_01#sh controller e1 0
~ E1 0 is up.
~   Applique type is Channelized E1 - unbalanced
~   No alarms detected.
~   Version info of Slot 1:  HW: 4, Firmware: 8, NEAT PLD: 18
~   Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line Primary.
~   Data in current interval (670 seconds elapsed):
~      0 Line Code Violations, 0 Path Code Violations
~      0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
~      0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
~
~
~ When fingering the AS5200 it shows no users!
~
~ Well, at Mon Aug  3 20:51:47 1998    user    Pwaisgold was dropped out as
~ you can see here at the tac_plus acct record
~
~ Mon Aug  3 20:51:47 1998  200.26.98.198   Pwaisgold       tty14
~ async/0279      stop    task_id=858     timezone=UTC    service=ppp
~ protocol=ipaddr=200.26.98.149      disc-cause=2    disc-cause-ext=1011
~ pre-bytes-in=134
~         pre-bytes-out=107       pre-paks-in=5   pre-paks-out=5
~ bytes_in=27752 bytes_out=140396        paks_in=1359    paks_out=1315
~ pre-session-time=7 elapsed_time=1389       data-rate=33600 xmit-rate=33600
~
~ Since then, it is Mon Aug  3 21:34:44 ART 1998 at the machine running the
~ syslog and tacacs 2.1 daemon, nobody was able to dialin because the busy
~ signal issue.
~
~ This is an extract from the debug output collected since that time
~
~ Aug  3 20:51:43 200.26.98.198 12565: %DSX0-5-RBSLINEDOWN: RBS of controller
~  0 timeslot 29 is down
~ Aug  3 20:51:43 200.26.98.198 12566: %DSX0-5-RBSLINEDOWN: RBS of controller
~  0 timeslot 30 is down
~ Aug  3 20:51:43 200.26.98.198 12567: %DSX0-5-RBSLINEDOWN: RBS of controller
~  0 timeslot 12 is down
~ Aug  3 20:51:43 200.26.98.198 12568: %DSX0-5-RBSLINEDOWN: RBS of controller
~  0 timeslot 16 is down
~ Aug  3 20:51:43 200.26.98.198 12569: %DSX0-5-RBSLINEDOWN: RBS of controller
~  0 timeslot 22 is down
~ Aug  3 20:51:43 200.26.98.198 12570: %DSX0-5-RBSLINEDOWN: RBS of controller
~  0 timeslot 31 is down
~ Aug  3 20:51:47 200.26.98.198 12571: %LINEPROTO-5-UPDOWN: Line protocol on
~ Interface Async14, changed state to down
~ Aug  3 20:51:48 200.26.98.198 12572: %LINK-5-CHANGED: Interface Async14,
~ changed state to reset
~ Aug  3 20:51:53 200.26.98.198 12573: %LINK-3-UPDOWN: Interface Async14,
~ changedstate to down
~ Aug  3 20:52:21 200.26.98.198 12574: %DSX0-5-RBSLINEDOWN: RBS of controller
~  0 timeslot 15 is down
~ Aug  3 20:52:36 200.26.98.198 12575: %MICA-5-MODEM_RECOVERY: Modem (0/8) is
~  being recovered by redownload
~ Aug  3 20:52:48 200.26.98.198 12576: %DSX0-5-RBSLINEUP: RBS of controller 0
~  timeslot 16 is up
~ Aug  3 20:52:48 200.26.98.198 12577: %DSX0-5-RBSLINEUP: RBS of controller 0
~  timeslot 22 is up
~ Aug  3 20:52:48 200.26.98.198 12578: %DSX0-5-RBSLINEUP: RBS of controller 0
~  timeslot 31 is up
~ Aug  3 20:52:48 200.26.98.198 12579: %DSX0-5-RBSLINEDOWN: RBS of controller
~  0 timeslot 16 is down
~ Aug  3 20:52:48 200.26.98.198 12580: %DSX0-5-RBSLINEDOWN: RBS of controller
~  0 timeslot 22 is down
~ Aug  3 20:52:48 200.26.98.198 12581: %DSX0-5-RBSLINEDOWN: RBS of controller
~  0 timeslot 31 is down
~ Aug  3 20:52:54 200.26.98.198 12582: %DSX0-5-RBSLINEUP: RBS of controller 0
~  timeslot 16 is up
~ Aug  3 20:52:54 200.26.98.198 12583: %DSX0-5-RBSLINEUP: RBS of controller 0
~  timeslot 22 is up
~ Aug  3 20:52:54 200.26.98.198 12584: %DSX0-5-RBSLINEUP: RBS of controller 0
~  timeslot 31 is up
~ Aug  3 20:52:54 200.26.98.198 12585: %DSX0-5-RBSLINEDOWN: RBS of controller
~  0 timeslot 16 is down
~ Aug  3 20:52:54 200.26.98.198 12586: %DSX0-5-RBSLINEDOWN: RBS of controller
~  0 timeslot 22 is down
~ Aug  3 20:52:54 200.26.98.198 12587: %DSX0-5-RBSLINEDOWN: RBS of controller
~  0 timeslot 31 is down
~ Aug  3 20:53:19 200.26.98.198 12588: %DSX0-5-RBSLINEUP: RBS of controller 0
~  timeslot 16 is up
~ Aug  3 20:53:19 200.26.98.198 12589: %DSX0-5-RBSLINEUP: RBS of controller 0
~  timeslot 22 is up
~ Aug  3 20:53:19 200.26.98.198 12590: %DSX0-5-RBSLINEUP: RBS of controller 0
~  timeslot 31 is up
~ Aug  3 20:53:19 200.26.98.198 12591: %DSX0-5-RBSLINEDOWN: RBS of controller
~  0 timeslot 16 is down
~ Aug  3 20:53:19 200.26.98.198 12592: %DSX0-5-RBSLINEDOWN: RBS of controller
~  0 timeslot 22 is down
~ Aug  3 20:53:19 200.26.98.198 12593: %DSX0-5-RBSLINEDOWN: RBS of controller
~  0 timeslot 31 is down
~ Aug  3 20:53:25 200.26.98.198 12594: %DSX0-5-RBSLINEUP: RBS of controller 0
~  timeslot 16 is up
~
~ Yyou can see there is a loop here with the RBS of controller 0 (the E1) and
~  timeslots 16, 22 and  31. Funny thing that timeslot is reserved for
~ signaling (I do not know nothing about E1 trunks, just repeating what I
~ read somewhere)
~
~ Now, please see this
~
~ Aug  3 21:42:08 200.26.98.198 14452: %DSX0-5-RBSLINEUP: RBS of controller 0
~  timeslot 16 is up
~ Aug  3 21:42:08 200.26.98.198 14453: %DSX0-5-RBSLINEUP: RBS of controller 0
~  timeslot 22 is up
~ Aug  3 21:42:08 200.26.98.198 14454: %DSX0-5-RBSLINEUP: RBS of controller 0
~  timeslot 31 is up
~ Aug  3 21:42:08 200.26.98.198 14455: %DSX0-5-RBSLINEDOWN: RBS of controller
~  0 timeslot 16 is down
~ Aug  3 21:42:08 200.26.98.198 14456: %DSX0-5-RBSLINEDOWN: RBS of controller
~  0 timeslot 22 is down
~ Aug  3 21:42:08 200.26.98.198 14457: %DSX0-5-RBSLINEDOWN: RBS of controller
~  0 timeslot 31 is down
~
~ As you can see almost 50 minutes later the loop is still there, noone can
~ dialin into the AS5200.
~ Reload will reset this to normal (after the reload AS5200 will still  drop
~ calls every 2-12 minutes anyway) and 48 hours from now we are going into
~ the loop again.
~
~
~ If you are at this part of this message, thank you for your attention. Hope
~  we can solve this.
~
~ Gustavo Faerman
~ Faerman & Solari consultores
~ Buenos Aires, Argentina.
~
~

 
 
 

1. 5200 Mica modems problem: users get disconnected intermittently GOT A LEAD!!!!

We set debug ISDN events on (thank you Sasa):

LOOK AT THIS (using Capital to distinguish from the syslog output)

Aug  3 19:12:50 200.26.98.198 11470: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 1 is down
Aug  3 19:12:50 200.26.98.198 11471: %DSX0-5-RBSLINEDOWN: RBS of controller
 0 timeslot 2 is down

2. comp.os.vxworks newsdigest

3. ess1878

4. Win98 - MS Update Site

5. 5200 Mica modems problem: users get disconnected intermittently

6. Wiring Pair Colors POTS --> Cat3

7. 5200 Mica modems problem: users get disconnected intermitten tly

8. 5200 Mica modems problem: users get disconnected inte

9. Getting a busy signal...

10. BitSURFR Pro prob - incoming call gets busy signal when using 2B channels