If you select default, the parameters are automatically configured. If you select verbose,
proceed with the following steps to modify the parameters in verbose mode.
4. In the Verbose work area, type the Voice VLAN ID in the Voice VLAN Id dialog box.
5. In the Voice VLAN Gateway dialog box, type the VLAN IP address.
6. In the Voice VLAN Gateway Mask dialog box, enter the VLAN IP mask address.
7. In the Data VLAN Id dialog box, type the data VLAN ID.
8. In the Data VLAN Gateway dialog box, type the data VLAN Gateway IP address.
9. In the Data VLAN Gateway Mask dialog box, type the data VLAN Gateway IP mask
address.
10. In the IP Route to Gateway Modem-Router dialog box, type the IP route address of the
Gateway Modem-Router.
11. In the IP Office Call-Server dialog box, type the call server IP address.
12. In the IP Office File-Server dialog box, type the file server IP address.
13. Click Apply.
IP Office script field description
The following table describes the fields on the IP Office script tab.
Name
Description
Run Script Mode Specifies to run the script either in default or verbose
mode.
Voice VLAN ID Specifies the voice VLAN ID. By default, the voice
VLAN ID is 42.
Voice VLAN Gateway Specifies the Voice VLAN Gateway IP Address. By
default, the voice VLAN gateway IP address is
192.168.42.254
Voice VLAN Gateway Mask Specifies the voice VLAN gateway IP mask address.
By default, the voice VLAN gateway IP mask
address is 255.255.255.0
The default subnet mask created by the run IP Office
script supports a maximum of 250 hosts. You can
change the subnet mask to 255.255.254.0 to allow
510 hosts for each subnet using the verbose mode.
Data VLAN ID Specifies the data VLAN ID. By default, the data
VLAN ID is 44.
Data VLAN Gateway Specifies the data VLAN Gateway. By default, the
data VLAN Gateway is 192.168.44.254
Data VLAN Gateway Mask Specifies the data VLAN Gateway Mask. By default,
the data VLAN Gateway Mask is 255.255.255.0
Table continues…
Configuring the switch using EDM
120 Getting Started with Avaya ERS 3500 Series July 2015
Comments on this document? infodev@avaya.com