<div>
<div class="content wysiwyg-content">
If hardware is all the same, what's best practice for OSPF cost?<br />
<br />
<br />
Left:<br />
Egress and ingress are opposite of one another. &nbsp;(Egress/Ingress are not on the same connection) &nbsp;I like this setup, but i'm not sure if its best practice compared to the far right picture. &nbsp;I prefer this idea because inflow/outflow aren't shared on a link, but is this enough justification to be BP?<br />
<br />
Middle:<br />
Each core will be responsible for their &quot;side&quot;. (Left core/distro vs right core/distro) &nbsp;Not sure if this is correct...i'm just guessing<br />
<br />
Right:<br />
Primary/Secondary setup. &nbsp;(Left core takes care of everything, Right Core is backup)<br />
<a href="https://filedb.experts-exchange.com/incoming/2017/03_w13/1153569/OSPF-FLOW.png" target="_blank" class="file-inline" title="OSPF-FLOW.png (448 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>OSPF-FLOW.png</a>
</div>
</div>


OSPF-FLOW.png

If hardware is all the same, what's best practice for OSPF cost?


Left:
Egress and ingress are opposite of one another.  (Egress/Ingress are not on the same connection)  I like this setup, but i'm not sure if its best practice compared to the far right picture.  I prefer this idea because inflow/outflow aren't shared on a link, but is this enough justification to be BP?

Middle:
Each core will be responsible for their "side". (Left core/distro vs right core/distro)  Not sure if this is correct...i'm just guessing

Right:
Primary/Secondary setup.  (Left core takes care of everything, Right Core is backup)

OSPF best practice for COST

Cisco PIX is a dedicated hardware firewall appliance; the Cisco Adaptive Security Appliance (ASA) is a firewall and anti-malware security appliance that provides unified threat management and protection the PIX does not. Other Cisco devices and systems include routers, switches, storage networking, wireless and the software and hardware for PIX Firewall Manager (PFM), PIX Device Manager (PDM) and Adaptive Security Device Manager (ASDM).

Cisco

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

Networking software modules are interfaced with a framework implemented on the machine's operating system that implements the networking functionality of the operating system. The best known frameworks are the TCP/IP model and the OSI model. Systems typically do not use a single protocol to handle a transmission. Instead they use a set of cooperating protocols, sometimes called a protocol family or protocol suite.[9] Some of the best known protocol suites include: IPX/SPX, X.25, AX.25, AppleTalk and TCP/IP. Other protocols indirectly related to networking include the hypertext transfer protocol (HTTP) and its related technologies, Dynamic Host Configuration Protocol (DHCP), Domain Name Server (DNS) and other Internet protocols.

Networking Protocols

Network design and methodology, also known as network architecture, is the design of a communication network. It is a framework for the specification of a network's physical components and their functional organization and configuration, its operational principles and procedures, as well as data formats used in its operation. In telecommunication, the specification of a network architecture may also include a detailed description of products and services delivered via a communications network, as well as detailed rate and billing structures under which services are compensated.