- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- LAN Routing
- >
- Re: 2920 intervlan routing (another intervlan issu...
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
тАО03-15-2016 03:21 AM
тАО03-15-2016 03:21 AM
Hi Guys,
I know that there are a lot of quesiton about intervlan routing on here (and gernearlly on the internet) and it seems that there is some basic information that is either being missed or passed over by us network admins. With that I have run in to the same problem, I am not getting any traffic between vlans. Can anyone see anything glaring in the below config.
Currently we can ping from the default vlan to its gateway and also the gateway of any vlan that has live connections, but we cant ping any of the machines on the other vlans - yes I have checked the machines gateway and firewall (which is turned off). From the non default vlans we are only able to ping that vlans gateway address.
We can ping the machines from the switch
We have tried updating the firmware to latest version and we have gone back to factory defaults, and setup as basic as possible to make sure it works.
This switch will be handling all the company routing so we dont need any ip default-gateway as we will be using static routing on this switch to route external traffic onwards, but just want to get intervlan routing working first.
Switch info:
Model:2920-48G
version: WB.16.01.0004, ROM WB.15.05
Running configuration:
; J9728A Configuration Editor; Created on release #WB.16.01.0004
; Ver #0b:34.59.14.29.eb.8f.fc.f3.ff.37.2d:d5
hostname "HP-2920-48G"
module 1 type j9728a
ip routing
snmp-server community "public" unrestricted
oobm
ip address dhcp-bootp
exit
vlan 1
name "DEFAULT_VLAN"
no untagged 7
untagged 1-6,8-48,A1-A2
ip address 10.97.1.1 255.255.255.0
exit
vlan 101
name "VLAN101"
untagged 7-8
ip address 10.97.101.1 255.255.255.0
exit
vlan 150
name "VLAN150"
ip address 10.97.150.1 255.255.255.0
ip helper-address 10.97.101.10
exit
vlan 180
name "VLAN180"
ip address 10.97.180.1 255.255.255.0
ip helper-address 10.97.101.10
exit
password manager
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-15-2016 03:25 AM
тАО03-15-2016 03:25 AM
Re: 2920 intervlan routing (another intervlan issue)
more info:
show ip route
IP Route Entries
Destination Gateway VLAN Type Sub-Type Metric Dist.
------------------ --------------- ---- --------- ---------- ---------- -----
10.97.1.0/24 DEFAULT_VLAN 1 connected 1 0
10.97.101.0/24 VLAN101 101 connected 1 0
127.0.0.0/8 reject static 0 0
127.0.0.1/32 lo0 connected 1 0
show arp
IP ARP table
IP Address MAC Address Type Port
--------------- ----------------- ------- ----
10.97.1.61 0050b6-0fd398 dynamic 1
10.97.101.5 68b599-fc76a1 dynamic 7
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-15-2016 04:54 AM
тАО03-15-2016 04:54 AM
SolutionAll I am going to say at this point is "I am a Muppet!"
On of the test clients had a ghost secondary gateway, which was not showing in the tcp/ip settings.
Flushed the gateways and readded the correct one and everything starts working.
Note to future self: Always check the clients!