GE MDS ORBIT MCR, Technical Manual, Page: 150 / 463

150 MDS Orbit MCR/ECR Technical Manual MDS 05-6632A01, Rev. F
NETCONF-notifications
The events generated by the unit are converted to NETCONF notifications. NETCONF clients can
subscribe to the unit to receive those notifications.
Syslog Server Setup
The events generated by the unit can be sent to remote syslog servers. The connection to the syslog server
can be made secure using syslog over TLS.
For example:

Name - User supplied unique name to identify this server configuration

IP - The hostname or IPv4 address of the syslog server.

Port - The port to connect to. DEFAULT =514

Version - The syslog protocol version to use. RFC3164 (DEFAULT) or RFC5424

Protocol - The transport protocol used to send syslog messages to this server. Choices: tcp,
udp, tls, tcp6, udp6, tls6

Message Format
– Choose either json_cee or text <insert more info here>
If the TLS protocol is selected the following fields may be filled in:

TLS CA Certificate - The name of the certificate of the CA server that was used to sign the
certificate that the syslog server will be using.

TLS Client Certificate - The client certificate to use when communicating to the syslog
server over TLS.

TLS Client Key - The name of the private key
To set up a syslog server, use the command:
% set logging syslog server my_server ip 192.168.1.200
Alarms
Events can be configured by Event Rules to be Alarms which can causes the Power Light and external
signal to go “high” state. Refer to Section 2.5 for further details.
Alarms have factory default settings that control the behavior of the alarm outputs timing in terms of
period and duration. These values can be overridden to adjust for local requirements.