Authentication and authorization is not bypassed; instead, authentication and authorization happens while granting access to Guest Shell. Only users with the maximum privilege are granted this access. Users can access the NETCONF service from Guest Shell without opening any external ports. Before connecting to the NETCONF-YANG server on the device, you must run the initializing commands in Guest Shell. These commands are:
iosp_client -f netconf_enable guestshell and iosp_client -f netconf_enable_passwordless guestshell The iosp_client -f netconf_enable guestshell port-number command configures the netconf-yang ssh local-vrf guestshell command, and blocks connections until NETCONF-YANG is up and running. The iosp_client -f netconf_enable_passwordless guestshell command creates the SSH keys required for Guest Shell access. To remove the NETCONF-YANG access from Guest Shell, use the following commands:
iosp_client -f netconf_disable guestshell and iosp_client -f netconf_disable_passwordless guestshell The iosp_client -f netconf_disable guestshell command disables access to NETCONF from within the Guest Shell; however, the NETCONF-YANG configuration will still exist. To shut down NETCONF-YANG, use the no netconf-yang command. The iosp_client -f netconf_disable_passwordless guestshell username command removes the SSH keys for the specified user. The user will not be able to access NETCONF without a password; however, the user would still be able to connect by using a password.
The netconf_enable_guestshell python API runs a combination of the iosp_client functions, iosp_client -f netconf_enable guestshell 830 and iosp_client -f netconf_enable_passwordless guestshell guestshell . This API hides the unfamiliar-to-user iosp_client function. When this function is called, it does not return a response until all commands are completed. Unless the function returns an error, you can be sure that NETCONF is running, and the passwordless setup is complete; and you can start creating connections. Logging and Tracing System Flow The following sections describes how the IOx logging and tracing works: LXC Logging 1. Guest OS enables /dev/ttyS2 on the guest application. 2.
Guest application writes data to /dev/ttyS2 . 3. Libvirt emulates /dev/ttyS2 to /dev/pts/x on the host. 4. IOXMAN gets the emulated serial device, /dev/pts/x from the XML file. 5. IOXMAN listens and reads available data from /dev/pts/x , sets the severity for the message, filters, parses and queues the message. 6. Start timer to send the message to /dev/log device on the host using errmsg . 7. Data is saved to the Cisco IOS syslog. Guest Shell Logging and Tracing System Flow Guest Shell 9