LMP > Control Channels
(ONS 15454 SDH only) Use the Control Channels subtab to define the role of the neighboring LMP nodes and how they are contacted. For information about creating, editing, or deleting LMP control channels see:
LMP > Control Channels > Create LMP Control Channel Dialog Box
LMP > Control Channels > Edit LMP Control Channel Dialog Box
LMP > Control Channels > Delete LMP Control Channel Dialog Box
 
Item
Description
Admin State
Displays the Admin State provisioning that tells the node to bring up or disable the link. In the Create or Edit LMP Control Channel Dialog Box, choosing an administrative state from the drop-down list and clicking Apply changes the control channel’s operational state unless network conditions prevent the change. Admin states include:
unlocked—Means that the node will try to establish the control channel, negotiate channel parameters, and begin the hello message exchange to bring up the link.
locked,disabled—Removes the control channel from service and disables the link.
Operational State
The Operational State reflects the status of bringing up the link that is started in Admin State provisioning:
Unknown—Indicates that LMP is not enabled.
Up—Indicates that LMP is enabled and the link is active. The control channel contacted the remote node and successfully negotiated a control channel.
Down—Indicates that LMP is enabled and the link is inactive. Check that the Admin State of the control channel is unlocked and not locked,disabled. If the state still does not transition to UP, it is possible that the far end control channel has disjointed hello negotiation times that might keep a control channel from changing to the UP state. For example, the local ONS 15454 SDH hello min and max range is 900-1000, and the remote hello min and max range is 1100-1200.
Config Send—No connection was made to the remote node. The node sent a configure request to the remote node, but has not received a configAck (configure acknowledgement) or configNack (configure negative acknowledgement). Make sure the Remote Node IP Address and Remote Node ID are correct.
Config Received—The remote node was contacted, and a response was sent to the local node. The node sent a configure request to the remote node and received a configAck or configNack. Check that the remote node is using the correct Remote Node IP Address and Remote Node ID.
Local Port
Displays the options selected from the drop-down list in the Create or Edit LMP Control Channel dialog box (Routed, or the Slot # and Port #).
Local Port Id
Displays the local port identifier assigned by the node.
Local Control Channel Id
Displays the local control channel identifier assigned by the node.
Remote Node IP Address
Displays the IP address of the remote node for which you created an LMP control channel.
Remote Node Id
Displays the remote node identifier of the node for which you created an LMP control channel.
Remote Control Channel Id
The remote control channel identifier is retrieved from the remote node that was specified by the Remote Node IP Address field. The remote system knows the channel ID assigned to this channel and sends the information to the local node as part of the LMP parameter negotiation.
Requested Hello Interval
Displays the Requested Hello Interval entered in the creation dialog box. The Requested Hello Interval must be greater than the Min Hello Interval and less than the Max Hello Interval. The hello interval specifies an interval at which the local node is scheduled to send a hello message to the remote node. This message allows the nodes to know that they are alive and talking.
Min Hello Interval
Displays the minimum hello interval acceptable for the local node that was entered in the creation or edit dialog box. The Min Hello Interval must be less than the Requested Hello Interval and less than the Max Hello Interval.
Max Hello Interval
Displays the maximum hello interval acceptable for the local node that was entered in the creation or edit dialog box. The Max Hello Interval must be greater than the Requested Hello Interval and the Min Hello Interval.
Actual Hello Interval
The nodes involved in LMP parameter negotiation calculate the Actual Hello Interval after you have entered a requested, minimum, and maximum hello interval in the creation dialog box. The Actual Hello Interval might be the same as the Requested Hello Interval if the remote node agrees to that value. The number will always be between the user-defined minimum and maximum values.
Requested Hello Dead Interval
Displays the Requested Hello Dead Interval entered in the creation dialog box. The Hello Dead Interval is how long the local node waits before it declares that the remote node is not responding (failed).
Min Hello Dead Interval
Displays the requested minimum hello dead interval acceptable for the local node that was entered in the creation or edit dialog box.
Max Hello Dead Interval
Displays the requested maximum hello dead interval acceptable for the local node that was entered in the creation or edit dialog box.
Actual Hello Dead Interval
The nodes involved in LMP parameter negotiation calculate the Actual Hello Dead Interval after you have entered a requested, minimum, and maximum hello dead interval in the creation dialog box. The Actual Hello Dead Interval might be the same as the Requested Hello Dead Interval if the remote node agrees to that value. The number will always be between the user-defined minimum and maximum values.
Remote Node Type
Displays the Remote Node Type selected in the creation dialog box. The Remote Node Type determines the type of control channel created.
Create
Displays the Create LMP Control Channel dialog box. See LMP > Control Channels > Create LMP Control Channel Dialog Box for field descriptions.
Edit
Displays the Edit LMP Control Channel dialog box. See LMP > Control Channels > Edit LMP Control Channel Dialog Box for field descriptions.
Delete
Displays the Delete LMP Control Channel dialog box. See LMP > Control Channels > Delete LMP Control Channel Dialog Box for field descriptions.
Help
Displays context-sensitive help.

Copyright © 2002-2009, Cisco Systems, Inc. All rights reserved.