Brocade Fibre Channel Networking Community

Expand all | Collapse all

CP not reachable

  • 1.  CP not reachable

    Posted 10-24-2016 10:50 PM


    How to find out the Bad CP.  CP0 is unreachable and we are suspecting might be faulty. Any commands or troubleshoot to confirm it.
    Local CP (Slot 7, CP1): Active, Warm Recovered
    Remote CP (Slot 6, CP0): Standby, Healthy
    HA enabled, Heartbeat Up, HA State synchronized

    As of now we are accessible mgmt ports VIa CP1.

    Model: DCX 8510-8


    Error:


    CP in Slot 6 set to faulty because CP ERROR asserted.
     CP in slot 6 not faulty, CP ERROR deasserted.


    #badcp
    #DCX8510
    #cp0
    #ha
    #CP
    #cp1
    #BrocadeFibreChannelNetworkingCommunity


  • 2.  Re: CP not reachable

    Posted 10-25-2016 12:35 AM

    @balaji.chitiraivel7

     

    slot 6 on DCX is the first CP left.

     

    what say "slotshow" output ?

     

    if the CP in slot 7 is Active and the switch is running, you can try with care to power off the Faulty CP and then power on, if the problem persist, i would suggest to open a case with Support


    #BrocadeFibreChannelNetworkingCommunity


  • 3.  Re: CP not reachable

    Posted 10-25-2016 04:55 AM

    Hi balaji.chitiraivel,

     

    in the haShow output, which I assume is from the active CP (1) currently (?) you have

     

    Local CP (Slot 7, CP1): Active, Warm Recovered
    Remote CP (Slot 6, CP0): Standby, Healthy
    HA enabled, Heartbeat Up, HA State synchronized

     

    this means that CP0 is active, and healthy.  If you have seen the below sequence of errors

     

    1. CP in Slot 6 set to faulty because CP ERROR asserted.
    2. CP in slot 6 not faulty, CP ERROR deasserted

    which typically happens when a CP is rebooted, I would say that you CP0 is running and healthy.

    The CP errors was deasserted or negated.  

     

    Now, if you are not able to ping CP0, but CP1, then I would troubleshoot the connectivity of CP0, first.


    #BrocadeFibreChannelNetworkingCommunity


  • 4.  Re: CP not reachable

    Posted 10-26-2016 01:40 AM
    Thanks Martin. Will check the connectivity.
    #BrocadeFibreChannelNetworkingCommunity


  • 5.  Re: CP not reachable

    Posted 03-08-2017 08:40 AM

    Hello Balaji,

     

    We had the same issue.

    We were using 100M network switches to manage brocade DCX which are 1GE management ports.

    We changed setting on brocade directotr not to Auto-negotiate and the problem solved


    #BrocadeFibreChannelNetworkingCommunity


  • 6.  Re: CP not reachable

    Posted 10-26-2016 01:07 AM

    Thanks Anthony,

     

    Please find the below details:

     

    Slot   Blade Type     ID    Status
    -----------------------------------
      1     SW BLADE     96     ENABLED
      2     SW BLADE     96     ENABLED
      3     SW BLADE     96     ENABLED
      4     SW BLADE     96     ENABLED
      5     CORE BLADE   98     ENABLED
      6     CP BLADE     50     ENABLED
      7     CP BLADE     50     ENABLED
      8     CORE BLADE   98     ENABLED
      9     SW BLADE     96     ENABLED
     10     SW BLADE     96     ENABLED
     11     SW BLADE     96     ENABLED
     12     SW BLADE     96     ENABLED


    #BrocadeFibreChannelNetworkingCommunity