Wednesday, November 5, 2014
Linux : List Ethernet Network Card Hardware and kernel driver information
# lspci | grep -i ether
03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
03:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
03:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
03:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
24:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)
24:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)
# grep -i "10 Gigabit" /var/log/messages
Nov 2 19:22:00 localhost kernel: ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 3.15.1-k
Nov 2 19:22:00 localhost kernel: ixgbe 0000:24:00.0: Intel(R) 10 Gigabit Network Connection
Nov 2 19:22:00 localhost kernel: ixgbe 0000:24:00.1: Intel(R) 10 Gigabit Network Connection
Nov 3 09:41:46 localhost kernel: ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 3.15.1-k
# lsmod | grep ixgbe
ixgbe 243936 0
mdio 4769 1 ixgbe
ptp 9614 2 ixgbe,tg3
dca 7101 2 ixgbe,ioatdma
Friday, October 31, 2014
Linux : Boot Kernel to Single User Mode or Emergency Mode
http://www.linuxsv.org/training/l1_linux_boot.html
The way that uses GRUB to load the Linux Kernel can be customized directly at the console typing "e" following the instructions of the GRUB graphical menu showed at startup or directly modifying the file /etc/grub.conf:
kernel /vmlinuz-2.6.18-53.el5 ro root=/dev/VolGroup01/LogVol00 rhgb quiet s
Single user mode "s" that provides a root shell without root password check. Very useful for root password recovery.
Single user mode "s" that provides a root shell without root password check. Very useful for root password recovery.
kernel /vmlinuz-2.6.18-53.el5 ro root=/dev/VolGroup01/LogVol00 rhgb quiet emergency
Emergency mode provides a maintenance root shell after root password check.
Emergency mode provides a maintenance root shell after root password check.
kernel /vmlinuz-2.6.18-53.el5 ro root=/dev/VolGroup01/LogVol00 rhgb quiet init=/bin/sh
With this configuration you can startup the system skipping the init process. It provides a root shell after root password check.
With this configuration you can startup the system skipping the init process. It provides a root shell after root password check.
kernel /vmlinuz-2.6.18-53.el5 ro root=/dev/VolGroup01/LogVol00 rhgb quiet 5
Graphical mode startup, the default behaviour.
Graphical mode startup, the default behaviour.
kernel /vmlinuz-2.6.18-53.el5 ro root=/dev/VolGroup01/LogVol00 rhgb quiet selinux=0
SElinux can be disabled at kernel boot time with this configuration.
SElinux can be disabled at kernel boot time with this configuration.
Thursday, October 23, 2014
Linux : NFS : Some NFS file systems are not mounted after reboot
Problem : Some NFS file systems are not mounted after reboot
Solution : Add options to /etc/fstab
Original fstab :
10.11.200.101:/test /test nfs rw 0 0
After :
10.11.200.101:/test /test nfs rw,bg,hard,rsize=32768,wsize=32768,vers=3 0 0
Also the following services need to be turned on
chkconfig nfs on
chkconfig portmap on
chkconfig netfs on
Solution : Add options to /etc/fstab
Original fstab :
10.11.200.101:/test /test nfs rw 0 0
After :
10.11.200.101:/test /test nfs rw,bg,hard,rsize=32768,wsize=32768,vers=3 0 0
Also the following services need to be turned on
chkconfig nfs on
chkconfig portmap on
chkconfig netfs on
Wednesday, October 22, 2014
Oracle VM Manager : VMPinfo3
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=393004587073657&id=1521931.1
Login as root
/u01/app/oracle/ovm-manager-3/ovm_tools/support/vmpinfo3.sh --username=admin
Enter OVM Manager Password:
Gathering files from all servers. This process may take some time.
Gathering OVM Model Dump files
:
:
:
Login as root
/u01/app/oracle/ovm-manager-3/ovm_tools/support/vmpinfo3.sh --username=admin
Enter OVM Manager Password:
Gathering files from all servers. This process may take some time.
Gathering OVM Model Dump files
:
:
:
Saturday, October 18, 2014
SDN NFV readling list
http://www.nec-labs.com/~lume/sdn-reading-list.html
http://portal.etsi.org/Portals/0/TBpages/NFV/Docs/NFV_White_Paper3.pdf
http://portal.etsi.org/Portals/0/TBpages/NFV/Docs/NFV_White_Paper3.pdf
Wednesday, October 15, 2014
VMWare : Virtual Networking Concepts
http://www.vmware.com/files/pdf/virtual_networking_concepts.pdf
VLANs in VMware Infrastructure
VLANs provide for logical groupings of stations or switch ports, allowing communications as if all stations or ports were on the same physical LAN segment. Confining broadcast traffic to a subset of the switch ports or end users saves significant amounts of network bandwidth and processor time.
In order to support VLANs for VMware Infrastructure users, one of the elements on the virtual or physical network has to tag the Ethernet frames with 802.1Q tag, as shown in Figure 3. There are three different configuration modes to tag (and untag) the packets for virtual machine frames.
• Virtual switch tagging (VST mode) — This is the most common configuration. In this mode, you provision one port group on a virtual switch for each VLAN, then attach the virtual machine’s virtual adapter to the port group instead of the virtual switch directly. The virtual switch port group tags all outbound frames and removes tags for all inbound frames. It also ensures that frames on one VLAN do not leak into a different VLAN.
Use of this mode requires that the physical switch provide a trunk.
Virtual machine guest tagging (VGT mode) — You may install an 802.1Q VLAN trunking driver inside the virtual machine, and tags will be preserved between the virtual machine networking stack and external switch when frames are passed from or to virtual switches. The format for the header of a packet tagged in this way is shown in Figure 3.
Use of this mode requires that the physical switch provide a trunk.
• External switch tagging (EST mode) — You may use external switches for VLAN tagging. This is similar to a physical network, and VLAN configuration is normally transparent to each individual physical server.
There is no need to provide a trunk in these environments.
For details on using VLANs with VMware Infrastructure, see the white paper titled VMware ESX Server 3 802.1Q VLAN Solutions, available from the VMTN Web site (http://www.vmware.com/vmtn/).
VLANs in VMware Infrastructure
VLANs provide for logical groupings of stations or switch ports, allowing communications as if all stations or ports were on the same physical LAN segment. Confining broadcast traffic to a subset of the switch ports or end users saves significant amounts of network bandwidth and processor time.
In order to support VLANs for VMware Infrastructure users, one of the elements on the virtual or physical network has to tag the Ethernet frames with 802.1Q tag, as shown in Figure 3. There are three different configuration modes to tag (and untag) the packets for virtual machine frames.
• Virtual switch tagging (VST mode) — This is the most common configuration. In this mode, you provision one port group on a virtual switch for each VLAN, then attach the virtual machine’s virtual adapter to the port group instead of the virtual switch directly. The virtual switch port group tags all outbound frames and removes tags for all inbound frames. It also ensures that frames on one VLAN do not leak into a different VLAN.
Use of this mode requires that the physical switch provide a trunk.
Virtual machine guest tagging (VGT mode) — You may install an 802.1Q VLAN trunking driver inside the virtual machine, and tags will be preserved between the virtual machine networking stack and external switch when frames are passed from or to virtual switches. The format for the header of a packet tagged in this way is shown in Figure 3.
Use of this mode requires that the physical switch provide a trunk.
• External switch tagging (EST mode) — You may use external switches for VLAN tagging. This is similar to a physical network, and VLAN configuration is normally transparent to each individual physical server.
There is no need to provide a trunk in these environments.
For details on using VLANs with VMware Infrastructure, see the white paper titled VMware ESX Server 3 802.1Q VLAN Solutions, available from the VMTN Web site (http://www.vmware.com/vmtn/).
Thursday, October 9, 2014
netcat cheat sheet
http://alexandreborgesbrazil.files.wordpress.com/2013/10/netcat_cheat_sheet_v1.pdf
Subscribe to:
Posts (Atom)
