Whilst at Cisco Networkers in Brisbane 2009 I prepare a blitz of social media. One of the things I did was use twitter to get the message out on Cisco UCS. The conference ran for 3 days and every 30 minutes between 9:00am and 5:00pm I sent a new UCS fact or tip. The purpose was to get discussion and interest going on this great technology. Hopefully it would get a few people coming to my Employers stand to talk UCS with me (which it did).

People who were not at the show found it helpful as well, there were many retweets.

Here is the list in all its glory. Its hard to say much in 140 characters!

1. Unless they are manually pinned, FLOGIs are assigned the FC uplinks in the appropriate VSAN in a round-robin fashion.
2. Menlo is the code name for one of the Mezz adapters. A CNA with 2 10GE (with failover) and 2 FC ports.
3. Oplin is the code name for one of the Mezz adapters. 2 10GE ports only, no failover functionality.
4. Palo is the code name for one of the futr Mezz adapters. Provides multiple Eth vNICs or FC vHBAs (limits apply)
5. The min between rails for chassis mounting is 74cm. Overall depth of chassis is 91cm if you include power cbls.
6. Understand those UCS acronyms in the UCS Dictonary of terms. http://rodos.haywood.org/2009/08/cisco-ucs-dictionary.html
7. If a F-I failes the dataplane failover depends on how you setup HA. Control plane (UCSM) takes approx 100 sec.
8. The IOM multiplexes IO ports & BMC from blades along with CMS and CMC to the 10GB ports (1,2or4) going to the F-I.
9. For only one Fabric-Interconnect (lab use maybe) you must place the IOM in left slot which is Fabric A.
10. Allow 2Kw per chassis of 8 blades. My testing shows @ 50% CPU load 1600 watts consumed.
11. Only the first 8 ports of the Fabric-Interconnect are licensed up front. Add port licenses for greater ports.
12. Create Pin Groups & apply to multiple service profiles to do manual pinning to North uplinks. else round robin.
13. The half width B200-M1 has 12 DIMM slots, the full width B250-M1 has 48 (but its not avail yet).
14. @stevie_chambers writes great information on operational practices with UCS. http://viewyonder.com/
15. Default F-I mode is end-host, North traffic is not switched rather each vNic is pinned to a uplink port or port channel.
16. If you need grid redundancy for you power ensure you order 4 PSUs as 3 only provides N+1 redundancy.
17. Smart Call Home is valid for Support Service or Mission Critical but NOT Warranty or Warranty Plus contracts.
18. You can not use 3 uplinks from an IOM to its Fabric-Interconnect, only 1,2 or 4.
19. LDAP for RBAC uses the mgmt port IP's on the F-I as source of reqsts, NOT the shared virtual IP address.
20. Server pools can auto populate based on qualification of mess adapter, RAM, CPU or disk.
21. A helpful list of UCS links and resources can be found at http://haywood.org/ucs/
22. The F-I's store their data on 256Gb of internal flash. Backup can be done from GUI or CLI to a remote sftp loc.
23. Templates can be either intial or updating. Modfying an updating template updates existing instances too.
24. In UCS maximum 242 VLANs are supported. Remember that VLANs 3968 to 4048 are reserved and can not be used.
25. Within the RBAC the privilages are for updating, everyone can view the UCSM configurations.
26. Serial EEPROM contain in chassis mid-plane helps resolve split brain of F-I, each half maint by each a IOM.
27. Warning. Even though the 61x0 Fabric-Interconnects are based on the Nexus 5000 they R not the same so don't compare btwn.
28. All uplinks from an IOM must go to the same Fabric-Interconnect.
29. Only the Menlo card does internal failover 4 Eth when a IOM looses an uplink.All other reqr host multipathing software.
30. KVM virtual media travels over the CMS network inside the IOM and therefore only runs at 100Mb.
31. There is a limit of 48 local users within UCSM, for more interface to RADIUS, LDAP or TACACS+.
32. UCSuOS - UCS Utility Operating System is "pre-OS configuration agent" for the blade, previously named PNuOS.
33. Fabric-Interconnect backup can be performed to either FTP, TFTP, SCP or SFTP destinations.
34. The CLI is organized into a hierarchy of command modes, use "scope" and mode name to move down modes.
35. @bradhedlund writes great technical information on UCS. http://www.internetworkexpert.org/
36. Each blade and chassis contains a locator beacon which flashes blue when enabled via the GUi, CLI or manually.
37. The F-I runs in NPV end-host not switch mode. You must connect to external FC storage via the expansion modules with FC.
38. UCSM split brains may be due to a partition in space or a partition in time.
39. An amber power light on the blade indicates standby state, green means powered on so check before removing it!
40. If there is a "*" next to the end of the scope in the CLI don't forget to execute "commit-buffer"!
41. Removing a blade will generate an event and set a presence of 'missing". The blade needs to be decomish from the ivntry.
42. UCSM lets you cfg >2 vNics/vHBAs. Atmpt to associate it and receive a major fault due to insuff'nt resc. Wait for Palo.
43. The "show tech-support" command details the config and state of your environment. Use liberally.
44. UCSM can pull stats at a collection interval of 30sec, 1 2 or 5 minutes. Modify via the collection policy.
45. Connect each Chassis IOM to its F-I via low cost Copper Twinax up to 5m, otherwise Fiber with apprt SFP+ trancvr.
46. Visio icons for UCS can be downloaded from http://www.cisco.com/en/US/products/prod_visio_icon_list.html
47. Cisco NetPro Forums has a Unified Computing section so learn, share, support. http://short.to/rv07
48. For further insights into UCS after Networkers follow my UCS feed for updates http://rodos.haywood.org/search/label/UCS