I have purchased 6 new switches, 1 3560, 2 2960-48, and 3 2960-24. My current network only has one subnet, 192.168.36.0/23 and I'm wanting to implement VLANs to help break up the network. I have created 5 VLANs 36,38,39,40,41 plus VLANs 1 and I have setup the 3560 as the VTP Server. The VLANs have prorogated to the 2960 switches fine. One of my goals is to replace our "Router on a Stick" router which is just using static routes. I've already added those routes to the 3560 as well as an IP helper address for the 36.0 subnet. I've plugged in a PC that use DHCP, and plugged it into a port assigned to VLAN 36. The PC receives the IP address fine and does not receive anything when it's plugged into a different port in a different VLAN, which is suppose to happen. It will also ping router that is located at a remote locations so I know it is working. As I mentioned my current network is using 192.168.0.36.0/23 so I'd wanting to leave my servers and network devices (switches, routers, etc), in the same subnet for an easier migration, but move the users, printers, and wireless devices to other VLANs. I'm currently testing VLAN 38 which is where I'm putting my printers. I have assigned a port in my 2960-24 switch to VLAN 38, I've given the printer an ip address of 192.168.38.2.
From the 3560 switch I can ping the 38.2 address and after modify my Windows XP route table, added the route to 192.168.38.0 I can also ping 10.0.38.2 from my PC which isn't plugged into any of these switches, just my normal network. The issues I'm having is that I can't print to the printer on 192.168.38.2 from my PC. To make sure it wasn't some kind of ACL issue, which I have none configured on the 3560, I assigned a port from the 3560 to VLAN 38 and plugged in the printer there. Now when I do that I can't even ping the printer, but when I move it back to the 2960 I can ping, but again still can't print. I'm sure it's a configuration oversight, can you assist me in finding this. I'm wondering if the problem could be related to the fact that my network is truly only aware of the 192.168.36.0/23 subnet, if so what is the best method of introducing the other subnets I plan on implementing.
Actually my worstataion gateway is set to 36.1, but I had already did a "route add 192.168.38.0 mask 255.255.255.0 192.168.36.5" which allowed me to ping the IP before. I did find my issue was a combintation of things:
1. Trunk port connecting the 3560 and 2960 is bad.
2. Printer wasn't working properly
3. No default gateway in 3560.
Once I changed the trunk port, changed the printer and added the gateway I was able to print to the printer from my 36 subnet when it was plugged into any of the switches.
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 customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...