Tech – Page 33 – jonamiki.com

April 28, 2014November 21, 2018

Configuring iSCSI and management networks on a Dell EqualLogic PS-M4110 storage array

Quick instructions on setting up an EqualLogic PS-M4110 storage array.
In this case it’s a blade model located in a Dell M1000e chassis, slot 7 and 8.
Fabric B is the iSCSI fabric and fabric A is for management
We start by configuring fabric B, then A

Since there is no IP configured, we connect via serial.
Luckily the M1000e provides serial connectivity via the CMC as per the below:

SSH to CMC IP address:
==============================

Using username "root".
Welcome to the CMC firmware version 4.50.A00.201311120922

$
$

Switch to the EQL serial interface (connect to the slot ID)
==============================

$ connect server-7
Telnet escape character is '^\'.
Trying 169.254.31.7...
Connected to server-7.
Escape character is '^\'.

PS Series Storage Arrays
Unauthorized Access Prohibited

Log in (default user/pass: grpadmin/grpadmin)
==============================

login: grpadmin
Password:

Welcome to Group Manager

Copyright 2001-2012 Dell Inc.

2724:5:unknown (0-000000-000000000-0000000000000000):netmgtd:28-Apr-2014 01:52:53.590006:rcc_util.c:1029:INFO:25.2.9:CLI: Login to account grpadmin succeeded, using local authentication. User privilege is group-admin.
It appears that the storage array has not been configured.
Would you like to configure the array now ? (y/n) [n]y

Group Manager Setup Utility

The setup utility establishes the initial network and storage
configuration for a storage array and then configures the array
as a member of a new or existing group of arrays.

For help, enter a question mark (?) at a prompt.

Do you want to proceed (yes | no ) [no]: yes

Initializing. This may take several minutes to complete..

Enter the network configuration for the array.

Member name []: DSC-ARRAY-02
Network interface [eth0]:
IP address for network interface []: 192.168.105.29
Netmask [255.255.255.0]:
Default gateway [192.168.105.1]:

Initializing interface eth0. This may take a minute.....

Enter the IP address and name of the group that the array will join.

Note: If creating a new group, just enter the desired group name and IP
==============================

Group name []: DSC-SHARED-SAN
Group IP address []: 192.168.105.28

Searching to see if the group exists. This may take a few minutes.

The group does not exist or currently cannot be reached. Make sure
you have entered the correct group IP address and group name.

Do you want to create a new group (yes | no) [yes]:

Group Configuration

Group Name: DSC-SHARED-SAN
Group IP address: 192.168.105.28

Do you want to use the group settings shown above (yes | no) [yes]:
Password for managing group membership:
Retype password for verification:

Password for the default group administration(grpadmin) account:
Retype password for verification:

Saving the configuration...

Waiting for configuration to become active......Done

Group DSC-SHARED-SAN has been created with one member.
Use the Group Manager GUI or CLI to set the RAID policy
for the member. You can then create a volume which
a host can connect to using an iSCSI initiator.

To access the Group Manager GUI, specify http://group_ip_address in
a Web browser window. To access the CLI, use telnet or SSH to
connect to the group IP address from a remote terminal, or attach a
console terminal directly to a serial port on a group member's
active control module. Log in to the default group administration
account (grpadmin) using the password you specified when creating
this group. See the Group Administration manual for more
information.

DSC-SHARED-SAN>
DSC-SHARED-SAN>
DSC-SHARED-SAN>

Setting up the management network:
=====================================

DSC-SHARED-SAN> show member
Name Status Version Disks Capacity FreeSpace Connections
---------- ------- ---------- ----- ---------- ---------- -----------
DSC-ARRAY- online V6.0.0 (R2 14 8.72TB 8.72TB 0
02 59485)
DSC-SHARED-SAN> member select DSC-ARRAY-02 eth select 1 mgmt-only enable
Make sure the IP address is on the management subnet.
DSC-SHARED-SAN> member select DSC-ARRAY-02 eth select 1 ipaddress 10.6.26.227 netmask 255.255.255.0
DSC-SHARED-SAN>
DSC-SHARED-SAN> member select DSC-ARRAY-02 eth select 1 up
This port is for group management only. Make sure it is connected to a dedicated
management network.
Do you want to enable the management interface? (y/n) [n]y

DSC-SHARED-SAN>

The array can now be accessed via the web:
==============================
http://10.6.26.227

December 22, 2013January 24, 2018

Nagios3 – location of config and plugin directories with Crunchbang (debian squeeze)

First:
apt-get install nagios3
apt-get install freeipmi

Access from http://localhost/nagios3/

Config files:
root@cruncher01:~# ls -l /etc/nagios3/conf.d/
total 32
-rw-r–r– 1 root root 1695 Nov 1 23:11 contacts_nagios2.cfg
-rw-r–r– 1 root root 418 Nov 1 23:11 extinfo_nagios2.cfg
-rw-r–r– 1 root root 1152 Nov 1 23:11 generic-host_nagios2.cfg
-rw-r–r– 1 root root 1803 Nov 1 23:11 generic-service_nagios2.cfg
-rw-r–r– 1 root root 678 Nov 1 23:11 hostgroups_nagios2.cfg
-rw-r–r– 1 root root 2167 Nov 1 23:11 localhost_nagios2.cfg
-rw-r–r– 1 root root 657 Nov 1 23:11 services_nagios2.cfg
-rw-r–r– 1 root root 1609 Nov 1 23:11 timeperiods_nagios2.cfg
root@cruncher01:~#

Plugin directory:
root@cruncher01:~# ls -l /usr/lib/nagios/plugins/ | head
total 3588
-rwxr-xr-x 1 root root 108904 Jun 28 2012 check_apt
-rwxr-xr-x 1 root root   7262 Jul 3 2012 check_backuppc
-rwxr-xr-x 1 root root   2242 Jun 28 2012 check_breeze
-rwxr-xr-x 1 root root 51984 Jun 28 2012 check_by_ssh
-rwxr-xr-x 1 root root   1723 Jul 3 2012 check_cert_expire
lrwxrwxrwx 1 root root      9 Jun 28 2012 check_clamd -> check_tcp
-rwxr-xr-x 1 root root 35112 Jun 28 2012 check_cluster
-rwxr-xr-x 1 root root 51536 Jun 28 2012 check_dhcp
-rwxr-xr-x 1 root root 47568 Jun 28 2012 check_dig
root@cruncher01:~#

October 7, 2013December 14, 2021

How to enable NTP on the vCenter appliance

VMware vCenter Server Appliance 5.1.0.10200 Build 1235310
root@10.10.10.10’s password:
Last login: Mon Oct 7 17:18:29 2013 from vrtx-vcenter
vrtx-vcenter:~ # yast2 ntp-client add server=210.173.160.27

Error:
Cannot update the dynamic configuration policy.

vrtx-vcenter:~ # ls -l /etc/resolv.conf*
-rw-r–r– 1 root root 22 Oct 8 2013 /etc/resolv.conf
-rw-r–r– 1 root root 795 Oct 7 17:35 /etc/resolv.conf.netconfig
vrtx-vcenter:~ # cp -p /etc/resolv.conf /etc/resolv.conf.orig
vrtx-vcenter:~ # !ls
ls -l /etc/resolv.conf*
-rw-r–r– 1 root root 22 Oct 8 2013 /etc/resolv.conf
-rw-r–r– 1 root root 795 Oct 7 17:35 /etc/resolv.conf.netconfig
-rw-r–r– 1 root root 22 Oct 8 2013 /etc/resolv.conf.orig
vrtx-vcenter:~ # cat /etc/resolv.conf.netconfig > /etc/resolv.conf
vrtx-vcenter:~ # !ls
ls -l /etc/resolv.conf*
-rw-r–r– 1 root root 795 Oct 7 17:38 /etc/resolv.conf
-rw-r–r– 1 root root 795 Oct 7 17:35 /etc/resolv.conf.netconfig
-rw-r–r– 1 root root 22 Oct 8 2013 /etc/resolv.conf.orig
vrtx-vcenter:~ # yast2 ntp-client add server=210.173.160.27
vrtx-vcenter:~ # yast2 ntp-client enable
vrtx-vcenter:~ # sntp -P no -r 210.173.160.27
vrtx-vcenter:~ # date
Mon Oct 7 17:39:25 JST 2013
vrtx-vcenter:~ # cp -p /etc/resolv.conf.orig /etc/resolv.conf
vrtx-vcenter:~ # !ls
ls -l /etc/resolv.conf*
-rw-r–r– 1 root root 22 Oct 8 2013 /etc/resolv.conf
-rw-r–r– 1 root root 795 Oct 7 17:35 /etc/resolv.conf.netconfig
-rw-r–r– 1 root root 22 Oct 8 2013 /etc/resolv.conf.orig
vrtx-vcenter:~ #

July 5, 2013

vCenter AD authentication

When enabling Active Directory authentication on the vCenter appliance, ensure that DNS name resolution is working first. Set the DNS settings and hostname and then ensure that resolution and reverse-lookup of the FQDN works. It may be necessary to add the Host(A) record and pointer for the vCenter appliance on the DNS server itself.

Failed AD activation (no DNS entry, and vCenter doesn’t register itself it seems):

After adding host and reverse lookup records on the DNS server:

July 5, 2013December 14, 2021

vCenter appliance: “No networking detected”

If after deploying and booting the vCenter appliance, automatic network configuration fails, the vCenter console will display “No networking detected” in red. To configure networking:

1. Access the appliance VM console via the the vSphere client / web client

2. Login using “root” and “vmware” as password

3. At the command prompt, enter “/opt/vmware/share/vami/vami_config_net”

4. The below screen will be shown, allowing for network configuration