The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2002-Aug> msg00145



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

support mpls-te-mib in transit and tail points.

  • From: Yuan Gu <yuangu@ipinfusion.com>
  • Date: Fri, 30 Aug 2002 14:48:20 -0700
  • CC: "mpls@UU.NET" <mpls@UU.NET>
  • Organization: IP Infusion Inc

> >If yes, mean while
> >this table allows creating new tunnel, updating and remove existing
> >tunnel. Is that to say a tunnel can be updated or removed from
> >transit/egress node (even created)?
>
>          In general, no. Most implementations only allow modification
> to a tunnel at its head. In general, the information shown at the mid-points
> and tail are informational only.
>
>

Then how do you inform SNMP that for same table, some rows can be modified
while some other rows can't( most of the objects in TunnelTable are
"read-create")? Or you just send error message back to SNMP when you receive a
SNMP "set" request but you don't want to change your value?