It is my understanding that since TE LSPs
are uni-directional (and likewise the corresponding admission control
calculation), therefore there shouldn't be any problem with your proposed
configuration (in a Cisco world at least). Admission control is administered separately
on egress interfaces as mentioned by Prabakaran.
Hope this helps
Ps. I am a new to this mailing list
-----Original Message-----
From: Prabakaran T Sampath
[mailto:prabakarts@future.futsoft.com]
Sent: Thursday, 7
August 2003 19:42
To: 'Alberto Alesina';
mpls-ops@mplsrc.com
Cc: 'prabakarts'
Subject: RE: [MPLS-OPS]: MPLS
traffic eng admission control
In
general and in my understanding, the admission control and the
BW
reservation for MPLS-TE tunnel will be done for the outgoing interface.
So, We
can create a MPLS-TE tunnel from A to B and from B to A
with bandwidth
100 with out any admission control problem.
Off
Phone: 91-44-24330550 - Extn: 337
--------------------------------------------------------
-----Original Message-----
From: Alberto Alesina
[mailto:aalesina@yahoo.com]
Sent: Thursday, 7 August 2003 2:11
PM
To: mpls-ops@mplsrc.com
Subject: [MPLS-OPS]: MPLS traffic
eng admission control
I have a MPLS TE question
- Is admission control for MPLS TE tunnels done just on the outgoing
interface or on both the incoming and outgoing interface?
If it is done on both
incoming and outgoing interfaces, will there be a common interface bandwidth
pool for both incoming and outgoing tunnels for any
particular interface?
For eg - if i have 2
Cisco routers as follows:
The link between A and B is configured from Cisco CLI as
There is one MPLS TE
tunnel from A to B with bandwidth 100. Can I have another tunnel from B
to A with bandwidth 100?
I will appreciate any
kind replies.
Do you Yahoo!?
The New
Yahoo! Search - Faster. Easier. Bingo.
***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.
If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************