XNET Trunks

[JamesFearn]

Hi all,

Had a strange one today that I could do with some help with. I have a multi site Mitel 3300 network linked via XNET trunks for internal dialling. Today one branch decided to disconnect from the rest of the systems without warning so internal calling has stopped.

The network infrastructure between the sites is working fine (BT MPLS network) and I can see all equipment from the head office end to the faulty branch and vice versa but the IP Trunks will no come up.

I have had a look at the alarm details and have an "ICP Comms Card" error. In the logs I am getting lots of SSL Handshake failures and lots of XNET handle timeouts.

As the network is up and working properly and there has been no configuration changes could there be a fault on the 3300?

Thanks

 

[james1982]

Sounds to me like your getting the icp comms alarm because the xnet link is down.
From maintainence enter "stat xnet all"
This will show all xnet links and whether there established

If one link is not established id busy the link and then return to service

If this fails reboot

 

[JamesFearn]

Thanks for the quick reply James.

Unfortunately I have already busied and returned to service the xnet trunks.

The strange thing is that 3 of the 7 trunks claim to be idle, the other 4 are out of service but the 3 that are idle don't work either!

I have rebooted and still have the same problem!

 

[kwbMitel]

You haven't told us what version the 3300 SW is.

With XNET it is extemely important that all sites are the same.

There were a lot of fixes to Xnet in Rel 7 and 8 that I know about.

Try the Rmess command to test the signalling channel between systems.

From each system to the other:

Rmess verify pbx X ppp (where X = PBX Number for each system)

You should also check the HDLC link status on each NSU by using the State + PLID of the NSU. (first 3 digits of PLID will show both links plus HDLC's)

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[slapin]

Are we talking about IP Trunking (XNET) or XNET over ISDN?

 

[kwbMitel]

Good catch Slapin, I only refer to XNET when PRI trunks are involved as that is what the licensing enables.

IP Networking does not require XNET licensing.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Mitelpassion]

If you are using IP trunking then try and telnet to the ports for IP networking (these are in the engineering guidelines)

example telnet "ip address" "port number"
telnet 192.168.1.2 1607

I don't recall these port numbers but they are in the docs.

Had a similar problem and using this method I understood that eventhough I was able to ping end point to end point, the ports in question was not allowed through.