This is the exact Syslog message from our Graylog:
vx-sw-b7-01 fpc0 BMACSEC Error: API bmacsec_event_handler((int)macsec_addr) at bcm_macsec_event_handler:562 -> Invalid parameter
As you can see the log level is on warning and not on informational.
Do you have some additional informations for me? For example why the "Status: inuse Create time" is on 00:00:00 on the EX3400, but not on the EX4300? Or why the log level is on warning and not on informational?
QUE:- why the "Status: inuse Create time" is on 00:00:00 on the EX3400, but not on the EX4300?
:- This is strange, "in use" shows that the associations is thr and both inbound and outbound associations is visible.
Did you check if you had any flaps omn teh said interface and after that macsec went to a stuck time state ??
ANy knowhow of when it went into the said state?
QUE:- Or why the log level is on warning and not on informational? J:- This is a debug log and hence a warning, but as per cases reported and response from engineering the same can be listed as informational and can be ignored. Junos logging wont explicitly log it as informational.
So you are telling me, that this is common behaviour to throw like 300 debug messages per minute? Is there something official, like a KB or anything? Dont get me wrong, I simply want to be sure that everything is allright with our encrypted connection and our data is safe.
The strange thing is simply, that on our EX4300 everything is fine. No syslog messages and "Status: inuse Create time" has a fitting time.
The error messages is seen due to the EX3400 chipset and the junos code. That is why you only see it on ex3400 and not on ex4300. These are generated due to the additional debugging capabilities added in the code and can be safely ignored. You can filter the logs messages with the following kb
Firstly, We do not have a Kb written for the said log while I am writing this post. [I will make sure we write one and update this forum post].
Secondly, Regarding the create time stuck at 0:0, I believe the NTP not sync and the time stuck back to Epoc(1970) is the cause of the stuck "create time". Interface flap might not recover the stuck macsec timer.
I propose to reboot the EX3400 to revert the stuck timer for the macsec timer. If that is not the possibility I suggest open a JTAC case to get a recovery without reboot.