network ip route | ethtool eth0 | ip a | route | ip addr add dev ens33 10.0.0.8/24 | ip route add 20.0.0.0/8 via 192.168.174.131 | ifconfig -a

By OK -
BIOS naming based on hardware properties
em[1-N] for embedded NICs
p<slot_num>p<port_num>

 Udev naming: classical ethX naming

 Logical naming: <vlan> and :<alias>

 ----------------------------------------------------
ifconfig is obsolete and shouldn't be used anymore

----------------------------------------------------
ethtool eth0
Look at the last line; it should say:
Link detected: yes

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

 centos@192 ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
    link/ether 00:0c:29:17:b4:58 brd ff:ff:ff:ff:ff:ff
[centos@192 ~]$

 ----------------------------------------------------
[centos@192 ~]$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:17:b4:58 brd ff:ff:ff:ff:ff:ff
    inet 192.168.174.131/24 brd 192.168.174.255 scope global dynamic ens33
       valid_lft 1293sec preferred_lft 1293sec
    inet6 fe80::20c:29ff:fe17:b458/64 scope link
       valid_lft forever preferred_lft forever
[centos@192 ~]$

 ----------------------------------------------------
Find your gateway address. your gateway should show up
at the top of the output. Note, the route command taking a long time to complete

is also a sign the connection is down

centos@192 ~]$ ip route
default via 192.168.174.2 dev ens33  proto static  metric 100 
192.168.174.0/24 dev ens33  proto kernel  scope link  src 192.168.174.131  metric 100 


 ----------------------------------------------------
[root@localhost ~]# ip addr add dev ens33 10.0.0.8/24
[root@localhost ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:17:b4:58 brd ff:ff:ff:ff:ff:ff
    inet 192.168.174.131/24 brd 192.168.174.255 scope global dynamic ens33
       valid_lft 1742sec preferred_lft 1742sec
    inet 10.0.0.8/24 scope global ens33
       valid_lft forever preferred_lft forever
    inet6 fe80::20c:29ff:fe17:b458/64 scope link 
       valid_lft forever preferred_lft forever
[root@localhost ~]# 

----------------------------------------------------
No secondary address for ifconfig command
[root@localhost ~]# ifconfig -a
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.174.131  netmask 255.255.255.0  broadcast 192.168.174.255
        inet6 fe80::20c:29ff:fe17:b458  prefixlen 64  scopeid 0x20<link>
        ether 00:0c:29:17:b4:58  txqueuelen 1000  (Ethernet)
        RX packets 55005  bytes 64763900 (61.7 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 31976  bytes 2760752 (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 1  (Local Loopback)
        RX packets 159  bytes 13974 (13.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 159  bytes 13974 (13.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[root@localhost ~]# ip route add 20.0.0.0/8 via 192.168.174.131
[root@localhost ~]# ip route
default via 192.168.174.2 dev ens33  proto static  metric 100 
10.0.0.0/24 dev ens33  proto kernel  scope link  src 10.0.0.8 
20.0.0.0/8 via 192.168.174.131 dev ens33 
192.168.174.0/24 dev ens33  proto kernel  scope link  src 192.168.174.131  metric 100 
[root@localhost ~]# 

Comments

Post a Comment

Popular posts from this blog

HAproxy logging

By OK -
ubuntu@ubuntu:/etc/haproxy$ cat /etc/rsyslog.d/haproxy.conf # Create an additional socket in haproxy's chroot in order to allow logging via # /dev/log to chroot'ed HAProxy processes $ModLoad imudp $UDPServerRun 514 local0.* -/var/log/haproxy-0.log local1.* -/var/log/haproxy-1.log ### keep logs in localhost ## $AddUnixListenSocket /var/lib/haproxy/dev/log ------------------- ubuntu@ubuntu:/etc/haproxy$ cat /etc/haproxy/haproxy.cfg global chroot /var/lib/haproxy user haproxy group haproxy log 127.0.0.1   local0         log 127.0.0.1   local1 notice daemon frontend www     bind 192.168.40.128:8282    # haproxy public IP     default_backend as-backend    # backend used backend as-backend    balance leastconn    mode http  server as1 192.168.40.128:8082 check    # application srv 1 defaults log global mode http option httplog option dontlognull         contimeout 5000    
Read more

tomcat catalina coyote jasper cluster

By OK -
Tomcat Component are Catalina Coyote Jasper Cluster Catalina :  Catalina is the name of the servlet container of Apache Tomcat since version 4.x. Tomcat implements Sun Microsystems' specifications for servlet and JavaServer Pages (JSP), which are important Java-based Web technologies. Tomcat's servlet container was redesigned as Catalina in Tomcat version 4.x. other components of the Tomcat engine are: Tomcat Jasper which converts the code portions within JavaServer Pages into servlets and pass them to Catalina to process. Tomcat Coyote which is an HTTP connector based on HTTP/1.1 specifications that receives and transmits web requests to the Tomcat engine by listening to a TCP/IP port and returns requests back to the requesting client. Coyote :  The Coyote JK Connector element represents a Connector component that communicates with a web connector via the JK protocol (also known as the AJP protocol). This is used for cases where you wish to invisibly integr
Read more

NFS mount add in fstab _netdev instead of default | firewall-cmd --list-all

By OK -
Redhat recommends us to add  _netdev  option for NFS file system in /etc/fstab. So that they can be mounted after starting the networking service. Alternative ways to refer to partitions: Label : LABEL=label Network ID Samba : //server/share NFS : server:/share SSHFS : sshfs#user@server:/share Device : /dev/sdxy (not recommended) Example #1 //192.168.1.134/share_name /mnt/share_name cifs username=server_user,password=server_password,_netdev 0 0 ^ Path to your share ^ Mountpoint ^ Username ^ Password ^ See note A Note A: The  _netdev  options makes sure the mount is only attempted AFTER a network connection has been established. Example #2 10.10.10.1:/vol1/fs1 /data nfs defaults,_netdev 0 0 ============================ [root@localhost ~]# firewall-cmd --list-all public   target: default   icmp-block-inversion: no   interfaces:   sources:   services: dhcpv6-client high-availability ssh   ports:   protocols:   masquera
Read more