Contrail vRouter - История изменений

Sirmax: /* flow -l */

2025-08-21T07:48:27Z

flow -l

← Предыдущая		Версия 07:48, 21 августа 2025
Строка 151:		Строка 151:

	<PRE>		<PRE>
−	# flow –l	+	# flow -l
	Flow table		Flow table
	Index Source:Port Destination:Port Proto(V)		Index Source:Port Destination:Port Proto(V)

2025-08-18T13:09:24Z

2025-08-18T13:07:16Z

2025-02-27T10:57:52Z

dpdkinfo Command

← Предыдущая		Версия 10:57, 27 февраля 2025
Строка 697:		Строка 697:
	=dpdkinfo Command=		=dpdkinfo Command=

		+
−	In Contrail Networking Release 2008, the dpdkinfo command enables you to see the details of the internal data structures of a DPDK enabled vRouter.

	dpdkinfo Options		dpdkinfo Options

2025-02-27T10:57:18Z

Tunnel

← Предыдущая		Версия 10:57, 27 февраля 2025
Строка 603:		Строка 603:
	There are different types of tunnel next hops, based on the type of tunnels used. <BR>		There are different types of tunnel next hops, based on the type of tunnels used. <BR>
	vRouter supports two main tunnel types for Layer 3 traffic:		vRouter supports two main tunnel types for Layer 3 traffic:
−	* MPLSoGRE	+	* <code>MPLSoGRE</code>
−	* MPLSoUDP.	+	* <code>MPLSoUDP</code>

	For Layer 2 traffic, a VXLAN tunnel is used.<BR>		For Layer 2 traffic, a VXLAN tunnel is used.<BR>

2025-02-27T10:56:36Z

nh Command

← Предыдущая		Версия 10:56, 27 февраля 2025
Строка 571:		Строка 571:
	<BR>		<BR>
	Есть различные типы Next-hop		Есть различные типы Next-hop
		+
		+
		+	TODO: По всем или хотя бы по некоторым - надо примеры!!!!!
	==<code>Receive</code>==		==<code>Receive</code>==

2025-02-27T10:56:02Z

Vxlan

← Предыдущая		Версия 10:56, 27 февраля 2025
Строка 627:		Строка 627:
	==Vxlan==		==Vxlan==

−	A VXLAN tunnel is used for Layer 2 traffic~~. A typical tunnel next hop indicates the kind of tunnel, the rewrite information, the outgoing interface, and the source and destination server IPs~~.	+	A VXLAN tunnel is used for Layer 2 traffic.
		+	<BR>
		+	A typical tunnel next hop indicates the kind of tunnel, the rewrite information, the outgoing interface, and the source and destination server IPs.

	==<code>nh --list</code>==		==<code>nh --list</code>==

2025-02-27T10:55:42Z

Composite

← Предыдущая		Версия 10:55, 27 февраля 2025
Строка 622:		Строка 622:
	==Composite==		==Composite==

−	Groups a set of next hops, called component next hops or sub next hops. ~~Typically used when multi-destination distribution is needed, for example for multicast, ECMP, and so on.~~	+	Groups a set of next hops, called component next hops or sub next hops. <BR>
		+	Typically used when multi-destination distribution is needed, for example for multicast, ECMP, and so on.

	==Vxlan==		==Vxlan==

2025-02-27T10:55:09Z

Tunnel

@@ Строка 597: / Строка 597: @@
 ==Tunnel==
-Encapsulates VM traffic in a tunnel and sends it to the server that hosts the destination VM. There are different types of tunnel next hops, based on the type of tunnels used. vRouter supports two main tunnel types for Layer 3 traffic: MPLSoGRE and MPLSoUDP. For Layer 2 traffic, a VXLAN tunnel is used. A typical tunnel next hop indicates the kind of tunnel, the rewrite information, the outgoing interface, and the source and destination server IPs.
+Encapsulates VM traffic in a tunnel and sends it to the server that hosts the destination VM.<BR>
 ==Discard==

2025-02-27T10:53:02Z

Encap (Interface)

← Предыдущая		Версия 10:53, 27 февраля 2025
Строка 587:		Строка 587:
	==<code>Encap (Interface)</code>==		==<code>Encap (Interface)</code>==

−	Used only to determine the outgoing interface and the Layer 2 information.	+	Used only to determine the outgoing interface and the Layer 2 information. <BR>
	<BR>		<BR>
−	As an example, when two VMs on the same server communicate with each other,	+	As an example, when two VMs on the same server communicate with each other, <BR>
−	the routes for each of them point to an <code>encap next hop</code>,	+	the routes for each of them point to an <code>encap next hop</code>, <BR>
−	because the only information needed is the Layer 2 information to send the packet to the tap interface of the destination VM.	+	because the only information needed is the Layer 2 information to send the packet to the tap interface of the destination VM. <BR>
	<BR>		<BR>
	A packet destined for a VM hosted on one server from a VM on a different server will also hit an encap next hop, after tunnel processing.		A packet destined for a VM hosted on one server from a VM on a different server will also hit an encap next hop, after tunnel processing.