I have an HP ProCurve 8212zl Switch which I am currently configuring from scratch. This switch is a Layer 3 switch, meaning it also supports routing.
I also have an ISP that provides me with access to the Internet via a 1000SX gigabit SFP fibre channel, and has assigned me a range of static IP addresses, and also given me the IP address of their Gateway.
My goal right now is to setup a minimal configuration that supports both LAN and WAN access (i.e. access to my local network devices and also access to the Internet via the ISP's gateway.)
Setting up the LAN was very simple. I used the switch's CLI to assign an IP address to the switch. Then I manually assigned static IP addresses to all devices connected to the switch. (I realize I should be using DHCP, but again, at the moment I am only interested in the simplest possible configuration that supports LAN and WAN.) So now I have the LAN working: all devices connected to the switch can ping the switch, and all devices connected to the switch can ping each other. The LAN consists of a single default VLAN.
However, I am unable to figure out how to get access to the Internet working.
I have a fibre channel that connects directly to a switch module via an SFP (1000SX Mini-GBIC). The SFP is connected to port
B21 in the switch. Using the switch CLI, I can check the status of the fibre channel port by typing
show interfaces B21. This shows me that port B21 is indeed enabled, and its status is up, and it is receiving bytes. So the SFP and port seems to be working fine.
Conceptually, my understanding is that in order to access the Internet, the switch would need to:
- Check if a packet has a destination IP that is not part of the local LAN
- If so, forward it to my ISP's Gateway via Port B21 (the fibre channel port)
I've read through many of the HP ProCurve manuals, but I don't understand how this is accomplished. The closest I can understand is that you need to enable routing on the switch (which I've done), and then specify a "default route". A default route basically tells the switch "if you see a packet that's destined for some address that is not part of the local LAN, then forward it to
<SOME IP ADDRESS>"
So, on the CLI I can do:
# ip route 0.0.0.0/0 <MY ISP'S GATEWAY IP ADDRESS>
This tells the switch that if a packet is destined for some address that is not part of the LAN, forward it to
<ISP GATEWAY ADDRESS>.
I tried this, and it doesn't work - meaning, even with the default route set, I still can't ping my ISP's Gateway, and I can't ping any external Internet address (like the IP address of google.com, for example).
But even worse, I don't even understand why this should work. How can the switch possibly know that it must go through the fibre channel port (port
B23) to even access the external world in order to even find
<ISP GATEWAY ADDRESS>? I don't see how the
ip route command gives the switch enough information about where to find
<ISP GATEWAY ADDRESS>.
I suspect I must be missing some key concept here. In general, I want to tell the switch: "if you see a packet destined for a non-LAN address, forward it to port B23, where you will find a connection to the outside world and the next hop (my ISP's Gateway)".
So what am I missing here?