RE: Virtual IP and UCS Manager http://developer.cisco.com/c/message_boards/find_recent_posts?p_l_id= 2013-05-20T17:04:47Z 2013-05-20T17:04:47Z Tige Phillips http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=2458246 2010-08-21T05:21:25Z 2010-08-21T05:21:25Z

[quote]/me wants that App![/quote]   It's in the iTunes app store.  Search for "simu ucs".   -Tige

Tige Phillips 2010-08-21T05:21:25Z Tige Phillips http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=2349620 2010-07-12T23:18:52Z 2010-07-12T23:14:23Z

Switch A and B both need an individual IP Address.  They then share a common Virtual IP Address that you would use to manage the system.  You should always use the common because the active switch will always respond.  If you have an outage of a switch, the secondary will take over responding to the virtual ip address.     Look on the Admin tab, under Communication Management, under Management Interfaces.  Please see attached file screen-capture-237.   extIp is the out of band management address for a server.  It is created by the Management IP Pool (ext-mgmt).  If this is not set, then you will not be able to use KVM to the individual server as an example.  I think this is reliable.  It might also be possible to check the Management IP Pools and see what IP Addresses are assigned to what servers, but I have not checked.  Please see the second picture for what I'm talking about.    

Tige Phillips 2010-07-12T23:14:23Z Tige Phillips http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=2164798 2010-05-05T01:22:02Z 2010-05-05T01:21:12Z

It is discoverable.  See the ping traces below.  .30 is the VIP, .32 is the Primary, and .33 is the Subordinate.     I have not dug through the MIB to see if you can pull the real addresses.  The virtual will get you to the Primary, so you should almost for sure get the primarys real address.       dhcp-olympia-wa-32-142:~ tigelane$ ping 10.10.50.30 PING 10.10.50.30 (10.10.50.30): 56 data bytes 64 bytes from 10.10.50.30: icmp_seq=0 ttl=63 time=152.892 ms 64 bytes from 10.10.50.30: icmp_seq=1 ttl=63 time=163.818 ms ^C --- 10.10.50.30 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 152.892/158.355/163.818/5.463 ms dhcp-olympia-wa-32-142:~ tigelane$ ping 10.10.50.32 PING 10.10.50.32 (10.10.50.32): 56 data bytes 64 bytes from 10.10.50.32: icmp_seq=0 ttl=63 time=156.894 ms 64 bytes from 10.10.50.32: icmp_seq=1 ttl=63 time=106.485 ms ^C --- 10.10.50.32 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 106.485/131.690/156.894/25.204 ms dhcp-olympia-wa-32-142:~ tigelane$ ping 10.10.50.33 PING 10.10.50.33 (10.10.50.33): 56 data bytes 64 bytes from 10.10.50.33: icmp_seq=0 ttl=63 time=148.898 ms 64 bytes from 10.10.50.33: icmp_seq=1 ttl=63 time=100.470 ms ^C --- 10.10.50.33 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 100.470/124.684/148.898/24.214 ms dhcp-olympia-wa-32-142:~ tigelane$

Tige Phillips 2010-05-05T01:21:12Z Tige Phillips http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=2164717 2010-05-04T23:59:27Z 2010-05-04T23:59:27Z

You got a really old screen-shot Brian.  

Tige Phillips 2010-05-04T23:59:27Z Tige Phillips http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=2164715 2010-05-04T23:48:21Z 2010-05-04T23:48:21Z

I am working on test implementation of UCS API polling. During reading documentation I have found expression Virtual IP. What is realation of Virtual IP to UCS manager ? Is there any limitation with using API over specific Virtual IP ?   UCS is always deployed with redundant Fabric Interconnects (6100s) that form a cluster.  Each of those two 6100s has an IP Address.  A third IP Address to be used as the "floating/virtual" management address is also assigned to the system.  The "Primary" device of the two responds to management inquiries, telnet, ssh, etc on that third "floating/virtual" IP Address.  The address will always be "controlled" by the "Primary" 6100 in the system.  The "Subordinate" unit takes over management and that third IP Address if there is a failure on the Primary.   You should normally connect to the virtual/floating/third IP Address regardless of your connection type (GUI, SSH, Telnet, etc).  You should not connect directly to the IP Address configured on either of the 6100s unless you are doing something specific that requires it (some form of maintenance or troubleshooting possibly).   A quote from the UCS management architecture document: "A "floating" management IP address is configured on the active instance so that all GUI and command-line interface (CLI) connections and management operations are forced to initiate there. Configuration and operational state changes are then propagated over the private network from the active instance to the standby instance so that management information is synchronized."

Tige Phillips 2010-05-04T23:48:21Z