Оценок - 0, средний балл: 0
(
)
)
|
К этому устройству также есть другие инструкции:
Фрагмент инструкции
Information You Need Before Installing MPE/iX 7.0
Release Notes
occur in first-release MPE/iX 7.0 but are hoped to end when large memory
support is added to MPE/iX for 7.0 Express-1.
The best workaround is to upgrade the network connection to allow the
100Base-T adapter to connect in full-duplex mode, allowing it to transmit
and receive at the same time. Network connections supporting 100Mbps
half-duplex also seem to avoid the collisions, since frames moving at
100Mbps are present on their LAN for a shorter interval and thus have
less chances to collide. A less reliable workaround may be to try altering
the LAN delay by moving to a different part of the network, or by inserting
an extra network hub or longer cable.
JAGad34883
NMMGR reports validation successful when SYSGEN says not
valid.
Starting in the MPE/iX 7.0 release, for the A- and N-Class platforms only,
networking components no longer need to be configured in SYSGEN.
However, SYSGEN will report warnings about missing components when
cross-validation is done. These particular warnings can be ignored.
Messages about conflicting paths between NMMGR and SYSGEN should
be examined to see if a path has been configured for SCSI devices in
SYSGEN and networking use in NMMGR.
JAGad36730
MPE/iX 7.0 SNMP/iX terminates on a system where it’s the target
of a request for information on the 100BT Interface.
Currently SNMP supports true link types for ThinLan, LAPB, SDLC, RJE,
and 8025. SNMP does not support NIO 100 BT, PCI 100 BT, FDDI and
ACC drivers. The support for these drivers will be available in release 7.0
Express 1.
JAGad40431
MPE/iX 7.0 NS DSLINE fails when only loopback started: works on
MPE/iX 6.0 release.
Problem Description
When only loopback network is started, then executing the commands
“dsline local m/c name” followed by “remote” will fail.
This happens only if the local m/c name resolve to an IP address other
than the 127.0.0.1.
For example, the system named “ALPHA” has one configured LAN
network, named “LAN1.”
And the IP address for the LAN interface is, 196.10.15.2.
And only the loopback network is started.
Now if the node name “ALPHA” resolves to the LAN IP address, i.e.,
196.10.15.2, then the “remote” command will fail. But if the name
“ALPHA” resolve to 127.0.01, then the remote command will succeed.
Workaround
There are at least two workarounds available.
Chapter 1
5
...Эта инструкция также подходит к моделям:
Программное обеспечение - MPE/iX 7.5 Operating System (46.41 kb)