- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Adding a Subnet - Part II
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2012 05:40 PM - edited 04-29-2012 05:47 PM
04-29-2012 05:40 PM - edited 04-29-2012 05:47 PM
Adding a Subnet - Part II
I thought it would be best to post this in a separate thread. I have added a second subnet to a 3500, and can ping DEFAULT VLAN from the Barracuda VLAN and can ping the router from both VLANs. I can also ping all clients on DEFAULT VLAN from the Barrracuda VLAN and can ping the Barracuda VLAN client from the clients on DEFAULT VLAN. In addition, the router will ping both VLANs and their clients.
Problem is I cannot ping the internet from the Barracuda VLAN. I thought this might be due to NAT on the router, and changed the ACL to allow all traffic, but this did not solve the problem Next, to rule out a problem with the barracuda appliance, I added a second port to the Barrracuda VLAN, and conected a laptop. Destination is unreachable when the internet is pingedfrom the laptop.
Another interesting observation, when using a network scanner, the Ip for the Barracuda VLAN 192.168.0.1 and the ip for the barracuda appliance 192.168.0.4 are discovered, but no MAC address shows up- which seems unusual. Also when show arp is done on the router, no entries for the 192.168.0.0 subnet are present.
Not sure if the router is missing something, or something needs to be done with the switch, the router config is below, thanks for any guidance!!
Building configuration...
Current configuration : 5557 bytes
!
! Last configuration change at 18:44:53 Chicago Sun Apr 29 2012
!
version 15.0
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname cisco1941
!
boot-start-marker
boot-end-marker
!
no aaa new-model
clock timezone Chicago -6
clock summer-time Chicago date Apr 6 2003 2:00 Oct 26 2003 2:00
!
no ipv6 cef
no ip source-route
ip cef
!
ip dhcp excluded-address 192.168.1.1
!
ip dhcp pool Home
import all
network 192.168.1.0 255.255.255.0
dns-server 68.113.206.10 24.217.0.5
default-router 192.168.1.1
lease infinite
!
ip name-server 68.113.206.10
ip name-server 24.217.0.5
ip name-server 8.8.8.8
multilink bundle-name authenticated
!
no ip ftp passive
!
interface GigabitEthernet0/0
description $ETH-WAN$
ip address dhcp client-id GigabitEthernet0/0
ip nat outside
ip virtual-reassembly
duplex auto
speed auto
no cdp enable
no mop enabled
!
interface GigabitEthernet0/1
ip address 192.168.1.1 255.255.255.0
ip nat inside
ip virtual-reassembly
duplex auto
speed auto
no cdp enable
!
ip forward-protocol nd
!
ip http server
ip http secure-server
!
ip nat inside source list 1 interface GigabitEthernet0/0 overload
ip nat inside source static tcp 192.168.1.111 80 interface GigabitEthernet0/0 80
ip nat inside source static tcp 192.168.1.111 4125 interface GigabitEthernet0/0 4125
ip nat inside source static tcp 192.168.1.111 3389 interface GigabitEthernet0/0 3389
ip nat inside source static tcp 192.168.1.111 443 interface GigabitEthernet0/0 443
ip nat inside source static tcp 192.168.1.106 90 interface GigabitEthernet0/0 90
ip nat inside source static tcp 192.168.1.106 3660 interface GigabitEthernet0/0 3660
ip nat inside source static tcp 192.168.1.106 3663 interface GigabitEthernet0/0 3663
ip nat inside source static tcp 192.168.1.106 4665 interface GigabitEthernet0/0 4665
ip nat inside source static tcp 192.168.0.4 81 interface GigabitEthernet0/0 81
ip nat inside source static tcp 192.168.0.4 444 interface GigabitEthernet0/0 444
ip nat inside source static tcp 192.168.0.4 22 interface GigabitEthernet0/0 22
ip nat inside source static udp 192.168.0.4 4500 interface GigabitEthernet0/0 4500
ip nat inside source static tcp 192.168.0.4 1723 interface GigabitEthernet0/0 1723
ip nat inside source static tcp 192.168.0.4 636 interface GigabitEthernet0/0 636
ip nat inside source static tcp 192.168.0.4 25 interface GigabitEthernet0/0 25
ip nat inside source static tcp 192.168.0.4 53 interface GigabitEthernet0/0 53
ip nat inside source static udp 192.168.0.4 53 interface GigabitEthernet0/0 53
ip nat inside source static udp 192.168.0.4 123 interface GigabitEthernet0/0 123
ip nat inside source static tcp 192.168.0.4 389 interface GigabitEthernet0/0 389
ip nat inside source static udp 192.168.0.4 500 interface GigabitEthernet0/0 500
ip route 192.168.0.0 255.255.255.0 192.168.1.37
!
logging trap debugging
logging 192.168.1.113
access-list 1 remark CCP_ACL Category=18
access-list 1 permit any
!
control-plane
!
scheduler allocate 20000 1000
no process cpu extended
no process cpu autoprofile hog
end
- Tags:
- VLAN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2012 12:28 PM - edited 04-30-2012 12:29 PM
04-30-2012 12:28 PM - edited 04-30-2012 12:29 PM
Re: Adding a Subnet - Part II
Ok, I solved this by adding a static route to the switch
ip route 0.0.0.0 0.0.0.0 192.168.1.1
but why was this necessary? shoudn't traffic out ot the secondary VLANs be routed out of DEFAULT VLAN gateway? Is there something about my switch configuration that is wrong?