11-02-2015 04:32 AM - edited 03-08-2019 02:32 AM
Hardware is 6807x with 6800ia, connecting with 10G, using WS-X6904-40G with CVR-CFP-4SFP10G. We recently had two of our fex interfaces trigger an alert Te2/1/13 & Te2/1/14. After investigating I found that an interface in two different fexs dropped into "connecting state".
PACORP-CORE#sh fex 132
FEX: 132 Description: FEX0132 state: online
FEX version: 15.0(2)EX7
Extender Model: C6800IA-48FPDR, Extender Serial: FDO1851I0JR
FCP ready: yes
Image Version Check: enforced
Fabric Portchannel Ports: 1
Fabric port for control traffic: Te1/1/14
Fabric interface state:
Po132 - Interface Up.
Te1/1/14 - Interface Up. state: bound
Te2/1/14 - Interface Up. state: connecting
I opened a case with TAC and provided logs, show tech etc. They suggested a shut/no shut on the interface and if that didnt work then reload the fex. After performing both steps the fex port is still in connecting state. Has anyone seen this issue, or have any suggested trouble shooting steps? Since both ports are on the same module and card, im leaning too a module restart, but because other ports on this module are active I am not sure if this is the best course of action.
Thanks in advance for you help,
Bret
11-02-2015 06:21 AM
Ask TAC to find the root cause and give you a reall answer with real solution. Shut/no shut, reseating modules and rebooting the device is not a solution. The issue will reapear sooner or later.
If you are not geeting the right answer, esculate the ticket and ask to speak to a suprvisor.
HTH
11-02-2015 06:31 AM
You hit that right on the head Reza! That is exactly what I told my TAC engineer. Next steps is to do just that.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide