Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: (ASCEND) Maxiumum no.of users on TNT
On Wednesday, October 29, 1997 7:03 AM, K.R.Kumar
[SMTP:krkumar@pacific.net.sg] wrote:
> Anybody is using TNT?.
Yes. We have about 20 in service, with an additional 20 waiting to go
into service - once the main bugs are sorted out.
> Have you checked max no.of users connected on the Max TNT.
Yes. We have had 240 user on one TNT [*1 - below].
> We have tested on TNTs the maximum no.of users connected
> on TNT is around 160 to 190, Eventhough it is capable of
> 240 sessions.
We have had various problems, most of which concern modem quality and
connectivity, but are mostly centred around the TNTs behaving
differently (and worse) than existing (software wise mature) MAX4000s.
> We have send this problem to ascend, as usual asked us to
> upgrade to 1.3Ap6, have done the same but no avail.
It is a shame to see that there are no releases after p6. This means
that I cannot advise you what release to run. As a site that has Ascend
working on specific issues that relate to us (and also general bugs too)
we are running special engineering code - which I cannot recommend to
you. 1.3Ap13 was looking OK on paper but got pulled - hopefully the next
release will be more stable.
> The interesting part is that mib results on no.of calls
> connected and no.of modems engaged is differ. A big margin.
Are you using v.34 modem cards of k56flex modem cards ? We experienced
"hanging modem" problems with v.34 cards that the release notes for p13
say were fixed, but again no p13 :(
> Disabling E1 line using set enable = no on E1 profile also
> not working. After doing for 8E1 lines I can able to see
> the users come in.
Just change the signalling type - that will confuse your telco's switch
enough for them to shut down the line. This is not however considered
"best practice". We have not tried shutting entire E1 lines down - our
telco's usually do that for us on request, but this may be a level of
service issue.
> Upgrading TNT os 1.3Ap6 is also painful. Especially after
> flash upgrade, the existing configuraion never works.
> Saved the configuration and checked it , I dont know what is
> that any shelf any slot . Any shelf entries are there for
> E1 lines , Ethernet entries and Ip interface. Removed
> any shelf entries for above profiles , it never works.
The call routing model is very complex, but makes sense after a while.
The CALL-ROUTE profile "{any any 0}" seems worthless, but I have not
been able to find out if it is necessary as a place holder. It is best
to make sure that you build your own call-route profile entries and
delete any for cards that are not in the system. If you use "slot -r" to
remove a card, I believe the CALL-ROUTE profile goes with it.
In terms of configuration, I strongly recommend saving a "working"
configuration with the "save -a" option to a file, then going through it
line by line (OK section by section, there are about 10000 lines) and
contructing a reference config file. Then when you upgrade, unless you
have the luxury of a test box to verify that the upgrade is seamless,
you should upgrade by wiping the NVRAM and reloading the config after
manually bringing up an Ethernet port - REMEMBER however that your
config will overwrite the manually configured Ethernet profile halfway
through the "load config", so what I do is delete the controller card
ethernet and default route profile from the reference config and use
that - this has the side efftect of leaving those alone.
> Ascend please do some thing on TNT.
I think that Ascend engineering is overheating doing things about the
TNT. We are still having a number of very serious problems, which should
never have made it to a customer site, but I cannot fault Ascend in its
reactivity to address those issues. I do not think it would be very
useful to list those issues here at this time.
Note *1: We have had 240 users on a TNT, but now run with 210 channels
and 240 modems temporarily. The problem that causes us to run this way
is that when the box is near full, dropped modem calls require that the
individual modem be reset before being reused - this takes about 4
seconds. Meanwhile new calls come in and there is no port for them, the
caller gets "busy" returned. Ascend are aware of this and should be
working on a fix - which is of course not to answer a call until a
suitable port is available.
Peter
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>