Getting the NAT: % Invalid Key lengths for tree insertionmessage on (5) 2800 routers in different locations running IOS 124. It is not impacting production. Checked cisco.com and did not come up with anything. Does anyone have any feedback/info regarding this message? Many thanks in advance.
I did some search, looks like this error message is generated when a code check during a key length calculation in NAT code. If the value returned is "0" then the error message is generated.
For example, and from what I saw this can often happen when we process a wrong packet with ip 0.0.0.0, that could be caused by a buggy packet sent to the router, or because of a bug on the router.
You can double check this by doing a "debug ip nat detail" and see what NAT was doing just before the error message, however this is a very chatty debug and you need to be cautious if you are going to try that in production.
If the error message occurs very often, I guess it's worth to already try to put a deny 0.0.0.0 in the acl attached to NAT and see if that stops. If not, then you probably need to go for controlled debugging session to find the guilty packets.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...