Cisco Cisco IOS Software Release 15.2(3)E 릴리즈 노트
33
Release Notes for the Catalyst 4500 Series Switch, Cisco IOS Releases 15.2(2)Ex
Limitations and Restrictions
–
Do not enter the link debounce command on fast UDLD ports.
–
Configure fast UDLD on at least two links between each connected network device. This
reduces the likelihood of fast UDLD incorrectly error disabling a link due to false positives.
reduces the likelihood of fast UDLD incorrectly error disabling a link due to false positives.
–
Fast UDLD does not report a unidirectional link if the same error occurs simultaneously on
more than one link to the same neighbor device.
more than one link to the same neighbor device.
•
A XML-PI specification file entry does not return the desired CLI output.
The outputs of certain commands, such as show ip route and show access-lists, contain
non-deterministic text. While the output is easily understood, the output text does not contain strings
that are consistently output. A general purpose specification file entry is unable to parse all possible
output.
non-deterministic text. While the output is easily understood, the output text does not contain strings
that are consistently output. A general purpose specification file entry is unable to parse all possible
output.
Workaround (1):
While a general purpose specification file entry may not be possible, a specification file entry might
be created that returns the desired text by searching for text that is guaranteed to be in the output. If
a string is guaranteed to be in the output, it can be used for parsing.
be created that returns the desired text by searching for text that is guaranteed to be in the output. If
a string is guaranteed to be in the output, it can be used for parsing.
For example, the output of the show ip access-lists SecWiz_Gi3_17_out_ip command is this:
Extended IP access list SecWiz_Gi3_17_out_ip
10 deny ip 76.0.0.0 0.255.255.255 host 65.65.66.67
20 deny ip 76.0.0.0 0.255.255.255 host 44.45.46.47
30 permit ip 76.0.0.0 0.255.255.255 host 55.56.57.57
The first line is easily parsed because access list is guaranteed to be in the output:
<Property name="access list" alias="Name" distance="1.0" length="-1" type="String"
/>
The remaining lines all contain the term host. As a result, the specification file may report the
desired values by specifying that string. For example, this line
desired values by specifying that string. For example, this line
<Property name="host" alias="rule" distance="s.1" length="1" type="String" />
will produce the following for the first and second rules
<rule>
deny
</rule>
and the following for the third statement
<rule>
permit
<rule>
Workaround (2):
Request the output of the show running-config command using NETCONF and parse that output
for the desired strings. This is useful when the desired lines contain nothing in common. For
example, the rules in this access list do not contain a common string and the order (three permits,
then a deny, then another permit), prevent the spec file entry from using permit as a search string,
as in the following example:
for the desired strings. This is useful when the desired lines contain nothing in common. For
example, the rules in this access list do not contain a common string and the order (three permits,
then a deny, then another permit), prevent the spec file entry from using permit as a search string,
as in the following example:
Extended MAC access list MACCOY
permit 0000.0000.ffef ffff.ffff.0000 0000.00af.bcef ffff.ff00.0000 appletalk
permit any host 65de.edfe.fefe xns-idp
permit any any protocol-family rarp-non-ipv4
deny host 005e.1e5d.9f7d host 3399.e3e1.ff2c dec-spanning
permit any any