openshift · kquinn1204 · Feb 27, 2026
diff --git a/modules/nw-metallb-collecting-data.adoc b/modules/nw-metallb-collecting-data.adoc
@@ -7,21 +7,21 @@
 = About collecting MetalLB data
 
 [role="_abstract"]
-To collect diagnostic data for debugging or support analysis, execute the `oc adm must-gather` CLI command. This utility captures essential information regarding the cluster, the MetalLB configuration, and the MetalLB Operator state.
+To collect diagnostic data for debugging or support analysis, run the `oc adm must-gather` CLI command. This utility captures essential information regarding the cluster, the MetalLB configuration, and the MetalLB Operator state.
 
 The following list details features and objects related to MetalLB and the MetalLB Operator:
 
 * The namespace and child objects where you deploy the MetalLB Operator
 * All MetalLB Operator custom resource definitions (CRDs)
 
-The command collects the following information from FRRouting (FRR), which Red{nbsp} Hat uses to implement BGP and BFD:
+The command collects the following information from `FRRouting` (FRR), which Red{nbsp}Hat uses to implement BGP and BFD:
 
 * `/etc/frr/frr.conf`
 * `/etc/frr/frr.log`
 * `/etc/frr/daemons` configuration file
 * `/etc/frr/vtysh.conf`
 
-The command collects log and configuration files from the `frr` container that exists in each `speaker` pod. Additionally, the command collects the output from the following `vtysh` commands:
+The command collects log and configuration files from the `frr` container that exists in each `frr-k8s` pod in the `openshift-frr-k8s` namespace. Additionally, the command collects the output from the following `vtysh` commands:
 
 * `show running-config`
 * `show bgp ipv4`

diff --git a/modules/nw-metallb-configure-community-bgp-advertisement.adoc b/modules/nw-metallb-configure-community-bgp-advertisement.adoc
@@ -97,7 +97,7 @@ spec:
   aggregationLength: 32
   aggregationLengthV6: 128
   communities:
-    - NO_ADVERTISE <1>
+    - NO_ADVERTISE
   ipAddressPools:
     - doc-example-bgp-community
   peers:

diff --git a/modules/nw-metallb-example-addresspool.adoc b/modules/nw-metallb-example-addresspool.adoc
@@ -68,17 +68,17 @@ metadata:
   namespace: metallb-system
 spec:
   addresses:
-  - 10.0.100.0/28 <1>
+  - 10.0.100.0/28
   - 2002:2:2::1-2002:2:2::100
 # ...
 ----
-`spec.addresses`: Where `10.0.100.0/28` is the local network IP address followed by the `/28` network prefix.
+`spec.addresses`: This list defines the IP ranges that MetalLB manages. This specific example is a dual-stack configuration, meaning it provides both IPv4 and IPv6 addresses.
 
 Example of assigning IP address pools to services or namespaces::
 
 You can assign IP addresses from an `IPAddressPool` to services and namespaces that you specify.
 
-If you assign a service or namespace to more than one IP address pool, MetalLB uses an available IP address from the higher-priority IP address pool. If no IP addresses are available from the assigned IP address pools with a high priority, MetalLB uses available IP addresses from an IP address pool with lower priority or no priority. 
+If you assign a service or namespace to more than one IP address pool, MetalLB uses an available IP address from the higher-priority IP address pool. If no IP addresses are available from the assigned IP address pools with a high priority, MetalLB uses available IP addresses from an IP address pool with lower priority or no priority.
 
 [NOTE]
 ====
@@ -98,15 +98,15 @@ spec:
   serviceAllocation:
     priority: 50
     namespaces:
-      - namespace-a 
+      - namespace-a
       - namespace-b
     namespaceSelectors:
       - matchLabels:
-          zone: east 
+          zone: east
     serviceSelectors:
-      - matchExpressions: 
-        - key: security 
-          operator: In 
+      - matchExpressions:
+        - key: security
+          operator: In
           values:
           - S1
 # ...
@@ -118,4 +118,4 @@ where:
 `serviceAllocation.namespaces`:: Assign one or more namespaces to the IP address pool in a list format.
 `serviceAllocation.namespaceSelectors`:: Assign one or more namespace labels to the IP address pool by using label selectors in a list format.
 `serviceAllocation.serviceSelectors`:: Assign one or more service labels to the IP address pool by using label selectors in a list format.
- 
+
diff --git a/modules/nw-metallb-levels.adoc b/modules/nw-metallb-levels.adoc
@@ -7,7 +7,7 @@
 = FRRouting (FRR) log levels
 
 [role="_abstract"]
-To control the verbosity of network logs for troubleshooting or monitoring, refer to the FRRouting (FRR) logging levels. 
+To control the verbosity of network logs for troubleshooting or monitoring, refer to the `FRRouting` (FRR) logging levels.
 
 The following values define the severity of recorded events, so that you can use them to filter output based on operational requirements:
 
@@ -31,7 +31,7 @@ Anything that can potentially cause inconsistent `MetalLB` behaviour. Usually `M
 
 | `error`
 a|
-Any error that is fatal to the functioning of `MetalLB`. These errors usually require administrator intervention to fix.
+Any unrecoverable error in `MetalLB`. These errors usually require administrator intervention to fix.
 
 | `none`
 |Turn off all logging.

diff --git a/modules/nw-metallb-loglevel.adoc b/modules/nw-metallb-loglevel.adoc
@@ -8,7 +8,7 @@
 = Setting the MetalLB logging levels
 
 [role="_abstract"]
-To manage log verbosity for the FRRouting (FRR) container, configure the `logLevel` specification. By adjusting this setting, you can reduce log volume from the default info level or increase detail for troubleshooting MetalLB configuration issues.
+To manage log verbosity for the `FRRouting` (FRR) container, configure the `logLevel` specification. By adjusting this setting, you can reduce log volume from the default info level or increase detail for troubleshooting MetalLB configuration issues.
 
 Gain a deeper insight into MetalLB by setting the `logLevel` to `debug`.
 
@@ -19,7 +19,7 @@ Gain a deeper insight into MetalLB by setting the `logLevel` to `debug`.
 
 .Procedure
 
-. Create a file, such as `setdebugloglevel.yaml`, with content like the following example:
+. Create a file, such as `setdebugloglevel.yaml`, with content such as the following example:
 +
 [source,yaml]
 ----
@@ -87,78 +87,42 @@ I0517 09:55:06.515686      95 request.go:665] Waited for 1.026500832s due to cli
 {"caller":"service_controller.go:113","controller":"ServiceReconciler","enqueueing":"openshift-kube-controller-manager-operator/metrics","epslice":"{\"metadata\":{\"name\":\"metrics-xtsxr\",\"generateName\":\"metrics-\",\"namespace\":\"openshift-kube-controller-manager-operator\",\"uid\":\"ac6766d7-8504-492c-9d1e-4ae8897990ad\",\"resourceVersion\":\"9041\",\"generation\":4,\"creationTimestamp\":\"2022-05-17T07:16:53Z\",\"labels\":{\"app\":\"kube-controller-manager-operator\",\"endpointslice.kubernetes.io/managed-by\":\"endpointslice-controller.k8s.io\",\"kubernetes.io/service-name\":\"metrics\"},\"annotations\":{\"endpoints.kubernetes.io/last-change-trigger-time\":\"2022-05-17T07:21:34Z\"},\"ownerReferences\":[{\"apiVersion\":\"v1\",\"kind\":\"Service\",\"name\":\"metrics\",\"uid\":\"0518eed3-6152-42be-b566-0bd00a60faf8\",\"controller\":true,\"blockOwnerDeletion\":true}],\"managedFields\":[{\"manager\":\"kube-controller-manager\",\"operation\":\"Update\",\"apiVersion\":\"discovery.k8s.io/v1\",\"time\":\"2022-05-17T07:20:02Z\",\"fieldsType\":\"FieldsV1\",\"fieldsV1\":{\"f:addressType\":{},\"f:endpoints\":{},\"f:metadata\":{\"f:annotations\":{\".\":{},\"f:endpoints.kubernetes.io/last-change-trigger-time\":{}},\"f:generateName\":{},\"f:labels\":{\".\":{},\"f:app\":{},\"f:endpointslice.kubernetes.io/managed-by\":{},\"f:kubernetes.io/service-name\":{}},\"f:ownerReferences\":{\".\":{},\"k:{\\\"uid\\\":\\\"0518eed3-6152-42be-b566-0bd00a60faf8\\\"}\":{}}},\"f:ports\":{}}}]},\"addressType\":\"IPv4\",\"endpoints\":[{\"addresses\":[\"10.129.0.7\"],\"conditions\":{\"ready\":true,\"serving\":true,\"terminating\":false},\"targetRef\":{\"kind\":\"Pod\",\"namespace\":\"openshift-kube-controller-manager-operator\",\"name\":\"kube-controller-manager-operator-6b98b89ddd-8d4nf\",\"uid\":\"dd5139b8-e41c-4946-a31b-1a629314e844\",\"resourceVersion\":\"9038\"},\"nodeName\":\"ci-ln-qb8t3mb-72292-7s7rh-master-0\",\"zone\":\"us-central1-a\"}],\"ports\":[{\"name\":\"https\",\"protocol\":\"TCP\",\"port\":8443}]}","level":"debug","ts":"2022-05-17T09:55:08Z"}
 ----
 
-. View the FRR logs:
+. Display the names of the FRR-K8s pods:
 +
 [source,terminal]
 ----
-$ oc logs -n metallb-system speaker-7m4qw -c frr
+$ oc get -n openshift-frr-k8s pods
+----
++
+.Example output
+[source,text]
+----
+NAME                                      READY   STATUS    RESTARTS   AGE
+frr-k8s-bz2dn                            7/7     Running   0          4h
+frr-k8s-statuscleaner-59cf6f5d44-9wkfr   1/1     Running   0          4h
+----
+
+. View the FRR logs by specifying the `frr` container in one of the `frr-k8s` pods:
++
+[source,terminal]
+----
+$ oc logs -n openshift-frr-k8s <frr_k8s_pod_name> -c frr
 ----
 +
 .Example output
 ----
-Started watchfrr
-2022/05/17 09:55:05 ZEBRA: client 16 says hello and bids fair to announce only bgp routes vrf=0
-2022/05/17 09:55:05 ZEBRA: client 31 says hello and bids fair to announce only vnc routes vrf=0
-2022/05/17 09:55:05 ZEBRA: client 38 says hello and bids fair to announce only static routes vrf=0
-2022/05/17 09:55:05 ZEBRA: client 43 says hello and bids fair to announce only bfd routes vrf=0
-2022/05/17 09:57:25.089 BGP: Creating Default VRF, AS 64500
-2022/05/17 09:57:25.090 BGP: dup addr detect enable max_moves 5 time 180 freeze disable freeze_time 0
-2022/05/17 09:57:25.090 BGP: bgp_get: Registering BGP instance (null) to zebra
-2022/05/17 09:57:25.090 BGP: Registering VRF 0
-2022/05/17 09:57:25.091 BGP: Rx Router Id update VRF 0 Id 10.131.0.1/32
-2022/05/17 09:57:25.091 BGP: RID change : vrf VRF default(0), RTR ID 10.131.0.1
-2022/05/17 09:57:25.091 BGP: Rx Intf add VRF 0 IF br0
-2022/05/17 09:57:25.091 BGP: Rx Intf add VRF 0 IF ens4
-2022/05/17 09:57:25.091 BGP: Rx Intf address add VRF 0 IF ens4 addr 10.0.128.4/32
-2022/05/17 09:57:25.091 BGP: Rx Intf address add VRF 0 IF ens4 addr fe80::c9d:84da:4d86:5618/64
-2022/05/17 09:57:25.091 BGP: Rx Intf add VRF 0 IF lo
-2022/05/17 09:57:25.091 BGP: Rx Intf add VRF 0 IF ovs-system
-2022/05/17 09:57:25.091 BGP: Rx Intf add VRF 0 IF tun0
-2022/05/17 09:57:25.091 BGP: Rx Intf address add VRF 0 IF tun0 addr 10.131.0.1/23
-2022/05/17 09:57:25.091 BGP: Rx Intf address add VRF 0 IF tun0 addr fe80::40f1:d1ff:feb6:5322/64
-2022/05/17 09:57:25.091 BGP: Rx Intf add VRF 0 IF veth2da49fed
-2022/05/17 09:57:25.091 BGP: Rx Intf address add VRF 0 IF veth2da49fed addr fe80::24bd:d1ff:fec1:d88/64
-2022/05/17 09:57:25.091 BGP: Rx Intf add VRF 0 IF veth2fa08c8c
-2022/05/17 09:57:25.091 BGP: Rx Intf address add VRF 0 IF veth2fa08c8c addr fe80::6870:ff:fe96:efc8/64
-2022/05/17 09:57:25.091 BGP: Rx Intf add VRF 0 IF veth41e356b7
-2022/05/17 09:57:25.091 BGP: Rx Intf address add VRF 0 IF veth41e356b7 addr fe80::48ff:37ff:fede:eb4b/64
-2022/05/17 09:57:25.092 BGP: Rx Intf add VRF 0 IF veth1295c6e2
-2022/05/17 09:57:25.092 BGP: Rx Intf address add VRF 0 IF veth1295c6e2 addr fe80::b827:a2ff:feed:637/64
-2022/05/17 09:57:25.092 BGP: Rx Intf add VRF 0 IF veth9733c6dc
-2022/05/17 09:57:25.092 BGP: Rx Intf address add VRF 0 IF veth9733c6dc addr fe80::3cf4:15ff:fe11:e541/64
-2022/05/17 09:57:25.092 BGP: Rx Intf add VRF 0 IF veth336680ea
-2022/05/17 09:57:25.092 BGP: Rx Intf address add VRF 0 IF veth336680ea addr fe80::94b1:8bff:fe7e:488c/64
-2022/05/17 09:57:25.092 BGP: Rx Intf add VRF 0 IF vetha0a907b7
-2022/05/17 09:57:25.092 BGP: Rx Intf address add VRF 0 IF vetha0a907b7 addr fe80::3855:a6ff:fe73:46c3/64
-2022/05/17 09:57:25.092 BGP: Rx Intf add VRF 0 IF vethf35a4398
-2022/05/17 09:57:25.092 BGP: Rx Intf address add VRF 0 IF vethf35a4398 addr fe80::40ef:2fff:fe57:4c4d/64
-2022/05/17 09:57:25.092 BGP: Rx Intf add VRF 0 IF vethf831b7f4
-2022/05/17 09:57:25.092 BGP: Rx Intf address add VRF 0 IF vethf831b7f4 addr fe80::f0d9:89ff:fe7c:1d32/64
-2022/05/17 09:57:25.092 BGP: Rx Intf add VRF 0 IF vxlan_sys_4789
-2022/05/17 09:57:25.092 BGP: Rx Intf address add VRF 0 IF vxlan_sys_4789 addr fe80::80c1:82ff:fe4b:f078/64
-2022/05/17 09:57:26.094 BGP: 10.0.0.1 [FSM] Timer (start timer expire).
-2022/05/17 09:57:26.094 BGP: 10.0.0.1 [FSM] BGP_Start (Idle->Connect), fd -1
-2022/05/17 09:57:26.094 BGP: Allocated bnc 10.0.0.1/32(0)(VRF default) peer 0x7f807f7631a0
-2022/05/17 09:57:26.094 BGP: sendmsg_zebra_rnh: sending cmd ZEBRA_NEXTHOP_REGISTER for 10.0.0.1/32 (vrf VRF default)
-2022/05/17 09:57:26.094 BGP: 10.0.0.1 [FSM] Waiting for NHT
-2022/05/17 09:57:26.094 BGP: bgp_fsm_change_status : vrf default(0), Status: Connect established_peers 0
-2022/05/17 09:57:26.094 BGP: 10.0.0.1 went from Idle to Connect
-2022/05/17 09:57:26.094 BGP: 10.0.0.1 [FSM] TCP_connection_open_failed (Connect->Active), fd -1
-2022/05/17 09:57:26.094 BGP: bgp_fsm_change_status : vrf default(0), Status: Active established_peers 0
-2022/05/17 09:57:26.094 BGP: 10.0.0.1 went from Connect to Active
-2022/05/17 09:57:26.094 ZEBRA: rnh_register msg from client bgp: hdr->length=8, type=nexthop vrf=0
-2022/05/17 09:57:26.094 ZEBRA: 0: Add RNH 10.0.0.1/32 type Nexthop
-2022/05/17 09:57:26.094 ZEBRA: 0:10.0.0.1/32: Evaluate RNH, type Nexthop (force)
-2022/05/17 09:57:26.094 ZEBRA: 0:10.0.0.1/32: NH has become unresolved
-2022/05/17 09:57:26.094 ZEBRA: 0: Client bgp registers for RNH 10.0.0.1/32 type Nexthop
-2022/05/17 09:57:26.094 BGP: VRF default(0): Rcvd NH update 10.0.0.1/32(0) - metric 0/0 #nhops 0/0 flags 0x6
-2022/05/17 09:57:26.094 BGP: NH update for 10.0.0.1/32(0)(VRF default) - flags 0x6 chgflags 0x0 - evaluate paths
-2022/05/17 09:57:26.094 BGP: evaluate_paths: Updating peer (10.0.0.1(VRF default)) status with NHT
-2022/05/17 09:57:30.081 ZEBRA: Event driven route-map update triggered
-2022/05/17 09:57:30.081 ZEBRA: Event handler for route-map: 10.0.0.1-out
-2022/05/17 09:57:30.081 ZEBRA: Event handler for route-map: 10.0.0.1-in
-2022/05/17 09:57:31.104 ZEBRA: netlink_parse_info: netlink-listen (NS 0) type RTM_NEWNEIGH(28), len=76, seq=0, pid=0
-2022/05/17 09:57:31.104 ZEBRA: 	Neighbor Entry received is not on a VLAN or a BRIDGE, ignoring
-2022/05/17 09:57:31.105 ZEBRA: netlink_parse_info: netlink-listen (NS 0) type RTM_NEWNEIGH(28), len=76, seq=0, pid=0
-2022/05/17 09:57:31.105 ZEBRA: 	Neighbor Entry received is not on a VLAN or a BRIDGE, ignoring
+2026/03/02 09:53:09 WATCHFRR: [T83RR-8SM5G] watchfrr 8.5.3 starting: vty@0
+2026/03/02 09:53:09 WATCHFRR: [ZCJ3S-SPH5S] zebra state -> down : initial connection attempt failed
+2026/03/02 09:53:09 WATCHFRR: [ZCJ3S-SPH5S] bgpd state -> down : initial connection attempt failed
+2026/03/02 09:53:09 WATCHFRR: [ZCJ3S-SPH5S] staticd state -> down : initial connection attempt failed
+2026/03/02 09:53:09 WATCHFRR: [ZCJ3S-SPH5S] bfdd state -> down : initial connection attempt failed
+2026/03/02 09:53:09 ZEBRA: [NNACN-54BDA][EC 4043309110] Disabling MPLS support (no kernel support)
+2026/03/02 09:53:09 WATCHFRR: [VTVCM-Y2NW3] Configuration Read in Took: 00:00:00
+2026/03/02 09:53:09 WATCHFRR: [QDG3Y-BY5TN] zebra state -> up : connect succeeded
+2026/03/02 09:53:09 WATCHFRR: [QDG3Y-BY5TN] bgpd state -> up : connect succeeded
+2026/03/02 09:53:09 WATCHFRR: [QDG3Y-BY5TN] staticd state -> up : connect succeeded
+2026/03/02 09:53:09 WATCHFRR: [QDG3Y-BY5TN] bfdd state -> up : connect succeeded
+2026/03/02 09:53:09 WATCHFRR: [KWE5Q-QNGFC] all daemons up, doing startup-complete notify
+2026/03/02 09:53:09 ZEBRA: [VTVCM-Y2NW3] Configuration Read in Took: 00:00:00
+2026/03/02 09:53:09 BGP: [VTVCM-Y2NW3] Configuration Read in Took: 00:00:00
 ----
diff --git a/modules/nw-metallb-metrics.adoc b/modules/nw-metallb-metrics.adoc
@@ -67,10 +67,10 @@ To monitor network connectivity and diagnose routing states, refer to the Promet
 | Counts the number of BGP update messages received from each BGP peer.
 
 | `frrk8s_bgp_keepalives_sent`
-| Counts the number of BGP keepalive messages sent to each BGP peer.
+| Counts the number of BGP `keepalive` messages sent to each BGP peer.
 
 | `frrk8s_bgp_keepalives_received`
-| Counts the number of BGP keepalive messages received from each BGP peer.
+| Counts the number of BGP `keepalive` messages received from each BGP peer.
 
 | `frrk8s_bgp_route_refresh_sent`
 | Counts the number of BGP route refresh messages sent to each BGP peer.
@@ -81,4 +81,7 @@ To monitor network connectivity and diagnose routing states, refer to the Promet
 | `frrk8s_bgp_total_received`
 | Counts the number of total BGP messages received from each BGP peer.
 
+| `frrk8s_bgp_received_prefixes_total`
+| Counts the number of load balancer IP address prefixes received from each BGP peer.
+
 |===