Hello

I am at the begining of implementing Openflow network...

I configured the following devices:

1- HP Switch which has Openflow version 2.02w
2-Ubuntu 12.04 which has latest version of NOX controller
===================
Here is the Openflow information in HP:

***********************************
HP-Wwitch# show openflow 10

 Openflow Configuration - VLAN 10

  Openflow state [Disabled] : Enabled
  Controller pseudo-URL : tcp:192.168.2.2:6633
  Listener pseudo-URL : ptcp:6633
  Openflow software rate limit [100] : 100
  Openflow connecting max backoff [60] : 60
  Openflow hardware acceleration [Enabled] : Enabled
  Openflow hardware rate limit [0] : 0
  Openflow hardware stats max refresh rate [0] : 0
  Openflow fail-secure [Disabled] : Disabled
  Second Controller pseudo-URL :
  Third Controller pseudo-URL :

 Openflow Status - VLAN 10

  Switch MAC address : 
  Openflow datapath ID : 
  Controller connection status (1/1) : disconnected ; state: BACKOFF
    Last error: Connection refused ; timeout: 59/60 ; duration: 139094
    Failed standalone; duration: 138913
  Listening connection status : listening (1 connections)
  SW Dpif n_flows: 0 ; cur_capacity:1 ; n_lost: 0
          n_hit: 0 ; n_missed: 0 ; n_frags: 0
  Number of hardware rules: 0


***********************************
it seems that I get this error before starting NOX controller:

Last error: Connection refused
=======================================
Here is the VLAN information:
vlan 10
   name "openflow"
   tagged A1
   no ip address
   exit


openflow
   vlan 10
      enable
      controller "tcp:192.168.2.2:6633" listener "ptcp:6633"
      exit
==========================================
Here is the Show openflow command in the switch:

HP-Switch# show open

 Openflow Configuration

  Openflow aggregate VLANs [Disabled] :
  Openflow aggregate management VlanId [0] : 0
  Openflow second aggregate management VlanId [0] : 0
  Openflow aggregate configuration VlanId [0] : 0

  VID  State HW  Active controller Pseudo-URL                       Conn
  ---- ----- --- -------------------------------------------------- ----
  35   On    On  tcp:192.168.2.2:6633                                    No

=============================================

After starting the NOX controller as follow:

nox@NOX:~$ cd nox
nox@NOX:~/nox$ cd build
nox@NOX:~/nox/build$ cd src
nox@NOX:~/nox/build/src$ ./nox_cor -i ptcp:6633
-bash: ./nox_cor: No such file or directory
nox@NOX:~/nox/build/src$ ./nox_core -i ptcp:6633
NOX 0.9.2~core~beta (nox_core), compiled Jul 11 2012 17:37:52
00001|connection_manager|WARN:connected: 
10.75.116.143:6633<->10.75.116.129:50520


=========================

And going back to the openflow switch and issuing the command :
show openflow 10

I got the following:

HP-Switch# show openflow 10

 Openflow Configuration - VLAN 10

  Openflow state [Disabled] : Enabled
  Controller pseudo-URL : tcp:192.168.2.2:6633
  Listener pseudo-URL : ptcp:6633
  Openflow software rate limit [100] : 100
  Openflow connecting max backoff [60] : 60
  Openflow hardware acceleration [Enabled] : Enabled
  Openflow hardware rate limit [0] : 0
  Openflow hardware stats max refresh rate [0] : 0
  Openflow fail-secure [Disabled] : Disabled
  Second Controller pseudo-URL :
  Third Controller pseudo-URL :

 Openflow Status - VLAN 10

  Switch MAC address : 
  Openflow datapath ID : 
  Controller connection status (1/1) : disconnected ; state: BACKOFF
    Last error: Connection reset by peer ; timeout: 51/60 ; duration: 140063
    Failed standalone; duration: 139874
  Listening connection status : listening (1 connections)
  SW Dpif n_flows: 0 ; cur_capacity:1 ; n_lost: 0
          n_hit: 0 ; n_missed: 0 ; n_frags: 0
  Number of hardware rules: 0

===========================
I got Connection reset by peer problem.

My Questions are:

1. Why I am getting Connection reset by peer error, where everything seems to 
be fine?
2. To view the flow table of the switch, we need dpctl utility...How to use 
this utility ?
3.How do I test my NOX controller ?


Al Araimi

MSc Student
Data Communications Systems

Reply via email to