Traditional best practices is to separate iscsi and network switches onto their own switches. We are preparing to deploy Nexus 5596UP's for our switching fabric and move to 10gb. I have been giving serious consideration to combining iscsi and traditional network on the same set of switches, while using VLAN's to segregate the traffic and utilizing NCIO and SCIO with VMWare's VDS to QoS the traffic.
I have been searching for customers/white papers, tech briefing's, etc. that go into detail about experiences and results of this approach and have come relatively dry. Unfortunately I do not have the opportunity to vet such a configuration, so I am looking for community opinions on the viability of taking this approach.
I know the bandwidth is available to handle this. I also realize some of the caveats that come up as a result of such a configuration. Please understand, there would still be redundant switches to handle multipathing and link resilency. We have 28 hosts, 1200 VM's and about 120tb of data supporting our virtual environment, running on ESXi 5.x.
Looking forward to hearing from some of the experienced users in the community on why this approach would or would not be advisable. I do realize I left out some details, but in an effort to keep the original post shorter.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.