Closed juztas closed 3 weeks ago
This template assumes we only have addresses on host interfaces. I think that is all that RTMON needs. If there will be a use case for having IP/MAC address monitored on the switch ports, we do a design on that use case and then deal with that as a future feature.
The following query: https://github.com/esnet/sense-rtmon/blob/main/autogole-api/src/python/RTMonLibs/SenseAPI.py#L49-L69
Produces this output:
{'Ports': [{'Name': 'Port-channel 102',
'Node': 'T2_US_Caltech:dellos10_s0',
'Peer': 'urn:ogf:network:sc-test.cenic.net:2020:aristaeos_s0:Port-Channel501',
'Port': 'urn:ogf:network:tier2.ultralight.org:2024:dellos10_s0:Port-channel_102',
'Site': 'urn:ogf:network:tier2.ultralight.org:2024',
'Vlan': '1788'},
{'Name': 'Port-channel 101',
'Node': 'T2_US_Caltech:dellos10_s0',
'Peer': 'urn:ogf:network:ultralight.org:2013:dellos9_s0:Port-channel_103',
'Port': 'urn:ogf:network:tier2.ultralight.org:2024:dellos10_s0:Port-channel_101',
'Site': 'urn:ogf:network:tier2.ultralight.org:2024',
'Vlan': '1788'},
{'Name': 'Port-Channel502',
'Node': 'NRM_CENIC:aristaeos_s0',
'Peer': 'urn:ogf:network:sense-oasis-nrp-nautilus.io:2020:oasis:Pc502',
'Port': 'urn:ogf:network:sc-test.cenic.net:2020:aristaeos_s0:Port-Channel502',
'Site': 'urn:ogf:network:sc-test.cenic.net:2020',
'Vlan': '1788'},
{'Name': 'Port-Channel501',
'Node': 'NRM_CENIC:aristaeos_s0',
'Peer': 'urn:ogf:network:tier2.ultralight.org:2024:dellos10_s0:Port-channel_102',
'Port': 'urn:ogf:network:sc-test.cenic.net:2020:aristaeos_s0:Port-Channel501',
'Site': 'urn:ogf:network:sc-test.cenic.net:2020',
'Vlan': '1788'},
{'Name': 'PortChannel502',
'Node': 'T2_US_SDSC:sn3700_s0',
'Peer': 'urn:ogf:network:nrp-nautilus.io:2020:edgecore_s0:PortChannel502',
'Port': 'urn:ogf:network:nrp-nautilus.io:2020:sn3700_s0:PortChannel502',
'Site': 'urn:ogf:network:nrp-nautilus.io:2020',
'Vlan': '1788'},
{'Name': 'Pc502',
'Node': 'T2_US_UCSD_OASIS:oasis',
'Peer': 'urn:ogf:network:sc-test.cenic.net:2020:aristaeos_s0:Port-Channel502',
'Port': 'urn:ogf:network:sense-oasis-nrp-nautilus.io:2020:oasis:Pc502',
'Site': 'urn:ogf:network:sense-oasis-nrp-nautilus.io:2020',
'Vlan': '1788'},
{'Name': 'Pc500',
'Node': 'T2_US_UCSD_OASIS:oasis',
'Peer': 'urn:ogf:network:nrp-nautilus.io:2020:edgecore_s0:PortChannel500',
'Port': 'urn:ogf:network:sense-oasis-nrp-nautilus.io:2020:oasis:Pc500',
'Site': 'urn:ogf:network:sense-oasis-nrp-nautilus.io:2020',
'Vlan': '1788'},
{'Name': 'Port-channel 103',
'Node': 'T2_US_Caltech_Test:dellos9_s0',
'Peer': 'urn:ogf:network:tier2.ultralight.org:2024:dellos10_s0:Port-channel_101',
'Port': 'urn:ogf:network:ultralight.org:2013:dellos9_s0:Port-channel_103',
'Site': 'urn:ogf:network:ultralight.org:2013',
'Vlan': '1788'},
{'Name': 'PortChannel500',
'Node': 'T2_US_SDSC:edgecore_s0',
'Peer': 'urn:ogf:network:sense-oasis-nrp-nautilus.io:2020:oasis:Pc500',
'Port': 'urn:ogf:network:nrp-nautilus.io:2020:edgecore_s0:PortChannel500',
'Site': 'urn:ogf:network:nrp-nautilus.io:2020',
'Vlan': '1788'},
{'Name': 'PortChannel502',
'Node': 'T2_US_SDSC:edgecore_s0',
'Peer': 'urn:ogf:network:nrp-nautilus.io:2020:sn3700_s0:PortChannel502',
'Port': 'urn:ogf:network:nrp-nautilus.io:2020:edgecore_s0:PortChannel502',
'Site': 'urn:ogf:network:nrp-nautilus.io:2020',
'Vlan': '1788'}]}
Would be nice to extend it to include ipv6-address and mac-address. The following request provisioned on sense-o-dev: d1d76373-bd8d-4893-8aaf-a66405aa9224 @xi-yang could you help me on this to extend and include switch/router ipv6-address and mac-address in query?
The query only fetches the ip and mac addresses for host vlan ports. None of the above is a host port.
We may add Mac address for switch ports. But most switches have no Mac address in the model.
Most SiteRMs (with switch control) are exposing mac-address for each port (in many cases it is the same, but on some devices they have diff based on port, for example:
<urn:ogf:network:ultralight.org:2013:dellos9_s0:Port-channel_103:mac-address+4c__76__25__e8__44__c2> a mrs:NetworkAddress ;
mrs:type "mac-address" ;
mrs:value "4c:76:25:e8:44:c2" .
Is this not right format? I could change that if needed.
Since the service instance is for a path of VLAN ports, do we want to expose the physical ports MAC? I understand sometimes they are the same but not always.
Do you see an issue exposing the physical port mac address?
Do you see an issue exposing the physical port mac address?
Not really for RTMON. For SENSE-O portal add-on, we will limit the manifest to only show model information within the instance.
All updated here: https://github.com/esnet/sense-rtmon/issues/114#issuecomment-2254185452.
Action items now:
First 2 action items done here: https://github.com/esnet/sense-rtmon/pull/129
Current template:
Need to include the following info (ipv6 address/mac address of switch port ):
@xi-yang could you take a look into this?