As you said, there is no "ip routing". All new 3Com switches start routing between vlans when you create the vlan interfaces.
Int Vlan 1
ip address 192.168.1.1 255.255.255.0
Int Vlan 2
ip address 192.168.2.1 255.255.255.0
This would create bosth vlans and vlan interfaces with those addresses. If you add a port to any of those vlans, set the gateway for your PCs to be the .1 address and it will be able to route to the other vlan.
At the end of the setup I would also add a stati route to your real default gateway for internet conectivity and such.
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
IP Lite introduced enterprise access Layer 3 features to the Cisco WS-C2960XR-24TS-I. IP Lite is subset of IP Base features. Some of the IP Lite features are: Routing Information Protocol (RIP) v1 Routing Information Protocol (RIP) v2 Open Shortest Path First (OSPF) v2 Routed Access Open Shortest Path First (OSPF) v3 Routed Access Enhanced Interior Gateway Routing Protocol (EIGRP) stub Equal-cost routing Hot Standby Router Protocol (HSRP) Protocol Independent Multicast PIM (Sparse Mode, Dense Mode, Sparse Dense Mode, Source Specific Multicast) stub Virtual Router Redundancy Protocol (VRRP) for IPv4 Private VLAN IPv6 First Hop Security source guard Per-VLAN and per-port policers
i don't see it i looked at the owners manual and see the basics as well as the VLANconfigs but that's it.
why do u want static routing? pass through? trunking? I don't see an option for the routing.
I will dig through my ios stuff and post if I find anything.
Hi, If you are creating only Layer 2 VLANs on the switch , you wont be able to ping the servers and Routers as they are in default VLAN1. you can do the below steps 1. Create sub interfaces on the router LAN interface 2. Provide a new ip range to the new sub interface 3. Make the switch port connecting router as trunk, so that it will carry both the VLAN info 4. on your Labtop/PC give the IP address in the newly defined range 5. Make your switch port to be in the new VLAN
This will work , if you wont be able to configure the above settings, let me know i will give you the detailed config
Make sure that the frame encapsulation is set on the router to 802.1q on each of the sub-interfaces. You could also try fixing the speed and duplex on both the router and the switch in case there is a problem negotiating the speed and duplex.
First, be sure to assign an ip address(in the proper subnet) to each VLAN.
Second, use the ip helper-address command in the context of each VLAN, the address used should be the address of the DHCP server
Third, Add a scope for each additional VLAN on the DHCP server.
The switch will route the DHCP request to the proper server based on the ip helper-address command parameter and based on the ip address of the VLAN that is passed tot he server, a DHCP address in the proper subnet is automatically configured.
Hmm... on your DHCP server, try setting the "default router" IP for each pool to be the VLAN ID on the switch.
scope 172.16.0.0 /24
scope 10.20.8.0 /22
I think the DHCP replies aren't going back where they should. I've never done this without a router doing all the DHCP, but it does work and i've done it many times. Your config looks spot on for the switch.