Routing Switching DC Management

▪ BGP Ethernet-Channel HSRP ▪ STP Proxy ARP VSS v.s VPC Radius
OSPF VRRP RSTP
IS-IS ▪ LACP GLBP MSTP Grutuius ARP VDC Tacacs
EIGRP ▪ PagP
▪ Load Balancing FEX Tacacs+
▪ Root Bridge
========== CEF
▪ MPLS (QOS) BPDU filter DHCP snooping
L2MPLS VPN BPDU Guard VDC divided SNMP
L3MPLS VPN Root Guard the nexus
AAA
switch into
▪ Port Status multiple
▪ VRF Port-Fast switches
▪ Address family Normal vdc
Storage vdc
ACI Firewalls
Redistribution ASA
Control the network (filtering)

VPN PaloAlto
Multicast Fortigate
SD-Wan Checkpoint
Qos
SRX
NSX
 EIGRP OSPF BGP
Hello 224.0.0.9 Hello Open
▪ Open TCP session
Update: - ▪ 224.0.0.5: From All → R
▪ Contains hold down timer & R.ID
▪ at Start R➔R
▪ at Change DR/BDR➔R
Keep-Alive
▪ 224.0.0.6: R → DR/BDR ▪ Keep the TCP session stay up
Query: - If S Down & no FS
▪ Sent every 60 sec
Reply: - To the Query ▪ The hold-time = 3 keep-alive
DBD: Data Base ‫ملخص عن الـ‬
Ack : it is reply for all = 180 Sec
messages except the hello & Update
LSR: ‫سؤال لمعلومات أكثر عن روتر أول مرة أسمع عنه‬ ▪ Contains info about destination
query
N/Ws and the attributes

LSU: ‫الرد‬ Notification

▪ used to identify there is a problem
LSA ACK: ACK ‫الروتر اللي سأل هيبعت‬ in the router like (CPU, Memory,…)

Message Status OSPF BGP

EIGRP OSPF BGP OSPF BGP LSA Type Metric
Hello Hello Open Down idle 1- Router: All Routers (O) Weight (Cisco)
Update DBD Keep-Alive ▪ Router (ID & Type)
Connect Local Preference
Neighbor discovery Internal- -Backbone
Query Update Attemp Active ABR - ASBR
LSR ▪ Link IP Local injected
Reply Notification init
LSU Open Sent ▪ Link Type =
Ack 2-Way
LSA ACK Open Confirm ➢ P2P Local Originate
➢ Virtual
➢ Loopback AS Path
Route discovery Establish ➢ Stub: Connected to
Exstart (M&S)
end device MED
Exchange
➢ Transit: Connected to
Loading
anther Router
OSPF Full
2- N/W : DR
DR/BDR: Non Preemptive

‫ وقع‬DR ‫يعني لو الـ‬ 3- N/W Summary : ABR (OIA)

‫ هيتشغل مكانه على طول‬BDR ‫الـ‬ 4- ASBR Summary : ABR
DR ‫ القديم قام مش هيشتغل تاني كـ‬DR ‫حتى ولو الـ‬
5- AS External : ASBR (OE1&2)
‫إال إذا عملنا‬ 7-NSSA External:ASBR of NSSA
(ON1&2)
Clear ip ospf process ‫أو‬ restart
6- Multicast : Not Supported by Cisco

DR& BDR: Non Primpteetive 1- O

1- First Router running OSPF with Enough time (4 Hello) 3- OIA
5- OE 1 & 2
2- Highest Priority interface
7- ON 1 & 2
3- Highest R.ID Any Filter O*IA
1) Manually
2) Highest IP of Loopback interface
3) Highest IP of Physical interface Master: Highest R.ID
 Neighborship Conditions
EIGRP OSPF BGP
▪ Direct connected ▪ Direct connected ▪ It’s not necessary
▪ Same Network ID ▪ Same Network ID To be direct connected.
AS # Same of the Following: Same Authentication
Authentication ▪ Area ID
K-value (BLD-RM) ▪ Area Type (Backbone area – Ordinary)
(Stub - Totally Stub - NSSA – Totally NSSA)
MTU Size xxxx
▪ Hello & dead time interval
▪ Authentication
▪ MTU
▪ Topology
➢ P2P
➢ P2Multipoint
➢ B.C Multiple Access
➢ NBMA

1- Hello: - Neighbor discovery & Maintain Neighbor Relationship.

2- Update: - at Start send full Routing Table & at Change send the change routes only
3- Query: - Sent only when there is no Route to destination
4- Reply: - it is the reply for the query
5- Ack : it is reply for all messages
except the hello & query message as the reply of hello is hello the reply of the query is reply
 BGP Status
1- idle
2- Connect
Open message
3- Active
➢ idle 1- BGP version
4- Open Sent 2- Hold-Time
3- Router-ID
5- Open Confirm 4- AS #
6- Establish

BGP Status in details

1- Idle Attempt to open TCP session over port 179
2- Connect state waiting the three-way handshake
▪ If successful, the Router will be in Open sent state
▪ If NOT successful the Router will be in active state & retry again after 60 Seconds.
✓ if successful, it will be in open sent state and
✓ if not successful, it will return to idle state, & retry again after 120 Seconds.

The router will be in Active state if

1- The neighbor NOT configured yet,
2- The IP address of the neighbor does not exist.
3- There is a firewall “ACL” between the router & its neighbor prevent TCP 179 session to be up.

❖ Open message:
1- Hold-time
2- BGP version
3- Router-ID
4- AS Number
✓ if my peering (neighbor)) is in wrong AS,
the notification message will be send and will tearing down (close) the TCP session

✓ If successful, it will receive open Confirmation

✓ If not successful a notification message will be sent and close the TCP session

3- Open Confirm: The router received agreement from his Neighbor

4- Establish:
▪ Peering is forming &
▪ BGP table exchanged &
▪ a keep alive message will be sent every 60 Sec to keep the session up always
 Configuration Steps
1- Create loopback interface
2- Configure IGP ((OSPF, EIGRP, IS-IS, RIP)) inside AS
3- Advertise the loopback in between the neighbors
▪ Inside AS we use the IGP (( OSPF, EIGRP, IS-IS, RIP ))
▪ Between AS we use static route
4- As we use loopback, we have to use update-source loopback 0
After writing neighbor command to inform the router to use the loopback to send & receive the update

5- Then ask yourself the following questions:

[1] The border router is going to make neighborship with another border router in another AS?
so, you have to use
1- Next-hop Self command
2- EBGP- multi-hop command Because the TTL of EBGP=1
[2] The router use authentication for the neighborship so use the password command
[3] xxxxxxx
[4] Xxxxxxxxxxxxx
[5] xxxxxxxxxxxxxxxxxxxxx
 VLAN
Switch 1(config) # interface F1/1
# Switchport mode Access
‫مفيش تفاوض مع الطرف التاني‬
Trunk
dynamic Auto ‫بيتفاوض مع الطرف التاني‬
dynamic desirable

.‫ بدون تفاوض مع الطرف الثاني‬Access ‫ هيبقى‬Access ‫الـ‬

.‫ بدون تفاوض مع الطرف الثاني‬Trunk ‫ هيبقى‬Trunk ‫الـ‬
Trunk ‫ والطرف التاني‬Access ‫▪ بس مينفعش نخلي طرف‬

‫ بيتفاوضوا مع الطرف التاني مع العلم بإن‬dynamic Auto & dynamic desirable ‫الـ‬

Access ‫ بيميل إلى أنه يبقى‬Auto ‫الـ‬ ▪

Auto ‫ وهو أقوى من الـ‬Trunk ‫ بيميلي إلى إنه يبقى‬desirable ‫الـ‬ ▪
desirable ‫ والطرف التاني كان‬Auto ‫➢ بمعني لو طرف كان‬
‫ هو اللي يكسف‬desirable ‫ يبقى ال‬Auto ‫ أقوى من الـ‬desirable ‫وبما أن الـ‬
Trunk ‫ يبقى اللينك هيبقى‬Trunk ‫ بيميل إلى إنه يبقى‬desirable ‫وبما أن الـ‬

Auto ‫ مع‬Auto ▪
Access ‫ يبقى الطرفين‬Access ‫ بيميل إلى أنه يبقى‬Auto ‫كده الطرفين هيتفاوضوا وبما إن الـ‬

desirable ‫ مع‬desirable ▪
Trunk ‫ يبقى الطرفين‬desirable ‫ بيميل إلى أنه يبقى‬desirable ‫كده الطرفين هيتفاوضوا وبما إن الـ‬

desirable ‫ مع‬Auto ▪
‫ بيميل إلى إنه يبقى‬desirable ‫ هو اللي يكسف والـ‬desirable ‫ يبقى ال‬Auto ‫ أقوى من الـ‬desirable ‫كده الطرفين هيتفاوضوا وبما إن الـ‬
Trunk ‫ يبقى اللينك هيبقى‬Trunk

Access Trunk dynamic Auto dynamic desirable

Access Access Not recommended Access Access

Trunk Not recommended Trunk Trunk Trunk

dynamic Auto Access Trunk Access Trunk

dynamic desirable Access Trunk Trunk Trunk

 Spanning Tree Security
Protect against un-expected BPDU

1- BPDU Filter: if the port received BPDU

and the port was configured as Port-Fast

The port will leave its Port -Fast-State

and goes to Normal STP Status [ Blocking --- Listening ---- Learning --- Forwarding ]

‫ولو شيلنا السويتش اللي إتوصل بالبورت ده‬

‫ تاني‬Fast -Port ‫البورت ده هيرجع‬

2- BPDU Guard: if the port received BPDU

It will go to error-disable-state
And the port will stop all its activities until solving this issue

We can solve it

Manually Automatically

By reset the port By configuring in-Advance (‫)مسبقا‬

to recover the error automatically after (300 Seconds)
# Shutdown if the port doesn’t receive any BPDU on this port again
# No Shutdown
# Err-disable recovery cause

So after (300 Seconds);

➢ The port will work normally if the port doesn’t
receive any BPDU on this port again.

3- Root Guard: if the port received Superior BPDU [[ BPDU Saying that the New Switch is the R.B(Root-Bridge)]]
the port will go to inconsistent-State and the port will stop its all activities until removing the cable from this port.

Configuration for Catalyst 2900XL/3500XL and 2950/3550

Switch(config)# interface fastethernet 0/8
Switch(config-if)# spanning-tree Root Guard

Configuration for Catalyst 4000/4500 and 6000/6500

Switch(config)# interface fastethernet 3/1
Switch(config-if)# spanning-tree Guard Ro ot
 DHCP Snooping
It is a way to save us from Man-In-The-Middle Attack

Man-In-The-Middle ‫حوار الـ‬

Gratuitous ARP ‫ والكالم ده بنسمية‬ARP reply ‫ في عملية الـ‬G.W ‫ بتاعه على إنه هو الماك بتاع الـ‬MAC ‫هو إنه بعت الـ‬
ARP ‫وبكده يكون بوظ الـ‬
ARP Poisoning or (ARP Spoofing) ‫علشان كده بنسميها‬

Gratuitous ARP: is an ARP Response that was not prompted by an ARP Request.
The Gratuitous ARP is sent as a broadcast

To solve this issue

Man-In-The-Middle Attack

The IP of the G.W The MAC of the G.W

 Redundant link
➢ Redundant link between switches provides redundancy.
Also possibility to create loops when switches do Broadcasts.
▪ Broadcast storms
▪ MAC-Table instability
▪ Multiple frame Copy

Spanning-Tree Protocol
▪ Stop the loops which occurs when you have Multiple links between the switches
▪ Avoiding Broadcast Storms, Multiple Frame Copies & MAC-Table instability.
▪ It is enabled by default on all Cisco Catalyst switches

The idea of Spanning Tree Protocol is that

➢ All the switches on the network select Root Bridge between them
and all the other switches will become Non Root Bridge.

➢ All the ports on Root Bridge will become Designated Port

and the ports of Non-Root Bridge will become either Root port or Designated port or Non-Designated Port
(Blocking Port)

The Question now is according to what the switches select the Root Bridge?

▪ The switch select the Root Bridge depending on something called Bridge id.
▪ The switch which has lowest Bridge id will become Root Bridge
▪ And all the other switches will become Non Root Bridge

What is the bridge ID

➢ The bridge ID it is either priority or the MAC address of the switch.
so the selection first depend on the priority and if the priority of the switches are equal the selection will depend
on the MAC address of the switch.

➢ The priority of the switch depends on the Extended System ID; If it is:-
1- Disabled
▪ The default priority is 32768
▪ it can be any value from this range (0:65535)

2- Enabled (default in the most of the switches)

▪ the default priority (32768 + VLAN ID)
▪ it can be any value from multiply of 4096 (0,4096, 8192…)
▪ in this case the priority range (0:61440)
We can change the priority as we need but it must be value pf multiply of 4096.
➢ The switch which act as root bridge it must be the core switch and it must have high resources
(Memory, high processor….)

➢ recommended to select high speed switch to be Root-Bridge by one of the following methods
[1] changing the priority
[2] Primary/Secondary command

➢ the secondary RB reduce its priority 4096 from the default value (7*4096=28672)
the primary RB reduce its priority 8192 from the default value (6*4096=24576)

➢ So, if we use the Primary/Secondary command the default priority will become For
o secondary RB = 28672
o Primary RB = 24576

➢ So, if we want to let the specific switch primary for specific VLANs (Ex VALN 10,20) and secondary for other VLANs (Ex VALN 30,40) we can do it
by two ways as we mentioned before.

1- By changing the priority

▪ Switch (config)# Spanning-tree VLAN 10, 20 priority 0
# Spanning-tree VLAN 30, 40 priority 4096

2- By using Primary/Secondary command

▪ Switch (config)# Spanning-tree VLAN 10, 20 root primary ( in this case, the priority for VLAN 10,20 is 24xxx)
# Spanning-tree VLAN 30, 40 root secondary ( in this case, the priority for VLAN 10,20 is 28xxx)

➢ We have to pay attention when we use the second method because if there is another switch has a priority lower than 24xxx the root port switch
will decrease its priority by multiply of 4096 until become lower than any other switch. But, the problem is that if there is the switch has a priority
lower than 4096, the root bridge will not be able to decrease its priority more than 4096. In this case, we have to use the first way instead of the
second way or we increase the priority of the other switch to be more than 4096.

The idea of STP:

1- One root bridge per N/W
2- One root port per non root bridge
3- One designated port per segment
4- All the other ports will become Non designated port
 STP Types

1- STP version 1 (common Spanning-tree)

▪ If we did not connect the cable to the port, the port will be in blocking state.
▪ And as soon as we connect the cable to the port, the port will go to listening state and it will stay in this state
15 seconds.
▪ After that, it will be either blocking port (so it will go to blocking state again) or (RP or DP, or ??
the question mark refers to that port did not know in which state it is) and in this case the port will go to the
learning state and it will stay 15 seconds in it. And after that the interface will be either blocking port (so it will
go to blocking state again) or (RP or DP) and it will go to forwarding state.

▪ As we can see, the ports will go to forwarding state after 30 seconds and it is long time in the network field.so,
cisco enhanced this protocol by adding three features on it.
➢ Cisco enhancement
▪ Port Fast
▪ Uplink Fast
▪ Backbone Fast

1- Port fast
if we need to let the port go to forwarding state immediately (without passing through listening state and learning state) as
soon as connecting cable, we have to configure it as port fast. (spanning-Tree PortFast)

2- Uplink fast (for direct change)

as we said before, we have only one RP per non root bridge and if this port go down, the switch will try to select
another port to act as RP.

But, by this feature (uplink fast feature) the switch will pre calculate its calculation and select backup port for root
port and when the primary root port goes down, the backup port will work as root port immediately without any
delay (the status of the backup port is blocking before the root port become down)
3- Backbone Fast (for indirect change)

If one switch lost the connection to the RB and send message to the connected switches to inform them that the RB
is down, the received switches will check by themselves if the RB is actually down or not by sending RLQ
(request link query) to the RB. Asking him if it is down or no and if it is not down, it will reply on RLQ by another
message RLR (Request Link Reply) says that it is still up and the received switch will send to the switch who lost
the connection to the RB telling him that RB is still up and they can do the election to select another port to be RP
and by this feature the switch will spend (15+15=30 seconds) instead of (10 hello time

+15+15=50 seconds) so the conversion time became 30 seconds instead of 50 seconds by using this feature
(Backbone Fast feature)
2- Rapid STP (STP version 2)

▪ it is STP v1 + Cisco enhancement)

▪ They grouped the blocking state and listening state into one state and named it into discarding state.
▪ The ports are
1- Root port
2- Backup RP called Alternative port Alternative port = equivalent to uplink fast

3- Designated Port
4- Backup DP called Backup Port
We will not see this port anymore because it is existing only when
we connect the switch to the HUB (HUB not exist anymore)

▪ Port fast become existed.

▪ on cisco devices, it is named portfast
Some of on non-cisco devices it named it as port fast
and Some of on non-cisco devices it named it as Edge port

3- PVST (it is used when we use ISL Trunking Protocol) Cisco Proprietary Load Sharing
4- PVST + (it is used when we use dot1Q Trunking Protocol)
PVST and PVST +

▪ ISL not exists anymore, =➔ so, the PVST not existed anymore
▪ so there is only PVST+ and there is no PVST
So they renamed PVST+ to be PVST but in this case it use dot1Q

5- RPVST: it provides Load Sharing & Redundancy Cisco Proprietary

Load Sharing : it will let a switch act as RB for a group of VLANs

and another switch act as RB for another group of VLANs

Redundancy: it will let a switch act as primary RB for a group of VLANs

and backup for another group of VLANs

And anther switch act as backup for the group of VLANs which have primary RB
and act as a primary for another group of VLANs which have backup RB.

For example,
switch A (primary for VLAN 10, 20,30 and backup for VLANs 40,50)
switch B (primary for VLANs 40,50 and backup for VLAN 10, 20,30)

6- MST (also known as Multiple Instance Spanning Tree Protocol (MISTP) on Cisco Catalyst 6500 switches and above)
➢ Same RPVST but it is standard
➢ Allow more VLANs to be mapped to one single instant of STP
 STP Types
1- STP version 1 (common Spanning-tree)

➢ Cisco enhancement
▪ Port Fast
▪ Uplink Fast
▪ Backbone Fast

▪ Port Fast: The port goes to the forwarding state immediately.

▪ Uplink Fast: Backup for R.P

▪ Backbone Fast: When SW detect that the R.B is down

it will inform the other SWs
The other SWs Will ask the R.B if it is really down or no (request link query)

The R.B will really on this message by sending another message (Request Link Reply)
says that it is still up and the received switch will send to the switch who lost
the connection to the RB telling him that RB is still up

Rapid STP (STP version 2)

▪ it is STP v1 + Cisco enhancement)

▪ They grouped the blocking state and listening state into one state and named it into discarding state.
▪ The ports are
1- Root port
2- Backup RP called Alternative port Alternative port = equivalent to uplink fast

3- Designated Port
4- Backup DP called Backup Port
We will not see this port anymore because it is existing only when
we connect the switch to the HUB (HUB not exist anymore)

2- PVST (it is used when we use ISL Trunking Protocol) Cisco Proprietary Load Sharing
3- PVST+ (it is used when we use dot1Q Trunking Protocol)

4- RPVST Load Sharing

5- MST Redundancy

Standard Cisco STP RSTP

STP PVST : Per VLAN STP Hello 2 Seconds 2 Seconds
RSTP PVST+ : Per VLAN STP
MST RPVST : Rapid per VLAN Dead 20 Seconds = 10 Hello 6 Seconds = 3 Hello
 STP

Root-Bridge for all VLAN

PVST & PVST+

Root-Bridge for some VLAN

And another Root-Bridge fro some VLAN

RPVST & MST

Primary Root-Bridge for Some VLAN

Secondary Root-Bridge for Some VLAN
 The Priority can be only multiple of 4096 (0, 4096, 8192, ….)
Secondary reduces priority 4096 from default value
primary reduces priority 8192 from default value

Recommended to select High Speed Switch to be R.B (Root Bridge) by doing one of these methods
1- Change the priority
2- Primary / Secondary Command

If the STP-Extended Sysyem-ID is enabled ( default in most SWs)

Default priorty will be 32768 + VLAN ID)
.
.
In this case priority range (0: 61440) and it should be only multiple of 4096

Sw(Config)# Spanning-Tree VLAN 10,20 priority 0

# Spanning-Tree VLAN 30,40 priority 4096

‫أو‬

Sw(Config)# Spanning-Tree VLAN 10,20 root Primary

# Spanning-Tree VLAN 30,40 root Secondary
VSS (Catalyst 4500, 6500, 6800) VPS
Virtual switch system Virtual port channel
Catalyst Switch (4500 - 6500 - 6800) Nexus Switch
Support L3 Port-Channel Support L2 Port-Channel
Support
Support
▪ LACP
▪ LACP Only
▪ PAGP

VSS (4500 – 6500) VPS

Virtual switch system Virtual port channel
Catalyst Switch Nexus Switch (5000 – 7000 and the newer)
Support L3 Port-Channel Support L2 Port-Channel
Support
Support
▪ LACP
▪ LACP Only
▪ PAGP
Once the SWs are configured in VSS, Their control plan are still separated.
they get merged Logically and become one logical SW
Both SWs are controlled individually by their respective
from control Plan
SUP.
This means that we have single control plan is
controlling both the switches in active and standby
manner
There is only 1 IP used to access & managed the SWs There are 2 IPs used to access & managed the SWs
Control messages & data frame. Flow between Active & Control messages are carried by CFS over peer link &
Standby Via VSL (Virtual Swtiching Link) Peer keep a live link
If the active SW fail ; the other SW will take place of it As the 2 SWs separately; we need to configure gateway
redundancy same as in traditional manner

VSS and vPC are both Cisco technologies used to create redundant network connections, but they have
some key differences:

Technology Platform:

• VSS (Virtual Switching System): Works with Cisco Catalyst 4500, 6500, and 6800 series switches.
• vPC (Virtual Port Channel): Used on Cisco Nexus 5000, 7000, and newer series switches.
Control Plane:

• VSS: Single control plane for both switches. This simplifies management but creates a single point
of failure if the control plane malfunctions.
• vPC: Separate control plane for each switch. This provides better redundancy and fault tolerance.

Port Channeling:

• VSS: Supports both L2 and L3 port-channel. This allows for increased bandwidth and redundancy at
both the data and routing levels.
• vPC: Supports only L2 port channeling. This increases bandwidth but doesn't extend redundancy to
routing protocols.

Redundancy Protocol:

• VSS: Doesn't require additional redundancy protocols like HSRP (Hot Standby Router Protocol)
because it has a single, active control plane.
• vPC: Requires HSRP or VRRP (Virtual Router Redundancy Protocol) for redundancy at the Layer 3
level.

Management:

• VSS: Managed as a single logical switch, simplifying configuration.

• vPC: Requires configuration on both individual switches, making it slightly more complex.

Applications:

• VSS: Commonly used in campus environments where high bandwidth and simplified management
are desired.
• vPC: More suited for data center environments where redundancy and high availability are critical.

Here's a table summarizing the key differences:

Feature VSS vPC

Platform Catalyst 4500, 6500, 6800 Nexus 5000, 7000, newer
Control Plane Single Separate for each switch
Port Channeling L2 and L3 L2 only
Redundancy Protocol Not required HSRP or VRRP
Management Single logical switch Requires configuration on both switches
Applications Campus environments Data center environments
 VSS
IOS Version must be the same [ Show Version | include ios]
and we have to install license (IP Base or Enterprise Service) [Show license image levels] =➔ Enterprise is installed & configured
 ‫‪Data Center Terminology‬‬
‫تعادل‬
‫‪▪ VDC : Virtual Device Context‬‬ ‫‪VLAN‬‬

‫‪VSS‬‬
‫‪▪ VPC : virtual Port Channel‬‬

‫‪▪ OTV : Overlay Transport Virtualization‬‬ ‫بعض‬ ‫ربط ‪2 Data Center‬‬

‫‪▪ FP : Fabric Path‬‬ ‫‪STP‬‬

‫‪▪ UP : Unified Port‬‬ ‫‪Fiber & Ethernet & FOCE‬‬ ‫بورت‬

‫يشتغل‬

‫الـ ‪VDC‬‬
‫هي تقسم الـ ‪ Nexus Switch‬إلى أكثر من سويتش زي الـ ‪VLAN‬‬

‫الـ ‪VPC‬‬
‫هو جعل إثنين ‪ Nexus Switch‬يشتغلوا وكأنهم سوتيش واحد زي الـ ‪VSS‬‬

‫الـ ‪OTV‬‬
‫هو ربط ‪ 2 Data Center‬في مكانين مختلفين أو دولتين مختلفتين‬
‫على ‪ L2 N/w‬ويشتغلوا وكأنهم ‪ N/W‬واحدة‬

‫الـ ‪FP‬‬
‫هو بروتوكول خاص بسيسكو‬
‫ويعتبر بديل الـ ‪ STP‬في الـ ‪ IOS‬العادية‬

‫وباقي الشركات بتسخدم برتوكول إسمة ‪Trill‬‬

‫الـ ‪UP‬‬
‫هو بورت ينفع يشتغل ‪ Fiber‬أو ‪ Ethernet‬أو ‪Fiber over channel Port‬‬

‫الـ ‪Series‬‬
‫الـ ‪5500 & 5600‬‬
‫تحتوي على ‪UPs‬‬
‫وبالتالي أقدر أوصلهم بالـ ‪Storage Devices‬‬
 ‫‪Nexus Switch Series‬‬
‫‪1000 : Support Vcenter v6‬‬
‫( حاجة كده زي الـ ‪2000 : FEX ( Line card‬‬
‫علشان كده بتستخدم في البنوك ‪3000 : There is no delay‬‬
‫‪: 4000‬‬
‫معلمول علشان لو عندي سيوتشات من ‪ Vendors‬تانيين وحابب أستخدمهم في النتورك بتاعتي زي ‪Dell / IBM‬‬

‫لذلك لو معنديش سويتشات من ‪ Vendors‬تانية‬

‫فمفيش داعي أستخدم الـ ‪Series 4000‬‬
‫أقوى السويتشات ‪5000 :‬‬
‫قريب جدا من ‪6000 : Series 5000‬‬
‫( تحتوي على ‪ Features‬الـ ‪7000 : (VDC – OTV – MPLS‬‬
‫مفيش ‪8000 : Series 8000‬‬

‫‪9300‬‬ ‫‪Fixed Switch‬‬

‫‪9000 : ACI‬‬
‫‪1000‬‬ ‫‪9300‬‬ ‫‪Modular‬‬
‫‪Switch‬‬

‫‪9504‬‬
‫‪9508‬‬
‫‪9516‬‬

‫الرقم األخير بيشير إلى عدد الـ ‪ Line Card‬اللي ممكن أركبها‬
‫الـ ‪ Module‬ممكن يكون فيه ‪ 4‬أو ‪ 8‬أو ‪16 Port‬‬

‫‪7018‬‬

‫الرقمين األخيرين بيشير إلى عدد الـ ‪ Line Card‬اللي ممكن أركبها مضافا إليه ‪2 Supervisor‬‬
‫يعني هنا عندي ‪ 16 line card‬و ‪2 Supervisor‬‬