DLSw, ethernet, sap-priority-list & [non]canonical
From: Sasa Milic (smilic@xxxxxxxx)
Date: Thu Jan 03 2002 - 19:01:13 GMT-3
- Next message: IPSec: "OT: HTH - IDH"
- Previous message: Huy Luu: "Study group"
- Next in thread: Michael C. Popovich: "RE: DLSw, ethernet, sap-priority-list & [non]canonical"
- Maybe reply: Michael C. Popovich: "RE: DLSw, ethernet, sap-priority-list & [non]canonical"
- Maybe reply: Sasa Milic: "Re: DLSw, ethernet, sap-priority-list & [non]canonical"
- Maybe reply: kenairs: "Re: DLSw, ethernet, sap-priority-list & [non]canonical"
- Maybe reply: Sasa Milic: "Re: DLSw, ethernet, sap-priority-list & [non]canonical"
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
[ attachment ]
Hi,
when using sap-priority-list to prioritize traffic origination
on ethernet and going toward FEP over DLSw cloud, should FEP
mac address be in canonical or non-cannonical format ? Example:
PC --- <ethernet> --- R1 --- DLSw --- R2 --- <token> --- FEP
FEP mac address is 4001.3745.0001.
R1 config:
!
dlsw bridge-group 1 sap-priority 1
!
interface Ethernet0
bridge-group 1
!
sap-priority-list 1 high dmac 4001.3745.0001 or <---
sap-priority-list 1 high dmac 0280.eca2.0080 <---
!
PC should have hard-coded FEP address 0280.eca2.0080, right ?
But what about sap-priority-list ?
Sasa
- Next message: IPSec: "OT: HTH - IDH"
- Previous message: Huy Luu: "Study group"
- Next in thread: Michael C. Popovich: "RE: DLSw, ethernet, sap-priority-list & [non]canonical"
- Maybe reply: Michael C. Popovich: "RE: DLSw, ethernet, sap-priority-list & [non]canonical"
- Maybe reply: Sasa Milic: "Re: DLSw, ethernet, sap-priority-list & [non]canonical"
- Maybe reply: kenairs: "Re: DLSw, ethernet, sap-priority-list & [non]canonical"
- Maybe reply: Sasa Milic: "Re: DLSw, ethernet, sap-priority-list & [non]canonical"
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
[ attachment ]
This archive was generated by hypermail 2.1.4
: Thu Jun 13 2002 - 10:56:15 GMT-3