Closed gve-vse-tim closed 2 years ago
The docs say the only two options are "default" and "jumbo" but specifying strings representing actual MTU sizes ("1500" and "9216") does in fact work. So, in short, could easily be simply a doc bug.
@gve-vse-tim, Thanks for raising this issue. You are right, this is a documentation issue, for truck and access mtu should be string and for routed interface it should be integer. Will fix it.
The DCNM Ansible dcnm_interface module documentation says that, for the 'eth' profile, the MTU attribute is supposed to be a string. However, when I do specify the MTU attribute for a routed interface (in the example below), I get an Ansible error regarding conversion to 'int'. While the example below indicated mtu 'default', I have verified the same error gets thrown for mtu 'jumbo' (which is supposed to be the default value).
Not specifying mtu at all works just fine (and of course defaults to jumbo: 9216). The example was tested against the dCloud VXLAN Multisite environment (not following the VXLAN script though... just giving you a standard environment upon which to verify it).
Sample Ansible:
Output of the error: