This is urgent. I need assistance. I have a Mitel ICP 3300 that won't boot. I have changed the ip addressing scheme and dhcp addresses for the phone switch. It gets it's IP from a novell dhcp server. Our main switch won't boot up. I know this is a vague description, I need ideas on where to begin.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
MITEL ICP 3300 won't boot - HELP. 4
- Thread starter advancex
- Start date
TheMitelGuy
IS-IT--Management
Is the 3300 IP's address static? Do you know what it could be? Do you have a serial cable? Do you have any dnic phones? Do any of them boot up?
Neil
Neil
- Thread starter
- #3
Hey TheAvayaGuy, Thanks for replying. Te IP address is static. We have a serial cable and we have IP phones that boot up almost all the way - the display and error waiting for server link. We know what address is and we can ping it successfully. When using serial cable to terminal session switch, the device stops at systemdiscovery:: mmcinfo retrieving mmc table.
Thanks.
Thanks.
-
1
- #4
does your 3300 have an et2 card, if so you need to change the ip address for this also.
can you log onto the system via the serisl cable or via the web browser.
if you can log on to your system and it's just the ip phones you have the problem with, it's more likely to be your dhcp server which will need the scope options changed to the new ip addresses you have changed to?????
hope this is of some help!!!!!!!!!
can you log onto the system via the serisl cable or via the web browser.
if you can log on to your system and it's just the ip phones you have the problem with, it's more likely to be your dhcp server which will need the scope options changed to the new ip addresses you have changed to?????
hope this is of some help!!!!!!!!!
- Thread starter
- #5
-
1
- #6
Every 3300 has an E2T, it's the IP gateway to the TDM side of the switch. The E2T usually takes up the first address in the DHCP scope.
I'd be willing to bet the phones aren't booting up because the DHCP settings aren't right. Make sure DHCP options 128, 129, and 130 are set correctly. 128 should be the TFTP server where the IP set firmware is at (default is the IP address of the RTC), 129 is the RTC IP address, and 130 needs to be set for "MITEL IP PHONE" so the IP set knows that the DHCP offer is for the phone.
I'd be willing to bet the phones aren't booting up because the DHCP settings aren't right. Make sure DHCP options 128, 129, and 130 are set correctly. 128 should be the TFTP server where the IP set firmware is at (default is the IP address of the RTC), 129 is the RTC IP address, and 130 needs to be set for "MITEL IP PHONE" so the IP set knows that the DHCP offer is for the phone.
Yes LUNDAH every 3300 does have an e2t, however as i asked does the system have an ET2 CARD, as the LX Controller does and the MX controller does not as this is built in,
Advancex,
I think it might not be your DHCP as you cannot access your Mitel system through the Web Browser, As I mentioned do you have an ET2 CARD as you will probably have to connect to this and change the IP address (Do you have 2 Lan ports, this will be a MX Controller) (Do you have 4 Lan ports, this will be a LX controller and have an E2T CARD)
If you have an LX Controller with E2T CARD there's a connection on the under side of the system (to which you need a mouse type connection)
If you have an MX Controller without the E2T CARD you can change the setting on the maintenance port.
Advancex,
I think it might not be your DHCP as you cannot access your Mitel system through the Web Browser, As I mentioned do you have an ET2 CARD as you will probably have to connect to this and change the IP address (Do you have 2 Lan ports, this will be a MX Controller) (Do you have 4 Lan ports, this will be a LX controller and have an E2T CARD)
If you have an LX Controller with E2T CARD there's a connection on the under side of the system (to which you need a mouse type connection)
If you have an MX Controller without the E2T CARD you can change the setting on the maintenance port.
- Thread starter
- #8
Andy4uk,
you are correct. We are in the process of trying to find that cable now. Problem is we are in the BVI and computer store or electronic store has that cable. I have taken the the 3300 cover off and removed hd, but still can't find e2t card. I will have to proceed with dismantililing all cards and cables.
you are correct. We are in the process of trying to find that cable now. Problem is we are in the BVI and computer store or electronic store has that cable. I have taken the the 3300 cover off and removed hd, but still can't find e2t card. I will have to proceed with dismantililing all cards and cables.
- Thread starter
- #9
advancex
On the underside of the Controller you will see a couple of Large silver round clips remove them with a small flat headded screw driver you will see PS/2 connection, you will need a PS/2 to serial which as far as i am aware you can only get from mitel.
The other thing to try is to narrow your DHCP server down to only 2 IP addresses reboot your 33000 and see if the E2T card picks 1 of those addresses up try pinging if you get a echo reply attempt to secure telnet to that ip address
On the underside of the Controller you will see a couple of Large silver round clips remove them with a small flat headded screw driver you will see PS/2 connection, you will need a PS/2 to serial which as far as i am aware you can only get from mitel.
The other thing to try is to narrow your DHCP server down to only 2 IP addresses reboot your 33000 and see if the E2T card picks 1 of those addresses up try pinging if you get a echo reply attempt to secure telnet to that ip address
As ianuk1974 said the location is under one of the silver clips,
I made up a lead from getting a PS/2 8 pin male (this end connects to the underside) to 25 pin male and a 25 pin female to 9 pin female connect the 25 pin coneectors together and the 9 pin to your com port. This will then give you a connection, which will be the same set up as if you where connected to the maintenance port.
These connectors i got from Maplins? don't know if you have one of these local to you?
I made up a lead from getting a PS/2 8 pin male (this end connects to the underside) to 25 pin male and a 25 pin female to 9 pin female connect the 25 pin coneectors together and the 9 pin to your com port. This will then give you a connection, which will be the same set up as if you where connected to the maintenance port.
These connectors i got from Maplins? don't know if you have one of these local to you?
- Thread starter
- #12
-
1
- #13
advancex,
The quickest way to get your system up and running again is to change the address back to the original ip you had it set at before. Then the PBX should boot up and you will be able to access the web page. If your 3300 software is older (and it probably is because loads 3.3 or 4.0 and higher do not need the e2t settings in order to boot up) the e2t may be looking for the proper dhcp settings in order to run. The e2t uses options 66 and 67 in dhcp to boot if it is not set staticly. The settings are as follows;
066 ASCII String (typically the IP address of the controller RTC)
067 ASCII String /sysro/E2T8260 for 250/700=user or
/sysro/Lite8260 for 100-user controller
Check these options in you novell scope to see if they are correct. There may also be a reservation for the e2t as well.
You can get the serial cable from a vendor, which by the way must not be on the greatest terms with you, otherwise I would think you would have called them or had them make the change so you would not be in this boat.
If you have a VLAN set up on your system the best thing to do is enable DHCP on the 3300 and have that assign the address to the E2T because it is then only dependant on it self. It can also then hand out the addresses to the sets and not interfere with your data lan.
Now once you get up and running, make sure you upgrade your software so that the PBX will at least boot! You'll find that it will be a lot faster too. Those older releases that needed the e2t to boot first were slooooww.
The quickest way to get your system up and running again is to change the address back to the original ip you had it set at before. Then the PBX should boot up and you will be able to access the web page. If your 3300 software is older (and it probably is because loads 3.3 or 4.0 and higher do not need the e2t settings in order to boot up) the e2t may be looking for the proper dhcp settings in order to run. The e2t uses options 66 and 67 in dhcp to boot if it is not set staticly. The settings are as follows;
066 ASCII String (typically the IP address of the controller RTC)
067 ASCII String /sysro/E2T8260 for 250/700=user or
/sysro/Lite8260 for 100-user controller
Check these options in you novell scope to see if they are correct. There may also be a reservation for the e2t as well.
You can get the serial cable from a vendor, which by the way must not be on the greatest terms with you, otherwise I would think you would have called them or had them make the change so you would not be in this boat.
If you have a VLAN set up on your system the best thing to do is enable DHCP on the 3300 and have that assign the address to the E2T because it is then only dependant on it self. It can also then hand out the addresses to the sets and not interfere with your data lan.
Now once you get up and running, make sure you upgrade your software so that the PBX will at least boot! You'll find that it will be a lot faster too. Those older releases that needed the e2t to boot first were slooooww.
- Thread starter
- #14
HI guys, i need to change the ip address on my both controllers, one in productoin the other like failover, i have the seria cable, BUT when i reboot the controller i never got the prompt or something, the configuration that i used is the default setting 9600 etc.
I dont know what is wrong
I hope you help
Thanks in advanced.
I dont know what is wrong
I hope you help
Thanks in advanced.
-
1
- #16
You need to access VXWorks by doing the following:
Terminal Program set for VT-100 emulation, ASCII, 9600, N-8-1 baud.
Use a 9 pin serial cable connected to the MAINTENANCE port on the front of the 3300 Controller (I am assuming that it is a 3300 ICP) and to a serial com port on your PC.
Reboot the controller. At this point you should be getting boot information on the screen, stuff like memory tests etc... IF you don't see anything, check the above stuff.
Wait until you see the prompt "Press <SPACE><SPACE><SPACE> to stop auto-boot AFTER countdown starts..." Depending on the software version you may get a prompt to press "any key" to stop auto-boot instead.
If you were successful in stopping the boot, you should see a "[VxWorks Boot]:" prompt.
Basic commands:
p = display the boot parameters
c = change the boot parameters
. = clear field
- = go to previous field
'enter' key will scroll to next field when changing boot parameters.
You will need to change the "inet on ethernet (e) : 192.168.1.2:ffffff00" field. What is shown is default. Remember to include the subnet field (ffffff00) when changing.
If you have an LX controller that previously had the E2T card statically set by using a debug cable, you will have to change the IP address there as well. If you were using the internal DHCP server, remember to update the static entry for the E2T card there.
Hope that helps.
Terminal Program set for VT-100 emulation, ASCII, 9600, N-8-1 baud.
Use a 9 pin serial cable connected to the MAINTENANCE port on the front of the 3300 Controller (I am assuming that it is a 3300 ICP) and to a serial com port on your PC.
Reboot the controller. At this point you should be getting boot information on the screen, stuff like memory tests etc... IF you don't see anything, check the above stuff.
Wait until you see the prompt "Press <SPACE><SPACE><SPACE> to stop auto-boot AFTER countdown starts..." Depending on the software version you may get a prompt to press "any key" to stop auto-boot instead.
If you were successful in stopping the boot, you should see a "[VxWorks Boot]:" prompt.
Basic commands:
p = display the boot parameters
c = change the boot parameters
. = clear field
- = go to previous field
'enter' key will scroll to next field when changing boot parameters.
You will need to change the "inet on ethernet (e) : 192.168.1.2:ffffff00" field. What is shown is default. Remember to include the subnet field (ffffff00) when changing.
If you have an LX controller that previously had the E2T card statically set by using a debug cable, you will have to change the IP address there as well. If you were using the internal DHCP server, remember to update the static entry for the E2T card there.
Hope that helps.
MitelInMyBlood
Technical User
By the way, those are zeroes at the end of the ffffff string, not "Oh's"
Also, there are instructions on how to build your own E2T cable that can be found in the FAQ for this group.
Also, there are instructions on how to build your own E2T cable that can be found in the FAQ for this group.
- Status