Alcatel Unleashed

Posted: **27 Jun 2024 05:05**

Hello forum,
We have some problems with errors on port 1/1/7 on a OS6570M-12 with AOS 8.9.221.R03

Swlog shows nothing special. Can I add more logging to identify the problem?
I use:

Code: Select all

swlog syslog-facility-id local2

Should I use another id?

Code: Select all

Chassis/Slot/Port          : 1/1/7   
 Operational Status        : up,
 Port-Down/Violation Reason: None,
 Last Time Link Changed    : Thu Jun 27 10:16:29 2024,
 Number of Status Change   : 3,
 Type                      : Ethernet,
 SFP/XFP                   : N/A,
 Interface Type            : Copper,
 EPP                       : Disabled,
 Link-Quality              : N/A,
 MAC address               : REDACTED,
 BandWidth (Megabits)      :       10,                  Duplex           : Half,
 Autonegotiation           :   0  [                              ],
 Long Frame Size(Bytes)    : 9216,
 Inter Frame Gap(Bytes)    : 12,
 loopback mode             : N/A,
 Rx              :
 Bytes Received  :              4460954, Unicast Frames :                21832,
 Broadcast Frames:                    0, M-cast Frames  :                 1666,
 UnderSize Frames:                    0, OverSize Frames:                    0,
 Lost Frames     :                    0, Error Frames   :                   34,
 CRC Error Frames:                   34, Alignments Err :                    0,
 Tx              :
 Bytes Xmitted   :              7805132, Unicast Frames :                24317,
 Broadcast Frames:                    0, M-cast Frames  :                14410,
 UnderSize Frames:                    0, OverSize Frames:                    0,
 Lost Frames     :                    0, Collided Frames:                    0,
 Error Frames    :                    0, Collisions     :                    0,
 Late collisions :                    0, Exc-Collisions :                    0
 
 
  Model Name:                    OS6570M-12,
  Module Type:                   0xd062201,
  Description:                   8G 4SFP+ METRO PTP,
  Part Number:                   904390-90,
  Hardware Revision:             03,
  Manufacture Date:              Nov 14 2023,
  Admin Status:                  POWER ON,
  Operational Status:            UP,
  Number Of Resets:              5,


   /flash/working
   Package           Release                 Size     Description
-----------------+-------------------------+---------+-----------------------------------
Wos.img           8.9.221.R03               125459560 Alcatel-Lucent OS


Chassis 1
CPU Manufacturer                  : Marvell
CPU Model                         : ARM
Flash Manufacturer                : Memphis
Flash size                        : 7639363584 bytes
RAM size                          : 1915684kB
FPGA version                      : 0.11
FPGA Manufacturer                 : Lattice
U-Boot Version                    : 8.9.139.R03
Power Supplies Present            : 1
NIs Present

Posted: **27 Jun 2024 06:19**

The Port is running on 10 Halfduplex, which is an indication for a faulty cable connection.

Posted: **27 Jun 2024 07:20**

10Mbps half duplex is by design. The connected device only has 10Mps half duplex.
The port is manually set. It was set to autoneg earlier. Still got error frames.

My question is how to get the correct log-level so I can match the events from the connected device.

Posted: **27 Jun 2024 07:34**

It looks like it started when we replaced the old OS6450-10 to OS6570M-12

Posted: **27 Jun 2024 08:32**

with "swlog appid *** subapp all level debug3" you see the most infos in the swlog-output.
To finde the correct appid use "swlog appid ?" - all possibilitiesa are listed.
You can look into your acutal swlog to find it too. I try f.e. this command after changing a port:

Code: Select all

show log swlog timestamp 06/27/2024 14:00:00 | grep -i ni
....
2024 Jun 27 14:26:57.525 SW105_ALD-1_Silvio swlogd portMgrNi main INFO: : [pmnHALLinkStatusCallback:208] LINKSTS 1/1/1 DOWN (gport 0x0) Speed 1000 Duplex HALF
2024 Jun 27 14:26:57.530 SW105_ALD-1_Silvio swlogd stpNi _SOKt INFO: stpnimsg_processMsgFromPM: PM_LINK_STATUS_MSGID gPort=x0 linkStatus=0
2024 Jun 27 14:26:57.532 SW105_ALD-1_Silvio swlogd intfNi Drv INFO: niEsmSendLinkStatusChgMsg(1153): linkstatus DOWN sent on peerId=1
2024 Jun 27 14:26:57.563 SW105_ALD-1_Silvio swlogd intfCmm Mgr INFO: cmmEsmHandleNiMsg: Rx CMM_ESM_LINK_STATUS_CHG from chassis 1 NI 1
2024 Jun 27 14:26:57.926 SW105_ALD-1_Silvio swlogd portMgrNi main INFO: : [pmnHALLinkStatusCallback:208] LINKSTS 1/1/7 DOWN (gport 0x6) Speed 1000 Duplex HALF
2024 Jun 27 14:26:57.926 SW105_ALD-1_Silvio swlogd intfNi Drv INFO: niEsmSendLinkStatusChgMsg(1153): linkstatus DOWN sent on peerId=1

So I see portMgrNI, intfNI are possible appids.
After that you should set the log-level back to info.
BR Silvio

Posted: **27 Jun 2024 09:38**

Thank you for the information.
The swlog did not catch anything while I got an error frame.

Code: Select all

swlog syslog-facility-id 18
swlog appid portMgrNi subapp all level debug3
swlog appid intfNi subapp all level debug3

Is there documentation on the different appid? In the manual they are just listed.

We also replaced four OS6450-24XM with OS6560-24X4 which also have the 10Mbps half duplex device and they get no errors.
We get the frame errors on the four OS6570M-12 just in different amount.

The main server reports RNRP node_down and then node_up to the devices around the same time as we get error frames om the OS6570M-12 so it feels connected.

We might roll-back to the old OS6450-10 to see if the errors goes away.

Posted: **29 Jun 2024 04:37**

Is there documentation on the different appid?

Not realy

The reason for CRC errors are mostly cable or connector issues. If the same cables are working at other types of switches without errors than there is an issue at the switch. Do you use the newest AOS release, Uboot and FPGA at the affected switches? If yes you should open a ticket at ALE.
Do you see any errors in the network that are based on this errors? Maybe this is only a monitoring issue?
best regards
Silvio

Posted: **16 Dec 2024 05:57**

We opened a ticket to ALE and they where able to reproduce the problem with 10Mbps half-duplex.
They believe the problem is in the chipset. They have a private pre-release for us to test.

Posted: **08 Apr 2025 01:40**

The chipset in the OS6570M-12 does NOT support 10Mbps half duplex. ALE made a special firmware but that didn't work.
They want us to try the OS6465T-12 which has another chipset.

Alcatel Unleashed

more logging

more logging

Re: more logging

Re: more logging

Re: more logging

Re: more logging

Re: more logging

Re: more logging

Re: more logging

OS6570M-12 10Mbps half duplex