Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
yes 112 isnt there in this doc,but here you go,A Document explaining error codes -http://www.cisco.com/en/US/products/sw/cscowork/ps1008/products_user_guide_chapter09186a0080368ff0.html#wp1368730
hi there,I would say the other/unknown ports are not specific to port numbers of tcp ( I have put more explanation below on that.) To address th e new question, NAM does not have an easy way to see the TCP port via the GUIinterface. However, you can ...
Pls check if your device discovery is still up showing all devices correctly with its neighbors. And if you are having devices in more than a site, check the discovery setting is enabled with jump router boundaries option.
The "others" issue is a known issue. We are addressing it in theupcoming 3.5 release. The issue stems fromthe fact that on the NAM GUI we only show protocolDir leaf nodes. In theRMON-II standard packetsare parsed and counted up all the protocol layer...