VTEvent

Important

The configuration for this was removed on 2026-01-29, as we are pretty sure this service has been superseded by VT Open WiFi. This documents what the service would look like, rough edges and subtleties included, if we need to spin it back up (which will probably happen with little notice).

One decision that would need to be made is what network devices land on:

• Unauthenticated: use aaa-vtopenwifi; strong preference for this as the devices are actually unauthenticated (unless registered)
• Authenticated: use aaa-authenticated

Overview

VTEvent is for one-off events to get the support staff online when we are not able to also provide connectivity to the large crowd. It is a hidden open network.

For example, during Relay4Life, the support staff needs a network in the Drillfield. Adding the VT Open WiFi network may not be suitable, as a rapid deployment unit would not be suitable for the density of clients.

Support

This is a very simple service. There is no authentication. The VLANs/subnets are the same as is used for VT Open WiFi (vlan-unauthenticated and, if registered, vlan-authenticated). 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

Because the SSID is hidden, 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, the network will be on its own APs. As such, the problem may not be as obvious as normal.

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 that the network is hidden. Because the network is hidden, the customer will need to type it in, so be verbose. Remember that SSIDs are case sensitive!

Create Jira tasks

When we deploy the network, or create a Jira task to deploy it, also create the task to shut it down, and put a fixed due date on it.

AOS config

aaa profile

aaa-vtopenwifi:

• Probably use this, see opening note
• See VT Open WiFi authentication for details.

aaa-authenticated:

• If we must

ssid-profile

ssid-vtevent:

• ESSID: VTEvent
• Hidden
• Normal data rates used elsewhere

virtual-ap profile

vap-vtevent:

• Just the aaa and ssid profiles from above

ap-group

apg-vtevent:

• For outdoor rapid deployment
• Virtual APs:
  • vap-vtevent
• dot11a: rp5-outdoor
• dot11g: rp2-outdoor
• Regulatory domain: rdp-blacksburg

apg-<bldg>-vtevent:

• For indoor deployment
• Unlikely to be needed; strongly consider another solution
• Virtual APs:
  • vap-vtevent
• dot11a: match apg-<bldg>
• dot11g: match apg-<bldg>
• Regulatory domain: rdp-blacksburg

Configuration

/md/vt

{
    {
      "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": 255
      },
      "mcast_rate_opt": {},
      "profile-name": "ssid-vtevent"
    }
  ],
  "virtual_ap": [
    {
      "aaa_prof": {
        "profile-name": "aaa-vtopenwifi"
      },
      "drop_mcast": {},
      "profile-name": "vap-vtevent",
      "ssid_prof": {
        "profile-name": "ssid-vtevent"
      }
    }
  ]
}

/md/vt/swva

{
  "ap_group": [
    {
      "dot11a_prof": {
        "profile-name": "rp5-outdoor"
      },
      "dot11g_prof": {
        "profile-name": "rp2-outdoor"
      },
      "profile-name": "apg-vtevent",
      "reg_domain_prof": {
        "profile-name": "rdp-blacksburg"
      },
      "virtual_ap": [
        {
          "profile-name": "vap-vtevent"
        }
      ]
    }
  ]
}