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
pmadm(1M)                                                                                                                                pmadm(1M)

NAME
pmadm - port monitor administration SYNOPSIS
pmadm -a [-p pmtag | -t type] -s svctag -i id -m pmspecific -v ver [ -f xu] [-y comment] [-z script] pmadm -r -p pmtag -s svctag pmadm -e -p pmtag -s svctag pmadm -d -p pmtag -s svctag pmadm -l [-t type | -p pmtag] [-s svctag] pmadm -L [-t type | -p pmtag] [-s svctag] pmadm -g -p pmtag -s svctag [-z script] pmadm -g -s svctag -t type -z script pmadm is the administrative command for the lower level of the Service Access Facility hierarchy, that is, for service administration. A port may have only one service associated with it although the same service may be available through more than one port. In order to uniquely identify an instance of a service, the pmadm command must identify both the port monitor or port monitors through which the ser- vice is available (-p or -t) and the service (-s). See . pmadm performs the following functions: o adds or removes a service o enables or disables a service o installs or replaces a per-service configuration script o prints requested service information Any user on the system may invoke pmadm to request service status (-l or -L) or to print per-service configuration scripts (-g without the -z option). pmadm with other options may be executed only by a privileged user. The following options are supported: -a Add a service. pmadm adds an entry for the new service to the port monitor's administrative file. Because of the complexity of the options and arguments that follow the -a option, it may be convenient to use a command script or the menu system to add services. -d Disable a service. Add x to the flag field in the entry for the service svctag in the port monitor's administrative file. This is the entry used by port monitor pmtag. See the -f option, below, for a description of the flags available. -e Enable a service. Remove x from the flag field in the entry for the service svctag in the port monitor administrative file. This is the entry used by port monitor pmtag. See the -f option, below, for a description of the flags available. -f xu The -f option specifies one or both of the following two flags which are then included in the flag field of the entry for the new service in the port monitor's administrative file. If the -f option is not included, no flags are set and the default conditions prevail. By default, a new service is enabled and no utmpx entry is created for it. An -f option without a following argument is illegal. x Do not enable the service svctag available through port monitor pmtag. u Create a utmpx entry for service svctag available through port monitor pmtag. -g Print, install, or replace a per-service configuration script. The -g option with a -p option and a -s option prints the per-service configuration script for service svctag available through port monitor pmtag. The -g option with a -p option, a -s option, and a -z option installs the per-service configuration script contained in the file script as the per-service configuration script for service svctag available through port monitor pmtag. The -g option with a - s option, a -t option, and a -z option installs the file script as the per-service configuration script for service svctag available through any port monitor of type type. Other combinations of options with -g are invalid. -i id id is the identity that is to be assigned to service svctag when it is started. id must be an entry in /etc/passwd. -l The -l option requests service information. Used by itself and with the options described below, it provides a filter for extracting information in several different groupings. -l By itself, the -l option lists all services on the system. -l -p pmtag Lists all services available through port monitor pmtag. -l -s svctag Lists all services with tag svctag. -l -p pmtag-ssvctag Lists service svctag. -l -t type Lists all services available through port monitors of type type. -l -t type-ssvctag Lists all services with tag svctag available through a port monitor of type type. Other combinations of options with -l are invalid. -L The -L option is identical to the -l option except that output is printed in a condensed format. -m pmspecific pmspecific is the port monitor-specific portion of the port monitor administrative file entry for the service. -p pmtag Specifies the tag associated with the port monitor through which a service (specified as -s svctag) is available. -r Remove a service. When pmadm removes a service, the entry for the service is removed from the port monitor's administrative file. -s svctag Specifies the service tag associated with a given service. The service tag is assigned by the system administrator and is part of the entry for the service in the port monitor's administrative file. -t type Specifies the port monitor type. -v ver Specifies the version number of the port monitor administrative file. The version number may be given as -v 'pmspec -V` where pmspec is the special administrative command for port monitor pmtag. This special command is ttyadm for ttymon and nlsadmin for listen. The version stamp of the port monitor is known by the command and is returned when pmspec is invoked with a -V option. -y comment Associate comment with the service entry in the port monitor administrative file. -z script Used with the -g option to specify the name of the file that contains the per-service configuration script. Modifying a configuration script is a three-step procedure. First a copy of the existing script is made (-g alone). Then the copy is edited. Finally, the copy is put in place over the existing script (-g with -z). Options that request information write the requested information to the standard output. A request for information using the -l option prints column headers and aligns the information under the appropriate headings. In this format, a missing field is indicated by a hyphen. A request for information in the condensed format using the -L option prints the information in colon-separated fields; missing fields are indicated by two successive colons. # is the comment character. Example 1: Adding a Service to a Port Monitor with the Tag pmtag The following command adds a service to a port monitor with tag pmtag and gives the service the tag svctag. The port monitor-specific information is generated by specpm. The service defined by svctag will be invoked with identity root. pmadm -a -p pmtag -s svctag -i root -m `specpm -a arg1 -b arg2`-v `specpm -V` Example 2: Adding a Service with Service Tab svctag The following command adds a service with service tag svctag, identity guest, and port monitor-specific information generated by specpm to all port monitors of type type: pmadm -a -s svctag -i guest -t type -m `specpm -a arg1 -b arg2`-v `specpm -V` Example 3: Removing a Service The following command removes the service svctag from port monitor pmtag: pmadm -r -p pmtag -s svctag Example 4: Enabling a Service The following command enables the service svctag available through port monitor pmtag: pmadm -e -p pmtag -s svctag Example 5: Disabling a Service The following command disables the service svctag available through port monitor pmtag: pmadm -d -p pmtag -s svctag Example 6: Listing Status Information The following command lists status information for all services: pmadm -l Example 7: Listing Status Information The following command lists status information for all services available through the port monitor with tag ports: pmadm -l -p ports Example 8: Listing Status Information in Condensed Format The following command lists the status information for all services available through the port monitor with tag ports in condensed format: pmadm -L -p ports Example 9: Listing Status Information for All Services List status information for all services available through port monitors of type listen: pmadm -l -t listen Example 10: Printing the per-service Configuration The following command prints the per-service configuration script associated with the service svctag available through port monitor pmtag: pmadm -g -p pmtag -s svctag The following exit values are returned: 0 Successful operation. >0 Operation failed. /etc/saf/pmtag/_config /etc/saf/pmtag/svctag /var/saf/pmtag/* See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ sac(1M), sacadm(1M), doconfig(3NSL), attributes(5) 10 Nov 1998 pmadm(1M)
All times are GMT -4. The time now is 11:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy