The QETH network device driver supports IBM System z HiperSockets, OSA-Express Fast
Ethernet, Gigabit Ethernet (including 1000Base-T), High Speed Token Ring, and ATM
features (running Ethernet LAN emulation) in QDIO mode.
I'm sorry, but I found this a bit funny. How is it even possible to install a System Z RHEL on x86 platform?
---------- Post updated at 03:40 PM ---------- Previous update was at 03:37 PM ----------
dearsumon, you probably have to contact DELL to check if they provide NIC drivers (for this model) for RHEL.
---------- Post updated at 03:43 PM ---------- Previous update was at 03:40 PM ----------
I'm sure that you have checked ifconfig -a output as well. If you have not selected networking during installation /etc/sysconfig/network-scripts/ifcfg-eth0 does not get created. If eth0 shows up in ifconfig, then you have to manually create ifcfg-eth0 file.
Hi there,
I got a problem with my linux eth0.
It worked well, just one day when i boot it, "Failed" to be active.
The eth0 is inactive! I tried to use KDE network configuration tool to add the type of the eth card, I can't make it active. It gave me warning of "the eth card can't be... (1 Reply)
Hi all,
Thanks for reading and any posts.
Quick question, has anyone out there got any suggestions for standards of security for Redhat enterprise 3. We are making an RAC cluster Oracle application using Oracle 9i (hopefully moving to 10g sooner rather than later).
Thanks again for any... (0 Replies)
when i finish installed rhel 4.4 to my hp dl585 box, ifcfg-eth0 and ifcfg-eth1 is not available.when i ifconfig -a,i can not see the eth0 and eth1, only lo0 and si0. Unlike to the other server i found eth0 and eth1 files in
/etc/sysconfig/network-scripts/.
what will i do? (2 Replies)
Hi All,
I have to upgrade python installed on my Redhat enterprise Linux 4. I downloaded the latest python package from python website but not able to install the new package as the make command itself goes on running for more than a day. Can some help me regarding this. Is ther any method to... (2 Replies)
hi all
do i need to add rc. prefix on the stop script all the time especially on redhat 5 enterprise? like below
ln -s /etc/init.d/rc.stopdb2 /etc/rc0.d/K01rc.stopdb2
and on the /etc/rc.local, i need to add this only
touch /var/lock/subsys/stopdb2
Is that going to work?
thanks... (1 Reply)
When i finished installation the Redhat Enterprise Linux 6.2, and login to the system, I can't login although username: root and Password correct. I install on the Hp Blade Server. I don't know why.
How to fix this error? who can help me? :confused:
Thanks! (3 Replies)
Hi guys,
I really need your help with this.
My network interface eth0 is up but not running. I checked udev rules and ifcfg-eth0 files to make sure the mac address are the same.
It just would not come up. Please please I will really appreciate the help here.
Thank you in advance. (3 Replies)
Having an issue with clustat not displaying the rgmanager info eventhu all the of the cman started successfully. No fencing errors. all of the cluster.conf are the same on all serers ..etc. However when i run the clustat i only see this:
Cluster Status for RESTON-LSMS @ Mon Aug 31 15:13:16 2015... (4 Replies)
Discussion started by: mrn6430
4 Replies
LEARN ABOUT OSF1
snmp_trapsnd
snmp_trapsnd(8) System Manager's Manual snmp_trapsnd(8)NAME
snmp_trapsnd - A program that sends SNMPv1 and SNMPv2 traps
SYNOPSIS
/usr/sbin/snmp_trapsnd enterprise agent_addr generic specific timeticks [-v version] [-c community] [-h host] [-p port] [-tcp] [variable
[type value]]
OPTIONS
Specifies the type of message in which to send the PDU. The default version is SNMPv1. Use 2c to specify that the PDU be sent in an
SNMPv2C message. Specifies the host name or dot-formatted IP address of the destination node to receive the trap message. If no host is
specified, the trap is sent to the loopback interface. Causes a hexadecimal dump of the encoded packet to be sent to stdout. Specifies
that the TCP transport be used instead of the UDP transport. If a connection cannot be established, the program silently sends the trap to
the standard transport address (UDP 162). Specifies the port number on the destination host to which this message is sent. The default is
162, the well-known SNMP trap port. Specifies the community string used to send the trap. The default is public.
OPERANDS
For SNMPv1 traps, this is the enterprise object identifier, in dot string notation, on whose behalf the trap is being sent (for example,
1.3.6.1.4.1.232).
For SNMPv2 traps (specified with the -v 2c option), this represents the value of snmpTrapOID.0. For an SNMPv2 enterprise-specific
trap, this is typically a concatenated string containing the enterprise OID, 0 (zero), and a single digit. See the generic parame-
ter table. The hostname or IP address of the entity on whose behalf the trap is being generated (the agent-addr field in the V1
trap PDU). The special name local reports the host on which this program is running. This value is ignored if the -v 2c option is
present. The generic trap identifier. This is a non-zero number. The following table summarizes the trap IDs:
------------------------------------------------------------------------
Description V1 generic Value V2 enterprise Value
------------------------------------------------------------------------
coldStart 0 1.3.6.1.6.3.1.1.5.1
warmStart 1 1.3.6.1.6.3.1.1.5.2
linkDown 2 1.3.6.1.6.3.1.1.5.3
linkUp 3 1.3.6.1.6.3.1.1.5.4
authenticationFailure 4 1.3.6.1.6.3.1.1.5.5
egpNeighborLoss 5 1.3.6.1.6.3.1.1.5.6
enterpriseSpecific 6 enterprise.0.x
------------------------------------------------------------------------
If the -v 2c option is present, this parameter is ignored. Specifies the enterprise-specific trap number. A value must be present,
but is ignored if the -v 2c option is present or if generic is a value other than 6. Specifies the relative time associated with
the generation of this trap message. This is the number of TIMETICKS (1/100 of a second) since the sending SNMP entity started.
Specifies a list of MIB variables to be included in the trap message. See snmp_request(8) for information on specifiying SNMP MIB
variables on the command line.
DESCRIPTION
The snmp_trapsnd program encodes an SNMPv1 Trap protocol data unit (PDU) (see RFC 1215) or a SNMPv2 Trap PDU (see RFC 1905) into an SNMP
message, and sends it to the specified host(s). All data fields in the trap PDU can be specified in the run-time arguments.
SNMPv1 traps are uniquely identified by the combination of enterprise, generic, and specific operands. SNMPv2 traps are uniquely identi-
fied by the value of snmpTrapOID.0 in the enterprise operand.
RESTRICTIONS
The use of this command should be limited. SNMP traps should be sent rarely, when significant state changes occur on a managed node.
SEE ALSO
Commands: snmpd(8), snmp_request(8), snmp_traprcv(8)
RFC 1907, Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)
snmp_trapsnd(8)