[c-nsp] 6500 mGRE/DMVPN on VSS
Hi, Wondering if anyone has done mGRE/DMVPN on VSS switches. I am thinking of a solution with VSS at the access with Layer 3 and mGRE (30+) and VSS at Distribution/Core. When multiple mGREs are required, tunnel keys must be used to differntitate between the tunnels, with the same source interface for all tunnels. But, the GREs will be done in software when tunnel keys are used in 6500 and I do not want to do this. Can someone sugegst any alternatives to mGRE/DMVPN? I know it is hard to sugegst something without more details/information. Thanks in advance, Shine ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] mGRE with VRF-Lite
- Original Message - From: Brad Holding To: Shine Joseph Sent: Tuesday, October 13, 2009 9:33 AM Subject: Re: [c-nsp] mGRE with VRF-Lite So when you added the 'ip nhrp map multicast 172.16.123.xxx' under the tunnel the EIGRP neighbours would just flap? On Tue, Oct 13, 2009 at 4:55 AM, Shine Joseph shinejos...@dodo.com.au wrote: Hi, Thanks for your responses and pointers. the vrf names in the tunnel and routing process is just an editing error. I can't get the multicasting working for the mGRE, it works well for the p2p GRE. When multicasting is used for EIGRP, the neibghors come up, but flaps and no routes are being exchanged. The Q counter is not zero. The only way, I got the mGRE worked is using neighbor statements in the routing process. See below my working config for two VRFs. Let me know if you have any further thoughts on this. Thanks Shine Router 1 = ip vrf data rd 100:110 ! ip vrf voice rd 100:111 ! interface Tunnel110 ip vrf forwarding data ip address 10.40.60.1 255.255.255.0 no ip redirects ip nhrp map 10.40.60.2 172.16.123.2 ip nhrp map 10.40.60.3 172.16.123.3 ip nhrp network-id 110 tunnel source GigabitEthernet0/1 tunnel mode gre multipoint tunnel key 110 ! interface Tunnel111 ip vrf forwarding voice ip address 10.40.61.1 255.255.255.0 no ip redirects ip nhrp map 10.40.61.2 172.16.123.2 ip nhrp map 10.40.61.3 172.16.123.3 ip nhrp network-id 111 tunnel source GigabitEthernet0/1 tunnel mode gre multipoint tunnel key 111 ! router eigrp 100 no auto-summary ! address-family ipv4 vrf voice network 10.40.61.1 0.0.0.0 no auto-summary autonomous-system 100 neighbor 10.40.61.2 Tunnel111 neighbor 10.40.61.3 Tunnel111 exit-address-family ! address-family ipv4 vrf data network 1.1.1.1 0.0.0.0 network 10.40.60.1 0.0.0.0 no auto-summary autonomous-system 100 neighbor 10.40.60.3 Tunnel110 neighbor 10.40.60.2 Tunnel110 exit-address-family ! Router 2 = ip vrf data rd 100:110 ! ip vrf voice rd 100:111 ! interface Tunnel110 ip vrf forwarding data ip address 10.40.60.2 255.255.255.0 no ip redirects ip nhrp map 10.40.60.1 172.16.123.1 ip nhrp network-id 110 tunnel source GigabitEthernet0/1 tunnel mode gre multipoint tunnel key 110 ! interface Tunnel111 ip vrf forwarding voice ip address 10.40.61.2 255.255.255.0 no ip redirects ip nhrp map 10.40.61.1 172.16.123.1 ip nhrp network-id 111 tunnel source GigabitEthernet0/1 tunnel mode gre multipoint tunnel key 111 ! router eigrp 100 no auto-summary ! address-family ipv4 vrf voice network 2.2.2.2 0.0.0.0 network 10.40.61.2 0.0.0.0 no auto-summary autonomous-system 100 neighbor 10.40.61.1 Tunnel111 exit-address-family ! address-family ipv4 vrf data network 10.40.60.2 0.0.0.0 no auto-summary autonomous-system 100 neighbor 10.40.60.1 Tunnel110 exit-address-family Router 3 = ip vrf data rd 100:110 ! ip vrf voice rd 100:111 ! interface Tunnel110 ip vrf forwarding data ip address 10.40.60.3 255.255.255.0 no ip redirects ip nhrp map 10.40.60.1 172.16.123.1 ip nhrp network-id 110 ip nhrp cache non-authoritative tunnel source GigabitEthernet0/1 tunnel mode gre multipoint tunnel key 110 ! interface Tunnel111 ip vrf forwarding voice ip address 10.40.61.3 255.255.255.0 no ip redirects ip nhrp map 10.40.61.1 172.16.123.1 ip nhrp network-id 111 ip nhrp cache non-authoritative tunnel source GigabitEthernet0/1 tunnel mode gre multipoint tunnel key 111 ! router eigrp 100 no auto-summary ! address-family ipv4 vrf voice network 10.40.61.3 0.0.0.0 no auto-summary autonomous-system 100 neighbor 10.40.61.1 Tunnel111 exit-address-family ! address-family ipv4 vrf data network 10.40.60.3 0.0.0.0 no auto-summary autonomous-system 100 neighbor 10.40.60.1 Tunnel110 exit-address-family ! - Original Message - From: Brad Holding To: shinejos...@dodo.com.au Sent: Monday, October 12, 2009 1:19 PM Subject: Fwd: [c-nsp] mGRE with VRF-Lite Also, the VRF names under the interfaces and the routing processes are not the same. ie. interface Tunnel110 ip vrf forwarding Data router eigrp 100
Re: [c-nsp] mGRE with VRF-Lite
Hi, That's correct. The neighbors come up, flaps. Also, they did not any exchange any routes. - Original Message - From: Brad Holding To: Shine Joseph Sent: Tuesday, October 13, 2009 9:33 AM Subject: Re: [c-nsp] mGRE with VRF-Lite So when you added the 'ip nhrp map multicast 172.16.123.xxx' under the tunnel the EIGRP neighbours would just flap? On Tue, Oct 13, 2009 at 4:55 AM, Shine Joseph shinejos...@dodo.com.au wrote: Hi, Thanks for your responses and pointers. the vrf names in the tunnel and routing process is just an editing error. I can't get the multicasting working for the mGRE, it works well for the p2p GRE. When multicasting is used for EIGRP, the neibghors come up, but flaps and no routes are being exchanged. The Q counter is not zero. The only way, I got the mGRE worked is using neighbor statements in the routing process. See below my working config for two VRFs. Let me know if you have any further thoughts on this. Thanks Shine Router 1 = ip vrf data rd 100:110 ! ip vrf voice rd 100:111 ! interface Tunnel110 ip vrf forwarding data ip address 10.40.60.1 255.255.255.0 no ip redirects ip nhrp map 10.40.60.2 172.16.123.2 ip nhrp map 10.40.60.3 172.16.123.3 ip nhrp network-id 110 tunnel source GigabitEthernet0/1 tunnel mode gre multipoint tunnel key 110 ! interface Tunnel111 ip vrf forwarding voice ip address 10.40.61.1 255.255.255.0 no ip redirects ip nhrp map 10.40.61.2 172.16.123.2 ip nhrp map 10.40.61.3 172.16.123.3 ip nhrp network-id 111 tunnel source GigabitEthernet0/1 tunnel mode gre multipoint tunnel key 111 ! router eigrp 100 no auto-summary ! address-family ipv4 vrf voice network 10.40.61.1 0.0.0.0 no auto-summary autonomous-system 100 neighbor 10.40.61.2 Tunnel111 neighbor 10.40.61.3 Tunnel111 exit-address-family ! address-family ipv4 vrf data network 1.1.1.1 0.0.0.0 network 10.40.60.1 0.0.0.0 no auto-summary autonomous-system 100 neighbor 10.40.60.3 Tunnel110 neighbor 10.40.60.2 Tunnel110 exit-address-family ! Router 2 = ip vrf data rd 100:110 ! ip vrf voice rd 100:111 ! interface Tunnel110 ip vrf forwarding data ip address 10.40.60.2 255.255.255.0 no ip redirects ip nhrp map 10.40.60.1 172.16.123.1 ip nhrp network-id 110 tunnel source GigabitEthernet0/1 tunnel mode gre multipoint tunnel key 110 ! interface Tunnel111 ip vrf forwarding voice ip address 10.40.61.2 255.255.255.0 no ip redirects ip nhrp map 10.40.61.1 172.16.123.1 ip nhrp network-id 111 tunnel source GigabitEthernet0/1 tunnel mode gre multipoint tunnel key 111 ! router eigrp 100 no auto-summary ! address-family ipv4 vrf voice network 2.2.2.2 0.0.0.0 network 10.40.61.2 0.0.0.0 no auto-summary autonomous-system 100 neighbor 10.40.61.1 Tunnel111 exit-address-family ! address-family ipv4 vrf data network 10.40.60.2 0.0.0.0 no auto-summary autonomous-system 100 neighbor 10.40.60.1 Tunnel110 exit-address-family Router 3 = ip vrf data rd 100:110 ! ip vrf voice rd 100:111 ! interface Tunnel110 ip vrf forwarding data ip address 10.40.60.3 255.255.255.0 no ip redirects ip nhrp map 10.40.60.1 172.16.123.1 ip nhrp network-id 110 ip nhrp cache non-authoritative tunnel source GigabitEthernet0/1 tunnel mode gre multipoint tunnel key 110 ! interface Tunnel111 ip vrf forwarding voice ip address 10.40.61.3 255.255.255.0 no ip redirects ip nhrp map 10.40.61.1 172.16.123.1 ip nhrp network-id 111 ip nhrp cache non-authoritative tunnel source GigabitEthernet0/1 tunnel mode gre multipoint tunnel key 111 ! router eigrp 100 no auto-summary ! address-family ipv4 vrf voice network 10.40.61.3 0.0.0.0 no auto-summary autonomous-system 100 neighbor 10.40.61.1 Tunnel111 exit-address-family ! address-family ipv4 vrf data network 10.40.60.3 0.0.0.0 no auto-summary autonomous-system 100 neighbor 10.40.60.1 Tunnel110 exit-address-family ! - Original Message - From: Brad Holding To: shinejos...@dodo.com.au Sent: Monday, October 12, 2009 1:19 PM Subject: Fwd: [c-nsp] mGRE with VRF-Lite Also, the VRF names under the interfaces and the routing processes
[c-nsp] mGRE with VRF-Lite
Hi, I am working on a solution to run mGRE for VRF-Lite. This is my situation: there are 5 sites currently connected by MPLS IPWAn provided by ISP. I want to run VRF-Lite throughout the network for path isolation between various VLANs. VRF-Lite works great within the site (Vrf-Lite end-to-end is being deployed). In order for to cross the IPWAN, mutipoint-GRE tunnels are being looked at. tunnels are getting created, but when advertised in the VRF routing process, neighbor is not being esablished. If I use the potint to point tunnel, neighbor relationship is estanblished, working as expected. The issue will be I need to create over 50 tunnels to achieve the expected results. Can someone help me, if the mGRE with VRF-Lite is a feasible solution? Thanks in advance Shine Following is a snippet of my configuration: Router 1 interface Tunnel110 ip vrf forwarding Data ip address 10.40.61.1 255.255.255.224 no ip redirects ip nhrp map 10.40.61.2 172.16.123.2 ip nhrp map 10.40.61.3 172.16.123.3 ip nhrp network-id 110 ip nhrp cache non-authoritative tunnel source GigabitEthernet0/1 tunnel mode gre multipoint tunnel key 110 router eigrp 100 no auto-summary ! address-family ipv4 vrf Gorgon_Data network 10.40.61.1 0.0.0.0 no auto-summary autonomous-system 100 exit-address-family ! Router 2 interface Tunnel110 ip vrf forwarding Data ip address 10.40.61.2 255.255.255.224 no ip redirects ip nhrp map 10.40.61.1 172.16.123.1 ip nhrp map 10.40.61.3 172.16.123.3 ip nhrp network-id 110 ip nhrp cache non-authoritative tunnel source GigabitEthernet0/1 tunnel mode gre multipoint tunnel key 110 router eigrp 100 no auto-summary ! address-family ipv4 vrf Gorgon_Data network 10.40.61.2 0.0.0.0 no auto-summary autonomous-system 100 exit-address-family ! Router 3 interface Tunnel110 ip vrf forwarding Data ip address 10.40.61.3 255.255.255.224 no ip redirects ip nhrp map 10.40.61.1 172.16.123.1 ip nhrp map 10.40.61.2 172.16.123.2 ip nhrp network-id 110 ip nhrp cache non-authoritative tunnel source GigabitEthernet0/1 tunnel mode gre multipoint tunnel key 110 router eigrp 100 no auto-summary ! address-family ipv4 vrf Gorgon_Data network 10.40.61.3 0.0.0.0 no auto-summary autonomous-system 100 exit-address-family ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] Wireless LAN controller 5508 on VSS
Hi, Can someone guide me if I can use WLC 5508's all the the 8 ports connected to a VSS with 4 links to each chassis? The reason I am asking this question is; in the documentation of VSS it says, not to turn off LACP or PAgP for creating MEC. But, for WLC LAG, the portchannel negtiation must be turned off. Any pointers are welcome. TIA Shine ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] Maximum spannig tree instances
Hi, I searched in the archives if I could find the answer to my this query. = The result was negative. How many spanning-tree instances are possible in Rapid PVST+ and MST = modes in Cisco 6500 series switches with Sup720? The only documentation that I could see which says about total number of = virtual ports per line card and total active logical ports. There is no = reference to number of instances. The following netpro link mentions about 4096 instances, but this point = is not validated. http://forums.cisco.com/eforum/servlet/NetProf?page=3Dnetprofforum=3DNet= work%20Infrastructuretopic=3DLAN%2C%20Switching%20and%20RoutingtopicID=3D= .ee71a04CommCmd=3DMB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40= %40.2cc1484e/2#selected_message Any links or pointers would be much appreciated. Thanks in advance, Shine ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] Fw: Data Centre Best pratices
Would anyone like to have a stab at this Hi, I am at the beginning of building a best practices document for data centre design. I am wondering if anyone can poiunt me to the right document that I can start with. I am looking at a Cisco centric solution. Following documents are currently being looked at. http://www.cisco.com/en/US/docs/solutions/Enterprise/Data_Center/DC_Infra2_5/DCI_SRND_2_5_book.html http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/prod_white_paper0900aecd804be7e2_ps2706_Products_White_Paper.html Any pointers and help would be highly appreciated. Thanks in advance. Shine ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] Data Centre Best pratices
Hi, I am at the beginning of building a best practices document for data centre design. I am wondering if anyone can poiunt me to the right document that I can start with. I am looking at a Cisco centric solution. Following documents are currently being looked at. http://www.cisco.com/en/US/docs/solutions/Enterprise/Data_Center/DC_Infra2_5/DCI_SRND_2_5_book.html http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/prod_white_paper0900aecd804be7e2_ps2706_Products_White_Paper.html Any pointers and help would be highly appreciated. Thanks in advance. Shine ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] ME6524 MPLS QoS
Hi, ME6524 is used as the PE devices in my topology. The P devices (6506) are in a remote locations and hence the link between PE and P are limited to 30Mbps. As the traffic enters the network, I can mark them with EXP bits, but I haven't found a way on ME6524 to prioritise the traffic as it leaves towards the P. Have anyone successfully deployed MPLS QoS on ME6524s? All pointers and suggestions welcome. Thanks in advance. Shine ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] MPLS QoS
Thanks guys. Much apprecitaed. Shine - Original Message - From: Johannes Resch j...@xor.at To: Shine Joseph shinejos...@dodo.com.au Cc: cisco-nsp@puck.nether.net Sent: Tuesday, June 23, 2009 2:23 PM Subject: Re: [c-nsp] MPLS QoS On Tue, June 23, 2009 05:12, Shine Joseph wrote: Hi, Can anyone with SP experience state why would one choose pipe model over short pipe model or vice versa for deploying MPLS QoS? With full pipe you get some nice benefits like the ability to classify all user traffic only based on MPLS EXP (since traffic will always be transported labelled only), and giving your end customers the option to transport their customer-set DSCP value transparently through your network. (you can fully decouple your core QoS handling from customer-set DSCP values). However, there are also a few issues here: Full pipe model requires ultimate hop popping, which has a performance penalty on many platforms. (e.g., on 7600 with SUP720/RSP720 it forces a recirculation of the traffic on the egress PE, effectively halving the PPS rate of the box). On that platform, supposedly EARL8 will have the HW capabilities of doing a label pop operation plus IP lookup at the same time without recirculation. Also, be sure to test HW platforms you are using well before making this decision. We found quite a few nasty bugs related to UHP on multiple vendors' products in the process, which lead me to think that UHP is not really commonly used (yet). One example - due to a HW bug on 6500/7600 3B/3BXL cards, full pipe mode does not work at all on any 6500/7600 chassis if it is in 3B/3BXL mode (if activated regardless, it leads to wrong imposed EXP values for traffic IP-MPLS). This has been fixed in 3C/3CXL HW. HTH, -jr ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] MPLS QoS
Hi, Can anyone with SP experience state why would one choose pipe model over short pipe model or vice versa for deploying MPLS QoS? I have been searching the cisco site and other places a for a while to get an answer. Any pointers suggests welcome. Thanks in advance, Shine ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] WLC discovery
Hi, A Cisco WLC4402 is configured and working alright. All of the APs currently are in the same subnet and hence the discovery do not require DHCP Option 43 or DNS. I want to add another AP that is in a different. When the AP tries to register with the WLC, it registers momentarily and un registers. This has happened for eithe DHCP option and DNS discovery. I am sure, there is something I have not done to get this working. Can anyone suggest somthing that I should try? Thanks in advance, Shine ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] WLC discovery
Thanks Mike for the the quick response. That means I have to have physical access to the APs which are already mounted on the ceiling. I am in the process of moving this AP to another subnet and I have some 18 of them to be moved from a single subnet to different subnets. I can see this AP regsiters momentarily and de-registers. We are running code 5.1. When the AP regsiters I can go to its configuration page and I see Hardware reset and Reset to Factory defaults. Any help is appreciated. Thanks, Shine - Original Message - From: Kaegler, Mike kaegl...@tessco.com To: Shine Joseph shinejos...@dodo.com.au; cisco-nsp@puck.nether.net Sent: Thursday, June 11, 2009 4:50 AM Subject: Re: [c-nsp] WLC discovery Boot the AP with the Mode button down to reset its parameter memory. If that doesn't help, hook into console and watch the messages. If that doesn't help, execute some 'debug [...]' statements on the same console. -porkchop On 6/10/09 4:42 PM, Shine Joseph shinejos...@dodo.com.au wrote: Hi, A Cisco WLC4402 is configured and working alright. All of the APs currently are in the same subnet and hence the discovery do not require DHCP Option 43 or DNS. I want to add another AP that is in a different. When the AP tries to register with the WLC, it registers momentarily and un registers. This has happened for eithe DHCP option and DNS discovery. I am sure, there is something I have not done to get this working. Can anyone suggest somthing that I should try? Thanks in advance, Shine ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ -- Michael Kaegler, TESSCO Technologies: Engineering, 410 229 1295 Your wireless success, nothing less. http://www.tessco.com/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] WLC discovery
Hi, There is only one controller and I believe this is the master controller. DO you know, where I could check this? Thanks, Shine - Original Message - From: a.l.m.bu...@lboro.ac.uk To: Shine Joseph shinejos...@dodo.com.au Cc: cisco-nsp@puck.nether.net Sent: Thursday, June 11, 2009 5:11 AM Subject: Re: [c-nsp] WLC discovery Hi, Hi, A Cisco WLC4402 is configured and working alright. All of the APs currently are in the same subnet and hence the discovery do not require DHCP Option 43 or DNS. I want to add another AP that is in a different. When the AP tries to register with the WLC, it registers momentarily and un registers. This has happened for eithe DHCP option and DNS discovery. I am sure, there is something I have not done to get this working. Can anyone suggest somthing that I should try? is master controller mode turned on? alan ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] WLC discovery
Yes it is in layer 3 mode - Original Message - From: Ryan West rw...@zyedge.com To: Shine Joseph shinejos...@dodo.com.au Cc: Kaegler, Mike kaegl...@tessco.com; cisco-nsp@puck.nether.net Sent: Thursday, June 11, 2009 5:30 AM Subject: Re: [c-nsp] WLC discovery Are you in Layer 2 or Layer 3 AP mode. I forget if this is the actual name, but you may need to switch to layer 3. Sent from handheld. On Jun 10, 2009, at 5:26 PM, Shine Joseph shinejos...@dodo.com.au wrote: Thanks Mike for the the quick response. That means I have to have physical access to the APs which are already mounted on the ceiling. I am in the process of moving this AP to another subnet and I have some 18 of them to be moved from a single subnet to different subnets. I can see this AP regsiters momentarily and de-registers. We are running code 5.1. When the AP regsiters I can go to its configuration page and I see Hardware reset and Reset to Factory defaults. Any help is appreciated. Thanks, Shine - Original Message - From: Kaegler, Mike kaegl...@tessco.com To: Shine Joseph shinejos...@dodo.com.au; cisco-nsp@puck.nether.net Sent: Thursday, June 11, 2009 4:50 AM Subject: Re: [c-nsp] WLC discovery Boot the AP with the Mode button down to reset its parameter memory. If that doesn't help, hook into console and watch the messages. If that doesn't help, execute some 'debug [...]' statements on the same console. -porkchop On 6/10/09 4:42 PM, Shine Joseph shinejos...@dodo.com.au wrote: Hi, A Cisco WLC4402 is configured and working alright. All of the APs currently are in the same subnet and hence the discovery do not require DHCP Option 43 or DNS. I want to add another AP that is in a different. When the AP tries to register with the WLC, it registers momentarily and un registers. This has happened for eithe DHCP option and DNS discovery. I am sure, there is something I have not done to get this working. Can anyone suggest somthing that I should try? Thanks in advance, Shine ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ -- Michael Kaegler, TESSCO Technologies: Engineering, 410 229 1295 Your wireless success, nothing less. http://www.tessco.com/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] Policy Based Routing on Cisco 6500
Hi, I am wondering if there any performance issue with using PBR on a Cisco 6500 with Sup720? Any pointers and suggestions are most appreciated. Thanks in advance, Shine ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
