- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: BL C-GBE2 Issues
ProLiant Servers (ML,DL,SL)
1752647
Members
5750
Online
108788
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
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
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
01-28-2005 11:33 PM
01-28-2005 11:33 PM
BL C-GBE2 Issues
I have a mixed netowrk which uses Cisco3750T's which are connected to CGBE2's on ports 21 n 22.. I see a lot of discards on those interfaces on all the swithces of HP.
I am quite foxed as I have checked everything.. I am attaching a TSDUMP of one of the switches.. anyone who helps will be highly appreciated as HP themselves are not helping us..
I am quite foxed as I have checked everything.. I am attaching a TSDUMP of one of the switches.. anyone who helps will be highly appreciated as HP themselves are not helping us..
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2005 01:58 AM
01-30-2005 01:58 AM
Re: BL C-GBE2 Issues
From the TSDUMP it looks like the discards on ports 21 n 22 are solely attributed to "dot1PortInDiscards".
From GbE2 Command Reference Guide.
"dot1PortInDiscards = Count of valid frames received which were discarded (that is, filtered) by the forwarding process"
As these ports are tag enabled dot1Q tagged packets will be processed. Non tagged packets will be associated to each ports PVID (VLAN 1 as per the TSDUMP)
Assuming that you have configured VTP Transparent mode on the Cisco Switches, then you cannot enable VTP pruning.
From Cisco UniverCD
"VTP Pruning
VTP pruning increases network available bandwidth by restricting flooded traffic to those trunk links that the traffic must use to reach the destination devices. Without VTP pruning, a switch floods broadcast, multicast, and unknown unicast traffic across all trunk links within a VTP domain even though receiving switches might discard them. VTP pruning is disabled by default."
"....VTP pruning is not designed to function in VTP transparent mode......"
Assuming there are additional VLANs defined within the Cisco switches that are not defined within the GbE2 switches. The Cisco switches may be presenting valid frames to the GbE2 switches with an unknown VLANID, the GbE2 switch should filter out (discard) those packets.
This leaves the "dot1PortInDiscards" port counters reporting all dot1Q frames received by those ports that cannot be matched to a VLAN defined within the GbE2 switch.
Possible Solution : Try defining the missing VLANs without associating any ports.
Otherwise accept this as normal reporting behaviour.
From GbE2 Command Reference Guide.
"dot1PortInDiscards = Count of valid frames received which were discarded (that is, filtered) by the forwarding process"
As these ports are tag enabled dot1Q tagged packets will be processed. Non tagged packets will be associated to each ports PVID (VLAN 1 as per the TSDUMP)
Assuming that you have configured VTP Transparent mode on the Cisco Switches, then you cannot enable VTP pruning.
From Cisco UniverCD
"VTP Pruning
VTP pruning increases network available bandwidth by restricting flooded traffic to those trunk links that the traffic must use to reach the destination devices. Without VTP pruning, a switch floods broadcast, multicast, and unknown unicast traffic across all trunk links within a VTP domain even though receiving switches might discard them. VTP pruning is disabled by default."
"....VTP pruning is not designed to function in VTP transparent mode......"
Assuming there are additional VLANs defined within the Cisco switches that are not defined within the GbE2 switches. The Cisco switches may be presenting valid frames to the GbE2 switches with an unknown VLANID, the GbE2 switch should filter out (discard) those packets.
This leaves the "dot1PortInDiscards" port counters reporting all dot1Q frames received by those ports that cannot be matched to a VLAN defined within the GbE2 switch.
Possible Solution : Try defining the missing VLANs without associating any ports.
Otherwise accept this as normal reporting behaviour.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP