How would you model physical and logical network resources, and what do you do when discovery disagrees with the inventory?
Logical network inventory should separate physical equipment, logical resources and services, then reconcile discovery as observed state against intended inventory. Do not overwrite the record blindly; classify gaps as faults, drift or orphaned resources. It also connects resource management to the point an interviewer is testing.
Answer
Short answer
Model telecom inventory in three layers: physical resources such as sites, cards and ports; logical resources such as VLANs, IPs and circuits; and services that consume them. Discovery is observed state, while inventory is intended state, so reconciliation should classify differences instead of blindly copying network data into the inventory.
Was this answer helpful?
Likely follow-ups
- Two orders reserve the last port on a card within the same second. What stops both from succeeding?
- How long should a released IP address stay unusable, and what decides that?
- Discovery finds a configured VLAN that no service in your record explains. What is your process?
- How would you model a resource that is shared by many services, such as a trunk or a wavelength?
Related questions
- A transform has been writing wrong revenue figures for three days and six downstream tables have consumed it. How do you backfill the corrected data without double-counting anything?hardAlso on reconciliation4 min
- How does the reserve figure your systems produce end up changing next year's rates, and where does that loop break?hardAlso on data-modelling6 min
- What is a loss development triangle, and what does the actuary need from your claims system that reporting does not?hardAlso on data-modelling5 min
- We sell to trade customers who each negotiate their own prices, and those prices change. Design the schema.hardAlso on data-modelling5 min