Syntax Description

• port <port number>

  (Optional) The network access server port to use for POD requests. If no port is specified, port 1700 is used.

• auth-type

  (Optional) The type of authorization required for disconnecting sessions.

  • any

    Session that matches all of the attributes sent in the POD packet is disconnected. The POD packet may contain one or more of four key attributes (user-name, framed-IP-address, session-ID, and session-key).

  • all

    Only a session that matches all four key attributes is disconnected. All is the default.

  • session-key

    Session with a matching session-key attribute is disconnected. All other attributes are ignored.

• <string>

  The secret text string that is shared between the network access server and the client workstation. This secret string must be the same on both systems.

This command is now documented as of 12.2(8)T.

Modem CD dropped unexpectedly.  
User exceeded timelimit 
ARAP connection was terminated.  
v42_input running (may be low memory) 
v42_output running (may be low memory) 
Force Quit pak v42bisflush C
Carrier dropped during startup

With the command csim you can emulate a voice call. It's like sombody calls the specified number. Usefull, if you don't have physically access to the telephone:

Sucessfull call:

wg1r1#csim start 089150
csim: called number = 089150, loop count = 1 ping count = 0
csim err csimDisconnected recvd DISC cid(21) 
csim: loop = 1, failed = 1 
csim: call attempted = 1, setup failed = 1, tone failed = 0

Call to an undefined number:

wg1r1#csim start 089151
csim: called number = 089151, loop count = 1 ping count = 0 

csim err:csim_do_test Error peer not found 

Crypto ISAKMP internals debugging.

Example output during ISAKMP SA establishment:

6w3d: ISAKMP cookie gen for src 62.245.147.66 dst 195.244.119.2
6w3d: ISAKMP cookie B5FCAD89 B2BD7BFF
6w3d: ISAKMP: find_me 
	a=(src 62.245.147.66 dst 195.244.119.2 state 0, init 1) 
	b=(src 0.0.0.0 dst 0.0.0.0 state 0, init 0) 
6w3d: my_cookie a B5FCAD89 9BEC22F8
6w3d: my_cookie b B5FCAD89 B2BD7BFF
6w3d: his_cookie a DB28B716 6D61AE4F
6w3d: his_cookie b 00000000 00000000
6w3d: ISAKMP: compare 
	a=(src 62.245.147.66 dst 195.244.119.2 state 0, init 1) 
	b=(src 62.245.147.66 dst 195.244.119.2 state 0, init 1) 
6w3d: my_cookie a B5FCAD89 9BEC22F8
6w3d: my_cookie b B5FCAD89 9BEC22F8
6w3d: his_cookie a DB28B716 6D61AE4F
6w3d: his_cookie b DB28B716 6D61AE4F
6w3d: ISAKMP cookie gen for src 195.244.119.2 dst 62.245.147.66
6w3d: ISAKMP cookie 10FA17FE 2C76366D
6w3d: ISAKMP: find_me 
	a=(src 62.245.147.66 dst 195.244.119.2 state 0, init 1) 
	b=(src 0.0.0.0 dst 0.0.0.0 state 0, init 0) 
6w3d: my_cookie a B5FCAD89 9BEC22F8
6w3d: my_cookie b 10FA17FE 2C76366D
6w3d: his_cookie a DB28B716 6D61AE4F
6w3d: his_cookie b 00000000 00000000
6w3d: ISAKMP: compare 
	a=(src 62.245.147.66 dst 195.244.119.2 state 0, init 1) 
	b=(src 62.245.147.66 dst 195.244.119.2 state 0, init 1) 
6w3d: my_cookie a B5FCAD89 9BEC22F8
6w3d: my_cookie b B5FCAD89 9BEC22F8
6w3d: his_cookie a DB28B716 6D61AE4F
6w3d: his_cookie b DB28B716 6D61AE4F

Crypto ISAKMP packet debugging.

Example output during ISAKMP SA establishment:

6w3d: -Traceback= 80A36FE0 80A3A5C0 80A3D41C 809F0880 809F8A34 
		  809F301C 809F33DC 809F5228 801710CC
6w3d: -Traceback= 80A36FE0 80A3A5C0 80A3D41C 809F8494 809F87C0 
		  809F8C20 809F301C 809F33DC 809F5228 801710CC
6w3d: ISAKMP: Main Mode packet contents (flags 0, len 72):
6w3d:           SA payload
6w3d:             PROPOSAL
6w3d:               TRANSFORM
6w3d: ISAKMP (0:1): sending packet to 195.244.119.2 (I) MM_NO_STATE
6w3d: ISAKMP (0:1): received packet from 195.244.119.2 (I) MM_NO_STATE
6w3d: ISAKMP: Main Mode packet contents (flags 0, len 72):
6w3d:           SA payload
6w3d:             PROPOSAL
6w3d:               TRANSFORM
6w3d: -Traceback= 80A36FE0 80A3A5C0 80A3D41C 809FF460 80A00E0C
		  80A01070 809FBEBC 809F99B8 809F468C 809F51C8 801710CC
6w3d: ISAKMP: Main Mode packet contents (flags 0, len 204):
6w3d:           KE payload
6w3d:           NONCE payload
6w3d:           VENDOR payload
6w3d: ISAKMP (0:1): sending packet to 195.244.119.2 (I) MM_SA_SETUP
6w3d: ISAKMP (0:1): received packet from 195.244.119.2 (I) MM_SA_SETUP
6w3d: ISAKMP: Main Mode packet contents (flags 0, len 184):
6w3d:           KE payload
6w3d:           NONCE payload
6w3d: ISAKMP: Main Mode packet contents (flags 1, len 64):
6w3d:           ID payload
6w3d:           HASH payload
6w3d: ISAKMP (0:1): sending packet to 195.244.119.2 (I) MM_KEY_EXCH
6w3d: ISAKMP (0:1): received packet from 195.244.119.2 (I) MM_KEY_EXCH
6w3d: ISAKMP: Main Mode packet contents (flags 1, len 68):
6w3d:           ID payload
6w3d:           HASH payload
6w3d: ISAKMP: Quick Mode packet contents (flags 1, len 168):
6w3d:           HASH payload
6w3d:           SA payload
6w3d:             PROPOSAL
6w3d:               TRANSFORM
6w3d:           NONCE payload
6w3d:           ID payload
6w3d:           ID payload
6w3d: ISAKMP (0:1): sending packet to 195.244.119.2 (I) QM_IDLE      
6w3d: ISAKMP (0:1): received packet from 195.244.119.2 (I) QM_IDLE    
6w3d: ISAKMP: Quick Mode packet contents (flags 1, len 172):
6w3d:           HASH payload
6w3d:           SA payload
6w3d:             PROPOSAL
6w3d:               TRANSFORM
6w3d:           NONCE payload
6w3d:           ID payload
6w3d:           ID payload
6w3d: ISAKMP: Quick Mode packet contents (flags 1, len 52):
6w3d:           HASH payload
6w3d: ISAKMP (0:1): sending packet to 195.244.119.2 (I) QM_IDLE

Activate debugging output for dialer hold queue events.

Jan 13 14:56:03.240: Se0/1:15 DDR: Creating holdq 626B1B9C
Jan 13 14:56:03.240: DDR: Assigning holdq 626B1B9C to 627923F8
Jan 13 14:56:09.208: DDR: Assigning holdq 626B1B9C to 61B667F4
Jan 13 14:56:09.208: DDR: freeing dialer holdq 626B1B9C (Ref ptr 61B667F4)
Jan 13 14:56:09.208: DDR: Dialing failed, 0 packets unqueued and discarded
Jan 13 14:56:09.208: : 2 packets unqueued and discarded

Activate OIR debugging.

ctalkb#debug oir
Online Insertion and Removal debugging is on
2w3d: OIR: Process woke, 'Event', stall=2, usec=0xB6835B36 
	-Traceback= 6040967C 603B6D2C 603B6D18
2w3d: OIR: Shutdown pulled interface for Serial5/0 
	-Traceback= 600E30C4 60409204 604096C8 603B6D2C 603B6D18
2w3d: %OIR-6-REMCARD: Card removed from slot 5, interfaces disabled 
	-Traceback= 60409748 603B6D2C 603B6D18
2w3d: OIR: Remove hwidbs for slot 5 
	-Traceback= 60409368 60409750 603B6D2C 603B6D18
2w3d: OIR: Process woke, 'Event(max not running)', stall=3, usec=0xD0115C9E
	-Traceback= 6040967C 603B6D2C 603B6D18
2w3d: OIR: Process woke, 'Timer(max running)', stall=3, usec=0xDDBB56D6
	-Traceback= 6040967C 603B6D2C 603B6D18
2w3d: OIR: (Re)Init card 5, retry_count=3 
	-Traceback= 60409894 603B6D2C 603B6D18
2w3d: %OIR-6-INSCARD: Card inserted in slot 5, interfaces administratively shut down 
	-Traceback= 604098BC 603B6D2C 603B6D18

Aug  7 21:58:44.207 MEST: Look up of parser mode 'route-map' succeeded
Aug  7 21:58:45.923 MEST: Look up of parser mode 'configure' succeeded

Catalyst 5000 series with Supervisor Engine I:

You will be prompted for a password. It has the following format:

• VTY
• VTY
• HW
• FW
• SW

Catalyst 5000 series with Supervisor-Engine II and III and Catalyst 6000 series with Supervisor I and II:

Format for the password is:

• VTY
• HW
• FW
• SW
• VTY

That is, the VTY password followed by the VTY password again, followed by the hardware version, followed by the software version (no spaces, do not type the dots in the versions).

This hidden command enables setting the FECN bit in all outgoing packets that have been delayed due to traffic shaping.

It's hidden, and you have to configure "service internal" in order to bring it into existence.

• <secs-between-runs> is 0-2147483 number of seconds between ager runs, default = 60 seconds. If the period between ager invalidation runs is set to 0, the ager process is disabled entirely.
• <fraction-low-memory> is 2-50 1/<fraction-low-memory> of cache to age per run (low memory), default = 4.
• <fraction> is 3-100 1/<fraction> of cache to age per run (normal), default = 20.

Configures the ager of the fast switching cache. Aaron Leonard <Aaron@cisco.com> recommended "20 3 3" on cisco-nas in the light of recent CodeRed attacks, i.e. make the ager more aggressive to prevent excessive cache growth.

Requires "service internal".

• <minimum-delay> is 0-300 seconds.
• <maximum-delay> is 1-300 seconds.
• <quiet-interval> is 1-600 seconds.

Use "no ip cache-invalidate-delay" to disable the delay altogether. See this posting from cisco-nas:

Date: Fri, 28 Apr 2000 10:07:03 -0700 (PDT)
From: Aaron Leonard <Aaron@cisco.com>
Subject: Re: CN: telnet DoS (CSCdm70743)
To: Cisco-NAS@datasys.net
Message-id: <01JORKP9PBPIA2AL39@Cisco.COM>
References: <01JOHR9QY432A2AAVQ@Cisco.COM>
Reply-To: Cisco-NAS@datasys.net

It's hidden, and you have to configure "service internal" in order
to bring it into existence.  I.e.

as5300-1(config)#service internal
as5300-1(config)#no ip cache-invalidate-delay

It's generally recommended for systems running 12.0T/12.1 code if
they have lots of interfaces (>300) and are not doing CEF.

From Cisco DE (slightly edited):

The motivation for this command is a timing problem where OSPF fails to determine the state of an interface. The solution was for OSPF to poll the interface for a while to verify its state. The hidden command allows us to lengthen the polling period on routers that have a large number of interfaces. The polls occur every 10 seconds and the command controls the number of polls that will be done. With a setting of 0 retries there will be no extra polling.

Default number of retries is 10.

As disclosed by Aaron Leonard from Cisco on cisco-nas:

Date: Thu, 11 Sep 2003 09:34:53 -0700 (PDT)
From: Aaron Leonard <Aaron@cisco.com>
Subject: Re: [cisco-nas] IP Route Profile
In-reply-to: "Your message dated Wed, 10 Sep 2003 22:21:02 -0500"
        <10e701c37813$bad83870$5370cd41@dellbert>
To: "Beprojects.com" <info@beprojects.com>
Cc: cisco-nas@puck.nether.net

[...]

"ip route profile" was implemented way back in late '96 by CSCdi76662. 
However we have historically refrained from documenting this (CSCdk01634,
CSCdz19775) as this has been declared to be a hidden command that "should
not be used by customers".
                                                                                                             
However, in fact this is NOT a hidden command ... so I've just now
gone ahead and reopened CSCdz19775.

Introduction

The Route Table Profiling feature was developed to assist network engineers
in monitoring routing table fluctuations, which may be the result of route
flapping, network failure, or network service restoration.  This feature was
added in CSCdi76662 to the 11.1CC train of Cisco IOS.

The Route Table Profiling feature is an undocumented and unsupported
feature.  There is no MIB support provided.

Configuration
                                                                                                          
The Route Table Profiling feature is enabled globally.  The command is "ip
route profile" in global configuration mode.  This feature can be disabled
with the command "no ip route profile" in global configuration mode.
                                                                                                          
Routing table change statistics can be viewed with the "show ip
route profile" command in exec mode.

This command is documented in DDTS CSCdm12190. From the release note:

By default, split horizon blocks information about periodic SAPs from being advertised by a router to the same interface on which the best route to that SAP is learned. But in the case where the SAP may be learned from interfaces other than (or in addition to) the interface on which the best route to that SAP is learned, enabling "ipx server-split-horizon-on-server-paths" will reduce unnecessary periodic SAP updates as that SAP will not be advertised to the interface(s) where it was learned from; this will also prevent potential "SAP loop" in the network.

The undocumented passive keyword specifies to listen but not send normal periodic SAP or RIP updates nor flash update caused by changes. Queries will still be replied to. The update interval is set to the same interval as changes-only.

See also "ipx sap-interval".

Turn off the %SNMP-3-AUTHFAIL message.

See CSCdv04268 for availability information.

From: Dennis Peng <dpeng@cisco.com>
To: "scott.list" <scott.list@mlec.net>
Cc: cisco-nas@external.cisco.com
Message-ID: <20010331195613.D28415@sj-cse-320.cisco.com>

I assume you have preauthentication already configured? By default, we
send Service-Type = Outbound-User. In 12.1(4)T and later, you can
configure the (hidden) command "radius send service-type call-check"
to change the value from Outbound-User to Call-Check. I submitted
CSCdt85947 to get the command unhidden and documented. Here is the
release-note I attached:

The command "radius send service-type call-check" is hidden. This
command is available in 12.1(4)T and later and is used to change the
value of the Service-Type RADIUS attribute the access server sends
when doing pre-authentication. The default is to send Outbound-User
(5). With this command configured, we will send Call-Check (10). This
is useful in a multi-vendor environment as well as when migrating an
existing RADIUS database for use withe Cisco access server.

Directly from the DDTS release note:

The hidden command "radius-server unique-ident" can be used to try to ensure that RADIUS session IDs are unique across IOS boots. It will have the side effect of automatically writing the IOS configuration to NVRAM some time after booting.

When the router parses the command "radius-server unique-ident" it sets the unique-ident variable to (n+1) and all accouting records have a prefix of (n+1). When you look at the configuration or write the configuration to NVRAM, it is also shows "radius-server unique-ident".

If the box is reloaded, upon booting the router will parse "radius-server unique-ident" and then set the unique-ident variable to (n+2) and all accounting records have a prefix of (n+2). When you look at the configuration or write the configuration to NVRAM, is will show "radius-server unique-ident".

Enables the use of third-party SFP or GBIC modules on Cisco switches but note the warning below.

Example output:

Switch(config)#service unsupported-transceiver
 Warning: When Cisco determines that a fault or defect can be traced to
 the use of third-party transceivers installed by a customer or reseller,
 then, at Cisco's discretion, Cisco may withhold support under warranty or
 a Cisco support program. In the course of providing support for a Cisco
 networking product Cisco may require that the end user install Cisco
 transceivers if Cisco determines that removing third-party parts will
 assist Cisco in diagnosing the cause of a support issue.

From CSCds43683:

Packets should be treated consistently on all platforms for a given configuration. This fix addresses the consistency issue when QoS Mod CLI is configured via the "service-policy" command on the 7500 vs the other IOS platforms.

After this fix, each packet will be matched for a matching class under the policy-map until a match is found. Matching terminates at the first matching class and all features configured under the class act on the packet. In the current IOS releases, matching happens across all classes under a policy until the first matching class is found for every configured QoS feature.

To maintain backward compatibility a hidden knob called "service-policy classify-per-feature" knob is introduced. When configured, the behaviour reverts to the current existing behaviour. By way of this fix, the default behaviour will be common for all platforms. This fix is going to affect 7200 and other non-distributed platforms only.

Enable tracing of the specified subsystem.

Possible category names (most certainly depending on CatOS version):
acct, acl, all, bdd, cdp, config, dhcp, diag, dns, dot1x, drip, dtp, dupflash, dupnvram, dynvlan, earl, envmon, eobc, epld, essr, evmgr, fabric, fcp, fddi, fib, filesys, fpoe, garp, gvrp, hamgr, http, inband, ipc, kerberos, l3age, l3sup, lane, ld, llc, ltl, mbuf, mcast, mdg, memdbg, mls, mlsm, modport, ntp, nvsync, oob, pagp, protfilt, pruning, privatevlan, qde, qos, radius, redundancy, rsfc, rsvp, rtios, rtipc, rticc, runtimecfg, scp, security, slp, snmp, span, spantree, ssh, syncmgr, synfig, syslog, tacacs, test, tftp, tftpd, udld, verb, vlanmgr, vmps, vtp.

• <level> = 0..15, 0 to disable, default is 1
• <level> = 0..255 for inband only

Warning: Can produce losts of output depending on your configuration and the level chosen.

Comment by Francois on this command:

Displays various statistics about the ACL subsystem and associated hardware components. There are some interesting counters like compilation errors and also usage counters for various tables (different masks, subnets, etc). Useful when you can't commit your ACL with a TCAM error message.

ACL: local stats table
Messaging
----------------------------------------------------------
rxScpMsg:              0
rxScpMsgAbort:         0
rxAclMsg:              1257
rxAclMsgAbort:         0
aclMsgUnknownType:     0
outOfSequence:         0
appIdMisUse:           0
intfConfError:         0
msgSendFailed:         1
appIdDifferAfterSwover:0
ignoreRaclOverride:    1
draco-id:  65535-ffffffff-ffffffff
draco-id:  33-ffffffff-ffffffff


Resources
----------------------------------------------------------
ACL malloc fail:       0
noLou:                 0
noMask:                0
noCapmap:              0
tcamFull:              0
compilerErr:           18
noLabel:               0
louExpandGt:           0
louExpandLt:           0
louExpandNeq:          0
louExpandRange:        0
freeListRebuild:       0


Acl engine stats
----------------------------------------------------------
perseusL3Parity:       0
perseusSequenceErr:    0
perseusLabelOverflow:  0
perseusCamLookupErr:   0
perseusDbusErr:        0
perseusCpuParityErr:   0
perseusIPChecksumErr:  1
perseusShortPacketErr: 0
perseusCpuTmout:       0
**lookup fifo undeflow:0
Hardware resource usage for ACL Tcam: label:3.73%, lou:20.31%,
mask:11.86%, value:4.4%


Acl manager stats
----------------------------------------------------------
aclRestarted:          F
Sec vacl restore done: T
Lda vacl restore done: T
Qos acl restore done:  T
Feature intf count:    0


HA stats
----------------------------------------------------------
activeHaCopyFail:      0
Gsync_count:           1
Sleep on gsync      Gsync done          Wakeup on gsync
14:58:43            14:58:45            14:58:45
00:00:00            00:00:00            00:00:00
00:00:00            00:00:00            00:00:00
00:00:00            00:00:00            00:00:00
000:00:00            00:00:00            00:00:00
00:00:00            00:00:00            00:00:00
00:00:00            00:00:00            00:00:00
00:00:00            00:00:00            00:00:00
00:00:00            00:00:00            00:00:00
00:00:00            00:00:00            00:00:00

There is a quiet recall on some Catalyst 5000 series switches that have the EARL 1 chip NFFC and a data rate that exceeds 80MBS across the backplane because of a defect that causes the ECB to reset continuously. Usually users will report a network slowdown.

This command will display the number of times the ECBs have reset since last power on, a number of 1 for each ECB is normal. Numbers in the hundreds or thousands mean you need to call Cisco for replacement boards.

The show controller switch command provides indicative information regarding the total switch utilization. An example is presented below:

    Switch#sh controller switch
    Switch registers:

    Device Type : 0x00040273
    Congestion Threshold : 0x00000E95
    Peak Total Allocation : 0x0000001A
    Total Allocation : 0x00000000
    Peak Total Bandwidth : 0x00000020
    Total Bandwidth : 0x00000000
    Total Bandwidth Limit : 0x000003DE
    Lower Bandwidth Limit : 0x000003DE
    Switch Mode : 0x00040000

    Switch#

The Total Bandwidth Limit varies between different 2900XL and 3500XL models. When the Total Bandwidth reaches the Total Bandwidth Limit value, the switch has reached its full bandwidth capacity and begins to drop packets. The Peak Total Bandwidth is the highest value attained by the Total Bandwidth since the last time the show controller switch command was executed. Note, the values for the above parameters are in hexadecimal.

The Congestion Threshold value is used as conservative value for the maximum global buffer utilization. When the buffer utilization noted by Total Allocation reaches this value, the switch may drop frames. The Peak Total Allocation value shows the highest value attained by the Total Allocation since the last time the show controller switch command was executed. It is possible for the Peak Total Allocation and/or the Total Allocation to be greater than Congestion Threshold. If the Total Allocation reaches or is over the Congestion Threshold amount, the switch is experiencing considerable network activity near its full capacity.

The global buffer utilization may be adversely effected by several configuration issues, described below:

1.Speed mismatch between an ingress and egress port; for example, several 100 megabit clients transferring files to a server connected to the switch at 10 megabits, half-duplex.

2.Multiple input ports feeding a single output port.

3.Duplex mismatch on multiple ports.

4.Numerous ports that are experiencing collisions and/or output errors due to half-duplex configuration or over-subscription of a slow link.

From a Catalyst 2048G-L3 (also applies to the Catalyst 4908G-L3 and probably in parts to the Catalyst 8500 series):

gepard#show epc ?
E-PAM show comands:
  IF-entry          IF Entry in IF-Table
  VC-entry          VC Entry in VC-Table
  VLAN-entry        VLAN Entry in VLAN-Table
  aal5              aal5 statistics
  acl               ACL FPGA related debug commands
  adm               Show contents of ADM in IOS
  age-timer         Aging Timer
  atm-debug-status  ATM debug statistics
  atmup_ipmcast     Show Multicast VC leg to external VC mapping
  caller-stats      Caller Stats at a merge-point
  caller-tags       Caller Tags
  cam               Show contents of E-PAM CAM
  card              Show information managed by CARD 
  coredb            show coredb
  counters          Counters of all epif-ports
  discards          discard statistics
  exvc-entry        External VC Entry in VC-Table
  fe-channel        FE-Channel Membership Information 
  fpga              Access ACL FPGA resources
  freecam           Free space in CAM
  ifmapping         Interface mapping to CAM IF number
  ip-address        Show adjacency entries in line cards
  ip-prefix         Show IP prefix entries (compare to CEF output)
  ipmcast           Show IP Multicast table in E-PAM CAM
  ipx-node          Show IPX node entry in E-PAM CAM
  ipx-prefix        Show IPX prefix in E-PAM CAM
  jaguar-fpga-epld  Access ACL2 EPLD Addresses with WID=2
  lec-ipx           Show LEC Local IPX Information
  lsipc             Show LSIPC information
  mac               Show MAC address in E-PAM
  macfilter         Show MAC filter address database
  mailbox           Read the mailbox value
  mem               Show contents of packet memory in E-PAM
  patricia          Show Patricia tree in E-PAM CAM
  port-qos          Show current port qos configuration
  queuing           queueing statistics
  register          print contents of EPIF register 
  ri-register       Show last reported contents of EPIF RI register
  sm                Show 1483 Local static map information
  spd               selective packet drop statistics
  status            Status of all epif-ports
  switching         VC switching statistics
  tcam              TCAM related commands
  ucode             uCode images on all epif-ports
  udp-flood         Show LS UDP-flooding information

Some of these commands are documented as part of the Catalyst 8540 documentation but are also useful on the Catalyst 2948G-L3 which seems to be based (at least partly) on the same hardware platform as the Catalyst 8540.

See: http://www.cisco.com/univercd/cc/td/doc/product/atm/c8540/12_1/11_ey/trouble/l3_net.htm

Shows the IP adjacencies installed in the CAM hardware:

gepard#show epc ip-address interface FastEthernet 1 all-entries 
IPaddr: 192.168.60.116  MACaddr: 0090.27b7.24d7  FastEthernet14(17)
IPaddr: 192.168.60.117  MACaddr: 0090.27d1.d47a  FastEthernet15(18)
IPaddr: 192.168.60.112  MACaddr: 00d0.b720.6fc9  FastEthernet10(13)
IPaddr: 192.168.60.113  MACaddr: 00d0.b720.750f  FastEthernet11(14)
IPaddr: 192.168.60.114  MACaddr: 00d0.b720.7357  FastEthernet12(15)
IPaddr: 192.168.60.115  MACaddr: 00d0.b720.755e  FastEthernet13(16)
IPaddr: 192.168.60.125  MACaddr: 0050.0457.edbf  FastEthernet19(22)
IPaddr: 10.232.4.202    MACaddr: 0009.b7b4.0700  Port-channel1.2(60)
IPaddr: 192.168.60.120  MACaddr: 0090.27c3.f042  FastEthernet5(8)
IPaddr: 192.168.60.100  MACaddr: 0002.b3ac.5470  GigabitEthernet50(53)
IPaddr: 192.168.60.101  MACaddr: 0002.b3ac.5470  GigabitEthernet50(53)
IPaddr: 192.168.60.102  MACaddr: 0090.27d1.88bf  FastEthernet4(7)
IPaddr: 192.168.60.103  MACaddr: 0090.27d1.88bf  FastEthernet4(7)
IPaddr: 192.168.60.99   MACaddr: 6080.0f3c.0000 
IPaddr: 192.168.60.110  MACaddr: 0090.27dd.f9a6  FastEthernet8(11)
IPaddr: 192.168.60.111  MACaddr: 00d0.b708.adb3  FastEthernet9(12)
IPaddr: 192.168.61.21   MACaddr: 0800.20ee.4ead  FastEthernet46(49)
IPaddr: 192.168.60.20   MACaddr: 0030.6e11.0157  FastEthernet37(40)
IPaddr: 192.168.60.21   MACaddr: 0030.6e11.139f  FastEthernet38(41)
IPaddr: 192.168.60.22   MACaddr: 0002.b3ac.5454  GigabitEthernet49(52)
IPaddr: 192.168.61.22   MACaddr: 0800.20ec.6709  FastEthernet46(49)
IPaddr: 192.168.60.23   MACaddr: 0002.b3ac.53f5  FastEthernet43(46)
IPaddr: 192.168.60.30   MACaddr: 00e0.18c2.baf9  FastEthernet21(24)
IPaddr: 192.168.60.25   MACaddr: 0030.6e12.099a  FastEthernet39(42)
IPaddr 192.168.60.26 missing
[...]
   Total number of IP adjacency entries: 46
   Missing IP adjacency entries: 1

Seems to show the FIB stored in the CAM memory of a specific ingress port.

Example output provided by Hank:

cs-c2948gl3-13a#sh epc patricia interface FastEthernet 3 ipucast detail
1# Synthetic entry: CAM location: 0x202B NAP location: 0x202C
    IP Prefix:224.0.0.0 MySubnet  LB:Disabled  Network Entry:Valid
2# Synthetic entry: CAM location: 0x2038 NAP location: 0x0000
3# Synthetic entry: CAM location: 0x202F NAP location: 0x2035
    IP Prefix:192.168.128.255 MySubnet  LB:Disabled  Network Entry:Valid
4# HOST Entry CAM location: 0x2030 NAP location: 0x0000
    IP addr:192.168.128.2   Host  IF Number:6 Entry:Valid
    Mac Addr:0090.a65c.63ff
5# Synthetic entry: CAM location: 0x2050 NAP location: 0x2032
    IP Prefix:192.168.128.0 MySubnet  LB:Disabled  Network Entry:Valid
    IP Prefix:192.168.128.1 MySubnet  LB:Disabled  Host Entry:Valid
6# Synthetic entry: CAM location: 0x203C NAP location: 0x2037
    IP Prefix:192.168.105.0 MySubnet  LB:Disabled  Network Entry:Valid
    IP Prefix:192.168.128.0 MySubnet  LB:Disabled  Network Entry:Valid
7# Synthetic entry: CAM location: 0x203F NAP location: 0x203E
    IP Prefix:192.168.105.255 MySubnet  LB:Disabled  Network Entry:Valid
8# HOST Entry CAM location: 0x2046 NAP location: 0x0000
    IP addr:192.168.105.8   Host  IF Number:5 Entry:Valid
    Mac Addr:0001.968e.33b0
9# Synthetic entry: CAM location: 0x2045 NAP location: 0x2040
    IP Prefix:192.168.105.2   LB:Disabled  Network Entry:Valid
    Nexthop CAM locations: 0x2046   0x0000
    Nexthop 1:
      IP addr:192.168.105.8   Host  Entry:Valid FastEthernet2 (5)
      Mac Addr:0001.968e.33b0
10# Synthetic entry: CAM location: 0x2033 NAP location: 0x203D
    IP Prefix:192.168.105.0 MySubnet  LB:Disabled  Network Entry:Valid
    IP Prefix:192.168.105.1 MySubnet  LB:Disabled  Host Entry:Valid
11# CAM location: 0x201B  ROOT
  IP Patricia Tree Summary:
    Number of IP entries: 18
    Number of Host Entries: 2
    Number of Network Entries: 10
    Number of Good Synthetic entries: 7
    Number of Dirty Synthetic entries: 1