Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: LDoms can't ping each other
Operating Systems Solaris LDoms can't ping each other Post 302442898 by mludvig on Thursday 5th of August 2010 09:23:04 PM
Old 08-05-2010
Played with it for a while, installed second LDom and found that the two LDoms can see each other but none can talk to the control (primary) domain. It must have something to do with the virtual switch I guess.

Here are the interfaces:
Code:
root@krikkit ~ # ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 192.168.140.210 netmask ffffff00 broadcast 192.168.140.255
        ether 0:3:ba:d8:e0:94

And here are all the interfaces found by the primary domain:

Code:
root@krikit ~ # dladm show-dev
vsw0            link: up        speed: 100   Mbps       duplex: full
vsw1            link: up        speed: 100   Mbps       duplex: full
e1000g0         link: up        speed: 100   Mbps       duplex: full
e1000g1         link: up        speed: 100   Mbps       duplex: full
e1000g2         link: unknown   speed: 0     Mbps       duplex: half
e1000g3         link: unknown   speed: 0     Mbps       duplex: half

I tried to "plumb" and "up" the vsw0 device, even give it a new address but that made no difference.

What interfaces do you guys use in the control (primary) domain? The physical e1000g0 (or what's there on your systems) or some virtual ldm interfaces? How do you configure them?

Thanks!
 

10 More Discussions You Might Find Interesting

1. Solaris

RAID1 and LDoms

I have a Netra T5220 Solaris 10 server with LDoms installed and enabled. RAID1 is enabled in the control domain with the following slices: d50 -m d51 d52 1 d51 1 1 c1t0d0s5 d52 1 1 c1t1d0s5 d10 -m d11 d12 1 d11 1 1 c1t0d0s0 d12 1 1 c1t1d0s0 d20 -m d21 d22 1 d21 1 1 c1t0d0s1 d22 1 1... (14 Replies)
Discussion started by: StarSol
14 Replies

2. Solaris

LDOMs on T5220

We're just about to migrate a large application from an Enterprise 6900 to a pair of T5220s utilising LDOMs. Does anyone have any experience of LDOMs on this kit and can provide any recommendations or pitfalls to avoid? I've heard that use of LDOMs can have an impact on I/O speeds as it's all... (9 Replies)
Discussion started by: JerryHone
9 Replies

3. Solaris

LDOMS command

What command would i type to get a list of LDOMS running on a blade? (3 Replies)
Discussion started by: soupbone38
3 Replies

4. Shell Programming and Scripting

Animation Ping on Solaris Like Cisco Ping

Hi, I develop simple animation ping script on Solaris Platform. It is like Cisco ping. Examples and source code are below. bash-3.00$ gokcell 152.155.180.8 30 Sending 30 Ping Packets to 152.155.180.8 !!!!!!!!!!!!!.!!!!!!!!!!!!!!!. % 93.33 success... % 6.66 packet loss...... (1 Reply)
Discussion started by: gokcell
1 Replies

5. Shell Programming and Scripting

How to get reason for ping failure using perls Net::Ping->new("icmp");?

Hi I am using perl to ping a list of nodes - with script below : $p = Net::Ping->new("icmp"); if ($p->ping($host,1)){ print "$host is alive.\n"; } else { print "$host is unreacheable.\n"; } $p->close();... (4 Replies)
Discussion started by: tavanagh
4 Replies

6. Solaris

Can not use zone in LDoms on T4-1

I have a T4-1 with Solaris 11.1, LDom ver 3.0.0.1 and I'm encountering two problems with zones. I'd greatly appreciate help on these, especially the first one. I have created multiple guest LDoms, all Solaris 11.1, and they all work fine. The first problem is that I can not boot any... (9 Replies)
Discussion started by: ad101
9 Replies

7. Solaris

Guest LDOMS on same subnet cant ping eachother

Hi all, New to this forum. I have just been reading through a historical thread about some issues with IPMP. Some tips from "Peasant" where very useful. Please see below "Just couple of more hints regarding VM. For VDS, use one VDS - one guest LDOM, don't put everything in primary-vds.... (9 Replies)
Discussion started by: selectstar
9 Replies

8. Programming

Ping test sends mail when ping fails

help with bash script! im am working on this script to make sure my server will stay online, so i made this script.. HOSTS="192.168.138.155" COUNT=4 pingtest(){ for myhost in "$@" do ping -c "$COUNT" "$myhost" &&return 1 done return 0 } if pingtest $HOSTS #100% failed... (4 Replies)
Discussion started by: mort3924
4 Replies

9. Solaris

LDOMS and memory (PA/RA)

If I do ldm ls l ldom1 the memory block is as follows:- MEMORY RA PA SIZE 0x20000000 0x20000000 64G 0x1420000000 0x1020000000 16G 0x1c20000000 0x1420000000 16G 0x2420000000 0x1820000000 16G 0x2c20000000... (1 Reply)
Discussion started by: psychocandy
1 Replies

10. Solaris

LDoms disappeared

System: SPARC S7-2 Server; 2x8-core CPUs; 128Gb RAM; 2x600Gb HDD. I have been experimenting on the above system, using ldmp2v to create "clones" of my physical systems as LDoms on the server when there was an unscheduled power outage. After the system came back up I had lost my LDoms, although... (7 Replies)
Discussion started by: apmcd47
7 Replies

LEARN ABOUT NETBSD

txp

TXP(4)							   BSD Kernel Interfaces Manual 						    TXP(4)

NAME

     txp -- 3Com 3XP Typhoon/Sidewinder (3CR990) Ethernet interface

SYNOPSIS

     txp* at pci? dev ? function ?

DESCRIPTION

     The txp interface provides access to the 10Mb/s and 100Mb/s Ethernet networks via the 3Com Typhoon/Sidewinder chipset.  This driver supports
     the following cards:

	   o   3Com 3CR990-TX-95
	   o   3Com 3CR990-TX-97
	   o   3Com 3CR990SVR95
	   o   3Com 3CR990SVR97

     Basic Ethernet functions are provided as well as support for vlan(4) tag removal and insertion assistance, receive ip(4), tcp(4), and udp(4)
     checksum offloading, and transmit ip(4) checksum offloading.  There is currently no support for transmit tcp(4) or udp(4) checksum offload-
     ing, tcp(4) segmentation, nor ipsec(4) acceleration.  Note that hardware checksumming is only used when the interface is not in bridge(4)
     mode.

     Each of the host's network addresses is specified at boot time with an SIOCSIFADDR ioctl(2).  The txp interface employs the address resolu-
     tion protocol described in arp(4) to dynamically map between Internet and Ethernet addresses on the local network.

     When a txp interface is brought up, by default, it will attempt to auto-negotiate the link speed and duplex mode.	The speeds, in order of
     attempt, are: 100Mb/s Full Duplex, 100Mb/s Half Duplex, 10 Mb/s Full Duplex, and 10 Mb/s Half Duplex.

     The txp supports several media types, which are selected via the ifconfig(8) command.  The supported media types are:

	   media autoselect
			   Attempt to autoselect the media type (default)

	   media 100baseTX mediaopt full-duplex
			   Use 100baseTX, full duplex

	   media 100baseTX [mediaopt half-duplex]
			   Use 100baseTX, half duplex

	   media 10baseT mediaopt full-duplex
			   Use 10baseT, full duplex

	   media 10baseT [mediaopt half-duplex]
			   Use 10baseT, half duplex

SEE ALSO

     arp(4), ifmedia(4), inet(4), intro(4), ip(4), netintro(4), pci(4), tcp(4), udp(4), vlan(4), ifconfig(8)

HISTORY

     The txp driver first appeared in NetBSD 2.0.

BSD
								  August 21, 2003							       BSD
All times are GMT -4. The time now is 08:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy