- Community Home
- >
- Networking
- >
- Software Defined Networking
- >
- Problem by adding Netmasks to Ipv4-Match Fields
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
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
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
тАО10-23-2017 02:46 AM
тАО10-23-2017 02:46 AM
Hello,
I try to add a Flow, via RSdoc REST-API at HPE SDN-Controller V 2.17.18, to my HPE 2920 Switch. I tried it like this:
{
"flow":{
"priority":50000,
"hard_timeout":60,
"table_id":100,
"match":[
{"ipv4_src": "192.168.59.10/24"},
{"ipv4_dst": "192.168.58.10/24"},
{ "eth_type": "ipv4"},],
"instructions":[
{ "apply_actions":[{"output":23}]}
]
}
}
Even I tried /255.255.255.0 instead of /24. Both did not work with netmasks, but without them the flow is able to be send to the switch. The error Response Body says:
{
"error": "java.lang.IllegalArgumentException",
"message": "Unsupported customized Match Field ipv4_src"
}
Does someone know the right syntax?
Regards Tobias
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-23-2017 07:37 AM
тАО10-23-2017 07:37 AM
SolutionI think you have to specify the mask separately:
{ "flow":{ "priority":50000, "hard_timeout":60, "table_id":100, "match":[ {"ipv4_src": "192.168.59.10", "mask": "255.255.255.0"}, {"ipv4_dst": "192.168.58.10", "mask": "255.255.255.0"}, { "eth_type": "ipv4"},], "instructions":[ { "apply_actions":[{"output":23}]} ] } }
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-25-2017 12:07 AM
тАО10-25-2017 12:07 AM
Re: Problem by adding Netmasks to Ipv4-Match Fields
Thanks Checho,
just remove the comma between the two closing brackets here { "eth_type": "ipv4"} , ] , and it works fine for me.