NCS540 XR6.3 interface issues

[saul alonso ramos]

Hi,

We just receive a NCS 540 with IOS-XR 6.33 in our lab to do some preflight test before implementing in a customer and found an estrange issue that we want to know if is a normal behaviour.

When we take out a transceiver from the 100G interface and plug another one (to simulate the change of a faulty interface) sometimes it went up quickly but most of the times it stays down.

We're receiving also an estrange message in the log that looks like from the subjacent linux system:

LC/0/0/CPU0:Jan 30 09:12:30.327 UTC: syslog_dev[112]: optics_driver[318] PID-28292: ATTEMPT failed at mcdAutoNegPortCtrlStop:1682
LC/0/0/CPU0:Jan 30 09:12:30.347 UTC: syslog_dev[112]: optics_driver[318] PID-28292: ATTEMPT failed at mcdAutoNegPortCtrlStop:1682
LC/0/0/CPU0:Jan 30 09:12:30.366 UTC: syslog_dev[112]: optics_driver[318] PID-28292: ATTEMPT failed at mcdAutoNegPortCtrlStop:1682
LC/0/0/CPU0:Jan 30 09:12:30.385 UTC: syslog_dev[112]: optics_driver[318] PID-28292: ATTEMPT failed at mcdAutoNegPortCtrlStop:1682

This message is shown also when the optic went up but is not always shown.

Thanks in advance,

[smilstea]

Can you send a show controller for the port in question?

Is the log only seen when you move ports or constantly?

What length is the fiber between the two end-points?

Does the port come up?

Any crashes on the router?

Sam

[saul alonso ramos · Accepted solution]

Hi Sam,

We were able to pinpoint/resolve the issue, was a batch of optical
transceiver whose lasers were turned on even if the interface was shutdow.
After we got another CFP2 batch issue was solved.

Regards,