Guest

Good afternon,

I'm having problems with CP 1623 - MAC duplicated. The Project i'm working for is compossed by
2 redundant pairs and 1 engineering station, i'm using just one CP 1623 in each computer.

Until 2 days ago i didn'd have any problema, but we are still working on Fiber Optic ring and we tried to close it. Before close the ring, i've checked the scalances x-204 configuration and assigned IP address to all of them and also set all of them but one, as HSR Client, the last one is HSR Manager.

When we close the ring we received a message in all computers taht says, "CP 1623 Mac duplicated has been detected". I could not solve the problem so i decided to shut down 2 computers to see what happens and the messages disppears but itis not clear what is going on in the network!.

This problema happen with any computer equipped with CP1623, even the ES.

I have an Excel list with all IP and MAC addresses of all components of the network and i'm very sure there is not any MAC or IP duplicated.


Could any body help me?

I've just right now the same problem. Did you get an answer?

Could you fix it?

Many thanks

Hi together,

two ports of CP 1623 (also ports on newer S7 ethernet CPs) are not independent network interfaces. So you can imaging them like a 3 port switch (two pointing outside, one pointing inside).  If you connect both (outside) ports of CP 1623 to the same layer 2 network, the CP sees its own traffic and so you have duplicated addresses.

Regards,

Towome

I am facing same problem. 

But I requred both port of CP on same layer of ethernet.

Hello,

only one my idea, with some SW can be this card be configured as like 2-port switch or 2 indipendent IPs ports. So probably I'll be check that. Sry I've never worked with it, only quick idea, maybe unhelpfully.

I have solved it.

You have to configure 2 ports of all scalance in Ring mode. Create a Ring using 2 server, 1 ES and 2 ports of all Scalance Swicth.

after configuration we were still facing duplication of MAC problem. To resolve the issue we just disabled media redundancy in 400H CPUs which was connected at other ports of  SCALANCE.

If you want to take 400H CPUs in redundancy then it should be set as client and include it in Ring created earlier.

One scalance will be Master and all others will be client.

Hope it may help.