netapp.ontap.na_ontap_net_port, _ifgrp modules

[keen rose]

Hi there - we're trying to create an Ansible role for a new ONTAP cluster creation. As part of that role, we want to setup ONTAP ports and networking (ifgrps, LIFs, etc.) However there's no current support for REST API nor ZAPI for either na-ontap-net-port and na-ontap-net-ifgrp-modules. Is this by design? If not, can we get support for it? Networking on ONTAP clusters is key and we need this. Thank you!

https://docs.ansible.com/ansible/devel/collections/netapp/ontap/na_ontap_net_port_module.html#ansible-collections-netapp-ontap-na-ontap-net-port-module
https://docs.ansible.com/ansible/devel/collections/netapp/ontap/na_ontap_net_ifgrp_module.html#ansible-collections-netapp-ontap-na-ontap-net-ifgrp-module

sorry - ZAPI is supported, however some of the options we'd like to set aren't - options that are critical to both the network ports and ifgrps functioning properly...

[rigid compass]

A couple of examples:

Module: na_ontap_net_port
Error:

# value(s) in REST: ['mtu', 'autonegotiate_admin', 'speed_admin']```

Module: **na_ontap_net_ifgrp**
Error:
```[WARNING]: Falling back to ZAPI because of unsupported option(s) or option
# value(s) in REST: ['name']```

[timid prism]

@keen rose Both the mentioned modules support REST, requires ONTAP 9.6 or later.

[timid prism]

The error is self explanatory i.e. the module is falling back to ZAPI as the mentioned option(s) aren't supported in REST.

[sinful elk]

@timid prism @tired drift if ‘name’ isn’t supported in rest then how do we create a ifgrp with the specific name?

[timid prism]

We had reached out to REST team regarding support for 'name' in REST while creating a ifgrp and the response received was "LAG names are not human-meaningful in ONTAP, so the names are automatically created in REST".
So as part of 22.8.0 collection release, we made a minor change to return 'name' and other details of a newly created interface group in module output in REST so that it can be utilized if required. Hope this information helps!

[sinful elk]

@timid prism if we have to use rest then we skip name and ontap will create ifgrp name automatically? But if we mention name then module will use zapi and not rest right?

[rigid compass]

@timid prism We are running 9.6+ so we know that REST is supported. The issue is that the parameters that we want to pass make it fall back to ZAPI. Similar to name for ifgrp, the mtu, autonegotiate, and speed admin options are critical for us to define so we would like to understand why these aren't available in REST

[tired drift]

@rigid compass that would be a question for the #1063542514780475493 team.

For na_ontap_net_port as of 9.14

MTU does exist now and we can add (i'll have to check what ever it was added.

But there is no rest equivalent or the other 2 variables, so thouse would need to be asked for for the ONTAP API team

na_ontap_net_ifgrp is something we need to add. So all the example the ONTAP team have for ifgrp don't include a top level name. Like this one.

But looking at the docs them self it look like it is support, so we can probably make the change to include a name.

[timid prism]

@tired drift we had received an earlier request for adding 'name' to module na_ontap_net_ifgrp in REST. But when we tested that REST API did not accept parameter “name” for the ifgrp/lag creation and threw error 'name can’t be set in this operation'.

And then REST team responded that LAG names are not human-meaningful in ONTAP, so the names are automatically created in REST.

[timid prism]

yes, that's right.

[keen rose]

@timid prism , @tired drift - we're okay if the automatically generated names are similar to the ones currently conventionally used in customer environments: a0a, a0b, etc.

[tired drift]

Ahhh ok if that the case, can you update the documentation to reference that.

[timid prism]

yes @keen rose, it'll be similar.

[timid prism]

sure @tired drift, I'll create a story for this.

we've story 6807 open for this.

[sinful elk]

@timid prism Our customer has standard ifgrp naming convention, like a1a for data and a1z for ic and considering rest doesn’t support name and since ontap automatic generated names won’t work for our customer. Considering our customer requirement, the only option for me is to use rest cli if I want to create ifgrp with a specific naming standard right?

[timid prism]

@sinful elk could you once confirm on the naming convention followed by REST in #1063542514780475493 ?