<div>
<div class="content wysiwyg-content">
I have a system with two NIC interfaces. The NICs are attached to CISCO switches over a multi-building campus. NIC 1 is configured for EWA0: and has an IP address configured on the 10.0 network. NIC 2 is configured for EWC0: and has an IP address configured on the 100.0 network.<br />
<br />
The problem, an OpenVMS system across campus is on the 100.0 network and DECNET seems to be attached (Circuit is defined) to EWA0: and not EWC0: <br />
<br />
The Circuit status is up for both connections and the line is associated with the MAC address of NIC #2 for EWC0:<br />
<br />
How does one hard-wire DECNET to use a specific Circuit / Line / NIC interface?<br />
<br />
I attempted a set/define node &lt;address&gt; name &lt;node name&gt; circuit EWC0 and DECNET displayed an error.<br />
<br />
I have not tried to set the EWA0: state to disabled... but would DECNET know to connect to EWC0? &nbsp;I was told DECNET broadcasts on all interfaces and selects and interface which responses to a &quot;hello&quot; broadcast.<br />
<br />
Any thoughts on this?<br />
<br />
Thanks!<br />
&nbsp;
</div>
</div>


I have a system with two NIC interfaces. The NICs are attached to CISCO switches over a multi-building campus. NIC 1 is configured for EWA0: and has an IP address configured on the 10.0 network. NIC 2 is configured for EWC0: and has an IP address configured on the 100.0 network.

The problem, an OpenVMS system across campus is on the 100.0 network and DECNET seems to be attached (Circuit is defined) to EWA0: and not EWC0: 

The Circuit status is up for both connections and the line is associated with the MAC address of NIC #2 for EWC0:

How does one hard-wire DECNET to use a specific Circuit / Line / NIC interface?

I attempted a set/define node <address> name <node name> circuit EWC0 and DECNET displayed an error.

I have not tried to set the EWA0: state to disabled... but would DECNET know to connect to EWC0?  I was told DECNET broadcasts on all interfaces and selects and interface which responses to a "hello" broadcast.

Any thoughts on this?

Thanks!
 

OpenVMS Systems: DECNET and Two NIC Interfaces

A mainframe operating system is networking software infrastructure that allows a mainframe computer to run programs, connect linked machines, and process complex numerical and data-driven tasks. Modern mainframe design is generally defined by redundant internal engineering, extensive input-output facilities, strict backward compatibility with older software, high hardware and computational utilization rates and high stability and reliability. Well-known operating systems include IBM z/OS, z/VM, zTPF, z/VSE, OS/390, and their predecessors, along with MCP for Unisys ClearPath, and NonStop OS/Guardian on HP/Tandem, and questions regarding the IBM midrange operating system called IBM i, OS/400, and i5/OS.

Mainframe OS

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.

Network Management

Networking software modules are interfaced with a framework implemented on the machine's operating system that implements the networking functionality of the operating system. The best known frameworks are the TCP/IP model and the OSI model. Systems typically do not use a single protocol to handle a transmission. Instead they use a set of cooperating protocols, sometimes called a protocol family or protocol suite.[9] Some of the best known protocol suites include: IPX/SPX, X.25, AX.25, AppleTalk and TCP/IP. Other protocols indirectly related to networking include the hypertext transfer protocol (HTTP) and its related technologies, Dynamic Host Configuration Protocol (DHCP), Domain Name Server (DNS) and other Internet protocols.