RE: EEK nags [%FR_EEK-5-FAILED]

That'll do. I just wasn't thinking clearly. Thanks for a simple solution.

Charles

                                                                                                                                 
  From: Ryan West <rwest_at_zyedge.com>
                                                                                                                                 
  To: "Charles.Henson_at_regions.com" <Charles.Henson_at_regions.com>, "ccielab_at_groupstudy.com" <ccielab_at_groupstudy.com>
                                                                                                                                 
  Date: 06/05/2009 10:46 AM
                                                                                                                                 
  Subject: RE: EEK nags [%FR_EEK-5-FAILED]
                                                                                                                                 

Charles,

Try applying it to your specific DLCI's only.

interface Serial0/1/0
frame-relay interface-dlci 506
class EEK

-ryan

-----Original Message-----
From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
Charles.Henson_at_regions.com
Sent: Friday, June 05, 2009 11:35 AM
To: ccielab_at_groupstudy.com
Subject: EEK nags [%FR_EEK-5-FAILED]

All,
      I've had a couple of labs recently where I've had to configure frame
relay end-to-end keepalive. No big deal. However, in both situations, I had
EEK failure notifications for all the DLCIs that weren't in use.

Caveats:
      Nothing dynamic
      frame maps for my used DLCIs
      no frame inverse
      no arp frame (just because)

So I end up with something like this:

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

interface Serial0/1/0
 bandwidth 72
 ip address 140.106.100.5 255.255.255.240
 encapsulation frame-relay
 ip ospf authentication message-digest
 ip ospf authentication-key cisco
 ip ospf network broadcast
 ip ospf priority 5
 no arp frame-relay
 frame-relay class EEK
 frame-relay map ip 140.106.100.13 504 broadcast
 frame-relay map ip 140.106.100.1 506 broadcast
 frame-relay map ip 140.106.100.5 506
 no frame-relay inverse-arp
 frame-relay lmi-type cisco
 frame-relay lmi-n391dte 100
--------------------------------------------------------------------------------------------

Yet I still see the failure notifications for all my unused DLCIs in the
frame mesh.

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

*Jun 4 20:46:48.086: %FR_EEK-5-FAILED: Interface Serial0/1/0 - DLCI 516
R5(config-if)#
*Jun 4 21:03:28.190: %FR_EEK-5-FAILED: Interface Serial0/1/0 - DLCI 526
R5(config-if)#do wr me
--------------------------------------------------------------------------------------------

It's no big deal just annoying. But I can't seem to find a way to filter it
out of my console output. Has anyone seen this nag before and managed to
filter it? How?

Charles

Blogs and organic groups at http://www.ccie.net
Received on Fri Jun 05 2009 - 10:51:00 ART