Events that change the Operational Status of the OpenFlow instance
The
Oper. Status
field indicates the operational status of the instance and can be either up or down. The operational status is down when either the member VLAN of the OpenFlow instance does not exist on the switch or the controller VLAN of the OpenFlow instance does not exist on the switch. In the case when multiple controllers connect over multiple controller VLANs, the operational status is down when none of the controller VLANs exist on the switch. When the member VLAN is down - all ports on the member VLAN are down.
For example, the
show openflow instance
<instance-name>
displays all the OpenFlow instance-related information as follows:
NOTE:
For purposes of this example, the instance <test> has been created.
switch(openflow)# show openflow instance test Configured OF Version : 1.3 only Negotiated OF Version : 1.3 Instance Name : test Data-path Description : test Administrator Status : Enabled Member List : VLAN 3 Pipeline Model : Standard Match Listen Port : 6633 Operational Status : Down Operational Status Reason : None of the member VLANs are configured Datapath ID : 0000000000000000 Mode : Active Flow Location : Hardware and Software No. of Hardware Flows : 0 No. of Software Flows : 0 Hardware Rate Limit : 0 kbps Software Rate Limit : 100 pps Conn. Interrupt Mode : Fail-Secure Maximum Backoff Interval : 60 seconds Probe Interval : 10 seconds Hardware Table Miss Count : NA No. of Software Flow Tables : 1 Egress Only Ports : None Table Model : Policy Engine and Software Source MAC Group Table : Disabled Destination MAC Group Table : Disabled Controller Id Connection Status Connection State Secure Role ------------- ----------------- ---------------- ------ ------ 1 Disconnected Void No Equal