<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Network Adapter question in VMS in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939544#M81726</link>
    <description>ANAL/SYS&lt;BR /&gt;SDA&amp;gt; SHOW LAN&lt;BR /&gt;will show the protocols enabled on each device.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 06 Feb 2007 16:41:05 GMT</pubDate>
    <dc:creator>Ian Miller.</dc:creator>
    <dc:date>2007-02-06T16:41:05Z</dc:date>
    <item>
      <title>Network Adapter question in VMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939540#M81722</link>
      <description>Greetings,&lt;BR /&gt;&lt;BR /&gt;How do I reference which NIC adapter that I am currently using?  Information on the NIC as follows:&lt;BR /&gt;&lt;BR /&gt;LANCP:&lt;BR /&gt;Device Characteristics EWA0:&lt;BR /&gt;                  Value  Characteristic&lt;BR /&gt;                  -----  --------------&lt;BR /&gt;                   1500  Device buffer size&lt;BR /&gt;                 Normal  Controller mode&lt;BR /&gt;               External  Internal loopback mode&lt;BR /&gt;      00-00-F8-07-41-BC  Hardware LAN address&lt;BR /&gt;                         Multicast address list&lt;BR /&gt;                CSMA/CD  Communication medium&lt;BR /&gt;      FF-FF-FF-FF-FF-FF  Current LAN address&lt;BR /&gt;                    128  Minimum receive buffers&lt;BR /&gt;                    256  Maximum receive buffers&lt;BR /&gt;                     No  Full duplex enable&lt;BR /&gt;                     No  Full duplex operational&lt;BR /&gt;               00000007  Line media type&lt;BR /&gt;                    100  Line speed (mbps)&lt;BR /&gt;    Disabled/No Failset  Logical LAN state&lt;BR /&gt;                      0  Failover priority&lt;BR /&gt;&lt;BR /&gt;Device Characteristics EWB0:&lt;BR /&gt;                  Value  Characteristic&lt;BR /&gt;                  -----  --------------&lt;BR /&gt;                   1500  Device buffer size&lt;BR /&gt;                 Normal  Controller mode&lt;BR /&gt;               External  Internal loopback mode&lt;BR /&gt;      00-10-18-10-A4-B8  Hardware LAN address&lt;BR /&gt;                         Multicast address list&lt;BR /&gt;                CSMA/CD  Communication medium&lt;BR /&gt;      FF-FF-FF-FF-FF-FF  Current LAN address&lt;BR /&gt;                    128  Minimum receive buffers&lt;BR /&gt;                    256  Maximum receive buffers&lt;BR /&gt;                    Yes  Full duplex enable&lt;BR /&gt;                    Yes  Full duplex operational&lt;BR /&gt;            TwistedPair  Line media type&lt;BR /&gt;                   1000  Line speed (mbps)&lt;BR /&gt;    Disabled/No Failset  Logical LAN state&lt;BR /&gt;                      0  Failover priority&lt;BR /&gt;&lt;BR /&gt;TCPIP&lt;BR /&gt; sho interface /full&lt;BR /&gt; Interface: LO0&lt;BR /&gt;   IP_Addr: 127.0.0.1         NETWRK: 255.0.0.0         BRDCST: 192.168.255.255&lt;BR /&gt;                                                           MTU:  4096&lt;BR /&gt;     Flags: UP LOOP NOARP MCAST SMPX&lt;BR /&gt;                                  RECEIVE        SEND&lt;BR /&gt;   Packets                          28259       28259&lt;BR /&gt;     Errors                             0           0&lt;BR /&gt;   Collisions:                          0&lt;BR /&gt;&lt;BR /&gt; Interface: WE1&lt;BR /&gt;   IP_Addr: 192.168.1.15        NETWRK: 255.255.0.0       BRDCST: 192.168.255.255&lt;BR /&gt; Cluster&lt;BR /&gt;    C_Addr: 192.168.1.15      C_NETWRK: 255.255.0.0     C_BRDCST: 192.168.255.255&lt;BR /&gt;                       Ethernet_Addr: 00-10-18-10-A4-B8    MTU:  1500&lt;BR /&gt;     Flags: UP BRDCST RUN MCAST SMPX&lt;BR /&gt;                                  RECEIVE        SEND&lt;BR /&gt;   Packets                      931348559   532107993&lt;BR /&gt;     Errors                             0           0&lt;BR /&gt;   Collisions:                          0&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thank you in advance.</description>
      <pubDate>Tue, 06 Feb 2007 13:58:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939540#M81722</guid>
      <dc:creator>Jorge Cocomess</dc:creator>
      <dc:date>2007-02-06T13:58:06Z</dc:date>
    </item>
    <item>
      <title>Re: Network Adapter question in VMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939541#M81723</link>
      <description>OpenVMS IP and DECnet will attempt to use all links that are found on the system.  To see which are in active use on a host, check the link counters.&lt;BR /&gt;&lt;BR /&gt;Within the specific information posted, the IP device interface WE1 is presently using physical device EWB0: for connection into a private class C address space.&lt;BR /&gt;&lt;BR /&gt;LO is the IP loopback device.&lt;BR /&gt;&lt;BR /&gt;EWA0: and EWB0: are two NICs that are present.  Based on what is shown, EWA0: isn't used for anything.  It's probably not plugged into a network, or it's been otherwise disabled, or there's a problem somewhere upstream of the EWA0: NIC in this network.&lt;BR /&gt;&lt;BR /&gt;(Some systems will have link status fault indications, and will flash an attention indicator light near the failure.  On various local servers, it's a bright blue LED right next to the NIC socket, and it automatically flashes when the NIC is not connected or the connection is not working.  Unfortunately, I've not seen this implemented on Integrity, Alpha or VAX hardware.  This would be a nice enhancement for the Integrity boxes, and would help you find out which NIC socket is -- for instance -- the EWA0: device here.  Right now, it's somewhat trial-and-error, assuming there's a wire plugged into each of the NICs on this system.  Pull one, see if the connections drop.  Or trace the wires.)&lt;BR /&gt;</description>
      <pubDate>Tue, 06 Feb 2007 14:12:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939541#M81723</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2007-02-06T14:12:55Z</dc:date>
    </item>
    <item>
      <title>Re: Network Adapter question in VMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939542#M81724</link>
      <description>&lt;BR /&gt;You have 2 network interfaces, TCPIP is configured to use the second interface.  Which adapter depends on what you're doing.  For TCPIP traffic, you'll be using the second interface.  For DECnet or LAT there isn't enough information to determine which adapter may be in use.  &lt;BR /&gt;&lt;BR /&gt;You may want to consider LAN failover or failSAFE IP with two interfaces available.  See the System Manager's manual for LAN failover documentation &lt;A href="http://h71000.www7.hp.com/doc/os83_index.html" target="_blank"&gt;http://h71000.www7.hp.com/doc/os83_index.html&lt;/A&gt; and this link from the OpenVMS Technical Journal &lt;A href="http://h71000.www7.hp.com/openvms/journal/v2/articles/tcpip.html" target="_blank"&gt;http://h71000.www7.hp.com/openvms/journal/v2/articles/tcpip.html&lt;/A&gt; for discussion on configuring TCPIP for reliable access.&lt;BR /&gt;&lt;BR /&gt;For details on the network adapters you can use:&lt;BR /&gt;$ anal/system&lt;BR /&gt;&amp;gt; clue config&lt;BR /&gt;&lt;BR /&gt;Depending on the version of your operating system and platform, the error log may inventory NICs (Diagnose or anal/error).  You can access this information from the console if you halt the system as well, although that can be a considered an extreme way to get this information.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Andy</description>
      <pubDate>Tue, 06 Feb 2007 14:21:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939542#M81724</guid>
      <dc:creator>Andy Bustamante</dc:creator>
      <dc:date>2007-02-06T14:21:59Z</dc:date>
    </item>
    <item>
      <title>Re: Network Adapter question in VMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939543#M81725</link>
      <description>You might try "show device ew /full" to see which processes are current using the device.</description>
      <pubDate>Tue, 06 Feb 2007 15:47:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939543#M81725</guid>
      <dc:creator>Walter Miller_1</dc:creator>
      <dc:date>2007-02-06T15:47:26Z</dc:date>
    </item>
    <item>
      <title>Re: Network Adapter question in VMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939544#M81726</link>
      <description>ANAL/SYS&lt;BR /&gt;SDA&amp;gt; SHOW LAN&lt;BR /&gt;will show the protocols enabled on each device.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 06 Feb 2007 16:41:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939544#M81726</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2007-02-06T16:41:05Z</dc:date>
    </item>
    <item>
      <title>Re: Network Adapter question in VMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939545#M81727</link>
      <description>Per your suggestions, I ran ANAL/SYS &amp;amp; Show lan and here's the stat:&lt;BR /&gt;&lt;BR /&gt; -- EWA Device Summary  6-FEB-2007 16:01:37 --&lt;BR /&gt;&lt;BR /&gt;LSB address  = 8718A000&lt;BR /&gt;Device state = 00001003 RUN,INITED&lt;BR /&gt;&lt;BR /&gt;UCB      UCB Addr  Fmt   Value           Client     State&lt;BR /&gt;---      --------  ---   -----           ------  -----------&lt;BR /&gt;EWA0     8151B1C0&lt;BR /&gt;EWA3     8168BF00  802E  08-00-2B-80-3C  DNAME   0017 STRTN,LEN,UNIQ,STRTD&lt;BR /&gt;EWA4     8168C700  Eth   80-3C           DNAME   0017 STRTN,LEN,UNIQ,STRTD&lt;BR /&gt;EWA5     817DDF40  802   FE              DECNETV 0017 STRTN,LEN,UNIQ,STRTD&lt;BR /&gt;EWA6     817DDC00  Eth   60-03           DECNET  0017 STRTN,LEN,UNIQ,STRTD&lt;BR /&gt;EWA7     8192B9C0  Eth   60-04           LAT     0015 STRTN,UNIQ,STRTD&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Doesn't look like I'm using EWA0, am I??&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 06 Feb 2007 17:04:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939545#M81727</guid>
      <dc:creator>Jorge Cocomess</dc:creator>
      <dc:date>2007-02-06T17:04:05Z</dc:date>
    </item>
    <item>
      <title>Re: Network Adapter question in VMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939546#M81728</link>
      <description>&lt;BR /&gt;EWA0 is the template for protocols running on EWA1, EWA2 . . . &lt;BR /&gt;&lt;BR /&gt;So in this examples, you're running DECnet phase V and LAT on the EWA NIC.  Are you using either of these for connectivity?  &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Andy</description>
      <pubDate>Tue, 06 Feb 2007 21:07:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939546#M81728</guid>
      <dc:creator>Andy Bustamante</dc:creator>
      <dc:date>2007-02-06T21:07:21Z</dc:date>
    </item>
    <item>
      <title>Re: Network Adapter question in VMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939547#M81729</link>
      <description>As suggested by Hoff;&lt;BR /&gt;&lt;BR /&gt;$ MC LANCP SHOW DEV/COUNT EWA0:&lt;BR /&gt;&lt;BR /&gt; Are your sent &amp;amp; received byte counters zero? if not, are they increasing?.&lt;BR /&gt;&lt;BR /&gt;Also, note the speed differences with your cards;&lt;BR /&gt;&lt;BR /&gt;EWA0: - 100 Line speed (mbps)&lt;BR /&gt;EWB0: - 1000 Line speed (mbps)</description>
      <pubDate>Tue, 06 Feb 2007 21:52:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939547#M81729</guid>
      <dc:creator>Martin Hughes</dc:creator>
      <dc:date>2007-02-06T21:52:01Z</dc:date>
    </item>
    <item>
      <title>Re: Network Adapter question in VMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939548#M81730</link>
      <description>Yes, device EWA0: displayed all zeroes when I execute the command '$ MC LANCP SHOW DEV/COUNT EWA0:'&lt;BR /&gt;&lt;BR /&gt;When I ran the same command on EWB0: and I get the stats and counters.&lt;BR /&gt;&lt;BR /&gt;That's good news.  I did not want to use the 100MBps NIC Adapter any longer.  I am now running on the faster NIC EWB0: at 1000MBps.&lt;BR /&gt;&lt;BR /&gt;Thanks guys!!</description>
      <pubDate>Tue, 06 Feb 2007 22:48:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939548#M81730</guid>
      <dc:creator>Jorge Cocomess</dc:creator>
      <dc:date>2007-02-06T22:48:09Z</dc:date>
    </item>
    <item>
      <title>Re: Network Adapter question in VMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939549#M81731</link>
      <description>A bit more information for you:&lt;BR /&gt;&lt;BR /&gt;DECnet Phase V device (CSMACD station) naming by default is CSMACD-0 (EWA0) and CSMACD-1 (EWA1). If you look at the devices with NCL you'll see which prototype EWx0 physical device the CSMACD-x station maps to. I like to change the default names to something more useful, like ETH_EWA0.&lt;BR /&gt;&lt;BR /&gt;TCPIP device naming for EW devices is WE0 (EWA0) and WE1 (EWB0).&lt;BR /&gt;&lt;BR /&gt;EW devices cover a wide range of hardware types, all the way from 10/100 copper devices to fibre GigE devices. You'll also find EI devices as well (generally the Intel 82559 chipset based ethernet devices).&lt;BR /&gt;&lt;BR /&gt;I suggest that you turn off the protocols you don't need on EWA0 - but be careful!&lt;BR /&gt;&lt;BR /&gt;Don't configure the interface in IP (or remove it with SET CONF NOINT WE0).&lt;BR /&gt;&lt;BR /&gt;Don't configure it in DECnet Phase V (or remove it with DISABLE CSMA STATION and DELETE CSMA STATION and don't forget to edit the NCL scripts or re-configure the devices with NET$CONFGURE in ADVANCED mode).&lt;BR /&gt;&lt;BR /&gt;Stop SCS on EWA with SCACP STOP LAN or the LAVC$STOP_BUS program in SYS$EXAMPLES.&lt;BR /&gt;&lt;BR /&gt;As for which devices are which - the hardware manual for the machine usually tells you, but it doesn't always tell you in what order VMS will find the LAN devices. I'm guessing that this is something like a RX26xx where you have both a GigE port and a 10/100 port. As you rightly show - LANCP gives you a reasonable picture of what's happening and the capabilities of the device.&lt;BR /&gt;&lt;BR /&gt;Other thoughts: &lt;BR /&gt;- You may want to look at using LAN failover.&lt;BR /&gt;- You may want to look at using IP failsafe if youre primary network activity is IP traffic.&lt;BR /&gt;&lt;BR /&gt;Cheers, Colin.</description>
      <pubDate>Wed, 07 Feb 2007 04:18:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/network-adapter-question-in-vms/m-p/3939549#M81731</guid>
      <dc:creator>Colin Butcher</dc:creator>
      <dc:date>2007-02-07T04:18:54Z</dc:date>
    </item>
  </channel>
</rss>

