No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade
Knowledge Base

CE12804S 40G Port not coming UP

Publication Date:  2020-01-14  |   Views:  116  |   Downloads:  0  |   Author:  k00316728  |   Document ID:  EKB1100044599

Contents

Issue Description

Port was not coming UP when connected 40G from CE12804S to CE6800. 

 SFP model used for connection : - Part : - 02311PUU Model : -  QSFP-40G-SDLC-PAM

 

1986447c2d62401481d3756ca7be4bf1

Alarm Information

* port not showing UP in display interface brief 

* also display transceiver verbose we see no RX Power. 

 

2791c5221fd440c9b6093b0287c0df69

 

18f0519fd426454887b271ea673f222d

Handling Process

  • for troubleshooting we tested local Loop on CE6800 and CE12804S as below

1. CE6800 <---- 40G Fiber ----- >  CE6800              || UP successful

2. CE12804S <---- 40G Fiber ----- >  CE12804S         || NOT UP 

from above test cable and SFP is fine. seems issue on CE12804S

 

  • on CE12804S from display alarm and display logbuffer we can see resource-mismatch error for all interface. 

 

13d37eb4df184591ad78712af740c1e4

 

 

9406a8386211401aa80e1bb8e7ba8170

 

 

Root Cause

from document we we can see the resource mismatch cause and solution. 

resource-mismatch: In LPU connection mode, if a stack card has different resource modes than the configured ones during startup, or the port split configurations are inconsistent, all service ports except physical member ports on the stack card will be set to Down. Resource modes include extended TCAM resource mode, ARP resource allocation mode, TCAM ACL resource mode, extended Layer 3 forwarding resource mode, tunnel mode, NVO3 ACL extension mode, card interoperability mode, card enhance mode (sFlow), card enhance mode (NetStream), large Layer 3 interface mode, EEDB resource mode, and Eth-Trunk quantity.

 

5b55e142be8c462387467669db456d65

Solution

reset the Card where the error has occurred. 

after reset port was up and working fine. 

 

 

9198ab452bac4bd281f0846cbe71e947