Filter
Top Products
1162 | FTOS XML Feature
www.dell.com | support.dell.com
Create an egress ACL and apply rules to the ACL
To create an egress ACL and apply rules to the ACL in one single XML request, first enter FTOS XML
mode, and then construct the configuration request (see Run an FTOS XML session on page 1159). The
following example shows a configuration request message that accomplishes this task:
<?xml version="1.0" encoding="UTF-8"?>
<request MajorVersion="1" MinorVersion="0">
<cli>
<configuration>
<command> interface GigabitEthernet 0/0</command>
<command> ip access-group abcd out</command>
<command> ip access-list extended abcd</command>
<command> seq 5 permit tcp any any</command>
<command> seq 10 deny icmp any any</command>
<command> permit 1.1.1.2</command>
</configuration>
</cli>
</request>
XML Error Conditions and Reporting
This section contains examples of various error conditions that might occur in an XML transaction, and the
associated responses that the XML generates. Note also, as shown below by the “NO_ERROR” message,
that the same response message format is used for a successful configuration request.
The general form of the response is as follows:
<?xml version="1.0" encoding="UTF-8"?>
<response MajorVersion="1" MinorVersion="0">
<responseType></responseType>
<responseSeverity></responseSeverity>
<responseMsg></responseMsg>
</response>
Summary of XML Limitations
• The XML response to a show running-configuration request is encoded in one single XML tag,
instead of the standard XML-encoded response.
•A
show command, in an XML request, requires <action> for the operation tag; the request is not
supported if <configuration> is used for the operation tag.
• Only allowed one show command is supported within a single XML request.
• XML namespace is not supported.
Error Messages
The following strings can appear after the <responseType> tag:
• XML_PARSE_ERROR
• CLI_PARSE_ERROR—This error is caused by:
— Malformed XML or mismatched XML tags