Wired Intelligent Edge

 View Only
last person joined: yesterday 

Bring performance and reliability to your network with the HPE Aruba Networking Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of your switching devices, and find ways to improve security across your network to bring together a mobile-first solution
Expand all | Collapse all

2930F JL261A to 6300M JL661A - link not passing data...

This thread has been viewed 12 times
  • 1.  2930F JL261A to 6300M JL661A - link not passing data...

    Posted 11 days ago


    I have an Aruba JL661A 6300M. It is running OSPF for routing and has several VLANs setup and running its own DHCP-Server on a few of those VLANs.

    I have a 2930F JL261A that will be running its own DHCP-Server as well. 

    I am trying to connect the two, the 2930F will be more of an access switch. I only have 3 VLANs on it. 1, 2 and 3. I have interface 28 configured as a trunk that is untagged on VLAN 1 and tagged on VLAN 2 and 3 (2 and 3 are doing their own DHCP-Server). 

    On the 6300M, I have a LAG created. VLAN 1 is native and allowed all. 

    I am able to see the other sides (sho cdp neigh det and sho lldp neighbor-info). I am picking up an IP from my DHCP-Server on the switch so I know that is working. I am not able to get out to the internet or ping the 6300M and vice versa to the 2930F. I think it is something with how I have the connection between the two set up. 


    interface LAG 1

    desc XXXX

    no shut

    no routing

    vlan trunk native 1

    vlan trunk allowed all

    lacp mode active

    On the 2930F:

    VLAN 1 untagged trk28 and VLAN 2 and 3 tagged trk28. 

    I think I am getting confused with terms between the two OS, but I believe I have both setup as a "trunk". The 6300M is running OSPF and I want to say I don't need to do any OSPF config on the 2930F, but I am not sure...

  • 2.  RE: 2930F JL261A to 6300M JL661A - link not passing data...

    Posted 11 days ago
    I don't understand the (usage of) OSPF on a Switch which is not acting as a Router (necessarily for eventually working with OSPF, I mean) when it acts just as a Layer 2 switch to which some VLAN IDs are extended (isn't this the role of the Aruba 2930F?)...but, first of all, don't fall in a trap due to the different meaning given to the word "trunk" in each Switch OS grammar (AOS-CX versus AOS-S): trunk on AOS- CX means passing more VLAN IDs (as you did) while on AOS-S it means aggregating physical ports.

    I see you did both things on both sides (aggregating with LACP: lag1 to Trk28 AND matching the VLAN ownerships on logical interfaces lag1 and Trk28) so, apparently, physical connectivity, logical connectivity and VLAN interfaces' ownerships all match.

    The question is: you really have aggregated links interconnecting both switches?

  • 3.  RE: 2930F JL261A to 6300M JL661A - link not passing data...

    Posted 10 days ago

    I was trying the OSPF just to see if that would work, I've been going back and forth with this the last 2-3 days...

    The plan was that my 6300M JL661A was going to be doing the OSPF. This 2930F JL261A was going to be acting more like an access switch.

    I know the cabling and transceivers are good. It is something with my configurations. As of right now I have some connectivity between the two switches....

    On the 6300M JL661A I have configured the following:

    vlan 100

    desc XXXX

    interface vlan 100

    desc XXXX

    ip address xxx.xxx.xxx.6/30

    ip ospf 1 area

    no ip ospf passive


    interface lag 10

    no shut

    desc XXXX

    no routing

    vlan trunk native 100

    vlan trunk allowed all


    interface 1/1/52

    desc XXXX lag 10


    On the 2930F JL 261A I have the following configured:

    trunk 28 trk28 lacp

    Vlan 100

    name XXXX

    untagged trk28

    ip address xxx.xxx.xxx.5

    ip ospf xxx.xxx.xxx.5 area backbone

    I am able to ping both sides of the vlan.  I do not see anything in the routing tables. I cannot ping anything else either.... 

  • 4.  RE: 2930F JL261A to 6300M JL661A - link not passing data...

    Posted 10 days ago
    You have a connectivity through useless (or partially useful) LAGs/Port Trunk: a LAG/Port Trunk made by just one physical interface is not a proper LAG/Port Trunk indeed there is no "aggregation", it behaves like a single physical interface while being born as a logical interface trying to operate (it's the real nature of a LAG/Port Trunk) as an aggregation of physical interfaces to offer enhanced resiliency/throughput.

    Technically speaking it could work for testing purposes (to have a partially useful LAG/Port Trunk).

    If you found issues at higher protocol levels (Layer 3) being pretty sure lower leves are very fine (Layer 1 and Layer 2), you should then troubleshoot that particular level: I expect that a ping from an host connected to the Aruba 2930F done against the SVI on the Aruba 6300M will work, provided that VLAN membership and transport along the" Aruba 6300M and Aruba 2930F chain" is already fine.