According to the Cisco documentation below • When configuring Layer 3 EtherChannels, you must manually create the port channel logical interface first (see the “Configuring Port Channel Logical Interfaces for Layer 3 EtherChannels” section on page 12-7), and then put the Layer 3 LAN ports into the channel group as described in this section. • When configuring Layer 2 EtherChannels, configure the LAN ports with the channel-group command as described in this section, which automatically creates the port channel logical interface. You cannot put Layer 2 LAN ports into a manually created port channel interface. • For Cisco IOS to create port channel interfaces for Layer 2 EtherChannels, the Layer 2 LAN ports must be connected and functioning Source: http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SXF/native/configuration/guide/channel.pdf. It is this statement “You cannot put Layer 2 LAN ports into a manually created port channel interface” from above that I disagree with I have created interface Port-channel 35 And then I have bundled Gi1/0/1 andGi1/0/2 within this using the channel-group command as normal Can any explain if this was something you couldn’t do on older switches or is this an error. I seem to recall reading this and witnessing this issue in the past but can’t be sure Thanks in advance, David ... View more

Good afternoon all, I have two 6509s both with single FWSMs running in transparent mode with bridged Inside and Outside VLANs. I have my Core A set to STP priority of 8192 and Core B set to 16,384 to make Core A the root for all VLANs. Problem I have is when I look at spanning-tree on Core A for Inside VLAN 324 it states to get to the Root go via PO100 (Cost of 9) and that the Root also has a Priority of 8192, but as the designated Root has a lower MAC address it's pointing to the etherchannel. PO100 is L2 Etherchannel between the Cores. Moving accross PO100 to Core B and running the show spanning-tree command I can see that to get to the Root Bridge I need to go via PO272.  PO272 is the internal Etherchannel to get to the FWSM on the Core B Switch.  This shows a cost of 6 to get to the Root and a mac address of the Root Bridge which resides on Core A (Outside VLAN 124) To give some perspectibe,theoutside VLAN of the pair has it's STP ROOT on the Core A switch as intended Any help would be much appreciated David ... View more

Hi All, I have two 6509s with a single CSM in each set up for FT.  No changes have been made to the configuration recently but I have noticed the following EMs occuring in the logs.  Both logs are from the same period of time so you can see what is happening on one CSM and compare it to the same time stamp on the other. This problem is reoccuring every couple of days As far as I can see everything looks good in terms of hardware and config, any help would be greately appreciated Please note I only have remote access to the switches and the Software version on both CSM is 4.2(2) Switch uptime is not greater that 828 days and I can see that of the 58,152 heartbeats the Active Master has sent, only 58,056 have been recieved by the Backup/Secondary I have looked into this for the last 4 hours and the only assumption I can make is that the L2 Etherchannel beteen the Cores is getting swamped with traffic and causing the keep alives to fail, but I don't know how to prove this.                 Core 1A Feb  7 14:49:23.130 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: LRP: no ACK from standby.. standby may be down Feb  7 14:49:23.730 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: LRP: no ACK from standby.. standby may be down Feb  7 14:49:26.130 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: LRP: no ACK from standby.. standby may be down Feb  7 14:49:35.730 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: LRP: no ACK from standby.. standby may be down Feb  7 14:50:04.691 UTC: %SEC-6-IPACCESSLOGRL: access-list logging rate-limited or missed 210 packets Feb  7 14:50:14.131 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: LRP: no ACK from standby.. standby may be down Feb  7 14:51:04.715 UTC: %SEC-6-IPACCESSLOGRL: access-list logging rate-limited or missed 1 packet Feb  7 14:52:04.739 UTC: %SEC-6-IPACCESSLOGRL: access-list logging rate-limited or missed 3 packets Feb  7 14:52:08.451 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: LRP: no ACK from standby.. standby may be down Feb  7 14:52:09.051 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: LRP: no ACK from standby.. standby may be down Feb  7 14:52:11.447 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: LRP: no ACK from standby.. standby may be down Feb  7 14:52:21.047 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: LRP: no ACK from standby.. standby may be down Feb  7 14:52:59.452 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: LRP: no ACK from standby.. standby may be down Feb  7 14:53:04.764 UTC: %SEC-6-IPACCESSLOGRL: access-list logging rate-limited or missed 224 packets Feb  7 14:53:37.808 UTC: %C6KPWR-SP-4-DISABLED: power to module in slot 1 set off (Module not responding to Keep Alive polling) Feb  7 14:55:16.820 UTC: %MLS_RATE-4-DISABLING: The Layer2 Rate Limiters have been disabled. Feb  7 14:55:15.800 UTC: %DIAG-SP-6-RUN_MINIMUM: Module 1: Running Minimal Diagnostics... Feb  7 14:55:16.468 UTC: %DIAG-SP-6-DIAG_OK: Module 1: Passed Online Diagnostics Feb  7 14:55:18.988 UTC: %OIR-SP-6-INSCARD: Card inserted in slot 1, interfaces are now online Feb  7 14:55:20.356 UTC: %CSM_SLB-6-REDUNDANCY_INFO: Module 1 FT info: State Transition Init -> Standby Feb  7 14:55:20.700 UTC: %CSM_SLB-6-REDUNDANCY_INFO: Module 1 FT info: State Transition Standby -> Active Feb  7 14:55:20.864 UTC: %CSM_SLB-6-INFO: Module 1 info: config reload completed successfully. Feb  7 14:55:23.896 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: LRP: no ACK from standby.. standby may be down Feb  7 14:55:24.496 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: LRP: no ACK from standby.. standby may be down Feb  7 14:55:26.896 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: LRP: no ACK from standby.. standby may be down Feb  7 14:55:36.496 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: LRP: no ACK from standby.. standby may be down Feb  7 14:56:14.905 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: LRP: no ACK from standby.. standby may be down COR-1A#show mod contentswitchingModule 1 ft FT group 1, vlan 4 This box is active priority 20, heartbeat 1, failover 3, preemption is on Core 1B Feb  7 14:49:44.463 UTC: %C6KPWR-SP-4-DISABLED: power to module in slot 1 set off (Module not responding to Keep Alive polling) Feb  7 14:51:22.467 UTC: %DIAG-SP-6-RUN_MINIMUM: Module 1: Running Minimal Diagnostics... Feb  7 14:51:24.495 UTC: %MLS_RATE-4-DISABLING: The Layer2 Rate Limiters have been disabled. Feb  7 14:51:24.156 UTC: %DIAG-SP-6-DIAG_OK: Module 1: Passed Online Diagnostics Feb  7 14:51:26.657 UTC: %OIR-SP-6-INSCARD: Card inserted in slot 1, interfaces are now online Feb  7 14:51:28.511 UTC: %CSM_SLB-6-INFO: Module 1 info: config reload completed successfully. Feb  7 14:51:28.567 UTC: %CSM_SLB-6-REDUNDANCY_INFO: Module 1 FT info: State Transition Init -> Standby Feb  7 14:52:31.748 UTC: %C6KPWR-SP-4-DISABLED: power to module in slot 1 set off (Module not responding to Keep Alive polling) Feb  7 14:54:10.782 UTC: %MLS_RATE-4-DISABLING: The Layer2 Rate Limiters have been disabled. Feb  7 14:54:09.762 UTC: %DIAG-SP-6-RUN_MINIMUM: Module 1: Running Minimal Diagnostics... Feb  7 14:54:10.554 UTC: %DIAG-SP-6-DIAG_OK: Module 1: Passed Online Diagnostics Feb  7 14:54:12.870 UTC: %OIR-SP-6-INSCARD: Card inserted in slot 1, interfaces are now online Feb  7 14:54:14.794 UTC: %CSM_SLB-6-INFO: Module 1 info: config reload completed successfully. Feb  7 14:55:04.094 UTC: %CSM_SLB-6-REDUNDANCY_INFO: Module 1 FT info: State Transition Elect -> Active Feb  7 14:55:07.102 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: LRP: no ACK from standby.. standby may be down Feb  7 14:55:07.698 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: LRP: no ACK from standby.. standby may be down Feb  7 14:55:10.098 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: LRP: no ACK from standby.. standby may be down Feb  7 14:55:19.698 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: LRP: no ACK from standby.. standby may be down Feb  7 14:55:20.502 UTC: %CSM_SLB-4-REDUNDANCY_WARN: Module 1 FT warning: FT configuration might be out of sync. Feb  7 14:55:20.702 UTC: %CSM_SLB-6-REDUNDANCY_INFO: Module 1 FT info: State Transition Active -> Standby Feb  7 14:55:45.043 UTC: %C6KPWR-SP-4-DISABLED: power to module in slot 1 set off (Module not responding to Keep Alive polling) Feb  7 14:57:24.076 UTC: %MLS_RATE-4-DISABLING: The Layer2 Rate Limiters have been disabled. Feb  7 14:57:23.048 UTC: %DIAG-SP-6-RUN_MINIMUM: Module 1: Running Minimal Diagnostics... Feb  7 14:57:23.740 UTC: %DIAG-SP-6-DIAG_OK: Module 1: Passed Online Diagnostics Feb  7 14:57:26.164 UTC: %OIR-SP-6-INSCARD: Card inserted in slot 1, interfaces are now online Feb  7 14:57:27.736 UTC: %CSM_SLB-6-REDUNDANCY_INFO: Module 1 FT info: State Transition Init -> Standby Feb  7 14:57:28.104 UTC: %CSM_SLB-6-INFO: Module 1 info: config reload completed successfully. COR-1B#show module contentSwitchingModule 1 ft FT group 1, vlan 4 This box is in standby state priority 10, heartbeat 1, failover 3, preemption is on Thanks in advance David ... View more

Good Morning All, First of all appologies if this is in the wrong category, but I couldn't find a QoS category I am studying QoS for my SWITCH exam and I am having a hardtime understanding the bits used for L3 IP Precedence and DSCP markings The texts keep referring to left most bits of the ToS Byte but the values they are stating lead me to look at the right most bits to get the values they are referring to! Book Extract IP Precedence markings and Differentiated Services Code Point (DSCP) markings are both Layer 3 markings. IP Precedence uses the three leftmost bits in an IPv4 header's Type of Service (ToS) byte. Like CoS, with three bits at its disposal, IP Precedence markings have values in the range of 0[nd]7. Question 1 Are the three left most bits the red highlight or the blue hightlight?  Example, 001 01011or 00 101 011 (So I am asking is it the left most bits in use or just the left most bits of the byte?). Book Extract Cont.. Again, Cisco cautions us that values of 6 and 7 are reserved, so you should mark voice media with an IP Precedence value of 5. DSCP markings use the six leftmost bits of a ToS byte, giving us 64 potential values (in the range 0[nd]63). Rather than allowing haphazard value assignments, the IETF has identified and named a collection of preselected values, called per-hop behaviors (PHBs). Question 2 How can the six leftmost bits of a ToS byte give a range of 0 - 63? Looking at a standard byte 00110011 the six left most bits would value 252 if all turned on, and the right most bits would value 64 if all turned on 00110011? Unless as asked above the six leftmost bits begin where the logical ON begins eg 00110011 in which case what would happen if the value was 00001111 as you wouldn't have six bits in play, so would the value be 15 as per the bold? Question 3 In addition to the above when referring to the Least Significant Bit are we looking at the last binary 1 (on) or the last binary digit to the right side of the byte regardless if it is a 1 (on) or 0 (off)?  Example 11011011 - So the bold 1 at the right side is the least significant but, but if the byte read 110110 1 0 would the 0 at the far right be the least significant bit or would this fall back to the next available 1 (on) bit which would be the bit highlighted in red? I suspect the digit in Red! Thanks in advance, I know someone out there who works with QoS will be able to answer this for me! David ... View more

Ladies and Gents, Your help will be greatly appreciated – I am currently studying CCNP Switch AAA configuration and I work with a tacacs+ server at work butI having difficulty getting my head around the below Cisco.com extract below When you create a named method list, you are defining a particular list of authorization methods for the indicated authorization type. Once defined, method lists must be applied to specific lines or interfaces before any of the defined methods will be performed. The only exception is the default method list (which is named "default"). If the aaa authorization command for a particular authorization type is issued without a named method list specified, the default method list is automatically applied to all interfaces or lines except those that have a named method list explicitly defined. (A defined method list overrides the default method list.) If no default method list is defined, local authorization takes place by default. My question is how do you define the Named Method List i.e. the none-default method list? I don't mean the cisco switch config but how the list is created, is this on the tacacs+ server and the referred to in the CLI? Any help would be much appreciated as I have read over tons of documents and I can’t see how this is created Thanks in advance David ... View more