Public-service ip not work after Harmonic cOS upgrade to 3.28.2.

[LiQuan]

Hi,

3.21.15:   no network issue.  cOS ping WAN IP OK

Upgrade to 3.28.2:  network issue.   Fail to ping any IP if no "source-ip" option.

CM didn't get an IP address from DHCP server. 

Is there any one(expert) tell me how to fix this network issue?

Thanks a lot.

[Arkadiusz Wroblewski]

Hello and Welcome to The Community @LiQuan 

This is not really related to Atlassian.

Please keep in mind that this is an Atlassian Community forum, so topics should generally be connected to Atlassian products or the Atlassian ecosystem.

I can try to help this one time, since I also work in IT Support and Infrastructure Administration.

The fact that ping only works when you specify a source-ip after upgrading from 3.21.15 to 3.28.2 points toward a change in routing, default source interfaces, or service IP behavior. This aligns with your DHCP relay statistics, which show DISCOVER and OFFER but no REQUEST or ACK. The handshake isn't completing, likely because the return path or interface mapping was altered by the firmware update.

I recommend opening a case with Harmonic Support and providing them with a clear comparison: the working version (3.21.15) versus the failing one (3.28.2), examples of the failing ping versus the working source-ip ping, your DHCP relay stats, and your routing table configuration to see if this is a known regression in 3.28.2.