PPP over Frame Relay (PPPoFR) could be used for :
- Need for authentication between routers
- Need for same IP on multiple DLCI and static mapping not permitted.
int s0/0
encap frame-relay
frame-relay interface-dlci XXX ppp virtual-template1
frame-relay interface-dlci YYY ppp virtual-template1
int virtual-template1
ip add 10.0.0.1 255.255.255.0
ppp authentication chap
dimanche 6 décembre 2009
dimanche 29 novembre 2009
3550 QOS : WRR
On 3550 : Weighted Round Robin is done per packet
On 6000/6500 : Weighted Round Robin is done by bandwidth
wrr-queue bandwidth 10 20 30 40
On gigabit ports:
The 4 queues could be assigned a different amount of buffer size and WRED or RED with 2 thershold by queues :
Wred :
wrr-queue random-detect max-threshold 1 50 100
On non-gigabit ports:
Only FiFO with a reserved number of packet by queues, (max 170) :
mls qos min-reserve level buffer_size
wrr-queue min-reserve level queue
On 6000/6500 : Weighted Round Robin is done by bandwidth
wrr-queue bandwidth 10 20 30 40
On gigabit ports:
The 4 queues could be assigned a different amount of buffer size and WRED or RED with 2 thershold by queues :
Wred :
wrr-queue random-detect max-threshold 1 50 100
Red :
wrr-queue threshold 1 50 100
Queue Size:
wrr-queue queue-limit Q_size1 Q_size2 Q_size3 Q_size4
On non-gigabit ports:
Only FiFO with a reserved number of packet by queues, (max 170) :
mls qos min-reserve level buffer_size
wrr-queue min-reserve level queue
3560 QOS
Differents tasks that could be asked :
1 Map Ingress DSCP value to different queues and WTD :
There is 2 input queues each with 2 different WTD threshold
Followinbg example maps dspc 00 and 01 to the queue 1 threshold 2 and configure for queue 1 and threshold 1 of 75 and threshold 2 of 50 and for queue 2 a threshold1 of 30 and a threshold 2 of 75
mls qos srr-queue input dscp-map queue 1 threshold 2 00 01
mls qos srr-queue input threshold 1 75 50
mls qos srr-queue input threshold 2 30 75
2 Configure the ingress bandwidth association to queues
Here 20 % is dedicated to Expedite queue 2, the remain bandwidth is shared between queue 1 35% and queue 2 45%
mls qos srr-queue input bandwidth 35 45
mls qos srr-queeu input priority 2 bandwidth 20
3 Modifiy default buffer
Buffer is the amount of packet each queue could contains before dropping
Input buffer is globally modified with :
mls qos srr-queue input buffer 60 40
Ouput is modified by Queue-set. Queue-set 1 is by default applied to all interfaces with egal shared. To apply a different queue-set to an interface :
mls qos queue-set output 2 buffers 40 20 20 20
int fa0/14
queue-set 2
4 Configure bandwidth shaping and sharing on interface
Shaped queue limit the bandwidth, whereas shared only limit during congestion.
Shape weight is an inverse ration 1/weight
Share weight is a ration weight_queue1/total_weight
0 in shape means queue is treated as shared. The remain bandwith is for shared.
A queue in shape mode is not take into account on the shared ratio.
Example Queue 1 is a shared queue with 12,5 percent of the bandwidh, the remaining bandwidth is shared among q2, q3, q4.
srr-queue bandwidth shape 8 0 0 0
srr-queue bandwidth share 25 25 25 25
1 Map Ingress DSCP value to different queues and WTD :
There is 2 input queues each with 2 different WTD threshold
Followinbg example maps dspc 00 and 01 to the queue 1 threshold 2 and configure for queue 1 and threshold 1 of 75 and threshold 2 of 50 and for queue 2 a threshold1 of 30 and a threshold 2 of 75
mls qos srr-queue input dscp-map queue 1 threshold 2 00 01
mls qos srr-queue input threshold 1 75 50
mls qos srr-queue input threshold 2 30 75
2 Configure the ingress bandwidth association to queues
Here 20 % is dedicated to Expedite queue 2, the remain bandwidth is shared between queue 1 35% and queue 2 45%
mls qos srr-queue input bandwidth 35 45
mls qos srr-queeu input priority 2 bandwidth 20
3 Modifiy default buffer
Buffer is the amount of packet each queue could contains before dropping
Input buffer is globally modified with :
mls qos srr-queue input buffer 60 40
Ouput is modified by Queue-set. Queue-set 1 is by default applied to all interfaces with egal shared. To apply a different queue-set to an interface :
mls qos queue-set output 2 buffers 40 20 20 20
int fa0/14
queue-set 2
4 Configure bandwidth shaping and sharing on interface
Shaped queue limit the bandwidth, whereas shared only limit during congestion.
Shape weight is an inverse ration 1/weight
Share weight is a ration weight_queue1/total_weight
0 in shape means queue is treated as shared. The remain bandwith is for shared.
A queue in shape mode is not take into account on the shared ratio.
Example Queue 1 is a shared queue with 12,5 percent of the bandwidh, the remaining bandwidth is shared among q2, q3, q4.
srr-queue bandwidth shape 8 0 0 0
srr-queue bandwidth share 25 25 25 25
lundi 12 octobre 2009
Private-VLAN
Differents vlan types :
- Promisicous/primary : a port/vlan that could communicate to all other private vlan associated with.
- Community : a port/vlan that could communicate with each other and with primary associated with.
- Isolated : a port/vlan that could communicate with primary associated with only.
A primary port can contains one isolted vlan and multiple communities vlan
Configuration
- Create the differents vlan
vlan 10
private-vlan primary
vlan 20
private-vlan community
vlan 30
private-vlan isolated
-Associate the vlan with a primary vlan
vlan 10
private-vlan association 10,20
Configure interface
On the following example,
- port 21 & 22 could communicate with each other and with port 1
- port 31 & 32 could not communicate with each other but could with port 1
- Port 1 could communicate with port 21,22,31,32
int f0/1
switchport mode private-vlan promiscious
switchport private-vlan mapping 10 add 20 30
int range f0/21-22
switchport mode private-vlan host
switchport private-vlan host-association 10 20
int range f0/31-32
switchport mode private-vlan host
switchport private-vlan host-association 10 30
- Promisicous/primary : a port/vlan that could communicate to all other private vlan associated with.
- Community : a port/vlan that could communicate with each other and with primary associated with.
- Isolated : a port/vlan that could communicate with primary associated with only.
A primary port can contains one isolted vlan and multiple communities vlan
Configuration
- Create the differents vlan
vlan 10
private-vlan primary
vlan 20
private-vlan community
vlan 30
private-vlan isolated
-Associate the vlan with a primary vlan
vlan 10
private-vlan association 10,20
Configure interface
On the following example,
- port 21 & 22 could communicate with each other and with port 1
- port 31 & 32 could not communicate with each other but could with port 1
- Port 1 could communicate with port 21,22,31,32
int f0/1
switchport mode private-vlan promiscious
switchport private-vlan mapping 10 add 20 30
int range f0/21-22
switchport mode private-vlan host
switchport private-vlan host-association 10 20
int range f0/31-32
switchport mode private-vlan host
switchport private-vlan host-association 10 30
vendredi 9 octobre 2009
Difference between BPDUGuard & BPDU Filtering
Thoses functions could be enabled globally for all PortFast ports :
span portfast bpdufilter default
span portfast bpduguard default
Or by interfaces.
The main difference is :
- Bpdu Guard will shutdown the port if a bpdu is received on a portfast port
- Bpdu filter will prevent inbound and outbound bpdu but will remove portfast state on a port if a bpdu is received.
span portfast bpdufilter default
span portfast bpduguard default
Or by interfaces.
The main difference is :
- Bpdu Guard will shutdown the port if a bpdu is received on a portfast port
- Bpdu filter will prevent inbound and outbound bpdu but will remove portfast state on a port if a bpdu is received.
jeudi 8 octobre 2009
Mac address Notification
The purpose is to notify a NMS of mac address changes :
Enable the TRAP :
snmp-server enable traps mac-notification
Enable the MAC notification globally :
mac address-table notification change
Enable the change on the port :
snmp trap mac-notification change [added | removed]
Limit the traps :
mac address-table notification interval seconds
mac address-table notification history-size messages
Verify :
show mac address-table notification change
Enable the TRAP :
snmp-server enable traps mac-notification
Enable the MAC notification globally :
mac address-table notification change
Enable the change on the port :
snmp trap mac-notification change [added | removed]
Limit the traps :
mac address-table notification interval seconds
mac address-table notification history-size messages
Verify :
show mac address-table notification change
Automatic IPv6 Tunnel
IPv6-IPv4 Compatible
Adress format : ::A.B.C.D/96
IPv4 Tunnel Source : IPv4 source interface
IPv4 Tunnel Destination : Deducted from the IPv6-Ipv4 compatible addess
IPv6 tunnel interface : Automatically generated from IPv4 Tunnel Source
Configuration
int tunnel 0
tunnel source int lo 0
tunnel mode ipv6ip auto-tunnel
6To4
Adress format : 2002:ipv4-border-router:/48
IPv4 Tunnel Source : IPv4 source interface
IPv4 Tunnel Destination : Deducted from the 6to4 addess
IPv6 tunnel interface : 2002:ipv4-border-router::/48
Configuration
int tunnel 0
tunnel source int lo 0
tunnel mode ipv6ip 6to4
ipv6 address 2002:ipv4-source-address::1/64
ipv6 router 2002::/16 tunnel 0
ISATAP
Adress format : ipv6-global-address:0000:5EFE:ipv4-border-router/128
IPv4 Tunnel Source : IPv4 source interface
IPv4 Tunnel Destination : Deducted from the ipv4 embedded address on ISATAP addess
IPv6 tunnel interface : Generated from the configured ipv6 prefix + ipv4-source-address
Configuration
int tunnel 0
tunnel source int lo 0
tunnel mode ipv6ip isatap
ipv6 address 2001:x:y::/64 eui-64
Adress format : ::A.B.C.D/96
IPv4 Tunnel Source : IPv4 source interface
IPv4 Tunnel Destination : Deducted from the IPv6-Ipv4 compatible addess
IPv6 tunnel interface : Automatically generated from IPv4 Tunnel Source
Configuration
int tunnel 0
tunnel source int lo 0
tunnel mode ipv6ip auto-tunnel
6To4
Adress format : 2002:ipv4-border-router:/48
IPv4 Tunnel Source : IPv4 source interface
IPv4 Tunnel Destination : Deducted from the 6to4 addess
IPv6 tunnel interface : 2002:ipv4-border-router::/48
Configuration
int tunnel 0
tunnel source int lo 0
tunnel mode ipv6ip 6to4
ipv6 address 2002:ipv4-source-address::1/64
ipv6 router 2002::/16 tunnel 0
ISATAP
Adress format : ipv6-global-address:0000:5EFE:ipv4-border-router/128
IPv4 Tunnel Source : IPv4 source interface
IPv4 Tunnel Destination : Deducted from the ipv4 embedded address on ISATAP addess
IPv6 tunnel interface : Generated from the configured ipv6 prefix + ipv4-source-address
Configuration
int tunnel 0
tunnel source int lo 0
tunnel mode ipv6ip isatap
ipv6 address 2001:x:y::/64 eui-64
Inscription à :
Articles (Atom)