vMBG can talk to anything except the Mitel 3300

[ralph]

Here's something I haven't seen before.
vMBG in server mode.
On same subnet as 3300.

I'm servicing this remotely so I use logme in to access a VM PC on the same host as the vMBG.
I can talk to the vMBG from the remote PC to it's internal IP address.
I can talk to the vMBG on it's external IP address.

I can talk to the 3300.

In the vMBG in diagnostics, when I test ICP connectivity it fails.
If I putty in to the MSL and ping the 3300 it fails.

The 3300 can't ping the vMBG.

I'm told there is no firewall between the two and I happen to believe them because they're both on the same subnet using the same subnet mask and gateway.

So bottom line is, it appears that the vMBG and the 3300 can talk to everything accept each other.

Anyone got a clue?   I'm thinking it's something in the VMWare host but I've no idea what that might be.

Ralph

[dilkie]

check to see if there is a route, in both directions, between the 3300 and the mbg.

run traceroute on msl to see what path is used to get to the 3300 and see if it makes it to final hop.

not sure what you can run in vxworks, I'm sure there's something.

[ralph]

They're both on the same subnet so no routing is involved.

Ralph

[v2win]

I know they are both on the same subnet but are they connected?

Can you ping the default gateway on both devices?

[lundah]

Gateway test is good for verifying network connectivity, but if both devices are on the same subnet and regularly pass traffic to each other, they should exist in each other's ARP tables. "arptabShow" is the 3300 shell command, I don't remember what it is in MSL but it should be something similar. If one is missing from the other, maybe get Wireshark running on the subnet and verify you see ARP requests going between the 2 when you attempt to connect? Sounds like one of the devices is sending its traffic somewhere it shouldn't, and it's most likely a simple IP networking config problem, like a bad gateway address or subnet mask.

[ralph]

I know they are both on the same subnet but are they connected?

Can you ping the default gateway on both devices?

Apparently not.  The only thing the TW server can talk to is anything that is on the same VM host.
It can't ping the default GW.
So it would appear that the VM host isn't connected to the vlan.

Ralph

[v2win]

I am assuming its a trunk port so maybe the VLAN isn't allowed on that port

[pmhaynes]

sounds like the vmbg is connected to the wrong network?
Do u have access to the vmware client? can you check what "lan" its programmed too?

[drumster34]

Bridge the virtual NIC so it can get outside of the host.

[v2win]

Did you get this sorted out yet?