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
- SDN Apps
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, yes, 5412zl should do inter-vlan routing just check if the command 'ip routing' is in ...
yes, 5412zl should do inter-vlan routing just check if the command 'ip routing' is in your configuration.
If not you have to enable it and then create some interfaces vlan (L3) that operates as the networks default gateways.
interface vlan 10
ip address 10.10.10.1 255.255.255.0
Note: If you enable 'ip routing' you have to erase the 'default gateway' command on the switch
This is always hard to anwser since there are a lot of different factors that can be depended on th...
This is always hard to anwser since there are a lot of different factors that can be depended on this. More or less a rule of thumb can be more than 20% is excessive in a network segement.
Super! Can you now maybe try the following? interface 23-24 broadcast-limit ...
Can you now maybe try the following?
interface 23-24 broadcast-limit 11 <#percentage you need>
-or- at least try
broadcast-limit 11 <#percentage you need>
A high capcity swithing fabric is integrated in the backplane. Therefore it's an active backplane. ...
A high capcity swithing fabric is integrated in the backplane. Therefore it's an active backplane. But the product is designed for redudancy due to fact of dual management and redudant power supplies options. The latency between the ports is also really low. Hope this anwsers your questions. Regards, Dobias
You need the following two entries to trigger the redirect: Radius:IETF NAS-Filter-Rule = deny in...
You need the following two entries to trigger the redirect:
Radius:IETF NAS-Filter-Rule = deny in tcp from any to any 80 cpy Radius:IETF NAS-Filter-Rule = deny in tcp from any to any 443 cpy
Also, you may want to consider using user-roles instead. Much easier.
Unfortunately, 802.1x is "link local" which means that the first switch that sees an EAPol fram nee...
Unfortunately, 802.1x is "link local" which means that the first switch that sees an EAPol fram needs to do something with it or "eat" it. That means a client typically needs to be directly connected to the switch that does 802.1x. You could make the 205 port as dumb as possible and make it trusted to just allow traffic to get from the 3500 to the 205, to make sure things are correctly configured.
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, 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.