TEN GIGABIT ETHERNET INTERFACE NOT COMING UP

[derreck]

Hello.

I am trying to enable the Te1/1/1 on a C9200l switch but everytime i key the no shutdown i am not presented with the log message saying state has gone to up. When i shut down the interface it goes to administratively down and when i try to enable the interface its state changes to down

[Leo Laohoo]

---

@derreck wrote:

but everytime i key the no shutdown i am not presented with the log message saying state has gone to up. 

---

Because the other end of the fibre optic is either not enabled or not patched.

Loop the Tx and the Rx port.  The link will come up.

[derreck]

Hello. 

Currently there is a fortiswitch which we are using for testing within the environment, when i plug the sfp into the switch it blinks and thus signifies there's traffic flowing. The other side has been connected to an ODF. When i connect myself to the L2 fortiswitch i am able to ping my gateway and have internet access. I am trying to set up the C9200l so that it replaces the fortiswitch

[marce1000]

 - Make sure a compatible SFP  is used on the C9200L : https://tmgmatrix.cisco.com/?npf=342
               Also check logs on all involved devices when connection attempts are made , 

 M.

[derreck]

Hi. It is compatible. Im using the SFP-10G-LR-S model

[derreck]

there is no log displayed when i try to enable the interface, a log is diplayed when i shut the interface down showing state has changed to administratively down afterwards, when i try to enable it again, the status changes to down. Refer to the screenshot on the original post

[marce1000]

    >....there is no log displayed when i try to enable the interface, a log is diplayed ...
  - That is not what I mean by looking at the logs , I mean looking at the to  inner logs on the device which can be seen
with the command show logging on the Cisco device ; the idea is that you examine the same info's on the foreign device according to similar commands for that device (consult documentation).

      As stated : use these commands when connection attempts are made on the involved devices ,

 M.

 M.

[marce1000]

               - Are you trying to connect anything to that port , if so elaborate on (w)that (?)

 M.

[derreck]

The other port is a firewall 

[MHM Cisco World]

check the errdisable status 

[derreck]

There was no error displayed . The SFPs are compatible

[MHM Cisco World]

• If both ends of the line support autonegotiation, we highly recommend the default setting of auto negotiation.

• If one interface supports autonegotiation and the other end does not, configure duplex and speed on both interfaces; do not use the auto setting on the supported side.

• When STP is enabled and a port is reconfigured, the device can take up to 30 seconds to check for loops. The port LED is amber while STP reconfigures. As best practice, we suggest configuring the speed and duplex options on a link to auto or to fixed on both the ends. If one side of the link is configured to auto and the other side is configured to fixed, the link may or may not be up and this is expected.
  
  

you share photo show you hardcoded the speed and duplex. 
so there are 
both end support auto no need hardcoded
one end support auto, need hardcoded 

[Kasun Bandara]

@derreck hi, few steps to check,.

1. check #sh int te1/1/1 --- find if any drops in output, duplex, and status for interface and link, and err disable status

2. check #sh int trans detail  -- check if transceiver details are correct and light is not loosing 

3. (use phone camera) check the laser in transceiver and notice the side right or left. and check the patch cable light in same way and make sure its coming from other side which not connect to the same side of transceiver.