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


 
Thread Tools Search this Thread
Operating Systems Solaris solaris link aggregation problem , once i reboot it is not showing, not able to ping the default gat
# 1  
Old 01-17-2012
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 aggregation i created the domain using the following commands.

# ldm add-vsw net-dev=aggr1 primary-vsw1 primary
# ldm add-vcc port-range=5127-5200 primary-vcc1 primary
# svcadm enable vntsd
# ldm add-vds primary-vds1 primary

# ldm add-domain solv01ldom
# ldm set-vcpu 24 solv01ldom
# ldm set-mem 2g solv01ldom
# mkfile -nv 30G /export/ldoms/disks/solv01ldom.vdisk
# ldm add-vdsdev /export/ldoms/disks/solv01ldom.vdisk solv01vol1@primary-vds1
# ldm add-vdisk solv01vdisk1 solv01vol1@primary-vds1 solv01ldom
# ldm add-vnet vnet0 primary-vsw1 solv01ldom
# ldm set-variable auto-boot\?=true solv01ldom
# ldm set-variable boot-device=solv01vdisk1 solv01ldom
# ldm add-vdisk vdisk_iso iso_vol@primary-vds1 solv01ldom
# ldm bind-domain solv01ldom
# ldm start-domain solv01ldom
# ldm remove-vdisk -f vdisk_iso solv01ldom
# ldm list
# telnet localhost 5000
# ok show-devs
# ok devalias
# boot vdisk_iso:f

i am able install the OS, but when i choose the DHCP option to get the IP automatically it is not getting when the configuration is on vnet0 primary-vsw1 i need to manually enter the IP and all the details after entering all the details i cann't ping my default gateway

when i change to vnet0 primary-vsw0 it recognizes and gets the IP.automatically and also able to ping the default gateway.

Can you please suggest what i have to do not to disaaper the aggr1 after reboot and also recognizes the DHCP from
vnet0 primary-vsw1


**************************************************************************************************** ***************************

Below is the output of my environment setup



root@solp01 # uname -a
SunOS solp01 5.10 Generic_144488-17 sun4v sparc sun4v
==================================================================================================== ====================================
root@solp01 # ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
igb0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet x.x.76.107 netmask fffffc00 broadcast x.x.79.255
ether 0:21:28:bb:56:24
==================================================================================================== ====================================
root@solp01 # dladm show-dev
vsw0 link: up speed: 1000 Mbps duplex: full
igb0 link: up speed: 1000 Mbps duplex: full
igb1 link: up speed: 1000 Mbps duplex: full
igb2 link: up speed: 1000 Mbps duplex: full
igb3 link: up speed: 100 Mbps duplex: full
==================================================================================================== ====================================
dladm create-aggr -d igb2 -d igb3 1
dladm show-aggr -L
root@solp01 # dladm show-aggr -L
key: 1 (0x0001) policy: L4 address: 0:21:28:bb:56:27 (fixed)
LACP mode: active LACP timer: short
device activity timeout aggregatable sync coll dist defaulted expired
igb2 active short yes no no no yes no
igb3 active short yes no no no yes no

root@solp01 # dladm show-aggr
key: 1 (0x0001) policy: L4 address: 0:21:28:bb:56:27 (fixed)
device address speed duplex link state
igb2 0:21:28:bb:56:26 1000 Mbps full up attached
igb3 0:21:28:bb:56:27 100 Mbps full up standby

root@solp01 # dladm show-link
vsw0 type: non-vlan mtu: 1500 device: vsw0
vsw1 type: non-vlan mtu: 1500 device: vsw1
igb0 type: non-vlan mtu: 1500 device: igb0
igb1 type: non-vlan mtu: 1500 device: igb1
igb2 type: non-vlan mtu: 1500 device: igb2
igb3 type: non-vlan mtu: 1500 device: igb3
aggr1 type: non-vlan mtu: 1500 aggregation: key 1


ifconfig aggr1 x.x.76.112 netmask x.x.79.255 up
dladm modify-aggr -PL4 -l active 1

root@solp01 # ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
igb0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet x.x.76.107 netmask fffffc00 broadcast x.x.79.255
ether 0:21:28:bb:56:24
aggr1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
inet x.x.76.112 netmask fffffc00 broadcast x.x.79.255
ether 0:21:28:bb:56:27
==================================================================================================== =====================================
root@solp01 # dladm show-dev -s -i 2
ipackets rbytes ierrors opackets obytes oerrors
vsw0 1284250 1699607254 0 286406 24057653 0
ipackets rbytes ierrors opackets obytes oerrors
vsw0 50 4628 0 2 134 0
ipackets rbytes ierrors opackets obytes oerrors
vsw0 46 4459 0 1 70 0
ipackets rbytes ierrors opackets obytes oerrors
vsw0 62 5617 0 0 0 0
ipackets rbytes ierrors opackets obytes oerrors
vsw0 50 4888 0 0 0 0
ipackets rbytes ierrors opackets obytes oerrors
vsw0 56 5200 0 0 0 0
ipackets rbytes ierrors opackets obytes oerrors
vsw0 45 4249 0 2 134 0
ipackets rbytes ierrors opackets obytes oerrors
vsw0 65 6007 0 11 916 0
ipackets rbytes ierrors opackets obytes oerrors
vsw0 49 4113 0 0 0 0
ipackets rbytes ierrors opackets obytes oerrors
vsw0 40 3882 0 0 0 0
ipackets rbytes ierrors opackets obytes oerrors
vsw0 44 4807 0 0 0 0
ipackets rbytes ierrors opackets obytes oerrors
vsw0 64 5959 0 2 134 0

==================================================================================================== =====================================

root@solp01 # ldm list-config
factory-default
primary-with-clients
primary-with-clients-2 [next poweron]

==================================================================================================== ====================================

root@solp01 # ldm list-services
VCC
NAME LDOM PORT-RANGE
primary-vcc0 primary 5000-5126
primary-vcc1 primary 5127-5200

VSW
NAME LDOM MAC NET-DEV ID DEVICE LINKPROP DEFAULT-VLAN-ID PVID VID MTU MODE
primary-vsw0 primary 00:14:4f:fa:78:21 igb1 0 switch@0 1 1 1500
primary-vsw1 primary 00:14:4f:fb:3c:40 aggr1 1 switch@1 1 1 1500

VDS
NAME LDOM VOLUME OPTIONS MPGROUP DEVICE
primary-vds0 primary vol1 /export/ldoms/disks/ldg1.vdisk
vol0 /export/ldoms/disks/ldg0.vdisk
vol2 /export/ldoms/disks/ldg2.vdisk
iso_vol /export/solarisdvd.iso
primary-vds1 primary solv01vol1 /export/ldoms/disks/solv01ldom.vdisk

==================================================================================================== =======================================
root@solp01 # ldm list
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -n-cv- UART 10 2G 1.0% 13m
ldg0 active -t---- 5000 24 5888M 4.2% 1h 51m
ldg1 active -n---- 5001 24 5888M 4.2% 3h 19m
ldg2 active -n---- 5002 24 5888M 0.0% 3h 19m
solv01ldom active -n---- 5003 24 2G 0.0% 2h 32m


==================================================================================================== ======================================

root@solp01 # ldm list-bindings ldg0
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
ldg0 active -t---- 5000 24 5888M 4.2% 1h 53m

UUID
d0939248-340a-ca41-803c-8e3afe3cd0bd

MAC
00:14:4f:fa:7c:9d

HOSTID
0x84fa7c9d

CONTROL
failure-policy=ignore

DEPENDENCY
master=

CORE
CID CPUSET
1 (8, 9, 10, 11, 12, 13, 14, 15)
2 (16, 17, 18, 19, 20, 21, 22, 23)
3 (24, 25, 26, 27, 28, 29, 30, 31)

VCPU
VID PID CID UTIL STRAND
0 8 1 100% 100%
1 9 1 0.0% 100%
2 10 1 0.0% 100%
3 11 1 0.0% 100%
4 12 1 0.0% 100%
5 13 1 0.0% 100%
6 14 1 0.0% 100%
7 15 1 0.0% 100%
8 16 2 0.0% 100%
9 17 2 0.0% 100%
10 18 2 0.0% 100%
11 19 2 0.0% 100%
12 20 2 0.0% 100%
13 21 2 0.0% 100%
14 22 2 0.0% 100%
15 23 2 0.0% 100%
16 24 3 0.0% 100%
17 25 3 0.0% 100%
18 26 3 0.0% 100%
19 27 3 0.0% 100%
20 28 3 0.0% 100%
21 29 3 0.0% 100%
22 30 3 0.0% 100%
23 31 3 0.0% 100%

MEMORY
RA PA SIZE
0x10000000 0xa0000000 5888M

VARIABLES
auto-boot?=true
auto-boot\?=true
autoboot\?=true
boot-device=disk:a
keyboard-layout=US-English
vdisk0=

NETWORK
NAME SERVICE ID DEVICE MAC MODE PVID VID MTU LINKPROP
vnet0 primary-vsw0@primary 0 network@0 00:14:4f:fb:da:e6 1 1500
PEER MAC MODE PVID VID MTU LINKPROP
primary-vsw0@primary 00:14:4f:fa:78:21 1 1500
vnet0@ldg1 00:14:4f:fa:36:bc 1 1500
vnet0@ldg2 00:14:4f:fb:28:1c 1 1500

DISK
NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
vdisk0 vol0@primary-vds0 0 disk@0 primary

VCONS
NAME SERVICE PORT
ldg0 primary-vcc0@primary 5000

==================================================================================================== ============

root@solp01 # ldm list-bindings ldg1
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
ldg1 active -n---- 5001 24 5888M 4.2% 3h 22m

UUID
e74e232f-cf3c-60dd-a0b8-9933568b240c

MAC
00:14:4f:f8:e5:7f

HOSTID
0x84f8e57f

CONTROL
failure-policy=ignore

DEPENDENCY
master=

CORE
CID CPUSET
4 (32, 33, 34, 35, 36, 37, 38, 39)
5 (40, 41, 42, 43, 44, 45, 46, 47)
6 (48, 49, 50, 51, 52, 53, 54, 55)

VCPU
VID PID CID UTIL STRAND
0 32 4 0.3% 100%
1 33 4 0.0% 100%
2 34 4 0.0% 100%
3 35 4 0.0% 100%
4 36 4 0.0% 100%
5 37 4 0.0% 100%
6 38 4 100% 100%
7 39 4 0.0% 100%
8 40 5 0.0% 100%
9 41 5 0.1% 100%
10 42 5 0.0% 100%
11 43 5 0.1% 100%
12 44 5 0.0% 100%
13 45 5 0.1% 100%
14 46 5 0.0% 100%
15 47 5 0.1% 100%
16 48 6 0.6% 100%
17 49 6 0.0% 100%
18 50 6 0.0% 100%
19 51 6 0.0% 100%
20 52 6 0.0% 100%
21 53 6 0.0% 100%
22 54 6 0.0% 100%
23 55 6 0.0% 100%

MEMORY
RA PA SIZE
0x10000000 0x210000000 5888M

VARIABLES
auto-boot\?=true
boot-device=disk:a vdisk0
keyboard-layout=US-English

NETWORK
NAME SERVICE ID DEVICE MAC MODE PVID VID MTU LINKPROP
vnet0 primary-vsw0@primary 0 network@0 00:14:4f:fa:36:bc 1 1500
PEER MAC MODE PVID VID MTU LINKPROP
primary-vsw0@primary 00:14:4f:fa:78:21 1 1500
vnet0@ldg0 00:14:4f:fb:da:e6 1 1500
vnet0@ldg2 00:14:4f:fb:28:1c 1 1500

DISK
NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
vdisk0 vol1@primary-vds0 0 disk@0 primary

VCONS
NAME SERVICE PORT
ldg1 primary-vcc0@primary 5001

==================================================================================================== ============
root@solp01 # ldm list-bindings ldg2
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
ldg2 active -n---- 5002 24 5888M 0.0% 3h 23m

UUID
6f861ea9-d2d2-c5d3-c527-cc5c1966bce7

MAC
00:14:4f:f8:00:0b

HOSTID
0x84f8000b

CONTROL
failure-policy=ignore

DEPENDENCY
master=

CORE
CID CPUSET
8 (64, 65, 66, 67, 68, 69, 70, 71)
9 (72, 73, 74, 75, 76, 77, 78, 79)
10 (80, 81, 82, 83, 84, 85, 86, 87)

VCPU
VID PID CID UTIL STRAND
0 64 8 0.2% 100%
1 65 8 0.0% 100%
2 66 8 0.0% 100%
3 67 8 0.1% 100%
4 68 8 0.0% 100%
5 69 8 0.1% 100%
6 70 8 0.0% 100%
7 71 8 0.0% 100%
8 72 9 0.0% 100%
9 73 9 0.0% 100%
10 74 9 0.0% 100%
11 75 9 0.0% 100%
12 76 9 0.0% 100%
13 77 9 0.0% 100%
14 78 9 0.0% 100%
15 79 9 0.2% 100%
16 80 10 0.0% 100%
17 81 10 0.0% 100%
18 82 10 0.0% 100%
19 83 10 0.0% 100%
20 84 10 0.0% 100%
21 85 10 0.1% 100%
22 86 10 0.1% 100%
23 87 10 0.0% 100%

MEMORY
RA PA SIZE
0x10000000 0x380000000 5888M

VARIABLES
auto-boot?=true
boot-device=disk:a vdisk0
keyboard-layout=US-English

NETWORK
NAME SERVICE ID DEVICE MAC MODE PVID VID MTU LINKPROP
vnet0 primary-vsw0@primary 0 network@0 00:14:4f:fb:28:1c 1 1500
PEER MAC MODE PVID VID MTU LINKPROP
primary-vsw0@primary 00:14:4f:fa:78:21 1 1500
vnet0@ldg1 00:14:4f:fa:36:bc 1 1500
vnet0@ldg0 00:14:4f:fb:da:e6 1 1500

DISK
NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
vdisk0 vol2@primary-vds0 0 disk@0 primary

VCONS
NAME SERVICE PORT
ldg2 primary-vcc0@primary 5002

==================================================================================================== ============
root@solp01 # ldm list-bindings solv01ldom
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
solv01ldom active -n---- 5003 24 2G 0.0% 2h 38m

UUID
63bfc691-62d4-c858-c7ff-88dbced3ea80

MAC
00:14:4f:f9:c3:99

HOSTID
0x84f9c399

CONTROL
failure-policy=ignore

DEPENDENCY
master=

CORE
CID CPUSET
11 (88, 89, 90, 91, 92, 93, 94, 95)
12 (96, 97, 98, 99, 100, 101, 102, 103)
13 (104, 105, 106, 107, 108, 109, 110, 111)

VCPU
VID PID CID UTIL STRAND
0 88 11 0.2% 100%
1 89 11 0.0% 100%
2 90 11 0.0% 100%
3 91 11 0.0% 100%
4 92 11 0.0% 100%
5 93 11 0.0% 100%
6 94 11 0.0% 100%
7 95 11 0.0% 100%
8 96 12 0.0% 100%
9 97 12 0.1% 100%
10 98 12 0.0% 100%
11 99 12 0.0% 100%
12 100 12 0.0% 100%
13 101 12 0.0% 100%
14 102 12 0.0% 100%
15 103 12 0.0% 100%
16 104 13 0.0% 100%
17 105 13 0.0% 100%
18 106 13 0.0% 100%
19 107 13 0.0% 100%
20 108 13 0.0% 100%
21 109 13 0.0% 100%
22 110 13 0.0% 100%
23 111 13 0.0% 100%

MEMORY
RA PA SIZE
0x10000000 0x4f0000000 2G

VARIABLES
auto-boot?=true
boot-device=disk:a solv01vdisk1
keyboard-layout=US-English

NETWORK
NAME SERVICE ID DEVICE MAC MODE PVID VID MTU LINKPROP
vnet0 primary-vsw1@primary 0 network@0 00:14:4f:f9:9f:e6 1 1500
PEER MAC MODE PVID VID MTU LINKPROP
primary-vsw1@primary 00:14:4f:fb:3c:40 1 1500

DISK
NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
solv01vdisk1 solv01vol1@primary-vds1 0 disk@0 primary
vdisk_iso iso_vol@primary-vds0 1 disk@1 primary

VCONS
NAME SERVICE PORT
solv01ldom primary-vcc0@primary 5003

==================================================================================================== =================================================
# 2  
Old 01-18-2012
1. please use CODE tags!

2. you have to handle an aggr set just like any other NIC. to make it persitant you've to create a file in /etc/hostname.aggr1 for example.
# 3  
Old 01-18-2012
Thanks Duke,

for responding to my question

I created the file /etc/hostname.aggr1 and added the following ip address X.X.79.112, when i rebooted the system, i am not able to ssh to the physical system then i went thru console and deleted the file /etc/hostname.aggr1 and rebooted again it came back i can ssh, don't know why it is causing problem when i add the /etc/hostname.aggr1.

Can you suggest where i am doing wrong.

Thanks
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

How can I test link aggregation?

Hi, I have Solaris-10 server and link aggregation is configured on this in below way # dladm show-aggr key: 1 (0x0001) policy: L4 address: 3c:d9:2b:ee:a8:a (auto) device address speed duplex link state bnx1 3c:d9:2b:ee:a8:a... (8 Replies)
Discussion started by: solaris_1977
8 Replies

2. 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

3. UNIX for Advanced & Expert Users

Bonding IEEE 802.3ad Dynamic link aggregation : Bond showing less than desired throughput

Hi All, I have done IEEE 802.3ad Dynamic link aggregation bond configuration with name bond0 which has 4 slaves (each 25GB/s) in it on cent os 6.8. Issue i am facing is bonding throughput is only 50GB/s not 100GB/s. below are the configuration files : DEVICE=bond0 IPADDR=xx.xx.xx.xx... (1 Reply)
Discussion started by: omkar.jadhav
1 Replies

4. 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

5. 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

6. HP-UX

Break Link Aggregation in HP UX.

Hi, I want to Break the Link Aggregation. My aggregation are lan0+lan1 = lan900. Now I want to break this and put the IP in lan0. But i have cluster environment and this is the main database server. So It need to change in cluster script. But I dont know where I have to change it. Please... (1 Reply)
Discussion started by: mkiron
1 Replies

7. 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

8. HP-UX

Link Aggregation HPUX

Hi, Hoping someone can offer some advice on something i have not dealt with before. We have a server that seems to have some very strange configuration done on it. It has 2 physical NIC's and rather than both be aggregated into LAN900 we have 1 in LAN900 and 1 in LAN901? (See Below)... (2 Replies)
Discussion started by: Andyp2704
2 Replies

9. 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
Login or Register to Ask a Question