Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

What is causing all my punt adjacencies on 7500 frame-relay interfaces?

I have 4 7500 routers on my network running 12.2(12a) with dCEF enabled. It appears the CEF is functioning fine on Token Ring/Ethernet/Point-to-Point interfaces. However, it appears the majority of my frame-relay interfaces and sub-interfaces have punt adjacencies when I do my "show ip cef." What could be the cause? I probably have

about 100 frame subinterfaces on the following 7500 router. There are some frame interfaces that are working correctly. Here is an example:

kylex7500a#sh ad s5/0/5.3

Protocol Interface Address

IP Serial5/0/5.3 point2point(22)

s5/0/5.3 has a valid adjacency, but other interfaces on s5/0/5 do not. For

instance, s5/0/5.1 and s5/0/5.1 do not:

kylex7500a#sh ad s5/0/5.1

Protocol Interface Address

kylex7500a#sh ad s5/0/5.2

Protocol Interface Address

Here is the config for those interfaces:

interface Serial5/0/5

bandwidth 1544

no ip address

encapsulation frame-relay

no ip mroute-cache

logging event subif-link-status

logging event dlci-status-change

load-interval 30

fair-queue

serial restart-delay 0

!

interface Serial5/0/5.1 point-to-point

description frame-relay to mnstp002 dlci 255

ip address 172.16.19.1 255.255.255.252

no ip mroute-cache

frame-relay interface-dlci 255

!

interface Serial5/0/5.2 point-to-point

description frame-relay to vadan213 dlci 299

ip address 172.16.19.5 255.255.255.252

no ip mroute-cache

frame-relay interface-dlci 299

!

interface Serial5/0/5.3 point-to-point

description frame-relay to paroc202 dlci 230

ip address 172.16.19.9 255.255.255.252

no ip mroute-cache

frame-relay interface-dlci 230

Out s5/0/5.2 is subnet 162.128.161.192/26. Here is the output for the sh

ip cef command:

kylex7500a#sh ip cef 162.128.161.192 255.255.255.192

162.128.161.192/26, version 22177, per-destination sharing

0 packets, 0 bytes

via 172.16.19.6, Serial5/0/5.2, 0 dependencies

next hop 172.16.19.6, Serial5/0/5.2

valid punt adjacency

0 packets, 0 bytes switched through the prefix

tmstats: external 0 packets, 0 bytes

internal 0 packets, 0 bytes

30 second output rate 0 Kbits/sec

Out s5/0/5.3 is subnet 149.55.202.0/24. Here is the output for the show ip

cef command:

kylex7500a#sh ip cef 149.55.202.0 255.255.255.0

149.55.202.0/24, version 60823, per-destination sharing

0 packets, 0 bytes

via 172.16.19.10, Serial5/0/5.3, 0 dependencies

next hop 172.16.19.10, Serial5/0/5.3

valid adjacency

489327 packets, 98153222 bytes switched through the prefix

tmstats: external 0 packets, 0 bytes

internal 489327 packets, 98153222 bytes

30 second output rate 24 Kbits/sec

I see similar results from my other three 7500s and my two 7200s. However,

it appears from all of my 2600s that cef is working correctly. Any thoughts? Sorry for the long detail. Thanks.

1 REPLY
Silver

Re: What is causing all my punt adjacencies on 7500 frame-relay

On a Frame Relay interface, configuring a static map statement prompts CEF to add a host prefix entry to the CEF table. Originally, CEF did not consider whether the PVC was in an "ACTIVE" status before creating the entry.

When the prefix is defined, prefixes requiring exception processing are cached with one of the special adjacencies .

Punt adjacency processes Features that require special handling or features that are not yet supported in conjunction with CEF switching paths are forwarded to the next switching layer for handling. Features that are not supported are forwarded to the next higher switching level. If the adjacency is punt then it is redirected to an MSFC for further processing.

Refer to this troubleshooting document.

http://www.cisco.com/warp/public/105/cef_incomp.html

93
Views
0
Helpful
1
Replies
CreatePlease to create content