Initialization, Bcm.user, Igure – ADLINK aTCA-N700 User Manual
Page 50: Ccess to bcm, User

aTCA-N700 SW Users Guide
44
xe14 40000
XLAUI
off
Rear Port 1
xe15 40000
XLAUI
off
Rear Port 2
xe16 1000
10000
GMII
SFI
off
Rear Port 3
xe17 1000
10000
GMII
SFI
off
Rear Port 4
xe18 1000
10000
GMII
SFI
off
Rear Port 5
xe19 1000
10000
GMII
SFI
off
Rear Port 6
8.2. Initialization
During booting up, /etc/init.d/bcm.sh script is executed and the switch software is
launched.
Here are lists of actions performed by /etc/init.d/bcm.sh.
1. Loading kernel modules (linux_kernel_bde, linux_user_bde)
2. Making device node file (/dev/linux_user_bde)
3. It makes CWD (current work directory) to be /usr/local/bcm.
4. Running bcm.user using nbm-netserve.
5. Checking and waiting done using log file of nbm-netserve.
Once activated, bcm.user can be accessed in the following way.
[root@N700]$ telnet localhost 9895
This access is performed via nbm-netserve as illustrated in Figure 5-1.
Figure 8-4 Access to bcm.user
Here’s an example for bcm.user.
[root@N700]$ telnet localhost 9895
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
To exit to Shell mode only to terminate telnet session, use “quit”.
BCM.0> quit
8.3. bcm.user