Releases: open-traffic-generator/ixia-c
Release v0.0.1-4013
About
This build includes new features.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.11.8 |
snappi | 0.11.14 |
gosnappi | 0.11.14 |
ixia-c-controller | 0.0.1-4013 |
ixia-c-traffic-engine | 1.6.0.35 |
ixia-c-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.299 |
ixia-c-ixhw-server | 0.11.8-8 |
ixia-c-operator | 0.3.1 |
ixia-c-gnmi-server | 1.11.13 |
ixia-c-one | 0.0.1-4013 |
Release Features(s)
- Egress tracking now also supports tracking for
vlan
,mpls
packet headers. - Support added in
ixia-c-gnmi-server
for fetching Latency measurements.- User can enable latency measurement by setting
f1.Metrics().SetEnable(true).Latency().SetEnable(true)
.- Only
cut_through
latency mode is supported.
- Only
- User can fetch latency measurements using given models-yang path.
module: open-traffic-generator-flow +--rw flows +--ro flow* [name] +--ro name -> ../state/name +--ro state | .... | .... | +--ro minimum-latency? otg-types:timeticks64 | +--ro maximum-latency? otg-types:timeticks64 | +--ro average-latency? otg-types:timeticks64 | .... | ....
- User can enable latency measurement by setting
Bug Fix(s)
- Intermittent crash in ixia-c-controller while fetching
flow_metrics
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-3927
About
This build includes new features.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.11.8 |
snappi | 0.11.14 |
gosnappi | 0.11.14 |
ixia-c-controller | 0.0.1-3927 |
ixia-c-traffic-engine | 1.6.0.35 |
ixia-c-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.298 |
ixia-c-ixhw-server | 0.11.8-1 |
ixia-c-operator | 0.3.1 |
ixia-c-gnmi-server | 1.11.10 |
ixia-c-one | 0.0.1-3927 |
Release Features(s)
-
A new property
egress_packet
inside flow has been introduced to configure expected packet shape as it is received on the test port.
go eth := flow.EgressPacket().Add().Ethernet() ipv4 := flow.EgressPacket().Add().Ipv4()
-
A new property
metric_tags
has been introduced for fields inside headers configured inegress_packet
to enable tracking metrics for each applicable value corresponding to a portion of or all bits inside the field.ipv4Tag := ipv4.Dst().MetricTags().Add() ipv4Tag.SetName("flow_ipv4_dst") ipv4Tag.SetOffset(24) ipv4Tag.SetLength(8)
-
As of this release, enabling metric_tags is only supported on ethernet.src/dst, ipv4.src/dst, ipv4.tos. Support for more fields shall be added in upcoming releases.
-
Limitations:
- The total number of tracking bits available on an ixia-c Rx port is 12 bits. Out of these some of the bits are needed for tracking flows, example 2 flows need 1 bit, 4 flows need 2 bits, 8 flows need 3 bits etc. The sum of
metric_tag.length
for each field inside each header configured inegress_packet
cannot exceed the remaining bits available on the Rx port. - The total number of tracking fields that can be configured across a set of flows which have the same Rx port, is two.
- The total number of tracking bits available on an ixia-c Rx port is 12 bits. Out of these some of the bits are needed for tracking flows, example 2 flows need 1 bit, 4 flows need 2 bits, 8 flows need 3 bits etc. The sum of
-
-
A new property is introduced in
get_metrics.flow
to fetch tagged metrics.
- User can set
get_metrics.flow.tagged_metrics.include=false
not to includetagged_metrics
in theflow_metrics
response. - Specific
tagged_metrics
can be fetched by settingget_metrics.flow.tagged_metrics.filters[i].name
.
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-3889
About
This build includes new features.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.11.4 |
snappi | 0.11.6 |
gosnappi | 0.11.6 |
ixia-c-controller | 0.0.1-3889 |
ixia-c-traffic-engine | 1.6.0.35 |
ixia-c-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.290 |
ixia-c-ixhw-server | 0.11.4-1 |
ixia-c-operator | 0.3.1 |
ixia-c-gnmi-server | 1.11.5 |
ixia-c-one | 0.0.1-3889 |
Features(s)
-
All API response errors over gRPC and HTTP transport can now be inspected like so:
# snippet of error handling in snappi try: # call set config api.set_config(payload) except Exception as e: err = api.from_exception(e) # helper function to parse exception if err is not None: # exception was of otg error format print(err.code) print(err.errors) else: # some other exception print(e)
// gosnappi snippet for error handling resp, err := api.SetConfig(config) if err != nil { // helper function to parse error // retuns a bool with err, indicating wheather the error was of otg error format errSt, ok := api.FromError(err) if ok { fmt.Println(errSt.Code()) if errSt.errSt.HasKind() { fmt.Println(errSt.Kind()) } fmt.Println(errSt.Errors()) } else { fmt.Println(err.Error()) } }
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-3865
About
This build includes new features.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.11.1 |
snappi | 0.11.1 |
gosnappi | 0.11.1 |
ixia-c-controller | 0.0.1-3865 |
ixia-c-traffic-engine | 1.6.0.35 |
ixia-c-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.283 |
ixia-c-ixhw-server | 0.11.1-1 |
ixia-c-operator | 0.3.1 |
ixia-c-gnmi-server | 1.11.1 |
ixia-c-one | 0.0.1-3865 |
Features(s)
- Warning messages shall now be automatically printed on STDOUT if a property or an API with status deprecated or under-review is exercised in
snappi
/gosnappi
. This may also lead to linters raising deprecation error. - New API endpoints
/control/state
and/control/action
have been exposed consolidating pre-existing API endpoints inside/control/
(now deprecated) in order to reduce API surface and introducing clean organization. Please see snappi-tests utils for usage. - API endpoints
/results/*
have now been renamed to/monitor/*
.
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-3841
Announcement
ixia-c
container images are hosted on GitHub Container Registry, We stopped publishing ixia-c
container images to DockerHub.
About
This build includes new features.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.10.12 |
snappi | 0.10.9 |
gosnappi | 0.10.9 |
ixia-c-controller | 0.0.1-3841 |
ixia-c-traffic-engine | 1.6.0.35 |
ixia-c-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.279 |
ixia-c-ixhw-server | 0.10.12-2 |
ixia-c-operator | 0.3.1 |
ixia-c-gnmi-server | 1.10.19 |
ixia-c-one | 0.0.1-3841 |
Features(s)
- API version compatibility check is now automatically performed between ixia-c containers upon API calls to
ixia-c-controller
. It can be disabled by bootingixia-c-controller
container with--disable-version-check
flag. - API version compatibility check can now be automatically performed between
snappi
/gosnappi
and ixia-c-controller upon API calls by enabling version check flag in API handle like so:- gosnappi
api := gosnappi.NewApi() api.SetVersionCompatibilityCheck(true)
- snappi
In upcoming releases, this will be enabled by default.api = snappi.api(version_check=True)
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-3807
Announcement
ixia-c
container images are hosted on GitHub Container Registry, We stopped publishing ixia-c
container images to DockerHub.
About
This build contains bug fixes.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.10.9 |
snappi | 0.10.7 |
gosnappi | 0.10.7 |
ixia-c-controller | 0.0.1-3807 |
ixia-c-traffic-engine | 1.6.0.30 |
ixia-c-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.271 |
ixia-c-ixhw-server | 0.10.7-8 |
ixia-c-operator | 0.3.1 |
ixia-c-gnmi-server | 1.10.14 |
ixia-c-one | 0.0.1-3807 |
Bug Fix(s)
- Concurrent API calls (where at least one call was
set_config
) toixia-c-controller
was resulting in crash.
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-3768
Announcement
ixia-c
container images are hosted on GitHub Container Registry, We stopped publishing ixia-c
container images to DockerHub.
About
This build contains bug fixes.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.10.7 |
snappi | 0.10.5 |
gosnappi | 0.10.5 |
ixia-c-controller | 0.0.1-3768 |
ixia-c-traffic-engine | 1.6.0.29 |
ixia-c-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.271 |
ixia-c-ixhw-server | 0.10.7-2 |
ixia-c-operator | 0.3.1 |
ixia-c-gnmi-server | 1.10.8 |
ixia-c-one | 0.0.1-3768 |
Bug Fix(s)
- Issue where TCP header length was not set correctly is fixed. #117
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-3724
Announcement
ixia-c
container images are hosted on GitHub Container Registry, We stopped publishing ixia-c
container images to DockerHub.
About
This build contains bug fixes.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.10.6 |
snappi | 0.10.4 |
gosnappi | 0.10.4 |
ixia-c-controller | 0.0.1-3724 |
ixia-c-traffic-engine | 1.6.0.24 |
ixia-c-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.256 |
ixia-c-ixhw-server | 0.10.6-1 |
ixia-c-operator | 0.3.1 |
ixia-c-gnmi-server | 1.10.6 |
ixia-c-one | 0.0.1-3722 |
Bug Fix(s)
- Payload size field in all inner headers for tunneling protocols do not take into account inner FCS is fixed. #112
Known Issues
- 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.
Known Limitations
- 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.
Release v0.0.1-3698
Announcement
ixia-c
container images is hosted on GitHub Container Registry, We stopped publishing ixia-c
container images to DockerHub.
About
This build contains stability fixes.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.10.5 |
snappi | 0.10.3 |
gosnappi | 0.10.3 |
ixia-c-controller | 0.0.1-3698 |
ixia-c-traffic-engine | 1.6.0.19 |
ixia-c-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.252 |
ixia-c-operator | 0.3.1 |
ixia-c-gnmi-server | 1.10.5 |
ixia-c-one | 0.0.1-3698 |
Known Issues
- 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.
Known Limitations
- 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.
Release v0.0.1-3662
Announcement
ixia-c
container images is hosted on GitHub Container Registry. However we will continue publishing ixia-c
container images to DockerHub until 18th November, 2022.
Build Details
Component | Version |
---|---|
Open Traffic Generator API | 0.9.10 |
snappi | 0.9.8 |
gosnappi | 0.9.8 |
ixia-c-controller | 0.0.1-3662 |
ixia-c-traffic-engine | 1.6.0.19 |
ixia-c-app-usage-reporter | 0.0.1-37 |
ixia-c-protocol-engine | 1.00.0.243 |
ixia-c-operator | 0.3.0 |
ixia-c-gnmi-server | 1.9.9 |
ixia-c-one | 0.0.1-3662 |
Features(s)
ixia-c-controller
now runs with a non-root user inside the container (instead of root user previously)ixia-c-controller
now listens on non-privileged HTTPs port 8443 (instead of 443 previously)
Known Issues
- 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.
Known Limitations
- 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.