• Not Answered

Problem with MX controller

I was downloading the version of the controller from the versión 11.3 to 10.3 and suddenly an error appear. Right now I cant see the controller in decommissioned nodes and its flashing lights in a strange way.

Behavior of the lights: The power light its on Solid while the error, active and stand by lights flash. Every ten times these lights flash the active, stand bye, pri and sec flash in a faster strobe way for half a second and then restarst the flashing of the error, active and stand by lights.

Somebody has seen this error?

What can I do to see it again in the network?

I unplugged the controller all night, just to discard a simple error but it didnt worked.

Thanks for the help!!!

ypiedra

10 Replies

  • Redundant or Simplex?

  • In reply to AdrianOffield:

    As Simplex adrian.

    ypiedra

  • In reply to ypiedra:

    Does it  look like?:

    Red LED - On for one second followed by all LEDs on for five seconds.

    -  Unit went through RESET due to an unrecoverable software error.

    - Contact customer support.

    (according to BOL)

    It sounds like you may also need to try to hard decommission by not just powering down the unit, but physically removing it from the backplane for 30 seconds.

    Is the device pingable, and can you establish telnet session?

  • In reply to ypiedra:

    Ouch, did you lose power whilst downgrading?  Was it a commissioned node that you then replaced with a new controller or is this a brand new controller / system?

    We need a bit more detail about your system before commenting.

  • In reply to Youssef.El-Bahtimy:

    Thanks for replying Youssef!!

    I left the controller all night unplugged and out of the back plane, still the error persist.

    I cant ping the device because it is not recognize as a  node.

    Also, it´s flashing in a way that BOL doesnt especify.

    I dont now if there is a different way to recognize the device.

    Thanks for the help!!!

    ypiedra

  • In reply to AdrianOffield:

    Thank for the answer Adrian!!

    I didnt lose power, while the procedure was taking place.

    This controller was being used in a 11.3 system and now I need him in a 10.3 configuration,  thats why I was downgrading him (It´s not a new controller)

    I downgraded other controllers that are working properly in the 10.3 versión. Only this one doesnt want to work!!

    Thanks for the help!!!

    ypiedra

  • In reply to ypiedra:

    Have you tried re-running controller flash upgrade on that controller node? In some cases if there was an error and you exit out of the flash upgrade the next time you try to flash the controller it will attempt to restart the flash step where you had the error.

    BTW, all controllers at decommissioned state will be set to IP address 10.5.255.254. Try to ping this IP, if you get an ICMP (ping) reply but not seeing controllers in the decommissioned lists that means your database server has a problem and you need to restart DVDBServer.

    MX are fairly new, you can easily get warranty replacements for them.

  • In reply to ypiedra:

    ok.  you can't ping through diagnostics, but is it reachable through ping and telnet commands outside of diagnostics (at its last known IP address?)

    It sounds like it's toast.

  • In reply to Youssef.El-Bahtimy:

    Phil, i cant ping him with the addres you provide me. I just realized that the controller has like the NIC card damaged, because any computer cant establish comunication with the device. Its like a hardware issue. I think Youssef was right...

    Someone knows the procedure to report this damage, in order to replace the controller??

    Thanks all for the help!!

    ypiedra

  • In reply to ypiedra:

    Try to contact Emerson LBP or Emerson office in your area - they can give you info regarding procedure...