T1000 Switch is designed to provide your IEC 61850 network with flexibility, reliability, robustness in the interconnection of IEDs and precision in synchronization with the new IEEE 1588 v2 standard. The modular design of T1000 allows up to 6 sets of 2 interfaces operating simultaneously to support Ethernet over copper communication of 10, 100 and 1000 Mbps and fiber optic links of 100 and 1000 Mbps.
- Modular design
- Modules field replaceable
- Redundant power supplies
- IEEE 1588v2 support on all interfaces
- PRP support (IEC 62439-3)
- Extended operating temperature range -40…+85°C
- Fail safe indicator (Dry contacts)
- Automatic detection and control for rings using STP, RSTP and MSTP
- Why the power LEDs are off?
Power LEDs off means power supply is missing. Check if power cables are correctly connected to the corresponding screws, check if power plug is correctly inserted or check if power supply is enabled at the system, verifying voltage at the power supply connectors.
- There is none connection at T1000 switch, but why LINK LED at the port 1 remains on?
T1000 switch does not have a power LED, as other switches. To allow informing that the equipment is operating when equipment do not have any Ethernet connection, the LINK LED of port one remains in on state, at orange color. Thus, this LED indicates that switch is powered up and operation system is running properly.
- What is switch’s management IP address
If IP address of the management interface was lost, there are some actions that could be done to recover it.
Major actions are shown below:
- Maintaining switch’s configuration: connect the terminal to the USB interface of the switch. After communication is established, the command to recover IP address is:
show ip interface brief
- Losing switch’s configuration: While the switch is turned off, connect ports 1 and 2 to create a loop between then. After this, power-up the This procedure will restore configuration to the factory default configuration, and then IP address of the equipment will be 192.168.4.88, and mask length will be 255.255.255.0
- Why does the Web interface cannot be accessed
If the terminal that is intended to be accessed cannot be reached even when IP is known, there are some steps to be performed to check if terminal is able to connect to the equipment.
- Check if cables connecting terminal and switch are properly operating. In addition, if possible, check if LEDs corresponding to the port used by terminal are blinking, showing that communication is being performed at the port.
- Be sure that terminal is at the same IP subnetwork of switch’s interface. Check it by inspecting switch’s management interface mask length and IP address and terminal mask length and IP address. Bits enabled related to mask length compared to IP address should be equal from both terminal and management interface, which means equipment in the same IP network.
- Be sure that port where terminal is connected is at the VLAN of the management interface. If there is no VLAN configured, be sure that VLAN of the management interface configured is the default VLAN (VID = 1).
- Try a PING command from terminal to the switch’s management If switch responds to PING messages but web interface is not able to open management interface, be sure that web browser’s proxy usage is properly configured to permit switch’s management interface.
- What do I do if the electrical link is not operating properly?
If electrical links are not operating properly, there are two options to be verified:
- Link is operating, but packets are being lost randomly. In this case, possible cause of the problem is a pair of the UTP cable broken. It can be verified by VeriPHY function, which will display the pair broken, or exchanging Ethernet cable. It can be also tested by changing the port’s speed, as 100 Mbps ports use 2 pairs while 1 Gbps uses 4 pairs of the cable, for instance. Thus, lowering port speed could give a feedback about cable quality. Besides, this problem should be solved after the UTP cable is exchanged by a good quality UTP cable.
- Link is not operating. In this case, possible cause of the problem is that cable is broken, RJ45 connector is broken or port is disabled. If port is disabled, enable it at the web interface. To enable ports, go to the Ports menu, choose port to be enabled and then select correct port speed. If cable or connector is broken, this problem should be solved after the UTP cable is exchanged by a good quality UTP cable.
- I do not need VLANs. Do I have to change default settings?
By default, all ports are member of the VLAN ID 1 in Reason Switches. Management interface is configured to be member of the VLAN ID 1, all ingress frames are classified to the VLAN ID 1 and all egress frames are forwarded without VLAN tag. Thus, all equipment connected will be member of the same VLAN, and will receive and transmit information as they are in the same LAN. Thus, if there is no VLAN usage on the network, default settings would not require to be changed.
- I use VLANs, why don’t they appear to be working?
When using VLANs, there are several topics that must be clarified by user while configuring the switches. Be sure that the following topics are respected if VLAN is not working properly.
- Port type must be correct. Be sure that equipment connected to the port where VLAN is being configured is correct. If not, the ingress filter should drop packets or change incoming VLAN ID frames to the VLAN ID of the ingress port, thus a given VID frame will be redirected to port VID VLAN.
- Port Filtering is being respected. If ingress filtering is enabled, untagged or tagged frames could be dropped, depending on the filter configured. Be sure that ingress filtering is correct for that port.
- Egress tagging parameters work as host Egress filtering can maintain VLAN tag, cut-off VLAN tag or cut-off only frames with the port VID tag. Thus, be sure that egress tagging is configured as the host needs. If host supports VLANs, be sure that egress filtering is sending VLAN tag the host is expecting to receive. If host does not supports VLANs, be sure that frames are being forwarded without VLAN tag.
- Be sure that VLAN is allowed in the port, and be sure that VLAN is not forbidden on that port. Frames with VLAN information can only be forwarded if they ingress at a port that is allowed to receive frame’s VLAN. If not, packet will be dropped. In addition, frames with VLAN ID forbidden for a given port will also be dropped.
- What do I do if Date or time are wrong?
Reason Switches internal clocks are updated based on a NTP server. If date or time is wrong, follow the steps below:
- Be sure that there is an NTP server configured at the switch. It can be verified at the Settings à System à NTP menu.
- Be sure that NTP server of the network is reachable. It can be tested by switch’s internal PING command, where it must be commanded a PING to configured NTP server.
- Check if Timezone is configured properly, at Settings à System à Time menu. If Daylight Saving Time is used, check if it is properly configured.
- How to update a Firmware?
When firmware update is required, the first step to be done is requiring Alstom for the firmware file. After this file is received, copy the file to the PC on which management interface of the switch is performed. Updating firmware menu is located at the Maintenance menu. To update firmware, go to the Maintenance àSoftware à Upload menu, select correct firmware file (.dat file) and then click at the Upload button.
- How can I guarantee that configuration file will not be lost if I reboot the switch?
When doing configuration changes, the first step is to guarantee that new settings are working properly. After changing and saving configuration, be sure that the configuration saved (the running configuration) is working properly, testing the Ethernet network. After guaranteed that running configuration is working, save it at the startup config, located in Maintenance à Configuration à Save startup-config. After running configuration is saved at the startup configuration, it is guaranteed that configuration will not be lost in a reboot process.
Be sure that there is no loop between ports 1 and 2 when rebooting the switch if restore the factory configurations in not required.