HMC Hardware Discovery does not work for p595 frames
Hi,
I require help with hardware discovery while running a command from an HMC with firmware V7.3.5 SP 3. The two frames I am running the command for are p 5 595's.
Command input:
Error output: The managed system does not support hardware discovery.
The above command works on p 6 595 frames. Has anybody seen this error code before? Please help with this issue.
I'm using ethereal to analyse my network from my pc.
There're too many TCP Bad checksum
1. between my PC and unix servers (checksum: 0x6660 )
2. between my PC and other servers (windows, novell) checksum: 0x6644 )
There're too many NBNS and BOOTP/DHCP Malformed Packet(Exception occured) ... (0 Replies)
The p595 have 6 Lpars, not all hardware resource assigned to 6 lpars.
which command can list all hardware configuration on p595? Do I need go to each lapr to list? (2 Replies)
Hi,
I am writing a web application using Perl CGI. And I have defined an frame within like this
"<iframe id=\"iframe01\" name=\"iframe01\" height=480 width=800 frameborder=0 scrolling=no></iframe>"
My problem is that this iframe appears differently on different browsers - IE6, IE7, Mozilla... (0 Replies)
Hi,
Need Help!
I'm porting VxWorks code to Linux. Here in VxWorks I have a structure called ether_tag_header.
What is the equivalent structure in Linux?
Note:
struct ether_tag_header {
u_char ether_dhost;
u_char ether_shost;
u_char etherTag;
u_short... (0 Replies)
Hello, we have a wierd and urgent problem, with a few of our p595 LPARs running AIX 5.3. The LPARs ran AIX 5.3 TL 7 and booted off EMC SAN disks, using EMC Powerpath. Every boot we run "pprootdev on" and "pprootdev fix". We can issue "bosboot -a" and we can reboot the machines.
Now, on two... (2 Replies)
Hi,
I have to insert html frames in for loop.
Here is the code.
for($k=0;$k<3;$k++)
{
print<<HTML;
<html>
<head>
<title>
HTML Horizontal Frames
</title>
</head>
<frameset cols="25%,75%">
<frame src="a.html">
<frame src="b.html">
</frameset> (0 Replies)
Hi,
We have a P595 machine with a dual port Fiber card per VIOs.
We have two VIOs in the box.
VIO1: ---> 2 port Fiber Card
VIO2: ---> 2 port Fiber Card
One port on each fiber card is utilized. Connected to SAN switches. We are getting all disks from SAN both for VIOs and LPARs.
Now... (0 Replies)
Hi All,
i would like to know if it's possible to know all the IP Addresses of all LPAR's interfaces from HMC (without connect into LPAR).
And if i can know also the "Application" hostname of LPAR from HMC.
Thanks in advance.
Bye
Mario (2 Replies)
Discussion started by: Zio Bill
2 Replies
LEARN ABOUT SUSE
pppoe-discovery
PPPOE-DISCOVERY(8) System Manager's Manual PPPOE-DISCOVERY(8)NAME
pppoe-discovery - perform PPPoE discovery
SYNOPSIS
pppoe-discovery [ options ]
pppoe-discovery { -V | -h }
DESCRIPTION
pppoe-discovery performs the same discovery process as pppoe, but does not initiate a session. It sends a PADI packet and then prints the
names of access concentrators in each PADO packet it receives.
OPTIONS -I interface
The -I option specifies the Ethernet interface to use. Under Linux, it is typically eth0 or eth1. The interface should be "up"
before you start pppoe-discovery, but should not be configured to have an IP address. The default interface is eth0.
-D file_name
The -D option causes every packet to be dumped to the specified file_name. This is intended for debugging only.
-U
Causes pppoe-discovery to use the Host-Uniq tag in its discovery packets. This lets you run multiple instances of pppoe-discovery
and/or pppoe without having their discovery packets interfere with one another. You must supply this option to all instances that
you intend to run simultaneously.
-S service_name
Specifies the desired service name. pppoe-discovery will only accept access concentrators which can provide the specified service.
In most cases, you should not specify this option. Use it only if you know that there are multiple access concentrators or know
that you need a specific service name.
-C ac_name
Specifies the desired access concentrator name. pppoe-discovery will only accept the specified access concentrator. In most cases,
you should not specify this option. Use it only if you know that there are multiple access concentrators. If both the -S and -C
options are specified, they must both match.
-A
This option is accepted for compatibility with pppoe, but has no effect.
-V | -h
Either of these options causes pppoe-discovery to print its version number and usage information, then exit.
AUTHORS
pppoe-discovery was written by Marco d'Itri <md@linux.it>, based on pppoe by David F. Skoll <dfs@roaringpenguin.com>.
SEE ALSO pppoe(8), pppoe-sniff(8)
22 January 2006 PPPOE-DISCOVERY(8)