SECC discovery wrong IP

How it presents

Symptom

SECC discovery wrong IP — vehicle cannot find SECC on the expected link-local/IP path; handshake dies at discovery/SDP. protocol field note: keep evidence scrubbed and prove the ranked cause before module RMA on CCS-H09.

Root causes (by observed frequency)

1. #1 SECC IP/VLAN misconfig after network change

   Protocol before power

2. #2 Switch blocking necessary discovery traffic
3. #3 Wrong SECC firmware/profile for the vehicle cohort
4. #4 Cable/PE issue mis-reported as discovery fail

Diagnostic procedure

1. 1. Capture stage: SDP/discovery vs later SLAC/ISO

   Expected: Fails at discovery

   Tools: SECC logs

2. 2. Verify SECC network settings vs OEM commissioning

   Expected: Correct IP/VLAN

   Tools: OEM tool

3. 3. Check switch ACLs/mirroring not dropping discovery

   Expected: Allowed

   Tools: IT

4. 4. Known-good vehicle/cable prove

   Expected: Discovery succeeds

   Tools: known-good

5. 5. OEM SECC config/FW only after network path proven

   Tools: OEM

The fix

Wrong SECC discovery IP is network/SECC config — confirm before power-module blame.

1. Correct SECC IP/VLAN to the commissioning standard. Document readings and scrubbed photos for CCS-H09 before closing the ticket.
2. Fix switch ACL issues blocking discovery. Document readings and scrubbed photos for CCS-H09 before closing the ticket.
3. Prove with known-good cable/vehicle. Document readings and scrubbed photos for CCS-H09 before closing the ticket.
4. Apply OEM SECC firmware/profile updates as required. Document readings and scrubbed photos for CCS-H09 before closing the ticket.
5. Validate full CCS start after discovery succeeds. Document readings and scrubbed photos for CCS-H09 before closing the ticket.