I have spent hours putting together a "stub network," using SDM, for a single server behind a 2811 router with a HWIC-4ESW switch connected to the server's management port and its public ethernet port.
Each of the server's 2 ports is connected to one of the switch ports Vlan interface (its second ethernet port is not used).
Looking at server's public interface only for this running config detail.
FE0/0 will be connected to the ISP Ethernet cloud, currently setup with a laptop (A.B.78.1):
ip address A.B.78.63 255.255.255.0
ip nat outside
no ip route-cache
no mop enabled
description Public Interface
switchport access vlan 30
description Public Internet
ip address aa.bb.87.49 255.255.255.240
ip route 0.0.0.0 0.0.0.0 A.B.78.1 permanent
ip route aa.bb.87.0 255.255.255.240 aa.bb.87.50 permanent
The server's ethernet connection to vlan30 has an ipconfig: ip: aa.bb.87.50, mask: 255.255.255.240 & default gateway: aa.bb.87.49.
[1.] The router's Tools/Ping form will ping from FE0/0 to the server's ethernet aa.bb.87.50 -- no worries.
[2.] Similarly, the router's Ping Tool will ping from vlan30 to the laptop. (aa.bb.87.49 to A.B.78.1 = 100% 5/5).
[1.] Using the command prompt ping tool from the server:
No ping from server aa.bb.87.50 to A.B.78.1. I can ping to A.B.78.63 (FE0/0).
[2.] Using command prompt ping tool from the laptop:
No ping from laptop A.B.78.1 to aa.bb.87.50. I can ping to aa.bb.87.49 (vlan30).
From looking at this, I think the problem is that the default routing to A.B.78.1 does not work for the vlan30 int traffic and that I need some sort of outbound vlan routing.
How do I do this? encapsulate? helper-address? There is a missing element here, and as frustration has taken over I cannot see it.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...