H3C Technologies H3C SecBlade LB Cards - Manual (Page 61)

51
Configuring a management IP address for the LB module
NOTE:
Support for this feature varies by the device model and software release of the network device that holds
the LB module.
In the OAA system, the network device and the LB module integrate together and function as one device.
For the SNMP UDP domain-based NMS, however, the device and the LB module are independent SNMP
agents. Physically, the two agents are on the same managed object. Logically, they belong to two
different systems and manage their own MIB objects on the device and the module separately.
When you use the NMS to manage the device and the LB module on the same interface, you must first
obtain the management IP addresses of the two SNMP agents and obtain the link relationship between
them. Then, you can access the two agents.
The management IP address configured on the device for the LB module must be the same as that
configured on the LB module. Otherwise, the NMS cannot access the LB module by using the configured
management IP address.
To configure a management IP address for the LB module:
Step Command Remarks
1. Enter system view. system-view N/A
2. Configure a management IP
address for an LB module.
• In standalone mode:
oap management-ip ip-address slot
slot-number
• In IRF mode:
oap management-ip ip-address chassis
chassis-number slot slot-number
Not configured by default.
Configuring the ACSEI protocol
ACFP Client and Server Exchange Information (ACSEI) is an H3C proprietary protocol.
ACSEI uses the server/client model:
• The ACSEI server is integrated in the Comware software system of the device as a function.
• The ACSEI client is integrated in the Comware software system of the device as a function or in the
Comware software system of the LB product as a function.
ACSEI functions
ACSEI provides the following functions:
• Enables ACSEI clients to register and deregister with the ACSEI server.
• Enables the ACSEI server to assign IDs to ACSEI clients to distinguish among them.
• Allows the ACSEI server and an ACSEI client to mutually monitor and detect each other.
• Supports information interaction between the ACSEI server and ACSEI clients, including clock
synchronization.
• Allows the ACSEI server to manage the ACSEI clients. For example, you can close or restart an
ACSEI client on the ACSEI server.