Parnassus was asking if you were truly creating a port-channel (Trunk on 3810, and Lag on 8360). These take two interfaces on the same device and make a bonded logical interface.
If you are looking to just create a trunk as in a port that carries multiple vlans, then there is no need for the trunk or lag commands. For instance lets say your default or untagged vlan is 50. You also want to carry traffic for vlan 10, 11, and 12 on the same link. You would do the following:
On the 3810:
config t
vlan 50 untagged 15
vlan 10-12 tagged 15
On the 8360:
config t
interface 1/1/19
no routing
vlan trunk native 50
vlan trunk allowed 10-12,50
------------------------------
Dustin Burns
Senior Mobility and Access Engineer @WEI
ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2021
If my post was useful accept solution and/or give kudos
------------------------------
Original Message:
Sent: Jun 03, 2021 11:53 AM
From: Adnan Khan
Subject: HP Aruba 3810 uplink to HP Aruba 8360.
Is the usage of LAG (Link Aggregation Group) on Aruba 8360 and Port Trunking (Links Aggregation) on Aruba 3810 intentional? I mean...you're using just on physical port per side...that's a simple link (no necessity to setup a LAG/Port Trunking).
In any case the Port Trunking on Aruba 3810 shouldn't be of type "trunk" but it should be instead of type "lacp" (to match the LAG type on Aruba 8360 side).
Yes, LAG 19 on Aruba 8360 and try to port trunk on Aruba 3810.
Let me explain. On HP Aruba 8360 core switch port number 19 . I assigned to LAG 19.
On HP Aruba 3810 Port 15 I want to link with hp aruba 8360 on port 19.
So should I create port 15 on hp aruba 3810 like this as follow.
trunk 15 trk15 lacp
I am new to hp and don't know how to establish this link between core switch 8360 and 3810 sw.
------------------------------
Adnan Khan
Original Message:
Sent: Jun 03, 2021 11:44 AM
From: Davide Poletto
Subject: HP Aruba 3810 uplink to HP Aruba 8360.
Is the usage of LAG (Link Aggregation Group) on Aruba 8360 and Port Trunking (Links Aggregation) on Aruba 3810 intentional? I mean...you're using just on physical port per side...that's a simple link (no necessity to setup a LAG/Port Trunking).
In any case the Port Trunking on Aruba 3810 shouldn't be of type "trunk" but it should be instead of type "lacp" (to match the LAG type on Aruba 8360 side).
------------------------------
Davide Poletto
Original Message:
Sent: Jun 03, 2021 11:29 AM
From: Adnan Khan
Subject: HP Aruba 3810 uplink to HP Aruba 8360.
I assigned interface 19 to lag 19 on core switch.
HP Aruba 3860
CoreSW# show run int lag 19
interface lag 19
no shutdown
no routing
vlan trunk native 50
vlan trunk allowed all
lacp mode active
exit
CoreSW# show run int 1/1/19
interface 1/1/19
no shutdown
description Link To AOA
lag 19
exit
---------------------------------------
HP Aruba 3810
vlan 1
name "DEFAULT_VLAN"
no untagged 15
untagged 12-14,Trk1-Trk11,Trk16,Trk15
ip address 172.22.x.x 255.255.255.0
ipv6 enable
ipv6 address dhcp full
exit
trunk 15 trk15 trunk
vlan 50
name "Management"
untagged 15
ip address 172.30.x.x 255.255.255.0
exit
Can you check the 3810 trunk configuration. I am sure there's something wrong on sw 3810 trunk port configuration.
------------------------------
Adnan Khan
Original Message:
Sent: Jun 03, 2021 06:29 AM
From: Dustin Burns
Subject: HP Aruba 3810 uplink to HP Aruba 8360.
Also, on the 3810 side, make sure you are untagging VLAN 50 on trunk 15 to match the native VLAN on the 8360 side.
------------------------------
Dustin Burns
Senior Mobility and Access Engineer @WEI
ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2021
If my post was useful accept solution and/or give kudos
Original Message:
Sent: Jun 03, 2021 01:04 AM
From: Adnan Khan
Subject: HP Aruba 3810 uplink to HP Aruba 8360.
Hi there
I have HP Aruba 3810 on one end and HP Aruba 8360 on the other end . I created a lag interface on 8360 sw for the trunk port to hp 3810. Here's the configuration
HP Aruba 8360:
interface lag 19
no shutdown
no routing
vlan trunk native 50
vlan trunk allowed all
lacp mode active
HP Aruba 3810:
trunk 15 trk15 trunk
But it doesn't ping. How can we create a trunk port at hp aruba 3810 switch to connect with core switch hp aruba 8360.?
Regards
Khan
The content of this email is considered privileged. If you are not its intended recipient, please notify the sender and delete all copies immediately.