Skip to content

Commit 26596b7

Browse files
Merge pull request #304360 from sushantjrao/break-glass-setup
Update howto-configure-network-packet-broker.md
2 parents 6254dda + a7f5dc7 commit 26596b7

1 file changed

Lines changed: 12 additions & 1 deletion

File tree

articles/operator-nexus/howto-configure-network-packet-broker.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -123,7 +123,6 @@ az networkfabric tap delete --name <tap-name> --resource-group <rg-name> --fabri
123123
az networkfabric tap show --name <tap-name> --resource-group <rg-name> --fabric-name <fabric-name>
124124
```
125125

126-
127126
## Step 4: Enable or Disable a Network TAP
128127

129128
After creating a TAP, **enable it** to start the packet brokering process. You can disable it at any time to stop forwarding traffic.
@@ -154,6 +153,18 @@ az networkfabric tap update-admin-state \
154153

155154
* Updates to TAP rules or neighbor groups can be applied dynamically without disrupting other flows.
156155

156+
## Common errors for NPB
157+
158+
During Network Packet Broker (NPB) configuration, the system classifies all control path errors into two broad categories:
159+
160+
- **Bad Request (400)**
161+
This occurs when the request is invalid. For example, missing required parameters, providing incorrect values, or using an unsupported schema.
162+
**Recommended action:** Review your request payload and ensure that all required fields and values are valid.
163+
164+
- **Internal Server Error (500)**
165+
This occurs when the system encounters an unexpected condition, such as backend unavailability or a transient failure.
166+
**Recommended action:** Retry the operation after a few minutes.
167+
If the issue persists, contact Microsoft Support.
157168

158169
## Additional resources
159170
[Concepts: Network Packet Broker](./concepts-nexus-network-packet-broker.md)

0 commit comments

Comments
 (0)