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

Am I using IDP incorrectly?

Solved119 views2 days agoIDP
4
Chris Glover [DevOps Advocate]1.60K 2 days ago 0 Comments

Hi,

I'm playing with IDP, but failing dismally to get it to discover anything

Scenario:-

I have an NMOS registry (GV Orbit) running on a device on port 4041. In Admin -> Discovery -> Discovery Profiles I have created a profile called Get_x-nmos. this is configured to GET /x-nmos from the end device on 4041. I create a scan range, that is just my device of interest

In Admin -> CI Types, I have created an NMOS Registry CI type, with discovery identifier confgured

Identifier: Get_x-nmos

Match: contains

Value: registration

If I send a request using cURL, I get

[
"node/",
"query/",
"registration/",
"system/"
]

In Provisioning I have configured the Protocol as AMWA NMOS IS-04 Registry, and set the relevant values

However when I run a discover against the Orbit scan range I get nothing. Checking with Wireshark, I can see no requests received by the Orbit sever from Dataminer. other NMOS traffic is flowing correctly

The Orbit and DMA are in the same subnet, and there's no firewalls between them. I can create an element manually, which works correctly

What am I missing?

Thanks

Chris Glover [DevOps Advocate] Selected answer as best 2 days ago

2 Answers

  • Active
  • Voted
  • Newest
  • Oldest
1
Chris Glover [DevOps Advocate]1.60K Posted 2 days ago 0 Comments

Thanks to João, It was due to the IDP Discovery element running on the other site. This is a test system, so not all the firewall rules are in place

After swarming to the same site, it's all good.

The /x-nmos vs x-nmos wasn't the issue

And now I know how to access hidden elements 🙂

Chris Glover [DevOps Advocate] Changed status to publish 2 days ago
You are viewing 1 out of 2 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

© 2025 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