02-Text
Chapters Download (125.4 KB)
Chapter 1 OAP/OAPS Module Overview
Chapter 2 OAP/OAPS Module Installation
2.5 Connecting the Interface Cable
Chapter 3 Router Configuration
Chapter 4 OAP/OAPS Module Configuration
4.1 Connecting the Console Terminal to the Linux OS of an OAP/OAPS Module
4.2 Restarting the Linux OS of an OAP Module
The open application platform (OAP) and open application platform-smart (OAPS) are developed for new services.
By running independent Linux operating systems (Linux OS) and service software on an OAP/OAPS module, you can perform related system and service configuration. Meanwhile, as an interface module on the router, the OAP/OAPS module exchanges data, status information, and control information with the router.
An OAP/OAPS module can satisfy some new service requirements including IDS intrusion detection in security services, and voice mailbox, automatic operator and CCM call management in voice services. The OAP/OAPS module has different functions on the device and the whole network depending on different services. For IDS network security, the OAP/OAPS module redirects network data packets received by the host to the module and then the CPU of the OAP/OAPS module analyzes the data packets and sends the result to the processor of the router’s main board for processing. For services as automatic operator and voice mailbox, the OAP module can provide services as voice data storage, voice call control and call processing; at the same time, it can support the corresponding security services.
The OAP/OAPS is mainly used on the software and hardware platforms providing multiple services on the router. The OAP includes FIC-OAP and MIM-OAP, while the OAPS only includes MIM-OAPS. The former is applicable on routers with FIC slots and the latter is applicable on routers with MIM slots.
The OAP/OAPS module supports the following functions:
l Serial redirection from the router to the Linux OS of the OPA/OAPS module
l Protocol for status information exchange between the router and the OAP/OAPS module
l Open Linux service platform
The OAP/OAPS module provides one Ethernet management interface and two USB interfaces.
Interface attributes of the OAP/OAPS module are shown in the following table:
Table 2-1 Attributes of the GE interface
|
Attribute |
Description |
|
|
OAP |
OAPS |
|
|
Connector type |
RJ45 |
|
|
Connector number |
1 |
|
|
Cable type |
Standard Ethernet cable |
|
|
Operation mode |
Full duplex/half duplex Autosensing 10/100/1000 Mbps |
Full duplex/half duplex Autosensing 10/100 Mbps |
|
Frame format |
Ethernet_II Ethernet_SNAP |
|
FIC-OAP panel is shown in the following figure:
Figure 2-1 FIC-OAP panel
MIM-OAP panel is shown in the following figure:
Figure 2-2 MIM-OAP panel
Figure 2-3 MIM-OAPS panel
The LEDs on the OAP/OAPS panel are described in the following table:
Table 2-2 Description of the LEDs on the OAP/OAPS panel
|
LED |
Monochrome/bichrome |
State |
Description |
|
SYS |
Bichrome |
Solid green |
Memory detection is being performed. |
|
Green and fast blinking |
BIOS phase |
||
|
Yellow and slow blinking |
Memory detection fails. |
||
|
Yellow and fast blinking |
No bootstrap program exists. |
||
|
Solid yellow |
Not in use currently |
||
|
Green and slow blinking |
The Linux OS is started according to the configuration |
||
|
CF |
Bichrome |
Solid green |
The CF module is in the slot and the POST of the router succeeds. |
|
Green and blinking |
The system is accessing the CF module. |
||
|
Solid yellow |
The CF module is in the slot but is operating abnormally. |
||
|
OFF |
The CF module is not in the slot or the router cannot identify it. |
||
|
LINK/ACT |
Bichrome |
OFF |
No connection is established. |
|
Green |
A Gigabit connection is established. |
||
|
Green and blinking |
Data is being transmitted and received. Active |
||
|
Yellow |
A 10M or 100M connection has been established. |
||
|
Yellow and blinking |
Data is being transmitted and received. Active |
||
|
Disk |
Bichrome |
Solid green |
The hard disk is on the module and the POST of the router succeeds. |
|
Green and blinking |
The system is accessing the hard disk. |
||
|
Steady yellow |
The hard disk is on the module but the router fails in accessing it. |
||
|
OFF |
The hard disk is not on the module or the router cannot identify it. |
The OAP/OAPS interface cable is a category-5 twisted pair cable with RJ45 connectors. Pinouts 1 and 2 are transmit end (Tx) and pinouts 3 and 6 are receive end (Rx), as shown in the following figure:
Step 1: Connect the Ethernet port of an OAP module to a PC or router using a crossover cable and to a Hub or LAN Switch using a straight-through cable;
Step 2: Check the status of LINK LED on the OAP/OAPS panel: ON means the link is connected and OFF means the link is not connected. In the latter case, check the line.
Caution:
l You should connect a cable to the port with the correct mark. Mis-plug is prone to impair the interface module and even damage the router.
l Use a crossover cable, instead of straight-through cable to connect the Ethernet management interface of an OAPS module.
& Note:
After the OAP/OAPS installation, perform the following configuration on the router according to the actual service condition.
Application Control Forwarding Protocol (ACFP) is a collaboration framework for the client/server model between devices. ACFP mainly describes the specifications for implementing collaboration between the OAP/OAPS module and the routers. The OAP/OAPS module is called ACFP client while the router is called ACFP server. After receiving IP packets, the router mirrors or redirects them to the ACFP client based on the ACFP collaboration policy. The software on the ACFP client monitors and detects the packets. Through the collaboration MIB, the ACFP client then instructs the router to make corresponding responses (for example, filter some packets) according to the monitoring and detection results.
By controlling data flows on the router, ACFP implements collaboration to provide users with a unified issuing interface.
Follow these steps to configure ACFP:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enable ACFP |
acfp enable |
Required ACFP is disabled by default. |
& Note:
l For detailed ACFP configurations, refer to ACFP Configuration in the System Volume.
l It is unnecessary to enable ACFP on all OAP/OAPS modules. Enable ACFP only on the OAP/OAPS modules on which the services require ACFP.
ACSEI provides a method for exchanging information between the ACFP client and the ACFP server. As an underlying protocol of ACFP, ACSEI also has two entities: ACSEI server and ACSEI client. ACSEI server is integrated into the software system of the router, while ACSEI client is integrated into the software system of OAP/OAPS module.
ACSEI is an inter-board protocol between the router and the OAP/OAPS module. ACSEI implements clock synchronization, heartbeat detection, and information exchange between the router and the OAP/OAPS module. In addition, ACSEI implements partial control over the system of the OAP/OAPS module through configuration on the router.
Follow these steps to configure ACSEI:
|
To do… |
Use the command… |
Remarks |
|
Enter system veiw |
system-view |
— |
|
Enable ACSEI server |
acsei server enable |
Required ACSEI server is disabled by default. |
& Note:
l For detailed ACSEI configurations, refer to ACSEI Configuration in the System Volume.
l ACSEI client is enabled by default, and therefore, you only need to decide whether to enable ACSEI server.
l Not all OAP/OAPS modules require the ACSEI client function. You can disable ACSEI client on the OAP/OAPS modules on which the services do not require the ACFP client function.
OAP/OAPS module configuration on the router includes the following:
l Connecting a console terminal to the Linux OS of an OAP/OAPS module
l Restarting the Linux OS of an OAP/OAPS module
You can telnet to the Linux OS through the Ethernet management interface on an OAP/OAPS module or connect to the Linux OS through the redirection function provided by the serial interface of the router. In the second mode, the terminal changes from the router CLI to Linux interface after you are redirected to the Linux operating system by the router. In this case, you can return to the router CLI by pressing <Ctrl + K>.
Follow these steps to connect the console terminal to the Linux OS of an OAP/OAPS module
|
Use the command… |
Remarks |
|
|
Connect to the Linux OS of an OAP/OAPS module |
oap connect slot slotnum |
Required |
& Note:
Execute this command in user view.
You can reset the Linux OS of an OAP/OAPS module from the router side.
Follow these steps to reset the Linux OS of an OAP/OAPS module:
|
To do… |
Use the command |
Remarks |
|
Restart the Linux OS |
oap reboot slot slotnum |
Required |
& Note:
l Execute this command in user view.
l If an OAPS module is equipped, you can execute the above command on the router to start the Linux OS of the OAPS module in the case that the Linux OS is shut down.
When the SYS LED on OAP module is green and slow blinking, the operating system on an OAP module is starting normally and can be used.
<System> oap connect slot 4
Connected to OAP
CentOS release 4.4 (Final)
Kernel 2.6.9-42.0.3.EL on an i686
localhost login: root
Password:
Last login: Mon Dec4 11:17:00 on ttyS0
You have new mail.
[root@localhost ~]#
At this time, you can configure and manage the system as you do on Linux OS.
Enter <Ctrl+k> to exit Linux OS. Perform the following to reset OAP module operating system:
<System> oap reboot slot 4
This command will recover the OAP from shutdown or other failed state.
Warning: This command may lose the data on the hard disk if the OAP is not shut
down!
Continue? [Y/N]y
OAP is being reboot.
