Sponsored Content
Operating Systems Solaris Solaris 11 link aggregation with multiple VLANs - not working Post 303044837 by solaris_1977 on Thursday 5th of March 2020 12:16:52 AM
Old 03-05-2020
Solaris 11 link aggregation - not working - can't ping gateway

This link was helpful and I got the idea that vlanNUM would be created on OVM/hypervisor level.
I deleted VLAN interfaces, recreated aggr0 with net0 and net7. But I can't ping its gateway. I can see packets incoming from two VLANs, if I snoop on net0, net7 and aggr0.
Per network guys, their side configurations are okay, but I will check again if my configurations are looking okay.
Code:
root@ovmi-host1:~# netstat -nrv | grep default
default              0.0.0.0         192.168.244.129                 0   2 UG       0      0
root@ovmi-host1:~# ping 192.168.244.129
no answer from 192.168.244.129
root@ovmi-host1:~# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
sp-phys0: flags=100001000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,PHYSRUNNING> mtu 1500 index 2
        inet 169.254.182.77 netmask ffffff00 broadcast 169.254.182.255
        ether 2:21:28:57:47:17
aggr0: flags=100001000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,PHYSRUNNING> mtu 1500 index 3
        inet 192.168.244.161 netmask ffffffc0 broadcast 192.168.244.191
        ether 0:10:e0:e2:dc:8c
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1
        inet6 ::1/128
sp-phys0: flags=120002000840<RUNNING,MULTICAST,IPv6,PHYSRUNNING> mtu 1500 index 2
        inet6 ::/0
        ether 2:21:28:57:47:17
aggr0: flags=120002000840<RUNNING,MULTICAST,IPv6,PHYSRUNNING> mtu 1500 index 3
        inet6 ::/0
        ether 0:10:e0:e2:dc:8c
root@ovmi-host1:~#
root@ovmi-host1:~# dladm show-phys | grep up
net0            Ethernet      up         1000   full      i40e0
net1            Ethernet      up         1000   full      i40e1
net7            Ethernet      up         1000   full      igb3
net16           Ethernet      up         1000   full      vsw0
sp-phys0        Ethernet      up         10     full      usbecm2
root@ovmi-host1:~# dladm show-aggr -x
LINK       PORT           SPEED DUPLEX   STATE     ADDRESS            PORTSTATE
aggr0      --             1000Mb full    up        0:10:e0:e2:dc:8c   --
           net0           1000Mb full    up        0:10:e0:e2:dc:8c   attached
           net7           1000Mb full    up        b4:96:91:4c:ae:93  attached
root@ovmi-host1:~# dladm show-aggr -L
LINK                PORT         AGGREGATABLE SYNC COLL DIST DEFAULTED EXPIRED
aggr0               net0         yes          yes  yes  yes  no        no
--                  net7         yes          yes  yes  yes  no        no
root@ovmi-host1:~#
root@ovmi-host1:~# dladm show-link | grep up
aggr0               aggr      1500   up       net0 net7
net0                phys      1500   up       --
net1                phys      1500   up       --
net7                phys      1500   up       --
net16               phys      1500   up       --
sp-phys0            phys      1500   up       --
root@ovmi-host1:~#

Am I missing something in this config ?

Last edited by solaris_1977; 03-05-2020 at 02:03 AM.. Reason: Corrected title
 

9 More Discussions You Might Find Interesting

1. Solaris

Link Aggregation

Hi there I have a requirement to provide failover to our customer boxes in case of interface / switch failure, I have been looking at Solaris Link Aggregation with LACP and I wanted to ask a question Ive seen multiple websites that say the following Does this also mean that if the... (2 Replies)
Discussion started by: hcclnoodles
2 Replies

2. UNIX for Advanced & Expert Users

Link Aggregation and LACP

Hi there I have a requirement to provide failover to our customer boxes in case of interface / switch failure, I have been looking at Solaris Link Aggregation with LACP and I wanted to ask a question Ive seen multiple websites that say the following Does this also mean that if the... (1 Reply)
Discussion started by: hcclnoodles
1 Replies

3. AIX

Link aggregation with hacmp ?

Hi, I need to setup a hacmp cluster (my first one, we usually use VCS on AIX), but I require more network bandwith than a normal gigabit etherchannel setup can provide, so I am thinking about using linkaggregation - 2 active adapters to one switch and a single backup adapter to another switch... (4 Replies)
Discussion started by: zxmaus
4 Replies

4. Solaris

Link aggregation

Me again :) I'm trying to find a page describing the L2, L3 und L4 modes of dladm. It's nice to read "hashed by ip header", but how should I use that? On the file-server it's ok to have the six interfaces serving six clients each on it's own. But an rsync connection via switch between two... (8 Replies)
Discussion started by: PatrickBaer
8 Replies

5. IP Networking

Interface bonding / Link aggregation (Multiple)

Hello, I've been using mode 4 with four slaves, however looking at ifconfig showed that the traffic was not balanced correctly between the interfaces, the outgoing traffic has been alot higher on the last slave. Example: eth0 RX 123.2 GiB TX 22.5 GiB eth1 RX 84.8 GiB TX 8.3 GiB eth2... (3 Replies)
Discussion started by: TehOne
3 Replies

6. Solaris

solaris link aggregation problem , once i reboot it is not showing, not able to ping the default gat

Hi All, I am trying to aggregate the NIC's,(igb2 and igb3) (igb0 is used by the physical system and igb1 is used by primary-vsw0) to create the domains on that for faster data transfer, I followed the process for creating the aggregation, dladm create-aggr -d igb2 -d igb3 1 after creating the... (2 Replies)
Discussion started by: buildscm
2 Replies

7. Solaris

Link aggregation issues Solaris 10

I have setup link aggregation with 3 interfaces on my solaris 10 system. All looks good but my problem is that the traffic is only going out bge0 and not the other 2 links. bash-4.3# dladm show-aggr -s key:33 ipackets rbytes opackets obytes %ipkts %opkts ... (3 Replies)
Discussion started by: primeaup
3 Replies

8. IP Networking

Link Aggregation

Hi ihave three link of internet and iwant to put one linux front of a firewall that this three linux speard firewall such az load balance and fialover but dont close any port and protocol and only firewall have been internet what way can i use for it ? are there any script and services do that... (0 Replies)
Discussion started by: mnnn
0 Replies

9. Solaris

Solaris link aggregation not working as expected

Hi, This is Solaris-10 x86 platform. I am not able to ping gateway associated with aggr50001. I am not getting idea, where could be issue. Please advise. # netstat -nr Routing Table: IPv4 Destination Gateway Flags Ref Use Interface --------------------... (10 Replies)
Discussion started by: solaris_1977
10 Replies
routing(7)						 Miscellaneous Information Manual						routing(7)

NAME
routing - system support for local network packet routing DESCRIPTION
The network facilities for HP-UX provide general packet routing support. Routing table maintenance is handled by application processes. A routing table consists of a set of data structures used by the network facilities to select the appropriate remote host or gateway when transmitting packets. The table contains a single entry for each route to a specific network or host, as displayed by the command with the or options (see netstat(1)). Routes that are not valid are not displayed. _______________________________________________________________ # netstat -r Routing tables Destination Gateway Flags Refs Use Interface Pmtu hpindwr.cup.hp.com localhost UH 1 39 lo0 4608 localhost localhost UH 0 68 lo0 4608 147.253.56.195 localhost UH 0 0 lo0 4608 147.253.144.66 localhost UH 0 0 lo0 4608 default hpinsmh.cup.hp.com UG 1 21 lan0 1500 15.13.136 hpindwr.cup.hp.com U 1 92 lan0 1500 147.253.56 147.253.56.195 U 0 7 lan2 1500 147.253.144.64 147.253.144.66 U 0 7 lan1 1500 _______________________________________________________________ # netstat -rn Routing tables Destination Gateway Flags Refs Use Interface Pmtu 15.13.136.66 127.0.0.1 UH 1 39 lo0 4608 127.0.0.1 127.0.0.1 UH 0 68 lo0 4608 147.253.56.195 127.0.0.1 UH 0 0 lo0 4608 147.253.144.66 127.0.0.1 UH 0 0 lo0 4608 default 15.13.136.11 UG 2 30 lan0 1500 15.13.136.0 15.13.136.66 U 1 113 lan0 1500 147.253.56.0 147.253.56.195 U 0 7 lan2 1500 147.253.144.64 147.253.144.66 U 0 7 lan1 1500 _______________________________________________________________ # netstat -rv Routing tables Dest/Netmask Gateway Flags Refs Use Interface Pmtu hpindwr.cup.hp.com/0xffffffff localhost UH 1 39 lo0 4608 localhost/0xffffffff localhost UH 0 68 lo0 4608 147.253.56.195/0xffffffff localhost UH 0 0 lo0 4608 147.253.144.66/0xffffffff localhost UH 0 0 lo0 4608 default/0x00000000 hpinsmh.cup.hp.com UG 2 31 lan0 1500 15.13.136/0xfffff800 hpindwr.cup.hp.com U 1 129 lan0 1500 147.253.56/0xfffffe00 147.253.56.195 U 0 7 lan2 1500 147.253.144.64/0xfffffff0 147.253.144.66 U 0 7 lan1 1500 _______________________________________________________________ # netstat -rnv Routing tables Dest/Netmask Gateway Flags Refs Use Interface Pmtu 15.13.136.66/255.255.255.255 127.0.0.1 UH 1 39 lo0 4608 127.0.0.1/255.255.255.255 127.0.0.1 UH 0 68 lo0 4608 147.253.56.195/255.255.255.255 127.0.0.1 UH 0 0 lo0 4608 147.253.144.66/255.255.255.255 127.0.0.1 UH 0 0 lo0 4608 default/0.0.0.0 15.13.136.11 UG 3 40 lan0 1500 15.13.136.0/255.255.248.0 15.13.136.66 U 1 153 lan0 1500 147.253.56.0/255.255.254.0 147.253.56.195 U 0 8 lan2 1500 147.253.144.64/255.255.255.240 147.253.144.66 U 0 8 lan1 1500 _______________________________________________________________ The following columns are of particular interest: The destination Internet address: host name, network name, or The keyword indicates a wildcard route, used as a last resort if no route is specified for a particular remote host or network. See The netmask and the destination Internet address together define a range of IP addresses that may be reached by the route's gateway. A host route by default has a netmask of all 1's. A default route by default has a netmask of all 0's. The netmask is also used in selecting a route to forward an IP packet. See the subsection. The gateway to use to get to the destination: a remote gateway or the local host. See The type of route: The route is "up" or available (see ifconfig(1M)). The route uses a remote host as a gateway; otherwise, the local host is shown as the gateway (see route(1M)). The destination is a host; otherwise, the destination is a network (see route(1M)). The interface connections: The local loopback after system boot. The interface cards installed on the local host after the command is executed at boot time (see ifconfig(1M)). The values of the count and destination type fields in the command determine the presence of the and flags in the display and thus the route type, as shown in the following table. Count Destination Type Flags Route Type ------------------------------------------------------------- =0 network U Route to a network directly from the local host >0 network UG Route to a network through a remote host gateway =0 host UH Route to a remote host directly from the local host >0 host UGH Route to a remote host through a remote host gateway =0 default U Wildcard route directly from the local host >0 default UG Wildcard route through a remote host gateway ------------------------------------------------------------- Subnets The network facilities support variable-length subnetting. An Internet address is made up of a portion, and a portion of an address in the form: Subnet addresses are defined as a portion of the network's Internet address. This scheme provides for: o Network addresses that identify physically distinct networks. o Subnet addresses that identify physically distinct subnetworks of the same network. A network manager can subdivide the Internet address of the local network into subnets using the host number space. This facility allows several physical networks to share a single Internet address. To allow for this, three Internet classes are defined, each accommodating a different amount of network and host addresses. The address classes are defined by the most significant bit of the binary form of the address. The following table lists the number of networks, nodes, and the address ranges for each address class: Nodes per Class Networks Network Address Range -------------------------------------------------------------- A 127 16777215 0.0.0.1 - 127.225.225.254 B 16383 65535 128.0.0.1 - 191.255.255.254 C 2097151 255 192.0.0.1 - 223.244.244.243 Reserved -- -- 224.0.0.0 - 255.255.255.255 -------------------------------------------------------------- The first 8 bits of a Class A network has network space for only 127, while accommodating the largest number of nodes possible among the classes defined. A single class B network has the network address limitation of 16 bits, and 16 bits to define the nodes. For example, a Class C address space is as follows: ______________________________________ Indicates Class C Class C subnet networks portion | | --- --- 10000000.00000110.00000001.11100001 -------------------------- ----- | | Network Address Host = 192.6.1 Address = 1 ______________________________________ A subnet for a given host is specified with the command (see ifconfig(1M)), using the parameter with a 32-bit subnet mask. The default masks for the three classes of Internet addresses are as follows: Class A: 255.0.0.0 Class B: 255.255.0.0 Class C: 255.255.255.0 An example Class C network number is 192.34.17.0. The last field specifies the host number. Thus, all hosts with the prefix 192.34.17 are recognized as being on the same logical and physical network. If subnets are not in use, the default mask used is 255.255.255.0. If subnets are used and the 8-bit host field is partitioned into 3 bits of subnet and 5 bits of host as in the above example, then the sub- net mask would be 255.255.255.192. If a host has multiple interfaces, then it can belong to different subnets. Unlike past releases, the subnets can have different sizes even if they may have the same network address. This is accomplished by using a different netmask on each of the host interfaces. For example, the and interface shown in the tables above are connected to two distinct subnets of the same network, 147.253. The subnet that belongs to can have at most 14 hosts, because its netmask is 255.255.255.240. Note: The host portion of those IP addresses in the subnet cannot be all 1's or all 0's, therefore this subnet can support only 14 hosts, not 16. The subnet that belongs to can have up to 510 hosts, because its netmask is 255.255.254.0. Supernets A supernet is a collection of smaller networks. Supernetting is a technique of using the netmask to aggregate a collection of smaller net- works into a supernet. This technique is particularly useful for class C networks. A Class C network can only have 254 hosts. This can be too restrictive for some companies. For these companies, a netmask that only contains a portion of the network part can be applied to the hosts in these class C networks to form a supernet. This supernet netmask should be applied to those interfaces that connect to the supernet using the ifconfig command (see ifconfig(1M)). For example, a host can configure its interface to connect to a class C supernet, for example, 192.6, by configuring an IP address of 192.6.1.1 and a netmask of 255.255.0.0 to its interface. Routing Algorithm The routing table entries are of three types: o Entries for a specific host. o Entries for all hosts on a specific network. o Wildcard entries for any destination not matched by entries of the first two types. To select a route for forwarding an IP packet, the network facilities select the complete set of "matching" routing table entries from the routing table. A routing table entry is considered a match, if the result of the bit-wise AND operation between the netmask in the routing entry and the IP packet's destination address equals the destination address in the routing entry. The network facilities then select from the set the routing entries that have the longest netmask. The length of a netmask is defined as the number of contiguous 1 bits starting from the leftmost bit position in the 32-bit netmask field. In other words, the network facili- ties select the routing entry that specifies the narrowest range of IP addresses. For example, the host route entry that has a destina- tion/netmask pair of (147.253.56.1, 0xFFFFFFFF), is more specific than the network route entry that has a destination/netmask pair of (147.253.56.0, 0xFFFFFE00); therefore, the network facilities select the host route entry. The default route by default has a destina- tion/netmask pair of (0,0). Therefore, the default route matches all destinations but it is also the least specific. The default route will be selected only if there is not a more specific route. There may still be multiple routing entries remaining. In that case, the IP packet is routed over the first entry displayed by Such multi- ple routes include: o Two or more routes to a host via different gateways. o Two or more routes to a network via different gateways. A superuser can change entries in the table by using the command (see route(1M), or by information received in Internet Control Message Protocol (ICMP) redirect messages. If there are more than one default gateways for a particular net or subnet, each will be used in turn to effect the even distribution of datagrams to the different gateways. WARNINGS
Reciprocal commands must be executed on the local host and the destination host, as well as all intermediate hosts, if routing is to suc- ceed in the cases of virtual circuit connections or bidirectional datagram transfers. AUTHOR
was developed by the University of California, Berkeley. FILES
SEE ALSO
netstat(1), ifconfig(1M), route(1M), route(7P). routing(7)
All times are GMT -4. The time now is 07:34 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy