F-port-channel-trunk disruptive or not?

Hi,
We have a N5K with NPIV configured and and MDS9148 we're gonna setup a port channel and have come to the conclusion that we need the F-port-channel-trunk feature enabled on the MDS side.
Question: Is enabling the F-port-channel-trunk feature on the MDS disruptive or non-disruptive?
--M

It's too late; I would say it is disruptive; however, the disruption is so short, that you didn't notice it. Similar without non F-port trunking channeling: using a link: the lost sessions are simply redistributed over the remaining links; new flogi is necessary.

Similar Messages

  • Fabric Interconnect To MDS 9148 FC Port Channel/Trunks

    Is it possible to create both a Port Channel and Trunk on a Cisco MDS 9148? Yes correct?
    Or can I only trunk between the 2 MDS switches and not the MDS to Fabric Interconnect?
    These FC links would be connected to a 2248XP Fabric Interconnect carrying multiple VSANs from the MDS to the Fabric Interconnect.
    Thanks

    Hello,
    Yes, you can have trunk links grouped into port channel ( F port-channel trunking ) between FI and MDS.
    http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_0101.html
    Padma

  • FC Port Channel & Trunking

    Hi, Cisco Experts:
    Can I have a definitive answer to the following?
    q1.
    EMC mentioned that they do not support FC Port Channel & Trunking with regard to our UCS Fabric Interconnects/MDS/VNX5300?
    Is that any truth in that?
    We are trying a Cisco UCS solutions with MDS and EMC VNX in the mix-SAN Boot basically, ESXi 5.1 and all others.
    q2.
    From MDS all the ways up to EMC VNX, is there such concept too-FC Port Channel & Trunking, assuming we are doing FC Port Channel & Trunking from FInterconnect to MDS?
    Please let me know.
    Appreciate it.
    SiM

    Hi Sim,
    We support FC port channel and trunking between UCS FI and MDS.
    Is EMC saying about the port channel between the MDS and VNX? Is there any document EMC pointed out?
    With respect to booting from SAN, yes, you can boot from SAN with MDS and EMC VNX as long as the OS is supported in the UCS system. You can refer to
    http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_list.html for the supported OS versions.
    Hope this answers your question.
    -Ganesh

  • MDS Code Level for UCS FC Port Channel/Trunking

    What is the required MDS code level needed to support FC Port-Channeling/Trunking on a 9222i, 9148, or 9509/9513 w/ Gen2 line cards to UCS 1.4(3)?
    I know the fport-channel-trunk feature is needed and was released in MDS 4.2 code but I have seen documents that this level of code wont support these features when used to connect to Cisco UCS. 
    Can someone confirm?  Is NXOS 5.0(4) or higher required?

    Doug,
    I wrote the doc almost a year ago and it doesn't have the latest interop matrix support information. The current MDS NX-OS support is located in this doc: http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/intmatrx.html
    While, I wish this was also duplicated in UCS docs, they are more or less taking the stance that 3rd party (Cisco MDS is this case) interop is maintained by the 3rd party. EMC, Netapp, or even Cisco.
    It would be a nightmare updating UCS docs with 3rd party qualifications and support.
    The short answer to your question is:
    UCS 1.4(1), 1.4(2), 1.4(3) Is supported by MDS9000: 3.3(4a), 3.3(5), 4.2(1a), 4.2(1b), 4.2(3a), 4.2(5), 5.0(1a), 5.0(4), 5.0(4c)
    NPV was introduced in MDS 3.3. f port-channel/trunk was introduced in MDS 4.2.
    As Ram mentioned above, 4.2(5) is what I would recommend if I wanted to implement f port-channel and/or f port-trunk. I have also had recent experience with 4.2(5) and it worked great with a large UCS f port-channel/trunk implementation
    The specific switch limitations I mentioned in my doc still exist. Only certain models of MDS will support f port-trunk. Almost all models will support f port-channel.
    Dave

  • ASA5550 port channel configuration ERROR: nameif not allowed on empty etherchannel interface

    Hi All,
    I am having problem when configure port channel on asa5550 
    IOS ver asa914-k8.bin also in ver 9.02   and 8.47.
    Please let me know how can I solve this problem.
    UK-LON-FW(config)# int port-channel 3
    UK-LON-FW(config-if)# vlan 245
                           ^
    ERROR: % Invalid input detected at '^' marker.
    UK-LON-FW(config-if)# nameif secure
    ERROR: nameif not allowed on empty etherchannel interface.
    UK-LON-FW(config-if)#
    here is my interfaces configuration:
    interface GigabitEthernet0/0
    description fw1:G0/0 to uk-lon-gw1:e1/8 fw2:G0/0 to uk-lon-gw2:e1/9 outside zone
    channel-group 1 mode on
    no nameif
    no security-level
    no ip address
    interface GigabitEthernet0/1
    description fw1:G0/1 to uk-lon-gw2:e1/8 fw2:G0/1 to uk-lon-gw1:e1/9 outside zone
    channel-group 1 mode on
    no nameif
    no security-level
    no ip address
    interface GigabitEthernet0/2
    description fw1:G0/2 to uk-lon-sw1a:1 fw2:G0/2 to uk-lon-sw1a:2 dmz
    channel-group 2 mode on
    no nameif
    no security-level
    no ip address
    interface GigabitEthernet0/3
    description fw1:G0/3 to uk-lon-sw1b: fw2:G0/3 to uk-lon-sw1b:2 dmz
    channel-group 2 mode on
    no nameif   
    no security-level
    no ip address
    interface Management0/0
    management-only
    nameif management
    security-level 0
    ip address 10.10.51.18 255.255.254.0
    interface GigabitEthernet1/0
    description fw1:G1/0 to uk-lon-sw1a:3 fw2:G1/0 to uk-lon-sw1a:4 secure zone
    no nameif
    no security-level
    no ip address
    interface GigabitEthernet1/1
    description fw1:G1/1 to uk-lon-sw1b:3 fw2:G1/1 to uk-lon-sw1b:4 secure zone
    no nameif
    no security-level
    no ip address
    interface GigabitEthernet1/2
    description LAN Failover Interface
    no nameif   
    no security-level
    no ip address
    interface GigabitEthernet1/3
    description STATE Failover Interface
    no nameif
    no security-level
    no ip address
    interface Port-channel1
    description outside zone
    no nameif
    no security-level
    no ip address
    interface Port-channel1.5
    description outside zone Bundle FW:G0/0-G0/1 connect to GW1:e1/8-GW2:e1/8
    vlan 5
    nameif outside
    security-level 0
    ip address 216.239.105.5 255.255.255.128 standby 216.239.105.6
    interface Port-channel2
    description dmz Bunlde uk-lon-fw:G0/2-3 to sw1a:1-2 sw1b:1-2
    no nameif
    no security-level
    no ip address
    interface Port-channel2.105
    description dmz
    vlan 105
    nameif dmz
    security-level 50
    ip address 216.239.105.193 255.255.255.192 standby 216.239.105.194
    interface Port-channel3
    description secure zone Bunlde uk-lon-fw:G1/0-1 to sw1a:3-3 sw1b:3-4
    no nameif
    security-level 100
    ip address 10.254.105.1 255.255.255.0 standby 10.254.105.2
    UK-LON-FW(config-if)# 

    Hi Marvin,
    Thank you for your answer.  I did everything but it did not work. Turn out it is a bug ver 8.45 will let you created the sub logical interface but actually it did not work right.  Verson 9.x  doesn't let you create more than 2 port channel (limitation of ASA5550 hardware).
    https://tools.cisco.com/bugsearch/bug/CSCtq62715/?reffering_site=dumpcr 
    Also, you can see the 8.4 release notes were you can see that it is not supported:
    http://www.cisco.com/c/en/us/td/docs/security/asa/asa84/release/notes/asarn84.html#pgfId-522232
    Interface Features
    EtherChannel support (ASA 5510 and higher)
    You can configure up to 48 802.3ad EtherChannels of eight active interfaces each.
    Note You cannot use interfaces on the 4GE SSM, including the integrated 4GE SSM in slot 1 on the ASA 5550, as part of an EtherChannel.
    We introduced the following commands: channel-group , lacp port-priority , interface port-channel , lacp max-bundle , port-channel min-bundle , port-channel load-balance , lacp system-priority , clear lacp counters , show lacp , show port-channel .

  • Port-channel / Trunking / VSAN

    Hi all,
    I have a quick question...
    I enabled trunking for all vsans and created a port-channel. I want to use this port-channel for all my vsans.
    Does it matter in which vsan I add my port-channel?
    If it doesn't matter why can I assign a port-channel to a vsan?
    Cheers,
    Mike

    Mike,
    It should be the same configuration on both sides for the port-channel to come up. The reason why you can assign a port-channel to a VSAN is that if you are using an E port then it depends on the matching port-channel VSAN to come up.
    TE Port functionality is specific to MDS for enhanced ISL capabilities. E ports can be used for non-cisco switches to make the trunk work seamlessly as an E port.
    You can refer to the following for more info:
    http://www/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_4_x/trnk.html
    http://www/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_4_x/pc.html
    Hope this helps.
    - Nikhil

  • SGE2010 port-channel and trunking config question

    I have port-channels configured and working for the native VLAN on multiple SGE2010s. I now want to add multiple VLANs and enable trunking for the port-channel. I am not clear on the appropriate way to enable trunking as it can be enabled on the port and on the port-channel. The ports and port-channel are currently in access mode. If anyone can provide the correct configuration, I would appreciate the guidance. I also need to get the port-channels and trunking working with 3Com 4500 & 4200s. If you know of any configuration issues, again any guidance would be appreciated

    Hi Jacqueline,
    Sorry Juans answer needs some correction, but I am grateful for Juans participation.
    The SGE2010 does not support a CLI.
    There is a unsupported CLI,  that someone plastered somehwere on this community, but i must admit i still like to use the GUI.
    The software on the SGE2XXX was recently updated so you can find that on the cisco.com website.
    I have created a link below  to a recording i just made,  regarding Link aggregation on the SGE2XXXX, i thnk if you see the 11 minute recording a couple of times, maybe pause it, play with your switch, it  will start to make sense.
    you can't breat the switch by configuring it
    click here to see a recording of me creating a Link aggregation between two switches
    regards Dave

  • FC Port Channel between UCS and MDS.

    Hi All,
    I am new to Cisco Fabric Concepts. In my enviornment i have a F port channel(8 Port Group) created on MDS 9513 switch and this Fport 
    channel is connected to Cisco UCS 6296 FI. The Cisco UCS Blade servers are connected to the Fabric Interconnect .
    On MDS NPIV is enabled.
    Can anyone explain the below questions.
    1. Why do we create an F port Channel Group and connect it to the UCS FI? Is this something similar to Brocade Edge to AG Switch Connectivity.
    2. How to configure F port Channel Group in MDS . Can anyone explain with an example.
    3. Do we need to make any Configuration on UCS FI ports for server connectivity and Channel port Connectivity if yes what are the steps required to 
    do the same.Does the WWPN shows up in the FLOGI Database if the connectivity and configuration looks good in UCS FI and MDS.
    4. What happens when a VSAN on MDS switch is added to the Port Channel.
    Thanks and Regards,
    Santosh surya

    Look at my remarks in
    https://supportforums.cisco.com/discussion/12468266/fc-port-channels-between-mds-and-ucs-fi-best-practice
    1. Why do we create an F port Channel Group and connect it to the UCS FI? Is this something similar to Brocade Edge to AG Switch Connectivity.
    F port channel is proprietary; therefore any such F port channel between UCS FI and Brocade doesn't work.
    2. How to configure F port Channel Group in MDS . Can anyone explain with an example.
    see eg.
    https://supportforums.cisco.com/sites/default/files/legacy/9/9/2/53299-UCS_1-4-1_F-port_channel-trunk-v1.pdf
    3. Do we need to make any Configuration on UCS FI ports for server connectivity and Channel port Connectivity if yes what are the steps required to 
    see eg.
    https://supportforums.cisco.com/sites/default/files/legacy/9/9/2/53299-UCS_1-4-1_F-port_channel-trunk-v1.pdf
    Does the WWPN shows up in the FLOGI Database if the connectivity and configuration looks good in UCS FI and MDS.
    flogi database is on the MDS, not FI; there are however UCS CLI commands, like "show npv ...."
    4. What happens when a VSAN on MDS switch is added to the Port Channel.
    If its not created on UCS, it will just not become the status "up"

  • Fabric Port Channel

    Hello,
    Once in production, when adding cables in a Fabric PortChannel between an IOM and a FI, ¿is it needed to re-ack the chassis? (so that, we'll have downtime of the whole chassis). Or rather, as it is a Port-Channel the cables are detected automatically, so that it is not needed to re-ack, and so there's no downtime at all...which one is the correct statement?
    Thanks,

    Hello,
    Let us consider following scenario on adding or removing links to existing deployment.
    Initial deployment
    UCSM 2.0, FI 62XX ,2208 IOM and 2 physical links with port channel configuration ( 2 link discovery policy )
    Change
    1) If additional links are added and if they need to be utilized and part of port channel, we need to re-ack the chassis.
    2) If a link goes down,traffic is distributed across other links in port channel and does not require re-ack. Parameters like bandwidth, VIF ports that are calculated based on initial configuration remains the same.
    3) If we physically remove the additional links between IOM / FI, re-acknowledment would create port-channel with original two links.Failure to re-ack will create over subscription ( bandwidth, available VIF ports ) of the network links.Re-ack is not mandatory but it creates appropriate configuration that matches required design criteria.
    Caution
    Adding or removing links  from a fabric port channel is disruptive and may affect the available amount of VIF namespace.
    http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_0101.html#concept_5D3D88341BFB43468B62B5A77876C67B
    Padma

  • Xconnect 20Gb Port-channel over MPLS Possible?

    Can anybody confirm if you can establish an Xconnect between two 20Gb port-channels (2x 10Gig bundle).  The core is 40Gig and running MPLS.  We have many gigabit pseudowires running over it already.
    Our intention is to terminate 10Gig server traffic on 4900M's and then have a 20Gb Port channel trunk link into a 6500 (which is part of the MPLS cloud).   We would then issue the xconnect directly on the 20Gig port channel in order to traverse the MPLS Core.
    Has anyone configured this before?  Are there any caveats to watch out for?  What sort of performance hit (if any does) xconnect functionality have on 10Gig Traffic.

    Hi,
    Yes it's supported but test it first (as always ;-) )
    HTH
    Laurent.

  • Port-channel - type Peer STP

    Hello,
    We have two Catalyst 4006 as core switchs in our network. Other access layer and server layer switchs (also Catalyst 4006) connect to the two core switchs; two Gigabit Ethernet links between one layer switch and one core switch form a port channel.
    Now I add one Catalyst 4507 switch in the backbone, Il connects to each core switch by two GE links formed a port channel. The show spanning-tree command presente different port-channel type for the older(P2P Peer STP and the new port-channel (PO31, only P2P, not peer STP).
    CDP-CO-SW-S17-01#sh spanning-tree vlan 2
    VLAN0002
    Spanning tree enabled protocol rstp
    Root ID Priority 8192
    Address 000a.418b.0401
    This bridge is the root
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Bridge ID Priority 8192
    Address 000a.418b.0401
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Aging Time 300
    Interface Role Sts Cost Prio.Nbr Type
    Po21 Desg FWD 3 128.661 P2p Peer(STP)
    Po22 Desg FWD 3 128.662 P2p Peer(STP)
    Po23 Desg FWD 3 128.663 P2p Peer(STP)
    Po24 Desg FWD 3 128.664 P2p Peer(STP)
    Po25 Desg FWD 3 128.665 P2p Peer(STP)
    Po26 Desg FWD 3 128.666 P2p Peer(STP)
    Po31 Desg FWD 3 128.671 P2p
    Po44 Desg FWD 3 128.684 P2p Peer(STP)
    Po45 Desg FWD 3 128.685 P2p Peer(STP)
    What does the type Peer STP means? I made the same configuration for PO31 like the other port-channel, why it is not in Peer STP type?
    Thank you.
    Jessie Dong

    Hi Jessie,
    You are running RSTP, which sends version 2 BPDUs. If the switch receives on a port version 0 BPDU (i.e. regular STP BPDUs), it will go to an STP compatibility mode and will start sending version 0 BPDUs on this port.
    So basically, what you are seeing is that all your neighbors are running STP, except the one connected to Po31 who is running RSTP.
    Regards,
    Francois

  • How to configure a port channel with VLAN trunking (and make it work..)

    We're trying to configure a port channel group with trunked ports to connect a NetApp HA pair. We want to create two data LIFs and connect them to the switch stack.  We are trying to create 2 data lifs, one for cifs and one for nfs that are on different vlans.
    We want the same ports to be able to allow multiple vlans to communicate. (trunked)
    These data lifs should be able to fail over to different nodes in the HA pair and still be able to communicate on the network.
    What this means is that we have to connect 4 ports each for each node in the NetApp HA Pair to the switches and create a port channel of some type that allows for trunked vlans. When we configure the ports, the configuration is as follows (below):
    We are only able to configure an IP on one of the vlans.
    When we configure an IP from another vlan for the data lif, it does not respond to a ping.
    Does anyone have any idea what I'm doing wrong on the Cisco switch?
    interface GigabitEthernet4/0/12
    description Netapp2-e0a
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    channel-protocol lacp
    channel-group 20 mode active
    end
    interface GigabitEthernet4/0/13
    description Netapp2-e0c
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    channel-protocol lacp
    channel-group 20 mode active
    end
    interface GigabitEthernet6/0/12
    description Netapp2-e0b
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    channel-protocol lacp
    channel-group 20 mode active
    end
    interface GigabitEthernet6/0/13
    description Netapp2-e0d
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    channel-protocol lacp
    channel-group 20 mode active
    end
    interface Port-channel20
    description Netapp2-NFS
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    spanning-tree portfast
    spanning-tree bpduguard enable
    end

    Our problem was fixed by the storage people.  They changed the server end to trunk, and the encapsulation / etherchannel.
    I like all the suggestions, and they probably helped out with the configuration getting this to work.
    Thanks!
    interface Port-channel20
    description Netapp2-NFS
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    switchport mode trunk
    interface GigabitEthernet4/0/12
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    switchport mode trunk
    channel-protocol lacp
    channel-group 20 mode active
    interface GigabitEthernet4/0/13
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    switchport mode trunk
    channel-protocol lacp
    channel-group 20 mode active
    interface GigabitEthernet6/0/12
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    switchport mode trunk
    channel-protocol lacp
    channel-group 20 mode active
    interface GigabitEthernet6/0/13
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    switchport mode trunk
    channel-protocol lacp
    channel-group 20 mode active

  • Difference between Trunk links and port channel

    Hi 
    Can anyone please explain me the difference between the Trunk links and Ether channel ?

    Disclaimer
    The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
    Liability Disclaimer
    In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
    Posting
    As the other posters have already described, in Cisco parlance, a "trunk" is a link that carries VLAN tagged frames.  (Note, Cisco has two technologies for these, ISL [old/proprietary] and IEEE 802.1Q [vendor independent].)  An Etherchannel (also called a port-channel) is one logical link that includes one or more physical links.  (Note, although Etherchannel can run across just one link, normally more than one link is configured.  Older and most Cisco implementations support up to 8 links in one channel bundle.  There's also multiple Cisco technologies that support Etherchannels, such as manual/PAgP[Cisco/old]/LACP[IEEE 802.3ad].)
    Trunk links might also be configured on an Etherchannel link.

  • Do I configure spanning-tree port type ed trunk on LACP port-channels

    Hello,
    Can't seem to see a clear answer and wondering if something could offer some advice please?
    We are using LACP aggregation across all our 10 gig attached servers and also trunking them.  We're running a VPC pair of 5596 Nexus.
    For a standard trunk port I always add the spanning-tree port type edge trunk to the interface config.
    However I think I should be adding this to the overiding port-channel config.  At present a colleague has configured the VPC below omitting the spanning-tree port type config.
    interface port-channel100
      description a-server
      switchport mode trunk
      switchport trunk allowed vlan 100
      vpc 100
    The port member configs are these which do contain the spanning tree port type:
    interface Ethernet1/1
      description a-server(1)
      switchport mode trunk
      switchport trunk allowed vlan 100
      spanning-tree port type edge trunk
      channel-group 100 mode active
    I always try to keep the overiding port channel config the same as its members and obviously for most config, you can't have disparate configs anyway.
    However for the spanning tree config the NexOS allows you to have the members with spanning tree port types and not have to reflect that in the port-channel.
    However I have this issue with STP:
    Switch1# show spanning-tree interface po100
    Vlan             Role Sts Cost      Prio.Nbr Type
    VLAN0100         Desg BKN*200       128.4996 (vPC) Network P2p *BA_Inc
    Is this due to the inconsistency with my port channel to member configs?
    Any advice would be gratefully accepted.
    Thanks!

    Hi Paul, there are some parameters you can define on individual ports and there are some of them that will be inherited from the port-channel configuration no matter what has been configured under the infidividual ports. Spanning-tree configuration is one of the inherited ones. As soon as the port joins into a port-channel, it will start to use spanning-tree settings under the port-channel. When it leaves the channel, then it can continue to use the individual configuration.
    There is a nice summary here under NX-OS Interface Conf Guide > Port-Channel Conf:
    http://www.cisco.com/en/US/docs/switches/datacenter/sw/6_x/nx-os/interfaces/configuration/guide/if_portchannel.html#wp1798338
    Evren

  • HSRP over L3 port-channel, switches do not ping each other

    Hello guys, 
    I have a L3 port-channel between 2 gigabit ethernet interfaces (one per switch Catalyst 6509), towards two giga interfaces in another two Catalyst 6509 in the other end. The port-channel is configured as follows in one of the ends (the first pair of 6509): 
    interface GigabitEthernet3/37
     description Conexion 
     no ip address
     channel-group 8 mode on
    interface GigabitEthernet3/38
     description Conexion 
     no ip address
     channel-group 8 mode on
    For each Catalyst 6509, the port-channel 8 has a HSRP group, 254. In one of the Catalyst (Central-1) the IP assigned is 192.168.254.253/24 and in the other (Central-2), 192.168.254.254/24. Here is the conf for one Catalyst 6509 (Central-1): 
    interface Port-channel8
     description CENTRALES
     ip address 192.168.254.253 255.255.255.0
     no ip redirects
     no ip unreachables
     no ip proxy-arp
     no ip route-cache
     load-interval 30
     standby delay minimum 20 reload 300
     standby preempt delay minimum 120
     standby 254 ip 192.168.254.254
     standby 254 timers 1 3
    As you can see, HSRP group 254 is defined and it is answering from L3, (from any host or switch, for the 3 IPs), but my doubt is about the HSRP behaviour between both Catalyst. They can't find which one is the master and in fact, they can't ping each other. The status of the group defined for po 8 is: 
    CENTRAL-1#sh standby port-channel 8
    Port-channel8 - Group 254
      Local state is Active, priority 100
      Hellotime 1 sec, holdtime 3 sec
      Next hello sent in 0.865
      Virtual IP address is 192.168.254.254 configured
      Active router is local
      Standby router is unknown
      Virtual mac address is 0000.0c07.acfe
      5 state changes, last state change 2w3d
      IP redundancy name is "hsrp-Po8-254" (default)
    CENTRAL-2#sh standby port-channel 8
    Port-channel8 - Group 254
      Local state is Active, priority 110
      Hellotime 1 sec, holdtime 3 sec
      Next hello sent in 0.645
      Virtual IP address is 192.168.254.254 configured
      Active router is local
      Standby router is unknown
      Virtual mac address is 0000.0c07.acfe
      5 state changes, last state change 6w1d
      IP redundancy name is "hsrp-Po8-254" (default)
    A "sh standby br" shows each switch considers itself the master and does not know the standby. 
    The thing is both switches have not an interface to connect L3 from network 192.168.254.0/24 directly. I mean, they only have one interface connected to the other end of the etherchannel, but not between them. Is this the reason why they can't ping each other, and consequently, they can't properly use HSRP group? 
    Could you tell me which could be a solution to this issue? I can't guess what can be done since the physical interfaces gi3/37 and gi3/38 exist and I think no any other interface should be configured in this network (192.168.254.0/24). 
    Thank you very much in advance. 

    Hello Jon, 
    Thank you very much for your answer. For the 3 possibilities, I answer you: 
    1) The pair are interconnected with a L2 trunk but the thing is this network, 192.168.254.0/24, is not associated to a vlan, but to a L3 etherchannel, so there is no way to associate it to a VLAN, am I right? 
    2) The other end of connections I think is configured at L3 too. 
    3) I am pending to know about the other end, but I think it is L3 too. 
    Anyway, although you have been very clear, try to imagine just 2 switches connected towards another 2 by one interface per each: 
    Central-1: gi3/37 ---> Ext1: gi1/20
    Central-2: gi3/38 ---> Ext2: gi1/30
    If etherchannel from Central is L3, I do not know how to include this traffic in vlan 2.... 
    Well, I keep on thinking. Thank you very much. 

Maybe you are looking for