- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Comware Based
- >
- Re: Layer 3 - link-mode route
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
тАО01-13-2020 08:48 AM - edited тАО01-13-2020 05:11 PM
тАО01-13-2020 08:48 AM - edited тАО01-13-2020 05:11 PM
Layer 3 - link-mode route
Hello Everyone,
I have been having difficulties correctly configuring my network. Currently my ports are configured as follows..
port link-mode bridge
port link-type trunk
port trunk permit 1-20, 255
port trunk pvid vlan 255
I have two ESXi hosts 10.1.255.2/24 and 10.1.255.3
On the first host I have a Repo server configured 10.1.255.14/24
On the second I have a host in a port group for vlan 1 10.1.1.2/24
With routes put in on the vms themselves I can ping around without issues, ssh between servers, but am unable to pull down yum updates traffic on essensially any port doesn't appear to be getting through. Do I need to have it configured with link-mode route instead? I have a basic understanding of vlan tagging, but not sure if maybe packets are being being dropped or what the issue is. Any help and recommendations are greatly appreciated, as I am new to this and have never built a setup from the ground up. Thank you so much!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2020 03:11 AM
тАО01-20-2020 03:11 AM
Re: Layer 3 - link-mode route
Hello,
As you are saying you are able to ping and do ssh beetween severs then I am very much sure there is no issue in the network. If there is any routing or other network issue then you wont able to ping or ssh beetween servers.
You may need to check application for yum updates issue.
I am an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-24-2020 04:44 PM
тАО01-24-2020 04:44 PM
Re: Layer 3 - link-mode route
How did you set the vSwitch Standard (VSS) which is using that uplink interface (PVID = 255 means untagged ingress traffic - incoming into that switch's port - will be internally tagged with VLAN id 255 but egressing that tag will be removed and so outgoing packets are without tag, untagged).
The permit 1-20, 255 means you're passing (and permitting in both directions) tagged traffic with VLAN id 1 - VLAN id 20 (range 1-20) to VMware's VSS.
At this point one expects that your VSS has twenty ones Port Groups (one with each one VLAN Tag: a Port Group with VLAN id 1, a Port Group with VLAN id 2 and so on up to VLAN id 20 and also VLAN id 255). VMs should then be set to use one of those Port Groups for each vNIC you set on them (but here YMMV because each VM could have a very particular configuration that, here, is not so relevant).
I'm not an HPE Employee