Reset Search



SNAP (0x00000000) is invalid. Correct value is (0x000000BB)

« Go Back


TitleSNAP (0x00000000) is invalid. Correct value is (0x000000BB)
  • Switch generating the following error message:

<Warn:EAPS.RxSNAPInv> MSM-A: 256:15, ctrl_755 - SNAP (0x00000000) is invalid. Correct value is (0x000000BB)
<Warn:EAPS.RxSNAPInv> MSM-A: 256:15, ctrl_704 - SNAP (0x00000000) is invalid. Correct value is (0x000000BB)
<Warn:EAPS.RxSNAPInv> MSM-A: 256:15, ctrl_703 - SNAP (0x00000000) is invalid.
Correct value is (0x000000BB)
<Warn:EAPS.RxSNAPInv> MSM-A: 256:15, ctrl_712 - SNAP (0x00000000) is invalid. Correct value is (0x000000BB)
<Warn:EAPS.RxSNAPInv> MSM-A: 256:15, ctrl_713 - SNAP (0x00000000) is invalid. Correct value is (0x000000BB)
<Warn:EAPS.Warning> MSM-A: EAPSD eaps_714 - No Protected Vlans have been added to the EAPS domain.
<Info:EAPS.RxPduRingDnFlush> MSM-A: EAPSD eaps_714 - Received RingDown-FlushFdb-Pdu (MAC = 00:04:96:8B:93:1D)

  • BD-8810
  • EXOS
  • The error message generated in switch logs might have caused due to possible programming error.
  • If sending station's packet itself has an incorrect SNAP ID, then most likely programming error while packet being created.
  • It could also be caused by another device on the ring modifying the EAPS PDU header.
  • In general, when EXOS sends the EAPS PDU it inserts the 0x000000BB value.
                          ((EnetTagHdr64_t *)buf)->llcSnap.dsap_ssap = LLC_LSAP_SNAP;
                          ((EnetTagHdr64_t *)buf)->llcSnap.control = 3;
                          ((EnetTagHdr64_t *)buf)->llcSnap.oui[0] = 0x00;
                          ((EnetTagHdr64_t *)buf)->llcSnap.oui[1] = 0xE0;
                          ((EnetTagHdr64_t *)buf)->llcSnap.oui[2] = 0x2B;
                          ((EnetTagHdr64_t *)buf)->llcSnap.type = htons(EEP_SNAP_ID);
  • When EXOS receives an EAPS PDU it checks for that value (0x000000BB). If the SNAP header is not the same, the PDU packet is dropped and the above mentioned error message is logged.
  • Switch reboot will resolve the possible programming error. After reboot, the switch logs will not generate any further logs related to SNAP ID.
  • If reboot did not resolve this issue, then we need to collect the logs from all switches participating in EAPS topology to understand which was sending the invlaid SNAP ID.
  • If the sending station's packet data differs from this packet, it would need further troubleshooting to isolate where in the network the SNAP field is getting modified.may have to capture packet using sniffer and compare with packet data at sending stations egress port.Also, we 
  • For further assistance, please check with GTAC.
Additional notes



Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255