Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1846
Views
0
Helpful
2
Replies

Cisco 877 and DSL problem too many dailys %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0

dyred
Level 1
Level 1

‎05-07-2011 11:20 AM - edited ‎03-04-2019 12:18 PM

Dear Cisco Support Community.

I have this problem with the cisco 877 router. About a month we migrate to this device in many branch offices, with adsl connections wih carrier telmex(infinitum).

And in several of these office we are having too many dailys networks breaks.

That's why i think we have a config error or similar and no line problem, besides with another modem/router it not happens.

The cisco log shows too many :

%LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down

this is my config for the conection

!
interface ATM0
no ip address
atm vc-per-vp 128
no atm ilmi-keepalive
pvc 8/35
  encapsulation aal5snap
  pppoe-client dial-pool-number 1
!
pvc 8/81
  encapsulation aal5snap
  pppoe-client dial-pool-number 1
!
dsl operating-mode auto
!

interface Dialer1
mtu 1492
ip address negotiated
ip nat outside
ip virtual-reassembly
encapsulation ppp
ip tcp adjust-mss 1452
dialer pool 1
dialer-group 1
no fair-queue
no cdp enable
ppp authentication pap callin
ppp pap sent-username xxxxxxxx password 0 xxxxxxxxxx
crypto map VPNS-GMM
!

ip route 0.0.0.0 0.0.0.0 Dialer1

this is my sh dsl interface atM 0

ATM0
Alcatel 20190 chipset information
                ATU-R (DS)                      ATU-C (US)
Modem Status:    Showtime (DMTDSL_SHOWTIME)
DSL Mode:        ITU G.992.5 (ADSL2+) Annex A
ITU STD NUM:     0x03                            0x2
Chip Vendor ID:  'STMI'                          'BDCM'
Chip Vendor Specific:  0x0000                    0x6193
Chip Vendor Country:   0x0F                      0xB5
Modem Vendor ID: 'CSCO'                          '    '
Modem Vendor Specific: 0x0000                    0x0000
Modem Vendor Country:  0xB5                      0x00
Serial Number Near:    FHK1449760Q
Serial Number Far:
Modem VerChip ID:        C196 (3)
DFE BOM:         DFE3.0 Annex A (1)
Capacity Used:   24%                             51%
Noise Margin:    28.5 dB                         23.5 dB
Output Power:    19.5 dBm                        11.5 dBm
Attenuation:     34.5 dB                         21.0 dB
Defect Status:   None                            None
Last Fail Code:  None
Watchdog Counter: 0x96
Watchdog Resets: 1
Selftest Result: 0x00

Interrupts:      21271 (0 spurious)
PHY Access Err:  0
Activations:     35
LED Status:      ON
LED On Time:     100
LED Off Time:    100
Init FW:         init_AMR_4.0.017.bin
Operation FW:    AMR-E-4.0.017.bin
FW Source:       external
FW Version:      4.0.17

                 DS Channel1      DS Channel0   US Channel1       US Channel0
Speed (kbps):             0             4095             0               636
Cells:                    0           445621             0          12633309

Reed-Solomon EC:          0                0             0                 0
CRC Errors:               0                0             0                 0
Header Errors:            0                0             0                 0
Total BER:                0E-0           0E-0
Leakage Average BER:      0E-0           0E-0
Interleave Delay:         0                2             0                40
                        ATU-R (DS)      ATU-C (US)
Bitswap:               enabled            enabled
Bitswap success:          0                   0
Bitswap failure:          0                   0

LOM Monitoring : Disabled

Notice how many Activations:     35 this is exactly the number of network break we had since reboot

We have :

Cisco IOS Software, C870 Software (C870-ADVIPSERVICESK9-M), Version 12.4(15)T14,
RELEASE SOFTWARE (fc2)

and i have try with firmware embedde dFW:    AMR-3.0.014.bin

and with external AMR-E-4.0.017.bin

with no luck

Any advices will be apreciate

Sincerely,

Ivanoff Capetillo

Labels:
0 Helpful
2 Replies 2

hhasolka
Cisco Employee
Cisco Employee

‎05-11-2011 09:08 AM

Hi there!

Looking at the output that you pasted , could be a layer 1 issue as you suspected. The activation counter shows the value from the last reload so there is no expected value as such that we can compare this couter to.

Here's what I would suggest:

1/ Isolate one site that's easier for your to troubleshoot out of all the site that are experiencing the issue and focus troubleshooting that one first.

2/ Check whether this is a layer 1 issue or layer 2 flap. From what you have mentioned , looks like a layer 1 issue though I am not sure why you didn't see a layer 1 down error as well in the log.

3/ You can enable the following command before enabling any debugging:

no logging console

logging buffer 2000000

This will make sure that you are not overloading the CPU in anyway and all the debug output will be sent to the log  buffer. You can retrieve it with show log command.

Then start debug atm event, debug atm error. This will tell you if the physical link went down or only the layer 2 only went down.

4/ Make sure there are no errors on that interface throughout the day incrementing consistently.

5/ Get the platform information from your ISP for the DSLAM they are using where you are seeing a lot of activations.

6/ Getting show interface output after the flap won't help as the errors might have incrementing during the line synch up so gather outputs other times of the day when the line is stable. See how many times this happens per day and if incrementing errors on the show interface command lead to this type of flap.

7/ We will have to get a training log before and after flap after enabling an hidden command so that we can check how the negotiation parameters and line conditions in detail.

7/ Gather the above information and open a TAC case , this way a CSE can enable some more internal logs and debug this further. This would require exchange of multilink show command output/debugs so it's better to handle this issue in a proper TAC case.

Hope this helps!

-

Harshad Hasolkar

Senior Network Engineer

Carrier Services, TAC

0 Helpful

dyred
Level 1
Level 1
In response to hhasolka

‎05-11-2011 03:27 PM

Hello Harshad.

I am doing the steps you kindly told us.

this is log after too network breaks:

May 11 19:32:36.006: ATM0:atmsar_dequeue_pak, dequeued a pak = 0x830840DC
May 11 19:32:36.006: atmsar_transmit_pak_wrapper: deq(830840DC). vcd: 1.atmsar_t
ransmit_pak_wrapper : encap = Data
May 11 19:32:38.594: DSL(ATM0): Defect: LOM
May 11 19:32:38.594: DSL(ATM0): Defect: LCDf: retraining
May 11 19:32:38.594: DSL(ATM0): Received response: 0x41
May 11 19:32:39.646: atmsar_vc_tx_start(832CED38).
May 11 19:32:39.646: ATM0:atmsar_dequeue_pak, dequeued a pak = 0x8380E8D0
May 11 19:32:39.646: atmsar_transmit_pak_wrapper: deq(8380E8D0). vcd: 1.atmsar_t
ransmit_pak_wrapper : encap = Data
May 11 19:32:40.542: atmsar_vc_tx_start(832CED38).
May 11 19:32:40.542: ATM0:atmsar_dequeue_pak, dequeued a pak = 0x84B44D9C
May 11 19:32:40.542: atmsar_transmit_pak_wrapper: deq(84B44D9C). vcd: 1.atmsar_t
ransmit_pak_wrapper : encap = Data
May 11 19:32:41.094:  atmsar_atm_lineaction(ATM0): state=0
May 11 19:32:41.094: ATM0: atmsar_1a_teardown_vc,vcinfo = 0x842D3E9C
May 11 19:32:41.094:  atmsar_1a_teardown_vc(ATM0): vc:1 vpi:8 vci:35
May 11 19:32:41.094:  Fill up paramaters for PVC 8/81[2] - Request for CoS 0 PCR
0 SCR 0 MCR 0 Available 384
May 11 19:32:41.094: ATM(): IP multicast cache invalidated for ATM0
May 11 19:32:41.094: ATM0: atmsar_1a_teardown_vc,vcinfo = 0x83E4C5CC
May 11 19:32:41.094:  atmsar_1a_teardown_vc(ATM0): vc:2 vpi:8 vci:81channel cann
ot be cleared
May 11 19:32:41.094: ATM(): IP multicast cache invalidated for ATM0
May 11 19:32:41.094: DSL: SM: [DMTDSL_SHOWTIME -> DMTDSL_RE_OPEN]
May 11 19:32:41.098: DSL(ATM0): Send ADSL_CLOSE command.
May 11 19:32:41.098: DSL(ATM0): Sent command 0x4
May 11 19:32:41.623: DSL(ATM0): Received response: 0x25
May 11 19:32:41.623: DSL(ATM0): Connection closed
May 11 19:32:41.623: DSL: SM: [DMTDSL_RE_OPEN -> DMTDSL_DO_OPEN]
May 11 19:32:41.623: DSL(ATM0): Send ADSL_OPEN command.
May 11 19:32:41.623: DSL(ATM0): Using preferred open mode
May 11 19:32:41.627: DSL(ATM0): Using ITU sync first for 5 secs, then ANSI/ITU s
ync alternatively for 2 secs
May 11 19:32:41.627: DSL(ATM0): Using subfunction 0x0
May 11 19:32:41.627: LOCAL:Max noise margin for power cutoff 31
May 11 19:32:41.627: DSL(ATM0): GPCI[0] 0x5
May 11 19:32:41.627: DSL(ATM0): GPCI[1] 0x9
May 11 19:32:41.627: DSL(ATM0): GPCI[2] 0x1
May 11 19:32:41.627: DSL(ATM0): GPCI[3] 0x0
May 11 19:32:41.627: DSL(ATM0): Sent extended command 0x3
May 11 19:32:43.095: %LINK-3-UPDOWN: Interface ATM0, changed state to down
May 11 19:32:43.095:  atmsar_atm_lineaction(ATM0): state=0
May 11 19:32:44.095: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, chang
ed state to down
May 11 19:32:44.127: DSL(ATM0): 1: Modem state = 0x8
May 11 19:32:44.863: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 172.31.254.33 (T
unnel0) is down: holding time expired
May 11 19:32:45.175: ATM0: atmsar_vc_dlcx
May 11 19:32:46.627: DSL(ATM0): 2: Modem state = 0x8
May 11 19:32:49.128: DSL(ATM0): 3: Modem state = 0x8
May 11 19:32:51.628: DSL(ATM0): 4: Modem state = 0x8
May 11 19:32:54.128: DSL(ATM0): 5: Modem state = 0x8
May 11 19:32:56.629: DSL(ATM0): 6: Modem state = 0x9
May 11 19:32:59.129: DSL(ATM0): 7: Modem state = 0x10
May 11 19:33:01.629: DSL(ATM0): 8: Modem state = 0x10
May 11 19:33:04.129: DSL(ATM0): 9: Modem state = 0x10
May 11 19:33:06.630: DSL(ATM0): 10: Modem state = 0x10
May 11 19:33:07.350: DSL(ATM0): Received response: 0x24
May 11 19:33:07.350: DSL(ATM0): Showtime!
May 11 19:33:07.350: DSL(ATM0): Sent command 0x31
May 11 19:33:07.358: DSL(ATM0): Received response: 0x12
May 11 19:33:07.358: DSL(ATM0): operation mode 0x0002
May 11 19:33:07.358: DSL(ATM0): Sent command 0x33
May 11 19:33:07.362: DSL(ATM0): Received response: 0x16
May 11 19:33:07.362: DSL(ATM0): Far End ITU Country Code 0xB5
May 11 19:33:07.362: DSL: Far End ITU Vendor ID BDCM
May 11 19:33:07.362: DSL: Far End ITU Vendor ID Specific 0x6193
May 11 19:33:07.362: DSL: Far End ITU Vendor STD Number 0x0002
May 11 19:33:07.362: DSL(ATM0): Sent command 0x32
May 11 19:33:07.370: DSL(ATM0): Received response: 0x14
May 11 19:33:07.370: DSL(ATM0): Near End ITU Country Code 0x0F
May 11 19:33:07.370: DSL: Near End ITU Vendor ID STMI
May 11 19:33:07.370: DSL: Near End ITU Vendor ID Specific 0x0000
May 11 19:33:07.370: DSL: Near End ITU Vendor STD Number 0x0003
May 11 19:33:07.370: ATM0 atmsar_update_us_bandwidth(): upstream bw =384 Kbps
May 11 19:33:07.370: DSL: SM: [DMTDSL_DO_OPEN -> DMTDSL_SHOWTIME]
May 11 19:33:15.179: ATM0: atmsar_vc_dlcx
May 11 19:33:15.179: (ATM0)1a_enable: delay activation of vcd=1, vc=0x842D3E9C
May 11 19:33:15.179: (ATM0)1a_enable: delay activation of vcd=2, vc=0x83E4C5CC
May 11 19:33:15.179: atmsar enable ATM0
May 11 19:33:15.179: ATM0: atmsar_bringup_interface: Interface and atm_db flags
are UP
May 11 19:33:16.967:  Reserved bw for 8/35 Available bw = 384
May 11 19:33:16.967: ATM0: atmsar_1a_setup_vc, vcinfo = 0x842D3E9C
May 11 19:33:16.967: ATM0 atmsar_vc_setup: vcd 1
May 11 19:33:16.967:  Fill up paramaters for PVC 8/35[1] - Request for CoS 0 PCR
0 SCR 0 MCR 0 Available 384
May 11 19:33:16.967:  Scheduler parameters for 8/35. Type UBR. PCR 384
May 11 19:33:16.967:  Total scheduled bandwidth after configuringPVC 8/35 will b
e 0
May 11 19:33:16.967: atmsar_setup_cos(ATM0): vc:1 wred_name:- max_q:0
May 11 19:33:16.967: ATM0: VC setup successful (vcd = 1)
May 11 19:33:16.967:  Reserved bw for 8/81 Available bw = 384
May 11 19:33:16.967: ATM0: atmsar_1a_setup_vc, vcinfo = 0x83E4C5CC
May 11 19:33:16.967: ATM0 atmsar_vc_setup: vcd 2

May 11 19:33:16.967:  Fill up paramaters for PVC 8/35[1] - Request for CoS 0 PCR
0 SCR 0 MCR 0 Available 384
May 11 19:33:16.967:  Fill up paramaters for PVC 8/81[2] - Request for CoS 0 PCR
0 SCR 0 MCR 0 Available 384
May 11 19:33:16.967:  Scheduler parameters for 8/81. Type UBR. PCR 384
May 11 19:33:16.967:  Total scheduled bandwidth after configuringPVC 8/81 will b
e 0
May 11 19:33:16.971: atmsar_setup_cos(ATM0): vc:2 wred_name:- max_q:0
May 11 19:33:16.971: ATM0: VC setup successful (vcd = 2)
May 11 19:33:16.971: ATM0: atmsar_atm_get_stats,vcinfo = 0x0
May 11 19:33:17.179: %LINK-3-UPDOWN: Interface ATM0, changed state to up
May 11 19:33:17.179:  atmsar_atm_lineaction(ATM0): state=4
May 11 19:33:17.675: atmsar_vc_tx_start(832CED38).
May 11 19:33:17.675: ATM0:atmsar_dequeue_pak, dequeued a pak = 0x849ABE14
May 11 19:33:17.675: atmsar_transmit_pak_wrapper: deq(849ABE14). vcd: 1.atmsar_t
ransmit_pak_wrapper : encap = Data
May 11 19:33:18.179: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, chang
ed state to up
May 11 19:33:20.604: atmsar_vc_tx_start(832CED38).
May 11 19:33:20.604: ATM0:atmsar_dequeue_pak, dequeued a pak = 0x8381D97C
May 11 19:33:20.604: atmsar_transmit_pak_wrapper: deq(8381D97C). vcd: 1.atmsar_t
ransmit_pak_wrapper : encap = Data
May 11 19:33:18.179: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, chang
ed state to up

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


May 11 20:09:32.967: ATM0:atmsar_dequeue_pak, dequeued a pak = 0x83DA0404
May 11 20:09:32.967: atmsar_transmit_pak_wrapper: deq(83DA0404). vcd: 2.atmsar_t
ransmit_pak_wrapper : encap = Data
May 11 20:09:41.736: atmsar_vc_tx_start(832CED38).
May 11 20:09:41.736: ATM0:atmsar_dequeue_pak, dequeued a pak = 0x8307F3FC
May 11 20:09:41.736: atmsar_transmit_pak_wrapper: deq(8307F3FC). vcd: 1.atmsar_t
ransmit_pak_wrapper : encap = Data
May 11 20:09:42.756: DSL(ATM0): Defect: LOM
May 11 20:09:43.360: atmsar_vc_tx_start(832CED38).
May 11 20:09:43.360: ATM0:atmsar_dequeue_pak, dequeued a pak = 0x849CADBC
May 11 20:09:43.360: atmsar_transmit_pak_wrapper: deq(849CADBC). vcd: 1.atmsar_t
ransmit_pak_wrapper : encap = Data
May 11 20:09:45.256: DSL(ATM0): Defect: LOM
May 11 20:09:47.065: ATM0: atmsar_atm_get_stats,vcinfo = 0x0
May 11 20:09:47.757: DSL(ATM0): Defect: LOM
May 11 20:09:50.257: DSL(ATM0): Defect: LOM
May 11 20:09:50.257: DSL(ATM0): Defect: LOS LOF: retraining
May 11 20:09:50.257: DSL(ATM0): Received response: 0x41
May 11 20:09:51.977: atmsar_vc_tx_start(832CED38).
May 11 20:09:51.977: ATM0:atmsar_dequeue_pak, dequeued a pak = 0x83432984
May 11 20:09:51.977: atmsar_transmit_pak_wrapper: deq(83432984). vcd: 1.atmsar_t

May 11 20:09:51.977: atmsar_transmit_pak_wrapper: deq(83432984). vcd: 1.atmsar_t
ransmit_pak_wrapper : encap = Data
May 11 20:09:52.757:  atmsar_atm_lineaction(ATM0): state=0
May 11 20:09:52.757: ATM0: atmsar_1a_teardown_vc,vcinfo = 0x842D3E9C
May 11 20:09:52.757:  atmsar_1a_teardown_vc(ATM0): vc:1 vpi:8 vci:35
May 11 20:09:52.757:  Fill up paramaters for PVC 8/81[2] - Request for CoS 0 PCR
0 SCR 0 MCR 0 Available 384
May 11 20:09:52.757: ATM(): IP multicast cache invalidated for ATM0
May 11 20:09:52.757: ATM0: atmsar_1a_teardown_vc,vcinfo = 0x83E4C5CC
May 11 20:09:52.757:  atmsar_1a_teardown_vc(ATM0): vc:2 vpi:8 vci:81channel cann
ot be cleared
May 11 20:09:52.757: ATM(): IP multicast cache invalidated for ATM0
May 11 20:09:52.761: DSL: SM: [DMTDSL_SHOWTIME -> DMTDSL_RE_OPEN]
May 11 20:09:52.761: DSL(ATM0): Send ADSL_CLOSE command.
May 11 20:09:52.761: DSL(ATM0): Sent command 0x4
May 11 20:09:53.285: DSL(ATM0): Received response: 0x25
May 11 20:09:53.285: DSL(ATM0): Connection closed
May 11 20:09:53.285: DSL: SM: [DMTDSL_RE_OPEN -> DMTDSL_DO_OPEN]
May 11 20:09:53.285: DSL(ATM0): Send ADSL_OPEN command.
May 11 20:09:53.285: DSL(ATM0): Using preferred open mode
May 11 20:09:53.285: DSL(ATM0): Using ITU sync first for 5 secs, then ANSI/ITU s
ync alternatively for 2 secs

May 11 20:09:53.289: DSL(ATM0): Using subfunction 0x0
May 11 20:09:53.289: LOCAL:Max noise margin for power cutoff 31
May 11 20:09:53.289: DSL(ATM0): GPCI[0] 0x5
May 11 20:09:53.289: DSL(ATM0): GPCI[1] 0x9
May 11 20:09:53.289: DSL(ATM0): GPCI[2] 0x1
May 11 20:09:53.289: DSL(ATM0): GPCI[3] 0x0
May 11 20:09:53.289: DSL(ATM0): Sent extended command 0x3
May 11 20:09:54.758: %LINK-3-UPDOWN: Interface ATM0, changed state to down
May 11 20:09:54.758:  atmsar_atm_lineaction(ATM0): state=0
May 11 20:09:55.494: ATM0: atmsar_vc_dlcx
May 11 20:09:55.758: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, chang
ed state to down
May 11 20:09:55.790: DSL(ATM0): 1: Modem state = 0x9
May 11 20:09:58.290: DSL(ATM0): 2: Modem state = 0x10
May 11 20:10:00.790: DSL(ATM0): 3: Modem state = 0x10
May 11 20:10:03.291: DSL(ATM0): 4: Modem state = 0x10
May 11 20:10:05.791: DSL(ATM0): 5: Modem state = 0x10
May 11 20:10:06.543: DSL(ATM0): Received response: 0x24
May 11 20:10:06.543: DSL(ATM0): Showtime!
May 11 20:10:06.543: DSL(ATM0): Sent command 0x31
May 11 20:10:06.551: DSL(ATM0): Received response: 0x12
May 11 20:10:06.551: DSL(ATM0): operation mode 0x0002
May 11 20:10:06.551: DSL(ATM0): Sent command 0x33
May 11 20:10:06.555: DSL(ATM0): Received response: 0x16
May 11 20:10:06.559: DSL(ATM0): Far End ITU Country Code 0xB5
May 11 20:10:06.559: DSL: Far End ITU Vendor ID BDCM
May 11 20:10:06.559: DSL: Far End ITU Vendor ID Specific 0x6193
May 11 20:10:06.559: DSL: Far End ITU Vendor STD Number 0x0002
May 11 20:10:06.559: DSL(ATM0): Sent command 0x32
May 11 20:10:06.563: DSL(ATM0): Received response: 0x14
May 11 20:10:06.563: DSL(ATM0): Near End ITU Country Code 0x0F
May 11 20:10:06.563: DSL: Near End ITU Vendor ID STMI
May 11 20:10:06.563: DSL: Near End ITU Vendor ID Specific 0x0000
May 11 20:10:06.563: DSL: Near End ITU Vendor STD Number 0x0003
May 11 20:10:06.563: ATM0 atmsar_update_us_bandwidth(): upstream bw =384 Kbps
May 11 20:10:06.563: DSL: SM: [DMTDSL_DO_OPEN -> DMTDSL_SHOWTIME]
May 11 20:10:15.496: ATM0: atmsar_vc_dlcx
May 11 20:10:15.496: (ATM0)1a_enable: delay activation of vcd=1, vc=0x842D3E9C
May 11 20:10:15.496: (ATM0)1a_enable: delay activation of vcd=2, vc=0x83E4C5CC
May 11 20:10:15.496: atmsar enable ATM0

May 11 20:10:15.496: ATM0: atmsar_bringup_interface: Interface and atm_db flags
are UP
May 11 20:10:16.948:  Reserved bw for 8/35 Available bw = 384
May 11 20:10:16.948: ATM0: atmsar_1a_setup_vc, vcinfo = 0x842D3E9C

May 11 20:10:16.948: ATM0 atmsar_vc_setup: vcd 1
May 11 20:10:16.948:  Fill up paramaters for PVC 8/35[1] - Request for CoS 0 PCR
0 SCR 0 MCR 0 Available 384
May 11 20:10:16.948:  Scheduler parameters for 8/35. Type UBR. PCR 384
May 11 20:10:16.948:  Total scheduled bandwidth after configuringPVC 8/35 will b
e 0
May 11 20:10:16.948: atmsar_setup_cos(ATM0): vc:1 wred_name:- max_q:0
May 11 20:10:16.948: ATM0: VC setup successful (vcd = 1)
May 11 20:10:16.948:  Reserved bw for 8/81 Available bw = 384
May 11 20:10:16.948: ATM0: atmsar_1a_setup_vc, vcinfo = 0x83E4C5CC
May 11 20:10:16.948: ATM0 atmsar_vc_setup: vcd 2
May 11 20:10:16.948:  Fill up paramaters for PVC 8/35[1] - Request for CoS 0 PCR
0 SCR 0 MCR 0 Available 384
May 11 20:10:16.948:  Fill up paramaters for PVC 8/81[2] - Request for CoS 0 PCR
0 SCR 0 MCR 0 Available 384
May 11 20:10:16.948:  Scheduler parameters for 8/81. Type UBR. PCR 384
May 11 20:10:16.948:  Total scheduled bandwidth after configuringPVC 8/81 will b
e 0
May 11 20:10:16.952: atmsar_setup_cos(ATM0): vc:2 wred_name:- max_q:0
May 11 20:10:16.952: ATM0: VC setup successful (vcd = 2)
May 11 20:10:17.497: %LINK-3-UPDOWN: Interface ATM0, changed state to up
May 11 20:10:17.497:  atmsar_atm_lineaction(ATM0): state=4
May 11 20:10:18.497: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, chang
ed state to up

I will gather more information.

Thank you

Ivanoff Capetillo

0 Helpful
Customers Also Viewed These Support Documents
Review Cisco Networking for a $25 gift card