• November 29, 2020, 04:56:29 PM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: Auto - Provisioning Policies & Wildcards ??  (Read 2984 times)

0 Members and 1 Guest are viewing this topic.

Offline donb

  • Rookie
  • **
  • Posts: 16
Auto - Provisioning Policies & Wildcards ??
« on: October 07, 2015, 11:02:47 AM »
Hi, I am following the guide WiNG 5.X How To Guide Auto - Provisioning  Policies & Wildcards

I am trying to do a LLDP match, but the document isn't 100% clear to me as to where the match takes place

I am trying to match XYZA in the first few characters of the LLDP string, is the syntax

 $LLDP[1:4]XYZA or  $XYZA[1:4]


 adopt br6511 precedence 1 profile default-br6511 rf-domain XYZA lldp-match $LLDP[1:4]XYZA

or

 adopt br6511 precedence 1 profile default-br6511 rf-domain XYZA lldp-match $XYZA[1:4]

Or am I completely wrong here?


perhaps it would take the form of

$LLDP[1:3]A ?
« Last Edit: October 07, 2015, 11:12:17 AM by donb »


Offline noobie

  • Full Member
  • ***
  • Posts: 92
Re: Auto - Provisioning Policies & Wildcards ??
« Reply #1 on: October 08, 2015, 09:00:58 AM »
Hi donb,

your rule should look like this:

adopt br6511 precedence 1 profile default-br6511 rf-domain $LLDP[1:4] any

this rule will take first 4 characters out of the hostname of the switch where AP is attached and match it against rf-domain name to provision the AP

you can also do this kind of rule if your domain name just contains part of the LLDP match:

adopt br6511 precedence 1 profile default-br6511 rf-domain SITE-$LLDP[1:4] any

Hope this helps

Offline donb

  • Rookie
  • **
  • Posts: 16
Re: Auto - Provisioning Policies & Wildcards ??
« Reply #2 on: October 08, 2015, 12:04:54 PM »
What if I wanted to allow or disallow an AP to a controller based on the LLDP information from the switch the AP is connected to?


i.e. if i wanted to match ABC1 from a wired switch but only the ABC portion but also taking into consideration of the 1 so I can differentiate between ABC1, ABC2, etc

i've tried the following with no luck:

adopt br6511 precedence 1 profile default-br6511-LLDP rf-domain default lldp-match [1:3]1
adopt br6511 precedence 1 profile default-br6511-LLDP rf-domain default lldp-match ABC1
adopt br6511 precedence 1 profile default-br6511-LLDP rf-domain default lldp-match $LLDP[1:3]1

Offline noobie

  • Full Member
  • ***
  • Posts: 92
Re: Auto - Provisioning Policies & Wildcards ??
« Reply #3 on: October 08, 2015, 03:31:22 PM »
well its very simple - if there is no match on rf-domain or profile $LLDP wildcard your APs wont get adopted. The match is happening on the wildcard itself, therefore you can safely leave last bit as "any"

In other words if you rule for example is:

adopt <model> precedence <X> profile <name> rf-domain SITE-$LLDP[3:6] any

then you have only 2 rf-domains created with names "SITE-ABC" and "SITE-DEF"

now lets image that the switch hostname is ICXABC1 and another switch hosntame is ICXBCD1.

So APs attached to the first switch will get adopted and assigned profile SITE-ABC, while APs attached to the second switch will not get adopted, as there is no rf-domain with the name SITE-BCD that would match the rule above.


Offline donb

  • Rookie
  • **
  • Posts: 16
Re: Auto - Provisioning Policies & Wildcards ??
« Reply #4 on: October 08, 2015, 04:18:55 PM »
Ah ha!

I see what you're saying now that makes perfect sense, thanks for the reply

One other question though, why can't the CDP/LLDP pulldown match fields be used though.. I have seen the examples and it seems like just as you showed me, everything is matched via RFDOMAIN/Profile

What I mean is what is  "lldp-match"  and "cdp-match" used for then?
« Last Edit: October 08, 2015, 04:39:58 PM by donb »