Sponsored Content
Operating Systems Solaris Solaris 11 2nd nic for different subnet Post 302898114 by ad101 on Friday 18th of April 2014 05:37:29 PM
Old 04-18-2014
Question Solaris 11 2nd nic for different subnet

I have a Solaris 11 machine with 2 network cables attached. The first one is the default route and is working okay. I am trying to activate the second on another subnet, but am sure missing something.

The first one is on 10.30.128. and with it everything works fine,
but when I try to add the second to 10.30.134. subnet, all hosts on that subnet become inaccessible, and of course the second address is not reachable from outside.

Here's the details, I started with:
Code:
# ipadm
NAME              CLASS/TYPE STATE        UNDER      ADDR
lo0               loopback   ok           --         --
   lo0/v4         static     ok           --         127.0.0.1/8
   lo0/v6         static     ok           --         ::1/128
net0              ip         ok           --         --
   net0/v4        static     ok           --         10.30.128.22/24

# route -p show
persistent: route add default 10.30.128.126

I then added
Code:
# ipadm create-ip net1
# ipadm create-addr -T static -a 10.30.134.22/24 net1/v4
# route add 10.30.134.0/24 10.30.134.126

After this, nothing in the .134 subnet is visible, and I cannot ping the second address from outside.

Do I need to restart anything?
output of ipadm and netstat after the changes are below.

Thanks for your help.

Code:
# ipadm
NAME              CLASS/TYPE STATE        UNDER      ADDR
lo0               loopback   ok           --         --
   lo0/v4         static     ok           --         127.0.0.1/8
   lo0/v6         static     ok           --         ::1/128
net0              ip         ok           --         --
   net0/v4        static     ok           --         10.30.128.22/24
net1              ip         ok           --         --
   net1/v4        static     ok           --         10.30.134.22/24


# netstat -rn

Routing Table: IPv4
  Destination           Gateway           Flags  Ref     Use     Interface
-------------------- -------------------- ----- ----- ---------- ---------
default              10.30.128.126        UG        4      23339
10.30.128.0          10.30.128.22         U         8    5947865 net0
10.30.134.0          10.30.134.126        UG        2         11
10.30.134.0          10.30.134.22         U         3         28 net1
127.0.0.1            127.0.0.1            UH        2       2532 lo0

# dladm show-phys
LINK              MEDIA                STATE      SPEED  DUPLEX    DEVICE
net1              Ethernet             up         100    full      igb1
net3              Ethernet             unknown    0      unknown   igb3
net0              Ethernet             up         100    half      igb0
net2              Ethernet             unknown    0      unknown   igb2
net6              Ethernet             up         100    half      vsw0
net5              Ethernet             up         10     full      usbecm2

 

8 More Discussions You Might Find Interesting

1. IP Networking

add route to a subnet - Solaris 2.6

WE are running Unix - Solaris 2.6, we create a subnet. In the windows enviroment we are able to add a static route by using route add -p 172.16.10.0 mask 255.255.255.0 172.16.17.224, but when we add the route in Solaris as route add -net 172.16.10.0 255.255.255.0 172.16.17.224, we receive an... (5 Replies)
Discussion started by: cassy
5 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

NIC drivers+solaris 10

Installed solaris 10 and now i want to connect to internet,to make work this i need to NIC drivers can some body tell me is it possible to get drivers and how to install. I am dying to get rid of this problem..please help me (1 Reply)
Discussion started by: srinivas2828
1 Replies

4. Solaris

x86 Solaris 10 nic driver added but not attached. NIC is not detected.

I couldn't install my nic in solaris 10. I compiled and added the driver but failed to attach the driver and ifconfig output shows only loopback dev. Please see the following output and tell me whether my nic has been detected and why the driver failed to attach? My nic is detected in linux... (0 Replies)
Discussion started by: vectrum
0 Replies

5. Solaris

Changing the subnet mask on solaris 10

Hello, can anyone help me with the command to change the subnet mask on solaris 10? The mask is currently 255.255.255.255 I will like to change it to 255.255.2555.0. Thank you (5 Replies)
Discussion started by: cjashu
5 Replies

6. Solaris

Solaris 2nd nic for different subnet

posted this on the other sub-forum https://www.unix.com/unix-for-dummies-questions-and-answers/246504-solaris-11-2nd-nic-different-subnet.html apologies if linking is not appropriate Thanks for your help. (0 Replies)
Discussion started by: ad101
0 Replies

7. Linux

Add two different subnet public IPs to single NIC or two different NIC on same box

Hello Admins, My ask is how can I add two different subnet IPs to same box with two different gateways? The issue is I can connect to the box when I am on ethernet LAN, but I am not able to connect to the same IP when I am on wifi. The server is RHEL 7 VM on vmware. How can I get connected... (4 Replies)
Discussion started by: snchaudhari2
4 Replies

8. UNIX for Advanced & Expert Users

Changing single path NIC to a teamed connection in same subnet

Dear all, I have a remote CentOS7 server that has two network cards. Each card has four ports and port one of card one was defined with the IP address assigned to the server. So far, so good and it's been working for over a year. We have now got cables sorted out so there are four paths... (4 Replies)
Discussion started by: rbatte1
4 Replies
AGGREGATE(1)                                                  General Commands Manual                                                 AGGREGATE(1)

NAME
aggregate - optimise a list of route prefixes to help make nice short filters SYNOPSIS
aggregate [-m max-length] [-o max-opt-length] [-p default-length] [-q] [-t] [-v] DESCRIPTION
Takes a list of prefixes in conventional format on stdin, and performs two optimisations to attempt to reduce the length of the prefix list. The first optimisation is to remove any supplied prefixes which are superfluous because they are already included in another supplied pre- fix. For example, 203.97.2.0/24 would be removed if 203.97.0.0/17 was also supplied. The second optimisation identifies adjacent prefixes that can be combined under a single, shorter-length prefix. For example, 203.97.2.0/24 and 203.97.3.0/24 can be combined into the single prefix 203.97.2.0/23. OPTIONS
-m max-length Sets the maximum prefix length for entries read from stdin max_length bits. The default is 32. Prefixes with longer lengths will be discarded prior to processing. -o max-opt-length Sets the maximum prefix length for optimisation to max-opt-length bits. The default is 32. Prefixes with longer lengths will not be subject to optimisation. -p default-length Sets the default prefix length. There is no default; without this option a prefix without a mask length is treated as invalid. Use -p 32 -m 32 -o 32 to aggregate a list of host routes specified as bare addresses, for example. -q Sets quiet mode -- instructs aggregate never to generate warning messages or other output on stderr. -t Silently truncate prefixes that seem to have an inconsistent prefix: e.g. an input prefix 203.97.2.226/24 would be truncated to 203.97.2.0/24. Without this option an input prefix 203.97.2.226/24 would not be accepted, and a warning about the inconsistent mask would be generated. -v Sets verbose mode. This changes the output format to display the source line number that the prefix was obtained from, together with a preceding "-" to indicate a route that can be suppressed, or a "+" to indicate a shorter-prefix aggregate that was added by aggre- gate as an adjacency optimisation. Note that verbose output continues even if -q is selected. DIAGNOSTICS
Aggregate exits 0 on success, and >0 if an error occurs. EXAMPLES
The following list of prefixes: 193.58.204.0/22 193.58.208.0/22 193.193.160.0/22 193.193.168.0/22 193.243.164.0/22 194.126.128.0/22 194.126.132.0/22 194.126.134.0/23 194.151.128.0/19 195.42.240.0/21 195.240.0.0/16 195.241.0.0/16 is optimised as followed by aggregate (output shown using the -v flag): aggregate: maximum prefix length permitted will be 24 [ 0] + 193.58.204.0/21 [ 1] - 193.58.204.0/22 [ 2] - 193.58.208.0/22 [ 3] 193.193.160.0/22 [ 4] 193.193.168.0/22 [ 5] 193.243.164.0/22 [ 0] + 194.126.128.0/21 [ 6] - 194.126.128.0/22 [ 7] - 194.126.132.0/22 [ 8] - 194.126.134.0/23 [ 9] 194.151.128.0/19 [ 10] 195.42.240.0/21 [ 0] + 195.240.0.0/15 [ 11] - 195.240.0.0/16 [ 12] - 195.241.0.0/16 Note that 193.58.204.0/22 and 193.58.208.0/22 were combined under the single prefix 193.58.204.0/21, and 194.126.134.0/23 was suppressed because it was included in 194.126.132.0/22. The number in square brackets at the beginning of each line indicates the original line num- ber, or zero for new prefixes that were introduced by aggregate. The output without the -v flag is as follows: 193.58.204.0/21 193.193.160.0/22 193.193.168.0/22 193.243.164.0/22 194.126.128.0/21 194.151.128.0/19 195.42.240.0/21 195.240.0.0/15 SEE ALSO
aggregate-ios(1) HISTORY
Aggregate was written by Joe Abley <jabley@mfnx.net>, and has been reasonably well tested. It is suitable for reducing customer prefix fil- ters for production use without extensive hand-proving of results. Autoconf bits were donated by Michael Shields <michael.shields@mfn.com>. The -t option was suggested by Robin Johnson <rob- bat2@fermi.orbis-terrarum.net>, and the treatment of leading zeros on octet parsing was changed following comments from Arnold Nipper <arnold@nipper.de>. An early version of aggregate would attempt to combine adjacent prefixes regardless of whether the first prefix lay on an appropriate bit boundary or not (pointed out with great restraint by Robert Noland <rnoland@2hip.net>). BUGS
Common unix parsing of IPv4 addresses understands the representation of individual octets in octal or hexadecimal, following a "0" or "0x" prefix, respectively. That convention has been deliberately disabled here, since resources such as the IRR do not follow the convention, and confusion can result. For extremely sensitive applications, judicious use of the -v option together with a pencil and paper is probably advisable. Joe Abley 2001 November 2 AGGREGATE(1)
All times are GMT -4. The time now is 09:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy