User Tools

Site Tools


info:devel:architecture

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
info:devel:architecture [2015/07/26 11:37]
info:devel:architecture [2015/07/26 11:52]
[CCE Communication Modes]
Line 456: Line 456:
 |classes|Lists all classes| |classes|Lists all classes|
 |set|Sets the properties of a certain object| |set|Sets the properties of a certain object|
 +
 +Table 17-6 contains additional commands that are available in the handler mode when the CCE is communicating with an event handler:
 +
 +Table 17-6 Additional Handler Mode Commands
 +^Command^Description^
 +|baddata|Reports that an unrecognized attribute or value was passed|
 +|info|Reports a piece of information|
 +|warn|Reports a warning or error|
 +
 +==== CCE Response Codes ====
 +For every command given to CCE, a response code is returned. These response codes consist of a numeric code and a set of arguments. The value of the first digit of the numeric code defines whether the message is an informational message (1), a success message (2), a warning message (3), a failure message (4), or a system-issued message (9). Table 17‐7 describes the response types.
 +
 +Table 17-7 CCE Response Codes
 +^Numeric code range^Type of response^
 +|100-199|Informational|
 +|200-299|Success|
 +|300-399|Warning|
 +|400-499|Failure|
 +|900-999|System~issucd message (which can be sent at any time)|
 +
 +===== Exercise: Testing Systems Changes From cceclient =====
 +
 +In this exercise you test the new feature added to the FTP server for root login access. This test must be successful before you extend the Server Desktop with new menu items.
 +
 +==== Tasks ====
 +Complete the following steps to determine the object number for the System object and test the FTP server changes performed by the event handler:
 +
 +1. In telnet, communicate to CCE using the cceclient utility and find the number for the System object:
 +  # /​usr/​sausalito/​bin/​cceclient
 + ​ 100 CSCP/O.80
 +  200 READY
 +  find system
 +  104 OBJECT 1
 +  201 OK
 +
 +2. Open another telnet session and list the /​etc/​proftpd.conffile contents:
 +  # cat /​etc/​proftpd.conf
 +
 +Notice that no RootLogin directive is listed in the file.
 +
 +3. In the first telnet session that has cceclient running,for the System object (object 1), set the FtpRootLogin name space’s enabled property to 0. (Zero equals off.)
 +  set 1.FtpRootLogin enabled="​0"​
 +  201 OK
 +
 +4. In the other telnet session, list the /​etc/​proftpd.conf file:
 +  # cat /​etc/​proftpd.conf
 +
 +Notice the last line of the file reads RootLogin off
 +
 +5. Try to log in to the FTP server as root and exit:
 +  # ftp localhost
 +  Connected to localhost.
 +  220 ProFTPD 1.2.0 Server (ProFTPD)
 +  [www.server_appliance.com]
 +  Name (localhost:​admin):​ root
 +  331 Password required for root.
 +  Password: your_password
 +  530 Login incorrect.
 +  Login failed.
 +  ftp> exit
 +
 +Notice the Login Failed.
 +
 +In the telnet window that has cceclient running, set the System object’s FtpRootLogin name space’s enabled property to 1.(One equals on.)
 +
 +  set 1.FtpRootLogin enabled=”1"​
 +  201 OK
 +
 +7. In the other telnet session, list the /​etc/​proftpd.conf file:
 +  # cat /​etc/​proftpd.conf
 +Notice that the last line of the file reads RootLogin on
 +
 +8. Log in to the FTP server as root and exit:
 +  # ftp localhost
 +  Connected to localhost.
 +  220 ProFTPD 1.2.0 Server (ProFTPD)
 +  [www.server_appliance.com]
 +  Name (localhostzadmin):​ root
 +  331 Password required for root.
 +  Password: your_password
 +  230 User root logged in.
 +  Remote system type is UNIX.
 +  Using binary mode to transfer files.
 +  ftp> exit
 +
 +Notice the 230 User root logged in.
 +
  
info/devel/architecture.txt · Last modified: 2015/07/26 12:35 by