文件列表:

LICENSE (4585, 2018-06-11)
Pipfile (190, 2018-06-11)
Pipfile.lock (8005, 2018-06-11)
dnacsdk (0, 2018-06-11)
dnacsdk\__init__.py (193, 2018-06-11)
dnacsdk\__pycache__ (0, 2018-06-11)
dnacsdk\__pycache__\__init__.cpython-36.pyc (371, 2018-06-11)
dnacsdk\__pycache__\api.cpython-36.pyc (5782, 2018-06-11)
dnacsdk\__pycache__\exceptions.cpython-36.pyc (3399, 2018-06-11)
dnacsdk\__pycache__\networkDevice.cpython-36.pyc (2773, 2018-06-11)
dnacsdk\__pycache__\profile.cpython-36.pyc (3511, 2018-06-11)
dnacsdk\__pycache__\site.cpython-36.pyc (1214, 2018-06-11)
dnacsdk\__pycache__\templateProgrammer.cpython-36.pyc (3002, 2018-06-11)
dnacsdk\__pycache__\util.cpython-36.pyc (1409, 2018-06-11)
dnacsdk\__pycache__\wireless_vlan.cpython-36.pyc (3010, 2018-06-11)
dnacsdk\__pycache__\wlan.cpython-36.pyc (2541, 2018-06-11)
dnacsdk\api.py (7383, 2018-06-11)
dnacsdk\exceptions.py (1811, 2018-06-11)
dnacsdk\make_request.py (611, 2018-06-11)
dnacsdk\networkDevice.py (3477, 2018-06-11)
dnacsdk\profile.py (4486, 2018-06-11)
dnacsdk\site.py (785, 2018-06-11)
dnacsdk\templateProgrammer.py (2640, 2018-06-11)
dnacsdk\util.py (1148, 2018-06-11)
dnacsdk\wireless_vlan.py (3503, 2018-06-11)
dnacsdk\wlan.py (3105, 2018-06-11)
requirements.txt (191, 2018-06-11)
src_dnac.example (87, 2018-06-11)
wlanmgmt.py (17449, 2018-06-11)

# Project `wlanmgmt` ## Our "Intent" - Dynamic WLAN-SSID Management Consider you're a manager for a building that is capable of holding several events per day for various organizations desiring various levels of WiFi access. You would like to give each of your clients unparalleled personal service in this area because, as you know, the first thing almost everyone does when getting to a new venue is ask for the wireless credentials. Now, consider the capability of creating/deleting SSID and assigning/un-assigning the existing infrastructure in a few seconds. Also, imagine that you can change that per need immediately, or automate based on schedule, to support not just the event specific purposes but security concerns as well. Finally, think about tying that to a simple UI that does not require any underlying knowledge of how all of the setup actually works. This is where Dynamic WLAN-SSID Management comes in. More concretely, a building has several different groups attending different events on different floors, or even rooms, and they can provide ephemeral WiFi access specific to each group through an application that the building manager or other trusted party can access. Once those events are done, the application can tear down those SSIDs/WLANs limiting exposure of that building’s network. The challenge many organizations have is quickly managing this configuration without compromising the security and performance of their network for the critical business applications and work that is also going on. Expecting senior network engineers to personally address each and every request is impractical... What is needed is a way for our senior architects and engineers to define policies that can be rapidly applied to new devices when these requests are made. DNA Center offers enterprises all the tools to meet the automation and assurance needs to translate the business intent - quickly bringing new systems online - to technical intent. # Enter Project `wlanmgmt` The goal of this application is to make it a one-stop-shop of SSID creation and removal. **Example Usage:** ```bash ./onboard.py deploy --template NetworkDeviceOnboarding \ --target cat_9k_1.abc.inc \ "INTERFACE=GigabitEthernet1/1/1" \ "VLAN=3001" \ "INTERFACE_DESCRIPTION=My new interface" ``` # Requirements To leverage this application you will need: * Python 3.6+ * DNA Center 1.2+ with the DNA Center Platform API package installed. * A DNA Center account with permissions to deploy templates. # Install and Setup Clone down the code. https://github.com/CiscoDevNet/dnacenter-host-onboarding cd dnacenter-host-onboarding Setup Python Virtual Environment (requires Python 3.6+) python3.6 -m venv venv source venv/bin/activate pip install -r requirements.txt > Pipfiles are also included if you prefer to use `pipenv` Setup local environment variables for your DNA Center. *Provide the info for your DNA Center* # Examples export DNAC_IP=192.168.139.73 export DNAC_USERNAME=admin export DNAC_PASSWORD=Cisco123 > The file `src_dnac.example` is provided in the repo. You can create a local `src_dnac` file with your information and then `source src_dnac` to simplify the env setup. # Using the Application Once installed and setup, you can now get started. Investigate the built in help with the tool. ./onboard.py --help # OUTPUT Usage: onboard.py [OPTIONS] COMMAND [ARGS]... Command line tool for deploying templates to DNA Center. Options: --help Show this message and exit. Commands: deploy Deploy a template with DNA Center. device_list Retrieve and return network devices list. interface_list Retrieve the list of interfaces on a device. template_list Retrieve the deployment templates that are... Look at the available templates. Each template will provide the required parameters, what will be configured, and give an example deploy command. ./onboard.py template_list # OUTPUT Retrieving the templates available ╒═════════════════════════╤═══════════════════════╤═══════════════════════════════════════╤══════════════════════════════════════╤═══════════════════╕ │ Template Name │ Parameters │ Deploy Command │ Content │ Device Types │ ╞═════════════════════════╪═══════════════════════╪═══════════════════════════════════════╪══════════════════════════════════════╪═══════════════════╡ │ ChangeTZ │ │ ./onboard.py deploy \ │ clock timezone +10 │ Switches and Hubs │ │ │ │ --template ChangeTZ \ │ │ Routers │ │ │ │ --target DEVICE │ │ │ ├─────────────────────────┼───────────────────────┼───────────────────────────────────────┼──────────────────────────────────────┼───────────────────┤ │ NetworkDeviceOnboarding │ VLAN │ ./onboard.py deploy \ │ interface $INTERFACE │ Switches and Hubs │ │ │ INTERFACE_DESCRIPTION │ --template NetworkDeviceOnboarding \ │ description $INTERFACE_DESCRIPTION │ │ │ │ INTERFACE │ --target DEVICE \ │ switchport mode access │ │ │ │ │ "VLAN=VALUE" \ │ switchport access vlan $VLAN │ │ │ │ │ "INTERFACE_DESCRIPTION=VALUE" \ │ no shut │ │ │ │ │ "INTERFACE=VALUE" │ │ │ ├─────────────────────────┼───────────────────────┼───────────────────────────────────────┼──────────────────────────────────────┼───────────────────┤ │ ChangeDescription │ interface │ ./onboard.py deploy \ │ interface $interface │ Switches and Hubs │ │ │ description │ --template ChangeDescription \ │ ! added by DNAC │ │ │ │ │ --target DEVICE \ │ description $description │ │ │ │ │ "interface=VALUE" \ │ │ │ │ │ │ "description=VALUE" │ │ │ ╘═════════════════════════╧═══════════════════════╧═══════════════════════════════════════╧══════════════════════════════════════╧═══════════════════╛ If needed, retrieve the list of devices (with `./onboard.py device_list`) or interfaces (with `./onboard.py interface_list DEVICE_NAME`). $ ./onboard.py device_list # OUTPUT Retrieving the devices. ╒═══════════════════╤═════════════════╤═══════════════════╕ │ Hostname │ Management IP │ Family │ ╞═══════════════════╪═════════════════╪═══════════════════╡ │ asr1001-x.abc.inc │ 10.10.22.74 │ Routers │ ├───────────────────┼─────────────────┼───────────────────┤ │ cat_9k_1.abc.inc │ 10.10.22.66 │ Switches and Hubs │ ├───────────────────┼─────────────────┼───────────────────┤ │ cat_9k_2.abc.inc │ 10.10.22.70 │ Switches and Hubs │ ├───────────────────┼─────────────────┼───────────────────┤ │ cs3850.abc.inc │ 10.10.22.69 │ Switches and Hubs │ ╘═══════════════════╧═════════════════╧═══════════════════╛ Deploy a template with the tool. (Remember the template list includes a sample for how to format the command). ./onboard.py deploy --template NetworkDeviceOnboarding \ --target cat_9k_1.abc.inc \ "INTERFACE=GigabitEthernet1/1/1" \ "VLAN=3001" \ "INTERFACE_DESCRIPTION=My new interface" # OUTPUT Attempting deployment. Deployment Status: IN_PROGRESS

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：