BGP is a fairly simple protocol, which is why it’s so flexible. When the BGP session is established, routes are exchanged between BGP peers via UPDATE messages. BGP routers receive the UPDATE messages, run some policies or filters over the updates, and then pass the routes to other BGP peers. An implementation is required to keep all BGP Full Article…
Search the Wiki
BGP Attributes detailed
The ORIGIN Attribute The ORIGIN attribute is a well-known mandatory attribute (Type Code 1) that indicates the origin of the routing update with respect to the autonomous system that originated it. BGP considers three types of origins: IGP – via command network EGP – old EGP protocol Incomplete – redistributed into BGP The AS-PATH The AS_PATH attribute Full Article…
Basic BGP Workflow
Establish TCP Transport – you need to have IP reachibility between BGP peers. You need to think about BGP more as an application. It uses TCP port 179, unlike OSPF or EIGRP you dont enable the BGP on link level, you define the static peers that establish the TCP transport under the BGP process configuration. Full Article…
OSPF Basic Functionality
It is important to note that when you are configuring in the SP the OSPF between the P routers they must have IPv4 reachibility between its loopback interfaces as these loopback interfaces will be used in MPLS tunnels as source IPs. Then the INE was quite shity regarding OSPF
FC Switching Overview
In high level we can say that FC is protocol that replaces SCSI disk cable with a network. The host machine thinks the disk is locally connected with SCSI cable but it is not, the disk is accessed via SAN network through the FC protocol. So we moved from this to this FibreChannel is just Full Article…
SAN overview
There are 3 main high level components that makes SAN: Storage arrays – these are the arrays of disk from various vendors. They offer various level of redundancy, connection ports, protocol support SAN Switches – storage area network devices that connect the servers and their remote disks. HBA (Host Bus Adapters) – The NICs to Full Article…
UCSM Overall Architecture
The architecture of UCSM consists of multiple layers with well-defined boundaries. External interfaces provide communication with the outside world. The Data Management Engine (DME) is the central service that manages the components of a UCS. Application gateways act as a hardware abstraction layer between the DME and the managed End-Points (EPs). The EPs are the actual devices or entities Full Article…
UCSM Operating Principles
Policies UCSM is a policy-driven device manager. Policies control behaviors and configurations. They control how a server or other components of the UCS will act or be affected in specific circumstances. The UCSM has a large number of different policies.These policies describe and control all aspects of the UCS such as network, storage, server configurations, and system behavior. Rules are defined Full Article…
UCSM integration with VMWare
Virtualization Support. UCS virutalization support includes VN-Link hardware capable adapters, provisioning of vNIC through policies and configuring VIFs. Support for integration with VMware is embedded in the service-profiles, which allows for dynamic VIFs definition and policy consumption. Multiple dynamic vNIC connection policies can be created and each of the policies defines a number of dynamic vNICs. A service Full Article…