Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: mitelrocks on May 20, 2014, 09:09:15 AM
-
Hi everyone -
Tech here accidentally disabled the L2 switch port instead of disabling VLAN tagging. As soon as this was done, all IP connectivity to the MCD controller was lost (of course!). We have no earthly idea how to turn back on the L2 switch port - this has to be done in Vxworks somehow. We have rebooted the box and noticed that during vxworks booting, we noticed that there is a warning message that the L2 switch port is turned off (constant pings to the MCD controller confirm this). Does anyone know of a vxworks command to turn back on the L2 switch port. We noticed there is a command called "ifShow", and it lists motfcc as one of the network interface cards..but that's it. We have a recent backup of the database, and we are prepared to re-install MCD software if we have to. Just doesn't seem right that the MCD software allows you to easily disable the port without being able to re-enable it quickly. Box is a MXe III running MCD 5.0.
-
Pretty sure this can be done from the RTC command shell (or serial port in this case), but I don't know the command. I would have the tech get on the phone to tech support ASAP, once he gets to a tech on the phone the fix should be pretty quick.
-
I believe the command is
vlan_off
or vlan_on
Ralph
-
I believe the command is
vlan_off
or vlan_on
Ralph
This will re-enable the L2 switch? Thought the OP said they disabled the whole switch, not just VLAN support.
-
This will re-enable the L2 switch? Thought the OP said they disabled the whole switch, not just VLAN support.
Dunno. It's all I've got at the moment though.
Ralph
-
We tried the 'vlan_off' / 'vlan_on' commands - and vxworks does confim the command, but it does not 'enable' or 'disable' the L2 switch port. We issued the command 'vlan_off' and then rebooted the MCD box - no effect.
-
From the command line can you ping the controllers IP?
Ralplh
-
No, from a Windows box here, we cannot ping the controller IP.
-
Little more detail - we are consoled into the MCD controller. On a Windows box, I setup a constant "ping" going to the MCD controller (but no ping replies back). OK, so we turned off the MCD. After you turn on the MCD, you see the memory check and system check, then Vxworks starts (press space bar, 7,6,5, etc) as soon as Vxworks starts up the pings work for about 4 seconds and then they stop, and they never start up again. At the point that the pings stop we see in the console window the status that the L2 switch was disabled. Will reach out to Mitel...
-
I suspect you're going to be reloading.
Put a serial cable on the console and watch what happens when it reboots.
9600,8,N,1
Ralph
-
On second thought, it's obvious you already have a cable on it.
Try pinging itself.
The command would be
ping "<ip addr>"
Ralph
-
Thanks for the replies!
A ping to itself shows no replies (from vxworks command prompt), after system boots. Planning to re-install....
-
Make sure the L2 switch has an IP address.....
-
Why would there be an option to disable the internal L2 switch? That is kind of ridiculous if it locks you out of the switch entirely... There has to be an easy way to re-enable it... did you call tech support?
-
Enter bootChange and hit return through the options.
Post the results here.
Let us know what the IP address should be.
I'm suspecting the IP was changed.
Ralph
-
results of bootChange:
Boot device : ata=0
processor number: 0
host name:
file name: /partition4/RTC8260
inet on ethernet (e): 192.168.1.20:fffffc00
inet on backplane (b):
host inet (h): 192.168.3.252
gateway inet (g): 192.168.1.1
user (u): IUSR
ftp password:
flags (f): 0x0
target name (tn):
startup script:
other: qefcc
Which matches what it should be. MCD should be at .20
FYI - Had the tech show me on other MCD what exactly he did. It's shockingly easy to do. Go to
LAN/WAN configuration. Click on Layer 2 Switch. In the right side bottom window will be a split area, which is labled "L2 ports". There are two listed of course for your 2 10/100 ports. Click on button "change member" which will open a new window and have Port 1 selected. There are different options listed such as "State" (enabled/disabled) "speed" (auto) "duplex mode" (auto), "flow control" (auto), and the most important one "voice vlan" (untagged/tagged/no). Instead of changing tagged to untagged, he clicked on "disabled" option for State.
-
Silly question but have you tried connecting to the second ethernet port?
-
I'm baffled. There has to be a command line option to re-enable.
Have you reached out to Mitel yet?
Let us know what the final fix is.
This is something I'll need to add to my notes.
Ralph
-
Great question - and yes we did connect the 2nd ethernet port, and nothing. It seems like it should have worked, given that there are two ports and two options (under L2 ports to disable). I had the tech contact Mitel and (of course) part of their system was down so they were not able to open a ticket, and they were supposed to call us back. I did open a TechCentral ticket tho. We were a bit pressed for time, so I made the call to re-install MCD and restore the system. It took about 15 minutes for the install/restore and all is well again. I am really curious to try the 2nd ethernet port again (somehow!). Looking back perhaps we missed something. I'll post whatever we get back from Mitel.
-
Just as a follow up, Mitel confirmed there is no vxworks command to turn on the Layer 2 switch ports. However, Mitel says this issue was fixed in versions > 11.0.1.10 as you cannot turn off port 1. Even though it looks like you can (it should be greyed out).