Hello, Garry, I believe that Ray is not talking about SNMP trap, but a configuration trap :-).
When configuring EtherChannels between switches in "mode on", unless you are absolutely 100% certain that the other end is configured correctly, you are running the danger of creating a bridging loop in your network, as no BPDUs will be sent on some of the links. This "trap" can be avoided by using LACP/PAgP. -- Marko Milivojevic - CCIE #18427 Senior Technical Instructor - IPexpert FREE CCIE Training: http://bit.ly/vLecture Mailto: [email protected] Telephone: +1-810-326-1444 Web: http://www.ipexpert.com/ On Wed, Aug 4, 2010 at 01:08, garry baker <[email protected]> wrote: > Netman, > > I have this product as well, what was the time at which he mentioned this > trap? > > was he talking about just a normal link up / link down trap? > > i am going to listen to it again and see if i can hear when he says, because > i looked in the 3560 config guide and do not see anything other than this > reference to traps in the etherchannel section and i didnt see it in the > 'traps' section for PAGP or LACP: > > "If a link within an EtherChannel fails, traffic previously carried over > that failed link moves to the remaining links within the EtherChannel. If > traps are enabled on the switch, a trap is sent for a failure that > identifies the switch, the EtherChannel, and the failed link. Inbound > broadcast and multicast packets on one link in an EtherChannel are blocked > from returning on any other link of the EtherChannel. " > > and you can see this in the "debug snmp packets" > > 00:16:11: %LINK-3-UPDOWN: Interface Port-channel1, changed state to down > 00:16:11: SNMP: Queuing packet to 1.1.1.2 > 00:16:11: SNMP: V1 Trap, ent ciscoSyslogMIB.2, addr 1.1.1.1, gentrap 6, > spectrap 1 > clogHistoryEntry.2.22 = LINK > clogHistoryEntry.3.22 = 4 > clogHistoryEntry.4.22 = UPDOWN > clogHistoryEntry.5.22 = Interface Port-channel1, changed state to down > clogHistoryEntry.6.22 = 97125 > 00:16:11: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to > down > 00:16:11: SNMP: Queuing packet to 1.1.1.2 > 00:16:11: SNMP: V1 Trap, ent ciscoSyslogMIB.2, addr 1.1.1.1, gentrap 6, > spectrap 1 > clogHistoryEntry.2.23 = LINK > clogHistoryEntry.3.23 = 4 > clogHistoryEntry.4.23 = UPDOWN > clogHistoryEntry.5.23 = Interface GigabitEthernet1/0/1, changed state to > down > clogHistoryEntry.6.23 = 97127 > Switch#sh etherchannel summary > Number of channel-groups in use: 1 > Number of aggregators: 1 > Group Port-channel Protocol Ports > ------+-------------+-----------+----------------------------------------------- > 1 Po1(SD) - Gi1/0/1(D) > -- > Garry L. Baker > > "There is no 'patch' for stupidity." - www.sqlsecurity.com > > > On Wed, Aug 4, 2010 at 6:50 AM, Netman <[email protected]> wrote: >> >> Hey Marko, >> >> I was listening to the Ether-channel MP3 and you discussed a trap with >> Port-channel mode ON when the ports have LACP or PAGP configured as the >> dynamic trunk protocol. I was not 100% on the example, but it seemed like a >> really good "trap". >> >> >> Can you help me understand that example? >> >> >> Last question: do you have a place where we can ask questions about >> particular products or even tasks and then look up the historical responses >> for that product? Or is it just the mailing list and the archive that we >> need search? >> >> >> Thanks, >> >> >> Ray >> >> >> _______________________________________________ >> For more information regarding industry leading CCIE Lab training, please >> visit www.ipexpert.com >> > > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
