- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- port 95/96?!?
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
тАО02-14-2011 02:47 AM
тАО02-14-2011 02:47 AM
i'm trying to sort out how HP got port '95' in this log:
I 02/14/11 11:04:34 00828 lldp: PVID mismatch on port 96(VID 0)with peer device
port 0(VID 1)(1050473)
here are the device specs:
Chassis: 5406zl J8697A Serial Number: SG833SU049
Management Module: J8726A Serial Number: ID828AS0SU
Slot Module Description Serial Number
----- ---------------------------------------- --------------
A ProCurve J8707A 4p 10-GbE zl Module SG844AX0FM
B ProCurve J8707A 4p 10-GbE zl Module SG845AX05G
C ProCurve J8706A 24p SFP zl Module SG839BD09X
D ProCurve J8706A 24p SFP zl Module SG839BD027
E ProCurve J8706A 24p SFP zl Module SG833BD082
Software revision : K.14.47
ROM Version : K.12.20
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2011 05:09 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2011 05:13 AM
тАО02-14-2011 05:13 AM
Re: port 95/96?!?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2011 06:09 AM
тАО02-14-2011 06:09 AM
Re: port 95/96?!?
while researching i also found how to check the MIB objects from the device itself "walkMIB"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-22-2011 10:33 AM
тАО02-22-2011 10:33 AM
Re: port 95/96?!?
show lldp info local-device
I have the same issue. I get a lot of these PVID mismatch logs.
All ports that have this mismatch are trunks or trunk/lacp with Cisco blade switches.
On the Cisco side, I allowed only the VLANs that are tagged on the HP on the trunk ports. The VLAN 1 is no untagged on the HP side and not allowed on the Cisco side.
Please let me know if you solved this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-23-2011 02:15 AM
тАО02-23-2011 02:15 AM
Re: port 95/96?!?
btw.. exactly the same problem with the trunk ports..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-12-2011 06:12 AM
тАО05-12-2011 06:12 AM
Re: port 95/96?!?
I have this on a link where the L3 (IP subnet) matches, but the L2 (VLANs) are mismatched
I 05/12/11 23:43:04 00828 lldp: PVID mismatch on port 24(VID 201)with peer device port 23(VID 30)(307)
In this case the local VLAN ID is 201, and the remote VLAN ID is 30.
The following command at each end will stop the messages appearing in the log:
no lldp config
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-12-2011 11:59 PM
тАО05-12-2011 11:59 PM