Re: some ports of NM-16AM is not workin, WHY?

gomesrichard · ‎01-18-2003

I am using a 3662 router, populated with 4x NM-16AM. Some ports of the 2nd module are not answering call. If I call those ports from regular telephone, it just rings, do not pick-up the call. Other ports are working fine.

My 3662 router has

1) Grounded chassis with Cisco recmndn.

2) Telephone lines are also surg-protected.

Why some ports are not working of NM-16AM?

Thanks

Richard

makchitale · ‎01-18-2003

1) Where these ports working fine earlier but stopped working recently?

2)Can you reverse telnet into one of there modems (that do not answer incomming calls) & try dialing out using ATDTxxxxxxx.

3)Just for sanity check what if we move the POTS line from a known working modem to the so called faulty modem...any change?

4)Can try swapping the NM-16AM (2nd module) with any other in that chassis, does the problem follow / remain / maybe go away?

Based on the above can say whether it's a possible hardware issue.

Thanks, Mak.

gomesrichard · ‎01-18-2003

Hi Mak,

Thanks for your reply.

1)Yes, these ports were working fine, but suddenly stopped working.

2) I can reverse telnet these ports and response of at command is 'ok'. I did not dialout from these ports , I will let you know.

3)Yes, all the telephone lines are jacked in.

4) Swapping the modules did not help us.

DO you know any firmware revision or patch for this issue?

Thanks and regards

Richard

gomesrichard · ‎01-18-2003

Hi Mak,

Below is the info's you may require. You can see from SH MODEM 2/6( and also for 1/13), the status of protocol and compression is unknown, but for SH MODEM 1/11 there are entries for protocol and compression( LAPM and V42bis).

And My

1) IOS version is: IOS (tm) 3600 Software (C3660-I-M), Version 12.2(7c), RELEASE SOFTWARE (fc1)

2) MOdem version: MCOM firmware: 1.3.3, Modem firmware: 2.3.17, DSP firmware: 0.0.2

3640#sh ver

Cisco Internetwork Operating System Software

IOS (tm) 3600 Software (C3660-I-M), Version 12.2(7c), RELEASE SOFTWARE (fc1)

Compiled Sat 11-May-02 09:26 by pwade

Image text-base: 0x600089C0, data-base: 0x60A60000

ROM: System Bootstrap, Version 12.0(6r)T, RELEASE SOFTWARE (fc1)

3640 uptime is 5 days, 12 minutes

System returned to ROM by power-on

System image file is "flash:c3660-i-mz.122-7c.bin"

cisco 3660 (R527x) processor (revision 1.0) with 28672K/4096K bytes of memory.

Processor board ID JAB0529816M

R527x CPU at 225Mhz, Implementation 40, Rev 10.0, 2048KB L2 Cache

Bridging software.

X.25 software, Version 3.0.0.

3660 Chassis type: ENTERPRISE

2 FastEthernet/IEEE 802.3 interface(s)

64 terminal line(s)

DRAM configuration is 64 bits wide with parity disabled.

125K bytes of non-volatile configuration memory.

8192K bytes of processor board System flash (Read/Write)

Configuration register is 0x201

----------------------------------------------------------------------------------------------

3640#sh modem 2/6

Mdm Typ Status Tx/Rx G Duration TX RX RTS CTS DSR DCD DTR

2/6 Unkn Idle 0/0 1 00:00:00 - - x

Modem 2/6 [line 71], Async71, TTY71

MCOM firmware: 1.3.3, Modem firmware: 2.3.17, DSP firmware: 0.0.2

Modem config: Incoming and Outgoing

Protocol: Unkn, Compression: Unkn

Management port config: AT session

Last clearing of "show modem" counters: never

0 incoming completes, 0 incoming failures

0 outgoing completes, 0 outgoing failures

0 failed dial attempts, 0 ring no answers, 0 busied outs

0 no dial tones, 0 dial timeouts, 0 watchdog timeouts

0 no carriers, 0 link failures, 0 resets, 0 recover oob

0 protocol timeouts, 0 protocol errors, 0 lost events

0/0 speedshifts initiated/accepted, 0/0 retrains initiated/accepted

3640#sh modem 1/13

Mdm Typ Status Tx/Rx G Duration TX RX RTS CTS DSR DCD DTR

1/13 Unkn Idle 0/0 1 00:00:00 - - x

Modem 1/13 [line 46], Async46, TTY46

MCOM firmware: 1.3.3, Modem firmware: 2.3.17, DSP firmware: 0.0.2

Modem config: Incoming and Outgoing

Protocol: Unkn, Compression: Unkn

Management port config: AT session

Last clearing of "show modem" counters: never

0 incoming completes, 0 incoming failures

0 outgoing completes, 0 outgoing failures

0 failed dial attempts, 0 ring no answers, 0 busied outs

0 no dial tones, 0 dial timeouts, 0 watchdog timeouts

0 no carriers, 0 link failures, 0 resets, 0 recover oob

0 protocol timeouts, 0 protocol errors, 0 lost events

0/0 speedshifts initiated/accepted, 0/0 retrains initiated/accepted

3640#sh modem 1/11

Mdm Typ Status Tx/Rx G Duration TX RX RTS CTS DSR DCD DTR

1/11 V34 Conn 19200/19200 1 00:04:50 - - x

Modem 1/11 [line 44], Async44, TTY44

MCOM firmware: 1.3.3, Modem firmware: 2.3.17, DSP firmware: 0.0.2

Modem config: Incoming and Outgoing

Protocol: LAPM, Compression: V42bis

Management port config: AT session

Last clearing of "show modem" counters: never

456 incoming completes, 22 incoming failures

0 outgoing completes, 0 outgoing failures

0 failed dial attempts, 0 ring no answers, 0 busied outs

0 no dial tones, 0 dial timeouts, 0 watchdog timeouts

22 no carriers, 0 link failures, 0 resets, 0 recover oob

0 protocol timeouts, 0 protocol errors, 0 lost events

0/0 speedshifts initiated/accepted, 406/251 retrains initiated/accepted

Modulation type V32bis V34

# of connections 3 453

I guess this is a modem firmware-IOS version conflict( ?).

Thanks

Richard

makchitale · ‎01-19-2003

When you say swapping the module did not help...will be good to understand the following:

The module with problem (in the 2nd slot) when moved to say the 3rd slot.

1)If the problem followed.....maybe a faulty modem on that module.

2)If problem remains still in the 2nd slot (but now with module from 3rd slot)...maybe we have some issue on that particular slot in the chassis.

Don't feel it's a software issue but more likely a hardware one.

Thanks, Mak.

tepatel · ‎01-19-2003

Since you are getting the response from modem for AT commands, it seems that the modem are responsive. Enter following commands

ATS0=1

Now you can keep the reverse telnet session open to the modem and callin to the same modem using another modem. Once the modem receive the ring, it will display RING in reverse telnet session and the modem will pick the line up after one ring.

After CONNECT is exchanged, type some chars on reverse telnet and it should be displayed as it is on hyperterminal session and vice versa.

It it is, modems are working fine. If not, it can be the hardware issue. Modems may have went bad. If swapping those modems with new modem module results the same problem one same modem ports, the slot on that chassis could be bad as well.

gomesrichard · ‎01-19-2003

Hi Mak and Tepatel,

Thanks for your reply.

1) What does this command do, ATS0=1?

2) First, from hyper-terminal session

a) I reverse telnet into 2/6( bad port) modem

b) put ATS0=1

c) put ctrl+shft+6 and x

d) again reverse telnet from 2/3( good port)

e) type some chars

f) check whether these chars are displayed in the 1/1 reverse telnet session.

3) Why this port 2/6 shows this:

Protocol: Unkn, Compression: Unkn, ....................it should be

Protocol: LAPM, Compression: V42bis.

All other good ports are showing the 2nd entry when I put "sh modem x/y".

Thanks and regards

Richard

makchitale · ‎01-20-2003

ATs0=1 means the modem should answere call after 1st RING in.

The procedure should be as follows:

1)Reverse telnet into 2/6( bad port) modem ..remain there.

2)Dial into the same modem from another modem using hyper term....after we see a CONNECT...type the characters to see if they are seen on the other end.

Thanks, Mak.

gomesrichard · ‎02-18-2003

Hi Mak,

We have done these tests. But when we tried to dial from one modem to another, it showed 'NO DialTone' message. It's also showing for good modems.

Thanks

Richard

makchitale · ‎02-18-2003

<3660>16AM-------POTS line---PSTN cloud------POTS line---modem

I understand you did the following:

1)Reverse telnet into a modem (bad) from the 3660.Type ATs0=1 & remain reverse telnetted into the modem.

2)Dial into the same modem from another modem (PC) using hyper term....after we see a CONNECT...type the characters to see if they are seen on the other end.

If the above was tried & still did not work then it could be a bad hardware.

Regarding the "no dial tone" ...what if we connect an regular telephone to the same POTS line, do we get a dial tone?

Analyzing all your postings appears to be a possible hardware issue.

Thanks, Mak.

gomesrichard · ‎02-19-2003

Mak,

We have 4x NM-16AM, and in the sh ver command output we heve 64 Async lines. If it is h/w fault, should it be in the sh ver output? I am just asking.

I will you the result of your test again. Right now I'm out-off-site.

Thank you very much.

Richard

makchitale · ‎02-20-2003

The show ver / show diag / show run (lines x y) will still show them as 64 async lines even if we have a few faulty modems on the cards, here the presence of hardware is recognized by IOS & reported.

Thanks, Mak.