Mitel Forums - The Unofficial Source
Mitel Forums => MiVoice Office 250/Mitel 5000 => Topic started by: BlackSunshine on October 04, 2017, 04:57:07 PM
-
I am having problem networking 2 Mitel 250's 6.2 software. I have a VPN tunnel built. Node 1 is 192.168.100.11 and Node 2 192.168.200.11. the node extensions 6002 and 6004. I can open command line on each system and PING each other. However when I try to import either way I get : Operation failed: ERR-Not Reachable......Any Help Appreciated!!
-
Blacksunshine,
Did you use the Networking Wizard or did you manually set up your Networking?
Thanks,
TE
-
I used the Networking wizard. Still can't get it to work. About to pull my hair out
-
When I have issues with networking systems, it's always something that I've fat-fingered.
I know that you've done it a dozen times, but go through everything again. Pay close attention to the node connections, especially since you've picked an unusual numbering plan.
-
I apologize for the crude pictures, but this is my method. Open it in Adobe and rotate the view. Hope it helps
-
I apologize for the crude pictures, but this is my method. Open it in Adobe and rotate the view. Hope it helps
Each system has different IP Connection numbers, right? So one is P6000/P6001and the other is P6010/P6011 or something like that? The numbers cannot match, gets people sometimes.
-
Node 1
System/DeviceandFeatureCodes/Nodes
By default, the system is already Node 1. Nothing to change here.
System/DeviceandFeatureCodes/IPConnections
By default, Processor Module is P6000 and Expansion Card is P6001. Nothing to change here.
System/DeviceandFeatureCodes/Nodes
Here, we define the remote Nodes one at a time. Right click, create remote node. We’re creating Node 2, so use extension 97002. If we were creating Node 3, we would use 97003 unless we had to account for Expansion Cards. System will not reboot, but DB Programming will restart.
System/DeviceandFeatureCodes/NodeIPConnectionGroups
P8000 has been automatically created for Node 2. Put 2 in the description field so you can keep up with which Node this group is for. This description comes in handy when you’re networking multiple nodes.
System/DeviceandFeatureCodes/IPConnections/97002
Right click, create off node ip connection. Create extension P6002 for Node 2. Double click P6002. Modify Remote IP Address to match IP address of Node 2.
System/DeviceandFeatureCodes/Nodes/97002/NodeTrunk/IPConnectionGroups
Right click, Add to Node/Trunk/IPConnectionsGroupsList. Add P8000 that was created for Node 2.
Node 2
System/DeviceandFeatureCodes/Nodes
Change Node number to Node 2. System will reboot.
System/DeviceandFeatureCodes/IPConnections
If you’re not using an Expansion Card, just change the Node 2 Processor Module to extension P6002 like we defined it as on Node 1.
System/DeviceandFeatureCodes/Nodes
Right click, Create Remote Node number 1. Define it as extension P6000. System will not reboot, but DB Programming will restart. ANNOYING!!!!
System/DeviceandFeatureCodes/NodeIPConnectionGroups
Here we see that P8000 has again been created by default. Put 1 in the description field because this group has been created for node 1. See how it gets confusing.
System/DeviceandFeatureCodes/IPConnections/97000
Right click, create off node ip connection. Create extension P6000 for Node 1. Double click P6000. Modify Remote IP Address to match IP address of Node 1.
System/DeviceandFeatureCodes/Nodes/97002/NodeTrunk/IPConnectionGroups
Right click, Add to Node/Trunk/IPConnectionsGroupsList. Add P8000 that was created for Node 1.
Now go to Operations and Export/Import. Always try to Import first. I haven’t had any success Exporting first. I’ve had spotty success with the Network Wizard, so I’ve just abandoned it and used this method.
-
I would delete everything and do it over with the Networking Wizard.
-
I appreciate the help guys. I fixed it finally. I made mistake and thought the node numbers could be the same on local side ...had both 250's as node 1...hard to explain but I had 3300 in my head. Once I thought of each location as a Lab I get it straightened out.
-
Awesome! I once networked 6 locations together and the wizard screwed me big time. That's why I use the method I described to you.
-
I appreciate the help guys. I fixed it finally. I made mistake and thought the node numbers could be the same on local side ...had both 250's as node 1...hard to explain but I had 3300 in my head. Once I thought of each location as a Lab I get it straightened out.
FYI... Can't have duplicate PBX/ICP node numbers in the 3300 either. :)
Sent from my Moto G (5) Plus using Tapatalk
-
Glad that you figured it out. I manually programmed about a half dozen sites about 10 years ago. Once I discovered the wizard, I haven't looked back.
My system is up to 66 nodes, with 4 more sites coming by year's end. I can't imagine adding all those connections manually.