- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- LAN Routing
- >
- Inter-VLAN Routing
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
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
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-25-2017 01:58 PM
01-25-2017 01:58 PM
Inter-VLAN Routing
I have read through several forum posts, but I have been unable to resolve my issue.
Currently I have a flat network, and everything is running on VLAN 1. My goal is to build a new network (with new servers) and slowly migrate all of my users over to the new infrastructure. This is my first time setting up routes on an HP switch, although I have done this for many years on Cisco gear.
Here is my switch config:
hostname "SVSCSW02" module 1 type j9726a fault-finder broadcast-storm sensitivity high fault-finder bad-driver sensitivity high fault-finder bad-transceiver sensitivity high fault-finder bad-cable sensitivity high fault-finder too-long-cable sensitivity high fault-finder over-bandwidth sensitivity high fault-finder loss-of-link sensitivity high fault-finder duplex-mismatch-hdx sensitivity high fault-finder duplex-mismatch-fdx sensitivity high fault-finder link-flap sensitivity high telnet-server listen data web-management listen data ip ssh listen data ip routing snmp-server community "public" unrestricted snmp-server listen data snmp-server location "Server Room" oobm disable ip address dhcp-bootp exit vlan 1 name "DEFAULT_VLAN" no untagged 13 untagged 1-12,14-24 ip address 10.10.4.221 255.255.252.0 exit vlan 2 name "Server" untagged 13 ip address 10.1.2.253 255.255.0.0 exit no tftp server tftp server listen data no autorun no dhcp config-file-update no dhcp image-file-update no dhcp tr69-acs-url password manager
Laptop Config:
Connected to Port 13 IP Address: 10.1.2.240/16 Default Gateway: 10.1.2.253
Desktop Config:
Connected to Port 15 IP Address: 10.10.5.159/22 Default Gateway: 10.10.4.221
Here are all of my ping results:
From Laptop (10.1.2.240)
- 10.1.2.253 Success
- 10.10.4.221 Success
- 10.10.5.159 Fail
From Desktop (10.10.5.159)
- 10.1.2.253 Fail
- 10.10.4.221 Success
- 10.1.2.240 Fail
From Switch (10.10.4.221)
- 10.1.2.253 Success
- 10.10.5.159 Success
- 10.1.2.240 Success
From Switch (10.1.2.253)
- 10.10.4.221 Success
- 10.10.5.159 Fail
- 10.1.2.240
It appears that routing isn't working properly for VLAN 1 back to VLAN 2. I fired up Wireshark, and I am able to see ICMP packets coming into 10.10.5.159 from 10.1.2.240
And I am ableto see ICMP packets coming into 10.1.2.240 from 10.10.5.159, and I show that 10.1.2.240 is sending responses back. But when I look at Wireshark on 10.10.5.159 I see some ping responses from 10.1.2.240, but I also see some ICMP Destination unreachable (Network unreachable) errors coming from the switch (10.10.4.221)
Here are the traceroutes from 10.10.5.159
[~]$ traceroute -i enp3s0 10.1.2.253
traceroute to 10.1.2.253 (10.1.2.253), 30 hops max, 60 byte packets
1 * * *
2 10.10.4.221 (10.10.4.221) 3.073 ms 3.082 ms 3.080 ms
[~]$ traceroute -i enp3s0 10.1.2.240
traceroute to 10.1.2.240 (10.1.2.240), 30 hops max, 60 byte packets
1 10.10.4.221 (10.10.4.221) 0.672 ms 0.667 ms 0.665 ms
2 * * *
3 * * *
Here is my route table on the switch:
Production1(config)# sh ip route IP Route Entries Destination Gateway VLAN Type Sub-Type Metric Dist. ------------------ --------------- ---- --------- ---------- ---------- ----- 10.1.0.0/16 Server 2 connected 1 0 10.10.4.0/22 DEFAULT_VLAN 1 connected 1 0 127.0.0.0/8 reject static 0 0 127.0.0.1/32 lo0 connected 1 0
Any suggestions or help would be greatly appreaciated.
Yes, I do know that I don't have a default route setup on the switch (ip route 0.0.0.0/0 10.10.4.1) for Internet access. I removed it while I am troubleshooting, just in case it was causing problems.