- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- VLAN not reachable
Switches, Hubs, and Modems
1752806
Members
6850
Online
108789
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-27-2010 06:42 AM
01-27-2010 06:42 AM
VLAN not reachable
Some history, I was troubleshooting a NAT translation issue and discovered that the failure was due to the wrong IP being used for traffic to the GW. My hosts which have 2 NIC cards have one interface assigned to a VLAN that is service specific and one interface assigned to a "central" VLAN which will be used for admin access etc. I realized that the initial configuration on the servers had a GW IP assigned to both interfaces which was causing the NAT policy to fail (I specified one IP but the other IP was seen at the FW). So I removed the GW IP from the interfaces that were part of the central VLAN since a host can't have more then one GW.
Everything seemed ok until I tried to ping the IP addresses assigned to the interfaces that are part of the central VLAN. I can ping some of the addresses but not all of them from my laptop to which I VPN into my data center to gain access to the LAN via a vlan between the FW and my 5406zl switch.
I get the same results when I ping the hosts from the FW itself, however if I log into the 5406 switch (which is assigned an IP from the VLAN that is between the FW and the LAN) I can ping the hosts just fine. I can also ping every one of the IP addresses assigned to this central VLAN from any host that is in a different VLAN from with my LAN.
Does anyone have any idea why this is occurring? Why would some hosts in the VLAN be reachable while others are not from the FW or from a VPN tunnel to the FW. I started thinking it has something to do with MTSP but I am not sure if this is the reason and how I would prove it or rule it out.
Thanks,
David
Everything seemed ok until I tried to ping the IP addresses assigned to the interfaces that are part of the central VLAN. I can ping some of the addresses but not all of them from my laptop to which I VPN into my data center to gain access to the LAN via a vlan between the FW and my 5406zl switch.
I get the same results when I ping the hosts from the FW itself, however if I log into the 5406 switch (which is assigned an IP from the VLAN that is between the FW and the LAN) I can ping the hosts just fine. I can also ping every one of the IP addresses assigned to this central VLAN from any host that is in a different VLAN from with my LAN.
Does anyone have any idea why this is occurring? Why would some hosts in the VLAN be reachable while others are not from the FW or from a VPN tunnel to the FW. I started thinking it has something to do with MTSP but I am not sure if this is the reason and how I would prove it or rule it out.
Thanks,
David
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2010 12:29 AM
01-30-2010 12:29 AM
Re: VLAN not reachable
Going to try to post this a different way with new information I gather during troubleshooting
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