- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: 2650 VLAN's
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
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
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
тАО03-25-2003 11:05 PM
тАО03-25-2003 11:05 PM
2650 VLAN's
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-25-2003 11:46 PM
тАО03-25-2003 11:46 PM
Re: 2650 VLAN's
Nevertheless you can easily assign different ip addresses for different VLANs, just as you suggest.
You could solve your problem with static routes and then restricting access with ACLs.
I don't think that the 2650 can route VLANs.
Maybe a full featured L3 device such as the 53xx would be more appropriate...
/Marcus
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-26-2003 06:14 AM
тАО03-26-2003 06:14 AM
Re: 2650 VLAN's
Note that you can only have 16 routes though, so this may limit you to 16 VLANs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-26-2003 06:16 AM
тАО03-26-2003 06:16 AM
Re: 2650 VLAN's
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-26-2003 01:47 PM
тАО03-26-2003 01:47 PM
Re: 2650 VLAN's
Just assign each VLAN an IP address in the subnet for that VLAN. All hosts on the same VLAN must now use that VLAN's IP address as their default route.
You need only define one static route on the switch (a default) and that is to your Cisco2621. You will have to tell your Cisco about the new subnets that it can reach via the VLAN1 IP address gateway.
The 2650 will automatically learn of the subnets present on each VLAN and will route between them without any input from you as long as IP routing is enabled and you assign a different IP address and subnet to each VLAN.
Breaking everything up into 32 VLANS will isolate the collision domains and cut down on the amount of traffic so everything will speed up but you will not be able to complete isolate each VLAN from the other. They can still talk if they know each other's IP address or if there is a local DNS that gives out that info. If total isolation is a requirement then the router will have to play too. In that case you would turn off IP routing on the 2650 and set up a trunk to the Cisco with every VLAN present. This requires 32 subinterfaces on the Cisco each with an IP address in the associated VLANs subnet (which would become the default gateway for all hosts in the VLAN). You could then filter via access lists on the Cisco. (I can find no indication in the manuals or the product specification and features that a 2650 has ever heard of access lists or filters (except for multicasting) so I think this would be the only way. ) This would put a lot of extra traffic on the link to the Cisco and would be a lot of work so I wouldn't bother unless you have a bunch of criminal or paranoid users. After all they have been one big happy family up until now.
Ron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2003 08:40 AM
тАО03-27-2003 08:40 AM
Re: 2650 VLAN's
In this example I have the 2650 port1 connected to the Cisco 2621. When I set up the Vlans - should the ports be tagged or untagged? or some tagged and some untagged. ALL Vlans will need to communicate through port1 to the Cisco 2621 for internet access
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2003 04:31 PM
тАО03-27-2003 04:31 PM
Re: 2650 VLAN's
Don't forget to put a default route in the switch pointing to the Cisco and to tell all of your hosts what their new default gateway is.
Ron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-05-2004 05:32 AM
тАО01-05-2004 05:32 AM
Re: 2650 VLAN's
Thanks in Advance
Vincent Bruijnes
http://www.nlisp.nl