Cisco 6500 bp_index problem

netdisco / snmp-info

Other

35 stars 31 forks source link

Cisco 6500 bp_index problem #8

Closed netdisco-automation closed 7 years ago

netdisco-automation commented 18 years ago

Cisco 6500 dot1dBasePortTable not always working with snmp getnext requests.

This results missing data in bp_index()

Reported by: jeneric-placeholder

Original Ticket: snmp-info/bugs/8

netdisco-automation commented 18 years ago

labels: --> Device Support

Original comment by: maxslug-placeholder

netdisco-automation commented 18 years ago

Logged In: YES user_id=19674

Any known fix for this?

Original comment by: maxslug-placeholder

netdisco-automation commented 18 years ago

milestone: --> v1.0
priority: 5 --> 6

Original comment by: maxslug-placeholder

netdisco-automation commented 18 years ago

Logged In: YES user_id=1135238

The potential solution is to use the CISCO-STACK-MIB rather than BRIDGE-MIB. This seems to work on all CatOS devices.

portCrossIndex should equal dot1dBasePort and portIfIndex should equal dot1dBasePortIfIndex

Original comment by: jeneric-placeholder

netdisco-automation commented 18 years ago

Logged In: YES user_id=1135238

Implemented using CISCO-STACK-MIB rather than BRIDGE-MIB for Catalyst class. Committed for inclusion in SNMP::Info 1.0

Ralf Gross reported working against: wsc2948g wsc2948ggetx 295048G 3508GXL 355024PWR wsc5000 wsc5005 wsc5500 wsc6006 wsc6503 WS-C6506 WS-C6509 (IOS) wsc6509

C4506/C4507 have problems with the patch, so it was not included in C6500 class. Future work may require moving 4500's to thier own class since they do not support the CISCO-STACK-MIB.

Original comment by: jeneric-placeholder

netdisco-automation commented 18 years ago

status: open --> closed-fixed

Original comment by: jeneric-placeholder