- Community Home
- >
- Networking
- >
- Legacy
- >
- IP Telephony - NBX
- >
- Re: Pkto TimeOut - to the NBX MAC address
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2010 06:21 PM
тАО01-31-2010 06:21 PM
Pkto TimeOut - to the NBX MAC address
I understand that this message in the NBOSS log, means the NBX did not recieve status packets from a device but what if the MAC is the NCP's address!! Does that mean the chasis needs to be replaced? Could it be a connectivity problem with the switch?
This is the message:
E Got a Pkto TimeOut - Application Should Mark Device DOWN
any suggestions?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2010 08:04 PM
тАО01-31-2010 08:04 PM
Re: Pkto TimeOut - to the NBX MAC address
I had joined the forum just to ask the same question!!
What I'm wondering is, if it's not the NCP trying to so much communicate with itself, but could it be that as a call extends to a phone, then is unanswered, has to return to the NCP <MAC address> to connect to one of the voicemail ports, and gets a PKTO trying to do so-- because of what?? network congestion, etc??
My customer doesn't complain of any issues with this; it just shows up in the NBoss Log. So I don't know what severity this carries.?.
-Jim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2010 07:43 AM
тАО02-01-2010 07:43 AM
Re: Pkto TimeOut - to the NBX MAC address
NoThink of it as an ack / nack .
The tel sends a packet saying I am here and the NCP answers back with an ok . A little more involved for the status updates etc . But when the NBX and the tel can see each other then these messages will not show up . Its only when the 2 devices do not talk . Usually a network issue blocking the packets . Could be a bad device as well but very rare . If you trac eout your network and see the packets coming from the tel , then you know the NBX is not seeing it , hence the network .
Try a hub for testing .....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2010 08:31 AM
тАО02-01-2010 08:31 AM
Re: Pkto TimeOut - to the NBX MAC address
But what does it mean when the NBX's own Mac address is reported as the device not connecting?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2010 06:58 AM
тАО02-08-2010 06:58 AM
Re: Pkto TimeOut - to the NBX MAC address
It means that for some reason that Mac is not responding within the time allowed ( Milliseconds response time ) . Happens once in a while . If the issue occurs all of the time , trace out the network and find out the timing between the send and the recieve . Thats the only real true way to see .