|
1 | 1 | # Ixia-c Release Notes and Version Compatibility |
2 | 2 |
|
3 | 3 | ## Release v1.8.0-1 (Latest) |
4 | | -> 19th August, 2024 |
| 4 | +> 20th August, 2024 |
5 | 5 |
|
6 | 6 |
|
7 | 7 | #### Build Details |
|
23 | 23 |
|
24 | 24 |
|
25 | 25 | # Release Features(s) |
26 | | -* <b><i>Ixia-C Ixia Chassis & Appliances(Novus, AresOne), UHD400</i></b>: TBD |
27 | 26 |
|
28 | | -### Bug Fix(s) |
29 | | -* <b><i>Ixia-C Ixia Chassis & Appliances(Novus, AresOne), UHD400</i></b>: TBD |
| 27 | +* <b><i>Ixia Chassis & Appliances(Novus, AresOne)</i></b>: Support added for DHCPv6 Client and Server in control plane. [details](https://github.com/open-traffic-generator/models/pull/369) |
| 28 | + - User will be the able to configure DHCPv6 Client and Server by the following code snippet. |
| 29 | + ```go |
| 30 | + // Configure a DHCP Client |
| 31 | + dhcpv6client := d1Eth1.Dhcpv6Interfaces().Add(). |
| 32 | + SetName("p1d1dhcpv61") |
| 33 | + |
| 34 | + dhcpv6client.IaType().Iata() |
| 35 | + dhcpv6client.DuidType().Llt() |
| 36 | + |
| 37 | + // Configure a DHCPv6 Server |
| 38 | + d1Dhcpv6Server := d2.DhcpServer().Ipv6Interfaces().Add(). |
| 39 | + SetName("p2d1Dhcpv6Server1"). |
| 40 | + |
| 41 | + d1Dhcpv6ServerPool := d1Dhcpv6Server.SetIpv6Name("p2d1ipv6"). |
| 42 | + Leases().Add(). |
| 43 | + SetLeaseTime(3600) |
| 44 | + IaType := d1Dhcpv6ServerPool.IaType().Iata() |
| 45 | + IaType. |
| 46 | + SetStartAddress("2000:0:0:1::100"). |
| 47 | + SetStep(1). |
| 48 | + SetSize(10). |
| 49 | + SetPrefixLen(64) |
| 50 | + ``` |
| 51 | + Note: Support for `devices[i].dhcp_server.ipv6_interfaces[j].options` and `devices[i].dhcp_server.ipv6_interfaces[j].leases[k].ia_type.choice.iapd/ianapd` will be available in the subsequent sprints. |
| 52 | + |
| 53 | +* <b><i>Ixia Chassis & Appliances(Novus, AresOne)</i></b>: gNMI support added to fetch control plane metics and states of DHCPv6 [Client](https://github.com/open-traffic-generator/models-yang/blob/main/artifacts/open-traffic-generator-dhcpv6client.txt) and [Server](https://github.com/open-traffic-generator/models-yang/blob/main/artifacts/open-traffic-generator-dhcpv6server.txt). |
| 54 | + - User able for DHCPv6 Client/Server metrics using following gNMI paths. |
| 55 | + ```gNMI |
| 56 | + // dhcpv6 client |
| 57 | + dhcpv6-clients/dhcpv6-client[name=*]/state/counters |
| 58 | +
|
| 59 | + // dhcpv6 server |
| 60 | + dhcpv6-servers/dhcpv6-server[name=*]/state/counters |
| 61 | + ``` |
| 62 | + - User able for DHCPv6 Client/Server states using following gNMI paths. |
| 63 | + ```gNMI |
| 64 | + // dhcpv6 client |
| 65 | + dhcpv6-clients/dhcpv6-client[name=*]/state/interface |
| 66 | +
|
| 67 | + // dhcpv6 server |
| 68 | + dhcpv6-servers/dhcpv6-server[name=*]/state/interface |
| 69 | + ``` |
30 | 70 |
|
31 | 71 |
|
32 | 72 | #### Known Issues |
33 | 73 | * <b><i>Ixia Chassis & Appliances(Novus, AresOne)</i></b>: If `keng-layer23-hw-server` version is upgraded/downgraded, the ports which will be used from this container must be rebooted once before running the tests. |
34 | | -* <b><i>Ixia Chassis & Appliances(Novus, AresOne)</i></b>: `StartProtocols`/`set_control_state.protocol.all.start` can get stuck till the time all DHPCv4 clients receive the leased IPv4 addresses from the DHCPv4 server/relay agent. This may result in getting `"context deadline exceeded"` error in the test program. |
| 74 | +* <b><i>Ixia Chassis & Appliances(Novus, AresOne)</i></b>: `StartProtocols`/`set_control_state.protocol.all.start` can get stuck till the time all DHPCv4/v6 clients receive the leased IPv4/v6 addresses from the DHCPv4/v6 server/relay agent. This may result in getting `"context deadline exceeded"` error in the test program. |
35 | 75 | * <b><i>UHD400</i></b>: Packets will not be transmitted if `flows[i].rate.pps` is less than 50. |
36 | 76 | * <b><i>UHD400</i></b>: `values` for fields in flow packet headers can be created with maximum length of 1000 values. |
37 | 77 | * <b><i>Ixia-C</i></b>: Flow Tx is incremented for flow with tx endpoints as LAG, even if no packets are sent on the wire when all active links of the LAG are down. |
38 | 78 | * <b><i>Ixia-C</i></b>: Supported value for `flows[i].metrics.latency.mode` is `cut_through`. |
39 | 79 | * <b><i>Ixia-C</i></b>: The metric `loss` in flow metrics is currently not supported. |
40 | | -* <b><i>Ixia-C</i></b>: When flow transmit is started, transmission will be restarted on any existing flows already transmitting packets. |
| 80 | +* <b><i>Ixia-C</i></b>: When flow transmit is started, transmission will be restarted on any existing flows already transmitting packets. |
41 | 81 |
|
42 | 82 |
|
43 | 83 | ## Release v1.7.2-1 |
|
0 commit comments