I have two CPU7 in duplication.
Which configuration should I use and why ????
Embended or external network ???
-
wizzy
No, you can connect both CPU to switch (hub) and you can access to both CPU without problem. But in this case you must disable embedded ethernet (with XF03). If you enable this interface may be problem with switch (loop for IP packets).
If you enable embedded ethernet - you can connect only one CPU to external network. You will have access to this CPU directly and you will have access to CPU2 (external network-CPU1-embeddedb ethernet-CPU2). If CPU1 will be lost - you cannot access CPU2 (you can wait when Linux on CPU1 will started or connect patchcord to CPU2).
So external ethernet always enabled. Embedded (CPU-CPU) ethernet can be enabled, can be inhibited (the main rule - inhibit embedded ethernet if connect both CPU to external network).
If you enable embedded ethernet - you can connect only one CPU to external network. You will have access to this CPU directly and you will have access to CPU2 (external network-CPU1-embeddedb ethernet-CPU2). If CPU1 will be lost - you cannot access CPU2 (you can wait when Linux on CPU1 will started or connect patchcord to CPU2).
So external ethernet always enabled. Embedded (CPU-CPU) ethernet can be enabled, can be inhibited (the main rule - inhibit embedded ethernet if connect both CPU to external network).
-
spinman
I would say that you should always deactivate embedded ethernet and use 2 connections to the LAN, why? you say...
Because if u have to do maintenence on the CPU1 (with the only connection to the LAN) the embedded ethernet will stop work if you remove the CPU from the cabinett.
a tip, be sure to deactivate "spannig tree" protocol on the network switch, if it exists...
Because if u have to do maintenence on the CPU1 (with the only connection to the LAN) the embedded ethernet will stop work if you remove the CPU from the cabinett.
a tip, be sure to deactivate "spannig tree" protocol on the network switch, if it exists...

