NBT Manual

NBT Event Messages

NBT Manual—424773-001

A-4

znbt-evt-cpuswitch

Cause. An NBTCOM CPUSWITCH command was received.

Effect. This is normally used only for NBT backup testing. The NBT primary process

stops, and the backup process will take over automatically.

Recovery. No action is required.

znbt-evt-domain-down

Cause. NBT has lost contact with the TCP/IP subnet, and all activity on the domain is

stopped.

Effect. The NBTCOM STATUS DOMAIN command will provide some additional

information. This usually indicates a problem with the TCP/IP subsystem.

Recovery. No action is required in NBT, as NBT will automatically retry connection to

TCP/IP every minute.

znbt-evt-domain-up

Cause. NBT has contacted the TCP/IP subnet on both the Name Server and Session

Server ports and is ready for sessions. This appears after ADD DOMAIN, after a backup

takeover, or after the TCP/IP subnet became available again after an outage.

Effect. NBT is available for use.

Recovery. No action is required.

znbt-evt-enter-debug

Cause. An NBTCOM DEBUG command was received. This command is normally

used only by NBT developers.

Effect. The NBT process is suspended while in debug mode, so applications will not

get any responses to file system requests, and remote sessions may timeout. Note that

the TACL DEBUG command can also be used to place NBT into debug mode, but no

event will be generated in that case.

Recovery. No action is required.

pname Primary process stopping - CPUSWITCH command

pname Domain domain down on subnet subnet

pname Domain domain up on subnet subnet

pname Process entering debug