OS6350: Successfully processed the link status change to CMM

[mawe]

Hi,

I have a little network on a customer site with four 6350-Switches. The "Core" is showing the following Messages:

Code: Select all

Apr 11 18:06:37 172.30.20.21 Apr 11 18:06:38 BVS-LAU-Core INTERFACE(6) Data: updateLinkStatus:165 Updating link status info in CMM for lport - 16 and linksta 
Apr 11 18:06:37 172.30.20.21 Apr 11 18:06:38 BVS-LAU-Core INTERFACE(6) Data: [Count.]te - 2 
Apr 11 18:06:39 172.30.20.21 Apr 11 18:06:39 BVS-LAU-Core INTERFACE(6) Data: eniLinkStatusChange:5991 Successfully processed the link status change to CMM fo 
Apr 11 18:06:39 172.30.20.21 Apr 11 18:06:39 BVS-LAU-Core INTERFACE(6) Data: [Count.]r lport - 16 and linkstatus - 1 
Apr 11 18:06:39 172.30.20.21 Apr 11 18:06:39 BVS-LAU-Core INTERFACE(6) Data: eniSendLinkStatusMsg2falcaddr:1223 eni_send_to_socket to CMM Successful 
Apr 11 18:06:39 172.30.20.21 Apr 11 18:06:39 BVS-LAU-Core VLAN(8) Data: vm ni rx from:AppID = 6   SnapID = 0  
Apr 11 18:06:39 172.30.20.21 Apr 11 18:06:39 BVS-LAU-Core INTERFACE(6) Data: updateLinkStatus:165 Updating link status info in CMM for lport - 16 and linksta 
Apr 11 18:06:39 172.30.20.21 Apr 11 18:06:39 BVS-LAU-Core INTERFACE(6) Data: [Count.]te - 1 
Apr 11 18:08:15 172.30.20.21 Apr 11 18:08:15 BVS-LAU-Core INTERFACE(6) Data: [Count.]e - 2 
Apr 11 18:08:19 172.30.20.21 Apr 11 18:08:19 BVS-LAU-Core INTERFACE(6) Data: eniLinkStatusChange:5991 Successfully processed the link status change to CMM fo 
Apr 11 18:08:19 172.30.20.21 Apr 11 18:08:19 BVS-LAU-Core INTERFACE(6) Data: [Count.]r lport - 5 and linkstatus - 1 
Apr 11 18:08:19 172.30.20.21 Apr 11 18:08:19 BVS-LAU-Core INTERFACE(6) Data: eniSendLinkStatusMsg2falcaddr:1223 eni_send_to_socket to CMM Successful 
Apr 11 18:08:19 172.30.20.21 Apr 11 18:08:19 BVS-LAU-Core VLAN(8) Data: vm ni rx from:AppID = 6   SnapID = 0  
Apr 11 18:08:19 172.30.20.21 Apr 11 18:08:19 BVS-LAU-Core INTERFACE(6) Data: updateLinkStatus:165 Updating link status info in CMM for lport - 5 and linkstat 
Apr 11 18:08:19 172.30.20.21 Apr 11 18:08:19 BVS-LAU-Core INTERFACE(6) Data: [Count.]e - 1 
Apr 11 18:09:41 172.30.20.21 Apr 11 18:09:41 BVS-LAU-Core INTERFACE(6) Data: eniLinkStatusChange:5991 Successfully processed the link status change to CMM fo 
Apr 11 18:09:41 172.30.20.21 Apr 11 18:09:41 BVS-LAU-Core INTERFACE(6) Data: [Count.]r lport - 20 and linkstatus - 2 
Apr 11 18:09:41 172.30.20.21 Apr 11 18:09:41 BVS-LAU-Core INTERFACE(6) Data: eniSendLinkStatusMsg2falcaddr:1223 eni_send_to_socket to CMM Successful 
Apr 11 18:09:41 172.30.20.21 Apr 11 18:09:41 BVS-LAU-Core VLAN(8) Data: vm ni rx from:AppID = 6   SnapID = 0  
Apr 11 18:09:41 172.30.20.21 Apr 11 18:09:41 BVS-LAU-Core INTERFACE(6) Data: updateLinkStatus:165 Updating link status info in CMM for lport - 20 and linksta 
Apr 11 18:09:41 172.30.20.21 Apr 11 18:09:41 BVS-LAU-Core INTERFACE(6) Data: [Count.]te - 2 
Apr 11 18:09:43 172.30.20.21 Apr 11 18:09:43 BVS-LAU-Core INTERFACE(6) Data: eniLinkStatusChange:5991 Successfully processed the link status change to CMM fo 
Apr 11 18:09:43 172.30.20.21 Apr 11 18:09:43 BVS-LAU-Core INTERFACE(6) Data: [Count.]r lport - 20 and linkstatus - 1 
Apr 11 18:09:43 172.30.20.21 Apr 11 18:09:43 BVS-LAU-Core INTERFACE(6) Data: eniSendLinkStatusMsg2falcaddr:1223 eni_send_to_socket to CMM Successful 
Apr 11 18:09:43 172.30.20.21 Apr 11 18:09:43 BVS-LAU-Core VLAN(8) Data: vm ni rx from:AppID = 6   SnapID = 0  

Sometimes additional the STP-Topology changes with this:

Code: Select all

Apr 11 18:09:43 172.30.20.21 Apr 11 18:09:43 BVS-LAU-Core INTERFACE(6) Data: [Count.]te - 1 
Apr 11 18:09:45 172.30.20.21 Apr 11 18:09:45 BVS-LAU-Core STP(11) Data: Topology changed on VLAN/STP id 4 
Apr 11 18:09:52 172.30.20.21 Apr 11 18:09:52 BVS-LAU-Core STP(11) Data: Topology changed on VLAN/STP id 1 

Any ideas what is wrong? What did "lport" mean? The customer-site is expericening slow network connections sometimes, but the CPU Health is ok so I'm not thinking that there's a loop.

Thanks, Marco

[silvio]

Hi,
some weeks ago I had the same question to alcatel support. Here the answer:
These swlog messages were added to debug an issue related to ports not coming up. When the ESM(Ethernet Switch module) or interface tries to send a message to any application, and if the message is sent successfully, these debugs will be printed. These debug logs were added as part of the PR 211615 to narrow down the lost message between CMM and NI communication. The logs seen on the customer’s network might not be due to interface link status changes as the ESM messages also prints those debug logs.

- lport-16 denotes the 1/17 interface(lport-0 is 1st interface on the switch), link status 1 shows that port is up and link status 2 means that port is down.
This info message displays in swlog every time the vlan port association occurs. So, any interfaces coming up will trigger the messages as the port gets assigned to the vlan as per the configuration. These messages can be suppressed by the following command:
-> swlog appid vlan level warning