This site is maintained by Adil Hasan Mhaisker.
Here I post things related to technology (mostly Computers), which I get into trouble and google won't give me straight and direct answers to. So, to not let this happen to other people, I put such things here which can save time for many people.
Recently I ran into issue to find out what is /dev/cciss/c0d0pX. Unfortunately, there was no direct and simple answer from the great Google.
This thing you can find in Linux OS where your partitions are mounted on for eg. /dev/cciss/c0d0p2 instead on regular /dev/hdaX or /dev/sdaX. These are kind of "virtual disks" (/dev/cciss/c0d0) and are NOT regular hard disks (unlike /dev/hda or /dev/sda). Actually, these are RAID device configured from the BIOS or SmartStart CD before installing the OS.
When you will try to install the Linux OS over such RAID
configured from BIOS level, your OS will detect them as "/dev/cciss/c0d0" disks instead of regular "/dev/hda" or "/dev/sda". Although you
can use them as your normal drives and create partitions, which will be called
as “/dev/cciss/c0d0p1”, “/dev/cciss/c0d0p2”, etc, whereas your
normal drives would have looked like “/dev/hda1”, “/dev/hda2”, etc or “/dev/sda1”,
“/dev/sda2”, etc. You CAN use these par…
This link includes the firmwares for ALL HP networking devices including firmware for Procurve switches (E-series), H3C switches (A-series), MSR Routers, H3C SecPath UTMs, etc. Just type the model (or part number) you are looking to upgrade in the search box as shown (Click to enlarge).
In case you are having HP
ProCurve Core Switches, and need to configure redundancy on it, you need to
configure VRRP to achieve it. I will assume you have the knowledge of HSRP for
this post. Somehow, HP
ProCurve switches does not support a separate Virtual IP address than the
Physical IP address for VRRP. Although, many other vendors do support it
(Virtual IP being different than the Physical IP addresses (in the same
network)). HP ProCurve requires that the Virtual IP address to be the same as
the Master's Physical IP address. I am not sure why they want us to enforce the
Virtual IP address being the same as Master's Physical IP address, since this
creates issues, especially in Monitoring software. For e.g., you want to
monitor both Cores by their IP address. Since they are running VRRP, and if
master fails, the Master's IP address will still show as "UP", since
the virtual IP (which is same as Master's Physical IP address) has shifted to