diff options
| author | Sai Gomathi N <nsaigomathi@vmware.com> | 2023-08-30 05:45:18 -0700 |
|---|---|---|
| committer | Sai Gomathi N <nsaigomathi@vmware.com> | 2023-08-30 06:02:12 -0700 |
| commit | dd1e34eff498985d8af26cfc329e751a4b022a9b (patch) | |
| tree | ab28dced85bab54493a071d4b078368a324013ad /pimd/pim_nb_config.c | |
| parent | 497584ac4825a283c2edbe4a55738020ebe7113e (diff) | |
pimd,pim6d: Resolving the YANG datatype Inconsistency for PIM Hello Interval
The YANG specification currently designates a uint8 data type for the hello interval,
despite the CLI documentation (ip pim hello (1-65535) [(1-65535)]) indicating a maximum value of 65535.
To address this inconsistency, updating the data type to uint16 allowing for a maximum value for hello intervals.
Signed-off-by: Sai Gomathi N <nsaigomathi@vmware.com>
Diffstat (limited to 'pimd/pim_nb_config.c')
| -rw-r--r-- | pimd/pim_nb_config.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/pimd/pim_nb_config.c b/pimd/pim_nb_config.c index 30d84710e6..be05b69401 100644 --- a/pimd/pim_nb_config.c +++ b/pimd/pim_nb_config.c @@ -1633,7 +1633,7 @@ int lib_interface_pim_address_family_hello_interval_modify( ifp = nb_running_get_entry(args->dnode, NULL, true); pim_ifp = ifp->info; pim_ifp->pim_hello_period = - yang_dnode_get_uint8(args->dnode, NULL); + yang_dnode_get_uint16(args->dnode, NULL); pim_ifp->pim_default_holdtime = -1; break; } |