Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Decnet Phave IV over CROSSOVER Network Connection

Shailender_1
Advisor

Decnet Phave IV over CROSSOVER Network Connection

There is no DECnet Phave IV traffic on N/W interfaces connect using crossover cable. I can see SCS traffic over this interface but not the Decnet.

I have two ES40 server running OpenVMS 7.3-1, It has two NICs, TCPIP is configured on one interface EWA0 and connected through the Switch. The second interfaces of both the servers are connect using a crossover network cable.

Is connecting two server using crossover network connection supported config fot Decnet PHASE IV to work ?

O/P from NCP and SDA

$CSP02/E14249> mc ncp sho known line


Known Line Volatile Summary as of 5-APR-2007 17:07:41

Line State

EWA-0 on
EWA-1 on

$CSP02/E14249> mc ncp sho known cir


Known Circuit Volatile Summary as of 5-APR-2007 17:07:31

Circuit State Loopback Adjacent
Name Routing Node

EWA-0 on 1.606 (F2ARCH)
EWA-1 on


Known Circuit Counters as of 5-APR-2007 17:08:45

Circuit = EWA-0

>65534 Seconds since last zeroed
376701510 Terminating packets received
188614849 Originating packets sent
0 Terminating congestion loss
0 Transit packets received
0 Transit packets sent
0 Transit congestion loss
0 Circuit down
0 Initialization failure
17 Adjacency down
1 Peak adjacencies
189663103 Data blocks sent
>4294967294 Bytes sent
377684029 Data blocks received
>4294967294 Bytes received
0 Unrecognized frame destination
0 User buffer unavailable


Circuit = EWA-1

>65534 Seconds since last zeroed
0 Terminating packets received
0 Originating packets sent
0 Terminating congestion loss
0 Transit packets received
0 Transit packets sent
0 Transit congestion loss
0 Circuit down
0 Initialization failure
0 Adjacency down
0 Peak adjacencies
1048265 Data blocks sent
52413250 Bytes sent
0 Data blocks received
0 Bytes received
0 Unrecognized frame destination
0 User buffer unavailable



O/p from SDA

-- EWA Device Summary 5-APR-2007 17:10:14 --

LSB address = 9D7CC000
Device state = 00000103 RUN,INITED,RING_AVAIL

UCB UCB Addr Fmt Value Client State
--- -------- --- ----- ------ -----------
EWA0 815D3400
EWA2 81607800 Eth 60-07 SCA 0017 STRTN,LEN,UNIQ,STRTD
EWA4 81796B40 Eth 60-03 DECNET 0017 STRTN,LEN,UNIQ,STRTD
EWA5 81798940 Eth 60-04 LAT 0015 STRTN,UNIQ,STRTD
EWA6 81809B00 Eth 08-00 IP 0015 STRTN,UNIQ,STRTD
EWA7 8180A240 Eth 08-06 ARP 0015 STRTN,UNIQ,STRTD
EWA8 8180A980 Eth 86-DD 0015 STRTN,UNIQ,STRTD
EWA9 81850200 802E 08-00-2B-80-48 AMDS 0017 STRTN,LEN,UNIQ,STRTD

-- EWB Device Summary 5-APR-2007 17:10:15 --

LSB address = 9D7DE000
Device state = 00000103 RUN,INITED,RING_AVAIL

UCB UCB Addr Fmt Value Client State
--- -------- --- ----- ------ -----------
EWB0 815EA740
EWB2 81607B40 Eth 60-07 SCA 0017 STRTN,LEN,UNIQ,STRTD
EWB4 81798C80 Eth 60-03 DECNET 0017 STRTN,LEN,UNIQ,STRTD

LAN Data Structures
-------------------
-- EWA Counters Information 5-APR-2007 17:10:43 --

Octets received 981052683030 Octets sent 806099650297
PDUs received 3647396785 PDUs sent 1054234935
Mcast octets received 608228125207 Mcast octets sent 1118560104
Mcast PDUs received 2563979615 Mcast PDUs sent 15153344
Unrec indiv dest PDUs 0 PDUs sent, deferred 0
Unrec mcast dest PDUs 26886066 PDUs sent, one coll 0
Data overruns 0 PDUs sent, mul coll 0
Unavail station buffs 4373 Excessive collisions 0
Unavail user buffers 0 Late collisions 0
CRC errors 0 Carrier check failure 2
Alignment errors 0 Last carrier failure None
Rcv data length err 0 Coll detect chk fail 0
Frame size errors 0 Short circuit failure 0
Frames too long 0 Open circuit failure 0
Seconds since zeroed 15724134 Transmits too long 0
Station failures 0 Send data length err 0
No work transmits 0 Ring avail transitions 1
Buffer_Addr transmits 0 Ring unavail transitions 0
SVAPTE/BOFF transmits 0 Loopback sent 0
Global page transmits 0 System ID sent 52670
Bad PTE transmits 0 ReqCounters sent 0
Restart pending counter 0 Internal counters size 504
+00 Driver version 107 +50 LCarrier workarounds 0
+04 Driver flags 00000201 +54 Xmt mult. workarounds 0
+08 Device type 00001080 +58 Xmt chained 48517841
+0C Link state 3 +5C Interrupts 403489854
+10 Link down timer 0 +60 BNC selections 0
+14 Link transition count 1 +64 Duplex changes 0
+18 Reset count 2 +68 Inits nomap 1
+1C Xmt timeouts 0 +6C Inits mapped 0
+20 Xmt underflows 0 +70 Xmt mapped 0
+24 Xmt length err 0 +74 Rcv mapped 0
+28 Rcv overflows 0 +78 Soft errors 0
+2C Rcv collision 0 +7C Duplex mismatches 0
+30 Startups 2 +80 Reforks 15
+34 Setup buffers 8 +84 NWAYs done 0
+38 CSR6 changes 4 +88 NWAY enable 0
+3C PTE->PFN translations 0 +8C NWAY state 0
+40 CSR13 (AUI=bit3 set)H 00000000 +90 NWAY link cnt 0
+44 Too many xsegs 0 +94 Autosense state 0
+48 Too few xsegs 0 +98 PHY address 00000000
+4C LW align (1 seg) 0 +9C Saved speed 0


-------------------
-- EWA2 60-07 (SCA) Counters Information 5-APR-2007 17:11:01 --

Octets received 1900193194 Octets sent 2185871912
PDUs received 17896311 PDUs sent 17894936
Mcast octets received 807275524 Mcast octets sent 916054820
Mcast PDUs received 6841318 Mcast PDUs sent 6836230
Unavail user buffer 0 Multicast not enabled 0
Last UUB time None User buffer too small 0

-- EWA4 60-03 (DECNET) Counters Information 5-APR-2007 17:11:09 --

Octets received 271923045087 Octets sent 147312761391
PDUs received 377687923 PDUs sent 189664083
Mcast octets received 33128724 Mcast octets sent 52413150
Mcast PDUs received 982528 Mcast PDUs sent 1048263
Unavail user buffer 0 Multicast not enabled 0
Last UUB time None User buffer too small 0


-- EWA5 60-04 (LAT) Counters Information 5-APR-2007 17:11:17 --

Octets received 810 Octets sent 36773364
PDUs received 15 PDUs sent 260804
Mcast octets received 810 Mcast octets sent 36773364
Mcast PDUs received 15 Mcast PDUs sent 260804
Unavail user buffer 0 Multicast not enabled 0
Last UUB time None User buffer too small 0

-- EWA6 08-00 (IP) Counters Information 5-APR-2007 17:11:24 --

Octets received 693536314371 Octets sent 662577097216
PDUs received 3143951263 PDUs sent 818521000
Mcast octets received 602814614452 Mcast octets sent 0
Mcast PDUs received 2475910623 Mcast PDUs sent 0
Unavail user buffer 0 Multicast not enabled 0
Last UUB time None User buffer too small 0

-- EWA7 08-06 (ARP) Counters Information 5-APR-2007 17:11:30 --

Octets received 2665277968 Octets sent 286941900
PDUs received 57940815 PDUs sent 6831950
Mcast octets received 2353435136 Mcast octets sent 284768820
Mcast PDUs received 51161623 Mcast PDUs sent 6780210
Unavail user buffer 0 Multicast not enabled 0
Last UUB time None User buffer too small 0

-- EWA8 86-DD Counters Information 5-APR-2007 17:11:36 --

Octets received 0 Octets sent 0
PDUs received 0 PDUs sent 0
Mcast octets received 0 Mcast octets sent 0
Mcast PDUs received 0 Mcast PDUs sent 0
Unavail user buffer 0 Multicast not enabled 0
Last UUB time None User buffer too small 0

-- EWA9 80-48 (AMDS) Counters Information 5-APR-2007 17:11:43 --

Octets received 7647962164 Octets sent 8460449418
PDUs received 23045828 PDUs sent 21018171
Mcast octets received 369810740 Mcast octets sent 32587944
Mcast PDUs received 2202861 Mcast PDUs sent 175204
Unavail user buffer 0 Multicast not enabled 0
Last UUB time None User buffer too small 0

-- EWB Counters Information 5-APR-2007 17:11:50 --

Octets received 1928583434 Octets sent 1966702379
PDUs received 17775318 PDUs sent 18878643
Mcast octets received 806135520 Mcast octets sent 851431492
Mcast PDUs received 6717796 Mcast PDUs sent 7820278
Unrec indiv dest PDUs 0 PDUs sent, deferred 0
Unrec mcast dest PDUs 0 PDUs sent, one coll 0
Data overruns 0 PDUs sent, mul coll 0
Unavail station buffs 0 Excessive collisions 0
Unavail user buffers 0 Late collisions 0
CRC errors 0 Carrier check failure 2
Alignment errors 0 Last carrier failure None
Rcv data length err 0 Coll detect chk fail 0
Frame size errors 0 Short circuit failure 0
Frames too long 0 Open circuit failure 0
Seconds since zeroed 15724201 Transmits too long 0
Station failures 0 Send data length err 0

No work transmits 0 Ring avail transitions 1
Buffer_Addr transmits 0 Ring unavail transitions 0
SVAPTE/BOFF transmits 0 Loopback sent 0
Global page transmits 0 System ID sent 52670
Bad PTE transmits 0 ReqCounters sent 0
Restart pending counter 0 Internal counters size 504
+00 Driver version 107 +50 LCarrier workarounds 0
+04 Driver flags 00000201 +54 Xmt mult. workarounds 0
+08 Device type 00001080 +58 Xmt chained 940
+0C Link state 3 +5C Interrupts 36653463
+10 Link down timer 0 +60 BNC selections 0
+14 Link transition count 1 +64 Duplex changes 0
+18 Reset count 2 +68 Inits nomap 1
+1C Xmt timeouts 0 +6C Inits mapped 0
+20 Xmt underflows 0 +70 Xmt mapped 0
+24 Xmt length err 0 +74 Rcv mapped 0
+28 Rcv overflows 0 +78 Soft errors 0
+2C Rcv collision 0 +7C Duplex mismatches 0
+30 Startups 2 +80 Reforks 0
+34 Setup buffers 3 +84 NWAYs done 0
+38 CSR6 changes 4 +88 NWAY enable 0
+3C PTE->PFN translations 0 +8C NWAY state 0
+40 CSR13 (AUI=bit3 set)H 00000000 +90 NWAY link cnt 0
+44 Too many xsegs 0 +94 Autosense state 0
+48 Too few xsegs 0 +98 PHY address 00000000
+4C LW align (1 seg) 0 +9C Saved speed 0

-- EWB2 60-07 (SCA) Counters Information 5-APR-2007 17:12:13 --

Octets received 1885611864 Octets sent 2170481765
PDUs received 17775342 PDUs sent 17777722
Mcast octets received 792700872 Mcast octets sent 900391962
Mcast PDUs received 6717804 Mcast PDUs sent 6719343
Unavail user buffer 0 Multicast not enabled 0
Last UUB time None User buffer too small 0

-- EWB4 60-03 (DECNET) Counters Information 5-APR-2007 17:12:19 --

Octets received 0 Octets sent 52413950
PDUs received 0 PDUs sent 1048279
Mcast octets received 0 Mcast octets sent 52413950
Mcast PDUs received 0 Mcast PDUs sent 1048279
Unavail user buffer 0 Multicast not enabled 0
Last UUB time None User buffer too small 0

9 REPLIES
Volker Halle
Honored Contributor

Re: Decnet Phave IV over CROSSOVER Network Connection

A DECnet Phase IV end-node (check with MC NCP SHOW EXE CHAR) is not supposed to use more than one DECnet circuit at a time.

Volker.
Robert Gezelter
Honored Contributor

Re: Decnet Phave IV over CROSSOVER Network Connection

shailysingh,

Several things:

- DECnet Phase IV End Node can only use one circuit at a time

- Identify which circuit is which. Zero all of the counters (using the appropriate commands in the appropriate utilities).

- SCA traffic appears to be using both circuits (or has in the past made use of both). The previous step of zeroing the counters will identify what is actually active now.

- A reversed cable is never the issue. It looks electrically the same as being plugged into a 10/100BaseT hub/switch

You will need to check carefully, as each of the two machines may be configured slightly differently (hardware and/or software).

- Bob Gezelter, http://www.rlgsc.com
Shailender_1
Advisor

Re: Decnet Phave IV over CROSSOVER Network Connection

Thanks for improving for knowledge and providing me valuable suggestions. Yes both the nodes are configured as ENDNODE. I have seen SCS traffing increasing on the both the interfaces.

We have an application running which updates the data on primary node and same data is replicated to the secondary node over the decnet and user has complaint that data is not in sync on both the nodes there have been delay of couple of minutes have been obsevered. can this configuration caused this delay? If I change the NCP circuit state off does it impact the online operations. and is it going to help improving the data sysnc issue between the two networks ?


I have a VMS node configured as DECnet phase IV routing node in the Network. so If I plug second interface of both the Servers to the Switch, I think decnet would start using both the interfaces isn't it ?

Volker Halle
Honored Contributor

Re: Decnet Phave IV over CROSSOVER Network Connection

This point-to-point (crossover) cable is there for a reason: to make sure your cluster-communication survives a temporary failure of the other LAN connection/switch and prevent your cluster members from crashing. A cross-over cable is still the most reliable way to provide a secondary SCA interconnect between 2 cluster members.

No other protocols should be running on this connection, so you should turn off the EWA-1 DECnet circuit. It isn't being used anyway.

Regarding your 'replication problem', you did not provide enough information to even guess what may be wrong.

Does DECnet work reliably between the 2 nodes ?

Volker.
Volker Halle
Honored Contributor

Re: Decnet Phave IV over CROSSOVER Network Connection

Connecting the EWB (EWA-1) cable to a switch won't help. Those nodes are end-nodes and will only make use of ONE DECnet circuit at any time.

It would also cause problems on your network, as both LAN interfaces (EWA and EWB) will then have the SAME MAC address, when the second DECnet LINE (EWA-1) will be started and both EWA-0 and EWA-1 are connected to the same network segment.

Volker.
Shailender_1
Advisor

Re: Decnet Phave IV over CROSSOVER Network Connection

HOw can I check the reliability of decnet. So far we have not seen any disconnects of network. nothing in the errorlog, operator.log related to decnet. set host works fine. Decnet copy works fine. I have been monitoring the both the interfaces for the Decnet and could see increase in decnet sent traffic but the receive counts are always zero on EWB0 what does it mean. System tries to send decnet data over EWB as well so what happens when the data is send on EWB interface ? could this cause a delay in decnet response ?
Volker Halle
Honored Contributor

Re: Decnet Phave IV over CROSSOVER Network Connection

You may have noticed, that DECnet only sends multicast-messages via EWB and may not have set up the appropriate multicast addresses for receive, so it doesn't receive any DECnet packets on the cross-over cable.

One way to test DECnet between those 2 systems would be to run DTSEND tests, monitor the performance and watch for response timeouts in the node counters, these would indicate lost packets:

MC NCP SHOW NODE COUNTERS

Retry these DTSEND tests after turning off the EWA-1 DECnet circuit and see whether the performance is the same or different.

How does the replication work ? Over an existing logical link between applications on both nodes ? Or establishing a new link for every replication ?

Volker.
Hoff
Honored Contributor

Re: Decnet Phave IV over CROSSOVER Network Connection

If it is not clear from the previous discussions, if you want to use that circuit and your main (existing) circuit and you want to use some or all of the available connections as DECnet circuit(s), then configure both DECnet nodes on the ends of that cable and that circuit as routers.

atul sardana
Frequent Advisor

Re: Decnet Phave IV over CROSSOVER Network Connection

Hi sir,How R U........
I love VMS