OLD_CHASSIS_MIB is been deprecated. The information from the OID cardIfConnectorTypeEnabled (cardIfIndexTable) is not giving out information. So I was thinking if anyone could help in getting similar kind of information from Entity MIB or which were is relavent or related.
Basically I am asking where did the information from the OID cardIfConnectorTypeEnabled is stored now after the chassis MIB is deprecated
I agree with you. Also, I read about it in cisco.com.
But the information that I am looking for is, for example, lets say, for a particular port the connector is rj-45; in this case, the cardIfConnectorTypeEnabled will report 3 and accordingly I will decide the connector for a particular port. Now in Entity MIB case, this type of information is not available in any of the OID in the phyiscal table.
I observed that, the entPhysicalVendorType, is used to map the model of a card or a chassis which is similar to cardType.
So, I am trying to find the information about the connector of a port through an alternative MIB's OID which is similar to cardIfConnectorTypeEnabled
Update on the above conversation is that, there are several documents which talks about the mapping of Chassis MIB to Entity MIB. They provide the information about all the OIDs except, the cardIfConnectorTypeEnabled OID.
One of the atricle which provides the information about the mapping is
I am not understanding why Cisco has not written any article to map the information of this OID to an alternative MIB or an OID. Or they have removed the access to such informaiton in the routers. If YES are these details are no more important?
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...