- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Virtual Routing Forward (VRF) with Virtual Connect...
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
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
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
11-03-2010 12:12 PM
11-03-2010 12:12 PM
Virtual Routing Forward (VRF) with Virtual Connect Flex-10
Mara had a Virtual Connect packet question:
********************
Hi all
I have a Virtual Connect Flex-10 connected to a top of rack switch that supports the VRF protocol.
The customer wants to know how the VC works in this case. Does it support the VRF ? Does it forward the package to servers?
*****************
Ramu replied:
*********************
VRF is a Layer 3 protocol to have multiple routing tables within a same router. This is used in VPN configurations primarily.
Virtual Connect operates only at Layer 2. Based on the routing table and servers' default gateway, packets would be forwarded.
**********************
Anyone else run into this requirement? Any comments or suggestions?