07-10-2014
you cannot check physical SEA interface from the LPAR. LPAR itself cannot see if the SEA (VIOS) interface does (not) have a link.
Only the way is using ping test to the default gateway ... it something what even ehterchannel relies on client LPARs
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have installed in the server a quad ethernet adapter, I'm using two interfaces with two different IP networks, both interfaces are connected to a switch, the switch report that is receiving the same MAC address in both ports so must of the times I have connectivity problems.
Any idea to change... (1 Reply)
Discussion started by: mono673
1 Replies
2. Solaris
I have a Dual Boot system - XP with Solaris 10. I built the system from the ground up with different components and the Ethernet Card built into the Motherboard is a Marvell Yukon Gigabit Ethernet 10/100/1000 T-base, RJ-45 Copper.
I am unable to go to the Web as the Ethernet Card is still not... (2 Replies)
Discussion started by: tubbyrana
2 Replies
3. Solaris
hi all,
How to install onboard ethernet card on Sun SPARC M4000 server? (3 Replies)
Discussion started by: Tlg13team
3 Replies
4. AIX
Hi,
In our AIX 5.2 server , we have one unused ethernet adapter which doesn't have cable connection . For this interface , we are getting alerts in errpt .
Could you suggesthow to stop this alert ? And sametime i would like to keep this device in ODM .
Is there... (1 Reply)
Discussion started by: sekarsamy
1 Replies
5. AIX
All
I am trying allocate an IVE to an LPAR (not a VIO) running AIX 7.1. I am getting the error:
HSCL068A
Explanation
Logical port can not be assigned to Logical Partition because this Logical Partition is not the promiscuous LPAR for the physical port.
Has anyone encountered this... (1 Reply)
Discussion started by: johnf
1 Replies
6. Red Hat
Hi,
I have installed Oracle Enterprise Linux 5 in my PC. After the installation the Ethernet Card is not got detected.
But I could able to get the details using the command lspci -a:
01:00.0 Ethernet controller: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0).
But I could... (4 Replies)
Discussion started by: chidhu.anu
4 Replies
7. AIX
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies
8. Hardware
Hi,
Does anybody have a "Sun 10-Gigabit Ethernet Adapter installation CD" or driver ixge for Sun 10-Gigabit Ethernet PCI-X adapter? I need it but can't find it anywhere. So if you know where I can download it or purchase it, please let me know. (Already tried Oracle's website, don't have it) ... (5 Replies)
Discussion started by: Lhao
5 Replies
9. Solaris
Hi Community,
i have one issue with 10 fiber ethernet adapter.
here is my details:
root@new-bpel.example.com #dladm show-dev
bge0 link: unknown speed: 0 Mbps duplex: unknown
bge1 link: up speed: 1000 Mbps duplex: full
qlge2 link:... (4 Replies)
Discussion started by: bentech4u
4 Replies
10. Red Hat
Hello community, I have a Proliant HP DL380P with the following network adapters:
NetXtreme BCM5719 Gigabit Ethernet PCIe (Ethernet 1Gb 4-port 331FLR Adapter)
82580 Gigabit Network Connection (NC365T 4-port Ethernet Server Adapter)
I installed Red Hat 7.2 but it recognizes only the... (9 Replies)
Discussion started by: Lord Spectre
9 Replies
LEARN ABOUT MOJAVE
traceroute6
TRACEROUTE6(8) BSD System Manager's Manual TRACEROUTE6(8)
NAME
traceroute6 -- print the route IPv6 packets will take to a network node
SYNOPSIS
traceroute6 [-dIlnNrvU] [-f firsthop] [-g gateway] [-m hoplimit] [-p port] [-q probes] [-s src] [-w waittime] target [datalen]
DESCRIPTION
The traceroute6 utility uses the IPv6 protocol hop limit field to elicit an ICMPv6 TIME_EXCEEDED response from each gateway along the path to
some host.
The only mandatory parameter is the destination host name or IPv6 address. The default probe datagram carries 12 bytes of payload, in addi-
tion to the IPv6 header. The size of the payload can be specified by giving a length (in bytes) after the destination host name.
Other options are:
-d Debug mode.
-f firsthop
Specify how many hops to skip in trace.
-g gateway
Specify intermediate gateway (traceroute6 uses routing header).
-I Use ICMP6 ECHO instead of UDP datagrams.
-l Print both host hostnames and numeric addresses. Normally traceroute6 prints only hostnames if -n is not specified, and only numeric
addresses if -n is specified.
-m hoplimit
Specify maximum hoplimit, up to 255. The default is 30 hops.
-n Do not resolve numeric address to hostname.
-N Use a packet with no upper layer header for the probes, instead of UDP datagrams.
-p port
Set UDP port number to port.
-q probes
Set the number of probe per hop count to probes.
-r Bypass the normal routing tables and send directly to a host on an attached network. If the host is not on a directly-connected net-
work, an error is returned. This option corresponds to the SO_DONTROUTE socket option; it can be used to ping a local host through
an interface that has no route through it (e.g., after the interface was dropped by a routing daemon).
-s src Src specifies the source IPv6 address to be used.
-U Use UDP datagrams for the probes. This is the default.
-v Be verbose.
-w waittime
Specify the delay time between probes.
This program prints the route to the given destination and the round-trip time to each gateway, in the same manner as traceroute.
Here is a list of possible annotations after the round-trip time for each gateway:
!N Destination Unreachable - No Route to Host.
!P Destination Unreachable - Administratively Prohibited.
!S Destination Unreachable - Not a Neighbour.
!A Destination Unreachable - Address Unreachable.
! This is printed if the hop limit is <= 1 on a port unreachable message. This means that the packet got to the destination, but
that the reply had a hop limit that was just large enough to allow it to get back to the source of the traceroute6. This was
more interesting in the IPv4 case, where some IP stack bugs could be identified by this behaviour.
RETURN VALUES
The traceroute6 utility will exit with 0 on success, and non-zero on errors.
SEE ALSO
ping(8), ping6(8), traceroute(8)
HISTORY
The traceroute6 utility first appeared in WIDE hydrangea IPv6 protocol stack kit.
BSD
May 17, 1998 BSD