MonPtitSite - Contributions de l’utilisateur [fr]

Virtualisation/KVM/Intro

2026-10-29T12:37:43Z

Admin :

{{MediaWiki}}


Convertir un ensemble de fichiers VMDK en .qcow2 :

for f in *.vmdk; do echo $f ; qemu-img convert -p -O qcow2 -S 0 $f ${f%.vmdk}.qcow2 ; done

{{REFERENCE
|nom=QEMU
|url=https://fr.wikipedia.org/wiki/QEMU
}}

DOC:UNIX:Commandes

2023-07-17T06:58:22Z

Admin : /* renommage de fichiers en masse */

{{MediaWiki}}
 
{{FOND_BLEU|Recettes de cuisine du sysadmin}}
=Recettes de cuisine & commandes utiles=

==Comment dire à linux qu'un disque (LUN SAN) a changé de taille ? ==

la commande a lancer est :

'''# blockdev --rereadpt /dev/sdx'''
(x = lettre associée au LUN)

# dmesg
SCSI device sdc: drive cache: write back w/ FUA
'''sdc: detected capacity change from 42949672960 to 214748364800'''
sdc: sdc1
SCSI device sdc: 419430400 512-byte hdwr sectors (214748 MB)
sdc: Write Protect is off
sdc: Mode Sense: a5 00 10 08

# fdisk -l /dev/sdx
Disk /dev/sdx: 214.7 GB, '''214748364800''' bytes
255 heads, 63 sectors/track, 26108 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 1 26108 209712478+ 8e Linux LVM

Puis, il faut rescanner les chemins, soit avec en lancant simplement multipath soit en utilisant le démon multipathd

# multipathd -k"resize multipath mpathX"

==Comment zipper (ou traiter) un ensemble de fichiers contenant des caractères blancs dans le nom ?==

la commande magique :

find <nom rép> -name '*.pdf' -print | sed "s/'/\\\'/g" | xargs -I "{}" zip -9m "{}".zip "{}"

que fait cette commande ?

elle recherche à partir d'un répertoire donné tous les fichiers PDF, affiche leurs noms, protège le caractère ' ' s'il y a lieu et ZIP le fichier en compression maximale

petite variante :

find . -mtime +365 -name '*.pdf' -print | sed "s/'/\\\'/g" | xargs -I "{}" zip -9m "{}".zip "{}"

idem que précédemment, mais ne prend que les fichiers modifiés il y à plus d'un an à partir du répertoire courant

==Comment supprimer les sous dossiers vides d'un répertoire ==

find /symlnks/io/jobs/workflows/wkftwist -depth -mindepth 2 -type d -empty -mtime +1 -print | xargs rmdir

recherche tous les sous dossiers (-type d ) vides (-empty) modifiés il y a plus d'un jour (-mtime +1) en ne prenant en compte qu'à partir du 2è niveau (-depth -mindepth 2)

==Commande equivalente à un "tree size" par répertoire ==

ex : trouver la taille des dossiers .trash" de MisTRAL

<syntaxhighlight lang="bash">
du -k `find /mnt/nfsshare/6.0/MiSTRAL/raid \
-maxdepth 2 \
-name '*.trash' \
-type d ` | \
perl -ni -e '$i += $_ ; END {printf "%.02f Mo" , $i/1024/1024 ."\n"}'
</syntaxhighlight>

= bash =

== créer 100 fichiers (vides) en 1 commande ==

Utilisation de l'opérateur <code>..</code> :

<syntaxhighlight lang="bash">
$ touch {0..9}{0..9}.fic
</syntaxhighlight>

== renommage de fichiers en masse ==

ex : changer l'extension de fichiers : *.fic en *.txt

<syntaxhighlight lang="bash">
$ for file in `find -name "*.fic"`; do mv "$file" "${file/.fic/.txt}" ; done
</syntaxhighlight>

== connaître les processus qui utilisent la swap ==

<syntaxhighlight lang="bash">
for proc in /proc/[0-9]*; do
awk '/VmSwap/ { print $2 "\t'`readlink $proc/exe | awk '{ print $1 }'`'" }' $proc/status;
done | sort -n | awk '{ total += $1 ; print $0 } END { print total "\tTotal" }'
</syntaxhighlight>

DOC:UNIX:Commandes

2023-07-16T21:55:35Z

Admin : /* renommage de fichiers en masse */

{{MediaWiki}}
 
{{FOND_BLEU|Recettes de cuisine du sysadmin}}
=Recettes de cuisine & commandes utiles=

==Comment dire à linux qu'un disque (LUN SAN) a changé de taille ? ==

la commande a lancer est :

'''# blockdev --rereadpt /dev/sdx'''
(x = lettre associée au LUN)

# dmesg
SCSI device sdc: drive cache: write back w/ FUA
'''sdc: detected capacity change from 42949672960 to 214748364800'''
sdc: sdc1
SCSI device sdc: 419430400 512-byte hdwr sectors (214748 MB)
sdc: Write Protect is off
sdc: Mode Sense: a5 00 10 08

# fdisk -l /dev/sdx
Disk /dev/sdx: 214.7 GB, '''214748364800''' bytes
255 heads, 63 sectors/track, 26108 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 1 26108 209712478+ 8e Linux LVM

Puis, il faut rescanner les chemins, soit avec en lancant simplement multipath soit en utilisant le démon multipathd

# multipathd -k"resize multipath mpathX"

==Comment zipper (ou traiter) un ensemble de fichiers contenant des caractères blancs dans le nom ?==

la commande magique :

find <nom rép> -name '*.pdf' -print | sed "s/'/\\\'/g" | xargs -I "{}" zip -9m "{}".zip "{}"

que fait cette commande ?

elle recherche à partir d'un répertoire donné tous les fichiers PDF, affiche leurs noms, protège le caractère ' ' s'il y a lieu et ZIP le fichier en compression maximale

petite variante :

find . -mtime +365 -name '*.pdf' -print | sed "s/'/\\\'/g" | xargs -I "{}" zip -9m "{}".zip "{}"

idem que précédemment, mais ne prend que les fichiers modifiés il y à plus d'un an à partir du répertoire courant

==Comment supprimer les sous dossiers vides d'un répertoire ==

find /symlnks/io/jobs/workflows/wkftwist -depth -mindepth 2 -type d -empty -mtime +1 -print | xargs rmdir

recherche tous les sous dossiers (-type d ) vides (-empty) modifiés il y a plus d'un jour (-mtime +1) en ne prenant en compte qu'à partir du 2è niveau (-depth -mindepth 2)

==Commande equivalente à un "tree size" par répertoire ==

ex : trouver la taille des dossiers .trash" de MisTRAL

<syntaxhighlight lang="bash">
du -k `find /mnt/nfsshare/6.0/MiSTRAL/raid \
-maxdepth 2 \
-name '*.trash' \
-type d ` | \
perl -ni -e '$i += $_ ; END {printf "%.02f Mo" , $i/1024/1024 ."\n"}'
</syntaxhighlight>

= bash =

== créer 100 fichiers (vides) en 1 commande ==

Utilisation de l'opérateur <code>..</code> :

<syntaxhighlight lang="bash">
$ touch {0..9}{0..9}.fic
</syntaxhighlight>

== renommage de fichiers en masse ==

ex : changer l'extension de fichiers : *.fic en *.txt

<syntaxhighlight lang="bash">
$ for file in `find -name "*.fic"`; do mv "$file" "${file/.fic/.txt}" ; done
</syntaxhighlight>

"" connaître les processus qui utilisent la swap ==

<syntaxhighlight lang="bash">
for proc in /proc/[0-9]*; do
awk '/VmSwap/ { print $2 "\t'`readlink $proc/exe | awk '{ print $1 }'`'" }' $proc/status;
done | sort -n | awk '{ total += $1 ; print $0 } END { print total "\tTotal" }'
</syntaxhighlight>

Virtualisation/VMWARE/SNMPv3

2023-05-25T14:51:45Z

Admin : /* Sur une appliance VCSA 7 */

{{MediaWiki}}
 
{{FOND_BLEU|VMWare - '''Configuration SNMPv3'''}}

=Configurer snmpv3 sur un ESX=

<syntaxhighlight lang="bash">

esxcli system snmp set -r -e 1 -l debug

engineid=$(esxcli system snmp get |grep Engineid |awk '{print $2}')
esxcli system snmp get

SNMP_USER=s_monitoring
SECRETS_PATH=/vmfs/volumes/localDS-${HOSTNAME}/.secrets
mkdir ${SECRETS_PATH}

mv secret* ${SECRETS_PATH}

esxcli system snmp set --authentication SHA1
esxcli system snmp set --privacy AES128

hash=$(esxcli system snmp hash --auth-hash ${SECRETS_PATH}/secret1 --priv-hash ${SECRETS_PATH}/secret2)
echo $hash
authhash=$(echo $hash | awk '{print $2}')
privhash=$(echo $hash | awk '{print $4}')

esxcli system snmp hash --auth-hash ${SECRETS_PATH}/secret1 --priv-hash ${SECRETS_PATH}/secret2
esxcli system snmp set --users ${SNMP_USER}/${authhash}/${privhash}/priv
esxcli system snmp test --user ${SNMP_USER} --auth-hash ${SECRETS_PATH}/secret1 --priv-hash ${SECRETS_PATH}/secret2

esxcli system snmp set --remote-users ${SNMP_USER}/SHA1/${authhash}/AES128/${privhash}/${engineid}

</syntaxhighlight>

=Configurer snmpv3 sur une appliance VCSA 7 =

<syntaxhighlight lang="bash">
shell
mkdir .secrets
vi .secrets/secret1
vi .secrets/secret2

exit

snmp.set --authentication SHA1
snmp.set --privacy AES128
snmp.hash --auth_hash /root/.secrets/secret1 --priv_hash /root/.secrets/secret2

snmp.set --user monitoring_user@vsphere.local/c84c59c......1/787....d23/priv
snmp.get

</syntaxhighlight>

Virtualisation/VMWARE/SNMPv3

2023-05-25T14:51:33Z

Admin : /* sur un ESX */

{{MediaWiki}}
 
{{FOND_BLEU|VMWare - '''Configuration SNMPv3'''}}

=Configurer snmpv3 sur un ESX=

<syntaxhighlight lang="bash">

esxcli system snmp set -r -e 1 -l debug

engineid=$(esxcli system snmp get |grep Engineid |awk '{print $2}')
esxcli system snmp get

SNMP_USER=s_monitoring
SECRETS_PATH=/vmfs/volumes/localDS-${HOSTNAME}/.secrets
mkdir ${SECRETS_PATH}

mv secret* ${SECRETS_PATH}

esxcli system snmp set --authentication SHA1
esxcli system snmp set --privacy AES128

hash=$(esxcli system snmp hash --auth-hash ${SECRETS_PATH}/secret1 --priv-hash ${SECRETS_PATH}/secret2)
echo $hash
authhash=$(echo $hash | awk '{print $2}')
privhash=$(echo $hash | awk '{print $4}')

esxcli system snmp hash --auth-hash ${SECRETS_PATH}/secret1 --priv-hash ${SECRETS_PATH}/secret2
esxcli system snmp set --users ${SNMP_USER}/${authhash}/${privhash}/priv
esxcli system snmp test --user ${SNMP_USER} --auth-hash ${SECRETS_PATH}/secret1 --priv-hash ${SECRETS_PATH}/secret2

esxcli system snmp set --remote-users ${SNMP_USER}/SHA1/${authhash}/AES128/${privhash}/${engineid}

</syntaxhighlight>

= Sur une appliance VCSA 7 =

<syntaxhighlight lang="bash">
shell
mkdir .secrets
vi .secrets/secret1
vi .secrets/secret2

exit

snmp.set --authentication SHA1
snmp.set --privacy AES128
snmp.hash --auth_hash /root/.secrets/secret1 --priv_hash /root/.secrets/secret2

snmp.set --user monitoring_user@vsphere.local/c84c59c......1/787....d23/priv
snmp.get

</syntaxhighlight>

Virtualisation/VMWARE/SNMPv3

2023-05-25T14:51:03Z

Admin : Page créée avec « {{MediaWiki}} {{FOND_BLEU|VMWare - '''Configuration SNMPv3'''}} = sur un ESX = <syntaxhighlight lang="bash"> esxcli system snmp set -r -e 1 -l debug engineid=$(es… »

{{MediaWiki}}
 
{{FOND_BLEU|VMWare - '''Configuration SNMPv3'''}}

= sur un ESX =

<syntaxhighlight lang="bash">

esxcli system snmp set -r -e 1 -l debug

engineid=$(esxcli system snmp get |grep Engineid |awk '{print $2}')
esxcli system snmp get

SNMP_USER=s_monitoring
SECRETS_PATH=/vmfs/volumes/localDS-${HOSTNAME}/.secrets
mkdir ${SECRETS_PATH}

mv secret* ${SECRETS_PATH}

esxcli system snmp set --authentication SHA1
esxcli system snmp set --privacy AES128

hash=$(esxcli system snmp hash --auth-hash ${SECRETS_PATH}/secret1 --priv-hash ${SECRETS_PATH}/secret2)
echo $hash
authhash=$(echo $hash | awk '{print $2}')
privhash=$(echo $hash | awk '{print $4}')

esxcli system snmp hash --auth-hash ${SECRETS_PATH}/secret1 --priv-hash ${SECRETS_PATH}/secret2
esxcli system snmp set --users ${SNMP_USER}/${authhash}/${privhash}/priv
esxcli system snmp test --user ${SNMP_USER} --auth-hash ${SECRETS_PATH}/secret1 --priv-hash ${SECRETS_PATH}/secret2

esxcli system snmp set --remote-users ${SNMP_USER}/SHA1/${authhash}/AES128/${privhash}/${engineid}

</syntaxhighlight>

= Sur une appliance VCSA 7 =

<syntaxhighlight lang="bash">
shell
mkdir .secrets
vi .secrets/secret1
vi .secrets/secret2

exit

snmp.set --authentication SHA1
snmp.set --privacy AES128
snmp.hash --auth_hash /root/.secrets/secret1 --priv_hash /root/.secrets/secret2

snmp.set --user monitoring_user@vsphere.local/c84c59c......1/787....d23/priv
snmp.get

</syntaxhighlight>

VMWARE

2023-05-25T14:46:38Z

Admin :

{{MediaWiki}}
 
* [[Virtualisation/VMWARE/CommandsCLI| Liste de commandes CLI utiles]]
* [[Virtualisation/VMWARE/SNMPv3| Configuration SNMPv3 pour ESXi 7 et VCSA 7]]

Network/Juniper/Survival guide

2023-02-20T18:09:21Z

Admin : /* Advanced Commands Summary */

Network/Juniper/Survival guide

2023-02-20T18:08:47Z

Admin : /* Advanced Commands Summary */

Network/Juniper/Survival guide

2023-02-20T17:51:24Z

Admin : /* Command Summary */

{{MediaWiki}}
 
{{FOND_BLEU|Juniper- '''Petit guide de survie''' pour un newbie ...}}

= Sites Références =
* [https://www.juniper.net/documentation/us/en/software/junos/multicast-l2/index.html The bible ....]
* [https://supportportal.juniper.net/s/knowledge?language=en_US Base de connaissance Juniper ]

= Notes =

There are several acronyms for interface types and components:

* IFD – Interface Physical Device
* IFL – Interface Logical Device
* IFF – Address Family
* IFA – Address Entry

Common interface names are:

* ge – Gigabit ethernet
* xe – 10G ethernet
* et – 100G ethernet
* ae – aggregated ethernet (LAG/etherchannel)
* vlan or irb – Logical interface based on VLAN

SFP’s can be of different speeds (eg, one may be 1G, and another may be 10G). So be aware that the interface names may change based on the SFP used.

The interface naming convention is type-x/y/z

Type is ge, xe, etc
x – FPC (aka linecard)
y – module or slot
z – port number

There are several names for management interfaces. Each platform may use different names. These include fxp0, em0, me0, and vme0. Some of these are physical, and others are virtual.

Some interfaces, such as pimd, pime, dsc, ipip, and gre, are special interfaces that are used for special purposes.

An unnumbered interface does not have an IP address. This helps conserve IP addresses.

All interfaces are configured with a unit. This contains logical interface information, like addressing. Sometimes this is used to create sub-interfaces. Physical properties (duplex, link speed, etc) are not configured in the unit.

Each unit may have one or more family. This is where the address is applied. For example, the inet family is for IPv4 addressing.

Addresses can be primary, preferred, or secondary. Primary addresses are used for locally sourced (broadcast or multicast) traffic, destined to a remote subnet. Preferred addresses are for locally sourced traffic to the local subnet.

Configuring voice ports means three main steps:

* Configuring a voice VLAN
* Configuring PoE
* Configuring LLDP-MED

Junos supports regex during configuration.

=Command Summary=

{| class="wikitable"
!colspan="3"|Juniper OS Command summary
|-
! class="wikitable" | Command
! Mode
! Description
|-
|{{CODE|show system uptime }}
|operational
| Get uptime & date of all fpc
|-
|{{CODE|show log messages }}
|operational
| Dump system logs
|-
|{{CODE|show cli history }}
|operational
| Get cli commands history
|-
|{{CODE|show interfaces terse}}
|operational
| Get a simplified view of all interfaces on the system
|-
|{{CODE|show interfaces [extensive]}}
|operational
|Get interface statistics
|-
|{{CODE|show interfaces terse}}
|operational
| Get a simplified view of all interfaces on the system
|-
|{{CODE|show lacp interfaces '''ae'''''xx'' [extensive]}}
|operational
|Get bond LACP interface statistics
|-
|{{CODE|set interfaces INTERFACE …}}
|configuration
|Configures an interface
|-
|{{CODE|set interfaces INTERFACE description}}
|configuration
|Adds a description to an interface
|-
|{{CODE|set interfaces INTERFACE unit NUMBER family inet address …}}
|configuration
|Configures an IPv4 address
|-
|{{CODE|set interfaces INTERFACE disable}}
|configuration
|Disables an interface
|-
|{{CODE|set vlans NAME vlan-id ID}}
|configuration
|Defines a VLAN
|-
|{{CODE|show vlans}}
|operational
|Shows a list of configured VLANs
|-
|{{CODE|set interfaces INTERFACE unit 0 family ethernet-switching interface-mode <access/trunk>}}
|configuration
|Sets a layer-2 port type (trunk port or access port)
|-
|{{CODE|set interfaces INTERFACE unit 0 family ethernet-switching vlan members VLAN}}
|configuration
|Adds VLANs to the port
|-
|{{CODE|set interfaces INTERFACE vlan-tagging}}
|configuration
|Enables VLAN tagging, which enables the use of units as subinterfaces
|-
|{{CODE|set poe interface all}}
|configuration
|Enables PoE on all interfaces
|-
|{{CODE|set protocols lldp-med interface all}}
|configuration
|Enables LLDP-MED on all interfaces
|-
|{{CODE|rename}}
|configuration
|Renames some configuration
|-
|{{CODE|deactivate}}
|configuration
|Deactivates any part of the config
|-
|{{CODE|copy}}
|configuration
|Copy some configuration from one place to another
|-
|{{CODE|replace}}
|configuration
|Replace some configuration
|-
|{{CODE|annotate}}
|configuration
|Adds annotations into the config, like comments in code

|}

=Advanced Commands Summary=

{| class="wikitable"
!colspan="3"|Juniper OS Command summary
|-
! class="wikitable" | Command
! Mode
! Description
|-
|{{CODE|show system uptime }}
|operational
| Get uptime & date of all fpc
|-
|{{CODE|show log messages }}
|operational
| Dump system logs
|-
|{{CODE|show cli history }}
|operational
| Get cli commands history
|-
|{{CODE|show interfaces terse}}
|operational
| Get a simplified view of all interfaces on the system
|-
|{{CODE|show interfaces [extensive]}}
|operational
|Get interface statistics
|-
|{{CODE|show interfaces terse}}
|operational
| Get a simplified view of all interfaces on the system
|-
|{{CODE|show lacp interfaces '''ae'''''xx'' [extensive]}}
|operational
|Get bond LACP interface statistics
|-
|{{CODE|set interfaces INTERFACE …}}
|configuration
|Configures an interface
|-
|{{CODE|set interfaces INTERFACE description}}
|configuration
|Adds a description to an interface
|-
|{{CODE|set interfaces INTERFACE unit NUMBER family inet address …}}
|configuration
|Configures an IPv4 address
|-
|{{CODE|set interfaces INTERFACE disable}}
|configuration
|Disables an interface
|-
|{{CODE|set vlans NAME vlan-id ID}}
|configuration
|Defines a VLAN
|-
|{{CODE|show vlans}}
|operational
|Shows a list of configured VLANs
|-
|{{CODE|set interfaces INTERFACE unit 0 family ethernet-switching interface-mode <access/trunk>}}
|configuration
|Sets a layer-2 port type (trunk port or access port)
|-
|{{CODE|set interfaces INTERFACE unit 0 family ethernet-switching vlan members VLAN}}
|configuration
|Adds VLANs to the port
|-
|{{CODE|set interfaces INTERFACE vlan-tagging}}
|configuration
|Enables VLAN tagging, which enables the use of units as subinterfaces
|-
|{{CODE|set poe interface all}}
|configuration
|Enables PoE on all interfaces
|-
|{{CODE|set protocols lldp-med interface all}}
|configuration
|Enables LLDP-MED on all interfaces
|-
|{{CODE|rename}}
|configuration
|Renames some configuration
|-
|{{CODE|deactivate}}
|configuration
|Deactivates any part of the config
|-
|{{CODE|copy}}
|configuration
|Copy some configuration from one place to another
|-
|{{CODE|replace}}
|configuration
|Replace some configuration
|-
|{{CODE|annotate}}
|configuration
|Adds annotations into the config, like comments in code

|}

= Additional References =

Explanation of “ifd” and “ifl” indexes https://kb.juniper.net/InfoCenter/index?page=content&id=KB2820

Router Interfaces Overview https://www.juniper.net/documentation/en_US/junos/topics/concept/interfaces-interface-naming-overview.html

Performing Loopback Testing https://www.juniper.net/documentation/en_US/junos/topics/topic-map/ethernet-fast-and-gigabit-loopback-testing.html

Configuring Default, Primary, and Preferred Addresses and Interfaces https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/interfaces-configuring-default-primary-and-preferred-addresses-and-interfaces.html

Virtualisation/VMWARE/CommandsCLI

2022-12-01T16:17:22Z

Admin : /* Command Summary */

{{MediaWiki}}
 
{{FOND_BLEU|VMWare- '''Petit guide de survie''' en CLI ...}}

=Command Summary=

{| class="wikitable"
!colspan="3"|ESXi CLI commands
|-
! class="wikitable" | Command
! Mode
! Description
|-
|{{CODE|esxtop }}
|monitoring
| Monitor ESXi system activity

|-
|{{CODE|esxcli storage filesystem list }}
|storage
| Get list of available filesystems
|-
|{{CODE|esxcli network nic list}}
|network
| Get list of available network interfaces
|-
|{{CODE|esxcli network nic [up / down] -n vmnicX}}
|network
| enable / disable a network interfaces
|}

Virtualisation/VMWARE/CommandsCLI

2022-12-01T14:08:24Z

Admin : /* Command Summary */

{{MediaWiki}}
 
{{FOND_BLEU|VMWare- '''Petit guide de survie''' en CLI ...}}

=Command Summary=

{| class="wikitable"
!colspan="3"|ESXi CLI commands
|-
! class="wikitable" | Command
! Mode
! Description
|-
|{{CODE|esxcli storage filesystem list }}
|storage
| Get list of available filesystems
|-
|{{CODE|esxcli network nic list}}
|network
| Get list of available network interfaces
|-
|{{CODE|esxcli network nic [up / down] -n vmnicX}}
|network
| enable / disable a network interfaces
|}

Virtualisation/VMWARE/CommandsCLI

2022-12-01T09:52:23Z

Admin : Page créée avec « {{MediaWiki}} {{FOND_BLEU|VMWare- '''Petit guide de survie''' en CLI ...}} =Command Summary= {| class="wikitable" !colspan="3"|ESXi CLI commands |- ! class="wikit… »

{{MediaWiki}}
 
{{FOND_BLEU|VMWare- '''Petit guide de survie''' en CLI ...}}

=Command Summary=

{| class="wikitable"
!colspan="3"|ESXi CLI commands
|-
! class="wikitable" | Command
! Mode
! Description
|-
|{{CODE|esxcli storage filesystem list }}
|storage
| Get list of available filesystems
|-
|{{CODE|esxcli network nic list}}
|network
| Get list of available network interfaces

|}

VMWARE

2022-12-01T09:47:44Z

Admin : Page créée avec « {{MediaWiki}} * Liste de commandes CLI utiles »

{{MediaWiki}}
 
* [[Virtualisation/VMWARE/CommandsCLI| Liste de commandes CLI utiles]]

Modèle:Virtualisation

2022-12-01T09:46:14Z

Admin :

* [[VMWARE|VMWare]]
* [[Virtualisation|Virtualisation]]

Modèle:Virtualisation

2022-12-01T09:45:41Z

Admin :

* [[Virtualisation|VMWare]]
* [[Virtualisation|Virtualisation]]

Network/Juniper/Survival guide

2022-11-25T09:55:20Z

Admin : /* Command Summary */

Network/Juniper/Survival guide

2022-11-25T09:26:52Z

Admin : /* Command Summary */

Network/Juniper/Survival guide

2022-11-25T09:23:26Z

Admin : /* Command Summary */

Network/Juniper/Survival guide

2022-11-25T08:10:13Z

Admin : /* Command Summary */

Network/Juniper/Survival guide

2022-11-24T18:17:36Z

Admin :

Network/Juniper/Survival guide

2022-11-24T18:08:14Z

Admin : Page créée avec « {{MediaWiki}} {{FOND_BLEU|Juniper- '''Petit guide de survie''' pour un newbie ...}} = Sites Références = * [https://www.juniper.net/documentation/us/en/software/j… »

{{MediaWiki}}
 
{{FOND_BLEU|Juniper- '''Petit guide de survie''' pour un newbie ...}}

= Sites Références =
* [https://www.juniper.net/documentation/us/en/software/junos/multicast-l2/index.html The bible ....]
* [https://supportportal.juniper.net/s/knowledge?language=en_US Base de connaissance Juniper ]

= Notes =

There are several acronyms for interface types and components:

* IFD – Interface Physical Device
* IFL – Interface Logical Device
* IFF – Address Family
* IFA – Address Entry

Common interface names are:

* ge – Gigabit ethernet
* xe – 10G ethernet
* et – 100G ethernet
* ae – aggregated ethernet (LAG/etherchannel)
* vlan or irb – Logical interface based on VLAN

SFP’s can be of different speeds (eg, one may be 1G, and another may be 10G). So be aware that the interface names may change based on the SFP used.

The interface naming convention is type-x/y/z

Type is ge, xe, etc
x – FPC (aka linecard)
y – module or slot
z – port number

There are several names for management interfaces. Each platform may use different names. These include fxp0, em0, me0, and vme0. Some of these are physical, and others are virtual.

Some interfaces, such as pimd, pime, dsc, ipip, and gre, are special interfaces that are used for special purposes.

An unnumbered interface does not have an IP address. This helps conserve IP addresses.

All interfaces are configured with a unit. This contains logical interface information, like addressing. Sometimes this is used to create sub-interfaces. Physical properties (duplex, link speed, etc) are not configured in the unit.

Each unit may have one or more family. This is where the address is applied. For example, the inet family is for IPv4 addressing.

Addresses can be primary, preferred, or secondary. Primary addresses are used for locally sourced (broadcast or multicast) traffic, destined to a remote subnet. Preferred addresses are for locally sourced traffic to the local subnet.

Configuring voice ports means three main steps:

* Configuring a voice VLAN
* Configuring PoE
* Configuring LLDP-MED

Junos supports regex during configuration.

<syntaxhighlight lang="bash">
[user@demo project2]$ tree -F group_vars
group_vars/
├── db_servers/
│ ├── 3.yml
│ ├── a.yml
│ └── myvars.yml
├── lb_servers/
│ ├── 2.yml
│ ├── b.yml
│ └── something.yml
└── web_servers/
└── nothing.yml
</syntaxhighlight>

=Command Summary=

{| class="wikitable"
!colspan="3"|Juniper OS Command summary
|-
! class="wikitable" | Command
! Mode
! Description
|-
|{{CODE|show interfaces terse}}
|operational
| Get a simplified view of all interfaces on the system
|-
|{{CODE|show interfaces [extensive]}}
|operational
| Get interface statistics
|-
|{{CODE|ansible_port}}
|Port utilisé par Ansible pour se connecter à l'hôte géré. Pour le plug-in de connexion par SSH (par défaut), la valeur par défaut est '''22'''.
|-
|{{CODE|ansible_user}}
|Utilisateur dont se sert Ansible pour se connecter à l'hôte géré. Le comportement par défaut d'Ansible est de se connecter à l'hôte géré à l'aide du même nom d'utilisateur que celui qui exécute le playbook Ansible sur le noeud de contrôle.
|-
|{{CODE|ansible_become_user}}
|Une fois qu'Ansible s'est connecté à l'hôte géré, il bascule vers cet utilisateur en utilisant absible_become_method (qui est {{CODE|sudo}} par défaut). Il se peut que vous deviez vous procurer des informations d'identification d'authentification de quelque façon que ce soit.
|-
|{{CODE|ansible_python_interpreter}}
|Chemin d'accès à l'exécutable Python qu'Ansible doit utiliser sur l'hôte géré. Sur Ansible 2.8 et versions ultérieures, cette valeur par défaut est {{CODE|auto}}, qui sélectionne automatiquement un interpréteur Python sur l'hôte exécutant le playbook en fonction du système d'exploitation qu'il exécute. Ainsi, il n'est plus autant nécessaire d'utiliser ce paramètre que dans les versions antérieures d'Ansible.
|}

=== Variables utilisées lors d'exécution de playbooks ===

Lorsqu'un play est en cours d'exécution, un certain nombre de variables et de faits peuvent être utilisés pour identifier le nom de l'hôte géré actuel qui exécute une tâche :

{| class="wikitable"
!colspan="2"|Variables Ansible spécifiques à l'exécution
|-
! class="wikitable" | Variable
! Description
|-
|{{CODE|inventory_hostname}}
|Nom de l'hôte géré en cours de traitement, extrait de l'inventaire.
|-
|{{CODE|ansible_host}}
|Adresse IP ou nom d'hôte réel qui a été utilisé pour se connecter à l'hôte géré, comme indiqué
précédemment.
|-
|{{CODE|ansible_facts ['nom d'hôte']}}
|Nom court (non qualifié) de l'hôte collecté comme un fait de l'hôte géré.
|-
|{{CODE|ansible_facts ['fqdn']}}
|Nom de domaine complet de l'hôte collecté comme un fait de l'hôte géré.
|-
|{{CODE|ansible_play_hosts}}
|liste de tous les hôtes qui n'ont pas encore échoué au cours du play actuel (et qui, par conséquent, sera utilisée
pour les tâches restantes du play).|}
|}

== Penser ré-utilisabilité ! ==

Les rôles permettent de créer des playbooks simples et de réutiliser du code commun à plusieurs projets. Un '''role''' doit porter sur un objectif ou une fonction spécifique.
Idéalement, il est préférable de créer des rôles génériques configurables par le biais de variables. Ces variables sont le plus souvent définies par défaut dans le fichier YAML <code>roles/[nom_role]/default/main.yml</code>
De cette façon, un rôle disposant de son propre paramétrage et ensemble de tâches peut facillement être intégré dans un autre playbook.

Si un playbook doit modifier le contenu d'une variable définie par un rôle, il suffit :
* soit inclure un fichier de définition de variables au niveau du playbook (cf <code>[https://docs.ansible.com/ansible/latest/user_guide/playbooks_variables.html#defining-variables-in-files var_files]</code>)
* soit définir une zone tasks <code>vars:</code> qui remplace le contenu de cette variable. (cf [https://docs.ansible.com/ansible/latest/user_guide/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable Ordre de précédence des variables dans un playbook ansible])

Exemple

<syntaxhighlight lang="yaml">
- hosts: webservers
vars:
apache2_config: true
apache2_default_port: 8000
roles:
ansible-apache2

</syntaxhighlight>

Ce playbook utilise le rôle <code>ansible-apache2</code> en modifiant 2 variables utilisées par ce rôle : <code>apache2_config</code> & <code>apache2_default_port</code>.

A l'éxécution de ce playbook, le service apache2 sera installé sur les serveurs <code>webservers</code> pour écouter sur le port 8000/tcp.

== Exécution centralisée des playbooks ==

Pour contrôler l'accès aux systèmes et auditer l'activité d'Ansible, il est nécessaire d'envisagez l'utilsiation d'un serveur de contrôle dédié à partir duquel tous les playbooks Ansible sont exécutés.
Les administrateurs système doivent toujours disposer de leurs propres comptes sur le système, ainsi que des informations d'identification permettant de se connecter aux hôtes gérés et d'augmenter les privilèges, si nécessaire.
Lorsqu'un administrateur système cesse de travailler sur le projet, sa clé SSH peut être supprimée du fichier <code>authorized_keys</code> de l'hôte géré et ses privilèges de commande <code>sudo</code> peuvent être révoqués, sans répercussion sur les autres administrateurs.

Ce serveur central peut avantageusement héberger les services <code>[https://www.ansible.com/products/awx-project/faq awx]</code> ou la version supportée par Red Hat <code>[https://www.ansible.com/products/tower Ansible Tower]</code>

= Tester régulièrement =

Il est bien évident qu'il faut tester les playbooks aussi bien au cours de la phase de développement que pendant l'exécution des playbooks eux-même. En effet, Ansible offre cette possibilité de s'auto-valider en définissant des tâches spécifiques permettant de vérifier une étape précédente d'un playbook.

== Test des résultats des tâches ==
Si on a besoin de confirmer la réussite d'une tâche, vérifiez le résultat de la tâche au lieu de faire confiance au code de retour du module.
Il existe plusieurs moyens de valider une tâche, en fonction du module concerné.

Exemple :

<syntaxhighlight lang="yaml">
- Start web server
service:
name: httpd
status: started
- name: Check web site from web server
uri:
url: http://{{ ansible_fqdn }}
return_content: yes
register: example_webpage
failed_when: example_webpage.status != 200
</syntaxhighlight>

== Utilisation de block/rescue pour effectuer une récupération ou une restauration ==

La directive <code>block</code> est utile pour regrouper des tâches ; lorsqu'elle est associée à la directive
<code>rescue</code>, elle est utile lorsqu'il s'agit d'effectuer une récupération après des erreurs ou des pannes.

Exemple :

<syntaxhighlight lang="yaml">
- block:
- name: Check web site from web server
uri:
url: http://{{ ansible_fqdn }}
return_content: yes
register: example_webpage
failed_when: example_webpage.status != 200
rescue:
- name: Restart web server
service:
name: httpd
status: restarted
</syntaxhighlight>

== Outils de test ==

* <code>ansible-playbook --syntax-check</code> : pour vérifier la syntaxe d'un playbook (sans l'exécuter)
* <code>ansible-playbook --check</code> : Exécute un playbook en mode "vérification"
{{NOTE
|contenu=
Cette vérification ne garantit pas une précision parfaite, étant donné que le playbook peut avoir besoin d'exécuter réellement certaines tâches avant que les tâches ultérieures du playbook ne fonctionnent correctement. Certaines tâches peuvent être marquées avec la directive check_mode: no. Ces tâches s'exécutent même en mode vérification.
}}

{{NOTE
|contenu=
Il existe d'autres outils. Par exemple :
L'outil <code>ansible-lint</code> analyse un playbook et recherche les problèmes éventuels. Tous les problèmes signalés n'interrompront pas forcément le fonctionnement du playbook, mais les problèmes signalés peuvent indiquer la présence d'une erreur.
L'outil <code>yamllint</code> analyse un fichier YAML et tente d'identifier les problèmes liés à la syntaxe YAML. Cet outil n'a pas une connaissance directe d'Ansible, mais il peut intercepter des problèmes potentiels de syntaxe YAML.
}}

Network/Juniper

2022-11-24T17:57:48Z

Admin : Page créée avec « {{MediaWiki}} * Petit guide de survie - '''Juniper''' »

{{MediaWiki}}
 
* [[Network/Juniper/Survival_guide| Petit guide de survie - '''Juniper''' ]]

Modèle:Boîte à Outils

2022-11-24T17:53:46Z

Admin :

* [[Tools/Ansible|Ansible]]
* [[Tools/Gitlab|Gitlab]]
* [[Network/Juniper|Commandes utiles sous Juniper]]

DOCS/UNIX/RHEL/ISCSI/Config iSCSI Initiator

2022-08-31T08:33:08Z

Admin : /* Configure iSCSI Initiator on CentOS 9|AlmaLinux 9|RHEL 9 systems */

{{MediaWiki}}
{{FOND_BLEU|QEMU - '''Configure iSCSI Initiator on CentOS 9|AlmaLinux 9|RHEL 9'''}}

= Sites Références =

Cet article est une transposition sous MediaWiki de ces 2 adresses :
* [https://technixleo.com/configure-iscsi-target-on-centos-alma-rhel/ Configure iSCSI Target on CentOS 9|AlmaLinux 9|RHEL 9]
* [https://technixleo.com/iscsi-initiator-centos-alma-rhel/ Configure iSCSI Initiator on CentOS 9|AlmaLinux 9|RHEL 9]

iSCSI is an acronym that stands for Internet Small Computer Systems Interface. It is a Storage Area Network (SAN) Protocol that enables block-level SCSI data transport from Storage arrays to client computers that are not directly connected to them. iSCSI SAN consists of iSCSI Initiators which are the clients and iSCSI targets which are the servers on Storage Array controllers. They are connected by an iSCSI protocol and represented by a unique string known as iSCSI Qualified Name (iQN).

In iSCSI technology, the iSCSI initiator or commonly known as the iSCSI client needs to be installed on your system. It is then added to an initiator group or what is also known as the Client definition. These groups help identify which clients are allowed to connect with the storage server (the iSCSI targets). Logical Unit Numbers (LUNs) are created and assigned to a group or client definition. LUNs are representations of devices that are part of the physical iSCSI target. If the Client and server are on the same IP network, The initiator can automatically discover the target. Once connected, the LUN is available for use.

=iSCSI Initiator=

=Setup pre-reqs=
An IP of the Target needs to be known. I will use the iSCSI target from the [[DOCS/UNIX/RHEL/ISCSI/Config_iSCSI_Target|Configure iSCSI target]] guide. You can also follow the steps in that guide to create a target.

=Configure iSCSI Initiator on CentOS 9|AlmaLinux 9|RHEL 9 systems=
- Update your system packages.
sudo yum update -y
or
sudo dnf update -y

- Install iSCSI initiator utilities with the following command.
sudo dnf -y install iscsi-initiator-utils

- Check the initiator name using the following command

<syntaxhighlight lang="shell">
$ cat /etc/iscsi/initiatorname.iscsi
InitiatorName=iqn.1994-05.com.redhat:4e8ff68af729
</syntaxhighlight>

If you changed the name while setting up iSCSI target ACLs. You will have to configure the initiator file to the new name.
sudo vi /etc/iscsi/initiatorname.iscsi

- Change the initiator’s name to match the one set on the target server.
InitiatorName=iqn.1994-05.com.redhat:4e8ff68af729

- Save and exit the file.
- [OPTIONAL] Edit the iSCSI configuration file to add the authentication details.
sudo vi /etc/iscsi/iscsid.conf
- Uncomment the following lines and edit as shown.

<syntaxhighlight lang="shell">
node.session.auth.authmethod = CHAP
node.session.auth.username = technix
node.session.auth.password = technix_passwd
</syntaxhighlight>

- Save and exit the file, then start the iSCSI daemon.

<syntaxhighlight lang="shell">
sudo systemctl start iscsid.service
sudo systemctl enable iscsid.service
</syntaxhighlight>

- Discover the target by using the target’s IP address as shown below. The response will be the target’s IP address and iQN address.

<syntaxhighlight lang="shell">
$ sudo iscsiadm -m discovery -t st -p 192.168.200.40
192.168.200.40:3260,1 iqn.2022-06.com.redhat:technixleo
</syntaxhighlight>

- Confirm its status after discovery.

<syntaxhighlight lang="shell">
$ sudo iscsiadm -m node -o show

##Sample Outpout ##
# BEGIN RECORD 2.1.4
node.name = iqn.2022-06.com.redhat:technixleo
node.tpgt = 1
node.startup = automatic
node.leading_login = No
iface.iscsi_ifacename = default
.....
.....
</syntaxhighlight>

- You can log in to the server using the iQN

<syntaxhighlight lang="shell">
$ sudo iscsiadm -m node -T iqn.2022-06.com.redhat:technixleo -l
Logging in to [iface: default, target: iqn.2022-06.com.redhat:technixleo, portal: 192.168.200.40,3260]
Login to [iface: default, target: iqn.2022-06.com.redhat:technixleo, portal: 192.168.200.40,3260] successful.
</syntaxhighlight>

- Confirm the established session.

<syntaxhighlight lang="shell">
$ sudo iscsiadm -m session -o show
tcp: [2] 192.168.200.40:3260,1 iqn.2022-06.com.redhat:technixleo (non-flash)
</syntaxhighlight>

- Confirm the partitions with the following command.

<syntaxhighlight lang="shell">
$ cat /proc/partitions

major minor #blocks name

8 0 33554432 sda
8 1 1048576 sda1
8 2 32504832 sda2
11 0 8519680 sr0
253 0 29143040 dm-0
253 1 3358720 dm-1
8 16 5242880 sdb
8 32 33554432 sdc
</syntaxhighlight>

The new partition ‘sdb‘ of size 5GB has been added from the target server.
To find the iSCSI disk name you can also use the following command.

$ sudo grep "Attached SCSI" /var/log/messages
Jul 30 10:30:02 cent9 kernel: sd 3:0:0:0: [sdb] Attached SCSI disk

Next, we are going to create a file on that disk.
<syntaxhighlight lang="shell">
$ sudo mkfs.ext4 /dev/sdb
Creating filesystem with 1310720 4k blocks and 327680 inodes
Filesystem UUID: b0acbfbc-106d-41aa-9446-b26182841ac8
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done
</syntaxhighlight>

Mount the file system. This is done by first creating a directory to mount the file and then mounting the file.

<syntaxhighlight lang="shell">
sudo mkdir /mnt/iscsi
sudo mount /dev/sdb /mnt/iscsi
</syntaxhighlight>

- Verify the file system has been mounted:

<syntaxhighlight lang="shell">
$ df -hT
Filesystem Type Size Used Avail Use% Mounted on
devtmpfs devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs tmpfs 3.8G 0 3.8G 0% /dev/shm
tmpfs tmpfs 1.6G 9.2M 1.5G 1% /run
/dev/mapper/cs-root xfs 28G 4.6G 24G 17% /
/dev/sda1 xfs 1014M 466M 549M 46% /boot
tmpfs tmpfs 769M 96K 768M 1% /run/user/1000
/dev/sr0 iso9660 8.2G 8.2G 0 100% /run/media/technixleo/CentOS-Stream-9-BaseOS-x86_64
/dev/sdb ext4 4.9G 24K 4.6G 1% /mnt/iscsi
</syntaxhighlight>

=Automount ISCSI storage=

To make the file persistent even on boot, edit the fstab file. But first Identify the UUID of the ISCSI disk.
$ sudo blkid /dev/sdb
/dev/sdb: UUID="b0acbfbc-106d-41aa-9446-b26182841ac8" BLOCK_SIZE="4096" TYPE="ext4"

- Open the fstab file and add the UUID of the ISCSI disk.

<syntaxhighlight lang="shell">
$ sudo vi /etc/fstab
UUID=b0acbfbc-106d-41aa-9446-b26182841ac8 /mnt/iscsi ext4 _netdev 0 0
</syntaxhighlight>

- Save and exit the file.

You can verify the disk has been mounted.
$ mount
....
/dev/sdb on /mnt/iscsi type ext4 (rw,relatime,seclabel,stripe=2048)

To unmount a disk

sudo umount /mnt/iscsi

To log out of a session, use the following command.

<syntaxhighlight lang="shell">
$ sudo iscsiadm -m node -T iqn.2022-06.com.redhat:technixleo -u
Logging out of session [sid: 1, target: iqn.2022-06.com.redhat:technixleo, portal: 192.168.200.40,3260]
Logout of [sid: 1, target: iqn.2022-06.com.redhat:technixleo, portal: 192.168.200.40,3260] successful.
</syntaxhighlight>

DOCS/UNIX/RHEL/ISCSI/Config iSCSI Initiator

2022-08-31T08:32:37Z

Admin : Page créée avec « {{MediaWiki}} {{FOND_BLEU|QEMU - '''Configure iSCSI Initiator on CentOS 9|AlmaLinux 9|RHEL 9'''}} = Sites Références = Cet article est une transposition sous MediaWiki… »

{{MediaWiki}}
{{FOND_BLEU|QEMU - '''Configure iSCSI Initiator on CentOS 9|AlmaLinux 9|RHEL 9'''}}

= Sites Références =

Cet article est une transposition sous MediaWiki de ces 2 adresses :
* [https://technixleo.com/configure-iscsi-target-on-centos-alma-rhel/ Configure iSCSI Target on CentOS 9|AlmaLinux 9|RHEL 9]
* [https://technixleo.com/iscsi-initiator-centos-alma-rhel/ Configure iSCSI Initiator on CentOS 9|AlmaLinux 9|RHEL 9]

iSCSI is an acronym that stands for Internet Small Computer Systems Interface. It is a Storage Area Network (SAN) Protocol that enables block-level SCSI data transport from Storage arrays to client computers that are not directly connected to them. iSCSI SAN consists of iSCSI Initiators which are the clients and iSCSI targets which are the servers on Storage Array controllers. They are connected by an iSCSI protocol and represented by a unique string known as iSCSI Qualified Name (iQN).

In iSCSI technology, the iSCSI initiator or commonly known as the iSCSI client needs to be installed on your system. It is then added to an initiator group or what is also known as the Client definition. These groups help identify which clients are allowed to connect with the storage server (the iSCSI targets). Logical Unit Numbers (LUNs) are created and assigned to a group or client definition. LUNs are representations of devices that are part of the physical iSCSI target. If the Client and server are on the same IP network, The initiator can automatically discover the target. Once connected, the LUN is available for use.

=iSCSI Initiator=

=Setup pre-reqs=
An IP of the Target needs to be known. I will use the iSCSI target from the [[DOCS/UNIX/RHEL/ISCSI/Config_iSCSI_Target|Configure iSCSI target]] guide. You can also follow the steps in that guide to create a target.

=Configure iSCSI Initiator on CentOS 9|AlmaLinux 9|RHEL 9 systems=
- Update your system packages.
sudo yum update -y
or
sudo dnf update -y

- Install iSCSI initiator utilities with the following command.
sudo dnf -y install iscsi-initiator-utils

- Check the initiator name using the following command

<syntaxhighlight lang="shell">
$ cat /etc/iscsi/initiatorname.iscsi
InitiatorName=iqn.1994-05.com.redhat:4e8ff68af729
</syntaxhighlight>

If you changed the name while setting up iSCSI target ACLs. You will have to configure the initiator file to the new name.
sudo vi /etc/iscsi/initiatorname.iscsi

- Change the initiator’s name to match the one set on the target server.
InitiatorName=iqn.1994-05.com.redhat:4e8ff68af729

- Save and exit the file.
- [OPTIONAL] Edit the iSCSI configuration file to add the authentication details.
sudo vi /etc/iscsi/iscsid.conf
- Uncomment the following lines and edit as shown.

<syntaxhighlight lang="shell">
node.session.auth.authmethod = CHAP
node.session.auth.username = technix
node.session.auth.password = technix_passwd
</syntaxhighlight>

- Save and exit the file, then start the iSCSI daemon.

<syntaxhighlight lang="shell">
sudo systemctl start iscsid.service
sudo systemctl enable iscsid.service
</syntaxhighlight>

- Discover the target by using the target’s IP address as shown below. The response will be the target’s IP address and iQN address.

<syntaxhighlight lang="shell">
$ sudo iscsiadm -m discovery -t st -p 192.168.200.40
192.168.200.40:3260,1 iqn.2022-06.com.redhat:technixleo
</syntaxhighlight>

- Confirm its status after discovery.

<syntaxhighlight lang="shell">
$ sudo iscsiadm -m node -o show

##Sample Outpout ##
# BEGIN RECORD 2.1.4
node.name = iqn.2022-06.com.redhat:technixleo
node.tpgt = 1
node.startup = automatic
node.leading_login = No
iface.iscsi_ifacename = default
.....
.....
</syntaxhighlight>

- You can log in to the server using the iQN

<syntaxhighlight lang="shell">
$ sudo iscsiadm -m node -T iqn.2022-06.com.redhat:technixleo -l
Logging in to [iface: default, target: iqn.2022-06.com.redhat:technixleo, portal: 192.168.200.40,3260]
Login to [iface: default, target: iqn.2022-06.com.redhat:technixleo, portal: 192.168.200.40,3260] successful.
</syntaxhighlight>

- Confirm the established session.

<syntaxhighlight lang="shell">
$ sudo iscsiadm -m session -o show
tcp: [2] 192.168.200.40:3260,1 iqn.2022-06.com.redhat:technixleo (non-flash)
</syntaxhighlight>

- Confirm the partitions with the following command.

<syntaxhighlight lang="shell">
$ cat /proc/partitions

major minor #blocks name

8 0 33554432 sda
8 1 1048576 sda1
8 2 32504832 sda2
11 0 8519680 sr0
253 0 29143040 dm-0
253 1 3358720 dm-1
''8 16 5242880 sdb''
8 32 33554432 sdc
</syntaxhighlight>

The new partition ‘sdb‘ of size 5GB has been added from the target server.
To find the iSCSI disk name you can also use the following command.

$ sudo grep "Attached SCSI" /var/log/messages
Jul 30 10:30:02 cent9 kernel: sd 3:0:0:0: [sdb] Attached SCSI disk

Next, we are going to create a file on that disk.
<syntaxhighlight lang="shell">
$ sudo mkfs.ext4 /dev/sdb
Creating filesystem with 1310720 4k blocks and 327680 inodes
Filesystem UUID: b0acbfbc-106d-41aa-9446-b26182841ac8
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done
</syntaxhighlight>

Mount the file system. This is done by first creating a directory to mount the file and then mounting the file.

<syntaxhighlight lang="shell">
sudo mkdir /mnt/iscsi
sudo mount /dev/sdb /mnt/iscsi
</syntaxhighlight>

- Verify the file system has been mounted:

<syntaxhighlight lang="shell">
$ df -hT
Filesystem Type Size Used Avail Use% Mounted on
devtmpfs devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs tmpfs 3.8G 0 3.8G 0% /dev/shm
tmpfs tmpfs 1.6G 9.2M 1.5G 1% /run
/dev/mapper/cs-root xfs 28G 4.6G 24G 17% /
/dev/sda1 xfs 1014M 466M 549M 46% /boot
tmpfs tmpfs 769M 96K 768M 1% /run/user/1000
/dev/sr0 iso9660 8.2G 8.2G 0 100% /run/media/technixleo/CentOS-Stream-9-BaseOS-x86_64
/dev/sdb ext4 4.9G 24K 4.6G 1% /mnt/iscsi
</syntaxhighlight>

=Automount ISCSI storage=

To make the file persistent even on boot, edit the fstab file. But first Identify the UUID of the ISCSI disk.
$ sudo blkid /dev/sdb
/dev/sdb: UUID="b0acbfbc-106d-41aa-9446-b26182841ac8" BLOCK_SIZE="4096" TYPE="ext4"

- Open the fstab file and add the UUID of the ISCSI disk.

<syntaxhighlight lang="shell">
$ sudo vi /etc/fstab
UUID=b0acbfbc-106d-41aa-9446-b26182841ac8 /mnt/iscsi ext4 _netdev 0 0
</syntaxhighlight>

- Save and exit the file.

You can verify the disk has been mounted.
$ mount
....
/dev/sdb on /mnt/iscsi type ext4 (rw,relatime,seclabel,stripe=2048)

To unmount a disk

sudo umount /mnt/iscsi

To log out of a session, use the following command.

<syntaxhighlight lang="shell">
$ sudo iscsiadm -m node -T iqn.2022-06.com.redhat:technixleo -u
Logging out of session [sid: 1, target: iqn.2022-06.com.redhat:technixleo, portal: 192.168.200.40,3260]
Logout of [sid: 1, target: iqn.2022-06.com.redhat:technixleo, portal: 192.168.200.40,3260] successful.
</syntaxhighlight>

DOCS/UNIX/RHEL/ISCSI/Config iSCSI Target

2022-08-31T08:15:57Z

Admin : /* Sites Références */

{{MediaWiki}}
{{FOND_BLEU|QEMU - '''Configure iSCSI Target on CentOS 9/AlmaLinux 9/RHEL 9'''}}

= Sites Références =

Cet article est une transposition sous MediaWiki de ces 2 adresses :
* [https://technixleo.com/configure-iscsi-target-on-centos-alma-rhel/ Configure iSCSI Target on CentOS 9|AlmaLinux 9|RHEL 9]
* [https://technixleo.com/iscsi-initiator-centos-alma-rhel/ Configure iSCSI Initiator on CentOS 9|AlmaLinux 9|RHEL 9]

iSCSI stands for Internet Small Computer Systems Interface. It is an Internet Protocol that allows multiple servers and users to access network drives remotely over a TCP/IP network by setting up a shared storage network. iSCSI components include the iSCSI target which is the server that stores and allows access to storage and iSCSI initiator which is the hardware installed on a client to send data. A basic Ethernet port or a Host Bus Adapter (HBA) is what is required to connect iSCSI targets and initiators to a network. Both components are identified by a unique name known as iSCSI Qulified Name (iQN).

=What is iSCSI Target?=
iSCSI target as discussed above is the server that stores the storage and allows access to it. It can be a dedicated physical device on a network or an iSCSI software-configured logical device on a networked storage server. It is the remote storage that appears as a local drive on a host system. The iSCSI protocol then links the host with the storage over IP networks like LAN and WAN or Internet.

This guide shows how to configure an iSCSI Target on CentOS 9|AlmaLinux 9|RHEL 9 systems.

=Install iSCSI Target on CentOS 9|AlmaLinux 9|RHEL 9=

- Update the system packages.
sudo yum update -y
or
sudo dnf update -y

- Install the targetcli tool

sudo dnf install targetcli

- Start and enable the target service on boot time.

sudo systemctl enable --now target

- Open port 3260 in the firewall.

sudo firewall-cmd --permanent --add-port=3260/tcp
sudo firewall-cmd --reload

- To view the targetcli layout, login to the admin console.

<syntaxhighlight lang="shell">
$ sudo targetcli
targetcli shell version 2.1.53
Copyright 2011-2013 by Datera, Inc and others.
For help on commands, type 'help'.

/>
</syntaxhighlight>

- List using the following command

<syntaxhighlight lang="shell">
> ls
o- / ..................................................................... [...]
o- backstores .......................................................... [...]
| o- block .............................................. [Storage Objects: 0]
| o- fileio ............................................. [Storage Objects: 0]
| o- pscsi .............................................. [Storage Objects: 0]
| o- ramdisk ............................................ [Storage Objects: 0]
o- iscsi ........................................................ [Targets: 0]
o- loopback ..................................................... [Targets: 0]
</syntaxhighlight>

- Exit the shell using the following command.

<syntaxhighlight lang="shell">
/> exit
Global pref auto_save_on_exit=true
Configuration saved to /etc/target/saveconfig.json
</syntaxhighlight>

=Configure iSCSI Target on CentOS 9|AlmaLinux 9|RHEL 9=
To configure an iSCSI Target, we will use the following details

* iSCSI target with a unique iQN.
* iSCSI Backstore – is a storage object that defines the resources that the backstore uses.
* Create iSCSI Portal.
* Setup iSCSI LUN.
* Creating an iSCSI ACL.
* Setup CHAP Authentication.

==Create an iSCSI target==

The target name is in the iQN format. iQN format is as follows <code>iqn.YYYY-MM.reverse.domain.name:OptionalIdentifier</code>. Let’s say I was to name a target with an iQN unique string with the name technixleo and my domain is target.example.com the iqn name will be as <code>iqn.2022-06.com.example.target:technixleo</code>
- Login to the admin console of the target CLI shell.
<syntaxhighlight lang="shell">
sudo targetcli
</syntaxhighlight>
- Navigate to the iSCSI directory
<syntaxhighlight lang="shell">
/> cd iscsi/
</syntaxhighlight>

- Create the iSCSI target as shown below.
<syntaxhighlight lang="shell">
/iscsi> create iqn.2022-06.com.example.target:technixleo

Created target iqn.2022-06.com.example.target:technixleo.
Created TPG 1.
Global pref auto_add_default_portal=true
Created default portal listening on all IPs (0.0.0.0), port 3260.
</syntaxhighlight>

- Then verify the created target.
<syntaxhighlight lang="shell">
/iscsi> ls

o- iscsi .......................................................... [Targets: 1]
o- iqn.2022-06.com.example.target:technixleo ....................... [TPGs: 1]
o- tpg1 ............................................. [no-gen-acls, no-auth]
o- acls ........................................................ [ACLs: 0]
o- luns ........................................................ [LUNs: 0]
o- portals .................................................. [Portals: 1]
o- 0.0.0.0:3260 ................................................... [OK]
</syntaxhighlight>

==Create iSCSI Backstore==

You can create backstore devices of any of the following 4 types

*fileio backstore for files
*block backstore for block devices.
*pscsi backstore for direct pass-through of SCSI commands.
*ramdisk backstore for a temporary RAM-backed device.

For this guide, I will create one for fileio and block backstores

<syntaxhighlight lang="shell">
</syntaxhighlight>

===Create fileio storage object===

-Navigate to the fileio on the backstore directory. The backstore is the device where the storage is located.

<syntaxhighlight lang="shell">
/> cd /backstores/fileio
</syntaxhighlight>

- Create a file storage object named disk1 in a directory say /tmp/disk1.img of size 5GB. You can create a different directory to store the disk.
<syntaxhighlight lang="shell">
/backstores/fileio> create disk1 /tmp/disk1.img 5G
Created fileio disk1 with size 5368709120
</syntaxhighlight>

- Verify the created storage object

<syntaxhighlight lang="shell">
/backstores/fileio> ls

o- fileio ................................................. [Storage Objects: 1]
o- disk1 .................... [/tmp/disk1.img (5.0GiB) write-back deactivated]
o- alua ................................................... [ALUA Groups: 1]
o- default_tg_pt_gp ....................... [ALUA state: Active/optimized]
</syntaxhighlight>

===Create a block storage object===
Block devices include physical devices like HDDs, SSDs, CDs, and DVDs, and logical devices such as software or hardware RAID volumes, or LVM volumes.

- Navigate to the block of the backstores directory
<syntaxhighlight lang="shell">
/> cd /backstores/block
</syntaxhighlight>

- Create a block storage object with the following command. Use a disk that is not in use.
<syntaxhighlight lang="shell">
/backstores/block> create name=block1 dev=/dev/vdb
Created block storage object block1 using /dev/vdb.
</syntaxhighlight>

- Verify the created block storage.

<syntaxhighlight lang="shell">
/backstores/block> ls
o- block .................................................. [Storage Objects: 1]
o- block1 ........................ [/dev/vdb (10.0GiB) write-thru deactivated]
o- alua ................................................... [ALUA Groups: 1]
o- default_tg_pt_gp ....................... [ALUA state: Active/optimized]
</syntaxhighlight>

==Creating an iSCSI Portal==

An iSCSI Portal adds an IP address and a port to the target that keeps the target enabled.

- Navigate to the Portals directory.
<syntaxhighlight lang="shell">
/> cd /iscsi/iqn.2022-06.com.example.target:technixleo/tpg1/portals
</syntaxhighlight>

By default, The iSCSI portal is set to listen to all IP addresses with the default port number that is: 0.0.0.0:3260. Delete the default portal with the following command

<syntaxhighlight lang="shell">
/iscsi/iqn.20.../tpg1/portals> delete ip_address=0.0.0.0 ip_port=3260
Deleted network portal 0.0.0.0:3260
</syntaxhighlight>

- Then create the new portal and specify the IP address to enable the target.
<syntaxhighlight lang="shell">
/iscsi/iqn.20.../tpg1/portals> create 192.168.200.47
Using default IP port 3260
Created network portal 192.168.200.47:3260.
</syntaxhighlight>

- Verify the portal created.
<syntaxhighlight lang="shell">
/iscsi/iqn.20.../tpg1/portals> ls
o- portals ........................................................ [Portals: 1]
o- 192.168.200.47:3260 .................................................. [OK]
</syntaxhighlight>

==Creating an iSCSI LUN==
- Create LUN of the create storage object above. Navigate to the iSCSI target directory.
<syntaxhighlight lang="shell">
/> cd /iscsi/iqn.2022-06.com.example.target:technixleo/tpg1/luns
</syntaxhighlight>
- Set the LUN for the created backstores with the following commands.
<syntaxhighlight lang="shell">
/iscsi/iqn.20...leo/tpg1/luns> create /backstores/fileio/disk1
Created LUN 0.

/iscsi/iqn.20...leo/tpg1/luns> create /backstores/block/block1
Created LUN 1.
</syntaxhighlight>

- Verify the creates LUN
<syntaxhighlight lang="shell">
/> ls
o- luns .............................................................. [LUNs: 2]
o- lun0 ................... [fileio/disk1 (/tmp/disk1.img) (default_tg_pt_gp)]
o- lun1 ......................... [block/block1 (/dev/vdb) (default_tg_pt_gp)]
</syntaxhighlight>

==Creating an iSCSI ACL==

Access Control Lists are used to configure access rules that each initiator has access to LUNs. To configure an ACL you should have the unique identifier for an initiator.

If you have installed an initiator, you can check its name with the following command on the client machine. I am using the initiator name installed on my client machine on the [[DOCS/UNIX/RHEL/ISCSI/Config_iSCSI_Initiator|Configure an iSCSI Initiator]] guide.

<syntaxhighlight lang="shell">
$ cat /etc/iscsi/initiatorname.iscsi
InitiatorName=iqn.1994-05.com.redhat:1cf224abfeb
</syntaxhighlight>

- Once you have the initiator name, navigate to your iSCSI target and then to the ACL directory

<syntaxhighlight lang="shell">
/> cd /iscsi/iqn.2022-06.com.example.target:technixleo/tpg1/acls
</syntaxhighlight>

- Then create an ACL using the initiator name.

<syntaxhighlight lang="shell">
/iscsi/iqn.20...leo/tpg1/acls> create <initiator name>
</syntaxhighlight>

You can create an initiator name that is easy to remember with the iQN format as shown below. You will also have to change the initiator name on the client machine to match.

<syntaxhighlight lang="shell">
/iscsi/iqn.20...leo/tpg1/acls> create iqn.2022-06.com.example.initiator:initiator1
Created Node ACL for iqn.2022-06.com.example.initiator:initiator1
Created mapped LUN 0
</syntaxhighlight>

- Set the user-created ACL within the TPG node on the target server.
/iscsi/iqn.20...leo/tpg1> set attribute generate_node_acls=1
Parameter generate_node_acls is now '1'.

- Verify the created ACL.

<syntaxhighlight lang="shell">
/iscsi/iqn.20...leo/tpg1/acls> ls
o- acls .............................................................. [ACLs: 1]
o- iqn.2022-06.com.example.initiator:initiator1 ............. [Mapped LUNs: 1]
o- mapped_lun0 .................................... [lun0 fileio/disk1 (rw)]
</syntaxhighlight>

==Setup CHAP for the target==

You can use the Challenge-Handshake Authentication Protocol (CHAP) to protect the target server with a password. The initiator should also be configured with the password to be able to connect to the target.

- Set the attribute authentication with the following command.
/iscsi/iqn.20...leo/tpg1> set attribute authentication=1
Parameter authentication is now '1'.

- Change directory to the newly created initiator.
/iscsi/iqn.20...leo/tpg1/acls> cd iqn.2022-06.com.example.initiator:initiator1

- Then set the user-id and Password.
<syntaxhighlight lang="shell">
/iscsi/iqn.20...or:initiator1> set auth userid=technix
Parameter userid is now 'technix'.

/iscsi/iqn.20...or:initiator1> set auth password=technix_passwd
Parameter password is now 'technix_passwd'.
</syntaxhighlight>

- Exit the shell.

<syntaxhighlight lang="shell">
/iscsi/iqn.20...or:initiator1> exit
lobal pref auto_save_on_exit=true
Configuration saved to /etc/target/saveconfig.json
</syntaxhighlight>

- Check where the target port is listening using the following command
<syntaxhighlight lang="shell">
$ netstat -tnlp | grep 3260
tcp 0 0 192.168.200.47:3260 0.0.0.0:* LISTEN
</syntaxhighlight>

Next read through our guide on how to configure iSCSI Initiator:

[[DOCS/UNIX/RHEL/ISCSI/Config_iSCSI_Initiator|Configure an iSCSI Initiator on CentOS 9/AlmaLinux 9/RHEL 9]]
<syntaxhighlight lang="shell">
</syntaxhighlight>

DOCS/UNIX/RHEL/ISCSI/Config iSCSI Target

2022-08-31T08:15:16Z

Admin : /* Setup CHAP for the target */

{{MediaWiki}}
{{FOND_BLEU|QEMU - '''Configure iSCSI Target on CentOS 9/AlmaLinux 9/RHEL 9'''}}

= Sites Références =

Cet articles est une transposition sous MediaWiki de ces adresses :
* [https://technixleo.com/configure-iscsi-target-on-centos-alma-rhel/ Configure iSCSI Target on CentOS 9|AlmaLinux 9|RHEL 9]
* [https://technixleo.com/iscsi-initiator-centos-alma-rhel/ Configure iSCSI Initiator on CentOS 9|AlmaLinux 9|RHEL 9]

iSCSI stands for Internet Small Computer Systems Interface. It is an Internet Protocol that allows multiple servers and users to access network drives remotely over a TCP/IP network by setting up a shared storage network. iSCSI components include the iSCSI target which is the server that stores and allows access to storage and iSCSI initiator which is the hardware installed on a client to send data. A basic Ethernet port or a Host Bus Adapter (HBA) is what is required to connect iSCSI targets and initiators to a network. Both components are identified by a unique name known as iSCSI Qulified Name (iQN).

=What is iSCSI Target?=
iSCSI target as discussed above is the server that stores the storage and allows access to it. It can be a dedicated physical device on a network or an iSCSI software-configured logical device on a networked storage server. It is the remote storage that appears as a local drive on a host system. The iSCSI protocol then links the host with the storage over IP networks like LAN and WAN or Internet.

This guide shows how to configure an iSCSI Target on CentOS 9|AlmaLinux 9|RHEL 9 systems.

=Install iSCSI Target on CentOS 9|AlmaLinux 9|RHEL 9=

- Update the system packages.
sudo yum update -y
or
sudo dnf update -y

- Install the targetcli tool

sudo dnf install targetcli

- Start and enable the target service on boot time.

sudo systemctl enable --now target

- Open port 3260 in the firewall.

sudo firewall-cmd --permanent --add-port=3260/tcp
sudo firewall-cmd --reload

- To view the targetcli layout, login to the admin console.

<syntaxhighlight lang="shell">
$ sudo targetcli
targetcli shell version 2.1.53
Copyright 2011-2013 by Datera, Inc and others.
For help on commands, type 'help'.

/>
</syntaxhighlight>

- List using the following command

<syntaxhighlight lang="shell">
> ls
o- / ..................................................................... [...]
o- backstores .......................................................... [...]
| o- block .............................................. [Storage Objects: 0]
| o- fileio ............................................. [Storage Objects: 0]
| o- pscsi .............................................. [Storage Objects: 0]
| o- ramdisk ............................................ [Storage Objects: 0]
o- iscsi ........................................................ [Targets: 0]
o- loopback ..................................................... [Targets: 0]
</syntaxhighlight>

- Exit the shell using the following command.

<syntaxhighlight lang="shell">
/> exit
Global pref auto_save_on_exit=true
Configuration saved to /etc/target/saveconfig.json
</syntaxhighlight>

=Configure iSCSI Target on CentOS 9|AlmaLinux 9|RHEL 9=
To configure an iSCSI Target, we will use the following details

* iSCSI target with a unique iQN.
* iSCSI Backstore – is a storage object that defines the resources that the backstore uses.
* Create iSCSI Portal.
* Setup iSCSI LUN.
* Creating an iSCSI ACL.
* Setup CHAP Authentication.

==Create an iSCSI target==

The target name is in the iQN format. iQN format is as follows <code>iqn.YYYY-MM.reverse.domain.name:OptionalIdentifier</code>. Let’s say I was to name a target with an iQN unique string with the name technixleo and my domain is target.example.com the iqn name will be as <code>iqn.2022-06.com.example.target:technixleo</code>
- Login to the admin console of the target CLI shell.
<syntaxhighlight lang="shell">
sudo targetcli
</syntaxhighlight>
- Navigate to the iSCSI directory
<syntaxhighlight lang="shell">
/> cd iscsi/
</syntaxhighlight>

- Create the iSCSI target as shown below.
<syntaxhighlight lang="shell">
/iscsi> create iqn.2022-06.com.example.target:technixleo

Created target iqn.2022-06.com.example.target:technixleo.
Created TPG 1.
Global pref auto_add_default_portal=true
Created default portal listening on all IPs (0.0.0.0), port 3260.
</syntaxhighlight>

- Then verify the created target.
<syntaxhighlight lang="shell">
/iscsi> ls

o- iscsi .......................................................... [Targets: 1]
o- iqn.2022-06.com.example.target:technixleo ....................... [TPGs: 1]
o- tpg1 ............................................. [no-gen-acls, no-auth]
o- acls ........................................................ [ACLs: 0]
o- luns ........................................................ [LUNs: 0]
o- portals .................................................. [Portals: 1]
o- 0.0.0.0:3260 ................................................... [OK]
</syntaxhighlight>

==Create iSCSI Backstore==

You can create backstore devices of any of the following 4 types

*fileio backstore for files
*block backstore for block devices.
*pscsi backstore for direct pass-through of SCSI commands.
*ramdisk backstore for a temporary RAM-backed device.

For this guide, I will create one for fileio and block backstores

<syntaxhighlight lang="shell">
</syntaxhighlight>

===Create fileio storage object===

-Navigate to the fileio on the backstore directory. The backstore is the device where the storage is located.

<syntaxhighlight lang="shell">
/> cd /backstores/fileio
</syntaxhighlight>

- Create a file storage object named disk1 in a directory say /tmp/disk1.img of size 5GB. You can create a different directory to store the disk.
<syntaxhighlight lang="shell">
/backstores/fileio> create disk1 /tmp/disk1.img 5G
Created fileio disk1 with size 5368709120
</syntaxhighlight>

- Verify the created storage object

<syntaxhighlight lang="shell">
/backstores/fileio> ls

o- fileio ................................................. [Storage Objects: 1]
o- disk1 .................... [/tmp/disk1.img (5.0GiB) write-back deactivated]
o- alua ................................................... [ALUA Groups: 1]
o- default_tg_pt_gp ....................... [ALUA state: Active/optimized]
</syntaxhighlight>

===Create a block storage object===
Block devices include physical devices like HDDs, SSDs, CDs, and DVDs, and logical devices such as software or hardware RAID volumes, or LVM volumes.

- Navigate to the block of the backstores directory
<syntaxhighlight lang="shell">
/> cd /backstores/block
</syntaxhighlight>

- Create a block storage object with the following command. Use a disk that is not in use.
<syntaxhighlight lang="shell">
/backstores/block> create name=block1 dev=/dev/vdb
Created block storage object block1 using /dev/vdb.
</syntaxhighlight>

- Verify the created block storage.

<syntaxhighlight lang="shell">
/backstores/block> ls
o- block .................................................. [Storage Objects: 1]
o- block1 ........................ [/dev/vdb (10.0GiB) write-thru deactivated]
o- alua ................................................... [ALUA Groups: 1]
o- default_tg_pt_gp ....................... [ALUA state: Active/optimized]
</syntaxhighlight>

==Creating an iSCSI Portal==

An iSCSI Portal adds an IP address and a port to the target that keeps the target enabled.

- Navigate to the Portals directory.
<syntaxhighlight lang="shell">
/> cd /iscsi/iqn.2022-06.com.example.target:technixleo/tpg1/portals
</syntaxhighlight>

By default, The iSCSI portal is set to listen to all IP addresses with the default port number that is: 0.0.0.0:3260. Delete the default portal with the following command

<syntaxhighlight lang="shell">
/iscsi/iqn.20.../tpg1/portals> delete ip_address=0.0.0.0 ip_port=3260
Deleted network portal 0.0.0.0:3260
</syntaxhighlight>

- Then create the new portal and specify the IP address to enable the target.
<syntaxhighlight lang="shell">
/iscsi/iqn.20.../tpg1/portals> create 192.168.200.47
Using default IP port 3260
Created network portal 192.168.200.47:3260.
</syntaxhighlight>

- Verify the portal created.
<syntaxhighlight lang="shell">
/iscsi/iqn.20.../tpg1/portals> ls
o- portals ........................................................ [Portals: 1]
o- 192.168.200.47:3260 .................................................. [OK]
</syntaxhighlight>

==Creating an iSCSI LUN==
- Create LUN of the create storage object above. Navigate to the iSCSI target directory.
<syntaxhighlight lang="shell">
/> cd /iscsi/iqn.2022-06.com.example.target:technixleo/tpg1/luns
</syntaxhighlight>
- Set the LUN for the created backstores with the following commands.
<syntaxhighlight lang="shell">
/iscsi/iqn.20...leo/tpg1/luns> create /backstores/fileio/disk1
Created LUN 0.

/iscsi/iqn.20...leo/tpg1/luns> create /backstores/block/block1
Created LUN 1.
</syntaxhighlight>

- Verify the creates LUN
<syntaxhighlight lang="shell">
/> ls
o- luns .............................................................. [LUNs: 2]
o- lun0 ................... [fileio/disk1 (/tmp/disk1.img) (default_tg_pt_gp)]
o- lun1 ......................... [block/block1 (/dev/vdb) (default_tg_pt_gp)]
</syntaxhighlight>

==Creating an iSCSI ACL==

Access Control Lists are used to configure access rules that each initiator has access to LUNs. To configure an ACL you should have the unique identifier for an initiator.

If you have installed an initiator, you can check its name with the following command on the client machine. I am using the initiator name installed on my client machine on the [[DOCS/UNIX/RHEL/ISCSI/Config_iSCSI_Initiator|Configure an iSCSI Initiator]] guide.

<syntaxhighlight lang="shell">
$ cat /etc/iscsi/initiatorname.iscsi
InitiatorName=iqn.1994-05.com.redhat:1cf224abfeb
</syntaxhighlight>

- Once you have the initiator name, navigate to your iSCSI target and then to the ACL directory

<syntaxhighlight lang="shell">
/> cd /iscsi/iqn.2022-06.com.example.target:technixleo/tpg1/acls
</syntaxhighlight>

- Then create an ACL using the initiator name.

<syntaxhighlight lang="shell">
/iscsi/iqn.20...leo/tpg1/acls> create <initiator name>
</syntaxhighlight>

You can create an initiator name that is easy to remember with the iQN format as shown below. You will also have to change the initiator name on the client machine to match.

<syntaxhighlight lang="shell">
/iscsi/iqn.20...leo/tpg1/acls> create iqn.2022-06.com.example.initiator:initiator1
Created Node ACL for iqn.2022-06.com.example.initiator:initiator1
Created mapped LUN 0
</syntaxhighlight>

- Set the user-created ACL within the TPG node on the target server.
/iscsi/iqn.20...leo/tpg1> set attribute generate_node_acls=1
Parameter generate_node_acls is now '1'.

- Verify the created ACL.

<syntaxhighlight lang="shell">
/iscsi/iqn.20...leo/tpg1/acls> ls
o- acls .............................................................. [ACLs: 1]
o- iqn.2022-06.com.example.initiator:initiator1 ............. [Mapped LUNs: 1]
o- mapped_lun0 .................................... [lun0 fileio/disk1 (rw)]
</syntaxhighlight>

==Setup CHAP for the target==

You can use the Challenge-Handshake Authentication Protocol (CHAP) to protect the target server with a password. The initiator should also be configured with the password to be able to connect to the target.

- Set the attribute authentication with the following command.
/iscsi/iqn.20...leo/tpg1> set attribute authentication=1
Parameter authentication is now '1'.

- Change directory to the newly created initiator.
/iscsi/iqn.20...leo/tpg1/acls> cd iqn.2022-06.com.example.initiator:initiator1

- Then set the user-id and Password.
<syntaxhighlight lang="shell">
/iscsi/iqn.20...or:initiator1> set auth userid=technix
Parameter userid is now 'technix'.

/iscsi/iqn.20...or:initiator1> set auth password=technix_passwd
Parameter password is now 'technix_passwd'.
</syntaxhighlight>

- Exit the shell.

<syntaxhighlight lang="shell">
/iscsi/iqn.20...or:initiator1> exit
lobal pref auto_save_on_exit=true
Configuration saved to /etc/target/saveconfig.json
</syntaxhighlight>

- Check where the target port is listening using the following command
<syntaxhighlight lang="shell">
$ netstat -tnlp | grep 3260
tcp 0 0 192.168.200.47:3260 0.0.0.0:* LISTEN
</syntaxhighlight>

Next read through our guide on how to configure iSCSI Initiator:

[[DOCS/UNIX/RHEL/ISCSI/Config_iSCSI_Initiator|Configure an iSCSI Initiator on CentOS 9/AlmaLinux 9/RHEL 9]]
<syntaxhighlight lang="shell">
</syntaxhighlight>

DOCS/UNIX/RHEL/ISCSI/Config iSCSI Target

2022-08-31T08:12:00Z

Admin : /* Creating an iSCSI ACL */

DOCS/UNIX/RHEL

2022-08-31T08:09:10Z

Admin : /* Stockage */

{{MediaWiki}}

{{FOND_BLEU|Bonnes pratiques d'administration d'un Système Linux Redhat/Centos/AlmaLinux 8/9}}

=Réseau=
==Bonding/Bridges/VLAN==
* [[Virtualisation/KVM/Bridges_bond_vlans| Configurer des bridges et des VLANs utilisables pour KVM/QEMU]]
=Stockage=
* [[DOCS/UNIX/RHEL/ISCSI/Config_iSCSI_Target|Configure iSCSI Target on CentOS 9/AlmaLinux 9/RHEL 9]]
* [[DOCS/UNIX/RHEL/ISCSI/Config_iSCSI_Initiator|Configure iSCSI Initiator on CentOS 9/AlmaLinux 9:RHEL 9]]

=Mises à jour OS=

DOCS/UNIX/RHEL/ISCSI/Config iSCSI Target

2022-08-31T08:07:06Z

Admin : /* Creating an iSCSI LUN */

{{MediaWiki}}
{{FOND_BLEU|QEMU - '''Configure iSCSI Target on CentOS 9/AlmaLinux 9/RHEL 9'''}}

= Sites Références =

Cet articles est une transposition sous MediaWiki de ces adresses :
* [https://technixleo.com/configure-iscsi-target-on-centos-alma-rhel/ Configure iSCSI Target on CentOS 9|AlmaLinux 9|RHEL 9]
* [https://technixleo.com/iscsi-initiator-centos-alma-rhel/ Configure iSCSI Initiator on CentOS 9|AlmaLinux 9|RHEL 9]

iSCSI stands for Internet Small Computer Systems Interface. It is an Internet Protocol that allows multiple servers and users to access network drives remotely over a TCP/IP network by setting up a shared storage network. iSCSI components include the iSCSI target which is the server that stores and allows access to storage and iSCSI initiator which is the hardware installed on a client to send data. A basic Ethernet port or a Host Bus Adapter (HBA) is what is required to connect iSCSI targets and initiators to a network. Both components are identified by a unique name known as iSCSI Qulified Name (iQN).

=What is iSCSI Target?=
iSCSI target as discussed above is the server that stores the storage and allows access to it. It can be a dedicated physical device on a network or an iSCSI software-configured logical device on a networked storage server. It is the remote storage that appears as a local drive on a host system. The iSCSI protocol then links the host with the storage over IP networks like LAN and WAN or Internet.

This guide shows how to configure an iSCSI Target on CentOS 9|AlmaLinux 9|RHEL 9 systems.

=Install iSCSI Target on CentOS 9|AlmaLinux 9|RHEL 9=

- Update the system packages.
sudo yum update -y
or
sudo dnf update -y

- Install the targetcli tool

sudo dnf install targetcli

- Start and enable the target service on boot time.

sudo systemctl enable --now target

- Open port 3260 in the firewall.

sudo firewall-cmd --permanent --add-port=3260/tcp
sudo firewall-cmd --reload

- To view the targetcli layout, login to the admin console.

<syntaxhighlight lang="shell">
$ sudo targetcli
targetcli shell version 2.1.53
Copyright 2011-2013 by Datera, Inc and others.
For help on commands, type 'help'.

/>
</syntaxhighlight>

- List using the following command

<syntaxhighlight lang="shell">
> ls
o- / ..................................................................... [...]
o- backstores .......................................................... [...]
| o- block .............................................. [Storage Objects: 0]
| o- fileio ............................................. [Storage Objects: 0]
| o- pscsi .............................................. [Storage Objects: 0]
| o- ramdisk ............................................ [Storage Objects: 0]
o- iscsi ........................................................ [Targets: 0]
o- loopback ..................................................... [Targets: 0]
</syntaxhighlight>

- Exit the shell using the following command.

<syntaxhighlight lang="shell">
/> exit
Global pref auto_save_on_exit=true
Configuration saved to /etc/target/saveconfig.json
</syntaxhighlight>

=Configure iSCSI Target on CentOS 9|AlmaLinux 9|RHEL 9=
To configure an iSCSI Target, we will use the following details

* iSCSI target with a unique iQN.
* iSCSI Backstore – is a storage object that defines the resources that the backstore uses.
* Create iSCSI Portal.
* Setup iSCSI LUN.
* Creating an iSCSI ACL.
* Setup CHAP Authentication.

==Create an iSCSI target==

The target name is in the iQN format. iQN format is as follows <code>iqn.YYYY-MM.reverse.domain.name:OptionalIdentifier</code>. Let’s say I was to name a target with an iQN unique string with the name technixleo and my domain is target.example.com the iqn name will be as <code>iqn.2022-06.com.example.target:technixleo</code>
- Login to the admin console of the target CLI shell.
<syntaxhighlight lang="shell">
sudo targetcli
</syntaxhighlight>
- Navigate to the iSCSI directory
<syntaxhighlight lang="shell">
/> cd iscsi/
</syntaxhighlight>

- Create the iSCSI target as shown below.
<syntaxhighlight lang="shell">
/iscsi> create iqn.2022-06.com.example.target:technixleo

Created target iqn.2022-06.com.example.target:technixleo.
Created TPG 1.
Global pref auto_add_default_portal=true
Created default portal listening on all IPs (0.0.0.0), port 3260.
</syntaxhighlight>

- Then verify the created target.
<syntaxhighlight lang="shell">
/iscsi> ls

o- iscsi .......................................................... [Targets: 1]
o- iqn.2022-06.com.example.target:technixleo ....................... [TPGs: 1]
o- tpg1 ............................................. [no-gen-acls, no-auth]
o- acls ........................................................ [ACLs: 0]
o- luns ........................................................ [LUNs: 0]
o- portals .................................................. [Portals: 1]
o- 0.0.0.0:3260 ................................................... [OK]
</syntaxhighlight>

==Create iSCSI Backstore==

You can create backstore devices of any of the following 4 types

*fileio backstore for files
*block backstore for block devices.
*pscsi backstore for direct pass-through of SCSI commands.
*ramdisk backstore for a temporary RAM-backed device.

For this guide, I will create one for fileio and block backstores

<syntaxhighlight lang="shell">
</syntaxhighlight>

===Create fileio storage object===

-Navigate to the fileio on the backstore directory. The backstore is the device where the storage is located.

<syntaxhighlight lang="shell">
/> cd /backstores/fileio
</syntaxhighlight>

- Create a file storage object named disk1 in a directory say /tmp/disk1.img of size 5GB. You can create a different directory to store the disk.
<syntaxhighlight lang="shell">
/backstores/fileio> create disk1 /tmp/disk1.img 5G
Created fileio disk1 with size 5368709120
</syntaxhighlight>

- Verify the created storage object

<syntaxhighlight lang="shell">
/backstores/fileio> ls

o- fileio ................................................. [Storage Objects: 1]
o- disk1 .................... [/tmp/disk1.img (5.0GiB) write-back deactivated]
o- alua ................................................... [ALUA Groups: 1]
o- default_tg_pt_gp ....................... [ALUA state: Active/optimized]
</syntaxhighlight>

===Create a block storage object===
Block devices include physical devices like HDDs, SSDs, CDs, and DVDs, and logical devices such as software or hardware RAID volumes, or LVM volumes.

- Navigate to the block of the backstores directory
<syntaxhighlight lang="shell">
/> cd /backstores/block
</syntaxhighlight>

- Create a block storage object with the following command. Use a disk that is not in use.
<syntaxhighlight lang="shell">
/backstores/block> create name=block1 dev=/dev/vdb
Created block storage object block1 using /dev/vdb.
</syntaxhighlight>

- Verify the created block storage.

<syntaxhighlight lang="shell">
/backstores/block> ls
o- block .................................................. [Storage Objects: 1]
o- block1 ........................ [/dev/vdb (10.0GiB) write-thru deactivated]
o- alua ................................................... [ALUA Groups: 1]
o- default_tg_pt_gp ....................... [ALUA state: Active/optimized]
</syntaxhighlight>

==Creating an iSCSI Portal==

An iSCSI Portal adds an IP address and a port to the target that keeps the target enabled.

- Navigate to the Portals directory.
<syntaxhighlight lang="shell">
/> cd /iscsi/iqn.2022-06.com.example.target:technixleo/tpg1/portals
</syntaxhighlight>

By default, The iSCSI portal is set to listen to all IP addresses with the default port number that is: 0.0.0.0:3260. Delete the default portal with the following command

<syntaxhighlight lang="shell">
/iscsi/iqn.20.../tpg1/portals> delete ip_address=0.0.0.0 ip_port=3260
Deleted network portal 0.0.0.0:3260
</syntaxhighlight>

- Then create the new portal and specify the IP address to enable the target.
<syntaxhighlight lang="shell">
/iscsi/iqn.20.../tpg1/portals> create 192.168.200.47
Using default IP port 3260
Created network portal 192.168.200.47:3260.
</syntaxhighlight>

- Verify the portal created.
<syntaxhighlight lang="shell">
/iscsi/iqn.20.../tpg1/portals> ls
o- portals ........................................................ [Portals: 1]
o- 192.168.200.47:3260 .................................................. [OK]
</syntaxhighlight>

==Creating an iSCSI LUN==
- Create LUN of the create storage object above. Navigate to the iSCSI target directory.
<syntaxhighlight lang="shell">
/> cd /iscsi/iqn.2022-06.com.example.target:technixleo/tpg1/luns
</syntaxhighlight>
- Set the LUN for the created backstores with the following commands.
<syntaxhighlight lang="shell">
/iscsi/iqn.20...leo/tpg1/luns> create /backstores/fileio/disk1
Created LUN 0.

/iscsi/iqn.20...leo/tpg1/luns> create /backstores/block/block1
Created LUN 1.
</syntaxhighlight>

- Verify the creates LUN
<syntaxhighlight lang="shell">
/> ls
o- luns .............................................................. [LUNs: 2]
o- lun0 ................... [fileio/disk1 (/tmp/disk1.img) (default_tg_pt_gp)]
o- lun1 ......................... [block/block1 (/dev/vdb) (default_tg_pt_gp)]
</syntaxhighlight>

==Creating an iSCSI ACL==
<syntaxhighlight lang="shell">
</syntaxhighlight>

==Setup CHAP for the target==

<syntaxhighlight lang="shell">
</syntaxhighlight>

DOCS/UNIX/RHEL/ISCSI/Config iSCSI Target

2022-08-31T08:05:42Z

Admin : /* Creating an iSCSI Portal */

DOCS/UNIX/RHEL/ISCSI/Config iSCSI Target

2022-08-31T08:03:48Z

Admin : /* Create a block storage object */

DOCS/UNIX/RHEL/ISCSI/Config iSCSI Target

2022-08-31T08:03:25Z

Admin : /* Create a block storage object */

DOCS/UNIX/RHEL/ISCSI/Config iSCSI Target

2022-08-31T08:02:03Z

Admin : /* Create fileio storage object */

DOCS/UNIX/RHEL/ISCSI/Config iSCSI Target

2022-08-31T08:01:49Z

Admin : /* Create fileio storage object */

DOCS/UNIX/RHEL/ISCSI/Config iSCSI Target

2022-08-31T08:00:32Z

Admin : /* Create a block storage object */

DOCS/UNIX/RHEL/ISCSI/Config iSCSI Target

2022-08-31T08:00:09Z

Admin : /* Create fileio storage object */

DOCS/UNIX/RHEL/ISCSI/Config iSCSI Target

2022-08-31T07:59:51Z

Admin : /* Create iSCSI Backstore */

DOCS/UNIX/RHEL/ISCSI/Config iSCSI Target

2022-08-31T07:58:01Z

Admin : /* Configure iSCSI Target on CentOS 9|AlmaLinux 9|RHEL 9 */

DOCS/UNIX/RHEL/ISCSI/Config iSCSI Target

2022-08-31T07:51:29Z

Admin : /* Install iSCSI Target on CentOS 9|AlmaLinux 9|RHEL 9 */

DOCS/UNIX/RHEL/ISCSI/Config iSCSI Target

2022-08-31T07:49:37Z

Admin : /* Sites Références */

DOCS/UNIX/RHEL/ISCSI/Config iSCSI Target

2022-08-31T07:49:00Z

Admin : Page créée avec « {{MediaWiki}} {{FOND_BLEU|QEMU - '''Configure iSCSI Target on CentOS 9/AlmaLinux 9/RHEL 9'''}} = Sites Références = Cet articles est une transposition sous MediaWiki… »

DOCS/UNIX/RHEL

2022-08-31T07:40:47Z

Admin : /* Stockage */

DOCS/UNIX/RHEL

2022-08-31T07:40:19Z

Admin : /* Stockage */

DOCS/UNIX/RHEL

2022-08-31T07:37:50Z

Admin :

DOCS/UNIX/RHEL

2022-08-31T07:37:21Z

Admin :

Virtualisation

2022-08-31T07:35:10Z

Admin :

{{MediaWiki}}
 
* [[Virtualisation/KVM/Intro| Virtu avec QEMU/KVM - Intro]]
* [[Virtualisation/KVM/Bridges_bond_vlans| Configurer des bridges et des VLANs utilisables pour KVM/QEMU]]
* [[Virtualisation/DEVOPS/Automatisation| Automatiser l'infrastrucuture virtuelle avec Packer+Terraform+Ansible]]

DOCS/UNIX/RHEL

2022-08-31T07:34:50Z

Admin :

{{MediaWiki}}

{{FOND_BLEU|Bonnes pratiques d'administration d'un Système Linux Redhat/Centos/AlmaLinux 8/9}}

* Réseau
** [[Virtualisation/KVM/Bridges_bond_vlans| Configurer des bridges et des VLANs utilisables pour KVM/QEMU]]
* Stockage

Modèle:SysAdmin

2022-08-31T07:31:09Z

Admin :

* [[DOC:UNIX:Commandes| Recettes de cuisine & commandes utiles]]
* [[DOC:UNIX:Droits| Les droits d'accès aux fichiers]]
* [[DOC:UNIX:Crontab| La planification de jobs via crontab ]]
* [[DOCS/UNIX/Trucs et astuces|Trucs et astuces sous Unix]]
* [[DOCS/UNIX/Désactiver complètement IPV6|Désactiver complètement IPV6 sur une serveur]]
* [[DOCS/UNIX/SElinux|Petit guide de survie SElinux sous Redhat/Centos]]
* [[DOCS/UNIX/Hardening|Sécuriser en profondeur un serveur Redhat/Centos 8]]
* [[DOCS/UNIX/RHEL|Bonnes pratiques d'administration d'un Système Linux Redhat/Centos/AlmaLinux 8/9]]