Final post of 2013

Each year, there is a special feeling that comes to me as the final week of the year approaches.  Christmas followed by a week of late night Christian movies on Netflix and sitting in the dark listening to music off our Pandora channels until 4 to 5 AM every night.  This is by far my most favorite week of the year, every year!  I literally can not wait for this week to come.
A small note about the blog. I had 270 posts this year on this blog. I'm hoping 2014 will bring more posts than 2013. Since I'm going back to consulting, I should have plenty of material to write about. If you would like to do a guest post on this blog, feel free to contact me. Keep coming back to Network Fun!!! for more tech talk. I'm always glad you stop by here.
I hope you are enjoying then end of your 2013 a much as I am.  I also hope that 2014 will be all you want it to be in your life. May God bless you! Let me say that again. May our God bless you, beyond measure! May He shine His face upon you, and bring you peace.

Merry Christmas

Merry Christmas to everyone tomorrow.  Please know that the promised Savior has come and done all the work for us there was to do to obtain salvation.  Its the free gift of salvation.  All you have to do is just accept the free gift, just like any other Christmas gift.  That is all.
This chorus is from a song I have recently heard from the group 'Downhere'.  Its called "How Many Kings".

How many kings step down from their thrones?
How many lords have abandoned their homes?
How many greats have become the least for me?
And how many gods have poured out their hearts
To romance a world that is torn all apart
How many fathers gave up their sons for me?
Only ONE did that for me!

Jesus (Yeshua) is the one who did that for me and for you.  Again, Merry Christmas to all.

Deuteronomy 18:15-18

15 The Lord your God will raise up for you a prophet like me from among you, from your fellow Israelites. You must listen to him. 16 For this is what you asked of the Lord your God at Horeb on the day of the assembly when you said, “Let us not hear the voice of the Lord our God nor see this great fire anymore, or we will die.”

17 The Lord said to me: “What they say is good. 18 I will raise up for them a prophet like you from among their fellow Israelites, and I will put my words in his mouth. He will tell them everything I command him. 

Brocade ICX6650: A Great Top Of Rack (ToR) Choice For Data Centers

I have not talked about this model before, but there is a lot of power in this top of rack unit.  I was just looking over the hardware specs on this ICX6650 and I like it.  I could easily see this as a nice a data center switch for a medium/large size company.  Not to mention with all the video/voice/application demands these days, this is an excellent choice for performance, not only for now, but for well into the future as well.  Lets look at some hardware specs:

OSI Model: How Data Gets Encapsulated And Moved Across The Wire

I found this while doing some leisure network reading and, again, because Im a visual learner, I thought this might be interesting for those interested.
When you send data from your computer, the information goes "down" the protocol stack from application to physical layers (7-1).  The packet goes across the Cat5 and is received on the far end PC (or whatever).  NIC gets it and is decapsulated "up" the protocol stack.  Interesting stuff.

What Is The Difference Between Half-Duplex and Full-Duplex Data Transmission?

I had someone ask me this recently, so because Im a visual learner, I found this representation of both half-duplex and full-duplex.  See the difference in how these two work across the wire:

ACME Net-Net: Console Cable Makeup

I thought, when I started working on the ACME Net-Net devices, that I could probably use a Cisco console cable and I would be just fine when trying to console into the 3820 ACMEs I have.  However, that was not true.  Instead of a roll over cable, which Cisco uses, I had to use a regular Cat5 patch cable to connect to their adapter that comes in the box.   With that said, there are two console ports on the Net-Net.  One in the front, and one in the back.  The default is the one in the front (pictured below), not the back.  Make sure you plug into the front, because you have to tell the ACME to use the back if you want that one.

Who Are You And What Do You Like To Do?

Something I have learned a while back, but have been recently reminded of, is that you want to make sure you consider your own personality when choosing where you want to go to work at AND what you want to do.  This plays an important part in your happiness.  With that said, I recommend two things:
1.  Figure out for sure what personality TYPE you are, without any questions.  Take a free online test based on the Jung/Briggs/Meyers research and find this info out about yourself.  You will be richly rewarded for discovering WHO you are and WHY you are the way you are.  I know this has helped me tremendously.  Take the time to do the research.  Just google 'personality test jung', and you should find plenty of free online tests.
2.  Find a job/career that goes hand in hand with your personality type.  Simple as that.  For me, I find that IT consulting is my thing.  For you, it could be something totally different.  Either way, do yourself the favor and figure out what careers line up with your personality type.  This will enrich your life greatly since you have to spend at least a third of your life working.

This not only will help you with your work life.  It will help you in ALL of your life.

Cisco: What Is The "Deferred Counter" In A Router Or Switch Interface?

This question came up as well around the topic of the 'late collision' pursuit.  Here is the 'deferred counter' definition:

The Deferred Counter

Here is an example of output from the show interface command:

router#show interface ethernet 0
Ethernet0 is up, line protocol is up 
  Hardware is Lance, address is 0010.7b36.1be8 (bia 0010.7b36.1be8)
  Internet address is 10.200.40.74/22
  MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output 00:00:06, output hang never
  Last clearing of "show interface" counters never
  Input queue: 1/75/1/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: random early detection(RED)
  Output queue :0/40 (size/max)
  5 minute input rate 1000 bits/sec, 2 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     2058015 packets input, 233768993 bytes, 1 no buffer
     Received 1880947 broadcasts, 0 runts, 0 giants, 1 throttles
     3 input errors, 0 CRC, 0 frame, 0 overrun, 3 ignored
     0 input packets with dribble condition detected
     298036 packets output, 32280269 bytes, 0 underruns
     0 output errors, 10 collisions, 0 interface resets
     0 babbles, 0 late collision, 143 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out

The deferred counter counts the number of times the interface has tried to send a frame, but found the carrier busy at the first attempt (Carrier Sense). This does not constitute a problem, and is part of normal Ethernet operation.

Cisco: What Is A "Late Collision" In A Router Or Switch

When I posted the 'collision/duplex mismatch' posting (click here to see it), I asked some IT guys that I work with what the difference between a 'collision' and a 'late collision' is.  This caused quite a stir here, and in reality, none of us really knew the answer to that. So we did the research.  If you are wondering what the difference between a 'collision' and a 'late collision' is, here is the answer, per Cisco:

Late Collisions

To allow collision detection to work properly, the period in which collisions are detected is restricted (512 bit-times). For Ethernet, this is 51.2us (microseconds), and for Fast Ethernet, 5.12us. For Ethernet stations, collisions can be detected up to 51.2 microseconds after transmission begins, or in other words up to the 512th bit of the frame.

When a collision is detected by a station after it has sent the 512th bit of its frame, it is counted as a late collision.

Late collisions are reported by these error messages:

%AMDP2_FE-5-LATECOLL: AMDP2/FE 0/0/[dec], Late collision 
%DEC21140-5-LATECOLL: [chars] transmit error 
%ILACC-5-LATECOLL: Unit [DEC], late collision error 
%LANCE-5-LATECOLL: Unit [DEC], late collision error 
%PQUICC-5-LATECOLL: Unit [DEC], late collision error 
%PQUICC_ETHER-5-LATECOLL: Unit [DEC], late collision error 
%PQUICC_FE-5-LATECOLL: PQUICC/FE([DEC]/[DEC]), Late collision    
%QUICC_ETHER-5-LATECOLL: Unit [DEC], late collision error

The exact error message depends on the platform. You can check the number of excessive collisions in the output of a show interface ethernet [interface number] command.

router#show interface ethernet 0
Ethernet0 is up, line protocol is up 
  Hardware is Lance, address is 0010.7b36.1be8 (bia 0010.7b36.1be8)
  Internet address is 10.200.40.74/22
  MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output 00:00:06, output hang never
  Last clearing of "show interface" counters never
  Input queue: 1/75/1/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: random early detection(RED)
  Output queue :0/40 (size/max)
  5 minute input rate 1000 bits/sec, 2 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     2058015 packets input, 233768993 bytes, 1 no buffer
     Received 1880947 broadcasts, 0 runts, 0 giants, 1 throttles
     3 input errors, 0 CRC, 0 frame, 0 overrun, 3 ignored
     0 input packets with dribble condition detected
     298036 packets output, 32280269 bytes, 0 underruns
     0 output errors, 10 collisions, 0 interface resets
     0 babbles, 0 late collision, 143 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out

Note: The station that reports the late collision merely indicates the problem; it is generally not the cause of the problem. Possible causes are usually incorrect cabling or a non-compliant number of hubs in the network. Bad network interface cards (NICs) can also cause late collisions.

Cisco Switch/Router: Collisions, Duplex Mismatch And Performance Problems

I know an IT Manager at a company that was telling me about his experience about slow performance across his MPLS to his remote sites.  He was telling me that he found that his core switch was giving him an "duplex mismatch" message.  He found that his MPLS router (controlled by the ISP) was not set correctly by the ISP.  They were running half-duplex.  This was causing performance problems and he found the following on his core switch interface (connect to the MPLS router).  Notice the collisions:

GigabitEthernet2/0/1 is up, line protocol is up (connected)
  Hardware is Gigabit Ethernet, address is 2c54.XXXX.XXXX
  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
     reliability 255/255, txload 61/255, rxload 3/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Half-duplex, 100Mb/s, media type is 10/100/1000BaseTX
  input flow-control is off, output flow-control is unsupported
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:17, output 00:00:00, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 977147969
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 1223000 bits/sec, 460 packets/sec
  5 minute output rate 24292000 bits/sec, 3800 packets/sec
     1980578959 packets input, 615394171190 bytes, 0 no buffer
     Received 381332 broadcasts (334480 multicasts)
     0 runts, 1 giants, 0 throttles
     4 input errors, 3 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 334480 multicast, 0 pause input
     0 input packets with dribble condition detected
     14455682756 packets output, 9820573157817 bytes, 0 underruns
     0 output errors, 46438986 collisions, 1 interface resets
     0 babbles, 199866683 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 PAUSE output
     0 output buffer failures, 0 output buffers swapped out

So he called up the ISP and told them to make the changes on their router interface to be full duplex.  They did and he reset the counters on the core switch, and you see the results below.  Better reliablitiy.  Better performance.  And no collisions on the interface.

GigabitEthernet2/0/1 is up, line protocol is up (connected)
  Hardware is Gigabit Ethernet, address is 2c54.XXXX.XXXX
  MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 5/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
  input flow-control is off, output flow-control is unsupported
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:26, output 00:00:00, output hang never
  Last clearing of "show interface" counters 00:00:47
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 1129000 bits/sec, 388 packets/sec
  5 minute output rate 20433000 bits/sec, 3134 packets/sec
     13547 packets input, 4241997 bytes, 0 no buffer
     Received 7 broadcasts (1 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 1 multicast, 0 pause input
     0 input packets with dribble condition detected
     161684 packets output, 142796555 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 PAUSE output
     0 output buffer failures, 0 output buffers swapped out

Oh Look At This Telecomm Box...

Oh, lovely.  I came across this Telecomm box outside one of the local businesses here in Birmingham.  I thought you all might be interested in seeing this.  There is just so many things wrong in this picture...

Cisco Config Register: Router/Switch Boot Options Flow Chart

I found this diagram on Cisco's website.  This is perfect for someone like me that likes flow charts.  In the beginning of the chart, the number representation is the last number in the config register.  From there, it should be self explanatory.

Change In My Plans...

Just FYI, in January, I'm heading back to the IT consulting arena...

Should Companies Use Social Media To Find Information About You?

Should Companies Use Social Media To Find Information About You?  Plain and simple.  YES.  If you put it out there, its fair game.  Don't be stupid.  If you put it on the Internet for all to see, then you put it out there for companies to see.  Use your brain.  If you don't want a hiring company to know you are a jerk, a militant, or a real nuisance, then don't put it out there for all to see.
I know when I want to know more about someone, the first thing I do is go online.  Its just the world we live in today.  This is not the year 1813.  Its 2013.

Cisco Router: Running IOS Image Is Not The Same As The Configured IOS Image In Running-Config

I came across a problem recently where my counterpart had tftp'ed a new IOS image to a voice XML gateway.  We are planning on upgrading from 12.4 to 15.1 on our voice XML gateways, which is for our UCCE environment.  As it turns out, when one of the routers got rebooted, before the upgrade, it actually booted up to the 15 code.  This caused some problems with some of our SIP stuff, so after troubleshooting, we noticed that this one gateway was running the 15 code.  Notice below the show version after a reboot (shortened for brevity):

XMLGateway#sh version
Cisco IOS Software, 5350 Software (C5350-IK9SU2-M), Version 15.1(3)T4, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Thu 24-May-12 07:24 by prod_rel_team

ROM: System Bootstrap, Version 12.3(12r)PI6b, RELEASE SOFTWARE (fc1)

XMLGateway uptime is 3 hours, 32 minutes
System returned to ROM by reload at 10:42:56 CST Wed Dec 4 2013
System restarted at 10:44:00 CST Wed Dec 4 2013
System image file is "flash:c5350-ik9su2-mz.151-3.T4.bin"
Last reload type: Normal Reload

-------------------------------------------------
Device#  PID SN
-------------------------------------------------
*0    AS535XM-AC-RPS        

Configuration register is 0x101


Notice that the config register is set to 0x101.  Interesting.  If you do a show run, you will notice that the boot system statements point to a different IOS (shortened for brevity):

XMLGateway#
XMLGateway#sh run
Building configuration...

Current configuration : 7905 bytes
!
version 15.1
!
boot-start-marker
boot system flash:/c5350-ik9s-mz.124-24.T3.bin
boot system flash:/c5350-is-mz.124-1c.bin
no boot startup-test
boot-end-marker
!
XMLGateway#

Notice when we look at the flash, the 15 code is the first code on the flash, hence why we are booting to that code.  See the dir flash: below:
XMLGateway#dir flash:
Directory of flash:/

    1  -rw-        1072   Sep 6 2006 15:24:38 -05:00  bootstrap.tcl
    2  -rw-    37680424  Nov 12 2013 08:47:44 -06:00  c5350-ik9su2-mz.151-3.T4.bin
    3  -rw-    33029120   Sep 6 2006 14:32:14 -05:00  c5350-ik9s-mz.124-24.T3.bin
    4  -rw-        5044   Sep 6 2006 15:24:56 -05:00  bootstrap.vxml
    5  -rw-       58446   Sep 6 2006 15:25:26 -05:00  critical_error.wav
    6  -rw-        1652   Sep 6 2006 15:25:44 -05:00  cvperror.tcl
    7  -rw-        1419   Sep 6 2006 15:25:58 -05:00  handoff.tcl
    8  -rw-         583   Sep 6 2006 15:26:12 -05:00  recovery.vxml
    9  -rw-       32110   Sep 6 2006 15:26:28 -05:00  ringback.wav
   10  -rw-        4187   Sep 6 2006 15:26:40 -05:00  ringtone.tcl
   11  -rw-      191832   May 3 2013 11:12:24 -05:00  crashinfo_20130503-211224

127918080 bytes total (56885248 bytes free)
XMLGateway#

This is what Cisco says about the config register below.  And this is what caused our problem.  Very interesting.
From a Cisco document I found:
–If the last digit of the boot field is1 (for example, 0x101), the boot helper image is loaded from ROM. (On some platforms, the boot helper image is specified by the BOOTLDR environment variable.)
–If the last digit of the boot field is 2 through F (for example, 0x102 through 0x10F), the router boots the first valid image specified in the configuration file or specified by the BOOT environment variable.

Cisco Switch: Switch Stack CPU Utilization

I was asked the question recently on how do you determine the overall switch CPU utilization for stacked switches?  That is a very good question.  The answer may be a little surprising to you.  The CPU utilization on a stacked switch config is measured only on the master switch.  Below is Cisco documentation to back this answer up:
"Under normal operating conditions, on a non-stackable switch, the CPU is busy at least 5 percent of the time. If the switch is stacked, the CPU is busy at a minimum of 7 or 8 percent utilization. In a switch stack, CPU utilization is measured only on the master switch. The number of members in the stack affects the overall CPU utilization"
Document: http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/troubleshooting/cpu_util.html

Good question that was asked.  I hope this has been helpful.

Cisco IOS: What Is The Difference Between The 12 Firmware and 15 Firmware

I have had to look at this in the past and have come back across this recently, but what are the differences between the 12 code and the 15 code?  It depends on the model of router you are looking at.  With the newer router series (1900, 2900, and 3900 routers), licensing and one code is the deal.  You get one universal code and you have to have licenses to unlock features and functionality.  Its a little easier to understand and it sounds a lot like Check Point, which is NOT easy to understand to me.  The universal code has all options available in the code for base, security, voice, and enterprise level features, but you have to license them.  All in one package.  So when you go to download an upgrade for the 1900, 2900, or the 3900, you wont see several IOSs to download.  Just one universal image.  Make sure you license for what you need.
For the 1800, 2800, and 3800 models, you still get the various names in the IOS.  c2801-adventerprisek9-mz.151-4.M6.bin or c2801-advipservicesk9-mz.151-4.M6.b are examples of this.  At this point, you just dont see any universal images for these models, and I doubt you ever will.  But, you don't have to have the licenses on these models.  Just download the image you need for the features you need and do the upgrade, even though it is the 15 code.
With all of this said, there are obviously going to be feature and functionality enhancements.  You will have to look over the release notes for the image version you want to see the updates in code for more info on that.  For example, I know from 12 to 15, there are some SIP security 'features' that when you do the upgrade, SIP will stop working to your carrier if you don't plan ahead of time for the correct configuration changes. So read your release notes.

When Is It Time To Just Move On From Your Current IT Job?

I have come across several people lately who contemplate this question for themselves.  'Is it time to move on from my current job?"  Sometimes it takes some clarification from others to just make sure you are thinking clearly.  I have compiled a list of things I have seen myself or heard others say, that I think are reasons to 'move on' from your current position.  Maybe some of you will agree or disagree.  These are just my own personal opinions on this.
1.  When your boss tells you that he wont give you a raise.  If you feel you legitimately deserve a raise and you can back it up with proof that you bring more value than when you were hired, and your boss is unwilling to even listen to you about it, its time to move on.  In the work world, money means respect.  If they will give you more money, they think you are worth keeping.  If they don't give you more money, they could care less if you stay or leave.  In their mind, you are replaceable.
On the same topic, when it comes to evaluation time, if the company is doing ok, then you should get a raise.  Its called a cost of living raise, at the very least.  If they don't give you your annual raise, its time to move on.
2.  If they disrespect you, its time to move on.  You don't deserve that.  No one does.  Everyone deserves respect.  Its a human thing, not an employee thing.  You are human BEFORE you are an employee.
3.  If you have to pay for your own tools for work related purposes, its time to move on.  The company should pay for work related tools, not you.  They are paying for you, not anything else you can bring to them.  This includes something to carry the company laptop with, like a backpack.
4.  If a company treats a consultant better than you (an employee), its time to move on.  Everyone deserves respect, a consultant and employee.  But, and employee is part of the company.  A consultant is not.
5.  If you are singled out and treated differently than everyone else, its time to move on.  If there are certain perks that everyone else gets, and you are the only one that doesn't, how fair is that?  Move on.
6.  If your job changes from what you hired in to do, and you don't want the new changes, move on.  If you got hired to do data, and now they expect you to do programming (and you don't want to), then you need to find something else.  If you tell them and they don't care?  They still want you to learn programming?  Move on.  You don't want to be stuck doing something you don't want to do.
7.  This one stinks, but if they don't tell you about the holidays you are off, move on.  This one really gripes me.  I've seen one company notorious for this.  I think they hope you will work and bring in money for them, only for you to find you were off anyway.  They robbed you of your off day.  Move on.
8.  If the company doesn't really care about your input (not about direction, but about IT related technologies, etc), move on.  You are a technical resource and you were hired to provided expertise.  Move on if they don't care about your opinion.  That equals disrespect to me, and no one wants that.
9.  If your company works you to death, and doesn't listen to your pleas for relief, move on.  For some reason, the business world thinks that the more hours you put in for them, the better.  I disagree.  You need rest.  You need balance in life.  If they want all of you all the time, move on.  They are not worth it.  Life is too short.
10.  If your employer asks you to do anything unethical, move on.  They should know better than to ever ask anyone to do something that wasn't right.
11.  If they try to trample on your religious (or non-religious) beliefs, move on.  No one deserves that.  They hired you to render services from you for pay to you.  Unless you are militant.  No one deserves to work around you in that case.

So these are just a few that I came up with.  I'm sure there are a ton more.
I just had a thought that I probably need to come up with a list of reasons why a company SHOULD fire you.  That article coming at some point this month.

ACME Net-Net: Practice Config

I had a lab ACME that I was working on that I already had some configuration on it.  Its a working config, and I wanted to practice adding some config into it.  I added two realm-configs, two steering-pools, two sip-interfaces and a local-policy.

TestACME# config t
TestACME(configure)# media-manager
TestACME(media-manager)# realm-config
TestACME(configure)# media-manager
TestACME(media-manager)# realm-config
TestACME(realm-config)# identifier Outside

TestACME(realm-config)# network-inter m10:0
TestACME(realm-config)# out-man NAT_IP
TestACME(realm-config)# account disabled
TestACME(realm-config)# exit
Save Changes [y/n]?: y
**TestACME(media-manager)# realm-config
**TestACME(realm-config)# identifier Inside
**TestACME(realm-config)# network-interfaces m00:0
**TestACME(realm-config)# out-man NAT_IP
**TestACME(realm-config)# exit
Save Changes [y/n]?: y

**TestACME(media-manager)# steering-pool
**TestACME(steering-pool)# ip-add 192.168.9.91
**TestACME(steering-pool)# start-port 7000
**TestACME(steering-pool)# end-port 7999
**TestACME(steering-pool)# realm-id Outside
**TestACME(steering-pool)# exit
Save Changes [y/n]?: y
steering-pool
        ip-address                     192.168.9.91
        start-port                     7000
        end-port                       7999
        realm-id                       Outside
        network-interface
        last-modified-by               admin@10.1.1.1.
        last-modified-date             2013-11-18 14:35:22
**TestACME(media-manager)# steering-pool
**TestACME(steering-pool)# ip-add 192.168.90.75
**TestACME(steering-pool)# start-port 7000
**TestACME(steering-pool)# end-port 7999
**TestACME(steering-pool)# realm-id Inside
**TestACME(steering-pool)# exit
Save Changes [y/n]?: y
steering-pool
        ip-address                     192.168.90.75
        start-port                     7000
        end-port                       7999
        realm-id                       Inside
        network-interface
        last-modified-by               admin@10.1.1.1.
        last-modified-date             2013-11-18 14:36:37

**TestACME(media-manager)# exit
**TestACME(configure)# session-router
**TestACME(session-router)# sip-interface
**TestACME(sip-interface)# realm-id Outside
**TestACME(sip-interface)# sip-port
**TestACME(sip-port)# address 192.168.9.91
**TestACME(sip-port)# port 5060
**TestACME(sip-port)# transport-protocol udp
**TestACME(sip-port)# allow-anonymous all
**TestACME(sip-port)# exit
Save Changes [y/n]?: y
        sip-port
                address                        192.168.9.91
                port                           5060
                transport-protocol             UDP
                tls-profile
                allow-anonymous                all
                ims-aka-profile
**TestACME(sip-interface)# trans-expire 14
**TestACME(sip-interface)# out-manipulationid NAT_IP
**TestACME(sip-interface)# rfc2833-mode preferred
**TestACME(sip-interface)# add-sdp-invite invite
**TestACME(sip-interface)# add-sdp-profiles G729 PCMU telephone-event
**TestACME(sip-interface)# exit
Save Changes [y/n]?: y

**TestACME(session-router)# sip-interface
**TestACME(sip-interface)# realm-id Inside
**TestACME(sip-interface)# sip-port
**TestACME(sip-port)# add 192.168.90.75
**TestACME(sip-port)# port 5060
**TestACME(sip-port)# transport-protocol udp
**TestACME(sip-port)# allow-anonymous all
**TestACME(sip-port)# exit
Save Changes [y/n]?: y
        sip-port
                address                        192.168.90.75
                port                           5060
                transport-protocol             UDP
                tls-profile
                allow-anonymous                all
                ims-aka-profile
**TestACME(sip-interface)# trans-expire 14
**TestACME(sip-interface)# out-manipulationid NAT_IP
**TestACME(sip-interface)# rfc2833-mode preferred
**TestACME(sip-interface)# exit
Save Changes [y/n]?: y

**TestACME(session-router)# local-policy
**TestACME(local-policy)# from-add *
**TestACME(local-policy)# to-add *
**TestACME(local-policy)# source-realm Inside
**TestACME(local-policy)# policy-attributes
**TestACME(local-policy-attributes)#
**TestACME(local-policy-attributes)# next-hop 4.3.4.3
**TestACME(local-policy-attributes)# realm                          Outside
**TestACME(local-policy-attributes)# action                         replace-uri
**TestACME(local-policy-attributes)# terminate-recursion            disabled
**TestACME(local-policy-attributes)# exit
Save Changes [y/n]?: y
policy-attribute
        next-hop                       4.3.4.3
        realm                          Outside
        action                         replace-uri
        terminate-recursion            disabled
        carrier
        start-time                     0000
        end-time                       2400
        days-of-week                   U-S
        cost                           0
        app-protocol
        state                          enabled
        methods
        media-profiles
        lookup                         single
        next-key
        eloc-str-lkup                  disabled
        eloc-str-match
**TestACME(local-policy)# exit
Save Changes [y/n]?: y
local-policy
        from-address
                                       *
        to-address
                                       *
        source-realm
                                       Inside
        description
        activate-time                  N/A
        deactivate-time                N/A
        state                          enabled
        policy-priority                none
        last-modified-by               admin@10.1.1.1.
        last-modified-date             2013-11-18 14:47:02
        policy-attribute
                next-hop                       4.3.4.3
                realm                          Outside
                action                         replace-uri
                terminate-recursion            disabled
                carrier
                start-time                     0000
                end-time                       2400
                days-of-week                   U-S
                cost                           0
                app-protocol
                state                          enabled
                methods
                media-profiles
                lookup                         single
                next-key
                eloc-str-lkup                  disabled
                eloc-str-match
**TestACME(session-router)# exit
**TestACME(configure)# exit