80
EPICenter Concepts and Solutions Guide
Configuring and Monitoring Your Network
Example 2: A Macro to Configure a New Switch
Another example of a re-usable macro would be a macro to configure new network devices with the
existing network configurations for specific VLAN, ESRP, STP or other customizations. This example
uses user-defined variables to enable the input of specific port and IP address information.
create vlan sales
config sales add port $salesVlanPorts
config sales ipaddr $salesVlanIP
enable ipforwarding
enable esrp sales
enable edp ports all
config ospf add vlan sales
enable ospf
save
yes
$salesVlanPorts
and
$salesVlanIP
are both user-defined variables. When the macro is run on a
device, EPICenter prompts for the values of the two variables. It uses as the prompt the description you
entered when you created the variable. Note that the save command requires a confirmation, which
must be included in the script.
Once this macro has been saved, you can run it on each new device that is added to the network. You
could also designate an execution context and an execution role for this command so that
non-administrator users could run it on a new device to accomplish this specific set of configuration
changes without having access to the Telnet applet and the full CLI.
Creating Macros to be Run From a Menu
Saved macros can be run from outside the Telnet applet, if they are given an execution context. They
can appear under the Macros sub-menu, accessed from a right-click pop-up menu or from the Tools
menu in many of EPICenter’s applets. This means that users who do not have access to the Telnet
applet (users with a Monitor role, for example) can still execute selected Telnet commands on network
devices. A network administrator can create a set of Telnet macros to do common tasks and configure
the macros to specify what users roles should be able to run those macros.
In the Macro Editor you can specify an execution context and execution roles for a macro. These allow
you to create a macro that can be run outside of the Telnet applet.
•
The execution context of a macro determines the type of components on which the macro can be run:
ports, devices or device groups. For example, if you created a macro to add a port to a VLAN you
would give it a port execution context. This means that the macro would be available from the
Macros sub-menu only when a port is selected in the Component Tree. It would not be available
when a device or device group is selected.
Similarly, a macro with a Device execution context will be available only when a Device is selected.
A macro with a Device Group context will run on all devices of a selected Device Group. A macro
can have multiple execution contexts, if appropriate.
•
An execution role defines which users can execute a macro. When you create a macro you can select
which roles will have access to the macro—users whose roles are specified as execution roles will see
the macro in the Macros sub-menu. Users whose roles are not included will not have the macro
available. For example, if only Administrator and Manager roles are selected for a macro, then users
with a Monitor role will not see that macro on the Macros sub-menu.
Summary of Contents for EPICenter 5.0
Page 12: ...12 EPICenter Concepts and Solutions Guide Preface...
Page 76: ...76 EPICenter Concepts and Solutions Guide Managing your Network Assets...
Page 92: ...92 EPICenter Concepts and Solutions Guide Managing VLANs...
Page 116: ...116 EPICenter Concepts and Solutions Guide Managing Wireless Networks...
Page 146: ...146 EPICenter Concepts and Solutions Guide VoIP and EPICenter Avaya Integrated Management...
Page 163: ...Appendices...
Page 164: ......
Page 178: ...178 EPICenter Concepts and Solutions Guide Troubleshooting...