Re: [c-nsp] MPLS Forwarding table (Two commands difference)
+ sh mpls forwarding http://www.cisco.com/en/US/docs/ios_xr_sw/iosxr_r3.7/mpls/command/reference/gr37fwd.html#wp1596071 RP/0/RP0/CPU0:router# show mpls forwarding location 0/1/CPU0 Local OutgoingOutgoing Next HopBytes Label Label InterfaceSwitched -- --- --- 22 Pop Label PO0/1/0/010.1.1.20 23 Pop Label PO0/1/0/010.1.1.20 24 Pop Label PO0/1/0/010.1.1.20 25 Unlabeled tt13 point2point 0 + sh mpls ldp forwarding http://www.cisco.com/en/US/docs/ios_xr_sw/iosxr_r3.7/mpls/command/reference/gr37ldp.html#wpmkr1642117 The following is sample output from the *show mpls ldp forwarding* command: RP/0/RP0/CPU0:router# *show mpls ldp forwarding* Prefix Label Label Outgoing Next HopGR Stale InOutInterface -- - -- --- -- - 2.2.2.2/32 22ImpNullPO0/2/0/112.0.0.2N N 3.0.0.1/32 2420 PO0/2/0/112.0.0.2N N 3.0.0.2/32 2521 PO0/2/0/112.0.0.2N N 3.0.0.3/32 2622 PO0/2/0/112.0.0.2N N 4.4.4.4/32 20ExpNullv4 tt10 4.4.4.4 N N 4.4.4.5/32 21ExpNullv4 tt10 4.4.4.4 N N 123.0.0.0/24 23ImpNullPO0/2/0/112.0.0.2N N On 16 July 2012 08:19, Xu Hu wrote: > Hi All, > > Anyone knows the difference between show mpls forwading and show mpls ldp > forwarding? > > Best Regards, > Hu Xu > ___ > 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/ > -- Mohamed Touré 06 38 62 99 07 ___ 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] Loopback IP set to .255 - 6500 responds to ICMP echo-request from wrong interface
Hi For "security reasons" (Smurf attacks ...) IP packets with destination of classfull broadcast may be filtered by your upstream security devices if any. Mohamed On 1 January 2012 10:05, Mikael Abrahamsson wrote: > On Sat, 31 Dec 2011, Eric Rosenberry wrote: > > Under that logic, the .254 IP on the other router is also the broadcast >> address since it is in a /32 subnet as well... >> > > For laughs I tried to use the highest and lowest address of a class B > network as loopback addresses. Some stuff will not work if you choose the > highest or lowest address of a classful network, in your case class C. > > Either you start logging cases against this so they fix the code, or if > you value your time, don't use these addresses (.0.0 and .255.255 on > 128.0.0.0-191.255.255.255 and .0 and .255 of 192.0.0.0-223.255.255.255). > > I would imagine the same problem exists with .0.0.0 and .255.255.255 in > class A space. > > -- > Mikael Abrahamssonemail: swm...@swm.pp.se > > __**_ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/**mailman/listinfo/cisco-nsp<https://puck.nether.net/mailman/listinfo/cisco-nsp> > archive at > http://puck.nether.net/**pipermail/cisco-nsp/<http://puck.nether.net/pipermail/cisco-nsp/> > -- Mohamed Touré 06 38 62 99 07 ___ 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] Changing VLANs
Hi, If SNMP is enabled on your switch you can set vlan information for catalyst switches. http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a00801c6035.shtml Best Regards Mohamed Touré On 4 November 2011 01:05, Mohammad Khalil wrote: > > Thanks a lot for the replies , i know that the switch will not help and i > am in need of some sort of scripting > i will start looking into doing it > > Thanks again > > Best Regards, > Mohammad Khalil > > Date: Thu, 3 Nov 2011 16:51:54 -0700 > From: td_mi...@yahoo.com > Subject: Re: [c-nsp] Changing VLANs > To: eng_m...@hotmail.com > CC: cisco-nsp@puck.nether.net > > Given the original spec, I would suggest something scripted with expect to > telnet to the switch and change the parameters when you need them. You > would then schedule it to run at the time interval you require. > There is nothing native on the switch that is going to do what you want, > you will have to look at external tools. > If you want the PC to renew it's DHCP address every 5 minutes (when you > change the VLAN it's connected to) then you'll also have to get your PC to > drop it's IP and ask for a new one from DHCP at the same time. > > > regards,Tony. > > From: Mohammad Khalil > To: joshuaatterb...@gmail.com; simon.thoma...@racq.com.au > Cc: cisco-nsp@puck.nether.net > Sent: Thursday, 3 November 2011 6:51 PM > Subject: Re: [c-nsp] Changing VLANs > > > Hi , Thank you all > > I had EEM in my mind , but i assumed that the switch is Layer 2 switch > the PC does not support dot1q trunk > the goal is i want to test some WiMAX CPEs (which by default act as a DHCP > server and provide the PC connected with access) > > > CC: eng_m...@hotmail.com; cisco-nsp@puck.nether.net > > From: joshuaatterb...@gmail.com > > Subject: Re: [c-nsp] Changing VLANs > > Date: Thu, 3 Nov 2011 16:03:43 +1000 > > To: simon.thoma...@racq.com.au > > > > Surely if you have a number of dhcp servers theres a layer3 switch or > router in the network that you can use to route between pc and servers > > > > Sent from my iPhone > > > > On 03/11/2011, at 1:11 PM, "Thomason, Simon" > wrote: > > > > > You could use EEM and tcl > scripts to do this. > > > > > > > > > -Original Message- > > > From: cisco-nsp-boun...@puck.nether.net [mailto: > cisco-nsp-boun...@puck.nether.net] On Behalf Of Mohammad Khalil > > > Sent: Thursday, 3 November 2011 4:15 AM > > > To: cisco-nsp@puck.nether.net > > > Subject: [c-nsp] Changing VLANs > > > > > > > > > Hi all , i have a layer 2 switch , i want to connect a PC to a port > and number of DHCP servers to other ports > > > i want to the PC to communicate with each server every 5 minutes > > > for example PC is connected to F0/1 and Server 1 is connected to F0/2 > , after 5 minutes i want the port the PC connecting to to change its VLAN > in order to communicate with Server 2 which is connected to port F0/3 > (which is on different VLAN) > > > > > ___ > 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/
Re: [c-nsp] Subnetting problem
Hi, the subnet in /29 is actually from 216.24.2.0 to 216.24.2.7 which includes 216.24.2.4 (basically an host of an /29 subnet). If you want to include 216.24.2.8 also you should consider a bigger subnet (/28 for example) that will include 216.24.2.0 - 216.24.2.15. the right subnet may be : 216.24.2.0/*28* On 6 October 2011 21:34, Gregori Parker wrote: > Try: > > ip route 216.24.2.0 255.255.255.248 216.24.0.54 > > > Router is complaining because your /29 cant have a base address of .4 > > > On 10/6/11 12:22 PM, "Joseph Mays" wrote: > > >It feels strange to be asking a question about something as simple as a > >subnet here, but I'm honestly not sure what's going on in this case. > >Probably something simple. > > > >As you can see from the following set of commands, the router is fine > >with breaking the following addresses up into /30's, but not fine with > >the aggregate of the two routes into a /29. > > > >gw1.armplc(config)#ip route 216.24.2.4 255.255.255.252 216.24.0.54 > >gw1.armplc(config)#no ip route 216.24.2.4 255.255.255.252 216.24.0.54 > >gw1.armplc(config)#ip route 216.24.2.8 255.255.255.252 216.24.0.54 > >gw1.armplc(config)#no ip route 216.24.2.8 255.255.255.252 216.24.0.54 > >gw1.armplc(config)#ip route 216.24.2.4 255.255.255.248 216.24.0.54 > >%Inconsistent address and mask > > > >___ > >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/ > -- Mohamed Touré 06 38 62 99 07 ___ 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/