- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Re: About Implementation of Openflow Meter Feature...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2019 07:03 AM
09-19-2019 07:03 AM
About Implementation of Openflow Meter Feature in ARUBA HPE 2930F Switches
Hi,
I want to know how Meter feature of Openflow protocol is realized in Aruba HPE 2930F switch. Like if I have a meter of type drop with rate of 100Mbps. How would switch make sure that throughput of a flow on which meter is applied does not go beyond 100Mbps? Specifically, after how many intervals does the switch keep checking thoughput of the flow to drop packets if it exceed the given rate? Also, What is the smallest rate that can be accurately applied via meters?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2019 10:23 AM
10-01-2019 10:23 AM
Re: About Implementation of Openflow Meter Feature in ARUBA HPE 2930F Switches
Hi
Thank you for writing.
May we know the Version/firmware running on the code and if you have basic configuration to share with us for review.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2019 06:00 AM
10-21-2019 06:00 AM
Re: About Implementation of Openflow Meter Feature in ARUBA HPE 2930F Switches
leaf1# sh version
Image stamp:
/ws/swbuildm/rel_venice_qaoff/code/build/lvm(swbuildm_rel_venice_qaoff_rel_veni
ce)
Mar 26 2018 23:16:08
WC.16.05.0007
570
Boot Image: Primary
Boot ROM Version: WC.16.01.0005
Active Boot ROM: Primary
I have configured OpenfFlow interface on the switch as follows:
leaf1(of-inst-l1)# sh openflow instance l1
Configured OF Version : 1.3 only
Negotiated OF Version : 1.3
Instance Name : l1
Data-path Description : l1
Administrator Status : Enabled
Member List : VLAN 3
Pipeline Model : Custom
Listen Port : 6633
Operational Status : Up
Operational Status Reason : NA
Datapath ID : 00035480285c79a0
Mode : Active
Flow Location : Hardware Only
No. of Hardware Flows : 4
No. of Software Flows : 0
Hardware Rate Limit : 0 kbps
Software Rate Limit : 2000 pps
Conn. Interrupt Mode : Fail-Secure
Maximum Backoff Interval : 10 seconds
Probe Interval : 10 seconds
Hardware Table Miss Count : NA
No. of Software Flow Tables : NA
Table Model : Custom Pipeline
Source MAC Group Table : Disabled
Destination MAC Group Table : Disabled
Default Miss Action : Drop
Packet-In VLAN Tagging : Input Form
Controller Id Connection Status Connection State Secure Role
------------- ----------------- ---------------- ------ ------
1 Disconnected Backoff No Equal
Show running configuration gives following results:
leaf1(of-inst-l1)# sh running-config
Running configuration:
; JL253A Configuration Editor; Created on release #WC.16.05.0007
; Ver #12:08.1d.9b.3f.bf.bb.ef.7c.59.fc.6b.fb.9f.fc.ff.ff.37.ef:ba
hostname "leaf1"
module 1 type jl253a
max-vlans 2048
interface 11
name "eleven"
exit
snmp-server community "public" unrestricted
openflow
controller-id 1 ip 192.168.0.1 controller-interface vlan 2
instance "l1"
listen-port
member vlan 3
controller-id 1
version 1.3 only
limit software-rate 2000
max-backoff-interval 10
pipeline-model custom
packet-in vlan-tagging input-form
enable
exit
enable
exit
vlan 1
name "DEFAULT_VLAN"
no untagged 1-3,11-13,19-24
untagged 4-10,14-18,25-28
no ip address
exit
vlan 2
name "c-vlan"
untagged 19-24
ip address 192.168.1.1 255.255.0.0
exit
vlan 3
name "s-vlan"
untagged 1-3,11-13
ip address 10.1.0.1 255.0.0.0
exit
I don't think my configuration has something to do with how Openflow rate meter is ensured in the hardware switch. Leaky bucket is one way of ensuring meter-rate. I want to knwo what approach ARUBA HPE 2930F switch uses.