For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Sebastian_Aguir's avatar
Sebastian_Aguir
Icon for Nimbostratus rankNimbostratus
Jan 14, 2015

F5 Logging: Changing severity level from notice to critical

Hi, is there any way to change the level from a MCP event? I need to change it because i'm using a remote logging server and i want to filter the events by severity and reporting it through an e-mail account.

 

application delivery
LTM
management

3 Replies

  • Sebastian_Agui1's avatar
    Sebastian_Agui1
    Icon for Altostratus rankAltostratus
    Jan 15, 2015

    Thanks. The level was changed but the log doesn't send the alert with the new level :(

     

  • tatmotiv's avatar
    tatmotiv
    Icon for Cirrostratus rankCirrostratus
    Dec 07, 2016

    Stumbled upon this discussion because we are currently experiencing the same issue. We want to have link up/down syslog messages logged with severity error rather than informational. We tried to change the log level of the bcm56xxd daemon via 

    modify sys db log.bcm56xxd.level value Error
    , which will immediately result in the following message being logged locally:

    Dec  7 14:17:18 slot1/my-lb info bcm56xxd[8167]: 012c0012:6: Changing log level to Error

    Hence, I suppose the change did have some effect already. But then, when provoking a link down on this box (by disabling its switch port), there is no syslog event at all being logged. When changing the log level back to default (informational) and provoking another link outage, we can see the according syslog entry:

    Dec  7 13:36:39 slot1/my-lb info bcm56xxd[8167]: 012c0012:6: Changing log level to Error


Dec  7 13:51:02 slot1/my-lb info bcm56xxd[8167]: 012c0012:6: Changing log level to Informational

Dec  7 13:51:13 slot1/my-lb info bcm56xxd[8167]: 012c0015:6: Link: 1/1.1 is DOWN

    Any idea what we are missing? We already tried 

    save sys config
    as suggested above as well as restarting the syslog daemon, but there is no change in behaviour. There must be some other configuration missing which we are not aware of. To make it even more confusing, changing the log level to debug (also by changing the sys db value) on the other hand works, resulting in a more chatty version...

    Any help is appreciated. Many thanks in advance!!

    Martin