[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 659
  • Last Modified:

IP Routing between HP 4208vl to a Stacked HP 2920

I will try my best to explain this.

Main Core Switch: HP 4208vl (11.40 Firmware)
IP Routing: Enabled
IP Default GW: 192.168.8.1
IP: 192.168.8.2 - VLAN8 (Primary Management)
Blade - G1 - X2 10GbE Fiber Module (Untagged on VLAN8)
Blade - H1 - X2 10GbE Fiber Module (Untagged on VLAN8)

New VMware Setup

(2) HP 2920-24 Port with Stacking Enabled  - Ring Configuration (Cabling)
IP Routing: Enabled
IP Default GW: 192.168.80.1
IP: 192.168.80.2 - VLAN1 (Primary Management)
Switch #1: Port A1 - 10GbE Fiber Module SFP+
Switch #2: Port A1 - 10GbE Fiber Module SFP+

When I am on DC (192,168.8.13) connected to the HP 4208VL switch; I try to ping 192.168.80.1 and receive "TTL expired in Transit"

The local router (Cisco 2921 running IOS 15.1) at this building and its IP is 192.168.8.1 and has IP Routing RIP Ver2 enabled  and Network 192.168.80.0 listed.

I believe this is either a routing issue or a stacking config issue. I tried researching about stacking but only found that i just need to type enable stacking on both of the 2920 switches. I know that part is fine because when I connect to the console ports i get the same config. I checked the config and it is turned on.

I just want these stacked switches to talk to the core (4208vl) switch. Any info to get this resolved would be greatly appreciated. I do have support on everything and will see if HP will help tomorrow morning. I just want to get this fixed so I don't waste my consultant's time on this issue.

I will work on a diagram later on tonight and post it because usually that clears up some questions people might have.
0
cslt
Asked:
cslt
  • 3
1 Solution
 
csltAuthor Commented:
Basic Diagram attached
Sample.pdf
0
 
Rick_O_ShayCommented:
It sounds like the path from the HP 4208VL switch might possibly have this getting routed via the default route. Most likely due to no route inside for that network. I can't tell from your diagram where the 80.0 network is.

You should see a route in each switch to all of your networks learned either via RIP, static route or directly connected.
0
 
csltAuthor Commented:
I forgot to mention on the TTL error message that it references 192.168.8.1

"Reply from 192.168.8.1: TTL expired in Transit"

I added 80 network to the router. Once i get to that building i will check to see if the 80 network is listed on the 4208 switch as well.
0
 
csltAuthor Commented:
I knew it was a routing problem to begin with; but you pointed me in the right direction. Thank you.
0

Featured Post

Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now