Security-defined interoperability will deliver routes that leverage the existing infrastructure and optimize
traffic
Packet-based routing will be providing a better accounting of all traffic in the network through better audit
log information for the auditors
SDN will deliver better isolation of data plane traffic and will provide more flexibility to address
redundancy needs
The ability to separate control plane from the data plane automatically makes data management easier and
more secure
SDN will deliver better isolation of data plane traffic and will provide more flexibility to address
redundancy needs
Reactively program a flow in the controller to redirect traffic toward the region at 1 am
Proactively program a flow in the controller to redirect traffic away from the region at 1 am
Proactively program a flow in the SDN Switches to redirect traffic away from the region at 1 am
Reactively program a flow in the SDN Switches to redirect traffic toward the region at 1 am
Proactively program a flow in the controller to redirect traffic away from the region at 1 am
The policy/intent interface of the SDN Controller
The user interface of the OpenFlow instance
The command line interface (CLI) of the VPN gateways
The SNMP interface of the optical network EMS
The policy/intent interface of the SDN Controller
Control plane in the SDN Switch
Control plane in the SDN Controller
Forwarding plane in the SDN Controller
Forwarding plane in the SDN Switch
Control plane in the SDN Controller
Eastbound/Westbound interface
Infrastructure layer interface
Application layer interface
Northbound/Southbound interface
Eastbound/Westbound interface
The SDN Switches east/west interfaces
The SDN Controller northbound interface
The SDN Controller OpenFlow interface
The SDN Switches southbound interface
The SDN Controller northbound interface
Deploy a separate network for OpenFlow protocol traffic
Find a network edge use case that would allow an interoperable OpenFlow solution to be deployed for
deep packet inspection
Find a hybrid networking solution by deploying custom APIs to manage switch traffic from the nonOpenFlow switches
Deploy an overlay SDN solution like VxLAN.
Deploy a separate network for OpenFlow protocol traffic
YANG
OpenFlow
OF-Config
NETCONF
NETCONF
Ansible and NETCONF
NFV and OpenFlow
OpenFlow and SNMP
OpenFlow and YANG
OpenFlow and SNMP
Whether the application should be data center-based or a cloud-based SDN solution
The nature of the SDN/Virtualization application and infrastructure
The ability for OpenFlow 1.3 to support IPv6 and multicast traffic
The interoperability of the legacy and the OpenFlow 1.3 compatible switches
The interoperability of the legacy and the OpenFlow 1.3 compatible switches
Upgrade the SDN Controller to the latest software version
Upgrade the network switch to the latest firmware and OpenFlow protocol version
Identify the issue through the analytics component and follow a more specific troubleshooting process
Move the SDN Controller on a new server in a new location
Upgrade the network switch to the latest firmware and OpenFlow protocol version
If VLAN ID = 20, forward to ANY port
If VLAN ID = 20, forward to CONTROLLER port
If VLAN ID = 20, forward to IN_PORT port
If VLAN ID = 20, forward to NORMAL port
If VLAN ID = 20, forward to NORMAL port
Minimum rate = 3 Gbps; Maximum rate = 3 Gbps
Minimum rate = 7 Gbps; Maximum rate = 7 Gbps
Minimum rate = 3 Gbps; Maximum rate = 10 Gbps
Minimum rate = 7 Gbps; Maximum rate = 10 Gbps
Minimum rate = 7 Gbps; Maximum rate = 7 Gbps
Meter 1: rate = 1 Mbps, type = DSCP remark; Meter 2: rate = 2 Mbps, type = drop
Meter 1: rate = 1 Mbps, type = drop; Meter 2: rate = 2 Mbps, type = drop
Meter 1: rate = 1 Mbps, type = DSCP remark; Meter 2: rate = 1.5 Mbps, type = DSCP remark
Meter 1: rate = 1 Mbps, type = drop; Meter 2: rate = 2 Mbps, type = DSCP remark
Meter 1: rate = 1 Mbps, type = DSCP remark; Meter 2: rate = 2 Mbps, type = drop
UDP Connection
Hello Messages
TLS Sequencing
Echo Request/Reply
Echo Request/Reply
The SDN control connection is established in-band and isolated from the data traffic
The SDN switch at the remote location is equipped with a battery backup unit
The SDN control connection uses an unreliable transport protocol (such as UDP)
The SDN control connections are established to both master and slave SDN controller
The SDN control connection is established in-band and isolated from the data traffic
The connection URl configured in both OF switches is TLS:192.168.1.100:6653
The connection URl configured in the first OF switch is TCP:192.168.1.1:6653
The connection URl configured in both OF switches is TLS:192.168.1.1:6653
The connection URl configured in both OF switches is TCP:192.168.1.100:6653
The connection URl configured in both OF switches is TLS:192.168.1.100:6653
Fail normal mode
Fail secure mode
Fail switch mode
Fail secure drop mode
Fail secure mode
Fail secure mode
Fail standalone mode
Fail normal mode
Fail secure drop mode
Fail standalone mode
The SDN Switches will drop all traffic received through the active physical ports
The SDN Switches will only forward new flows through the active physical ports
The SDN Switches will forward all traffic through the active physical ports
The SDN Switches will forward already configured flows through the active physical ports
The SDN Switches will forward already configured flows through the active physical ports
VXLAN
IPv6
IPSEC
MPLS
VXLAN
Broadcast the traffic to all SDN Switches in the affected areas
Dispatch a technician to the unaffected area
Redirect the traffic away from the affected areas
Configure more ports on the SDN Switches in the affected areas
Redirect the traffic away from the affected areas
OpenStack
OpenDaylight
Open Source Networking
Open Software Defined System
OpenDaylight
Roll back to the Beacon SDN Controller
Implement high availability functionality for all network elements
Fix the APIs for each of the applications on the network
Replace Ryu with two OpenDaylight controllers in active/active mode
Replace Ryu with two OpenDaylight controllers in active/active mode