- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2013 11:31 AM - edited 03-07-2019 04:29 PM
OK, is it just me, or can you not ping a 192.168 address when creating vlans for it?
For example I created 3 vlans with the config below and can ping each one from my data network 10.20.60.0
int gig0/1.10
encapsulation dot1q 10
ip address 10.20.60.1/23
int gig0/1.20
encapsulation dot1q 20
ip address 10.20.20.1/23
int gig0/130
encapsulation dot1q 30
ip address 172.20.30.1/23
CANNOT PING
int gig0/1.40
encapsulation dot1q 40
ip address 192.168.40.1/24
Is there something wrong that I am not seeing.. Also the 192.168.40.0 is my voice net
Solved! Go to Solution.
- Labels:
-
Other Switching
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2013 08:34 AM
Are you able to ping the vlan from switch
Check with your gateway address in data vlan.
Usally data vlan gateway will be firewall, so you are packet getting dropped.
try to put the Core Switch ip in the gateway address,you will be able to ping.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2013 11:51 AM
I ok I think I know whats gonig on.. Working it out.... There is more to my configs than what you see here.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2013 08:34 AM
Are you able to ping the vlan from switch
Check with your gateway address in data vlan.
Usally data vlan gateway will be firewall, so you are packet getting dropped.
try to put the Core Switch ip in the gateway address,you will be able to ping.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2013 08:32 AM
Please post yout topology and all running-configs.
You might blocking vlan40 in trunk, you might not have vlan40 created on all devices.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2019 09:17 PM
Now Really there is Nothing to Worry About. it Just Might Be Some Technical Glitch. You Did Not Explain About Series & Model Number of Your Router. Whether 192.168.2.1 is the default Gateway Or Some Other Lost Host According to Your Router. Please Explain it Further Where all I can recommend Right Now is to Login & Update the Firmware of your Router. to Know More About 192.168.1.1 Which is Default Ip for Cisco Router Read on Official Cisco Website.
thanks
