Submit a ticketCall us

Putting Your Logs Where They Belong with the New SolarWinds Log Manager for Orion

The new SolarWinds® Log Manager for Orion® finally puts your log data right where it belongs, in the heart of your Orion console. Gain insight into the performance of your infrastructure by monitoring your logs in a unified console allowing you to see a wealth of information about the health and performance of your network and servers.

Reserve a Seat for Wednesday May 23rd 11am CDT | Reserve a Seat for Tuesday May 22nd 10:30am GMT | Reserve a Seat for Tuesday May 22nd 1pm SGT / 3pm AEST

Home > Success Center > User Device Tracker (UDT) > Endpoints on ports from non-ethernet based VLANs are missing

Endpoints on ports from non-ethernet based VLANs are missing

Created by Eric Bryant, last modified by Eric Bryant on Jul 06, 2016

Views: 1,063 Votes: 1 Revisions: 8

Overview

This article explains the issue where all MAC endpoints are missing for ports that are associated with non-ethernet based VLANs such as VOIP based VLANs and trunk ports because the VMMembership table is not showing attached ports for these VLANs.

Environment

UDT v2.5 and later

Cause 

When a device is using VOIP VLANs or trunk ports assigned to a VLAN, the vmmembershipsummarytable (1.3.6.1.4.1.9.9.68.1.2.1) table does not show the VLAN to port association information as this table only reports non-trunk and non-VOIP based  VLANs. If the device has either of these VLANs, the results in this table will back as zero. This value means that there are no ports assigned to that VLAN.

When this occurs, none of the endpoints from that VLAN will show up in polling. The reason for this is that UDT does not know that it needs to conduct a VLAN context poll against the device as it believes that there is nothing attached to that VLAN. This results in ports in missing endpoints on a VOIP plan or on a trunk port, while access ports on default or ethernet VLANs show up with no problems.

Resolution

This is a known issue. You will need to upgrade to either upgrade straight to UDT 3.2.4, or if you are unable to upgrade to that version, upgrade to UDT 3.2.3 and apply the UDT 3.2.3 HotFix 1 and this will introduce a new method of gathering vlan information through context polling. You can find the link to the HotFix here. If the event the hotfix is already in place click here.

 

 

Last modified

Tags

Classifications

Public