First thing we do with every TC card that we get in, is reload software - All of our cards have the same software version - and it's all from the same software "series," including the TCM. Second we reset defaults every place that TCM allows it. That has always fixed "flaky" cards. Personally I can't imagine putting cards into production that I haven't personally reloaded code and reset to defaults.... -Wayne ----- Original Message ----- From: "Lee Terrell" <leet@directcon.net> To: <usr-tc@mailman.xmission.com> Sent: Wednesday, November 06, 2002 10:57 PM Subject: Re: [USR-TC] Help with LPBK/D-ALM
I believe it has to do with the versions of code on the HiperArc and/or NMC. My chassis that shows NFAS Settings is a newer unit we purchased used a few years ago, and it is running 5.1.99 on the HiperArc and 6.2.17 on the NMC. The chassis with no NFAS is running 4.1.22 on the HiperArc and 5.5.5 on the NMC.
Actually, I guess the NFAS would be dependent on just the HiperArc code.
Something else I've found digging around, when I pull the PRI out of the card, TCM show the red alarm LED, but the actual card shows no alarm. And from the CLI if I run "sh modem_group slot:x" this card shows 24 modems available rather than 23 like all the other DSPs show, which makes me think the card is stuck in some type of channelized T1 mode and/or it is malfunctioning.
These cards supposedly came from an ISP that liquidated it's hardware, but as to whether or not these DSPs came from previously working units or a shelf of spare unknown cards I don't know. Regardless, I'm planning to contact the merchant and arrange for some different cards to try. Because the original code on these cards when I got them was so old, I'm leaning toward thinking that these were shelved cards that weren't in production use for awhile.
I've checked and rechecked the code version on these new cards against my working ones and they all check out at 2.1.9 in the inventory. I'll run through tomorrow and try some older code, but I have a hunch that based off what I've seen this evening, the card is not going to run right.
If all goes well hopefully I'll be trying this again within a week :)
Thanks for all the useful feedback. I've at least got a few more notes in my 3com troubleshooting notebook.
Regards, Lee
Seth Jacobs wrote:
I'm curious as to why one chassis would show an NFAS setting and another would not.
One thing we've found is that if a card doesn't work, sometimes if we reinstall with an early version of DSP code (e.g.., 2.0.19) and then step through the upgrades until we get to our current code level (e.g., 3.5.100) it will fix things.
Sorry I can't be of more help.
Seth
_______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc