CSCsw43211 or some variant thereof, upgrade to SRD2 was last suggestion I was given.
I would personally avoid SRD2 having good experience /so far/ with SRD3 for PPP termination. Dave. Youssef Bengelloun-Zahr wrote: > Hello list, > > I have been receiving theese messages for months now on several routers of > ours (7204 VXR, NPE-400 / NPE-G1, running > c7200-adventerprisek9-mz.122-33.SRD.bin). > > Jun 24 14:05:41.306: %IDMGR-3-INVALID_ID: bad id in id_to_ptr (bad id) (id: > 0x0) > -Traceback= 6061CB64 6061D0C4 6063762C 6109238C 61094A38 61A3E32C 61A49F2C > 61A49F84 613B4710 613AF418 613A4688 613A4D7C 613A50C4 613A2C48 613A2C8C > 61399658 > Jun 24 17:27:52.335: %IDMGR-3-INVALID_ID: bad id in id_to_ptr (bad id) (id: > 0x0) > -Traceback= 6061CB64 6061D0C4 6063762C 6109238C 61094A38 61A3E32C 61A49F2C > 61A49F84 613B4710 613AF418 613A4688 613A4D7C 613A50C4 613A2C48 613A2C8C > 61399658 > Jun 25 15:35:54.875: %IDMGR-3-INVALID_ID: bad id in id_to_ptr (bad id) (id: > 0x0) > -Traceback= 6061CB64 6061D0C4 6063762C 6109238C 61094A38 61A3E32C 61A49F2C > 61A49F84 613B4710 613AF418 613A4688 613A4D7C 613A50C4 613A2C48 613A2C8C > 61399658 > Jun 26 13:07:35.158: %IDMGR-3-INVALID_ID: bad id in id_to_ptr (bad id) (id: > 0x0) > -Traceback= 6061CB64 6061D0C4 6063762C 6109238C 61094A38 61A3E32C 61A49F2C > 61A49F84 613B4710 613AF418 613A4688 613A4D7C 613A50C4 613A2C48 613A2C8C > 61399658 > Jun 26 13:42:48.262: %IDMGR-3-INVALID_ID: bad id in id_to_ptr (bad id) (id: > 0x0) > -Traceback= 6061CB64 6061D0C4 6063762C 6109238C 61094A38 61A3E32C 61A49F2C > 61A49F84 613B4710 613AF418 613A4688 613A4D7C 613A50C4 613A2C48 613A2C8C > 61399658 > Jun 27 04:01:23.083: %RADIUS-4-RADIUS_DEAD: RADIUS server > 77.246.81.66:1812,1813 > is not responding. > Jun 27 04:01:23.083: %RADIUS-4-RADIUS_ALIVE: RADIUS server > 77.246.81.66:1812,1813 > is being marked alive. > Jun 28 03:17:46.715: %IDMGR-3-INVALID_ID: bad id in id_to_ptr (bad id) (id: > 0x0) > -Traceback= 6061CB64 6061D0C4 6063762C 6109238C 61094A38 61A3E32C 61A49F2C > 61A49F84 613B4710 613AF418 613A4688 613A4D7C 613A50C4 613A2C48 613A2C8C > 61399658 > Jun 28 12:56:51.295: %IDMGR-3-INVALID_ID: bad id in id_to_ptr (bad id) (id: > 0x0) > -Traceback= 6061CB64 6061D0C4 6063762C 6109238C 61094A38 61A3E32C 61A49F2C > 61A49F84 613B4710 613AF418 613A4688 613A4D7C 613A50C4 613A2C48 613A2C8C > 61399658 > Jun 28 12:56:52.495: %IDMGR-3-INVALID_ID: bad id in id_to_ptr (bad id) (id: > 0x0) > -Traceback= 6061CB64 6061D0C4 6063762C 6109238C 61094A38 61A3E32C 61A49F2C > 61A49F84 613B4710 613AF418 613A4688 613A4D7C 613A50C4 613A2C48 613A2C8C > 61399658 > Jun 28 12:56:52.555: %IDMGR-3-INVALID_ID: bad id in id_to_ptr (bad id) (id: > 0x0) > -Traceback= 6061CB64 6061D0C4 6063762C 6109238C 61094A38 61A3E32C 61A49F2C > 61A49F84 613B4710 613AF418 613A4688 613A4D7C 613A50C4 613A2C48 613A2C8C > 61399658 > Jun 29 09:19:59.935: %IDMGR-3-INVALID_ID: bad id in id_to_ptr (bad id) (id: > 0x0) > -Traceback= 6061CB64 6061D0C4 6063762C 6109238C 61094A38 61A3E32C 61A49F2C > 61A49F84 613B4710 613AF418 613A4688 613A4D7C 613A50C4 613A2C48 613A2C8C > 61399658 > > > I tried to google this but nothing really interesting related to my > plateform. Anyone out there might know what theese mean ? > > Thanks. > > Best regards. > > Y. > -- David Freedman Group Network Engineering Claranet Group _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
