We definitely have to review the cost structure at the end of this
mapping exercise!
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Rok Vidmar
Sent: Thursday, December 29, 2011 3:30 PM
To: hecnet at update.uu.se
Subject: Re: [HECnet] Re: Topology 28-Dec-2011
Are you looking at the links dynamically or based on what was
submitted
by each of us?
Dynamically, with ncp show adjacent nodes.
--
Regards, Rok
On 12/29/2011 11:37 AM, Steve Davidson wrote:
Brian,
".eqs." is a simple test for equality for strings. ".eq." is the
version for non-string (integer) values.
Multinet circuits are in the form of "TCP-x-y". Both "x" and "y" are
assignable and default to zero (0). I have been using "x" to denote
physical circuit and "y" to denote area end-point. This way I no longer
have to remember (or guess) what the other end is. SG1:: only has one
(1) NIC so in my case "x" is always zero (0).
DECnet LAN circuits are in the form of xxA-n, where "xx" is the
controller type, and "n" is the physical unit of that type (starting at
zero (0)).
Ok, then things work as I expect. :-D
Thanks!
-brian
Brian,
".eqs." is a simple test for equality for strings. ".eq." is the
version for non-string (integer) values.
Multinet circuits are in the form of "TCP-x-y". Both "x" and "y" are
assignable and default to zero (0). I have been using "x" to denote
physical circuit and "y" to denote area end-point. This way I no longer
have to remember (or guess) what the other end is. SG1:: only has one
(1) NIC so in my case "x" is always zero (0).
DECnet LAN circuits are in the form of xxA-n, where "xx" is the
controller type, and "n" is the physical unit of that type (starting at
zero (0)).
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Brian Hechinger
Sent: Thursday, December 29, 2011 11:25 AM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] DCL Help needed
On 12/29/2011 11:17 AM, Steve Davidson wrote:
Steal and steal often is my motto :-)
Take whatever you need! The new version will be better commented and
not require the reboot. I will place a copy of the old version of the
data file (it matches this version) in the same directory.
I'm assuming .eqs. is rather limited (say the way = is in bash)?
Is there any sort of regex style matching available?
Short of that, is it fair to say that all circuit names in the output of
show known circuits will always be in the form of XXX-N for non-multinet
tunnels?
-brian
On 12/29/2011 11:17 AM, Steve Davidson wrote:
Steal and steal often is my motto :-)
Take whatever you need! The new version will be better commented and
not require the reboot. I will place a copy of the old version of the
data file (it matches this version) in the same directory.
I'm assuming .eqs. is rather limited (say the way = is in bash)?
Is there any sort of regex style matching available?
Short of that, is it fair to say that all circuit names in the output of show known circuits will always be in the form of XXX-N for non-multinet tunnels?
-brian
