HP Cisco MDS 9216A Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Re - Page 29

When Microsoft Challenge Handshake Authentication Protocol MSCHAP is enabled

Page 29 highlights

Caveats Send documentation comments to [email protected]. • ICSCsi77055 Symptom: An MDS switch that provides IVR routing on a local VSAN may not be able to export new devices via IVR if there are multiple IVR routers in the local VSAN or if one IVR router contains stale entries for a device. When an IVR router has stale information, it will be out of sync with the other IVR routers. Because IVR routers work in sync, then IVR cannot export any new devices. Workaround: This problem is resolved. • CSCsj07363 Symptom: An SNMP Get-Next Request for the MIB object ip.ipAddrTable.ipAddrEntry.ipAdEntIfIndex on an MDS 9000 switch resolves by asking ifIndex for a loopback address. Because there is no hardware (ifIndex) for a loopback address, the ifIndex reply for this interface is skipped and the next possible instance of the object, which is IP-MIB::ipAdEntNetMask, is returned. Workaround: This issue is resolved. • CSCsj26584 Symptom: When Microsoft Challenge Handshake Authentication Protocol (MSCHAP) is enabled, NAS-IP is not sent. When Password Authentication Protocol (PAP) is used, NAS-IP is sent. PAP is the default authentication protocol. Workaround: This issue is resolved. • CSCsi79423 Symptom: If you disable error or discard messages in Performance Manager via the server.properties file, you may see the following error in the FMServer.log file: WARNING 2007/05/07 14:54:26 PM 10.62.40.75 error: java.io.EOFException java.io.EOFException at java.io.RandomAccessFile.readChar(RandomAccessFile.java:683) at com.cisco.dcbu.lib.rrd.core.RrdFile.readString(Unknown Source) at com.cisco.dcbu.lib.rrd.core.RrdString.get(Unknown Source) at com.cisco.dcbu.lib.rrd.core.RrdString.get(Unknown Source) at com.cisco.dcbu.lib.rrd.core.Header.(Unknown Source) at com.cisco.dcbu.lib.rrd.core.RrdDb.(Unknown Source) at com.cisco.dcbu.pm.Query.getErrDB(Unknown Source) at com.cisco.dcbu.pm.PmStore.store(Unknown Source) at com.cisco.dcbu.pm.PmStore.run(Unknown Source) at java.lang.Thread.run(Thread.java:595) In addition, a file whose filename is a WWN will be erroneously created in the Performance Manager database. Workaround: This issue is resolved. • CSCsi87114 Symptom: When you enter the show fcip tape-session command, the switch displays the outputs of the first ten sessions, but additional session outputs are needed. Workaround: This issue is resolved. • CSCsi98091 Symptom: If you attempt to examine the logging information of an FCIP tunnel that has write acceleration enabled, you might notice that some of the logs do not contain the correct debugging information. The logging information can be used to debug possible error conditions in an FCIP tunnel. Workaround: This issue is resolved. OL-12208-06 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3a) 29

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34

Send documentation comments to [email protected].
29
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.1(3a)
OL-12208-06
Caveats
ICSCsi77055
Symptom:
An MDS switch that provides IVR routing on a local VSAN may not be able to export
new devices via IVR if there are multiple IVR routers in the local VSAN or if one IVR router
contains stale entries for a device. When an IVR router has stale information, it will be out of sync
with the other IVR routers. Because IVR routers work in sync, then IVR cannot export any new
devices.
Workaround:
This problem is resolved.
CSCsj07363
Symptom
: An SNMP Get-Next Request for the MIB object
ip.ipAddrTable.ipAddrEntry.ipAdEntIfIndex on an
MDS 9000 switch resolves by asking ifIndex
for a loopback address. Because there is no hardware (ifIndex) for a loopback address, the ifIndex
reply for this interface is skipped and the next possible instance of the object, which is
IP-MIB::ipAdEntNetMask,
is returned.
Workaround
: This issue is resolved.
CSCsj26584
Symptom
: When Microsoft Challenge Handshake Authentication Protocol (MSCHAP) is enabled,
NAS-IP is not sent. When Password Authentication Protocol (PAP) is used, NAS-IP is sent. PAP is
the default authentication protocol.
Workaround
: This issue is resolved.
CSCsi79423
Symptom
: If you disable error or discard messages in Performance Manager via the
server.properties file, you may see the following error in the FMServer.log file:
WARNING 2007/05/07 14:54:26 PM 10.62.40.75 error: java.io.EOFException
java.io.EOFException
at java.io.RandomAccessFile.readChar(RandomAccessFile.java:683)
at com.cisco.dcbu.lib.rrd.core.RrdFile.readString(Unknown Source)
at com.cisco.dcbu.lib.rrd.core.RrdString.get(Unknown Source)
at com.cisco.dcbu.lib.rrd.core.RrdString.get(Unknown Source)
at com.cisco.dcbu.lib.rrd.core.Header.<init>(Unknown Source)
at com.cisco.dcbu.lib.rrd.core.RrdDb.<init>(Unknown Source)
at com.cisco.dcbu.pm.Query.getErrDB(Unknown Source)
at com.cisco.dcbu.pm.PmStore.store(Unknown Source)
at com.cisco.dcbu.pm.PmStore.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)
In addition, a file whose filename is a WWN will be erroneously created in the Performance
Manager database.
Workaround
: This issue is resolved.
CSCsi87114
Symptom
: When you enter the
show fcip tape-session
command, the switch displays the outputs
of the first ten sessions, but additional session outputs are needed.
Workaround
: This issue is resolved.
CSCsi98091
Symptom
: If you attempt to examine the logging information of an FCIP tunnel that has write
acceleration enabled, you might notice that some of the logs do not contain the correct debugging
information. The logging information can be used to debug possible error conditions in an FCIP
tunnel.
Workaround
: This issue is resolved.