Search the Community
- ClearPass Recipe Review
- ClearPass Recipe Submission
- Admin Tool - Assign Role in Bulk
- Admin Tool - User Search
- CWNP Conf 2015
- Airheads Conference Vegas 2015
- Wlan Pro Conference 2015
- Airheads Conference Shanghai 2014
- WLAN Pro Conf EU 2014
- CWNP Conference 2014 (Sep 22 - 24)
- Airheads Local 2014
- Wireless Field Day 7 (Aug 6-8, 2014)
- Black Hat 2014 Contest
- Airheads EMEA Italy 2014 (June 9 - 13)
- Americas Airheads Conference 2014
- WLAN Professionals Summit 2014
- Airheads Roadshow 2013
- EMEA Airheads Conference 2013
- APJ Airheads Conference 2013
- Americas Airheads Conference 2013
- Americas Airheads Conference 2012
- APJ Airheads Conference 2012
- EMEA Airheads Conference 2012
- Airheads EMEA 2012 Contest: How to Enter - Contest Terms & Conditions
- Airheads EMEA 2012 Contest: Create your Entry to Win Here!
- Airheads Conferences Prior to 2012
- Americas Airheads Local Events 2012
- EMEA Airheads Local Events 2012
- Wireless Field Day 3 @ Aruba Networks
- Wireless Tech Field Day 2- Silicon Valley
- Wi-Fi Mobility Symposium- San Jose, CA USA
You need to confige a SNMP read string on the HPE switch and then put that into airwave. That...
You need to confige a SNMP read string on the HPE switch and then put that into airwave. That is all that you should need. The amp-server command is something additional, but not is what is necessary.
snmp-server community "public"
Hi, the 2530 switch is an L2 only switch you shoud change it by a 2930F or 3810 that supports L3 fe...
Hi, the 2530 switch is an L2 only switch you shoud change it by a 2930F or 3810 that supports L3 features (PBR, RIP, OSPF, static routing and inter vlan routing).
If you want a ring topology you should configure Spanning Tree but it is hard to maintain and can cause loops.
Hi, I hope this will help 1) At first please erase the default gateway command because you...
Hi, I hope this will help
1) At first please erase the default gateway command because you are doing routing and your default static route is configured. That is causing the problem.
no ip default-gateway 10.1.12.2
After that please erase from port 24 all the tagged vlans just maintain vlan 10 untag. That beause it is not a trunk (dot1q) is an L3 connection through the firewall.
2) There is no an exact place to configure the IP address to manage the stack. As I understand from your configuration VLAN 10 is your Management IT LAN so you have to configure an IP address from that VLAN on the switch. The way to do it is:
#Enter configuration mode
#Create an L3 interface (SVI)
interface vlan 10
#Configure an IP address to that SVI VLAN 10 interface
ip address 10.1.12.x 255.255.255.0
# Create a default gateway to your core via vlan 10
ip default-gateway 10.1.12.1
After that you will access the VSF cluster management through that vlan 10 ip address.
Try and let me know if that helps.
Hello, The SDN Controller has to be on a different subnet as the member vlans. There are...
The SDN Controller has to be on a different subnet as the member vlans. There are valid reasons to separate the controller traffic from the data. It is common practice to have a separate control plane and dataplane. This ensures that data plane performance does not interfere with control traffic. In addition, also consider the security risks. Users of that VLAN can access the controller as well because control plane and dataplane are on the same VLAN.
This means that you have to create a VLAN for data traffic and a VLAN for control traffic. From the drawing I can see that you have a class C network, so what you can do is split up the class C. You can use a /30 on the controller VLAN and a /25 on the data VLAN. This means that you will lose 50% of your addressing space. You can potentially solve this by adding IP addresses with /26 /27 /28 /29 /30. You will still lose some IP addresses though for network/broadcast and IP address assignment to the switches of these subnets (lose 28 IP addresses). You also have to consider the additional routing for the added subnets.
For LLDP-MAD the following must be supported by the neighbor switch: - IP-address reachable from V...
For LLDP-MAD the following must be supported by the neighbor switch:
- IP-address reachable from VSF
VSF system performs a number of checks to verify if all requirements have been met. You can verfify with "show vsf lldp-mad parameters" the "MAD readiness status".
=> therefore there is no need for an Aruba/HPE switch if the above is supported.
Hi Kamikaze, Aruba OS-Switch doesn't support any other key exchange algorithms ...
Aruba OS-Switch doesn't support any other key exchange algorithms other than “diffie-hellman-group14-sha1” for SSH Connections by default. Any SSH client will have to support the same key exchange algorithm to the switch.
TECHNICAL MARKETING ENGINEER – ARUBA CAMPUS TECHNOLOGIES
O: +1 916 540 1748 | firstname.lastname@example.org
8000 FOOTHILLS BLVD | ROSEVILLE, CA 95747 USA
you can use "isolate-list" feature on the vlan. Isolate-list feature creates a list of isolate...
you can use "isolate-list" feature on the vlan. Isolate-list feature creates a list of isolated ports for the VLAN. Traffic received on isolated ports will not be forwarded to other isolated ports in the VLAN. Traffice will be forwarded only to non-isolated ports on that vlan.For example if ports a1-a23 is part of vlan 1,and if "isolate-list" is created with ports a1-a22, then ports a1-a22 will not be able to talk to each other. only port a23 can talk to a1-a22.
HP-Switch-5406Rzl2(vlan-1)# isolate-list a1-a22