Netvanta 1534P (Gen 2.1) possible corrupt boot

[Anonymous]

Hi, my name is Nathaniel.

     My company recently purchased a Netvanta 1534P (Gen 2.1) and when we booted it up we got this issue in the picture.

     When I boot it up only the ports 25 - 28 (SPF ports i think) turn on and stay yellow. All other lights do no turn on.

     I know it is a hardware issue, but I would like to know how it happened. Before this issue occurred, it was shipped to our office. I took out of the box and set it up using a mix between GUI and CLI interfaces. Packaged it back up and sent it to the client location.

The technician on-site mounted it on the rack and plugged it in to a UPS. That is when the issue started to happen. We already removed the UPS and plugged it straight into the wall. This did not fix the issue. Is there anyway to figure out what happened? Right now I am just thinking that it was broken during Delivery to the client location.

[Anonymous · Accepted solution]

deltranathaniel:

Thank you for asking this question in the support community.  Unfortunately, it is difficult to determine what happened based on the information you provided.  I recommend opening a ticket with ADTRAN Technical Support.  They can direct you where to go to determine the failure analysis.

- Open a webticket by clicking on this link: https://www.adtran.com/openacase

- Open a ticket by emailing support@adtran.com

- Open a ticket by phone by calling 1-888-423-8726

Levi

[Anonymous]

I did put in a support ticket and they have replaced it. I was wondering if anyone else has run into this problem before. I just wanted to makes sure it was a hardware issue.

[Anonymous]

Not sure if it is related, but i recently put a 1534 2.1 into production.  On first boot, the unit failed.  After watching the boot up on the console port, i saw that it was stuck in bootstrap due to a bad copy of the primary firmware.  I set it to boot on the other copy that was already on flash, and the unit booted fine.  This is the first time i have ever seen an issue like this, but was simple to resolve.  I removed the corrupt image and upgraded anyways.

[Anonymous]

This is similar, but the issue did not occur on first boot. It actually occurred after i had set everything up. I even rebooted a few times while it was in my office before i sent on-site. Although, I am pretty sure i upgraded the firmware.