General information about the Impact on an IT network, when Sigma utilizes it.
1 - Sigma is very IT-friendly and complies with the following IETF (Internet Engineering Task Force) standards:
- RFC 791: Internet Protocol (IP)
- RFC 972: Internet Control Message Protocol (ICMP)
- RFC 826: Address Resolution Protocol (ARP)
- RFC 950: Subnet Mask
- RFC 1256: Router Discovery
- RFC 768: User Datagram Protocol (UDP)
- RFC 1058: Routing Information Protocol (RIP)
2 - Sigma will utilize 1 - 2% of a 100M Ethernet connection.
3 - The Sigma system use peer to peer communications, therefore communications between devices will only occur when required by the system or user.
4 - Devices can operate as stand alone for long periods, in the event of network problems.
5 - Controllers can be restricted on how often global data is passed to other controllers.
6 - Sigma Remote Clients will poll the Sigma Server to ensure the connection is still there.
7 - Messages between the server and the controllers / DNN's / IC's all use UDP (User defined protocol) messages, their sizes will vary dependent on the message.
8 - Client to Server messages are TCP Transmission control protocol), and again the message size varies.
9 - Sigma uses ports 49152, 3614, 80 and 8080.
10 - Sigma V53 devices communicate at 10M half Duplex.
11 - Sigma ARM devices negotiate a communications speed, starting at 100M half Duplex, then moving to 10M full Duplex, and finally 10M half Duplex.