Примечания к выпуску для Cisco Cisco IOS Software Release 12.4(2)XB
15
Release Notes for Cisco GGSN Release 6.0 on the Cisco MWAM, Cisco IOS Software Release 12.4(2)XB6
Cisco MWAM Caveats, with Cisco IOS Release 12.4(2)XB6
•
CSCsj74145
Description: On a Cisco MWAM running the Cisco GGSN software, if an Error-Indication is
received from the SGSN on a GTPv1 path, which leads to a PDP context deletion on the GGSN, the
corresponding Accounting-Stop, will have the Acct-Terminate-Cause as “Unknown” instead of
“Nas-Error.” This would be Nas-Error if the SGSN path is GTPv0. This Error-Indication is received
on a GTPv1 path.
received from the SGSN on a GTPv1 path, which leads to a PDP context deletion on the GGSN, the
corresponding Accounting-Stop, will have the Acct-Terminate-Cause as “Unknown” instead of
“Nas-Error.” This would be Nas-Error if the SGSN path is GTPv0. This Error-Indication is received
on a GTPv1 path.
Cisco MWAM Caveats, with Cisco IOS Release 12.4(2)XB6
This section lists the Cisco MWAM caveats that are open and resolved with Cisco Release 12.4(2)XB6.
Open Caveats
The following Cisco MWAM caveats are open with Cisco IOS Release 12.4(2)XB6:
•
CSCef74977
Description: If a Supervisor switchover occurs while a reload all is in progress on an MWAM, the
some CPUs might be left in an inactive state. If this occurs, the following message might display:
some CPUs might be left in an inactive state. If this occurs, the following message might display:
<MWAM: No response from IOS complex n, resetting complex.>
where n is the complete number 0, 1, or 2.
This condition occurs in rare cases when a Supervisor switchover is triggered immediately after the
reload all command is issued on the MWAM to reload all the MWAM processors.
reload all command is issued on the MWAM to reload all the MWAM processors.
Workaround: There is currently no known workaround.
•
CSCef76954
Description: The session from the Supervisor to the SiByte processor on the MWAM is lost if the
no ip routing command is executed and a default gateway is configured on the processor.
no ip routing command is executed and a default gateway is configured on the processor.
This condition occurs only when IP routing and a default gateway are configured and the
no ip routing command is executed.
no ip routing command is executed.
Workaround: Log into the processor control (PC) complex on the MWAM and reset the processor.
•
CSCeg13327
Description: Forwarding traffic through a GRE tunnel on an MWAM processor causes the output
queue interface to be wedged. After starting traffic, the interface gi0/0 output queue reaches max
very soon. Thereafter, any attempt to access any device from the MWAM processor (for example,
the ping command) fails.
queue interface to be wedged. After starting traffic, the interface gi0/0 output queue reaches max
very soon. Thereafter, any attempt to access any device from the MWAM processor (for example,
the ping command) fails.
This condition occurs when a GRE tunnel is established between two MWAM processors of the
same sibyte complex and traffic is passed through. If processors in different complexes are GRE
endpoints, the problem does not happen.
same sibyte complex and traffic is passed through. If processors in different complexes are GRE
endpoints, the problem does not happen.
Workaround: There is currently no known workaround. The MWAM processor complex has to be
reset for accessing to/from this processor. However, it is not a common scenario to establish GRE
tunnel between the processors of the same complex.
reset for accessing to/from this processor. However, it is not a common scenario to establish GRE
tunnel between the processors of the same complex.