We are buying ACEs. We're having an outside contractor do the initial implementation, but I'll be maintaining after they leave, so I'm reading to get conversant with the technology.
I've come across config instructions that seem to mean the VIP of a server farm is the IP address of the interface for the VLAN the real servers are in.
Is that true?
Later... In the same doc (full doc details below...), near the end of "Configuring Basic...", in the Verifying the VIP Load-Balancing section, it says "You can also verify access to the real servers by using a Telnet session to connect to the VIP address". But the address they use to demonstrate (172.19.110.9) was not configured on anything in this doc. And it certainly isn't the IP address of the interface for the VLAN the real servers are in... I think I'm confused...
Wait - Steps 5 & 6, in Configure the VIP Traffic Policy creates a class-map, then does "match virtual-address 172.19.110.9 any". Is THAT where the VIP gets created?
(My first instinct, before any reading, was that you'd somehow assign an IP address to the server farm itself. But this doc doesn't say any such thing.)
Also - It seems to me this means that implementing smaller server farms (one farm for 5 web servers for instance, another for 5 ftp servers...) requires subnetting if you don't want to waste huge piles of address space. True?
(I know this is very basic stuff - any and all guidance/confirmation/correction most sincerely appreciated...)
The VIP has nothing to do with how the real servers are subnetted. The VIP is just the IP address clients connect to, and serverfarms are simply a list of real servers that are assigned to service a VIP. The VIP does not need to be part of same subnet as the real servers.
In your example you can have 5 web servers and 5 ftp servers all on the same subnet if you wish:
Moquery is the command line cousin of Vizore, it's very helpful and efficient sometimes during the troubleshooting. This article aims to provide moquery cheat sheet to the users for some most common seen scenarios.
Here is the checklist before customers/partners contact Cisco TAC:
Firmware Version of APIC and Switch
Download Switch and APIC techsupport logs
Problem description (Symptoms with details)
Business impact (eg, what kind of services...
moquery usageAPIC moquerySwitchmoquery
This document discuss a common issue observed during the VMM integration & VM workload migration to ACI fabric.
VMware Virtual machines are hosted in Cisco UCS-B seri...