Bright Cluster Manager Licensing

Provisional: This issue currently has evidence from 3 tickets. Treat guidance as support-history-backed but still verify license terms with Sales Engineering or the Bright/NVIDIA licensing owner when customers ask contractual questions (Tickets #18832, #27873, #43752).

Summary

Customers ask Support for Bright Cluster Manager license-expiration, product-key, or renewal guidance when a cluster warns that its Bright license has expired or when they need to confirm the installed Bright key (Tickets #18832, #27873, #43752). Support typically handles this as a mixed technical/commercial inquiry: renewal quotes go through Sales, while technical-impact questions may require Sales Engineering input (Tickets #18832, #43752).

Frequency

• 3 tickets currently cite Bright Cluster Manager licensing, product-key, or renewal-impact questions (Tickets #18832, #27873, #43752).

Common Causes

1. Expired Bright Cluster Manager license warning. Customers reported warnings that the Bright license for the cluster had expired or was expiring and asked how to renew it (Tickets #18832, #43752).
2. Need to understand operational impact before renewal. A customer asked whether right-to-use meant the cluster would continue operating as-is while only updates/support were limited, and Sales Engineering advised that expiration could hinder or limit job scheduling (Ticket #43752).
3. Need to confirm a Bright product key. A customer needed help validating Bright product-key information after earlier cluster documentation had contained incorrect serial-number information (Ticket #27873).

Diagnostic Steps

1. Separate quote/procurement from technical impact. Route renewal pricing or quote requests to Sales, but keep explicit operational-impact questions open until Support or Sales Engineering answers them (Tickets #18832, #43752).
2. Confirm whether the customer is seeing an expiration warning or asking for key validation. Expiration warnings point to renewal/impact handling, while product-key questions may require identity validation and the appropriate Bright command or license note (Tickets #27873, #43752).
3. Consult Sales Engineering for license-behavior questions. When the question is about what functionality could be lost after expiration, Support should avoid guessing and relay Sales Engineering guidance (Ticket #43752).

Solutions

1. Renew through Sales to reduce downtime and retain support. Support advised renewal because an expired Bright Cluster Manager license could hinder or limit cluster job scheduling and because renewal preserves continued support (Ticket #43752).
2. Provide Sales contact paths for quotes. When customers ask for renewal pricing, Support can provide Sales contact methods or escalate the request to Sales/Sales Engineering rather than quoting from Support (Tickets #18832, #43752).
3. Provide product-key validation guidance when the issue is key discovery. For product-key confirmation, Support validated system identity and provided the Bright key-check guidance needed for the customer to confirm the key (Ticket #27873).

Edge Cases

• Right-to-use ambiguity: A customer may interpret right-to-use as meaning the cluster will continue to function unchanged except for updates, but Support history records Sales Engineering guidance that job scheduling could be hindered or limited after expiration (Ticket #43752).
• Quote-only handling can miss technical subquestions: A renewal request may contain both a commercial quote request and a technical licensing-impact question, so agents should explicitly answer both tracks before closure (Ticket #43752).

Related Issues

• Sales Quote Follow-up
• Software Installation