VTEvent
Overview
VTEvent is for one-off events.
It can be used to get event staff or users online.
It is an open network.
It can be a hidden or visible network.
There is also an AP group for rapid deploy units.
Scope and Purpose
Often, there are events on campus where the standard networks are not suitable.
VTEvent fills this gap.
Deployments have a fixed start and end date/time.
Hidden Example
For example, during Relay4Life, the support staff needs a network in the
Drillfield.
Adding the VT Open WiFi network would not be suitable, as a rapid deployment
unit would not be suitable for the density of clients.
In this example, the hidden version of VTEvent should be deployed.
Visible example
Another example would be the SANS and VT-Hacks events, where the attendees need
to get all manner of hackerish and IoT devices online.
Normally, the registered device service would suit, but since this is an event,
we cannot guarantee everyone is a VT affiliate with access to the registered
device service.
In this example, the visible version of VTEvent should be deployed.
Support
This is a very simple service.
There is no authentication.
The VLAN/subnet is the same as is used for the other wireless services
(vlan-users).
As such, the most likely place for something to go wrong is communication.
Here are a few cases where something is most likely to go awry.
Hidden SSID
The SSID may be hidden.
If so, the customer will need to type in the SSID exactly correct,
case sensitive.
There is no punctuation or any unexpected characters.
For reference, the SSID is VTEvent
Limited time
Is it before the event started? Is the event over? If so, the network may not be broadcasting. It goes up and down at the times agreed upon by the customer and NEO.
Down APs
Unlike the other two examples, this one is a technical issue, not a communications issue. Usually, if the network is hidden, it will be on its own APs. As such, the problem may not be as obvious as normal. If the network is visible, it is probably broadcast from the same APs as the standard networks. This should help in determining if the APs are up.
Deployment and Cleanup
The nature of these events is that they are one offs, so it is easy to miscommunicate or leave cruft.
Communicate with the customer
Be sure to communicate with the customer what the name of the SSID is, and if the network is hidden. If deploying the hidden version, the customer will need to type it in, so be verbose. Remember that SSIDs are case sensitive!
Don't do it manually
Doing it manually is a sure way to forget the cleanup. Use an existing tool to deploy and cleanup the service. NetMRI is an excellent choice.
Create an ECO
Create an ECO for when the service is deployed and keep it open until it has been removed. Double check the tool really did clean up the service before closing the ECO.
AOS config
aaa profile
Both variations use the aaa profile aaa-open.
This is has no layer 2 nor layer 3 authentication.
The VLAN is undefined (it is set by the virtual-ap profile).
ssid-profile
There are two SSID profiles:
ssid-VTEventssid-VTEvent-hiddenBoth use the ESSIDVTEvent, with the normal data rates used elsewhere. The only difference is thatssid-VTEvent-hiddenis hidden.
virtual-ap profile
There are two virtual-ap profiles:
vap-VTEventvap-VTEvent-hiddenAgain, they are exactly the same, exceptvap-VTEvent-hiddenusesssid-VTEvent-hidden. Both have no authentication (layer 2 nor layer 3), and use the normal wireless VLAN.
ap-group
There are two AP groups for rapid deployment:
apg-vteventapg-vtevent-hidden
The only virtual-ap configured is the appropriate VTEvent virtual-ap.
These AP groups are optimized for outdoor use (see the config below for
details).
Configuration
/md/vt
{
"aaa_prof": [
{
"default_user_role": {
"role": "ur-open"
},
"profile-name": "aaa-open"
}
],
"ssid_prof": [
{
"a_basic_rates": {
"12": "12"
},
"a_beacon_rate": {
"a_phy_rate": "12"
},
"a_tx_rates": {
"12": "12",
"18": "18",
"24": "24",
"36": "36",
"48": "48",
"54": "54"
},
"advertise_ap_name": {},
"essid": {
"essid": "VTEvent"
},
"g_basic_rates": {
"12": "12"
},
"g_beacon_rate": {
"g_phy_rate": "12"
},
"g_tx_rates": {
"12": "12",
"18": "18",
"24": "24",
"36": "36",
"48": "48",
"54": "54"
},
"max_clients": {
"max-clients": 150
},
"mcast_rate_opt": {},
"profile-name": "ssid-vtevent"
},
{
"a_basic_rates": {
"12": "12"
},
"a_beacon_rate": {
"a_phy_rate": "12"
},
"a_tx_rates": {
"12": "12",
"18": "18",
"24": "24",
"36": "36",
"48": "48",
"54": "54"
},
"advertise_ap_name": {},
"deny_bcast": {},
"essid": {
"essid": "VTEvent"
},
"g_basic_rates": {
"12": "12"
},
"g_beacon_rate": {
"g_phy_rate": "12"
},
"g_tx_rates": {
"12": "12",
"18": "18",
"24": "24",
"36": "36",
"48": "48",
"54": "54"
},
"hide_ssid": {},
"max_clients": {
"max-clients": 150
},
"mcast_rate_opt": {},
"profile-name": "ssid-vtevent-hidden"
}
],
"virtual_ap": [
{
"aaa_prof": {
"profile-name": "aaa-open"
},
"drop_mcast": {},
"profile-name": "vap-vtevent",
"ssid_prof": {
"profile-name": "ssid-vtevent"
},
"vlan": {
"vlan": "vlan-user"
}
},
{
"aaa_prof": {
"profile-name": "aaa-open"
},
"drop_mcast": {},
"profile-name": "vap-vtevent-hidden",
"ssid_prof": {
"profile-name": "ssid-vtevent-hidden"
},
"vlan": {
"vlan": "vlan-user"
}
}
]
}
/md/vt/swva
{
"ap_a_radio_prof": [
{
"eirp_max": {
"eirp-max": 127
},
"eirp_min": {
"eirp-min": 127
},
"profile-name": "rpa-outdoor"
}
],
"ap_g_radio_prof": [
{
"eirp_max": {
"eirp-max": 127
},
"eirp_min": {
"eirp-min": 127
},
"profile-name": "rpg-outdoor"
}
],
"ap_group": [
{
"dot11a_prof": {
"profile-name": "rpa-outdoor"
},
"dot11g_prof": {
"profile-name": "rpg-outdoor"
},
"profile-name": "apg-vtevent",
"reg_domain_prof": {
"profile-name": "rdp-blacksburg"
},
"virtual_ap": [
{
"profile-name": "vap-vtevent"
}
]
},
{
"dot11a_prof": {
"profile-name": "rpa-outdoor"
},
"dot11g_prof": {
"profile-name": "rpg-outdoor"
},
"profile-name": "apg-vtevent-hidden",
"reg_domain_prof": {
"profile-name": "rdp-blacksburg"
},
"virtual_ap": [
{
"profile-name": "vap-vtevent-hidden"
}
]
}
]
}