Sponsored Content
Operating Systems Solaris Guest LDOMS on same subnet cant ping eachother Post 302938325 by selectstar on Saturday 14th of March 2015 11:08:49 AM
Old 03-14-2015
Hi Peasant, again, I cant thank you enough for your input.

So what we actually have is a t5-2 which has two sockets, 2x two port FC Cards and 4x gigabit Ethernet ports.

As you said the machine is split right down the middle with each root complex owning exactly half of the hardware including local Hard drives.

What we have is:
1x Primary Control domain (Control, IO, Service). Obviously all LDOMS are managed from the Primary.

1x Secondary (Or what some people call 'Alternate') IO, Service domain which can see bare metal Storage.


Im sure im telling you what you already know but it help me explain it out Smilie The idea of us have two IO, service domains (Priamry and Secondary) is that we can actually take one of them down (i.e for patching) and all Guest LDOMS will continue to run, route traffic in/out, see LUNS etc.

And this is the case. When i init 6 or shutdown the primary LDOM, all Guests continue to operate via the Secndary (Alternate) Domain. And vice-a-versa.



So when I create a guest LDOM, i make sure to create two VNET's, one pointing to the Primary VSW and the other to the Secondary VSW. And when creating new LDOMS, i alterante which switch vnet0 point to so that all traffic does always go through one switch.

And this is the same principle for DISKS, i use multipathing groups (MPGROUP) to ensure that guest can see LUNs from both IO, SERVICE domains.


I think you are correct about the IPMP guest settings, I am just reading up more about that.

I also don't pretend to completely understand the difference between the trunk policies (L2, L3 etc.). I am also doing some more reading on that.


FYI, we also have some T5-2 servers which not only have 2x two port FC cards but also 2x two port ehternet cards in addition to the 4x on board ethernet ports. These serers follow the same principle as the on i use in the original post, but onviously each root complex has 4 ethernet ports each for the trunk.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix TCP/IP ping to other subnet

I have Digital UNIX V4.0B (Rev. 564) on alpha machine. I'm trying to acces network in subnet (192.168.1.x). Ip on Alpha comp. is from 192.168.3.X subnet. My default gateway on this network is 192.168.3.1 and it working OK from other machines. This machine is visible from same subnet... (2 Replies)
Discussion started by: ermingut
2 Replies

2. IP Networking

Migrating existing Subnet to a new subnet and changing ip addresses in UNIX

Hi, My project needs to migrate the existing Subnet (255.255.255.0) to a new subnet and change the ipaddresses (currently C class). How can I do that. I need some information. John (0 Replies)
Discussion started by: johnmarsh
0 Replies

3. Solaris

LDoms can't ping each other

I've got Sun Fire T2000 with two LDoms - primary and ldom1, both being Solaris 10 u8. Both can be accessed over the network (ssh, ping), both can access the network, but they can't ping or ssh to each other. I only use e1000g0 interface on T2000, the primary ldom has an address on it, ldm has a... (1 Reply)
Discussion started by: mludvig
1 Replies

4. Shell Programming and Scripting

Bash script for ping in your own subnet

I have a question for one who wants to help me. I want to create a bash script to ping IP-adresses. It must first ask me the beginnen IP, then the ending IP like: 192.168.100.1 - 192.168.100.255. When nothing is filled in, then it must find my subnet and ping that, like when my ip is... (14 Replies)
Discussion started by: ugurgazi
14 Replies

5. Programming

putting numbers behind eachother

I want to make a program where you have to insert binary numbers like this: do { iBinary = getche(); }while(iBinary == 1 || iBinary == 0); after you get the numbers I want them to be placed behind eachother so you will get: input: 1 1 0 1 output: 1101 (7 Replies)
Discussion started by: metal005
7 Replies

6. Solaris

Migrating Solaris 8, 9 to Guest Domains (LDOMs)

Hi Everyone, one question is it possible to migrate a physical standalone Solaris 8 or 9 OS to Guest Domain (LDOMs). If yes, can someone please provide steps to migrate these OS to LDOMs. Thanks, Kartheek. (1 Reply)
Discussion started by: bobby320
1 Replies

7. Linux

Ping check failed from Nagios master server on windows hosts in the same subnet

Hello All, We have added a windows host and its config files to Nagios master server and wanted to do a ping check alone at the moment however, the nagios master server identifies the host in its GUI and immediately disappears can anyone let me know the right approach to this one, We want to... (2 Replies)
Discussion started by: lovesaikrishna
2 Replies

8. Solaris

Help needed - trying to run commands in Guest LDoms from Control LDOM

Hi Folks, I am used to writing scripts to get info by running commands at local zones level from their respective global zone by using zlogin <localzone> "command>" while remaining at the global zone level. Can the same be done with Guest LDoms while remaining at the control LDOM level? ... (4 Replies)
Discussion started by: momin
4 Replies

9. Linux

Unable to ping Linux guest from win7 host

Hi, I am using win7 on my PC and installed VMware on it on which i am running linux I am unable to ping my linux guest from my win machine, but i can ping my windows host from linux guest : Below is my system configuration Linux root@localhost ~]# ifconfig eth0 Link... (9 Replies)
Discussion started by: chander_1987
9 Replies

10. IP Networking

Loop in /24 Subnet, No ping beyond .1 and .2

Running 3650 switch. I have this odd issue where I cannot get 4 new Centos 7 boxes pinging out on public IPs (nor pinging in), only gateway .1 and first public IP .2 This is what I see, which doesn't look normal. How do I fix this? The server itself is configured fine (Centos 7) # cat... (0 Replies)
Discussion started by: Bashed
0 Replies
STAPVIRT(1)						      General Commands Manual						       STAPVIRT(1)

NAME
stapvirt - prepare libvirt domains for systemtap probing SYNOPSIS
stapvirt [-c URI] [-d PATH] [-v] COMMAND ARGUMENTS DESCRIPTION
The stapvirt program can be used to add ports to domains managed by libvirt (see <http://libvirt.org/>). These ports can then be used by stap to run scripts inside the domains (see the '--remote' option in stap(1) for more information). Starting from libvirt v1.1.1 and QEMU v0.10.0, SystemTap ports can be hotplugged and thus domains do not require any preparation using stapvirt. The 'query' command can be used to determine whether hotplugging is supported. If hotplugging is not supported, then ports must be added to the definition of the domain using the 'port-add' command. These ports can later be removed using the 'port-remove' command. Note that there can only be as many simultaneous stap sessions as there are ports. OPTIONS
The following options are supported. Any other option prints a short help message. -c URI Specify the libvirt driver URI to which to connect (e.g. 'qemu:///system'). The default value is NULL, which indicates to libvirt to connect to the default driver. See the page at <http://libvirt.org/uri.html> for supported values. -d PATH Specify the directory in which UNIX sockets should be created when SystemTap ports are added. The default directory is '/var/lib/libvirt/qemu'. -v Increase verbosity. This option may be repeated for more verbosity. COMMANDS
The following commands are recognized by stapvirt. Any other command prints a short help message. help Display the help message. list List available domains. port-add DOMAIN Add a permanent SystemTap port to the domain's definition. If the domain is currently running, it must be restarted before changes take effect. port-list DOMAIN List the UNIX socket paths of the permanent SystemTap ports in the domain's definition. port-remove DOMAIN Remove a permanent SystemTap port from the domain's definition. If the domain is currently running, it must be restarted before changes take effect. query DOMAIN Display the following information about the domain: its name, its UUID, its state, the number of permanent SystemTap ports in- stalled, and whether hotplugging is supported. TUTORIAL
This tutorial will help you get started with stapvirt. Let's start by listing all the privileged domains on the machine with the list com- mand: $ stapvirt -c 'qemu:///system' list Available domains on URI 'qemu:///system': ID State Type Name 2 running persistent TestVM Note that we specified the libvirt URI using the -c switch. Otherwise libvirt might have defaulted to e.g. 'qemu:///session'. Rather than typing the URI everytime, it might be easier to instead set the LIBVIRT_DEFAULT_URI environment variable and omit the -c switch. Note that this is a libvirt functionality (see <libvirt.org/uri.html> for more details). The list command indicates that we have a running domain named 'TestVM' with ID 2. Let's use the query command to retrieve more informa- tion: $ stapvirt query TestVM # by name $ stapvirt query 2 # by ID Name: TestVM UUID: 905951c0-fa4f-409b-079c-c91ddda27028 State: running ID: 2 Type: persistent Permanent Ports: 0 Hotplugging: not supported The query command gives us some basic information about the domain, such as its name, UUID, and state. More importantly, it gives us two pieces of information: the number of permanent ports installed, and whether hotplugging is supported. Technically, hotplugging support de- pends on libvirt and qemu, and is not related to the domain in itself. If hotplugging were supported, we could stop here and run stap directly. Since in our case hotplugging is not supported, we need to add SystemTap ports. To do this, we use the port-add command: $ stapvirt port-add TestVM Added new port org.systemtap.stapsh.0 The domain must be restarted before changes take effect. We can confirm that a port was added by running the query command again: $ stapvirt query TestVM ... Permanent Ports: 1 Hotplugging: not supported It now indicates that there is 1 permanent port. We can also use the port-list command to know exactly where the port will be created: $ stapvirt port-list TestVM /var/lib/libvirt/qemu/TestVM.org.systemtap.stapsh.0.sock After stopping and restarting the domain, we are now ready to use the port with stap: $ stap -e 'probe begin { printf("Hello from TestVM! "); exit() }' --remote=libvirt://TestVM Hello from TestVM! Finally, if we'd like to remove the port, we can use the port-remove command: $ stapvirt port-remove TestVM Removed port org.systemtap.stapsh.0 The domain must be restarted before changes take effect. And that's all there is to it! SEE ALSO
stap(1) BUGS
Use the Bugzilla link of the project web page or our mailing list. http://sourceware.org/systemtap/,<systemtap@sourceware.org>. STAPVIRT(1)
All times are GMT -4. The time now is 11:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy