Switches and routers interfaces name dictionary - networking

I am curently looking for a dictionary that contains all (or a lot) of interfaces names for routers and switches.
For instance a dictionary that would look like this :
[[Cisco : GigabithEthernet1/0/0, ..., GigabithEthernet1/0/28, FastEthernet1/0/0, ...],
[Juniper : ge-0/0/1, ..., ge-0/0/12,fa-0/0/1, ...,fa-0/0/12]]
I would like it to contain as much of interfaces names of as much of brand as possible.
I have already been looking for it for a long time now, but I have not been able to find anything so far. So if anyone has something to share on this it would be very much appreciated.
Thanks for reading.

A quick update to inform you that I have not been able to find a dictionnary and that after some research I find out that you don't need one if your problem is to identify interfaces on a switch or router.
Using SNMP, you can find which one of the interfaces on your machine is a physical or logical interface. So I used this reference to know which one of my interfaces are physical interfaces or not.
The OID is : 1.3.6.1.2.1.2.2.1.3
Thanks for the help I have been given so far !

Related

Difference Between "if_ether.h" and "ether.h"

I am currently trying to build an easy TCP structure in C, following the OSI model,
And I just found that there are 2 differents type of "ether" use no kernel related, which are using similar struct,
I guess the "if_ether.h" intervene if a L2 layer does not exist ?
Or an address is not set.
While the "ether.h" is there to configure directly if a use of the L2 is done.
Or is it something who intervene in case of protocol like "PPP", or anything who may bypass the L2 like a Rawsocket
Some stuff are blur.
Thank you in advance to share your light with me.
Take care !

Why mounting file systems is better design option than prefixing path names with a drive name or number?

This is an exercise from "Modern Operating Systems" book. In introduction there's a paragraph about this question
UNIX does not allow path names to be prefixed
by a drive name or number; that would be precisely the kind of device dependence
that operating systems ought to eliminate
Can someone give an example to show what kind of dependency it is?
If this is an actual question in the book—
Why mounting file systems is better design option than prefixing path names with a drive name or number?
—you need a different book to get a broader view of the world.The eunuch's system is a different way of doing things and it not necessarily a better one.
Non-eunuchs mainframe and mini systems typically use logical name translations so users do not actually even see the drive name/number.
Presumably the dependence they are referring to is having to code something to access "X:FILENAME", where X is a physical device. If the data moves to drive W: you then have to recode.
The question ignores systems that use logical device translation. They could use "ACCOUNTING_DATA:FILENAME" where ACCOUNTING_DATA is a logical device. Eunuch's would try to simulate something like that with symbolic links. However, the logical translation method is more flexible.
In short, it sounds like your book is rationalizing eunuch's idiosyncrasies as superior design.

GNS3: using a router as switch with it's functions

I took a look over the already asked questions and I didn't find the information I need. In case I miss the questions somehow, please accept my apologize.
I would like to know how can I use a router as switch on GNS3? Since GNS3 (at least in this moment) doesn't accept switches images, how can it be done?
Once this step is made, it is possible to use most the important switch functions? like etherchannel, trunk, multiple vlans etc.
Thank you very much.
Firstly, there is no true way to put switching into hardware, as of yet, that is. The TCAM's functions in L3 switches these days has yet to be perfected in software.
Secondly, there are a couple of ways to do this, but out of the three, two of them will either cost money or take some investigative work.
Drag the switch icon into the simulation. You can do vlan tagging as an access port, or as a trunk port. No etherchannel though. Alternatively, the 3725 Router has some switching capabilities using the 16-ESW card, however functionality is limited and syntax differs.
Buy VIRL from Cisco's website. It is basically an Ubuntu VM with Cisco routers, IOSvL2 (a switch essentially), ASAv, and a couple other virtual network devices. However, if you're not a student, it's a few bucks. In addition, it is subscription based
3.Upload IOU to GNS3. You will need:
-IOU image, found here: http://sourceforge.net/projects/gns-3/files/IOU%20VMs/
-Virtualbox
-License file for IOU
-GNS3 (Obviously)
-L2/L3 IOU images (The L2 images are switches)
You can find the instructions here: http://srijit.com/how-to-configure-iou-in-gns3-for-real-cisco-switching-labs/
Hope this helps.

SOA: Use SDO (Service Data Object)? [duplicate]

I've been programming in Delphi with Midas/DataSnap for quite long time and quite happy with it. Moving to .NET I'm more than happy with the ADO.NET DataSet. For CRUD application, I'm highly uncomfortable with any kind of ORM. Generic data-structure with automatic diff/delta handling get my job done better for me, an average database application developer.
Tried to study Java years ago, and could not find similar idea implemented. The closest I could find is SDO (Service Data Object). I thought it should be widely adopted when I saw it, but I'm wrong. Even the spec is rather old now, I still hardly find many people discuss on it or use it extensively. Assuming from information I can find on the internet, SDO usage is highly passive.
Wondering if it's dying ? Any experience in SDO you want to share ? Manual DTO coding is always better ?
Ok. I see. The answer is "no"
;)
Same for me when trying SDO first time. Old specs, passive feedback... Definitely NO.
I wouldn't recommend using SDO unless it's imposed on you by some other part of the project.
WebSphere process server uses SDO. It's not really a bad API once you learn it. But the spec and the documentation are vague. It doesn't spell out what happens if you ask for a field that doesn't exist, or whether it does type conversions while getting or setting fields, to name two gripes.
I don't think the API defines how to define new types, so that part will be implementation-specific. Type definitions are based on XSD, so you'll be working with those and all of the associated standards.
As others have implied, the API isn't widely used. This means it'll be hard to find people experienced with it, or help using it.

Pointers and online change in TwinCAT and CoDeSys

Are pointers safe against online change of running PLC program in TwinCAT 2.10 and in CoDeSys 2.3 on which the first one is based? What happens if memory block gets reallocated as part of online program change and there are pointers pointing to that memory block?
ADR (Address Operator) description in TwinCAT's help says:
Attention:
After an Online Change there might be changes concerning the data on certain addresses. Please regard this in case of using pointers on addresses.
It looks to me like pointers cannot be stored permanently if someone pretends to use online modification of the program. Otherwise if pointers are stored (for example as a binding between some data structures) online change should be avoided.

Resources