This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Unable to run an ARP report against a Cisco Nexus with KIWI CatTools 3.6.0

mbrison over 13 years ago

When trying to run an ARP table report against the Nexus platform, the report fails. The Info Log shows "Unable to find the title line in router ARP table" and then follows with the line "No ARP data available."

Any ideas on how to work around this? The output from other Cisco equipment was in the format of the following:

#show arp

ARP Aging time = 1200 sec
+ - Permanent Arp Entries
* - Static Arp Entries
default                                   at 00-00-00-00-00-00 on vlan 0
DNSName1.domain.com               at 00-00-00-00-00-01 port 1/2,3/1 on vlan 214
DNSName1.domain.com            at 00-00-00-00-00-02 port 1/2,3/1 on vlan 214
192.168.1.1                           at 00-00-00-00-00-04 port 1/2,3/1 on vlan 214
192.168.1.2                           at 00-00-00-00-00-05 port 1/2,3/1 on vlan 214

On the NEXUS, it looks like this:

# show ip arp # yes, I tried changing the command in the activity

Flags: * - Adjacencies learnt on non-active FHRP router
       + - Adjacencies synced via CFSoE
       # - Adjacencies Throttled for Glean
       D - Static Adjacencies attached to down interface

IP ARP Table for context default
Total number of entries: 7
Address Age MAC Address Interface
192.168.1.12 00:03:13 0000.0000.0001 Vlan925
192.168.1.13 00:11:25 0000.0000.0002 Vlan925
192.168.1.14 00:05:25 0000.0000.0003 Vlan925
192.168.1.15 00:06:21 0000.0000.0004 Vlan925
192.168.1.16 00:02:01 0000.0000.0005 Vlan901
192.168.1.17 00:00:49 0000.0000.0006 Vlan901
192.168.1.18 00:00:47 0000.0000.0007 Vlan901

0 Spartacus over 13 years ago

Hi mbrison
It's possible that the line:
   # - Adjacencies Throttled for Glean
before the ARP table is displayed is causing CatTools to think that it has reached the 'anchor-point' (i.e. the device hostname prompt being #), so ignores the rest of the data and therefore can't find any ARP table header row.
Does your device have a hostname (e.g. 'nexus#' or 'abc123#'), or is the enable mode hostname prompt simply just the '#' character?   If the latter than this is most likely the problem. Configure a hostname for the device and you may get it working.
If this isn't the issue, I'd recommend raising a support ticket as we'd need to get some device logs from you to analyze.
Kind regards,
Steve
Cancel
Vote Up 0 Vote Down

Cancel
0 mbrison over 13 years ago in reply to Spartacus

Under the options tab > use alternate command, I typed the following command to use: show ip arp | exclude #
The results of this command show the same results as previously mentioned without the line containing #-Adjacencies...
The report still fails with the same errors.
Cancel
Vote Up 0 Vote Down

Cancel
0 mbrison over 13 years ago

I think I have resolved my problem. When I upgraded to the latest version of KIWI CatTools, I failed to update the device types to "Cisco.NXOS," which was not a device type option prior to the upgrade. Once I did this, I was able to get the ARP table report to run and appear to finish.
Cancel
Vote Up 0 Vote Down

Cancel