What should teams do first when UAG array trunk settings do not appear in the management console?

First confirm that the array has more than one machine. In UAG, the trunk settings for dedicated IPs and integrated NLB do not appear while only the array manager is present. After adding a second array member, close and reopen the management console so the updated trunk options are displayed and can be configured correctly.

What to check first when trunk options are missing

The first check is simple: confirm the array has more than one machine. In UAG, trunk settings for dedicated IPs and integrated NLB are hidden until the array contains at least two members. That makes the console behaviour look like a configuration problem when it is really a topology prerequisite.

Once the second member is added, close the management console and reopen it so the interface refreshes. The trunk options should then appear and be configurable, which confirms the array state has been recognised correctly.

Why the console hides trunk settings in this state

UAG exposes trunk controls only when the array can actually use them. With a single array manager, those settings are suppressed because dedicated IP and integrated NLB depend on a multi-member array design. The console is therefore reflecting the deployment state, not a failed feature.

This is a useful pattern to recognise in administrative tools: some controls are conditional on topology, membership, or role rather than on licensing or browser behaviour. If the expected option is absent, check the underlying object state before spending time on UI troubleshooting.

After the array changes, reopen the console instead of assuming a cached page or permissions issue. Refreshing the session forces the management interface to re-evaluate the array membership and display the correct trunk configuration path.

What a clean fix looks like

A clean resolution is to add the second array member, verify that both machines are present and healthy, then reopen the management console and confirm the trunk settings are now visible. If the options still do not appear, the next step is to verify the array membership and management session rather than changing unrelated network settings.

Teams should also keep the sequence straight: topology first, UI refresh second, configuration third. That order avoids false troubleshooting paths and ensures the trunk settings are being exposed by the product for the right reason.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.

Framework	Control / Reference	Relevance
NIST SP 800-53 Rev 5	CM-2 — Baseline Configuration	Trunk options depend on the array's configured topology and member count.
	CM-6 — Configuration Settings	The fix is to ensure the system is set to the correct multi-member state before configuring trunks.
Recommendation — Validate the deployed array configuration before expecting topology-dependent controls to appear. Recheck configuration state after adding the second array member and reopening the console.
NIST CSF 2.0	PR.IP-1 — Configuration management	The answer hinges on configuration state driving which management options are exposed.
Recommendation — Confirm the platform state has changed before assuming a missing option is a fault.

Practitioner Guidance

What to verify: Confirm the array really has two members before treating the missing trunk options as an error. In practice, the most common mistake is to look for a hidden setting before the platform prerequisites are satisfied.

Decision rule: If only the array manager exists, stop and add the second member first. If the second member is already present, reopen the console before escalating further, because the management session may still be showing the pre-change state.

Practitioner takeaway: Absence of a console option is often a state issue, not a product defect, so validate the deployment topology before you troubleshoot the interface.