Web GUI

Overview

The Alcatel-Lucent 1850 TSS-5 CLI-based circuit packs can be managed using the CLI command interface or the Web GUI interface. In addition, the VLNC42B circuit packs use both TL1 and SNMP commands and are managed by the Web GUI interface. This section provides a brief introduction to the Web GUI interface. It explains how to access the interface and use the menu structure for system management and provisioning.

Each VLNC4x or VLNC6x pack should be connected to the network and have its IP address configured first. The user then accesses the pack via the Web GUI by entering the IP address of the pack as the URL in the HTTP-enabled Web browser. The Login screen is displayed next. Once the user enters the valid username and password and connecting to the VLNC4x or VLNC6x pack is successful, then the Web GUI main page is displayed.

Access ports

Initial configuration for connectivity requires you to use either the RS-232 console port or the MGMT LAN service port.

Out-of-band connectivity refers to using the RS-232 console port on the VLIU or the MGMT LAN service port on the VLNC4x/VLNC6x faceplate to access the VLNC4x/VLNC6x.

In-band connectivity allows you to access the VLNC4x/VLNC6x from a local or remote PC using the Ethernet network and the IP address information assigned to the VLNC4x/VLNC6x. You must configure the VLNC4x/VLNC6x network parameters with IP address information (IP address, subnet mask, and default gateway) to access the VLNC4x/VLNC6x in-band. All the network LA ports will share one IP address.

Local access control

Alcatel-Lucent 1850 TSS-5 supports the capability to coordinate access to the NE between the Web GUI and a Network Management System (NMS), such as Alcatel-Lucent 1350 OMS).

In many deployments, an NMS and Web GUI are both used to manage Alcatel-Lucent 1850 TSS-5. Simultaneous configuration changes executed by the NMS and Web GUI may result in an inconsistent database and undesirable behavior. To avoid this possible conflict, local access control allows configuration (read-write) access only one, either the NMS or the Web GUI. Note that both may have read access simultaneously.

Table 5-10: Local access control (LAC) details

LACState	Access rights
	Web GUI	NMS
Requested	Web GUI issued a request for read-write access, but has read-only access until it gets response from NMS. The NMS may: Ignore the request. In this case, the Web GUI received read-write access after a preconfigured timeout period (LAC Timeout Period). Deny the request. In this case, only the NMS has read-write access. At any point, the NMS can change the LAC state to Denied to preempt access to the NE from the Web GUI.	Read-Write
Granted (default)	Read-Write	Read-only
Denied	Read-only	Read-Write

Note:

On the NE, the LAC state field is common to all management interfaces. If the LACState is changed via SNMP, TL1 notification is generated; if the LACState is changed via TL1, SNMP notification is generated.