Manage Workgroup Computers with WSUS Server

2021/09/11 / Fred / Leave a comment

Still current

I was recently required to manage a number of clients in a workgroup with the WSUS server within my domain. In order to so, this is as simple as modifying the clients registry settings to replicate those of the clients within your domain, so basically you will be required to create/import the following registry key, HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsWindowsUpdate:

"TargetGroupEnabled"=dword:00000001 
"TargetGroup"="Managed Workgroup" 
"ElevateNonAdmins"=dword:00000000 
"WUServer"="http://wsus1.domain.com"
"WUStatusServer"="http://wsus1.domain.com"

The above registry settings will configure your WSUS client to use a managed computer group on your WSUS Server with the name ‘Managed Workgroup’, where only the administrator can install updates and the Windows Update and Status Server is configured to be WSUS1.domain.com.

The additional automatic update options of the workgroup client can be created/imported to the following registry key, HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsWindowsUpdateAU:

"NoAutoUpdate"=dword:00000000 
"AUOptions"=dword:00000003
"ScheduledInstallDay"=dword:00000000
"ScheduledInstallTime"=dword:00000011
"UseWUServer"=dword:00000001

These settings will enable automatic updates to automatically download and notify for install (I choose to install my approved updates on demand using…

View original post 23 more words

Using Netbackup ?

2021/08/252021/08/25 / Fred / Leave a comment

To be able to get a “quick” view of Veritas Netbackup status graphically, it is not a usual trick but a tool I have build this time !

If you use already grafana and prometheus, you can build and use this golang exporter from my github,

Feel free to like it and / or comment it

Wildfly & Elastic

2021/08/25 / Fred / Leave a comment

A simple way to get wildfly events into Elastic it to use the syslog handler. (warning if elastic is somehow not listening, no event are catches)

On wildfly side

Stop wildfly and modify logging.properties file to add a new handler (can also be done in UI):

handler.ELF=org.jboss.logmanager.handlers.SyslogHandler
handler.ELF.level=DEBUG
handler.ELF.formatter=PATTERN
handler.ELF.properties=enabled,facility,port,serverHostname,syslogType
handler.ELF.enabled=true
handler.ELF.facility=SYSTEM_DAEMONS
handler.ELF.port=1515
handler.ELF.serverHostname="elastic server"
handler.ELF.syslogType=RFC5424

And add the handler to the active logger list

logger.handlers=CONSOLE,DEFAULT,ELF

We need to ensure our logging pattern is still the default

formatter.PATTERN=org.jboss.logmanager.formatters.PatternFormatter
formatter.PATTERN.properties=pattern
formatter.PATTERN.pattern=%d{yyyy-MM-dd HH\:mm\:ss,SSS} %-5p [%c] (%t) %s%e%n

On logstash side

Create a new port dedicated to wildfly logs (it has to be the same port as in wildfly logger). It is a logstash input

input {
  udp {
    port => 1515
    type => wildfly
  }
}

Then do the magic

filter {
  if [type] == "wildfly"  {
      grok {
        break_on_match => true
        match => [
          "message", "<%{NONNEGINT:syslog5424_pri}>%{NONNEGINT:syslog5424_ver} +(?:%{TIMESTAMP_ISO8601:syslog5424_ts}|-) +(?:%{HOSTNAME:syslog5424_host}|-) +(?:%{WORD:syslog5424_app}|-) +(?:%{WORD:syslog5424_proc}|-) +(?:%{JAVACLASS:package}|-) - %{NOTSPACE}%{YEAR:y2}[-]%{MONTHNUM:m2}[-]%{MONTHDAY:d2} (?!<[0-9])%{HOUR:h2}:%{MINUTE:M2}(?::%{SECOND:s2})(?![0-9]) %{LOGLEVEL:level} \[%{JAVACLASS:class}\] \(%{DATA:thread}\) %{GREEDYDATA:msgdata}"
          
        ]
      }
    syslog_pri { }
  }

}

In kibana you can get the most valuable data in msgdata. All other meta data are available too

Consuming hashicorp vault values in bash

2021/08/242021/08/24 / Fred / Leave a comment

Vault is “only” the same cli tool in client or server mode.

Covering the server mode can be discussed later but the client is really opening doors. A shell example :

My VAULT_TOKEN is in an environment variable. I can use it to login. Normally I do no use the tls verification

RESULT=$(vault login -no-print -tls-skip-verify token=$VAULT_TOKEN )
export RESULT

Then I can use it to query values from vault. jq to the rescue to get the value

VMWARE_SERVER=$(vault kv get -tls-skip-verify --format=json kv/infra/prod/vmware/vsi | jq ".data[\"data\"][\"hostname\"]")

VMWARE_USERNAME=$(vault kv get -tls-skip-verify --format=json kv/infra/prod/vmware/vsi/user | jq ".data[\"data\"][\"username\"]")

VMWARE_PASSWORD=$(vault kv get -tls-skip-verify --format=json kv/infra/prod/vmware/vsi/user | jq ".data[\"data\"][\"password\"]")

export VMWARE_SERVER VMWARE_USERNAME VMWARE_PASSWORD

Et voila !

Using vCenter tags with ansible

2021/08/242021/08/24 / Fred / Leave a comment

Goal

To configure an ansible inventory to consume vm tags, you can use such a configuration. Create a file like myLnxToPatch-vmware.yml (it has to finish as -vmware.yml) and use for example

---
plugin: community.vmware.vmware_vm_inventory
strict: false
validate_certs: false
with_nested_properties: false
with_path: false
with_tags: true
filters:
  - ( config.guestId == "rhel6_64Guest" or config.guestId == "rhel7_64Guest" or config.guestId == "rhel8_64Guest" ) and ( summary.customValue is defined ) and ('Update' in tag_category.Action) and ( runtime.powerState == "poweredOn" )
hostnames:
  - config.name
properties:
  - "config.name"
  - "config.guestFullName"
  - "config.guestId"
  - "guest.ipAddress"
  - "summary.customValue"
  - "summary.config.uuid"
  - "summary.runtime.powerState"
keyed_groups:
  - key: summary.customValue
    separator: ""

The specific to be noted are :

if you want to use custom attributes, you need to check if they are defined
the tag are values in the tag category

Caching can be used as vCenter can be very slow

Environment variables

You need to specify in your environment the following variables:

VMWARE_SERVER
VMWARE_USERNAME
VMWARE_PASSWORD

Powertool to mass deploy some UCS

2015/05/07 / Fred / Leave a comment

When you need to create 2 UCS domain the same way, Cisco PowerTool is a wonderfull assistance

We set our Domain number

$dc="02"

We “store” the DC number in all pool of wwn and other UCS id

$wwnn_pool = Add-UcsWwnPool -Name "DC$($dc)-WWNN" -Purpose node-wwn-assignment -Org $org 
$wwnn_pool | Add-UcsWwnMemberBlock -From 20:00:DC:$($dc):B5:00:00:00 -To 20:00:DC:$($dc):B5:00:00:FF 

$wwpn_pool = Add-UcsWwnPool -Name "DC$($dc)-WWPN-A1" -Purpose port-wwn-assignment -Org $org
$wwpn_pool | Add-UcsWwnMemberBlock -From 20:00:DC:$($dc):B5:00:A1:00 -To 20:00:DC:$($dc):B5:00:A1:FF

$wwpn_pool = Add-UcsWwnPool -Name "DC$($dc)-WWPN-B1" -Purpose port-wwn-assignment  -Org $org
$wwpn_pool | Add-UcsWwnMemberBlock -From 20:00:DC:$($dc):B5:00:B1:00 -To 20:00:DC:$($dc):B5:00:B1:FF


$uuid_pool = Add-UcsUuidSuffixPool -Name "DC$($dc)-UUID" -Org $org 
$uuid_pool | Add-UcsUuidSuffixBlock -From "DC$($dc)-000000000001" -To "DC$($dc)-0000000003E7"

We will “clone” our template per vCenter cluster for easier evolution

$clusters=("CTX","RDM")
foreach ($cluster in $clusters) {
    $lsp = Get-UcsServiceProfile -Name "DC$($dc)-esx-2nic-2hba-NOUSE" -Org $org
    $tpl= copy-UcsServiceProfile -ServiceProfile $lsp   -DestinationOrg $org -NewName "SPT-$($cluster)-template" 
    $pool = Get-UcsServerPool -Name $cluster -Org $org
    Associate-UcsServiceProfile -ServerPoolName $pool.name -ServiceProfile $tpl -Force 
}

We create server pool to match vCenter clusters

$server_pool = Add-UcsServerPool -Name "RDM" -Org $org
$server_pool | Add-UcsComputePooledSlot -ChassisId 1 -SlotId 1
$server_pool | Add-UcsComputePooledSlot -ChassisId 2 -SlotId 1

$server_pool = Add-UcsServerPool -Name "CTX" -Org $org
$server_pool | Add-UcsComputePooledSlot -ChassisId 1 -SlotId 2
$server_pool | Add-UcsComputePooledSlot -ChassisId 5 -SlotId 2

We create servers (service profiles from our templates)

Add-UcsServiceProfile  -Org $org -SrcTemplName SPT-RDM-template -Name dc$($dc)-esxi-01
Add-UcsServiceProfile  -Org $org -SrcTemplName SPT-RDM-template -Name dc$($dc)-esxi-02
...
Add-UcsServiceProfile  -Org $org -SrcTemplName SPT-CTX-template -Name dc$($dc)-esxi-13 
...

Nb Template name is “published” during PXE boot by UCS, very useful for autodeply

$pattern='oemstring=$SPT:SPT-SHP-template'

I may do a complete autodeploy article later …

PowerCLI from ESXi mass modifications

2015/05/072015/05/07 / Fred / Leave a comment

Most of the time, I use vCenter (Web) Client for day to day operation, for a massive deployment, I have played a bit with PowerCLI. As it is a complete framework, some gems that really helped me.

You should already be logged in vCenter

Set ESXi powermanagement on “Maximum performance”

$hostname="fqdn"
$view = (Get-VMHost $hostname| Get-View)
(Get-View $view.ConfigManager.PowerSystem).ConfigurePowerPolicy(1)

Configure multiple IP addresses from DHCP to Fixed IP

You need a CSV file with

srvname,ipmgmt,ipvmotion

as header inside the file

$servers = "$($ScriptPath)servers.txt"
$FileInitExists = Test-Path $servers

if ($FileInitExists -eq $false){
    "servers.txt does not exist. Create it and place the aliases, one per line"
    exit
}
$file = Import-Csv $servers
foreach ($row in $file){
    $name="$($row.srvname).esx.mercuria.met"
    write-host "$name $($row.ipmgmt) $($row.ipvmotion)"
    $srv=get-vmhost -Name $name
    Get-VMHost $srv| Get-VMHostNetworkAdapter -VMKernel -Name vmk0 |Set-VMHostNetworkAdapter  -IP $($row.ipmgmt) -SubnetMask 255.255.255.0 -Confirm:$false
    Get-VMHost $srv| Get-VMHostNetworkAdapter -VMKernel -Name vmk1 |Set-VMHostNetworkAdapter  -IP $($row.ipvmotion) -SubnetMask 255.255.255.0 -Confirm:$false
}

NB default gateway is another set of commands, normally the same value as DHCP

Configure all LUN for a disk array to round robin multipath

$srv=get-vmhost -Name $name
Get-ScsiLun -CanonicalName "naa.60030d90*" -VmHost $srv| Set-ScsiLun -MultipathPolicy "roundrobin"

Bypass Powerpath for Hitachi disk array

$srv=get-vmhost -Name $name
$cli=Get-EsxCli -vmhost $srv
$cli.storage.core.claimrule.remove($null,$null,"280")
$cli.storage.core.claimrule.add($null,$null,$null,$null,$null,$null,$null,$null,$null,$null,"*","NMP",201,$null,$null,"vendor","HITACHI",$null,$null)

Rescan all HBAs

$srv=get-vmhost -Name $name
Get-VMHostStorage -VmHost $srv-RescanAllHba

Useful in a foreach loop 😉

Disable all VAAI

$srv=get-vmhost -Name "fqdn"
Set-VMHostAdvancedConfiguration -VMHost $srv -Name DataMover.HardwareAcceleratedMove -Value 0
Set-VMHostAdvancedConfiguration -VMHost $srv -Name DataMover.HardwareAcceleratedInit -Value 0
Set-VMHostAdvancedConfiguration -VMHost $srv -Name VMFS3.HardwareAcceleratedLocking -Value 0

Set 1 to re-enable

Set host in maintenance mode

Set-VMHost -VMHost $srv -state Maintenance -RunAsync -Confirm:$false

To exit :

Set-VMHost -VMHost $srv -state Connected -RunAsync -Confirm:$false

Working with annotations

$myvalue=get-vm $vm | Get-Annotation -CustomAttribute "my-annotation"

Reboot an ESX

Remember that maintenance mode is normally a best practive

 Restart-VMHost $srv -RunAsync -force  -Confirm:$false

Disable IPv6 in vSphere 5.5

 $cli = Get-EsxCli -vmhost $srv
 $cli.network.ip.set($false)

Attach a host profile

Set-VMHost -VMHost $ucs -profile "UCS-RDM-55"

Upgrading UCS FI … an “easy” job

2015/03/03 / Fred / Leave a comment

if you need to upgrade a cisco UCS “brain”, the procedure exist publically available at cisco but I post here a bit more details after a first experience …

Step 1

Mount the replacement fabric interconnects into either the same rack or an adjacent rack.

Refer to the Cisco UCS 6200 Series Installation Guide for details.

Step 2

Using either the Cisco UCS Manager CLI or GUI, verify the state (subordinate or active) of the fabric interconnects.

See http://www.cisco.com/en/us/docs/unified_computing/ucs/sw/upgrading/from1.4/to2.0/b_upgradingciscoucsfrom1.4to2.0_chapter_0101.html.

Step 3

Back up the software configuration information and the Cisco UCS Manager software.

Step 4

Disable the server ports on the subordinate fabric interconnect.

Step 5

Power down the subordinate fabric interconnect by unplugging it from the power source.

If you are monitoring the upgrade using a KVM session, you may need to reconnect the KVM session when you power down the fabric interconnect.

Step 6

Disconnect the cables from the chassis FEXes or fabric extenders to the subordinate fabric interconnect ports in slot 1 on the old fabric interconnect.

Step 7

Connect these cables into the corresponding ports on slot 1 of one of the new Cisco UCS 6248 UP fabric interconnects, using the connection records to preserve the port mapping and the configured server pinning.

Step 8

Disconnect the L1/L2, M1 management, and console cables on the old fabric interconnect.

The ports for these connections are on the opposite side of the interconnect, so if your cables are just barely long enough to connect two rack-adjacent Cisco UCS 6120 interconnects you will probably need new cables.

Step 9

Connect the M1 management, and console cables to the new Cisco UCS 6248 UP.

Step 10

Connect the L1/L2 cables that were disconnected onto the new Cisco UCS 6248 UP :

L1 connects to L1
L2 connects to L2.

Step 11

Disconnect the Ethernet or FC cables from slot 2 of the old fabric interconnect.

Step 12

Connect the Ethernet or FC cables to the corresponding ports in slot 2 of the new Cisco UCS 6248 UP.

Some may go to slot 1, depending on the mappings planned out earlier in the process.

Step 13

Connect the power to the new Cisco UCS 6248 UP, it will automatically boot and run POST tests. If it reboots itself, this is a normal behavior.

IMPORTANT:

Directly connect the console port to a terminal and observe the boot sequence. You should at some point see the Basic System Configuration Dialog, where you will configure the switch as a subordinate interconnect. If you do not see this dialog, you either have different builds of software on your old primary and new subordinate, or the new subordinate has previously been part of a cluster and will need to have all configuration information wiped before it can be added to a cluster as a subordinate. In either case, immediately disconnect the L1 and L2 connections and complete the process bring up as a standalone fabric interconnect, then correct the issue before proceeding further.

We power on the FI after the first cables swap, Server ports are disabled

N5000 BIOS v.3.6.0, Wed 05/09/2012, 03:15 PM

[2J[1;1H[25;78H98[1;1H[25;78H9C[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78H99[1;1H[25;78H99[1;1H[25;78H99[1;1H[25;78H92[1;1H[25;78H99[1;1H[25;78HA0[1;1H[25;78HA2[1;1H[25;78HA3[1;1H[25;78HA0[1;1H[25;78HA2[1;1H[25;78HA3[1;1H[25;78HB2[1;1H[2J[1;1H                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      B2[1;1H[0;37;40m[2J[1;37;40m[1;1HVersion 2.00.1201. Copyright (C) 2009 American Megatrends, Inc.                 [2J[2JBooting kickstart image: bootflash:/installables/switch/ucs-6100-k9-kickstart.5

.2.3.N2.2.23c.bin....

...............................................................................

..............................................Image verification OK

 

ÿUsage: init 0123456SsQqAaBbCcUu

INIT: [   10.665234] I2C - Mezz absent

Starting system POST.....

Executing Mod 1 1 SEEPROM Test:...done (0 seconds)

Executing Mod 1 1 GigE Port Test:....done (32 seconds)

Executing Mod 1 1 PCIE Test:.................done (0 seconds)

Mod 1 1 Post Completed Successfully

POST is completed

can't create lock file /var/lock/mtab~207: No such file or directory (use -n flag to override)

S10mount-ramfs.supnuovaca Mounting /isan 3000m

Mounted /isan

Creating /callhome..

Mounting /callhome..

Creating /callhome done.

Callhome spool file system init done.

nohup: redirecting stderr to stdout

autoneg unmodified, ignoring

autoneg unmodified, ignoring

Checking all filesystems....r. done.

Checking NVRAM block device ... done

The startup-config won't be used until the next reboot.

.

Loading system software

Uncompressing system image: bootflash:/installables/switch/ucs-6100-k9-system.5.2.3.N2.2.23c.bin

 

Loading plugin 0: core_plugin...

Loading plugin 1: eth_plugin...

Loading plugin 2: fc_plugin...

 

C

10+1 records in

10+1 records out

8538 bytes (8.5 kB) copied, 4.3137e-05 s, 198 MB/s

ethernet end-host mode on CA

FC end-host mode on CA

n_port virtualizer mode.

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

INIT: Entering runlevel: 3

touch: cannot touch `/var/lock/s

/isan/bin/muxif_config: fex vlan id: -f,4042

Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config

Added VLAN with VID == 4042 to IF -:muxif:-

cp: cannot stat `/isan/plugin_img/fex.bin': No such file or directory

 

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

enabled fc feature

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

2015 Mar 1 09:21:56 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files begin - clis

2015 Mar 1 09:22:00 %$ VDC-1 %$ Mar 1 09:21:59 %KERN-0-SYSTEM_MSG: [   10.665234] I2C - Mezz absent - kernel

2015 Mar 1 09:22:06 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files end - clis

2015 Mar 1 09:22:06 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: init begin - clis

System is coming up ... Please wait ...

System is coming up ... Please wait ...

System is coming up ... Please wait ...

System is coming up ... Please wait ...

System is coming up ... Please wait ...

System is coming up ... Please wait ...

2015 Mar 1 09:23:09 %$ VDC-1 %$ %VDC_MGR-2-VDC_ONLINE: vdc 1 has come online

System is coming up ... Please wait ...

nohup: appending output to `nohup.out'

2015 Mar 1 09:23:24 switch %$ VDC-1 %$ %USER-2-SYSTEM_MSG: Running in PIO stats mode - carmelusd

We try to join the fabric – but …

---- Basic System Configuration Dialog ----

 

This setup utility will guide you through the basic configuration of

the system. Only minimal configuration including IP connectivity to

the Fabric interconnect and its clustering mode is performed through these steps.

 

Type Ctrl-C at any time to abort configuration and reboot system.

To back track or make modifications to already entered values,

complete input till end of section and answer no when prompted

to apply configuration.

 

Enter the configuration method. (console/gui) ? console

 

Installer has detected the presence of a peer Fabric interconnect. This Fabric interconnect will be added to the cluster. Continue (y/n) ? y

 

Enter the admin password of the peer Fabric interconnect:

Connecting to peer Fabric interconnect... done

Retrieving config from peer Fabric interconnect... done

 Peer Fabric Interconnect Model is 6100 and different from Local Fabric Interconnect Model 6248 . Cannot trigger the firmware Synchronization

 

Do you wish to setup this fabric in standalone mode? [hint: Please Remove the cable before selecting 'y'] (y/n): n

Cannot proceed with peer that has a different Image Version. Restarting installer.

We configure the FI as standalone to put same firmware

Enter the configuration method. (console/gui) [console] ? console

Enter the setup mode; setup newly or restore from backup. (setup/restore) ? setup

 

You have chosen to setup a new Fabric interconnect. Continue? (y/n): y

 

Enforce strong password? (y/n) [y]: n

 

Enter the password for "admin":

Confirm the password for "admin":

 

Is this Fabric interconnect part of a cluster(select 'no' for standalone)? (yes/no) [n]: n

 

Enter a system name : dc03-ucs

 

Physical Switch Mgmt0 IP address : 10.41.5.71

 

Physical Switch Mgmt0 IPv4 netmask : 255.255.255.0

 

IPv4 address of the default gateway : 10.41.5.1

 

Configure the DNS Server IP address? (yes/no) [n]: n

 

Configure the default domain name? (yes/no) [n]: n

 

Join centralized management environment (UCS Central)? (yes/no) [n]: n

 

Following configurations will be applied:

 

Switch Fabric=A

System Name=dc03-ucs

Enforced Strong Password=no

Physical Switch Mgmt0 IP Address=10.41.5.71

Physical Switch Mgmt0 IP Netmask=255.255.255.0

Default Gateway=10.41.5.1

Ipv6 value=0

 

Apply and save the configuration (select 'no' if you want to re-enter)? (yes/no): yes

Applying configuration. Please wait.

 

Configuration file - Ok

 

 

Cisco UCS 6200 Series Fabric Interconnect

We upgrade the bundle using the web interface

Use the infrastructure workflow, it takes a while … (30 min )

We reboot with correct firmware

Cisco UCS 6200 Series Fabric Interconnect

dc03-ucs-A login: [ 1628.406302] Shutdown Ports..

[ 1628.440678] writing reset reason 9,

INIT:

INIT: Sending processes the TERM signal

Sending all processes the TERM signal...

Sending all processes the KILL signal...

Saving random seed:

Syncing hardware clock to system time WARNING from hwclock: The clock was in 11 minute mode, which normally means that something else, possibly an NTP daemon, has been setting the hardware clock. Setting the clock with hwclock turns off 11 minute mode. See hwclock documentation.

 

Unmounting file systems: umount2: Device or resource busy

umount: /var/tmp: device is busy

umount2: Device or resource busy

umount: /var/tmp: device is busy

 

/var/tmp:           c

Unmounting file systems (retry): umount2: Device or resource busy

umount: /var/tmp: device is busy

umount2: Device or resource busy

umount: /var/tmp: device is busy

 

/var/tmp:           c

Unmounting file systems (retry): umount2: Device or resource busy

umount: /var/tmp: device is busy

umount2: Device or resource busy

umount: /var/tmp: device is busy

 

/var/tmp:           c

umount2: Device or resource busy

umount: /var/tmp: device is busy

umount2: Device or resource busy

umount: /var/tmp: device is busy

mount: you must specify the filesystem type

mount: /var not mounted already, or bad option

Please stand by while rebooting the system...

[ 1659.685775] Resetting board

 

N5000 BIOS v.3.6.0, Wed 05/09/2012, 03:15 PM

[2J[1;1H[25;78H98[1;1H[25;78H9C[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78H99[1;1H[25;78H99[1;1H[25;78H99[1;1H[25;78H92[1;1H[25;78H99[1;1H[25;78HA0[1;1H[25;78HA2[1;1H[25;78HA3[1;1H[25;78HA0[1;1H[25;78HA2[1;1H[25;78HA3[1;1H[25;78HB2[1;1H[2J[1;1H                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     B2[1;1H[0;37;40m[2J[1;37;40m[1;1HVersion 2.00.1201. Copyright (C) 2009 American Megatrends, Inc.                 [2J[2JBooting kickstart image: bootflash:/installables/switch/ucs-6100-k9-kickstart.5

.2.3.N2.2.23d.bin....

...............................................................................

..............................................Image verification OK

 

ÿUsage: init 0123456SsQqAaBbCcUu

INIT: [   10.688287] I2C - Mezz absent

Starting system POST.....

Executing Mod 1 1 SEEPROM Test:...done (0 seconds)

Executing Mod 1 1 GigE Port Test:....done (32 seconds)

Executing Mod 1 1 PCIE Test:.................done (0 seconds)

Mod 1 1 Post Completed Successfully

POST is completed

can't create lock file /var/lock/mtab~207: No such file or directory (use -n flag to override)

S10mount-ramfs.supnuovaca Mounting /isan 3000m

Mounted /isan

Creating /callhome..

Mounting /callhome..

Creating /callhome done.

Callhome spool file system init done.

nohup: redirecting stderr to stdout

autoneg unmodified, ignoring

autoneg unmodified, ignoring

Checking all filesystems..... done.

Checking NVRAM block device ... done

The startup-config won't be used until the next reboot.

.

Loading system software

Uncompressing system image: bootflash:/installables/switch/ucs-6100-k9-system.5.2.3.N2.2.23d.bin

 

Loading plugin 0: core_plugin...

Loading plugin 1: eth_plugin...

Loading plugin 2: fc_plugin...

 

C

10+1 records in

10+1 records out

8538 bytes (8.5 kB) copied, 5.0374e-05 s, 169 MB/s

ethernet end-host mode on CA

FC end-host mode on CA

n_port virtualizer mode.

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

INIT: Entering runlevel: 3

touch: cannot touch `/var/lock/subsys/n

/isan/bin/muxif_config: fex vlan id: -f,4042

Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config

Added VLAN with VID == 4042 to IF -:muxif:-

cp: cannot stat `/isan/plugin_img/fex.bin': No such file or directory

 

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

enabled fc feature

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

2015 Mar 1 09:50:20 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files begin - clis

2015 Mar 1 09:50:23 %$ VDC-1 %$ Mar 1 09:50:23 %KERN-0-SYSTEM_MSG: [   10.688287] I2C - Mezz absent - kernel

2015 Mar 1 09:50:30 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files end - clis

2015 Mar 1 09:50:30 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: init begin - clis

System is coming up ... Please wait ...

System is coming up ... Please wait ...

System is coming up ... Please wait ...

System is coming up ... Please wait ...

System is coming up ... Please wait ...

System is coming up ... Please wait ...

2015 Mar 1 09:51:41 %$ VDC-1 %$ %VDC_MGR-2-VDC_ONLINE: vdc 1 has come online

System is coming up ... Please wait ...

 

2015 Mar 1 09:51:52 dc03-ucs-A %$ VDC-1 %$ %USER-2-SYSTEM_MSG: Running in PIO stats mode - carmelusd

We reset the configuration to factory to permit synchronisation

Cisco UCS 6200 Series Fabric Interconnect

dc03-ucs-A login: admin

Password:

Cisco Nexus Operating System (NX-OS) Software

TAC support: http://www.cisco.com/tac

Copyright (c) 2009, Cisco Systems, Inc. All rights reserved.

The copyrights to certain works contained in this software are

owned by other third parties and used and distributed under

license. Certain components of this software are licensed under

the GNU General Public License (GPL) version 2.0 or the GNU

Lesser General Public License (LGPL) Version 2.1. A copy of each

such license is available at

http://www.opensource.org/licenses/gpl-2.0.php and

http://www.opensource.org/licenses/lgpl-2.1.php

 

[Kdc03-ucs-A# connect local-mgmt

Cisco Nexus Operating System (NX-OS) Software

TAC support: http://www.cisco.com/tac

Copyright (c) 2009, Cisco Systems, Inc. All rights reserved.

The copyrights to certain works contained in this software are

owned by other third parties and used and distributed under

license. Certain components of this software are licensed under

the GNU General Public License (GPL) version 2.0 or the GNU

Lesser General Public License (LGPL) Version 2.1. A copy of each

such license is available at

http://www.opensource.org/licenses/gpl-2.0.php and

http://www.opensource.org/licenses/lgpl-2.1.php

 

dc03-ucs-A(local-mgmt)# erase config

All UCS configurations will be erased and system will reboot. Are you sure? (yes/no):yes

Removing all the configuration. Please wait....

/bin/rm: cannot remove directory `/bootflash/sysdebug//tftpd_logs': Device or resource busy

sudo: cannot get working directory

sudo: cannot get working directory

Configurations are cleaned up. Rebooting....

[ 408.459209] Shutdown Ports..

[ 408.493606] writing reset reason 9,

 

 

Broadcast message from root (ttyS0) (Sun Mar 1 09:55:24 2015):

Step 14 (Optional)

Remap Cisco UCS 6100 fabric interconnect FC ports 2/1 to 2/4 on a N10-E0440 expansion module or any slot 3 ports onto the new fabric interconnect expansion module

Use Cisco UCS Manager to delete the ports on the subordinate fabric interconnect that you will need to move within the configuration.
For each port you have just deleted, create new ports on either slot 1 or slot 2. These ports must use the same port type definitions as the old ports, but will use different port numbers.
For recently moved Ethernet server ports, reconfigure the associated service profile to use the new port number for the appropriate LAN pin group.
For recently moved uplink Ethernet ports, reconfigure the port channel settings to use the new ports.
For recently moved uplink FC ports, reconfigure the associated service profile SAN pin group to use the new ports.
Re-acknowledge chassis for blade servers and fabric extender for rack servers.
This will be disruptive to traffic, but is necessary in this specific scenario.

If you use SAN pingroup, this can be avoided

Step 15

The new subordinate fabric interconnect will automatically synchronize the configuration and database/state information from the primary fabric interconnect. Synchronization between primary and subordinate fabric interconnects can take several minutes. You may see an error message that will persist until the server ports are enabled. The port configuration is copied from the subordinate switch to the new hardware.

We replay the setup to join the existing FI

INIT: Sending processes the TERSending all processes the TERM signal...

Sending all processes the KILL signal...

Saving random seed:

Syncing hardware clock to system time WARNING from hwclock: The clock was in 11 minute mode, which normally means that something else, possibly an NTP daemon, has been setting the hardware clock. Setting the clock with hwclock turns off 11 minute mode. See hwclock documentation.

Unmounting file systems: umount2: Device or resource busy