Re: (RADIATOR) HiperARC port numbers different on SNMPGET than on my Radiator logs

2001-04-02 Thread Alexey A. Shavaldin
Hi ! On Monday 02 April 2001 11:10 am, Jes?s M D?az wrote: > 3Com HiperARC can send NasPort in two ways. first, 'density based', > the nasport sent to Radius is '(slot - 1) * REPORTED_PORT_DENSITY + > mod', where 'slot:X/mod:Y' is the modem which the user is connected > to. > > So, if a user is c

Re: (RADIATOR) HiperARC port numbers different on SNMPGET than on my Radiator logs

2001-04-02 Thread Jesús M Díaz
Hello, .iso.org.dod.internet.private.enterprises.429.4.10.1.1.18. i enterprises.usRobotics.common.usrCip.usrCipPortParamTable.usrCipPortPa ramEntry.usrCipUserName.. Here is not the nasport, instead that, is the 'UsrInterfaceIndex' (sent by H.arc to radius in accounting packages). H.Arc does

Re: (RADIATOR) HiperARC port numbers different on SNMPGET than on my Radiator logs

2001-04-01 Thread Jesús M Díaz
3Com HiperARC can send NasPort in two ways. first, 'density based', the nasport sent to Radius is '(slot - 1) * REPORTED_PORT_DENSITY + mod', where 'slot:X/mod:Y' is the modem which the user is connected to. So, if a user is connected against the modem 'slot:3/mod:5', the NASPORT sent to Radius w

(RADIATOR) HiperARC port numbers different on SNMPGET than on my Radiator logs

2001-04-01 Thread Brett Murphy
Hi All, when I snmpget my 3COM HiperARC's to check for multiple logins, the port numebrs are substantially different to that being reported to Radiator by the NAS in my radius accounting table. I have found something in the archives regarding set pb REPORTED_PORT_DENSITY 30 but this does not solv