DX NetOps

What is the best route for getting official NCM support for hardware?  Specifically, when I have a switch that is not on the list of NCM supported hardware from a vendor, but it does use the same MIB for config changes as the NCM supported hardware from that vendor, I'm having a hard time getting a certification request for that hardware through tech support.  I keep getting pointed at the instructions on how to build a custom device family, but of course that's a waste of time when the existing NCM family should work just fine with the device if the NCM family would just cover the device.  Has anyone had any luck getting NCM support added for a device through a certification request?  If you have gotten NCM support added for a device, how did you request it?

It's faster if you do it yourself, as they suggested, using custom device family.

Lately it does seem like anything would be faster than going through technical support, but I shouldn't have to re-implement the Cisco config copy mib or junos script when it's already in NCM.

I think that's because they treat the request as a solution configuration request and they direct you towards CA Services, rather than  as an enhancement request/certification request.What device are you trying to certify? It's not very difficult to create a second device family, even to have the system capture automatically the config on configuration change traps that it receives from the devices.

If it was a device family that didn't exist, I'd go ahead and create a custom one.  I don't expect that NCM can support everything.  It just seems to be a waste of my time to have to create a custom device family that re-implements existing device families for hardware that is listed as certified with enhanced support.

The Spectrum support team is not in the position to create and implement new functionality or enhancements such as this to the product.  What support can help with is known solutions, workarounds, tshooting and debugging, reporting bugs to sustaining engineering and moving issues such as this through our established processes.  I believe this particular request falls under the Device Certification process and am verifying with Product Management that this is the best process to follow for what you need.  I have the support case you opened for this and will use it to communicate what will happen with your request.

You can always contact me directly for this issue or any issue if you'd like.

--

Rene' Cantwell

Support Delivery Managaer

603-334-2497 rene.cantwell@ca.com

It's certainly not new functionality or an enhancement.  I would expect it to be similar to device certification.

I'm talking about devices that should be in a device family, but aren't yet.  For example, adding support for Juniper EX2200s.  The EX3200 and EX4200 are supported.  They all three are using the Junos script interface.  They are the same device family, just different sizes of hardware, but only some of them are supported.  Or the MX routers, which also use the same config management interface and discover as the same model type and run the same OS, but no NCM support.

Hey Mathias,

What is the actual device type you are talking about here?

From the sounds, it appears to be a Cisco device that may have a new/different OID perhaps?

What is the model type that it is being created as?  There are a few filters for the Cisco based families.  Model type being one of them, OID, etc.

What I have done in the past for another customer with a newer Cisco switch was utilize Model Type Editor to update the sysOIDVerifyList for the SwCiscoIOS model type to include the new OID.

Before the change it was GnSNMPDev or the generic Cisco model type that we have.

After the change it becamse SwCiscoIOS (remodel of course) and was then placed in the family.

You can try that if this is the same scenario you are seeing.

Thanks!

Matt

Mostly Junipers (EX and MX), right now, but we have had this problem in the past with Cisco and Brocade.  In the Cisco and Brocade cases, I think that workaround would be ok.

The sysoidverifylist workaround does not appear to be the issue here, the sysobjectids for the Juniper MX and EX devices that I have modeled are already in the sysoidverifylist.

All of the EX and MX hardware that I'm having this problem with is already listed on the device cert page as having enhanced support, and they discover as JuniperJunosRtr models.

you may want to support this idea:

NCM possibility to add devices to CA Device Families

Yes, I've voted for that.  It's a significant gap in NCM right now. 

Thanks for using the CA Community!  It looks like your question has been answered so we are closing this thread out.  If you have additional questions, please feel free to contact us again.

No, my question wasn't answered.

Hi Mathias - I'm going through old threads and closing them out. This one is almost 2 years old and it looks like its addressed in the idea posted by Olaf Schalenberg NCM possibility to add devices to CA Device Families.

I apologize if you feel we didn't answer your question and I think this is best handled through the idea wall posting and update requests from Product Management.