Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update documentation for lnw_v3 and grpc-addr option #18

Merged
merged 4 commits into from
Apr 17, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions docs/apps/lnw/es2k/es2k-lnw-overlay-ipv6.md
Original file line number Diff line number Diff line change
Expand Up @@ -159,6 +159,17 @@ ovs-vsctl set Open_vSwitch . other_config:n-handler-threads=1
ovs-vsctl show
```

Note: If you are using a P4Runtime gRPC server address other than localhost, specify the gRPC server address when starting ovs-vswitchd using the `--grpc-addr` option.
This address will be used by ovs-p4rt client for communication with P4Runtime gRPC server.

Example:
If infrap4d server is started on address 5.5.5.5 using `$P4CP_INSTALL/sbin/infrap4d --nodetach --local_stratum_url="5.5.5.5:9559" --external_stratum_urls="5.5.5.5:9339,5.5.5.5:9559"`, then start ovs-vswitchd as follows:

```bash
ovs-vswitchd --pidfile --detach --mlockall \
--log-file=/tmp/logs/ovs-vswitchd.log --grpc-addr="5.5.5.5"
```

### Create Overlay network

Option 1: Create VFs on HOST and spawn VMs on top of those VFs.
Expand Down
20 changes: 20 additions & 0 deletions docs/apps/lnw/es2k/es2k-lnw-overlay-vms.md
Original file line number Diff line number Diff line change
Expand Up @@ -191,6 +191,17 @@ ovs-vsctl set Open_vSwitch . other_config:n-handler-threads=1
ovs-vsctl show
```

Note: If you are using a P4Runtime gRPC server address other than localhost, specify the gRPC server address when starting ovs-vswitchd using the `--grpc-addr` option.
This address will be used by ovs-p4rt client for communication with P4Runtime gRPC server.

Example:
If infrap4d server is started on address 5.5.5.5 using `$P4CP_INSTALL/sbin/infrap4d --nodetach --local_stratum_url="5.5.5.5:9559" --external_stratum_urls="5.5.5.5:9339,5.5.5.5:9559"`, then start ovs-vswitchd as follows:

```bash
ovs-vswitchd --pidfile --detach --mlockall \
--log-file=/tmp/logs/ovs-vswitchd.log --grpc-addr="5.5.5.5"
```

### Create Overlay network

Option 1: Create VFs on HOST and spawn VMs on top of those VFs.
Expand Down Expand Up @@ -344,11 +355,20 @@ Example:

For TCAM entry configure LPM LUT table

- For Linux Networking v2

```bash
p4rt-ctl add-entry br0 linux_networking_control.ipv4_lpm_root_lut \
"user_meta.cmeta.bit32_zeros=4/255.255.255.255,priority=65535,action=linux_networking_control.ipv4_lpm_root_lut_action(0)"
```

- For Linux Networking v3

```bash
p4rt-ctl add-entry br0 linux_networking_control.ipv4_lpm_root_lut \
"user_meta.cmeta.bit16_zeros=4/65535,priority=2048,action=linux_networking_control.ipv4_lpm_root_lut_action(0)"
```

Create a dummy LAG bypass table for all 8 hash indexes

- For Linux Networking v2
Expand Down
20 changes: 20 additions & 0 deletions docs/apps/lnw/es2k/es2k-lnw-underlay-ecmp.md
Original file line number Diff line number Diff line change
Expand Up @@ -187,6 +187,17 @@ ovs-vsctl set Open_vSwitch . other_config:n-handler-threads=1
ovs-vsctl show
```

Note: If you are using a P4Runtime gRPC server address other than localhost, specify the gRPC server address when starting ovs-vswitchd using the `--grpc-addr` option.
This address will be used by ovs-p4rt client for communication with P4Runtime gRPC server.

Example:
If infrap4d server is started on address 5.5.5.5 using `$P4CP_INSTALL/sbin/infrap4d --nodetach --local_stratum_url="5.5.5.5:9559" --external_stratum_urls="5.5.5.5:9339,5.5.5.5:9559"`, then start ovs-vswitchd as follows:

```bash
ovs-vswitchd --pidfile --detach --mlockall \
--log-file=/tmp/logs/ovs-vswitchd.log --grpc-addr="5.5.5.5"
```

### Create Overlay network

Option 1: Create VFs on HOST and spawn VMs on top of those VFs.
Expand Down Expand Up @@ -339,11 +350,20 @@ Example:

For TCAM entry configure LPM LUT table

- For Linux Networking v2

```bash
p4rt-ctl add-entry br0 linux_networking_control.ipv4_lpm_root_lut \
"user_meta.cmeta.bit32_zeros=4/255.255.255.255,priority=65535,action=linux_networking_control.ipv4_lpm_root_lut_action(0)"
```

- For Linux Networking v3

```bash
p4rt-ctl add-entry br0 linux_networking_control.ipv4_lpm_root_lut \
"user_meta.cmeta.bit16_zeros=4/65535,priority=2048,action=linux_networking_control.ipv4_lpm_root_lut_action(0)"
```

Create a dummy LAG bypass table for all 8 hash indexes

- For Linux Networking v2
Expand Down
20 changes: 20 additions & 0 deletions docs/apps/lnw/es2k/es2k-lnw-underlay-frr.md
Original file line number Diff line number Diff line change
Expand Up @@ -185,6 +185,17 @@ ovs-vsctl set Open_vSwitch . other_config:n-handler-threads=1
ovs-vsctl show
```

Note: If you are using a P4Runtime gRPC server address other than localhost, specify the gRPC server address when starting ovs-vswitchd using the `--grpc-addr` option.
This address will be used by ovs-p4rt client for communication with P4Runtime gRPC server.

Example:
If infrap4d server is started on address 5.5.5.5 using `$P4CP_INSTALL/sbin/infrap4d --nodetach --local_stratum_url="5.5.5.5:9559" --external_stratum_urls="5.5.5.5:9339,5.5.5.5:9559"`, then start ovs-vswitchd as follows:

```bash
ovs-vswitchd --pidfile --detach --mlockall \
--log-file=/tmp/logs/ovs-vswitchd.log --grpc-addr="5.5.5.5"
```

### Create Overlay network

Option 1: Create VFs on HOST and spawn VMs on top of those VFs.
Expand Down Expand Up @@ -337,11 +348,20 @@ Example:

For TCAM entry configure LPM LUT table

- For Linux NEtworking v2

```bash
p4rt-ctl add-entry br0 linux_networking_control.ipv4_lpm_root_lut \
"user_meta.cmeta.bit32_zeros=4/255.255.255.255,priority=65535,action=linux_networking_control.ipv4_lpm_root_lut_action(0)"
```

- For Linux Networking v3

```bash
p4rt-ctl add-entry br0 linux_networking_control.ipv4_lpm_root_lut \
"user_meta.cmeta.bit16_zeros=4/65535,priority=2048,action=linux_networking_control.ipv4_lpm_root_lut_action(0)"
```

Create a dummy LAG bypass table for all 8 hash indexes

- For Linux Networking v2
Expand Down
20 changes: 20 additions & 0 deletions docs/apps/lnw/es2k/es2k-lnw-underlay-lag.md
Original file line number Diff line number Diff line change
Expand Up @@ -188,6 +188,17 @@ ovs-vsctl set Open_vSwitch . other_config:n-handler-threads=1
ovs-vsctl show
```

Note: If you are using a P4Runtime gRPC server address other than localhost, specify the gRPC server address when starting ovs-vswitchd using the `--grpc-addr` option.
This address will be used by ovs-p4rt client for communication with P4Runtime gRPC server.

Example:
If infrap4d server is started on address 5.5.5.5 using `$P4CP_INSTALL/sbin/infrap4d --nodetach --local_stratum_url="5.5.5.5:9559" --external_stratum_urls="5.5.5.5:9339,5.5.5.5:9559"`, then start ovs-vswitchd as follows:

```bash
ovs-vswitchd --pidfile --detach --mlockall \
--log-file=/tmp/logs/ovs-vswitchd.log --grpc-addr="5.5.5.5"
```

### Create Overlay network

Option 1: Create VFs on HOST and spawn VMs on top of those VFs.
Expand Down Expand Up @@ -340,11 +351,20 @@ Example:

For TCAM entry configure LPM LUT table

- For Linux Networking v2

```bash
p4rt-ctl add-entry br0 linux_networking_control.ipv4_lpm_root_lut \
"user_meta.cmeta.bit32_zeros=4/255.255.255.255,priority=65535,action=linux_networking_control.ipv4_lpm_root_lut_action(0)"
```

- For Linux Networking v3

```bash
p4rt-ctl add-entry br0 linux_networking_control.ipv4_lpm_root_lut \
"user_meta.cmeta.bit16_zeros=4/65535,priority=2048,action=linux_networking_control.ipv4_lpm_root_lut_action(0)"
```

Create a map between source port and bridge ID 0.

```bash
Expand Down