如何導入SDN的優點到傳統網路
摘自: http://searchsdn.techtarget.com/tip/How-to-assess-the-benefits-of-SDN-in-your-network?utm_content=control&utm_medium=EM&asrc=EM_ERU_74610891&utm_campaign=20170324_ERU%20Transmission%20for%2003/24/2017%20(UserUniverse:%202335837)&utm_source=ERU&src=5621330
Find out what three networking problems the benefits of SDN could address in your network and the questions you should ask to make sure you're on the right track.
Software-defined networking has matured from a science experiment into deployable, enterprise-ready technology in the last several years, with vendors from Big Switch Networks and Pica8 to Hewlett Packard Enterprise and VMware offering services for different use cases. Still, Nemertes Research's 2016 Cloud and Data Center Benchmark survey found a little more than 9% of organizations now deploying SDN in production.
In terms of the benefits of SDN, let's look at three of the most important problems the technology can solve, along with some considerations you can use to decide how SDN could help you.
1. More intelligent access.
2. Network virtualization
3. Data center network automation
~
So, is it time for you to look at SDN? Consider the answers to the following questions as you go through the decision-making process.
1. Is the relevant network -- access edge, data center or both -- ready for SDN as is? In other words, is your network gear of relatively recent enough vintage that it can be a part of an OpenFlow-based software-defined network?
2. If not, is it time for a refresh? If the answer is yes, you can make SDN a key criterion in the decision about what to replace it with.
If it's not refresh time, is the problem you face acute enough to justify a replacement outside of the regular refresh cycle? You can also consider overlaying an SDN infrastructure selectively, adding the necessary gear only where it is needed most urgently and expanding from there.
3. Can your vendor or provider give you a validated architecture or blueprint for deployment that addresses your specific requirements?
4. Can your vendor give you references to people in other organizations who have done what you want to do, or who have done something similar enough that their experience can serve as a guidepost?
5. Can you carve off a meaningful piece of the problem to solve in a pilot deployment with minimal investment of equipment and time? You shouldn't have to make an all-or-nothing transition to a new platform without a chance to test in place that it can work for you.
6. Do you have a robust change management process? You need one when you make a fundamental shift in technology.
7. If you are aiming to address a data center issue, especially in support of microsegmentation, do you have solid relationship mapping information for the systems there? That is, do you understand fully the relationships among the systems to which you are seeking to apply microsegmentation? Early adopters in the space have repeatedly told Nemertes their projects slowed down dramatically when they realized how incomplete their knowledge was about which systems really needed to talk to each other. It isn't hard to find out which ones are talking to each other. It's much harder to know which ones should be talking to each other.
http://searchsdn.techtarget.com/answer/How-will-virtual-routing-software-affect-the-networking-industry?utm_content=control&utm_medium=EM&asrc=EM_ERU_74610266&utm_campaign=20170324_ERU%20Transmission%20for%2003/24/2017%20(UserUniverse:%202335837)&utm_source=ERU&src=5621330
1. More intelligent access.
2. Network virtualization
3. Data center network automation
~
So, is it time for you to look at SDN? Consider the answers to the following questions as you go through the decision-making process.
1. Is the relevant network -- access edge, data center or both -- ready for SDN as is? In other words, is your network gear of relatively recent enough vintage that it can be a part of an OpenFlow-based software-defined network?
2. If not, is it time for a refresh? If the answer is yes, you can make SDN a key criterion in the decision about what to replace it with.
If it's not refresh time, is the problem you face acute enough to justify a replacement outside of the regular refresh cycle? You can also consider overlaying an SDN infrastructure selectively, adding the necessary gear only where it is needed most urgently and expanding from there.
3. Can your vendor or provider give you a validated architecture or blueprint for deployment that addresses your specific requirements?
4. Can your vendor give you references to people in other organizations who have done what you want to do, or who have done something similar enough that their experience can serve as a guidepost?
5. Can you carve off a meaningful piece of the problem to solve in a pilot deployment with minimal investment of equipment and time? You shouldn't have to make an all-or-nothing transition to a new platform without a chance to test in place that it can work for you.
6. Do you have a robust change management process? You need one when you make a fundamental shift in technology.
7. If you are aiming to address a data center issue, especially in support of microsegmentation, do you have solid relationship mapping information for the systems there? That is, do you understand fully the relationships among the systems to which you are seeking to apply microsegmentation? Early adopters in the space have repeatedly told Nemertes their projects slowed down dramatically when they realized how incomplete their knowledge was about which systems really needed to talk to each other. It isn't hard to find out which ones are talking to each other. It's much harder to know which ones should be talking to each other.
Virtual Routing Software
http://searchsdn.techtarget.com/answer/How-will-virtual-routing-software-affect-the-networking-industry?utm_content=control&utm_medium=EM&asrc=EM_ERU_74610266&utm_campaign=20170324_ERU%20Transmission%20for%2003/24/2017%20(UserUniverse:%202335837)&utm_source=ERU&src=5621330
留言
張貼留言