Strange behaviour in a 7304 router when a route overlaps another one.

Unanswered Question
Dec 4th, 2006
User Badges:

HI all,


We are having an strange issue in a 7304 core router, the thing is that after adding a new route which overlaps another one already configured (an human error here) the route processor crash and an the box behavies in a very strange way, here is the "sh log" output (the more significant lines):


Dec 4 11:15:17: %COMMON_FIB-4-FIBNULLIDB: Missing idb for fibidb (no name) (if_number 363).

-Traceback= 406DC2E0 40471F1C 40515C98 40471240 405491F8 4054987C 4054A430 405378B0 4054DD1C 4054037C 405407D8


and here is the sh ver:


Cisco IOS Software, 7300 Software (C7300-K91P-M), Version 12.2(27)SBC5, RELEASE SOFTWARE (fc1)

Technical Support: http://www.cisco.com/techsupport

Copyright (c) 1986-2006 by Cisco Systems, Inc.

Compiled Tue 20-Jun-06 11:24 by pwade


ROM: System Bootstrap, Version 12.1(12r)EX1, RELEASE SOFTWARE (fc1)


GIJON-PE01 uptime is 4 weeks, 3 days, 16 hours, 59 minutes

Uptime for this control processor is 3 hours, 45 minutes

System returned to ROM by Stateful Switchover at 11:12:19 MET Mon Dec 4 2006

System restarted at 11:13:31 MET Mon Dec 4 2006

System image file is "disk0:c7300-k91p-mz.122-27.SBC5.bin"



This product contains cryptographic features and is subject to United

States and local country laws governing import, export, transfer and

use. Delivery of Cisco cryptographic products does not imply

third-party authority to import, export, distribute or use encryption.

Importers, exporters, distributors and users are responsible for

compliance with U.S. and local country laws. By using this product you

agree to comply with applicable laws and regulations. If you are unable

to comply with U.S. and local laws, return this product immediately.


A summary of U.S. laws governing Cisco cryptographic products may be found at:

http://www.cisco.com/wwl/export/crypto/tool/stqrg.html


If you require further assistance please contact us by sending email to

[email protected].


cisco 7300 (NSE100) processor (revision D) with 491520K/32768K bytes of memory.

Processor board ID SMQ0938N271

R7000 CPU at 350Mhz, Implementation 39, Rev 3.3, 256KB L2, 1024KB L3 Cache

4 slot midplane, Version 67.49


Last reset from software reset or reload

PXF processor tmc0 'system:pxf/ucode1' is running ( v4.1 ).

PXF processor tmc1 'system:pxf/ucode1' is running ( v4.1 ).

1 FastEthernet interface

4 Gigabit Ethernet interfaces

1 ATM interface

509K bytes of non-volatile configuration memory.


125440K bytes of ATA compact flash in bootdisk (Sector size 512 bytes).

125184K bytes of ATA compact flash in disk0 (Sector size 512 bytes).


Standby route processor in slot 0 is up with 524288K/32768K bytes of memory.

Standby image version:

Cisco IOS Software, 7300 Software (C7300-K91P-M), Version 12.2(27)SBC5, RELEASE SOFTWARE (fc1)

Technical Support: http://www.cisco.com/techsupport

Copyright (c) 1986-2006 by Cisco Systems, Inc.

Compiled Tue 20-Jun-06 11:24 by pwade


Configuration register is 0x2102


any idea about what's happening here?


thx a lot in advance.


cheers,


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 2.5 (2 ratings)
Loading.
mheusinger Mon, 12/04/2006 - 23:54
User Badges:
  • Green, 3000 points or more

Hello,


looks like a software bug:


1. %COMMON_FIB-4-FIBNULLIDB: Missing idb for fibidb [chars] (if_number [dec]).


An internal software error has occurred.


Recommended Action: Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


Related documents- No specific documents apply to this error message.


So recommendation would be to avoid to configure this or to upgrade IOS.


Hope this helps! Please rate all posts.


Regards, Martin

enriquebs Tue, 12/05/2006 - 00:18
User Badges:

Thx a lot for the reply, there is a TAC open finally. The thing is that the IOS is updated from a couple of months ago, and another update don't looks like the best option for the client, we'll look forward to the response.


cheers,

enriquebs Thu, 12/07/2006 - 08:02
User Badges:

HI all,


We got a little bit more information.

There is a bug which say that if you install a route in the FIB through a non existent VRF ID the NSE reboot... but here we have a doubt, how can you install a route in that way? what I mean is that if you type "ip route vrf NON_EXISTENT_VRF 10.1.1.0 255.255.255.0 15.1.1.254" where NON_EXISTENT_VRF is the name for a NON existent VRF in the router we get an error message saying something like the vrf don't exists... so... no way to install the route in the FIB.

Anyway, the thing is that the VRF exists in the router, then here we have the issue, the route is installed in the FIB via an static route through an existent VRF...

Any suggestion?


cheers,

smothuku Thu, 12/07/2006 - 11:48
User Badges:
  • Silver, 250 points or more

Hi ,


Below is the decode of the traceback seen on the router...Too many bugs are matching for the below decodes..


0x406DC2E0:errmsg(0x406dc2a8)+0x38

0x40471F1C:swidb_or_null_from_fibidb(0x40471ecc)+0x50

0x40515C98:ipfib_repopulate_single_fibidb(0x40515c70)+0x28

0x40471240:fibidb_handle_comingup(0x40471178)+0xc8

0x405491F8:fibidb_process_state_change(0x40549194)+0x64

0x4054987C:fibidb_message(0x40549420)+0x45c

0x4054A430:fib_lc_xdr_fibidb_decode(0x4054a418)+0x18

0x405378B0:xdr_client_decode_data(0x40537720)+0x190

0x4054DD1C:xdr_ipc_unpack_received_data(0x4054d74c)+0x5d0

0x4054037C:xdr_lc_service_received_ipcQ(0x405402fc)+0x80

0x405407D8:xdr_lc_background(0x405406e8)+0xf0



**** Let the TAC engineer examine it to know the root cause...


Thanks,

Satish

Actions

This Discussion