Skip to content
DataMiner Dojo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Tutorials
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • YouTube Videos
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Agility
      • Learn more about Agile
        • Agile Webspace
        • Everything Agile
          • The Agile Manifesto
          • Best Practices
          • Retro Recipes
        • Methodologies
          • The Scrum Framework
          • Kanban
          • Extreme Programming
        • Roles
          • The Product Owner
          • The Agile Coach
          • The Quality & UX Coach (QX)
      • Book your Agile Fundamentals training
      • Book you Kanban workshop
    • >> Go to DataMiner Docs
  • DevOps
    • About the DevOps Program
    • Sign up for the DevOps Program
    • DataMiner DevOps Support
    • Feature Suggestions
  • Downloads
  • Swag Shop
  • PARTNERS
    • Business Partners
    • Technology Partners
  • Contact
    • Sales, Training & Certification
    • DataMiner Support
    • Global Feedback Survey
  • >> Go to dataminer.services

Protocol Update for Elements in a Redundancy Group

Solved95 views3 days agodriver upgrade redundancy group
4
Catarina Grilo [SLC] [DevOps Enabler]2.95K 3 days ago 0 Comments

Hi DOJO,

What is the recommended approach for updating the protocol on elements that belong to a redundancy group?

From what I can see, the protocol options are greyed out on the edit page of elements that are part of a redundancy group, so they cannot be changed directly.

Should these elements be configured to use the production version so that, when the production version is updated, the protocol version can then be upgraded through the "Set Production" action on the new version?

Thanks in advance.

Catarina Grilo [SLC] [DevOps Enabler] Selected answer as best 3 days ago

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
4
Paulo Henriques [SLC] [DevOps Advocate]1.20K Posted 3 days ago 0 Comments

Hi Catarina,

Correct - elements that are referenced in a redundancy group, whether as primary/backup or as part of the switching detection conditions, cannot have their protocol version changed directly. This is why the option is greyed out. If you truly need to change the protocol directly on the element, you would have to temporarily remove and re-create the redundancy group after updating the protocol.

The supported and recommended approach, however, is to update them through the production version: once a new protocol version is available, set it as the production version and it will be applied to the elements. This assumes, of course, that the elements in the redundancy group are configured to run the production version.

Hope this helps.

Catarina Grilo [SLC] [DevOps Enabler] Selected answer as best 3 days ago
You are viewing 1 out of 1 answers, click here to view all answers.
Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2026 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs

[ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin