Hello,   most times we can solve such problems by reloading only the affected linecard:   c6800#hw-module switch <switch> module <module> reset   This is much faster than reloading a VSS member- or standalone switch and has less impact.   Example: %EARL-SW1_DFC2-1-EXCESSIVE_PARITY_ERROR: EARL 1: Parity error detected in VRAM c6800#hw-module switch 1 module 2 reset   HTH Rolf   ... View more

all routers form full adjacencies with DR and BDR on broadcast- and NBMA Networks. Perhaps I should have been clearer. All routers (DR, BDR, DROther) form full adjacencies (only) with neighbor routers which are the DR or the BDR for that network. ... View more

Full. ... View more

Hi, all routers form full adjacencies with DR and BDR on broadcast- and NBMA networks. Link: RFC 2328 Section 7.4: The Backup Designated Router   Regards, Rolf ... View more

I'm afraid this is quite complicated. You need some more OIDs to translate the indexes, calculate hex to decimal, do the mappings, etc... Have a look at the OID description here: https://snmp.cloudapps.cisco.com/Support/SNMP/do/BrowseOID.do?objectInput=clagAggPortListPorts&translate=Translate&submitValue=SUBMIT&submitClicked=true You are correct: the first two octets indicate the number of ports bundled in the portchannel. The following octet pairs represent the list of ports belonging to the portchannel. I guess it's easier to understand by looking at an example:   Group  Port-channel  Protocol    Ports ------+-------------+-----------+----------------------------------------------- 3      Po3(SU)         LACP      Te1/2/12(P)    Te2/3/5(P) clagAggPortListPorts.221 = "00 02 08 8C 11 05" cieIfDot1dBaseMappingPort.28 = 2188 (0x088C) cieIfDot1dBaseMappingPort.97 = 4357 (0x1105) ifName.28 = Te1/2/12 ifName.97 = Te2/3/5 ifName.221 = Po3   Depending on the channel protocol(s) you use, there may be easier ways. Example with LACP (OID dot3adAggPortAttachedAggID): iso.2.840.10006.300.43.1.2.1.1.13.28 = 221 iso.2.840.10006.300.43.1.2.1.1.13.97 = 221   Hope that helps Rolf ... View more

Hi, this is normal behavior: CISCO-PRODUCTS-MIB cat4500X32 OBJECT IDENTIFIER ::= { ciscoProducts 1606 } -- Cisco Catalyst 4500X series fixed 10GE aggregation switch with 32 10GE SFP+ ports cat4xxxVirtualSwitch OBJECT IDENTIFIER ::= { ciscoProducts 1732 } -- Catalyst 4xxx Virtual Switch   HTH Rolf ... View more

Hi, in addition to the portconfigs, what is the platform and what IOS are you running? Could be a well-known misbehaviour, documented in several bugs for many years: When you add new VLANs or enable new uplinks, sometimes the spanning-tree (software) process begins sending BPDUs for this VLAN(s) before the ASIC got knowledge about the new VLAN(s). The ASIC then sends those BPDUs untagged (!), so the neighbor switch receives them in the trunk's native VLAN. After recovering from the err-disabled or stp-inconsistent state, the link should work as desired. We see this every now and then in our networks. If it occurs only once after a link- or VLAN-change, normally no further actions are required.      HTH Rolf ... View more