cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3511
Views
0
Helpful
12
Replies

LEDs for a DSL interface on a cisco 2921 router

Hi,

I'm dealing with a 2921 router, a VDSL2 HWIC card, and a DSL line. Currently the line is connected to a modem which is connected to the router via ethernet and it all works fine.

I'm trying to use the HWIC card to connect directly with the service provider avoiding the modem.

The configuration on the router is ready but I think that's not the issue right now.

Just to clarify this: I did use the "no shutdown" command at the interface, and it works fine while connected to the modem so the line is powered on for sure.

First I connect the line to the router.

Then wait for a while (even more than 2 minutes).

Run the "show ip interface brief" command, and the interface still shows with the Status = Down; Line protocol = Down.

I'm thinking may be there is something wrong with the card, the LEDs at any time are:

  • EN = solid green.
  • CD = blinking green.
  • LP = turned off.

It doesn't matter wheter I connect or disconnect the line, turn on or off the interface, these LEDs remain that way.

Is there something wrong with the interface? or it might be possible that the line turns off when connect it to my router and then detect when I re-connect it to the modem so it turns on again (Highly doubt it).

Thanks in advanced for any help.

Regards.

12 Replies 12

paolo bevilacqua
Hall of Fame
Hall of Fame

You can not connect a VDSL2 HWIC to an ADSL circuit. it will not work, and there is no way or configuration that will make it work.

http://www.cisco.com/en/US/prod/collateral/routers/ps10536/data_sheet_c78-584157_ps10536_Products_Data_Sheet.html

You need HWIC-1ADSL for ADSL or ADSL2 or ADSL2+ circuit.

Sorry, I'm not really sure what type of interface I have, but I have a similar card already working with another ISP line.

How can I look in the router the type of interface I have?

I found only this info, not sure if it helps:

Router#show version

...

2 DSL controllers

...

2 ATM interfaces

...

Router#show controllers atm0/1/0

Interface: ATM0/1/0, Hardware: MPC ATMSAR, State: administratively down

IDB: 0x2ABBD09C  Instance: 0x30842D1C  PHY Inst: 0x00000000  us_bwidth: 1024

Slot:    0         Unit:     1         pkt Size: 4528

Sar ctrl queue: max depth = 0, current queue depth = 0,

                drops = 0, urun cnt = 0, total cnt = 0

VC TX ring stats:

VCD  VPI  VCI  High_Watermark  Low_Watermark  Queue_Depth

=========================================================

VC QoS Summary

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

  Active            Scheduled

VCD VPI VCI  COS ST     COS       PCR  SCR/MCR

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

OAM statistics (vcd/count/drop)

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

1/0/0  2/0/0  3/0/0  4/0/0

Misc Oam Drops: 0

ATM Encap Mapping

                                                Tx Congestion

Entry MAC address    VPI/VCI   VCD sts       set        clr     fastsend   safestart    drops

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

Router#show ip interface brief

...

ATM0/0/0                   unassigned      YES NVRAM up                    up

ATM0/0/0.1                 unassigned      YES unset  up                    up

ATM0/1/0                   unassigned      YES NVRAM  down down

ATM0/1/0.1                     YES manual down down

The last command shows that atm0/0/0 is already working (with an ISP1) while atm0/1/0 (with ISP2) doesn't.

Thanks.

You can known what you have reading the interface label, or doing "show diag"

Please post the output to the command "sh inventory".

Router# show diag

....

WIC Slot 1:

HWIC MULTI VDSL over POTS

Hardware Revision        : 1.0

Top Assy. Part Number    : 800-34635-01

Part Number              : 73-13372-02

Board Revision           : A0

Deviation Number         : 0

Fab Version              : 02

PCB Serial Number        : FOC15263F4N

RMA Test History         : 00

RMA Number               : 0-0-0-0

RMA History              : 00

Product (FRU) Number     : EHWIC-VA-DSL-A

Version Identifier       : V01

CLEI Code                : COUIA8YCAA

EEPROM format version 4

EEPROM contents (hex):

  0x00: 04 FF 40 07 1B 41 01 00 C0 46 03 20 00 87 4B 01

  0x10: 82 49 34 3C 02 42 41 30 88 00 00 00 00 02 02 C1

  0x20: 8B 46 4F 43 31 35 32 36 33 46 34 4E 03 00 81 00

  0x30: 00 00 00 04 00 CB 92 45 48 57 49 43 2D 56 41 2D

  0x40: 44 53 4C 2D 41 00 00 00 00 89 56 30 31 20 D9 02

  0x50: 40 C1 C6 8A 43 4F 55 49 41 38 59 43 41 41 FF FF

  0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

  0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

...

Router# show inventory

...

NAME: "ADSL/VDSL over POTS supporting ADSL1, ADSL2, ADSL2+ and VDSL2 on Slot 0 SubSlot 1", DESCR: "ADSL/VDSL over POTS supporting ADSL1, ADSL2, ADSL2+ and VDSL2"

PID: EHWIC-VA-DSL-A    , VID: V01 , SN: FOC15263F4N

...

I hope that can help you to help me

Regards.

Ok, can you please post relevant configuration now.

Router# show run interface a0/1/0.1

interface ATM0/1/0.1 point-to-point

ip address

no ip redirects

no ip unreachables

no ip proxy-arp

ip nat outside

ip virtual-reassembly in

pvc 0/33

  encapsulation aal5snap

!

end

That was working with another line weeks ago, I understand it doesn't necessarily means it has to work now. However, as I said before, the interface is showing a "Status = down" (no shutdown command already set), so I don't think the interface configuration is relevant since the problem should be still at layer 1.

Could it be possible that the interface card is damaged? how could I check that?

Can you please post all the relevant configuration, that includes

controller vdsl 1

and

interface atm0/1/0

Router#sh controllers a0/1/0

Interface: ATM0/1/0, Hardware: MPC ATMSAR, State: down

IDB: 0x2ABBD09C  Instance: 0x30842D1C  PHY Inst: 0x00000000  us_bwidth: 1024

Slot:    0         Unit:     1         pkt Size: 4528

Sar ctrl queue: max depth = 0, current queue depth = 0,

                drops = 0, urun cnt = 0, total cnt = 0

VC TX ring stats:

VCD  VPI  VCI  High_Watermark  Low_Watermark  Queue_Depth

=========================================================

VC QoS Summary

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

  Active            Scheduled

VCD VPI VCI  COS ST     COS       PCR  SCR/MCR

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

OAM statistics (vcd/count/drop)

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

1/0/0  2/0/0  3/0/0  4/0/0

Misc Oam Drops: 0

ATM Encap Mapping

                                                Tx Congestion

Entry MAC address    VPI/VCI   VCD sts       set        clr     fastsend   safestart    drops

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

Router# sh int a0/1/0

ATM0/1/0 is down, line protocol is down

  Hardware is MPC ATMSAR, address is 2c3f.382f.13f6 (bia 2c3f.382f.13f6)

  MTU 1600 bytes, sub MTU 1600, BW 1024 Kbit/sec, DLY 360 usec,

     reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation ATM, loopback not set

  Keepalive not supported

  Encapsulation(s): AAL5

  4 maximum active VCs, 1024 VCs per VP, 0 current VCCs

  VC Auto Creation Disabled.

  VC idle disconnect time: 300 seconds

  Last input never, output 1w0d, output hang never

  Last clearing of "show interface" counters never

  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

  Queueing strategy: Per VC Queueing

  5 minute input rate 0 bits/sec, 0 packets/sec

  5 minute output rate 0 bits/sec, 0 packets/sec

     3 packets input, 584 bytes, 0 no buffer

     Received 0 broadcasts (0 IP multicasts)

     0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

     767 packets output, 51375 bytes, 0 underruns

     0 output errors, 0 collisions, 16 interface resets

     0 unknown protocol drops

     0 output buffer failures, 0 output buffers swapped out

Router#sh int a0/1/0.1

ATM0/1/0.1 is down, line protocol is down

  Hardware is MPC ATMSAR, address is 2c3f.382f.13f6 (bia 2c3f.382f.13f6)

  Internet address is

  MTU 1600 bytes, BW 1024 Kbit/sec, DLY 360 usec,

     reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation ATM

  Keepalive not supported

     3 packets input, 572 bytes

     767 packets output, 51375 bytes

     0 OAM cells input, 0 OAM cells output

  AAL5 CRC errors : 0

  AAL5 SAR Timeouts : 0

  AAL5 Oversized SDUs : 0

  Last clearing of "show interface" counters never

I forgot the VDSL controller:

Router# show controllers VDSL0/1/0

Controller VDSL 0/1/0 is DOWN

Daemon Status:           Establishing Link

                        XTU-R (DS)              XTU-C (US)

Chip Vendor ID:         'BDCM'                   'IFTN'

Chip Vendor Specific:   0x0000                   0x71B9

Chip Vendor Country:    0xB500                   0xB500

Modem Vendor ID:        'CSCO'                   '    '

Modem Vendor Specific:  0x4602                   0x0000

Modem Vendor Country:   0xB500                   0x0000

Serial Number Near:    FOC15263F4N 2921/K9  15.1(4)M

Serial Number Far:

Modem Version Near:    15.1(4)M

Modem Version Far:     0x71b9

Modem Status:            Idle

DSL Config Mode:         AUTO

Trained Mode:

TC Mode:                 ATM

Selftest Result:         0x00

DELT configuration:      enabled

DELT state:              successful

Trellis:                 ON                       ON

Full inits:             1

Failed full inits:      1

Short inits:            0

Failed short inits:     0

Firmware        Source          File Name (version)

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

VDSL            embedded        VDSL_LINUX_DEV_01212008 (1)

Modem FW  Version:      110506_1916-4.02L.03.A2pv6C032b.d23i

Modem PHY Version:      A2pv6C032b.d23i

Training Log :  Stopped

Training Log Filename : flash:vdsllog.bin

Can you try

controller vdsl 1

mode adsl

or adsl2, adsl2+ depending from your circuit.

Also, can you try updating DSL firmware to

vdsl.bin-A2pv6C035d_d23j

that is available under downloads for 887VA. Note you may need to contact the TAC to obtain this file.

Thank you very much for the help, it may take a while to try this (a few days) but I'll be comming back here, hopefully to confirm that was the solution.

Thanks again and see you soon,

Ricardo.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco