Summarising routes on VOSS into Area 0

In the following example we have a VOSS switch configured with OSPF with area 0 and area 100. All local VLANs with IP enabled interfaces with the exception of the broadcast VLAN are IP OSPF passive addresses with class C subnets. The switch is an ABR.

VLAN 44 with IP 44.44.44.1/24.

Vlan44 44.44.44.1 255.255.255.0 enable up 44 false disable

To summarise these /24 routes as /16 and advertise into area 0 the following command can be used: 

router ospf enable
router ospf
area 0.0.0.100
area range 0.0.0.100 44.44.0.0/255.255.0.0 summary-link advertise-mode summarize
area range 0.0.0.100 44.44.0.0/255.255.0.0 summary-link advertise-metric 10
exit

The 44.44.44.0/24 subnet is summarised as a /16.

Extract from show ip ospf lsdb command…

Summary Lsas in Area 0.0.0.0

LSTYPE LINKSTATEID ADV_ROUTER AGE SEQ_NBR CSUM

Summary 44.44.0.0 151.58.1.0 17 0x80000001 0xe3e8

Routing table of OSPF neighbour in area 0…

VSP-8284XSQ:1(config)#show ip route

DST MASK NEXT VRF/ISID COST FACE PROT AGE TYPE PRF

44.44.0.0 255.255.0.0 55.55.55.1 GlobalRouter 111 55 OSPF 0 IB 25
55.55.55.0 255.255.255.0 55.55.55.2 – 1 55 LOC 0 DB 0

2 out of 2 Total Num of Route Entries, 2 Total Num of Dest Networks displayed.

TYPE Legend:
I=Indirect Route, D=Direct Route, A=Alternative Route, B=Best Route, E=Ecmp Route,
U=Unresolved Route, N=Not in HW, F=Replaced by FTN, V=IPVPN Route, S=SPBM Route
PROTOCOL Legend:
v=Inter-VRF route redistributed
VSP-8284XSQ:1(config)#

 

 

 

 

 

 

New Extreme Fabric Best Practices from Extreme Networks

Just notice some best practice knowledge based article were posted yesterday and each one has links to other ones to complete the set.

Her is a link to one of them… Extreme Fabric Best Practice – vIST Cluster / Article Number: 000124824.

https://extreme-networks.my.site.com/ExtrArticleDetail?an=000124824

Additional notes

This document was created by a team of engineers in Professional Services, PLM, GTAC, and SE’s using: VOSS/FE 9.1.0

Extreme Fabric Best Practice – Architecture and Topology
https://extreme-networks.my.site.com/ExtrArticleDetail?an=000124842 
Extreme Fabric Best Practice – Autosense Portshttps://extreme-networks.my.site.com/ExtrArticleDetail?an=000124841 
Extreme Fabric Best Practice – Chassis Settingshttps://extreme-networks.my.site.com/ExtrArticleDetail?an=000124840 
Extreme Fabric Best Practice – DvRhttps://extreme-networks.my.site.com/ExtrArticleDetail?an=000124843
Extreme Fabric Best Practice – Fabric Extendhttps://extreme-networks.my.site.com/ExtrArticleDetail?an=000124839 
Extreme Fabric Best Practice – Fabric Managementhttps://extreme-networks.my.site.com/ExtrArticleDetail?an=000124838 
Extreme Fabric Best Practice – IP Multicasthttps://extreme-networks.my.site.com/ExtrArticleDetail?an=000124837 
Extreme Fabric Best Practice – IS-IS/OSPF Route Policieshttps://extreme-networks.my.site.com/ExtrArticleDetail?an=000124836 
Extreme Fabric Best Practice – Layer 2 VSNhttps://extreme-networks.my.site.com/ExtrArticleDetail?an=000124835 
Extreme Fabric Best Practice – Layer 3 VSNhttps://extreme-networks.my.site.com/ExtrArticleDetail?an=000124834 
Extreme Fabric Best Practice – Loop Preventionhttps://extreme-networks.my.site.com/ExtrArticleDetail?an=000124596
Extreme Fabric Best Practice – Migration Strategy
https://extreme-networks.my.site.com/ExtrArticleDetail?an=000124833 
Extreme Fabric Best Practice – Multi-Area SPBmhttps://extreme-networks.my.site.com/ExtrArticleDetail?an=000124832 
Extreme Fabric Best Practice – Onboarding and Provisioning
https://extreme-networks.my.site.com/ExtrArticleDetail?an=000124830 
Extreme Fabric Best Practice – QoShttps://extreme-networks.my.site.com/ExtrArticleDetail?an=000124844 
Extreme Fabric Best Practice – SPBm Infrastructurehttps://extreme-networks.my.site.com/ExtrArticleDetail?an=000124826 
Extreme Fabric Best Practice – Switch Selection and Features
https://extreme-networks.my.site.com/ExtrArticleDetail?an=000124825 
Extreme Fabric Best Practice – vIST Cluster
https://extreme-networks.my.site.com/ExtrArticleDetail?an=000124824

EXOS Virtual Router

Do Extreme Networks Switch Engine EXOS devices support virtualization?

Yes, they support Virtual Routers (VRs). There are three default ones known as VR-Mgmt, VR-Control and VR-Default.

VRs allow the switch to be segmented into different forwarding planes with each VR having its own routing table.

To create a new VR called blue:

create vr “blue”

To add all ports on slot 3 to VR blue:

configure vlan default delete ports 3:*
configure vr vr-default delete ports 3:*
configure vr blue add ports 3:*

After a user VR is created, the ports are added, and support for any required routing protocols is added, you can configure the VR.

To create a VLAN (Virtual LAN) in a VR, use the command:
create vlan vlan_name {description vlan-description} {vr name}

Removing route-map from BGP peer in VOSS

I have an existing BGP neighbour connection configured with a route-map that blocks a particular IP subnet in VOSS and I wish to remove it. The BGP neighbour is established in VRF green. 

My routing table shows IP network 192.168.0.0/24 is not learnt from BGP neighbour 192.168.255.1 and the route-map is doing its job for VRF green.

ip bgp neighbor 192.168.255.1 in-route-map “denysubnet”

I want to remove the route-map and learn the IP network again. 

Within the VRF green remove the route-map from the peer statement.

R1:1(config)#router vrf green
R1:1(router-vrf)#

R1:1(router-vrf)#no ip bgp neighbor 192.168.255.1 in-route-map

Restart or soft-restart the peer for the policy change to take effect

exit

R1:1(config)#ip bgp restart-bgp neighbor 192.168.255.1 vrf green soft-reconfiguration in

The routing table will now show the missing network that was filtered out by the route-map.

 

Find Extreme Networks AP305C using LED

Login to the AP and type the following command and the LED on the AP will flash off and on. Repeat to do it again.

system led power on 1 off 1 (turns on LED for 1 second and then turns off led for 1 second) (up arrow to repeat)

The LED will be on for an active AP so effectively the command makes the LED flash once! Useful way to identify the AP.

Configuring AirDefense Essentials in Cloud IQ

Configure an AP template for AirDefense which has one radio configured as a sensor on AP 4000.

Configure a Classification Rules Common Object

Configure>Common Objects>Policy>Classification Rules.

Select Add.

Enter a name for the rule ie AIR-AP-CLASSIFICATION.

Enter an optional description ie Classification Rule to use with AP template with sensor enabled.

Select Add.

Select Cloud Config Group.

Match Type Contains.

Select Add (or select existing CCG).

Enter a name for the CCG ie AIR-AP-LIST.

Enter an optional description ie CCG containing APs where AirDefense sensor is required.

Select AP(s) from the list of available APs (AP4000).

Click Save Cloud Config Group.

Click Continue.

Click Save Rule.

The Classification Rule and CCG will be available to assign to the new template added to the Network Policy.

Configure new AP template for AirDefense

Go to the Network Policy and select Wireless>AP Template.

Select Add (or copy existing template, one that has already been made and tweaked, one that is a copy of a default template which has been tailored already).

Select existing template used normally and copy it and save with a new name ie AIR-AP4000-Template.

Click Save.

Under Classification Rules column select the arrow icon which allows you to select the Classification Rule we created earlier.

Select Classification Rule called AIR-AP-CLASSIFICATION and then select LINK.

Select the AP template AIR-AP4000-Template

Click WiFi2 under Wireless Interfaces

Select sensor for Radio Usage and Save Template.

Upload Network Policy to the AP(s).

APs that are part of the CCG should have their third radio set as a sensor. APs excluded from the CCG will use their third radio as Client Access (default).

AirDefense Essentials

AirDefense Essentials requires WIPS to be turned ON.

Give WIPS a name ie WIPS-Policy and ensure Enable AirDefense Essentials is set to ON in the Network Policy. Click Save.

Once the APs are prepared and the Network Policy update is pushed out to the APs then go to Essentials and Enable AirDefense Essentials. The WIPS Policy created
for the Network Policy should be visible and in use by AirDefense Essentials.

Allow time for the sensors and AirDefense Essentials to collect data. The data is accessible and presented via the Essentials>AirDefense dashboard.