When i use postman

URL :

http://127.0.0.1:8181/restconf/operational/opendaylight-inventory:nodes/node/openflow:726054106310272/table/0/flow/#UF$TABLE*0-2

<table xmlns="urn:opendaylight:flow:inventory">
<id>0</id>
<aggregate-flow-statistics xmlns="urn:opendaylight:flow:statistics">
<packet-count>105</packet-count>
<flow-count>2</flow-count>
<byte-count>6300</byte-count>
</aggregate-flow-statistics>
<flow>
<id>#UF$TABLE*0-2</id>
<match>
<ethernet-match>
<ethernet-type>
<type>35020</type>
</ethernet-type>
</ethernet-match>
</match>
<table_id>0</table_id>
<priority>100</priority>
<cookie>3098476543630901248</cookie>
<idle-timeout>0</idle-timeout>
<instructions>
<instruction>
<order>0</order>
<apply-actions>
<action>
<order>0</order>
<output-action>
<output-node-connector>CONTROLLER</output-node-connector>
<max-length>65535</max-length>
</output-action>
</action>
</apply-actions>
</instruction>
</instructions>
<flow-statistics xmlns="urn:opendaylight:flow:statistics">
<packet-count>0</packet-count>
<duration>
<nanosecond>448000000</nanosecond>
<second>5161</second>
</duration>
<byte-count>0</byte-count>
</flow-statistics>
<hard-timeout>0</hard-timeout>
</flow>
<flow-hash-id-map>
<hash>Match [_ethernetMatch=EthernetMatch [_ethernetType=EthernetType [_type=EtherType [_value=35020], augmentation=[]], augmentation=[]], augmentation=[]]1003098476543630901248</hash>
<flow-id>#UF$TABLE*0-2</flow-id>
</flow-hash-id-map>
<flow-table-statistics xmlns="urn:opendaylight:flow:table:statistics">
<active-flows>2</active-flows>
<packets-matched>0</packets-matched>
<packets-looked-up>11853</packets-looked-up>
</flow-table-statistics>
</table>

 I found the flow id is

<id>#UF$TABLE*0-2</id>

 but it not exitst.

so, what is correctly flow-id to use.

Hi all,

I am working on a VAN module which depends on the OkHttp Java library. I have added the library as a dependency in the pom.xml file for my business logic project, and my project compiles just fine. However, when I try to deploy the application on VAN, I get the following error:

Server Error – 500: Internal Server Error
URL: rs/apps/com.netlab.webhooks/install
View ID: apps
Type: error

The only thing I can think is that VAN (running on an Ubuntu machine) does not have the OkHttp library installed. What is the best course of action here? Should I try to package the library with my project or install OkHttp on the Ubuntu machine? Regardless, how do I go about this?

Thanks!

The software-defined networking is changing the pace of data transition with infrastructure driven networking approach, more agile network management and affordable network hardware. However, there are still many who are unaware of fundamentals of SDN?

What is Software-defined networking?
SDN refers to a network infrastructure approach in which the networking control plane is decoupled from the hardware or physical topology. The Software defined approaching in the networking provides operators with a number of advantages. It has increased flexibility to the users along with improved performance and simplified operations.

The most important and key features of software defined networking include centralized control plane. This facilitates logical mapping of the network. It also provides features like slicing and virtualization of the network.
There are many approaches to SDN; however, the most significant is the arrival of switch firmware and white-box switches technology. This is the core of the solution accessible from Cumulus software network.

Cumulus Linux is based on the Debian distribution. Debain is similar to ordinary Linux box form the inside. For Example, For configuring an Ethernet interface, you you have to add an entry to the network interfaces file. This is how details are provided about that physical interface. After this, ifup and ifdown approach is used to control the network interface. If you know how to do standard routing, forwarding, bridging, and firewalling with Debian, then it is easier to configure Linux. The advanced routing protocol used by cumulus is Quagga, which is similar to OSPF and BGP protocols, Moreover, it offers, a Cisco-like interface.

So the bottom line is that, network admin who has Linux experience will be always be ahead of the network admin with No Linux experience. Later one, have to put in extra efforts to become accustomed with working of network device.

The entirely open framework of Cumulus Linux has made it possible to develop a custom command-line interface. Cumulus Download software can be used to manipulate various networking switches. Linux has simplified the networking complexities, now CLI could be as simple as a Python tool, or any other programming framework.
Understanding the Hardware Part of Cumulus Defined Networking Switches:

Configuration of switch is handled entirely within Linux. Therefore, the kernel itself is not directly involved in packet switching and routing. As a substitute, Cumulus has enabled a translation service called switched. This has helped to communicate between the network configurations. It has made the changes in Linux to the hardware Ethernet controllers.

Linux layer as a template for applied the hardware:
It runs as a daemon tool on the switch. The switched monitors the communication channels and configuration changes in any part of the network stack. This includes adding a port, configuring a firewall and most essentially adding the IP address. Whenever switchd network detects a change, it configures the Ethernet controllers to match. This is how, a cumulus Linux layer act as a template for applied networking hardware.

Similarly, the other data coming from the physical ports are communicated back up through the Linux layer. Thus, by Cumulus Download, the Linux interface acts as inspection commands. This is the essence of Cumulus Linux. From the operator's standpoint, it’s merely Linux.

Booting and configuration in Cumulus Linux
When you install a new switch the first task performed is to boot it with the operating system. The Cumulus utilizes the ONIE (Open Network Install Environment) software. Once the operating system is loaded, it starts running the initial boot automation trial. This script has the ability to perform any kind of configuration tasks. The configuration includes installing custom packages, data center clients for Puppet and adding local APT sources.

Bottom Line:
The brilliance of Cumulus Linux is in its simplicity as it is the standard Linux software. It makes use of commodity hardware switches. It can be scripted, adjusted, adapted, and customized according to the administrator’s requirements. The Cumulus Linux offers a combination of flexibility, compatibility, and ease of use that has redefined the traditional networking approach.

Hello, everyone

There is a question.

The Host ip config:

10.1.1.20

255.0.0.0

Gateway:10.1.1.2

and the architecture graph.



The host(10.1.1.20) will ping to switch(192.168.6.162) success.

and switch(192.168.6.162) also ping to controller(192.168.6.189) success.

but the host can't ping through switch.

10.1.1.20 straight to connect 192.168.6.189 is not working.

HP 2920 config is:

ip default-gateway 192.168.6.189
ip routing
snmp-server community "public" unrestricted
openflow
controller-id 1 ip 192.168.6.189 controller-interface vlan 2
instance "control"
listen-port
member vlan 1
controller-id 1
mode passive
enable
exit
enable
exit
oobm
ip address dhcp-bootp
vlan 1
name "DEFAULT_VLAN"
no untagged 3-14,17-24
untagged 1-2
tagged 15-16
ip address 10.1.1.2 255.255.255.0
vlan 2
name "VLAN 2"
untagged 3-24
ip address 192.168.6.162 255.255.255.0

Where is the problem?

Thank you all.

Can anyone help me with a flow definition containing a wildcarded ipv4 address in json. I thought it would be something like the following, but the HP VAN Controller (version 2.4.5.0614) returns:

{"error":"java.lang.IllegalArgumentException","message":"Bad address format: 192.168.0.0/16"}

----- flow.json ------

{

"flow": {

"priority": 30000,

"idle_timeout": 30,

"match": [

{"eth_type": "ipv4"},

{"ipv4_dst": "192.168.0.0/16"}

],

"instructions":[{

"apply_actions": [{"output": "NORMAL"}]}]

}}

Thanks!

Hi Team,

I have created a mininet network with virtual nodes.I am trying to connect a DSLAM as a phyical node in the network.

sudo mn --controller=remote,ip=10.177.175.30 --custom emptynet.py  --switch=ovsk,protocols=OpenFlow13

Please can anyone help me with connecting the phyical host ie which has an IP address of 10.177.174.110 (DSLAM) using the mininet.I need to acheive a network with both physical and virtual nodes to see their interaction.

Thanks,

Raghu

Hi everyone. I am trying to develop a traffic engineering simulation sdn app, but I'm having trouble to get the traffic to go to the hosts. 

Imagine this scenarium:

h0 <--> s0 <--> s1 <---> h1 

I'm pinging h1 on the h0 CLI and s0 gets the first packet, applies a rule and all next pings match the rule. When I check the HP Controller Inferface via Firefox, I can see through the flows interface of each switch that s0 and s1 are getting packets that match the flow entry. Still, h0 ins't pinging h1... There are images attached to show the problem.

NOTE: I'm using a custom topology on mininet and I specified that the port between a switch and a host is 500.

Hi everyone!

First i am sorry for my english, i am from Argentina.

We have a HP 2920 Switch and we use POX controller (forwarding.l2_learning module) with this arquitecture

Host1 (10.0.0.2) ----------Switch-------- Host2 (10.0.0.3)

when we put flow location for default (Software and hardware) the iperf test give us a 23 Mbps rate, it is very poor, we have the software rate limit in 2000 pps. We want use the hardware only flow location with a hardware rate limit of 1000000 kbps but when we put the controller with that the switch doesn't work, we cant ping between hosts and we haven't conection. we read the manual and found this:

NOTE: An error is returned to the controller if the flow cannot be added in hardware and the flow-location is set as hardware-only.

 NOTE: Flows with an action to forward to multiple ports or all ports of a VLAN, such as flood, cannot be hardware accelerated. Such flows are handled in software. Changing flow location to hardware-only affects those flows.
For example, if a flow is added with action such as FLOOD, it can only go in software. This causes in a performance penalty or the flow not being programmed at all if running in hardware-only mode.

can i use hardware-only with this switch? My POX controller is added actions with multiple ports forwarding? i have to change the controller for another? (ODL, Floodlight, Beacon)

the instance and the switch are configure fine because we can use with software and hardware flow location.

thanks you so much

Hello,

I am developing an application for the HP VAN 2.6 controller, the application works well but I am unable to log anything at all on the 'Support Logs' section of the controller GUI and makes it difficult to debug. Following the Developer Guide I can see that using a logger works almost out-of-the-box via slf4j, but again, I am unable to make this work. Here's part of the code that I am using (taken from the bl folder of my app):

public class ArpMirrorManager implements ArpMirrorService, SequencedPacketListener {

	/* Service dependencies */
	@Reference(policy = ReferencePolicy.DYNAMIC,
	cardinality = ReferenceCardinality.MANDATORY_UNARY)
	private volatile ControllerService controller;
	
	private static final Logger logger = LoggerFactory.getLogger(ArpMirrorManager.class);

Here are some places where I am trying to log information whenever an event ocurs:

	@Activate
	public void activate(){
		controller.addPacketListener(this, PacketListenerRole.DIRECTOR, DIR_ALTITUDE, INTEREST);
		logger.info("Module ARP Mirror activated");
	}

	
	@Deactivate
	public void deactivate(){
		controller.removePacketListener(this);
		logger.info("Module ARP Mirror deactivated");
	}

	
	@Override
	public void event(MessageContext context){
		logger.info("ARP MIRROR: Packet IN event");
                /* Some more code dealing with the PKT IN*/
                ....
         }

Am I missing something? Where can I access the logged messages?

Thanks,

Sergio

This is my topology:



There have another question.

When I connect a links between the switches.

To create the data plane.

but route problem extends.

In OVS I can set where the packet forward to specific ethernet card, How do i set the route table in hp 2920 switch?

That not like the OVS has specific ethernet interface.

and these three switches not in the same subnet.

I try to use mininet(miniedit) create a topology.

and type "s1 route -n" to observe the route table.

But it's to simple that is not fit reality.

Where i need to modify to realistic.

Finally, I need ping the three switches each other.

Hello everyone, i need your help,

As part of my internship, I just discovered the notion of OpenFlow and SDN. I understand some concepts about how OpenFlow works. And I want to know if the ideas I aqcuired are correct.

-SDN is a network, where we can use programmable devices, so we can deploy a dynamic network architecture.
-OpenFlow is a protocol that allows communication between an OpenFlow switch and an SDN controller.
-In SDN networks, all of the switches control plan will be housed in an external controller.
-In an SDN using OpenFlow, the switch keeps only the packet forwarding function on ports and following the actions defined by the controller.
- The controller set the packet switching policy, and connects the switch to execute the actions corresponding to the packet.

To test this, I have two HP-2920 switches that support OpenFlow 1.3. But i I have no HP SDN controller.
My questions:
-Can i operate a computer in such a way that it can play the role of an HP SDN controller? (the POX?)

-Did i have to  define OpenFlow VLAN (which will communicate traffic between OpenFlow switches and endpoint) and a non-openflow vlan used to communicate with the SDN controller ?
-Can you help me understand how can i test a controller  that set the Flow tables of a switch?

I know that i need to configure the switch somehow like this:

openflow
   controller-id 1 ip 192.168.56.7 controller-interface vlan 1
   egress-only-ports
   instance "test01"
      listen-port
      member vlan 10
      controller-id 1
      version 1.3
      enable
      exit
   enable
   exit

but i don't really understand how it gonna work with a SD HP controller.

Best Regards.

I have HP3800 switches configured as OpenLFow 1.3 SDN switches (firmware version KA.15.15.0006).

In OpenFlow SDN mode, If the switches reveive mutlicast packets, they broadcast the packets as per a traditional switch, without the SDN controller adding any rules in the flow tables.

If I direct the mutlciast stream to mulitple ports on the same switch (using flow rules) then remove a port, packets are broadcast on other ports for approx 0.1ms, even when there is a lower priority drop packet flow rule.

In SDN OpenFlow mode, this shoudl not happen.

Has this been seen before? Has it been fixed in newer firmware versions?

Hi guys,

Pls help me to find the answer for below,

Which openflow use case is an example of NFV in hp?

options are 1.Use openflow to implement traffic prioritazation on the edge

                    2.Use openflow to implement a router on an open-vswitch

                    3.Use openflow to deploy configurations using IMC VAN sdn manager

                    4.Use openflow to replace the need of an snmp-agent on the switch.

Hi Friends,

What is the best prctice to configure VAN SDN Controller, to configure in a fastest failover from one controller to another.

Pls help me to get this.

Hi, I'd like to know how to create a Multipart Request message of type Aggregate (OF 1.3 spec page 64). In particular, I want to aggregate the statistics of flows that match on cookie and a cookie mask. I can see a lot of classes implementing the interface MultipartBody but none of them is for the type Aggregate ( representing "ofp_aggregate_stats_request" in the spec). 

The closest one is MbodyMutableFlowStatsRequest, but after the OF message is sent, the response will include an array multiple flows rather than the aggregated counters with no array. 

I'd like to know whether that's a design decision for HP VAN and I should do the aggregation manually in my module's Manager, or I am missing something to create these type of requests. 

Thank you!

Code I am using:

		MBodyMutableFlowStatsRequest flow_stats = new MBodyMutableFlowStatsRequest(PV);
		flow_stats.cookie(cookie)
			.cookieMask(cookieMask)
			.match((Match) MatchFactory.createMatch(PV).toImmutable());

		OfmMutableMultipartRequest req = 
    		(OfmMutableMultipartRequest) MessageFactory.create(PV, MessageType.MULTIPART_REQUEST);

                //And one of the following lines
		req.body((MultipartBody) flow_stats.toImmutable()); // Get an array back when cs.send
                req.type(MultipartType.AGGREGATE);   // Eaises IllegalArg Exception "expected body(...) : AGGREGATE"
                ...
		MessageFuture future = cs.send(req.toImmutable(), dp);
		future.await(); // Blocks
		if (future.result().isSuccess()){
                      ....

We are trying to add a flow that outputs to controller and to a physical port  but we are getting a BAD_ACTION/BAD_TYPE error back from the switch (3800 - Sw:KA.16.02.0012) regardless of the order in which we specify the actions. Here's part of the OF trace:

Time: 11:08:02.636
Event: Tx

{ofm:[V_1_3,FLOW_MOD,136,2292534],cmd=ADD,match={Match(V_1_3):[type=OXM,len=45],fields=ETH_TYPE,IP_PROTO,IPV4_SRC,IPV4_DST,TCP_DST},...}
  Cookie   : 0xab01400000000001
  C Mask   : 0x0
  Table ID : 100
  FMod Cmd : ADD
  Idle t/o : 0s
  Hard t/o : 120s
  Priority : 10064
  Buffer ID: 0xffffffff(NO_BUFFER)
  Out Port : 0xffffffff(ANY)
  Out Group: 0xffffffff(ANY)
  FMod Flgs: [sendFlowRem]
  Match    : {Match(V_1_3):[type=OXM,len=45],fields=ETH_TYPE,IP_PROTO,IPV4_SRC,IPV4_DST,TCP_DST}
    {Oxm:V_1_3:[cls=0x8000(OPENFLOW_BASIC),ft=5(ETH_TYPE),hm=false,len=2],type=0x0800(IPv4)}
    {Oxm:V_1_3:[cls=0x8000(OPENFLOW_BASIC),ft=10(IP_PROTO),hm=false,len=1],ipp=6(TCP)}
    {Oxm:V_1_3:[cls=0x8000(OPENFLOW_BASIC),ft=11(IPV4_SRC),hm=true,len=8],ip=172.23.7.162,mask=255.255.255.255}
    {Oxm:V_1_3:[cls=0x8000(OPENFLOW_BASIC),ft=12(IPV4_DST),hm=true,len=8],ip=172.23.7.170,mask=255.255.255.255}
    {Oxm:V_1_3:[cls=0x8000(OPENFLOW_BASIC),ft=14(TCP_DST),hm=false,len=2],port=0x16(22)}
  Instructions:
    {Instr:V_1_3:[type=APPLY_ACTIONS,len=40],actList=OUTPUT,OUTPUT}
      {Act:[OUTPUT,len=16],port=0x6(6),maxLen=0}
      {Act:[OUTPUT,len=16],port=0xfffffffd(CONTROLLER),maxLen=65535(NO_BUFFER)}

Time: 11:08:02.638
Event: Rx
Data Path ID: 00:02:10:60:4b:b6:46:80
Message: {ofm:[V_1_3,ERROR,76,2292534],BAD_ACTION/BAD_TYPE,#dataBytes=64,OFM-cause:[V_1_3,FLOW_MOD,136,2292534]}

{ofm:[V_1_3,ERROR,76,2292534],BAD_ACTION/BAD_TYPE,#dataBytes=64,OFM-cause:[V_1_3,FLOW_MOD,136,2292534]}
  data = 040e00880022fb36ab0140000000000100000000000000006400000000782750ffffffffffffffffffffffff000100000001002d80000a020800800014010680

However, if we output to two physical ports the rule is successfully installed.

Through testing, I have found that LLDP packets traverse links between two HP devices untagged. This has raised some questions, so let me present a scenario. Consider two switches A and B connected by a link (say between port 1 on both switches). Let A port 1 and B port 1 be both configured as follows: tagged VLAN 2, no untagged VLANs. LLDP packets will traverse the link and be processed by both switches. However, being that LLDP packets are sent untagged, how are they processed? Is a packet automatically associated with some special VLAN if it arrives untagged on a port with no native VLAN? The relation here to OpenFlow is that if I want to send LLDP packets to the controller, it seems that I cannot. Even an aggregate OpenFlow instance will not receive these tagless packets. What is going on here?

Thanks!

This is going to be a bit of an overloaded question, so please bear with me.

There is a table listed at http://h22208.www2.hpe.com/eginfolib/networking/docs/switches/K-KA-KB/15-18/5998_8148_sww_admin_guide/content/ch05s03.html#v32701554 which is prefixed by "HP switches running OpenFlow do not support Push and Pop VLANs." However, the table seems to indicate that there is some level of support for popping VLANs. For the first part of my question, could someone please explain the details regarding the support of these operations on HP switches? Is there or is there not support, and is it based on module version, switch version, firmware version, VAN version, etc.?

Second, I am very confused about how the standard pipeline processes packets with or without VLAN tags and when OpenFlow takes over. Through testing, I have observed many confusing results including:

1. Popping a VLAN before outputting on a port resulting in the packet being dropped.

2. A packet arrives on an untagged port. I set the VLAN ID (what VLAN ID? it shouldn't have one. is there internal tagging?). I output the (now somehow tagged) packet on another untagged port. It successfully travels across the wire and arrives on the other side. Though the other side is configured as an access port, the tag containing the same VLAN as the native/untagged VLAN of the access port is automatically popped from the packet.

Could someone please explain, in as much detail as possible, the details of the OpenFlow pipeline with respect to VLANs. I will likely have follow up questions, as this has caused numurous problems and confusion for me.

Thanks for your time!

All,

We are running into issues with VAN's OfIpDiscoveryComponent. Consider the following (real) scenario.

We have two hosts: h1 and h2 connected in the following topology: h1 --- s1 --- s2 --- s3 --- r1 --- s4 --- h2. The devices s1, s2, s3, s4, and r1 are all HP switches running OpenFlow. Additionally, r1 has routing enabled. On the link from r1 to s3, r1 is configured with IP address 172.23.7.161/29 and on the link from r1 to s4, r1 is configured with IP address 172.23.7.169/29. Furtheremore, h1 has IP address 172.23.7.162 and h2 has IP address 172.23.7.170.

Test 1: OfIpDiscoveryComponent Enabled (Default)

Initially, VAN doesn't know about h1 and h2 (it hasn't discovered them).

We install rules (both forward and reverse: for the reverse rules, flip the ip's and change tcp_dst to tcp_src) in all the switches matching the following flow:
ip_src=172.23.7.162
ip_dst = 172.23.7.170
tcp_dst = 5001

Additionally, at r1, we rewrite the source MAC address to r1's MAC address on the port with link connected to s4, and we rewrite the destination MAC address to h2's MAC address.

After these rules are installed, we launch iperf server on h2 and run iperf client on h1. The iperf TCP SYN packets make it to r1 *and* they match the rule which rewrite's the MAC addresses and outputs on the correct port. However, we used mirroring on the physical switch r1 and found that no TCP sync packets were leaving the port. Thus, it seems like the switch is ignoring the fact that we are commanding it to output on the port. Is it taking something else into consideration to make this decision? Why?

We did notice that r1 does not discover h2 since h2 doesn't send any traffic. However, we would expect this to not matter at the OpenFlow level. Ideally, OpenFlow should do whatever we tell it to do, regardless of what the controller knows about hosts.

Test 2: OfIpDiscoveryComponent Disabled

Consider the exact same setup as Test 1, but with OfIpDiscoveryComponent Disabled (property set to false in the Web interface). We restart the controller to have a clean starting slate where the hosts were once again not known to the controller. We installed the same rules as before, and we ran iperf again. However, this time r1 went ahead and obeyed our request even though it had yet to learn about h2.

What in the world is going on here? What is this mythical OfIpDiscoveryComponent and what effects does it have on OpenFlow processing?

Thanks for your time.

UPDATE

Somehow, our Test 1 magically started working after a while. This baffled us greatly, so we had the idea that maybe the physical switches are keeping some state that affects this OpenFlow processing somehow. To test this theory, we physically rebooted all of our switches as well as the OpenFlow controller. Upon the controller and switches returning to working capacity, we tried Test 1 again, and it failed again.

Now we are really confused. What is going on here? Why do the physical switches affect OpenFlow policies like this? Presumably, we are just modifying the existing incoming L2 frame. Are we wrong about this? Is the L2 frame being removed and eventually re-encapsulated outside of the OpenFlow pipeline?

Thanks!

Hi,

I am using an HP 2920-24G/ J9726A switch. I upgraded the firmware to  WB.16.02.0012. I created an aggregate instance with version 1.3 and was successfully connected to a floodlight controller. However, I am unable to create a new flow entry although I set the table id to 100 (As I read in many other discussions).

I get the following error:

 OFFlowModFailedErrorMsgVer13(xid=307, code=EPERM, data=OFFlowModifyStrictVer13(xid=307, cookie=0x00a000004039d1a6, cookieMask=0x0000000000000000, tableId=0x64, idleTimeout=0, hardTimeout=0, priority=32768, bufferId=4294967295, outPort=any, outGroup=any, flags=[SEND_FLOW_REM], match=OFMatchV3Ver13(in_port=1), instructions=[])) from switch OFSwitch DPID[00:02:48:0f:cf:0c:b1:c0] in state net.floodlightcontroller.core.internal.OFSwitchHandshakeHandler$MasterState@5f0decc3

If I set the out-port to a vaild working port in the switch, I get the following error:

OFBadActionErrorMsgVer13(xid=366, code=BAD_OUT_PORT, data=[unparsed: 04 0e 00 58 00 00 01 6e 00 a0 00 00 40 39 d1 a6 00 00 00 00 00 00 00 00 64 02 00 00 00 00 80 00 ff ff ff ff ff ff ff ff ff ff ff ff 00 01 00 00 00 01 00 0c 80 00 00 04 00 00 00 01 00 00 00 00]) from switch OFSwitch DPID[00:02:48:0f:cf:0c:b1:c0] in state net.floodlightcontroller.core.internal.OFSwitchHandshakeHandler$MasterState@5f0decc3

An of course if I use the defualt table 0, I get the following error:

OFBadMatchErrorMsgVer13(xid=458, code=BAD_TYPE, data=[unparsed: 04 0e 00 58 00 00 01 ca 00 a0 00 00 40 39 d1 a6 00 00 00 00 00 00 00 00 00 02 00 00 00 00 80 00 ff ff ff ff ff ff ff ff ff ff ff ff 00 01 00 00 00 01 00 0c 80 00 00 04 00 00 00 01 00 00 00 00]) from switch OFSwitch DPID[00:02:48:0f:cf:0c:b1:c0] in state net.floodlightcontroller.core.internal.OFSwitchHandshakeHandler$MasterState@5f0decc3

Any suggestions ?

Thanks,

Enas