IP Telephony - NBX
cancel
Showing results for 
Search instead for 
Did you mean: 

V3000 Analog lines go to Unknown status

tjryberg
Occasional Contributor

V3000 Analog lines go to Unknown status

One of our client's V3000 has a couple of analog lines that quit working. When you look at them in the NBX, the status shows they are "unknown".



This seems to happen randomly and only to the ports on the V3000 chassis itself (analog card/ports on the expansion chassis work fine)



The only solution I've found is to reboot the NBX. Any thoughts?

14 REPLIES
merlin_1
Super Advisor

Re: V3000 Analog lines go to Unknown status

I would open up a case. Not sure what is going on but it seems that the NBX and the TLIM ports are losing sitr of each other . Whats the network like ? IPOTF or ethernet only protocol on the NBX ?

tjryberg
Occasional Contributor

Re: V3000 Analog lines go to Unknown status

Striaght Ethernet, no IPOTF.



Setup is fairly simple, 6 POTS lines into the V3000 and it's expansion chassis. The chassis and phones are connected via a 2626pwr (I think it's a 2626).



The only semi-unique thing is that there is a Cat6 cross-connect between the 2626 to a 4500 on the other side of the office, which supplies connectivity (and power) to the rest of the phones in the office.



Some users on the 4500 side have complained about it being hard to hear callers, but that seems to be a random issue. People on the 2626 have no complaints.

tjryberg
Occasional Contributor

Re: V3000 Analog lines go to Unknown status

Oh, and they're all using 3102s. Two of the phones have the attendant consoles.

This message was edited by tjryberg on 4-3-09 @ 8:43 AM
merlin_1
Super Advisor

Re: V3000 Analog lines go to Unknown status

If you remove the network connection , can you see if you can re establish the tlim port connection thru a hub to see if the tlims re appear ? Unplug the network cable and plug into a hub , and uplink to the switch then monitor until they fail . A trace at this time would be very helpful as well. When the issue occurs , take out the uplink to the network , have a pc ready and see if you can browse in and find a status on the tlims , also pull out the nboss , and a network trace would help as we can see why the msg's are not being sent between the NBX and the TLIM board internally via the network trace . I would open a case and see what the data reveals .

MBlank
Advisor

Re: V3000 Analog lines go to Unknown status

Make sure you have the newest firmware revision on the Network switch.

Mike Blank

LeBlanc Communications

Mike Blank

LeBlanc Communications

tjryberg
Occasional Contributor

Re: V3000 Analog lines go to Unknown status

Thanks, all. Next time it fails, I'll hook up my laptop and see what I can see.



Only challenge is the whole office will be down while the NBX is off the network.

indmillert
Occasional Visitor

Re: V3000 Analog lines go to Unknown status

We have the EXACT same problem on a V3001R with an external SS chassis with 4 line cards in it. ALL 4 line cards (and all 4 ports on each) go to an UNKNOWN status all of a sudde and WILL NOT come back until you pull the power on the Chassis. We have upgraded the OS on the NBX to the last version prior to 6.5 and have upgraded the 3Com 5500 switches to 3.03.02P01S56. We have also made sure that all the ports on the switch etc are set to a Fixed speed and duplex as recommended. I cannot find ANY reason why this is happening. HELP!

indmillert
Occasional Visitor

Re: V3000 Analog lines go to Unknown status

Here is what we see in the NBosslog file:





0619:182631:0134 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:182635:0230 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:f9:d3

0619:182635:0230 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:182639:0326 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:f9:d3

0619:182639:0326 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:182643:0423 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:f9:d3

0619:182643:0423 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:182647:0519 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:f9:d3

0619:182647:0519 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:182651:0615 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:f9:d3

0619:182651:0615 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:182655:0711 Dnld W fnTimeOut: exceeded pkt resend count reseting

0619:183203:0576 CDR E m_bWriteCallDetailRecord() - Error opening CDR Temp file.

0619:200926:0576 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:cf

0619:200926:0576 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:200926:0596 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:d7

0619:200926:0596 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:200926:0749 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:c3

0619:200926:0749 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:200931:0096 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:c3

0619:200931:0096 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:200931:0115 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:d7

0619:200931:0115 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:200935:0211 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:d7

0619:200935:0211 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:200935:0211 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:c3

0619:200935:0211 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:200939:0307 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:c3

0619:200939:0307 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:200939:0307 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:d7

0619:200939:0307 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:200943:0403 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:d7

0619:200943:0403 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:200943:0403 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:c3

0619:200943:0403 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:200947:0499 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:c3

0619:200947:0499 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:200947:0499 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:d7

0619:200947:0499 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:200951:0596 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:d7

0619:200951:0596 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:200951:0596 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:c3

0619:200951:0596 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:200955:0692 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:d7

0619:200955:0692 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:200955:0692 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:c3

0619:200955:0692 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:200959:0788 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:d7

0619:200959:0788 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:200959:0788 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:c3

0619:200959:0788 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201003:0884 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:c3

0619:201003:0884 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201003:0884 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:d7

0619:201003:0884 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201007:0980 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:d7

0619:201007:0980 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201007:0980 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:c3

0619:201007:0980 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201012:0076 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:c3

0619:201012:0076 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201012:0076 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:d7

0619:201012:0076 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201016:0173 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:c3

0619:201016:0173 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201016:0173 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:d7

0619:201016:0173 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201020:0269 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:d7

0619:201020:0269 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201020:0269 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:c3

0619:201020:0269 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201024:0365 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:c3

0619:201024:0365 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201024:0365 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:d7

0619:201024:0365 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201028:0461 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:d7

0619:201028:0461 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201028:0461 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:c3

0619:201028:0461 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201032:0557 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:c3

0619:201032:0557 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201032:0557 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:d7

0619:201032:0557 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201036:0980 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:d7

0619:201036:0980 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201036:0980 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:c3

0619:201036:0980 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201041:0076 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:c3

0619:201041:0076 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

0619:201041:0076 Dnld W fnTimeOut: Resending data packet MAC 00:e0:bb:36:75:d7

0619:201041:0076 Dnld W fnTimeOut: State 2 - Operation 1001 - next state 2

merlin_1
Super Advisor

Re: V3000 Analog lines go to Unknown status

when you RMA the unit(s) please send me the rma info so we can take a look at the unit ?



Is it warranty or contract ?

Also the S/N will help on the units .

indmillert
Occasional Visitor

Re: V3000 Analog lines go to Unknown status

Warranty. We have an open SR with support on this but we're not being told to RMA at this point. Thoughts?

merlin_1
Super Advisor

Re: V3000 Analog lines go to Unknown status

whats the SR # ?

VonRyan
Occasional Visitor

Re: V3000 Analog lines go to Unknown status

What was the solution to the problem? My customer is having the same problem.

The V3001 all the ATA and analog ports go unknown have to reboot the system to restore them.



Thanks

merlin_1
Super Advisor

Re: V3000 Analog lines go to Unknown status

what software version and type of system ? Are you running sip ?

VonRyan
Occasional Visitor

Re: V3000 Analog lines go to Unknown status

V3001R USING

Version: R6_5_20

Not Runing SIP

This message was edited by VonRyan on 9-3-09 @ 4:41 PM