swlog running full as no additional VC-Chassis

[ruemelin]

Hi,

on our NMS I get warnings within the last days that the swlog of a switch is going to fail as it is running full.
looking into the swlog I get a mass of thouse messages:

Code: Select all

2023 Mar 13 08:11:29.624 $SWITCH-NAME swlogd lpCmm LanCmmMip ERR: lpMipGetChassisSlotAndNextVcSlot 176:
2023 Mar 13 08:11:29.624 $SWITCH-NAME swlogd ^^ repeated 1 times
2023 Mar 13 08:11:29.624 $SWITCH-NAME swlogd lpCmm LanCmmMip ERR: lpGetNextChassisSlot 721: i > MAX_VC_CHASSIS_ID No valid Chassis/Slot found
2023 Mar 13 08:11:29.624 $SWITCH-NAME swlogd lpCmm LanCmmMip ERR: lpMipGetChassisSlotAndNextVcSlot188:

Thouse appear about every 5 to 60 seconds ant then 7 times within this same second. For me it looks like the switch is seeing it as an error that it cannot find a further chassis in the VC.
The switch does not have a second chassis connected and does not have any issues I am aware of. Anyone an idea how I could get rid of the messages, I would like to understand them and keep my log clear

Best Regards
Norbert

[Gleylancer]

Try to disable auto-fabric

[ruemelin]

Hi,

tanks for the input, I would like not not just try randomly as the switch is in a remote location and productive there. So I would like to be quite sure what I am doing. In this case when looking for

Code: Select all

sh auto-fabric config

I get

Code: Select all

Auto-fabric Status          : Disable,
Config Save Timer Status    : Disabled,
Config Save Timer Interval  : 300 seconds,
Default UNP SAP Profile     : Auto-vlan,
Discovery Interval          : 0 minute(s),
Discovery Status            : Idle,
LACP Discovery Status       : Enabled,
LBD Discovery Status        : Enabled,
MVRP Discovery Status       : Enabled,
OSPFv2 Discovery Status     : Enabled,
OSPFv3 Discovery Status     : Enabled,
ISIS Discovery Status       : Enabled,
SPB Discovery Status        : Enabled

so it looks like Auto-fabric is already disabled and thus it should not have an effect to disable it.

Regards