- Community Home
- >
- Networking
- >
- Software Defined Networking
- >
- Re: Which switches are v1 and which switches are v...
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
01-15-2014 11:57 AM
01-15-2014 11:57 AM
Hello,
I upgraded two 3500yl-24G to K.15.14.0003 and connected to pox with l2 topology and HP SDN 2.0 network controller. Than I tried to ping which worked but had a latency of 1.2 ms normally it would be 0.3 ms. Than I tried
to do netio between the nodes which gave me a throughput of 8 MByte/s but it should above 100 MB/s for Gbit ethernet. I also noticed that the CPU consumption of the switch went up to 80% + so verify my assumption that
the switch is operating in software, I run the following commands:
; J8692A Configuration Editor; Created on release #K.15.14.0003 ; Ver #05:08.7f.ff.3f.ef:5d hostname "HP-3500yl-24G" module 1 type j86xxa snmp-server community "public" unrestricted openflow controller-id 1 ip 192.168.10.21 controller-interface vlan 1 instance aggregate listen-port controller-id 1 version 1.3 limit hardware-rate 10000000 limit software-rate 10000 enable exit enable exit vlan 1 name "DEFAULT_VLAN" no untagged 5-24 untagged 1-4 ip address 192.168.10.1 255.255.255.0 exit vlan 5 name "OPENFLOW" untagged 5-24 no ip address exit no tftp server no autorun no dhcp config-file-update no dhcp image-file-update
After seeing that the flows are installed in software, we tried to enable ip control table mode, which failed:
HP-3500yl-24G(openflow)# ip-control-table-mode IP Control Table Mode cannot be set when V1 module is enabled.
We can see that the flows are installed in software:
HP-3500yl-24G# show openflow instance aggregate flows OpenFlow Flow Table Flow 1 Match Incoming Port : 11 Ethernet Type : IP Source MAC : 7446a0-c0e6a9 Destination MAC : 7446a0-c0e66a VLAN ID : 5 VLAN Priority : 2 Source Protocol Address : 10.10.10.2/32 Target Protocol Address : 10.10.10.1/32 IP Protocol : TCP IP ToS Bits : 0 Source Port : 43566 Destination Port : 18767 Attributes Priority : 65535 Duration : 0 seconds Hard Timeout : 30 seconds Idle Timeout : 10 seconds Byte Count : 112558 Packet Count : 77 Controller ID : 1 Cookie : 0x0 Flow Location : Software Hardware Index : NA Reason Code : 2 Reason Description : The rule has a match criterion for MAC address Actions Output : 21 Flow 2 Match Incoming Port : 21 Ethernet Type : IP Source MAC : 7446a0-c0e66a Destination MAC : 7446a0-c0e6a9 VLAN ID : 5 VLAN Priority : 2 Source Protocol Address : 10.10.10.1/32 Target Protocol Address : 10.10.10.2/32 IP Protocol : TCP IP ToS Bits : 0 Source Port : 18767 Destination Port : 43565 Attributes Priority : 65535 Duration : 10 seconds Hard Timeout : 30 seconds Idle Timeout : 10 seconds Byte Count : 54204171 Packet Count : 39894 Controller ID : 1 Cookie : 0x0 Flow Location : Software Hardware Index : NA Reason Code : 2 Reason Description : The rule has a match criterion for MAC address Actions Output : 11 Flow 3 Match Incoming Port : 21 Ethernet Type : IP Source MAC : 7446a0-c0e66a Destination MAC : 7446a0-c0e6a9 VLAN ID : 5 VLAN Priority : 2 Source Protocol Address : 10.10.10.1/32 Target Protocol Address : 10.10.10.2/32 IP Protocol : TCP IP ToS Bits : 0 Source Port : 18767 Destination Port : 43566 Attributes Priority : 65535 Duration : 0 seconds Hard Timeout : 30 seconds Idle Timeout : 10 seconds Byte Count : 1548 Packet Count : 22 Controller ID : 1 Cookie : 0x0 Flow Location : Software Hardware Index : NA Reason Code : 2 Reason Description : The rule has a match criterion for MAC address Actions Output : 11 Flow 4 Match Incoming Port : 11 Ethernet Type : IP Source MAC : 7446a0-c0e6a9 Destination MAC : 7446a0-c0e66a VLAN ID : 5 VLAN Priority : 2 Source Protocol Address : 10.10.10.2/32 Target Protocol Address : 10.10.10.1/32 IP Protocol : TCP IP ToS Bits : 0 Source Port : 43565 Destination Port : 18767 Attributes Priority : 65535 Duration : 10 seconds Hard Timeout : 30 seconds Idle Timeout : 10 seconds Byte Count : 39550586 Packet Count : 33716 Controller ID : 1 Cookie : 0x0 Flow Location : Software Hardware Index : NA Reason Code : 2 Reason Description : The rule has a match criterion for MAC address Actions Output : 21
So it appears that v1 hardware is completly useless for OpenFlow becaue it can't even switch layer2 in hardware.
Can someone provide me with a list of HP switches which support Layer 2 and Layer 3 in hardware?
Is there a list of devices which are v1 and which are v2?
Cheers,
Thomas
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2014 12:04 PM
01-15-2014 12:04 PM
SolutionThe 3500 is a V1 switch. The 2920 and 3800 are V2 switches and the 5400 and 8200 support V2 modules. If you have only V2 modules in a switch, it is a good idea to disable v1 modules with "no allow-v1-modules". The 2920 does have one limitation that the 3800 and other V2 devices don't. It cannot process rules in hardware that are based on destination MAC address.
I also recommend that you look at the OpenFlow guide for the switches: http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/action.process/public/psi/manualsDisplay/?sp4ts.oid=3457354&javax.portlet.action=true&spf_p.tpst=psiContentDisplay&javax.portlet.begCacheTok=com.vignette.cachetoken&spf_p.prp_psiContentDisplay=wsrp-interactionState%3DdocId%253Demr_na-c03991489%257CdocLocale%253Den_US&javax.portlet.endCacheTok=com.vignette.cachetoken
The 3500 is useful and can process rules based on L3 information in hardware.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2014 12:31 PM
01-15-2014 12:31 PM
Re: Which switches are v1 and which switches are v2?
Hello Eric,
the document you mentioned lists the 3500 being capable of matching all fields for IPv4 in hardware in figure 7 on page 70. Is this information wrong? It also lists SRC and DST MAC. This is for firmware KA.15.14 which I have installed.
Cheers,
Thomas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2014 01:18 PM
01-15-2014 01:18 PM
Re: Which switches are v1 and which switches are v2?
Hi Thomas,
Wow, no the doc is not correct. I sincerely appologize. For v1 devices on K.15.14, the VLAN Priority, Src & Dst MAC fields should be yellow.
I will get the doc fixed.
Thank you for bringing it to my attention,
Eric
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2014 11:57 PM - edited 01-15-2014 11:57 PM
01-15-2014 11:57 PM - edited 01-15-2014 11:57 PM
Re: Which switches are v1 and which switches are v2?
Hello Eric,
thank you so much for the clarification. Now everything is clear. Next week I hopefully get my hands on v2 hardware
and can continue my tests.
Cheers,
Thomas