This document will describe on how to validate/check CRC on  the physical interface attributes on SD.

When working on Fusion setup, there might be errors on extended ports, if we want to check on the errors and physical attributes of extended ports.

If we run commands on AD, it might not show any CRC/errors on extended interface, but peer devices are receiving the errors.

As below we are not seeing any abnormal here

labroot@host-re0> show interfaces ge-101/0/0 extensive | match "link|error|speed|nego" 
Physical interface: ge-101/0/0, Enabled, Physical link is Up, Extended Port
  Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode, Link-mode: Full-duplex, Speed: 100mbps, BPDU Error: None,
  Loop Detect PDU Error: None, Ethernet-Switching Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled,
  Flow control: Enabled, Auto-negotiation: Enabled, Remote fault: Online, IEEE 802.3az Energy Efficient Ethernet: Disabled, Auto-MDIX: Enabled
  Link flags     : None
  Input errors:
    Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0,
    FIFO errors: 0, Resource errors: 0
  Output errors:
    Carrier transitions: 3, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0,
    Resource errors: 0
    CRC/Align errors                         0                0
    FIFO errors                              0                0
    Total errors                             0                0
    Output packet error count                                 0
  Autonegotiation information:
    Negotiation status: Complete
    Link partner:
        Link mode: Full-duplex, Flow control: None, Remote fault: OK, Link partner Speed: 100 Mbps
        Flow control: None, Remote fault: Link OK

 Once login the Satellite Device using the below command and check on the partner attributes, we do see that we are not in full-duplex mode, which is causing the CRC errors on peer device.

> request chassis satellite login fpc-slot 150

spfe$ vty

spfe# show int ge-0/0/0

Physical device ge-0/0/0 (Index 127, context 0x53cba5a8)

Chassis slot = 0, Type: Gig Ethernet, Port: 0, Subport: 0, pic_i2cid: 0xf03b

Speed: 100MBps (Configured 1GBps), MTU: 1514 bytes (cfg mtu 1514), Header: 0, Link select: 2

Auto Negotiation Info:

Configuration:

Enabled, Duplex:Full, Speed: Unspecified

Completed: Yes

Link Partner:

Link OK: Yes, Offline: No, Failed: No, Antoneg error: No

Half Duplex, Pause: 0x0, ASM pause: 0x0

Speed: 100MBps

Local Link:

Full Duplex, Pause: 0x0

Speed: 100MBps