Port Address Translation (PAT) means using PORTS in order to NAT various Inside Local IPs to 1 Inside Global IP.
Step 1: Create an ACL with all the Inside Local addresses:
(config)#access-list 1 permit 10.2.2.0 0.0.0.7
Step 2: There are 2 ways to configure PAT, described in Steps 2.1 and 2.2:
Step 2.1:
- Create the Inside Global IP Pool of any addresses from the Link towards the other Router:
(config)#ip nat pool OVERLOAD 10.1.1.2 10.1.1.2 prefix-length 24
- Configure the NAT Overload with the defined pool:
(config)#ip nat inside source list 1 pool TASK2 overload
Step 2.2:
Configure the NAT to point to the Interface you need the traffic to go out from:
(config)#ip nat inside source list 1 interface s0/1/0.21
!!! The system adds "overload" argument:
(config)#do sh run | i nat inside
ip nat inside
ip nat inside source list 1 interface Serial0/1/0.21 overload
Load Balancing using NAT
This is a configuration that I´ve never implemented in any production environment, but I see quite a few cases where it can be usefull.
Step 1: Create a POOL of all the INSIDE IPs, and define the pool type: "type rotary":
(config)#ip nat pool TASK1 10.2.2.1 10.2.2.5 prefix-length 24 type rotary
Step 2: Define an ACL with the Inside Global IP (the one we´re NAT-ing into):
(config)#access-list 1 permit 200.2.2.2
Step 3: Do the inside NAT with the ACL 1 as the DESTINATION list, and the POOL or LOCAL IPs:
(config)#ip nat inside destination list 1 pool ?
WORD Pool name for local addresses
Step 4: Define the NAT inside and outside interfaces, exactly like in case of Static/Dynamic NAT:
(config)#int lo0
(config-if)#ip nat inside
(config-if)#
(config-if)#int s0/1/0.21
(config-subif)#ip nat outside
!!!Be sure that the routing is in place (both, go and return path towards the NAT-ed IP, 200.2.2.2)!!!
Step 5: Make sure that the IP NAT Translations are correct, and that the sources VARY:
#sh ip nat translations
Pro Inside global Inside local Outside local Outside global
tcp 200.2.2.2:23 10.2.2.1:23 131.1.12.1:20186 131.1.12.1:20186
tcp 200.2.2.2:23 10.2.2.2:23 131.1.12.1:25096 131.1.12.1:25096
tcp 200.2.2.2:23 10.2.2.3:23 131.1.12.1:20389 131.1.12.1:20389
Step 1: Create a POOL of all the INSIDE IPs, and define the pool type: "type rotary":
(config)#ip nat pool TASK1 10.2.2.1 10.2.2.5 prefix-length 24 type rotary
Step 2: Define an ACL with the Inside Global IP (the one we´re NAT-ing into):
(config)#access-list 1 permit 200.2.2.2
Step 3: Do the inside NAT with the ACL 1 as the DESTINATION list, and the POOL or LOCAL IPs:
(config)#ip nat inside destination list 1 pool ?
WORD Pool name for local addresses
Step 4: Define the NAT inside and outside interfaces, exactly like in case of Static/Dynamic NAT:
(config)#int lo0
(config-if)#ip nat inside
(config-if)#
(config-if)#int s0/1/0.21
(config-subif)#ip nat outside
!!!Be sure that the routing is in place (both, go and return path towards the NAT-ed IP, 200.2.2.2)!!!
Step 5: Make sure that the IP NAT Translations are correct, and that the sources VARY:
#sh ip nat translations
Pro Inside global Inside local Outside local Outside global
tcp 200.2.2.2:23 10.2.2.1:23 131.1.12.1:20186 131.1.12.1:20186
tcp 200.2.2.2:23 10.2.2.2:23 131.1.12.1:25096 131.1.12.1:25096
tcp 200.2.2.2:23 10.2.2.3:23 131.1.12.1:20389 131.1.12.1:20389
NAT - Dynamic NAT
1 - Define the POOL of the DESTINATION IPs (Public)
(config)#ip nat pool DESTIN 131.1.12.3 131.1.12.8 prefix-length 24
2 - Define the ACCESS-LIST of the PRIVATE IPs
(config)#access-list 1 permit 10.2.2.0 0.0.0.255
3- Implement the NAT from-ACL-to-POOL IPs
(config)#ip nat inside source list 1 pool DESTIN
Do not forget to configure the "ip nat inside | outside" on the appropriate interfaces!
#sh ip nat translations <- BE SURE TO PING SOMETHING BEFORE YOU CHECK THE TRANSLATIONS:
Pro Inside global Inside local Outside local Outside global
icmp 131.1.12.3:2 10.2.2.2:2 10.1.1.1:2 10.1.1.1:2
--- 131.1.12.3 10.2.2.2 --- ---
(config)#ip nat pool DESTIN 131.1.12.3 131.1.12.8 prefix-length 24
2 - Define the ACCESS-LIST of the PRIVATE IPs
(config)#access-list 1 permit 10.2.2.0 0.0.0.255
3- Implement the NAT from-ACL-to-POOL IPs
(config)#ip nat inside source list 1 pool DESTIN
Do not forget to configure the "ip nat inside | outside" on the appropriate interfaces!
#sh ip nat translations <- BE SURE TO PING SOMETHING BEFORE YOU CHECK THE TRANSLATIONS:
Pro Inside global Inside local Outside local Outside global
icmp 131.1.12.3:2 10.2.2.2:2 10.1.1.1:2 10.1.1.1:2
--- 131.1.12.3 10.2.2.2 --- ---
NAT - Static NAT
You can do STATIC NAT and just "go out" of the router with a different IP address:
*Traffic sourced from 10.2.2.1 will seem from 131.1.12.3
*Extendable is used if you need 1 LOCAL IP to be mapped to Various Public IPs
(config)#ip nat inside source static 10.2.2.1 131.1.12.3 [extendable]
Be sure to DEFINE the NAT INTERFACES:
(config)#int lo0 <- PRIVATE IP
(config-if)#ip nat inside
(config-if)#int s0/1/0.21 <- PUBLIC (Global) IP
(config-subif)#ip nat outside
#sh ip nat translations
Pro Inside global Inside local Outside local Outside global
--- 131.1.12.3 10.2.2.1 --- ---
Inside Local - Private IP of the host in your Network
Inside Global - Public IP that outside network sees your hosts as
Outside Local - How the local network sees IP of the remote host
Outside Global - Public IP of the remote host
If you want to do NAT for a SUBNET:
(config)#ip nat inside source static network 10.2.2.0 200.2.2.0 /24
*Traffic sourced from 10.2.2.1 will seem from 131.1.12.3
*Extendable is used if you need 1 LOCAL IP to be mapped to Various Public IPs
(config)#ip nat inside source static 10.2.2.1 131.1.12.3 [extendable]
Be sure to DEFINE the NAT INTERFACES:
(config)#int lo0 <- PRIVATE IP
(config-if)#ip nat inside
(config-if)#int s0/1/0.21 <- PUBLIC (Global) IP
(config-subif)#ip nat outside
#sh ip nat translations
Pro Inside global Inside local Outside local Outside global
--- 131.1.12.3 10.2.2.1 --- ---
Inside Local - Private IP of the host in your Network
Inside Global - Public IP that outside network sees your hosts as
Outside Local - How the local network sees IP of the remote host
Outside Global - Public IP of the remote host
If you want to do NAT for a SUBNET:
(config)#ip nat inside source static network 10.2.2.0 200.2.2.0 /24
Is SDN really the future?
For all the Network Engineers out there who, like myself, scream inside whenever someone confidently declares that SDN is the future - Don´t panic... But DO consider expanding your skill set with a bit of Scripting/ Process Automation and similar... just in case.
*this article was originally published by networkworld.com
"We are seeing clients looking to hire a lot more DevOps people, because they need folks not just with a tactical, technical skillset, but with the ability to collaborate and coordinate business efforts across different departments," says Laura McGarrity, vice president of marketing for Mondo, an IT recruiting, hiring, and consulting firm.
"Our clients are hearing the terms 'SDN' and 'DevOps' a lot, and they want to find out what DevOps means, how and where to place these positions in their organizations, and whether to hire from outside or to mold talent from within," says Felix Fermin, senior technical recruiter at Mondo.
SDNs essentially automate networking functions. By removing the intelligence from traditional networking hardware and delegating network decision-making capabilities to the server, the data layer (the actual information traveling on a network) is decoupled from the control layer (the technology that determines how, when, and where that information flows), and each layer is automated.
This means independent control of each layer is possible without either the expensive, complicated hardware and software (e.g., routers and switches) or the highly skilled professionals who manage those devices, says Steve Shah, senior director of product management, of the Netscaler group at Citrix.
This push toward automation is a crucial element of SDN technology and one of the main reasons DevOps experience will be in high demand, says Shah.
"The kind of expertise you'll look for is no longer a hard-core, specialized programmer who focuses on individual devices and pieces of the network, but someone who can write code or scripts to automate processes and actions," Shah says.
"You may have to let people go in order to add new folks with the right skills. You may have to look long and hard, and spend more money to find experienced DevOps people, because you're looking at folks with a programmer's salary and with senior experience." --Steve Shah, senior director of product management, of the Netscaler group at Citrix.
"You need programming and scripting expertise, yes, but also folks with the broader business knowledge to see the entire data center topography and where inefficiencies and bottlenecks are happening - DevOps," Shah says.
Say Goodbye to Network Troubleshooters (YES, This scares the *** out of Network Engineers)
What kind of people have these skills? Higher-level networking pros, middle management types and DevOps people, Shah says. While the conventional argument is that low-level, junior network troubleshooters are all that's needed to keep an automated network running, Shah says the opposite is true.
"I think, contrary to popular belief, that entry-level, network troubleshooters who have expertise only on specific devices will suffer," Shah says.
"What makes an elite networking person special is the ability not just to troubleshoot, but to see the larger network topography, to understand how and why processes are automated, and to perform complicated heuristics to quickly get to the root of the problem," Shah says. "These guys have both a breadth and a depth to their skill set; they know not just how to design and deploy an automated network but also how to troubleshoot and fix problems at the command line. That's valuable."
Kurt Marko, an author, networking consultant and analyst, agrees with Shah's assessment.
"The low-level command line expert's going to go the way of the shell-scripting Linux wizard, or the DOS guy who was really good at writing batch jobs -- in other words, extinct," Marko says.
"With SDNs, networking devices are becoming so much more programmable with higher-level languages, and the networking guys are going to have to reskill to learn automation tools, scripting languages and the like," Marko says.
A First Time for Everything.
There's some uncertainty involved in making such a huge shift, and the technology and hiring decisions may be different for each company, Citrix's Shah says. That's where having a DevOps strategy, even if it's vague, can be helpful.
"Many times CIOs are encountering the need to hire DevOps folks for the first time, and there's by no means one simple way to go about fulfilling this new demand," Shah says. "Businesses should be asking, 'Where do I put them? How do I find system administrators who can write code? Or programmers who understand the larger IT landscape? We have ERP or CRM programmers on staff already - do we go with what we've got, invest in additional education for them, and promote them? Or should we hire some hard-core programmers and try and teach them the business side?'," Shah says.
Many organizations are asking these same questions, says Mondo's Fermin. While some of Mondo's clients are looking to hire DevOps professionals, Fermin says, many are simply in the early stages of assessing whether or not such positions will be valuable to their business.
That said, the sudden spike in interest from clients has Mondo predicting a strong demand for SDN-related skillsets and DevOps professionals into 2014.
There's no right or wrong approach, says McGarrity, so for now Mondo is tackling the issue from both sides: counseling candidates on how to beef up existing skills or add new ones that are applicable to these kinds of positions, and on the hiring side advising clients on which skills to look for, or how to identify and mold talent from within, she says.
Those decisions are unique to the needs of each business, but Citrix's Shah notes that these hard questions can lead to some hard decisions.
"You may have to let people go in order to add new folks with the right skills. You may have to look long and hard, and spend more money to find experienced DevOps people, because you're looking at folks with a programmer's salary and with senior experience," he says.
You also must remember that DevOps folks need to be involved in higher-level business decisions so they can create software and automation processes that can act in concert with or react quickly to changing business requirements, he says.
The bottom line is that both businesses and technology professionals must accept and adapt to the new landscape of an automated data center, including SDNs, says Marko.
In this sense, the advent of SDNs follows the trajectory of other disruptive IT technologies.
"Server administrators had to learn virtualization technologies. Networking guys are going to have to do the same, now," Marko says. "While there's still some value in these high-level, specialized networking skill sets, these professionals are going to have to adapt to whatever new skills are necessary, or be out of a job," he says.
A must read:
Isaac Asimov - The Last Question
http://filer.case.edu/dts8/thelastq.htm
*this article was originally published by networkworld.com
"We are seeing clients looking to hire a lot more DevOps people, because they need folks not just with a tactical, technical skillset, but with the ability to collaborate and coordinate business efforts across different departments," says Laura McGarrity, vice president of marketing for Mondo, an IT recruiting, hiring, and consulting firm.
"Our clients are hearing the terms 'SDN' and 'DevOps' a lot, and they want to find out what DevOps means, how and where to place these positions in their organizations, and whether to hire from outside or to mold talent from within," says Felix Fermin, senior technical recruiter at Mondo.
SDNs essentially automate networking functions. By removing the intelligence from traditional networking hardware and delegating network decision-making capabilities to the server, the data layer (the actual information traveling on a network) is decoupled from the control layer (the technology that determines how, when, and where that information flows), and each layer is automated.
This means independent control of each layer is possible without either the expensive, complicated hardware and software (e.g., routers and switches) or the highly skilled professionals who manage those devices, says Steve Shah, senior director of product management, of the Netscaler group at Citrix.
This push toward automation is a crucial element of SDN technology and one of the main reasons DevOps experience will be in high demand, says Shah.
"The kind of expertise you'll look for is no longer a hard-core, specialized programmer who focuses on individual devices and pieces of the network, but someone who can write code or scripts to automate processes and actions," Shah says.
"You may have to let people go in order to add new folks with the right skills. You may have to look long and hard, and spend more money to find experienced DevOps people, because you're looking at folks with a programmer's salary and with senior experience." --Steve Shah, senior director of product management, of the Netscaler group at Citrix.
"You need programming and scripting expertise, yes, but also folks with the broader business knowledge to see the entire data center topography and where inefficiencies and bottlenecks are happening - DevOps," Shah says.
Say Goodbye to Network Troubleshooters (YES, This scares the *** out of Network Engineers)
What kind of people have these skills? Higher-level networking pros, middle management types and DevOps people, Shah says. While the conventional argument is that low-level, junior network troubleshooters are all that's needed to keep an automated network running, Shah says the opposite is true.
"I think, contrary to popular belief, that entry-level, network troubleshooters who have expertise only on specific devices will suffer," Shah says.
"What makes an elite networking person special is the ability not just to troubleshoot, but to see the larger network topography, to understand how and why processes are automated, and to perform complicated heuristics to quickly get to the root of the problem," Shah says. "These guys have both a breadth and a depth to their skill set; they know not just how to design and deploy an automated network but also how to troubleshoot and fix problems at the command line. That's valuable."
Kurt Marko, an author, networking consultant and analyst, agrees with Shah's assessment.
"The low-level command line expert's going to go the way of the shell-scripting Linux wizard, or the DOS guy who was really good at writing batch jobs -- in other words, extinct," Marko says.
"With SDNs, networking devices are becoming so much more programmable with higher-level languages, and the networking guys are going to have to reskill to learn automation tools, scripting languages and the like," Marko says.
A First Time for Everything.
There's some uncertainty involved in making such a huge shift, and the technology and hiring decisions may be different for each company, Citrix's Shah says. That's where having a DevOps strategy, even if it's vague, can be helpful.
"Many times CIOs are encountering the need to hire DevOps folks for the first time, and there's by no means one simple way to go about fulfilling this new demand," Shah says. "Businesses should be asking, 'Where do I put them? How do I find system administrators who can write code? Or programmers who understand the larger IT landscape? We have ERP or CRM programmers on staff already - do we go with what we've got, invest in additional education for them, and promote them? Or should we hire some hard-core programmers and try and teach them the business side?'," Shah says.
Many organizations are asking these same questions, says Mondo's Fermin. While some of Mondo's clients are looking to hire DevOps professionals, Fermin says, many are simply in the early stages of assessing whether or not such positions will be valuable to their business.
That said, the sudden spike in interest from clients has Mondo predicting a strong demand for SDN-related skillsets and DevOps professionals into 2014.
There's no right or wrong approach, says McGarrity, so for now Mondo is tackling the issue from both sides: counseling candidates on how to beef up existing skills or add new ones that are applicable to these kinds of positions, and on the hiring side advising clients on which skills to look for, or how to identify and mold talent from within, she says.
Those decisions are unique to the needs of each business, but Citrix's Shah notes that these hard questions can lead to some hard decisions.
"You may have to let people go in order to add new folks with the right skills. You may have to look long and hard, and spend more money to find experienced DevOps people, because you're looking at folks with a programmer's salary and with senior experience," he says.
You also must remember that DevOps folks need to be involved in higher-level business decisions so they can create software and automation processes that can act in concert with or react quickly to changing business requirements, he says.
The bottom line is that both businesses and technology professionals must accept and adapt to the new landscape of an automated data center, including SDNs, says Marko.
In this sense, the advent of SDNs follows the trajectory of other disruptive IT technologies.
"Server administrators had to learn virtualization technologies. Networking guys are going to have to do the same, now," Marko says. "While there's still some value in these high-level, specialized networking skill sets, these professionals are going to have to adapt to whatever new skills are necessary, or be out of a job," he says.
A must read:
Isaac Asimov - The Last Question
http://filer.case.edu/dts8/thelastq.htm
Configure SSH Access
Cisco Documents:
Security>AAA>Secure Shell Configuration Guide
http://www.cisco.com/en/US/docs/ios-xml/ios/sec_usr_ssh/configuration/12-4t/sec-cfg-secure-shell.html
First step would be to make sure that all the devices within your network SUPPORT the Secure Shell. The you need to make sure HOW you want to implement it, as there are 2 options:
1. Configuring a Router for SSH Version 2 Using a Hostname and Domain Name
2. Configuring a Router for SSH Version 2 Using RSA Key Pairs
In the first configuration type, these are the steps to follow:
Step 1: Be sure to have the Hostname and the IP Domain Name configured:
(config)#ip domain name SNArchs
Step 2: Decide the key pair (in bits, by defaut its 512 bits) and generate the RSA key. This ENABLES SSHv2:
(config)#crypto key generate rsa usage-keys
The name for the keys will be: ES-MAT-AES-SR04.SNArchs
Choose the size of the key modulus in the range of 360 to 2048 for your
Signature Keys. Choosing a key modulus greater than 512 may take a few minutes.
How many bits in the modulus [512]:
Choose the size of the key modulus in the range of 360 to 2048 for your
Encryption Keys. Choosing a key modulus greater than 512 may take a few minutes.
How many bits in the modulus [512]: 512
% Generating 512 bit RSA keys, keys will be non-exportable...[OK]
% Generating 512 bit RSA keys, keys will be non-exportable...[OK]
*Dec 5 12:58:48.123: %SSH-5-ENABLED: SSH 2.0 has been enabled
Then configure the VTY port for the user database to use (TACACS or LOCAL), and to use SSH:
(config)#line vty 0 4
(config-line)#login local <-WONT BE AVAILABLE AFTER SSH IS ENABLED
(config-line)#transport input ssh
*When testing the access via SSH don't forget to use the "-l" to define the username:
#ssh -l mat 10.1.12.2
You can also use AAA to define the AUTHENTICATION PROFILE (AAA_AUTH), that can later be applied to ALL VTY ports:
(config)#aaa new-model
(config)#aaa authentication login AAA_AUTH local
Now apply it to the VTY port:
(config)#line vty 0 4
(config-line)#transport input ssh
(config-line)#login authentication AAA_AUTH
*"rotary" command under the VTY changes the telnet port to that line. "rotary 5" sets the port on that line to 3005
Security>AAA>Secure Shell Configuration Guide
http://www.cisco.com/en/US/docs/ios-xml/ios/sec_usr_ssh/configuration/12-4t/sec-cfg-secure-shell.html
First step would be to make sure that all the devices within your network SUPPORT the Secure Shell. The you need to make sure HOW you want to implement it, as there are 2 options:
1. Configuring a Router for SSH Version 2 Using a Hostname and Domain Name
2. Configuring a Router for SSH Version 2 Using RSA Key Pairs
In the first configuration type, these are the steps to follow:
Step 1: Be sure to have the Hostname and the IP Domain Name configured:
(config)#ip domain name SNArchs
Step 2: Decide the key pair (in bits, by defaut its 512 bits) and generate the RSA key. This ENABLES SSHv2:
(config)#crypto key generate rsa usage-keys
The name for the keys will be: ES-MAT-AES-SR04.SNArchs
Choose the size of the key modulus in the range of 360 to 2048 for your
Signature Keys. Choosing a key modulus greater than 512 may take a few minutes.
How many bits in the modulus [512]:
Choose the size of the key modulus in the range of 360 to 2048 for your
Encryption Keys. Choosing a key modulus greater than 512 may take a few minutes.
How many bits in the modulus [512]: 512
% Generating 512 bit RSA keys, keys will be non-exportable...[OK]
% Generating 512 bit RSA keys, keys will be non-exportable...[OK]
*Dec 5 12:58:48.123: %SSH-5-ENABLED: SSH 2.0 has been enabled
Then configure the VTY port for the user database to use (TACACS or LOCAL), and to use SSH:
(config)#line vty 0 4
(config-line)#login local <-WONT BE AVAILABLE AFTER SSH IS ENABLED
(config-line)#transport input ssh
*When testing the access via SSH don't forget to use the "-l" to define the username:
#ssh -l mat 10.1.12.2
You can also use AAA to define the AUTHENTICATION PROFILE (AAA_AUTH), that can later be applied to ALL VTY ports:
(config)#aaa new-model
(config)#aaa authentication login AAA_AUTH local
Now apply it to the VTY port:
(config)#line vty 0 4
(config-line)#transport input ssh
(config-line)#login authentication AAA_AUTH
*"rotary" command under the VTY changes the telnet port to that line. "rotary 5" sets the port on that line to 3005
AAA Authentication
Cisco Docs: Securing User Services Configuration>Authentication Authorization and Accounting
http://www.cisco.com/en/US/docs/ios-xml/ios/sec_usr_aaa/configuration/12-4t/sec-cfg-authentifcn.html
This is pretty straight forward, because on CCIE R&S exam you wont have to configure an actual ACS server. For starters be sure that the "aaa new-model" is configured.
Turn the TACACS+ authentication ON, and set LOCAL DB as backup:
(config)#aaa authentication login MYTACACS group tacacs+ local enable
*MYTACACS is the authentication policy. If you put "default" instead of specifying the policy, there is no need to assign the policy to VTY line later, it's a default policy on a device, from where ever you try to authenticate. In case you have a default policy, you need to ALSO define a NO_AUTH policy to apply where you dont want TACACS, like AUX and CONSOLE ports maybe.
Define the TACACS+ as a server, and set the Shared Secret:
(config)#tacacs-server host 10.1.1.10 key cisco
Define the source interface from which you will authenticate:
(config)#ip tacacs source-interface Loopback0
Apply the authentication settings to the VTY line:
(config-line)#login authentication MYTACACS
Test the access USERNAME/PASSWORD via TACACS:
#test aaa group tacacs+ USERNAME PASSWORD legacy
http://www.cisco.com/en/US/docs/ios-xml/ios/sec_usr_aaa/configuration/12-4t/sec-cfg-authentifcn.html
This is pretty straight forward, because on CCIE R&S exam you wont have to configure an actual ACS server. For starters be sure that the "aaa new-model" is configured.
Turn the TACACS+ authentication ON, and set LOCAL DB as backup:
(config)#aaa authentication login MYTACACS group tacacs+ local enable
*MYTACACS is the authentication policy. If you put "default" instead of specifying the policy, there is no need to assign the policy to VTY line later, it's a default policy on a device, from where ever you try to authenticate. In case you have a default policy, you need to ALSO define a NO_AUTH policy to apply where you dont want TACACS, like AUX and CONSOLE ports maybe.
Define the TACACS+ as a server, and set the Shared Secret:
(config)#tacacs-server host 10.1.1.10 key cisco
Define the source interface from which you will authenticate:
(config)#ip tacacs source-interface Loopback0
Apply the authentication settings to the VTY line:
(config-line)#login authentication MYTACACS
Test the access USERNAME/PASSWORD via TACACS:
#test aaa group tacacs+ USERNAME PASSWORD legacy
Subscribe to:
Posts (Atom)
Most Popular Posts
-
Follow @SnarchsCOM First let's establish the difference between the NFV and the VNF: VNF (Virtualized Network Function) refers to ... -
Before we start, lets once again make sure we fully understand what Bridge Domain is. The bridge domain can be compared to a giant distribut... -
Before I get into the Python for NX-OS, let me explain a few concepts that I've seen Network Engineers have been struggling with. Dev... -
The VM-Series firewall for VMware NSX is jointly developed by Palo Alto Networks and VMware. NetX APIs are used to integrate the Palo Alto N...
-
Unified Fabric is a term for all of the equipment that makes LAN and SAN possible. There are two different networks (LAN as Front-end an... -
Ever since Cisco bought Insieme and created Cisco ACI, and VMware bought Nicira and created NSX, I've been intensively deep-diving and b...
-
By know you should know the following facts about ACI: Cisco Nexus 9k Switches make the ACI Fabric, which is the Control and the Data pla... -
Before we get deeper into the ACI (Application Centric Infrastructure) as the Cisco's official SDN solution, we need to clarify a few te... -
First of all, I need to explain why I decided to write such a post. It's quite simple to everyone who ever tried to Deploy/Configure/Und... -
Google has made their Cloud Platform (GCP) so that you can host your application any way your business requires. When we talk about the ...
