Migration of Cisco CRS-1 to Huawei NE40E-X16 was performed few days ago & all goes well. After a day we received complaint about few sites from customer that they are not able to reach our backbone :(, while checking the related configuration for that customer, we notice that the Pseduowire is down, although we notice that vsi is down for that customer. migration was done on aggregator node. You can issue following command to see the status:
PE-AggX16-RegionName-2222-1 -- display vsi name Vlan8888 verbose
***VSI Name : Vlan8888
Administrator VSI : no
Isolate Spoken : disable
VSI Index : 28
PW Signaling : ldp
Member Discovery Style : static
PW MAC Learn Style : unqualify
Encapsulation Type : ethernet
MTU : 1500
VSI State : down
..................................................output Omitted
VSI ID : 8888
*Peer Router ID : 192.168.98.21
primary or secondary : primary
ignore-standby-state : no
VC Label : 5461
Peer Type : dynamic
State : down
.................................................output Omitted
**PW Information:
*Peer Ip Address : 192.168.98.21
PW State : down
Local VC Label : 5461
Remote VC Label : 28751
PW Type : label
.................................................output Omitted
After checking the configuration and logs we find out that at Agg-222, PW under VSI Vlan8888 was down. We found vsi id under vsi Vlan8888 was 8888 while at the peer Edge-333 that VSI ID was configured under different VSI. So we changed VSI-id at aggregator to 1880. At edge there was no vsi Vlan8888, so we create it & define same vsi-id under it whis is 1880.
Second, We also notice that Interface vlan 8888 was not bind to Vsi Vlan8888 at both Agg-222 and Edge-333, so we bind it to the interface vlan 8888 and then VSI came up.
Configuration done on both Aggreegator and Edge are:
Edge - 2222 Configuration:
==========================
vsi Vlan1058 static
pwsignal ldp
vsi-id 1880
peer 192.168.xx.xx
encapsulation ethernet
tnl-policy loadbalance
#
interface Vlanif8888
l2 binding vsi Vlan8888
#
Agg-2222 Configuration:
=======================
vsi Vlan1058 static
pwsignal ldp
vsi-id 1880
peer 192.168.xx.xx
encapsulation ethernet
tnl-policy loadbalance
#
interface Vlanif8888
l2 binding vsi Vlan8888
Verification:
PE-AggX16-RegionName-2222-1 -- dis vsi name Vlan8888
Vsi Mem PW Mac Encap Mtu Vsi
Name Disc Type Learn Type Value State
--------------------------------------------------------------------------
Vlan1058 static ldp unqualify ethernet 1500 up
PE-AggX16-RegionName-2222-1 -- display vsi name Vlan8888 verbose
***VSI Name : Vlan8888
Administrator VSI : no
Isolate Spoken : disable
VSI Index : 28
PW Signaling : ldp
Member Discovery Style : static
PW MAC Learn Style : unqualify
Encapsulation Type : ethernet
MTU : 1500
Diffserv Mode : uniform
Service Class : --
Color : --
DomainId : 255
Domain Name :
Tunnel Policy Name : loadbalance
Ignore AcState : disable
P2P VSI : disable
Create Time : 0 days, 0 hours, 26 minutes, 18 seconds
VSI State : up
VSI ID : 1880
*Peer Router ID : 192.168.xx.xx
primary or secondary : primary
ignore-standby-state : no
VC Label : 5461
Peer Type : dynamic
Session : up
Tunnel ID : 0x60036ed9
Broadcast Tunnel ID : 0x60036ed9
Broad BackupTunnel ID : 0x0
CKey : 69
NKey : 66
StpEnable : 0
PwIndex : 0
Interface Name : Vlanif8888
State : up
Access Port : false
Last Up Time : 2012/06/26 21:04:41
Total Up Time : 0 days, 0 hours, 10 minutes, 33 seconds
**PW Information:
*Peer Ip Address : 192.168.xx.xx
PW State : up
Local VC Label : 5461
Remote VC Label : 28751
PW Type : label
Tunnel ID : 0x60036ed9
Broadcast Tunnel ID : 0x60036ed9
Broad BackupTunnel ID : 0x0
Ckey : 0x45
Nkey : 0x42
Main PW Token : 0x40007e66
Slave PW Token : 0x40007e67
Tnl Type : LSP
OutInterface : Tunnel0/0/3000
Backup OutInterface :
Stp Enable : 0
Mac Flapping : 0
PW Last Up Time : 2012/06/26 21:04:41
PW Total Up Time : 0 days, 0 hours, 10 minutes, 33 seconds
I Hope this will be informative for you !
Saturday, June 30, 2012
Thursday, June 21, 2012
Multiprotocol Label Switching (MPLS) VPN
Yes Guys & Girls! Waiting for detail step wise configuration of Multiprotocol Label Switching Virtual Private Network (MPLS-VPN).
R1(config) # ip cef
R1(config) # mpls ldp router-id loopback 0
R1(config) # mpls label protocol ldp
R1(config) # mpls ip
Repeat same commands on router R2 & R3
We can divide the configuration phase into four steps:
1 - VRP related Configuration
2 - MP-BGP Related Configuration
3 - PE-CE Routing Protocol Configuration
4 - Redistribution
Step # 1 VRF Configuration
R1(config)# ip vrf test
R1(config-vrf)# rd 1:1
R1(config-vrf)# route-target 1:1
By using above command for RT it is defined automatically for both
importa and export, if you want to use seperate you can do so. Use
R1 # show running-config command to see that both import and export
RT is defined using above command.
R1(config)# interface serial 1/1
R1(config-if)# ip vrf forwarding test
./. You will get Warning that IP Address 5.1.1.2 is removed due to
vrf configuration. Assign IP Address again.
R1(config)# interface serial 1/1
R1(config-if)# ip address 5.1.1.1 255.0.0.0
Note: Now when you check your routing table you will not see 5.0.0.0 network as it is removed and move to vrf table. you can confirm it using below command:
R1 # show ip route vrf test
R1 # ping vrf test 5.1.1.1
The result should be sucessfull :)
R3(config)# ip vrf test //The vrf name here can be differnt.
R3(config-vrf)# rd 1:1
R3(config-vrf)# route-target 1:1
R3(config)# interface serial 1/0
R3(config-if)# ip vrf forwarding test
./. You will get Warning that IP Address 5.1.1.2 is removed due to
vrf configuration. Assign IP Address again.
R3(config)# interface serial 1/0
R3(config-if)# ip address 3.1.1.1 255.0.0.0
Step # 2 MP-BGP Configuration
R1(config)# router bgp 1
R1(config-router)# bgp router-id 11.1.1.1
R1(config-router)# bgp auto-summary
R1(config-router)# no synchronization
R1(config-router)# neighbor 33.3.3.3 remote-as 1
R1(config-router)# neighbor 33.3.3.3 update-source loopback 0
R3(config-router)# router bgp 1
R3(config-router)# bgp router-id 33.3.3.3
R3(config-router)# bgp auto-summary
R3(config-router)# no synchronization
R3(config-router)# neighbor 11.1.1.1 remote-as 1
R3(config-router)# neighbor 11.1.1.1 update-source loopback 0
The above is basic BGP configuration. Now MP-BGP configuraiton (We used Multi-Protocol BGP (MP-BGP) because we need this to carry VPNv4, VPNv6, IPv6 & IPv4 Packets while BGP only carry IPv4 traffic.
R1(config) # router bgp 1
R1(config-router) # address-family vpnv4
R1(config-router-af) # neighbor 33.3.3.3 activate
R1(config-router-af) # neighbor 33.3.3.3 send-community both
R3(config) # router bgp 1
R3(config-router) # address-family vpnv4
R3(config-router-af) # neighbor 11.1.1.1 activate
R3(config-router-af) # neighbor 11.1.1.1 send-community both
Step # 3 PE-CE Configuration
Run OSPF between PE & CE but make sure to use different process-id from one which is already running on PE as you all routes will be in service provider area.
R1(config)# router ospf 10 vrf test
R1(config-vrf)# router-id 5.1.1.2
R1(config-vrf)# network 5.0.0.0 0.255.255.255 area 0
Note: We used different id other than loopback as that is already use by OSPF-1.
R5(config)# router ospf 1
R5(config-router)# router-id 55.5.5.5
R5(config-router)# network 55.5.5.5 0.0.0.0 area 0
R5(config-router)# network 50.1.1.1 0.0.0.0 area 0
R5(config-router)# network 5.1.1.1 0.0.0.0 area 0
R1# show ip route vrf test
R3(config)# router ospf 10 vrf test
R3(config-vrf)# router-id 3.1.1.1
R3(config-vrf)# network 3.0.0.0 0.255.255.255 area 0
R7(config)# router ospf 1
R7(config-router)# router-id 77.7.7.7
R7(config-router)# network 77.7.7.7 0.0.0.0 area 0
R7(config-router)# network 70.1.1.1 0.0.0.0 area 0
R3# show ip route vrf test
R3# ping 11.1.1.1
Step # 4 Redistribution
On R1, Routes which are learned via OSPF are now redistributed into BGP which is run in the MPLS domain.
R1(config)# router bgp 1
R1(config-router)# address-family ipv4 vrf test
R1(config-router)# redistribute ospf 10 match internal external
R3# show ip route vrf test
Now redistribute BGP into OSPF as routes reached to R3 but not R7 as on R7 we have OSPF, so redistribute BGP into OSPF.
R3(config)# router ospf 10
R3(config-router)# redistribute bgp 1 subnets
Now do the redistribution in reverse direction. Redistribute OSPF into BGP.
R3(config)# router bgp 1
R3(config-router)# address-family ipv4 vrf test
R3(config)# redistribute ospf 10 match internal external
R1(config)# router ospf 10
R1(config-router)#redistribute bgp 1 subnets
Verifications:
R5# ping 77.7.7.7
R5# traceroute 77.7.7.7
I hope this will be informative for you :)
R1(config) # ip cef
R1(config) # mpls ldp router-id loopback 0
R1(config) # mpls label protocol ldp
R1(config) # mpls ip
Repeat same commands on router R2 & R3
We can divide the configuration phase into four steps:
1 - VRP related Configuration
2 - MP-BGP Related Configuration
3 - PE-CE Routing Protocol Configuration
4 - Redistribution
Step # 1 VRF Configuration
R1(config)# ip vrf test
R1(config-vrf)# rd 1:1
R1(config-vrf)# route-target 1:1
By using above command for RT it is defined automatically for both
importa and export, if you want to use seperate you can do so. Use
R1 # show running-config command to see that both import and export
RT is defined using above command.
R1(config)# interface serial 1/1
R1(config-if)# ip vrf forwarding test
./. You will get Warning that IP Address 5.1.1.2 is removed due to
vrf configuration. Assign IP Address again.
R1(config)# interface serial 1/1
R1(config-if)# ip address 5.1.1.1 255.0.0.0
Note: Now when you check your routing table you will not see 5.0.0.0 network as it is removed and move to vrf table. you can confirm it using below command:
R1 # show ip route vrf test
R1 # ping vrf test 5.1.1.1
The result should be sucessfull :)
R3(config)# ip vrf test //The vrf name here can be differnt.
R3(config-vrf)# rd 1:1
R3(config-vrf)# route-target 1:1
R3(config)# interface serial 1/0
R3(config-if)# ip vrf forwarding test
./. You will get Warning that IP Address 5.1.1.2 is removed due to
vrf configuration. Assign IP Address again.
R3(config)# interface serial 1/0
R3(config-if)# ip address 3.1.1.1 255.0.0.0
Step # 2 MP-BGP Configuration
R1(config)# router bgp 1
R1(config-router)# bgp router-id 11.1.1.1
R1(config-router)# bgp auto-summary
R1(config-router)# no synchronization
R1(config-router)# neighbor 33.3.3.3 remote-as 1
R1(config-router)# neighbor 33.3.3.3 update-source loopback 0
R3(config-router)# router bgp 1
R3(config-router)# bgp router-id 33.3.3.3
R3(config-router)# bgp auto-summary
R3(config-router)# no synchronization
R3(config-router)# neighbor 11.1.1.1 remote-as 1
R3(config-router)# neighbor 11.1.1.1 update-source loopback 0
The above is basic BGP configuration. Now MP-BGP configuraiton (We used Multi-Protocol BGP (MP-BGP) because we need this to carry VPNv4, VPNv6, IPv6 & IPv4 Packets while BGP only carry IPv4 traffic.
R1(config) # router bgp 1
R1(config-router) # address-family vpnv4
R1(config-router-af) # neighbor 33.3.3.3 activate
R1(config-router-af) # neighbor 33.3.3.3 send-community both
R3(config) # router bgp 1
R3(config-router) # address-family vpnv4
R3(config-router-af) # neighbor 11.1.1.1 activate
R3(config-router-af) # neighbor 11.1.1.1 send-community both
Step # 3 PE-CE Configuration
Run OSPF between PE & CE but make sure to use different process-id from one which is already running on PE as you all routes will be in service provider area.
R1(config)# router ospf 10 vrf test
R1(config-vrf)# router-id 5.1.1.2
R1(config-vrf)# network 5.0.0.0 0.255.255.255 area 0
Note: We used different id other than loopback as that is already use by OSPF-1.
R5(config)# router ospf 1
R5(config-router)# router-id 55.5.5.5
R5(config-router)# network 55.5.5.5 0.0.0.0 area 0
R5(config-router)# network 50.1.1.1 0.0.0.0 area 0
R5(config-router)# network 5.1.1.1 0.0.0.0 area 0
R1# show ip route vrf test
R3(config)# router ospf 10 vrf test
R3(config-vrf)# router-id 3.1.1.1
R3(config-vrf)# network 3.0.0.0 0.255.255.255 area 0
R7(config)# router ospf 1
R7(config-router)# router-id 77.7.7.7
R7(config-router)# network 77.7.7.7 0.0.0.0 area 0
R7(config-router)# network 70.1.1.1 0.0.0.0 area 0
R3# show ip route vrf test
R3# ping 11.1.1.1
Step # 4 Redistribution
On R1, Routes which are learned via OSPF are now redistributed into BGP which is run in the MPLS domain.
R1(config)# router bgp 1
R1(config-router)# address-family ipv4 vrf test
R1(config-router)# redistribute ospf 10 match internal external
R3# show ip route vrf test
Now redistribute BGP into OSPF as routes reached to R3 but not R7 as on R7 we have OSPF, so redistribute BGP into OSPF.
R3(config)# router ospf 10
R3(config-router)# redistribute bgp 1 subnets
Now do the redistribution in reverse direction. Redistribute OSPF into BGP.
R3(config)# router bgp 1
R3(config-router)# address-family ipv4 vrf test
R3(config)# redistribute ospf 10 match internal external
R1(config)# router ospf 10
R1(config-router)#redistribute bgp 1 subnets
Verifications:
R5# ping 77.7.7.7
R5# traceroute 77.7.7.7
I hope this will be informative for you :)
Saturday, June 16, 2012
MPLS Traffic Engineering:: Part – 1 :: Theory
Whenever data is moved and we want the data not to follow the routing protocol dedicated path but to redirect to the path which we select for the traffic to follow. When we determined the path for traffic or data to follow so there are some concept on which Multiprotocol Label Switching - Traffic Engineering (MPLS-TE) is based:
When Routing Protocol is configured on a node it results about the interface parameters like Bandwidth information:
1. MPLS-TE also gives us some information like Bandwidth of the link, how much bandwidth is left (remaining) or Bandwidth is available. Basically it gives the link properties (all these are link constraints).
2. Protocol is needed which carry information and these information are carried by Link State Protocol either OSPF or IS-IS.
3. Constraint based SPF or Path Calculation algorithm is needed for the determination of best path to various routes. This CBSPF use many constraints for path selection other than bandwidth.
4. We have to make sure that the connectivity is available on that path which is selected for traffic. Resource Reservation Protocol (RSVP) is used to reserve bandwidth on the path. For example, we need 10 Mbps on a link, so RSVP ensures this much of bandwidth & RSVP also do the label, changing end-to-end changing (information).
Path Message: Which ensure Bandwidth?
Reserve Message: Confirmation of Bandwidth
In TE, the tunnel headed router decided which path the traffic should follow
a: The LSP Path/Tunnel is one way
b: TE Tunnel configuration is done on Head router, that’s why one way
c: We can use RSVP and LDP parallel like some traffic will pass through tunnel which will use Tunnel Label while some traffic will pass out of Tunnel which will use LDP Label.
d: We can have multiple Tunnels so we can have more than one label.
e: In MPLS TE we basically decided: How to allow the traffic in tunnel means How to route the traffic to the tunnel? & How to feed the traffic in Tunnel?
f: In TE we basically engineer, Like we select another path other than the path which is selected by routing protocols. Routing protocols select best path using only metric which TE use many other parameters for it.
I hope this will be informative for you !
Cheers :)
When Routing Protocol is configured on a node it results about the interface parameters like Bandwidth information:
1. MPLS-TE also gives us some information like Bandwidth of the link, how much bandwidth is left (remaining) or Bandwidth is available. Basically it gives the link properties (all these are link constraints).
2. Protocol is needed which carry information and these information are carried by Link State Protocol either OSPF or IS-IS.
3. Constraint based SPF or Path Calculation algorithm is needed for the determination of best path to various routes. This CBSPF use many constraints for path selection other than bandwidth.
4. We have to make sure that the connectivity is available on that path which is selected for traffic. Resource Reservation Protocol (RSVP) is used to reserve bandwidth on the path. For example, we need 10 Mbps on a link, so RSVP ensures this much of bandwidth & RSVP also do the label, changing end-to-end changing (information).
Path Message: Which ensure Bandwidth?
Reserve Message: Confirmation of Bandwidth
In TE, the tunnel headed router decided which path the traffic should follow
a: The LSP Path/Tunnel is one way
b: TE Tunnel configuration is done on Head router, that’s why one way
c: We can use RSVP and LDP parallel like some traffic will pass through tunnel which will use Tunnel Label while some traffic will pass out of Tunnel which will use LDP Label.
d: We can have multiple Tunnels so we can have more than one label.
e: In MPLS TE we basically decided: How to allow the traffic in tunnel means How to route the traffic to the tunnel? & How to feed the traffic in Tunnel?
f: In TE we basically engineer, Like we select another path other than the path which is selected by routing protocols. Routing protocols select best path using only metric which TE use many other parameters for it.
I hope this will be informative for you !
Cheers :)
Interfac GigabitEthernet 2/9/1 :: Received Pause Frames Exceeded Threshold
At time something is not that big thing but live network is live which makes you so careful and conscious that you take care of each and every alarms of Router (NE40E). I saw the above alarms on my NE40E, when I try to troubleshoot so it was not that big problem. At time due to this may be some data services lost on that interface. You can get this due to some reasons which include “The receiving rate of pause frames exceeded the threshold” or it is receiving for continuous time.
Solution:
You just need to check the rate on the interface; if you see this alarm what you need is to reduce the traffic rate from neighbor node. In my case when I notice this so no high rate was noticed on the interface, it just appear for a while and then disappear.
I hope this will be informative for you.
Solution:
You just need to check the rate on the interface; if you see this alarm what you need is to reduce the traffic rate from neighbor node. In my case when I notice this so no high rate was noticed on the interface, it just appear for a while and then disappear.
I hope this will be informative for you.
Subscribe to:
Posts (Atom)