odiefoxydog
Technical User
Hi, hope someone can help.
I'm setting up a CXi II controller for a new customer that was delivered with MCD4 UR2 on the Sata hard drive. I changed the IP address to a 192.168.2.x address (our local LAN address) so I could license it and upgraded it OK to MCD4.1. I then changed the RTC IP address to 192.168.1.253 and the L2 address to 192.168.1.252 ready for the customers LAN. After resetting the controller I couldn't get onto the 3300 on 192.168.1.253 (and yes I had changed my laptop to a static address). On vxWorks it was showing the correct address so I've changed it back to 192.168.1.2 but still no joy. However, on VXWorks I'm getting the following errors constantly:
MIPS LAN Mac address is 08:00:0f:48:73:ac
MIPS Environment Updated
MIPS *** Autoboot: Trying device 'eth0' file 192.168.1.2:vmlinuz (eth0,tftp) ***
MIPS *** Autoboot failed ***
Does anyone know if I can recover from this or is it a case of sending it back to Mitel as DOA?
Thanks
Julie
I'm setting up a CXi II controller for a new customer that was delivered with MCD4 UR2 on the Sata hard drive. I changed the IP address to a 192.168.2.x address (our local LAN address) so I could license it and upgraded it OK to MCD4.1. I then changed the RTC IP address to 192.168.1.253 and the L2 address to 192.168.1.252 ready for the customers LAN. After resetting the controller I couldn't get onto the 3300 on 192.168.1.253 (and yes I had changed my laptop to a static address). On vxWorks it was showing the correct address so I've changed it back to 192.168.1.2 but still no joy. However, on VXWorks I'm getting the following errors constantly:
MIPS LAN Mac address is 08:00:0f:48:73:ac
MIPS Environment Updated
MIPS *** Autoboot: Trying device 'eth0' file 192.168.1.2:vmlinuz (eth0,tftp) ***
MIPS *** Autoboot failed ***
Does anyone know if I can recover from this or is it a case of sending it back to Mitel as DOA?
Thanks
Julie