[Contents] [Prev] [Next] [Index] [Report an Error]

Router C Status

After you enter the local-address, remote-address, and interface parameters in TE link te-oxc2 and commit the changes, the router automatically creates a local ID at the te-link and interface levels of the [edit protocols link-management] hierarchy. To view these IDs, issue the show link-management te-link command.

user@RouterC> show link-management te-link

  
TE link name: te-oxc2,  State: Up
   Local identifier: 41059, Remote identifier: 0,  Local address: 10.35.200.1, Remote address: 10.35.200.2, Encoding: SDH/SONET,
  Minimum bandwidth: 155.52Mbps, Maximum bandwidth: 155.52Mbps, Total bandwidth: 155.52Mbps, Available bandwidth: 0bps
   Name          Local ID  Remote ID      Bandwidth In use    LSP
   so-0/1/0         22277          0     155.52Mbps No

Once you see what these values are, configure them as remote IDs at the same hierarchy levels on OXC2 where you found them on Router C. In this example, 41059 is Router C’s local TE link ID (configure this as the TE link remote-ID on OXC2) and 22277 is Router C’s local interface ID (configure this as the interface remote-ID on OXC2).

After you configure both remote IDs on both peers, the GMPLS TE links should work. Using the same command as before, you can determine whether the link is functional, with both remote and local IDs in place:

user@RouterC> show link-management te-link

 
TE link name: te-oxc2, State: Up
  Local identifier: 41059, Remote identifier: 41060, Local address: 10.35.200.1, Remote address: 10.35.200.2, Encoding: SDH/SONET,
  Minimum bandwidth: 155.52Mbps, Maximum bandwidth: 155.52Mbps, Total bandwidth: 155.52Mbps, Available bandwidth: 0bps
   Name          Local ID  Remote ID      Bandwidth In use    LSP
   so-0/1/0         22277      22278     155.52Mbps Yes       gmpls-lsp1

The other show commands operate like those in Router A Status.

[Contents] [Prev] [Next] [Index] [Report an Error]