Duplicate ipv6 ips(one is external facing) in two slices

[Fengping Hu]

We created two slices and got same ipv6 ip addresses allocated to both slices. Here are the slice and ip informations
slice 1)
ID d9611402-72e6-4ced-a681-3836b894105d
Name ServiceXSlice
networks
ef716d0d-ec82-474a-b511-e141a805947f NET1 L3 FABNetv4 CERN 10.143.1.1 10.143.1.0/24 Active
16fa9e2e-5a20-4464-9c63-0c718d6a4160 NET2 L3 FABNetv6 CERN 2602:fcfb:1d:1::1 2602:fcfb:1d:1::/64 Active
Slice 2)
ID b7387dd8-01b7-4036-bcf8-96869ed6f07e
Name ServiceXSlice1
Networks
d90dbe24-b8d3-4ea8-ae97-8d9dbab38d83 NET1 L3 FABNetv4 CERN 10.143.2.1 10.143.2.0/24 Active
24f90584-a39f-4e77-8559-653dbc57f946 NET2 L3 FABNetv6 CERN 2602:fcfb:1d:2::1 2602:fcfb:1d:2::/64 Active
a9d5ad39-f6dc-41ea-b9ef-aae75575cd49 NET3 L3 FABNetv6Ext CERN 2602:fcfb:1d:1::1 2602:fcfb:1d:1::/64 Active

Notice above that NET2 of the ServiceXSlice has gateway ip 2602:fcfb:1d:1::1, which is the same as the NET3 of the ServiceXSlice1. The two network service are of different types, one is FABNetV6, the other is FABNetv6Ext. Similarly, the ips allocated to node interfaces are also duplicated.

Please let me know if more details are needed.

Thanks,
Fengping

[Komal Thareja]

Thank you for sharing this and helping us make the testbed better. It was a bug. A fix has been deployed. Could you please delete the slice which has FABNetv6Ext and recreate it again?

Thanks,
Komal

[Fengping Hu]

Hi Komal,

Thanks for getting a fix in so quickly. It seems I still have some issues(could be a different issue)

I created the slice and then tried to call the change_public_ip function. Then the whole network service disappeared from the slice. One thing to note is that I use this network3.change_public_ip(ipv6=list(map(str,network3_available_ips[0:100])))

instead of

network3.change_public_ip(ipv6=[str(network3_available_ips[0])]).

My intention is to change_public_ip for 100 address instead of just one.  Since the ipv6 parameter is a list,  I assume this would work.

Here’s the slice information.

ID
1fe8c351-e6be-4205-9c23-e77b9ccd8a41
Name
ServiceXSlice1

Network service before the change_public_ip call
b2483916-e980-490d-9315-c7705d7264c0 NET1 L3 FABNetv4 CERN 10.143.2.1 10.143.2.0/24 Active
0ea13f16-c58b-4ef0-945c-d6c92493190a NET2 L3 FABNetv6 CERN 2602:fcfb:1d:2::1 2602:fcfb:1d:2::/64 Active
4a338812-470d-41fc-a510-145dfd775816 NET3 L3 FABNetv6Ext CERN 2602:fcfb:1d:3::1 2602:fcfb:1d:3::/64 Active

Network service after the change_public_ip call
b2483916-e980-490d-9315-c7705d7264c0 NET1 L3 FABNetv4 CERN 10.143.2.1 10.143.2.0/24 Active
0ea13f16-c58b-4ef0-945c-d6c92493190a NET2 L3 FABNetv6 CERN 2602:fcfb:1d:2::1 2602:fcfb:1d:2::/64 Active

Thanks,

Fengping

[Komal Thareja]

Hello Fengping,

Thanks you for sharing your observation. I looked at your slice. The Network Service in your slice is in Closed state as NSO failed to allow 100 external IP addresses. Enclosing the snapshot of the error below.

Also, I confirmed with the Network Team and found that we have an upper limit of 90 public IPs on a FabNetV6Ext. Their recommendation is to create an additional slice if you need more than 90 public IPs. Hope this helps!

err=failed lease update- all units failed priming: Exception during modify for unit: 4a338812-470d-41fc-a510-145dfd775816 Playbook has failed tasks: NSO exists invalid params. path = /ncs:services/l3rt:l3rt{NET3-4a338812-470d-41fc-a510-145dfd775816}/external-access/permit-ipv6{100}

Thanks,
Komal

[Fengping Hu]

Hi Komal,

Thanks for the details. I just randomly picked the number 100. I believe 90 address should be enough for my use case.

Thank you so much for getting this figure out so quickly.

Have a good weekend!
Fengping

[Author]

Posts