MS-Office:- 4 Ways to Insert Horizontal Lines in Microsoft Word

4 Ways to Insert Horizontal Lines in Microsoft Word

by Alicia Katz Pollock on July 24, 2014 in Tips & Tricks

One of my tricks with quite the “wow factor” is inserting artistic lines into my documents. To insert a horizontal line (also called a “horizontal rule”), there are four ways to do it.

1. Use Auto Format

On a blank line, type these 3 characters in a row and press ENTER. A line appears across the page.

---

===

***

###

~~~

This is so cool. I loved it

2. Use the Clip Art Gallery

Word’s built-in Clip Art Gallery contains dozens of images that act as lines. Open up INSERT > CLIP ART, and search for LINES. For more choices, when you have an Internet connection, INCLUDE OFFICE.COM CONTENT.

Insert any of the images. If it doesn’t extend across the page, use any of the RESIZE HANDLES to make it larger — but keep in mind that these are images, so if your line image is extended longer than its original dimension, it may become fuzzy.

Use any of the features on the PICTURE TOOLS > FORMAT Tab to change the color, shadow, style, and effects of the line image.

3. Add Bottom Borders

This technique works best on Headings.

Click in the paragraph of text you want a line under. Click on the HOME Tab > BORDERS button — Bottom Border is usually the default. This places a line across the page, underlining not just the text but the rest of the row, too.

Click on BORDERS AND SHADING, the last option on the drop-down list, to refine the weight and color of this line.

When you press Enter at the end of the paragraph, this border may extend down to the next row, an effect you probably don’t want.

Use the CLEAR FORMATTING button on the HOME ribbon, and the border returns to the desired text.

4. Use Shapes

Click on the INSERT RIBBON > SHAPES button. On the drop-down gallery, the second section has a series of lines. Some have arrowheads; others have bends and angles. Pick one.

Click where the line begins, and drag to where the line ends.

To keep the line straight, hold down the SHIFT key while dragging.

Upon letting go, each line has a resize handle at the beginning and end to change the dimension. Lines that have curves and bends also have adjustment diamonds to refine the angles.

Use the DRAWING TOOLS > FORMAT ribbon to stylize the line’s color and special effects.

source: http://royalwise.com/4-ways-insert-horizontal-lines-microsoft-word/

Sun M10 - Series server set up xscf command line reference

SUN SPARC System Console access


ALOM and the System Controller

T-series servers t1000 and t2000 servers can be access through ALOM to get access to ok prompt. Even server is powered off, ALOM still run its firmwares which allow you to login and power on and off the system. The server comes with two ports called SER MGT and NET MGT. Ser MGT is used for serial connection while network management is used with console servers such as digi comsole (cisco, avacent) or similar products.

Here is the basic overview,
when you first time login, you will be prompted for pw. Please check for service manual for default username and password.

Please login:
Please Enter password:

Once you login, you will see sc prompt.

sc>

To connect to console, type consule and press enter.

sc> console


You should either at ok prompt or on the login prompt of the OS.

{ok}

To go back to sc menu, type #., it will take you to sc prompt. and type exit to get out of sc prompt.


At any time, you can switch back to the system controller prompt from the OpenBoot prompt by typing the pound key (#) followed by the period (.) as follows:


To poweron or power off the OS, you can type poweron or poweroff on the sc prompt.

sc> poweron

Only one user can use console at rw mode. If you already have a user, you can use -f to gain control of the console.


sc> console –f

to go back to the sc prompt, type #.


ILOM and the Service Processor

Other t-series servers such as t3, t4, t5 and blade servers, you can use ILOM.

These servers are also come with SER MGT and the NET MGT. You can configure login in through the serial console or theough the console server.



Please login:
Enter a password:

Once you login, you will see -> prompt (-> service processor prompt).

->

To login to the console, you have to Start the system console

-> start /SP/console<cr>

Are you sure you want to start /SP/console (y/n)?

Once you type y, you will either be on OK prompt or on os login prompt.

To go back to system processor prompt, just type #.

To turn the power of the server, type

-> start /SYS

-> stop /SYS

/SYS is uppercase


Like ALOM, to login with write access if user is already logged on, you can forrce login.

-> start -force /SP/console


To login to M-series servers (M3k/M5K)

login:
password:

XSCF>

List configured domains on your physical system.
XSCF>showdomainstatus -a

Login to console on domain 0 or 00

XSCF> console –d 0
XSCF> console –d 00
XSCF> console –d0
Increment of domain is like 1 , 2, 3

To login to domain 1
XSCF> console –d 1



XSCF> console -p 0


Press the [Enter] key. Then, press the [#] (default value for the escape
symbol) and [.] (period) keys to move from the console to the XSCF shell.

{0} ok #


Note: M-series such as M3k/4K/5K do not support LDOM but M10 series do.


M10 series server console login

1. Execute the showdomainstatus command, and confirm that status is "OpenBoot Running".

XSCF# showdomainstatus -p 0
Logical Domain Name    Status
primary                OpenBoot Running
XSCF#


2. Execute the console command to connect to the console of the specified physical partition.

XSCF> console -p 0



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

M10 server login

Logging In to the XSCF

login: default

XSCF>

1. Checking the XCP Version
XSCF> version -c xcp

if you have M10-4S and chassis has different XCP version, then the command to update XCP version on that chassis.

XSCF> flashupdate -c sync


2. Display the XSCF time.
XSCF> showdate

To change the date and time
XSCF> setdate -s 102016592012.00

Sat Oct 20 16:59:00 JST 2012

Performing a Diagnosis Test
---------------------------
The SPARC M10 system cannot be powered on until a CPU Activation key is registered and CPU core resources are assigned to a physical partition.


1. Execute the testsb command.
The testsb command performs an initial diagnosis of the specified physical system board (PSB).

XSCF> testsb -v -p -s -a -y

The command powers on and off the system during the diagnosis.

options
-v: Additionally displays detailed messages of the initial diagnosis
-p: Executes the "probe-scsi-all" command of OpenBoot PROM and displays the results while a diagnosis is being processed
-s: Executes the "show-devs" command of OpenBoot PROM and displays the results while a diagnosis is being processed
-a: Diagnoses all the mounted PSBs
-y: Automatically responds with "y" to a query


2. showhardconf command -  Checking the Component Status
The command displays all the FRUs mounted in the chassis and their status.
However, it does not display the status of I/O-related components such as PCI
cards and PCI expansion units while the system power is off.

XSCF> showhardconf -M


3. Execute the showlogs error command.
Confirm that no error is displayed

XSCF> showlogs error


4. Execute the showstatus command.
When there is no problem, the command displays nothing.

XSCF> showstatus


Making the Initial System Settings

a. Setting the Password Policy

1. Execute the showpasswordpolicy command to check the password policy.

XSCF> showpasswordpolicy

2. Execute the setpasswordpolicy command to set the password policy

XSCF> setpasswordpolicy -y 3 -m 8 -d 2 -u 0 -l 0 -o 0 -M 60 -w 15

Option Password policy
-n        Mindays
-M        Maxdays
-w        Warn
-i        Inactive
-e        Expiry
-y        Retry
-k        Difok
-m        Minlen
-d        Dcredit
-u        Ucredit
-l        Lcredit
-o        Ocredit
-r        Remember

verify the change
XSCF> showpasswordpolicy

b. Setting a User Account and Password
1. Execute the adduser command to add a user account
XSCF> adduser jsmith
or to add with userid
XSCF> adduser -u 359 jsmith

2. Execute the password command, and specify a password
XSCF> password jsmith
XSCF> password -M 60 -w 15 jsmith

Password expores in 60 days and warn you 15 days ahead before the password expires.


3. Execute the setprivileges command to assign a user privilege to the user account.

User privilege   Overview
------------- ---------
platadm Manage the whole system
useradm Manage user accounts.
auditop Refer to the XSCF audit status
auditadm Control auditing OR delete XSCF audit methods.
fieldeng Allow use by field engineers.

XSCF> setprivileges jsmith useradm platadm

specifies useradm and platadm for the user account

4. Execute the showuser command to check information on a created user account.
XSCF> showuser -l


C. Configuring the Telnet/SSH Service

1. Execute the showtelnet command to display the Telnet setting.
XSCF> showtelnet

2. Execute the settelnet command to configure the Telnet service.
XSCF> settelnet -c enable

3. Execute the showtelnet command, and confirm that the Telnet setting is "enabled".
XSCF> showtelnet

 Configuring the SSH service

1. Execute the showssh command to display the SSH settings.
displays the SSH service settings. The factory default is "disabled".

XSCF> showssh

2. Execute the setssh command to configure the SSH service
XSCF> setssh -c enable

3. Execute the showssh command to display the host key and fingerprint.
XSCF> showssh

4. Execute the setssh command to generate the host key
XSCF> setssh -c genhostkey

The following example updates the host key.
XSCF> setssh -c genhostkey
Host key already exists. The key will be updated. Continue? [y|n] :y


D. Configuring the HTTPS Service
XSCF Web with a connection to the XSCF-LAN and for use of a Web browser window.


1. Execute the showhttps command to display the HTTPS service settings.
XSCF> showhttps

2. Execute the sethttps command to configure HTTPS.
XSCF> sethttps -c enable

3. Execute the showhttps command, and confirm that the HTTPS setting has changed to "enabled"
XSCF> showhttps


E. Configuring the XSCF Network
Setting an XSCF host name and domain name

1. Execute the showhostname command to display host names
XSCF> showhostname -a

2. Execute the sethostname command to set a host name.
XSCF> sethostname xscfu hostname

For hostname, specify the host name to set. For xscfu, specify the chassis for the
setting. You can specify it as follows depending on the system configuration:
- M10-1/M10-4/M10-4S (no crossbar box): bb#00, bb#01
- M10-4S (with crossbar boxes): xbbox#80, xbbox#81


The following example sets the host name scf0-hostname for BB#00 and the host name scf1-hostname for BB#01.

XSCF> sethostname bb#00 scf0-hostname
XSCF> sethostname bb#01 scf1-hostname
The following example sets the host name scf0-hostname for XBBOX#80 and the host name scf1-hostname for XBBOX#81

XSCF> sethostname xbbox#80 scf0-hostname
XSCF> sethostname xbbox#81 scf1-hostname

The following example sets the domain name example.com for the master XSCF and standby XSCF.
XSCF> sethostname -d example.com

Setting an Ethernet (XSCF-LAN) IP address

The XSCF-LAN is a LAN established for user access to the XSCF. Two XSCF-LAN
ports can be used, depending on the network configuration.


M10-1/M10-4/1BB configuration of the M10-4S

In the systems with one XSCF, set either or both of the following IP addresses:
- XSCF-LAN#0 of BB#00
- XSCF-LAN#1 of BB#00


1. Execute the setnetwork command with network interface information specified.
The following example sets the IP addresses and net masks for XSCF-LAN#0 and
XSCF-LAN#1 of BB#00 to enable them.

XSCF> setnetwork bb#00-lan#0 -m 255.255.255.0 192.168.1.x
XSCF> setnetwork bb#00-lan#1 -m 255.255.255.0 192.168.2.a

FOR SPARC M10-4S, CHECK THE MANUAL.


Setting the routing
1. Execute the showroute command to display the routing environment.

XSCF> showroute -a


2. Execute the setroute command to set the default gateway

XSCF> setroute -c add -n address -g address interface


For -n address, specify the IP address that is the routing information destination.
If 0.0.0.0 is specified in address, the command sets the default routing information.
For -g address, specify the gateway address used in routing.
For interface, specify the network interface to be set.

XSCF> setroute -c add -n address -g address interface

XSCF> setroute -c add -n 0.0.0.0 -g 192.168.1.1 bb#00-lan#0

The following example adds the default gateway IP address 192.168.1.1 for XSCF-LAN#0 of BB#00.
XSCF> setroute -c add -n 0.0.0.0 -g 192.168.2.1 xbbox#80-lan#1

Applying network settings

1. Execute the applynetwork command on the XSCF shell.
XSCF> applynetwork

2. Execute the rebootxscf command to reset the XSCF and complete the settings
XSCF> rebootxscf -a

Execution of the command disconnects the XSCF connection.

nOTE: To switch from a serial connection to an XSCF-LAN connection, connect to the
XSCF by specifying its IP address on a PC connected to the XSCF-LAN, and log in again.

3. Execute the showhostname, shownetwork, showsscp, and showroute
commands again to display the network settings, and confirm the new
network information


F.  Configuring Memory Mirroring
The SPARC M10 systems support memory mirroring configurations to protect data
through memory duplication. Data reliability increases, but the amount of available
memory is halved.

The memory access controller controls writing of data to memory and reading of
data from memory. The SPARC M10 systems configure the mirroring by grouping
memory into sets controlled by two memory access controllers.

Note - The memory grouped together in a mirroring group must all have the same capacity
and be the same rank

1. Execute the showfru command to check memory mirror mode
XSCF> showfru -a
DISPLAYS default settings.

2. Execute the setupfru command to configure memory mirroring.
XSCF> setupfru [-m {y|n}] device location

To configure memory mirroring, specify -m y
For device, specify the device for which to configure the mirroring. To configure
memory mirroring for all the CPUs mounted on the specified system board
(PSB), specify sb. To configure it only for the specified CPU, specify cpu.
For location, specify the location of the target device. You can specify it in the
xx-0-z format. For xx, specify a system board number. For z, specify a CPU chip
number from 0 to 3.
The following example sets all the CPUs mounted on physical system board 00-0
to memory mirror mode

XSCF> setupfru -m y sb 00-0

3. Execute the showfru command to check the set memory mirror mode.
XSCF> showfru -a


g. Creating a Physical Partition Configuration List (PCL)

A physical partition (PPAR) consists of physical system boards (PSBs). In the
physical partition, the hardware resources of a physical system board (PSB) can be
assigned to logical system boards (LSB).
Use the showpcl command to check a physical partition configuration list (PCL), and
use the setpcl command to set a PCL.

¦ Physical system board (PSB)
The PSB consists of all physical components mounted on a SPARC M10 System
chassis such as CPUs and memory. In other words, the physical system board
(PSB) of the SPARC M10-1 is a motherboard unit, and that of the SPARC
M10-4/M10-4S is a CPU memory unit (containing the <CMUL> on the bottom and
the <CMUU> on top). The other devices that are treated as physical system boards
(PSBs) may include PCIe cards and disk devices. Sometimes, a physical unit of
hardware being installed/removed/replaced is described as a physical system
board (PSB).

¦ Logical system board (LSB)
The LSB is a logical unit name assigned to a physical system board (PSB). Each
physical partition has a set of logical system boards (LSBs) assigned to it. A logical
system board number is used to control how resources such as kernel memory are
assigned to each logical domain.

¦ System board
This term is used to describe hardware resources in operations such as configuring
or displaying a physical partition.


1. Execute the showpcl command to check a physical partition configuration list(PCL).
No physical partition configuration list (PCL) is set in the factory default settings.

XSCF> showpcl -p 0

2. Execute the setpcl command to create a physical partition configuration list (PCL).

The following example maps system board 00-0 to logical system board 0 of
physical partition 0.

XSCF> setpcl -p 0 -a 0=00-0

The following example maps system boards 01-0, 02-0, and 03-0 to logical system
boards 0, 1, and 2, respectively, of physical partition 1.

XSCF> setpcl -p 1 -a 0=01-0 1=02-0 2=03-0


3. Execute the setpcl command to set the configuration policy for all physical
partitions as a whole

XSCF> setpcl -p ppar_id -s policy=value

In value, specify fru (part), psb (system board), or system (all physical partitions
as a whole) as the degradation unit. The default setting is fru.
The following example sets the configuration policy to "All physical partitions"
for physical partitions 0 and 1.

XSCF> setpcl -p 0 -s policy=system
XSCF> setpcl -p 1 -s policy=system

4. Execute the showpcl command, and confirm the set physical partition
configuration list (PCL).
XSCF> showpcl -a


h. Assigning a System Board (PSB) to a Physical Partition (PPAR)

Based on the physical partition configuration list (PCL), assign a system board (PSB)
to a logical system board (LSB) of the physical partition (PPAR).
For the SPARC M10-1/M10-4 system, a system board is already assigned.

1. Execute the showboards command to check the system board (PSB) status.

XSCF> showboards -a


2. Execute the addboard command to assign the system board (PSB) to the physical partition.
The following example adds system board 00-0 to physical partition 0

XSCF> addboard -c assign -p 0 00-0

The following example adds system boards 01-0, 02-0, and 03-00 to physical partition 1.
XSCF> addboard -c assign -p 1 01-0 02-0 03-0

3. Execute the showboards command to check the system board (PSB) status.

XSCF> showboards -a


i. Setting a CPU Operational Mode for the Physical Partition

There are two CPU operational modes (cpumode) that are specifiable for the
setpparmode command: auto mode and compatible mode.


1. Execute the showpparmode command to check the CPU Mode of the physical partition.

XSCF>showpparmode -p 0


2. To change the CPU mode to "compatible" mode, execute the setpparmode
command and set the CPU Mode to "compatible".

XSCF>setpparmode -p 0 -m cpumode=compatible

3. Execute the showpparmode command, and confirm that the CPU Mode of the
physical partition has been set to "compatible".

XSCF>showpparmode -p 0

j. Synchronizing the Physical Partition (PPAR) Time and XSCF Time


1. Execute the showdate command to display the XSCF time.
XSCF> showdate

2. Confirm that the set XSCF time is correct. To change the date and time,
execute the setdate command.

3. Execute the showdateoffset command to check the times difference between
the XSCF system time and physical partition time.

XSCF> showdateoffset -p 0

4. Unless the time difference in step 3 was 0 seconds, execute the resetdateoffset
command to initialize the difference between the XSCF system time and the
time of the physical partition.
The time of each physical partition is synchronized with the XSCF system time at
the next physical partition startup.

XSCF> resetdateoffset -p 0


Registering a CPU Activation Key

Checking a CPU Activation key

1. Execute the showcodactivation command to check the CPU Activation key information

XSCF> showcodactivation

XSCF> showcodactivation

Registering a CPU Activation key

XSCF> addcodactivation -F file:///media/usb_msd/XXXXX_XX.TXT


4. Execute the showcodactivation command, and confirm that the CPU
Activation key is registered with the XSCF.

XSCF> showcodactivation


1. Copy the "ACTIVATION_KEY" contents on the CPU Activation key CD-ROM to
a USB device.
2. Connect the USB device to the USB connector (where "MAINTENANCE
ONLY" is printed) on the XSCF unit panel (rear panel) of the master XSCF.
3. Register the CPU Activation key by executing the addcodactivation command
from the storage location of the key.
The following example specifies the "XXXXX_XX.TXT" file on a USB device to
register CPU Activation keys


XSCF> addcodactivation -F file:///media/usb_msd/XXXXX_XX.TXT

4. Execute the showcodactivation command, and confirm that the CPU
Activation key is registered with the XSCF.

XSCF> showcodactivation

How to copy and paste the CPU Activation key contents
1. Insert the CPU Activation key CD-ROM into the system administration terminal.
2. Open the ACTIVATION_KEY folder on the CD-ROM.

3. Open the relevant file (XXXX_XX_001.TXT), and copy the contents of the key.
4. Execute the addcodactivation command to register the CPU Activation key

XSCF> addcodactivation "Product: SPARC M10-x

5. Execute the showcodactivation command, and confirm that the CPU
Activation key is registered with the XSCF.

XSCF> showcodactivation


Assigning CPU Core Resources

1. Execute the setcod command to assign the CPU core resources to the physical partition.

XSCF> setcod -p ppar_id -s cpu permits

XSCF> setcod -p 0 -s cpu 4

2. Execute the showcod command, and confirm the number of assigned CPU Activations.
XSCF> showcod -v -s cpu

3. Similarly assign CPU core resources to all of the physical partitions.


Starting and Stopping a Physical Partition (PPAR)

1. Execute the setpparparam command to change the auto-boot? setting, which
is an OpenBoot PROM environment variable

XSCF> setpparparam -p 0 -s bootscript "setenv auto-boot? false"

2. Execute the poweron command to start the physical partition.

XSCF> poweron -a

Note - In the SPARC M10-1, a physical partition takes about 5 minutes to start. In the SPARC
M10-4, it takes about 7 minutes. In the SPARC M10-4S in the 4BB configuration, it takes
about 25 minutes.

3. Execute the showpparprogress command
XSCF> showpparprogress -p 0


4. Execute the showdomainstatus command, and confirm that status is "OpenBoot Running".

XSCF# showdomainstatus -p 0
Logical Domain Name    Status
primary                OpenBoot Running
XSCF#


5. Execute the console command to connect to the console of the specified physical partition.

XSCF> console -p 0


6. Press the [Enter] key. Then, press the [#] (default value for the escape
symbol) and [.] (period) keys to move from the console to the XSCF shell.

{0} ok #


7. Execute the poweroff command to stop the physical partition

XSCF> poweroff -a


8. Execute the showpparprogress command, and confirm that the command
displays "The sequence of power control is completed." and ends.

XSCF> showpparprogress -p 0



XSCF> showlogs error

showhardconf command to check the configuration, status, and quantities.

Execute the showpcl command to check a physical partition configuration list
XSCF> showpcl -p 0

Execute the setpcl command to register a system board in the physical partition configuration list




Once you login to the control domain, you can run the following command to see the LDOMs

To check the operation status of the logical domains.

# ldm list-domain
You can check the LDOM status from the characters displayed on the output under FLAGS


The characters and their meanings under FLAGS are
"n" -> Solaris OS running
"t" -> OS on OK prompt PROM state
"-" -> other state (including cases in which STATE is not active)


After reconfiguration, execute the ldm add-spconfig command to save the LDOM configuration in the XSCF.



Check the status of resource usages
# ldm list-devices -a

Execute the ldm list-io command to check the status of I/O device usage

# ldm list-io


In the following example, PCIE8 to PCIE11 belong to domain01


NAME                    TYPE    BUS       DOMAIN    STATUS
----                    ----    ---       ------    ------
PCIE0                   BUS     PCIE0     primary    IOV
PCIE1                   BUS     PCIE1     primary    IOV
PCIE2                   BUS     PCIE2     primary    IOV
PCIE3                   BUS     PCIE3     primary    IOV
PCIE8                   BUS     PCIE8     domain01 IOV
PCIE9                   BUS     PCIE9     domain01 IOV
PCIE10                  BUS     PCIE10    domain01 IOV
PCIE11                  BUS     PCIE11    domain01 IOV
/BB0/CMUL/NET0          PCIE    PCIE0     primary    OCC
/BB0/CMUL/NET2          PCIE    PCIE0     primary    OCC
/BB0/CMUL/SASHBA        PCIE    PCIE0     primary    OCC
/BB0/PCI0               PCIE    PCIE1     primary    EMP
/BB0/PCI1               PCIE    PCIE1     primary    EMP

Of the services provided by the I/O domain, release all the I/O devices of the system board (PSB) that is the removal target.

The following example stops the I/O domain domain01 and releases the PCIe
root complexes related to the removal-target system board (PSB) from among
those belonging to domain01.

# ldm stop domain01
# ldm rm-io PCIE11 domain01
# ldm rm-io PCIE10 domain01
# ldm rm-io PCIE9 domain01
# ldm rm-io PCIE8 domain01


Execute the ldm list-io command again to check the status of I/O device usage
# ldm list-io



Return to the XSCF shell, execute the showboards command, and check the
system board (PSB) status

XSCF> showboards -p 0



Execute the console command to connect to the console of the control domain, and then log in

XSCF> console -p 0


. Execute the deleteboard command to release the system board (PSB) from
the physical partition



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


Stop the target physical partition, and check the cables.
XSCF> poweroff -y -p 0


XSCF> showlogs error
XSCF> poweron -y -p 0

Execute the poweroff command to stop the system.
XSCF> poweroff -y -a


Checking information on a component where a failure or degradation occurred
XSCF> showstatus

Checking diagnosis results
XSCF> testsb -v -p -s -a -y






reference doc: http://www.fujitsu.com/downloads/SPARCS/manuals/en/c120-e678-09en.pdf

Veritas MENU Recommended NetBackup *NIX semaphore tuning values

Problem

 A Master Server and Media server running NetBackup may need OS level system resources increased to function properly.  The following values are used by NetBackup engineering in their test environments.  These are recommended minimum values that should address some OS related performance issues.  If OS resource limitations are below recommended values NetBackup may not work as effectively as expected.  Resource limitations have been known to cause behaviors including application hangs, status code 252, processing delays, and lack of responsiveness amongst other things.

The proposed semaphore values are a recommended minimum.  If your environment already exceeds these values, you should not reduce them to the recommended values. 

Solution

The following semaphore properties should be adjusted:
SEMMSL            - The maximum number of semaphores in a sempahore set.
SEMMNS            - A system-wide limit on the number of semaphores in all semaphore sets. The maximum number of sempahores in the system.
SEMOPM            - The maximum number of operations in a single semop call
SEMMNI             - A system-widerff limit on the maximum number of semaphore identifiers (sempahore sets) 

NetBackup support recommends the following values:

SEMMSL            SEMMNS            SEMOPM            SEMMNI
300                      307200                32                        1024  

Validating/Changing Linux semaphore values:

Run the following command to check existing semaphore values:

root@NBU-Master:~ > sysctl -a | grep kernel.sem
kernel.sem = 250    256000 32    1024  

These values can be adjusted immediately without a restart using the following (but will not persist over a reboot):   

root@NBU-Master:~ > cat /proc/sys/kernel/sem
250 256000 32 1024

root@NBU-Master:~ > echo 300   307200   32   1024 > /proc/sys/kernel/sem

root@NBU-Master:~ > sysctl -a | grep kernel.sem                    
kernel.sem = 300    307200  32   1024  

To modify system semaphore values permanently, running the following will change their default setting and apply these new values immediately:

root@NBU-Master:~ > echo "kernel.sem=300  307200  32  1024">> /etc/sysctl.conf

root@NBU-Master:~ >  cat /etc/sysctl.conf | grep kernel.sem
kernel.sem = 300    307200 32    1024

root@NBU-Master:~ > sysctl -p

 

After running these commands, even after a reboot, the server will maintain the semaphore values that have been set.  Changing semaphore values has resolved multiple performance issues observed on NetBackup Master or Media Servers.

Validating/Changing Solaris semaphore values:

Solaris 10 uses projects to set these values.  The following steps check for the existence of a NetBackup project, and allow you to tune semaphore values within the project.  It is not required to run NetBackup in a project on these operating systems but the following steps are what is required to set semaphore values on a Solaris 10 system:

First check to see if a NetBackup project already exists on the server:

12:17:00^root@NBSolMaster:~ > projects -l NetBackup
projects: project "NetBackup" does not exist

If no NetBackup project has been configured on your system, please review http://www.symantec.com/docs/TECH62633 for a detailed explanation of the steps required to setup a NetBackup project on Solaris. 

After a project has been added for NetBackup, you will see the following output:

12:30:15^root@NBSolMaster:~ > projects -l NetBackup                            
NetBackup
        projid : 1000
        comment: "NetBackup resource project"
        users  : root
        groups : (none)
        attribs:

Once a project has been designed attributes can be set to address semaphore usage as follows:

12:30:15^root@NBSolMaster:~ > projmod -a -K 'project.max-sem-nsems=(privileged,300,deny)' NetBackup
12:30:25^root@NBSolMaster:~ > projmod -a -K 'project.max-sem-ops=(privileged,32,deny)' NetBackup
12:30:37^root@NBSolMaster:~ > projmod -a -K 'project.max-sem-ids=(privileged,1024,deny)' NetBackup 

In Solaris 10+ SEMMNS has been deprecated.

After entering these values, please rerun the following to confirm that they have been set:

12:35:03^root@NBSolMaster:~ > projects -l NetBackup
NetBackup
        projid : 1000
        comment: "NetBackup resource project"
        users  : root
        groups : (none)
        attribs: project.max-sem-ids=(privileged,1024,deny)
        project.max-sem-nsems=(privileged,300,deny)
        project.max-sem-ops=(privileged,32,deny)

Validating/Changing HP-UX semaphore values:

Run the following command to check existing semaphore values:

# kctune -v semmsl semmns semopm semmni

Increasing the semaphore values that are reported can be done with the following:

# kctune semmsl=300
# kctune semmns=307200
# kctune semopm=32
# kctune semmni=1024

After setting these values using kctune, you may need to reboot the server to update these values.  The following command can be used to validate the changes:

# kctune -v semmsl semmns semopm semmni

Validating/Changing AIX semaphore values:

AIX is self tuning and will adjust these values automatically as needed.

Terms of use for this information are found in Legal Notices.

source: https://www.veritas.com/support/en_US/article.000081309

Veritas as a separate company

I am sort of excited and happy to know that Veritas is an independent company and operating independently. I hope they will develop better product the way they used to.

Wish them good luck.


On August 11, 2015 – Symantec announced that it has entered into a definitive agreement to sell its Veritas information management business to The Carlyle Group, a global investment firm with a strong track record of growing businesses. Upon completion of the sale, expected to close at the end of the year, Veritas will become a privately held company. This development will give both Symantec and the Veritas business the financial wherewithal to accelerate the execution of their respective strategies and bring innovation to market sooner for our partners and customers.

RHEL7 - LVM

RHEL7 - LVM

VMware - The network bridge on device vmnet0 is not running

After upgrading windows from 8.1 to Windows10, my vmware interface stop working. To fix this issue, follow the steps below.

1. Open your network and Sharing Center by right clicking network icon on right side bottom of the windows.
2. On network and sharing center windows on left top side, click on change adopter setting.
3. Double Click on your adapter (either wireless or physical) and click on properties.
4. Properties windows pops up.
5. Click on Install on left bottom side.
6. Now, double click on Service
7. Click on VMware Bridge protocol and click ok to close the windows.
8. Now, login to your virtual server and verify your network connectivity.

Sun Sparc Server console access procedure

SUN SPARC System Console access information

ALOM 

T-series servers t1000 and t2000 servers can be access through ALOM to get access to ok prompt. Even server is powered off, ALOM still run its firmwares which allow you to login and power on and off the system. The server comes with two ports called SER MGT and NET MGT. Ser MGT is used for serial connection while network management is used with console servers such as digi comsole (cisco, avacent) or similar products.

Here is the basic overview,
when you first time login, you will be prompted for pw. Please check for service manual for default username and password.

Please login:
Please Enter password:

Once you login, you will see sc prompt.

sc>

To connect to console, type consule and press enter.

sc> console


You should either at ok prompt or on the login prompt of the OS.

{ok}

To go back to sc menu, type #., it will take you to sc prompt. and type exit to get out of sc prompt.


At any time, you can switch back to the system controller prompt from the OpenBoot prompt by typing the pound key (#) followed by the period (.) as follows:


To poweron or power off the OS, you can type poweron or poweroff on the sc prompt.

sc> poweron

Only one user can use console at rw mode. If you already have a user, you can use -f to gain control of the console.


sc> console –f

to go back to the sc prompt, type #.


ILOM 

Other t-series servers such as t3, t4, t5 and blade servers, you can use ILOM.

These servers are also come with SER MGT and the NET MGT. You can configure login in through the serial console or theough the console server.

Please login:
Enter a password:

Once you login, you will see -> prompt (-> service processor prompt).

->

To login to the console, you have to Start the system console

-> start /SP/console<cr>

Are you sure you want to start /SP/console (y/n)?

Once you type y, you will either be on OK prompt or on os login prompt.

To go back to system processor prompt, just type #.

To turn the power of the server, type

-> start /SYS

-> stop /SYS

/SYS is uppercase


Like ALOM, to login with write access if user is already logged on, you can forrce login.

-> start -force /SP/console


To login to M-series servers (M3k/M5K)

login:
password:

XSCF>

List configured domains on your physical system.
XSCF>showdomainstatus -a

Login to console on domain 0 or 00

XSCF> console –d 0
XSCF> console –d 00
XSCF> console –d0
Increment of domain is like 1 , 2, 3

To login to domain 1
XSCF> console –d 1



XSCF> console -p 0


Press the [Enter] key. Then, press the [#] (default value for the escape
symbol) and [.] (period) keys to move from the console to the XSCF shell.

{0} ok #


Note: M-series such as M3k/4K/5K do not support LDOM but M10 series do.


M10 series server console login

1. Execute the showdomainstatus command, and confirm that status is "OpenBoot Running".

XSCF# showdomainstatus -p 0
Logical Domain Name    Status
primary                OpenBoot Running
XSCF#


2. Execute the console command to connect to the console of the specified physical partition.

XSCF> console -p 0

LDAP - intro

LDAP

attribute=value pairs
- Most specific attribute is listed first
  - This may be similar to the way you already think

CN=WIDGETWEB, OU=Marketing, O=Widget, L=London, ST=London, C-GB, DC=widget, DC=com

Attribute Field Usage
------------------------------------------------------------------
CN -------- Common Name                   Identifies the person or object
OU -------- Organizational Unit            A unit or department within the organization
O  ---------  Organization                      Name of the organization
L  ---------  Locality                             Usually a city or area
ST --------  State                                 A state province or country within a country
C  -------- - Country                            The country's 2-character ISO code such as c=US or c=GB)
DC --------  Domain Component        Components of the objects domain


Hirarchical structure
- Build a tree

Container objects
 - country, organization, org units

Leaf object
- users, computers, printers, files


root
 |
-------------------------
| |
C=GB C=US
|
|
|
--------------------------------------
| | |
| | |
O=Widget
|
|
-------------------------------------------------
| | |
| | |
OU=Marketing OU=Accounts OU=MIS
|
|
---------------------------------------------- Leaf objects
| |
| |
CN=WEDGETWEB CN=WEBMASTER

source  - internet / unknown

RHEL7 - yum repo

[root@ashok yum.repos.d]# cat /tmp/a | awk '{$1=""; print $0}'
 rpm -ivh httpd-2.4.6-40.el7.centos.x86_64.rpm
 rpm -ih httpd-2.4.6-40.el7.centos.x86_64.rpm
 rpm -i httpd-2.4.6-40.el7.centos.x86_64.rpm
 ls -l bind*
 rpm -ivh bind-9.9.4-29.el7.x86_64.rpm
 rpm -ivh bind-libs-9.9.4-29.el7.x86_64.rpm
 yum search bind
 yum clean all
 yum repolist
 pwd
 cd /etc/yum.repos.d/
 ls
 cat CentOS-CR.repo CentOS-fasttrack.repo CentOS-Sources.repo kern.repo
 clear
 ls
 vi kern.repo
 yum repolist
 yum search bind
 ls
 mv CentOS-CR.repo CentOS-fasttrack.repo CentOS-Sources.repo kern.repo
 mv kern.repo kern.repo.oldie
 yum repolist
 yum search bind
 yum search bind | more
 yum search bind.x86_64
 yum install bind
 pwd
 cd -
 ls -l httpd-tools-2.4.6-40.el7.centos.x86_64.rpm
 more /boot/grub2/grub.cfg
 ls -l /etc/grub2.cfg
 more ../boot/grub2/grub.cfg
 more /boot/grub2/grub.cfg
 more /etc/yum.conf
 pwd
 ls
 cd -
 ls
 more CentOS-Base.repo
 yum repolist
 yum list yum*
 yum list httpd
 yum list bind
 yum list installed
 yum list installed | wc -l
 yum grouplist
 yum list 'http*'
 yum list 'http'
 yum list http
 yum list httpd
 yum search all 'web server'
 yum info httpd
 yum provides /var/named
 yum provides /var/www/html/
 yum update httpd
 yum list kernel
 uname -r
 uname -a
 yum group list
 yum group info "identiry management server"
 yum group info "identiry Management Server"
 yum group info "identity Management Server"
 yum group install "Infiniband support"
 yum history
 history
 yum.repos.d]#

[root@ashok yum.repos.d]#

RHEL7 - Assigning ip, gateway and dns on RHEL7 server

1. List all available interface on the system

[root@ashok ~]# nmcli connection show
- only to show active ones
[root@ashok ~]# nmcli connection show -active
NAME                UUID                                  TYPE            DEVICE
virbr0-nic          e9279275-54b8-48ef-a756-d4d714bcd5ac  generic         virbr0-nic
virbr0              b7af90bc-8003-49df-bf58-4180828be0fd  bridge          virbr0
Wired connection 2  e3d708dc-aefd-41ea-96d2-81bdd0d307b7  802-3-ethernet  ens37
Wired connection 1  8b3b2e8a-1e5d-4982-93d0-77f7fe4eba6a  802-3-ethernet  ens38
default             4f8fe83d-df38-4441-83ae-0d400f76c43d  802-3-ethernet  ens33

- list all configuration setting for the interace
[root@ashok ~]# nmcli con show "Wired connection 1"
connection.id:                          Wired connection 1
connection.uuid:                        8b3b2e8a-1e5d-4982-93d0-77f7fe4eba6a
connection.interface-name:              --
connection.type:                        802-3-ethernet
connection.autoconnect:                 yes

- [root@ashok ~]# nmcli dev status
DEVICE      TYPE      STATE      CONNECTION
virbr0      bridge    connected  virbr0
ens33       ethernet  connected  default
ens37       ethernet  connected  Wired connection 2
ens38       ethernet  connected  Wired connection 1
virbr0-nic  tap       connected  virbr0-nic
lo          loopback  unmanaged  --

- display device status
[root@ashok ~]# nmcli dev show ens38
GENERAL.DEVICE:                         ens38
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         00:0C:29:80:C1:E6
GENERAL.MTU:                            1500
GENERAL.STATE:                          100 (connected)
GENERAL.CONNECTION:                     Wired connection 1
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/1
WIRED-PROPERTIES.CARRIER:               on
IP4.ADDRESS[1]:                         192.168.10.17/24
IP4.GATEWAY:                            192.168.10.1
IP4.DNS[1]:                             192.168.10.1
IP6.ADDRESS[1]:                         fe80::20c:29ff:fe80:c1e6/64
IP6.GATEWAY:
[root@ashok ~]#



2. Assign static ip/gateway/dns on one of the interface
- adding ip/gateway
[root@ashok ~]# nmcli con add con-name eth-ens38 ifname ens38 type ethernet ip4 192.168.10.220/24 gw4 192.168.10.1
Connection 'eth-ens38' (23d86e57-2fae-480f-8015-4ea7a8539812) successfully added.
[root@ashok ~]#

- adding nameserver
[root@ashok ~]# nmcli con mod "eth-ens38" ipv4.dns 192.168.10.110


3. Bring up the interface.

- list connections on the system
[root@ashok ~]# nmcli connection show
NAME                UUID                                  TYPE            DEVICE
eth-ens38           23d86e57-2fae-480f-8015-4ea7a8539812  802-3-ethernet  --
Wired connection 1  8b3b2e8a-1e5d-4982-93d0-77f7fe4eba6a  802-3-ethernet  ens38
15dd-442e-bc69-25c5bf2c1b6b  802-3-ethernet  --

- bring up the interface
[root@ashok ~]# nmcli con up eth-ens38

- list the active interface
[root@ashok ~]# nmcli con show --active
NAME                UUID                                  TYPE            DEVICE
eth-ens38           23d86e57-2fae-480f-8015-4ea7a8539812  802-3-ethernet  ens38

- verify the ip address

[root@ashok ~]# ip addr show ens38
4: ens38: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:80:c1:e6 brd ff:ff:ff:ff:ff:ff
    inet 192.168.10.220/24 brd 192.168.10.255 scope global ens38
       valid_lft forever preferred_lft forever
    inet6 fe80::20c:29ff:fe80:c1e6/64 scope link
       valid_lft forever preferred_lft forever
[root@ashok ~]#


4. Reboot the system and verify that your assigned ip address is still available.

- upon rebooting the system, verify the ip address is available.

# ifconfig -a
# ip addr show

[root@ashok ~]# ip route
default via 192.168.10.1 dev ens33  proto static  metric 100
192.168.10.0/24 dev ens38  proto kernel  scope link  src 192.168.10.220  metric 102
[root@ashok ~]#

[root@ashok ~]# ping -c 2 yahoo.com
PING yahoo.com (98.138.253.109) 56(84) bytes of data.
64 bytes from ir1.fp.vip.ne1.yahoo.com (98.138.253.109): icmp_seq=1 ttl=52 time=53.9 ms

RHEL7:- interface configuration

ipv6.dhcp-send-hostname:                yes
ipv6.dhcp-hostname:                     --
[root@new-host-4 ~]# nmcli connection show static
connection.id:                          static
connection.uuid:                        6ed539ad-9039-4903-8686-dd0d75896954
connection.interface-name:              ens33
connection.type:                        802-3-ethernet
connection.autoconnect:                 no
connection.autoconnect-priority:        0
connection.timestamp:                   1451691995
connection.read-only:                   no
connection.permissions:
connection.zone:                        --
connection.master:                      --
connection.slave-type:                  --
connection.autoconnect-slaves:          -1 (default)
connection.secondaries:
connection.gateway-ping-timeout:        0
connection.metered:                     unknown
802-3-ethernet.port:                    --
802-3-ethernet.speed:                   0
802-3-ethernet.duplex:                  --
802-3-ethernet.auto-negotiate:          yes
802-3-ethernet.mac-address:             --
802-3-ethernet.cloned-mac-address:      --
802-3-ethernet.mac-address-blacklist:
802-3-ethernet.mtu:                     auto
802-3-ethernet.s390-subchannels:
802-3-ethernet.s390-nettype:            --
802-3-ethernet.s390-options:
802-3-ethernet.wake-on-lan:             1 (default)
802-3-ethernet.wake-on-lan-password:    --
ipv4.method:                            manual
ipv4.dns:
ipv4.dns-search:
ipv4.addresses:                         192.168.10.22/24
ipv4.gateway:                           192.168.10.1
ipv4.routes:
ipv4.route-metric:                      -1
ipv4.ignore-auto-routes:                no
ipv4.ignore-auto-dns:                   no
ipv4.dhcp-client-id:                    --
ipv4.dhcp-send-hostname:                yes
ipv4.dhcp-hostname:                     --
ipv4.never-default:                     no
ipv4.may-fail:                          yes
ipv6.method:                            auto
ipv6.dns:
ipv6.dns-search:
ipv6.addresses:
ipv6.gateway:                           --
ipv6.routes:
ipv6.route-metric:                      -1
ipv6.ignore-auto-routes:                no
ipv6.ignore-auto-dns:                   no
ipv6.never-default:                     no
ipv6.may-fail:                          yes
ipv6.ip6-privacy:                       -1 (unknown)
ipv6.dhcp-send-hostname:                yes
ipv6.dhcp-hostname:                     --
[root@new-host-4 ~]# nmcli connection show static | grep -i auto
connection.autoconnect:                 no
connection.autoconnect-priority:        0
connection.autoconnect-slaves:          -1 (default)
802-3-ethernet.auto-negotiate:          yes
802-3-ethernet.mtu:                     auto
ipv4.ignore-auto-routes:                no
ipv4.ignore-auto-dns:                   no
ipv6.method:                            auto
ipv6.ignore-auto-routes:                no
ipv6.ignore-auto-dns:                   no
[root@new-host-4 ~]# nmcli con mod "static" connection.autoconnect yes
[root@new-host-4 ~]# ifconfig ens33
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.22  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::20c:29ff:fe80:c1d2  prefixlen 64  scopeid 0x20<link>
        ether 00:0c:29:80:c1:d2  txqueuelen 1000  (Ethernet)
        RX packets 5118  bytes 1001886 (978.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 194  bytes 28144 (27.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[root@new-host-4 ~]# nmcli con up best
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkMana                 ger/ActiveConnection/9)
[root@new-host-4 ~]# ifconfig ens33
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.11  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::20c:29ff:fe80:c1d2  prefixlen 64  scopeid 0x20<link>
        ether 00:0c:29:80:c1:d2  txqueuelen 1000  (Ethernet)
        RX packets 5130  bytes 1004593 (981.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 212  bytes 30869 (30.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[root@new-host-4 ~]# nmcli connection up static
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkMana                 ger/ActiveConnection/10)
[root@new-host-4 ~]# nmcli con mod static ipv4.dns 192.168.10.110
[root@new-host-4 ~]# cat /etc/resolv.conf
# Generated by NetworkManager
search home
nameserver 192.168.10.1
[root@new-host-4 ~]# nmcli mod static +ipv4.dns 8.8.8.8
Error: Object 'mod' is unknown, try 'nmcli help'.
[root@new-host-4 ~]# nmcli con mod static +ipv4.dns 8.8.8.8
[root@new-host-4 ~]# nmcli con mod static ipv4.addresses "192.168.10.222/24 192.16                 8.10.1"
Error: failed to modify ipv4.addresses: invalid prefix '24 192.168.10.1'; <1-32> a                 llowed.
[root@new-host-4 ~]# nmcli con mod static ipv4.addresses "192.168.10.222/24  192.168.10.1"         Error: failed to modify ipv4.addresses: invalid prefix '24  192.168.10.1'; <1-32> allowed.
[root@new-host-4 ~]# nmcli con mod static ipv4.addresses "192.168.10.222 255.255.255.0  192.168.10.1"
Error: failed to modify ipv4.addresses: invalid IP address: Invalid IPv4 address '192.168.10.222 255.255.255.0  192.168.10.1'.
[root@new-host-4 ~]# nmcli con mod static ipv4.addresses "192.168.10.122/24  192.168.10.1"         Error: failed to modify ipv4.addresses: invalid prefix '24  192.168.10.1'; <1-32> allowed.
[root@new-host-4 ~]# nmcli con mod static ipv4.addresses "192.168.10.122/24"
[root@new-host-4 ~]# nmcli con status static
Usage: nmcli connection { COMMAND | help }

COMMAND := { show | up | down | add | modify | edit | delete | reload | load }

  show [--active] [[--show-secrets] [id | uuid | path | apath] <ID>] ...

  up [[id | uuid | path] <ID>] [ifname <ifname>] [ap <BSSID>] [passwd-file <file with passwords>]

  down [id | uuid | path | apath] <ID> ...

  add COMMON_OPTIONS TYPE_SPECIFIC_OPTIONS IP_OPTIONS

  modify [--temporary] [id | uuid | path] <ID> ([+|-]<setting>.<property> <value>)+

  edit [id | uuid | path] <ID>
  edit [type <new_con_type>] [con-name <new_con_name>]

  delete [id | uuid | path] <ID>

  reload

  load <filename> [ <filename>... ]

Error: 'status' is not valid 'connection' command.
[root@new-host-4 ~]# nmcli dev status static
Unknown parameter: static
DEVICE      TYPE      STATE         CONNECTION
virbr0      bridge    connected     virbr0
ens33       ethernet  connected     static
ens37       ethernet  connected     Wired connection 1
virbr0-nic  ethernet  disconnected  --
lo          loopback  unmanaged     --
[root@new-host-4 ~]# nmcli dev status static ens33
Unknown parameter: static
Unknown parameter: ens33
DEVICE      TYPE      STATE         CONNECTION
virbr0      bridge    connected     virbr0
ens33       ethernet  connected     static
ens37       ethernet  connected     Wired connection 1
virbr0-nic  ethernet  disconnected  --
lo          loopback  unmanaged     --
[root@new-host-4 ~]# nmcli con up static
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/11)
[root@new-host-4 ~]# nmcli dev status static ens33
Unknown parameter: static
Unknown parameter: ens33
DEVICE      TYPE      STATE         CONNECTION
virbr0      bridge    connected     virbr0
ens33       ethernet  connected     static
ens37       ethernet  connected     Wired connection 1
virbr0-nic  ethernet  disconnected  --
lo          loopback  unmanaged     --
[root@new-host-4 ~]# ifconfig ens33
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.122  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::20c:29ff:fe80:c1d2  prefixlen 64  scopeid 0x20<link>
        ether 00:0c:29:80:c1:d2  txqueuelen 1000  (Ethernet)
        RX packets 5326  bytes 1044006 (1019.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 289  bytes 41901 (40.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[root@new-host-4 ~]# list all devices (interfaces)^C
[root@new-host-4 ~]# nmcli dev status
DEVICE      TYPE      STATE         CONNECTION
virbr0      bridge    connected     virbr0
ens33       ethernet  connected     static
ens37       ethernet  connected     Wired connection 1
virbr0-nic  ethernet  disconnected  --
lo          loopback  unmanaged     --
[root@new-host-4 ~]# list all connections^C
[root@new-host-4 ~]# nmcli connection show
NAME                UUID                                  TYPE            DEVICE
Wired connection 2  14060a87-3977-46fe-a350-6ec3948627c2  802-3-ethernet  --
Wired connection 1  07fdc26a-ec57-427e-a877-8bacc8893ecd  802-3-ethernet  ens37
ens33               eaa62a4e-fb5c-4461-983a-58bad6f8cbf7  802-3-ethernet  --
static              6ed539ad-9039-4903-8686-dd0d75896954  802-3-ethernet  ens33
best                64c78344-15dd-442e-bc69-25c5bf2c1b6b  802-3-ethernet  --
virbr0              b53ef7bb-7c98-4d88-9dc5-64cdab8f1bad  bridge          virbr0
[root@new-host-4 ~]# list only active connections
bash: list: command not found...
[root@new-host-4 ~]# nmcli con up ens33
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/12)
[root@new-host-4 ~]# activate a connection
bash: activate: command not found...
[root@new-host-4 ~]# nmcli con up ens33
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/13)
[root@new-host-4 ~]# de-activate a connection^C
[root@new-host-4 ~]# nmcli con down static
Error: 'static' is not an active connection.
Error: no active connection provided.
[root@new-host-4 ~]# nmcli con down best
Error: 'best' is not an active connection.
Error: no active connection provided.
[root@new-host-4 ~]# nmcli con down ens33
Connection 'ens33' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/13)
[root@new-host-4 ~]# bringdown the interface and disable autoconnect^C
[root@new-host-4 ~]# nmcli dev disconnect ens33
Device 'ens33' successfully disconnected.
[root@new-host-4 ~]# disable all managed interfaces
bash: disable: command not found...
[root@new-host-4 ~]# nmcli net off
[root@new-host-4 ~]# Enable all managed interfaces
[root@new-host-4 ~]# nmcli net on

[root@new-host-4 ~]# ifconfig -a
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.122  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::20c:29ff:fe80:c1d2  prefixlen 64  scopeid 0x20<link>
        ether 00:0c:29:80:c1:d2  txqueuelen 1000  (Ethernet)
        RX packets 5717  bytes 1099802 (1.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 645  bytes 202638 (197.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens37: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.9  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::20c:29ff:fe80:c1dc  prefixlen 64  scopeid 0x20<link>
        ether 00:0c:29:80:c1:dc  txqueuelen 1000  (Ethernet)
        RX packets 14854  bytes 1909941 (1.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 7451  bytes 2775734 (2.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 64  bytes 5440 (5.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 64  bytes 5440 (5.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 00:00:00:00:00:00  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0-nic: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 52:54:00:ec:67:76  txqueuelen 500  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[root@new-host-4 ~]#

[root@new-host-4 ~]#  nmcli con del ens33^C

 456  ls -l /etc/sysconfig/network-scripts/

  457  pwd

  458  cd /etc/sysconfig/network-scripts/

  459  pwd

  460  ls

  461  ls -l *ens*

  462  ifconfig -a

  463  ls

  464  more ifup-wireless

  465    ls

  466  ls -ltr

  467  more ifcfg-ens33

  468  htrp ens37 *

  469  grep ens37 *

  470  grep ens33 *

  471  nmcli con show

  472  ls

  473  nmcli con show

  474  nmcli con show --active

  475  nmcli con show -a

  476  man nm_settings

  477  man nm-settings

  478  nmcli con show "Wired connection"

  479  nmcli con show "Wired connection 1"

  480  nmcli dev status

  481  nmcli device show ens37

  482  nmcli dev show ens37

  483  nmcli net on

  484  ifconfig -a

  485  history

[root@new-host-4 ~]#

[root@new-host-4 ~]# nslookup ashok.expanor.local
Server:         192.168.10.110
Address:        192.168.10.110#53

Name:   ashok.expanor.local
Address: 192.168.10.122

[root@new-host-4 ~]# hostnamectl set-hostname ashok.expanor.local
[root@new-host-4 ~]# hostname
ashok.expanor.local
[root@new-host-4 ~]# hostnamectl status
   Static hostname: ashok.expanor.local
         Icon name: computer-vm
           Chassis: vm
        Machine ID: c52adc6d406d4d69904cf8ef9afbaf4a
           Boot ID: 1439f42e91ca4645991e8aaf4d51ed6d
    Virtualization: vmware
  Operating System: CentOS Linux 7 (Core)
       CPE OS Name: cpe:/o:centos:centos:7
            Kernel: Linux 3.10.0-327.el7.x86_64
      Architecture: x86-64
[root@new-host-4 ~]# cat /etc/hostname
ashok.expanor.local
[root@new-host-4 ~]#