[cisco-nas] Cisco3640 NM-16AM analog modem configuration problem

[Aaron Leonard]

> Dear Aaron,

> Thank for your assistance. Actually, I have followed this instruction 
> to configure my NAS:
> http://www.cisco.com/en/US/products/hw/modules/ps2797/products_configuration_example09186a00800e0dcd.shtml

That's a good example.

> However, it doesn't work for me. This is the modem log rigth after the
> NAS has been reloaded:

> sh modem log 1/0
> Modem 1/0 Events Log:
> 00:01:27.252 DC session request: AT-I1Z
> 00:01:27.252 RS232: noCTS* DSR* noDCD* noRI  noRxBREAK  TxBREAK*
> 00:01:27.252 MSMP Reset
> 00:01:27.252 RS232: CTS* DSR  noDCD  noRI  noRxBREAK  TxBREAK
> 00:01:27.252 PPP escape maps set: TX map=00000000 RX map=FFFFFFFF
> 00:01:27.252 DTR set high
> 00:01:27.252 Modem disabled

> Is that normal status ? 

Yes, you can see that.

> Also when I pluged RJ11 phone jack on the modem port and unplug. The
> modem active led is green (modem active), and when I use "show
> interface command" I got the following:

Here's what I would do.

1. Be sure that either your AC power cable or chassis is properly
grounded.  The NM-AM modems will not work without a proper ground.

2. Be sure that you are running at least firmware 1.2.2.
I.e. be running at least 12.1(3.1+) 12.1(3.3+)T, or else 
load in 1.2.2 from http://www.cisco.com/pcgi-bin/tablebuild.pl/x600-analog .

3. Dial into a modem from a handset and be sure that you hear
good 2100Hz answer tone.  If not, and if your POTS line is good
(i.e. if you connect an external modem to it, and that modem 
answers), and if your router is correctly configured, then
I would say that your NM-16AM is bad.

Aaron

---

> ras3#sh interfaces async 33
> Async33 is up (spoofing), line protocol is up (spoofing)
> modem(slot/port):1/0, csm_state:CSM_CONNECT_INITIATED_STATE,
> bchan_num:-1 csm_status: CALL_ACTIVE

>   Hardware is MCOM Integrated Modem Controller
>   Interface is unnumbered. Using address of Ethernet0/0 (10.6.20.4)
>   MTU 1500 bytes, BW 9 Kbit, DLY 100000 usec,
>      reliability 255/255, txload 1/255, rxload 1/255
>   Encapsulation PPP, loopback not set
>   Keepalive not set
>   DTR is pulsed for 5 seconds on reset
>   LCP Closed
>   Closed: IPCP
>   Last input never, output never, output hang never
>   Last clearing of "show interface" counters 00:08:29
>   Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
>   Queueing strategy: weighted fair
>   Output queue: 0/1000/64/0 (size/max total/threshold/drops)
>      Conversations  0/0/16 (active/max active/max total)
>      Reserved Conversations 0/0 (allocated/max allocated)
>      Available Bandwidth 6 kilobits/sec
>   5 minute input rate 0 bits/sec, 0 packets/sec
>   5 minute output rate 0 bits/sec, 0 packets/sec

> Please help me to indentify the problem.

> Regards,
> Souphonh

> ----- Original Message -----
> From: "Aaron Leonard" <Aaron at cisco.com>
> To: "Souphonh" <souphonh at laopdr.com>
> Cc: <cisco-nas at puck.nether.net>
> Sent: Wednesday, September 17, 2003 11:33 PM
> Subject: Re: [cisco-nas] Cisco3640 NM-16AM analog modem configuration problem


> > > Dear All,
> >
> > > I have very little experience with Cisco nas configuration. Now
> > > I am configuring Cisco3640 with NM-16AM analog modem module. IOS
> > > image file is c3640-i-mz.122-8.T1. After the configuration, I use
> > > command "sh interface asyn 33" The speed of the line is 9.6 K, and
> > > could not answer any PPP connection. Could you please suggest what
> > > is possible problem.
> >
> > > Many thanks.
> > > Souphonh
> >
> > Welcome Souphonh.
> >
> > Here's a sample configuration to use for starters:
> > http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fdial_c/fnsprt12/dafspex.htm#1000911
> > "Individual Remote PCs Using Analog Modems" in
> > "Telco and ISP Dial Scenarios and Configurations".  In your case, with
> > the analog modems, you would skip the T1 controller and ISDN D channel
> > configuration part.
> >
> > If you still have problems, here are the debugs I'd use:
> >
> > config term
> >   service timestamp debug date msec
> >   modem call-record terse
> >   end
> >
> > debug modem
> > debug ppp negotiation
> > terminal monitor
> > [ have a client dial in ]
> >
> > As far as the "speed" (actually, bandwidth) shown via "show interface"
> > ... this is simply taken from the "bandwidth" command configured on
> > the async interface, and does not reflect the actual modem speed.
> > The "bandwidth" value is basically cosmetic (except insofar as it is
> > used by MLPPP and routing protocols.)
> >
> > Aaron
> >