Log filled with Psecure Message

cco_heerema · ‎10-22-2013

Hi All,

I've got an issue which has also been discussed on March 2008, and than marked as an ignorable error (as in will be solved in new IOS release)

Currently more than 5 years later I am also having this issue on one of my switches.

Here are the facts :

Stack of 5 3750X switches :

Switch Ports Model SW Version SW Image

------ ----- ----- ---------- ----------

1 54 WS-C3750X-48P 15.0(2)SE2 C3750E-IPBASEK9-M

2 54 WS-C3750X-48P 15.0(2)SE2 C3750E-IPBASEK9-M

* 3 54 WS-C3750X-48P 15.0(2)SE2 C3750E-IPBASEK9-M

4 54 WS-C3750X-48P 15.0(2)SE2 C3750E-IPBASEK9-M

5 54 WS-C3750X-48P 15.0(2)SE2 C3750E-IPBASEK9-M

Generates every 2minutes and 30 seconds this messages (so floods my logging)

Oct 22 13:58:24.330: PSECURE: Assert failure: psecure_sb->info.num_addrs <= psecure_sb->max_addrs: ../switch/psecure/psecure_utils.c: 144: psecure_update_address_counts (AESWSG02001-4)

Oct 22 13:58:24.330: -Traceback= 4FDBB8z 2444D98z 2450CB4z 2452C6Cz 742CCz 7196Cz 2149E4Cz 223EAF8z 26BF904z 26BA058z (AESWSG02001-4)

Oct 22 13:58:24.397: PSECURE: Assert failure: psecure_sb->info.num_addrs <= psecure_sb->max_addrs: ../switch/psecure/psecure_utils.c: 144: psecure_update_address_counts (AESWSG02001-4)

Oct 22 13:58:24.397: -Traceback= 4FDBB8z 2444D98z 2450CB4z 2452C6Cz 742CCz 7196Cz 2149E4Cz 223EAF8z 26BF904z 26BA058z (AESWSG02001-4)

Oct 22 14:00:54.648: PSECURE: Assert failure: psecure_sb->info.num_addrs <= psecure_sb->max_addrs: ../switch/psecure/psecure_utils.c: 144: psecure_update_address_counts (AESWSG02001-4)

Oct 22 14:00:54.648: -Traceback= 4FDBB8z 2444D98z 2450CB4z 2452C6Cz 742CCz 7196Cz 2149E4Cz 223EAF8z 26BF904z 26BA058z (AESWSG02001-4)

Oct 22 14:00:54.741: PSECURE: Assert failure: psecure_sb->info.num_addrs <= psecure_sb->max_addrs: ../switch/psecure/psecure_utils.c: 144: psecure_update_address_counts (AESWSG02001-4)

Oct 22 14:00:54.741: -Traceback= 4FDBB8z 2444D98z 2450CB4z 2452C6Cz 742CCz 7196Cz 2149E4Cz 223EAF8z 26BF904z 26BA058z (AESWSG02001-4)

Oct 22 14:03:24.334: PSECURE: Assert failure: psecure_sb->info.num_addrs <= psecure_sb->max_addrs: ../switch/psecure/psecure_utils.c: 144: psecure_update_address_counts (AESWSG02001-4)

Oct 22 14:03:24.334: -Traceback= 4FDBB8z 2444D98z 2450CB4z 2452C6Cz 742CCz 7196Cz 2149E4Cz 223EAF8z 26BF904z 26BA058z (AESWSG02001-4)

Oct 22 14:03:24.334: PSECURE: Assert failure: psecure_sb->info.num_addrs <= psecure_sb->max_addrs: ../switch/psecure/psecure_utils.c: 144: psecure_update_address_counts (AESWSG02001-4)

Oct 22 14:03:24.334: -Traceback= 4FDBB8z 2444D98z 2450CB4z 2452C6Cz 742CCz 7196Cz 2149E4Cz 223EAF8z 26BF904z 26BA058z (AESWSG02001-4)

I have searched and searched but could not find any sollution, so I hope I overlooked the right information and you could point me to it

I do use (and need) portsecurity on these switches (also the stack member which is generating the error) and reloading the stack is not realy an option as we are running full production with limited service window.

But again to keep my logs clean, and usable (now all messageges get overwritten by the error every 150 seconds) I would like to get rid of this.

Thanks for your help & time

Marvin Rhoads · ‎10-22-2013

You could try using a logging discriminator to keep the unwanted message from being generated in the first place.

Have a look at this thread where I descibe its use.

wstephanos · ‎10-24-2013

Hi cco_heerema

We have a few hundred stacks deployed with 15.0(1)SE2 and 15.0(2)SE2. About a dozen of them have the same LOG issue i.e. they are filled with the following messages. Most of the rest also have Traceback messsages and other messages related to psecure_sb->. This is related to the Port Security commands.

Oct 24 18:32:10.200 UTC: PSECURE: Assert failure: psecure_sb->info.num_addrs <= psecure_sb->max_addrs: ../switch/psecure/psecure_utils.c: 144: psecure_update_address_counts
Oct 24 18:32:10.200 UTC: -Traceback= 4FDBB8z 2444D98z 2450CB4z 2452C6Cz 742CCz 7196Cz 2149E4Cz 223EAF8z 26BF904z 26BA058z

Switch Ports Model SW Version SW Image

------ ----- ----- ---------- ----------

* 1 54 WS-C3750X-48P 15.0(2)SE2 C3750E-UNIVERSALK9-M

2 54 WS-C3750X-48P 15.0(2)SE2 C3750E-UNIVERSALK9-M

3 54 WS-C3750X-48P 15.0(2)SE2 C3750E-UNIVERSALK9-M

4 54 WS-C3750X-48P 15.0(2)SE2 C3750E-UNIVERSALK9-M

5 54 WS-C3750X-48P 15.0(2)SE2 C3750E-UNIVERSALK9-M

6 54 WS-C3750X-48P 15.0(2)SE2 C3750E-UNIVERSALK9-M

7 54 WS-C3750X-48P 15.0(2)SE2 C3750E-UNIVERSALK9-M

We have tested a stack that had that a similar issue and were able to get rid of those messages with the new IOS Release 15.2(1)E.

Switch Ports Model SW Version SW Image

------ ----- ----- ---------- ----------

1 54 WS-C3750X-48P 15.2(1)E C3750E-UNIVERSALK9-M

2 54 WS-C3750X-48P 15.2(1)E C3750E-UNIVERSALK9-M

3 54 WS-C3750X-48P 15.2(1)E C3750E-UNIVERSALK9-M

4 54 WS-C3750X-48P 15.2(1)E C3750E-UNIVERSALK9-M

* 5 54 WS-C3750X-48P 15.2(1)E C3750E-UNIVERSALK9-M

6 54 WS-C3750X-48P 15.2(1)E C3750E-UNIVERSALK9-M

7 54 WS-C3750X-48P 15.2(1)E C3750E-UNIVERSALK9-M

8 54 WS-C3750X-48P 15.2(1)E C3750E-UNIVERSALK9-M

We plan on testing 15.2(1) E on a few more stacks to see if we can get good results too.

If you try it let us know what you find out.

Thanks

Good luck.

William

cco_heerema · ‎12-02-2013

William,

Still looking for a stable less problem version of IOS 15 at this moment.

Just posted a question regarding this issue (as all IOS15's are ED) to get some advise which version should be "stable".

I am getting lost in all the ED's and just looking for that one stablised golden version.