HP ProCurve - Routing and Internet access woes

[CHiLL]

Hello,

We have a a large problem which is becoming out of hand. On Tuesday, we started our Internet switch from one provider to another. We have a new router from the new provider, which has been configured.

 

Juniper Router

Interface 0 - Connects to the Virgin Media media converter box for Internet in/out

Interface 1 - Has an IP address of 10.22.2.1 and connects into our HP ProCurve core switch on interface F2.

 

HP ProCurve Core Switch

Interface F2 - Has an IP address of 10.22.2.254.

 

However, it appears I am having routing issues. I have been provided commands to run on the core switch by our supplier who implemented the HP ProCurve solution last year, but still having issues.

 

First, he told me to run the following commands:

Conf t
vlan 2
no ip address
ip address 10.22.2.254 255.255.255.0
exit
no ip route 0.0.0.0 0.0.0.0 10.22.2.254
ip route 0.0.0.0 0.0.0.0 10.22.2.1
wr mem

However, I received the following message when running them:

10.22.2.254/24 can not be switch IP address and route gateway at the same time.

 

He then sent me the following commands to run:

conf t
no ip route 0.0.0.0 0.0.0.0 10.22.2.254
vlan 2
no ip address
ip address 10.22.2.254 255.255.255.0
exit
ip route 0.0.0.0 0.0.0.0 10.22.2.1
wr mem

Yesterday, it accepted those commands but there was still no Internet access.

 

I have attempted to run the second set of commands again and receive the following message when running the command 'no ip route 0.0.0.0 0.0.0.0 10.22.2.254':

10.22.2.254 can not be switch IP address and route gateway at the same time

 

At this moment:

Our client machines can ping the core switch interface F2 on 10.22.2.254.

The core switch itself can ping the Juniper on 10.22.2.1

The Juniper itself can ping the core switch on 10.22.2.254.

 

Can anybody help, as I'm tearing my hair out at the moment!

Edited April 1, 2016 by CHiLL

[CHiLL]

Update:

Our core switch can ping Google's DNS servers at 8.8.8.8. However our clients cannot. This means the problem is with the core switch.

 

Can anybody advise?

[themightymrp]

What default gateway are your clients set to use? They should be set to use the IP address which has been assigned to the relevant VLAN (i.e. the same VLAN the client sits on) on your core switch.

[IrritableTech]

Have you got 'ip routing' enabled for a start - that's not in your supplied instructions?

Have you got any VLANs set up already? If so what?

You can't give an IP to a port, you've given it to the switch to use in VLAN 2 - is Port F2 configured for VLAN2?

[IrritableTech]

What default gateway are your clients set to use? They should be set to use the IP address which has been assigned to the relevant VLAN (i.e. the same VLAN the client sits on) on your core switch.

 

Another good point.

@CHiLL - log onto the CLI and run 'show run' There isn't usually anything you shouldn't be showing us in there, but if there is something you're uncomfortable about showing blank it out. If we can see the config someone will be able to determine if it's that at fault.

[ellsandell]

As above - if you could provide the full configs that would be helpful.

[ricki]

Have you got the correct subnet configured on all devices

[DMcCoy]

If your switch has internet access, and the clients are using it as their gateway, then it is likely that the router does not have any return routes set up.

 

As the router has a default gateway as the internet, then it will need a route back to the switch for your internal IP ranges.

[Wave9_Tim]

Quite possibly this is one of the problems (lack of the appropriate return routes on the SRX), in addition it could be that the Juniper device also requires the access rules/NAT statements to support the downstream IP subnets.

[CHiLL]

Thanks for the replies.

 

Thought I'd update this thread as I've been away on annual leave. The issue was indeed with the Juniper router, where the supplier did not configure the router with our VLAN information. The router has now been configured and the internet is working.