Re: (ASCEND) TNT: multiple T3's into one stack

[Joe Pautler <pautler@grasshopper.cit.buffalo.edu>]

Dean Frye wrote:           (written on 02/23/00 at 10:24)
]At 01:21 PM 2/22/00 -0800, Joe Max wrote:
]
]>So in the best case, you could serve up to 1024 calls (about
]>41 T1s) in that configuration. I suggest you contact your friendly
]>sales rep to find what the real upper limit is. I suspect it is less
]>than that.
]
]The real upper limit is slightly less than 1024 as some of the timeslots
]are reserved - about 960 on 8.x software. This means 960 DS0s can be
]concurrently terminated on a chassis.
]
]Regards,
]
]dean

Thank you both VERY MUCH for this information!  I did not know this, and
my Ascend/Lucent reps certainly didn't mention it!

Up until last night, we had a stack of TNT's serving 624 phone
lines (26 T1's via a T3), and it was working just fine.  As of
yesterday, we expanded to 768 phone lines (32 T1's, via 2 T3's).
We seem to have maxed out at 748 users however (20 less than the
number of lines/modems), and from the period of time during the
saturation, I have a ton of log messages of the form:

Feb 22 21:19:39 tnt200-79.dialin.buffalo.edu 1/17: NETIF: _idAllocated, slot 1/1
, can't allocate sys ID for slot ID 299
Feb 22 21:19:45 tnt200-79.dialin.buffalo.edu 1/17: NETIF: _idAllocated, slot 1/1
, can't allocate sys ID for slot ID 144
Feb 22 21:19:46 tnt200-79.dialin.buffalo.edu 1/17: NETIF: _idAllocated, slot 1/1
, can't allocate sys ID for slot ID 668
Feb 22 21:19:47 tnt200-79.dialin.buffalo.edu 1/17: NETIF: _idAllocated, slot 1/1
, can't allocate sys ID for slot ID 512
Feb 22 21:19:56 tnt200-79.dialin.buffalo.edu 1/17: NETIF: _idAllocated, slot 1/1
, can't allocate sys ID for slot ID 356
Feb 22 21:19:56 tnt200-79.dialin.buffalo.edu 1/17: NETIF: _idAllocated, slot 1/1
, can't allocate sys ID for slot ID 125
Feb 22 21:20:03 tnt200-79.dialin.buffalo.edu 1/1: [1/1/1/9] Far End Hung Up
Feb 22 21:20:03 tnt200-79.dialin.buffalo.edu 1/17: NETIF: _idDeleted, can't dele
te slot 1/1, id 668
Feb 22 21:20:12 tnt200-79.dialin.buffalo.edu 1/1: [1/1/1/8] Far End Hung Up
Feb 22 21:20:12 tnt200-79.dialin.buffalo.edu 1/17: NETIF: _idDeleted, can't dele
te slot 1/1, id 299
Feb 22 21:20:18 tnt200-79.dialin.buffalo.edu 1/17: NETIF: _idDeleted, can't dele
te slot 1/1, id 356

And there are a few of these sprinkled in:

Feb 22 21:29:03 tnt200-79.dialin.buffalo.edu 1/17: WARNING  Index: 179  Revision
: 7.2.3  Shelf 1  (tntsr)  Location:  10208e34 1020ac0c 1020ad38 102fe3bc 103ace
54 103aef2c 


slot 1/1 is the T3 card that would have been attempting to terminate
the last 20 calls.  Do you know if these messages are related to the
timeslot limitation that you both were refering to?  If so, do you
know what these users would have experienced (busy signal, dead air, etc).
I've called this into Ascend/Lucent, but past experience has been that 
I get much better support from everyone on this list then I do from 
my 'official support contract'.  :-)

Thanks in advance for any info you can provide!

Specific stack config:
   TNT1:   T3 card  (26 T1's enabled)
           4/1ether-card  (not in use)
           6x 48modem-56k-card          
   TNT2:   T3 card  (not in use)
	   4/1ether-card  (not in use)
	   7x 48modem-56k-card
   TNT3:   T3 card (6 T1's enabled)
	   4ether2-card
	   4x csmx-card
   SOFTWARE = 7.2.3

___________________________________________________________________________
Joe Pautler, E.I.T.                             University at Buffalo
CIT/OSS Network Engineering                     224 Computing Center
http://www.oss.buffalo.edu/~pautler             (716) 645-3536

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>