<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Pete&#039;s Packet</title>
	<atom:link href="http://petespacket.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://petespacket.com</link>
	<description>Limitless</description>
	<lastBuildDate>Wed, 02 May 2012 19:29:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='petespacket.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://s2.wp.com/i/buttonw-com.png</url>
		<title>Pete&#039;s Packet</title>
		<link>http://petespacket.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://petespacket.com/osd.xml" title="Pete&#039;s Packet" />
	<atom:link rel='hub' href='http://petespacket.com/?pushpress=hub'/>
		<item>
		<title>Juniper SRX &#8211;  Basic NAT64 configuration example</title>
		<link>http://petespacket.com/2012/05/02/juniper-srx-basic-nat64-configuration-example/</link>
		<comments>http://petespacket.com/2012/05/02/juniper-srx-basic-nat64-configuration-example/#comments</comments>
		<pubDate>Wed, 02 May 2012 19:29:18 +0000</pubDate>
		<dc:creator>Peter Kurdziel</dc:creator>
				<category><![CDATA[Juniper]]></category>

		<guid isPermaLink="false">http://petespacket.com/?p=1623</guid>
		<description><![CDATA[[SRX] Basic NAT64 configuration example SUMMARY: This article provides an example of a basic NAT64 configuration. PROBLEM OR GOAL: Basic NAT64 Configuration Example. IPv6-Host ( 2001:0660:1000:8c00::b ) &#60;&#8212;&#8212;&#8212;&#8212;&#62; ( 2001:0660:1000:8c00::a ) &#124; SRX-DUT &#124; ( 192.168.203.1 ) &#60;&#8212;&#8212;&#8212;-&#62; ( 192.168.203.10 ) Server You have a device with a IPV6 address; but your servers are using [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=petespacket.com&amp;blog=5091198&amp;post=1623&amp;subd=usaccie&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://petespacket.com/2012/05/02/juniper-srx-basic-nat64-configuration-example/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/9f3ca338e3c74ee30f330961db548e59?s=96&#38;d=monsterid" medium="image">
			<media:title type="html">Peter Kurdziel</media:title>
		</media:content>
	</item>
		<item>
		<title>802.1q tunneling scenario 3</title>
		<link>http://petespacket.com/2012/03/09/802-1q-tunneling-scenario-3/</link>
		<comments>http://petespacket.com/2012/03/09/802-1q-tunneling-scenario-3/#comments</comments>
		<pubDate>Fri, 09 Mar 2012 19:03:02 +0000</pubDate>
		<dc:creator>Peter Kurdziel</dc:creator>
				<category><![CDATA[CATALYST]]></category>
		<category><![CDATA[Routing & Switching Lab]]></category>
		<category><![CDATA[802.1q tunneling]]></category>
		<category><![CDATA[q-in-q]]></category>
		<category><![CDATA[qinq]]></category>

		<guid isPermaLink="false">http://petespacket.com/?p=1618</guid>
		<description><![CDATA[Configs: custsw1 vlan 555 ! vlan 1700 name custvlan !vlan 555 ! interface FastEthernet0/4 switchport access vlan 555 switchport mode access ! interface FastEthernet0/5 switchport access vlan 1700 switchport mode access ! interface FastEthernet0/22 des TRUNK to SPSW1 switchport trunk encapsulation dot1q switchport mode trunk ! interface Vlan555 ip address 5.5.5.1 255.255.255.0 ! interface Vlan1700 [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=petespacket.com&amp;blog=5091198&amp;post=1618&amp;subd=usaccie&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://petespacket.com/2012/03/09/802-1q-tunneling-scenario-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/9f3ca338e3c74ee30f330961db548e59?s=96&#38;d=monsterid" medium="image">
			<media:title type="html">Peter Kurdziel</media:title>
		</media:content>

		<media:content url="http://usaccie.files.wordpress.com/2012/03/ctc10-mar-09-2012.jpg" medium="image">
			<media:title type="html">802.1q tunneling 3</media:title>
		</media:content>
	</item>
		<item>
		<title>802.1q tunneling scenario 2</title>
		<link>http://petespacket.com/2012/03/09/802-1q-tunneling-scenario-2/</link>
		<comments>http://petespacket.com/2012/03/09/802-1q-tunneling-scenario-2/#comments</comments>
		<pubDate>Fri, 09 Mar 2012 18:57:55 +0000</pubDate>
		<dc:creator>Peter Kurdziel</dc:creator>
				<category><![CDATA[CATALYST]]></category>
		<category><![CDATA[Routing & Switching Lab]]></category>

		<guid isPermaLink="false">http://petespacket.com/?p=1612</guid>
		<description><![CDATA[Configs custsw1 vlan 555 ! vlan 1700 name custvlan !vlan 555 ! interface FastEthernet0/4 switchport access vlan 555 switchport mode access ! interface FastEthernet0/5 switchport access vlan 1700 switchport mode access ! interface FastEthernet0/22 des TRUNK to SPSW1 switchport trunk encapsulation dot1q switchport mode trunk ! interface Vlan555 ip address 5.5.5.1 255.255.255.0 ! interface Vlan1700 [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=petespacket.com&amp;blog=5091198&amp;post=1612&amp;subd=usaccie&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://petespacket.com/2012/03/09/802-1q-tunneling-scenario-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/9f3ca338e3c74ee30f330961db548e59?s=96&#38;d=monsterid" medium="image">
			<media:title type="html">Peter Kurdziel</media:title>
		</media:content>

		<media:content url="http://usaccie.files.wordpress.com/2012/03/ctc04-mar-09-2012.jpg" medium="image">
			<media:title type="html">802.1q tunneling 2</media:title>
		</media:content>
	</item>
		<item>
		<title>802.1q tunneling scenario 1</title>
		<link>http://petespacket.com/2012/03/08/802-1q-tunneling/</link>
		<comments>http://petespacket.com/2012/03/08/802-1q-tunneling/#comments</comments>
		<pubDate>Fri, 09 Mar 2012 03:25:10 +0000</pubDate>
		<dc:creator>Peter Kurdziel</dc:creator>
				<category><![CDATA[CATALYST]]></category>
		<category><![CDATA[Routing & Switching Lab]]></category>
		<category><![CDATA[802.1q tunneling]]></category>
		<category><![CDATA[q-in-q]]></category>
		<category><![CDATA[qinq]]></category>
		<category><![CDATA[qinq q-in-q 802.1q tunneling]]></category>

		<guid isPermaLink="false">http://petespacket.com/?p=1596</guid>
		<description><![CDATA[How 802.1q tunneling works. 802.1Q tunneling enables service providers to use a single VLAN to support customers who have multiple VLANs, while preserving customer VLAN IDs and keeping traffic in different customer VLANs segregated. A port configured to support 802.1Q tunneling is called a tunnel port. When you configure tunneling, you assign a tunnel port [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=petespacket.com&amp;blog=5091198&amp;post=1596&amp;subd=usaccie&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://petespacket.com/2012/03/08/802-1q-tunneling/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/9f3ca338e3c74ee30f330961db548e59?s=96&#38;d=monsterid" medium="image">
			<media:title type="html">Peter Kurdziel</media:title>
		</media:content>

		<media:content url="http://usaccie.files.wordpress.com/2012/03/ctc02-mar-09-2012.jpg" medium="image">
			<media:title type="html">802.1q tunnel 1</media:title>
		</media:content>

		<media:content url="http://usaccie.files.wordpress.com/2012/03/ctc03-mar-09-2012.jpg" medium="image">
			<media:title type="html">802.1q verification 1</media:title>
		</media:content>
	</item>
		<item>
		<title>How to configure a Catalyst 3750/3750-E/3750-X Series Switches Using LLDP (Link Layer Discovery Protocol)</title>
		<link>http://petespacket.com/2012/03/08/how-to-configure-a-catalyst-37503750-e3750-x-series-switches-using-lldp-link-layer-discovery-protocol/</link>
		<comments>http://petespacket.com/2012/03/08/how-to-configure-a-catalyst-37503750-e3750-x-series-switches-using-lldp-link-layer-discovery-protocol/#comments</comments>
		<pubDate>Thu, 08 Mar 2012 21:00:35 +0000</pubDate>
		<dc:creator>Peter Kurdziel</dc:creator>
				<category><![CDATA[Routing & Switching Lab]]></category>

		<guid isPermaLink="false">http://usaccie.wordpress.com/?p=1587</guid>
		<description><![CDATA[Link Layer Discovery Protocol - LLDP LLDP is a neighbor discovery protocol that allows non-Cisco devices to advertise information about themselves to other devices on the network. Cisco switches supports the IEEE 802.1AB LLDP which allow non-Cisco devices for interoperability between other devices. LLDP runs over the data-link layer which allows two devices running different network [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=petespacket.com&amp;blog=5091198&amp;post=1587&amp;subd=usaccie&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://petespacket.com/2012/03/08/how-to-configure-a-catalyst-37503750-e3750-x-series-switches-using-lldp-link-layer-discovery-protocol/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/9f3ca338e3c74ee30f330961db548e59?s=96&#38;d=monsterid" medium="image">
			<media:title type="html">Peter Kurdziel</media:title>
		</media:content>
	</item>
		<item>
		<title>Sample IPv6 Configuration for BGP with Two Different Service Providers (Multihoming)  [IP Routed Protocols] &#8211; Cisco Systems</title>
		<link>http://petespacket.com/2012/03/08/sample-ipv6-configuration-for-bgp-with-two-different-service-providers-multihoming-ip-routed-protocols-cisco-systems/</link>
		<comments>http://petespacket.com/2012/03/08/sample-ipv6-configuration-for-bgp-with-two-different-service-providers-multihoming-ip-routed-protocols-cisco-systems/#comments</comments>
		<pubDate>Thu, 08 Mar 2012 20:19:03 +0000</pubDate>
		<dc:creator>Peter Kurdziel</dc:creator>
				<category><![CDATA[Routing & Switching Lab]]></category>
		<category><![CDATA[IPV6 BGP multihoming]]></category>

		<guid isPermaLink="false">http://usaccie.wordpress.com/?p=1575</guid>
		<description><![CDATA[Sample IPv6 Configuration for BGP with Two Different Service Providers (Multihoming)  [IP Routed Protocols] &#8211; Cisco Systems Router-A Router-A# ipv6 unicast-routing !&#8212;Enables the forwarding of IPv6 packets. ipv6 cef interface Serial3/0 description CONNECTED TO SP-A ip address 192.168.10.1 255.255.255.0 ipv6 address 1202:ABCD::/64 eui-64 ipv6 enable no fair-queue clock rate 64000 ! interface Serial3/1 description CONNECTED [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=petespacket.com&amp;blog=5091198&amp;post=1575&amp;subd=usaccie&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://petespacket.com/2012/03/08/sample-ipv6-configuration-for-bgp-with-two-different-service-providers-multihoming-ip-routed-protocols-cisco-systems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/9f3ca338e3c74ee30f330961db548e59?s=96&#38;d=monsterid" medium="image">
			<media:title type="html">Peter Kurdziel</media:title>
		</media:content>

		<media:content url="http://www.cisco.com/image/gif/paws/112228/bgp2isp-01.gif" medium="image" />
	</item>
		<item>
		<title>Recent Field Notices</title>
		<link>http://petespacket.com/2012/03/08/recent-field-notices/</link>
		<comments>http://petespacket.com/2012/03/08/recent-field-notices/#comments</comments>
		<pubDate>Thu, 08 Mar 2012 19:46:42 +0000</pubDate>
		<dc:creator>Peter Kurdziel</dc:creator>
				<category><![CDATA[Routing & Switching Lab]]></category>
		<category><![CDATA[Cisco field notices]]></category>

		<guid isPermaLink="false">http://petespacket.com/?p=1571</guid>
		<description><![CDATA[All Cisco Field Notices 01-MAR-2012 (Cisco ONS 15400 Series) Field Notice: FN &#8211; 63484 &#8211; OC192XFP card does not recognize newer revisions of XFP ONS-XC-10G-C= (Rev. 02 or higher) and ONS-XC-10G-xx.y= (Rev. 02 or higher) prior to 9.2.1- SW update required 01-FEB-2012 (Cisco IP Interactive Voice Response) Field Notice: FN &#8211; 63487 &#8211; UCCX 8.5(X) [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=petespacket.com&amp;blog=5091198&amp;post=1571&amp;subd=usaccie&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://petespacket.com/2012/03/08/recent-field-notices/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/9f3ca338e3c74ee30f330961db548e59?s=96&#38;d=monsterid" medium="image">
			<media:title type="html">Peter Kurdziel</media:title>
		</media:content>
	</item>
		<item>
		<title>Google Global Cache (GGC)</title>
		<link>http://petespacket.com/2012/02/29/google-global-cache-ggc/</link>
		<comments>http://petespacket.com/2012/02/29/google-global-cache-ggc/#comments</comments>
		<pubDate>Wed, 29 Feb 2012 14:10:11 +0000</pubDate>
		<dc:creator>Peter Kurdziel</dc:creator>
				<category><![CDATA[Real World]]></category>

		<guid isPermaLink="false">http://petespacket.com/?p=1567</guid>
		<description><![CDATA[Google Global Cache Google Global Cache (GGC) allows you to serve Google content, primarily video, from the edge of your own network. This eases congestion on your network and lessens traffic on peering and transit links. GGC saves you money while improving the experience of your users. I am only posting the “Network” side of [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=petespacket.com&amp;blog=5091198&amp;post=1567&amp;subd=usaccie&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://petespacket.com/2012/02/29/google-global-cache-ggc/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/9f3ca338e3c74ee30f330961db548e59?s=96&#38;d=monsterid" medium="image">
			<media:title type="html">Peter Kurdziel</media:title>
		</media:content>
	</item>
		<item>
		<title>How to Implement Multiprotocol BGP for IPv6</title>
		<link>http://petespacket.com/2012/02/29/how-to-implement-multiprotocol-bgp-for-ipv6/</link>
		<comments>http://petespacket.com/2012/02/29/how-to-implement-multiprotocol-bgp-for-ipv6/#comments</comments>
		<pubDate>Wed, 29 Feb 2012 13:55:28 +0000</pubDate>
		<dc:creator>Peter Kurdziel</dc:creator>
				<category><![CDATA[BGP]]></category>
		<category><![CDATA[IPV6]]></category>

		<guid isPermaLink="false">http://petespacket.com/?p=1564</guid>
		<description><![CDATA[&#160; Configuring a BGP Process, BGP Router ID, and IPv6 Multiprotocol BGP Peer ipv6 unicast-routing ! router bgp 65000 no bgp default ipv4-unicast bgp router-id 192.168.99.70 neighbor 2001:DB8:0:CC00::1 remote-as 64600 address-family ipv6 unicast   neighbor 2001:DB8:0:CC00::1 activate Configuring an IPv6 Multiprotocol BGP Peer Using a Link-Local Address router bgp 65000 neighbor FE80::XXXX:BFF:FE0E:A471 remote-as 64600 neighbor [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=petespacket.com&amp;blog=5091198&amp;post=1564&amp;subd=usaccie&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://petespacket.com/2012/02/29/how-to-implement-multiprotocol-bgp-for-ipv6/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/9f3ca338e3c74ee30f330961db548e59?s=96&#38;d=monsterid" medium="image">
			<media:title type="html">Peter Kurdziel</media:title>
		</media:content>
	</item>
		<item>
		<title>Troubleshooting BGP</title>
		<link>http://petespacket.com/2012/02/29/troubleshooting-bgp/</link>
		<comments>http://petespacket.com/2012/02/29/troubleshooting-bgp/#comments</comments>
		<pubDate>Wed, 29 Feb 2012 07:13:52 +0000</pubDate>
		<dc:creator>Peter Kurdziel</dc:creator>
				<category><![CDATA[BGP]]></category>
		<category><![CDATA[Troubleshooting]]></category>

		<guid isPermaLink="false">http://petespacket.com/?p=1561</guid>
		<description><![CDATA[Main Troubleshooting Flowchart Troubleshooting BGP Neighbor Establishment Note: *Sample log messages to be checked when neighbor is not coming up: BGP_SESSION-5-ADJCHANGE: neighbor[ip address] IPv4 Unicast topology base removed from session Peer closed the session BGP_SESSION-5-ADJCHANGE: neighbor[ip address] IPv4 Unicast topology base removed from session Unknown path error Note: **Example of ping with packet size and enable does [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=petespacket.com&amp;blog=5091198&amp;post=1561&amp;subd=usaccie&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://petespacket.com/2012/02/29/troubleshooting-bgp/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/9f3ca338e3c74ee30f330961db548e59?s=96&#38;d=monsterid" medium="image">
			<media:title type="html">Peter Kurdziel</media:title>
		</media:content>

		<media:content url="http://www.cisco.com/image/gif/paws/22166/bgp_trouble_main.jpg" medium="image">
			<media:title type="html">bgp_trouble_main.jpg</media:title>
		</media:content>

		<media:content url="http://www.cisco.com/image/gif/paws/22166/bgp_trouble_neighbor.jpg" medium="image">
			<media:title type="html">bgp_trouble_neighbor.jpg</media:title>
		</media:content>

		<media:content url="http://www.cisco.com/image/gif/paws/22166/bgp_trouble_route_missing.jpg" medium="image">
			<media:title type="html">bgp_trouble_route_missing.jpg</media:title>
		</media:content>

		<media:content url="http://www.cisco.com/image/gif/paws/22166/bgp_trouble_multi_in.jpg" medium="image">
			<media:title type="html">bgp_trouble_multi_in.jpg</media:title>
		</media:content>

		<media:content url="http://www.cisco.com/image/gif/paws/22166/bgp_trouble_route_adv.jpg" medium="image">
			<media:title type="html">bgp_trouble_route_adv.jpg</media:title>
		</media:content>

		<media:content url="http://www.cisco.com/image/gif/paws/22166/bgp_trouble_multi_out.jpg" medium="image">
			<media:title type="html">bgp_trouble_multi_out.jpg</media:title>
		</media:content>
	</item>
	</channel>
</rss>
