Frequently Asked Questions about MCP Server and UBOS Integration

Q: What is MCP Server for SONiC? A: MCP Server contains scripts to perform an installable binary image build for SONiC (Software for Open Networking in the Cloud). It automates the process of creating NOS images for network switches.

Q: Which ASIC platforms are supported by MCP Server? A: MCP Server supports a wide range of ASIC vendors, including Broadcom, Marvell, Mellanox, Centec, Nephos, and Innovium.

Q: What are the hardware requirements for running MCP Server? A: A server with multiple cores, at least 8GB of RAM, and 300GB of free disk space is recommended.

Q: What is UBOS, and how does it integrate with MCP Server? A: UBOS is a full-stack AI Agent development platform. It integrates with MCP Server to automate the SONiC image building process, provide data-driven insights, and enable the creation of custom AI agents for network management.

Q: How can UBOS help automate network operations with MCP Server? A: UBOS can orchestrate the entire SONiC image building process, automate NOS upgrades, and optimize network configurations using AI-powered agents.

Q: What are the benefits of using UBOS and MCP Server together? A: Increased efficiency, reduced costs, improved network performance, enhanced security, and accelerated innovation.

Q: How do I build an image for ARM architecture using MCP Server? A: You need to configure the build environment with the appropriate PLATFORM_ARCH (armhf or arm64) and then build the specific target.

Q: What should I do if I encounter a “No space left on device” error during the build process? A: Ensure that the Docker workspace directory (/var/lib/docker) has sufficient free space. If not, move it to a partition with more space.

Q: Where can I find the generated SONiC installer images and docker images? A: The generated files are located in the ./target directory.

Q: How can I enable HTTP/HTTPS proxy during the build process? A: Use the http_proxy, https_proxy, and no_proxy environment variables when running the make command.

Q: Is root or sudo supported while building images A: No, Add your user account to docker group and use your user account to make. root or sudo are not supported.