I have a 7206VXR running 12.1(4).  When I push an ACL with CiscoWorks (CW),
the write back to my CW server kills the LANE client and my users are
isolated from the WAN until the LANE reestablishes (2-5 minutes).  The ACL
push is actually successful.

I can tftp the ACL from my desktop with Cisco tftp server 1.1 without any
difficulty.

The 200BX code was upgraded and the problem still exists?  Any ideas why IP
traffic would kill the LANE?  I know that sounds funny...

Must the UNI version from the router to the ATM switch match?  If they don't
match but must, why would the problem only manifest itself on the writeback
to the CW server?

I have noted the proc cpu jumps big with the ACL push - 60% SNMP usage!

But I do this to several (100+) routers a day without failures or pegging
the load on the router.  Am considering downgrading the code to 12.1.1AT1...

Ideas?  Suggestions?  

Thanks!

Mar  2 15:25:24: %SYS-5-CONFIG: Configured from
tftp://XXX.XXX.XXX.XXX/pcmdiFSD58964
Mar  2 15:25:27: %SYS-5-CONFIG_I: Configured from
tftp://XXX.XXX.XXX.XXX/pcmdiFSD58964 by console
Mar  2 15:25:36: %SYS-4-SNMP_WRITENET: SNMP WriteNet request. Writing
current configuration to XXX.XXX.XXX.XXX
9
Mar  2 15:25:40: %LANE-6-INFO: ATM2/0: ILMI prefix add event received
 Mar  2 15:26:04: %LANE-5-UPDOWN: ATM2/0.200 elan XXXXXXXXXX: LE
 Client changed state to down
 Mar  2 15:26:04: %BGP-5-ADJCHANGE: neighbor XXX.XXX.XXX.XXX Down Interface
 flap
 Mar  2 15:26:08: %LANE-3-NOREGILMI: ATM2/0.200 LEC cannot register
 35.000103.00027ULD3T
 38.C8 with ILMI
 Mar  2 15:26:16: %LANE-3-NOREGILMI: ATM2/0.200 LEC cannot register
 35. 000103.00027ULD3T
 38.C8 with ILMI
 Mar  2 15:26:27: %LANE-3-NOREGILMI: ATM2/0.200 LEC cannot register
 47.0006103.00026Y8G88
 38.C8 with ILMI
 Mar  2 15:26:42: %ATMSSCOP-4-UNMATCHUNIVERSION: (ATM2/0): rcv N(SQ)=0 in
 BeginPdu at UNI 3.1. Please veri
 fy peer UNI version
 Mar  2 15:26:44: %LANE-3-NOREGILMI: ATM2/0.200 LEC cannot register
 35. 000103.00057DUELT
 38.C8 with ILMI
 Mar  2 15:27:04: %LANE-6-INFO: ATM2/0: ILMI prefix add event received
 Mar  2 15:27:17: %LANE-5-UPDOWN: ATM2/0.200 elan XXXXXXXXXXXX: LE
 Client changed state to up

ROUTER#sh int atm 2/0.200
ATM2/0.200 is up, line protocol is up
  Hardware is TI1570 ATM
  Description: link to elan xxxxxxxx
  Internet address is XXX.XXX.XXX.XXX
  MTU 1500 bytes, BW 12000 Kbit, DLY 80 usec,
     reliability 255/255, txload 3/255, rxload 7/255
  Encapsulation ATM-LANE
  59422 packets input, 34074665 bytes
  57427 packets output,11690823 bytes
  0 OAM cells input, 0 OAM cells output
  AAL5 Oversized SDUs : 0
  ARP type: ARPA, ARP Timeout 04:00:00

ROUTER#sh int atm 2/0
ATM2/0 is up, line protocol is up
  Hardware is TI1570 ATM
  MTU 4470 bytes, sub MTU 4470, BW 155520 Kbit, DLY 80 usec,
     reliability 255/255, txload 3/255, rxload 7/255
  Encapsulation ATM, loopback not set
  Keepalive not supported
  Encapsulation(s): AAL5, PVC mode
  2048 maximum active VCs, 1024 VCs per VP, 7 current VCCs
  VC idle disconnect time: 300 seconds
  Signalling vc = 1, vpi = 0, vci = 5
  UNI Version = 3.1, Link Side = user
  Last input 00:00:00, output 00:00:00, output hang never
  Last clearing of "show interface" counters 00:01:29
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 4669000 bits/sec, 982 packets/sec
  5 minute output rate 2210000 bits/sec, 956 packets/sec
     85627 packets input, 48443618 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     82029 packets output, 16215942 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
ROUTER#

Roger Gore
CCNA
CONUS TNOSC
Ft Huachuca, AZ
[EMAIL PROTECTED]
DSN 879-1237
COM 520 538-1237




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=499&t=499
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to