11
Microsoft Standard TCP/IP Port Monitor Futures Mike Fenelon – Software Design Engineer Windows Digital Document Platforms & Solutions Group November 2004

Microsoft Standard TCP/IP Port Monitor Futures Mike Fenelon – Software Design Engineer Windows Digital Document Platforms & Solutions Group November 2004

Embed Size (px)

Citation preview

Page 1: Microsoft Standard TCP/IP Port Monitor Futures Mike Fenelon – Software Design Engineer Windows Digital Document Platforms & Solutions Group November 2004

Microsoft Standard TCP/IP Port Monitor FuturesMicrosoft Standard TCP/IP Port Monitor Futures

Mike Fenelon – Software Design Engineer

Windows Digital Document Platforms & Solutions Group

November 2004

Mike Fenelon – Software Design Engineer

Windows Digital Document Platforms & Solutions Group

November 2004

Page 2: Microsoft Standard TCP/IP Port Monitor Futures Mike Fenelon – Software Design Engineer Windows Digital Document Platforms & Solutions Group November 2004

AgendaAgenda

Standard TCP/IP Port Monitor (TCPMon) Port Id feature

TCPMon Print Device Type detection

TCPMon Network Card detection

Standard TCP/IP Port Monitor (TCPMon) Port Id feature

TCPMon Print Device Type detection

TCPMon Network Card detection

Page 3: Microsoft Standard TCP/IP Port Monitor Futures Mike Fenelon – Software Design Engineer Windows Digital Document Platforms & Solutions Group November 2004

Standard TCP/IP Port Monitor Port Id featureStandard TCP/IP Port Monitor Port Id feature

Read Network Card information from the MIB-2Request MIB-2.system.sysDescr OID (1.3.6.1.2.1.1.1)

Compare sysDescr against expressions inn TCPMON.INIList of regular expressions describing supported network cards

Once matched lookup the section that contains the default port parameters for the network card

Use parameters to configure the new TCPMon portIntegrated network card or single port device simply create the new port

Multi port devices allow user to select which device port to use for printing

Read Network Card information from the MIB-2Request MIB-2.system.sysDescr OID (1.3.6.1.2.1.1.1)

Compare sysDescr against expressions inn TCPMON.INIList of regular expressions describing supported network cards

Once matched lookup the section that contains the default port parameters for the network card

Use parameters to configure the new TCPMon portIntegrated network card or single port device simply create the new port

Multi port devices allow user to select which device port to use for printing

Page 4: Microsoft Standard TCP/IP Port Monitor Futures Mike Fenelon – Software Design Engineer Windows Digital Document Platforms & Solutions Group November 2004

TCPMon Print Device Type detectionTCPMon Print Device Type detection

Additional step after port identification

New Parameter in the Port Install sectionAdded to TCPMon in Windows Server 2003 SP1

DEVICEIDOID# - location within the network device that contains the 1284 DeviceId for the printer attached to the current port

OID is specified per network device

Each port on the device has a separate OID for printer identification

Used in Windows Server 2003 R2 option pack to enable automatic discovery and installation of print queues

Additional step after port identification

New Parameter in the Port Install sectionAdded to TCPMon in Windows Server 2003 SP1

DEVICEIDOID# - location within the network device that contains the 1284 DeviceId for the printer attached to the current port

OID is specified per network device

Each port on the device has a separate OID for printer identification

Used in Windows Server 2003 R2 option pack to enable automatic discovery and installation of print queues

Page 5: Microsoft Standard TCP/IP Port Monitor Futures Mike Fenelon – Software Design Engineer Windows Digital Document Platforms & Solutions Group November 2004

Evolution of TCPMon Network Card detectionEvolution of TCPMon Network Card detection

Current system using TCPMON.INI works fine for existing devices

Supporting new devices is problematicExisting OSes don’t recognize the network cards in TCPMON.INI

TCPMON.INI can be updated in future Service Packs, but there will always be lag for network admins

Current servicing model doesn’t work for Microsoft or IHVs

IHV knows the best parameters for their own network cards

Q: Where can TCPMON.INI info be stored to enable support for new devices as they are released?A: In the network card itself

Current system using TCPMON.INI works fine for existing devices

Supporting new devices is problematicExisting OSes don’t recognize the network cards in TCPMON.INI

TCPMON.INI can be updated in future Service Packs, but there will always be lag for network admins

Current servicing model doesn’t work for Microsoft or IHVs

IHV knows the best parameters for their own network cards

Q: Where can TCPMON.INI info be stored to enable support for new devices as they are released?A: In the network card itself

Page 6: Microsoft Standard TCP/IP Port Monitor Futures Mike Fenelon – Software Design Engineer Windows Digital Document Platforms & Solutions Group November 2004

TCPMON.INI parameters in the deviceTCPMON.INI parameters in the device

Create a new MIB section that contains the basic TCPMON.INI information or the network card

Entry to describe number of output ports device supports

Table containing an entry or each output port

Table Entry describes default parameters for an output port

Contains the information defined in TCPMON.INI syntax as OIDs.

Also contains a new entry for the 1284 Device ID of the printer reachable through the port

Create a new MIB section that contains the basic TCPMON.INI information or the network card

Entry to describe number of output ports device supports

Table containing an entry or each output port

Table Entry describes default parameters for an output port

Contains the information defined in TCPMON.INI syntax as OIDs.

Also contains a new entry for the 1284 Device ID of the printer reachable through the port

Page 7: Microsoft Standard TCP/IP Port Monitor Futures Mike Fenelon – Software Design Engineer Windows Digital Document Platforms & Solutions Group November 2004

Port Table Entry specificsPort Table Entry specifics

PortName: OCTET_STRING – User friendly name of the port. Helps the user select the port on multi-port devices

Protocol: ENUMERATION – identifies the default protocol in TCPMON (RAW or LPR)

RAW Mode only parametersPortNumber: INTEGER – specifies the TCP Port to use when communicating with the Printer

LPR Mode only parametersLPRQueueName: OCTET_STRING – Queue name for LPR mode

LPRByteCountEnabled: INTEGER – Enables/Disables byte counting

PortName: OCTET_STRING – User friendly name of the port. Helps the user select the port on multi-port devices

Protocol: ENUMERATION – identifies the default protocol in TCPMON (RAW or LPR)

RAW Mode only parametersPortNumber: INTEGER – specifies the TCP Port to use when communicating with the Printer

LPR Mode only parametersLPRQueueName: OCTET_STRING – Queue name for LPR mode

LPRByteCountEnabled: INTEGER – Enables/Disables byte counting

Page 8: Microsoft Standard TCP/IP Port Monitor Futures Mike Fenelon – Software Design Engineer Windows Digital Document Platforms & Solutions Group November 2004

Port Table Entry specifics (cont.)Port Table Entry specifics (cont.)

SNMP Status paramtersSnmpStatusEnabled: INTEGER – Enables/Disables staus queries for te printer using SNMP

SnmpCommunityName: OCTET_STRING – Community name used when making SNMP status queries

SNMPResourceDeviceIndex: INTEGER – Device index of the current Port as defined in Host Resource MIB (RFC 2790)

IEEE1284Id: OCTET_STRING – String containing the 1284 Device ID for the printer connected to the current output port.

SNMP Status paramtersSnmpStatusEnabled: INTEGER – Enables/Disables staus queries for te printer using SNMP

SnmpCommunityName: OCTET_STRING – Community name used when making SNMP status queries

SNMPResourceDeviceIndex: INTEGER – Device index of the current Port as defined in Host Resource MIB (RFC 2790)

IEEE1284Id: OCTET_STRING – String containing the 1284 Device ID for the printer connected to the current output port.

Page 9: Microsoft Standard TCP/IP Port Monitor Futures Mike Fenelon – Software Design Engineer Windows Digital Document Platforms & Solutions Group November 2004

New TCPMon port creation procedureNew TCPMon port creation procedure

During Port Creation TCPMon will look for this NumberOfPorts OID

If found walk through the SNMP table to retrieve default parameters

Use retrieved data to help user create the TCPMON portSetup integrated ports automatically

Ask user to select which port on multi-port devices

Once port is created check for IEEE1284Id, if availbale try to install the printer driver automatically

If new OID not found fall back to MIB-2 sysDescr and use TCPMON.INI

During Port Creation TCPMon will look for this NumberOfPorts OID

If found walk through the SNMP table to retrieve default parameters

Use retrieved data to help user create the TCPMON portSetup integrated ports automatically

Ask user to select which port on multi-port devices

Once port is created check for IEEE1284Id, if availbale try to install the printer driver automatically

If new OID not found fall back to MIB-2 sysDescr and use TCPMON.INI

Page 10: Microsoft Standard TCP/IP Port Monitor Futures Mike Fenelon – Software Design Engineer Windows Digital Document Platforms & Solutions Group November 2004

Where to go from here…Where to go from here…

Complete the definition of the new MIB table and associated OIDs

Small group of interested parties working together

Email & teleconference

Figure out where this new MIB extension belongsPrinter MIB?

Host Resource MIB?

MIB-2?

Finish all this in time for Longhorn Beta 1

Complete the definition of the new MIB table and associated OIDs

Small group of interested parties working together

Email & teleconference

Figure out where this new MIB extension belongsPrinter MIB?

Host Resource MIB?

MIB-2?

Finish all this in time for Longhorn Beta 1

Page 11: Microsoft Standard TCP/IP Port Monitor Futures Mike Fenelon – Software Design Engineer Windows Digital Document Platforms & Solutions Group November 2004

Thank You!Thank You!

© 2004 Microsoft Corporation. All rights reserved.© 2004 Microsoft Corporation. All rights reserved.This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.