SNMP - Error Lexical Order in QoS Class

Unanswered Question
Mar 11th, 2008

Hi experts,


I am facing a problem with one Router. My network has 8 router Cisco OSR 7609, all is using IOS "s72033-advipservicesk9_wan-mz.122-33.SRA4". We have an application known eHealth developed by CA to management these router. When we try to discover the routers by snmp, 7 are Ok by ine Router can not be discovered. when we use a snmpwalk to this router we see that some problem with MIBs cbQosServicePolicy - OID Tree - 1.3.6.1.4.1.9.9.166.1.1 y cbQosObjects - OID Tree - 1.3.6.1.4.1.9.9.166.1.5. I suppose that the MIB can be corrupted but how can fix this problem , system restart ?


I attach the logs about my investigation the MIBs

1.3.6.1.4.1.9.9.166.1.1.1.1.2.1325 ----> continue with the next existent OID after 1325

1.3.6.1.4.1.9.9.166.1.1.1.1.2.1341 ----> correct and continue with the next existent OID after 1341

1.3.6.1.4.1.9.9.166.1.1.1.1.2.1357 ----> correct and continue with the next existent OID after 1357

1.3.6.1.4.1.9.9.166.1.1.1.1.2.1657 ----> correct and continue with the next existent OID after 1657

1.3.6.1.4.1.9.9.166.1.1.1.1.2.1405 ----> incorrect - "Lexicographic order" error because 1405 is less than 1657, so continue with the next existent OID after 1405

1.3.6.1.4.1.9.9.166.1.1.1.1.2.1421 ----> correct and continue with the next existent OID after

1.3.6.1.4.1.9.9.166.1.1.1.1.2.1437 ----> correct and continue with the next existent OID after

1.3.6.1.4.1.9.9.166.1.1.1.1.2.1723 ----> correct and continue with the next existent OID after

1.3.6.1.4.1.9.9.166.1.1.1.1.2.1739 ----> correct and continue with the next existent OID after

1.3.6.1.4.1.9.9.166.1.1.1.1.2.1279 ----> incorrect - "Lexicographic order" error because 1279 is less than 1739, so continue with the next existent OID after 1279

1.3.6.1.4.1.9.9.166.1.1.1.1.2.1325 ----> BEGINS the LOOP because the GetNext will continue with the next existent OID after 1325 and the next valid one is 1341



Thank in advance


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
carlosdeidan Mon, 03/17/2008 - 13:52

Hello,


Thank for the information but I was trying to see what this Bug mean, but I can not access, Could you share me the document or link about this Bug ?


Thank in advance

Actions

This Discussion