Let me preface this post with a quick word – all the information presented here is pure speculation with a little bit of evidence to back up my speculation.  By no means is any of this a guarantee nor a near-time release for any of these modules.  This is me just presenting the information that I am able to find and sharing it with you.  Now, I am excited for some of this – and it definitely shows where the Nexus 7000 is going – so I hope that this type of information can help keep you informed on where this platform is going.  The future looks bright.

While I was doing the research on the track names for the Nexus line cards I came across a few things.  Things that we have all either assumed or have heard rumors of, but I guess now we know what is coming in the future for the Nexus 7000. First this is a listing for Silverstone – Supervisor 2 module, a little curious for sure.

The second thing that I came across was a bit more interesting to me – its a Service Module – N7K-SVC-APP-HW-1 – named after the Indian God, Agni.  What is curious is that Agni is a messenger from and to the other gods (modules), so it is aptly named.  I am guessing that this will be a 2-port module (Agni has 2-heads) similar to what the WS-X6582-2PA adapter is to the 6500. @matthewnorwood just also suggested perhaps this is an Application Load Balancer similar to the ACE30 on the Cat6k, I actually think that might be a more realistic option.(continued)

]]>https://hugo.fryguy.net/2010/07/22/data-capture-on-cisco-asa/Fri, 23 Jul 2010 00:21:15 +0000Fryguyhttps://hugo.fryguy.net/2010/07/22/data-capture-on-cisco-asa/A few weeks ago t I blogged on the iPhone FaceTime application and how the communication worked.  Since I did the data capture on the Cisco ASA via CLI, I thought I would share the basics on how to do that.  Capturing data right on you ASA makes it much easier to troubleshoot as well as support new applications where you are unsure of how they are working.  Honestly though, we know that good documentation comes with all in-house application development, right?
For this blog, the inside IP that I wanted to capture information for was 192.168.0.128 to any outside IP address.
1.  Create the appropriate access-list on your ASA for the interesting traffic. Below I am capturing any traffic to and from my iPhone (IP Address 192.168.0.128)
access-list capture_iphone extended permit ip host 192.168.0.128 any
access-list capture_iphone extended permit ip any host 192.168.0.128
2. From the Enable prompt, you then create the capture.  In this case I am creating a capture called iPhone against access-list created in the last step of capture_iphone with a buffer of 1m bytes and a packet length of 2000, on the inside interface and set to overwrite when the buffer is full.
capture iPhone type raw-data access-list capture_iphone buffer 1000000 packet-length 2000 interface inside circular-buffer
3. Once the capture file is running, you can view it by using the command sh capture iPhone , or my preference is to download it from the ASA in PCAP format:
https://ip_address_of_asa/admin/capture/capturename/pcap
or in this example:  https://192.168.0.1/admin/capture/iPhone/pcap
4. After you d/l the capture file, just open it in Wireshark and you are good to go!
There is another way to view the capture and that is from the CLI. Below are the command options and their Cisco explanation.
FryGuyFW-ASA# sh capture iPhone ?
access-list    Display packets matching access-list
count          Display of packets in capture
decode         Display decode information for each packet
detail         Display more information for each packet
dump           Display hex dump for each packet
packet-number  Display packet in capture
trace          Display extended trace information for each packet
|              Output modifiers