Cisco UCS steps :-
First Time setup :
1)Configure the Fabric InterconnectA and floating IP
2)Configure Fabric Interconnect B ip
3)Chasis Discovery Policy(1-uplink,2-uplink,4uplink) configure your minimum uplink policy
4)Power Policy (n+1 or grid)
5)MAC Address Table Aging.(mostly deafult)
6) DNS serevr and time serevrs and syslog----------Pending
7)Maintence Polices
8)Network Polices
9)Configure Storage uplinks---------Pending
10)COnfigure Server ports
11)Configure Network Ports
12)Boot Policy
13)Syslog---------------Pending
14)Settings in Admin Tab
15)Call Home-----------------Pending
16)
Step 2 :-
Pools Creation :-
Reset Cisco UCS Blade
Create EX-Mgmt Pool
Create UUID Pool
Create MAC Pool for server profile
FAB A
FAB B
Create WWN pools
FAB A
FAB B
Create WWPN Pools
FAB A
FAB B
Create Global Vlans
Create GLoal VSan
Assign VSAN to FC Uplink
Create vNIC Template
Create vHBA Template
Define Boot Policy
Define Polices
Create Servive Profile for single Blade
pair of Nexus 7K vPC
Uplink Connectivity :-
UPlink Config from interconnect to Core Network Switches.
1) Atleast two uplinks from interconnect to Core Network Switches
2) or Use VPC(Virtual port channel if these are nexsus 7000 series)
3) Configure interface in trunk mode
4) Configure Sapnning tree portfast trunk(So that failover happen faster)
5)Specify Vlans to trunk
6)CreaTE PORT CHANNELS AND ADD INTERFACES .Port channel must be lacp active mode.
7)uplinked Switches must be trunk vlans to UCS.
8)Use pin gourps for DMZ atleeast UCSM 2.0
FC SAN COnnectivity :-
NPIV should be enabled on FC switch
NPV should be enabled on FI
FC switch sees FI as bunch of WWPN and WWNN names
Tuesday, March 27, 2012
FI commads
UCLI COmmands :
?
show
scope
top/up
where
connect
SSH to cluster IP :
#? shows all your commands
#where (shows your peresnt location )
#show ? (will show all your operation you can use)
#scope (Zoom down to particular item and dig into it )
#scope chassis 1 (will get you in chasis one to look into details)
#up (goes back to pervious state )
#top (goes all the way back to start of ssh ip )
#connect (Connect to NX os or frabirc to do failover and others)
UCS-A# connect local-mgmt (for performing ping and local operations on that fabric)
UCS-A(local-mgmt) # enable cluster virtual-ip-addr(enable Cluster Mode)
Changing Mgmt subnet of a Cluster :
UCS-A # scope fabric-interconnect a
set out-of-bandip ip-address netmask ip-netmask gw gateway-Ip-Addr
UCS-A # scope fabric-interconnect b
set out-of-bandip ip-address netmask ip-netmask gw gateway-Ip-Addr
UCS-A /fabric-interconnect # scope system
UCS-A /sytem #set virtual-ip ip-add
UCS-A /system #commit-buffer
Set end Host mode :-
UCS-A#scope eth-uplink
UCS-A /eth-uplink #set mode end-host
UCS-A /eth-uplink #commit-buffer
FI will reboot after this
Set system Name :-
UCS-A#scope system
UCS-A /system #set name DOmainname
UCS-A /system #commit-buffer
Move Primary to secondary for Maintence :-
UCS-A#connect local-mgmt
UCS-A(local-mgmt)#cluster lead B(name of FI to want to make as primary)
UCS-A(local-mgmt)#show cluster extendedstate
UCS-A(Local-mgmt)#Cluster force B(When you want to chnage the FI and force it)
-------------------------------------------------
Split Brain in FI :Both FI think that they are the primary FI."Partition in space " to FI can not speak with each other.
Partition in time :time mismatch in FI who ever wirtes seeprom.
?
show
scope
top/up
where
connect
SSH to cluster IP :
#? shows all your commands
#where (shows your peresnt location )
#show ? (will show all your operation you can use)
#scope (Zoom down to particular item and dig into it )
#scope chassis 1 (will get you in chasis one to look into details)
#up (goes back to pervious state )
#top (goes all the way back to start of ssh ip )
#connect (Connect to NX os or frabirc to do failover and others)
UCS-A# connect local-mgmt (for performing ping and local operations on that fabric)
UCS-A(local-mgmt) # enable cluster virtual-ip-addr(enable Cluster Mode)
Changing Mgmt subnet of a Cluster :
UCS-A # scope fabric-interconnect a
set out-of-bandip ip-address netmask ip-netmask gw gateway-Ip-Addr
UCS-A # scope fabric-interconnect b
set out-of-bandip ip-address netmask ip-netmask gw gateway-Ip-Addr
UCS-A /fabric-interconnect # scope system
UCS-A /sytem #set virtual-ip ip-add
UCS-A /system #commit-buffer
Set end Host mode :-
UCS-A#scope eth-uplink
UCS-A /eth-uplink #set mode end-host
UCS-A /eth-uplink #commit-buffer
FI will reboot after this
Set system Name :-
UCS-A#scope system
UCS-A /system #set name DOmainname
UCS-A /system #commit-buffer
Move Primary to secondary for Maintence :-
UCS-A#connect local-mgmt
UCS-A(local-mgmt)#cluster lead B(name of FI to want to make as primary)
UCS-A(local-mgmt)#show cluster extendedstate
UCS-A(Local-mgmt)#Cluster force B(When you want to chnage the FI and force it)
-------------------------------------------------
Split Brain in FI :Both FI think that they are the primary FI."Partition in space " to FI can not speak with each other.
Partition in time :time mismatch in FI who ever wirtes seeprom.
Wednesday, March 14, 2012
UCS Techsupport operations
Interconnect : reboot command will reboot the interconnect.
I/O module Reset : Hot Pull and Plug back the I/O module.
Equipment ->Chasis -> IO Module -> IO Module 1
BMC: Baseboard Managment Controllers for out of band management on each blade and monioters the blades.
CMC : Chasis Management Controller -->:lives of FEX and performs monitoring of the chasis
I/O Adapters on blades out put can redirected to CSV
Commands to check status:
connect local-mgmt
Show tech-support ucsm brief
show tech-support ucsm detail
Dir workspace:///what ever
copy workspace://what ever scp://dir/what ever
show tech-support chasis ---gives information on chasis,Blades,fex,I/O modules and BMC can be filtered.
Setting Threshold Polices:-
We can set thresolds on each
all sorts if ethernet port stats
FC port
vNIC Port
I/O module Reset : Hot Pull and Plug back the I/O module.
Equipment ->Chasis -> IO Module -> IO Module 1
BMC: Baseboard Managment Controllers for out of band management on each blade and monioters the blades.
CMC : Chasis Management Controller -->:lives of FEX and performs monitoring of the chasis
I/O Adapters on blades out put can redirected to CSV
Commands to check status:
connect local-mgmt
Show tech-support ucsm brief
show tech-support ucsm detail
Dir workspace:///what ever
copy workspace://what ever scp://dir/what ever
show tech-support chasis ---gives information on chasis,Blades,fex,I/O modules and BMC can be filtered.
Setting Threshold Polices:-
We can set thresolds on each
all sorts if ethernet port stats
FC port
vNIC Port
Service Profiles
Service Profiles :
Two models
1)Basic Opt-in Model :-Traditainal blade servers in that hardware defaults are used no logical pools.
2)Logical Server Pot-IN :- use pools for indentifiers and other information.When you move a profile
all the identifiers intact move as well.
3)Make sure your pools are designed first since this requires some planning before.
Service Profile Templates :-
Service profile Templates allow you to spawn new profiles.They are two templates.
Intial Template :
If you modify the template the changes do not get passed to those porfiles
created from the templates
Updating Template:
If you make a change to the template that change gets pushed down to the profiles created from the
template.Need to set Mantinaece policy so that Blades do not reboot with notice.you can set user Ack.
---------------------------------------------------------------------------------------------
Native Vlan frames comming and out are not tag . Examples Windows Machine and it need only one
vlan .
IPMI : Help DPM in case of VMware to power down server and bring them up when the need arise .
Autodeploy : Is boot from nothing ,it does a pix boot to a boot server and pool everyhting from Vcenter builds the image and runs on memmory .
Two models
1)Basic Opt-in Model :-Traditainal blade servers in that hardware defaults are used no logical pools.
2)Logical Server Pot-IN :- use pools for indentifiers and other information.When you move a profile
all the identifiers intact move as well.
3)Make sure your pools are designed first since this requires some planning before.
Service Profile Templates :-
Service profile Templates allow you to spawn new profiles.They are two templates.
Intial Template :
If you modify the template the changes do not get passed to those porfiles
created from the templates
Updating Template:
If you make a change to the template that change gets pushed down to the profiles created from the
template.Need to set Mantinaece policy so that Blades do not reboot with notice.you can set user Ack.
---------------------------------------------------------------------------------------------
Native Vlan frames comming and out are not tag . Examples Windows Machine and it need only one
vlan .
IPMI : Help DPM in case of VMware to power down server and bring them up when the need arise .
Autodeploy : Is boot from nothing ,it does a pix boot to a boot server and pool everyhting from Vcenter builds the image and runs on memmory .
Sunday, March 11, 2012
UCS Pools
Pools:-
Management IP Address Pool:Pool of IP addresses used to access a server via the CIMC(Cisco Intergarted Managment Controller)
Examples:KVM,serial over Lan.Mgmt IP are accessed through Mgmt Ports on FI and connections are
distributed half & Half .If you lose an FI you will lose half of the KVM access.No taging on MGMT IP's.
Can be added to :Serive profiles,Servers and thorugh Template pool oh MGMT
Check if the Management IP on FI are same a Managemtn pools ?
UUID Pools:for servers, Similar to Serial Number,32 hex digit,only sufix is changed
MAC Address Pools:-LAN ->Pools--MAC Pools,00:25:B5 is cisco MAC start (Organization Unique identifier),Cannot chnage MAC pool name once created.
WWNN Pools:have 00:25:B5 total address 20:OA:00:25:XX:XX:XX gerally start with NAA -20 NAA-50 reservered for sttroage arrays
WWPN Pools:
Server Pools
Server Pool Memebership
Tuesday, March 6, 2012
UCS Pools
Pools:-
Management IP Address Pool:Pool of IP addresses used to access a server via the CIMC(Cisco Intergarted Management Controller)
Examples:KVM,serial over Lan.Mgmt IP are accessed through Mgmt Ports on FI and connections are
distributed half & Half .If you lose an FI you will lose half of the KVM access.No taging on MGMT IP's.
Can be added to :Serive profiles,Servers and thorugh Template pool oh MGMT
Check if the Management IP on FI are same a Managemtn pools ?
UUID Pools:for servers, Similar to Serial Number,32 hex digit,only sufix is changed
MAC Address Pools:-LAN ->Pools--MAC Pools,00:25:B5 is cisco MAC start (Organization Unique identifier),Cannot chnage MAC pool name once created.
WWNN Pools:have 00:25:B5 total address 20:OA:00:25:XX:XX:XX gerally start with NAA -20 NAA-50 reservered for sttroage arrays
WWPN Pools:
Server Pools
Server Pool Memebership
UCS SAN Config
UCS uses the concept of service proflies for flexibility and mobility .To utilize stateless
ness of the blades you have to use boot from SAN using FC or iSCSi protocals from ucsm 2.0.
Reason why iSCSI or FC should be used is becoz of block level protocal.We can not use NFS since this file based stroage protocal.
FIber Channel:
Operates in 1,2,4 ,8 and 16 Gb speeds ,Block Level Acess to stroage,servers use HBA to connect to storage Array using optical cables.
Servers are called initiators.Storage array is usually known as targets
To allow the two to comminicate we perform Zoning.You zone one or more initators to one or more targets.
Zoening is done on switches (MDC,Brocade,Macdata).Once you Zone you should also make sure server see the LUN is wants to and mask all the other Lun
using LUN making this is supported by stroage array.
HBA has two part A world Wide Node Name for HBA and depending on the number of ports on HBA it would have one or two World Wide Port Name.
Example DUAL PORT HBA would have one WWNN and Two WWPN names. When you zone you zone them to WWPN not WWNN and make sure one port goes to one frabric
and other ports goes to another fabric.
Ports types:
N_Ports- Node ports,a port on the end node (Server or stroage array)
E-ports - expanssion Ports ,usaually connect to switches.
F-ports - Fabric ports,ports on a switch that connect N-Ports
Cisco UCS uses a technology known as N_Port ID Virtulization (NPIV).
NPIV allows a single N-Port to have many initators behind it.NPIV is enabled on FC Switch this lets
the FC hosts to see the FI as bunch of WWPN and WWNN like networking End host mode.FI use NPV not on the FC switch.
FC Switching Modes :
FC End host host mode: Uses NPIV,appers to Host as bunch of WWPN numbers.
FC Switching Mode
Fiber channel Port -Channels and Trunking:
Similar to Ethernet port Channels,bind multiple uplinks together if one fails other take over and better
load dsitribution only supported on MDS and Nexus FC Switch.
Trunking is smilar to ethernet Trunks: Allows for multiple VSANs over links.
6100 -- FC ports are located on Expansion Module
6200 -- use slider to ajust the port port on left are ethernet,right are FC and expasion module
FCoE: Fibre Channel encapsulated in ethernet.
Subscribe to:
Posts (Atom)