Invalid Response

This has really just been my luck so far this week.  I turn on our new Avocent MergePoint 5300 to start the configuration.  Go into the configuration via the console port:

  1:Summary
  2:Network config
  3:Set date and time
  4:Set admin password
  5:Reboot
  6:Power off
  7:Roll back the version
  8:Security config
  9:Debug Log
  10:Restore to Factory Defaults
  0:Exit
  Please select [0 - 10]:

Fair enough, right?  All I need to do is set up the IP address so I can jump into the configuration website so I select “Network Config”.

  Set eth1 Speed:
  1:Auto-Negotiate
  2:10 Mbps/Half Duplex
  3:10 Mbps/Full Duplex
  4:100 Mbps/Half Duplex
  5:100 Mbps/Full Duplex
  0:Return
  Current Setting [Auto-Negotiate]
  Please select [0 - 5]:1

Set eth1 DHCP?(Y/N):N
Invalid response, please input again [YES/NO] -> NO
Invalid response, please input again [YES/NO] -> N
Invalid response, please input again [YES/NO] -> no
Invalid response, please input again [YES/NO] -> n
Invalid response, please input again [YES/NO] ->
Invalid response, please input again [YES/NO] -> YES
Invalid response, please input again [YES/NO] -> yes
Invalid response, please input again [YES/NO] -> y
Invalid response, please input again [YES/NO] -> quit
Invalid response, please input again [YES/NO] -> exit
Invalid response, please input again [YES/NO] ->
Invalid response, please input again [YES/NO] ->
Invalid response, please input again [YES/NO] ->

Apparently there is no known valid response.  How does a product leave QA in this state?  I already hate this thing and I haven’t even set it up yet. 

Tags:

Comments are closed.