Total Pageviews

MDS Blogs

Please visit
http://mds9000.blogspot.com for
MDS Config and Troubleshooting Info.

-jerome.jsph@gmail.com

UCS Config -Disclaimer

Please note that this is just a lab recreation and documentation, this is no way replaces official manual and best pratice documentations

Wednesday, May 26, 2010

Palo_PTS2

 
http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-05%20at%202.05.48%20PM.png
 
 
  Verify in Vcenter: http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-05%20at%202.07.17%20PM.png
 
 

8.Installing the Palo Card: http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-05%20at%202.09.55%20PM.png
 

9. Enable static 2 VNICs and HBAs if needed on PALO
http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-05%20at%202.12.20%20PM.png
 
10 Enable Directed I/O n BIOS

http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-05%20at%202.22.43%20PM.png
 
 11. Create Dynamic Vnic policy: total # of vnics = (number of uplinks between IOM and FI * 15) -2 ==

for one uplink , it will be 15 -2 =13 and also 2 VHBAs , so 13 -2 =11. http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-05%20at%202.28.06%20PM.png
 
12. Associate the Dynamic Vnic policy to Service Profile (SP change will reboot the server)
http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-05%20at%202.30.05%20PM.png
http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-05%20at%202.46.45%20PM.png
 
13.Install ESX server 4.0

14. Enable ssh root access on ESX server and install VEM.

Tricky part to find right vem, and also use vumupdate.


http://172.25.182.88/http://zed.cisco.com/confluence/images/icons/linkext7.gif has the list of VEM and appropriate "vmware -v" version. http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-05%20at%202.37.19%20PM.png
 

15.

[root@localhost ~]# vmware -v
VMware ESX 4.0.0 build-208167
[root@localhost ~]# esxupdate -b cross_cisco-vem-v110-4.0.4.1.2.0.80-1.9.179-release.vib update --nosigcheck
cross_cisco-vem-v110-4.0.4.1... ######################################## [100%]

Unpacking cross_cisco-vem-v11.. ######################################## [100%]

Installing cisco-vem-v110-esx   ######################################## [100%]

Running [/usr/sbin/vmkmod-install.sh]...
ok.

 [root@localhost ~]# vmkload_mod -l |grep vem
vem-v110-svs-mux    0x4180320b1000    0x8000      0x417ff2e116c0    0x1000        56 Yes    
vem-v110-pts        0x4180320b9000    0xd000      0x417ff2e12ee0    0x1000        57 Yes   

16. Register the ESX host in Vcenter under specific DATACENTER/CLuster as per the requirement. http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-06%20at%2012.34.44%20PM.png
 
Add License:Enterprise License is required.--- Assign an enterprise license key....

 

17. Add STratic Vnics to VEM http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-06%20at%2012.37.45%20PM.png
 

19.

This adds the host to DVS and makes Service console /Network Adapters part of DVS
 

 


Palo_PTS3

17. Add STratic Vnics to VEM http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-06%20at%2012.37.45%20PM.png
 

19.

This adds the host to DVS and makes Service console /Network Adapters part of DVS
http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-06%20at%2012.39.11%20PM.pnghttp://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-06%20at%2012.41.47%20PM.png
 
http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-06%20at%2012.44.05%20PM.png
 
 http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-06%20at%2012.44.43%20PM.png
 
 
http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-06%20at%2012.45.40%20PM.png
 
 
now it moves to DVS from Vswitch on Networking for that host
 
http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-06%20at%2012.47.14%20PM.png
 
On UCSM, you can ESX server added to VSWITCH (DVS) and has a ServiceConsole  VNIC
 
http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-06%20at%2012.50.49%20PM.png
 
20. Add a VM ....
 http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-06%20at%2012.52.00%20PM.png
 
adding second nic to internal Net (143 VLAN) to the same VM.
http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-06%20at%2012.53.07%20PM.png
 
 Power on VM
 
and on UCSM , you will see vnics (one vlan 182 and other vlan 143) created and online for RHEL Virtual Machine

 
http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-06%20at%2012.56.02%20PM.png
 
http://zed.cisco.com/confluence/download/attachments/380808801/Screen%20shot%202010-05-06%20at%2012.57.19%20PM.png
 
 
Install OS on the RHEL Virtual Machine from Virtual Center, you will see two NICs on the RHEL Guest OS.
 

nxos-b:(show int br)
veth993       143    eth  trunk  up      none                        10G(D) --
UCS1-FI-A(nxos)# show int br | inc 994
veth994       143    eth  trunk  up      none                        10G(D) --

UCS1-FI-B(nxos)# show int br | inc 996
veth996       182    eth  trunk  up      none                        10G(D) --

---------

 Unconfiguring:

1. Shutdown the Virtual machine - remove the both network interfaces that use the DVS port profile

2. In Networking of ESX server ->Go  to DVS ->Manage phy. adapter

3. Remove one of the adapters  and add that interface to vswitch with service console.

4. Go to DVS (manage virtual adapters) - virtual interface and remove vswif0 or migrate to Virtual switch.

5. Remove the other adapter from DVS. (physical)

6. Now DVS has no phy adapter or Service console configured.

7. Inventory -->Networking and remove the ESX from the DVS
 

8. Disable DVS PTS_vswitch

 9. Go to UCSM, remove port profiles from Profile Client ( it might take time to disab;e)

DATA_PROFILE_182 used by some virtual machines :ERROR:
 

From Vsphere Clinet -- some active objects are there.

10. Service profile -remove dynamic vnic config

and this will reboot the server.

11. Now Data_Profile PC can be deleted.

12. Delete the Data Center from UCSM and also VC

13. Delete the Virtual Center from VM tab in UCSM.

14. delete port profiles if u want.

 


Monday, March 1, 2010

uplink_no_policy

 

Setting up NIC Policies: if uplink is down, veths can still be up based on the policy

But failover won’t work.

Available from 1.0.2d

 

 

 

 

 

 

Set this to all the service profile which u don’t want failover to work , but want the link to stay up when uplink fails.

 

 

Test

 

Linux Suse on Server 5 – eth0 – which corresponds vnic1 on Fabric B.

Redhat 5.4 on Server 3 eth0 – which corresponds to vnic1 on Fabric

 

 

 

 

 

 

 

 

Able ping router via uplink and ping the redhat linux (6120 switches within)

 

Let us bringdown the uplink

 

Able to ping the linux but not the router.

 

 

 

(I shutdown both uplinks still able to ping between the servers)

 

 

Config change

 

 

UCS1-FI-B(nxos)# show run int veth767

version 4.0(1a)N2(1.2e)

 

interface vethernet767

  no cdp enable

  switchport trunk allowed vlan 1,143,153,163

  bind interface Ethernet1/1/4

  no pinning server sticky

  pinning server pinning-failure link-down

 

UCS1-FI-B(nxos)# show run int veth788

version 4.0(1a)N2(1.2e)

 

interface vethernet788

  no cdp enable

  switchport trunk allowed vlan 1,143,153,163

  bind interface Ethernet1/1/5

  no pinning server sticky  <<<<<<<<<<<<<<<<<<<<<<<

 

UCS1-FI-B(nxos)# show int br | inc veth

veth767       1      eth  trunk  down    inactive                    10G(S) --  <<<no change of policy

veth775       1      eth  trunk  up      none                        10G(S) – esc-no-uplink – veth stays up

veth788       1      eth  trunk  up      none                        10G(S) --

veth790       1      eth  trunk  up      none                        10G(S) --


Friday, February 19, 2010

upgrade

  1. tftp does not work
  2. if u try tftp and then scp , then both will not work

Bugs:

Image download via TFTP fails.

FW Management.

 

Use SCP or FTP.

Download stuck in downloading if a download failed previously

 

FW Management.

 

Use SCP or FTP. Do not use TFTP to download image.

To recover:

1. Delete the Download task from UI.

2. Force HA failover. Restart problematic Fabric Interconnect.

 

 

UCS1-FI-A /firmware # download image scp://jejoseph@171.68.227.115/SAN/UCS/Cases/ucs-k9-bundle.1.0.2e.bin

 

UCS1-FI-A /firmware # show download-task fsm status

 

File Name: ucs-k9-bundle.1.0.2e.bin

 

    FSM 1:

        Remote Result: Not Applicable

        Remote Error Code: None

        Remote Error Description:

        Status: Download Local

        Previous Status: Download Local

        Timestamp: 2009-11-06T19:16:10

        Try: 1

        Progress (%): 2

        Current Task: downloading image ucs-k9-bundle.1.0.2e.bin from 171.68.22

.115(FSM-STAGE:sam:dme:FirmwareDownloaderDownload:Local)

 

UCS1-FI-A /firmware # SHOW IMage

Name                                          Type                 Version

    State

--------------------------------------------- -------------------- ------------

--- -----

ucs-2100.1.0.1e.bin                           Iom                  1.0(1e)

    Active

ucs-2100.1.0.2e.bin                           Iom                  1.0(2e)

    Active

……………..

……………….

 

 

Update Firmware

 

 

Activate Firmware:

Filter Interface card – Set Version 1.0.2e – Ignore Compatiblity and Set Startup version

 

Now the screen will look like this after applying

 

BMC:

Click Apply with ignore compatibility check on

Warning: this will reboot

 

 

Wait until it shows ready:

 

IOM (ignore/set startup only)

 

 

 

Wait until it becomes pending –reboot

 

 

UCSM:

 

 

 

 

 

Then close the ucsm gui.

 

Refresh http:// on the browser

Verify:1.0.2e

 

After login – Firmware management

 

 

 

 

 

Then it reboots – wait for sometime ( 5-6 minutes)

 

Upgrade is done, if u have Bonding or Nic Failover, server should not see disruption.


Wednesday, February 3, 2010

UCS PXE Boot

Pieces Needed to successfully PXE boot on UCS (DHCPd, TFTPd, Installation Media, PXE client):

1: DHCP server: This doc assumes the DHCP server is on same VLAN as the PXE client (else use ip-helper address config)
Option A = IOS dhcp server config:

ip dhcp pool VLAN903
network 172.23.182.0 255.255.255.0
bootfile linux-install/pxelinux.0
next-server 172.23.182.59
dns-server 171.70.168.183
domain-name cisco.com
default-router 172.23.182.1

service dhcp

Option B = RHEL (or other linux) dhcpd config:

[root@localhost etc]# more dhcpd.conf
#
# DHCP Server Configuration file.
# see /usr/share/doc/dhcp*/dhcpd.conf.sample
#
ddns-update-style interim;
ignore client-updates;

allow booting;
allow bootp;

class "pxeclients" {
match if substring(option vendor-class-identifier, 0, 9) = "PXEClient";
next-server 172.23.182.59;
filename "linux-install/pxelinux.0";
}

subnet 172.23.182.0 netmask 255.255.255.0 {

option routers 172.23.182.1;
option subnet-mask 255.255.255.0;
option domain-name "cisco.com";
option domain-name-servers 171.70.168.183;

range dynamic-bootp 172.23.182.51 172.23.182.250;
default-lease-time 21600;
max-lease-time 43200;
}
[root@localhost etc]#

Troubleshooting DHCP:

1) You might want to test this with a non-PXE DHCP client to make sure that DHCP is indeed working as expected.

2) A successful DHCP negotiation should look something like this (DHCPDISCOVER, DHCPOFFER, DHCPREQUEST, DHCPACK ('debug ip dhcp server packet' from IOS):

Feb 2 06:34:48.536 PDT: DHCPD: DHCPDISCOVER received from client 0025.b500.038a on interface Vlan903.
Feb 2 06:34:48.536 PDT: DHCPD: Sending DHCPOFFER to client 0025.b500.038a (172.23.182.136).
Feb 2 06:34:48.536 PDT: DHCPD: broadcasting BOOTREPLY to client 0025.b500.038a.
Feb 2 06:34:50.568 PDT: DHCPD: DHCPREQUEST received from client 0025.b500.038a.
Feb 2 06:34:50.568 PDT: DHCPD: Sending DHCPACK to client 0025.b500.038a (172.23.182.136).
Feb 2 06:34:50.568 PDT: DHCPD: broadcasting BOOTREPLY to client 0025.b500.038a.

2) Installation Source (http server):
http://172.23.182.59/Linux/

a. mount -o loop

/root/RHEL5.4-Server-20090819.0-x86_64-DVD.iso on /mnt/disk type iso9660 (rw,loop=/dev/loop0)

b.httpd.conf


Options Indexes
AllowOverride None

Alias /Linux /mnt/disk

c. restart httpd.
d.

[root@localhost pxeboot]# pwd
/mnt/disk/images/pxeboot

boot.iso minstg2.img README TRANS.TBL
diskboot.img pxeboot stage2.img xen


3) TFTP server:(RHEL)

http://syslinux.zytor.com/wiki/index.php/PXELINUX (sample)

This could run on the same server as the DHCP (i.e if using Linux) or not, but it should be in the same VLAN as the PXE cleints.

Set up TFTP server: We'll be PXE booting to RHEL so we'll need the RHEL files on the tftp server.

1. Verify if tftp server is installed: rpm -q tftp-server
tftp-server-0.49-2
2. tftp config file : /etc/xinetd.d/tftp

3. chmod 777 /tftpboot

4. sbin/chkconfig --level 345 xinetd on /sbin/chkconfig --level 345 tftp on (set it to boot at startup)

5. [root@localhost tftpboot]# ls -al
total 44
drwxr-xr-x 3 root root 4096 Jan 29 16:47 .
drwxr-xr-x 26 root root 4096 Jan 29 15:28 ..
drwxr-xr-x 4 root root 4096 Feb 1 13:36 linux-install
-rw-r-r- 1 root root 13148 Jan 28 14:33 pxelinux.0

6. [root@localhost tftpboot]# cd linux-install/
[root@localhost linux-install]# ls -al (these files need to be here for the linux kernel boot are copied from /mnt/disk/images/pxeboot)
total 9192
drwxr-xr-x 4 root root 4096 Feb 1 13:36 .
drwxr-xr-x 3 root root 4096 Jan 29 16:47 ..
-r-rr- 1 root root 7399936 Jan 28 14:32 initrd.img
drwxr-xr-x 2 root root 4096 Jan 29 17:02 msgs
-rw-r-r- 1 root root 13100 Dec 19 2005 pxelinux.0
drwxr-xr-x 2 root root 4096 Feb 1 11:22 pxelinux.cfg
-r-rr- 1 root root 1932316 Jan 28 14:32 vmlinuz
[root@localhost linux-install]#

7. [root@localhost linux-install]# cd pxelinux.cfg (location of pxe client config files)
[root@localhost pxelinux.cfg]# ls -al
total 100
drwxr-xr-x 2 root root 4096 Jan 30 22:35 .
drwxr-xr-x 4 root root 4096 Jan 29 16:42 ..
-rw-r-r- 1 root root 0 Jan 28 15:36 01-00-25-B5-00-03-1A (need to 'touch' empty files named as mac-address of clients with 01- prefix)
-rw-r-r- 1 root root 0 Jan 28 15:36 01-00-25-B5-00-03-1B
-rw-r-r- 1 root root 0 Jan 30 19:22 01-00-25-B5-00-03-2A
-rw-r-r- 1 root root 0 Jan 29 16:40 01-00-25-B5-00-18-FE
-rw-r-r- 1 root root 0 Jan 30 22:35 01-00-25-B5-55-03-1A
-rw-r-r- 1 root root 0 Jan 28 14:43 A
-rw-r-r- 1 root root 0 Jan 28 14:43 AC
-rw-r-r- 1 root root 0 Jan 28 14:44 AC1
-rw-r-r- 1 root root 0 Jan 28 14:44 AC17
-rw-r-r- 1 root root 0 Jan 28 14:44 AC17B
-rw-r-r- 1 root root 0 Jan 28 14:44 AC17B6
-rw-r-r- 1 root root 0 Jan 28 14:44 AC17B6F
-rw-r-r- 1 root root 0 Jan 28 14:44 AC17B6FE
-rw-r-r- 1 root root 122 Jan 28 14:36 default <<

4) PXE client:

a couple options with UCS here, LAN boot on bare metal blade/rack server, or a newly built stock ESX client will try to PXE boot

Service Profile should have LAN as first boot option.

Client should boot, get ip address, then tftp kernel and begin install. You'll then need to point to an installation source.

a. Service Profile Config - (vnic configuration - select Native VLAN if the PXE/DHCP servers are not on 6120's default vlan,

we selected native vlan for 182 because our 6120/N5k switches' native vlan was 1 and our DHCP server was in vlan 182)


Boot Order: (selected vnic)




KVM output of the server PXE booting:





Please verify the pinning to confirm the VETH is taking right path northbound.

UCS3-FI-A(nxos)# show run int veth730
version 4.0(1a)N2(1.2j)

interface vethernet730
no cdp enable
switchport trunk native vlan 182
switchport trunk allowed vlan 182
bind interface Ethernet1/1/7
pinning server sticky border-interface Ethernet1/2
pinning server pinning-failure link-down

UCS3-FI-A(nxos)# show pinning server-interfaces (Portchannel 30 is our Test lab network, which does not access to vlan 182, so the server was failing to PXE boot (veth 731 is veth of server1/8 and we have to use manual pin group))

------------------------------------+-------------
SIF Interface Sticky Pinned Border Interface Pinned Duration
------------------------------------+-------------
veth730 Yes(hard-pinned) Eth1/2 0:27:17
veth731 No Po30 0:12:35
veth732 No Po30 0:5:54
veth733 No Eth1/2 0:4:16
Eth1/20 Yes - -
Eth1/1/1 Yes - -
Eth1/1/2 Yes - -
Eth1/1/3 Yes - -
Eth1/1/4 Yes - -
Eth1/1/5 Yes - -
Eth1/1/6 Yes - -
Eth1/1/7 Yes - -
Eth1/1/8 Yes - -
Eth1/1/9 Yes - -

Total Interfaces : 14

Comments (Hide Comments)

After we pinned the interfaces,
UCS3-FI-A(nxos)# show pinning server-interfaces

---------------------------------------------------+----------------
SIF Interface Sticky Pinned Border Interface Pinned Duration
---------------------------------------------------+----------------
veth736 Yes(hard-pinned) Eth1/2 0:22:27
veth737 Yes(hard-pinned) Eth1/2 0:20:11
veth738 Yes(hard-pinned) Eth1/2 0:17:56
veth739 Yes(hard-pinned) Eth1/2 0:19:16
Eth1/20 Yes - -
Eth1/1/1 Yes - -
Eth1/1/2 Yes - -
Eth1/1/3 Yes - -
Eth1/1/4 Yes - -
Eth1/1/5 Yes - -
Eth1/1/6 Yes - -
Eth1/1/7 Yes - -
Eth1/1/8 Yes - -

UCS3-FI-A(nxos)# show run int eth 1/2
version 4.0(1a)N2(1.1e)

interface Ethernet1/2
switchport mode trunk
switchport trunk allowed vlan 1,55-56,182,998
pinning border
no shutdown

interface vethernet736
switchport trunk native vlan 182
switchport trunk allowed vlan 182
bind interface Ethernet1/1/2
pinning server sticky border-interface Ethernet1/2
pinning server pinning-failure link-down

---------------------
enter service-profile pxe-server7 instance
associate server 1/7
enter boot-definition
enter lan
enter path primary
set vnic vnic1
exit
set order 1
exit
set descr ""
set reboot-on-update no
exit

enter vnic vnic1
enter eth-if vlan182
set default-net yes
exit
set adaptor-profile ""
set identity dynamic-mac 00:25:B5:00:03:7A
set identity mac-pool ""
set order 1
set pin-group vlan1
set qos-policy ""
set stats-policy default
set template-name ""
exit
power up
set boot-policy ""
set descr ""
set dynamic-vnic-conn-policy ""
set host-fw-policy 2j-2027
set identity dynamic-uuid derived
set identity uuid-suffix-pool ""
set identity wwnn-pool node-default
set ipmi-access-profile ""
set local-disk-policy default
set mgmt-fw-policy ""
set scrub-policy ""
set sol-policy default
set src-templ-name ""
set stats-policy default
exit

Followers