GE C60 Instruction Manual

Also see for C60: Communications manual Communications guide Instruction manual Instruction manual Instruction manual

Contents

5-46 C60 BREAKER PROTECTION SYSTEM – INSTRUCTION MANUALPRODUCT SETUP CHAPTER 5: SETTINGS5PRT2 REDUNDANCY — Determines if ports 2 and 3 operate in redundant or independent mode. If a license for PRP waspurchased, the options are None, Failover, and PRP. If a license for PRP was not purchased, the options are None andFailover. In non-redundant mode (REDUNDANCY set to None), ports 2 and 3 operate independently with their own MAC, IP,and mask addresses. If REDUNDANCY is set to Failover, the operation of ports 2 and 3 is as follows:• Ports 2 and 3 use the port 2 MAC address, IP address, and mask• The configuration fields for IP address and mask on port 3 are hidden• Port 3 is in standby mode and does not actively communicate on the Ethernet network but monitors its link to theMultilink switch. If port 2 detects a problem with the link, communications is switched to Port 3. Port 3 is, in effect,acting as a redundant or backup link to the network for port 2. Once port 2 detects that the link between itself and theswitch is good and that communication is healthy for five minutes, then switching back to port 2 is performed. Thedelay in switching back ensures that rebooted switching devices connected to the C60, which signal their ports asactive prior to being completely functional, have time to completely initialize themselves and become active. Onceport 2 is active again, port 3 returns to standby mode.If REDUNDANCY is set to PRP, the operation of ports 2 and 3 is as follows:• Ports 2 and 3 use the port 2 MAC address, IP address, and mask• The configuration fields for IP address and mask on port 3 are overwritten with those from port 2. This is visible on thefront panel but not displayed in the EnerVista software.• Port 2 MCST ADDRESS field is visible• The port 2 PTP function still uses only port 2 and the port 3 PTP function still uses only port 3. The relay stillsynchronizes to whichever port has the best master. When ports 2 and 3 see the same master, as is typically the casefor PRP networks, the port with the better connectivity is used.Behavior for GOOSE messages is as follows:• If REDUNDANCY is set to Failover or PRP, In order to transmit a GOOSE message on port 2, the CID file must beconfigured to have the corresponding GSE element in both ConnectedAPs S2 and S3. In the EnerVista software, theTxGOOSE PORT ASSIGNMENT needs to be "Ports-1,2,3" to transmit GOOSE on both ports 1 and 2, or "Ports-2,3" to haveGOOSE only on port 2, with failover/ PRP.• If REDUNDANCY is set to PRP, the port 2 configured GOOSE message is simultaneously transmitted on ports 2 and 3• If REDUNDANCY is set to failover and the port 2 link fails, then only the port 2 configured GOOSE message is transmittedon port 3For any changes to this setting to take effect, restart the unit.PRT2 PRP MCST ADDR — This setting allows the user to change the multicast address used by the PRP supervision frames.This setting is available if REDUNDANCY is set to PRP. All devices in the same PRP network need to have the same multicastaddress. Choose an address that does not conflict with another multicast protocol.5.3.5.5 Far-End Fault Indication (FEFI)Since 100BASE-FX does not support Auto-Negotiation, a Far-End Fault Indication (FEFI) feature is included since UR 7 thatallows for detection of link failures.The purpose of the Far-End Fault feature is to allow the stations on both ends of a pair of fibers to be informed when thereis a problem with one of the fibers. Without the Far-End Fault feature, it is impossible for a fiber interface to detect aproblem that affects only its transmit fiber.When the Far-End Fault feature is supported, a loss of receive signal (link) causes the transmitter to generate a Far-EndFault pattern in order to inform the device at the far end of the fiber pair that a fault has occurred.When the local receiver again detects a signal, the local transmitter automatically returns to normal operation.If a Far-End Fault pattern is received by a fiber interface that supports the Far-End Fault feature and it is enabled, it reactsby dropping the link as if there were no signal at all.The two ports must be connected to completely independent LANs with no single point of failure, such as commonpower supplies that feed switches on both LANs.