Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Multilink QOS Problem 1

Status
Not open for further replies.

JOAMON

IS-IT--Management
Mar 4, 2005
1,462
US
Hello....
Have wierd problem.
Have a Cisco 2811 router with two wic-1dsu-t1-v2 cards. Two t1 point to point lines to building 1/2 mile away. Both t1 lines bonded together on a multilink interface which connect to a Cisco 2611 router with two wic-1dsu-t1 cards configured in the exact same manner. QOS has been seup for voip traffic. When I do a show policy-map interface on the 2811 there are many matches on the multilink interface. When do the same on the 2611 no matches. Only thing different is the equipment. Is it possible that the 2611 does not support QOS on a multilink interface? When I remove the multilink interface and just use one point to point serial connection with the same output policy it works like a charm? Both t1's are from the same service provider. Need the bandwidth to run server applications. Is there a better way to utilize all of the available bandwidth that will allow QOS to function?

Thank You in advance
 
Joamon,

Nah, you have it right using multilink to aggregate the 2 t1s. It might be an IOS bug or something, can you post the relevant portions of the config? Maybe an access-list or something is borked.
 
I think you are right about it probably being an IOS bug...will upgrade to a more current 12.3 IOS. Cant be access list as it works when just applied to p2p serial connection. Quits when multilink is in place. Will re-post after upgrade and testing with results.

Thanks
 
Hey Eric....
You think I would be better off staying with 12.2.15T15 ( ED - Early Deployment )
Or upgrading to 12.3.13 ( LD - Limited Deployment )
Seems that for my feature set only 12.3 releases available are LD.
 
Yeah, always choose mainline code over T or others. Remember, mainline always includes all the features from the last minor release + bugfixes. (so, 12.3 includes everything from 12.2T, plus bugfixes - no additional features = more stable)

Give it a go and see if the problem goes away.
 
Thanks much...

Also...you ever flash a router from rommon mode via tftp....I set my paramaters but I keep getting the following error:
Missing or illegal ip address for variable IP_ADDRESS
ILLEGAL IP address.
 
Yeah, don't you have to type out all the pertinent parameters first?

usage: tftpdnld [-ur]
Use this command for disaster recovery only to recover an image via TFTP.
Monitor variables are used to set up parameters for the transfer.
(Syntax: "VARIABLE_NAME=value" and use "set" to show current variables.)
"ctrl-c" or "break" stops the transfer before flash erase begins.

The following variables are REQUIRED to be set for tftpdnld:
IP_ADDRESS: The IP address for this unit
IP_SUBNET_MASK: The subnet mask for this unit
DEFAULT_GATEWAY: The default gateway for this unit
TFTP_SERVER: The IP address of the server to fetch from
TFTP_FILE: The filename to fetch

The following variables are OPTIONAL:
TFTP_VERBOSE: Print setting. 0=quiet, 1=progress(default), 2=verbose
TFTP_RETRY_COUNT: Retry count for ARP and TFTP (default=7)
TFTP_TIMEOUT: Overall timeout of operation in seconds (default=7200)
TFTP_CHECKSUM: Perform checksum test on image, 0=no, 1=yes (default=1)

So, you actually have to type stuff like:

rommon1>IP_ADDRESS=192.168.1.1
rommon2>SUBNET_MASK=255.255.255.0

and so on, until you have all the options in there and then type

rommon10>tftpdnld
 
Ya I did all that and still not work....I did this a long time ago but don't remember the trick to make it work that was not documented by Cisco. I did it the long way....90 minutes to laod the 5 meg ip only ios so i could tftp the 16 meg 3des ios.
 
I knew it...something stupid.....or maybe just me stupid....commands have to be in uppercase but Cisco docs dont say this.....will accept and list out both ways but only uppercase set works.....
 
hahah - I just assumed it should be uppercase. IOS is built off of *nix, so, anything that you see in the parser that's uppercase, I would suggest you do it!
 
Already did it and it worked as it should........RTFM....right....
 
Was not wrong just assumed....and you know what happens when things are assumed......
 
bah - will take a look at it after lunch. working on a pix right now.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top