network components, Uncategorized

OSPF limitation on Aruba 3810M-16SFP+ (JL075)

Per test result, on the mentioned switch (on firmware KB.16.05.0011) it is not possible to add more than 8 summary routes per one OSPF area (all other summary statements for the area will be rejected):

OSPF_limitation_on_JL075

Based on that, Aruba 3810M-16SFP+ (JL075) better not to choose if it is expected more than 8 summary routes per one OSPF area. Due to such limitation more prefixes may come to provider, which will do charging per package defining prefixes amount.

network components, network design, wireless topics

Connection of Cisco WLC and Aruba switch

It is a fact that Cisco WLCs per their design supports only LAG type or protocol which has no negotiation (in this aspect LAG considered as non-LACP and non-PaGP etherchannel technique, in some documentation though LAG (link aggregation groups) may be considered as a general term for all types of protocols to build etherchannel ). LAG on Cisco switches can be recognized by null in the “protocol” field, as shown below:

etherchannel Pic.1 – Po1,Po2 – LAG etherchannels

In Lab environment following hardware was used and connected:

etherchannel for cisco WLC

Pic.2 – Lab topology to test LAG support by Aruba switch

Configuration on Cisco WLCs (enabled LAG) and on Aruba core2  L3 switch are shown below:

LAG_WLC

Pic3 – LAG settings on WLC1

LACP_Aruba

Pic4 – LACP configuration and verification on Aruba core2  L3 switch

Ping and SSH from core1 to WLC via such etherchannel were successful. Per such example, Aruba automatically negotiates LACP or LAG based on what is configured on the other end.