Skip to content

Commit 6d3cd0b

Browse files
stu-clarkstu-clark
committed
Merge branch 'stage' of https://github.com/CumulusNetworks/docs into stage
2 parents 911b4e4 + 31e3d29 commit 6d3cd0b

3 files changed

Lines changed: 1 addition & 158 deletions

File tree

‎content/cumulus-linux-517/Network-Virtualization/Ethernet-Virtual-Private-Network-EVPN/EVPN-Enhancements.md‎

Lines changed: 1 addition & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -300,41 +300,12 @@ leaf01#
300300
{{< /tab >}}
301301
{{< /tabs >}}
302302

303-
You can configure route maps to match unreachability EVPN route types with the `nv set router policy route-map <route-map-id> rule 10 match evpn-route-type prefix-unreachability` command. You can also set communities, extended communities (where supported), MED, local-pref, AS-path manipulation, origin, and other generic BGP set actions that apply to other EVPN route types to unreachability EVPN route types.
303+
You can configure route maps to match unreachability EVPN route types with the NVUE `nv set router policy route-map <route-map-id> rule 10 match evpn-route-type prefix-unreachability` command or the vtysh `match evpn route-type prefix-unreachability` command. You can also set communities, extended communities (where supported), MED, local-pref, AS-path manipulation, origin, and other generic BGP set actions that apply to other EVPN route types to unreachability EVPN route types.
304304

305305
{{%notice note%}}
306306
Setting the gateway overlay for unreachability EVPN prefixes is not supported.
307307
{{%/notice%}}
308308

309-
The following example configures a route map that sets the BGP AS path exclude attribute to 2 for unreachability EVPN route types:
310-
311-
{{< tabs "TabID311 ">}}
312-
{{< tab "NVUE Commands ">}}
313-
314-
```
315-
cumulus@leaf01:mgmt:~$ nv set router policy route-map MATCH_EVPN_UNREACH rule 10 match evpn-route-type prefix-unreachability
316-
cumulus@leaf01:mgmt:~$ nv set router policy route-map MATCH_EVPN_UNREACH rule 10 set as-path-exclude 2
317-
cumulus@leaf01:mgmt:~$ nv set router policy route-map MATCH_EVPN_UNREACH rule 10 action permit
318-
cumulus@leaf01:mgmt:~$ nv config apply
319-
```
320-
321-
{{< /tab >}}
322-
{{< tab "vtysh Commands ">}}
323-
324-
```
325-
cumulus@leaf01:mgmt:~$ sudo vtysh
326-
leaf01# configure terminal
327-
leaf01(config)# route-map MATCH_EVPN_UNREACH permit 10
328-
leaf01(config-route-map)# match evpn route-type prefix-unreachability
329-
leaf01(config-route-map)# set as-path exclude 2
330-
leaf01(config-route-map)# end
331-
leaf01# write memory
332-
leaf01# exit
333-
```
334-
335-
{{< /tab >}}
336-
{{< /tabs >}}
337-
338309
### Considerations
339310

340311
- EVPN Multihoming is not supported with unreachability in disjoined planes.

‎content/cumulus-netq-24/More-Documents/rn.md‎

Lines changed: 0 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -26,24 +26,3 @@ pdfhidden: True
2626
| 2545685 | NetQ UI: On medium- and large-sized Scheduled Trace cards, the destination field does not accept IPv6 addresses. They are reported as invalid destination IP addresses. The source field on these cards accepts IPv6 addresses. | 2.3.1-2.4.0 | |
2727
| 2545119 | NetQ UI and CLI: EVPN failure details do not appear in the full screen EVPN Service card or when running 'netq show validation results type evpn' in the NetQ CLI, even though the EVPN failure is seen on validation. | 2.3.1-2.4.0 | |
2828

29-
## 2.4.0 Release Notes
30-
### Open Issues in 2.4.0
31-
32-
| Issue ID | Description | Affects | Fixed |
33-
|--- |--- |--- |--- |
34-
| 2551641 | Infra: NetQ VM installation fails if the designated disk size is greater than 2TB. To work around this issue, specify the disk for cloud deployments to be between 256GB and 2TB SSD, and for on-premises deployments to be between 32 GB and 2TB. | 2.4.0-3.1.1 | 3.2.0-3.3.1|
35-
| 2549246, 2549315, 2549518, 2549315 | NetQ UI: Snapshot comparison cards may not render correctly after navigating away from a workbench and then returning to it. If you are viewing the Snapshot comparison card(s) on a custom workbench, refresh the page to reload the data. If you are viewing it on the Cumulus Default workbench, after refreshing the page you must recreate the comparison(s). | 2.4.0-3.2.1 | 3.3.0-3.3.1|
36-
| 2548560 | When a switch or host reports its memory size in GB rather than MB, the NetQ Agent cannot parse the information and thus fails to register with the NetQ server. Contact customer support if you run into this issue. | 2.4.0-2.4.1 | 3.0.0-3.3.1|
37-
| 2546397 | NetQ Admin UI: When installing NetQ with the Admin UI, the job status is presented to show progress. However, when an error is encountered while running individual tasks, the UI may feel unresponsive. Please wait for at least 15 minutes to receive a response. | 2.4.0 | 2.4.1|
38-
| 2545685 | NetQ UI: On medium- and large-sized Scheduled Trace cards, the destination field does not accept IPv6 addresses. They are reported as invalid destination IP addresses. The source field on these cards accepts IPv6 addresses. | 2.3.1-2.4.0 | 2.4.1|
39-
| 2545119 | NetQ UI and CLI: EVPN failure details do not appear in the full screen EVPN Service card or when running 'netq show validation results type evpn' in the NetQ CLI, even though the EVPN failure is seen on validation. | 2.3.1-2.4.0 | 2.4.1|
40-
41-
### Fixed Issues in 2.4.0
42-
| Issue ID | Description | Affects |
43-
|--- |--- |--- |
44-
| 2545622 | NetQ UI: This only applies to the NetQ 2.3.1 UI installed on the NetQ Server or NetQ Appliance in on-premises deployments. Cloud deployments are not impacted by this bug. Trace results are not shown after running an on-demand or scheduled trace request in the NetQ UI. The medium Trace Result cards are blank whether the trace was successful or not. The full-screen Trace Result card and the NetQ CLI show the results correctly.<br />To work around this issue, apply the update to your existing 2.3.1 build as follows:<br /><br />* Download the update tarball.<br />If your server or appliance has internet access, use <code>wget</code> to perform the download. Be sure to use your download directory in place of _/home/cumulus_ indicated in this example.<br /><pre><br />cumulus&#64;opta:~$ wget http://netq-shared.s3-us-west-2.amazonaws.com/NetQ-2.3.1.1.tgz -O /home/cumulus/NetQ-2.3.1.1.tgz<br /></pre><br />If your server or appliance is air-gapped, first download the tarball and then, as a root user, copy it to the appropriate directory on your server or appliance.<br /><pre><br />root&#64;opta:~# cd /mnt/swinstalls/<br />root&#64;opta:/mnt/swinstalls# cp /home/cumulus/NetQ-2.3.1.1.tgz ./ <br /></pre><br />* Extract the script.<br /><pre><br />cumulus&#64;opta:~$ tar -xvzf /home/cumulus/NetQ-2.3.1.1.tgz update-app.sh<br /></pre><br />* Run the script. On completion, a new GUI container will be running and the card will display the trace result.<br /><pre><br />cumulus&#64;opta:~$ ./update-app.sh /home/cumulus/NetQ-2.3.1.1.tgz<br />Loading the new app<br />e9b2c1648ab5: Loading layer &#91;==================================================>&#93; 2.048kB/2.048kB<br />e7acfa3378f4: Loading layer &#91;==================================================>&#93; 20.59MB/20.59MB<br />...<br />Loaded image: 498186410471.dkr.ecr.us-west-2.amazonaws.com/netq-gui:2.3.1<br />Restarting the app with new image<br />deployment.extensions/netq-gui-deploy scaled<br />Sleeping for 15 seconds<br />Confirming the app is running with new image<br />Found the container running with new image.<br /></pre><br />* Close and reopen the NetQ UI to run the new image. *Note*: You may need to press Cmd+Shift+R to fully clear the cache on the Chrome browser. | | |
45-
| 2545549 | When you upgrade both the NetQ Agent and the NetQ Apps in on-premises deployments, a temporary increase in event messages is seen. They are the result of collecting package information from the NetQ Agent on each monitored node. This only happens on initial upgrade and there is no functional impact to the operation of the NetQ software. | 2.3.1 | |
46-
| 2545296, 2545925 | NetQ UI: When a warning occurs during a VXLAN validation, the small, medium, and large VXLAN Scheduled Validation Result cards incorrectly display the text of the warning instead of the Failed icon and text. | 2.3.1 | |
47-
| 2545113 | NetQ UI: When troubleshooting a user may wish to disable auto-refresh so that the data is not changed in the middle of analysis. If auto-refresh causes any state loss on the card of interest, pause the auto-refresh feature by clicking the Refresh icon in the workbench header. When finished with the analysis, re-enable the auto-refresh feature by clicking the Refresh icon again to ensure the card data is always the most recent available. | 2.3.1 | |
48-
| 2543333 | NetQ UI: Trace configuration information is not captured until the trace has been run at least once, leaving the large Trace Result card blank. The schedule information remains missing even after the trace has been run. | 2.2.2-2.3.1 | |
49-

‎content/cumulus-netq-24/rn.xml‎

Lines changed: 0 additions & 107 deletions
Original file line numberDiff line numberDiff line change
@@ -53,111 +53,4 @@
5353
<td>2.3.1-2.4.0</td>
5454
</tr>
5555
</table>
56-
<table name="Open Issues in 2.4.0">
57-
<tr>
58-
<th> Issue ID </th>
59-
<th> Description </th>
60-
<th> Affects </th>
61-
<th> Fixed </th>
62-
</tr>
63-
<tr>
64-
<td>2551641</td>
65-
<td>Infra: NetQ VM installation fails if the designated disk size is greater than 2TB. To work around this issue, specify the disk for cloud deployments to be between 256GB and 2TB SSD, and for on-premises deployments to be between 32 GB and 2TB.</td>
66-
<td>2.4.0-3.1.1</td>
67-
<td>3.2.0-3.3.1</td>
68-
</tr>
69-
<tr>
70-
<td>2549246, 2549315, 2549518, 2549315</td>
71-
<td>NetQ UI: Snapshot comparison cards may not render correctly after navigating away from a workbench and then returning to it. If you are viewing the Snapshot comparison card(s) on a custom workbench, refresh the page to reload the data. If you are viewing it on the Cumulus Default workbench, after refreshing the page you must recreate the comparison(s).</td>
72-
<td>2.4.0-3.2.1</td>
73-
<td>3.3.0-3.3.1</td>
74-
</tr>
75-
<tr>
76-
<td>2548560</td>
77-
<td>When a switch or host reports its memory size in GB rather than MB, the NetQ Agent cannot parse the information and thus fails to register with the NetQ server. Contact customer support if you run into this issue.</td>
78-
<td>2.4.0-2.4.1</td>
79-
<td>3.0.0-3.3.1</td>
80-
</tr>
81-
<tr>
82-
<td>2546397</td>
83-
<td>NetQ Admin UI: When installing NetQ with the Admin UI, the job status is presented to show progress. However, when an error is encountered while running individual tasks, the UI may feel unresponsive. Please wait for at least 15 minutes to receive a response.</td>
84-
<td>2.4.0</td>
85-
<td>2.4.1</td>
86-
</tr>
87-
<tr>
88-
<td>2545685</td>
89-
<td>NetQ UI: On medium- and large-sized Scheduled Trace cards, the destination field does not accept IPv6 addresses. They are reported as invalid destination IP addresses. The source field on these cards accepts IPv6 addresses.</td>
90-
<td>2.3.1-2.4.0</td>
91-
<td>2.4.1</td>
92-
</tr>
93-
<tr>
94-
<td>2545119</td>
95-
<td>NetQ UI and CLI: EVPN failure details do not appear in the full screen EVPN Service card or when running &apos;netq show validation results type evpn&apos; in the NetQ CLI, even though the EVPN failure is seen on validation.</td>
96-
<td>2.3.1-2.4.0</td>
97-
<td>2.4.1</td>
98-
</tr>
99-
</table>
100-
<table name="Fixed Issues in 2.4.0">
101-
<tr>
102-
<th> Issue ID </th>
103-
<th> Description </th>
104-
<th> Affects </th>
105-
</tr>
106-
<tr>
107-
<td>2545622</td>
108-
<td>NetQ UI: This only applies to the NetQ 2.3.1 UI installed on the NetQ Server or NetQ Appliance in on-premises deployments. Cloud deployments are not impacted by this bug. Trace results are not shown after running an on-demand or scheduled trace request in the NetQ UI. The medium Trace Result cards are blank whether the trace was successful or not. The full-screen Trace Result card and the NetQ CLI show the results correctly.
109-
To work around this issue, apply the update to your existing 2.3.1 build as follows:
110-
111-
* Download the update tarball.
112-
If your server or appliance has internet access, use {{wget}} to perform the download. Be sure to use your download directory in place of _/home/cumulus_ indicated in this example.
113-
114-
cumulus@opta:~$ wget http://netq-shared.s3-us-west-2.amazonaws.com/NetQ-2.3.1.1.tgz -O /home/cumulus/NetQ-2.3.1.1.tgz
115-
116-
If your server or appliance is air-gapped, first download the tarball and then, as a root user, copy it to the appropriate directory on your server or appliance.
117-
118-
root@opta:~# cd /mnt/swinstalls/
119-
root@opta:/mnt/swinstalls# cp /home/cumulus/NetQ-2.3.1.1.tgz ./
120-
121-
* Extract the script.
122-
123-
cumulus@opta:~$ tar -xvzf /home/cumulus/NetQ-2.3.1.1.tgz update-app.sh
124-
125-
* Run the script. On completion, a new GUI container will be running and the card will display the trace result.
126-
127-
cumulus@opta:~$ ./update-app.sh /home/cumulus/NetQ-2.3.1.1.tgz
128-
Loading the new app
129-
e9b2c1648ab5: Loading layer [==================================================&gt;] 2.048kB/2.048kB
130-
e7acfa3378f4: Loading layer [==================================================&gt;] 20.59MB/20.59MB
131-
...
132-
Loaded image: 498186410471.dkr.ecr.us-west-2.amazonaws.com/netq-gui:2.3.1
133-
Restarting the app with new image
134-
deployment.extensions/netq-gui-deploy scaled
135-
Sleeping for 15 seconds
136-
Confirming the app is running with new image
137-
Found the container running with new image.
138-
139-
* Close and reopen the NetQ UI to run the new image. *Note*: You may need to press Cmd+Shift+R to fully clear the cache on the Chrome browser.</td>
140-
<td></td>
141-
</tr>
142-
<tr>
143-
<td>2545549</td>
144-
<td>When you upgrade both the NetQ Agent and the NetQ Apps in on-premises deployments, a temporary increase in event messages is seen. They are the result of collecting package information from the NetQ Agent on each monitored node. This only happens on initial upgrade and there is no functional impact to the operation of the NetQ software.</td>
145-
<td>2.3.1</td>
146-
</tr>
147-
<tr>
148-
<td>2545296, 2545925</td>
149-
<td>NetQ UI: When a warning occurs during a VXLAN validation, the small, medium, and large VXLAN Scheduled Validation Result cards incorrectly display the text of the warning instead of the Failed icon and text.</td>
150-
<td>2.3.1</td>
151-
</tr>
152-
<tr>
153-
<td>2545113</td>
154-
<td>NetQ UI: When troubleshooting a user may wish to disable auto-refresh so that the data is not changed in the middle of analysis. If auto-refresh causes any state loss on the card of interest, pause the auto-refresh feature by clicking the Refresh icon in the workbench header. When finished with the analysis, re-enable the auto-refresh feature by clicking the Refresh icon again to ensure the card data is always the most recent available.</td>
155-
<td>2.3.1</td>
156-
</tr>
157-
<tr>
158-
<td>2543333</td>
159-
<td>NetQ UI: Trace configuration information is not captured until the trace has been run at least once, leaving the large Trace Result card blank. The schedule information remains missing even after the trace has been run.</td>
160-
<td>2.2.2-2.3.1</td>
161-
</tr>
162-
</table>
16356
</tables>

0 commit comments

Comments
 (0)