Deployment Guide

54
If you can read the switch node ID from the controller then you have established communications with the
controller and can begin programming it for flows. For a continued example of setting up a simple end to end
traffic L2 bridging flow, see Appendix B.
5.6 Logging
Due to the requirement not to impact any of the existing N series firmware, the DNOS-OF switch maintains
only a minimal set of in-memory trace logs that are accessible by engineering and support for internal program
debugging. All other user configurable logging is intended to use a remote syslog server or, if
necessary/desired, the serial console. Later releases of the firmware may add local logging.
The logging system allows for use of the component and verbosity as well as whether it is enabled or disabled,
to be controller. It also allows specification of the IP address and port for the syslog service to use for external
logging, the parameters needed to set the logging to that service and whether it is enabled or disabled.
The logging levels and components are configurable for either the runtime or stored configured values used by
the system. The set logging level/component commands are runtime only and do not affect the stored
logging settings in the running-config. The set default logging level/component commands are used to store
a given logging level or component to the running-config.
The default persistent logging values from the switch configuration are shown below:
"Default Logging":
{
"components":
{
"API": true,
"Mapping": true,
"OFDB": true,
"datapath": true
},
"level": 1
},
"Remote Syslog":
{
"enabled": false,
"ip address": "",
"ip port": 514
},