HPE GreenLake Administration
- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- using snmp to identify uplink port on 5308 and 410...
Switches, Hubs, and Modems
1836452
Members
2874
Online
110101
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
04-27-2005 11:06 AM
04-27-2005 11:06 AM
using snmp to identify uplink port on 5308 and 4108
I have some php scripts that use SNMP to search a group of switches for a particular client's MAC address, with a goal of manipulating some of the interface's characteristics (vlan membership, adminstatus, etc.). The problem: occasionally the MAC will be found on an uplink interface. Typically the uplinks are fiber module interfaces (a1, a2, etc.), but sometimes they are simply one of the ports on a standard 24-port RJ45 module (d24, g10, etc.). Does anyone know of OID(s) that could help me distinguish between uplinks and regular ports?
thanks!
thanks!
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-27-2005 07:30 PM
04-27-2005 07:30 PM
Re: using snmp to identify uplink port on 5308 and 4108
You could try using the dot1dTpFdbPort variable. It is the OID for the MAC-addres forwarding table. If multiple instances exist with the same port, than that port is an uplink (or at least has multiple mac-addresses connected).
Or if you have CDP running on all your network switches and stuff, you could try any of the cdpCache variables like: cdpCacheAddressType
If the port is directly behind it (like cdpCacheAddressType.1.etc (1 is the portnumber here)), it is connected with a cdp enabled device. In most circumstances this would be another switch or router. But if you know your network environment, you should know what devices talk CDP.
A clear OID to query that will return a different value for being an uplink or not does not exist to my knowledge.
Or if you have CDP running on all your network switches and stuff, you could try any of the cdpCache variables like: cdpCacheAddressType
If the port is directly behind it (like cdpCacheAddressType.1.etc (1 is the portnumber here)), it is connected with a cdp enabled device. In most circumstances this would be another switch or router. But if you know your network environment, you should know what devices talk CDP.
A clear OID to query that will return a different value for being an uplink or not does not exist to my knowledge.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP