Ios - Tag - Fryguy's Blog

Cisco CSR1000v For Home Labs

Fryguy — Fri, 27 Dec 2013 14:00:40 +0000

I have been using the Cisco CSR1000V for my home lab setup for a little bit now. There have been some questions on how to set this up for a home lab and I figured I would cover how I am using it.
For this post, here is what we are going to build – a three (3) node CSR1000V network and three (3) vSwitch Networks to connect the CSR1000Vs together. We will also configure the CSR1000V to have connectivity back to the “home production” network so that we can SSH/Telnet to these routers when we are labbing.

Obtaining the CSR1000V Router Software

To obtain the Cisco CSR1000V you need to download it from Cisco at this LINK and click on the Download software as seen circled below

IOS XR – iBGP and eBGP

Fryguy — Mon, 24 Sep 2012 12:25:02 +0000

BGP, this is where it starts to get different with IOS XR.
First up, configuring an iBGP peering with R2’s 150.1.12.2 in AS1 and advertise our loopback interface.
RP/0/7/CPU0:R1(config)#
RP/0/7/CPU0:R1(config)#router bgp 1
Let’s define the network we want to advertise, under the address family:
RP/0/7/CPU0:R1(config-bgp)#address-family ipv4 unicast
RP/0/7/CPU0:R1(config-bgp-af)#net 1.1.1.1/32
RP/0/7/CPU0:R1(config-bgp-af)#exit
Now, we can configure the neighbor. Notice all the commands for the neighbor are under the neighbor now – not next to the neighbor.
RP/0/7/CPU0:R1(config-bgp)#nei 150.1.12.2
RP/0/7/CPU0:R1(config-bgp-nbr)#remote-as 1
RP/0/7/CPU0:R1(config-bgp-nbr)#address-family ipv4 unicast
RP/0/7/CPU0:R1(config-bgp-nbr-af)#exit
RP/0/7/CPU0:R1(config-bgp-nbr)#comm
Thu Mar 29 22:47:05.147 UTC
RP/0/7/CPU0:R1(config-bgp)#exit
RP/0/7/CPU0:R1(config)#exit
Now, time to see if we have a neighbor established:
RP/0/7/CPU0:R1#sh bgp nei 150.1.12.2
Thu Mar 29 22:48:13.338 UTC

IOS XR – OSPF Configuration

Fryguy — Fri, 14 Sep 2012 13:22:03 +0000

Time for some OSPF configs, these will build off the previous configs we just did. For this lab, the other router, R2, was
preconfigured to support the connections.

We will place our loopback and out g0/3/0/2 interface into OSPF process LAB and area 0.0.0.0

RP/0/7/CPU0:R1#
RP/0/7/CPU0:R1#conf t
Thu Mar 29 19:37:52.671 UTC

Defineour OSPF process name
RP/0/7/CPU0:R1(config)#router ospf LAB

Now to define our area first
RP/0/7/CPU0:R1(config-ospf)#area 0.0.0.0

Now we can place the interfaces into the area, no need to entering subnets
RP/0/7/CPU0:R1(config-ospf-ar)#inter loo0
RP/0/7/CPU0:R1(config-ospf-ar-if)#inter g0/3/0/2
RP/0/7/CPU0:R1(config-ospf-ar-if)#exit
RP/0/7/CPU0:R1(config-ospf-ar)#exit
RP/0/7/CPU0:R1(config-ospf)#exit
RP/0/7/CPU0:R1(config)#commit

Thu Mar 29 19:38:15.182 UTC
RP/0/7/CPU0:R1(config)#

Now to look at our IP Protocols running:
RP/0/7/CPU0:R1#sh ip proto
Thu Mar 29 19:38:24.113 UTC
Routing Protocol OSPF LAB
Router Id: 1.1.1.1
Distance: 110
Non-Stop Forwarding: Disabled
Redistribution:
None
Area 0.0.0.0
Loopback0
GigabitEthernet0/3/0/2
RP/0/7/CPU0:R1#

IOS XR – Wildcard Masks

Fryguy — Sat, 08 Sep 2012 01:24:21 +0000

Sorry for the lapse in posting. I am working on something that I think is pretty cool. Should be ready for publication soon!
But back to IOS XR for a quick post!
A really cool thing with IOS XR is interface wildcards.
If you want to only see the Loopback interfaces, all of them. Normally you would do something like Show int br | in Loop, but with XR you can use a wildcard ()
RP/0/7/CPU0:R1#sh int l br
Mon Apr 16 17:21:08.088 UTC
Intf Intf LineP Encap MTU BW
Name State State Type (byte) (Kbps)
———————————————————————-
Lo0 up up Loopback 1500 0
Lo100 up up Loopback 1500 0
Lo666 up up Loopback 1500 0
Lo667 up up Loopback 1500 0
Lo1000 up up Loopback 1500 0
RP/0/7/CPU0:R1#

AppleTV Unboxing and first thoughts

Fryguy — Thu, 15 Mar 2012 18:00:31 +0000

It arrived today – one day early – the AppleTV 3rd Gen. I jumped on ordering this as soon as I was able to, especially since I wanted to get another one for the bedroom (we already have the 2nd Gen in our family room). The 3rd Gen one will be hooked up on our primary TV in the family room, but I could not wait to see what the 1080P looked like, so I hooked it up.
But first the boring unboxing:
You can see the box in the top picture, here is a picture of… the back of the box! It has some information and such on it, pretty cool for a quick overview of what you can use this for.

When you look at the side of the box, you can see that is boasts 802.11n WiFi, HDMI, and 1080P graphics.

Cisco 3750 Stack Member Recovery

Fryguy — Mon, 15 Aug 2011 15:28:57 +0000

Interesting day today, that it was. Well, I guess I should say that the weekend was interesting as we had some bad weather – and just by some random chance we lost a CoreWAN router and a Cisco 3750 Stack member. So lets just say that I spent my morning recovering the WAN router by moving the circuits to another router and recovering a 3750 switch. Since moving WAN circuits around is no big deal, lets talk about recovering a Cisco 3750 stack member switch. I will assume you have identified the switch that is dead – no lights is a good indication – and have received your replacement switch from Cisco already. The first thing you should do is independently boot the new switch and check the IOS version and make sure that it is either the same or compatible. For me, I prefer to make sure they are the same before adding a switch to the stack as I never trust “compatible” version of switch code. If you have ever upgraded a 3750 stack, you know it can take some time for the stack to come back – over 10 minutes is not unheard of. So what do you do if you lose a switch in your stack, and have the right replacement? Amazingly enough, just swap it out and the stack will work as normal. Now, don’t we always wish life was that simple!

CatOS and IOS

Fryguy — Mon, 15 Aug 2011 12:05:06 +0000

Ahh, Catalyst OS – old skool Layer 2. There is a dwindling number of engineer who have seen this code, let alone have ever used this code and understand it. Since I am about to convert some of the CatOS switches at work to IOS, I figured I would share some of the basics and joys of CatOS with you. Ok, perhaps I am just reminiscing a bit here – but if this can help just one person, then all is good – right?
So, what is this thing called CatOS one might ask. Well, in short it is Cisco OS that is Layer 2 only; there are no routed interfaces, no IP addresses on interfaces (well, there is SC0) or IPs for VLANS – just L2 VLANS and Ports. When a Catalyst switch is running CatOS for Layer 2 it is called Hybrid mode – if the switch is running IOS for Layer 2 and Layer 3, it is called Native mode. CatOS dates back to 1993 when Cisco acquired Crescendo Communications in 1993 and the Catalyst line – its first foray into Switching – and because of the wide acceptance of XDi/CatOS, the OS has lived on for many years. As the Catalyst line moved forward from the 5000, to the 5500, and now the 6500 – CatOS has survived. It is only recently ( Dec 2010 ) that Cisco is no longer fixing and producing CatOS code, and CatOS code will finally go End-Of-Support in December of 2014.

IOS 15 License

Fryguy — Thu, 30 Jun 2011 19:36:21 +0000

The other day I was looking for a Cisco IOS 15 license matrix and was unable to find anything definitive and all that I was doing was trying to find out what services are enabled in different images. Granted, one can use the Feature Navigator to find out and compare, but sometimes we just need something quick and simple.
In IOS 15 there is a Base image, a Security Image, a Data Image, and a Unified Communications / Collaboration Image. Each one has some common features, but for the most part each are different. Below is a matrix that I was able to put together using the Cisco Feature Navigator and comparing all the images to each other. If you would like an Excel version, you can click here

I had to remove the in-line matrix for the moment as it was just too big for WordPress to handle. For now, just grab the link above.
Also, I think I need to check a few things with some of the other hardware out there. I think the Cisco 3925e that I selected has much more features in the base code then say, a 2901 would have. I will do an updated post shortly on some of the model comparisons and IOS feature matrix.

Cisco Archive and Configure

Fryguy — Mon, 06 Jun 2011 08:15:36 +0000

There has been some interesting discussions on configuration differences with IOS and JUNOS on Twitter the past few days. One of the biggest things has been the inclusion of a Rollback command in JUNOS; and to be perfectly honest, that has to be one of the best commands that JUNOS has!
In case you are not familiar with it, in JUNOS if you submit a change and then enter commit confirm (default 10 minutes), the router will not “save” the configuration change until you commit the change again. This way if you make a change, lock yourself out of the device, it will revert to the previous configuration and you should have your access back.
(some housekeeping)
Router/Switch Output
Commands
Notes

[edit]
user@host# commit confirmed
commit confirmed will be automatically rolled back in 10 minutes unless confirmed
commit complete
#commit confirmed will be rolled back in 10 minutes
By entering commit again, the change will become permenant
[edit]
user@host# commit

Now, what about IOS? Well, typically we do the reload in x command before we make a change, but is there another way? Well, yes there is! We have the archive command and the config replace command string that will perform a similar function to to the JUNOS command and less drastic then the reload in command.
So, lets first cover the archive command.
The archive command allows you to make an archive of the config either over a time-period (say 1440 minutes) or when the write-memory command is initiated. The archive can be stored in flash, tftp, ftp, or a few other places. To setup archiving:
Rack1R2#conf t
Enter configuration commands, one per line. End with CNTL/Z.
To enter the archive config, enter the archive command
Rack1R2(config)#archive
From there, you need to tell it 1) where to store the file and 2) what to call it.
Here it will be flash:/archive with a name of Rollback
Rack1R2(config-archive)#path flash:/archive/Rollback
Here I tell it to archive the previous config whenever the write-memory command is executed
Rack1R2(config-archive)#write-memory
Also, I might as well make sure that we back it up once a day at a minimum. Range is from 1 minute to 525600 minutes (1 year)
Rack1R2(config-archive)#time-period ?
<1-525600> Number of minutes to wait between archive creation
Rack1R2(config-archive)#time-period 1440
Rack1R2(config-archive)#
Now, if we look at the flash:/archive/ folder, what will we see? Lets look (I already have some saved in memory)
Rack1R2#dir flash:archive
Directory of flash:/archive/
17 -rw-        1806   Jun 3 2011 19:34:16 +00:00 Rollback-2
18 -rw-        1806   Jun 3 2011 19:35:02 +00:00 Rollback-3
16 -rw-        1744   Jun 3 2011 19:31:54 +00:00 Rollback-1
512057344 bytes total (328622080 bytes free)
Rack1R2#
As you can see, we have a few files there, each appended with a number (call it revision with highest being most recent). To check, use the show archive command
Rack1R2#show archive
There are currently 4 archive configurations saved.
The next archive file will be named flash:/archive/Rollback-4
Archive # Name

1       flash:/archive/Rollback-1
2       flash:/archive/Rollback-2
3       flash:/archive/Rollback-3 <- Most Recent
4
5
6
7
8
9
10
11
12
13
14
Rack1R2#
So, what does all this mean and how does this relate to the commit confirm command in Junos? Good question! Here we go!
So, when you need to do a change, just execute the archive config command prior to the change. That will create a snapshot of the existing config in the archive directory.
Rack1R2#archive config

Lets take a look and see what revision we have saved:
Rack1R2#show archive
There are currently 5 archive configurations saved.
The next archive file will be named flash:/archive/Rollback-5
Archive # Name

1       flash:/archive/Rollback-1
2       flash:/archive/Rollback-2
3       flash:/archive/Rollback-3
4       flash:/archive/Rollback-4 <- Most Recent
5
6
7
8
9
10
11
12
13
14
Rack1R2#
Now, there is another command that we need to know about – its the configure replace command! We can use that similar to the commit confirm command because of the archive command.
Rack1R2#configure replace flash:archive/Rollback-4 time 60
That is all good – lets test the command!

I have R1 and R2 configured like the diagram below, connected via Frame-Relay and all interfaces are in RIPv2

Here is the routing table and interface status on R2:
Rack1R2#sh ip route
Codes: C – connected, S – static, R – RIP, M – mobile, B – BGP
D – EIGRP, EX – EIGRP external, O – OSPF, IA – OSPF inter area
N1 – OSPF NSSA external type 1, N2 – OSPF NSSA external type 2
E1 – OSPF external type 1, E2 – OSPF external type 2
i – IS-IS, su – IS-IS summary, L1 – IS-IS level-1, L2 – IS-IS level-2
ia – IS-IS inter area, * – candidate default, U – per-user static route
o – ODR, P – periodic downloaded static route
Gateway of last resort is not set
150.1.0.0/16 is variably subnetted, 4 subnets, 2 masks
R       150.1.1.1/32 [120/1] via 150.1.12.1, 00:00:23, Serial4/0.1
C       150.1.12.0/24 is directly connected, Serial4/0.1
R       150.1.11.0/24 [120/1] via 150.1.12.1, 00:00:23, Serial4/0.1
R       150.1.111.1/32 [120/1] via 150.1.12.1, 00:00:23, Serial4/0.1
150.2.0.0/32 is subnetted, 3 subnets
C       150.2.222.2 is directly connected, Loopback2
C       150.2.22.2 is directly connected, Loopback1
C       150.2.2.2 is directly connected, Loopback0
Rack1R2#sh ip int br | ex un
Interface                  IP-Address      OK? Method Status                Protocol
Serial4/0.1                150.1.12.2      YES manual up                    up
Loopback0                  150.2.2.2       YES manual up                    up
Loopback1                  150.2.22.2      YES manual up                    up
Loopback2                  150.2.222.2     YES manual up                    up
Rack1R2#
Here is the same information for R1
Rack1R1#sh ip route
Codes: C – connected, S – static, R – RIP, M – mobile, B – BGP
D – EIGRP, EX – EIGRP external, O – OSPF, IA – OSPF inter area
N1 – OSPF NSSA external type 1, N2 – OSPF NSSA external type 2
E1 – OSPF external type 1, E2 – OSPF external type 2
i – IS-IS, su – IS-IS summary, L1 – IS-IS level-1, L2 – IS-IS level-2
ia – IS-IS inter area, * – candidate default, U – per-user static route
o – ODR, P – periodic downloaded static route
Gateway of last resort is not set
150.1.0.0/16 is variably subnetted, 4 subnets, 2 masks
C       150.1.1.1/32 is directly connected, Loopback0
C       150.1.12.0/24 is directly connected, Serial4/0.1
C       150.1.11.0/24 is directly connected, Loopback1
C       150.1.111.1/32 is directly connected, Loopback2
150.2.0.0/32 is subnetted, 3 subnets
R       150.2.222.2 [120/1] via 150.1.12.2, 00:00:12, Serial4/0.1
R       150.2.22.2 [120/1] via 150.1.12.2, 00:00:12, Serial4/0.1
R       150.2.2.2 [120/1] via 150.1.12.2, 00:00:13, Serial4/0.1
Rack1R1#sh ip int br | ex un
Interface                  IP-Address      OK? Method Status                Protocol
Serial4/0.1                150.1.12.1      YES manual up                    up
Loopback0                  150.1.1.1       YES manual up                    up
Loopback1                  150.1.11.1      YES manual up                    up
Loopback2                  150.1.111.1     YES manual up                    up
Rack1R1#
Lets test the connectivity by PINGing R2 Loopback 2 from R1 Loopback2
Rack1R1#ping 150.2.222.2 so lo2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 150.2.222.2, timeout is 2 seconds:
Packet sent with a source address of 150.1.111.1
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/57/60 ms
Rack1R1#
Good, now lets test the config replace command (IOS Rollback)
First, we will archive the config
Rack1R2#archive config
Now lets see what archives we have:
Rack1R2#sh archive
There are currently 6 archive configurations saved.
The next archive file will be named flash:/archive/Rollback-6
Archive # Name

1       flash:/archive/Rollback-1
2       flash:/archive/Rollback-2
3       flash:/archive/Rollback-3
4       flash:/archive/Rollback-4
5       flash:/archive/Rollback-5 <- Most Recent
[– SNIP –]

Ok, Rollback-5 is the most recent.
Now on R1 we will start a 1000 packet ping
Rack1R1#ping 150.2.222.2 so lo2 repeat 100
Type escape sequence to abort.
Sending 1000, 100-byte ICMP Echos to 150.2.222.2, timeout is 2 seconds:
Packet sent with a source address of 150.1.111.1
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Now that we have that started, lets move on
Now, on R2 we will execute the configure replace command, set the timer to 60 seconds, then shut down the Serial 4/0 (frame-relay) interface
Rack1R2#configure replace flash:/archive/Rollback-5 time 60
Timed Rollback: Backing up to flash:/archive/Rollback-7
It will now ask you to make sure you want to do this – checks and balances
This will apply all necessary additions and deletions
to replace the current running configuration with the
contents of the specified configuration file, which is
assumed to be a complete configuration, not a partial
configuration. Enter Y if you are sure you want to proceed. ? [no]: Y
Total number of passes: 0
Rollback Done
*Jun 3 21:43:22.026: Rollback:Acquired Configuration lock.
Rack1R2#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Rack1R2(config)#int ser 4/0
Rack1R2(config-if)#shut
Rack1R2(config-if)#
*Jun 3 21:43:28.274: %LINK-5-CHANGED: Interface Serial4/0, changed state to administratively down
*Jun 3 21:43:29.274: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial4/0, changed state to down
Rack1R2(config-if)
Hmm, if we look at the ping that we have going on R1 we see that it can no longer PING R2
Rack1R1#ping 150.2.222.2 so lo2 repeat 1000
Type escape sequence to abort.
Sending 1000, 100-byte ICMP Echos to 150.2.222.2, timeout is 2 seconds:
Packet sent with a source address of 150.1.111.1
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!………………………….
……..
Lets wait…. there, the config just rolled back on R2 and R1 can PING again!
Rack1R1#ping 150.2.222.2 so lo2 repeat 1000
Type escape sequence to abort.
Sending 1000, 100-byte ICMP Echos to 150.2.222.2, timeout is 2 seconds:
Packet sent with a source address of 150.1.111.1
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!………………………….
…………………!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!
Success rate is 94 percent (948/1000), round-trip min/avg/max = 56/57/240 ms
Rack1R1#
So what happened on R2? Here is the output on the console:
Rack1R2(config-if)#Timed Rollback: rolling to:flash:/archive/Rollback-7
!Pass 1
Neat, it will show you the commands it is about to enter!

!List of Commands:
interface Serial4/0
no shutdown
end
Total number of passes: 1
Rollback Done
*Jun 3 21:44:22.218: Rollback:Acquired Configuration lock.
Rack1R2(config-if)#
*Jun 3 21:44:22.778: %PARSER-3-CONFIGNOTLOCKED: Unlock requested by process ’21’. Configuration not locked.
Rack1R2(config-if)#
*Jun 3 21:44:24.586: %LINK-3-UPDOWN: Interface Serial4/0, changed state to up
*Jun 3 21:44:25.586: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial4/0, changed state to up
Rack1R2(config-if)#
If all is good after your change and you need to not roll-back, just issue the command configure confirm and it will cancel the rollback._
_
Rack1R2#configure confirm

If you already issued that command, you will get the following output:
Rack1R2#configure confirm
%No timed rollback pending
Rack1R2#
Not as simple as the JUNOS commands, but is still valuable in the IOS world!

R1 Config Here
R2 Config Here

Cisco ASR and LACP

Fryguy — Thu, 02 Dec 2010 16:50:03 +0000

I am currently working on a new site deployment utilizing some Cisco ASR1002 routers. When we typically design a location we cross-connect the two WAN routers via a cross-over cable; this allows us to have the capability to continue to transit traffic over the connected WAN routers and WAN links if need to take down the Core at the site for maintenance.
If you look at the image below you will see three Sites – A – B – C. Traffic that is destined to Site B from Site A will transit the connected WAN link. So what happens if that WAN link goes down, it will transit through Site C instead. By having the WAN routers connected via a cross-over cable, the traffic will stay at the end and not transverse the internal LAN of the site.

Ok, the background information is now out of the way. Lets continue.
Typically we use a single gigabit ethernet cross-over cable between the routers, due to hardware limitations. Well, with the ASR series we now have more interfaces that we can use for this connectivity. What I have also found is that the ASR and IOS-XE support LACP and etherchannels. This is a wonderful thing as it actually solves some of the problems of a single cross-over cable between routers.
So, how does one configure LACP on the ASR 1002? It is done the same way as you would on the Nexus for L3 etherchannel. Below are the configuration commands as well as the ways to check.
For this example, we are going to create Port-Channel 12 on the router and assign interfaces G0/0/2 and G0/0/3 to the channel-group
Router#conf t
Router(config)#interface GigabitEthernet0/0/2
Router(config-if)# channel-group 12 mode active
Router(config-if)# no shut
Router(config-if)# exit
Router(config)#interface GigabitEthernet0/0/3
Router(config-if)# channel-group 12 mode active
Router(config-if)# no shut
Router(config-if)# exit
Now we can configure an IP address on the port-channel interface:
Router(config)#interface Port-channel12
Router(config-if)# ip address 10.1.1.1 255.255.255.252
T0 check the port-channel:
Router#sh int port-channel 12
Port-channel12 is up, line protocol is up
Hardware is GEChannel, address is c471.fe0c.55cb (bia c471.fe0c.55cb)
Internet address is 10.98.255.9/30
MTU 1500 bytes, BW 2000000 Kbit/sec, DLY 10 usec,
You can also look at the LACP information:
Router#sh lacp 12 neighbor
Flags: S – Device is requesting Slow LACPDUs
F – Device is requesting Fast LACPDUs
A – Device is in Active mode       P – Device is in Passive mode
Channel group 12 neighbors
Partner’s information:
Partner Partner   LACP Partner Partner   Partner Partner     Partner
Port      Flags   State     Port Priority Admin Key Oper Key Port Number Port State
Gi0/0/2   SA      bndl      32768         0x0       0xC      0x3         0x3D
Gi0/0/3   SA      bndl      32768         0x0       0xC      0x4         0x3D
Router#
Now lets ping to test:
Router#p 10.1.1.2 t 1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 1 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
Router#
If you noticed I typed t 1 – that means use a 1 second timeout. I did that in case, for some reason, it does not PING successfully I only have to wait half the normal time of 2 seconds per ping. This might not seem like a big deal, but if you use this on some LAB test – you can save some time and frustration. 🙂