Segment Range Validation should be Done based on Segment Type.

Bug #1227031 reported by Sunder Jadam
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cisco Openstack
Fix Committed
Undecided
Abishek Subramanian

Bug Description

The value entered in Segment Range should be validated for example for the vlan if i entered vlan range >4094 it should given the error message saying segment range is invalid.

Segment Type - Range

Vlan <1-3967,4048-4093>
vxlan - 4096-16000000

Logs :

(quantum) cisco-network-profile-list
+--------------------------------------+---------+--------------+----------+---------------+------------------+--------------------+
| id | name | segment_type | sub_type | segment_range | physical_network | multicast_ip_range |
+--------------------------------------+---------+--------------+----------+---------------+------------------+--------------------+
| 3fd8d809-e133-44c1-8a69-7afd552ee758 | name | vlan | | 101-100 | vsm | |
| 54ffca18-10a0-4edb-8055-63c0ad88547e | vlan1 | vlan | | 2252-2258 | vsm | |
| b8ef8e12-8fde-4e52-b48f-e3ad21765b7d | -vetest | vlan | | 4090-4099 <<<<<<<<<< This was not expected .. | VSM | |
+--------------------------------------+---------+--------------+----------+---------------+------------------+--------------------+
(quantum)

With CLI also

(quantum) cisco-network-profile-create test vlan --segment_range 4092-4096 --physical_network VSM
Created a new network_profile:
+--------------------+--------------------------------------+
| Field | Value |
+--------------------+--------------------------------------+
| id | 02101cf2-cd4f-401c-94a3-69aab8a6c0b0 |
| multicast_ip_range | |
| name | test |
| physical_network | VSM |
| segment_range | 4092-4096 |
| segment_type | vlan |
| sub_type | |
+--------------------+--------------------------------------+
(quantum)

(quantum) cisco-network-profile-list
+--------------------------------------+-------+--------------+----------+---------------+------------------+--------------------+
| id | name | segment_type | sub_type | segment_range | physical_network | multicast_ip_range |
+--------------------------------------+-------+--------------+----------+---------------+------------------+--------------------+
| 02101cf2-cd4f-401c-94a3-69aab8a6c0b0 | test | vlan | | 4092-4096 | VSM | |
| 0a6fd808-0190-4c3d-a132-7e01e91fff82 | vlan1 | vlan | | 2252-2260 | VSM | |
+--------------------------------------+-------+--------------+----------+---------------+------------------+--------------------+
(quantum)

Tags: n1k
tags: added: n1k
Changed in openstack-cisco:
assignee: nobody → Abishek Subramanian (absubram)
Revision history for this message
Abishek Subramanian (absubram) wrote :

This is a VSM issue - not an openstack issue. The help description is more of a guideline giving the segment ranges. However if the VSM accepts those ranges, then openstack can't error out.

Changed in openstack-cisco:
status: New → Incomplete
Revision history for this message
Abishek Subramanian (absubram) wrote :

Check with the Cisco N1K VSM team first.

Revision history for this message
Abishek Subramanian (absubram) wrote :

Has been fixed on neutron side. No longer an issue.

Changed in openstack-cisco:
status: Incomplete → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.