From 5729103b3b284a9a673032b66ce3aa8c1d88d440 Mon Sep 17 00:00:00 2001 From: Chris Date: Tue, 20 Feb 2024 17:34:15 -0500 Subject: [PATCH 01/22] adding DNAT --- docs/config_nat.md | 78 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 78 insertions(+) diff --git a/docs/config_nat.md b/docs/config_nat.md index 13c24f22b8..1df80ec3b0 100644 --- a/docs/config_nat.md +++ b/docs/config_nat.md @@ -168,6 +168,84 @@ For details about command output, refer to the [`show sessions`](cli_reference.m | ------- | ------------ | | 6.2.0 | Static NAT Feature Introduced | +## Dynamic Source NAT + +Dynamic Source NAT translates multiple source IP addresses into a smaller pool of translated addresses and dynamic ports, which conserves public IP address space and provides the flexibility to source NAT a specific IP range. This supports scaling up sessions for the internal service. For example, in a corporate office with a SIP phone service, where all phones have different IPs on port 5060, these internal IP addresses are source NAT’ed to a single external IP address. It may also provide solutions for IP address conflicts, but because it is not mapping NAT one-to-one, it is not required to facilitate the destination NAT mapping for network connections from the external client to the internal client. + +Consider the following table and diagram, similar to the example earlier focusing on a company acquisition, where spk-lan2 network, is overlapping, or not routable in Corp and Internet. + +The Dynamic Source NAT challenge is illustrated in scenarios #2 and #4, where multiple clients of IP subnet 192.168.1.0/24, from spk-lan2 are running same application on port 1111, but given only one IP address, 172.16.128.10, to source NAT out. + +images here + +By applying Dynamic Source NAT configuration to the spk-lan2 interface, the 192.168.1.0/24 subnet can be mapped to the single IP address subnet 172.16.128.10/32, with dynamically allocated ports. This allows the SSR to dynamically build a many-to-one source NAT mapping. + +Examples: +In scenario #2 above, sessions from an application using port 1111 are initiated from multiple clients of the spk-lan2 interface, to a client of hub-lan1 on 10.10.10.10. The first client at host 192.168.1.10 and port 1111 is assigned a source NAT of 172.16.128.10:1653 where port 1653 is allocated dynamically. The second client at 192.168.1.11 with port 1111 is allocated a dynamic source NAT of 172.16.128.10:1654. + +Scenario #4 above is similar, except the target connections are to the client at the spk-lan2 interface using 172.16.129.10 which has been mapped by Static NAT. The same Dynamic Source NAT processes from Senario #2 are applied here. + +The following is the PCLI router configuration for both the above use cases. Packets going through spk-lan2 within the 192.168.1.0/24 domain will be source-natted to 172.16.128.10/32. + +``` +config + authority + router spoke + node node1-spoke + device-interface spk-lan2 + network-interface spk-lan2 + dynamic-source-nat 192.168.1.0/24 + local-ip 192.168.1.0/24 + remote-ip 172.16.128.10/32 + exit + exit + exit + exit + exit + exit +exit +``` + +Sample GUI Configuration: +`network-interface` + +`dynamic-source-nat` + +Commands + +network-interface has the following commands added: + +`dynamic-source-nat`: Defines the prefixes that need to be dynamically source natted for packets ingressing this interface. + `local-ip`: For packets ingressing this interface, the IP which will be source natted to remote-ip IP. + `remote-ip`: For packets ingressing this interface, the IP to which the local-ip IP will be source natted. + +`show network-interface source-nat-rules detail`(router) + +``` +admin@combo-east-1.RTR_EAST_COMBO# show network-interface source-nat-rules name ingress-intf detail +Thu 2024-02-08 18:54:48 UTC +✔ Retrieving source NAT rules... + +=========== =============== ================= ================== ========== ======================== ========= ============= ============= ============== ================ ============== + Direction Type From To Protocol Key State Total Ports Ports In Db Ports In Mem Ports Released Ports In Use +=========== =============== ================= ================== ========== ======================== ========= ============= ============= ============== ================ ============== + ingress dynamic 172.16.1.0/24 192.168.5.120/32 tcp 2/1/1/192.168.5.120/6 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.0/24 192.168.5.120/32 udp 2/1/1/192.168.5.120/17 Standby 49151 48151 999 0 1 + ingress dynamic 172.16.1.0/24 192.168.5.120/32 icmp 2/1/1/192.168.5.120/1 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.202/31 192.168.6.202/32 tcp 2/1/1/192.168.6.202/6 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.202/31 192.168.6.202/32 udp 2/1/1/192.168.6.202/17 Standby 49151 48151 998 0 2 + ingress dynamic 172.16.1.202/31 192.168.6.202/32 icmp 2/1/1/192.168.6.202/1 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.204/31 192.168.7.204/32 tcp 2/1/1/192.168.7.204/6 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.204/31 192.168.7.204/32 udp 2/1/1/192.168.7.204/17 Standby 49151 48151 998 0 2 + ingress dynamic 172.16.1.204/31 192.168.7.204/32 icmp 2/1/1/192.168.7.204/1 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.206/31 192.168.8.206/32 tcp 2/1/1/192.168.8.206/6 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.206/31 192.168.8.206/32 udp 2/1/1/192.168.8.206/17 Standby 49151 48151 999 0 1 + ingress dynamic 172.16.1.206/31 192.168.8.206/32 icmp 2/1/1/192.168.8.206/1 Standby 49151 48151 1000 0 0 + ingress bidirectional 172.16.1.204/30 192.168.9.200/30 n/a n/a n/a n/a n/a n/a n/a n/a + +Completed in 0.05 seconds +``` + ## NAT Pools NAT pools are a construct that allow for the use of IP and port ranges to be shared across one or more network-interfaces for either source or destination NATing capabilities. From c532baf83d18fd9ec6bdc573fd69097de7fce659 Mon Sep 17 00:00:00 2001 From: Chris Date: Wed, 21 Feb 2024 12:29:29 -0500 Subject: [PATCH 02/22] adding Dynamic Source NAT info and reorganizing the NAT section of the docs. --- docs/config_dnat.md | 77 ++++++ docs/config_nat.md | 306 ------------------------ docs/config_nat_pools.md | 64 +++++ docs/config_source-dest_nat.md | 63 +++++ docs/config_static_nat.md | 109 +++++++++ docs/ts_nat_troubleshooting.md | 142 +++++++++++ sidebars.js | 12 +- static/img/dnat_gui_config.png | Bin 0 -> 17521 bytes static/img/dnat_net-intf_gui_config.png | Bin 0 -> 17513 bytes static/img/dnat_netmap.png | Bin 0 -> 19075 bytes static/img/dnat_scenario_table.png | Bin 0 -> 35571 bytes 11 files changed, 466 insertions(+), 307 deletions(-) create mode 100644 docs/config_dnat.md delete mode 100644 docs/config_nat.md create mode 100644 docs/config_nat_pools.md create mode 100644 docs/config_source-dest_nat.md create mode 100644 docs/config_static_nat.md create mode 100644 docs/ts_nat_troubleshooting.md create mode 100644 static/img/dnat_gui_config.png create mode 100644 static/img/dnat_net-intf_gui_config.png create mode 100644 static/img/dnat_netmap.png create mode 100644 static/img/dnat_scenario_table.png diff --git a/docs/config_dnat.md b/docs/config_dnat.md new file mode 100644 index 0000000000..b95c326484 --- /dev/null +++ b/docs/config_dnat.md @@ -0,0 +1,77 @@ +--- +title: Dynamic Source NAT +sidebar_label: Dynamic Source NAT +--- + +## Dynamic Source NAT + +Dynamic Source NAT translates multiple source IP addresses into a smaller pool of translated addresses and dynamic ports, which conserves public IP address space and provides the flexibility to source NAT a specific IP range. This supports scaling up sessions for an internal service. For example, in a corporate office with a SIP phone service where all phones have different IPs on port 5060, these internal IP addresses are source NAT’ed to a single external IP address. + +Dynamic Source NAT may also provide solutions for IP address conflicts, but because it is not mapping NAT one-to-one, it is not required to facilitate the destination NAT mapping for network connections from the external client to the internal client. + +Consider the following scenario, similar to the Static NAT example focusing on a company acquisition, where the `spk-lan2` network is overlapping and not routable in `Corp` and `Internet`. + +![Static Nat Diagram](/img/static_nat_example.png) + +The Dynamic Source NAT challenge is illustrated in scenarios #2 and #4 below, where multiple clients of IP subnet 192.168.1.0/24, from `spk-lan2` are running same application on port 1111, but given only one IP address, 172.16.128.10, to source NAT out. + +| Scenario | Source | Destination | Translation Required | +| --- | --- | --- | --- | +| 2 | 192.168.1.10:1111 @ spk-lan2
192.168.1.11:1111 @ spk-lan2 | 10.10.10.10:xxxx @ hub-lan1 | 172.16.128.10:1653 -> 10.10.10.10:xxxx
172.16.128.10:1654 -> 10.10.10.10:xxxx | +| 4 | 192.168.1.10:1111 @ spk-lan2
192.168.1.11:1111 @ spk-lan2 | 172.16.129.10:* @spk-lan1 | 172.16.128.10:1653 -> 172.16.129.10:xxxx
172.16.128.10:1654 -> 172.16.129.10:xxxx | + +By applying Dynamic Source NAT configuration to the `spk-lan2` interface, the `192.168.1.0/24` subnet can be mapped to the single IP address and subnet `172.16.128.10/32`, with dynamically allocated ports. This allows the SSR to dynamically build a many-to-one source NAT mapping. + +### Configuration + +In scenario #2, sessions from an application using port 1111 are initiated from multiple clients of the spk-lan2 interface, to a client of hub-lan1 on 10.10.10.10. The first client at host 192.168.1.10 and port 1111 is assigned a source NAT of 172.16.128.10:1653 where port 1653 is allocated dynamically. The second client at 192.168.1.11 with port 1111 is allocated a dynamic source NAT of 172.16.128.10:1654. + +Scenario #4 is similar, except the target connections are to the client at the `spk-lan1` interface using 172.16.129.10 which has been mapped by Static NAT. The same Dynamic Source NAT processes from Senario #2 are applied here. + +The following is the router configuration for both the above use cases. Packets going through `spk-lan2` within the 192.168.1.0/24 domain will be source-natted to 172.16.128.10/32. + +#### PCLI Configuration + +``` +config + authority + router spoke + node node1-spoke + device-interface spk-lan2 + network-interface spk-lan2 + dynamic-source-nat 192.168.1.0/24 + local-ip 192.168.1.0/24 + remote-ip 172.16.128.10/32 + exit + exit + exit + exit + exit + exit +exit +``` + +#### Sample GUI Configuration: + +Network Interface Configuration + +![Network Interface configuration](/img/dnat_net-intf_gui_config.png) + +Dynamic Source NAT Configuration + +![Dynamic Source NAT Configuration](/img/dnat_gui_config.png) + +### Configuration Commands + +Dynamic Source NAT is configured from the network-interface using the following commands: + +`dynamic-source-nat`: Defines the prefixes that need to be dynamically source natted for packets ingressing this interface. + +- `local-ip`: For packets ingressing this interface, the IP that is source NAT'ed to the `remote-ip`. +- `remote-ip`: For packets ingressing this interface, the IP where the `local-ip` will be source NAT'ed. + +For additional information refer to [`dynamic-source-nat`] in the Configuration Command Reference Guide. + +### Show Commands + +The `show network-interface source-nat-rules detail` is available on the router or the conductor and will display brief or detailed information for NAT configurations. Please see the [NAT Troubleshooting](ts_nat_troubleshooting) pages for information about the `source-nat-rules` subcommand. \ No newline at end of file diff --git a/docs/config_nat.md b/docs/config_nat.md deleted file mode 100644 index 1df80ec3b0..0000000000 --- a/docs/config_nat.md +++ /dev/null @@ -1,306 +0,0 @@ ---- -title: Network Address Translation (NAT) -sidebar_label: NAT ---- -## Source NAT -Source NAT can be enabled on `authority > router > node > network-interface`. When enabling `source-nat` on a network-interface, all traffic egressing the interface will be network address and port translated (NAPT) to that of the address on the interface. - -:::note -The port range is not configurable and ranges between 16384 to 65534, allowing for 49,150 concurrent sessions per interface. -::: - -``` -admin@gouda.novigrad# show config running authority router novigrad node gouda device-interface wan network-interface wan-interface - -config - - authority - - router novigrad - name novigrad - - node gouda - name gouda - - device-interface wan - name wan - - network-interface wan-interface - name wan-interface - global-id 1 - vlan 0 - type external - conductor false - - neighborhood internet - name internet - exit - inter-router-security interfabric - prioritization-mode local - source-nat true - mtu 1500 - enforced-mss disabled - icmp allow - hostname gouda.novigrad.net - multicast-listeners automatic - multicast-report-proxy false - dhcp v4 - exit - exit - exit - exit - exit -exit -``` - -If support for more than 49,150 concurrent sessions per interface is needed, you can configure a _NAT Pool_ or add additional `address`es to the network-interface, expanding the source NAT capacity. - -When multiple addresses are configured, utilizing `source-nat`, the second address configured will only be utilized once the first is fully exhausted; so on and so forth. Once the next configured address starts being utilized, it will remain in use until exhausted. - -## Destination NAT - -Static desination network address translation can be performed by configuring a `service-route > nat-target`. It is common to leverage the public address of the router for internal services, such as VPN. Traffic destined to the SSR, configured as a _service_ with an _address_ that matches that of the public-facing network-interface is then NATed to an internal private address on the LAN for the application. This setting only performs address translation and does not modify the port. - -## Static NAT - -SSR supports source NAT pool configurations at interface and service-route level as described in [Static NAT Bindings](#static-nat-bindings). However, this is not always sufficient to enable simple configuration for static bidirectional NAT between two same-sized subnets. - -Static NAT defines a one-to-one mapping from one IP subnet to another IP subnet. The mapping includes source IP address translation in one direction and destination IP address translation in the reverse direction. In cases where IP address overlapping is found, such as when merging networks (for example, a corporate acquisition and merger) this simple configuration change is significantly less work than changing all the local IP addresses. The diagram below illustrates this example. - -![Static Nat Diagram](/img/static_nat_example.png) - -The `spk-lan2` network-interface is not routable (cannot send or receive traffic) in the `Corp` and `Internet` networks. The client in `spk-lan2` has a local IP within the `192.168.1.0/24` subnet and overlaps with another client from `Corp` in `spk-lan1`. This will cause problems for any sessions between `hub-lan1` or `spk-lan1` to `spk-lan2`. By configuring `bidirectional-nat` on `spk-lan1` and `spk-lan2`, the two `192.168.1.0/24` subnets are mapped to `172.16.128.0/24` and `172.16.129.0/24` respectively and differentiate themselves on the hub router. - -`bidirectional-nat` provides value in two ways: -- NAT an unroutable private IP to a routable public IP -- NAT duplicate private IPs (on different routers/networks) to different public IPs to provide differentiation on the receiving end - -#### Example - -``` -config - authority - router spoke - node node1-spoke - device-interface spk-lan2 - network-interface spk-lan2 - bidirectional-nat 192.168.1.0/24 - local-ip 192.168.1.0/24 - remote-ip 172.16.128.0/24 - exit - exit - exit - - device-interface spk-lan1 - network-interface spk-lan1 - bidirectional-nat 192.168.1.0/24 - local-ip 192.168.1.0/24 - remote-ip 172.16.129.0/24 - exit - exit - exit - exit - exit - exit -exit - -``` - -### Non-SVR Traffic - -In order for non-SVR traffic (for example, LAN-to-LAN traffic traversing a single SSR) to take advantage of static-NAT addressing, you must disable egress source-nat at the service level by setting `service > source-nat` to `disabled` as shown below. - -``` -authority - service LAN-to-LAN - name LAN-to-LAN - description "LAN-to-LAN non-SVR traffic traversing a single SSR router" - source-nat disabled - scope private - security aes1 - address - access-policy - source - permission allow - exit - exit -exit -``` - -### Using the GUI - -Set the local and remote IP addresses under Authority > Router > Node > Device Interface > Network Interface. - -![Network Interface](/img/static_nat_gui_net-intf.png) - -![Bidirectional NAT Config](/img/static_nat_gui_nat-config.png) - -### Show Commands - -For details about command output, refer to the [`show sessions`](cli_reference.md#show-sessions) and [`show sessions by-id`](cli_reference.md#show-sessions-by-id) commands. - -#### Source NAT -- On the session ingress node, the `show sessions by-id` output has an Ingress Source NAT field where the source-nat type, NAT’d source address, NAT’d port, and protocol are displayed. - -![Session Ingress](/img/source-nat1.png) - -- On the session egress node the `show sessions by-id` output has an Ingress Source NAT field where the source-nat type, NAT’d source address, NAT’d port, and protocol are displayed. - -![Session Egress](/img/source-nat2.png) - -- The `show sessions` output has `NAT IP` and `NAT Port` columns where the NAT’d source address and NAT’d source port are displayed. - -![NAT IP and Port](/img/source-nat3.png) - -#### Destination NAT - -- On the session egress node the `show sessions by-id` output shows the NAT’d destination address in the Forward Flow `NextHop` and Reverse Flow `src ip` fields. - -![Destination forward flow](/img/dest-nat1.png) - -- The `show sessions` output reverse flow `src ip `column also shows the NAT’d destination address. - -![Destination Reverse Flow Source IP](/img/dest-nat2.png) - -#### Version History - -| Release | Modification | -| ------- | ------------ | -| 6.2.0 | Static NAT Feature Introduced | - -## Dynamic Source NAT - -Dynamic Source NAT translates multiple source IP addresses into a smaller pool of translated addresses and dynamic ports, which conserves public IP address space and provides the flexibility to source NAT a specific IP range. This supports scaling up sessions for the internal service. For example, in a corporate office with a SIP phone service, where all phones have different IPs on port 5060, these internal IP addresses are source NAT’ed to a single external IP address. It may also provide solutions for IP address conflicts, but because it is not mapping NAT one-to-one, it is not required to facilitate the destination NAT mapping for network connections from the external client to the internal client. - -Consider the following table and diagram, similar to the example earlier focusing on a company acquisition, where spk-lan2 network, is overlapping, or not routable in Corp and Internet. - -The Dynamic Source NAT challenge is illustrated in scenarios #2 and #4, where multiple clients of IP subnet 192.168.1.0/24, from spk-lan2 are running same application on port 1111, but given only one IP address, 172.16.128.10, to source NAT out. - -images here - -By applying Dynamic Source NAT configuration to the spk-lan2 interface, the 192.168.1.0/24 subnet can be mapped to the single IP address subnet 172.16.128.10/32, with dynamically allocated ports. This allows the SSR to dynamically build a many-to-one source NAT mapping. - -Examples: -In scenario #2 above, sessions from an application using port 1111 are initiated from multiple clients of the spk-lan2 interface, to a client of hub-lan1 on 10.10.10.10. The first client at host 192.168.1.10 and port 1111 is assigned a source NAT of 172.16.128.10:1653 where port 1653 is allocated dynamically. The second client at 192.168.1.11 with port 1111 is allocated a dynamic source NAT of 172.16.128.10:1654. - -Scenario #4 above is similar, except the target connections are to the client at the spk-lan2 interface using 172.16.129.10 which has been mapped by Static NAT. The same Dynamic Source NAT processes from Senario #2 are applied here. - -The following is the PCLI router configuration for both the above use cases. Packets going through spk-lan2 within the 192.168.1.0/24 domain will be source-natted to 172.16.128.10/32. - -``` -config - authority - router spoke - node node1-spoke - device-interface spk-lan2 - network-interface spk-lan2 - dynamic-source-nat 192.168.1.0/24 - local-ip 192.168.1.0/24 - remote-ip 172.16.128.10/32 - exit - exit - exit - exit - exit - exit -exit -``` - -Sample GUI Configuration: -`network-interface` - -`dynamic-source-nat` - -Commands - -network-interface has the following commands added: - -`dynamic-source-nat`: Defines the prefixes that need to be dynamically source natted for packets ingressing this interface. - `local-ip`: For packets ingressing this interface, the IP which will be source natted to remote-ip IP. - `remote-ip`: For packets ingressing this interface, the IP to which the local-ip IP will be source natted. - -`show network-interface source-nat-rules detail`(router) - -``` -admin@combo-east-1.RTR_EAST_COMBO# show network-interface source-nat-rules name ingress-intf detail -Thu 2024-02-08 18:54:48 UTC -✔ Retrieving source NAT rules... - -=========== =============== ================= ================== ========== ======================== ========= ============= ============= ============== ================ ============== - Direction Type From To Protocol Key State Total Ports Ports In Db Ports In Mem Ports Released Ports In Use -=========== =============== ================= ================== ========== ======================== ========= ============= ============= ============== ================ ============== - ingress dynamic 172.16.1.0/24 192.168.5.120/32 tcp 2/1/1/192.168.5.120/6 Standby 49151 48151 1000 0 0 - ingress dynamic 172.16.1.0/24 192.168.5.120/32 udp 2/1/1/192.168.5.120/17 Standby 49151 48151 999 0 1 - ingress dynamic 172.16.1.0/24 192.168.5.120/32 icmp 2/1/1/192.168.5.120/1 Standby 49151 48151 1000 0 0 - ingress dynamic 172.16.1.202/31 192.168.6.202/32 tcp 2/1/1/192.168.6.202/6 Standby 49151 48151 1000 0 0 - ingress dynamic 172.16.1.202/31 192.168.6.202/32 udp 2/1/1/192.168.6.202/17 Standby 49151 48151 998 0 2 - ingress dynamic 172.16.1.202/31 192.168.6.202/32 icmp 2/1/1/192.168.6.202/1 Standby 49151 48151 1000 0 0 - ingress dynamic 172.16.1.204/31 192.168.7.204/32 tcp 2/1/1/192.168.7.204/6 Standby 49151 48151 1000 0 0 - ingress dynamic 172.16.1.204/31 192.168.7.204/32 udp 2/1/1/192.168.7.204/17 Standby 49151 48151 998 0 2 - ingress dynamic 172.16.1.204/31 192.168.7.204/32 icmp 2/1/1/192.168.7.204/1 Standby 49151 48151 1000 0 0 - ingress dynamic 172.16.1.206/31 192.168.8.206/32 tcp 2/1/1/192.168.8.206/6 Standby 49151 48151 1000 0 0 - ingress dynamic 172.16.1.206/31 192.168.8.206/32 udp 2/1/1/192.168.8.206/17 Standby 49151 48151 999 0 1 - ingress dynamic 172.16.1.206/31 192.168.8.206/32 icmp 2/1/1/192.168.8.206/1 Standby 49151 48151 1000 0 0 - ingress bidirectional 172.16.1.204/30 192.168.9.200/30 n/a n/a n/a n/a n/a n/a n/a n/a - -Completed in 0.05 seconds -``` - -## NAT Pools - -NAT pools are a construct that allow for the use of IP and port ranges to be shared across one or more network-interfaces for either source or destination NATing capabilities. - -### Static NAT bindings -A static NAT binding can be configured by creating an `authority > router > nat-pool` object and assigning it to a network-interface. The following rules and constraints will apply to this configuration: - -* The _nat-pool_ prefix is used to create a N:M mapping. Where each source IP (from an ingress interface) is hashed to an IP address in the nat pool. -* The static _nat-pool_ can only be configured as: - * _ingress-nat-pool_ on a _network-interface_ when peering with another SSR - * *egress-nat-pool* on a _network-interface_ when not performing SVR - * _source-nat-pool_ on a _service-route / next-hop_ -* SSR software will not reply to ARP requests on the pool prefix on the associated interface. Therefore the SSR relies on the pool to be routed to the SSR gateway interface by another mechanism such as static-routes, BGP, etc., by the _next-hop_ in the network. -* Changes to the pool configuration will not affect the existing sessions as it has the potential of cascading effect on the network. These changes will resolve over time as the existing sessions naturally expire. - -The static NAT pool will simply hash the source IP address of incoming packets to the corresponding IP address in the pool. - -``` -nat-pool - name static-pool-1 - type static - address-pool - address 10.10.10.10/31 - -network-interface - name test-lan - address - ip-address 192.168.10.1 - prefix-length 24 - ingress-source-nat-pool static-pool-1 -``` - -In the configuration snippet above, the _192.168.10.0/24_ network for the `test-lan` will be source NAT’d to `10.10.10.10/31`. Traffic from an endpoint of source address 192.168.10.10 will be source NAT’d to 10.10.10.10; 192.168.10.11 will be source NAT’d to 10.10.10.11 and so on. Since the NAT in the model relies on a N:M mapping this can only be configured as an _ingress-source-nat-pool_ (on _network-interface_) or as a destination-nat-pool (on _service-route / next-hop_). - -### Shared NAT pools -In some scenarios, it is desirable to share the same NAT pool across services and interfaces. This feature accommodates the same NAT pool to be configured on different interfaces. There are some considerations that should be noted for failure and recovery. - -Flow Move Considerations - -Currently session migration is only supported for SVR sessions. This restriction exists because session migration of a non-SVR session is not guaranteed to terminate on the same server. As a result, the remote server might receive mid flow packets from a different source, resulting in undefined behavior. - -Session Recovery Considerations - -For shared NAT pools provisioned on an HA interface that encounters a failover, the SSR software will put the interface into recovery mode to recover all sessions. At the end of the recovery period all non-discovered ports designed as free are returned to the NAT pool. - -### Tenant filtering -The _nat-pool_ configuration can optionally be provisioned with a list of tenants. When the configuration has _multiple_ IP pools available, the _tenant_ can be used to determine which IP pool will be selected for the source NAT. Absence of a tenant implies that the IP pool is valid for all traffic. The following rules will be applied in order to determine the selection of the NAT pool: - -* The packet has a source tenant associated with it - * If more than one IP pool has a matching tenant, only the first IP pool is used and the hash is applied to create a session. The remainder of the matches are discarded - * If a pool with no tenant is configured - * Same as above - * All IP pools have tenant configured but none of them match the source tenant - * Log the failure, increment stat and drop the packet -* The packet has no source tenant associated with it - * At least one IP pool has no tenant configured to do the source NAT otherwise this will result in the session being dropped - -The tenant matching rules will apply to sub-tenants as well. For example, if an IP pool allows tenant engineering, then traffic with source tenant lab.engineering will also match the pool. diff --git a/docs/config_nat_pools.md b/docs/config_nat_pools.md new file mode 100644 index 0000000000..aa3db9828e --- /dev/null +++ b/docs/config_nat_pools.md @@ -0,0 +1,64 @@ +--- +title: NAT Pools +sidebar_label: NAT Pools +--- + +## NAT Pools + +NAT pools are a construct that allows for the use of IP and port ranges to be shared across one or more network-interfaces for either source or destination NATing capabilities. + +### Static NAT Bindings + +A static NAT binding is configured by creating an `authority > router > nat-pool` object and assigning it to a network-interface. The following rules and constraints apply to this configuration: + +* The _nat-pool_ prefix is used to create a N:M mapping, where each source IP (from an ingress interface) is hashed to an IP address in the nat pool. +* The static _nat-pool_ can only be configured as: + * _ingress-nat-pool_ on a _network-interface_ when peering with another SSR + * *egress-nat-pool* on a _network-interface_ when not performing SVR + * _source-nat-pool_ on a _service-route / next-hop_ +* SSR software will not reply to ARP requests on the pool prefix on the associated interface. The SSR relies on the pool to be routed to the SSR gateway interface by another mechanism such as static-routes, BGP, etc., by the _next-hop_ in the network. +* Changes to the pool configuration will not affect the existing sessions as it has the potential of cascading effect on the network. These changes resolve over time as the existing sessions naturally expire. + +The static NAT pool hashes the source IP address of incoming packets to the corresponding IP address in the pool. + +``` +nat-pool + name static-pool-1 + type static + address-pool + address 10.10.10.10/31 + +network-interface + name test-lan + address + ip-address 192.168.10.1 + prefix-length 24 + ingress-source-nat-pool static-pool-1 +``` + +In the configuration snippet above, the _192.168.10.0/24_ network for the `test-lan` will be source NAT’d to `10.10.10.10/31`. Traffic from an endpoint of source address 192.168.10.10 will be source NAT’d to 10.10.10.10; 192.168.10.11 will be source NAT’d to 10.10.10.11 and so on. Since the NAT in the model relies on a N:M mapping this can only be configured as an _ingress-source-nat-pool_ (on _network-interface_) or as a destination-nat-pool (on _service-route / next-hop_). + +### Shared NAT pools +In some scenarios, it is desirable to share the same NAT pool across services and interfaces. This feature accommodates the same NAT pool to be configured on different interfaces. There are some considerations that should be noted for failure and recovery. + +#### Flow Move Considerations + +Currently session migration is only supported for SVR sessions. This restriction exists because session migration of a non-SVR session is not guaranteed to terminate on the same server. As a result, the remote server might receive mid flow packets from a different source, resulting in undefined behavior. + +#### Session Recovery Considerations + +For shared NAT pools provisioned on an HA interface that encounters a failover, the SSR software will put the interface into recovery mode to recover all sessions. At the end of the recovery period all non-discovered ports designed as free are returned to the NAT pool. + +### Tenant Filtering +The _nat-pool_ configuration can optionally be provisioned with a list of tenants. When the configuration has _multiple_ IP pools available, the _tenant_ can be used to determine which IP pool will be selected for the source NAT. Absence of a tenant implies that the IP pool is valid for all traffic. The following rules will be applied in order to determine the selection of the NAT pool: + +* The packet has a source tenant associated with it: + * If more than one IP pool has a matching tenant, only the first IP pool is used and the hash is applied to create a session. The remainder of the matches are discarded. + * If a pool with no tenant is configured: + * Same as above. + * All IP pools have tenant configured but none of them match the source tenant: + * Log the failure, increment stat and drop the packet. +* The packet has no source tenant associated with it: + * At least one IP pool has no tenant configured to do the source NAT, otherwise this will result in the session being dropped. + +The tenant matching rules apply to sub-tenants as well. For example, if an IP pool allows tenant engineering, then traffic with source tenant `lab.engineering` will also match the pool. diff --git a/docs/config_source-dest_nat.md b/docs/config_source-dest_nat.md new file mode 100644 index 0000000000..923d0f6ed7 --- /dev/null +++ b/docs/config_source-dest_nat.md @@ -0,0 +1,63 @@ +--- +title: Source and Destination NAT +sidebar_label: Source and Destination NAT +--- +## Source NAT +Source NAT can be enabled on `authority > router > node > network-interface`. When enabling `source-nat` on a network-interface, all traffic egressing the interface will be network address and port translated (NAPT) to the address on the interface. + +:::note +The port range is not configurable and ranges between 16384 to 65534, allowing for 49,150 concurrent sessions per interface. +::: + +``` +admin@gouda.novigrad# show config running authority router novigrad node gouda device-interface wan network-interface wan-interface + +config + + authority + + router novigrad + name novigrad + + node gouda + name gouda + + device-interface wan + name wan + + network-interface wan-interface + name wan-interface + global-id 1 + vlan 0 + type external + conductor false + + neighborhood internet + name internet + exit + inter-router-security interfabric + prioritization-mode local + source-nat true + mtu 1500 + enforced-mss disabled + icmp allow + hostname gouda.novigrad.net + multicast-listeners automatic + multicast-report-proxy false + dhcp v4 + exit + exit + exit + exit + exit +exit +``` + +If support for more than 49,150 concurrent sessions per interface is needed, you can configure a [NAT Pool](config_nat_pools) or add additional `addresses` to the `network-interface`, expanding the source NAT capacity. + +When multiple addresses are configured using `source-nat`, the next configured address is utilized **only after the first is fully exhausted**. Each configured address is used until it is exhausted. + +## Destination NAT + +Static desination network address translation can be performed by configuring a `service-route > nat-target`. It is common to leverage the public address of the router for internal services, such as VPN. Traffic destined to the SSR, configured as a _service_ with an _address_ that matches that of the public-facing network-interface is then NATed to an internal private address on the LAN for the application. This setting only performs address translation and does not modify the port. + diff --git a/docs/config_static_nat.md b/docs/config_static_nat.md new file mode 100644 index 0000000000..28622b2249 --- /dev/null +++ b/docs/config_static_nat.md @@ -0,0 +1,109 @@ +--- +title: Static NAT +sidebar_label: Static NAT +--- + +SSR supports source NAT pool configurations at interface and service-route level as described in [Static NAT Bindings](config_nat_pools#static-nat-bindings). However, this is not always sufficient to enable simple configuration for static bidirectional NAT between two same-sized subnets. + +Static NAT defines a one-to-one mapping from one IP subnet to another IP subnet. The mapping includes source IP address translation in one direction and destination IP address translation in the reverse direction. In cases where IP address overlapping is found, such as when merging networks (for example, a corporate acquisition and merger) this simple configuration change is significantly less work than changing all the local IP addresses. The diagram below illustrates this example. + +![Static Nat Diagram](/img/static_nat_example.png) + +The `spk-lan2` network-interface is not routable (cannot send or receive traffic) in the `Corp` and `Internet` networks. The client in `spk-lan2` has a local IP within the `192.168.1.0/24` subnet and overlaps with another client from `Corp` in `spk-lan1`. This will cause problems for any sessions between `hub-lan1` or `spk-lan1` to `spk-lan2`. By configuring `bidirectional-nat` on `spk-lan1` and `spk-lan2`, the two `192.168.1.0/24` subnets are mapped to `172.16.128.0/24` and `172.16.129.0/24` respectively and differentiate themselves on the hub router. + +`bidirectional-nat` provides value in two ways: +- NAT an unroutable private IP to a routable public IP +- NAT duplicate private IPs (on different routers/networks) to different public IPs to provide differentiation on the receiving end + +#### Example + +``` +config + authority + router spoke + node node1-spoke + device-interface spk-lan2 + network-interface spk-lan2 + bidirectional-nat 192.168.1.0/24 + local-ip 192.168.1.0/24 + remote-ip 172.16.128.0/24 + exit + exit + exit + + device-interface spk-lan1 + network-interface spk-lan1 + bidirectional-nat 192.168.1.0/24 + local-ip 192.168.1.0/24 + remote-ip 172.16.129.0/24 + exit + exit + exit + exit + exit + exit +exit + +``` + +### Non-SVR Traffic + +In order for non-SVR traffic (for example, LAN-to-LAN traffic traversing a single SSR) to take advantage of static-NAT addressing, you must disable egress source-nat at the service level by setting `service > source-nat` to `disabled` as shown below. + +``` +authority + service LAN-to-LAN + name LAN-to-LAN + description "LAN-to-LAN non-SVR traffic traversing a single SSR router" + source-nat disabled + scope private + security aes1 + address + access-policy + source + permission allow + exit + exit +exit +``` + +### Using the GUI + +Set the local and remote IP addresses under Authority > Router > Node > Device Interface > Network Interface. + +![Network Interface](/img/static_nat_gui_net-intf.png) + +![Bidirectional NAT Config](/img/static_nat_gui_nat-config.png) + +### Show Commands + +For details about command output, refer to the [`show sessions`](cli_reference.md#show-sessions) and [`show sessions by-id`](cli_reference.md#show-sessions-by-id) commands. + +#### Source NAT +- On the session ingress node, the `show sessions by-id` output has an Ingress Source NAT field where the source-nat type, NAT’d source address, NAT’d port, and protocol are displayed. + +![Session Ingress](/img/source-nat1.png) + +- On the session egress node the `show sessions by-id` output has an Ingress Source NAT field where the source-nat type, NAT’d source address, NAT’d port, and protocol are displayed. + +![Session Egress](/img/source-nat2.png) + +- The `show sessions` output has `NAT IP` and `NAT Port` columns where the NAT’d source address and NAT’d source port are displayed. + +![NAT IP and Port](/img/source-nat3.png) + +#### Destination NAT + +- On the session egress node the `show sessions by-id` output shows the NAT’d destination address in the Forward Flow `NextHop` and Reverse Flow `src ip` fields. + +![Destination forward flow](/img/dest-nat1.png) + +- The `show sessions` output reverse flow `src ip `column also shows the NAT’d destination address. + +![Destination Reverse Flow Source IP](/img/dest-nat2.png) + +#### Version History + +| Release | Modification | +| ------- | ------------ | +| 6.2.0 | Static NAT Feature Introduced | \ No newline at end of file diff --git a/docs/ts_nat_troubleshooting.md b/docs/ts_nat_troubleshooting.md new file mode 100644 index 0000000000..33e35edee6 --- /dev/null +++ b/docs/ts_nat_troubleshooting.md @@ -0,0 +1,142 @@ +--- +title: NAT Troubleshooting +sidebar_label: NAT Troubleshooting +--- + +A new `source-nat-rules` subcommand was added to `show network-interface` to display source NAT rules under a given network interface. A network-interface name is required and can be issued from a conductor with targeted router and node. The rules are organized in the following columns. + +#### Direction +- Ingress + - network-interface -> dynamic-source-nat + - network-interface -> bidirectional-nat + - network-interface -> ingress-source-nat-pool + +- Egress + - network-interface -> source-nat + - network-interface -> egress-source-nat-pool + +#### Type: + +- Dynamic + - network-interface -> dynamic-source-nat + - network-interface -> source-nat + +- Bidirectional + - network-interface -> bidirectional-nat + +- Shared + - network-interface -> ingress-source-nat-pool + - network-interface -> egress-source-nat-pool + +- From: The original source ip prefix. +- To: The NAT’d source ip prefix. +- Protocol: TCP, UDP, or ICMP. + +#### Dynamic Rules + +For dynamic rules, the following columns are populated using information from the underlying port allocator: + +- Key: Port allocator key in the form of `2/1//`. +- State: Port allocator state, ready, standby, or recovery. +- Total Ports: Total ports configured. +- Ports In Db: Ports left in redis. +- Ports In Mem: Ports available in memory. +- Ports Released: Ports released in memory but not put back in redis. +- Ports In Use: Ports used by active sessions. + + + +#### Summary View - Conductor + +``` +admin@conductor.RTR_EAST_CONDUCTOR# show network-interface source-nat-rules router RTR_EAST_COMBO node combo-east-1 name ingress-intf summary +Thu 2024-02-08 18:53:13 UTC +✔ Retrieving source NAT rules... + +=========== =============== ================= ================== + Direction Type From To +=========== =============== ================= ================== + ingress dynamic 172.16.1.0/24 192.168.5.120/32 + ingress dynamic 172.16.1.202/31 192.168.6.202/32 + ingress dynamic 172.16.1.204/31 192.168.7.204/32 + ingress dynamic 172.16.1.206/31 192.168.8.206/32 + ingress bidirectional 172.16.1.204/30 192.168.9.200/30 + +Completed in 0.04 seconds + +``` + +#### Detail View - Conductor + +``` +admin@conductor.RTR_EAST_CONDUCTOR# show network-interface source-nat-rules router RTR_EAST_COMBO node combo-east-1 name ingress-intf detail +Thu 2024-02-08 18:54:43 UTC +✔ Retrieving source NAT rules... + +=========== =============== ================= ================== ========== ======================== ========= ============= ============= ============== ================ ============== + Direction Type From To Protocol Key State Total Ports Ports In Db Ports In Mem Ports Released Ports In Use +=========== =============== ================= ================== ========== ======================== ========= ============= ============= ============== ================ ============== + ingress dynamic 172.16.1.0/24 192.168.5.120/32 tcp 2/1/1/192.168.5.120/6 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.0/24 192.168.5.120/32 udp 2/1/1/192.168.5.120/17 Standby 49151 48151 999 0 1 + ingress dynamic 172.16.1.0/24 192.168.5.120/32 icmp 2/1/1/192.168.5.120/1 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.202/31 192.168.6.202/32 tcp 2/1/1/192.168.6.202/6 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.202/31 192.168.6.202/32 udp 2/1/1/192.168.6.202/17 Standby 49151 48151 998 0 2 + ingress dynamic 172.16.1.202/31 192.168.6.202/32 icmp 2/1/1/192.168.6.202/1 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.204/31 192.168.7.204/32 tcp 2/1/1/192.168.7.204/6 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.204/31 192.168.7.204/32 udp 2/1/1/192.168.7.204/17 Standby 49151 48151 998 0 2 + ingress dynamic 172.16.1.204/31 192.168.7.204/32 icmp 2/1/1/192.168.7.204/1 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.206/31 192.168.8.206/32 tcp 2/1/1/192.168.8.206/6 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.206/31 192.168.8.206/32 udp 2/1/1/192.168.8.206/17 Standby 49151 48151 999 0 1 + ingress dynamic 172.16.1.206/31 192.168.8.206/32 icmp 2/1/1/192.168.8.206/1 Standby 49151 48151 1000 0 0 + ingress bidirectional 172.16.1.204/30 192.168.9.200/30 n/a n/a n/a n/a n/a n/a n/a n/a + +Completed in 0.04 seconds + +``` + +#### Summary View - Router + +``` +admin@combo-east-1.RTR_EAST_COMBO# show network-interface source-nat-rules name ingress-intf +Thu 2024-02-08 18:53:24 UTC +✔ Retrieving source NAT rules... + +=========== =============== ================= ================== + Direction Type From To +=========== =============== ================= ================== + ingress dynamic 172.16.1.0/24 192.168.5.120/32 + ingress dynamic 172.16.1.202/31 192.168.6.202/32 + ingress dynamic 172.16.1.204/31 192.168.7.204/32 + ingress dynamic 172.16.1.206/31 192.168.8.206/32 + ingress bidirectional 172.16.1.204/30 192.168.9.200/30 + +Completed in 0.06 seconds + +``` + +#### Detail View - Router + +``` +admin@combo-east-1.RTR_EAST_COMBO# show network-interface source-nat-rules name ingress-intf detail +Thu 2024-02-08 18:54:48 UTC +✔ Retrieving source NAT rules... + +=========== =============== ================= ================== ========== ======================== ========= ============= ============= ============== ================ ============== + Direction Type From To Protocol Key State Total Ports Ports In Db Ports In Mem Ports Released Ports In Use +=========== =============== ================= ================== ========== ======================== ========= ============= ============= ============== ================ ============== + ingress dynamic 172.16.1.0/24 192.168.5.120/32 tcp 2/1/1/192.168.5.120/6 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.0/24 192.168.5.120/32 udp 2/1/1/192.168.5.120/17 Standby 49151 48151 999 0 1 + ingress dynamic 172.16.1.0/24 192.168.5.120/32 icmp 2/1/1/192.168.5.120/1 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.202/31 192.168.6.202/32 tcp 2/1/1/192.168.6.202/6 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.202/31 192.168.6.202/32 udp 2/1/1/192.168.6.202/17 Standby 49151 48151 998 0 2 + ingress dynamic 172.16.1.202/31 192.168.6.202/32 icmp 2/1/1/192.168.6.202/1 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.204/31 192.168.7.204/32 tcp 2/1/1/192.168.7.204/6 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.204/31 192.168.7.204/32 udp 2/1/1/192.168.7.204/17 Standby 49151 48151 998 0 2 + ingress dynamic 172.16.1.204/31 192.168.7.204/32 icmp 2/1/1/192.168.7.204/1 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.206/31 192.168.8.206/32 tcp 2/1/1/192.168.8.206/6 Standby 49151 48151 1000 0 0 + ingress dynamic 172.16.1.206/31 192.168.8.206/32 udp 2/1/1/192.168.8.206/17 Standby 49151 48151 999 0 1 + ingress dynamic 172.16.1.206/31 192.168.8.206/32 icmp 2/1/1/192.168.8.206/1 Standby 49151 48151 1000 0 0 + ingress bidirectional 172.16.1.204/30 192.168.9.200/30 n/a n/a n/a n/a n/a n/a n/a n/a + +Completed in 0.05 seconds +``` \ No newline at end of file diff --git a/sidebars.js b/sidebars.js index 734e2d1173..e80ab421b6 100644 --- a/sidebars.js +++ b/sidebars.js @@ -139,7 +139,6 @@ module.exports = { "config_flow_perf_mon", "config_gre_tunnel", "config_in-memory_metrics", - "config_nat", "config_rate_limiting", "config_RBAC", "config_service_health", @@ -175,6 +174,17 @@ module.exports = { "config_dhcp", ], }, + { + "type": "category", + "label": "Network Address Translation (NAT)", + "items": [ + "config_source-dest_nat", + "config_static_nat", + "config_dnat", + "config_nat_pools", + "ts_nat_troubleshooting", + ], + }, { "type": "category", "label": "High Availability", diff --git a/static/img/dnat_gui_config.png b/static/img/dnat_gui_config.png new file mode 100644 index 0000000000000000000000000000000000000000..69085dad489286a679b7dadf416f224f7a6490b9 GIT binary patch literal 17521 zcmYhD1y~%r+xBrS4#j=Z;uP1y0t<^nad&suBE_BJ*5VX*clY92pg6_d;oY9o^Z!1$ zmJHd5@=^-DKV&u z36cZIKf$IN(q?jUP>hgmBq(@jY$(`2MIgUW&_q!1|7=4+$v_kTZ(A9f{%;u=D5y|N zD7e36v>@r99}wgP+52w_`xW~C9q}v7f2E<9zry~v4HfWbH>~!#Ye<6Z0Mc}Zfzj5v3bS!@oL5Uu|19FabRHl=L{TL#3!n+Nc1p}1d|a7 zh?1mSuP7mkr3i-$4M{NJj&Knn>D?*P-NS{IP$$-}B9Qr_WP7u zJDJG^0(oOy7uqSqmPbcN2KMH9{cIz<9tsKyZ%AhG^CV+-RgkmwI?gV=S>^b76+27p z4*iHM#UC>KOVulMuyWBfxYsf4z%?d0JlrtJMSGAteD+L%37EPFx;pvUO7NqT6`M}} zjbHB1yvvSfgrR$XN^)&&0hhzIc(T5yuRO!BLfG+A3l;uxKuj)KOy9dR=!tBhAmxG) zY{v(9t-To1l`6Ai#=bBt*h;;2F&-=9T%a_J961p_3jT29aH849Ah|zwg8$PU`+T`} zG_73vD4%f-m$u~5PiKOuJgLFLapEffbv;4f8@OyTviF2CF=C%1zPcRL0A>9GZ_Bk` zjdsT@o1CsW=F7CCe0754GPt|=tW+s~`aL5UqbAiFZt(-7iO?GD*L(VqRj}Tv*;IYM ziY3!^IGmTWT9ECF#K+KXv>k{!)(-ceLe;!E;Dpj{u5Gv&Y zncX6v4xcJiDpJQchQefNJ|^SHd>s-Fqgs{c);KCudOP;DHFB_OX8MZ}f4j2Y?| z*{D=yVEEo@QME#VpZ}}EdN#dgO%#oS#VTr^Y<4k|W*d@rqaAlH(>gkOOe(uGcUxOe z=#{NyDjDQa?^2hd0Ogv7=N_My|H%Dlty7RD2!2;h68nabL#CBX*oPkD)p>7%$}4Igl*rFqq1(#1V+P8Bjz2IwJwA>$pUkE* z>>&^KsL*Q_%ij)nIhe*$N-f}}tx_(CG?*D6rTVtGvNF{>BNdh=eLE0s9Y!h;1L|k` zmD%ZlPRMDJaM9ErnK~%|bI)Jt!!F3-zZA+_Mrr-H3e=Gb`Vd z&srC+vhoHYI0IWZxlJ%9{7$1av^lf(D zD+nzXz)IuMdR@~A3z$JCSd^Mgtu<2+Z-3z0`Lf4oZWb!C#|-qIGSu)KG`oVpZG~lyJK%6$WLcwU;LcB_}_LEG8cB~0EK zaGkVyMov|$5L5b4XLo9TZnb@UJ6o!);9wNEhYYhd0yp9BV@tV z`m8$Tw)M(IUp|XJ03e+ZhLU=D*%wITIWZV8JUQgQy-%rH@x)0cx<@|TYO|!AFP}J{5IXvPWb-1mNj^t78vVExB%)C;2K2w&m80CZn96nJXyJ*6 zH_paAhl_^YsEAvfJ^8yPbCjj9n*5-6K|;Y*AvWg$9}_w!{RS51t&VhC$nhqD7(O6 z<Z)wP6qBc^Mfl+H){?M|<2l((#UpK$16e%*!V(Q8-mN;hPKM3(~% zdl9AqhTIyPE^bcTH9lwKz{mY_YM^V3O>=TozHfF_CSdw>DKCd6n+_k+pnIbZF7t(w z7*qOFr*J;6W+Vnrn8LqdLcTp+zz;$|kLyh1980YEba18fM?wVr08%Wf4St(K^7G)J zER;(m>U>frZhv%n=?tLi=o#bW^n?C8t%=v^H|LB*A^+9r-nH{ zYt{a4l8BtI3t5Kk4UK*%mPtC40b`#Ag~o2{T>!T(lE4;o-b`V6uh&V|1M+Q34X$2sjR-;UyA%qE|cJC#F$s#`DpW# zTuAMYfTO6xyvqj?C*a}8Z60g$C?#eKc@ssazwfh0BT58pQ(LD%Dxb&I7Eg6gc%7b< zJV1E%w8S~``W7Aq_iYkIY0!G;ZHb(TgDISKc;=RJfs8l;a|WoU9erZ*Foa3k*`Vim zt(~)kwQ>~p>FOY{hI_SGi8G3XPZi1Ouz@+>$&V2*j1yFEtq#uEoyd~L@OpK|x3?!x zxM2k8xl`TsgWqlfO2DXZnE;0kA}@C$XDu8!7F}*m-WsMqw_=3}WR$7&%^9K>lzA%F z1Mx=HhKa1{5@a>e?2^OQZ!_pHy>E`NhciZN(3w0$JRHbb!*o1-TR$F}(JSZk60-eF z+>$^|K|XNuZHw`d9r4!}i>K;$IJl4)9`)3qnLKQ;ne)AQ@@#5uHGB@Kzhj?K;9%hO ze_4GTbLq40Yzxu*u1cspyztHIbaWbuSTCID=K#QWPuTT%P2xR9nVg4sVp@)WMU1hO z{Iu4YS&w0D-2Qhw>!)}o^#PCSZyK#Pq!zjl&(p!3A^YL~XzXuMpKK@f+8^PIVw}w< zr{9rq=l*^p|M1E3F5o~WVeqMQ*NCU&lcwBKu_2DqHIbzX030Cbd7-J-X?Q>{9+DIM zBQqU=q#P2O%=a%!M<1EpYk@ed=uyAOj;<@Jid=V3pTxF?tvy3PP zth>s-n+Fv~1$Q5)(4EgHq@8Ed(heU8JBol+L}+D6f_%N*6J5^%Q=)9pli6IP#9=0y z*SbaWLOOZKxWs-1av6GMxhe%R(WSr|RvmpLEPNIXIF&+q3iyEN;@6ayb|kLvb7Er} z)%mYcr=7uwrMd1$tCERds9aKP^G`d1yR%x|LHs=0jKrNZhxX>?dl;a_2QP=%`^IkH zU#76a4d{X;3@Qzoo!%C{y0LhWR=7!pnLk&}#T1Fp{DrFt1&>j=4o#ZXv7FU^iX9v+ ztM!a{l~6D1XJL8QfMr1SkQ)3_qQ@R^x>QTtAAyIFQaN%KY&o(moh!%w&@&>gY>kkp&-4Ta8mK9Cn%)*61+&2z(oR7- zQwIV8>dy`$9g&+Fp9u*(fi>YC-`)Le2PU`u?TrRP9cuzesk)OZI@eq8Tko*Wc)$7A zX><989Qbj3L&ym~p?vi#=ZU{h7zsAHcZVYPDoh; zs#6=9t$4D)qbca!VyGbYLPyQ*@vzG;*rwM#%+7uNE?0J4&SU2V3fVYrkH&lLWV&r8 zG5n_2?`%_$JNpz>{kCF|-(c_n19pScJA}071ZrMb7u>^i>OWP{X3_( zaqdV|%bIvt{^TR*CUmgpd?hmeorE|Ac5C%}>oFM1K*@J7`gj3sGjg7BqkL|yMU)P3 z9@Lm?+Kc>Wz@I6q_E^y-gs^HTE#95G;z}j8YJDky<<<&1dPxZaXj&Nmwi_Ry9sPBE zFVYjvommT+8E`c0tcd8cec$@=8@*MLnA7ZypZ$#d z&A{<=bDm9%h|50adz(eYw#KUb{q61GhU4W(>RV6ey|}GgmhC}T8e5kfwYL7YLLr+a zx@;D*Z>2p^1L9@`7%8ktsfD1BazfMaW-#oj;0{93cH_L=jJ2W zIhB;f6u_Rif&I(!?2sf?lVwiZNQUS0~xF@lS%_m&*8 zIo$9{pv|#lW&t;w^$!!%)*3Cpz%g6kFHAImVPOMLr*1pw=BHX<%fWO(N;rac`&(8e zZ2!2}+5By<*sSi_6~PS9l?*~W+n#aKTSQt@bQ`FFovL>o``Zx{F(jjVqdEFd+3PcY!ln;IG+qyUC=MwI8LN)wxc`lZY_O*B2+ zb&zxFWVatbdPTYDUmR~8N{i@T0w>p4IO;=Vnqy}hK-^~U{ChVSRu-~O>iMFT=ms4# ze2}Tpp&zAGScQ6o9W6}>%${UR6+n0=4LX7{Nw7}o$eoFb>xS{WOwFGwAeIM|9`?h(Voc+G~ zA?3CrTK2HvB+>My!Ct zy)Rck>xaG+N70-ZBR+|eHuJHzBnvU+8|FJwP-WJY!Z4Z=M!-$Y5Kg^xq{S7Tl)y;| zm`5~zFqO&R_xljFu8Ey(ay@E#DgL;}=$4w3`xx7Q2Vw{+aRF1{=m zg?98fBm+NIR`3&Va6MCAePs@*F;001G>&0t?MeevPHuOUyIthYVcQd1?|z&PW#=M{ zm>-0Huyz{pRmiBq95FeGIM;p$(xT0dF?BOI_=WDVb&g9qVpEOl|7(rAOoU4@EOkYn z_0@&)S_08u%4W~xu6>&btR=kYV1+a{*NeUP`v%IGI|Y#7UegCJcy@j%da)1ha5`T7 zDMgq!b`ul!`f^fq)q-JrInZD0*LsmuJkLiV+{szBO|m9ExW?1yJ$}O+e=0W*;&RVpOkg(pe+~p)wlYq}^Rw_D7CCpqri zXJ1aWG#quYf->>2MO!uxar7sp69Q6!T(^#rD@+BN15Z}6Q%*9VumXsg6d#}5rU;E@ zdgf4SEsUHCEgetuTAq<(O8l82m$wf%sQmc3IECyvYuXIBr~JBc7JVN^#7D+KV-{3{ zaelkdG|3xoLylJ(b1POZXv}7-E|&(_1}SBQ)l$p(k$g50YG0=^9CPuwx`+T-WCNf( zF#!G8OUq&JEdq&!o?ZbQzmTOGaOZy1+@VCRXvO5KyHAstgcMC$$7AbHBM=8I?DnxX z4{nU~w)47L;~DYIa3Hl`@|oD$#UnJwd>j?~n7|@iTMXUU}nIx*9l|tSSf^w0X5%U@wF_iN`;fZt# zLs4G@`mL*(t~nfAn)1K+abQ)=+#lszU4Luvkw>yV{jh45oZQRU=Hwr2p|lx!WuZ$4 z=E(q|_}*Q>?2_GaDH<6o8zx-SN@oqH7ucQj)@<3bN9X_Kd$f)RZibI*1ysVECN2*obSOBeX+xLF`33vNj| zQ`VQ$B@7PBKVRTVvwE%`0V@_j%jLoRo^B3{PGxl@1uI;3mVF^U5> zD0IE7P@-nZ4zL|9>7fF*tg&SkbG%W7s%u%~bFQ%+MyaQL;unVFJO!S~y`ckTSTK4c zo-12X^Zho`^V?(KR+rVDqro$6FB5X?oj&Dpr{ zn5Xn0J#;F@0iqihdd`heG&>o*%HpytDq6NszGKy)b`o(m&q_E-fhoQ3g@@@*u+WUK zUYIWn;Q%znSqOm>qltJvOp^V?qKUwP_<7+(Tz(%4Wz+f$h8ANS9_lPTF1EwlvT+o1 z-!FFq`K{+=XUjCf00Zi^J2Gw?B)`XUtWAhF5B&W5_VeZ5c_7ob%RN?ucm%Q9o^3~` zjidJKAsOrHdF$em%{}pWm*eWk3ys-P0lFWE3;l>0j<%O%ZH1&MRwm?h2@J#zNn?v> z)tL#yM5L8mg^%Ch=Ccmu@?8@eKKq3Cv2!YB?-@vcmz)R}n`SDnc}QBQm9k?79q7a} zFR_LlWCB1R4M3Y)Qpz{k;29;JQ{2ATc$wMuHaks$N#0dYH<{UH`FuAyEY=18@AG_4 zI%!O7)y;}}$&Ak+B5)E#XR(lG5;2=YyMN;Q@zd9i3lH403;fKCBBoUY^fJ4h`t!Xy z+zk`*nQ3`rw4?=tW;E@|7^-RgSaRv#q@DGG())t!2_<+ZGdIb@nmd;GOjT1Tc$Z0ik(-(FjhMu=KaV=~1@E{Hr{pT@qxB7{*Yg1ASPmIz@H z&b4>=G!g8@L(z|i+Sg#;P#RO~-M(R3?ex!Ca})}9+#1jT zNUJ@Q@w;G#qLcNZazuEESDt4IIZIa5*0~wH3Wu*Kxc*VA^J>Gz!7w@cl(5BFR}UDS z7rg-spICnAjc3M0m-31vzC!GEM~E%mJb``G>}b>N9$9D)4^l**;jX`)Ih4R{m zSSqaW)CyCAvnzf@kL<8@Zs_@`73(0Uxi)_G8=}M2E{E1@IqP>tZUh-3fygI`NRk{G ze^&R)w}H~qpVNhv9N$x1@3N1ia7ldB@%Df+FDbjcZ5VZ*Bk6^)O(L~~y^CGJR{rh8 z4cLmu<~S+pBN#4b&YBxzSOVHe!}GM9iR}< z$f!=+YuMH1ZI;-478PZ4*n_wmHQl8Iza8U{?N`Y-a+M|`sG@OZ`%l585kk5>j-&2_z&|6?sobHQjc2pj5 zG;AGqHDLn%CjAu^4SyH_(Q}9Pttj|5{g9ta~ab@)#2C~mcj8&aHah>6h*1nuO4#R=$mf}oXC>awgd-jn{w~3VnTnWww?CZ1Z z!O*JXRf~8tO(WCc+q=%u?q_q z0yaG{{@8h!!tS(9U+r+RT2N{u#%_86VDH=1&651V#XW|7XyD~)K2wNx#bV3hsY|Dn z3*dFW!3{wtWDHSbLUR_0zg{fu&5+WbRkFxl|mLJWF3py6kM%z_tD1 z<7HV)XSuN7;_|DJ>yzQh89t6q>DKGAQ$7DnWtindC1lVqifQ8}T70koac3{Urx^r+ zYh=xcdCH`6`@&7Z{Wx^;ajI=#?l=z+c41a|T2r*T<;WL?(5zOsjne|K1@oO0rLiA* zL$^H|bE`-iPYPQn5iTD}yECY5(#nwghY=TlCo1tfH>U7Xm0R`qmdhj`{a(`M{kMLd zv?Jo$M~+tMZfMLsCDv5=B~^KO@-HDgl? zERWvAIqy!;49`DVMUs{m*{#(f%Vls$jV70eksS9Wr14P1zGWuDrjubpGf1e=DB&nn z$cfm`FEr!WfD68dxUs1e0;)iY0=`Mr#x0T`w3ri|$hd=d-+W zBEDEkY4A3ku$Y+ZQ#fNs_2_s0mjSy)sf^O^Td_U4@mNR!_IkOdPCM!`ZxVLA&E@O{ zV&vyQta_y`&BSA@PiqC(HywHDL;byu;_0}LvsLf&wEvo%fLxgOJ39yDguk%D7nCK~(E50e0`0nxf;7A<%1~D_+=N73isz)F??U=FS zal#6*(-N*n)-{vK(`l8~ze*un_`VPtb$nouX7G|hN9XBdw|5t9k-Ng=&lM#1)0CGA z-&49aN8oa>ghlzvq*%>Ugy~5>vuS9_XzY@dQ|dTg?;AUN5%;@P!Hr|{H6r#gM)ZOR zA343*6dspKv5G)mc?KmmctWb>JLTrziWJ*%a|sZ$h>bI3bD$Q8o&5M3f?)7XleQAS z7J6eQ_uwX<$P@?PtGyTrQv)oOswSdd6|#ld*n;n1;OlmTg$#ZF|>gkJbFyu#i7yh{AeZ939&4YmHj)Ylng*_jc7oHrPv{ zOtxj+S)ty39TrBWZoOAG%D|V6tY*L+?y$p69r7S{u)}r4N_@3{<6>L!k9Qs++V?>; zoO^TC`ncrZj4pLi(eRshpDI57b5p(xO1GZ=93*^ z*!>Kutz7~zx(tEIFLYNYy@8E*N=yVf#34-@{T-Az^uO} zQ-!4-22UQe>TE)!aSD3`zGhG`j<2ks;xQ(RO^`HCHP|BdMc@g%Zz(YSd+9#VFgX%+ zZAx9pRB_GDZ?U00wtjr`S1fgNt+Sd#Amn@sGZ{_@ubj7>q0KYwrA_6sCQ2xB=uVp{ zisRCD`$DgWg3po(0Y|jM%Y^!|yq_P?93kvdo7Xdnto)7J4L!t{<+fcD6=+OTY`v+h z`>BNsP{@@KMSfB5%m1$L?dI`R)` z0U>sx>nvyTwC0F3KIH4>JFq(tz?cHw`Z)nEut&q52QSs^QsAAFQsoqar1FPMIE?x*<1z7BHAUqiPwH$2 zh3~@~!1xZ8kpc@~G|AJ$W8>tffPv%co%RC0^+p+!^Snqf~=eJbrun;aQ9n&i22$=1-`OUUf&B5JSJbTr1 zs?*KtAY%YS{0N5-V5Im9{ONf+zl6q7C9S@0rlQ1PKJl zbH%!23coRyGjkfs;1S_>x0Ev3i-Fv@h^t}1o&@8>Ky*4*8dMs`3zEA##?$2_^utOl zy}S}I*ZcaR08|uB#3k|a#1#Dye|0aJ-|2II0TCe$PD0qy(ROzB5-7|PKwG$=%oh?q zHPDxW1?z5<Gr(n0omK9a zr8=^jv)VYHF)!9C;5SRiUoW!+k6wR8PxXGhC8n}9gAtOt+x;qyU@xIj2Vz$epp(yp z`;3B@YfRo0cV&INAzWN@o&LA0+NZ>%0v_%SW=q-t1Hs8m@bO2U5EcuwbGG>T!{{@p z{qT4vddgVR;5c0l=raW}%9J@61DKnzg(Xgw$3`Cp_|`7hL4d-GK}j(P_l0$!Hr<(s zJARR?lyiRE3A}-Q7r>GM@@hoa8N4}O3Hu?4C8Fn}{L%d3Yc#b~%!g?G?{Om!?56ct zmOg0GWAgG7yiVIyWtCo7=-o7073*CAAGe`lC$XXqck90FZt0??ew>8FTmR6jVpsu_ zv|0^rx-Bm8m`Ihxg`i(lCM)^UsCB15v^HCh1Z1X5R}jY=!%b*+bX(o9&v^}hws2WY z=ieh9z(hJYH~=g!n58rPsm;n#P0nyJG;7W9b2S_N&~)_MFb}Q{X6S0{2;ZqOF<3#6 zz&I9PFD4yc^6`xNT-OCo;DrjXVBG3tC?@9RyUDdj=At9J+bVq@jhHFNXigyh6KGV&1U%h=h+baVn8j6Ya6| zrdA#zZCMVRN0XnKch)(82>fACBK(z*Rbo3he z<+lFQZRhEbsIX~DxpbE%pL=YpxM~b=t8^l*_{f)%{l#F9^DXe&5ybS%5lmKB8Bs3| zR%KA3hJ=ak0zjin42+s=wZ9TkJ)Ywa!EqFn2>@xvJs{{DlF>@#e_#>A@P7 zviEDtV7_7b$s5Mw!3y}Soa@5V+0IiAXD{@5SEpHl=!;fW@>i6WirBq-qH6NPtp$tF z`I3J>5(7z!zVP`oyph9HqJMzuKTuRyOqY4(6aoTCsl>fP(7#RXPi!74=b5ZLu;|}C z|AgvuBq7>jhQJc#pGW#noT~PZI!}!b)gZO81zs(2SxNryEn=xpXbMZT!)&5x-vx32 zTE^{jOAJm`C~v-Vv={z&OdkxSs*Qu)69yQ196LqIq0*=2NS=1O-?;rs(%kg8|7-Zc zVxMR2sBv+Fy;{L*2DHL_+8=8S<&iC(z>A{sfb) zHv8RwpaB+Pz{VnrZ-NCi$ERiY|J4(WrI`Dy49C^^--TnsLDbiWPkAZ-yFsiHkn09x z%|87V)e)kYNc2+(&@p=dBN94rp=p*`B@{3Jce)Q0UxCDMyk64()(*m~EB_H*xF5zV z|GRp)fKS-Am>c^v|6gV9@>K#@%SA6?Azb8QgKdT=ghxi^6%csG1UWh80McrUD{3e@ zsaTmtb=TIJ3UPO+<7HjTDM0{RqQyeFcI4hlle0X8v?4vSx!j%nTv^FVD@(A)I(aZtWN2+2>2bdKt0>2>Cj^Zc zkktwF%0&vshB1_^yCq+JG&oa87leMiJx#1Q_lv*8AM1@s8r|`^&HkCn;ff8BH8gwn z>mBu?XUPCyVh(a_cwfjHq7WtOL4((h_Oq+2x_r;8eM(6G6kdO*W;~Vf8N1VX&uuK5 zb0)#;a$YW#&l{n^hFyeBtz6Ht*$uKH03erui;PX%HCL)$Wqr$HH44t;^Cn6xlI_WG zKjw4WBxoYPJy{Pb3Z?t5R{m?!{xq7HCyq{mtS^cXN45n*v;|4kf$us8Wo?ptL55yXYtPCY$Je#EDxD=VWn2e{tXfTk0z$|r`FrEv#$6&DK_^t zlJE>p_qSzq6aG_8dtOcD+k?OXB08U|J1o66kAT-_*2wKG^WIIG$nDgX8iy%;r!jKt zh4Sve&zI-FuisJ54l0mqSDZtq^a3EUWWA%Gt@!g;-9VVl+xE!B&1Y%hCz}9Y{ixNx(!eE_q(y) zx2KyUbE6)zL0RP3toqG8YioM62<2K01LXcLlt#B*kWl|r%SU3WL%FKj+FlG~|F|1s zc*5-11UiKnh@dB&dMHN<=7ky9-IbS@uX1qm#f9~G>YH#_vURwxni>sURsphN(Wxv;8Xa;4kOja z5!F> z&{hkadD7d>lI&Q%5?(bq8i#G@AuQXf!Mh&MBePl}=;ecyfYCR8aVslJ;11kj-Hn8v z&qH-NphEDAUR0Cg<}Y69Tvw}CMiwaNAL5^bK17ry`@No3edGE_=gE7tTo3!?u+fHo zgWlx!%uh7?DtDol8yXs08QUk~aR=qN*_Y&@Mwlb$iA~6924qYJR-r_0y@y1XqPvb) z8mC(1z$69Xzb-n}jZQm$zLyq^8j$l3!g&tidvCd_N*k5L_z^mhE);cdat1IPTfvoh zDWBC6foo+E=61Ri{)~8o!j8wJhy($m<6H(1aR|Vjf}W(pHu+f0>*&C{wQb2VyDa@~ z$}CEhDs8pI6^vs{f9IT)3U_< zYAQ@Cq+o_A4tA$72;vnP+Rb} z7ix$glEe~c7{PQjdGPF4kg4GLssH%*YmcYx_-zKYGPsMKaaJ%xSvnelV7nl@=jQCE zDW?gOapND^w1rPuJodt~1=R!)|D5RET0VSD(#=}CyTW_W7o?)e%;dJ-P>k;Vsd?-2 zUB|^LL+WAe4js>{K})tkAJujwFVTHE>xsf=ysYt+^%QPQc2^K`=&#d zxKMn4yuVMgTWzvyfeeFuMc0Hg;~6|m3lP8TeIURHr>F=*g2mU;tUY|S?_6{8I$hHR zzh8h*FElus(BM@_|0KImEN8n?pX|)asxSlbYvpwCizt&)!VjrRmX#3*1=B2c?KWQ= zAYr)b1C$+4+4a?;=nQVq3KQX#C>9bmoJCr%@(kq3-%j-}s=HzAw2bk1eyHywUiUHD zrZ$$iXKrn61*bz6+e{I(F$@ZtRn9CHgcoOC4x$pFlH6$-7;fexI}L+I=>#i0%M!O4 z7w%FAcV{gVcQOab^3@tz^Hb*O&1EzGlm1en%zwG>fx(P&yNs{}_s5VGB_kmgJKV^h; z3XxMGw*vXcD*qCmcZGjMS)qLnx87fE*G3IdQ){Pj4GRBeY-Ie=q8S~&%O3xVr+~8< zh?t^qFIL{U2+*0bfaD_C!g+9}6LqSh9b47;NKnZB8Op{JS?Q)tWtp=!e;R4kS%tLS zI~)FpgT@|g6>~jUMutb-6E9%IgHYHEDivSyb)W5K{3k?w`V?^)6UgNOE<7#`F_HHnRYdhCK^l~I~^)IJ^P3KW+L@$s@8X#L1uUAfT8q#OO zu+@0+gLRgdVjWUhTb|dv(!jd2LOL6OI6~W!=Lr%8Xr2eDgD|fp|3E4h!)Ox&KjA1R%+Jyw}DYZjGhW3|b^B{PLpediqmG%|PvLUGy=GiX~d0!$l1 zY4^?Dz8j|;J2E3{yF%X2l%^?_iXm>57pH<ZvPVayiXgH@|dIMHe%7BJ^^B58of)rhy(rd>h9>Y}ABu>+YmTIrizH-|>y>&)& zPD|}kteBc<*=;M1!=S}xuoPdu?OVCyeOwbX&PL zalD1WfXVy&u2#u-Sh$iz_wV1;w#>m~kmaZy2r%7Cgp6YVt;?gHHuZyJfyN;Lg*Qu& z?{$~!c%?aQ-3G>3>ODkeo9g!1ynEPT1|@Pu(2vMsb*KBou)xzbQl#jP#)I7ucaJ9K zxn0uH>r^M}@-oNOL%MbF>i3eApqGPB?>dq3p<3Nv%863$wFeG&c$NAiOKTHlkqPC z>5i>Ig_1%(I3I84cCD(^=A?0XmSPa-~_}Whbl>7f;!*0kM`-S5h#m=_xse;;ZonU zwcKHxaknbyw2fJz+svT3h~<-|Z=EpPd}S;F$^?&m;S~?!;k&Qi?h1l1z$BY!`5&G` zum{QUS@j?!qfnJqKat}tm)#S=xrl(_CT~-_Yj3J!-VewUkG=@P(F7?B+<>#du6bK+ zQ$fOGLmtPrfo7LsC+gopr@eq#*%vX6Ty6yY}uUiGGe1GMGXd<2+}pR)vR zK+PH4wonT4o>6dbj&??Re+B{8hMdCN535qj9dQP_(k%qydC1V))U>O`XyTo`Z+^!Z z^+!aKYd04|R4uP0MbyVZGXN-7UVcUhD-?lNK>PK4kbI{nOe8c9c%DEnZ`Zu|J8oub zxm@H^*hE-u zTuAT%lv(<^)`DiG`uh1vS`Wc{O0(Vy-s}2+63*l5%u%&e30|P_^cM}~DAB={W$lkZ zrl>R%VlEq5&K2w->BExoVVDaPAqo#)*VWW>;Pm8=uZBWp+O_dyL^`!-n%u&)7e}8y z`$KNz^)^n*@-I0*c0_a%7>))}vh-o%!(Q9v`efdQm|gAk;UOp}Sg$|d1@I${#7MpN z;=-7CSS?@2I7~V!PTjiE~ zV0@26Ji|;Z_F(u{VsiN0fDIQ(5=q%)I=j@sht3yYHoGG@Lhw#r$eaPch3zV{RQrD!LBblgQtruKqHaMrVo>-^k%Vf?^FH)WTM4vZ4ZZSH0DaLAqH8bs6*Q={gfX|OZs1- zLeWG0kL0ng!+M#Zhx#upivY2Ukeo~F^ZsV&!$LAD16uww>M#v46?3E68npzz|LYb( zR<9t{E_f$1Y32&h`$h|tx%$;2nT&i1*J~ZdExXAP@h5vK`T!9}fuT^Hx4NZj702Z6}9MB;Dbf4`;SPWX>}6Fx1yk@+j%GXI!i z@^-=8f8*&Jk3figdu*#*e)sph4uM^C;q%zeSM}Qt#wCQ=gH0M5Hwc%I(dg-hrpA# z<8#itwEq0@uE q1SWDo9vG1S9$XNH2~bVR5BuOfMct`+p2-b6Mw<&;$S%sE2j{ literal 0 HcmV?d00001 diff --git a/static/img/dnat_net-intf_gui_config.png b/static/img/dnat_net-intf_gui_config.png new file mode 100644 index 0000000000000000000000000000000000000000..cb234a60168a95396e2abeaa4619d328aca1190a GIT binary patch literal 17513 zcmagGWpo=$6D?|rnVFfHnVFd}W@hF%i9sfrF}4#kGh@um%#1NJ`zq(0``xwPpC>PQ zdX}nZq*ixz)!w@VP*s*eg2#sk0|P^nla*8l0|Q?HwcTN%LH|X*^a_Cv;O^=&;$W2% zgvX$h@0Pl9R!T}>^q@8@*e7swFv!0qpg%Bhe6Uadw86mS!3qA?RtKm3&jtbvEZi0h z>OUKO(DCm>7W4%5{_hC+6a4>O@h8OpwFY1L3Hg89VD5jrQOGR}fevskvU;F%1dP8= zaIlOYxL{zSU~-aTnm*uXMle2DQaD2Sanhu>=zbSju)n;M$dznQR4`Oa)%(A~%3>VD z!b5zGnE7CHjAaHj&k=^2bK9+xt0t+AR zg%2L{MOu{NC)yM&B|L;SAfZ%Q^Pe*tC{74`@X#;R`fud_wn2uZXlPTCnGstj`COnE z|LOS|0|(Z@(Gd+D9X*wnzg(JB4Yj(lQQFSH{_#<8;2LZ6v!i7UjY{^`x_2f;;IjuT z9Fl~MjZN-e1;#w=-wV5nk!m@_{OalLWph73tan((U#_);tkNj0tErK@2D+4LmV9<} zq_9AJ9;x!>I%*IZWbsatQbr?FDZ37ad?=$-Bc4}b)NaQ?>-}9t! zPDeA<0Q6aWVo)QnrmrCdZD)YZTgQN{tqwg@49Gax2ul{#8`v(e#Hpo(9%pjfQo=&0T7< z>#p<q8b)^X9&GQ>IJDXKHNE2-e&kh)8PReE;U^rDK<^0`f9 zeWtc1UEiL$ROgr5CTVzGchbm9rJ}I6Mv_PAiACyX3stl&x1K^EU$mZ_)>{EpU3g#N zFa|PaO={fel;PQ82|k2)CmeWTUgpvSoVlGg-zP8GiKOK7es_rSgIP~xr(6dV=8Fwb z;Z+zt023l*0!0i%AFewiI^X=vHeQ!MXLwM^1eIO?;IfC7j((Mv`{;PN{k`7SRP#6~ zbu_at!T1{3nf}OoFBCX{iAZ>x{=H?Ca_i5ZsO{dafjv4A`s1;Q3Cd)2oZhD=p#jX6 z&5OEhc$$Nc)vqnOZC*&i@68lmXB)Pab-yG(AKLEpT{Q6Kbq~~%gclX0*rKN>6mj(|04tXP&tKoEb zdd_4~&DFFmSRlGTOKtW#D@9$<#bh?b#R&cpmeF9xV74doak|W*TWe7hx92D|lvt#w zYH_>2C^1!GpfXpriF(mwTRGR;~vJTRygyFr5yzra_~mmaN<%1q}*84|owM_{K}MK^N`_R8sA+H;?% z(gwdA7&&mkDaAs@!$9^iQ!tvQwLv+?5{4`ug$?7+Tvef9v z!R=&N^~x6~m+)@2q`Ehpi4qErrJeD$cm=}5goHQZ#Pc+b#Pwl<==J%J!`&;8NFb6z z26?BfsVn=#7{v~r*`zaC{F9Px2K!#KE&UHZcj=L8@Jwze%`T)ri@h3Q zWc9QEEM#X02o_5H(x|7JdXM_^=qhu0WaL=(0|AM-DWbhd;qA*Cl)hgQFxxbJp4WS> z&02m44BCuZ`4;BpQT4X7xu4%(FCQMlJF=KMNrVU!sg-*Vmj2GKlSqr zC3B=ERIfC=sD@e}ZoNIM_Rez^kwcYfYCqn$nf~NlsxScB3_j_0Rad*j!~2seq?Fs- zJ0Xxg%+d?TIP*duot`rG)gXJ?Ee;NA(0n#`bWDkr5dV6$4MP-9r(wmm;A-I}o61cT ziOm%ILtR)t%yKkI%d*HLM`EZ`vxMDcd^>V`Gq&e^T_7pr>Bpd+A;xjGdQ<8HRr`8z zO}fn!Av_l2_pT4)lKjn)Ws}7cZhXI&_MrXBm(`{4v8Ejvp^Cp}q zBN8ej7Nh5)$SR0o5$j`E)ZX53l;YU_l3*pfYZt&~;~5OQa1Ig?f53OHk5@;@cs6|# zwJQ`<^=#++T{yUA%@TE928%YwRc(j$R;hY)9o1Y(fb8~d=syn1#|SNAN{reSNe=by zg!^~vo&DS#qP)IsX!FT@S(Wg_39Y2}#e1OpFvK_Ut%G~)SYiQYi)4axt2<5LywsP(1e=>^+OZlv4m*qWib^Ipbd$98H?@E)EAxFyo{2F z-+;`YAANAPGoY0-_&s5Ep%y>ssr^-pFWDvt0_c`9?<^HTH_Rr$SH|OwRz@0r0ne0q1 z7IT(palUT$2hDEP`T2a($lF{=u#|=>l;ei;sDV0*r>bY0-yQsdvu+tD!o#Ove7W?V z?+P@-Vp*$lPthgD+X-@m$|PHp{i9L|$UzyZeIfgVtS+bnK$37yW!tGb9TmFWx@~f^ zBaVOe{mW<4OK|{qP3Z{Gxy_5@^K@=#H5z+8)^*+-?{3lY$W*DuA<*S*z>}AcFVezO zHQLc>>;2nHu~uDWv4%kDl_+{ulrF3DYU8K-d*ouZycB$y*N07wN9!{?2i>j-!B~e& z*gq2FWqNguvVF6mV8V&4)aWseMx!ZoRr!ZeI4nb$34W0l#l-7f!6GZ(J{K*+j{wPu zSKGk#LPrFtub<%eH1ZozSm#V%luXlrh-8oJ&tDZl< zOpu`f)AL+S>5MGK?Geu5flLXPTAWTZU`!cJ>XsuZOyNB?#|c_rXAeh!Q1;Y%`;c1L z!Rgey6!d$bZ9si;>$t)iSyO<=X#s2#iG)h>oy2L#T|FzFmP~G>!~a3-klBcHSh`!< z#17=Ot9T%4GBzY&d5M=wc4f$s-YmE)0Sug)VjBJOa^sJX>`y`O&*QzkIUnbX#ukJ+Rfo)h_u1}sE(?J zd9CGWWxjgh)zYMn=E#2X9xgsUyca&iHwabf6SKJv@lbjBKt(|S(QvwXDOF@D=A8$A zz_qP6TP*&U(bRUSH$zp^(Q3wEUpD>RHnJ>SFE7Nk<3aXiIiuN8Od@BtXYvpnCVfN{ zV&OPCk$%aBV9^mnwU|G(=fuR;7NzQ@)9^pQT=Q_p1J>5)W$=ToSK!Wy!SOf_{0-w> zw~Lt#?oS_||Cp8rsa+h~|1)Xh=3x5(HUbFK+|JYJ+U(eJW}~SrChDm=hYt`?wEID~ zT_~*96V6t>RXCDzHBA>0WNYt`FZsQgE$~iecq+B?%Kt{nFi>Vn^@M*2`E~^AI1M`d zJT()p)Xx$qAgCeh_H@~esQ+Ceg=DDqxq-7^rtkg@bwMGss5t56Nc1oC+)I9>e~kW# zyuG0kJp6#Rp}+Q!0nD3aqN0WT4ECow@l6vN|K5-qLQcLuliP8DWVSCLgO1m6;+L1d z0`RG5OQtxg5){1mefdJ17Xyxami3Cpsz;Ei7#nkJHrzGW`W+AoR+KW0H`q5KQ&ff) z!2lsgKRwXk!XMxPE15ouZWOmTGkJ@~RVr=9^`=L%N3mZ#LJ$IiRW@BTcHo#2T7PjhB5S%ewW!2axCeU)hIX3UU z1F)o;h$R06oJ!8)UN=@k_YmR!ZE7799w3oNl8g~*eWd`}xp=g-K@>p~H) z>1DKXDWj@2yNx$HoT1@jzlWQkS=88%lWT*j6o`~O(co@vi;k({0GM|ZyHUJ;o^W>9 z=Xk>=CN@yUTo7{n9pMIhQtJt4T99#sH-`zpU%$xWqp0z}XkMH8VaTP3E-mwuKLWb& zFiImGx4sODHH`;7?~O};={wsE)?iW@d5{o@5p@$Il>>0IF%W6=Cd9WFnftQww5RRh z?{me(yAsm+1vV9k2%sxY&Hxuvh!BmtXjLej1EWR1oQU;a*}8dCDTwT53wI8~4hiJS z-75uwCs?kVAmr{}$C(6kX~yHgIToIRd7RA2aV6VKeF3jsUlqMQn?*1-#&Lapbd~Z$ zoRqq|7#cVTet&}Le7;6#Aecy--Ym1EZt0z%(o4!gI16U8_<4#wXL42~53vu8ph2UO zFb=I=7CwS>;(fM8m-+jp)FW-7-Pc{q&jb-K|N7&(jAfqs&U*5Pwk4jR4cNPJ!%Taq zQEh-gg6l7GS{^(cb)2(gQdIZU=VVM7>ryn)azM(isr$hgv|PWszJd*+Tn6QD_rnQ* z+LW)Sa@Qf>x!Y{Z=%C#o9()#a?TeyK#3?mJ?1O&2O(?Ln@wssn7C$Vf$%{yChzaQik9s3hCH{@$+CzvxelDDTO@C(FLEEtbsI+ z7o3~tY5E$dR~ZFGg0eYw?38?oD>z-qtfYTapeNYAXM}*Oolk@*9cpw~v3MNJ-A$wv z>BM{ixb_RLF{8D2cs%Mw&_~aA_Cu*GA{pF{k+rq`s~qO3*NDYo<5>bt34|?WQ*Gl0 z#mFJYSKq(o+gMvyH71NQtzI$dK4zjCF~rmA(B)A$EjTqJ;&H&CrS#mNt*VymUKO3l zVVDNbq8Iuh96`S&{!$kN8*x}hH{O1d6B6zF8d?rY5bn_Ugt|8?Y=kkZk#>I zbQ;=c)_-;qwC|&l#A7lVSl#wyPdD3O%Csv*TdwynkESUI`F&6ka2Q1q$h=GQpAZt* z)wtd==aT))sPo(Y_`|t-HHvLSJJ}eyvfD*q9Vk!YEx9^{*-&JE3^`V4^d1~fR>Ny0 z)D(0jBjHZWurV^_#WV|M^yH&|L~zoX&R*Hzr5pnG#j~NL<@p%}HTfk9564R+QXZ5R z#o~K7%590u+DQ^puKdw0<>UP}8L!!U@MH=xo+*b2bKa#}15A>^@W9J4>Xh;p%g$T{A2kY0TEH1{_}w|E=wrDV}wmF>=#F@ z;sPh!HhUuFfCH^j=bp8 zp&wop&eXF5H(|kZ6umL;MG(;3D>%p40LSi5<>DV*6xWtsss58eh)-<9Erq-@OO^?K zdU^8i6UFM)9D*OKVf!*K2z(hQ>TJ$1r!AKpolbrOin`(LINJxk8od7YiR5Zl#IKZK z9e*79O3fu)W)Gtu^S?$(Ca-bkF8I%i^coH#|t`{-89E-vQD zHuA$e3#V3pwtuazKs#HgHRM&O_?LE=q~Uk8J; ziWQwgJ6VVR{*<|Ys^wWQ`gK)F$N+s-Mk}~Gs7i|0-yEaU-go84ylK#TRY?q!a{hlB}SKec}Tcj zjoe=)-sXg4+HN1qx1pooil8@AJwTh_*N$xWd7%WmL;RaE1A8qWCV%OSHvFQ<(`Bz?MmG+r*;3df_YmFn%(pD zHhNop?z@w9ouNT|qc*SJ*C+SnkrYY1c{P4mqw+_4%%z!BuM41^*Ss;m9 zFWz>HJ#mZ+r93|*%4oGBi`}~-59{SJdx<3a)@IGV5- zOeA-6;*##uZRb{oOU(p13-2=ddd!um%razH$6$f#_A%tMFF`urEmnW}kI$=1GbnDZ zz#7>z#=G3JB{+EOM_1%@RB+szyb_I%1b?G~fuXl8H_XP?ZSTtQD0ILYPKa}}W(3+l zsL&gJ?S&wxBEe@SVmbD~b$X0sSI4n#=52vrcECihs?fZn+%rHCisLduGYoctH(%70 z;2%6aGJa8sHr}lqDtFj8!0oIpkCVnvHcX4t5pT&|{_|6-pAENRMak2v*c3KCwg={% zW1Hkwbf~Vir`h)@-bT+Ab0LectTw2r2lln5Dz$a-*NDeH&6~QET|=bT-~xw+W?MXjX`5y5 zNfUL41Sm&<-%r6sBt>y)hvw5sJe})+XL&la(GBiA+;fpa;u1xA#ZM(>Ih-JcCyXbg zD(^-q_U<;k#6Wc6>+?hEo{(=WAA1ooT{@uPs`&f>}cXE10*dSin5Cu zihn+dH7Q$W7DF2d2n9)RJ8+?q`nDCa6r4=-vs@1izP#_2rPUN9qt5BZ`;f@M408ni z5|2G?Uc0;d3XBc~Spv-XPP%!vL|z+<2>7)=wDO0+u)@?yv(#HgJSgRdjO<>i)vp;n zD*068-X<+jReRoETgiiJQ|<6a|Pk8 zD(H#6IUKCX%_Z5iEf^Ma;#8~;M0%MwJqfE6OKX?8$%QA{W}euSZ_9%3`gAKVnO=xo zOmvs91f36AJ7G|uV zZ`$NKH0&r$>90Q{=XVFNlW>OVVgjZ0JV%U9P(zlZBBgt|<#&Wbyr-JSR0ZLishYjj zEi@?onYs_QIOM9`Yu-*3mm=+W3`a!S6=)AhUR6t`>5vkNqiZw^RkUii+4=UdAcAO3 z71f_#jY#se3fOXI8V4s0R)2Yao0nGo(R|I5k@N;1Ga3|QL|liZEXU=Y?z!Y=#a@c@ zgd5)ep7h+_p6^hZCOi#GNd{4qVso+C1vKvP1BlJ|-8@=~Cv$*e=EvtuQ{6g0tT2S_ zY$1Q>ryCsAg#qh6+T&H{u5M6l8EO$uVLlMeW~Bh|oFCa2cS0CAj78? z@^K-_&dxq?-2ub%?(~0%)#Wi6JOOZIJ`yr&^os+%yzVJW>!Pe&%wX(Bf@X>pU1 z8@#nPME7xV`F;hbb!NDj{^Z)uU1E53+Tc3)0P)_@s4WL5N0`qBeml<KVBUh+jO5CyG^u=w^6+KJoEFjvtk=40_yOitT;Q=ht#tUfMok&y{Wmqai zvvvY=NmMYen;BBJ9*F(F=|g+@ppTs0yeiGJ1s{x*o;p3P{Q4qW;y*Fj|D~xZO1_P? zR+gru<3*FO^)}T5UD5nJz~p>1t#tA1jos;lpoEulH+^;Gr}#z+yI{5IN>KUBLHrEh z;!^{OztG{RKjw7fPG(AM5t@${Y+vjAR7UDTTewA}%G)y%dV9NGtwn#IoCaq6WX4mX zIspg9gus5l?DO3p5uF4}U7)+QT3sRPc-HDtlefr-PVpBafkyN7l?M6!j-WUGxe@~$ zg;Ykgk`^L(EM~?VyARRC!i$|nzOJ8UQatGd0>m0c=$TLB_9-MzB;N$9e0?cUxC58sZVy3tXkQXNk-R?fb~qzLMXlJ zH`hrWriRvYUA!PaI5#yUm1$MCd09Z@bH|3GNn{s>OOmDJG$4x&eGwQHN~EumJB}ZT z2(??*4AHjHu;ovQ(p=9wpr@vi+|AEt@r;l7uxXZrq{0Wk$}{5j<|wc#Fhw;Iy`+eC z2t+oJ{7Me)UG^4!U8IRm`w*>FOnY@-+9WR*m3mHy?Rg-;t}LV&4?f@ML1qTU-F(Fy z|B6sr|5fsnN{KN&eAn-`BR%H=c$s0BaX>t8pyRjJpygmf?zEN$q!q1nM4D+{L2UE7 zoW}aTWPh1?jE||n6brOiqFnjSVAl{oFEKKpmdq*eEpX46o(p@_x}OXTzs@!AOy-^E zx2tV}F)dT-C&-PadR^|GP6wjgsL6?3FZ__CXwe_#v2yjC#*r7i){5GL)8IC^^!?iV z@+J8nhi|O<2anehd`_ph0RjQv^+RnRy(!|Ejrh67!xE@*s?&r6>7Q@U!ks(c(Kms_ zQF$`RqdQoKQY%8?(#~DqdP1X$`zfK3@fl}bm`%^C>ZW%SvzN$j>{sg@tNF3*3(e&ez1l%!hplU4L0z4|MUQ z3;l6C3JZvARe#Sue7xf6krZl*#xcU(uqIR(bV)hJH8qQL##_7=?9?7iu}vE>qYv3{ zK?}P;6*-Y!MhwD|>EYJb-eQJGZdq{0qSZxhzvV*4Zy@MnlM!Z0qv2#TKXx^%&;F1y z%6h)if#A4Oj|Gv;msqPsWVF%lo2(xn^*XD+B!`{R9JJf2yRFYqW}ZOv#xT-uV77a& zZ7J0pt&m(h#@X}c|KOXx7kgrcPuo(+QX$+-86TnIIM!c-h%wt@=`hNA3-lw(%CW>9 zbszP>*j-EDWSop?M;xYW^*>-$<43;*GPf6)C>}~@zy)&dTc2!6<~!;|9=_m{#h6Rl zWJ`HaGhP^E%OF=({lolWIJ$*Jy6c08b=uk3PVEGS(G%Zy!5~}_%@0`yuEHBH%Dpq3roW!)My_iUDWptEP|M zo7>a9;kD#*FGrifq*miUVhJnx&~Q;Bsyg4H=OudzC|@KQL(0n^O(P$9siV`{aA<+yU5U)ikj z%!N)fk()9Ki#3$RhuH>IS<3rZfy0kp#!H+q{0G7M%%Voz-DdM3;Tmo3g@4)isl=DU zQTkS3a?Mb~tTsdOyT#Nx%vMk~5mG%d6RyLZJg)Tp7-{OYHce+Npexf4w9E= z3QAf=>9J^Dx;xnfE%%>!!Bpy>8=@mA4Xp(z*KqJ=EJMB}W@VTa@tf(_DurAO{L$N^ zq*+mRQAM?)^P=c+9*-uAg^OwC z!9uY)t%Dz85&H%Gc|YelN(?e?tn6o0>KE9wAuY^PyK_GX>hi=H*mgpwCU(qYugt1B@Z*@$f3c#DXxo#=cSsa*vpMGO<`UQ6hPf5}|@ z5FCo%uAlY0R+p%c$A)ll6vJgTp&rLt0Ez)f%#QV*#<{{ISQV1jw(N5zV z$!?u4K;u#hd^;ffY@NzKqpU%w&0aVn=!XEI2mB5rb$W#$(~frtD3 zw|A;YFWy6L=f!krUG(5%G{HPe%?kL9UaJROdq>B-@VqcE0L1;V@D6ilPP&&b=E(pp zEO|+=7W(`5eY?#Af%|-i+aa%?u15vUg*0*Px6oNXw*$CYX;H!7-%DxhJL{5RKpgXr zFH%v$boc0)oQ_|V2)qSnT^P+TEdw8q$Q&%tLCl%At6Y^|Zi*@T&Fe1*_8e|Ue)nwY z-R*q8&PNB;SJ46mYdb|m=V#P3?2$vwP((cTG!cGn?FC-9JyLqjVyNJ5A=2L@$FtU| z$Iff@#2{`rqLCj2b=Npw5YLw#SUuozSc;#mc#iK!awpse?4oXI1C!TAOxIV&WfKSV zm|mwkWUN6fzJ6n9z4V(O($#i2QM`~pGNEt)Do79#7n>;rBEZ8^m^LIj{HD8tSs)T@ zoi{s`R>X13Lv3m;#v=uNui?d(ce_5`dyj)Zk_)&iGzEq-c~GwRM}eR*%MEzCj$B)| z5)_);J(;&JeTx%Rz+^!Nx*uv18gnQr>*yFJmP8kF52%OcIj#HI35?++vsFGUR+&_t zu)A!LYDqV?E!PEi{|@;kRf`nK){-X^E4v>1)2u*#sm+>aBdDlGFp862aMaO56r>U9 zoteDkd5vZjG;VeQZ*f1=UZ_K~{=VJf1ptb+1H8shv>tD&M7GY2wYU;u2o`_Yr=CA< zeft0$`$s&9xq+oGo)X<`*M>XX#x4&%CO&`}8nNgq9w;qR-yxQ%*hbso?*7PcvAkhU zPC+wSPYNDr^eR%$65R|En*J$9ftC8?eX)Rn$6=+p$oOqo(u5JFpDoZl(L2L+)*~m# zAzv_T1p3?|O;E=&Is4O1?O4u!{V7@SrKtg@?F?dv-@VrRxA1`25Xer^_t#IFyH0EQ z**|dl!bvMCkB0K?KxAin@}JPR=x9PcRBdb5579PBE#Mv zn^kFRR~UoSje-8W{Jiq%qs5;Uoi92&c-@XrN0R8GO6N=EXx3pyQ<>C!xSVF7^y;j7 z0f{uIl;ROZMKr>%N5PTR0P~3-eACYz4_f+tW*_f?L-D;>6&wDO7JNh+ruD&J$x)qi zspv3KXK<&2Bk1EYR}GfxZ6P~x`BnXzkg(|D0#4?uLi&Rl6M=ym$D!JBHrkh$yx-0Y zyiFgnJC+*!1;oEfR6D+4D`s;_+@&18K68|6Rz}tl7j5sQNz0k1RvAk#v+uL{OsOUx z94HA$5zQLOc?G!ADm{DzRFkKHxaD6yR|&Ynrvh5sPtvfyVP=ODXK8}_GMdG@aMlGy z#+`$>%i<4? zD4fxSM#O~>5fPE9@9+;Uq*Tt^{XNha{6T#C=Y{XDB*2N}K{T)FPbudUo5M^qp4DV} zs4)6uEr=^~TCIdcCSC&KbJ_1sbwh%@Ku%9YheJXoNNg!zH(GGhXm(5=aH-~h7ld1U zxn9@U7*DeI_Dl$~XT-k3b}{W~vq%h5_r=bca_tPB(>@bCWlvoNXAAneXvoHAd9bjs z7=n^iS+cNiF$q&OvI#?>hL-wN;M zevA)!;V4phmMe~t;$c8w)d{Q!OBeMuk#4;U8N2l`IZ+J#Nn4Zoix<^=&`KFkJBzWV zWQN!Z({K{e$8aKbuFi!pEQaaUNkf^<{Iif@B833Sx_`h|0q^sz?r$%p+OO1}Z_Na; zL;_)FtBt=h;u^i=zKOm9v_}S02ad2>^F8BhX2D)B@+QQ2HyLu*De0Bu^+U)5Ynu4} z6q#sNobZ%?i<@HI!@^Q?slH|1@4v;-Dh?mi^UUcu0Oi2Dako1IF(ff^iG_5-m5yx- zR)AD+x|Z{m8WQc9ttT@z^nx<|hSpn%ho9P6C*s-nv`j+XL4h!^01|X|V#P=rSc$5Q^#UBCEAhJN3X?AE^|lAe${&>p-nh&@zP(!f2r3rw0sLlm%cM{7q{mic zamJ3KDtC#lIfIHb=7lHAGi-udPOrGy71~57=bJjX90BjIPumYmIv5pHpPeuHv}(8) z8g;8(z#}o~A_0j5Wyp@2vXv%Xg&XOt+}sE>qs{c}+#7OH2Cl+f8+RVZGx7qk7=SS? zPx*9i04M+8%-(3~MTs;`ZR9+=;4H0XaU3~qVKVA|gJRC%oE?|L6lxdCGZ9D!1PN0E zSZZ;naXTC-fKAINPBT0h)4Lol5^|N$T$2G3Np1H?Wu7CtLs|vgdQ2yl2`d=!4#!KR$Fe~I+Z#@XI{6D6&0cqr_&~OlnLPOPJ!u^3 zd<;y?a^s96d}tHagh;X4XbC!xkv%+lI}rMn=O+eI@Q82Bx>%x0(#4r)Z_m&kMdPR$ z>AvRO65-;OpY#~p#U%lJuW*i(ME-I496V3^Kdw zo!uqoWv`{M3x)8@=LUPy7r~4D|iw!^~n*QFHmOi*7n-V(mL1_O!D6V z`)=?hUZ+cNncv4!m<%Ebm+R_6MxNNElGyhBl?RdmbOI9v@+s;|2jiJ2$9)TV+7&A< z{(qP>%Z!OuCGj2Cn&Cygywp7!aK;RH874+pl)sbn@}_2XN|Od0z;(>Co;@ALTk`BHOL)ti&`|wJ6%g z*rCzTBzAw9_MycKd(6x?pv#q=6fYOgAS7w=I8MO-XlC9`^->vBIN$6lI_bulvKdR6 zVmFd6W~>vt|50sR{h4em?L7*9q2~Ei{rt zzZH$gvGsU`F~jz`*~Ri!0xoqz9o|ZyFeN(nxUH>?!A+YO?h$A?M1HbaX(XbZg=MVK z^Ml&*MIRS;026Sc{44zrso{{Xa4m9Rn7o9K62V>bx zSqKD{KL#!$8)6#ta9yzwtK_XM2X1Xk35kSXW$VLgI}T=@p@1vTyel$sHrZFy`tliV zUT3Pi1&l`LYrd?3E0gjNuWm=I<+^l2ErfjeX!$xF^!f+{%%ZZR%X}4f`7xPusW`NG zeq?T~2a?74_NZX{Dh|H{2%-rbEevLNchfK#3Lkdf8-|(&! zkyT#Lw43wK=n(bD^Nl=&Lgmb2+4s?3o5eWErGK80>~eFX*YW9f!z_tC9LjTUk3v^G z*Qi(sEa}<1;D)h&Z2+Qto1zGHTX2bg zX^2QqUO(L&mR@CtA{;Q3?S{o{aGN`PUmWDY08f|%VieLRP(cJZ>vK96#GXUV%m&*X7Y03mprodLkn8NW4_p4S+e0ndFCg{%eg25kM##Q4qn)@r_Bq{ zzQ=c}aieq1TH+RVr>6Q|?-!gbrG3bFqWj+$-YOom629T)#6A?uTfKbdR|Hir zDbH8-PcyFn6s(B4$%vu=s2*sNs`oh@LUuCk+ACsrGk<{~`M&^`IzI%<%eK<--Qqrw z07BoBkf+_l=6@=^J~(itde^TCF#pzQ{1x-9p-xE>{C|u>bb-?u3y!Qz8>mHu9-sf$ zypzt^=u*EkBf7`~I zbS8{QN3)t?)$o7SI)C4{yv!GZk-mkFI2-fKIOP9}-u-d2NYrzxCY2$J+x5Hj{o5Bj6rX zQUi*6o!g1IdHgmT>~ZipZGP@-b_N>Ur!;6l?i(8$!-s>icv6*Y!7F(a84$1|4;2s? z=(^qWN$a~}I{UC!Op9?VFGvMc-P8nR%lfleMFCp$&7k@SP#H+UifW_7a-5L=J?`!i z0e;9{glKL_EQj?3BD%srG#qq!w01Y8g(es2!`5S}Si zic-syrrT*iESltk7$ypljJHYjFEG~-=Du|9dc%&v=lUz&(t^C0FT>dg{s?3=YQ=ne zzU$rS@Q>&Bw4?fz%BaUaU@@C7_YH(kU!@ZRemLg&-JMK|#(`J`Oj=d2zk3j|pwCbKi%F;%Vh}JF`GtA~mw0TY!JaMP z(It+uMEw9r5(_#lBk|wU#L~!;9&P}AZ_|Z+M#8dlgRw*!=od+J8o5YCLjQbj&=~i2 zcY_NH3qPK>T}-ukJI{wuiv1;)L9Yx(piyic9Yu(JgWlc+iVVz`>4=$G8sG`})t8dL z@kvTJ>ckTAv6}Wkc`Coe-2GV;k*Mcp?{Im#-v6B0?zSH}gGl9F?(xJ4kpgRz+aUU_ z)bw5UFT?d4M2%vWs5>r{XwZQ0ZuOGE$LY_zDmlVJ{2oW2-@oWmS_&7ySBQtg7i$zD z7Yi>aQ^cvG*({XfxgAc#3@6esC?PlS1$>mu6y%jIE(ymvev37)P7>v-95uzz(a~{F zlK~Q!u=Ypc$c$%jVc8M{oeazdJ0v=YoQ|;*fgoc#q!3AhycpXC#AljC-xkWHcnTSM zF4uT+sX1NLd1H|1MXPV6&RV4adbe4l!EQc@a}0STQMjr4J#OM1ZgmRf}1sZ zh{dE9k)j=;#^e(tu9_^*6+gYp^?IlFk9_$rH9+?%L`S)v?h~z%^8egaA52Iys$*`< z^gz)Tf9yZ*`>z`|=7Hjz?sQVoT$K5*djb|jhE3x9?o{Z1J}hJrDMWWXZ-2%{Obkt- zq{E5y==uLuDKf);|1PYiJy-+4V94EH9m&W(Ta`Rh4BVLCy# z$%)U!h7gE0u+9lA#C`}a=}WM+*!(R3i+m?B!0DT43+Gt_TFw|D9M;O;{Fhr>4-~UM z%@z1jpvq$A?l-y_PNuyyxjC9E48~;RFzUvAmK-&5J6WiBnX#wI>8San(jy+nqal@F zGYJbMSVcw025FobdWV@IiJv$78eRrXtrMZ2>NMkHupLmJDPg0nEiGd}Iuk9fs&x^7 zKai!H%#$B;LK_3T8@LsC_;U?GCjPX6D!T&SduPOMX=N!-b>XDCp^-;o&(*!nq3=@i zwXAz!Mfr(^j~8`(1gSUuPbMn$!?i^@n00sr(}SS%ne;D*`7zrg43OfTqB^LTzdCWP zT8!dyZ7F0_|K6ZdrwSZYTtlDP{1IMjIWod5Qc3?(rc<@GIs4I5F=JrYrRSvTws&OO zz@V-5U>6B?vC$R<33Fd|_8_0k7&D9hew{o@tCyQ}Z7zN|;rsjME6rbk7F6|7T0iOc zLyce{l|@JF?7H`2EW4vEeubNB!>_CszBf4dy#Y67)Anm(k#cGOW(x-DE+L;A?uQgz z6<@+%y#*@-ppc&$ytTQRR3Z#9J}6*1Pril4fac(;))pJ}x;@|l)=5w>#?iX4m*of? z-okY-nyCVfa%OKvLL!bqLT@cN0BaN__*bNZd6qtGCG=H0V7iNa++Ctf8ixaL6gM< zaEFXOuI&}`gW&03E1VfGodb&njjrEglCw}7xhh3?qgML;OY+?;8DsJ`MyDDM0zBWe zyYHKW9yg1Y^S^dD;`6B#R055S0oivcySEK7;*Bv$Bo{E@&_k0Xwvz1Jgg14{mI+SB z4^tmuvdvz!Oq5E8p8hDW--vhQd{{GdaLLp?Bw4an*$WaxHopk)o_1i8G^^ko^XpQ6 zo*h)6`uSlCg^mhNKw#i*?X?3;OvWD6h^XV8 zj)_5Pj&JMeuw7Nsz@7CsXjU~Po9dwtxGUwFBW_x*wboE~b#bYVdopi`7ld^Au(qd5 z+}3Y!h}r38w@x%EBE5~&vwRtORZ!tUt{CYw z<%-R@G%jGB)Kcbo9gFXlf5fRQ64hwEvFRQi{I8EY#PWWZvi1 ziSkxux<2eGdzgkLQeHt3leK3ZKD)@XvsU3KK61>sBPEQ4cokY_L|tcXXFvneJB4b= zgpqjej%Xyq`<+)#9O(vfpFjF_(`+^JMgLtZ)DVR9zy7=r4;HKUum6~@ z*_BcIDN43Cl-+x3{R0XL`t$Y$0!V8uak|>1lRwKhP+=Xb$>Y4-s)s%7s)>HOuduPi zs9p@LVtIvp&4E+dQO=y`Kh2Trg!ACAQkI!7EhNKYZpNUr5OOl?JGdTHA>>Hr8LZpq zqA672gn;`Z8cDMPgF^fhM8q_^?aM>_HkBuj38cO)?SdCNVOA?$`++x7Tr(|4upxc% z92|wu>sas0w`z@sP7D<`nf{CO-dGoG@s?`(=bp7)^gPRv6Qx!S9U6w3waZB89~2}x zyxaldNC#%A%gwx-gPN5tAabgQ!fs@m2!!webK|T{}L`M{~_fO}$YB;RaldZV?t$aOS z<4e2jmGlf=d#u6b@q)2{gzG*Q&J2?K zMz1V-UDui=UQnuC>*zK?9Mk8k9T79eDl`=mE(o}gzY(#y`k<L zQZp?Z_TN6~oV`5~1rDY@Ti!}|#A^GJcMjd<=j7YmGA)ARuKOFV-#7SvYPJxlDE;<# z+O=rsl(l?OPG@0t*3n5CUsse%2k8vW4;CJ(KXxuIQQE7bvkCiU?S{L%(VffLJLQu{ z;O%2$BztEd)hb+c;uI^?mq~NtN*>N2ZPd>RlJ6HdW?lZohtrP^m)WbaFRs#NwEjE*AY+@8jg415&B*6Y@w%ac2< z7G~Ac6xXPsXI07O6NG-YUApZ8@|*r?WHLkD{|bugO7P&x$jFYCjwzz?gp@-^lj!Q= zd~p;rg{9DLx#2{9evn2JbHL}^K4Na0fnnYESvaKYYtD&$uq(*5-<`}2f`DzcA}=DX zPLz*DaHh;Nv*^VJPzy`p!k*M%o#;(Lp4+4ZdL5D!1g7`i7jDh)+%(5sdhTLLyXF6$TzIT> z@u2X@_ns2gmYvH=I;KqD2kbTbaRfLlcsLcfs_2N*gQ>!~NufT#eP59E8NjYmgF{S* z*->d{RrUj=lAt3Vz)c+iVbDJ1K2x{YyPC_6Y}pTQi``>kd6aYo)E`agm;W8YdVN5vjCkQs*O{+>BN~{V90e9rUpp2o zoN~kOanIDh*22o&+1Wp*e6f153AC3Ia zA%PBU`D3#(f+hHN?Le3;2J9#JiuF5+J3(8Rap9mg=Q{te>)x<7Co9u`_Gn9n|MMHC RfsPPi@O1TaS?83{1OUrLpy2=j literal 0 HcmV?d00001 diff --git a/static/img/dnat_netmap.png b/static/img/dnat_netmap.png new file mode 100644 index 0000000000000000000000000000000000000000..3cf58dd982d1a144db1c37fe152d5bde9d8c1795 GIT binary patch literal 19075 zcmYIv1CS<7uD z6y+u0VQ^r8fPmnoBt@0~*1o|K3-v9!}0RsQOJ`j*JFz)~Q%D`0rg8=~o0$2fo{SQX_pZ)KW{5Su- z{XZ5o5BUE_%mevfbZ{Q%|MP+W#Q_33RRt;iXP_M{wmUZ;#X&=W&K<_Y2hIF=3sz3qaxM z4<7S(7#QpD^=DySn`bm;b2Id5T}`r^cQwCeK=o_C6}Ta4)093m<0H=>xtDi3&6BRj z992qxf$V46cZn-#Yt`u2Dm-{VrT;|a@kk@iey!?G;#hL!reC#1T;5OJ7z({9tX!&BzV;1s&eVlw)=6h_`I7tsa^&8 zeCzhSEXb43w0KrU52PmS}3Oic5WOcHPd@ z{)@6uvyqf&9mwo8h?CS%rWh`KL+)&L?P1qzeFS?gU{7ZO=j-V(`>Uj`u2i@I6%K@Nmbh>gLAJWtfp|S{RapU|UcId?vX0U36UHDU1%YHW*)r4wc@n}Tel+dZTTDGRacpRs*-cu`>CU^)ZV0*cAnmB%j?s{F8M5JuNwh%VDUam?B zx4&pi1H>8Oz&oddFZAys{!m;nO$%bKx2kE1(rrdKZoIr^Zy7a$;PcJ?^l&6J4U|c& zoOy9lp*;Syv@2jhJryWqBUR94anZrVjz~|j)_rm{#DeFD#A1PNeSJ>K+dLdTFbnbN ze&v*HoP@mp(k{NbW!t9nG#*I8?k#dE$3KK~ahra}& zsG-;}N_?3lc_YDAX2`Wc-*M7e41o4{8w@6;t_jhB<(2TnLS8{?FCKmksyIrX!B6MB z?LYbhz`(g7g3%U6=XKbeMBvxk7$Zx=aTcACWq}sh^hNf+qZIQ6Px^N4t*Fg)dD56& zdk0P#p}kr35G@_Q1W(5y;1BiqfWibLS8`h@ssAE|19uM@U#fNgG1PjhOAj1NSi@1W7uUob6v8P!CcQ!1q;QY+qjtwS6mU- z&y0NKg~vtp51+^Z)-E+3nj<)Roi~0*{o?MEN4()_(ouLRN3U)9?he3ynHfK zuFgS0p?jUK>^{A>&5O)pZ0$XF;$0(a_U*-K1YDWuZOpBdcnh!IL zfBpytuMM^3VNk?RnR3~Verh14Wko&;iGYk(5Lfq?jq(us02ZgL*e>FK1Lq^tZ4Nrs z)g|sG`xf?JMC%-}&}t`pK{sYj&4a*CbBnfe|}*+s@ew*`o?2rv81d;jLT?_#=71 zoF(cOh$vg{N@aI`L4ChTz^N;DC7r20KIzm zq<@d2fV;g{(ibx6usp_RmmbE14v<)lDOeb~5QA&|@sP1e4I^d9A+h0u*PLV(eiyTCdC7DL zYZsuq8*qc60!D-t)O{yH$j%qIb(v{F-AW-?Z&I3cw{Xw!*iNnEr;x^8CpR$6*1d zF8u_09`t59U6MB=ZcRo}s-8{r9h`4Ek&5&@cHq@fD8n9vEKC2cK z&4(_6!9JrcTAu}Jzb~`G5@4-L9%c3jZ3FyO;Hx+qARCVfFx^%0&9;hd1SHP-~X$ro_tB)PARMG-Ue=b=lf-oAYg{oi?`!6NHGcgzV4{Ai3AeI-Tw zTZ`e)+1LG4&OYoWyo??oe!X899Pdvq4Oh6FOvw&cAA)d!k|g(-G-5eyLt9CP{~DwM zGV-{{^r_m>1D=yOTy_?~j(h3h0|PX+YpNx5o{?H^$u?=99U1df7CtouP-% zaO06@rAjIK`{qKJDUhEBy2Gb(0@gt@p@WdE4{889cOhFFEaC%r znIRn_oqKe}XI((yi^+4MSN+xDV>s0~t0Inj6*OwIy6B;GB?y6qWSGcjq{%hJ`$I}i zac7yVzdBq*KGWTeU)#pzq}?uy$tfaZy^qT}7&o=OD5LH!>+6AFDP6DqZqdmQGK8*| zS4E0nC`Qv03~VL562Sq|cw@3H#1kX(g2)N}L$PQp0 z;i55HF*N*1O2H1Oz%n2U;gQHzN5|$MMO_nO345w%nW^=klE4Js4!>?75m3^{D%`#0 z5pXQZPRuvn_ikWy>+SxcVj;aaW0U11Cp zm8Scr?~6k*1aG$xo?D{{GSUDa5nPwFhQTuEMMmU@=*~A*Nq_Ej(E2IV)cAe`jj|(q zT?O1rII2rJV9`=+3M)v_V+t#m_wi#07Hg07Xv?%(6SM&AHlf15O_%OliWYHdk5GU7 zWc01dBeITb&Qu}jWw!OzHoTYTCKsIom|v3&^^W1ZCeAX#**Le%!kHjr$?+*OMbEw3 zH+bTSMBd>;<#kh22_%0_&v$Tccx}Kp-pyY`DLMQxE-~T>XtUBUc%pf-^KH}h@gh*jmbUH`0A5iKFCIgTT&`9L0unNf z5h!!>O^*TzQqtM z)DRad)3>?9UyK|M21^EI^xZ^;QHtPdsQs>#i{NK|YR3}TfZH142;%i8qbwv`DI z61s!0u4}g3gx0nd6KUBA?Y)<8U>FbK!h?&RB{=zYff{w&DRzg2eG)QVR;>q?VL?@d zS<-GKk&a`X4W@{vOTzXdB^n~JM51^u z6j}4O(%_i62BNF9Mb$aHq2^f;-eYLdvw;mwk}GHhej2YCZ8|?#H;~!xqBzRw@ugl>4DQh|x;b=kzev(+pjKnK?y1zy zebU)~r&U7A=5T^(rH|J=0Ac(NDsQx(a|wCVwZ@1g8XR*#i0shQ8n}*`xTfXUUwTsV zu*86O+@KD4^wJvHHrOB8&vu*I(U0>j=GG)N8Ape!TQ4xI7jtf39^cdNZWwTy>ucH8 zf=|jPu*l{{Sp!W<$igGVE8Ma&*@G(9)%v`>;N5gPVgjM|3Eb5gK!9a}+H+6-b306c zd!4BTti+-N5hVp+hrE1U_>{)$2g2zeau{C~L~@ZI8mp=RxTQbM(1@PWI__~LG1;kN z9Qj{V2D3ywzDs;KfN}|Q(nQIfVX7O(2g%g_SW?1^RKU0Wc0yN>pQ|v*r_vNd>T2l1 zpuHzeh@V>GjkvUc9hWxbtFEoIa!${-8@@yZm^_Zja%Khy2Ry9pgXlU~n`=(d{rdg7 zT;pqas@rNs4>9QK}3wh26Fs>8PzA`1K+{KP`yb$s7WQ#_KH6Skg zI!0QsHy4LEXuM~t8V4k_E&Je}@x8(KtLtaZy-Dhng5j{zl+hP}jwPz)bM+xjM>iHA zh3~w$g_rMH`R8q>OPMyccD*=SCsP3a$G`|Y%=4o1uGaO}(BI7-jaRl58QR(DKfSL+ z>hl&N2Czn;5Nmb!xl7IA(X-~bk8~22Yo|)QJO>xWJnzvUXO#w;0YWW#z76FVkeB7Q z0n3zuKIrG=H#iEsZr2Q_D*GgKeTp+rp%R#?B;2W`dm)l_PCqA;Kl(ux*1uI`!_jE- zj6=Y&dNx!bWiI;yrtd)u7MUYl(X>G8-M)HEazZX*;vs`iVRo)u2XInWd8AD;>1iiS zc@Z!*TChns2|{?WOsTzGfm>f7nT9ugV+sb<-<6Rh41I|$o1x&-evkfDNd@pH7Y!WZn>{C< zXqUYM1uClY!R}c*VeIbQ@Na4oq5GzV&PXs=J($naIrdk}HR5P&yuxeOClR{x%UJPQ zS3NmG={sCFV^j-$T9cy7^^_Yt1z(oYyoF3F^3_hW=2Ja4%p4}~3zbj$a0g6g$pmOy z#{|+%5(a71h(9LRa$eG1~IKI8vV^5!ZFbI@tPc{ss5hWbcFd$~=CaR}QN4weyK`yy+`(iZ@O~ zT-5w*5_*Ac6WdoQ?hdTD0`q7%HK4iIbT^jU&vqhUK;j0HKZR`^$h z)R(SmSOS`Hw2V2}^F5gBHivc0cGP^zPbr)jPn1wdWKc+p9R5+O@gF_*z<^%Cc;4~m zf5cumSF_)C#`~zH{1;$5TdHuLY1>6SPJVDrjrloVu_H{xA``l@QN!I1&FBC%>ChBO2d2N!`XSAt`Fz_%fcgm8Q+&>m?Ly=$o`#1?BcDZu>krq z5`SwopPwFn;Q2s88NgrJON32QN^DJs(Yc{X9`@96TyQN-5_)|0s5HrNB^TEWBxV^1 z81+kw?P%cZE|8Tz(7?Fq-{P1(hlv@au+t0_8WLk09*)tF$PXDMd}{hu^gJZ8``L3G z!%kke2uqSn!1*tGOitbJ-HYn_o1s<6JUboNTJV-66Ku!)+l=u6!EdfEYUGaz*MGq- z_VbYJm91`7bBCN#76aUNx7#WA_ZvryCQd!Nns*H|k6rfQqU(Tz zf%Y23ei7UiO1PECrh%SWne%$MgA};%DD|6oJqq!z$=_G(&Ph?60DnGjH^wLAl+BdO zD%9`)%h@lv3W!t!@+_BEv_ea!Yu^g@n)&kCN=vxtn8m(J;;=N8uAB#=JZS})X#>W~ zdmCmcua8kIZF0dz4YzPK>^f3IF4PWY(Z-`!6`?cw0a}#NeU~aD?9O`!lk%4|20xYp z^4STISyPhW@;i+VAJ6ng0A8#ijOPb(^&v5D=HFd~as{v_4xC+@o%t|?KH9Y*%{t7z?cTkx zmt(#0`DzHn;6}?n;QXuZUlrSENt`uO8jjOK9Ur&E#3}MBC?RL(nXqgy@uosi`B>1i zIfimLeN9swr{%UzX?*qIcr&4JVqyb&ZhI&iIN}h*Bq0&6l2gb+!3&wW-orH^1C!5D z+9}iUs_n2Fla#K{p=~vQ)XXcIP^huFg~zf}HQCg7k1QCWnN9&iS@D$f3Nh|RAO9$( z(*G0@bK90Z^P7a|{sA2Zh{r?w>K@D{76td&7XJ%>9~0Gm=xn9eS0Si$e{?j_IOv?Z7MGO%>;p6C)G-#z8$1Md$=69WN1fw> zI6Ts*>DD-|%aeV0N4&c1j?qKKygUW>uZ%fUQFCz$zt><~%j!$_=Gbw~zVG3Jm{;?= zk$_7~T|35K_Tj}V?=U@s{(6!VNy%7IxV71#W8u3vE3abgN#h|uU0)C_C$$n2;Z*E? z0%4JQ?R#Hvj-W+U-@ofpG$PF0jh_6v-ezpt&H%0VWqW-u0+F+!j6G}N;4=3K$^7h4 zsM7OkUywnIDzC!n-8erUCe+vMT5z^ao&B$msBq?V-*(7OBM)dRg*}KMw9&O#fz13i zMc6uScKcmH%v6Rdu2s9Hd^4tK3*_s{9KagGFudiAJT2H4%PwW^tv{!Z^(Jc#$-{N8XZNWI1nl zoSz3LsE#m!;TEjD93C-n!5DYpaUKGcm=m&ulPbA5g&?6^*ZRF_i@vh9BY zf45&KDLMtmot;G}+x}W-EZv>ywKXJ-8-ad-);LUe`&soLsBQwO0+bkwl@f$)Ey?Z)Eqz(K&c zB6hU$!qDY*q2@RnpKMLu-#+wrL@1_^3dowE(Kbb zP1GKSs$>O?ktK%<1^kd?f1@lfEKiUd0?a#g$bYQiFcjMlN`j1PHQ-74H~jcQH^m|i z=G5XaFE~H8w0~`i?Ri%KFgf!DPRh(;6GWr0Yf2(+8Y{tz?^Cn-%+9a<&Aoi373*xF z8AGOhWS`b(-ZT(O$$!x-$QDkA=?$TzU>am~ z8vqqOyZ1L?^3n88SLT*swyDEb9U{lig5$c=m}>cwZq&e^S17Q* zbwe*KcVCo@cs=^(W7w2ez@Cvy_-|&JTm!h8EY!(%mwz+LMx{H$$V`{q~qd)Idy6 z?}BJf<+WpLJDn1q-#wH}x2^e6{`uM>)6D4+5PA*$U(t=d3C+1p5$34r&F8XzO?nNX zNf&s7)gxssVL&<04BFbutPf=f&x}Q;W&4K_tQRctQf+Jk2h2UGkw7F+bKap`Dhmo$ znK4yKWM&s`)#hJrNd^HF9q%dxy%n=^;vsDMeBpZ>Jz+W;zVJ8D^fIBVo=<#-u@P8# ze6e#3jM6_}xkQ4y-a_PTm2r={mP2S&BIHN{2o(8eUE+Xsw1XHX&z367KECKuSDHoE`)tns<+~g~(~MJ02v?n0 z{5B1SQ=K(Xe3(o%En54g^5f@-4bH`uo0*EgP%)P}<&(=zlH-QUmUh7Y0#QknRLR_k%qk{RO$v)9MDVJa>!dKP@dE9XF=RqDzAszz`*8P5Y}uP>E%b%( zgL^PFg|~nr`wVsErD{!~d`l~1g;rb11Qu%WE&R1OYR_J>`S>PP)8PfukcpP{ zO_mZ|VRxpyz>5uAM{Gx|hU)Tg>I-l);-qVA+X9Nl62e8us1V}i5VN$6COlUp;65Lg zbgaKb4nQa!H+nzi^WD>}CHNveHkDawCFW%1qpc=w^j70FL{vm@D3ZLB7cFOPvI(k+ zexQKOyz_Hen?&$|g^kg!IL8a!>l}62TqpOC!-W^wG8$l!4!^faUBe4f9u&11#GDn5 zjz6u3RxOGBR8L`}UbsLLbQ;tYdWK?#p67I`qy~x=-}BY- zvolj27|XQcpe8Z#pb?X<0KY`9JVoXQtOk+^F9T+L}C(h`pk;S zh7%C6d>c|fL5*19NCA-vqUwoywS!sdDhUD-OyHwi^Rix?sY+twMI`;cLt;Gv0`1R% zZ1V@AXO#_|Da{RI7FI|~*9~ni#AyZj84wgnjRh&2ZYrj>q@BN*wq-M>RAf0qd?tK6 z85|Fwm<$Zv;s2vMShz>*HHoVlp*#05$4Bp!o-4{-`CB(;%sKB!B?Q9SPD zfvdtHs7ntkj;e;2&NA<5JP+!HhHoldAM4jbX0vNFC1ir3phMew^5AjX@#9}iRf%_a zf8lJ(mU@ z)tx93Q}U#$AKU?<;UJXsd{qgQ+9uYtsU}D)WqhqF#5Fqip8wer3|z)@feI|nCxhA} zfAwnBjVhpyIr64>A$!FsKl4q|)}DOHI?L#3w9-w{&yn$=kC0w@Y&}InIc%g3$UH75 zX}X&WNpD6j{An>jLqe#t1dO16PUK;t{5!_XaE9(A52(t2l69SR%{9HPAa^ho0m}k9 zjgYCUJDzyKG**~AU+8xB)9_13R7d71J*I?`#KzdfU&-?$h>!i65_ml2nQZIE9ejaW3xOHzS z1>OfQP9v2TQ2X8=iki-M2)i11pO19T*LU+Xb)VNIzampvTmI@*)D-I@e3n%{RXs6C z0~v>x&9&;G+n-c_L#E8Tr&a@Fhrf6}Zw7%S)W5Shw(DH!?bx`APxG-6g67T zq2-1M7ycH?%;=TtEVLDbnK{N3@VU|*;`_YOkkxn(F{g1pv;2k6)s^_0IVtrxMS@z~ zGm`kxVAXo3K;iN@@f0@;{pWDc`J0{C0%H5~hy}$v`bMqV2hvSfkQTeeOJ-3jy&zSJ zFx@gyAU!yPn+0Kk^P!A7TU&VtEZ#mtGe?R$Wt+os*nWI)Ms1w(1}jR!4kt$9Bvu_& zvl=50*Y2I1Vx4yMF`<#kdmmi0)td{V{r<>o6WqX)9L`Xqy-h9L z)|YIF`)qo8B(ko}YPwDgt-_=rado0-`^H$Y4Re6!**Em-*-mR-xHz-Besb_I@1H}b zj=MM0HzQp^1G&xzn|S#HbVouu0{xskkvbM_#_nfN1_BR9*oii{?-{}pcXzdnqnp-0 zmZ>sHgm+3(6_im)40n5vW0?XY*CHFIR$F0>C3>+14IsnE{vPjqoQh4btP;~BZ>+U* zcs}^<^k2MRI_;13f1h^hrs{dk^Dq#*-Ee2}c=CJ!?nq2a(PW2ZZTv}M7gGn~>v#LG0+j_}y zYE3~X8i51MJz56Q0E3Oda?*VdVFSLLE@!%)#ACoG$p9 zC4EPQ5pcxR0bZ_Pr0|dQTX(+AB~SwGwq+oDw{$gB4MyZu#jUM8j5yKNY`;H@)tLG7 zl4`LF_fr%~p>@-ByY8T_dt9h|Rqm2`%dvjW+d!y$NU~k-T_?fUsPdH}fl4Sv{tge_ zPB~6g?|jG@440$M3~xFU=2!UwhDM92|_t)Az`#C&8a;vYWmj+xtj-sGfvPb0Wt7=kZ%W&V^=3A=ji zPEg*>g2z>cUFn)NHKAyXEEL%Og1Aao=zO8hkC|<*%yGLVe;>qDAc$-9Ysn(FOE#3N zEjI1h>9MbFihRQ-g)yaA!dyo|HQL{mu@Q89`FPzBD3<9I*AX-T-}tt({X7-*4*$!TWTGIT-zK;b@&jYPMyqi~5VmQ2~+nKN}IA$$N8EY0r9Q2e-=9CF%_Do(ZTNMWDbg_3t-!39ke(tSvdr70uyQ2e055fwE#d;o5k$!=HtlXqsHOc#lxer=VLpHpuh=_ zEyPxe5T{6K+?MWUA`@u}oLlxaM29g9p4G{?$pTFNH8v6u=rTZhKf1)Hk4Y6~X*SOd zl<)qfsDUHh`C&m!bKob=66rKVI#?{nE;TW{ymh;7+ zM0W1HXLDiSL)C{+lC0+wIxPVl!$2SY1-Flk;nE|v*nzCgk&m*VN8fG)u7{M_NpR5n zh%X;Wlnt)Hv+ERkkAS;dksLB3m-m$fO`TBGS{38+TDxk}Af!CK5gneQI9C{v6i`>~ zfi7M;B`7RfVf~jrl=jrPoEj?$=^+Pr^NoR8HXA|ty~ra0z`BrnLGs=rTx2;RNJW_R=dpQtY}nj z_*!vBQmFNX&|#+|q!E0+ zGJDc+7VlGSdp<1~h3WRig>dcYolG>IFit2VgZx&I*M8=p1RdlM!%Lx8ApKO3u@Cms z@77hiDnd!lq}A234xGb0nd$oKhmz(8D~`<62nt1=&u5qz9V+{9l5$dg)ReK}(kNSd zw|%U@irzxJO`n7cMcvmy{V=9i!|-VqdJuydpY~(>*)9xfQ!&hQW3`)w=i0*%Rc5oX zY@>C1XGJt#NL$O6xFXdQF`>sAm;DLrBJfpy4|_Ljx8$6{2*_p;YJ-wda}a<|1Z?JD z>YV8CMv6gOt?7qC38VgsY^+ofl{fVuD#v0o2DW z`Aan#^`)IFHe3b@CBuoSZ?DzMTr!WR{uP~sQHnWmia~pt1ilSCl~o2!;5uFqW3Bi) z`pTga+){oScW(EZ6h`f6d)B(|qktzCYeA&>V@zbxA+izcF5@iWP!I2n%xXg$hcZSO z8Nwtbx3tM}jK<~ry6?K|Ib3+SJXk@}DP}oAZC59}x*j$IuMNvc9RA{E9ZR~x>-ooE z782{+J{2!U9uDo+w;Cjj=|{v-`6J$2nxTxEZhk5}p;@HbZ{kQpvRd|C$;%P(WCQx( zI&-Vfp>Q_t0VkT>v2E#uX=8de7S_=2m696r>d@GKeC2buh4+$nCM>;>pm2Oeuv$3p zh*swl!|>E-Pn^hpNU`gEo1*J>LW51#%B56eDqBTO*ZYsNu}3veQ<-I@01r^Gc-C@; zVx!_Rtysf|R%oE(;Mh9A(0yDyGRityE<555R9?_Y6#{pm5a(I5@^~bx82L0v=M1gB z#Z(s00p$sBwpn3L8rEgq`E^tZH*oD6QC7Y*Xga^w?vFQ+`QU;T&j&*hMP~=y3L}i9 z$}&WbIFMg~#rwQ6tEh89#=*279O}uLv~h5LO4(5hzJznt{=MMUY>T!;tHt<1LXPKc z;8mA-2d6r}X{|4~+Jq-YXLYC(%~v!>4z&_bTp12ecoN?Y(mi``=NfXpIP1fE{{x5lhz020iT;>GtpI5jO*{d$}g zIJ9deO`JA37JhFeXcn(wB&A>?rDke|Cz9~;q#g~Iv8yFyP&J(w*6q4GH+Ka4al7{qJ^yg!3+$3Q z^tMkYR3!(tQB<^f^0pPcjxGX$=RN5WMq9O0*o7~67-|EfM{UjW-CRA4{;BGu@o~%3 z%~QA(PL()Qw;Buna5l9$()Nb~mzZWD$fnK_^s%?^0DjF^LRtod+LuP@O6~|e>0JXT zm1gE1Aq7-)@54#v3^HJ z9`2F5j`G5Ox_%$sjvYYG(pJcSXqeh+*E)rk6ua|W@mlBMwCV|Da*HClp|DSP0cw2< zBOqpWy?-J|8R58GJ@?IKbFz6Y1tlH83A3ZkXF=iE7zj1~}x4%SWAyslZQ#L@7G23NwNbX^9U zqMXTqZu}Ba?h@Ue1G^}>8NhjVzNt4^yleU=2^V|V!j-R~=^PNmO%!9sIR$x7=}A-3 zoTZ&#jl4J7*@(pw?bV~NsQXY>#N}m2uwV%*RjL#z7mZ|UAt-bMMT6CakSv}=XBZI| zG;|SfV9{@&U|-{X-a>u<*eaxsi+1pA|89JQv`)hnvH8NVyj=hM*H89GQUjQc`9)Za(l zd|3U3A-TQo1^2t!gM9G4UY@l2?`Nh*7D~ETd~eTo;K>Gh9J=`Y3^iU!o?Z2t3|rre zUKt~<@;+E+muwvFj4sBy*vCSZ^(&e9k@xcQ$xGPW?j=DE0knkL5epQQ2Qdb6O7L9~ z1S)nWgX&hkbayLYgNz9wKD6^=>xgItg@)_|V_tqTZ^WYBVPNI|^ z3Cs6h+^p4=#Si!VeYj{?!p$U3;cb8!QJzASkp-~dXt*yHjJE20yg}YrC}*0i3C5(U zvlX6DmcM5GqYt%~9C>#-y4FKCjn}m)v{EQN?*6{tgtotaRc@T+HP$T1UF4U3lvx5R zj26%>VoL;rU`K+hWocKXg@C#X+9(m-bn3z>OugP{c)CnnDf^}Wd}WrOzdQ#o9U^&k zJ^gj*x<3O>zSBJ;A)t6)$Ar9Ftv0#cZUy(arbJbgOCaIT{GGjtbdbL%W7~9DeVG@K zFS(0hrW`cWbI+$;OHw%8sQ=?xw;0-fb8Z-cy}GB`#1!>ewVb?z)} zy#d&;LdXxV*_3kO0L-RS61gxHzl$wcl)% zy73K(N?9=y3BwR+2QDs)5Yqk0D3+!3*CQ-Uini&#)3WiZAS}nH6RJBQj1e#d_P}J; zU|dO?l8RrO#&D>tz{ceB?mDgc6ZY^N;N+j&Ut7mPfEjaEUaX6?KhD(MM=WYluW`KZ zF3`(qYk}+AWP8O^)hB2b2w)7C2=gPCGQZ$l!*MJCOWw#-=B@Bo^$|6v z!M9<~;6)m#uYu_Z@dRDh1_5|RXro??j;Exs_~^Q4BOnPYI&u?xIKcNdieB~)vU%$% ziV^%fS+FTf(epdl7@@dYbH%O_@ICJHVVR9BS@_?6^(r`l=L>2E8u{j9Zo;>#?_s#hS`AHHR|=T0`(ZvGh=lrU?lFR6LC64?OM z`YQ}Vz>yT}Y+ytPWGl@Zt`os*ahZ_T?>AczLrr1M8}DSw@i=@KZ4d&JM^>Bv@BUk3l~Z z^RXjf=CT5l0xYCWhoKk6lHvx3-Kw_KBc0_DdQHGGR15d!EoT26d6~oMT@pC7$HP6z z%xm-P)KHxo0-sLvN+5^2YF^t+G!3OfYkBK^9v|%a8RTC<33h$=?8@yUs@6ZeC9hQW zo3}=wj>qK(MhBvag`fiQ#zc*_Tgc7E>3H_P(V5_r5rU)YfI-hvsGcWSEmrS7LGwo#mb7X@t9t>G4D*bRsuGsx*;n){qsff@ zT&oLdi4@asMY{g#yLeGxRMQQ#qhT6*BVXtH=4?zhSLQ#=_WBS8d&eR2c|*(z451tH zR@ZV|(v{K|L$v5qXbILLYB9YYqY>~oSEWm=23X@B4uOQDQji7J(4d+1YqcgUq&k%w%sx`U15l&_A9_)D$p9r9Ir< zF~%q$Y)a-Z@d&KhQ~`xKGoyS#;%8czC<$#kv3XWdOV35ul^L`{uce_9?UdX#M6XY983ri1n@5g}t z10271-+uWDamx`R_R)R61&2l7I-D z`P+58>^_wfW1O4jgj~Qi)J1!xw5GX;mx1o`>QKI(*`Cl*Kw%@8CB42}Otu8^h)rCq zXTnYBbnh_basXJAxx^}23@2XH@tM~sMw_RX9GHg(65SRQo79ejoJtl{PL2Dnp^}Xl z!USJ$A5oQ{C}?j7nyh2_pW9J;D2S_5Qz^O`1{TI|E|ij-1tWdvq}hSTwC6!A&!&8B zsXaH=8zApSGRjTu@$M^~ee>Hj?-6J6#<>=u)aKEJ;3;rknS?L;rgXvgtOc;}Dm{Cj%p?eAxEL%~PD8O=p>Gq+ z5#L6u8sh%FW~oXuD^v1OeO=@LhlwGwP##BwXF_?l@uDP$AXclL+dUSpDYa;;fB&BW z4?D7zZDku2`iMtpbR23%IZ@pMKX|z-0qehA66N&R;BCKi6V4$E*=HbB;=5FgC~(7; zH`a(eZM!lhR3B}=lAR-5jf8g^2o3cqJziK2wgE71w+Y0ksG`izBK1X&Wcw3tc1CXr zS?xw7P4&KQRIgtNM2`6fBR%RriaV3#OaRU2B~a9Cj-3ztcvWjkVSgk^?KpX&%smKn zMM%@e2ltb2#(K9{ft3yshJ=FWsse;RmHm1OpjL8ILaDgPy2EI*om3yP&dMK!Ee0ch zn}H=FblzKg{jR4yHKf{kMXz|NCcXHfUh~BBep5c|c|lx_JG|q}HC>X`pZLC)GcdV@ zS76$ng@Wm}HkDDPNK|M8A)s{EK_y%I;Mg6zf7z>`Q#VA?6A^YN)GO1UpO9dtOgN^e z?!(7C`s9Pwu~hd zT=ruL+rIbK+*dJTTvxyk>`YqSkobJfUHux!=6qcqtiqcur%>Fd%#k9h25b)n%VE2? zv{93Y7M3AIEX=BqkQm+L72A|a^1UXc+lqlJbkf&27;1_aIf;Bm*>G)UCP?ojxGgH{ zPU&a|jGjr~*52Iov))`Q6({K(lISmARS;?X#nC=y7OfglAH#Whjnv#y~17kTw}CZ`7!j;y4Uo*L&gHS9Rz*}I1z}Ad5Oa3K!J*dJ>GZ4 zV3;!dY;*V3*w1p((0Jt-lBdXXQ`P2g z){gWKaO=)$jVx_U)`hFgLc-YG?MCU;WveTYo}P@0>d0_0xIFYoUs9L#yJyNUGYy9s z%>Q=87n^JZiwci(?-`dctHu@ZcWgwV-4B$9Kl!mD(v6$cjs zY#00%E&oSwmm00pp6R={g<^??`UK)}uJZSC)IfKfuoo)vuNIV&3$e#q^9!IN2@Mw-l3V2V# z4mvIE?ckr7U@b-aZm_%|000S$NklH_q+oO_ z_DmTCv=)4KWdw2GbDJ7`Pqr4f<-IntY#FWX-^?Hw)obeoeswPo$GW3u%tA@-Djs~^ z(c!2)$MdS$K&c}pqdvf~cx-GW998)+#AQW={O*!@K3Z?ijXhbf+k*)78Uf+Q+#5>DZlmNjFF0WH^VhIebg! zICtm3;4#BA;YNVM zN!ZJRixpe8aI5<&jS3YN!0&$#RMPR9gg4#*-hEfQZuz-?Kd^jxnAS6*p+wtF}5Ij261T=na0kX|L> zrI&cn*-_Jo|Na+v{dFyeLiUS4{DIhNqkqWzYihK(wbVghewp(Ohd_l?quYuV+Ow9Q zLdPm?x}w=58B#v^B(RB7FTPMrX8r1`a?S?u=%bvg*x`Gky|1Xq+IXWASNcxGQB$Tn zceruWTtEmdVe(|)Dt59fuLO=9b^89+TfoYrb4gk(;NU^v+G~N2KGN$pep z1V9?;x#u(jJ^QRLh4y`z{y(p{qIG~tr3Hx65Wo7B7Jund;N+9p=h^AEZPUu(Yq+2M z1d#WlbH`n&3{4zSK0}Z`_@LIPQZFf!H05c_|0#qbGe(R6u?M+(#S2t&wd8Xm;uaX8~DI-{q=y9;oEP4*|UMGuciwE z2e5D<@aI1Rd-t}?rTyQX0)x1(89LO6haQqG?OKL{RB06HHBnJogUid)TR1bx%F+-m z#Fg;d-)d+UVhtUt5#-^Afm?3Tp8G!2(tsCU;7p&*cc<}NfOXPIT7&23Yxm!I2My)B z?><283t)f!YYnhQV`KWxTuE=c=U!mQ5K3Iu)yhsL98MZ)*Dm0qi-3Uxf#_CLkh|^z z#*NbkB0?kKN&<)t8-QDH)j&IC3OQAaGD$-pcUFv@;0wQ5?AAbx;PrB?f4MaEIsHGEqL5MEI zlXnVGeB9&Wi#1|PuN5&PY*~7T1d*x2+Hbl^i~s%iS|d)K%3eN7i_@7;vzY`Ypo9wu z3l>fx-vSI_`NDmqLB@{Na+A9Gbf2I8lukz01G8oU(m56^0Ob9`O{PuL=p>y(0Q2dm z8dxM35q;8$ME4PK^!3-;J$WW{xaJx_KqTBj04|+Hf|NzLWp=h!M$tRYIY-`Sp`#NO zrBffo5Lta22bSq*Wn>EqU{)-G)xUHhY(L~2?e7szU ziXsFV>JM#&&U7;WO8JZUFgrIw)e1dXSr9A3K2Go-M)(#Fy2sD+0veGRl} z@VXrAT0AQ*|X-&d6Ikl%*$&=|u2&B2ZBN16nNEIuX0) zqa+Uk^2*wOuh&a^kPe5@jd_q!wGl`&9Z!Jgst-*L-Ka0Pydk17a~!>;Wy86R{EzDZ zrctxhGxx!735JW{+_41S>JsQ869|Tr;oQuw>$WrAscZ@l-1`?X^A06c!~24ELHh!O z_=f5b4|E3RiN>}=zRbvCpO2GK%jZ~_{zsy{ZO3N%LHx-EM@d%MTU zTioy9X0N9a3U8<=-r6H1qM+&MZ`V=pt@VzhUR;?+uMxTPFYXEnqwVfVFnFrj zsMOqyIUL|pYzQb!BTiy3=b2F^Zmr`VSFE5H+eW9oO;RY)p~Oxi#YYW+(D?>wGt>SD zL8n05oPn?MQs%pPD3>u~40VLd)XP283)}_Up^Hw2dAz2zd1=5Z@!IO{rtHZ8|3r6i z=Wb-QwlNs=8un+{X$rIp2Fa!V&<^Sg+c>zTB2`bZAY&EwY}Xc!C&lnX8dem+N7-K)T0n|Ar5cDv(ncW{SLB9+Br<`jeOy@;8Y=K0EX^62D4E|=q1CKKnM z{|AFf=H21F?~JKKDij!m240VD8qMEpOh!WpG45p3GditoO zM;#8w&ukHqT-a$KNy}(`>bKO>%moss!+G`WQHlSM${i!j9jo5I%A@m4(0OUi(no?< zhY~N(B_T)PvQ^vRvkiHfCX?+l?s&^23o*1EGmM`I);YoI_3HK+4EDEA9g)t-r2f!P rfqn|~Q=p#${S@e@KtBaKPl5jrolBSUF-1)#00000NkvXXu0mjfd&TMj literal 0 HcmV?d00001 diff --git a/static/img/dnat_scenario_table.png b/static/img/dnat_scenario_table.png new file mode 100644 index 0000000000000000000000000000000000000000..59cd4ca4cd48851c2b7bcd0e7fd59aab5617eaaa GIT binary patch literal 35571 zcmYIw19awa^KP*_e0l#@Lgs=0|2^hG{I4~*Ngm|?>R`qHaYKit5&sf!PSQHAU|okUK$eU0;eh4zE|Dk3Kbz_gy7{NQLrIV+TTw@e!~`!X@kuf6-g(N zX;j=JqxoFrg#8h|1vGMTdDBV{5|bbm zk-2$x4}}w*`zSXVE>i7Qu{`^V?YRGNj>&pp9Ucb#k42DE8gtvP_MU?%C*|)R|KCm3 zm1OfMwbD)%`;2~O44fJ!o50D1BnnayHE#dcUDp3N|2ZU(R!8l@lyr23Q1KeDND=06 zu|y|EF54Q|U-LR+nzoEX(Yj(%7@exyuyi`t+;0hb8OZ4feGw5g9kDlhByInW5GJr? zpi*van>?L%8#n3lvnD-8;rKl6(YLU}RONBX6$!?31g;)nh?r~=$ z5D|a>O{uF~nFiBh(H3DWQ{i)%s~Lb`74+gk^BX_kBmpwFX2bqkHZ?~w)OduvmX4a2?YZd21dhaCIyvJcwepWtb6Mf8o zQ=!mG9{5Y%rfau?$SJMpjXFRXx}Ehk-|!bARqw^AKN+9Gi@G7zNE3!3F%#GF3PQlQ zpyVpKOZfmQf9MjKk*BtZ{i}wSPvGHRa+QfeRDteT({l{K0Pm<_ojepp^~JX@_FXhD zD?4wt(;j^BM^2nB^X~L{M=j@gUr(OL=rHGG>h#Ec#?DJB*V9s9^7hUM5~%Sx<54|u zp>b_qC**bK*y(MXFH6i-BP2m`qTdC zL`&l2(fB_ETIXDPF)tFGd($-tuQ6xYmf`?}_XSj97mKFb8Nd*r&BWx_b|J}m23=Au z?YZ+alPzql*M^x@$P`V}(<%qsJTg!pLkmKz-h0P_vm|TIb{%;$2;h@8)ILG_Y&XFJ zxvUlHus=b>Q*XNAtxl5-->8`*%3xcY7AjgkR1$%WZ+SePl-_m!Y;dD-tl~7vz#hoT z))7#T3FuN?Wp}&br=4wk(tVrsVgGPq81B+QYt#aW;@hfiN!hdIm~DJaJX_qbxY;Lf zxP_q%0|zeuYF$(yw_zkHMu^dS-J$dgQpA z?uz73{snJx03i}c`_uXvS}z3(;AxD7-7X%t)EPyxUr(&-w7>HUUg;vH$fb-cr7plzcF=neNTK+9N4i}f?1)BD-fl?I@Vv&~-?}#bb z)HwM{b&6(_OnlcjhiQ{ZL-%=W4vX8;fzk3;Qc0_#@Ha&J6FT~=)sbetTSyiDHgV|xjj49-}q1rL^ee5Rcef7U9YaTu$|wB74Eh`JMYfB z&`_+NmVwCATq@jBF3)oiI+Fn`dozW@@MvD}`hhxbh+N!3QALCg?>EF|XO_}O_WFkN z4RN_Gk8ntUuC({@p`f7zwiOoJb?}3EWux`=_{Kw#}Vr{&A%wCaiWGI``FD zU*}ZgXNqc!gdpAV1!^G}?bI>P&e_<|k}7zRg&O5uj67WimV%M zpoKxH#Y?gJaf1srkotedzlhYMdbsTN!sQg$h0!rlxPO}4dd~{l*m9-_@^}G zg<1!n<(voTd*IEzR3+c|NAeV49xSkx%6s;*{6aFdTK)6=)4;a3{g$AfHuk+@#ir)B%8NSr znc5VCQ9MT@?(|icBGO1`9=0T|YNwa7aFGo>;#S+6_N_}Oc~Kv4a$~)%A1ID|eU_2Y z5D?5>znDPwk`t^N+i@me0pQKNO}kP7Rn~}f)x4Aot~iD{JMDUIcWsD}7-IUxpp5}3 z&}RHsg$@}LQw!IA+BDqq7?ze)eULCO%Xh6Se3-XW9qQiRBz`gx1g|Wu=*PBKeUR}l zJKAWX-706!jcW;42~wb98FP>A2kD~(B!l0mzqNSNd#h|nb5gjHCS#7(P-9YzMa=7s zCn9X@mVi6oXaOnPAIZyLp!FIqhBzB*p>8slJQ9I=lBuiw;SLSN&yDh9InW9Zp*&)A z`4iU+f9%xWg&Rsu7DJy7u~fEzF2x)OMSs(0kV-VNOoOij--~muPW}UK zWd4GKmqUY5Z{IcXtN#}#6*%?54MYxT zT9y2F!yET*03H7%9|grgCsD6ecKLr0P~U%`&}9;&sDTlaC-GB-#KNZ6LpwphBmIg0 z@wwmT|3gYd1ha_)siB-O9j==u3k!sy`iOPT=0uOBdHB>L+Y~fWej^7 z`=lbi0G#4rOD2CHLV%t(u8k`zw=7wzYiCvMuPxDdle?RRAS(T~PcQJ`tWvJyZZ&); zhYQIBdYRsSa{f17#!mq(JN+%?e6gJkjyVBCEpF*vUq8+pVpnH4**DP-F-mTcXF$8ABPp}6jmJpdVHLvs_~kDuHm~dTyQ^NhI6oK5-md@^`fskANV?fX_4CuD^eU#dVmSCPyJS zc!k-1-EpH_U&}$@=PR5X)~8KPIpi>9=X$9l%N{4thfVs1-&w2l zieUv{VRMD!-R8C2J6z8fYCg#)tv@;7NFlks4Z>suG23+I(@j&UunBW zyN8~Yules9TdDK&tcWY{Y>6(N!8+$$q&XSi2iw1v)V&=kR$}zg~?{uX${-xWGr_L5L1>BR^ zunD><6b8k34{+yvFdSPJ_I6BD`G{n&aW~_T&F7i=gezwLs!3k@m>q6@`tooNyLuPz zEq==r&02lWDRZe+tJ}}(mEO}7wWC$7>+q5>Ulzl5k%dk6GSUzE$`bECGYpa9{CI); z#&5%~n9c2AmGuvxGK#6P_#MJ2iE3td2Few^`}!G!WY~|_jYPNEIxH_wSlakgwRSHBgZpbNi8^04g&GOg?`aFCjW$sQQI$XT<|<{FA{1YvY;-|X>$mIl+R1%+;lgh)*2(RB^%N*<~<6R zX5y&X$`dEQOKS+vd0XF&mR|?4Tz$b&6WKUET>d`B3slB1DUS){!53@6(>aBPy`GMF z0sg~&Bt-Bry&&i^b=tEJIL@6Ur4XPccxQl8<~Mq6u&!$eP+?^QpwNz)#b-4Rd$PJUsw%>{ig0`N7vhHmU zgpMcsdi=q0IBdD$vFO99{f+~Ll!Rk5-Q{2Kxk6aH$CIt8)M%EXPkU#W^E@6ec#5PG z5_5QAJg&B7>UbhQ-UY>{v)kwHfGD$|r4`z5x!gYYb>PQeVX}Wl2v=%V2T>cn*nT6W zbLdG$_zjm%DV>CJ16f~k>5@(*{>B4ywL>B2Cl0rBJY42>o{J>purF?;?N~`8qWlcW z+Gc#MQ(-6-P(%S*L2EXdHpZ6IVVV@3WQ38LMbJXC=k79MG>4C=5oIKEsq%UohFDE{ z!;Gal&<5{xp?IY2iW)cIhkt0ef^wDi_aX`u0iJ(l0)c>fFkCkC{Z~k8B?7VHagEUt z2Lf{j)UT(T4BGz|mvjNDa;0jp(xBsDNHM40iFS4(Ep5;dV3aPgx>!pBB0S(MV}G9%;JN7GIll(JF_%2saJA zeBpSw(bqGsE(L|uD`%fMlyAG0*Apr+eZEBJM$^9#n~lV0=M3EZ#e-$Ce^Ct#?GG7T zZ~JNvk0n7W@q<_C+kgX40FaLZw;2sUCe5wy1EVTU8)w-h;Pq@#k6WO z%zbobER^K^oYr9M4nJ*HJmMgZJ%Ck45IZLT7+#NWSWGvA5ybcGTvVT&2>vg~oT0Uh zWxylB#0$6!-kxXCqJ6bIVUeyIOD5OPe{+RDKliL3MEQQ^p;6X7mdd}gc-Ehqo~;CVpbZS>?U0_4&lB%&o#blX{(y_^;uM;x2ZZ2G|; z&LnCZ%svx3MTHIXLype=*okJ=9$@_5%H8I_7heetvDWbk->t0e<6>i_ zY)9NB;julm8qTB@WzbxX1y(TI6OsOo8la)mYB>2jd6bJPvB~+)&&)g;RQ=vnxOpzH zNxm7oQr6_{?VS-|!5aCj^e&5)tRK^11RTp8&0tHbck_M16`lwIW{6|h!KRIESDu{1 znwDbM$xQhDp*Rlsx^)h*{f>@2{_Ok*cyM4c{%U%NW0uPJ z=E}J3-^v9YuV+pj`L_7_?_VhZi@>5yh>O5P*_AjT;New-Xyh@ej{sP^qW^=stn&WMg#FzWG3=Ij77E@KX6U5nN9fFgFJkJl*qX- z*N=Kvdpx$|8b8vcTq;~~|0#N%Pt{n@H6U$!cfvFi2h!_zMOmn`*Rp$$(|0Ly4VE$W z#uDtZvt-6WsNF=$x~VX*X2#?H($e*mcR4y-`*7^6X9_c!`R&ox{3NxD}dKOw7)tV6D>4P>C>33vwkA1!_e=-h}8MbU_8t)wz!$)~U12*r^zVeJh) z65crXiVR~?kr>t6lJmO%oD#9&zO$7rK12IRZ^d8>0N9@09>jmLxnis}90|t}@Q~YP zyAd<`2d=tbHbe8wufDk)lpO#jCl+_dF%<<@xe{v>>t%2E#N$d!F*~_wXa+Z*Zf_4q z@x}L!s@R<)8b*;_{w}VJL|EHSTu2D6AxxBbt*~sv_7m`Mg5gy3fm;bFIKyW+=zPl`L&>N# zhk@c8eO?~q^M5LKy?uEwZh_MvpI@r%zb;B8Z4H4|NDyAw*%`UkOOl;8=jX3tn_J8s zH?r}6*M{8zji->5JaHVI_N>d>pGdn9`){5IY!@!eGk}sv|9+oFX09ngs5n$ON@st3 zN{@*JZ3OIltN>q~{W=nu@b%&IK_>_YZN67&1AqP7c|}8GEL2u`w!|=jQs@_K6itXV zFpkEZsti3ya5zgS1Tt8Ej$y?I2!(`*7j~9v7pWeC) z+K*J>x-7@)=8d}XtY1oAGJAWMxM~dw-_WTYSbn?1)>it-4Hw=m*2lrU8}J=xK5RW3 zR+;Ga>`tUP&h&-VNc-KQE02e{6y^Qi-A9{Gr>Ju;GJf&@9xO6GLG{{+$4fQjKBag7 z+t*PNd=@FIVLiV{(#9Na3v0FIJr$ZWWv%`g`W*maoS-Q*83_YM2kZu`%QKW)p??s>W_;gM;kr_R_keISu;0MpVa8bq0QT2&}5lH)YaILY4q?1 zw`-FB{v_hH54j}2$#n7ZjT&1`?*&pjdT#X)kCa0H@N`6`f>T8FBT|jNN_7kRzN6LV zO-BsAs+#QZ6oZr*_r&4F`-nfnsRcmi+17eV$56Wj29yL?OmvVNe&g8{*LRP~2sC|< zgBpm`m_7JY%g!owHs8R?>&K73P3wAl+bbG;UmKA*AMUYn>7)u zP)0M$A^cn6Enkw;{m9CnWxCUTS^T9ZBlr=u!k)&;WMcp$<0h<&g=EN4+BL2OQXU-O zDUeBu8kX8LtE6a6z+c<7#!1=-b=GbSX;+a;-jvBeP8@67by=4+wbKRiu&VFKvO$Iz z46{H3!xeG_vMjuDG$Q*y`Ikdz))QNa$xA91mFbIv-5@)HiEjte$6beqeUJx1ulWlr z-K7jdAh4Jtn8)eqkevUUcM67?1}B`xJI1>_$t4fU0|V|2zPV-Ud9N?WYdy{^B;r)K2JY3Ji{@+6o&`%O!yXyE>IV zMA2Y8d(t7Qz@zlA$i4|f&-!~a`ME%xx@WE|`&@c|FkMw-Ft&RNgqfL?n6=oY_uD8n z;kUbxf86Ey1M1fzRk6J`rc${&(r6-+l2g4(yA+Cetrp=21SV{FUo;2g;AR{irBxfq zg+e3kbMC!Z<~N&ZKKdK@K5coblqwRsz5-i!ju}ZE&|UHtN|ns=I9K>)6Ue2mkJ5}X z=^}7-D=eonWBS~NNq<2U$FSo|x;dj4md4<5{J0I^^EDHweH;Fx34=`VyNfH>S27xt zZutFiCd)3cdILu33Z|3I`HsjT!DF6$5M1k#iw-(0V~K-Z2eEiE8C2CZ|#<&>xnMDa})jy7P^F8rRos;{K2#MPLE3OwjVm;Z}bPf9S8_8 zsF&|Hj*^v{nq86puT|O@wOyuLh1OXHJ~sw~tlqcg(8uf6MB6R)__j+Gn6wccG}-?a z%aht`Eee$c9xy_&-faRlK9P=dF9m!b(*gbzuy!>J5<7bCb; zcC3cJK#t3KeJpRFVQ<^cd8iC%lRex+x8C%ZP8gH0-C|k7+8&v)-IPG;FL=z5z6Vzc zMpC%L3(5IL2%vtu3(Nkx&?fL`j3Ipr7y5=tGS+9lXlIOB`JC|J_U26F@@BKcy|Ue? z<)@BA8vg)rZYUpmt;?J3DYcZVN6**3F4t&CJ7BBRlWVt2c&}6%{2~(m#r1NN$ANMx z_A7~0;IP$UxhtKo@NT{v%Kz3xxd1iPNxk1 zSew1y=-o?tL+*UM+yllFuUsl3sLQ3bn2JbS(deMXC|gR%CJ_l&F&E9I%B5->b6X-R zmmubi+H%%MXTn;qLr+~s8g}>9<@H_lLhc0ELBXhcb1MI62_yWWX2JhTkE08g-hVW~ z;{sMJ%fgL*x7oe%WAFW`nioFiWTtgrS^BN1DVHys#f_$wzZM$fZlGi$jfqWq&Nt@y zG1hM<8Z|$c5 zTBg%Ni308vZL!W(29uE>WQ%Ef5UbU6b~wx9D79phqoai8f@koP=Z?P>SgUb=$OQ%4 zYQK*JMBTjfL~MJiI#{)xR(pmZ-vNYe=bg@@18`OKuf^W6_mNdnkil_e84TA29nEhV zp~5_MWsGE4v}^c0d{y_kX~u3bZ8T62kazGQLp>?jIVDGX#j^LE-h~=L%E!S|;j9;N zvm-~~jotF`DxIb_?N{lq)vb7ZHiag(A#}|mcJRDD=7DFnqltg2qjKQ1?y%@qqH}XU zm8X*779Xp28tO3N)pp0P5hdjq^j9HNUMNXYcN=F=L4puF#fZQ2+c+G%A5!b}N8*VcZ|71^qN@S_mccBI~kPS=SPQO0hNz^~)5n3p?W`mG%{C(-mU3oQzS z!Y;N*X2>A&so{$Fh!=eM-CtG820Q!O=5=FQb>CqL*?^~yM9-jIG^|4SZJo?!>BT;< zbz;#`N?DEfJ+cT?ksCPssHRi9aJf(t^_&N!%}G?-x6wmGtDUb^Mx87p}+symv)$r1+WY_pSIS zXdJnfAJQZ=D)Ee< zZ=ELCKvlrMk;mh^lhLHdEBufv>fcLJ>Z@zeT$MM$zFD|8@WD{vH-##}mJwuRdC9Gk z*J*h9IbRg%p7bf#pTIAZpCC%1lcY)kHMSk_a{>USR`e!5Zz{2VR^wN+IX0EowwS1Z z1V(nm1i~JB!OWp9#2}V9y|?K^pPG7oW(tu|;ej1gSFs7elOTdVTdvMB@vvDp_%!?d zS-LjPio}kFgu~pIjs#%|3RozT3Dq+4Psy=NlOf-U?Q4VZcXhmkdc zsa!HjEn)Hg%SLUdp3s;7TOHJ1>TKsY%w}UulyL zYA5?wH_n*shMg$Pe!DkpPzCJQFv?>|5!Y?I$ zeWE5>;NRNm!)XE;B>ZD`m_4y3b?9&D2H{C7ZofvX5XV#q?#6vB!+n9ozUIYiq~}h^ zV7`HI7DTSp==2MSD|wLeOQXB?T$uaA4cE-tC)}q!b6qXvVkt!1gw@1l#QSTt8uRJ{ zBCR&x+E5RIt?jaBPJsv~9@n>6vBFc?tQ3H@EMODRu)M|q=e6qxOXBpl3po);hpO>r zazxjsW!@a{PG47I5f1@H50;7@R}f4b0A?}uLru3?pIB8gg}B-aa+KX^Es%an+qwDB z7fU7_pDn0<6WN9B3-3Kp+YBT!wSOM|7!~;(*+E37&VIiBixT@2Uj9h;&k%jxN4m+e z;ted?SoQ72POs1wZ7{T(+?G(-cE0AQG|^Fq#E(r!1wsac`^+3Er;qf-=UAj` zxG;Xc=vp`_emNuP>WkSFmkEsBdjM?i24y{F#T5ECfxmeyy zG{!IQQ{63;6P7Y<_Pqq+WNFg?g{2^t&1NpR2x%dQT_RWEE>3qyYbZK(3@ z6hQuM_aW!5k4wrqcmC#k3)<>d+x%bx2A@r|)OWX!;Igz`3OS~VUJ9>A6nZh3g`?ml z(o^`F4OjOI8rxg@DE7OnqQSi&uwz9G$yxas?J?q*Es5)g!KR}T=RFr#*&~I1bWZ*o z^RcG%LF3DA-Q&NbHm~yhOQ3Tcw4{)o5=D=g+#cdydj6<+L{y{P`rlApTX-iTp(r15 zP<@^i(Fgv)mF!U9`T9Q~v}~Fn`j82E)2}jd5|&7+)v==A&du2IF+^^kWI{3F=#TKw z(#Jm;?X@l`!CS^rNha1491V0MZ;6!bM3=*F|CCg{SQ{rT6~4f(a{c_iI$Ux-@?^YH zIz#Szw|(rS$ntk8%a#zP?tm@gU_94dTCbcov>SV5sry_Wnpfa}S%mlXj=10ArL?WZ z5i)M-ji7v-Ka_1EAVjV*-V8hWpVmuV*e9N`fs$K|Kn&ENi&R;n|I0l~#rt3Fy^&(Y z%S%Qt|3l80Ged%Rs<%)w{$O%<*4&KN6Ea3aB#C48ZA2@aaHBK=v1_Dr)LHNxc$3Mh z&@z2?BzFPq><*lmFLuvBG%4Xoj{#bD?}m+{3vxFK)%XyJ6UG=NNggKZI#uDj4Ymo> ztFyimtyXYOM0dxaVy%+R-$z$gA)wV!;vYU)^*EK02kQAVtl}ijo=mk1h1Ha=;tBDv;`Wl-}7*thNDz02<7 zWxpm9WdsBZ1+PCRoZ5NZ?KMEa$Wi%}N8X%kS-u!8gq>!A<;=z7syId|HgemSTNty_ zEu9i$%_n|`%aq>1W@-_am-}nEPUIgkF1yhn6GCe*)07C~EEDQV(R~74-R?}n18Rnz zqsr)kAdpH_ny*Rn%Z@uOu3w`ts`D%593y71S6tr!((q40<>Zc;2y3GAug$-bsNpeP z@cJQr5wE1Kt~?7RPn)=XhBN(m`_Q=pzIZ&%a-}2lQ&vb|Mi!G6IfMB$4xK0l#e8H* zJeo4poI7-pD7Vo{ne1cF;~gGA+a^^VGi6Y zE5Pl2c|74OF*s1An}9`+Am6xc%Vg7{(I%`B(8I{DS86qr%l~=3pskUHFMfI$y7H~+ z82PR1bTdYT*B-QgEOdH~)PJ;9=_M*jZSH-Eq`%6&lAY&wH_k&rrwwPdBLDXR9h_g{ z0AsrP1!?3YMsz(2$=T-IG|Z3(AAGbQmbaaF%^UCT0o^yDlpJ!5`cyIt>_r*!-vnY_ zEn5&PYTpM&kXQr+cOaTDE^=Ncbr8Ytm)E-)Fl2}2Du&KawGOk9DyzSLAy+lQ zvzh8IjXE&;`k8_RpZ>S9>J8@Kq|%$R(`*MmJY&0Ja=8iiVhu@y0G=+u7j#)tb{~zE zutQpE+N8ZH)XXpcOp&NJ>EX&#f+e|Ho_ z!6Oz@zEWFes1o;d$B=0{bQun^s{jt2L3X=D=O|6V>Y*V{?MEBy`a{@ry?-a2k{wU$Exh97USK|^!U5Wg5 zjlKMjrm$FtfI9=Z-DIWZs_#&Bh|QH?TCU)nV=nVyS<43#)zn-m$+-5}b(q9JgxO<6 zTA@t06*LW6gv?QNxS(I(RiT@ng;xv4T=zo8=Lfz$P@D8AGop`uRY=D4?!ITXX%QBU z+T1$fr2VljxH6Ox+|$my?zT)#pRu`>!l$Gty2X#WS-&T-gx@WKvoRf}QuwxpL_M2y zT#kvv<9f`VM{~RZR%K(T96#UEKSFH znYMYw62t17bBE=m=`8V+I;jLmOp><4$1SeJ=PN@9( zUIsVjJ4&@3Kl+NrvSO1vH_cWJjEydX#F^3z2RIEA8U5^AWSe&?KTlssrRDublul`- z{sHTxS@Y1(iX_xHs4%f$n&`1VCRSSfbKRM~S}VNrtjq@?yVyXjm*uv4%X(d1 zBM3#BT+rhpT?e$EUJIrpH%H<7cuX_$`r=Ug+PoFca%Cqd<^boveW`3V!XHNXf?gg6 zCldb+maZnWNwRukY1!P~3019mTho}zUTuY))h04=U*=z~BrOPy!?rxX=*G4^N%4kI zD1cvT$7h%@?}R;z$vD-9{PWK;^qCslYv#WM=qfh||)n+m#x7%a`UV zS*jSx$pC$6+N5GgEu^xfe}so8$=($9+TP<*TNkl6i{b97SN2VHVb-U7hY3_EpMJS!-?%=!S~Fq5^6} zrRzf{I!|$oB2h}nF~Whj9vaR3Ypv3pLbon2Y%(1y&=1bk`y($KoOCYIM#___C#qTJ zBpQ{=EPl#FZm^{ig=i2Q4 z1LaVILnTj0YCMU7V|{7tce@?#KkC`g1yPx$@7~Zkb~F_j_rq#RhpttLcdueI;7I9n zFc&b^(h@G`A7@UKtbmczXkUHw{&;jqqEt`di>QTL@z^m1HO&49_zQXV{Xf?rytLQh zpoxI1n6(V^j+Me0juZU};tRcGQs3`5D`FCAAVXP8(?e9@ zsTMO#o*7J^MlqhDfjr!UIPj_B>q0*=^!g-v38&-2zM$4hvc*(*!)NB-jJDfu6ijxH z{?wzem!*c?f$41qKiuKeeq*(QY&c=Wx0Z|& zhmF{j!-_v-d%PUlXjZsxo}kH^`zx&7HB7YtYx+w}OgXC?P-a8xzj^aSY^G8(6|ouY zRO#}g*5Q3!Wl zpyQq5I??9S!PAXPX$${DF#am}zsa?QXTN9EM)$cMkBes&KdwuBL)Ve|LaEsz6$5Bg zUbCI!xHfVej$5{vH`8?Q>5&oaojBZBTaAeVyR^832WQlcQLBTOg5OpE4_Y)JEE$x! zqXu1N;Xf%~bt$~}`BHkSE+ag{-1^MSq;H9Lf$^xW_+!0{KOg$R50&vZ^PGTkt0BgwM1Tp zQrMR-w-(8D)z;UWYWxcmQR&6^Xd%-~t?|DZ`aA*}=>!Q`NnFlbZ$TH0O4kosM(H_< zK9&z>DP9$d8te`@OX01KY3ZH=2?b6Z&nG59p}$jMPcDbMnBp4-v?_wQrNQ?QdbyCs zZd0NU7!A<6eBRGed<{v@2B?XL7g9NT%@=NaQ!@okr05!JN17FkfRBHlc1+Jxr?|g( zjfNMq@HxCKdvWu<*9(Kh*M4^=1rqM}cTYnRS5NHk;-Cr?4s#XDA- zN(CXDal!eUA?!&TCaHKL%iapJ7cKRiO=d4;qsv)7hr0a0-tEDR6@@@GyuG-Wr?z^y z_~?2HEfc~(086|cDRw6OMv9*@0AkMOi#E7pr%6h|{!K_}-s9k8HqQh-{DN;(T8g2a zvLOdtt20i>PbgI{mMaNlES!dGy-|Z+BA+uQEZDhsx;JK(Wjba`=awUEf$|jOu-(Oi zR<%fqOw2p@4%~o6t|>F9WDNj4crFH(q=H8iev42mRdmX_vq~2Pa<#F=ufTS--yI%- zT;1Ec>xp~Kk}HmzqMpM9+n!{oJgm=>sR`Ofi&$UBr7Ejt zPAD2rsSWx%XA;u{?QQ<-bh`C~cpSFjCKpwl{(Q%D!=&1F>-#H4RQoB@Th~Ijs{B~? zYYpG?FI>mi77;{UVR)-}SBUDj6NT ze|@_8`{sRn6OJ!}`+fv_yEt{9MVH3p94hbKb?<`hcm1)Eu={gm?#28q*lkV4uTK?y zR>0~UoaU`x-n?StS7<~QoV!lmi1>7YSLPw(g%rCpY}10b`8<=jh8Bi*AaB%z9xQ+! zlu#l{9+oYHjE&+ku%UusxWzbRUrQW)&}5M#RbFNRZ=biz9rf23-Sa{63ou#9{(QC%fsLiVaZ;lkaRi+=y)wb%K+RwD0g@iV#l*aro< z$0(M_1X});#~&G=GktDrnC-<_9kA8v$kd7l!|X7qVm_USN#66EX|IVq_Lfw*p2TtO zQH!D=RCkxbdBjCPrOn1nHnB0VRocvAH!V7zy(FkrqtD4g8b>H(`6AwUTs>Q0f&Uom zsNC$LGx=f00*&U07*wU25i_wXuAD}qnLAIvs2L$n`oEdvr!E+^B`EIWQSIOKVgX}u&^A3QV6 zlhc*4CGf~YbvM@gm8j7nClr9YgD5zA)n5T>w3%>-kL_oYCdYreuBlYPQtcODb}vy zWv1GZYxW}Qyb!g%IXmsP z5B3hu=~y)W`G2j&BPzvSc<7t&lg0RD!&jx#FeCIo`U5K>CjW<0gWjC{Q30Iy+&g zK6%H!35{iO5eGYQW^&qn*YOxp%qg#aW+Mz8s4|L(MDJn4E3dA{pwom{YdB#)g&KfD zIJW9&-kg3%oG(^zWX}!~_)Hg(eXsYvOD&NXsPjJXNv1czf`Z2iftG~pedaJbhInIf zqF9bP6T=FaK#lHZcKjfY8P*y=tSS+X_#DvjC@D4SUt3Z`b#voVO)ZP{H#0nd zBOt~@>e?&c%G!8xTTm$Bd@(`0Y5&ZsvQd8^OoubQ0;b-hLTg`HcpX@l_}3#*Fxm7fp#l zm3ZAGLNjv+%LND#3t~{prjn6h^p_sjPM=W=-B+HDj8FaHxE{~X*>j03VQ@Tpu z?QVAgTYUAtC&+~)^v|w5W>fUW8TH0&4Tev*l$s7-C86Qxo1J{0sdebEOUi|?07<55 zAtfcIAY3-0HI%6kRreH~a#DpBCPVvt>+3^99a*r%ZL>`xUO*=|h!`%&c-{xR9HQ&z|8`K)UH6MHiFy2U>O=mL zvG+SclY5HM_=oWdh*@^eKNTNO)((feySkD}!|W5p^ClkiUjkMCftHZD-On1t(wMKl`XzuGmEenWs>O=Gl*0XNznw#bmecU2-X?ME z1E&_^)}U)W&rO?5h61*GTv4DA-@=?70POwx=5R8?3ZM&wj7IZ*+6pHt9PLiy`~k1} zg9*v=ACm#3;2jczvZG&&oUr!5NzRhbFD6bwMl+QiY@UwhgLA|k-|{|wmE;Kx1S93kNv8l$JUAyj1*UW z!RVJS`pZQezL4sA)L~I2vLtgUY?ExuMEjlyW0MKdqQh3o#%^wsn^+~oAHArxcqtob z{3&Q=QLZ$Z!L~43%x?NX8(dLS$)rs1htwb1@7hFY(YqpdOwZyshL@DTT%b`5PPl6E z1hcY|Zq*cG=XeuS<4~+n{FFqyPcna-LF#Crcy=&2l;pc}| z+zUhr9$A3tVM*?)G{c3bt*ZCvo7{c;$#@EWw-8=X2&i!`CO7yU=Fwyk8?d)vLaq>@ zOu4nSRTp!_^d1dk+Ynkt3U&G3lYt#g$xG~@TsolL0HVj=g6iJD>SGuOS@m8H#f55J z_YRHBRzOeHm%n;vLMzcx{i)jWha)^Y+U0S^b{;z~Dev_gVOBl(nd$#$?uj-icBBhdC^Y$o<09`{#DM_c|orM ztj9MU;gO{S1T$`Nw8G+K;g7}$_CKcVuoFOQ4x{V43JX%p9+PON!@o7I1q@f)Xx~T$ z?AMYU$~~E*MmP|d?dLt)Gw!L4fLca@*udW}56OJ(QKCGvmwaBCrRDbnOrKfP?cbOR z`E&C0OxEUy(z$J-G72+fv5x?O(-u{G^V)SzJhB)Qb}#c0#61xmh*2Dt7vK0*`gK#1 zsg(qiBJ`st%KBs)1p+_lkJTEty6vb7iIBz3biEFS{S_w8)d;xVG8v;;kMFN2Cq5)W z4H9+sBLQkgul{Ja3&mF`ozvaRBvN=V0hHz+@d}0z21v&9U713kAvS#qU(xd&w-88$RTxLO862BrIM7T&x9ew`a#wdux3?qR`s*!Rqmn=J4GMmL z9i+y+-HM1J72CPo8Um@ZpM<&kVt5po;}`vU`fQ*vCx^Tve6ogp-O{{jGRHk;Mx?8Me9>HQx7M?tv0ezaff z!PQ<`V%>W6jpimm7U{%fnK@DVKvezYN|>>dvmuF0s>9<<;(xhv6&TaDqS4F*%C0nH zgF?gM?-@4=>*)F&{puzf0INOJLz1V-80qe~n>KQB388yt?A<()WNE{~QnRdtow!P} z%0HljV!0z8P(A(=#Y({SXH)$ri{itv8<9Rs-e}kD`-%N|GxP>(mCejmC9yT}#4h_` z%0Fhi_#{t*kV>y%+wX(#XQ}Ufy`o!+^l13yUpyT2UI6PRPuOmAU*#v>!|MMJ-i?`f z@0aj7J3%<%c^a8x#o{?IxU&nEtldM?H*T#fGI1h&Nu9zU9U9jr2;YmKCqjiDmMqy8 z6+3(kk1m5AOpVwT!r3GtIuGcc$=Rm&%({o{K?A}92zwUzA*SDf_x`0I}xYfGWKK6D^3nLIpE}glLHCC z0S~T@lHG3V?;+5;@-0ycBzv{(;H2JE8P_%a$#sA^`yb z`1@~#&Wldlwrz{Nuxr;Y1|X5<00!mRiS_H(N8ZyH?Q+|@cW<<73S@Nf;6Zau-&d?y zVbVD!I>gu&b})}?*RDmTR~oy1`hM!vDFivpgdaP03=0=7WWbblx{Vv2nW@w~0036u zTvF%8Ew*1xW<(YzJwhCC1-l>nA8_#^W28_7)SbA48)wdd{T1Bd75#NKZPMCx>zcaz zs#VeNpF3wgtE&>94G~>}U7Mi-fGby`r>E#e(vBTb!GG+F40^~d|Mo9X?yNi|3TxLg z_Qz)Hp6aE)_|i#kRlj`svPr&r^=js|mi66ct}S1_octg|97r-R85c=T|KiJBSLGro zn2b8gSUIA7`}SeY8f`YQNZ2BIb)>_G51Vbwx_0*LSq8LP?RcAfx`H2m_<`-fhKL6} z5+FQazyOpkUD_~k-n@C{1;79Pd-Jjavzaqz;*(E4iG1CrO`9^_fTbyHW=oG5GloHD z{24>w2nG)xY(U!vWj)lmabvvm&O4FM>&tV`Jr|j0;lhQHK7D%Bty|Zm5hyF)mMvSF zI_YASDpk;@Paku?T)A?1;)y5B_YLgH`o2TGl(cBkBE0wBd**%An4LOx;`U_^bMHa^ zcjC0Q-~K_?At}rLXZdUlspNq{$(Nf zcK-U5;t~@8C3})@TYeRPM4#$dDmQj`{QFb362(=-02G!40i&D#MU-HfT%fYej~f(}+cC(4c|AfQ}tI zM#dyjUXttm`}dnPclz&<0O8)fdow^!DYM~0FJGxrCA|6On;fY(pljEzhOrqHM=ye= zO`B%Y>*tgyQ_N`f9V47%&z{|A!jl<$PoQbj?Afy;HCp@Hf&~lAHFX39A}LUy0Jpzx zG|Yef_18`Q{nhItNP~e!RFO2?bm`KW?`pvR{qKL~yZ#%;-l#w&fBf->8Nq*Muh*`w z2Tcz{9g>O%ffvtW?-%V*Emtzs$d@X~|5R>qpNkmNf~a?oq_C9(2U-s^rWAwbSlVT? zX6j>B*vW`4Xc7rf72;A|P2EvZ?ILi;+|QH=P)JGvqXGjd7!YG$ar-@}d|1B)yf(FK z2Lhk<>#MJTwr#E73ZePRE7tX8%Z#CAe*E~ORWE7ajHkoMc9vG0i~;$CXVSV07POwT z|CiiJ=_*^ctO@p{>k9BA1(r?OX~uKr%)v(=ePpmf&)L+iTQ{RnX~WKLhO8Bi zv}5IM3pN=mAce~A|4J{M$ifjyTCo89S;pzqv!eX@^BcfcegfI28KnGf3~#x^-(tX3B>H2M!o!sR5QOS%Mc|d@;_~6|)6&V)nNj zmS1?`1$L5GFm~+NIMc_xsO`uaEk*jCHf>syPt0_Vb-dkoJyWAb4Tg5~God+aQgYO& zYS8$Sk}B?mBi&>Kpu5Pz@zKZfdl>sfYVY_De4Z&Y!h^f)B8kjSUZ@I#^8C96bL;w5 zZpt94#X*Yxb@f90%+)v^H9kk@4emjoyR2~gbSFRidl8*QF6fJo6 zbueg>r47@%Ht~rgtoo>o`Hj24jhjOnG(`jxCPce!ekj@-l}rQt)vH_X4vMg$MvZ_k zzOXcTU65-)3XY<#N#T+rB%q9o1jgOFcV~pdROYtQFI~DcGO431Ds3YcCQa8-{vFet zrawnY+)EsVq|wUtscXrTCy&h2mRCh*yFs;I7$e2%^Ups=jvP6RZ2$7hFXnsXL;vz6 zP7s#rEsgDAp|8LG+BCu&Z@ghfpOGU+nnuc-H?J9O!~`|kCOVenr~TlA4~)xUAXSCu zpMTzrgc?ybs)@k@<)XB`bWco_R;`Ac$f3STlO`rgmqx@{vu2qFlQ!F-LkGw$A|H@O zJdKhnQ`gm5+P7~HY0s zli$&y*1DTJvoD@3N$GH)7wct5X2vEK#q~@|e-FIhCO=+!HiyxK93H)=ucJqgHt#GK zi`+ZIh7B|C`|Gd2M!IkuGnPBZrU{hLk7;{~7dFk9F~k09OhC1_=r|pU(kdMN>AJ4= zw|S?LIm4rg@FKIxg+FG5cm-vjM+~%7)_PR8-d8ujA>Cbs+a|`x+cG}ToZft zfc@3dj{Ektg0{=mAZVcB$F{OG zUp6jE`Hbb3R38*R#B`rnZ}ji~y9}AM=iIxk^E(XlFr8J->1E>HLrh|z<0$qJS2eO~ z;;9-|=1yg*8I2k>Mvd-^c_M%XqIN=WPgm5hlnEOczS7HsLE}?FWf*T0&XY| zM_aS=0%H${n^QWbE<27KJPs*S8gI;5a|+dprGeHV1{}M_C~aZp_@j4P-VNm8o(d3dA(nZNvOPSmZC9(}(52ZLWOjHi38Msi;dp5#Hz zEru&2uCo8_nydzC7$Rx&0zsK!^2cSOV^I?u@}b!zptM(`NF&iC%G9Y-4R9-s09k%C zo5ULpQYCp#kK8r_dx5)60(V&$BKZN8mo#!scuFgmH6)**>L!x;S%MB!)ou9j;Re`c zM#e>9!9nmynSpVF48-LT^!Bd^V_+oN->wYUes#~^ zaQ9CIzifr6DPP3qw=0;l<&Mw!60SPh=ynYpR|W3s+WSl$z4JV109N(yuMYP=eUw(>2pBQbI)5h~2fm+s2z}ZWMA2L+DDUBzwD2fWr|>eTX=Kmf zgDrb6p;W$|3vVz4+KDX|_Y);&e=KE!j;&}U;?FGqTp-rtNf|@2 zYlWhH=V9%Onc?d0jr=`+gnz#B=IA4xx?#m$;i)6?6BBqnQl>X&)`ii%VKm|UL#H@u z>)`N>5E6V>i1alSRgFlsLVvoIzH+E98+lTkw=O9SZu4(l=n*goaP+4uXtic zX1XF~fAWL@&}Ey?;F}o-@l3^xJe}hl4)Q#@UM=(TNGBHr6Kv~KYhJkVEZq;5hU`sE z`8m2Z@@4hMur9^$?zcOzbstapy-m4ydRh6~XjWL~Zx{x|s%ikN!3QDT_Xd zi`$l9eb+*k=1Z8}`hGQna!PtAZsFkgcX2c5GD6NB!Oi(&%&8h%-s5B)^Vv6+j#2uT zkIx!m6?2cgj#bBK7hL%(wp%G$66cQx#sRGzmOR9V;`9l}=fR{*qsbgil*u%e>Dsq% zUn6WXMdd)3Pf)8KG^r-i1dL2lEtVD_bm`K?tV+<*6!|WtHR+m`oryZoF|SDg`8I8m zMIg6~{D~5LP4Y>j(h?bwCVK=lGO;yts!0K@Ka?pg2fmh|X*r$N6$*ef>8A-k0Z7lD zJ+hUV-5Srb_Fo zU?BXIo~vupo;}=M&3SchyddAPu)y8jg}%_(s1RSDutODNX{L_%9+vM~8>+sbb)pq{ zT(GqCtLIK(dym4msUmsE$)8jupTfn>3+}iA!g2}3=I3oPkG!lW799x0M{DTXxCh#| z&y6dE!Z;bM!)UE#XIuu);Pv2X)S#7Noj(`hn#VWaSQBrWbd!NWF)-_Y+4T)+e}h&+ zP|VEoG>(sE1Bjj*Ki*nCrcZl=hbH^jjm;_wt^L(xoTdr1j7>}1M4IqZeJG-|K&%Nu zO&S(24o+lQCqCQD+~ob_95(&=QI?w8&XzZmA^+1LtHD@J5A_oGFi_n zohJM=$D_5uB264?--6~j?gYg03A>u79`gUhY?+dp5!VPKM*YZzhcZ8h4jpPh&)y87 zSJ8}makVr_;3rTlQlyA!P?^hWH2d^sr5VrO6>|n&fNU?&7D!7wlU62R@5@0T7Z-TT z$Ea(fpEwOHK^N(|G(wTq3TmCOy&9l-^X6vrh6WIUx)ynB>03t_z$6z#@UR&Ye>}p8SgofK9@C_%Eg_;U2O`^hYGb8gM1F z0$`DsuRnI5<)NWun%ETmkG%76$F&`rEM;Gbbw76cJEw{H3^y&@xQWVbB9;-{0~d1U zv{pQ*`{mAUt&Y%w6X5_cgERG@auSs>_cw4h-*`&6ng!hO0JDn1P9fbwDmZ^4H5(T zN~gSP)UY;~=(kOhcdaCnJlQ0WmF(NHDc4p#?h4U7g}zHE(+Vk@1cJIR`P0t1oMfEx z6~Ky=pA;s0jlY(qNhXCS!T>2u%ER6PtGNYPXv$AZ*QCg)Z@vBY+h&!JuE~`qx!2CQ z_)si&M0_4f>NJ||wn0qVr*^aH^ka>JBAL0`R&0}eg|=BL%~K=bu+`2vfw0ICxE&{Z)WG%*(y3f+f0j#38nUcjZO{@)fwSda zTc?FXs*CVOt~8Mb4*kWK9tjY>#8%dNUNJ=@k=B4pyOp+^lOvmEZVAVkSlUXC6SHtNU<)c3_S>+3m7cX9HMpu<7 zZC36GeX4PkhZ;xE>p6k1p3{gc(x9OGn#o^A8*S^>Eoe6^fbIm3__kT1q?5M%I8n-s z+0gp4sgLX{vpbr#z3g_JNVi-K#4AIRf2|=Fuxg_hF@mPErD@6?!G$O0I=iYNEq2ik zIqh6iNCt`#H$PbGgq1+61GN*5qGs-C--PlI`09_IK;r_TkxGpaT)V4n|CYvUD}&lR zLQ$ZsSX-Or3Dg1>Y3JJIr`Qn@B4Rc<$ih{e2l@V`U^(uBlQk;YlZ?qtpbcD-FDYf3 zACT26nb#V9%>zg-^^CAXyI$o^(4??%MDj1$RaqiwwsJMdl_=R29!L{bo?4Hrop35! zGA}oTFhz4Bn)uZuweaO`SC%~zK4Af%097N7MlShzrIBh>5;%**Fg1kIsBr|Wx+V=( zOw*DjJu3jzJuylkE6^5r>zbZdeva2vhO}D!+2sppH3I56ktTcWdZ;{=FS6@o|5iGI z@7%d_&Ej))1dYaZyH3U}pKO+`Xr4^^|DMQo9sRr2PWpnKCEgPU!o%Iz|ESuMq=9n0 zXP>mPiVz6{z5-x@o3vb86Q&r@60|_j)~Mxfi0ID79btdheToKw%G#`<-|F51R1E|o zl`pVm*Eido?Yh|Y&@)O;{lg3fs*^N#`G-|Ek)BaLE-ozW4rI%khA#4)hYYn>ck^C!dd`UjxM*@W7 z`$CUOI*rU~Pz?lXu)o$HK#$>nAx);daC4`GBoR>-5OO0B*Us+4s)?QGGmemmBr4xo z%>8hH&ei|i>WHg+rj<9=TV0xGOBv%F(=fvRrPg{xJ(yZ9d3R zHbT8fqF3&kER^!>)mta;^csn15OTz1MZ<*-yasv2qaEQR1Rn+*o%w)^_k?v0XFpJ zEpB(VX3>+p`~)meD^t7}I`TpAQ3^`v%@EGAC#}Ce0omuw>LKQU6ND47akTb!>YrQi z)1u=DbK&}%Bqn;Ckiq{3M)j&o0DE+s+Limazn}IQmhAeKYn_sQK;hm+Wc104!LLu? zvdAR%*~i&uJmBp$j=Ln|&xRh~STx78_JxJLg*Gg{VM zXzZkTaUhmty1Ke?t)G{1PuM#{;+0b(C(>#HtZf&nZrqw17|1O?4x}_% z2P_Rr(YpkQN~7;C{2t_xUdzO^=1{dqh<5T3HtTJmIdt{<`ebMqoE;fz_g@jh145TtLb>P5$ZgSKfylM{j_Dtk@3B@DZ``;J zb!t~b=T}}d3y&X$iXLP`mMT#I*Lcj31h!Fwr}13<+6EANzSRxYs+Q-r#eI=g-L`ED zDwHe6&gW-#%e>I437Ry1#(-t3mW|P*VLfwQ52)dP|9uKNzuewz{?Iiw@~{7!i1*)n z%Ph|R?bk_Y(&$+R>zU8=ZU%t&?F&G!p55{8J8zobSFT*fn?1UqX_E$M^FmVt(8@c6 zkFRlhg@2n14 z+|^g{W#8Ta6fc^WgIHkXvuDqqLEWdS;q)o4#wRJ=i4({1RISR9M?>klc+{b7i^xGs z{0RtP%;SN5(Z64Bv#4H+<@@x07tNbCMC%utaf|nE@|@xyrVTjC<=@H2(~q%}Q~rCR z+uW7A!P_&6|BlIgd_8fU@rEB3;&2^V6%AH#k#@7$r(AF-H%VMv?rt5r;!G$HfwxVJ zZDmNOWaxXu@oV;Nw!dPWxG-kQBy{QAfwJ_Ikr6wA?uqPAeOF(YHf=Jxz4lV19P0YA zWsA|OMPs8p>9=UX{6Fwwhn5DMtt&cTZ#7DnENC`bDPPIyw_`@5UEAlmlWl?dZKr+M zKBHPPqGspLon^&eWMG`nADYo4kXog`e=-W(C&k-XK2m^N)Xvx8?c0rbn!kKzL1Ti+9+O@T)~IoFT)4;$?GdDF zZQFI?mds1s%n-sbi|^v+|4qm1U0)_oLNIOWWNvFbi-U&_VC9Ns>X^hLtno^u-(a@!c{A4v9lk;RBAHJ!W0*_V@BZLsy= zZ*TgVHBf%=!bp7FW;A{1QSV_Y74e@HCdu*2gZnPv)j4q7iECmpRIhFwH#Bl2xGmQL zPVHdh#xTmV+R3V`4WK+9*N_6|=#X$85N-ngaOW*Uj9Pgpfr9wNIPslwWIe0@6|hHJ zmGwO1;Fw)>=g*(R?p-@^?8qTA7;o6HF0%d9R(^gysKIt!wQ9N9ai)B9y;-wX5poy> z(&frmgpaT00wP|3X{%JLZa~}dT8iY>z{@6P9EwdidgL(n2JA6P+dh6uh8|Xmg%A}g zJi$1zJMrAJwXkx{rdVeFgLsjmMTtIyF-1ygKY}-lwB6C$n-7z& zUb}+KnX(uy?IuA+?u`1+H8P|1y!lJ%8u8RBS<~gj(8?3h?aM~=o%-SRhJA61#}uvm zXDMozYJ@ClbK%s*qxklZ!T7T4bR0RmA5)iqj}g;8z`M^6bFA`1`JG)5)vJf$tI^h0 zV1co={3}x zt#FZ|MoH7t#fp_MnGE{mGraR&Z|+P@#qiG2`(jin5B{5lG!FGpAd3bx^@|oS$(N53 zHislh{#BZ-o0~fuHaYj3r#HT!I!`}inBBNxU3@*}|Lt7|d{o8PJ%RKDLI@?0P!d85 zO+p|RM4A*)iULxlgLDz;(h&g>3!cd7<<5G#T{C2#Md;_5ghHOuJ`LcKpX(s3Va9Vc3@PVI~3xn|c z&MR_#Hfry;1_6aJ|JQS}DQ9W4Yv843HaI)v#jEwarLN?|u)&&Lm$7=sW#x)s**{Kw z5+go8tgLC3VK#oTE%JyDo^3&w1V&t7oa>R?l?Bhu^=A@tr?I=Z1q2Q1%(PiHo9P0F}NSE`$Zkjw6vMn6C)_Ix&t@i?3&`E&Q*Kpz!mL!RHZsUboLcH(hi9IJaV`$sys8;4lY&pCR zN6+m=?`EUW_v4pvFnEXH<}H@*1?luE;^!@2;l(FAAUY-r$ItIWS+6QMdEv0cRYtR* z4)8Bk9mme?!_`RcEtfK~;BdBL(Wl^3qP$TB3;x={E&n7`tZ-K;Rw4Y7XV&Bv5Rx#Q zIRnW41+s~NiFBu1H;BT@Csr-F8SLTXlc1Q-sAx$kNo7qJ1L-g6=k@S_bd+QigCc|X z@sa%t<$f($^0u|wCtu*QQ*I?L zz?!v!RHw*jDqlWxe7++hqtw0Q=~+w^`%)q6Dk?Ocp<;x@tN1U!oF{IW;<$S4x+r#0 zyfPYHym*l?nAO6m)92)+rD;nlW1qpK;;rt7oZrhggs!uhF#pK4e$7jHBz0D*q6Ew6 zy{xY0Qla~;pLu#7Q||Zr%=1tgr1_$Scvw1vYhhRAW_VKSC~u`jY1Hic6+FHDQl+Nv zmgMW)q;vIqPow^jO-cdNpGCi8TtcGs=wcR##7bHRX)G#lE~?>Xo^isSWoIY6s`Ap0 z;cPp8^0|oLGgV1^;bDt9Wunom_0wr$tn)A3JsfFVlx-TS*9a6+A$zfcoY8EU9}0OU zjg6D49+z-S9R-$qR#`!t53dzWO>>Fk6XM|P;3^#yag!M?0xsVv&?g)(=du0i3r-O0 zm;Pf~!3<{$Fr4Ykg*%tDsxk!ipK5L%Y?0%;cb!qRaN3qORYi7qSJrRZiru+GCa}wL z-Smw=$k3eQN->S^LBb-o%J9GHJ*0fRlW>IFdcyAXyDbxz`&Cdm4dwmT&pf^P@%_~M z-_GNdG#}qG>SLa-X&`1EB9wzk`@hj@eR0%Q<)WaQ!Vp^-wi)7-l-6G2`9hE4AU z>Lh+*LmXrXOJN!#oe`Jz*T^qzcuxPfv57}S)QSv?eMw%VMMPx~b(cN7%+yic{Da&P zyg%>dJfVF}^vR$CIw&&)Ql9qAQt0ppMu2|I!ubVan#JZr4YM3+)n=!}M2DjoiCc5A z&^PInS7wQ10%O{jcG+>M(cv+0caw3tRmg2|i#4%|n&?XWcLcN&{_hxOn#0Z5cziUp z0s2n;1>q4lGfkIW5yH@f9<2h=qF$v`Ga9n1yzI(1M&{>E>a_rGz28peJV$0%F`4Ge zQBePO<58nh9qCK6x6{nD5<23MML?~^;!rpfL+z2h@SM6Z@1ky4J*P`f6_=_UT8_8H zk4(3Rxw|7(qFnOF*Sj2knSID&wWZHkO^YI^S~LO=0Rhg4qS&4ajd5DE_Clt^<%dv~ z&O#%g5zq)|1kxa2D=*x|%kE@b)z>X%NL#;**J`FYN&nRdXaqC@8i9w0z{+h`Zsrl1 zLp{EFc$n&(Gy)m{jlex4p!tOF87iI7(g=h_Tt&ChEoJ)E^&GCsU0H$YhBv#8LxU$@ z$lShycm{|P)R??%Djy7dbGnbe7cVcLFlq& z%dG0k|M=sNWZF9(uV24j)ojAJN19lrcFY*w<|lb0<2!WIysC> zjZGrko|Jx-gz` zT=dbo;b7sTD5}z#e~~!Jyx!(n|gX zY4u@DjJ@I!Cg%j3DI~;*H-1g&_-~C=ZtdE&M#R7Vo)%`JD6-L;33U=TX)u?4`}U(_<6=aBG+?!%->lag!Op+g5De`&4$Q%U~z+iyY`Q&osf&fv>0zr=YV>G><= zu0oeCT`*Qhet0 zyHI$&E)-i=$z_-%?4Sk?9GL3C*}i={1`i&rnCqB~IPzhuEfijT`t(sslpW-R2@`}& z<~gP4*^W$OaDEv1Q`y$4@SGy*ad$0@r~Dhjw^#*u2s2uM-!tg{(m175?}#g*b)BBD z%WIEUYIjpCYfWpmL9Z7^;)S4g2&zyQ?d$c!%M#~R*hi850C{uKE^e~#odu-$HcfM_J_2C=|cuIp2PbtT20FTBn>8sd{`HGw2~z(EJ7U*9Xb>pJ9bPCHx7#=I!(uI!Wv4(TN=u1!mF0x$sdMMf*t2I3x^?TOC=~rjbebgp6Q=1ZRjR0e-+%wT zYS3vyhFZFGY3vr7sd@9}2}@iZBf0Reex1(Bq2)}=hrO@6ySqB~;6Wki5d}M9#0X&! zD}(Xl$79HlAu1m#c-|1~5L{hd)lEX4W0KLE3$5GHoysZN$wH!dXAiC_1n-VmFtUb_ z$lMW<_ToZY=_QsQiONO$ijd5wx}TdcsTCC~%^u_+rsC$g+mA-zM959C2=5>&Ci{nf zyymiH%bH&j8aHmNZhrH?Hf`D{MQR=v6chwLkcJSuqD6};i z;{Ns5U(;FL#`&j0k0C7TGJ-1BM>+2*N`bmK<;R)JC$RnapXlCX7+w@+w41R}qNE$3 zV}k*x>Qf8nub#%Xqko`tgMp}AIuQGXd!k~AY6uQJjtkdFmuQq=y}w6~%98lPCI&QN z5XI7^wD?Svmb9O^)Vpg}6W{O5nZP^mK%VQnf+gb;#7KdRcA+?eyLT5l)E^-oEAYxI zCdDhwB5eTa5Fxq%s9xQK1-YaRYF=qBVL>x7uX%c!h~4GULcMyX^7+hCXdrz+jh!SM zMUiWo#?3oYF&a$<_jFBRhyVQZ&yA$&m&Om%nMe;o+J*~>9v1>50Sp`={#SE#rcywIgdN#$a2 z61JswLTO3gu%nRooC%G=lC|fBB}^<|>6lhb4#MlR_KCHZt~t$%wz^}EO2|7*%i5Dq zu}ENGpz8d{F-+y|@9!@UdIlE0q>YY=Q0!;yoP9mZqju#c0>>Trc$R~wyEiUgJA;kF z7rbi6G7M}v5x;C(ioP$sEv^dToOTlTjij{^O>*;AG-Bdqs4Mx{ip9*2;TlnuvcfOv z^M#($M5a!KE4Q_xqNMd|bRtxe+|G|mm;=2_mlBoI4GwmY=K+e`ow`X3Na4*kr4e3z zC1T?!g-nasTsCb=5Tz#AN1Hl)flTf2A%h&nJ50SRtg>Rf+!dol4n(Lh%`IVew1!fx zRH>3OlDIp|!xY|EG?*xS=4nY=t4KeVT4<@%ldg=`-`1^LQ%73pA6*5sVB5*wEVE|K zQbP;&oEtZ8RKwI7LY&H>FRfz_Awy*YGj70u0YYfq7XbkQ>Y<{=+d}qhp`}WnBZn?O ziV48;XmL?7uUxrO4Xt>rf1C;px;JQH(|TrJ9JYV( z{xsn_^-GnG)RQD^cM{h@#0}Gpw`5EWT#bmAU1}3CZvIhxI;0w!4BLVj`M-EHw+Onc zwlsRSYC(LnJ_JHy9-grYj47|VCk^%65SE=KSZzS+b$T#mRXo!C6tQNvkr3$qip&0~uxO9$fU`TdG}_{^o_@bV~y z**}a!sO+$DHR_V$8P4zGjw9#x2-$n#bncIAg!F;3ZrU`jY)6zR7@I6l`h{ubQt68Q zBz)T@*MNB1WVA>HOl4_{F=I@{aUjT7DdGi^-BL`7ldc5A$~D}t)QvPuMQZ!VQ>#F;Pqbt7S;d9OooX@MZi_Nqp z$FGg(SkA-RD{Afaqq3nNltXFyn2n*3f13sHDp@X7_2YyGm_{qDhz%b-ix)<0#f{k8 zir;}&44KuOll;3p<_^wr!YfSDcV}@;kZ+iZI98N2XHuw_e^LT1W4bZSg?z$ID#v0- zm%8S`R(s4BcXWvr6hd(NikopO2a&q{{7|@9!F#SZX(zMV6ONW{T0e7EnUhcWwWmj* zS>2bjN|u9hsoVM93igs@7v$qBpY+NxZ63To4XZjOj_$Q+`51Yn#H2o=eJ2`ROO^;U z8M-B7KH)6S(vcY=Kp(TYpV>&1ks{!xo`y6TzC|fl^DsjJGfhU^!Q>I<17h$A8$82C zo~eH2DPr2(BGsx@OMcmDUT4`qSG}NALjd!LOpY_c-8||2C}5tKC_Z=Y;$S@@=IMRU z6Lyeu;^gBbAC8!^R^;gwu$-cHZ5Hzv^jk2m%)~CU2pygV0d`kfvJnCA!VXzJDzt91 zPizn!aT&fPX!+!BX;|fDY(29Yc4F;YLc)S?qVCAXmMA)tGE;`|nIzD`xdZ{NgtNJ! zmQHPsSBHLs%VAO3TvGb%=}R8o<2kf!AWpwrE@S$>D>FbQn|wGHxR$)Ow&MCp8Npbf z3cAQg6oK@cl0BjqYN^XARKNx6=k>5u@sCisHZnUz4{;x%2Gy66gn;dV(~&Mym;9q< z4`@_00vZ90fJPu^5U`cE^LO&xb+N5jGT)6iT9tO>RybNT0vZ90fJPu^5O9(A8-MJ* z7HumphHP%$x}B@upyv!kx|GKa0nV7P{+$B3rLl>|V_$oUI7!%ySb0 zoQ}11{~3(^WDUqSk(0tfsEd;$#=Tx2H7k|K$)a^xR)Bz>9bpBHpsQec1kQy~19vcMooSVm{sr7|sg+P45Z8*Bz+loAs+aRmlGLPf3 zb)KJ*+_iPiV1-&nDRtPRgn(AUk5X&uYx$1|q*so7VI42a%&9oZRL9Sg{so0!!Y+Ba zIMZ-WwxL{^hRW7hPHr62-#n#fMU3iLPVz}#*1xS_`;Ql=Pq$J8v^&B|8%9^l@(56| z)(!@KP-QJx(3#PfVPCKqaAcDtPlZOwykB?lD`jJ zQwnwMt}BYUjs!}JM%BQ_D^8vwDbqTo?0nQr^k50gke}^JSEL!@8XMKATVUh7Tb}l-3KR{a{ z+n>DXIBtoBT+BU0ToDQQa^)FeU9%Bl`CHh1JOa_NiLjS+gJvH+>3x|kpvyJDSiUZ9X@r@w7Dc-q=iMtBQlAIpI3VPyll=U!n4A} z2TVB`Yf69eg6WrG(Mde}mK7p4vLkc0i1;eDV!jJtepaIYbXap>YfObb@Gy3*+dBKk*ge$&c;}SGY={ouVi_J;M?8J1ug1T)&xHHgQ!Pg>hV+@SH!kB!_ziSx zQB${9j-YNGg``u$=39YV6Tvj=Wz@&0BmbL@8JGI4a{Bb9H0I};H-UM2Biua9MmBj& zTSh`c0_^SWQ`O5jhjsgG*=8KORsf~^Jd7-}{N)VQw3DMU3d=GRvq;wYjhSn(`jbwG zxn-KiY8L&#hsHHB10GXS+QM|K0+YVdr@!~Mu*oC1bBUUWd09zWrwYp~p6z5S8+97O zbVi+wdn%7u!C$P{j^br%;ZEXhBdJ^$%T4~9e2`gqa)JjqaB^|O@0*XHTg#d`-U&QF zb@eF^34wGz;l+#Qp>3Py>Jt)j?jaTP-?GV@H!r%r)(){TF=A2XLEk>z(5KgHD$}X& zj7N*+&m%rQMaeigIG|_uj&N~tR%u3#7=mUm)K%vWdutFnv~LBbF(f49Jf=(UY-ME@l|ou!rx6wv_fV~H z;@_!bYuvhZOX1n8M`sM^*HaZeVf-kxYS|Q2dWNu*>fW_IoSjW=@z&6RX#P?|(mC0j*doh!8I5&XG~SNpFI6GxR z?K@%V|5m`m!vj7(Wh{QJyfIg=UWF4Uj){Uwz>*~k(W!Gc^yt|ar%#+<2f4~q? zqHibH^~WE+0~M=0|M)?UhYcTtUw_+xW5v^vhbbc&U+6JiB-8z@*oiYp~+GWjH16#I{)S)dGwiHw8ZnmWK}RNBQy<(YVQr*!1^Cm7dmWOiV0J zoII|4vi0jdg`ZchL;F`-pApT}-LP z%0Bs3hgaRt4dqLi!tI5uhvFf`JO%UFgK6knCeK6_Ic`{^u(G86yj;|=n~R;|o*=gb zT_6u4Y==XK4&r}H7vY0h(^ZG{$NDws-mQbeXZ^b0@!s?)>i%?bbyjI6j2o3aVtbG> z^*PyxKsqICFA9Y>^yN#Jq#U@Rf!O6*FNmZ^?1>?q!!2J1h#WFn) z?-C{P-M3$(N3VX#8MSEnidediV&wq4c5K5}i|3jHw}tvoxG#qrWY4p2N((mC&teDWzD) zb}5gx^}LkAB`+Gw~)wOfP?T7q+CJT zQXkHLwnfvXFN)>rq%y1?P!nTD55wZG=Hr5Ndfwh8@y$0&(D}7)$pyaL`c*aRpf_OO z-aS~f@JrPel`B`nVriFI@4t&@>(o=}dA~jVbf8iekx`NG^72-=#|~auwEzGK@JU2L zRK~`rkxntsf_S2OAYx--&vO4BSsJ7%&pg=yQj9FKPZTxGebi}JsE9fb8 z&$Msf8Ba?`Ib+5)xT)lcFxvm)A5Sh7}35g{7dD7 zzbM@i9m?W^0aZYlY7|R)eZw*_QlhcJy6cu1qXwp;8n;e)jgL{*_nk= z2_HPL7v-cA+p&GC>HwE7{~EJq%|Xq;O4ubGOYJ&!@%@VB_~H8%;HZv0!MSs1GRsnj zTM&VCN|-~u_v8khJ?BfS={ad3arjC_T~TfH_yF6B z(qOrT3Khn=vuBlS!$Xb%x(G%0U0hvJp+ZH~WC1k-Wti z;uwXy(H1PDU_lR28pPcR`Q6;qzHc!xiPH9aRVQ%iQmD$;L0lR3;tHa5ylv}d#NJAP zo1`yNv?$!&-KCyRQn$(~ZCKbf3HQYDW5<-=m#&Rk(wSx@9HneK5-t>$dEp>dZ$800 zA!!t|??i;$BR23Y?xKi(s+TQ*^}DZNa*v8wBea);MDbD_<=hQ>uVK$W5lV?q>*bH( za}OztIIFU=iX*1AYuACFU>zkLRzdfI@GMqb?!`DYdh_!uhoVJ`DO`&c^Fpgutx-%m zEiKlEKsqJtBpVJ=tict*da&0YGx{xM-O%@YREEN3{K~2!EG;3r1Ex$Khc4nXK6L1S z8iuxN@uC{0zW7or^z7XamHmAXeIpugkDY{1KAwdE{d-~5=|i|PS^*t%tt8p=+8?;`{}QBmA9--~}TSmnVqRMr#@EC2p$1Abk-0pll3 zMK39{MT?h3ftp+nDv{aO!Bf#7$#=Z$CH7RMf*8}O98QGXK!lLPtlD-7U7D1{=>I!{ zm2%9XZT)~EIC3URlx!X~EG8Ql!&&;z?>vcb)?dK0RSRajJAx1X@L_|L1=pf^BkbL? z3%sM^*uQT#X1@21DCl{3qFM#a{bCWOzB?0DDwVD3^*F^tOy7Q#oX^g*q^C0qOWTj{T2Xbn85DU>K?S6P;S@wqPfyih*~tA+GteJ@ z{JBjT9yB1ly-T2V>vq_=b36DhB+&{+w)b>#k69v{3G({)LN0L5y%r5`oT`q6> z_2QQc6~#k^!xvJMK3|Q0BE978ermT4{fKlm&_6h=U0FYa+7 zp?B4;4L5`iks>NbEG0BJB13j#<(!_$9lWLLqRY*G1nAmoJz@7q8FXuT7zogxSvTpS zHZ0`K@}*@&i5BbV(;rWZMa-#o3^6HDLjkK036cp_@&Ye0Mfoy{f@)uvQN=wg^#OjJUOLrZCR+1 zGH*Al^pAU-tFr@^Piw7Sep&*HM458PW#(EQF9fs_&c^n(l^GqMk7+J%)hz=vm%`qR zjn|g&eYCMwg7*QIPWn&~u#9$iC{@oLnZ(6&lgHFA=5j~PbuBdl8iAZZKr7*#Kv|cO zD-hu91Wx_4gz#0|9q~)+S8|p>-?C+DC2U#zb?H`u0Oxdf8nqPh4yDv=l$@=WjVRz) z1o_!vWcPa7eU!7{Tf8)_ge~3#x&qdKz`2XUA?)T4N10J#39+$p#kLbyWXd7ukelX% zTcRGi%$!HSGIw0gU#BinBakHm9d=Q zty<}3ejblGZO$gIV~$UaOIr{9Kj#t9N;u~+*CpmM1SWPfEivYT8m@ApaQff)t`*eM zW5bV39tp01w3A=*fKVBeYl6pIA^G0xl@#$38Q8RF1PlbUJHkLh|7rv>L4b>DMs+NQ zgQuh5=jDn?i;iLL&?jX6b)sTXlW2^Xdsrswj&`*X%?jZ2s^)ZZEbK|qg-^lhLK_!k6f5BLktqFg5~Jf>cp(br3*%3pFgla9$z ztYYqT(sv}6S`9^8iBM3=jI8_LDX8;?0aHKZk1S^hKkuQZ|gu$xEgaL~Vza z-W!sW)zD?-AOd{Pa5s<59ovojug%%CKisr^Z4OpI7o`!<2xtTzX9TE#6Yt*H_y5{M VFQU%kou>c*002ovPDHLkV1h;fVru{Z literal 0 HcmV?d00001 From 7c8c84ab3954e439a8fdf780d3a597980f270ec6 Mon Sep 17 00:00:00 2001 From: Chris Date: Wed, 21 Feb 2024 16:09:11 -0500 Subject: [PATCH 03/22] updating CLI reference docs, and linking to them from NAT docs. --- docs/cli_reference.md | 181 +- docs/cli_stats_reference.md | 4712 ++++++---- docs/config_command_guide.md | 15538 ++++++++++++++++++++++++++++++- docs/config_dnat.md | 11 +- docs/release_notes_128t_6.2.md | 2 +- docs/ts_nat_troubleshooting.md | 2 +- 6 files changed, 18568 insertions(+), 1878 deletions(-) mode change 100644 => 100755 docs/cli_stats_reference.md diff --git a/docs/cli_reference.md b/docs/cli_reference.md index 23e4dd4d85..6004cc2088 100644 --- a/docs/cli_reference.md +++ b/docs/cli_reference.md @@ -12,7 +12,7 @@ Assign the current router to a Mist organization. #### Usage ``` -adopt [{org-id | registration-code }] [force] [router-name ] +adopt [{org-id | registration-code }] [force] [router-name ] [mist-instance ] ``` ##### Keyword Arguments @@ -20,6 +20,7 @@ adopt [{org-id | registration-code }] [force] [route | name | description | | ---- | ----------- | | force | Skip confirmation prompt. | +| mist-instance | Global01 \| Global02 \| Global03 \| Global04 \| Global05 \| EMEA01 \| EMEA02 \| EMEA03 \| APAC01 \| APAC02 \| APAC03 \| APAC04 \| APAC05 \| USGov01 (default: Global01) | | org-id | The ID of the Mist organization where the router is assigned. | | registration-code | The registration code used to assign this router to an organization. | | router-name | Assign a name to the router. | @@ -34,9 +35,14 @@ adopt [{org-id | registration-code }] [force] [route If you know the ID of the organization in Mist, or the registration code for the router, you can use the optional `org-id` or `registration-code` arguments. Otherwise, use the interactive dialog to walk through entering Mist credentials and assigning the router to an organization. +:::note +This command can only be run on a Router. +::: + | Release | Modification | | ------- | ----------------------------| | 6.0.0 | This feature was introduced | +| 6.3.0 | Added `mist-instance` | ## `clear app-id cache` @@ -612,6 +618,12 @@ connect [username ] router node | router | The router to connect to | | username | Username to use for login to the Managed Router (default: <current user>) | +#### Description + +:::note +This command can only be run on a Conductor. +::: + ## `create capture-filter` Creates a capture-filter using BPF syntax (as used in wireshark) on the target interface. @@ -1884,6 +1896,12 @@ manage plugin install [node ] [] | [`show plugins categories`](#show-plugins-categories) | Shows all possible plugin categories. | | [`show plugins installed`](#show-plugins-installed) | Shows installed plugins. | +#### Description + +:::note +This command can only be run on a Conductor. +::: + ## `manage plugin remove` Remove an installed plugin. @@ -1915,6 +1933,12 @@ manage plugin remove [node ] | [`show plugins categories`](#show-plugins-categories) | Shows all possible plugin categories. | | [`show plugins installed`](#show-plugins-installed) | Shows installed plugins. | +#### Description + +:::note +This command can only be run on a Conductor. +::: + ## `migrate` Migrate an SSR to a new conductor. For more details on the SSR router migration refer to [How to: Conductor Migration](howto_conductor_migration.md). @@ -3129,6 +3153,12 @@ send command reconnect disconnected [force] | [`show assets software`](#show-assets-software) | Shows assets software information. | | [`show assets summary`](#show-assets-summary) | A summary of assets connected to the Conductor. | +#### Description + +:::note +This command can only be run on a Conductor. +::: + ## `send command restart` Restart an SSR node @@ -3167,7 +3197,9 @@ send command restart [force] router node #### Description -_send command_ is only available within the PCLI of an SSR Conductor. +:::note +This command can only be run on a Conductor. +::: ## `send command rollback` @@ -3207,7 +3239,9 @@ send command rollback [force] {router | resource-group #### Description -_send command_ is only available within the PCLI of an SSR Conductor. +:::note +This command can only be run on a Conductor. +::: ## `send command start` @@ -3247,7 +3281,9 @@ send command start [force] router node #### Description -_send command_ is only available within the PCLI of an SSR Conductor. +:::note +This command can only be run on a Conductor. +::: ## `send command stop` @@ -3287,7 +3323,9 @@ send command stop [force] router node #### Description -_send command_ is only available within the PCLI of an SSR Conductor. +:::note +This command can only be run on a Conductor. +::: ## `send command sync` @@ -3330,6 +3368,10 @@ send command sync [{router | resource-group }] [force] Transition an asset back to **connected** and perform a sync. The sync operation ensures the asset is provisioned correctly and all plugin changes are applied. +:::note +This command can only be run on a Conductor. +::: + #### Version History | Release | Modification | | ------- | --------------------------- | @@ -3380,7 +3422,9 @@ send command upgrade [dry-run] [force] {router | resource-group | resource-group ...] The shell command allows administrators to execute a bash shell, or to execute a command within the context of a bash shell (specified as a series of optional parameters to the _shell_ command). +:::note +This command can only be run by users that are a part of the 'admin' group. +::: + #### Example ``` @@ -4481,6 +4535,10 @@ show assets [{router | resource-group }] [force] [node The _show assets_ command displays the automated provisioning status of the SSR nodes within an Authority. With SSR's automated provisioning feature set, each "asset" represents a platform into which the SSR software is installed, updated, managed, etc. The _show assets_ command allows administrators to see, at a glance, the state of all assets – including which software versions have been installed on which nodes, what their router and node identifiers are, etc. +:::note +This command can only be run on a Conductor. +::: + #### Example ``` @@ -4546,6 +4604,10 @@ show assets errors [{router | resource-group }] [force] _show assets errors_ will display all assets with at least one automated provisioner related error. +:::note +This command can only be run on a Conductor. +::: + #### Example ``` @@ -4611,6 +4673,10 @@ Displays software related information for each managed asset. The following info - Software versions currently being downloaded. - Previously downloaded versions that can be used to upgrade the platform. +:::note +This command can only be run on a Conductor. +::: + #### Example ``` @@ -4684,6 +4750,10 @@ show assets summary [{router | resource-group }] [force _show assets summary_ will display a total of all assets in each state. +:::note +This command can only be run on a Conductor. +::: + #### Example ``` @@ -5472,6 +5542,12 @@ Display all routers with a locally modified config version. show config locally-modified ``` +#### Description + +:::note +This command can only be run on a Conductor. +::: + ## `show config out-of-sync` Display all routers with a config version that is out of sync with the conductor. @@ -5482,6 +5558,12 @@ Display all routers with a config version that is out of sync with the conductor show config out-of-sync ``` +#### Description + +:::note +This command can only be run on a Conductor. +::: + ## `show config running` Display running configuration data @@ -6117,6 +6199,12 @@ show dynamic-peer-update [{router | resource-group }] [ | [`show stats dynamic-peer-update`](cli_stats_reference.md#show-stats-dynamic-peer-update) | Stats pertaining to dynamic peer update processes | | [`sync peer addresses`](#sync-peer-addresses) | Synchronize dynamic addresses (DHCP and PPPoE) between routers and a conductor. | +#### Description + +:::note +This command can only be run on a Conductor. +::: + ## `show entitlement` Displays entitlement utilized. @@ -6391,7 +6479,7 @@ show fib [{service-name | hierarchy-service-name | contains-servic | name | description | | ---- | ----------- | | contains-service-name | The partial substring match to show for the fib | -| force | Skip confirmation prompt. Only required when targeting all routers. | +| force | Skip confirmation prompt. Only required when targeting all routers | | hierarchy-service-name | The hierarchy root to show for the fib | | match-service-name | The regex to match service names to show for the fib | | node | The node from which to retrieve fib entries | @@ -7554,6 +7642,8 @@ show network-interface [name ] [force] [node ] {router | re | command | description | | ------- | ----------- | | [`application`](#show-network-interface-application) | Display application data info for network-interfaces. | +| [`redundancy`](#show-network-interface-redundancy) | Display redundancy info for network-interfaces. | +| [`source-nat-rules`](#show-network-interface-source-nat-rules) | Display source NAT rules on a network-interface. Source NAT ports usage is available in the detail view for dynamic rules. | #### Description @@ -7671,6 +7761,53 @@ Tue 2020-04-21 15:26:19 UTC Completed in 0.76 seconds ``` +## `show network-interface redundancy` + +Display redundancy info for network-interfaces. + +#### Usage + +``` +show network-interface redundancy [name ] [force] [node ] {router | resource-group } +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| name | Network interface to display (if omitted, all will be displayed) | +| node | The node for which to display redundancy data | +| resource-group | The name of the resource group | +| router | The router for which to display redundancy data | + +#### Description + +The command _show network-interface redundancy_ can be used to display information regarding network-interface redundancy status + +## `show network-interface source-nat-rules` + +Display source NAT rules on a network-interface. Source NAT ports usage is available in the detail view for dynamic rules. + +#### Usage + +``` +show network-interface source-nat-rules name router node [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| name | The network-interface where the source NAT rules are configured | +| node | The node on which to run show source-nat-rules | +| router | The router on which to run show source-nat-rules | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary (default: summary) | ## `show ntp` @@ -9076,6 +9213,10 @@ show peers hostnames [{router | resource-group }] [forc | resource-group | The name of the resource group | | router | The router on which to display peer hostnames (default: all) | +:::note +This command can only be run on a Conductor. +::: + #### Example ``` @@ -9349,6 +9490,12 @@ show plugins available [{name | category }] [node ] | [`show plugins categories`](#show-plugins-categories) | Shows all possible plugin categories. | | [`show plugins installed`](#show-plugins-installed) | Shows installed plugins. | +#### Description + +:::note +This command can only be run on a Conductor. +::: + ## `show plugins categories` Shows all possible plugin categories. @@ -9368,6 +9515,12 @@ show plugins categories | [`show plugins available`](#show-plugins-available) | Shows latest verison of plugins available for install. | | [`show plugins installed`](#show-plugins-installed) | Shows installed plugins. | +#### Description + +:::note +This command can only be run on a Conductor. +::: + ## `show plugins installed` Shows installed plugins. @@ -9394,6 +9547,12 @@ show plugins installed [category ] [node ] | [`show plugins available`](#show-plugins-available) | Shows latest verison of plugins available for install. | | [`show plugins categories`](#show-plugins-categories) | Shows all possible plugin categories. | +#### Description + +:::note +This command can only be run on a Conductor. +::: + ## `show plugins state` Show plugin state data for a given plugin @@ -10292,7 +10451,11 @@ show step-repo clients [] | ---- | ----------- | | verbosity | detail \| summary (default: summary) | +#### Description +:::note +This command can only be run on a Conductor. +::: ## `show system` @@ -11145,6 +11308,10 @@ sync peer addresses [{router | resource-group }] [force This command will force a network element (or group of network elements) to synchronize any dynamically-learned IP addresses to its conductor. (The conductor will redistribute these dynamic addresses to other members of the Authority as necessary.) +:::note +This command can only be run on a Conductor, or a Router that is managed by a Conductor. +::: + #### Example ``` diff --git a/docs/cli_stats_reference.md b/docs/cli_stats_reference.md old mode 100644 new mode 100755 index 09d1af3df7..32fce3d885 --- a/docs/cli_stats_reference.md +++ b/docs/cli_stats_reference.md @@ -471,7 +471,7 @@ show stats aggregate-session by-device-interface bandwidth-received-forward [dev #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-device-interface bandwidth-received-other-protocol` @@ -525,7 +525,7 @@ show stats aggregate-session by-device-interface bandwidth-received-other-protoc #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-device-interface bandwidth-received-other-protocol-reverse` @@ -554,7 +554,7 @@ show stats aggregate-session by-device-interface bandwidth-received-other-protoc #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-device-interface bandwidth-received-reverse` @@ -583,7 +583,7 @@ show stats aggregate-session by-device-interface bandwidth-received-reverse [dev #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-device-interface bandwidth-received-tcp` @@ -637,7 +637,7 @@ show stats aggregate-session by-device-interface bandwidth-received-tcp-forward #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-device-interface bandwidth-received-tcp-reverse` @@ -666,7 +666,7 @@ show stats aggregate-session by-device-interface bandwidth-received-tcp-reverse #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-device-interface bandwidth-received-udp` @@ -720,7 +720,7 @@ show stats aggregate-session by-device-interface bandwidth-received-udp-forward #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-device-interface bandwidth-received-udp-reverse` @@ -749,7 +749,7 @@ show stats aggregate-session by-device-interface bandwidth-received-udp-reverse #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-device-interface bandwidth-tcp` @@ -828,7 +828,7 @@ show stats aggregate-session by-device-interface bandwidth-transmitted-forward [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-device-interface bandwidth-transmitted-other-protocol` @@ -882,7 +882,7 @@ show stats aggregate-session by-device-interface bandwidth-transmitted-other-pro #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-device-interface bandwidth-transmitted-other-protocol-reverse` @@ -911,7 +911,7 @@ show stats aggregate-session by-device-interface bandwidth-transmitted-other-pro #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-device-interface bandwidth-transmitted-reverse` @@ -940,7 +940,7 @@ show stats aggregate-session by-device-interface bandwidth-transmitted-reverse [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-device-interface bandwidth-transmitted-tcp` @@ -994,7 +994,7 @@ show stats aggregate-session by-device-interface bandwidth-transmitted-tcp-forwa #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-device-interface bandwidth-transmitted-tcp-reverse` @@ -1023,7 +1023,7 @@ show stats aggregate-session by-device-interface bandwidth-transmitted-tcp-rever #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-device-interface bandwidth-transmitted-udp` @@ -1077,7 +1077,7 @@ show stats aggregate-session by-device-interface bandwidth-transmitted-udp-forwa #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-device-interface bandwidth-transmitted-udp-reverse` @@ -1106,7 +1106,7 @@ show stats aggregate-session by-device-interface bandwidth-transmitted-udp-rever #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-device-interface bandwidth-udp` @@ -1160,7 +1160,7 @@ show stats aggregate-session by-device-interface bytes [device-interface ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bandwidth-received-other-protocol` @@ -8086,7 +8086,7 @@ show stats aggregate-session by-node bandwidth-received-other-protocol-forward [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bandwidth-received-other-protocol-reverse` @@ -8115,7 +8115,7 @@ show stats aggregate-session by-node bandwidth-received-other-protocol-reverse [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bandwidth-received-reverse` @@ -8144,7 +8144,7 @@ show stats aggregate-session by-node bandwidth-received-reverse [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bandwidth-received-tcp` @@ -8198,7 +8198,7 @@ show stats aggregate-session by-node bandwidth-received-tcp-forward [since ] [force] [router ] [forc #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-dropped-other-protocol-forward` @@ -8779,7 +8779,7 @@ show stats aggregate-session by-node bytes-dropped-other-protocol-forward [since #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-dropped-other-protocol-reverse` @@ -8808,7 +8808,7 @@ show stats aggregate-session by-node bytes-dropped-other-protocol-reverse [since #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-dropped-reverse` @@ -8837,7 +8837,7 @@ show stats aggregate-session by-node bytes-dropped-reverse [since ] [forc #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-dropped-tcp-forward` @@ -8866,7 +8866,7 @@ show stats aggregate-session by-node bytes-dropped-tcp-forward [since ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-dropped-tcp-reverse` @@ -8895,7 +8895,7 @@ show stats aggregate-session by-node bytes-dropped-tcp-reverse [since ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-dropped-udp-forward` @@ -8924,7 +8924,7 @@ show stats aggregate-session by-node bytes-dropped-udp-forward [since ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-dropped-udp-reverse` @@ -8953,7 +8953,7 @@ show stats aggregate-session by-node bytes-dropped-udp-reverse [since ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-other-protocol` @@ -8982,7 +8982,7 @@ show stats aggregate-session by-node bytes-other-protocol [since ] [force #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-received` @@ -9011,7 +9011,7 @@ show stats aggregate-session by-node bytes-received [since ] [force] [rou #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-received-forward` @@ -9040,7 +9040,7 @@ show stats aggregate-session by-node bytes-received-forward [since ] [for #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-received-other-protocol` @@ -9069,7 +9069,7 @@ show stats aggregate-session by-node bytes-received-other-protocol [since ] [for #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-received-tcp` @@ -9185,7 +9185,7 @@ show stats aggregate-session by-node bytes-received-tcp [since ] [force] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-received-tcp-forward` @@ -9214,7 +9214,7 @@ show stats aggregate-session by-node bytes-received-tcp-forward [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-received-tcp-reverse` @@ -9243,7 +9243,7 @@ show stats aggregate-session by-node bytes-received-tcp-reverse [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-received-udp` @@ -9272,7 +9272,7 @@ show stats aggregate-session by-node bytes-received-udp [since ] [force] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-received-udp-forward` @@ -9301,7 +9301,7 @@ show stats aggregate-session by-node bytes-received-udp-forward [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-received-udp-reverse` @@ -9330,7 +9330,7 @@ show stats aggregate-session by-node bytes-received-udp-reverse [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-tcp` @@ -9359,7 +9359,7 @@ show stats aggregate-session by-node bytes-tcp [since ] [force] [router < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-transmitted` @@ -9388,7 +9388,7 @@ show stats aggregate-session by-node bytes-transmitted [since ] [force] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-transmitted-forward` @@ -9417,7 +9417,7 @@ show stats aggregate-session by-node bytes-transmitted-forward [since ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-transmitted-other-protocol` @@ -9446,7 +9446,7 @@ show stats aggregate-session by-node bytes-transmitted-other-protocol [since ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-transmitted-tcp` @@ -9562,7 +9562,7 @@ show stats aggregate-session by-node bytes-transmitted-tcp [since ] [forc #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-transmitted-tcp-forward` @@ -9591,7 +9591,7 @@ show stats aggregate-session by-node bytes-transmitted-tcp-forward [since ] [forc #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node bytes-transmitted-udp-forward` @@ -9678,7 +9678,7 @@ show stats aggregate-session by-node bytes-transmitted-udp-forward [since ] [force] [router < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node gross-entitlement` @@ -9815,7 +9815,7 @@ show stats aggregate-session by-node packets-dropped-forward [since ] [fo #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-dropped-other-protocol-forward` @@ -9844,7 +9844,7 @@ show stats aggregate-session by-node packets-dropped-other-protocol-forward [sin #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-dropped-other-protocol-reverse` @@ -9873,7 +9873,7 @@ show stats aggregate-session by-node packets-dropped-other-protocol-reverse [sin #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-dropped-reverse` @@ -9902,7 +9902,7 @@ show stats aggregate-session by-node packets-dropped-reverse [since ] [fo #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-dropped-tcp-forward` @@ -9931,7 +9931,7 @@ show stats aggregate-session by-node packets-dropped-tcp-forward [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-dropped-tcp-reverse` @@ -9960,7 +9960,7 @@ show stats aggregate-session by-node packets-dropped-tcp-reverse [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-dropped-udp-forward` @@ -9989,7 +9989,7 @@ show stats aggregate-session by-node packets-dropped-udp-forward [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-dropped-udp-reverse` @@ -10018,7 +10018,7 @@ show stats aggregate-session by-node packets-dropped-udp-reverse [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-other-protocol` @@ -10097,7 +10097,7 @@ show stats aggregate-session by-node packets-received-forward [since ] [f #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-received-other-protocol` @@ -10151,7 +10151,7 @@ show stats aggregate-session by-node packets-received-other-protocol-forward [si #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-received-other-protocol-reverse` @@ -10180,7 +10180,7 @@ show stats aggregate-session by-node packets-received-other-protocol-reverse [si #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-received-reverse` @@ -10209,7 +10209,7 @@ show stats aggregate-session by-node packets-received-reverse [since ] [f #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-received-tcp` @@ -10263,7 +10263,7 @@ show stats aggregate-session by-node packets-received-tcp-forward [since #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-received-tcp-reverse` @@ -10292,7 +10292,7 @@ show stats aggregate-session by-node packets-received-tcp-reverse [since #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-received-udp` @@ -10346,7 +10346,7 @@ show stats aggregate-session by-node packets-received-udp-forward [since #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-received-udp-reverse` @@ -10375,7 +10375,7 @@ show stats aggregate-session by-node packets-received-udp-reverse [since #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-tcp` @@ -10454,7 +10454,7 @@ show stats aggregate-session by-node packets-transmitted-forward [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-transmitted-other-protocol` @@ -10508,7 +10508,7 @@ show stats aggregate-session by-node packets-transmitted-other-protocol-forward #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-transmitted-other-protocol-reverse` @@ -10537,7 +10537,7 @@ show stats aggregate-session by-node packets-transmitted-other-protocol-reverse #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-transmitted-reverse` @@ -10566,7 +10566,7 @@ show stats aggregate-session by-node packets-transmitted-reverse [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node packets-transmitted-tcp` @@ -10620,7 +10620,7 @@ show stats aggregate-session by-node packets-transmitted-tcp-forward [since ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node tcp-bad-flag-combinations-forward` @@ -10890,7 +10890,7 @@ show stats aggregate-session by-node tcp-bad-flag-combinations-forward [since ] [force] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node tcp-duplicate-acks-forward` @@ -10977,7 +10977,7 @@ show stats aggregate-session by-node tcp-duplicate-acks-forward [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node tcp-duplicate-acks-reverse` @@ -11006,7 +11006,7 @@ show stats aggregate-session by-node tcp-duplicate-acks-reverse [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node tcp-invalid-state-transitions` @@ -11035,7 +11035,7 @@ show stats aggregate-session by-node tcp-invalid-state-transitions [since ] [force] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node tcp-out-of-window-forward` @@ -11151,7 +11151,7 @@ show stats aggregate-session by-node tcp-out-of-window-forward [since ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node tcp-out-of-window-reverse` @@ -11180,7 +11180,7 @@ show stats aggregate-session by-node tcp-out-of-window-reverse [since ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node tcp-resets` @@ -11209,7 +11209,7 @@ show stats aggregate-session by-node tcp-resets [since ] [force] [router #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node tcp-resets-received` @@ -11238,7 +11238,7 @@ show stats aggregate-session by-node tcp-resets-received [since ] [force] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node tcp-resets-received-forward` @@ -11267,7 +11267,7 @@ show stats aggregate-session by-node tcp-resets-received-forward [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node tcp-resets-received-reverse` @@ -11296,7 +11296,7 @@ show stats aggregate-session by-node tcp-resets-received-reverse [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node tcp-resets-transmitted` @@ -11325,7 +11325,7 @@ show stats aggregate-session by-node tcp-resets-transmitted [since ] [for #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-node tcp-resets-transmitted-forward` @@ -11354,7 +11354,7 @@ show stats aggregate-session by-node tcp-resets-transmitted-forward [since ] [since #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-service bytes-dropped-forward` @@ -12575,7 +12575,7 @@ show stats aggregate-session by-service bytes-dropped-forward [service #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-service bytes-dropped-other-protocol-forward` @@ -12605,7 +12605,7 @@ show stats aggregate-session by-service bytes-dropped-other-protocol-forward [se #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-service bytes-dropped-other-protocol-reverse` @@ -12635,7 +12635,7 @@ show stats aggregate-session by-service bytes-dropped-other-protocol-reverse [se #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-service bytes-dropped-reverse` @@ -12665,7 +12665,7 @@ show stats aggregate-session by-service bytes-dropped-reverse [service #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-service bytes-dropped-tcp-forward` @@ -12695,7 +12695,7 @@ show stats aggregate-session by-service bytes-dropped-tcp-forward [service ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-service bytes-received` @@ -12844,7 +12844,7 @@ show stats aggregate-session by-service bytes-received [service ] [sinc #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-service bytes-received-forward` @@ -12874,7 +12874,7 @@ show stats aggregate-session by-service bytes-received-forward [service ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-service bytes-received-tcp-forward` @@ -13053,7 +13053,7 @@ show stats aggregate-session by-service bytes-received-tcp-forward [service ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-service bytes-received-udp-forward` @@ -13142,7 +13142,7 @@ show stats aggregate-session by-service bytes-received-udp-forward [service ] [since ] [s #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-service bytes-transmitted-forward` @@ -13260,7 +13260,7 @@ show stats aggregate-session by-service bytes-transmitted-forward [service #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-service bytes-transmitted-tcp-forward` @@ -13439,7 +13439,7 @@ show stats aggregate-session by-service bytes-transmitted-tcp-forward [service < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-service bytes-transmitted-tcp-reverse` @@ -13469,7 +13469,7 @@ show stats aggregate-session by-service bytes-transmitted-tcp-reverse [service < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-service bytes-transmitted-udp` @@ -13498,7 +13498,7 @@ show stats aggregate-session by-service bytes-transmitted-udp [service #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-service bytes-transmitted-udp-forward` @@ -13528,7 +13528,7 @@ show stats aggregate-session by-service bytes-transmitted-udp-forward [service < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-service bytes-transmitted-udp-reverse` @@ -13558,7 +13558,7 @@ show stats aggregate-session by-service bytes-transmitted-udp-reverse [service < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-service bytes-udp` @@ -13587,7 +13587,7 @@ show stats aggregate-session by-service bytes-udp [service ] [since ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-service tcp-duplicate-acks-forward` @@ -14835,7 +14835,7 @@ show stats aggregate-session by-service tcp-duplicate-acks-forward [service ] [s #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-service tcp-out-of-window-forward` @@ -15015,7 +15015,7 @@ show stats aggregate-session by-service tcp-out-of-window-forward [service ] [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-service tcp-resets-received-forward` @@ -15133,7 +15133,7 @@ show stats aggregate-session by-service tcp-resets-received-forward [service ] [since ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant bytes-dropped-forward` @@ -28067,7 +28067,7 @@ show stats aggregate-session by-tenant bytes-dropped-forward [tenant ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant bytes-dropped-other-protocol-forward` @@ -28097,7 +28097,7 @@ show stats aggregate-session by-tenant bytes-dropped-other-protocol-forward [ten #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant bytes-dropped-other-protocol-reverse` @@ -28127,7 +28127,7 @@ show stats aggregate-session by-tenant bytes-dropped-other-protocol-reverse [ten #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant bytes-dropped-reverse` @@ -28157,7 +28157,7 @@ show stats aggregate-session by-tenant bytes-dropped-reverse [tenant ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant bytes-dropped-tcp-forward` @@ -28187,7 +28187,7 @@ show stats aggregate-session by-tenant bytes-dropped-tcp-forward [tenant ] [s #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant bytes-received` @@ -28336,7 +28336,7 @@ show stats aggregate-session by-tenant bytes-received [tenant ] [since < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant bytes-received-forward` @@ -28366,7 +28366,7 @@ show stats aggregate-session by-tenant bytes-received-forward [tenant ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant bytes-received-other-protocol` @@ -28396,7 +28396,7 @@ show stats aggregate-session by-tenant bytes-received-other-protocol [tenant ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant bytes-received-tcp` @@ -28515,7 +28515,7 @@ show stats aggregate-session by-tenant bytes-received-tcp [tenant ] [sin #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant bytes-received-tcp-forward` @@ -28545,7 +28545,7 @@ show stats aggregate-session by-tenant bytes-received-tcp-forward [tenant ] [sin #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant bytes-received-udp-forward` @@ -28634,7 +28634,7 @@ show stats aggregate-session by-tenant bytes-received-udp-forward [tenant ] [since ] [sinc #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant bytes-transmitted-forward` @@ -28752,7 +28752,7 @@ show stats aggregate-session by-tenant bytes-transmitted-forward [tenant ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant bytes-transmitted-tcp-forward` @@ -28931,7 +28931,7 @@ show stats aggregate-session by-tenant bytes-transmitted-tcp-forward [tenant ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant bytes-transmitted-udp-forward` @@ -29020,7 +29020,7 @@ show stats aggregate-session by-tenant bytes-transmitted-udp-forward [tenant ] [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant packets-dropped-other-protocol-forward` @@ -29164,7 +29164,7 @@ show stats aggregate-session by-tenant packets-dropped-other-protocol-forward [t #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant packets-dropped-other-protocol-reverse` @@ -29194,7 +29194,7 @@ show stats aggregate-session by-tenant packets-dropped-other-protocol-reverse [t #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant packets-dropped-reverse` @@ -29224,7 +29224,7 @@ show stats aggregate-session by-tenant packets-dropped-reverse [tenant ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant packets-dropped-tcp-forward` @@ -29254,7 +29254,7 @@ show stats aggregate-session by-tenant packets-dropped-tcp-forward [tenant #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant packets-received-other-protocol` @@ -29481,7 +29481,7 @@ show stats aggregate-session by-tenant packets-received-other-protocol-forward [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant packets-received-other-protocol-reverse` @@ -29511,7 +29511,7 @@ show stats aggregate-session by-tenant packets-received-other-protocol-reverse [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant packets-received-reverse` @@ -29541,7 +29541,7 @@ show stats aggregate-session by-tenant packets-received-reverse [tenant #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant packets-received-tcp` @@ -29596,7 +29596,7 @@ show stats aggregate-session by-tenant packets-received-tcp-forward [tenant ] [sin #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant tcp-duplicate-acks-forward` @@ -30327,7 +30327,7 @@ show stats aggregate-session by-tenant tcp-duplicate-acks-forward [tenant ] [sinc #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant tcp-out-of-window-forward` @@ -30507,7 +30507,7 @@ show stats aggregate-session by-tenant tcp-out-of-window-forward [tenant ] [since ] [si #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant tcp-resets-received-forward` @@ -30625,7 +30625,7 @@ show stats aggregate-session by-tenant tcp-resets-received-forward [tenant ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats aggregate-session by-tenant tcp-resets-transmitted-forward` @@ -30714,7 +30714,7 @@ show stats aggregate-session by-tenant tcp-resets-transmitted-forward [tenant ] [force] [router #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id application-director cache miss` @@ -31136,7 +31136,7 @@ show stats app-id application-director cache miss [since ] [force] [route #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id application-director cache size` @@ -31177,7 +31177,7 @@ show stats app-id application-director cache size [since ] [force] [route #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id application-director lookup` @@ -31239,7 +31239,7 @@ show stats app-id application-director lookup failure [since ] [force] [r #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id application-director lookup miss` @@ -31268,7 +31268,7 @@ show stats app-id application-director lookup miss [since ] [force] [rout #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id application-director lookup success` @@ -31297,7 +31297,7 @@ show stats app-id application-director lookup success [since ] [force] [r #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications` @@ -31495,7 +31495,7 @@ show stats app-id applications acknowledgement-round-trip forward count [netintf #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications acknowledgement-round-trip forward max` @@ -31536,7 +31536,7 @@ show stats app-id applications acknowledgement-round-trip forward max [netintf < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications acknowledgement-round-trip forward min` @@ -31577,7 +31577,7 @@ show stats app-id applications acknowledgement-round-trip forward min [netintf < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications acknowledgement-round-trip forward total` @@ -31618,7 +31618,7 @@ show stats app-id applications acknowledgement-round-trip forward total [netintf #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications acknowledgement-round-trip reverse` @@ -31705,7 +31705,7 @@ show stats app-id applications acknowledgement-round-trip reverse count [netintf #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications acknowledgement-round-trip reverse max` @@ -31746,7 +31746,7 @@ show stats app-id applications acknowledgement-round-trip reverse max [netintf < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications acknowledgement-round-trip reverse min` @@ -31787,7 +31787,7 @@ show stats app-id applications acknowledgement-round-trip reverse min [netintf < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications acknowledgement-round-trip reverse total` @@ -31828,7 +31828,7 @@ show stats app-id applications acknowledgement-round-trip reverse total [netintf #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications bytes-received-reverse` @@ -31868,7 +31868,7 @@ show stats app-id applications bytes-received-reverse [netintf ] [appli #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications bytes-transmitted-forward` @@ -31908,7 +31908,7 @@ show stats app-id applications bytes-transmitted-forward [netintf ] [ap #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications capacity-limits` @@ -31981,7 +31981,7 @@ show stats app-id applications capacity-limits quad-zero-client-used [since ] [force] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications classify-source` @@ -32093,7 +32093,7 @@ show stats app-id applications classify-source domain-name [application-name ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications expiration next-hop timer-set-timestamp` @@ -32486,7 +32486,7 @@ show stats app-id applications expiration next-hop timer-set-timestamp [netintf #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications expiration timer-cleared` @@ -32521,7 +32521,7 @@ show stats app-id applications expiration timer-cleared [since ] [force] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications expiration timer-set` @@ -32556,7 +32556,7 @@ show stats app-id applications expiration timer-set [since ] [force] [rou #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications next-hops-added` @@ -32658,7 +32658,7 @@ show stats app-id applications packets-received-reverse [netintf ] [app #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications packets-transmitted-forward` @@ -32698,7 +32698,7 @@ show stats app-id applications packets-transmitted-forward [netintf ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications reclassified-from` @@ -32734,7 +32734,7 @@ show stats app-id applications reclassified-from [application-name ] [application #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications sessions close-before-establishment` @@ -32895,7 +32895,7 @@ show stats app-id applications sessions close-before-establishment [netintf ] [application #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications sessions length` @@ -33020,7 +33020,7 @@ show stats app-id applications sessions length count [netintf ] [protoc #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications sessions length max` @@ -33061,7 +33061,7 @@ show stats app-id applications sessions length max [netintf ] [protocol #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications sessions length min` @@ -33102,7 +33102,7 @@ show stats app-id applications sessions length min [netintf ] [protocol #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications sessions length total` @@ -33143,7 +33143,7 @@ show stats app-id applications sessions length total [netintf ] [protoc #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications sessions success` @@ -33183,7 +33183,7 @@ show stats app-id applications sessions success [netintf ] [application #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications tcp-bad-flag-combinations-forward` @@ -33223,7 +33223,7 @@ show stats app-id applications tcp-bad-flag-combinations-forward [netintf ] [a #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications tcp-duplicate-acks-reverse` @@ -33343,7 +33343,7 @@ show stats app-id applications tcp-duplicate-acks-reverse [netintf ] [a #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications tcp-invalid-state-transitions-forward` @@ -33383,7 +33383,7 @@ show stats app-id applications tcp-invalid-state-transitions-forward [netintf ] [ap #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications tcp-out-of-window-reverse` @@ -33503,7 +33503,7 @@ show stats app-id applications tcp-out-of-window-reverse [netintf ] [ap #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications tcp-resets-received-forward` @@ -33543,7 +33543,7 @@ show stats app-id applications tcp-resets-received-forward [netintf ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications tcp-resets-received-reverse` @@ -33583,7 +33583,7 @@ show stats app-id applications tcp-resets-received-reverse [netintf ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications tcp-resets-transmitted-forward` @@ -33623,7 +33623,7 @@ show stats app-id applications tcp-resets-transmitted-forward [netintf #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications tcp-resets-transmitted-reverse` @@ -33663,7 +33663,7 @@ show stats app-id applications tcp-resets-transmitted-reverse [netintf #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications tcp-retransmission-packets-received-forward` @@ -33703,7 +33703,7 @@ show stats app-id applications tcp-retransmission-packets-received-forward [neti #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications tcp-retransmission-packets-received-reverse` @@ -33743,7 +33743,7 @@ show stats app-id applications tcp-retransmission-packets-received-reverse [neti #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications tcp-retransmission-packets-transmitted-forward` @@ -33783,7 +33783,7 @@ show stats app-id applications tcp-retransmission-packets-transmitted-forward [n #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications tcp-retransmission-packets-transmitted-reverse` @@ -33823,7 +33823,7 @@ show stats app-id applications tcp-retransmission-packets-transmitted-reverse [n #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications time-to-first-data-packet` @@ -33910,7 +33910,7 @@ show stats app-id applications time-to-first-data-packet count [netintf ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications time-to-first-data-packet min` @@ -33992,7 +33992,7 @@ show stats app-id applications time-to-first-data-packet min [netintf ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id applications time-to-first-data-packet total` @@ -34033,7 +34033,7 @@ show stats app-id applications time-to-first-data-packet total [netintf ] [since ] [fo #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id subcategory-lookup miss` @@ -34451,7 +34451,7 @@ show stats app-id subcategory-lookup miss [service ] [since ] [f #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id subcategory-lookup service-not-applicable` @@ -34480,7 +34480,7 @@ show stats app-id subcategory-lookup service-not-applicable [since ] [for #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id url-lookup` @@ -34543,7 +34543,7 @@ show stats app-id url-lookup hit [service ] [since ] [force] [ro #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id url-lookup miss` @@ -34573,7 +34573,7 @@ show stats app-id url-lookup miss [service ] [since ] [force] [r #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats app-id url-lookup service-not-applicable` @@ -34602,7 +34602,7 @@ show stats app-id url-lookup service-not-applicable [since ] [force] [rou #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats application-director` @@ -34729,7 +34729,7 @@ show stats application-director classify-session cache request [since ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats application-director classify-session cache success` @@ -34758,7 +34758,7 @@ show stats application-director classify-session cache success [since ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats application-director classify-session classified` @@ -34821,7 +34821,7 @@ show stats application-director classify-session classified domain [since ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats application-director classify-session classified transport` @@ -34879,7 +34879,7 @@ show stats application-director classify-session classified transport [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats application-director classify-session unclassified` @@ -34971,7 +34971,7 @@ show stats application-director classify-session unclassified domain [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats application-director classify-session unclassified transport` @@ -35029,7 +35029,7 @@ show stats application-director classify-session unclassified transport [since < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats application-director classify-session unclassified url` @@ -35058,7 +35058,7 @@ show stats application-director classify-session unclassified url [since #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats application-director classify-session websense` @@ -35090,6 +35090,7 @@ show stats application-director classify-session websense [since ] [force | command | description | | ------- | ----------- | | [`request`](#show-stats-application-director-classify-session-websense-request) | Websense Request (requests) (in-memory) | +| [`response-time`](#show-stats-application-director-classify-session-websense-response-time) | Response time (requests) (in-memory) | | [`success`](#show-stats-application-director-classify-session-websense-success) | Websense Success (requests) (in-memory) | ## `show stats application-director classify-session websense request` @@ -35120,7 +35121,37 @@ show stats application-director classify-session websense request [status ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| duration | The response time duration (comma-separated list) | +| force | Skip confirmation prompt. Only required when targeting all routers | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats application-director classify-session websense success` @@ -35149,7 +35180,7 @@ show stats application-director classify-session websense success [since #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats application-director requests` @@ -35180,7 +35211,7 @@ show stats application-director requests [endpoint ] [status ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats application-framework` @@ -36763,7 +36794,7 @@ show stats audit events produced [collector ] [type ] [subtype #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats automated-provisioner` @@ -37390,7 +37421,7 @@ show stats bfd by-peer-path async received miss [peer-name ] [peer-ho #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats bfd by-peer-path async received success` @@ -37430,7 +37461,7 @@ show stats bfd by-peer-path async received success [peer-name ] [peer #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats bfd by-peer-path async sent` @@ -37514,7 +37545,7 @@ show stats bfd by-peer-path async sent arp-failure [peer-name ] [peer #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats bfd by-peer-path async sent buffer-allocation-failure` @@ -37554,7 +37585,7 @@ show stats bfd by-peer-path async sent buffer-allocation-failure [peer-name ] [peer-hos #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats bfd by-peer-path average-latency` @@ -37713,7 +37744,7 @@ show stats bfd by-peer-path dynamic-damping current-hold-down-time [peer-name

] [peer-host ] [peer- #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats bfd by-peer-path echo sent buffer-allocation-failure` @@ -37960,7 +37991,7 @@ show stats bfd by-peer-path echo sent buffer-allocation-failure [peer-name ] [peer-host #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats bfd by-peer-path jitter` @@ -38157,7 +38188,7 @@ show stats bfd by-peer-path link-down local-oper-down [peer-name ] [p #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats bfd by-peer-path link-down remote-admin-down` @@ -38197,7 +38228,7 @@ show stats bfd by-peer-path link-down remote-admin-down [peer-name ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats bfd by-peer-path link-down remote-down` @@ -38237,7 +38268,7 @@ show stats bfd by-peer-path link-down remote-down [peer-name ] [peer- #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats bfd by-peer-path link-down timer-expiry` @@ -38277,7 +38308,7 @@ show stats bfd by-peer-path link-down timer-expiry [peer-name ] [peer #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats bfd by-peer-path link-up` @@ -38317,7 +38348,7 @@ show stats bfd by-peer-path link-up [peer-name ] [peer-host ] [pee #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats bfd by-peer-path local-source-nat-reset` @@ -38397,7 +38428,7 @@ show stats bfd by-peer-path local-source-nat-reset [peer-name ] [peer #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats bfd by-peer-path loss` @@ -38552,7 +38583,7 @@ show stats bfd by-peer-path neighbor failover [peer-name ] [peer-host #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats bfd by-peer-path neighbor source-nat-change` @@ -38592,7 +38623,7 @@ show stats bfd by-peer-path neighbor source-nat-change [peer-name ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats bfd dynamic-damping` @@ -38666,7 +38697,7 @@ show stats bfd dynamic-damping hold-down-link-flaps [since ] [force] [rou #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats bfd echo` @@ -39518,7 +39549,7 @@ show stats bfd received-invalid hostname-collision-with-static-ip [since #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats bfd received-invalid local-discriminator` @@ -41174,7 +41205,7 @@ show stats conflux messages write rate [pipeline ] [source ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats conflux messages write success` @@ -41232,7 +41263,7 @@ show stats conflux messages write total [pipeline ] [source ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats conflux stream` @@ -41301,7 +41332,7 @@ show stats conflux stream continue [pipeline ] [source ] [sinc #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats conflux stream delay` @@ -41332,7 +41363,7 @@ show stats conflux stream delay [pipeline ] [source ] [since < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats conflux stream end` @@ -41363,7 +41394,7 @@ show stats conflux stream end [pipeline ] [source ] [since ] [source ] [sinc #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats conflux stream responses` @@ -41460,7 +41491,7 @@ show stats conflux stream responses empty [pipeline ] [source #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats conflux stream responses error` @@ -41526,7 +41557,7 @@ show stats conflux stream responses error boundary [pipeline ] [source #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats conflux stream responses error connection` @@ -41557,7 +41588,7 @@ show stats conflux stream responses error connection [pipeline ] [sour #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats conflux stream responses error other` @@ -41588,7 +41619,7 @@ show stats conflux stream responses error other [pipeline ] [source ] [source ] [source ] [since < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats cpu` @@ -43740,7 +43771,7 @@ show stats external-protocols agent errors pim-over-svr-drops [since ] [f #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats external-protocols agent errors session-collision` @@ -43878,7 +43909,7 @@ show stats external-protocols agent packets pim-secure-vector-routed [since ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability icmp time-to-establishment` @@ -44612,7 +44643,7 @@ show stats highway destination-reachability icmp time-to-establishment max [serv #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability icmp time-to-establishment mean` @@ -44645,7 +44676,7 @@ show stats highway destination-reachability icmp time-to-establishment mean [ser #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability icmp time-to-establishment min` @@ -44678,7 +44709,7 @@ show stats highway destination-reachability icmp time-to-establishment min [serv #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability icmp timeout-before-establishment` @@ -44711,7 +44742,7 @@ show stats highway destination-reachability icmp timeout-before-establishment [s #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability icmp unreachable` @@ -44744,7 +44775,7 @@ show stats highway destination-reachability icmp unreachable [service ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability other` @@ -44815,7 +44846,7 @@ show stats highway destination-reachability other established [service #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability other time-to-establishment` @@ -44885,7 +44916,7 @@ show stats highway destination-reachability other time-to-establishment max [ser #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability other time-to-establishment mean` @@ -44918,7 +44949,7 @@ show stats highway destination-reachability other time-to-establishment mean [se #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability other time-to-establishment min` @@ -44951,7 +44982,7 @@ show stats highway destination-reachability other time-to-establishment min [ser #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability other timeout-before-establishment` @@ -44984,7 +45015,7 @@ show stats highway destination-reachability other timeout-before-establishment [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability other unreachable` @@ -45017,7 +45048,7 @@ show stats highway destination-reachability other unreachable [service #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability tcp` @@ -45089,7 +45120,7 @@ show stats highway destination-reachability tcp close-before-establishment [serv #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability tcp established` @@ -45122,7 +45153,7 @@ show stats highway destination-reachability tcp established [service ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability tcp time-to-establishment` @@ -45192,7 +45223,7 @@ show stats highway destination-reachability tcp time-to-establishment max [servi #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability tcp time-to-establishment mean` @@ -45225,7 +45256,7 @@ show stats highway destination-reachability tcp time-to-establishment mean [serv #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability tcp time-to-establishment min` @@ -45258,7 +45289,7 @@ show stats highway destination-reachability tcp time-to-establishment min [servi #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability tcp timeout-before-establishment` @@ -45291,7 +45322,7 @@ show stats highway destination-reachability tcp timeout-before-establishment [se #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability tcp unreachable` @@ -45324,7 +45355,7 @@ show stats highway destination-reachability tcp unreachable [service ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability tls` @@ -45395,7 +45426,7 @@ show stats highway destination-reachability tls close-before-establishment [serv #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability tls established` @@ -45428,7 +45459,7 @@ show stats highway destination-reachability tls established [service ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability tls time-to-establishment` @@ -45498,7 +45529,7 @@ show stats highway destination-reachability tls time-to-establishment max [servi #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability tls time-to-establishment mean` @@ -45531,7 +45562,7 @@ show stats highway destination-reachability tls time-to-establishment mean [serv #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability tls time-to-establishment min` @@ -45564,7 +45595,7 @@ show stats highway destination-reachability tls time-to-establishment min [servi #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability tls timeout-before-establishment` @@ -45597,7 +45628,7 @@ show stats highway destination-reachability tls timeout-before-establishment [se #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability udp` @@ -45668,7 +45699,7 @@ show stats highway destination-reachability udp established [service ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability udp time-to-establishment` @@ -45738,7 +45769,7 @@ show stats highway destination-reachability udp time-to-establishment max [servi #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability udp time-to-establishment mean` @@ -45771,7 +45802,7 @@ show stats highway destination-reachability udp time-to-establishment mean [serv #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability udp time-to-establishment min` @@ -45804,7 +45835,7 @@ show stats highway destination-reachability udp time-to-establishment min [servi #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability udp timeout-before-establishment` @@ -45837,7 +45868,7 @@ show stats highway destination-reachability udp timeout-before-establishment [se #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway destination-reachability udp unreachable` @@ -45870,7 +45901,7 @@ show stats highway destination-reachability udp unreachable [service ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats highway firewall-detector` @@ -46343,11 +46374,101 @@ show stats icmp reachability-probe service-routes [probe-profile-name ] [probe-address ] [netintf ] [next-hop-gateway ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| next-hop-gateway | The next hop's gateway for a service route (comma-separated list) | +| node | The name of the node generating this metric | +| probe-address | The target address for a ICMP probe (comma-separated list) | +| probe-profile-name | The profile name for an ICMP probe (comma-separated list) | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +## `show stats icmp reachability-probe service-routes exceeded-by-max-loss` + +The number of ICMP probe intervals whose maximum percent lost exceeds the profile SLA for the service route. + +#### Usage + +``` +show stats icmp reachability-probe service-routes exceeded-by-max-loss [probe-profile-name ] [probe-address ] [netintf ] [next-hop-gateway ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| next-hop-gateway | The next hop's gateway for a service route (comma-separated list) | +| node | The name of the node generating this metric | +| probe-address | The target address for a ICMP probe (comma-separated list) | +| probe-profile-name | The profile name for an ICMP probe (comma-separated list) | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +## `show stats icmp reachability-probe service-routes exceeded-by-mean-latency` + +The number of ICMP probe intervals whose mean latency exceeds the profile SLA for the service route. + +#### Usage + +``` +show stats icmp reachability-probe service-routes exceeded-by-mean-latency [probe-profile-name ] [probe-address ] [netintf ] [next-hop-gateway ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| next-hop-gateway | The next hop's gateway for a service route (comma-separated list) | +| node | The name of the node generating this metric | +| probe-address | The target address for a ICMP probe (comma-separated list) | +| probe-profile-name | The profile name for an ICMP probe (comma-separated list) | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + ## `show stats icmp reachability-probe service-routes jitter` Jitter in milliseconds for the service route. (in-memory) @@ -46379,7 +46500,7 @@ show stats icmp reachability-probe service-routes jitter [probe-profile-name ] [force] [router ] [node ] [force] [router ] [node #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats idp attacks received` @@ -47295,7 +47416,7 @@ show stats idp attacks received [since ] [force] [router ] [node #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats idp attacks total` @@ -47341,7 +47462,7 @@ show stats idp attacks total [since ] [force] [router ] [node ] [force] [router ] [node < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats idp packets processed` @@ -47621,7 +47742,7 @@ show stats idp packets processed [since ] [force] [router ] [node #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats idp packets protocol` @@ -47718,7 +47839,7 @@ show stats idp packets protocol icmp [since ] [force] [router ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats idp packets protocol other` @@ -47764,7 +47885,7 @@ show stats idp packets protocol other [since ] [force] [router ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats idp packets protocol tcp` @@ -47810,7 +47931,7 @@ show stats idp packets protocol tcp [since ] [force] [router ] [n #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats idp packets protocol udp` @@ -47856,7 +47977,7 @@ show stats idp packets protocol udp [since ] [force] [router ] [n #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats idp packets received` @@ -48621,7 +48742,7 @@ show stats ipfix dropped invalid-interface [since ] [force] [router ] [force] [router #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats ipfix enqueue` @@ -48710,7 +48831,7 @@ show stats ipfix enqueue attempts [since ] [force] [router ] [nod #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats ipfix record-export-rate` @@ -48739,7 +48860,7 @@ show stats ipfix record-export-rate [since ] [force] [router ] [n #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats ipfix time-per-export` @@ -48768,7 +48889,7 @@ show stats ipfix time-per-export [since ] [force] [router ] [node #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats ipfix time-per-session` @@ -48797,7 +48918,7 @@ show stats ipfix time-per-session [since ] [force] [router ] [nod #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats ipfix total-generation-time` @@ -48826,7 +48947,7 @@ show stats ipfix total-generation-time [since ] [force] [router ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats ipfix total-records` @@ -48855,7 +48976,7 @@ show stats ipfix total-records [since ] [force] [router ] [node < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats mars` @@ -48950,7 +49071,7 @@ show stats mars requests bad-response [process-name ] [since ] [status ] [ #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats memory` @@ -49441,7 +49562,7 @@ show stats mtu-discovery peer-path probe-timeout [peer-name ] [peer-h #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats mtu-discovery peer-path received` @@ -49474,7 +49595,7 @@ show stats mtu-discovery peer-path received [peer-name ] [peer-host < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats mtu-discovery peer-path received-icmp-fragmentation-needed` @@ -49507,7 +49628,7 @@ show stats mtu-discovery peer-path received-icmp-fragmentation-needed [peer-name #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats mtu-discovery peer-path sent` @@ -49577,7 +49698,7 @@ show stats mtu-discovery peer-path sent arp-failure [peer-name ] [pee #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats mtu-discovery peer-path sent buffer-allocation-failure` @@ -49610,7 +49731,7 @@ show stats mtu-discovery peer-path sent buffer-allocation-failure [peer-name ] [peer-ho #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats mtu-discovery probe-timeout` @@ -49925,7 +50046,7 @@ show stats network-interface received bytes [port ] [netintf ] [s #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats network-interface received packets` @@ -49956,7 +50077,7 @@ show stats network-interface received packets [port ] [netintf ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats network-interface sent` @@ -50021,7 +50142,7 @@ show stats network-interface sent bytes [port ] [netintf ] [since #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats network-interface sent packets` @@ -50052,7 +50173,7 @@ show stats network-interface sent packets [port ] [netintf ] [sin #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-capture` @@ -50135,7 +50256,7 @@ show stats packet-capture cloud-send-failure [core ] [port ] [since #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-capture cloud-send-success` @@ -50174,7 +50295,7 @@ show stats packet-capture cloud-send-success [core ] [port ] [since #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-capture success` @@ -51446,7 +51567,7 @@ show stats packet-processing action failure fec add allocation [core ] [po #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-processing action failure fec add buffer-expansion` @@ -51477,7 +51598,7 @@ show stats packet-processing action failure fec add buffer-expansion [core #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-processing action failure fec remove parity-discard` @@ -51638,7 +51759,7 @@ show stats packet-processing action failure fec remove parity-discard [core ] [port ] [port ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| core | The core number for which this metric was generated (comma-separated list) | +| force | Skip confirmation prompt. Only required when targeting all routers | +| node | The name of the node generating this metric | +| port | The device interface for which this metric was generated (comma-separated list) | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +## `show stats packet-processing action failure path-metrics invalid-path-index` + +The number of times path metrics have been discarded due to invalid path index + +#### Usage + +``` +show stats packet-processing action failure path-metrics invalid-path-index [core ] [port ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| core | The core number for which this metric was generated (comma-separated list) | +| force | Skip confirmation prompt. Only required when targeting all routers | +| node | The name of the node generating this metric | +| port | The device interface for which this metric was generated (comma-separated list) | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +## `show stats packet-processing action failure path-metrics sender-key` + +The number of times path metrics have been discarded due to invalid sender key + +#### Usage + +``` +show stats packet-processing action failure path-metrics sender-key [core ] [port ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| core | The core number for which this metric was generated (comma-separated list) | +| force | Skip confirmation prompt. Only required when targeting all routers | +| node | The name of the node generating this metric | +| port | The device interface for which this metric was generated (comma-separated list) | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | ## `show stats packet-processing action failure path-metrics sent-correlated-data` @@ -52999,6 +53205,33 @@ show stats packet-processing action failure path-metrics sent-unidirectional-rep | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | +## `show stats packet-processing action failure path-metrics update-allocation` + +The number of times path metrics have been discarded due to buffer allocation failure + +#### Usage + +``` +show stats packet-processing action failure path-metrics update-allocation [core ] [port ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| core | The core number for which this metric was generated (comma-separated list) | +| force | Skip confirmation prompt. Only required when targeting all routers | +| node | The name of the node generating this metric | +| port | The device interface for which this metric was generated (comma-separated list) | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + ## `show stats packet-processing action failure rate-limit-check` Statistics for 'rate-limit-check' @@ -53590,7 +53823,7 @@ show stats packet-processing action failure tcp-stitch allocation-failure [core #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-processing action failure tcp-stitch client-reset-before-establish` @@ -53621,7 +53854,7 @@ show stats packet-processing action failure tcp-stitch client-reset-before-estab #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-processing action failure tcp-stitch discarded-after-reset` @@ -53652,7 +53885,7 @@ show stats packet-processing action failure tcp-stitch discarded-after-reset [co #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-processing action failure tcp-stitch failed-to-establish` @@ -53683,7 +53916,7 @@ show stats packet-processing action failure tcp-stitch failed-to-establish [core #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-processing action failure tcp-stitch injection-failure` @@ -53714,7 +53947,7 @@ show stats packet-processing action failure tcp-stitch injection-failure [core < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-processing action failure tcp-stitch mss-mismatch` @@ -53745,7 +53978,7 @@ show stats packet-processing action failure tcp-stitch mss-mismatch [core #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-processing action failure tcp-stitch server-sack-disabled` @@ -53776,7 +54009,7 @@ show stats packet-processing action failure tcp-stitch server-sack-disabled [cor #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-processing action failure tcp-stitch unexpected-packet` @@ -53807,7 +54040,7 @@ show stats packet-processing action failure tcp-stitch unexpected-packet [core < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-processing action failure tcp-stitch window-rounded-up` @@ -53838,7 +54071,7 @@ show stats packet-processing action failure tcp-stitch window-rounded-up [core < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-processing action failure tcp-stitch window-truncated` @@ -53869,7 +54102,7 @@ show stats packet-processing action failure tcp-stitch window-truncated [core ] [p #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-processing action success fec add trailer-added` @@ -55559,7 +55792,7 @@ show stats packet-processing action success fec add trailer-added [core ] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-processing action success fec remove` @@ -55628,7 +55861,7 @@ show stats packet-processing action success fec remove completed-round [core #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-processing action success fec remove regenerated-packet` @@ -55690,7 +55923,7 @@ show stats packet-processing action success fec remove regenerated-packet [core #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-processing action success fec remove resync` @@ -55721,7 +55954,7 @@ show stats packet-processing action success fec remove resync [core ] [por #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-processing action success fec remove trailer-removed` @@ -55752,7 +55985,7 @@ show stats packet-processing action success fec remove trailer-removed [core ] [port ] [si | [`icmpv6-link-local-discards`](#show-stats-packet-processing-classifier-received-icmpv6-link-local-discards) | The number of discarded link-local ICMPv6 packets | | [`icmpv6-unknown-type-discards`](#show-stats-packet-processing-classifier-received-icmpv6-unknown-type-discards) | The number of ICMPv6 packets with unknown type discarded | | [`igmp`](#show-stats-packet-processing-classifier-received-igmp) | Stats pertaining to IGMP processing | +| [`invalid-gre-header`](#show-stats-packet-processing-classifier-received-invalid-gre-header) | The number of invalid GRE packets discarded | | [`invalid-header-length`](#show-stats-packet-processing-classifier-received-invalid-header-length) | The number of packets received with an invalid header length | | [`invalid-ipv6`](#show-stats-packet-processing-classifier-received-invalid-ipv6) | The number of invalid IPv6 packets received | | [`invalid-length`](#show-stats-packet-processing-classifier-received-invalid-length) | The number of packets received with an invalid length | @@ -60260,6 +60494,33 @@ show stats packet-processing classifier received igmp total [core ] [port | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | +## `show stats packet-processing classifier received invalid-gre-header` + +The number of invalid GRE packets discarded + +#### Usage + +``` +show stats packet-processing classifier received invalid-gre-header [core ] [port ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| core | The core number for which this metric was generated (comma-separated list) | +| force | Skip confirmation prompt. Only required when targeting all routers | +| node | The name of the node generating this metric | +| port | The device interface for which this metric was generated (comma-separated list) | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + ## `show stats packet-processing classifier received invalid-header-length` The number of packets received with an invalid header length @@ -60943,7 +61204,7 @@ show stats packet-processing classifier received pim total [core ] [port < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats packet-processing classifier received q-in-q` @@ -64705,12 +64966,13 @@ show stats packet-processing received [core ] [port ] [since | [`control-success`](#show-stats-packet-processing-received-control-success) | Number of control packets recieved | | [`injected-success`](#show-stats-packet-processing-received-injected-success) | The number of packets injected into the fast lane | | [`injected-timeout`](#show-stats-packet-processing-received-injected-timeout) | The number of injected packets dropped in fastlane due to excessive queue time | +| [`injected-unhandled-exception`](#show-stats-packet-processing-received-injected-unhandled-exception) | The number of injected packets dropped in fastlane due to unhandled exception | | [`interface-empty-head`](#show-stats-packet-processing-received-interface-empty-head) | The number of empty head packets received from the interface | | [`interface-invalid-chain`](#show-stats-packet-processing-received-interface-invalid-chain) | The number of invalid chain packets received from the interface | | [`interface-invalid-metadata-length`](#show-stats-packet-processing-received-interface-invalid-metadata-length) | The number of packets received from the interface having metadata with an invalid length | | [`interface-sanitized`](#show-stats-packet-processing-received-interface-sanitized) | The number of sanitized packets received from the interface | -| [`interface-standby`](#show-stats-packet-processing-received-interface-standby) | The number of packets received on the interface while in standby mode. | -| [`interface-standby-drop`](#show-stats-packet-processing-received-interface-standby-drop) | The number of packets dropped because the interface is in standby mode. | +| [`interface-standby`](#show-stats-packet-processing-received-interface-standby) | The number of packets received on the device interface while in standby mode. | +| [`interface-standby-drop`](#show-stats-packet-processing-received-interface-standby-drop) | The number of packets dropped because the device interface is in standby mode. | | [`interface-standby-empty-head`](#show-stats-packet-processing-received-interface-standby-empty-head) | The number of empty head packets received from the standby interface. | | [`interface-standby-invalid-chain`](#show-stats-packet-processing-received-interface-standby-invalid-chain) | The number of invalid chain packets received from the standby interface | | [`interface-standby-invalid-metadata-length`](#show-stats-packet-processing-received-interface-standby-invalid-metadata-length) | The number of invalid metadata length packets received from the standby interface | @@ -64718,7 +64980,10 @@ show stats packet-processing received [core ] [port ] [since | [`interface-standby-unhandled-exception`](#show-stats-packet-processing-received-interface-standby-unhandled-exception) | The number of packets received from the standby interface which encountered an unhandled exception | | [`interface-success`](#show-stats-packet-processing-received-interface-success) | The number of packets received from the interface | | [`interface-unhandled-exception`](#show-stats-packet-processing-received-interface-unhandled-exception) | The number of packets received from the interface which encountered an unhandled exception | +| [`mac-filtered-discards`](#show-stats-packet-processing-received-mac-filtered-discards) | The number of packets dropped because the destination MAC address doesn't match the interface. | | [`max-burst`](#show-stats-packet-processing-received-max-burst) | Maximum-Sized Receive Bursts Per Interface | +| [`network-interface-standby`](#show-stats-packet-processing-received-network-interface-standby) | The number of packets received on the network interface while in standby mode. | +| [`network-interface-standby-drop`](#show-stats-packet-processing-received-network-interface-standby-drop) | The number of packets dropped because the network interface is in standby mode. | ## `show stats packet-processing received burst-size` @@ -65000,6 +65265,33 @@ show stats packet-processing received injected-timeout [core ] [port ] [port ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| core | The core number for which this metric was generated (comma-separated list) | +| force | Skip confirmation prompt. Only required when targeting all routers | +| node | The name of the node generating this metric | +| port | The device interface for which this metric was generated (comma-separated list) | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + ## `show stats packet-processing received interface-empty-head` The number of empty head packets received from the interface @@ -65110,7 +65402,7 @@ show stats packet-processing received interface-sanitized [core ] [port

] [port | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | +## `show stats packet-processing received mac-filtered-discards` + +The number of packets dropped because the destination MAC address doesn't match the interface. + +#### Usage + +``` +show stats packet-processing received mac-filtered-discards [core ] [port ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| core | The core number for which this metric was generated (comma-separated list) | +| force | Skip confirmation prompt. Only required when targeting all routers | +| node | The name of the node generating this metric | +| port | The device interface for which this metric was generated (comma-separated list) | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + ## `show stats packet-processing received max-burst` Maximum-Sized Receive Bursts Per Interface @@ -65467,14 +65786,14 @@ show stats packet-processing received max-burst transition-to [core ] [por | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats packet-processing sent` +## `show stats packet-processing received network-interface-standby` -Statistics for 'sent' +The number of packets received on the network interface while in standby mode. #### Usage ``` -show stats packet-processing sent [core ] [port ] [since ] [force] [router ] [node ] [] +show stats packet-processing received network-interface-standby [core ] [port ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -65494,28 +65813,14 @@ show stats packet-processing sent [core ] [port ] [since ] [f | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -##### Subcommands - -| command | description | -| ------- | ----------- | -| [`interface-failure`](#show-stats-packet-processing-sent-interface-failure) | The number of packets failed to be transmitted on the interface | -| [`interface-retry`](#show-stats-packet-processing-sent-interface-retry) | The number of packet send retry attempts on this interface | -| [`interface-standby`](#show-stats-packet-processing-sent-interface-standby) | The number of packets transmitted while interface is in standby mode | -| [`interface-standby-drop`](#show-stats-packet-processing-sent-interface-standby-drop) | The number of packets not transmitted because the interface is in standby mode | -| [`interface-success`](#show-stats-packet-processing-sent-interface-success) | The number of packets transmitted out this interface | -| [`interface-unconfigured-drop`](#show-stats-packet-processing-sent-interface-unconfigured-drop) | The number of packets received and dropped because the interface has not been configured. | -| [`to-wire-empty-head`](#show-stats-packet-processing-sent-to-wire-empty-head) | The number of empty head packets destined to wire | -| [`to-wire-invalid-chain`](#show-stats-packet-processing-sent-to-wire-invalid-chain) | The number of invalid chain packets destined to wire | -| [`to-wire-sanitized`](#show-stats-packet-processing-sent-to-wire-sanitized) | The number of sanitized packets destined to wire | - -## `show stats packet-processing sent interface-failure` +## `show stats packet-processing received network-interface-standby-drop` -The number of packets failed to be transmitted on the interface +The number of packets dropped because the network interface is in standby mode. #### Usage ``` -show stats packet-processing sent interface-failure [core ] [port ] [since ] [force] [router ] [node ] [] +show stats packet-processing received network-interface-standby-drop [core ] [port ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -65535,14 +65840,14 @@ show stats packet-processing sent interface-failure [core ] [port ] | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats packet-processing sent interface-retry` +## `show stats packet-processing sent` -The number of packet send retry attempts on this interface +Statistics for 'sent' #### Usage ``` -show stats packet-processing sent interface-retry [core ] [port ] [since ] [force] [router ] [node ] [] +show stats packet-processing sent [core ] [port ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -65562,14 +65867,31 @@ show stats packet-processing sent interface-retry [core ] [port ] [s | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats packet-processing sent interface-standby` +##### Subcommands -The number of packets transmitted while interface is in standby mode +| command | description | +| ------- | ----------- | +| [`interface-failure`](#show-stats-packet-processing-sent-interface-failure) | The number of packets failed to be transmitted on the interface | +| [`interface-retry`](#show-stats-packet-processing-sent-interface-retry) | The number of packet send retry attempts on this interface | +| [`interface-standby`](#show-stats-packet-processing-sent-interface-standby) | The number of packets transmitted while device interface is in standby mode | +| [`interface-standby-drop`](#show-stats-packet-processing-sent-interface-standby-drop) | The number of packets not transmitted because the device interface is in standby mode | +| [`interface-success`](#show-stats-packet-processing-sent-interface-success) | The number of packets transmitted out this interface | +| [`interface-unconfigured-drop`](#show-stats-packet-processing-sent-interface-unconfigured-drop) | The number of packets received and dropped because the interface has not been configured. | +| [`network-interface-standby`](#show-stats-packet-processing-sent-network-interface-standby) | The number of packets transmitted while network interface is in standby mode | +| [`network-interface-standby-drop`](#show-stats-packet-processing-sent-network-interface-standby-drop) | The number of packets not transmitted because the network interface is in standby mode | +| [`network-interface-unconfigured-drop`](#show-stats-packet-processing-sent-network-interface-unconfigured-drop) | The number of packets received and dropped because the network interface has not been configured. | +| [`to-wire-empty-head`](#show-stats-packet-processing-sent-to-wire-empty-head) | The number of empty head packets destined to wire | +| [`to-wire-invalid-chain`](#show-stats-packet-processing-sent-to-wire-invalid-chain) | The number of invalid chain packets destined to wire | +| [`to-wire-sanitized`](#show-stats-packet-processing-sent-to-wire-sanitized) | The number of sanitized packets destined to wire | + +## `show stats packet-processing sent interface-failure` + +The number of packets failed to be transmitted on the interface #### Usage ``` -show stats packet-processing sent interface-standby [core ] [port ] [since ] [force] [router ] [node ] [] +show stats packet-processing sent interface-failure [core ] [port ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -65589,14 +65911,14 @@ show stats packet-processing sent interface-standby [core ] [port ] | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats packet-processing sent interface-standby-drop` +## `show stats packet-processing sent interface-retry` -The number of packets not transmitted because the interface is in standby mode +The number of packet send retry attempts on this interface #### Usage ``` -show stats packet-processing sent interface-standby-drop [core ] [port ] [since ] [force] [router ] [node ] [] +show stats packet-processing sent interface-retry [core ] [port ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -65616,14 +65938,14 @@ show stats packet-processing sent interface-standby-drop [core ] [port ] [port ] [since ] [force] [router ] [node ] [] +show stats packet-processing sent interface-standby [core ] [port ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -65643,14 +65965,14 @@ show stats packet-processing sent interface-success [core ] [port ] | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats packet-processing sent interface-unconfigured-drop` +## `show stats packet-processing sent interface-standby-drop` -The number of packets received and dropped because the interface has not been configured. +The number of packets not transmitted because the device interface is in standby mode #### Usage ``` -show stats packet-processing sent interface-unconfigured-drop [core ] [port ] [since ] [force] [router ] [node ] [] +show stats packet-processing sent interface-standby-drop [core ] [port ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -65670,14 +65992,14 @@ show stats packet-processing sent interface-unconfigured-drop [core ] [por | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats packet-processing sent to-wire-empty-head` +## `show stats packet-processing sent interface-success` -The number of empty head packets destined to wire +The number of packets transmitted out this interface #### Usage ``` -show stats packet-processing sent to-wire-empty-head [core ] [port ] [since ] [force] [router ] [node ] [] +show stats packet-processing sent interface-success [core ] [port ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -65697,14 +66019,14 @@ show stats packet-processing sent to-wire-empty-head [core ] [port ] | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats packet-processing sent to-wire-invalid-chain` +## `show stats packet-processing sent interface-unconfigured-drop` -The number of invalid chain packets destined to wire +The number of packets received and dropped because the interface has not been configured. #### Usage ``` -show stats packet-processing sent to-wire-invalid-chain [core ] [port ] [since ] [force] [router ] [node ] [] +show stats packet-processing sent interface-unconfigured-drop [core ] [port ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -65724,14 +66046,14 @@ show stats packet-processing sent to-wire-invalid-chain [core ] [port ] [port ] [since ] [force] [router ] [node ] [] +show stats packet-processing sent network-interface-standby [core ] [port ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -65751,23 +66073,24 @@ show stats packet-processing sent to-wire-sanitized [core ] [port ] | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree` +## `show stats packet-processing sent network-interface-standby-drop` -Metrics tracking PathTree server and client behavior +The number of packets not transmitted because the network interface is in standby mode #### Usage ``` -show stats path-tree [process ] [since ] [force] [router ] [node ] [] +show stats packet-processing sent network-interface-standby-drop [core ] [port ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | +| core | The core number for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| process | The name of the process generating this metric (comma-separated list) | +| port | The device interface for which this metric was generated (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | @@ -65777,30 +66100,24 @@ show stats path-tree [process ] [since ] [force] [router ] [since ] [force] [router ] [node ] [] +show stats packet-processing sent network-interface-unconfigured-drop [core ] [port ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | +| core | The core number for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| process | The name of the process generating this metric (comma-separated list) | +| port | The device interface for which this metric was generated (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | @@ -65810,31 +66127,24 @@ show stats path-tree client [process ] [since ] [force] [router | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -##### Subcommands - -| command | description | -| ------- | ----------- | -| [`received`](#show-stats-path-tree-client-received) | Statistics for 'received' | -| [`sent`](#show-stats-path-tree-client-sent) | Statistics for 'sent' | -| [`transactions`](#show-stats-path-tree-client-transactions) | Statistics for 'transactions' | - -## `show stats path-tree client received` +## `show stats packet-processing sent to-wire-empty-head` -Statistics for 'received' +The number of empty head packets destined to wire #### Usage ``` -show stats path-tree client received [process ] [since ] [force] [router ] [node ] [] +show stats packet-processing sent to-wire-empty-head [core ] [port ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | +| core | The core number for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| process | The name of the process generating this metric (comma-separated list) | +| port | The device interface for which this metric was generated (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | @@ -65844,31 +66154,24 @@ show stats path-tree client received [process ] [since ] [force] | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -##### Subcommands - -| command | description | -| ------- | ----------- | -| [`notifications`](#show-stats-path-tree-client-received-notifications) | Statistics for 'notifications' | -| [`responses`](#show-stats-path-tree-client-received-responses) | Statistics for 'responses' | -| [`unknown`](#show-stats-path-tree-client-received-unknown) | Statistics for 'unknown' | - -## `show stats path-tree client received notifications` +## `show stats packet-processing sent to-wire-invalid-chain` -Statistics for 'notifications' +The number of invalid chain packets destined to wire #### Usage ``` -show stats path-tree client received notifications [process ] [since ] [force] [router ] [node ] [] +show stats packet-processing sent to-wire-invalid-chain [core ] [port ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | +| core | The core number for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| process | The name of the process generating this metric (comma-separated list) | +| port | The device interface for which this metric was generated (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | @@ -65878,31 +66181,24 @@ show stats path-tree client received notifications [process ] [since ] [since ] [force] [router ] [node ] [] +show stats packet-processing sent to-wire-sanitized [core ] [port ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | +| core | The core number for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| process | The name of the process generating this metric (comma-separated list) | +| port | The device interface for which this metric was generated (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | @@ -65912,14 +66208,14 @@ show stats path-tree client received notifications duration [process ] | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree client received notifications error` +## `show stats path-tree` -The number of invalid or malformed notification messages received (count) +Metrics tracking PathTree server and client behavior #### Usage ``` -show stats path-tree client received notifications error [process ] [since ] [force] [router ] [node ] [] +show stats path-tree [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -65938,40 +66234,21 @@ show stats path-tree client received notifications error [process ] [si | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree client received notifications total` - -The number of notification messages received successfully (count) - -#### Usage - -``` -show stats path-tree client received notifications total [process ] [since ] [force] [router ] [node ] [] -``` - -##### Keyword Arguments - -| name | description | -| ---- | ----------- | -| force | Skip confirmation prompt. Only required when targeting all routers | -| node | The name of the node generating this metric | -| process | The name of the process generating this metric (comma-separated list) | -| router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | - -##### Positional Arguments +##### Subcommands -| name | description | -| ---- | ----------- | -| verbosity | detail \| summary \| debug (default: detail) | +| command | description | +| ------- | ----------- | +| [`client`](#show-stats-path-tree-client) | Statistics for 'client' | +| [`server`](#show-stats-path-tree-server) | Statistics for 'server' | -## `show stats path-tree client received responses` +## `show stats path-tree client` -Statistics for 'responses' +Statistics for 'client' #### Usage ``` -show stats path-tree client received responses [process ] [since ] [force] [router ] [node ] [] +show stats path-tree client [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -65994,18 +66271,18 @@ show stats path-tree client received responses [process ] [since ] [since ] [force] [router ] [node ] [] +show stats path-tree client received [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66024,40 +66301,22 @@ show stats path-tree client received responses duration [process ] [sin | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree client received responses error` - -The number of invalid or malformed transaction response messages received (count) - -#### Usage - -``` -show stats path-tree client received responses error [process ] [since ] [force] [router ] [node ] [] -``` - -##### Keyword Arguments - -| name | description | -| ---- | ----------- | -| force | Skip confirmation prompt. Only required when targeting all routers | -| node | The name of the node generating this metric | -| process | The name of the process generating this metric (comma-separated list) | -| router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | - -##### Positional Arguments +##### Subcommands -| name | description | -| ---- | ----------- | -| verbosity | detail \| summary \| debug (default: detail) | +| command | description | +| ------- | ----------- | +| [`notifications`](#show-stats-path-tree-client-received-notifications) | Statistics for 'notifications' | +| [`responses`](#show-stats-path-tree-client-received-responses) | Statistics for 'responses' | +| [`unknown`](#show-stats-path-tree-client-received-unknown) | Statistics for 'unknown' | -## `show stats path-tree client received responses total` +## `show stats path-tree client received notifications` -The number of transaction response messages received successfully (count) +Statistics for 'notifications' #### Usage ``` -show stats path-tree client received responses total [process ] [since ] [force] [router ] [node ] [] +show stats path-tree client received notifications [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66076,14 +66335,22 @@ show stats path-tree client received responses total [process ] [since | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree client received unknown` +##### Subcommands -Statistics for 'unknown' +| command | description | +| ------- | ----------- | +| [`duration`](#show-stats-path-tree-client-received-notifications-duration) | Average time to process Notifications on the client (microseconds) | +| [`error`](#show-stats-path-tree-client-received-notifications-error) | The number of invalid or malformed notification messages received (count) | +| [`total`](#show-stats-path-tree-client-received-notifications-total) | The number of notification messages received successfully (count) | + +## `show stats path-tree client received notifications duration` + +Average time to process Notifications on the client (microseconds) #### Usage ``` -show stats path-tree client received unknown [process ] [since ] [force] [router ] [node ] [] +show stats path-tree client received notifications duration [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66102,20 +66369,14 @@ show stats path-tree client received unknown [process ] [since ] | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -##### Subcommands - -| command | description | -| ------- | ----------- | -| [`total`](#show-stats-path-tree-client-received-unknown-total) | The number of unknown message types received (count) | - -## `show stats path-tree client received unknown total` +## `show stats path-tree client received notifications error` -The number of unknown message types received (count) +The number of invalid or malformed notification messages received (count) #### Usage ``` -show stats path-tree client received unknown total [process ] [since ] [force] [router ] [node ] [] +show stats path-tree client received notifications error [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66134,14 +66395,14 @@ show stats path-tree client received unknown total [process ] [since ] [since ] [force] [router ] [node ] [] +show stats path-tree client received notifications total [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66160,20 +66421,14 @@ show stats path-tree client sent [process ] [since ] [force] [ro | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -##### Subcommands - -| command | description | -| ------- | ----------- | -| [`requests`](#show-stats-path-tree-client-sent-requests) | Statistics for 'requests' | - -## `show stats path-tree client sent requests` +## `show stats path-tree client received responses` -Statistics for 'requests' +Statistics for 'responses' #### Usage ``` -show stats path-tree client sent requests [process ] [since ] [force] [router ] [node ] [] +show stats path-tree client received responses [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66196,17 +66451,18 @@ show stats path-tree client sent requests [process ] [since ] [f | command | description | | ------- | ----------- | -| [`error`](#show-stats-path-tree-client-sent-requests-error) | The number of transaction request messages that could not be sent (count) | -| [`total`](#show-stats-path-tree-client-sent-requests-total) | The number of transaction request messages sent successfully (count) | +| [`duration`](#show-stats-path-tree-client-received-responses-duration) | Average time to process transaction responses on the client (microseconds) | +| [`error`](#show-stats-path-tree-client-received-responses-error) | The number of invalid or malformed transaction response messages received (count) | +| [`total`](#show-stats-path-tree-client-received-responses-total) | The number of transaction response messages received successfully (count) | -## `show stats path-tree client sent requests error` +## `show stats path-tree client received responses duration` -The number of transaction request messages that could not be sent (count) +Average time to process transaction responses on the client (microseconds) #### Usage ``` -show stats path-tree client sent requests error [process ] [since ] [force] [router ] [node ] [] +show stats path-tree client received responses duration [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66225,14 +66481,14 @@ show stats path-tree client sent requests error [process ] [since ] [since ] [force] [router ] [node ] [] +show stats path-tree client received responses error [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66251,14 +66507,14 @@ show stats path-tree client sent requests total [process ] [since ] [since ] [force] [router ] [node ] [] +show stats path-tree client received responses total [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66277,20 +66533,14 @@ show stats path-tree client transactions [process ] [since ] [fo | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -##### Subcommands - -| command | description | -| ------- | ----------- | -| [`server-latency`](#show-stats-path-tree-client-transactions-server-latency) | Average latency for the server to process/respond-to transactions (microseconds) | - -## `show stats path-tree client transactions server-latency` +## `show stats path-tree client received unknown` -Average latency for the server to process/respond-to transactions (microseconds) +Statistics for 'unknown' #### Usage ``` -show stats path-tree client transactions server-latency [process ] [since ] [force] [router ] [node ] [] +show stats path-tree client received unknown [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66309,14 +66559,20 @@ show stats path-tree client transactions server-latency [process ] [sin | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server` +##### Subcommands -Statistics for 'server' +| command | description | +| ------- | ----------- | +| [`total`](#show-stats-path-tree-client-received-unknown-total) | The number of unknown message types received (count) | + +## `show stats path-tree client received unknown total` + +The number of unknown message types received (count) #### Usage ``` -show stats path-tree server [process ] [since ] [force] [router ] [node ] [] +show stats path-tree client received unknown total [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66335,22 +66591,14 @@ show stats path-tree server [process ] [since ] [force] [router | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -##### Subcommands - -| command | description | -| ------- | ----------- | -| [`received`](#show-stats-path-tree-server-received) | Statistics for 'received' | -| [`sent`](#show-stats-path-tree-server-sent) | Statistics for 'sent' | -| [`transactions`](#show-stats-path-tree-server-transactions) | Statistics for 'transactions' | - -## `show stats path-tree server received` +## `show stats path-tree client sent` -Statistics for 'received' +Statistics for 'sent' #### Usage ``` -show stats path-tree server received [process ] [since ] [force] [router ] [node ] [] +show stats path-tree client sent [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66373,16 +66621,16 @@ show stats path-tree server received [process ] [since ] [force] | command | description | | ------- | ----------- | -| [`requests`](#show-stats-path-tree-server-received-requests) | Statistics for 'requests' | +| [`requests`](#show-stats-path-tree-client-sent-requests) | Statistics for 'requests' | -## `show stats path-tree server received requests` +## `show stats path-tree client sent requests` Statistics for 'requests' #### Usage ``` -show stats path-tree server received requests [process ] [since ] [force] [router ] [node ] [] +show stats path-tree client sent requests [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66405,26 +66653,23 @@ show stats path-tree server received requests [process ] [since | command | description | | ------- | ----------- | -| [`average`](#show-stats-path-tree-server-received-requests-average) | The number of transaction request messages received successfully (count) | -| [`error`](#show-stats-path-tree-server-received-requests-error) | The number of invalid or malformed transaction request messages received (count) | -| [`ignored`](#show-stats-path-tree-server-received-requests-ignored) | The number of transaction request messages received but were ignored due to invalid session state (count) | -| [`total`](#show-stats-path-tree-server-received-requests-total) | The number of transaction request messages received successfully (count) | +| [`error`](#show-stats-path-tree-client-sent-requests-error) | The number of transaction request messages that could not be sent (count) | +| [`total`](#show-stats-path-tree-client-sent-requests-total) | The number of transaction request messages sent successfully (count) | -## `show stats path-tree server received requests average` +## `show stats path-tree client sent requests error` -The number of transaction request messages received successfully (count) +The number of transaction request messages that could not be sent (count) #### Usage ``` -show stats path-tree server received requests average [process ] [client ] [since ] [force] [router ] [node ] [] +show stats path-tree client sent requests error [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | -| client | The name of the client within a process generating this metric (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | process | The name of the process generating this metric (comma-separated list) | @@ -66437,14 +66682,14 @@ show stats path-tree server received requests average [process ] [clien | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server received requests error` +## `show stats path-tree client sent requests total` -The number of invalid or malformed transaction request messages received (count) +The number of transaction request messages sent successfully (count) #### Usage ``` -show stats path-tree server received requests error [process ] [since ] [force] [router ] [node ] [] +show stats path-tree client sent requests total [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66463,14 +66708,14 @@ show stats path-tree server received requests error [process ] [since < | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server received requests ignored` +## `show stats path-tree client transactions` -The number of transaction request messages received but were ignored due to invalid session state (count) +Statistics for 'transactions' #### Usage ``` -show stats path-tree server received requests ignored [process ] [since ] [force] [router ] [node ] [] +show stats path-tree client transactions [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66489,14 +66734,20 @@ show stats path-tree server received requests ignored [process ] [since | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server received requests total` +##### Subcommands -The number of transaction request messages received successfully (count) +| command | description | +| ------- | ----------- | +| [`server-latency`](#show-stats-path-tree-client-transactions-server-latency) | Average latency for the server to process/respond-to transactions (microseconds) | + +## `show stats path-tree client transactions server-latency` + +Average latency for the server to process/respond-to transactions (microseconds) #### Usage ``` -show stats path-tree server received requests total [process ] [since ] [force] [router ] [node ] [] +show stats path-tree client transactions server-latency [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66515,14 +66766,14 @@ show stats path-tree server received requests total [process ] [since < | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server sent` +## `show stats path-tree server` -Statistics for 'sent' +Statistics for 'server' #### Usage ``` -show stats path-tree server sent [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66545,16 +66796,18 @@ show stats path-tree server sent [process ] [since ] [force] [ro | command | description | | ------- | ----------- | -| [`responses`](#show-stats-path-tree-server-sent-responses) | Statistics for 'responses' | +| [`received`](#show-stats-path-tree-server-received) | Statistics for 'received' | +| [`sent`](#show-stats-path-tree-server-sent) | Statistics for 'sent' | +| [`transactions`](#show-stats-path-tree-server-transactions) | Statistics for 'transactions' | -## `show stats path-tree server sent responses` +## `show stats path-tree server received` -Statistics for 'responses' +Statistics for 'received' #### Usage ``` -show stats path-tree server sent responses [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server received [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66577,17 +66830,16 @@ show stats path-tree server sent responses [process ] [since ] [ | command | description | | ------- | ----------- | -| [`error`](#show-stats-path-tree-server-sent-responses-error) | The number of transaction response messages that could not be sent (count) | -| [`total`](#show-stats-path-tree-server-sent-responses-total) | The number of transaction response messages sent successfully (count) | +| [`requests`](#show-stats-path-tree-server-received-requests) | Statistics for 'requests' | -## `show stats path-tree server sent responses error` +## `show stats path-tree server received requests` -The number of transaction response messages that could not be sent (count) +Statistics for 'requests' #### Usage ``` -show stats path-tree server sent responses error [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server received requests [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66606,46 +66858,30 @@ show stats path-tree server sent responses error [process ] [since ] [since ] [force] [router ] [node ] [] -``` - -##### Keyword Arguments - -| name | description | -| ---- | ----------- | -| force | Skip confirmation prompt. Only required when targeting all routers | -| node | The name of the node generating this metric | -| process | The name of the process generating this metric (comma-separated list) | -| router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | - -##### Positional Arguments +##### Subcommands -| name | description | -| ---- | ----------- | -| verbosity | detail \| summary \| debug (default: detail) | +| command | description | +| ------- | ----------- | +| [`average`](#show-stats-path-tree-server-received-requests-average) | The number of transaction request messages received successfully (count) | +| [`error`](#show-stats-path-tree-server-received-requests-error) | The number of invalid or malformed transaction request messages received (count) | +| [`ignored`](#show-stats-path-tree-server-received-requests-ignored) | The number of transaction request messages received but were ignored due to invalid session state (count) | +| [`total`](#show-stats-path-tree-server-received-requests-total) | The number of transaction request messages received successfully (count) | -## `show stats path-tree server transactions` +## `show stats path-tree server received requests average` -Statistics for 'transactions' +The number of transaction request messages received successfully (count) #### Usage ``` -show stats path-tree server transactions [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server received requests average [process ] [client ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | +| client | The name of the client within a process generating this metric (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | process | The name of the process generating this metric (comma-separated list) | @@ -66658,28 +66894,14 @@ show stats path-tree server transactions [process ] [since ] [fo | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -##### Subcommands - -| command | description | -| ------- | ----------- | -| [`connect`](#show-stats-path-tree-server-transactions-connect) | Statistics for 'connect' | -| [`disconnect`](#show-stats-path-tree-server-transactions-disconnect) | Statistics for 'disconnect' | -| [`list`](#show-stats-path-tree-server-transactions-list) | Statistics for 'list' | -| [`ping`](#show-stats-path-tree-server-transactions-ping) | Statistics for 'ping' | -| [`publish`](#show-stats-path-tree-server-transactions-publish) | Statistics for 'publish' | -| [`read`](#show-stats-path-tree-server-transactions-read) | Statistics for 'read' | -| [`remove`](#show-stats-path-tree-server-transactions-remove) | Statistics for 'remove' | -| [`unsubscribe`](#show-stats-path-tree-server-transactions-unsubscribe) | Statistics for 'unsubscribe' | -| [`update`](#show-stats-path-tree-server-transactions-update) | Statistics for 'update' | - -## `show stats path-tree server transactions connect` +## `show stats path-tree server received requests error` -Statistics for 'connect' +The number of invalid or malformed transaction request messages received (count) #### Usage ``` -show stats path-tree server transactions connect [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server received requests error [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66698,22 +66920,14 @@ show stats path-tree server transactions connect [process ] [since ] [since ] [force] [router ] [node ] [] +show stats path-tree server received requests ignored [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66732,14 +66946,14 @@ show stats path-tree server transactions connect duration [process ] [s | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions connect error` +## `show stats path-tree server received requests total` -The number of Connect transactions that could not be processed successfully (count) +The number of transaction request messages received successfully (count) #### Usage ``` -show stats path-tree server transactions connect error [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server received requests total [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66758,14 +66972,14 @@ show stats path-tree server transactions connect error [process ] [sinc | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions connect processed` +## `show stats path-tree server sent` -The number of successfully processed Connect transactions (count) +Statistics for 'sent' #### Usage ``` -show stats path-tree server transactions connect processed [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server sent [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66784,14 +66998,20 @@ show stats path-tree server transactions connect processed [process ] [ | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions disconnect` +##### Subcommands -Statistics for 'disconnect' +| command | description | +| ------- | ----------- | +| [`responses`](#show-stats-path-tree-server-sent-responses) | Statistics for 'responses' | + +## `show stats path-tree server sent responses` + +Statistics for 'responses' #### Usage ``` -show stats path-tree server transactions disconnect [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server sent responses [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66814,18 +67034,17 @@ show stats path-tree server transactions disconnect [process ] [since < | command | description | | ------- | ----------- | -| [`duration`](#show-stats-path-tree-server-transactions-disconnect-duration) | Average time to process/respond-to Disconnect transactions (microseconds) | -| [`error`](#show-stats-path-tree-server-transactions-disconnect-error) | The number of Disconnect transactions that could not be processed successfully (count) | -| [`processed`](#show-stats-path-tree-server-transactions-disconnect-processed) | The number of successfully processed Disconnect transactions (count) | +| [`error`](#show-stats-path-tree-server-sent-responses-error) | The number of transaction response messages that could not be sent (count) | +| [`total`](#show-stats-path-tree-server-sent-responses-total) | The number of transaction response messages sent successfully (count) | -## `show stats path-tree server transactions disconnect duration` +## `show stats path-tree server sent responses error` -Average time to process/respond-to Disconnect transactions (microseconds) +The number of transaction response messages that could not be sent (count) #### Usage ``` -show stats path-tree server transactions disconnect duration [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server sent responses error [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66844,14 +67063,14 @@ show stats path-tree server transactions disconnect duration [process ] | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions disconnect error` +## `show stats path-tree server sent responses total` -The number of Disconnect transactions that could not be processed successfully (count) +The number of transaction response messages sent successfully (count) #### Usage ``` -show stats path-tree server transactions disconnect error [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server sent responses total [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66870,14 +67089,14 @@ show stats path-tree server transactions disconnect error [process ] [s | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions disconnect processed` +## `show stats path-tree server transactions` -The number of successfully processed Disconnect transactions (count) +Statistics for 'transactions' #### Usage ``` -show stats path-tree server transactions disconnect processed [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66896,14 +67115,28 @@ show stats path-tree server transactions disconnect processed [process | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions list` +##### Subcommands -Statistics for 'list' +| command | description | +| ------- | ----------- | +| [`connect`](#show-stats-path-tree-server-transactions-connect) | Statistics for 'connect' | +| [`disconnect`](#show-stats-path-tree-server-transactions-disconnect) | Statistics for 'disconnect' | +| [`list`](#show-stats-path-tree-server-transactions-list) | Statistics for 'list' | +| [`ping`](#show-stats-path-tree-server-transactions-ping) | Statistics for 'ping' | +| [`publish`](#show-stats-path-tree-server-transactions-publish) | Statistics for 'publish' | +| [`read`](#show-stats-path-tree-server-transactions-read) | Statistics for 'read' | +| [`remove`](#show-stats-path-tree-server-transactions-remove) | Statistics for 'remove' | +| [`unsubscribe`](#show-stats-path-tree-server-transactions-unsubscribe) | Statistics for 'unsubscribe' | +| [`update`](#show-stats-path-tree-server-transactions-update) | Statistics for 'update' | + +## `show stats path-tree server transactions connect` + +Statistics for 'connect' #### Usage ``` -show stats path-tree server transactions list [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions connect [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66926,18 +67159,18 @@ show stats path-tree server transactions list [process ] [since | command | description | | ------- | ----------- | -| [`duration`](#show-stats-path-tree-server-transactions-list-duration) | Average time to process/respond-to List transactions (microseconds) | -| [`error`](#show-stats-path-tree-server-transactions-list-error) | The number of List transactions that could not be processed successfully (count) | -| [`processed`](#show-stats-path-tree-server-transactions-list-processed) | The number of successfully processed List transactions (count) | +| [`duration`](#show-stats-path-tree-server-transactions-connect-duration) | Average time to process/respond-to Connect transactions (microseconds) | +| [`error`](#show-stats-path-tree-server-transactions-connect-error) | The number of Connect transactions that could not be processed successfully (count) | +| [`processed`](#show-stats-path-tree-server-transactions-connect-processed) | The number of successfully processed Connect transactions (count) | -## `show stats path-tree server transactions list duration` +## `show stats path-tree server transactions connect duration` -Average time to process/respond-to List transactions (microseconds) +Average time to process/respond-to Connect transactions (microseconds) #### Usage ``` -show stats path-tree server transactions list duration [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions connect duration [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66956,14 +67189,14 @@ show stats path-tree server transactions list duration [process ] [sinc | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions list error` +## `show stats path-tree server transactions connect error` -The number of List transactions that could not be processed successfully (count) +The number of Connect transactions that could not be processed successfully (count) #### Usage ``` -show stats path-tree server transactions list error [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions connect error [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -66982,14 +67215,14 @@ show stats path-tree server transactions list error [process ] [since < | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions list processed` +## `show stats path-tree server transactions connect processed` -The number of successfully processed List transactions (count) +The number of successfully processed Connect transactions (count) #### Usage ``` -show stats path-tree server transactions list processed [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions connect processed [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67008,14 +67241,14 @@ show stats path-tree server transactions list processed [process ] [sin | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions ping` +## `show stats path-tree server transactions disconnect` -Statistics for 'ping' +Statistics for 'disconnect' #### Usage ``` -show stats path-tree server transactions ping [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions disconnect [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67038,18 +67271,18 @@ show stats path-tree server transactions ping [process ] [since | command | description | | ------- | ----------- | -| [`duration`](#show-stats-path-tree-server-transactions-ping-duration) | Average time to process/respond-to Ping transactions (microseconds) | -| [`error`](#show-stats-path-tree-server-transactions-ping-error) | The number of Ping transactions that could not be processed successfully (count) | -| [`processed`](#show-stats-path-tree-server-transactions-ping-processed) | The number of successfully processed Ping transactions (count) | +| [`duration`](#show-stats-path-tree-server-transactions-disconnect-duration) | Average time to process/respond-to Disconnect transactions (microseconds) | +| [`error`](#show-stats-path-tree-server-transactions-disconnect-error) | The number of Disconnect transactions that could not be processed successfully (count) | +| [`processed`](#show-stats-path-tree-server-transactions-disconnect-processed) | The number of successfully processed Disconnect transactions (count) | -## `show stats path-tree server transactions ping duration` +## `show stats path-tree server transactions disconnect duration` -Average time to process/respond-to Ping transactions (microseconds) +Average time to process/respond-to Disconnect transactions (microseconds) #### Usage ``` -show stats path-tree server transactions ping duration [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions disconnect duration [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67068,14 +67301,14 @@ show stats path-tree server transactions ping duration [process ] [sinc | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions ping error` +## `show stats path-tree server transactions disconnect error` -The number of Ping transactions that could not be processed successfully (count) +The number of Disconnect transactions that could not be processed successfully (count) #### Usage ``` -show stats path-tree server transactions ping error [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions disconnect error [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67094,14 +67327,14 @@ show stats path-tree server transactions ping error [process ] [since < | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions ping processed` +## `show stats path-tree server transactions disconnect processed` -The number of successfully processed Ping transactions (count) +The number of successfully processed Disconnect transactions (count) #### Usage ``` -show stats path-tree server transactions ping processed [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions disconnect processed [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67120,14 +67353,14 @@ show stats path-tree server transactions ping processed [process ] [sin | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions publish` +## `show stats path-tree server transactions list` -Statistics for 'publish' +Statistics for 'list' #### Usage ``` -show stats path-tree server transactions publish [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions list [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67150,18 +67383,18 @@ show stats path-tree server transactions publish [process ] [since ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions list duration [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67180,14 +67413,14 @@ show stats path-tree server transactions publish duration [process ] [s | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions publish error` +## `show stats path-tree server transactions list error` -The number of Publish transactions that could not be processed successfully (count) +The number of List transactions that could not be processed successfully (count) #### Usage ``` -show stats path-tree server transactions publish error [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions list error [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67206,14 +67439,14 @@ show stats path-tree server transactions publish error [process ] [sinc | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions publish processed` +## `show stats path-tree server transactions list processed` -The number of successfully processed Publish transactions (count) +The number of successfully processed List transactions (count) #### Usage ``` -show stats path-tree server transactions publish processed [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions list processed [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67232,14 +67465,14 @@ show stats path-tree server transactions publish processed [process ] [ | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions read` +## `show stats path-tree server transactions ping` -Statistics for 'read' +Statistics for 'ping' #### Usage ``` -show stats path-tree server transactions read [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions ping [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67262,18 +67495,18 @@ show stats path-tree server transactions read [process ] [since | command | description | | ------- | ----------- | -| [`duration`](#show-stats-path-tree-server-transactions-read-duration) | Average time to process/respond-to Read transactions (microseconds) | -| [`error`](#show-stats-path-tree-server-transactions-read-error) | The number of Read transactions that could not be processed successfully (count) | -| [`processed`](#show-stats-path-tree-server-transactions-read-processed) | The number of successfully processed Read transactions (count) | +| [`duration`](#show-stats-path-tree-server-transactions-ping-duration) | Average time to process/respond-to Ping transactions (microseconds) | +| [`error`](#show-stats-path-tree-server-transactions-ping-error) | The number of Ping transactions that could not be processed successfully (count) | +| [`processed`](#show-stats-path-tree-server-transactions-ping-processed) | The number of successfully processed Ping transactions (count) | -## `show stats path-tree server transactions read duration` +## `show stats path-tree server transactions ping duration` -Average time to process/respond-to Read transactions (microseconds) +Average time to process/respond-to Ping transactions (microseconds) #### Usage ``` -show stats path-tree server transactions read duration [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions ping duration [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67292,14 +67525,14 @@ show stats path-tree server transactions read duration [process ] [sinc | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions read error` +## `show stats path-tree server transactions ping error` -The number of Read transactions that could not be processed successfully (count) +The number of Ping transactions that could not be processed successfully (count) #### Usage ``` -show stats path-tree server transactions read error [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions ping error [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67318,14 +67551,14 @@ show stats path-tree server transactions read error [process ] [since < | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions read processed` +## `show stats path-tree server transactions ping processed` -The number of successfully processed Read transactions (count) +The number of successfully processed Ping transactions (count) #### Usage ``` -show stats path-tree server transactions read processed [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions ping processed [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67344,14 +67577,14 @@ show stats path-tree server transactions read processed [process ] [sin | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions remove` +## `show stats path-tree server transactions publish` -Statistics for 'remove' +Statistics for 'publish' #### Usage ``` -show stats path-tree server transactions remove [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions publish [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67374,18 +67607,18 @@ show stats path-tree server transactions remove [process ] [since ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions publish duration [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67404,14 +67637,14 @@ show stats path-tree server transactions remove duration [process ] [si | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions remove error` +## `show stats path-tree server transactions publish error` -The number of Remove transactions that could not be processed successfully (count) +The number of Publish transactions that could not be processed successfully (count) #### Usage ``` -show stats path-tree server transactions remove error [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions publish error [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67430,14 +67663,14 @@ show stats path-tree server transactions remove error [process ] [since | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions remove processed` +## `show stats path-tree server transactions publish processed` -The number of successfully processed Remove transactions (count) +The number of successfully processed Publish transactions (count) #### Usage ``` -show stats path-tree server transactions remove processed [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions publish processed [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67456,14 +67689,14 @@ show stats path-tree server transactions remove processed [process ] [s | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions unsubscribe` +## `show stats path-tree server transactions read` -Statistics for 'unsubscribe' +Statistics for 'read' #### Usage ``` -show stats path-tree server transactions unsubscribe [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions read [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67486,18 +67719,18 @@ show stats path-tree server transactions unsubscribe [process ] [since | command | description | | ------- | ----------- | -| [`duration`](#show-stats-path-tree-server-transactions-unsubscribe-duration) | Average time to process/respond-to Unsubscribe transactions (microseconds) | -| [`error`](#show-stats-path-tree-server-transactions-unsubscribe-error) | The number of Unsubscribe transactions that could not be processed successfully (count) | -| [`processed`](#show-stats-path-tree-server-transactions-unsubscribe-processed) | The number of successfully processed Unsubscribe transactions (count) | +| [`duration`](#show-stats-path-tree-server-transactions-read-duration) | Average time to process/respond-to Read transactions (microseconds) | +| [`error`](#show-stats-path-tree-server-transactions-read-error) | The number of Read transactions that could not be processed successfully (count) | +| [`processed`](#show-stats-path-tree-server-transactions-read-processed) | The number of successfully processed Read transactions (count) | -## `show stats path-tree server transactions unsubscribe duration` +## `show stats path-tree server transactions read duration` -Average time to process/respond-to Unsubscribe transactions (microseconds) +Average time to process/respond-to Read transactions (microseconds) #### Usage ``` -show stats path-tree server transactions unsubscribe duration [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions read duration [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67516,14 +67749,14 @@ show stats path-tree server transactions unsubscribe duration [process | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions unsubscribe error` +## `show stats path-tree server transactions read error` -The number of Unsubscribe transactions that could not be processed successfully (count) +The number of Read transactions that could not be processed successfully (count) #### Usage ``` -show stats path-tree server transactions unsubscribe error [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions read error [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67542,14 +67775,14 @@ show stats path-tree server transactions unsubscribe error [process ] [ | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions unsubscribe processed` +## `show stats path-tree server transactions read processed` -The number of successfully processed Unsubscribe transactions (count) +The number of successfully processed Read transactions (count) #### Usage ``` -show stats path-tree server transactions unsubscribe processed [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions read processed [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67568,14 +67801,14 @@ show stats path-tree server transactions unsubscribe processed [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions remove [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67598,18 +67831,18 @@ show stats path-tree server transactions update [process ] [since ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions remove duration [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67628,14 +67861,14 @@ show stats path-tree server transactions update duration [process ] [si | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions update error` +## `show stats path-tree server transactions remove error` -The number of Update transactions that could not be processed successfully (count) +The number of Remove transactions that could not be processed successfully (count) #### Usage ``` -show stats path-tree server transactions update error [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions remove error [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67654,14 +67887,14 @@ show stats path-tree server transactions update error [process ] [since | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats path-tree server transactions update processed` +## `show stats path-tree server transactions remove processed` -The number of successfully processed Update transactions (count) +The number of successfully processed Remove transactions (count) #### Usage ``` -show stats path-tree server transactions update processed [process ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions remove processed [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -67680,30 +67913,25 @@ show stats path-tree server transactions update processed [process ] [s | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -## `show stats performance-monitoring` +## `show stats path-tree server transactions unsubscribe` -Stats pertaining to SSR peer path performance monitoring +Statistics for 'unsubscribe' #### Usage ``` -show stats performance-monitoring [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions unsubscribe [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | -| device-name | The name of the device port for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| peer-host | The host of the peer generating this metric (comma-separated list) | -| peer-name | The name of the peer generating this metric (comma-separated list) | -| protocol | The protocol for which this metric was generated (comma-separated list) | +| process | The name of the process generating this metric (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | -| traffic-class | The traffic class for which this metric was generated (comma-separated list) | -| vlan | The vlan for which this metrics was generated (comma-separated list) | ##### Positional Arguments @@ -67715,32 +67943,29 @@ show stats performance-monitoring [peer-name ] [peer-host | command | description | | ------- | ----------- | -| [`peer-path`](#show-stats-performance-monitoring-peer-path) | Statistics for 'peer-path' | +| [`duration`](#show-stats-path-tree-server-transactions-unsubscribe-duration) | Average time to process/respond-to Unsubscribe transactions (microseconds) | +| [`error`](#show-stats-path-tree-server-transactions-unsubscribe-error) | The number of Unsubscribe transactions that could not be processed successfully (count) | +| [`processed`](#show-stats-path-tree-server-transactions-unsubscribe-processed) | The number of successfully processed Unsubscribe transactions (count) | -## `show stats performance-monitoring peer-path` +## `show stats path-tree server transactions unsubscribe duration` -Statistics for 'peer-path' +Average time to process/respond-to Unsubscribe transactions (microseconds) #### Usage ``` -show stats performance-monitoring peer-path [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions unsubscribe duration [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | -| device-name | The name of the device port for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| peer-host | The host of the peer generating this metric (comma-separated list) | -| peer-name | The name of the peer generating this metric (comma-separated list) | -| protocol | The protocol for which this metric was generated (comma-separated list) | +| process | The name of the process generating this metric (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | -| traffic-class | The traffic class for which this metric was generated (comma-separated list) | -| vlan | The vlan for which this metrics was generated (comma-separated list) | ##### Positional Arguments @@ -67748,42 +67973,25 @@ show stats performance-monitoring peer-path [peer-name ] [peer-host < | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -##### Subcommands - -| command | description | -| ------- | ----------- | -| [`jitter`](#show-stats-performance-monitoring-peer-path-jitter) | Jitter in milliseconds for the SSR peer path. (in-memory) | -| [`latency`](#show-stats-performance-monitoring-peer-path-latency) | Latency in milliseconds for the SSR peer path. (in-memory) | -| [`loss`](#show-stats-performance-monitoring-peer-path-loss) | Aggregate packet loss percentange for the SSR peer path. (in-memory) | -| [`mos`](#show-stats-performance-monitoring-peer-path-mos) | MOS value calculated for the SSR peer path. (hundreths of a decimal) (in-memory) | -| [`received`](#show-stats-performance-monitoring-peer-path-received) | Statistics for 'received' | -| [`transmit`](#show-stats-performance-monitoring-peer-path-transmit) | Statistics for 'transmit' | -| [`updated`](#show-stats-performance-monitoring-peer-path-updated) | The unix timestamp (seconds) when the peer path's values were last updated. (in-memory) | - -## `show stats performance-monitoring peer-path jitter` +## `show stats path-tree server transactions unsubscribe error` -Jitter in milliseconds for the SSR peer path. (in-memory) +The number of Unsubscribe transactions that could not be processed successfully (count) #### Usage ``` -show stats performance-monitoring peer-path jitter [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions unsubscribe error [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | -| device-name | The name of the device port for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| peer-host | The host of the peer generating this metric (comma-separated list) | -| peer-name | The name of the peer generating this metric (comma-separated list) | -| protocol | The protocol for which this metric was generated (comma-separated list) | +| process | The name of the process generating this metric (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | -| traffic-class | The traffic class for which this metric was generated (comma-separated list) | -| vlan | The vlan for which this metrics was generated (comma-separated list) | ##### Positional Arguments @@ -67791,34 +67999,25 @@ show stats performance-monitoring peer-path jitter [peer-name ] [peer | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -#### Description - -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) - -## `show stats performance-monitoring peer-path latency` +## `show stats path-tree server transactions unsubscribe processed` -Latency in milliseconds for the SSR peer path. (in-memory) +The number of successfully processed Unsubscribe transactions (count) #### Usage ``` -show stats performance-monitoring peer-path latency [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions unsubscribe processed [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | -| device-name | The name of the device port for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| peer-host | The host of the peer generating this metric (comma-separated list) | -| peer-name | The name of the peer generating this metric (comma-separated list) | -| protocol | The protocol for which this metric was generated (comma-separated list) | +| process | The name of the process generating this metric (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | -| traffic-class | The traffic class for which this metric was generated (comma-separated list) | -| vlan | The vlan for which this metrics was generated (comma-separated list) | ##### Positional Arguments @@ -67826,34 +68025,25 @@ show stats performance-monitoring peer-path latency [peer-name ] [pee | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -#### Description - -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) - -## `show stats performance-monitoring peer-path loss` +## `show stats path-tree server transactions update` -Aggregate packet loss percentange for the SSR peer path. (in-memory) +Statistics for 'update' #### Usage ``` -show stats performance-monitoring peer-path loss [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions update [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | -| device-name | The name of the device port for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| peer-host | The host of the peer generating this metric (comma-separated list) | -| peer-name | The name of the peer generating this metric (comma-separated list) | -| protocol | The protocol for which this metric was generated (comma-separated list) | +| process | The name of the process generating this metric (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | -| traffic-class | The traffic class for which this metric was generated (comma-separated list) | -| vlan | The vlan for which this metrics was generated (comma-separated list) | ##### Positional Arguments @@ -67861,34 +68051,33 @@ show stats performance-monitoring peer-path loss [peer-name ] [peer-h | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -#### Description +##### Subcommands -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +| command | description | +| ------- | ----------- | +| [`duration`](#show-stats-path-tree-server-transactions-update-duration) | Average time to process/respond-to Update transactions (microseconds) | +| [`error`](#show-stats-path-tree-server-transactions-update-error) | The number of Update transactions that could not be processed successfully (count) | +| [`processed`](#show-stats-path-tree-server-transactions-update-processed) | The number of successfully processed Update transactions (count) | -## `show stats performance-monitoring peer-path mos` +## `show stats path-tree server transactions update duration` -MOS value calculated for the SSR peer path. (hundreths of a decimal) (in-memory) +Average time to process/respond-to Update transactions (microseconds) #### Usage ``` -show stats performance-monitoring peer-path mos [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions update duration [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | -| device-name | The name of the device port for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| peer-host | The host of the peer generating this metric (comma-separated list) | -| peer-name | The name of the peer generating this metric (comma-separated list) | -| protocol | The protocol for which this metric was generated (comma-separated list) | +| process | The name of the process generating this metric (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | -| traffic-class | The traffic class for which this metric was generated (comma-separated list) | -| vlan | The vlan for which this metrics was generated (comma-separated list) | ##### Positional Arguments @@ -67896,34 +68085,25 @@ show stats performance-monitoring peer-path mos [peer-name ] [peer-ho | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -#### Description - -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) - -## `show stats performance-monitoring peer-path received` +## `show stats path-tree server transactions update error` -Statistics for 'received' +The number of Update transactions that could not be processed successfully (count) #### Usage ``` -show stats performance-monitoring peer-path received [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions update error [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | -| device-name | The name of the device port for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| peer-host | The host of the peer generating this metric (comma-separated list) | -| peer-name | The name of the peer generating this metric (comma-separated list) | -| protocol | The protocol for which this metric was generated (comma-separated list) | +| process | The name of the process generating this metric (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | -| traffic-class | The traffic class for which this metric was generated (comma-separated list) | -| vlan | The vlan for which this metrics was generated (comma-separated list) | ##### Positional Arguments @@ -67931,38 +68111,25 @@ show stats performance-monitoring peer-path received [peer-name ] [pe | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -##### Subcommands - -| command | description | -| ------- | ----------- | -| [`loss`](#show-stats-performance-monitoring-peer-path-received-loss) | Packet loss percentange for receiving from the SSR peer path. (in-memory) | -| [`marked-packets`](#show-stats-performance-monitoring-peer-path-received-marked-packets) | The number of packets marked by the peer during a given interval. (in-memory) | -| [`marked-packets-acknowledged`](#show-stats-performance-monitoring-peer-path-received-marked-packets-acknowledged) | The number of marked packets acknowledged by the node during a given interval. (in-memory) | - -## `show stats performance-monitoring peer-path received loss` +## `show stats path-tree server transactions update processed` -Packet loss percentange for receiving from the SSR peer path. (in-memory) +The number of successfully processed Update transactions (count) #### Usage ``` -show stats performance-monitoring peer-path received loss [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] +show stats path-tree server transactions update processed [process ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | -| device-name | The name of the device port for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| peer-host | The host of the peer generating this metric (comma-separated list) | -| peer-name | The name of the peer generating this metric (comma-separated list) | -| protocol | The protocol for which this metric was generated (comma-separated list) | +| process | The name of the process generating this metric (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | -| traffic-class | The traffic class for which this metric was generated (comma-separated list) | -| vlan | The vlan for which this metrics was generated (comma-separated list) | ##### Positional Arguments @@ -67970,18 +68137,14 @@ show stats performance-monitoring peer-path received loss [peer-name | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -#### Description - -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) - -## `show stats performance-monitoring peer-path received marked-packets` +## `show stats performance-monitoring` -The number of packets marked by the peer during a given interval. (in-memory) +Stats pertaining to SSR peer path performance monitoring #### Usage ``` -show stats performance-monitoring peer-path received marked-packets [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] +show stats performance-monitoring [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68005,18 +68168,20 @@ show stats performance-monitoring peer-path received marked-packets [peer-name < | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -#### Description +##### Subcommands -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +| command | description | +| ------- | ----------- | +| [`peer-path`](#show-stats-performance-monitoring-peer-path) | Statistics for 'peer-path' | -## `show stats performance-monitoring peer-path received marked-packets-acknowledged` +## `show stats performance-monitoring peer-path` -The number of marked packets acknowledged by the node during a given interval. (in-memory) +Statistics for 'peer-path' #### Usage ``` -show stats performance-monitoring peer-path received marked-packets-acknowledged [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] +show stats performance-monitoring peer-path [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68040,18 +68205,26 @@ show stats performance-monitoring peer-path received marked-packets-acknowledged | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -#### Description +##### Subcommands -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +| command | description | +| ------- | ----------- | +| [`jitter`](#show-stats-performance-monitoring-peer-path-jitter) | Jitter in milliseconds for the SSR peer path. (in-memory) | +| [`latency`](#show-stats-performance-monitoring-peer-path-latency) | Latency in milliseconds for the SSR peer path. (in-memory) | +| [`loss`](#show-stats-performance-monitoring-peer-path-loss) | Aggregate packet loss percentange for the SSR peer path. (in-memory) | +| [`mos`](#show-stats-performance-monitoring-peer-path-mos) | MOS value calculated for the SSR peer path. (hundreths of a decimal) (in-memory) | +| [`received`](#show-stats-performance-monitoring-peer-path-received) | Statistics for 'received' | +| [`transmit`](#show-stats-performance-monitoring-peer-path-transmit) | Statistics for 'transmit' | +| [`updated`](#show-stats-performance-monitoring-peer-path-updated) | The unix timestamp (seconds) when the peer path's values were last updated. (in-memory) | -## `show stats performance-monitoring peer-path transmit` +## `show stats performance-monitoring peer-path jitter` -Statistics for 'transmit' +Jitter in milliseconds for the SSR peer path. (in-memory) #### Usage ``` -show stats performance-monitoring peer-path transmit [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] +show stats performance-monitoring peer-path jitter [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68075,22 +68248,18 @@ show stats performance-monitoring peer-path transmit [peer-name ] [pe | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -##### Subcommands +#### Description -| command | description | -| ------- | ----------- | -| [`loss`](#show-stats-performance-monitoring-peer-path-transmit-loss) | Packet loss percentange for transmitting to the SSR peer path. (in-memory) | -| [`marked-packets`](#show-stats-performance-monitoring-peer-path-transmit-marked-packets) | The number of packets marked by the node during a given interval. (in-memory) | -| [`marked-packets-acknowledged`](#show-stats-performance-monitoring-peer-path-transmit-marked-packets-acknowledged) | The number of marked packets acknowledged by the peer during a given interval. (in-memory) | +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). -## `show stats performance-monitoring peer-path transmit loss` +## `show stats performance-monitoring peer-path latency` -Packet loss percentange for transmitting to the SSR peer path. (in-memory) +Latency in milliseconds for the SSR peer path. (in-memory) #### Usage ``` -show stats performance-monitoring peer-path transmit loss [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] +show stats performance-monitoring peer-path latency [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68116,16 +68285,16 @@ show stats performance-monitoring peer-path transmit loss [peer-name #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). -## `show stats performance-monitoring peer-path transmit marked-packets` +## `show stats performance-monitoring peer-path loss` -The number of packets marked by the node during a given interval. (in-memory) +Aggregate packet loss percentange for the SSR peer path. (in-memory) #### Usage ``` -show stats performance-monitoring peer-path transmit marked-packets [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] +show stats performance-monitoring peer-path loss [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68151,16 +68320,16 @@ show stats performance-monitoring peer-path transmit marked-packets [peer-name < #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). -## `show stats performance-monitoring peer-path transmit marked-packets-acknowledged` +## `show stats performance-monitoring peer-path mos` -The number of marked packets acknowledged by the peer during a given interval. (in-memory) +MOS value calculated for the SSR peer path. (hundreths of a decimal) (in-memory) #### Usage ``` -show stats performance-monitoring peer-path transmit marked-packets-acknowledged [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] +show stats performance-monitoring peer-path mos [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68186,16 +68355,16 @@ show stats performance-monitoring peer-path transmit marked-packets-acknowledged #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). -## `show stats performance-monitoring peer-path updated` +## `show stats performance-monitoring peer-path received` -The unix timestamp (seconds) when the peer path's values were last updated. (in-memory) +Statistics for 'received' #### Usage ``` -show stats performance-monitoring peer-path updated [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] +show stats performance-monitoring peer-path received [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68219,29 +68388,38 @@ show stats performance-monitoring peer-path updated [peer-name ] [pee | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -#### Description +##### Subcommands -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +| command | description | +| ------- | ----------- | +| [`loss`](#show-stats-performance-monitoring-peer-path-received-loss) | Packet loss percentange for receiving from the SSR peer path. (in-memory) | +| [`marked-packets`](#show-stats-performance-monitoring-peer-path-received-marked-packets) | The number of packets marked by the peer during a given interval. (in-memory) | +| [`marked-packets-acknowledged`](#show-stats-performance-monitoring-peer-path-received-marked-packets-acknowledged) | The number of marked packets acknowledged by the node during a given interval. (in-memory) | -## `show stats process` +## `show stats performance-monitoring peer-path received loss` -Metrics about SSR processes +Packet loss percentange for receiving from the SSR peer path. (in-memory) #### Usage ``` -show stats process [process-name ] [since ] [force] [router ] [node ] [] +show stats performance-monitoring peer-path received loss [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | +| device-name | The name of the device port for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| process-name | The name of the process (comma-separated list) | +| peer-host | The host of the peer generating this metric (comma-separated list) | +| peer-name | The name of the peer generating this metric (comma-separated list) | +| protocol | The protocol for which this metric was generated (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | +| vlan | The vlan for which this metrics was generated (comma-separated list) | ##### Positional Arguments @@ -68249,39 +68427,34 @@ show stats process [process-name ] [since ] [force] [router | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -##### Subcommands - -| command | description | -| ------- | ----------- | -| [`cpu`](#show-stats-process-cpu) | Metrics about CPU usage of SSR processes | -| [`memory`](#show-stats-process-memory) | Metrics about memory usage of SSR processes | -| [`thread`](#show-stats-process-thread) | Metrics about threads in SSR processes | - -##### See Also +#### Description -| command | description | -| ------- | ----------- | -| [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). -## `show stats process cpu` +## `show stats performance-monitoring peer-path received marked-packets` -Metrics about CPU usage of SSR processes +The number of packets marked by the peer during a given interval. (in-memory) #### Usage ``` -show stats process cpu [process-name ] [since ] [force] [router ] [node ] [] +show stats performance-monitoring peer-path received marked-packets [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | +| device-name | The name of the device port for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| process-name | The name of the process (comma-separated list) | +| peer-host | The host of the peer generating this metric (comma-separated list) | +| peer-name | The name of the peer generating this metric (comma-separated list) | +| protocol | The protocol for which this metric was generated (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | +| vlan | The vlan for which this metrics was generated (comma-separated list) | ##### Positional Arguments @@ -68289,37 +68462,34 @@ show stats process cpu [process-name ] [since ] [force] [ro | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -##### Subcommands - -| command | description | -| ------- | ----------- | -| [`usage`](#show-stats-process-cpu-usage) | CPU percentage used per process | - -##### See Also +#### Description -| command | description | -| ------- | ----------- | -| [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). -## `show stats process cpu usage` +## `show stats performance-monitoring peer-path received marked-packets-acknowledged` -CPU percentage used per process +The number of marked packets acknowledged by the node during a given interval. (in-memory) #### Usage ``` -show stats process cpu usage [process-name ] [since ] [force] [router ] [node ] [] +show stats performance-monitoring peer-path received marked-packets-acknowledged [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | +| device-name | The name of the device port for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| process-name | The name of the process (comma-separated list) | +| peer-host | The host of the peer generating this metric (comma-separated list) | +| peer-name | The name of the peer generating this metric (comma-separated list) | +| protocol | The protocol for which this metric was generated (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | +| vlan | The vlan for which this metrics was generated (comma-separated list) | ##### Positional Arguments @@ -68327,31 +68497,34 @@ show stats process cpu usage [process-name ] [since ] [forc | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -##### See Also +#### Description -| command | description | -| ------- | ----------- | -| [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). -## `show stats process memory` +## `show stats performance-monitoring peer-path transmit` -Metrics about memory usage of SSR processes +Statistics for 'transmit' #### Usage ``` -show stats process memory [process-name ] [since ] [force] [router ] [node ] [] +show stats performance-monitoring peer-path transmit [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | +| device-name | The name of the device port for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| process-name | The name of the process (comma-separated list) | +| peer-host | The host of the peer generating this metric (comma-separated list) | +| peer-name | The name of the peer generating this metric (comma-separated list) | +| protocol | The protocol for which this metric was generated (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | +| vlan | The vlan for which this metrics was generated (comma-separated list) | ##### Positional Arguments @@ -68363,37 +68536,34 @@ show stats process memory [process-name ] [since ] [force] | command | description | | ------- | ----------- | -| [`allocated`](#show-stats-process-memory-allocated) | Number of bytes allocated to the application itself | -| [`heap-size`](#show-stats-process-memory-heap-size) | Number of bytes allocated to the heap | -| [`rss`](#show-stats-process-memory-rss) | Resident memory used per process (bytes) | -| [`tc-malloc`](#show-stats-process-memory-tc-malloc) | Statistics for 'tc-malloc' | -| [`vsz`](#show-stats-process-memory-vsz) | Virtual memory used per process (bytes) | - -##### See Also - -| command | description | -| ------- | ----------- | -| [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | +| [`loss`](#show-stats-performance-monitoring-peer-path-transmit-loss) | Packet loss percentange for transmitting to the SSR peer path. (in-memory) | +| [`marked-packets`](#show-stats-performance-monitoring-peer-path-transmit-marked-packets) | The number of packets marked by the node during a given interval. (in-memory) | +| [`marked-packets-acknowledged`](#show-stats-performance-monitoring-peer-path-transmit-marked-packets-acknowledged) | The number of marked packets acknowledged by the peer during a given interval. (in-memory) | -## `show stats process memory allocated` +## `show stats performance-monitoring peer-path transmit loss` -Number of bytes allocated to the application itself +Packet loss percentange for transmitting to the SSR peer path. (in-memory) #### Usage ``` -show stats process memory allocated [process-name ] [since ] [force] [router ] [node ] [] +show stats performance-monitoring peer-path transmit loss [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | +| device-name | The name of the device port for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| process-name | The name of the process (comma-separated list) | +| peer-host | The host of the peer generating this metric (comma-separated list) | +| peer-name | The name of the peer generating this metric (comma-separated list) | +| protocol | The protocol for which this metric was generated (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | +| vlan | The vlan for which this metrics was generated (comma-separated list) | ##### Positional Arguments @@ -68401,31 +68571,34 @@ show stats process memory allocated [process-name ] [since | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -##### See Also +#### Description -| command | description | -| ------- | ----------- | -| [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). -## `show stats process memory heap-size` +## `show stats performance-monitoring peer-path transmit marked-packets` -Number of bytes allocated to the heap +The number of packets marked by the node during a given interval. (in-memory) #### Usage ``` -show stats process memory heap-size [process-name ] [since ] [force] [router ] [node ] [] +show stats performance-monitoring peer-path transmit marked-packets [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | +| device-name | The name of the device port for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| process-name | The name of the process (comma-separated list) | +| peer-host | The host of the peer generating this metric (comma-separated list) | +| peer-name | The name of the peer generating this metric (comma-separated list) | +| protocol | The protocol for which this metric was generated (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | +| vlan | The vlan for which this metrics was generated (comma-separated list) | ##### Positional Arguments @@ -68433,31 +68606,34 @@ show stats process memory heap-size [process-name ] [since | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -##### See Also +#### Description -| command | description | -| ------- | ----------- | -| [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). -## `show stats process memory rss` +## `show stats performance-monitoring peer-path transmit marked-packets-acknowledged` -Resident memory used per process (bytes) +The number of marked packets acknowledged by the peer during a given interval. (in-memory) #### Usage ``` -show stats process memory rss [process-name ] [since ] [force] [router ] [node ] [] +show stats performance-monitoring peer-path transmit marked-packets-acknowledged [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | +| device-name | The name of the device port for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| process-name | The name of the process (comma-separated list) | +| peer-host | The host of the peer generating this metric (comma-separated list) | +| peer-name | The name of the peer generating this metric (comma-separated list) | +| protocol | The protocol for which this metric was generated (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | +| vlan | The vlan for which this metrics was generated (comma-separated list) | ##### Positional Arguments @@ -68465,31 +68641,34 @@ show stats process memory rss [process-name ] [since ] [for | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -##### See Also +#### Description -| command | description | -| ------- | ----------- | -| [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). -## `show stats process memory tc-malloc` +## `show stats performance-monitoring peer-path updated` -Statistics for 'tc-malloc' +The unix timestamp (seconds) when the peer path's values were last updated. (in-memory) #### Usage ``` -show stats process memory tc-malloc [process-name ] [since ] [force] [router ] [node ] [] +show stats performance-monitoring peer-path updated [peer-name ] [peer-host ] [device-name ] [vlan ] [traffic-class ] [protocol ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | +| device-name | The name of the device port for which this metric was generated (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | -| process-name | The name of the process (comma-separated list) | +| peer-host | The host of the peer generating this metric (comma-separated list) | +| peer-name | The name of the peer generating this metric (comma-separated list) | +| protocol | The protocol for which this metric was generated (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | +| vlan | The vlan for which this metrics was generated (comma-separated list) | ##### Positional Arguments @@ -68497,29 +68676,18 @@ show stats process memory tc-malloc [process-name ] [since | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | -##### Subcommands - -| command | description | -| ------- | ----------- | -| [`current-total-thread-cache`](#show-stats-process-memory-tc-malloc-current-total-thread-cache) | Number of (some of the) bytes tc-malloc is using for small objects | -| [`max-total-thread-cache`](#show-stats-process-memory-tc-malloc-max-total-thread-cache) | Number of bytes tc-malloc dedicates for small objects | -| [`page-heap-free`](#show-stats-process-memory-tc-malloc-page-heap-free) | Number of bytes in free, mapped pages in the page heap | -| [`page-heap-unmapped`](#show-stats-process-memory-tc-malloc-page-heap-unmapped) | Number of bytes in free, unmapped pages in the page heap | - -##### See Also +#### Description -| command | description | -| ------- | ----------- | -| [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). -## `show stats process memory tc-malloc current-total-thread-cache` +## `show stats process` -Number of (some of the) bytes tc-malloc is using for small objects +Metrics about SSR processes #### Usage ``` -show stats process memory tc-malloc current-total-thread-cache [process-name ] [since ] [force] [router ] [node ] [] +show stats process [process-name ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68538,20 +68706,28 @@ show stats process memory tc-malloc current-total-thread-cache [process-name ] [since ] [force] [router ] [node ] [] +show stats process cpu [process-name ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68570,20 +68746,26 @@ show stats process memory tc-malloc max-total-thread-cache [process-name ] [since ] [force] [router ] [node ] [] +show stats process cpu usage [process-name ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68608,14 +68790,14 @@ show stats process memory tc-malloc page-heap-free [process-name ] | ------- | ----------- | | [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | -## `show stats process memory tc-malloc page-heap-unmapped` +## `show stats process memory` -Number of bytes in free, unmapped pages in the page heap +Metrics about memory usage of SSR processes #### Usage ``` -show stats process memory tc-malloc page-heap-unmapped [process-name ] [since ] [force] [router ] [node ] [] +show stats process memory [process-name ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68634,20 +68816,30 @@ show stats process memory tc-malloc page-heap-unmapped [process-name ] [since ] [force] [router ] [node ] [] +show stats process memory allocated [process-name ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68672,14 +68864,14 @@ show stats process memory vsz [process-name ] [since ] [for | ------- | ----------- | | [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | -## `show stats process thread` +## `show stats process memory heap-size` -Metrics about threads in SSR processes +Number of bytes allocated to the heap #### Usage ``` -show stats process thread [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] +show stats process memory heap-size [process-name ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68691,7 +68883,6 @@ show stats process thread [process-name ] [thread-name ] [thread-name ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| node | The name of the node generating this metric | +| process-name | The name of the process (comma-separated list) | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | ##### See Also @@ -68713,14 +68928,14 @@ show stats process thread [process-name ] [thread-name ] [thread-name ] [since ] [force] [router ] [node ] [] +show stats process memory tc-malloc [process-name ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68732,7 +68947,6 @@ show stats process thread cpu [process-name ] [thread-name ] [thread-name ] [thread-name ] [thread-name ] [since ] [force] [router ] [node ] [] +show stats process memory tc-malloc current-total-thread-cache [process-name ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68774,7 +68988,6 @@ show stats process thread cpu iowait [process-name ] [thread-name | process-name | The name of the process (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | -| thread-name | The name of the thread (comma-separated list) | ##### Positional Arguments @@ -68788,14 +69001,14 @@ show stats process thread cpu iowait [process-name ] [thread-name | ------- | ----------- | | [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | -## `show stats process thread cpu system-usage` +## `show stats process memory tc-malloc max-total-thread-cache` -System-level CPU percentage used in a thread +Number of bytes tc-malloc dedicates for small objects #### Usage ``` -show stats process thread cpu system-usage [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] +show stats process memory tc-malloc max-total-thread-cache [process-name ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68807,7 +69020,6 @@ show stats process thread cpu system-usage [process-name ] [thread | process-name | The name of the process (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | -| thread-name | The name of the thread (comma-separated list) | ##### Positional Arguments @@ -68821,14 +69033,14 @@ show stats process thread cpu system-usage [process-name ] [thread | ------- | ----------- | | [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | -## `show stats process thread cpu usage` +## `show stats process memory tc-malloc page-heap-free` -CPU percentage used in a thread for both user and system +Number of bytes in free, mapped pages in the page heap #### Usage ``` -show stats process thread cpu usage [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] +show stats process memory tc-malloc page-heap-free [process-name ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68840,7 +69052,6 @@ show stats process thread cpu usage [process-name ] [thread-name < | process-name | The name of the process (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | -| thread-name | The name of the thread (comma-separated list) | ##### Positional Arguments @@ -68854,14 +69065,78 @@ show stats process thread cpu usage [process-name ] [thread-name < | ------- | ----------- | | [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | -## `show stats process thread cpu user-usage` +## `show stats process memory tc-malloc page-heap-unmapped` -User-level CPU percentage used in a thread +Number of bytes in free, unmapped pages in the page heap #### Usage ``` -show stats process thread cpu user-usage [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] +show stats process memory tc-malloc page-heap-unmapped [process-name ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| node | The name of the node generating this metric | +| process-name | The name of the process (comma-separated list) | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +##### See Also + +| command | description | +| ------- | ----------- | +| [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | + +## `show stats process memory vsz` + +Virtual memory used per process (bytes) + +#### Usage + +``` +show stats process memory vsz [process-name ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| node | The name of the node generating this metric | +| process-name | The name of the process (comma-separated list) | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +##### See Also + +| command | description | +| ------- | ----------- | +| [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | + +## `show stats process thread` + +Metrics about threads in SSR processes + +#### Usage + +``` +show stats process thread [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68881,20 +69156,28 @@ show stats process thread cpu user-usage [process-name ] [thread-n | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | +##### Subcommands + +| command | description | +| ------- | ----------- | +| [`cpu`](#show-stats-process-thread-cpu) | Metrics about CPU usage of threads in SSR processes | +| [`queue`](#show-stats-process-thread-queue) | Metrics about queues in threads in SSR processes | +| [`task`](#show-stats-process-thread-task) | Metrics about tasks in threads in SSR processes | + ##### See Also | command | description | | ------- | ----------- | | [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | -## `show stats process thread queue` +## `show stats process thread cpu` -Metrics about queues in threads in SSR processes +Metrics about CPU usage of threads in SSR processes #### Usage ``` -show stats process thread queue [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] +show stats process thread cpu [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68918,9 +69201,10 @@ show stats process thread queue [process-name ] [thread-name ] [thread-name ] [thread-name ] [average-type-name ] [since ] [force] [router ] [node ] [] +show stats process thread cpu iowait [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | -| average-type-name | The name of the average type: long-term vs. recent (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | process-name | The name of the process (comma-separated list) | @@ -68962,14 +69245,14 @@ show stats process thread queue delay [process-name ] [thread-name | ------- | ----------- | | [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | -## `show stats process thread queue depth` +## `show stats process thread cpu system-usage` -The number of tasks in the thread-queue waiting to be executed +System-level CPU percentage used in a thread #### Usage ``` -show stats process thread queue depth [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] +show stats process thread cpu system-usage [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -68995,14 +69278,14 @@ show stats process thread queue depth [process-name ] [thread-name | ------- | ----------- | | [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | -## `show stats process thread queue total` +## `show stats process thread cpu usage` -The lifetime total number of tasks sent through the thread-queue (in-memory) +CPU percentage used in a thread for both user and system #### Usage ``` -show stats process thread queue total [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] +show stats process thread cpu usage [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -69028,18 +69311,47 @@ show stats process thread queue total [process-name ] [thread-name | ------- | ----------- | | [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | -#### Description +## `show stats process thread cpu user-usage` -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +User-level CPU percentage used in a thread -## `show stats process thread task` +#### Usage -Metrics about tasks in threads in SSR processes +``` +show stats process thread cpu user-usage [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| node | The name of the node generating this metric | +| process-name | The name of the process (comma-separated list) | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| thread-name | The name of the thread (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +##### See Also + +| command | description | +| ------- | ----------- | +| [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | + +## `show stats process thread queue` + +Metrics about queues in threads in SSR processes #### Usage ``` -show stats process thread task [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] +show stats process thread queue [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -69063,10 +69375,9 @@ show stats process thread task [process-name ] [thread-name ] [thread-name ] [thread-name ] [since ] [force] [router ] [node ] [] +show stats process thread queue delay [process-name ] [thread-name ] [average-type-name ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | +| average-type-name | The name of the average type: long-term vs. recent (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | process-name | The name of the process (comma-separated list) | @@ -69107,31 +69419,25 @@ show stats process thread task errors [process-name ] [thread-name | ------- | ----------- | | [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | -#### Description - -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) - -## `show stats process thread task execution-time` +## `show stats process thread queue depth` -The running-average execution times for tasks of the given type on the thread (us) (in-memory) +The number of tasks in the thread-queue waiting to be executed #### Usage ``` -show stats process thread task execution-time [process-name ] [thread-name ] [task-type ] [average-type-name ] [since ] [force] [router ] [node ] [] +show stats process thread queue depth [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments | name | description | | ---- | ----------- | -| average-type-name | The name of the average type: long-term vs. recent (comma-separated list) | | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | process-name | The name of the process (comma-separated list) | | router | The router for which to display stats (default: <current router>) | | since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | -| task-type | The type of the task: normal, packet, exclusive, etc. (comma-separated list) | | thread-name | The name of the thread (comma-separated list) | ##### Positional Arguments @@ -69146,18 +69452,14 @@ show stats process thread task execution-time [process-name ] [thr | ------- | ----------- | | [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | -#### Description - -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) - -## `show stats process thread task timeouts` +## `show stats process thread queue total` -The total number of tasks that timed out on the thread (in-memory) +The lifetime total number of tasks sent through the thread-queue (in-memory) #### Usage ``` -show stats process thread task timeouts [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] +show stats process thread queue total [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] ``` ##### Keyword Arguments @@ -69185,7 +69487,162 @@ show stats process thread task timeouts [process-name ] [thread-na #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats process thread task` + +Metrics about tasks in threads in SSR processes + +#### Usage + +``` +show stats process thread task [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| node | The name of the node generating this metric | +| process-name | The name of the process (comma-separated list) | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| thread-name | The name of the thread (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +##### Subcommands + +| command | description | +| ------- | ----------- | +| [`errors`](#show-stats-process-thread-task-errors) | The total number of failed tasks on the thread (in-memory) | +| [`execution-time`](#show-stats-process-thread-task-execution-time) | The running-average execution times for tasks of the given type on the thread (us) (in-memory) | +| [`timeouts`](#show-stats-process-thread-task-timeouts) | The total number of tasks that timed out on the thread (in-memory) | +| [`total`](#show-stats-process-thread-task-total) | The lifetime total number of tasks of the given type executed on the thread (in-memory) | + +##### See Also + +| command | description | +| ------- | ----------- | +| [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | + +## `show stats process thread task errors` + +The total number of failed tasks on the thread (in-memory) + +#### Usage + +``` +show stats process thread task errors [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| node | The name of the node generating this metric | +| process-name | The name of the process (comma-separated list) | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| thread-name | The name of the thread (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +##### See Also + +| command | description | +| ------- | ----------- | +| [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats process thread task execution-time` + +The running-average execution times for tasks of the given type on the thread (us) (in-memory) + +#### Usage + +``` +show stats process thread task execution-time [process-name ] [thread-name ] [task-type ] [average-type-name ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| average-type-name | The name of the average type: long-term vs. recent (comma-separated list) | +| force | Skip confirmation prompt. Only required when targeting all routers | +| node | The name of the node generating this metric | +| process-name | The name of the process (comma-separated list) | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| task-type | The type of the task: normal, packet, exclusive, etc. (comma-separated list) | +| thread-name | The name of the thread (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +##### See Also + +| command | description | +| ------- | ----------- | +| [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats process thread task timeouts` + +The total number of tasks that timed out on the thread (in-memory) + +#### Usage + +``` +show stats process thread task timeouts [process-name ] [thread-name ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| node | The name of the node generating this metric | +| process-name | The name of the process (comma-separated list) | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| thread-name | The name of the thread (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +##### See Also + +| command | description | +| ------- | ----------- | +| [`show system processes`](cli_reference.md#show-system-processes) | Display a table summarizing the statuses of processes. | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats process thread task total` @@ -69223,7 +69680,7 @@ show stats process thread task total [process-name ] [thread-name #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats queue` @@ -69319,7 +69776,7 @@ show stats queue consumed bytes [topic ] [since ] [force] [router #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats queue consumed messages` @@ -69349,7 +69806,7 @@ show stats queue consumed messages [topic ] [since ] [force] [rout #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats queue produced` @@ -69412,7 +69869,7 @@ show stats queue produced bytes [topic ] [since ] [force] [router #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats queue produced messages` @@ -69442,7 +69899,7 @@ show stats queue produced messages [topic ] [since ] [force] [rout #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats redis-server-manager` @@ -74674,7 +75131,7 @@ show stats service-area mist-events failed [since ] [force] [router ] [force] [router ] [force] [router ] [node ] [ | ------- | ----------- | | [`device-interface`](#show-stats-traffic-eng-device-interface) | Stats pertaining to device interface traffic engineering | | [`internal-application`](#show-stats-traffic-eng-internal-application) | Stats pertaining to traffic engineering stats for internal applications | +| [`network-interface`](#show-stats-traffic-eng-network-interface) | Stats pertaining to network-interface traffic engineering | ## `show stats traffic-eng device-interface` @@ -80040,7 +80498,7 @@ show stats traffic-eng device-interface [since ] [force] [router | command | description | | ------- | ----------- | -| [`common`](#show-stats-traffic-eng-device-interface-common) | Stats pertaining to both device interface and peer path traffic engineering | +| [`common`](#show-stats-traffic-eng-device-interface-common) | Common stats pertaining to traffic engineering | | [`dequeue-cycle-count`](#show-stats-traffic-eng-device-interface-dequeue-cycle-count) | The current dequeue cycle count in traffic engineering (cycles) | | [`enqueue-cycle-count`](#show-stats-traffic-eng-device-interface-enqueue-cycle-count) | The current enqueue cycle count in traffic engineering (cycles) | | [`packets-queued`](#show-stats-traffic-eng-device-interface-packets-queued) | The current number of packets queued for this device interface | @@ -80050,7 +80508,7 @@ show stats traffic-eng device-interface [since ] [force] [router ## `show stats traffic-eng device-interface common` -Stats pertaining to both device interface and peer path traffic engineering +Common stats pertaining to traffic engineering #### Usage @@ -80312,7 +80770,7 @@ show stats traffic-eng device-interface peer-path dequeue-cycle-count [peer-name #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats traffic-eng device-interface peer-path enqueue-cycle-count` @@ -80345,7 +80803,7 @@ show stats traffic-eng device-interface peer-path enqueue-cycle-count [peer-name #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats traffic-eng device-interface peer-path packets-queued` @@ -80378,7 +80836,7 @@ show stats traffic-eng device-interface peer-path packets-queued [peer-name ] [internal | ---- | ----------- | | verbosity | detail \| summary \| debug (default: detail) | +## `show stats traffic-eng network-interface` + +Stats pertaining to network-interface traffic engineering + +#### Usage + +``` +show stats traffic-eng network-interface [netintf ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +##### Subcommands + +| command | description | +| ------- | ----------- | +| [`dequeue-cycle-count`](#show-stats-traffic-eng-network-interface-dequeue-cycle-count) | The current dequeue cycle count in traffic engineering for this network-interface (cycles) (in-memory) | +| [`enqueue-cycle-count`](#show-stats-traffic-eng-network-interface-enqueue-cycle-count) | The current enqueue cycle count in traffic engineering for this network-interface (cycles) (in-memory) | +| [`packets-queued`](#show-stats-traffic-eng-network-interface-packets-queued) | The current number of packets queued in traffic engineering for this network-interface (in-memory) | +| [`per-traffic-class`](#show-stats-traffic-eng-network-interface-per-traffic-class) | Stats pertaining to network-interface per traffic class traffic engineering | +| [`scheduler-reset`](#show-stats-traffic-eng-network-interface-scheduler-reset) | The number of times the scheduler has been reset | + +## `show stats traffic-eng network-interface dequeue-cycle-count` + +The current dequeue cycle count in traffic engineering for this network-interface (cycles) (in-memory) + +#### Usage + +``` +show stats traffic-eng network-interface dequeue-cycle-count [netintf ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats traffic-eng network-interface enqueue-cycle-count` + +The current enqueue cycle count in traffic engineering for this network-interface (cycles) (in-memory) + +#### Usage + +``` +show stats traffic-eng network-interface enqueue-cycle-count [netintf ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats traffic-eng network-interface packets-queued` + +The current number of packets queued in traffic engineering for this network-interface (in-memory) + +#### Usage + +``` +show stats traffic-eng network-interface packets-queued [netintf ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats traffic-eng network-interface per-traffic-class` + +Stats pertaining to network-interface per traffic class traffic engineering + +#### Usage + +``` +show stats traffic-eng network-interface per-traffic-class [netintf ] [traffic-class ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +##### Subcommands + +| command | description | +| ------- | ----------- | +| [`buffer-capacity-exceeded-bytes`](#show-stats-traffic-eng-network-interface-per-traffic-class-buffer-capacity-exceeded-bytes) | The number of bytes failed to be scheduled for transmission due to exceeded buffer capacity for this network-interface (in-memory) | +| [`buffer-capacity-exceeded-packets`](#show-stats-traffic-eng-network-interface-per-traffic-class-buffer-capacity-exceeded-packets) | The number of packets failed to be scheduled for transmission due to exceeded buffer capacity for this network-interface (in-memory) | +| [`dequeue-aqm-drop-bytes`](#show-stats-traffic-eng-network-interface-per-traffic-class-dequeue-aqm-drop-bytes) | The number of bytes scheduled for transmission that were dropped due to Active Queue Management for this network-interface (in-memory) | +| [`dequeue-aqm-drop-packets`](#show-stats-traffic-eng-network-interface-per-traffic-class-dequeue-aqm-drop-packets) | The number of packets scheduled for transmission that were dropped due to Active Queue Management for this network-interface (in-memory) | +| [`dequeue-max-latency-drop-bytes`](#show-stats-traffic-eng-network-interface-per-traffic-class-dequeue-max-latency-drop-bytes) | The number of bytes scheduled for transmission that were dropped due to excessive latency for this network-interface (in-memory) | +| [`dequeue-max-latency-drop-packets`](#show-stats-traffic-eng-network-interface-per-traffic-class-dequeue-max-latency-drop-packets) | The number of packets scheduled for transmission that were dropped due to excessive latency for this network-interface (in-memory) | +| [`dequeue-success-bytes`](#show-stats-traffic-eng-network-interface-per-traffic-class-dequeue-success-bytes) | The number of bytes successfully dequeued from the scheduler for transmission for this network-interface (in-memory) | +| [`dequeue-success-packets`](#show-stats-traffic-eng-network-interface-per-traffic-class-dequeue-success-packets) | The number of packets successfully dequeued from the scheduler for transmission for this network-interface (in-memory) | +| [`schedule-failure-bandwidth`](#show-stats-traffic-eng-network-interface-per-traffic-class-schedule-failure-bandwidth) | Traffic bandwidth dropped by the scheduler for this network-interface (bytes per second) (in-memory) | +| [`schedule-failure-bytes`](#show-stats-traffic-eng-network-interface-per-traffic-class-schedule-failure-bytes) | The number of bytes failed to be scheduled for transmission due to bandwidth oversubscription for this network-interface (in-memory) | +| [`schedule-failure-packets`](#show-stats-traffic-eng-network-interface-per-traffic-class-schedule-failure-packets) | The number of packets failed to scheduled for transmission due to bandwidth oversubscription for this network-interface (in-memory) | +| [`schedule-success-bandwidth`](#show-stats-traffic-eng-network-interface-per-traffic-class-schedule-success-bandwidth) | Traffic bandwidth successfully scheduled for transmission for this network-interface (bytes per second) (in-memory) | +| [`schedule-success-bytes`](#show-stats-traffic-eng-network-interface-per-traffic-class-schedule-success-bytes) | The number of bytes successfully scheduled for transmission for this network-interface (in-memory) | +| [`schedule-success-packets`](#show-stats-traffic-eng-network-interface-per-traffic-class-schedule-success-packets) | The number of packets successfully scheduled for transmission for this network-interface (in-memory) | + +## `show stats traffic-eng network-interface per-traffic-class buffer-capacity-exceeded-bytes` + +The number of bytes failed to be scheduled for transmission due to exceeded buffer capacity for this network-interface (in-memory) + +#### Usage + +``` +show stats traffic-eng network-interface per-traffic-class buffer-capacity-exceeded-bytes [netintf ] [traffic-class ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats traffic-eng network-interface per-traffic-class buffer-capacity-exceeded-packets` + +The number of packets failed to be scheduled for transmission due to exceeded buffer capacity for this network-interface (in-memory) + +#### Usage + +``` +show stats traffic-eng network-interface per-traffic-class buffer-capacity-exceeded-packets [netintf ] [traffic-class ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats traffic-eng network-interface per-traffic-class dequeue-aqm-drop-bytes` + +The number of bytes scheduled for transmission that were dropped due to Active Queue Management for this network-interface (in-memory) + +#### Usage + +``` +show stats traffic-eng network-interface per-traffic-class dequeue-aqm-drop-bytes [netintf ] [traffic-class ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats traffic-eng network-interface per-traffic-class dequeue-aqm-drop-packets` + +The number of packets scheduled for transmission that were dropped due to Active Queue Management for this network-interface (in-memory) + +#### Usage + +``` +show stats traffic-eng network-interface per-traffic-class dequeue-aqm-drop-packets [netintf ] [traffic-class ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats traffic-eng network-interface per-traffic-class dequeue-max-latency-drop-bytes` + +The number of bytes scheduled for transmission that were dropped due to excessive latency for this network-interface (in-memory) + +#### Usage + +``` +show stats traffic-eng network-interface per-traffic-class dequeue-max-latency-drop-bytes [netintf ] [traffic-class ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats traffic-eng network-interface per-traffic-class dequeue-max-latency-drop-packets` + +The number of packets scheduled for transmission that were dropped due to excessive latency for this network-interface (in-memory) + +#### Usage + +``` +show stats traffic-eng network-interface per-traffic-class dequeue-max-latency-drop-packets [netintf ] [traffic-class ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats traffic-eng network-interface per-traffic-class dequeue-success-bytes` + +The number of bytes successfully dequeued from the scheduler for transmission for this network-interface (in-memory) + +#### Usage + +``` +show stats traffic-eng network-interface per-traffic-class dequeue-success-bytes [netintf ] [traffic-class ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats traffic-eng network-interface per-traffic-class dequeue-success-packets` + +The number of packets successfully dequeued from the scheduler for transmission for this network-interface (in-memory) + +#### Usage + +``` +show stats traffic-eng network-interface per-traffic-class dequeue-success-packets [netintf ] [traffic-class ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats traffic-eng network-interface per-traffic-class schedule-failure-bandwidth` + +Traffic bandwidth dropped by the scheduler for this network-interface (bytes per second) (in-memory) + +#### Usage + +``` +show stats traffic-eng network-interface per-traffic-class schedule-failure-bandwidth [netintf ] [traffic-class ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats traffic-eng network-interface per-traffic-class schedule-failure-bytes` + +The number of bytes failed to be scheduled for transmission due to bandwidth oversubscription for this network-interface (in-memory) + +#### Usage + +``` +show stats traffic-eng network-interface per-traffic-class schedule-failure-bytes [netintf ] [traffic-class ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats traffic-eng network-interface per-traffic-class schedule-failure-packets` + +The number of packets failed to scheduled for transmission due to bandwidth oversubscription for this network-interface (in-memory) + +#### Usage + +``` +show stats traffic-eng network-interface per-traffic-class schedule-failure-packets [netintf ] [traffic-class ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats traffic-eng network-interface per-traffic-class schedule-success-bandwidth` + +Traffic bandwidth successfully scheduled for transmission for this network-interface (bytes per second) (in-memory) + +#### Usage + +``` +show stats traffic-eng network-interface per-traffic-class schedule-success-bandwidth [netintf ] [traffic-class ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats traffic-eng network-interface per-traffic-class schedule-success-bytes` + +The number of bytes successfully scheduled for transmission for this network-interface (in-memory) + +#### Usage + +``` +show stats traffic-eng network-interface per-traffic-class schedule-success-bytes [netintf ] [traffic-class ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats traffic-eng network-interface per-traffic-class schedule-success-packets` + +The number of packets successfully scheduled for transmission for this network-interface (in-memory) + +#### Usage + +``` +show stats traffic-eng network-interface per-traffic-class schedule-success-packets [netintf ] [traffic-class ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| traffic-class | The traffic class for which this metric was generated (comma-separated list) | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + +#### Description + +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). + +## `show stats traffic-eng network-interface scheduler-reset` + +The number of times the scheduler has been reset + +#### Usage + +``` +show stats traffic-eng network-interface scheduler-reset [netintf ] [since ] [force] [router ] [node ] [] +``` + +##### Keyword Arguments + +| name | description | +| ---- | ----------- | +| force | Skip confirmation prompt. Only required when targeting all routers | +| netintf | The network interface for which this metric was generated (comma-separated list) | +| node | The name of the node generating this metric | +| router | The router for which to display stats (default: <current router>) | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | + +##### Positional Arguments + +| name | description | +| ---- | ----------- | +| verbosity | detail \| summary \| debug (default: detail) | + ## `show stats traffic-export` Stats pertaining to exported traffic events @@ -81854,7 +82944,7 @@ show stats traffic-export enqueue-failure [core ] [since ] [force] #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats traffic-export error-enqueue-failure` @@ -81883,7 +82973,7 @@ show stats traffic-export error-enqueue-failure [since ] [force] [router #### Description -For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md) +For more information regarding in-memory metrics, please refer to [Configuring In-Memory Metrics](config_in-memory_metrics.md). ## `show stats traffic-export rate-limit-exceeded` @@ -81912,7 +83002,7 @@ show stats traffic-export rate-limit-exceeded [since ] [force] [router ] [force] [router ] [force] [router ] [force] [router ] | ---- | ----------- | | identityref | Value to add to this list | +#### Description + +##### identityref + +A value from a set of predefined names. + +Options: +config-read Configuration Read Capability +config-write Configuration Write Capability +provisioning Asset Provisioning Capability + ## `configure authority access-management role description` A description about the role. @@ -139,6 +150,12 @@ configure authority access-management role description [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + ## `configure authority access-management role exclude-resource` Exclude a resource from being associated with this role. @@ -179,6 +196,20 @@ configure authority access-management role exclude-resource id [] | ---- | ----------- | | resource-id | The value to set for this field | +#### Description + +##### resource-id (string) + +The identifier of the resource. + +Must be either just a `*` asterisk or an identifier +followed by a colon which is then followed by either +an asterisk, or a path that contains only valid yang +names and list-keys separated by forward-slashes and +optionally followed by a forward-slash and an asterisk. + +Example: 128t:/authority/router/MyRouter/* + ## `configure authority access-management role name` A unique name that identifies this role. @@ -195,6 +226,15 @@ configure authority access-management role name [] | ---- | ----------- | | name-id | The value to set for this field | +#### Description + +##### name-id (string) + +A string identifier which only uses alphanumerics, underscores, or dashes, and cannot exceed 63 characters. + +Must contain only alphanumeric characters or any of the following: _ - +Length: 0-63 + ## `configure authority access-management role resource` Associate this role with a resource. @@ -237,6 +277,14 @@ configure authority access-management role resource generated [] | ---- | ----------- | | boolean | The value to set for this field | +#### Description + +##### boolean + +A true or false value. + +Options: true or false + ## `configure authority access-management role resource id` Configure Id @@ -253,6 +301,20 @@ configure authority access-management role resource id [] | ---- | ----------- | | resource-id | The value to set for this field | +#### Description + +##### resource-id (string) + +The identifier of the resource. + +Must be either just a `*` asterisk or an identifier +followed by a colon which is then followed by either +an asterisk, or a path that contains only valid yang +names and list-keys separated by forward-slashes and +optionally followed by a forward-slash and an asterisk. + +Example: 128t:/authority/router/MyRouter/* + ## `configure authority access-management role resource-group` Associate this role with a top-level resource-group. @@ -269,6 +331,12 @@ configure authority access-management role resource-group [] | ---- | ----------- | | resource-group-ref | Value to add to this list | +#### Description + +##### resource-group-ref (leafref) + +This type is used by other entities that need to reference configured resource groups. + ## `configure authority access-management token` Configuration for HTTP authentication token generation. @@ -302,6 +370,27 @@ configure authority access-management token expiration [] Units: minutes +Default: never + +##### union + +A value that corresponds to one of its member types. + +Must be one of the following types: + +###### (0) uint64 + +An unsigned 64-bit integer. + +Range: 1-18446744073709551615 + +###### (1) enumeration + +A value from a set of predefined names. + +Options: +never Never expire + ## `configure authority asset-connection-resiliency` Configure Asset Connection Resiliency @@ -331,6 +420,16 @@ configure authority asset-connection-resiliency enabled [] | ---- | ----------- | | boolean | The value to set for this field | +#### Description + +Default: true + +##### boolean + +A true or false value. + +Options: true or false + ## `configure authority backwards-compatible-vrf-bgp-tenants` When generating tenant names for VRF BGP over SVR, do not use leading or trailing underscores. This enables backwards compatibility with router versions smaller than 5.1.3 @@ -347,6 +446,16 @@ configure authority backwards-compatible-vrf-bgp-tenants [] | ---- | ----------- | | boolean | The value to set for this field | +#### Description + +Default: false + +##### boolean + +A true or false value. + +Options: true or false + ## `configure authority bgp-service-generation` Configure Bgp Service Generation @@ -378,6 +487,16 @@ configure authority bgp-service-generation route-reflector-client-mesh [] | ---- | ----------- | | security-ref | The value to set for this field | +#### Description + +##### security-ref (leafref) + +This type is used by other entities that need to reference configured security policies. + ## `configure authority bgp-service-generation service-policy` Service policy to be used for generated BGP services. @@ -410,6 +535,12 @@ configure authority bgp-service-generation service-policy [] | ---- | ----------- | | service-policy-ref | The value to set for this field | +#### Description + +##### service-policy-ref (leafref) + +This type is used by other entities that need to reference configured service policies. + ## `configure authority cli-messages` Configure Cli Messages @@ -440,6 +571,12 @@ configure authority cli-messages login-message [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + ## `configure authority cli-messages welcome-message` The message displayed after a successful login through console. @@ -456,6 +593,12 @@ configure authority cli-messages welcome-message [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + ## `configure authority client-certificate` The client-certificate configuration contains client certificate content. @@ -498,6 +641,12 @@ configure authority client-certificate content [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string (required) + +A text value. + ## `configure authority client-certificate name` An identifier for the client certificate. @@ -514,6 +663,15 @@ configure authority client-certificate name [] | ---- | ----------- | | name-id | The value to set for this field | +#### Description + +##### name-id (string) + +A string identifier which only uses alphanumerics, underscores, or dashes, and cannot exceed 63 characters. + +Must contain only alphanumeric characters or any of the following: _ - +Length: 0-63 + ## `configure authority conductor-address` IP address or FQDN of the conductor @@ -530,6 +688,60 @@ configure authority conductor-address [] | ---- | ----------- | | hostv4 | Value to add to this list | +#### Description + +##### hostv4 (union) + +The host type represents either an IPv4 address or a DNS domain name. + +Must be one of the following types: + +###### (0) ipv4-address (string) + +The ipv4-address type represents an IPv4 address in dotted-quad notation. + +Must be a valid IPv4 address. + +###### (1) domain-name (string) + +The domain-name type represents a DNS domain name. The +name SHOULD be fully qualified whenever possible. + +Internet domain names are only loosely specified. Section +3.5 of RFC 1034 recommends a syntax (modified in Section +2.1 of RFC 1123). The pattern above is intended to allow +for current practice in domain name use, and some possible +future expansion. It is designed to hold various types of +domain names, including names used for A or AAAA records +(host names) and other records, such as SRV records. Note +that Internet host names have a stricter syntax (described +in RFC 952) than the DNS recommendations in RFCs 1034 and +1123, and that systems that want to store host names in +schema nodes using the domain-name type are recommended to +adhere to this stricter standard to ensure interoperability. + +The encoding of DNS names in the DNS protocol is limited +to 255 characters. Since the encoding consists of labels +prefixed by a length bytes and there is a trailing NULL +byte, only 253 characters can appear in the textual dotted +notation. + +The description clause of schema nodes using the domain-name +type MUST describe when and how these names are resolved to +IP addresses. Note that the resolution of a domain-name value +may require to query multiple DNS records (e.g., A for IPv4 +and AAAA for IPv6). The order of the resolution process and +which DNS record takes precedence can either be defined +explicitely or it may depend on the configuration of the +resolver. + +Domain-name values use the US-ASCII encoding. Their canonical +format uses lowercase US-ASCII characters. Internationalized +domain names MUST be encoded in punycode as described in RFC +3492 + +Length: 1-253 + ## `configure authority currency` Local monetary unit. @@ -546,6 +758,14 @@ configure authority currency [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +Default: USD + +##### string + +A text value. + ## `configure authority district` Districts in the authority. @@ -589,6 +809,15 @@ configure authority district name [] | ---- | ----------- | | non-default-district-name | The value to set for this field | +#### Description + +##### non-default-district-name (string) + +A text value. + +Must contain only alphanumeric characters or any of the following: _ - +Length: 0-63 + ## `configure authority district neighborhood` Neighborhoods which belong to this district. @@ -605,6 +834,15 @@ configure authority district neighborhood [] | ---- | ----------- | | neighborhood-id | Value to add to this list | +#### Description + +##### neighborhood-id (string) + +A string identifier for network neighborhood. + +Must contain only alphanumeric characters or any of the following: . _ - +Length: 0-63 + ## `configure authority district resource-group` Associate this district with a top-level resource-group. @@ -621,6 +859,12 @@ configure authority district resource-group [] | ---- | ----------- | | resource-group-ref | Value to add to this list | +#### Description + +##### resource-group-ref (leafref) + +This type is used by other entities that need to reference configured resource groups. + ## `configure authority dscp-map` Configure Dscp Map @@ -719,6 +963,14 @@ configure authority dscp-map dscp-prioritization dscp-range end-value [] | ---- | ----------- | | dscp | The value to set for this field | +#### Description + +##### dscp (uint8) (required) + +A DSCP value (0-63) + +Range: 0-63 + ## `configure authority dscp-map dscp-prioritization priority` The priority assigned to the incoming DSCP value. @@ -751,6 +1011,14 @@ configure authority dscp-map dscp-prioritization priority [] | ---- | ----------- | | priority-id | The value to set for this field | +#### Description + +##### priority-id (uint8) + +An unsigned 8-bit integer. + +Range: 0-3 + ## `configure authority dscp-map dscp-traffic-class` Mapping from incoming DSCP value to a traffic-class. These values are used when in DSCP trust mode. @@ -820,6 +1088,14 @@ configure authority dscp-map dscp-traffic-class dscp-range end-value [] | ---- | ----------- | | dscp | The value to set for this field | +#### Description + +##### dscp (uint8) (required) + +A DSCP value (0-63) + +Range: 0-63 + ## `configure authority dscp-map dscp-traffic-class traffic-class` The traffic-class assigned to the incoming DSCP value. @@ -852,6 +1136,18 @@ configure authority dscp-map dscp-traffic-class traffic-class [] | ---- | ----------- | | name-id | The value to set for this field | +#### Description + +##### name-id (string) + +A string identifier which only uses alphanumerics, underscores, or dashes, and cannot exceed 63 characters. + +Must contain only alphanumeric characters or any of the following: _ - +Length: 0-63 + ## `configure authority dscp-map resource-group` Associate this DSCP map with a top-level resource-group. @@ -884,6 +1189,12 @@ configure authority dscp-map resource-group [] | ---- | ----------- | | resource-group-ref | Value to add to this list | +#### Description + +##### resource-group-ref (leafref) + +This type is used by other entities that need to reference configured resource groups. + ## `configure authority dynamic-hostname` Hostname format for interfaces with dynamic addresses. It is a template with subsitution variables used to generate a unique hostname corresponding to Network Interfaces that have dynamically learned IP addresses. Uses the following substitution variables: {interface-id} for Network Interface Global Identifier {router-name} for Router Name {authority-name} for Authority Name For example, 'interface-{interface-id}.{router-name}.{authority-name}'. @@ -900,6 +1211,22 @@ configure authority dynamic-hostname [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +Default: interface-{interface-id}.{router-name}.{authority-name} + +##### string + +A text value. + +Must contain substitution variables: +{interface-id} for Network Interface Global Identifier +{router-name} for Router Name +{authority-name} for Authority Name +For example, 'interface-{interface-id}.{router-name}.{authority-name}'. +Any other characters must be alphanumeric or any of the +following: - _ . + ## `configure authority fib-service-match` When creating FIB entries by matching route updates to service addresses, consider the specified service addresses. @@ -916,6 +1243,18 @@ configure authority fib-service-match [] | ---- | ----------- | | enumeration | The value to set for this field | +#### Description + +Default: best-match-only + +##### enumeration + +A value from a set of predefined names. + +Options: +best-match-only Longest matching service prefix only. +any-match All service prefixes are considered. + ## `configure authority forward-error-correction-profile` A profile for Forward Error Correection parameters, describing how often to send parity packets. @@ -959,6 +1298,18 @@ configure authority forward-error-correction-profile mode [] | ---- | ----------- | | enumeration | The value to set for this field | +#### Description + +Default: dynamic + +##### enumeration + +A value from a set of predefined names. + +Options: +dynamic Alter ratio of packets to parity based on loss observed. +static Use a consistent ratio of packets to parity regardless of loss. + ## `configure authority forward-error-correction-profile name` The name of the Forward Error Correction profile @@ -975,6 +1326,15 @@ configure authority forward-error-correction-profile name [] | ---- | ----------- | | name-id | The value to set for this field | +#### Description + +##### name-id (string) + +A string identifier which only uses alphanumerics, underscores, or dashes, and cannot exceed 63 characters. + +Must contain only alphanumeric characters or any of the following: _ - +Length: 0-63 + ## `configure authority forward-error-correction-profile ratio` The ratio (expressed as x:1) which will dictate the number of data packets to transmit before a parity packet will be transmitted. @@ -991,6 +1351,16 @@ configure authority forward-error-correction-profile ratio [] | ---- | ----------- | | uint8 | The value to set for this field | +#### Description + +Default: 10 + +##### uint8 + +An unsigned 8-bit integer. + +Range: 2-50 + ## `configure authority icmp-control` Settings for ICMP packet handling @@ -1021,6 +1391,18 @@ configure authority icmp-control icmp-async-reply [] | ---- | ----------- | | enumeration | The value to set for this field | +#### Description + +Default: allow + +##### enumeration + +A value from a set of predefined names. + +Options: +drop ICMP replies without matching requests are dropped. +allow ICMP replies without matching requests are forwarded. + ## `configure authority icmp-control icmp-session-match` How to differentiate ICMP sessions. @@ -1037,6 +1419,18 @@ configure authority icmp-control icmp-session-match [] | ---- | ----------- | | enumeration | The value to set for this field | +#### Description + +Default: identifier-only + +##### enumeration + +A value from a set of predefined names. + +Options: +identifier-only ICMP sessions are based on identifier. +identifier-and-type ICMP sessions are based on identifier and type. + ## `configure authority idp-profile` User defined IDP profiles. @@ -1081,6 +1475,17 @@ configure authority idp-profile base-policy [] | ---- | ----------- | | idp-policy | The value to set for this field | +#### Description + +##### idp-policy (enumeration) (required) + +Predefined policies for intrusion detection actions. + +Options: +alert A policy that only alerts. +standard The standard blocking and alerting policy. +strict A strict blocking and alerting policy. + ## `configure authority idp-profile name` Name of the profile. @@ -1097,6 +1502,16 @@ configure authority idp-profile name [] | ---- | ----------- | | name-id | The value to set for this field | +#### Description + +##### name-id (string) + +A string identifier which only uses alphanumerics, underscores, or dashes, and cannot exceed 63 characters. + +Must contain only alphanumeric characters or any of the following: _ - +IDP profile name (alert|strict|standard|none) is reserved. +Length: 0-63 + ## `configure authority idp-profile rule` Configure Rule @@ -1141,6 +1556,12 @@ configure authority idp-profile rule description [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + ## `configure authority idp-profile rule match` The options to use for matching. @@ -1174,6 +1595,53 @@ configure authority idp-profile rule match client-address [] | ---- | ----------- | | ip-prefix | Value to add to this list | +#### Description + +##### ip-prefix (union) + +The ip-prefix type represents an IP prefix and is IP version neutral. The format of the textual representations implies the IP version. + +Must be one of the following types: + +###### (0) ipv4-prefix (string) + +The ipv4-prefix type represents an IPv4 address prefix. +The prefix length is given by the number following the +slash character and must be less than or equal to 32. + +A prefix length value of n corresponds to an IP address +mask that has n contiguous 1-bits from the most +significant bit (MSB) and all other bits set to 0. + +The canonical format of an IPv4 prefix has all bits of +the IPv4 address set to zero that are not part of the +IPv4 prefix. + +###### (1) ipv6-prefix (string) + +The ipv6-prefix type represents an IPv6 address prefix. +The prefix length is given by the number following the +slash character and must be less than or equal 128. + +A prefix length value of n corresponds to an IP address +mask that has n contiguous 1-bits from the most +significant bit (MSB) and all other bits set to 0. + +The IPv6 address should have all bits that do not belong +to the prefix set to zero. + +The canonical format of an IPv6 prefix has all bits of +the IPv6 address set to zero that are not part of the +IPv6 prefix. Furthermore, IPv6 address is represented +in the compressed format described in RFC 4291, Section +2.2, item 2 with the following additional rules: the :: +substitution must be applied to the longest sequence of +all-zero 16-bit chunks in an IPv6 address. If there is +a tie, the first sequence of all-zero 16-bit chunks is +replaced by ::. Single all-zero 16-bit chunks are not +compressed. The canonical format uses lowercase +characters and leading zeros are not allowed. + ## `configure authority idp-profile rule match destination-address` Destination address prefix to match in the rule. @@ -1190,6 +1658,53 @@ configure authority idp-profile rule match destination-address [] | ---- | ----------- | | ip-prefix | Value to add to this list | +#### Description + +##### ip-prefix (union) + +The ip-prefix type represents an IP prefix and is IP version neutral. The format of the textual representations implies the IP version. + +Must be one of the following types: + +###### (0) ipv4-prefix (string) + +The ipv4-prefix type represents an IPv4 address prefix. +The prefix length is given by the number following the +slash character and must be less than or equal to 32. + +A prefix length value of n corresponds to an IP address +mask that has n contiguous 1-bits from the most +significant bit (MSB) and all other bits set to 0. + +The canonical format of an IPv4 prefix has all bits of +the IPv4 address set to zero that are not part of the +IPv4 prefix. + +###### (1) ipv6-prefix (string) + +The ipv6-prefix type represents an IPv6 address prefix. +The prefix length is given by the number following the +slash character and must be less than or equal 128. + +A prefix length value of n corresponds to an IP address +mask that has n contiguous 1-bits from the most +significant bit (MSB) and all other bits set to 0. + +The IPv6 address should have all bits that do not belong +to the prefix set to zero. + +The canonical format of an IPv6 prefix has all bits of +the IPv6 address set to zero that are not part of the +IPv6 prefix. Furthermore, IPv6 address is represented +in the compressed format described in RFC 4291, Section +2.2, item 2 with the following additional rules: the :: +substitution must be applied to the longest sequence of +all-zero 16-bit chunks in an IPv6 address. If there is +a tie, the first sequence of all-zero 16-bit chunks is +replaced by ::. Single all-zero 16-bit chunks are not +compressed. The canonical format uses lowercase +characters and leading zeros are not allowed. + ## `configure authority idp-profile rule match severities` List of severity to match in the rule. @@ -1206,6 +1721,17 @@ configure authority idp-profile rule match severities [] | ---- | ----------- | | idp-severity | Value to add to this list | +#### Description + +##### idp-severity (enumeration) + +Severity levels for IDP rules. + +Options: +minor Filter minor or higher vulnerabilities. +major Filter major or higher vulnerabilities. +critical Filter only critical vulnerabilities. + ## `configure authority idp-profile rule match severity` Match vulnerabilities only with severity mentioned or above. @@ -1222,6 +1748,17 @@ configure authority idp-profile rule match severity [] | ---- | ----------- | | idp-severity | The value to set for this field | +#### Description + +##### idp-severity (enumeration) + +Severity levels for IDP rules. + +Options: +minor Filter minor or higher vulnerabilities. +major Filter major or higher vulnerabilities. +critical Filter only critical vulnerabilities. + ## `configure authority idp-profile rule match vulnerability` List of custom vulnerabilities to match in the rule. @@ -1238,6 +1775,12 @@ configure authority idp-profile rule match vulnerability [] | ---- | ----------- | | string | Value to add to this list | +#### Description + +##### string + +A text value. + ## `configure authority idp-profile rule name` Name of the rule. @@ -1254,6 +1797,15 @@ configure authority idp-profile rule name [] | ---- | ----------- | | name-id | The value to set for this field | +#### Description + +##### name-id (string) + +A string identifier which only uses alphanumerics, underscores, or dashes, and cannot exceed 63 characters. + +Must contain only alphanumeric characters or any of the following: _ - +Length: 0-63 + ## `configure authority idp-profile rule outcome` The outcome applied to the match @@ -1284,6 +1836,17 @@ configure authority idp-profile rule outcome action [] | ---- | ----------- | | enumeration | The value to set for this field | +#### Description + +##### enumeration (required) + +A value from a set of predefined names. + +Options: +alert Alert only. +drop Drop session. +close-tcp-connection Close TCP Connection. + ## `configure authority idp-profile rule outcome severity` Modify a vulnerability severity level of the match. @@ -1300,6 +1863,17 @@ configure authority idp-profile rule outcome severity [] | ---- | ----------- | | idp-severity | The value to set for this field | +#### Description + +##### idp-severity (enumeration) + +Severity levels for IDP rules. + +Options: +minor Filter minor or higher vulnerabilities. +major Filter major or higher vulnerabilities. +critical Filter only critical vulnerabilities. + ## `configure authority ipfix-collector` Configuration for IPFIX record export. @@ -1353,6 +1927,14 @@ configure authority ipfix-collector interim-record-interval [] Units: seconds +Default: 120 + +##### uint32 + +An unsigned 32-bit integer. + +Range: 60-1800 + ## `configure authority ipfix-collector ip-address` The IP address or hostname of the collector. @@ -1369,6 +1951,84 @@ configure authority ipfix-collector ip-address [] | ---- | ----------- | | host | The value to set for this field | +#### Description + +##### host (union) (required) + +The host type represents either an IP address or a DNS domain name. + +Must be one of the following types: + +###### (0) ip-address (union) (required) + +The ip-address type represents an IP address and is IP version neutral. The format of the textual representations implies the IP version. + +Must be one of the following types: + +####### (0) ipv4-address (string) (required): + +The ipv4-address type represents an IPv4 address in dotted-quad notation. + +Must be a valid IPv4 address. + +####### (1) ipv6-address (string) (required): + +The ipv6-address type represents an IPv6 address in full, +mixed, shortened, and shortened-mixed notation. + +The canonical format of IPv6 addresses uses the compressed +format described in RFC 4291, Section 2.2, item 2 with the +following additional rules: the :: substitution must be +applied to the longest sequence of all-zero 16-bit chunks +in an IPv6 address. If there is a tie, the first sequence +of all-zero 16-bit chunks is replaced by ::. Single +all-zero 16-bit chunks are not compressed. The canonical +format uses lowercase characters and leading zeros are +not allowed. + +Must be a valid IPv6 address. +Must be a valid IPv6 address. + +###### (1) domain-name (string) (required) + +The domain-name type represents a DNS domain name. The +name SHOULD be fully qualified whenever possible. + +Internet domain names are only loosely specified. Section +3.5 of RFC 1034 recommends a syntax (modified in Section +2.1 of RFC 1123). The pattern above is intended to allow +for current practice in domain name use, and some possible +future expansion. It is designed to hold various types of +domain names, including names used for A or AAAA records +(host names) and other records, such as SRV records. Note +that Internet host names have a stricter syntax (described +in RFC 952) than the DNS recommendations in RFCs 1034 and +1123, and that systems that want to store host names in +schema nodes using the domain-name type are recommended to +adhere to this stricter standard to ensure interoperability. + +The encoding of DNS names in the DNS protocol is limited +to 255 characters. Since the encoding consists of labels +prefixed by a length bytes and there is a trailing NULL +byte, only 253 characters can appear in the textual dotted +notation. + +The description clause of schema nodes using the domain-name +type MUST describe when and how these names are resolved to +IP addresses. Note that the resolution of a domain-name value +may require to query multiple DNS records (e.g., A for IPv4 +and AAAA for IPv6). The order of the resolution process and +which DNS record takes precedence can either be defined +explicitely or it may depend on the configuration of the +resolver. + +Domain-name values use the US-ASCII encoding. Their canonical +format uses lowercase US-ASCII characters. Internationalized +domain names MUST be encoded in punycode as described in RFC +3492 + +Length: 1-253 + ## `configure authority ipfix-collector name` A unique name for the collector. @@ -1385,6 +2045,15 @@ configure authority ipfix-collector name [] | ---- | ----------- | | name-id | The value to set for this field | +#### Description + +##### name-id (string) + +A string identifier which only uses alphanumerics, underscores, or dashes, and cannot exceed 63 characters. + +Must contain only alphanumeric characters or any of the following: _ - +Length: 0-63 + ## `configure authority ipfix-collector port` The port of the collector. @@ -1401,6 +2070,16 @@ configure authority ipfix-collector port [] | ---- | ----------- | | l4-port | The value to set for this field | +#### Description + +Default: 4739 + +##### l4-port (uint16) + +Transport (layer 4) port number. + +Range: 0-65535 + ## `configure authority ipfix-collector protocol` The transport protocol to be used when communicating with the collector. @@ -1417,6 +2096,18 @@ configure authority ipfix-collector protocol [] | ---- | ----------- | | ipfix-protocol | The value to set for this field | +#### Description + +Default: tcp + +##### ipfix-protocol (enumeration) + +Transport (Layer 4) protocol. + +Options: +tcp Transmission Control Protocol. +udp User Datagram Protocol. + ## `configure authority ipfix-collector resource-group` Associate this IPFIX collector with a top-level resource-group. @@ -1433,6 +2124,12 @@ configure authority ipfix-collector resource-group [] | ---- | ----------- | | resource-group-ref | Value to add to this list | +#### Description + +##### resource-group-ref (leafref) + +This type is used by other entities that need to reference configured resource groups. + ## `configure authority ipfix-collector sampling-percentage` The percentage of flows to be selected for export OR 'dynamic'. When set to 'dynamic', the system will select a percentage based on the current data volume as follows: || < 100 Mb/s : 1 in 256 || < 1 Gb/s : 1 in 512 || < 10 Gb/s : 1 in 1024 || < 25 Gb/s : 1 in 2048 || > 25 Gb/s : 1 in 8192 || @@ -1449,6 +2146,30 @@ configure authority ipfix-collector sampling-percentage [] | ---- | ----------- | | union | The value to set for this field | +#### Description + +Default: dynamic + +##### union + +A value that corresponds to one of its member types. + +Must be one of the following types: + +###### (0) decimal64 + +A 64-bit decimal value. + +Range: 0-100 +Fraction digits: 16 + +###### (1) enumeration + +A value from a set of predefined names. + +Options: +dynamic Dynamically determine sampling based on data volume. + ## `configure authority ipfix-collector template-refresh-interval` The time between template retransmissions when using the UDP protocol. @@ -1469,6 +2190,14 @@ configure authority ipfix-collector template-refresh-interval [] Units: seconds +Default: 60 + +##### uint32 + +An unsigned 32-bit integer. + +Range: 60-1800 + ## `configure authority ipfix-collector tenant` The tenants whose records this collector should receive. An empty list indicates all tenants. @@ -1485,6 +2214,12 @@ configure authority ipfix-collector tenant [] | ---- | ----------- | | tenant-ref | Value to add to this list | +#### Description + +##### tenant-ref (leafref) + +This type is used by other entities that need to reference configured tenants. + ## `configure authority ipv4-option-filter` Configure Ipv 4 Option Filter @@ -1515,6 +2250,18 @@ configure authority ipv4-option-filter action [] | ---- | ----------- | | enumeration | The value to set for this field | +#### Description + +Default: allow-all + +##### enumeration + +A value from a set of predefined names. + +Options: +allow-all Allow all packets that contain options headers. +drop-all Drop all packets that contain options headers except for those defined in the exclusion list. + ## `configure authority ipv4-option-filter drop-exclusion` Option headers that will not cause the packet to be dropped when present. @@ -1531,6 +2278,14 @@ configure authority ipv4-option-filter drop-exclusion [] | ---- | ----------- | | uint8 | Value to add to this list | +#### Description + +##### uint8 + +An unsigned 8-bit integer. + +Range: 0-255 + ## `configure authority ldap-server` LDAP Servers against which to authenticate user credentials. @@ -1584,6 +2339,84 @@ configure authority ldap-server address [] | ---- | ----------- | | host | The value to set for this field | +#### Description + +##### host (union) (required) + +The host type represents either an IP address or a DNS domain name. + +Must be one of the following types: + +###### (0) ip-address (union) (required) + +The ip-address type represents an IP address and is IP version neutral. The format of the textual representations implies the IP version. + +Must be one of the following types: + +####### (0) ipv4-address (string) (required): + +The ipv4-address type represents an IPv4 address in dotted-quad notation. + +Must be a valid IPv4 address. + +####### (1) ipv6-address (string) (required): + +The ipv6-address type represents an IPv6 address in full, +mixed, shortened, and shortened-mixed notation. + +The canonical format of IPv6 addresses uses the compressed +format described in RFC 4291, Section 2.2, item 2 with the +following additional rules: the :: substitution must be +applied to the longest sequence of all-zero 16-bit chunks +in an IPv6 address. If there is a tie, the first sequence +of all-zero 16-bit chunks is replaced by ::. Single +all-zero 16-bit chunks are not compressed. The canonical +format uses lowercase characters and leading zeros are +not allowed. + +Must be a valid IPv6 address. +Must be a valid IPv6 address. + +###### (1) domain-name (string) (required) + +The domain-name type represents a DNS domain name. The +name SHOULD be fully qualified whenever possible. + +Internet domain names are only loosely specified. Section +3.5 of RFC 1034 recommends a syntax (modified in Section +2.1 of RFC 1123). The pattern above is intended to allow +for current practice in domain name use, and some possible +future expansion. It is designed to hold various types of +domain names, including names used for A or AAAA records +(host names) and other records, such as SRV records. Note +that Internet host names have a stricter syntax (described +in RFC 952) than the DNS recommendations in RFCs 1034 and +1123, and that systems that want to store host names in +schema nodes using the domain-name type are recommended to +adhere to this stricter standard to ensure interoperability. + +The encoding of DNS names in the DNS protocol is limited +to 255 characters. Since the encoding consists of labels +prefixed by a length bytes and there is a trailing NULL +byte, only 253 characters can appear in the textual dotted +notation. + +The description clause of schema nodes using the domain-name +type MUST describe when and how these names are resolved to +IP addresses. Note that the resolution of a domain-name value +may require to query multiple DNS records (e.g., A for IPv4 +and AAAA for IPv6). The order of the resolution process and +which DNS record takes precedence can either be defined +explicitely or it may depend on the configuration of the +resolver. + +Domain-name values use the US-ASCII encoding. Their canonical +format uses lowercase US-ASCII characters. Internationalized +domain names MUST be encoded in punycode as described in RFC +3492 + +Length: 1-253 + ## `configure authority ldap-server auto-generate-filter` When enabled, the SSR will generate user-search-base and group-search-base LDAP filters. @@ -1600,6 +2433,16 @@ configure authority ldap-server auto-generate-filter [] | ---- | ----------- | | boolean | The value to set for this field | +#### Description + +Default: true + +##### boolean + +A true or false value. + +Options: true or false + ## `configure authority ldap-server bind-type` The type of binding to the LDAP server. @@ -1616,6 +2459,19 @@ configure authority ldap-server bind-type [] | ---- | ----------- | | enumeration | The value to set for this field | +#### Description + +Default: anonymous + +##### enumeration + +A value from a set of predefined names. + +Options: +anonymous Bind to this server anonymously. +unauthenticated Bind to this server with a distinguished name only. +password Bind to this server with a distinguished name and password. + ## `configure authority ldap-server certificate-assurance` LDAP assurance level to apply on server certificates in a TLS session. @@ -1632,6 +2488,20 @@ configure authority ldap-server certificate-assurance [] | ---- | ----------- | | enumeration | The value to set for this field | +#### Description + +Default: strong + +##### enumeration + +A value from a set of predefined names. + +Options: +weak Do not request or check any server certificates. +mild Ignore invalid or missing certificates but check for hostname +moderate Terminate on invalid certificate but ignore missing certificates. +strong Terminate on invalid and missing certificates. + ## `configure authority ldap-server distinguished-name` The distinguished name to use for binding to the server. @@ -1648,6 +2518,14 @@ configure authority ldap-server distinguished-name [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + +Length: 1-18446744073709551615 + ## `configure authority ldap-server group-search-base` An optional group search LDAP filter to restrict searches for this attribute type. @@ -1664,6 +2542,14 @@ configure authority ldap-server group-search-base [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + +Length: 1-18446744073709551615 + ## `configure authority ldap-server name` The name of the LDAP server. @@ -1680,6 +2566,15 @@ configure authority ldap-server name [] | ---- | ----------- | | name-id | The value to set for this field | +#### Description + +##### name-id (string) + +A string identifier which only uses alphanumerics, underscores, or dashes, and cannot exceed 63 characters. + +Must contain only alphanumeric characters or any of the following: _ - +Length: 0-63 + ## `configure authority ldap-server password` The password to use for binding to the server. @@ -1696,6 +2591,14 @@ configure authority ldap-server password [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + +Length: 1-18446744073709551615 + ## `configure authority ldap-server port` Port to connect to LDAP server. @@ -1712,6 +2615,29 @@ configure authority ldap-server port [] | ---- | ----------- | | union | The value to set for this field | +#### Description + +Default: server-type-default + +##### union + +A value that corresponds to one of its member types. + +Must be one of the following types: + +###### (0) l4-port (uint16) + +Transport (layer 4) port number. + +Range: 0-65535 + +###### (1) enumeration + +A value from a set of predefined names. + +Options: +server-type-default Use the default based on server-type. + ## `configure authority ldap-server resource-group` Associate this LDAP server with a top-level resource-group. @@ -1728,6 +2654,12 @@ configure authority ldap-server resource-group [] | ---- | ----------- | | resource-group-ref | Value to add to this list | +#### Description + +##### resource-group-ref (leafref) + +This type is used by other entities that need to reference configured resource groups. + ## `configure authority ldap-server search-base` The LDAP search base string. @@ -1744,6 +2676,14 @@ configure authority ldap-server search-base [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string (required) + +A text value. + +Length: 1-18446744073709551615 + ## `configure authority ldap-server server-type` The type of LDAP server. @@ -1760,6 +2700,19 @@ configure authority ldap-server server-type [] | ---- | ----------- | | enumeration | The value to set for this field | +#### Description + +Default: ldaps + +##### enumeration + +A value from a set of predefined names. + +Options: +starttls Connect to this server using STARTTLS. Default port is 389. +ldaps Connect to this server via LDAPS. Default port is 636. +global-catalog Connect to this server as an Active Directory Global Catalog. Default port is 3269. + ## `configure authority ldap-server user-search-base` An optional user search LDAP filter to restrict searches for this attribute type. @@ -1776,6 +2729,14 @@ configure authority ldap-server user-search-base [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + +Length: 1-18446744073709551615 + ## `configure authority management-service-generation` Configure Management Service Generation @@ -1806,6 +2767,12 @@ configure authority management-service-generation service-policy [] | ---- | ----------- | | name-id | The value to set for this field | +#### Description + +##### name-id (string) + +A string identifier which only uses alphanumerics, underscores, or dashes, and cannot exceed 63 characters. + +Must contain only alphanumeric characters or any of the following: _ - +Length: 0-63 + ## `configure authority metrics-profile filter value` The values that should be included if matched @@ -1908,6 +2896,12 @@ configure authority metrics-profile filter value [] | ---- | ----------- | | string | Value to add to this list | +#### Description + +##### string + +A text value. + ## `configure authority metrics-profile metric` The ID of the metric as it exists in the REST API @@ -1950,6 +2944,12 @@ configure authority metrics-profile metric description [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + ## `configure authority metrics-profile metric id` The ID of the metric as it exists in the REST API @@ -1966,6 +2966,14 @@ configure authority metrics-profile metric id [] | ---- | ----------- | | metric-id | The value to set for this field | +#### Description + +##### metric-id (string) + +A string metric identifier based on the stats YANG path which only uses alphanumerics, dashes, and forward slashes. + +Must contain only alphanumeric characters or any of the following: - / + ## `configure authority metrics-profile name` The name of the profile @@ -1982,6 +2990,15 @@ configure authority metrics-profile name [] | ---- | ----------- | | name-id | The value to set for this field | +#### Description + +##### name-id (string) + +A string identifier which only uses alphanumerics, underscores, or dashes, and cannot exceed 63 characters. + +Must contain only alphanumeric characters or any of the following: _ - +Length: 0-63 + ## `configure authority name` The identifier for the Authority. @@ -1998,6 +3015,15 @@ configure authority name [] | ---- | ----------- | | name-id | The value to set for this field | +#### Description + +##### name-id (string) (required) + +A string identifier which only uses alphanumerics, underscores, or dashes, and cannot exceed 63 characters. + +Must contain only alphanumeric characters or any of the following: _ - +Length: 0-63 + ## `configure authority password-policy` Password policy for user's passwords. @@ -2030,6 +3056,16 @@ configure authority password-policy deny [] | ---- | ----------- | | uint32 | The value to set for this field | +#### Description + +Default: 6 + +##### uint32 + +An unsigned 32-bit integer. + +Range: 1-65535 + ## `configure authority password-policy lifetime` The lifetime of a user's password in days @@ -2050,6 +3086,14 @@ configure authority password-policy lifetime [] Units: days +Default: 99999 + +##### uint32 + +An unsigned 32-bit integer. + +Range: 1-99999 + ## `configure authority password-policy minimum-length` The minimum length of user's password. @@ -2066,6 +3110,16 @@ configure authority password-policy minimum-length [] | ---- | ----------- | | uint32 | The value to set for this field | +#### Description + +Default: 9 + +##### uint32 + +An unsigned 32-bit integer. + +Range: 8-65535 + ## `configure authority password-policy unlock-time` The time a user account will remained locked after failing login attempts @@ -2086,6 +3140,12 @@ configure authority password-policy unlock-time [] Units: seconds +Default: 1800 + +##### uint32 + +An unsigned 32-bit integer. + ## `configure authority pcli` Configure the PCLI. @@ -2171,6 +3231,14 @@ configure authority pcli alias command path [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + +Length: 1-18446744073709551615 + ## `configure authority pcli alias command table-filter` Filter the output table to only include the specified columns. This is a case-insensitive match (and also excludes special characters such as dashes.) @@ -2187,6 +3255,14 @@ configure authority pcli alias command table-filter [] | ---- | ----------- | | string | Value to add to this list | +#### Description + +##### string + +A text value. + +Length: 1-18446744073709551615 + ## `configure authority pcli alias description` A short, one line, description of the alias. This will be displayed in the PCLI as part of the command's help text. @@ -2203,6 +3279,14 @@ configure authority pcli alias description [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + +Length: 1-18446744073709551615 + ## `configure authority pcli alias path` The space-delimited path to the alias. This will be the text that a user must enter to run the alias. @@ -2219,6 +3303,14 @@ configure authority pcli alias path [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + +Length: 1-18446744073709551615 + ## `configure authority pcli alias resource-group` Associate this PCLI alias with a top-level resource-group. @@ -2235,6 +3327,12 @@ configure authority pcli alias resource-group [] | ---- | ----------- | | resource-group-ref | Value to add to this list | +#### Description + +##### resource-group-ref (leafref) + +This type is used by other entities that need to reference configured resource groups. + ## `configure authority performance-monitoring-profile` A performance monitoring profile used to determine how often packets should be marked. @@ -2284,6 +3382,14 @@ configure authority performance-monitoring-profile interval-duration [] Units: milliseconds +Default: 10000 + +##### uint32 + +An unsigned 32-bit integer. + +Range: 100-3600000 + ## `configure authority performance-monitoring-profile marking-count` The number of packets to mark within a given interval. @@ -2304,6 +3410,14 @@ configure authority performance-monitoring-profile marking-count [] Units: packets +Default: 100 + +##### uint16 + +An unsigned 16-bit integer. + +Range: 1-32767 + ## `configure authority performance-monitoring-profile monitor-only` Collect statistics without influencing packet processing features. @@ -2320,6 +3434,16 @@ configure authority performance-monitoring-profile monitor-only [] | ---- | ----------- | | boolean | The value to set for this field | +#### Description + +Default: false + +##### boolean + +A true or false value. + +Options: true or false + ## `configure authority performance-monitoring-profile name` The name of the performance monitoring profile. @@ -2336,6 +3460,15 @@ configure authority performance-monitoring-profile name [] | ---- | ----------- | | name-id | The value to set for this field | +#### Description + +##### name-id (string) + +A string identifier which only uses alphanumerics, underscores, or dashes, and cannot exceed 63 characters. + +Must contain only alphanumeric characters or any of the following: _ - +Length: 0-63 + ## `configure authority performance-monitoring-profile resource-group` Associate this performance monitoring profile with a top-level resource-group. @@ -2352,6 +3485,12 @@ configure authority performance-monitoring-profile resource-group [] | ---- | ----------- | | host | The value to set for this field | +#### Description + +##### host (union) (required) + +The host type represents either an IP address or a DNS domain name. + +Must be one of the following types: + +###### (0) ip-address (union) (required) + +The ip-address type represents an IP address and is IP version neutral. The format of the textual representations implies the IP version. + +Must be one of the following types: + +####### (0) ipv4-address (string) (required): + +The ipv4-address type represents an IPv4 address in dotted-quad notation. + +Must be a valid IPv4 address. + +####### (1) ipv6-address (string) (required): + +The ipv6-address type represents an IPv6 address in full, +mixed, shortened, and shortened-mixed notation. + +The canonical format of IPv6 addresses uses the compressed +format described in RFC 4291, Section 2.2, item 2 with the +following additional rules: the :: substitution must be +applied to the longest sequence of all-zero 16-bit chunks +in an IPv6 address. If there is a tie, the first sequence +of all-zero 16-bit chunks is replaced by ::. Single +all-zero 16-bit chunks are not compressed. The canonical +format uses lowercase characters and leading zeros are +not allowed. + +Must be a valid IPv6 address. +Must be a valid IPv6 address. + +###### (1) domain-name (string) (required) + +The domain-name type represents a DNS domain name. The +name SHOULD be fully qualified whenever possible. + +Internet domain names are only loosely specified. Section +3.5 of RFC 1034 recommends a syntax (modified in Section +2.1 of RFC 1123). The pattern above is intended to allow +for current practice in domain name use, and some possible +future expansion. It is designed to hold various types of +domain names, including names used for A or AAAA records +(host names) and other records, such as SRV records. Note +that Internet host names have a stricter syntax (described +in RFC 952) than the DNS recommendations in RFCs 1034 and +1123, and that systems that want to store host names in +schema nodes using the domain-name type are recommended to +adhere to this stricter standard to ensure interoperability. + +The encoding of DNS names in the DNS protocol is limited +to 255 characters. Since the encoding consists of labels +prefixed by a length bytes and there is a trailing NULL +byte, only 253 characters can appear in the textual dotted +notation. + +The description clause of schema nodes using the domain-name +type MUST describe when and how these names are resolved to +IP addresses. Note that the resolution of a domain-name value +may require to query multiple DNS records (e.g., A for IPv4 +and AAAA for IPv6). The order of the resolution process and +which DNS record takes precedence can either be defined +explicitely or it may depend on the configuration of the +resolver. + +Domain-name values use the US-ASCII encoding. Their canonical +format uses lowercase US-ASCII characters. Internationalized +domain names MUST be encoded in punycode as described in RFC +3492 + +Length: 1-253 + ## `configure authority radius-server name` The name of the Radius server. @@ -2413,6 +3630,15 @@ configure authority radius-server name [] | ---- | ----------- | | name-id | The value to set for this field | +#### Description + +##### name-id (string) + +A string identifier which only uses alphanumerics, underscores, or dashes, and cannot exceed 63 characters. + +Must contain only alphanumeric characters or any of the following: _ - +Length: 0-63 + ## `configure authority radius-server port` The port number Radius server listens on. @@ -2429,6 +3655,26 @@ configure authority radius-server port [] | ---- | ----------- | | port-number | The value to set for this field | +#### Description + +Default: 1812 + +##### port-number (uint16) + +The port-number type represents a 16-bit port number of an +Internet transport layer protocol such as UDP, TCP, DCCP, or +SCTP. Port numbers are assigned by IANA. A current list of +all assignments is available from <http://www.iana.org/>. + +Note that the port number value zero is reserved by IANA. In +situations where the value zero does not make sense, it can +be excluded by subtyping the port-number type. + +In the value set and its semantics, this type is equivalent +to the InetPortNumber textual convention of the SMIv2. + +Range: 0-65535 + ## `configure authority radius-server secret` The secret key to bind to the Radius server. @@ -2445,6 +3691,14 @@ configure authority radius-server secret [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string (required) + +A text value. + +Length: 1-16 + ## `configure authority radius-server timeout` Radius Request Timeout. @@ -2465,6 +3719,14 @@ configure authority radius-server timeout [] Units: seconds +Default: 3 + +##### uint32 + +An unsigned 32-bit integer. + +Range: 1-86400 + ## `configure authority rekey-interval` Hours between security key regeneration. Recommended value 24 hours. @@ -2485,6 +3747,27 @@ configure authority rekey-interval [] Units: hours +Default: never + +##### union + +A value that corresponds to one of its member types. + +Must be one of the following types: + +###### (0) uint32 + +An unsigned 32-bit integer. + +Range: 1-720 + +###### (1) enumeration + +A value from a set of predefined names. + +Options: +never Never regenerate security keys + ## `configure authority remote-login` Configure Remote Login @@ -2514,6 +3797,16 @@ configure authority remote-login enabled [] | ---- | ----------- | | boolean | The value to set for this field | +#### Description + +Default: false + +##### boolean + +A true or false value. + +Options: true or false + ## `configure authority resource-group` Collect objects into a management group. @@ -2556,6 +3849,12 @@ configure authority resource-group description [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + ## `configure authority resource-group name` The name of the resource group. @@ -2572,6 +3871,15 @@ configure authority resource-group name [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + +Must be the single character '*' OR Must contain only alphanumeric characters or any of the following: _ - +Length: 1-63 + ## `configure authority router` The router configuration element serves as a container for holding the nodes of a single deployed router, along with their policies. @@ -2651,7 +3959,16 @@ configure authority router administrative-group [] #### Description -Warning: 'administrative-group' is deprecated and will be removed in a future software version +:::warning +&#x27;administrative-group&#x27; is deprecated and will be removed in a future software version +::: + +##### name-id (string) + +A string identifier which only uses alphanumerics, underscores, or dashes, and cannot exceed 63 characters. + +Must contain only alphanumeric characters or any of the following: _ - +Length: 0-63 ## `configure authority router application-identification` @@ -2691,6 +4008,14 @@ configure authority router application-identification application-director-cache | ---- | ----------- | | uint64 | The value to set for this field | +#### Description + +Default: 10000 + +##### uint64 + +An unsigned 64-bit integer. + ## `configure authority router application-identification auto-update` Automatic updating of application data @@ -2724,6 +4049,21 @@ configure authority router application-identification auto-update day-of-week [< | ---- | ----------- | | enumeration | The value to set for this field | +#### Description + +##### enumeration + +A value from a set of predefined names. + +Options: +sun Download each Sunday +mon Download each Monday +tue Download each Tuesday +wed Download each Wednesday +thu Download each Thursday +fri Download each Friday +sat Download each Saturday + ## `configure authority router application-identification auto-update enabled` Enable updates @@ -2740,6 +4080,16 @@ configure authority router application-identification auto-update enabled [] | ---- | ----------- | | uint64 | The value to set for this field | +#### Description + +Default: 10000 + +##### uint64 + +An unsigned 64-bit integer. + ## `configure authority router application-identification mode` Application learning modes. @@ -2820,6 +4211,18 @@ configure authority router application-identification mode [] | ---- | ----------- | | enumeration | Value to add to this list | +#### Description + +##### enumeration + +A value from a set of predefined names. + +Options: +module Learn application via modules. +tls Learn application via TLS server name parsing. +http Learn application via HTTP host name parsing. +all Learn application via any available techniques. + ## `configure authority router application-identification per-app-metrics` Enable per app classification metrics @@ -2836,6 +4239,16 @@ configure authority router application-identification per-app-metrics [ | ---- | ----------- | | boolean | The value to set for this field | +#### Description + +Default: true + +##### boolean + +A true or false value. + +Options: true or false + ## `configure authority router application-identification summary-retention` Configure Summary Retention @@ -2866,6 +4279,16 @@ configure authority router application-identification summary-retention duration | ---- | ----------- | | duration | The value to set for this field | +#### Description + +Default: 24h + +##### duration (string) + +A simple time duration. Valid units are s - seconds, m - minutes, h - hours, and d - days: 5s, 10m, 24h, 15d + +Must be a duration with units of seconds, minutes, hours, or days. e.g. 5s, 10m, 23h, 5d + ## `configure authority router application-identification summary-retention enabled` Enable persistence of app summary to the DB for UI and other uses @@ -2882,6 +4305,16 @@ configure authority router application-identification summary-retention enabled | ---- | ----------- | | boolean | The value to set for this field | +#### Description + +Default: true + +##### boolean + +A true or false value. + +Options: true or false + ## `configure authority router application-identification summary-tracking` Enable session stats tracking by applications @@ -2898,6 +4331,16 @@ configure authority router application-identification summary-tracking [ | ---- | ----------- | | duration | The value to set for this field | +#### Description + +Default: 1m + +##### duration (string) + +A simple time duration. Valid units are s - seconds, m - minutes, h - hours, and d - days: 5s, 10m, 24h, 15d + +Must be a duration with units of seconds, minutes, hours, or days. e.g. 5s, 10m, 23h, 5d + ## `configure authority router bfd` BFD parameters for sessions between nodes within the router. @@ -3087,6 +4596,18 @@ configure authority router bfd authentication-type [] | ---- | ----------- | | enumeration | The value to set for this field | +#### Description + +Default: sha256 + +##### enumeration + +A value from a set of predefined names. + +Options: +simple Simple Password. +sha256 SHA256 + ## `configure authority router bfd desired-tx-interval` Represents the frequency with which BFD asynchronous control packets are sent to peer nodes/routers. @@ -3107,6 +4628,14 @@ configure authority router bfd desired-tx-interval [] Units: milliseconds +Default: 1000 + +##### uint32 + +An unsigned 32-bit integer. + +Range: 50-600000 + ## `configure authority router bfd dscp` The DSCP value to use with BFD packets. @@ -3123,6 +4652,16 @@ configure authority router bfd dscp [] | ---- | ----------- | | dscp | The value to set for this field | +#### Description + +Default: 0 + +##### dscp (uint8) + +A DSCP value (0-63) + +Range: 0-63 + ## `configure authority router bfd dynamic-damping` When enabled, extend the hold-down time if additional link flaps occur during the hold-down period. @@ -3139,6 +4678,18 @@ configure authority router bfd dynamic-damping [] | ---- | ----------- | | enumeration | The value to set for this field | +#### Description + +Default: disabled + +##### enumeration + +A value from a set of predefined names. + +Options: +enabled Extend hold-down time exponentially if link flaps occur during hold-down time. +disabled Use simple hold-down timer for every link up event. + ## `configure authority router bfd hold-down-time` Represents the hold-down time. If dynamic-damping is enabled, this is the initial hold-down time. @@ -3159,6 +4710,14 @@ configure authority router bfd hold-down-time [] Units: seconds +Default: 5 + +##### uint32 + +An unsigned 32-bit integer. + +Range: 1-300 + ## `configure authority router bfd link-test-interval` This represents the interval between BFD echo tests sent to the peer node/router. @@ -3179,6 +4738,14 @@ configure authority router bfd link-test-interval [] Units: seconds +Default: 10 + +##### uint32 + +An unsigned 32-bit integer. + +Range: 1-86400 + ## `configure authority router bfd link-test-length` This is the number of packets sent during one test cycle. A value of 0 disables BFD echo tests. @@ -3199,6 +4766,14 @@ configure authority router bfd link-test-length [] Units: packets +Default: 10 + +##### uint8 + +An unsigned 8-bit integer. + +Range: 0-255 + ## `configure authority router bfd maximum-hold-down-time` Represents the maximum hold-down time of dynamic-damping exponential backoff. If the hold-down-time hits the maximum three times in a row, it will reset back to the original value. @@ -3219,6 +4794,14 @@ configure authority router bfd maximum-hold-down-time [] Units: seconds +Default: 3600 + +##### uint32 + +An unsigned 32-bit integer. + +Range: 1-86400 + ## `configure authority router bfd multiplier` Number of consecutive missed messages from a peer before deciding that the link between them is unusable. Valid range is (3,20). @@ -3235,6 +4818,16 @@ configure authority router bfd multiplier [] | ---- | ----------- | | uint8 | The value to set for this field | +#### Description + +Default: 3 + +##### uint8 + +An unsigned 8-bit integer. + +Range: 3-20 + ## `configure authority router bfd required-min-rx-interval` Represents the minimum interval between BFD asynchronous control packets that this router is capable of supporting. @@ -3255,6 +4848,12 @@ configure authority router bfd required-min-rx-interval [] Units: milliseconds +Default: 1000 + +##### uint32 + +An unsigned 32-bit integer. + ## `configure authority router bfd state` When enabled, run BFD between all nodes within the router. @@ -3271,6 +4870,18 @@ configure authority router bfd state [] | ---- | ----------- | | enumeration | The value to set for this field | +#### Description + +Default: enabled + +##### enumeration + +A value from a set of predefined names. + +Options: +enabled BFD is enabled on all nodes of this router. +disabled BFD is disabled on all nodes of this router. + ## `configure authority router conductor-address` IP address or FQDN of the conductor @@ -3287,6 +4898,60 @@ configure authority router conductor-address [] | ---- | ----------- | | hostv4 | Value to add to this list | +#### Description + +##### hostv4 (union) + +The host type represents either an IPv4 address or a DNS domain name. + +Must be one of the following types: + +###### (0) ipv4-address (string) + +The ipv4-address type represents an IPv4 address in dotted-quad notation. + +Must be a valid IPv4 address. + +###### (1) domain-name (string) + +The domain-name type represents a DNS domain name. The +name SHOULD be fully qualified whenever possible. + +Internet domain names are only loosely specified. Section +3.5 of RFC 1034 recommends a syntax (modified in Section +2.1 of RFC 1123). The pattern above is intended to allow +for current practice in domain name use, and some possible +future expansion. It is designed to hold various types of +domain names, including names used for A or AAAA records +(host names) and other records, such as SRV records. Note +that Internet host names have a stricter syntax (described +in RFC 952) than the DNS recommendations in RFCs 1034 and +1123, and that systems that want to store host names in +schema nodes using the domain-name type are recommended to +adhere to this stricter standard to ensure interoperability. + +The encoding of DNS names in the DNS protocol is limited +to 255 characters. Since the encoding consists of labels +prefixed by a length bytes and there is a trailing NULL +byte, only 253 characters can appear in the textual dotted +notation. + +The description clause of schema nodes using the domain-name +type MUST describe when and how these names are resolved to +IP addresses. Note that the resolution of a domain-name value +may require to query multiple DNS records (e.g., A for IPv4 +and AAAA for IPv6). The order of the resolution process and +which DNS record takes precedence can either be defined +explicitely or it may depend on the configuration of the +resolver. + +Domain-name values use the US-ASCII encoding. Their canonical +format uses lowercase US-ASCII characters. Internationalized +domain names MUST be encoded in punycode as described in RFC +3492 + +Length: 1-253 + ## `configure authority router description` A human-readable string that allows administrators to describe this configuration. @@ -3303,6 +4968,12 @@ configure authority router description [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + ## `configure authority router dhcp-server-generated-address-pool` The address pool for KNI network-interfaces generated for dhcp-servers. @@ -3319,6 +4990,24 @@ configure authority router dhcp-server-generated-address-pool [] | ---- | ----------- | | ipv4-prefix | The value to set for this field | +#### Description + +Default: 169.254.130.0/24 + +##### ipv4-prefix (string) + +The ipv4-prefix type represents an IPv4 address prefix. +The prefix length is given by the number following the +slash character and must be less than or equal to 32. + +A prefix length value of n corresponds to an IP address +mask that has n contiguous 1-bits from the most +significant bit (MSB) and all other bits set to 0. + +The canonical format of an IPv4 prefix has all bits of +the IPv4 address set to zero that are not part of the +IPv4 prefix. + ## `configure authority router district-settings` Per-district settings for the router. @@ -3361,6 +5050,15 @@ configure authority router district-settings district-name [] | ---- | ----------- | | district-name | The value to set for this field | +#### Description + +##### district-name (string) + +A text value. + +Must contain only alphanumeric characters or any of the following: _ - +Length: 0-63 + ## `configure authority router district-settings step-peer-path-sla-metrics-advertisement` STEP advertisement settings for peer path SLA metrics. @@ -3396,6 +5094,14 @@ configure authority router district-settings step-peer-path-sla-metrics-advertis Units: seconds +Default: 30 + +##### uint32 + +An unsigned 32-bit integer. + +Range: 0-86400 + ## `configure authority router district-settings step-peer-path-sla-metrics-advertisement update-burst-size` Limit on the number of peer path SLA metric value updates advertised in STEP at the minimum (burst) update interval. @@ -3412,6 +5118,16 @@ configure authority router district-settings step-peer-path-sla-metrics-advertis | ---- | ----------- | | uint8 | The value to set for this field | +#### Description + +Default: 2 + +##### uint8 + +An unsigned 8-bit integer. + +Range: 1-100 + ## `configure authority router district-settings step-peer-path-sla-metrics-advertisement update-rate-limit` Rate limit interval in between updating peer path SLA metric values advertised in STEP @@ -3432,6 +5148,14 @@ configure authority router district-settings step-peer-path-sla-metrics-advertis Units: seconds +Default: 180 + +##### uint32 + +An unsigned 32-bit integer. + +Range: 1-86400 + ## `configure authority router dns-config` Configure Dns Config @@ -3475,6 +5199,38 @@ configure authority router dns-config address [] | ---- | ----------- | | ip-address | Value to add to this list | +#### Description + +##### ip-address (union) + +The ip-address type represents an IP address and is IP version neutral. The format of the textual representations implies the IP version. + +Must be one of the following types: + +###### (0) ipv4-address (string) + +The ipv4-address type represents an IPv4 address in dotted-quad notation. + +Must be a valid IPv4 address. + +###### (1) ipv6-address (string) + +The ipv6-address type represents an IPv6 address in full, +mixed, shortened, and shortened-mixed notation. + +The canonical format of IPv6 addresses uses the compressed +format described in RFC 4291, Section 2.2, item 2 with the +following additional rules: the :: substitution must be +applied to the longest sequence of all-zero 16-bit chunks +in an IPv6 address. If there is a tie, the first sequence +of all-zero 16-bit chunks is replaced by ::. Single +all-zero 16-bit chunks are not compressed. The canonical +format uses lowercase characters and leading zeros are +not allowed. + +Must be a valid IPv6 address. +Must be a valid IPv6 address. + ## `configure authority router dns-config mode` Mode of DNS server configuration. @@ -3491,6 +5247,16 @@ configure authority router dns-config mode [] | ---- | ----------- | | enumeration | The value to set for this field | +#### Description + +##### enumeration + +A value from a set of predefined names. + +Options: +static Static list of DNS nameservers +automatic Populate DNS nameservers from learned sources + ## `configure authority router dns-config move address` Address of servers to use for DNS queries. @@ -3546,6 +5312,12 @@ configure authority router entitlement description [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + ## `configure authority router entitlement id` Project identifier. @@ -3562,6 +5334,14 @@ configure authority router entitlement id [] | ---- | ----------- | | entitlement-project-id | The value to set for this field | +#### Description + +Default: trial + +##### entitlement-project-id (string) + +Indicates that an enclosing leaf represents the project ID for entitlement. + ## `configure authority router entitlement max-bandwidth` Purchased bandwidth for the project. @@ -3582,6 +5362,12 @@ configure authority router entitlement max-bandwidth [] Units: bits/second +Default: 0 + +##### uint64 + +An unsigned 64-bit integer. + ## `configure authority router half-open-connection-limit` A limit on half-open TCP sessions. @@ -3598,6 +5384,29 @@ configure authority router half-open-connection-limit [] | ---- | ----------- | | union | The value to set for this field | +#### Description + +Default: unlimited + +##### union + +A value that corresponds to one of its member types. + +Must be one of the following types: + +###### (0) uint32 + +An unsigned 32-bit integer. + +Range: 100-4294967295 + +###### (1) enumeration + +A value from a set of predefined names. + +Options: +unlimited No limit on this value + ## `configure authority router icmp-probe-profile` Profile for active ICMP probes for reachability-detection enforcement @@ -3645,6 +5454,12 @@ configure authority router icmp-probe-profile name [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + ## `configure authority router icmp-probe-profile number-of-attempts` Number of consecutive ICMP ping requests to be sent within the probe-duration before deciding that destination is unreachable @@ -3661,6 +5476,16 @@ configure authority router icmp-probe-profile number-of-attempts [] | ---- | ----------- | | uint8 | The value to set for this field | +#### Description + +Default: 4 + +##### uint8 + +An unsigned 8-bit integer. + +Range: 1-20 + ## `configure authority router icmp-probe-profile probe-address` Address to send ICMP ping requests to @@ -3677,6 +5502,38 @@ configure authority router icmp-probe-profile probe-address [] | ---- | ----------- | | ip-address | Value to add to this list | +#### Description + +##### ip-address (union) (required) + +The ip-address type represents an IP address and is IP version neutral. The format of the textual representations implies the IP version. + +Must be one of the following types: + +###### (0) ipv4-address (string) (required) + +The ipv4-address type represents an IPv4 address in dotted-quad notation. + +Must be a valid IPv4 address. + +###### (1) ipv6-address (string) (required) + +The ipv6-address type represents an IPv6 address in full, +mixed, shortened, and shortened-mixed notation. + +The canonical format of IPv6 addresses uses the compressed +format described in RFC 4291, Section 2.2, item 2 with the +following additional rules: the :: substitution must be +applied to the longest sequence of all-zero 16-bit chunks +in an IPv6 address. If there is a tie, the first sequence +of all-zero 16-bit chunks is replaced by ::. Single +all-zero 16-bit chunks are not compressed. The canonical +format uses lowercase characters and leading zeros are +not allowed. + +Must be a valid IPv6 address. +Must be a valid IPv6 address. + ## `configure authority router icmp-probe-profile probe-duration` Duration within which to reach the destination. Each attempt will be made in (probe-duration / number-of-attempts) interval @@ -3697,6 +5554,14 @@ configure authority router icmp-probe-profile probe-duration [] Units: seconds +Default: 1 + +##### uint8 + +An unsigned 8-bit integer. + +Range: 1-10 + ## `configure authority router icmp-probe-profile probe-failure-trigger` Control how failure to ping probe-addresses impacts state. @@ -3713,6 +5578,18 @@ configure authority router icmp-probe-profile probe-failure-trigger [] Units: seconds +Default: 10 + +##### uint32 + +An unsigned 32-bit integer. + +Range: 1-3600 + ## `configure authority router icmp-probe-profile sla-metrics` SLA-metrics requirements for ICMP ping @@ -3781,6 +5666,12 @@ configure authority router icmp-probe-profile sla-metrics latency max [] Units: milliseconds +Default: 250 + +##### uint32 + +An unsigned 32-bit integer. + ## `configure authority router icmp-probe-profile sla-metrics latency mean` The maximum acceptable mean latency based on the ping test @@ -3801,6 +5692,12 @@ configure authority router icmp-probe-profile sla-metrics latency mean [ Units: milliseconds +Default: 100 + +##### uint32 + +An unsigned 32-bit integer. + ## `configure authority router icmp-probe-profile sla-metrics max-loss` The amount of acceptable loss on the link. Determined by sending number-of-attempts ICMP requests and waiting probe-duration for response @@ -3821,6 +5718,14 @@ configure authority router icmp-probe-profile sla-metrics max-loss [ Units: percent +Default: 10 + +##### percentage (uint8) + +Integer indicating a percentage value + +Range: 0-100 + ## `configure authority router idp` Advanced IDP configuration. @@ -3851,6 +5756,16 @@ configure authority router idp bypass-enabled [] | ---- | ----------- | | boolean | The value to set for this field | +#### Description + +Default: true + +##### boolean + +A true or false value. + +Options: true or false + ## `configure authority router idp mode` IDP config management mode @@ -3867,6 +5782,20 @@ configure authority router idp mode [] | ---- | ----------- | | enumeration | The value to set for this field | +#### Description + +Default: auto + +##### enumeration + +A value from a set of predefined names. + +Options: +auto Automatically toggle IDP based on idp-policies +disabled Disable IDP +spoke Enable spoke mode for IDP +hub Enable hub mode for IDP + ## `configure authority router inter-node-security` The name of the security policy used for inter node communication between router interfaces @@ -3883,6 +5812,12 @@ configure authority router inter-node-security [] | ---- | ----------- | | security-ref | The value to set for this field | +#### Description + +##### security-ref (leafref) (required) + +This type is used by other entities that need to reference configured security policies. + ## `configure authority router location` A descriptive location for this SSR. @@ -3899,6 +5834,12 @@ configure authority router location [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + ## `configure authority router location-coordinates` The geolocation of this router in ISO 6709 format. Some examples: (1) Degrees only: +50.20361-074.00417/ (2) Degrees and minutes: +5012.22-07400.25/ or (3) Degrees, minutes, and seconds: +501213.1-0740015.1/ @@ -3915,6 +5856,14 @@ configure authority router location-coordinates [] | ---- | ----------- | | geolocation | The value to set for this field | +#### Description + +##### geolocation (string) + +Geolocation in ISO 6709 format. + +Must be a geographic coordinate in ISO-6709 format. Example: +50.1-074.1/ + ## `configure authority router maintenance-mode` When enabled, the router will be in maintenance mode and alarms related to this router will be shelved. @@ -3931,6 +5880,14 @@ configure authority router maintenance-mode [] | ---- | ----------- | | boolean | The value to set for this field | +#### Description + +##### boolean + +A true or false value. + +Options: true or false + ## `configure authority router management-service-generation` Configure Management Service Generation @@ -3962,6 +5919,16 @@ configure authority router management-service-generation proxy [] | ---- | ----------- | | boolean | The value to set for this field | +#### Description + +Default: false + +##### boolean + +A true or false value. + +Options: true or false + ## `configure authority router management-service-generation service-policy` Service policy to be used instead of auto-generated service policy. @@ -3978,6 +5945,12 @@ configure authority router management-service-generation service-policy [] #### Description -Warning: a restart is required if max-inter-node-way-points is created, modified, or deleted +Default: 50000 + +:::warning +a restart is required if max-inter-node-way-points is created, modified, or deleted +::: + +##### uint32 + +An unsigned 32-bit integer. + +Range: 50000-1000000 ## `configure authority router name` @@ -4032,7 +6027,16 @@ configure authority router name [] #### Description -Warning: a restart is required if name is created or deleted +:::warning +a restart is required if name is created or deleted +::: + +##### reserved-name-id (string) + +A string identifier which only uses alphanumerics, underscores, or dashes, and cannot exceed 63 characters, and cannot be the words 'all', 'any', or 'unknown'. + +Must contain only alphanumeric characters or any of the following: _ - +Length: 0-63 ## `configure authority router nat-pool` @@ -4105,6 +6109,53 @@ configure authority router nat-pool address-pool address [] | ---- | ----------- | | ip-prefix | The value to set for this field | +#### Description + +##### ip-prefix (union) + +The ip-prefix type represents an IP prefix and is IP version neutral. The format of the textual representations implies the IP version. + +Must be one of the following types: + +###### (0) ipv4-prefix (string) + +The ipv4-prefix type represents an IPv4 address prefix. +The prefix length is given by the number following the +slash character and must be less than or equal to 32. + +A prefix length value of n corresponds to an IP address +mask that has n contiguous 1-bits from the most +significant bit (MSB) and all other bits set to 0. + +The canonical format of an IPv4 prefix has all bits of +the IPv4 address set to zero that are not part of the +IPv4 prefix. + +###### (1) ipv6-prefix (string) + +The ipv6-prefix type represents an IPv6 address prefix. +The prefix length is given by the number following the +slash character and must be less than or equal 128. + +A prefix length value of n corresponds to an IP address +mask that has n contiguous 1-bits from the most +significant bit (MSB) and all other bits set to 0. + +The IPv6 address should have all bits that do not belong +to the prefix set to zero. + +The canonical format of an IPv6 prefix has all bits of +the IPv6 address set to zero that are not part of the +IPv6 prefix. Furthermore, IPv6 address is represented +in the compressed format described in RFC 4291, Section +2.2, item 2 with the following additional rules: the :: +substitution must be applied to the longest sequence of +all-zero 16-bit chunks in an IPv6 address. If there is +a tie, the first sequence of all-zero 16-bit chunks is +replaced by ::. Single all-zero 16-bit chunks are not +compressed. The canonical format uses lowercase +characters and leading zeros are not allowed. + ## `configure authority router nat-pool address-pool pool-type` Type of NAT pool @@ -4121,6 +6172,18 @@ configure authority router nat-pool address-pool pool-type [] | ---- | ----------- | | enumeration | The value to set for this field | +#### Description + +Default: static + +##### enumeration + +A value from a set of predefined names. + +Options: +static Static IP assignment per endpoint +dynamic Dynamic IP & port assignment per session + ## `configure authority router nat-pool address-pool tenant-name` Tenant for which this nat pool is applied @@ -4137,6 +6200,12 @@ configure authority router nat-pool address-pool tenant-name [] | ---- | ----------- | | tenant-ref | Value to add to this list | +#### Description + +##### tenant-ref (leafref) + +This type is used by other entities that need to reference configured tenants. + ## `configure authority router nat-pool move address-pool` Defines the NAT prefix and ports in the pool. @@ -4171,6 +6240,15 @@ configure authority router nat-pool name [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + +Must contain only alphanumeric characters or any of the following: _ - +Length: 0-63 + ## `configure authority router node` List of one or two SSR software instances, comprising an SSR. @@ -4233,6 +6311,14 @@ configure authority router node asset-id [] | ---- | ----------- | | asset-id | The value to set for this field | +#### Description + +##### asset-id (string) + +A unique identifier of an SSR node. + +Must not contain repeating, leading, or ending '_' character + ## `configure authority router node asset-validation-enabled` Validate that the asset is suitable to run SSR. @@ -4249,6 +6335,16 @@ configure authority router node asset-validation-enabled [] | ---- | ----------- | | boolean | The value to set for this field | +#### Description + +Default: true + +##### boolean + +A true or false value. + +Options: true or false + ## `configure authority router node description` A description about the node. @@ -4265,6 +6361,12 @@ configure authority router node description [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + ## `configure authority router node device-interface` List of physical or virtual interfaces in the node. @@ -4317,7 +6419,7 @@ configure authority router node device-interface | [`traffic-engineering`](#configure-authority-router-node-device-interface-traffic-engineering) | Configure Traffic Engineering | | [`type`](#configure-authority-router-node-device-interface-type) | Type of interface. | | [`vmbus-uuid`](#configure-authority-router-node-device-interface-vmbus-uuid) | The VMBus UUID of the network device. Hyper-V Environment only. Only relevant if type is ethernet. | -| [`vrrp`](#configure-authority-router-node-device-interface-vrrp) | Parameters for Interface Redundancy using Virtual Router Redundancy Protocol (VRRP) like protocol. | +| [`vrrp`](#configure-authority-router-node-device-interface-vrrp) | Configure Vrrp | ## `configure authority router node device-interface bond-settings` @@ -4348,6 +6450,16 @@ configure authority router node device-interface bond-settings lacp-enable [] | ---- | ----------- | | bridge-name | The value to set for this field | +#### Description + +##### bridge-name (string) + +A string identifier for bridge-name which only uses alphanumerics, underscores, or dashes, and cannot exceed 15 characters. + +Must contain only alphanumeric characters, start with a alphabet and can contain any of the following: _ - +Length: 0-15 + ## `configure authority router node device-interface capture-filter` Filter to be used when matching packets on this device interface. Uses Berkeley Packet Filter (BPF) syntax. @@ -4380,6 +6501,12 @@ configure authority router node device-interface capture-filter [] | ---- | ----------- | | string | Value to add to this list | +#### Description + +##### string + +A text value. + ## `configure authority router node device-interface description` A description of the device-interface. @@ -4396,6 +6523,12 @@ configure authority router node device-interface description [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + ## `configure authority router node device-interface enabled` Whether this interface is administratively enabled. @@ -4412,6 +6545,16 @@ configure authority router node device-interface enabled [] | ---- | ----------- | | boolean | The value to set for this field | +#### Description + +Default: true + +##### boolean + +A true or false value. + +Options: true or false + ## `configure authority router node device-interface forwarding` Whether this interface is used for forwarding traffic. @@ -4428,6 +6571,16 @@ configure authority router node device-interface forwarding [] | ---- | ----------- | | boolean | The value to set for this field | +#### Description + +Default: true + +##### boolean + +A true or false value. + +Options: true or false + ## `configure authority router node device-interface interface-name` The interface name associated with the OS network device. @@ -4444,6 +6597,12 @@ configure authority router node device-interface interface-name [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string + +A text value. + ## `configure authority router node device-interface link-settings` Ethernet link settings on the interface @@ -4460,6 +6619,21 @@ configure authority router node device-interface link-settings [] | ---- | ----------- | | enumeration | The value to set for this field | +#### Description + +Default: auto + +##### enumeration + +A value from a set of predefined names. + +Options: +auto Use auto-negotation for the Ethernet link +10Mbps-half Force the Ethernet link to 10 Mbps half duplex +10Mbps-full Force the Ethernet link to 10 Mbps full duplex +100Mbps-half Force the Ethernet link to 100 Mbps half duplex +100Mbps-full Force the Ethernet link to 100 Mbps full duplex + ## `configure authority router node device-interface lldp` Link Layer Description Protocol settings @@ -4496,6 +6670,14 @@ configure authority router node device-interface lldp advertisement-interval [] | ---- | ----------- | | boolean | The value to set for this field | +#### Description + +Default: true + +##### boolean + +A true or false value. + +Options: true or false + ## `configure authority router node device-interface lldp hold-multiplier` The multiplier to apply to the advertisement-interval when setting the LLDP TTL. @@ -4528,6 +6720,16 @@ configure authority router node device-interface lldp hold-multiplier [] | ---- | ----------- | | uint8 | The value to set for this field | +#### Description + +Default: 4 + +##### uint8 + +An unsigned 8-bit integer. + +Range: 2-10 + ## `configure authority router node device-interface lldp mode` The mode in which LLDP operates on the interface @@ -4546,7 +6748,20 @@ configure authority router node device-interface lldp mode [] #### Description -Warning: 'mode' is deprecated and will be removed in a future software version +Default: disabled + +:::warning +&#x27;mode&#x27; is deprecated and will be removed in a future software version +::: + +##### enumeration + +A value from a set of predefined names. + +Options: +disabled Disable LLDP +receive-only Receive and process incoming LLDP packets +enabled Enable sending and receiving LLDP packets ## `configure authority router node device-interface load-balancing` @@ -4582,6 +6797,14 @@ configure authority router node device-interface load-balancing utilization-high Units: percent +Default: 100 + +##### percentage (uint8) + +Integer indicating a percentage value + +Range: 0-100 + ## `configure authority router node device-interface load-balancing utilization-low-water-mark` Percentage of allowed bandwidth utilization below which this interface will be reconsidered for load balancing. @@ -4602,6 +6825,14 @@ configure authority router node device-interface load-balancing utilization-low- Units: percent +Default: 80 + +##### percentage (uint8) + +Integer indicating a percentage value + +Range: 0-100 + ## `configure authority router node device-interface lte` Configure Lte @@ -4633,6 +6864,12 @@ configure authority router node device-interface lte apn-name [] | ---- | ----------- | | string | The value to set for this field | +#### Description + +##### string (required) + +A text value. + ## `configure authority router node device-interface lte authentication` Configure Authentication @@ -4664,6 +6901,16 @@ configure authority router node device-interface lte authentication authenticati | ---- | ----------- | | enumeration | The value to set for this field | +#### Description + +##### enumeration (required) + +A value from a set of predefined names. + +Options: +chap Challenge-Handshake Authentication Protocol. +pap Password Authentication Protocol. + ## `configure authority router node device-interface lte authentication password` Password required to connect to the LTE network. @@ -4680,6 +6927,12 @@ configure authority router node device-interface lte authentication password [