[NX-OS] - "show running-configuration bgp" - Network statements are being overwritten

[jp2195]

The show running-configuration bgp looks like the network statements are being overwritten and not added to the dictionary. When utilizing the below bgp configuration you get the following output. There is a single af_network_number (192.168.3.0) and single af_network_mask (24). The output should contain both 192.168.1.1/32 and 192.168.3.0/24.
 
Example output:

router bgp 65000
  vrf bgptesting
    router-id 192.168.1.1
    log-neighbor-changes
    address-family ipv4 unicast
      network 192.168.1.1/32
      network 192.168.3.0/24
    neighbor 192.168.3.2
      remote-as 65001
      address-family ipv4 unicast

Resulting parsed data from this output:

{
    "bgp": {
        "instance": {
            "default": {
                "bgp_id": 65000,
                "protocol_shutdown": False,
                "vrf": {
                    "bgptesting": {
                        "graceful_restart": True,
                        "log_neighbor_changes": True,
                        "router_id": "192.168.1.1",
                        "enforce_first_as": True,
                        "fast_external_fallover": True,
                        "flush_routes": False,
                        "isolate": False,
                        "af_name": {
                            "ipv4 unicast": {
                                "af_client_to_client_reflection": True,
                                "af_network_number": "192.168.3.0",
                                "af_network_mask": 24,
                            }
                        },
                        "neighbor_id": {
                            "192.168.3.2": {
                                "nbr_fall_over_bfd": False,
                                "nbr_suppress_four_byte_as_capability": False,
                                "nbr_disable_connected_check": False,
                                "nbr_ebgp_multihop": False,
                                "nbr_local_as_no_prepend": False,
                                "nbr_local_as_replace_as": False,
                                "nbr_local_as_dual_as": False,
                                "nbr_remote_as": 65001,
                                "nbr_remove_private_as": False,
                                "nbr_shutdown": False,
                                "nbr_af_name": {
                                    "ipv4 unicast": {
                                        "nbr_af_allowas_in": False,
                                        "nbr_af_route_reflector_client": False,
                                        "nbr_af_soft_reconfiguration": False,
                                        "nbr_af_next_hop_self": False,
                                        "nbr_af_as_override": False,
                                        "nbr_af_default_originate": False,
                                    }
                                },
                            }
                        },
                    }
                },
            }
        }
    }
}

Specific Section:

                        "af_name": {
                            "ipv4 unicast": {
                                "af_client_to_client_reflection": True,
                                "af_network_number": "192.168.3.0",
                                "af_network_mask": 24,
                            }
                        },

[ParimiNeeraja]

Hi @jp2195 ,
Thank you for letting us know. Kindly give me some time to check this issue.

Thank you.

[ParimiNeeraja]

Hi @jp2195 ,

I fix the issue, it had been merge with upcoming latest version.