Changing color so that you can identify inline text.

 

Regards,

Sheili

 

From: Sheili Mittal 
Sent: 16 January 2012 15:03
To: 'Murphy McCauley'
Cc: nox-dev@noxrepo.org
Subject: RE: [nox-dev] need support for these features in NOX

 

Hi Murphy,

 

I am using Python APIs.

Please see inline.

 

Regards,

Sheili 

 

From: Murphy McCauley [mailto:jam...@nau.edu] 
Sent: 16 January 2012 14:28
To: Sheili Mittal
Cc: nox-dev@noxrepo.org
Subject: Re: [nox-dev] need support for these features in NOX

 

The enqueue action is supported in destiny.

Is the dentiny branch safe to test all openflow 1.0 functionalities? , I
saw its unstable.

 

Flow stats are possible (there has been some recent discussion about it
on the list, I believe).

I will search for that.

 

I'm not sure what you mean by queue statistics.

According to openflow 1.0 spec , we can add any packet to a queue with
its action "enqueue" in flow entry , so there is a functionality to get
its statistics also.

Following parameters are in openflow 1.0 spec, which I want to access -

Transmit Packets 64

Transmit Bytes 64

Transmit Overrun Errors 64

 

Matches support wildcards to the extent offered by OpenFlow 1.0.

When I am using wildcard then NOX (0.9)  giving me error :-
(error:unsupported flow attribute)

 

I'm actually not sure about fragments.  If I recall correctly, this is
more a function of the switch rather than the controller.

There are parameters to make flow entry with ip fragment fields ( to
match IP packets against these fields), that I haven''t found in NOX 0.9
zaku, it is present in ovs-ofctl.

 

I'm not sure what you mean by supporting those errors.  The controller
receives error the messages, so... yes?

 

You also haven't mentioned whether you're interested in the Python or
the C++ API, and support differs somewhat across languages.

 

-- Murphy

 

On Jan 15, 2012, at 7:55 PM, Sheili Mittal wrote:

 

Hi Murphy,

 

Thanks for this quick response, I needed that data urgently.

Can you please confirm are the below mentioned features supported in
destiny branch?

 

I saw destiny branch is unstable on NOX site so I used 0.9 zaku.

 

Thanks & Regards,

Sheili Mittal

 

From: Murphy McCauley [mailto:jam...@nau.edu] 
Sent: 16 January 2012 09:22
To: Sheili Mittal
Cc: nox-dev@noxrepo.org
Subject: Re: [nox-dev] need support for these features in NOX

 

The most recent branch is destiny.

 

-- Murphy

 

On Jan 15, 2012, at 7:49 PM, Sheili Mittal wrote:

 

Hi,

 

I am using NOX 0.9 zaku, following is not supporting in this, Can anyone
please confirm in which branch of NOX all the following supported:-

 

1)      Action Enqueue

2)      Flow statistics

3)      Queue statistics

4)      Wilcard ( ANY and other wildcard of openflow 1.0)

5)      L3 matching on IP fragment

6)      Error message -

OFPET_FLOW_MOD_FAILED

OFPET_PORT_MOD_FAILED

OFPET_QUEUE_OP_FAILED

 

Regards,

Sheili

 

 

DISCLAIMER: 
------------------------------------------------------------------------
----------------------------------------------- 
The contents of this e-mail and any attachment(s) are confidential and
intended 
for the named recipient(s) only.  
It shall not attach any liability on the originator or NECHCL or its 
affiliates. Any views or opinions presented in  
this email are solely those of the author and may not necessarily
reflect the 
opinions of NECHCL or its affiliates.  
Any form of reproduction, dissemination, copying, disclosure,
modification, 
distribution and / or publication of  
this message without the prior written consent of the author of this
e-mail is 
strictly prohibited. If you have  
received this email in error please delete it and notify the sender 
immediately. . 
------------------------------------------------------------------------
-----------------------------------------------

_______________________________________________
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

 

DISCLAIMER: 
------------------------------------------------------------------------
----------------------------------------------- 
The contents of this e-mail and any attachment(s) are confidential and
intended 
for the named recipient(s) only.  
It shall not attach any liability on the originator or NECHCL or its 
affiliates. Any views or opinions presented in  
this email are solely those of the author and may not necessarily
reflect the 
opinions of NECHCL or its affiliates.  
Any form of reproduction, dissemination, copying, disclosure,
modification, 
distribution and / or publication of  
this message without the prior written consent of the author of this
e-mail is 
strictly prohibited. If you have  
received this email in error please delete it and notify the sender 
immediately. . 
------------------------------------------------------------------------
-----------------------------------------------

 




DISCLAIMER: 
-----------------------------------------------------------------------------------------------------------------------
 
The contents of this e-mail and any attachment(s) are confidential and
intended 
for the named recipient(s) only.  
It shall not attach any liability on the originator or NECHCL or its 
affiliates. Any views or opinions presented in  
this email are solely those of the author and may not necessarily reflect the 
opinions of NECHCL or its affiliates.  
Any form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of  
this message without the prior written consent of the author of this e-mail is 
strictly prohibited. If you have  
received this email in error please delete it and notify the sender 
immediately. . 
-----------------------------------------------------------------------------------------------------------------------
_______________________________________________
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Reply via email to