View Single Post
Old 24-10-2008, 13:00   #6
Ignitionnet
Inactive
 
Join Date: Jun 2008
Location: Leeds, West Yorkshire
Age: 47
Posts: 13,995
Ignitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny stars
Ignitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny stars
Re: Downstream channel 189????

I'll repeat, the channel number is cosmetic, it's just a setting with nothing interesting about it that indicates that the downstream on 339MHz is channel 189. I think you are referring to channel IDs on upstream which do have relevance as they are specified in the MAP that's sent. If you'd changed a customer's downstream channel ID you'd have disconnected them.

It's a second downstream on 339MHz that happens to have an ID of 189 as that's what VM decided the ID was.

Channel downstream can be anything from 1 to 255, and it doesn't matter what VM set so long as it's unique on that CMTS.

No fault here, it's no more worth reporting to VM than the fact the downstream frequency is 339MHz.

EDIT: It could be high because you're on a Cisco 10k chassis, the 189 could indicate which physical slot you're on, it could be a node ID, etc, etc. It's just a label that also means customers can be connected to it via the ID rather than having to specify the full frequency.
Ignitionnet is offline   Reply With Quote