Avaya G430 - Page 134

• Server. Communication Manager login and password
Note:
The server must be the first listing in NMC’s discovery output. If an
Survivable Core Server node is discovered and listed prior to the main
server, the main server’s login/password will not permit access to the
Survivable Core Server node.
• Gateway. SNMPv1/v3 access parameters
• Gateway. NMC has discovered the Branch Gateway’s IP address
3. Make sure the Communication Manager has been configured for SLS as described
in
Configuring Communication Manager for SLS on page 120.
4. Click the Device Profiles icon/link in the top-level toolbar of the main PIM
window.
Alternatively, select PIM Objects > Device Profiles from the left panel.
5. Click the New icon on the Device Profile list page that appears in the right panel
of the main PIM window.
If this is not a new profile, open the existing profile from the left panel or from the
Device Profile list page.
6. Proceed through the Device Profile Wizard to the Details page.
Set the CM version field to 4.0.
7. Proceed through the Device Profile Wizard to the SLS / ARS page and perform the
following:
a. Select the Enable the SLS feature on this device? checkbox to enable SLS
on the Branch Gateway.
A cleared checkbox means that SLS is disabled.
b. Select the Perform scheduled SLS updates on this device? checkbox to
send the SLS administration data set to the Branch Gateway according to the
settings on the SLS Update Schedule screen.
8. Optionally click the following buttons:
• View Extract
• Perform Extract
• Actions
9. If this Branch Gateway has not been previously provisioned, click Add ARS
Entry to open the ARS Entry page.
10. Use the SLS Update Schedule page to administer up to six SLS updates per day.
a. Check the Enable SLS Updates box.
b. Set as many as six Daily Updates.
Standard Local Survivability (SLS)
134 Administering Avaya G430 Branch Gateway October 2013
Comments? infodev@avaya.com