Releases: open-traffic-generator/ixia-c
Releases · open-traffic-generator/ixia-c
Release v0.1.0-53
About
This build includes new features and bug fixes.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.13.0 |
snappi | 0.13.0 |
gosnappi | 0.13.0 |
keng-controller | 0.1.0-53 |
ixia-c-traffic-engine | 1.6.0.85 |
keng-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.337 |
keng-layer23-hw-server | 0.13.0-6 |
keng-operator | 0.3.13 |
otg-gnmi-server | 1.13.0 |
ixia-c-one | 0.1.0-53 |
UHD400 | 1.0.27 |
Release Features(s)
- Support added for link
up/down
trigger for UHD400.portStateAction := gosnappi.NewControlState(). Port(). Link(). SetPortNames([]string{"port1"}). SetState(gosnappi.StatePortLinkState.DOWN) gosnappi.NewApi().setControlState(portStateAction)
- Support added for 0x8100(Vlan) and 0x6007(Google Discovery Protocol) ether types in data plane traffic in UHD400.
Bug Fix(s)
- Some tests were failing because packets were not sent on wire due to frame size of flows not being sufficient to include tracking information in Ixia Chassis & Appliances(AresOne only) is fixed.
egress
tracking on VLAN id or other fields for more than 3 bits was not working in Ixia Chassis & Appliances(Novus, AresOne), is fixed.egress
tracking now supports upto 11 bits.
- Issue in ARP resolution in certain cases is now fixed in UHD400.
Known Issues
- If
keng-layer23-hw-server
version is upgraded/downgraded, the ports from Ixia Chassis & Appliances(Novus, AresOne) which will be used from this container must be rebooted once before running the tests. - Adding more than 256 devices on a single ixia-c-port causing failure for Ixia Chassis & Appliances(Novus, AresOne).
- 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.
- With certain DUTs, ssh service hangs if ISIS L1 MD5 is enabled.
- Supported value for
flows[i].metrics.latency.mode
iscut_through
. - The metric
loss
in flow metrics is currently not supported. - When flow transmit is started, transmission will be restarted on any existing flows already transmitting packets.
- #118
Release v0.1.0-26
About
This build includes stability fixes.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.13.0 |
snappi | 0.13.0 |
gosnappi | 0.13.0 |
keng-controller | 0.1.0-26 |
ixia-c-traffic-engine | 1.6.0.85 |
keng-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.337 |
keng-layer23-hw-server | 0.13.0-2 |
keng-operator | 0.3.13 |
otg-gnmi-server | 1.13.0 |
ixia-c-one | 0.1.0-26 |
UHD400 | 1.0.26 |
Known Issues
- If
keng-layer23-hw-server
version is upgraded/downgraded, the ports from Ixia Chassis & Appliances(Novus, AresOne) which will be used from this container must be rebooted once before running the tests. - Adding more than 256 devices on a single ixia-c-port causing failure for Ixia Chassis & Appliances(Novus, AresOne).
- 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.
- With certain DUTs, ssh service hangs if ISIS L1 MD5 is enabled.
- Supported value for
flows[i].metrics.latency.mode
iscut_through
. - The metric
loss
in flow metrics is currently not supported. - When flow transmit is started, transmission will be restarted on any existing flows already transmitting packets.
- #118
Release v0.0.1-4555
About
This build extends usage expiry of previously released v0.0.1-4554
to 30th November, 2023
.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.12.5 |
snappi | 0.12.6 |
gosnappi | 0.12.6 |
ixia-c-controller | 0.0.1-4555 |
ixia-c-traffic-engine | 1.6.0.85 |
ixia-c-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.331 |
ixia-c-ixhw-server | 0.12.5-1 |
ixia-c-operator | 0.3.6 |
ixia-c-gnmi-server | 1.12.7 |
ixia-c-one | 0.0.1-4555 |
Release v0.1.0-3
About
This build includes new features, stability and bug fixes.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.13.0 |
snappi | 0.13.0 |
gosnappi | 0.13.0 |
keng-controller | 0.1.0-3 |
ixia-c-traffic-engine | 1.6.0.85 |
keng-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.337 |
keng-layer23-hw-server | 0.13.0-2 |
keng-operator | 0.3.13 |
otg-gnmi-server | 1.13.0 |
ixia-c-one | 0.1.0-3 |
Release Feature(s)
- Ixia-C now offers following existing licensed features free for community use (without requiring Keysight Licensing Solution):
ixia-c-protocol-engine
, which enables control plane emulation in Ixia-C is now publicly downloadable.- Emulation of one or more IPv4 and IPv6 interfaces with Address Resolution Protocol (ARP) and Neighbor Discovery (ND), respectively, is now supported.
- Automatic destination MAC address resolution for flows with IPv4 / IPv6 endpoints is now supported.
- Configuring one BGP session over IPv4 / IPv6, advertising V4 / V6 routes is now supported.
- Users exercising full feature set (Keysight Elastic Network Generator aka KENG) will now have to subscribe to Keysight Licensing Solution. Please reach out to Keysight for more details.
keng-layer23-hw-server
, which facilitates control and data plane operations on Ixia Chassis & Appliances(Novus, AresOne) is now publicly downloadable (but can only be used with Keysight Licensing Solution)- Support is added for overload bit and extended ipv4 reachability in
get_states
for isis_lsps in Ixia Chassis & Appliances(Novus, AresOne); gNMI path forisis_lsps
:+--rw isis-routers +--ro isis-router* [name] +--ro name -> ../state/name +--ro state +--ro name? string . . +--ro link-state-database +--ro lsp-states
The container image paths have changed for some Ixia-C artifacts. Please review Build Details for correct paths.
Bug Fix(s)
- Memory leak in Ixia Chassis & Appliances(Novus, AresOne) is fixed for long duration tests.
gosnappi
now correctly validates required primitive types when they're not explicitly set by users.- IS-IS metric is no longer sent as 63 when configured as 200 (or more than 63) with wide metrics enabled on Ixia Chassis & Appliances(Novus, AresOne).
Known Issues
- If
keng-layer23-hw-server
version is upgraded/downgraded, the ports from Ixia Chassis & Appliances(Novus, AresOne) which will be used from this container must be rebooted once before running the tests. - Adding more than 256 devices on a single ixia-c-port causing failure for Ixia Chassis & Appliances(Novus, AresOne).
- 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.
- With certain DUTs, ssh service hangs if ISIS L1 MD5 is enabled.
- Supported value for
flows[i].metrics.latency.mode
iscut_through
. - The metric
loss
in flow metrics is currently not supported. - When flow transmit is started, transmission will be restarted on any existing flows already transmitting packets.
- #118
Release v0.0.1-4554
About
This build includes bug fixes.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.12.5 |
snappi | 0.12.6 |
gosnappi | 0.12.6 |
ixia-c-controller | 0.0.1-4554 |
ixia-c-traffic-engine | 1.6.0.85 |
ixia-c-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.331 |
ixia-c-ixhw-server | 0.12.5-1 |
ixia-c-operator | 0.3.6 |
ixia-c-gnmi-server | 1.12.7 |
ixia-c-one | 0.0.1-4554 |
Bug Fix(s)
monitor.flow_metrics
will now correctly reportsbytes_tx
.- The VLAN TPID field in flow packet header configuration is now set to correct default of 65535 when it’s not encapsulating known protocol header.
Known Issues
- Supported value for
flows[i].metrics.latency.mode
iscut_through
. - The metric
loss
in flow metrics is currently not supported. - When flow transmit is started, transmission will be restarted on any existing flows already transmitting packets.
- #118
Release v0.0.1-4478
About
This build includes stability fixes.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.12.3 |
snappi | 0.12.3 |
gosnappi | 0.12.3 |
ixia-c-controller | 0.0.1-4478 |
ixia-c-traffic-engine | 1.6.0.45 |
ixia-c-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.326 |
ixia-c-ixhw-server | 0.12.3-2 |
ixia-c-operator | 0.3.6 |
ixia-c-gnmi-server | 1.12.5 |
ixia-c-one | 0.0.1-4478 |
Known Issues
- Supported value for
flows[i].metrics.latency.mode
iscut_through
. - The metric
loss
in flow metrics is currently not supported. - When flow transmit is started, transmission will be restarted on any existing flows already transmitting packets.
- #118
Release v0.0.1-4435
About
This build includes bug fixes.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.12.2 |
snappi | 0.12.2 |
gosnappi | 0.12.2 |
ixia-c-controller | 0.0.1-4435 |
ixia-c-traffic-engine | 1.6.0.35 |
ixia-c-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.325 |
ixia-c-ixhw-server | 0.12.2-2 |
ixia-c-operator | 0.3.4 |
ixia-c-gnmi-server | 1.12.4 |
ixia-c-one | 0.0.1-4435 |
Bug Fix(s)
set_config
fails withunsuccessful Response: RX runtime not configured for port:
if large port testbed is used on subsequent test runs is fixed.
Known Issues
- Supported value for
flows[i].metrics.latency.mode
iscut_through
. - The metric
loss
in flow metrics is currently not supported. - When flow transmit is started, transmission will be restarted on any existing flows already transmitting packets.
- #118
Release v0.0.1-4399
About
This build includes new features.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.12.1 |
snappi | 0.12.1 |
gosnappi | 0.12.1 |
ixia-c-controller | 0.0.1-4399 |
ixia-c-traffic-engine | 1.6.0.35 |
ixia-c-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.320 |
ixia-c-ixhw-server | 0.12.1-2 |
ixia-c-operator | 0.3.4 |
ixia-c-gnmi-server | 1.12.2 |
ixia-c-one | 0.0.1-4399 |
` |
Release Feature(s)
- Support for deprecated control, action and update APIs (
set_transmit_state
,set_link_state
,set_capture_state
,update_flows
,set_route_state
,send_ping
,set_protocol_state
,set_device_state
) have been removed. Please use followingset_control_state
,set_control_action
andupdate_config
APIs instead of the previous ones. Please refer to go utils and python utils for further details usage. - Most properties in OTG with integer data type have been assigned correct integer format (from
uint32
,uint64
,int32
andint64
). Please click here to examine all changes. - Once you upgrade the new ixia-c release, in addition to removing the deprecated APIs from the test programs, data types of some variables in the test programs might need to be changed to avoid compilation errors.
Known Issues
- Supported value for
flows[i].metrics.latency.mode
iscut_through
. - The metric
loss
in flow metrics is currently not supported. - When flow transmit is started, transmission will be restarted on any existing flows already transmitting packets.
- #118
Release v0.0.1-4306
About
This build includes stability fixes.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.11.11 |
snappi | 0.11.17 |
gosnappi | 0.11.17 |
ixia-c-controller | 0.0.1-4306 |
ixia-c-traffic-engine | 1.6.0.35 |
ixia-c-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.318 |
ixia-c-ixhw-server | 0.11.11-2 |
ixia-c-operator | 0.3.4 |
ixia-c-gnmi-server | 1.11.17 |
ixia-c-one | 0.0.1-4306 |
` |
Known Issues
- Supported value for
flows[i].metrics.latency.mode
iscut_through
. - The metric
loss
in flow metrics is currently not supported. - When flow transmit is started, transmission will be restarted on any existing flows already transmitting packets.
- #118
Release v0.0.1-4167
About
This build includes new features.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.11.10 |
snappi | 0.11.16 |
gosnappi | 0.11.16 |
ixia-c-controller | 0.0.1-4167 |
ixia-c-traffic-engine | 1.6.0.35 |
ixia-c-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.316 |
ixia-c-ixhw-server | 0.11.10-13 |
ixia-c-operator | 0.3.4 |
ixia-c-gnmi-server | 1.11.16 |
ixia-c-one | 0.0.1-4167 |
Release Feature(s)
- Enabling
metric_tags
for egress tracking is now also supported on ipv6.src/dst, ipv6.traffic_class, ipv6.flow_label and ipv6.payload_length. [Ixia-C]eth := flow.EgressPacket().Add().Ethernet() ipv6 := flow.EgressPacket().Add().Ipv6() ipv6Tag := ipv6.Dst().MetricTags().Add() ipv6Tag.SetName("flow_ipv6_dst") ipv6Tag.SetOffset(120) ipv6Tag.SetLength(8)
- Support is available in gNMI to fetch the drill-down statistics for egress tracking as follows [Ixia-C] details:
1. Flow level metrics + Tagged Metrics: example path: "flows/flow[name=f1]“ 2. Only Flow level metrics: example path: "flows/flow[name=f1]/state“ 3. Only Tagged metrics example path: "flows/flow[name=f1]/tagged-metrics“ 4. Filtered Tagged metrics: example path: "flows/flow[name=f1]/tagged-metrics/tagged-metric[name-value-pairs=flow_ipv6_dst=0x2]”
Bug Fix(s)
- For
flow.duration.continuous
type of traffic in Ixia-C, intermittent issue where last few packets in a traffic flow were not accounted for inflow_metrics.frames_rx
statistics after stopping a flow is fixed. - Proper error mesage is propagated to user if user has used community edition of Ixia-C (instead of licensed edition) and invoked any API/Configuration not supported by it.
example:Device configuration is not supported in free version of controller.
Known Issues
- Supported value for
flows[i].metrics.latency.mode
iscut_through
. - The metric
loss
in flow metrics is currently not supported. - When flow transmit is started, transmission will be restarted on any existing flows already transmitting packets.
- #118