- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- 5400yl restricting iSCSI network on its own VLAN
Switches, Hubs, and Modems
1748216
Members
3528
Online
108759
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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-23-2010 07:44 AM
тАО03-23-2010 07:44 AM
5400yl restricting iSCSI network on its own VLAN
Hi all,
I am planning to segment 24 ports on my 5400yl core switch for my iSCSI network.
I am going to be placing those 24 ports on VLAN 97 (iSCSI).
I am using RIPv2 internally. What would be the best way to deny users from accessing the iSCSI VLAN?
I am planning to put an ACL on VLAN 97 that deny's all and also excluding VLAN 97 in RIPv2 advertisements would that work or is there anything else I should do to make this happen? Since turning on IP routing allows all VLAN(s) to communicate with each other.
Thanks for you responses
I am planning to segment 24 ports on my 5400yl core switch for my iSCSI network.
I am going to be placing those 24 ports on VLAN 97 (iSCSI).
I am using RIPv2 internally. What would be the best way to deny users from accessing the iSCSI VLAN?
I am planning to put an ACL on VLAN 97 that deny's all and also excluding VLAN 97 in RIPv2 advertisements would that work or is there anything else I should do to make this happen? Since turning on IP routing allows all VLAN(s) to communicate with each other.
Thanks for you responses
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-23-2010 11:46 AM
тАО03-23-2010 11:46 AM
Re: 5400yl restricting iSCSI network on its own VLAN
ACL will do the job. All VLAN are directly connected and there are routes between them. I use ACL, but you may try to delete route from route table (if is possible). I haven't tried this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-23-2010 11:50 AM
тАО03-23-2010 11:50 AM
Re: 5400yl restricting iSCSI network on its own VLAN
Perfect do you just have an ACL to deny all?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-24-2010 07:58 PM
тАО03-24-2010 07:58 PM
Re: 5400yl restricting iSCSI network on its own VLAN
Is there a reason you would give that iSCSI vlan a IP address? If not, then just create your VLAN, do not assign it an IP address which will make it a L2 VLAN only, so no reason I can think of to have to mess with ACLs (although ACLs are fine if you have to give the VLAN a IP address which would make it L3 and routable). Then the other step I'd look at would be to enable jumbo frames on that VLAN (of course, your NICs and SAN or whatever your connecting on that VLAN would have to support jumbo frames).
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP