- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2016 10:55 AM - edited 03-08-2019 05:53 AM
Dear Cisco Experts,
Need your valuable inputs in setting up my test lab; i have bought a Cisco 1812-J/K9 ISR a month ago and still struggling make it work the way i want. I am very new to Cisco devices and basically to advance networking concepts as well. I did go through loads of videos and steps from cisco documents and our good old friend google too, finally posting it here.
Ok heres the hardware i have:
HP DL 380 G7 server with 4 Nics
Cisco 1812-J/K9 ISR which has 2 WAN Ports[Fe0 & Fe9] & 8 LAN Ports[F2 to Fe9]
Dlink DIR-816L home router provided by my ISP - Capabilities DHCP, Wireless & LAN ports 4
Software & Connectivity Information:
HP Server is loaded with Windows 2012 R2; configured Hyper V with 3 Hyper-V virtual Switches with VLAN IDs as 3, 5 & 9, each Hyper-V virtual Switch is configured to use 1 physical nic, so i have the following setup:
Hyper-V vSwitch 1 - VLAN ID 3 --> Connected Physical Nic1 --> Connected to Fe3 on Cisco 1812
Cisco Configuration:
Fe0 port on Cisco is connected to Dlink Home Router on Port 2 and i have assigned the ip to Fe0 which 192.168.0.10
Enabled IP Routing
Created VLAN 3
Assigned IP to VLAN 3 as 192.168.3.2 255.255.255.0
trunking enabled on VLAN 3 and native vlan enabled & configured to use VLAN 8[Fe8 Int added and no physical connection on Fe 8]
Fe0 interface on Cisco is connected to Dlink Home Router on Interface 2 and i have assigned an ip to Fe0 as 192.168.0.10
Configured Static Route 192.168.3.0 255.255.255.0 192.168.0.1 <-- This is my dlink router ip
Configured Last Resort Gateway as 0.0.0.0 0.0.0.0 192.168.0.1 <-- This is my dlink router ip
Enabled IP ROUTING
I can ping from cisco to devices 192.168.3.0 network [example: i can ping 192.168.3.2[VLAN 3 IP] & 192.168.3.3[Physical Nic 1 on my Hyper-V host] & 192.168.3.5[Static IP assigned to a centos VM which is connected to Hyper-V vSwitch1 which is connected to Physical Nic1]
I can ping from the CentOS VM mentioned above to all the devices on 192.168.3.0 and can ping 192.168.8.2[IP of VLAN 8 on Cisco] & also ping 192.168.0.10[ip of Fe0 on Cisco]
but unable to ping dlink router on 192.168.0.1 & any other devices 192.168.0.0 network other than cisco Fe0 which is 192.168.0.10.
My aim is to reach internet on CentOS vm, IPTABLES & Firewall disabled on CentOS & Hyper-V host.
Please let me know what i am missing, and now i have big doubt if i can achieve my requirement with Cisco 1812-J/K9 device.
Thanks and Regards
Tammali
Solved! Go to Solution.
- Labels:
-
Other Switching
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2016 01:25 AM
Hello
Can you post the running config of the cisco router please.
in the interim you can try the following:
On the cisco:
ip route 0.0.0.0 0.0.0.0 192.168.0.1 < this is correct as it will the be pointing to the Dlink rtrs Lan facing interface
ip route 192.168.3.0 255.255.255.0 192.168.0.1 <------ Not required, remove it
Now for reachability between your vlan 3 to the dlink rtr you can do a couple of thngs:
1) apply 192.168.3.0 255.255.255.0 192.168.0.10 < on the dlink rtr for return traffic toward your LAN
or
2) Enable Network Translation on the cisco rtr. even though I can see with the addressing at present that the dlink is providing would be already doing NAT
access-list 10 permit 192.168.3.0 0.0.0.255
ip nat source list 10 interface fe0 overload
interface fe0 and fe3
ip nat enable
For the Hyper v - the Default-gateway would be 192.168.3.2 <----- this is pointing the L3 svi for vlan 3 on the cisco rtr
res
Paul
Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.
Kind Regards
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2016 01:25 AM
Hello
Can you post the running config of the cisco router please.
in the interim you can try the following:
On the cisco:
ip route 0.0.0.0 0.0.0.0 192.168.0.1 < this is correct as it will the be pointing to the Dlink rtrs Lan facing interface
ip route 192.168.3.0 255.255.255.0 192.168.0.1 <------ Not required, remove it
Now for reachability between your vlan 3 to the dlink rtr you can do a couple of thngs:
1) apply 192.168.3.0 255.255.255.0 192.168.0.10 < on the dlink rtr for return traffic toward your LAN
or
2) Enable Network Translation on the cisco rtr. even though I can see with the addressing at present that the dlink is providing would be already doing NAT
access-list 10 permit 192.168.3.0 0.0.0.255
ip nat source list 10 interface fe0 overload
interface fe0 and fe3
ip nat enable
For the Hyper v - the Default-gateway would be 192.168.3.2 <----- this is pointing the L3 svi for vlan 3 on the cisco rtr
res
Paul
Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.
Kind Regards
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2016 02:37 AM
Hi Paul,
Thanks for the quick response, will try your suggestions, right now i wiped of the config and starting fresh. Will follow your instructions and let you know the results.
Just a quick query; i am unable to enable NAT or assign an ip on Fe3 interface and the cli response is that ip cannot be assigned on L2 Links and for IP NAT ENABLE while i am in Fe3 interface the command doesn't exist.
I can do both the things for Fe0 and Fe1 and just a reminder, Fe0 and Fe1 are called WAN ports in CISCO 1812-J and Fe2 to Fe9 are called Ethernet or LAN ports. I am confused with these WAN and LAN ports.
I can configure Sub Interfaces on Fe0 and Fe1 and i cannot do the same on LAN ports.
Also Dlink router doesn't have option to configure NAT.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2016 09:05 AM
Hi Paul,
Thanks a ton for your help, its resolved and working as expected. I got one VM on 1 VLan communicating with external world....
instead of Fe3 i enabled nat for vlan 3 to which fe3 has been configured as switch port.
Can you explain how you derived 10 for Access-list ; or if you can point me to a documents that would also help me.
I am planning to create 4 Vlans out 4 Physical NICs, lets how that goes.
Thanks & Regards
Tammali
